ENodeB Performance Monitoring Reference (Draft D) (PDF) - en

eNodeB
Performance Monitoring Reference

Issue
Draft D
Date
2014-03-26
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue Draft D (2014-03-26)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
eNodeB
Contents
Contents
1 About This Document..................................................................................................................1
2 Change History..............................................................................................................................3
3 Introduction....................................................................................................................................8
3.1 Overview........................................................................................................................................................................8
3.2 Performance Monitoring Types......................................................................................................................................8
3.3 Precautions....................................................................................................................................................................11
3.3.1 Precautions for Monitoring on 3900 Series Base Stations........................................................................................11
3.3.2 Precautions for Monitoring on BTS3202Es and BTS3203Es...................................................................................12
3.3.3 Precautions for Monitoring on BTS3205Es..............................................................................................................12
3.3.4 General Parameter Input Description........................................................................................................................13
4 Cell Performance Monitoring...................................................................................................15

4.1 UL CoMP (Cell) Monitoring........................................................................................................................................15
4.1.1 Usage Scenario..........................................................................................................................................................15
4.1.2 Service Impact...........................................................................................................................................................15
4.1.3 Parameters.................................................................................................................................................................15
4.1.4 Monitoring Results....................................................................................................................................................16
4.2 Satisfaction of Service Monitoring...............................................................................................................................16
4.2.1 Usage Scenario..........................................................................................................................................................16
4.2.2 Service Impact...........................................................................................................................................................17
4.2.3 Parameters.................................................................................................................................................................17
4.3 General Throughput Monitoring..................................................................................................................................19
4.3.1 Usage Scenario..........................................................................................................................................................19
4.3.2 Service Impact...........................................................................................................................................................19
4.3.3 Parameters.................................................................................................................................................................20
4.4 Service Statistics Monitoring........................................................................................................................................24
4.4.1 Usage Scenario..........................................................................................................................................................25
4.4.2 Service Impact...........................................................................................................................................................25
4.4.3 Parameters.................................................................................................................................................................25

ii
eNodeB
Contents
4.5 User Statistics Monitoring............................................................................................................................................26

4.5.1 Usage Scenario..........................................................................................................................................................26
4.5.2 Service Impact...........................................................................................................................................................26
4.5.3 Parameters.................................................................................................................................................................26
4.6 Usage of RB Monitoring..............................................................................................................................................29
4.6.1 Usage Scenario..........................................................................................................................................................29
4.6.2 Service Impact...........................................................................................................................................................29
4.6.3 Parameters.................................................................................................................................................................30
4.7 ICIC (Cell) Monitoring.................................................................................................................................................32
4.7.1 Usage Scenario..........................................................................................................................................................32
4.7.2 Service Impact...........................................................................................................................................................32
4.7.3 Parameters.................................................................................................................................................................32
4.8 Multi-User MIMO Monitoring.....................................................................................................................................35
4.8.1 Usage Scenario..........................................................................................................................................................35
4.8.2 Service Impact...........................................................................................................................................................35
4.8.3 Parameters.................................................................................................................................................................35
4.9 RSSI Statistic Monitoring.............................................................................................................................................36
4.9.1 Usage Scenario..........................................................................................................................................................36
4.9.2 Service Impact...........................................................................................................................................................36
4.9.3 Parameters.................................................................................................................................................................36
4.10 Interference Detection Monitoring.............................................................................................................................39
4.10.1 Usage Scenario........................................................................................................................................................39
4.10.2 Service Impact.........................................................................................................................................................39
4.10.3 Parameters...............................................................................................................................................................40
4.10.4 Monitoring Results..................................................................................................................................................40
4.11 TDD Interference Detection Monitoring....................................................................................................................42
4.11.1 Usage Scenario........................................................................................................................................................42
4.11.2 Service Impact.........................................................................................................................................................42
4.11.3 Parameters...............................................................................................................................................................42
4.12 Multi-User BF (Cell) Monitoring...............................................................................................................................45
4.12.1 Usage Scenario........................................................................................................................................................45
4.12.2 Service Impact on....................................................................................................................................................45
4.12.3 Parameters...............................................................................................................................................................45
4.13 Scheduled Users Statistic Monitoring........................................................................................................................50

iii
eNodeB
Contents
4.13.1 Usage Scenario........................................................................................................................................................50

4.13.2 Service Impact.........................................................................................................................................................50
4.13.3 Parameters...............................................................................................................................................................51
4.14 HARQ Statistic Monitoring........................................................................................................................................52
4.14.1 Usage Scenario........................................................................................................................................................52
4.14.2 Service Impact.........................................................................................................................................................52
4.14.3 Parameters...............................................................................................................................................................52
4.15 DCI Statistic Monitoring............................................................................................................................................57
4.15.1 Usage Scenario........................................................................................................................................................57
4.15.2 Service Impact.........................................................................................................................................................57
4.15.3 Parameters...............................................................................................................................................................57
4.16 DRB Statistics Monitoring.........................................................................................................................................59
4.16.1 Usage Scenario........................................................................................................................................................59
4.16.2 Service Impact.........................................................................................................................................................59
4.16.3 Parameters...............................................................................................................................................................59
4.17 Idle MLB Monitoring.................................................................................................................................................64
4.17.1 Usage Scenario........................................................................................................................................................64
4.17.2 Service Impact.........................................................................................................................................................64
4.17.3 Parameters...............................................................................................................................................................64
4.18 MLB Monitoring........................................................................................................................................................65
4.18.1 Usage Scenario........................................................................................................................................................65
4.18.2 Service Impact.........................................................................................................................................................65
4.18.3 Parameters...............................................................................................................................................................65
4.19 eICIC CEU Throughput Monitoring..........................................................................................................................92
4.19.1 Usage Scenario........................................................................................................................................................92
4.19.2 Service Impact.........................................................................................................................................................93
4.19.3 Parameters...............................................................................................................................................................93
4.20 eICIC Statistic for CRE Area Monitoring..................................................................................................................95
4.20.1 Usage Scenario........................................................................................................................................................95
4.20.2 Service Impact.........................................................................................................................................................95
4.20.3 Parameters...............................................................................................................................................................95
4.21 DL CoMP (Cell) Monitoring....................................................................................................................................100
4.21.1 Usage Scenario......................................................................................................................................................100

iv
eNodeB
Contents
4.21.2 Service Impact.......................................................................................................................................................100

4.21.3 Parameters.............................................................................................................................................................100
4.21.4 Monitoring Results................................................................................................................................................100
4.22 Cell-Level Interference Randomization...................................................................................................................101
4.22.1 Usage Scenario......................................................................................................................................................101
4.22.2 Service Impact.......................................................................................................................................................101
4.22.3 Parameters.............................................................................................................................................................101
5 User Performance Monitoring................................................................................................103

5.1 UL CoMP (User) Monitoring.....................................................................................................................................103
5.1.1 Usage Scenario........................................................................................................................................................103
5.1.2 Service Impact.........................................................................................................................................................103
5.1.3 Parameters...............................................................................................................................................................103
5.2 VQI Monitoring..........................................................................................................................................................104
5.2.1 Usage Scenario........................................................................................................................................................104
5.2.2 Service Impact.........................................................................................................................................................104
5.2.3 Parameters...............................................................................................................................................................105
5.3 DL RSRP/RSRQ Monitoring.....................................................................................................................................107
5.3.1 Usage Scenario........................................................................................................................................................107
5.3.2 Service Impact.........................................................................................................................................................107
5.3.3 Parameters...............................................................................................................................................................107
5.4 BLER Monitoring.......................................................................................................................................................108
5.4.1 Usage Scenario........................................................................................................................................................108
5.4.2 Service Impact.........................................................................................................................................................108
5.4.3 Parameters...............................................................................................................................................................109
5.5 Power Headroom Monitoring.....................................................................................................................................112
5.5.1 Usage Scenario........................................................................................................................................................112
5.5.2 Service Impact.........................................................................................................................................................112
5.5.3 Parameters...............................................................................................................................................................112
5.6 Quality of Channel Monitoring..................................................................................................................................114
5.6.1 Usage Scenario........................................................................................................................................................114
5.6.2 Service Impact.........................................................................................................................................................114
5.6.3 Parameters...............................................................................................................................................................114
5.7 Scheduling Monitoring...............................................................................................................................................118
5.7.1 Usage Scenario........................................................................................................................................................118

eNodeB
Contents
5.7.2 Service Impact.........................................................................................................................................................118

5.7.3 Parameters...............................................................................................................................................................118
5.8 RLC Data Stream Monitoring....................................................................................................................................121
5.8.1 Usage Scenario........................................................................................................................................................122
5.8.2 Service Impact.........................................................................................................................................................122
5.8.3 Parameters...............................................................................................................................................................122
5.9 Throughput Monitoring..............................................................................................................................................123
5.9.1 Usage Scenario........................................................................................................................................................123
5.9.2 Service Impact.........................................................................................................................................................123
5.9.3 Parameters...............................................................................................................................................................123
5.10 AQM Monitoring......................................................................................................................................................126
5.10.1 Usage Scenario......................................................................................................................................................126
5.10.2 Service Impact.......................................................................................................................................................126
5.10.3 Parameters.............................................................................................................................................................127
5.11 UL Power Control Monitoring.................................................................................................................................128
5.11.1 Usage Scenario......................................................................................................................................................128
5.11.2 Service Impact.......................................................................................................................................................128
5.11.3 Parameters.............................................................................................................................................................128
5.12 DL Power Control Monitoring.................................................................................................................................130
5.12.1 Usage Scenario......................................................................................................................................................130
5.12.2 Service Impact.......................................................................................................................................................130
5.12.3 Parameters.............................................................................................................................................................130
5.13 ICIC (User) Monitoring............................................................................................................................................133
5.13.1 Usage Scenario......................................................................................................................................................133
5.13.2 Service Impact.......................................................................................................................................................133
5.13.3 Parameters.............................................................................................................................................................133
5.14 MCS Count Monitoring............................................................................................................................................136
5.14.1 Usage Scenario......................................................................................................................................................136
5.14.2 Service Impact.......................................................................................................................................................137
5.14.3 Parameters.............................................................................................................................................................137
5.15 Multi-User BF (User) Monitoring............................................................................................................................140
5.15.1 Usage Scenario......................................................................................................................................................140
5.15.2 Service Impact.......................................................................................................................................................140

vi
eNodeB
Contents
5.15.3 Parameters.............................................................................................................................................................140
5.16 SFN Detection Monitoring.......................................................................................................................................142
5.16.1 Usage Scenario......................................................................................................................................................142
5.16.2 Service Impact.......................................................................................................................................................142
5.16.3 Parameters.............................................................................................................................................................142
5.17 Cell Combination Monitoring..................................................................................................................................146
5.17.1 Usage Scenario......................................................................................................................................................146
5.17.2 Service Impact.......................................................................................................................................................146
5.17.3 Parameters.............................................................................................................................................................146
5.18 eICIC (User) Monitoring..........................................................................................................................................149
5.18.1 Usage Scenario......................................................................................................................................................150
5.18.2 Impact on Services.................................................................................................................................................150
5.18.3 Parameters.............................................................................................................................................................150
5.19 DL CoMP (User) Monitoring...................................................................................................................................154
5.19.1 Usage Scenario......................................................................................................................................................154
5.19.2 Impact on Services.................................................................................................................................................154
5.19.3 Parameters.............................................................................................................................................................155
6 Device Monitoring....................................................................................................................157
6.1 CPRI BER Monitoring...............................................................................................................................................157
6.1.1 Usage Scenario........................................................................................................................................................157
6.1.2 Service Impact.........................................................................................................................................................157
6.1.3 Parameters...............................................................................................................................................................157
6.2 CPU Usage Monitoring..............................................................................................................................................159
6.2.1 Usage Scenario........................................................................................................................................................159
6.2.2 Service Impact.........................................................................................................................................................159
6.2.3 Parameters...............................................................................................................................................................159
6.3 RRU/RFU/BRU Output Power Monitoring...............................................................................................................160
6.3.1 Usage Scenario........................................................................................................................................................160
6.3.2 Service Impact.........................................................................................................................................................160
6.3.3 Parameters...............................................................................................................................................................161
6.4 Board Temperature Monitoring..................................................................................................................................162
6.4.1 Usage Scenario........................................................................................................................................................162
6.4.2 Service Impact.........................................................................................................................................................162

vii
eNodeB
Contents
6.4.3 Parameters...............................................................................................................................................................163
6.5 Clock Quality Test Monitoring...................................................................................................................................164
6.5.1 Usage Scenario........................................................................................................................................................164
6.5.2 Service Impact.........................................................................................................................................................164
6.5.3 Parameters...............................................................................................................................................................164
6.6 IP Clock Data Collection Monitoring.........................................................................................................................165
6.6.1 Usage Scenario........................................................................................................................................................165
6.6.2 Service Impact.........................................................................................................................................................165
6.6.3 Parameters...............................................................................................................................................................166
6.7 RRU/RFU Output Power Monitoring.........................................................................................................................167
6.7.1 Usage Scenario........................................................................................................................................................167
6.7.2 Service Impact.........................................................................................................................................................167
6.7.3 Parameters...............................................................................................................................................................167
6.8 Rx Frequency Scanning..............................................................................................................................................169
6.8.1 Usage Scenario........................................................................................................................................................169
6.8.2 Service Impact.........................................................................................................................................................169
6.8.3 Parameters...............................................................................................................................................................169
6.9 DTF Test.....................................................................................................................................................................171
6.9.1 Usage Scenario........................................................................................................................................................171
6.9.2 Service Impact.........................................................................................................................................................171
6.9.3 Parameters...............................................................................................................................................................171
6.10 FFT Frequency Scan.................................................................................................................................................173
6.10.1 Usage Scenario......................................................................................................................................................173
6.10.2 Service Impact.......................................................................................................................................................173
6.10.3 Parameters.............................................................................................................................................................173
6.11 AAS..........................................................................................................................................................................175
6.11.1 Usage Scenario......................................................................................................................................................175
6.11.2 Service Impact.......................................................................................................................................................175
6.11.3 Parameters.............................................................................................................................................................176
6.12 Frequency Scanning Intermodulation Interference Detection Monitoring...............................................................177
6.12.1 Usage Scenario......................................................................................................................................................177
6.12.2 Service Impact.......................................................................................................................................................177
6.12.3 Parameters.............................................................................................................................................................177

viii
eNodeB
Contents
7 Transport Performance Monitoring.......................................................................................180

7.1 Local Pass-By Traffic Monitoring..............................................................................................................................180
7.1.1 Usage Scenario........................................................................................................................................................180
7.1.2 Service Impact.........................................................................................................................................................180
7.1.3 Parameters...............................................................................................................................................................180
7.2 IP Performance Monitoring........................................................................................................................................181
7.2.1 Usage Scenario........................................................................................................................................................181
7.2.2 Service Impact.........................................................................................................................................................181
7.2.3 Parameters...............................................................................................................................................................182
7.3 Transport Port Flux Stat Monitoring..........................................................................................................................183
7.3.1 Usage Scenario........................................................................................................................................................183
7.3.2 Service Impact.........................................................................................................................................................183
7.3.3 Parameters...............................................................................................................................................................183
7.4 Transport Link Flux Stat Monitoring.........................................................................................................................192
7.4.1 Usage Scenario........................................................................................................................................................192
7.4.2 Service Impact.........................................................................................................................................................192
7.4.3 Parameters...............................................................................................................................................................192
7.5 UDP Test Monitoring.................................................................................................................................................199
7.5.1 Usage Scenario........................................................................................................................................................199
7.5.2 Service Impact.........................................................................................................................................................199
7.5.3 Parameters...............................................................................................................................................................200
7.6 PPPoE Monitoring......................................................................................................................................................202
7.6.1 Usage Scenario........................................................................................................................................................202
7.6.2 Service Impact.........................................................................................................................................................202
7.6.3 Parameters...............................................................................................................................................................202
7.7 IPSec Performance Monitoring..................................................................................................................................204
7.7.1 Usage Scenario........................................................................................................................................................204
7.7.2 Service Impact.........................................................................................................................................................204
7.7.3 Parameters...............................................................................................................................................................205
7.8 Transport OAM Monitoring.......................................................................................................................................206
7.8.1 Usage Scenario........................................................................................................................................................206
7.8.2 Service Impact.........................................................................................................................................................206
7.8.3 Parameters...............................................................................................................................................................206

ix
eNodeB
Contents

7.9 Transport Auto Setup User Plane Monitoring............................................................................................................209
7.9.1 Usage Scenario........................................................................................................................................................209
7.9.2 Service Impact.........................................................................................................................................................209
7.9.3 Parameters...............................................................................................................................................................209
8 RRU/RFU Performance Monitoring.......................................................................................213

8.1 Sector Performance Monitoring.................................................................................................................................213
8.1.1 Usage Scenario........................................................................................................................................................213
8.1.2 Service Impact.........................................................................................................................................................213
8.1.3 Parameters...............................................................................................................................................................213

eNodeB
1 About This Document
About This Document
Purpose
This document describes the information about eNodeB-related performance monitoring tasks,
including:
l
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
V100R009C00
DBS3900 TDD
BTS3900
The mapping single-mode base station version is:

