eNodeB Performance Monitoring Reference (08) (PDF) - EN PDF

eNodeB
Performance Monitoring
Reference
Issue 08
Date 2014-02-28
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 08 (2014-02-28) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eNodeB
Performance Monitoring Reference About This Document
About This Document
Purpose
This document describes the information about eNodeB-related performance monitoring tasks,
including:
The descriptions of parameters for performance monitoring
The descriptions of monitor items
The value range of each monitor item
The formula used to calculate the value of each monitor item
Product Versions
The following table lists the product version related to this document.
Product Name Product Version

DBS3900 V100R008C00
DBS3900 TDD The mapping single-mode base station version is:
eNodeB: V100R006C00
BTS3900
BTS3900A
BTS3900L
BTS3900AL
BTS3202E
BTS3203E LTE V100R006C00
NOTE
In this document, BTS3203E refers to the BTS3203E LTE.
Intended Audience
This document is intended for:
System engineers
Issue 08 (2014-02-28) Huawei Proprietary and Confidential ii

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

4.3.4 Monitoring Results Modified the name of the parameters.
No information in Issue 07 (2014-01-27) is deleted from this issue.
07 (2014-01-27)
This is the seventh official release.
Issue 08 (2014-02-28) Huawei Proprietary and Confidential iii

eNodeB

2.6.4 Monitoring Results Updatad the descriptions of "Value Range"
and "Description" in Table 2-16 Results of
usage of RB monitoring.
2.17.3 Parameters Updated the condition inTable 2-45
Parameters for neighboring cells.
2.17.4 Monitoring Results Added the parameter "Local Cell ID" in
Table 2-46 Results of MLB monitoring.
3.1.4 Monitoring Results Added the descriptions of " UL CoMP User
Indication."
3.3.4 Monitoring Results Added note of the Description in parameters
of "NeighborCell RSRP[n]" and
"NeighborCell RSRQ[n]."
and "Description" in CA Property.
3.6.4 Monitoring Results
3.7.4 Monitoring Results  Updatad the descriptions of "Value

Range" and "Description" in CA
Property.
 Modified the Value Range of RLC
Buffer Length.
 Updated the descrptioon of Table 3-17.
3.11.3 Parameters Added the parameter of Test Item.

3.14.3 Parameters
3.16.3 Parameters Updated the description of Test Items.
5.3.3 Parameters Updatad the Table 5-5Parameters for

transport port flux stat monitoring.
5.9.3 Parameters Updatad the descriptions of IPPM Flag.
Added the parameter of Destination IP
address.
Issue 08 (2014-02-28) Huawei Proprietary and Confidential iv

eNodeB

5.9.4 Monitoring Results Updatad the Value Range of Test Type.
Compared with Issue 06 (2013-10-30), this issue deleted the following new information:
Deleted the Results of PVC monitoring in 5.4.4 Monitoring Results.
06 (2013-10-30)
This is the sixth official release.

1.3.3 General Parameter Input Description Add the descriptions of General Parameter.
1.3 Precautions Add the descriptions of the Note.
3.7.4 Monitoring Results Updated the "Result of RLC data stream

monitoring."
3.8.4 Monitoring Results Updated the "Results of RLC throughput
monitoring."
3.12.4 Monitoring Results Updated the "Results of user downlink
property monitoring."
Compared with Issue 05 (2013-08-01), this issue does not include any changes.
05 (2013-08-01)
This is the fifth official release.
Compared with Issue 04 (2013-07-22), this issue includes the following changes.

5.3 Transport Port Flux Stat Monitoring Modified descriptions of Usage Scenario.
Issue 08 (2014-02-28) Huawei Proprietary and Confidential v

eNodeB
04 (2013-07-22)
This is the fourth official release.

Whole document Added descriptions of BTS3203Es.
3 User Performance Monitoring Modified the value range of Physical Cell

Identifier.
2.14 HARQ Statistic Monitoring Modified the description of the Code[m]
DTX Num.
3.7.4 Monitoring Results Modified the description of the Byte Length
of LCG BS[n].
03 (2013-06-27)
This is the third official release.

3.11.4 Monitoring Results Modified the description in section "PDSCH
Maximum Number of Transmissions".
5.6.3 Parameters Modified the name of "PPPoELink No".
02 (2013-05-30)
This is the second official release.
Issue 08 (2014-02-28) Huawei Proprietary and Confidential vi

eNodeB

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

4.3 RRU/RFU/BRU Output Power Modified monitoring results.
Monitoring
4.8 Rx Frequency Scanning
4.9 DTF Test
5.5 UDP Test Monitoring
6.1 Sector Performance Monitoring
The following information in draft C (2013-04-10) is deleted from this issue:

LTE IP Link Monitoring
LTE IP Path Performance Monitoring
LTE SCTP Performance Monitoring
LTE Resource Group Monitoring
Draft C (2013-04-10)
This is the release of Draft C.
Compared with draft B (2013-02-25), this issue does not include any new information.
Compared with draft B (2013-02-25), this issue includes the following changes.
Issue 08 (2014-02-28) Huawei Proprietary and Confidential vii

eNodeB

2.5 User Statistics Monitoring Modified the monitoring results of the
2.16 DRB Statistics Monitoring monitoring tasks in these sections.
3.3 DL RSRP/RSRQ Monitoring
4.3 RRU/RFU/BRU Output Power Monitoring
4.4 Board Temperature Monitoring
4.7 RRU/RFU Output Power Monitoring
No information in draft B (2013-02-25) is deleted from this issue.
Draft B (2013-02-25)
This is the release of Draft B.
Compared with draft A (2013-02-08), this issue does not include any new information.
Compared with draft A (2013-02-08), this issue includes the following changes.

3.2 VQI Monitoring Modified the description of VQI Monitoring.
3.6 Quality of Channel Monitoring Modified the description of
Quality of Channel Monitoring.
No information in issue draft A (2013-02-08) is deleted from this issue.
Draft A (2013-02-08)
This is the release of Draft A.
Compared with issue 02 (2012-11-30) of V100R005C01, this issue includes the following
new information.

2.1 UL CoMP (Cell) Monitoring Added the descriptions on UL CoMP (Cell)
Monitoring.
3.1 UL CoMP (User) Monitoring Added the descriptions on UL CoMP (User)
Monitoring.
2.17 MLB Monitoring Added new monitoring items.
3.2 VQI Monitoring Added new monitoring items.
3.16 Cell Combination Monitoring Added new monitoring items.
4.4 Board Temperature Monitoring Added new monitoring items.
4.7 RRU/RFU Output Power Monitoring Added new monitoring items.
Issue 08 (2014-02-28) Huawei Proprietary and Confidential viii

eNodeB

4.8 Rx Frequency Scanning Added new monitoring items.
4.9 DTF Test Added new monitoring items.
4.10 FFT Frequency Scan Added new monitoring items.
4.11 AAS Added new monitoring items.
4.12 Frequency Scanning Intermodulation Added new monitoring items.
Interference Detection Monitoring
5.3 Transport Port Flux Stat Monitoring Added new monitoring items.
5.4 Transport Link Flux Stat Monitoring Added new monitoring items.
5.7 IPSec Performance Monitoring Added new monitoring items.
5.8 Transport OAM Monitoring Added new monitoring items.
5.9 Transport Auto Setup User Plane Added new monitoring items.
Monitoring
Compared with issue 02 (2012-11-30) of V100R005C01, this issue includes the following
changes:

2.9 RSSI Statistic Monitoring Modified the descriptions on the results of
2.10 Interference Detection Monitoring parameters and monitoring results.
2.11 TDD Interference Detection
Monitoring
6.1 Sector Performance Monitoring Modified the Local Sector ID parameter to the
Sector Device ID parameter.
Added the value range for the Sector Device ID
parameter.
The following information in issue 02 (2012-11-30) of V100R005C01 is deleted from this

issue:
Board Temperature Monitoring
Transport Performance Monitoring
Spectrum Detection
Issue 08 (2014-02-28) Huawei Proprietary and Confidential ix

eNodeB
Performance Monitoring Reference Contents
Contents
About This Document .................................................................................................................... ii

1 Introduction.................................................................................................................................... 1
1.1 Overview .......................................................................................................................................................... 1
1.2 Performance Monitoring Types ........................................................................................................................ 1
1.3 Precautions ....................................................................................................................................................... 3
1.3.1 Precautions for Monitoring on 3900 Series Base Stations ...................................................................... 3
1.3.2 Precautions for Monitoring on BTS3202Es and BTS3203Es ................................................................. 4
1.3.3 General Parameter Input Description ...................................................................................................... 4
2 Cell Performance Monitoring ..................................................................................................... 6

2.1 UL CoMP (Cell) Monitoring ............................................................................................................................ 6
2.1.1 Usage Scenario........................................................................................................................................ 6
2.1.2 Impact on Services .................................................................................................................................. 6
2.1.3 Parameters ............................................................................................................................................... 6
2.1.4 Monitoring Results .................................................................................................................................. 7
2.2 Satisfaction of Service Monitoring................................................................................................................... 7
2.2.1 Usage Scenario........................................................................................................................................ 7
2.2.2 Service Impact ........................................................................................................................................ 7
2.2.3 Parameters ............................................................................................................................................... 8
2.2.4 Monitoring Results .................................................................................................................................. 8
2.3 General Throughput Monitoring .................................................................................................................... 10
2.3.1 Usage Scenario...................................................................................................................................... 10
2.3.2 Service Impact ...................................................................................................................................... 10
2.3.3 Parameters ............................................................................................................................................. 10
2.3.4 Monitoring Results ................................................................................................................................ 10
2.4 Service Statistics Monitoring ......................................................................................................................... 13
2.4.1 Usage Scenario...................................................................................................................................... 13
2.4.2 Service Impact ...................................................................................................................................... 13
2.4.3 Parameters ............................................................................................................................................. 14
2.5 User Statistics Monitoring .............................................................................................................................. 15
2.5.1 Usage Scenario...................................................................................................................................... 15
2.5.2 Service Impact ...................................................................................................................................... 15
Issue 08 (2014-02-28) Huawei Proprietary and Confidential x

eNodeB
2.5.3 Parameters ............................................................................................................................................. 15

2.6 Usage of RB Monitoring ................................................................................................................................ 18
2.6.1 Usage Scenario...................................................................................................................................... 18
2.6.2 Service Impact ...................................................................................................................................... 18
2.6.3 Parameters ............................................................................................................................................. 18
2.7 ICIC (Cell) Monitoring .................................................................................................................................. 20
2.7.1 Usage Scenario...................................................................................................................................... 20
2.7.2 Service Impact ...................................................................................................................................... 20
2.7.3 Parameters ............................................................................................................................................. 20
2.8 Multi-User MIMO Monitoring ....................................................................................................................... 22
2.8.1 Usage Scenario...................................................................................................................................... 22
2.8.2 Service Impact ...................................................................................................................................... 23
2.8.3 Parameters ............................................................................................................................................. 23
2.9 RSSI Statistic Monitoring .............................................................................................................................. 23
2.9.1 Usage Scenario...................................................................................................................................... 23
2.9.2 Service Impact ...................................................................................................................................... 23
2.9.3 Parameters ............................................................................................................................................. 23
2.10 Interference Detection Monitoring ............................................................................................................... 27
2.10.1 Usage Scenario .................................................................................................................................... 27
2.10.2 Service Impact .................................................................................................................................... 27
2.10.3 Parameters ........................................................................................................................................... 27
2.10.4 Monitoring Results .............................................................................................................................. 28
2.11 TDD Interference Detection Monitoring ...................................................................................................... 30
2.11.1 Usage Scenario .................................................................................................................................... 30
2.11.2 Impact on Services .............................................................................................................................. 30
2.11.3 Parameters ........................................................................................................................................... 30
2.12 Multi-User BF (Cell) Monitoring ................................................................................................................. 32
2.12.1 Usage Scenario .................................................................................................................................... 32
2.12.3 Parameters ........................................................................................................................................... 32
2.13 Scheduled Users Statistic Monitoring .......................................................................................................... 34
2.13.1 Usage Scenario .................................................................................................................................... 34
2.13.2 Service Impact .................................................................................................................................... 34
2.13.3 Parameters ........................................................................................................................................... 34
Issue 08 (2014-02-28) Huawei Proprietary and Confidential xi

eNodeB
2.14 HARQ Statistic Monitoring.......................................................................................................................... 35

2.14.1 Usage Scenario .................................................................................................................................... 35
2.14.2 Service Impact .................................................................................................................................... 35
2.14.3 Parameters ........................................................................................................................................... 36
2.15 DCI Statistic Monitoring .............................................................................................................................. 39
2.15.1 Usage Scenario .................................................................................................................................... 39
2.15.2 Service Impact .................................................................................................................................... 39
2.15.3 Parameters ........................................................................................................................................... 39
2.16 DRB Statistics Monitoring ........................................................................................................................... 41
2.16.1 Usage Scenario .................................................................................................................................... 41
2.16.2 Service Impact .................................................................................................................................... 41
2.16.3 Parameters ........................................................................................................................................... 41
2.17 MLB Monitoring .......................................................................................................................................... 44
2.17.1 Usage Scenario .................................................................................................................................... 44
2.17.2 Service Impact .................................................................................................................................... 44
2.17.3 Parameters ........................................................................................................................................... 44
3 User Performance Monitoring .................................................................................................. 59

3.1 UL CoMP (User) Monitoring ......................................................................................................................... 59
3.1.1 Usage Scenario...................................................................................................................................... 59
3.1.2 Service Impact ...................................................................................................................................... 59
3.1.3 Parameters ............................................................................................................................................. 59
3.2 VQI Monitoring.............................................................................................................................................. 60
3.2.1 Usage Scenario...................................................................................................................................... 60
3.2.2 Service Impact ...................................................................................................................................... 60
3.2.3 Parameters ............................................................................................................................................. 60
3.3 DL RSRP/RSRQ Monitoring ......................................................................................................................... 62
3.3.1 Usage Scenario...................................................................................................................................... 62
3.3.2 Service Impact ...................................................................................................................................... 62
3.3.3 Parameters ............................................................................................................................................. 62
3.4 BLER Monitoring .......................................................................................................................................... 64
3.4.1 Usage Scenario...................................................................................................................................... 64
3.4.2 Service Impact ...................................................................................................................................... 64
3.4.3 Parameters ............................................................................................................................................. 64
Issue 08 (2014-02-28) Huawei Proprietary and Confidential xii

eNodeB
3.5 Power Headroom Monitoring ......................................................................................................................... 67

3.5.1 Usage Scenario...................................................................................................................................... 67
3.5.2 Service Impact ...................................................................................................................................... 67
3.5.3 Parameters ............................................................................................................................................. 67
3.6 Quality of Channel Monitoring ...................................................................................................................... 68
3.6.1 Usage Scenario...................................................................................................................................... 68
3.6.2 Service Impact ...................................................................................................................................... 68
3.6.3 Parameters ............................................................................................................................................. 68
Scheduling Monitoring ......................................................................................................................................... 71
3.6.5 Usage Scenario...................................................................................................................................... 71
3.6.6 Service Impact ...................................................................................................................................... 71
3.6.7 Parameters ............................................................................................................................................. 71
3.7 RLC Data Stream Monitoring ........................................................................................................................ 75
3.7.1 Usage Scenario...................................................................................................................................... 75
3.7.2 Service Impact ...................................................................................................................................... 75
3.7.3 Parameters ............................................................................................................................................. 75
3.8 Throughput Monitoring .................................................................................................................................. 76
3.8.1 Usage Scenario...................................................................................................................................... 76
3.8.2 Service Impact ...................................................................................................................................... 76
3.8.3 Parameters ............................................................................................................................................. 76
3.9 AQM Monitoring ........................................................................................................................................... 78
3.9.1 Usage Scenario...................................................................................................................................... 78
3.9.2 Service Impact ...................................................................................................................................... 78
3.9.3 Parameters ............................................................................................................................................. 78
3.10 UL Power Control Monitoring ..................................................................................................................... 79
3.10.1 Usage Scenario .................................................................................................................................... 79
3.10.2 Service Impact .................................................................................................................................... 79
3.10.3 Parameters ........................................................................................................................................... 80
3.11 DL Power Control Monitoring ..................................................................................................................... 81
3.11.1 Usage Scenario .................................................................................................................................... 81
3.11.2 Service Impact ..................................................................................................................................... 81
3.11.3 Parameters ........................................................................................................................................... 81
3.12 ICIC (User) Monitoring ............................................................................................................................... 83
3.12.1 Usage Scenario .................................................................................................................................... 83
Issue 08 (2014-02-28) Huawei Proprietary and Confidential xiii

