enodeb performance monitoring reference(v100r004c00_01)(pdf)-en

8/13/2019 eNodeB Performance Monitoring Reference(V100R004C00_01)(PDF)-En

1/74

eNodeBV100R004C00

Performance MonitoringReference

Issue 01

Date 2011-09-15

HUAWEI TECHNOLOGIES CO., LTD.


2/74

Issue 01 (2011-09-15) Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd

i

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

No part of this document may be reproduced or transmitted in any form or by any means without prior

written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective

holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and

the customer. All or part of the products, services and features described in this document may not be

within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,

information, and recommendations in this document are provided "AS IS" without warranties, guarantees orrepresentations 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: [email protected]
http://www.huawei.com/http://www.huawei.com/mailto:[email protected]:[email protected]:[email protected]://www.huawei.com/


3/74

eNodeB

Performance Monitoring Reference Contents



ii

Contents

1 Introduction ......................................................................................................................................... 12 Sector Performance Monitoring ..................................................................................................... 3

2.1 Parameters for Sector Performance Monitoring ............................................................. .................................. 32.2 Results of Sector Performance Monitoring ................................. ............................................................... ...... 4

3 RRU/RFU Performance Monitoring.............................................................................................. 53.1 Parameters for RRU/RFU Performance Monitoring ........................................................................................ 53.2 Results of RRU/RFU Performance Monitoring ............................... ............................................................. ... 6

4 Spectrum Detection ........................................................................................................................... 74.1 Parameters for Spectrum Detection ........................................................... ....................................................... 74.2 Results of Spectrum Detection ....................................................... ............................................................ ...... 8

5 QoS Satisfaction Rate Monitoring ................................................................................................ 95.1 Parameters for QoS Satisfaction Rate Monitoring ................................................................ ........................... 95.2 Results of QoS Satisfaction Rate Monitoring................................................................ ................................. 10

6 General Throughput Monitoring ................................................................................................ 116.1 Parameters for General Throughput Monitoring .................................................................... ........................ 116.2 Results of General Throughput Monitoring ............................................ ....................................................... 11

7 Service Statistics Monitoring ........................................................................................................ 137.1 Parameters for Service Statistics Monitoring ................................................................................................. 137.2 Results of Service Statistics Monitoring ........................................................................................... ............. 13

8 User Statistics Monitoring ............................................................................................................. 148.1 Parameters for User Statistics Monitoring.................................................................. .................................... 148.2 Results of User Statistics Monitoring ........................................................ ..................................................... 14

9 RB Usage Monitoring ..................................................................................................................... 169.1 Parameters for RB Usage Monitoring ................................................................................................ ............ 169.2 Results of RB Usage Monitoring .............................................................. ..................................................... 16

10 ICIC Monitoring ............................................................................................................................ 1810.1 Parameters for ICIC Monitoring ............................................................. ..................................................... 1810.2 Results of ICIC Monitoring ............................................................ ............................................................. . 18

11 MU-MIMO Monitoring ............................................................................................................... 21


4/74

eNodeB




iii

11.1 Parameters for MU-MIMO Monitoring.............................. ............................................................. ............. 2111.2 Results of MU-MIMO Monitoring .......................................................... ..................................................... 21

12 Interference Detection Monitoring ........................................................................................... 2212.1 Parameters for Interference Detection Monitoring ................................................................ ....................... 2212.2 Results of Interference Detection Monitoring .............................................................. ................................ 22

13 Scheduled Cell-Level UE Information Monitoring .............................................................. 2413.1 Parameters for Scheduled Cell-Level UE Information Monitoring............................................................. . 2413.2 Results of Scheduled Cell-Level UE Information Monitoring ........................................................ ............. 24

14 HARQ Status Monitoring ............................................................................................................ 2614.1 Parameters for HARQ Status Monitoring ................................................................ .................................... 2614.2 Results of HARQ Status Monitoring ....................................................... ..................................................... 26

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

15.1 Parameters for Air-Interface DCI Status Monitoring ....... ............................................................. ............... 2815.2 Results of Air-Interface DCI Status Monitoring ........................................................... ................................ 29

16 Air-Interface DRB Statistics Monitoring ................................................................................. 3116.1 Parameters for Air-Interface DRB Statistics Monitoring................................................................ .............. 3116.2 Results of Air-Interface DRB Statistics Monitoring .............................................................. ....................... 31

17 BLER Monitoring ........................................................................................................................... 3317.1 Parameters for BLER Monitoring ............................................................................................................ .... 3317.2 Results of BLER Monitoring ....................................................... ............................................................ .... 33

18 Power Headroom Monitoring .................................................................................................... 3618.1 Parameters for Power Headroom Monitoring ......... ............................................................. ........................ 3618.2 Result of Power Headroom Monitoring ........................................................... ............................................ 36

19 Channel Quality Monitoring ...................................................................................................... 3719.1 Parameters for Channel Quality Monitoring ........................................................................ ........................ 3719.2 Results of Channel Quality Monitoring ................................................................................................. ...... 37

20 Scheduling Monitoring ................................................................................................................ 3920.1 Parameters for Scheduling Monitoring ..................................... ............................................................. ...... 3920.2 Results of Scheduling Monitoring ........................................................... ..................................................... 39

21 RLC Data Stream Monitoring..................................................................................................... 4221.1 Parameters for RLC Data Stream Monitoring .............................................................. ................................ 4221.2 Result of RLC Data Stream Monitoring ........................................................... ............................................ 42

22 Throughput Monitoring............................................................................................................... 4322.1 Parameters for Throughput Monitoring ............................................................ ............................................ 4322.2 Results of Throughput Monitoring .......................................................... ..................................................... 43

23 AQM Monitoring ........................................................................................................................... 4523.1 Parameters for AQM Monitoring ............................................................................... .................................. 45


5/74

eNodeB




iv

23.2 Results of AQM Monitoring................................................................ ......................................................... 4524 Uplink Power Control Monitoring ........................................................................................... 47

24.1 Parameters for Uplink Power Control Monitoring ....................................................................................... 4724.2 Results of Uplink Power Control Monitoring ................................................................................. ............. 47

25 Downlink Power Control Monitoring ..................................................................................... 5025.1 Parameters for Downlink Power Control Monitoring .................................................................................. 5025.2 Results of Downlink Power Control Monitoring ................................................................ ......................... 50

26 Uplink ICIC Monitoring .............................................................................................................. 5326.1 Parameters for Uplink ICIC Monitoring ............................................... ....................................................... 5326.2 Results of Uplink ICIC Monitoring ......................................................... ..................................................... 53

27 MCS Statistics Monitoring .......................................................................................................... 5527.1 Parameters for MCS Statistics Monitoring ....................................................... ............................................ 55

27.2 Results of MCS Statistics Monitoring ................................................................ .......................................... 55

28 IP Performance Monitoring ........................................................................................................ 5728.1 Parameters for IP Performance Monitoring ...................................................... ............................................ 5728.2 Results of IP Performance Monitoring ............................................................................................ ............. 57

29 IP Path Performance Monitoring ............................................................................................... 5929.1 Parameters for IP Path Performance Monitoring .......................................................... ................................ 5929.2 Results of IP Path Performance Monitoring ................................................................................................. 59

30 SCTP Performance Monitoring .................................................................................................. 61

