ENodeB Performance Monitoring Reference (V100R004C00 - 03) (PDF) - en

eNodeB
V100R004C00
Performance Monitoring
Reference
Issue 03
Date 2011-12-24
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. 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 03 (2011-12-24) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd
eNodeB
Performance Monitoring Reference Contents
Contents
1 Introduction ......................................................................................................................................... 1
2 Sector Performance Monitoring ..................................................................................................... 4
2.1 Parameters for Sector Performance Monitoring ............................................................................................... 4
2.2 Results of Sector Performance Monitoring ...................................................................................................... 5
3 RRU/RFU Performance Monitoring.............................................................................................. 6

3.1 Parameters for RRU/RFU Performance Monitoring ........................................................................................ 6
3.2 Results of RRU/RFU Performance Monitoring ............................................................................................... 7
4 Spectrum Detection ........................................................................................................................... 8

4.1 Parameters for Spectrum Detection .................................................................................................................. 8
4.2 Results of Spectrum Detection ......................................................................................................................... 9
5 QoS Satisfaction Rate Monitoring .............................................................................................. 10

5.1 Parameters for QoS Satisfaction Rate Monitoring ......................................................................................... 10
5.2 Results of QoS Satisfaction Rate Monitoring................................................................................................. 11
6 General Throughput Monitoring ................................................................................................ 12

6.1 Parameters for General Throughput Monitoring ............................................................................................ 12
6.2 Results of General Throughput Monitoring ................................................................................................... 13
6.2.1 Typical Scenario .................................................................................................................................... 13
6.2.2 RAN Sharing Scenario .......................................................................................................................... 14
7 Service Statistics Monitoring ........................................................................................................ 16

7.1 Parameters for Service Statistics Monitoring ................................................................................................. 16
7.2 Results of Service Statistics Monitoring ........................................................................................................ 16
8 User Statistics Monitoring ............................................................................................................. 17

8.1 Parameters for User Statistics Monitoring...................................................................................................... 17
8.2 Results of User Statistics Monitoring ............................................................................................................. 17
9 RB Usage Monitoring ..................................................................................................................... 19

9.1 Parameters for RB Usage Monitoring ............................................................................................................ 19
9.2 Results of RB Usage Monitoring ................................................................................................................... 19
9.2.1 Typical Scenario .................................................................................................................................... 19
9.2.2 RAN Sharing Scenario .......................................................................................................................... 20
Issue 03 (2011-12-24) Huawei Proprietary and Confidential ii

eNodeB
10 ICIC Monitoring ............................................................................................................................ 21

10.1 Parameters for ICIC Monitoring .................................................................................................................. 21
10.2 Results of ICIC Monitoring.......................................................................................................................... 21
11 MU-MIMO Monitoring ............................................................................................................... 24

11.1 Parameters for MU-MIMO Monitoring........................................................................................................ 24
11.2 Results of MU-MIMO Monitoring ............................................................................................................... 24
12 Interference Detection Monitoring ........................................................................................... 25

12.1 Parameters for Interference Detection Monitoring....................................................................................... 25
12.2 Results of Interference Detection Monitoring .............................................................................................. 25
13 Scheduled Cell-Level UE Information Monitoring .............................................................. 27

13.1 Parameters for Scheduled Cell-Level UE Information Monitoring.............................................................. 27
13.2 Results of Scheduled Cell-Level UE Information Monitoring ..................................................................... 27
14 HARQ Status Monitoring ............................................................................................................ 29

14.1 Parameters for HARQ Status Monitoring .................................................................................................... 29
14.2 Results of HARQ Status Monitoring............................................................................................................ 29
15 Air-Interface DCI Status Monitoring ....................................................................................... 31

15.1 Parameters for Air-Interface DCI Status Monitoring ................................................................................... 31
15.2 Results of Air-Interface DCI Status Monitoring........................................................................................... 32
16 Air-Interface DRB Statistics Monitoring ................................................................................. 34

16.1 Parameters for Air-Interface DRB Statistics Monitoring.............................................................................. 34
16.2 Results of Air-Interface DRB Statistics Monitoring..................................................................................... 34
17 BLER Monitoring ........................................................................................................................... 36

17.1 Parameters for BLER Monitoring ................................................................................................................ 36
17.2 Results of BLER Monitoring ....................................................................................................................... 36
18 Power Headroom Monitoring .................................................................................................... 39

18.1 Parameters for Power Headroom Monitoring .............................................................................................. 39
18.2 Result of Power Headroom Monitoring ....................................................................................................... 39
19 Channel Quality Monitoring ...................................................................................................... 40

19.1 Parameters for Channel Quality Monitoring ................................................................................................ 40
19.2 Results of Channel Quality Monitoring ....................................................................................................... 40
20 Scheduling Monitoring ................................................................................................................ 42

20.1 Parameters for Scheduling Monitoring ........................................................................................................ 42
20.2 Results of Scheduling Monitoring................................................................................................................ 42
21 RLC Data Stream Monitoring..................................................................................................... 45

21.1 Parameters for RLC Data Stream Monitoring .............................................................................................. 45
21.2 Result of RLC Data Stream Monitoring ....................................................................................................... 45
22 Throughput Monitoring............................................................................................................... 46
Issue 03 (2011-12-24) Huawei Proprietary and Confidential iii

eNodeB
22.1 Parameters for Throughput Monitoring........................................................................................................ 46

22.2 Results of Throughput Monitoring ............................................................................................................... 46
23 AQM Monitoring ........................................................................................................................... 48

23.1 Parameters for AQM Monitoring ................................................................................................................. 48
23.2 Results of AQM Monitoring......................................................................................................................... 48
24 Uplink Power Control Monitoring ........................................................................................... 50

24.1 Parameters for Uplink Power Control Monitoring ....................................................................................... 50
24.2 Results of Uplink Power Control Monitoring .............................................................................................. 50
25 Downlink Power Control Monitoring ..................................................................................... 53

25.1 Parameters for Downlink Power Control Monitoring .................................................................................. 53
25.2 Results of Downlink Power Control Monitoring ......................................................................................... 53
26 Uplink ICIC Monitoring .............................................................................................................. 56

26.1 Parameters for Uplink ICIC Monitoring ...................................................................................................... 56
26.2 Results of Uplink ICIC Monitoring.............................................................................................................. 56
27 MCS Statistics Monitoring .......................................................................................................... 58

27.1 Parameters for MCS Statistics Monitoring................................................................................................... 58
27.2 Results of MCS Statistics Monitoring .......................................................................................................... 58
28 IP Performance Monitoring ........................................................................................................ 60

28.1 Parameters for IP Performance Monitoring.................................................................................................. 60
28.2 Results of IP Performance Monitoring ......................................................................................................... 60
29 IP Path Performance Monitoring ............................................................................................... 62

29.1 Parameters for IP Path Performance Monitoring.......................................................................................... 62
29.2 Results of IP Path Performance Monitoring ................................................................................................. 62
30 SCTP Performance Monitoring .................................................................................................. 64

30.1 Parameters for SCTP Performance Monitoring ............................................................................................ 64
30.2 Results of SCTP Performance Monitoring ................................................................................................... 64
31 PPPoE Performance Test .............................................................................................................. 66

31.1 Parameters for a PPPoE Performance Test ................................................................................................... 66
31.2 Results of the PPPoE Performance Test ....................................................................................................... 67
32 Local and Forwarded Traffic Monitoring ................................................................................ 69

32.1 Parameters for Local and Forwarded Traffic Monitoring............................................................................. 69
32.2 Results of Local and Forwarded Traffic Monitoring .................................................................................... 69
33 Logical Port Monitoring ............................................................................................................... 71

33.1 Parameters for Logical Port Monitoring....................................................................................................... 71
33.2 Results of Logical Port Monitoring .............................................................................................................. 72
33.2.1 Single-Rate Mode................................................................................................................................ 72
33.2.2 Double-Rate Mode .............................................................................................................................. 73
Issue 03 (2011-12-24) Huawei Proprietary and Confidential iv

eNodeB
34 TRM Statistic Monitoring ........................................................................................................... 76

34.1 Parameters for TRM Statistic Monitoring .................................................................................................... 76
34.2 Results of TRM Statistic Monitoring ........................................................................................................... 76
35 UDP Injection Test Monitoring ................................................................................................. 79

35.1 Parameters for UDP Injection Test Monitoring ............................................................................................ 79
35.2 Result of UDP Injection Test Monitoring..................................................................................................... 80
Issue 03 (2011-12-24) Huawei Proprietary and Confidential v

eNodeB
Performance Monitoring Reference 1 Introduction
1 Introduction
Purpose
This document describes eNodeB performance monitoring results and explains monitoring
items in terms of the meanings, value ranges, and calculation methods.
Product Versions
The following table lists the product versions related to this document.
Product Name Product Version

DBS3900 LTE V100R004C00
DBS3900 LTE TDD V100R004C00

BTS3900 LTE V100R004C00
BTS3900A LTE V100R004C00
BTS3900L LTE V100R004C00

BTS3202E V100R004C00
Intended Audience
This document is intended for:
 Technical support engineers
 Maintenance engineers
Change History
This document is revised based on review comments. The latest document contains all
updates.
Document Issues
The document issues are as follows:
Issue 03 (2011-12-24) Huawei Proprietary and Confidential 1

eNodeB
 03 (2011-12-24)
 02 (2011-11-15)
 01 (2011-09-15)
 Draft A (2011-07-15)
03 (2011-12-24)
This is the third commercial release.
Compared with issue 02 (2011-11-15) of V100R004C00, this issue adds the following topics.
Topic Change Description

6.2 Results of General Throughput Added the description of the results of
Monitoring general throughput monitoring in a RAN
sharing scenario.
9.2 Results of RB Usage Monitoring Added the description of the results of

resource block (RB) usage monitoring in a
RAN sharing scenario.
33 Logical Port Monitoring  Added the parameters for logical port
monitoring.
 Added the description of the results of
logical port monitoring.
Compared with issue 02 (2011-11-15) of V100R004C00, this issue incorporates the change
described in the following table.