eNodeB
3.12.2 Service Impact .................................................................................................................................... 83

3.12.3 Parameters ........................................................................................................................................... 83
3.13 MCS Count Monitoring ............................................................................................................................... 85
3.13.1 Usage Scenario .................................................................................................................................... 85
3.13.2 Service Impact .................................................................................................................................... 86
3.13.3 Parameters ........................................................................................................................................... 86
3.14 Multi-User BF (User) Monitoring ................................................................................................................ 88
3.14.1 Usage Scenario .................................................................................................................................... 88
3.14.3 Parameters ........................................................................................................................................... 88
3.15 SFN Detection Monitoring ........................................................................................................................... 89
3.15.1 Usage Scenario .................................................................................................................................... 89
3.15.3 Parameters ........................................................................................................................................... 89
3.16 Cell Combination Monitoring ...................................................................................................................... 91
3.16.1 Usage Scenario .................................................................................................................................... 91
3.16.3 Parameters ........................................................................................................................................... 91
4 Device Monitoring ...................................................................................................................... 94

4.1 CPRI BER Monitoring ................................................................................................................................... 94
4.1.1 Usage Scenario...................................................................................................................................... 94
4.1.2 Service Impact ...................................................................................................................................... 94
4.1.3 Parameters ............................................................................................................................................. 94
4.2 CPU Usage Monitoring .................................................................................................................................. 95
4.2.1 Usage Scenario...................................................................................................................................... 95
4.2.2 Service Impact ...................................................................................................................................... 95
4.2.3 Parameters ............................................................................................................................................. 96
4.3 RRU/RFU/BRU Output Power Monitoring ................................................................................................... 96
4.3.1 Usage Scenario...................................................................................................................................... 96
4.3.2 Service Impact ...................................................................................................................................... 96
4.3.3 Parameters ............................................................................................................................................. 97
4.4 Board Temperature Monitoring ...................................................................................................................... 98
4.4.1 Usage Scenario...................................................................................................................................... 98
Issue 08 (2014-02-28) Huawei Proprietary and Confidential xiv

eNodeB
4.4.2 Service Impact ...................................................................................................................................... 98

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

eNodeB
5 Transport Performance Monitoring ...................................................................................... 112

5.1 Local Pass-By Traffic Monitoring ................................................................................................................ 112
5.1.1 Usage Scenario.................................................................................................................................... 112
5.1.2 Service Impact .................................................................................................................................... 112
5.1.3 Parameters ........................................................................................................................................... 112
5.2 IP Performance Monitoring .......................................................................................................................... 113
5.2.1 Usage Scenario.................................................................................................................................... 113
5.2.2 Service Impact .................................................................................................................................... 113
5.2.3 Parameters ........................................................................................................................................... 113
5.3 Transport Port Flux Stat Monitoring ............................................................................................................ 114
5.3.1 Usage Scenario.................................................................................................................................... 114
5.3.2 Service Impact .................................................................................................................................... 114
5.3.3 Parameters ........................................................................................................................................... 114
5.4 Transport Link Flux Stat Monitoring ........................................................................................................... 122
5.4.1 Usage Scenario.................................................................................................................................... 122
5.4.2 Service Impact .................................................................................................................................... 122
5.4.3 Parameters ........................................................................................................................................... 122
5.5 UDP Test Monitoring ................................................................................................................................... 127
5.5.1 Usage Scenario.................................................................................................................................... 127
5.5.2 Service Impact .................................................................................................................................... 127
5.5.3 Parameters ........................................................................................................................................... 127
5.6 PPPoE Monitoring ....................................................................................................................................... 129
5.6.1 Usage Scenario.................................................................................................................................... 129
5.6.2 Service Impact .................................................................................................................................... 129
5.6.3 Parameters ........................................................................................................................................... 129
5.7 IPSec Performance Monitoring .................................................................................................................... 130
5.7.1 Usage Scenario.................................................................................................................................... 130
5.7.2 Service Impact .................................................................................................................................... 130
5.7.3 Parameters ........................................................................................................................................... 131
5.8 Transport OAM Monitoring ......................................................................................................................... 131
5.8.1 Usage Scenario.................................................................................................................................... 131
5.8.2 Service Impact .................................................................................................................................... 132
5.8.3 Parameters ........................................................................................................................................... 132
Issue 08 (2014-02-28) Huawei Proprietary and Confidential xvi

eNodeB

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

6.1 Sector Performance Monitoring ................................................................................................................... 137
6.1.1 Usage Scenario.................................................................................................................................... 137
6.1.2 Service Impact .................................................................................................................................... 137
6.1.3 Parameters ........................................................................................................................................... 137
Issue 08 (2014-02-28) Huawei Proprietary and Confidential xvii

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

Table 1-1 Performance monitoring types
Type Task Platform

Cell Performance UL CoMP (Cell) Monitoring M2000
Monitoring
Satisfaction of Service Monitoring M2000
General Throughput Monitoring M2000&LMT
Service Statistics Monitoring M2000
User Statistics Monitoring M2000&LMT
Usage of RB Monitoring M2000
ICIC (Cell) Monitoring M2000
Multi-User MIMO Monitoring M2000
RSSI Statistic Monitoring M2000
Interference Detection Monitoring M2000&LMT
TDD Interference Detection Monitoring M2000
Multi-User BF (Cell) Monitoring M2000
Scheduled Users Statistic Monitoring M2000
Issue 08 (2014-02-28) Huawei Proprietary and Confidential 1

eNodeB
Type Task Platform

HARQ Statistic Monitoring M2000
DCI Statistic Monitoring M2000
DRB Statistics Monitoring M2000
MLB Monitoring M2000
User Performance UL CoMP (User) Monitoring M2000
Monitoring
VQI Monitoring M2000
DL RSRP/RSRQ Monitoring M2000
BLER Monitoring M2000
Power Headroom Monitoring M2000
Quality of Channel Monitoring M2000
Scheduling Monitoring M2000
RLC Data Stream Monitoring M2000
Throughput Monitoring M2000
AQM Monitoring M2000
UL Power Control Monitoring M2000
DL Power Control Monitoring M2000
ICIC (User) Monitoring M2000
MCS Count Monitoring M2000
Multi-User BF (User) Monitoring M2000
SFN Detection Monitoring M2000
Cell Combination Monitoring M2000
Device Monitoring CPRI BER Monitoring M2000
CPU Usage Monitoring M2000&LMT
RRU/RFU/BRU Output Power M2000
Monitoring
Board Temperature Monitoring M2000&LMT
Clock Quality Test Monitoring M2000&LMT
IP Clock Data Collection Monitoring M2000&LMT
RRU/RFU Output Power Monitoring LMT
Rx Frequency Scanning LMT
DTF Test LMT

eNodeB
Type Task Platform

FFT Frequency Scan LMT
AAS LMT
Frequency Scanning Intermodulation LMT
Interference Detection
Transport Performance Local Pass-By Traffic Monitoring M2000&LMT
Monitoring
IP Performance Monitoring M2000&LMT
Transport Port Flux Stat Monitoring M2000&LMT
Transport Link Flux Stat Monitoring M2000&LMT
UDP Test Monitoring M2000
PPPoE Monitoring M2000&LMT
IPSec Performance Monitoring M2000&LMT
Transport OAM Monitoring LMT
Transport Auto Setup User Plane LMT
Monitoring
RRU/RFU Performance Sector Performance Monitoring LMT
Monitoring
1.3 Precautions
This section describes the precautions for monitoring on 3900 series base stations and
BTS3202Es,and BTS3203Es.
NOTE
This issue do not support the following monitoring tasks:
 LTE IP Link Monitoring
 LTE IP Path Performance Monitoring
 LTE SCTP Performance Monitoring
 LTE Resource Group Monitoring
1.3.1 Precautions for Monitoring on 3900 Series Base Stations

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

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

Take the following precautions for monitoring on BTS3202Es and BTS3203Es:
The values of Cabinet No., Subrack No., and Slot No. must be 0.
The value of Local Cell ID must be 0.
BTS3202Es and BTS3203Es do not support the following monitoring tasks:
− UL CoMP (Cell) Monitoring
− CPRI BER Monitoring
− TDD Interference Detection Monitoring
− Multi-User BF (Cell) Monitoring
− UL CoMP (User) Monitoring
− Multi-User BF (User) Monitoring
− SFN User Detection
− RRU/RFU Output Power Monitoring
− DTF Test
− AAS
− Frequency Scanning Intermodulation Interference Detection Monitoring
− Transport OAM Monitoring
BTS3202Es support the following monitoring tasks:
− Rx Frequency Scanning
− FFT Frequency Scan
BTS3202Es do not support PPP Performance monitoring and MP Performance monitoring in the Transport Port
Flux Stat Monitoring task.
BTS3202Es do not support the CA Property monitoring item in the following monitoring tasks:
− BLER Monitoring
− Power Headroom Monitoring
− Quality of Channel Monitoring
− 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.
1.3.3 General Parameter Input Description

UEIDs are used to trace UE-level performance tests. UEIDs can be set to S-Temporary
Mobile Subscriber Identity (STMSI), Random Value, and Trace Reference No.

eNodeB
The following describes how to obtain and use the three types of UEIDs:
STMSI and Random Value
The ue-Identity IE in the RRC Connection Request message contains the MMEc and
m-TMSI fields. Therefore, you can obtain the MMEc and m-TMSI in hexadecimal
format from the ue-Identity IE. Enter the MMEc and m-TMSI in decimal format on the
trace interface.
The RRC Connection Request message may carry a Random Value in hexadecimal
format. Enter the Random Value in hexadecimal format on the trace interface.
The STMSI in decimal format and Random Value in hexadecimal format can also be
queried by running DSP ALLUEBASICINFO.
If the EPC does not support IMSI-based single UE tracing on the entire network, use the STMSI and
Random Value to collect data for single UE tracing and monitoring.
A maximum of 30 NEs of the same version can be selected when creating the tracing and monitoring tasks
based on the STMSI and Random Value. If the specified UE can be successfully handed over among
multiple selected NEs over the X2 interface, the UE data can be continuously collected in the tracing and
monitoring task.
If the eNodeB is not a selected NE for this tracing task, the M2000 cannot continue collecting data, even
when the UE is handed over to the original eNodeB.
Due to the timing sequence problem, however, some data may fail to be recorded when the UE is handed
over to the target NE.
Trace Reference No.
For details about the Trace Reference No., see Trace ID in 3GPP TS 32.422. The value
range is 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).
Click displayed at the end of the User Trace ID of each tracing and monitoring task,
the M2000 will provide the existing Trace Reference No. on the live network.
The M2000 lists the Trace Reference No. of the first 200 tracing tasks in the recent two days.
If the EPC supports IMSI-based single UE tracing on the entire network, use the Trace Reference No. to
collect data for single UE tracing and monitoring.
A maximum of 30 NEs can be selected when creating the tracing and monitoring tasks based on the Trace
Reference No. The UE data can be continuously collected as long as the UE is served by the selected NEs.
If the eNodeB is not a selected NE for this tracing task, the M2000 cannot continue collecting data.
However, the M2000 can collect the data again when the UE is handed over to the original eNodeB.

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

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

None.
2.1.3 Parameters
Table 2-1 Parameters for UL CoMP (Cell) monitoring
Parameter Description
Local Cell ID Local cell ID of the cell performing cell-level UL CoMP
monitoring.
Monitor Period (ms) Interval of reporting monitoring results. It can be set to 1000, 2000.

eNodeB

Table 2-2 Results of UL CoMP (Cell) monitoring
Parameter Unit Value Description Formula

Range
UL CoMP Number 0 to 1000 The eNodeB reports the number N/A
Users Num of of UEs using the UL CoMP in
Scenario 1 scenario 1 to the M2000 at the
end of each monitoring period.
UL CoMP Users of Scenario 1:
UEs located at the cell edge
using the UL CoMP function.
Scenario 2 scenario 2 to the M2000 at the
end of each monitoring period.
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.
mixed Scenario mixed scenario to the M2000 at
the end of each monitoring
period.
UL CoMP Users of mixed
Scenario: UEs using the UL
CoMP of both scenario1 and
scenario 2 during a monitoring
period.
2.2 Satisfaction of Service Monitoring

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

None.

eNodeB
2.2.3 Parameters
Table 2-3 Parameters for satisfaction of service monitoring
Test Items It can be set to DL QCI1 Satisfaction rate of Service, DL QCI2
Satisfaction rate of Service, DL QCI3 Satisfaction rate of Service,
DL QCI4 Satisfaction rate of Service, UL QCI1 Satisfaction rate
of Service, UL QCI2 Satisfaction rate of Service, UL QCI3
Satisfaction rate of Service, UL QCI4 Satisfaction rate of Service,
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 Interval of reporting monitoring results. It can be set to 50, 100, 200,
(ms) 500, 1000, or 2000.

Table 2-4 Results of satisfaction of service monitoring

Range
CN N/A 0 to 5 ID of the operator for which satisfaction N/A
Operator ID of service monitoring is performed.

eNodeB

Range
CN % 0 to 100 Average QoS satisfaction rates of N/A
Operator different uplink services in a cell when
UL QCI[n] monitoring results are reported. n ranges
Satisfaction from 1 to 4. On the uplink, the uplink
rate of QoS satisfaction rate of QCI1 is
Service 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.
The uplink QoS satisfaction rates of
GBR services with QCIs 2 to 4 are
evaluated for each logical channel group.
The QoS satisfaction rate of a logical
channel group is evaluated based on the
transmitted data and the total amount of
data to be transmitted. The higher the
transmitted data volume, the higher the
QoS satisfaction rate.
CN % 0 to 100 Average QoS satisfaction rates of N/A
Operator different downlink services in a cell
DL QCI[n] when monitoring results are reported.
Satisfaction The value range of n is 1 to 4. On the
rate of downlink, the downlink QoS satisfaction
Service 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.
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 N/A Congesti Current congestion state of an operator N/A
State on, when monitoring results are reported.
Unconge
stion

eNodeB
2.3 General Throughput Monitoring

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

None.
2.3.3 Parameters
Table 2-5 Parameters for general throughput monitoring
Local Cell ID ID of the cell on which general throughput monitoring is
performed.
Test Items It can be set to RLC Throughput, RLC Throughput of GBR
service, RLC Throughput of NON-GBR service, or a
combination of some items.
CN Operator ID In a RAN sharing scenario, a cell can be shared by a maximum of
six operators. In a non-RAN sharing scenario, a cell can be used by
only one operator.
Monitor Period (ms) Interval of reporting monitoring results. It can be set to 50, 100,
200, 500, 1000, or 2000.

RLC Throughput
Table 2-6 Results of RLC Throughput monitoring

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

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

eNodeB

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

Range
which general
is performed.
Cell GBR Traffic bps 0 to Uplink throughput of (General RLC
Uplink RLC 300000000 GBR services in a cell. throughput of
Throughput Only RLC payloads are uplink GBR
included. The RLC services (Byte) x 8)
headers, retransmitted x 1000/Monitor
are excluded.

eNodeB

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

Range

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

eNodeB

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

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

None.

eNodeB
2.4.3 Parameters
Table 2-9 Parameters for service statistics monitoring
Test Items It can be set to Service Number of QCI1, Service Number of
QCI2, Service Number of QCI3, Service Number of QCI4,
Service Number of QCI5, Service Number of QCI6, Service
Number of QCI7, Service Number of QCI8, or Service Number of
QCI9.
Local Cell ID ID of the cell on which service 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.
(ms) 500, 1000, or 2000.

Table 2-10 Results of service statistics monitoring

Range
Service Number Number 0 to 4000 Total number of services N/A
of QCI[n] with different QCIs when
monitoring results are
reported. n ranges from 1
to 9.
which service statistic
monitoring is performed.
CN Operator Number 0 to 4000 Total number of services N/A
Service Number with different QCIs for
of QCI[n] an operator when
reported. n ranges from 1
to 9.

eNodeB
2.5 User Statistics Monitoring

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

None.
2.5.3 Parameters
Table 2-11 Parameters for user statistics monitoring
Test Items It can be set to Keep UL Synch Users Number, General
Users Number, NO-Activated Users Number, or a
combination of some items.
Local Cell ID ID of the cell on which user statistic monitoring is performed.
CN Operator ID In a RAN sharing scenario, a cell can be shared by a maximum
of six operators. In a non-RAN sharing scenario, a cell can be
used by only one operator.
Monitor Period (ms) Interval of reporting monitoring results. It can be set to 50,
100, 200, 500, 1000, or 2000.