30.1 Parameters for SCTP Performance Monitoring ............................................................ ................................ 6130.2 Results of SCTP Performance Monitoring ....................................................... ............................................ 61

31 Local and Forwarded Traffic Monitoring ................................................................................ 6331.1 Parameters for Local and Forwarded Traffic Monitoring ...................................................... ....................... 6331.2 Results of Local and Forwarded Traffic Monitoring ............................................................. ....................... 63

32 TRM Statistic Monitoring ........................................................................................................... 6532.1 Parameters for TRM Statistic Monitoring ........................................................ ............................................ 6532.2 Results of TRM Statistic Monitoring ....................................................................................................... .... 66

33 UDP Injection Test Monitoring ................................................................................................. 6833.1 Parameters for UDP Injection Test Monitoring ............................................................ ................................ 6833.2 Result of UDP Injection Test Monitoring ......................................................... ............................................ 69


6/74

eNodeB

Performance Monitoring Reference 1 Introduction



1

1 IntroductionPurpose

This document describes eNodeB performance monitoring results and explains monitoring

items in terms of the meanings, value ranges, and calculation methods.

Product Versions

The following table lists the product versions related to this document.

Product Name Product Version

DBS3900 LTE V100R004C00

DBS3900 LTE TDD V100R004C00

BTS3900 LTE V100R004C00

BTS3900A LTE V100R004C00

BTS3900L LTE V100R004C00

Intended Audience

This document is intended for:

Technical support engineers Maintenance engineers

Change History

This document is revised based on review comments. The latest document contains allupdates.

Document Issues

The document issues are as follows:

01 (2011-09-15)


7/74

eNodeB

Performance Monitoring Reference 1 Introduction



2

Draft A (2011-07-15)

01 (2011-09-15)

This is the first commercial issue.

Compared with issue Draft A (2011-07-15) of V100R004C00, this issue adds the following

topics:

Topic Change Description

3 RRU/RFU Performance Monitoring Added the parameters for RRU/RFUperformance monitoring.

Added the results of RRU/RFU

performance monitoring.

Compared with issue Draft A (2011-07-15) of V100R004C00, this issue incorporates the

changes described in the following table:

Topic Change Description

5 QoS Satisfaction Rate Monitoring Added the parameters for operator QoS

satisfaction rate monitoring.

Added the results of operator QoSsatisfaction rate monitoring.

Compared with issue Draft A (2011-07-15) of V100R004C00, this issue does not remove anyinformation.

Draft A (2011-07-15)

This is the draft.


8/74

eNodeB

Performance Monitoring Reference 2 Sector Performance Monitoring



3

2 Sector Performance MonitoringRadio networks work in open environments and therefore are inevitably affected byinterference. Interference detection and location are required in network deployment and

long-term network operation. The base station is a receiver system and supports scalablebands. Therefore, it can be used for simple collection of uplink interference information,

reducing manual workloads (for example, carrying instruments) during network deploymentand interference detection. Uplink frequency scanning helps to check the electromagnetic

environment around the eNodeB and detect internal interference in the eNodeB. The RRU orRFU calculates the received signal strength and reports the strength to the LMT after scanning

frequencies continuously. The received signal strength is used as reference for interferencelocation and analysis.

2.1 Parameters for Sector Performance Monitoring

Table 2-1Parameters for sector performance monitoring

Parameter Description

Monitor Item It can be set to UL Widefreq Scan.

Monitor Period

(ms)

Period for reporting monitoring results. It can be set to 50, 100, 200,

500, 1000, or 2000.

Local Sector ID ID of the sector for performance monitoring.

Frequency Band Frequency band supported by the sector. It is set to a value in the range

of 1to 40.

UL EARFCN Uplink EARFCN of a cell. It is set to a value in the ranges of 18000to41589and 65236to 65535.

UL Bandwidth Uplink bandwidth of the cell. It can be set to 1.4M, 3M, 5M, 10M,

15M, or 20M.

Autosave to File After you select the Autosave to Filecheck box, monitoring results

are automatically saved in the default path. You can also specify the

file name, file format, and another save path.


9/74

eNodeB

Performance Monitoring Reference 2 Sector Performance Monitoring



4

2.2 Results of Sector Performance Monitoring

NOTE In the figure of monitoring result description, the horizontal axis indicates frequency, center frequency

for each RB at the air interface, which is in units of kHz. The vertical axis indicates the received signalstrength, frequency spectrum, which is in units of dBm.

Table 2-2Results of sector performance monitoring

Monitor Item Parameter Unit Value Range Description

UL WidefreqScan

Signal Strength dBm -140 to -50 Received signalstrength indicator

(RSSI) of each RBfrom the physical layer

when the monitoringresult is reported.


10/74

eNodeB

Performance Monitoring Reference 3 RRU/RFU Performance Monitoring



5

3 RRU/RFU Performance MonitoringThis task is used to monitor the performance of the remote radio unit (RRU) or radiofrequency unit (RFU) power, temperature, and distance to fault (DTF).

3.1 Parameters for RRU/RFU Performance Monitoring

Table 3-1Parameters for RRU/RFU performance monitoring


Monitor Item It can be set to RRU/RFU Output Power, RRU/RFU

Temperature, or Distance To Fault(DTF).

Cabinet No. Number of the cabinet where the board for RRU/RFU performancemonitoring is located.

Subrack No. Number of the subrack where the board for RRU/RFU performancemonitoring is located.

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

monitoring is located.

Monitor Period

(ms)

Period for reporting monitoring results.

TX Channel No. Number of the TX channel located on the board for RRU/RFU

performance monitoring.

Autosave to File After you select the Autosave to Filecheck box, monitoring results

are automatically saved in the default directory. You can customizethe folder and file name.


11/74

eNodeB

Performance Monitoring Reference 3 RRU/RFU Performance Monitoring



6

3.2 Results of RRU/RFU Performance Monitoring

Table 3-2Results of RRU/RFU performance monitoring

MonitorItem

Parameter Unit ValueRange

Description

RRU/RFU

Output

Power

Output Power dBm -200 to -1 Output power of a carrier.

Output Power of TX

Carrier

dBm -200 to -1 Output power of a TX

channel.

RRU/RFUTemperature

Board TemperatureC -100 to 200 Board temperature.

LPA TemperatureC -100 to 200 Power amplifier

temperature.

Distance ToFault(DTF)

VSWR Position(M) m 0 to (232

-1) Distance between theantenna port and the

voltage standing wave ratio

(VSWR) point.

VSWR(0.1) N/A 0 to (216

-1) VSWR value.


12/74

eNodeB

Performance Monitoring Reference 4 Spectrum Detection



7

4 Spectrum DetectionThis task is used to detect the spectrum status, monitoring the interference in frequency andtime domains in radio environments by analyzing spectrum and power distribution of sampled

data.

4.1 Parameters for Spectrum Detection

Table 4-1Parameters for spectrum detection


Scan Mode Detects the output power of each TX channel and carrier. It can be set

to Carrier Mode, Channel Current Band Mode, or Channel Full

Band Mode.

Cabinet No. Number of the cabinet where the board for spectrum detection is

located.

Subrack No. Number of the subrack where the board for spectrum detection islocated.

Slot No. Number of the slot where the board for spectrum detection is located.