eNodeB: V100R007C00
BTS3900A
BTS3900L
BTS3900AL
BTS3202E
BTS3203E LTE
V100R009C00
BTS3205E
V100R009C00
NOTE
In this document, BTS3203E refers to the BTS3203E LTE.

eNodeB
1 About This Document
Intended Audience
This document is intended for:
l
System engineers
Site maintenance engineers

eNodeB
2 Change History
Change History
The following describes the changes in eNodeB Performance Monitoring Reference.

The document issues are as follows:
l
Draft D (2014-03-26)
Draft C (2014-02-28)
Draft B (2014-02-10)
Draft A (2014-01-27)
Draft D (2014-03-26)
This is the release of Draft D.
Compared with Draft C (2014-02-28), this issue does not include any new information.
Compared with Draft C (2014-02-28), this issue includes the following changes:
Topic
Change History
4.10.4 Monitoring Results
Changed Max RB Number of PUCCH in

the monitoring result to Max Number of
Used PUCCH RBs and modified its
description.
No information in Draft C (2014-02-28) is deleted from this issue.
Draft C (2014-02-28)
This is the release of Draft C.
Compared with Draft B (2014-02-10), this issue does not include the any new information.
Compared with Draft B (2014-02-10), this issue includes the following changes:

eNodeB
2 Change History
Topic
Change Description
Modified the description of the parameters CN

Operator Keep UL Synch Users Number, CN
Operator General Users Number, and CN
Operator NO-Activated Users Number.
Modified the value range of the parameters

Downlink Equivalent Used RB Num, Uplink
Equivalent Used RB Num, Downlink Freq
Diversity Used RB Num, Downlink Freq Select
Used RB Num, Downlink Harq RB Used RB
Num, and Downlink power off RB Num.
Modified the value range of the parameter MIMO

UE Pair Num.
Deleted the parameter DlEarfcnNum.
No informations in Draft B (2014-02-10) is deleted from this issue.
Draft B (2014-02-10)
This is the release of Draft B.
Compared with Draft A (2014-01-27), this issue includes the following new information.
l
4.21 DL CoMP (Cell) Monitoring
4.22 Cell-Level Interference Randomization
5.19 DL CoMP (User) Monitoring
Compared with Draft A (2014-01-27), this issue includes the following changes:
Topic
Change Description
5.16 SFN Detection Monitoring
Modified 5.16.3 Parameters and 5.16.4

Monitoring Results.
5.17 Cell Combination Monitoring
Modified 5.17.3 Parameters and 5.17.4

Monitoring Results.
No informations in Draft A (2014-01-27) is deleted from this issue.
Draft A (2014-01-27)
This is the release of Draft A.
Compared with issue 05 (2013-08-01) of V100R006C00, this issue includes the following new
information.

eNodeB
2 Change History
Idle MLB Monitoring

4.19 eICIC CEU Throughput Monitoring4.19 eICIC CEU Throughput Monitoring
Compared with issue 05 (2013-08-01) of V100R006C00, this issue includes the following
changes:
Topic
Change Description
3.3.2 Precautions for Monitoring on

BTS3202Es and BTS3203Es
Modified the value range of Local Cell ID.
4.3.3 Parameters
Added the parameter Save File.
4.5.3 Parameters
Updatad the value range and description in Table

4-16.
Modified the description of parameter antenna[y]

RSSI in Table 4-27.
4.18.3 Parameters
Added the parameter PLMN ID of Local Cell.
Updated the results of MLB monitoring in Table

4-48.
Updated the description of parameter Power

Offset of PDCCH in Table 5-34.
Updated the parameter of CQI in Table 5-16.

Modified the value range of the parameter
Effective Len in Table 5-16.
5.16.3 Parameters
Updated the context in the section Test Type

Bitmap.
Updated the context in the parameter Uplink SRS

RSRP.
Modified the value range of the parameters UL
RRU Flag and DL RRU Flag in Table 5-46.
Modified the eNodeB Bypass Traffic to Bypass

Traffic in Table 7-2.
Modified the parameters in Table 7-4.

l Modified the Number increment of RX to
Receive Packets.
l Modified the Number increment of TX to
Send Packets.
l Modified the Number increment of
discarded packets to Receive Drop Packets.

eNodeB
2 Change History
Topic
Change Description
7.3.3 Parameters
Modified the description of the paremeter Sub

Board Type in Table 7-5.
Updated the description of the parameter Extend
Option Table 7-5.
7.3.3 Parameters
Modified the monitoring results in Table 7-5.

l Deleted the RX Packets Discard Ratio of IP
Layer, TX Packets Discard Ratio of IP
Layer, RX Packets Discard Ratio of Link
Layer, TRX Packets Discard Ratio of Link
Layer, RX Packets number of Link Level,
and TX Packets number of Link Level.
l Added the Rx Traffic, Tx Traffic, Rx Packets,
Tx Packets, Rx Loss Packets, and Tx Loss
Packets.

l Modified RX Rate of OMCH to RX Rate.
l Modified TX Rate of OMCH to TX Rate.
l Modified Path Index to Index.
l Modified Path ID to Flag.
l Modified RX Rate of IPPATH to RX Rate.
l Modified TX Rate of IPPATH to TX Rate.
l Modified RX Rate of SCTP to RX Rate.
l Modified TX Rate of SCTP to TX Rate.
l Modified Receive Error Packets of SCTP to
RX Error Packets.
l Modified Retransmit Ratio of SCTP to
Resend Trunk Rate.
l Modified RX Packet Discard Rate of SCTP
to RX Packet Discard Rate.
7.9.3 Parameters
Modified the description of the parameter IPPM

Flag in 7.9.3 Parameters.
Modified the value range and description of

parameter Test Type in Table 7-21.
All
Changed the name of Huawei mobile element

management system from M2000 to U2000.
No informations in issue 05 (2013-08-01) of V100R006C00 is deleted from this issue.


eNodeB
2 Change History

eNodeB
3 Introduction
Introduction
3.1 Overview
Performance monitoring is used to monitor the equipment running status and service status of
eNodeBs by using iManager U2000 Mobile Element Management System (referred to as U2000)
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.
3.2 Performance Monitoring Types

Table 3-1 Performance monitoring types
Type
Task
Platform
Cell Performance Monitoring
UL CoMP (Cell) Monitoring
U2000
Satisfaction of Service
Monitoring
U2000
General Throughput
Monitoring
U2000&LMT
Service Statistics
Monitoring
U2000
User Statistics Monitoring
U2000&LMT
Usage of RB Monitoring
U2000
ICIC (Cell) Monitoring
U2000
Multi-User MIMO
Monitoring
U2000
RSSI Statistic Monitoring
U2000

eNodeB
3 Introduction
Type
User Performance
Monitoring
Task
Platform
Interference Detection
Monitoring
U2000&LMT
TDD Interference Detection

Monitoring
U2000
Multi-User BF (Cell)
Monitoring
U2000
Scheduled Users Statistic

Monitoring
U2000
HARQ Statistic Monitoring
U2000
DCI Statistic Monitoring
U2000
DRB Statistics Monitoring
U2000
MLB Monitoring
U2000
eICIC CEU Throughput

Monitoring
U2000
eICIC Statistic for CRE Area

Monitoring
U2000
DL CoMP (Cell) Monitoring
U2000
Cell-Level Interference
Randomization
U2000
UL CoMP (User)
Monitoring
U2000
VQI Monitoring
U2000
DL RSRP/RSRQ
Monitoring
U2000
BLER Monitoring
U2000
Power Headroom
Monitoring
U2000
Quality of Channel
Monitoring
U2000
Scheduling Monitoring
U2000
RLC Data Stream

Monitoring
U2000
Throughput Monitoring
U2000
AQM Monitoring
U2000

eNodeB
3 Introduction
Type
Device Monitoring
Transport Performance
Monitoring
Task
Platform
UL Power Control
Monitoring
U2000
DL Power Control
Monitoring
U2000
ICIC (User) Monitoring
U2000
MCS Count Monitoring
U2000
Multi-User BF (User)
Monitoring
U2000
SFN Detection Monitoring
U2000
Cell Combination
Monitoring
U2000
eICIC (User) Monitoring
U2000
DL CoMP (User)
Monitoring
U2000
CPRI BER Monitoring
U2000
CPU Usage Monitoring
U2000&LMT
RRU/RFU/BRU Output
Power Monitoring
U2000
Board Temperature
Monitoring
U2000&LMT
Clock Quality Test

Monitoring
U2000&LMT
IP Clock Data Collection

Monitoring
U2000&LMT
RRU/RFU Output Power

Monitoring
LMT
Rx Frequency Scanning
LMT
DTF Test
LMT
FFT Frequency Scan
LMT
AAS
LMT
Frequency Scanning
Intermodulation Interference
Detection
LMT
Local Pass-By Traffic

Monitoring
U2000&LMT

10
eNodeB
3 Introduction
Type
RRU/RFU Performance
Monitoring
Task
Platform
IP Performance Monitoring
U2000&LMT
Transport Port Flux Stat

Monitoring
U2000&LMT
Transport Link Flux Stat

Monitoring
U2000&LMT
UDP Test Monitoring
U2000
PPPoE Monitoring
U2000&LMT
IPSec Performance
Monitoring
U2000&LMT
Transport OAM Monitoring
LMT
Transport Auto Setup User

Plane Monitoring
U2000&LMT
Sector Performance
Monitoring
LMT
3.3 Precautions
This section describes the precautions for monitoring on 3900 series base stations and
BTS3202Es, BTS3203Es, and BTS3205Es.
NOTE
This issue do not support the following monitoring tasks:

l LTE IP Link Monitoring
l LTE IP Path Performance Monitoring
l LTE SCTP Performance Monitoring
l LTE Resource Group Monitoring
3.3.1 Precautions for Monitoring on 3900 Series Base Stations

3900 series base stations do not support the PPPoE Monitoring task, cell-specific eICIC statistic
for CRE area, or UE-specific eICIC statistic for CRE area. The PPPoE Monitoring task is
available only on BTS3202Es and BTS3203Es. Cell-specific eICIC statistic for CRE area and
UE-specific eICIC statistic for CRE area are available only on BTS3205Es.
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 be reported.
If a monitoring item does not involve the CA feature, actual monitoring result of the monitoring
item is reported.

11
eNodeB
3 Introduction
3.3.2 Precautions for Monitoring on BTS3202Es and BTS3203Es

Take the following precautions for monitoring on BTS3202Es and BTS3203Es:
l
The values of Cabinet No., Subrack No., and Slot No. must be 0.
The value range of Local Cell ID is 0~255.
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
Cell-Level eICIC Statistic for CRE Area
UL CoMP (User) Monitoring
Multi-User BF (User) Monitoring
SFN User Detection
UE-Level eICIC Statistic for CRE Area
DTF Test
AAS
Frequency Scanning Intermodulation Interference Detection Monitoring
BTS3202Es support the following monitoring tasks:

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
Scheduling 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.
In Transport Port Flux Stat Monitoring and Transport Link Flux Stat Monitoring tasks,
Subboard Type must be BASE_BOARD.
3.3.3 Precautions for Monitoring on BTS3205Es

Take the following precautions for monitoring on BTS3205Es:

12
eNodeB
3 Introduction
The values of Cabinet No., Subrack No., and Slot No. must be 0.
The value of Local Cell ID must be 0.
BTS3205Es do not support the following monitoring tasks:

Cell-Level UL CoMP Monitoring
Multi-User MIMO Monitoring
CPRI BER Monitoring
ICIC(Cell)Monitoring
TDD Interference Detection Monitoring
Multi-User BF (Cell) Monitoring
UL CoMP (User) Monitoring
Multi-User BF (User) Monitoring
ICIC(User)Monitoring
SFN User Detection
Cell Combination Monitoring
RRU/RFU Output Power Monitoring
DTF Test
AAS
Frequency Scanning Intermodulation Interference Detection Monitoring
Transport OAM Monitoring
BTS3205Es do not support PPP Performance monitoring and MP Performance monitoring

in the Transport Port Flux Stat Monitoring task.
In Transport Port Flux Stat Monitoring and Transport Link Flux Stat Monitoring tasks,
Subboard Type must be BASE_BOARD.
3.3.4 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:
l
STMSI and Random Value

The ue-Identity IE in the RRC Connection Request message contains the MMEc and mTMSI 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.

13
eNodeB
3 Introduction
NOTE
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 U2000 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 0~16777215 (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).
displayed at the end of the User Trace ID of each tracing and monitoring task, the
Click
U2000 will provide the existing Trace Reference No. on the live network.
NOTE
The U2000 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.
If the eNodeB is not a selected NE for this tracing task, the U2000 cannot continue collecting data. However,
the U2000 can collect the data again when the UE is handed over to the original eNodeB.

14
eNodeB
4 Cell Performance Monitoring
Cell Performance Monitoring
4.1 UL CoMP (Cell) Monitoring

4.1.1 Usage Scenario
This task is used to monitor the number of cell-level UEs using uplink (UL) coordinated multipoint (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.
4.1.2 Service Impact

None.
4.1.3 Parameters
Table 4-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.

15
eNodeB

Table 4-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
U2000 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

CoMP in scenario 2 to the
U2000 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

CoMP in mixed scenario to
the U2000 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.
4.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

16
eNodeB
2 to 4 in a cell based on the throughput. The QoS satisfaction rates of GBR services indicate
whether the QoS requirements of admitted GBR services are met and can be used to determine
the cell load status.

None.
4.2.3 Parameters
Table 4-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, UL QCI1 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)

be set to 50, 100, 200, 500, 1000, or 2000.

Table 4-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
N/A

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

18
eNodeB
Parameter
Unit
Value Range
Description
Formula
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
N/A
Congestion,U
ncongestion
Current congestion state of an

operator when monitoring
results are reported.
N/A
4.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.

19
eNodeB
4.3.3 Parameters
Table 4-5 Parameters for general throughput monitoring
Parameter
Description
Local Cell ID
ID of the cell on which general throughput

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

Monitor Period (ms)

be set to 50, 100, 200, 500, 1000, or 2000.
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.

l
RLC Throughput
Table 4-6 Results of RLC Throughputmonitoring

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

20
eNodeB
Parameter
Unit
Value Range
Description
Formula
Cell Uplink
RLC
Throughput
bps
0 to 300000000
Uplink
throughput of a
cell. Only RLC
payloads are
included. The
RLC headers,
retransmitted
data, and state
reports are
excluded.
(General uplink
RLC throughput
(byte) x 8) x
1000/Monitor
Period (ms)
Cell Downlink
RLC
Throughput
bps
0 to 300000000
Downlink
throughput of a
cell. Only the
RLC payloads
are included.
The RLC
headers,
retransmitted
data, and 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 headers,
retransmitted
data, and state
reports are
excluded.
(Downlink RLC
throughput of an
operator of a cell
(byte) x 8) x
1000/Monitor
Period (ms)

21
eNodeB
RLC Throughput of GBR service
Table 4-7 Results of RLC Throughputof GBR service 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 GBR
Traffic Uplink
RLC
Throughput
bps
0 to 300000000
Uplink
throughput of
GBR services in
a cell. Only RLC
payloads are
included. The
RLC headers,
retransmitted
data, and state
reports are
excluded.
(General RLC
throughput of
uplink GBR
services (Byte)
x 8) x 1000/
Monitor Period
(ms)
Cell GBR
Traffic
Downlink RLC
Throughput
bps
0 to 300000000
Downlink
throughput of
GBR services in
a cell. Only RLC
payloads are
included. The
RLC headers,
retransmitted
data, and state
reports are
excluded.
(General RLC
throughput of
downlink GBR
services (Byte)
x 8) 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 headers,
retransmitted
data, and state
reports are
excluded.
(Uplink GBR
service
throughput of an
operator of a cell
(byte) x 8) x
1000/Monitor
Period (ms)

22
eNodeB
Parameter
Unit
Value Range
Description
Formula
Operator Cell
GBR Traffic
Downlink RLC
Throughput
bps
0 to 300000000
Downlink GBR
service
throughput of an
operator cell.
Only RLC
payloads are
included. The
RLC headers,
retransmitted
data, and 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 4-8 Results of RLC Throughput of NON-GBR service 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 Non-GBR
Traffic Uplink
RLC
Throughput
bps
0 to 300000000
Uplink
throughput of
non-GBR
services in a
cell. Only RLC
payloads are
included. The
RLC headers,
retransmitted
data, and state
reports are
excluded.
(General RLC
throughput of
uplink nonGBR services
(Byte) x 8) x
1000/Monitor
Period (ms)

23
eNodeB
Parameter
Unit
Value Range
Description
Formula
Cell Non-GBR
Traffic
Downlink RLC
Throughput
bps
0 to 300000000
Downlink
throughput of
non-GBR
services in a
cell. Only RLC
payloads are
included. The
RLC headers,
retransmitted
data, and state
reports are
excluded.
(General RLC
throughput of
downlink nonGBR services
(Byte) x 8) x
1000/Monitor
Period (ms)
CN Operator
Cell Non-GBR
Traffic Uplink
RLC
Throughput
bps
0 to 300000000
Uplink
throughput of
non-GBR
services in a CN
operator cell.
Only RLC
payloads are
included. The
RLC headers,
retransmitted
data, and state
reports 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
Downlink
throughput of
non-GBR
services in a CN
operator cell.
Only RLC
payloads are
included. The
RLC headers,
retransmitted
data, and state
reports are
excluded.
General
downlink RLC
throughput of
non-GBR
services in a CN
operator cell
(Byte) x 8) x
1000/Monitor
Period (ms)
4.4 Service Statistics Monitoring