Keep UL Synch Users Number
Table 2-12 Results of Keep UL Synch Users Number monitoring

Range
Keep UL Synch Number 0 to 2000 Number of users with uplink N/A
Users Number synchronization in a cell when
monitoring results are reported.
Users with uplink
synchronization are also known
as active users.
NOTE
CA users that use the local cell as
their SCell keeping uplink
synchronization are users with
uplink synchronization.

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

user statistic monitoring is
performed.
CN Operator Number 0 to 2000 Number of an operator's users N/A
Keep UL Synch with uplink synchronization
Users Number when monitoring results are
reported. Users with uplink
synchronization are also known
as active users.
NOTE
An operator's CA users that use
the local cell as their SCell
keeping uplink synchronization
are users with uplink
synchronization.
General Users Number
Table 2-13 Results of General Users Number monitoring

Range
General Number 0 to 2000 Number of connected users and Number of
Users users that are requesting access connected users
Number to the E-UTRAN in a cell when + Number of
the monitoring result is reported. users that are
Connected users consist of requesting access
active users and inactive users. to the E-UTRAN
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 N/A 0 to 5 ID of the operator for which user N/A
Operator ID statistic monitoring is
performed.

eNodeB

Range
CN Number 0 to 2000 Number of connected users and Number of
Operator users that are requesting access connected users
General to the E-UTRAN of an operator + Number of
Users when the monitoring result is users that are
Number reported. requesting access
Connected users consist of to the E-UTRAN
active users and inactive users.
Users that are requesting access
to the E-UTRAN consist of the
users initiating radio resource
control (RRC) connection
requests and the users that are
handed over to the E-UTRAN
cell.
NO-Activated Users Number
Table 2-14 Results of NO-Activated Users Number monitoring

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

user statistic monitoring is
performed.
NO-Activated Number 0 to 2000 Number of inactive users in a N/A
Users Number cell when monitoring results
are reported. Inactive users are
also known as users with
uplink out-of-synchronization.
NOTE
CA users that use the local cell as
their SCell keeping uplink
out-of-synchronization are users
with uplink
out-of-synchronization.
CN Operator Number 0 to 2000 Number of inactive users of an N/A

NO-Activated operator when monitoring
Users Number results are reported. Inactive
users are also known as users
with uplink
NOTE
An operator's CA users that use
the local cell as their SCell
keeping uplink
out-of-synchronization are users
with uplink

eNodeB
2.6 Usage of RB Monitoring

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

During high-volume traffic, the monitoring data may be lost but services are not affected.
2.6.3 Parameters
Table 2-15 Parameters for usage of RB monitoring
Local Cell ID ID of the cell on which RB usage monitoring is performed.
CN Operator ID In a RAN sharing scenario, a cell can be shared by a maximum of
six operators. In a non-RAN sharing scenario, a cell can be used by
only one operator.
200, 500, 1000, or 2000.

Table 2-16 Results of usage of RB monitoring

Range
Downlink Number 0 to Number of downlink RBs used N/A

Equivalent 2000000 within a monitoring period,
Used RB Num 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.
In a SFN or cell combination
scenario, the number of used
PRBs in each physical cell is
accumulated.

eNodeB

Range
Uplink Number 0 to Number of uplink RBs used N/A
Equivalent 2000000 within a monitoring period,
Used RB Num which is the total number of RBs
occupied by the PUSCH,
PUCCH, and PRACH within all
TTIs in the monitoring period.
accumulated.
Downlink Freq Number 0 to Number of RBs allocated for N/A
Diversity Used 2000000 downlink diversity scheduling
RB Num within all TTIs in a monitoring
period.
accumulated.
Downlink Freq Number 0 to Number of RBs allocated for N/A
Select Used RB 2000000 downlink frequency selective
Num scheduling within all TTIs in a
monitoring period.
accumulated.
Downlink Number 0 to Number of RBs allocated for N/A
HARQ RB 2000000 downlink HARQ retransmission
Used RB Num within all TTIs in a monitoring
period.
accumulated.
Uplink PUCCH Number 0 to 200000 Number of RBs used by the N/A
RB Num PUCCH within all TTIs in a
monitoring period.
CN Operator N/A 0 to 5 ID of the operator for which RB N/A
ID usage monitoring is performed.

eNodeB

Range
CN Operator Number 0 to 200000 Number of downlink RBs used N/A
Downlink by the PDSCH of the operator
Equivalent within all TTIs in a monitoring
Used RB Num period.
NOTE
The value of this parameter

equals the actual number of
downlink RBs used by the
operator.
CN Operator Number 0 to 200000 Number of uplink RBs used by N/A
Uplink the PUSCH of the operator
Equivalent within all TTIs in a monitoring
Used RB Num period.
NOTE
The value of this parameter equals
the actual number of uplink RBs
used by the operator.
2.7 ICIC (Cell) Monitoring

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

None.
2.7.3 Parameters
Table 2-17 Parameters for ICIC (cell) monitoring
Test Items It can be set to HII Information, OI Information, Proportion of
Uplink High Interference RB in System Bandwidth, Uplink Edge
User RB Information, Uplink Neighbor Cell List Information,
Cell Downlink Edge Bandwidth Information, or a combination of
some items.
Local Cell ID ID of the cell on which ICIC (cell) monitoring is performed.
(ms) 500, 1000, or 2000.

eNodeB

HII information
Table 2-18 Results of HII information monitoring

Range
Valid RB Number 0 to 100 Number of valid RBs in one HII N/A
Num in One when monitoring results are
HII sent reported, which is the same as
the number of RBs occupied by
the current cell bandwidth.
OI information
Table 2-19 Results of OI information monitoring

Range
Valid RB Num Number 0 to 100 Number of valid RBs in one OI N/A
in One OI sent when monitoring results are
reported, which is the same as
the number of RBs occupied by
the current cell bandwidth.
Proportion of Uplink High Interference RB in System Bandwidth
Table 2-20 Results of Proportion of Uplink High Interference RB in System Bandwidth

monitoring

Range
Proportion of Uplink % 0 to 100 Proportion of uplink N/A
High Interference high-interference RBs in the
RB in System serving cell to RBs occupied by
Bandwidth the current cell bandwidth when
monitoring results are reported.

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

Range
Uplink Edge User Number 0 to 100 Number of valid RBs in the N/A
Valid RB Num available frequency band for
uplink cell edge users (CEUs)
when monitoring results are
reported.
Uplink Neighbor Cell List Information
Table 2-22 Results of Uplink Neighbor Cell List Information monitoring
Parameter Unit Value Range Description Formula

Uplink Valid Number 0 to 32 Number of valid neighboring N/A
Interference cells used for ICIC (cell)
Neighbor Cell when monitoring results are
Num reported.
Cell Downlink Edge Band Information
Table 2-23 Results of Cell Downlink Edge Band Information monitoring

Range
Cell Downlink Edge Numb 0 to 100 Number of valid RBs in the N/A
Band Valid RB Num er cell downlink edge
frequency band when
reported.
2.8 Multi-User MIMO Monitoring

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

eNodeB

None.
2.8.3 Parameters
Table 2-24 Parameters for Multi-User MIMO monitoring
Local Cell ID ID of the cell on which MU-MIMO monitoring is performed.

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

Table 2-25 Results of Multi-User MIMO monitoring

MIMO UE Pair 0 to 10000 Total number of UEs paired with N/A
Pair Num uplink MU-MIMO during all
TTIs in the monitoring period.
Two UEs paired with
MU-MIMO are called one pair.
2.9 RSSI Statistic Monitoring

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

None.
2.9.3 Parameters
Table 2-26 Parameters for RSSI statistic monitoring
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.

eNodeB
Local Cell ID ID of the cell on which interference RSSI statistic detect monitoring
is performed.
200, 500, 1000, or 2000.

Table 2-27 Results of RSSI statistic monitoring

RRU Cabinet N/A 0 to 62 Number of N/A
No. the cabinet
that houses
the RRU
serving the
cell. This
parameter is
set to an
actual value
only in
scenarios of
SFN and Cell
Combination
in LTE TDD,
and is set to
an invalid
value in other
scenarios.
An invalid
value is
displayed as
N/A on the
M2000.

eNodeB

RRU Subrack N/A 4 to 5 Number of N/A
No. 60 to 254 the subrack
that houses
the RRU
serving the
cell. This
parameter is
set to an
actual value
only in
scenarios of
SFN and Cell
Combination
in LTE TDD,
and is set to
an invalid
value in other
scenarios.
An invalid
value is
displayed as
N/A on the
M2000.
RRU Slot No. N/A 0 to 8 Number of N/A
the slot that
houses the
RRU serving
the cell. This
parameter is
set to an
actual value
only in
scenarios of
SFN and Cell
Combination
in LTE TDD,
and is set to
an invalid
value in other
scenarios.
An invalid
value is
displayed as
N/A on the
M2000.

eNodeB

RBk dBm –140 to –50 RSSI of an AntNum∑AntNum
AntIdx = 0 ∑n = 0 {P(AntIdx, k, n)}
- 1 11
RSSI_RB(k) =
Spectrum RB. The AntNum
Information power of 12
subcarriers in
the RB is where
summed and AntNum indicates the
then averaged number of antennas for the
for multiple current cell.
antennas.
RSSIs of the P( ) indicates
RBs falling the receive power of
beyond the subcarrier n in RBk
bandwidth received by antenna AntIdx.
are reported
as 0 by layer
1.
Received dBm –140 to –50 RSSI within
Signal the current
Strength system where
Indicator bandwidth.
SysRB indicates the
number of RBs in the
current system bandwidth.
System Number 6, 15, 25, 50, Current N/A
Bandwidth 75, 100 system
(Number of 25, 50, 75, and bandwidth.
RB) 100 in
BTS3202Es and
BTS3203Es.
antenna[y] dBm –140 to –50 RSSI for SysRB 11
RSSI_Ant(AntIdx) = ∑ ∑{P(AntIdx, k, n)}
RSSI antenna y k=0 n=0
within the
current where
system
AntNum indicates the
bandwidth. y
number of antennas for the
ranges from 0
current cell.
to 7.
P( ) indicates
the receive power of
subcarrier n in RBk of
antenna AntIdx. The value
of AntIdx is y.

eNodeB
2.10 Interference Detection Monitoring

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

None.
2.10.3 Parameters
Table 2-28 Parameters for interference detection monitoring
left unspecified in scenarios other than the SFN and Cell
Combination in LTE TDD.
Local Cell ID ID of the cell on which interference detection monitoring is
performed.
200, 500, 1000, or 2000.

eNodeB

Table 2-29 Results of interference detection monitoring

Range
RRU Cabinet N/A 0 to 62 Number of N/A
No. the cabinet
that houses
the RRU
serving the
cell. This
parameter is
set to an
actual value
only in
scenarios of
SFN and Cell
Combination
in LTE TDD,
and is set to
an invalid
value in other
scenarios.
An invalid
value is
displayed as
N/A on the
M2000.
RRU Subrack N/A 4 to 5 Number of N/A
No. 60 to 254 the subrack
that houses
the RRU
serving the
cell. This
parameter is
set to an
actual value
only in
scenarios of
SFN and Cell
Combination
in LTE TDD,
and is set to
an invalid
value in other
scenarios.
An invalid
value is
displayed as
N/A on the
M2000.

eNodeB

Range
RRU Slot No. N/A 0 to 8 Number of N/A

the slot that
houses the
RRU serving
the cell. This
parameter is
set to an
actual value
only in
scenarios of
SFN and Cell
Combination
in LTE TDD,
and is set to
an invalid
value in other
scenarios.
An invalid
value is
displayed as
N/A on the
M2000.
CELL AVG dBm –140 to –50 Average
Interference RB-level
Noise Power interference where
per RB (dBm) noise power
PUSCH_RB indicates the
of the
number of RBs on the
PUSCH in
current PUSCH.
the whole
system
bandwidth.
PUCCH Number 0 to 48 Number of N/A
Extended RB extended
Number PHCCH RBs,
which is also
the number of
RBs reserved
on the band
edges for the
PUSCH.
Max RB Number 0 to 26 Maximum N/A
Number of number of
PUCCH RBs in the
current
PUCCH

eNodeB

Range
System Number 6, 15, 25, 50, Current N/A
Bandwidth 75, 100 system
(Number of 25, 50, 75, bandwidth.
RB) and 100 in
BTS3202Es
and
BTS3203Es.
RBk dBm –140 to –50 Average
Interference PUSCH
Noise Power interference where
(dBm) noise power AntNum indicates the
on each RB. number of antennas for the
Interference current cell. IN(AntIdx, k,
of the RBs n) indicates the receive
falling power of subcarrier n in RB
beyond the k received by antenna
PUSCH AntIdx.
bandwidth is
reported as 0.
2.11 TDD Interference Detection Monitoring

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

None.
2.11.3 Parameters
Table 2-30 Parameters for TDD interference detection monitoring
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.

eNodeB

Table 2-31 Results of TDD interference detection monitoring

Range
RRU Cabinet No. N/A 0 to 62 Number of the cabinet that N/A
houses the RRU serving the
cell.
RRU Subrack No. N/A 4 to 5 Number of the subrack that N/A
60 to 254 houses the RRU serving the
cell.
RRU Slot No. N/A 0 to 8 Number of the slot that houses N/A
the RRU serving the cell.
Uppts IN Power dBm –32768 to Power of the interference in N/A
+32767 the uplink pilot time slots
(UpPTSs).
RB Group x IN dBm –32768 to Interference noise (IN) of the N/A
Power +32767 xth RB group on the full
bandwidth.
Receive Power of dBm –32768 to Receive power of symbol 0 in N/A
Symbol 0 in First +32767 the first uplink subframe.
UL Subframe This parameter is invalid if the
LBBPc frame transmitted
upon initiation of the
monitoring request does not
have loads.
Receive Power of dBm –32768 to Receive power of the last N/A
the 6th (or 4th) +32767 symbol in the first uplink
Symbol in First subframe. If normal cyclic
UL Subframe prefixes (CPs) are used, the
6th symbol is measured; if
extended CPs are used, the 4th
symbol is measured.
This parameter is invalid if the
have loads.
Receive Power of dBm –32768 to Receive power of symbol 0 in N/A
Symbol 0 in Last +32767 the last uplink subframe.
UL Subframe This parameter is invalid if the
have loads.

eNodeB

Range
Receive Power of dBm –32768 to Receive power of the last but N/A
the Last but Two +32767 two symbols in the first uplink
Symbols on the subframe. If normal CPs are
Last UL Subframe used, the 11th symbol is
measured; if extended CPs are
used, the 9th symbol is
measured.
This parameter is invalid if the
have loads.
2.12 Multi-User BF (Cell) Monitoring

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

None.
2.12.3 Parameters
Table 2-32 Parameters for multi-user BF (cell) monitoring
Local Cell ID ID of the cell on which cell-level multi-user BF monitoring is
performed.
200, 500, 1000, or 2000.

eNodeB

Table 2-33 Results of multi-user BF (cell) monitoring

Range
Indep-Indep Number 0 to 1000 Number of downlink spectrum N/A
Number of resources used by UEs of
successful independent scheduling that have
MUBF pairing been successfully paired using
RB MUBF. It is obtained by
accumulating the number of RBs
used by a UE at each TTI and
calculating the average number at
the end of the monitoring period.
For cell-level monitoring, the
related RBs of all RRUs are
counted.
Indep-Indep Pair 0 to 1000 Number of pairs of UEs of N/A
Number of independent scheduling that have
users' been successfully paired using
successful MUBF. It is obtained by
pairing Users 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.
Indep-Indep Number 0 to 1000 Number of RBs that can be used N/A
Number of by UEs of independent
enable pairing scheduling that can be paired
RB using MUBF, excluding the RBs
used for retransmission, non-TM
8 single stream, and the VoIP
service. It is obtained by
Indep-Joint Number 0 to 1000 Number of downlink spectrum N/A
Number of resources used by UEs of
successful independent scheduling that have
MUBF pairing been successfully paired using
RB MUBF with UEs of combined
scheduling. It is obtained by
For cell-level monitoring, the
related RBs of all RRUs are
counted.

eNodeB