RBW Time frequency of Fast Fourier Transport (FFT) frequency detection,

in units of kHz.

NOTE

As stipulated by protocols, the minimum accuracy is 100 kHz. You are advised to

set this parameter to 100 kHz, which is the default value.

Monitor Period

(ms)

Period for reporting monitoring results. It can be set to 1000, 2000, or

3000.

Autosave to File The Autosave to Filecheck box is selected by default, and monitoring

results are automatically saved in the default path. You can also

customize another save path and file name.


13/74

eNodeB

Performance Monitoring Reference 4 Spectrum Detection



8

4.2 Results of Spectrum Detection

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


14/74

eNodeB

Performance Monitoring Reference 5 QoS Satisfaction Rate Monitoring



9

5 QoS Satisfaction Rate MonitoringQoS satisfaction rates of services with different QoS class identifiers (QCIs) are importantindicators of evaluating radio network performance. This task is used to check the QoS

satisfaction rates of services to evaluate service performance.

5.1 Parameters for QoS Satisfaction Rate Monitoring

Table 5-1Parameters for QoS satisfaction rate monitoring


Monitor Item It can be set to GBR Degrade Flag, UL QCI1 Satisfaction rate of

Service, UL QCI2 Satisfaction rate of Service, UL QCI3

Satisfaction rate of Service, UL QCI4 Satisfaction rate ofService, DL QCI1 Satisfaction rate of Service, DL QCI2

Satisfaction rate of Service, DL QCI3 Satisfaction rate ofService, DL QCI4 Satisfaction rate of Service, CN Operator

GBR Degrade Flag, CN Operator UL QCI1 Satisfaction rate ofService, CN Operator UL QCI2 Satisfaction rate of Service , CN

Operator UL QCI3 Satisfaction rate of Service, CN Operator ULQCI4 Satisfaction rate of Service, CN Operator DL QCI1

Satisfaction rate of Service, CN Operator DL QCI2 Satisfaction

rate of Service, CN Operator DL QCI3 Satisfaction rate ofService, CN Operator DL QCI4 Satisfaction rate of Service , or a

combination of these items.

Local Cell ID ID of the cell on which QoS satisfaction rate monitoring is

performed.

CN Operator ID ID of the operator on which QoS satisfaction rate monitoring isperformed.

Monitor Period

(ms)


500, 1000, or 2000.


15/74

eNodeB

Performance Monitoring Reference 5 QoS Satisfaction Rate Monitoring



10

5.2 Results of QoS Satisfaction Rate Monitoring

Table 5-2Results of QoS satisfaction rate monitoring


GBR Degrade

Flag

GBR

DegradeFlag

% 0 to 100 GBR service degradation flag.

Value 0indicates the service isnot degraded. Value 100

indicates the service isdegraded.

UL QCI

Satisfactionrate of Service

UL QCI

Satisfactionrate of

Service

% 0 to 100 Average uplink QoS

satisfaction rates of differentservices in a cell when the

monitoring result is reported.QoS satisfaction rate is used to

check QoS can be guaranteed.

DL QCISatisfaction

rate of Service

DL QCISatisfaction

rate ofService

% 0 to 100 Average downlink QoSsatisfaction rates of different

services in a cell when themonitoring result is reported.

QoS satisfaction rate is used to


CN Operator

GBR DegradeFlag

CN

OperatorGBR

Degrade

Flag

% 0 to 100 GBR service degradation flag.

Value 0indicates the service isnot degraded. Value 100

indicates the service is

degraded.

CN Operator

UL QCISatisfaction

rate of Service

CN

OperatorUL QCI

Satisfaction

rate ofService

% 0 to 100 Average uplink QoS

satisfaction rates of differentservices in a operator when the

monitoring result is reported.

QoS satisfaction rate is used tocheck QoS can be guaranteed.

CN OperatorDL QCI

Satisfaction

rate of Service

CNOperator

DL QCI

Satisfactionrate of

Service

% 0 to 100 Average downlink QoSsatisfaction rates of different

services in a operator when the

monitoring result is reported.QoS satisfaction rate is used to



16/74

eNodeB

Performance Monitoring Reference 6 General Throughput Monitoring



11

6 General Throughput MonitoringThis task is used to monitor the general throughput of guaranteed bit rate (GBR) services andnon-GBR services to check the air interface quality and scheduling algorithms.

6.1 Parameters for General Throughput Monitoring

Table 6-1Parameters for throughput monitoring


Monitor Item It can be set to RLC thruput of GBR service, RLC thruput, RLC

thruput of NON-GBR service, or a combination of these items.

Local Cell ID ID of the cell on which throughput monitoring is performed.

Monitor Period (ms) Period for reporting monitoring results. It can be set to 50, 100,

200, 500, 1000, or 2000.

6.2 Results of General Throughput Monitoring

Table 6-2Results of throughput monitoring


RLC thruput ofGBR service

Cell GBR TrafficUplink RLC

Throughput (bps)

bps 0 to300,000,000

Uplink throughput forservice data units

(SDUs) of all GBRservices received at the

radio link control(RLC) RLC layer

within a monitoringperiod.


17/74

eNodeB

Performance Monitoring Reference 6 General Throughput Monitoring



12


Cell GBR TrafficDownlink RLC

Throughput (bps)

bps 0 to300,000,000

Downlink throughputfor SDUs of all GBR

services transmitted by

the RLC layer within amonitoring period.

RLC thruput Cell Uplink RLCThroughput (bps)

bps 0 to300,000,000

Uplink throughput forSDUs of all service

DRBs received at the

RLC layer within amonitoring period.

Cell GBR TrafficDownlink RLC

Throughput (bps)

bps 0 to300,000,000

Downlink throughputfor SDUs of all service

DRBs transmitted by

the RLC layer within amonitoring period.

RLC thruput ofNON-GBR

service

Cell Non-GBRTraffic Uplink

RLC Throughput

(bps)

bps 0 to300,000,000

Uplink throughput forSDUs of all non-GBR

services received at the

RLC layer within amonitoring period.

Cell Non-GBRTraffic Downlink

RLC Throughput

(bps)

bps 0 to300,000,000

Downlink throughputfor SDUs of all

non-GBR services

transmitted by the RLC

layer within amonitoring period.


18/74

eNodeB

Performance Monitoring Reference 7 Service Statistics Monitoring



13

7 Service Statistics MonitoringThis task is used to monitor the number of services in a cell to view the distribution ofservices with different QCIs.

7.1 Parameters for Service Statistics Monitoring

Table 7-1Parameters for service statistics monitoring


Monitor Item It can be set to Service Number of QCI1, Service Number of

QCI2, Service Number of QCI3, Service Number of QCI3 ,Service Number of QCI4, Service Number of QCI5, Service

Number of QCI6 , Service Number of QCI7, Service Number ofQCI8, or Service Number of QCI9.

Local Cell ID ID of the cell for service number monitoring.

Monitor Period (ms) Period for reporting monitoring results. It can be set to 50, 100,200, 500, 1000, or 2000.

7.2 Results of Service Statistics MonitoringTable 7-2Results of service statistics monitoring

Monitor Item Parameter Unit ValueRange

Description

Service Number

of QCI

Service Number of

QCI

Integer 0 to 4000 Total number of services

with different QCIs

when the monitoringresult is reported.