24
eNodeB

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

None.
4.4.3 Parameters
Table 4-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)
Interval of reporting monitoring results. It can be set to 50,

100, 200, 500, 1000, or 2000.

Table 4-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

25
eNodeB
Parameter
Unit
Value Range
Description
Formula
CN Operator ID
N/A
0 to 5
ID of the
operator for
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
monitoring
results are
reported. n
ranges from 1 to
9.
N/A
4.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.
4.5.3 Parameters
Table 4-11 Parameters for user statistics monitoring
Parameter
Description
Test Items
It can be set to Keep UL Synch Users

Number, General Users Number, NOActivated Users Number, or a combination
of some items.
Local Cell ID
ID of the cell on which user statistic


26
eNodeB
Parameter
Description
CN Operator ID

Monitor Period (ms)

be set to 50, 100, 200, 500, 1000, or 2000.

l
Keep UL Synch Users Number

Table 4-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.
CN Operator ID
N/A
0 to 5

user statistic monitoring is
performed.
N/A
CN Operator
Keep UL Synch
Users Number
Number
0 to 2000
Number of users with uplink

synchronization that have
obtained the operator
information 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.

27
eNodeB
General Users Number

Table 4-13 Results of General Users Number monitoring
Paramete
r
Unit
Value
Range
Description
Formula
General
Users
Number
Numbe
r
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 EUTRAN
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
N/A
0 to 5

performed.
N/A
CN
Operator
General
Users
Number
Numbe
r
0 to 2000
Number of users that have

information when the
monitoring result is reported.
These users consist of
connected users and users that
are requesting access to the EUTRAN of an operator.
Number of
connected users
+ Number of
users that are
requesting
access to the EUTRAN
Connected users that have

information consist of active
users and inactive users. Users
that are requesting access to the
E-UTRAN of an operator and
have obtained the operator
information refer to users that
are being handed over to the EUTRAN.
NO-Activated Users Number

28
eNodeB
Table 4-14 Results of NO-Activated Users Number monitoring

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

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-ofsynchronization.
N/A
NOTE
CA users that use the local cell
as their SCell keeping uplink
out-of-synchronization are users
with uplink out-ofsynchronization.
CN Operator
NO-Activated
Users Number
Number
0 to 2000
Number of inactive users that

have obtained the operator
information when monitoring
results are reported. Inactive
users are also known as users
with uplink out-ofsynchronization.
N/A
NOTE
An operator's CA users that use
the local cell as their SCell
keeping uplink out-ofsynchronization are users with
uplink out-of-synchronization.
4.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.

29
eNodeB
4.6.3 Parameters
Table 4-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

Monitor Period (ms)

be set to 50, 100, 200, 500, 1000, or 2000.

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

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

scenario, the number of used
PRBs in each physical cell is
accumulated.
Uplink Equivalent
Used RB Num
Numbe
r
0 to 200000
Number of uplink RBs used

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

accumulated.

30
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Downlink Freq
Diversity Used
RB Num
Numbe
r
0 to 200000
Number of RBs allocated for

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

accumulated.
Downlink Freq
Select Used RB
Num
Numbe
r
0 to 200000

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

accumulated.
Downlink Harq
RB Used RB Num
Numbe
r
0 to 200000

downlink HARQ retransmission
period.
N/A

accumulated.
Downlink power
off RB Num
Numbe
r
0 to 200000
Number of RBs powered off

within all TTIs in a measurement
period after downlink CSPC is
enabled.
N/A
Uplink PUCCH
RB Num
Numbe
r
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 N/A

usage monitoring is performed.
CN Operator
Downlink
Equivalent Used
RB Num
Numbe
r
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.

31
eNodeB
Parameter
Unit
Value
Range
Description
Formula
CN Operator
Uplink Equivalent
Used RB Num
Numbe
r
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.
4.7 ICIC (Cell) Monitoring

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

None.
4.7.3 Parameters
Table 4-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 ofsome items.
Local Cell ID
ID of the cell on which ICIC (cell) monitoring is performed.
Monitor Period (ms)
Interval of reporting monitoring results. It can be set to 50, 100,

200, 500, 1000, or 2000.

l
HII information

32
eNodeB
Table 4-18 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
when
monitoring
results are
reported, which
is the same as
the number of
RBs occupied
by the current
cell bandwidth.
N/A
OI information
Table 4-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
when
monitoring
results are
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 4-20 Results of Proportion of Uplink High Interference RB in System Bandwidth

monitoring
Parameter
Unit
Value Range
Description

Formula
33
eNodeB
Proportion of
Uplink High
Interference RB
in System
Bandwidth
0 to 100
Proportion of
uplink highinterference
RBs in the
serving cell to
RBs occupied
by the current
cell bandwidth
when
monitoring
results are
reported.
N/A
Uplink Edge User RB Information
Table 4-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) when
monitoring
results are
reported.
N/A
Uplink Neighbor Cell List Information
Table 4-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)
when
monitoring
results are
reported.
N/A

34
eNodeB
Cell Downlink Edge Band Information
Table 4-23 Results of Cell Downlink Edge Band Information monitoring

Parameter
Unit
Value Range
Description
Formula
Cell Downlink
Edge Band
Valid RB Num
Number
0 to 100
Number of valid
RBs in the cell
downlink edge
frequency band
when
monitoring
results are
reported.
N/A
4.8 Multi-User MIMO Monitoring

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

None.
4.8.3 Parameters
Table 4-24 Parameters for Multi-User MIMO monitoring
Parameter
Description
Local Cell ID
ID of the cell on which MU-MIMO

Monitor Period (ms)

be set to 1000, 2000.

35
eNodeB

Table 4-25 Results of Multi-User MIMO monitoring
Parameter
Unit
Value Range
Description
Formula
MIMO UE Pair
Num
Pair
0 to 32000
Total number of
UEs paired with
uplink MUMIMO during
all TTIs in the
monitoring
period. Two
UEs paired with
MU-MIMO are
called one pair.
N/A
4.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.
4.9.3 Parameters
Table 4-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.
Local Cell ID
ID of the cell on which interference RSSI

statistic detect monitoring is performed.
Monitor Period (ms)

be set to 50, 100, 200, 500, 1000, or 2000.

36
eNodeB

Table 4-27 Results of RSSI statistic monitoring
Parameter
Unit
Value
Range
Description
Formula
RRU
Cabinet No.
N/A
0 to 62
Number of the
N/A
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.
An invalid value is
displayed as N/A on
the U2000.
RRU
Subrack No.
N/A
4 to 5
60 to 254
Number of the
N/A
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
invalid value in
other scenarios.
An invalid value is
displayed as N/A on
the U2000.

37
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
invalid value in
other scenarios.
N/A
An invalid value is
displayed as N/A on
the U2000.
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.
where
AntNum indicates the number
of antennas for the current cell.
P( QUOTE
) indicates
the receive power of
subcarrier n in RBk received
by antenna AntIdx.
Received
Signal
Strength
Indicator
dBm
-140 to -50
RSSI within the

current system
bandwidth.
where
SysRB indicates the number
of RBs in the current system
bandwidth.

38
eNodeB
Parameter
Unit
Value
Range
Description
Formula
System
Bandwidth
(Number of
RB)
Num
ber
6, 15, 25, 50,

75, 100.
Current system
bandwidth.
N/A
antenna[y]
RSSI
dBm
In
BTS3202Es,
BTS3203Es,
and
BTS3205Es,
the value
range is 25,
50, 75, and
100.
-140 to -50
RSSI for antenna y

within the current
system
bandwidth. y ranges
from 0 to 7.
where
SysRB indicates the number
of RBs in the current system
bandwidth.
P( QUOTE
) indicates the
receive power of subcarrier n
in RBk of antenna AntIdx. The
value of AntIdx is y.
4.10 Interference Detection Monitoring

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

None.

39
eNodeB
4.10.3 Parameters
Table 4-28 Parameters for interference detection monitoring
Parameter
Description
Main eNodeB ID
Local Cell ID
ID of the cell on which interference detection

Monitor Period (ms)

be set to 50, 100, 200, 500, 1000, or 2000.

Table 4-29 Results of interference detection monitoring
Paramet
er
Unit
Value
Range
Description
Formula
RRU
Cabinet
No.
N/A
0 to 62
Number of the cabinet

that houses the RRU
scenarios of SFN and
Cell Combination , and
is set to an invalid value
in other scenarios.
N/A
An invalid value is
displayed as N/A on the
U2000.
RRU
Subrack
No.
N/A
4 to 5
60 to 254
Number of the subrack

that houses the RRU
scenarios of SFN and
Cell Combination, and
is set to an invalid value
in other scenarios.
N/A
An invalid value is
U2000.

40
eNodeB
Paramet
er
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, and is set
to an invalid value in
other scenarios.
N/A
An invalid value is
U2000.
CELL
AVG
Interferen
ce Noise
Power per
RB (dBm)
dBm
PUCCH
Extended
RB
Number
Numb
er
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
of Used
PUCCH
RBs
Numb
er
0 to 26
Maximum number of
RBs occupied by the
PUCCHs of UEs
N/A
System
Bandwidt
h
(Number
of RB)
Numb
er
6, 15, 25, 50,

75, and 100.
Current system
bandwidth.
N/A
-140 to -50
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.
NOTE
In
BTS3202E
s,
BTS3203E
s, and
BTS3205E
s, the value
range is 25,
50, 75, and
100.

41
eNodeB
Paramet
er
Unit
Value
Range
Description
Formula
RBk
Interferen
ce Noise
Power
(dBm)
dBm
-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
AntNum indicates the
number of antennas for the
current cell. IN(AntIdx, k,
nQUOTE) indicates the
receive power of subcarrier
n in RB k received by
antenna AntIdx.
4.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.
4.11.3 Parameters
Table 4-30 Parameters for TDD interference detection monitoring
Parameter
Description
Main eNodeB ID

This parameter can be 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.

42
eNodeB

Table 4-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
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
60 to 254
This parameter
is invalid if the
LBBPc frame
transmitted
upon initiation
of the
monitoring
request does not
have loads.

43
eNodeB
Parameter
Unit
Value Range
Description
Formula
Receive Power
of the 6th (or
4th) Symbol in
First UL
Subframe
dBm
-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
This parameter
is invalid if the
LBBPc frame
transmitted
upon initiation
of the
monitoring
request does not
have loads.
Receive Power
of Symbol 0 in
Last UL
Subframe
dBm
-32768 to
+32767
Receive power
of symbol 0 in
the last uplink
subframe.
N/A
This parameter
is invalid if the
LBBPc frame
transmitted
upon initiation
of the
monitoring
request does not
have loads.

44
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
This parameter
is invalid if the
LBBPc frame
transmitted
upon initiation
of the
monitoring
request does not
have loads.
4.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.
4.12.2 Service Impact on

None.
4.12.3 Parameters
Table 4-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.

45
eNodeB
Parameter
Description
Monitor Period (ms)

be set to 50, 100, 200, 500, 1000, or 2000.

Table 4-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 celllevel
monitoring, the
related RBs of
all RRUs are
counted.
N/A

46
eNodeB
Parameter
Unit
Value Range
Description
Formula
Indep-Indep
Number of
users' successful
pairing Users
Pair
0 to 1000
Number of pairs
of UEs of
independent
scheduling that
have been
successfully
paired using
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
accumulating
the number of
RBs used by a
UE at each TTI
and calculating
the average
number at the
end of the
monitoring
period.
N/A

47
eNodeB
Parameter
Unit
Value Range
Description
Formula
Indep-Joint
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 with
UEs of
combined
scheduling. 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
monitoring, the
related RBs of
all RRUs are
counted.
N/A

48
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
been
successfully
paired using
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
monitoring, the
related RBs of
all RRUs are
counted.
N/A

49
eNodeB
Parameter
Unit
Value Range
Description
Formula
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 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
monitoring, the
related RBs of
all RRUs are
counted.
N/A
4.13 Scheduled Users Statistic Monitoring

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

None.

50
eNodeB
4.13.3 Parameters
Table 4-34 Parameters for scheduled users statistic monitoring
Parameter
Description
Local Cell ID
ID of the cell on which scheduled users

statistic monitoring is performed.
Monitor Period (ms)

be set to 50, 100, 200, 500, 1000, or 2000.

Table 4-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
Total number of
UEs in
downlink
frequency
selective
scheduling
mode within a
monitoring
period.
N/A
Total DLSCH
Diversity Users
Within Monitor
Period
Number
0 to 65535
Total number of
UEs in
downlink
diversity
scheduling
mode within a
monitoring
period.
N/A

51
eNodeB
Parameter
Unit
Value Range
Description
Formula
Total ULSCH
Users Within
Monitor Period
Number
0 to 65535
Total number of
UEs in uplink
scheduling
mode within a
monitoring
period.
N/A
4.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.
4.14.3 Parameters
Table 4-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

Monitor Period (ms)

be set to 1000 or 2000.

l
DL HARQ State

52
eNodeB
Table 4-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

within a monitoring
of NACKs to the total
number of ACKs,
less successfully received
messages from the
eNodeB.
N/A
For details about ACK

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

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.

53
eNodeB
Parameter
Unit
Value
Range
Description
Formula
DL PDSCH
Code[m] DTX
Num
Number
0 to 64000
Number of DTXs for

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}) within a
monitoring period.
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.

54
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

55
eNodeB
Table 4-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,
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
0to 64000
Number of times the CRC

for data blocks on the
PUSCH is incorrect
within a monitoring
of NACKs to the total
number of ACKs,
more the times that the
CRC for the PUSCH data
sent by the UE to the
eNodeB is incorrect.
N/A
UL PUSCH
DTX Num
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,
more the times that the UE
incorrectly demodulates
the downlink PDCCH
data.
N/A

56
eNodeB
Parameter
Unit
Value
Range
Description
Formula
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.
4.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:
l
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.
4.15.3 Parameters
Table 4-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

Monitor Period (ms)

be set to 1000 or 2000.

57
eNodeB

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

Total number of
CCEs in
downlink DCI/
Total number of
CCEs within the
monitoring
period.
Total number of
CCEs in
common DCI/
Total number of
CCEs within the
monitoring
period.
58
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Total CCE Num

Within a
Monitoring
Period
Number
0 to 100000
Total number of CCEs

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
4.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.
4.16.3 Parameters
Table 4-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

Monitor Period (ms)

be set to 1000 or 2000.

59
eNodeB

l
DL DRB STATISTIC
Table 4-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
within a
monitoring
period.
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