Range
Indep-Joint Pair 0 to 1000 Number of UE pairs that have N/A
Number of been successfully paired using
users' MUBF between UEs of
successful independent scheduling and UEs
pairing Users of combined scheduling. It is
obtained by accumulating the
number of UE pairs at each TTI
and calculating the average
number based on the number of
TTIs at the end of the monitoring
period. For cell-level monitoring,
the related RBs of all RRUs are
counted.
Joint-Joint Number 0 to 1000 Number of RBs that can be used N/A
Number of by UEs of combined scheduling
enable pairing that can be paired using MUBF,
RB 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 period. For cell-level
monitoring, the related RBs of all
RRUs are counted.
2.13 Scheduled Users Statistic Monitoring

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

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

performed.

eNodeB
200, 500, 1000, or 2000.

Table 2-35 Results of scheduled users statistic monitoring

Range
Total DLSCH Number 0 to 65535 Total number of UEs in N/A
Users Within downlink scheduling mode
Monitor Period within a monitoring period.
Frequency downlink frequency selective
Selected Users scheduling mode within a
Within Monitor monitoring period.
Period
Diversity Users downlink diversity scheduling
Within Monitor mode within a monitoring
Period period.
Total ULSCH Number 0 to 65535 Total number of UEs in uplink N/A
Users Within scheduling mode within a
Monitor Period monitoring period.
2.14 HARQ Statistic Monitoring

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

None.

eNodeB
2.14.3 Parameters
Table 2-36 Parameters for HARQ statistic monitoring
Test Items It can be set to DL HARQ State, UL HARQ State, or a combination
of the items.
Local Cell ID ID of the cell on which HARQ statistic monitoring is performed.
Monitor Period Interval of reporting monitoring results. It can be set to 1000 or 2000.
(ms)

DL HARQ State
Table 2-37 Results of DL HARQ State monitoring

Range
DL PDSCH Number 0 to 64000 Number of ACKs for codeword m N/A
Code[m] (m = {0, 1}) within a monitoring
ACK Num period. The greater the proportion
of the number of ACKs to the
total number of ACKs, NACKs,
and DTXs, the more successfully
received messages from the
eNodeB, indicating effective cell
coverage.
For details about ACK and
NACK, see 3GPP TS 36.321.
DL PDSCH Number 0 to 64000 Number of NACKs for codeword N/A
Code[m] m (m = {0, 1}) within a
NACK Num monitoring period. The greater the
proportion of the number of
NACKs to the total number of
ACKs, NACKs, and DTXs, the
less successfully received
messages from the eNodeB.
For details about ACK and
NACK, see 3GPP TS 36.321.

eNodeB

Range
DL PDSCH Number 0 to 64000 Number of NoRsps for codeword N/A
Code[m] m (m = {0, 1}) within a
NoRsp Num 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.
For details about the HARQ RTT,
see DL PDSCH Rsp for [m] TTI
Num.
DL PDSCH Number 0 to 64000 Number of DTXs for codeword m N/A
Code[m] (m = {0, 1}) within a monitoring
DTX Num period. DTX indicates that the
eNodeB fails to detect the HARQ
feedback.
For details, see section 7.3 in
3GPP TS 36.213.
DL PDSCH Number 0 to 64000 Number of times the HARQ N/A
Version[m] redundancy version in transport
Num blocks (TBs) sent from the
eNodeB is m (m = {0, 1, 2, 3})
within a monitoring period.
DL PDSCH Number 0 to 64000 Number of times that DTXs and N/A
Code[m] NACKs cannot be distinguished
DTX/NACK for downlink codeword m (m =
Num {0, 1}) within a monitoring
period.
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.

eNodeB

Range
DL PDSCH Number 0 to 64000 Number of times the eNodeB N/A
Rsp for [m] receives the HARQ feedback
TTI Num within a downlink scheduling
interval m TTIs (One TTI equals
to one millisecond) within a
monitoring period.
m = {8, 9, 10, 11}. Any value
greater than 11 is treated as 11.
This item monitors the duration
that the eNodeB internally
processes the HARQ feedback.
According to the protocol, the
HARQ RTT equals to 8 TTIs for
FDD mode. For TDD mode, the
HARQ RTT varies depending on
the subframe distribution rate. If
the duration exceeds the HARQ
RTT, the eNodeB experiences
internal processing exceptions.
UL HARQ State
Table 2-38 Results of UL HARQ State monitoring

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

eNodeB

Range
UL PUSCH Number 0 to 64000 Number of times the UE does not N/A
DTX Num transmit data on the PUSCH within
a monitoring period. The greater
the proportion of the number of
DTXs to the total number of ACKs,
NACKs, and DTXs, the more the
times that the UE incorrectly
demodulates the downlink PDCCH
data.
UL PUSCH Number 0 to 64000 Number of times the HARQ N/A
Version[n] redundancy version for the eNodeB
Num uplink scheduling is m (m = {0, 1,
2, 3}) within a monitoring period.
For details, see 3GPP TS 36.321.
2.15 DCI Statistic Monitoring

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

None.
2.15.3 Parameters
Table 2-39 Parameters for DCI statistic monitoring
Test Items It can be set to DCI STATISTIC.

Local Cell ID ID of the cell on which DCI statistic monitoring is performed.
Monitor Period Interval of reporting monitoring results. It can be set to 1000 or
(ms) 2000.

eNodeB

Table 2-40 Results of DCI statistic monitoring

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

Utilization utilization within a in downlink
Within a monitoring period. DCI/Total number of
Monitoring Downlink DCI is DCI CCEs within the
Period format n, where n is 1, monitoring period.
1A, 1B, 1C, 1D, 2, 2A,
and 2B.
Comm DCI % 0 to 100 Common DCI Total number of CCEs
Utilization utilization within a in common DCI/Total
Within a monitoring period. number of CCEs
Monitoring Common DCI is DCI within the monitoring
Period format 3 and DCI period.
format 3A.

eNodeB

Range
Total CCE Number 0 to 100000 Total number of CCEs N/A
Num Within within a monitoring
a Monitoring period. If the CFI
Period 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.
2.16 DRB Statistics Monitoring

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

None.
2.16.3 Parameters
Table 2-41 Parameters for DRB statistics monitoring
Test Items It can be set to DL DRB STATISTIC, UL DRB STATISTIC, or a
combination of the items.
Local Cell ID ID of the cell on which DRB statistic monitoring is performed.
Monitor Period Interval of reporting monitoring results. It can be set to 1000 or 2000.
(ms)

DL DRB STATISTIC

eNodeB
Table 2-42 Results of downlink DRB statistics monitoring

Range
Number of Packet 0 to Total number of data packets N/A
Packets 300000000 received by the downlink PDCP
Received at the layer within a monitoring
DL PDCP period.
Number of Bits Bit 0 to Total throughput for data N/A
Received at the 300000000 packets received by the
DL PDCP downlink PDCP layer within a
monitoring period.
Number of TBs Number 0 to Total number of TBs for N/A
for DL MAC 300000000 downlink MAC scheduling
scheduling within a monitoring period.
Number of Bits Bit 0 to Total number of bits contained N/A
for DL MAC 300000000 in the TBs for downlink MAC
scheduling scheduling within a monitoring
period.
Number of Number 0 to Total number of times that the N/A
Times DL RLC 300000000 downlink RLC layer transmits
Sends Data in data in acknowledgment (AM)
AM mode mode within a monitoring
period.
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 Number 0 to Total number of times that the N/A

Times DL RLC 300000000 downlink RLC layer transmits
Sends Data in data in unacknowledgment
UM mode (UM) mode within a
monitoring period.
Number of Succ Number 0 to Total number of times that the N/A
Trans DL PDCP 4294967295 downlink PDCP SDU packets
SDUs with are successfully transmitted
QCI[n] over the QCI[n] within a
monitoring period, in which n
ranges from 1 to 9.
Processing ms 0 to Total processing delay of N/A
Delay of DL 4294967295 downlink packets over the
PDCP SDUs QCI[n] within a monitoring
with QCI[n] period, in which n ranges from
1 to 9.
UL DRB STATISTIC

eNodeB
Table 2-43 Results of uplink DRB statistics monitoring

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

eNodeB
2.17 MLB Monitoring

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

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

(ms) 2000.
Ncell 1 Mandatory. For details, see Table 2-45.
Ncell 2 Optional. For details, see Table 2-45.
Table 2-45 Parameters for neighboring cells
Ncell x Type Neighboring cell types. It can be set to LTEinterFreq,
UTRAN, GERAN, LTEintraFreq, or NULL.
NOTE
 Ncell 1 is mandatory and must not be set to NULL.
 The value of x ranges from 1 to 4.
MCC Mobile country code of neighboring E-UTRAN, UTRAN, or

GERAN cells.
MNC Mobile network code of neighboring E-UTRAN, UTRAN,
or GERAN cells.
LTEinter NCell x eNodeB ID of the eNodeB serving a neighboring inter-frequency cell.
ID This parameter is valid only when Ncell Type is set to
LTEinterFreq.

eNodeB
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 of the eNodeB serving a neighboring intra-frequency cell.
ID This parameter is valid only when Ncell Type is set to
LTEintraFreq.
LTEintra NCell x Cell ID ID of a neighboring intra-frequency cell. This parameter is
valid only when Ncell Type is set to LTEintraFreq.
UTRAN NCell x RNC ID ID of the RNC of a neighboring UTRAN cell. This
parameter is valid only when Ncell Type is set to UTRAN.
UTRAN NCell x CELL ID ID of a neighboring UTRAN cell. This parameter is valid
only when Ncell Type is set to UTRAN.
GSM NCell x Geran ID ID of a neighboring GERAN cell. This parameter is valid
only when Ncell Type is set to GERAN.
GSM NCell x Geran Lac Location area code of a neighboring GERAN cell. This
parameter is valid only when Ncell Type is set to GERAN.

Table 2-46 Results of MLB monitoring

Local Cell ID N/A 0~35 ID of the cell N/A
on which MLB
monitoring is
performed.
Serving Cell % 0 to 100 PRB usage in N/A
downlink GBR downlink GBR
traffic PRB services of the
usage(%) serving cell
within a
monitoring
period.
Serving Cell uplink % 0 to 100 PRB usage in N/A
Non-GBR traffic uplink
PRB usage(%) non-GBR
services of the
serving cell
within a
monitoring
period.

eNodeB

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

eNodeB

Intra-frequency N/A Decimal number, which Reasons for the N/A
MLB type must be converted to a intra-frequency
binary number for cause MLB.
value determination.
Meanings represented
by each bit in the binary
number are described as
follows:
BIT0: UlGBRIntraMLB
BIT1: DlGBRIntraMLB
BIT2:
UlNonGBRIntraMLB
BIT3:
DlNonGBRIntraMLB
BIT4:
UlTotalIntraMLB
BIT5:
DlTotalIntraMLB
If the value of a bit is 0,
the intra-frequency
MLB is not triggered by
the cause specified by
the bit. If the value of a
bit is 1, the
intra-frequency MLB is
triggered by the cause
specified by the bit.
If a GUI value is 8, and
the corresponding
binary value is 001000,
the intra-frequency
MLB is caused by
DlNonGBRIntraMLB.

eNodeB

Inter-frequency N/A Decimal number, which Reasons for the N/A
MLB type must be converted to a inter-frequency
binary number for cause MLB.
value determination.
follows:
BIT0: UlGBRInterMLB
BIT1: DlGBRInterMLB
BIT2:
UlNonGBRInterMLB
BIT3:
DlNonGBRInterMLB
BIT4:
UlTotalInterMLB
BIT5:
DlTotalInterMLB
the inter-frequency
MLB is not triggered by
the bit. If the value of a
bit is 1, the
inter-frequency MLB is
triggered by the cause
specified by the bit.
the corresponding
the intra-frequency
MLB is caused by
DlNonGBRInterMLB.

eNodeB

Utran MLB Type N/A Decimal number, which Reasons for the N/A
must be converted to a inter-RAT
binary number for cause MLB to
value determination. UTRAN.
follows:
BIT0:
UlGBRUtranMLB
BIT1:
DlGBRUtranMLB
BIT2:
UlNonGBRUtranMLB
BIT3:
DlNonGBRUtranMLB
BIT4:
UlTotalUtranMLB
BIT5:
DlTotalUtranMLB
the MLB to UTRAN is
not triggered by the
cause specified by the
bit. If the value of a bit
is 1, the MLB to
UTRAN is triggered by
the bit. If a GUI value is
8, and the corresponding
the MLB to UTRAN is
caused by
DlNonGBRUtranML
B.

eNodeB

IfGeran MLB Type N/A Decimal number, which Reasons for N/A
must be converted to a inter-RAT
binary number for cause MLB to
value determination. GERAN.
NOTE
number are described as BTS3202Es
and
follows:
BTS3203Es do
BIT0: not support this
UlGBRGeranMLB monitoring
item.
BIT1:
DlGBRGeranMLB
BIT2:
UlNonGBRGeranMLB
BIT3:
DlNonGBRGeranMLB
BIT4:
UlTotalGeranMLB
BIT5:
DlTotalGeranMLB
the MLB to GERAN is
not triggered by the
cause specified by the
bit. If the value of a bit
is 1, the MLB to
GERAN is triggered by
the bit.
the corresponding
the MLB to GERAN is
caused by
DlNonGBRGeranML
B.
LTEintra NCell N/A Depending on eNodeB Mobile country N/A
MCC configurations code of a
neighboring
intra-frequency
cell.
LTEintra NCell N/A Depending on eNodeB Mobile network N/A
MNC configurations code of a
neighboring
intra-frequency
cell.

eNodeB

LTEintra NCell N/A Depending on eNodeB ID of the N/A
eNodeB ID configurations eNodeB
serving a
neighboring
intra-frequency
cell.
LTEintra NCell N/A Depending on eNodeB ID of a N/A
Cell ID configurations neighboring
intra-frequency
cell.
Ue number in the Number 0 to 254 Number of cell N/A
edge of the serving edge UEs near a
cell near to the neighboring
intra-frequency cell intra-frequency
cell.
CIO value of the dB –24 to 24 CIO value of N/A
serving cell (dB) the serving cell.
CIO margin value dB 0 to 2 CIO margin N/A
of the serving value of the
cell(dB) serving cell.
CIO adjusted cause N/A 0: NULL Cause values of N/A
of the serving cell 1: Serving cell spring to CIO adjustment
modify on the serving
cell and its
2: Serving cell spring to neighboring
comeback cells.
3: Serving cell spring to
quit MLB
4: Serving cell respond
to modify
to comeback
to quit MLB
Intra-Frequency % 0 to 100 PRB usage in N/A
cell uplink GBR uplink GBR
traffic PRB services target
usage(%) of the
intra-frequency
cell.
cell downlink GBR downlink GBR
traffic PRB services in the
usage(%) target
intra-frequency
cell.

eNodeB

cell uplink uplink
PRB usage(%) services in the
target
intra-frequency
cell.
cell downlink downlink
target
intra-frequency
cell.
cell uplink Total uplink GBR
usage(%) services in the
target
intra-frequency
cell.
cell downlink Total downlink GBR
target
intra-frequency
cell.

eNodeB

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

eNodeB

Success ratio of % 0 to 100 Success rate of N/A
handover to the handovers from
intra-frequency the serving cell
cell(%) to the target
intra-frequency
cell.
UE number of Number 0 to 254 Number of UEs N/A
MLB handover to that are handed
the intra-frequency over to the
cell target
intra-frequency
cell based on
MLB. The
value becomes
0 after MLB is
exited.
LTEinter NCell N/A Depending on eNodeB Mobile country N/A
neighboring
inter-frequency
cell.
LTEinter NCell N/A Depending on eNodeB Mobile network N/A
neighboring
inter-frequency
cell.
LTEintra NCell N/A Depending on eNodeB ID of the N/A
eNodeB ID configurations eNodeB
serving a
neighboring
inter-frequency
cell.
LTEinter NCell N/A Depending on eNodeB ID of a N/A
Cell ID configurations neighboring
inter-frequency
cell.
Inter-Frequency % 0 to 100 PRB usage in N/A
cell uplink GBR uplink GBR
usage(%) target
inter-frequency
cell.
cell downlink GBR downlink GBR
usage(%) target
inter-frequency
cell.

eNodeB