8.2 Results of User Statistics Monitoring Modified the description of the results of the
monitoring item General Users Number.
Compared with issue 02 (2011-11-15) of V100R004C00, this issue removes the following
topic.

13.2 Results of Scheduled Cell-Level UE Removed the parameter Total DLSCH
Information Monitoring Candidates Within Monitor Period.
02 (2011-11-15)
This is the second commercial release.
Compared with issue 01 (2011-09-15) of V100R004C00, this issue adds the following topic.

eNodeB
31 PPPoE Performance Test  Added the parameters for a Point-to-Point

Protocol over Ethernet (PPPoE)
performance test.
 Added the description of the results of the
PPPoE performance test.
Compared with issue 01 (2011-09-15) of V100R004C00, this issue incorporates the change
14.2 Results of HARQ Status Monitoring Modified the description of the results of
HARQ status monitoring.
Compared with issue 01 (2011-09-15) of V100R004C00, this issue does not remove any
topics.
01 (2011-09-15)
This is the first commercial issue.
Compared with draft A (2011-07-15) of V100R004C00, this issue adds the following topic.

3 RRU/RFU Performance Monitoring  Added the parameters for RRU/RFU
performance monitoring.
 Added the results of RRU/RFU
Compared with draft A (2011-07-15) of V100R004C00, this issue incorporates the changes

5 QoS Satisfaction Rate Monitoring  Added the parameters for operator QoS
satisfaction rate monitoring.
 Added the results of operator QoS
satisfaction rate monitoring.
Compared with draft A (2011-07-15) of V100R004C00, this issue does not remove any topics.
Draft A (2011-07-15)
This is the draft.

eNodeB
Performance Monitoring Reference 2 Sector Performance Monitoring
2 Sector Performance Monitoring
Radio networks work in open environments and therefore are inevitably affected by
interference. Interference detection and location are required in network deployment and
long-term network operation. The base station is a receiver system and supports scalable
bands. Therefore, it can be used for simple collection of 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 the eNodeB and detect internal interference in the eNodeB. The RRU or
RFU calculates the received signal strength and reports the strength to the LMT after scanning
frequencies continuously. The received signal strength is used as reference for interference
location and analysis.
2.1 Parameters for Sector Performance Monitoring

Table 2-1 Parameters for sector performance monitoring
Parameter Description
Monitor Item It can be set to UL Widefreq Scan.
Monitor Period Period for 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.
UL EARFCN Uplink EARFCN of a cell. It is set to a value in the ranges of 18000 to
41589 and 65236 to 65535.
UL Bandwidth Uplink bandwidth of the cell. It can be set to 1.4M, 3M, 5M, 10M,
15M, or 20M.
Autosave to File After you select the Autosave to File check box, monitoring results
are automatically saved in the default path. You can also specify the
file name, file format, and another save path.

eNodeB
Performance Monitoring Reference 2 Sector Performance Monitoring
2.2 Results of Sector Performance Monitoring

NOTE
In the figure of monitoring result description, the horizontal axis indicates frequency, center frequency for
each RB at the air interface, which is in units of kHz. The vertical axis indicates the received signal
strength, frequency spectrum, which is in units of dBm.
Table 2-2 Results of sector performance monitoring
Monitor Item Parameter Unit Value Range Description

UL Widefreq Signal Strength dBm -140 to -50 Received signal
Scan strength indicator
(RSSI) of each RB
from the physical layer
when the monitoring
result is reported.

eNodeB
Performance Monitoring Reference 3 RRU/RFU Performance Monitoring
3 RRU/RFU Performance Monitoring
This task is used to monitor the performance of the remote radio unit (RRU) or radio
frequency unit (RFU) power, temperature, and distance to fault (DTF).
3.1 Parameters for RRU/RFU Performance Monitoring

Table 3-1 Parameters for RRU/RFU performance monitoring
Monitor Item It can be set to RRU/RFU Output Power, RRU/RFU
Temperature, or Distance To Fault(DTF).
Cabinet No. Number of the cabinet where the board for RRU/RFU performance
monitoring is located.
Subrack No. Number of the subrack where the board for RRU/RFU performance
Slot No. Number of the slot where the board for RRU/RFU performance
Monitor Period Period for reporting monitoring results.
(ms)
TX Channel No. Number of the TX channel located on the board for RRU/RFU
Autosave to File After you select the Autosave to File check box, monitoring results
are automatically saved in the default path. You can customize the
folder and file name.

eNodeB
Performance Monitoring Reference 3 RRU/RFU Performance Monitoring
3.2 Results of RRU/RFU Performance Monitoring

Table 3-2 Results of RRU/RFU performance monitoring
Monitor Parameter Unit Value Description

Item Range
RRU/RFU Output Power dBm -200 to -1 Output power of a carrier.
Output
Power Output Power of TX dBm -200 to -1 Output power of a TX
Carrier channel.
°
RRU/RFU Board Temperature C -100 to 200 Board temperature.
Temperature °
LPA Temperature C -100 to 200 Power amplifier
temperature.
Distance To VSWR Position(M) m 0 to (232-1) Distance between the
Fault(DTF) antenna port and the
voltage standing wave ratio
(VSWR) point.
VSWR(0.1) N/A 0 to (216-1) VSWR value.

eNodeB
Performance Monitoring Reference 4 Spectrum Detection
4 Spectrum Detection
This task is used to detect the spectrum status, monitoring the interference in frequency and
time domains in radio environments by analyzing spectrum and power distribution of sampled
data.
4.1 Parameters for Spectrum Detection

Table 4-1 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.
Cabinet No. Number of the cabinet where the board for spectrum detection is
located.
Subrack No. Number of the subrack where the board for spectrum detection is
located.
Slot No. Number of the slot where the board for spectrum detection is located.
RBW Time frequency of Fast Fourier Transport (FFT) frequency detection,
in units of kHz.
NOTE
As stipulated by protocols, the minimum accuracy is 100 kHz. You are advised to
set this parameter to 100 kHz, which is the default value.
Monitor Period Period for reporting monitoring results. It can be set to 1000, 2000, or
(ms) 3000.
Autosave to File The Autosave to File check box is selected by default, and monitoring
results are automatically saved in the default path. You can also
customize another save path and file name.

eNodeB
Performance Monitoring Reference 4 Spectrum Detection
4.2 Results of Spectrum Detection

Results of spectrum detection are used for fault diagnosis and are not displayed on the LMT.
If the results need to be viewed, send the result file to Huawei technical support for analysis.

eNodeB
Performance Monitoring Reference 5 QoS Satisfaction Rate Monitoring
5 QoS Satisfaction Rate Monitoring
QoS satisfaction rates of services with different QoS class identifiers (QCIs) are important
indicators of evaluating radio network performance. This task is used to check the QoS
satisfaction rates of services to evaluate service performance.
5.1 Parameters for QoS Satisfaction Rate Monitoring

Table 5-1 Parameters for QoS satisfaction rate monitoring
Monitor Item It can be set to GBR Degrade Flag, UL QCI1 Satisfaction rate of
Service, UL QCI2 Satisfaction rate of Service, UL QCI3
Satisfaction rate of Service, UL QCI4 Satisfaction rate of
Service, DL QCI1 Satisfaction rate of Service, DL QCI2
Satisfaction rate of Service, DL QCI3 Satisfaction rate of
Service, DL QCI4 Satisfaction rate of Service, CN Operator
GBR Degrade Flag, CN Operator UL QCI1 Satisfaction rate of
Service, CN Operator UL QCI2 Satisfaction rate of Service, CN
Operator UL QCI3 Satisfaction rate of Service, CN Operator UL
QCI4 Satisfaction rate of Service, CN Operator DL QCI1
Satisfaction rate of Service, CN Operator DL QCI2 Satisfaction
rate of Service, CN Operator DL QCI3 Satisfaction rate of
Service, CN Operator DL QCI4 Satisfaction rate of Service, or a
combination of these items.
Local Cell ID ID of the cell on which QoS satisfaction rate monitoring is
performed.
CN Operator ID ID of the operator on which QoS satisfaction rate monitoring is
performed.
(ms) 500, 1000, or 2000.

eNodeB
Performance Monitoring Reference 5 QoS Satisfaction Rate Monitoring
5.2 Results of QoS Satisfaction Rate Monitoring

Table 5-2 Results of QoS satisfaction rate monitoring

GBR Degrade GBR % 0 to 100 Guaranteed bit rate (GBR)
Flag Degrade service degradation flag. Value
Flag 0 indicates the service is not
degraded. Value 100 indicates
the service is degraded.
UL QCI UL QCI % 0 to 100 Average uplink QoS
Satisfaction Satisfaction satisfaction rates of different
rate of Service rate of services in a cell when the
Service monitoring result is reported.
QoS satisfaction rate is used to
check QoS can be guaranteed.
DL QCI DL QCI % 0 to 100 Average downlink QoS

Satisfaction Satisfaction satisfaction rates of different
rate of Service rate of services in a cell when the
Service monitoring result is reported.
QoS satisfaction rate is used to
check QoS can be guaranteed.
CN Operator CN % 0 to 100 GBR service degradation flag.
GBR Degrade Operator Value 0 indicates the service is
Flag GBR not degraded. Value 100
Degrade indicates the service is
Flag degraded.
CN Operator CN % 0 to 100 Average uplink QoS
UL QCI Operator satisfaction rates of different
Satisfaction UL QCI services in an operator when
rate of Service Satisfaction the monitoring result is
rate of reported. QoS satisfaction rate
Service is used to check QoS can be
guaranteed.
CN Operator CN % 0 to 100 Average downlink QoS
DL QCI Operator satisfaction rates of different
Satisfaction DL QCI services in an operator when
rate of Service Satisfaction the monitoring result is
rate of reported. QoS satisfaction rate
Service is used to check QoS can be
guaranteed.

eNodeB
Performance Monitoring Reference 6 General Throughput Monitoring
6 General Throughput Monitoring
This task is used to monitor the general throughput of GBR services and non-GBR services to
check the air interface quality and scheduling algorithms.
6.1 Parameters for General Throughput Monitoring