19/74

eNodeB

Performance Monitoring Reference 8 User Statistics Monitoring



14

8 User Statistics MonitoringThis task is used to monitor the number of users in different scenarios to view the distributionof users in a cell.

8.1 Parameters for User Statistics Monitoring

Table 8-1Parameters for user statistics monitoring


Monitor Item It can be set to Keep UL Synch Users Number, General Users

Number, NO-Activated Users Number, or a combination of theseitems.

Local Cell ID ID of the cell for user number monitoring.

Monitor Period(ms)

Period for reporting monitoring results. It can be set to 50, 100, 200,500, 1000, or 2000.

8.2 Results of User Statistics Monitoring

Table 8-2Results of user statistics monitoring


Description

Keep UL Synch

Users Number

Keep UL Synch

Users Number

Integer 0 to 2,000 Number of users with

uplink synchronizationwhen the monitoring

result is reported,

which is the number ofactive users.


20/74

eNodeB

Performance Monitoring Reference 8 User Statistics Monitoring



15


Description

General Users

Number

General Users

Number

Integer 0 to 2,000 Number of connected

users when themonitoring result is

reported, including thenumber of active users

and non-active users.

NO-ActivatedUsers Number

NO-Activated UsersNumber

Integer 0 to 2,000 Number of non-activeusers when the

monitoring result isreported, which is the

number of users withuplink

out-of-synchronization.


21/74

eNodeB

Performance Monitoring Reference 9 RB Usage Monitoring



16

9 RB Usage MonitoringThis task is used to monitor the usage of cell-level resource blocks (RBs) in differentscheduling modes. RB is the minimum unit of time-frequency resource allocation.

9.1 Parameters for RB Usage Monitoring

Table 9-1Parameters for RB usage monitoring


Local Cell ID ID of the cell for RB usage monitoring.


200, 500, 1000, or 2000.

9.2 Results of RB Usage Monitoring

Table 9-2Results of RB usage monitoring

MonitorItem


Description

Usage of

RB

Downlink

Equivalent Used

RB Num

Integer 0 to

200,000

Number of downlink RBs used

within a monitoring period.

Uplink

Equivalent UsedRB Num

Integer 0 to

200,000

Number of uplink RBs used


Downlink Freq

Diversity UsedRB Num

Integer 0 to

200,000

Number of RBs scheduled for

downlink diversity within amonitoring period.


22/74

eNodeB

Performance Monitoring Reference 9 RB Usage Monitoring



17

MonitorItem


Description

Downlink Freq

Select Used RBNum

Integer 0 to

200,000


downlink frequency selectionwithin a monitoring period.

Downlink Harq

RB Used RBNum

Integer 0 to

200,000


downlink HARQ retransmissionwithin a monitoring period.

Uplink Pucch RBNum

Integer 0 to200,000

Number of RBs used by theuplink PUCCH when the



23/74

eNodeB

Performance Monitoring Reference 10 ICIC Monitoring



18

10 ICIC MonitoringThis task is used to check the status of inter-cell interference coordination (ICIC) bymonitoring the data associated to ICIC.

10.1 Parameters for ICIC Monitoring

Table 10-1Parameters for ICIC monitoring


Monitor Item It can be set to HII Information, OI Information, Proportion of

High Interference RB in System Bandwidth, Edge User RBInformation, Neighbor Cell List Information, or a combination of

these items.

Local Cell ID ID of the cell for ICIC monitoring.

Monitor Period

(ms)


500, 1000, or 2000.

10.2 Results of ICIC Monitoring

Table 10-2Results of ICIC monitoring

MonitorItem


Description

HIIInformation

Hii SentInformati

GlobalCell Id

N/A N/A Physical cell identifier (PCI)of the serving cell.


24/74

eNodeB




19

MonitorItem


Description

on Valid

RBNumber

in oneHii

Integer 0 to 110 Number of valid RBs in one

HII when the monitoring resultis reported, which is the same

as the number of RBsoccupied by the current cell

bandwidth.

Hii BitInforma

tionStream

in OneHii

N/A N/A HII information about theserving cell. For details, see

3GPP TS 36.421.

Valid HiiReceivedNum

ValidHiiReceive

dNumber

Integer 0 to 4 Number of valid HIIs receivedfrom neighboring cells by theserving cell when the


Hii

ReceivedInformati

on

Global

Cell Id

N/A N/A PCI of a neighboring cell that

transmits HII information tothe serving cell.

Valid

RBNum in

One Hii


HII when the monitoring resultis reported.

HII

Informa

tion

N/A N/A HII information about a

neighboring cell that transmits

the information to the servingcell. For details, see 3GPP TS

36.421.

OI

Information

OI Sent

Informati

on

Global

Cell Id

N/A N/A PCI of the serving cell.

ValidRB

Num inOne OI

Integer 0 to 110 Number of valid RBs in oneOI when the monitoring result

is reported, which is the sameas the number of RBsoccupied by the current cell

bandwidth.

OI

Informa

tion

N/A N/A OI information about the

serving cell, including high,

medium, and low interferencelevels. For details, see 3GPP

TS 36.421.


25/74

eNodeB




20

MonitorItem


Description

Valid OI

ReceivedNum

Valid

OIReceive

d Num

Integer 0 to 4 Number of valid OIs received

from neighboring cells by theserving cell when the


OI

Received

Information

Global

Cell Id

N/A N/A PCI of a neighboring cell that

transmits OI information to the

serving cell.

Valid

RB

Num inOne OI


OI when the monitoring result

is reported, which is the sameas the number of RBs

occupied by the current

bandwidth.OI

Information

N/A N/A OI information about a

neighboring cell that transmitsthe information to the serving

cell, including high, medium,and low interference levels.

For details, see 3GPP TS36.421.

Proportion

of HighInterference

RB inSystem

Bandwidth

Proportion of High

Interference RB inSystem Bandwidth

% 0 to 100 Proportion of

high-interference RBs in theserving cell to RBs occupied

by the current cell bandwidthwhen the monitoring result is

reported.

Edge userRB

Information

Global Cell Id N/A N/A PCI of the local cell.

EdgeUser Valid RB

Num

Integer 0 to 110 Number of valid RBs in the

available band for cell edge

users (CEUs) when themonitoring result is reported.

EdgeUser BitInformation Stream

N/A N/A Information about theavailable band for CEUs in the

serving cell. For details, see3GPP TS 36.421.

Neighbor

Cell ListInformation

Valid Cell Num Integer 0 to 32 Number of valid neighboring

cells used for ICIC when themonitoring result is reported.

Cell Neighbor List N/A N/A PCI of an available

neighboring cell used by ICIC


26/74

eNodeB

Performance Monitoring Reference 11 MU-MIMO Monitoring



21

11 MU-MIMO MonitoringThis task is used to monitor the number of UEs paired with multi-user multiple-inputmultiple-output (MU-MIMO) within a transmission time interval (TTI) so that the paired UEs

can be viewed conveniently.

11.1 Parameters for MU-MIMO Monitoring

Table 11-1Parameters for MU-MIMO monitoring


Local Cell ID ID of the cell for MU-MIMO monitoring.

Monitor Period(ms)


11.2 Results of MU-MIMO Monitoring

Table 11-2Results of MU-MIMO monitoring