cell uplink uplink
target
inter-frequency
cell.
cell downlink downlink
target
inter-frequency
cell.
cell uplink Total uplink GBR
usage(% services in the
target
inter-frequency
cell.
cell downlink Total downlink GBR
target
inter-frequency
cell.

eNodeB

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

eNodeB

Success ratio of Number 0 to 100 Success rate of N/A
handover to the handovers from
inter-frequency the serving cell
cell(%) to the target
inter-frequency
cell.
MLB transfer load entering MLB
control for the transfer load
inter-frequency cell control for the
inter-frequency
cell. The value
becomes 0 after
UEs exit MLB.
MLB handover to handed over to
the inter-frequency the
cell inter-frequency
cell for MLB
after the UE
enters MLB
transfer load
control. The
value becomes
0 after UEs exit
MLB.
UTRAN NCell N/A Depending on eNodeB Mobile country N/A
neighboring
UTRAN cell.
UTRAN NCell N/A Depending on eNodeB Mobile network N/A
neighboring
UTRAN cell.
UTRAN NCell N/A Depending on eNodeB ID of the RNC N/A
RNC ID configurations of a
neighboring
UTRAN cell.
UTRAN NCell Cell N/A Depending on eNodeB ID of a N/A
ID configurations neighboring
UTRAN cell.
Utran Cell load N/A 0: Overload Load status of a N/A
Status 1: Congestion neighboring
UTRAN cell.
2: Normal
3: Invalid

eNodeB

Cause of utran cell N/A 0: Null Cause of a N/A
not being MLB cell 1: Algo_Not_triggered neighboring
UTRAN cell
2: not being
Ncell_Radio_Resource selected as the
_Unmeet MLB cell.
the utran cell the UTRAN
cell for MLB.
The value
becomes 0 after
UEs exit MLB.
GSM NCell MCC N/A Depending on eNodeB Mobile country N/A
configurations code of a
neighboring
GERAN cell.
GSM NCell MNC N/A Depending on eNodeB Mobile network N/A
configurations code of a
neighboring
GERAN cell.
GSM NCell Geran N/A Depending on eNodeB ID of a N/A
ID configurations neighboring
GERAN cell.
GSM NCell Geran N/A Depending on eNodeB Location area N/A
Lac configurations code of a
neighboring
GERAN cell.
Cause of geran cell N/A 0: Null Cause of a N/A
not being MLB cell 1: Algo_Not_triggered neighboring
GERAN cell
not being
selected as the
MLB cell.
the geran cell the GERAN
cell for MLB.
The value
becomes 0 after
UEs exit MLB.

eNodeB
Performance Monitoring Reference 3 User Performance Monitoring
3 User Performance Monitoring
3.1 UL CoMP (User) Monitoring

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

None.
3.1.3 Parameters
Table 3-1 Parameters for UL CoMP (user) monitoring
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 It must be configured when the UEID Type parameter is set to
STMSI.
Random Value It must be configured when the UEID Type parameter is set to
Random Value.
PLMN 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 It must be configured when the UEID Type parameter is set to
Trace Reference No.
Monitor Period (ms) Interval of reporting monitoring results. It can be set to 1000, 2000.

eNodeB

Table 3-2 Results of UL CoMP (user) monitoring

Range
Physical Cell N/A 0 to 503 Physical cell identifier of the N/A
Identifier serving cell.
UL CoMP User N/A N/A Category of the UL CoMP used by N/A
Indication a UE:
 Normal User
 UL CoMP User of Scenario 1
 UL CoMP User of Scenario 2
 UL CoMP User of mixed
Scenario
3.2 VQI Monitoring

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

None.
3.2.3 Parameters
Table 3-3 Parameters for VQI monitoring
STMSI.
STMSI.
Random Value.

eNodeB
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 It must be configured when the UEID Type parameter is set to Trace
Reference No.
Monitor Period Interval of reporting monitoring results. It is set to 2500 by default.
(ms)
Test Item It can be set to DL Quality of Voice, or UL Quality of Voice. All
items are monitored by default.

DL Quality of Voice monitoring
Table 3-4 Results of DL Quality of Voice monitoring
Monitoring Unit Value Range Description Formula

Results
Physical Cell N/A 0 to 503 Physical cell identifier of N/A
Identifier the serving cell.
DL.VQI(0.01) 0.01 0 to 500 Downlink voice quality N/A
indicator.
LossRatio(%) ‰ 0 to 1000 Downlink voice packet N/A
loss rate.
DL.Delay(ms) ms 0 to 65535 Average delay of N/A
downlink voice packets
over the air interface.
UL Quality of Voice monitoring
Table 3-5 Results of UL Quality of Voice monitoring
Monitoring Unit Value Description Formula

Results Range
Physical Cell N/A 0 to 503 Physical cell identifier of the serving N/A
Identifier cell.
UL.VQI(0.01) 0.01 0 to 500 Uplink voice quality indicator. N/A
UL.FER(‰) ‰ 0 to Proportion of the number of uplink N/A
1000 lost and delayed voice packets to the
total uplink voice packets.

eNodeB

Results Range
UL.LFE(times) times 0 to 255 Maximum number of times when a N/A

user's packets are consecutively lost
in the uplink.
UL.OutDelayR ‰ 0 to Proportion of uplink delayed voice N/A
atio(‰) 1000 packets to the total uplink voice
packets.
3.3 DL RSRP/RSRQ Monitoring

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

None.
3.3.3 Parameters
Table 3-6 Parameters for DL RSRP/RSRQ monitoring
STMSI.
STMSI.
Random Value.
respectively.
Trace Reference No.

eNodeB
480, 640, 1024, or 2048.

Table 3-7 Results of DL RSRP/RSRQ monitoring
ServCell PCI N/A 0 to 503 Physical cell ID of a serving N/A

cell.
ServCell dBm -140 to -44 RSRP of a serving cell. N/A
RSRP
ServCell dB -19.5 to -3 RSRQ of a serving cell. N/A
RSRQ
NeighborCell N/A 0 to 503 Physical cell ID of the nth N/A
PCI[n] neighboring cell. n is an integer
from 1 to 8.
NOTE
This field specifies the sequence
for reporting the measurement
reports of neighboring cells. A
maximum of eight neighboring
cells are dynamically displayed.
NeighborCell dBm –140 to –44 RSRP of the nth neighboring cell. n N/A
RSRP[n] is an integer from 1 to 8.
NOTE
NeighborCell dB –19.5 to –3 RSRQ of the nth neighboring cell. n N/A

RSRQ[n] is an integer from 1 to 8.
NOTE

eNodeB
3.4 BLER Monitoring

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

None.
3.4.3 Parameters
Table 3-8 Parameters for BLER monitoring
UEID Type It can be set to STMSI, Random Value, or Trace Reference
No.
STMSI.
STMSI.
Random Value.
Trace Reference No. When this parameter is selected, MCC
and MNC specify the mobile country code and mobile network
code, respectively.
Trace Reference No.
200, 500, 1000, or 2000.
Test Item It can be set to Init BLER, Pdcch BLER, or Resident BLER.
All items are monitored by default.

Init BLER

eNodeB
Table 3-9 Results of Init BLER monitoring

Range
CA Property N/A N/A Carrier aggregation N/A

property of a user.
The result contains
Non CA, CA PCell
and CA SCell.
Physical Cell N/A 0 to 503 Physical cell identifier N/A
Identifier of the serving cell.
Downlink ‰ 0 to 1000 BLER of initial TB Total number of TBs that
IBLER transmission on a fail to be initially
PDSCH within a transmitted on the
monitoring period. PDSCH x 1000/Total
number of initially
transmitted TBs on the
PDSCH within the
monitoring period
Uplink ‰ 0 to 1000 BLER of initial TB Total number of TBs that
IBLER transmission on a fail to be initially
PUSCH within a transmitted on the
monitoring period. PUSCH x 1000/Total
number of initially
PUSCH within the
monitoring period
Resident BLER
Table 3-10 Results of Resident BLER monitoring

Range

property of a user.
The result contains
Non CA, CA PCell
and CA SCell.
Physical Cell N/A 0 to 503 Physical cell N/A
Identifier identifier of the
serving cell.

eNodeB

Range
Downlink ‰ 0 to 1000 BLER of the last TB Number of times TBs
RBLER retransmission on a that last fail to be
PDSCH within a retransmitted on the
monitoring period. PDSCH x 1000/Total
number of initially
PDSCH within the
monitoring period
Uplink RBLER ‰ 0 to 1000 BLER of the last TB Number of times TBs
retransmission on a that last fail to be
PUSCH within a retransmitted on the
monitoring period. PUSCH x 1000/Total
number of initially
PUSCH within the
monitoring period
PDCCH BLER
Table 3-11 Results of PDCCH BLER monitoring

Range
CA Property N/A N/A Carrier N/A

aggregation
property of a
user. The
result contains
Non CA, CA
PCell and CA
SCell.
Physical Cell N/A 0 to 503 Physical cell N/A
Identifier identifier of the
serving cell.
PDCCH BLER ‰ 0 to 1000 BLER of Number of times
DLGRANT DLGRANTs decoded
decoding on a incorrectly x 1000/Total
PDCCH within number of DLGRANTs sent
a monitoring on a PDCCH
period. The number of DLGRANTs
decoded incorrectly is the
number of DTXs that were
the feedback given to the
DLGRANTs sent on a
PDCCH.

eNodeB
3.5 Power Headroom Monitoring

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

None.
3.5.3 Parameters
Table 3-12 Parameters for power headroom monitoring
STMSI.
STMSI.
Random Value.
respectively.
Trace Reference No.
200, 500, 1000, or 2000.

eNodeB

Table 3-13 Result of power headroom monitoring

Range
CA Property N/A N/A Carrier aggregation property of a N/A
user. The result contains Non
CA, CA PCell and CA SCell.
Power Headroom dB –23 to +40 Power headroom last reported by N/A
the UE.
For details about formula of
Power Headroom, see 3GPP TS
36.213, 36.321, and 36.133.
3.6 Quality of Channel Monitoring

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

During high-volume traffic, the monitoring data may be lost but services are not affected.
3.6.3 Parameters
Table 3-14 Parameters for quality of channel monitoring
STMSI.
STMSI.
Random Value.

eNodeB
respectively.
Trace Reference No.
200, 500, 1000, or 2000.
Test Item It can be set to CQI , ULSINR & UL DMRS RSRP or UL SRS
RSRP. All items are monitored by default.

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

CA Property N/A N/A Carrier aggregation property N/A
of a user. The result
contains Non CA, CA PCell
and CA SCell.
SINR 0.01 dB –12700 to Average SINR for the full N/A
+12700 bandwidth of the eNodeB
monitored.
UL DMRS 0.01 dB –15000 to Uplink reference signal N/A
RSRP –3000 received power.
CQI
Table 3-16 Results of CQI monitoring

Range

property of a user. The
result contains Non CA,
CA PCell and CA SCell.

eNodeB

Range
UE Code Number 1 to 2 Number of transmitted N/A
Count code words in the downlink
when monitoring results are
reported.
Effective ms 41 to 44 Valid length of the N/A
Len aperiodic CQI for the full
bandwidth. This parameter
takes effect only when the
aperiodic CQI frequency
selection is configured.
CQI N/A 0 to 31 Five-bit value mapped to
the originally reported CQI
for the full bandwidth.
Code Index N/A 0 to 3 Index of the UE codeword. N/A
UL SRS RSRP
Table 3-17 Results of UL SRS RSRP

property of a user.
The result contains
Non CA, CA PCell
and CA SCell.
Physical Cell N/A 0~503 Physical cell ID of a N/A
ServCell 0.01dBm -15000 ~ -3000 RSRP of a serving N/A
RSRP cell.
NeighborCel N/A 0~503 Physical cell ID of the N/A
l PCI[n] nth neighboring cell.
NOTE
This field specifies the

sequence for reporting
the measurement
reports of neighboring
cells. A maximum of
eight neighboring
cells are dynamically
displayed.

eNodeB

NeighborCel 0.01dBm -15000 ~ -3000 of the nth RSRP
l RSRP neighboring cell.
NOTE
This field specifies the

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

None.
3.6.7 Parameters
Table 3-18 Parameters for scheduling monitoring
STMSI.
STMSI.
Random Value.

eNodeB
respectively.
Trace Reference No.
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.

eNodeB

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

and CA SCell.
Number of SRs Number 0 to 64000 Number of SRs reported by N/A
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.
For details, see 3GPP TS
36.321.
UL BSR of Service
Table 3-20 Results of UL BSR of Service monitoring

CA Property N/A N/A Carrier aggregation property of N/A
a user. The result contains
Non CA, CA PCell and CA
SCell.

eNodeB

Byte Length of Bit 0 to 150000 Buffered data volume of the N/A
LCG BS[n] 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].
For details, see 3GPP TS
36.321.
Percentage of DRX activity timer in DRX timer
Table 3-21 Results of Percentage of DRX activity timer in DRX timer monitoring

Range

user. The result contains Non
CA, CA PCell and CA SCell.
TTIs in GAP Number 0 to Number of accumulated TTIs in N/A
State 4294967295 the call gapping (GAP) state
during the monitoring period.
TTIs in DRX Number 0 to Number of accumulated TTIs in N/A
State 4294967295 the DRX state during the
monitoring period.
Number of TTI Number 0 to Number of accumulated TTIs N/A
4294967295 between the establishment and the
release of an L2 case.

eNodeB
3.7 RLC Data Stream Monitoring

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

None.
3.7.3 Parameters
Table 3-22 Parameters for RLC data stream monitoring
STMSI.
STMSI.
Random Value.
respectively.
Reference No.

Table 3-23 Result of RLC data stream monitoring

DRB No. N/A 1 to 8 Number of the DRB. N/A

eNodeB

RLC Buffer Byte 0~3000000 Data stream of the RLC N/A
Length SDUs to be sent on the data
radio bearer (DRB) from the
downlink buffer area at the
RLC layer when monitoring
results are reported.
3.8 Throughput Monitoring

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

None.
3.8.3 Parameters
Table 3-24 Parameters for throughput monitoring
MMEc It must be configured when the UEID Type parameter is set to STMSI.
mTMSI It must be configured when the UEID Type parameter is set to STMSI.
Random Value It must be configured when the UEID Type parameter is set to Random
Value.
Reference No. When this parameter is selected, MCC and MNC specify
the mobile country code and mobile network code, respectively.
Reference No.
(ms) 500, 1000, or 2000.
Test Item It can be set to Throughput of MAC or Throughput of RLC. Both

eNodeB

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

Range
result contains Non
CA, CA PCell and CA
SCell.
DRB No. N/A 1to 8 Number of the DRB. N/A
Downlink bps 0 to Total throughput of the (Downlink RLC
RLC 300000000 downlink RLC SDUs throughput on the
Throughput sent on the DRB at the RLC logical
RLC layer within a channels (byte) x 8)
monitoring period. x 1000/Monitoring
period (ms)
Uplink RLC bps 0 to Total throughput of the (Uplink RLC
Throughput 300000000 uplink RLC SDUs throughput on the
received on the DRB at RLC logical
the RLC layer within a channels (byte) x 8)
monitoring period. x 1000/Monitoring
period (ms)
Throughput of MAC
Table 3-26 Results of MAC throughput monitoring

result contains Non
CA, CA PCell and CA
SCell.

eNodeB

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

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

None
3.9.3 Parameters
Table 3-27 Parameters for AQM monitoring

STMSI.
STMSI.
Random Value.

eNodeB
respectively.
Reference No.
(ms) 500, 1000, or 2000.
Test Item It can be set to DL RLC buffer length of eNB or Percentage of
AQM discard package. Both items are monitored by default.

Table 3-28 Results of AQM monitoring

Range
Number of Packets Packet 0 to 20000 Number of RLC SDUs to be sent N/A
in RLC Buffer on the DRB from the downlink
RLC buffer area at the end of a
monitoring period.
Number of Packet 0 to 20000 Number of SDUs discarded by N/A
Discarded Packets AQM.
3.10 UL Power Control Monitoring

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

None.

eNodeB
3.10.3 Parameters
Table 3-29 Parameters for UL power control monitoring
UEID Type It can be set to STMSI, Random Value, or Trace Reference
No.
STMSI.
STMSI.
Random Value.
Trace Reference No. When this parameter is selected, MCC
and MNC specify the mobile country code and mobile network
code, respectively.
Trace Reference No.
200, 500, 1000, or 2000.

PUCCH SINR&RSRP
Table 3-30 Result of PUCCH SINR&RSRP monitoring

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

eNodeB

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

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

None.
3.11.3 Parameters
Table 3-31 Parameters for DL power control monitoring
STMSI.
STMSI.
Random Value.
respectively.
Trace Reference No.
200, 500, 1000, or 2000.
Test Item It can be set to PUCCH SINR&RSRP. It is monitored by default.

eNodeB

PDSCH UE
Table 3-32 Results of PDSCH UE monitoring

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

Range

Power Offset 0.01 dB –1500 to Power offset between each N/A
of PHICH +2000 RE on the PHICH and the
pilot when monitoring

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