Table 6-1 Parameters for throughput monitoring
Monitor Item It can be set to RLC thruput of GBR service, RLC thruput, RLC
thruput of NON-GBR service, or a combination of these items.
Local Cell ID ID of the cell on which throughput monitoring is performed.
Monitor Period (ms) Period for reporting monitoring results. It can be set to 50, 100,
200, 500, 1000, or 2000.

eNodeB
6.2 Results of General Throughput Monitoring

6.2.1 Typical Scenario
Table 6-2 Results of general throughput monitoring in a typical scenario
RLC thruput Cell Uplink RLC bit/s 0 to Uplink throughput for

Throughput 300,000,000 service data units
(bit/s) (SDUs) of all service
data radio bearers
(DRBs) received at the
Radio Link Control
(RLC) layer in the cell
within a monitoring
period.
Cell GBR Traffic bit/s 0 to Downlink throughput

Downlink RLC 300,000,000 for SDUs of all service
Throughput DRBs transmitted at the
(bit/s) RLC layer in the cell
within a monitoring
period.
RLC thruput of Cell GBR Traffic bit/s 0 to Uplink throughput for
GBR service Uplink RLC 300,000,000 service data units
Throughput (SDUs) of all GBR
(bit/s) services received at the
radio link control
(RLC) RLC layer in the
cell within a monitoring
period.
Cell GBR Traffic bit/s 0 to Downlink throughput

Downlink RLC 300,000,000 for SDUs of all GBR
Throughput services transmitted at
(bit/s) the RLC layer in the
cell within a monitoring
period.
RLC thruput of Cell Non-GBR bit/s 0 to Uplink throughput for
NON-GBR Traffic Uplink 300,000,000 SDUs of all non-GBR
service RLC Throughput services received at the
(bit/s) RLC layer in the cell
within a monitoring
period.
Cell Non-GBR bit/s 0 to Downlink throughput
Traffic Downlink 300,000,000 for SDUs of all
RLC Throughput non-GBR services
(bit/s) transmitted at the RLC
layer in the cell within a
monitoring period.

eNodeB
6.2.2 RAN Sharing Scenario

Table 6-3 Results of general throughput monitoring in a RAN sharing scenario

CN Operator ID CN Operator ID N/A 0 to 3 Index of the operator
that is configured in
the current eNodeB.
RLC thruput CN Operator Cell bit/s 0 to Uplink throughput for

Uplink RLC 300,000,000 SDUs of all service
Throughput DRBs received at the
RLC layer for the
operator within a
monitoring period.
CN Operator Cell bit/s 0 to Downlink throughput
Downlink RLC 300,000,000 for SDUs of all
Throughput service DRBs
transmitted at the
RLC layer for the
operator within a
monitoring period.
RLC thruput of CN Operator Cell bit/s 0 to Uplink throughput for
GBR service GBR Traffic Uplink 300,000,000 SDUs of all GBR
RLC Throughput services received at
the RLC layer for the
operator within a
monitoring period.
GBR Traffic 300,000,000 for SDUs of all GBR
Downlink RLC services transmitted
Throughput at the RLC layer for
the operator within a
monitoring period.
RLC thruput of CN Operator Cell bit/s 0 to Uplink throughput for
NON-GBR Non-GBR Traffic 300,000,000 SDUs of all non-GBR
service Uplink RLC services received at
Throughput the RLC layer for the
operator within a
monitoring period.

Non-GBR Traffic 300,000,000 for SDUs of all
Downlink RLC non-GBR services
Throughput transmitted at the
RLC layer for the
operator within a
monitoring period.

eNodeB
NOTE
In a RAN sharing scenario, more general throughputs are monitored compared with a typical scenario. For
example, in the RAN sharing scenario where two operators share a RAN, the preceding monitoring items
are monitored separately for the two operators.

eNodeB
Performance Monitoring Reference 7 Service Statistics Monitoring
7 Service Statistics Monitoring
This task is used to monitor the number of services in a cell to view the distribution of
services with different QCIs.
7.1 Parameters for Service Statistics Monitoring

Table 7-1 Parameters for service statistics monitoring
Monitor Item It can be set to Service Number of QCI1, Service Number of
QCI2, Service Number of QCI3, 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 for service number monitoring.

200, 500, 1000, or 2000.
7.2 Results of Service Statistics Monitoring

Table 7-2 Results of service statistics monitoring
Monitor Item Parameter Unit Value Description

Range
Service Number Service Number of Number 0 to 4000 Total number of
of QCI QCI services with different
QCIs when the
monitoring result is
reported.

eNodeB
Performance Monitoring Reference 8 User Statistics Monitoring
8 User Statistics Monitoring
This task is used to monitor the number of users in different scenarios to view the distribution
of users in a cell.
8.1 Parameters for User Statistics Monitoring

Table 8-1 Parameters for user statistics monitoring
Monitor Item It can be set to Keep UL Synch Users Number, General Users
Number, NO-Activated Users Number, or a combination of these
items.
Local Cell ID ID of the cell for user number monitoring.
(ms) 500, 1000, or 2000.
8.2 Results of User Statistics Monitoring

Table 8-2 Results of user statistics monitoring

Range
Keep UL Synch Keep UL Synch Number 0 to 2,000 Number of users with
Users Number Users Number uplink synchronization
when the monitoring
result is reported,
which is the number of
active users.

eNodeB
Performance Monitoring Reference 8 User Statistics Monitoring

Range
General Users General Users Number 0 to 2,000 Number of connected
Number Number users and users that are
requesting access to the
evolved universal
terrestrial radio access
network (E-UTRAN)
when the monitoring
result is reported.
Connected users are
the users for which
uplink synchronization
is maintained or lost.
Users that are
E-UTRAN are the
users initiating a radio
resource control (RRC)
connection request or
E-UTRAN from
another network during
handovers.
NO-Activated NO-Activated Number 0 to 2,000 Number of non-active
Users Number Users Number users when the
reported, which is the
number of users with
uplink
out-of-synchronization.

eNodeB
Performance Monitoring Reference 9 RB Usage Monitoring
9 RB Usage Monitoring
This task is used to monitor the usage of cell-level RBs in different scheduling modes. RB is
the minimum unit of time-frequency resource allocation.
9.1 Parameters for RB Usage Monitoring

Table 9-1 Parameters for RB usage monitoring
Local Cell ID ID of the cell for RB usage monitoring.
200, 500, 1000, or 2000.
9.2 Results of RB Usage Monitoring

9.2.1 Typical Scenario
Table 9-2 Results of RB usage monitoring in a typical scenario

Item Range
Usage of Downlink Numbe 0 to Number of downlink RBs used
RB Equivalent Used r 200,000 within a monitoring period.
RB Num
Uplink Numbe 0 to Number of uplink RBs used
Equivalent Used r 200,000 within a monitoring period.
RB Num

eNodeB
Performance Monitoring Reference 9 RB Usage Monitoring

Item Range
Downlink Freq Numbe 0 to Number of RBs scheduled for
Diversity Used r 200,000 downlink diversity within a
RB Num monitoring period.
Downlink Freq Numbe 0 to Number of RBs scheduled for
Select Used RB r 200,000 downlink frequency selection
Num within a monitoring period.
Downlink Harq Numbe 0 to Number of RBs scheduled for
RB Used RB r 200,000 downlink HARQ retransmission
Num within a monitoring period.
Uplink Pucch RB Numbe 0 to Number of RBs used by the

Num r 200,000 uplink PUCCH when the
monitoring result is reported.
9.2.2 RAN Sharing Scenario

Table 9-3 Results of RB usage monitoring in a RAN sharing scenario

Item Range
Usage of CN Operator ID N/A 0 to 3 Index of the operator that is

RB configured in the current
eNodeB.
CN Operator Numbe 0 to Number of downlink RBs used

Downlink r 200,000 by the operator.
Equivalent Used
RB Num
CN Operator Numbe 0 to Number of uplink RBs used by

Uplink r 200,000 the operator.
Equivalent Used
RB Num
NOTE
In a RAN sharing scenario, more RB usage items are monitored compared with a typical scenario. For
example, in the RAN sharing scenario where two operators share a RAN, the preceding monitoring items
are monitored separately for the two operators.

eNodeB
Performance Monitoring Reference 10 ICIC Monitoring
10 ICIC Monitoring
This task is used to check the status of inter-cell interference coordination (ICIC) by
monitoring the data associated to ICIC.
10.1 Parameters for ICIC Monitoring

Table 10-1 Parameters for ICIC monitoring
Monitor Item 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
these items.
Local Cell ID ID of the cell for ICIC monitoring.
(ms) 500, 1000, or 2000.
10.2 Results of ICIC Monitoring

Table 10-2 Results of ICIC monitoring

Item Range
HII Hii Sent Global N/A N/A Physical cell identifier (PCI)
Information Informati Cell Id of the serving cell.

eNodeB

Item Range
on Valid Number 0 to Number of valid RBs in one
RB 110 HII when the monitoring
Number result is reported, which is the
in one same as the number of RBs
Hii occupied by the current cell
bandwidth.
Hii Bit N/A N/A HII information about the

Informa serving cell. For details, see
tion 3GPP TS 36.421.
Stream
in One
Hii
Valid Hii Valid Number 0 to 4 Number of valid HIIs

Received Hii received from neighboring
Num Receive cells by the serving cell when
d the monitoring result is
Number reported.
Hii Global N/A N/A PCI of a neighboring cell that

Received Cell Id transmits HII information to
Informati the serving cell.
on
Valid Number 0 to Number of valid RBs in one
RB 110 HII when the monitoring
Num in result is reported.
One Hii
HII N/A N/A HII information about a
Informa neighboring cell that transmits
tion the information to the serving
cell. For details, see 3GPP TS
36.421.
OI OI Sent Global N/A N/A PCI of the serving cell.
Information Informati Cell Id
on
RB 110 OI when the monitoring result
Num in is reported, which is the same
One OI as the number of RBs
occupied by the current cell
bandwidth.
OI N/A N/A OI information about the
Informa serving cell, including high,
tion medium, and low interference
levels. For details, see 3GPP
TS 36.421.

