ENodeB Performance Monitoring Reference (07) (PDF) - en

eNodeB
Performance Monitoring
Reference
Issue
07
Date
2013-11-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2013. 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 07 (2013-11-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
eNodeB
Performance Monitoring Reference
About This Document
About This Document

Purpose
This document describes the information about eNodeB-related performance monitoring tasks,
including:
The descriptions of parameters for performance monitoring
The descriptions of monitor items
The value range of each monitor item
The formula used to calculate the value of each monitor item
Product Versions
The following table lists the product version related to this document.
Product Name
Product Version
DBS3900
V100R008C00
DBS3900 TDD
The mapping single-mode base station version is:

eNodeB: V100R006C00
BTS3900
BTS3900A
BTS3900L
BTS3900AL
BTS3202E
BTS3203E LTE
V100R006C00
NOTE
In this document, BTS3203E refers to the BTS3203E LTE.
Intended Audience
This document is intended for:
System engineers
Issue 07 (2013-11-30)

ii
eNodeB
About This Document
Site maintenance engineers
Change History
The following describes the changes in eNodeB Performance Monitoring Reference.
The document issues are as follows:
07 (2013-11-30)
06 (2013-10-30)
05 (2013-08-01)
04 (2013-07-22)
03 (2013-06-27)
02 (2013-05-30)
01 (2013-04-28)
Draft C (2013-04-10)
Draft B (2013-02-25)
Draft A (2013-02-08)
07 (2013-11-30)
This is the seventh official release.
Compared with Issue 06 (2013-10-30), this issue does not include any new information.
Compared with Issue 06 (2013-10-30), this issue includes the following new information.
Topic
Change Description
2.6.4 Monitoring Results
Updatad the descriptions of "Value Range"

and "Description" in Table 2-16 Results of
usage of RB monitoring.
2.17.3 Parameters
Updated the condition inTable 2-45

Parameters for neighboring cells.
Added the parameter "Local Cell ID" in

Table 2-46 Results of MLB monitoring.
Added the descriptions of " UL CoMP User

Indication."
Added note of the Description in parameters

of "NeighborCell RSRP[n]" and
"NeighborCell RSRQ[n]."

and "Description" in CA Property.
Issue 07 (2013-11-30)

iii
eNodeB
About This Document
Topic
Change Description
Updatad the descriptions of "Value

Range" and "Description" in CA
Property.
Modified the Value Range of RLC

Buffer Length.

3.11.3 Parameters
Added the parameter of Test Item.


3.14.3 Parameters
5.3.3 Parameters
Updatad the Table 5-5Parameters for

transport port flux stat monitoring.
5.9.3 Parameters
Updatad the descriptions of IPPM Flag.

Added the parameter of Destination IP
address.
Updatad the Value Range of Test Type.
Compared with Issue 06 (2013-10-30), this issue deleted the following new information:
Deleted the Results of PVC monitoring in 5.4.4 Monitoring Results.
06 (2013-10-30)
This is the sixth official release.
Topic
Change Description
1.3.3 General Parameter Input Description
Add the descriptions of General Parameter.
1.3 Precautions
Add the descriptions of the Note.
Updated the "Result of RLC data stream

monitoring."
Issue 07 (2013-11-30)

iv
eNodeB
About This Document
Topic
Change Description
Updated the "Results of RLC throughput

monitoring."
Updated the "Results of user downlink

property monitoring."
Compared with Issue 05 (2013-08-01), this issue does not include any changes.
No information in Issue 05 (2013-08-01) is deleted from this issu.
05 (2013-08-01)
This is the fifth official release.
Compared with Issue 04 (2013-07-22), this issue includes the following changes.
Topic
Change Description
5.3 Transport Port Flux Stat Monitoring
Modified descriptions of Usage Scenario.
No information in Issue 04 (2013-07-22) is deleted from this issu
04 (2013-07-22)
This is the fourth official release.
Topic
Change Description
Whole document
Added descriptions of BTS3203Es.
Topic
Change Description
3 User Performance Monitoring
Modified the value range of Physical Cell

Identifier.
2.14 HARQ Statistic Monitoring
Modified the description of the Code[m]

DTX Num.
Issue 07 (2013-11-30)

eNodeB
About This Document
Topic
Change Description
0
UL SRS RSRP
Modified the description of the Byte Length

of LCG BS[n] in section 3.1.4 Monitoring
Results.
Table 1-1 Results of

UL SRS RSRP
Parameter
Unit
Value Range
Description
Formula
CA Property
N/A
N/A
Carrier aggregation
property of a user.
N/A
The result contains

Non CA, CA PCell
and CA SCell.
Physical Cell
Identifier
N/A
0~503
Physical cell ID of a
serving cell.
N/A
ServCell
RSRP
0.01dBm
-15000 ~ -3000
RSRP of a serving
cell.
N/A
NeighborCel
l PCI[n]
N/A
0~503
Physical cell ID of the

nth neighboring cell.
n is an integer from 1
to 8.
N/A
NOTE
This field specifies the

sequence for reporting
the measurement
reports of neighboring
cells. A maximum of
eight neighboring
cells are dynamically
displayed.
NeighborCel
l RSRP
0.01dBm
-15000 ~ -3000

to 8.
NOTE
This field specifies

the sequence for
reporting the
measurement
reports of
neighboring cells. A
maximum of eight
neighboring cells
are dynamically
displayed.
Scheduling Monitoring
Issue 07 (2013-11-30)

vi
eNodeB
About This Document
No information in Issue 03 (2013-06-27) is deleted from this issue.
03 (2013-06-27)
This is the third official release.
Topic
Change Description
Modified the description in section "PDSCH

Maximum Number of Transmissions".
5.6.3 Parameters
Modified the name of "PPPoELink No".
02 (2013-05-30)
This is the second official release.
Topic
Change Description
2.2 Satisfaction of Service Monitoring
Modified the description in section 2.2.1

"Usage Scenario."
Modified the description of parameters CN
Operator UL QCI[n] Satisfaction rate of
Service and CN Operator DL QCI[n]
Satisfaction rate of Service in section
"Monitoring Results."
01 (2013-04-28)
This is the first official release.
Compared with draft C (2013-04-10), this issue does not include any new information.
Compared with draft C (2013-04-10), this issue includes the following changes.
Issue 07 (2013-11-30)

vii
eNodeB
About This Document
Topic
Change Description
4.3 RRU/RFU/BRU Output Power

Monitoring
Modified monitoring results.
4.8 Rx Frequency Scanning

4.9 DTF Test
5.5 UDP Test Monitoring
6.1 Sector Performance Monitoring
The following information in draft C (2013-04-10) is deleted from this issue:

LTE IP Link Monitoring
LTE IP Path Performance Monitoring
LTE SCTP Performance Monitoring
LTE Resource Group Monitoring
Draft C (2013-04-10)
This is the release of Draft C.
Compared with draft B (2013-02-25), this issue does not include any new information.
Compared with draft B (2013-02-25), this issue includes the following changes.
Topic
Change Description
2.5 User Statistics Monitoring
Modified the monitoring results of the

monitoring tasks in these sections.
2.16 DRB Statistics Monitoring

3.3 DL RSRP/RSRQ Monitoring
4.3 RRU/RFU/BRU Output Power Monitoring
4.4 Board Temperature Monitoring
4.7 RRU/RFU Output Power Monitoring
No information in draft B (2013-02-25) is deleted from this issue.
Draft B (2013-02-25)
This is the release of Draft B.
Compared with draft A (2013-02-08), this issue does not include any new information.
Compared with draft A (2013-02-08), this issue includes the following changes.
Topic
Change Description
3.2 VQI Monitoring
Modified the description of VQI Monitoring.
Issue 07 (2013-11-30)

viii
eNodeB
About This Document
Topic
Change Description
3.6 Quality of Channel Monitoring
Modified the description of

Quality of Channel Monitoring.
No information in issue draft A (2013-02-08) is deleted from this issue.
Draft A (2013-02-08)
This is the release of Draft A.
Compared with issue 02 (2012-11-30) of V100R005C01, this issue includes the following
new information.
Topic
Change Description
2.1 UL CoMP (Cell) Monitoring
Added the descriptions on UL CoMP (Cell)

Monitoring.
3.1 UL CoMP (User) Monitoring
Added the descriptions on UL CoMP (User)

Monitoring.
2.17 MLB Monitoring
Added new monitoring items.
3.2 VQI Monitoring
3.16 Cell Combination Monitoring
4.9 DTF Test
4.10 FFT Frequency Scan
4.11 AAS
4.12 Frequency Scanning Intermodulation

Interference Detection Monitoring
5.4 Transport Link Flux Stat Monitoring
5.7 IPSec Performance Monitoring
5.8 Transport OAM Monitoring
5.9 Transport Auto Setup User Plane

Monitoring
Compared with issue 02 (2012-11-30) of V100R005C01, this issue includes the following
changes:
Issue 07 (2013-11-30)

ix
eNodeB
About This Document
Topic
Change Description
2.9 RSSI Statistic Monitoring
Modified the descriptions on the results of

parameters and monitoring results.
2.10 Interference Detection Monitoring

2.11 TDD Interference Detection
Monitoring
Modified the Local Sector ID parameter to the

Sector Device ID parameter.
Added the value range for the Sector Device ID
parameter.
The following information in issue 02 (2012-11-30) of V100R005C01 is deleted from this

issue:
Board Temperature Monitoring
Transport Performance Monitoring
Spectrum Detection
Issue 07 (2013-11-30)

eNodeB
Contents
Contents
About This Document .................................................................................................................... ii
1 Introduction.................................................................................................................................... 1
1.1 Overview .......................................................................................................................................................... 1
1.2 Performance Monitoring Types ........................................................................................................................ 1
1.3 Precautions ....................................................................................................................................................... 3
1.3.1 Precautions for Monitoring on 3900 Series Base Stations ...................................................................... 3
1.3.2 Precautions for Monitoring on BTS3202Es and BTS3203Es ................................................................. 4
1.3.3 General Parameter Input Description ...................................................................................................... 5
2 Cell Performance Monitoring ..................................................................................................... 7

2.1 UL CoMP (Cell) Monitoring ............................................................................................................................ 7
2.1.1 Usage Scenario........................................................................................................................................ 7
2.1.2 Impact on Services .................................................................................................................................. 7
2.1.3 Parameters ............................................................................................................................................... 7
2.1.4 Monitoring Results .................................................................................................................................. 8
2.2 Satisfaction of Service Monitoring ................................................................................................................... 8
2.2.1 Usage Scenario........................................................................................................................................ 8
2.2.2 Service Impact ........................................................................................................................................ 8
2.2.3 Parameters ............................................................................................................................................... 9
2.2.4 Monitoring Results .................................................................................................................................. 9
2.3 General Throughput Monitoring .................................................................................................................... 11
2.3.1 Usage Scenario...................................................................................................................................... 11
2.3.2 Service Impact ...................................................................................................................................... 11
2.3.3 Parameters ............................................................................................................................................. 11
2.3.4 Monitoring Results ................................................................................................................................ 11
2.4 Service Statistics Monitoring ......................................................................................................................... 14
2.4.1 Usage Scenario...................................................................................................................................... 14
2.4.2 Service Impact ...................................................................................................................................... 14
2.4.3 Parameters ............................................................................................................................................. 15
2.5 User Statistics Monitoring .............................................................................................................................. 16
2.5.1 Usage Scenario...................................................................................................................................... 16
2.5.2 Service Impact ...................................................................................................................................... 16
Issue 07 (2013-11-30)

xi
eNodeB
Contents
2.5.3 Parameters ............................................................................................................................................. 16

2.6 Usage of RB Monitoring ................................................................................................................................ 19
2.6.1 Usage Scenario...................................................................................................................................... 19
2.6.2 Service Impact ...................................................................................................................................... 19
2.6.3 Parameters ............................................................................................................................................. 19
2.7 ICIC (Cell) Monitoring .................................................................................................................................. 21
2.7.1 Usage Scenario...................................................................................................................................... 21
2.7.2 Service Impact ...................................................................................................................................... 21
2.7.3 Parameters ............................................................................................................................................. 21
2.8 Multi-User MIMO Monitoring ....................................................................................................................... 23
2.8.1 Usage Scenario...................................................................................................................................... 23
2.8.2 Service Impact ...................................................................................................................................... 24
2.8.3 Parameters ............................................................................................................................................. 24
2.9 RSSI Statistic Monitoring .............................................................................................................................. 24
2.9.1 Usage Scenario...................................................................................................................................... 24
2.9.2 Service Impact ...................................................................................................................................... 24
2.9.3 Parameters ............................................................................................................................................. 24
2.10 Interference Detection Monitoring ............................................................................................................... 28
2.10.1 Usage Scenario .................................................................................................................................... 28
2.10.2 Service Impact .................................................................................................................................... 28
2.10.3 Parameters ........................................................................................................................................... 28
2.10.4 Monitoring Results .............................................................................................................................. 29
2.11 TDD Interference Detection Monitoring ...................................................................................................... 31
2.11.1 Usage Scenario .................................................................................................................................... 31
2.11.2 Impact on Services .............................................................................................................................. 31
2.11.3 Parameters ........................................................................................................................................... 31
2.12 Multi-User BF (Cell) Monitoring ................................................................................................................. 33
2.12.1 Usage Scenario .................................................................................................................................... 33
2.12.3 Parameters ........................................................................................................................................... 33
2.13 Scheduled Users Statistic Monitoring .......................................................................................................... 35
2.13.1 Usage Scenario .................................................................................................................................... 35
2.13.2 Service Impact .................................................................................................................................... 35
2.13.3 Parameters ........................................................................................................................................... 35
Issue 07 (2013-11-30)

xii
eNodeB
Contents
2.14 HARQ Statistic Monitoring.......................................................................................................................... 36

2.14.1 Usage Scenario .................................................................................................................................... 36
2.14.2 Service Impact .................................................................................................................................... 36
2.14.3 Parameters ........................................................................................................................................... 37
2.15 DCI Statistic Monitoring .............................................................................................................................. 40
2.15.1 Usage Scenario .................................................................................................................................... 40
2.15.2 Service Impact .................................................................................................................................... 40
2.15.3 Parameters ........................................................................................................................................... 40
2.16 DRB Statistics Monitoring ........................................................................................................................... 42
2.16.1 Usage Scenario .................................................................................................................................... 42
2.16.2 Service Impact .................................................................................................................................... 42
2.16.3 Parameters ........................................................................................................................................... 42
2.17 MLB Monitoring .......................................................................................................................................... 45
2.17.1 Usage Scenario .................................................................................................................................... 45
2.17.2 Service Impact .................................................................................................................................... 45
2.17.3 Parameters ........................................................................................................................................... 45
3 User Performance Monitoring .................................................................................................. 60

3.1 UL CoMP (User) Monitoring ......................................................................................................................... 60
3.1.1 Usage Scenario...................................................................................................................................... 60
3.1.2 Service Impact ...................................................................................................................................... 60
3.1.3 Parameters ............................................................................................................................................. 60
3.2 VQI Monitoring.............................................................................................................................................. 61
3.2.1 Usage Scenario...................................................................................................................................... 61
3.2.2 Service Impact ...................................................................................................................................... 61
3.2.3 Parameters ............................................................................................................................................. 61
3.3 DL RSRP/RSRQ Monitoring ......................................................................................................................... 63
3.3.1 Usage Scenario...................................................................................................................................... 63
3.3.2 Service Impact ...................................................................................................................................... 63
3.3.3 Parameters ............................................................................................................................................. 63
3.4 BLER Monitoring .......................................................................................................................................... 64
3.4.1 Usage Scenario...................................................................................................................................... 64
3.4.2 Service Impact ...................................................................................................................................... 64
3.4.3 Parameters ............................................................................................................................................. 65
Issue 07 (2013-11-30)

xiii
eNodeB
Contents
3.5 Power Headroom Monitoring ......................................................................................................................... 68

3.5.1 Usage Scenario...................................................................................................................................... 68
3.5.2 Service Impact ...................................................................................................................................... 68
3.5.3 Parameters ............................................................................................................................................. 68
3.6 Quality of Channel Monitoring ...................................................................................................................... 69
3.6.1 Usage Scenario...................................................................................................................................... 69
3.6.2 Service Impact ...................................................................................................................................... 69
3.6.3 Parameters ............................................................................................................................................. 69
3.7 Scheduling Monitoring ................................................................................................................................... 71
3.7.1 Usage Scenario...................................................................................................................................... 72
3.7.2 Service Impact ...................................................................................................................................... 72
3.7.3 Parameters ............................................................................................................................................. 72
3.8 RLC Data Stream Monitoring ........................................................................................................................ 76
3.8.1 Usage Scenario...................................................................................................................................... 76
3.8.2 Service Impact ...................................................................................................................................... 76
3.8.3 Parameters ............................................................................................................................................. 76
3.9 Throughput Monitoring .................................................................................................................................. 77
3.9.1 Usage Scenario...................................................................................................................................... 77
3.9.2 Service Impact ...................................................................................................................................... 77
3.9.3 Parameters ............................................................................................................................................. 77
3.10 AQM Monitoring ......................................................................................................................................... 79
3.10.1 Usage Scenario .................................................................................................................................... 79
3.10.2 Service Impact .................................................................................................................................... 79
3.10.3 Parameters ........................................................................................................................................... 79
3.11 UL Power Control Monitoring ..................................................................................................................... 80
3.11.1 Usage Scenario .................................................................................................................................... 80
3.11.2 Service Impact ..................................................................................................................................... 80
3.11.3 Parameters ........................................................................................................................................... 81
3.12 DL Power Control Monitoring ..................................................................................................................... 82
3.12.1 Usage Scenario .................................................................................................................................... 82
3.12.2 Service Impact .................................................................................................................................... 82
3.12.3 Parameters ........................................................................................................................................... 82
3.13 ICIC (User) Monitoring ............................................................................................................................... 84
3.13.1 Usage Scenario .................................................................................................................................... 84
Issue 07 (2013-11-30)

xiv
eNodeB
Contents
3.13.2 Service Impact .................................................................................................................................... 84

3.13.3 Parameters ........................................................................................................................................... 84
3.14 MCS Count Monitoring ............................................................................................................................... 86
3.14.1 Usage Scenario .................................................................................................................................... 86
3.14.2 Service Impact .................................................................................................................................... 87
3.14.3 Parameters ........................................................................................................................................... 87
3.15 Multi-User BF (User) Monitoring ................................................................................................................ 89
3.15.1 Usage Scenario .................................................................................................................................... 89
3.15.3 Parameters ........................................................................................................................................... 89
3.16 SFN Detection Monitoring ........................................................................................................................... 90
3.16.1 Usage Scenario .................................................................................................................................... 90
3.16.3 Parameters ........................................................................................................................................... 90
3.17 Cell Combination Monitoring ...................................................................................................................... 92
3.17.1 Usage Scenario .................................................................................................................................... 92
3.17.3 Parameters ........................................................................................................................................... 92
4 Device Monitoring ...................................................................................................................... 95

4.1 CPRI BER Monitoring ................................................................................................................................... 95
4.1.1 Usage Scenario...................................................................................................................................... 95
4.1.2 Service Impact ...................................................................................................................................... 95
4.1.3 Parameters ............................................................................................................................................. 95
4.2 CPU Usage Monitoring .................................................................................................................................. 96
4.2.1 Usage Scenario...................................................................................................................................... 96
4.2.2 Service Impact ...................................................................................................................................... 96
4.2.3 Parameters ............................................................................................................................................. 97
4.3 RRU/RFU/BRU Output Power Monitoring ................................................................................................... 97
4.3.1 Usage Scenario...................................................................................................................................... 97
4.3.2 Service Impact ...................................................................................................................................... 97
4.3.3 Parameters ............................................................................................................................................. 98
4.4 Board Temperature Monitoring ...................................................................................................................... 99
4.4.1 Usage Scenario...................................................................................................................................... 99
Issue 07 (2013-11-30)

xv
eNodeB
Contents
4.4.2 Service Impact ...................................................................................................................................... 99

4.4.3 Parameters ............................................................................................................................................. 99
4.5 Clock Quality Test Monitoring ..................................................................................................................... 100
4.5.1 Usage Scenario.................................................................................................................................... 100
4.5.2 Service Impact .................................................................................................................................... 100
4.5.3 Parameters ........................................................................................................................................... 101
4.6 IP Clock Data Collection Monitoring ........................................................................................................... 102
4.6.1 Usage Scenario.................................................................................................................................... 102
4.6.2 Service Impact .................................................................................................................................... 102
4.6.3 Parameters ........................................................................................................................................... 102
4.7 RRU/RFU Output Power Monitoring .......................................................................................................... 103
4.7.1 Usage Scenario.................................................................................................................................... 103
4.7.2 Service Impact .................................................................................................................................... 103
4.7.3 Parameters ........................................................................................................................................... 103
4.8 Rx Frequency Scanning ............................................................................................................................... 105
4.8.1 Usage Scenario.................................................................................................................................... 105
4.8.2 Service Impact .................................................................................................................................... 105
4.8.3 Parameters ........................................................................................................................................... 105
4.9 DTF Test....................................................................................................................................................... 106
4.9.1 Usage Scenario.................................................................................................................................... 106
4.9.2 Service Impact .................................................................................................................................... 107
4.9.3 Parameters ........................................................................................................................................... 107
4.10 FFT Frequency Scan .................................................................................................................................. 108
4.10.1 Usage Scenario .................................................................................................................................. 108
4.10.2 Service Impact .................................................................................................................................. 108
4.10.3 Parameters ......................................................................................................................................... 108
4.10.4 Monitoring Results ............................................................................................................................ 109
4.11 AAS ............................................................................................................................................................ 110
4.11.1 Usage Scenario .................................................................................................................................. 110
4.11.2 Service Impact ................................................................................................................................... 110
4.11.3 Parameters ......................................................................................................................................... 110
4.12 Frequency Scanning Intermodulation Interference Detection Monitoring ................................................. 111
4.12.1 Usage Scenario .................................................................................................................................. 111
4.12.2 Service Impact .................................................................................................................................. 111
4.12.3 Parameters ......................................................................................................................................... 111
Issue 07 (2013-11-30)

xvi
eNodeB
Contents
5 Transport Performance Monitoring ...................................................................................... 113

5.1 Local Pass-By Traffic Monitoring ................................................................................................................ 113
5.1.1 Usage Scenario.................................................................................................................................... 113
5.1.2 Service Impact .................................................................................................................................... 113
5.1.3 Parameters ........................................................................................................................................... 113
5.2 IP Performance Monitoring .......................................................................................................................... 114
5.2.1 Usage Scenario.................................................................................................................................... 114
5.2.2 Service Impact .................................................................................................................................... 114
5.2.3 Parameters ........................................................................................................................................... 114
5.3 Transport Port Flux Stat Monitoring ............................................................................................................ 115
5.3.1 Usage Scenario.................................................................................................................................... 115
5.3.2 Service Impact .................................................................................................................................... 115
5.3.3 Parameters ........................................................................................................................................... 115
5.4 Transport Link Flux Stat Monitoring ........................................................................................................... 123
5.4.1 Usage Scenario.................................................................................................................................... 123
5.4.2 Service Impact .................................................................................................................................... 123
5.4.3 Parameters ........................................................................................................................................... 123
5.5 UDP Test Monitoring ................................................................................................................................... 128
5.5.1 Usage Scenario.................................................................................................................................... 128
5.5.2 Service Impact .................................................................................................................................... 128
5.5.3 Parameters ........................................................................................................................................... 128
5.6 PPPoE Monitoring ....................................................................................................................................... 130
5.6.1 Usage Scenario.................................................................................................................................... 130
5.6.2 Service Impact .................................................................................................................................... 130
5.6.3 Parameters ........................................................................................................................................... 130
5.7 IPSec Performance Monitoring .................................................................................................................... 131
5.7.1 Usage Scenario.................................................................................................................................... 131
5.7.2 Service Impact .................................................................................................................................... 131
5.7.3 Parameters ........................................................................................................................................... 132
5.8 Transport OAM Monitoring ......................................................................................................................... 132
5.8.1 Usage Scenario.................................................................................................................................... 132
5.8.2 Service Impact .................................................................................................................................... 133
5.8.3 Parameters ........................................................................................................................................... 133
Issue 07 (2013-11-30)

xvii
eNodeB
Contents

5.9 Transport Auto Setup User Plane Monitoring .............................................................................................. 134
5.9.1 Usage Scenario.................................................................................................................................... 134
5.9.2 Service Impact .................................................................................................................................... 134
5.9.3 Parameters ........................................................................................................................................... 135
6 RRU/RFU Performance Monitoring ...................................................................................... 138

6.1 Sector Performance Monitoring ................................................................................................................... 138
6.1.1 Usage Scenario.................................................................................................................................... 138
6.1.2 Service Impact .................................................................................................................................... 138
6.1.3 Parameters ........................................................................................................................................... 138
Issue 07 (2013-11-30)

xviii
eNodeB
1 Introduction
Introduction
1.1 Overview
Performance monitoring is used to monitor the equipment running status and service status of
eNodeBs by using iManager M2000 Mobile Element Management System (referred to as
M2000) or the local maintenance terminal (LMT). Monitoring results are displayed in tables
or charts. In this way, equipment can be maintained and faults can be rectified by analyzing
the exceptions shown in monitoring results.
1.2 Performance Monitoring Types

Table 1-1 Performance monitoring types
Type
Task
Platform
Cell Performance
Monitoring
UL CoMP (Cell) Monitoring
M2000
Satisfaction of Service Monitoring
M2000
General Throughput Monitoring
M2000&LMT
Service Statistics Monitoring
M2000
User Statistics Monitoring
M2000&LMT
Usage of RB Monitoring
M2000
ICIC (Cell) Monitoring
M2000
Multi-User MIMO Monitoring
M2000
RSSI Statistic Monitoring
M2000
Interference Detection Monitoring
M2000&LMT
TDD Interference Detection Monitoring
M2000
Multi-User BF (Cell) Monitoring
M2000
Scheduled Users Statistic Monitoring
M2000
Issue 07 (2013-11-30)

eNodeB
1 Introduction
Type
User Performance
Monitoring
Device Monitoring
Issue 07 (2013-11-30)
Task
Platform
HARQ Statistic Monitoring
M2000
DCI Statistic Monitoring
M2000
DRB Statistics Monitoring
M2000
MLB Monitoring
M2000
UL CoMP (User) Monitoring
M2000
VQI Monitoring
M2000
DL RSRP/RSRQ Monitoring
M2000
BLER Monitoring
M2000
Power Headroom Monitoring
M2000
Quality of Channel Monitoring
M2000
M2000
RLC Data Stream Monitoring
M2000
Throughput Monitoring
M2000
AQM Monitoring
M2000
UL Power Control Monitoring
M2000
DL Power Control Monitoring
M2000
ICIC (User) Monitoring
M2000
MCS Count Monitoring
M2000
Multi-User BF (User) Monitoring
M2000
SFN Detection Monitoring
M2000
Cell Combination Monitoring
M2000
CPRI BER Monitoring
M2000
CPU Usage Monitoring
M2000&LMT
RRU/RFU/BRU Output Power

Monitoring
M2000
Board Temperature Monitoring
M2000&LMT
Clock Quality Test Monitoring
M2000&LMT
IP Clock Data Collection Monitoring
M2000&LMT
RRU/RFU Output Power Monitoring
LMT
Rx Frequency Scanning
LMT
DTF Test
LMT

eNodeB
1 Introduction
Type
Transport Performance
Monitoring
RRU/RFU Performance
Monitoring
Task
Platform
FFT Frequency Scan
LMT
AAS
LMT
Frequency Scanning Intermodulation

Interference Detection
LMT
Local Pass-By Traffic Monitoring
M2000&LMT
IP Performance Monitoring
M2000&LMT
Transport Port Flux Stat Monitoring
M2000&LMT
Transport Link Flux Stat Monitoring
M2000&LMT
UDP Test Monitoring
M2000
PPPoE Monitoring
M2000&LMT
IPSec Performance Monitoring
M2000&LMT
Transport OAM Monitoring
LMT
Transport Auto Setup User Plane

Monitoring
LMT
Sector Performance Monitoring
LMT
1.3 Precautions
This section describes the precautions for monitoring on 3900 series base stations and
BTS3202Es,and BTS3203Es.
NOTE
This issue do not support the following monitoring tasks:
LTE IP Link Monitoring
LTE IP Path Performance Monitoring
LTE SCTP Performance Monitoring
LTE Resource Group Monitoring
1.3.1 Precautions for Monitoring on 3900 Series Base Stations

3900 series base stations do not support the PPPoE Monitoring task. The PPPoE Monitoring
task is available only on BTS3202Es and BTS3203Es.
A carrier aggregation (CA) UE is able to access multiple cells simultaneously and report the
monitoring results of each cell at the same time. However, if a CA UE whose secondary
serving cell (SCell) is not configured or not activated, monitoring results in the SCell will not
Issue 07 (2013-11-30)

eNodeB
1 Introduction
be reported. If a monitoring item does not involve the CA feature, actual monitoring result of
the monitoring item is reported.
1.3.2 Precautions for Monitoring on BTS3202Es and BTS3203Es

Take the following precautions for monitoring on BTS3202Es and BTS3203Es:
The values of Cabinet No., Subrack No., and Slot No. must be 0.
The value of Local Cell ID must be 0.
BTS3202Es and BTS3203Es do not support the following monitoring tasks:
UL CoMP (Cell) Monitoring
CPRI BER Monitoring
TDD Interference Detection Monitoring
Multi-User BF (Cell) Monitoring
UL CoMP (User) Monitoring
Multi-User BF (User) Monitoring
SFN User Detection
RRU/RFU Output Power Monitoring
DTF Test
AAS
Frequency Scanning Intermodulation Interference Detection Monitoring
Transport OAM Monitoring
BTS3202Es
support the following monitoring tasks:
Rx Frequency Scanning
FFT Frequency Scan
BTS3202Es do not support PPP Performance monitoring and MP Performance

monitoring in the Transport Port Flux Stat Monitoring task.
BTS3202Es do not support the CA Property monitoring item in the following

monitoring tasks:
BLER Monitoring
Power Headroom Monitoring
Quality of Channel Monitoring
Throughput Monitoring
UL Power Control Monitoring
DL Power Control Monitoring
ICIC (User) Monitoring
MCS Count Monitoring
The monitoring results of this monitoring item in these monitoring tasks are Non CA.
Issue 07 (2013-11-30)
In Transport Port Flux Stat Monitoring and Transport Link Flux Stat Monitoring tasks,
Subboard Type must be BASE_BOARD.

eNodeB
1 Introduction
1.3.3 General Parameter Input Description

UEIDs are used to trace UE-level performance tests. UEIDs can be set to S-Temporary
Mobile Subscriber Identity (STMSI), Random Value, and Trace Reference No.
The following describes how to obtain and use the three types of UEIDs:
STMSI and Random Value

The ue-Identity IE in the RRC Connection Request message contains the MMEc and
m-TMSI fields. Therefore, you can obtain the MMEc and m-TMSI in hexadecimal
format from the ue-Identity IE. Enter the MMEc and m-TMSI in decimal format on the
trace interface.
The RRC Connection Request message may carry a Random Value in hexadecimal
format. Enter the Random Value in hexadecimal format on the trace interface.
The STMSI in decimal format and Random Value in hexadecimal format can also be
queried by running DSP ALLUEBASICINFO.
If the EPC does not support IMSI-based single UE tracing on the entire network, use the STMSI and
Random Value to collect data for single UE tracing and monitoring.
A maximum of 30 NEs of the same version can be selected when creating the tracing and monitoring
tasks based on the STMSI and Random Value. If the specified UE can be successfully handed over
among multiple selected NEs over the X2 interface, the UE data can be continuously collected in the
tracing and monitoring task.
If the eNodeB is not a selected NE for this tracing task, the M2000 cannot continue collecting data,
even when the UE is handed over to the original eNodeB.
Due to the timing sequence problem, however, some data may fail to be recorded when the UE is
handed over to the target NE.
Trace Reference No.

For details about the Trace Reference No., see Trace ID in 3GPP TS 32.422. The value
range is 016777215 (3 bytes).
Use a Trace Reference No. in the following conditions:
The EPC of a vendor must support single UE tracing on the entire network based on the
IMSI (complying with 3GPP TS 32.422), and the tracing task has been initiated.
For example, the EPC of Huawei has initiated LTE/EPC End-to-End User Trace.
The Trace Reference No. on the LTE side can be obtained from:
For the Huawei EPC, obtain the TraceID that is automatically displayed on the interface
when LTE/EPC End-to-End User Trace is created.
Obtain the Trace Reference No. from the Trace Activation IE from the S1 interface
messages (INITIAL CONTEXT SETUP REQUEST, HANDOVER REQUEST,
TRACE START) and the X2 interface message (HANDOVER REQUEST).
Click
displayed at the end of the User Trace ID of each tracing and monitoring task,
the M2000 will provide the existing Trace Reference No. on the live network.
The M2000 lists the Trace Reference No. of the first 200 tracing tasks in the recent two days.
If the EPC supports IMSI-based single UE tracing on the entire network, use the Trace Reference No. to
collect data for single UE tracing and monitoring.
A maximum of 30 NEs can be selected when creating the tracing and monitoring tasks based on the
Trace Reference No. The UE data can be continuously collected as long as the UE is served by the
selected NEs.
Issue 07 (2013-11-30)

eNodeB
1 Introduction
If the eNodeB is not a selected NE for this tracing task, the M2000 cannot continue collecting data.
However, the M2000 can collect the data again when the UE is handed over to the original eNodeB.
Issue 07 (2013-11-30)

eNodeB
2 Cell Performance Monitoring
Cell Performance Monitoring
2.1 UL CoMP (Cell) Monitoring

2.1.1 Usage Scenario
This task is used to monitor the number of cell-level UEs using uplink (UL) coordinated
multi-point (CoMP). This counter measures the UL CoMP Users Num of Scenario 1, UL
CoMP Users Num of Scenario 2, and UL CoMP Users Num of mixed Scenario. This
monitoring item is used to initially determine the usage of the UL CoMP function in a cell.
2.1.2 Impact on Services

None.
2.1.3 Parameters
Table 2-1 Parameters for UL CoMP (Cell) monitoring
Parameter
Description
Local Cell ID
Local cell ID of the cell performing cell-level UL CoMP

monitoring.
Monitor Period (ms)
Interval of reporting monitoring results. It can be set to 1000, 2000.
Issue 07 (2013-11-30)

eNodeB

Table 2-2 Results of UL CoMP (Cell) monitoring
Parameter
Unit
Value
Range
Description
Formula
UL CoMP
Users Num of
Scenario 1
Number
0 to 1000
The eNodeB reports the number

of UEs using the UL CoMP in
scenario 1 to the M2000 at the
end of each monitoring period.
N/A
UL CoMP Users of Scenario 1:

UEs located at the cell edge
using the UL CoMP function.
UL CoMP
Users Num of
Scenario 2
Number
0 to 1000

scenario 2 to the M2000 at the
end of each monitoring period.
N/A
UL CoMP Users of Scenario 2:

UEs that are interfered by UEs
using the ULCoMP of scenario
1 in a collaborative neighboring
cell use the UL CoMP function.
UL CoMP
Users Num of
mixed Scenario
Number
0 to 1000

mixed scenario to the M2000 at
the end of each monitoring
period.
N/A
UL CoMP Users of mixed

Scenario: UEs using the UL
CoMP of both scenario1 and
scenario 2 during a monitoring
period.
2.2 Satisfaction of Service Monitoring

This task is used to monitor the QoS satisfaction rate of VoIP services with QoS class
identifier (QCI) 1. This task is also used to monitor the QoS satisfaction rates of GBR services
with QCIs 2 to 4 in a cell based on the throughput. The QoS satisfaction rates of GBR
services indicate whether the QoS requirements of admitted GBR services are met and can be
used to determine the cell load status.
2.2.2 Service Impact

None.
Issue 07 (2013-11-30)

eNodeB
2.2.3 Parameters
Table 2-3 Parameters for satisfaction of service monitoring
Parameter
Description
Test Items
It can be set to DL QCI1 Satisfaction rate of Service, DL QCI2

Satisfaction rate of Service, DL QCI3 Satisfaction rate of Service,
DL QCI4 Satisfaction rate of Service, UL QCI1 Satisfaction rate
of Service, UL QCI2 Satisfaction rate of Service, UL QCI3
Satisfaction rate of Service, UL QCI4 Satisfaction rate of Service,
Congestion State, or a combination of some items.
Local Cell ID
ID of the cell on which satisfaction of service monitoring is

performed.
CN Operator ID
In a RAN sharing scenario, a cell can be shared by a maximum of six

operators. In a non-RAN sharing scenario, a cell can be used by only
one operator.
Monitor Period
(ms)
Interval of reporting monitoring results. It can be set to 50, 100, 200,

500, 1000, or 2000.

Table 2-4 Results of satisfaction of service monitoring
Parameter
Unit
Value
Range
Description
Formula
CN
Operator ID
N/A
0 to 5
ID of the operator for which satisfaction

of service monitoring is performed.
N/A
Issue 07 (2013-11-30)

eNodeB
Parameter
Unit
Value
Range
Description
Formula
CN
Operator
UL QCI[n]
Satisfaction
rate of
Service
0 to 100
Average QoS satisfaction rates of

different uplink services in a cell when
monitoring results are reported. n ranges
from 1 to 4. On the uplink, the uplink
QoS satisfaction rate of QCI1 is
represented by the average uplink VoIP
service satisfaction rate in a cell, that is,
the ratio of the total uplink VoIP service
satisfaction rates to the total number of
VoIP services in a cell. The higher the
proportion, the higher the satisfaction
rate.
N/A
The uplink QoS satisfaction rates of

GBR services with QCIs 2 to 4 are
evaluated for each logical channel group.
The QoS satisfaction rate of a logical
channel group is evaluated based on the
transmitted data and the total amount of
data to be transmitted. The higher the
transmitted data volume, the higher the
QoS satisfaction rate.
CN
Operator
DL QCI[n]
Satisfaction
rate of
Service
0 to 100
Average QoS satisfaction rates of

different downlink services in a cell
when monitoring results are reported.
The value range of n is 1 to 4. On the
downlink, the downlink QoS satisfaction
rate of QCI1 is represented by the
average downlink VoIP service
satisfaction rate in a cell, that is, the ratio
of the total downlink VoIP service
satisfaction rates to the total number of
VoIP services in a cell. The higher the
proportion, the higher the satisfaction
rate.
N/A
The downlink QoS satisfaction rates of

GBR services with QCIs 2 to 4 are
evaluated based on the ratio of the
scheduled data volume of these services
to the total data volume to be transmitted
for these services. If the scheduled data
volume is high or the data volume in the
buffer is low, the QoS satisfaction rate is
high.
Congestion
State
Issue 07 (2013-11-30)
N/A
Congesti
on,
Unconge
stion
Current congestion state of an operator

when monitoring results are reported.

N/A
10
eNodeB
2.3 General Throughput Monitoring

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

None.
2.3.3 Parameters
Table 2-5 Parameters for general throughput monitoring
Parameter
Description
Local Cell ID
ID of the cell on which general throughput monitoring is

performed.
Test Items
It can be set to RLC Throughput, RLC Throughput of GBR

service, RLC Throughput of NON-GBR service, or a
combination of some items.
CN Operator ID
In a RAN sharing scenario, a cell can be shared by a maximum of

six operators. In a non-RAN sharing scenario, a cell can be used by
only one operator.
Monitor Period (ms)
Interval of reporting monitoring results. It can be set to 50, 100,

200, 500, 1000, or 2000.
RLC Throughput
Table 2-6 Results of RLC Throughput monitoring

Parameter
Unit
Value
Range
Description
Formula
CN Operator ID
N/A
0 to 5
ID of the operator for

which general
throughput monitoring
is performed.
N/A
Cell Uplink RLC

Throughput
bps
0 to
300000000
Uplink throughput of a
cell. Only RLC
payloads are included.
The RLC headers,
retransmitted data, and
state reports are
excluded.
(General uplink
RLC throughput
(byte) x 8) x
1000/Monitor
Period (ms)
Issue 07 (2013-11-30)

11
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Cell Downlink
RLC Throughput
bps
0 to
300000000
Downlink throughput
of a cell. Only the RLC
The RLC headers,
state reports are
excluded.
(General downlink
RLC throughput
(byte) x 8) x
1000/Monitor
Period (ms)
CN Operator Cell
Uplink RLC
Throughput
bps
0 to
300000000
Uplink RLC throughput

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

Parameter
Unit
Value
Range
Description
Formula
CN Operator ID
N/A
0 to 5

which general
is performed.
N/A
Cell GBR Traffic

Uplink RLC
Throughput
bps
0 to
300000000
Uplink throughput of
GBR services in a cell.
included. The RLC
are excluded.
(General RLC
throughput of
uplink GBR
services (Byte) x 8)
x 1000/Monitor
Period (ms)
Issue 07 (2013-11-30)

12
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Cell GBR Traffic

Downlink RLC
Throughput
bps
0 to
300000000
Downlink throughput of
GBR services in a cell.
included. The RLC
are excluded.
(General RLC
throughput of
downlink GBR
x 1000/Monitor
Period (ms)
CN Operator Cell
GBR Traffic
Uplink RLC
Throughput
bps
0 to
300000000
Uplink GBR service

throughput of an
operator of a cell. Only
RLC payloads are
included. The RLC
are excluded.
(Uplink GBR
service throughput
of an operator of a
cell (byte) x 8) x
1000/Monitor
Period (ms)
Operator Cell GBR

Traffic Downlink
RLC Throughput
bps
0 to
300000000
Downlink GBR service

throughput of an
operator cell. Only RLC
The RLC headers,
state reports are
excluded.
(Downlink GBR
service throughput
of an operator of a
cell (Byte) x 8) x
1000/Monitor
Period (ms)
RLC Throughput of NON-GBR service
Table 2-8 Results of RLC Throughput of NON-GBR service monitoring

Parameter
Unit
Value
Range
Description
Formula
CN Operator ID
N/A
0 to 5

which general
is performed.
N/A
Cell Non-GBR
Traffic Uplink
RLC Throughput
bps
0 to
300000000
non-GBR services in a
cell. Only RLC
The RLC headers,
state reports are
excluded.
(General RLC
throughput of
uplink non-GBR
x 1000/Monitor
Period (ms)
Issue 07 (2013-11-30)

13
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Cell Non-GBR
Traffic Downlink
RLC Throughput
bps
0 to
300000000
cell. Only RLC
The RLC headers,
state reports are
excluded.
(General RLC
throughput of
downlink non-GBR
x 1000/Monitor
Period (ms)
CN Operator Cell
Non-GBR Traffic
Uplink RLC
Throughput
bps
0 to
300000000
CN operator cell. Only
RLC payloads are
included. The RLC
are excluded.
General uplink
RLC throughput of
non-GBR services
in a CN operator
cell (Byte) x 8) x
1000/Monitor
Period (ms)
CN Operator Cell
Non-GBR Traffic
Downlink RLC
Throughput
bps
0 to
300000000
CN operator cell. Only
RLC payloads are
included. The RLC
are excluded.
General downlink
RLC throughput of
non-GBR services
in a CN operator
cell (Byte) x 8) x
1000/Monitor
Period (ms)
2.4 Service Statistics Monitoring

This task is used to count the number of services with different QCIs in a cell to view the
distribution of these services.

None.
Issue 07 (2013-11-30)

14
eNodeB
2.4.3 Parameters
Table 2-9 Parameters for service statistics monitoring
Parameter
Description
Test Items
It can be set to Service Number of QCI1, Service Number of

QCI2, Service Number of QCI3, Service Number of QCI4,
Service Number of QCI5, Service Number of QCI6, Service
Number of QCI7, Service Number of QCI8, or Service Number of
QCI9.
Local Cell ID
ID of the cell on which service statistic monitoring is performed.
CN Operator ID
In a RAN sharing scenario, a cell can be shared by a maximum of six

operators. In a non-RAN sharing scenario, a cell can be used by only
one operator.
Monitor Period
(ms)

500, 1000, or 2000.

Table 2-10 Results of service statistics monitoring
Parameter
Unit
Value
Range
Description
Formula
Service Number
of QCI[n]
Number
0 to 4000
Total number of services

with different QCIs when
monitoring results are
reported. n ranges from 1
to 9.
N/A
CN Operator ID
N/A
0 to 5

which service statistic
monitoring is performed.
N/A
CN Operator
Service Number
of QCI[n]
Number
0 to 4000
Total number of services

with different QCIs for
an operator when
reported. n ranges from 1
to 9.
N/A
Issue 07 (2013-11-30)

15
eNodeB
2.5 User Statistics Monitoring

This task is used to count the number of users in different scenarios to view the distribution of
users in a cell.

None.
2.5.3 Parameters
Table 2-11 Parameters for user statistics monitoring
Parameter
Description
Test Items
It can be set to Keep UL Synch Users Number, General

Users Number, NO-Activated Users Number, or a
combination of some items.
Local Cell ID
ID of the cell on which user statistic monitoring is performed.
CN Operator ID
In a RAN sharing scenario, a cell can be shared by a maximum

of six operators. In a non-RAN sharing scenario, a cell can be
used by only one operator.
Monitor Period (ms)
Interval of reporting monitoring results. It can be set to 50,

100, 200, 500, 1000, or 2000.
Keep UL Synch Users Number
Table 2-12 Results of Keep UL Synch Users Number monitoring

Parameter
Unit
Value
Range
Description
Formula
Keep UL Synch
Users Number
Number
0 to 2000
Number of users with uplink

synchronization in a cell when
monitoring results are reported.
Users with uplink
synchronization are also known
as active users.
N/A
NOTE
CA users that use the local cell as

their SCell keeping uplink
synchronization are users with
uplink synchronization.
Issue 07 (2013-11-30)

16
eNodeB
CN Operator ID
N/A
0 to 5
ID of the operator for which

user statistic monitoring is
performed.
N/A
CN Operator
Keep UL Synch
Users Number
Number
0 to 2000
Number of an operator's users

with uplink synchronization
when monitoring results are
reported. Users with uplink
synchronization are also known
as active users.
N/A
NOTE
An operator's CA users that use

the local cell as their SCell
keeping uplink synchronization
are users with uplink
synchronization.
General Users Number
Table 2-13 Results of General Users Number monitoring

Parameter
Unit
Value
Range
Description
Formula
General
Users
Number
Number
0 to 2000
Number of connected users and

users that are requesting access
to the E-UTRAN in a cell when
the monitoring result is reported.
Number of
connected users
+ Number of
users that are
requesting access
to the E-UTRAN
Connected users consist of

active users and inactive users.
Users that are requesting access
to the E-UTRAN consist of the
users initiating radio resource
control (RRC) connection
requests and the users that are
handed over to the E-UTRAN
cell.
CN
Operator ID
Issue 07 (2013-11-30)
N/A
0 to 5
ID of the operator for which user

statistic monitoring is
performed.

N/A
17
eNodeB
Parameter
Unit
Value
Range
Description
Formula
CN
Operator
General
Users
Number
Number
0 to 2000
Number of connected users and

users that are requesting access
to the E-UTRAN of an operator
when the monitoring result is
reported.
Number of
connected users
+ Number of
users that are
requesting access
to the E-UTRAN
Connected users consist of

active users and inactive users.
Users that are requesting access
to the E-UTRAN consist of the
users initiating radio resource
control (RRC) connection
requests and the users that are
handed over to the E-UTRAN
cell.
NO-Activated Users Number
Table 2-14 Results of NO-Activated Users Number monitoring

Parameter
Unit
Value
Range
Description
Formula
CN Operator ID
N/A
0 to 5
ID of the operator for which

user statistic monitoring is
performed.
N/A
NO-Activated
Users Number
Number
0 to 2000
Number of inactive users in a

cell when monitoring results
are reported. Inactive users are
also known as users with
uplink out-of-synchronization.
N/A
NOTE
CA users that use the local cell as

their SCell keeping uplink
out-of-synchronization are users
with uplink
out-of-synchronization.
CN Operator
NO-Activated
Users Number
Number
0 to 2000
Number of inactive users of an

operator when monitoring
results are reported. Inactive
users are also known as users
with uplink
N/A
NOTE
An operator's CA users that use

the local cell as their SCell
keeping uplink
out-of-synchronization are users
with uplink
Issue 07 (2013-11-30)

18
eNodeB

2.6 Usage of RB Monitoring

This task is used to monitor the usage of cell-level RBs in different scheduling modes. RB is
the minimum unit for time-frequency resource allocation.

During high-volume traffic, the monitoring data may be lost but services are not affected.
2.6.3 Parameters
Table 2-15 Parameters for usage of RB monitoring
Parameter
Description
Local Cell ID
ID of the cell on which RB usage monitoring is performed.
CN Operator ID
In a RAN sharing scenario, a cell can be shared by a maximum of

six operators. In a non-RAN sharing scenario, a cell can be used by
only one operator.
Monitor Period (ms)

200, 500, 1000, or 2000.

Table 2-16 Results of usage of RB monitoring
Parameter
Unit
Value
Range
Description
Formula
Downlink
Equivalent
Used RB Num
Number
0 to
2000000
Number of downlink RBs used

within a monitoring period,
which is the total number of RBs
used by paging messages and
system information blocks
(SIBs) within all transmission
time intervals (TTIs) in the
monitoring period.
N/A
In a SFN or cell combination

scenario, the number of used
PRBs in each physical cell is
accumulated.
Issue 07 (2013-11-30)

19
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Uplink
Equivalent
Used RB Num
Number
0 to
2000000
Number of uplink RBs used

within a monitoring period,
which is the total number of RBs
occupied by the PUSCH,
PUCCH, and PRACH within all
TTIs in the monitoring period.
N/A

accumulated.
Downlink Freq
Diversity Used
RB Num
Number
0 to
2000000
Number of RBs allocated for

downlink diversity scheduling
within all TTIs in a monitoring
period.
N/A

accumulated.
Downlink Freq
Select Used RB
Num
Number
0 to
2000000

downlink frequency selective
scheduling within all TTIs in a
monitoring period.
N/A

accumulated.
Downlink
HARQ RB
Used RB Num
Number
0 to
2000000

downlink HARQ retransmission
period.
N/A

accumulated.
Uplink PUCCH
RB Num
Number
0 to 200000
Number of RBs used by the

PUCCH within all TTIs in a
monitoring period.
N/A
CN Operator
ID
N/A
0 to 5
ID of the operator for which RB

usage monitoring is performed.
N/A
Issue 07 (2013-11-30)

20
eNodeB
Parameter
Unit
Value
Range
Description
Formula
CN Operator
Downlink
Equivalent
Used RB Num
Number
0 to 200000
Number of downlink RBs used

by the PDSCH of the operator
period.
N/A
NOTE
The value of this parameter

equals the actual number of
downlink RBs used by the
operator.
CN Operator
Uplink
Equivalent
Used RB Num
Number
0 to 200000
Number of uplink RBs used by

the PUSCH of the operator
period.
N/A
NOTE
The value of this parameter equals

the actual number of uplink RBs
used by the operator.
2.7 ICIC (Cell) Monitoring

This task is used to check the status of ICIC (cell) by monitoring the data associated to ICIC
(cell).

None.
2.7.3 Parameters
Table 2-17 Parameters for ICIC (cell) monitoring
Parameter
Description
Test Items
It can be set to HII Information, OI Information, Proportion of

Uplink High Interference RB in System Bandwidth, Uplink Edge
User RB Information, Uplink Neighbor Cell List Information,
Cell Downlink Edge Bandwidth Information, or a combination of
some items.
Local Cell ID
ID of the cell on which ICIC (cell) monitoring is performed.
Monitor Period
(ms)

500, 1000, or 2000.
Issue 07 (2013-11-30)

21
eNodeB
HII information
Table 2-18 Results of HII information monitoring

Parameter
Unit
Value
Range
Description
Formula
Valid RB
Num in One
HII sent
Number
0 to 100
Number of valid RBs in one HII

reported, which is the same as
the number of RBs occupied by
the current cell bandwidth.
N/A
OI information
Table 2-19 Results of OI information monitoring

Parameter
Unit
Value
Range
Description
Formula
Valid RB Num
in One OI sent
Number
0 to 100
Number of valid RBs in one OI

reported, which is the same as
the number of RBs occupied by
the current cell bandwidth.
N/A
Proportion of Uplink High Interference RB in System Bandwidth
Table 2-20 Results of Proportion of Uplink High Interference RB in System Bandwidth

monitoring
Parameter
Unit
Value
Range
Description
Formula
Proportion of Uplink
High Interference
RB in System
Bandwidth
0 to 100
Proportion of uplink
high-interference RBs in the
serving cell to RBs occupied by
the current cell bandwidth when
N/A
Issue 07 (2013-11-30)

22
eNodeB
Uplink Edge User RB Information
Table 2-21 Results of Uplink Edge User RB Information monitoring

Parameter
Unit
Value
Range
Description
Formula
Uplink Edge User

Valid RB Num
Number
0 to 100
Number of valid RBs in the

available frequency band for
uplink cell edge users (CEUs)
reported.
N/A
Uplink Neighbor Cell List Information
Table 2-22 Results of Uplink Neighbor Cell List Information monitoring

Parameter
Unit
Value Range
Description
Formula
Uplink Valid
Interference
Neighbor Cell
Num
Number
0 to 32
Number of valid neighboring

cells used for ICIC (cell)
reported.
N/A
Cell Downlink Edge Band Information
Table 2-23 Results of Cell Downlink Edge Band Information monitoring

Parameter
Unit
Value
Range
Description
Formula
Cell Downlink Edge

Band Valid RB Num
Numb
er
0 to 100
Number of valid RBs in the

cell downlink edge
frequency band when
reported.
N/A
2.8 Multi-User MIMO Monitoring

This task is used to monitor the number of UEs paired with multi-user multiple-input
multiple-output (MU-MIMO) during a transmission time interval (TTI). Two UEs
successfully paired with MU-MIMO are called one pair. On the M2000, the total number of
UEs paired with MU-MIMO within a configured period is displayed, based on which the
number of paired UEs in the current cell can be viewed.
Issue 07 (2013-11-30)

23
eNodeB

None.
2.8.3 Parameters
Table 2-24 Parameters for Multi-User MIMO monitoring
Parameter
Description
Local Cell ID
ID of the cell on which MU-MIMO monitoring is performed.
Monitor Period
(ms)

Table 2-25 Results of Multi-User MIMO monitoring
Parameter
Unit
Value Range
Description
Formula
MIMO UE
Pair Num
Pair
0 to 10000
Total number of UEs paired with

uplink MU-MIMO during all
TTIs in the monitoring period.
Two UEs paired with
MU-MIMO are called one pair.
N/A
2.9 RSSI Statistic Monitoring

This task is used to monitor the RX power of each RB used by the demodulation reference
signals (DMRS) within the current bandwidth and average RX power of each antenna.

None.
2.9.3 Parameters
Table 2-26 Parameters for RSSI statistic monitoring
Parameter
Description
Main eNodeB ID
ID of the eNodeB serving the monitored cell. This parameter can be

left unspecified in scenarios other than the SFN and Cell
Combination in LTE TDD.
Issue 07 (2013-11-30)

24
eNodeB
Parameter
Description
Local Cell ID
ID of the cell on which interference RSSI statistic detect monitoring

is performed.
Monitor Period (ms)

200, 500, 1000, or 2000.

Table 2-27 Results of RSSI statistic monitoring
Parameter
Unit
Value Range
Description
Formula
RRU Cabinet
No.
N/A
0 to 62
Number of
the cabinet
that houses
the
RRU
serving the
cell.
This
parameter is
set to an
actual value
only
in
scenarios of
SFN and Cell
Combination
in LTE TDD,
and is set to
an
invalid
value in other
scenarios.
N/A
An
invalid
value
is
displayed as
N/A on the
M2000.
Issue 07 (2013-11-30)

25
eNodeB
Parameter
Unit
Value Range
Description
Formula
RRU Subrack
No.
N/A
4 to 5
Number of
the subrack
that houses
the
RRU
serving the
cell.
This
parameter is
set to an
actual value
only
in
scenarios of
SFN and Cell
Combination
in LTE TDD,
and is set to
an
invalid
value in other
scenarios.
N/A
60 to 254
An
invalid
value
is
displayed as
N/A on the
M2000.
RRU Slot No.
N/A
0 to 8
Number of
the slot that
houses
the
RRU serving
the cell. This
parameter is
set to an
actual value
only
in
scenarios of
SFN and Cell
Combination
in LTE TDD,
and is set to
an
invalid
value in other
scenarios.
N/A
An
invalid
value
is
displayed as
N/A on the
M2000.
Issue 07 (2013-11-30)

26
eNodeB
Parameter
Unit
Value Range
Description
RB Spectrum
Information
dBm
140 to 50
RSSI of an
RB.
The
power of 12
subcarriers in
the RB is
summed and
then averaged
for multiple
antennas.
RSSIs of the
RBs falling
beyond the
bandwidth
are reported
as 0 by layer
1.
Received
Signal
Strength
Indicator
dBm
System
Bandwidth
(Number of
RB)
Number
antenna[y]
RSSI
dBm
140 to 50
6, 15, 25, 50,

75, 100
25, 50, 75, and
100
in
BTS3202Es and
BTS3203Es.
140 to 50
RSSI within
the current
system
bandwidth.
Formula
RSSI_RB(k) =
- 1 11
AntNumAntNum
AntIdx = 0 n = 0 {P(AntIdx, k, n)}
AntNum
where
AntNum indicates the
number of antennas for the
current cell.
P(
) indicates
the receive power of
subcarrier n in RBk
received by antenna AntIdx.
where
SysRB
indicates
the
number of RBs in the
current system bandwidth.
Current
system
bandwidth.
N/A
RSSI
for
antenna
y
within
the
current
system
bandwidth. y
ranges from 0
to 7.
RSSI_Ant(AntIdx) = {P(AntIdx, k, n)}
SysRB 11
k=0 n=0
where
current cell.
P(
) indicates
the receive power of
subcarrier n in RBk of
antenna AntIdx. The value
of AntIdx is y.
Issue 07 (2013-11-30)

27
eNodeB
2.10 Interference Detection Monitoring

This task is used to record the current average interference power of each RB for checking the
uplink interference.

None.
2.10.3 Parameters
Table 2-28 Parameters for interference detection monitoring
Parameter
Description
Main eNodeB ID

left unspecified in scenarios other than the SFN and Cell
Combination in LTE TDD.
Local Cell ID
ID of the cell on which interference detection monitoring is

performed.
Monitor Period (ms)

200, 500, 1000, or 2000.
Issue 07 (2013-11-30)

28
eNodeB

Table 2-29 Results of interference detection monitoring
Parameter
Unit
Value
Range
Description
Formula
RRU Cabinet
No.
N/A
0 to 62
Number of
the cabinet
that houses
the
RRU
serving the
cell.
This
parameter is
set to an
actual value
only
in
scenarios of
SFN and Cell
Combination
in LTE TDD,
and is set to
an
invalid
value in other
scenarios.
N/A
An
invalid
value
is
displayed as
N/A on the
M2000.
RRU Subrack
No.
N/A
4 to 5
60 to 254
Number of
the subrack
that houses
the
RRU
serving the
cell.
This
parameter is
set to an
actual value
only
in
scenarios of
SFN and Cell
Combination
in LTE TDD,
and is set to
an
invalid
value in other
scenarios.
N/A
An
invalid
value
is
displayed as
N/A on the
M2000.
Issue 07 (2013-11-30)

29
eNodeB
Parameter
Unit
Value
Range
Description
Formula
RRU Slot No.
N/A
0 to 8
Number of
the slot that
houses
the
RRU serving
the cell. This
parameter is
set to an
actual value
only
in
scenarios of
SFN and Cell
Combination
in LTE TDD,
and is set to
an
invalid
value in other
scenarios.
N/A
An
invalid
value
is
displayed as
N/A on the
M2000.
140 to 50
CELL AVG
Interference
Noise Power
per RB (dBm)
dBm
PUCCH
Extended RB
Number
Number
0 to 48
Number of
extended
PHCCH RBs,
which is also
the number of
RBs reserved
on the band
edges for the
PUSCH.
N/A
Max
Number
PUCCH
Number
0 to 26
Maximum
number
of
RBs in the
current
PUCCH
N/A
Issue 07 (2013-11-30)
RB
of
Average
RB-level
interference
noise power
of
the
PUSCH
in
the
whole
system
bandwidth.

where
PUSCH_RB indicates the
number of RBs on the
current PUSCH.
30
eNodeB
Parameter
Unit
Value
Range
Description
Formula
System
Bandwidth
(Number
of
RB)
Number
6, 15, 25, 50,

75, 100
Current
system
bandwidth.
N/A
RBx
Interference
Noise Power
(dBm)
dBm
25, 50, 75,

and 100 in
BTS3202Es
and
BTS3203Es.
140 to 50
Average
PUSCH
interference
noise power
on each RB.
Interference
of the RBs
falling
beyond the
PUSCH
bandwidth is
reported as 0.
where
current cell. IN(AntIdx, k,
n) indicates the receive
power of subcarrier n in RB
k received by antenna
AntIdx.
2.11 TDD Interference Detection Monitoring

This task is used to detect TDD interference by comparing the RX power of the symbols in
the first and last uplink subframes.

None.
2.11.3 Parameters
Table 2-30 Parameters for TDD interference detection monitoring
Parameter
Description
Main eNodeB ID

left unspecified if the specified eNodeB is to be monitored.
Local Cell ID
ID of the cell on which TDD interference detection is performed.
Monitor Period (ms)
Interval of reporting detection results. The default value is 2000.
Issue 07 (2013-11-30)

31
eNodeB

Table 2-31 Results of TDD interference detection monitoring
Parameter
Unit
Value
Range
Description
Formula
RRU Cabinet No.
N/A
0 to 62
Number of the cabinet that

houses the RRU serving the
cell.
N/A
RRU Subrack No.
N/A
4 to 5
Number of the subrack that

houses the RRU serving the
cell.
N/A
60 to 254
RRU Slot No.
N/A
0 to 8
Number of the slot that houses

the RRU serving the cell.
N/A
Uppts IN Power
dBm
32768 to
+32767
Power of the interference in

the uplink pilot time slots
(UpPTSs).
N/A
RB Group x IN
Power
dBm
32768 to
+32767
Interference noise (IN) of the

xth RB group on the full
bandwidth.
N/A
Receive Power of
Symbol 0 in First
UL Subframe
dBm
32768 to
+32767
Receive power of symbol 0 in

the first uplink subframe.
N/A
Receive Power of
the 6th (or 4th)
Symbol in First
UL Subframe
dBm
This parameter is invalid if the

LBBPc frame transmitted
upon initiation of the
monitoring request does not
have loads.
32768 to
+32767
Receive power of the last

symbol in the first uplink
subframe. If normal cyclic
prefixes (CPs) are used, the
6th symbol is measured; if
extended CPs are used, the 4th
symbol is measured.
N/A

have loads.
Receive Power of
Symbol 0 in Last
UL Subframe
Issue 07 (2013-11-30)
dBm
32768 to
+32767
Receive power of symbol 0 in

the last uplink subframe.
N/A

have loads.

32
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Receive Power of
the Last but Two
Symbols on the
Last UL Subframe
dBm
32768 to
+32767
Receive power of the last but

two symbols in the first uplink
subframe. If normal CPs are
used, the 11th symbol is
measured; if extended CPs are
used, the 9th symbol is
measured.
N/A

have loads.
2.12 Multi-User BF (Cell) Monitoring

This task is used to monitor multi-user pairing using beamforming (BF) on the single
frequency network (SFN), which helps to locate multi-user beamforming (MUBF) algorithm
faults.

None.
2.12.3 Parameters
Table 2-32 Parameters for multi-user BF (cell) monitoring
Parameter
Description
Local Cell ID
ID of the cell on which cell-level multi-user BF monitoring is

performed.
Monitor Period (ms)

200, 500, 1000, or 2000.
Issue 07 (2013-11-30)

33
eNodeB

Table 2-33 Results of multi-user BF (cell) monitoring
Parameter
Unit
Value
Range
Description
Formula
Indep-Indep
Number of
successful
MUBF pairing
RB
Number
0 to 1000
Number of downlink spectrum

resources used by UEs of
independent scheduling that have
been successfully paired using
MUBF. It is obtained by
accumulating the number of RBs
used by a UE at each TTI and
calculating the average number at
the end of the monitoring period.
For cell-level monitoring, the
related RBs of all RRUs are
counted.
N/A
Indep-Indep
Number of
users'
successful
pairing Users
Pair
0 to 1000
Number of pairs of UEs of

MUBF. It is obtained by
accumulating the number of UE
pairs at each TTI and calculating
the average number based on the
number of TTIs at the end of the
monitoring period.
N/A
Indep-Indep
Number of
enable pairing
RB
Number
0 to 1000
Number of RBs that can be used

by UEs of independent
scheduling that can be paired
using MUBF, excluding the RBs
used for retransmission, non-TM
8 single stream, and the VoIP
service. It is obtained by
N/A
Indep-Joint
Number of
successful
MUBF pairing
RB
Number
0 to 1000
Number of downlink spectrum

resources used by UEs of
MUBF with UEs of combined
scheduling. It is obtained by
For cell-level monitoring, the
related RBs of all RRUs are
counted.
N/A
Issue 07 (2013-11-30)

34
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Indep-Joint
Number of
users'
successful
pairing Users
Pair
0 to 1000
Number of UE pairs that have

MUBF between UEs of
independent scheduling and UEs
of combined scheduling. It is
obtained by accumulating the
number of UE pairs at each TTI
and calculating the average
number based on the number of
TTIs at the end of the monitoring
period. For cell-level monitoring,
the related RBs of all RRUs are
counted.
N/A
Joint-Joint
Number of
enable pairing
RB
Number
0 to 1000
Number of RBs that can be used

by UEs of combined scheduling
that can be paired using MUBF,
excluding the RBs used for
retransmission, non-TM 9 single
stream, and the VoIP service. It is
number of RBs used by a UE at
each TTI and calculating the
average number at the end of the
monitoring period. For cell-level
monitoring, the related RBs of all
RRUs are counted.
N/A
2.13 Scheduled Users Statistic Monitoring

This task is used to monitor the distribution of UEs in various scheduling modes in a cell.

None.
2.13.3 Parameters
Table 2-34 Parameters for scheduled users statistic monitoring
Parameter
Description
Local Cell ID
ID of the cell on which scheduled users statistic monitoring is

performed.
Issue 07 (2013-11-30)

35
eNodeB
Parameter
Description
Monitor Period (ms)

200, 500, 1000, or 2000.

Table 2-35 Results of scheduled users statistic monitoring
Parameter
Unit
Value
Range
Description
Formula
Total DLSCH
Users Within
Monitor Period
Number
0 to 65535
Total number of UEs in

downlink scheduling mode
within a monitoring period.
N/A
Total DLSCH
Frequency
Selected Users
Within Monitor
Period
Number
0 to 65535

downlink frequency selective
scheduling mode within a
monitoring period.
N/A
Total DLSCH
Diversity Users
Within Monitor
Period
Number
0 to 65535

downlink diversity scheduling
mode within a monitoring
period.
N/A
Total ULSCH
Users Within
Monitor Period
Number
0 to 65535
Total number of UEs in uplink

scheduling mode within a
monitoring period.
N/A
2.14 HARQ Statistic Monitoring

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

None.
Issue 07 (2013-11-30)

36
eNodeB
2.14.3 Parameters
Table 2-36 Parameters for HARQ statistic monitoring
Parameter
Description
Test Items
It can be set to DL HARQ State, UL HARQ State, or a combination

of the items.
Local Cell ID
ID of the cell on which HARQ statistic monitoring is performed.
Monitor Period
(ms)
Interval of reporting monitoring results. It can be set to 1000 or 2000.
DL HARQ State
Table 2-37 Results of DL HARQ State monitoring

Parameter
Unit
Value
Range
Description
Formula
DL PDSCH
Code[m]
ACK Num
Number
0 to 64000
Number of ACKs for codeword m

(m = {0, 1}) within a monitoring
period. The greater the proportion
of the number of ACKs to the
total number of ACKs, NACKs,
and DTXs, the more successfully
received messages from the
eNodeB, indicating effective cell
coverage.
N/A
For details about ACK and

NACK, see 3GPP TS 36.321.
DL PDSCH
Code[m]
NACK Num
Number
0 to 64000
Number of NACKs for codeword

m (m = {0, 1}) within a
monitoring period. The greater the
proportion of the number of
NACKs to the total number of
ACKs, NACKs, and DTXs, the
less successfully received
messages from the eNodeB.
N/A
For details about ACK and

NACK, see 3GPP TS 36.321.
Issue 07 (2013-11-30)

37
eNodeB
Parameter
Unit
Value
Range
Description
Formula
DL PDSCH
Code[m]
NoRsp Num
Number
0 to 64000
Number of NoRsps for codeword

m (m = {0, 1}) within a
monitoring period. NoRsp
indicates that no HARQ feedback
is decoded due to an exception in
the eNodeB, or the eNodeB
decodes the HARQ feedback but
the decoding duration exceeds the
HARQ RTT.
N/A
For details about the HARQ RTT,

see DL PDSCH Rsp for [m] TTI
Num.
DL PDSCH
Code[m]
DTX Num
Number
0 to 64000
Number of DTXs for codeword m

(m = {0, 1}) within a monitoring
period. DTX indicates that the
eNodeB fails to detect the HARQ
feedback.
N/A
For details, see section 7.3 in

3GPP TS 36.213.
DL PDSCH
Version[m]
Num
Number
0 to 64000
Number of times the HARQ

redundancy version in transport
blocks (TBs) sent from the
eNodeB is m (m = {0, 1, 2, 3})
N/A
DL PDSCH
Code[m]
DTX/NACK
Num
Number
0 to 64000
Number of times that DTXs and

NACKs cannot be distinguished
for downlink codeword m (m =
{0, 1}) within a monitoring
period.
N/A
DTX indicates that the eNodeB

does not detect the HARQ
feedback from a UE. For details,
see section 7.3 in 3GPP TS
36.213.
For details about NACKs, see
section 5.3.2 in 3GPP TS 36.321.
Issue 07 (2013-11-30)

38
eNodeB
Parameter
Unit
Value
Range
Description
Formula
DL PDSCH
Rsp for [m]
TTI Num
Number
0 to 64000
Number of times the eNodeB

receives the HARQ feedback
within a downlink scheduling
interval m TTIs (One TTI equals
to one millisecond) within a
monitoring period.
N/A
m = {8, 9, 10, 11}. Any value

greater than 11 is treated as 11.
This item monitors the duration
that the eNodeB internally
processes the HARQ feedback.
According to the protocol, the
HARQ RTT equals to 8 TTIs for
FDD mode. For TDD mode, the
HARQ RTT varies depending on
the subframe distribution rate. If
the duration exceeds the HARQ
RTT, the eNodeB experiences
internal processing exceptions.
UL HARQ State
Table 2-38 Results of UL HARQ State monitoring

Parameter
Unit
Value
Range
Description
Formula
UL PUSCH
ACK Num
Number
0 to 64000
Number of times the CRC for data

blocks on the PUSCH is correct
within a monitoring period. The
greater the proportion of the
number of ACKs to the total
number of ACKs, NACKs, and
DTXs, the more the times that the
CRC for the PUSCH data sent by
the UE to the eNodeB is correct,
indicating higher uplink
transmitting quality of the UE.
N/A
UL PUSCH
NACK Num
Number
0 to 64000
Number of times the CRC for data

blocks on the PUSCH is incorrect
within a monitoring period. The
greater the proportion of the
number of NACKs to the total
number of ACKs, NACKs, and
DTXs, the more the times that the
CRC for the PUSCH data sent by
the UE to the eNodeB is incorrect.
N/A
Issue 07 (2013-11-30)

39
eNodeB
Parameter
Unit
Value
Range
Description
Formula
UL PUSCH
DTX Num
Number
0 to 64000
Number of times the UE does not

transmit data on the PUSCH within
a monitoring period. The greater
the proportion of the number of
DTXs to the total number of ACKs,
NACKs, and DTXs, the more the
times that the UE incorrectly
demodulates the downlink PDCCH
data.
N/A
UL PUSCH
Version[n]
Num
Number
0 to 64000
Number of times the HARQ

redundancy version for the eNodeB
uplink scheduling is m (m = {0, 1,
2, 3}) within a monitoring period.
N/A
For details, see 3GPP TS 36.321.
2.15 DCI Statistic Monitoring

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

PDCCH.
The PDCCH symbol number indicates the number of OFDM symbols occupied by a
PDCCH.

None.
2.15.3 Parameters
Table 2-39 Parameters for DCI statistic monitoring
Parameter
Description
Test Items
It can be set to DCI STATISTIC.
Local Cell ID
ID of the cell on which DCI statistic monitoring is performed.
Monitor Period
(ms)
Interval of reporting monitoring results. It can be set to 1000 or

2000.
Issue 07 (2013-11-30)

40
eNodeB

Table 2-40 Results of DCI statistic monitoring
Parameter
Unit
Value
Range
Description
Formula
PDCCH
Type DCI[n]
Num
Number
0 to 64000
Total number of times

the PDCCH type is DCI
format n (n = {0, 1, 1A,
1B, 1C, 1D, 2, 2A, 2B,
3, 3A}) within a
monitoring period.
N/A
PDCCH Use
[n] CCE
Num
Number
0 to 64000

the aggregation level is
n (n = {1, 2, 4, 8})
within a monitoring
period.
N/A
CFI Engross
[n] Symbol
State Num
Number
0 to 64000

the control format
indicator (CFI) is n (n =
{1, 2, 3, 4}) OFDM
symbols within a
monitoring period.
N/A
UL DCI
Utilization
Within a
Monitoring
Period
0 to 100
Uplink DCI utilization

within a monitoring
period.
Total number of CCEs

in uplink DCI/Total
number of CCEs
within the monitoring
period
DL DCI
Utilization
Within a
Monitoring
Period
Comm DCI
Utilization
Within a
Monitoring
Period
Issue 07 (2013-11-30)
Uplink DCI is DCI

format 0.
0 to 100
Downlink DCI
utilization within a
monitoring period.
Downlink DCI is DCI
format n, where n is 1,
1A, 1B, 1C, 1D, 2, 2A,
and 2B.
0 to 100
Common DCI
utilization within a
monitoring period.
Common DCI is DCI
format 3 and DCI
format 3A.


in downlink
DCI/Total number of
CCEs within the
monitoring period.

in common DCI/Total
number of CCEs
within the monitoring
period.
41
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Total CCE
Num Within
a Monitoring
Period
Number
0 to 100000

within a monitoring
period. If the CFI
adaption switch is
disabled, the total
number of CCEs does
not change. When the
symbol dynamic
adjustment switch is
enabled, the number of
CCEs varies based on
the adjustment of the
CFI. The status of the
switch can be queried
by running the DSP
CELLPDCCHALGO
command.
N/A
2.16 DRB Statistics Monitoring

This task is used to monitor data transmission information at the cell-level PDCP, RLC, or
MAC layer, including the throughput, number of received packets, and number of transmitted
packets.

None.
2.16.3 Parameters
Table 2-41 Parameters for DRB statistics monitoring
Parameter
Description
Test Items
It can be set to DL DRB STATISTIC, UL DRB STATISTIC, or a

combination of the items.
Local Cell ID
ID of the cell on which DRB statistic monitoring is performed.
Monitor Period
(ms)
Interval of reporting monitoring results. It can be set to 1000 or 2000.
Issue 07 (2013-11-30)
DL DRB STATISTIC

42
eNodeB
Table 2-42 Results of downlink DRB statistics monitoring

Parameter
Unit
Value
Range
Description
Formula
Number of
Packets
Received at the
DL PDCP
Packet
0 to
300000000
Total number of data packets

received by the downlink PDCP
layer within a monitoring
period.
N/A
Number of Bits
Received at the
DL PDCP
Bit
0 to
300000000
Total throughput for data

packets received by the
downlink PDCP layer within a
monitoring period.
N/A
Number of TBs
for DL MAC
scheduling
Number
0 to
300000000
Total number of TBs for

downlink MAC scheduling
N/A
Number of Bits
for DL MAC
scheduling
Bit
0 to
300000000
Total number of bits contained

in the TBs for downlink MAC
scheduling within a monitoring
period.
N/A
Number of
Times DL RLC
Sends Data in
AM mode
Number
0 to
300000000
Total number of times that the

downlink RLC layer transmits
data in acknowledgment (AM)
mode within a monitoring
period.
N/A
NOTE
The RLC layer transmits data in

AM or UM modes. In AM mode, a
transmission report is fed back. In
UM, no report is fed back.
Number of
Times DL RLC
Sends Data in
UM mode
Number
0 to
300000000

downlink RLC layer transmits
data in unacknowledgment
(UM) mode within a
monitoring period.
N/A
Number of Succ
Trans DL PDCP
SDUs with
QCI[n]
Number
0 to
4294967295

downlink PDCP SDU packets
are successfully transmitted
over the QCI[n] within a
monitoring period, in which n
ranges from 1 to 9.
N/A
Processing
Delay of DL
PDCP SDUs
with QCI[n]
ms
0 to
4294967295
Total processing delay of

downlink packets over the
QCI[n] within a monitoring
period, in which n ranges from
1 to 9.
N/A
Issue 07 (2013-11-30)
UL DRB STATISTIC

43
eNodeB
Table 2-43 Results of uplink DRB statistics monitoring

Parameter
Unit
Value Range
Description
Formula
Number of TBs
for UL MAC
Scheduling
Number
0 to 300000000
Total number of TBs for

uplink MAC scheduling
within a monitoring
period.
N/A
Number of Bits
for UL MAC
Scheduled
Bit
0 to 300000000
Total number of bits

contained in the TBs for
uplink MAC scheduling
within a monitoring
period.
N/A
Number of UL
TBs With CRC
Correct
Number
0 to 300000000
Total number of times the

uplink MAC layer receives
correct CRCs from a UE
within a monitoring
period.
N/A
Number of UL
TBs With CRC
Incorrect
Number
0 to 300000000

uplink MAC layer receives
incorrect CRCs from a UE
within a monitoring
period.
N/A
Number of
Times UL RLC
Receives Data
in AM mode
Number
0 to 300000000

uplink RLC layer transmits
data in AM mode within a
monitoring period.
N/A
Number of
Times UL RLC
Receives Data
in UM mode
Number
0 to 300000000

uplink RLC layer transmits
data in UM mode within a
monitoring period.
N/A
Number of
Packets
Transmitted at
the UL PDCP
Packet
0 to 300000000
Total number of data

packets transmitted by the
uplink PDCP layer within
a monitoring period.
N/A
Number of Bits
Transmitted at
the UL PDCP
Bit
0 to 300000000
Total throughput for data

packets transmitted by the
uplink PDCP layer within
N/A
Issue 07 (2013-11-30)

44
eNodeB
2.17 MLB Monitoring

This task is used to monitor performance counters on the cell-level mobility load balancing
(MLB), including performance counters on the MLB in the serving cell and target cell, and
MLB monitoring execution.

None.
2.17.3 Parameters
Table 2-44 Parameters for MLB monitoring
Parameter
Description
Local Cell ID
ID of the cell on which MLB monitoring is performed.
Monitor Period
(ms)
Interval of reporting monitoring results. It can be set to 1000, or

2000.
Ncell 1
Mandatory. For details, see Table 2-45.
Ncell 2
Optional. For details, see Table 2-45.
Ncell 3
Ncell 4
Table 2-45 Parameters for neighboring cells

Parameter
Description
Ncell x Type
Neighboring cell types. It can be set to LTEinterFreq,

UTRAN, GERAN, LTEintraFreq, or NULL.
NOTE
Ncell 1 is mandatory and must not be set to NULL.
The value of x ranges from 1 to 4.
MCC
Mobile country code of neighboring E-UTRAN, UTRAN, or

GERAN cells.
MNC
Mobile network code of neighboring E-UTRAN, UTRAN,

or GERAN cells.
LTEinter NCell x eNodeB

ID
ID of the eNodeB serving a neighboring inter-frequency cell.

This parameter is valid only when Ncell Type is set to
LTEinterFreq.
Issue 07 (2013-11-30)

45
eNodeB
Parameter
Description
LTEinter NCell x Cell ID
ID of a neighboring inter-frequency cell. This parameter is

valid only when Ncell Type is set to LTEinterFreq.
LTEintra NCell x eNodeB

ID
ID of the eNodeB serving a neighboring intra-frequency cell.

This parameter is valid only when Ncell Type is set to
LTEintraFreq.
LTEintra NCell x Cell ID
ID of a neighboring intra-frequency cell. This parameter is

valid only when Ncell Type is set to LTEintraFreq.
UTRAN NCell x RNC ID
ID of the RNC of a neighboring UTRAN cell. This

parameter is valid only when Ncell Type is set to UTRAN.
UTRAN NCell x CELL ID
ID of a neighboring UTRAN cell. This parameter is valid

only when Ncell Type is set to UTRAN.
GSM NCell x Geran ID
ID of a neighboring GERAN cell. This parameter is valid

only when Ncell Type is set to GERAN.
GSM NCell x Geran Lac
Location area code of a neighboring GERAN cell. This

parameter is valid only when Ncell Type is set to GERAN.

Table 2-46 Results of MLB monitoring
Parameter
Unit
Value Range
Description
Formula
Local Cell ID
N/A
0~35
ID of the cell
on which MLB
monitoring is
performed.
N/A
Cell
GBR
PRB
0 to 100
PRB usage in
downlink GBR
services of the
serving
cell
within
a
monitoring
period.
N/A
Serving Cell uplink

Non-GBR traffic
PRB usage(%)
0 to 100
PRB usage in
uplink
non-GBR
services of the
serving
cell
within
a
monitoring
period.
N/A
Serving
downlink
traffic
usage(%)
Issue 07 (2013-11-30)

46
eNodeB
Parameter
Unit
Value Range
Description
Formula
Serving
Cell
downlink
Non-GBR traffic
PRB usage(%)
0 to 100
PRB usage in
downlink
non-GBR
services of the
serving
cell
within
a
monitoring
period.
N/A
Serving Cell uplink

Total traffic PRB
usage(%)
0 to 100
PRB usage in
uplink
GBR
and non-GBR
services of the
serving
cell
within
a
monitoring
period.
N/A
Serving
downlink
traffic
usage(%)
0 to 100
PRB usage in
downlink GBR
and non-GBR
services of the
serving
cell
within
a
monitoring
period.
N/A
Issue 07 (2013-11-30)
Cell
Total
PRB

47
eNodeB
Parameter
Unit
Value Range
Description
Formula
Intra-frequency
MLB type
N/A
Decimal number, which

must be converted to a
binary number for cause
value
determination.
Meanings represented
by each bit in the binary
number are described as
follows:
Reasons for the

intra-frequency
MLB.
N/A
BIT0: UlGBRIntraMLB
BIT1: DlGBRIntraMLB
BIT2:
UlNonGBRIntraMLB
BIT3:
DlNonGBRIntraMLB
BIT4:
UlTotalIntraMLB
BIT5:
DlTotalIntraMLB
If the value of a bit is 0,
the
intra-frequency
MLB is not triggered by
the cause specified by
the bit. If the value of a
bit
is
1,
the
intra-frequency MLB is
triggered by the cause
specified by the bit.
If a GUI value is 8, and
the
corresponding
binary value is 001000,
the
intra-frequency
MLB is caused by
DlNonGBRIntraMLB.
Issue 07 (2013-11-30)

48
eNodeB
Parameter
Unit
Value Range
Description
Formula
Inter-frequency
MLB type
N/A

value
determination.
follows:
Reasons for the

inter-frequency
MLB.
N/A
BIT0: UlGBRInterMLB
BIT1: DlGBRInterMLB
BIT2:
UlNonGBRInterMLB
BIT3:
DlNonGBRInterMLB
BIT4:
UlTotalInterMLB
BIT5:
DlTotalInterMLB
the
inter-frequency
MLB is not triggered by
the bit. If the value of a
bit
is
1,
the
inter-frequency MLB is
triggered by the cause
specified by the bit.
the
corresponding
the
intra-frequency
MLB is caused by
DlNonGBRInterMLB.
Issue 07 (2013-11-30)

49
eNodeB
Parameter
Unit
Value Range
Description
Formula
Utran MLB Type
N/A

value
determination.
follows:
Reasons for the

inter-RAT
MLB
to
UTRAN.
N/A
BIT0:
UlGBRUtranMLB
BIT1:
DlGBRUtranMLB
BIT2:
UlNonGBRUtranMLB
BIT3:
DlNonGBRUtranMLB
BIT4:
UlTotalUtranMLB
BIT5:
DlTotalUtranMLB
the MLB to UTRAN is
not triggered by the
cause specified by the
bit. If the value of a bit
is 1, the MLB to
UTRAN is triggered by
the bit. If a GUI value is
8, and the corresponding
the MLB to UTRAN is
caused
by
DlNonGBRUtranML
B.
Issue 07 (2013-11-30)

50
eNodeB
Parameter
Unit
Value Range
Description
Formula
IfGeran MLB Type
N/A

value
determination.
follows:
Reasons
inter-RAT
MLB
GERAN.
N/A
BIT0:
UlGBRGeranMLB
BIT1:
DlGBRGeranMLB
for
to
NOTE
BTS3202Es
and
BTS3203Es do
not support this
monitoring
item.
BIT2:
UlNonGBRGeranMLB
BIT3:
DlNonGBRGeranMLB
BIT4:
UlTotalGeranMLB
BIT5:
DlTotalGeranMLB
the MLB to GERAN is
not triggered by the
cause specified by the
bit. If the value of a bit
is 1, the MLB to
GERAN is triggered by
the bit.
the
corresponding
the MLB to GERAN is
caused
by
DlNonGBRGeranML
B.
LTEintra
MCC
NCell
N/A
Depending on eNodeB
configurations
Mobile country
code
of
a
neighboring
intra-frequency
cell.
N/A
LTEintra
MNC
NCell
N/A
Depending on eNodeB
configurations
Mobile network
code
of
a
neighboring
intra-frequency
cell.
N/A
Issue 07 (2013-11-30)

51
eNodeB
Parameter
Unit
Value Range
Description
Formula
LTEintra
NCell
eNodeB ID
N/A
Depending on eNodeB
configurations
ID
of
the
eNodeB
serving
a
neighboring
intra-frequency
cell.
N/A
LTEintra
Cell ID
N/A
Depending on eNodeB
configurations
ID
of
a
neighboring
intra-frequency
cell.
N/A
Ue number in the
edge of the serving
cell near to the
intra-frequency cell
Number
0 to 254
Number of cell
edge UEs near a
neighboring
intra-frequency
cell.
N/A
CIO value of the

serving cell (dB)
dB
24 to 24
CIO value of
the serving cell.
N/A
CIO margin value

of the serving
cell(dB)
dB
0 to 2
CIO
margin
value of the
serving cell.
N/A
CIO adjusted cause

of the serving cell
N/A
0: NULL
Cause values of
CIO adjustment
on the serving
cell and its
neighboring
cells.
N/A
NCell
1: Serving cell spring to

modify
comeback
quit MLB
4: Serving cell respond
to modify
to comeback
to quit MLB
Intra-Frequency
cell uplink GBR
traffic
PRB
usage(%)
0 to 100
PRB usage in
uplink
GBR
services target
of
the
intra-frequency
cell.
N/A
Intra-Frequency
cell downlink GBR
traffic
PRB
usage(%)
0 to 100
PRB usage in
downlink GBR
services in the
target
intra-frequency
cell.
N/A
Issue 07 (2013-11-30)

52
eNodeB
Parameter
Unit
Value Range
Description
Formula
Intra-Frequency
cell
uplink
Non-GBR traffic
PRB usage(%)
0 to 100
PRB usage in
uplink
non-GBR
services in the
target
intra-frequency
cell.
N/A
Intra-Frequency
cell
downlink
Non-GBR traffic
PRB usage(%)
0 to 100
PRB usage in
downlink
non-GBR
services in the
target
intra-frequency
cell.
N/A
Intra-Frequency
cell uplink Total
traffic
PRB
usage(%)
0 to 100
PRB usage in
uplink
GBR
and non-GBR
services in the
target
intra-frequency
cell.
N/A
Intra-Frequency
cell downlink Total
traffic
PRB
usage(%)
0 to 100
PRB usage in
downlink GBR
and non-GBR
services in the
target
intra-frequency
cell.
N/A
Issue 07 (2013-11-30)

53
eNodeB
Parameter
Unit
Value Range
Description
Formula
Cause
of
Intra-Frequency
cell not being MLB
cell
N/A
0: Null
Cause of a
neighboring
intra-frequency
cell not being
selected as an
MLB cell.
N/A
1: Algo_Not_triggered
2: Invalid_Ncell
3: NO_X2_Link
4: HO_Unallowed
5: PCI_Conflict
6:
History_Succ_Ratio_Lo
w
7: Ncell_Deactive
8: Ncell_Black
9:
Ncell_Energy_Saving
10: Pci_Fail
11: App_Fail
12:
Ncell_IntraMLB_Sw_O
ff
13:
Hardware_Load_high
14: S1_TNL Load_high
15:
Ncell_Radio_Resource
_Unmeet
16: Margin_Ue_Num_
Unmeet
17: Cio_Adjust_Max
18:
Resource_Status_not_R
eceived
19:
Radio_Resource_Invali
d
20:
Current_Succ_Ratio_L
ow
21: Best_Cell_Unmeet
22:
Dont_Sel_intra_eNB_n
cell_for_inter_eNB_M
LB
23:
Dont_Sel_inter_eNB_n
cell_for_intra_eNB_M
LB
Issue 07 (2013-11-30)

54
eNodeB
Parameter
Unit
Value Range
Description
Formula
Success ratio of
handover to the
intra-frequency
cell(%)
0 to 100
Success rate of
handovers from
the serving cell
to the target
intra-frequency
cell.
N/A
UE number of
MLB handover to
the intra-frequency
cell
Number
0 to 254
Number of UEs
that are handed
over to the
target
intra-frequency
cell based on
MLB.
The
value becomes
0 after MLB is
exited.
N/A
LTEinter
MCC
NCell
N/A
Depending on eNodeB
configurations
Mobile country
code
of
a
neighboring
inter-frequency
cell.
N/A
LTEinter
MNC
NCell
N/A
Depending on eNodeB
configurations
Mobile network
code
of
a
neighboring
inter-frequency
cell.
N/A
LTEintra
NCell
eNodeB ID
N/A
Depending on eNodeB
configurations
ID
of
the
eNodeB
serving
a
neighboring
inter-frequency
cell.
N/A
LTEinter
Cell ID
N/A
Depending on eNodeB
configurations
ID
of
a
neighboring
inter-frequency
cell.
N/A
Inter-Frequency
cell uplink GBR
traffic
PRB
usage(%)
0 to 100
PRB usage in
uplink
GBR
services in the
target
inter-frequency
cell.
N/A
Inter-Frequency
cell downlink GBR
traffic
PRB
usage(%)
0 to 100
PRB usage in
downlink GBR
services in the
target
inter-frequency
cell.
N/A
Issue 07 (2013-11-30)
NCell

55
eNodeB
Parameter
Unit
Value Range
Description
Formula
Inter-Frequency
cell
uplink
Non-GBR traffic
PRB usage(%)
0 to 100
PRB usage in
uplink
non-GBR
services in the
target
inter-frequency
cell.
N/A
Inter-Frequency
cell
downlink
Non-GBR traffic
PRB usage(%)
0 to 100
PRB usage in
downlink
non-GBR
services in the
target
inter-frequency
cell.
N/A
Inter-Frequency
cell uplink Total
traffic
PRB
usage(%
0 to 100
PRB usage in
uplink
GBR
and non-GBR
services in the
target
inter-frequency
cell.
N/A
Inter-Frequency
cell downlink Total
traffic
PRB
usage(%)
0 to 100
PRB usage in
downlink GBR
and non-GBR
services in the
target
inter-frequency
cell.
N/A
Issue 07 (2013-11-30)

56
eNodeB
Parameter
Unit
Value Range
Description
Formula
Cause
of
Inter-Frequency
cell not being MLB
cell
N/A
0: Null
Cause
of
Inter-Frequenc
y cell not being
selected
as
MLB cell.
N/A
2: Invalid_Ncell
3: NO_X2_Link
4: HO_Unallowed
5: PCI_Conflict
6:
History_Succ_Ratio_Lo
w
7: Ncell_Deactive
8: Ncell_Black
9:
Ncell_Energy_Saving
10: Pci_Fail
11: App_Fail
12:
Ncell_IntraMLB_Sw_O
ff
13:
Hardware_Load_high
14: S1_TNL Load_high
15:
_Unmeet
16: Margin_Ue_Num_
Unmeet
17: Cio_Adjust_Max
18:
Resource_Status_not_R
eceived
19:
Radio_Resource_Invali
d
20:
Current_Succ_Ratio_L
ow
21: Best_Cell_Unmeet
22:
Dont_Sel_intra_eNB_n
cell_for_inter_eNB_M
LB
23:
Dont_Sel_inter_eNB_n
cell_for_intra_eNB_M
LB
Issue 07 (2013-11-30)

57
eNodeB
Parameter
Unit
Value Range
Description
Formula
Success ratio of
handover to the
inter-frequency
cell(%)
Number
0 to 100
Success rate of
handovers from
the serving cell
to the target
inter-frequency
cell.
N/A
UE number of
MLB transfer load
control for the
inter-frequency cell
Number
0 to 254
Number of UEs
entering MLB
transfer
load
control for the
inter-frequency
cell. The value
becomes 0 after
UEs exit MLB.
N/A
UE number of
MLB handover to
the inter-frequency
cell
Number
0 to 254
Number of UEs
handed over to
the
inter-frequency
cell for MLB
after the UE
enters
MLB
transfer
load
control.
The
value becomes
0 after UEs exit
MLB.
N/A
UTRAN
MCC
NCell
N/A
Depending on eNodeB
configurations
Mobile country
code
of
a
neighboring
UTRAN cell.
N/A
UTRAN
MNC
NCell
N/A
Depending on eNodeB
configurations
Mobile network
code
of
a
neighboring
UTRAN cell.
N/A
UTRAN
RNC ID
NCell
N/A
Depending on eNodeB
configurations
ID of the RNC
of
a
neighboring
UTRAN cell.
N/A
UTRAN NCell Cell

ID
N/A
Depending on eNodeB
configurations
ID
of
a
neighboring
UTRAN cell.
N/A
Utran Cell
Status
N/A
0: Overload
Load status of a
neighboring
UTRAN cell.
N/A
load
1: Congestion
2: Normal
3: Invalid
Issue 07 (2013-11-30)

58
eNodeB
Parameter
Unit
Value Range
Description
Formula
Cause of utran cell

not being MLB cell
N/A
0: Null
Cause of a
neighboring
UTRAN
cell
not
being
selected as the
MLB cell.
N/A
2:
_Unmeet
UE number of
MLB handover to
the utran cell
Number
0 to 254
Number of UEs
handed over to
the
UTRAN
cell for MLB.
The
value
becomes 0 after
UEs exit MLB.
N/A
GSM NCell MCC
N/A
Depending on eNodeB
configurations
Mobile country
code
of
a
neighboring
GERAN cell.
N/A
GSM NCell MNC
N/A
Depending on eNodeB
configurations
Mobile network
code
of
a
neighboring
GERAN cell.
N/A
GSM NCell Geran

ID
N/A
Depending on eNodeB
configurations
ID
of
a
neighboring
GERAN cell.
N/A
GSM NCell Geran

Lac
N/A
Depending on eNodeB
configurations
Location area
code
of
a
neighboring
GERAN cell.
N/A
Cause of geran cell

not being MLB cell
N/A
0: Null
Cause of a
neighboring
GERAN
cell
not
being
selected as the
MLB cell.
N/A
UE number of
MLB handover to
the geran cell
Number
Number of UEs
handed over to
the
GERAN
cell for MLB.
The
value
becomes 0 after
UEs exit MLB.
N/A
Issue 07 (2013-11-30)
0 to 254

59
eNodeB
User Performance Monitoring
3.1 UL CoMP (User) Monitoring

This task is used to monitor the UL CoMP used by UEs, and applies to the verification and
performance evaluation of the UL CoMP function.

None.
3.1.3 Parameters
Table 3-1 Parameters for UL CoMP (user) monitoring
Parameter
Description
UEID Type
It can be set to STMSI, Random Value, or Trace Reference No.
MMEc
It must be configured when the UEID Type parameter is set to

STMSI.
mTMSI

STMSI.
Random Value

Random Value.
PLMN

Trace Reference No. When this parameter is selected, MCC and
MNC specify the mobile country code and mobile network code,
respectively.
User Trace ID

Trace Reference No.
Monitor Period (ms)
Issue 07 (2013-11-30)

60
eNodeB

Table 3-2 Results of UL CoMP (user) monitoring
Parameter
Unit
Value
Range
Description
Formula
Physical Cell
Identifier
N/A
0 to 503
Physical cell identifier of the

serving cell.
N/A
UL CoMP User
Indication
N/A
N/A
Category of the UL CoMP used by a

UE. It is classified into Normal User,
UL COMP User of Scenario 1 or UL
COMP User of Scenario 2.
N/A
3.2 VQI Monitoring

This task is used to monitor the uplink and downlink voice quality of a UE and measure
counters affecting voice quality in real time. If a UE performs a handover within the default
monitoring period of 2.5 seconds, the monitoring result may not be accurate because the
number of voice packets is insufficient.

None.
3.2.3 Parameters
Table 3-3 Parameters for VQI monitoring
Parameter
Description
UEID Type
MMEc

STMSI.
mTMSI

STMSI.
Random Value

Random Value.
PLMN
It must be configured when the UEID Type parameter is set to Trace

Reference No. When this parameter is selected, MCC and MNC
specify the mobile country code and mobile network code,
respectively.
User Trace ID

Reference No.
Issue 07 (2013-11-30)

61
eNodeB
Parameter
Description
Monitor Period
(ms)
Interval of reporting monitoring results. It is set to 2500 by default.
Test Item
It can be set to DL Quality of Voice, or UL Quality of Voice. All

items are monitored by default.
DL Quality of Voice monitoring
Table 3-4 Results of DL Quality of Voice monitoring

Monitoring
Results
Unit
Value Range
Description
Formula
Physical Cell
Identifier
N/A
0 to 503
Physical cell identifier of

the serving cell.
N/A
DL.VQI(0.01)
0.01
0 to 500
Downlink voice quality

indicator.
N/A
LossRatio(%)
0 to 1000
Downlink voice packet

loss rate.
N/A
DL.Delay(ms)
ms
0 to 65535
Average delay of
downlink voice packets
over the air interface.
N/A
UL Quality of Voice monitoring
Table 3-5 Results of UL Quality of Voice monitoring

Monitoring
Results
Unit
Value
Range
Description
Formula
Physical Cell
Identifier
N/A
0 to 503
Physical cell identifier of the serving

cell.
N/A
UL.VQI(0.01)
0.01
0 to 500
Uplink voice quality indicator.
N/A
UL.FER()
0 to
1000
Proportion of the number of uplink

lost and delayed voice packets to the
total uplink voice packets.
N/A
UL.LFE(times)
times
0 to 255
Maximum number of times when a

user's packets are consecutively lost
in the uplink.
N/A
UL.OutDelayR
atio()
0 to
1000
Proportion of uplink delayed voice

packets to the total uplink voice
packets.
N/A
Issue 07 (2013-11-30)

62
eNodeB
3.3 DL RSRP/RSRQ Monitoring

Reference signal received power (RSRP) and reference signal received quality (RSRQ)
indicate the received signal power and quality of UEs respectively. DL RSRP/RSRQ
Monitoring can be used to:
Calculate loss on the downlink to facilitate the analysis of drive test (DT) data.
Preliminarily detect and isolate network coverage problems.

None.
3.3.3 Parameters
Table 3-6 Parameters for DL RSRP/RSRQ monitoring
Parameter
Description
UEID Type
MMEc

STMSI.
mTMSI

STMSI.
Random Value

Random Value.
PLMN

respectively.
User Trace ID

Trace Reference No.
Monitor Period (ms)

480, 640, 1024, or 2048.
Issue 07 (2013-11-30)

63
eNodeB

Table 3-7 Results of DL RSRP/RSRQ monitoring
Parameter
Unit
Value Range
Description
Formula
ServCell PCI
N/A
0 to 503
Physical cell ID of a serving

cell.
N/A
ServCell
RSRP
dBm
-140 to -44
RSRP of a serving cell.
N/A
ServCell
RSRQ
dB
-19.5 to -3
RSRQ of a serving cell.
N/A
NeighborCell
PCI[n]
N/A
0 to 503
Physical cell ID of the nth

neighboring cell. n is an integer
from 1 to 8.
N/A
NOTE
This field specifies the sequence

for reporting the measurement
reports of neighboring cells. A
maximum of eight neighboring
cells are dynamically displayed.
NeighborCell
RSRP[n]
dBm
140 to 44
RSRP of the nth neighboring cell. n

is an integer from 1 to 8.
N/A
NOTE

NeighborCell
RSRQ[n]
dB
19.5 to 3
RSRQ of the nth neighboring cell. n

is an integer from 1 to 8.
N/A
NOTE

3.4 BLER Monitoring

This task is used to monitor the BLERs on each channel of the UE.

None.
Issue 07 (2013-11-30)

64
eNodeB
3.4.3 Parameters
Table 3-8 Parameters for BLER monitoring
Parameter
Description
UEID Type
It can be set to STMSI, Random Value, or Trace Reference

No.
MMEc

STMSI.
mTMSI

STMSI.
Random Value

Random Value.
PLMN

Trace Reference No. When this parameter is selected, MCC
and MNC specify the mobile country code and mobile network
code, respectively.
User Trace ID

Trace Reference No.
Monitor Period (ms)

200, 500, 1000, or 2000.
Test Item
It can be set to Init BLER, Pdcch BLER, or Resident BLER.

All items are monitored by default.
Init BLER
Table 3-9 Results of Init BLER monitoring

Parameter
Unit
Value
Range
Description
Formula
CA Property
N/A
N/A
Carrier aggregation
property of a user.
N/A
The result contains

Non CA, CA PCell
and CA SCell.
Physical Cell
Identifier
Issue 07 (2013-11-30)
N/A
0 to 503
Physical cell identifier

of the serving cell.

N/A
65
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Downlink
IBLER
0 to 1000
BLER of initial TB
transmission on a
PDSCH within a
monitoring period.
Total number of TBs that

fail to be initially
transmitted on the
PDSCH x 1000/Total
number of initially
transmitted TBs on the
PDSCH within the
monitoring period
Uplink
IBLER
0 to 1000
BLER of initial TB
transmission on a
PUSCH within a
monitoring period.
Total number of TBs that

fail to be initially
transmitted on the
PUSCH x 1000/Total
number of initially
PUSCH within the
monitoring period
Resident BLER
Table 3-10 Results of Resident BLER monitoring

Parameter
Unit
Value
Range
Description
Formula
CA Property
N/A
N/A
Carrier aggregation
property of a user.
N/A
The result contains

Non CA, CA PCell
and CA SCell.
Physical Cell
Identifier
N/A
0 to 503
Physical cell
identifier of the
serving cell.
N/A
Downlink
RBLER
0 to 1000
BLER of the last TB

retransmission on a
PDSCH within a
monitoring period.
Number of times TBs

that last fail to be
retransmitted on the
PDSCH x 1000/Total
number of initially
PDSCH within the
monitoring period
Issue 07 (2013-11-30)

66
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Uplink RBLER
0 to 1000
BLER of the last TB

retransmission on a
PUSCH within a
monitoring period.
Number of times TBs

that last fail to be
retransmitted on the
PUSCH x 1000/Total
number of initially
PUSCH within the
monitoring period
PDCCH BLER
Table 3-11 Results of PDCCH BLER monitoring

Parameter
Unit
Value
Range
Description
Formula
CA Property
N/A
N/A
Carrier
aggregation
property of a
user. The
N/A
result contains
Non CA, CA
PCell and CA
SCell.
Physical Cell
Identifier
N/A
0 to 503
Physical cell
identifier of the
serving cell.
N/A
PDCCH BLER
0 to 1000
BLER of
DLGRANT
decoding on a
PDCCH within
a monitoring
period.
Number of times
DLGRANTs decoded
incorrectly x 1000/Total
number of DLGRANTs sent
on a PDCCH
Issue 07 (2013-11-30)

The number of DLGRANTs

decoded incorrectly is the
number of DTXs that were
the feedback given to the
DLGRANTs sent on a
PDCCH.
67
eNodeB
3.5 Power Headroom Monitoring

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

None.
3.5.3 Parameters
Table 3-12 Parameters for power headroom monitoring
Parameter
Description
UEID Type
MMEc

STMSI.
mTMSI

STMSI.
Random Value

Random Value.
PLMN

respectively.
User Trace ID

Trace Reference No.
Monitor Period (ms)

200, 500, 1000, or 2000.

Table 3-13 Result of power headroom monitoring
Parameter
Unit
Value
Range
Description
Formula
CA Property
N/A
N/A
Carrier aggregation property of a

user. The result contains Non
CA, CA PCell and CA SCell.
N/A
Issue 07 (2013-11-30)

68
eNodeB
Physical Cell
Identifier
N/A
0 to 503

serving cell.
N/A
Power Headroom
dB
23 to +40
Power headroom last reported by

the UE.
N/A
For details about formula of

Power Headroom, see 3GPP TS
36.213, 36.321, and 36.133.
3.6 Quality of Channel Monitoring

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

During high-volume traffic, the monitoring data may be lost but services are not affected.
3.6.3 Parameters
Table 3-14 Parameters for quality of channel monitoring
Parameter
Description
UEID Type
MMEc

STMSI.
mTMSI

STMSI.
Random Value

Random Value.
PLMN

respectively.
User Trace ID

Trace Reference No.
Monitor Period (ms)

200, 500, 1000, or 2000.
Test Item
It can be set to CQI , ULSINR & UL DMRS RSRP or UL SRS

RSRP. All items are monitored by default.
Issue 07 (2013-11-30)

69
eNodeB
UL SINR & UL DMRS RSRP
Table 3-15 Results of UL SINR & UL DMRS RSRP monitoring

Parameter
Unit
Value Range
Description
Formula
CA Property
N/A
N/A
Carrier aggregation property

of a user. The result
N/A
contains Non CA, CA PCell

and CA SCell.
Physical Cell
Identifier
N/A
0 to 503

serving cell.
N/A
SINR
0.01 dB
12700 to
+12700
Average SINR for the full

bandwidth of the eNodeB
monitored.
N/A
UL DMRS
RSRP
0.01 dB
15000 to
3000
Uplink reference signal

received power.
N/A
CQI
Table 3-16 Results of CQI monitoring

Parameter
Unit
Value
Range
Description
Formula
CA Property
N/A
N/A
Carrier aggregation
property of a user. The
N/A
result contains Non CA,

CA PCell and CA SCell.
Physical Cell
Identifier
N/A
0 to 503

the serving cell.
N/A
UE Code
Count
Number
1 to 2
Number of transmitted
code words in the downlink
reported.
N/A
Effective
Len
ms
41 to 44
Valid length of the

aperiodic CQI for the full
bandwidth. This parameter
takes effect only when the
aperiodic CQI frequency
selection is configured.
N/A
Issue 07 (2013-11-30)

70
eNodeB
Parameter
Unit
Value
Range
Description
CQI
N/A
0 to 31
Five-bit value mapped to

the originally reported CQI
for the full bandwidth.
Code Index
N/A
0 to 3
Index of the UE codeword.
Formula
N/A
UL SRS RSRP
Table 3-17 Results of UL SRS RSRP

Parameter
Unit
Value Range
Description
Formula
CA Property
N/A
N/A
Carrier aggregation
property of a user.
N/A
The result contains

Non CA, CA PCell
and CA SCell.
Physical Cell
Identifier
N/A
0~503
Physical cell ID of a
serving cell.
N/A
ServCell
RSRP
0.01dBm
-15000 ~ -3000
RSRP of a serving
cell.
N/A
NeighborCel
l PCI[n]
N/A
0~503

to 8.
N/A
NOTE
This field specifies the

sequence for reporting
the measurement
reports of neighboring
cells. A maximum of
eight neighboring
cells are dynamically
displayed.
Issue 07 (2013-11-30)

71
eNodeB
Parameter
Unit
Value Range
Description
NeighborCel
l RSRP
0.01dBm
-15000 ~ -3000

to 8.
Formula
NOTE
This field specifies

the sequence for
reporting the
measurement
reports of
neighboring cells. A
maximum of eight
neighboring cells
are dynamically
displayed.
This task is used to monitor the scheduling information sent from the UE, including the
number of scheduling requests (SRs), the status of each data buffer area, and the number of
GAPs, DRXs, and TTIs within a monitoring period.
The status of each data buffer area is not the BSR indexes reported by the UE, but the status
of the buffer area corresponding to different logical channels maintained for the UE and
mapped to the eNodeB based on the BSRs reported by the UE. The eNodeB maintains four
data buffer areas for each UE. The four data buffer areas are BSR[0], BSR[1], BSR[2], and
BSR[3].

None.
3.6.7 Parameters
Table 3-18 Parameters for scheduling monitoring
Parameter
Description
UEID Type
MMEc

STMSI.
mTMSI

STMSI.
Issue 07 (2013-11-30)

72
eNodeB
Parameter
Description
Random Value

Random Value.
PLMN

respectively.
User Trace ID

Trace Reference No.
Monitor Period (ms)

200, 500, 1000, or 2000.
Test Item
It can be set to Percentage of DRX activity timer in DRX timer,

UL BSR of Service or UL SR of Service. Both items are
monitored by default.
Issue 07 (2013-11-30)

73
eNodeB
UL SR of Service
Table 3-19 Results of UL SR of Service monitoring

Parameter
Unit
Value Range
Description
Formula
CA Property
N/A
N/A

N/A

and CA SCell.
Physical Cell
Identifier
N/A
0 to 503

serving cell.
N/A
Number of SRs
Number
0 to 64000
Number of SRs reported by

the UE to the eNodeB within
a monitoring period. When
the UE needs to perform an
uplink data transfer but there
is no uplink resources
available, the UE must send
an SR to require the eNodeB
to grant uplink data transfer
permission.
N/A
For details, see 3GPP TS

36.321.
UL BSR of Service
Table 3-20 Results of UL BSR of Service monitoring

Parameter
Unit
Value Range
Description
Formula
CA Property
N/A
N/A
Carrier aggregation property of

a user. The result contains
Non CA, CA PCell and CA
SCell.
N/A
Physical Cell
Identifier
N/A
0 to 503

serving cell.
N/A
Issue 07 (2013-11-30)

74
eNodeB
Parameter
Unit
Value Range
Description
Formula
Byte Length of
LCG BS[n]
Bit
0 to 150000
Buffered data volume of the

LCG, which is represented
with BSR[n] (n = {0 to 3}),
indicating the volume of user
data to be scheduled in a butter
area. After reported by the UE,
LongBsr, TruncateBsr, and
ShortBsr are mapped by the
eNodeB into BSR[0] to
BSR[3]. After received the
data from the UE, the eNodeB
subtracts corresponding data in
BSR[n].
N/A
For details, see 3GPP TS

36.321.
Percentage of DRX activity timer in DRX timer
Table 3-21 Results of Percentage of DRX activity timer in DRX timer monitoring
Parameter
Unit
Value
Range
Description
Formula
CA Property
N/A
N/A

user. The result contains Non
CA, CA PCell and CA SCell.
N/A
Physical Cell
Identifier
N/A
0 to 503

serving cell.
N/A
TTIs in GAP
State
Number
0 to
4294967295
Number of accumulated TTIs in

the call gapping (GAP) state
during the monitoring period.
N/A

TTIs in DRX
State
Number
0 to
4294967295
Number of accumulated TTIs in

the DRX state during the
monitoring period.
N/A

Number of TTI
Issue 07 (2013-11-30)
Number
0 to
4294967295
Number of accumulated TTIs

between the establishment and the
release of an L2 case.

N/A
75
eNodeB
3.7 RLC Data Stream Monitoring

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

None.
3.7.3 Parameters
Table 3-22 Parameters for RLC data stream monitoring
Parameter
Description
UEID Type
MMEc

STMSI.
mTMSI

STMSI.
Random Value

Random Value.
PLMN

respectively.
User Trace ID

Reference No.

Table 3-23 Result of RLC data stream monitoring
Parameter
Unit
Value Range
Description
Formula
Physical Cell
Identifier
N/A
0 to 503

serving cell.
N/A
DRB No.
N/A
1 to 8
Number of the DRB.
N/A
Issue 07 (2013-11-30)

76
eNodeB
Parameter
Unit
Value Range
Description
Formula
RLC Buffer
Length
Byte
0~3000000
Data stream of the RLC

SDUs to be sent on the data
radio bearer (DRB) from the
downlink buffer area at the
RLC layer when monitoring
results are reported.
N/A
3.8 Throughput Monitoring

This task is used to view the uplink and downlink throughput of the UE and the uplink and
downlink throughput on each bearer in real time. Based on the monitoring results, whether the
data transmission of the eNodeB or UE is proper can be determined.

None.
3.8.3 Parameters
Table 3-24 Parameters for throughput monitoring
Parameter
Description
UEID Type
MMEc
It must be configured when the UEID Type parameter is set to STMSI.
mTMSI
It must be configured when the UEID Type parameter is set to STMSI.
Random Value
It must be configured when the UEID Type parameter is set to Random

Value.
PLMN

Reference No. When this parameter is selected, MCC and MNC specify
the mobile country code and mobile network code, respectively.
User Trace ID

Reference No.
Monitor Period
(ms)

500, 1000, or 2000.
Test Item
It can be set to Throughput of MAC or Throughput of RLC. Both

items are monitored by default.
Issue 07 (2013-11-30)

77
eNodeB
Throughput of RLC
Table 3-25 Results of RLC throughput monitoring

Parameter
Unit
Value
Range
Description
Formula
CA Property
N/A
N/A
Carrier aggregation
N/A
result contains Non

CA, CA PCell and CA
SCell.
Physical Cell
Identifier
N/A
0 to 503

N/A
DRB No.
N/A
1to 8
Number of the DRB.
N/A
Downlink
RLC
Throughput
bps
0 to
300000000
Total throughput of the

downlink RLC SDUs
sent on the DRB at the
RLC layer within a
monitoring period.
(Downlink RLC
throughput on the
RLC logical
channels (byte) x 8)
x 1000/Monitoring
period (ms)
Uplink RLC
Throughput
bps
0 to
300000000
Total throughput of the

uplink RLC SDUs
received on the DRB at
the RLC layer within a
monitoring period.
(Uplink RLC
throughput on the
RLC logical
channels (byte) x 8)
x 1000/Monitoring
period (ms)
Throughput of MAC
Table 3-26 Results of MAC throughput monitoring

Parameter
Unit
Value Range
Description
Formula
CA Property
N/A
N/A
Carrier aggregation
N/A
result contains Non

CA, CA PCell and CA
SCell.
Physical Cell
Identifier
Issue 07 (2013-11-30)
N/A
0 to 503


N/A
78
eNodeB
Parameter
Unit
Value Range
Description
Formula
Downlink MAC
Throughput
bps
0 to
300000000
User-level downlink
MAC throughput(that
is, traffic from the
MAC layer to the
physical layer,
including the MAC
header fields) within a
monitoring period.
User-level
downlink MAC
throughput within
a monitoring
period
Uplink MAC
Throughput
bps
0 to
300000000
User-level uplink
MAC throughput (that
is, traffic from the
MAC layer to the RLC
layer, excluding the
MAC header
fields)within a
monitoring period.
(Uplink MAC
throughput (byte)
x 8) x
1000/Monitoring
period (ms)
3.9 AQM Monitoring

This task is used to monitor the number of discarded packets related to the active queue
management (AQM) algorithm and the number of RLC SDUs to be sent on the DRB from the
downlink RLC buffer area. Based on the monitoring results, whether the data transmission of
the eNodeB or UE is proper can be determined.

None
3.9.3 Parameters
Table 3-27 Parameters for AQM monitoring
Parameter
Description
UEID Type
MMEc

STMSI.
mTMSI

STMSI.
Random Value

Random Value.
Issue 07 (2013-11-30)

79
eNodeB
Parameter
Description
PLMN

respectively.
User Trace ID

Reference No.
Monitor Period
(ms)

500, 1000, or 2000.
Test Item
It can be set to DL RLC buffer length of eNB or Percentage of

AQM discard package. Both items are monitored by default.

Table 3-28 Results of AQM monitoring
Parameter
Unit
Value
Range
Description
Formula
Physical Cell
Identifier
N/A
0 to 503

serving cell.
N/A
Number of Packets
in RLC Buffer
Packet
0 to 20000
Number of RLC SDUs to be sent

on the DRB from the downlink
RLC buffer area at the end of a
monitoring period.
N/A
Number of
Discarded Packets
Packet
0 to 20000
Number of SDUs discarded by

AQM.
N/A
3.10 UL Power Control Monitoring

This task is used to monitor the necessary information about uplink power control when the
switch for uplink power control is turned on or off. This enables users to obtain the
information about the power adjustment when the switch for uplink power control is turned
on or off.

None.
Issue 07 (2013-11-30)

80
eNodeB
3.10.3 Parameters
Table 3-29 Parameters for UL power control monitoring
Parameter
Description
UEID Type
It can be set to STMSI, Random Value, or Trace Reference

No.
MMEc

STMSI.
mTMSI

STMSI.
Random Value

Random Value.
PLMN

Trace Reference No. When this parameter is selected, MCC
and MNC specify the mobile country code and mobile network
code, respectively.
User Trace ID

Trace Reference No.
Monitor Period (ms)

200, 500, 1000, or 2000.
PUCCH SINR&RSRP
Table 3-30 Result of PUCCH SINR&RSRP monitoring

Parameter
Unit
Value Range
Description
Formula
CA Property
N/A
N/A
Carrier aggregation
N/A

Physical Cell
Identifier
N/A
0 to 503

the serving cell.
N/A
PUCCH SINR
0.01 dB
1500 to
+
The SINR value of the

PUCCH.
N/A
Issue 07 (2013-11-30)

81
eNodeB
Parameter
Unit
Value Range
Description
Formula
PUCCH RSRP
dBm
150 to
The RSRP of a PUCCH is

measured after each time of
PUCCH measurement. In
each report period, the
RSRP values in different
formats are converted to
that in Formatla format.
N/A
3.11 DL Power Control Monitoring

This task is used to monitor the necessary information about downlink power control when
the switch for downlink power control is turned on or off. This enables users to obtain the
power adjustment when the switch for downlink power control is turned on or off.

None.
3.11.3 Parameters
Table 3-31 Parameters for DL power control monitoring
Parameter
Description
UEID Type
MMEc

STMSI.
mTMSI

STMSI.
Random Value

Random Value.
PLMN

respectively.
User Trace ID

Trace Reference No.
Monitor Period (ms)

200, 500, 1000, or 2000.
Test Item
It can be set to PUCCH SINR&RSRP. It is monitored by default.
Issue 07 (2013-11-30)

82
eNodeB
PDSCH UE
Table 3-32 Results of PDSCH UE monitoring

Parameter
Unit
Value
Range
Description
Formula
CA Property
N/A
N/A

N/A

and CA SCell.
Physical Cell
Identifier
N/A
0 to 503

serving cell.
N/A
PDSCH PA
0.01 dB
600 to
+300
Power offset between each

resource element (RE) on the
PDSCH and the pilot when
reported.
N/A
PDSCH Maximum
Number of
Transmissions
Number
0 to 28
Maximum number of
transmissions on the
PDSCH.
N/A
PDSCH IBLER
Target
0 to 1000
Target BLER in the initial

transmission during the
semi-static PDSCH power
control. It is set by running
MML commands.
N/A
PHICH UE
Table 3-33 Results of PHICH UE monitoring

Parameter
Unit
Value
Range
Description
Formula
CA Property
N/A
N/A
Carrier aggregation
N/A

Physical Cell
Identifier
N/A
0 to 503

the serving cell.
N/A
Power Offset
of PHICH
0.01 dB
1500 to
+2000
Power offset between each

RE on the PHICH and the
pilot when monitoring
N/A
Issue 07 (2013-11-30)

83
eNodeB
PDCCH UE
Table 3-34 Results of PDCCH UE monitoring

Parameter
Unit
Value Range
Description
Formula
CA Property
N/A
N/A
Carrier aggregation
N/A

Physical Cell
Identifier
N/A
0 to 503

the serving cell.
N/A
Power Offset of
PDCCH
0.01 dB
1500 to +2000
Offset between the power

for transmitting each RE
on the PDCCH and the
pilot power when
reported.
N/A
TTI
ms
0 to 4294967295
TTI for the PDCCH

power transmitted at the
MAC layer.
N/A
3.12 ICIC (User) Monitoring

This task is used to monitor the user properties and neighboring cell information in the uplink
ICIC to obtain the operating status of the uplink ICIC.

None.
3.12.3 Parameters
Table 3-35 Parameters for uplink ICIC monitoring
Parameter
Description
UEID Type
MMEc

STMSI.
mTMSI

STMSI.
Issue 07 (2013-11-30)

84
eNodeB
Random Value

Random Value.
PLMN

respectively.
User Trace ID

Trace Reference No.
Monitor Period (ms)

200, 500, 1000, or 2000.
Test Item
It can be set to User DL Property information, User PDSCH

RB information, User PUSCH RB information, or User UL
Property information. All items are monitored by default.
User downlink property
Table 3-36 Results of user downlink property monitoring

Parameter
Unit
Value Range
Description
Formula
CA Property
N/A
N/A

of a user. The result contains
SCell.
N/A
Physical Cell
Identifier
N/A
0 to 503

serving cell.
N/A
DL User ICIC
Property
N/A
N/A
User property. It includes the

CEUs, cell center users, and
users at full frequency bands.
N/A
PDSCH RB Usage
Table 3-37 Results of PDSCH RB usage monitoring

Parameter
Unit
Value
Range
Description
Formula
CA Property
N/A
N/A

SCell.
N/A
Physical Cell
Identifier
N/A
0 to 503

serving cell.
N/A
Issue 07 (2013-11-30)

85
eNodeB
Parameter
Unit
Value
Range
Description
Formula
PDSCH RB Num
N/A
N/A
Number of RBs used at the

PDSCH.
N/A
PUSCH RB usage
Table 3-38 Results of PUSCH RB usage monitoring

Parameter
Unit
Value
Range
Description
Formula
CA Property
N/A
N/A

user. The result contains Non CA,
N/A
Physical Cell
Identifier
N/A
0 to 503

cell.
N/A
PDSCH RB
Num
N/A
N/A
Number of RBs used at the PUSCH.
N/A
User uplink property
Table 3-39 Results of user uplink property monitoring

Parameter
Unit
Value
Range
Description
Formula
CA Property
N/A
N/A

user. The result contains Non CA,
N/A
Physical Cell
Identifier
N/A
0 to 503

cell.
N/A
UL User ICIC
Property
N/A
N/A
User property. It includes the CEUs,

cell center users, and users at full
frequency bands.
N/A
3.13 MCS Count Monitoring

This task is used to monitor the number of scheduling attempts and number of RBs in
scenarios of different MCSs. The eNodeB uses different MCSs to schedule UEs in different
channel situations. The step of the MCS ranges from steps 0 through 31. The number of
scheduling attempts indicates the number of scheduling attempts with a specific MCS step,
Issue 07 (2013-11-30)

86
eNodeB
and the number of RBs indicates the total number of RBs scheduled using a specific MCS
step.

None.
3.13.3 Parameters
Table 3-40 Parameters for MCS statistic monitoring
Parameter
Description
UEID Type
MMEc

STMSI.
mTMSI

STMSI.
Random Value

Random Value.
PLMN

respectively.
User Trace ID

Trace Reference No.
Monitor Period (ms)
Interval of reporting monitoring results. It can be set to 1000 or

2000.
Test Item
It can be set to DL MCS or UL MCS. Both items are monitored

by default.
DL MCS
Table 3-41 Results of DL MCS monitoring

Parameter
Unit
Value Range
Description
Formula
CA Property
N/A
N/A

SCell.
N/A
Physical Cell
Identifier
N/A
0 to 503

serving cell.
N/A
Issue 07 (2013-11-30)

87
eNodeB
Parameter
Unit
Value Range
Description
Formula
DLSCH Code
0 Num[n]
Number
0 to 2000
Total number (n) of scheduling

on codeword 0 in the downlink
period.
N/A
The value n indicates the MCS

order, and ranges from 0 to 31.
DLSCH Code
0 RBs[n]
Number
0 to 200,000
Total number (n) of RBs on

codeword 0 in the downlink
period.
N/A

DLSCH Code
1 Num[n]
Number
0 to 2000
Total number (n) of scheduling

on codeword 1 in the downlink
period.
N/A

DLSCH Code
1 RBs[n]
Number
0 to 200,000
Total number (n) of RBs on

codeword 1 in the downlink
period.
N/A

order and ranges from 0 to 31.
UL MCS
Table 3-42 Results of UL MCS monitoring

Parameter
Unit
Value Range
Description
Formula
CA Property
N/A
N/A

of a user. The result contains
SCell.
N/A
Physical Cell
Identifier
N/A
0 to 503

serving cell.
N/A
ULSCH
Num[n]
Number
0 to 2000
Total number (n) of uplink

scheduling within a
monitoring period.
N/A
The value n indicates the

MCS order, and its value
range is from 0 to 31.
Issue 07 (2013-11-30)

88
eNodeB
ULSCH
RBs[n]
Number
0 to 200,000
Total number (n) of RBs in

the uplink scheduling within
N/A
The value n indicates the

MCS order, and its value
range is from 0 to 31.
3.14 Multi-User BF (User) Monitoring

This task is used to monitor the RB usage by common UEs paired with UEs of independent or
combined scheduling on the SFN, which helps to locate MUBF algorithm faults.

None.
3.14.3 Parameters
Table 3-43 Parameters for multi-user BF (user) monitoring
Parameter
Description
UEID-MME
MME serving a user.
UEID-TMSI
TMSI to be monitored.
Trace Reference
No.
Trace reference number to be monitored.
Monitor Period (ms)

200, 500, 1000, or 2000.
Test Type Bitmap
Bit 0 and bit 1 respectively represent Indep-Indep MUBF pairing

and Indep-Joint MU-BF pairing. By default, all the corresponding
items are monitored.

Table 3-44 Results of multi-user BF (user) monitoring
Parameter
Unit
Value
Range
Description
Formula
Physical Cell
Identifier
N/A
0 to
503

cell.
N/A
Issue 07 (2013-11-30)

89
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Indep-Indep
Number of
successful
MUBF pairing
RB
Number
0 to
1000
Number of RBs used by common

UEs that have been successfully
paired using MUBF with UEs of
independent scheduling. It is
number of RBs used by a UE at each
TTI and calculating the average
number at the end of the monitoring
period.
N/A
Indep-Joint
Number of
successful
MUBF pairing
RB
Number
0 to
1000
Number of RBs used by common

UEs that have been successfully
paired using MUBF with UEs of
combined scheduling. It is obtained
by accumulating the number of RBs
calculating the average number at the
end of the monitoring period.
N/A
3.15 SFN Detection Monitoring

This task is used to monitor the RRU usage for uplink and downlink transmission of a UE and
the link quality on the SFN, which helps to verify and evaluate the SFN function.

None.
3.15.3 Parameters
Table 3-45 Parameters for SFN detection monitoring
Parameter
Description
UEID-MME
MME serving a user.
UEID-TMSI
Trace Reference
No.
Trace reference number to be monitored.
Monitor Period (ms)

200, 500, 1000, or 2000.
Issue 07 (2013-11-30)

90
eNodeB
Parameter
Description
Test Type Bitmap
Bit 0 and bit 1 respectively represent UL RRU Detect and DL

RRU Detect. By default, the items corresponding to UL RRU
Detect are monitored. All items are monitored by default.

Table 3-46 Results of SFN detection monitoring
Parameter
Unit
Value Range
Description
Formula
UL User
Mode
N/A
Joint Sch User

and Independent
Sch User
User attributes can be queried

on real time to determine the
scheduling mode of the user for
uplink transmission.
N/A
DL User
Mode
N/A
Joint Sch User

and Independent
Sch User
User attributes can be queried

on real time to determine the
scheduling mode of the user for
downlink transmission.
N/A
Physical
Cell
Identifier
N/A
0 to 503

serving cell.
N/A
UL RRU
eNodebId
N/A
0 to 1048575
eNodeB ID of the RRU used for

N/A
UL RRU
Cabinet No.
N/A
0 to 62

houses the RRU used for uplink
transmission.
N/A
UL RRU
Subrack No.
N/A
4 to 5 and 60 to
254

houses the RRU used for uplink
transmission.
N/A
UL RRU
Slot No.
N/A
0 to 8

the RRU used for uplink
transmission.
N/A
UL RRU
Flag
N/A
Target RRU and

Work RRU
It indicates that the RRU used

for uplink transmission is a
target RRU or a working RRU.
N/A
Uplink SRS
RSRP
dBm
141 to 43
Uplink RSRP of sounding

reference signals (SRSs)
measured by all the RRUs on
the SFN.
N/A
Uplink
SRS&DMR
S SINR
dB
20 to +60
Uplink SINR of the user.
N/A
Issue 07 (2013-11-30)

91
eNodeB
Parameter
Unit
Value Range
Description
Formula
Uplink
DMRS
SINR
dB
20 to +60
DMRS SINR measured by all

the RRUs on the SFN.
N/A
DL RRU
eNodebId
N/A
0 to 1048575
eNodeB ID of the RRU used for

N/A
DL RRU
Cabinet No.
N/A
0 to 62

houses the RRU used for
N/A
DL RRU
Subrack No.
N/A
4 to 5 and 60 to
254

N/A
DL RRU
Slot No.
N/A
0 to 8

the RRU used for downlink
transmission.
N/A
DL RRU
Flag
N/A
Target RRU and

Work RRU
It indicates that the RRU used

for downlink transmission is a
target RRU or a working RRU.
N/A
3.16 Cell Combination Monitoring

This task is used to monitor the RRU usage and link transmission quality for the uplink and
downlink in a cell combination scenario. This monitoring task helps to verify and evaluate the
cell combination function.

None.
3.16.3 Parameters
Table 3-47 Parameters for cell combination monitoring
Parameter
Description
MMEc
MME serving a user.
mTMSI
Monitor Period (ms)

2000.
Issue 07 (2013-11-30)

92
eNodeB
Parameter
Description
Test Items
Either DL Cell Combination RRU Detect or UL Cell

Combination RRU Detect can be selected for monitoring. UL Cell
Combination RRU Detect is selected by default.

Table 3-48 Results of cell combination monitoring
Parameter
Unit
Value Range
Description
Formula
UL User Mode
N/A
Joint Sch User

and
Independent
Sch User
User attributes can be

queried on real time to
determine the scheduling
mode of the user for uplink
transmission.
N/A
DL User Mode
N/A
Joint Sch User

and
Independent
Sch User
User attributes can be

queried on real time to
determine the scheduling
mode of the user for
N/A
Physical Cell
Identifier
N/A
0 to 503

the serving cell.
N/A
UL RRU eNodebId
N/A
0 to 1048575
eNodeB ID of the RRU

used for uplink
transmission.
N/A
UL RRU Cabinet
No.
N/A
0 to 62

N/A
UL RRU Subrack
No.
N/A
4 to 5 and 60 to
254
Number of the subrack

that houses the RRU used
for uplink transmission.
N/A
UL RRU Slot No.
N/A
0 to 8
Number of the slot that

N/A
UL RRU Flag
N/A
Target RRU
and Work RRU
It indicates that the RRU

used for uplink
transmission is a target
RRU or a working RRU.
N/A
Uplink SRS RSRP
dBm
-141 to -43
Uplink RSRP of SRSs

measured by all the RRUs
in a cell combination
scenario.
N/A
Uplink
SRS&DMRS SINR
dB
-20 to 60
Uplink SINR of the user.
N/A
Issue 07 (2013-11-30)

93
eNodeB
Parameter
Unit
Value Range
Description
Formula
Uplink DMRS SINR
dB
-20 to 60
DMRS SINR measured by

all the RRUs in a cell
combination scenario.
N/A
DL RRU eNodebId
N/A
0 to 1048575
eNodeB ID of the RRU

used for downlink
transmission.
N/A
DL RRU Cabinet
No.
N/A
0 to 62

N/A
DL RRU Subrack
No.
N/A
4 to 5 and 60 to
254

that houses the RRU used
for downlink transmission.
N/A
DL RRU Slot No.
N/A
0 to 8
Number of the slot that

N/A
DL RRU Flag
N/A
Target RRU
and Work RRU
It indicates that the RRU

used for downlink
transmission is a target
RRU or a working RRU.
N/A
Issue 07 (2013-11-30)

94
eNodeB
4 Device Monitoring
Device Monitoring
4.1 CPRI BER Monitoring

This task is used to monitor the bit error rate (BER) on the common public radio interface
(CPRI) link to determine whether the fault on the eNodeB is caused by the optical fiber or the
BBU or RRU.

None.
4.1.3 Parameters
Table 4-1 Parameters for CPRI BER monitoring
Parameter
Description
Upper Cabinet NO.
The cabinet number of the upper-level node at the other end of the
monitored link.
NOTE
The upper-level node mentioned in this table is the node connected to the
link towards the BBU.
Upper Subrack NO.
The subrack number of the upper-level node at the other end of the
monitored link.
Upper Slot No.
The slot number of the upper-level node at the other end of the
monitored link.
Upper Port No.
The port number of the upper-level node at the other end of the
monitored link. This parameter is mandatory if the upper-level node
is a BBU. CPRI BER monitoring supports cascaded RRUs. This
parameter is optional if the upper-level node and lower-level node
at the other end of the monitored link are RRUs.
Issue 07 (2013-11-30)

95
eNodeB
4 Device Monitoring
Parameter
Description
Lower Cabinet No.
The cabinet number of the lower-level node at the other end of the
monitored link.
NOTE
The lower-level node mentioned in this table is the node connected to the
link towards the lowest-level RRU.
Lower Subrack No.
The subrack number of the lower-level node at the other end of the
monitored link.
Lower Slot No.
The slot number of the lower-level node at the other end of the
monitored link.

Table 4-2 Results of CPRI BER monitoring
Parameter
Unit
Value Range
Description
Formula
Uplink BER
e^(-9)
0 to 1000000000
Uplink BER in the test second
N/A
NOTE
Because LBBPc does not support

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

second.
N/A
BER
Threshold
e^(-9)
0 to 1000000000
BER threshold
N/A
NOTE
If the actual measured downlink

and uplink BER is greater than
the threshold, the link quality
may be poor.
4.2 CPU Usage Monitoring

This task is used to monitor the CPU usage of each board of an eNodeB or the CPU usage of
an eNodeB.

None.
Issue 07 (2013-11-30)

96
eNodeB
4 Device Monitoring
4.2.3 Parameters
Table 4-3 Parameters for CPU usage monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the board/eNodeB is located.
Subrack No.
Number of the subrack where the board/eNodeB is located.
Slot No.
Number of the slot where the board/eNodeB is located.
Monitor Period
(Seconds)
Interval of reporting monitoring results. It is set to the fixed value 5.

Table 4-4 Results of CPU usage monitoring
Parameter
Unit
Value Range
Description
Formula
Board No.
N/A
N/A
The board number is

displayed as follows:
N/A
Cabinet No.: Subrack No.:

Slot No.
CPU No.
N/A
N/A
The default CPU number is 0.
N/A
Type
N/A
N/A
The CPU type is as follows:
N/A
CPU Usage
0 to 100
CPU.
DSP.
Slave CPU.
CPU usage when monitoring

N/A
4.3 RRU/RFU/BRU Output Power Monitoring

This task is used to monitor the remote radio unit (RRU/RFU/BRU) output power.

None.
Issue 07 (2013-11-30)

97
eNodeB
4 Device Monitoring
4.3.3 Parameters
Table 4-5 Parameters for RRU/RFU/BRU Output Power monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the board for RRU/RFU/BRU

Output Power monitoring is located.
Subrack No.
Number of the subrack where the board for RRU/RFU/BRU

Output Power monitoring is located.
Slot No.
Number of the slot where the board for RRU/RFU/BRU Output

Power monitoring is located.
Monitor Period (ms)

2000, or 3000.

Table 4-6 Results of RRU/RFU/BRU Output Power monitoring
Parameter
Unit
Value Range
Description
Formula
Index of TX
N/A
0 to 7
Index of TX channel.
N/A
If only 0 is displayed,
the RRU supports one
carrier.
N/A
If both 0 and 1 are

displayed, the
RRU/RFU supports
two carriers.
NOTE
0 and 1 for
BTS3202Es and
BTS3203Es.
Index of Carrier
N/A
0 to 1
NOTE
0 for BTS3202Es
and BTS3203Es.
TX Freq of TX
Carrier[n]
N/A
The actual value

depends on the
working frequency
band of the
monitored RF
module.
Downlink frequency of a
carrier.
N/A
Output power of
TX Carrier[n]
0.1 dBm
-200 to -1, and
Output power of a
carrier.
N/A
0 to 1000
NOTE
0 to 370 for
BTS3202Es and
BTS3203Es.
Issue 07 (2013-11-30)

98
eNodeB
4 Device Monitoring
Parameter
Unit
Value Range
Description
Formula
Mode
N/A
LTE-FDD, and
LTE-TDD
Working mode of the

board to be monitored.
N/A
Output Power
0.1 dBm
-200 to -1, and 0 to

1000
Output power of a TX
channel.
N/A
NOTE
0 to 370 for
BTS3202Es and
BTS3203Es.

This task is used to monitor board or eNodeB temperature.

None.
4.4.3 Parameters
Table 4-7 Parameters for temperature monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the board/eNodeB for board

temperature monitoring is located.
Subrack No.
Number of the subrack where the board/eNodeB for board

temperature monitoring is located.
Slot No.
Number of the slot where the board/eNodeB for board temperature

monitoring is located.
Monitor Period
(ms)

or 3000.
Save File
The Save File check box is selected by default, and monitoring

results are automatically saved in the default path. The file name, file
format, and save path can be set.
NOTE
This parameter is available only on the LMT.
Issue 07 (2013-11-30)

99
eNodeB
4 Device Monitoring

Table 4-8 Results of board temperature monitoring
Monitoring
Results
Unit
Value
Range
Description
Formula
Board Temperature
-100 to 200
Board temperature.
N/A
Power amplifier
temperature.
N/A
0x7FFF:
Invalid
values are not
displayed.
PA Temperature
-100 to 200
0x7FFF:
Invalid
values are not
displayed.
Branch Index
N/A
0 to 1
Index of PA branch. This

monitoring item is available
only on the M2000.
N/A
Number of PA
Number
1 to 8
Number of power
amplifiers. This monitoring
item is available only on
the LMT.
N/A
Temperature of power
amplifier branches when
multiple power amplifiers
are available in the RRU or
RFU.
N/A
NOTE
1 and 2 for
BTS3202Es
and
BTS3203Es.
PA branch
Temperature
100 to 200
0x7FFF:
Invalid
values are not
displayed.
4.5 Clock Quality Test Monitoring

This task is used to collect the phase offset data of non-packet-based clocks to facilitate fault
diagnosis. Note that clocks complying with IEEE 1588 V2 or clock over IP are packet-based.

None.
Issue 07 (2013-11-30)

100
eNodeB
4 Device Monitoring
4.5.3 Parameters
Table 4-9 Parameters for clock quality test monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the board/eNodeB for clock quality

Subrack No.
Number of the subrack where the board/eNodeB for clock quality

Slot No.
Number of the slot where the board/eNodeB for clock quality

Test Type
Type of clock quality monitoring. It can be set to Frequency

Discrimination or Phase Discrimination.
Report
Period(Seconds)
Interval of reporting monitoring results. This parameter must be set to

1.

Table 4-10 Results of clock quality monitoring
Parameter
Unit
Value Range
Description
Formula
Cabinet No.
N/A
0 to 7
Number of the
cabinet where the
board whose
monitoring results
are reported is
located.
N/A
Subrack No.
N/A
0 to 1
Number of the
subrack where the
board whose
monitoring results
are reported is
located.
N/A
Slot No.
N/A
0 to 7
Number of the slot

where the board
whose monitoring
results are reported is
located.
N/A
TestResultT
ype
N/A
Frequency
discrimination
Test result types.
N/A
Phase
discrimination
Issue 07 (2013-11-30)

101
eNodeB
4 Device Monitoring
Parameter
Unit
Value Range
Description
Formula
Count
Value
Frequency
discrimination:
ppb
Frequency
discrimination:
5000 to 5000
N/A
Phase
discrimination: ns
Phase
discrimination:
200000 to
200000
Frequency
discrimination value
or phase
discrimination value.
4.6 IP Clock Data Collection Monitoring

This task is used to collect network jitter data of IP clocks. This helps locate faults and find
out the alarm reporting cause. Causes for reporting reference clockrelated alarms include
jitter, excessive frequency deviation, and excessive phase offset.

None.
4.6.3 Parameters
Table 4-11 Parameters for IP clock data collection monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the board/eNodeB for IP clock data

collection monitoring is located.
Subrack No.
Number of the subrack where the board/eNodeB for IP clock data

Slot No.
Number of the slot where the board/eNodeB for IP clock data

Report
Period(Seconds)
Interval of reporting monitoring results. This parameter must be set to

1.
Issue 07 (2013-11-30)

102
eNodeB
4 Device Monitoring

Table 4-12 Results of IP clock data collection monitoring
Parameter
Unit
Value
Range
Description
Formula
Tp1 Max QoS Value
ns
263 to
2631
Maximum delay per second for

transmitting packets from the
clock server to the eNodeB
N/A
Tp1 Min QoS Value
ns
263 to
2631
Minimum delay per second for

clock server to the eNodeB
N/A
Tp2 Max QoS Value
ns
263 to
2631
Maximum delay per second for

eNodeB to the clock server
N/A
Tp2 Min QoS Value
ns
263 to
2631
Minimum delay per second for

eNodeB to the clock server
N/A

This task is used to monitor RRU/RFU output power.

None.
4.7.3 Parameters
Table 4-13 Parameters for RRU/RFU output power monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the board for output power monitoring
is located.
Subrack No.
Number of the subrack where the board for output power monitoring
is located.
Slot No.
Number of the slot where the board for output power monitoring is
located.
Monitor Period
(ms)

or 3000.
Issue 07 (2013-11-30)

103
eNodeB
4 Device Monitoring
Parameter
Description
Save File


Table 4-14 Results of RRU/RFU output power monitoring
Parameter
Unit
Value Range
Description
Formula
Cabinet No.
N/A
0 to 62
Number of the cabinet

where the board whose
reported is located.
N/A
NOTE
BTS3202Es and
BTS3203Es do not
support this monitoring
item.
Subrack No.
N/A
4 to 5, 60 to 254

N/A
NOTE
BTS3202Es and
BTS3203Es do not
item.
Slot No.
N/A
0 to 8
Number of the slot

N/A
NOTE
BTS3202Es and
BTS3203Es do not
item.
Monitor Period
(ms)
ms
1000, 2000, 3000
Interval of reporting
monitoring results.
N/A
Output power of
Tx Freq[n]
(0.1dBm)
Mode:LTE-FDD
0.1 dBm
[1800, 1999]:
corresponding to
[200, 1]
Output power of a
TX[n] channel, in
which n can be set to 0
or 1.
N/A
Issue 07 (2013-11-30)
0xFFFF: invalid
value, which is not
displayed in GUI.

104
eNodeB
4 Device Monitoring
Parameter
Unit
Value Range
Description
Formula
TX branch Output
power of TX[n]
0.1 dBm
[1800..1999]:
corresponding to
[200..1].
Output power of a
TX[n] channel, in
which n can be set to 0
or 1.
N/A
0xFFFF: invalid
value, which is not
displayed in GUI.

This task is used to detect the external interference to the RRU, RFU, or BRU.

Services in cells served by the RRU, RFU, or BRU are interrupted during the test.
4.8.3 Parameters
Table 4-15 Parameters for uplink frequency scan monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the RRU, RFU, or BRU for uplink
frequency scanning is located.
Subrack No.
Number of the subrack where the RRU, RFU, or BRU for uplink
Slot No.
Number of the slot where the RRU, RFU, or BRU for uplink
Start RF
Frequency(200kHz)
Start RF frequency in uplink frequency scanning. It can be set to

4130, 4410, 8560, 9260, 9610, or 12510. The default value is 9610.
End RF
Frequency(200kHz)
End RF frequency in uplink frequency scanning. It can be set to

4235, 4565, 8915, 9540, 9890, or 12840. The default value is 9890.
Scanning Frequency
Interval(200kHz)
Frequency interval in uplink frequency scanning.
Scanning Time
Interval(0.1s)
Interval in uplink frequency scanning.
Save File

results are automatically saved in the default path. The file name,
file format, and save path can be set.
Issue 07 (2013-11-30)

105
eNodeB
4 Device Monitoring

Table 4-16 Results of uplink frequency scan monitoring
Monitoring
Results
Unit
Value
Range
Description
Formula
Cabinet No.
N/A
0 to 62
Number of the cabinet where the

board whose monitoring results are
N/A
Subrack No.
N/A
4 to 5, 60
to 254
Number of the subrack where the

N/A
Slot No.
N/A
0 to 8
Number of the slot where the board

whose monitoring results are
N/A
StartFeq
200
kHz
4130
Start frequency for uplink frequency

scanning.
N/A
End frequency for uplink frequency

scanning.
N/A
4410
8560
9260
9610
12510
EndFeq
200
kHz
4235
4565
8915
9540
9890
12840
Branch[n]
0.1
dBm
-2^31 to
2^31
Received total bandwidth power of

branch[n]. The value of n ranges
from 1 to 4 for 3900 series base
stations, and is 1 for BTS3202Es
and BTS3203Es.
N/A
Data Type
N/A
N/A
Data type of uplink frequency

scanning result.
N/A
4.9 DTF Test

This task is used to detect the distance to fault (DTF).
Issue 07 (2013-11-30)

106
eNodeB
4 Device Monitoring

Services in cells served by the RRU or RFU are interrupted during the test.
4.9.3 Parameters
Table 4-17 Parameters for DTF test monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the RRU or RFU for the DTF test
is located.
Subrack No.
Number of the subrack where the RRU or RFU for the DTF test
is located.
Slot No.
Number of the slot where the RRU or RFU for the DTF test is
located.
TX Channel No.
Number of the transmit channel for the DTF test.
Cable Type
Type of the feeder for the DTF test. It can be set to 1/4 Cable,
3/8 Cable, 1/2 Cable, 5/8 Cable, 7/8 Cable, 7/8 Low-loss
Cable, 11/4 Cable, 15/8 Cable, or Ideal Transmission Line.
The default value is 7/8 Cable.
Display Range of
Feeder Test Result (m)
Values of the DTF test that can be displayed. The value ranges 0
to 120, and the default value is 100.
Start
Frequency(0.1MHz)
Start frequency in the DTF test. The value ranges 0 to 65535,

and the default value is 0.
Stop
Frequency(0.1MHz)
Final frequency in the DTF test. The value ranges 0 to 65535,

and the default value is 65535.
Save File

results are automatically saved in the default path. The file
name, file format, and save path can be set.

Table 4-18 Results of DTF test
Parameter
Unit
Value
Range
Description
Formula
Cabinet No.
N/A
0 to 62

N/A
Subrack No.
N/A
4 to 5, 60
to 254

N/A
Issue 07 (2013-11-30)

107
eNodeB
4 Device Monitoring
Parameter
Unit
Value
Range
Description
Formula
Slot No.
N/A
0 to 8

N/A
TX Channel
No.
N/A
0 to 7
Number of the branch on which

N/A
Feeder Test
N/A
N/A
Test results.
N/A
Display Range
of Feeder Test
Results
0 to 120
VSWR DTF monitoring results.
N/A
4.10 FFT Frequency Scan

This task is used to check the spectrum status. You can check interference in the frequency
and time domains by analyzing the sampled spectrum and power distribution.

None.
4.10.3 Parameters
Table 4-19 Parameters for FFT Frequency Scanning
Parameter
Description
Cabinet No.
Number of the cabinet where the board/eNodeB for Fast Fourier

Transport (FFT) frequency scanning is located.
Subrack No.
Number of the subrack where the board/eNodeB for FFT frequency

scanning is located.
Slot No.
Number of the slot where the board/eNodeB for FFT frequency

scanning is located.
Index of RX
Channel[n]
Index of RX channel[n] of the RRU in 3900 series base stations or

BRU in BTS3202Es for FFT frequency scan. The value of n is 1 or 2.
Mode
Mode for FFT frequency scan.
Issue 07 (2013-11-30)

108
eNodeB
4 Device Monitoring
Parameter
Description
Scan Mode
Mode of checking the output power of each transmit channel and

carrier. It can be set to High-Resolution Online Frequency,
Broadband Online Frequency, or Broadband Offline Frequency.
TX channel is provided by the RF port of the RRU/RFU/BRU. A carrier is
similar to a cell.
RBW(KHZ)
Save File
Time frequency of FFT frequency detection, in units of kHz.
When Scan Mode is set to High-Resolution Online Frequency,

the value range of this parameter is from 15 to 200, and the default
value is 100.
When Scan Mode is set to Broadband Online Frequency or

Broadband Offline Frequency, the value range of this parameter is
from 100 to 5000, and the default value is 200.
The Save File check box is selected by default, and monitoring results
are automatically saved in the default path. The file name, file format,
and save path can be set.

Table 4-20 Results of FFT frequency scanning monitoring
Parameter
Unit
Value
Range
Description
Formula
Cabinet No.
N/A
0 to 62

N/A
Subrack No.
N/A
4 to 5, 60 to
254

N/A
Slot No.
N/A
0 to 8

N/A
RX Channel
Index
N/A
0 to 7
Index of the RX channel. An RX

channel may have several carriers
for 3900 series base stations, but
only one carrier for BTS3202Es.
N/A
Spectrum process types are as

follows:
N/A
NOTE
0 and 1 in
BTS3202Es
Spectrum
Process Type
N/A
0 to 2
0: High-Resolution Online
Frequency
1: Broadband Online Frequency
2: Broadband Offline Frequency
Issue 07 (2013-11-30)

109
eNodeB
4 Device Monitoring
Parameter
Unit
Value
Range
Description
Formula
Data Type
N/A
N/A
Data type of the channel ID.
N/A
RBW(KHZ)
kHz
15 to 200,
Time frequency of the FFT

frequency detection.
N/A
100 to 5000
4.11 AAS
This task is used to maintain an eNodeB.

None.
4.11.3 Parameters
Table 4-21 Parameters for AAS
Parameter
Description
AARU Cabinet
No.
Number of the cabinet where the active antenna radio unit (AARU) is
located. The value ranges from 0 to 62.
AARU Subrack
No.
Number of the subrack where the AARU is located. The value ranges
from 60 to 254.
AARU Slot No.
Number of the slot where the AARU is located. The value ranges
from 0 to 3.
Frequency
Frequency of the carrier for AAS query. The value ranges from 0 to
65535.
Antenna Port No.
Virtual antenna port number used by the carrier for AAS query. The
value ranges from 0 to 255.
HE

Issue 07 (2013-11-30)

110
eNodeB
4 Device Monitoring

Table 4-22 Results for AAS
Parameter
Unit
Value
Range
Description
Formula
AARU Cabinet
No.
N/A
0 to 62

AARU is located.
N/A
AARU Subrack
No.
N/A
60 to 254

AARU is located.
N/A
AARU Slot No.
N/A
0 to 3
Number of the slot where the AARU

is located.
N/A
Antenna Port
No.
N/A
0 to 255
Number of the virtual antenna port

used by the carrier for AAS query.
N/A
Direction
N/A
0 to 2^8-1
1: Rx in uplink
N/A
2: Tx in downlink
Data Type
N/A
N/A
Data in the horizontal or vertical

direction.
N/A
4.12 Frequency Scanning Intermodulation Interference

Detection Monitoring
This task is used to detect the interference between the uplink and downlink in the TX
channel of an RRU or RFU.

Services in cells served by the RRU or RFU are interrupted during the test.
4.12.3 Parameters
Table 4-23 Parameters for frequency scanning intermodulation interference detection monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the RRU or RFU for frequency

scanning intermodulation interference detection is located.
Subrack No.
Number of the subrack where the RRU or RFU for frequency

scanning intermodulation interference detection is located.
Issue 07 (2013-11-30)

111
eNodeB
4 Device Monitoring
Parameter
Description
Slot No.
Number of the slot where the RRU or RFU for frequency scanning
intermodulation interference detection is located.
TX Channel No.
Number of the TX channel for frequency scanning intermodulation

interference detection.
Start
Freq(0.1MHz)
Start frequency in frequency scanning intermodulation interference

detection. The value ranges from 0 to 65535.
End Freq(0.1MHz)
End frequency in frequency scanning intermodulation interference

Freq
Step(0.1MHz)
Frequency step in frequency scanning intermodulation interference

Save File


Table 4-24 Results of frequency scanning intermodulation interference detection monitoring
Parameter
Unit
Value Range
Description
Formula
Cabinet No.
N/A
0 to 62
Number of the cabinet

N/A
Subrack No.
N/A
4 to 5, 60 to 254

N/A
Slot No.
N/A
0 to 8
Number of the slot where

the board whose monitoring
results are reported is
located.
N/A
TX Channel
No.
N/A
0 to 1
Number of the TX channel

whose monitoring results
are reported.
N/A
Data Type
N/A
n = 3, 5, 7, 9, 11,
13, 15
IM order that is reported.
N/A
The value of n
indicates the IM
order.
Issue 07 (2013-11-30)

112
eNodeB
5 Transport Performance Monitoring
Transport Performance Monitoring
5.1 Local Pass-By Traffic Monitoring

This task is used to monitor the local traffic and forwarded traffic in real time. Forwarded
traffic is common when eNodeBs are cascaded.

None.
5.1.3 Parameters
Table 5-1 Parameters for local and forwarded traffic monitoring
Parameter
Description
Monitor Period (Seconds)
Interval of reporting monitoring results. It is set to 1 by

default.

Table 5-2 Results of local and forwarded traffic monitoring
Parameter
Unit
Value Range
Description
Formula
Local Receive
Traffic
Byte/s
0 to 100000000
Number of bytes received

by the eNodeB per second
within a monitoring period
and that are destined for the
local eNodeB.
N/A
Issue 07 (2013-11-30)

113
eNodeB
Parameter
Unit
Value Range
Description
Formula
Local Send
Traffic
Byte/s
0 to 100000000
Number of bytes transmitted

by the eNodeB within a
monitoring period,
excluding the forwarded
traffic.
N/A
eNodeB Bypass
Traffic
Byte/s
0 to 100000000
Number of bytes forwarded

by the eNodeB per second
N/A
5.2 IP Performance Monitoring

This task is used to monitor packet transmission and reception of the eNodeB at the IP layer
in real time.

None.
5.2.3 Parameters
Table 5-3 Parameters for IP performance monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the board/eNodeB for IP

performance monitoring is located.
Subrack No.
Number of the subrack where the board/eNodeB for IP

Slot No.
Number of the slot where the board/eNodeB for IP

VRF
Number of the virtual routing and forwarding instance for IP

performance monitoring.
Monitor Period (Seconds)
Interval of reporting monitoring results. It is set to 1 by

default.
Issue 07 (2013-11-30)

114
eNodeB

Table 5-4 Results of IP Performance monitoring
Parameter
Unit
Value
Range
Description
Formula
Number
increment of
RX packets
Packets
0 to 2000000
Total number of packets at the IP

layer received by the
board/eNodeB within a
monitoring period.
N/A
Number
increment of
TX packets
Packets
0 to 2000000
Total number of packets at the IP

layer transmitted by the
board/eNodeB within a
monitoring period.
N/A
Number
increment of
discarded
packets
Packets
0 to 2000000
Total number of discarded

packets at the IP layer received by
the board/eNodeB within a
monitoring period.
N/A

This task is used to monitor the traffic transmitted and received over physical ports, and to
monitor the traffic and load.
NOTE
When Port Type is set to Physical Port and Protocol Type is set to IP, the sending and receiving rates at
different layers are calculated for IP ports depending on the setting of Physical Port Type.If Physical
Port Type is set to TUNNEL, sending and receiving rates at the network layer are calculated for IP
ports.If Physical Port Type is set to other values, sending and receiving rates at the link layer are
calculated for IP ports.

None.
5.3.3 Parameters
Table 5-5 Parameters for transport port flux stat monitoring
Parameter
Description
Protocol Type
Type of the protocol for transport port flux stat monitoring. It can be set
to IP.
NOTE
LTE does not support ATM.
Issue 07 (2013-11-30)

115
eNodeB
Parameter
Description
Cabinet No.
Number of the cabinet where the board/eNodeB for transport port flux
stat monitoring is located.
Subrack No.
Number of the subrack where the board/eNodeB for transport port flux
Slot No.
Number of the slot where the board/eNodeB for transport port flux stat
Sub Board Type
Type of the subboard of a board or an eNodeB for transport port flux

stat monitoring. It can be set to the following values:
BASE_BOARD
BACK_BOARD
ETH_COVERBOARD
E1_COVERBOARD
UNCHANNELLED_COVERBOARD
NOTE
The LTE supports BASE_BOARD, BACK_BOARD or E1_COVERBOARD.
Type of the protocol for transport port flux stat monitoring. It can be set
to IP.
Protocol Type
NOTE
The LTE does not support ATM.

Port Type
Type of the port for transport port flux stat monitoring. It can be set to
PHYSICAL_PORT or RSCGRP.
Physical Port
Type
Type of the physical port for transport port flux stat monitoring. It can
be set to PPP, MPGroup, EthPort, EthTrunk, or TUNNEL.
NOTE
It can be set to PPPoE or EthPort in BTS3202Es or BTS3203Es.

It can be set to EthPort or EthTrunk in 3900 Series Base Station.
Port No.
Number of the physical port of a board or an eNodeB for transport port

flux stat monitoring.
Monitor Type
It is valid only when Port Type is set to RSCGRP and can be set to
Flow Stat or Load Stat.
Rate Config
Mode
It is valid only when Monitor Type is set to Load Stat and can be set
to Single Rate or Dual Rate.
Resource Group
No.
Number of the resource group for transport port flux stat monitoring. It
is valid only when Port Type is set to RSCGRP.
Include Packet
Discard
Information of
IP Layer
Specifies whether monitoring results contain the lost packets in the IP

layer.
Issue 07 (2013-11-30)

116
eNodeB
Parameter
Description
Include Packet
Discard
Information of
LINK Layer
Specifies whether monitoring results contain the lost packets in the data
link layer.
Extend Option
Specifies whether monitoring results contain the lost packets in the IP

layer or data link layer.
This monitoring item is valid when Protocol Type and Port Type are
set to ATM and PHYSICAL_PORT, respectively.

Table 5-6 Results of transport port flux stat monitoring
Parameter
Unit
Value Range
Description
Formula
RX Packet
Discard Ratio
of IP Layer
0 to 1000
Packet loss rate during

reception in the IP layer
within a monitoring
period.
N/A
TX Packet
Discard Ratio
of IP Layer
0 to 1000

transmission in the IP
layer within a
monitoring period.
N/A
RX Packet
Discard Ratio
of Link Layer
0 to 1000

reception in the data
link layer within a
monitoring period.
N/A
TX Packet
Discard Ratio
of Link Layer
0 to 1000

transmission in the data
link layer within a
monitoring period.
N/A
RX Packet
number of
Link Level
packet
0 to
4294967295

link layer within a
monitoring period.
N/A
TX Packet
number of
Link Level
packet
0 to
4294967295
Number of packets
transmitted in the data
link layer within a
monitoring period.
N/A
RX CRC Error
Packet number
of Link Level
packet
0 to
4294967295
Number of packets that

fail the CRC during
link layer within a
monitoring period.
N/A
Issue 07 (2013-11-30)

117
eNodeB
Parameter
Unit
Value Range
Description
Formula
TX Rate of IP
Resource
Group(pps)
pps
0 to
1000000000
Transmit rate of a
resource group
transmitted in a
physical port within a
monitoring period.
N/A
TX Rate of IP
Resource
Group(bps)
bps
0 to
1000000000
Transmit rate of a
resource group
transmitted in a
monitoring period.
N/A
RX Rate of IP
Port(bps)
bps
0 to
4294967295
Receive rate on a
monitoring period.
N/A
TX Rate of IP
Port(bps)
bps
0 to
4294967295
Transmit rate on a
monitoring period.
N/A
RX Rate of IP
Port(pps)
pps
0 to
4294967295
Receive rate on a
monitoring period.
N/A
TX Rate of IP
Port(pps)
pps
0 to
4294967295
Transmit rate on a
monitoring period.
N/A
Tx Logic Port
Admitted
Bandwidth of
SingleRate
Kbps
0 to
1000000000
Admission bandwidth
for data transmission on
the logical port in
single-rate mode within
N/A
Rx Logic Port
Admitted
Bandwidth of
SingleRate
Kbps
0 to
1000000000
Admission bandwidth
for data reception on
the logical port in
N/A
Tx Logic Port
GBR Load of
SingleRate
Kbps
0 to
1000000000
Transmit load for GBR

service data
transmission on the
logical port in
N/A
Rx Logic Port
GBR Load of
SingleRate
Kbps
0 to
1000000000
Receive load for GBR

service data reception
on the logical port in
N/A
Issue 07 (2013-11-30)

118
eNodeB
Parameter
Unit
Value Range
Description
Formula
Tx Logic Port
GBR Load
Ratio of
SingleRate
0 to 100
Transmit load rate of

GBR service data
transmission on the
logical port in
Transmit load for

GBR service data
transmission on
the logical port in
single-rate mode x
100/Transmit rate
of a transmission
resource group in
an IP port
Rx Logic Port
GBR Load
Ratio of
SingleRate
0 to 100
Receive load rate of

GBR service data
reception on the logical
port in single-rate mode
within a monitoring
period.
Receive load for

GBR service data
reception on the
logical port in
single-rate mode x
100/receive rate of
a transmission
resource group in
an IP port
Tx Logic Port
Load of
SingleRate
Kbps
0 to
1000000000
Transmit load for data

transmission on the
logical port in
N/A
Rx Logic Port
Load of
SingleRate
Kbps
0 to
1000000000
Receive load for data

port in single-rate mode
within a monitoring
period.
N/A
Tx Logic Port
Load Ratio of
SingleRate
0 to 100

data transmission on
the logical port in
Transmit load for

data transmission
on the logical port
in single-rate mode
x 100/Admission
bandwidth for data
transmission on
the logical port in
single-rate mode
Rx Logic Port
Load Ratio of
SingleRate
0 to 100

data reception on the
logical port in
Receive load for

data reception on
the logical port in
single-rate mode x
100/Admission
bandwidth for data
reception on the
logical port in
single-rate mode
Issue 07 (2013-11-30)

119
eNodeB
Parameter
Unit
Value Range
Description
Formula
Tx Logic Port
Flow of
SingleRate
Kbps
0 to
1000000000
Transmit traffic for data

transmission on the
logical port in
N/A
Tx Logic Port
CIR Admitted
Bandwidth of
DualRate
Kbps
0 to
1000000000
CIR admission
bandwidth for data
transmission on the
logical port in
double-rate mode
within a monitoring
period.
N/A
Rx Logic Port
CIR Admitted
Bandwidth of
DualRate
Kbps
0 to
1000000000
CIR admission
bandwidth for data
port in double-rate
mode within a
monitoring period.
N/A
Tx Logic Port
PIR Admitted
Bandwidth of
DualRate
Kbps
0 to
1000000000
PIR admission
bandwidth for data
transmission on the
logical port in
double-rate mode
within a monitoring
period.
N/A
Rx Logic Port
PIR Admitted
Bandwidth of
DualRate
Kbps
0 to
1000000000
PIR admission
bandwidth for data
port in double-rate
mode within a
monitoring period.
N/A
Tx Logic Port
GBR Load of
DualRate
Kbps
0 to
1000000000
Transmit load for GBR

service data
transmission on the
logical port in
double-rate mode
within a monitoring
period.
N/A
Rx Logic Port
GBR Load of
DualRate
Kbps
0 to
1000000000
Receive load for GBR

double-rate mode
within a monitoring
period.
N/A
Issue 07 (2013-11-30)

120
eNodeB
Parameter
Unit
Value Range
Description
Formula
Tx Logic Port
Non-Flow-Con
trol Service
Load of
DualRate
Kbps
0 to
1000000000
Transmit load for

non-flow-controllable
service data
transmission on the
logical port in
double-rate mode
within a monitoring
period.
N/A
Rx Logic Port
Non-Flow-Con
trol Service
Load of
DualRate
Kbps
0 to
1000000000
Receive load for

non-flow-controllable
double-rate mode
within a monitoring
period.
N/A
Tx Logic Port
GBR Load
Rate of
DualRate
0 to 100

GBR service data
transmission on the
logical port in
double-rate mode
within a monitoring
period.
Transmit load for

GBR service data
transmission on
the logical port in
double-rate mode
x 100/PIR
admission
bandwidth for data
transmission on
the logical port in
double-rate mode
Rx Logic Port
GBR Load
Rate of
DualRate
0 to 100

GBR service data
port in double-rate
mode within a
monitoring period.
Receive load for

GBR service data
reception on the
logical port in
double-rate mode
x 100/PIR
admission
bandwidth for data
reception on the
logical port in
double-rate mode
Tx Logic Port
CIR
Bandwidth
Load Rate of
DualRate
0 to 100
CIR bandwidth load

rate of GBR service
data transmission on
the logical port in
double-rate mode
within a monitoring
period.
Transmit load for

non-flow-controlla
ble service data
transmission on
the logical port in
double-rate mode
x 100/CIR
admission
bandwidth for data
transmission on
the logical port in
double-rate mode
Issue 07 (2013-11-30)

121
eNodeB
Parameter
Unit
Value Range
Description
Formula
Rx Logic Port
CIR
Bandwidth
Load Rate of
DualRate
0 to 100
CIR bandwidth load

rate of GBR service
data reception on the
logical port in
double-rate mode
within a monitoring
period.
Receive load for

non-flow-controlla
ble service data
reception on the
logical port in
double-rate mode
x 100/CIR
admission
bandwidth for data
reception on the
logical port in
double-rate mode
Tx Logic Port
Load of
DualRate
Kbps
0 to
1000000000
Transmit load for data

transmission on the
logical port in
double-rate mode
within a monitoring
period.
N/A
Rx Logic Port
Load of
DualRate
Kbps
0 to
1000000000
Receive load for data

port in double-rate
mode within a
monitoring period.
N/A
Tx Logic Port
PIR
Bandwidth
Load Rate of
DualRate
0 to 100
PIR bandwidth load

rate of data
transmission on the
logical port in
double-rate mode
within a monitoring
period.
Transmit load for

data transmission
on the logical port
in double-rate
mode x 100/PIR
admission
bandwidth for data
transmission on
the logical port in
double-rate mode
Rx Logic Port
PIR
Bandwidth
Load Rate of
DualRate
0 to 100
PIR bandwidth load

rate of data reception
double-rate mode
within a monitoring
period.
Receive load for

data reception on
the logical port in
double-rate mode
x 100/PIR
admission
bandwidth for data
reception on the
logical port in
double-rate mode
Tx Logic Port
Flow of
DualRate
Kbps
0 to
1000000000
Transmit traffic for data

transmission on the
logical port in
double-rate mode
within a monitoring
period.
N/A
Issue 07 (2013-11-30)

122
eNodeB
5.4 Transport Link Flux Stat Monitoring

This task is used to monitor the traffic on the control plane, user plane, and the OM channel.

None.
5.4.3 Parameters
Table 5-7 Parameters for transport link flux stat monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the board/eNodeB for transport link flux
Subrack No.
Number of the subrack where the board/eNodeB for transport link flux
Slot No.
Number of the slot where the board/eNodeB for transport link flux stat
Protocol Type
It can be set to ATM or IP in 3900 series base stations. It can be set

only to IP in BTS3202Es and BTS3203Es.
Sub Board Type
Type of the subboard of a board or an eNodeB for transport port flux

stat monitoring. It can be set to BASE_BOARD,
UNCHANNELLED_COVERBOARD, E1_COVERBOARD, or
BACK_BOARD.
This parameter is valid in 3900 series base stations only when Protocol
Type is set to ATM.
Physical Port
Type
Physical port type of the board/eNodeB for transport port flux stat
monitoring. It can be set to IMAGRP, UNI, STM_1, or FRAATM.
Type is set to ATM.
Unit
It can be set to cps or bps.

Type is set to ATM.
Port No.
Port number of the board for transport port flux stat monitoring.
Type is set to ATM.
PVCx
The value range for x is from 1 to 6.

Type is set to ATM.
VPI
Issue 07 (2013-11-30)
Type is set to ATM.

123
eNodeB
Parameter
Description
VCI
Type is set to ATM.
Extend Option
Specifies whether monitoring results include the IPPM statistic. It can

be set to Exclude IPPM Statistic or Include IPPM Statistic.
This parameter is valid only when Protocol Type is set to IP.
SCTP
Specifies whether to monitor the SCTP link quality.

SCTP No.
Number of the SCTP link.

IPPATH
Specifies whether to monitor the quality of links on the user plane.

PATH ID
Number of the IP path.

OMCH
Specifies whether to detect the OM channel.

DSCP
Differentiated services code point (DSCP) value of the OM channel

when the OMCH parameter is specified.
Local IP
Local IP address of the OM channel when the OMCH parameter is

specified.
Remote IP
Remote IP address of the OM channel when the OMCH parameter is

specified.
Select Trace
Type
Type of a link to be monitored. It can be set to OMCH, IPPATH, or

SCTP. This parameter is available only on the M2000.
Save File
NOTE
Issue 07 (2013-11-30)

124
eNodeB
OMCH
Table 5-8 Results of OMCH monitoring

Parameter
Unit
Value Range
Description
Formula
Test Type
N/A
1: PVC
Test result types, including

PVC, OMCH, IPPath,
SCTP, and IPPM.
N/A
2: OMCH
3: IPPath
4: SCTP
34: IPPM
BTS3202Es and BTS3203Es

do not support PVC.
RX Rate of OMCH
pps,
bps
0 to
4294967295
Receive rate of the OM

channel within a monitoring
period.
N/A
RX Rate of OMCH
pps,
bps
0 to
4294967295
Transmit rate of the OM

channel within a monitoring
period.
N/A
IP Path
Table 5-9 Results of IP Path monitoring

Parameter
Unit
Value Range
Description
Formula
Test Type
N/A
1: PVC

PVC, OMCH, IPPath,
SCTP, and IPPM.
N/A
2: OMCH
3: IPPath
4: SCTP
34: IPPM

do not support PVC.
Path Index
N/A
1 to 3
Index of an IP path.
N/A
Path ID
N/A
0 to 65535
Number of an IP path.
N/A
RX Rate of IPPATH
pps,
or
bps
0 to
4294967295
Receive rate of an IP path

N/A
TX Rate of IPPATH
pps,
or
bps
0 to
4294967295
Transmit rate of an IP path

N/A
Issue 07 (2013-11-30)

125
eNodeB
SCTP
Table 5-10 Results of SCTP monitoring

Parameter
Unit
Value Range
Description
Formula
Test Type
N/A
1: PVC

PVC, OMCH, IPPath,
SCTP, and IPPM.
N/A
2: OMCH
3: IPPath
4: SCTP
34: IPPM

do not support PVC.
Index
N/A
1 to 2
Index of an SCTP link
N/A
SCTP Link No.
N/A
0 to 65535
Number of an SCTP link
N/A
RX Rate of SCTP
pps,
bps
0 to
4294967295
Receive rate of the SCTP

link within a monitoring
period. That is, the number
of packets received over
the SCTP link per second,
including messages on
heartbeat, link setup, link
disconnection, and
handshake.
N/A
TX Rate of SCTP
pps,
bps
0 to
4294967295
Transmit rate of the SCTP

period. That is, the number
of packets transmitted over
the SCTP link per second,
including messages on
heartbeat, link setup, link
disconnection, and
handshake.
N/A
Receive Error
Packets of SCTP
pps
0 to
4294967295
Number of error packets

received over the SCTP
period.
N/A
Retransmit Ratio of
SCTP
0 to 1000
Retransmission rate of
SCTP association data
N/A
RX Packet Discard
Rate of SCTP
pps
0 to
4294967295
Number of discarded
incoming packets in the
SCTP link within a
monitoring period.
N/A
Issue 07 (2013-11-30)

126
eNodeB
IPPM
Table 5-11 Results of IPPM monitoring

Parameter
Unit
Value Range
Description
Formula
Test Type
N/A
1: PVC
Test result types,

including PVC, OMCH,
IPPath, SCTP, and IPPM.
N/A
2: OMCH
3: IPPath
4: SCTP
34: IPPM
BTS3202Es and
BTS3203Es do not support
PVC.
Index
N/A
1 to 3
Index of the IPPM.
N/A
Number
N/A
0 to 65535
Number of an IPPM
session.
N/A
Average RTT
Delay(ms)
ms
0 to
4294967295
Average delay of the

IPPM within a monitoring
period.
N/A
TX Packet
Discard Rate()
0.000001
0 to 100000
Uplink average packet

loss rate of the IPPM
within a monitoring
period.
N/A
TX Time
Jitter(ms)
ms
-65536 to
65535
Uplink average jitter of

the IPPM within a
monitoring period.
N/A
RX Packet
Discard Rate()
0.000001
0 to 100000
Downlink average packet

loss rate of the IPPM
within a monitoring
period.
N/A
RX Time
Jitter(ms)
ms
-65536 to
65535
Downlink average jitter of

the IPPM within a
monitoring period.
N/A
TX Lost Packet
number
Packet
0 to
4294967295
Number of discarded
packets in data
transmission of the IPPM
within a monitoring
period.
N/A
Tx Packet Num
Packet
0 to
4294967295
Number of packets
transmitted over the IPPM
within a monitoring
period.
N/A
Issue 07 (2013-11-30)

127
eNodeB
5.5 UDP Test Monitoring

This task is used to measure the link quality, including the round-trip delays, jitter, and packet
loss rate by injecting User Datagram Protocol (UDP) packets from the eNodeB to other NEs
and then transmitting the packets back to the eNodeB when the eNodeB is not serving any
UEs.

None.
5.5.3 Parameters
Table 5-12 Parameters for UDP test monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the main control board/eNodeB for the
UDP test is located.
Subrack No.
Number of the subrack where the main control board/eNodeB for the
Slot No.
Number of the slot where the main control board/eNodeB for the
Monitor Period
(Seconds)
VRF
Number of the virtual routing and forwarding instance for UDP test
monitoring.
Source IP Address
IP address of the eNodeB.
Source Port No.
Number of UDP port on the eNodeB. The value ranges from 1024 to
65,535.
Destination IP
Address
IP address of the peer end.
Destination Port
No
Number of UDP port on the peer end. The value ranges from 1024 to
65,535.
DSCP
Differentiated services code point (DSCP) of the UDP packet. The

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

150,000. The default value is 150000.
UDP PACKETS
LENGTH
(BYTES)
Length of the UDP packet. The value ranges from 72 to 1500. The
default value is 1500.
Issue 07 (2013-11-30)

128
eNodeB
Parameter
Description
Time (Minutes)
Duration of UDP test monitoring. The test stops automatically when

the duration expires. The value ranges from 1 to 60. The default value
is 15.

Table 5-13 Result of UDP test monitoring
Parameter
Unit
Value
Range
Description
Formula
Drop Packet
Ratio
0.001%
0 to 100000
Rate of lost packets to total

packets on the
transmission link within a
monitoring period.
Number of
discarded packets
per minute x
100000/Expected
number of
packets received
on the
transmission link
per minute
Average Drop
Packet Ratio
0.001%
0 to 100000
Average rate of lost

packets to total packets on
the transmission link
within a monitoring
period.
Total number of
discarded packets
x 100000/Total
number of
packets
Delay
Micros
econd
0 to
4000000
Delay on the transmission

link when monitoring
results are reported. This
monitoring item indicates
the time difference
between sending a packet
by the sender and
receiving the packet by the
receiver.
N/A
Jitter
N/A
N/A
Jitter on the transmission

period.
|Delay - Average
Delay|/Average
Delay
NOTE
The displayed value is equal

to the monitored value
multiplied by 1000.
Average Delay
Issue 07 (2013-11-30)
Micros
econd
0 to
4000000
Average delay on the

transmission link within a
monitoring period.

N/A
129
eNodeB
5.6 PPPoE Monitoring

This task is used to monitor PPPoE online performance. PPPoE online performance
monitoring helps monitor the link quality, which involves number of received packets,
number of transmitted packets, receive rate, transmit rate, number of discarded packets during
reception, number of discarded packets during transmission, packet loss rate during reception,
and packet loss rate during transmission. Packet drip ratio is a key indicator of the efficiency
of packet transmission.

None.
5.6.3 Parameters
Table 5-14 Parameters for PPPoE monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the board/eNodeB for the PPPoE

performance tests is located.
Subrack No.
Number of the subrack where the board/eNodeB for the PPPoE

Slot No.
Number of the slot where the board/eNodeB for the PPPoE

PPPoELink No.
Number of the PPPoE link to be tested.
Monitor Period
(Seconds)

Table 5-15 Results of PPPoE monitoring
Parameter
Unit
Value Range
Description
Formula
Receive
Packets
Packet
0 to 2000000
Number of packets
received by the receiving
end of a PPPoE link
within a monitoring
period.
N/A
Send
Packets
Packet
0 to 2000000
Number of packets
transmitted by the
transmitting end of a
PPPoE link within a
monitoring period.
N/A
Issue 07 (2013-11-30)

130
eNodeB
Parameter
Unit
Value Range
Description
Formula
Receive
Bytes
bps
0 to
300000000
Number of bits received

per second by the
receiving end of a PPPoE
period.
N/A
Send Bytes
bps
0 to
300000000
Number of bits transmitted

per second by the
PPPoE link within a
monitoring period.
N/A
Receive
Drop
Packets
Packet
0 to 2000000
Number of packets
discarded by the receiving
end of a PPPoE link
within a monitoring
period.
N/A
Send Drop
Packets
Packet
0 to 2000000
Number of packets
discarded by the
PPPoE link within a
monitoring period.
N/A
Receive
Drop
Packets
Ratio
0 to 100
Statistics on the packet

loss rate of the receiving
end of a PPPoE link
within a monitoring
period.
Receive Drop
Packets
x100/(Receive
Drop Packets +
Receive Packets)
Send Drop
Packets
Ratio
0 to 100
Statistics on the packet

loss rate of the
PPPoE link within a
monitoring period.
Send Drop
Packets
x100/(Send
Packets + Send
Drop Packets)
5.7 IPSec Performance Monitoring

This task is used to monitor packets transmitted and received over the IP security (IPsec)
tunnel.

None.
Issue 07 (2013-11-30)

131
eNodeB
5.7.3 Parameters
Table 5-16 Parameters for IPSec performance monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the board/eNodeB for IPSec performance

Subrack No.
Number of the subrack where the board/eNodeB for IPSec performance

Slot No.
Number of the slot where the board/eNodeB for IPSec performance

Monitor Period
(Seconds)
Save File
NOTE

Table 5-17 Results of IPSec performance monitoring
Parameter
Unit
Value Range
Description
Formula
IPSec Send
Rate
pps
0 to
4294967295
Transmit rate on the

IPSec tunnel within a
monitoring period.
N/A
IPSec Receive
Rate
pps
0 to
4294967295
Receive rate on the

IPSec tunnel within a
monitoring period.
N/A
IPSec Receive
DropRate
0.0000
001
0 to 1000000
Packet loss rate for data

reception on the IPSec
tunnel within a
monitoring period.
N/A
5.8 Transport OAM Monitoring

This task is used to monitor packets transmitted and received over the ITU-T Y.1731-based
link and the link quality.
Issue 07 (2013-11-30)

132
eNodeB

None.
5.8.3 Parameters
Table 5-18 Parameters for transport OAM monitoring
Parameter
Description
Test Type
It can be set to:
Y1731-LM
Y1731-DM
Session ID
Number of the session for transport OAM monitoring.
Save File

Table 5-19 Results of transport OAM monitoring
Parameter
Unit
Value Range
Description
Formula
Total Frames
Transmitted in
Uplink
Number
0 to
4294967295
Total number frame

transmitted in the uplink
N/A
Total Frames
Lost in Uplink
Number
0 to
4294967295
Absolute value of the total

number of frames discarded
in the uplink within a
monitoring period.
N/A
NOTE
Generally, the number of

transmitted frames is greater
than or equal to the number of
received frames. In this case,
this monitoring item indicates
the number of lost packets.
In abnormal scenarios, such as
the unordered transport
network, measurement
exceptions at the local end or
peer end, or different
monitoring polices at the local
end and peer end, the number
of transmitted frames is less
than the number of received
frames. In this case, this
monitoring item indicates the
level of measurement errors.
Issue 07 (2013-11-30)

133
eNodeB
Parameter
Unit
Value Range
Description
Formula
Total Frames
Transmitted in
Downlink
Number
0 to
4294967295
Total number of frames

transmitted in the downlink
N/A
Total Frames
Lost in
Downlink
Number
0 to
4294967295
Absolute value of the total

number of frames discarded
in the downlink within a
monitoring period.
N/A
NOTE
Generally, the number of

transmitted frames is greater
than or equal to the number of
received frames. In this case,
this monitoring item indicates
the number of lost packets.
In abnormal scenarios, such as
the unordered transport
network, measurement
exceptions at the local end or
peer end, or different
monitoring polices at the local
end and peer end, the number
of transmitted frames is less
than the number of received
frames. In this case, this
monitoring item indicates the
level of measurement errors.
Average
Delay(ms)
ms
0 to
4294967295
Average delay on the

transport OAM within a
monitoring period.
N/A
Average
Jitter(ms)
ms
-65536 to
65535
Average jitter on the

transport OAM within a
monitoring period.
N/A
5.9 Transport Auto Setup User Plane Monitoring

This task is used to monitor packets transmitted and received over the transport auto setup
user plane and the link quality.

None.
Issue 07 (2013-11-30)

134
eNodeB
5.9.3 Parameters
Table 5-20 Parameters for transport auto setup user plane monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the board/eNodeB for transport auto setup
user plane monitoring is located.
Subrack No.
Number of the subrack where the board/eNodeB for transport auto setup
Slot No.
Number of the slot where the board/eNodeB for transport auto setup
VRF
Index of the virtual routing and forwarding instance for transport auto
setup user plane monitoring.
IPPM Flag
It can be set to Include or Not Include.
Source IP
address
Source IP address of the link for transport auto setup user plane
monitoring.
Destination IP
address
This parameter is valid only when IPPM Flag is set to Include.
Save File
NOTE

Table 5-21 Results of transport auto setup user plane monitoring
Parameter
Unit
Value Range
Description
Formula
Test Type
N/A
0:
UserPlaneLink
Type of the link for transport

auto setup user plane
monitoring.
N/A
Index of the link for transport

auto setup user plane
monitoring.
N/A
1:
UserPlaneLink
+IPPM
Index
Issue 07 (2013-11-30)
N/A
0 to 2

135
eNodeB
Parameter
Unit
Value Range
Description
Formula
VRF Index
N/A
0 to 7
Index of the virtual routing

and forwarding instance for
transport auto setup user plane
monitoring.
N/A
0 in
BTS3202Es
and
BTS3203Es
Source IP
N/A
Valid IP
address
Source IP address of the link

for transport auto setup user
plane monitoring.
N/A
Destination IP
N/A
Valid IP
address
Destination IP address of the

link for transport auto setup
user plane monitoring.
N/A
Receive
Rate(pps)
pps
0 to
4294967295
Receive rate of a user plane

link in the IP layer within a
monitoring period.
N/A
Transmit
Rate(pps)
pps
0 to
4294967295
Transmit rate of a user plane

monitoring period.
N/A
Receive
Rate(bps)
bps
0 to
4294967295
Receive rate of a user plane

monitoring period.
N/A
Transmit
Rate(bps)
bps
0 to
4294967295
Transmit rate of a user plane

monitoring period.
N/A
Average RTT
Delay(ms)
ms
0 to
4294967295
Average delay of a user plane

monitoring period.
N/A
Transmit
Packet Discard
Rate
0.01
0 to 1000
Average packet loss rate of a

user plane link in the IP layer
N/A
Transmit Time
Jitter(ms)
ms
-65536 to
65535
Average jitter for data

transmission of a user plane
monitoring period.
N/A
Receive Packet
Discard Rate
0.01
0 to 1000
Average packet loss rate for

data reception of a user plane
monitoring period.
N/A
Receive Time
Jitter(ms)
ms
-65536 to
65535
Average jitter for data

reception of a user plane link
in the IP layer within a
monitoring period.
N/A
Issue 07 (2013-11-30)

136
eNodeB
Parameter
Unit
Value Range
Description
Formula
Transmit lost
packet
packet
0 to
4294967295
Number of discarded packets

for data transmission of a user
plane link in the IP layer
N/A
Transmit
packet
packet
0 to
4294967295
Number of transmitted packets

of a user plane link in the IP
layer within a monitoring
period.
N/A
Issue 07 (2013-11-30)

137
eNodeB
6 RRU/RFU Performance Monitoring
RRU/RFU Performance Monitoring

The RRU or RFU scans frequencies continuously, calculates the received signal strength, and
reports the strength to the LMT. The received signal strength is used as reference for
interference location and analysis.

None.
6.1.3 Parameters
Table 6-1 Parameters for sector performance monitoring
Parameter
Description
Test Items
It can be set only to UL Widefreq Scan.
Monitor Period (ms)

200, 500, 1000, or 2000.
Sector Device ID
ID of the sector for performance monitoring. It is set to a value in

the range of 0 to 65535. It is set to 0 by default.
Frequency Band
Frequency band supported by the sector. It is set to a value in the

range of 1 to 40.
UL EARFCN
Uplink EARFCN of a cell. It is set to a value in the ranges of

18000 to 45589 and 54436 to 65535.
UL Bandwidth
Uplink bandwidth of the cell. It can be set to 1.4M, 3M, 5M,

10M, 15M, or 20M.
BTS3202Es and BTS3203Es do not support the cell bandwidth of
1.4 MHz or 3 MHz.
Issue 07 (2013-11-30)

138
eNodeB
6 RRU/RFU Performance Monitoring

Table 6-2 Results of UL Widefreq Scan monitoring
Parameter
Unit
Value
Range
Description
Formula
Local Sector ID
N/A
0 to 65535
ID of the monitored sector.
N/A
Monitor Period
ms
[50, 100,
200, 500,
1000, 2000]
Interval of reporting monitoring

results.
N/A
Frequency
kHz
0
to
2620000
Frequency of the monitored RB

for
sector
performance
monitoring.
N/A
Signal Strength
dBm
140 to 50
RSSI in each RB from the

physical layer when monitoring
N/A
Issue 07 (2013-11-30)

139

ENodeB Performance Monitoring Reference (07) (PDF) - en

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

ENodeB Performance Monitoring Reference (07) (PDF) - en

Transféré par

Droits d'auteur :

Formats disponibles

eNodeB

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

The descriptions of parameters for performance monitoring

The descriptions of monitor items

The value range of each monitor item

The formula used to calculate the value of each monitor item

The mapping single-mode base station version is:

In this document, BTS3203E refers to the BTS3203E LTE.

Huawei Proprietary and Confidential

About This Document

Site maintenance engineers

2.6.4 Monitoring Results

Updatad the descriptions of "Value Range"

Updated the condition inTable 2-45

2.17.4 Monitoring Results

Added the parameter "Local Cell ID" in

3.1.4 Monitoring Results

Added the descriptions of " UL CoMP User

3.3.4 Monitoring Results

Added note of the Description in parameters

3.4.4 Monitoring Results

Updatad the descriptions of "Value Range"

3.6.4 Monitoring Results

Huawei Proprietary and Confidential

About This Document

3.7.4 Monitoring Results

Updatad the descriptions of "Value

Modified the Value Range of RLC

3.9.4 Monitoring Results

Updatad the descriptions of "Value Range"

Added the parameter of Test Item.

3.11.4 Monitoring Results

Updatad the descriptions of "Value Range"

3.12.4 Monitoring Results

Updatad the Table 5-5Parameters for

Updatad the descriptions of IPPM Flag.

5.9.4 Monitoring Results

Updatad the Value Range of Test Type.

1.3.3 General Parameter Input Description

Add the descriptions of General Parameter.

Add the descriptions of the Note.

3.7.4 Monitoring Results

Updated the "Result of RLC data stream

Huawei Proprietary and Confidential

About This Document

3.8.4 Monitoring Results

Updated the "Results of RLC throughput

3.12.4 Monitoring Results

Updated the "Results of user downlink

5.3 Transport Port Flux Stat Monitoring

Modified descriptions of Usage Scenario.

No information in Issue 04 (2013-07-22) is deleted from this issu

Added descriptions of BTS3203Es.

3 User Performance Monitoring

Modified the value range of Physical Cell

2.14 HARQ Statistic Monitoring