Professional Documents
Culture Documents
eNodeB Performance Monitoring Reference (V100R004C00 - 01) (PDF) - en
eNodeB Performance Monitoring Reference (V100R004C00 - 01) (PDF) - en
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.
Issue 01 (2011-09-15)
Contents
Contents
1 Introduction ......................................................................................................................................... 1 2 Sector Performance Monitoring ..................................................................................................... 3
2.1 Parameters for Sector Performance Monitoring ............................................................................................... 3 2.2 Results of Sector Performance Monitoring ...................................................................................................... 4
Contents
11.1 Parameters for MU-MIMO Monitoring........................................................................................................ 21 11.2 Results of MU-MIMO Monitoring ............................................................................................................... 21
22 Throughput Monitoring............................................................................................................... 43
22.1 Parameters for Throughput Monitoring........................................................................................................ 43 22.2 Results of Throughput Monitoring ............................................................................................................... 43
Issue 01 (2011-09-15)
iii
Contents
Issue 01 (2011-09-15)
iv
1 Introduction
1
Purpose Product Versions
Product Name DBS3900 LTE DBS3900 LTE TDD BTS3900 LTE BTS3900A LTE BTS3900L LTE V100R004C00 V100R004C00 V100R004C00 V100R004C00 V100R004C00
Introduction
This document describes eNodeB performance monitoring results and explains monitoring items in terms of the meanings, value ranges, and calculation methods.
The following table lists the product versions related to this document. Product Version
Intended Audience
This document is intended for:
Change History
This document is revised based on review comments. The latest document contains all updates.
Document Issues
The document issues are as follows:
01 (2011-09-15)
Issue 01 (2011-09-15)
1 Introduction
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 3 RRU/RFU Performance Monitoring Change Description
Added the parameters for RRU/RFU performance 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 5 QoS Satisfaction Rate Monitoring Change Description
Added the parameters for operator QoS satisfaction rate monitoring. Added the results of operator QoS satisfaction rate monitoring.
Compared with issue Draft A (2011-07-15) of V100R004C00, this issue does not remove any information.
Draft A (2011-07-15)
This is the draft.
Issue 01 (2011-09-15)
Radio networks work in open environments and therefore are inevitably affected by interference. Interference detection and location are required in network deployment and long-term network operation. The base station is a receiver system and supports scalable bands. Therefore, it can be used for simple collection of uplink interference information, reducing manual workloads (for example, carrying instruments) during network deployment and interference detection. Uplink frequency scanning helps to check the electromagnetic environment around the eNodeB and detect internal interference in the eNodeB. The RRU or RFU calculates the received signal strength and reports the strength to the LMT after scanning frequencies continuously. The received signal strength is used as reference for interference location and analysis.
Issue 01 (2011-09-15)
In the figure of monitoring result description, the horizontal axis indicates frequency, center frequency for each RB at the air interface, which is in units of kHz. The vertical axis indicates the received signal strength, frequency spectrum, which is in units of dBm.
Table 2-2 Results of sector performance monitoring Monitor Item UL Widefreq Scan Parameter Signal Strength Unit dBm Value Range -140 to -50 Description Received signal strength indicator (RSSI) of each RB from the physical layer when the monitoring result is reported.
Issue 01 (2011-09-15)
This task is used to monitor the performance of the remote radio unit (RRU) or radio frequency unit (RFU) power, temperature, and distance to fault (DTF).
Issue 01 (2011-09-15)
Description Output power of a carrier. Output power of a TX channel. Board temperature. Power amplifier temperature. Distance between the antenna port and the voltage standing wave ratio (VSWR) point. VSWR value.
C C
Distance To Fault(DTF)
VSWR(0.1)
N/A
0 to (216-1)
Issue 01 (2011-09-15)
4 Spectrum Detection
4
Table 4-1 Parameters for spectrum detection Parameter Scan Mode Description
Spectrum Detection
This task is used to detect the spectrum status, monitoring the interference in frequency and time domains in radio environments by analyzing spectrum and power distribution of sampled data.
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. Number of the cabinet where the board for spectrum detection is located. Number of the subrack where the board for spectrum detection is located. Number of the slot where the board for spectrum detection is located. 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.
Period for reporting monitoring results. It can be set to 1000, 2000, or 3000. The Autosave to File check box is selected by default, and monitoring results are automatically saved in the default path. You can also customize another save path and file name.
Issue 01 (2011-09-15)
4 Spectrum Detection
Issue 01 (2011-09-15)
5
Parameter
QoS satisfaction rates of services with different QoS class identifiers (QCIs) are important indicators of evaluating radio network performance. This task is used to check the QoS satisfaction rates of services to evaluate service performance.
Monitor Item
Issue 01 (2011-09-15)
0 to 100
0 to 100
CN Operator GBR Degrade Flag CN Operator UL QCI Satisfaction rate of Service CN Operator DL QCI Satisfaction rate of Service
0 to 100
0 to 100
0 to 100
Issue 01 (2011-09-15)
10
6
Parameter Monitor Item Local Cell ID
This task is used to monitor the general throughput of guaranteed bit rate (GBR) services and non-GBR services to check the air interface quality and scheduling algorithms.
Issue 01 (2011-09-15)
11
Monitor Item
Unit bps
Description Downlink throughput for SDUs of all GBR services transmitted by the RLC layer within a monitoring period. Uplink throughput for SDUs of all service DRBs received at the RLC layer within a monitoring period. Downlink throughput for SDUs of all service DRBs transmitted by the RLC layer within a monitoring period. Uplink throughput for SDUs of all non-GBR services received at the RLC layer within a monitoring period. Downlink throughput for SDUs of all non-GBR services transmitted by the RLC layer within a monitoring period.
RLC thruput
bps
0 to 300,000,000
bps
0 to 300,000,000
Cell Non-GBR Traffic Uplink RLC Throughput (bps) Cell Non-GBR Traffic Downlink RLC Throughput (bps)
bps
0 to 300,000,000
bps
0 to 300,000,000
Issue 01 (2011-09-15)
12
7
Parameter Monitor Item
This task is used to monitor the number of services in a cell to view the distribution of services with different QCIs.
Issue 01 (2011-09-15)
13
8
Parameter Monitor Item
This task is used to monitor the number of users in different scenarios to view the distribution of users in a cell.
Issue 01 (2011-09-15)
14
Unit Integer
Description Number of connected users when the monitoring result is reported, including the number of active users and non-active users. Number of non-active users when the monitoring result is reported, which is the number of users with uplink out-of-synchronization.
Integer
0 to 2,000
Issue 01 (2011-09-15)
15
9 RB Usage Monitoring
9
Parameter Local Cell ID Monitor Period (ms) Description
RB Usage Monitoring
This task is used to monitor the usage of cell-level resource blocks (RBs) in different scheduling modes. RB is the minimum unit of time-frequency resource allocation.
ID of the cell for RB usage monitoring. Period for reporting monitoring results. It can be set to 50, 100, 200, 500, 1000, or 2000.
Integer
Integer
Issue 01 (2011-09-15)
16
9 RB Usage Monitoring
Monitor Item
Parameter Downlink Freq Select Used RB Num Downlink Harq RB Used RB Num Uplink Pucch RB Num
Unit Integer
Description Number of RBs scheduled for downlink frequency selection within a monitoring period. Number of RBs scheduled for downlink HARQ retransmission within a monitoring period. Number of RBs used by the uplink PUCCH when the monitoring result is reported.
Integer
Integer
Issue 01 (2011-09-15)
17
10 ICIC Monitoring
10
10.1 Parameters for ICIC Monitoring
Table 10-1 Parameters for ICIC monitoring Parameter Monitor Item Description
ICIC Monitoring
This task is used to check the status of inter-cell interference coordination (ICIC) by monitoring the data associated to ICIC.
It can be set to HII Information , OI Information , Proportion of High Interference RB in System Bandwidth, Edge User RB Information , Neighbor Cell List Information, or a combination of these items. ID of the cell for ICIC monitoring. Period for reporting monitoring results. It can be set to 50, 100, 200, 500, 1000, or 2000.
Issue 01 (2011-09-15)
18
10 ICIC Monitoring
Monitor Item
Parameter on Valid RB Number in one Hii Hii Bit Informa tion Stream in One Hii Valid Hii Received Num Valid Hii Receive d Number Global Cell Id Valid RB Num in One Hii HII Informa tion
Unit Integer
Description Number of valid RBs in one HII when the monitoring result is reported, which is the same as the number of RBs occupied by the current cell bandwidth. HII information about the serving cell. For details, see 3GPP TS 36.421.
N/A
N/A
Integer
0 to 4
Number of valid HIIs received from neighboring cells by the serving cell when the monitoring result is reported. PCI of a neighboring cell that transmits HII information to the serving cell. Number of valid RBs in one HII when the monitoring result is reported. HII information about a neighboring cell that transmits the information to the serving cell. For details, see 3GPP TS 36.421. PCI of the serving cell. Number of valid RBs in one OI when the monitoring result is reported, which is the same as the number of RBs occupied by the current cell bandwidth. OI information about the serving cell, including high, medium, and low interference levels. For details, see 3GPP TS 36.421.
N/A
N/A
Integer
0 to 110
N/A
N/A
OI Information
OI Sent Informati on
N/A Integer
N/A 0 to 110
OI Informa tion
N/A
N/A
Issue 01 (2011-09-15)
19
10 ICIC Monitoring
Monitor Item
Parameter Valid OI Received Num OI Received Informati on Valid OI Receive d Num Global Cell Id Valid RB Num in One OI
Unit Integer
Value Range 0 to 4
Description Number of valid OIs received from neighboring cells by the serving cell when the monitoring result is reported. PCI of a neighboring cell that transmits OI information to the serving cell. Number of valid RBs in one OI when the monitoring result is reported, which is the same as the number of RBs occupied by the current bandwidth. OI information about a neighboring cell that transmits the information to the serving cell, including high, medium, and low interference levels. For details, see 3GPP TS 36.421. Proportion of high-interference RBs in the serving cell to RBs occupied by the current cell bandwidth when the monitoring result is reported. PCI of the local cell. Number of valid RBs in the available band for cell edge users (CEUs) when the monitoring result is reported. Information about the available band for CEUs in the serving cell. For details, see 3GPP TS 36.421. Number of valid neighboring cells used for ICIC when the monitoring result is reported. PCI of an available neighboring cell used by ICIC
N/A
N/A
Integer
0 to 110
OI Informa tion
N/A
N/A
0 to 100
N/A Integer
N/A 0 to 110
N/A
N/A
Integer
0 to 32
N/A
N/A
Issue 01 (2011-09-15)
20
11 MU-MIMO Monitoring
11
Parameter Local Cell ID Monitor Period (ms) Description
MU-MIMO Monitoring
This task is used to monitor the number of UEs paired with multi-user multiple-input multiple-output (MU-MIMO) within a transmission time interval (TTI) so that the paired UEs can be viewed conveniently.
ID of the cell for MU-MIMO monitoring. Period for reporting monitoring results. It can be set to 50, 100, 200, 500, 1000, or 2000.
Issue 01 (2011-09-15)
21
12
The interference detection monitoring process is described as follows: An RRU collects data and the LMPT performs fast Fourier transformation (FFT) calculation analysis and processes the data. The signal spectrum within a configured frequency range is displayed in real time.
Interference detection monitoring implements some functions of a spectrum analyzer and facilitates identification and analysis of interference problems.
Issue 01 (2011-09-15)
22
Monitor Item
Unit Integer
Description Current system bandwidth (number of RBs). Received signal strength indicator for an antenna. Average interference noise power in an RB.
dBm dBm
Issue 01 (2011-09-15)
23
13
Issue 01 (2011-09-15)
24
Monitor Item
Unit Integer
Description Total number of UEs scheduled in the downlink within a monitoring period. Total number of UEs for frequency selective scheduling in the downlink within a monitoring period. Total number of UEs for diversity scheduling in the downlink within a monitoring period. Total number of UEs scheduled in the uplink within a monitoring period.
Integer
0 to 65535
Integer
0 to 65535
Integer
0 to 65535
Issue 01 (2011-09-15)
25
14
Parameter Monitor Item Local Cell ID Monitor Period (ms)
This task is used to monitor uplink and downlink hybrid automatic repeat request (HARQ) information about all UEs in a cell. Based on this information, data transmission status of the eNodeB or UE can be determined.
0 to 64,000
Issue 01 (2011-09-15)
26
Monitor Item
Description Number of times no response is received for downlink codeword m (m = {0, 1}) within a monitoring period. Number of DTXs for downlink codeword m (m = {0, 1}) within a monitoring period. Number of times the downlink HARQ version is m (m = {0, 1, 2, 3}) within a monitoring period. Number of times downlink HARQ reports n (n = {8, 9, 10, 11}) TTIs within a monitoring period. Number of uplink ACKs within a monitoring period. Number of uplink NACKs within a monitoring period. Number of uplink DTXs within a monitoring period. Number of times the uplink HARQ version is m (m = {0, 1, 2, 3}) within a monitoring period.
0 to 64,000
0 to 64,000
Num ber
0 to 64,000
UL HARQ State
UL PUSCH ACK Num UL PUSCH NACK Num UL PUSCH DTX Num UL PUSCH Version m Num
Issue 01 (2011-09-15)
27
15
This task is used to monitor the usage of a cell-level physical downlink control channel (PDCCH), including the downlink control information (DCI) format, aggregation level, and PDCCH symbol number, which are described as follows: The DCI format indicates resource allocation information. A specific DCI format is used in a different MIMO mode. The aggregation level indicates the size of time-frequency resources occupied by a PDCCH. The PDCCH symbol number indicates the number of OFDM symbols occupied by a PDCCH.
Issue 01 (2011-09-15)
28
Issue 01 (2011-09-15)
29
Monitor Item
Description Total number of times the CFI occupies n (n = {1, 2, 3, 4}) symbols within a monitoring period.
Issue 01 (2011-09-15)
30
16
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.
Issue 01 (2011-09-15)
31
Monitor Item
Parameter Number of bits received at the DL PDCP Number of TBs for DL MAC scheduling Number of Bit for DL MAC scheduling Number of times DL RLC sends data in AM mode Number of times DL RLC sends data in UM mode
Unit Bit
Value Range 0 to 300,000,0 00 0 to 300,000,0 00 0 to 300,000,0 00 0 to 300,000,0 00 0 to 300,000,0 00 0 to 300,000,0 00 0 to 300,000,0 00 0 to 300,000,0 00 0 to 300,000,0 00 0 to 300,000,0 00 0 to 300,000,0 00 0 to 300,000,0 00 0 to 300,000,0 00
Description Total throughput for data packets received at the downlink PDCP layer within a monitoring period. Total number of TBs for downlink MAC scheduling within a monitoring period. Total throughput for TBs scheduled at the downlink MAC layer within a monitoring period. Total number of times the downlink RLC layer transmits data in acknowledgment (AM) mode within a monitoring period. Total number of times the downlink RLC layer transmits data in unacknowledgment (UM) mode within a monitoring period. Total number of TBs for uplink MAC scheduling within a monitoring period. Total throughput for TBs scheduled at the uplink MAC layer within a monitoring period. Total number of times the uplink MAC layer receives correct cyclic redundancy checks (CRCs) from a UE within a monitoring period. Total number of times the uplink MAC layer receives incorrect CRCs from a UE within a monitoring period. Total number of times the uplink RLC layer receives data in AM mode within a monitoring period. Total number of times the uplink RLC layer receives data in UM mode within a monitoring period. Total number of data packets transmitted at the uplink PDCP layer within a monitoring period. Total throughput for data packets transmitted at the uplink PDCP layer within a monitoring period.
Integer
Bit
Numbe r
Numbe r
UL DRB STATISTI C
Integer
Bit
Numbe r
Number of incorrect UL MAC CRCs Number of times UL RLC receives data in AM mode Number of times UL RLC receives data in UM mode Number of packets transmitted at the UL PDCP Number of bits transmitted at the UL PDCP
Numbe r
Bit
Issue 01 (2011-09-15)
32
17 BLER Monitoring
17
Table 17-1 Parameters for BLER monitoring Parameter Monitor Item UEID-MME UEID-TMSI/Trac eRef Monitor (ms) Period Description
BLER Monitoring
This task is used to monitor the convergence of block error rates (BLERs) on each channel.
It can be set to Init BLER , Resident BLER , PDCCH BLER, or a combination of these items. MME of a user. TMSI or TraceRef to be monitored. Period for reporting monitoring results. It can be set to 50, 100, 200, 500, 1000, or 2000.
Issue 01 (2011-09-15)
33
17 BLER Monitoring
Unit
Description BLER of initial TB transmission on a PDSCH within a monitoring period = Total number of TBs that fail to be initially transmitted on the PDSCH within the monitoring period x 1000/Total number of initially transmitted TBs on the PDSCH within the monitoring period. BLER of initial TB transmission on a PUSCH within a monitoring period = Total number of TBs that fail to be initially transmitted on the PUSCH within the monitoring period x 1000/Total number of initially transmitted TBs on the PUSCH within the monitoring period. 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 monitoring period x 1000/Total number of initially transmitted TBs on the PDSCH within the monitoring period.. BLER of the last TB retransmission on a PUSCH within a monitoring period = Number of times TBs last fail to be retransmitted on the PUSCH within the monitoring period x 1000/Total number of initially transmitted TBs on the PUSCH within the monitoring period.
Uplink IBLER
0 to 1,000
Resident BLER
Downlink RBLER
0 to 1,000
Uplink RBLER
0 to 1,000
Issue 01 (2011-09-15)
34
17 BLER Monitoring
Unit
Description BLER of DLGRANT decoding on a PDCCH within a monitoring period = Number of times DLGRANTs decoded incorrectly x 1000/Total number of DLGRANTs sent on a PDCCH. The error rate is in the unit of . The number of DLGRANTs decoded incorrectly is the number of DTXs that were the feedback given to the DLGRANTs sent on a PDCCH.
Issue 01 (2011-09-15)
35
18
Parameter UEID-MME
This task is used to monitor the power headroom reported by the UE. Based on this information, the scheduling module estimates the remaining processing capacity of the UE.
Issue 01 (2011-09-15)
36
19
Parameter Monitor Item UEID-MME UEID-TMSI/Trac eRef Monitor Period (ms)
This task is used to monitor the uplink and downlink channel status of the UE in real time, which is affected by the inference and varies depending on the position of the UE in a cell. Based on the channel status information, the uplink and downlink channel quality of the UE can be determined.
Issue 01 (2011-09-15)
37
Parameter SINR
Unit 0.01 dB
Description Average signal to interference plus noise ratio (SINR) for the full bandwidth of the UE measured when the monitoring result is reported. Flag of the effective average SINR for the full bandwidth of the UE. Number of transmitted codewords in the downlink when the monitoring result is reported. Valid length of the channel quality indicator (CQI) for the full bandwidth. Value mapped to the originally reported CQI for the full bandwidth when the monitoring result is reported.
SINR Flag
N/A
N/A
CQI
UE Code Count
Integ er
1 to 2
Effective Len
ms
41 to 44
CQI
N/A
0 to 31
Issue 01 (2011-09-15)
38
20 Scheduling Monitoring
20
Parameter Monitor Item UEID-MME UEID-TMSI/Tra ceRef Monitor Period (ms) Description
Scheduling Monitoring
This task is used to monitor the number of scheduling requests sent from the UE and status of each data buffer area for uplink services.
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. MME of a user. TMSI or TraceRef to be monitored. Period for reporting monitoring results. It can be set to 50, 100, 200, 500, 1000, or 2000.
Issue 01 (2011-09-15)
39
20 Scheduling Monitoring
Unit bit
Description 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 corresponding Logical Channel Group (LCG) must be updated. When the UE is in the out-of-synchronization state, the BSR of all LCGs must be cleared.
bit
0 to 150,000
Data volume in the BSR[1] when the monitoring result is reported If the CRC is successful, the BSR of the corresponding LCG must be updated. When the UE is in the out-of-synchronization state, the BSR of all LCGs must be cleared.
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. When the UE is in the out-of-synchronization state, the BSR of all LCGs must be cleared.
bit
0 to 150,000
Data volume in the BSR[3] when the monitoring result is reported. If the CRC is successful, the BSR of the corresponding LCG must be updated. When the UE is in the out-of-synchronization state, the BSR of all LCGs must be cleared.
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.
Issue 01 (2011-09-15)
40
20 Scheduling Monitoring
Unit Integ er
Description Number of accumulated TTIs in the DRX state between the start and the end of the scheduling monitoring. Number of accumulated TTIs between the establishment and the release of an L2 case.
Number of TTI
Integ er
0 to 4294967296
Issue 01 (2011-09-15)
41
21
Parameter Monitor Item UEID-MME
This task is used to monitor the data volume to be sent in the downlink buffer area at the RLC layer corresponding to the DRBs for user data.
Issue 01 (2011-09-15)
42
22 Throughput Monitoring
22
Parameter Monitor Item UEID-MME UEID-TMSI/TraceRef Monitor Period (ms)
Throughput Monitoring
This task is used to view the throughputs at the MAC or RLC layer at the eNodeB side in real time. Based on the comparison of the throughputs between the eNodeB side and the UE side, whether the data transmission at the eNodeB side is properly can be determined.
Issue 01 (2011-09-15)
43
22 Throughput Monitoring
Unit bit/s
Description Total throughputs of the downlink RLC SDUs sent on the DRB at the RLC layer within a monitoring period = (Downlink RLC throughputs on the RLC logical channels x 8)/(Monitoring period x 1000). Total throughputs of the uplink RLC SDUs received on the DRB at the RLC layer within a monitoring period = (Uplink RLC throughputs on the RLC logical channels x 8)/(Monitoring period x 1000). User-level downlink MAC throughputs within a monitoring period = (Downlink MAC throughputs x 8)/(Monitoring period x 1000). User-level uplink MAC throughputs within a monitoring period = (Uplink MAC throughputs x 8)/(Monitoring period x 1000).
bit/s
0 to 150,000,000
Throughput of MAC
bit/s
0 to 150,000,000
bit/s
0 to 150,000,000
Issue 01 (2011-09-15)
44
23 AQM Monitoring
23
Table 23-1 Parameters for AQM monitoring Parameter Monitor Item UEID-MME UEID-TMSI/Trac eRef Monitor Period (ms) Description
AQM Monitoring
This task is used to monitor the packet loss rate and buffer queues related to the active queue management (AQM) algorithms for DRBs.
It can be set to Percentage of AQM discard package, DL RLC buffer length of eNB , or a combination of these two items. MME of a user. TMSI or TraceRef to be monitored. Period for reporting monitoring results. It can be set to 50, 100, 200, 500, 1000, or 2000.
Issue 01 (2011-09-15)
45
23 AQM Monitoring
Unit Packet
Description Number of RLC SDUs to be sent on the DRB from the downlink RLC buffer area at the end of a monitoring period.
Issue 01 (2011-09-15)
46
24
This task is used to monitor the necessary information about uplink power control when the switch for uplink power control is turned on or turned off. This enables users to obtain the information about the power adjustment when the switch for uplink power control is turned on or turned off.
Issue 01 (2011-09-15)
47
Unit dB
Description Target SINR of PUSCH power control. The value is set by running MML commands. The difference between the actual SINR and target SINR when the closed-loop power control is adjusted when the monitoring result is reported. Target IBLER of PUSCH closed-loop power control. The value is set by running MML commands. Target SINR of PUCCH closed-loop power control. The value is set by running MML commands. The difference between the actual SINR and the target SINR of PUCCH closed-loop power control when the monitoring result is reported. The maximum number of transmissions on the uplink PUSCH. It is set by running MML commands. The number of ACKs detected on the PUCCH by the eNodeB within a monitoring period.
dB
1500 2000
to
1500 2000
to
dB
1500 2000
to
dB
1500 2000
to
Number
0 to 10
Number of ACK
Number
0 to 2000
Issue 01 (2011-09-15)
48
Monitor Item
Unit Number
Description The number of NACKs on the PUCCH detected by the eNodeB within a monitoring period. The number of DTXs on the PUCCH detected by the eNodeB within a monitoring period.
Number of DTX
Number
0 to 2000
NOTE
If the three items are selected for simultaneous monitoring, the value ranges of the parameters are all from 600 to 2000.
Issue 01 (2011-09-15)
49
25
This task is used to monitor the necessary information about downlink power control when the switch for downlink power control is turned on or turned off. This enables users to obtain the power adjustment when the switch for downlink power control is turned on or turned off.
Issue 01 (2011-09-15)
50
Parameter PDSCH PA
Unit dB
Value Range 6 to 3
Description Power offset between each resource element (RE) on the PDSCH and the pilot when the monitoring result is reported. The maximum number of transmissions on the PDSCH, excluding the initial transmission. It is set by running MML commands. Target BLER in the initial transmission during the semi-static PDSCH power control. It is set by running MML commands. Target SINR of PHICH outer-loop power control. The value is set by running MML commands. The SINR adjustment step calculated in the PHICH outer-loop power control = Adjustment step x Number of NACKs transmitted on the PHICH within the period of outer-loop power control (Actually measured BLER Target BLER)/(1 Target BLER). The result is multiplied by 1000.
Num ber
0 to 28
600 to 1000
PHICH of UE
dB
1500 to 2000
dB
1500 to 2000
Issue 01 (2011-09-15)
51
Monitor Item
Unit
Description The probability for decoding NACKs into ACKs within the adjustment period of the PHICH outer-loop power control = Number of NACKs that are decoded into ACKs x 1000/Number of NACKs transmitted on the PHICH. Offset between the power for transmitting each RE on the PDCCH and the pilot power when the monitoring result is reported. TTI for the PDCCH power transmitted at the MAC layer.
PDCCH of UE
dB
1500 to 2000
TTI
ms
1500 to 2000
NOTE
If the three items are selected for simultaneous monitoring, the value ranges of the parameters are all from 600 to 2000.
Issue 01 (2011-09-15)
52
26
Parameter Monitor Item
This task is used to monitor the user property and neighbor cell information during the uplink ICIC to obtain the operating status of the uplink ICIC.
Issue 01 (2011-09-15)
53
Unit N/A
Description Physical ID of the detected neighbor cell with the best signal quality among the cells in the user neighbor list. Physical ID of the detected neighbor cell with the second best signal quality among the cells in the user neighbor list.
N/A
N/A
Issue 01 (2011-09-15)
54
27
This task is used to monitor the number of scheduling attempts and number of RBs in scenarios of different MCSs. The eNodeB uses different MCSs to schedule UEs in different channel situations. The step of the MCS ranges from step 0 to step 28. The number of scheduling attempts indicates the number of scheduling attempts with a specific MCS step and the number of RBs indicates the total number of RBs scheduled using a specific MCS step.
Issue 01 (2011-09-15)
55
Unit Number
Description Total number of scheduling on codeword 0 in the downlink scheduling within a monitoring period. Total number of RBs on codeword 0 in the downlink scheduling within a monitoring period. Total number of scheduling on codeword 1 in the downlink scheduling within a monitoring period. Total number of RBs on codeword 1 in the downlink scheduling within a monitoring period. The number of uplink scheduling within a monitoring period. Total number of RBs in the uplink scheduling within a monitoring period.
Integer
0 to 200,000
Number
0 to 2000
Integer
0 to 200,000
UL MCS
ULSCH Num
Number
0 to 2000
ULSCH RBs
Integer
0 to 200,000
Issue 01 (2011-09-15)
56
28 IP Performance Monitoring
28
Parameter Cabinet No. Subrack No. Slot No. Monitor Period (Second)
IP Performance Monitoring
This task is used to monitor the transmission and reception of data at the IP layer of the eNodeB in real time.
Issue 01 (2011-09-15)
57
28 IP Performance Monitoring
Monitor Item
Parameter Tx Packets
Unit Integer
Description Total number of packets at the IP layer transmitted by the board within a monitoring period. Total number of packets discarded at the IP layer by the board within a monitoring period.
Rx Loss Packets
Integer
Issue 01 (2011-09-15)
58
29
Parameter IP PATH No. Monitor Period (Second)
This task is used to monitor the transmission and reception of service data flows in real time. This facilitates the verification of the stability of traffic flow.
Transmit Rate
kbit/s
0 to 100,000
Issue 01 (2011-09-15)
59
Monitor Item
Unit ms
Description The average delay on the IP path within the monitoring period = (Sum of delays for transmitting the IP PM data bound to the IP path from the eNodeB to the EPC + Sum of delays for transmitting data the IP PM data bound to the IP path from the eNodeB to the EPC)/Number of all quadruplet-based and triplet-based IP PM packets bound to the IP path. One IP path can only be bound to one triplet-based IP PM, but can be bound to multiple quadruplet-based IP PMs..
Average Jitter
ms
0 to 100
The average jitter on the IP path within the monitoring period = Sum of jitter occurrences of all the IP PM packets bound to the IP path from the eNodeB to the EPC/Number of IP PM packets bound to the IP path from the eNodeB to the EPC. The jitter of each IP PM packet = Delay of data transmission from the IP PM to the EPC Average delay of data transmission from the IP PM to the EPC.
Issue 01 (2011-09-15)
60
30
Parameter Cabinet No. Subrack No. Slot No. Monitor Period (Second)
This task is used to monitor the transmission and reception of data on the Stream Control Transmission Protocol (SCTP) link in real time. This facilitates the verification of the stability of the signaling data flow.
Issue 01 (2011-09-15)
61
Monitor Item
Parameter Send Total Packets Receive Total Drop Packets Retrans Ratio
Unit Integer
Description The number of packets transmitted on the SCTP link within a monitoring period. The number of packets discarded on the SCTP link within a monitoring period. Formula: Retransmission ratio = Number of data blocks retransmitted on the SCTP link within the monitoring period x 100/Number of data blocks transmitted on the SCTP link.
Integer
Issue 01 (2011-09-15)
62
31
This task is used to monitor the local traffic and forwarded throughput in real time. Forwarded traffic is common when eNodeBs are cascaded.
byte/s
0 to 4,294,967,295
Issue 01 (2011-09-15)
63
Monitor Item
Unit byte/s
Description The number of bytes forwarded by the eNodeB per second within the monitoring period.
Issue 01 (2011-09-15)
64
32
Parameter Cabinet No. Subrack No. Slot No. CN Operator ID Monitor Period (Second)
Issue 01 (2011-09-15)
65
UL Trans Load
kbit/s
UL Total Traffic
kbit/s
bit
bit
UL Cong State
N/A
DL License Congestion
N/A
N/A
DL Trans Load
kbit/s
0 to 429496729 5 0 to 429496729 5
DL Total Traffic
kbit/s
Issue 01 (2011-09-15)
66
Monitor Item
Unit Bit
Description The virtual buffer capacity for downlink CIRs of the monitored operator when the monitoring result is reported. The virtual buffer capacity for downlink PIRs of the monitored operator when the monitoring result is reported. The downlink congestion status of the monitored operator. 0 indicates that the congestion is cleared and 1 indicates that congestion is generated.
Bit
DL Cong State
N/A
Issue 01 (2011-09-15)
67
33
Parameter Cabinet No. Subrack No. Slot No. Monitor Period (Second)
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.
Source IP Address Source Port No. Destination IP Address UDestination Port No. DSCP Speed (Kbps)
Issue 01 (2011-09-15)
68
Description Length of the UDP packet. The value ranges from 72 to 1500. The default value is 1500. Duration of UDP injection test monitoring. The test stops automatically when the duration expires. The value ranges from 1 to 60. The default value is 15.
0 to 100
Delay
N/A
0 to 100
Jitter
N/A
0 to 100
Average Delay
N/A
0 to 100
Issue 01 (2011-09-15)
69