eNodeB

Item Range
Valid OI Valid Number 0 to 4 Number of valid OIs received
Received OI from neighboring cells by the
Num Receive serving cell when the
d Num monitoring result is reported.
OI Global N/A N/A PCI of a neighboring cell that
Received Cell Id transmits OI information to
Informati the serving cell.
on
RB 110 OI when the monitoring result
Num in is reported, which is the same
One OI as the number of RBs
occupied by the current cell
bandwidth.
OI N/A N/A OI information about a

Informa neighboring cell that transmits
tion the information to the serving
cell, including high, medium,
and low interference levels.
For details, see 3GPP TS
36.421.
Proportion Proportion of High % 0 to Proportion of
of High Interference RB in 100 high-interference RBs in the
Interference System Bandwidth serving cell to RBs occupied
RB in by the current cell bandwidth
System when the monitoring result is
Bandwidth reported.
Edge user Global Cell Id N/A N/A PCI of the local cell.
RB
Information EdgeUser Valid RB Number 0 to Number of valid RBs in the
Num 110 available band for cell edge
users (CEUs) when the
EdgeUser Bit N/A N/A Information about the
Information Stream available band for CEUs in
the serving cell. For details,
see 3GPP TS 36.421.
Neighbor Valid Cell Num Number 0 to 32 Number of valid neighboring
Cell List cells used for ICIC when the
Information monitoring result is reported.
Cell Neighbor List N/A N/A PCI of an available

neighboring cell used by ICIC

eNodeB
Performance Monitoring Reference 11 MU-MIMO Monitoring
11 MU-MIMO Monitoring
This task is used to monitor the number of UEs paired with multi-user multiple-input
multiple-output (MU-MIMO) within a transmission time interval (TTI) so that the paired UEs
can be viewed conveniently.
11.1 Parameters for MU-MIMO Monitoring

Table 11-1 Parameters for MU-MIMO monitoring
Local Cell ID ID of the cell for MU-MIMO monitoring.
(ms) 500, 1000, or 2000.
11.2 Results of MU-MIMO Monitoring

Table 11-2 Results of MU-MIMO monitoring

Item Range
Multi MIMO UE Pair Pair 0 to 16 Number of UEs paired with
User-MIM Num MU-MIMO when the
O monitoring result is reported.
Two UEs paired with
MU-MIMO are called one
pair.

eNodeB
Performance Monitoring Reference 12 Interference Detection Monitoring
12 Interference Detection Monitoring
The interference detection monitoring process is described as follows:

 An RRU collects data and the LMPT performs fast Fourier transformation (FFT)
calculation analysis and processes the data.
 The signal spectrum within a configured frequency range is displayed in re al time.
Interference detection monitoring implements some functions of a spectrum analyzer and
facilitates identification and analysis of interference problems.
12.1 Parameters for Interference Detection Monitoring

Table 12-1 Parameters for interference detection monitoring
Local Cell ID ID of the cell on which interference detection monitoring is

performed.
200, 500, 1000, or 2000.
12.2 Results of Interference Detection Monitoring

Table 12-2 Results of interference detection monitoring

Item Range
Interference RB Spectrum dBm -216 to 216 Received signal strength
Detect Information in an RB.
Received Signal dBm –140 to –50 Received signal strength

Strength Indicator in the wideband.

eNodeB
Performance Monitoring Reference 12 Interference Detection Monitoring

Item Range
System Bandwidth Numb 0 to 100 Current system
er bandwidth (number of
RBs).
Antenna RSSI dBm –140 to –50 Received signal strength
indicator for an antenna.
PUSCH Cell dBm –32,768 to Average interference
32,767 noise power in an RB.

eNodeB
Performance Monitoring Reference 13 Scheduled Cell-Level UE Information Monitoring
13 Scheduled Cell-Level UE Information

Monitoring
This task is used to monitor the number of scheduled cell-level UEs in different scheduling
modes.
13.1 Parameters for Scheduled Cell-Level UE Information

Monitoring
Table 13-1 Parameters for scheduled cell-level UE information monitoring
Local Cell ID ID of the cell on which scheduled cell-level UE information
monitoring is performed.
(ms) 500, 1000, or 2000.
13.2 Results of Scheduled Cell-Level UE Information

Monitoring
Table 13-2 Results of scheduled cell-level UE information monitoring

Range
Scheduled Users Total DLSCH Users Number 0 to 65535 Total number of UEs
Statistic Within Monitor Period for downlink
scheduling within a
monitoring period.

eNodeB
Performance Monitoring Reference 13 Scheduled Cell-Level UE Information Monitoring

Range
Total DLSCH Number 0 to 65535 Total number of UEs
Frequency Selected for frequency
Users Within Monitor selective scheduling
Period in the downlink
within a monitoring
period.
Total DLSCH Number 0 to 65535 Total number of UEs

Diversity Users Within for diversity
Monitor Period scheduling in the
downlink within a
monitoring period.
Total ULSCH Users Number 0 to 65535 Total number of UEs
Within Monitor Period scheduled in the
uplink within a
monitoring period.

eNodeB
Performance Monitoring Reference 14 HARQ Status Monitoring
14 HARQ Status Monitoring
This task is used to monitor uplink and downlink hybrid automatic repeat request (HARQ)
information about all UEs in a cell. Based on this information, data transmission status of the
eNodeB or UE can be determined.
14.1 Parameters for HARQ Status Monitoring

Table 14-1 Parameters for HARQ status monitoring
Monitor Item It can be set to DL HARQ State, UL HARQ State, or a combination
of these two items.
Local Cell ID ID of the cell on which HARQ status monitoring is performed.
Monitor Period Period for reporting monitoring results. It can be set to 1000 or 2000.
(ms)
14.2 Results of HARQ Status Monitoring

Table 14-2 Results of HARQ status monitoring

Item Range
DL HARQ DL PDSCH Code Num 0 to 64,000 Number of ACKs for downlink
State m ACK Num ber codeword m (m = {0, 1})
within a monitoring period.
DL PDSCH Code Num 0 to 64,000 Number of NACKs for

m NACK Num ber downlink codeword m (m = {0,
1}) within a monitoring period.

eNodeB
Performance Monitoring Reference 14 HARQ Status Monitoring

Item Range
DL PDSCH Code Num 0 to 64,000 Number of times no feedback
m NoRsp Num ber for downlink codeword m (m =
{0, 1}) is decoded within a
monitoring period.
DL PDSCH Code Num 0 to 64,000 Number of times no UE feeds
m DTX Num ber back downlink codeword m (m
= {0, 1}) within a monitoring
period.
DL PDSCH Num 0 to 64,000 Number of times the downlink
Version m Num ber HARQ version is m (m = {0, 1,
2, 3}) within a monitoring
period.
DL PDSCH Rsp for Num 0 to 64,000 Number of times downlink
n TTI Num ber HARQ RRT equals to n (n =
{8, 9, 10, 11}) TTIs within a
monitoring period. If the n is
larger than 11, n is treated as
11.
UL HARQ UL PUSCH ACK Num 0 to 64,000 Number of uplink ACKs within
State Num ber a monitoring period.
UL PUSCH NACK Num 0 to 64,000 Number of uplink NACKs
Num ber within a monitoring period.
UL PUSCH DTX Num 0 to 64,000 Number of uplink DTXs within
Num ber a monitoring period.
UL PUSCH Num 0 to 64,000 Number of times the uplink

Version m Num ber HARQ version is m (m = {0, 1,
2, 3}) within a monitoring
period.

