Professional Documents
Culture Documents
3900 Series Base Station Performance Counter Reference (V100R008C00 - 08, eNodeB) (PDF) - EN PDF
3900 Series Base Station Performance Counter Reference (V100R008C00 - 08, eNodeB) (PDF) - EN PDF
3900 Series Base Station Performance Counter Reference (V100R008C00 - 08, eNodeB) (PDF) - EN PDF
V100R008C00 (eNodeB)
Issue 08
Date 2014-03-14
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Purpose
This document describes all the performance counters of the eNodeB.
Product Version
The following table lists the product version involved in this document.
DBS3900 V100R008C00
The mapping single-mode base station version
BTS3900A
is:
DBS3900 eNodeB: V100R006C00
BTS3900L
BTS3900AL
Intended Audience
This document is intended for:
l Network planners
l System engineers
Change History
For detailed performance counter changes, see Performance Counter Changes document of the
release notes.
Document Structure
Figure 1 shows the document structure.
Table 1 Terms
Term Explanation
Item Description
Item Description
Counter A table that lists parent counters and their child counters in a
Relationship table. Note that the child counters listed in the table cover only
typical scenarios. That is, some scenarios are not covered by
any counter. Therefore, the value of a parent counter is larger
than or equal to the sum of the values of its child counters.
Some counters may not be involved in any counter
relationship.
Related Features Features related to a counter are listed in feature ID and feature
name. A counter is used to estimate related features. Related
features are listed as follows in different scenarios:
l If a counter has no related features, no features are listed.
l A counter has related features,
– If this counter applies only to GSM, UMTS, LTE, or
SingleRAN, the features are related to such RAT.
– If this counter applies to multiple RATs in GSM,
UMTS, LTE, and SingleRAN, the features are a set of
features related to all associated RATs. Only the
feature IDs and feature names of the features for related
RATs are listed.
Original Release The number of version for which the counter was first
available.
Measurement Period
The measurement period is 15 minutes or 60 minutes.
Contents
2.2.6.12 Number of E-RAB Releases Initiated by the eNodeB Because of the S1 RESET in a Cell..............................506
2.2.6.13 Number of E-RAB Releases Initiated by the MME Because of the S1 RESET in a Cell..................................510
2.2.7 Measurement related to E-RAB establish failure (E-RAB.EstFail.Cell)................................................................515
2.2.7.1 Number of E-RAB Setup Failures for Different Causes in a Cell........................................................................517
2.2.8 Measurement related to E-RAB modify (E-RAB.Modify.Cell)..............................................................................524
2.2.8.1 Number of E-RAB Modification Attempts in a Cell............................................................................................529
2.2.8.2 Number of Successful E-RAB Modifications in a Cell........................................................................................533
2.2.8.3 Number of E-RAB Modification Failures for Different Causes in a Cell............................................................538
2.2.9 Measurement related to Cell Algorithm (Algo.Cell)...............................................................................................539
2.2.9.1 Number of Times Uplink or Downlink Congestion Occurs in a Cell..................................................................547
2.2.9.2 Duration of Uplink or Downlink Congestion in a Cell........................................................................................548
2.2.9.3 Number of Service Releases due to Congestion in a Cell....................................................................................549
2.2.9.4 Duration of Cell Unavailability............................................................................................................................550
2.2.9.5 Duration of Cell Availability................................................................................................................................552
2.2.9.6 Number of Signaling Messages over the Uu Interface.........................................................................................553
2.2.9.7 Number of DRX Reconfiguration Messages........................................................................................................554
2.2.9.8 Uplink or Downlink Voice Quality in a Cell........................................................................................................555
2.2.9.9 Number of Times that E-UTRAN is Configured as the Highest Frequency Priority in an IMMCI IE................559
2.2.9.10 Number of Times that the WCDMA Network is Configured as the Highest Frequency Priority in an IMMCI IE
..........................................................................................................................................................................................560
2.2.9.11 Number of Times that GERAN is Configured as the Highest Frequency Priority in an IMMCI IE.................562
2.2.9.12 Number of Successful Preemptions Triggered due to User Limitation..............................................................563
2.2.9.13 Number of Semi-Persistent Scheduling Times in a cell.....................................................................................564
2.2.9.14 Number of Failed Semi-Persistent Scheduling Transmissions in a Cell............................................................566
2.2.9.15 Number of Times a UE in Connected Mode Enters DRX in RRC_CONECTED Mode...................................567
2.2.9.16 Number of Times a UE in Connected Mode Exits DRX in RRC_CONECTED Mode.....................................569
2.2.9.17 DRX Duration.....................................................................................................................................................570
2.2.10 Measurement related to DRB (Traffic.DRB.Cell).................................................................................................572
2.2.10.1 Number of DRBs in a Cell.................................................................................................................................575
2.2.11 Measurement related to Thruput (Traffic.Thruput.Cell).......................................................................................578
2.2.11.1 Maximum Uplink Traffic Volume for PDCP SDUs in a Cell............................................................................601
2.2.11.2 Maximum Downlink Traffic Volume for PDCP SDUs in a Cell.......................................................................605
2.2.11.3 Total Bits of Transmitted Signaling SDUs on SRBs at the PDCP Layer in a Cell............................................609
2.2.11.4 Total Bits of Received Signaling SDUs on SRBs at the PDCP Layer in a Cell................................................609
2.2.11.5 Total Duration of Downlink Data Transmission in a Cell..................................................................................610
2.2.11.6 Total Duration of Uplink Data Transmission in a Cell......................................................................................612
2.2.11.7 Duration of Data Transmission for Services with a Specific QCI in a Cell.......................................................613
2.2.11.8 Total Duration of UE Data Transmission in a Cell............................................................................................617
2.2.11.9 Uplink Traffic Volume for PDCP SDUs in a Cell.............................................................................................618
2.2.11.10 Receive Duration of Uplink PDCP SDUs in a Cell..........................................................................................622
2.2.11.11 Downlink Traffic Volume for PDCP SDUs in a Cell......................................................................................626
2.2.11.12 Transmit Duration of Downlink PDCP SDUs in a Cell...................................................................................630
2.2.11.13 Total Bits of User Data Received at the PDCP Layer from CEUs in a Cell....................................................635
2.2.11.14 Total Duration in Which User Data From CEUs Is Received at the PDCP Layer in a Cell............................636
2.2.11.15 Total Bits of User Data Transmitted at the PDCP Layer to CEUs in a Cell....................................................637
2.2.11.16 Total Duration in Which User Data Is Transmitted to CEUs at the PDCP Layer in a Cell.............................638
2.2.11.17 Total Traffic Volume of Downlink PDCP SDUs Transmitted to Activated CA UEs in a Cell.......................639
2.2.11.18 Total Transmit Duration of Downlink PDCP SDUs Transmitted to Activated CA UEs in a Cell..................640
2.2.11.19 Total Duration of Downlink Data Transmission with the Precision of 1 Millisecond in a Cell......................642
2.2.11.20 Total Duration of Uplink Data Transmission with the Precision of 1 Millisecond in a Cell...........................643
2.2.11.21 Downlink traffic volume sent in the last TTI before the buffer is empty.........................................................644
2.2.11.22 Data transmit duration except the last TTI before the downlink buffer is empty.............................................648
2.2.11.23 Traffic Volume of Uplink PDCP SDUs Sent in the Last TTI Before the UE Buffer is Empty.......................653
2.2.11.24 Uplink Data Transmit Duration Except the Last TTI Before the UE Buffer is Empty....................................654
2.2.11.25 Uplink Traffic Volume of PDCP SDUs Scheduled for Small Packets............................................................655
2.2.11.26 Uplink Data Transmission Duration Except that for Small Packets.................................................................656
2.2.12 Measurement related to PDCP (Traffic.PDCP.Cell).............................................................................................657
2.2.12.1 Number of Discarded Downlink PDCP SDUs...................................................................................................662
2.2.12.2 Downlink ROHC Compression Rate of Headers...............................................................................................665
2.2.12.3 Downlink ROHC Compression Rate..................................................................................................................667
2.2.12.4 Decompression Failure Rate of Uplink PDCP SDUs After the ROHC.............................................................668
2.2.12.5 Number of Transmitted Downlink Traffic PDCP SDUs for DRB Services in a Cell over the Uu Interface
..........................................................................................................................................................................................669
2.2.12.6 Uplink ROHC Compression Rate of Headers....................................................................................................672
2.2.12.7 Uplink ROHC Compression Rate.......................................................................................................................674
2.2.13 Measurement related to Paging (Paging.Cell).......................................................................................................675
2.2.13.1 Number of Received Paging Messages over the S1 Interface in a Cell.............................................................676
2.2.13.2 Number of UEs Contained in Paging Messages Transmitted over the Uu Interface in a Cell...........................677
2.2.13.3 Number of Successful Paging Responses from the UE in a Cell.......................................................................679
2.2.13.4 Number of Discarded Paging Messages from the MME to UEs in a Cell.........................................................680
2.2.13.5 Number of Paging Messages Transmitted Due to System Information Changes..............................................681
2.2.13.6 Number of Paging Messages Discarded due to Paging Channel Congestion....................................................682
2.2.14 Measurement related to securmode (SecurMode.Cell).........................................................................................683
2.2.14.1 Number of Security Mode Setups in a Cell........................................................................................................684
2.2.15 Measurement related to RA (RA.Cell)..................................................................................................................688
2.2.15.1 Number of Times the Contention Preamble Is Received...................................................................................694
2.2.15.2 Number of Times the Random Access Response Message Is Sent After the Contention Preamble Is Received
..........................................................................................................................................................................................695
2.2.15.3 Number of Times the Contention Resolution Message Is Sent After the Contention Preamble Is Received
..........................................................................................................................................................................................697
2.2.15.4 Number of Times the Non-Contention-Based Preamble Is Received................................................................700
2.2.15.5 Number of Times the Random Access Response Message Is Sent After the Non-Contention-Based Preamble Is
Received...........................................................................................................................................................................702
2.2.15.6 Number of Times the UE Msg3 Response Message Is Received in the Handover-Triggered Non-Contention-
Based RA Procedure.........................................................................................................................................................704
2.2.15.7 Number of Times the TA with a Specific Value Range in a UE-Initiated Random Access Procedure in a Cell
..........................................................................................................................................................................................705
2.2.16 Measurement related to PWR (ChMeas.Pwr.Cell)................................................................................................710
2.2.16.1 Downlink Transmit Power..................................................................................................................................712
2.2.16.2 Interference and Noise Received by Each PRB in a Cell...................................................................................713
2.2.16.3 Receive Power of interference and noise detected of each PRB in the UL UpPTS...........................................715
2.2.16.4 Receive Power of the first Symbol in First UL Subframe..................................................................................716
2.2.16.5 Receive Power of the seventh (or fifth) Symbol in First UL Subframe.............................................................717
2.2.16.6 Receive Power of the first Symbol in Last UL Subframe..................................................................................718
2.2.16.7 Receive Power of the twelfth (or tenth) Symbol in the Last UL Subframe.......................................................719
2.2.17 Measurement related to MIMO (ChMeas.MIMO.Cell)........................................................................................720
2.2.17.1 Number of Used Downlink PRBs in MIMO Mode............................................................................................723
2.2.17.2 Number of RBs That Are Successfully Paired for VMIMO UEs in a Cell........................................................727
2.2.17.3 Number of RBs That Can Be Paired for VMIMO UEs in a Cell.......................................................................728
2.2.17.4 Number of RBs for MIMO UEs That Are Successfully Paired for MUBF in a Cell.........................................729
2.2.17.5 Number of RBs for MIMO UEs That Can Be Paired for MUBF in a Cell........................................................730
2.2.17.6 Number of Used Downlink PRBs in BF Mode..................................................................................................731
2.2.18 Measurement related to CQI (ChMeas.CQI.Cell).................................................................................................732
2.2.18.1 Number of Wideband CQI Reports in a Cell.....................................................................................................755
2.2.18.2 Number of Periodic Wideband CQI Reports in Single-Codeword Transmission in a Cell...............................762
2.2.18.3 Number of Aperiodic Wideband CQI Reports in Single-Codeword Transmission in a Cell.............................770
2.2.18.4 Number of Periodic Wideband CQI Reports for Codeword 0 in Dual-Codeword Transmission in a Cell.......777
2.2.18.5 Number of Aperiodic Wideband CQI Reports for Codeword 0 in Dual-Codeword Transmission in a Cell
..........................................................................................................................................................................................784
2.2.18.6 Number of Periodic Wideband CQI Reports for Codeword 1 in Dual-Codeword Transmission in a Cell.......791
2.2.18.7 Number of Aperiodic Wideband CQI Reports for Codeword 1 in Dual-Codeword Transmission in a Cell
..........................................................................................................................................................................................798
2.2.19 Measurement related to MCS (ChMeas.MCS.Cell)..............................................................................................805
2.2.19.1 Number of Times an MCS Index Is Scheduled on the PUSCH.........................................................................837
2.2.19.2 Number of Times a Specific MCS Index Is Scheduled on the PDSCH.............................................................853
2.2.19.3 Number of PRBs on the PUSCH Using a Specified MCS for Scheduling in a Cell..........................................869
2.2.19.4 Number of PRBs on the PDSCH Using a Specific MCS index for Scheduling in a Cell..................................879
2.2.20 Measurement related to PRB (ChMeas.PRB.Cell)................................................................................................921
2.2.20.1 Number of Used Uplink PRBs...........................................................................................................................928
2.2.20.2 Number of Used Downlink PRBs......................................................................................................................930
2.2.20.3 Number of Used PUCCH...................................................................................................................................931
2.2.20.4 Number of OFDM Symbols Occupied by the PDCCH......................................................................................932
2.2.20.5 Number of PDCCH CCEs used in a cell............................................................................................................934
2.2.20.6 Average Number of PRBs Occupied by CA UEs in a Cell................................................................................936
2.2.20.7 Average Number of Available PRBs in a Cell...................................................................................................938
2.2.20.8 Average Number of PRBs Used by CEUs in a Cell...........................................................................................940
2.2.20.9 Average Number of PRBs Allocated for Frequency Selective Scheduling.......................................................941
2.2.23.42 Number of Inter-RAT Handover Executions from E-UTRAN to WCDMA Network Triggered for UEs to Go
back to the HPLMN........................................................................................................................................................1152
2.2.23.43 Number of Inter-RAT Handovers from E-UTRAN to WCDMA Network Triggered for UEs to Go back to the
HPLMN..........................................................................................................................................................................1154
2.2.23.44 Number of Inter-RAT Handover Executions from E-UTRAN to WCDMA Network Triggered for UEs That Do
not Transmit or Receive Data.........................................................................................................................................1156
2.2.23.45 Number of Successful Inter-RAT Handovers from E-UTRAN to WCDMA Network Triggered for UEs That Do
not Transmit or Receive Data.........................................................................................................................................1158
2.2.23.46 Number of LCS-based Inter-RAT Handover Executions for SRVCC...........................................................1160
2.2.23.47 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During Inter-RAT
Handover Executions from E-UTRAN to Another System...........................................................................................1165
2.2.23.48 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During Inter-RAT
Handover Executions from E-UTRAN to Another System for SRVCC........................................................................1169
2.2.23.49 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During CCO Executions
from E-UTRAN to GERAN...........................................................................................................................................1172
2.2.23.50 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During CSFB-based Inter-
RAT Handover Executions from E-UTRAN to Another System..................................................................................1174
2.2.24 Measurement related to IRATHOIN (HO.IRAT.In.Cell)...................................................................................1177
2.2.24.1 Success Rate of Inter-RAT Handovers from E-UTRAN to CDMA2000 Network.........................................1181
2.2.24.2 Success Rate of Inter-RAT Handovers from E-UTRAN to WCDMA Network..............................................1182
2.2.24.3 Success Rate of Inter-RAT Handovers from E-UTRAN to GERAN...............................................................1183
2.2.24.4 Number of Inter-RAT Handover Attempts from GERAN to E-UTRAN........................................................1184
2.2.24.5 Number of Inter-RAT Handover Preparation from GERAN to E-UTRAN.....................................................1186
2.2.24.6 Number of Successful Inter-RAT Handovers from GERAN to E-UTRAN....................................................1187
2.2.24.7 Number of Inter-RAT inter-RAT Handover Preparation Failures for Different Causes in a Cell...................1189
2.2.24.8 Number of Inter-RAT Handover Attempts from TD-SCDMA Network to E-UTRAN..................................1192
2.2.24.9 Number of Inter-RAT Handover Preparation from TD-SCDMA Network to E-UTRAN..............................1194
2.2.24.10 Number of Successful Inter-RAT Handovers from TD-SCDMA Network to E-UTRAN............................1195
2.2.24.11 Number of Inter-RAT Handover Attempts from WCDMA Network to E-UTRAN.....................................1197
2.2.24.12 Number of Inter-RAT Handover Preparation from WCDMA Network to E-UTRAN..................................1199
2.2.24.13 Number of Successful Inter-RAT Handovers from WCDMA Network to E-UTRAN.................................1200
2.2.25 Measurement related to Intra eRan HOOUT (HO.eRAN.Out.Cell)...................................................................1202
2.2.25.1 Number of Intra-eNodeB Outgoing Handover Attempts in a Cell...................................................................1213
2.2.25.2 Number of Intra-eNodeB Outgoing Handovers Executions in a Cell..............................................................1214
2.2.25.3 Number of Successful Intra-eNodeB Outgoing Handovers in a Cell...............................................................1216
2.2.25.4 Number of Inter-eNodeB Outgoing Handover Attempts in a Cell...................................................................1219
2.2.25.5 Number of Inter-eNodeB Outgoing Handovers Executions in a Cell..............................................................1222
2.2.25.6 Number of Successful Inter-eNodeB Outgoing Handovers in a Cell...............................................................1224
2.2.25.7 Intra-Frequency Handover Success Rate..........................................................................................................1230
2.2.25.8 Inter-Frequency Handover Success Rate..........................................................................................................1231
2.2.25.9 Number of Outgoing Blind Handover Attempts in a Cell................................................................................1232
2.2.25.10 Number of Outgoing Blind Handovers Executions in a Cell.........................................................................1234
2.2.25.11 Number of Successful Outgoing Blind Handovers in a Cell..........................................................................1237
2.2.34.1 Number of Times When the Downlink Attribute of a UE Changes from Independent-scheduling to Joint-
scheduling.......................................................................................................................................................................1459
2.2.34.2 Number of Times When the Downlink Attribute of a UE Changes from Joint-scheduling to Independent-
scheduling.......................................................................................................................................................................1459
2.2.34.3 Number of Times that the Downlink Target RRU of a UE in an SFN Cell Changes......................................1460
2.2.34.4 Average Number of Joint-scheduling UEs in the Uplink.................................................................................1461
2.2.34.5 Average number of working RRUs for a joint-scheduling UE in the uplink...................................................1462
2.2.34.6 Number of Times When the Uplink Attribute of a UE Changes from Independent Scheduling to Joint Scheduling
in an SFN Cell................................................................................................................................................................1463
2.2.34.7 Number of Times When the Uplink Attribute of a UE Changes from Joint-scheduling to Independent-scheduling
in an SFN cell.................................................................................................................................................................1464
2.2.34.8 Number of Times that the Uplink Target RRU of a UE in an SFN Cell Changes...........................................1465
2.2.34.9 Average Number of Joint-scheduling UEs in the Downlink............................................................................1466
2.2.34.10 Average Number of Working RRUs for a Joint-scheduling UE in the Downlink.........................................1467
2.2.35 Measurements related to UECNTX Modify (UeCntx.Mod.Cell).......................................................................1469
2.2.35.1 Number of UE Context Modification Attempts...............................................................................................1470
2.2.35.2 Number of Successful UE Context Modifications...........................................................................................1471
2.2.36 Measurement related to CA (CA.Cell)................................................................................................................1472
2.2.36.1 Total Number of Abnormal E-RAB Releases for CA UEs in a Cell................................................................1474
2.2.36.2 Total Number of Normal E-RAB Releases for CA UEs in a Cell....................................................................1476
2.2.36.3 Number of Handover Attempts for CA UEs in a Cell......................................................................................1479
2.2.36.4 Number of Handover Executions for CA UEs in a Cell...................................................................................1482
2.2.36.5 Number of Successful Handovers for CA UEs in a Cell..................................................................................1484
2.2.37 Measurement related to RLC (Traffic.RLC.Cell)................................................................................................1491
2.2.37.1 Number of Bits of Uplink RLC ARQ PDUs Retransmitted by UEs................................................................1493
2.2.37.2 Number of Bits of Downlink RLC ARQ PDUs Retransmitted by the eNodeB...............................................1494
2.2.37.3 Number of Received Uplink RLC ARQ PDUs................................................................................................1495
2.2.37.4 Number of Transmitted Downlink RLC ARQ PDUs.......................................................................................1495
2.2.37.5 Number of Received Uplink RLC ARQ PDUs Retransmitted by UEs............................................................1496
2.2.37.6 Number of Downlink RLC ARQ PDUs Retransmitted by UEs.......................................................................1497
2.2.37.7 Number of Downlink RLC PDUs Failed to Be Sent to UEs in AM Mode in a Cell.......................................1498
2.2.38 Measurement related to Reserve Cell (Reserve.Cell)..........................................................................................1499
2.2.38.1 L.Reserve.1.......................................................................................................................................................1506
2.2.38.2 L.Reserve.2.......................................................................................................................................................1506
2.2.38.3 L.Reserve.3.......................................................................................................................................................1507
2.2.38.4 L.Reserve.4.......................................................................................................................................................1508
2.2.38.5 L.Reserve.5.......................................................................................................................................................1508
2.2.38.6 L.Reserve.6.......................................................................................................................................................1509
2.2.38.7 L.Reserve.7.......................................................................................................................................................1510
2.2.38.8 L.Reserve.8.......................................................................................................................................................1511
2.2.38.9 L.Reserve.9.......................................................................................................................................................1511
2.2.38.10 L.Reserve.10...................................................................................................................................................1512
2.2.38.11 L.Reserve.11...................................................................................................................................................1513
2.2.38.12 L.Reserve.12...................................................................................................................................................1514
2.2.38.13 L.Reserve.13...................................................................................................................................................1514
2.2.38.14 L.Reserve.14...................................................................................................................................................1515
2.2.38.15 L.Reserve.15...................................................................................................................................................1516
2.2.38.16 L.Reserve.16...................................................................................................................................................1517
2.2.38.17 L.Reserve.17...................................................................................................................................................1517
2.2.38.18 L.Reserve.18...................................................................................................................................................1518
2.2.38.19 L.Reserve.19...................................................................................................................................................1519
2.2.38.20 L.Reserve.20...................................................................................................................................................1520
2.2.38.21 L.Reserve.21...................................................................................................................................................1520
2.2.38.22 L.Reserve.22...................................................................................................................................................1521
2.2.38.23 L.Reserve.23...................................................................................................................................................1522
2.2.38.24 L.Reserve.24...................................................................................................................................................1523
2.2.38.25 L.Reserve.25...................................................................................................................................................1523
2.2.38.26 L.Reserve.26...................................................................................................................................................1524
2.2.38.27 L.Reserve.27...................................................................................................................................................1525
2.2.38.28 L.Reserve.28...................................................................................................................................................1526
2.2.38.29 L.Reserve.29...................................................................................................................................................1526
2.2.38.30 L.Reserve.30...................................................................................................................................................1527
2.2.39 Measurement related to CellComb (CellComb.Cell)..........................................................................................1528
2.2.39.1 Number of Downlink Joint-scheduling UEs in a Combination Cell................................................................1530
2.2.39.2 Average Number of Work Physical Cells of Downlink Joint-scheduling UEs in a Combination Cell...........1531
2.2.39.3 Number of Times an Independent-scheduling UE Becomes a Joint-scheduling UE in Downlink in a Combination
Cell..................................................................................................................................................................................1532
2.2.39.4 Number of Times a Joint-scheduling UE Becomes an Independent-scheduling UE in Downlink in a Combination
Cell..................................................................................................................................................................................1533
2.2.39.5 Number of Times the Downlink Target Physical Cell of a UE in a Combination Cell Changes in a Combination
Cell..................................................................................................................................................................................1533
2.2.39.6 Number of Uplink Joint-scheduling UEs in a Combination Cell.....................................................................1534
2.2.39.7 Average Number of Work Physical Cells of Uplink Joint-scheduling UEs in a Combination Cell in a Combination
Cell..................................................................................................................................................................................1535
2.2.39.8 Number of Times an Independent-scheduling UE Becomes a Joint-scheduling UE in Uplink in a Combination
cell..................................................................................................................................................................................1536
2.2.39.9 Number of Times a Joint-scheduling UE Becomes an Independent-scheduling UE in Uplink in a Combination
Cell..................................................................................................................................................................................1537
2.2.39.10 Number of Times the Uplink Target Physical Cell of a UE in a Combination Cell Changes in a Combination
Cell..................................................................................................................................................................................1537
2.2.40 Measurement related to Measure Reports (ChMeas.MeasRpt.Cell)...................................................................1538
2.2.40.1 Number of Measurement Control Messages Sent by the eNodeB in a Cell.....................................................1539
2.2.41 Measurement related to UECNTX establish (UeCntx.Est.Cell).........................................................................1541
2.2.41.1 Number of UE Context Setup Attempts in a Cell............................................................................................1542
2.2.41.2 Number of Successful UE Context Setups in a Cell........................................................................................1544
2.6.2.5 Number of Abnormal E-RAB Releases for Different Causes for a specific operator in a cell..........................1745
2.6.2.6 Number of E-RAB Releases Initiated by the eNodeB Because of the S1 RESET for a Specific Operator
........................................................................................................................................................................................1748
2.6.3 Measurement related to Thruput for the Operator (Traffic.Thruput.Cell.Operator).............................................1754
2.6.3.1 Uplink Traffic Volume for PDCP SDUs for a specified operator......................................................................1769
2.6.3.2 Receive Duration of Uplink PDCP SDUs for a specific Operator in a Cell.......................................................1775
2.6.3.3 Downlink Traffic Volume for PDCP SDUs for a Specific Operator in a Cell...................................................1782
2.6.3.4 Transmit Duration of Downlink PDCP SDUs for a Specific Operator in a Cell...............................................1789
2.6.3.5 Downlink Traffic Volume Sent in the Last TTI Before the Buffer Is empty for a Specific Operator...............1796
2.6.3.6 Data Transmit Duration Except the Last TTI Before the Downlink Buffer Is Empty for a Specific Operator
........................................................................................................................................................................................1803
2.6.3.7 Traffic Volume of Uplink PDCP SDUs Sent in the Last TTI Before the UE Buffer is Empty for a Specific Operator
........................................................................................................................................................................................1810
2.6.3.8 Uplink Data Transmit Duration Except the Last TTI Before the UE Buffer is Empty for a Specific Operator
........................................................................................................................................................................................1811
2.6.3.9 Uplink Traffic Volume of PDCP SDUs Scheduled for Small Packets for a Specific Operator.........................1813
2.6.3.10 Uplink Data Transmission Duration Except that for Small Packets for a Specific Operator...........................1814
2.6.4 Measurement related to the number of User for the Operator (Traffic.User.Cell.Operator).................................1815
2.6.4.1 Number of Users for a Specific Operator in a Cell............................................................................................1816
2.6.5 Measurement related to the RB number for the Operator (Traffic.RB.Cell.Operator).........................................1818
2.6.5.1 Average Number of PDSCH PRBs Used by a Specific Operator......................................................................1819
2.6.5.2 Average Number of PUSCH PRBs Used by a Specific Operator......................................................................1821
2.6.6 Measurement related to Intra eRan HOOUT for the operator (HO.eRAN.Out.Cell.Operator)............................1823
2.6.6.1 Number of Intra-eNodeB Outgoing Handover Attempts for a Specific Operator..............................................1830
2.6.6.2 Number of Intra-eNodeB Outgoing Handover Executions for a Specific Operator..........................................1832
2.6.6.3 Number of Successful Intra-eNodeB Outgoing Handovers for a Specific Operator..........................................1834
2.6.6.4 Number of Inter-eNodeB Outgoing Handover Attempts for a specified operator.............................................1837
2.6.6.5 Number of Performed Inter-eNodeB Outgoing Handovers for a specified operator.........................................1840
2.6.6.6 Number of Successful Inter-eNodeB Outgoing Handovers for a specified operator.........................................1843
2.6.6.7 Number of X2-based Outgoing Handover Attempts for a Specific Operator....................................................1850
2.6.6.8 Number of X2-based Outgoing Handover Executions for a Specific Operator.................................................1853
2.6.6.9 Number of Successful X2-based Outgoing Handovers for a specific operator..................................................1856
2.6.6.10 Number of Outgoing Blind Handover Attempts for a Specific Operator.........................................................1860
2.6.6.11 Number of Outgoing Blind Handover Executions for a Specific Operator......................................................1863
2.6.6.12 Number of Successful Outgoing Blind Handovers for a Specific Operator.....................................................1866
2.6.7 Measurement related to IRATHOOUT for the operator (HO.IRAT.Out.Cell.Operator)......................................1872
2.6.7.1 Number of Inter-RAT Handover Attempts from E-UTRAN to WCDMA Network for a Specific Operator
........................................................................................................................................................................................1876
2.6.7.2 Number of Inter-RAT Handover Executions from E-UTRAN to WCDMA Network for a Specific Operator
........................................................................................................................................................................................1878
2.6.7.3 Number of Successful Inter-RAT Handovers from E-UTRAN to WCDMA Network for a Specific Operator
........................................................................................................................................................................................1880
2.6.7.4 Number of Inter-RAT Handover Attempts from E-UTRAN to GERAN for a Specific Operator.....................1882
2.6.7.5 Number of Inter-RAT Handover Executions from E-UTRAN to GERAN for a Specific Operator.................1884
2.6.7.6 Number of Successful Inter-RAT Handovers from E-UTRAN to GERAN for a Specific Operator.................1886
2.6.7.7 Number of Inter-RAT Blind Handover Attempts from E-UTRAN to Another System for a Specific Operator
........................................................................................................................................................................................1888
2.6.7.8 Number of Inter-RAT Blind Handover Executions from E-UTRAN to Another System for a Specific Operator
........................................................................................................................................................................................1891
2.6.7.9 Number of Successful Inter-RAT Blind Handovers from E-UTRAN to Another System for a Specific Operator
........................................................................................................................................................................................1894
2.6.8 Measurement related to Thruput Distribution for the Operator (Traffic.Thruput.PDF.Cell.Operator).................1897
2.6.8.1 Distribution of the Downlink Throughput in a Cell for a Specific Operator......................................................1920
2.6.8.2 Distribution of the Uplink Throughput in a Cell for a Specific Operator..........................................................1990
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The ETHPORT function subset measures the traffic volumes at the data link layer on an Ethernet
port, helping users to plan network. Figure 1-1 shows the position of the Ethernet port in the
TCP/IP model.
Figure 1-1
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters provide the number of bytes in the packets successfully transmitted and the
number of bytes in the packets successfully received on an Ethernet port within a measurement
period, respectively. They reflect the traffic on the Ethernet port at the data link layer. The counter
value includes the number of bytes in the MAC header, VLAN flag, payload, and CRC field
that is at the end of a packet.
Measurement Points
The number of bytes in the packets successfully transmitted or successfully received on the
Ethernet port is sampled per second. At the end of a measurement period, the sum of these
sampling results is used as the value of the corresponding counter.
Formula
None
Unit
byte
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters provide the number of transmitted packets, received packets, or error packets on
an Ethernet port within a measurement period. They reflect the traffic on and the transmission
quality of the Ethernet port at the data link layer. The FEGE.RxErrPackets counter provides the
number of error packets received on physical links and failed in CRC checks.
Measurement Points
The number of transmitted packets, received packets, or error packets is sampled per second. At
the end of a measurement period, the sum of these sampling results is used as the value of the
corresponding counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the transmit rate and the receive rate on the Ethernet port within a
measurement period. They indicate the traffic on the Ethernet port at the data link layer.
Measurement Points
The transmit rate or the receive rate on the Ethernet port is sampled per second. At the end of a
measurement period, the maximum, minimum, or average of these sampling results is used as
the value of the corresponding counter.
Formula
None
Unit
bit/s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters provide total transmit and receive bandwidth in Ethernet in the current
measurement period, reflecting the ETH bandwidth.
Measurement Points
Available bandwidth in the transmit and receive directions of the Ethernet per second. At the
end of a measurement period, the average of these sampling results is used as the value of the
corresponding counter.
Formula
None
Unit
kbit/s
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Figure 1-2
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of code type errors on the E1/T1 electrical port within a
measurement period. A code type error occurs if the line coding modes at two communicating
E1/T1 electrical ports mismatch.
Measurement Points
The number of code type errors on the E1/T1 electrical port is sampled per second. At the end
of a measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.2.1.2 Number of Base Frame Alignment Errors on the E1/T1 Electrical Port
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of base frame alignment errors on the E1/T1 electrical port
within a measurement period. A base frame alignment error prohibits the precise location of
frames.
Measurement Points
The number of base frame alignment errors on the E1/T1 electrical port is sampled per second.
At the end of a measurement period, the sum of these sampling results is used as the value of
the counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of CRC errors on the E1/T1 electrical port within a
measurement period. This counter is relevant only for CRC multiframes (E1) or extended
superframes (T1).
Measurement Points
The measurement is performed per second to count the number of CRC errors on the E1/T1
electrical port, and the sum of these sampling results is calculated as the result of the
corresponding counter at the end of a measurement period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of Ebit errors, that is the number of cyclic redundancy check
(CRC) failures reported by the peer end, within a measurement period. The counter measures
the number of Ebit errors for CRC multi-frames (E1) or extended super-frames (T1).
Measurement Points
The number of Ebit errors on the E1/T1 port is sampled per second. At the end of a measurement
period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of Sa6 errors on the E1 port within a measurement period.
This counter is relevant only for CRC multiframes (E1 port).
Measurement Points
The measurement is performed per second to count the number of Sa6 errors on the E1 port, and
the sum of these sampling results is calculated as the result of the corresponding counter at the
end of a measurement period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of multiframe cycles on the E1/T1 electrical port within a
measurement period.
Measurement Points
The measurement is performed per second to count the number of multiframe cycles on the E1/
T1 electrical port, and the sum of these sampling results is calculated as the result of the
corresponding counter at the end of a measurement period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of times that frames are not aligned within a measurement
period. It indicates the multiframe variable. This counter is relevant only for CRC multiframes
(E1) or extended superframes (T1).
Measurement Points
The measurement is performed per second to count the number of times that frames are not
aligned on the E1/T1 electrical port. Every time the multi-frames (E1) or extended super-frames
(T1) change, the counter increases by one.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter provides the total error seconds in the TX direction on an E1/T1 link. It reflects the
quality on the E1/T1 link. A second is considered an error second in the TX direction if an e-bit
error occurs or an RDI alarm is generated in this second.
Measurement Points
This counter is sampled per second in the TX direction. This counter is increased by one each
time a second is considered as a errored second.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter provides the total severely errored seconds (SESs) in the TX direction on an E1/
T1 link. It reflects the quality on the E1/T1 link. A second is considered a severe error bit second
in the TX direction if the e-bit error rate is larger than 30% or an RDI alarm is generated in this
second.
Measurement Points
This counter is sampled per second in the TX direction. This counter is increased by one each
time a second is considered as a severely errored second.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter provides the total severely errored seconds (SESs) in the TX direction on an E1/
T1 link. If there are more than 10 consecutive seconds with severe bit errors, these seconds are
considered as SESs.
Measurement Points
This counter is sampled per second in the TX direction.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter provides the total errored seconds in the RX direction on an E1/T1 link. It reflects
the quality on the E1/T1 link. A second is considered an error second in the RX direction if an
error occurs or an LOS/AIS/LOF alarm is generated in this second.
Measurement Points
This counter is sampled per second in the RX direction. This counter is increased by one each
time a second is considered as a errored second.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter provides the total severely errored seconds (SESs) in the RX direction on an E1/
T1 link. It reflects the quality on the E1/T1 link. A second is considered a severe error bit second
in the RX direction if the bit error rate is larger than 30% or an LOS/AIS/LOF alarm is generated
in this second.
Measurement Points
This counter is sampled per second in the RX direction. This counter is increased by one each
time a second is considered as a severely errored second.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter provides the total severely errored seconds (SESs) in the RX direction on an E1/
T1 link. If there are more than 10 consecutive seconds with severe bit errors, these seconds are
considered as SESs.
Measurement Points
This counter is sampled per second in the RX direction.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The DataLink.PPP function subset measures the number of packets transmitted on the PPP link
of the base station and evaluates the information about the rates, for example, the number of
received packets, the number of transmitted packets, and the rate. It represents the traffic volume
and quality of services carried by the PPP link. Figure 1-3 shows the position of the PPP link
in the TCP/IP model.
Figure 1-3
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The following table describes the meanings of each counter.
Measurement Points
Number of successfully transmitted packets, packets discarded by the transmit direction,
successfully received packets, and packets discarded by the receive direction on the PPP link
per second. At the end of a measurement period, the sum of these sampling results is used as the
value of the corresponding counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The following table describes the meanings of each counter.
Measurement Points
Number of bytes successfully transmitted and received on the PPP link per second. At the end
of a measurement period, the sum of these sampling results is used as the value of the
corresponding counter.
Formula
None
Unit
byte
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The following table describes the meanings of each counter.
Measurement Points
Number of bytes transmitted and received on the PPP link per second. At the end of a
measurement period, the maximum, minimum, and average sampling results are reported.
Formula
None
Unit
bit/s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The following table describes the meanings of each counter.
Measurement Points
Available bandwidth in the transmit and receive directions of the PPP link per second. At the
end of a measurement period, the average of these sampling results is used as the value of the
corresponding counter.
Formula
None
Unit
kbit/s
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The MPGRP function subset measures traffic volumes of the services carried by the MPGRP
links and the service quality. Figure 1-4 shows the position of the MP group in the TCP/IP
model.
Figure 1-4
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The following table describes the meanings of each counter.
Measurement Points
Number of successfully transmitted packets, packets discarded by the transmit direction,
successfully received packets, and packets discarded by the receive direction by the MP group
is sampled per second. At the end of a measurement period, the average of these sampling results
is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The following table describes the meanings of each counter.
Measurement Points
Number of bytes successfully transmitted and received by the MP group is sampled per second.
At the end of a measurement period, the sum of these sampling results is used as the value of
the counter.
Formula
None
Unit
byte
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The following table describes the meanings of each counter.
Measurement Points
The number of bytes transmitted and received by the MP group is sampled per second. At the
end of a measurement period, the maximum, minimum, and average sampling results are
reported.
Formula
None
Unit
bit/s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The following table describes the meanings of each counter.
Measurement Points
Available bandwidth in the transmit and receive directions on the MP group per second. At the
end of a measurement period, the average of these sampling results is used as the value of the
corresponding counter.
Formula
None
Unit
kbit/s
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The Network.IP function subset measures the IP packet traffic, such as the number of
successfully transmitted or received IP packets or the number of bytes in the transmitted or
received IP packets. It represents the traffic volume and quality of services at the IP layer. Figure
1-5 shows the position of the IP layer in the TCP/IP model.
Figure 1-5
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of IP packets successfully transmitted, successfully
received, or discarded within a measurement period. They indicate the traffic on and the
processing capability of the base station at the network layer.
Measurement Points
The number of IP packets successfully transmitted, successfully received, or discarded is
sampled per second. At the end of a measurement period, the sum of these sampling results is
used as the value of the corresponding counter.
The VS.IP.TxPackets counter measures the number of IP packets successfully transmitted when
the routing table and ARP table are found successfully. The counter is incremented after
fragment.
The VS.IP.RxPackets counter measures the number of IP packets successfully received from
the data link layer. This counter is incremented before reassembly.
The VS.IP.TxDropPkts counter measures the number of transmitted IP packets discarded. It is
incremented in any of the following conditions: (1) The forward information base (FIB) fails to
be found. (2) The address of the FIB table is invalid. (3) The FIB table is invalid. (4) During the
configuration of the routing load sharing, the configuration is incorrect or the routing table is
invalid.
The VS.IP.RxDropPkts counter measures the number of received IP packets discarded. It is
incremented in any of the following conditions: (1) The IP header check fails. (2) Packet
reassembly fails. (3) Broadcast packets are discarded when the access control list (ACL) filtering
function is enabled.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of bytes in the successfully transmitted, successfully
received, or discarded IP packets within a measurement period. They indicate the traffic and the
processing capability of the base station at the network layer.
Measurement Points
The number of bytes in the successfully transmitted, successfully received, or discarded IP
packets is sampled per second. At the end of a measurement period, the sum of these sampling
results is used as the value of the corresponding counter.
The VS.IP.TxBytes counter measures the number of bytes in the IP packets successfully
transmitted when the routing table and ARP table are found successfully. It includes the IP header
and payload (or IPSec-related payload such as AH header and ESP header in IPSec scenarios).
If packets need to be fragmented, this counter is incremented after fragment.
The VS.IP.RxBytes counter measures the number of bytes in the IP packets successfully received
from the data link layer. It includes the IP header and payload (or IPSec-related payload such
as AH header and ESP header in IPSec scenarios). If packets are fragmented, this counter is
incremented before packet reassembly.
The VS.IP.TxDropBytes counter is incremented in any of the following conditions: (1) The
forward information base (FIB) fails to be found. (2) The address of the FIB table is invalid. (3)
The FIB table is invalid. (4) During the configuration of the routing load sharing, the
configuration is incorrect or the routing table is invalid.
The VS.IP.RxDropBytes counter is incremented in any of the following conditions: (1) The IP
header check fails. (2) Packet reassembly fails. (3) Broadcast packets are discarded when the
access control list (ACL) filtering function is enabled.
Formula
None
Unit
byte
Related Features
Counter Name Feature ID Feature Name
on the transmission board. It represents the traffic volume of the packets that follow the General
Packet Radio Service Tunneling Protocol for User Plane (GTP-U). It provides a fine-grained
flow monitoring mechanism, which facilitates the user-data based Qos management.
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The IP Path function subset provides the measurements on an IP path in the base station. It
measures the traffic volumes of services carried by an IP path and the service quality at a smaller
granularity, and supports QoS management based on the traffic volumes. Figure 1-6 shows the
position of the IP path in the TCP/IP model.
Figure 1-6
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of IP packets successfully transmitted and received on an
IP path within a measurement period, respectively. They indicate the real-time service traffic at
the IP layer on the IP path. Real-time services include voice services, video on demand (real-
time streams), and real-time games. Real-time service data is generally the UDP-based stream
media data.
Measurement Points
The number of real-time service packets transmitted or received on the IP path is sampled per
second. At the end of a measurement period, the sum of these sampling results is used as the
value of the corresponding counter.
Formula
None
Unit
packet
Related Features
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of bytes in the IP packets successfully transmitted and
received on an IP path within a measurement period, respectively. They indicate the real-time
service traffic at the IP layer on the IP path. Real-time services include voice services, video on
demand (real-time streams), and real-time games. Real-time service data is generally the UDP-
based stream media data.
Measurement Points
The number of bytes in the real-time service packets successfully transmitted or successfully
received on the IP path is sampled per second. At the end of a measurement period, the sum of
these sampling results is used as the value of the corresponding counter.
In IPSec scenarios, the IPPath.RxRtBytes counter measures the number of bytes in the decrypted
IP packets successfully received after reassembly, and the IPPath.TxRtBytes counter measures
the number of bytes in the encrypted IP packets successfully transmitted before fragment.
In non-IPSec scenarios, the IPPath.RxRtBytes counter measures the number of bytes in the IP
packets successfully received after reassembly, and the IPPath.TxRtBytes counter measures the
number of bytes in the IP packets successfully transmitted before fragment.
Formula
None
Unit
byte
Related Features
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of IP packets successfully transmitted and received on an
IP path within a measurement period, respectively. They indicate the non-real-time service traffic
at the IP layer on the IP path. Non-real-time services include video on demand (that is, buffer
streams), interactive games, and TCP-based data streams.
Measurement Points
The number of non-real-time service packets transmitted or received on the IP path is sampled
per second. At the end of a measurement period, the sum of these sampling results is used as the
value of the corresponding counter.
The measurement is triggered in the following conditions:
(1) IP path performance measurement is enabled.
(2) Non-real-time services are provided.
Formula
None
Unit
packet
Related Features
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of bytes in the IP packets successfully transmitted and
received on an IP path within a measurement period, respectively. They indicate the non-real-
time service traffic at the IP layer on the IP path. Non-real-time services include video on demand
(that is, buffer streams), interactive games, and TCP-based data streams.
Measurement Points
The number of bytes in the non-real-time service packets successfully transmitted or successfully
received on the IP path is sampled per second. At the end of a measurement period, the sum of
these sampling results is used as the value of the corresponding counter.
In IPSec scenarios, the IPPath.RxNrtBytes counter measures the number of bytes in the
decrypted IP packets successfully received after reassembly, and the IPPath.TxNrtBytes counter
measures the number of bytes in the encrypted IP packets successfully transmitted before
fragment.
In non-IPSec scenarios, the IPPath.RxNrtBytes counter measures the number of bytes in the IP
packets successfully received after reassembly, and the IPPath.TxNrtBytes counter measures
the number of bytes in the IP packets successfully transmitted before fragment.
Formula
None
Unit
byte
Related Features
None
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The resource group of an base station is a set of data streams. The data streams can be related
to control plane services, user plane services, OM services, IP clock services, or bypass services
(regardless of control plane services or user plane services). The transmission quality affects the
services of the base station. The base station manages bandwidths based on resource groups.
The base station can configure the bandwidth, flow shaping, admission control, and flow control
for the resource group. Multiple resource groups can be configured on one physical link, the
bandwidth of which is shared among these resource groups. Multiple transport-layer bearers can
be configured for one resource group, the configured bandwidth of which is shared among these
bearers. The Transport.RscGroup function subset measures the number of bytes or packets
transmitted by the resource group of the base station. It represents the service processing
capability of the resource group. Figure 1-7 shows the position of the resource group in the TCP/
IP model. The Transport.RscGroup function subset measures only the data transmitted from a
resource group.The counters of function subset Transport.RscGourp report valid values in IP
transmission, and reports zero in ATM transmission.
Figure 1-7
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of bytes in the packets transmitted by all the queues of a
resource group at the data link layer within a measurement period and the number of bytes in
the packets discarded due to congestion in the queues within a measurement period. They
represent the transmit traffic on the resource group at the data link layer. If the resource group
is carried on an Ethernet port, the counters measure the MAC headers and payloads in the packets.
If the resource group is carried on a port carrying a PPP link or MP link, the counters measure
the data parts of the PPP frames or MP frames. The measurement of the counters remains
unchanged in packet fragment or IPSec scenarios.
Measurement Points
Number of transmitted bytes and discarded bytes in the resource group per second. At the end
of a measurement period, the sum of these sampling results is used as the value of the
corresponding counter.
Formula
None
Unit
byte
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of IP packets transmitted by all the queues of a resource
group at the data link layer within a measurement period and the number of packets discarded
due to congestion in the queues within a measurement period. They represent the transmit traffic
on the resource group at the data link layer.
Measurement Points
Number of transmitted and discarded packets in the resource group per second. At the end of a
measurement period, the sum of these sampling results is used as the value of the corresponding
counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the transmit rate of a resource group within a measurement period. They
represent the transmission rate of the resource group. If the resource group is carried on an
Ethernet port, the counters measure the MAC headers and payloads. If the resource group is
carried on the PPP or MP group port, the counters measure the information part of the PPP frame
or MP frame.
Measurement Points
The transmit rate of the resource group is sampled per second. At the end of a measurement
period, the maximum, minimum, or average of these sampling results is used as the value of the
corresponding counter.
Formula
None
Unit
bit/s
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The IP PM function subset provides the measurements on an IP PM in the base station. It
measures the quality of traffic carried on the transmission boards. Figure 1-8 shows the position
of the IP PM in the TCP/IP model. Figure 1-9 shows the principles of the IP PM. The IP PM
checks the packet loss, delay, and jitter condition of a link by the local end transmitting forward
monitoring (FM) frames and the peer end responding with backward reporting (BR) frames. The
number of FM frames is used to represent the number of frames transmitted by the local end,
whereas that of BR frames is used to represent the number of frames received by the peer end.
The local end calculates the delay, jitter, and packet loss rate along the local-to-peer direction
based on the received BR frames. Ultimately, the bandwidth condition is obtained.
Figure 1-8
Figure 1-9
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters provide transmit byte rates and receive byte rates of the transport network on the
IP performance monitor (IP PM) within a measurement period. They indicate the transmission
capability of the transport network.
Measurement Points
The transmit byte rate or receive byte rate at the local or peer end is sampled per second on the
IP PM. At the end of a measurement period, the average or maximum of these sampling results
is used as the value of the corresponding counter.
Formula
None
Unit
bit/s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters provide transmit packet rates and receive packet rates of the transport network
on the IP performance monitor (IP PM) within a measurement period. They indicate the
transmission capability of the transport network.
Measurement Points
The transmit packet rate or receive packet rate at the local or peer end is sampled per second on
the IP PM. At the end of a measurement period, the average or maximum of these sampling
results is used as the value of the corresponding counter.
Formula
None
Unit
packet/s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters provide packet loss rate on the transport network by using the IP performance
monitor (IP PM) within a measurement period. They reflect the quality on the detected IP path.
Measurement Points
The number of forward packets transmitted and the number of forward packets lost over the link
are sampled and accumulated every second, respectively. The packet loss rate in a second is
obtained by dividing the number of forward packets lost in one second by the number of forward
packets transmitted in one second. At the end of the measurement period, the maximum packet
loss rate is the maximum one among all the packet loss rates in the measurement period, and the
average packet loss rate is obtained by dividing the total number of lost forward packets by the
total number of forward packets transmitted in the measurement period.
Formula
(([VS.IPPM.Local.TxPkts]-[VS.IPPM.Peer.RxPkts])/[VS.IPPM.Local.TxPkts])*{100}
Unit
%
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters provide the standard delay deviation of the round trip time (RTT) for the IP PM
packets on the transport network within a measurement period. They reflect the stabilization of
the transmission delay of a detected data flow. A larger counter value reflects a larger fluctuation
in transmission delay. The forward delay variation represents the delay variation in the RTT of
IP PM packets from the local end to the peer end. The backward delay variation represents the
delay variation in the RTT of IP PM packets from the peer end to the local end.
Measurement Points
A sample is taken every 1 second to obtain the forward jitter and backward jitter of the IP PM
for calculating the forward jitter standard deviation and backward jitter standard deviation at the
end of a measurement period based on the standard deviation formula.
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters provide the latency of the round trip time (RTT) for the IP PM packets on the
transport network within a measurement period. They reflect the time delay on the transport
network.
Measurement Points
The RTT is sampled and calculated by the IP PM mechanism every second.
After forward activation is performed for an IP PM link, the local end sends FM frames and
receives BR frames periodically.
The value of the VS.IPPM.Rtt.Means counter can be calculated in the following formula:
VS.IPPM.Rtt.Means counter = Total delay of FM and BR frames/Total number of transmitted
FM frames.
The maximum delay of the sampling delays of FM frames and BR frames is used as the value
of the VS.IPPM.MaxRttDelay counter.
The minimum delay of the sampling delays of FM frames and BR frames is used as the value
of the VS.IPPM.MinRttDelay counter.
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters provide the number of packets sent by the local end of an IP PM session and the
number of packets received by the peer end of an IP PM session. They reflect the service traffic
volume on IP paths measured by IP PM.
Measurement Points
The base station takes samples of the number of packets sent by the local end of an IP PM session
and the number of packets received by the peer end of an IP PM session every measurement
period of 1 second. At the end of each measurement period, the base station adds up all sampled
values to obtain the value of the corresponding counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The SCTP function subset measures the traffic volumes of IP packets transmitted and received
on an SCTP link inside the base station. It measures traffic volumes of the signaling services
carried on base station transmission boards and the service quality. Figure 1-10 shows the
position of the SCTP layer in the TCP/IP model.
Figure 1-10
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters provide the number of bytes in the packets received from or transmitted to the
IP layer on an SCTP link within a measurement period. They reflect the traffic of signaling
services. The counter VS.Sctp.RxDropBytes is not supported currently and the value of the
counter is always 0.
Measurement Points
The number of bytes in the IP packets successfully transmitted or successfully received on the
SCTP link is sampled per second. At the end of a measurement period, the sum of these sampling
results is used as the value of the corresponding counter. The counter value includes the number
of bytes in user data (the data field of a user data packet, excluding the MAC header, IP header,
and SCTP header). This counter excludes the number of bytes in the following SCTP
management messages: Heartbeat messages, Link establishment messages, Link disconnection
messages, Handshake messages.
Formula
None
Unit
byte
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters provide the number of packets received from or transmitted to the IP layer on
an SCTP link within a measurement period. They reflect the traffic of signaling services. IP
packets with any of the following errors are discarded on the SCTP link: parsing error, block
type error, and association query failure.
The counter 1542455424 VS.Sctp.RxPkts will be replaced with the VS.SctpLnk.RxPkts counter
in a later version. In the current version, either this counter or the VS.SctpLnk.RxPkts counter
is used, or they can both be used. The reported value of this counter may be normal or invalid,
and therefore this counter is not recommended for used. In later versions, only the
VS.SctpLnk.RxPkts is used.
The counter 1542455425 VS.Sctp.TxPkts will be replaced with the VS.SctpLnk.TxPkts counter
in a later version. In the current version, either this counter or the VS.SctpLnk.TxPkts counter
is used, or they can both be used. The reported value of this counter may be normal or invalid,
and therefore this counter is not recommended for used. In later versions, only the
VS.SctpLnk.TxPkts counter is used.
Measurement Points
The number of IP packets successfully transmitted, successfully received, or discarded on the
SCTP link is sampled per second. At the end of a measurement period, the sum of these sampling
results is used as the value of the corresponding counter. The counter value includes the number
of all the packets transmitted and received over an SCTP link. The packets include SCTP
management messages, such as heartbeat messages, link establishment messages, link
disconnection messages, and handshake messages. However, the received packets on an SCTP
link are not measured in any of the following cases: (1) The SCTP link is not configured. (2)
There is no signaling bearer at the upper layer of the SCTP link. (3) The SCTP link is blocked.
The VS.Sctp.RxPkts counter provides the number of IP packets received on the SCTP link.
The VS.Sctp.RxDropPkts counter provides the number of discarded IP packets received on the
SCTP link. An IP packet is discarded when any of the following occurs: (1) The chunk length
is incorrect in the packet. (2) The chunktype length is incorrect and the highest two bits are 10
in the packet. (3) The binding function of the packet is abnormal. For example, the DATA chunk
and ABORT chunk are in the same packet. (4) The packet can be parsed but an exception occurs
during the data check. For example, the V-tag is incorrect.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters provide the maximum rate, minimum rate, and average rate for transmitting or
receiving packets received from or transmitted to the IP layer on an SCTP link within a
measurement period. These rates are calculated on a per-byte basis. They reflect the transmission
capability on the SCTP link.
The counter 1542455430 VS.Sctp.RxMaxSpeed will be replaced with the
VS.SctpLnk.RxMaxSpeed counter in a later version. In the current version, either this counter
or the VS.SctpLnk.RxMaxSpeed counter is used, or they can both be used. The reported value
of this counter may be normal or invalid, and therefore this counter is not recommended for
used. In later versions, only the VS.SctpLnk.RxMaxSpeed is used.
The counter 1542455431 VS.Sctp.RxMinSpeed will be replaced with the
VS.SctpLnk.RxMinSpeed counter in a later version. In the current version, either this counter
or the VS.SctpLnk.RxMinSpeed is used, or they can both be used. The reported value of this
counter may be normal or invalid, and therefore this counter is not recommended for used. In
later versions, only the VS.SctpLnk.RxMinSpeed counter is used.
The counter 1542455432 VS.Sctp.RxMeanSpeed will be replaced with the
VS.SctpLnk.RxMeanSpeed counter in a later version. In the current version, either this counter
or the VS.SctpLnk.RxMeanSpeed is used, or they can both be used. The reported value of this
counter may be normal or invalid, and therefore this counter is not recommended for used. In
later versions, only the VS.SctpLnk.RxMeanSpeed counter is used.
Measurement Points
The transmit rate or the receive rate on the SCTP link is sampled per second. At the end of a
measurement period, the maximum, minimum, or average of these sampling results is used as
the value of the corresponding counter.
Formula
None
Unit
bit/s
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
transmitted or received IPv6 packets. It represents the throughput of IPv6 packets on the
transmission board in the base station. Figure 1-11 shows the position of the IPv6 in the TCP/
IP model.
Figure 1-11
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of IPv6 packets successfully transmitted, successfully
received, or discarded within a measurement period. They indicate the traffic on and the
processing capability of the base station at the network layer.
Measurement Points
Number of successfully transmitted packets, discarded packets due to transmission failures,
successfully received packets, and discarded packets due to receive failures on the IPv6 path per
second. At the end of a measurement period, the sum of these sampling results is used as the
value of the corresponding counter. If packets need to be fragmented, the number of TX packets
is measured after the packets are fragmented and the number of RX packets is measured before
the packets are reassembled.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of bytes in the successfully transmitted, successfully
received, or discarded IPv6 packets within a measurement period. They indicate the traffic and
the processing capability of the base station at the network layer.
Measurement Points
Number of successfully transmitted bytes, discarded bytes due to transmission failures,
successfully received bytes, and discarded bytes due to receive failures on the IPv6 path per
second. At the end of a measurement period, the sum of these sampling results is used as the
value of the corresponding counter. If packets need to be fragmented, the number of TX bytes
is measured after the packets are fragmented and the number of RX bytes is measured before
the packets are reassembled.
Formula
None
Unit
byte
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The Transport.IPv6Path function subset measures the traffic volumes of real-time or non-real-
time services on the IPv6 path, such as the number of successfully received, successfully
transmitted, or discarded packets. It represents the traffic volumes of the services carried by the
IPv6 path on the transmission board in the base station and the service quality. Figure 1-12
shows the position of the IPv6Path in the TCP/IP model.
Figure 1-12
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of IP packets successfully transmitted and received on an
IPv6Path within a measurement period, respectively. They indicate the real-time service traffic
at the IP layer on the IPv6Path. Real-time services include voice services, video on demand
(real-time streams), and real-time games. Real-time service data is generally the UDP-based
stream media data.
Measurement Points
The number of real-time service packets that are successfully transmitted or received on the IPv6
path is sampled per second. At the end of a measurement period, the sum of these sampling
results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.11.1.2 Number of Bytes in the Real-Time Service Packets on the IPv6 Path
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of bytes in the IP packets successfully transmitted and
received on an IPv6Path within a measurement period, respectively. They indicate the real-time
service traffic at the IP layer on the IPv6Path. Real-time services include voice services, video
on demand (real-time streams), and real-time games. Real-time service data is generally the
UDP-based stream media data.
Measurement Points
The number of bytes in the real-time service packets that are successfully transmitted or received
on the IPv6 path is sampled per second. At the end of a measurement period, the sum of these
sampling results is used as the value of the counter.
In IPSec scenarios, the IPv6Path.RxRtBytes counter measures the number of bytes in the
decrypted IP packets successfully received after reassembly, and the IPv6Path.TxRtBytes
counter measures the number of bytes in the encrypted IP packets successfully transmitted before
fragment.
In non-IPSec scenarios, the IPv6Path.RxRtBytes counter measures the number of bytes in the
IP packets successfully received after reassembly, and the IPv6Path.TxRtBytes counter
measures the number of bytes in the IP packets successfully transmitted before fragment.
Formula
None
Unit
byte
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of IP packets successfully transmitted and received on an
IPv6Path within a measurement period, respectively. They indicate the non-real-time service
traffic at the IP layer on the IPv6Path. Non-real-time services include video on demand (that is,
buffer streams), interactive games, and TCP-based data streams.
Measurement Points
The number of non-real-time service packets that are successfully transmitted or received on the
IPv6 path is sampled per second. At the end of a measurement period, the sum of these sampling
results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.11.1.4 Number of Bytes in the Non-Real-Time Service Packets on the IPv6 Path
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of bytes in the IP packets successfully transmitted and
received on an IPv6Path within a measurement period, respectively. They indicate the non-real-
time service traffic at the IP layer on the IPv6Path. Non-real-time services include video on
demand (that is, buffer streams), interactive games, and TCP-based data streams.
Measurement Points
The number of bytes in the non-real-time service packets that are successfully transmitted or
received on the IPv6 path is sampled per second. At the end of a measurement period, the sum
of these sampling results is used as the value of the counter.
In IPSec scenarios, the IPv6Path.RxNrtBytes counter measures the number of bytes in the
decrypted IP packets successfully received after reassembly, and the IPv6Path.TxNrtBytes
counter measures the number of bytes in the encrypted IP packets successfully transmitted before
fragment.
In non-IPSec scenarios, the IPv6Path.RxNrtBytes counter measures the number of bytes in the
IP packets successfully received after reassembly, and the IPv6Path.TxNrtBytes counter
measures the number of bytes in the IP packets successfully transmitted before fragment.
Formula
None
Unit
byte
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The OMCH function subset provides the measurements on an OM channel in the base station.
It measures traffic volumes of the services carried on the OM channel in the base station and the
service quality. The OM channel uses TCP packets for transmission. Figure 1-13 shows the
position of the OM channel in the TCP/IP model.
Figure 1-13
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the total number of TCP packets received on the OM channel within a
measurement period. It represents the traffic on the OM channel.
Measurement Points
The number of packets received on the OM channel is sampled per second. At the end of a
measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.12.1.2 VS.OMCH.RxInSeqPkts
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of in-order TCP packets with lengths of non-zero received
on the OM channel within a measurement period. It represents the quality of the OM channel.
Measurement Points
The number of in-order packets received on the OM channel is sampled per second. At the end
of a measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.12.1.3 VS.OMCH.RxWndProbePkts
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the total number of window probe packets received on the OM channel
within a measurement period. It represents the traffic on the OM channel. After the local end
informs the peer end that the receiving window size is zero, the peer end periodically sends
window probe packets to check the size of the receiving window at the local end.
Measurement Points
The number of window probe packets received on the OM channel is sampled per second. At
the end of a measurement period, the sum of these sampling results is used as the value of the
counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.12.1.4 VS.OMCH.RxWndUpdatePkts
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of the window size update packets received on the OM
channel within a measurement period. The peer end transmits such a packet when the peer end
receives a probe packet from the local end or when the window size at the peer end changes.
This counter represents the quality of the OM channel.
Measurement Points
The number of the window size update packets received on the OM channel is sampled per
second. At the end of a measurement period, the sum of these sampling results is used as the
value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.12.1.5 VS.OMCH.RxDupPkts
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of fully duplicated ACKs received on the OM channel within
a measurement period. It represents the quality of the OM channel. Two packets are fully
duplicated if they have the same sequence number and the same data. This counter indicates the
channel quality and the receive capability of the transmitter.
Measurement Points
The number of fully duplicated packets received on the OM channel is sampled per second. At
the end of a measurement period, the sum of these sampling results is used as the value of the
counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.12.1.6 VS.OMCH.RxPartDupPkts
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of partially duplicated packets received on the OM channel
within a measurement period. It represents the quality of the OM channel. Two packets are
partially duplicated if they have the same data. This counter indicates the channel quality and
the receive capability of the transmitter.
Measurement Points
The number of partially duplicated packets received on the OM channel is sampled per second.
At the end of a measurement period, the sum of these sampling results is used as the value of
the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.12.1.7 VS.OMCH.RxOutOfOrderPkts
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of out-of-order packets received on the OM channel within
a measurement period. It represents the quality of the OM channel.
Measurement Points
The number of out-of-order packets received on the OM channel is sampled per second. At the
end of a measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.12.1.8 VS.OMCH.RxAfterWndPkts
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of packets beyond the receive window of the OM channel
within the measurement period. A packet falls beyond the receive window of the OM channel
when its size is larger than the receive capacity of the receive window. This counter indicates
the quality of service of the OM channel.
Measurement Points
The number of packets beyond the receive window of the OM channel is sampled per second.
At the end of a measurement period, the sum of these sampling results is used as the value of
the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.12.1.9 VS.OMCH.RxAfterClosePkts
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of packets with the FIN bit set to 1 that are received on the
OM channel within a measurement period. The FIN packet indicates the packet received on the
OM channel after the connection is released. Certain data is buffered during transmission, which
causes the receiver to receive some packets after the connection is released. This counter
represents the quality of the OM channel and the network.
Measurement Points
The number of packets received on the OM channel after the connection is released is sampled
per second. At the end of a measurement period, the sum of these sampling results is used as the
value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of acknowledge messages (ACKs), that is, messages have
only ACK information or other information, received on the OM channel within a measurement
period. An acknowledge message is a message with the ACK flag being set. It represents the
quality of the OM channel.
Measurement Points
The number of ACKs received on the OM channel is sampled per second. At the end of a
measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.12.1.11 VS.OMCH.RxDupAckPkts
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of duplicated ACKs received on the OM channel within a
measurement period. It represents the quality of the OM channel.
Measurement Points
The number of duplicated ACKs received on the OM channel is sampled per second. At the end
of a measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.12.1.12 VS.OMCH.RxTooMuchAckPkts
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of received ACKs for the data that has not been transmitted
on the OM channel within a measurement period. This counter indicates the quality of the OM
channel.
Measurement Points
The number of received ACKs for the data that has not been transmitted on the OM channel is
sampled per second. At the end of a measurement period, the sum of these sampling results is
used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the total number of TCP packets successfully transmitted on the OM
channel within a measurement period. The TCP packet includes the control packet, data packet,
and keep-alive packet. This counter represents the traffic on the OM channel.
Measurement Points
The number of packets transmitted on the OM channel is sampled per second. At the end of a
measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.12.1.14 VS.OMCH.TxUrgentPkts
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of all urgent data packets transmitted on the OM channel
within a measurement period. It represents the traffic on the OM channel. An urgent data packet
is a TCP packet with the URG bit set to 1.
Measurement Points
The number of urgent data packets transmitted on the OM channel is sampled per second. At
the end of a measurement period, the sum of these sampling results is used as the value of the
counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of control all packets transmitted on the OM channel within
a measurement period. It represents the traffic on the OM channel. The control packet is used
for connection setup or connection release. It is a TCP packet with the SYN bit, FIN bit, and
RST bit all set and with no data.
Measurement Points
The number of control packets transmitted on the OM channel is sampled per second. At the
end of a measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.12.1.16 VS.OMCH.TxWndProbePkts
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of all window probe packets transmitted on the OM channel
within a measurement period. It represents the traffic on the OM channel. If the local end receives
an ACK from the peer end indicating that the receiving window size is zero, the local end will
send a one-byte TCP packet, that is, a window probe packet, to the peer end after waiting for a
period of time. Window probe packets transmitted on the OM channel are used to determine
whether the receiver can still receive packets, that is, whether the actual receiving window size
is zero. In general, a larger value of this counter indicates a larger extent that the receive capability
is stronger than the transmit capability.
Measurement Points
The number of detection packets transmitted on the OM channel is sampled per second. At the
end of a measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.12.1.17 VS.OMCH.TxWndUpdatePkts
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of all window size update packets transmitted on the OM
channel within a measurement period. Such a packet is transmitted as a response to the window
probe packet. It only includes the window size update information and has no data. This counter
represents the quality of the OM channel.
Measurement Points
The number of window size update packets transmitted on the OM channel is sampled per
second. At the end of a measurement period, the sum of these sampling results is used as the
value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of all data packets transmitted on the OM channel within a
measurement period. It represents the traffic on the OM channel.
Measurement Points
The number of data packets transmitted on the OM channel is sampled per second. At the end
of a measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of all packets retransmitted on the OM channel within a
measurement period. The transmitter retransmits a packet if no ACK message for the packet is
received within a specified time. This counter represents the quality of the OM channel.
Measurement Points
The number of packets retransmitted on the OM channel is sampled per second. At the end of
a measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of all ACKs, that is, the packets only include ACK
information and have no data, transmitted on the OM channel within a measurement period.
This counter represents the quality of the OM channel.
Measurement Points
The number of ACKs transmitted on the OM channel is sampled per second. At the end of a
measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The Network.Tunnel function subset measures the traffic and data rate in the tunnel. It represents
the traffic volume of services carried by the tunnel in the base station and the quality of data
transmission. Figure 1-14 shows the position of the tunnel in the TCP/IP model.
Figure 1-14
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The following table describes the meanings of each counter.
Measurement Points
The number of bytes in the packets successfully transmitted or received in the tunnel is sampled
per second. At the end of a measurement period, the sum of these sampling results is used as the
value of the counter.
Formula
None
Unit
byte
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The following table describes the meanings of each counter.
Measurement Points
The number of packets successfully transmitted or received in the tunnel is sampled per second.
At the end of a measurement period, the sum of these sampling results is used as the value of
the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The following table describes the meanings of each counter.
Measurement Points
Transmit rate and receive rate in the TUNNEL per second. At the end of a measurement period,
the maximum, minimum, average sampling results are reported.
Formula
None
Unit
bit/s
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The Datalink.TRUNK function subset measures the data rate in the TRUNK. It represents the
traffic volume of services carried by the TRUNK in the base station and the quality of service.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters provide total transmit and receive bandwidth in TRUNK link in the current
measurement period, reflecting the TRUNK bandwidth.
Measurement Points
Available bandwidth in the transmit and receive directions of the trunk group per second. At the
end of a measurement period, the average of these sampling results is used as the value of the
corresponding counter.
Formula
None
Unit
kbit/s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters provide the transmit rate and the receive rate in TRUNK in the current
measurement period, reflecting the TRUNK link quality.
Measurement Points
The transmit rate or the receive rate on the trunk is sampled per second. At the end of a
measurement period, the maximum, minimum, or average of these sampling results is used as
the value of the corresponding counter.
Formula
None
Unit
kbit/s
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of discarded packets due to L2 ACL filter based on port.
Measurement Points
The number of discarded packets received due to L2 ACL filter based on port is sampled per
second. At the end of a measurement period, the sum of these sampling results is used as the
value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
1.15.1.2 Number of discarded packets due to advanced ACL filter based on port
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of discarded packets due to advanced ACL filter based on
port. Advanced ACLs refer to L3 and L4 ACLs.
Measurement Points
The number of discarded packets received due to advanced ACL filter based on port is sampled
per second. At the end of a measurement period, the sum of these sampling results is used as the
value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The IKE function subset measures the state of IKE.It helps to analyze the IKE state.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of IKE packets received by the base station.
Measurement Points
The number of IKE packets received is sampled per second. At the end of a measurement period,
the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of IKE packets transmitted.
Measurement Points
The number of IKE packets transmitted is sampled per second. At the end of a measurement
period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the times of IKE child SA rekey completed by the base station.
Measurement Points
When sub SA rekey completed, the counter will be added 1.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the failure times of base station DPD session.
Measurement Points
Times of DPD session fail is sampled in 30 seconds. At the end of a measurement period, the
sum of these sampling results is used as the value of the counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The IPSec function subset measures the state of IPSec,It helps to analyze the IPSec state.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of packets discarded by the base station RX due to the replay
checking.
Measurement Points
The number of discarded packets received due to replay checking fail is sampled per second. At
the end of a measurement period, the sum of these sampling results is used as the value of the
counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of packets discarded by the base station RX due to the AH
authentication failure.
Measurement Points
The number of discarded packets received due to AH checking fail is sampled per second. At
the end of a measurement period, the sum of these sampling results is used as the value of the
counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of packets discarded by the base station RX due to the ESP
authentication failure or decryption failure.
Measurement Points
The number of discarded packets received due to ESP fail is sampled per second. At the end of
a measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of packets discarded by the base station RX due to packets
that should not have been encrypted.
Measurement Points
The number of discarded packets received due to decrypt ACL fail is sampled per second. At
the end of a measurement period, the sum of these sampling results is used as the value of the
counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of packets successfully decrypted by the base station RX.
Measurement Points
The number of packets decryption successful received is sampled per second. At the end of a
measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of packets discarded by the base station TX due to outbound
SA miss.
Measurement Points
The number of discarded packets transmitted due to outbound SA miss is sampled per second.
At the end of a measurement period, the sum of these sampling results is used as the value of
the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of packets discarded by the base station TX due to sequence
number overflow.
Measurement Points
The number of discarded packets transmitted due to sequence number overflow is sampled per
second. At the end of a measurement period, the sum of these sampling results is used as the
value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of packets successfully encrypted by the base station TX.
Measurement Points
The number of packets encryption successful transmitted is sampled per second. At the end of
a measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The SCTPLNK function subset measures the traffic volumes of IP packets transmitted and
received on an SCTP link inside the base station. It measures traffic volumes of the signaling
services carried on base station transmission boards and the service quality.Figure 1-15 shows
the position of the SCTP layer in the TCP/IP model.
Figure 1-15
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of bytes in the IP packets transmitted or received on the
SCTP link within a measurement period. They represent the traffic volume of signaling services.
The counter measure the number of bytes discarded on the SCTP link within a measurement
period is not supported currently and the value of the counter VS.SctpLnk.RxDropBytes is
always 0.
Measurement Points
The number of bytes in the IP packets successfully transmitted, successfully received or
discarded on the SCTP link is sampled per second. At the end of a measurement period, the sum
of these sampling results is used as the value of the corresponding counter. The counter value
includes the number of bytes in user data (the data field of a user data packet, excluding the
MAC header, IP header, and SCTP header). This counter excludes the number of bytes in the
following SCTP management messages: Heartbeat messages, Link establishment messages,
Link disconnection messages, Handshake messages.
Formula
None
Unit
byte
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of IP packets transmitted or received or discarded on the
SCTP link within a measurement period. They represent the traffic volume of signaling services.
Measurement Points
The number of IP packets successfully transmitted, successfully received or discarded on the
SCTP link is sampled per second. At the end of a measurement period, the sum of these sampling
results is used as the value of the corresponding counter. The counter value includes the number
of all the packets received over an SCTP link. The packets include SCTP management messages,
such as heartbeat messages, link establishment messages, link disconnection messages, and
handshake messages. However, the received packets on an SCTP link are not measured in any
of the following cases: (1) The SCTP link is not configured. (2) There is no signaling bearer at
the upper layer of the SCTP link. (3) The SCTP link is blocked.
The VS.SctpLnk.RxPkts counter provides the number of IP packets received on the SCTP link.
A measured IP packet must carry the IP addresses and port numbers that can identify an SCTP
association. The following packets are measured: (1) ABORT packets. (2) Packets that pass the
code check (excluding the V-tag check) and can be sent to the corresponding association.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the maximum rate, minimum rate, and average rate for transmitting or
receiving IP packets on an SCTP link within a measurement period. These rates are calculated
on a per-byte basis. They represent the transmission capability of the SCTP link.
Measurement Points
The transmit rate or the receive rate on the SCTP link is sampled per second. At the end of a
measurement period, the maximum rate, minimum rate or average rate of these sampling results
is used as the value of the corresponding counter.
Formula
None
Unit
bit/s
Related Features
Counter Name Feature ID Feature Name
1.18.1.4 Number of packets on the SCTP link from the application layer
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of user packets transmitted or received on the SCTP link
within a measurement period. They represent the traffic volume of signaling services.
Measurement Points
The number of packets received from or transmitted to the application layer on an SCTP link is
sampled per second. At the end of a measurement period, the sum of these sampling results is
used as the value of the corresponding counters.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of chunks retransmitted from the SCTP link. They represent
the transmission capability of the SCTP link.
Measurement Points
The number of packets retransmitted on an SCTP link is sampled per second. At the end of a
measurement period, the sum of these sampling results is used as the value of the corresponding
counters.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter provides the duration through which an SCTP link is in the congested state in a
measurement period.
Measurement Points
The congestion duration is sampled per second. At the end of a measurement period, the sum of
these sampling results is used as the value of the corresponding counter. An SCTP link is
considered congested when the buffered data of the SCTP link reaches the threshold.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter provides the number of times that an SCTP link enters the congested state in a
measurement period.
Measurement Points
The number of congestion times is sampled per second. At the end of a measurement period,
the sum of these sampling results is used as the value of the corresponding counter. An SCTP
link is considered congested when the buffered data of the SCTP link reaches the threshold.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter provides the duration through which an SCTP link is in the unavailable state.
Measurement Points
The duration through which an SCTP link is unavailable is sampled per second. At the end of a
measurement period, the sum of these sampling results is used as the value of the corresponding
counter. When an SCTP link is in the unavailable state, the link may be faulty or deactivated.
Due to time adjustment and measurement precision, the measurement result of the counter
VS.SctpLnk.Unavail.Dur may have an error of several seconds.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter provides the number of times that an SCTP link is unavailable due to link
disconnection.
Measurement Points
The number of times that an SCTP link becomes unavailable is sampled per second. At the end
of a measurement period, the sum of these sampling results is used as the value of the
corresponding counter. When an SCTP link is in the unavailable state, the link may be faulty or
deactivated.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The UserPlaneHostIP function subset measures the IP packets and bytes in the IP packets
transmitted from and received by a user-plane local IP address. It helps analyze the transmission
quality of the system and ensure stable and reliable operation of the system.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of packets received and transmitted based on the user-plane
local IP address at the IP layer within a measurement period. It indicates the traffic of a user-
plane local IP address at the IP layer.
Measurement Points
The number of packets successfully transmitted or received on the user-plane local IP address
is sampled per second. At the end of a measurement period, the sum of these sampling results
is used as the value of the corresponding counter. The packets to be measured are IP packets. If
IP packets need to be fragmented, the number of TX packets is measured before the packets are
fragmented and the number of RX packets is measured after the packets are reassembled.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of bytes received and transmitted based on the user-plane
local IP address at the IP layer within a measurement period. It indicates the traffic of a user-
plane local IP address at the IP layer.
Measurement Points
The number of bytes in the packets successfully transmitted or received on the user-plane local
IP address is sampled per second. At the end of a measurement period, the sum of these sampling
results is used as the value of the corresponding counter. The bytes to be measured include IP
packet header and payload. When IPSec is used, the bytes to be measured include IPSec-related
payloads, such as AH header and ESP header. If packets need to be fragmented, the number of
TX bytes is measured before the packets are fragmented and the number of RX bytes is measured
after the packets are reassembled.
Formula
None
Unit
byte
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure receive and transmit rate based on the user-plane local IP address at the
IP layer within a measurement period. It indicates the load of a user-plane local IP address at
the IP layer.
Measurement Points
The transmit rate or the receive rate on the user-plane local IP address is sampled per second.
At the end of a measurement period, the maximum and average sampling results are reported.
The counter includes the IP header and payload.
Formula
None
Unit
bit/s
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The Transport.Gtpu function subset measures the number of packets or the number of bytes in
the packets received or transmitted on the GTP-U link. It represents the data volume on the user
plane of the base station. The GTP-U layer uses UDP packets for transmission. Figure 1-16
shows the position of the GTP-U layer in the TCP/IP model.
Figure 1-16
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of bytes in the packets transmitted, received, and erroneous
in the receive direction respectively within a measurement period. Both GTP-U control messages
and user data are measured, as shown in Figure 1. These counters indicate the data volume
(including the GTP-U header) on the user plane.
Measurement Points
The number of bytes in the packets transmitted, received, or erroneous in the receive direction
on the GTP-U link is sampled per second. At the end of a measurement period, the sum of these
sampling results is used as the value of the corresponding counter.
The counter VS.Gtpu.RxDropBytes measures the number of bytes in the erroneous packets
received at the GTP-U layer in the following cases:(1) Searching the inter working (ITW) table
fails.(2) Errors occur in version check.(3) The protocol type is incorrect.(4) The packet length
is incorrect.(5) The TEID is not a configured one.(6) An extra layer of extension header exist in
the packet.(7) The extension header is invalid.
Figure 1-17
Formula
None
Unit
byte
Related Features
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
These counters measure the number of packets successfully received or transmitted on the GTP-
U link within a measurement period. They indicate the data volume on the user plane.
Measurement Points
The number of packets successfully transmitted or received on the GTP-U link is sampled per
second. At the end of a measurement period, the sum of these sampling results is used as the
value of the corresponding counter.
Formula
None
Unit
packet
Related Features
None
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The Board.CPU function subset measures the CPU usage of the LMPT, UMPT and LBBP.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the maximum and average CPU usage of the LMPT, UMPT and LBBP
within a measurement period.
In the current version, either counter 1526727013 VS.Board.CPUload.Max or the 1593835632
VS.BBUBoard.CPULoad.Max counter is used, or they can both be used. The reported value of
counter 1526727013 VS.Board.CPUload.Max is normal but counter 1526727013
VS.Board.CPUload.Max is not recommended for use. In a later version, only the 1593835632
VS.BBUBoard.CPUload.Max counter is used.
In the current version, either counter 1526727014 VS.Board.CPUload.Mean or the 1593835633
VS.BBUBoard.CPUload.Mean counter is used, or they can both be used. The reported value of
Measurement Points
In the sampling interval of 5s, the CPU usage is sampled many times, and the average of these
sampling results is used as the average CPU usage of this sampling interval. The maximum or
the average of the final sampling results is used as the value of this counter. Each sampling result
is based on the maximum usage among multiple CPUs in the board. For example, if the number
of times that the average CPU usage exceeds the preconfigured threshold in the measurement
period is X1, X2, X3, ..., and Xn, the value of the VS.Board.CPUload.Max and
VS.Board.CPUload.Mean counters are calculated using the following formulae:
VS.Board.CPUload.Max = MAX(Xi), VS.Board.CPUload.Mean =(X1+X2+...+Xn)/n.
Formula
None
Unit
%
Related Features
Counter Name Feature ID Feature Name
1.21.1.2 Number of Times that the CPU Usage of Boards Exceeds the Preconfigured
Threshold
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of times that the CPU usage of the LMPT, UMPT and the
LBBP exceeds the preconfigured threshold. It indicates the load status of boards during a
measurement period.
Measurement Points
In the sampling interval of 5s, the CPU usage is sampled many times, and the average of these
sampling results is used as the average CPU usage of this sampling interval. At the end of a
measurement period, the number of times that the average CPU usage exceeds the preconfigured
threshold is used as the value of the counter. The preconfigured threshold is 85%. For example,
if the number of times that the average CPU usage exceeds the preconfigured threshold in the
measurement period is X1, X2, X3, ..., and Xn, the value of the
VS.Board.CPULoad.CumulativeHighloadCount counter is the sum of X1, X2, X3, ..., and Xn.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The RRU.Device function subset measures the performance of the RRU, such as power
consumption.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total power consumption of the RRU or RFU within a measurement
period. It provides data basis for energy conservation policies.
The counter 1526727065 VS.EnergyCons.RRU can report in current version and will be
removed in later version. Counter 1526727065 VS.EnergyCons.RRU is not recommended for
use.
Measurement Points
The RRU or RFU power consumption is sampled every 5 minutes. At the end of a measurement
period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
kWh
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The eNodeB.Device function subset measures the performance of the eNodeB, such as power
consumption.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total power consumption of the eNodeB within a measurement period.
It provides data basis for energy conservation policies.
Counter 1526728153 VS.EnergyCons.BTS.Adding will be replaced by counter 1593835637
VS.EnergyCons.BTS.Adding.LTE in later versions. In the current version, counters
1526728153 VS.EnergyCons.BTS.Adding and 1593835637 VS.EnergyCons.BTS.Adding.LTE
are both valid, and the value of counter 1526728153 VS.EnergyCons.BTS.Adding is properly
reported. Counter 1526728153 VS.EnergyCons.BTS.Adding will be deleted in later versions.
Using counter 1526728153 VS.EnergyCons.BTS.Adding is not recommended.
Measurement Points
The estimated eNodeB power consumption is sampled every 5 minutes based on the power
consumption of the BBU, RRUs/RFUs, and peripheral devices such as electromechanical
devices and ALDs. At the end of a measurement period, the sum of these sampling results is
used as the value of this counter.
Formula
None
Unit
kWh
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total power consumption monitored by all the PMUs within a
measurement period. It provides a reference for energy conservation policies.The power
consumption of the eNodeB can be classified into DC power consumption and AC power
consumption, and you can run the SET ECMP command to set the power consumption type.
The PMU monitors the DC power consumption by default. The dependence of this counter on
the PMU is as follows:
For the PMU01B, this counter is reported only when the software version of the PMU is 138 or
later.
For the PMU10A or PMU11A, this counter is reported regardless of the software version of the
PMU.
You can run the DSP PMU command to query the type and software version of a PMU.
If a BS contains multiple PMUs and one or more PMUs do not support reporting this counter,
the measurement results of this counter are inaccurate.
Measurement Points
The power consumption monitored by all the PMUs is sampled every 5 minutes. At the end of
a measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
kWh
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the shutdown duration of all power supplying units (PSUs) in the NodeB
within the measurement period.
Measurement Points
The duration of PSU intelligent shutdown is sampled per minute. At the end of a measurement
period, the sum of these sampling results is used as the value of the counter.
A deviation of one sampling period may be caused in the sampling timer when the timer performs
time synchronization. As a result, a deviation of one sampling period will also be generated in
the value of this counter, which affects the values of the KPIs that are calculated by using this
counter. The effects vary depending on the deviation in the value of this counter and calculation
formulas for the KPIs.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Overview
The BBU.Device function subset measures the performance of the BBU, such as power
consumption.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total power consumption of the BBU within a measurement period.
It provides data basis for energy conservation policies.
The counter 1526727551 VS.EnergyCons.BBU can report in current version and will be
removed in later version. Counter 1526727551 VS.EnergyCons.BBU is not recommended for
use.
Measurement Points
The BBU power consumption is sampled every 5 minutes based on the power of all configured
and detected boards in the BBU subrack. At the end of a measurement period, the sum of these
sampling results is used as the value of the counter.
Formula
None
Unit
kWh
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The PMU.Device function subset measures the performance of the Power Monitoring Unit
(PMU), such as its power consumption.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total DC power consumption monitored by a power monitoring unit
(PMU) within a measurement period. It provides data basis for energy conservation policies.
The counter 1526727549 VS.EnergyCons.PMU can report in current version and will be
removed in later version. Counter 1526727549 VS.EnergyCons.PMU is not recommended for
use.
Measurement Points
The power consumption of each PMU is sampled every 30 seconds. At the end of a measurement
period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
kWh
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The Node Equipment Performance Measurement function subset measures the node equipment
performance measurement.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the shutdown duration of all power supplying units (PSUs) in the base
station within the measurement period.
Measurement Points
In a measurement period, the intelligent shutdown status of each PSU is sampled every second.
When one or more PSUs are intelligently shut down, this counter is added by one.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the power consumption of the LTE within a measurement period, which
equals the sum of the power consumption of boards and RF modules working in LTE mode. In
a LTE only base station, the value of this counter equals the base station power consumption.
In a multimode base station, the value of this counter is a part of the base station power
consumption.
Measurement Points
The system samples the power consumption of boards and RF modules working in LTE mode
every 5 minutes. At the end of a measurement period, the sum of these estimated sampling results
is used as the value of this counter.
Formula
None
Unit
kWh
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the power consumption of the LTE within a measurement period. In a
LTE only base station, the value of this counter equals the base station power consumption. In
a multimode base station, the value of this counter is a part of the base station power consumption.
Measurement Points
The system samples the power consumption measured by the power system every 5 minutes. At
the end of a measurement period, the sum of these sampling results divided by the number of
modes where the PMU is configured equals to the LTE power consumption and is used as the
value of the counter.
Formula
None
Unit
kWh
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
The BBU Board Load Performance Measurement function subset measures the load on a BBU
board.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter provides the number of times of CPU use rate overload.
Measurement Points
In the sampling interval of 5s, the CPU usage is sampled many times, and the average of these
sampling results is used as the average CPU usage of this sampling interval. At the end of a
measurement period, the number of times that the average CPU usage exceeds the preconfigured
threshold is used as the value of the counter. The preconfigured threshold is 85%. For example,
if the number of times that the average CPU usage exceeds the preconfigured threshold in the
measurement period is X1, X2, X3, ..., and Xn, the value of the
VS.BBUBoard.CPULoad.CumulativeHighloadCount counter is the sum of X1, X2, X3, ..., and
Xn.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter provides the maximum and average CPU usage of a board in a specified
measurement period.
Measurement Points
In the sampling interval of 5s, the CPU usage is sampled many times, and the average of these
sampling results is used as the average CPU usage of this sampling interval. The maximum or
the average of the final sampling results is used as the value of this counter. Each sampling result
is based on the maximum usage among multiple CPUs in the board. For example, if the number
of times that the average CPU usage exceeds the preconfigured threshold in the measurement
period is X1, X2, X3, ..., and Xn, the value of the VS.BBUBoard.CPUload.Max and
VS.BBUBoard.CPUload.Mean counters are calculated using the following formulae:
Formula
None
Unit
%
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter provides the percentage of the period during which the CPU usage of a board
exceeds the threshold to the entire measurement period.
Measurement Points
In the measurement period of 5s, the CPU usage is sampled many times, and the average of these
sampling results is used as the final sampling result of this measurement period. The percentage
of the period during which the CPU usage of a board exceeds the threshold to the entire
measurement period is used as the value of this counter. Each sampling result is based on the
maximum usage among multiple CPUs in the board.
Formula
None
Unit
%
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
This counter provides the number of GNSS satellites that can be traced. It helps users identify
GNSS cards that can trace few satellites.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
1.27.1.1 Number of times that the number of traced GNSS satellites falls in level 0
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of times no satellites are traced by this satellite card.
Measurement Points
The number of times that no satellites are traced by the satellite card is sampled every 3s. At the
end of a measurement period, the sum of these sampling results is used as the value of this
counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.27.1.2 Number of times that the number of traced GNSS satellites falls in level 1
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of times one to three satellites are traced by this satellite card.
Measurement Points
The number of times that one to three satellites are traced by the satellite card is sampled every
3s. At the end of a measurement period, the sum of these sampling results is used as the value
of this counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.27.1.3 Number of times that the number of traced GNSS satellites falls in level 2
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of times four satellites are traced by this satellite card.
Measurement Points
The number of times that four satellites are traced by the satellite card is sampled every 3s. At
the end of a measurement period, the sum of these sampling results is used as the value of this
counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.27.1.4 Number of times that the number of traced GNSS satellites falls in level 3
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of times five satellites are traced by this satellite card.
Measurement Points
The number of times that five satellites are traced by the satellite card is sampled every 3s. At
the end of a measurement period, the sum of these sampling results is used as the value of this
counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
1.27.1.5 Number of times that the number of traced GNSS satellites falls in level 4
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of times more than five satellites are traced by this satellite
card.
Measurement Points
The number of times that more than five satellites are traced by the satellite card is sampled
every 3s. At the end of a measurement period, the sum of these sampling results is used as the
value of this counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the average number of satellites traced by this satellite card.
Measurement Points
The number of satellites traced by the satellite card is sampled every 3s. At the end of a
measurement period, the average of these sampling results is used as the value of this counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.4 Measurement of X2-LINK performance between eNodeB and neighbor eNodeB (Sig.X2)
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
Location Service (LCS) provides a means to determine the geographic position and velocity of
a UE based on measuring radio signals. The eNodeB supports the E-CID and OTDOA
positioning techniques. The LCS.ENODEB function subset measures the number of OTDOA
measurement attempts and successful OTDOA measurement requests in an eNodeB.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of LCS OTDOA Information Request messages received by
the eNodeB. The LCS OTDOA Information Request message is an LPPa signaling message sent
from the E-SMLC to an eNodeB. The messaged is used to request the OTDOA assistance data
for positioning a target UE of the eNodeB.
Measurement Points
The L.LCS.OtdoaMeas.Req counter is incremented by 1 each time the eNodeB receives an LCS
OTDOA Information Request message.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of LCS OTDOA Information Response messages sent by the
eNodeB. The LCS OTDOA Information Response message is an LPPa signaling message sent
from an eNodeB to the E-SMLC. The messaged is used to report the OTDOA-related
configuration data of the associated cell controlled by the eNodeB.
Measurement Points
The L.LCS.OtdoaMeas.Succ counter is incremented by 1 each time the eNodeB sends an LCS
OTDOA Information Response message.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The Traffic.User.eNodeB function subset measures the number of users under an eNodeB within
a measurement period.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the maximum number of licenses that the eNodeB has allocated to all
UEs, including UEs experiencing admission successes, admission failures, incoming-handover
successes, and incoming handover failures. This counter helps operators to determine whether
user licenses need capacity expansion.
Measurement Points
The number of UEs in connected mode under an eNodeB is sampled per second. At the end of
a measurement period, the maximum of these sampling results is used as the value of the counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The RIM.eNodeB function subset measures the performance of the requests and transfers of
RAN information between eNodeB and other RAN nodes via the core network.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of system information requests from eNodeB to WCDMA
network.
Measurement Points
As shown at point A in Figure 2-1, the L.RIM.SI.E2W.Req counter is incremented by 1 each
time the eNodeB sends an eNB DIRECT INFORMATION TRANSFER message to WCDMA
to request the system information.
Figure 2-1
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of system information responses from WCDMA network to
eNodeB.
Measurement Points
As shown at point B in Figure 2-2, the L.RIM.SI.E2W.Resp counter is incremented by 1 each
time the eNodeB receives an MME DIRECT INFORMATION TRANSFER message
transferring RAN INFORMATION RESPONSE for system information from WCDMA.
Figure 2-2
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of system information updates from eNodeB to WCDMA
network.
Measurement Points
As shown at point A in Figure 2-3, the L.RIM.SI.E2W.Update counter is incremented by 1 each
time the eNodeB receives an MME DIRECT INFORMATION TRANSFER message
transferring RAN INFORMATION UPDATE for system information from WCDMA.
Figure 2-3
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of load requests from eNodeB to WCDMA network.
Measurement Points
As shown at point A in Figure 2-4, the L.RIM.Load.E2W.Req counter is incremented by 1 each
time the eNodeB sends an eNB DIRECT INFORMATION TRANSFER message transferring
RAN INFORMATION REQUEST to WCDMA for load information request.
Figure 2-4
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of load responses from WCDMA network to eNodeB.
Measurement Points
As shown at point B in Figure 2-5, the L.RIM.Load.E2W.Resp counter is incremented by 1
each time the eNodeB receives an MME DIRECT INFORMATION TRANSFER message
transferring RAN INFORMATION UPDATE for load information from WCDMA.
Figure 2-5
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of load updates from eNodeB to WCDMA network.
Measurement Points
As shown at point A in Figure 2-6, the L.RIM.Load.E2W.Update counter is incremented by 1
each time the eNodeB receives an MME DIRECT INFORMATION TRANSFER message
transferring RAN INFORMATION UPDATE for load information from WCDMA.
Figure 2-6
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The Traffic.Thruput.eNodeB function subset measures the uplink or downlink throughput in an
eNodeB.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the maximum of uplink, downlink, and the sum of uplink and downlink
traffic volumes for PDCP SDUs in an eNodeB.
Measurement Points
The sizes of the payloads in the uplink, downlink, and the sum of uplink and downlink PDCP
SDUs are sampled per second in an eNodeB. At the end of a measurement period, the maximum
of these sampling results per type is used as the value of the corresponding counter.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Overview
The SCTP.eNodeB measurement unit measures the traffic over the SCTP link.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of times that the eNodeB triggers downlink SCTP congestion
control.
Measurement Points
The counter is incremented by 1 each time the eNodeB triggers downlink SCTP congestion
control when the CPU usage reaches 85% and the downlink SCTP message rate reaches 4550
pkts/s because a plenty of packets are sent from the EPC.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Overview
An RRC connection is a Uu interface connection for carrying user signaling messages. The setup
success rate of RRC connections in a cell represents the capability of the cell to provide RRC
connections for users. The RRC.Setup.Cell function subset measures the number of RRC
connection setup requests, number of RRC connection setup attempts, and number of successful
RRC connection setups in a cell. The setup success rate of RRC connections can be calculated
on the basis of the reported counters. Figure 2-7 shows the measurement points in an RRC
connection setup procedure.
Figure 2-7
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.RRC.ConnReq.Att L.RRC.ConnReq.Att.Emc
L.RRC.ConnReq.Att.HighPri
L.RRC.ConnReq.Att.Mt
L.RRC.ConnReq.Att.MoSig
L.RRC.ConnReq.Att.MoData
L.RRC.ConnReq.Att.DelayTol
L.RRC.ConnReq.Succ L.RRC.ConnReq.Succ.Emc
L.RRC.ConnReq.Succ.HighPri
L.RRC.ConnReq.Succ.Mt
L.RRC.ConnReq.Succ.MoSig
L.RRC.ConnReq.Succ.MoData
L.RRC.ConnReq.Succ.DelayTol
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of RRC connection setup requests for different causes in a
cell. The RRC Connection Request message is the first RRC signaling message sent from the
UE to the eNodeB. The message is used to request the setup of an RRC connection.
Measurement Points
As shown at point A in Figure 2-8, the corresponding counter is incremented by 1 each time
the eNodeB receives an RRC Connection Request message from a UE. The counters are
measured as follows:
The L.RRC.ConnReq.Att.Mt counter is incremented by 1 only when the eNodeB receives a non-
retransmitted RRC Connection Request message and the Establishment Cause IE of the message
is "mt-Access".
Figure 2-8
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of successful RRC connection setups for different causes in
a cell. That is, the counters measure the number of RRC Connection Setup Complete messages
received by the eNodeB from a UE. The RRC Connection Setup Complete message is an RRC
signaling message sent from a UE to the eNodeB. The message is used to inform the eNodeB
that the RRC connection setup is completed and informs the eNodeB of the carried NAS
signaling information and the information about PLMN selection.
Measurement Points
As shown at point C in Figure 2-9, the corresponding counter is incremented by 1 each time the
eNodeB receives an RRC Connection Setup Complete message from a UE. The counters are
measured as follows:
The L.RRC.ConnReq.Succ counter is incremented by 1 each time the eNodeB receives the
message from a UE.
The L.RRC.ConnReq.Succ.Emc counter is incremented by 1 each time the eNodeB receives the
message from a UE and the Establishment Cause information element (IE) of the RRC
Connection Request message is "emergency call".
The L.RRC.ConnReq.Succ.HighPri counter is incremented by 1 each time the eNodeB receives
the message from a UE and the Establishment Cause IE of the RRC Connection Request message
is "highPriorityAccess".
The L.RRC.ConnReq.Succ.Mt counter is incremented by 1 each time the eNodeB receives the
message from a UE and the Establishment Cause IE of the RRC Connection Request message
is "mt-Access".
The L.RRC.ConnReq.Succ.MoSig counter is incremented by 1 each time the eNodeB receives
the message from a UE and the Establishment Cause IE of the RRC Connection Request message
is "mo-Signalling".
The L.RRC.ConnReq.Succ.MoData counter is incremented by 1 each time the eNodeB receives
the message from a UE and the Establishment Cause IE of the RRC Connection Request message
is "mo-Data".
The L.RRC.ConnReq.Succ.DelayTol counter is incremented by 1 each time the eNodeB
receives the message from a UE and the Establishment Cause IE of the RRC Connection Request
message is "delayTolerantAccess-v1020".
Figure 2-9
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the success rate of RRC connection setups for services in a cell.
This counter will be deleted in later versions. It is reported normally in the current version but
the measurement value is invalid. You are advised not to use this counter.
Measurement Points
The success rate of RRC connection setups for services in a cell is calculated by using the
following formula based on the values of the counters L.RRC.ConnReq.Succ.Emc,
L.RRC.ConnReq.Succ.HighPri, L.RRC.ConnReq.Succ.Mt, and
L.RRC.ConnReq.Succ.MoData.
Formula
{100}*([L.RRC.ConnReq.Succ.Emc] + [L.RRC.ConnReq.Succ.HighPri] +
[L.RRC.ConnReq.Succ.Mt] + [L.RRC.ConnReq.Succ.MoData])/ ([L.RRC.ConnReq.Att.Emc]
+ [L.RRC.ConnReq.Att.HighPri] + [L.RRC.ConnReq.Att.Mt] +
[L.RRC.ConnReq.Att.MoData])
Unit
%
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of RRC connection setup attempts in a cell. That is, the counter
measures the number of times that the eNodeB sends an RRC Connection Setup message to the
UE after receiving a non-retransmitted RRC Connection Request message from the UE. The
RRC Connection Setup message is an RRC signaling message that the eNodeB sends to the UE.
The message is used to inform the UE of the RRC connection setup result and the related
configuration information.
Measurement Points
As shown at point B in Figure 2-10, the L.RRC.ConnSetup counter is incremented by 1 each
time the eNodeB sends an RRC Connection Setup message to a UE after receiving a non-
retransmitted RRC Connection Request message from the UE.
Figure 2-10
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of times a UE transits from the uplink-synchronized state to
the uplink out-of-synchronization state in the cell.
Measurement Points
The L.RRC.StateTrans.Syn2Unsyn counter is incremented by 1 each time a UE transits from
the uplink-synchronized state to the uplink out-of-synchronization state.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of times a UE transits from the uplink out-of-synchronization
state to the uplink-synchronized state in the cell.
Measurement Points
The L.RRC.StateTrans.Unsyn2Syn counter is incremented by 1 each time a UE transits from
the uplink out-of-synchronization state to the uplink-synchronized state.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the RRC connection setup duration in a cell. The RRC connection setup
duration indicates the interval between the receiving of the RRC Connection Request message
and RRC Connection Setup Complet message.
Measurement Points
As shown at points A and B in Figure 2-11, the eNodeB records the time when it receives the
RRC Connection Request or RRC Connection Setup Complete message. The RRC connection
setup duration is the interval between the time when the two messages are received in an RRC
connection setup procedure. At the end of a measurement period, the average and maximum
RRC connection setup duration are the average and maximum duration of all durations,
respectively.
Figure 2-11
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
Overview
An RRC connection is a Uu interface connection for carrying user signaling messages. The setup
success rate of RRC connections in a cell represents the capability of the cell to provide RRC
connections for users. The RRC.SetupFail.Cell function subset measures the number of RRC
connection setup failures for different causes in a cell. The setup success rate of RRC connections
can be calculated on the basis of the reported counters. Figure 2-12 shows the measurement
points in a failed RRC connection setup procedure.
Figure 2-12
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.RRC.SetupFail.ResFail L.RRC.SetupFail.ResFail.SRS
L.RRC.SetupFail.ResFail.PUCCH
L.RRC.SetupFail.Rej L.RRC.SetupFail.ResFail
L.RRC.SetupFail.Rej.FlowCtrl
2.2.2.1 Number of RRC Connection Setup Failures for Different Causes in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of RRC connection setup failures due to different causes in a
cell and the number of RRC Connection Request messages that are discarded due to flow control
in the cell. The RRC Connection Reject message is an RRC signaling message sent from the
eNodeB to the UE to inform the UE that the access is rejected by the eNodeB.
Measurement Points
As shown at point A in Figure 2-13, the L.RRC.SetupFail.ResFail,
L.RRC.SetupFail.ResFail.SRS, or L.RRC.SetupFail.ResFail.PUCCH counter is incremented by
1 each time the eNodeB sends an RRC Connection Reject message to the UE due to resource
allocation failure, SRS resource allocation failure, PUCCH resource allocation failure,
respectively, after receiving an RRC Connection Request message from the UE.
Figure 2-13
Figure 2-14
Figure 2-15
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Figure 2-16
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.RRC.ReEst.Att L.RRC.ReEst.ReconfFail.Att
L.RRC.ReEst.HoFail.Att
L.RRC.ReEst.Succ L.RRC.ReEst.ReconfFail.Succ
L.RRC.ReEst.HoFail.Succ
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of RRC connection reestablishment requests for different
causes in a cell. The RRC Connection Reestablishment Request message is an RRC signaling
message sent by the UE. The message is used to recover the RRC signaling connection.
Measurement Points
As shown at point A in Figure 2-17, the corresponding counter is incremented by 1 each time
the eNodeB receives an RRC Connection Reestablishment Request message from the UE. The
counters are measured as follows:
The L.RRC.ReEst.Att counter is incremented by 1 only when the eNodeB receives a non-
retransmitted RRC Connection Reestablishment Request message.
The L.RRC.ReEst.HoFail.Att counter is incremented by 1 each time the eNodeB receives a non-
retransmitted RRC Connection Reestablishment Request message from the UE and the
ReestablishmentCause IE in the message is "handoverFailure".
Figure 2-17
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of successful RRC connection reestablishments for different
causes in a cell. The RRC Connection Reestablishment Complete message is an RRC signaling
message sent from the UE to the eNodeB. The message is used to inform the eNodeB that the
RRC connection reestablishment is completed.
Measurement Points
As shown at point B in Figure 2-18, the corresponding counter is incremented by 1 each time
the eNodeB receives an RRC Connection Reestablishment Complete message from the UE. The
counters are measured as follows:
The L.RRC.ReEst.Succ counter is incremented by 1 each time the eNodeB receives the message
from the UE.
Figure 2-18
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
An RRC connection reestablishment is a UE-initiated process of recovering an RRC connection.
The RRC.ReEstFail.Cell function subset measures the number of RRC connection
reestablishment failures for different causes in a cell. Figure 2-19 shows the measurement points
in a failed RRC connection reestablishment procedure.
Figure 2-19
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.RRC.ReEstFail.Rej L.RRC.ReEst.ReconfFail.Rej
L.RRC.ReEst.HoFail.Rej
L.RRC.ReEstFail.Rej L.RRC.ReEstFail.ResFail
L.RRC.ReEstFail.NoCntx
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of RRC connection reestablishment failures due to different
causes in a cell. The RRC Connection Reestablishment Reject message is an RRC signaling
message sent from the eNodeB to the UE to inform the UE that the reestablishment is rejected
by the eNodeB.
Measurement Points
As shown at point A in Figure 2-20, the corresponding counter is incremented by 1 each time
the eNodeB sends an RRC Connection Reestablishment Reject message after receiving an RRC
Connection Reestablishment Request message from the UE. The counters are measured as
follows:
The L.RRC.ReEstFail.Rej counter is incremented by 1 each time the eNodeB sends the message
to the UE.
Figure 2-20
Figure 2-21
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Figure 2-22
Figure 2-23
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.E-RAB.AttEst.QCI.1 L.E-RAB.InitAttEst.QCI.1
L.E-RAB.SuccEst.QCI.1 L.E-RAB.InitSuccEst.QCI.1
L.E-RAB.AttEst.QCI.2 L.E-RAB.InitAttEst.QCI.2
L.E-RAB.SuccEst.QCI.2 L.E-RAB.InitSuccEst.QCI.2
L.E-RAB.AttEst.QCI.3 L.E-RAB.InitAttEst.QCI.3
L.E-RAB.SuccEst.QCI.3 L.E-RAB.InitSuccEst.QCI.3
L.E-RAB.AttEst.QCI.4 L.E-RAB.InitAttEst.QCI.4
L.E-RAB.SuccEst.QCI.4 L.E-RAB.InitSuccEst.QCI.4
L.E-RAB.AttEst.QCI.5 L.E-RAB.InitAttEst.QCI.5
L.E-RAB.SuccEst.QCI.5 L.E-RAB.InitSuccEst.QCI.5
L.E-RAB.AttEst.QCI.6 L.E-RAB.InitAttEst.QCI.6
L.E-RAB.SuccEst.QCI.6 L.E-RAB.InitSuccEst.QCI.6
L.E-RAB.AttEst.QCI.7 L.E-RAB.InitAttEst.QCI.7
L.E-RAB.SuccEst.QCI.7 L.E-RAB.InitSuccEst.QCI.7
L.E-RAB.AttEst.QCI.8 L.E-RAB.InitAttEst.QCI.8
L.E-RAB.SuccEst.QCI.8 L.E-RAB.InitSuccEst.QCI.8
L.E-RAB.AttEst.QCI.9 L.E-RAB.InitAttEst.QCI.9
L.E-RAB.SuccEst.QCI.9 L.E-RAB.InitSuccEst.QCI.9
L.E-RAB.SuccEst L.E-RAB.SuccEst.QCI.1
L.E-RAB.SuccEst.QCI.2
L.E-RAB.SuccEst.QCI.3
L.E-RAB.SuccEst.QCI.4
L.E-RAB.SuccEst.QCI.5
L.E-RAB.SuccEst.QCI.6
L.E-RAB.SuccEst.QCI.7
L.E-RAB.SuccEst.QCI.8
L.E-RAB.SuccEst.QCI.9
L.E-RAB.SuccEst L.E-RAB.InitSuccEst
L.E-RAB.AttEst L.E-RAB.AttEst.QCI.1
L.E-RAB.AttEst.QCI.2
L.E-RAB.AttEst.QCI.3
L.E-RAB.AttEst.QCI.4
L.E-RAB.AttEst.QCI.5
L.E-RAB.AttEst.QCI.6
L.E-RAB.AttEst.QCI.7
L.E-RAB.AttEst.QCI.8
L.E-RAB.AttEst.QCI.9
L.E-RAB.AttEst L.E-RAB.InitAttEst
L.E-RAB.InitAttEst L.E-RAB.InitAttEst.QCI.1
L.E-RAB.InitAttEst.QCI.2
L.E-RAB.InitAttEst.QCI.3
L.E-RAB.InitAttEst.QCI.4
L.E-RAB.InitAttEst.QCI.5
L.E-RAB.InitAttEst.QCI.6
L.E-RAB.InitAttEst.QCI.7
L.E-RAB.InitAttEst.QCI.8
L.E-RAB.InitAttEst.QCI.9
L.E-RAB.InitSuccEst L.E-RAB.InitSuccEst.QCI.1
L.E-RAB.InitSuccEst.QCI.2
L.E-RAB.InitSuccEst.QCI.3
L.E-RAB.InitSuccEst.QCI.4
L.E-RAB.InitSuccEst.QCI.5
L.E-RAB.InitSuccEst.QCI.6
L.E-RAB.InitSuccEst.QCI.7
L.E-RAB.InitSuccEst.QCI.8
L.E-RAB.InitSuccEst.QCI.9
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of E-RAB setup attempts initiated by UEs for services with
a specific QCI ranging from 1 to 9 and the total number of E-RABsetup attempts initiated by
UEs in a cell. The E-RAB setup is initiated by a UE when the UE requests a service from the
radio network. The setup is implemented through the initial UE context setup or the E-RAB
setup procedure.
Measurement Points
As shown at point A in Figure 2-24 or Figure 2-25, the corresponding counter is incremented
based on the QCI of each service each time the eNodeB receives an INITIAL CONTEXT SETUP
REQUEST or an E-RAB SETUP REQUEST message from the MME. If the INITIAL
CONTEXT SETUP REQUEST or E-RAB SETUP REQUEST message requests multiple E-
RAB setups at the same time, the corresponding counter is incremented by the number of
requested E-RAB setups in the message based on the QCI of each service. In addition the number
of requested E-RAB setups contained in the INITIAL CONTEXT SETUP REQUEST and E-
RAB SETUP REQUEST messages is accumulated as the value of the L.E-RAB.AttEst counter.
Figure 2-24
Figure 2-25
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of successful E-RAB setups initiated by UEs for services with
a specific QCI ranging from 1 to 9 and the total number of successful E-RAB setups initiated
by UEs in a cell. The E-RAB setup is initiated by a UE when the UE requests a service from the
radio network. The setup is implemented through the initial UE context setup or the E-RAB
setup procedure.
Measurement Points
As shown at point B in Figure 2-26 or Figure 2-27, the corresponding counter is incremented
based on the QCI of each service each time the eNodeB sends an E-RAB SETUP RESPONSE
or an INITIAL CONTEXT SETUP RESPONSE message to the MME. If the E-RAB SETUP
RESPONSE or INITIAL CONTEXT SETUP RESPONSE message reports multiple successful
E-RAB setups at the same time, the corresponding counter is incremented by the number of
successful E-RAB setups in the message based on the QCI of each service. In addition, the
number of successful E-RAB setups contained in the E-RAB SETUP RESPONSE and INITIAL
CONTEXT SETUP RESPONSE messages is accumulated as the value of the L.E-RAB.SuccEst
counter.
Figure 2-26
Figure 2-27
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the E-RAB setup success rate in a cell.
This counter will be deleted in later versions. It is reported normally in the current version but
the measurement value is invalid. You are advised not to use this counter.
Measurement Points
The E-RAB setup success rate in a cell is calculated by using the corresponding KPI calculation
formula based on the values of the counters L.E-RAB.SuccEst.QCI.1, L.E-RAB.SuccEst.QCI.
2, L.E-RAB.SuccEst.QCI.3, L.E-RAB.SuccEst.QCI.4, L.E-RAB.SuccEst.QCI.5, L.E-
RAB.SuccEst.QCI.6, L.E-RAB.SuccEst.QCI.7, L.E-RAB.SuccEst.QCI.8, L.E-
RAB.SuccEst.QCI.9, L.E-RAB.AttEst.QCI.1, L.E-RAB.AttEst.QCI.2, L.E-RAB.AttEst.QCI.
3, L.E-RAB.AttEst.QCI.4, L.E-RAB.AttEst.QCI.5, L.E-RAB.AttEst.QCI.6, L.E-
RAB.AttEst.QCI.7, L.E-RAB.AttEst.QCI.8, and L.E-RAB.AttEst.QCI.9.
Formula
{100}*([L.E-RAB.SuccEst.QCI.1]+[L.E-RAB.SuccEst.QCI.2]+[L.E-RAB.SuccEst.QCI.3]+
[L.E-RAB.SuccEst.QCI.4]+[L.E-RAB.SuccEst.QCI.5]+[L.E-RAB.SuccEst.QCI.6]+[L.E-
RAB.SuccEst.QCI.7]+[L.E-RAB.SuccEst.QCI.8]+[L.E-RAB.SuccEst.QCI.9])/([L.E-
RAB.AttEst.QCI.1]+[L.E-RAB.AttEst.QCI.2]+[L.E-RAB.AttEst.QCI.3]+[L.E-
RAB.AttEst.QCI.4]+[L.E-RAB.AttEst.QCI.5]+[L.E-RAB.AttEst.QCI.6]+[L.E-
RAB.AttEst.QCI.7]+[L.E-RAB.AttEst.QCI.8]+[L.E-RAB.AttEst.QCI.9])
Unit
%
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of initial E-RAB setup attempts initiated by UEs for services
with a specific QCI ranging from 1 to 9 and the total number of initial E-RAB setup attempts
initiated by UEs in a cell. The initial E-RAB setup is initiated by a UE when the UE requests a
service from the radio network. The setup is implemented through the initial UE context setup
procedure.
Measurement Points
As shown at point A in Figure 2-28, the corresponding counter is incremented based on the QCI
of each service each time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST
message from the MME. If the INITIAL CONTEXT SETUP REQUEST message requests to
set up multiple initial E-RABs at the same time, the corresponding counter is incremented by
the number of requested initial E-RAB setups in the message based on the QCI of each service.
In addition, the number of requested initial E-RAB setups contained in the INITIAL CONTEXT
SETUP REQUEST messages is accumulated as the value of the L.E-RAB.InitAttEst counter.
Figure 2-28
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of successful initial E-RAB setups initiated by UEs for
services with a specific QCI ranging from 1 to 9 and the total number of successful initial E-
RAB setups initiated by UEs in a cell. The initial E-RAB setup is initiated by a UE when the
UE requests a service from the radio network. The setup is implemented through the initial UE
context setup procedure.
Measurement Points
As shown at point B in Figure 2-29, the corresponding counter is incremented based on the QCI
of each service each time the eNodeB sends an INITIAL CONTEXT SETUP RESPONSE
message to the MME. If the INITIAL CONTEXT SETUP RESPONSE message reports multiple
successful initial E-RAB setups at the same time, the corresponding counter is incremented by
the number of successful initial E-RAB setups in the message based on the QCI of each service.
In addition, the number of successful initial E-RAB setups contained in the INITIAL CONTEXT
SETUP RESPONSE messages is accumulated as the value of the L.E-RAB.InitSuccEst counter.
Figure 2-29
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.5.6 Total Number of E-RAB Setup Attempts for Incoming Handovers in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the total number of E-RAB setup attempts for incoming handovers in a
cell.
Measurement Points
Figure 2-30 shows an intra-eNodeB handover, Figure 2-31 shows anX2-based handover, and
Figure 2-32 shows an S1-bases handover. As shown at point A in Figure 2-30, Figure 2-31, or
Figure 2-32, the L.E-RAB.AttEst.HOIn counter is incremented in the target cell each time the
eNodeB decides to perform a handover after receiving a measurement report from a UE. If
multiple E-RABs are attempted to be set up in the target cell, the counter is incremented in the
target cell by the number of requested E-RAB setups.
Figure 2-30
Figure 2-31
Figure 2-32
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of successful E-RAB setups for services with a specific QCI
ranging from 1 to 9 for incoming handovers and the total number of successful E-RAB setups
for incoming handovers in a cell.
Measurement Points
As shown at point C in Figure 2-33, during an intra-eNodeB handover the corresponding counter
is incremented in the target cell based on the QCI of each service each time the target cell receives
an RRC Connection Reconfiguration Complete message from a UE and the subsequent
processing is successful. If multiple E-RABs are set up in the target cell, the corresponding
counter is incremented by the number of successful E-RAB setups in the target cell based on
the QCI of each service.
As shown at point C in Figure 2-34, the corresponding counter is incremented in the target cell
based on the QCI of each service each time the target cell receives an RRC Connection
Reestablishment Complete message from a UE and the subsequent processing is successful. If
multiple E-RABs are set up in the target cell, the corresponding counter is incremented by the
number of successful E-RAB setups in the target cell based on the QCI of each service.
As shown at point C in Figure 2-35, during an X2-based handover the corresponding counter
is incremented in the target cell based on the QCI of each service each time the target eNodeB
receives a PATH SWITCH REQUEST ACKNOWLEDGE message from the MME and sends
a UE CONTEXT RELEASE message to the source eNodeB over the X2 interface. If multiple
E-RABs are set up in the target cell, the corresponding counter is incremented by the number
of successful E-RAB setups in the target cell based on the QCI of each service.
As shown at point C in Figure 2-36, during an X2-based handover the corresponding counter
is incremented in the target cell based on the QCI of each service each time the target eNodeB
receives a PATH SWITCH REQUEST ACKNOWLEDGE message from the MME and sends
a UE CONTEXT RELEASE message to the source eNodeB over the X2 interface after the RRC
connection for the UE is successfully reestablished to the target eNodeB. If multiple E-RABs
are set up in the target cell, the corresponding counter is incremented by the number of successful
E-RAB setups in the target cell based on the QCI of each service.
As shown at point C in Figure 2-37, during an S1-based handover the corresponding counter is
incremented in the target cell based on the QCI of each service each time the target eNodeB
sends a HANDOVER NOTIFY message to the MME. If multiple E-RABs are set up in the target
cell, the corresponding counter is incremented by the number of successful E-RAB setups in the
target cell based on the QCI of each service.
As shown at point C in Figure 2-38, during an S1-based handover the corresponding counter is
incremented in the target cell based on the QCI of each service each time the target eNodeB
sends a HANDOVER NOTIFY message to the MME after the RRC connection for the UE is
successfully to the target eNodeB. If multiple E-RABs are set up in the target cell, the
corresponding counter is incremented by the number of successful E-RAB setups in the target
cell based on the QCI of each service.
Figure 2-33
Figure 2-34
Figure 2-35
Figure 2-36
Figure 2-37
Figure 2-38
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of UE-related signaling connection setup attempts and the
number of successful UE-specific signaling connection setups over the S1 interface, that is, the
number of times that the eNodeB sends an INITIAL UE MESSAGE message to the MME and
the number of times the eNodeB receives the first message over the S1 interface from the MME,
respectively. The INITIAL UE MESSAGE message is the first message that the eNodeB sends
to the MME over the S1 interface. This message is used to transmit UE-related NAS layer
configuration data to the MME. The MME sets up S1 signaling connections based on NAS
information in the message. The first message that the eNodeB received from the MME over
the S1 interface can be the INITIAL CONTEXT SETUP REQUEST, DOWNLINK NAS
TRANSPORT, or UE CONTEXT RELEASE COMMAND message. If the message is received,
an S1 signaling connection is set up successfully.
Measurement Points
As shown at point A in Figure 2-39, the L.S1Sig.ConnEst.Att counter is incremented by 1 each
time the eNodeB sends an INITIAL UE MESSAGE message to the MME.
Figure 2-39
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the E-RAB setup duration. The E-RAB setup is initiated by a UE when
the UE requests a service from the radio network. The setup is implemented through the initial
UE context setup or the E-RAB setup procedure.
Measurement Points
As shown at points A and B in Figure 2-40, the eNodeB records the time points when the eNodeB
receives an INITIAL CONTEXT SETUP REQUEST message from the MME and sends the
corresponding INITIAL CONTEXT SETUP RESPONSE message to the MME and saves the
interval between them as a sample regardless of the number of E-RABs indicated by the
messages. As shown at points A and B in Figure 2-41, the eNodeB records the time points when
the eNodeB receives an E-RAB SETUP REQUEST message from the MME and sends the
corresponding E-RAB SETUP RESPONSE message to the MME and saves the interval between
them as a sample regardless of the number of E-RABs indicated by the messages. At the end of
a measurement period, the average and maximum of these sampling results are used as the values
As shown at points A and B in Figure 2-40, the eNodeB records the time points when the eNodeB
receives an INITIAL CONTEXT SETUP REQUEST message from the MME and sends the
corresponding INITIAL CONTEXT SETUP RESPONSE message to the MME and saves the
interval between them as a sample regardless of the number of E-RABs indicated by the
messages. At the end of a measurement period, the average and maximum of these sampling
results are used as the values of the L.E-RAB.InitEst.TimeAvg and L.E-RAB.InitEst.TimeMax
counters, respectively. The initial E-RAB setup duration is not counted if the initial E-RAB setup
fails.
Figure 2-40
Figure 2-41
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
Overview
An E-RAB is the access layer bearer for carrying service data of a UE. The E-RAB release is a
process of releasing the access layer bearer resources of UEs. It represents the capability of a
cell to release access layer bearer resources for UEs. The E-RAB.Rel.Cell function subset
measures the number of normal E-RAB releases and number of abnormal E-RAB releases for
each service with a specific QCI in a cell. The release of one E-RAB is counted once. Figure
2-42 and Figure 2-43 shows the measurement points of an E-RAB release procedure during a
non-handover process. Figure 2-44 shows the measurement points of an E-RAB release
procedure initiated by the source eNodeB during a handover.
Figure 2-42
Figure 2-43
Figure 2-44
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.E-RAB.NormRel.QCI.1 L.E-RAB.Rel.MME.QCI.1
L.E-RAB.NormRel.QCI.2 L.E-RAB.Rel.MME.QCI.2
L.E-RAB.NormRel.QCI.3 L.E-RAB.Rel.MME.QCI.3
L.E-RAB.NormRel.QCI.4 L.E-RAB.Rel.MME.QCI.4
L.E-RAB.NormRel.QCI.5 L.E-RAB.Rel.MME.QCI.5
L.E-RAB.NormRel.QCI.6 L.E-RAB.Rel.MME.QCI.6
L.E-RAB.NormRel.QCI.7 L.E-RAB.Rel.MME.QCI.7
L.E-RAB.NormRel.QCI.8 L.E-RAB.Rel.MME.QCI.8
L.E-RAB.NormRel.QCI.9 L.E-RAB.Rel.MME.QCI.9
L.E-RAB.AbnormRel L.E-RAB.AbnormRel.QCI.1
L.E-RAB.AbnormRel.QCI.2
L.E-RAB.AbnormRel.QCI.3
L.E-RAB.AbnormRel.QCI.4
L.E-RAB.AbnormRel.QCI.5
L.E-RAB.AbnormRel.QCI.6
L.E-RAB.AbnormRel.QCI.7
L.E-RAB.AbnormRel.QCI.8
L.E-RAB.AbnormRel.QCI.9
L.E-RAB.AbnormRel L.E-RAB.AbnormRel.Radio
L.E-RAB.AbnormRel.TNL
L.E-RAB.AbnormRel.Cong
L.E-RAB.AbnormRel.HOFailure
L.E-RAB.NormRel L.E-RAB.NormRel.QCI.1
L.E-RAB.NormRel.QCI.2
L.E-RAB.NormRel.QCI.3
L.E-RAB.NormRel.QCI.4
L.E-RAB.NormRel.QCI.5
L.E-RAB.NormRel.QCI.6
L.E-RAB.NormRel.QCI.7
L.E-RAB.NormRel.QCI.8
L.E-RAB.NormRel.QCI.9
L.E-RAB.NormRel L.E-RAB.Rel.MME
L.E-RAB.NormRel.HOOut L.E-RAB.NormRel.HOOut.QCI.1
L.E-RAB.NormRel.HOOut.QCI.2
L.E-RAB.NormRel.HOOut.QCI.3
L.E-RAB.NormRel.HOOut.QCI.4
L.E-RAB.NormRel.HOOut.QCI.5
L.E-RAB.NormRel.HOOut.QCI.6
L.E-RAB.NormRel.HOOut.QCI.7
L.E-RAB.NormRel.HOOut.QCI.8
L.E-RAB.NormRel.HOOut.QCI.9
L.E-RAB.AbnormRel.HOOut L.E-RAB.AbnormRel.HOOut.QCI.1
L.E-RAB.AbnormRel.HOOut.QCI.2
L.E-RAB.AbnormRel.HOOut.QCI.3
L.E-RAB.AbnormRel.HOOut.QCI.4
L.E-RAB.AbnormRel.HOOut.QCI.5
L.E-RAB.AbnormRel.HOOut.QCI.6
L.E-RAB.AbnormRel.HOOut.QCI.7
L.E-RAB.AbnormRel.HOOut.QCI.8
L.E-RAB.AbnormRel.HOOut.QCI.9
L.E-RAB.AbnormRel.eNBTot L.E-RAB.AbnormRel
L.E-RAB.Rel.eNodeB L.E-RAB.Rel.eNodeB.QCI.1
L.E-RAB.Rel.eNodeB.QCI.2
L.E-RAB.Rel.eNodeB.QCI.3
L.E-RAB.Rel.eNodeB.QCI.4
L.E-RAB.Rel.eNodeB.QCI.5
L.E-RAB.Rel.eNodeB.QCI.6
L.E-RAB.Rel.eNodeB.QCI.7
L.E-RAB.Rel.eNodeB.QCI.8
L.E-RAB.Rel.eNodeB.QCI.9
L.E-RAB.Rel.MME L.E-RAB.Rel.MME.QCI.1
L.E-RAB.Rel.MME.QCI.2
L.E-RAB.Rel.MME.QCI.3
L.E-RAB.Rel.MME.QCI.4
L.E-RAB.Rel.MME.QCI.5
L.E-RAB.Rel.MME.QCI.6
L.E-RAB.Rel.MME.QCI.7
L.E-RAB.Rel.MME.QCI.8
L.E-RAB.Rel.MME.QCI.9
L.E-RAB.Rel.MME L.E-RAB.AbnormRel.MME
L.E-RAB.Rel.MME L.E-RAB.AbnormRel.MMETot
L.E-RAB.Left L.E-RAB.Left.QCI.1
L.E-RAB.Left.QCI.2
L.E-RAB.Left.QCI.3
L.E-RAB.Left.QCI.4
L.E-RAB.Left.QCI.5
L.E-RAB.Left.QCI.6
L.E-RAB.Left.QCI.7
L.E-RAB.Left.QCI.8
L.E-RAB.Left.QCI.9
L.E-RAB.Rel.S1Reset.eNodeB L.E-RAB.Rel.S1Reset.eNodeB.QCI.1
L.E-RAB.Rel.S1Reset.eNodeB.QCI.2
L.E-RAB.Rel.S1Reset.eNodeB.QCI.3
L.E-RAB.Rel.S1Reset.eNodeB.QCI.4
L.E-RAB.Rel.S1Reset.eNodeB.QCI.5
L.E-RAB.Rel.S1Reset.eNodeB.QCI.6
L.E-RAB.Rel.S1Reset.eNodeB.QCI.7
L.E-RAB.Rel.S1Reset.eNodeB.QCI.8
L.E-RAB.Rel.S1Reset.eNodeB.QCI.9
L.E-RAB.Rel.S1Reset.MME L.E-RAB.Rel.S1Reset.MME.QCI.1
L.E-RAB.Rel.S1Reset.MME.QCI.2
L.E-RAB.Rel.S1Reset.MME.QCI.3
L.E-RAB.Rel.S1Reset.MME.QCI.4
L.E-RAB.Rel.S1Reset.MME.QCI.5
L.E-RAB.Rel.S1Reset.MME.QCI.6
L.E-RAB.Rel.S1Reset.MME.QCI.7
L.E-RAB.Rel.S1Reset.MME.QCI.8
L.E-RAB.Rel.S1Reset.MME.QCI.9
L.E-RAB.AbnormRel.MMETot L.E-RAB.AbnormRel.MME
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of abnormal E-RAB releases for services with a specific QCI
ranging from 1 to 9 in a cell. An E-RAB is the access layer bearer for carrying service data of a
UE. The E-RAB release is a process of releasing the access layer bearer resources of UEs. It
represents the capability of a cell to release access layer bearer resources for UEs.
Measurement Points
As shown at point A in Figure 2-45, when the eNodeB sends an E-RAB RELEASE
INDICATION message to the MME, the corresponding counter is incremented based on the
QCI of each service each time the eNodeB determines that the E-RAB to be released carries
data and the release cause is not "Normal Release", "Detach", "User Inactivity", "CS Fallback
triggered", "UE Not Available For PS Service", "Inter-RAT Redirection", or "Successful
Handover". If the E-RAB RELEASE INDICATION message requests to release multiple E-
RABs at the same time, the corresponding counter is incremented by the number of requested
E-RAB releases in the message based on the QCI of each service.
As shown at point A in Figure 2-46, when the eNodeB sends a UE CONTEXT RELEASE
REQUEST message to the MME, all E-RABs of the UE are released. In this case, the
corresponding counter is incremented by the number of E-RABs to be released based on the
QCI of each service if the eNodeB determines that the E-RABs to be released carry data and the
release cause is not "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered",
"UE Not Available For PS Service", "Inter-RAT Redirection", "Time Critical Handover", or
"Handover Cancelled". When the MME sends a UE CONTEXT RELEASE COMMAND
message to the eNodeB, the corresponding counter is not incremented.
Figure 2-45
Figure 2-46
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of normal E-RAB releases for services with a specific QCI
ranging from 1 to 9 and the total number of normal E-RAB releases in a cell. An E-RAB is the
access layer bearer for carrying service data of a UE. The E-RAB release is a process of releasing
the access layer bearer resources of UEs. It represents the capability of a cell to release access
layer bearer resources for UEs.
Measurement Points
As shown at point A in Figure 2-47, in an E-RAB release procedure initiated by the eNodeB,
the corresponding counter is incremented based on the QCI of each service each time the eNodeB
sends an E-RAB RELEASE INDICATION message to the MME and one of the following
conditions is met:
(1) The release cause is "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered",
"UE Not Available For PS Service", or "Inter-RAT Redirection".
(2) The eNodeB determines that the E-RAB to be released does not carry data. If the E-RAB
RELEASE INDICATION message requests to release multiple E-RABs at the same time, the
corresponding counter is incremented by the number of E-RABs to be released in the message
based on the QCI of each service. In addition, the number of requested E-RAB releases contained
in the E-RAB RELEASE INDICATION messages is accumulated as the value of the L.E-
RAB.NormRel counter.
As shown at point A in Figure 2-48, in an E-RAB release procedure initiated by the MME, the
corresponding counter is incremented based on the QCI of each service each time the the eNodeB
receives an E-RAB RELEASE COMMAND message from the MME. If the E-RAB RELEASE
COMMAND message requests to release multiple E-RABs at the same time, the corresponding
counter is incremented by the number of requested E-RAB releases in the message based on the
QCI of each service. In addition, the number of requested E-RAB releases contained in the E-
RAB RELEASE COMMAND messages is accumulated as the value of the L.E-RAB.NormRel
counter.
As shown at point A in Figure 2-49, in an E-RAB releases procedure initiated by the eNodeB,
all E-RABs of the UE are released when the eNodeB sends a UE CONTEXT RELEASE
REQEUST message to the MME. In this case, the corresponding counter is incremented based
on the QCI of each service each time one the following conditions is met:
(1) The release cause is "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered",
"UE Not Available for PS Service", "Inter-RAT Redirection", "Time Critical Handover", or
"Handover Cancelled".
(2) The eNodeB determines that the E-RABs to be released do not carry data. In addition, the
number of requested E-RAB releases contained in the UE CONTEXT RELEASE REQEUST
messages is accumulated as the value of the L.E-RAB.NormRel counter. When the MME sends
a UE CONTEXT RELEASE COMMAND message to the eNodeB, the corresponding counter
is not incremented.
As shown at point B in Figure 2-49, in an E-RAB release procedure initiated by the MME, all
E-RABs of the UE are released when the eNodeB receives a UE CONTEXT RELEASE
COMMAND message from the MME. The corresponding counter is incremented based on the
QCI if the release cause is not "Successful Handover ", "Partial Handover ", "S1 intra system
Handover triggered ", "S1 inter system Handover triggered ", or "X2 Handover triggered ". The
L.E-RAB.NormRel counter is incremented based on the number of services.
Figure 2-47
Figure 2-48
Figure 2-49
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of normal E-RAB releases for outgoing handovers of services
with a specific QCI ranging from 1 to 9 and the total number of normal E-RAB releases for
outgoing handovers in the source cell when the E-RABs for incoming handovers are successfully
set up in the target cell and the corresponding E-RABs in the source cell are normally released
for outgoing handovers.
Measurement Points
Figure 2-50 shows an intra-eNodeB handover, Figure 2-51 shows an X2-based handover,
Figure 2-52 shows an S1-based handover, and Figure 2-53 shows a handover from E-UTRAN
to WCDMA network, GERAN, or TD-SCDMA network. As shown at point C in Figure 2-50,
Figure 2-51, Figure 2-52, or Figure 2-53, the corresponding counter is incremented by the
number of normal E-RAB releases in the source cell based on the QCI of each service each time
a handover is successfully executed and the source cell normally releases the E-RABs that
correspond to the E-RABs successfully set up in the target cell. The number of normal E-RAB
releases in the target cell is accumulated as the value of the L.E-RAB.NormRel.HOOut counter.
Figure 2-50
Figure 2-51
Figure 2-52
Figure 2-53
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of abnormal E-RAB releases for outgoing handovers of
services with a specific QCI and the total number of abnormal E-RAB releases for outgoing
handovers in the source cell when the E-RABs for incoming handovers fail to be set up in the
target cell and the corresponding E-RABs for outgoing handovers are abnormally released in
the source cell.
Measurement Points
Figure 2-54 shows an intra-eNodeB handover, Figure 2-55 shows an X2-based handover,
Figure 2-56 shows an S1-based handover, and Figure 2-57 shows a handover from E-UTRAN
to WCDMA network, GERAN, or TD-SCDMA network. As shown at point C in Figure 2-54,
Figure 2-55, Figure 2-56, or Figure 2-57, the corresponding counter is incremented by the
number of abnormal E-RAB releases in the source cell based on the QCI of each service each
time a handover is successfully executed and the source cell abnormally releases the E-RABs
that correspond to the E-RABs failed to be set up in the target cell. The number of corresponding
abnormal E-RAB releases in the source cell is accumulated as the value of the L.E-
RAB.AbnormRel.HOOut counter.
Figure 2-54
Figure 2-55
Figure 2-56
Figure 2-57
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the total number of abnormal E-RAB releases in a cell based on the release
cause and user data transmission. An E-RAB is the access layer bearer for carrying service data
of a UE. The E-RAB release is a process of releasing the access layer bearer resources of UEs.
It represents the capability of a cell to release access layer bearer resources for UEs.
Measurement Points
As shown at point A in Figure 2-58, the L.E-RAB.AbnormRel.eNBTot counter is incremented
each time the eNodeB sends an E-RAB RELEASE INDICATION message to the MME and the
release cause is not "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered",
"UE Not Available For PS Service", "Inter-RAT Redirection", or "Successful Handover". In this
case, if the E-RAB RELEASE INDICATION message requests to release multiple E-RABs at
the same time, the L.E-RAB.AbnormRel.eNBTot counter is incremented by the number of
requested E-RAB releases contained in the message.
As shown at point A in Figure 2-58, the L.E-RAB.AbnormRel counter is incremented each time
the eNodeB sends an E-RAB RELEASE INDICATION message to the MME and the following
conditions are met:
(1) the release cause is not "Normal Release", "Detach", "User Inactivity", "CS Fallback
triggered", "UE Not Available For PS Service", "Inter-RAT Redirection", or "Successful
Handover".
(2) The eNodeB determines that the E-RAB to be released carries data.
In this case, if the E-RAB RELEASE INDICATION message requests to release multiple E-
RABs at the same time, the L.E-RAB.AbnormRel counter is incremented by the number
requested E-RAB releases contained in the message.
As shown at point A in Figure 2-59, when the eNodeB sends a UE CONTEXT RELEASE
REQUEST message to the MME, all E-RABs of the UE are released. In this case, the L.E-
RAB.AbnormRel.eNBTot counter is incremented each time the release cause is not "Normal
Release", "Detach", "User Inactivity", "CS Fallback triggered", "UE Not Available For PS
Service", "Inter-RAT Redirection", "Time Critical Handover", or "Handover Cancelled". If
multiple E-RABs of the UE are released, the L.E-RAB.AbnormRel.eNBTot counter is
incremented by the number of E-RAB releases. When the MME sends a UE CONTEXT
RELEASE COMMAND message to the eNodeB, the corresponding counter is not incremented.
As shown at point A in Figure 2-59, when the eNodeB sends a UE CONTEXT RELEASE
REQUEST message to the MME, all E-RABs of the UE are released. In this case, the L.E-
RAB.AbnormRel.eNBTot counter is incremented each time the following two conditions are
met:
(1) The release cause is not "Normal Release", "Detach", "User Inactivity", "CS Fallback
triggered", "UE Not Available For PS Service", "Inter-RAT Redirection", "Time Critical
Handover", or "Handover Cancelled".
(2) The eNodeB determines that the E-RABs to be released carry data.
Figure 2-58
Figure 2-59
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of abnormal E-RAB releases based on the release cause in a
cell. An E-RAB is the access layer bearer for carrying service data of a UE. The E-RAB release
is a process of releasing the access layer bearer resources of UEs.
Measurement Points
As shown at point A in Figure 2-60, in an E-RAB release procedure initiated by the MME, the
L.E-RAB.AbnormRel.MMETot counter is incremented each time the eNodeB receives an E-
RAB RELEASE COMMAND message from the MME and the release cause is not "Normal
Release", "Detach, User Inactivity", "CS Fallback triggered", "UE Not Available for PS
Service", "Inter-RAT Redirection", or "Successful Handover". In addition, the L.E-
RAB.AbnormRel.MME counter is incremented each time the preceding condition is met and
the corresponding bearer carries data. If the E-RAB RELEASE COMMAND message requests
to release multiple E-RABs at the same time, the L.E-RAB.AbnormRel.MMETot and L.E-
RAB.AbnormRel.MME counters are incremented by the number of requested E-RAB releases
in the message.
As shown at point A in Figure 2-61, in a UE context release procedure initiated by the MME,
all E-RABs of the UE are released when the eNodeB receives a UE CONTEXT RELEASE
COMMAND message from the MME. In this case, the L.E-RAB.AbnormRel.MMETot counter
is incremented by the number of requested E-RAB releases in the message each time the release
cause is not "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered", "UE Not
Available for PS Service", "Inter-RAT Redirection", or "Successful Handover". In addition, the
L.E-RAB.AbnormRel.MME counter is incremented each time the preceding condition is met
and the corresponding bearer carries data.
As shown at point A in Figure 2-62, when the eNodeB sends an E-RAB RELEASE
INDICATION message to the MME, the counters are measured as follows:
(1) The L.E-RAB.AbnormRel.Radio counter is incremented each time the E-RAB is abnormally
released due to faults at the radio network layer and the eNodeB determines that the E-RAB to
be released carries data.
(2) The L.E-RAB.AbnormRel.TNL counter is incremented each time the E-RAB is abnormally
released due to faults at the transport network layer and the eNodeB determines that the E-RAB
to be released carries data.
(3) The L.E-RAB.AbnormRel.Cong counter is incremented each time the E-RAB is abnormally
released due to network congestion and the eNodeB determines that the E-RAB to be released
carries data.
For details about faults at the radio network layer and the transport network layer as well as
network congestion faults, see 3GPP TS 36.413. In addition, if the E-RAB RELEASE
INDICATION message requests to release multiple E-RABs at the same time, the corresponding
counter is incremented by the number of requested E-RAB releases based on the release cause.
As shown at point A in Figure 2-63, when the eNodeB sends a UE CONTEXT RELEASE
REQUEST message to the MME, all E-RABs of the UE are released. The counters are measured
as follows:
(1) The L.E-RAB.AbnormRel.Radio counter is incremented each time the E-RABs are
abnormally released due to faults at the radio network layer and the eNodeB determines that the
E-RABs to be released carry data.
(2) The L.E-RAB.AbnormRel.TNL counter is incremented each time the E-RABs are
abnormally released due to faults at the transport network layer and the eNodeB determines that
the E-RABs to be released carry data.
(3) The L.E-RAB.AbnormRel.Cong counter is incremented each time the E-RABs are
abnormally released due to network congestion (including preemption and resource insufficient)
and the eNodeB determines that the E-RABs to be released carry data.
For details about faults at the radio network layer and the transport network layer as well as
network congestion faults, see 3GPP TS 36.413.
(4) The L.E-RAB.AbnormRel.HOFailure counter is incremented each time the E-RABs are
abnormally released due to handover failures and the eNodeB determines that the E-RABs to
be released carry data.
The corresponding counters are incremented by the number of requested E-RAB releases based
on the release cause. When the MME sends a UE CONTEXT RELEASE COMMAND message
to the eNodeB, the corresponding counter is not incremented.
Figure 2-60
Figure 2-61
Figure 2-62
Figure 2-63
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of released E-RABs of UEs in the uplink out-of-
synchronization state in a cell.
Measurement Points
As shown at point A in Figure 2-64, Figure 2-65, Figure 2-66, or Figure 2-67, when the UE
is in the uplink out-of-synchronization state, the L.E-RAB.Release.Unsyn counter is
incremented by 1 in any of the following scenarios:
- The eNodeB receives an E-RAB RELEASE COMMAND message from the MME without
sending the corresponding E-RAB RELEASE INDICATION message to the MME.
- The eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME
without sending the corresponding UE CONTEXT RELEASE REQUEST message to the MME.
In each scenario, if the message requests to release multiple E-RABs, the corresponding counter
is incremented by the number of requested E-RAB releases in the message.
Figure 2-64
Figure 2-65
Figure 2-66
Figure 2-67
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.6.8 Total Number of E-RABs of UEs When the UEs Transit from the Uplink-
synchronized State to the Uplink Out-of-Synchronization State
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total number of E-RABs of UEs when the UEs transit from the uplink-
synchronized state to the uplink out-of-synchronization state in a cell.
Measurement Points
When UEs transit from the uplink-synchronized state to the uplink out-of-synchronization state
in a cell, the total number of E-RABs contained in the UE contexts is used as the value of the
counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of E-RAB releases initiated by eNodeB for services with a
specific QCI ranging from 1 to 9 and the total number of E-RAB releases initiated by the eNodeB
in a cell.
Measurement Points
As shown at point A in Figure 2-68, the corresponding counter is incremented based on the QCI
of each service each time the eNodeB sends the E-RAB RELEASE INDICATION message to
the MME. If the E-RAB RELEASE INDICATION message requests to release multiple E-RABs
at the same time, the corresponding counter is incremented by the number of requested E-RAB
releases based on the QCI of each service in the message.
As shown at point A in Figure 2-69, the corresponding counter is incremented based on the QCI
of each service each time the eNodeB sends the UE CONTEXT RELEASE REQUEST message
to the MME and all E-RABs of the UE are released. If multiple E-RABs of the UE have been
set up, the corresponding counter is incremented by the number of requested E-RAB releases
based on the QCI of each service.
Figure 2-68
Figure 2-69
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of E-RAB releases initiated by the MME for services with a
specific QCI ranging from 1 to 9 in a cell and the total number of E-RAB releases initiated by
the MME in a cell.
Measurement Points
As shown at point A in Figure 2-70, the corresponding counter is incremented based on the QCI
of each service each time the MME sends the E-RAB RELEASE COMMAND message to the
eNodeB. If the E-RAB RELEASE COMMAND message requests to release multiple E-RABs
at the same time, the corresponding counter is incremented by the number of requested E-RAB
releases based on the QCI of each service in the message.
As shown at point A in Figure 2-71, the corresponding counter is incremented based on the QCI
of each service each time the MME sends the UE CONTEXT RELEASE COMMAND message
to the eNodeB and all E-RABs of the UE are released. If multiple E-RABs of the UE have been
set up, the corresponding counter is incremented by the number of requested E-RAB releases
based on the QCI of each service.
Figure 2-70
Figure 2-71
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of remaining E-RABs for services with a specific QCI ranging
from 1 to 9 in a cell and the total number of remaining E-RABs in a cell.
Measurement Points
The number of E-RABs not released in a cell is sampled based on the QCI of each service per
measurement period. At the end of a measurement period, the sampling result is used as the
value of the corresponding counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of E-RAB releases initiated by the eNodeB for services with
a specific QCI ranging from 1 to 9 because of the S1 RESET. An E-RAB is the access layer
bearer for carrying service data of a UE. The E-RAB release is a process of releasing the access
layer bearer resources of UEs.
Measurement Points
As shown at point A in Figure 2-72, the corresponding counter is incremented based on the QCI
of each service each time the eNodeB sends a S1 RESET message to the MME. If the S1 RESET
message request to release multiple E-RABs at the same time, the corresponding counter is
incremented by the number of requested E-RAB releases based on the QCI of each service. In
addition, the number of E-RAB releases initiated by the eNodeB because of the S1 RESET is
accumulated as the value of the L.E-RAB.Rel.S1Reset.eNodeB counter.
Figure 2-72
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.6.13 Number of E-RAB Releases Initiated by the MME Because of the S1 RESET
in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of E-RAB releases initiated by the MME for services with a
specific QCI ranging from 1 to 9 because of the S1 RESET in a cell. An E-RAB is the access
layer bearer for carrying service data of a UE. The E-RAB release is a process of releasing the
access layer bearer resources of UEs.
Measurement Points
As shown at point A in Figure 2-73, the corresponding counter is incremented based on the QCI
of each service each time the MME sends a S1 RESET message to the eNodeB. If the S1 RESET
message requests to release multiple E-RABs at the same time, the corresponding counter is
incremented by the number of requested E-RAB releases based on the QCI of each service. In
addition, the number of E-RAB releases initiated by the MME because of the S1 RESET is
accumulated as the value of the L.E-RAB.Rel.S1Reset.MME counter.
Figure 2-73
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
An E-RAB is an access layer bearer for carrying service data of users. The E-RAB setup success
rate in a cell directly represents the capability of the cell to provide E-RAB connections for users.
The E-RAB.EstFail.Cell function subset measures the number of E-RAB setup failures for
different causes in a cell. One E-RAB setup failure is counted once. Figure 2-74 shows the
measurement points in a failed E-RAB setup procedure.
Figure 2-74
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.E-RAB.FailEst.RNL L.E-RAB.FailEst.NoReply
L.E-RAB.FailEst.NoRadioRes
L.E-RAB.FailEst.SecurModeFail
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of E-RAB setup failures due to different causes in a cell. An
E-RAB is the access layer bearer for carrying service data of users. The E-RAB setup success
rate in a cell directly represents the capability of the cell to provide E-RAB connection setups
for users. The counters indicate the number of E-RAB setup failures due to different causes on
the network.
Measurement Points
During the initial UE context setup procedure or the E-RAB setup procedure, the corresponding
counter is incremented each time the E-RAB setup is failed due to faults on the MME side, faults
at the transport network layer, faults at the radio network layer, radio resource allocation failures,
security mode configuration failures, or no responses from the UE. The counters are measured
as follows:
As shown at point A in Figure 2-75, the L.E-RAB.FailEst.MME counter is incremented each
time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST message from the MME
but the message fails the validity check performed by the eNodeB, or the INITIAL CONTEXT
SETUP REQUEST message cannot be processed due to an interaction of the initial UE context
setup procedure and other S1AP-related procedures. If the INITIAL CONTEXT SETUP
REQUEST message requests to set up multiple E-RABs at the same time, the counter is
incremented by the number of requested E-RAB setups. A validity check failure may be caused
by an error in the message or a repeated E-RAB ID. A failure to process the message due to an
interaction of the initial UE context setup procedure and other S1AP-related procedures may
occur when the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the
MME during the UE context setup procedure.
As shown at point A in Figure 2-75, the corresponding counter is incremented each time the
eNodeB fails to set up the E-RAB and sends an INITIAL CONTEXT SETUP RESPONSE
message or an INITIAL CONTEXT SETUP FAILURE message to the MME after receiving an
INITIAL CONTEXT SETUP REQUEST message from the MME. The L.E-RAB.FailEst.TNL
counter is incremented each time the E-RAB setup failure is caused by faults at the transport
network layer. The L.E-RAB.FailEst.RNL counter is incremented each time the failure is caused
by faults at the radio network layer. For details about faults at the transport network layer and
the radio network layer, see 3GPP TS36.413. The L.E-RAB.FailEst.NoRadioRes counter is
incremented each time the failure is caused by insufficient radio resources. If there are multiple
E-RAB setup failures, the corresponding counter is incremented by the number of E-RAB setup
failures. The measuring conditions of the L.E-RAB.FailEst.RNL counter involve the measuring
conditions of the L.E-RAB.FailEst.NoRadioRes, L.E-RAB.FailEst.SecurModeFail, and L.E-
RAB.FailEst.NoReply counters.
As shown at point A in Figure 2-76, the corresponding counter is incremented each time the
eNodeB fails to set up the E-RAB and sends an E-RAB SETUP RESPONSE message to the
MME after receiving an E-RAB SETUP REQUEST message from the MME. The L.E-
RAB.FailEst.TNL counter is incremented each time the failure is caused by faults at the transport
network layer. The L.E-RAB.FailEst.RNL counter is incremented each time the failure is caused
by faults at the radio network layer. For details about faults at the transport network layer and
the radio network layer, see 3GPP TS36.413. The L.E-RAB.FailEst.NoRadioRes counter is
incremented each time the failure is caused by insufficient radio resources. If there are multiple
E-RAB setup failures, the corresponding counter is incremented by the number of E-RAB setup
failures. The measuring conditions of the L.E-RAB.FailEst.RNL counter involve the measuring
conditions of the L.E-RAB.FailEst.NoRadioRes, L.E-RAB.FailEst.SecurModeFail, and L.E-
RAB.FailEst.NoReply counters.
Figure 2-75
Figure 2-76
Figure 2-77
Figure 2-78
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
An E-RAB is an access layer bearer for carrying service data of users. The E-RAB modification
success rate in a cell directly represents the capability of the cell to provide E-RAB modifications
for users. The E-RAB.Modify.Cell function subset measures the number of E-RAB modification
attempts and the number of successful E-RAB modifications for each service with a different
QCI in a cell, and the number of E-RAB modification failures caused by insufficient radio
resources in a cell. The modification of one E-RAB is counted once. Figure 2-79 shows the
measurement points in an E-RAB modification procedure.
Figure 2-79
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.E-RAB.AttModify L.E-RAB.AttModify.QCI.1
L.E-RAB.AttModify.QCI.2
L.E-RAB.AttModify.QCI.3
L.E-RAB.AttModify.QCI.4
L.E-RAB.AttModify.QCI.5
L.E-RAB.AttModify.QCI.6
L.E-RAB.AttModify.QCI.7
L.E-RAB.AttModify.QCI.8
L.E-RAB.AttModify.QCI.9
L.E-RAB.SuccModify L.E-RAB.SuccModify.QCI.1
L.E-RAB.SuccModify.QCI.2
L.E-RAB.SuccModify.QCI.3
L.E-RAB.SuccModify.QCI.4
L.E-RAB.SuccModify.QCI.5
L.E-RAB.SuccModify.QCI.6
L.E-RAB.SuccModify.QCI.7
L.E-RAB.SuccModify.QCI.8
L.E-RAB.SuccModify.QCI.9
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of E-RAB modification attempts for each service with a
specific QCI ranging from 1 to 9 and the total number of E-RAB modification attempts in a cell.
Measurement Points
As shown at point A in Figure 2-80, the corresponding counter is incremented each time the
eNodeB receives an E-RAB MODIFY REQUEST message from the MME. If the E-RAB
MODIFY REQUEST message requests to modify multiple E-RABs at the same time, the
corresponding counter is incremented by the number of requested E-RAB modifications based
on the QCI of each service. In addition, the number of requested E-RAB modifications contained
in the E-RAB MODIFY REQUEST messages is accumulated as the value of the L.E-
RAB.AttModify counter.
Figure 2-80
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of successful E-RAB modifications for each service with a
specific QCI ranging from 1 to 9 and the total number of successful E-RAB modifications in a
cell.
Measurement Points
As shown at point B in Figure 2-81, the corresponding counter is incremented each time the
eNodeB sends an E-RAB MODIFY RESPONSE message to the MME. If the E-RAB MODIFY
RESPONSE message indicates multiple successful E-RAB modifications at the same time, the
corresponding counter is incremented by the number of successful E-RAB modifications in the
message based on the QCI of each service. In addition, the number of successful E-RAB
modifications in the message is accumulated as the value of the L.E-RAB.SuccModify counter.
Figure 2-81
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of E-RAB modification failures due to insufficient radio
resources in a cell. The eNodeB sends the E-RAB MODIFY RESPONSE message to inform the
MME of failure causes. For details, see 3GPP TS36.413.
Measurement Points
As shown at point B in Figure 2-82, when the eNodeB sends the E-RAB MODIFY RESPONSE
message to the MME, the L.E-RAB.FailModify.NoRadioRes counter is incremented if the
message indicates that the E-RAB fails to be modified and the modification failure is caused by
insufficient radio resources. If the E-RAB MODIFY RESPONSE message indicates multiple
E-RAB modification failures, this counter is incremented by the number of E-RAB modification
failures.
Figure 2-82
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The Algo.Cell function subset measures the duration of cell unavailability and cell availability
and the measurements related to load control, including congestion times and duration.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of times that uplink or downlink congestion occurs in a cell
after the congestion control feature is enabled.
Measurement Points
After the congestion control feature is enabled, the corresponding counter is incremented by 1
each time uplink or downlink congestion occurs in a cell. If the cell is in RAN sharing mode,
the corresponding counter is incremented by the number of times that uplink or downlink
congestion occurs for each operator.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the duration of downlink and uplink congestion in a cell after the
congestion control feature is enabled.
Measurement Points
The uplink and downlink congestion status are sampled per five seconds. If the cell is in uplink
or downlink congestion, the corresponding counter is incremented by 5 at that sampling point.
At the end of a measurement period, the accumulated counter values are reported. A deviation
of one sampling period may exist in the sampling timer when the timer performs time
synchronization. As a result, a deviation of one sampling period will also be generated in the
value of this counter, which affects the values of the KPIs that are calculated by using this
counter. The effects vary with the deviation in the value of the counter and calculation formulas
for the KPIs. If the cell is in RAN sharing mode and the uplink or downlink for a specified
operator is in congestion, the whole cell is in uplink or downlink congestion, respectively.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of times that a GBR service is released due to congestion in
a cell.
Measurement Points
The counter is incremented by 1 each time a GBR service is released due to congestion in a cell.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the duration of cell unavailability due to human operations, system faults,
or energy saving.
Human operations include blocking and deactivating a cell by using MML commands (BLK
CELL and DEA CELL, respectively). System faults include board faults, faults on a CPRI link,
faults on the LBBP carrying services of the cell, faults on TX or RX channels of an RF module,
unavailability of control-plane transmission resources (S1 links), unavailability of user-plane
transmission resources (IP paths), insufficiency of license resources, unavailability of clocks, or
running the BLK BRD, RST BRD, or RST BTSNODE command. Energy saving includes RF
module regular time sleep, the cell entering intelligent power-off of carriers in the same coverage
mode, intelligent power-off of carriers in the same coverage of UMTS network mode, or cell
shutdown in low power consumption mode.
Measurement Points
The duration of cell unavailability is sampled per five seconds. If a cell is unavailable, the
corresponding counter is incremented by 5 at that sampling point.At the end of a measurement
period, the sum of these sampling results is reported.A deviation of one sampling period may
exist in the sampling timer when the timer performs time synchronization. As a result, a deviation
of one sampling period will also be generated in the value of the counters, which affects the
values of the KPIs that are calculated by using the counters. The effects vary depending on the
deviation in the value of the counters and calculation formulas for the KPIs.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the availability duration of a cell.
Measurement Points
The duration of cell availability in a cell is sampled per five seconds. If the cell is available, the
counter is incremented by 5 at that sampling point. At the end of a measurement period, the sum
of these sampling results is reported. A deviation of one sampling period may exist in the
sampling timer when the timer performs time synchronization. As a result, a deviation of one
sampling period will also be generated in the value of the counter, which affects the values of
the KPIs that are calculated by using the counter. The effects vary depending on the deviation
in the value of the counter and calculation formulas for the KPIs.
Formula
None
Unit
s
Related Features
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of UE level signaling messages including the non-access
stratum (NAS) messages over the Uu interface in a cell.
Measurement Points
The L.Signal.Num.Uu counter is incremented by 1 each time the eNodeB receives or sends a
UE-level air interface signaling message, including a non-access stratum (NAS) message in a
cell.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of RRC Connection Reconfiguration messages sent in a cell
to reconfigure DRX. DRX reconfiguration includes DRX activation, DRX deactivation, or DRX
parameter reconfiguration.
Measurement Points
The L.Signal.Num.DRX.Reconfig counter is incremented by 1 each time the eNodeB sends an
RRC Connection Reconfiguration message to the UE to reconfigure DRX.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure uplink and downlink voice quality.
Measurement Points
The voice quality can be classified into Bad, Poor, Accept, Good or Excellent. The uplink and
downlink voice quality is sampled per 2.5 second in an available cell. A corresponding counter
is incremented by 1 each time the voice quality is sampled. At the end of a measurement period,
the accumulated result is used as the value of the corresponding counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measure the times that an RRC Connection Release message contains an
idleModeMobilityControlInfo IE in which E-UTRAN is configured as the highest frequency
priority in a cell.
Measurement Points
As shown at point A in Figure 2-83, the L.RRCRel.DedicatedPri.LTE.High counter is
incremented by 1 each time the eNodeB sends an RRC Connection Release message to the UE
and the message contains an idleModeMobilityControlInfo IE in which the E-UTRAN is
configured as the highest frequency priority in a cell.
Figure 2-83
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.9.10 Number of Times that the WCDMA Network is Configured as the Highest
Frequency Priority in an IMMCI IE
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the times that an RRC Connection Release message contains an
idleModeMobilityControlInfo IE in which the WCDMA network is configured with the highest
frequency priority in a cell.
Measurement Points
As shown at point A in Figure 2-84, the L.RRCRel.DedicatedPri.WCDMA.High counter is
incremented by 1 each time the eNodeB sends an RRC Connection Release message to the UE
and the message contains an idleModeMobilityControlInfo IE in which the WCDMA network
is configured as the highest frequency priority in a cell.
Figure 2-84
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measure the times that an RRC Connection Release message contains an
idleModeMobilityControlInfo IE in which GERAN is configured as the highest frequency
priority in a cell.
Measurement Points
As shown at point A in Figure 2-85, the L.RRCRel.DedicatedPri.GERAN.High counter is
incremented by 1 each time the eNodeB sends an RRC Connection Release message to the UE
and the message contains an idleModeMobilityControlInfo IE in which the GERAN is
configured as the highest frequency priority in a cell.
Figure 2-85
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-operator or intra-operator preemptions
triggered due to user limitation.
Measurement Points
The L.Cell.UserLimit.PreEmp.Num counter is incremented by 1 each time an inter-operator or
intra-operator preemption triggered due to user limitation is successfully executed.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of uplink or downlink semi-persistent scheduling times
performed in a cell.
Measurement Points
The corresponding counter is incremented by 1 each time VoIP services use uplink or downlink
semi-persistent scheduling in a cell.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of times the transmission of uplink or downlink semi-
persistent scheduling fails in a cell.
Measurement Points
The corresponding counter is incremented by 1 each time the transmission of uplink or downlink
semi-persistent scheduling for VoIP services fails in a cell.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of times that the UE enters the discontinuous reception (DRX)
in RRC_CONNECTED mode. DRX in RRC_CONNECTED mode does not include out-of-
synchronization DRX.
Measurement Points
The L.Cdrx.Enter.Num counter is incremented by 1 each time the eNodeB sends an RRC
Connection Reconfiguration message to the UE in connected mode, instructing the UE to enter
the DRX in RRC_CONNECTED mode.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of times the UE exits discontinuous reception (DRX) in
RRC_CONNECTED mode.
Measurement Points
The L.Cdrx.Exit.Num counter is incremented by 1 each time the eNodeB sends an RRC
Connection Reconfiguration message to the UE in connected mode to inform the UE to exit
DRX in RRC_CONNECTED mode.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the numbers of transmission time intervals (TTIs) for the following UEs:
Measurement Points
The total number of TTIs for UEs in active state, in active state while performing VoIP services,
in sleep state, or in sleep state while performing VoIP services after entering the DRX mode is
sampled per TTI. At the end of a measurement period, the sum of these sampling results is used
as the value of the corresponding counter.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The Traffic.DRB.Cell function subset measures the number of Data Radio Bearers (DRBs) for
services with a specific QCI in a cell.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.Traffic.DRB L.Traffic.DRB.QCI.1
L.Traffic.DRB.QCI.2
L.Traffic.DRB.QCI.3
L.Traffic.DRB.QCI.4
L.Traffic.DRB.QCI.5
L.Traffic.DRB.QCI.6
L.Traffic.DRB.QCI.7
L.Traffic.DRB.QCI.8
L.Traffic.DRB.QCI.9
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of DRBs for services with a specific QCI ranging from 1 to
9 in a cell.
Measurement Points
The number of DRBs for services with a specific QCI ranging from 1 to 9 in a cell is sampled
per second. At the end of a measurement period, the average of these sampling results is used
as the value of the corresponding counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The Traffic.Thruput.Cell function subset measures the uplink or downlink throughput of services
with a specific QCI in a cell and the duration of data transmission.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.Thrp.bits.UL L.Thrp.bits.UL.QCI.1
L.Thrp.bits.UL.QCI.2
L.Thrp.bits.UL.QCI.3
L.Thrp.bits.UL.QCI.4
L.Thrp.bits.UL.QCI.5
L.Thrp.bits.UL.QCI.6
L.Thrp.bits.UL.QCI.7
L.Thrp.bits.UL.QCI.8
L.Thrp.bits.UL.QCI.9
L.Thrp.Time.UL L.Thrp.Time.UL.QCI.1
L.Thrp.Time.UL.QCI.2
L.Thrp.Time.UL.QCI.3
L.Thrp.Time.UL.QCI.4
L.Thrp.Time.UL.QCI.5
L.Thrp.Time.UL.QCI.6
L.Thrp.Time.UL.QCI.7
L.Thrp.Time.UL.QCI.8
L.Thrp.Time.UL.QCI.9
L.Thrp.bits.DL L.Thrp.bits.DL.QCI.1
L.Thrp.bits.DL.QCI.2
L.Thrp.bits.DL.QCI.3
L.Thrp.bits.DL.QCI.4
L.Thrp.bits.DL.QCI.5
L.Thrp.bits.DL.QCI.6
L.Thrp.bits.DL.QCI.7
L.Thrp.bits.DL.QCI.8
L.Thrp.bits.DL.QCI.9
L.Thrp.Time.DL L.Thrp.Time.DL.QCI.1
L.Thrp.Time.DL.QCI.2
L.Thrp.Time.DL.QCI.3
L.Thrp.Time.DL.QCI.4
L.Thrp.Time.DL.QCI.5
L.Thrp.Time.DL.QCI.6
L.Thrp.Time.DL.QCI.7
L.Thrp.Time.DL.QCI.8
L.Thrp.Time.DL.QCI.9
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the maximum uplink traffic volume for received PDCP SDUs of services
with a specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The size of the payloads in the received PDCP SDUs of each service with a specific QCI ranging
from 1 to 9 is sampled per second in a cell. The size is accumulated at each sampling point. At
the end of a measurement period, the maximum of these sampling results is used as the value of
the corresponding counter.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the maximum downlink traffic volume for transmitted PDCP SDUs of
services with a specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The size of the payloads in the transmitted PDCP SDUs of each service with a different QCI
ranging from 1 to 9 is sampled per second in a cell. At the end of a measurement period, the
maximum of these sampling results is used as the value of the corresponding counter.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
2.2.11.3 Total Bits of Transmitted Signaling SDUs on SRBs at the PDCP Layer in a
Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total bits of transmitted signaling SDUs on SRBs at the PDCP layer
in a cell.
Measurement Points
The total bits of successfully transmitted SDUs on SRBs at the PDCP layer are sampled per
second. At the end of a measurement period, the sum of these sampling results is used as the
value of the counter.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
2.2.11.4 Total Bits of Received Signaling SDUs on SRBs at the PDCP Layer in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total bits of received signaling SDUs on SRBs at the PDCP layer in
a cell.
Measurement Points
The total bits of successfully received signaling SDUs on SRBs at the PDCP layer are sampled
per second. At the end of a measurement period, the sum of these sampling results is used as the
value of the counter.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total duration of downlink data transmission in a cell. The sampling
period is 1 second.
Measurement Points
The duration of data transmission in a cell is sampled per second. If there is downlink data
transmission within a sampling period, the sampling result is 1. At the end of a measurement
period, the sum of these sampling results is used as the value of the L.Thrp.Time.Cell.DL
counter.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total duration of uplink data transmission in a cell. The sampling period
is 1 second.
Measurement Points
The duration of data transmission in a cell is sampled per second. If there is uplink data
transmission within a sampling period, the sampling result is 1. At the end of a measurement
period, the sum of these sampling results is used as the value of the L.Thrp.Time.Cell.UL
counter.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
2.2.11.7 Duration of Data Transmission for Services with a Specific QCI in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the duration of data transmission for services with a specific QCI ranging
from 1 to 9 in a cell.
Measurement Points
The duration of data transmission for each service with a specific QCI ranging from 1 to 9 in a
cell is sampled per second. If there is uplink or downlink data transmission within this second,
the sampling result is 1. At the end of a measurement period, the sum of these sampling results
is used as the value of the corresponding counter based on the QCI. A deviation of one sampling
period may exist in the sampling timer when the timer performs time synchronization. As a
result, a deviation of one sampling period will also be generated in the value of the corresponding
counter, which affects the values of the KPIs that are calculated by using the counter. The effects
vary with the deviation in the value of the counter and calculation formulas for the KPIs.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total duration of UE data transmission in a cell.
Measurement Points
The duration of UE data transmission in a cell is sampled per second. If there is uplink or
downlink data transmission for a UE within the second, the sampling result is one second. At
the end of a measurement period, the sum of these sampling results for all UEs is used as the
value of the counter. A deviation of one sampling period may exist in the sampling timer when
the timer performs time synchronization. As a result, a deviation of one sampling period will
also be generated in the value of the counter, which affects the values of the KPIs that are
calculated by using the counter. The effects vary depending on the deviation in the value of the
counter and calculation formulas for the KPIs.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the total traffic volume of received PDCP SDUs for services with a specific
QCI ranging from 1 to 9 in a cell.
Measurement Points
The size of the payloads in the received PDCP SDUs of each service with a specific QCI is
sampled in a cell. At the end of a measurement period, the sum of these sampling results is used
as the value of the corresponding counter.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the total uplink transmit duration of PDCP SDUs for all UEs in a cell.
Measurement Points
The receive duration of uplink PDCP SDUs for each service with a specific QCI ranging from
1 to 9 in a cell is sampled per millisecond. If there is uplink data transmission within this
millisecond, the sampling result of the corresponding counter is 1. At the end of a measurement
period, the sum of these sampling results is used as the value of the corresponding counter.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the total traffic volume of transmitted PDCP SDUs for services with a
specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The size of the payloads in the transmitted PDCP SDUs of each service with a specific QCI is
sampled in a cell. At the end of a measurement period, the sum of these sampling results is used
as the value of the corresponding counter.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the total downlink transmit duration of PDCP SDUs for all UEs in a cell.
Measurement Points
The transmit duration of downlink PDCP SDUs transmitted to all UEs for each service with a
specific QCI ranging from 1 to 9 is sampled per millisecond in a cell. If there is downlink data
to be transmitted within a millisecond, the corresponding counter is incremented by 1.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
2.2.11.13 Total Bits of User Data Received at the PDCP Layer from CEUs in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total bits of user data received at the PDCP layer from CEUs in a cell.
Measurement Points
The sum of the bits of user data received at the PDCP layer from all CEUs in a cell within a
measurement period is used as the value of the L.Thrp.bits.UL.CEU counter.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
2.2.11.14 Total Duration in Which User Data From CEUs Is Received at the PDCP
Layer in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total duration in which user data from CEUs is received at the PDCP
layer in a cell.
Measurement Points
The sum of the duration in which user data from CEUs is received at the PDCP layer in a cell
within a measurement period is used as the value of the L.Thrp.Time.UL.CEU counter.
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
2.2.11.15 Total Bits of User Data Transmitted at the PDCP Layer to CEUs in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total bits of user data transmitted at the PDCP layer to downlink CEUs
in a cell.
Measurement Points
The sum of the bits of user data transmitted at the PDCP layer to CEUs in a cell within a
measurement period is used as the value of the L.Thrp.bits.DL.CEU counter.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
2.2.11.16 Total Duration in Which User Data Is Transmitted to CEUs at the PDCP
Layer in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total duration in which user data is transmitted to CEUs at the PDCP
layer in a cell.
Measurement Points
The sum of the duration in which user data is transmitted at the PDCP layer to CEUs in a cell
within a measurement period is used as the value of the L.Thrp.Time.DL.CEU counter.
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total volume of downlink SDUs transmitted by activated CA UEs at
the PDCP layer in a cell.
Measurement Points
The payloads of downlink data successfully transmitted at the PDCP layer to activated CA UEs
in a cell are measured. The sum of these measurement results is used as the value of the
L.Thrp.bits.DL.CAUser counter.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the duration for activated CA UEs transmitting downlink data at the PDCP
layer in a cell.
Measurement Points
The transmit duration of downlink PDCP SDUs transmitted to activated CA UEs is sampled per
millisecond. The eNodeB determines that an activated CA UE transmits downlink PDCP SDUs
within a millisecond, the L.Thrp.Time.DL.CAUser counter is incremented by 1. At the end of
a measurement period, the sum of these sampling results is used as the value of the corresponding
counter.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total duration of downlink data transmission in a cell. The sampling
period is 1 millisecond.
Measurement Points
The duration of data transmission in a cell is sampled per millisecond. If there is downlink data
transmission within a sampling period, the sampling result is 1. At the end of a measurement
period, the sum of these sampling results is used as the value of the
L.Thrp.Time.Cell.DL.HighPrecision counter.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total duration of uplink data transmission in a cell. The sampling period
is 1 millisecond.
Measurement Points
The duration of data transmission in a cell is sampled per millisecond. If there is uplink data
transmission within a sampling period, the sampling result is 1. At the end of a measurement
period, the sum of these sampling results is used as the value of the
L.Thrp.Time.Cell.UL.HighPrecision counter.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
2.2.11.21 Downlink traffic volume sent in the last TTI before the buffer is empty
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the traffic volume sent in the last TTI before the DRB downlink buffer is
empty for services with a specific QCI.
Measurement Points
The downlink traffic volume sent in the last TTI for services with a specific QCI ranging from
1 to 9 before the buffer is empty is measured in the cell.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
2.2.11.22 Data transmit duration except the last TTI before the downlink buffer is
empty
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the data transmit duration except the last TTI before the DRB downlink
buffer is empty for services with a specific QCI.
Measurement Points
The data transmit duration of downlink PDCP SDUs for each service with a specific QCI ranging
from 1 to 9 in a cell is sampled per millisecond. If there is downlink data transmission within
this millisecond, the sampling result of the corresponding counter is 1, excluding the last TTI
before the buffer is empty. At the end of a measurement period, the sum of these sampling results
is used as the value of the corresponding counter.
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
2.2.11.23 Traffic Volume of Uplink PDCP SDUs Sent in the Last TTI Before the UE
Buffer is Empty
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the uplink traffic volume sent in the last TTI before the UE buffer is empty
in a cell.
Measurement Points
The uplink traffic volume sent in the last TTI before the UE buffer is empty is measured in a
cell.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
2.2.11.24 Uplink Data Transmit Duration Except the Last TTI Before the UE Buffer
is Empty
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the uplink data transmit duration except the last TTI before the UE buffer
is empty in a cell.
Measurement Points
The data transmit duration of uplink PDCP SDUs in a cell is sampled per millisecond. If there
is uplink data transmission within this millisecond, the sampling result of the corresponding
counter is 1, excluding the last TTI before the UE buffer is empty. At the end of a measurement
period, the sum of the sampling results is used as the value of the
L.Thrp.Time.UE.UL.RmvLastTTI counter.
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
2.2.11.25 Uplink Traffic Volume of PDCP SDUs Scheduled for Small Packets
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the traffic volume of PDCP SDUs scheduled for small packets in a cell.
Measurement Points
An uplink packet whose PDCP SDU is scheduled before the eNodeB receives a buffer status
report (BSR) or is received by the eNodeB when the uplink buffer of the UE is empty is a small
packet. The traffic volume of these small packets received in a measurement period in a cell is
accumulated as the value of the L.Thrp.bits.UE.UL.SmallPkt counter.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
2.2.11.26 Uplink Data Transmission Duration Except that for Small Packets
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the uplink data transmission duration except that for small packets in a
cell.
Measurement Points
The duration from the time that the uplink buffer of the UE is not empty to the time that the
uplink buffer of the UE is empty is sampled in a cell. A buffer status report (BSR) indicates the
data amount of the uplink buffer of the UE. The sampling result excluding the last TTI before
the UE buffer is empty is used as the value of the L.Thrp.Time.UE.UL.RmvSmallPkt counter.
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
Overview
The Traffic.PDCP.Cell function subset measures the number of downlink signaling SDUs
transmitted from the PDCP layer to the RLC layer, number of downlink traffic SDUs transmitted
from the PDCP layer to the RLC layer for services with a specific QCI, number of discarded
downlink signaling SDUs transmitted from the PDCP layer to the RLC layer, number of
discarded downlink traffic SDUs transmitted from the PDCP layer to the RLC layer for services
with a specific QCI, number of uplink signaling SDUs received by the PDCP layer from the
RLC layer, or number of discarded uplink signaling SDUs received by the PDCP layer from the
RLC layer.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
PDCP SDUs may be discarded after being received and before being sent over the air interface.
The counters measure the number of discarded downlink traffic PDCP SDUs for services with
a specific QCI ranging from 1 to 9 in a cell. If this cell is an SCell of a CA UE, SDUs that are
discarded at the MAC layer by the CA UE are also counted in this counter.
Measurement Points
The corresponding counter is incremented by 1 each time a PDCP SDU is discarded before being
sent over the air interface.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the compression rate of headers of all downlink PDCP SDUs after the
Robust Header Compression (ROHC) in a cell. Only the PDCP SDUs whose headers are
compressed by the ROHC algorithm are measured.
Measurement Points
When ROHC is used to compress the headers of downlink PDCP SDUs to be transmitted in a
cell, the total sizes of the headers before and after compression are counted within a measurement
period. The rate of the total size of the headers after compression to the total size of the headers
before compression is used as the value of the counter. If ROHC is disabled within a
measurement period, the value of this counter is invalid.
Formula
None
Unit
%
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the compression rate of headers and payloads of all downlink PDCP SDUs
after the ROHC in a cell. Only the PDCP SDUs that are compressed by the ROHC algorithm
are measured.
Measurement Points
When ROHC is used to compress the headers of downlink PDCP SDUs to be transmitted in a
cell, the total sizes of the PDCP SDUs before and after compression are counted within a
measurement period. The rate of the total size of the PDCP SDUs after compression to the total
size of the PDCP SDUs before compression is used as the value of the counter. If ROHC is
disabled within a measurement period, the value of this counter is invalid.
Formula
None
Unit
%
Related Features
Counter Name Feature ID Feature Name
2.2.12.4 Decompression Failure Rate of Uplink PDCP SDUs After the ROHC
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the decompression failure rate of all uplink PDCP SDUs after the ROHC
in a cell.Only the PDCP SDUs that are compressed by the ROHC algorithm are measured.
Measurement Points
When the received uplink PDCP SDUs need to be decompressed in a cell, the number of PDCP
SDUs that fail to be decompressed and the number of uplink PDCP SDUs to be decompressed
are calculated respectively. The decompression failure rate is counted within a measurement
period.The rate of the number of PDCP SDUs that fail to be decompressed to the number of
uplink PDCP SDUs to be decompressed is used as the value of the counter. If ROHC is disabled
within a measurement period, the value of this counter is invalid.
Formula
None
Unit
%
Related Features
Counter Name Feature ID Feature Name
2.2.12.5 Number of Transmitted Downlink Traffic PDCP SDUs for DRB Services
in a Cell over the Uu Interface
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of transmitted downlink traffic PDCP SDUs for DRB services
with a specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The number of transmitted downlink traffic PDCP SDUs for DRB services with a specific QCI
ranging from 1 to 9 is sampled per second. At the end of a measurement period, the sum of these
sampling results is used as the value of the corresponding counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the decompression rate of headers of all uplink PDCP SDUs after robust
header compression (ROHC) in a cell. Only the PDCP SDUs whose headers are compressed by
the ROHC algorithm are measured.
Measurement Points
When ROHC is used to decompress the headers of uplink PDCP SDUs received in a cell, the
total sizes of the headers before and after decompression are counted within a measurement
period. The rate of the total size of the headers before decompression to the total size of the
headers after decompression is used as the value of the counter. If ROHC is disabled within a
measurement period, the value of this counter is invalid.
Formula
None
Unit
%
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the decompression rate of headers and payloads of all downlink PDCP
SDUs after the robust header compression (ROHC) in a cell. Only the PDCP SDUs whose
headers are compressed by the ROHC algorithm are measured.
Measurement Points
When ROHC is used to decompress the headers of uplink PDCP SDUs received in a cell, the
total sizes of the PDCP SDUs before and after decompression are counted within a measurement
period. The rate of the total size of the PDCP SDUs before decompression to the total size of
the PDCP SDUs after decompression is used as the value of the counter. If ROHC is disabled
within a measurement period, the value of this counter is invalid.
Formula
None
Unit
%
Related Features
Counter Name Feature ID Feature Name
Overview
The Paging.Cell function subset measures the number of received paging messages over the S1
interface, number of paging attempts to UEs over the Uu interface, and number of discarded
paging messages from the MME to UEs in a cell.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of paging messages received by the eNodeB over the S1
interface in a cell.
Measurement Points
As shown at point A in Figure 2-86, the counter is incremented by 1 each time the eNodeB
receives a paging message from the MME and at least one tracking area identifier (TAI) of the
cell is contained in the TAI list in the paging message.
Figure 2-86
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of UEs contained in paging messages that the eNodeB sends
to UEs over the Uu interface.
Measurement Points
As shown at point A in Figure 2-87, the counter is incremented based on the number of UEs
contained in paging messages each time the eNodeB sends a paging message to UEs over the
Uu interface.
Figure 2-87
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful paging responses from the UE in a cell.
Measurement Points
as shown at point A in Figure 2-88, the counter is incremented by 1 each time the eNodeB
receives an RRC Connection Request message from the UE and the Establishment Cause
information element of the message is "mt-Access".
Figure 2-88
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.13.4 Number of Discarded Paging Messages from the MME to UEs in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of paging messages discarded by the eNodeB due to flow
control in a cell. The messages are sent from the MME to UEs in a cell.
Measurement Points
The counter is incremented by 1 each time the eNodeB discards a paging message due to flow
control in a cell.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of paging messages that are transmitted from the eNodeB to
UEs due to system information changes.
Measurement Points
As shown at point A in Figure 2-89, the counter is incremented each time the eNodeB sends a
paging message to UEs over the Uu interface and the paging message contains a field indicating
system information changes.
Figure 2-89
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of paging messages discarded due to paging channel
congestion in a cell.
Measurement Points
When the traffic volume of paging message is too large, the buffer is insufficient for these paging
messages and some paging messages are discarded. The counter is incremented by 1 each time
a paging message is discarded in this case.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The security mode configuration provides integrity protection and ciphering for signaling
messages and ciphering for user data. It directly represents the capability of the cell to provide
security mode configurations for users. The SecurMode.Cell function subset measures the
number of security mode configurations received over the S1 interface, the number of security
mode commands sent over the Uu interface, and the number of responses to security modes from
the UE. Figure 2-90 shows the measurement points of security mode configuration.
Figure 2-90
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of security mode setups in different scenarios in a cell. During
a security mode configuration process, parameters related to integrity and security are negotiated
among the MME, eNodeB, and UE with the purpose to provide integrity protection and ciphering
for signaling messages and user data over the Uu interface.
Measurement Points
as shown at point A in Figure 2-91, the L.SecurMode.S1.Rx counter is incremented by 1 each
time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST message from the MME.
as shown at point B in Figure 2-91, the L.SecurMode.Cmd counter is incremented by 1 each
time the eNodeB sends a Security Mode Command message to the UE.
as shown at point C in Figure 2-91, the L.SecurMode.Cmp counter is incremented by 1 each
time the eNodeB receives a Security Mode Complete message from the UE.
as shown at point A in Figure 2-92, the L.SecurMode.Fail counter is incremented by 1 each
time the eNodeB receives a Security Mode Failure message from the UE.
Figure 2-91
Figure 2-92
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
Random access (RA) can be classified into contention-based RA and non-contention-based RA.
The RA.Cell function subset measures the number of times the preamble is received and the
number of times the Random Access Response message is sent in two RA procedures, as well
as the number of times the Contention Resolution message is sent during the contention-based
RA procedure. It is used to analyze the RA load and success rate.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.RA.GrpA.ContResolution L.RA.GrpA.ContResolution.PDCCH
L.RA.GrpB.ContResolution L.RA.GrpB.ContResolution.PDCCH
L.RA.Dedicate.Att L.RA.Dedicate.HO.Att
L.RA.Dedicate.Resp L.RA.Dedicate.HO.Resp
Counters
Counter ID Counter Name Counter Network Element
Description
Description
Contention-based preambles may belong to either group A or group B. Contention-based
preambles in group A are mandatory, and contention-based preambles in group B are optional.
The number of contention-based preambles that can be assigned to each cell and the grouping
of preambles are set by the eNodeB, and the information is broadcast on the BCH. In the UE-
initiated contention-based RA procedure, the UE determines the group of preambles based on
the eNodeB configuration on group A and group B and the UE's radio environment. Then, the
UE randomly selects a preamble and transmit it. The counters measure the number of times the
contention-based preamble in group A or B is received. They indicate the reception load of
contention-based preambles.
Measurement Points
As shown at point A in Figure 2-93, the corresponding counter is incremented by 1 each time
the eNodeB receives a contention preamble:
Figure 2-93
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.15.2 Number of Times the Random Access Response Message Is Sent After the
Contention Preamble Is Received
Counters
Counter ID Counter Name Counter Network Element
Description
Description
After receiving a contention preamble, the eNodeB sends a Random Access Response (RAR)
message to the UE if system resources are sufficient. The counters measure the number of times
the Random Access Response message is sent after the contention preamble in group A or group
B is received. They indicate the eNodeB's response to the contention preamble.
Measurement Points
As shown at point B in Figure 2-94, the corresponding counter is incremented by 1 each time
the eNodeB sends a Random Access Response message to the UE after receiving a contention
preamble:
Figure 2-94
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.15.3 Number of Times the Contention Resolution Message Is Sent After the
Contention Preamble Is Received
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of times the Contention Resolution message is sent after the
contention preamble in group A or group B is received. They indicate the success rate of the
contention RA procedure.
Measurement Points
As shown at point C in Figure 2-95, the corresponding counter is incremented by 1 each time
the eNodeB sends a Contention Resolution message to the UE after receiving a preamble:
The L.RA.GrpA.ContResolution counter is incremented by 1 if the contention preamble belongs
to group A.
As shown at point C in Figure 2-95, the corresponding counter is incremented by 1 each time
the eNodeB sends a Contention Resolution message to a UE on the PDCCH after receiving a
preamble from the UE. The counters are measured as follows:
Figure 2-95
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The non-contention-based RA procedure is used in a handover or recovery of uplink
synchronization. The preamble used in the RA procedure is the non-contention-based preamble,
which is also called dedicated preamble. It is allocated by the eNodeB. In a handover, the eNodeB
sends the preamble to the UE in the RRC signaling message. In the recovery of uplink
synchronization, the eNodeB sends the preamble to the UE in the DCI on the PDCCH. The
counters measure the total number of times the non-contention-based preamble is received in a
cell and the number of times the non-contention-based preamble is received in a cell upon
handovers to evaluate its usage.
Measurement Points
As shown at point B in Figure 2-96, the corresponding counter is incremented by 1 each time
the eNodeB receives a non-contention-based preamble:
Figure 2-96
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.15.5 Number of Times the Random Access Response Message Is Sent After the
Non-Contention-Based Preamble Is Received
Counters
Counter ID Counter Name Counter Network Element
Description
Description
After receiving the non-contention-based preamble, the eNodeB sends a Random Access
Response (RAR) message to the UE if system resources are sufficient. The counters measure
the total number of times the RAR message is sent and the number of times the RAR message
is sent due to handovers. They indicate the eNodeB's response to the non-contention-based
preamble.
Measurement Points
As shown at point C in Figure 2-97, the corresponding counter is increment by 1 each time the
eNodeB sends a Random Access Response message to the UE after receiving a Random Access
Preamble:
Figure 2-97
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of times the UE Msg3 Response message is received in the
handover-triggered non-contention-based RA procedure. It is used to evaluate the success rate
of RA procedures during handovers.
Measurement Points
As shown at point D in Figure 2-98, in the handover-triggered non-contention-based RA
procedure, the L.RA.Dedicate.HO.Msg3Rcv counter is incremented by 1 each time the eNodeB
receives a UE Msg3 Response message from the UE.
Figure 2-98
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of times the TA with a specific value range contained in the
Random Access Response message in a UE-initiated random access procedure in a cell. One
TA equals 0.52 microsecond.
Measurement Points
In a UE-initiated random access procedure, when the eNodeB sends a Random Access Response
(RAR) message to the UE after receiving a Random Access Preamble message, the
corresponding counter is incremented based on the TA value contained in the RAR message
each time the eNodeB receives the first uplink data packet that passes the cyclic redundancy
check (CRC).
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The ChMeas.Pwr.Cell function subset measures the power in a cell to analyze the overall quality
of the downlink channel.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
Downlink transmit power is allocated dynamically by the eNodeB at the MAC layer within each
TTI. The transmit power of only the PDSCH is involved in these counters. In LTE-TDD, if the
TTI at a sampling point is an uplink subframe, the measurement is sampled at the closest next
downlink subframe. The counters measure the maximum and average downlink transmit power
respectively. They are used to analyze the usage of PDSCH power.
Measurement Points
The downlink transmit power is sampled per second. At the end of a measurement period, the
maximum or average of these sampling results is used as the value of the corresponding
counter.Note that for SFN cells, the maximum or average of downlink transmit power should
be measured for all physical cells.
Formula
None
Unit
dBm
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the uplink interference and noise received by each PRB in a cell.
Measurement Points
The total power of noise floor and neighboring cell interference received by each PRB is
measured per TTI in the uplink, the eNodeB divides the total power of noise floor and
neighboring cell interference by the number of PRBs, the value is used as a sampling result.
Note for SFN cells, the average interference power and neighboring cell interference of each
PRB should be measured for all physical cells. At the end of a measurement period, the
maximum, average, and minimum of these sampling results are used as the values of the
L.UL.Interference.Max, L.UL.Interference.Avg, and L.UL.Interference.Min counters,
respectively.
Formula
None
Unit
dBm
Related Features
Counter Name Feature ID Feature Name
2.2.16.3 Receive Power of interference and noise detected of each PRB in the UL
UpPTS
Counters
Counter ID Counter Name Counter Network Element
Description
Description
Power of interference and noise detected in each PRB in the UL UpPTS.
Measurement Points
This eNodeB measures the power of interference and noise detected in the UpPTS of a selected
RRU in every 2s and calculates the average value, which indicates the average power of the
interference and noise of each PRB. The average value is used as a sampling result. At the end
of a measurement period, the average of these sampling results is used as the value of the counter.
Formula
None
Unit
dBm
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter indicates the receive power of the first symbol in the first UL subframe.
Measurement Points
The eNodeB measures the power of the first symbol in the first UL subframe of a selected RRU
in every 2s and uses the value as a sampling result. At the end of a measurement period, the
average of these sampling results is used as the value of the counter.
Formula
None
Unit
dBm
Related Features
Counter Name Feature ID Feature Name
2.2.16.5 Receive Power of the seventh (or fifth) Symbol in First UL Subframe
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter indicates the receive power of the seventh (or fifth) symbol in the first UL subframe.
Measurement Points
The eNodeB measures the power of the seventh symbol (or the fifth symbol if extended CP is
used) in the first UL subframe of a selected RRU in every 2s and uses the value as a sampling
result. At the end of a measurement period, the average of these sampling results is used as the
value of the counter.
Formula
None
Unit
dBm
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter indicates the receive power of the first symbol in the last UL subframe.
Measurement Points
The eNodeB measures the power of the first symbol in the last UL subframe of a selected RRU
in every 2s and uses the value as a sampling result. At the end of a measurement period, the
average of these sampling results is used as the value of the counter.
Formula
None
Unit
dBm
Related Features
Counter Name Feature ID Feature Name
2.2.16.7 Receive Power of the twelfth (or tenth) Symbol in the Last UL Subframe
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter indicates the receive power of the twelfth (or tenth) symbol in the last UL subframe.
Measurement Points
The eNodeB measures the power of the twelfth symbol (or the tenth symbol if extended CP is
used) in the last UL subframe of a selected RRU in every 2s and uses the value as a sampling
result. At the end of a measurement period, the average of these sampling results is used as the
value of the counter.
Formula
None
Unit
dBm
Related Features
Counter Name Feature ID Feature Name
Overview
The ChMeas.MIMO.Cell function subset measures the number of used PRBs in different
Multiple Input Multiple Output (MIMO) modes in a cell.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
Downlink MIMO is divided into eight modes: open-loop modes with the rank ranging from 1
to 4 and closed-loop modes with the rank ranging from 1 to 4. The counters measure the number
of used downlink PRBs in different MIMO modes for analyzing the PRB usage in different
scenarios.
Measurement Points
The number of used downlink PRBs in each MIMO mode is measured within the measurement
period. For cells configured with single frequency network (SFN), the number of PRBs used in
each physical cell is incremented.
In the TDD LTE system, the number of PRBs used by each related physical cell is incremented
for cells configured with Cell Combination.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.17.2 Number of RBs That Are Successfully Paired for VMIMO UEs in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of RBs that are successfully paired for VMIMO UEs in a
cell. The number of RBs that are successfully paired for VMIMO UEs is accumulated during
each subframe for uplink scheduling. Only the number of RBs for one out of each pair of UEs
is accumulated and the number of RBs in each related RRU is accumulated for an SFN cell.
Measurement Points
The number of RBs that are successfully paired for VMIMO UEs during each subframe for
uplink scheduling in a cell is sampled per second. At the end of the measurement period, the
average of these sampling results is used as the value of the L.ChMeas.VMIMO.PairPRB.Succ
counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.17.3 Number of RBs That Can Be Paired for VMIMO UEs in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of RBs that can be paired for VMIMO UEs in a cell. The
number of RBs that can be paired for VMIMO UEs is accumulated during each subframe for
uplink scheduling. The number of RBs in each related RRU is accumulated for an SFN cell.
Measurement Points
The number of RBs that can be paired for VMIMO UEs during each subframe for uplink
scheduling in a cell is sampled per second. At the end of the measurement period, the average
of these sampling results is used as the value of the L.ChMeas.VMIMO.PairPRB.Tot counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.17.4 Number of RBs for MIMO UEs That Are Successfully Paired for MUBF in
a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of RBs that are successfully paired for MUBF UEs in a cell.
The number of RBs that are successfully paired for MUBF UEs is accumulated during each
subframe for downlink scheduling. Only the number of RBs for one out of each pair of UEs is
accumulated and the number of RBs in each related RRU is accumulated for an SFN cell.
Measurement Points
The number of RBs that are successfully paired for MUBF UEs during each subframe for
downlink scheduling in a cell is sampled per second. At the end of the measurement period, the
average of these sampling results is used as the value of the L.ChMeas.MUBF.PairPRB.Succ
counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.17.5 Number of RBs for MIMO UEs That Can Be Paired for MUBF in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of RBs that can be paired for MUBF UEs in a cell. The number
of RBs that can be paired for MUBF UEs is accumulated during each subframe for downlink
scheduling. The number of RBs in each related RRU is accumulated for an SFN cell.
Measurement Points
The number of RBs that can be paired for MUBF UEs during each subframe for downlink
scheduling in a cell is sampled per second. At the end of the measurement period, the average
of these sampling results is used as the value of the L.ChMeas.MUBF.PairPRB.Tot counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
Downlink BF is divided into two modes: rank 1 and rank 2. The counters measure the number
of used downlink PRBs in different BF modes
Measurement Points
The number of used downlink PRBs in each BF mode is sampled per second. At the end of a
measurement period, the sum of these sampling results is used as the value of the corresponding
counter. A deviation of one sampling period may exist in the sampling timer when the timer
performs time synchronization. As a result, a deviation of one sampling period will also be
generated in the value of this counter, which affects the values of the KPIs that are calculated
by using this counter. The effects vary depending on the deviation in the value of this counter
and calculation formulas for the KPIs.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
Channel Quality Indicator (CQI) indicates downlink channel quality and is calculated by the
UE. The UE sends the evaluation result to the eNodeB through the uplink channel. The CQI
report is used as the input of MAC scheduling of the eNodeB. The ChMeas.CQI.Cell function
subset measures the number CQI reports with a specific value ranging from 0 to 15 in a cell and
indicates the overall quality of the downlink channel.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
Channel Quality Indicator (CQI) indicates downlink channel quality and is calculatd by the UE.
The UE sends the evaluation result to the eNodeB through the uplink channel. The CQI report
is used as the input of MAC scheduling of the eNodeB. The counters measure the number of
wideband CQI reports with a specific value ranging from 0 to 15 in a cell (if RI > 1, CQI for
each of the two codewords is calculated separately) and indicate the overall quality of the
downlink channel.
Measurement Points
The corresponding counter is incremented by 1 based on the CQI value ranging from 0 to 15
each time the eNodeB receives a wideband CQI report from a UE.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
Channel Quality Indicator (CQI) indicates downlink channel quality and is calculated by the
UE. The UE sends the evaluation result to the eNodeB through the uplink channel. The CQI
report is used as the input of MAC scheduling of the eNodeB. The counters measure the number
of periodic wideband CQI reports with a specific value ranging from 0 to 15 in single-codeword
transmission in a cell and indicate the overall quality of the downlink channel.
Measurement Points
The corresponding counter is incremented by 1 based on the CQI value ranging from 0 to 15
each time the eNodeB receives a periodic wideband CQI report from a UE in single-codeword
transmission.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
Channel Quality Indicator (CQI) indicates downlink channel quality and is calculated by the
UE. The UE sends the evaluation result to the eNodeB through the uplink channel. The CQI
report is used as the input of MAC scheduling of the eNodeB. The counters measure the number
of aperiodic wideband CQI reports with a specific value ranging from 0 to 15 in single-codeword
transmission in a cell and indicate the overall quality of the downlink channel.
Measurement Points
The corresponding counter is incremented by 1 based on the CQI value ranging from 0 to 15
each time the eNodeB receives an aperiodic wideband CQI report in single-codeword
transmission from a UE.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
Channel Quality Indicator (CQI) indicates downlink channel quality and is calculated by the
UE. The UE sends the evaluation result to the eNodeB through the uplink channel. The CQI
report is used as the input of MAC scheduling of the eNodeB. The counters measure the number
of periodic wideband CQI reports with a specific value ranging from 0 to 15 for codeword 0 in
dual-codeword transmission in a cell and indicate the overall quality of the downlink channel.
Measurement Points
The corresponding counter is incremented by 1 based on the CQI value ranging from 0 to 15
each time the eNodeB receives a periodic wideband CQI report for codeword 0 in dual-codeword
transmission from a UE.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
Channel Quality Indicator (CQI) indicates downlink channel quality and is calculated by the
UE. The UE sends the evaluation result to the eNodeB through the uplink channel. The CQI
report is used as the input of MAC scheduling of the eNodeB. The counters measure the number
of aperiodic wideband CQI reports with a specific value ranging from 0 to 15 for codeword 0
in dual-codeword transmission in a cell and indicate the overall quality of the downlink channel.
Measurement Points
The corresponding counter is incremented by 1 based on the CQI value ranging from 0 to 15
each time the eNodeB receives an aperiodic wideband CQI report for codeword 0 in dual-
codeword transmission from a UE.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
Channel Quality Indicator (CQI) indicates downlink channel quality and is calculated by the
UE. The UE sends the evaluation result to the eNodeB through the uplink channel. The CQI
report is used as the input of MAC scheduling of the eNodeB. The counters measure the number
of periodic wideband CQI reports with a specific value ranging from 0 to 15 for codeword 1 in
dual-codeword transmission in a cell and indicate the overall quality of the downlink channel.
Measurement Points
The corresponding counter is incremented by 1 based on the CQI value ranging from 0 to 15
each time the eNodeB receives a periodic wideband CQI report for codeword 1 in dual-codeword
transmission from a UE.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
Channel Quality Indicator (CQI) indicates downlink channel quality and is calculated by the
UE. The UE sends the evaluation result to the eNodeB through the uplink channel. The CQI
report is used as the input of MAC scheduling of the eNodeB. The counters measure the number
of aperiodic wideband CQI reports with a specific value ranging from 0 to 15 for codeword 1
in dual-codeword transmission in a cell and indicate the overall quality of the downlink channel.
Measurement Points
The corresponding counter is incremented by 1 based on the CQI value ranging from 0 to 15
each time the eNodeB receives an aperiodic wideband CQI report for codeword 1 in dual-
codeword transmission from a UE.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
Modulation and Coding Scheme (MCS) is the basic output of MAC scheduling. The
ChMeas.MCS.Cell function subset measures the number of times an MCS index is scheduled
in the uplink or downlink in a cell.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The uplink MCS index is an output of uplink scheduling. It corresponds to a unique modulation
order, TBS index, and redundancy version. The counters measure the number of times that the
eNodeB schedules an MCS index for a UE in the uplink, and the MCS index ranges from 0 to
31.
Measurement Points
The corresponding counter is incremented by 1 each time the eNodeB schedules an MCS index
for a UE in the uplink within a TTI.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The downlink MCS index is an output of downlink scheduling. It corresponds to a unique
modulation order and TBS index(MCS index 29, 30, or 31 corresponds to a modulation mode
for retransmission). The counters measure the number of times that the eNodeB schedules an
MCS index for UEs in the downlink, and the MCS index ranges from 0 to 31. Each codeword
is configured with an MCS. Therefore, the MCS for each codeword is counted separately. The
counters are used to analyze the downlink scheduling condition.
Measurement Points
The corresponding counter is incremented by 1 each time the eNodeB schedules an MCS index
for a UE in the downlink within a TTI.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.19.3 Number of PRBs on the PUSCH Using a Specified MCS for Scheduling in
a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of PRBs to be allocated using a specified MCS for uplink
scheduling, including HARQ retransmission.
Measurement Points
The number of PRBs on the PUSCH to be allocated using a specified MCS for uplink scheduling
in a cell is measured within the measurement period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.19.4 Number of PRBs on the PDSCH Using a Specific MCS index for Scheduling
in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the numbers of PRBs in different modes to be allocated using a specified
MCS for downlink scheduling, including HARQ retransmission. For UEs in rank 2 mode, two
codewords are transmitted at the same time. Each codeword is configured with an MCS.
Therefore, the number of PRBs in rank 2 mode for scheduling in each codeword is counted
separately.
Measurement Points
The number of PRBs on the PDSCH in rank 1 or rank 2 to be allocated using a specified MCS
for downlink scheduling in a cell is measured within the measurement period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
Physical resource blocks (PRBs) are the basic air interface resources. The ChMeas.PRB.Cell
function subset measures the usage of uplink or downlink PRBs in a cell.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The L.ChMeas.PRB.UL.Used.Avg counter measures the average number of uplink PRBs used
by PUSCH, PRACH, and PUCCH. It is used to analyze the usage of uplink PRBs.
The L.ULCoMP.RB counter measures the average number of PRBs used by UL CoMP UEs in
a cell. It is used to analyze the usage of uplink PRBs for UL CoMP UEs.
The number of uplink used PRBs is determined by the uplink traffic volume and signal quality.
Measurement Points
During a measurement period, the average number of PRBs used by all uplink channels, by
PUSCH, by PUSCH DRBs (in an SFN cell, the number of used PRBs is accumulated), and by
UL CoMP UEs is measured in a cell per millisecond.
Only after the uplink data is correctly parsed and recognized that it is transmitted on DRBs, the
number of PRBs used by PUSCH DRBs can be calculated. Therefore, if all HARQ
retransmission fails, the eNodeB cannot recognize that the data is transmitted on DRBs and the
corresponding used PRBs are not counted. During the adaptive uplink transmission, if HARQ
retransmission feedbacks were NACK and then ACK at last, the number of used PRBs is
estimated based on the data transmitted with ACK messages. As a result, the number of PRBs
actually used may differ from that calculated in these two scenarios.
In LTE TDD mode, only uplink subframes are measured. In a cell combination scenario, the
number of used PRBs in each physical cell is accumulated.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the average number of PRBs used by PDSCH and by PDSCH DRBs in
a cell. They are used to analyze the usage of downlink PRBs.
The number of downlink PDSCH PRBs is determined by the downlink traffic and quality of
signals.
Measurement Points
During a measurement period, the average number of PRBs used by PDSCH and by PDSCH
DRBs (in an SFN cell, the number of used PRBs is accumulated) is measured per millisecond
in a cell.
In LTE TDD mode, only the downlink subframes are recorded. In a cell combination scenario,
the number of used PRBs in each physical cell is accumulated.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the average number of used PUCCH PRBs in a cell. It is used to analyze
the usage of PRBs over the PUCCH.
Measurement Points
During a measurement period, the average number of used PUCCH PRBs is measured in a cell
per millisecond.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of times that the PDCCH occupies n OFDM symbols in a cell,
where n ranges from 1 to 4.
Measurement Points
The number of OFDM symbols occupied by the PDCCH in a cell is measured within the
measurement period.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of available CCEs in a cell and the number of PDCCH CCEs
used by uplink DCI (including DCI 0), downlink DCI (including DCI 1, DCI 1A, DCI 1B, DCI
1C, DCI 1D, DCI 2, DCI 2A, and DCI 2B), and common DCI (including DCI 3 and DCI 3A)
in a cell.
Measurement Points
During a measurement period, these counters measure the number of available PDCCH CCEs
and the PDCCH CCEs used by each category of DCI in a cell.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the average number of PRBs occupied by CA UEs that use the local cell
as their primary and that occupied by CA UEs that use the local cell as their secondary serving
cell in a cell.
Measurement Points
The average number of PRBs occupied by the CA UEs that use the local cell as their primary
or secondary serving cells on downlink PDSCHs is measured per millisecond within the
measurement period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of available uplink or downlink PRBs, which is related to the
system bandwidth. In single frequency network (SFN) or cell combination scenarios, the counter
values are the total number of PRBs in each physical cell. In a cell with customized bandwidth,
the actually usable PRBs are measured. In the carrier aggregation scenario, if a cell is configured
as a secondary serving cell and is not configured with an uplink frequency band, the number of
available PRBs is zero.
Measurement Points
The number of available downlink or uplink PRBs in a cell is sampled per second. At the end
of a measurement period, the average of these sampling results is used as the counter value.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the average number of PRBs used by uplink or downlink CEUs in a cell.
Measurement Points
The average number of PRBs used by uplink or downlink CEUs per millisecond in a cell is
measured within the measurement period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the average number of PRBs allocated for uplink or downlink frequency
selective scheduling. They are used to analyze the PRB usage in uplink or downlink frequency
selective scheduling.
Measurement Points
The average number of PRBs allocated for uplink or downlink frequency selective scheduling
per millisecond in a cell is measured within the measurement period.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the average number of PRBs allocated for uplink pre-scheduling in a cell.
Measurement Points
During a measurement period, the average number of PRBs allocated for uplink pre-scheduling
is measured in a cell per millisecond.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.20.11 Number of Times of DTX for PDCCH Resource Allocation with a Specific
Aggregation Level in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
After allocating PDCCH resources, the eNodeB detects the ACK, NACK, or DTX status of the
corresponding PDSCH resource on the PUCCH or PUSCH. Each time the eNodeB detects the
DTX, the corresponding counter is incremented by 1. The PDCCH resource allocations without
feedbacks (such as SIB, RAR, and paging messages) are not counted in the counter. The counter
is incremented if one of the following conditions is met: (1)The UE does not detect the PDCCH
resource allocation messages. (2) The eNodeB falsely determines that the ACK or NACK
messages as DTX messages.
Measurement Points
The corresponding counter is incremented by 1 each time the eNodeB detects DTX for PDCCH
resource allocation with aggregation level 1, 2, 4, or 8.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of times PDCCH resource allocation with aggregation level
1, 2, 4, or 8. The PDCCH resource allocations in aggregation level without feedbacks (such as
SIB, RAR, and paging messages) are not counted.
Measurement Points
The corresponding counter is incremented by 1 each time the PDCCH resources with aggregation
level 1, 2, 4 or 8 are successfully allocated.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The Traffic.MAC.Cell function subset measures the traffic volume on logical channels and
transport channels in different modulation modes in a cell.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the total number of bits of transport blocks(TBs) transmitted on the
broadcast channel (BCH) in a cell. It is the sum of bits of system information block type 1 (SIB1)
and system information (SI) transmitted on the broadcast control channel (BCCH) over the air
interface.
Measurement Points
The counter is incremented by the number of bits of the TB each time the eNodeB transmits a
TB on the BCH in a cell.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The air interface paging message is transmitted on the paging channel (PCH). The counter
measures the total number of bits of TBs transmitted on the PCH in a cell.
Measurement Points
The counter is incremented by the number of bits of the TB each time the eNodeB transmits a
TB on the PCH in a cell.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The eNodeB determines an MCS index for initial transmission of the UE based on the quality
of the downlink channel. Each MCS index corresponds to a modulation mode, such as QPSK,
16QAM, and 64QAM. The counters measure the number of TBs initially transmitted on the
downlink SCH in QPSK, 16QAM, and 64QAM modulation modes in a cell.
Measurement Points
The corresponding counter is incremented by 1 based on modulation mode each time the eNodeB
initially transmits a TB on the downlink SCH.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the corresponding counter has a deviation.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The eNodeB determines an MCS index for initial transmission of the UE based on the quality
of the downlink channel. Each MCS index corresponds to a modulation mode, such as QPSK,
16QAM, and 64QAM. The counters measure the number of bits of TBs initially transmitted on
the downlink SCH in QPSK, 16QAM, and 64QAM modulation modes in a cell.
Measurement Points
The corresponding counter is incremented by the number of bits of the TB based on modulation
mode each time the eNodeB initially transmits a TB on the downlink SCH.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the corresponding counter has a deviation.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The eNodeB determines an MCS index for retransmission of the UE based on the quality of the
downlink channel. Each MCS index corresponds to a modulation mode, such as QPSK, 16QAM,
and 64QAM. The counters measure the number of TBs retransmitted on the downlink SCH in
QPSK, 16QAM, and 64QAM modulation modes in a cell.
Measurement Points
The corresponding counter is incremented by 1 based on modulation mode each time the eNodeB
retransmits a TB on the downlink SCH.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the corresponding counter has a deviation.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The eNodeB determines an MCS index for retransmission of the UE based on the quality of the
downlink channel. Each MCS index corresponds to a modulation mode, such as QPSK, 16QAM,
and 64QAM. The counters measure the number of bits of TBs retransmitted on the downlink
SCH in QPSK, 16QAM, and 64QAM modulation modes in a cell.
Measurement Points
The corresponding counter is incremented by the number of bits of the TB based on modulation
mode each time the eNodeB retransmits a TB on the downlink SCH.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the corresponding counter has a deviation.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The eNodeB determines an MCS index for initial transmission of the UE based on the quality
of the uplink channel. Each MCS index corresponds to a modulation mode, such as QPSK,
16QAM, and 64QAM. The counters measure the number of TBs initially transmitted on the
uplink SCH in QPSK, 16QAM, and 64QAM modulation modes in a cell.
Measurement Points
The corresponding counter is incremented by 1 based on modulation mode each time the eNodeB
receives a TB initially transmitted on the uplink SCH.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the corresponding counter has a deviation.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
TDLBFD-002002 UL 64QAM
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The eNodeB determines an MCS index for initial transmission of the UE based on the quality
of the uplink channel. Each MCS index corresponds to a modulation mode, such as QPSK,
16QAM, and 64QAM. The counters measure the number of bits of TBs initially transmitted on
the uplink SCH in QPSK, 16QAM, and 64QAM modulation modes in a cell.
Measurement Points
The corresponding counter is incremented by the number of bits of the TB based on modulation
mode each time the eNodeB receives a TB initially transmitted on the uplink SCH.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the corresponding counter has a deviation.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
TDLBFD-002002 UL 64QAM
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The eNodeB determines an MCS index for retransmission of the UE based on the quality of the
uplink channel. Each MCS index corresponds to a modulation mode, such as QPSK, 16QAM,
and 64QAM. The counters measure the number of TBs retransmitted on the uplink SCH in
QPSK, 16QAM, and 64QAM modulation modes in a cell.
Measurement Points
The number of TBs is incremented by 1 based on the modulation mode each time the eNodeB
receives a TB retransmitted over the uplink SCH.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
TDLBFD-002002 UL 64QAM
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The eNodeB determines an MCS index for retransmission of the UE based on the quality of the
uplink channel. Each MCS index corresponds to a modulation mode, such as QPSK, 16QAM,
and 64QAM. The counters measure the number of bits of TBs retransmitted on the uplink SCH
in QPSK, 16QAM, and 64QAM modulation modes in a cell.
Measurement Points
The corresponding counter is incremented by the number of bits of the TB based on modulation
mode each time the eNodeB receives a TB retransmitted on the uplink SCH.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the corresponding counter has a deviation.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
TDLBFD-002002 UL 64QAM
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of downlink error TBs after initial transmission in QPSK,
16QAM, and 64QAM modulation mode.
Measurement Points
The corresponding counter is incremented by 1 based on the modulation mode each time the
eNodeB receives a downlink error TB indicator after initial transmission.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of downlink error TBs after the maximum number of
retransmissions in QPSK, 16QAM, or 64QAM modulation mode is reached.
Measurement Points
The corresponding counter is incremented by 1 based on the modulation mode each time the
eNodeB receives a downlink error TB indicator after the maximum number of retransmissions
is reached.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of uplink error TBs after initial transmission in QPSK,
16QAM, and 64QAM modulation mode.
Measurement Points
The corresponding counter is incremented by 1 based on the modulation mode each time the
eNodeB receives an uplink error TB after initial transmission.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of uplink error TBs after the maximum number of
retransmissions in QPSK, 16QAM, or 64QAM modulation mode is reached.
Measurement Points
The corresponding counter is incremented by 1 based on the modulation mode each time the
eNodeB receives an uplink error TB after the maximum number of retransmissions is reached.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the maximum uplink and downlink traffic volumes for MAC SDUs in a
cell.
Measurement Points
The number of bits of payloads transmitted in uplink or downlink (excluding retransmission) at
the MAC layer is sampled per second in a cell. At the end of a measurement period, the maximum
of the sampling results per type is used as the value of the corresponding counter.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Overview
The Traffic.User.Cell function subset measures the number of users in different uplink or
downlink scenarios in a cell. The numbers of users are measured in different mechanisms. One
mechanism is based on the user state within the sampling period. For example, the
L.Traffic.User.Data.Avg counter measures data transmission within a sampling period. Another
mechanism is based on the user state at the sampling time. For example, the L.Traffic.User.Avg
counter measures the number of users in RRC_CONNECTED mode at the sampling time. The
two mechanisms determine that the two kinds of counters may have different impacts on inter-
counter relationships in different scenarios. To count the number of CA users in an SCell, only
the L.Traffic.User.SCell.DL.Avg and L.Traffic.User.SCell.DL.Max counters are used, but other
counters related to the number of users are not used.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the average and maximum number of UEs in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of UEs in
connected mode in a cell is sampled per second. At the end of a measurement period, the average
and maximum of these sampling results are used as the values of the corresponding counters.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the average and maximum number of uplink and downlink CEUs in a
cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of uplink
and downlink CEUs in connected mode in a cell is sampled per second. At the end of a
measurement period, the average and maximum of these sampling results are used as the values
of the corresponding counters.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the average and maximum number of UEs with data in the uplink buffer
in a cell.
Measurement Points
The counters are measured based on the user state within the sampling period. The number of
UEs that are in RRC_CONNECTED mode and have data in the uplink buffer in a cell is sampled
per second. At the end of a measurement period, the average and maximum of these sampling
results are used as the values of the corresponding counters.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the average and maximum number of UEs with data in the downlink buffer
in a cell.
Measurement Points
The counters are measured based on the user state within the sampling period. The number of
UEs that are in RRC_CONNECTED mode and have data in the downlink buffer in a cell is
sampled per second. At the end of a measurement period, the average and maximum of these
sampling results are used as the values of the corresponding counters.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the average number of UL synchronized users in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of all UL
synchronized users in a cell is sampled per second. At the end of a measurement period, the
average of these sampling results is used as the value of the counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the average and maximum number of users transmitting or receiving data
in a cell.
Measurement Points
The counters are measured based on the status of users within the sampling period. The number
of users in connected mode and with data in the buffer in a cell is sampled per second. At the
end of a measurement period, the average and maximum of these sampling results is used as the
value of the corresponding counters.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the maximum number and the average number of UEs using uplink (UL)
coordinated multi-point (CoMP) in a cell within a measurement period.
Measurement Points
This kind of counters are measured based on the status of users in the sampling period. The
number of all UEs using UL CoMP in a cell is sampled per second. At the end of a measurement
period, the maximum and the average of these sampling results are used as the values of the
corresponding counters.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the average and maximum number of downlink CA UEs that use the local
cell as their primary serving cells and the average and maximum number of downlink CA UEs
that use the local cell as their secondary serving cells.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of all
downlink CA UEs in connected mode in a cell that use the local cell as their primary serving
cells or secondary serving cells is sampled per second. At the end of a measurement period, the
average and maximum of these sampling results are used as the values of the corresponding
counters.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.22.9 Average Number of Activated UEs with a Specific QCI in the Uplink Buffer
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the average number of UEs that have data with a specific QCI in the uplink
buffer in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of UEs in
RRC_CONNECTED mode that have data in the uplink buffer with a specific QCI (standardized
or extended QCI) in a cell is sampled per millisecond. At the end of a measurement period, the
average of these sampling results is used as the values of the corresponding counters. The sum
of these values is used as the value of the L.Traffic.ActiveUser.UL.QCI.Total counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.22.10 Average Number of Activated UEs with a Specific QCI in the Downlink
Buffer
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the average number of UEs that have data with a specific QCI in the
downlink buffer in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of UEs in
RRC_CONNECTED mode that have data in the downlink buffer with a specific QCI
(standardized or extended QCI) in a cell is sampled per millisecond. At the end of a measurement
period, the average of these sampling results is used as the values of the corresponding counters.
The sum of these values is used as the value of the L.Traffic.ActiveUser.DL.QCI.Total counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the average and maximum number of UEs configured with SRS resources
in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of UEs
allocated SRS resources in connected mode in a cell is sampled per second. At the end of a
measurement period, the average and maximum of these sampling results are used as the values
of the corresponding counters.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the average number of UEs on which TTI bundling takes effect in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of UEs in
connected mode on which TTI bundling takes effect in a cell is sampled per second. At the end
of a measurement period, the average of these sampling results is used as the counter value.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the average and maximum number of UEs on which ROHC takes effect
in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of connected
UEs on which ROHC takes effect in a cell is sampled per second. At the end of a measurement
period, the average and maximum of these sampling results are used as the values of the
corresponding counters.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the average number of UEs on which DRX takes effect in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of connected
UEs on which DRX takes effect in a cell is sampled per second. At the end of a measurement
period, the average of these sampling results is used as the counter value.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of UEs that have data in the downlink buffer in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of UEs that
are in RRC_CONNECTED mode and have data in the downlink buffer in a cell is sampled per
millisecond. At the end of a measurement period, the average and maximum of these sampling
results are used as the values of the corresponding counters.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of UEs that have data in the uplink buffer in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of UEs that
are in RRC_CONNECTED mode and have data in the uplink buffer in a cell is sampled per
millisecond. At the end of a measurement period, the average and maximum of these sampling
results are used as the values of the corresponding counters.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of UEs that have data in the buffer in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of UEs that
are in RRC_CONNECTED mode and have data in either the downlink or uplink buffer in a cell
is sampled per millisecond. At the end of a measurement period, the average and maximum of
these sampling results are used as the values of the corresponding counters.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The HO.IRAT.Out.Cell function subset measures the performance of inter-RAT handovers from
E-UTRAN to CDMA2000 network, WCDMA network, GERAN, or TD-SCDMA network, as
shown in Figure 2-99, Figure 2-100, and Figure 2-101.
Figure 2-99
Figure 2-100
Figure 2-101
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.IRATHO.E2C.PrepAttOut L.IRATHO.E2C.CSFB.PrepAttOut
L.IRATHO.E2C.ExecAttOut L.IRATHO.E2C.CSFB.ExecAttOut
L.IRATHO.E2C.ExecSuccOut L.IRATHO.E2C.CSFB.ExecSuccOut
L.IRATHO.E2C.ExecSuccOut L.IRATHO.E21xRTT.MMEAbnormRsp
L.IRATHO.E2HRPD.MMEAbnormRsp
L.IRATHO.E2W.PrepAttOut L.IRATHO.BlindHO.E2W.PrepAttOut
L.IRATHO.E2W.PrepAttOut L.IRATHO.SRVCC.E2W.PrepAttOut
L.IRATHO.E2W.PrepAttOut L.IRATHO.E2W.CSFB.PrepAttOut
L.IRATHO.E2W.PrepAttOut L.IRATHO.E2W.Load.PrepAttOut
L.IRATHO.E2W.RegainHPLMN.PrepAtt-
Out
L.IRATHO.E2W.ExecAttOut L.IRATHO.BlindHO.E2W.ExecAttOut
L.IRATHO.E2W.ExecAttOut L.IRATHO.SRVCC.E2W.ExecAttOut
L.IRATHO.E2W.ExecAttOut L.IRATHO.E2W.CSFB.ExecAttOut
L.IRATHO.E2W.ExecAttOut L.IRATHO.E2W.Load.ExecAttOut
L.IRATHO.E2W.RegainHPLMN.ExecAtt-
Out
L.IRATHO.E2W.ExecSuccOut L.IRATHO.BlindHO.E2W.ExecSuccOut
L.IRATHO.E2W.ExecSuccOut L.IRATHO.SRVCC.E2W.ExecSuccOut
L.IRATHO.E2W.ExecSuccOut L.IRATHO.E2W.CSFB.ExecSuccOut
L.IRATHO.E2W.ExecSuccOut L.IRATHO.E2W.Load.ExecSuccOut
L.IRATHO.E2W.RegainHPLMN.Exe-
cSuccOut
L.IRATHO.E2W.ExecSuccOut L.IRATHO.E2W.MMEAbnormRsp
L.IRATHO.E2G.PrepAttOut L.IRATHO.BlindHO.E2G.PrepAttOut
L.IRATHO.E2G.PrepAttOut L.IRATHO.SRVCC.E2G.PrepAttOut
L.IRATHO.E2G.PrepAttOut L.IRATHO.E2G.CSFB.PrepAttOut
L.IRATHO.E2G.PrepAttOut L.IRATHO.E2G.Load.PrepAttOut
L.IRATHO.E2G.ExecAttOut L.IRATHO.BlindHO.E2G.ExecAttOut
L.IRATHO.E2G.ExecAttOut L.IRATHO.SRVCC.E2G.ExecAttOut
L.IRATHO.E2G.ExecAttOut L.IRATHO.E2G.CSFB.ExecAttOut
L.IRATHO.E2G.ExecAttOut L.IRATHO.E2G.Load.ExecAttOut
L.IRATHO.E2G.ExecSuccOut L.IRATHO.BlindHO.E2G.ExecSuccOut
L.IRATHO.E2G.ExecSuccOut L.IRATHO.SRVCC.E2G.ExecSuccOut
L.IRATHO.E2G.ExecSuccOut L.IRATHO.E2G.CSFB.ExecSuccOut
L.IRATHO.E2G.ExecSuccOut L.IRATHO.E2G.Load.ExecSuccOut
L.IRATHO.E2G.ExecSuccOut L.IRATHO.E2G.MMEAbnormRsp
L.IRATHO.E2T.PrepAttOut L.IRATHO.BlindHO.E2T.PrepAttOut
L.IRATHO.E2T.PrepAttOut L.IRATHO.SRVCC.E2T.PrepAttOut
L.IRATHO.E2T.PrepAttOut L.IRATHO.E2T.CSFB.PrepAttOut
L.IRATHO.E2T.ExecAttOut L.IRATHO.BlindHO.E2T.ExecAttOut
L.IRATHO.E2T.ExecAttOut L.IRATHO.SRVCC.E2T.ExecAttOut
L.IRATHO.E2T.ExecAttOut L.IRATHO.E2T.CSFB.ExecAttOut
L.IRATHO.E2T.ExecSuccOut L.IRATHO.BlindHO.E2T.ExecSuccOut
L.IRATHO.E2T.ExecSuccOut L.IRATHO.SRVCC.E2T.ExecSuccOut
L.IRATHO.E2T.ExecSuccOut L.IRATHO.E2T.CSFB.ExecSuccOut
L.IRATHO.E2T.ExecSuccOut L.IRATHO.E2T.MMEAbnormRsp
L.CSFB.PrepAtt L.CSFB.PrepAtt.Idle
L.CSFB.PrepAtt L.CSFB.PrepAtt.Emergency
L.CSFB.PrepSucc L.CSFB.PrepSucc.Idle
L.CSFB.PrepSucc L.CSFB.PrepSucc.Emergency
L.CSFB.E2W L.CSFB.E2W.Idle
L.CSFB.E2W L.RRCRedirection.E2W.CSFB
L.IRATHO.E2W.CSFB.ExecAttOut
L.CSFB.E2W L.CSFB.E2W.Emergency
L.CSFB.E2G L.RRCRedirection.E2G.CSFB
L.IRATHO.E2G.CSFB.ExecAttOut
L.CSFB.E2G L.CSFB.E2G.Emergency
L.RRCRedirection.E2W L.RRCRedirection.E2W.Load
L.RRCRedirection.E2G L.RRCRedirection.E2G.Load
L.IRATHO.SRVCC.E2W.PrepAttOut L.IRATHO.SRVCC.LCS.E2W.PrepAttOut
L.IRATHO.SRVCC.E2W.ExecAttOut L.IRATHO.SRVCC.LCS.E2W.ExecAttOut
L.IRATHO.SRVCC.E2W.ExecSuccOut L.IRATHO.SRVCC.LCS.E2W.ExecSucc-
Out
L.IRATHO.SRVCC.E2W.ExecSuccOut L.IRATHO.SRVCC.E2W.MMEAb-
normRsp
L.IRATHO.SRVCC.E2G.PrepAttOut L.IRATHO.SRVCC.LCS.E2G.PrepAttOut
L.IRATHO.SRVCC.E2G.ExecAttOut L.IRATHO.SRVCC.LCS.E2G.ExecAttOut
L.IRATHO.SRVCC.E2G.ExecSuccOut L.IRATHO.SRVCC.LCS.E2G.ExecSucc-
Out
L.IRATHO.SRVCC.E2G.ExecSuccOut L.IRATHO.SRVCC.E2G.MMEAbnormRsp
L.IRATHO.SRVCC.E2T.PrepAttOut L.IRATHO.SRVCC.LCS.E2T.PrepAttOut
L.IRATHO.SRVCC.E2T.ExecAttOut L.IRATHO.SRVCC.LCS.E2T.ExecAttOut
L.IRATHO.SRVCC.E2T.ExecSuccOut L.IRATHO.SRVCC.LCS.E2T.ExecSucc-
Out
L.IRATHO.SRVCC.E2T.ExecSuccOut L.IRATHO.SRVCC.E2T.MMEAbnormRsp
L.CCO.E2G.ExecSuccOut L.CCO.E2G.MMEAbnormRsp
L.RRCRedirection.E2W.CSFB L.FlashCSFB.E2W
L.RRCRedirection.E2G.CSFB L.FlashCSFB.E2G
L.IRATHO.E2C.CSFB.ExecSuccOut L.IRATHO.E2C.CSFB.MMEAbnormRsp
L.IRATHO.E2W.CSFB.ExecSuccOut L.IRATHO.E2W.CSFB.MMEAbnormRsp
L.IRATHO.E2G.CSFB.ExecSuccOut L.IRATHO.E2G.CSFB.MMEAbnormRsp
L.IRATHO.E2T.CSFB.ExecSuccOut L.IRATHO.E2T.CSFB.MMEAbnormRsp
L.CSFB.E2T L.CSFB.E2T.Idle
L.IRATHO.E2W.MMEAbnormRsp L.IRATHO.SRVCC.E2W.MMEAb-
normRsp
L.IRATHO.E2G.MMEAbnormRsp L.IRATHO.SRVCC.E2G.MMEAbnormRsp
L.IRATHO.E2T.MMEAbnormRsp L.IRATHO.SRVCC.E2T.MMEAbnormRsp
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to
CDMA2000 network.
Measurement Points
As shown at point A in Figure 2-102, the L.IRATHO.E2C.PrepAttOut counter is incremented
by 1 each time the eNodeB decides to perform an inter-RAT blind handover from E-UTRAN
to CDMA2000 network or decides to perform an inter-RAT handover from E-UTRAN to
CDMA2000 after the eNodeB receives a measurement report from a UE.
Figure 2-102
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measure the number of inter-RAT handovers executions from E-UTRAN to
CDMA2000 network.
Measurement Points
As shown at point B in Figure 2-103, during an inter-RAT handover from E-UTRAN to
CDMA2000 network the L.IRATHO.E2C.ExecAttOut counter is incremented by 1 each time
the eNodeB sends a Mobility From EUTRA Command message to the UE.
Figure 2-103
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-RAT handovers from E-UTRAN to
CDMA2000 network.
Measurement Points
As shown at point C in Figure 2-104, during an inter-RAT handover from E-UTRAN to
CDMA2000 network the L.IRATHO.E2C.ExecSuccOut counter is incremented by 1 each time
the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME after
the UE is handed over from the E-UTRAN to a CDMA2000 network.
Figure 2-104
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to WCDMA
network.
Measurement Points
As shown at point A in Figure 2-105, the L.IRATHO.E2W.PrepAttOut counter is incremented
by 1 each time the eNodeB decides to perform an inter-RAT blind handover from E-UTRAN
to WCDMA network or decides to perform an inter-RAT handover from E-UTRAN to WCDMA
network after the eNodeB receives a measurement report from a UE.
Figure 2-105
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measure the number of inter-RAT handovers executions from E-UTRAN to
WCDMA network.
Measurement Points
As shown at point B in Figure 2-106, during an inter-RAT handover from E-UTRAN to
WCDMA network the L.IRATHO.E2W.ExecAttOut counter is incremented by 1 each time the
eNodeB sends a Mobility From EUTRA Command message to the UE.
Figure 2-106
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-RAT handovers from E-UTRAN to
WCDMA network.
Measurement Points
As shown at point C in Figure 2-107, during an inter-RAT handover from E-UTRAN to
WCDMA network the L.IRATHO.E2W.ExecSuccOut counter is incremented by 1 each time
the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME after
the UE is handed over from the E-UTRAN to a WCDMA network.
Figure 2-107
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to GERAN.
Measurement Points
As shown at point A in Figure 2-108, the L.IRATHO.E2G.PrepAttOut counter is incremented
by 1 each time the eNodeB decides to perform an inter-RAT blind handover from E-UTRAN
to GERAN or decides to perform an inter-RAT handover from E-UTRAN to GERAN after the
eNodeB receives a measurement report from a UE.
Figure 2-108
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measure the number of inter-RAT handovers executions from E-UTRAN to
GERAN.
Measurement Points
As shown at point B in Figure 2-109, during an inter-RAT handover from E-UTRAN to GERAN
the L.IRATHO.E2G.ExecAttOut counter is incremented by 1 each time the eNodeB sends a
Mobility From EUTRA Command message to the UE.
Figure 2-109
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-RAT handovers from E-UTRAN to
GERAN.
Measurement Points
As shown at point C in Figure 2-110, during an inter-RAT handover from E-UTRAN to GERAN
the L.IRATHO.E2G.ExecSuccOut counter is incremented by 1 each time the eNodeB receives
a UE CONTEXT RELEASE COMMAND message from the MME after the UE is handed over
from the E-UTRAN to a GERAN.
Figure 2-110
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to TD-
SCDMA network.
Measurement Points
As shown at point A in Figure 2-111, the L.IRATHO.E2T.PrepAttOut counter is incremented
by 1 each time the eNodeB decides to perform an inter-RAT blind handover from E-UTRAN
to TD-SCDMA network or decides to perform an inter-RAT handover from E-UTRAN to TD-
SCDMA network after the eNodeB receives a measurement report from a UE.
Figure 2-111
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handovers executions from E-UTRAN to TD-
SCDMA network.
Measurement Points
As shown at point B in Figure 2-112, during an inter-RAT handover from E-UTRAN to TD-
SCDMA network the L.IRATHO.E2T.ExecAttOut counter is incremented by 1 each time the
eNodeB sends a Mobility From EUTRA Command message to the UE.
Figure 2-112
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-RAT handovers from E-UTRAN to TD-
SCDMA network.
Measurement Points
As shown at point C in Figure 2-113, during an inter-RAT handover from E-UTRAN to TD-
SCDMA network the L.IRATHO.E2T.ExecSuccOut counter is incremented by 1 each time the
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME after the
UE is handed over from the E-UTRAN to a TD-SCDMA network.
Figure 2-113
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of inter-RAT handover failures for different causes. Inter-
RAT outgoing handover failures usually occur during the handover preparation phase and are
caused by faults on the MME side, no responses from the target cell of another system, or the
target cell of another system sending handover failure messages. During the handover
preparation phase, between the handover decision phase and the handover execution phase, the
handover resources are prepared. In an inter-RAT handover, a UE is handed over from the E-
UTRAN to another system to ensure service continuity in multi-RAT networking scenarios.
Measurement Points
As shown at point A in Figure 2-114, the corresponding counter is incremented by 1 based on
the handover target system each time the eNodeB does not receive a HANDOVER COMMAND
message from the MME after the eNodeB sends a HANDOVER REQUIRED message to the
MME.
If the target system is WCDMA network, the L.IRATHO.E2W.Prep.FailOut.NoReply counter
is incremented.
If the target system is GERAN, the L.IRATHO.E2G.Prep.FailOut.NoReply counter is
incremented.
If the target system is TD-SCDMA network, the L.IRATHO.E2T.Prep.FailOut.NoReply counter
is incremented.
As shown at point A in Figure 2-115, the corresponding counter is incremented by 1 based on
the handover target system each time the eNodeB receives a HANDOVER PREPARE
FAILURE message from the MME after the eNodeB sends a HANDOVER REQUIRED
message to the MME.
If the target system is WCDMA network, the L.IRATHO.E2W.Prep.FailOut.PrepFailure
counter is incremented.
If the target system is GERAN, the L.IRATHO.E2G.Prep.FailOut.PrepFailure counter is
incremented.
If the target system is TD-SCDMA network, the L.IRATHO.E2T.Prep.FailOut.PrepFailure
counter is incremented.
As shown at point A in Figure 2-116, the corresponding counter is incremented by 1 based on
the target system each time the eNodeB receives a UE CONTEXT RELEASE COMMAND
message from the MME after the eNodeB sends a HANDOVER REQUIRED message to the
MME.
Figure 2-114
Figure 2-115
Figure 2-116
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of inter-RAT blind handover attempts from E-UTRAN to
another system in a cell. Not triggered on the basis of UE measurement reports, the blind
handover is a handover in which the eNodeB specifies the target cell for the UE. In specific
networking scenarios, the eNodeB performs a blind handover to actively hand over the UE from
the source cell.
Measurement Points
As shown at point A in Figure 2-117, the corresponding counter is incremented by 1 based on
the blind handover target system each time the eNodeB decides to perform a blind handover and
sends a HANDOVER REQUIRED message to the MME. If the target system is WCDMA
network, the L.IRATHO.BlindHO.E2W.PrepAttOut counter is incremented.
Figure 2-117
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of inter-RAT blind handover executions from the E-UTRAN
to another system in a cell. Not triggered on the basis of UE measurement reports, the blind
handover is a handover in which the eNodeB specifies the target cell for the UE. In specific
networking scenarios, the eNodeB performs a blind handover to actively hand over the UE from
the target cell.
Measurement Points
As shown at point B in Figure 2-118, the corresponding counter is incremented by 1 based on
the blind handover target system each time the eNodeB decides to perform a blind handover and
sends a Mobility From EUTRA Command message to the UE.
Figure 2-118
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of successful inter-RAT blind handovers from E-UTRAN to
another system in a cell. Not triggered on the basis of UE measurement reports, the blind
handover is a handover in which the eNodeB specifies the target cell for the UE. In specific
networking scenarios, the eNodeB performs a blind handover to actively hand over the UE from
the target cell.
Measurement Points
As shown at point C in Figure 2-119, the corresponding counter is increased by 1based on the
blind handover target system each time the eNodeB decides to perform a blind handover and
receives s a UE CONTEXT RELEASE COMMAND message from the MME.
Figure 2-119
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of CSFB indicators received by the eNodeB. The MME sends
an INITIAL CONTEXT SETUP REQUEST or UE CONTEXT MODIFICATION REQUEST
message containing the information element (IE) "CS Fallback Indicator" to the eNodeB. Then,
the eNodeB triggers a CSFB based on the IE.
Measurement Points
As shown at point A in Figure 2-120, the L.CSFB.PrepAtt counter is incremented by 1 each
time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST message containing the
IE "CS Fallback Indicator" from the MME and the eNodeB determines that the CSFB procedure
is for voice services.
Figure 2-120
Figure 2-121
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of CSFB responses from the eNodeB to MMEs. During a
CSFB procedure, the eNodeB sends an INITIAL CONTEXT SETUP RESPONSE or UE
CONTEXT MODIFICATION RESPONSE message to the MME.
The eNodeB initiates a CSFB procedure based on the CS fallback indicator sent from the MME.
Measurement Points
As shown at point C in Figure 2-122, the L.CSFB.PrepSucc counter is incremented by 1 each
time the eNodeB successfully sends an INITIAL CONTEXT SETUP RESPONSE message to
the MME and the corresponding INITIAL CONTEXT SETUP REQUEST message is
determined that the CSFB procedure is for voice services.
message to the MME for an emergency call and the corresponding INITIAL CONTEXT SETUP
REQUEST message is determined that the CSFB procedure is for voice services.
Figure 2-122
Figure 2-123
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of Procedures for CSFB from E-UTRAN to Another System.
The CSFB to WCDMA network mechanism include blind redirection, blind handover, and
handover. The CSFB to GERAN mechanism includes blind redirection, blind handover, blind
CCO, redirection, handover, and CCO. The CSFB to TD-SCDMA mechanism includes blind
redirection, blind handover, redirection, and handover. The counter that measures the total
number of CSFB procedures performed by UEs and the number of CSFB procedures performed
by UEs in idle mode are measured are separately. The number of CSFB procedures performed
by UEs in the connected mode can be calculated by deducting the number of CSFB procedures
performed by UEs in idle mode from the total number of CSFB procedures performed by UEs.
Measurement Points
As shown at point A in Figure 2-124, the L.IRATHO.E2W.CSFB.PrepAttOut counter is
incremented by 1 each time the eNodeB decides to perform an inter-RAT blind handover for
CSFB to WCDMA network or the eNodeB decides to perform an inter-RAT handover for CSFB
to WCDMA network after the eNodeB receives a measurement report from the UE.
As shown at point B in Figure 2-124, the L.CSFB.E2W and
L.IRATHO.E2W.CSFB.ExecAttOut counters are incremented by 1 each time the eNodeB
performs a CSFB procedure to WCDMA network after the eNodeB sends a Mobility From
EUTRA Command message to the UE. In this case, if the CSFB procedure is initiated by a UE
in idle mode (when the UE initiates a CSFB, the initial state is determined by the eNodeB), the
L.CSFB.E2W.Idle counter is incremented by 1.
As shown at point B in Figure 2-124, the L.CSFB.E2T counter is incremented by 1 each time
the eNodeB performs a CSFB procedure to the TD-SCDMA network after the eNodeB sends a
Mobility From EUTRA Command message to the UE.
As shown at point A in Figure 2-125, the L.CSFB.E2T counter is incremented by 1 each time
the eNodeB performs a CSFB procedure to the TD-SCDMA network after the eNodeB sends
an RRC Connection Release message to the UE.
As shown at point B in Figure 2-124 or point A in Figure 2-125, the initial state of the UE must
be saved before the measurement. The L.CSFB.E2T.idle counter is incremented by 1 each time
the UE in idle mode performs a CSFB procedure to TD-SCDMA network.
Figure 2-124
Figure 2-125
Figure 2-126
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of inter-RAT redirection preparations triggered by the
eNodeB. In a redirection, the eNodeB sends an RRC Connection Release message containing
the target frequency and other access information to a UE to perform a redirection procedure.
During the procedure, the UE is released by the source cell and accesses the target cell to continue
its services.
Measurement Points
As shown at point A in Figure 2-127, the L.RRCRedirection.E2W.PrepAtt counter is
incremented by 1 each time the eNodeB decides to trigger an inter-RAT redirection from E-
UTRAN to WCDMA network.
As shown at point A in Figure 2-127, the L.RRCRedirection.E2G.PrepAtt counter is
incremented by 1 each time the eNodeB decides to trigger an inter-RAT redirection from E-
UTRAN to GERAN.
as shown at point A in Figure 2-127, the L.RRCRedirection.E2T.PrepAtt counter is incremented
by 1 each time the eNodeB decides to trigger an inter-RAT redirection from E-UTRAN to TD-
SCDMA network.
Figure 2-127
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of inter-RAT redirections triggered by the eNodeB. In a
redirection, the eNodeB sends an RRC Connection Release message containing the target
frequency and other access information to a UE to perform a redirection procedure. During the
procedure, the UE is released by the source cell and accesses the target cell to continue its
services.
Measurement Points
As shown at point A in Figure 2-128, the L.RRCRedirection.E2W counter is incremented by 1
each time the eNodeB sends an RRC Connection Release message to the UE when the eNodeB
triggers a redirection to WCDMA network.
Figure 2-128
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to WCDMA
network for SRVCC in a cell.
Measurement Points
As shown at point A in Figure 2-129, the L.IRATHO.SRVCC.E2W.PrepAttOut counter is
incremented by 1 each time the eNodeB decides to perform an inter-RAT blind handover from
E-UTRAN to WCDMA network or the eNodeB decides to perform an inter-RAT handover from
E-UTRAN to WCDMA network for SRVCC after the eNodeB receives a measurement report
from the UE.
Figure 2-129
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover executions from E-UTRAN to
WCDMA network for SRVCC in a cell.
Measurement Points
As shown at point B in Figure 2-130, during an inter-RAT handover from E-UTRAN to
WCDMA network for SRVCC the L.IRATHO.SRVCC.E2W.ExecAttOut counter is
incremented by 1 each time the eNodeB sends a Mobility From EUTRA Command message to
the UE.
Figure 2-130
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-RAT handovers from E-UTRAN to
WCDMA network for SRVCC in a cell.
Measurement Points
As shown at point C in Figure 2-131, during an inter-RAT handover from E-UTRAN to
WCDMA network the L.IRATHO.SRVCC.E2W.ExecSuccOut counter is incremented by 1
each time the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the
MME after the UE is handed over from the E-UTRAN to a WCDMA network.
Figure 2-131
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to GERAN
for SRVCC in a cell.
Measurement Points
As shown at point A in Figure 2-132, the L.IRATHO.SRVCC.E2G.PrepAttOut counter is
incremented by 1 each time the eNodeB decides to perform an inter-RAT blind handover from
E-UTRAN to GERAN or the eNodeB decides to perform an inter-RAT handover from E-
UTRAN to GERAN for SRVCC after the eNodeB receives a measurement report from the UE.
Figure 2-132
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover executions from E-UTRAN to
GERAN for SRVCC in a cell.
Measurement Points
As shown at point B in Figure 2-133, during an inter-RAT handover from E-UTRAN to GERAN
for SRVCC the L.IRATHO.SRVCC.E2G.ExecAttOut counter is incremented by 1 each time
the eNodeB sends a Mobility From EUTRA Command message to the UE.
Figure 2-133
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-RAT handovers from E-UTRAN to
GERAN for SRVCC in a cell.
Measurement Points
As shown at point C in Figure 2-134, during an inter-RAT handover from E-UTRAN to GERAN
for SRVCC the L.IRATHO.SRVCC.E2G.ExecSuccOut counter is incremented by 1 each time
the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME after
the UE is handed over from the E-UTRAN to a GERAN.
Figure 2-134
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to TD-
SCDMA network for SRVCC in a cell.
Measurement Points
As shown at point A in Figure 2-135, the L.IRATHO.SRVCC.E2T.PrepAttOut counter is
incremented by 1 each time the eNodeB decides to perform an inter-RAT handover from E-
UTRAN to TD-SCDMA network after the eNodeB receives a measurement report from the UE.
Figure 2-135
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover executions from E-UTRAN to TD-
SCDMA network for SRVCC in a cell.
Measurement Points
As shown at point B in Figure 2-136, during an inter-RAT handover from E-UTRAN to TD-
SCDMA network for SRVCC the L.IRATHO.SRVCC.E2T.ExecAttOut counter is incremented
by 1 each time the eNodeB sends a Mobility From EUTRA Command message to the UE.
Figure 2-136
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-RAT handovers from E-UTRAN to TD-
SCDMA network for SRVCC in a cell.
Measurement Points
As shown at point C in Figure 2-137, during an inter-RAT handover from E-UTRAN to TD-
SCDMA network for SRVCC the L.IRATHO.SRVCC.E2T.ExecSuccOut counter is
incremented by 1 each time the eNodeB receives a UE CONTEXT RELEASE COMMAND
message from the MME after the UE is handed over from the E-UTRAN to a TD-SCDMA
network.
Figure 2-137
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of LCS-triggered CS fallback indicators received by the
eNodeB in a cell.
Measurement Points
As shown at point A in Figure 2-138, the L.CSFB.LCS.PrepAtt counter is incremented by 1
each time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST message containing
the IE "CS Fallback Indicator" from the MME and the eNodeB determines that the CSFB
procedure is for LCS.
Figure 2-138
Figure 2-139
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.23.32 Number of Responses Sent from the eNodeB to MMEs for CSFB Triggered
by LCS
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of responses sent from the eNodeB to MMEs for CSFB
triggered by LCS.
Measurement Points
As shown at point C in Figure 2-140, the L.CSFB.LCS.PrepSucc counter is incremented by 1
each time the eNodeB successfully sends an INITIAL CONTEXT SETUP RESPONSE message
to the MME and the corresponding INITIAL CONTEXT SETUP REQUEST message is
determined that the CSFB procedure is for LCS.
Figure 2-140
Figure 2-141
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of CCO executions from E-UTRAN to GERAN in a cell.
Measurement Points
As shown at point B in Figure 2-142, during a CCO procedure from E-UTRAN to GERAN the
L.CCO.E2G.ExecAttOut counter is incremented by 1 each time the eNodeB sends a Mobility
From EUTRA Command message to the UE.
Figure 2-142
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful CCOs from E-UTRAN to GERAN in a cell.
Measurement Points
As shown at point C in Figure 2-143, during a CCO procedure from E-UTRAN to GERAN the
L.CCO.E2G.ExecSuccOut counter is incremented by 1 each time the eNodeB receives a UE
CONTEXT RELEASE COMMAND message from the MME after the UE is handed over from
E-UTRAN to GERAN.
Figure 2-143
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of inter-RAT handover initiation failures in a cell because the
adjacent cell is not the NRT of the source cell. The RAT of the target cell can be WCDMA
network, TD-SCDMA network , GERAN, CDMA2000 1xRTT network, or CDMA2000 HPRD
network.
Measurement Points
As shown at point A in Figure 2-144 or Figure 2-145, the corresponding counter is incremented
by 1 each time the source cell receives the first measurement report from the UE and determines
to initiate a handover, but the handover initiation fails because the adjacent cell that has the best
signal quality in the first measurement report is not on the NRT of the source cell. On GERANs,
measurement is reported based on the measurement mechanism configured by the corresponding
handover module. On UTRANs and CDMA2000 network, measurement is reported based on
the measurement mechanism configured by the SON module. Figure 2-144 shows the
measurement procedure on a GERAN. Figure 2-145 shows the measurement procedure on a
UTRAN or a CDMA2000 network. The counters are measured as follows:
Figure 2-144
Figure 2-145
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of CSFB preparation failures because of process conflict.
Measurement Points
As shown at point C in Figure 2-146, the L.CSFB.PrepFail.Conflict counter is incremented by
1 each time the eNodeB sends a UE CONTEXT MODIFICATION FAILURE message to the
MME containing the cause value "X2 Handover triggered", "S1 intra system Handover
triggered", or "S1 inter system Handover triggered" and the eNodeB determines that the CSFB
procedure is for voice services.
Figure 2-146
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover preparation attempts triggered because
of high load in a cell.
Measurement Points
As shown at point A in Figure 2-147, the L.IRATHO.E2W.Load.PrepAttOut counter is
incremented by 1 each time the eNodeB decides to perform a blind handover from E-UTRAN
to WCDMA network triggered because of high load or the eNodeB decides to perform a
handover from E-UTRAN to WCDMA network after the eNodeB receives a measurement report
from the UE triggered because of high load.
Figure 2-147
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover execution attempts triggered because
of high load in a cell.
Measurement Points
As shown at point B in Figure 2-148, the L.IRATHO.E2W.Load.ExecAttOut counter is
incremented by 1 each time the eNodeB performs an inter-RAT handover from E-UTRAN to
WCDMA network triggered because of high load and sends a Mobility From EUTRA Command
message to the UE.
As shown at point B in Figure 2-148, the L.IRATHO.E2G.Load.ExecAttOut counter is
incremented by 1 each time the eNodeB performs an inter-RAT handover from E-UTRAN to
GERAN triggered because of high load and sends a Mobility From EUTRA Command message
to the UE.
Figure 2-148
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-RAT handover executions triggered
because of high load in a cell.
Measurement Points
As shown at point C in Figure 2-149, the L.IRATHO.E2W.Load.ExecSuccOut counter is
incremented by 1 each time the eNodeB performs an inter-RAT handover from E-UTRAN to
WCDMA network triggered because of high load and the eNodeB receives a UE CONTEXT
RELEASE COMMAND message from the MME after the UE is handed over to a WCDMA
network.
Figure 2-149
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of redirections from E-UTRAN to another system triggered
because of high load in a cell.
Measurement Points
As shown at point A in Figure 2-150, the corresponding counter is incremented by 1 based on
the target system each time the eNodeB sends an RRC Connection Release message to the UE
during an RRC redirection to another system triggered because of high load. If the target system
is WCDMA network, the L.RRCRedirection.E2W.Load counter is incremented by 1. If the
target system is GERAN, the L.RRCRedirection.E2G.Load counter is incremented by 1.
Figure 2-150
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to WCDMA
network triggered for UEs to go back to the HPLMN in a cell. In national roaming scenarios, if
the handovers back to the HPLMN for UEs are enabled, a roaming UE can be handed over to
the HPLMN when this UE moves back to the HPLMN.
Measurement Points
As shown at point A in Figure 2-151, the L.IRATHO.E2W.RegainHPLMN.PrepAttOut counter
is incremented by 1 each time the eNodeB decides to perform an inter-RAT handover to
WCDMA network after the eNodeB receives a measurement report from the UE. The
corresponding Measurement Control message is triggered for the UE to go back to the HPLMN.
Figure 2-151
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover executions from E-UTRAN to
WCDMA network triggered for UEs to go back to the HPLMN in a cell. In national roaming
scenarios, if the handovers back to the HPLMN for UEs are enabled, a roaming UE can be handed
over to the HPLMN when this UE moves back to the HPLMN.
Measurement Points
As shown at point B in Figure 2-152, the L.IRATHO.E2W.RegainHPLMN.ExecAttOut counter
is incremented by 1 each time the eNodeB performs an inter-RAT handover from E-UTRAN to
WCDMA network after the eNodeB receive a HANDOVER COMMAND from the MME and
sends a Mobility From EUTRA Command message to the UE. The handover is triggered for the
UE to go back to the HPLMN.
Figure 2-152
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-RAT handovers from E-UTRAN to
WCDMA network triggered for UEs to go back to the HPLMN in a cell. In national roaming
scenarios, if the handovers back to the HPLMN for UEs are enabled, a roaming UE can be handed
over to the HPLMN when this UE moves back to the HPLMN.
Measurement Points
As shown at point C in Figure 2-153, the L.IRATHO.E2W.RegainHPLMN.ExecSuccOut
counter is incremented by 1 each time the eNodeB receives a UE CONTEXT RELEASE
COMMAND message from the MME after the UE is handed over to WCDMA network. The
corresponding handover is triggered for the UE to go back to the HPLMN.
Figure 2-153
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover executions from E-UTRAN to
WCDMA network triggered for a UE that has no data transmission.
Measurement Points
As shown at point B in Figure 2-154, during an inter-RAT handover that the UE does not transmit
or receive data, from an E-UTRAN to a WCDMA network the
L.IRATHO.E2W.NoData.ExecAttOut counter is incremented by 1 each time the eNodeB sends
a Mobility From EUTRA Command message to the UE.
Figure 2-154
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-RAT handovers from E-UTRAN to
WCDMA network triggered for UEs that do not transmit or receive data.
Measurement Points
As shown at point C in Figure 2-155, during an inter-RAT handover that the UE does not transmit
or receive data, from an E-UTRAN to a WCDMA network the
Figure 2-155
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of CSFB-based inter-RAT handover attempts from E-UTRAN
to WCDMA network. If the UE is performing services with the QCI of 1, the SRVCC procedure
is triggered to retain the services with the QCI of 1 after the eNodeB receives a CS fallback
indicator.
Measurement Points
As shown at point A in Figure 2-156, the L.IRATHO.SRVCC.LCS.E2W.PrepAttOut counter
is incremented by 1 each time the eNodeB receives a measurement report from the UE triggered
by CSFB and the eNodeB decides to perform an SRVCC procedure from E-UTRAN to WCDMA
network.
Figure 2-156
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.23.47 Number of Responses for Abnormal Causes Received by the eNodeB from
the MME During Inter-RAT Handover Executions from E-UTRAN to Another
System
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of responses for abnormal causes received by the eNodeB
from the MME during inter-RAT handover executions from E-UTRAN to another system.
Measurement Points
As shown at point C in Figure 2-157, during an inter-RAT handover from E-UTRAN to another
system the corresponding counter is incremented by 1 based on the handover target system each
time the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME
and the release cause is not "Successful Handover" or "Normal Release". If the target system is
CDMA2000 1xRTT network, the L.IRATHO.E21xRTT.MMEAbnormRsp counter is
incremented by 1. If the target system is CDMA2000 HRPD network, the
L.IRATHO.E21HRPD.MMEAbnormRsp counter is incremented by 1.
As shown at point C in Figure 2-158, during an inter-RAT handover from E-UTRAN to another
system the corresponding counter is incremented by 1 based on the handover target system each
time the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME
and the release cause is not "Successful Handover" or "Normal Release". If the target system is
WCDMA network, the L.IRATHO.E2W.MMEAbnormRsp counter is incremented by 1. If the
target system is TD-SCDMA network, the L.IRATHO.E2T.MMEAbnormRsp counter is
incremented by 1. If the target system is GERAN, the L.IRATHO.E2G.MMEAbnormRsp
counter is incremented by 1.
Figure 2-157
Figure 2-158
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.23.48 Number of Responses for Abnormal Causes Received by the eNodeB from
the MME During Inter-RAT Handover Executions from E-UTRAN to Another
System for SRVCC
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of responses for abnormal causes received by the eNodeB
from the MME during inter-RAT handover executions from E-UTRAN to another system for
SRVCC.
Measurement Points
As shown at point C in Figure 2-159, during an inter-RAT handover from E-UTRAN to another
system for SRVCC, the corresponding counter is incremented by 1 based on the handover target
system each time the eNodeB receives a UE CONTEXT RELEASE COMMAND message from
the MME and the release cause is not "Successful Handover" or "Normal Release". If the target
system is WCDMA network, the L.IRATHO.SRVCC.E2W.MMEAbnormRsp counter is
incremented by 1. If the target system is TD-SCDMA network, the
L.IRATHO.SRVCC.E2T.MMEAbnormRsp counter is incremented by 1. If the target system is
GERAN, the L.IRATHO.SRVCC.E2G.MMEAbnormRsp counter is incremented by 1.
Figure 2-159
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.23.49 Number of Responses for Abnormal Causes Received by the eNodeB from
the MME During CCO Executions from E-UTRAN to GERAN
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of responses for abnormal causes received by the eNodeB
from the MME during CCO executions from E-UTRAN to GERAN.
Measurement Points
As shown at point C in Figure 2-160, during a CCO execution from E-UTRAN to GERAN the
L.CCO.E2G.MMEAbnormRsp counter is incremented by 1 each time the eNodeB receives a
UE CONTEXT RELEASE COMMAND message from the MME and the release cause is not
"Successful Handover" or "Normal Release".
Figure 2-160
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.23.50 Number of Responses for Abnormal Causes Received by the eNodeB from
the MME During CSFB-based Inter-RAT Handover Executions from E-UTRAN to
Another System
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of responses for abnormal causes received by the eNodeB
from the MME during CSFB-based inter-RAT handover executions from E-UTRAN to another
system.
Measurement Points
As shown at point C in Figure 2-161, during an CSFB-based inter-RAT handover from E-
UTRAN to CDMA2000 network, the L.IRATHO.E2C.CSFB.MMEAbnormRsp counter is
incremented by 1 each time the eNodeB receives a UE CONTEXT RELEASE COMMAND
message from the MME and the release cause is not "Successful Handover" or "Normal Release".
Figure 2-161
Figure 2-162
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The HO.IRAT.In.Cell function subset measures the performance of inter-RAT handovers from
WCDMA network, GERAN, or TD-SCDMA network to E-UTRAN, as shown in Figure
2-163.
Figure 2-163
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the success rate of inter-RAT handovers from E-UTRAN to CDMA2000
network in a cell.
The counter will be deleted in later versions. It is reported normally in the current version but
the measurement value is invalid. You are advised not to use this counter.
Measurement Points
The success rate of inter-RAT handovers from E-UTRAN to CDMA2000 network in a cell is
calculated by using the corresponding KPI calculation formula based on the values of the
counters L.IRATHO.E2C.ExecSuccOut and L.IRATHO.E2C.ExecAttOut.
Formula
{100}*[L.IRATHO.E2C.ExecSuccOut]/ [L.IRATHO.E2C.ExecAttOut]
Unit
%
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the success rate of inter-RAT handovers from E-UTRAN to WCDMA
network in a cell.
The counter will be deleted in later versions. It is reported normally in the current version but
the measurement value is invalid. You are advised not to use this counter.
Measurement Points
The success rate of inter-RAT handovers from E-UTRAN to WCDMA network in a cell is
calculated by using the corresponding KPI calculation formula based on the values of the
counters L.IRATHO.E2W.ExecSuccOut and L.IRATHO.E2W.ExecAttOut.
Formula
{100}*[L.IRATHO.E2W.ExecSuccOut]/ [L.IRATHO.E2W.ExecAttOut]
Unit
%
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the success rate of inter-RAT handovers from E-UTRAN to GERAN in
a cell.
The counter will be deleted in later versions. It is reported normally in the current version but
the measurement value is invalid. You are advised not to use this counter.
Measurement Points
The success rate of inter-RAT handovers from E-UTRAN to GERAN in a cell is calculated by
using the corresponding KPI calculation formula based on the values of the counters
L.IRATHO.E2G.ExecSuccOut and L.IRATHO.E2G.ExecAttOut.
Formula
{100}*[L.IRATHO.E2G.ExecSuccOut]/ [L.IRATHO.E2G.ExecAttOut]
Unit
%
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover attempts from GERAN to E-UTRAN
in a cell.
Measurement Points
As shown at point A in Figure 2-164, the L.IRATHO.G2E.PrepAttIn counter is incremented by
1 each time the eNodeB receives a HANDOVER REQUEST message from the MME and this
message indicates an inter-RAT handover preparation from GERAN to E-UTRAN.
Figure 2-164
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-RAT handover preparations from GERAN
to E-UTRAN in a cell.
Measurement Points
As shown at point B in Figure 2-165, the L.IRATHO.G2E.PrepInSucc counter is incremented
by 1 each time the eNodeB sends a HANDOVER REQUEST ACKNOWLEDGE message to
the MME and this message indicates a successful inter-RAT handover preparation from GERAN
to E-UTRAN.
Figure 2-165
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-RAT handovers from GERAN to E-
UTRAN in a cell.
Measurement Points
As shown at point C in Figure 2-166, the L.IRATHO.G2E.ExecSuccIn counter is incremented
by 1 each time the eNodeB sends a HANDOVER NOTIFY message to the MME and this
message indicates a successful inter-RAT handover from GERAN to E-UTRAN.
Figure 2-166
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of inter-RAT handover preparation failures with the cause of
"Handover Target not allowed."
Measurement Points
As shown at point A in Figure 2-167, the corresponding counter is incremented by 1 each time
the eNodeB sends a HANDOVER FAILURE message to the MME and this message indicates
an inter-RAT incoming handover preparation failure with the cause of " Handover Target Not
Allowed." The counters are measured as follows:
Figure 2-167
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover attempts from TD-SCDMA network
to E-UTRAN in a cell.
Measurement Points
As shown at point A in Figure 2-168, the L.IRATHO.T2E.PrepAttIn counter is incremented by
1 each time the eNodeB receives a HANDOVER REQUEST message from the MME and this
message indicates an inter-RAT handover preparation from TD-SCDMA network to E-UTRAN.
Figure 2-168
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-RAT handover preparations from TD-
SCDMA network to E-UTRAN in a cell.
Measurement Points
As shown at point B in Figure 2-169, the L.IRATHO.T2E.PrepInSucc counter is incremented
by 1 each time the eNodeB sends a HANDOVER REQUEST ACKNOWLEDGE message to
the MME and this message indicates a successful inter-RAT handover preparation from TD-
SCDMA network to E-UTRAN.
Figure 2-169
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-RAT handovers from TD-SCDMA
network to E-UTRAN in a cell.
Measurement Points
As shown at point C in Figure 2-170, the L.IRATHO.T2E.ExecSuccIn counter is incremented
by 1 each time the eNodeB sends a HANDOVER NOTIFY message from the MME and this
maessage indicates a successful inter-RAT handover from TD-SCDMA network to E-UTRAN.
Figure 2-170
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-RAT handover attempts from WCDMA network to
E-UTRAN in a cell.
Measurement Points
As shown at point A in Figure 2-171, the L.IRATHO.W2E.PrepAttIn counter is incremented
by 1 each time the eNodeB receives a HANDOVER REQUEST message from the MME and
this message indicates an inter-RAT handover preparation from WCDMA network to E-
UTRAN.
Figure 2-171
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-RAT handover preparations from
WCDMA network to E-UTRAN in a cell.
Measurement Points
As shown at point B in Figure 2-172, the L.IRATHO.W2E.PrepInSucc counter is incremented
by 1 each time the eNodeB sends a HANDOVER REQUEST ACKNOWLEDGE message to
the MME and this message indicates a successful inter-RAT handover preparation from
WCDMA network to E-UTRAN.
Figure 2-172
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-RAT handovers from WCDMA network
to E-UTRAN in a cell.
Measurement Points
As shown at point C in Figure 2-173, the L.IRATHO.W2E.ExecSuccIn counter is incremented
by 1 each time the eNodeB sends a HANDOVER NOTIFY message from the MME and this
message indicates a successful inter-RAT handover from WCDMA network to E-UTRAN.
Figure 2-173
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The HO.eRAN.Out.Cell function subset measures the performance of intra-frequency and inter-
frequency of intra E-UTRAN outgoing handovers in a cell, as shown in Figure 2-174, Figure
2-175, Figure 2-176, and Figure 2-177.
Figure 2-174
Figure 2-175
Figure 2-176
Figure 2-177
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.HHO.IntraeNB.IntraFreq.ExecSuccOut L.HHO.IntraeNB.IntraFreq.Succ.ReEst2Src
L.HHO.IntraeNB.InterFreq.ExecSuccOut L.HHO.IntraeNB.InterFreq.Succ.ReEst2Src
L.HHO.IntereNB.IntraFreq.ExecSuccOut L.HHO.IntereNB.IntraFreq.Succ.ReEst2Src
L.HHO.IntereNB.IntraFreq.ExecSuccOut L.HHO.S1.IntraFreq.MMEAbnormRsp
L.HHO.IntereNB.InterFreq.ExecSuccOut L.HHO.IntereNB.InterFreq.Succ.ReEst2Src
L.HHO.IntereNB.InterFreq.ExecSuccOut L.HHO.S1.InterFreq.MMEAbnormRsp
L.HHO.BlindHO.ExecSuccOut L.HHO.BlindHO.Succ.ReEst2Src
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of intra-eNodeB intra-frequency outgoing handover attempts
and the number of intra-eNodeB inter-frequency outgoing handover attempts in a cell. In an
intra-eNodeB handover, the source cell and target cell are controlled by the same eNodeB. If
the source cell and target cell work on the same frequency, the handover is an intra-frequency
handover. If the source cell and target cell work on different frequencies, the handover is an
inter-frequency handover.
Measurement Points
As shown at point A in Figure 2-178, during an intra-eNodeB handover the corresponding
counter is incremented by 1 each time the eNodeB decides to perform an intra-eNodeB blind
handover or decides to perform an intra-eNodeB handover after the cell receives a measurement
report from the UE.
If the source cell and target cell work on the same frequency, the
L.HHO.IntraeNB.IntraFreq.PrepAttOut counter is incremented by 1.
If the source cell and target cell work on different frequencies, the
L.HHO.IntraeNB.InterFreq.PrepAttOut counter is incremented by 1.
Figure 2-178
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of intra-eNodeB intra-frequency outgoing handover
executions and the number of intra-eNodeB inter-frequency outgoing handover executions in a
cell. In an intra-eNodeB handover, the source cell and target cell are controlled by the same
eNodeB. If the source cell and target cell work on the same frequency, the handover is an intra-
frequency handover. If the source cell and target cell work on different frequencies, the handover
is an inter-frequency handover.
Measurement Points
As shown at point B in Figure 2-179, during an intra-eNodeB handover the corresponding
counter is incremented by 1 each time the source cell sends an RRC Connection Reconfiguration
message to the UE.
If the source cell and target cell work on the same frequency, the
L.HHO.IntraeNB.IntraFreq.ExecAttOut counter is incremented by 1.
If the source cell and target cell work on different frequencies, the
L.HHO.IntraeNB.InterFreq.ExecAttOut counter is incremented by 1.
Figure 2-179
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of successful intra-eNodeB intra-frequency outgoing
handovers and the number of successful intra-eNodeB inter-frequency outgoing handovers in a
cell. In an intra-eNodeB handover, the source cell and target cell are controlled by the same
eNodeB. If the source cell and target cell work on the same frequency, the handover is an intra-
frequency handover. If the source cell and target cell work on different frequencies, the handover
is an inter-frequency handover.
Measurement Points
As shown at point C in Figure 2-180, during an intra-eNodeB handover the corresponding
counter is incremented by 1 each time data in the buffer is forwarded during the handover after
the target cell receives an RRC Connection Reconfiguration Complete message from the UE.
If the source cell and the target cell work on the same frequency, the
L.HHO.IntraeNB.IntraFreq.ExecSuccOut counter is incremented by 1.
If the source cell and the target cell work on different frequencies, the
L.HHO.IntraeNB.InterFreq.ExecSuccOut counter is incremented by 1.
Figure 2-180
Figure 2-181
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of inter-eNodeB intra-frequency outgoing handover attempts
and the number of inter-eNodeB inter-frequency outgoing handover attempts in a cell. In an
inter-eNodeB handover, the source cell and target cell are controlled by different eNodeBs. Such
a handover is performed between different eNodeBs over the S1 or X2 interface. If the source
cell and target cell work on the same frequency, the handover is an intra-frequency handover.
If the source cell and target cell work on different frequencies, the handover is an inter-frequency
handover.
Measurement Points
As shown at point A in Figure 2-182, during an X2-based handover the corresponding counter
is incremented by 1 each time the source eNodeB decides to perform an X2-based blind handover
or the source eNodeB decides to perform an X2-based handover after the source cell receives a
measurement report from the UE.
As shown at point A in Figure 2-183, during an S1-based handover the corresponding counter
is incremented by 1 each time the source eNodeB decides to perform an S1-based blind handover
or the source eNodeB decides to perform an S1-based handover after the source cell receives a
measurement report from the UE.
If the source cell and target cell work on the same frequency, the
L.HHO.IntereNB.IntraFreq.PrepAttOut counter is incremented by 1.
If the source cell and target cell work on different frequencies, the
L.HHO.IntereNB.InterFreq.PrepAttOut counter is incremented by 1.
Figure 2-182
Figure 2-183
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of inter-eNodeB intra-frequency outgoing handover
executions and the number of inter-eNodeB inter-frequency outgoing handover executions in a
cell. In an inter-eNodeB handover, the source cell and target cell are controlled by different
eNodeBs. Such a handover is performed between different eNodeBs over the S1 or X2 interface.
If the source cell and target cell work on the same frequency, the handover is an intra-frequency
handover. If the source cell and target cell work on different frequencies, the handover is an
inter-frequency handover.
Measurement Points
As shown at point B in Figure 2-184, during an X2-based handover the corresponding counter
is incremented by 1 each time the source eNodeB sends an RRC Connection Reconfiguration
message to the UE after receiving a HANDOVER REQUEST ACKNOWLEDGE message from
the target eNodeB.
As shown at point B in Figure 2-185, during an S1-based handover the corresponding counter
is incremented by 1 each time the source eNodeB sends an RRC Connection Reconfiguration
message to the UE after receiving a HANDOVER COMMAND message from the MME.
If the source cell and target cell work on the same frequency, the
L.HHO.IntereNB.IntraFreq.ExecAttOut counter is incremented by 1.
If the source cell and target cell work on different frequencies, the
L.HHO.IntereNB.InterFreq.ExecAttOut counter is incremented by 1.
Figure 2-184
Figure 2-185
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of successful inter-eNodeB intra-frequency outgoing
handovers and the number of successful inter-eNodeB inter-frequency outgoing handovers in a
cell. In an inter-eNodeB handover, the source cell and target cell are controlled by different
eNodeBs. Such a handover is performed between different eNodeBs over the S1 or X2 interface.
If the source cell and target cell work on the same frequency, the handover is an intra-frequency
handover. If the source cell and target cell work on different frequencies, the handover is an
inter-frequency handover.
Measurement Points
As shown at point C in Figure 2-186, during an X2-based handover the corresponding counter
is incremented by 1 each time data in the buffer is forwarded during the handover after the source
eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB.
As shown at point C in Figure 2-187, during an X2-based handover after an RRC connection
is successfully reestablished to the target eNodeB for the UE, the corresponding counter is
incremented by 1 each time data in the buffer is forwarded during the handover after the source
eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB.
As shown at point C in Figure 2-190, during an X2-based handover after an RRC connection
is successfully reestablished to the source eNodeB for the UE, the corresponding counter is
incremented by 1 each time.
As shown at point C in Figure 2-188, during an S1-based handover the corresponding counter
is incremented by 1 each time data in the buffer is forwarded during the handover after the source
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME.
As shown at point C in Figure 2-189, during an S1-based handover after an RRC connection is
successfully reestablished to the target eNodeB for the UE, the corresponding counter is
incremented by 1 each time data in the buffer is forwarded during the handover after the source
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME.
As shown at point C in Figure 2-191, during an S1-based handover after an RRC connection is
successfully reestablished to the source eNodeB for the UE, the corresponding counter is
incremented by 1 each time.
If the source cell and target cell work on the same frequency, the
L.HHO.IntereNB.IntraFreq.ExecSuccOut counter is incremented by 1.
If the source cell and target cell work on different frequencies, the
L.HHO.IntereNB.InterFreq.ExecSuccOut counter is incremented by 1.
Figure 2-186
Figure 2-187
Figure 2-188
Figure 2-189
Figure 2-190
Figure 2-191
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the intra-frequency handover success rate in a cell.
This counter will be deleted in later versions. It is reported normally in the current version but
the measurement value is invalid. You are advised not to use this counter.
Measurement Points
The intra-frequency handover success rate in a cell is calculated by using the corresponding KPI
calculation formula based on the values of the counters
L.HHO.IntereNB.IntraFreq.ExecSuccOut, L.HHO.IntraeNB.IntraFreq.ExecSuccOut,
L.HHO.IntereNB.IntraFreq.ExecAttOut, and L.HHO.IntraeNB.IntraFreq.ExecAttOut.
Formula
{100}*([L.HHO.IntereNB.IntraFreq.ExecSuccOut]+
[L.HHO.IntraeNB.IntraFreq.ExecSuccOut])/([L.HHO.IntereNB.IntraFreq.ExecAttOut]+
[L.HHO.IntraeNB.IntraFreq.ExecAttOut])
Unit
%
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the inter-frequency handover success rate in a cell.
This counter will be deleted in later versions. It is reported normally in the current version but
the measurement value is invalid. You are advised not to use this counter.
Measurement Points
The inter-frequency handover success rate in a cell is calculated by using the corresponding KPI
calculation formula based on the values of the counters
L.HHO.IntereNB.InterFreq.ExecSuccOut, L.HHO.IntraeNB.InterFreq.ExecSuccOut,
L.HHO.IntereNB.InterFreq.ExecAttOut, and L.HHO.IntraeNB.InterFreq.ExecAttOut.
Formula
{100}*([L.HHO.IntereNB.InterFreq.ExecSuccOut]+
[L.HHO.IntraeNB.InterFreq.ExecSuccOut])/([L.HHO.IntereNB.InterFreq.ExecAttOut]+
[L.HHO.IntraeNB.InterFreq.ExecAttOut])
Unit
%
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of intra-RAT outgoing blind handover attempts in a cell. Not
triggered on the basis of UE measurement reports, the blind handover is a handover in which
the eNodeB specifies the target cell for the UE. In specific networking scenarios, the eNodeB
performs a blind handover to actively hand over the UE from the target cell.
Measurement Points
As shown at point A in Figure 2-192, Figure 2-193, or Figure 2-194, the
L.HHO.BlindHO.PrepAttOut counter is incremented by 1 each time the eNodeB decides to
perform a blind handover. Figure 2-192 shows an intra-eNodeB blind handover, Figure
2-193 shows an X2-based blind handover, and Figure 2-194 shows an S1-based blind handover.
Figure 2-192
Figure 2-193
Figure 2-194
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of intra-RAT outgoing blind handover executions in a cell.
Not triggered on the basis of UE measurement reports, the blind handover is a handover in which
the eNodeB specifies the target cell for the UE. In specific networking scenarios, the eNodeB
performs a blind handover to actively hand over the UE from the target cell.
Measurement Points
As shown at point B in Figure 2-195, Figure 2-196, or Figure 2-197, the
L.HHO.BlindHO.ExecAttOut counter is incremented by 1 each time the eNodeB decides to
perform a blind handover and sends an RRC Connection Reconfiguration message to the UE.
Figure 2-195 shows an intra-eNodeB blind handover, Figure 2-196 shows an X2-based blind
handover, and Figure 2-197 shows an S1-based blind handover.
Figure 2-195
Figure 2-196
Figure 2-197
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful intra-RAT outgoing blind handovers in a cell.
Not triggered on the basis of UE measurement reports, the blind handover is a handover in which
the eNodeB specifies the target cell for the UE. In specific networking scenarios, the eNodeB
performs a blind handover to actively hand over the UE from the target cell.
Measurement Points
As shown at point C in Figure 2-198, the L.HHO.BlindHO.ExecSuccOut counter is incremented
by 1 each time the eNodeB decides to perform an intra-eNodeB blind handover and target cell
receives an RRC Connection Reconfiguration Complete message from the UE.
Figure 2-198
Figure 2-199
Figure 2-200
Figure 2-201
Figure 2-202
Figure 2-203
Figure 2-204
Figure 2-205
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of outgoing handover failures based on the failure cause in a
cell. Outgoing handover failures usually occur during handover preparation and are caused by
faults on the MME side, no responses from the target cell, the target cell sending handover
preparation failure messages, or the source cell sending handover cancellation messages. During
the handover preparation phase, between the handover decision phase and the handover
execution phase, the handover resources are prepared.
Measurement Points
As shown at point B in Figure 2-206 during an S1-based handover preparation phase or as shown
at point B in Figure 2-207 during an X2-based handover preparation phase, the
L.HHO.Prep.FailOut.MME counter is incremented by 1 each time the source cell receives a UE
CONTEXT RELEASE COMMAND message from the MME.
As shown at point B in Figure 2-208 at the end of an S1-based handover preparation phase or
as shown at point B in Figure 2-209 at the end of an X2-based handover preparation phase, the
L.HHO.Prep.FailOut.NoReply counter is incremented by 1 each time the source cell does not
receive any message from the target eNodeB, such as the HANDOVER REQUEST
ACKNOWLEDEG and HANDOVER PREPARATION FAILURE messages sent from the
target eNodeB during the X2-based handover and the HANDOVER COMMAND and
HANDOVER PREPARATION FAILURE messages sent from the MME during the S1-based
handover.
As shown at point B in Figure 2-211, during an X2-based handover preparation phase the
L.HHO.Prep.FailOut.PrepFailure counter is incremented by 1 each time the source cell receives
a HANDOVER PREPARATION FAILURE message from the target cell. As shown at point B
in Figure 2-210, during an S1-based handover preparation phase the
L.HHO.Prep.FailOut.PrepFailure counter is incremented by 1 each time the source cell receives
a HANDOVER PREPARATION FAILURE message from the MME.
Figure 2-206
Figure 2-207
Figure 2-208
Figure 2-209
Figure 2-210
Figure 2-211
Figure 2-212
Figure 2-213
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of intra-RAT redirections initiated by the eNodeB. In an
redirection, the eNodeB sends an RRC Connection Release message containing the target
frequency and other information to a UE, releases the RRC connection to the source cell for the
UE, and then directs the UE to access the target cell to continue its services.
Measurement Points
As shown at point A in Figure 2-214, the L.RRCRedirection.IntraLTE counter is incremented
by 1 each time the eNodeB sends an RRC Connection Release message to the UE and the
handover target cell is an intra-RAT inter-frequency cell of the source cell.
Figure 2-214
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of intra-RAT handover initiation failures in a cell because the
adjacent cell is not on the neighboring relation table (NRT) of the source cell. If the source cell
and target cell work on the same frequency, the handover is an intra-frequency handover. If the
source cell and target cell work on different frequencies, the handover is an inter-frequency
handover.
Measurement Points
As shown at point A in Figure 2-215, Figure 2-216, or Figure 2-217, the corresponding counter
is incremented by 1 each time the eNodeB receives the first measurement report from a UE in
the source cell and decides to perform a handover, but the handover initiation fails because that
the adjacent cell has the best signal quality in the first measurement report is not on the NRT of
the source cell.
Figure 2-215 shows an intra-eNodeB handover, Figure 2-216 shows an X2-based handover,
and Figure 2-217 shows an S1-based handover. The counters are measured as follows:
Figure 2-215
Figure 2-216
Figure 2-217
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-frequency handover preparation attempts triggered
because of high load in a cell.
Measurement Points
As shown at point A in Figure 2-218, Figure 2-219 or Figure 2-220, the
L.HHO.InterFreq.Load.PrepAttOut counter is incremented by 1 each time the eNodeB decides
to perform an inter-frequency blind handover because of high load or the eNodeB receives a
measurement report from the UE because of high load and decides to perform an inter-frequency
handover. Figure 2-218 shows an intra-eNodeB inter-frequency handover, Figure 2-219 shows
an X2-based inter-frequency handover and Figure 2-220 shows an S1-based inter-frequency
handover.
Figure 2-218
Figure 2-219
Figure 2-220
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-frequency handover execution attempts triggered
because of high load in a cell.
Measurement Points
As shown at point B in Figure 2-221, Figure 2-222 or Figure 2-223, the
L.HHO.InterFreq.Load.ExecAttOut counter is incremented by 1 each time the eNodeB decides
to perform an inter-frequency handover because of high load and sends an RRC Connection
Reconfiguration message to the UE. Figure 2-221 shows an intra-eNodeB inter-frequency
handover, Figure 2-222 shows an X2-based inter-frequency handover and Figure 2-223 shows
an S1-based inter-frequency handover.
Figure 2-221
Figure 2-222
Figure 2-223
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-frequency handover executions triggered
because of high load in a cell.
Measurement Points
As shown at point C in Figure 2-224, the L.HHO.InterFreq.Load.ExecSuccOut counter is
incremented by 1 each time the eNodeB decides to perform an intra-eNodeB handover because
of high load and target cell receives an RRC Connection Reconfiguration Complete message
from the UE.
As shown at point C in Figure 2-225, the L.HHO.InterFreq.Load.ExecSuccOut counter is
incremented by 1 each time the eNodeB decides to perform an intra-eNodeB handover because
of high load and the target cell receives an RRC Connection Reestablishment Complete message
from the UE.
As shown at point C in Figure 2-225, the L.HHO.InterFreq.Load.ExecSuccOut counter is
incremented by 1 each time the eNodeB decides to perform an intra-eNodeB handover because
of high load and the source cell receives an RRC Connection Reestablishment Complete message
from the UE.
As shown at point C in Figure 2-226, the L.HHO.InterFreq.Load.ExecSuccOut counter is
incremented by 1 each time the eNodeB decides to perform an X2-based blind handover because
of high load and the source eNodeB receives a UE CONTEXT RELEASE message from the
target eNodeB.
As shown at point C in Figure 2-227, during an X2-based blind handover the
L.HHO.InterFreq.Load.ExecSuccOut counter is incremented by 1 each time the eNodeB decides
to perform an X2-based blind handover because of high load and the source eNodeB receives a
UE CONTEXT RELEASE message from the target eNodeB after an RRC connection is
successfully reestablished to the target eNodeB for the UE.
As shown at point C in Figure 2-228, during an X2-based blind handover the
L.HHO.InterFreq.Load.ExecSuccOut counter is incremented by 1 each time the eNodeB decides
to perform an X2-based blind handover because of high load and after an RRC connection is
successfully reestablished to the source eNodeB for the UE.
As shown at point C in Figure 2-229, the L.HHO.InterFreq.Load.ExecSuccOut counter is
incremented by 1 each time the eNodeB decides to perform an s1-based blind handover because
of high load and the source eNodeB receives a UE CONTEXT RELEASE message from MME.
Figure 2-224
Figure 2-225
Figure 2-226
Figure 2-227
Figure 2-228
Figure 2-229
Figure 2-230
Figure 2-231
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-frequency outgoing handover attempts triggered for
UEs to go back to the HPLMN in a cell. In national roaming scenarios, if the handovers back to
the HPLMN for UEs is enabled, a roaming UE can be handed over to the HPLMN when this
UE moves back to the HPLMN.
Measurement Points
As shown at point A in Figure 2-232, during an X2-based handover the
L.HHO.InterFreq.RegainHPLMN.PrepAttOut counter is incremented by 1 each time the source
eNodeB determines to perform an X2-based handover after the source eNodeB receives a
measurement report from the UE. The corresponding measurement control message is triggered
for the UE to go back to the HPLMN.
Figure 2-232
Figure 2-233
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-frequency outgoing handover executions triggered
for UEs to go back to the HPLMN in a cell. In national roaming scenarios, if the handovers back
to the HPLMN for UEs is enabled, a roaming UE can be handed over to the HPLMN when this
UE moves back to the HPLMN.
Measurement Points
As shown at point B in Figure 2-234, during an X2-based handover the
L.HHO.InterFreq.RegainHPLMN.ExecAttOut counter is incremented by 1 each time the source
eNodeB sends an RRC Connection Reconfiguration message to the UE after the source eNodeB
receives a HANDOVER REQUEST ACKNOWLEDGE message from the target eNodeB.
Figure 2-234
Figure 2-235
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-frequency outgoing handovers triggered
for UEs to go back to the HPLMN in a cell. In national roaming scenarios, if the handovers back
to the HPLMN for UEs is enabled, a roaming UE can be handed over to the HPLMN when this
UE moves back to the HPLMN.
Measurement Points
As shown at point C in Figure 2-236, during an X2-based handover the
L.HHO.InterFreq.RegainHPLMN.ExecSuccOut counter is incremented by 1 each time data in
the buffer is forwarded during the handover after the source eNodeB receives a UE CONTEXT
RELEASE message from the target eNodeB.
As shown at point C in Figure 2-237, during an X2-based handover after an RRC connection
is successfully reestablished to the target eNodeB for the UE, the
L.HHO.InterFreq.RegainHPLMN.ExecSuccOut counter is incremented by 1 each time data in
the buffer is forwarded during the handover after the source eNodeB receives a UE CONTEXT
RELEASE message from the target eNodeB.
As shown at point C in Figure 2-240, during an X2-based handover after an RRC connection
is successfully reestablished to the source eNodeB for the UE, the
L.HHO.InterFreq.RegainHPLMN.ExecSuccOut counter is incremented by 1 each time.
As shown at point C in Figure 2-239, during an S1-based handover after an RRC connection is
successfully reestablished to the target eNodeB for the UE, the
L.HHO.InterFreq.RegainHPLMN.ExecSuccOut counter is incremented by 1 each time data in
the buffer is forwarded during the handover after the source eNodeB receives a UE CONTEXT
RELEASE COMMAND message from the MME.
As shown at point C in Figure 2-241, during an S1-based handover after an RRC connection is
successfully reestablished to the source eNodeB for the UE, the
L.HHO.InterFreq.RegainHPLMN.ExecSuccOut counter is incremented by 1 each time.
Figure 2-236
Figure 2-237
Figure 2-238
Figure 2-239
Figure 2-240
Figure 2-241
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of intra-frequency handover execution attempts triggered for
UEs that do not transmit or receive data.
Measurement Points
This counter is measured in a handover where the source cell and the target cell work on the
same frequency.
As shown at point B in Figure 2-242, during an intra-eNodeB handover that the UE does not
transmit or receive data, the L.HHO.IntraFreq.NoData.ExecAttOut counter is incremented by 1
each time the source eNodeB sends an RRC Connection Reconfiguration message to the UE.
As shown at point B in Figure 2-243, during an X2-based handover that the UE does not transmit
or receive data, the L.HHO.IntraFreq.NoData.ExecAttOut counter is incremented by 1 each time
the source eNodeB sends an RRC Connection Reconfiguration message to the UE after the
source eNodeB receives a HANDOVER REQUEST ACKNOWLEDGE message from the
target eNodeB.
Figure 2-242
Figure 2-243
Figure 2-244
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful intra-frequency handover executions triggered
for UEs that do not transmit or receive data.
Measurement Points
This counter is measured in a handover where the source cell and the target cell work on the
same frequency.
As shown at point C in Figure 2-245, during an intra-eNodeB handover that the UE does not
transmit or receive data, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented by
1 each time the target cell receives an RRC Connection Reconfiguration Complete message from
the UE.
As shown at point C in Figure 2-246, during an intra-eNodeB handover that the UE does not
transmit or receive data, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented by
1 each time the target cell receives an RRC Connection Reestablishment Complete message
from the UE.
As shown at point C in Figure 2-246, during an intra-eNodeB handover that the UE does not
transmit or receive data, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented by
1 each time the source cell receives an RRC Connection Reestablishment Complete message
from the UE.
As shown at point C in Figure 2-247, during an X2-based handoverthat the UE does not transmit
or receive data, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented by 1 each
time the source eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB.
As shown at point C in Figure 2-248, during an X2-based inter-eNodeB handover that the UE
does not transmit or receive data, after an RRC connection is successfully reestablished to the
target eNodeB for the UE, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented
by 1 each time the source eNodeB receives a UE CONTEXT RELEASE message from the target
eNodeB.
As shown at point C in Figure 2-251, during an X2-based inter-eNodeB handover that the UE
does not transmit or receive data, after an RRC connection is successfully reestablished to the
source eNodeB for the UE, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented
by 1 each time.
As shown at point C in Figure 2-249, during an S1-based handover that the UE does not transmit
or receive data, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented by 1 each
time the source eNodeB receives a UE CONTEXT RELEASE COMMAND from the MME.
As shown at point C in Figure 2-250, during an S1-based handover that the UE does not transmit
or receive data, after an RRC connection is successfully reestablished to the target eNodeB for
the UE, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented by 1 each time the
source eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME.
As shown at point C in Figure 2-252, during an S1-based handover that the UE does not transmit
or receive data, after an RRC connection is successfully reestablished to the source eNodeB for
the UE, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented by 1 each time.
Figure 2-245
Figure 2-246
Figure 2-247
Figure 2-248
Figure 2-249
Figure 2-250
Figure 2-251
Figure 2-252
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-frequency handover execution attempts triggered for
UEs that do not transmit or receive data.
Measurement Points
This counter is measured in a handover where the source cell and the target cell work on the
different frequency.
As shown at point B in Figure 2-253, during an intra-eNodeB handover that the UE does not
transmit or receive data, the L.HHO.InterFreq.NoData.ExecAttOut counter is incremented by 1
each time the source eNodeB sends an RRC Connection Reconfiguration message to the UE.
As shown at point B in Figure 2-254, during an X2-based handover that the UE does not transmit
or receive data, the L.HHO.InterFreq.NoData.ExecAttOut counter is incremented by 1 each time
the source eNodeB sends an RRC Connection Reconfiguration message to the UE after the
Figure 2-253
Figure 2-254
Figure 2-255
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-frequency handover executions triggered
for UEs that do not transmit or receive data.
Measurement Points
This counter is measured in a handover where the source cell and the target cell work on different
frequencies.
As shown at point C in Figure 2-256, during an intra-eNodeB handover that the UE does not
transmit or receive data, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented by
1 each time the target cell receives an RRC Connection Reconfiguration Complete message from
the UE.
As shown at point C in Figure 2-257, during an intra-eNodeB handover that the UE does not
transmit or receive data, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented by
1 each time the target cell receives an RRC Connection Reestablishment Complete message
from the UE.
As shown at point C in Figure 2-257, during an intra-eNodeB handover that the UE does not
transmit or receive data, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented by
1 each time the source cell receives an RRC Connection Reestablishment Complete message
from the UE.
As shown at point C in Figure 2-258, during an X2-based handover that the UE does not transmit
or receive data, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented by 1 each
time the source eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB.
As shown at point C in Figure 2-259, during an X2-based handover that the UE does not transmit
or receive data, after an RRC connection is successfully reestablished to the target eNodeB for
the UE, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented by 1 each time the
source eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB.
As shown at point C in Figure 2-262, during an X2-based handover that the UE does not transmit
or receive data, after an RRC connection is successfully reestablished to the source eNodeB for
the UE, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented by 1 each time.
As shown at point C in Figure 2-260, during an S1-based handover that the UE does not transmit
or receive data, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented by 1 each
time the source eNodeB receives a UE CONTEXT RELEASE COMMAND from the MME.
As shown at point C in Figure 2-261, during an S1-based handover that the UE does not transmit
or receive data, after an RRC connection is successfully reestablished to target eNodeB for the
UE, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented by 1 each time the
source eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME.
As shown at point C in Figure 2-263, during an S1-based handover that the UE does not transmit
or receive data, after an RRC connection is successfully reestablished to source eNodeB for the
UE, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented by 1 each time.
Figure 2-256
Figure 2-257
Figure 2-258
Figure 2-259
Figure 2-260
Figure 2-261
Figure 2-262
Figure 2-263
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.25.25 Number of Responses for Abnormal Causes Received by the eNodeB from
the MME During S1-based Outgoing Handover Executions
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of responses for abnormal causes received by the eNodeB
from the MME during S1-based outgoing handover executions.
Measurement Points
As shown at point C in Figure 2-264, during an S1-based handover the corresponding counter
is incremented by 1 each time the source eNodeB receives a UE CONTEXT RELEASE
COMMAND message from the MME and the release cause is not "Successful Handover" or
"Normal Release". The counters are measured as follows:
If the source cell and the target cell work on the same frequency, the
L.HHO.S1.IntraFreq.MMEAbnormRsp counter is incremented by 1.
If the source cell and the target cell work on different frequencies, the
L.HHO.S1.InterFreq.MMEAbnormRsp counter is incremented by 1.
Figure 2-264
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of successful intra-eNodeB outgoing handovers where RRC
connections are reestablished to the source cell for UEs in a cell.
Measurement Points
As shown at point C in Figure 2-265, during an intra-eNodeB handover the corresponding
counter is incremented by 1 each time the source cell receives an RRC Connection
Reestablishment Complete message from the UE. The counters are measured as follows:
If the source cell and the target cell work on the same frequency, the
L.HHO.IntraeNB.IntraFreq.Succ.ReEst2Src counter is incremented by 1.
If the source cell and the target cell work on different frequencies, the
L.HHO.IntraeNB.InterFreq.Succ.ReEst2Src counter is incremented by 1.
Figure 2-265
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of successful inter-eNodeB outgoing handovers where RRC
connections are reestablished to the source cell for UEs in a cell.
Measurement Points
As shown at point C in Figure 2-266, during an X2-based handover the corresponding counter
is incremented by 1 each time the source cell receives an RRC Connection Reestablishment
Complete message from the UE. The counters are measured as follows:
If the source cell and the target cell work on the same frequency, the
L.HHO.IntereNB.IntraFreq.Succ.ReEst2Src counter is incremented by 1.
If the source cell and the target cell work on different frequencies, the
L.HHO.IntereNB.InterFreq.Succ.ReEst2Src counter is incremented by 1.
As shown at point C in Figure 2-267, during an S1-based handover the corresponding counter
is incremented by 1 each time the source cell receives an RRC Connection Reestablishment
Complete message from the UE. The counters are measured as follows:
If the source cell and the target cell work on the same frequency, the
L.HHO.IntereNB.IntraFreq.Succ.ReEst2Src counter is incremented by 1.
If the source cell and the target cell work on different frequencies, the
L.HHO.IntereNB.InterFreq.Succ.ReEst2Src counter is incremented by 1.
Figure 2-266
Figure 2-267
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful blind outgoing handovers where RRC
connections are reestablished to the source cell for UEs in a cell. Not triggered on the basis of
UE measurement reports, the blind handover is a handover in which the eNodeB specifies the
target cell for the UE. In specific networking scenarios, the eNodeB performs a blind handover
to actively hand over the UE from the target cell.
Measurement Points
As shown at point C in Figure 2-268, during an intra-eNodeB blind handover the
L.HHO.BlindHO.Succ.ReEst2Src counter is incremented by 1 each time the source cell receives
an RRC Connection Reestablishment Complete message from the UE.
Figure 2-268
Figure 2-269
Figure 2-270
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The HO.eRAN.In.Cell function subset measures the performance of intra-frequency and inter-
frequency of intra E-UTRAN incoming handovers in a cell, as shown in Figure 2-271, Figure
2-272, and Figure 2-273.
Figure 2-271
Figure 2-272
Figure 2-273
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.HHO.Prep.FailIn.AdmitFail L.HHO.Prep.FailIn.AdmitFail.Load
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of intra-eNodeB incoming handover attempts in a cell. In an
intra-eNodeB handover, the source cell and target cell are controlled by the same eNodeB.
Measurement Points
As shown at point A in Figure 2-274, the L.HHO.IntraeNB.PrepAttIn counter is incremented
by 1 in the target cell each time the eNodeB decides to perform an intra-eNodeB incoming
handover after receiving a measurement report from the UE.
Figure 2-274
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of intra-eNodeB incoming handover executions in a cell. In
an intra-eNodeB handover, the source cell and target cell are controlled by the same eNodeB.
Measurement Points
As shown at point B in Figure 2-275, the L.HHO.IntraeNB.ExecAttIn counter is incremented
by 1 in the target cell each time the eNodeB sends an RRC Connection Reconfiguration message
to the UE.
Figure 2-275
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful intra-eNodeB incoming handovers in a cell. In
an intra-eNodeB handover, the source cell and target cell are controlled by the same eNodeB.
Measurement Points
As shown at point C in Figure 2-276, the L.HHO.IntraeNB.ExecSuccIn counter is incremented
by 1 in the target cell each time the eNodeB receives an RRC Connection Reconfiguration
Complete message from the UE and the subsequent processing is successful.
Figure 2-276
Figure 2-277
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-eNodeB incoming handover attempts in a cell. In an
inter-eNodeB handover, the source cell and target cell are controlled by different eNodeBs. Such
a handover is performed between different eNodeBs over the S1 or X2 interface.
Measurement Points
Figure 2-278 shows an X2-based handover, and Figure 2-279 shows an S1-based handover. As
shown at point A in Figure 2-278, the L.HHO.IntereNB.PrepAttIn counter is incremented by 1
in the target cell each time the target eNodeB receives a HANDOVER REQUEST message from
the source eNodeB over the X2 interface.
Figure 2-278
Figure 2-279
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of inter-eNodeB incoming handover executions in a cell. In
an inter-eNodeB handover, the source cell and target cell are controlled by different eNodeBs.
Such a handover is performed between different eNodeBs over the S1 or X2 interface.
Measurement Points
Figure 2-280 shows an X2-based handover, and Figure 2-281 shows an S1-based handover. As
shown at point B in Figure 2-280 or Figure 2-281, the L.HHO.IntereNB.ExecAttIn counter is
incremented by 1 in the target cell each time the target eNodeB sends a HANDOVER REQUEST
ACKNOWLEDGE message to the source eNodeB over the X2 interface>
Figure 2-280
Figure 2-281
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful inter-eNodeB incoming handovers in a cell. In
an inter-eNodeB handover, the source cell and target cell are controlled by different eNodeBs.
Such a handover is performed between different eNodeBs over the S1 or X2 interface.
Measurement Points
As shown at point C in Figure 2-282, during an X2-based handover the
L.HHO.IntereNB.ExecSuccIn counter is incremented by 1 in the target cell each time the target
eNodeB sends a UE CONTEXT RELEASE message to the source eNodeB over the X2 interface
after the target eNodeB receives a PATH SWITCH REQUEST ACKNOWLEDGE message
from the MME.
As shown at point E in Figure 2-283, during an X2-based handover after an RRC connection is
successfully reestablished to the target eNodeB for the UE, the L.HHO.IntereNB.ExecSuccIn
counter is incremented by 1 in the target cell each time the target eNodeB receives a PATH
SWITCH REQUEST ACKNOWLEDGE message from the MME and sends a UE CONTEXT
RELEASE message to the source eNodeB over the X2 interface.
As shown at in point C in Figure 2-285, during an S1-based handover after an RRC connection
is successfully reestablished to the target eNodeB for the UE, the L.HHO.IntereNB.ExecSuccIn
counter is incremented by 1 in the target cell each time the target eNodeB sends a HANDOVER
NOTIFY message to the MME.
Figure 2-282
Figure 2-283
Figure 2-284
Figure 2-285
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of incoming handover failures for different causes in a cell.
Outgoing handover failures usually occur during handover preparation and are caused by faults
on the MME side, no responses from the target cell, handover preparation failures at the target
cell, or handover cancellation messages sent by the source cell. Handover preparation is the
procedure to prepare handover resources between the handover decision and the handover
execution.
Measurement Points
As shown at point B in Figure 2-286, during an S1-based handover preparation phase the
L.HHO.Prep.FailIn.AdmitFail counter is incremented by 1 in the target cell each time the target
eNodeB receives a HANDOVER REQUEST message over the S1 interface and sends a
HANDOVER FAILURE message to the MME over the S1 interface because of admission
rejection in the target cell.
As shown at point B in Figure 2-286, during an X2-based handover preparation phase the
L.HHO.Prep.FailIn.AdmitFail counter in incremented by 1 in the target cell each time the target
eNodeB receives a HANDOVER REQUEST message over the X2 interface and sends a
HANDOVER PREPARATION FAILURE message to the target eNodeB over the X2 interface
because of admission rejection in the target cell.
As shown at point B in Figure 2-286, during an S1-based handover preparation phase the
L.HHO.Prep.FailIn.FlowCtrl counter is incremented by 1 in the target cell each time the target
eNodeB receives a HANDOVER REQUEST message over the S1 interface and sends a
HANDOVER FAILURE message to the MME over the S1 interface if the incoming handover
fails because of flow control in the target cell.
As shown at point B in Figure 2-287, during an X2-based handover preparation phase the
L.HHO.Prep.FailIn.FlowCtrl counter in incremented by 1 in the target cell each time the target
eNodeB receives a HANDOVER REQUEST message over the X2 interface and sends a
HANDOVER PREPARATION FAILURE message to the target eNodeB over the X2 interface
if the incoming handover fails because of flow control in the target cell.
As shown at point B in Figure 2-286, during an S1-based handover preparation phase, the
L.HHO.Prep.FailIn counter is incremented by 1 in the target cell each time the target eNodeB
receives a HANDOVER REQUEST message over the S1 interface and the target cell sends a
HANDOVER PREPARATION FAILURE message to the source MME.
As shown at point in B in Figure 2-286, during an X2-based handover preparation phase, the
L.HHO.Prep.FailIn counter is incremented by 1 in the target cell each time the target eNodeB
receives a HANDOVER REQUEST message over the X2 interface and the target cell sends a
HANDOVER PREPARATION FAILURE message to the source eNodeB.
Figure 2-286
Figure 2-287
Figure 2-288
Figure 2-289
Figure 2-290
Figure 2-291
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of path switch requests for X2-based incoming handovers in
a cell. In an X2-based handover, the source and target cells are controlled by different eNodeBs.
Such a handover is performed between different eNodeBs over the X2 interface.
Measurement Points
As shown at point D in Figure 2-292, during an X2-based handover the
L.HHO.IntereNB.PathSwAtt counter is incremented by 1 in the target cell each time the target
eNodeB sends a PATH SWITCH REQUEST message to the MME over the S1 interface.
Figure 2-292
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful path switches for X2-based incoming handovers
in a cell. In an X2-based handover, the source and target cells are controlled by different
eNodeBs. Such a handover is performed between different eNodeBs over the X2 interface.
Measurement Points
As shown at point E in Figure 2-293, during an X2-based handover the
L.HHO.IntereNB.PathSwSucc counter is incremented by 1 in the target cell each time the target
eNodeB receives a PATH SWITCH REQUEST ACKNOWLEDGE message from the MME.
Figure 2-293
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of incoming handover failures because of high load in a cell.
Measurement Points
As shown at point B in Figure 2-294, during an S1-based handover preparation phase the
L.HHO.Prep.FailIn.AdmitFail.Load counter is incremented by 1 in the target cell each time the
target eNodeB receives a HANDOVER REQUEST message over the S1 interface and sends a
HANDOVER FAILURE message to the MME over the S1 interface if the access is rejected
because of high load in the target cell.
As shown at point B in Figure 2-295, during an X2-based handover preparation phase the
L.HHO.Prep.FailIn.AdmitFail.Load counter is incremented by 1 in the target cell each time the
target eNodeB receives a HANDOVER REQUEST message over the X2 interface and sends a
HANDOVER PREPARATION FAILURE message to the target eNodeB over the X2 interface
if the access is rejected because of high load in the target cell.
Figure 2-294
Figure 2-295
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of times that the target cell receives a HANDOVER CANCEL
message from the source cell during inter-eNodeB handover executions in a cell.
Measurement Points
As shown at point C in Figure 2-296, during an X2-based handover the
L.HHO.X2.Cancel.ExecIn counter is incremented by 1 each time the target cell sends a
HANDOVER REQUEST ACKNOWLEDGE message to the source cell and receives a
HANDOVER CANCEL message from the source cell.
Figure 2-296
Figure 2-297
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The HO.eRAN.X2Out.Cell function subset measures the performance of X2-based intra-
frequency and X2-based inter-frequency outgoing handovers over the X2 interface in a cell, as
shown in Figure 2-298.
Figure 2-298
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.HHO.X2.IntraFreq.ExecSuccOut L.HHO.X2.IntraFreq.Succ.ReEst2Src
L.HHO.X2.InterFreq.ExecSuccOut L.HHO.X2.InterFreq.Succ.ReEst2Src
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number ofX2-based intra-frequency outgoing handover attempts and
X2-basedinter-frequency outgoing handover attempts in a cell.
Measurement Points
As shown at point A in Figure 2-299, the corresponding counter is incremented by 1 in the
source cell each time the source eNodeB decides to perform an X2-based blind handover or the
source eNodeB decides to perform an X2-based handover after receiving a measurement report
from the UE. The counters are measured as follows: If the source cell and the target cell work
on the same frequency, the L.HHO.X2.IntraFreq.PrepAttOut counter is incremented by 1. If the
source cell and the target cell work on different frequencies, the
L.HHO.X2.InterFreq.PrepAttOut counter is incremented by 1.
Figure 2-299
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of X2-based intra-frequency outgoing handover executions
and X2-basedinter-frequency outgoing handover executions in a cell.
Measurement Points
As shown at point B in Figure 2-300, during an X2-basded handover the corresponding counter
is incremented by 1 in the target cell each time the source eNodeB sends an RRC Connection
Reconfiguration message to the UE after receiving a HANDOVER REQUEST
ACKNOWLEDGE message from the target eNodeB. The counters are measured as follows:
If the source cell and the target cell work on the same frequency, the
L.HHO.X2.IntraFreq.ExecAttOut counter is incremented by 1.
If the source cell and the target cell work on different frequencies, the
L.HHO.X2.InterFreq.ExecAttOut counter is incremented by 1.
Figure 2-300
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of successful X2-based intra-frequency outgoing handovers
and the number of successful X2-based inter-frequency outgoing handovers in a cell.
Measurement Points
As shown at point C in Figure 2-301, during an X2-based handover the corresponding counter
is incremented by 1 in the source cell each time the source eNodeB receives an UE CONTEXT
RELEASE message from the target eNodeB.
As shown at point C in Figure 2-302, the corresponding counter is incremented by 1 in the target
cell each time the source eNodeB receives a UE CONTEXT RELESE message from the target
eNodeB after an RRC connection is successfully reestablished to the target eNodeB for the UE.
If the source cell and the target cell work on the same frequency, the
L.HHO.X2.IntraFreq.ExecSuccOut counter is incremented by 1.
If the source cell and the target cell work on different frequencies, the
L.HHO.X2.InterFreq.ExecSuccOut counter is incremented by 1.
Figure 2-301
Figure 2-302
Figure 2-303
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of X2-based incoming handover failures for different causes
in a cell. The incoming handover failure usually occurs during the handover preparation phase.
During the handover preparation phase, between the handover decision phase and the handover
execution phase, the handover resources are prepared.
Measurement Points
As shown at point B in Figure 2-304, during an X2-based handover the
L.HHO.X2.FailOut.HOCancel counter is incremented by 1 each time the source cell decides to
cancel the handover and sends a HANDOVER CANCEL message to the target eNodeB.
Figure 2-304
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of successful X2-based outgoing handovers where RRC
connections are reestablished to the source cell for UEs in a cell.
Measurement Points
As shown at point C in Figure 2-305, during an X2-based handover the corresponding counter
is incremented by 1 each time the source cell receives an RRC Connection Reestablishment
Complete message from the UE. The counters are measured as follows:
If the source cell and the target cell work on the same frequency, the
L.HHO.X2.IntraFreq.Succ.ReEst2Src counter is incremented by 1.
If the source cell and the target cell work on different frequencies, the
L.HHO.X2.InterFreq.Succ.ReEst2Src counter is incremented by 1.
Figure 2-305
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The HO.DRX.Out.Cell function subset measures the performance of outgoing handovers of the
UE in the DRX state in a cell, as shown in Figure 2-306, Figure 2-307, and Figure 2-308.
Figure 2-306
Figure 2-307
Figure 2-308
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of executed intra-eNodeB intra-frequency and intra-eNodeB
inter-frequency outgoing handovers, respectively. The source cell and target cell of such a
handover are controlled by the same eNodeB and the UE enters the discontinuous reception
(DRX) state when the eNodeB decides to perform a handover.
Measurement Points
During such a handover, the source cell and target cell are controlled by the same eNodeBs and
the UE enters the DRX state when the eNodeB decides to perform a handover. As shown at point
B in Figure 2-309, if the source cell and target cell work on the same frequency, the
L.HHO.DRX.IntraeNB.IntraFreq.ExecAttOut counter is incremented by 1 in the source cell
each time the eNodeB sends an RRC Connection Reconfiguration message to the UE. If the
source cell and target cell work on different frequencies, the
L.HHO.DRX.IntraeNB.InterFreq.ExecAttOut counter is incremented by 1 accordingly.
Figure 2-309
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
TDLBFD-00201801 DRX
Coverage Based Intra-
frequency Handover
TDLBFD-00201802 DRX
Coverage Based Inter-
frequency Handover
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of successful intra-eNodeB intra-frequency and intra-eNodeB
inter-frequency outgoing handovers, respectively. The source cell and target cell of such a
handover are controlled by the same eNodeB and the UE enters the discontinuous reception
(DRX) state when the eNodeB decides to perform a handover.
Measurement Points
During such a handover, the source cell and target cell are controlled by the same eNodeB and
the UE enters the DRX state when the eNodeB decides to perform a handover. As shown at point
C in Figure 2-310 or Figure 2-311, the corresponding counter is incremented by 1 each time
data in the buffer is forwarded during the handover after the target or source cell receives an
RRC Connection Reconfiguration Complete or RRC Connection Reestablishment Complete
message from the UE. If the source cell and target cell work on the same frequency, the
L.HHO.DRX.IntraeNB.IntraFreq.ExecSuccOut counter is incremented by 1 in the source cell.
If the source cell and target cell work on different frequencies, the
L.HHO.DRX.IntraeNB.InterFreq.ExecSuccOut counter is incremented by 1 in the source cell.
Figure 2-310
Figure 2-311
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
TDLBFD-00201801 DRX
Coverage Based Intra-
frequency Handover
TDLBFD-00201802 DRX
Coverage Based Inter-
frequency Handover
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of executed inter-eNodeB intra-frequency and inter-eNodeB
inter-frequency outgoing handovers, respectively. The source cell and target cell of such a
handover are controlled by different eNodeBs and the UE enters the discontinuous reception
(DRX) state when the source eNodeB decides to perform a handover.
Measurement Points
During such a handover, the source cell and target cell are controlled by different eNodeBs and
the UE enters the DRX state when the source eNodeB decides to perform a handover. As shown
at point B in Figure 2-312 or Figure 2-313, if the source cell and target cell work on the same
frequency, the L.HHO.DRX.IntereNB.IntraFreq.ExecAttOut counter is incremented by 1 in the
source cell each time the source eNodeB sends an RRC Connection Reconfiguration message
to the UE after receiving a HANDOVER REQUEST ACKNOWLEDGE message from the
target eNodeB or receiving a HANDOVER COMMAND message from the MME. If the source
cell and target cell work on different frequencies, the
L.HHO.DRX.IntereNB.InterFreq.ExecAttOut counter is incremented by 1 accordingly.
Figure 2-312
Figure 2-313
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of successful inter-eNodeB intra-frequency and inter-eNodeB
inter-frequency outgoing handovers, respectively. The source cell and target cell of such a
handover are controlled by different eNodeBs and the UE enters the discontinuous reception
(DRX) state when the source eNodeB decides to perform a handover.
Measurement Points
During such a handover, the source cell and target cell are controlled by different eNodeBs and
the UE enters the DRX state when the source eNodeB decides to perform a handover.
As shown at point C in Figure 2-314, the corresponding counter is incremented by 1 each time
data in the buffer is completely forwarded during the handover after the source eNodeB receives
a UE CONTEXT RELEASE message from the target eNodeB during an X2-based handover.
As shown at point C in Figure 2-315, the corresponding counter is incremented by 1 each time
data in the buffer is completely forwarded during the handover after the UE is successfully
reestablished towards the target eNodeB during an X2-based handover and after the source
eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB.
As shown at point C in Figure 2-318, the corresponding counter is incremented by 1 each time
after the UE is successfully reestablished towards the source eNodeB during an X2-based
handover.
As shown at point C in Figure 2-316, the corresponding counter is incremented by 1 each time
data in the buffer is completely forwarded during the handover after the source eNodeB receives
a UE CONTEXT RELEASE COMMAND message from the MME during an S1-based
handover.
As shown at point C in Figure 2-317, the corresponding counter is incremented by 1 each time
data in the buffer is completely forwarded during the handover after the UE is successfully
reestablished towards the target eNodeB during an S1-based handover and after the source
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME.
As shown at point C in Figure 2-319, the corresponding counter is incremented by 1 each time
after the UE is successfully reestablished towards the source eNodeB during an S1-based
handover.
If the source cell and target cell work on the same frequency, the
L.HHO.DRX.IntereNB.IntraFreq.ExecSuccOut counter is incremented by 1.
If the source cell and target cell work on different frequencies, the
L.HHO.DRX.IntereNB.InterFreq.ExecSuccOut counter is incremented by 1.
Figure 2-314
Figure 2-315
Figure 2-316
Figure 2-317
Figure 2-318
Figure 2-319
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
TDLBFD-00201801 DRX
Overview
The Traffic.Packet.Cell function subset measures the processing delay and loss rate of uplink
or downlink PDCP SDUs of each service with a different QCI in a cell.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
2.2.29.1 Total Processing Delay of Downlink PDCP SDUs for DRB Services in a
Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the total processing delay of downlink PDCP SDUs for DRB services
with a specific QCI ranging from 1 to 9 in a cell. If this cell is an SCell of a CA UE, the processing
delay of downlink PDCP SDUs for the CA UE is also counted in the corresponding counter.
Measurement Points
The total processing delay of downlink PDCP SDUs for DRB services with a specific QCI
ranging from 1 to 9 is sampled in a cell. At the end of a measurement period, the sum of these
sampling results is used as the value of the corresponding counter.
Formula
None
Unit
ms
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of successfully transmitted downlink PDCP SDUs for DRB
services with a specific QCI ranging from 1 to 9 in a cell. If this cell is an SCell of a CA UE,
the number of successfully transmitted downlink PDCP SDUs for the CA UE is also counted in
the corresponding counter.
Measurement Points
The corresponding counter is incremented by 1 based on the QCI each time a PDCP SDU is
successfully sent. A PDCP SDU is successfully sent if an HARQ ACK is received.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
2.2.29.3 Total Number of Discarded Downlink PDCP SDUs for DRB Services in a
Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the total number of discarded downlink PDCP SDUs for DRB services
with a specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The total number of discarded downlink PDCP SDUs for DRB services with a specific QCI
ranging from 1 to 9 is sampled per second. At the end of a measurement period, the sum of these
sampling results is used as the value of the corresponding counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
2.2.29.4 Total Number of Transmitted Downlink PDCP SDUs for DRB Services in
a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the total number of transmitted downlink PDCP SDUs for DRB services
with a specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The total number of transmitted downlink PDCP SDUs for DRB services with a specific QCI
ranging from 1 to 9 is sampled per second. At the end of a measurement period, the sum of these
sampling results is used as the value of the corresponding counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
2.2.29.5 Total Number of Discarded Uplink PDCP SDUs for DRB Services in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the total number of discarded uplink PDCP SDUs for DRB services with
a specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The total number of discarded uplink PDCP SDUs for DRB services with a specific QCI ranging
from 1 to 9 is sampled per second. At the end of a measurement period, the sum of these sampling
results is used as the value of the corresponding counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
2.2.29.6 Total Number of Expected Uplink Data Packets for DRB Services in a Cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the total number of expected uplink data packets for DRB services with
a specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The total number of expected uplink data packets for DRB services with a specific QCI ranging
from 1 to 9 is sampled per second. The sampling result is calculated by accumulating the
difference between the sequence numbers of the current PDCP PDU and previous PDCP PDU
once the PDCP layer receives a PDCP PDU. At the end of a measurement period, the sum of
these sampling results is used as the value of the corresponding counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Overview
The ChMeas.DFEE.Cell function subset measures the duration when a cell enters the energy
saving and emission reduction state, including RF channel intelligent shutdown, and intelligent
power-off of carriers in the same coverage of UMTS network or intelligent power-off of carriers.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the duration when the cell is in the energy saving and emission reduction
state (including RF channel intelligent shutdown, and intelligent power-off of carriers in the
same coverage of UMTS network or intelligent power-off of carriers in the same coverage).
Measurement Points
The energy saving mode of a cell is sampled per second. If the cell is in the energy saving and
emission reduction state (including RF channel intelligent shutdown, and intelligent power-off
of carriers in the same coverage of UMTS network or intelligent power-off of carriers in the
same coverage), the sampling result is 1 second. At the end of a measurement period, the sum
of these sampling results is used as the value of the corresponding counter. A deviation of one
sampling period may exist in the sampling timer when the timer performs time synchronization.
As a result, a deviation of one sampling period will also be generated in the value of the
corresponding counter. The deviation affects the values of the KPIs that are calculated by using
the counter. The effects vary with the deviation in the value of the counter and calculation
formulas for the KPIs.
Formula
None
Unit
s
Related Features
Counter Name Feature ID Feature Name
Overview
Location Service (LCS) provides a means to determine the geographic position and velocity of
the UE based on measuring radio signals. The Enhanced Cell ID (E-CID) and Observed Time
Difference of Arrival (OTDOA) positioning techniques are supported by the eNodeB. The
LCS.Cell function subset measures the number of E-CID measurement requests and successful
E-CID measurement requests in a cell. The values of the two counters are used to calculate the
successful E-CID measurement rate.
Figure 2-320
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of LCS E-CID MEASUREMENT INITIATION REQUEST
messages received by the eNodeB from the E-SMLC. The LCS E-CID MEASUREMENT
INITIATION REQUEST message is an LPPa signaling message. The message is sent by the E-
SMLC to an eNodeB, requesting the E-CID measurement.
Measurement Points
as shown at point A in Figure 2-321, the L.LCS.EcidMeas.Req counter is incremented by 1
each time the eNodeB receives an E-CID MEASUREMENT INITIATION REQUEST message.
Figure 2-321
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of E-CID MEASUREMENT INITIATION RESPONSE
messages in a cell. The E-CID MEASUREMENT INITIATION RESPONSE message is an
LPPa signaling message sent from an eNodeB to the E-SMLC. The message is used to notify
the E-SMLC that the E-CID measuring is successfully performed and report the E-CID
measurement data.
Measurement Points
as shown at point B in Figure 2-322, the L.LCS.EcidMeas.Succ counter is incremented by 1
each time the eNodeB sends an E-CID MEASUREMENT INITIATION RESPONSE message.
Figure 2-322
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The EMC.Cell function subset measures the counters related to emergency calls in a cell.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of intra-eNodeB and inter-eNodeB outgoing handover
attempts. Intra-eNodeB outgoing handovers include intra-eNodeB intra-frequency and intra-
eNodeB inter-frequency outgoing handovers. Similarly, inter-eNodeB outgoing handovers
include inter-eNodeB intra-frequency and inter-eNodeB inter-frequency outgoing handovers.
Measurement Points
During a handover where the source cell and target cell are controlled by the same eNodeB, as
shown at point A in Figure 2-323, the counter is incremented by 1 each time the eNodeB decides
to perform an intra-eNodeB outgoing handover for an emergency call after receiving a
measurement report from the UE.
Figure 2-324 shows a handover over the X2 interface. During such a handover where the source
cell and target cell are controlled by different eNodeBs, as shown at point A in Figure 2-324,
the counter is incremented by 1 each time the source eNodeB decides to perform an inter-eNodeB
handover over the X2 interface for an emergency call after receiving a measurement report from
the UE.
Figure 2-325 shows a handover over the S1 interface. During such a handover where the source
cell and target cell are controlled by different eNodeBs, as shown at point A in Figure 2-325,
the counter is incremented by 1 each time the source eNodeB decides to perform an inter-eNodeB
handover over the S1 interface for an emergency call after receiving a measurement report from
the UE.
Figure 2-323
Figure 2-324
Figure 2-325
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of executed intra-eNodeB and inter-eNodeB outgoing
handovers. Intra-eNodeB outgoing handovers include intra-eNodeB intra-frequency and intra-
eNodeB inter-frequency outgoing handovers. Similarly, inter-eNodeB outgoing handovers
include inter-eNodeB intra-frequency and inter-eNodeB inter-frequency outgoing handovers.
Measurement Points
The counter is incremented if any of the following conditions occurs:
(1) During an intra-eNodeB handover, as shown at point B in Figure 2-326, the source cell sends
an RRC Connection Reconfiguration message to the UE for an emergency call.
(2) During a handover over the X2 interface, as shown at point B in Figure 2-327, the source
eNodeB sends an RRC Connection Reconfiguration message to the UE for an emergency call
after receiving a HANDOVER REQUEST ACKNOWLEDGE message from the target eNodeB.
(3) During a handover over the S1 interface, as shown at point B in Figure 2-328, the source
eNodeB sends an RRC Connection Reconfiguration message to the UE for an emergency call
after receiving a HANDOVER COMMAND message from the MME.
Figure 2-326
Figure 2-327
Figure 2-328
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful intra-eNodeB and inter-eNodeB outgoing
handovers in a cell. Intra-eNodeB outgoing handovers include intra-eNodeB intra-frequency
and intra-eNodeB inter-frequency outgoing handovers. Similarly, inter-eNodeB outgoing
handovers include inter-eNodeB intra-frequency and inter-eNodeB inter-frequency outgoing
handovers.
Measurement Points
As shown at point C in Figure 2-329, the counter is incremented by 1 each time the eNodeB
receives an RRC Connection Reconfiguration Complete message from the UE for an emergency
call after the eNodeB decides to perform an intra-eNodeB handover.
As shown at point C in Figure 2-330, the counter is incremented by 1 each time the target cell
receives an RRC Connection Reestablishment Complete message from the UE for an emergency
call.
As shown at point C in Figure 2-330, the counter is incremented by 1 each time the source cell
receives an RRC Connection Reestablishment Complete message from the UE for an emergency
call.
As shown at point C in Figure 2-331, the counter is incremented by 1 each time the source
eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB for an
emergency call after the eNodeB decides to perform an X2-based handover.
As shown at point C in Figure 2-332, the counter is incremented by 1 each time the source
eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB for an
emergency call after an RRC connection is successfully reestablished for the UE towards the
target eNodeB during X2-based handover.
As shown at point C in Figure 2-335, the counter is incremented by 1 each time for an emergency
call after an RRC connection is successfully reestablished for the UE towards the source eNodeB
during X2-based handover.
As shown at point C in Figure 2-333, the counter is incremented by 1 each time the source
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME for an
emergency call after the eNodeB decides to perform an S1-based handover.
As shown at point C in Figure 2-334, the counter is incremented by 1 each time the source
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME for an
emergency call after an RRC connection is successfully reestablished for the UE towards the
target eNodeB during S1-based handover.
As shown at point C in Figure 2-336, the counter is incremented by 1 each time for an emergency
call after an RRC connection is successfully reestablished for the UE towards the source eNodeB
during S1-based handover.
Figure 2-329
Figure 2-330
Figure 2-331
Figure 2-332
Figure 2-333
Figure 2-334
Figure 2-335
Figure 2-336
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of E-RAB setup attempts for emergency calls in a cell.
Measurement Points
As shown at point A in Figure 2-337 or Figure 2-338, the counter is incremented by 1 each
time the eNodeB receives an E-RAB SETUP REQUEST message or an INITIAL CONTEXT
SETUP REQUEST message from the MME for an emergency call.
Figure 2-337
Figure 2-338
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful E-RAB setups for emergency calls in a cell.
Measurement Points
As shown at point B in Figure 2-339 or Figure 2-340, the counter is incremented by 1 each time
the eNodeB sends an E-RAB SETUP RESPONSE message or an INITIAL CONTEXT SETUP
RESPONSE message to the MME for a successfully established emergency call.
Figure 2-339
Figure 2-340
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of normal E-RAB releases due to outgoing handovers for
emergency calls.
Measurement Points
Figure 2-341 shows an intra-eNodeB handover, Figure 2-342 shows a handover over the X2
interface, and Figure 2-343 shows a handover over the S1 interface. As shown at point C in
Figure 2-341, Figure 2-342, or Figure 2-343, the counter is incremented by 1 in the source cell
each time the source cell normally releases an E-RAB that corresponds to a successful E-RAB
setup in the target cell after a handover is successfully performed and the E-RAB is released for
an emergency call.
Figure 2-341
Figure 2-342
Figure 2-343
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of abnormal E-RAB releases due to outgoing handovers for
emergency calls in a cell.
Measurement Points
Figure 2-344 shows an intra-eNodeB handover, Figure 2-345 shows a handover over the X2
interface, and Figure 2-346 shows a handover over the S1 interface. As shown at point C in
Figure 2-344, Figure 2-345, or Figure 2-346, the counter is incremented by 1 in the source cell
each time the source cell abnormally releases an E-RAB that corresponds to a failed E-RAB
setup in the target cell after a handover is successfully performed, and the E-RAB is released
for an emergency call.
Figure 2-344
Figure 2-345
Figure 2-346
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of abnormal E-RAB releases for emergency calls in a cell.
Measurement Points
As shown at point A in Figure 2-347, the counter is incremented by 1 each time the eNodeB
sends an E-RAB RELEASE INDICATION message to the MME for an E-RAB that carries data
for an emergency call and the release cause is not "Normal Release", "Detach", "User Inactivity",
"CS Fallback triggered", "UE Not Available For PS Service", or "Inter-RAT Redirection". If
the E-RAB RELEASE INDICATION message requires multiple E-RAB releases at the same
time, the corresponding counter is incremented based on the number of services.
As shown at point A in Figure 2-348, all E-RABs of the UE are released each time the eNodeB
sends a UE CONTEXT RELEASE REQUEST message to the MME. The counter is incremented
by 1 each time the eNodeB determines that the E-RAB carries data for an emergency call and
the release cause is not "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered",
"UE Not Available For PS Service", "Inter-RAT Redirection", "Time Critical Handover" or
"Handover Cancelled". The corresponding counter is incremented repeatedly based on the
number of services. When the MME responds to the eNodeB with a UE CONTEXT RELEASE
COMMAND message, the counter is not incremented.
Figure 2-347
Figure 2-348
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of normal E-RAB releases for emergency calls in a cell.
Measurement Points
As shown at point A in Figure 2-349, the eNodeB sends an E-RAB RELEASE INDICATION
message to the MME. The L.EMC.E-RAB.NormRel counter is incremented by 1 each time the
release cause is "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered", "UE
Not Available For PS Service" or "Inter-RAT Redirection" for an emergency call, or the eNodeB
determines that the E-RAB to be released does not carry data. If the E-RAB RELEASE
INDICATION message requires multiple E-RAB releases at the same time, the L.EMC.E-
RAB.NormRel counter is incremented based on the number of services.
As shown at point A in Figure 2-351, all E-RABs of the UE will be released each time the
eNodeB sends a UE CONTEXT RELEASE REQEUST message to the MME during an eNodeB-
initiated UE context release. The L.EMC.E-RAB.NormRel counter is incremented by 1 each
time the release cause is "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered",
"UE Not Available For PS Service", "Inter-RAT Redirection", "Time Critical Handover", or
"Handover Cancelled" for an emergency call, or the eNodeB determines that the E-RAB to be
released does not carry data. The corresponding counter is incremented repeatedly based on the
number of services. When the MME responds to the eNodeB with a UE CONTEXT RELEASE
COMMAND message, the counter is not incremented.
As shown at point B in Figure 2-351, all E-RABs of the UE will be released when the eNodeB
receives a UE CONTEXT RELEASE COMMAND message from the MME. The L.EMC.E-
RAB.NormRel counter is incremented by one each time the released E-RAB is used for an
emergency call and the release cause is not "Successful Handover ", "Partial Handover ", "S1
intra system Handover triggered ", "S1 inter system Handover triggered ", or "X2 Handover
triggered ".
Figure 2-349
Figure 2-350
Figure 2-351
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
UE context contains user-specific context information throughout the network. The release
success rate of UE contexts represents the capability of a cell to retrieve the UE resources. The
UeCntx.Rel.Cell function subset measures the number of abnormal or normal UE context
releases in a cell. Based on the values of the counters, the release success rate of UE contexts in
a cell is determined. The measurement point of the function subset is shown in Figure 2-352.
Figure 2-352
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.UECNTX.Rel.eNodeB L.UECNTX.Rel.eNodeB.Rnl
L.UECNTX.Rel.eNodeB.Userinact
L.UECNTX.Rel.eNodeB.Rnl L.UECNTX.Rel.eNodeB.UeLost
L.UECNTX.Rel.eNodeB.HOFailure
L.UECNTX.Rel.MME L.UECNTX.Rel.MME.Normalrel
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of abnormal UE context releases in a cell. Abnormal UE
context releases are releases initiated by the eNodeB due to exceptions and the releases due to
the S1 RESET initiated by the eNodeB or MME.
Measurement Points
As shown at point A in Figure 2-353, all E-RABs of the UE are released if the eNodeB sends
a UE CONTEXT RELEASE REQUEST message to the MME for the UE. The
L.UECNTX.AbnormRel counter is incremented by 1 each time the cause value is not "Normal
Release", "Detach", "User Inactivity", "CS Fallback triggered", "UE Not Available for PS
Service", "Inter-RAT Redirection", "Time Critical Handover", or "Handover Cancelled".
As shown at point A in Figure 2-354, when the eNodeB sends a S1 RESET message to the
MME, the L.UECNTX.Rel.S1Reset.eNodeB counter is accumulated by the number of contexts
in the message.
As shown at point A in Figure 2-355, when the MME sends a S1 RESET message to the eNodeB,
the L.UECNTX.Rel.S1Reset.MME counter is accumulated by the number of contexts in the
message.
Figure 2-353
Figure 2-354
Figure 2-355
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of normal UE context releases in a cell. A normal UE context
release is initiated by the MME or by the eNodeB due to a normal cause.
Measurement Points
As shown at point A in Figure 2-356, the counter is incremented by 1 each time the eNodeB
sends a UE CONTEXT RELEASE REQEUST message to the MME and the cause value is
"Normal Release", "Detach", "User Inactivity", "CS Fallback triggered", "UE Not Available for
PS Service", "Inter-RAT Redirection", "Time Critical Handover", or "Handover Cancelled". In
this case, the counter is not incremented again when the eNodeB receives the UE CONTEXT
RELEASE COMMAND message from the MME.
As shown at point B in Figure 2-356, the counter is incremented by 1 each time the MME sends
the UE CONTEXT RELEASE COMMAND message to the eNodeB to release the UE context
and the release cause is not "Successful Handover ", "Partial Handover ", "S1 intra system
Handover triggered ", "S1 inter system Handover triggered ", or "X2 Handover triggered ".
Figure 2-356
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of UE context releases due to high mobility of UEs with no
data transmission.
Measurement Points
As shown at point A in Figure 2-357, The L.UECNTX.Release.HighSpeed counter is
incremented by 1 each time the eNodeB actively releases the context of a high-mobility UE
without data transmission and sends a UE CONTEXT RELEASE REQUEST message to the
MME.
Figure 2-357
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
LBFD-002008 High-Mobility-Triggered
Idle Mode
TDLBFD-002008
Radio Bearer Management
Radio Bearer Management
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of UE context releases during an inter-RAT measurement in
a cell.
Measurement Points
As shown at point A in Figure 2-358, after the eNodeB sends the UE a measurement control
message for the WCDMA network due to poor coverage, the eNodeB sends a UE CONTEXT
RELEASE REQUEST message to the MME before receiving a measurement report for the
WCDMA network from the UE. The L.UECNTX.Release.DurMeasU counter is incremented
by 1 each time the cause value contained in the message is "Radio Connection With UE Lost"
or "Failure in the Radio Interface Procedure".
As shown at point A in Figure 2-358, after the eNodeB sends the UE a measurement control
message for the GERAN due to poor coverage, the eNodeB sends a UE CONTEXT RELEASE
REQUEST message to the MME before receiving a measurement report for the GERAN from
the UE. The L.UECNTX.Release.DurMeasG counter is incremented by 1 each time the cause
value contained in the message is "Radio Connection With UE Lost" or "Failure in the Radio
Interface Procedure".
Figure 2-358
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of UE context releases initiated by the eNodeB in a cell.
Measurement Points
As shown at point A in Figure 2-359, this counter is incremented by 1 each time the eNodeB
sends the UE CONTEXT RELEASE REQUEST message to the MME to release a UE context
that has been successfully set up.
Figure 2-359
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of UE context releases initiated by the eNodeB due to different
causes.
Measurement Points
As shown at point A in Figure 2-360, after a UE context is successfully set up, it is released if
the eNodeB sends the UE CONTEXT RELEASE REQUEST message to the MME. The
L.UECNTX.Rel.eNodeB.Rnl counter is incremented by 1 if the release is caused by faults at
the radio network layer. The L.UECNTX.Rel.eNodeB.Userinact counter is incremented by 1 if
the release cause is "User Inactivity". The L.UECNTX.Rel.eNodeB.UeLost counter in
incremented if the release cause is "Radio Connection With UE Lost". The
L.UECNTX.Rel.eNodeB.HOFailure counter is incremented by 1 if the release is caused by a
handover failure.
Figure 2-360
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of UE context releases initiated by the MME in a cell.
Measurement Points
As shown at point A in Figure 2-361,this counter is incremented by 1 each time the MME sends
the UE CONTEXT RELEASE COMMAND message to the eNodeB to release the UE context
and the release cause is not "Successful Handover ", "Partial Handover ", "S1 intra system
Handover triggered ", "S1 inter system Handover triggered ", or "X2 Handover triggered ".
Figure 2-361
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of UE context releases due to "Normal Release".
Measurement Points
As shown at point A in Figure 2-362, this counter is incremented by 1 each time the MME sends
the UE CONTEXT RELEASE COMMAND message to the eNodeB to release a UE context
that has been successfully set up and the release cause is "Normal Release".
Figure 2-362
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The SFN.Cell function subset measures the used resources and number of scheduled resources
in an SFN cell, indicating the operating status of the SFN cell.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The coutners measures the number of times when the downlink attribute of a UE changes from
independent-scheduling to joint-scheduling
Measurement Points
The counter is incremented by 1 each time the downlink attribute of a UE changes from
independent-scheduling to joint-scheduling.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measures the number of times when the downlink attribute of a UE changes from
joint -scheduling to independent-scheduling
Measurement Points
The counter is incremented by 1 each time the downlink attribute of a UE changes from joint-
scheduling to independent-scheduling.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.34.3 Number of Times that the Downlink Target RRU of a UE in an SFN Cell
Changes
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures number of times that the downlink target RRU of a UE in an SFN cell
changes
Measurement Points
The L.SFN.DLTRRU.Chg couner is incremented by 1 each time the downlink target RRU of a
UE in an SFN cell changes.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the average number of joint-scheduling UEs in uplink
Measurement Points
The number of uplink joint-scheduling UEs in an SFN cell is sampled per second. At the end of
an measurement period, the average of these sampling results is used as the value of the counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the average number of work RRUs for a UE involved in uplink joint
scheduling in an SFN cell. After a UE accesses the network, the number of work RRUs for the
UE is added to this counter. Each time when a UE decides the uplink attribute of an SFN cell,
this counter increases or decreases correspondingly if a UE work RRU set changes. After the
UE exits the network, the number of RRUs for the UE is deducted from this counter.
Measurement Points
The number of working RRUs used by uplink joint-scheduling UEs in an SFN cell is sample
per second. At the end of a measurement period, the average of these sampling results is used
as the value of the counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measures the number of times when the uplink attribute of a UE changes from
independent-scheduling to joint-scheduling
Measurement Points
The counter is incremented by 1 each time the uplink attribute of a UE changes from independent-
scheduling to joint-scheduling.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.34.7 Number of Times When the Uplink Attribute of a UE Changes from Joint-
scheduling to Independent-scheduling in an SFN cell
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counte measures the number of times when the uplink attribute of a UE changes from joint
-scheduling to independent-scheduling
Measurement Points
The counter is incremented by 1 each time the uplink attribute of a UE changes from joint-
scheduling to independent-scheduling.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
2.2.34.8 Number of Times that the Uplink Target RRU of a UE in an SFN Cell
Changes
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of times that the uplink target RRU of a UE in an SFN cell
changes
Measurement Points
The L.SFN.ULTRRU.Chg couner is incremented by 1 each time the uplink target RRU of a UE
in an SFN cell changes.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the average number of joint-scheduling UEs in downlink
Measurement Points
The number of downlink joint-scheduling UEs in an SFN cell is sampled per second. At the end
of an measurement period, the average of these sampling results is used as the value of the
counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the average number of work RRUs for a UE involved in downlink joint
scheduling in an SFN cell.After a UE accesses the network, the number of work RRUs for the
UE is added to this counter. Each time when a UE decides the downlink attribute of an SFN cell,
this counter increases or decreases correspondingly if a UE work RRU set changes. After the
UE exits the network, the number of work RRUs for the UE is deducted from this counter.
Measurement Points
The number of working RRUs used by downlink joint-scheduling UEs in an SFN cell is sample
per second. At the end of a measurement period, the average of these sampling results is used
as the value of the counter.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Figure 2-363
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of UE context modification attempts.
Measurement Points
As shown at point A in Figure 2-364, the L.UECNTX.Modify.Att counter is incremented by 1
each time the eNodeB receives a UE CONTEXT MODIFICATION REQUEST message from
the MME.
Figure 2-364
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful UE context modifications.
Measurement Points
As shown at point B in Figure 2-365, the L.UECNTX.Modify.Succ counter is incremented by
1 each time the eNodeB sends a UE CONTEXT MODIFICATION RESPONSE message to the
MME.
Figure 2-365
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The CA.Cell function subset measures the service drop rate and handover success rate of CA
UEs in a cell.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of abnormal E-RAB releases for CA UEs in a cell. An E-RAB
is the access layer bearer for carrying service data of UEs. The E-RAB release is a process of
releasing the access layer bearer resources of UEs. It represents the capability of a cell to release
access layer bearer resources for UEs.
Measurement Points
As shown at point A in Figure 2-366, the eNodeB sends an E-RAB RELEASE INDICATION
message to the MME. The L.E-RAB.AbnormRel.CAUser counter is incremented by 1 each time
the eNodeB determines that the E-RAB to be released carries data and the Release Cause
information element of the message is not "Normal Release", "Detach", "User Inactivity", "CS
Fallback triggered", "UE Not Available For PS Service", or "Inter-RAT Redirection". If the E-
RAB RELEASE INDICATION message requires multiple E-RAB releases at the same time,
the corresponding counter is incremented according to the number of E-RABs.
As shown at point A in Figure 2-367, all E-RABs of the UE are released each time the eNodeB
sends a UE CONTEXT RELEASE REQUEST message to the MME. The L.E-
RAB.AbnormRel.CAUser counter is incremented by 1 each time the eNodeB determines that
the E-RAB to be released carries data and the Release Cause information element of the message
is not "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered", "UE Not
Available For PS Service", "Inter-RAT Redirection", "Time Critical Handover", or "Handover
Cancelled". When the MME sends a UE CONTEXT RELEASE COMMAND message to the
eNodeB, the L.E-RAB.AbnormRel.CAUser counter is not incremented.
Figure 2-366
Figure 2-367
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of normal E-RAB releases for CA UEs in a cell. An E-RAB
is the access layer bearer for carrying service data of UEs. The E-RAB release is a process of
releasing the access layer bearer resources of UEs. It represents the capability of a cell to release
access layer bearer resources for UEs.
Measurement Points
As shown at point A in Figure 2-368, the eNodeB initiates E-RAB release and sends an E-RAB
RELEASE INDICATION message to the MME. The L.E-RAB.NormRel.CAUser counter is
incremented when either of the following conditions is met: (1) The UE is a CA UE and the
Release Cause IE in the E-RAB RELEASE INDICATION message is "Normal Release",
"Detach", "User Inactivity", "CS Fallback triggered", "UE Not Available For PS Service", or
"Inter-RAT Redirection". (2) The eNodeB determines that no data is transmitted on the
associated E-RAB.
If the E-RAB RELEASE INDICATION message requires multiple E-RAB releases at the same
time, the L.E-RAB.NormRel.CAUser counter is incremented based on the number of E-RABs.
As shown at point A in Figure 2-370, in the eNodeB-initiated E-RAB release, all E-RABs of a
UE are released when the eNodeB sends a UE CONTEXT RELEASE REQUEST message to
the MME. The L.E-RAB.NormRel.CAUser counter is incremented when either of the following
conditions is met: (1) The UE is a CA UE and the Release Cause IE in the UE CONTEXT
RELEASE REQUEST message is "Normal Release", "Detach", "User Inactivity", "CS Fallback
triggered", "UE Not Available for PS Service", "Inter-RAT Redirection", "Time Critical
Handover", or "Handover Cancelled". (2) The eNodeB determines that no data is transmitted on
the associated E-RAB. The L.E-RAB.NormRel.CAUser counter is incremented based on the
number of E-RABs. When the MME sends a UE CONTEXT RELEASE COMMAND message
to the eNodeB, the L.E-RAB.NormRel.CAUser counter is not incremented.
As shown at point B in Figure 2-370, in the MME-initiated E-RAB release, all E-RABs of a
UE are released, when the eNodeB receives a UE CONTEXT RELEASE COMMAND message
from the MME and the UE is a CA UE. The L.E-RAB.NormRel.CAUser counter is incremented
if the release cause is not "Successful Handover ", "Partial Handover ", "S1 intra system
Handover triggered ", "S1 inter system Handover triggered ", or "X2 Handover triggered ". The
L.E-RAB.NormRel.CAUser counter is incremented based on the number of E-RABs.
Figure 2-368
Figure 2-369
Figure 2-370
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of intra-eNodeB and inter-eNodeB outgoing handover
attempts of CA UEs.
Measurement Points
As shown at point A in Figure 2-371, the L.HHO.PrepAttOut.CAUser.PCC counter is
incremented by 1 each time the eNodeB determines to perform an intra-eNodeB blind handover
during an intra-eNodeB handover trigger of a CA UE or the eNodeB determines to perform an
intra-eNodeB handover after the serving cell receives a Measurement Report message from the
UE.
Figure 2-371
Figure 2-372
Figure 2-373
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of intra-eNodeB and inter-eNodeB outgoing handover
executions of CA UEs.
Measurement Points
As shown at point B in Figure 2-374, the L.HHO.ExecAttOut.CAUser.PCC counter is
incremented by 1 each time the source eNodeB sends an RRC Connection Reconfiguration
message to the CA UE during intra-eNodeB handover.
As shown at point B in Figure 2-375, during an X2-based handover the
L.HHO.ExecAttOut.CAUser.PCC counter is incremented by 1 each time the source eNodeB
sends an RRC Connection Reconfiguration message to the CA UE after the source eNodeB
receives a HANDOVER REQUEST ACKNOWLEDGE message from the target eNodeB.
As shown at point B in Figure 2-376, during an S1-based handover the
L.HHO.ExecAttOut.CAUser.PCC counter is incremented by 1 each time the source eNodeB
sends an RRC Connection Reconfiguration message to the CA UE after the source eNodeB
receives a HANDOVER COMMAND from the MME.
Figure 2-374
Figure 2-375
Figure 2-376
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful intra-eNodeB and inter-eNodeB outgoing
handover executions of CA UEs.
Measurement Points
As shown at point C in Figure 2-377, during an intra-eNodeB handover the
L.HHO.ExecSuccOut.CAUser.PCC counter is incremented by 1 each time data in the buffer is
forwarded after the source cell receives an RRC Connection Reconfiguration Complete message
from the CA UE.
As shown at point C in Figure 2-380, during an X2-based handover, after the RRC connection
to the target eNodeB for a CA UE is reestablished, the L.HHO.ExecSuccOut.CAUser.PCC
counter is incremented by 1 each time data in the buffer is forwarded after the source eNodeB
receives a UE CONTEXT RELEASE message from the target eNodeB.
As shown at point C in Figure 2-382, during an S1-based handover, after the RRC connection
to the target eNodeB for a CA UE is reestablished, the L.HHO.ExecSuccOut.CAUser.PCC
counter is incremented by 1 each time data in the buffer is forwarded after the source eNodeB
receives a UE CONTEXT RELEASE COMMAND message from the MME.
Figure 2-377
Figure 2-378
Figure 2-379
Figure 2-380
Figure 2-381
Figure 2-382
Figure 2-383
Figure 2-384
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The Traffic.RLC.Cell function subset measures the numbers of retransmitted packets, discarded
packets, total packets, and retransmitted bytes in AM mode at the RLC layer in a cell.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The volume of retransmitted data at the RLC layer in AM mode is influenced by the channel
quality. The counter measures the total bits of retransmitted uplink RLC PDUs in AM mode.
The counter value is used to analyze the radio resources used for retransmission.
Measurement Points
The number of bits of retransmitted RLC PDUs in AM mode received from UEs in a cell is
sampled in a measurement period. At the end of a measurement period, the sum of these sampling
results is used as the value of the L.Traffic.UL.AM.Retrans.bits counter.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The volume of retransmitted data at the RLC layer in AM mode is influenced by the channel
quality. The counter measures the total bits of retransmitted downlink RLC PDUs in AM mode.
The counter value is used to analyze the radio resources used for retransmission.
Measurement Points
The number of bits of retransmitted RLC PDUs in AM mode sent to UEs in a cell is sampled in
a measurement period. At the end of a measurement period, the sum of these sampling results
is used as the value of the L.Traffic.DL.AM.Retrans.bits counter.
Formula
None
Unit
bit
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The volume of retransmitted data at the RLC layer in AM mode is influenced by the channel
quality. The counter measures the total number of uplink RLC PDUs in AM mode. The counter
value is used to compare with the data traffic.
Measurement Points
The number of RLC PDUs received in AM mode from UEs in a cell is sampled in a measurement
period. At the end of a measurement period, the sum of these sampling results is used as the
value of the L.Traffic.UL.AM.RxPackets counter. The resegmented RLC PDUs are also counted
in the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The volume of retransmitted data at the RLC layer in AM mode is influenced by the channel
quality. The counter measures the total number of downlink RLC PDUs in AM mode. The
counter value is used to compare with the data traffic.
Measurement Points
The number of RLC PDUs sent in AM mode to UEs in a cell is sampled in a measurement period.
At the end of a measurement period, the sum of these sampling results is used as the value of
the L.Traffic.DL.AM.TxPackets counter. The resegmented RLC PDUs are also counted in the
counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The volume of retransmitted data at the RLC layer in AM mode is influenced by the channel
quality. The counter measures the total number of retransmitted uplink RLC PDUs in AM mode.
The counter value is used to analyze the radio resources used for retransmission.
Measurement Points
The total number of retransmitted RLC PDUs in AM mode received from UEs in a cell is sampled
in a measurement period. At the end of a measurement period, the sum of these sampling results
is used as the value of the L.Traffic.UL.AM.Retrans.RxPackets counter. The resegmented RLC
PDUs are also counted in the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The volume of retransmitted data at the RLC layer in AM mode is influenced by the channel
quality. The counter measures the total number of retransmitted downlink RLC PDUs in AM
mode. The counter value is used to analyze the radio resources used for retransmission.
Measurement Points
The total number of retransmitted RLC PDUs in AM mode sent to UEs in a cell is sampled in
a measurement period. At the end of a measurement period, the sum of these sampling results
is used as the value of the L.Traffic.DL.AM.Retrans.TxPackets counter. The resegmented RLC
PDUs are also counted in the counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The volume of retransmitted data at the RLC layer in AM mode is influenced by the channel
quality. The counter measures the number of downlink RLC PDUs that fail to be sent to UEs
after retransmission and are discarded in a cell.
Measurement Points
The total number of downlink RLC PDUs failed to be sent to UEs after retransmission in AM
mode in a cell is sampled in a measurement period. At the end of a measurement period, the sum
of these sampling results is used as the value of the L.Traffic.DL.AM.TxDropPackets counter.
Formula
None
Unit
packet
Related Features
Counter Name Feature ID Feature Name
Overview
The Reserve.Cell function subset is reserved.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
2.2.38.1 L.Reserve.1
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.1
Measurement Points
L.Reserve.1
Formula
None
Unit
None
Related Features
None
2.2.38.2 L.Reserve.2
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.2
Measurement Points
L.Reserve.2
Formula
None
Unit
None
Related Features
None
2.2.38.3 L.Reserve.3
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.3
Measurement Points
L.Reserve.3
Formula
None
Unit
None
Related Features
None
2.2.38.4 L.Reserve.4
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.4
Measurement Points
L.Reserve.4
Formula
None
Unit
None
Related Features
None
2.2.38.5 L.Reserve.5
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.5
Measurement Points
L.Reserve.5
Formula
None
Unit
None
Related Features
None
2.2.38.6 L.Reserve.6
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.6
Measurement Points
L.Reserve.6
Formula
None
Unit
None
Related Features
None
2.2.38.7 L.Reserve.7
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.7
Measurement Points
L.Reserve.7
Formula
None
Unit
None
Related Features
None
2.2.38.8 L.Reserve.8
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.8
Measurement Points
L.Reserve.8
Formula
None
Unit
None
Related Features
None
2.2.38.9 L.Reserve.9
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.9
Measurement Points
L.Reserve.9
Formula
None
Unit
None
Related Features
None
2.2.38.10 L.Reserve.10
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.10
Measurement Points
L.Reserve.10
Formula
None
Unit
None
Related Features
None
2.2.38.11 L.Reserve.11
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.11
Measurement Points
L.Reserve.11
Formula
None
Unit
None
Related Features
None
2.2.38.12 L.Reserve.12
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.12
Measurement Points
L.Reserve.12
Formula
None
Unit
None
Related Features
None
2.2.38.13 L.Reserve.13
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.13
Measurement Points
L.Reserve.13
Formula
None
Unit
None
Related Features
None
2.2.38.14 L.Reserve.14
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.14
Measurement Points
L.Reserve.14
Formula
None
Unit
None
Related Features
None
2.2.38.15 L.Reserve.15
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.15
Measurement Points
L.Reserve.15
Formula
None
Unit
None
Related Features
None
2.2.38.16 L.Reserve.16
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.16
Measurement Points
L.Reserve.16
Formula
None
Unit
None
Related Features
None
2.2.38.17 L.Reserve.17
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.17
Measurement Points
L.Reserve.17
Formula
None
Unit
None
Related Features
None
2.2.38.18 L.Reserve.18
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.18
Measurement Points
L.Reserve.18
Formula
None
Unit
None
Related Features
None
2.2.38.19 L.Reserve.19
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.19
Measurement Points
L.Reserve.19
Formula
None
Unit
None
Related Features
None
2.2.38.20 L.Reserve.20
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.20
Measurement Points
L.Reserve.20
Formula
None
Unit
None
Related Features
None
2.2.38.21 L.Reserve.21
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.21
Measurement Points
L.Reserve.21
Formula
None
Unit
None
Related Features
None
2.2.38.22 L.Reserve.22
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.22
Measurement Points
L.Reserve.22
Formula
None
Unit
None
Related Features
None
2.2.38.23 L.Reserve.23
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.23
Measurement Points
L.Reserve.23
Formula
None
Unit
None
Related Features
None
2.2.38.24 L.Reserve.24
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.24
Measurement Points
L.Reserve.24
Formula
None
Unit
None
Related Features
None
2.2.38.25 L.Reserve.25
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.25
Measurement Points
L.Reserve.25
Formula
None
Unit
None
Related Features
None
2.2.38.26 L.Reserve.26
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.26
Measurement Points
L.Reserve.26
Formula
None
Unit
None
Related Features
None
2.2.38.27 L.Reserve.27
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.27
Measurement Points
L.Reserve.27
Formula
None
Unit
None
Related Features
None
2.2.38.28 L.Reserve.28
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.28
Measurement Points
L.Reserve.28
Formula
None
Unit
None
Related Features
None
2.2.38.29 L.Reserve.29
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.29
Measurement Points
L.Reserve.29
Formula
None
Unit
None
Related Features
None
2.2.38.30 L.Reserve.30
Counters
Counter ID Counter Name Counter Network Element
Description
Description
L.Reserve.30
Measurement Points
L.Reserve.30
Formula
None
Unit
None
Related Features
None
Overview
The CellComb.Cell function subset measures the used resources and number of scheduled
resources in a combined cell, indicating the operating status of the combined cell.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of downlink joint-scheduling UEs in a combination cell.
Measurement Points
The number of downlink joint-scheduling UEs in a combination cell is sampled per second. At
the end of a measurement period, the average of these sampling results is used as the value of
the counter.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the average number of work physical cells of downlink joint-scheduling
UEs in a combination cell. The number of work physical cells of downlink joint-scheduling UEs
is calculated by adding the measurement result to the number of cells in the work cell set of the
UE after the UE accesses the network. Each time a UE decides the downlink attribute of a
combination cell, this counter increases or decreases correspondingly if the UE work physical
cell set changes. After the UE exits the network, the number of cells in the work cell set for the
UE is deducted from this counter.
Measurement Points
The average number of work physical cells per downlink joint-scheduling UE in a combination
cell is sampled per second. At the end of a measurement period, the average of these sampling
results is used as the value of the L.CellComb.DLJSch.PhyCell.Avg counter
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of times the downlink attribute of a UE changes from
independent scheduling to joint scheduling in a combination cell.
Measurement Points
The L.CellComb.User.DLI2J counter is incremented by 1 each time the downlink attribute of a
UE changes from independent scheduling to joint scheduling in a combination cell.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of times the downlink attribute of a UE changes from joint
scheduling to independent scheduling in a combination cell.
Measurement Points
The L.CellComb.User.DLJ2I counter is incremented by 1 each time the downlink attribute of a
UE changes from joint scheduling to independent scheduling in a combination cell
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of times the downlink target physical cell of a UE in a
combination cell changes.
Measurement Points
The L.CellComb.DLTPhyCell.Chg counter is incremented by 1 each time the downlink target
physical cell of a UE in a combination cell changes.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of uplink joint-scheduling UEs in a combination cell.
Measurement Points
The number of uplink joint-scheduling UEs in a combination cell is sampled per second. At the
end of a measurement period, the average of these sampling results is used as the value of the
counter.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the average number of work physical cells of uplink joint-scheduling
UEs in a combination cell. The number of work physical cells of uplink joint-scheduling UEs
is calculated by adding the measurement result to the number of cells in the work cell set of the
UE after the UE accesses the network. Each time a UE decides the uplink attribute of a
combination cell, this counter increases or decreases correspondingly if the UE work physical
cell set changes. After the UE exits the network, the number of cells in the work cell set for the
UE is deducted from this counter.
Measurement Points
The average number of work physical cells per uplink joint-scheduling UE in a combination cell
is sampled per second. At the end of a measurement period, the average of these sampling results
is used as the value of the L.CellComb.ULJSch.PhyCell.Avg counter.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of times the uplink attribute of a UE changes from independent
scheduling to joint scheduling in a combination cell.
Measurement Points
The L.CellComb.User.ULI2J counter is incremented by 1 each time the uplink attribute of a UE
changes from independent scheduling to joint scheduling in a combination cell.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of times the uplink attribute of a UE changes from joint
scheduling to independent scheduling in a combination cell.
Measurement Points
The L.CellComb.User.ULJ2I counter is incremented by 1 each time the uplink attribute of a UE
changes from joint scheduling to independent scheduling in a combination cell.
Formula
None
Unit
None
Related Features
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of times the uplink target physical cell of a UE in a
combination cell changes.
Measurement Points
The L.CellComb.ULTPhyCell.Chg counter is incremented by 1 each time the uplink target
physical cell of a UE in a combination cell changes.
Formula
None
Unit
None
Related Features
None
Overview
The ChMeas.MeasRpt.Cell function subset measures the number of measurement controls in a
cell.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of measurement control messages triggered by poor coverage
during inter-RAT measurement in a cell.
Measurement Points
As shown at point A in Figure 2-385, the eNodeB sends the UE a measurement control message
RRC Connection Reconfiguration due to poor coverage, and this message contains the
information element "MeasConfig". The L.MeasCtrl.WCDMA.Add counter is incremented by
1 each time the information element list measIdToAddModList contains any information
element measID dedicated to WCDMA network. The L.MeasCtrl.GERAN.Add counter is
incremented by 1 each time the information element list measIdToAddModList contains any
information element measID dedicated to GERAN.
Figure 2-385
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
UE context contains user-specific context information throughout the network. The success rate
of the UE context setup represents the capability of a cell to set up UE contexts. The
UECNTX.Est.Cell function subset measures the number of UE context setups in a cell. The
counter is incremented by 1 each time the UE context is set up. The measurement points in a
UE context setup process is shown in Figure 2-386.
Figure 2-386
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of UE context setup attempts in a cell.
Measurement Points
As shown at point A in Figure 2-387, the counter is incremented by 1 each time the eNodeB
receives the INITIAL CONTEXT SETUP REQUEST message from the MME. Even if the
message contains multiple E-RABs, the counter is incremented only once.
Figure 2-387
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
This counter measures the number of successful UE context setups in a cell.
Measurement Points
As shown at point B in Figure 2-388, the counter is incremented by 1 each time the eNodeB
sends the INITIAL CONTEXT SETUP RESPONSE message to the MME. Even if the message
contains multiple E-RABs, the counter is incremented only once.
Figure 2-388
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
UE context contains user-specific context information throughout the network. The success rate
of the UE context setup represents the capability of a cell to set UE contexts. The
UECNTX.EstFail.Cell function subset measures the number of UE context setup failures due
to different causes. The counter is incremented by 1 each time the UE context setup fails. The
measurement points in a UE context setup failure process is shown in Figure 2-389.
Figure 2-389
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
Counter Sub Counter
L.UECNTX.FailEst.RNL L.UECNTX.FailEst.SecurModeFail
L.UECNTX.FailEst.NoRadioRes
L.UECNTX.FailEst.UeNoReply
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the number of UE context setup failures due to different causes in a cell.
The measurement of the counters reflect different causes of UE context setup failures.
Measurement Points
The corresponding counter is incremented if the context setup fails due to a cause such as a fault
at the radio network layer, radio resource allocation failure, security mode configuration failure,
or no response from the UE. The counters are measured as follows:
As shown at point A in Figure 2-390, after receiving the INITIAL CONTEXT SETUP
REQUEST message from the MME, the eNodeB starts initial context setup. If the UE context
setup fails, the eNodeB sends the INITIAL CONTEXT SETUP FAILURE message to the MME
and a corresponding counter is incremented based on the failure cause. The L.E-
UECNTX.FailEst.RNL counter is incremented by 1 each time the UE context setup failure is
caused by faults at the radio network layer. For details, see 3GPP TS36.413. The
L.UECNTX.FailEst.NoRadioRes counter is incremented if the UE context setup failure is
caused by insufficient radio resources. The measurement of the L.UECNTX.FailEst.RNL
Figure 2-390
Figure 2-391
Figure 2-392
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Figure 2-393
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of X2-based incoming handover attempts in a cell.
Measurement Points
As shown at point A in Figure 2-394, the L.HHO.X2.PrepAttIn counter is incremented by 1 in
the target cell each time the target eNodeB receives a HANDOVER REQUEST message from
the source eNodeB over the X2-interface.
Figure 2-394
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of X2-based incoming handover executions in a cell.
Measurement Points
As shown at point B in Figure 2-395, the L.HHO.X2.ExecAttIn counter is incremented by 1 in
the target cell each time the target eNodeB sends a HANDOVER REQUEST ACKNOWLEDGE
message to the source eNodeB over the X2-interface.
Figure 2-395
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counter measures the number of successful X2-based incoming handovers in a cell.
Measurement Points
As shown at point C in Figure 2-396, during an X2-based handover the L.HHO.X2.ExecSuccIn
counter is incremented by 1 each time the target eNodeB receives a PATH SWITCH REQUEST
ACKNOWLEDGE message from the MME and sends a UE CONTEXT RELEASE message
to the source eNodeB over the X2-interface.
As shown at point E in Figure 2-397, after an RRC connection is reestablished to the target
eNodeB for the UE during an X2-based handover, the L.HHO.X2.ExecSuccIn counter is
incremented by 1 each time the target eNodeB receives a PATH SWITCH REQUEST
ACKNOWLEDGE message from the MME and sends a UE CONTEXT RELEASE message
to the source eNodeB over the X2-interface.
Figure 2-396
Figure 2-397
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
Overview
The Traffic.Thruput.PDF.Cell function subset measures the Throughput of services per QCI
within a measurement period. According to the Throughput distribution, a probability density
function (PDF) is generated and helps the network-level performance evaluation.
Counters
Counter ID Counter Name Counter Original Release
Description
Counter Relationship
None
Counters
Counter ID Counter Name Counter Network Element
Description
Description
The counters measure the downlink Throughput of services per QCI and indicate the distribution
of the downlink Throughput in a cell.
Measurement Points
The downlink traffic volume and data transmission duration of services per QCI are sampled
per second except the last TTI before the DRB buffer is empty. If there is data transmission for
a service within a measurement period, the corresponding counter is incremented by 1 at the end
of a measurement period based on the downlink throughput of the service.
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name