Monitor

Item

Parameter Unit Value

Range

Description

Multi

User-MIMO

MIMO UE Pair

Num

Pair 0 to 16 Number of UEs paired with

MU-MIMO when themonitoring result is reported.

Two UEs paired withMU-MIMO are called one

pair.


27/74

eNodeB

Performance Monitoring Reference 12 Interference Detection Monitoring



22

12 Interference Detection MonitoringThe interference detection monitoring process is described as follows:

An RRU collects data and the LMPT performs fast Fourier transformation (FFT)calculation analysis and processes the data.

The signal spectrum within a configured frequency range is displayed in real time.

Interference detection monitoring implements some functions of a spectrum analyzer and

facilitates identification and analysis of interference problems.

12.1 Parameters for Interference Detection Monitoring

Table 12-1Parameters for interference detection monitoring

Parameter DescriptionLocal Cell ID ID of the cell on which interference detection monitoring is

performed.


200, 500, 1000, or 2000.

12.2 Results of Interference Detection Monitoring

Table 12-2Results of interference detection monitoring

MonitorItem


Description

InterferenceDetect

RB SpectrumInformation

dBm -216

to 216

Received signal strengthin an RB.

Received Signal

Strength Indicator

dBm 140 to50 Received signal strength

in the wideband.


28/74

eNodeB

Performance Monitoring Reference 12 Interference Detection Monitoring



23

MonitorItem


Description

System Bandwidth Integer 0 to 100 Current system

bandwidth (number ofRBs).

Antenna RSSI dBm 140 to50 Received signal strength

indicator for an antenna.

PUSCH Cell dBm 32,768 to

32,767

Average interference

noise power in an RB.


29/74

eNodeB

Performance Monitoring Reference 13 Scheduled Cell-Level UE Information Monitoring



24

13 Scheduled Cell-Level UE InformationMonitoring

This task is used to monitor the number of scheduled cell-level UEs in different scheduling

modes.

13.1 Parameters for Scheduled Cell-Level UE InformationMonitoring

Table 13-1Parameters for scheduled cell-level UE information monitoring

Parameter

Description

Local Cell ID ID of the cell on which scheduled cell-level UE information

monitoring is performed.

Monitor Period

(ms)


500, 1000, or 2000.

13.2 Results of Scheduled Cell-Level UE Information

Monitoring

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


Description

Scheduled Users

Statistic

Total DLSCH

Candidates WithinMonitor Period

Integer 0 to 65535 Total number of

candidate UEs fordownlink scheduling



30/74

eNodeB

Performance Monitoring Reference 13 Scheduled Cell-Level UE Information Monitoring



25


Description

Total DLSCH Users

Within Monitor Period

Integer 0 to 65535 Total number of UEs

scheduled in thedownlink within a

monitoring period.

Total DLSCH

Frequency Selected

Users Within MonitorPeriod


for frequency

selective schedulingin the downlink


Total DLSCH

Diversity Users Within

Monitor Period


for diversity

scheduling in thedownlink within amonitoring period.

Total ULSCH Users

Within Monitor Period


scheduled in theuplink within a

monitoring period.


31/74

eNodeB

Performance Monitoring Reference 14 HARQ Status Monitoring



26

14 HARQ Status MonitoringThis task is used to monitor uplink and downlink hybrid automatic repeat request (HARQ)information about all UEs in a cell. Based on this information, data transmission status of the

eNodeB or UE can be determined.

14.1 Parameters for HARQ Status Monitoring

Table 14-1Parameters for HARQ status monitoring

Parameter DescriptionMonitor Item It can be set to DL HARQ State, UL HARQ State, or a combination

of these two items.

Local Cell ID ID of the cell on which HARQ status monitoring is performed.

Monitor Period(ms)

Period for reporting monitoring results. It can be set to 1000or 2000.

14.2 Results of HARQ Status Monitoring

Table 14-2Results of HARQ status monitoring

MonitorItem


Description

DL HARQ

State

DL PDSCH Code

m ACK Num

Num

ber

0 to 64,000 Number of ACKs for downlink

codeword m(m= {0, 1})within a monitoring period.

DL PDSCH Code

m NACK Num

Num

ber

0 to 64,000 Number of NACKs for

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


32/74

eNodeB

Performance Monitoring Reference 14 HARQ Status Monitoring



27

MonitorItem


Description

DL PDSCH Code

m NoRsp Num

Num

ber

0 to 64,000 Number of times no response is

received for downlinkcodeword m(m= {0, 1})


DL PDSCH Code

m DTX Num

Num

ber

0 to 64,000 Number of DTXs for downlink

codeword m (m = {0, 1})


DL PDSCH

Version m Num

Num

ber

0 to 64,000 Number of times the downlink

HARQ version is m(m= {0, 1,

2, 3}) within a monitoringperiod.

DL PDSCH Rsp for

n TTI Num

Num

ber

0 to 64,000 Number of times downlink

HARQ reports n(n= {8, 9, 10,11}) TTIs within a monitoring

period.

UL HARQ

State

UL PUSCH ACK

Num

Num

ber

0 to 64,000 Number of uplink ACKs within

a monitoring period.

UL PUSCH NACKNum

Number

0 to 64,000 Number of uplink NACKswithin a monitoring period.

UL PUSCH DTX

Num

Num

ber

0 to 64,000 Number of uplink DTXs within

a monitoring period.

UL PUSCHVersion m Num

Number

0 to 64,000 Number of times the uplinkHARQ version is m(m= {0, 1,

2, 3}) within a monitoringperiod.


33/74

eNodeB

Performance Monitoring Reference 15 Air-Interface DCI Status Monitoring



28

15 Air-Interface DCI Status MonitoringThis task is used to monitor the usage of a cell-level physical downlink control channel(PDCCH), including the downlink control information (DCI) format, aggregation level, and

PDCCH symbol number, which are described as follows:

The DCI format indicates resource allocation information. A specific DCI format is used

in a different MIMO mode.

The aggregation level indicates the size of time-frequency resources occupied by aPDCCH.

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

15.1 Parameters for Air-Interface DCI Status MonitoringTable 15-1Parameters for air-interface DCI status monitoring

Parameter DescriptionMonitor Item It can be set to DCI STATISTIC.

Local Cell ID ID of the cell on which air-interface DCI status monitoring is

performed.

Monitor Period

(ms)



34/74

eNodeB




29

15.2 Results of Air-Interface DCI Status Monitoring

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

MonitorItem Parameter Unit ValueRange DescriptionDCI

Statistic

PDCCH Type DCI0

Num

Num

ber

0 to

64,000

Total number of times the

PDCCH type is DCI format 0


PDCCH Type DCI1

Num

Num

ber

0 to

64,000


PDCCH type is DCI format 1within a monitoring period.

PDCCH Type

DCI1A Num

Num

ber

0 to

64,000


PDCCH type is DCI format 1A


PDCCH Type

DCI1B Num

Num

ber

0 to

64,000


PDCCH type is DCI format 1Bwithin a monitoring period.

PDCCH Type

DCI1C Num

Num

ber

0 to

64,000


PDCCH type is DCI format 1Cwithin a monitoring period.

PDCCH Type

DCI1D Num

Num

ber

0 to

64,000


PDCCH type is DCI format 1Dwithin a monitoring period.