eNodeB
Performance Monitoring Reference 15 Air-Interface DCI Status Monitoring
15 Air-Interface DCI Status Monitoring
This task is used to monitor the usage of a cell-level physical downlink control channel
(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.
15.1 Parameters for Air-Interface DCI Status Monitoring

Table 15-1 Parameters for air-interface DCI status monitoring
Monitor Item It can be set to DCI STATISTIC.
Local Cell ID ID of the cell on which air-interface DCI status monitoring is

performed.
(ms)

eNodeB
15.2 Results of Air-Interface DCI Status Monitoring

Table 15-2 Results of air-interface DCI status monitoring

Item Range
DCI PDCCH Type DCI0 Num 0 to Total number of times the
Statistic Num ber 64,000 PDCCH type is DCI format 0
PDCCH Type DCI1 Num 0 to Total number of times the
Num ber 64,000 PDCCH type is DCI format 1
PDCCH Type Num 0 to Total number of times the
DCI1A Num ber 64,000 PDCCH type is DCI format 1A

DCI1B Num ber 64,000 PDCCH type is DCI format 1B

DCI1C Num ber 64,000 PDCCH type is DCI format 1C
DCI1D Num ber 64,000 PDCCH type is DCI format 1D


DCI2B Num ber 64,000 PDCCH type is DCI format 2B

PDCCH Use m CCE Num 0 to Total number of times the CCE
Num ber 64,000 aggregation level is m (m = {1,
2, 4, 8}) within a monitoring
period.

eNodeB

Item Range
CFI Engross n Num 0 to Total number of times the CFI
Symbol Stat. Num ber 64,000 occupies n (n = {1, 2, 3, 4})
symbols within a monitoring
period.

eNodeB
Performance Monitoring Reference 16 Air-Interface DRB Statistics Monitoring
16 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.
16.1 Parameters for Air-Interface DRB Statistics

Monitoring
Table 16-1 Parameters for air-interface DRB statistics monitoring
Monitor Item It can be set to DL DRB STATISTIC, UL DRB STATISTIC, or a
combination of these two items.
Local Cell ID ID of the cell on which air-interface DRB statistics monitoring is
performed.
(ms)
16.2 Results of Air-Interface DRB Statistics Monitoring

Table 16-2 Results of air-interface DRB statistics monitoring

Item Range
DL DRB Number of packets Numbe 0 to Total number of data packets

STATISTI received at the DL r 300,000,0 received at the downlink PDCP
C PDCP 00 layer within a monitoring period.

eNodeB
Performance Monitoring Reference 16 Air-Interface DRB Statistics Monitoring

Item Range
Number of bits Bit 0 to Total throughput for data packets
received at the DL 300,000,0 received at the downlink PDCP
PDCP 00 layer within a monitoring period.
Number of TBs Numbe 0 to Total number of TBs for
for DL MAC r 300,000,0 downlink MAC scheduling within
scheduling 00 a monitoring period.
Number of bits for Bit 0 to Total throughput for TBs
DL MAC 300,000,0 scheduled at the downlink MAC
scheduling 00 layer within a monitoring period.
Number of times Numbe 0 to Total number of times the

DL RLC sends r 300,000,0 downlink RLC layer transmits
data in AM mode 00 data in acknowledgment (AM)
mode within a monitoring period.
Number of times Numbe 0 to Total number of times the

DL RLC sends r 300,000,0 downlink RLC layer transmits
data in UM mode 00 data in unacknowledgment (UM)
mode within a monitoring period.
UL DRB Number of TBs Numbe 0 to Total number of TBs for uplink

STATISTI for UL MAC r 300,000,0 MAC scheduling within a
C scheduling 00 monitoring period.
UL Mac TB Bit 0 to Total throughput for TBs

Number 300,000,0 scheduled at the uplink MAC
00 layer within a monitoring period.
Number of correct Numbe 0 to Total number of times the uplink
UL MAC CRCs r 300,000,0 MAC layer receives correct cyclic
00 redundancy checks (CRCs) from a
UE within a monitoring period.
Number of Numbe 0 to Total number of times the uplink
incorrect UL r 300,000,0 MAC layer receives incorrect
MAC CRCs 00 CRCs from a UE within a
monitoring period.
Number of times Numbe 0 to Total number of times the uplink
UL RLC receives r 300,000,0 RLC layer receives data in AM
data in AM mode 00 mode within a monitoring period.
Number of times Numbe 0 to Total number of times the uplink
UL RLC receives r 300,000,0 RLC layer receives data in UM
data in UM mode 00 mode within a monitoring period.
Number of packets Numbe 0 to Total number of data packets
transmitted at the r 300,000,0 transmitted at the uplink PDCP
UL PDCP 00 layer within a monitoring period.
Number of bits Bit 0 to Total throughput for data packets
transmitted at the 300,000,0 transmitted at the uplink PDCP
UL PDCP 00 layer within a monitoring period.

eNodeB
Performance Monitoring Reference 17 BLER Monitoring
17 BLER Monitoring
This task is used to monitor the convergence of block error rates (BLERs) on each channel.
17.1 Parameters for BLER Monitoring

Table 17-1 Parameters for BLER monitoring
Monitor Item It can be set to Init BLER, Resident BLER, PDCCH BLER, or a
UEID-MME MME of a user.

UEID-TMSI/Trac TMSI or TraceRef to be monitored.
eRef
(ms) 500, 1000, or 2000.
17.2 Results of BLER Monitoring

Table 17-2 Results of BLER monitoring

Item Range
- Physical Cell N/A N/A Physical cell identifier of the
Identifier serving cell.

eNodeB

Item Range
Init BLER Downlink IBLER ‰ 0 to 1,000 BLER of initial TB
transmission on a PDSCH
within a monitoring period =
Total number of TBs that fail to
be initially transmitted on the
PDSCH within the monitoring
period x 1000/Total number of
initially transmitted TBs on the
period.
Uplink IBLER ‰ 0 to 1,000 BLER of initial TB

transmission on a PUSCH
Total number of TBs that fail to
be initially transmitted on the
PUSCH within the monitoring
period.
Resident Downlink RBLER ‰ 0 to 1,000 BLER of the last TB
BLER retransmission on a PDSCH
Number of times TBs last fail
to be retransmitted on the
period.
Uplink RBLER ‰ 0 to 1,000 BLER of the last TB
retransmission on a PUSCH
Number of times TBs last fail
to be retransmitted on the
period.

eNodeB

Item Range
PDCCH PDCCH Bler ‰ 0 to 1,000 BLER of DLGRANT decoding
BLER on a PDCCH within a
monitoring period = Number of
times DLGRANTs decoded
incorrectly x 1000/Total
number of DLGRANTs sent on
a PDCCH. The error rate is in
the unit of ‰.
The number of DLGRANTs
decoded incorrectly is the
number of DTXs that were the
feedback given to the
DLGRANTs sent on a
PDCCH.

eNodeB
Performance Monitoring Reference 18 Power Headroom Monitoring
18 Power Headroom Monitoring
This task is used to monitor the power headroom reported by the UE. Based on this
information, the scheduling module estimates the remaining processing capacity of the UE.
18.1 Parameters for Power Headroom Monitoring

Table 18-1 Parameters for power headroom monitoring
UEID-TMSI/TraceRef TMSI or TraceRef to be monitored.

200, 500, 1000, or 2000.
18.2 Result of Power Headroom Monitoring

Table 18-2 Result of power headroom monitoring

Range
- Physical Cell N/A N/A Physical cell identifier of
Identifier the serving cell.
Power Power Headroom dB –23 to 40 Power headroom last
Headroom reported by the UE.

eNodeB
Performance Monitoring Reference 19 Channel Quality Monitoring
19 Channel Quality Monitoring
This task is used to monitor the uplink and downlink channel status of the UE in real time,
which is affected by the inference and varies depending on the position of the UE in a cell.
Based on the channel status information, the uplink and downlink channel quality of the UE
can be determined.
19.1 Parameters for Channel Quality Monitoring

Table 19-1 Parameters for channel quality monitoring
Monitor Item It can be set to SINR, CQI, or a combination of these two items.

eRef
(ms) 500, 1000, or 2000.
19.2 Results of Channel Quality Monitoring

Table 19-2 Results of channel quality monitoring
Monitor Parameter Unit Value Range Description

Item

eNodeB
Performance Monitoring Reference 19 Channel Quality Monitoring

Item
SINR SINR 0.01 –12700 to Average signal to interference
dB 12700 plus noise ratio (SINR) for the
full bandwidth of the UE
measured when the monitoring
result is reported.
SINR Flag N/A N/A Flag of the effective average

SINR for the full bandwidth of
the UE.
CQI UE Code Count Num 1 to 2 Number of transmitted
ber codewords in the downlink
when the monitoring result is
reported.
Effective Len ms 41 to 44 Valid length of the channel
quality indicator (CQI) for the
full bandwidth.
CQI N/A 0 to 31 Value mapped to the originally
reported CQI for the full
bandwidth when the

eNodeB
Performance Monitoring Reference 20 Scheduling Monitoring
20 Scheduling Monitoring
This task is used to monitor the number of scheduling requests sent from the UE and status of
each data buffer area for uplink services.
20.1 Parameters for Scheduling Monitoring

Table 20-1 Parameters for scheduling monitoring
Monitor Item 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.
UEID-TMSI/Tra TMSI or TraceRef to be monitored.
ceRef
(ms) 500, 1000, or 2000.
20.2 Results of Scheduling Monitoring

Table 20-2 Results of scheduling monitoring

Item
UL SR of Number of SRs Num 0 to 4294967296 Number of scheduling
Service ber requests (SRs) reported by the
UE to the eNodeB within a
monitoring period.

eNodeB

Item
UL BSR Byte Length 1 of bit 0 to 150,000 Data volume in the buffer
of Service LCG BS status report [0] (BSR[0])
when the monitoring result is
reported.
If the CRC is successful, the
BSR of the corresponding
Logical Channel Group
(LCG) must be updated.
When the UE is in the
out-of-synchronization state,
the BSR of all LCGs must be
cleared.
Byte Length 2 of bit 0 to 150,000 Data volume in the BSR[1]
LCG BS when the monitoring result is
reported
LCG must be updated. When
the UE is in the
cleared.

reported.
the UE is in the
cleared.
reported.
the UE is in the
cleared.
percentag GAP Time Num 0 to 4294967296 Number of accumulated TTIs
e of DRX ber in the call gapping (GAP)
activity state between the start and the
timer in end of the scheduling
DRX monitoring.

eNodeB

Item
timer DRX Time Num 0 to 4294967296 Number of accumulated TTIs
ber in the DRX state between the
start and the end of the
scheduling monitoring.
Number of TTI Num 0 to 4294967296 Number of accumulated TTIs
ber between the establishment
and the release of an L2 case.

eNodeB
Performance Monitoring Reference 21 RLC Data Stream Monitoring
21 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 corresponding to the DRBs for user data.
21.1 Parameters for RLC Data Stream Monitoring

Table 21-1 Parameters for RLC data stream monitoring
Monitor Item It can be set to RLC Data Stream.

200, 500, 1000, or 2000.
21.2 Result of RLC Data Stream Monitoring

Table 21-2 Result of RLC data stream monitoring

Item Range
RLC Data RLC Buffer Byte 0 to Data stream of the RLC SDUs to
Stream Length 10,000,00 be sent on the DRB from the
0 downlink buffer area at the RLC
layer when the monitoring result is
reported.

eNodeB
Performance Monitoring Reference 22 Throughput Monitoring
22 Throughput Monitoring
This task is used to view the throughputs at the MAC or RLC layer at the eNodeB side in real
time. Based on the comparison of the throughputs between the eNodeB side and the UE side,
whether the data transmission at the eNodeB side is proper can be determined.
22.1 Parameters for Throughput Monitoring

Table 22-1 Parameters for throughput monitoring
Monitor Item It can be set to Throughput of RLC, Throughput of MAC, or
a combination of these two items.

200, 500, 1000, or 2000.
22.2 Results of Throughput Monitoring

Table 22-2 Results of throughput monitoring

Item

eNodeB
Performance Monitoring Reference 22 Throughput Monitoring

Item
Throughput Downlink RLC bit/s 0 to Total throughputs of the
of RLC Throughput 150,000,000 downlink RLC SDUs sent on
the DRB at the RLC layer
(Downlink RLC throughputs
on the RLC logical channels
x 8)/(Monitoring period x
1000).
Uplink RLC bit/s 0 to Total throughputs of the
Throughput 150,000,000 uplink RLC SDUs received
on the DRB at the RLC layer
(Uplink RLC throughputs on
the RLC logical channels x
8)/(Monitoring period x
1000).
Throughput Downlink MAC bit/s 0 to User-level downlink MAC
of MAC Throughput 150,000,000 throughputs within a
monitoring period =
(Downlink MAC
throughputs x
1000).
Uplink MAC bit/s 0 to User-level uplink MAC
Throughput 150,000,000 throughputs within a
monitoring period = (Uplink
MAC throughputs x
1000).

eNodeB
Performance Monitoring Reference 23 AQM Monitoring
23 AQM Monitoring
This task is used to monitor the packet loss rate and buffer queues related to the active queue
management (AQM) algorithms for DRBs.
23.1 Parameters for AQM Monitoring

Table 23-1 Parameters for AQM monitoring
Monitor Item It can be set to Percentage of AQM discard package, DL RLC
buffer length of eNB, or a combination of these two items.
eRef
(ms) 500, 1000, or 2000.
23.2 Results of AQM Monitoring

Table 23-2 Results of AQM monitoring

Item Range
Percentag Number of Packet 0 to 20,000 Number of discarded packets on
e of AQM Discarded the DRB monitored in AQM mode
discard Packets within a monitoring period.
package

eNodeB
Performance Monitoring Reference 23 AQM Monitoring

Item Range
DL RLC Number of Packet 0 to 20,000 Number of RLC SDUs to be sent
buffer Packets in on the DRB from the downlink
length of RLC Buffer RLC buffer area at the end of a
eNB monitoring period.

eNodeB
Performance Monitoring Reference 24 Uplink Power Control Monitoring
24 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 turned off. This enables users to obtain the
information about the power adjustment when the switch for uplink power control is turned
on or turned off.
24.1 Parameters for Uplink Power Control Monitoring

Table 24-1 Parameters for uplink power control monitoring
Monitor Item It can be set to Close-loop Power of UE, PUSCH N max updated of
UE, PUCCH ACK/NACK/DTX Statistic, or a combination of these
items.

UEID-TMSI/Tra TMSI or TraceRef to be monitored.
ceRef
(ms) 500, 1000, or 2000.
24.2 Results of Uplink Power Control Monitoring

Table 24-2 Results of uplink power control monitoring

Range
- Physical Cell N/A N/A Physical cell

Identifier identifier of the
serving cell.

eNodeB

Range
Close-loop PUSCH SINR target dB –1500 to Target SINR of
Power of UE 2000 PUSCH power
control. The value
is set by running
MML commands.
PUSCH SINR Adjust dB –1500 to The difference

Step 2000 between the actual
SINR and target
SINR when the
closed-loop power
control is adjusted
when the
reported.
PUSCH IBLER target ‰ –1500 to Target IBLER of

2000 PUSCH
closed-loop power
control. The value
is set by running
MML commands.
PUCCH SINR target dB –1500 to Target SINR of
2000 PUCCH
closed-loop power
control. The value
is set by running
MML commands.
PUCCH SINR Adjust dB –1500 to The difference

Step 2000 between the actual
SINR and the target
SINR of PUCCH
closed-loop power
control when the
reported.
PUSCH N max Maximum Number of Number 0 to 10 The maximum

updated of UE Transmissions number of
transmissions on
the uplink PUSCH.
It is set by running
MML commands.
PUCCH Number of ACK Number 0 to 2000 The number of
ACK/NACK/DT ACKs detected on
X Statistic the PUCCH by the
eNodeB within a
monitoring period.

eNodeB

Range
Number of NACK Number 0 to 2000 The number of
NACKs on the
PUCCH detected
by the eNodeB
within a monitoring
period.
Number of DTX Number 0 to 2000 The number of

DTXs on the
PUCCH detected
by the eNodeB
within a monitoring
period.
NOTE
If the three items are selected for simultaneous monitoring, the value ranges of the parameters are all
from –600 to 2000.

eNodeB
Performance Monitoring Reference 25 Downlink Power Control Monitoring
25 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 turned off. This enables users to obtain
the power adjustment when the switch for downlink power control is turned on or turned off.
25.1 Parameters for Downlink Power Control Monitoring

Table 25-1 Parameters for downlink power control monitoring
Monitor Item It can be set to PDSCH of UE, PHICH of UE, PDCCH of UE, or a

eRef
(ms) 500, 1000, or 2000.
25.2 Results of Downlink Power Control Monitoring

Table 25-2 Results of downlink power control monitoring

Range
- Physical Cell N/A N/A Physical cell
Identifier identifier of the
serving cell.

eNodeB

Range
PDSCH of UE PDSCH PA dB –6 to 3 Power offset between
each resource
element (RE) on the
PDSCH and the pilot
when the monitoring
result is reported.
Maximum number of Num 0 to 28 The maximum

transmissions ber number of
transmissions on the
PDSCH, excluding
the initial
transmission. It is set
by running MML
commands.
PDSCH IBLER target ‰ –600 to Target BLER in the

1000 initial transmission
during the semi-static
PDSCH power
control. It is set by
running MML
commands.
PHICH of UE PHICH SINR target dB –1500 to Target SINR of
2000 PHICH outer-loop
power control. The
value is set by
running MML
commands.
PHICH SINR adjust dB –1500 to The SINR adjustment

step 2000 step calculated in the
PHICH outer-loop
power control =
Adjustment step x
Number of NACKs
transmitted on the
PHICH within the
period of outer-loop
power control
(Actually measured
BLER – Target
BLER)/(1 – Target
BLER).
The result is
multiplied by 1000.

eNodeB

Range
PHICH BER ‰ –1500 to The probability for
2000 decoding NACKs
into ACKs within the
adjustment period of
the PHICH
outer-loop power
control = Number of
NACKs that are
decoded into ACKs x
1000/Number of
NACKs transmitted
on the PHICH.
PDCCH of UE Power Offset of dB –1500 to Offset between the
Pdcch 2000 power for
transmitting each RE
on the PDCCH and
the pilot power when
the monitoring result
is reported.
TTI ms –1500 to TTI for the PDCCH

2000 power transmitted at
the MAC layer.
NOTE
If the three items are selected for simultaneous monitoring, the value ranges of the parameters are all
from –600 to 2000.

eNodeB
Performance Monitoring Reference 26 Uplink ICIC Monitoring
26 Uplink ICIC Monitoring
This task is used to monitor the user property and neighbor cell information during the uplink
ICIC to obtain the operating status of the uplink ICIC.
26.1 Parameters for Uplink ICIC Monitoring

Table 26-1 Parameters for uplink ICIC monitoring
Monitor Item It can be set to USER PROPERTY or USER NEIGHBOR
LIST. You can also select both monitoring items for
simultaneous monitoring.

Monitor Period (ms) Period for reporting monitoring results. It can be set to 50,
100, 200, 500, 1000, or 2000.
26.2 Results of Uplink ICIC Monitoring

Table 26-2 Results of uplink ICIC monitoring

Range
- Physical Cell N/A N/A Physical cell identifier of
Identifier the serving cell.
USER User Type N/A N/A User property. It includes

PROPERTY the CEUs, cell center
users, and users for
full-frequency scheduling.

eNodeB
Performance Monitoring Reference 26 Uplink ICIC Monitoring

Range
USER Strongest Neighbor N/A N/A Physical ID of the
NEIGHBOR Cell detected neighbor cell
LIST with the best signal quality
among the cells in the user
neighbor list.
Sub-Strongest N/A N/A Physical ID of the

Neighbor Cell detected neighbor cell
with the second best signal
quality among the cells in
the user neighbor list.

eNodeB
Performance Monitoring Reference 27 MCS Statistics Monitoring
27 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 step 0 to step 28. 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.
27.1 Parameters for MCS Statistics Monitoring

Table 27-1 Parameters for MCS statistics monitoring
Monitor Item It can be set to DL MCS or UL MCS. You can also select both
monitoring items for simultaneous monitoring.
Monitor Period (ms) Period for reporting monitoring results. It can be set to 1000 or
2000.
27.2 Results of MCS Statistics Monitoring

Table 27-2 Results of MCS statistics monitoring

Item Range


eNodeB
Performance Monitoring Reference 27 MCS Statistics Monitoring

Item Range
DL MCS DLSCH Code0 Number 0 to 2000 Total number of scheduling
Num on codeword 0 in the
downlink scheduling within a
monitoring period.
DLSCH Code0 Number 0 to Total number of RBs on
RBs 200,000 codeword 0 in the downlink
scheduling within a
monitoring period.
DLSCH Code1 Number 0 to 2000 Total number of scheduling
Num on codeword 1 in the
downlink scheduling within a
monitoring period.
DLSCH Code1 Number 0 to Total number of RBs on
RBs 200,000 codeword 1 in the downlink
scheduling within a
monitoring period.
UL MCS ULSCH Num Number 0 to 2000 The number of uplink

scheduling within a
monitoring period.
ULSCH RBs Number 0 to Total number of RBs in the

200,000 uplink scheduling within a
monitoring period.

eNodeB
Performance Monitoring Reference 28 IP Performance Monitoring
28 IP Performance Monitoring
This task is used to monitor the transmission and reception of data at the IP layer of the
eNodeB in real time.
28.1 Parameters for IP Performance Monitoring

Table 28-1 Parameters for IP performance monitoring
Cabinet No. Number of the cabinet where the board for IP performance monitoring
is located.
Subrack No. Number of the subrack where the board for IP performance monitoring
is located.
Slot No. Number of the slot where the board for IP performance monitoring is
located.
Monitor Period Period for reporting monitoring results. It is set to 1 by default.
(Second)
28.2 Results of IP Performance Monitoring

Table 28-2 Results of IP performance monitoring

Item Range
IP Rx Packets Numbe 0 to Total number of packets received
Performance r 4,294,967,2 at the IP layer by the board within
95 a monitoring period.

eNodeB
Performance Monitoring Reference 28 IP Performance Monitoring

Item Range
Tx Packets Numbe 0 to Total number of packets at the IP
r 4,294,967,2 layer transmitted by the board
95 within a monitoring period.
Rx Loss Numbe 0 to Total number of packets discarded
Packets r 4,294,967,2 at the IP layer by the board within
95 a monitoring period.

eNodeB
Performance Monitoring Reference 29 IP Path Performance Monitoring
29 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.
29.1 Parameters for IP Path Performance Monitoring

Table 29-1 Parameters for IP path performance monitoring
IP PATH No. Number of the IP path.
Monitor Period It is set to 1 by default.

(Second)
29.2 Results of IP Path Performance Monitoring

Table 29-2 Results of IP path performance monitoring

Item Range
IP Path Lost Packets ‰ 0 to 1000 The packet loss rate within a
Performan Ratio monitoring period = (Number of
ce packets transmitted by the eNodeB
– Number of packets received by
the peer end) x 1000/Number of
packets transmitted by the eNodeB.
Transmit Rate kbit/s 0 to The number of k/bits on the IP path
100,000 transmitted by the eNodeB per
second within a monitoring period.

eNodeB
Performance Monitoring Reference 29 IP Path Performance Monitoring

Item Range
Average Delay ms 0 to 100 The average delay on the IP path
within the monitoring period =
(Sum of delays for transmitting the
IP PM data bound to the IP path
from the eNodeB to the EPC + Sum
of delays for transmitting data the
IP PM data bound to the IP path
from the eNodeB to the
EPC)/Number of all
quadruplet-based and triplet-based
IP PM packets bound to the IP path.
One IP path can only be bound to
one triplet-based IP PM, but can be
bound to multiple quadruplet-based
IP PMs.
Average Jitter ms 0 to 100 The average jitter on the IP path
within the monitoring period = Sum
of jitter occurrences of all the IP
PM packets bound to the IP path
from the eNodeB to the
EPC/Number of IP PM packets
bound to the IP path from the
eNodeB to the EPC.
The jitter of each IP PM packet =
Delay of data transmission from the
IP PM to the EPC – Average delay
of data transmission from the IP
PM to the EPC.

eNodeB
Performance Monitoring Reference 30 SCTP Performance Monitoring
30 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.
30.1 Parameters for SCTP Performance Monitoring

Table 30-1 Parameters for SCTP performance monitoring
Cabinet No. Number of the cabinet where the board for SCTP performance
Subrack No. Number of the subrack where the board for SCTP performance
Slot No. Number of the slot where the board for SCTP performance monitoring
is located.
Monitor Period Period for reporting monitoring results. It is set to 1 by default.

(Second)
30.2 Results of SCTP Performance Monitoring

Table 30-2 Results of SCTP performance monitoring

Item Range
SCTP Link Receive Total Numbe 0 to The number of packets received on
Performanc Packets r 4,294,967, the SCTP link within a monitoring
e 295 period.

eNodeB
Performance Monitoring Reference 30 SCTP Performance Monitoring

Item Range
Send Total Numbe 0 to The number of packets transmitted
Packets r 4,294,967, on the SCTP link within a
295 monitoring period.
Receive Total Numbe 0 to The number of packets discarded
Drop Packets r 4,294,967, on the SCTP link within a
295 monitoring period.
Retrans Ratio % 0 to 100 Formula: Retransmission ratio =
Number of data blocks
retransmitted on the SCTP link
within the monitoring period x
100/Number of data blocks
transmitted on the SCTP link.

eNodeB
Performance Monitoring Reference 31 PPPoE Performance Test
31 PPPoE Performance Test
This task is used to test PPPoE online performance. PPPoE online performance test 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.
31.1 Parameters for a PPPoE Performance Test

Table 31-1 Parameters for a PPPoE performance test
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.
PPPoE Link No. Number of the PPPoE link to be tested.
Before starting a PPPoE performance test, query the corresponding PPPoE link
number.
Autosave to File After you select the Autosave to File check box, monitoring results are
automatically saved in the default path. You can customize the folder
and file name.

eNodeB
31.2 Results of the PPPoE Performance Test

Table 31-2 Results of the PPPoE performance test

Range
PPPoE Receive Packets Num 0 to Number of packets
Performance Test ber 4294967295 received by the
receiving end of a
PPPoE link within a
monitoring period.
Send Packets Num 0 to Number of packets
ber 4294967295 transmitted by the
transmitting end of a
PPPoE link within a
monitoring period.
Receive Rate bit/s 0 to Number of bits received
300000000 per second by the
receiving end of a
PPPoE link within a
monitoring period.
Send Rate bit/s 0 to Number of bits
300000000 transmitted per second
by the transmitting end
of a PPPoE link within
a monitoring period.
Receive Drop Num 0 to Number of packets
Packets ber 4294967295 discarded by the
receiving end of a
PPPoE link within a
monitoring period.
Send Drop Packets Num 0 to Number of packets
ber 4294967295 discarded by the
PPPoE link within a
monitoring period.
Receive Drop % 0 to 100 Statistics on the packet
Packets Ratio loss rate of the
receiving end of a
PPPoE link within a
monitoring period.
Packet loss rate
indicates whether the
packets on a link are
effectively transmitted.

eNodeB

Range
Send Drop Packets % 0 to 100 Statistics on the packet
Ratio loss rate of the
PPPoE link within a
monitoring period.
Packet loss rate
indicates whether the
packets on a link are
effectively transmitted.

eNodeB
Performance Monitoring Reference 32 Local and Forwarded Traffic Monitoring
32 Local and Forwarded Traffic

Monitoring
This task is used to monitor the local traffic and forwarded throughput in real time. Forwarded
traffic is common when eNodeBs are cascaded.
32.1 Parameters for Local and Forwarded Traffic

Monitoring
Table 32-1 Parameters for local and forwarded traffic monitoring
Monitor Period It is set to 1 by default.
(Second)
32.2 Results of Local and Forwarded Traffic Monitoring

Table 32-2 Results of local and forwarded traffic monitoring

Item
Local and Local byte/s 0 to The number of bytes received
forwarded Receive 4,294,967,295 by the eNodeB per second
Traffic Traffic within the monitoring period
and that are destined for the
local eNodeB.
Local Send byte/s 0 to The number of bytes transmitted
Traffic 4,294,967,295 by the eNodeB within the
monitoring period, excluding the
forwarded traffic.

eNodeB
Performance Monitoring Reference 32 Local and Forwarded Traffic Monitoring

Item
eNodeB byte/s 0 to The number of bytes forwarded
Bypass 4,294,967,295 by the eNodeB per second
Traffic within the monitoring period.

eNodeB
Performance Monitoring Reference 33 Logical Port Monitoring
33 Logical Port Monitoring
This task is used to monitor the realtime 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.
33.1 Parameters for Logical Port Monitoring

Table 33-1 Parameters for logical port monitoring
Cabinet No. Number of the cabinet where the board for logical port monitoring
is located.
Subrack No. Number of the subrack where the board for logical port monitoring
is located.
Slot No. Number of the slot where the board for logical port monitoring is
located.
Subboard Type Type of the subboard for logical port monitoring.
Physical Port Type Type of the physical port for logical port monitoring.
Physical Port No. Number of the physical port for logical port monitoring.
Transmission Resource Number of the transport resource group for logical port
Group No. monitoring.
Rate Config Type Rate mode for logical port monitoring. It can be single-rate mode
or double-rate mode.
Monitor Period (ms) Period for reporting monitoring results. It can be set to 1.

eNodeB
33.2 Results of Logical Port Monitoring

33.2.1 Single-Rate Mode
Table 33-2 Results of logical port monitoring in single-rate mode

Item Range
Logic Port Admission kbit/s 0 to Admission bandwidth for
Monitorin Bandwidth(Tx) 360,000 data transmission on the
g current logical port in
single-rate mode.
Admission kbit/s 0 to Admission bandwidth for
Bandwidth(Rx) 540,000 data reception on the current
logical port in single-rate
mode.
GBR Load(Tx) kbit/s 0 to Transport load for GBR
360,000 service data transmission on
the current logical port in
single-rate mode.
GBR Load(Rx) kbit/s 0 to Transport load for GBR
540,000 service data reception on the
current logical port in
single-rate mode.
GBR Load Ratio(Tx) % 0 to 100 Transport load ratio of GBR
service data transmission on
single-rate mode.
Transport load ratio of GBR
services = Transport load for
GBR services on the
port/Admission bandwidth
of the port.
GBR Load Ratio(Rx) % 0 to 100 Transport load ratio of GBR
service data reception on the
single-rate mode.
GBR services on the
of the port.
Logical Port Load(Tx) kbit/s 0 to Transport load for data
360,000 transmission on the current
mode.
Logical Port kbit/s 0 to Transport load for data

eNodeB

Item Range
Load(Rx) 540,000 reception on the current
mode.
Logical Port Load % 0 to 100 Transport load ratio of data
Ratio(Tx) transmission on the current
mode.
Transport load ratio of the
logical port = Transport load
on the logical
of the port.
Logical Port Load % 0 to 100 Transport load ratio of data

Ratio(Rx) reception on the current
mode.
Transport load ratio of the
logical port = Transport load
on the logical
of the port.
33.2.2 Double-Rate Mode

Table 33-3 Results of logical port monitoring in double-rate mode

Item Range
Logic Port CIR Admission kbit/s 0 to Committed information rate
Monitorin Bandwidth(Tx) 360,000 (CIR) admission bandwidth
g for data transmission on the
double-rate mode.
CIR Admission kbit/s 0 to CIR admission bandwidth
Bandwidth(Rx) 540,000 for data reception on the
double-rate mode.
PIR Admission kbit/s 0 to Peak information rate (PIR)

Bandwidth(Tx) 360,000 admission bandwidth for
data transmission on the
double-rate mode.
PIR Admission kbit/s 0 to PIR admission bandwidth
Bandwidth(Rx) 540,000 for data reception on the

eNodeB

Item Range
double-rate mode.
GBR Load(Tx) kbit/s 0 to Transport load for GBR

360,000 service data transmission on
double-rate mode.
GBR Load(Rx) kbit/s 0 to Transport load for GBR

540,000 service data reception on the
double-rate mode.
Real Time Traffic kbit/s 0 to Transport load for

Load(Tx) 360,000 non-flow-controllable
double-rate mode.
Real Time Traffic kbit/s 0 to Transport load for
Load(Rx) 540,000 non-flow-controllable
double-rate mode.
GBR Load Ratio(Tx) % 0 to 100 Transport load ratio of GBR
double-rate mode.
GBR services on the
port/Available PIR
bandwidth of the port.
GBR Load Ratio(Rx) % 0 to 100 Transport load ratio of GBR
double-rate mode.
GBR services on the
port/Available PIR
bandwidth of the port.
CIR Load Ratio(Tx) % 0 to 100 CIR bandwidth load ratio of

double-rate mode.
CIR bandwidth load ratio =
Transport load for
non-flow-controllable
services on the
port/Available CIR

eNodeB

Item Range
bandwidth.
CIR Load Ratio(Rx) % 0 to 100 CIR bandwidth load ratio of

data reception on the current
logical port in double-rate
mode.
CIR bandwidth load ratio =
Transport load for
non-flow-controllable
services on the
port/Available CIR
bandwidth.
Logical Port Load(Tx) kbit/s 0 to Transport load for data
360,000 transmission on the current
mode.
Logical Port kbit/s 0 to Transport load for data
Load(Rx) 540,000 reception on the current
mode.
PIR Load Ratio(Tx) % 0 to 100 PIR bandwidth load ratio of
double-rate mode.
PIR bandwidth load ratio =
Transport load on the
port/Available PIR
bandwidth.
PIR Load Ratio(Rx) % 0 to 100 PIR bandwidth load ratio of
data reception on the current
mode.
PIR bandwidth load ratio =
Transport load on the
port/Available PIR
bandwidth.

eNodeB
Performance Monitoring Reference 34 TRM Statistic Monitoring
34 TRM Statistic Monitoring
This task is used to monitor the license-controlled throughput of the operator.
34.1 Parameters for TRM Statistic Monitoring

Table 34-1 Parameters for TRM statistic monitoring
Cabinet No. Number of the cabinet where the board for TRM statistic
Subrack No. Number of the subrack where the board for TRM statistic
Slot No. Number of the slot where the board for TRM statistic monitoring is
located.
CN Operator ID ID of CN Operator. The value ranges from 0 to 3. The default
value is 0.
Monitor Period Period for reporting monitoring results. It can be set to 1.
(Second)
34.2 Results of TRM Statistic Monitoring

Table 34-2 Results of TRM statistic performance monitoring

Item Range
TRM UL License N/A N/A The uplink congestion status of
Statistic Congestion the monitored operator. 0
indicates that the congestion is
cleared and 1 indicates that
congestion is generated when the

eNodeB

Item Range
UL Trans Load kbit/s 0 to Total uplink transmission loads
429496729 of the monitored operator when
5 the monitoring result is reported.
UL Total Traffic kbit/s 0 to Total uplink transmission loads
429496729 of the monitored operator when
5 the monitoring result is reported.
UL Cir Virtual bit -214748364 The virtual buffer capacity for
Buffer 8 to uplink committed information
214748364 rate (CIRs) of the monitored
7 operator when the monitoring
result is reported.
UL Pir Virtual bit -214748364 The virtual buffer capacity for
Buffer 8 to uplink peak information rates
214748364 (PIRs) of the monitored operator
7 when the monitoring result is
reported.
UL Cong State N/A N/A The uplink congestion status of

the monitored operator. 0
indicates that the overload is
cleared and 1 indicates that an
overload is generated.
DL License N/A N/A The downlink congestion status

Congestion of the monitored operator. 0
congestion is generated.
DL Trans Load kbit/s 0 to Total downlink transmission
429496729 loads of the monitored operator
reported.
DL Total Traffic kbit/s 0 to Total downlink transmission
429496729 loads of the monitored operator
reported.
DL Cir Virtual Bit -214748364 The virtual buffer capacity for
Buffer 8 to downlink CIRs of the monitored
7 result is reported.
DL Pir Virtual Bit -214748364 The virtual buffer capacity for

Buffer 8 to downlink PIRs of the monitored
7 result is reported.

eNodeB

Item Range
DL Cong State N/A 0 or 1 The downlink congestion status
of the monitored operator. 0
congestion is generated.

eNodeB
Performance Monitoring Reference 35 UDP Injection Test Monitoring
35 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.
35.1 Parameters for UDP Injection Test Monitoring

Table 35-1 Parameters for UDP injection test monitoring
Cabinet No. Number of the cabinet where the board for UDP injection test
Subrack No. Number of the subrack where the board for UDP injection test
Slot No. Number of the slot where the board for UDP injection test
Monitor Period Period for reporting monitoring results. It can be set to 1.

(Second)
Source IP Address IP address of the eNodeB.
Source Port No. Number of UDP port on the eNodeB. The value ranges from
1024 to 65535.
Destination IP IP address of the peer end.
Address
UDestination Port No. Number of UDP port on the peer end. The value ranges from
1024 to 65535.
DSCP Differentiated services code point (DSCP) of the UDP packet.

The value ranges from 0 to 63. The default value is 63.
Speed (Kbit/s) Data rate of the data transmission. The value ranges from 28 to
150000. The default value is 150000.

eNodeB
Performance Monitoring Reference 35 UDP Injection Test Monitoring
UDP Package Length Length of the UDP packet. The value ranges from 72 to 1500.
(Byte) The default value is 1500.
TM (Minute) Duration of UDP injection test monitoring. The test stops

automatically when the duration expires. The value ranges from 1
to 60. The default value is 15.
35.2 Result of UDP Injection Test Monitoring

Table 35-2 Result of UDP injection test monitoring

Item Range
UDP Injection Drop Packets % 0 to 100 Ratio of lost packets to total
Test packets on the transmission
link within a monitoring
period.
Average Drop % 0 to 100 Average ratio of lost
Packet Ratio packets to total packets on
the transmission link within
a monitoring period.
Delay N/A 0 to 100 Delay on the transmission

link when the monitoring
result is reported.
Jitter N/A 0 to 100 Jitter on the transmission
link within a monitoring
period.
Average Delay N/A 0 to 100 Average delay on the

transmission link within the
monitoring period.


ENodeB Performance Monitoring Reference (V100R004C00 - 03) (PDF) - en

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

ENodeB Performance Monitoring Reference (V100R004C00 - 03) (PDF) - en

Diunggah oleh

Hak Cipta:

Format Tersedia

eNodeB

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2011-12-24) Huawei Proprietary and Confidential i