60
eNodeB
Parameter
Unit
Value Range
Description
Formula
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
acknowledgme
nt (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
Total number of
times that the
downlink RLC
layer transmits
data in
unacknowledg
ment (UM)
mode within a
monitoring
period.
N/A
Number of Succ
Trans DL PDCP
SDUs with QCI
[n]
Number
0 to
4294967295
Total number of
times that the
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

61
eNodeB
Parameter
Unit
Value Range
Description
Formula
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
UL DRB STATISTIC
Table 4-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

62
eNodeB
Parameter
Unit
Value Range
Description
Formula
Number of UL
TBs With CRC
Incorrect
Number
0 to 300000000
Total number of
times the 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
Total number of
times the 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
Total number of
times the 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 a
monitoring
period.
N/A

63
eNodeB
4.17 Idle MLB Monitoring

This task is used to monitor performance counters on the cell-level mobility load balancing
(MLB) for UEs in idle mode.

None.
4.17.3 Parameters
Table 4-44 Parameters for MLB monitoring for UEs in idle mode
Parameter
Description
Local Cell ID
ID of the cell on which MLB monitoring for UEs in idle mode is

performed.
Monitor Period(m)
Interval of reporting monitoring results. It can be set to 1, 5, 10, 30, or

60.
DlEarfcn
Downlink frequency on which MLB monitoring for UEs in idle mode

is performed.

Table 4-45 Results of MLB monitoring for UEs in idle mode
Parameter
Unit
Value Range
Description
Formula
DlEarfcn
N/A
0 to 45589, 54436
to 65535
Downlink
EARFCNs used in
MLB monitoring for
UEs in idle mode
within a monitoring
period..
N/A

64
eNodeB
Parameter
Unit
Value Range
Description
Formula
Proportion
ReleaseUsers X
N/A
0 to 65535
Proportion of UEs in
idle mode released to
specified frequencies
when InterFreqIdleMlbSwitch is
turned on within a
monitoring period.
N/A
X indicates the
number of
frequencies.
4.18 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.
4.18.3 Parameters
Table 4-46 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.
PLMN ID of local cell
Indicates the ID of the operator where the serving cell

belongs. The default value is empty. The value 0 to 5 can be
entered.
l If you enter a digit in the range 0 to 5, the information at
the operator level is reported.
l If the parameter is left empty or you enter a digit outside
the range 0 to 5, the information at the cell level is
reported.
Ncell 1
Mandatory. For details, see the following table.
Ncell 2
Optional. For details, see the following table.

65
eNodeB
Parameter
Description
Ncell 3
Ncell 4
Table 4-47 Parameters for neighboring cells

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

UTRAN, GERAN, LTEintraFreq, or NULL.
NOTE
l Ncell 1 is mandatory and must not be set to NULL.
l 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 whenNcell Type is set to
LTEinterFreq.
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.

66
eNodeB

Table 4-48 Results of MLB monitoring
Parameter
Unit
Value Range
Description
Formula
Local Cell ID
N/A
0~255
ID of the cell on which

MLB monitoring is
performed.
N/A
PLMN ID of
Local Cell
N/A
0~5
Indicates the ID of the

operator where the
serving cell belongs. N/
A indicates that the
information at the cell
level is monitored, and
the operator ID indicates
that the information at
the operator level is
monitored.
N/A
Serving Cell
uplink GBR
traffic PRB
usage(%)
0 to 100
PRB usage in uplink

GBR services of the
serving cell within a
monitoring period.
N/A
Serving Cell
downlink GBR
traffic PRB
usage(%)
0 to 100
PRB usage in downlink

GBR services of the
monitoring period.
N/A
Serving Cell
uplink NonGBR traffic
PRB usage(%)
0 to 100
PRB usage in uplink

non-GBR services of the
monitoring period.
N/A
Serving Cell
downlink NonGBR traffic
PRB usage(%)
0 to 100

non-GBR services of the
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 Cell
downlink Total
traffic PRB
usage(%)
0 to 100

GBR and non-GBR
services of the serving
cell within a monitoring
period.
N/A

67
eNodeB
Parameter
Unit
Value Range
Description
Formula
Serving Cell
Number of Ue
with downlink
data
Number
0 to 65534
Number of UEs with the

downlink non-GBR
service rate higher than
the specified threshold
at the time of reporting.
Valid values are
displayed only for TDD
cells. The invalid value
N/A is displayed for
FDD cells.
N/A
Serving Cell
uplink PRB
Valuation
N/A
0~65534
Valid values are

cells. The value N/A is
displayed for FDD cells.
N/A
Serving Cell
downlink PRB
Valuation
N/A
0~65534
Valid values are

N/A
Serving Cell
uplink
Available
Capacity
0~100
Valid values are

N/A
Serving Cell
downlink
Available
Capacity
0~100
Valid values are

N/A
Serving Cell
Target
Frequency
Priority for
inter-frequency
MLB
N/A
0~254
Priority of the target

frequency for interfrequency load
balancing.
N/A
Serving Cell
Target
Frequency
Priority for
Utran MLB
N/A
0~254
Priority of the target

UTRAN frequency for
inter-RAT load sharing
to UTRAN.
N/A

68
eNodeB
Parameter
Unit
Value Range
Description
Formula
Serving Cell UE
number of Interfrequency MLB
Redirection
Number
0~254
Number of UEs
redirected to the target
cell for inter-frequency
load balancing. The
number is cleared after
UEs exit MLB. Valid
values are displayed
only for TDD cells. The
invalid value N/A is
N/A
Serving Cell UE
number of
UtranMLB
Redirection
Number
0~254
Number of UEs
UTRAN cell for interRAT load sharing to
UTRAN. The number is
cleared after UEs exit
MLB.
N/A
Serving Cell UE
number of
GeranMLB
Redirection
Number
0~254
Number of UEs
GERAN cell for interRAT load sharing to
GERAN. The number is
MLB.
N/A

69
eNodeB
Parameter
Unit
Value Range
Description
Formula
Serving Cell UE
number of Interfrequency
IdleMLB
Number
0~254
Number of UEs in idle

mode in the operatorlevel transferred during
inter-frequency load
balancing for UEs in
idle mode if the PLMN
ID of local cell
parameter value is not
N/A. Number of UEs in
idle mode in the celllevel transferred during
inter-frequency load
idle mode if the PLMN
ID of local cell
parameter value is N/A.
N/A

mode transferred to the
target cell for interfrequency load
idle mode. The number
is cleared after UEs exit
MLB.
Serving Cell UE
number of
UtranIdleMLB
Number
0~254

mode transferred to the
target UTRAN cell for
inter-RAT load sharing
for UEs in idle mode.
The number is cleared
after UEs exit MLB.

N/A
70
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 intrafrequency MLB.
N/A
BIT0:
UlGBRIntraM
LB
BIT1:
DlGBRIntraM
LB
BIT2:
UlNonGBRIn
traMLB
BIT3:
DlNonGBRIn
traMLB
BIT4:
UlTotalIntra
MLB
BIT5:
DlTotalIntra
MLB
If the value of
a bit is 0, the
intrafrequency
MLB is not
triggered by
the cause
specified by
the bit. If the
value of a bit is
1, the intrafrequency
MLB is
triggered by
the cause

71
eNodeB
Parameter
Unit
Value Range
Description
Formula
specified by
the bit.
If a GUI value
is 8, and the
corresponding
binary value is
001000, the
intrafrequency
MLB is
caused by
DlNonGBRI
ntraMLB.

72
eNodeB
Parameter
Unit
Value Range
Description
Formula
Inter-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 interfrequency MLB.
N/A
0:
InterMLBNot
Triggered
BIT0:
UlGBRInterM
LB
BIT1:
DlGBRInterM
LB
BIT2:
UlNonGBRIn
terMLB
BIT3:
DlNonGBRIn
terMLB
BIT4:
UlTotalInter
MLB
BIT5:
DlTotalInter
MLB
BIT6:
ActiveUeNum
MLB
BIT7:
IdleOffloadM
LB
BIT8:
DlDataUeNu
mMLB

73
eNodeB
Parameter
Unit
Value Range
Description
Formula
BIT9:
UlPRBValML
B
BIT10:
DlPRBValML
B
If the value of
a bit is 0, the
interfrequency
MLB is not
triggered by
the cause
specified by
the bit. If the
value of a bit is
1, the interfrequency
MLB is
triggered by
the cause
specified by
the bit.
If a GUI value
is 8, and the
corresponding
binary value is
001000, the
intrafrequency
MLB is
caused by
DlNonGBRI
nterMLB.

74
eNodeB
Parameter
Unit
Value Range
Description
Formula
Utran 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 interRAT MLB to UTRAN.
N/A
0:
UtranMLBNo
tTriggered
BIT0:
UlGBRUtran
MLB
BIT1:
DlGBRUtran
MLB
BIT2:
UlNonGBRUt
ranMLB
BIT3:
DlNonGBRUt
ranMLB
BIT4:
UlTotalUtran
MLB
BIT5:
DlTotalUtran
MLB
BIT6:
ActiveUeNum
MLB
BIT7:
IdleOffloadM
LB
If the value of
a bit is 0, the
MLB to
UTRAN is not
triggered by

75
eNodeB
Parameter
Unit
Value Range
Description
Formula
the cause
specified by
the bit. If the
value of a bit is
1, the MLB to
UTRAN is
triggered by
the cause
specified by
the bit. If a
GUI value is 8,
and the
corresponding
binary value is
001000, the
MLB to
UTRAN is
caused by
DlNonGBRU
tranMLB.

76
eNodeB
Parameter
Unit
Value Range
Description
Formula
Geran 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 inter-RAT

MLB to GERAN.
N/A
NOTE
BTS3202Es,
BTS3203Es, and
BTS3205Esdo not
support this monitoring
item.
0:
GeranMLBNo
tTriggered
BIT0:
UlGBRGeran
MLB
BIT1:
DlGBRGeran
MLB
BIT2:
UlNonGBRG
eranMLB
BIT3:
DlNonGBRG
eranMLB
BIT4:
UlTotalGeran
MLB
BIT5:
DlTotalGeran
MLB
If the value of
a bit is 0, 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

77
eNodeB
Parameter
Unit
Value Range
Description
Formula
the cause
specified by
the bit.
If a GUI value
is 8, and the
corresponding
binary value is
001000, the
MLB to
GERAN is
caused by
DlNonGBRG
eranMLB.
Serving Cell
number of
Admission
Failure for
Optimisation
Handover-in
Number
0 to 254
Number of admission
failures for
optimization-based
handover attempts to the
local cell within a
measurement period.
Valid values are
N/A
Intra-frequency
cell number
Number
0 to 4
The number of the intrafrequency cells.
N/A
LTEintra NCell
MCC
N/A
Depending on
eNodeB
configuration
Mobile country code of

a neighboring intrafrequency cell.
N/A
LTEintra NCell
MNC
N/A
Depending on
eNodeB
configuration
Mobile network code of

a neighboring intrafrequency cell.
N/A
LTEintra NCell
eNodeB ID
N/A
Depending on
eNodeB
configurations
ID of the eNodeB
serving a neighboring
intra-frequency cell.
N/A
LTEintra NCell
Cell ID
N/A
Depending on
eNodeB
ID of a neighboring
N/A
Ue number in
the edge of the
serving cell near
to the intrafrequency cell
Number
0 to 254
Number of cell edge

UEs near a neighboring
N/A

78
eNodeB
Parameter
Unit
Value Range
Description
Formula
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
1: Serving cell
spring to
modify
2: Serving cell
spring to
comeback
3: Serving cell
spring to quit
MLB
4: Serving cell
respond to
modify
5: Serving cell
respond to
comeback
6: Serving cell
respond to quit
MLB
IntraFrequency cell
uplink GBR
traffic PRB
usage(%)
0 to 100
PRB usage in uplink

GBR services target of
the intra-frequency cell.
N/A
IntraFrequency cell
downlink GBR
traffic PRB
usage(%)
0 to 100

GBR services in the
target intra-frequency
cell.
N/A
IntraFrequency cell
PRB usage(%)
0 to 100
PRB usage in uplink

non-GBR services in the
cell.
N/A

79
eNodeB
Parameter
Unit
Value Range
Description
Formula
IntraFrequency cell
PRB usage(%)
0 to 100

cell.
N/A
IntraFrequency cell
uplink Total
traffic PRB
usage(%)
0 to 100
PRB usage in uplink

GBR and non-GBR
services in the target
N/A
IntraFrequency cell
downlink Total
traffic PRB
usage(%)
0 to 100

GBR and non-GBR
N/A

80
eNodeB
Parameter
Unit
Value Range
Description
Formula
Cause of IntraFrequency cell

not being MLB
cell
N/A
0 to 30
Cause of a neighboring
intra-frequency cell not
being selected as an
MLB cell.
N/A
0: Null
1:
Algo_Not_tri
ggered
2:
NO_X2_Link
3:
HO_Unallowe
d
4:
PCI_Conflic
5:
History_Succ
_Ratio_Low
6:
Invalid_Ncell
7:
Ncell_Black
8:
Ncell_Energy
_Saving
9:
Resource_Stat
us_not_Recei
ved
10:
Current_Succ
_Ratio_Low
11:
Hardware_Lo
ad_high
12: S1_TNL
Load_high
13:
Ncell_Radio_
Resource_Un
meet
15: Pci_Fail
16: App_Fail

81
eNodeB
Parameter
Unit
Value Range
Description
Formula
17:
Ncell_IntraM
LB_Sw_Off
18:
Margin_Ue_N
um_Unmeet
19:
Cio_Adjust_
Max
21:
Best_Cell_Un
meet
22:
Dont_Sel_intr
a_eNB_ncell_
for_inter_eNB
_MLB
23:
Ncell_Deactiv
e
24:
Margin_Ue_N
um_Unmeet
25:
Dont_Sel_intr
a_eNB_ncell_
for_inter_eNB
_MLB
26:
Null_Overlap
_Ncell
27:
Frequency_N
ot_Allowed
28:
Be_Punished
29:
Ncell_Not_Cf
g_Operater
30:
Be_Punished_
for_MLB_Pri
ority

82
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
N/A
UE number of
MLB handover
to the intrafrequency 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
Inter-frequency
cell number
Number
0 to 4
The number of the interfrequency cell number.
N/A
LTEinter NCell
MCC
N/A
Depending on
eNodeB
configuration

a neighboring interfrequency cell.
N/A
LTEinter NCell
MNC
N/A
Depending on
eNodeB
configuration

a neighboring interfrequency 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 NCell
Cell ID
N/A
Depending on
eNodeB
configurations
ID of a neighboring
N/A
InterFrequency cell
uplink GBR
traffic PRB
usage(%)
0 to 100
PRB usage in uplink

GBR services in the
target inter-frequency
cell.
N/A
InterFrequency cell
downlink GBR
traffic PRB
usage(%)
0 to 100

GBR services in the
cell.
N/A
InterFrequency cell
PRB usage(%)
0 to 100
PRB usage in uplink

cell.
N/A

83
eNodeB
Parameter
Unit
Value Range
Description
Formula
InterFrequency cell
PRB usage(%)
0 to 100

cell.
N/A
InterFrequency cell
uplink Total
traffic PRB
usage(%
0 to 100
PRB usage in uplink

GBR and non-GBR
N/A
InterFrequency cell
downlink Total
traffic PRB
usage(%)
0 to 100

GBR and non-GBR
N/A
Inter-Freqency
cell number of
Ue with
downllink data
Number
0 to 65534
Number of UEs in the

inter-frequency target
cell with the downlink
non-GBR service rate
higher than the specified
threshold at the time of
reporting. Valid values
are displayed only for
TDD cells. An invalid
value 65535 is displayed
for FDD cells.
N/A
Inter-Freqency
cell MLB Ue
seletion of
location
N/A
Value:
Location selection
strategy for MLB UEs.
N/A
0: Null
1: inner first
2: outer first

84
eNodeB
Parameter
Unit
Value Range
Description
Formula
Cause of InterFrequency cell

not being MLB
cell
N/A
0 to 30
Cause of InterFrequency cell not being

selected as MLB cell.
N/A
0: Null
1:
Algo_Not_tri
ggered
2:
NO_X2_Link
3:
HO_Unallowe
d
4:
PCI_Conflic
5:
History_Succ
_Ratio_Low
6:
Invalid_Ncell
7:
Ncell_Black
8:
Ncell_Energy
_Saving
9:
Resource_Stat
us_not_Recei
ved
10:
Current_Succ
_Ratio_Low
11:
Hardware_Lo
ad_high
12: S1_TNL
Load_high
13:
Ncell_Radio_
Resource_Un
meet
15: Pci_Fail
16: App_Fail

85
eNodeB
Parameter
Unit
Value Range
Description
Formula
17:
Ncell_IntraM
LB_Sw_Off
18:
Margin_Ue_N
um_Unmeet
19:
Cio_Adjust_
Max
21:
Best_Cell_Un
meet
22:
Dont_Sel_intr
a_eNB_ncell_
for_inter_eNB
_MLB
23:
Ncell_Deactiv
e
24:
Margin_Ue_N
um_Unmeet
25:
Dont_Sel_intr
a_eNB_ncell_
for_inter_eNB
_MLB
26:
Null_Overlap
_Ncell
27:
Frequency_N
ot_Allowed
28:
Be_Punished
29:
Ncell_Not_Cf
g_Operater
30:
Be_Punished_
for_MLB_Pri
ority

86
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
N/A
UE number of
MLB transfer
load control for
the interfrequency cell
Number
0 to 254
Number of UEs entering

MLB transfer load
control for the interfrequency cell. The
value becomes 0 after
UEs exit MLB.
N/A
UE number of
MLB handover
to the interfrequency cell
Number
0 to 254
Number of UEs handed

over to the interfrequency cell for MLB
after the UE enters MLB
transfer load control.
The value becomes 0
after UEs exit MLB.
N/A
Downlink data
UE number of
MLB handover
to the interfrequency cell
Number
0 to 254

over to the interfrequency cell for MLB
after the UE enters
downlink data
transmission MLB
The value becomes 0
after UEs exit downlink
data transmission MLB.
Valid values are
cells. An invalid value
65535 is displayed for
FDD cells.
N/A

87
eNodeB
Parameter
Unit
Value Range
Description
Formula
Downlink data
priority UE
number of MLB
handover to the
inter-frequency
cell
Number
0 to 254
Number of prioritized
UEs handed over to the
inter-frequency cell for
MLB after the UE enters
downlink data
transmission MLB
The value becomes 0
after UEs exit downlink
data transmission MLB.
Valid values are
cells. An invalid value
65535 is displayed for
FDD cell.
N/A
Active UE
number of MLB
handover to the
inter-frequency
cell
Number
0 to 254
Number of UEs selected

for inter-frequency load
balancing based on PRB
usage. This number is
PRB-based interfrequency load
balancing. Valid values
are displayed only for
TDD cells. The value N/
A is displayed for FDD
cells.
N/A
Utran cell
number
Number
0 to 4
Number of the UTRAN

cells.
N/A
UTRAN NCell
MCC
N/A
Depending on
eNodeB
configurations

a neighboring UTRAN
cell.
N/A
UTRAN NCell
MNC
N/A
Depending on
eNodeB
configurations

a neighboring UTRAN
cell.
N/A
UTRAN NCell
RNC ID
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

88
eNodeB
Parameter
Unit
Value Range
Description
Formula
Utran Cell load

Status
N/A
0: Overload
Load status of a
neighboring UTRAN
cell.
N/A
1: Congestion
2: Normal
3: MidLoad
4: Invalid

89
eNodeB
Parameter
Unit
Value Range
Description
Formula
Cause of utran
cell not being
MLB cell
N/A
0 to 30
UTRAN cell not being
selected as the MLB
cell.
N/A
0: Null
1:
Algo_Not_tri
ggered
2:
NO_X2_Link
3:
HO_Unallowe
d
4:
PCI_Conflic
5:
History_Succ
_Ratio_Low
6:
Invalid_Ncell
7:
Ncell_Black
8:
Ncell_Energy
_Saving
9:
Resource_Stat
us_not_Recei
ved
10:
Current_Succ
_Ratio_Low
11:
Hardware_Lo
ad_high
12: S1_TNL
Load_high
13:
Ncell_Radio_
Resource_Un
meet
15: Pci_Fail
16: App_Fail

90
eNodeB
Parameter
Unit
Value Range
Description
Formula
17:
Ncell_IntraM
LB_Sw_Off
18:
Margin_Ue_N
um_Unmeet
19:
Cio_Adjust_
Max
21:
Best_Cell_Un
meet
22:
Dont_Sel_intr
a_eNB_ncell_
for_inter_eNB
_MLB
23:
Ncell_Deactiv
e
24:
Margin_Ue_N
um_Unmeet
25:
Dont_Sel_intr
a_eNB_ncell_
for_inter_eNB
_MLB
26:
Null_Overlap
_Ncell
27:
Frequency_N
ot_Allowed
28:
Be_Punished
29:
Ncell_Not_Cf
g_Operater
30:
Be_Punished_
for_MLB_Pri
ority

91
eNodeB
Parameter
Unit
Value Range
Description
Formula
UE number of
MLB handover
to the utran cell
Number
0 to 254

over to the UTRAN cell
for MLB. The value
becomes 0 after UEs
exit MLB.
N/A
Geran cell
number
Number
0 to 4
Number of neighboring
GERAN cells to be
monitored.
GSM NCell
MCC
N/A
Depending on
eNodeB
configuration

a neighboring GERAN
cell.
N/A
GSM NCell
MNC
N/A
Depending on
eNodeB
configuration

a neighboring GERAN
cell.
N/A
GSM NCell
Geran ID
N/A
Depending on
eNodeB
configuration
ID of a neighboring
GERAN cell.
N/A
GSM NCell
Geran Lac
N/A
Depending on
eNodeB
configuration
Location area code of a

neighboring GERAN
cell.
N/A
Cause of geran
cell not being
MLB cell
N/A
0: Null
GERAN cell not being
selected as the MLB
cell.
N/A
UE number of
MLB handover
to the geran cell
Number

over to the GERAN cell
for MLB. The value
becomes 0 after UEs
exit MLB.
N/A
1:
Algo_Not_tri
ggered
0 to 254
4.19 eICIC CEU Throughput Monitoring

This task monitors performance counters on the cell-level eICIC cell edge user (CEU)
throughput, thereby determining whether the eNodeBs or eICIC CEUs successfully transmit
data.

92
eNodeB

None.
4.19.3 Parameters
Table 4-49 Parameters for eICIC CEU throughput monitoring
Parameter
Description
Local Cell ID
ID of the cell on which eICIC CEU

throughput monitoring is performed.
Test Items
This parameter can be set to eICIC CEU

RLC Throughput, eICIC CEU RLC
Throughput of GBR service, and eICIC
CEU RLC Throughput of NON-GBR
service. Multiple items can be selected at a
time.
Monitor Period (ms)

be set to 1000 or 2000.

l
eICIC CEU RLC Throughput
Table 4-50 Parameters for general uplink and downlink RLC throughput monitoring for eICIC
CEUs
Parameter
Unit
Value Range
Description
Formula
Uplink eICIC
CEU RLC
Throughput
bps
0 to 300000000
Uplink RLC throughput

for eICIC CEUs, including
the RLC payload only.
Uplink eICIC
CEU RLC
Throughput
(byte) x 8/
Monitor Period
(ms) x 1000
Downlink
eICIC CEU
RLC
Throughput
bps
0 to 300000000
Downlink RLC
throughput for eICIC
CEUs, including the RLC
payload only.
Downlink
eICIC CEU
RLC
Throughput
(byte) x 8/
Monitor Period
(ms) x 1000

93
eNodeB
eICIC CEU RLC Throughput of GBR service
Table 4-51 Parameters for general uplink and downlink GBR service RLC throughput
monitoring for eICIC CEUs
Parameter
Unit
Value Range
Description
Formula
GRB Traffic
Uplink eICIC
CEU RLC
Throughput
bps
0 to 300000000
General uplink GBR

service RLC throughput
GRB Traffic
Uplink eICIC
CEU RLC
Throughput
(byte) x 8/
Monitor Period
(ms) x 1000
GRB Traffic
Downlink
HetNet eICIC
CEU RLC
Throughput
bps
0 to 300000000
General downlink GBR

GRB Traffic
Downlink
eICIC CEU
RLC
Throughput
(byte) x 8/
Monitor Period
(ms) x 1000
eICIC CEU RLC Throughput of NON-GBR service
Table 4-52 Parameters for general uplink and downlink non-GBR service RLC throughput
monitoring for eICIC CEUs
Parameter
Unit
Value Range
Description
Formula
Non-GRB
Traffic Uplink
HetNet eICIC
CEU RLC
Throughput
bps
0 to 300000000
General uplink non-GBR

Non-GRB
Traffic Uplink
HetNet eICIC
CEU RLC
Throughput
(byte) x 8/
Monitor Period
(ms) x 1000
Non-GRB
Traffic
Downlink
HetNet eICIC
CEU RLC
Throughput
bps
0 to 300000000
General downlink nonGBR service RLC

throughput for eICIC
CEUs, including the RLC
payload only.
Non-GRB
Traffic
Downlink
HetNet eICIC
CEU RLC
Throughput
(byte) x 8/
Monitor Period
(ms) x 1000

94
eNodeB
4.20 eICIC Statistic for CRE Area Monitoring

This task is used to monitor cell-level eICIC statistics for CRE area, including the number of
PRBs scheduled in ABS subframes and that scheduled in non-ABS subframes, and the times of
reporting the CQI that indicates the channel quality of ABS or non-ABS subframes.

None
4.20.3 Parameters
Table 4-53 Parameters for cell-level eICIC statistics for CRE area
Parameter
Description
Test Items
It can be set to Average PRBs Used In ABS

For CRE, Average PRBs Used In Non-ABS
For CRE, Number of ABS CQI of 0~15 For
CRE, Number of Non-ABS CQI of 0~15
For CRE, or a combination of some items.
Local Cell ID
ID of the cell on which cell-level eICIC

statistics for CRE area monitoring is
performed
Monitor Period(ms)

be set to 1000 or 2000.

Table 4-54 Results of cell-level eICIC statistics for CRE area monitoring
Parameter
Unit
Value
Range
Description
Formula
Average PRBs
Used in ABS
Number
0 to 100
Average number of
PRBs scheduled in ABS
subframes for UEs
enabled with the eICIC
function in the CRE
area
N/A

95
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Average PRBs
Used in NonABS
Number
0 to 100
Average number of
PRBs scheduled in nonABS subframes for UEs
enabled with the eICIC
function in the CRE
area
N/A
Number Of
ABS CQI 0 For
CRE
Number
0 to 480000
Number of times when

eICIC-enabled UEs in
the CRE area report
CQIs of 0 in ABS
subframes
N/A
Number Of
ABS CQI 1 For
CRE
Number
0 to 480000

the CRE area report
CQIs of 1 in ABS
subframes
N/A
Number Of
ABS CQI 2 For
CRE
Number
0 to 480000

the CRE area report
CQIs of 2 in ABS
subframes
N/A
Number Of
ABS CQI 3 For
CRE
Number
0 to 480000

the CRE area report
CQIs of 3 in ABS
subframes
N/A
Number Of
ABS CQI 4 For
CRE
Number
0 to 480000

the CRE area report
CQIs of 4 in ABS
subframes
N/A
Number Of
ABS CQI 5 For
CRE
Number
0 to 480000

the CRE area report
CQIs of 5 in ABS
subframes
N/A
Number Of
ABS CQI 6 For
CRE
Number
0~480000

the CRE area report
CQIs of 6 in ABS
subframes
N/A

96
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Number Of
ABS CQI 7 For
CRE
Number
0 to 480000

the CRE area report
CQIs of 7 in ABS
subframes
N/A
Number Of
ABS CQI 8 For
CRE
Number
0 to 480000

the CRE area report
CQIs of 8 in ABS
subframes
N/A
Number Of
ABS CQI 9 For
CRE
Number
0 to 480000

the CRE area report
CQIs of 9 in ABS
subframes
N/A
Number Of
ABS CQI 10 For
CRE
Number
0 to 480000

the CRE area report
CQIs of 10 in ABS
subframes
N/A
Number Of
ABS CQI 11 For
CRE
Number
0 to 480000

the CRE area report
CQIs of 11 in ABS
subframes
N/A
Number Of
ABS CQI 12 For
CRE
Number
0 to 480000

the CRE area report
CQIs of 12 in ABS
subframes
N/A
Number Of
ABS CQI 13 For
CRE
Number
0 to 480000

the CRE area report
CQIs of 13 in ABS
subframes
N/A
Number Of
ABS CQI 14 For
CRE
Number
0 to 480000

the CRE area report
CQIs of 14 in ABS
subframes
N/A

97
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Number Of
ABS CQI 15 For
CRE
Number
0 to 480000

the CRE area report
CQIs of 15 in ABS
subframes
N/A
Number Of nonABS CQI 0 For

CRE
Number
0 to 480000

the CRE area report
CQIs of 0 in non-ABS
subframes
N/A

CRE
Number
0 to 480000

the CRE area report
subframes
N/A

CRE
Number
0 to 480000

the CRE area report
subframes
N/A

CRE
Number
0 to 480000

the CRE area report
subframes
N/A

CRE
Number
0 to 480000

the CRE area report
subframes
N/A

CRE
Number
0 to 480000

the CRE area report
subframes
N/A

CRE
Number
0 to 480000

the CRE area report
subframes
N/A

98
eNodeB
Parameter
Unit
Value
Range
Description
Formula

CRE
Number
0 to 480000

the CRE area report
subframes
N/A

CRE
Number
0 to 480000

the CRE area report
subframes
N/A

CRE
Number
0 to 480000

the CRE area report
subframes
N/A

CRE
Number
0 to 480000

the CRE area report
subframes
N/A

CRE
Number
0 to 480000

the CRE area report
subframes
N/A

CRE
Number
0 to 480000

the CRE area report
subframes
N/A

CRE
Number
0 to 480000

the CRE area report
subframes
N/A

CRE
Number
0 to 480000

the CRE area report
subframes
N/A

99
eNodeB
Parameter
Unit
Value
Range
Description
Formula

CRE
Number
0 to 480000

the CRE area report
subframes
N/A
4.21 DL CoMP (Cell) Monitoring

This task is used to monitor the number of UEs in a cell enabled with DL CoMP. This task
measures JT User Num, CBF User Num, DCS User Num, JT User Schedule RB Num, CBF
User Schedule RB Num, and DCS User Schedule RB Num.

None
4.21.3 Parameters
Table 4-55 Parameters for DL CoMP (cell) monitoring
Parameter
Description
Local Cell ID
ID of the local cell where monitoring for DL CoMP is performed at the

cell level
Monitor Period
(ms)
Interval of reporting monitoring results. It can be set to 1000 or 2000.

Table 4-56 Results of DL CoMP (Cell) monitoring
Parameter
Unit
Value Range
Description
Formula
JT User Num
Num
ber
0 to 1000
Number of JT UEs in a cell
N/A
CBF User Num
Num
ber
0 to 1000
Number of CBF UEs in a cell
N/A

100
eNodeB
Parameter
Unit
Value Range
Description
Formula
DCS User Num
Num
ber
0 to 1000
Number of DCS UEs in a cell
N/A
JT User
Schedule RB
Num
Num
ber
0 to 200000
Number of paired RBs for JT UEs
N/A
CBF User
Schedule RB
Num
Num
ber
0 to 200000
Number of paired RBs for CBF

UEs
N/A
DCS User
Schedule RB
Num
Num
ber
0 to 200000
Number of paired RBs for DCS

UEs
N/A
4.22 Cell-Level Interference Randomization

This task is used to monitor the start position of an RB used for scheduling when the interference
randomization function is enabled.

None
4.22.3 Parameters
Table 4-57 Parameters for cell-level interference randomization monitoring
Parameter
Description
Local Cell ID
ID of the local cell where interference randomization is performed at

the cell level
Monitor Period
(ms)
Interval of reporting monitoring results. It can be set to 1000 or 2000.

101
eNodeB

Table 4-58 Results of cell-level interference randomization monitoring
Parameter
Unit
Value Range
Description
Formula
Schedule RB
Start
N/A
0 to 99
The start position of an RB used

for scheduling
N/A

102
eNodeB
5 User Performance Monitoring
User Performance Monitoring
5.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.
5.1.3 Parameters
Table 5-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

to STMSI.
Random Value

to Random Value.
PLMN

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

to Trace Reference No.

103
eNodeB
Parameter
Description
Monitor Period (ms)

2000.

Table 5-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:
N/A
l Normal User
l UL CoMP
User of
Scenario 1
l UL CoMP
User of
Scenario 2
l UL CoMP
User of
mixed
Scenario
5.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.

104
eNodeB
5.2.3 Parameters
Table 5-3 Parameters for VQI monitoring
Parameter
Description
UEID Type

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

l
DL Quality of Voice monitoring
Table 5-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

105
eNodeB
Monitoring
Results
Unit
Value Range
Description
Formula
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 5-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

106
eNodeB
5.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:
l
Calculate loss on the downlink to facilitate the analysis of drive test (DT) data.
Preliminarily detect and isolate network coverage problems.

None.
5.3.3 Parameters
Table 5-6 Parameters for DL RSRP/RSRQ monitoring
Parameter
Description
UEID Type
It can be set to STMSI, Random Value, or Trace

Reference No.
MMEc

to STMSI.
mTMSI

to STMSI.
Random Value

to Random Value.
PLMN

MCC and MNC specify the mobile country code and
mobile network code, respectively.
User Trace ID

Monitor Period (ms)

120, 240, 480, 640, 1024, or 2048.

107
eNodeB

Table 5-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.5to -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
NOTE
maximum of eight
N/A
NeighborCell
RSRQ[n]
dB
-19.5 to -3
NOTE
maximum of eight
N/A
5.4 BLER Monitoring

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

None.

108
eNodeB
5.4.3 Parameters
Table 5-8 Parameters for BLER monitoring
Parameter
Description
UEID Type

No.
MMEc

to STMSI.
mTMSI

to STMSI.
Random Value

to Random Value.
PLMN

User Trace ID

Monitor Period (ms)

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

l
Init BLER
Table 5-9 Results of Init BLER 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
Physical cell
identifier of the
serving cell.
N/A

109
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
0to 1000
BLER of initial
TB transmission
on a PUSCH
within a
monitoring
period.
Total number of
TBs that fail to
be initially
transmitted on
the PUSCH x
1000/Total
number of
initially
transmitted TBs
on the PUSCH
within the
monitoring
period
Resident BLER
Table 5-10 Results of Resident BLER 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
Physical cell
identifier of the
serving cell.
N/A

110
eNodeB
Parameter
Unit
Value Range
Description
Formula
Downlink
RBLER
0to 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
transmitted TBs
on the PDSCH
within the
monitoring
period
Uplink RBLER
0to 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
transmitted TBs
on the PUSCH
within the
monitoring
period
PDCCH BLER
Table 5-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 result
contains Non
CA, CA PCell
and CA SCell.
N/A
Physical Cell
Identifier
N/A
0 to 503
Physical cell
identifier of the
serving cell.
N/A

111
eNodeB
Parameter
Unit
Value Range
Description
Formula
PDCCH BLER
0to 1000
BLER of
DLGRANT
decoding on a
PDCCH within
a monitoring
period.
Number of
times
DLGRANTs
decoded
incorrectly x
1000/Total
number of
DLGRANTs
sent on a
PDCCH
The number of
DLGRANTs
decoded
incorrectly is the
number of
DTXs that were
the feedback
given to the
DLGRANTs
sent on a
PDCCH.
5.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.
5.5.3 Parameters
Table 5-12 Parameters for power headroom monitoring
Parameter
Description
UEID Type
It can be set to STMSI, Random Value, or

Trace Reference No.

112
eNodeB
Parameter
Description
MMEc
It must be configured when the UEID Type

parameter is set to STMSI.
mTMSI

parameter is set to STMSI.
Random Value

parameter is set to Random Value.
PLMN

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

parameter is set to Trace Reference No.
Monitor Period (ms)

be set to 50, 100, 200, 500, 1000, or 2000.

Table 5-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
Physical Cell
Identifier
N/A
0 to 503
Physical cell
identifier of the
serving cell.
N/A

113
eNodeB
Parameter
Unit
Value Range
Description
Formula
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.
5.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.
5.6.3 Parameters
Table 5-14 Parameters for quality of channel monitoring
Parameter
Description
UEID Type

No.
MMEc

to STMSI.
mTMSI

to STMSI.
Random Value

to Random Value.
PLMN


114
eNodeB
Parameter
Description
User Trace ID

Monitor Period (ms)

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

ULSRS RSRP. All items are monitored by default.

l
UL SINR & UL DMRS RSRP
Table 5-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
contains Non
CA, CA PCell
and CA SCell.
N/A
Physical Cell
Identifier
N/A
0 to 503
Physical cell
identifier of the
serving cell.
N/A
SINR
0.01dB
-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 DMRS
reference signal
received power.
N/A
CQI

115
eNodeB
Table 5-16 Results of CQI 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
Physical cell
identifier of the
serving cell.
N/A
UE Code Count
Number
1to 2
Number of
transmitted
code words in
the downlink
when
monitoring
results are
reported.
N/A
Code Index
N/A
0 to 3
Index of the UE
codeword.
N/A
Effective Len
ms
N/A
Valid length of
the aperiodic
CQI for the full
bandwidth. This
parameter takes
effect only when
the aperiodic
CQI frequency
selection is
configured.
N/A
CQI
N/A
0to 15
Four-bit value
mapped to the
originally
reported CQI for
the full
bandwidth.
N/A
UL SRS RSRP

116
eNodeB
Table 5-17 Results of UL SRS RSRP

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~503
Physical cell ID
of a serving cell.
N/A
ServCell UL
SRS RSRP
0.01dBm
-15000 ~ -3000
RSRP of a
serving cell.
N/A
NeighborCell
PCI[n]
N/A
0~503
Physical cell ID
of the nth
neighboring
cell.
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.
Neighbor Cell
UL SRS RSRP
0.01dBm
-15000 ~ -3000
NOTE
This field
specifies the
sequence for
reporting the
measurement
reports of
neighboring
cells. A
maximum of
eight
neighboring
cells are
dynamically
displayed.

117
eNodeB
5.7 Scheduling Monitoring

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

None.
5.7.3 Parameters
Table 5-18 Parameters for scheduling monitoring
Parameter
Description
UEID Type
It can be set to STMSI, Random Value, or Trace

Reference No.
MMEc

to STMSI.
mTMSI

to STMSI.
Random Value

to Random Value.
PLMN

User Trace ID

Monitor Period (ms)

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

118
eNodeB

l
UL SR of Service
Table 5-19 Results of UL SR 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
Physical cell
identifier of the
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

119
eNodeB
Table 5-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
Physical cell
identifier of the
serving cell.
N/A
Byte Length of
LCG BS[n]
Bit
0 to 3000000
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

120
eNodeB
Table 5-21 Results of Percentage of DRX activity timer in DRX timer 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
Physical cell
identifier of the
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
For details, see

3GPP TS
36.213.
TTIs in DRX
State
Number
0 to
4294967295
Number of
accumulated
TTIs in the DRX
state during the
monitoring
period.
N/A
For details, see

3GPP TS
36.321.
Number of TTI
Number
0 to
4294967295
Number of
accumulated
TTIs between
the
establishment
and the release
of an L2 case.
N/A
5.8 RLC Data Stream Monitoring

121
eNodeB

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.
5.8.3 Parameters
Table 5-22 Parameters for RLC data stream 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
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.

Table 5-23 Result of RLC data stream monitoring
Parameter
Unit
Value Range
Description
Formula
Physical Cell
Identifier
N/A
0 to 503
Physical cell
identifier of the
serving cell.
N/A
DRB No.
N/A
1 to 8
Number of the
DRB.
N/A

122
eNodeB
Parameter
Unit
Value Range
Description
Formula
DRB RLC
Buffer Length
Byte
0 to 10000000
Data stream of
the RLC SDUs
to be sent on the
data radio bearer
(DRB) from the
downlink buffer
area at the RLC
layer when
monitoring
results are
reported.
N/A
DRB RLC First

Packet Delay
ms
0 to 5000
Delay in
sending the first
data packet on
the DRB from
the downlink
buffer area at the
RLC layer.
N/A
5.9 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.
5.9.3 Parameters
Table 5-24 Parameters for throughput monitoring
Parameter
Description
UEID Type

No.
MMEc

STMSI.

123
eNodeB
Parameter
Description
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 Throughput of MAC or Throughput of RLC.

Both items are monitored by default.

l
Throughput of RLC
Table 5-25 Results of RLC throughput 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
Physical cell
identifier of the
serving cell.
N/A
DRB No.
N/A
1to 8
Number of the
DRB.
N/A

124
eNodeB
Parameter
Unit
Value Range
Description
Formula
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 5-26 Results of MAC throughput 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
Physical cell
identifier of the
serving cell.
N/A

125
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)
5.10 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

126
eNodeB
5.10.3 Parameters
Table 5-27 Parameters for AQM monitoring
Parameter
Description
UEID Type

No.
MMEc

STMSI.
mTMSI

STMSI.
Random Value

Random Value.
PLMN

code, respectively.
User Trace ID

Trace Reference No.
Monitor Period (ms)

100, 200, 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 5-28 Results of AQM monitoring
Parameter
Unit
Value Range
Description
Formula
Physical Cell
Identifier
N/A
0 to 503
Physical cell
identifier of the
serving cell.
N/A

127
eNodeB
Parameter
Unit
Value Range
Description
Formula
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
5.11 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.
5.11.3 Parameters
Table 5-29 Parameters for UL power control monitoring
Parameter
Description
UEID Type

No.
MMEc

STMSI.
mTMSI

STMSI.
Random Value

Random Value.

128
eNodeB
Parameter
Description
PLMN

code, respectively.
User Trace ID

Trace Reference No.
Monitor Period (ms)

100, 200, 500, 1000, or 2000.
Test Item
It can be set to PUCCH SINR&RSRP. It is monitored by

default.

PUCCH SINR&RSRP
Table 5-30 Result of PUCCH SINR&RSRP 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
Physical cell
identifier of the
serving cell.
N/A
PUCCH SINR
0.01dB
-1500 to +4000
The SINR value

of the PUCCH.
N/A

129
eNodeB
Parameter
Unit
Value Range
Description
Formula
PUCCH RSRP
dBm
-150 to -40
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
5.12 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.
5.12.3 Parameters
Table 5-31 Parameters for DL power control monitoring
Parameter
Description
UEID Type

No.
MMEc

STMSI.
mTMSI

STMSI.
Random Value

Random Value.

130
eNodeB
Parameter
Description
PLMN

code, respectively.
User Trace ID

Trace Reference No.
Monitor Period (ms)

100, 200, 500, 1000, or 2000.
Test Item
It can be set to PDCCH of UE, PDSCH of UE, or PHICH of

UE. All items are monitored by default.

l
PDSCH UE
Table 5-32 Results of PDSCH UE 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
Physical cell
identifier of the
serving cell.
N/A
PDSCH PA
0.01dB
-600 to +300
Power offset
between each
resource
element (RE) on
the PDSCH and
the pilot when
monitoring
results are
reported.
N/A
PDSCH
Maximum
Number of
Transmissions
Number
0 to 28
Maximum
number of
transmissions
on the PDSCH.
N/A

131
eNodeB
PDSCH IBLER
Target
0 to 1000
Target BLER in
the initial
transmission
during the semistatic PDSCH
power control. It
is set by running
MML
commands.
N/A
PHICH UE
Table 5-33 Results of PHICH UE 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
Physical cell
identifier of 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
results are
reported.
N/A
PDCCH UE

132
eNodeB
Table 5-34 Results of PDCCH UE 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
Physical cell
identifier of the
serving cell.
N/A
Power Offset of
PDCCH
0.01dB
-1500 to +2000
Power offset
between each
RE on the
PDCCH and the
pilot when
monitoring
results are
reported.
N/A
TTI
ms
0to 4294967295
TTI for the

PDCCH power
transmitted at
the MAC layer.
N/A
5.13 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.
5.13.3 Parameters
Table 5-35 Parameters for uplink ICIC monitoring
Parameter
Description

133
eNodeB
UEID Type

No.
MMEc

to STMSI.
mTMSI

to STMSI.
Random Value

to Random Value.
PLMN

User Trace ID

Monitor Period (ms)

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

l
User downlink property
Table 5-36 Results of user downlink property 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
Physical cell
identifier of the
serving cell.
N/A

134
eNodeB
Parameter
Unit
Value Range
Description
Formula
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 5-37 Results of PDSCH RB usage 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
Physical cell
identifier of the
serving cell.
N/A
PDSCH RB
Num
N/A
N/A
Number of RBs
used at the
PDSCH.
N/A
PUSCH RB usage
Table 5-38 Results of PUSCH RB usage 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

135
eNodeB
Parameter
Unit
Value Range
Description
Formula
Physical Cell
Identifier
N/A
0 to 503
Physical cell
identifier of the
serving cell.
N/A
PDSCH RB
Num
N/A
N/A
Number of RBs
used at the
PUSCH.
N/A
User uplink property
Table 5-39 Results of user uplink property 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
Physical cell
identifier of the
serving 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
5.14 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, and the number
of RBs indicates the total number of RBs scheduled using a specific MCS step.

136
eNodeB

None.
5.14.3 Parameters
Table 5-40 Parameters for MCS statistic monitoring
Parameter
Description
UEID Type

No.
MMEc

to STMSI.
mTMSI

to STMSI.
Random Value

to Random Value.
PLMN

User Trace ID

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.

l
DL MCS

137
eNodeB
Table 5-41 Results of DL MCS 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
Physical cell
identifier of the
serving cell.
N/A
DLSCH Code 0
Num[n]
Number
0 to 2000
Total number
(n) of
scheduling on
codeword 0 in
the downlink
scheduling
within a
monitoring
period.
N/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
scheduling
within a
monitoring
period.
N/A
The value n
indicates the
MCS order, and
ranges from 0 to
31.

138
eNodeB
Parameter
Unit
Value Range
Description
Formula
DLSCH Code 1
Num[n]
Number
0 to 2000
Total number
(n) of
scheduling on
codeword 1 in
the downlink
scheduling
within a
monitoring
period.
N/A
The value n
indicates the
MCS order, and
ranges from 0 to
31.
DLSCH Code 1
RBs[n]
Number
0 to 200,000
Total number
(n) of RBs on
codeword 1 in
the downlink
scheduling
within a
monitoring
period.
N/A
The value n
indicates the
MCS order and
ranges from 0 to
31.
UL MCS
Table 5-42 Results of UL MCS 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
Physical cell
identifier of the
serving cell.
N/A

139
eNodeB
Parameter
Unit
Value Range
Description
Formula
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.
ULSCH RBs[n]
Number
0 to 200,000
Total number
(n) of RBs in the
uplink
scheduling
within a
monitoring
period.
N/A
The value n
indicates the
MCS order, and
its value range is
from 0 to 31.
5.15 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.
5.15.3 Parameters
Table 5-43 Parameters for multi-user BF (user) monitoring
Parameter
Description
UEID-MME
MME serving a user.

140
eNodeB
Parameter
Description
UEID-TMSI
TMSI to be monitored.
Trace Reference No.
Trace reference number to be monitored.
Monitor Period (ms)

100, 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. All items are monitored by
default.

Table 5-44 Results of multi-user BF (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
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
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.
N/A

141
eNodeB
Parameter
Unit
Value Range
Description
Formula
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 used by a
UE at each TTI
and calculating
the average
number at the
end of the
monitoring
period.
N/A
5.16 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.
5.16.3 Parameters
Table 5-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.

142
eNodeB
Parameter
Description
Monitor Period (ms)

200, 500, 1000, or 2000.
Test Type Bitmap
Bit 0 and bit 1 respectively represent UL RRU Detect and DL

RRU Detect. Bit 2 represents PDCCH RRU Detect.

Table 5-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
Physical cell
identifier of 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
Number of the
cabinet that
houses the RRU
used for uplink
transmission.
N/A

143
eNodeB
Parameter
Unit
Value Range
Description
Formula
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
N/A
UL RRU Flag
N/A
0, 1, and 2
It indicates that
the RRU used
for uplink
transmission is a
target RRU (the
value is 1), work
RRU (the value
is 0), or other
RRU (the value
is 2).
N/A
Uplink SRS
RSRP
dBm
-151 to -43
Uplink RSRP of
sounding
reference
signals (SRSs)
measured by all
the RRUs on the
SFN.
N/A
Uplink
SRS&DMRS
SINR
dB
-20 to +60
Uplink SINR of
the user.
N/A
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 downlink
transmission.
N/A
DL RRU
Cabinet No.
N/A
0 to 62
Number of the
cabinet that
houses the RRU
used for
downlink
transmission.
N/A
slot that houses

the RRU used
for uplink
transmission.

144
eNodeB
Parameter
Unit
Value Range
Description
Formula
DL RRU
Subrack No.
N/A
4 to 5 and 60 to
254
Number of the
subrack that
houses the RRU
used for
downlink
transmission.
N/A
DL RRU Slot
No.
N/A
0 to 8
Number of the
slot that houses
the RRU used
for downlink
transmission.
N/A
DL RRU Flag
N/A
0 and 1
It indicates that
the RRU used
for downlink
transmission is a
target RRU (the
value is 1) or
working RRU
(the value is 0).
N/A
PDCCH RRU
eNodebId
N/A
0 to 1048575
ID of the
eNodeB where
the RRU is used
for downlink
transmission
N/A
PDCCH RRU
Cabinet No.
N/A
0 to 62
Number of the
cabinet that
houses the RRU
for downlink
transmission
N/A
PDCCH RRU
Subrack No.
N/A
4 to 5, 60 to 254
Number of the
subrack that
houses the RRU
used for
downlink
transmission
N/A
PDCCH RRU
Slot No.
N/A
0 to 8
Number of the
slot that houses
the RRU for
downlink
transmission
N/A

145
eNodeB
Parameter
Unit
Value Range
Description
Formula
RRU Flag
N/A
0 and 1
Specifies
whether an RRU
is a target RRU
(the value is 1)
or working RRU
(the value is 0)
N/A
5.17 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.
5.17.3 Parameters
Table 5-47 Parameters for cell combination monitoring
Parameter
Description
MMEc
MME serving a user.
mTMSI
Monitor Period (ms)
Interval of reporting monitoring results. It can be set to 1000 or

2000.
Test Items
DL Cell Combination RRU Detect, UL Cell Combination

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

146
eNodeB

Table 5-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 downlink
transmission.
N/A
Physical Cell
Identifier
N/A
0 to 503
Physical cell
identifier of 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
Number of the
cabinet that
houses the RRU
used for uplink
transmission.
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 houses
the RRU used
for uplink
transmission.
N/A

147
eNodeB
Parameter
Unit
Value Range
Description
Formula
UL RRU Flag
N/A
0, 1, and 2
It indicates that
the RRU used
for uplink
transmission is a
target RRU (the
value is 1),
working RRU
(the value is 0),
or other RRU
(the value is 2).
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
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
Number of the
cabinet that
houses the RRU
used for
downlink
transmission.
N/A
DL RRU
Subrack No.
N/A
4 to 5 and 60 to
254
Number of the
subrack that
houses the RRU
used for
downlink
transmission.
N/A

148
eNodeB
Parameter
Unit
Value Range
Description
Formula
DL RRU Slot
No.
N/A
0 to 8
Number of the
N/A
DL RRU Flag
N/A
0 and 1
It indicates that
the RRU used
for downlink
transmission is a
target RRU or a
working RRU.
N/A
PDCCH RRU
eNodebId
N/A
0 to 1048575
ID of the
eNodeB where
the RRU is used
for downlink
transmission
N/A
PDCCH RRU
Cabinet No.
N/A
0 to 62
Number of the
cabinet that
houses the RRU
used for
downlink
transmission
N/A
PDCCH RRU
Subrack No.
N/A
4 to 5, 60 to 254
Number of the
subrack that
houses the RRU
used for
downlink
transmission
N/A
PDCCH RRU
Slot No.
N/A
0 to 8
Number of the
slot that houses
the RRU used
for downlink
transmission
N/A
RRU Flag
N/A
0 and 1
Specifies
whether an RRU
is a target RRU
(the value is 1)
or working RRU
(the value is 0)
N/A
slot that houses

the RRU used
for downlink
transmission.
5.18 eICIC (User) Monitoring


149
eNodeB

This task is used to monitor UE-level eICIC statistics, including the number of PRBs scheduled
in ABS subframes and that scheduled in non-ABS subframes, and the times of reporting the CQI
that indicates the channel quality of ABS or non-ABS subframes.
5.18.2 Impact on Services

None.
5.18.3 Parameters
Table 5-49 Parameters for UE-level eICIC statistics for CRE area
Parameter
Description
UEIDType
MMEc

STMSI.
mTMSI

STMSI.
Random Value

Random Value.
PLMN

respectively.
User Trace ID

Reference No.
Monitor Period (ms)

2000.
Test Items
It can be set to Number of Schedule ABS Subframe, Number of

Schedule Non-ABS Subframe, Average Used PRBs In ABS
Subframe, Average Used PRBs In Non-ABS Subframe, Number
of ABS Subframe CQI of 0~15, Number of Non-ABS Subframe
CQI of 0~15, or a combination of some items.

150
eNodeB

Table 5-50 Results of UE-level eICIC statistics for CRE area monitoring
Parameter
Unit
Value
Range
Description
Formula
Number of Schedule
ABS Subframe
Number
0 to 65535
Number of scheduled ABS

subframes. The same ABS
subframe scheduled for
the same UE will not be
counted repeatedly.
N/A
Number of Schedule
NonABS Subframe
Number
0 to 65535
Number of scheduled nonABS subframes. The same

non-ABS subframe
scheduled for the same UE
will not be counted
repeatedly.
N/A
Average Used PRB In

ABS Subframe
Number
0 to 100
Average number of PRBs

used in ABS subframes for
a UE
N/A
Average Used PRB In

NoneABS Subframe
Number
0 to 100
Average number of PRBs

used in non-ABS
subframes for a UE
N/A
Number Of ABS CQI

0
Number
0 to 400
Number of times when an

eICIC-enabled UE reports
CQIs of 0 in ABS
subframes
N/A
Number Of ABS CQI

1
Number
0 to 400

CQIs of 1 in ABS
subframes
N/A
Number Of ABS CQI

2
Number
0 to 400

CQIs of 2 in ABS
subframes
N/A
Number Of ABS CQI

3
Number
0 to 400

CQIs of 3 in ABS
subframes
N/A
Number Of ABS CQI

4
Number
0 to 400

CQIs of 4 in ABS
subframes
N/A

151
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Number Of ABS CQI

5
Number
0 to 400

CQIs of 5 in ABS
subframes
N/A
Number Of ABS CQI

6
Number
0 to 400

CQIs of 6 in ABS
subframes
N/A
Number Of ABS CQI

7
Number
0 to 400

CQIs of 7 in ABS
subframes
N/A
Number Of ABS CQI

8
Number
0 to 400

CQIs of 8 in ABS
subframes
N/A
Number Of ABS CQI

9
Number
0 to 400

CQIs of 9 in ABS
subframes
N/A
Number Of ABS CQI

10
Number
0 to 400

CQIs of 10 in ABS
subframes
N/A
Number Of ABS CQI

11
Number
0 to 400

CQIs of 11 in ABS
subframes
N/A
Number Of ABS CQI

12
Number
0 to 400

CQIs of 12 in ABS
subframes
N/A
Number Of ABS CQI

13
Number
0 to 400

CQIs of 13 in ABS
subframes
N/A
Number Of ABS CQI

14
Number
0 to 400

CQIs of 14 in ABS
subframes
N/A

152
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Number Of ABS CQI

15
Number
0 to 400

CQIs of 15 in ABS
subframes
N/A
Number Of NonABS CQI 0
Number
0~400

subframes
N/A
Number
0 to 400

subframes
N/A
Number
0 to 400

subframes
N/A
Number
0 to 400

subframes
N/A
Number
0 to 400

subframes
N/A
Number
0 to 400

subframes
N/A
Number
0 to 400

subframes
N/A
Number
0 to 400

subframes
N/A
Number
0 to 400

subframes
N/A

153
eNodeB
Parameter
Unit
Value
Range
Description
Formula
Number
0 to 400

subframes
N/A
Number
0 to 400

subframes
N/A
Number
0 to 400

subframes
N/A
Number
0 to 400

subframes
N/A
Number
0 to 400

subframes
N/A
Number
0 to 400

subframes
N/A
Number
0 to 400

subframes
N/A
5.19 DL CoMP (User) Monitoring

This task is used to monitor the DL CoMP used by UEs. The task measures DL CoMP User
Indication, DL CoMP Schedule RB Num, CBF Paired RB Num, and CBF Failing Paired
RB Num.
5.19.2 Impact on Services

None

154
eNodeB
5.19.3 Parameters
Table 5-51 Parameters for DL CoMP (user) monitoring
Parameter
Description
UEIDType
MMEc
Set this parameter only when the UEID Type parameter is set to
STMSI.
mTMSI
STMSI.
Random Value
Random Value.
PLMN
Set this parameter only when the UEID Type parameter is set to Trace
respectively.
User Trace ID
Set this parameter only when the UEID Type parameter is set to Trace
Reference No.
Monitor Period (ms)

2000.

Table 5-52 Results of DL CoMP (user) monitoring
Monitoring
Results
Unit
Value Range
Description
Formula
DL CoMP User
Indication
N/A
0, 1, 2, 3
Specifies whether a UE is
a common UE (the value is
0), JT UE (the value is 1),
CBF UE (the value is 2), or
DCS UE (the value is 3)
N/A
DL CoMP Schedule
RB Num
Num
ber
0 to 200000
Number of RBs used for

scheduling of DL CoMP
UEs
N/A
CBF Paired RB Num
Num
ber
0 to 200000
Number of paired RBs

used for scheduling of
CBF UEs
N/A

155
eNodeB
Monitoring
Results
Unit
Value Range
Description
Formula
CBF Failing Paired

RB Num
Num
ber
0 to 200000
Number of RBs that failed

to be paired used for
scheduling of CBF UEs
N/A

156
eNodeB
6 Device Monitoring
Device Monitoring
6.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.
6.1.3 Parameters
Table 6-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

Upper Slot No.
The slot number of the upper-level node at the

other end of the monitored link.

157
eNodeB
6 Device Monitoring
Parameter
Description
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 lowerlevel node at the other end of the monitored
link are RRUs.
Lower Cabinet No.
The cabinet number of the lower-level node

NOTE
The lower-level node mentioned in this table is the
node connected to the link towards the lowestlevel RRU.
Lower Subrack No.
The subrack number of the lower-level node

Lower Slot No.
The slot number of the lower-level node at the

other end of the monitored link.

Table 6-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
158
eNodeB
6 Device Monitoring
Parameter
Unit
Value Range
Description
Formula
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.
6.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.
6.2.3 Parameters
Table 6-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.

159
eNodeB
6 Device Monitoring

Table 6-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:
Cabinet
No.:Subrack
No.:Slot No.
N/A
Type
N/A
N/A
The CPU type is

as follows:
N/A
l CPU.
l DSP.
l Slave CPU.
CPU No.
N/A
N/A
The default
CPU number is
0.
N/A
CPU Usage
0 to 100
CPU usage
when
monitoring
results are
reported.
N/A
6.3 RRU/RFU/BRU Output Power Monitoring

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

None.

160
eNodeB
6 Device Monitoring
6.3.3 Parameters
Table 6-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

Slot No.
Number of the slot where the board for RRU/RFU/BRU

Monitor Period (ms)
Interval of reporting monitoring results.It can be set to 1000,

2000, or 3000.

Table 6-6 Results of RRU/RFU/BRU Output Power monitoring
Parameter
Unit
Value Range
Description
Formula
Index of TX
Branch
N/A
0 to 7
Index of TX
channel.
N/A
Index of Carrier
N/A
l If only 0 is
displayed,
the RRU
supports one
carrier.
N/A
NOTE
0 and 1 for
BTS3202Es,
BTS3203Es,
and
BTS3205Es.
0 to 1
NOTE
0 for
BTS3202Es,
BTS3203Es,
and
BTS3205Es.
l If both 0 and
1 are
displayed,
the RRU/
RFU
supports two
carriers.

161
eNodeB
6 Device Monitoring
Parameter
Unit
Value Range
Description
Formula
TX Freq of
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
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,
BTS3203Es,
and
BTS3205Es.
Mode
N/A
LTE-FDD, and
LTE-TDD
Working mode
of the board to
be monitored.
N/A
Output Power of
TX Branch
0.1 dBm
-200 to -1, and 0

to 1000
Output power of
a TX channel.
N/A
NOTE
0 to 370 for
BTS3202Es,
BTS3203Es,
and
BTS3205Ess.
6.4 Board Temperature Monitoring

This task is used to monitor board or eNodeB temperature.

None.

162
eNodeB
6 Device Monitoring
6.4.3 Parameters
Table 6-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

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

Monitor Period (ms)

2000, 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

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

163
eNodeB
6 Device Monitoring
Monitoring
Results
Unit
Value Range
Description
Formula
PA branch
Temperature
-100 to 200
Temperature of
power amplifier
branches when
multiple power
amplifiers are
available in the
RRU or RFU.
N/A
0x7FFF: Invalid
values are not
displayed.
6.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 IEEE1588 V2 or clock over IP are packet-based.

None.
6.5.3 Parameters
Table 6-9 Parameters for clock quality test monitoring
Parameter
Description
Cabinet No.

eNodeB for clock quality monitoring is
located.
Subrack No.

eNodeB for clock quality monitoring is
located.
Slot No.

for clock quality monitoring is located.
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.

164
eNodeB
6 Device Monitoring

Table 6-10 Results of clock quality monitoring
Parameter
Unit
Value Range
Description
Formul
a
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
located.
N/A
Slot No.
N/A
0 to 7
Number of the slot where the

board whose monitoring
located.
N/A
TestResultType
N/A
Frequency
discrimination
Test result types.
N/A
Frequency discrimination
value or phase discrimination
value.
N/A
Phase
discrimination
Count Value
Frequency
discriminati
on: ppb
Frequency
discrimination:
-5000 to 5000
Phase
discriminati
on: ns
Phase
discrimination:
-200000 to
200000
6.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 clock-related alarms include jitter,
excessive frequency deviation, and excessive phase offset.

None.

165
eNodeB
6 Device Monitoring
6.6.3 Parameters
Table 6-11 Parameters for IP clock data collection monitoring
Parameter
Description
Cabinet No.

eNodeB for IP clock data collection
monitoring is located.
Subrack No.

eNodeB for IP clock data collection
Slot No.

for IP clock data collection monitoring is
located.
Report Period(Seconds)
Interval of reporting monitoring results. This

parameter must be set to 1.

Table 6-12 Results of IP clock data collection monitoring
Parameter
Unit
Value Range
Description
Formula
Tp1 Max QoS

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

Value
ns
-263 to 263-1
Minimum delay
per second for
transmitting
packets from the
clock server to
the eNodeB
N/A
Tp2 Max QoS

Value
ns
-263 to 263-1
Maximum delay
per second for
transmitting
packets from the
eNodeB to the
clock server
N/A

166
eNodeB
6 Device Monitoring
Parameter
Unit
Value Range
Description
Formula
Tp2 Min QoS

Value
ns
-263 to 263-1
Minimum delay
per second for
transmitting
packets from the
eNodeB to the
clock server
N/A
6.7 RRU/RFU Output Power Monitoring

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

None.
6.7.3 Parameters
Table 6-13 Parameters for RRU/RFU output power monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the board for output power

Subrack No.
Number of the subrack where the board for output power

Slot No.
Number of the slot where the board for output power

Monitor Period (ms)

1000, 2000, 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.

167
eNodeB
6 Device Monitoring

Table 6-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
monitoring
results are
reported is
located.
N/A
Subrack No.
N/A
4 to 5, 60 to 254
Number of the
subrack where
the board whose
monitoring
results are
reported is
located.
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
Monitor Period
(ms)
ms
1000, 2000,
3000
Interval of
reporting
monitoring
results.
N/A
Output power of
Tx Freq[n]
(0.1dBm)
Mode:LTEFDD
0.1 dBm
0 to 1000, and
-200 to -1
Output power of
a TX[n]
channel, in
which n can be
set to 0 or 1.
N/A
TX branch
Output power of
TX[n]
0.1 dBm
Output power of
a TX[n]
channel, in
which n can be
set to 0 or 1.
N/A
NOTE
In BTS3202E,
BTS3203E,
BTS3205E, the
value range is 0
to 370.
0 to 1000, and
-200 to -1
NOTE
In BTS3202E,
BTS3203E,
BTS3205E, the
value range is 0
to 370.

168
eNodeB
6 Device Monitoring
6.8 Rx Frequency Scanning

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.
6.8.3 Parameters
Table 6-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 frequency scanning is
located.
Slot No.
Number of the slot where the RRU, RFU, or

BRU for uplink frequency scanning is
located.
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

set.

169
eNodeB
6 Device Monitoring

Table 6-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 reported is
located.
N/A
Subrack No.
N/A
4 to 5, 60 to 254
Number of the
subrack where the
board whose
monitoring results
are reported is
located.
N/A
Slot No.
N/A
0 to 8
Number of the slot

where the board
whose monitoring
located.
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

170
eNodeB
6 Device Monitoring
Monitoring
Results
Unit
Value Range
Description
Formula
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,
BTS3203Es, and
BTS3205Es.
N/A
Data Type
N/A
N/A
Data type of uplink

frequency scanning
result.
N/A
6.9 DTF Test

This task is used to detect the distance to fault (DTF).

Services in cells served by the RRU or RFU are interrupted during the test.
6.9.3 Parameters
Table 6-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.

171
eNodeB
6 Device Monitoring
Parameter
Description
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

set.

Table 6-18 Results of DTF test
Parameter
Unit
Value Range
Description
Formula
Cabinet No.
N/A
0 to 62
Number of the
cabinet where the
board whose
monitoring results
are reported is
located.
N/A
Subrack No.
N/A
4 to 5, 60 to 254
Number of the
subrack where the
board whose
monitoring results
are reported is
located.
N/A
Slot No.
N/A
0 to 8
Number of the slot

where the board
whose monitoring
located.
N/A

172
eNodeB
6 Device Monitoring
Parameter
Unit
Value Range
Description
Formula
TX Channel No.
N/A
0 to 7
Number of the branch

on which monitoring
results are reported.
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
6.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.
6.10.3 Parameters
Table 6-19 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 or BTS3205Es for
FFT frequency scan. The value of n is 1 or 2.
Mode
Mode for FFT frequency scan.

173
eNodeB
6 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.
NOTE
TX channel is provided by the RF port of the RRU/RFU/
BRU. A carrier is similar to a cell.
RBW(KHZ)
Time frequency of FFT frequency detection, in units

of kHz.
l 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.
l 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.
Save File

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

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

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

174
eNodeB
6 Device Monitoring
Parameter
Unit
Value Range
Description
Formula
Slot No.
N/A
0 to 8
Number of the slot

where the board
whose monitoring
located.
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 and
BTS3205Es.
N/A
Spectrum
Process Type
N/A
Spectrum process
types are as follows:
N/A
NOTE
0 and 1 in
BTS3202Es and
BTS3205Es
0 to 2
0: High-Resolution
Online Frequency
1: Broadband Online
Frequency
2: Broadband Offline
Frequency
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
6.11 AAS
This task is used to maintain an eNodeB.

None.

175
eNodeB
6 Device Monitoring
6.11.3 Parameters
Table 6-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

set.

Table 6-22 Results for AAS
Parameter
Unit
Value Range
Description
Formula
AARU Cabinet
No.
N/A
0 to 62
Number of the
cabinet where
the AARU is
located.
N/A
AARU Subrack
No.
N/A
60 to 254
Number of the
subrack where
the AARU is
located.
N/A
AARU Slot No.
N/A
0 to 3
Number of the
slot where the
AARU is
located.
N/A

176
eNodeB
6 Device Monitoring
Parameter
Unit
Value Range
Description
Formula
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
6.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.
6.12.3 Parameters
Table 6-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.

177
eNodeB
6 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 detection. The value ranges from 0 to
65535.
Freq Step(0.1MHz)
Frequency step in frequency scanning intermodulation

interference detection. The value ranges from 1 to 100.
Save File

path. The file name, file format, and save path can be
set.

Table 6-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 where the
board whose
monitoring results
are reported is
located.
N/A
Subrack No.
N/A
4 to 5,60 to 254
Number of the
subrack where the
board whose
monitoring results
are reported is
located.
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

178
eNodeB
6 Device Monitoring
Parameter
Unit
Value Range
Description
Formula
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.

179
eNodeB
7 Transport Performance Monitoring
Transport Performance Monitoring
7.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.
7.1.3 Parameters
Table 7-1 Parameters for local and forwarded traffic monitoring
Parameter
Description

set to 1 by default.

180
eNodeB

Table 7-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
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
Bypass Traffic
Byte/s
0 to 100000000
Number of bytes
N/A
forwarded by the
eNodeB per
second within a
monitoring period.
7.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.

181
eNodeB
7.2.3 Parameters
Table 7-3 Parameters for IP performance monitoring
Parameter
Description
Cabinet No.

eNodeB for IP performance monitoring is
located.
Subrack No.

located.
Slot No.
Number of the logical slot where the board/

located.
VRF
Number of the virtual routing and forwarding

instance for IP performance monitoring.


Table 7-4 Results of IP Performance monitoring
Parameter
Unit
Value Range
Description
Formula
Receive Packets
Packets
0 to 2000000
Total number of
packets at the IP
layer received by
the board/eNodeB
within a
monitoring
period.
N/A
Send Packets
Packets
0 to 2000000
Total number of
packets at the IP
layer transmitted
by the board/
eNodeB within a
monitoring
period.
N/A

182
eNodeB
Parameter
Unit
Value Range
Description
Formula
Receive Drop
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
7.3 Transport Port Flux Stat Monitoring

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.
7.3.3 Parameters
Table 7-5 Parameters for transport port flux stat monitoring
Parameter
Description
Cabinet No.

eNodeB for transport port flux stat
Subrack No.

Slot No.


183
eNodeB
Parameter
Description
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:
l BASE_BOARD
l BACK_BOARD
l ETH_COVERBOARD
l E1_COVERBOARD
l UNCHANNELLED_COVERBOARD
NOTE
The LTE supports BASE_BOARD,
BACK_BOARD or ETH_COVERBOARD.
It can be set only to BASE_BOARD in BTS3202E
and BTS3203E.
Protocol Type
Type of the protocol for transport port flux

stat monitoring. It can be set to IP.
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 EthPortor EthTrunkin 3900Series
Base Station.
Port No.
Number of the physical port of a board or an

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.

184
eNodeB
Parameter
Description
Include Packet Discard Information of IP

Layer
Specifies whether monitoring results contain

the lost packets in the IP layer.
Include Packet Discard Information of LINK

Layer

the lost packets in the data link layer.
Extend Option

Exclude Packet Loss Info., Include IP
Layer Packet Loss Info, Include Link
Layer Packet Loss Info and Include All
Packet Loss Info.
This monitoring item is valid when Protocol
Type and Port Type are set to IP and
PHYSICAL_PORT, respectively.

Table 7-6 Results of transport port flux stat monitoring
Parameter
Unit
Value Range
Description
Formula
Rx Traffic
bps
0 to 100000000
Number of bytes received

by the eNodeB within the
monitoring period.
N/A
Tx Traffic
bps
0 to 100000000
Number of bytes
transmitted by the
eNodeB within the
monitoring period.
N/A
Rx Packets
packet
0 to 2000000
Number of packets
received by the eNodeB
within the monitoring
period.
N/A
Tx Packets
packet
0 to 2000000
Number of packets
transmitted by the
eNodeB within the
monitoring period.
N/A
Rx Loss Packets
packet
0 to 4294967295
Number of loss packets

during reception within
the monitoring period.
N/A
Tx Loss Packets
packet
0 to 4294967295
Number of loss packets

during transmission
within the monitoring
period.
N/A

185
eNodeB
Parameter
Unit
Value Range
Description
Formula
RX CRC Error
Packet number
of Link Level
packet
0 to 4294967295
Number of packets that

fail the CRC during
reception in the data link
layer within a monitoring
period.
N/A
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 physical
port within a monitoring
period.
N/A
RX Rate of IP
Port(bps)
bps
0 to 4294967295
Receive rate on a
physical port within 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 a
monitoring period.
N/A
Rx Logic Port
Admitted
Bandwidth of
SingleRate
Kbps
0 to 1000000000
Admission bandwidth for

data reception on the
mode within a
monitoring period.
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
single-rate mode within a
monitoring period.
N/A

186
eNodeB
Parameter
Unit
Value Range
Description
Formula
Rx Logic Port
GBR Load of
SingleRate
Kbps
0 to 1000000000
Receive load for GBR

service data reception on
the logical port in singlerate mode within a
monitoring period.
N/A
Tx Logic Port
GBR Load
Ratio of
SingleRate
0 to 100
Transmit load rate of

GBR service data
transmission on the
mode within a
monitoring period.
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

the logical port in singlerate mode within a
monitoring period.
Receive load for

GBR service
data reception
on the logical
port in singlerate 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
mode within a
monitoring period.
N/A
Rx Logic Port
Load of
SingleRate
Kbps
0 to 1000000000
Receive load for data

reception on the logical
port in single-rate mode
within a monitoring
period.
N/A

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

transmission on the
mode within a
monitoring period.
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
Receive load rate of data

port in single-rate mode
within a monitoring
period.
Receive load for

data reception
on the logical
port in singlerate mode x 100/
Admission
bandwidth for
data reception
on the logical
port in singlerate mode
Tx Logic Port
Flow of
SingleRate
Kbps
0 to 1000000000
Transmit traffic for data

transmission on the
mode within a
monitoring period.
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 doublerate 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

188
eNodeB
Parameter
Unit
Value Range
Description
Formula
Tx Logic Port
PIR Admitted
Bandwidth of
DualRate
Kbps
0 to 1000000000
PIR admission
bandwidth for data
transmission on the
monitoring period.
N/A
Rx Logic Port
PIR Admitted
Bandwidth of
DualRate
Kbps
0 to 1000000000
PIR admission
bandwidth for data
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
N/A
Rx Logic Port
GBR Load of
DualRate
Kbps
0 to 1000000000
Receive load for GBR

the logical port in doublerate mode within a
monitoring period.
N/A
Tx Logic Port
Non-FlowControl Service
Load of
DualRate
Kbps
0 to 1000000000
Transmit load for nonflow-controllable service

data transmission on the
monitoring period.
N/A
Rx Logic Port
Non-FlowControl Service
Load of
DualRate
Kbps
0 to 1000000000
Receive load for nonflow-controllable service

data reception on the
monitoring period.
N/A

189
eNodeB
Parameter
Unit
Value Range
Description
Formula
Tx Logic Port
GBR Load Rate
of DualRate
0 to 100
Transmit load rate of

GBR service data
transmission on the
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
Receive load rate of GBR

monitoring period.
Receive load for

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

of GBR service data
transmission on the
monitoring period.
Transmit load
for non-flowcontrollable
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

190
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
within a monitoring
period.
Receive load for

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

transmission on the
monitoring period.
N/A
Rx Logic Port
Load of
DualRate
Kbps
0 to 1000000000
Receive load for data

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

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

of data reception on the
monitoring period.
Receive load for

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

transmission on the
monitoring period.
N/A
7.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.
7.4.3 Parameters
Table 7-7 Parameters for transport link flux stat monitoring
Parameter
Description
Cabinet No.

transport link flux stat monitoring is located.
Subrack No.

transport link flux stat monitoring is located.
Slot No.
Number of the logical slot where the board/eNodeB

for transport link flux stat monitoring is located.
Protocol Type
It can be set to ATM or IP in 3900 series base

stations. It can be set only to IP in BTS3202Es,
BTS3203Es, and BTS3205Es.

192
eNodeB
Parameter
Description
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.
It can be set only to BASE_BOARD in BTS3202E
and BTS3203E.
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.
Unit
It can be set to cps or bps.

Port No.
Port number of the board for transport port flux stat

monitoring.
PVCx
The value range for x is from 1 to 6.

VPI

VCI

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.

set to IP.
SCTP No.
Number of the SCTP link.

set to IP.

193
eNodeB
Parameter
Description
IPPATH
Specifies whether to monitor the quality of links on

the user plane.
set to IP.
PATH ID
Number of the IP path.

set to IP.
OMCH
Specifies whether to detect the OM channel.

set to IP.
DSCP
Differentiated services code point (DSCP) value of

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

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

OMCH parameter is specified.
set to IP.
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 U2000.
set to IP.
Save File

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

l
OMCH

194
eNodeB
Table 7-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
NOTE
BTS3202Es,
BTS3203Es,
and BTS3205Es
do not support
PVC.
RX Rate
pps, bps
0 to
4294967295
Receive rate of
the OM channel
within a
monitoring
period.
N/A
TX Rate
pps, bps
0 to
4294967295
Transmit rate of
the OM channel
within a
monitoring
period.
N/A
IP Path
Table 7-9 Results of IP Path 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
NOTE
BTS3202Es,
BTS3203Es,
and BTS3205Es
do not support
PVC.
Index
N/A
1 to 3
Index of an IP
path.

N/A
195
eNodeB
Parameter
Unit
Value Range
Description
Formula
Flag
N/A
0 to 65535
Number of an IP
path.
N/A
RX Rate
pps, bps
0 to
4294967295
Receive rate of
an IP path
within a
monitoring
period.
N/A
TX Rate
pps, bps
0 to
4294967295
Transmit rate of
an IP path
within a
monitoring
period.
N/A
SCTP
Table 7-10 Results of SCTP 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
NOTE
BTS3202Es,
BTS3203Es,
and BTS3205Es
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

196
eNodeB
Parameter
Unit
Value Range
Description
Formula
RX Rate
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
pps, bps
0 to
4294967295
Transmit rate of
the SCTP link
within a
monitoring
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
RX Error
Packets
pps
0 to
4294967295
Number of error
packets received
over the SCTP
link within a
monitoring
period.
N/A
Resend Trunk
Rate
0 to 1000
Retransmission
rate of SCTP
association data
within a
monitoring
period.
N/A

197
eNodeB
Parameter
Unit
Value Range
Description
Formula
RX Packet
Discard Rate
pps
0 to
4294967295
Number of
discarded
incoming
packets in the
SCTP link
within a
monitoring
period.
N/A
IPPM
Table 7-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
NOTE
BTS3202Es,
BTS3203Es,
and BTS3205Es
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

198
eNodeB
Parameter
Unit
Value Range
Description
Formula
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
7.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.

199
eNodeB
7.5.3 Parameters
Table 7-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 UDP test is
located.
Slot No.
Number of the logical slot where the main

control board/eNodeB for the UDP test is
located.

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

200
eNodeB

Table 7-13 Result of UDP test monitoring
Parameter
Unit
Value Range
Description
Formula
Drop Packets
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 *
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
*100000/Total
number of
packets
Delay
Microsecond
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

201
eNodeB
Parameter
Unit
Value Range
Description
Formula
Jitter
N/A
N/A
Jitter on the
transmission
link within a
monitoring
period.
|Delay Average Delay|/

Average Delay
NOTE
The displayed
value is equal to
the monitored
value multiplied
by 1000.
Average Delay
Microsecond
0 to 4000000
Average delay
on the
transmission
link within a
monitoring
period.
N/A
7.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.
7.6.3 Parameters
Table 7-14 Parameters for PPPoE monitoring
Parameter
Description
Cabinet No.

eNodeB for the PPPoE performance tests is
located.

202
eNodeB
Parameter
Description
Subrack No.

located.
Slot No.

located.
PPPoELink No.
Number of the PPPoE link to be tested.


Table 7-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
Receive Bytes
bps
0 to 300000000
Number of bits
received per second
by the receiving
end of a PPPoE link
within a monitoring
period.
N/A
Send Bytes
bps
0 to 300000000
Number of bits
transmitted per
second by the
transmitting end of
a PPPoE link
within a monitoring
period.
N/A

203
eNodeB
Parameter
Unit
Value Range
Description
Formula
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
transmitting end of
a 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 transmitting
end of a PPPoE link
within a monitoring
period.
Send Drop
Packets
x100/(Send
Packets +
Send Drop
Packets)
7.7 IPSec Performance Monitoring

This task is used to monitor packets transmitted and received over the IP security (IPsec) tunnel.

None.

204
eNodeB
7.7.3 Parameters
Table 7-16 Parameters for IPSec performance monitoring
Parameter
Description
Cabinet No.
Number of the cabinet where the board/eNodeB for IPSec

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

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

IPSec performance monitoring is located.
Interval of reporting monitoring results. It is set to 1 by

default.
Save File

NOTE

Table 7-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.0000001
0 to 1000000
Packet loss rate

for data
reception on the
IPSec tunnel
within a
monitoring
period.
N/A

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

None.
7.8.3 Parameters
Table 7-18 Parameters for transport OAM monitoring
Parameter
Description
Test Type
It can be set to:

l Y1731-LM
l Y1731-DM
Session ID
Number of the session for transport OAM

monitoring.
Save File

set.

Table 7-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
within a
monitoring
period.
N/A

206
eNodeB
Parameter
Unit
Value Range
Description
Formula
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.
Total Frames
Transmitted in
Downlink
Number
0 to
4294967295
Total number of
N/A
frames
transmitted in the
downlink within a
monitoring
period.

207
eNodeB
Parameter
Unit
Value Range
Description
Formula
Total Frames
Lost in
Downlink
Number
0 to
4294967295
Absolute value of N/A

the total number
of frames
discarded in the
downlink within a
monitoring
period.
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

208
eNodeB
7.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.
7.9.3 Parameters
Table 7-20 Parameters for transport auto setup user plane monitoring
Parameter
Description
Cabinet No.

transport auto setup user plane monitoring is located.
Subrack No.

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

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 in U2000. And

it can be set to User Plane Link or User Plane Link +
IPPM.in LMT.
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.
DSCP
It is valid only when Port Type is set to RSCGRP and

can be set to Flow Stat or Load Stat.
Save File

NOTE

209
eNodeB

Table 7-21 Results of transport auto setup user plane monitoring
Parameter
Unit
Value Range
Description
Formula
Test Type
N/A
Include,
Exclude
Type of the link

for transport
auto setup user
plane
monitoring.
Specifies the
monitoring task
including or
excluding
IPPM.
N/A
Index
N/A
0 to 2
Index of the link

for transport
auto setup user
plane
monitoring.
N/A
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,
BTS3203Es,
and BTS3205Es
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

210
eNodeB
Parameter
Unit
Value Range
Description
Formula
Transmit Rate
(pps)
pps
0 to
4294967295
Transmit rate of
a user plane link
in the IP layer
within a
monitoring
period.
N/A
Receive Rate
(bps)
bps
0 to
4294967295
Receive rate of a
user plane link
in the IP layer
within a
monitoring
period.
N/A
Transmit Rate
(bps)
bps
0 to
4294967295
Transmit rate of
a user plane link
in the IP layer
within a
monitoring
period.
N/A
Average RTT
Delay(ms)
ms
0 to
4294967295
Average delay
of a user plane
link in the IP
layer within a
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
within a
monitoring
period.
N/A
Transmit Time
Jitter(ms)
ms
-65536 to 65535
Average jitter
for data
transmission of
a user plane link
in the IP layer
within a
monitoring
period.
N/A

211
eNodeB
Parameter
Unit
Value Range
Description
Formula
Receive Packet
Discard Rate
0.01
0 to 1000
Average packet
loss rate for data
reception of a
user plane link
in the IP layer
within a
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
Transmit lost
packet
packet
0 to
4294967295
Number of
discarded
packets for data
transmission of
a user plane link
in the IP layer
within a
monitoring
period.
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

212
eNodeB
8 RRU/RFU Performance Monitoring
RRU/RFU Performance Monitoring
8.1 Sector Performance Monitoring

The RRU or RFU scans frequencies continuously, calculates the received signal strength, and
reports the strength to the LMT. The received signal strength is used as reference for interference
location and analysis.

None.
8.1.3 Parameters
Table 8-1 Parameters for sector performance monitoring
Parameter
Description
Test Items
It can be set only to UL Widefreq Scan.
Monitor Period (ms)

50, 100, 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 64.
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, BTS3203Es, and BTS3205Esdo not
support the cell bandwidth of 1.4 MHz or 3 MHz.

213
eNodeB
8 RRU/RFU Performance Monitoring
Parameter
Description
Save File

path. The file name, file format, and save path can be
set.
NOTE

Table 8-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 results
are reported.
N/A

214

ENodeB Performance Monitoring Reference (Draft D) (PDF) - en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ENodeB Performance Monitoring Reference (Draft D) (PDF) - en

Uploaded by

Copyright:

Available Formats

eNodeB

Performance Monitoring Reference

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Issue Draft D (2014-03-26)

Huawei Proprietary and Confidential

4 Cell Performance Monitoring...................................................................................................15

Huawei Proprietary and Confidential

4.5 User Statistics Monitoring............................................................................................................................................26

Huawei Proprietary and Confidential

4.13.1 Usage Scenario........................................................................................................................................................50

Huawei Proprietary and Confidential

4.21.2 Service Impact.......................................................................................................................................................100

5 User Performance Monitoring................................................................................................103

Huawei Proprietary and Confidential

5.7.2 Service Impact.........................................................................................................................................................118

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

6.12.4 Monitoring Results................................................................................................................................................178

7 Transport Performance Monitoring.......................................................................................180

Huawei Proprietary and Confidential

7.8.4 Monitoring Results..................................................................................................................................................206

8 RRU/RFU Performance Monitoring.......................................................................................213

Issue Draft D (2014-03-26)

Huawei Proprietary and Confidential

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

Issue Draft D (2014-03-26)

Huawei Proprietary and Confidential

1 About This Document

Site maintenance engineers

Issue Draft D (2014-03-26)

Huawei Proprietary and Confidential

The following describes the changes in eNodeB Performance Monitoring Reference.

4.10.4 Monitoring Results

Changed Max RB Number of PUCCH in

No information in Draft C (2014-02-28) is deleted from this issue.

Issue Draft D (2014-03-26)

Huawei Proprietary and Confidential

4.5.4 Monitoring Results

Modified the description of the parameters CN

4.6.4 Monitoring Results

Modified the value range of the parameters

4.8.4 Monitoring Results

Modified the value range of the parameter MIMO

4.18.4 Monitoring Results

Deleted the parameter DlEarfcnNum.

No informations in Draft B (2014-02-10) is deleted from this issue.

4.21 DL CoMP (Cell) Monitoring

4.22 Cell-Level Interference Randomization

5.19 DL CoMP (User) Monitoring

5.16 SFN Detection Monitoring

Modified 5.16.3 Parameters and 5.16.4