PDCCH Type DCI2

Num

Num

ber

0 to

64,000


PDCCH type is DCI format 2within a monitoring period.

PDCCH TypeDCI2A Num

Number

0 to64,000

Total number of times thePDCCH type is DCI format 2A


PDCCH TypeDCI2B Num

Number

0 to64,000

Total number of times thePDCCH type is DCI format 2B


PDCCH Type DCI3Num

Number

0 to64,000

Total number of times thePDCCH type is DCI format 3


PDCCH TypeDCI3A Num

Number

0 to64,000

Total number of times thePDCCH type is DCI format 3A


PDCCH Use m CCE

Num

Num

ber

0 to

64,000

Total number of times the CCE

aggregation level is m(m= {1,

2, 4, 8}) within a monitoringperiod.


35/74

eNodeB




30

MonitorItem Parameter Unit ValueRange Description

CFI Engross n

Symbol Stat. Num

Num

ber

0 to

64,000

Total number of times the CFI

occupies n(n= {1, 2, 3, 4})symbols within a monitoring

period.


36/74

eNodeB

Performance Monitoring Reference 16 Air-Interface DRB Statistics Monitoring



31

16 Air-Interface DRB StatisticsMonitoring

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

16.1 Parameters for Air-Interface DRB StatisticsMonitoring

Table 16-1Parameters for air-interface DRB statistics monitoring

Parameter DescriptionMonitor Item It can be set to DL DRB STATISTIC, UL DRB STATISTIC, or a

combination of these two items.

Local Cell ID ID of the cell on which air-interface DRB statistics monitoring isperformed.

Monitor Period

(ms)


16.2 Results of Air-Interface DRB Statistics Monitoring

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

MonitorItem


Description

DL DRBSTATISTI

C

Number of packetsreceived at the DL

PDCP

Integer 0 to300,000,0

00

Total number of data packetsreceived at the downlink PDCP

layer within a monitoring period.


37/74

eNodeB

Performance Monitoring Reference 16 Air-Interface DRB Statistics Monitoring



32

MonitorItem


Description

Number of bits

received at the DLPDCP

Bit 0 to

300,000,000

Total throughput for data packets

received at the downlink PDCPlayer within a monitoring period.

Number of TBs for

DL MACscheduling

Integer 0 to

300,000,000

Total number of TBs for downlink

MAC scheduling within amonitoring period.

Number of Bit forDL MAC

scheduling

Bit 0 to300,000,0

00

Total throughput for TBsscheduled at the downlink MAC


Number of timesDL RLC sends

data in AM mode

Number

0 to300,000,0

00

Total number of times thedownlink RLC layer transmits

data in acknowledgment (AM)

mode within a monitoring period.

Number of times

DL RLC sendsdata in UM mode

Numbe

r

0 to

300,000,000


downlink RLC layer transmitsdata in unacknowledgment (UM)


UL DRBSTATISTI

C

Number of TBs forUL MAC

scheduling

Integer 0 to300,000,0

00

Total number of TBs for uplinkMAC scheduling within a

monitoring period.

UL Mac TBNumber

Bit 0 to300,000,0

00

Total throughput for TBsscheduled at the uplink MAC layer


Number of correct

UL MAC CRCs

Numbe

r

0 to

300,000,0

00

Total number of times the uplink

MAC layer receives correct cyclic

redundancy checks (CRCs) from aUE within a monitoring period.

Number of

incorrect UL MACCRCs

Numbe

r

0 to

300,000,000


MAC layer receives incorrectCRCs from a UE within a

monitoring period.

Number of times

UL RLC receivesdata in AM mode

Numbe

r

0 to

300,000,000


RLC layer receives data in AMmode within a monitoring period.

Number of times

UL RLC receives

data in UM mode

Numbe

r

0 to

300,000,0

00


RLC layer receives data in UM


Number of packets

transmitted at theUL PDCP

Integer 0 to

300,000,000

Total number of data packets

transmitted at the uplink PDCPlayer within a monitoring period.

Number of bits

transmitted at the

UL PDCP

Bit 0 to

300,000,0

00

Total throughput for data packets

transmitted at the uplink PDCP



38/74

eNodeB

Performance Monitoring Reference 17 BLER Monitoring



33

17 BLER MonitoringThis task is used to monitor the convergence of block error rates (BLERs) on each channel.

17.1 Parameters for BLER Monitoring

Table 17-1Parameters for BLER monitoring

Parameter DescriptionMonitor Item It can be set to Init BLER, Resident BLER, PDCCH BLER, or a


UEID-MME MME of a user.

UEID-TMSI/TraceRef

TMSI or TraceRef to be monitored.

Monitor Period

(ms)


500, 1000, or 2000.

17.2 Results of BLER Monitoring

Table 17-2Results of BLER monitoring

MonitorItem


Description

- Physical CellIdentifier

N/A N/A Physical cell identifier of theserving cell.


39/74

eNodeB




34

MonitorItem


Description

Init BLER Downlink IBLER 0 to 1,000 BLER of initial TB

transmission on a PDSCHwithin a monitoring period =

Total number of TBs that fail tobe initially transmitted on the

PDSCH within the monitoringperiod x 1000/Total number of

initially transmitted TBs on thePDSCH within the monitoring

period.

Uplink IBLER 0 to 1,000 BLER of initial TBtransmission on a PUSCH

within a monitoring period =

Total number of TBs that fail tobe initially transmitted on thePUSCH within the monitoring

period x 1000/Total number of

initially transmitted TBs on thePUSCH within the monitoring

period.

Resident

BLER

Downlink RBLER 0 to 1,000 BLER of the last TB

retransmission on a PDSCH

within a monitoring period =Number of times TBs last fail

to be retransmitted on the

PDSCH within the monitoringperiod x 1000/Total number ofinitially transmitted TBs on the

PDSCH within the monitoringperiod..

Uplink RBLER 0 to 1,000 BLER of the last TB

retransmission on a PUSCHwithin a monitoring period =

Number of times TBs last failto be retransmitted on the

PUSCH within the monitoring

period x 1000/Total number ofinitially transmitted TBs on thePUSCH within the monitoring

period.


40/74

eNodeB




35

MonitorItem


Description

PDCCH

BLER

PDCCH Bler 0 to 1,000 BLER of DLGRANT decoding

on a PDCCH within amonitoring period = Number of

times DLGRANTs decodedincorrectly x 1000/Total

number of DLGRANTs sent ona PDCCH. The error rate is in

the unit of .

The number of DLGRANTs

decoded incorrectly is the

number of DTXs that were thefeedback given to the

DLGRANTs sent on aPDCCH.


41/74

eNodeB

Performance Monitoring Reference 18 Power Headroom Monitoring



36

18 Power Headroom MonitoringThis task is used to monitor the power headroom reported by the UE. Based on thisinformation, the scheduling module estimates the remaining processing capacity of the UE.

18.1 Parameters for Power Headroom Monitoring

Table 18-1Parameters for power headroom monitoring

Parameter DescriptionUEID-MME MME of a user.

UEID-TMSI/TraceRef TMSI or TraceRef to be monitored.


18.2 Result of Power Headroom Monitoring

Table 18-2Result of power headroom monitoring


Description

- Physical Cell

Identifier

N/A N/A Physical cell identifier of