Power Offset of 0.01 dB –1500 to +2000 Offset between the power N/A
PDCCH for transmitting each RE
on the PDCCH and the
pilot power when
reported.
TTI ms 0 to 4294967295 TTI for the PDCCH N/A
power transmitted at the
MAC layer.
3.12 ICIC (User) Monitoring

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

None.
3.12.3 Parameters
Table 3-35 Parameters for uplink ICIC monitoring
STMSI.
STMSI.

eNodeB
Random Value.
respectively.
Trace Reference No.
200, 500, 1000, or 2000.
Test Item It can be set to User DL Property information, User PDSCH
RB information, User PUSCH RB information, or User UL
Property information. All items are monitored by default.

User downlink property
Table 3-36 Results of user downlink property monitoring

of a user. The result contains
SCell.
DL User ICIC N/A N/A User property. It includes the N/A
Property CEUs, cell center users, and
users at full frequency bands.
PDSCH RB Usage
Table 3-37 Results of PDSCH RB usage monitoring

Range

SCell.

eNodeB

Range
PDSCH RB Num N/A N/A Number of RBs used at the N/A

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

Range

user. The result contains Non CA,
Identifier cell.
PDSCH RB N/A N/A Number of RBs used at the PUSCH. N/A
Num
User uplink property
Table 3-39 Results of user uplink property monitoring

Range

user. The result contains Non CA,
Identifier cell.
UL User ICIC N/A N/A User property. It includes the CEUs, N/A
Property cell center users, and users at full
frequency bands.
3.13 MCS Count Monitoring

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

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

None.
3.13.3 Parameters
Table 3-40 Parameters for MCS statistic monitoring

STMSI.
STMSI.
Random Value.
respectively.
Trace Reference No.
Monitor Period (ms) Interval of reporting monitoring results. It can be set to 1000 or
2000.
Test Item It can be set to DL MCS or UL MCS. Both items are monitored
by default.

DL MCS
Table 3-41 Results of DL MCS monitoring

SCell.

eNodeB

DLSCH Code Number 0 to 2000 Total number (n) of scheduling N/A
0 Num[n] on codeword 0 in the downlink
scheduling within a monitoring
period.
The value n indicates the MCS
order, and ranges from 0 to 31.
DLSCH Code Number 0 to 200,000 Total number (n) of RBs on N/A
0 RBs[n] codeword 0 in the downlink
period.
DLSCH Code Number 0 to 2000 Total number (n) of scheduling N/A
1 Num[n] on codeword 1 in the downlink
period.
DLSCH Code Number 0 to 200,000 Total number (n) of RBs on N/A
1 RBs[n] codeword 1 in the downlink
period.
order and ranges from 0 to 31.
UL MCS
Table 3-42 Results of UL MCS monitoring

of a user. The result contains
SCell.
ULSCH Number 0 to 2000 Total number (n) of uplink N/A
Num[n] scheduling within a
monitoring period.
The value n indicates the
MCS order, and its value
range is from 0 to 31.

eNodeB
ULSCH Number 0 to 200,000 Total number (n) of RBs in N/A

RBs[n] the uplink scheduling within
The value n indicates the
MCS order, and its value
range is from 0 to 31.
3.14 Multi-User BF (User) Monitoring

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

None.
3.14.3 Parameters
Table 3-43 Parameters for multi-user BF (user) monitoring
UEID-MME MME serving a user.
UEID-TMSI TMSI to be monitored.
Trace Reference Trace reference number to be monitored.
No.
200, 500, 1000, or 2000.
Test Type Bitmap Bit 0 and bit 1 respectively represent Indep-Indep MUBF pairing
and Indep-Joint MU-BF pairing. By default, all the corresponding
items are monitored.

Table 3-44 Results of multi-user BF (user) monitoring

Range
Physical Cell N/A 0 to Physical cell identifier of the serving N/A
Identifier 503 cell.

eNodeB

Range
Indep-Indep Number 0 to Number of RBs used by common N/A
Number of 1000 UEs that have been successfully
successful paired using MUBF with UEs of
MUBF pairing independent scheduling. It is
RB 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.
Indep-Joint Number 0 to Number of RBs used by common N/A
Number of 1000 UEs that have been successfully
successful paired using MUBF with UEs of
MUBF pairing combined scheduling. It is obtained
RB by accumulating the number of RBs
calculating the average number at the
end of the monitoring period.
3.15 SFN Detection Monitoring

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

None.
3.15.3 Parameters
Table 3-45 Parameters for SFN detection monitoring
UEID-MME MME serving a user.

UEID-TMSI TMSI to be monitored.
Trace Reference Trace reference number to be monitored.
No.
200, 500, 1000, or 2000.
Test Type Bitmap Bit 0 and bit 1 respectively represent UL RRU Detect and DL
RRU Detect. All items are monitored by default.

eNodeB

Table 3-46 Results of SFN detection monitoring

UL User N/A Joint Sch User User attributes can be queried N/A
Mode and Independent on real time to determine the
Sch User scheduling mode of the user for
uplink transmission.
DL User N/A Joint Sch User User attributes can be queried N/A
Mode and Independent on real time to determine the
Sch User scheduling mode of the user for
downlink transmission.
Physical N/A 0 to 503 Physical cell identifier of the N/A
Cell serving cell.
Identifier
UL RRU N/A 0 to 1048575 eNodeB ID of the RRU used for N/A
eNodebId uplink transmission.
UL RRU N/A 0 to 62 Number of the cabinet that N/A
Cabinet No. houses the RRU used for uplink
transmission.
UL RRU N/A 4 to 5 and 60 to Number of the subrack that N/A
Subrack No. 254 houses the RRU used for uplink
transmission.
UL RRU N/A 0 to 8 Number of the slot that houses N/A
Slot No. the RRU used for uplink
transmission.
UL RRU N/A Target RRU and It indicates that the RRU used N/A
Flag Work RRU for uplink transmission is a
target RRU or a working RRU.
Uplink SRS dBm –141 to –43 Uplink RSRP of sounding N/A
RSRP reference signals (SRSs)
measured by all the RRUs on
the SFN.
Uplink dB –20 to +60 Uplink SINR of the user. N/A
SRS&DMR
S SINR
Uplink dB –20 to +60 DMRS SINR measured by all N/A
DMRS the RRUs on the SFN.
SINR
DL RRU N/A 0 to 1048575 eNodeB ID of the RRU used for N/A
eNodebId downlink transmission.

eNodeB

DL RRU N/A 0 to 62 Number of the cabinet that N/A
Cabinet No. houses the RRU used for
DL RRU N/A 4 to 5 and 60 to Number of the subrack that N/A
Subrack No. 254 houses the RRU used for
DL RRU N/A 0 to 8 Number of the slot that houses N/A
Slot No. the RRU used for downlink
transmission.
DL RRU N/A Target RRU and It indicates that the RRU used N/A
Flag Work RRU for downlink transmission is a
target RRU or a working RRU.
3.16 Cell Combination Monitoring

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

None.
3.16.3 Parameters
Table 3-47 Parameters for cell combination monitoring
MMEc MME serving a user.

mTMSI TMSI to be monitored.
2000.
Test Items Either DL Cell Combination RRU Detect or UL Cell
Combination RRU Detect can be selected for monitoring. All

eNodeB

Table 3-48 Results of cell combination monitoring

UL User Mode N/A Joint Sch User User attributes can be N/A
and queried on real time to
Independent determine the scheduling
Sch User mode of the user for uplink
transmission.
DL User Mode N/A Joint Sch User User attributes can be N/A
and queried on real time to
Independent determine the scheduling
Sch User mode of the user for
UL RRU eNodebId N/A 0 to 1048575 eNodeB ID of the RRU N/A
used for uplink
transmission.
UL RRU Cabinet N/A 0 to 62 Number of the cabinet that N/A
No. houses the RRU used for
UL RRU Subrack N/A 4 to 5 and 60 to Number of the subrack N/A
No. 254 that houses the RRU used
for uplink transmission.
UL RRU Slot No. N/A 0 to 8 Number of the slot that N/A
houses the RRU used for
UL RRU Flag N/A Target RRU It indicates that the RRU N/A
and Work RRU used for uplink
transmission is a target
RRU or a working RRU.
Uplink SRS RSRP dBm -141 to -43 Uplink RSRP of SRSs N/A
measured by all the RRUs
in a cell combination
scenario.
Uplink dB -20 to 60 Uplink SINR of the user. N/A
SRS&DMRS SINR
Uplink DMRS SINR dB -20 to 60 DMRS SINR measured by N/A
all the RRUs in a cell
combination scenario.
DL RRU eNodebId N/A 0 to 1048575 eNodeB ID of the RRU N/A
used for downlink
transmission.

eNodeB

DL RRU Cabinet N/A 0 to 62 Number of the cabinet that N/A
No. houses the RRU used for
DL RRU Subrack N/A 4 to 5 and 60 to Number of the subrack N/A
No. 254 that houses the RRU used
for downlink transmission.
DL RRU Slot No. N/A 0 to 8 Number of the slot that N/A
houses the RRU used for
DL RRU Flag N/A Target RRU It indicates that the RRU N/A
and Work RRU used for downlink
transmission is a target
RRU or a working RRU.

eNodeB
Performance Monitoring Reference 4 Device Monitoring
4 Device Monitoring
4.1 CPRI BER Monitoring

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

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

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

Table 4-2 Results of CPRI BER monitoring

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 e^(-9) 0 to 1000000000 Downlink BER in the test N/A

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

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

None.

eNodeB
4.2.3 Parameters
Table 4-3 Parameters for CPU usage monitoring
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 Interval of reporting monitoring results. It is set to the fixed value 5.
(Seconds)

Table 4-4 Results of CPU usage monitoring

Board No. N/A N/A The board number is N/A
displayed as follows:
Cabinet No.: Subrack No.:
Slot No.
CPU No. N/A N/A The default CPU number is 0. N/A
Type N/A N/A The CPU type is as follows: N/A
 CPU.
 DSP.
 Slave CPU.
CPU Usage % 0 to 100 CPU usage when monitoring N/A
4.3 RRU/RFU/BRU Output Power Monitoring

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

None.

eNodeB
4.3.3 Parameters
Table 4-5 Parameters for RRU/RFU/BRU Output Power monitoring
Cabinet No. Number of the cabinet where the board for RRU/RFU/BRU
Output Power monitoring is located.
Subrack No. Number of the subrack where the board for RRU/RFU/BRU
Output Power monitoring is located.
Slot No. Number of the slot where the board for RRU/RFU/BRU Output
Power monitoring is located.
2000, or 3000.

Table 4-6 Results of RRU/RFU/BRU Output Power monitoring

Index of TX N/A 0 to 7 Index of TX channel. N/A
NOTE
0 and 1 for
BTS3202Es and
BTS3203Es.
Index of Carrier N/A 0 to 1  If only 0 is displayed, N/A

the RRU supports one
NOTE
carrier.
0 for BTS3202Es
 If both 0 and 1 are
and BTS3203Es.
displayed, the
RRU/RFU supports
two carriers.
TX Freq of TX N/A The actual value Downlink frequency of a N/A
Carrier[n] depends on the carrier.
working frequency
band of the
monitored RF
module.
Output power of 0.1 dBm -200 to -1, and Output power of a N/A
Carrier[n] 0 to 1000 carrier.
NOTE
0 to 370 for
BTS3202Es and
BTS3203Es.

eNodeB

Mode N/A LTE-FDD, and Working mode of the N/A
LTE-TDD board to be monitored.
Output Power of 0.1 dBm -200 to -1, and 0 to Output power of a TX N/A
TX Branch 1000 channel.
NOTE
0 to 370 for
BTS3202Es and
BTS3203Es.
4.4 Board Temperature Monitoring

This task is used to monitor board or eNodeB temperature.

None.
4.4.3 Parameters
Table 4-7 Parameters for temperature monitoring
Cabinet No. Number of the cabinet where the board/eNodeB for board
temperature monitoring is located.
Subrack No. Number of the subrack where the board/eNodeB for board
temperature monitoring is located.
Slot No. Number of the slot where the board/eNodeB for board temperature
monitoring is located.
Monitor Period Interval of reporting monitoring results. It can be set to 1000, 2000,
(ms) or 3000.
Save File The Save File check box is selected by default, and monitoring
results are automatically saved in the default path. The file name, file
format, and save path can be set.
NOTE
This parameter is available only on the LMT.

eNodeB

Table 4-8 Results of board temperature monitoring

Results Range
Board Temperature ℃ -100 to 200 Board temperature. N/A
0x7FFF:
Invalid
values are not
displayed.
PA Temperature ℃ -100 to 200 Power amplifier N/A
0x7FFF: temperature.
Invalid
values are not
displayed.
Branch Index N/A 0 to 1 Index of PA branch. This N/A
monitoring item is available
only on the M2000.
Number of PA Number 1 to 8 Number of power N/A
amplifiers. This monitoring
NOTE
item is available only on
1 and 2 for the LMT.
BTS3202Es
and
BTS3203Es.
PA branch ℃ –100 to 200 Temperature of power N/A

Temperature 0x7FFF: amplifier branches when
Invalid multiple power amplifiers
values are not are available in the RRU or
displayed. RFU.
4.5 Clock Quality Test Monitoring

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

None.

eNodeB
4.5.3 Parameters
Table 4-9 Parameters for clock quality test monitoring
Cabinet No. Number of the cabinet where the board/eNodeB for clock quality
Subrack No. Number of the subrack where the board/eNodeB for clock quality
Slot No. Number of the slot where the board/eNodeB for clock quality
Test Type Type of clock quality monitoring. It can be set to Frequency
Discrimination or Phase Discrimination.
Report Interval of reporting monitoring results. This parameter must be set to
Period(Seconds) 1.

Table 4-10 Results of clock quality monitoring

Cabinet No. N/A 0 to 7 Number of the N/A
cabinet where the
board whose
monitoring results
are reported is
located.
Subrack No. N/A 0 to 1 Number of the N/A
subrack where the
board whose
monitoring results
are reported is
located.
Slot No. N/A 0 to 7 Number of the slot N/A
where the board
whose monitoring
results are reported is
located.
TestResultT N/A Frequency Test result types. N/A
ype discrimination
Phase
discrimination

eNodeB

Count Frequency Frequency Frequency N/A
Value discrimination: discrimination: discrimination value
ppb –5000 to 5000 or phase
Phase Phase discrimination value.
discrimination: ns discrimination:
–200000 to
200000
4.6 IP Clock Data Collection Monitoring

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

None.
4.6.3 Parameters
Table 4-11 Parameters for IP clock data collection monitoring
Cabinet No. Number of the cabinet where the board/eNodeB for IP clock data
collection monitoring is located.
Subrack No. Number of the subrack where the board/eNodeB for IP clock data
Slot No. Number of the slot where the board/eNodeB for IP clock data
Report Interval of reporting monitoring results. This parameter must be set to
Period(Seconds) 1.

eNodeB

Table 4-12 Results of IP clock data collection monitoring

Range
Tp1 Max QoS Value ns –263 to Maximum delay per second for N/A
263–1 transmitting packets from the
clock server to the eNodeB
Tp1 Min QoS Value ns –263 to Minimum delay per second for N/A
clock server to the eNodeB
Tp2 Max QoS Value ns –263 to Maximum delay per second for N/A
eNodeB to the clock server
Tp2 Min QoS Value ns –263 to Minimum delay per second for N/A
eNodeB to the clock server
4.7 RRU/RFU Output Power Monitoring

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

None.
4.7.3 Parameters
Table 4-13 Parameters for RRU/RFU output power monitoring
Cabinet No. Number of the cabinet where the board for output power monitoring
is located.
Subrack No. Number of the subrack where the board for output power monitoring
is located.
Slot No. Number of the slot where the board for output power monitoring is
located.
Monitor Period Interval of reporting monitoring results. It can be set to 1000, 2000,
(ms) or 3000.

eNodeB

Table 4-14 Results of RRU/RFU output power monitoring

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

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

NOTE
BTS3202Es and
BTS3203Es do not
item.
Monitor Period ms 1000, 2000, 3000 Interval of reporting N/A

(ms) monitoring results.
Output power of 0.1 dBm [1800, 1999]: Output power of a N/A
Tx Freq[n] corresponding to TX[n] channel, in
(0.1dBm) [–200, –1] which n can be set to 0
Mode:LTE-FDD 0xFFFF: invalid or 1.
value, which is not
displayed in GUI.

eNodeB