3 RRU/RFU Performance Monitoring.............................................................................................. 6

4 Spectrum Detection ........................................................................................................................... 8

5 QoS Satisfaction Rate Monitoring .............................................................................................. 10

6 General Throughput Monitoring ................................................................................................ 12

7 Service Statistics Monitoring ........................................................................................................ 16

8 User Statistics Monitoring ............................................................................................................. 17

9 RB Usage Monitoring ..................................................................................................................... 19

Issue 03 (2011-12-24) Huawei Proprietary and Confidential ii

10 ICIC Monitoring ............................................................................................................................ 21

11 MU-MIMO Monitoring ............................................................................................................... 24

12 Interference Detection Monitoring ........................................................................................... 25

13 Scheduled Cell-Level UE Information Monitoring .............................................................. 27

14 HARQ Status Monitoring ............................................................................................................ 29

15 Air-Interface DCI Status Monitoring ....................................................................................... 31

16 Air-Interface DRB Statistics Monitoring ................................................................................. 34

17 BLER Monitoring ........................................................................................................................... 36

18 Power Headroom Monitoring .................................................................................................... 39

19 Channel Quality Monitoring ...................................................................................................... 40

20 Scheduling Monitoring ................................................................................................................ 42

21 RLC Data Stream Monitoring..................................................................................................... 45