the serving cell.

PowerHeadroom

Power Headroom dB 23 to 40 Power headroom lastreported by the UE.


42/74

eNodeB

Performance Monitoring Reference 19 Channel Quality Monitoring



37

19 Channel Quality MonitoringThis task is used to monitor the uplink and downlink channel status of the UE in real time,which is affected by the inference and varies depending on the position of the UE in a cell.

Based on the channel status information, the uplink and downlink channel quality of the UEcan be determined.

19.1 Parameters for Channel Quality Monitoring

Table 19-1Parameters for channel quality monitoring

Parameter DescriptionMonitor Item It can be set to SINR, CQI, or a combination of these two items.


UEID-TMSI/TraceRef


Monitor Period

(ms)


500, 1000, or 2000.

19.2 Results of Channel Quality Monitoring

Table 19-2Results of channel quality monitoring

MonitorItem Parameter Unit Value Range Description- Physical Cell

IdentifierN/A N/A Physical cell identifier of the

serving cell.


43/74

eNodeB

Performance Monitoring Reference 19 Channel Quality Monitoring



38

MonitorItem Parameter Unit Value Range DescriptionSINR SINR 0.01

dB

12700 to

12700

Average signal to interference

plus noise ratio (SINR) for thefull bandwidth of the UE

measured when the monitoringresult is reported.

SINR Flag N/A N/A Flag of the effective average

SINR for the full bandwidth ofthe UE.

CQI UE Code Count Integ

er

1 to 2 Number of transmitted

codewords in the downlinkwhen the monitoring result is

reported.

Effective Len ms 41 to 44 Valid length of the channelquality indicator (CQI) for the

full bandwidth.

CQI N/A 0 to 31 Value mapped to the originally

reported CQI for the fullbandwidth when the



44/74

eNodeB

Performance Monitoring Reference 20 Scheduling Monitoring



39

20 Scheduling MonitoringThis task is used to monitor the number of scheduling requests sent from the UE and status ofeach data buffer area for uplink services.

20.1 Parameters for Scheduling Monitoring

Table 20-1Parameters for scheduling monitoring

Parameter DescriptionMonitor Item It can be set to UL SR of Service, UL BSR of Service, Percentage of

DRX activity timer in DRX timer, or a combination of these items.


UEID-TMSI/Tra

ceRef


Monitor Period(ms)


20.2 Results of Scheduling Monitoring

Table 20-2Results of scheduling monitoring

Monitor

Item Parameter Unit Value Range Description- Physical Cell

Identifier

N/A N/A Physical cell identifier of the

serving cell.

UL SR of

Service

Number of SRs Num

ber

0 to 4294967296 Number of scheduling

requests (SRs) reported by the

UE to the eNodeB within a

monitoring period.


45/74

eNodeB




40

MonitorItem Parameter Unit Value Range DescriptionUL BSR

of Service

Byte Length 1 of

LCG BS

bit 0 to 150,000 Data volume in the buffer

status report [0] (BSR[0])when the monitoring result is

reported.

If the CRC is successful, the

BSR of the correspondingLogical Channel Group

(LCG) must be updated.When the UE is in the

out-of-synchronization state,

the BSR of all LCGs must becleared.

Byte Length 2 of

LCG BS

bit 0 to 150,000 Data volume in the BSR[1]

when the monitoring result isreported

If the CRC is successful, theBSR of the corresponding

LCG must be updated. Whenthe UE is in the

out-of-synchronization state,the BSR of all LCGs must be

cleared.

Byte Length 3 ofLCG BS

bit 0 to 150,000 Data volume in the BSR[2]when the monitoring result is

reported.If the CRC is successful, the

BSR of the corresponding

LCG must be updated. Whenthe UE is in the

out-of-synchronization state,the BSR of all LCGs must be

cleared.

Byte Length 4 of

LCG BS

bit 0 to 150,000 Data volume in the BSR[3]

when the monitoring result is

reported.

If the CRC is successful, theBSR of the correspondingLCG must be updated. When

the UE is in theout-of-synchronization state,

the BSR of all LCGs must be

cleared.

percentag

e of DRXactivity

timer in

DRX

GAP Time Integ

er

0 to 4294967296 Number of accumulated TTIs

in the call gapping (GAP)state between the start and the

end of the scheduling

monitoring.


46/74

eNodeB




41

MonitorItem Parameter Unit Value Range Descriptiontimer DRX Time Integ

er


in the DRX state between thestart and the end of the

scheduling monitoring.

Number of TTI Integ

er


between the establishment

and the release of an L2 case.


47/74

eNodeB

Performance Monitoring Reference 21 RLC Data Stream Monitoring



42

21 RLC Data Stream MonitoringThis task is used to monitor the data volume to be sent in the downlink buffer area at the RLClayer corresponding to the DRBs for user data.

21.1 Parameters for RLC Data Stream Monitoring

Table 21-1Parameters for RLC data stream monitoring

Parameter DescriptionMonitor Item It can be set to RLC Data Stream.




200, 500, 1000, or 2000.

21.2 Result of RLC Data Stream Monitoring

Table 21-2Result of RLC data stream monitoring

Monitor

Item Parameter Unit ValueRange Description- Physical Cell

Identifier


serving cell.

RLC Data

Stream

RLC Buffer

Length

Byte 0 to

10,000,00

0

Data stream of the RLC SDUs to be

sent on the DRB from the downlink

buffer area at the RLC layer whenthe monitoring result is reported.


48/74

eNodeB

Performance Monitoring Reference 22 Throughput Monitoring



43

22 Throughput MonitoringThis task is used to view the throughputs at the MAC or RLC layer at the eNodeB side in realtime. Based on the comparison of the throughputs between the eNodeB side and the UE side,

whether the data transmission at the eNodeB side is properly can be determined.

22.1 Parameters for Throughput Monitoring

Table 22-1Parameters for throughput monitoring

Parameter DescriptionMonitor Item It can be set to Throughput of RLC, Throughput of MAC, or

a combination of these two items.




22.2 Results of Throughput Monitoring

Table 22-2Results of throughput monitoring

Monitor

Item Parameter Unit Value Range Description- Physical Cell

Identifier


serving cell.


49/74

eNodeB

Performance Monitoring Reference 22 Throughput Monitoring



44

MonitorItem Parameter Unit Value Range DescriptionThroughput

of RLC

Downlink RLC

Throughput

bit/s 0 to

150,000,000

Total throughputs of the

downlink RLC SDUs sent onthe DRB at the RLC layer

within a monitoring period =(Downlink RLC throughputs

on the RLC logical channelsx 8)/(Monitoring period x

1000).

Uplink RLCThroughput

bit/s 0 to150,000,000

Total throughputs of theuplink RLC SDUs received

on the DRB at the RLC layerwithin a monitoring period =

(Uplink RLC throughputs on

the RLC logical channels x8)/(Monitoring period x1000).

Throughput

of MAC

Downlink MAC

Throughput

bit/s 0 to

150,000,000

User-level downlink MAC

throughputs within amonitoring period =

(Downlink MACthroughputs x

8)/(Monitoring period x

1000).

Uplink MAC

Throughput

bit/s 0 to

150,000,000

User-level uplink MAC

throughputs within amonitoring period = (Uplink

MAC throughputs x

8)/(Monitoring period x1000).