TX branch Output 0.1 dBm [1800..1999]: Output power of a N/A
power of TX[n] corresponding to TX[n] channel, in
[–200..–1]. which n can be set to 0
0xFFFF: invalid or 1.
value, which is not
displayed in GUI.
4.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.
4.8.3 Parameters
Table 4-15 Parameters for uplink frequency scan monitoring
Cabinet No. Number of the cabinet where the RRU, RFU, or BRU for uplink
frequency scanning is located.
Subrack No. Number of the subrack where the RRU, RFU, or BRU for uplink
Slot No. Number of the slot where the RRU, RFU, or BRU for uplink
Start RF Start RF frequency in uplink frequency scanning. It can be set to
Frequency(200kHz) 4130, 4410, 8560, 9260, 9610, or 12510. The default value is 9610.
End RF End RF frequency in uplink frequency scanning. It can be set to
Frequency(200kHz) 4235, 4565, 8915, 9540, 9890, or 12840. The default value is 9890.
Scanning Frequency Frequency interval in uplink frequency scanning.
Interval(200kHz)
Scanning Time Interval in uplink frequency scanning.
Interval(0.1s)
results are automatically saved in the default path. The file name,
file format, and save path can be set.

eNodeB

Table 4-16 Results of uplink frequency scan monitoring

Results Range
Cabinet No. N/A 0 to 62 Number of the cabinet where the N/A
board whose monitoring results are
Subrack No. N/A 4 to 5, 60 Number of the subrack where the N/A
to 254 board whose monitoring results are
Slot No. N/A 0 to 8 Number of the slot where the board N/A
whose monitoring results are
StartFeq 200 4130 Start frequency for uplink frequency N/A
kHz 4410 scanning.
8560
9260
9610
12510
EndFeq 200 4235 End frequency for uplink frequency N/A
kHz 4565 scanning.
8915
9540
9890
12840
Branch[n] 0.1 -2^31 to Received total bandwidth power of N/A
dBm 2^31 branch[n]. The value of n ranges
from 1 to 4 for 3900 series base
stations, and is 1 for BTS3202Es
and BTS3203Es.
Data Type N/A N/A Data type of uplink frequency N/A
scanning result.
4.9 DTF Test

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

eNodeB

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

Table 4-18 Results of DTF test

Range

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

eNodeB

Range
TX Channel N/A 0 to 7 Number of the branch on which N/A
No. monitoring results are reported.
Feeder Test N/A N/A Test results. N/A
Display Range m 0 to 120 VSWR DTF monitoring results. N/A
of Feeder Test
Results
4.10 FFT Frequency Scan

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

None.
4.10.3 Parameters
Table 4-19 Parameters for FFT Frequency Scanning
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 Index of RX channel[n] of the RRU in 3900 series base stations or
Channel[n] BRU in BTS3202Es for FFT frequency scan. The value of n is 1 or 2.
Mode Mode for FFT frequency scan.

eNodeB
Scan Mode Mode of checking the output power of each transmit channel and
carrier. It can be set to High-Resolution Online Frequency,
Broadband Online Frequency, or Broadband Offline Frequency.
TX channel is provided by the RF port of the RRU/RFU/BRU. A carrier is

similar to a cell.
RBW(KHZ) Time frequency of FFT frequency detection, in units of kHz.

 When Scan Mode is set to High-Resolution Online Frequency,
the value range of this parameter is from 15 to 200, and the default
value is 100.
 When Scan Mode is set to Broadband Online Frequency or
Broadband Offline Frequency, the value range of this parameter is
from 100 to 5000, and the default value is 200.
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.

Table 4-20 Results of FFT frequency scanning monitoring

Range

Subrack No. N/A 4 to 5, 60 to Number of the subrack where the N/A
254 board whose monitoring results are
RX Channel N/A 0 to 7 Index of the RX channel. An RX N/A
Index channel may have several carriers
NOTE
for 3900 series base stations, but
0 and 1 in only one carrier for BTS3202Es.
BTS3202Es
Spectrum N/A 0 to 2 Spectrum process types are as N/A

Process Type follows:
0: High-Resolution Online
Frequency
1: Broadband Online Frequency
2: Broadband Offline Frequency

eNodeB

Range
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 N/A
100 to 5000 frequency detection.
4.11 AAS
This task is used to maintain an eNodeB.

None.
4.11.3 Parameters
Table 4-21 Parameters for AAS
AARU Cabinet Number of the cabinet where the active antenna radio unit (AARU) is
No. located. The value ranges from 0 to 62.
AARU Subrack Number of the subrack where the AARU is located. The value ranges
No. 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 The Save File check box is selected by default, and monitoring

eNodeB

Table 4-22 Results for AAS

Range
AARU Cabinet N/A 0 to 62 Number of the cabinet where the N/A
No. AARU is located.
AARU Subrack N/A 60 to 254 Number of the subrack where the N/A
No. AARU is located.
AARU Slot No. N/A 0 to 3 Number of the slot where the AARU N/A
is located.
Antenna Port N/A 0 to 255 Number of the virtual antenna port N/A
No. used by the carrier for AAS query.
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 N/A
direction.
4.12 Frequency Scanning Intermodulation Interference

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

Services in cells served by the RRU or RFU are interrupted during the test.
4.12.3 Parameters
Table 4-23 Parameters for frequency scanning intermodulation interference detection monitoring
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.

eNodeB
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 Start frequency in frequency scanning intermodulation interference
Freq(0.1MHz) 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 Frequency step in frequency scanning intermodulation interference
Step(0.1MHz) detection. The value ranges from 1 to 100.

Table 4-24 Results of frequency scanning intermodulation interference detection monitoring

Cabinet No. N/A 0 to 62 Number of the cabinet N/A
Subrack No. N/A 4 to 5, 60 to 254 Number of the subrack N/A
Slot No. N/A 0 to 8 Number of the slot where N/A
the board whose monitoring
results are reported is
located.
TX Channel N/A 0 to 1 Number of the TX channel N/A
No. whose monitoring results
are reported.
Data Type N/A n = 3, 5, 7, 9, 11, IM order that is reported. N/A
13, 15
The value of n
indicates the IM
order.

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

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

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

Table 5-2 Results of local and forwarded traffic monitoring

Local Receive Byte/s 0 to 100000000 Number of bytes received N/A
Traffic by the eNodeB per second
within a monitoring period
and that are destined for the
local eNodeB.

eNodeB

Local Send Byte/s 0 to 100000000 Number of bytes transmitted N/A
Traffic by the eNodeB within a
monitoring period,
excluding the forwarded
traffic.
eNodeB Bypass Byte/s 0 to 100000000 Number of bytes forwarded N/A
Traffic by the eNodeB per second
5.2 IP Performance Monitoring

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

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

performance monitoring is located.
Subrack No. Number of the subrack where the board/eNodeB for IP
Slot No. Number of the slot where the board/eNodeB for IP
VRF Number of the virtual routing and forwarding instance for IP
performance monitoring.
Monitor Period (Seconds) Interval of reporting monitoring results. It is set to 1 by
default.

eNodeB

Table 5-4 Results of IP Performance monitoring

Range
Number Packets 0 to 2000000 Total number of packets at the IP N/A
increment of layer received by the
RX packets board/eNodeB within a
monitoring period.
Number Packets 0 to 2000000 Total number of packets at the IP N/A
increment of layer transmitted by the
TX packets board/eNodeB within a
monitoring period.
Number Packets 0 to 2000000 Total number of discarded N/A
increment of packets at the IP layer received by
discarded the board/eNodeB within a
packets monitoring period.
5.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.
5.3.3 Parameters
Table 5-5 Parameters for transport port flux stat monitoring
Protocol Type Type of the protocol for transport port flux stat monitoring. It can be set
to IP.
NOTE
LTE does not support ATM.

eNodeB
Cabinet No. Number of the cabinet where the board/eNodeB for transport port flux
stat monitoring is located.
Subrack No. Number of the subrack where the board/eNodeB for transport port flux
Slot No. Number of the slot where the board/eNodeB for transport port flux stat
Sub Board Type  Type of the subboard of a board or an eNodeB for transport port flux
stat monitoring. It can be set to the following values:
 BASE_BOARD
 BACK_BOARD
 ETH_COVERBOARD
 E1_COVERBOARD
 UNCHANNELLED_COVERBOARD
NOTE
The LTE supports BASE_BOARD, BACK_BOARD or E1_COVERBOARD.
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 of the physical port for transport port flux stat monitoring. It can
Type be set to PPP, MPGroup, EthPort, EthTrunk, or TUNNEL.
NOTE
It can be set to PPPoE or EthPort in BTS3202Es or BTS3203Es.
It can be set to EthPort or EthTrunk in 3900 Series Base Station.
Port No. Number of the physical port of a board or an eNodeB for transport port
flux stat monitoring.
Monitor Type It is valid only when Port Type is set to RSCGRP and can be set to
Flow Stat or Load Stat.
Rate Config It is valid only when Monitor Type is set to Load Stat and can be set
Mode to Single Rate or Dual Rate.
Resource Group Number of the resource group for transport port flux stat monitoring. It
No. is valid only when Port Type is set to RSCGRP.
Include Packet Specifies whether monitoring results contain the lost packets in the IP
Discard layer.
Information of
IP Layer

eNodeB
Include Packet Specifies whether monitoring results contain the lost packets in the data
Discard link layer.
Information of
LINK Layer
Extend Option Specifies whether monitoring results contain the lost packets in the IP
layer or data link layer.
This monitoring item is valid when Protocol Type and Port Type are
set to ATM and PHYSICAL_PORT, respectively.

Table 5-6 Results of transport port flux stat monitoring
RX Packet ‰ 0 to 1000 Packet loss rate during N/A

Discard Ratio reception in the IP layer
of IP Layer within a monitoring
period.
TX Packet ‰ 0 to 1000 Packet loss rate during N/A
Discard Ratio transmission in the IP
of IP Layer layer within a
monitoring period.
RX Packet ‰ 0 to 1000 Packet loss rate during N/A
Discard Ratio reception in the data
of Link Layer link layer within a
monitoring period.
TX Packet ‰ 0 to 1000 Packet loss rate during N/A
Discard Ratio transmission in the data
of Link Layer link layer within a
monitoring period.
RX Packet packet 0 to Packet loss rate during N/A
number of 4294967295 reception in the data
Link Level link layer within a
monitoring period.
TX Packet packet 0 to Number of packets N/A
number of 4294967295 transmitted in the data
Link Level link layer within a
monitoring period.
RX CRC Error packet 0 to Number of packets that N/A
Packet number 4294967295 fail the CRC during
of Link Level reception in the data
link layer within a
monitoring period.

eNodeB

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

eNodeB

Tx Logic Port % 0 to 100 Transmit load rate of Transmit load for
GBR Load GBR service data GBR service data
Ratio of transmission on the transmission on
SingleRate logical port in the logical port in
single-rate mode within single-rate mode x
a monitoring period. 100/Transmit rate
of a transmission
resource group in
an IP port
Rx Logic Port % 0 to 100 Receive load rate of Receive load for
Ratio of reception on the logical reception on the
SingleRate port in single-rate mode logical port in
within a monitoring single-rate mode x
period. 100/receive rate of
a transmission
resource group in
an IP port
Tx Logic Port Kbps 0 to Transmit load for data N/A
Load of 1000000000 transmission on the
SingleRate logical port in
Rx Logic Port Kbps 0 to Receive load for data N/A
Load of 1000000000 reception on the logical
SingleRate port in single-rate mode
within a monitoring
period.
Load Ratio of data transmission on data transmission
SingleRate the logical port in on the logical port
single-rate mode within in single-rate mode
a monitoring period. x 100/Admission
bandwidth for data
transmission on
the logical port in
single-rate mode
Load Ratio of data reception on the data reception on
SingleRate logical port in the logical port in
single-rate mode within single-rate mode x
a monitoring period. 100/Admission
bandwidth for data
reception on the
logical port in
single-rate mode

eNodeB

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

eNodeB

Tx Logic Port Kbps 0 to Transmit load for N/A
Non-Flow-Con 1000000000 non-flow-controllable
trol Service service data
Load of transmission on the
double-rate mode
within a monitoring
period.
Rx Logic Port Kbps 0 to Receive load for N/A
Non-Flow-Con 1000000000 non-flow-controllable
trol Service service data reception
Load of on the logical port in
DualRate double-rate mode
within a monitoring
period.
Rate of transmission on the transmission on
DualRate logical port in the logical port in
double-rate mode double-rate mode
within a monitoring x 100/PIR
period. admission
bandwidth for data
transmission on
the logical port in
double-rate mode
Rate of reception on the logical reception on the
DualRate port in double-rate logical port in
mode within a double-rate mode
monitoring period. x 100/PIR
admission
bandwidth for data
reception on the
logical port in
double-rate mode
Tx Logic Port % 0 to 100 CIR bandwidth load Transmit load for
CIR rate of GBR service non-flow-controlla
Bandwidth data transmission on ble service data
Load Rate of the logical port in transmission on
DualRate double-rate mode the logical port in
within a monitoring double-rate mode
period. x 100/CIR
admission
bandwidth for data
transmission on
the logical port in
double-rate mode

eNodeB

Rx Logic Port % 0 to 100 CIR bandwidth load Receive load for
CIR rate of GBR service non-flow-controlla
Bandwidth data reception on the ble service data
Load Rate of logical port in reception on the
DualRate double-rate mode logical port in
within a monitoring double-rate mode
period. x 100/CIR
admission
bandwidth for data
reception on the
logical port in
double-rate mode
Tx Logic Port Kbps 0 to Transmit load for data N/A
Load of 1000000000 transmission on the
double-rate mode
within a monitoring
period.
Rx Logic Port Kbps 0 to Receive load for data N/A
Load of 1000000000 reception on the logical
mode within a
monitoring period.
Tx Logic Port % 0 to 100 PIR bandwidth load Transmit load for
PIR rate of data data transmission
Bandwidth transmission on the on the logical port
Load Rate of logical port in in double-rate
DualRate double-rate mode mode x 100/PIR
within a monitoring admission
period. bandwidth for data
transmission on
the logical port in
double-rate mode
Rx Logic Port % 0 to 100 PIR bandwidth load Receive load for
PIR rate of data reception data reception on
Bandwidth on the logical port in the logical port in
Load Rate of double-rate mode double-rate mode
DualRate within a monitoring x 100/PIR
period. admission
bandwidth for data
reception on the
logical port in
double-rate mode
Tx Logic Port Kbps 0 to Transmit traffic for data N/A
Flow of 1000000000 transmission on the
double-rate mode
within a monitoring
period.

eNodeB
5.4 Transport Link Flux Stat Monitoring

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

None.
5.4.3 Parameters
Table 5-7 Parameters for transport link flux stat monitoring
Cabinet No. Number of the cabinet where the board/eNodeB for transport link flux
Subrack No. Number of the subrack where the board/eNodeB for transport link flux
Slot No. Number of the slot where the board/eNodeB for transport link flux stat
Protocol Type It can be set to ATM or IP in 3900 series base stations. It can be set
only to IP in BTS3202Es and BTS3203Es.
Sub Board Type Type of the subboard of a board or an eNodeB for transport port flux
stat monitoring. It can be set to BASE_BOARD,
UNCHANNELLED_COVERBOARD, E1_COVERBOARD, or
BACK_BOARD.
This parameter is valid in 3900 series base stations only when Protocol
Type is set to ATM.
Physical Port Physical port type of the board/eNodeB for transport port flux stat
Type monitoring. It can be set to IMAGRP, UNI, STM_1, or FRAATM.
Type is set to ATM.
Unit It can be set to cps or bps.
Type is set to ATM.
Port No. Port number of the board for transport port flux stat monitoring.
Type is set to ATM.
PVCx The value range for x is from 1 to 6.
Type is set to ATM.
VPI This parameter is valid in 3900 series base stations only when Protocol
Type is set to ATM.

eNodeB
VCI This parameter is valid in 3900 series base stations only when Protocol
Type is set to ATM.
Extend Option Specifies whether monitoring results include the IPPM statistic. It can
be set to Exclude IPPM Statistic or Include IPPM Statistic.
This parameter is valid only when Protocol Type is set to IP.
SCTP Specifies whether to monitor the SCTP link quality.
SCTP No. Number of the SCTP link.
IPPATH Specifies whether to monitor the quality of links on the user plane.
PATH ID Number of the IP path.
OMCH Specifies whether to detect the OM channel.
DSCP Differentiated services code point (DSCP) value of the OM channel
when the OMCH parameter is specified.
Local IP Local IP address of the OM channel when the OMCH parameter is
specified.
Remote IP Remote IP address of the OM channel when the OMCH parameter is
specified.
Select Trace Type of a link to be monitored. It can be set to OMCH, IPPATH, or
Type SCTP. This parameter is available only on the M2000.
NOTE