Issue 03 (2011-12-24) Huawei Proprietary and Confidential iii

22.1 Parameters for Throughput Monitoring........................................................................................................ 46

23 AQM Monitoring ........................................................................................................................... 48

24 Uplink Power Control Monitoring ........................................................................................... 50

25 Downlink Power Control Monitoring ..................................................................................... 53

26 Uplink ICIC Monitoring .............................................................................................................. 56

27 MCS Statistics Monitoring .......................................................................................................... 58

28 IP Performance Monitoring ........................................................................................................ 60

29 IP Path Performance Monitoring ............................................................................................... 62

30 SCTP Performance Monitoring .................................................................................................. 64

31 PPPoE Performance Test .............................................................................................................. 66

32 Local and Forwarded Traffic Monitoring ................................................................................ 69

33 Logical Port Monitoring ............................................................................................................... 71

Issue 03 (2011-12-24) Huawei Proprietary and Confidential iv

34 TRM Statistic Monitoring ........................................................................................................... 76

35 UDP Injection Test Monitoring ................................................................................................. 79

Issue 03 (2011-12-24) Huawei Proprietary and Confidential v

Product Name Product Version

DBS3900 LTE TDD V100R004C00

BTS3900A LTE V100R004C00

BTS3900L LTE V100R004C00

Issue 03 (2011-12-24) Huawei Proprietary and Confidential 1

Topic Change Description

9.2 Results of RB Usage Monitoring Added the description of the results of

Topic Change Description

Topic Change Description

Issue 03 (2011-12-24) Huawei Proprietary and Confidential 2

Topic Change Description

31 PPPoE Performance Test  Added the parameters for a Point-to-Point

Topic Change Description

Topic Change Description

Topic Change Description

Issue 03 (2011-12-24) Huawei Proprietary and Confidential 3

2 Sector Performance Monitoring

2.1 Parameters for Sector Performance Monitoring

Issue 03 (2011-12-24) Huawei Proprietary and Confidential 4

2.2 Results of Sector Performance Monitoring

Table 2-2 Results of sector performance monitoring