50/74

eNodeB

Performance Monitoring Reference 23 AQM Monitoring



45

23 AQM MonitoringThis task is used to monitor the packet loss rate and buffer queues related to the active queuemanagement (AQM) algorithms for DRBs.

23.1 Parameters for AQM Monitoring

Table 23-1Parameters for AQM monitoring

Parameter DescriptionMonitor Item It can be set to Percentage of AQM discard package, DL RLC

buffer length of eNB, or a combination of these two items.


UEID-TMSI/Trac

eRef


Monitor Period(ms)


23.2 Results of AQM Monitoring

Table 23-2Results of AQM monitoring

Monitor

Item Parameter Unit ValueRange Description- Physical Cell

Identifier


serving cell.

Percentag

e of AQM

discard

package

Number of

Discarded

Packets

Packet 0 to 20,000 Number of discarded packets on

the DRB monitored in AQM mode



51/74

eNodeB

Performance Monitoring Reference 23 AQM Monitoring



46

MonitorItem Parameter Unit ValueRange DescriptionDL RLC

bufferlength of

eNB

Number of

Packets inRLC Buffer

Packet 0 to 20,000 Number of RLC SDUs to be sent

on the DRB from the downlinkRLC buffer area at the end of a

monitoring period.


52/74

eNodeB

Performance Monitoring Reference 24 Uplink Power Control Monitoring



47

24 Uplink Power Control MonitoringThis task is used to monitor the necessary information about uplink power control when theswitch for uplink power control is turned on or turned off. This enables users to obtain the

information about the power adjustment when the switch for uplink power control is turnedon or turned off.

24.1 Parameters for Uplink Power Control Monitoring

Table 24-1Parameters for uplink power control monitoring


Monitor Item It can be set to Close-loop Power of UE, PUSCH N max updated of

UE, PUCCH ACK/NACK/DTX Statistic, or a combination of theseitems.


UEID-TMSI/TraceRef


Monitor Period

(ms)


500, 1000, or 2000.

24.2 Results of Uplink Power Control Monitoring

Table 24-2Results of uplink power control monitoring


Description


N/A N/A Physical cellidentifier of the

serving cell.


53/74

eNodeB




48


Description

Close-loop

Power of UE

PUSCH SINR target dB 1500 to

2000

Target SINR of

PUSCH powercontrol. The value

is set by runningMML commands.

PUSCH SINR Adjust

Step

dB 1500 to

2000

The difference

between the actualSINR and target

SINR when theclosed-loop power

control is adjustedwhen the

monitoring result is

reported.

PUSCH IBLER target 1500 to

2000

Target IBLER of

PUSCHclosed-loop power

control. The valueis set by running

MML commands.

PUCCH SINR target dB 1500 to2000

Target SINR ofPUCCH

closed-loop powercontrol. The value

is set by runningMML commands.

PUCCH SINR Adjust

Step

dB 1500 to

2000

The difference

between the actualSINR and the target

SINR of PUCCHclosed-loop power

control when the

monitoring result isreported.

PUSCH N max

updated of UE

Maximum Number of

Transmissions

Number 0 to 10 The maximum

number oftransmissions on

the uplink PUSCH.It is set by running

MML commands.

PUCCH

ACK/NACK/DT

X Statistic

Number of ACK Number 0 to 2000 The number of

ACKs detected on

the PUCCH by theeNodeB within a

monitoring period.


54/74

eNodeB




49


Description

Number of NACK Number 0 to 2000 The number of

NACKs on thePUCCH detected

by the eNodeBwithin a monitoring

period.

Number of DTX Number 0 to 2000 The number ofDTXs on the

PUCCH detectedby the eNodeB


NOTE

If the three items are selected for simultaneous monitoring, the value ranges of the parameters are allfrom600 to 2000.


55/74

eNodeB

Performance Monitoring Reference 25 Downlink Power Control Monitoring



50

25 Downlink Power Control MonitoringThis task is used to monitor the necessary information about downlink power control whenthe switch for downlink power control is turned on or turned off. This enables users to obtain

the power adjustment when the switch for downlink power control is turned on or turned off.

25.1 Parameters for Downlink Power Control Monitoring

Table 25-1Parameters for downlink power control monitoring


Monitor Item It can be set to PDSCH of UE, PHICH of UE, PDCCH of UE, or a



UEID-TMSI/TraceRef


Monitor Period

(ms)


500, 1000, or 2000.

25.2 Results of Downlink Power Control Monitoring

Table 25-2Results of downlink power control monitoring


Description


N/A N/A Physical cellidentifier of the

serving cell.


56/74

eNodeB




51


Description

PDSCH of UE PDSCH PA dB 6 to 3 Power offset between

each resourceelement (RE) on the

PDSCH and the pilotwhen the monitoring

result is reported.

Maximum number oftransmissions

Number

0 to 28 The maximumnumber of

transmissions on thePDSCH, excluding

the initialtransmission. It is set

by running MML

commands.

PDSCH IBLER target 600 to

1000

Target BLER in the

initial transmissionduring the semi-static

PDSCH powercontrol. It is set by

running MMLcommands.

PHICH of UE PHICH SINR target dB 1500 to

2000

Target SINR of

PHICH outer-looppower control. The

value is set byrunning MML

commands.

PHICH SINR adjuststep

dB 1500 to2000

The SINR adjustmentstep calculated in the

PHICH outer-looppower control =

Adjustment step x

Number of NACKstransmitted on the

PHICH within theperiod of outer-loop

power control(Actually measured

BLERTargetBLER)/(1Target

BLER).

The result is

multiplied by 1000.


57/74

eNodeB




52


Description

PHICH BER 1500 to

2000

The probability for

decoding NACKsinto ACKs within the

adjustment period ofthe PHICH

outer-loop powercontrol = Number of

NACKs that aredecoded into ACKs x

1000/Number ofNACKs transmitted

on the PHICH.

PDCCH of UE Power Offset of

Pdcch

dB 1500 to

2000

Offset between the

power fortransmitting each REon the PDCCH and

the pilot power when

the monitoring resultis reported.

TTI ms 1500 to2000

TTI for the PDCCHpower transmitted at

the MAC layer.

NOTE

If the three items are selected for simultaneous monitoring, the value ranges of the parameters are all

from600 to 2000.


58/74

eNodeB

Performance Monitoring Reference 26 Uplink ICIC Monitoring



53

26 Uplink ICIC MonitoringThis task is used to monitor the user property and neighbor cell information during the uplink

ICIC to obtain the operating status of the uplink ICIC.

26.1 Parameters for Uplink ICIC Monitoring

Table 26-1Parameters for uplink ICIC monitoring


Monitor Item It can be set to USER PROPERTY orUSER NEIGHBOR

LIST. You can also select both monitoring items for

simultaneous monitoring.



Monitor Period (ms) Period for reporting monitoring results. It can be set to 50,100, 200, 500, 1000, or 2000.

26.2 Results of Uplink ICIC MonitoringTable 26-2Results of uplink ICIC monitoring


Description

- Physical Cell

Identifier

N/A N/A Physical cell identifier of

the serving cell.

USERPROPERTY

User Type N/A N/A User property. It includesthe CEUs,

enodeb performance monitoring reference(v100r004c00_01)(pdf)-en

Documents