eNodeB

OMCH
Table 5-8 Results of OMCH monitoring

Test Type N/A 1: PVC Test result types, including N/A
2: OMCH PVC, OMCH, IPPath,
SCTP, and IPPM.
3: IPPath
4: SCTP BTS3202Es and BTS3203Es
34: IPPM do not support PVC.
RX Rate of OMCH pps, 0 to Receive rate of the OM N/A

bps 4294967295 channel within a monitoring
period.
RX Rate of OMCH pps, 0 to Transmit rate of the OM N/A
bps 4294967295 channel within a monitoring
period.
IP Path
Table 5-9 Results of IP Path monitoring

SCTP, and IPPM.
3: IPPath
Path Index N/A 1 to 3 Index of an IP path. N/A
Path ID N/A 0 to 65535 Number of an IP path. N/A

RX Rate of IPPATH pps, 0 to Receive rate of an IP path N/A
or 4294967295 within a monitoring period.
bps
TX Rate of IPPATH pps, 0 to Transmit rate of an IP path N/A
or 4294967295 within a monitoring period.
bps

eNodeB
SCTP
Table 5-10 Results of SCTP monitoring

SCTP, and IPPM.
3: IPPath
Index N/A 1 to 2 Index of an SCTP link N/A

SCTP Link No. N/A 0 to 65535 Number of an SCTP link N/A
RX Rate of SCTP pps, 0 to Receive rate of the SCTP N/A
bps 4294967295 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.
TX Rate of SCTP pps, 0 to Transmit rate of the SCTP N/A
bps 4294967295 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.
Receive Error pps 0 to Number of error packets N/A
Packets of SCTP 4294967295 received over the SCTP
link within a monitoring
period.
Retransmit Ratio of ‰ 0 to 1000 Retransmission rate of N/A
SCTP SCTP association data
RX Packet Discard pps 0 to Number of discarded N/A
Rate of SCTP 4294967295 incoming packets in the
SCTP link within a
monitoring period.

eNodeB
IPPM
Table 5-11 Results of IPPM monitoring

Test Type N/A 1: PVC Test result types, N/A
2: OMCH including PVC, OMCH,
IPPath, SCTP, and IPPM.
3: IPPath
4: SCTP BTS3202Es and
34: IPPM BTS3203Es do not support
PVC.
Index N/A 1 to 3 Index of the IPPM. N/A

Number N/A 0 to 65535 Number of an IPPM N/A
session.
Average RTT ms 0 to Average delay of the N/A
Delay(ms) 4294967295 IPPM within a monitoring
period.
TX Packet 0.000001 0 to 100000 Uplink average packet N/A
Discard Rate(‰) loss rate of the IPPM
within a monitoring
period.
TX Time ms -65536 to Uplink average jitter of N/A
Jitter(ms) 65535 the IPPM within a
monitoring period.
RX Packet 0.000001 0 to 100000 Downlink average packet N/A
Discard Rate(‰) loss rate of the IPPM
within a monitoring
period.
RX Time ms -65536 to Downlink average jitter of N/A
Jitter(ms) 65535 the IPPM within a
monitoring period.
TX Lost Packet Packet 0 to Number of discarded N/A
number 4294967295 packets in data
transmission of the IPPM
within a monitoring
period.
Tx Packet Num Packet 0 to Number of packets N/A
4294967295 transmitted over the IPPM
within a monitoring
period.

eNodeB
5.5 UDP Test Monitoring

This task is used to measure the link quality, including the round-trip delays, jitter, and packet
loss rate by injecting User Datagram Protocol (UDP) packets from the eNodeB to other NEs
and then transmitting the packets back to the eNodeB when the eNodeB is not serving any
UEs.

None.
5.5.3 Parameters
Table 5-12 Parameters for UDP test monitoring
Cabinet No. Number of the cabinet where the main control board/eNodeB for the
UDP test is located.
Subrack No. Number of the subrack where the main control board/eNodeB for the
Slot No. Number of the slot where the main control board/eNodeB for the
(Seconds)
VRF Number of the virtual routing and forwarding instance for UDP test
monitoring.
Source IP Address IP address of the eNodeB.
Source Port No. Number of UDP port on the eNodeB. The value ranges from 1024 to
65,535.
Destination IP IP address of the peer end.
Address
Destination Port Number of UDP port on the peer end. The value ranges from 1024 to
No 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 of the UDP packet. The value ranges from 72 to 1500. The
LENGTH default value is 1500.
(BYTES)

eNodeB
Time (Minutes) Duration of UDP test monitoring. The test stops automatically when
the duration expires. The value ranges from 1 to 60. The default value
is 15.

Table 5-13 Result of UDP test monitoring

Range
Drop Packet 0.001% 0 to 100000 Rate of lost packets to total Number of
Ratio packets on the discarded packets
transmission link within a per minute x
monitoring period. 100000/Expected
number of
packets received
on the
transmission link
per minute
Average Drop 0.001% 0 to 100000 Average rate of lost Total number of
Packet Ratio packets to total packets on discarded packets
the transmission link x 100000/Total
within a monitoring number of
period. packets
Delay Micros 0 to Delay on the transmission N/A
econd 4000000 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.
Jitter N/A N/A Jitter on the transmission |Delay - Average
link within a monitoring Delay|/Average
period. Delay
NOTE
The displayed value is equal
to the monitored value
multiplied by 1000.
Average Delay Micros 0 to Average delay on the N/A

econd 4000000 transmission link within a
monitoring period.

eNodeB
5.6 PPPoE Monitoring

This task is used to monitor PPPoE online performance. PPPoE online performance
monitoring helps monitor the link quality, which involves number of received packets,
number of transmitted packets, receive rate, transmit rate, number of discarded packets during
reception, number of discarded packets during transmission, packet loss rate during reception,
and packet loss rate during transmission. Packet drip ratio is a key indicator of the efficiency
of packet transmission.

None.
5.6.3 Parameters
Table 5-14 Parameters for PPPoE monitoring
Cabinet No. Number of the cabinet where the board/eNodeB for the PPPoE
performance tests is located.
Subrack No. Number of the subrack where the board/eNodeB for the PPPoE
Slot No. Number of the slot where the board/eNodeB for the PPPoE
PPPoELink No. Number of the PPPoE link to be tested.
(Seconds)

Table 5-15 Results of PPPoE monitoring

Receive Packet 0 to 2000000 Number of packets N/A
Packets received by the receiving
end of a PPPoE link
within a monitoring
period.
Send Packet 0 to 2000000 Number of packets N/A
Packets transmitted by the
transmitting end of a
PPPoE link within a
monitoring period.

eNodeB

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

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

None.

eNodeB
5.7.3 Parameters
Table 5-16 Parameters for IPSec performance monitoring
Cabinet No. Number of the cabinet where the board/eNodeB for IPSec performance
Subrack No. Number of the subrack where the board/eNodeB for IPSec performance
Slot No. Number of the slot where the board/eNodeB for IPSec performance
(Seconds)
NOTE

Table 5-17 Results of IPSec performance monitoring

IPSec Send pps 0 to Transmit rate on the N/A
Rate 4294967295 IPSec tunnel within a
monitoring period.
IPSec Receive pps 0 to Receive rate on the N/A
Rate 4294967295 IPSec tunnel within a
monitoring period.
IPSec Receive 0.0000 0 to 1000000 Packet loss rate for data N/A
DropRate 001 reception on the IPSec
tunnel within a
monitoring period.
5.8 Transport OAM Monitoring

This task is used to monitor packets transmitted and received over the ITU-T Y.1731-based
link and the link quality.

eNodeB

None.
5.8.3 Parameters
Table 5-18 Parameters for transport OAM monitoring
Test Type It can be set to:

 Y1731-LM
 Y1731-DM
Session ID Number of the session for transport OAM monitoring.

Table 5-19 Results of transport OAM monitoring

Total Frames Number 0 to Total number frame N/A
Transmitted in 4294967295 transmitted in the uplink
Uplink within a monitoring period.
Total Frames Number 0 to Absolute value of the total N/A
Lost in Uplink 4294967295 number of frames discarded
in the uplink 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.

eNodeB

Total Frames Number 0 to Total number of frames N/A
Transmitted in 4294967295 transmitted in the downlink
Downlink within a monitoring period.
Total Frames Number 0 to Absolute value of the total N/A
Lost in 4294967295 number of frames discarded
Downlink 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 ms 0 to Average delay on the N/A

Delay(ms) 4294967295 transport OAM within a
monitoring period.
Average ms -65536 to Average jitter on the N/A
Jitter(ms) 65535 transport OAM within a
monitoring period.
5.9 Transport Auto Setup User Plane Monitoring

This task is used to monitor packets transmitted and received over the transport auto setup
user plane and the link quality.

None.

eNodeB
5.9.3 Parameters
Table 5-20 Parameters for transport auto setup user plane monitoring
Cabinet No. Number of the cabinet where the board/eNodeB for transport auto setup
user plane monitoring is located.
Subrack No. Number of the subrack where the board/eNodeB for transport auto setup
Slot No. Number of the slot where the board/eNodeB for transport auto setup
VRF Index of the virtual routing and forwarding instance for transport auto
setup user plane monitoring.
IPPM Flag It can be set to Include or Not Include.
Source IP Source IP address of the link for transport auto setup user plane
address monitoring.
Destination IP This parameter is valid only when IPPM Flag is set to Include.
address
NOTE

Table 5-21 Results of transport auto setup user plane monitoring

Test Type N/A 0: Type of the link for transport N/A
UserPlaneLink auto setup user plane
1: monitoring.
UserPlaneLink
+IPPM
Index N/A 0 to 2 Index of the link for transport N/A
auto setup user plane
monitoring.

eNodeB

VRF Index N/A 0 to 7 Index of the virtual routing N/A
0 in and forwarding instance for
BTS3202Es transport auto setup user plane
and monitoring.
BTS3203Es
Source IP N/A Valid IP Source IP address of the link N/A
address for transport auto setup user
plane monitoring.
Destination IP N/A Valid IP Destination IP address of the N/A
address link for transport auto setup
user plane monitoring.
Receive pps 0 to Receive rate of a user plane N/A
Rate(pps) 4294967295 link in the IP layer within a
monitoring period.
Transmit pps 0 to Transmit rate of a user plane N/A
Rate(pps) 4294967295 link in the IP layer within a
monitoring period.
Receive bps 0 to Receive rate of a user plane N/A
Rate(bps) 4294967295 link in the IP layer within a
monitoring period.
Transmit bps 0 to Transmit rate of a user plane N/A
Rate(bps) 4294967295 link in the IP layer within a
monitoring period.
Average RTT ms 0 to Average delay of a user plane N/A
Delay(ms) 4294967295 link in the IP layer within a
monitoring period.
Transmit 0.01‰ 0 to 1000 Average packet loss rate of a N/A
Packet Discard user plane link in the IP layer
Rate within a monitoring period.
Transmit Time ms -65536 to Average jitter for data N/A
Jitter(ms) 65535 transmission of a user plane
link in the IP layer within a
monitoring period.
Receive Packet 0.01‰ 0 to 1000 Average packet loss rate for N/A
Discard Rate data reception of a user plane
link in the IP layer within a
monitoring period.
Receive Time ms -65536 to Average jitter for data N/A
Jitter(ms) 65535 reception of a user plane link
in the IP layer within a
monitoring period.

eNodeB

Transmit lost packet 0 to Number of discarded packets N/A
packet 4294967295 for data transmission of a user
plane link in the IP layer
Transmit packet 0 to Number of transmitted packets N/A
packet 4294967295 of a user plane link in the IP
layer within a monitoring
period.

eNodeB
Performance Monitoring Reference 6 RRU/RFU Performance Monitoring
6 RRU/RFU Performance Monitoring
6.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.
6.1.3 Parameters
Table 6-1 Parameters for sector performance monitoring
Test Items It can be set only to UL Widefreq Scan.
200, 500, 1000, or 2000.
Sector Device ID ID of the sector for performance monitoring. It is set to a value in
the range of 0 to 65535. It is set to 0 by default.
Frequency Band Frequency band supported by the sector. It is set to a value in the
range of 1 to 40.
UL EARFCN Uplink EARFCN of a cell. It is set to a value in the ranges of
18000 to 45589 and 54436 to 65535.
UL Bandwidth Uplink bandwidth of the cell. It can be set to 1.4M, 3M, 5M,
10M, 15M, or 20M.
BTS3202Es and BTS3203Es do not support the cell bandwidth of
1.4 MHz or 3 MHz.

eNodeB
Performance Monitoring Reference 6 RRU/RFU Performance Monitoring

Table 6-2 Results of UL Widefreq Scan monitoring

Range
Local Sector ID N/A 0 to 65535 ID of the monitored sector. N/A
Monitor Period ms [50, 100, Interval of reporting monitoring N/A
200, 500, results.
1000, 2000]
Frequency kHz 0 to Frequency of the monitored RB N/A

2620000 for sector performance
monitoring.
Signal Strength dBm –140 to –50 RSSI in each RB from the N/A
physical layer when monitoring


eNodeB Performance Monitoring Reference (08) (PDF) - EN PDF

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 (08) (PDF) - EN PDF

Uploaded by

Copyright:

Available Formats

eNodeB

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 08 (2014-02-28) Huawei Proprietary and Confidential i

About This Document

Product Name Product Version

Issue 08 (2014-02-28) Huawei Proprietary and Confidential ii

Site maintenance engineers

Topic Change Description

No information in Issue 07 (2014-01-27) is deleted from this issue.

Issue 08 (2014-02-28) Huawei Proprietary and Confidential iii

Topic Change Description

3.7.4 Monitoring Results  Updatad the descriptions of "Value

3.11.4 Monitoring Results Updatad the descriptions of "Value Range"

3.13.4 Monitoring Results

3.14.4 Monitoring Results

3.16.3 Parameters Updated the description of Test Items.

5.3.3 Parameters Updatad the Table 5-5Parameters for

Issue 08 (2014-02-28) Huawei Proprietary and Confidential iv

Topic Change Description

Topic Change Description

1.3 Precautions Add the descriptions of the Note.

3.7.4 Monitoring Results Updated the "Result of RLC data stream

Topic Change Description

No information in Issue 04 (2013-07-22) is deleted from this issue.

Issue 08 (2014-02-28) Huawei Proprietary and Confidential v

Topic Change Description

Topic Change Description

3 User Performance Monitoring Modified the value range of Physical Cell

No information in Issue 03 (2013-06-27) is deleted from this issue.

Topic Change Description

No information in Issue 02 (2013-05-30) is deleted from this issue.

Issue 08 (2014-02-28) Huawei Proprietary and Confidential vi

Topic Change Description

No information in Issue 01 (2013-04-28) is deleted from this issue.

Topic Change Description

The following information in draft C (2013-04-10) is deleted from this issue:

Issue 08 (2014-02-28) Huawei Proprietary and Confidential vii

Topic Change Description

No information in draft B (2013-02-25) is deleted from this issue.

Topic Change Description

No information in issue draft A (2013-02-08) is deleted from this issue.

Topic Change Description

Issue 08 (2014-02-28) Huawei Proprietary and Confidential viii

Topic Change Description

Topic Change Description

The following information in issue 02 (2012-11-30) of V100R005C01 is deleted from this

Issue 08 (2014-02-28) Huawei Proprietary and Confidential ix

About This Document .................................................................................................................... ii

2 Cell Performance Monitoring ..................................................................................................... 6

Issue 08 (2014-02-28) Huawei Proprietary and Confidential x

2.5.3 Parameters ............................................................................................................................................. 15

Issue 08 (2014-02-28) Huawei Proprietary and Confidential xi

2.14 HARQ Statistic Monitoring.......................................................................................................................... 35

3 User Performance Monitoring .................................................................................................. 59

Issue 08 (2014-02-28) Huawei Proprietary and Confidential xii

3.5 Power Headroom Monitoring ......................................................................................................................... 67

Issue 08 (2014-02-28) Huawei Proprietary and Confidential xiii

3.12.2 Service Impact .................................................................................................................................... 83

4 Device Monitoring ...................................................................................................................... 94

Issue 08 (2014-02-28) Huawei Proprietary and Confidential xiv

4.4.2 Service Impact ...................................................................................................................................... 98