3900 Series Base Station ENodeBFunction Performance Counter Reference (V100R010C10 - 11) (PDF) - en

3900 Series Base Station
V100R010C10
eNodeBFunction Performance
Counter Reference
Issue 11
Date 2016-12-05
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 11 (2016-12-05) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
eNodeBFunction Performance Counter Reference Contents
Contents
1 Measurement of Cell Performance (Cell)................................................................................. 1

1.1 RRC Setup Measurement (RRC.Setup.Cell).................................................................................................................. 6
1.1.1 Number of RRC Connection Setup Requests in a Cell............................................................................................. 12
1.1.2 Number of Successful RRC Connection Setups in a Cell......................................................................................... 19
1.1.3 Number of RRC Connection Setup Attempts in a Cell............................................................................................. 24
1.1.4 Number of Times a UE switch from the Uplink-Synchronized State to the Uplink Out-of-Synchronization State. 25
1.1.5 Number of Times a UE switch from the Uplink Out-of-Synchronization state to the Uplink-Synchronized State..26
1.1.6 RRC Connection Setup Duration in a Cell................................................................................................................ 27
1.1.7 Number of Successfully Recovered RRC Connections When UEs switch from the Uplink Out-of-Synchronization
State to Uplink-Synchronized State....................................................................................................................................29
1.1.8 Maximum Number of RRC Connection Setup Requests in a Cell............................................................................31
1.2 RRC Setup Failure Measurement (RRC.SetupFail.Cell)............................................................................................. 32
1.2.1 Number of RRC Connection Setup Failures for Different Causes in a Cell............................................................. 35
1.3 RRC Reestablishment Measurement (RRC.ReEst.Cell).............................................................................................. 41
1.3.1 Number of RRC Connection Reestablishment Requests in a Cell............................................................................ 44
1.3.2 Number of Successful RRC Connection Reestablishments in a Cell........................................................................47
1.4 RRC Reestablishment Failure Measurement (RRC.ReEstFail.Cell)............................................................................49
1.4.1 Number of RRC Connection Reestablishment Failures for Different Causes in a Cell............................................ 52
1.5 E-RAB Setup Measurement (E-RAB.Est.Cell)............................................................................................................ 57
1.5.1 Number of E-RAB Setup Attempts in a Cell............................................................................................................ 71
1.5.2 Number of Successful E-RAB Setups in a Cell........................................................................................................ 77
1.5.3 Number of Initial E-RAB Setup Attempts in a Cell.................................................................................................. 82
1.5.4 Number of Successful Initial E-RAB Setups in a Cell.............................................................................................. 87
1.5.5 Number of E-RAB Setup Attempts for Incoming Handovers in a Cell.................................................................... 92
1.5.6 Number of Successful E-RAB Setups for Incoming Handovers in a Cell.............................................................. 100
1.5.7 Number of UE-related Signaling Connection Setups over the S1 Interface............................................................111
1.5.8 E-RAB Setup Duration in a Cell..............................................................................................................................113
1.5.9 Number of E-RAB Recovery Attempts When UEs switch from the Uplink Out-of-Synchronization State to
Uplink-Synchronized State............................................................................................................................................... 116
1.5.10 Number of Successfully Recovered E-RABs When UEs switch from the Uplink Out-of-Synchronization State to
Uplink-Synchronized State............................................................................................................................................... 118
1.6 E-RAB Release Measurement (E-RAB.Rel.Cell)...................................................................................................... 119
1.6.1 Number of Abnormal E-RAB Releases in a Cell.................................................................................................... 155
1.6.2 Number of Normal E-RAB Releases in a Cell........................................................................................................ 163
Issue 11 (2016-12-05) Huawei Proprietary and Confidential ii

1.6.3 Number of Normal E-RAB Releases for Outgoing Handovers in a Cell................................................................ 169
1.6.4 Number of Abnormal E-RAB Releases for Outgoing Handovers in a Cell............................................................ 181
1.6.5 Total Number of Abnormal E-RAB Releases in a Cell...........................................................................................192
1.6.6 Number of Abnormal E-RAB Releases for Different Causes in a Cell.................................................................. 195
1.6.7 Number of Released E-RABs of UEs in the Uplink Out-of-Synchronization State............................................... 212
1.6.8 Total Number of E-RABs of UEs When the UEs switch from the Uplink-synchronized State to the Uplink Out-of-
Synchronization State....................................................................................................................................................... 214
1.6.9 Number of E-RAB Releases Initiated by the eNodeB in a Cell.............................................................................. 215
1.6.10 Number of E-RAB Releases Initiated by the MME in a Cell............................................................................... 220
1.6.11 Number of Remaining E-RABs in a Cell.............................................................................................................. 224
1.6.12 Number of E-RAB Releases Initiated by the eNodeB Because of the S1 RESET in a Cell................................. 227
1.6.13 Number of E-RAB Releases Initiated by the MME Because of the S1 RESET in a Cell.....................................232
1.6.14 Number of MME-triggered Abnormal E-RAB Releases...................................................................................... 237
1.6.15 Number of Abnormal E-RAB Releases for Other Reasons in a Cell.................................................................... 241
1.6.16 Number of MME-initiated Abnormal Releases of E-RABs During Handover Executions..................................247
1.6.17 Number of Normal E-RAB Releases Caused by Inactivity Timer Expiration...................................................... 253
1.7 E-RAB Setup Failure Measurement (E-RAB.EstFail.Cell)....................................................................................... 254
1.7.1 Number of E-RAB Setup Failures for Different Causes in a Cell...........................................................................265
1.7.2 Number of E-RAB Setup Failures for Other Causes in a Cell................................................................................ 291
1.8 E-RAB Modification Measurement (E-RAB.Modify.Cell)........................................................................................296
1.8.1 Number of E-RAB Modification Attempts in a Cell...............................................................................................300
1.8.2 Number of Successful E-RAB Modifications in a Cell...........................................................................................305
1.8.3 Number of E-RAB Modification Failures for Different Causes in a Cell............................................................... 309
1.9 Cell Algorithm Measurement (Algo.Cell).................................................................................................................. 311
1.9.1 Number of Times Uplink or Downlink Congestion Occurs in a Cell..................................................................... 325
1.9.2 Duration of Uplink or Downlink Congestion in a Cell........................................................................................... 326
1.9.3 Number of Service Releases due to Congestion in a Cell....................................................................................... 328
1.9.4 Duration of Cell Unavailability............................................................................................................................... 329
1.9.5 Duration of Cell Availability................................................................................................................................... 331
1.9.6 Number of Signaling Messages over the Uu Interface............................................................................................332
1.9.7 Number of DRX Reconfiguration Messages...........................................................................................................333
1.9.8 Uplink or Downlink Voice Quality in a Cell........................................................................................................... 335
1.9.9 Number of Times that E-UTRAN is Configured as the Highest Frequency Priority in an IMMCI IE...................338
1.9.10 Number of Times that the WCDMA Network is Configured as the Highest Frequency Priority in an IMMCI IE
.......................................................................................................................................................................................... 340
1.9.11 Number of Times that GERAN is Configured as the Highest Frequency Priority in an IMMCI IE.....................342
1.9.12 Number of Successful Preemptions Triggered due to User Limitation.................................................................343
1.9.13 Number of Semi-Persistent Scheduling Times in a cell........................................................................................ 344
1.9.14 Number of Failed Semi-Persistent Scheduling Transmissions in a Cell............................................................... 345
1.9.15 Number of Times a UE in Connected Mode Enters DRX in RRC_CONECTED Mode......................................347
1.9.16 Number of Times a UE in Connected Mode Exits DRX in RRC_CONECTED Mode........................................348
1.9.17 DRX Duration........................................................................................................................................................350
1.9.18 Number of Messages Sent for Instructing UEs to Enter or Exit TTI bundling Mode...........................................352
Issue 11 (2016-12-05) Huawei Proprietary and Confidential iii

1.9.19 Times of ETWS-induced SIB1 changes................................................................................................................ 354

1.9.20 Number of processed ETWS-induced WRITE-REPLACE WARNING REQUEST messages in a cell..............355
1.9.21 Number of Packets of Non-GBR Bearers Discarded by AQM............................................................................. 357
1.9.22 Number of Times That Dynamic AC Barring Is Triggered...................................................................................358
1.9.23 Number of Times That Dynamic AC Barring Is Cancelled.................................................................................. 359
1.9.24 Number of Times That Parameters Related to Dynamic AC Barring Are Adjusted.............................................360
1.9.25 Control Duration of Dynamic AC Barring............................................................................................................ 361
1.9.26 Number of Times that the TDSCDMA Network is Configured as the Highest Frequency Priority in an IMMCI IE
.......................................................................................................................................................................................... 362
1.9.27 Number of S1 Signaling Messages Received or Sent by a Cell............................................................................ 364
1.9.28 Number of X2 Signaling Messages Received or Sent by a Cell........................................................................... 365
1.9.29 Distribution of Out-of-Synchronization Durations for UEs in a Cell................................................................... 366
1.9.30 Number of Semi-persistent Scheduling Times in a Cell........................................................................................370
1.9.31 Number of Semi-persistent Scheduling Failures in a Cell.................................................................................... 371
1.9.32 Number of Times the eNodeB Delivers the Load-Triggered Inter-Frequency Measurement Configuration to a UE
.......................................................................................................................................................................................... 372
1.9.33 Number of Times the Load-Triggered Inter-Frequency Measurement is Successful............................................374
1.9.34 Duration in Which a Cell with Inter-Frequency Load Balancing Enabled Is in the High-Load State.................. 376
1.9.35 Number of Times a Cell with Inter-Frequency Load Balancing Enabled Enters from the Low-Load State to the
High-Load State................................................................................................................................................................377
1.9.36 Number of Uplink and Downlink TTIs................................................................................................................. 378
1.9.37 Number of times that a cell is unavailable.............................................................................................................379
1.9.38 Uplink and Downlink Voice Quality..................................................................................................................... 380
1.9.39 Number of Times that a UE Is Detected Based on the SRLTE Optimization Feature to Be Switched Out of the
State of Performing LTE Services.................................................................................................................................... 384
1.9.40 Number of Normal Voice Call Releases in the Cell (Poor Uplink Voice Quality)................................................385
1.9.41 Number of Times that a UE Experiences Uplink Voice Mute in the Cell............................................................. 387
1.9.42 Number of Times that an eNodeB Attempts to Measure the Time Difference Among eNodeBs by Using UEs
Performing Inter-eNodeB Handovers...............................................................................................................................388
1.9.43 Number of Times that an eNodeB Attempts to Measure the Time Difference Among eNodeBs by Using Inter-
eNodeB CEUs...................................................................................................................................................................390
1.9.44 Number of Times that an eNodeB Successfully Measures the Time Difference Among eNodeBs by Using UEs
that Are Performing Inter-eNodeB Handovers.................................................................................................................392
1.9.45 Number of Times that an eNodeB Successfully Measures the Time Difference Among eNodeBs by Using Inter-
eNodeB CEUs...................................................................................................................................................................394
1.9.46 Number of times when a cell receives a power configuration message from the centralized scheduler but the
validation period expires.................................................................................................................................................. 396
1.9.47 Number of cell received configuration message from centre controller............................................................... 397
1.9.48 Number of Downlink Subframes Without Power on the Power Spectrun of a Cell............................................. 398
1.9.49 Number of Times Dynamic SSAC Is Triggered....................................................................................................399
1.9.50 Number of Times Parameters Related to Dynamic SSAC are Adjusted ..............................................................400
1.9.51 Number of Times Dynamic SSAC Is Canceled.....................................................................................................401
1.9.52 Duration of Dynamic SSAC.................................................................................................................................. 402
1.9.53 Number of Times Preemptions Are Triggered by the User Number Specification...............................................403
1.9.54 Number of Times the Licensed Number of UEs Is Limited..................................................................................405
Issue 11 (2016-12-05) Huawei Proprietary and Confidential iv

1.9.55 Number of Successful Preemptions Triggered by the Limitation of the Licensed Number of Ues...................... 406
1.9.56 Number of Times IRC, MRC, or Smart IRC Is Used on the PUSCH................................................................... 408
1.9.57 Number of Times IRC or MRC Is Used on the PUCCH.......................................................................................410
1.9.58 Number of Times IRC or MRC Is Used on the PRACH.......................................................................................411
1.9.59 Number of SPID-based Target PLMN Selection Attempts................................................................................... 413
1.9.60 Number of times the eCoordinator triggers interference coordination in high-speed railway scenarios.............. 417
1.9.61 Number of times the eCoordinator stops interference coordination in high-speed railway scenarios.................. 418
1.10 DRB Measurement (Traffic.DRB.Cell)....................................................................................................................419
1.10.1 Number of DRBs in a Cell.................................................................................................................................... 422
1.10.2 Max number of DRBs in a Cell............................................................................................................................. 425
1.11 Throughput and Data Volume Measurement (Traffic.Thruput.Cell)........................................................................ 428
1.11.1 Maximum Uplink Traffic Volume for PDCP PDUs in a Cell................................................................................449
1.11.2 Maximum Downlink Traffic Volume for PDCP SDUs in a Cell...........................................................................453
1.11.3 Total Bits of Transmitted Signaling SDUs on SRBs at the PDCP Layer in a Cell................................................457
1.11.4 Total Bits of Received Signaling SDUs on SRBs at the PDCP Layer in a Cell.................................................... 458
1.11.5 Total Duration of Uplink or Downlink Data Transmission in a Cell.....................................................................459
1.11.6 Duration of Data Transmission for Services with a Specific QCI in a Cell.......................................................... 461
1.11.7 Total Duration of UE Data Transmission in a Cell................................................................................................465
1.11.8 Uplink Traffic Volume for PDCP PDUs in a Cell................................................................................................. 466
1.11.9 Receive Duration of Uplink PDCP PDUs in a Cell...............................................................................................470
1.11.10 Downlink Traffic Volume for PDCP SDUs in a Cell.......................................................................................... 474
1.11.11 Transmit Duration of Downlink PDCP SDUs in a Cell.......................................................................................478
1.11.12 Total Bits of Uplink or Downlink User Data Received from or Sent to ICIC CEUs at the PDCP Layer from
CEUs in a Cell.................................................................................................................................................................. 482
1.11.13 Total Duration in Which Uplink User Data Is Received from or Downlink User Data Is Sent to ICIC CEUs at
the PDCP Layer in a Cell................................................................................................................................................. 484
1.11.14 Total Traffic Volume of Downlink PDCP SDUs Transmitted to Activated CA UEs in a Cell........................... 486
1.11.15 Total Transmit Duration of Downlink PDCP SDUs Transmitted to Activated CA UEs in a Cell...................... 487
1.11.16 Total Duration of Uplink or Downlink Data Transmission in a Cell (with the Precision of 1 ms)..................... 488
1.11.17 Downlink traffic volume sent in the last TTI before the buffer is empty............................................................ 489
1.11.18 Data transmit duration except the last TTI before the downlink buffer is empty................................................494
1.11.19 Traffic Volume of Uplink PDCP SDUs Sent in the Last TTI Before the UE Buffer is Empty........................... 499
1.11.20 Uplink Data Transmit Duration Except the Last TTI Before the UE Buffer is Empty....................................... 500
1.11.21 Uplink PDCP throughput in an SFN cell.............................................................................................................501
1.11.22 Downlink PDCP throughput in an SFN cell........................................................................................................502
1.11.23 Uplink Traffic Volume of PDCP PDUs Scheduled for Small Packets................................................................ 503
1.11.24 Uplink Data Transmission Duration Except that for Small Packets....................................................................504
1.11.25 Average Rate of Transmitting Downlink Signaling Data at the PDCP Layer in a Cell...................................... 505
1.11.26 Average Rate of Receiving Uplink Signaling Data at the PDCP Layer in a Cell................................................506
1.11.27 Uplink Data Transmission Duration Except that for Specific Small Packets Transmitted in the Last TTI........ 507
1.11.28 Uplink Traffic Volume at the PDCP Layer of Specific Small Packets Transmitted in the Last TTI...................508
1.11.29 Downlink PDCP-layer Traffic Volume of CA UEs that Are in the 3CC CA State and Treat the Local as Their
PCell with Two SCell Activated.......................................................................................................................................509
Issue 11 (2016-12-05) Huawei Proprietary and Confidential v

1.11.30 Uplink PDCP-layer Traffic Volume of CA UEs that Treat the Local as Their PCell with All SCells Activated510
1.11.31 Total Downlink Traffic Volume of Downlink Relaxed-Backhaul-based Inter-eNodeB CA UEs in a Cell......... 511
1.11.32 Total Duration for Sending Downlink Data to Active Downlink Relaxed-Backhaul-based Inter-eNodeB CA UEs
at the PDCP Layer in a Cell..............................................................................................................................................512
1.11.33 Total Duration of UE Data Transmission with the precision of 100 milliseconds in a Cell................................514
1.11.34 Total duration of transmission time for services with all the QCI with the precision of 100 milliseconds in a cell
.......................................................................................................................................................................................... 515
1.11.35 Uplink PDCP-layer Traffic Volume of CCUs in a Cell Using the UMTS and LTE Shared Spectrum............... 520
1.11.36 Transmission Duration of Uplink PDCP-layer Data for CCUs in a Cell Using the UMTS and LTE Shared
Spectrum........................................................................................................................................................................... 521
1.11.37 Duration of Downlink PDCP-Layer Data Transmission to CA UEs That Have All SCells Activated for
Downlink FDD+TDD CA in a Cell..................................................................................................................................522
1.11.38 Total Traffic Volume of Downlink PDCP SDUs to CA UEs That Have All SCells Activated for Downlink FDD
+TDD CA......................................................................................................................................................................... 524
Downlink 3CC CA in a Cell.............................................................................................................................................526
1.11.40 Duration of downlink PDCP-Layer Data Transmission to CA UEs That Have All SCells Activated for
Downlink FDD+TDD 3CC CA in a Cell......................................................................................................................... 528
+TDD 3CC CA in a Cell.................................................................................................................................................. 530
downlink 4CC CA in a Cell..............................................................................................................................................532
1.11.43 Total Traffic Volume of Downlink PDCP SDUs to CA UEs That Have All SCells Activated for Downlink 4CC
CA in a Cell...................................................................................................................................................................... 534
1.11.44 Duration of downlink PDCP-Layer Data Transmission to CA UEs That Have All SCells Activated for
Downlink FDD+TDD 4CC CA in a Cell......................................................................................................................... 536
+TDD 4CC CA in a Cell.................................................................................................................................................. 538
1.12 Throughput and Data Volume Measurement 1 (Traffic.Thruput.Cell.1)..................................................................540
1.12.1 Uplink Traffic Volume at the PDCP layer............................................................................................................. 545
1.12.2 Downlink Traffic Volume at the PDCP layer........................................................................................................ 549
1.12.3 Downlink Traffic Volume at the Physical Layer................................................................................................... 553
1.12.4 Uplink Traffic Volume at the Physical Layer........................................................................................................ 554
1.12.5 Maximum Downlink Traffic Volume at the Physical Layer..................................................................................555
1.12.6 Maximum Uplink Traffic Volume at the Physical Layer.......................................................................................556
1.12.7 Total Duration of Data Storage in the Uplink and Downlink Buffer.....................................................................557
1.12.8 Total PDCP-Layer Traffic Volume of To-Be-Transmitted Downlink Data in a Cell............................................ 558
1.12.9 Total PDCP-Layer Traffic Volume of Discarded To-Be-Transmitted Downlink Data in a Cell........................... 559
1.12.10 Total RLC-Layer Traffic Volume of Downlink Data in a Cell............................................................................ 560
1.12.11 Total RLC-Layer Traffic Volume of Uplink Data in a Cell................................................................................. 561
1.12.12 Total PDCP-Layer Traffic Volume of Discarded Uplink Data............................................................................ 562
1.12.13 Total PDCP-Layer Traffic Volume of Uplink Data in a Cell...............................................................................563
1.12.14 Uplink Traffic Volume Received for CEUs in a Cell.......................................................................................... 564
1.12.15 Downlink Traffic Volume Sent for CEUs in a Cell............................................................................................. 565
1.12.16 PDCP-layer Traffic Volume Scheduled for Uplink Small Packets for CEUs in a Cell.......................................566
Issue 11 (2016-12-05) Huawei Proprietary and Confidential vi

1.12.17 Transmission Duration of Uplink Data Except Small Packets for CEUs in a cell.............................................. 567
1.12.18 Downlink PDCP-layer Traffic Volume Sent in the Last TTI for CEUs Before the Buffer is Empty in a Cell... 568
1.12.19 Data Transmission Duration for CEUs Except the Last TTI Before the Downlink Buffer Is Empty................. 569
1.13 Paging Measurement (Paging.Cell).......................................................................................................................... 570
1.13.1 Number of Received Paging Messages over the S1 Interface in a Cell................................................................ 572
1.13.2 Number of UEs Contained in Paging Messages Transmitted over the Uu Interface in a Cell..............................574
1.13.3 Number of Successful Paging Responses from the UE in a Cell.......................................................................... 575
1.13.4 Number of Discarded Paging Messages from the MME to UEs in a Cell............................................................ 577
1.13.5 Number of Paging Messages Transmitted Due to System Information Changes..................................................578
1.13.6 Number of Paging Messages Discarded due to Paging Channel Congestion....................................................... 579
1.13.7 Number of Paging Messages Sent Over the Uu Interface in a Cell.......................................................................580
1.14 Security Mode Measurement (SecurMode.Cell)...................................................................................................... 581
1.14.1 Number of Security Mode Setups in a Cell........................................................................................................... 583
1.15 RA Measurement (RA.Cell)..................................................................................................................................... 586
1.15.1 Number of Times the Contention Preamble Is Received...................................................................................... 592
1.15.2 Number of Times the Random Access Response Message Is Sent After the Contention Preamble Is Received.594
1.15.3 Number of Times the Contention Resolution Message Is Sent After the Contention Preamble Is Received....... 596
1.15.4 Number of Times the Non-Contention-Based Preamble Is Received................................................................... 599
1.15.5 Number of Times the Random Access Response Message Is Sent After the Non-Contention-Based Preamble Is
Received........................................................................................................................................................................... 601
1.15.6 Number of Times the UE Msg3 Response Message Is Received in the Handover-Triggered Non-Contention-
Based RA Procedure.........................................................................................................................................................603
1.15.7 Number of Random Access Procedures................................................................................................................ 605
1.15.8 Number of Times the Non-Contention-based Preamble is Requested.................................................................. 609
1.15.9 Number of Times the Non-Contention-based Preamble is Assigned.................................................................... 610
1.15.10 Number of Times the TA with a Specific Value Range in a UE-Initiated Random Access Procedure in a Cell 611
1.15.11 Number of Times that the Contention-based Preamble in Group A is Discarded based on the TA....................616
1.15.12 Number of Times that the Contention-based Preamble in Group B is Discarded Based on the TA................... 618
1.16 Channel Quality Measurement (ChMeas.Pwr.Cell)................................................................................................. 619
1.16.1 Downlink Transmit Power.....................................................................................................................................639
1.16.2 Interference and Noise Received by Each PRB in a Cell......................................................................................640
1.16.3 Receive Power of interference and noise detected of each PRB in the UL UpPTS..............................................642
1.16.4 Receive Power of the first Symbol in First UL Subframe.....................................................................................643
1.16.5 Receive Power of the seventh (or fifth) Symbol in First UL Subframe................................................................ 644
1.16.6 Receive Power of the first Symbol in Last UL Subframe..................................................................................... 645
1.16.7 Receive Power of the twelfth (or tenth) Symbol in the Last UL Subframe.......................................................... 646
1.16.8 Distribution of RSSIs on the PUCCH................................................................................................................... 647
1.16.9 Distribution of RSSIs on the PUSCH....................................................................................................................657
1.16.10 Distribution of INs on the PUSCH...................................................................................................................... 667
1.16.11 Distribution of INs on the PUCCH......................................................................................................................674
1.16.12 Distribution of INs on the PRACH......................................................................................................................681
1.16.13 Distribution of RSRPs on the PUSCH................................................................................................................ 689
1.16.14 Distribution of RSRPs on the PUCCH................................................................................................................ 699
Issue 11 (2016-12-05) Huawei Proprietary and Confidential vii

1.17 Channel Quality Measurement1 (ChMeas.Pwr1.Cell)............................................................................................. 709

1.17.1 Average Interference and Noise Received by Each PRB in a Cell........................................................................729
1.17.2 Maximum Interference and Noise Received by Each PRB in a Cell.................................................................... 762
1.18 CQI Measurement (ChMeas.CQI.Cell).................................................................................................................... 795
1.18.1 Number of Wideband CQI Reports in a Cell.........................................................................................................814
1.18.2 Number of Periodic Wideband CQI Reports in Single-Codeword Transmission in a Cell...................................820
1.18.3 Number of Aperiodic Wideband CQI Reports in Single-Codeword Transmission in a Cell................................ 828
1.18.4 Number of Periodic Wideband CQI Reports for Codeword 0 in Dual-Codeword Transmission in a Cell...........836
1.18.5 Number of Aperiodic Wideband CQI Reports for Codeword 0 in Dual-Codeword Transmission in a Cell........ 844
1.18.6 Number of Periodic Wideband CQI Reports for Codeword 1 in Dual-Codeword Transmission in a Cell...........852
1.18.7 Number of Aperiodic Wideband CQI Reports for Codeword 1 in Dual-Codeword Transmission in a Cell........ 860
1.18.8 Number of Times a UE Reports a Rank Value in a Cell........................................................................................867
1.18.9 wideband CQIs reported by CEUs in a Cell..........................................................................................................869
1.19 MCS Measurement (ChMeas.MCS.Cell)................................................................................................................. 871
1.19.1 Number of Times an MCS Index Is Scheduled on the PUSCH............................................................................ 898
1.19.2 Number of Times a Specific MCS Index Is Scheduled on the PDSCH................................................................ 913
1.19.3 Number of PRBs on the PUSCH Using a Specified MCS for Scheduling in a Cell.............................................929
1.19.4 Number of PRBs on the PDSCH Using a Specific MCS index for Scheduling in a Cell..................................... 939
1.20 PRB Measurement (ChMeas.PRB.Cell).................................................................................................................1003
1.20.1 Number of Used Uplink PRBs............................................................................................................................ 1014
1.20.2 Number of Used Downlink PRBs....................................................................................................................... 1019
1.20.3 Number of Used PUCCH PRBs.......................................................................................................................... 1022
1.20.4 Number of OFDM Symbols Occupied by the PDCCH.......................................................................................1023
1.20.5 Number of PDCCH CCEs used in a cell............................................................................................................. 1025
1.20.6 Average Number of PRBs Occupied by CA UEs in a Cell................................................................................. 1032
1.20.7 Average Number of Available PRBs in a Cell.....................................................................................................1034
1.20.8 Average Number of PRBs Used by ICIC CEUs in a Cell................................................................................... 1035
1.20.9 Average Number of PRBs Allocated for Frequency Selective Scheduling.........................................................1037
1.20.10 Average Number of PRBs Allocated for Uplink Pre-scheduling...................................................................... 1038
1.20.11 Number of Times of DTX for PDCCH Resource Allocation with a Specific Aggregation Level in a Cell..... 1040
1.20.12 Number of Times of Successful PDCCH Resource Allocations with a Specific Aggregation Level...............1042
1.20.13 Average number of PRBs used for downlink CoMP scheduling in a cell.........................................................1044
1.20.14 Average Number of Available PUSCH PRBs in a Cell.....................................................................................1045
1.20.15 Number of Times of DMRS TA Scheduling in a cell........................................................................................1046
1.20.16 Number of CCE Allocation Failures in a Cell...................................................................................................1047
1.20.17 PUSCH PRB Usage Distribution...................................................................................................................... 1048
1.20.18 Average Number of PRBs Allocated for Uplink TA Measurement.................................................................. 1054
1.20.19 PDSCH PRB Usage Distribution...................................................................................................................... 1055
1.20.20 Number of PRBs Occupied by Inter-eNodeB CA UEs that Treat the Local Cell as Their PCell or SCell....... 1060
1.20.21 Average Number of Uplink PRBs Occupied by CA UEs that Are in the Uplink CA State (Each with at Least
One Uplink SCC Configured) and Treat the Local Cell as Their PCell or SCell...........................................................1061
1.20.22 Number of PRBs of the Downlink Edge Band in Adaptive ICIC..................................................................... 1063
1.20.23 Average Number of PRBs Used for Inter-eNodeB DL CoMP Scheduling in a Cell........................................ 1064
Issue 11 (2016-12-05) Huawei Proprietary and Confidential viii

1.20.24 Number of Used Uplink PRBs on the PUSCH on the UMTS and LTE Shared Spectrum in a Cell.................1065
1.20.25 Average Number of Standardized PRBs Used for Downlink Services............................................................. 1066
1.21 MAC Measurement (Traffic.MAC.Cell)................................................................................................................ 1067
1.21.1 Total Number of Bits of TBs Transmitted on the BCH....................................................................................... 1082
1.21.2 Total Number of Bits of TBs Transmitted on the PCH....................................................................................... 1083
1.21.3 Number of TBs Initially Transmitted on the Downlink SCH..............................................................................1084
1.21.4 Number of Bits of TBs Initially Transmitted on the Downlink SCH..................................................................1087
1.21.5 Number of TBs Retransmitted on the Downlink SCH........................................................................................ 1089
1.21.6 Number of Bits of TBs Retransmitted on the Downlink SCH............................................................................ 1091
1.21.7 Number of TBs Initially Transmitted on the Uplink SCH...................................................................................1094
1.21.8 Number of bits of TBs Initially Transmitted on the Uplink SCH....................................................................... 1096
1.21.9 Number of TBs Retransmitted on the Uplink SCH............................................................................................. 1098
1.21.10 Number of bits of TBs Retransmitted on the Uplink SCH................................................................................ 1100
1.21.11 Number of Downlink Error TBs After Initial Transmission..............................................................................1102
1.21.12 Number of Downlink Error TBs After the Maximum Number of Retransmissions Is Reached.......................1105
1.21.13 Number of Uplink Error TBs After Initial Transmission.................................................................................. 1107
1.21.14 Number of Uplink Error TBs After the Maximum Number of Retransmissions Is Reached............................1110
1.21.15 Maximum Traffic Volume for MAC TBs in a Cell............................................................................................1111
1.21.16 Number of Bits of TBs Initially Transmitted on the Downlink SCH in the Shared Spectrum..........................1113
1.21.17 Number of TBs Initially Transmitted on the Downlink SCH in the Shared Spectrum..................................... 1114
1.21.18 Number of Bits of TBs Failed to be Transmitted During Initial Transmission on the Downlink SCH in the
Shared Spectrum............................................................................................................................................................. 1115
1.21.19 Number of TBs Failed to be Transmitted During Initial Transmission on the Downlink SCH in the Shared
Spectrum......................................................................................................................................................................... 1116
1.21.20 Duration of Downlink Scheduling in the Shared Spectrum...............................................................................1117
1.21.21 Duration of Downlink Scheduling in the Dedicated Spectrum......................................................................... 1118
1.21.22 Average Number of Used Downlink PRBs in the Shared Spectrum................................................................. 1119
1.21.23 Number of Times of Downlink Scheduling in the Shared Spectrum................................................................ 1120
1.21.24 Number of Times of Downlink Scheduling in the Dedicated Spectrum........................................................... 1121
1.21.25 Distribution of Packet Transmission Intervals for UEs in a Cell.......................................................................1122
1.21.26 Number of Error TBs After the Maximum Number of Retransmissions Is Reached for UEs with Poor Channel
Quality............................................................................................................................................................................ 1126
1.21.27 Number Of TBs Initially Transmitted for UEs with Poor Channel Quality...................................................... 1127
1.21.28 Number of Times that UEs are Scheduled in a Cell in the Uplink or Downlink...............................................1128
1.21.29 Number of Handover Command TBs Initially Transmitted on the Downlink SCH......................................... 1129
1.21.30 Number of Downlink Error TBs for Handover Commands After Initial Transmission....................................1131
1.21.31 Number of Downlink Error TBs for Handover Commands After the Maximum Number of Retransmissions is
Reached...........................................................................................................................................................................1133
1.21.32 Number of Voice Service TBs Initially Transmitted on the Uplink SCH..........................................................1134
1.21.33 Number of Voice Service TBs Retransmitted on the Uplink SCH.................................................................... 1137
1.21.34 Number of Voice Service TBs with Initial Transmission Failures on the Uplink SCH.....................................1139
1.21.35 Number of Voice Service TBs Initially Transmitted on the Downlink SCH.....................................................1141
1.21.36 Number of Voice Service TBs Retransmitted on the Downlink SCH............................................................... 1143
Issue 11 (2016-12-05) Huawei Proprietary and Confidential ix

1.21.37 Number of Voice Service TBs with Initial Transmission Failures on the Downlink SCH................................1145
1.21.38 Number of Service Data TBs Initially Transmitted on the Downlink SCH...................................................... 1147
1.21.39 Number of Service Data TBs Retransmitted on the Downlink SCH.................................................................1150
1.21.40 Number of Downlink Error Service Data TBs After Initial Transmission........................................................ 1152
1.21.41 Number of Downlink Error Service Data TBs After the Maximum Number of Retransmissions Is Reached. 1154
1.22 Cell User Quantity Measurement (Traffic.User.Cell).............................................................................................1156
1.22.1 Number of Users in a Cell................................................................................................................................... 1176
1.22.2 Number of ICIC Cell Edge Users in a Cell......................................................................................................... 1178
1.22.3 Number of UEs with Data in the Uplink Buffer.................................................................................................. 1181
1.22.4 Number of UEs with Data in the Downlink Buffer............................................................................................. 1182
1.22.5 Number of UL Synchronized Users in a Cell...................................................................................................... 1183
1.22.6 Number of UEs Transmitting or Receiving Data in a Cell..................................................................................1184
1.22.7 Number of UL CoMP UEs in a Cell....................................................................................................................1186
1.22.8 Number of CA UEs in a Cell............................................................................................................................... 1189
1.22.9 Average Number of Activated UEs with a Specific QCI in the Uplink Buffer...................................................1203
1.22.10 Average Number of Activated UEs with a Specific QCI in the Downlink Buffer............................................1207
1.22.11 Number of UEs Configured with SRS Resources in a Cell...............................................................................1211
1.22.12 Number of UEs on Which TTI Bundling Takes Effect in a Cell.......................................................................1212
1.22.13 Number of UEs on Which ROHC Takes Effect in a Cell..................................................................................1213
1.22.14 Number of UEs on Which DRX Takes Effect in a Cell.................................................................................... 1214
1.22.15 Number of Uplink IiCS UEs with Strong Interference in a Cell.......................................................................1215
1.22.16 Number of Uplink IiCS UEs with Weak Interference in a Cell........................................................................ 1216
1.22.17 Number of Activated UEs in the Downlink in a Cell........................................................................................1217
1.22.18 Number of Activated UEs in the Uplink in a Cell.............................................................................................1218
1.22.19 Number of Activated UEs in a Cell...................................................................................................................1219
1.22.20 Number of UEs Enabled with the eICIC Function in a Cell............................................................................. 1220
1.22.21 Average number of CoMP UEs in a cell........................................................................................................... 1222
1.22.22 Number of UEs in a Cell That Are Close to the Border with the Other Type of Cells in a Heterogeneous
Network.......................................................................................................................................................................... 1223
1.22.23 Number of UEs in a Cell That Are Close to the Border with the Other Type of Cells and Support TDM eICIC in
a Heterogeneous Network.............................................................................................................................................. 1224
1.22.24 Number of Privileged UEs in a Cell.................................................................................................................. 1225
1.22.25 Number of UEs Whose Uplink Timing Offsets are Measured Based on the PUCCH...................................... 1226
1.22.26 Maximum Number of Activated UEs with a QCI in the Downlink Buffer.......................................................1228
1.22.27 Maximum Number of Activated UEs with a QCI in the Uplink Buffer........................................................... 1232
1.22.28 Number of Scheduled UEs per TTI in the Downlink in a Cell......................................................................... 1236
1.22.29 Number of Scheduled UEs per TTI in the Uplink in a Cell.............................................................................. 1237
1.22.30 Maximum Total Number of Scheduled UEs per TTI in the Uplink and Downlink in a Cell............................1238
1.22.31 Licensed Number of UEs in RRC_CONNECTED Mode.................................................................................1239
1.22.32 Number of UEs running unlimited services...................................................................................................... 1240
1.22.33 Average and Maximum Numbers of Activated CA UEs That Use the Local Cell As Their Scell................... 1241
1.22.34 Number of Times the UE Quantity in a Cell Falls Within Different Ranges.................................................... 1244
1.22.35 Number of VoIP UEs in a Cell.......................................................................................................................... 1248
Issue 11 (2016-12-05) Huawei Proprietary and Confidential x

1.22.36 Number of UEs that apply TM9 in a cell.......................................................................................................... 1250

1.22.37 Average Number and Maximum Number of Uplink CA UEs that Use the Local Cell as Their Scell..............1251
1.22.38 Average and Maximum Number of CA UEs that Use the Local Cell as Their PCells in the Uplink............... 1252
1.22.39 Average Number and Maximum Number of Downlink Relaxed-Backhaul-based Inter-eNodeB CA UEs that
Treat the Local Cell as Their PCell or Scell................................................................................................................... 1254
1.22.40 Average and Maximum Number of CA UEs with the Local Cell as Their PCell and with All Configured Two
SCCs Activated...............................................................................................................................................................1256
1.22.41 Average Number and Maximum Number of CA UEs that Treat the Local Cell as Their SCell and Have the Cell
Activated in the Uplink...................................................................................................................................................1258
1.22.42 Duration of CA UEs in the Uplink CA State that Treat the Local Cell as Their PCell and Have the SCell
Activated.........................................................................................................................................................................1259
1.22.43 Duration of CA UEs in the Uplink CA State that Treat the Local Cell as Their SCell and Have the SCell
Activated.........................................................................................................................................................................1260
1.22.44 Number of Times Inter-eNodeB CA based on Relaxed Backhaul Stops Because the Inter-eNodeB Transmission
Delay Does Not Meet the Requirement..........................................................................................................................1261
1.22.45 Number of UEs on Which Smart DRX Takes Effect in a Cell..........................................................................1262
1.22.46 Number of UEs that Are Configured with a GBR and Whose Throughput Falls Within Different Ranges.....1263
1.22.47 Average Number of FeICIC-capable UEs in a Cell...........................................................................................1266
1.22.48 Average Number of FeICIC-capable UEs in a Cell that Are Close to the Border with the Other Type of Cells in
a HetNet.......................................................................................................................................................................... 1267
1.22.49 Number of CEUs in Adaptive ICIC in a Cell.................................................................................................... 1268
1.22.50 Average number of UEs for Which Coordinated Uplink AMC Is Used in a Cell.............................................1269
1.22.51 Average Number of Inter-eNodeB DL CoMP UEs in a Cell............................................................................ 1270
1.22.52 Average Number of UEs Using the UMTS and LTE Shared Spectrum in a Cell............................................. 1271
1.22.53 Number of CA UEs That Treat the Local Cell as Their PCell and Have All SCells Activated........................1272
1.22.54 Number of CA UEs That Treat the Local Cell as Their PCell and Have All SCells Activated for Downlink 4CC
CA...................................................................................................................................................................................1276
1.22.55 Number of CA UEs That Treat the Local Cell as Their PCell and Have All SCells Activated for Downlink FDD
+TDD CA....................................................................................................................................................................... 1279
+TDD 3CC CA...............................................................................................................................................................1282
+TDD 4CC CA...............................................................................................................................................................1285
1.22.58 Number of UEs with Service Data to Be Transmitted in a Cell........................................................................ 1288
1.23 Outgoing Inter-RAT Handover Measurement (HO.IRAT.Out.Cell).......................................................................1289
1.23.1 Number of Inter-RAT Handover Attempts from E-UTRAN to CDMA2000 Network.......................................1332
1.23.2 Number of Inter-RAT Handovers Executions from E-UTRAN to CDMA2000 Network.................................. 1334
1.23.3 Number of Successful Inter-RAT Handovers from E-UTRAN to CDMA2000 Network...................................1336
1.23.4 Number of Inter-RAT Handover Attempts from E-UTRAN to WCDMA Network...........................................1338
1.23.5 Number of Inter-RAT Handovers Executions from E-UTRAN to WCDMA Network...................................... 1340
1.23.6 Number of Successful Inter-RAT Handovers from E-UTRAN to WCDMA Network.......................................1342
1.23.7 Number of Inter-RAT Handover Attempts from E-UTRAN to GERAN............................................................1344
1.23.8 Number of Inter-RAT Handovers Executions from E-UTRAN to GERAN....................................................... 1346
1.23.9 Number of Successful Inter-RAT Handovers from E-UTRAN to GERAN........................................................1348
1.23.10 Number of Inter-RAT Handover Attempts from E-UTRAN to TD-SCDMA Network....................................1350
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xi

1.23.11 Number of Inter-RAT Handovers Executions from E-UTRAN to TD-SCDMA Network............................... 1352
1.23.12 Number of Successful Inter-RAT Handovers from E-UTRAN to TD-SCDMA Network................................1354
1.23.13 Number of Inter-RAT Handover Failures for Different Causes........................................................................ 1356
1.23.14 Number of Inter-RAT Blind Handover Attempts from E-UTRAN to Another System....................................1365
1.23.15 Number of Blind Handover Executions from E-UTRAN to Another System.................................................. 1368
1.23.16 Number of successful Inter-RAT Blind Handovers from E-UTRAN to Another System ............................... 1370
1.23.17 Number of Indicators for CSFB to Another System......................................................................................... 1373
1.23.18 Number of CSFB Responses to MMEs............................................................................................................. 1377
1.23.19 Number of Procedures for CSFB to Another System........................................................................................1380
1.23.20 Number of Inter-RAT Redirection Preparations from E-UTRAN to Another System..................................... 1403
1.23.21 Number of Inter-RAT Redirections from E-UTRAN to Another System......................................................... 1407
1.23.22 Number of Inter-RAT Handover Attempts from E-UTRAN to WCDMA network for SRVCC...................... 1411
1.23.23 Number of Inter-RAT Handover Executions from E-UTRAN to WCDMA network for SRVCC................... 1413
1.23.24 Number of Successful Inter-RAT Handovers from E-UTRAN to WCDMA Network for SRVCC................. 1415
1.23.25 Number of Inter-RAT Handover Attempts from E-UTRAN to GERAN for SRVCC...................................... 1417
1.23.26 Number of Inter-RAT Handover Executions from E-UTRAN to GERAN for SRVCC................................... 1419
1.23.27 Number of Successful Inter-RAT Handovers from E-UTRAN to GERAN for SRVCC.................................. 1421
1.23.28 Number of Inter-RAT Handover Attempts from E-UTRAN to TD-SCDMA Network for SRVCC................ 1423
1.23.29 Number of Inter-RAT Handover Executions from E-UTRAN to TD-SCDMA Network for SRVCC............. 1425
1.23.30 Number of Successful Inter-RAT Handovers from E-UTRAN to TD-SCDMA network for SRVCC............. 1427
1.23.31 Number of LCS-triggered CS Fallback Indicators Received by the eNodeB................................................... 1429
1.23.32 Number of Responses Sent from the eNodeB to MMEs for CSFB Triggered by LCS.................................... 1431
1.23.33 Number of CCO Executions from E-UTRAN to GERAN................................................................................1433
1.23.34 Number of Successful CCOs from E-UTRAN to GERAN...............................................................................1435
1.23.35 Number of Inter-RAT Handover Initiation Failures Because the Adjacent Cell is not the NRT of the Source Cell
........................................................................................................................................................................................ 1437
1.23.36 Number of CSFB Preparation Failures Because of Process Conflict................................................................1442
1.23.37 Number of Handover Preparation Attempts from E-UTRAN to WCDMA Network Triggered Because of High
Load................................................................................................................................................................................ 1444
1.23.38 Number of Inter-RAT Handover Execution Attempts Triggered Because of High Load................................. 1447
1.23.39 Number of Successful Inter-RAT Handover Executions Triggered Because of High Load............................. 1450
1.23.40 Number of Redirections from E-UTRAN to WCDMA Network Triggered Because of High Load................1453
1.23.41 Number of Inter-RAT Handover Attempts from E-UTRAN to WCDMA Network Triggered for UEs to Go back
to the HPLMN................................................................................................................................................................ 1455
1.23.42 Number of Inter-RAT Handover Executions from E-UTRAN to WCDMA Network Triggered for UEs to Go
back to the HPLMN........................................................................................................................................................1457
1.23.43 Number of Inter-RAT Handovers from E-UTRAN to WCDMA Network Triggered for UEs to Go back to the
HPLMN.......................................................................................................................................................................... 1459
1.23.44 Number of Inter-RAT Handover Executions from E-UTRAN to WCDMA Network Triggered for UEs That Do
not Transmit or Receive Data......................................................................................................................................... 1461
1.23.45 Number of Successful Inter-RAT Handovers from E-UTRAN to WCDMA Network Triggered for UEs That Do
not Transmit or Receive Data......................................................................................................................................... 1463
1.23.46 Number of LCS-based Inter-RAT Handover Executions for SRVCC...............................................................1465
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xii

1.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........................................................................................... 1470
Handover Executions from E-UTRAN to Another System for SRVCC........................................................................ 1475
1.23.49 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During CCO Executions
from E-UTRAN to GERAN........................................................................................................................................... 1478
1.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.......................................................................... 1480
1.23.51 Number of Inter-RAT Handover Attempts from E-UTRAN to CDMA2000 HRPD Network......................... 1484
1.23.52 Number of Inter-RAT Handover Executions from E-UTRAN to CDMA2000 HRPD Network......................1486
1.23.53 Number of Successful Inter-RAT Handovers from E-UTRAN to CDMA2000 HRPD Network..................... 1488
1.23.54 Handover Time from E-UTRAN to Another RAT............................................................................................ 1490
1.23.55 Number of Coverage-based Inter-RAT Handover Attempts from E-UTRAN to Another System................... 1494
1.23.56 Number of Coverage-based Inter-RAT Handover Executions from E-UTRAN to Another System................1496
1.23.57 Number of Successful Coverage-based Inter-RAT Handovers from E-UTRAN to Another System............... 1498
1.23.58 Number of Coverage-based Inter-RAT Redirections from E-UTRAN to Another System.............................. 1501
1.23.59 Number of SPID-based Inter-RAT Redirections Back to the HPLMN............................................................. 1503
1.23.60 Number of Successful Service-based Inter-RAT Outgoing Handover Attempts from E-UTRAN to Another
System............................................................................................................................................................................ 1504
1.23.61 Number of Service-based Inter-RAT Outgoing Handover Executions from E-UTRAN to Another System... 1507
1.23.62 Number of Successful Service-based Inter-RAT Outgoing Handovers from E-UTRAN to Another System.. 1509
1.23.63 Number of Service-based Inter-RAT Redirections from E-UTRAN to Another System..................................1511
1.23.64 Number of UL-Quality-based Outgoing Handover Attempts from E-UTRAN to Another System.................1513
1.23.65 Number of UL-Quality-based Outgoing Handover Executions from E-UTRAN to Another System..............1515
1.23.66 Number of Successful UL-Quality-based Outgoing Handovers from E-UTRAN to Another System.............1518
1.23.67 Number of UL-Quality-based Inter-RAT Redirections from E-UTRAN to Another System...........................1520
1.23.68 Number of Distance-based Inter-RAT Outgoing Handover Attempts from E-UTRAN to Another System.... 1522
1.23.69 Number of Distance-based Inter-RAT Outgoing Handover Executions from E-UTRAN to Another System. 1524
1.23.70 Number of Successful Distance-based Inter-RAT Outgoing Handovers from E-UTRAN to Another System 1527
1.23.71 Number of Distance-based Inter-RAT Redirections from E-UTRAN to Another System............................... 1529
1.23.72 Number of Inter-RAT CSFB-based Handover Failures for Different Causes................................................... 1531
1.23.73 Number of Inter-RAT SRVCC-based Handover Failures for Different Causes................................................ 1536
1.23.74 Number of Outgoing CS-Only SRVCC-based Handover Attempts from E-UTRAN to WCDMA Network...1542
1.23.75 Number of Outgoing CS-Only SRVCC-based Handover Executions from E-UTRAN to WCDMA Network
........................................................................................................................................................................................ 1544
1.23.76 Number of Successful Outgoing CS-Only SRVCC-based Handovers from E-UTRAN to WCDMA Network
........................................................................................................................................................................................ 1546
1.23.77 Number of Outgoing CS-Only SRVCC-based Handover Attempts from E-UTRAN to TD-SCDMA Network
........................................................................................................................................................................................ 1548
1.23.78 Number of Outgoing CS-Only SRVCC-based Handover Executions from E-UTRAN to TD-SCDMA Network
........................................................................................................................................................................................ 1550
1.23.79 Number of Successful Outgoing CS-Only SRVCC-based Handovers from E-UTRAN to TD-SCDMA Network
........................................................................................................................................................................................ 1552
1.23.80 Number of Outgoing CS-Only SRVCC-based Handover Attempts from E-UTRAN to GERAN....................1554
1.23.81 Number of Outgoing CS-Only SRVCC-based Handover Executions from E-UTRAN to GERAN................ 1556
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xiii

1.23.82 Number of Successful Outgoing CS-Only SRVCC-based Handovers from E-UTRAN to GERAN................1558
1.23.83 Number of SRVCC-based Outgoing Handover Attempts from E-UTRAN to WCDMA Network for Ultra-Flash
CSFB.............................................................................................................................................................................. 1560
1.23.84 Number of SRVCC-based Outgoing Handover Executions from E-UTRAN to WCDMA Network for Ultra-
Flash CSFB.....................................................................................................................................................................1562
1.23.85 Number of Successful SRVCC-based Outgoing Handovers from E-UTRAN to WCDMA Network for Ultra-
Flash CSFB.....................................................................................................................................................................1564
1.23.86 Number of Responses with Abnormal Causes Received by the eNodeB from the MME During Inter-RAT Blind
1.23.87 Number of Ultra-Flash CSFB Attempts............................................................................................................ 1568
1.23.88 Number of Ultra-Flash CSFB Executions......................................................................................................... 1570
1.23.89 Number of Successful Ultra-Flash CSFBs........................................................................................................ 1572
1.23.90 Number of Abnormal Responses from the MME During Ultra-Flash CSFB to GERAN................................ 1574
1.24 Outgoing Inter-RAT Handover Measurement 1 (HO.IRAT.Out.Cell.1).................................................................1576
1.24.1 Number of Handover Preparation Attempts from E-UTRAN to WCDMA Network Triggered by UE-Number-
Based MLB.....................................................................................................................................................................1582
1.24.2 Number of Handover Execution Attempts from E-UTRAN to WCDMA Network Triggered by UE-Number-
Based MLB.....................................................................................................................................................................1585
1.24.3 Number of Successful Handover Executions from E-UTRAN to WCDMA Network Triggered by UE-Number-
based MLB..................................................................................................................................................................... 1587
Outgoing Handovers for Ultra-Flash CSFB................................................................................................................... 1589
1.24.5 Number of Inter-RAT Outgoing Handover Failures for Ultra-Flash CSFB for Different Causes...................... 1591
1.24.6 Number of QoE-based EUTRAN-to-WCDMA Handover Attempts..................................................................1596
1.24.7 Number of QoE-based EUTRAN-to-WCDMA Handover Executions...............................................................1597
1.24.8 Number of Successful QoE-based EUTRAN-to-WCDMA Handovers..............................................................1599
1.24.9 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During QoE-based
EUTRAN-to-WCDMA Handover Executions............................................................................................................... 1600
1.24.10 Number of Coverage-based Inter-RAT Handover Executions from E-UTRAN to Another System................1602
1.24.11 Number of Successful Coverage-based Inter-RAT Handovers from E-UTRAN to Another System............... 1604
1.24.12 Number of Coverage-based Inter-RAT Handover Attempts from E-UTRAN to Another System................... 1606
1.24.13 Number of Successful Service-based Inter-RAT Handover Attempts from E-UTRAN to Another System.... 1608
1.24.14 Number of Service-based Inter-RAT Handover Executions from E-UTRAN to Another System................... 1610
1.24.15 Number of Successful Service-based Inter-RAT Handovers from E-UTRAN to Another System.................. 1612
1.24.16 Number of Coverage-based Inter-RAT Redirections from E-UTRAN to Another System.............................. 1614
1.24.17 Number of Service-based Inter-RAT Redirections from E-UTRAN to TD-SCDMA Network....................... 1615
1.24.18 Number of CSFB Executions from E-UTRAN to Another System.................................................................. 1616
1.24.20 Number of Inter-RAT Blind Redirections......................................................................................................... 1621
1.25 Incoming Inter-RAT Handover Measurement (HO.IRAT.In.Cell)......................................................................... 1622
1.25.1 Number of Inter-RAT Handover Attempts from GERAN to E-UTRAN............................................................1628
1.25.2 Number of Inter-RAT Handover Preparation from GERAN to E-UTRAN........................................................ 1629
1.25.3 Number of Successful Inter-RAT Handovers from GERAN to E-UTRAN........................................................1631
1.25.4 Number of Inter-RAT Incoming Handover Preparation Failures for Different Causes in a Cell........................1633
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xiv

1.25.5 Number of Inter-RAT Handover Attempts from TD-SCDMA Network to E-UTRAN......................................1645

1.25.6 Number of Inter-RAT Handover Preparation from TD-SCDMA Network to E-UTRAN.................................. 1647
1.25.7 Number of Successful Inter-RAT Handovers from TD-SCDMA Network to E-UTRAN..................................1649
1.25.8 Number of Inter-RAT Handover Attempts from WCDMA Network to E-UTRAN...........................................1650
1.25.9 Number of Inter-RAT Handover Preparation from WCDMA Network to E-UTRAN....................................... 1652
1.25.10 Number of Successful Inter-RAT Handovers from WCDMA Network to E-UTRAN.....................................1654
1.26 Outgoing Intra-RAT Handover Measurement (HO.eRAN.Out.Cell).....................................................................1655
1.26.1 Number of Intra-eNodeB Outgoing Handover Attempts in a Cell......................................................................1685
1.26.2 Number of Intra-eNodeB Outgoing Handovers Executions in a Cell................................................................. 1687
1.26.3 Number of Successful Intra-eNodeB Outgoing Handovers in a Cell..................................................................1690
1.26.4 Number of Inter-eNodeB Outgoing Handover Attempts in a Cell......................................................................1693
1.26.5 Number of Inter-eNodeB Outgoing Handovers Executions in a Cell................................................................. 1696
1.26.6 Number of Successful Inter-eNodeB Outgoing Handovers in a Cell..................................................................1699
1.26.7 Number of Outgoing Blind Handover Attempts in a Cell...................................................................................1705
1.26.8 Number of Outgoing Blind Handovers Executions in a Cell.............................................................................. 1708
1.26.9 Number of Successful Outgoing Blind Handovers in a Cell............................................................................... 1711
1.26.10 Number of Outgoing Handover Failures for Different Causes in a Cell........................................................... 1718
1.26.11 Number of Intra-RAT Redirections................................................................................................................... 1732
1.26.12 Number of Intra-RAT Handover Initiation Failures Because the Adjacent Cell is not on the NRT of the Source
Cell..................................................................................................................................................................................1737
1.26.13 Number of Load-based Inter-Frequency Handover Preparation Attempts........................................................1741
1.26.14 Number of Load-based Inter-Frequency Handover Execution Attempts..........................................................1744
1.26.15 Number of Successful Load-based Inter-Frequency Handover Executions......................................................1747
1.26.16 Number of Inter-Frequency Outgoing Handover Attempts Triggered for UEs to Go back to the HPLMN.....1755
1.26.17 Number of Inter-Frequency Outgoing Handover Executions Triggered for UEs to Go back to the HPLMN..1757
1.26.18 Number of Successful Inter-Frequency Outgoing Handovers Triggered for UEs to Go Back to the HPLMN 1760
1.26.19 Number of Intra-Frequency Handover Execution Attempts Triggered for UEs that do not transmit or receive
data..................................................................................................................................................................................1766
1.26.20 Number of Successful Intra-Frequency Handover Executions Triggered for UEs that do not transmit or receive
data..................................................................................................................................................................................1769
1.26.21 Number of Inter-Frequency Handover Execution Attempts Triggered for UEs That Do not Transmit or Receive
Data.................................................................................................................................................................................1776
1.26.22 Number of Successful Inter-Frequency Handover Executions Triggered for UEs That Do not Transmit or
Receive Data...................................................................................................................................................................1779
1.26.23 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During S1-based
Outgoing Handover Executions......................................................................................................................................1786
1.26.24 Number of Successful Intra-eNodeB Outgoing Handovers Where RRC Connections Are Reestablished to the
Source Cell for UEs in a Cell......................................................................................................................................... 1789
1.26.25 Number of Successful Inter-eNodeB Outgoing Handovers Where RRC Connections Are Reestablished to the
Source Cell for UEs in a Cell......................................................................................................................................... 1792
1.26.26 Number of Successful Blind Outgoing Handovers Where RRC Connections Are Reestablished to the Source
Cell for UEs in a cell...................................................................................................................................................... 1796
1.26.27 Number of Coverage-based Inter-Frequency Handover Preparation Attempts................................................ 1801
1.26.28 Number of Coverage-based Inter-Frequency Handover Execution Attempts...................................................1804
1.26.29 Number of Successful Coverage-based Inter-Frequency Handovers................................................................ 1806
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xv

1.26.30 Inter-eNodeB Handover Time in a Cell.............................................................................................................1813

1.26.31 Number of Service-based Inter-Frequency Handover Preparation Attempts....................................................1816
1.26.32 Number of Service-based Inter-Frequency Handover Execution Attempts...................................................... 1819
1.26.33 Number of Successful Service-based Inter-Frequency Handover Executions.................................................. 1822
1.26.34 Number of Frequency-Priority-based Inter-Frequency Handover Preparation Attempts................................. 1829
1.26.35 Number of Frequency-Priority-based Inter-Frequency Handover Execution Attempts....................................1831
1.26.36 Number of Successful Frequency-Priority-based Inter-Frequency Handover Executions................................1833
1.26.37 Number of Intra-eNodeB Outgoing Handover Attempts for UEs Performing Voice Services in a Cell.......... 1840
1.26.38 Number of Intra-eNodeB Outgoing Handover Executions for UEs Performing Voice Services in a Cell....... 1842
1.26.39 Number of Successful Intra-eNodeB Outgoing Handovers for UEs Performing Voice Services in a Cell...... 1845
1.26.40 Number of Inter-eNodeB Outgoing Handover Attempts for UEs Performing Voice Services in a Cell.......... 1848
1.26.41 Number of Inter-eNodeB Outgoing Handover Executions for UEs Performing Voice Services in a Cell....... 1852
1.26.42 Number of Successful Inter-eNodeB Outgoing Handovers for UEs Performing Voice Services in a Cell...... 1855
1.26.43 Number of Inter-Duplex-Mode Handover Execution Attempts Triggered for UEs that Do Not Transmit or
Receive Data...................................................................................................................................................................1862
1.26.44 Number of Successful Inter-Duplex-Mode Handover Executions Triggered for UEs that Do Not Transmit or
Receive Data...................................................................................................................................................................1865
1.26.45 Number of Load-based Inter-Duplex-Mode Handover Preparation Attempts.................................................. 1872
1.26.46 Number of Load-based Inter-Duplex-Mode Handover Execution Attempts.................................................... 1875
1.26.47 Number of Successful Load-based Inter-Duplex-Mode Handover Executions................................................ 1878
1.26.48 Number of Coverage-based Inter-Duplex-Mode Handover Preparation Attempts........................................... 1885
1.26.49 Number of Coverage-based Inter-Duplex-Mode Handover Execution Attempts............................................. 1888
1.26.50 Number of Successful Coverage-based Inter-Duplex-Mode Handover Executions......................................... 1890
1.26.51 Number of SPID-based Inter-Duplex-Mode Outgoing Handover Attempts back to the HPLMN................... 1897
1.26.52 Number of SPID-based Inter-Duplex-Mode Outgoing Handover Executions back to the HPLMN................ 1899
1.26.53 Number of Successful SPID-based Inter-Duplex-Mode Outgoing Handovers back to the HPLMN............... 1902
1.26.54 Number of UL-Quality-based Inter-Frequency Handover Preparation Attempts............................................. 1909
1.26.55 Number of UL-Quality-based Inter-Duplex-Mode Handover Preparation Attempts........................................1911
1.26.56 Number of UL-Quality-based Inter-Frequency Handover Execution Attempts............................................... 1914
1.26.57 Number of UL-Quality-based Inter-Duplex-Mode Handover Execution Attempts..........................................1916
1.26.58 Number of Successful UL-Quality-based Inter-Frequency Handover Executions........................................... 1919
1.26.59 Number of Successful UL-Quality-based Inter-Duplex-Mode Handover Executions......................................1926
1.26.60 Number of Service-Based Inter-Duplex-Mode Handover Preparation Attempts..............................................1933
1.26.61 Number of Service-based Inter-Duplex-Mode Handover Execution Attempts................................................ 1935
1.26.62 Number of Successful Service-based Inter-Duplex-Mode Handover Executions............................................ 1938
1.26.63 Number of Frequency-Priority-based Inter-Duplex-Mode Handover Preparation Attempts............................1945
1.26.64 Number of Frequency-Priority-based Inter-Duplex-Mode Handover Execution Attempts.............................. 1947
1.26.65 Number of Successful Frequency-Priority-based Inter-Duplex-Mode Handover Executions.......................... 1949
1.26.66 Number of Distance-based Inter-Frequency Handover Preparation Attempts..................................................1956
1.26.67 Number of Distance-based Inter-Duplex-Mode Handover Preparation Attempts............................................ 1958
1.26.68 Number of Distance-based Inter-Frequency Handover Execution Attempts.................................................... 1961
1.26.69 Number of Distance-based Inter-Duplex-Mode Handover Execution Attempts.............................................. 1963
1.26.70 Number of Successful Distance-based Inter-Frequency Handover Executions................................................ 1966
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xvi

1.26.71 Number of Successful Distance-based Inter-Duplex-Mode Handover Executions.......................................... 1972

1.26.72 Number of Responses With Abnormal Causes Received by the eNodeB from the MME During S1-based
Outgoing Blind Handover Executions............................................................................................................................1979
1.26.73 Number of Inter-Frequency Outgoing Handover Preparation Attempts Triggered by Interests in MBMS
Services...........................................................................................................................................................................1981
1.26.74 Number of Inter-Frequency Outgoing Handover Execution Attempts Triggered by Interests in MBMS Services
........................................................................................................................................................................................ 1983
1.26.75 Number of Successful Inter-Frequency Handovers Triggered by Interests in MBMS Services.......................1986
1.26.76 Number of Inter-Duplex-Mode Outgoing Handover Preparation Attempts Triggered by Interests in MBMS
Services...........................................................................................................................................................................1993
1.26.77 Number of Inter-Duplex-Mode Outgoing Handover Execution Attempts Triggered by Interests in MBMS
Services...........................................................................................................................................................................1995
1.26.78 Number of Successful Inter-Duplex-Mode Handovers Triggered by Interests in MBMS Services................. 1998
1.26.79 Number of Inter-Frequency Outgoing Handover Preparation Attempts of Low-Speed Ues............................ 2005
1.26.80 Number of Inter-Frequency Outgoing Handover Execution Attempts of Low-Speed Ues.............................. 2008
1.26.81 Number of Successful Inter-Frequency Outgoing Handover Executions of Low-Speed Ues...........................2011
1.26.82 Number of Times when the eNodeB Receives Messages from the MME with Abnormal Reasons During Inter-
Frequency Outgoing Handover Executions of Low-Speed UEs.................................................................................... 2020
1.26.83 Number of Intra-eNodeB Inter-SFN-Cell Outgoing Handover Attempts in a Super Combined Cell...............2022
1.26.84 Number of Successful Intra-eNodeB Inter-SFN-Cell Outgoing Handovers in a Super Combined Cell...........2023
1.26.85 Number of Inter-eNodeB Inter-SFN-Cell Outgoing Handover Attempts in a Super Combined Cell...............2025
1.26.86 Number of Successful Inter-eNodeB Inter-SFN-Cell Outgoing Handovers in a Super Combined Cell...........2027
1.26.87 Number of Inter-duplex-mode Handover Preparation Attempts Triggered by MLB Based on the Number of
Low-Efficiency UEs....................................................................................................................................................... 2029
1.26.88 Number of Inter-duplex-mode Handover Execution Attempts Triggered by MLB Based on the Number of Low-
Efficiency UEs................................................................................................................................................................2032
1.26.89 Number of Successful Inter-duplex-mode Handovers Triggered by MLB Based on the Number of Low-
Efficiency UEs................................................................................................................................................................2035
1.26.90 Number of Times That the eNodeB Receives Responses from the MME Due to Abnormal Reasons During S1-
based Inter-duplex-mode Outgoing Handovers Triggered by MLB Based on the Number of Low-Efficiency UEs.... 2042
1.26.91 Number of Inter-eNodeB Inter-SFN-Cell outgoing Handover Executions in a Super Combined Cell............ 2044
1.26.92 Number of Service-triggered Inter-duplex-mode Measurement Expiration Times...........................................2046
1.26.93 Number of unsuccessful service-triggered inter-duplex-mode handover initiation request attempts due to lack of
neighboring relationship between two cells................................................................................................................... 2048
1.27 Outgoing Intra-RAT Handover Measurement 1 (HO.eRAN.Out.Cell.1)...............................................................2049
1.27.1 Number of Successful Intra-eNodeB Voice Service Outgoing Handovers by Reestablishing RRC Connections in
the Source Cell................................................................................................................................................................2053
1.27.2 Number of Successful Inter-eNodeB Voice Service Outgoing Handovers by Reestablishing RRC Connections in
the Source Cell................................................................................................................................................................2055
1.27.3 Number of Outgoing Handover Failures for Different Causes in a Cell............................................................. 2059
1.27.4 Number of Intra-RAT Redirections Triggered by High-Speed UEs....................................................................2061
1.27.5 Number of Outgoing Handover Preparation Failures for 3GPP-Defined Causes............................................... 2062
1.28 Incoming Intra-RAT Handover Measurement (HO.eRAN.In.Cell)....................................................................... 2064
1.28.1 Number of Intra-eNodeB Incoming Handover Attempts in a Cell......................................................................2079
1.28.2 Number of Intra-eNodeB Incoming Handovers Executions in a Cell.................................................................2081
1.28.3 Number of Successful Intra-eNodeB Incoming Handovers in a Cell..................................................................2083
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xvii

1.28.4 Number of Inter-eNodeB Incoming Handover Attempts in a Cell......................................................................2086

1.28.5 Number of Inter-eNodeB Incoming Handovers Executions in a Cell................................................................. 2089
1.28.6 Number of Successful Inter-eNodeB Incoming Handovers in a Cell..................................................................2092
1.28.7 Number of Incoming Handover Failures for Different Causes in a Cell.............................................................2096
1.28.8 Number of Path Switch Requests for Inter-eNodeB Incoming Handovers in a Cell...........................................2118
1.28.9 Number of Successful Path Switches for inter-eNodeB Incoming Handovers in a Cell.....................................2120
1.28.10 Number of HANDOVER CANCEL Messages Received by the Target Cell from the Source Cell During Inter-
eNodeB Incoming Handover Executions in a Cell.........................................................................................................2123
1.28.11 Number of Successful Intra-eNodeB Incoming Handovers Where RRC Connections Are Reestablished to the
Target Cell for UEs in a Cell.......................................................................................................................................... 2128
1.28.12 Number of Successful Inter-eNodeB Incoming Handovers Where RRC Connections Are Reestablished to the
Target Cell for UEs in a Cell.......................................................................................................................................... 2131
1.28.13 Number of conflicts with inter-eNodeB incoming handovers in a cell............................................................. 2134
1.28.14 Number of Incoming Handover Preparation Failures for 3GPP-Defined Causes.............................................2136
1.29 Outgoing Intra-RAT Handover Measurement over X2 (HO.eRAN.X2Out.Cell).................................................. 2139
1.29.1 Number of X2-based Outgoing Handover Attempts in a Cell............................................................................ 2147
1.29.2 Number of X2-based Outgoing Handover Executions in a Cell......................................................................... 2150
1.29.3 Number of Successful X2-based Outgoing Handovers in a Cell........................................................................ 2154
1.29.4 Number of X2-based Outgoing Handover Failures for Different Causes in a Cell.............................................2158
1.29.5 Number of Successful X2-based Outgoing Handovers Where RRC Connections Are Reestablished to the Source
Cell for UEs in a Cell..................................................................................................................................................... 2171
1.29.6 Number of Inter-eNodeB X2-based Voice Service Outgoing Handover Attempts in a Cell.............................. 2174
1.29.7 Number of Inter-eNodeB X2-based Voice Service Outgoing Handover Executions in a Cell........................... 2176
1.29.8 Number of Successful X2-based Voice Service Outgoing Handovers in a Cell................................................. 2178
1.29.9 Number of Successful X2-based Inter-Frequency Voice Service Outgoing Handovers by Reestablishing RRC
Connections in the Source Cell...................................................................................................................................... 2182
1.29.10 Number of X2-based Outgoing Handover Failures for Different Causes in a Cell...........................................2184
1.30 Outgoing Intra-RAT Handover Measurement in DRX (HO.DRX.Out.Cell)......................................................... 2186
1.30.1 Number of Intra-eNodeB Outgoing Handovers Executions in the DRX State................................................... 2190
1.30.2 Number of Successful Intra-eNodeB Outgoing Handovers in the DRX State....................................................2192
1.30.3 Number of Inter-eNodeB Outgoing Handovers Executions in the DRX State................................................... 2196
1.30.4 Number of Successful Inter-eNodeB Outgoing Handovers in the DRX State.................................................... 2199
1.31 Packet Measurement (Traffic.Packet.Cell)............................................................................................................. 2206
1.31.1 Downlink Packet Processing Delay of DRB Services in a Cell.......................................................................... 2223
1.31.2 Number of Successfully Transmitted Downlink PDCP SDUs for DRB Services in a Cell................................2227
1.31.3 Number of Downlink PDCP SDUs Discarded for Services Carried on DRBs in a Cell over the Uu Interface. 2232
1.31.4 Number of Downlink PDCP SDUs Transmitted for Services Carried on DRBs in a Cell over the Uu Interface
........................................................................................................................................................................................ 2237
1.31.5 Number of Uplink PDCP SDUs Discarded for Services Carried on DRBs in a Cell......................................... 2243
1.31.6 Number of Expected Uplink PDCP SDUs for Services Carried on DRBs in a Cell...........................................2248
1.31.7 Total Number of Downlink PDCP SDUs that Are for DRB Services and Enter the Empty Buffer in a Cell.....2253
1.31.8 Total Transmission Delay of the First PDCP SDUs of DRB Services in the Empty Buffer in a Cell................ 2257
1.32 DFEE Measurement (ChMeas.DFEE.Cell)............................................................................................................2262
1.32.1 Duration of Energy Saving and Emission Reduction.......................................................................................... 2262
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xviii

1.33 Cell LCS Measurement (LCS.Cell)........................................................................................................................2264

1.33.1 Number of E-CID Measurement Requests in a Cell........................................................................................... 2265
1.33.2 Number of Successful E-CID Measurement Requests in a Cell......................................................................... 2267
1.34 Cell Emergency Call Measurement (EMC.Cell).................................................................................................... 2268
1.34.1 Number of Outgoing Handover Attempts for Emergency Calls in a Cell...........................................................2272
1.34.2 Number of Executed Outgoing Handovers for Emergency Calls in a Cell......................................................... 2275
1.34.3 Number of Successful Outgoing Handovers for Emergency Calls in a Cell.......................................................2278
1.34.4 Number of E-RAB Setup Attempts for Emergency Calls in a Cell.................................................................... 2285
1.34.5 Number of Successful E-RAB Setups for Emergency Calls in a Cell................................................................ 2287
1.34.6 Number of Normal E-RAB Releases Due to Outgoing Handovers for Emergency Calls in a Cell....................2289
1.34.7 Number of Abnormal E-RAB Releases Due to Outgoing Handovers for Emergency Calls in a Cell................2292
1.34.8 Number of Abnormal Releases of E-RABs for Emergency Calls in a Cell........................................................ 2294
1.34.9 Number of Normal E-RAB Releases for Emergency Calls in a Cell.................................................................. 2296
1.34.10 Number of Handover Attempts from E-UTRAN to WCDMA Network for SRVCC Triggered for Emergency
Calls................................................................................................................................................................................ 2298
1.34.11 Number of Handover Executions from E-UTRAN to WCDMA Network for SRVCC Triggered for Emergency
Calls................................................................................................................................................................................ 2300
1.34.12 Number of Successful Handovers from E-UTRAN to WCDMA Network for SRVCC Triggered for Emergency
Calls................................................................................................................................................................................ 2302
1.34.13 Number of Handover Attempts from E-UTRAN to GERAN for SRVCC Triggered for Emergency Calls..... 2304
1.34.14 Number of Handover Executions from E-UTRAN to GERAN for SRVCC Triggered for Emergency Calls.. 2306
1.34.15 Number of Successful Handovers from E-UTRAN to GERAN for SRVCC Triggered for Emergency Calls. 2308
1.34.16 Number of Handover Attempts from E-UTRAN to TD-SCDMA Network for SRVCC Triggered for Emergency
Calls................................................................................................................................................................................ 2310
1.34.17 Number of Handover Executions from E-UTRAN to TD-SCDMA Network for SRVCC Triggered for
Emergency Calls.............................................................................................................................................................2312
1.34.18 Number of Successful Handovers from E-UTRAN to TD-SCDMA Network for SRVCC Triggered for
Emergency Calls.............................................................................................................................................................2314
1.35 UE Context Release Measurement (UeCntx.Rel.Cell)...........................................................................................2315
1.35.1 Number of Abnormal UE Context Releases in a Cell......................................................................................... 2319
1.35.2 Number of Normal UE Context Releases in a Cell............................................................................................. 2322
1.35.3 Number of UE Context Releases due to High Mobility of UEs..........................................................................2324
1.35.4 Number of UE Context Releases During an Inter-RAT Measurement................................................................2325
1.35.5 Number of UE Context Releases Initiated by the eNodeB in a Cell................................................................... 2327
1.35.6 Number of UE Context Releases Initiated by the eNodeB due to Different Causes in a Cell............................ 2328
1.35.7 Number of UE Context Releases Initiated by the MME in a Cell.......................................................................2331
1.35.8 Number of UE Context Releases Initiated by the MME due to a Normal Cause in a Cell.................................2333
1.35.9 Number of Remaining UE Context in a Cell.......................................................................................................2334
1.36 SFN Measurement (SFN.Cell)............................................................................................................................... 2335
1.36.1 Number of Times When the Downlink Attribute of a UE Changes from Independent-scheduling to Joint-
scheduling....................................................................................................................................................................... 2338
1.36.2 Number of Times When the Downlink Attribute of a UE Changes from Joint-scheduling to Independent-
scheduling....................................................................................................................................................................... 2339
1.36.3 Number of Times that the Downlink Target RRU of a UE in an SFN Cell Changes..........................................2340
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xix

1.36.4 Number of Times that the Uplink Attribute of a UE Changes from Independent-Scheduling to Joint-Scheduling
........................................................................................................................................................................................ 2341
1.36.5 Number of Times that the Uplink Attribute of a UE Changes from Joint-Scheduling to Independent-Scheduling
........................................................................................................................................................................................ 2343
1.36.6 Number of Times that the Uplink Target RRU of a UE in an SFN Cell Changes...............................................2344
1.36.7 Average Number of Joint-Scheduling UEs in a Cell........................................................................................... 2345
1.36.8 Average Number of Working RRUs Per Joint-Scheduling UE in a Cell.............................................................2347
1.36.9 Scheduling Duration of UEs with Downlink Services in a Cell..........................................................................2348
1.36.10 Scheduling Duration of UEs with Uplink Services in a Cell............................................................................ 2349
1.36.11 Average Number of Working RRUs that Send PDCCH Data in an SFN Cell.................................................. 2350
1.36.12 Average Number of UEs in an SFN Cell with Uplink Joint Reception Enabled.............................................. 2351
1.36.13 Average Number of PRBs Used by UEs in an SFN Cell with Uplink Joint Reception Enabled...................... 2352
1.37 UE Context Modification Measurement (UeCntx.Mod.Cell)................................................................................ 2353
1.37.1 Number of UE Context Modification Attempts.................................................................................................. 2354
1.37.2 Number of Successful UE Context Modifications.............................................................................................. 2356
1.38 CA Measurement (CA.Cell)................................................................................................................................... 2357
1.38.1 Total Number of Abnormal E-RAB Releases for CA UEs in a Cell...................................................................2363
1.38.2 Total Number of Normal E-RAB Releases for CA UEs in a Cell.......................................................................2374
1.38.3 Number of Handover Attempts for CA UEs in a Cell.........................................................................................2385
1.38.4 Number of Handover Executions for CA UEs in a Cell......................................................................................2389
1.38.5 Number of Successful Handovers for CA UEs in a Cell.....................................................................................2393
1.38.6 Number of SCell Activation Executions for CA UEs Using MCEs................................................................... 2401
1.38.7 Number of Successful SCell Activations for CA UEs Using the MCEs.............................................................2403
1.38.8 Number of SCell Deactivation Executions for CA UEs Using the MCEs.......................................................... 2405
1.38.9 Number of Successful SCell Deactivations for CA UEs Using the MCEs......................................................... 2409
1.38.10 Total Downlink Activation Duration of CA UEs That Use the Local Cell as Their Pcell................................ 2413
1.38.11 Total Downlink Activation Duration of CA UEs That Use the Local Cell as Their Scell................................ 2414
1.38.12 Number of SCell Additions, Removals, and Changes for CA Ues................................................................... 2416
1.38.13 Total Downlink Traffic Volume of MAC TBs in the DL-SCH Transmitted to CA UEs That Use the Local Cell
as Their Scell.................................................................................................................................................................. 2428
1.38.14 Downlink MAC-Layer Traffic Volume for CA UEs That Treat the Local Cell as Their PCell and Have Their
SCell Activated...............................................................................................................................................................2429
1.38.15 Duration of CA UEs with the Local Cell as Their PCell and with All Configured Two SCCs Activated........2431
1.38.16 Downlink MAC Traffic Volume of CA UEs That Treat the Local Cell as Their PCell and Have All SCells
Activated for Downlink Relaxed-Backhaul-based Inter-eNodeB CA............................................................................2432
1.38.17 Downlink MAC Traffic Volume of CA UEs That Treat the Local Cell as Their SCell and Have All SCells
Activated for Downlink Relaxed-Backhaul-based Inter-eNodeB CA............................................................................2434
1.39 RLC Measurement (Traffic.RLC.Cell)...................................................................................................................2435
1.39.1 Number of Bits of Uplink RLC ARQ PDUs Retransmitted by UEs...................................................................2437
1.39.2 Number of Bits of Downlink RLC ARQ PDUs Retransmitted by the eNodeB..................................................2438
1.39.3 Number of Received Uplink RLC ARQ PDUs................................................................................................... 2439
1.39.4 Number of Transmitted Downlink RLC ARQ PDUs..........................................................................................2440
1.39.5 Number of Received Uplink RLC ARQ PDUs Retransmitted by UEs...............................................................2441
1.39.6 Number of Downlink RLC ARQ PDUs Retransmitted by UEs..........................................................................2442
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xx

1.39.7 Number of Downlink RLC PDUs Failed to Be Sent to UEs in AM Mode in a Cell.......................................... 2443
1.39.8 Distribution of Delay of the First RLC SDUs for Non-GBR Bearers.................................................................2444
1.40 Cell Reserved Counter Measurement (Reserve.Cell).............................................................................................2446
1.40.1 L.Reserve.1.......................................................................................................................................................... 2455
1.40.2 L.Reserve.2.......................................................................................................................................................... 2455
1.40.3 L.Reserve.3.......................................................................................................................................................... 2456
1.40.4 L.Reserve.4.......................................................................................................................................................... 2457
1.40.5 L.Reserve.5.......................................................................................................................................................... 2457
1.40.6 L.Reserve.6.......................................................................................................................................................... 2458
1.40.7 L.Reserve.7.......................................................................................................................................................... 2459
1.40.8 L.Reserve.8.......................................................................................................................................................... 2459
1.40.9 L.Reserve.9.......................................................................................................................................................... 2460
1.40.10 L.Reserve.10...................................................................................................................................................... 2461
1.40.11 L.Reserve.11...................................................................................................................................................... 2461
1.40.12 L.Reserve.12...................................................................................................................................................... 2462
1.40.13 L.Reserve.13...................................................................................................................................................... 2463
1.40.14 L.Reserve.14...................................................................................................................................................... 2463
1.40.15 L.Reserve.15...................................................................................................................................................... 2464
1.40.16 L.Reserve.16...................................................................................................................................................... 2465
1.40.17 L.Reserve.17...................................................................................................................................................... 2465
1.40.18 L.Reserve.18...................................................................................................................................................... 2466
1.40.19 L.Reserve.19...................................................................................................................................................... 2467
1.40.20 L.Reserve.20...................................................................................................................................................... 2467
1.40.21 L.Reserve.21...................................................................................................................................................... 2468
1.40.22 L.Reserve.22...................................................................................................................................................... 2469
1.40.23 L.Reserve.23...................................................................................................................................................... 2469
1.40.24 L.Reserve.24...................................................................................................................................................... 2470
1.40.25 L.Reserve.25...................................................................................................................................................... 2471
1.40.26 L.Reserve.26...................................................................................................................................................... 2471
1.40.27 L.Reserve.27...................................................................................................................................................... 2472
1.40.28 L.Reserve.28...................................................................................................................................................... 2473
1.40.29 L.Reserve.29...................................................................................................................................................... 2473
1.40.30 L.Reserve.30...................................................................................................................................................... 2474
1.40.31 L.Reserve.31...................................................................................................................................................... 2475
1.40.32 L.Reserve.32...................................................................................................................................................... 2475
1.40.33 L.Reserve.33...................................................................................................................................................... 2476
1.40.34 L.Reserve.34...................................................................................................................................................... 2477
1.40.35 L.Reserve.35...................................................................................................................................................... 2477
1.40.36 L.Reserve.36...................................................................................................................................................... 2478
1.40.37 L.Reserve.37...................................................................................................................................................... 2479
1.40.38 L.Reserve.38...................................................................................................................................................... 2479
1.40.39 L.Reserve.39...................................................................................................................................................... 2480
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxi

1.40.40 L.Reserve.40...................................................................................................................................................... 2481

1.40.41 L.Reserve.41...................................................................................................................................................... 2481
1.40.42 L.Reserve.42...................................................................................................................................................... 2482
1.40.43 L.Reserve.43...................................................................................................................................................... 2483
1.40.44 L.Reserve.44...................................................................................................................................................... 2483
1.40.45 L.Reserve.45...................................................................................................................................................... 2484
1.40.46 L.Reserve.46...................................................................................................................................................... 2485
1.40.47 L.Reserve.47...................................................................................................................................................... 2485
1.40.48 L.Reserve.48...................................................................................................................................................... 2486
1.40.49 L.Reserve.49...................................................................................................................................................... 2487
1.40.50 L.Reserve.50...................................................................................................................................................... 2487
1.40.51 L.Reserve.51...................................................................................................................................................... 2488
1.40.52 L.Reserve.52...................................................................................................................................................... 2489
1.40.53 L.Reserve.53...................................................................................................................................................... 2489
1.40.54 L.Reserve.54...................................................................................................................................................... 2490
1.40.55 L.Reserve.55...................................................................................................................................................... 2491
1.40.56 L.Reserve.56...................................................................................................................................................... 2491
1.40.57 L.Reserve.57...................................................................................................................................................... 2492
1.40.58 L.Reserve.58...................................................................................................................................................... 2493
1.40.59 L.Reserve.59...................................................................................................................................................... 2493
1.40.60 L.Reserve.60...................................................................................................................................................... 2494
1.40.61 L.Reserve.61...................................................................................................................................................... 2495
1.40.62 L.Reserve.62...................................................................................................................................................... 2495
1.40.63 L.Reserve.63...................................................................................................................................................... 2496
1.40.64 L.Reserve.64...................................................................................................................................................... 2497
1.40.65 L.Reserve.65...................................................................................................................................................... 2497
1.40.66 L.Reserve.66...................................................................................................................................................... 2498
1.40.67 L.Reserve.67...................................................................................................................................................... 2499
1.40.68 L.Reserve.68...................................................................................................................................................... 2499
1.40.69 L.Reserve.69...................................................................................................................................................... 2500
1.40.70 L.Reserve.70...................................................................................................................................................... 2501
1.40.71 L.Reserve.71...................................................................................................................................................... 2501
1.40.72 L.Reserve.72...................................................................................................................................................... 2502
1.40.73 L.Reserve.73...................................................................................................................................................... 2503
1.40.74 L.Reserve.74...................................................................................................................................................... 2503
1.40.75 L.Reserve.75...................................................................................................................................................... 2504
1.40.76 L.Reserve.76...................................................................................................................................................... 2505
1.40.77 L.Reserve.77...................................................................................................................................................... 2505
1.40.78 L.Reserve.78...................................................................................................................................................... 2506
1.40.79 L.Reserve.79...................................................................................................................................................... 2507
1.40.80 L.Reserve.80...................................................................................................................................................... 2507
1.41 Cell Combination Measurement (CellComb.Cell)................................................................................................. 2508
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxii

1.41.1 Number of Downlink Joint-scheduling UEs in a Combination Cell................................................................... 2510

1.41.2 Average Number of Work Physical Cells of Downlink Joint-scheduling UEs in a Combination Cell............... 2511
1.41.3 Number of Times an Independent-scheduling UE Becomes a Joint-scheduling UE in Downlink in a Combination
Cell..................................................................................................................................................................................2512
1.41.4 Number of Times a Joint-scheduling UE Becomes an Independent-scheduling UE in Downlink in a Combination
Cell..................................................................................................................................................................................2513
1.41.5 Number of Times the Downlink Target Physical Cell of a UE in a Combination Cell Changes in a Combination
Cell..................................................................................................................................................................................2514
1.41.6 Number of Uplink Joint-scheduling UEs in a Combination Cell........................................................................ 2515
1.41.7 Average Number of Work Physical Cells of Uplink Joint-scheduling UEs in a Combination Cell in a
Combination Cell............................................................................................................................................................2516
1.41.8 Number of Times an Independent-scheduling UE Becomes a Joint-scheduling UE in Uplink in a Combination
cell.................................................................................................................................................................................. 2517
1.41.9 Number of Times a Joint-scheduling UE Becomes an Independent-scheduling UE in Uplink in a Combination
Cell..................................................................................................................................................................................2518
1.41.10 Number of Times the Uplink Target Physical Cell of a UE in a Combination Cell Changes in a Combination
Cell..................................................................................................................................................................................2519
1.42 MR Measurement (ChMeas.MeasRpt.Cell)........................................................................................................... 2519
1.42.1 Number of Measurement Control Messages Sent by the eNodeB in a Cell........................................................2521
1.43 UE Context Setup Measurement (UeCntx.Est.Cell).............................................................................................. 2523
1.43.1 Number of UE Context Setup Attempts in a Cell............................................................................................... 2525
1.43.2 Number of Successful UE Context Setups in a Cell........................................................................................... 2526
1.44 UE Context Setup Failure Measurement (UeCntx.EstFail.Cell)............................................................................ 2528
1.44.1 Number of UE Context Setup Failures for Different Causes in a Cell ...............................................................2529
1.45 Incoming Intra-RAT Handover Measurement over X2 (HO.eRAN.X2In.Cell).................................................... 2534
1.45.1 Number of X2-based Incoming Handover Attempts in a Cell............................................................................ 2538
1.45.2 Number of X2-based Incoming Handover Executions in a Cell......................................................................... 2541
1.45.3 Number of Successful X2-based Incoming Handovers in a Cell........................................................................ 2544
1.45.4 Number of X2-based Incoming Handover Failures for Different Causes in a Cell............................................ 2548
1.45.5 Number of Successful X2-based Intra-duplex-mode Incoming Handovers Where RRC Connections Are
Reestablished to the Target Cell for UEs in a Cell......................................................................................................... 2551
1.46 Throughput Distribution Measurement (Traffic.Thruput.PDF.Cell)...................................................................... 2553
1.46.1 Distribution of the Downlink Throughput in a Cell............................................................................................ 2570
1.46.2 Distribution of the Uplink Throughput in a Cell................................................................................................. 2608
1.47 Packet Size Distribution Measurement (Traffic.Packet.PDF.Cell).........................................................................2613
1.47.1 Downlink PDCP SDU Size Distribution............................................................................................................. 2638
1.47.2 Uplink PDCP SDU Size Distribution.................................................................................................................. 2670
1.48 Cell MBMS Measurement (MBMS.Cell).............................................................................................................. 2702
1.48.1 Number of Bits for MBMS Services Scheduled in a Cell................................................................................... 2703
1.48.2 Number of Bits for MBMS Services Received in a Cell.....................................................................................2704
1.48.3 Number of SYNC PDUs for MBMS Services Received in a Cell...................................................................... 2705
1.48.4 Number of SYNC PDUs for MBMS Services Discarded in a Cell.....................................................................2706
1.49 PCell CQI Measurement (ChMeas.CQI.CA.PCell)............................................................................................... 2707
1.49.1 Number of Periodic Wideband CQI Reports in Single-Codeword Transmission Sent by CA UEs that Use the
Local Cell as Their Pcell................................................................................................................................................ 2730
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxiii

1.49.2 Number of Aperiodic Wideband CQI Reports in Single-Codeword Transmission Sent by CA UEs that Use the
Local Cell as Their Pcell................................................................................................................................................ 2739
1.49.3 Number of Periodic Wideband CQI Reports for Codeword 0 in Dual-Codeword Transmission Sent by CA UEs
that Use the Local Cell as Their Pcell............................................................................................................................ 2748
1.49.4 Number of Aperiodic Wideband CQI Reports for Codeword 0 in Dual-Codeword Transmission Sent by CA UEs
1.50 SCell CQI Measurement (ChMeas.CQI.CA.SCell)............................................................................................... 2784
1.50.1 Number of Periodic Wideband CQI Reports in Single-Codeword Transmission Sent by CA UEs that Use the
Local Cell as Their Scell................................................................................................................................................ 2807
1.50.2 Number of Aperiodic Wideband CQI Reports in Single-Codeword Transmission Sent by CA UEs that Use the
Local Cell as Their Scell................................................................................................................................................ 2816
that Use the Local Cell as Their Scell............................................................................................................................ 2825
1.51 PCell MCS Measurement (ChMeas.MCS.CA.PCell)............................................................................................ 2861
1.51.1 Number of Times a Specific MCS Index is Used for Scheduling on the PDSCH for CA UEs that Use the Local
Cell as Their Pcell...........................................................................................................................................................2877
1.51.2 Number of Times a Specific MCS Index Is Used for Scheduling on the PUSCH for CA UEs that Are in the
Uplink CA State (Each with at Least One Uplink SCC Configured) and Treat the Local Cell as Their Pcell.............. 2891
1.51.3 Number of Used PRBs When a Specific MCS Index Is Used for Scheduling CA UEs that Are in the Uplink CA
State (Each with at Least One Uplink SCC Configured) and Treat the Local Cell as Their Pcell.................................2905
1.52 SCell MCS Measurement (ChMeas.MCS.CA.SCell)............................................................................................ 2920
1.52.1 Number of Times a Specific MCS Index is Used for Scheduling on the PDSCH for CA UEs that Use the Local
Cell as Their Scell...........................................................................................................................................................2936
1.52.2 Number of Times a Specific MCS Index Is Used for Scheduling on the PUSCH for CA UEs that Treat the Local
Cell as Their SCell..........................................................................................................................................................2950
1.52.3 Number of Used PRBs When a Specific MCS Index Is Used for Scheduling for CA UEs that Treat the Local Cell
as Their SCell................................................................................................................................................................. 2964
1.53 CA Cell MAC Measurement (Traffic.MAC.CA.Cell)........................................................................................... 2978
1.53.1 Number of TBs Initially Transmitted on the Downlink SCH for CA UEs that Use the Local Cell as Their Pcell
........................................................................................................................................................................................ 2986
1.53.2 Number of TBs Initially Transmitted on the Downlink SCH for CA UEs that Use the Local Cell as Their Scell
........................................................................................................................................................................................ 2988
1.53.3 Number of Downlink Error TBs After Initial Transmission for CA UEs that Use the Local Cell as Their Pcell
........................................................................................................................................................................................ 2990
1.53.4 Number of Downlink Error TBs After Initial Transmission for CA UEs that Use the Local Cell as Their Scell
........................................................................................................................................................................................ 2992
1.53.5 Number of Downlink Error TBs After the Maximum number of Transmissions for CA UEs that Use the Local
Cell as Their Pcell...........................................................................................................................................................2995
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxiv

1.53.6 Number of Downlink Error TBs After the Maximum number of Transmissions for CA UEs that Use the Local
Cell as Their Scell...........................................................................................................................................................2997
1.53.7 Uplink MAC-layer Traffic Volume of CA UEs in the Uplink CA State that Treat the Local Cell as Their PCell
and Have Their SCell Activated..................................................................................................................................... 2999
1.53.8 Uplink MAC-layer Traffic Volume of CA UEs in the Uplink CA State that Treat the Local Cell as Their SCell
........................................................................................................................................................................................ 3000
1.53.9 Number of TBs Initially Transmitted on the Uplink SCH for CA UEs that Are in the Uplink CA State (Each with
at Least One Uplink SCC Configured) and Treat the Local Cell as Their Pcell............................................................ 3001
1.53.10 Number of TBs Initially Transmitted on the Uplink SCH for CA UEs that Treat the Local Cell as Their SCell
........................................................................................................................................................................................ 3003
1.53.11 Number of Uplink Error TBs After Initial Transmission for CA UEs that Are in the Uplink CA State (Each with
at Least One Uplink SCC Configured) and Treat the Local Cell as Their Pcell............................................................ 3006
1.53.12 Number of Uplink Error TBs After Initial Transmission for CA UEs that Treat the Local Cell as Their SCell
........................................................................................................................................................................................ 3008
1.53.13 Number of Uplink Error TBs After the Maximum Number of Retransmissions Is Reached for CA UEs that Are
in the Uplink CA State (Each with at Least One Uplink SCC Configured) and Treat the Local Cell as Their Pcell.... 3010
1.53.14 Number of Uplink Error TBs After the Maximum Number of Retransmissions Is Reached for CA UEs that
Treat the Local Cell as Their SCell................................................................................................................................ 3012
1.53.15 Number of TBs to Which CA UEs That Treat the Local Cell as Their PCell in the Downlink CA State Respond
with NACKs................................................................................................................................................................... 3014
1.53.16 Number of TBs to Which CA UEs That Treat the Local Cell as Their SCell in the Downlink CA State Respond
with NACKs................................................................................................................................................................... 3017
1.54 PDCP Measurement (Traffic.PDCP.Cell)...............................................................................................................3018
1.54.1 Number of Downlink PDCP SDUs Discarded for Services Carried on DRBs................................................... 3024
1.54.2 Downlink ROHC Compression Rate of Headers................................................................................................ 3030
1.54.3 Downlink ROHC Compression Rate...................................................................................................................3031
1.54.4 Decompression Failure Rate of Uplink PDCP SDUs After the ROHC.............................................................. 3032
1.54.5 Number of Downlink PDCP SDUs Transmitted for Services Carried on DRBs................................................ 3033
1.54.6 Uplink ROHC Compression Rate of Headers..................................................................................................... 3038
1.54.7 Uplink ROHC Compression Rate........................................................................................................................3039
1.54.8 Number of PDCP-layer Signaling SDUs Sent in the Downlink or Received in the Uplink............................... 3040
1.54.9 Number of Bytes of SDUs that a Cell Receives from or Sends to the S-GW..................................................... 3041
1.54.10 Number of Bytes of SDUs Transmitted During Inter-eNodeB Handovers....................................................... 3043
1.54.11 Number of Downlink PDCP SDUs Sent to CA UEs in a Cell.......................................................................... 3044
1.54.12 Number of Discarded Downlink PDCP SDUs for UEs in the Downlink CA State.......................................... 3047
1.55 MIMO Measurement (ChMeas.MIMO.Cell)......................................................................................................... 3049
1.55.1 Number of Used Downlink PRBs in MIMO Mode.............................................................................................3054
1.55.2 Number of RBs That Are Successfully Paired for VMIMO UEs in a Cell.........................................................3058
1.55.3 Number of RBs That Can Be Paired for VMIMO UEs in a Cell........................................................................ 3059
1.55.4 Number of RBs for MIMO UEs That Are Successfully Paired for MUBF in a Cell..........................................3060
1.55.5 Number of RBs for MIMO UEs That Can Be Paired for MUBF in a Cell......................................................... 3061
1.55.6 Number of Used Downlink PRBs in BF Mode................................................................................................... 3062
1.55.7 Number of TBs Transmitted in Downlink MIMO Mode.................................................................................... 3063
1.55.8 Number of TBs Transmitted in Downlink BF Mode...........................................................................................3071
1.55.9 Numbers of Bits Transmitted in the Downlink in Different Transmission Modes..............................................3072
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxv

1.55.10 Numbers of Used Downlink PRBs in Different Transmission Modes.............................................................. 3075

1.56 Service Setup Measurement (Traffic.Service.AttEst.Cell)..................................................................................... 3077
1.56.1 Average Access Delay for Downlink Data Services Successfully Initiated by Idle-Mode Ues..........................3079
1.56.2 Access Delay Distribution for Downlink Data Services Successfully Initiated by Idle-Mode Ues....................3080
1.56.3 Average Access Delay for Uplink Data Services Successfully Initiated by Idle-Mode UEs in the Cell............ 3082
1.56.4 Access Delay Distribution for Uplink Data Services Successfully Initiated by Idle-Mode Ues.........................3083
1.57 UE Traffic Rate Distribution Measurement (Traffic.User.Thruput.Cell)............................................................... 3084
1.57.1 Downlink PS Service Traffic Distribution...........................................................................................................3087
1.57.2 Downlink PS Service Throughput Distribution...................................................................................................3089
1.58 Throughput and Data Volume Measurement per Path Loss Range (PL.Traffic.Thruput.Cell).............................. 3091
1.58.1 Distribution of Total Uplink Traffic Volume of PDCP PDUs for UEs with Different Path Loss Ranges.......... 3098
1.58.2 Distribution of Data Transmission Duration of Uplink PDCP PDUs (Excluding Small Packets) for UEs with
Different Path Loss Ranges............................................................................................................................................ 3104
1.58.3 Distribution of Traffic Volume of Uplink Small Packets at the PDCP Layer for UEs With Different Path Loss
Ranges.............................................................................................................................................................................3111
1.58.4 Distribution of UEs that Are Performing Services with Different Path Loss Ranges......................................... 3117
1.59 Resource Optimization Measurement (ResOpt.Cell)............................................................................................. 3122
1.59.1 Ratio of Times the Number of Scheduled UEs per TTI in the Downlink Is Limited in a Cell........................... 3124
1.59.2 Ratio of Remaining PDSCH RBs When the Number of Scheduled UEs per TTI in the Downlink Is Limited in a
Cell..................................................................................................................................................................................3125
1.59.3 Ratio of Remaining Downlink PDSCH RBs When CCE Resources Are Limited............................................. 3126
1.59.4 Ratio of Times the Number of Scheduled UEs per TTI in the Uplink Is Limited in a Cell................................ 3128
1.59.5 Ratio of Remaining PUSCH RBs When the Number of Scheduled UEs per TTI in the Uplink Is Limited in a Cell
........................................................................................................................................................................................ 3129
1.59.6 Ratio of Remaining Uplink PUSCH RBs When CCE Resources Are Limited.................................................. 3131
1.59.7 Ratio of Remaining CCEs When the Number of Scheduled UEs per TTI Is Limited in a Cell..........................3132
1.60 Cell Relay UE Quantity Measurement (Traffic.User.Relay.Cell)...........................................................................3133
1.60.1 Number of Relay UEs in a Cell........................................................................................................................... 3134
1.60.2 Number of Active Relay Users in a Cell............................................................................................................. 3135
1.61 Relay Throughput or Throughput Rate Measurement (Traffic.Thruput.Relay.Cell)..............................................3136
1.61.1 Total Downlink PDCP Throughput of Relay Users............................................................................................ 3137
1.61.2 Duration of PDCP Sending Downlink Data of Relay Users............................................................................... 3138
1.61.3 Total Uplink PDCP Throughput of Relay Users................................................................................................. 3139
1.61.4 Duration of PDCP Receiving Uplink Data of Relay Users................................................................................. 3140
1.62 Relay Packet Measurement (Traffic.Packet.Relay.Cell).........................................................................................3141
1.62.1 Total Processing Delay of Downlink PDCP SDUs Transmitted by Relay Users in a Cell................................. 3142
1.62.2 Number of Downlink PDCP SDUs Successfully Transmitted by Relay Users in a Cell....................................3143
1.62.3 Number of Uplink PDCP SDUs Discarded by Relay Users in a Cell................................................................. 3144
1.62.4 Number of Uplink PDCP PDUs Expected to Be Received by Relay Users in a Cell.........................................3145
1.63 Relay PRB Measurement (ChMeas.PRB.Relay.Cell)............................................................................................ 3146
1.63.1 Average Number of Downlink PRBs Used by Relay Users................................................................................3147
1.63.2 Average Number of Uplink PRBs Used by Relay Users.....................................................................................3148
1.64 Relay RRC Connection Reestablishment Measurement (RRC.ReEst.Relay.Cell)................................................ 3149
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxvi

1.64.1 Number of RRC Connection Reestablishment Requests of Relay Users in a Cell............................................. 3151
1.64.2 Number of Successful RRC Connection Reestablishment Times of Relay Users in a Cell................................3152
1.65 Relay Users E-RAB Releases Measurement (E-RAB.Rel.Relay.Cell).................................................................. 3154
1.65.1 Number of Abnormal E-RAB Releases for Relay Users in a Cell...................................................................... 3155
1.65.2 Cause of Abnormal E-RAB Releases for Relay Users in a Cell......................................................................... 3157
1.66 Differentiated Service Throughput Measurement (Traffic.Thruput.Diff.Cell).......................................................3159
1.66.1 Downlink Data Transmission Duration of Services per Priority.........................................................................3161
1.66.2 Downlink Traffic Volume of Services per Priority..............................................................................................3165
1.67 E-RAB Data Volume Distribution Measurement (Traffic.Volume.PDF.Cell)........................................................3167
1.67.1 Distribution of Downlink Traffic Volume of E-RABs........................................................................................ 3174
1.67.2 Distribution of Uplink Traffic Volume of E-RABs............................................................................................. 3179
1.68 Inter-RAT MRO Measurement (MroMeas.InterRat.Cell)...................................................................................... 3184
1.68.1 Number of Delayed Inter-RAT Handovers..........................................................................................................3187
1.68.2 Number of Unnecessary Inter-RAT Handovers...................................................................................................3190
1.68.3 Number of Ping-Pong Inter-RAT Handovers...................................................................................................... 3193
1.68.4 Number of Premature Inter-RAT Handovers.......................................................................................................3195
2 Measurement of eNodeB Performance (eNodeB)............................................................. 3198

2.1 eNodeB LCS Measurement (LCS.ENODEB)..........................................................................................................3200
2.1.1 Number of OTDOA Measurement Attempts Received by an eNodeB.................................................................3200
2.1.2 Number of Successful Responses Sent by an eNodeB to OTDOA Measurement Requests.................................3201
2.2 eNodeB User Quantity Measurement (Traffic.User.eNodeB)..................................................................................3202
2.2.1 Maximum Number of Users Under an eNodeB.................................................................................................... 3203
2.2.2 Maximum Number of UL-Sync UEs in an eNodeB..............................................................................................3204
2.3 eNodeB RIM Measurement (RIM.eNodeB)............................................................................................................ 3205
2.3.1 Number of times the eNodeB sends a system information request to a WCDMA network................................. 3207
2.3.2 Number of times the eNodeB receives a system information response from a WCDMA network......................3209
2.3.3 Number of times the eNodeB receives a system information update from a WCDMA network......................... 3211
2.3.4 Number of times the eNodeB sends a load information request to a WCDMA network..................................... 3213
2.3.5 Number of times the eNodeB receives a load information response from a WCDMA network.......................... 3215
2.3.6 Number of times the eNodeB receives a load information update from a WCDMA network............................. 3217
2.3.7 Number of times the eNodeB receives a load information request from a WCDMA network.............................3219
2.3.8 Number of times the eNodeB sends a load information response to a WCDMA network................................... 3221
2.3.9 Number of times the eNodeB sends a load information update to a WCDMA network...................................... 3223
2.3.10 Number of times the eNodeB receives a load information update acknowledgment from a WCDMA network
........................................................................................................................................................................................ 3225
2.3.11 Number of times the eNodeB sends a load information request to a GERAN....................................................3227
2.3.12 Number of times the eNodeB receives a load information response from a GERAN........................................ 3229
2.3.13 Number of times the eNodeB sends a system information request to a GERAN............................................... 3231
2.3.14 Number of times the eNodeB receives a system information response from a GERAN.................................... 3233
2.3.15 Number of times the eNodeB receives a system information update from a GERAN....................................... 3235
2.4 eNodeB Throughput Measurement (Traffic.Thruput.eNodeB)................................................................................ 3236
2.4.1 Maximum Traffic Volume for PDCP SDUs in an eNodeB................................................................................... 3237
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxvii

2.5 eNodeB SCTP Measurement (SCTP.eNodeB)......................................................................................................... 3239

2.5.1 Number of Times of Downlink SCTP Congestion Control...................................................................................3240
2.5.2 Number of UE Context Releases Because of S1 SCTP Link Disconnection........................................................3241
2.6 MBMS Session Measurement (MBMS.eNodeB).................................................................................................... 3242
2.6.1 Number of MBMS Session Setup Attempts in an eNodeB...................................................................................3243
2.6.2 Number of Successfully Set up MBMS Sessions in an eNodeB...........................................................................3244
2.6.3 Number of MBMS Session Setup Failures............................................................................................................3246
2.6.4 Number of MBMS Session Stop Attempts in an eNodeB.....................................................................................3248
2.6.5 Number of MBMS Sessions in an eNodeB........................................................................................................... 3249
2.7 eNodeB Reserved Counter Measurement (Reserve.eNodeB).................................................................................. 3250
2.7.1 L.eNodeB.Reserve.1..............................................................................................................................................3251
2.7.2 L.eNodeB.Reserve.2..............................................................................................................................................3252
2.7.3 L.eNodeB.Reserve.3..............................................................................................................................................3253
2.7.4 L.eNodeB.Reserve.4..............................................................................................................................................3253
2.7.5 L.eNodeB.Reserve.5..............................................................................................................................................3254
2.7.6 L.eNodeB.Reserve.6..............................................................................................................................................3255
2.7.7 L.eNodeB.Reserve.7..............................................................................................................................................3255
2.7.8 L.eNodeB.Reserve.8..............................................................................................................................................3256
2.7.9 L.eNodeB.Reserve.9..............................................................................................................................................3257
2.7.10 L.eNodeB.Reserve.10..........................................................................................................................................3257
2.8 eNodeB Transmission Interface Measurement (Traffic.TRPIP.eNodeB).................................................................3258
2.8.1 Number of Bytes of the IP-layer Data Transmitted over the eNodeB Transmission Interfaces............................3260
2.8.2 Number of the IP-layer Packets Transmitted over the eNodeB Transmission Interfaces..................................... 3262
2.8.3 IP-layer Data Rate over the eNodeB Transmission Interfaces.............................................................................. 3263
2.9 EPC-Inside User Quantity Measurement (EPCInside.User).................................................................................... 3266
2.9.1 Maximum number of users attached to the EPC-inside........................................................................................ 3267
2.9.2 Average Number of Users Attached to the EPC-Inside.........................................................................................3268
2.9.3 Average Number of Dual-PDN Connection-enabled Users Attached to the EPC-Inside..................................... 3269
2.10 EPC-Inside Attach Measurement (EPCInside.Attach)........................................................................................... 3269
2.10.1 Number of Attachment Requests of UEs in the EPC-Inside............................................................................... 3271
2.10.2 Number of Successful Attachments in the EPC-Inside....................................................................................... 3272
2.10.3 Number of Attachment Failures in the EPC-Inside.............................................................................................3273
2.11 EPC-Inside Authentication Measurement (EPCInside.Authentication).................................................................3275
2.11.1 Number of authentication requests on the EPC inside........................................................................................ 3276
2.11.2 Number of successful authentication times on the EPC inside........................................................................... 3277
2.12 eNodeB Algorithm Measurement (Algo.eNodeB)................................................................................................. 3278
2.12.1 Number of Times an eNodeB Becomes Unavailable.......................................................................................... 3279
2.12.2 Duration of eNodeB Unavailability.....................................................................................................................3280
3 Measurement of S1 Link Performance (Sig.S1)................................................................. 3282

3.1 S1 Link Measurement (Sig.S1)................................................................................................................................ 3283
3.1.1 Number of S1 Interface Setups..............................................................................................................................3284
3.1.2 Duration of S1 Link Unavailability....................................................................................................................... 3286
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxviii

4 Measurement of X2 Link Performance (Sig.X2)................................................................ 3288

4.1 X2 Link Measurement (Sig.X2)............................................................................................................................... 3289
4.1.1 Number of X2 Link Setup Attempts......................................................................................................................3290
4.1.2 Number of Successful X2 Link Setups..................................................................................................................3292
4.1.3 Duration of X2 Link Unavailability...................................................................................................................... 3294
5 Measurement of Intra-RAT Inter-Cell Handover Performance (NCell).......................3296

5.1 LTE Cell-to-LTE Cell Outgoing Handover Measurement (HO.NCell.Cell)............................................................ 3297
5.1.1 Number of Outgoing Handover Attempts Between Two Specific Cells...............................................................3302
5.1.2 Number of Outgoing Handover Executions Between Two Specific Cells............................................................3305
5.1.3 Number of Successful Outgoing Handovers Between Two Specific Cells...........................................................3309
5.1.4 Number of Ping-Pong Handovers Between Two Specific Cells........................................................................... 3318
5.1.5 Number of Delayed Intra-RAT Handovers between two specific cells.................................................................3325
5.1.6 Number of Premature Intra-RAT Handovers between two specific cells..............................................................3327
5.1.7 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During Outgoing Handover
Executions Between Two Specific Cells........................................................................................................................ 3331
5.1.8 Number of Successful Outgoing Handovers Between Two Specific Cells Where RRC Connections Are
Reestablished to the Source Cell for UEs in a Cell........................................................................................................ 3333
5.1.9 Number of intra-RAT handovers to a wrong cell between two specific cells....................................................... 3336
5.1.10 Reasons of Outgoing Handover Failures Between Two Specific Cells.............................................................. 3339
5.2 LTE Cell-to-LTE Cell Incoming Handover Measurement (HO.NCell.In.Cell)....................................................... 3343
5.2.1 Number of Successful Incoming Handovers Between Two Specific Cells Where RRC Connections Are
Reestablished to the Target Cell for UEs in a Cell......................................................................................................... 3345
5.2.2 Number of Incoming Handover Attempts Between Two Cells.............................................................................3349
5.2.3 Number of Incoming Handovers Performed Between Two Cells......................................................................... 3351
5.2.4 Number of Successful Incoming Handovers Between Two Cells.........................................................................3354
6 Measurement of CNOperator Performance (Cell.Operator)...........................................3359

6.1 E-RAB Setup Measurement per CNOperator (E-RAB.Est.Cell.Operator)..............................................................3361
6.1.1 Number of E-RAB Setup Attempts for a Specific Operator in a Cell...................................................................3367
6.1.2 Number of Successful E-RAB Setups for a Specific Operator in a Cell...............................................................3377
6.1.3 Number of E-RAB Setup Attempts for Incoming Handovers for a Specific Operator in a Cell.......................... 3386
6.1.4 Number of Successful E-RAB Setups for Incoming Handovers for a Specific Operator in a Cell...................... 3391
6.2 E-RAB Release Measurement per CNOperator (E-RAB.Rel.Cell.Operator).......................................................... 3399
6.2.1 Number of Abnormal E-RAB Releases for a Specific Operator...........................................................................3423
6.2.2 Number of Normal E-RAB Releases for a Specific Operator...............................................................................3432
6.2.3 Number of Normal E-RAB Releases for Outgoing Handovers for a Specific Operator in a Cell........................ 3441
6.2.4 Number of Abnormal E-RAB Releases for Outgoing Handovers for a Specific Operator...................................3451
6.2.5 Number of Abnormal E-RAB Releases for Different Causes for a specific operator in a cell............................. 3461
6.2.6 Number of E-RAB Releases Initiated by the eNodeB Because of the S1 RESET for a Specific Operator..........3489
6.2.7 Number of Abnormal E-RAB Releases for Other Causes for a Specified Operator.............................................3498
6.3 Throughput and Data Volume Measurement per CNOperator (Traffic.Thruput.Cell.Operator)..............................3504
6.3.1 Uplink Traffic Volume for PDCP PDUs for a specified operator......................................................................... 3518
6.3.2 Receive Duration of Uplink PDCP PDUs for a specific Operator in a Cell..........................................................3525
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxix

6.3.3 Downlink Traffic Volume for PDCP SDUs for a Specific Operator in a Cell...................................................... 3532
6.3.4 Transmit Duration of Downlink PDCP SDUs for a Specific Operator in a Cell...................................................3539
6.3.5 Downlink Traffic Volume Sent in the Last TTI Before the Buffer Is empty for a Specific Operator................... 3546
6.3.6 Data Transmit Duration Except the Last TTI Before the Downlink Buffer Is Empty for a Specific Operator.....3554
6.3.7 Traffic Volume of Uplink PDCP PDUs Sent in the Last TTI Before the UE Buffer is Empty for a Specific
Operator.......................................................................................................................................................................... 3562
6.3.8 Uplink Data Transmit Duration Except the Last TTI Before the UE Buffer is Empty for a Specific Operator... 3563
6.3.9 Uplink Traffic Volume of PDCP PDUs Scheduled for Small Packets for a Specific Operator............................ 3565
6.3.10 Uplink Data Transmission Duration Except that for Small Packets for a Specific Operator..............................3566
6.3.11 Total Duration of Data Transmission for a Specific Operator in a cell (with the Sampling Period of 1
Millisecond)....................................................................................................................................................................3568
6.3.12 Total Duration of UE Data Transmission for a Specific Operator in a Cell (with the Precision of 100 ms)...... 3570
6.3.13 Total Duration of Data Transmission for a Specific Operator in a Cell (with the Precision of 100 ms).............3571
6.4 Cell User Quantity Measurement per CNOperator (Traffic.User.Cell.Operator).....................................................3579
6.4.1 Number of Users for a Specific Operator in a Cell............................................................................................... 3581
6.4.2 Number of UL Synchronized Users for a Specific Operator in a Cell.................................................................. 3583
6.4.3 Number of VoIP UEs of a Specific Operator in a Cell.......................................................................................... 3584
6.4.4 Number of times the licensed number of UEs is limited for a specific operator...................................................3586
6.4.5 Number of successful preemptions triggered by the limitation of the licensed number of UEs for a specific
operator........................................................................................................................................................................... 3588
6.5 PRB Measurement per CNOperator (Traffic.RB.Cell.Operator)............................................................................. 3590
6.5.1 Average Number of PDSCH PRBs Used by a Specific Operator......................................................................... 3591
6.5.2 Average Number of PUSCH PRBs Used by a Specific Operator......................................................................... 3593
6.6 Outgoing Intra-RAT Handover Measurement per CNOperator (HO.eRAN.Out.Cell.Operator).............................3595
6.6.1 Number of Intra-eNodeB Outgoing Handover Attempts for a Specific Operator.................................................3607
6.6.2 Number of Intra-eNodeB Outgoing Handover Executions for a Specific Operator............................................. 3610
6.6.3 Number of Successful Intra-eNodeB Outgoing Handovers for a Specific Operator.............................................3614
6.6.4 Number of Inter-eNodeB Outgoing Handover Attempts for a specified operator................................................ 3618
6.6.5 Number of Inter-eNodeB Outgoing Handover Executions for a Specific Operator............................................. 3622
6.6.6 Number of Successful Inter-eNodeB Outgoing Handovers for a specified operator............................................ 3626
6.6.7 Number of X2-based Outgoing Handover Attempts for a Specific Operator....................................................... 3634
6.6.8 Number of X2-based Outgoing Handover Executions for a Specific Operator.................................................... 3638
6.6.9 Number of Successful X2-based Outgoing Handovers for a specific operator.....................................................3642
6.6.10 Number of Outgoing Blind Handover Attempts for a Specific Operator............................................................3647
6.6.11 Number of Outgoing Blind Handover Executions for a Specific Operator.........................................................3651
6.6.12 Number of Successful Outgoing Blind Handovers for a Specific Operator........................................................3654
6.6.13 Number of Load-based Inter-Frequency Handover Preparation Attempts for a Specific Operator....................3663
6.6.14 Number of Load-based Inter-Frequency Handover Executions for a Specific Operator.................................... 3666
6.6.15 Number of Successful Load-based Inter-Frequency Handovers for a Specific Operator................................... 3669
6.6.16 Number of Inter-eNodeB Outgoing Handover Attempts for UEs Performing Voice Services for a Specific
Operator in a Cell........................................................................................................................................................... 3676
6.6.17 Number of Inter-eNodeB Outgoing Handovers Executions for UEs Performing Voice Services for a Specific
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxx

6.6.18 Number of Successful Inter-eNodeB Outgoing Handovers for UEs Performing Voice Services for a Specific
6.6.19 Number of Intra-eNodeB Outgoing Handover Attempts for UEs Performing Voice Services for a Specific
6.6.20 Number of Intra-eNodeB Outgoing Handovers Executions for UEs Performing Voice Services for a Specific
6.6.21 Number of Successful Intra-eNodeB Outgoing Handovers for UEs Performing Voice Services for a Specific
6.7 Outgoing Inter-RAT Handover Measurement per CNOperator (HO.IRAT.Out.Cell.Operator).............................. 3705
6.7.1 Number of Inter-RAT Handover Attempts from E-UTRAN to WCDMA Network for a Specific Operator....... 3714
6.7.2 Number of Inter-RAT Handover Executions from E-UTRAN to WCDMA Network for a Specific Operator.... 3716
6.7.3 Number of Successful Inter-RAT Handovers from E-UTRAN to WCDMA Network for a Specific Operator... 3718
6.7.4 Number of Inter-RAT Handover Attempts from E-UTRAN to GERAN for a Specific Operator........................ 3720
6.7.5 Number of Inter-RAT Handover Executions from E-UTRAN to GERAN for a Specific Operator..................... 3722
6.7.6 Number of Successful Inter-RAT Handovers from E-UTRAN to GERAN for a Specific Operator.................... 3724
6.7.7 Number of Inter-RAT Blind Handover Attempts from E-UTRAN to Another System for a Specific Operator.. 3726
6.7.8 Number of Inter-RAT Blind Handover Executions from E-UTRAN to Another System for a Specific Operator
........................................................................................................................................................................................ 3729
6.7.9 Number of Successful Inter-RAT Blind Handovers from E-UTRAN to Another System for a Specific Operator
........................................................................................................................................................................................ 3732
6.7.10 Number of Inter-RAT Redirections from E-UTRAN to Another System for a Specific Operator..................... 3735
6.7.11 Number of Inter-RAT Handover Initiation Failures Because the Adjacent Cell Is Not on the NRT of the Source
Cell for a Specific Operator............................................................................................................................................3738
6.7.12 Number of Indicators for CSFB to Another System for a Specific Operator......................................................3742
6.7.13 Number of CSFB Responses to MMEs for a Specific Operator......................................................................... 3745
6.7.14 Number of Times of CSFB to Another System...................................................................................................3747
6.7.15 Number of SRVCC-based Outgoing Handover Attempts from E-UTRAN to WCDMA Network for a Specific
Operator.......................................................................................................................................................................... 3755
6.7.16 Number of SRVCC-based Outgoing Handover Executions from E-UTRAN to WCDMA Network for a Specific
Operator.......................................................................................................................................................................... 3757
6.7.17 Number of Successful Outgoing Handovers from E-UTRAN to WCDMA Network for a Specified Operator 3759
6.7.18 Number of SRVCC-based Outgoing Handover Attempts from E-UTRAN to GERAN for a Specific Operator
........................................................................................................................................................................................ 3761
6.7.19 Number of SRVCC-based Outgoing Handover Executions from E-UTRAN to GERAN for a Specific Operator
........................................................................................................................................................................................ 3763
6.7.20 Number of Successful SRVCC-based Outgoing Handovers from E-UTRAN to GERAN for a Specific Operator
........................................................................................................................................................................................ 3765
Handover Executions for a Specific Operator................................................................................................................ 3767
Handover Executions for SRVCC for a Specific Operator............................................................................................ 3770
6.7.23 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During CSFB-based Inter-
RAT Handover Executions for a Specific Operator....................................................................................................... 3773
6.8 E-RAB Establish Failure Measurement per CNOperator (E-RAB.EstFail.Cell.Operator)......................................3774
6.8.1 Number of E-RAB Setup Failures for Different Causes for a Specific Operator in a Cell................................... 3787
6.8.2 Number of E-RAB Setup Failures for Other Causes in a Cell for a Specific Operator........................................ 3822
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxxi

6.9 Throughput Distribution Measurement per CNOperator (Traffic.Thruput.PDF.Cell.Operator).............................. 3827

6.9.1 Distribution of the Downlink Throughput for a Specific Operator in a Cell.........................................................3848
6.9.2 Distribution of the Uplink Throughput in a Cell for a Specific Operator............................................................. 3919
6.10 Paging Measurement per CNOperator (Paging.Cell.Operator)..............................................................................3927
6.10.1 Number of Received Paging Messages over the S1 Interface for a Specific Operator in a Cell.........................3928
6.11 Voice Quality Measurement per CNOperator (VoiceQuality.Cell.Operator)......................................................... 3929
6.11.1 Uplink and Downlink Voice Quality for a Specific Operator..............................................................................3933
6.12 Packet Measurement per CNOperator (Traffic.Packet.Cell.Operator)...................................................................3944
6.12.1 Total Number of Discarded Uplink PDCP SDUs for DRB Services for a Specific Operator in a Cell.............. 3947
6.12.2 Total Number of Expected Uplink Data Packets for DRB Services for a Specific Operator in a Cell............... 3949
6.12.3 Number of Successfully Transmitted Downlink PDCP SDUs for DRB Services for a Specific Operator in a Cell
........................................................................................................................................................................................ 3951
6.12.4 Total Processing Delay of Downlink PDCP SDUs for DRB Services for a Specific Operator in a Cell............3953
6.12.5 Total Number of Discarded downlink PDCP SDUs for DRB Services for a Specific Operator in a Cell.......... 3955
6.12.6 Total Number of Expected downlink Data Packets for DRB Services for a Specific Operator in a Cell........... 3957
6.13 PDCP Measurement per CNOperator (Traffic.PDCP.Cell.Operator).....................................................................3959
6.13.1 Number of Discarded Downlink PDCP SDUs for a Specific Operator.............................................................. 3960
6.13.2 Number of Transmitted Downlink Traffic PDCP SDUs for a Specific Operator............................................... 3962
7 Measurement of EUTRAN Cell-to-GERAN Cell Handover Performance

(ECELL_GCELL)......................................................................................................................... 3964
7.1 EUTRAN Cell-to-GERAN Cell Handover Measurement (IRATHO.NCell.GCell)................................................ 3965
7.1.1 Number of Handover Attempts from a Specific E-UTRAN Cell to a Specific GERAN Cell.............................. 3966
7.1.2 Number of Handover Executions from a Specific E-UTRAN Cell to a Specific GERAN Cell........................... 3968
7.1.3 Number of Successful Handovers from a Specific E-UTRAN Cell to a Specific GERAN Cell.......................... 3970
8 Measurement of EUTRAN Cell-to-WCDMA Cell Handover Performance

(ECELL_WCELL).........................................................................................................................3973
8.1 EUTRAN Cell-to-WCDMA Cell Handover Measurement (IRATHO.NCell.WCell)............................................. 3974
8.1.1 Number of Handover Attempts from a Specific E-UTRAN Cell to a Specific WCDMA Cell............................ 3975
8.1.2 Number of Handover Executions from a Specific E-UTRAN Cell to a Specific WCDMA Cell......................... 3977
8.1.3 Number of Successful Handovers from a Specific E-UTRAN Cell to a Specific WCDMA Cell........................ 3979
9 Measurement of Cell Sector Equipment Performance (CellSectorEQUIP)................. 3982

9.1 SFN Cell Sector Equipment User Quantity Measurement (User.CellSectorEQUIP)...............................................3984
9.1.1 Average Number of Independent-Scheduling UEs in the Downlink Served by a Set of Sector Equipment in an
SFN Cell......................................................................................................................................................................... 3985
9.1.2 Average Number of Independent-Scheduling UEs in the Uplink Served by a Set of Sector Equipment in an SFN
Cell..................................................................................................................................................................................3986
9.1.3 Average Number of UEs Served by a Set of Sector Equipment in an SFN Cell During Downlink Scheduling.. 3987
9.1.4 Average Number of UEs Served by a Set of Sector Equipment in an SFN Cell During Uplink Scheduling....... 3988
9.1.5 Average Number of UEs that Apply TM9 Under a Sector Equipment of an SFN Cell........................................ 3989
9.2 SFN Cell Sector Equipment PRB Measurement (PRB.CellSectorEQUIP)............................................................. 3990
9.2.1 Average Number of PRBs Occupied by Independent-Scheduling UEs in the Downlink Served by a Set of Sector
Equipment in an SFN Cell..............................................................................................................................................3991
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxxii

9.2.2 Average Number of PRBs Occupied by Independent-Scheduling UEs in the Uplink Served by a Set of Sector
Equipment in an SFN Cell..............................................................................................................................................3992
9.2.3 Average Number of Downlink PRBs for UEs Served by a Set of Sector Equipment in an SFN Cell.................. 3993
9.2.4 Average Number of Uplink PRBs for UEs Served by a Set of Sector Equipment in an SFN Cell.......................3994
9.3 SFN Cell Sector Equipment E-RAB Measurement (E-RAB.CellSectorEQUIP.SFN)............................................ 3995
9.3.1 Number of Successful E-RAB Setup Times on a Set of Sector Equipment in an SFN Cell.................................3996
9.3.2 Number of E-RAB Setup Failures on a Set of Sector Equipment in an SFN Cell................................................ 3999
9.3.3 Number of Normal E-RAB Releases on a Set of Sector Equipment in an SFN Cell............................................4001
9.3.4 Number of Abnormal E-RAB Releases on a Set of Sector Equipment in an SFN Cell........................................4004
9.4 SFN Cell Sector Equipment MAC Measurement (MAC.CellSectorEQUIP.SFN).................................................. 4006
9.4.1 Number of Bits used for Initial Service Transmissions on the Downlink SCH on a Set of Sector Equipment in an
SFN Cell......................................................................................................................................................................... 4007
9.4.2 Number of Bits used for Initial Service Transmissions on the Uplink SCH on a Set of Sector Equipment in an SFN
Cell..................................................................................................................................................................................4008
9.4.3 Duration of Downlink Service Scheduling at the MAC Layer of a Set of Sector Equipment in an SFN Cell..... 4009
9.4.4 Duration of Uplink Service Scheduling at the MAC Layer of a Set of Sector Equipment in an SFN Cell.......... 4010
9.4.5 Average Number of UEs Served by a Set of Sector Equipment in an SFN Cell with Uplink Joint Reception
Enabled........................................................................................................................................................................... 4011
9.4.6 Average Number of PRBs Used by UEs Served by a Set of Sector Equipment in an SFN Cell with Uplink Joint
Reception Enabled.......................................................................................................................................................... 4012
9.5 SFN Cell Sector Equipment RRC Measurement (RRC.CellSectorEQUIP.SFN).................................................... 4013
9.5.1 Number of RRC Connection Setup Requests Initiated by UEs Served by a Set of Sector Equipment in an SFN Cell
........................................................................................................................................................................................ 4014
9.5.2 Number of RRC Connection Setup Failures on a Set of Sector Equipment in an SFN Cell................................ 4016
9.5.3 Number of Successful RRC Connection Setup Times on a Set of Sector Equipment in an SFN Cell................. 4018
9.6 Combination Cell Sector Equipment PRB Measurement (User.CellSectorEQUIP.CellComb)............................... 4020
9.6.1 The average number of downlink PRBs for UEs served by a set of sector equipment in a combination cell is
calculated in a measurement period................................................................................................................................4021
9.6.2 The average number of uplink PRBs for UEs served by a set of sector equipment in a combination cell is
9.7 Combination Cell Sector Equipment User Quantity Measurement (PRB.CellSectorEQUIP.CellComb)................4023
9.7.1 The number of UEs served by a set of sector equipment in a combination cell during downlink scheduling is
9.7.2 The number of UEs served by a set of sector equipment in a combination cell during uplink scheduling is
9.8 Cell Sector Equipment Physical Layer Measurement (ChMeas.PHY.CellSectorEQUIP)....................................... 4026
9.8.1 RSSI of Every Antenna in a Set of Cell Sector Equipment...................................................................................4029
10 Measurement of Cell Sector Equipment Group Performance

(CellSectorEQUIPGroup)..........................................................................................................4038
10.1 SFN Cell Sector Equipment Group User Quantity Measurement (User.CellSectorEQUIPGroup)....................... 4039
10.1.1 Average Number Of Independent-Scheduling UEs in the Downlink Served by a Sector Equipment Group in an
SFN Cell......................................................................................................................................................................... 4040
10.1.2 Average Number Of Independent-Scheduling UEs in the Uplink Served by a Sector Equipment Group in an SFN
Cell..................................................................................................................................................................................4041
10.1.3 Average Number of UEs Served by a Sector Equipment Group in an SFN Cell During Downlink Scheduling4042
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxxiii

10.1.4 Average Number of Uplink UEs Served by a Sector Equipment Group in an SFN Cell During Uplink Scheduling
........................................................................................................................................................................................ 4043
10.1.5 Average Number of UEs that Apply TM9 Under a Sector Equipment Group of an SFN Cell...........................4044
10.2 SFN Cell Sector Equipment Group PRB Measurement (PRB.CellSectorEQUIPGroup)......................................4045
10.2.1 Average Number of PRBs Occupied by Independent-Scheduling UEs in the Downlink Served by a Sector
Equipment Group in an SFN Cell...................................................................................................................................4046
10.2.2 Average Number of PRBs Occupied by Independent-Scheduling UEs in the Uplink Served by a Sector
Equipment Group in an SFN Cell...................................................................................................................................4047
10.2.3 Average Number of Downlink PRBs for UEs Served by a Sector Equipment Group in an SFN Cell............... 4048
10.2.4 Average Number of Uplink PRBs for UEs Served by a Sector Equipment Group in an SFN Cell.................... 4049
10.3 SFN Cell Sector Equipment Group E-RAB Measurement (E-RAB.CellSectorEQUIPGroup.SFN).....................4050
10.3.1 Number of Successful E-RAB Setup Times in a Sector Equipment Group in an SFN Cell............................... 4051
10.3.2 Number of E-RAB Setup Failures in a Sector Equipment Group in an SFN Cell.............................................. 4053
10.3.3 Number of Normal E-RAB Releases in a Sector Equipment Group in an SFN Cell..........................................4055
10.3.4 Number of Abnormal E-RAB Releases in a Sector Equipment Group in an SFN Cell......................................4058
10.4 SFN Cell Sector Equipment Group MAC Measurement (MAC.CellSectorEQUIPGroup.SFN).......................... 4060
10.4.1 Number of Bits Used for Initial Service Transmissions on the Downlink SCH in a Sector Equipment Group in an
SFN Cell......................................................................................................................................................................... 4061
10.4.2 Number of Bits Used for Initial Service Transmissions on the Uplink SCH in a Sector Equipment Group in an
SFN Cell......................................................................................................................................................................... 4062
10.4.3 Duration of Downlink Service Scheduling at the MAC Layer of a Sector Equipment Group in an SFN Cell...4063
10.4.4 Duration of Uplink Service Scheduling at the MAC Layer of a Sector Equipment Group in an SFN Cell....... 4064
10.5 SFN Cell Sector Equipment Group RRC Measurement (RRC.CellSectorEQUIPGroup.SFN).............................4065
10.5.1 Number of RRC Connection Setup Requests Initiated by UEs Served by a Sector Equipment Group in an SFN
Cell..................................................................................................................................................................................4066
10.5.2 Number of RRC Connection Setup Failures in a Sector Equipment Group in an SFN Cell...............................4068
10.5.3 Number of Successful RRC Connection Setup Times in a Sector Equipment Group in an SFN Cell................4070
11 Measurement of Board Service Performance (Board.Service)...................................... 4072

11.1 Board User Quantity Measurement (Traffic.Board)............................................................................................... 4073
11.1.1 Maximum Number of Scheduled UEs per TTI in the Downlink in Cells Served by a Baseband Processing Unit
........................................................................................................................................................................................ 4074
11.1.2 Maximum Total Number of Scheduled UEs per TTI in the Uplink and Downlink in Cells Served by a Baseband
Processing Unit...............................................................................................................................................................4075
11.1.3 Maximum Number of Scheduled UEs per TTI in the Uplink in Cells Served by a Baseband Processing Unit. 4076
11.1.4 Maximum Number of UL-Sync UEs Served by a BBP...................................................................................... 4077
11.2 eNodeB Board Call Processing Measurement (Call Attempt.Board).....................................................................4078
11.2.1 Number of Call Processing Times in a Board..................................................................................................... 4079
11.3 eNodeB Board User-Plane CPU Measurement (UserPlane.CPU.Board)...............................................................4081
11.3.1 Maximum and Average User-Plane CPU Usage of a Board in an eNodeB........................................................ 4081
11.3.2 Number of Times the User-Plane CPU Usage of a Board in an eNodeB Is Greater Than the Preset Threshold.
........................................................................................................................................................................................ 4083
Index..............................................................................................................................................4084
Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxxiv

eNodeBFunction Performance Counter Reference 1 Measurement of Cell Performance (Cell)
1 Measurement of Cell Performance (Cell)
About This Chapter
Overview
The object type Cell Measurement contains cell-related function subsets. It represents the
quality of each type of service provided by the eNodeB.
FunctionSubSets
FunctionSubSet FunctionSubSet Name
RRC.Setup.Cell RRC Connection Setup Measurement (Cell)

(RRC.Setup.Cell)
RRC.SetupFail.Cell RRC Connection Setup Failure

Measurement (Cell) (RRC.SetupFail.Cell)
RRC.ReEst.Cell RRC Connection Reestablishment

Measurement (Cell) (RRC.ReEst.Cell)
RRC.ReEstFail.Cell RRC Connection Reestablishment Failure

Measurement (Cell) (RRC.ReEstFail.Cell)
E-RAB.Est.Cell E-RAB Setup Measurement (Cell) (E-

RAB.Est.Cell)
E-RAB.Rel.Cell E-RAB Release Measurement (Cell) (E-

RAB.Rel.Cell)
E-RAB.EstFail.Cell E-RAB Setup Failure Measurement (Cell)

(E-RAB.EstFail.Cell)
E-RAB.Modify.Cell E-RAB Modification Measurement (Cell)

(E-RAB.Modify.Cell)
Algo.Cell Cell Algo Measurement (Algo.Cell)
Issue 11 (2016-12-05) Huawei Proprietary and Confidential 1

Traffic.DRB.Cell DRB Measurement (Cell)

(Traffic.DRB.Cell)
Traffic.Thruput.Cell Throughput Measurement (Cell)

(Traffic.Thruput.Cell)
Traffic.Thruput.Cell.1 Throughput and Data Volume Measurement

1 (Traffic.Thruput.Cell.1)
Paging.Cell Paging Measurement (Cell) (Paging.Cell)
SecurMode.Cell SecurMode Measurement (Cell)

(SecurMode.Cell)
RA.Cell RA Measurement (Cell) (RA.Cell)
ChMeas.Pwr.Cell Channel Quality Measurement (Cell)

(ChMeas.Pwr.Cell)
ChMeas.Pwr1.Cell Channel Quality Measurement1 (Cell)

(ChMeas.Pwr1.Cell)
ChMeas.CQI.Cell CQI Measurement (Cell)

(ChMeas.CQI.Cell)
ChMeas.MCS.Cell MCS Measurement (Cell)

(ChMeas.MCS.Cell)
ChMeas.PRB.Cell PRB Measurement (Cell)

(ChMeas.PRB.Cell)
Traffic.MAC.Cell MAC Data Unit Measurement (Cell)

(Traffic.MAC.Cell)
Traffic.User.Cell User Number Measurement (Cell)

(Traffic.User.Cell)
HO.IRAT.Out.Cell Inter-RAT Outgoing Handover

Measurement (Cell) (HO.IRAT.Out.Cell)
HO.IRAT.Out.Cell.1 Inter-RAT Outgoing Handover

Measurement 1 (Cell) (HO.IRAT.Out.Cell.
1)
HO.IRAT.In.Cell Inter-RAT Incoming Handover

Measurement (Cell) (HO.IRAT.In.Cell)
HO.eRAN.Out.Cell Outgoing Handover Measurement (Cell)

(HO.eRAN.Out.Cell)
HO.eRAN.Out.Cell.1 Outgoing Handover Measurement 1(Cell)

(HO.eRAN.Out.Cell.1)
HO.eRAN.In.Cell Incoming Handover Measurement (Cell)

(HO.eRAN.In.Cell)

HO.eRAN.X2Out.Cell Measurement of Outgoing Handovers over

the X2 Interface (Cell)
(HO.eRAN.X2Out.Cell)
HO.DRX.Out.Cell DRX Outgoing Handover Measurement

(Cell) (HO.DRX.Out.Cell)
Traffic.Packet.Cell Packet Processing Measurement (Cell)

(Traffic.Packet.Cell)
ChMeas.DFEE.Cell Measurement of the Duration for Energy

Conservation and Emission Reduction
(Cell) (ChMeas.DFEE.Cell)
LCS.Cell LCS Measurement (Cell) (LCS.Cell)
EMC.Cell Measurement of Emergency Calls (Cell)

(EMC.Cell)
UeCntx.Rel.Cell UE Context Release Measurement (Cell)
SFN.Cell SFN Cell Measurement (SFN.Cell)
UeCntx.Mod.Cell UE Context Release Measurement (Cell)
CA.Cell CA Measurement (CA.Cell)
Traffic.RLC.Cell RLC Measurement (Cell)

(Traffic.RLC.Cell)
Reserve.Cell Reserve Cell Measurement (Reserve.Cell)
CellComb.Cell CellComb Cell Measurement

(CellComb.Cell)
ChMeas.MeasRpt.Cell Measure Reports Measurement

(ChMeas.MeasRpt.Cell)
UeCntx.Est.Cell UE ContextSetup Measurement (Cell)

(UECNTX.Est.Cell)
UeCntx.EstFail.Cell UE ContextSetup Failure Measurement

(Cell) (UECNTX.EstFail.Cell)
HO.eRAN.X2In.Cell Measurement of Incoming Handovers over

the X2 Interface (Cell)
(HO.eRAN.X2In.Cell)
Traffic.Thruput.PDF.Cell Throughput Distribution Measurement

(Cell) (Traffic.Thruput.PDF.Cell)
Traffic.Packet.PDF.Cell Packet Size Distribution Measurement

(Cell) (Traffic.Packet.PDF.Cell)
MBMS.Cell Cell MBMS Measurement (MBMS.Cell)

ChMeas.CQI.CA.PCell PCell CQI Measurement

(ChMeas.CQI.CA.PCell)
ChMeas.CQI.CA.SCell SCell CQI Measurement

(ChMeas.CQI.CA.SCell)
ChMeas.MCS.CA.PCell PCell MCS Measurement

(ChMeas.MCS.CA.PCell)
ChMeas.MCS.CA.SCell SCell MCS Measurement

(ChMeas.MCS.CA.SCell)
Traffic.MAC.CA.Cell CA Cell MAC Measurement

(Traffic.MAC.CA.Cell)
Traffic.PDCP.Cell PDCP Measurement (Cell)

(Traffic.PDCP.Cell)
ChMeas.MIMO.Cell MIMO Measurement (Cell)

(ChMeas.MIMO.Cell)
Traffic.Service.AttEst.Cell Service Setup Measurement

(Traffic.Service.AttEst.Cell)
Traffic.User.Thruput.Cell UE Traffic Rate Distribution Measurement

(Traffic.User.Thruput.Cell)
PL.Traffic.Thruput.Cell Throughput and Data Volume Measurement

per Path Loss Range
(PL.Traffic.Thruput.Cell)
ResOpt.Cell Resource Optimization Measurement

(ResOpt.Cell)
Traffic.User.Relay.Cell Cell Relay UE Quantity Measurement

(Traffic.User.Relay.Cell)
Traffic.Thruput.Relay.Cell Relay Throughput or Throughput Rate

Measurement(Traffic.Thruput.Relay.Cell)
Traffic.Packet.Relay.Cell Relay Packet

Measurement(Traffic.Packet.Relay.Cell)
ChMeas.PRB.Relay.Cell Relay PRB

Measurement(ChMeas.PRB.Relay.Cell)
RRC.ReEst.Relay.Cell Relay RRC Connection Reestablishment

Measurement (RRC.ReEst.Relay.Cell)
E-RAB.Rel.Relay.Cell Relay Users E-RAB Releases Measurement

(E-RAB.Rel.Relay.Cell)
Traffic.Thruput.Diff.Cell Differentiated Service Throughput

Measurement (Traffic.Thruput.Diff.Cell)

Traffic.Volume.PDF.Cell E-RAB Data Volume Distribution

Measurement (Traffic.Volume.PDF.Cell)
MroMeas.InterRat.Cell Inter-RAT MRO Measurement

(MroMeas.InterRat.Cell)

1.1 RRC Setup Measurement (RRC.Setup.Cell)

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 1-1 shows the measurement points in
an RRC connection setup procedure.
Figure 1-1
Counters
Counter ID Counter Name Counter Original Release
Description
1526726657 L.RRC.ConnReq. Number of RRC BTS3900:

Msg connection setup V100R008C00
requests BTS3900 LTE:
(retransmission version earlier than
included) V100R003C00
1526726658 L.RRC.ConnReq.A Number of RRC BTS3900:

tt connection setup V100R008C00
requests BTS3900 LTE:
(retransmission version earlier than
excluded) V100R003C00


Description
1526726659 L.RRC.ConnReq.S Number of RRC BTS3900:

ucc connection setup V100R008C00
completion times BTS3900 LTE:
version earlier than
V100R003C00
1526728216 L.RRC.ConnSetup Number of RRC BTS3900:

connection setup V100R008C00
times BTS3900 LTE:
V100R003C00

tt.Emc connection setup V100R008C00
attempts with a BTS3900 LTE:
cause value of V100R003C00
emergency

tt.HighPri connection setup V100R008C00
highPriorityAccess

tt.Mt connection setup V100R008C00
cause value of mt- V100R003C00
Access

tt.MoSig connection setup V100R008C00
cause value of mo- V100R003C00
Signalling

tt.MoData connection setup V100R008C00
Data

ucc.Emc Connection Setup V100R008C00
Complete messages BTS3900 LTE:
with a cause value V100R003C00
of emergency
received from UEs
in a cell


Description

ucc.HighPri Connection Setup V100R008C00
of
highPriorityAccess
received from UEs
in a cell

ucc.Mt Connection Setup V100R008C00
of mt-Access
received from UEs
in a cell

ucc.MoSig Connection Setup V100R008C00
of mo-Signalling
received from UEs
in a cell

ucc.MoData Connection Setup V100R008C00
of mo-Data received
from UEs in a cell

tt.DelayTol connection setup V100R008C00
delayTolerantAc-
cess-v1020
1526728358 L.RRC.ConnReq.S Number of BTS3900:

ucc.DelayTol successful RRC V100R008C00
connection setups BTS3900 LTE:
of delayTolerantAc-
cess-v1020


Description
1526728438 L.RRC.StateTrans. Number of times a BTS3900:

Syn2Unsyn UE switch from the V100R008C00
Uplink- BTS3900 LTE:
Synchronized state V100R008C00
to the uplink out-of-
synchronization
state
1526728439 L.RRC.StateTrans. Number of times a BTS3900:

Unsyn2Syn UE switch from the V100R008C00
out-of- BTS3900 LTE:
synchronization V100R008C00
state to the uplink-
synchronized state
1526728774 L.RRC.ConnSetup. Average RRC BTS3900:

TimeAvg connection setup V100R008C00
duration BTS3900 LTE:
V100R008C00
1526728775 L.RRC.ConnSetup. Maximum RRC BTS3900:

TimeMax connection setup V100R008C00
duration BTS3900 LTE:
V100R008C00
1526729656 L.RRC.StateTrans. Number of BTS3900:

Unsyn2Syn.Succ successfully V100R009C00
recovered RRC BTS3900 LTE:
connections when V100R009C00
UEs switch from the
uplink out-of-
synchronization
synchronized state

Msg.Emc connection setup V100R009C00
emergency
performed by UEs in
a cell
(retransmission
included)


Description

Msg.HighPri connection setup V100R009C00
highPriorityAccess
performed by UEs in
a cell
(retransmission
included)

Msg.Mt connection setup V100R009C00
cause value of mt- V100R009C00
Access performed
by UEs in a cell
(retransmission
included)

Msg.MoSig connection setup V100R009C00
Signalling
performed by UEs in
a cell
(retransmission
included)

Msg.MoData connection setup V100R009C00
Data performed by
UEs in a cell
(retransmission
included)

Msg.DelayTol connection setup V100R009C00
delayTolerantAc-
cess-v1020
performed by UEs in
a cell
(retransmission
included)


Description
1526730846 L.RRC.ConnReq. Maximum number BTS3900:

Max of RRC Connection V100R009C00
Request messages BTS3900 LTE:
received by a cell V100R009C00
from UEs (including
the discarded ones)
Counter Relationship
The RRC.Setup.Cell function subset contains counters related to RRC connection setup.
Some of these counters can be categorized in terms of the triggering cause for RRC
connection setup. The following table shows the parent-child relationship of the counters.
Root Counter Level-1 Counter
L.RRC.ConnReq.Msg L.RRC.ConnReq.Msg.Emc
L.RRC.ConnReq.Msg.HighPri
L.RRC.ConnReq.Msg.Mt
L.RRC.ConnReq.Msg.MoSig
L.RRC.ConnReq.Msg.MoData
L.RRC.ConnReq.Msg.DelayTol
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

1.1.1 Number of RRC Connection Setup Requests in a Cell

Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
1526726657 L.RRC.ConnRe Number of BTS3900, L

q.Msg RRC BTS3900 LTE
connection
setup requests
(retransmission
included)

q.Att RRC BTS3900 LTE
connection
setup requests
(retransmission
excluded)

q.Att.Emc RRC BTS3900 LTE
connection
setup attempts
with a cause
value of
emergency

q.Att.HighPri RRC BTS3900 LTE
connection
setup attempts
with a cause
value of
highPriorityAcc
ess

q.Att.Mt RRC BTS3900 LTE
connection
setup attempts
with a cause
value of mt-
Access

q.Att.MoSig RRC BTS3900 LTE
connection
setup attempts
with a cause
value of mo-
Signalling



q.Att.MoData RRC BTS3900 LTE
connection
setup attempts
with a cause
value of mo-
Data

q.Att.DelayTol RRC BTS3900 LTE
connection
setup attempts
with a cause
value of
delayTolerantA
ccess-v1020

q.Msg.Emc RRC BTS3900 LTE
connection
setup attempts
with a cause
value of
emergency
performed by
UEs in a cell
(retransmission
included)

q.Msg.HighPri RRC BTS3900 LTE
connection
setup attempts
with a cause
value of
highPriorityAcc
ess performed
by UEs in a cell
(retransmission
included)



q.Msg.Mt RRC BTS3900 LTE
connection
setup attempts
with a cause
value of mt-
Access
performed by
UEs in a cell
(retransmission
included)

q.Msg.MoSig RRC BTS3900 LTE
connection
setup attempts
with a cause
value of mo-
Signalling
performed by
UEs in a cell
(retransmission
included)

q.Msg.MoData RRC BTS3900 LTE
connection
setup attempts
with a cause
value of mo-
Data performed
by UEs in a cell
(retransmission
included)

q.Msg.DelayTol RRC BTS3900 LTE
connection
setup attempts
with a cause
value of
delayTolerantA
ccess-v1020
performed by
UEs in a cell
(retransmission
included)

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.
The signaling flows involved in the counter(s) comply with sections 5.3.3 in 3GPP TS 36.331
V10.4.0.
Measurement Points
As shown at point A in Figure 1-2, each time the cell receives an RRC Connection Request
message sent by a UE, the corresponding counters are calculated as follows:
The L.RRC.ConnReq.Msg counter is incremented by 1. The number of retransmitted RRC
Connection Request messages is also calculated.
The L.RRC.ConnReq.Msg.Emc counter is incremented by 1 each time the Establishment
Cause IE in the RRC Connection Request message is "emergency". The number of
retransmitted RRC Connection Request messages is also calculated.
The L.RRC.ConnReq.Msg.HighPri counter is incremented by 1 each time the Establishment
Cause IE in the RRC Connection Request message is "highPriorityAccess". The number of
The L.RRC.ConnReq.Msg.Mt counter is incremented by 1 each time the Establishment Cause
IE in the RRC Connection Request message is "mt-Access". The number of retransmitted
RRC Connection Request messages is also calculated.
The L.RRC.ConnReq.Msg.MoSig counter is incremented by 1 each time the Establishment
Cause IE in the RRC Connection Request message is "mo-Signalling". The number of
The L.RRC.ConnReq.Msg.MoData counter is incremented by 1 each time the Establishment
Cause IE in the RRC Connection Request messages is "mo-Data". The number of
The L.RRC.ConnReq.Msg.DelayTol counter is incremented by 1 each time the Establishment
Cause IE in the RRC Connection Request message is "delayTolerantAccess-v1020". The
number of retransmitted RRC Connection Request messages is also calculated.
The L.RRC.ConnReq.Att counter is incremented by 1. The number of retransmitted RRC
Connection Request messages is not calculated.
The L.RRC.ConnReq.Att.Emc counter is incremented by 1 each time the Establishment
Cause IE in the RRC Connection Request message is "emergency". The number of
retransmitted RRC Connection Request messages is not calculated.
The L.RRC.ConnReq.Att.HighPri counter is incremented by 1 each time the Establishment
Cause IE in the RRC Connection Request message is "highPriorityAccess". The number of
The L.RRC.ConnReq.Att.Mt counter is incremented by 1 each time the Establishment Cause
IE in the RRC Connection Request message is "mt-Access". The number of retransmitted
RRC Connection Request messages is not calculated.
The L.RRC.ConnReq.Att.MoSig counter is incremented by 1 each time the Establishment
Cause IE in the RRC Connection Request message is "mo-Signalling". The number of

The L.RRC.ConnReq.Att.MoData counter is incremented by 1 each time the Establishment

Cause IE in the RRC Connection Request message is "mo-Data". The number of
The L.RRC.ConnReq.Att.DelayTol counter is incremented by 1 each time the Establishment

Cause IE in the RRC Connection Request message is "delayTolerantAccess-v1020". The
number of retransmitted RRC Connection Request messages is not calculated.
Figure 1-2
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
L.RRC.ConnReq.Msg Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002007 RRC Connection
TDLBFD-002007 Management
RRC Connection
Management

L.RRC.ConnReq.Att Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnReq.Att.Emc Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnReq.Att.HighPr Multi-mode: None

i GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnReq.Att.Mt Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnReq.Att.MoSig Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management

L.RRC.ConnReq.Att.MoDat Multi-mode: None

a GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnReq.Att.Delay Multi-mode: None

Tol GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnReq.Msg.Emc Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnReq.Msg.High Multi-mode: None

Pri GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnReq.Msg.Mt Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management

L.RRC.ConnReq.Msg.MoSi Multi-mode: None

g GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnReq.Msg.MoD Multi-mode: None

ata GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnReq.Msg.Delay Multi-mode: None

Tol GSM: None
UMTS: None
RRC Connection
Management
1.1.2 Number of Successful RRC Connection Setups in a Cell

Counters

q.Succ RRC BTS3900 LTE
connection
setup
completion
times



q.Succ.Emc RRC BTS3900 LTE
Connection
Setup Complete
messages with a
cause value of
emergency
received from
UEs in a cell

q.Succ.HighPri RRC BTS3900 LTE
Connection
Setup Complete
messages with a
cause value of
highPriorityAcc
ess received
from UEs in a
cell

q.Succ.Mt RRC BTS3900 LTE
Connection
Setup Complete
messages with a
cause value of
mt-Access
received from
UEs in a cell

q.Succ.MoSig RRC BTS3900 LTE
Connection
Setup Complete
messages with a
cause value of
mo-Signalling
received from
UEs in a cell

q.Succ.MoData RRC BTS3900 LTE
Connection
Setup Complete
messages with a
cause value of
mo-Data
received from
UEs in a cell



q.Succ.DelayTo successful RRC BTS3900 LTE
l connection
setups with a
cause value of
delayTolerantA
ccess-v1020
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.
V10.4.0.
Measurement Points
As shown at point C in Figure 1-3, 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
Request message is "mo-Signalling".
The L.RRC.ConnReq.Succ.MoData counter is incremented by 1 each time the eNodeB
Request message is "mo-Data".
The L.RRC.ConnReq.Succ.DelayTol counter is incremented by 1 each time the eNodeB
Request message is "delayTolerantAccess-v1020".

Figure 1-3
Formula
None
Unit
None
Related Features
L.RRC.ConnReq.Succ Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnReq.Succ.Emc Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management

L.RRC.ConnReq.Succ.High Multi-mode: None

Pri GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnReq.Succ.Mt Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnReq.Succ.MoSi Multi-mode: None

g GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnReq.Succ.MoD Multi-mode: None

ata GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnReq.Succ.Dela Multi-mode: None

yTol GSM: None
UMTS: None
RRC Connection
Management

1.1.3 Number of RRC Connection Setup Attempts in a Cell

Counters
1526728216 L.RRC.ConnSe Number of BTS3900, L

tup RRC BTS3900 LTE
connection
setup times
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.
V10.4.0.
Measurement Points
As shown at point B in Figure 1-4, 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 1-4

Formula
None
Unit
None
Related Features
L.RRC.ConnSetup Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
1.1.4 Number of Times a UE switch from the Uplink-

Synchronized State to the Uplink Out-of-Synchronization State
Counters
1526728438 L.RRC.StateTra Number of BTS3900, L

ns.Syn2Unsyn times a UE BTS3900 LTE
switch from the
Uplink-
Synchronized
state to the
uplink out-of-
synchronization
state
Description
The counter measures the number of times a UE switch 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 switch from
the uplink-synchronized state to the uplink out-of-synchronization state.

Formula
None
Unit
None
Related Features
L.RRC.StateTrans.Syn2Uns Multi-mode: None

yn GSM: None
UMTS: None
RRC Connection
Management
1.1.5 Number of Times a UE switch from the Uplink Out-of-

Synchronization state to the Uplink-Synchronized State
Counters

ns.Unsyn2Syn times a UE BTS3900 LTE
switch from the
out-of-
synchronization
state to the
uplink-
synchronized
state
Description
The counter measures the number of times a UE switch 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 switch from
the uplink out-of-synchronization state to the uplink-synchronized state.

Formula
None
Unit
None
Related Features
L.RRC.StateTrans.Unsyn2S Multi-mode: None

yn GSM: None
UMTS: None
RRC Connection
Management
1.1.6 RRC Connection Setup Duration in a Cell
Counters
1526728774 L.RRC.ConnSe Average RRC BTS3900, L

tup.TimeAvg connection BTS3900 LTE
setup duration
1526728775 L.RRC.ConnSe Maximum RRC BTS3900, L

tup.TimeMax connection BTS3900 LTE
setup duration
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.
The signaling flows involved in the counter(s) comply with section 5.3.3 in 3GPP TS 36.331
V10.4.0.
Measurement Points
As shown at points A and B in Figure 1-5, 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 1-5
Formula
None
Unit
ms
Related Features
L.RRC.ConnSetup.TimeAvg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management

L.RRC.ConnSetup.TimeMa Multi-mode: None

x GSM: None
UMTS: None
RRC Connection
Management
1.1.7 Number of Successfully Recovered RRC Connections When

UEs switch from the Uplink Out-of-Synchronization State to
Uplink-Synchronized State
Counters

ns.Unsyn2Syn. successfully BTS3900 LTE
Succ recovered RRC
connections
when UEs
switch from the
uplink out-of-
synchronization
state to the
uplink-
synchronized
state
Description
The counter measures the number of times that an RRC connection is recovered successfully
when UEs switch from the uplink out-of-synchronization state to the uplink-synchronized
state. An RRC connection is regarded as recovered for a UE when the eNodeB finishes uplink
PUCCH resource allocation for the UE.
The signaling flows involved in the counter(s) comply with section 5.1 in 3GPP TS 36.321
V10.4.0 and section 5.3.5 in 3GPP TS 36.331 V10.4.0.
Measurement Points
As shown at point B in Figure 1-6, when UEs switch from the uplink out-of-synchronization
state to the uplink-synchronized state, the L.RRC.StateTrans.Unsyn2Syn.Succ counter is
incremented by 1 each time the eNodeB receives an RRC Connection Reconfiguration

Complete message from a UE which indicating that the eNodeB finishes uplink PUCCH
resource allocation for the UE.
Figure 1-6
Formula
None
Unit
None
Related Features
L.RRC.StateTrans.Unsyn2S Multi-mode: None

yn.Succ GSM: None
UMTS: None
LTE: LOFD-001105 Dynamic DRX
TDLOFD-001105 Dynamic DRX

1.1.8 Maximum Number of RRC Connection Setup Requests in a

Cell
Counters
1526730846 L.RRC.ConnRe Maximum BTS3900, L

q.Max number of RRC BTS3900 LTE
Connection
Request
messages
received by a
cell from UEs
(including the
discarded ones)
Description
The counter measures the maximum number of RRC Connection Request messages received
by 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
The number of RRC Connection Request messages is sampled in a cell per second. At the end
of a measurement period, the maximum of these sampling results is used as the
L.RRC.ConnReq.Max counter value.
Formula
None
Unit
None

Related Features
L.RRC.ConnReq.Max Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
1.2 RRC Setup Failure Measurement (RRC.SetupFail.Cell)

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 1-7 shows the
measurement points in a failed RRC connection setup procedure.
Figure 1-7

Counters
Description
1526727083 L.RRC.SetupFail.R Number of RRC BTS3900:

esFail connection setup V100R008C00
failures due to BTS3900 LTE:
resource allocation version earlier than
failures V100R003C00
1526727084 L.RRC.SetupFail.N Number of RRC BTS3900:

oReply connection setup V100R008C00
failures due to no BTS3900 LTE:
responses from the version earlier than
UE V100R003C00

ej Connection Reject V100R008C00
messages sent to BTS3900 LTE:
UEs in a cell V100R003C00

esFail.SRS connection setup V100R008C00
failures due to SRS BTS3900 LTE:
resource allocation V100R008C00
failure

esFail.PUCCH connection setup V100R008C00
failures due to BTS3900 LTE:
PUCCH resource V100R008C00
allocation failure
1526728489 L.RRC.ConnReq. Number of times the BTS3900:

Msg.disc.FlowCtrl RRC Connection V100R008C00
Request message is BTS3900 LTE:
discarded due to V100R008C00
flow control
1526728490 L.RRC.SetupFail.R Number of times the BTS3900:

ej.FlowCtrl eNodeB sends an V100R008C00
RRC Connection BTS3900 LTE:
Reject message to V100R008C00
the UE due to flow
control

esFail.UserSpec connection setup V100R009C00
failures because of BTS3900 LTE:
limitation of UE V100R009C00
number specification


Description
1526732044 L.RRC.SetupFail.R Number of times the BTS3900:

ej.MMEOverload eNodeB sends an V100R009C00
RRC Connection BTS3900 LTE:
Reject message to V100R009C00
the UE due to MME
overload

ej.Other connection setup V100R010C00
requests rejected due BTS3900 LTE:
to other causes V100R010C00

esFail.Other connection setup V100R010C00
failures due to other BTS3900 LTE:
resource allocation V100R010C00
failure
1526737854 L.RRC.ReEstFail. Number of times the BTS3900:

Disc.FlowCtrl RRC Connection V100R010C10
Reestablishment BTS3900 LTE:
Request messages V100R010C10
are discarded due to
flow control
The RRC.SetupFail.Cell function subset contains counters related to RRC connection setup
failure. In terms of the procedure, the causes for RRC connection setup failure can be
categorized as no response from a UE over the air interface and request rejection. The request
rejection can be caused by resource insufficiency, flow control, MME overload, or others. The
resource insufficiency causes can be further categorized in terms of the resource type. The
following table shows the parent-child relationship of the counters.
Root Counter Level-1 Counter Level-2 Counter
L.RRC.SetupFail.Rej L.RRC.SetupFail.ResFail L.RRC.SetupFail.ResFail.S

RS
L.RRC.SetupFail.ResFail.P
UCCH
L.RRC.SetupFail.ResFail.U
serSpec
L.RRC.SetupFail.ResFail.Ot
her
L.RRC.SetupFail.Rej.FlowC -
trl

L.RRC.SetupFail.Rej.MME -
Overload
L.RRC.SetupFail.Rej.Other -
1.2.1 Number of RRC Connection Setup Failures for Different

Causes in a Cell
Counters
1526727083 L.RRC.SetupFa Number of BTS3900, L

il.ResFail RRC BTS3900 LTE
connection
setup failures
due to resource
allocation
failures

il.NoReply RRC BTS3900 LTE
connection
setup failures
due to no
responses from
the UE

il.Rej RRC BTS3900 LTE
Connection
Reject
messages sent
to UEs in a cell

il.ResFail.SRS RRC BTS3900 LTE
connection
setup failures
due to SRS
resource
allocation
failure



il.ResFail.PUC RRC BTS3900 LTE
CH connection
setup failures
due to PUCCH
resource
allocation
failure

q.Msg.disc.Flo times the RRC BTS3900 LTE
wCtrl Connection
Request
message is
discarded due
to flow control

il.Rej.FlowCtrl times the BTS3900 LTE
eNodeB sends
an RRC
Connection
Reject message
to the UE due
to flow control

il.ResFail.User RRC BTS3900 LTE
Spec connection
setup failures
because of
limitation of
UE number
specification

il.Rej.MMEOve times the BTS3900 LTE
rload eNodeB sends
an RRC
Connection
Reject message
to the UE due
to MME
overload

il.Rej.Other RRC BTS3900 LTE
connection
setup requests
rejected due to
other causes



il.ResFail.Other RRC BTS3900 LTE
connection
setup failures
due to other
resource
allocation
failure
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.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-8, the L.RRC.SetupFail.ResFail,
L.RRC.SetupFail.ResFail.SRS, L.RRC.SetupFail.ResFail.PUCCH, or
L.RRC.SetupFail.ResFail.UserSpec counter is incremented by 1 each time the eNodeB sends
an RRC Connection Reject message to a UE because of resource allocation failure, SRS
resource allocation failure, PUCCH resource allocation failure, or UE number specification
limitation, respectively, after receiving an RRC Connection Request message from the UE.
As shown at point A in Figure 1-9, the L.RRC.SetupFail.NoReply counter is incremented by
1 each time the eNodeB does not receive an RRC Connection Setup Complete message from
the UE within the specified time. Before that, the eNodeB has sent an RRC Connection Setup
message to the UE after receiving an RRC Connection Request message from the UE.
As shown at point A in Figure 1-8, the L.RRC.SetupFail.Rej counter is incremented by 1
each time the eNodeB sends an RRC Connection Reject message to the UE after receiving an
RRC Connection Request message from the UE.
As shown at point A in Figure 1-8, the L.RRC.SetupFail.Rej.FlowCtrl counter is incremented
by 1 each time the eNodeB sends an RRC Connection Reject message to the UE due to flow
control after receiving an RRC Connection Request message from the UE.
As shown at point A in Figure 1-8, the L.RRC.SetupFail.Rej.MMEOverload counter is
incremented by 1 each time the eNodeB sends an RRC Connection Reject message to the UE
because the MME is overloaded or no MME is available for other reasons after receiving an
RRC Connection Request message from the UE.
As shown at point A in Figure 1-8, the L.RRC.SetupFail.Rej.Other counter is incremented by
1 when the eNodeB sends an RRC Connection Reject message to a UE after receiving an
RRC Connection Request message from the UE and the RRC Connection Reject message has
a cause value other than resource allocation failure, flow control, or MME overloaded.

As shown at point A in Figure 1-8, the L.RRC.SetupFail.ResFail.Other counter is

incremented by 1 when the eNodeB sends an RRC Connection Reject message to a UE after
receiving an RRC Connection Request message from the UE and the RRC Connection Reject
message has a cause value of resource allocation failure and a sub-cause-value other than SRS
resource allocation failure, PUCCH resource allocation failure, or UE number exceeding
specification.
As shown at point A in Figure 1-10, the L.RRC.ConnReq.Msg.disc.FlowCtrl counter is
incremented by 1 each time the eNodeB discards an RRC Connection Request message
(including retransmissions) from a UE due to flow control.
Figure 1-8
Figure 1-9

Figure 1-10
Formula
None
Unit
None
Related Features
L.RRC.SetupFail.ResFail Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.SetupFail.NoReply Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.SetupFail.Rej Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management

L.RRC.SetupFail.ResFail.S Multi-mode: None

RS GSM: None
UMTS: None
RRC Connection
Management
L.RRC.SetupFail.ResFail.P Multi-mode: None

UCCH GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnReq.Msg.disc. Multi-mode: None

FlowCtrl GSM: None
UMTS: None
RRC Connection
Management
L.RRC.SetupFail.Rej.FlowC Multi-mode: None

trl GSM: None
UMTS: None
RRC Connection
Management
L.RRC.SetupFail.ResFail.U Multi-mode: None

serSpec GSM: None
UMTS: None
RRC Connection
Management

L.RRC.SetupFail.Rej.MME Multi-mode: None

Overload GSM: None
UMTS: None
RRC Connection
Management
L.RRC.SetupFail.Rej.Other Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.SetupFail.ResFail.Ot Multi-mode: None

her GSM: None
UMTS: None
RRC Connection
Management
1.3 RRC Reestablishment Measurement (RRC.ReEst.Cell)

Overview
An RRC connection reestablishment is a UE-initiated process of recovering an RRC
connection. The RRC.ReEst.Cell function subset measures the number of RRC connection
reestablishment requests for different causes and number of successful RRC connection
reestablishment times in a cell. Figure 1-11 shows the measurement points in an RRC
connection reestablishment procedure.

Figure 1-11
Counters
Description
1526727085 L.RRC.ReEst.Att Number of RRC BTS3900:

connection V100R008C00
reestablishment BTS3900 LTE:
requests version earlier than
V100R003C00
1526727086 L.RRC.ReEst.Succ Number of BTS3900:

successful RRC V100R008C00
connection BTS3900 LTE:
reestablishments version earlier than
V100R003C00
1526727087 L.RRC.ReEst.Reco Number of RRC BTS3900:

nfFail.Att connection V100R008C00
requests triggered by version earlier than
reconfiguration V100R003C00
failures


Description
1526727088 L.RRC.ReEst.Reco Number of BTS3900:

nfFail.Succ successful RRC V100R008C00
triggered by V100R003C00
reconfiguration
failures
1526727090 L.RRC.ReEst.HoF Number of RRC BTS3900:

ail.Att connection V100R008C00
requests triggered by version earlier than
failed handovers V100R003C00
1526727091 L.RRC.ReEst.HoF Number of BTS3900:

ail.Succ successful RRC V100R008C00
triggered by failed V100R003C00
handovers
1526730536 L.RRC.ReEst.Non Number of RRC BTS3900:

Srccell.Att connection V100R009C00
requests to another V100R009C00
cell
1526730537 L.RRC.ReEst.Non Number of BTS3900:

Srccell.Succ successful RRC V100R009C00
reestablishment V100R009C00
times to another cell
The RRC.ReEst.Cell function subset contains counters related to RRC connection
reestablishment. Some of these counters can be categorized in terms of the triggering cause
for RRC connection reestablishment. The following table shows the parent-child relationship
of the counters.
L.RRC.ReEst.Att L.RRC.ReEst.ReconfFail.Att
L.RRC.ReEst.HoFail.Att
L.RRC.ReEst.NonSrccell.Att
L.RRC.ReEst.Succ L.RRC.ReEst.ReconfFail.Succ

L.RRC.ReEst.HoFail.Succ
L.RRC.ReEst.NonSrccell.Succ
1.3.1 Number of RRC Connection Reestablishment Requests in a

Cell
Counters
1526727085 L.RRC.ReEst.A Number of BTS3900, L

tt RRC BTS3900 LTE
connection
reestablishment
requests
1526727087 L.RRC.ReEst.R Number of BTS3900, L

econfFail.Att RRC BTS3900 LTE
connection
reestablishment
requests
triggered by
reconfiguration
failures
1526727090 L.RRC.ReEst.H Number of BTS3900, L

oFail.Att RRC BTS3900 LTE
connection
reestablishment
requests
triggered by
failed
handovers
1526730536 L.RRC.ReEst.N Number of BTS3900, L

onSrccell.Att RRC BTS3900 LTE
connection
reestablishment
requests to
another cell
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.

V10.4.0.
Measurement Points
As shown at point A in Figure 1-12, 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.ReconfFail.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 information element (IE) in the message is "reconfigurationFailure".
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".
The L.RRC.ReEst.NonSrccell.Att counter is incremented by 1 if the reestablishment target

cell is not the serving cell of the UE before reestablishment.
Figure 1-12
Formula
None
Unit
None

Related Features
L.RRC.ReEst.Att Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ReEst.ReconfFail.At Multi-mode: None

t GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ReEst.HoFail.Att Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ReEst.NonSrccell.At Multi-mode: None

t GSM: None
UMTS: None
RRC Connection
Management

1.3.2 Number of Successful RRC Connection Reestablishments in

a Cell
Counters
1526727086 L.RRC.ReEst.S Number of BTS3900, L

ucc successful RRC BTS3900 LTE
connection
reestablishment
s

econfFail.Succ successful RRC BTS3900 LTE
connection
reestablishment
s triggered by
reconfiguration
failures

oFail.Succ successful RRC BTS3900 LTE
connection
reestablishment
s triggered by
failed
handovers
1526730537 L.RRC.ReEst.N Number of BTS3900, L

onSrccell.Succ successful RRC BTS3900 LTE
connection
reestablishment
times to another
cell
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.
V10.4.0.
Measurement Points
As shown at point B in Figure 1-13, 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.
The L.RRC.ReEst.ReconfFail.Succ counter is incremented by 1 if the Reestablishment Cause
information element (IE) in the corresponding RRC Connection Reestablishment Request
message from the UE is "reconfigurationFailure".
The L.RRC.ReEst.HoFail.Succ counter is incremented by 1if the Reestablishment Cause IE in
the corresponding RRC Connection Reestablishment Request message from the UE is
"handoverFailure".
The L.RRC.ReEst.NonSrccell.Succ counter is incremented by 1 if the reestablishment target
cell is not the serving cell of the UE before reestablishment.
Figure 1-13
Formula
None
Unit
None

Related Features
L.RRC.ReEst.Succ Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ReEst.ReconfFail.Su Multi-mode: None

cc GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ReEst.HoFail.Succ Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ReEst.NonSrccell.Su Multi-mode: None

cc GSM: None
UMTS: None
RRC Connection
Management
1.4 RRC Reestablishment Failure Measurement

(RRC.ReEstFail.Cell)
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 1-14 shows the
measurement points in a failed RRC connection reestablishment procedure.

Figure 1-14
Counters
Description
1526727089 L.RRC.ReEst.Reco Number of rejected BTS3900:

nfFail.Rej RRC connection V100R008C00
attempts triggered version earlier than
by reconfiguration V100R003C00
failures
1526727092 L.RRC.ReEst.HoF Number of rejected BTS3900:

ail.Rej RRC connection V100R008C00
attempts triggered version earlier than
by handover failures V100R003C00
1526727093 L.RRC.ReEstFail. Number of RRC BTS3900:

ResFail connection V100R008C00
failures due to failed V100R003C00
resource allocations


Description

NoReply connection V100R008C00
failures due to no V100R003C00
responses from the
UE
1526728270 L.RRC.ReEstFail. Total number of BTS3900:

Rej RRC connection V100R008C00
rejections V100R003C00

NoCntx connection V100R008C00
failures due to V100R003C00
unavailability of UE
contexts

NoCntx.PreProcFa connection V100R009C00
il reestablishment BTS3900 LTE:
failures due to UE V100R009C00
context
unavailability
caused by the pre-
processing failure
The RRC.ReEstFail.Cell function subset contains counters related to RRC connection
reestablishment failure. Some of these counters can be categorized in terms of the triggering
cause and failure cause for RRC connection reestablishment. In terms of the procedure, the
triggering causes can be further categorized as no response from a UE over the air interface
and request rejection. The request rejection can be caused by resource insufficiency, no UE
context, or others. The following table shows the parent-child relationship of the counters.
L.RRC.ReEstFail.Rej L.RRC.ReEst.ReconfFail.Re -
j
L.RRC.ReEst.HoFail.Rej -
L.RRC.ReEstFail.Rej L.RRC.ReEstFail.ResFail -
L.RRC.ReEstFail.NoCntx L.RRC.ReEstFail.NoCntx.P
reProcFail

1.4.1 Number of RRC Connection Reestablishment Failures for

Different Causes in a Cell
Counters
1526737854 L.RRC.ReEstFa Number of BTS3900, L

il.Disc.FlowCtrl times the RRC BTS3900 LTE
Connection
Reestablishmen
t Request
messages are
discarded due
to flow control

econfFail.Rej rejected RRC BTS3900 LTE
connection
reestablishment
attempts
triggered by
reconfiguration
failures

oFail.Rej rejected RRC BTS3900 LTE
connection
reestablishment
attempts
triggered by
handover
failures

il.ResFail RRC BTS3900 LTE
connection
reestablishment
failures due to
failed resource
allocations

il.NoReply RRC BTS3900 LTE
connection
reestablishment
failures due to
no responses
from the UE


1526728270 L.RRC.ReEstFa Total number of BTS3900, L

il.Rej RRC BTS3900 LTE
connection
reestablishment
rejections

il.NoCntx RRC BTS3900 LTE
connection
reestablishment
failures due to
unavailability
of UE contexts

il.NoCntx.PrePr RRC BTS3900 LTE
ocFail connection
reestablishment
failures due to
UE context
unavailability
caused by the
pre-processing
failure
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.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-15, 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.
The L.RRC.ReEst.ReconfFail.Rej counter is incremented by 1 if the ReestablishmentCause

information element (IE) in the corresponding RRC Connection Reestablishment Request
message from the UE is "reconfigurationFailure".

The L.RRC.ReEst.HoFail.Rej counter is incremented by 1 if the ReestablishmentCause IE in

the corresponding RRC Connection Reestablishment Request message from the UE is
"handoverFailure".
The L.RRC.ReEstFail.ResFail counter is incremented by 1 each time the RRC connection
reestablishment fails due to a failed resource allocation.
The L.RRC.ReEstFail.NoCntx counter is incremented by 1 each time the RRC connection
reestablishment fails because UE contexts are unavailable.
The L.RRC.ReEstFail.NoCntx.PreProcFail counter is incremented by 1 each time the RRC
connection reestablishment fails because the UE context is unavailable due to the pre-
processing failure.
As shown at point A in Figure 1-16, the L.RRC.ReEstFail.NoReply counter is incremented
by 1 each time the eNodeB does not receive an RRC Connection Reestablishment Complete
message from the UE within the specified time.
As shown at point A in Figure 1-17, the L.RRC.ReEstFail.Disc.FlowCtrl counter is
incremented by 1 each time the cell discards an RRC Connection Reestablishment Request
message from a UE because of flow control.
Figure 1-15

Figure 1-16
Figure 1-17
Formula
None
Unit
None

Related Features
L.RRC.ReEstFail.Disc.Flow Multi-mode: None

Ctrl GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ReEst.ReconfFail.Re Multi-mode: None

j GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ReEst.HoFail.Rej Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ReEstFail.ResFail Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ReEstFail.NoReply Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management

L.RRC.ReEstFail.Rej Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ReEstFail.NoCntx Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ReEstFail.NoCntx.P Multi-mode: None

reProcFail GSM: None
UMTS: None
RRC Connection
Management
1.5 E-RAB Setup Measurement (E-RAB.Est.Cell)

Overview
An E-RAB is the access layer bearer for carrying service data of a UE. The E-RAB setup
success rate in a cell directly represents the capability of the cell to provide E-RAB
connections for UEs. The E-RAB.Est.Cell function subset measures the number of E-RAB
setup attempts and number of successful E-RAB setups for each service with a specific QoS
Class Identifier (QCI) in a cell. The setup of one E-RAB is counted once. Figure 1-18 shows
the measurement points of an E-RAB setup procedure during a non-handover process. Figure
1-19 shows the measurement points of an E-RAB setup procedure initiated by the target
eNodeB during a handover.

Figure 1-18

Figure 1-19
Counters
Description
1526726668 L.E- Number of E-RAB BTS3900:

RAB.AttEst.QCI.1 setup attempts V100R008C00
initiated by UEs for BTS3900 LTE:
services with the version earlier than
QCI of 1 in a cell V100R003C00
1526726669 L.E- Number of BTS3900:

RAB.SuccEst.QCI. successful E-RAB V100R008C00
1 setups initiated by BTS3900 LTE:
UEs for services version earlier than
with the QCI of 1 in V100R003C00
a cell

1526726671 L.E- Number of BTS3900:

a cell


Description

1526726673 L.E- Number of BTS3900:

a cell

1526726675 L.E- Number of BTS3900:

a cell

1526726677 L.E- Number of BTS3900:

a cell

1526726679 L.E- Number of BTS3900:

a cell


Description

1526726681 L.E- Number of BTS3900:

a cell

1526726683 L.E- Number of BTS3900:

a cell

1526726685 L.E- Number of BTS3900:

a cell
1526727544 L.E-RAB.SuccEst Total number of BTS3900:

successful E-RAB V100R008C00
setups initiated by BTS3900 LTE:
UEs in a cell version earlier than
V100R003C00
1526727545 L.E-RAB.AttEst Total number of E- BTS3900:

RAB setup attempts V100R008C00
initiated by UEs in a BTS3900 LTE:
cell version earlier than
V100R003C00


Description
1526728192 L.E- Number of initial E- BTS3900:

RAB.InitAttEst.Q RAB setup attempts V100R008C00
CI.1 initiated by UEs for BTS3900 LTE:
services with the V100R003C00
QCI of 1 in a cell
1526728193 L.E- Number of BTS3900:

RAB.InitSuccEst.Q successful initial E- V100R008C00
CI.1 RAB setups initiated BTS3900 LTE:
by UEs for services V100R003C00
with the QCI of 1 in
a cell

QCI of 2 in a cell
1526728195 L.E- Number of BTS3900:

a cell

QCI of 3 in a cell
1526728197 L.E- Number of BTS3900:

a cell

QCI of 4 in a cell
1526728199 L.E- Number of BTS3900:

a cell


Description

QCI of 5 in a cell
1526728201 L.E- Number of BTS3900:

a cell

QCI of 6 in a cell
1526728203 L.E- Number of BTS3900:

a cell

QCI of 7 in a cell
1526728205 L.E- Number of BTS3900:

a cell

QCI of 8 in a cell
1526728207 L.E- Number of BTS3900:

a cell


Description

QCI of 9 in a cell
1526728209 L.E- Number of BTS3900:

a cell
1526728244 L.E- Total number of E- BTS3900:

RAB.AttEst.HOIn RAB setup attempts V100R008C00
for incoming BTS3900 LTE:
handovers in a cell V100R003C00
1526728245 L.E- Total number of BTS3900:

RAB.SuccEst.HOI successful E-RAB V100R008C00
n setups for incoming BTS3900 LTE:
1526728272 L.S1Sig.ConnEst.A Number of UE- BTS3900:

tt related signaling V100R008C00
connection setup BTS3900 LTE:
attempts over the S1 V100R003C00
interface
1526728273 L.S1Sig.ConnEst.S Number of BTS3900:

ucc successful UE- V100R008C00
related signaling BTS3900 LTE:
connection setups V100R003C00
over the S1 interface

RAB.InitAttEst initial E-RAB setup V100R008C00
attempts initiated by BTS3900 LTE:

RAB.InitSuccEst successful initial E- V100R008C00
RAB setups initiated BTS3900 LTE:
by UEs in a cell V100R003C00
1526728776 L.E- Average E-RAB BTS3900:

RAB.Est.TimeAvg setup duration in a V100R008C00
cell BTS3900 LTE:
V100R008C00


Description
1526728777 L.E- Maximum E-RAB BTS3900:

RAB.Est.TimeMax setup duration in a V100R008C00
cell BTS3900 LTE:
V100R008C00
1526728778 L.E- Number of BTS3900:

n.QCI.1 setups for incoming BTS3900 LTE:
handovers of V100R008C00
services with QCI of
1 in a cell
1526728779 L.E- Number of BTS3900:

2 in a cell
1526728780 L.E- Number of BTS3900:

3 in a cell
1526728781 L.E- Number of BTS3900:

4 in a cell
1526728782 L.E- Number of BTS3900:

5 in a cell
1526728783 L.E- Number of BTS3900:

6 in a cell


Description
1526728784 L.E- Number of BTS3900:

7 in a cell
1526728785 L.E- Number of BTS3900:

8 in a cell
1526728786 L.E- Number of BTS3900:

9 in a cell
1526728879 L.E- Average initial E- BTS3900:

RAB.InitEst.Time RAB setup duration V100R008C00
Avg in a cell BTS3900 LTE:
V100R008C00
1526728880 L.E- Maximum initial E- BTS3900:

RAB.InitEst.Time RAB setup duration V100R008C00
Max in a cell BTS3900 LTE:
V100R008C00

RAB.AttEst.HOIn. setups attempts for V100R008C01
QCI.1 incoming handovers BTS3900 LTE:
of services with QCI V100R008C01
of 1 in a cell

of 2 in a cell

of 3 in a cell


Description

of 4 in a cell

of 5 in a cell

of 6 in a cell

of 7 in a cell

of 8 in a cell

of 9 in a cell

RAB.StateTrans.U recovery attempts V100R009C00
nsyn2Syn.Att when UEs switch BTS3900 LTE:
from the uplink out- V100R009C00
of-synchronization
synchronized state
1526729658 L.E- Number of BTS3900:

RAB.StateTrans.U successfully V100R009C00
nsyn2Syn.Succ recovered E-RABs BTS3900 LTE:
when UEs switch V100R009C00
from the uplink out-
of-synchronization
synchronized state


Description
1526736847 L.E- Number of BTS3900:

PTT setups initiated by BTS3900 LTE:
UEs for PTT V100R010C10
services

RAB.AttEst.QCI.P setup attempts V100R010C10
TT initiated by UEs for BTS3900 LTE:
PTT services V100R010C10

CI.PTT initiated by UEs for BTS3900 LTE:
PTT services V100R010C10
1526736850 L.E- Number of BTS3900:

CI.PTT RAB setups initiated BTS3900 LTE:
by UEs for PTT V100R010C10
services

QCI.PTT incoming handovers BTS3900 LTE:
of PTT services V100R010C10
1526736852 L.E- Number of BTS3900:

n.QCI.PTT setups for incoming BTS3900 LTE:
handovers of PTT V100R010C10
services
The E-RAB.Est.Cell function subset contains counters related to E-RAB setup. In terms of the
procedure, some of these counters can be categorized as counters related to E-RAB setup
during initial context setup and others. Some of these counters can be categorized in terms of
the QCI. The following table shows the parent-child relationship of the counters.
L.E-RAB.SuccEst L.E-RAB.SuccEst.QCI.1 L.E-RAB.InitSuccEst.QCI.1
L.E-RAB.SuccEst.QCI.2 L.E-RAB.InitSuccEst.QCI.2

L.E-RAB.SuccEst.QCI.PTT -
L.E-RAB.SuccEst L.E-RAB.InitSuccEst L.E-RAB.InitSuccEst.QCI.1
L.E-RAB.InitSuccEst.QCI.2
L.E-
RAB.InitSuccEst.QCI.PTT
L.E-RAB.AttEst L.E-RAB.AttEst.QCI.1 L.E-RAB.InitAttEst.QCI.1
L.E-RAB.AttEst.QCI.2 L.E-RAB.InitAttEst.QCI.2
L.E-RAB.AttEst.QCI.PTT -
L.E-RAB.AttEst L.E-RAB.InitAttEst L.E-RAB.InitAttEst.QCI.1
L.E-RAB.InitAttEst.QCI.2

L.E-
RAB.InitAttEst.QCI.PTT
L.E-RAB.AttEst.HOIn L.E-RAB.AttEst.HOIn.QCI. -
1
L.E-RAB.AttEst.HOIn.QCI. -
2
3
4
5
6
7
8
9
L.E- -
RAB.AttEst.HOIn.QCI.PTT
L.E-RAB.SuccEst.HOIn L.E- -
RAB.SuccEst.HOIn.QCI.1
L.E- -
L.E- -
L.E- -

L.E- -
L.E- -
L.E- -
L.E- -
L.E- -
L.E- -
RAB.SuccEst.HOIn.QCI.PT
T
1.5.1 Number of E-RAB Setup Attempts in a Cell

Counters
1526726668 L.E- Number of E- BTS3900, L

RAB.AttEst.QC RAB setup BTS3900 LTE
I.1 attempts
initiated by UEs
for services
with the QCI of
1 in a cell

I.2 attempts
initiated by UEs
for services
with the QCI of
2 in a cell

I.3 attempts
initiated by UEs
for services
with the QCI of
3 in a cell



I.4 attempts
initiated by UEs
for services
with the QCI of
4 in a cell

I.5 attempts
initiated by UEs
for services
with the QCI of
5 in a cell

I.6 attempts
initiated by UEs
for services
with the QCI of
6 in a cell

I.7 attempts
initiated by UEs
for services
with the QCI of
7 in a cell

I.8 attempts
initiated by UEs
for services
with the QCI of
8 in a cell

I.9 attempts
initiated by UEs
for services
with the QCI of
9 in a cell


1526727545 L.E- Total number of BTS3900, L

RAB.AttEst E-RAB setup BTS3900 LTE
attempts
initiated by UEs
in a cell

I.PTT attempts
initiated by UEs
for PTT
services
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-RAB setup 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.
The signaling flows involved in the counter(s) comply with sections 19.2.2.3 and 19.2.2.4 in
3GPP TS 36.300 V10.6.0.
Measurement Points
As shown at point A in Figure 1-20 or Figure 1-21, 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 1-20
Figure 1-21

Formula
None
Unit
None
Related Features
L.E-RAB.AttEst.QCI.1 Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002008 Radio Bearer Management
TDLBFD-002008 Radio Bearer Management

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
L.E-RAB.AttEst Multi-mode: None

GSM: None
UMTS: None
L.E-RAB.AttEst.QCI.PTT Multi-mode: None

GSM: None
UMTS: None
LOFD-081218 Enhanced Extended QCI
TDLOFD-081215 Enhanced Extended QCI

1.5.2 Number of Successful E-RAB Setups in a Cell
Counters
1526726669 L.E- Number of BTS3900, L

RAB.SuccEst.Q successful E- BTS3900 LTE
CI.1 RAB setups
initiated by UEs
for services
with the QCI of
1 in a cell
1526726671 L.E- Number of BTS3900, L

CI.2 RAB setups
initiated by UEs
for services
with the QCI of
2 in a cell
1526726673 L.E- Number of BTS3900, L

CI.3 RAB setups
initiated by UEs
for services
with the QCI of
3 in a cell
1526726675 L.E- Number of BTS3900, L

CI.4 RAB setups
initiated by UEs
for services
with the QCI of
4 in a cell
1526726677 L.E- Number of BTS3900, L

CI.5 RAB setups
initiated by UEs
for services
with the QCI of
5 in a cell
1526726679 L.E- Number of BTS3900, L

CI.6 RAB setups
initiated by UEs
for services
with the QCI of
6 in a cell


1526726681 L.E- Number of BTS3900, L

CI.7 RAB setups
initiated by UEs
for services
with the QCI of
7 in a cell
1526726683 L.E- Number of BTS3900, L

CI.8 RAB setups
initiated by UEs
for services
with the QCI of
8 in a cell
1526726685 L.E- Number of BTS3900, L

CI.9 RAB setups
initiated by UEs
for services
with the QCI of
9 in a cell

RAB.SuccEst successful E- BTS3900 LTE
RAB setups
initiated by UEs
in a cell
1526736847 L.E- Number of BTS3900, L

CI.PTT RAB setups
initiated by UEs
for PTT
services
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.
3GPP TS 36.300 V10.6.0.

Measurement Points
As shown at point B in Figure 1-22 or Figure 1-23, 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 1-22

Figure 1-23
Formula
None
Unit
None
Related Features
L.E-RAB.SuccEst.QCI.1 Multi-mode: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None
L.E-RAB.SuccEst Multi-mode: None

GSM: None
UMTS: None
L.E-RAB.SuccEst.QCI.PTT Multi-mode: None

GSM: None
UMTS: None
1.5.3 Number of Initial E-RAB Setup Attempts in a Cell

Counters
1526728192 L.E- Number of BTS3900, L

RAB.InitAttEst. initial E-RAB BTS3900 LTE
QCI.1 setup attempts
initiated by UEs
for services
with the QCI of
1 in a cell
1526728194 L.E- Number of BTS3900, L

initiated by UEs
for services
with the QCI of
2 in a cell


1526728196 L.E- Number of BTS3900, L

initiated by UEs
for services
with the QCI of
3 in a cell
1526728198 L.E- Number of BTS3900, L

initiated by UEs
for services
with the QCI of
4 in a cell
1526728200 L.E- Number of BTS3900, L

initiated by UEs
for services
with the QCI of
5 in a cell
1526728202 L.E- Number of BTS3900, L

initiated by UEs
for services
with the QCI of
6 in a cell
1526728204 L.E- Number of BTS3900, L

initiated by UEs
for services
with the QCI of
7 in a cell
1526728206 L.E- Number of BTS3900, L

initiated by UEs
for services
with the QCI of
8 in a cell


1526728208 L.E- Number of BTS3900, L

initiated by UEs
for services
with the QCI of
9 in a cell

RAB.InitAttEst initial E-RAB BTS3900 LTE
setup attempts
initiated by UEs
in a cell
1526736849 L.E- Number of BTS3900, L

QCI.PTT setup attempts
initiated by UEs
for PTT
services
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.
The signaling flows involved in the counter(s) comply with sections 19.2.2.3 in 3GPP TS
36.300 V10.6.0.
Measurement Points
As shown at point A in Figure 1-24, 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 1-24
Formula
None
Unit
None
Related Features
L.E-RAB.InitAttEst.QCI.1 Multi-mode: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None
L.E-RAB.InitAttEst Multi-mode: None

GSM: None
UMTS: None
L.E- Multi-mode: None

RAB.InitAttEst.QCI.PTT GSM: None
UMTS: None
1.5.4 Number of Successful Initial E-RAB Setups in a Cell

Counters
1526728193 L.E- Number of BTS3900, L

RAB.InitSuccE successful BTS3900 LTE
st.QCI.1 initial E-RAB
setups initiated
by UEs for
services with
the QCI of 1 in
a cell
1526728195 L.E- Number of BTS3900, L

setups initiated
by UEs for
services with
the QCI of 2 in
a cell


1526728197 L.E- Number of BTS3900, L

setups initiated
by UEs for
services with
the QCI of 3 in
a cell
1526728199 L.E- Number of BTS3900, L

setups initiated
by UEs for
services with
the QCI of 4 in
a cell
1526728201 L.E- Number of BTS3900, L

setups initiated
by UEs for
services with
the QCI of 5 in
a cell
1526728203 L.E- Number of BTS3900, L

setups initiated
by UEs for
services with
the QCI of 6 in
a cell
1526728205 L.E- Number of BTS3900, L

setups initiated
by UEs for
services with
the QCI of 7 in
a cell


1526728207 L.E- Number of BTS3900, L

setups initiated
by UEs for
services with
the QCI of 8 in
a cell
1526728209 L.E- Number of BTS3900, L

setups initiated
by UEs for
services with
the QCI of 9 in
a cell

st initial E-RAB
setups initiated
by UEs in a cell
1526736850 L.E- Number of BTS3900, L

st.QCI.PTT initial E-RAB
setups initiated
by UEs for PTT
services
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.
The signaling flows involved in the counter(s) comply with sections 19.2.2.3 in 3GPP TS
36.300 V10.6.0.
Measurement Points
As shown at point B in Figure 1-25, 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 1-25
Formula
None
Unit
None
Related Features
L.E-RAB.InitSuccEst.QCI.1 Multi-mode: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None
L.E-RAB.InitSuccEst Multi-mode: None

GSM: None
UMTS: None

RAB.InitSuccEst.QCI.PTT GSM: None
UMTS: None
1.5.5 Number of E-RAB Setup Attempts for Incoming Handovers

in a Cell
Counters

RAB.AttEst.H E-RAB setup BTS3900 LTE
OIn attempts for
incoming
handovers in a
cell

RAB.AttEst.H RAB setups BTS3900 LTE
OIn.QCI.1 attempts for
incoming
handovers of
services with
QCI of 1 in a
cell



incoming
handovers of
services with
QCI of 2 in a
cell

incoming
handovers of
services with
QCI of 3 in a
cell

incoming
handovers of
services with
QCI of 4 in a
cell

incoming
handovers of
services with
QCI of 5 in a
cell

incoming
handovers of
services with
QCI of 6 in a
cell



incoming
handovers of
services with
QCI of 7 in a
cell

incoming
handovers of
services with
QCI of 8 in a
cell

incoming
handovers of
services with
QCI of 9 in a
cell

OIn.QCI.PTT attempts for
incoming
handovers of
PTT services
Description
The counters measure the number of E-RAB setup attempts for services with a specific QCI
ranging from 1 to 9 for incoming handovers and the total number of E-RAB setup attempts
for incoming handovers in a cell.
The signaling flows involved in the counter(s) comply with sections 10.1.2 and 19.2.2.5 in
3GPP TS 36.300 V10.6.0 and section 5.3.5.4 in 3GPP TS 36.331 V10.4.0.
Measurement Points
Figure 1-26 shows an intra-eNodeB handover, Figure 1-27 shows an X2-based handover,
Figure 1-28 shows an S1-based handover, and Figure 1-29 shows an inter-RAT incoming
handover. As shown at point A in Figure 1-26,Figure 1-27, or Figure 1-28, 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 in

Figure 1-29, the corresponding counter is incremented in the target cell based on the QCI of
each service each time the target eNodeB receives a HANDOVER REQUEST message from
the MME instructing an incoming handover from GERAN, WCDMA, or TD-SCDMA to E-
UTRAN and settting up multiple E-RABs 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 1-26
Figure 1-27

Figure 1-28
Figure 1-29
Formula
None
Unit
None

Related Features
L.E-RAB.AttEst.HOIn Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-00201801 Coverage Based Intra-
LBFD-00201802 frequency Handover
TDLBFD-00201801 Coverage Based Inter-
frequency Handover
TDLBFD-00201802
Coverage Based Intra-
frequency Handover
Coverage Based Inter-
frequency Handover
L.E-RAB.AttEst.HOIn.QCI. Multi-mode: None

1 GSM: None
UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

2 GSM: None
UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover


3 GSM: None
UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

4 GSM: None
UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

5 GSM: None
UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover


6 GSM: None
UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

7 GSM: None
UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

8 GSM: None
UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover


9 GSM: None
UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

RAB.AttEst.HOIn.QCI.PTT GSM: None
UMTS: None
frequency Handover
TDLBFD-00201802
LOFD-081218 frequency Handover
TDLOFD-081215 Coverage Based Inter-
frequency Handover
Enhanced Extended QCI
1.5.6 Number of Successful E-RAB Setups for Incoming

Handovers in a Cell
Counters

RAB.SuccEst.H successful E- BTS3900 LTE
OIn RAB setups for
incoming
handovers in a
cell


1526728778 L.E- Number of BTS3900, L

OIn.QCI.1 RAB setups for
incoming
handovers of
services with
QCI of 1 in a
cell
1526728779 L.E- Number of BTS3900, L

incoming
handovers of
services with
QCI of 2 in a
cell
1526728780 L.E- Number of BTS3900, L

incoming
handovers of
services with
QCI of 3 in a
cell
1526728781 L.E- Number of BTS3900, L

incoming
handovers of
services with
QCI of 4 in a
cell
1526728782 L.E- Number of BTS3900, L

incoming
handovers of
services with
QCI of 5 in a
cell


1526728783 L.E- Number of BTS3900, L

incoming
handovers of
services with
QCI of 6 in a
cell
1526728784 L.E- Number of BTS3900, L

incoming
handovers of
services with
QCI of 7 in a
cell
1526728785 L.E- Number of BTS3900, L

incoming
handovers of
services with
QCI of 8 in a
cell
1526728786 L.E- Number of BTS3900, L

incoming
handovers of
services with
QCI of 9 in a
cell
1526736852 L.E- Number of BTS3900, L

OIn.QCI.PTT RAB setups for
incoming
handovers of
PTT services
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.

3GPP TS 36.300 V10.6.0 and section 5.3.5.4 in 3GPP TS 36.331 V10.4.0.
Measurement Points
As shown at point C inFigure 1-30, 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 1-31, 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 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 1-32, 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 E in Figure 1-33, during an X2-based handover the corresponding counter
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 1-34, during an S1-based handover the corresponding counter
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 1-35, during an S1-based handover the corresponding counter
sends a HANDOVER NOTIFY message to the MME 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 1-36, the corresponding couter is incremented in the target cell
based on the QCI of each service each time the eNodeB sends a HANDOVER NOTIFY
message to the MME to instruct an incoming handover from GERAN, WCDMA, or TD-
SCDMA to E-UTRAN. 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 1-30
Figure 1-31

Figure 1-32
Figure 1-33

Figure 1-34
Figure 1-35

Figure 1-36
Formula
None
Unit
None
Related Features
L.E-RAB.SuccEst.HOIn Multi-mode: None

GSM: None
UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover


RAB.SuccEst.HOIn.QCI.1 GSM: None
UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover


UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover


UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

UMTS: None
frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover


RAB.SuccEst.HOIn.QCI.PT GSM: None
T
UMTS: None
frequency Handover
TDLBFD-00201802
LOFD-081218 frequency Handover
TDLOFD-081215 Coverage Based Inter-
frequency Handover
1.5.7 Number of UE-related Signaling Connection Setups over the

S1 Interface
Counters
1526728272 L.S1Sig.ConnE Number of UE- BTS3900, L

st.Att related BTS3900 LTE
signaling
connection
setup attempts
over the S1
interface
1526728273 L.S1Sig.ConnE Number of BTS3900, L

st.Succ successful UE- BTS3900 LTE
related
signaling
connection
setups over the
S1 interface
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.
The signaling flows involved in the counter(s) comply with section 8.6.2 and 8.3.3 and 8.3.1
in 3GPP TS 36.413 V10.4.0.
Measurement Points
As shown at point A in Figure 1-37, the L.S1Sig.ConnEst.Att counter is incremented by 1
each time the eNodeB sends an INITIAL UE MESSAGE message to the MME.
As shown at point B in Figure 1-37, the L.S1Sig.ConnEst.Succ counter is incremented by 1
each time the eNodeB receives the first message from the MME over the S1 interface after
sending an INITIAL UE MESSAGE message to the MME.
Figure 1-37
Formula
None
Unit
None

Related Features
L.S1Sig.ConnEst.Att Multi-mode: None

GSM: None
UMTS: None
L.S1Sig.ConnEst.Succ Multi-mode: None

GSM: None
UMTS: None
1.5.8 E-RAB Setup Duration in a Cell

Counters
1526728776 L.E- Average E- BTS3900, L

RAB.Est.Time RAB setup BTS3900 LTE
Avg duration in a
cell
1526728777 L.E- Maximum E- BTS3900, L

RAB.Est.Time RAB setup BTS3900 LTE
Max duration in a
cell
1526728879 L.E- Average initial BTS3900, L

RAB.InitEst.Ti E-RAB setup BTS3900 LTE
meAvg duration in a
cell
1526728880 L.E- Maximum BTS3900, L

RAB.InitEst.Ti initial E-RAB BTS3900 LTE
meMax setup duration
in a cell
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.

The signaling flows involved in the counter(s) comply with section 19.2.2.3, 19.2.2.4.1 in
3GPP TS 36.300 V10.6.0.
Measurement Points
As shown at points A and B in Figure 1-38, 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 1-39, 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 of the L.E-RAB.Est.TimeAvg and L.E-RAB.Est.TimeMax counters,
respectively. The E-RAB setup duration is not counted if the setup fails.
As shown at points A and B in Figure 1-38, 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 1-38

Figure 1-39
Formula
None
Unit
ms
Related Features
L.E-RAB.Est.TimeAvg Multi-mode: None

GSM: None
UMTS: None
L.E-RAB.Est.TimeMax Multi-mode: None

GSM: None
UMTS: None

L.E-RAB.InitEst.TimeAvg Multi-mode: None

GSM: None
UMTS: None
L.E-RAB.InitEst.TimeMax Multi-mode: None

GSM: None
UMTS: None
1.5.9 Number of E-RAB Recovery Attempts When UEs switch

from the Uplink Out-of-Synchronization State to Uplink-
Synchronized State
Counters

RAB.StateTran RAB recovery BTS3900 LTE
s.Unsyn2Syn.A attempts when
tt UEs switch
from the uplink
out-of-
synchronization
state to the
uplink-
synchronized
state
Description
The counter measures the number of E-RAB recovery attempts when UEs switch from the
uplink out-of-synchronization state to the uplink-synchronized state. When a UE finish
performing random access and the eNodeB is about to allocate uplink PUCCH resources for
the UE, the eNodeB attempts to recover E-RABs for the UE.
Measurement Points
As shown at point A in Figure 1-40, when UEs transmit from the uplink out-of-
synchronization state to the uplink-synchronized state, the L.E-

RAB.StateTrans.Unsyn2Syn.Att counter is incremented by the number of E-RABs of a UE

each time the eNodeB is about to send an RRC Connection Reconfiguration message to a UE
to allocate uplink PUCCH resources for the UE when the UE finishes performing random
access.
Figure 1-40
Formula
None
Unit
None
Related Features

RAB.StateTrans.Unsyn2Syn GSM: None
.Att
UMTS: None

1.5.10 Number of Successfully Recovered E-RABs When UEs

switch from the Uplink Out-of-Synchronization State to Uplink-
Synchronized State
Counters
1526729658 L.E- Number of BTS3900, L

RAB.StateTran successfully BTS3900 LTE
s.Unsyn2Syn.S recovered E-
ucc RABs when
UEs switch
from the uplink
out-of-
synchronization
state to the
uplink-
synchronized
state
Description
The counter measures the number of times that an E-RAB is recovered successfully when
UEs switch from the uplink out-of-synchronization state to uplink-synchronized state. The E-
RABs are recovered for a UE when the eNodeB finishes uplink PUCCH resource allocation
for the UE. The counter is incremented by the number of recovered E-RABs.
Measurement Points
As shown at point B in Figure 1-41, when UEs switch from the uplink out-of-synchronization
state to the uplink-synchronized state, the L.E-RAB.StateTrans.Unsyn2Syn.Succ counter is
incremented by the number of successfully recovered E-RABs each time the eNodeB receives
an RRC Connection Reconfiguration Complete message from a UE which indicating that the
eNodeB finishes uplink PUCCH resource allocation for the UE.

Figure 1-41
Formula
None
Unit
None
Related Features

RAB.StateTrans.Unsyn2Syn GSM: None
.Succ
UMTS: None
1.6 E-RAB Release Measurement (E-RAB.Rel.Cell)

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
1-42 and Figure 1-43 shows the measurement points of an E-RAB release procedure during a
non-handover process. Figure 1-44 shows the measurement points of an E-RAB release
procedure initiated by the source eNodeB during a handover.

Figure 1-42
Figure 1-43

Figure 1-44
Counters
Description
1526726686 L.E- Number of abnormal BTS3900:

RAB.AbnormRel. releases of activated V100R008C00
QCI.1 E-RABs for services BTS3900 LTE:
with the QCI of 1 in version earlier than
a cell V100R003C00
1526726687 L.E- Number of normal BTS3900:

RAB.NormRel.QC E-RAB releases for V100R008C00
I.1 services with the BTS3900 LTE:
QCI of 1 in a cell version earlier than
V100R003C00

a cell V100R003C00

V100R003C00


Description

a cell V100R003C00

V100R003C00

a cell V100R003C00

V100R003C00

a cell V100R003C00

V100R003C00

a cell V100R003C00

V100R003C00


Description

a cell V100R003C00

V100R003C00

a cell V100R003C00

V100R003C00

a cell V100R003C00

V100R003C00

RAB.NormRel.HO E-RAB releases for V100R008C00
Out.QCI.1 outgoing handovers BTS3900 LTE:
of services with the version earlier than



Description








RAB.AbnormRel. E-RAB releases for V100R008C00
HOOut.QCI.1 outgoing handovers BTS3900 LTE:


Description










Description

RAB.AbnormRel abnormal releases of V100R008C00
activated E-RABs BTS3900 LTE:
initiated by the version earlier than
eNodeB V100R003C00
1526727547 L.E-RAB.NormRel Total number of BTS3900:

normal E-RAB V100R008C00
releases initiated by BTS3900 LTE:
the eNodeB in a cell version earlier than
V100R003C00

RAB.NormRel.HO normal E-RAB V100R008C00
Out releases for outgoing BTS3900 LTE:

RAB.AbnormRel. abnormal E-RAB V100R008C00
HOOut releases for outgoing BTS3900 LTE:

RAB.AbnormRel.R releases of activated V100R008C00
adio E-RABs due to BTS3900 LTE:
faults at the radio V100R003C00
network layer

RAB.AbnormRel.T releases of activated V100R008C00
NL E-RABs due to BTS3900 LTE:
faults at the V100R003C00
transport network
layer

RAB.AbnormRel.C releases of activated V100R008C00
ong E-RABs due to BTS3900 LTE:
network congestion V100R003C00

HOFailure E-RABs due to BTS3900 LTE:
handover failures V100R003C00
1526728292 L.E- Number of MME- BTS3900:

RAB.AbnormRel. triggered abnormal V100R008C00
MME releases of activated BTS3900 LTE:
E-RABs V100R003C00


Description

RAB.AbnormRel.e abnormal releases of V100R008C00
NBTot E-RABs initiated by BTS3900 LTE:
the eNodeB V100R005C00
1526728436 L.E- Number of released BTS3900:

RAB.Release.Unsy E-RABs of UEs in V100R008C00
n the uplink out-of- BTS3900 LTE:
state

RAB.Num.Syn2Un RABs in UE V100R008C00
syn contexts when the BTS3900 LTE:
UEs switch from the V100R008C00
uplink synchronized
state to the uplink
out-of-
synchronization
state in a cell

RAB.Rel.eNodeB.Q releases initiated by V100R008C00
CI.1 the eNodeB for BTS3900 LTE:
services with QCI of V100R008C00
1 in a cell

2 in a cell

3 in a cell

4 in a cell

5 in a cell


Description

6 in a cell

7 in a cell

8 in a cell

9 in a cell

RAB.Rel.eNodeB RAB releases V100R008C00
initiated by the BTS3900 LTE:
eNodeB in a cell V100R008C00

RAB.Rel.MME.QC releases initiated by V100R008C00
I.1 the MME for BTS3900 LTE:
1 in a cell

2 in a cell

3 in a cell

4 in a cell


Description

5 in a cell

6 in a cell

7 in a cell

8 in a cell

9 in a cell

RAB.Rel.MME RAB releases V100R008C00
initiated by the BTS3900 LTE:
MME V100R008C00
1526728808 L.E- Number of BTS3900:

RAB.Left.QCI.1 remaining E-RABs V100R008C00
for services with BTS3900 LTE:
1526728809 L.E- Number of BTS3900:

1526728810 L.E- Number of BTS3900:



Description
1526728811 L.E- Number of BTS3900:

1526728812 L.E- Number of BTS3900:

1526728813 L.E- Number of BTS3900:

1526728814 L.E- Number of BTS3900:

1526728815 L.E- Number of BTS3900:

1526728816 L.E- Number of BTS3900:

1526728817 L.E-RAB.Left Total number of BTS3900:

remaining E-RABs V100R008C00
in a cell BTS3900 LTE:
V100R008C00

RAB.Rel.S1Reset.e E-RAB releases V100R008C00
NodeB.QCI.1 initiated by the BTS3900 LTE:
eNodeB for services V100R008C00
with QCI of 1
because of the S1
RESET in a cell

with QCI of 2
because of the S1
RESET in a cell


Description

with QCI of 3
because of the S1
RESET in a cell

with QCI of 4
because of the S1
RESET in a cell

with QCI of 5
because of the S1
RESET in a cell

with QCI of 6
because of the S1
RESET in a cell

with QCI of 7
because of the S1
RESET in a cell

with QCI of 8
because of the S1
RESET in a cell


Description

with QCI of 9
because of the S1
RESET in a cell

RAB.Rel.S1Reset.e abnormal E-RAB V100R008C00
NodeB releases initiated by BTS3900 LTE:
the eNodeB because V100R008C00
of the S1 RESET in
a cell

RAB.Rel.S1Reset. E-RAB releases V100R008C00
MME.QCI.1 initiated by the BTS3900 LTE:
MME with QCI of 1 V100R008C00
because of the S1
RESET in a cell

because of the S1
RESET in a cell

because of the S1
RESET in a cell

because of the S1
RESET in a cell

because of the S1
RESET in a cell


Description

because of the S1
RESET in a cell

because of the S1
RESET in a cell

because of the S1
RESET in a cell

because of the S1
RESET in a cell

RAB.Rel.S1Reset. abnormal E-RAB V100R008C00
MME releases initiated by BTS3900 LTE:
the MME because of V100R008C00
the S1 RESET in a
cell

RAB.AbnormRel. MME-triggered V100R008C01
MMETot abnormal E-RAB BTS3900 LTE:
releases V100R008C01

adio.SRBReset E-RABs because the BTS3900 LTE:
RLC PDU for an V100R009C00
SRB has been
retransmitted for the
maximum number
of times


Description

adio.DRBReset E-RABs because the BTS3900 LTE:
RLC PDU for a V100R009C00
DRB has been
maximum number
of times

adio.ULSyncFail E-RABs due to BTS3900 LTE:
uplink V100R009C00
resynchronization
failures

adio.UuNoReply E-RABs because of BTS3900 LTE:
no responses from V100R009C00
the UE

MME.EUtranGen E-RABs triggered BTS3900 LTE:
by the MME with V100R009C00
the release cause of
Release due to E-
UTRAN Generated
Reason

ong.PreEmp E-RABs because of BTS3900 LTE:
radio resource V100R009C00
preemption

ong.Load E-RABs because of BTS3900 LTE:
overload

NL.PreEmp E-RABs because of BTS3900 LTE:
transport resource V100R009C00
preemption


Description

NL.Load E-RABs because of BTS3900 LTE:
transport resource V100R009C00
overload

MMETot.VoIP releases of E-RABs BTS3900 LTE:
for voice services V100R009C00

adio.SRBReset.VoI E-RABs for voice BTS3900 LTE:
P services because the V100R009C00
RLC PDU for an
SRB has been
maximum number
of times

adio.NoReply.VoIP E-RABs for voice BTS3900 LTE:
services because of V100R009C00
no responses from
the UE

adio.ULSyncFail.V E-RABs for voice BTS3900 LTE:
oIP services because of V100R009C00
uplink
resynchronization
failures

MME.EUtranGen. E-RABs for voice BTS3900 LTE:
VoIP services triggered by V100R009C00
the MME with the
release cause of
Release due to E-
UTRAN Generated
Reason


Description

adio.VoIP E-RABs for voice BTS3900 LTE:
faults at the radio
network layer

HOFailure.VoIP E-RABs for voice BTS3900 LTE:
handover failures

ong.VoIP E-RABs for voice BTS3900 LTE:
radio network
congestion

MME.VoIP releases of activated BTS3900 LTE:
E-RABs for voice V100R009C00
services

NL.VoIP E-RABs for voice BTS3900 LTE:
faults at the
transport network
layer

ong.PreEmp.VoIP E-RABs for voice BTS3900 LTE:
radio resource
preemption

ong.Load.VoIP E-RABs for voice BTS3900 LTE:
radio resource
overload


Description

NL.PreEmp.VoIP E-RABs for voice BTS3900 LTE:
transport resource
preemption

NL.Load.VoIP E-RABs for voice BTS3900 LTE:
transport resource
overload

RAB.AbnormRel.e releases of E-RABs V100R009C00
NBTot.QCI.1 for services with the BTS3900 LTE:








Description



RAB.AbnormRel.U releases of activated V100R009C00
lWeak.VoIP E-RABs for voice BTS3900 LTE:
uplink weak
coverage

MME.QCI.2 releases of activated BTS3900 LTE:
E-RABs for services V100R009C00
with the QCI of 2

with the QCI of 3

with the QCI of 4

with the QCI of 5

with the QCI of 6

with the QCI of 7


Description

with the QCI of 8

with the QCI of 9

Other E-RABs due to other BTS3900 LTE:
reasons V100R010C00

Other.VoIP E-RABs for voice BTS3900 LTE:
services due to other V100R010C00
reasons

adio.Other E-RABs due to other BTS3900 LTE:
faults at the radio V100R010C00
network layer

adio.Other.VoIP E-RABs for voice BTS3900 LTE:
faults at the radio
network layer

NL.Other E-RABs due to other BTS3900 LTE:
faults at the V100R010C00
transport network
lay

NL.Other.VoIP E-RABs for voice BTS3900 LTE:
faults at the
transport network
layer


Description

ong.Other E-RABs due to other BTS3900 LTE:
congestion reaso

ong.Other.VoIP E-RABs for voice BTS3900 LTE:
radio resource
congestion reasons

RAB.AbnormRel. releases of E-RABs V100R010C10
QCI.PTT for PTT services BTS3900 LTE:
V100R010C10

I.PTT PTT services in a BTS3900 LTE:
cell V100R010C10

Out.QCI.PTT outgoing handovers BTS3900 LTE:

HOOut.QCI.PTT outgoing handovers BTS3900 LTE:

RAB.AbnormRel. initiated abnormal V100R010C10
MME.HOOut.QCI. releases of E-RABs BTS3900 LTE:
1 for services with a V100R010C10
QCI of 1 during
handover executions

QCI of 2 during
handover executions


Description

QCI of 3 during
handover executions

QCI of 4 during
handover executions

QCI of 5 during
handover executions

QCI of 6 during
handover executions

QCI of 7 during
handover executions

QCI of 8 during
handover executions

QCI of 9 during
handover executions


Description

RAB.AbnormRel. MME-initiated V100R010C10
MME.HOOut abnormal releases of BTS3900 LTE:
E-RABs during V100R010C10
handover executions
1526737848 L.E- Number of eNodeB- BTS3900:

RAB.Rel.eNodeB.U triggered E-RAB V100R010C10
serinact releases with the BTS3900 LTE:
cause value of User V100R010C10
Inactivity
The E-RAB.Rel.Cell function subset contains of counters related to E-RAB release. Some of
these counters can be categorized in terms of the QCI. In terms of the procedure, the E-RAB
releases can be categorized as E-RAB release in non-handover scenarios, E-RAB release in
handover scenarios, and E-RAB release because of S1 interface reset. The E-RAB releases in
handover scenarios can be further categorized as normal release and abnormal release. In
terms of the triggering object, the E-RAB releases because of S1 interface reset can be
categorized as E-RAB release initiated by the eNodeB and E-RAB release initiated by the
MME. The E-RAB releases in non-handover scenarios can be further categorized as E-RAB
release initiated by the eNodeB and E-RAB release initiated by the MME. The E-RAB
releases in non-handover scenarios can be also further categorized as normal release and
abnormal release. The abnormal E-RAB release in non-handover scenarios can be caused by
radio network layer cause, transport network layer cause, network congestion, and handover
failure. Each release cause is further categorized in terms of the sub-release cause. Each
abnormal release cause is categorized in terms of whether the E-RAB is for VoIP service or
not. The following table shows the parent-child relationship of the counters.
Root Counter Level-1 Level-2 Level-3 Level-4

Counter Counter Counter Counter
L.E- L.E- L.E- L.E- -

RAB.AbnormR RAB.AbnormR RAB.AbnormR RAB.AbnormR
el el.QCI.1 el.Radio.VoIP el.Radio.SRBR
eset.VoIP
L.E- -
RAB.AbnormR
el.Radio.NoRep
ly.VoIP
L.E- -
RAB.AbnormR
el.Radio.ULSyn
cFail.VoIP


L.E- L.E- -
RAB.AbnormR RAB.AbnormR
el.Cong.VoIP el.Cong.PreEm
p.VoIP
L.E- -
RAB.AbnormR
el.Cong.Load.V
oIP
L.E- L.E- -
el.TNL.VoIP el.TNL.PreEmp
.VoIP
L.E- -
RAB.AbnormR
el.TNL.Load.V
oIP
L.E- - -
RAB.AbnormR
el.HOFailure.V
oIP
L.E- - -
RAB.AbnormR
el.UlWeak.VoIP
L.E- - - -
RAB.AbnormR
el.QCI.2
L.E- - - -
RAB.AbnormR
el.QCI.3
L.E- - - -
RAB.AbnormR
el.QCI.4
L.E- - - -
RAB.AbnormR
el.QCI.5
L.E- - - -
RAB.AbnormR
el.QCI.6
L.E- - - -
RAB.AbnormR
el.QCI.7


L.E- - - -
RAB.AbnormR
el.QCI.8
L.E- - - -
RAB.AbnormR
el.QCI.9
L.E- L.E- L.E- L.E- -

RAB.AbnormR RAB.AbnormR RAB.AbnormR RAB.AbnormR
el el.Radio el.Radio.SRBR el.Radio.SRBR
eset eset.VoIP
L.E- - -
RAB.AbnormR
el.Radio.DRBR
eset
L.E- L.E- -
el.Radio.ULSyn el.Radio.ULSyn
cFail cFail.VoIP
L.E- L.E- -
el.Radio.UuNo el.Radio.NoRep
Reply ly.VoIP
L.E- L.E- -
el.Radio.Other el.Radio.Other.
VoIP
L.E- L.E- L.E- -

RAB.AbnormR RAB.AbnormR RAB.AbnormR
el.Radio el.Radio.VoIP el.Radio.SRBR
eset.VoIP
L.E- -
RAB.AbnormR
el.Radio.NoRep
ly.VoIP
L.E- -
RAB.AbnormR
el.Radio.ULSyn
cFail.VoIP
L.E- L.E- L.E- -

el.TNL el.TNL.PreEmp el.TNL.PreEmp
.VoIP


L.E- L.E- -
el.TNL.Load el.TNL.Load.V
oIP
L.E- L.E- -
el.TNL.Other el.TNL.Other.V
oIP
L.E- L.E- L.E- -

el.TNL el.TNL.VoIP el.TNL.PreEmp
.VoIP
L.E- -
RAB.AbnormR
el.TNL.Load.V
oIP
L.E- L.E- L.E- -

el.Cong el.Cong.PreEm el.Cong.PreEm
p p.VoIP
L.E- L.E- -
el.Cong.Load el.Cong.Load.V
oIP
L.E- L.E- -
el.Cong.Other el.Cong.Other.
VoIP
L.E- L.E- L.E- -

el.Cong el.Cong.VoIP el.Cong.PreEm
p.VoIP
L.E- -
RAB.AbnormR
el.Cong.Load.V
oIP
L.E- L.E- - -
el.HOFailure el.HOFailure.V
oIP


L.E- L.E- - -
el.Other el.Other.VoIP
L.E- L.E- L.E- L.E- L.E-

RAB.NormRel RAB.NormRel. RAB.Rel.MME RAB.AbnormR RAB.AbnormR
QCI.1 .QCI.1 el.MMETot.VoI el.MME.VoIP
P
L.E- L.E- - -
RAB.NormRel. RAB.Rel.MME
QCI.2 .QCI.2
L.E- L.E- - -
QCI.3 .QCI.3
L.E- L.E- - -
QCI.4 .QCI.4
L.E- L.E- - -
QCI.5 .QCI.5
L.E- L.E- - -
QCI.6 .QCI.6
L.E- L.E- - -
QCI.7 .QCI.7
L.E- L.E- - -
QCI.8 .QCI.8
L.E- L.E- - -
QCI.9 .QCI.9
L.E- - - -
RAB.NormRel.
QCI.PTT
L.E- L.E- L.E- L.E- L.E-

RAB.NormRel RAB.Rel.MME RAB.Rel.MME RAB.AbnormR RAB.AbnormR
.QCI.1 el.MMETot.VoI el.MME.VoIP
P
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- L.E- L.E- L.E-

RAB.Rel.MME RAB.AbnormR RAB.AbnormR RAB.AbnormR
el.MMETot el.MME el.MME.EUtran
Gen
L.E-
RAB.AbnormR
el.MME.VoIP
L.E-
RAB.AbnormR
el.MME.QCI.2
L.E-
RAB.AbnormR
el.MME.QCI.3
L.E-
RAB.AbnormR
el.MME.QCI.4
L.E-
RAB.AbnormR
el.MME.QCI.5


L.E-
RAB.AbnormR
el.MME.QCI.6
L.E-
RAB.AbnormR
el.MME.QCI.7
L.E-
RAB.AbnormR
el.MME.QCI.8
L.E-
RAB.AbnormR
el.MME.QCI.9
L.E- L.E- L.E-

el.MMETot el.MMETot.VoI el.MME.VoIP
P
L.E- L.E- - - -
RAB.NormRel. RAB.NormRel.
HOOut 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.NormRel.
HOOut.QCI.PT
T
L.E- L.E- - - -
el.HOOut el.HOOut.QCI.
1
L.E- - - -
RAB.AbnormR
el.HOOut.QCI.
2
L.E- - - -
RAB.AbnormR
el.HOOut.QCI.
3
L.E- - - -
RAB.AbnormR
el.HOOut.QCI.
4
L.E- - - -
RAB.AbnormR
el.HOOut.QCI.
5
L.E- - - -
RAB.AbnormR
el.HOOut.QCI.
6
L.E- - - -
RAB.AbnormR
el.HOOut.QCI.
7
L.E- - - -
RAB.AbnormR
el.HOOut.QCI.
8


L.E- - - -
RAB.AbnormR
el.HOOut.QCI.
9
L.E- - - -
RAB.AbnormR
el.HOOut.QCI.
PTT
L.E- L.E- - - -
el.eNBTot el.eNBTot.QCI.
1
L.E- - - -
RAB.AbnormR
el.eNBTot.QCI.
2
L.E- - - -
RAB.AbnormR
el.eNBTot.QCI.
3
L.E- - - -
RAB.AbnormR
el.eNBTot.QCI.
4
L.E- - - -
RAB.AbnormR
el.eNBTot.QCI.
5
L.E- - - -
RAB.AbnormR
el.eNBTot.QCI.
6
L.E- - - -
RAB.AbnormR
el.eNBTot.QCI.
7
L.E- - - -
RAB.AbnormR
el.eNBTot.QCI.
8


L.E- - - -
RAB.AbnormR
el.eNBTot.QCI.
9
L.E- L.E- - - -
RAB.Rel.eNod RAB.Rel.eNod
eB eB.QCI.1
L.E- - - -
RAB.Rel.eNod
eB.QCI.2
L.E- - - -
RAB.Rel.eNod
eB.QCI.3
L.E- - - -
RAB.Rel.eNod
eB.QCI.4
L.E- - - -
RAB.Rel.eNod
eB.QCI.5
L.E- - - -
RAB.Rel.eNod
eB.QCI.6
L.E- - - -
RAB.Rel.eNod
eB.QCI.7
L.E- - - -
RAB.Rel.eNod
eB.QCI.8
L.E- - - -
RAB.Rel.eNod
eB.QCI.9
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- L.E- - - -
RAB.Rel.S1Res RAB.Rel.S1Res
et.eNodeB et.eNodeB.QCI.
1
L.E- - - -
RAB.Rel.S1Res
et.eNodeB.QCI.
2
L.E- - - -
RAB.Rel.S1Res
et.eNodeB.QCI.
3
L.E- - - -
RAB.Rel.S1Res
et.eNodeB.QCI.
4
L.E- - - -
RAB.Rel.S1Res
et.eNodeB.QCI.
5
L.E- - - -
RAB.Rel.S1Res
et.eNodeB.QCI.
6


L.E- - - -
RAB.Rel.S1Res
et.eNodeB.QCI.
7
L.E- - - -
RAB.Rel.S1Res
et.eNodeB.QCI.
8
L.E- - - -
RAB.Rel.S1Res
et.eNodeB.QCI.
9
L.E- L.E- - - -
RAB.Rel.S1Res RAB.Rel.S1Res
et.MME et.MME.QCI.1
L.E- - - -
RAB.Rel.S1Res
et.MME.QCI.2
L.E- - - -
RAB.Rel.S1Res
et.MME.QCI.3
L.E- - - -
RAB.Rel.S1Res
et.MME.QCI.4
L.E- - - -
RAB.Rel.S1Res
et.MME.QCI.5
L.E- - - -
RAB.Rel.S1Res
et.MME.QCI.6
L.E- - - -
RAB.Rel.S1Res
et.MME.QCI.7
L.E- - - -
RAB.Rel.S1Res
et.MME.QCI.8
L.E- - - -
RAB.Rel.S1Res
et.MME.QCI.9


L.E- L.E- - - -
el.MME.HOOu el.MME.HOOu
t t.QCI.1
L.E- - - -
RAB.AbnormR
el.MME.HOOu
t.QCI.2
L.E- - - -
RAB.AbnormR
el.MME.HOOu
t.QCI.3
L.E- - - -
RAB.AbnormR
el.MME.HOOu
t.QCI.4
L.E- - - -
RAB.AbnormR
el.MME.HOOu
t.QCI.5
L.E- - - -
RAB.AbnormR
el.MME.HOOu
t.QCI.6
L.E- - - -
RAB.AbnormR
el.MME.HOOu
t.QCI.7
L.E- - - -
RAB.AbnormR
el.MME.HOOu
t.QCI.8
L.E- - - -
RAB.AbnormR
el.MME.HOOu
t.QCI.9
Level-4 Counter Level-5 Counter
L.E-RAB.AbnormRel.MME.VoIP L.E-
RAB.AbnormRel.MME.EUtranGen.VoIP

Level-4 Counter Level-5 Counter
L.E-RAB.AbnormRel.MME.EUtranGen L.E-
1.6.1 Number of Abnormal E-RAB Releases in a Cell

Counters
1526726686 L.E- Number of BTS3900, L

RAB.AbnormR abnormal BTS3900 LTE
el.QCI.1 releases of
activated E-
RABs for
services with
the QCI of 1 in
a cell
1526726688 L.E- Number of BTS3900, L

activated E-
RABs for
services with
the QCI of 2 in
a cell
1526726690 L.E- Number of BTS3900, L

activated E-
RABs for
services with
the QCI of 3 in
a cell


1526726692 L.E- Number of BTS3900, L

activated E-
RABs for
services with
the QCI of 4 in
a cell
1526726694 L.E- Number of BTS3900, L

activated E-
RABs for
services with
the QCI of 5 in
a cell
1526726696 L.E- Number of BTS3900, L

activated E-
RABs for
services with
the QCI of 6 in
a cell
1526726698 L.E- Number of BTS3900, L

activated E-
RABs for
services with
the QCI of 7 in
a cell
1526726700 L.E- Number of BTS3900, L

activated E-
RABs for
services with
the QCI of 8 in
a cell


1526726702 L.E- Number of BTS3900, L

activated E-
RABs for
services with
the QCI of 9 in
a cell
1526730539 L.E- Number of BTS3900, L

el.eNBTot.QCI. releases of E-
1 RABs for
services with
the QCI of 1 in
a cell
1526730540 L.E- Number of BTS3900, L

2 RABs for
services with
the QCI of 2 in
a cell
1526730541 L.E- Number of BTS3900, L

3 RABs for
services with
the QCI of 3 in
a cell
1526730542 L.E- Number of BTS3900, L

4 RABs for
services with
the QCI of 4 in
a cell
1526730543 L.E- Number of BTS3900, L

5 RABs for
services with
the QCI of 5 in
a cell


1526730544 L.E- Number of BTS3900, L

6 RABs for
services with
the QCI of 6 in
a cell
1526730545 L.E- Number of BTS3900, L

7 RABs for
services with
the QCI of 7 in
a cell
1526730546 L.E- Number of BTS3900, L

8 RABs for
services with
the QCI of 8 in
a cell
1526730547 L.E- Number of BTS3900, L

9 RABs for
services with
the QCI of 9 in
a cell
1526736853 L.E- Number of BTS3900, L

el.QCI.PTT releases of E-
RABs for PTT
services
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.
The signaling flows involved in the counter(s) comply with sections 19.2.2.2, 19.2.2.4.3 and
19.2.2.4.4 in 3GPP TS 36.300 V10.6.0.

Measurement Points
As shown at point A in Figure 1-45, the corresponding counter (L.E-
RAB.AbnormRel.eNBTot.QCI.1 to L.E-RAB.AbnormRel.eNBTot.QCI.9) is incremented
based on the QCI of each service when the eNodeB sends an E-RAB RELEASE
INDICATION message to the MME and the release cause is not "Normal Release", "Detach",
"User Inactivity","Om-Intervention", "CS Fallback triggered", "UE Not Available for PS
Service", "Inter-RAT Redirection", or "Successful Handover". If the eNodeB determines that
the E-RAB to be released carries data, a counter of L.E-RAB.AbnormRel.QCI.1 to L.E-
RAB.AbnormRel.QCI.9 is incremented. 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 1-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 (L.E-RAB.AbnormRel.eNBTot.QCI.1 to L.E-
RAB.AbnormRel.eNBTot.QCI.9) is incremented by the number of E-RABs to be released
based on the QCI of each service if the release cause is not "Normal Release", "Detach",
"User Inactivity","Om-Intervention", "CS Fallback triggered", "UE Not Available for PS
Service", "Inter-RAT Redirection", "Time Critical Handover", or "Handover Cancelled". If the
eNodeB determines that the E-RABs to be released carry data, a counter of L.E-
RAB.AbnormRel.QCI.1 to L.E-RAB.AbnormRel.QCI.9 is incremented. When the MME
sends a UE CONTEXT RELEASE COMMAND message to the eNodeB, the corresponding
counter is not incremented.
Figure 1-45

Figure 1-46
Formula
None
Unit
None
Related Features
L.E-RAB.AbnormRel.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

RAB.AbnormRel.eNBTot.Q GSM: None
CI.1
UMTS: None


CI.2
UMTS: None

CI.3
UMTS: None

CI.4
UMTS: None

CI.5
UMTS: None

CI.6
UMTS: None

CI.7
UMTS: None

CI.8
UMTS: None


CI.9
UMTS: None

RAB.AbnormRel.QCI.PTT GSM: None
UMTS: None
1.6.2 Number of Normal E-RAB Releases in a Cell

Counters
1526726687 L.E- Number of BTS3900, L

RAB.NormRel. normal E-RAB BTS3900 LTE
QCI.1 releases for
services with
the QCI of 1 in
a cell
1526726689 L.E- Number of BTS3900, L

QCI.2 releases for
services with
the QCI of 2 in
a cell
1526726691 L.E- Number of BTS3900, L

QCI.3 releases for
services with
the QCI of 3 in
a cell


1526726693 L.E- Number of BTS3900, L

QCI.4 releases for
services with
the QCI of 4 in
a cell
1526726695 L.E- Number of BTS3900, L

QCI.5 releases for
services with
the QCI of 5 in
a cell
1526726697 L.E- Number of BTS3900, L

QCI.6 releases for
services with
the QCI of 6 in
a cell
1526726699 L.E- Number of BTS3900, L

QCI.7 releases for
services with
the QCI of 7 in
a cell
1526726701 L.E- Number of BTS3900, L

QCI.8 releases for
services with
the QCI of 8 in
a cell
1526726703 L.E- Number of BTS3900, L

QCI.9 releases for
services with
the QCI of 9 in
a cell

RAB.NormRel normal E-RAB BTS3900 LTE
releases
initiated by the
eNodeB in a
cell


1526736858 L.E- Number of BTS3900, L

QCI.PTT releases for
PTT services in
a cell
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.
The signaling flows involved in the counter(s) comply with sections 19.2.2.2, 19.2.2.4.3 and
19.2.2.4.4 in 3GPP TS 36.300 V10.6.0.
Measurement Points
As shown at point A in Figure 1-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","Om-Intervention",

"CS Fallback triggered", "UE Not Available for PS Service", "Inter-RAT Redirection", or
"Redirection towards 1xRTT".
(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 1-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 1-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","Om-Intervention",

"CS Fallback triggered", "UE Not Available for PS Service", "Inter-RAT Redirection", "Time
Critical Handover", "Handover Cancelled", or "Redirection towards 1xRTT".
(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 1-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 1-47
Figure 1-48

Figure 1-49
Formula
None
Unit
None
Related Features
L.E-RAB.NormRel.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
L.E-RAB.NormRel Multi-mode: None

GSM: None
UMTS: None


RAB.NormRel.QCI.PTT GSM: None
UMTS: None
1.6.3 Number of Normal E-RAB Releases for Outgoing Handovers

in a Cell
Counters
1526727317 L.E- Number of BTS3900, L

HOOut.QCI.1 releases for
outgoing
handovers of
services with
the QCI of 1 in
a cell
1526727318 L.E- Number of BTS3900, L

outgoing
handovers of
services with
the QCI of 2 in
a cell
1526727319 L.E- Number of BTS3900, L

outgoing
handovers of
services with
the QCI of 3 in
a cell


1526727320 L.E- Number of BTS3900, L

outgoing
handovers of
services with
the QCI of 4 in
a cell
1526727321 L.E- Number of BTS3900, L

outgoing
handovers of
services with
the QCI of 5 in
a cell
1526727322 L.E- Number of BTS3900, L

outgoing
handovers of
services with
the QCI of 6 in
a cell
1526727323 L.E- Number of BTS3900, L

outgoing
handovers of
services with
the QCI of 7 in
a cell
1526727324 L.E- Number of BTS3900, L

outgoing
handovers of
services with
the QCI of 8 in
a cell


1526727325 L.E- Number of BTS3900, L

outgoing
handovers of
services with
the QCI of 9 in
a cell

HOOut releases for
outgoing
handovers in a
cell
1526736859 L.E- Number of BTS3900, L

HOOut.QCI.PT releases for
T outgoing
handovers of
PTT services
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.
3GPP TS 36.300 V10.6.0, section 5.3.5.4 in 3GPP TS 36.331 V10.4.0, and section 8.3.3 in
3GPP TS 36.413 V10.4.0.
Measurement Points
Figure 1-52 shows an S1-based handover, Figure 1-53 shows a handover from E-UTRAN to
WCDMA network, GERAN, or TD-SCDMA network, Figure 1-54 shows an intra-eNodeB
handover where the RRC connection is reestablished to the target cell for the UE, Figure 1-55
shows an X2-based handover where the RRC connection is reestablished to the target eNodeB
for the UE, and Figure 1-56 shows an S1-based handover where the RRC connection is
reestablished to the target eNodeB for the UE.
As shown at point C in Figure 1-50, Figure 1-51, Figure 1-52, or Figure 1-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 source cell is accumulated as
the value of the L.E-RAB.NormRel.HOOut counter.
As shown at point C in Figure 1-54, Figure 1-55, or Figure 1-56, 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 the RRC connection is reestablished to the target eNodeB 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 source cell is accumulated as
the value of the L.E-RAB.NormRel.HOOut counter.
Figure 1-50
Figure 1-51

Figure 1-52
Figure 1-53

Figure 1-54
Figure 1-55

Figure 1-56
Formula
None
Unit
None

Related Features

RAB.NormRel.HOOut.QCI. GSM: None
1
UMTS: None
LTE: LOFD-001019 PS Inter-RAT Mobility
LBFD-00201801 between E-UTRAN and
UTRAN
LBFD-00201802
TDLOFD-001019 frequency Handover
TDLBFD-00201802 frequency Handover
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover

2
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover


3
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover

4
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover


5
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover

6
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover


7
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover

8
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover


9
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover
L.E-RAB.NormRel.HOOut Multi-mode: None

GSM: None
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover


PTT
UMTS: None
UTRAN
LBFD-00201802
LOFD-081218 PS Inter-RAT Mobility
TDLOFD-081215 between E-UTRAN and
UTRAN
frequency Handover
frequency Handover
1.6.4 Number of Abnormal E-RAB Releases for Outgoing

Handovers in a Cell
Counters
1526727326 L.E- Number of BTS3900, L

RAB.AbnormR abnormal E- BTS3900 LTE
el.HOOut.QCI. RAB releases
1 for outgoing
handovers of
services with
the QCI of 1 in
a cell


1526727327 L.E- Number of BTS3900, L

2 for outgoing
handovers of
services with
the QCI of 2 in
a cell
1526727328 L.E- Number of BTS3900, L

3 for outgoing
handovers of
services with
the QCI of 3 in
a cell
1526727329 L.E- Number of BTS3900, L

4 for outgoing
handovers of
services with
the QCI of 4 in
a cell
1526727330 L.E- Number of BTS3900, L

5 for outgoing
handovers of
services with
the QCI of 5 in
a cell
1526727331 L.E- Number of BTS3900, L

6 for outgoing
handovers of
services with
the QCI of 6 in
a cell


1526727332 L.E- Number of BTS3900, L

7 for outgoing
handovers of
services with
the QCI of 7 in
a cell
1526727333 L.E- Number of BTS3900, L

8 for outgoing
handovers of
services with
the QCI of 8 in
a cell
1526727334 L.E- Number of BTS3900, L

9 for outgoing
handovers of
services with
the QCI of 9 in
a cell

el.HOOut RAB releases
for outgoing
handovers in a
cell
1526736860 L.E- Number of BTS3900, L

PTT for outgoing
handovers of
PTT services
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.

3GPP TS 36.413 V10.4.0.
Measurement Points
Figure 1-59 shows an S1-based handover, and Figure 1-60 shows a handover from E-
UTRAN to WCDMA network, GERAN, or TD-SCDMA network. As shown at point C in
Figure 1-57, Figure 1-58, Figure 1-59, or Figure 1-60, 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 1-57

Figure 1-58
Figure 1-59

Figure 1-60
Formula
None
Unit
None

Related Features

RAB.AbnormRel.HOOut.Q GSM: None
CI.1
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover

CI.2
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover


CI.3
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover

CI.4
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover


CI.5
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover

CI.6
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover


CI.7
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover

CI.8
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover


CI.9
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover

RAB.AbnormRel.HOOut GSM: None
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover


CI.PTT
UMTS: None
UTRAN
LBFD-00201802
UTRAN
frequency Handover
frequency Handover
1.6.5 Total Number of Abnormal E-RAB Releases in a Cell

Counters

el releases of
activated E-
RABs initiated
by the eNodeB

el.eNBTot releases of E-
RABs initiated
by the eNodeB
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.
The signaling flows involved in the counter(s) comply with section 19.2.2.2, 19.2.2.4.3,
19.2.2.4.4 in 3GPP TS 36.300 V10.6.0.
Measurement Points
As shown at point A in Figure 1-61, 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","Om-
Intervention", "CS Fallback triggered", "UE Not Available for PS Service", "Inter-RAT
Redirection", "Successful Handover", or "Redirection towards 1xRTT". 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 1-61, 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","Om-Intervention",
"CS Fallback triggered", "UE Not Available for PS Service", "Inter-RAT Redirection",
"Successful Handover", or "Redirection towards 1xRTT".
(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.
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","Om-Intervention", "CS Fallback triggered", "UE Not
Available for PS Service", "Inter-RAT Redirection", "Successful Handover", "Time critical
handover", or Redirection towards 1xRTT"". 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.
REQUEST message to the MME, all E-RABs of the UE are released. In this case, the L.E-
RAB.AbnormRel counter is incremented each time the following two conditions are met:
(1) The release cause is not "Normal Release", "Detach", "User Inactivity", "Om-
Intervention","CS Fallback triggered", "UE Not Available for PS Service", "Inter-RAT
Redirection", "Time Critical Handover", "Handover Cancelled", or "Redirection towards
1xRTT".
(2) The eNodeB determines that the E-RABs to be released carry data.
If multiple E-RABs of the UE are released, the L.E-RAB.AbnormRel 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.

Figure 1-61
Figure 1-62
Formula
None
Unit
None
Related Features
L.E-RAB.AbnormRel Multi-mode: None

GSM: None
UMTS: None


RAB.AbnormRel.eNBTot GSM: None
UMTS: None
1.6.6 Number of Abnormal E-RAB Releases for Different Causes

in a Cell
Counters
1526728282 L.E- Number of BTS3900, L

el.Radio releases of
activated E-
RABs due to
faults at the
radio network
layer
1526728283 L.E- Number of BTS3900, L

el.TNL releases of
activated E-
RABs due to
faults at the
transport
network layer
1526728284 L.E- Number of BTS3900, L

el.Cong releases of
activated E-
RABs due to
network
congestion
1526728291 L.E- Number of BTS3900, L

el.HOFailure releases of
activated E-
RABs due to
handover
failures


1526728292 L.E- Number of BTS3900, L

RAB.AbnormR MME-triggered BTS3900 LTE
el.MME abnormal
releases of
activated E-
RABs

el.MMETot abnormal E-
RAB releases
1526729549 L.E- Number of BTS3900, L

el.Radio.SRBR releases of
eset activated E-
RABs because
the RLC PDU
for an SRB has
been
retransmitted
for the
maximum
number of
times
1526729550 L.E- Number of BTS3900, L

el.Radio.DRBR releases of
eset activated E-
RABs because
the RLC PDU
for a DRB has
been
retransmitted
for the
maximum
number of
times
1526729551 L.E- Number of BTS3900, L

el.Radio.ULSyn releases of
cFail activated E-
RABs due to
uplink
resynchronizati
on failures


1526729552 L.E- Number of BTS3900, L

el.Radio.UuNo releases of
Reply activated E-
RABs because
of no responses
from the UE
1526729911 L.E- Number of BTS3900, L

el.MME.EUtran releases of
Gen activated E-
RABs triggered
by the MME
with the release
cause of
Release due to
E-UTRAN
Generated
Reason
1526729912 L.E- Number of BTS3900, L

el.Cong.PreEm releases of
p activated E-
RABs because
of radio
resource
preemption
1526729913 L.E- Number of BTS3900, L

el.Cong.Load releases of
activated E-
RABs because
of radio
resource
overload
1526729914 L.E- Number of BTS3900, L

el.TNL.PreEmp releases of
activated E-
RABs because
of transport
resource
preemption


1526729915 L.E- Number of BTS3900, L

el.TNL.Load releases of
activated E-
RABs because
of transport
resource
overload
1526729916 L.E- Number of BTS3900, L

el.MMETot.VoI abnormal
P releases of E-
RABs for voice
services
1526729917 L.E- Number of BTS3900, L

el.Radio.SRBR releases of
eset.VoIP activated E-
RABs for voice
services
because the
RLC PDU for
an SRB has
been
retransmitted
for the
maximum
number of
times
1526729918 L.E- Number of BTS3900, L

el.Radio.NoRep releases of
ly.VoIP activated E-
RABs for voice
services
because of no
responses from
the UE


1526729919 L.E- Number of BTS3900, L

el.Radio.ULSyn releases of
cFail.VoIP activated E-
RABs for voice
services
because of
uplink
resynchronizati
on failures
1526729920 L.E- Number of BTS3900, L

el.MME.EUtran releases of
Gen.VoIP activated E-
RABs for voice
services
triggered by the
MME with the
release cause of
Release due to
E-UTRAN
Generated
Reason
1526729921 L.E- Number of BTS3900, L

el.Radio.VoIP releases of
activated E-
RABs for voice
services
because of
faults at the
radio network
layer
1526729922 L.E- Number of BTS3900, L

el.HOFailure.V releases of
oIP activated E-
RABs for voice
services
because of
handover
failures


1526729923 L.E- Number of BTS3900, L

el.Cong.VoIP releases of
activated E-
RABs for voice
services
because of
radio network
congestion
1526729924 L.E- Number of BTS3900, L

el.MME.VoIP abnormal
releases of
activated E-
RABs for voice
services
1526729925 L.E- Number of BTS3900, L

el.TNL.VoIP releases of
activated E-
RABs for voice
services
because of
faults at the
transport
network layer
1526729926 L.E- Number of BTS3900, L

el.Cong.PreEm releases of
p.VoIP activated E-
RABs for voice
services
because of
radio resource
preemption
1526729927 L.E- Number of BTS3900, L

el.Cong.Load.V releases of
oIP activated E-
RABs for voice
services
because of
radio resource
overload


1526729928 L.E- Number of BTS3900, L

el.TNL.PreEmp releases of
.VoIP activated E-
RABs for voice
services
because of
transport
resource
preemption
1526729929 L.E- Number of BTS3900, L

el.TNL.Load.V releases of
oIP activated E-
RABs for voice
services
because of
transport
resource
overload
1526730862 L.E- Number of BTS3900, L

el.UlWeak.VoIP releases of
activated E-
RABs for voice
services
because of
uplink weak
coverage
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.
The signaling flows involved in the counter(s) comply with section 19.2.2.2 and 19.2.2.4.3
and 19.2.2.4. in 3GPP TS 36.300 V10.6.0.
Measurement Points
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","Om-Intervention", "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 eNodeB

determines that the corresponding E-RAB carries data, and the L.E-
RAB.AbnormRel.MME.EUtranGen counter is incremented each time the release cause is
"Release due to E-UTRAN Generated Reason" and the eNodeB determines that the
corresponding E-RAB carries data. If the E-RAB RELEASE COMMAND message requests
to release multiple E-RABs at the same time, the corresponding counters are incremented by
the number of requested E-RAB releases in the message.
the L.E-RAB.AbnormRel.MMETot.VoIP counter is incremented each time the following
conditions are met: (1) The eNodeB receives an E-RAB RELEASE COMMAND message
from the MME. (2) This message is used to release the E-RABs for services with the QCI of 1
and other QCIs. (3) The release cause is not "Normal Release", "Detach", "User
Inactivity","Om-Intervention", "CS Fallback triggered", "UE Not Available for PS Service",
"Inter-RAT Redirection", or "Successful Handover". In addition, the L.E-
RAB.AbnormRel.MME.VoIP counter is incremented each time the eNodeB determines that
the corresponding E-RAB for services with the QCI of 1 carries data, and the L.E-
RAB.AbnormRel.MME.EUtranGen.VoIP counter is incremented each time the release cause
is "Release due to E-UTRAN Generated Reason" and the eNodeB determines that the
corresponding E-RAB for services with the QCI of 1 carries data. If the E-RAB RELEASE
COMMAND message requests to release multiple E-RABs for services with the QCI of 1 at
the same time, the corresponding counters are incremented by the number of requested E-
RAB releases in the message.
As shown at point A in Figure 1-64, 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 each time the release cause is not "Normal Release", "Detach", "User
Inactivity","Om-Intervention", "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 eNodeB determines that the
corresponding E-RAB carries data, and the L.E-RAB.AbnormRel.MME.EUtranGen counter
is incremented each time the release cause is "Release due to E-UTRAN Generated Reason"
and the eNodeB determines that the corresponding E-RAB carries data. If multiple E-RABs
have been set up for the UE, the corresponding counters are incremented by the number of E-
RABs.
As shown at point A in Figure 1-64, 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.VoIP
counter is incremented each time the E-RABs for services with the QCI of 1 and other QCIs
are released and release cause is not "Normal Release", "Detach", "User Inactivity","Om-
Redirection", or "Successful Handover". In addition, the L.E-RAB.AbnormRel.MME.VoIP
counter is incremented each time the eNodeB determines that the corresponding E-RAB for
services with the QCI of 1 carries data, and the L.E-RAB.AbnormRel.MME.EUtranGen.VoIP
counter is incremented each time the release cause is "Release due to E-UTRAN Generated
Reason" and the eNodeB determines that the corresponding E-RAB for services with the QCI
of 1 carries data. If multiple E-RABs for services with the QCI of 1 have been set up for the
UE, the corresponding counters are incremented by the number of E-RABs.
As shown at point A in Figure 1-65, 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 corresponding E-
RAB is released because of faults at the radio network layer and the eNodeB determines that

the E-RAB carries data. In addition, the L.E-RAB.AbnormRel.Radio.DRBReset counter is

incremented each time the corresponding E-RAB is released because the RLC PDU for a
DRB has been retransmitted for the maximum number of times.
(2) The L.E-RAB.AbnormRel.TNL counter is incremented each time the corresponding E-

RAB is released because of faults at the transport network layer and the eNodeB determines
that the E-RAB carries data. In addition, the L.E-RAB.AbnormRel.TNL.PreEmp counter is
incremented each time the corresponding E-RAB is released because of transport resource
preemption, and the L.E-RAB.AbnormRel.TNL.Load is incremented each time the
corresponding E-RAB is released because of transport resource overload.
(3) The L.E-RAB.AbnormRel.Cong counter is incremented each time the corresponding E-

RAB is released because of radio network congestion and the eNodeB determines that the E-
RAB carries data. In addition, the L.E-RAB.AbnormRel.Cong.PreEmp counter is
incremented each time the corresponding E-RAB is released because of radio resource
preemption, and the L.E-RAB.AbnormRel.Cong.Load counter is incremented each time the
corresponding E-RAB is released because of radio resource overload.
For details about faults at the radio network layer and the transport network layer as well as
radio network congestion, see 3GPP TS 36.413. If the E-RAB RELEASE INDICATION
message requests to release multiple E-RABs at the same time, the corresponding counters are
incremented by the number of requested E-RAB releases based on the release cause.
As shown at point A in Figure 1-65, when the eNodeB sends the MME an E-RAB RELEASE
INDICATION message that is used to release E-RABs for services with the QCI of 1 and
other QCIs, the counters are measured as follows:
(1) The L.E-RAB.AbnormRel.Radio.VoIP counter is incremented each time the eNodeB

determines that the E-RAB with the QCI of 1 carries data and the corresponding E-RAB is
released because of faults at the radio network layer.
(2) The L.E-RAB.AbnormRel.TNL.VoIP counter is incremented each time the eNodeB

determines that the E-RAB for services with the QCI of 1 carries data and the corresponding
E-RAB is released because of faults at the transport network layer. In addition, the L.E-
RAB.AbnormRel.TNL.PreEmp.VoIP counter is incremented each time the corresponding E-
RAB is released because of transport resource preemption, and the L.E-
RAB.AbnormRel.TNL.Load.VoIP is incremented each time the corresponding E-RAB is
released because of transport resource overload.
(3) The L.E-RAB.AbnormRel.Cong.VoIP counter is incremented each time the eNodeB

determines that the E-RAB for services with the QCI of 1 carries data and the corresponding
E-RAB is released because of radio network congestion. In addition, the L.E-
RAB.AbnormRel.Cong.PreEmp.VoIP counter is incremented each time the corresponding E-
RAB is released because of radio resource preemption, and the L.E-
RAB.AbnormRel.Cong.Load.VoIP counter is incremented each time the corresponding E-
RAB is released because of radio resource overload.
radio network congestion, see 3GPP TS 36.413. If the E-RAB RELEASE INDICATION
message requests to release multiple of E-RABs for services with the QCI of 1 at the same
time, the corresponding counters are incremented by the number of requested E-RAB releases
based on the release cause.
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 eNodeB determines
that the corresponding E-RABs carry data and the E-RABs are released because of faults at
the radio network layer. In addition, the L.E-RAB.AbnormRel.Radio.DRBReset counter is
incremented each time the E-RABs are released because the RLC PDU for a DRB has been
retransmitted for the maximum number of times, the L.E-RAB.AbnormRel.Radio.SRBReset
counter is incremented each time the E-RABs are released because the RLC PDU for an SRB
has been retransmitted for the maximum number of times, the L.E-
RAB.AbnormRel.Radio.ULSyncFail counter is incremented each time the E-RABs are
released because of uplink resynchronization failures, the L.E-
RAB.AbnormRel.Radio.UuNoReply counter is incremented each time the E-RABs are
released because of signaling exchange failures over the air interface (excluding in the
handover or RRC connection reestablishment procedures).
(2) The L.E-RAB.AbnormRel.TNL counter is incremented each time the eNodeB determines
that the corresponding E-RABs carry data and the E-RABs are released because of faults at
the transport network layer. In addition, the L.E-RAB.AbnormRel.TNL.PreEmp counter is
incremented each time the E-RABs are released because of transport resource preemption,
and the L.E-RAB.AbnormRel.TNL.Load counter is incremented each time the E-RABs are
released because of transport resource overload.
(3) The L.E-RAB.AbnormRel.Cong counter is incremented each time the eNodeB determines
that corresponding E-RABs carry data and the E-RABs are released because of radio network
congestion. In addition, the L.E-RAB.AbnormRel.Cong.PreEmp counter is incremented each
time the corresponding E-RABs are released because of radio resource preemption, and the
L.E-RAB.AbnormRel.Cong.Load counter is incremented each time the E-RABs are released
because of radio resource overload.
(4) The L.E-RAB.AbnormRel.HOFailure counter is incremented each time the eNodeB
determines that the corresponding E-RABs carry data and the E-RABs are released because of
handover failures.
radio network congestion, see 3GPP TS 36.413. 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
counters are not incremented.
REQUEST message to the MME, all E-RABs of the UE are released. The counters are
(1) The L.E-RAB.AbnormRel.Radio.VoIP counter is incremented each time the following
conditions are met: a. The E-RABs of the UE include E-RABs for services with the QCI of 1.
b. The eNodeB determines that the corresponding E-RABs for services with the QCI of 1
carry data. c. The E-RABs are released because of faults at the radio network layer. In
addition, the L.E-RAB.AbnormRel.Radio.SRBReset.VoIP counter is incremented each time
the E-RABs are released because the RLC PDU for an SRB has been retransmitted for the
maximum number of times, the L.E-RAB.AbnormRel.Radio.ULSyncFail.VoIP counter is
incremented each time the E-RABs are released because of uplink resynchronization failures,
the L.E-RAB.AbnormRel.Radio.NoReply.VoIP counter is incremented each time the E-RABs
are released because of signaling exchange failures over the air interface (excluding in the
handover or RRC connection reestablishment procedures).
(2) The L.E-RAB.AbnormRel.TNL.VoIP counter is incremented each time the eNodeB
determines that the corresponding E-RABs for services with the QCI of 1 carry data and the
E-RABs are released because of faults at the transport network layer. In addition, the L.E-

RAB.AbnormRel.TNL.PreEmp.VoIP counter is incremented each time the E-RABs are

released because of transport resource preemption, and the L.E-
RAB.AbnormRel.TNL.Load.VoIP counter is incremented each time the E-RABs are released
because of transport resource overload.
(3) The L.E-RAB.AbnormRel.Cong.VoIP counter is incremented each time the eNodeB
determines that corresponding E-RABs for services with the QCI of 1 carry data and the E-
RABs are released because of radio network congestion. In addition, the L.E-
RAB.AbnormRel.Cong.PreEmp.VoIP counter is incremented each time the corresponding E-
RABs are released because of radio resource preemption, and the L.E-
RAB.AbnormRel.Cong.Load.VoIP counter is incremented each time the corresponding E-
RABs are released because of radio resource overload.
(4) The L.E-RAB.AbnormRel.HOFailure.VoIP counter is incremented each time the eNodeB
determines that the corresponding E-RABs carry data and the E-RABs are released because of
handover failures.
(5) The L.E-RAB.AbnormRel.UlWeak.VoIP counter is incremented each time the eNodeB
determines that the UE is in an uplink weak coverage area and the E-RAB of QCI 1 carries
data when the release cause is "Radio Connection With UE Lost" or the release is caused by a
handover failure.
radio network congestion, see 3GPP TS 36.413. The corresponding counters are incremented
by the number of requested releases of E-RABs for services with the QCI of 1 based on the
release cause. When the MME sends a UE CONTEXT RELEASE COMMAND message to
the eNodeB, the corresponding counters are not incremented.
Figure 1-63
Figure 1-64

Figure 1-65
Figure 1-66
Formula
None
Unit
None
Related Features
L.E-RAB.AbnormRel.Radio Multi-mode: None

GSM: None
UMTS: None

L.E-RAB.AbnormRel.TNL Multi-mode: None

GSM: None
UMTS: None
L.E-RAB.AbnormRel.Cong Multi-mode: None

GSM: None
UMTS: None
LBFD-002024 Congestion Control
TDLBFD-002024 Congestion Control
LOFD-00102901 Radio/transport resource
TDLOFD-00102901 pre-emption
Radio/transport resource
pre-emption

RAB.AbnormRel.HOFailure GSM: None
UMTS: None
L.E-RAB.AbnormRel.MME Multi-mode: None

GSM: None
UMTS: None

RAB.AbnormRel.MMETot GSM: None
UMTS: None

RAB.AbnormRel.Radio.SR GSM: None
BReset
UMTS: None


RAB.AbnormRel.Radio.DR GSM: None
BReset
UMTS: None

RAB.AbnormRel.Radio.UL GSM: None
SyncFail
UMTS: None

RAB.AbnormRel.Radio.Uu GSM: None
NoReply
UMTS: None

RAB.AbnormRel.MME.EUt GSM: None
ranGen
UMTS: None

RAB.AbnormRel.Cong.Pre GSM: None
Emp
UMTS: None
pre-emption


RAB.AbnormRel.Cong.Loa GSM: None
d
UMTS: None

RAB.AbnormRel.TNL.PreE GSM: None
mp
UMTS: None

RAB.AbnormRel.TNL.Load GSM: None
UMTS: None

RAB.AbnormRel.MMETot. GSM: None
VoIP
UMTS: None

RAB.AbnormRel.Radio.SR GSM: None
BReset.VoIP
UMTS: None

RAB.AbnormRel.Radio.No GSM: None
Reply.VoIP
UMTS: None

RAB.AbnormRel.Radio.UL GSM: None
SyncFail.VoIP
UMTS: None


RAB.AbnormRel.MME.EUt GSM: None
ranGen.VoIP
UMTS: None

RAB.AbnormRel.Radio.VoI GSM: None
P
UMTS: None

RAB.AbnormRel.HOFailure GSM: None
.VoIP
UMTS: None

RAB.AbnormRel.Cong.VoI GSM: None
P
UMTS: None
pre-emption

RAB.AbnormRel.MME.VoI GSM: None
P
UMTS: None

RAB.AbnormRel.TNL.VoIP GSM: None
UMTS: None


RAB.AbnormRel.Cong.Pre GSM: None
Emp.VoIP
UMTS: None
pre-emption

RAB.AbnormRel.Cong.Loa GSM: None
d.VoIP
UMTS: None

RAB.AbnormRel.TNL.PreE GSM: None
mp.VoIP
UMTS: None

RAB.AbnormRel.TNL.Load GSM: None
.VoIP
UMTS: None

RAB.AbnormRel.UlWeak.V GSM: None
oIP
UMTS: None

1.6.7 Number of Released E-RABs of UEs in the Uplink Out-of-

Synchronization State
Counters
1526728436 L.E- Number of BTS3900, L

RAB.Release.U released E- BTS3900 LTE
nsyn RABs of UEs in
the uplink out-
of-
synchronization
state
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 1-67, Figure 1-68, Figure 1-69, or Figure 1-70, 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 sends an E-RAB RELEASE INDICATION message to the MME.
- 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 sends a UE CONTEXT RELEASE REQUEST 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 1-67

Figure 1-68
Figure 1-69
Figure 1-70
Formula
None
Unit
None

Related Features
L.E-RAB.Release.Unsyn Multi-mode: None

GSM: None
UMTS: None
1.6.8 Total Number of E-RABs of UEs When the UEs switch from
the Uplink-synchronized State to the Uplink Out-of-
Synchronization State
Counters

RAB.Num.Syn E-RABs in UE BTS3900 LTE
2Unsyn contexts when
the UEs switch
from the uplink
synchronized
state to the
uplink out-of-
synchronization
state in a cell
Description
The counter measures the total number of E-RABs of UEs when the UEs switch from the
uplink-synchronized state to the uplink out-of-synchronization state in a cell.
Measurement Points
When UEs switch 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
L.E-RAB.Num.Syn2Unsyn Multi-mode: None

GSM: None
UMTS: None
1.6.9 Number of E-RAB Releases Initiated by the eNodeB in a

Cell
Counters

RAB.Rel.eNod RAB releases BTS3900 LTE
eB.QCI.1 initiated by the
eNodeB for
services with
QCI of 1 in a
cell

eNodeB for
services with
QCI of 2 in a
cell

eNodeB for
services with
QCI of 3 in a
cell



eNodeB for
services with
QCI of 4 in a
cell

eNodeB for
services with
QCI of 5 in a
cell

eNodeB for
services with
QCI of 6 in a
cell

eNodeB for
services with
QCI of 7 in a
cell

eNodeB for
services with
QCI of 8 in a
cell

eNodeB for
services with
QCI of 9 in a
cell



RAB.Rel.eNod E-RAB releases BTS3900 LTE
eB initiated by the
eNodeB in a
cell
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.
The signaling flows involved in the counter(s) comply with section 19.2.2.2 and 19.2.2.4.4 in
3GPP TS 36.300 V10.6.0.
Measurement Points
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.
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 1-71

Figure 1-72
Formula
None
Unit
None
Related Features
L.E-RAB.Rel.eNodeB.QCI. Multi-mode: None

1 GSM: None
UMTS: None

2 GSM: None
UMTS: None

3 GSM: None
UMTS: None


4 GSM: None
UMTS: None

5 GSM: None
UMTS: None

6 GSM: None
UMTS: None

7 GSM: None
UMTS: None

8 GSM: None
UMTS: None

9 GSM: None
UMTS: None
L.E-RAB.Rel.eNodeB Multi-mode: None

GSM: None
UMTS: None

1.6.10 Number of E-RAB Releases Initiated by the MME in a Cell
Counters

RAB.Rel.MME RAB releases BTS3900 LTE
.QCI.1 initiated by the
MME for
services with
QCI of 1 in a
cell

MME for
services with
QCI of 2 in a
cell

MME for
services with
QCI of 3 in a
cell

MME for
services with
QCI of 4 in a
cell

MME for
services with
QCI of 5 in a
cell

MME for
services with
QCI of 6 in a
cell



MME for
services with
QCI of 7 in a
cell

MME for
services with
QCI of 8 in a
cell

MME for
services with
QCI of 9 in a
cell

RAB.Rel.MME E-RAB releases BTS3900 LTE
initiated by the
MME
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.
The signaling flows involved in the counter(s) comply with section 19.2.2.2 and 19.2.2.4.3 in
3GPP TS 36.300 V10.6.0.
Measurement Points
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.
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 1-73
Figure 1-74
Formula
None
Unit
None
Related Features
L.E-RAB.Rel.MME.QCI.1 Multi-mode: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None
L.E-RAB.Rel.MME Multi-mode: None

GSM: None
UMTS: None
1.6.11 Number of Remaining E-RABs in a Cell

Counters
1526728808 L.E- Number of BTS3900, L

RAB.Left.QCI. remaining E- BTS3900 LTE
1 RABs for
services with
QCI of 1 in a
cell
1526728809 L.E- Number of BTS3900, L

2 RABs for
services with
QCI of 2 in a
cell
1526728810 L.E- Number of BTS3900, L

3 RABs for
services with
QCI of 3 in a
cell
1526728811 L.E- Number of BTS3900, L

4 RABs for
services with
QCI of 4 in a
cell


1526728812 L.E- Number of BTS3900, L

5 RABs for
services with
QCI of 5 in a
cell
1526728813 L.E- Number of BTS3900, L

6 RABs for
services with
QCI of 6 in a
cell
1526728814 L.E- Number of BTS3900, L

7 RABs for
services with
QCI of 7 in a
cell
1526728815 L.E- Number of BTS3900, L

8 RABs for
services with
QCI of 8 in a
cell
1526728816 L.E- Number of BTS3900, L

9 RABs for
services with
QCI of 9 in a
cell
1526728817 L.E-RAB.Left Total number of BTS3900, L

remaining E- BTS3900 LTE
RABs in a cell
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
L.E-RAB.Left.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
L.E-RAB.Left Multi-mode: None

GSM: None
UMTS: None
1.6.12 Number of E-RAB Releases Initiated by the eNodeB

Because of the S1 RESET in a Cell
Counters
1526728818 L.E- Number of BTS3900, L

RAB.Rel.S1Res abnormal E- BTS3900 LTE
et.eNodeB.QCI. RAB releases
1 initiated by the
eNodeB for
services with
QCI of 1
because of the
S1 RESET in a
cell


1526728819 L.E- Number of BTS3900, L

2 initiated by the
eNodeB for
services with
QCI of 2
because of the
S1 RESET in a
cell
1526728820 L.E- Number of BTS3900, L

3 initiated by the
eNodeB for
services with
QCI of 3
because of the
S1 RESET in a
cell
1526728821 L.E- Number of BTS3900, L

4 initiated by the
eNodeB for
services with
QCI of 4
because of the
S1 RESET in a
cell
1526728822 L.E- Number of BTS3900, L

5 initiated by the
eNodeB for
services with
QCI of 5
because of the
S1 RESET in a
cell


1526728823 L.E- Number of BTS3900, L

6 initiated by the
eNodeB for
services with
QCI of 6
because of the
S1 RESET in a
cell
1526728824 L.E- Number of BTS3900, L

7 initiated by the
eNodeB for
services with
QCI of 7
because of the
S1 RESET in a
cell
1526728825 L.E- Number of BTS3900, L

8 initiated by the
eNodeB for
services with
QCI of 8
because of the
S1 RESET in a
cell
1526728826 L.E- Number of BTS3900, L

9 initiated by the
eNodeB for
services with
QCI of 9
because of the
S1 RESET in a
cell



et.eNodeB RAB releases
initiated by the
eNodeB
because of the
S1 RESET in a
cell
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.
The signaling flows involved in the counter(s) comply with section 19.2.2.7.1a in 3GPP TS
36.300 V10.6.0.
Measurement Points
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 1-75

Formula
None
Unit
None
Related Features

RAB.Rel.S1Reset.eNodeB. GSM: None
QCI.1
UMTS: None

QCI.2
UMTS: None

QCI.3
UMTS: None

QCI.4
UMTS: None

QCI.5
UMTS: None

QCI.6
UMTS: None


QCI.7
UMTS: None

QCI.8
UMTS: None

QCI.9
UMTS: None

RAB.Rel.S1Reset.eNodeB GSM: None
UMTS: None
1.6.13 Number of E-RAB Releases Initiated by the MME Because

of the S1 RESET in a Cell
Counters
1526728828 L.E- Number of BTS3900, L

et.MME.QCI.1 RAB releases
initiated by the
MME with QCI
of 1 because of
the S1 RESET
in a cell


1526728829 L.E- Number of BTS3900, L

initiated by the
MME with QCI
of 2 because of
the S1 RESET
in a cell
1526728830 L.E- Number of BTS3900, L

initiated by the
MME with QCI
of 3 because of
the S1 RESET
in a cell
1526728831 L.E- Number of BTS3900, L

initiated by the
MME with QCI
of 4 because of
the S1 RESET
in a cell
1526728832 L.E- Number of BTS3900, L

initiated by the
MME with QCI
of 5 because of
the S1 RESET
in a cell
1526728833 L.E- Number of BTS3900, L

initiated by the
MME with QCI
of 6 because of
the S1 RESET
in a cell


1526728834 L.E- Number of BTS3900, L

initiated by the
MME with QCI
of 7 because of
the S1 RESET
in a cell
1526728835 L.E- Number of BTS3900, L

initiated by the
MME with QCI
of 8 because of
the S1 RESET
in a cell
1526728836 L.E- Number of BTS3900, L

initiated by the
MME with QCI
of 9 because of
the S1 RESET
in a cell

et.MME RAB releases
initiated by the
MME because
of the S1
RESET in a cell
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.
The signaling flows involved in the counter(s) comply with section 19.2.2.7.1b in 3GPP TS
36.300 V10.6.0.
Measurement Points
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 1-76
Formula
None
Unit
None
Related Features

RAB.Rel.S1Reset.MME.QC GSM: None
I.1
UMTS: None

I.2
UMTS: None


I.3
UMTS: None

I.4
UMTS: None

I.5
UMTS: None

I.6
UMTS: None

I.7
UMTS: None

I.8
UMTS: None

I.9
UMTS: None


RAB.Rel.S1Reset.MME GSM: None
UMTS: None
1.6.14 Number of MME-triggered Abnormal E-RAB Releases

Counters
1526730864 L.E- Number of BTS3900, L

el.MME.QCI.2 abnormal
releases of
activated E-
RABs for
services with
the QCI of 2
1526730865 L.E- Number of BTS3900, L

releases of
activated E-
RABs for
services with
the QCI of 3
1526730866 L.E- Number of BTS3900, L

releases of
activated E-
RABs for
services with
the QCI of 4
1526730867 L.E- Number of BTS3900, L

releases of
activated E-
RABs for
services with
the QCI of 5


1526730868 L.E- Number of BTS3900, L

releases of
activated E-
RABs for
services with
the QCI of 6
1526730869 L.E- Number of BTS3900, L

releases of
activated E-
RABs for
services with
the QCI of 7
1526730870 L.E- Number of BTS3900, L

releases of
activated E-
RABs for
services with
the QCI of 8
1526730871 L.E- Number of BTS3900, L

releases of
activated E-
RABs for
services with
the QCI of 9
Description
The counters measure the number of MME-triggered abnormal releases of activated E-RABs
per QCI in a cell.
Measurement Points
the counters L.E-RAB.AbnormRel.MME.QCI.2 to L.E-RAB.AbnormRel.MME.QCI.9 are
incremented based on the QCI each time the following conditions are met: (1) The eNodeB
receives an E-RAB RELEASE COMMAND message from the MME. (2) The release cause is
not "Normal Release", "Detach", "User Inactivity", "Om-Intervention","CS Fallback
triggered", "UE Not Available for PS Service", "Inter-RAT Redirection", or "Successful

Handover". (3) The eNodeB determines that the corresponding E-RAB carries data. If the E-
RAB RELEASE COMMAND message requests to release multiple E-RABs at the same time,
the corresponding counters are incremented by the number of requested E-RAB releases in
the message.
As shown at point A in Figure 1-78, in a UE context release procedure, the eNodeB releases
all E-RABs of the UE when the eNodeB receives a UE CONTEXT RELEASE COMMAND
message from the MME. In this case, the counters L.E-RAB.AbnormRel.MME.QCI.2 to L.E-
RAB.AbnormRel.MME.QCI.9 are incremented based on the QCI each time the release cause
is not "Normal Release", "Detach", "User Inactivity","Om-Intervention", "CS Fallback
triggered", "UE Not Available for PS Service", "Inter-RAT Redirection", or "Successful
Handover" and the eNodeB determines that the corresponding E-RAB carries data. If multiple
E-RABs have been set up for the UE, the corresponding counters are incremented by the
number of E-RABs.
Figure 1-77
Figure 1-78
Formula
None
Unit
None

Related Features

RAB.AbnormRel.MME.QC GSM: None
I.2
UMTS: None

I.3
UMTS: None

I.4
UMTS: None

I.5
UMTS: None

I.6
UMTS: None

I.7
UMTS: None

I.8
UMTS: None


I.9
UMTS: None
1.6.15 Number of Abnormal E-RAB Releases for Other Reasons in

a Cell
Counters
1526732938 L.E- Number of BTS3900, L

el.Other releases of
activated E-
RABs due to
other reasons
1526732939 L.E- Number of BTS3900, L

el.Other.VoIP releases of
activated E-
RABs for voice
services due to
other reasons
1526732940 L.E- Number of BTS3900, L

el.Radio.Other releases of
activated E-
RABs due to
other faults at
the radio
network layer
1526732941 L.E- Number of BTS3900, L

el.Radio.Other. releases of
VoIP activated E-
RABs for voice
services due to
other faults at
the radio
network layer


1526732942 L.E- Number of BTS3900, L

el.TNL.Other releases of
activated E-
RABs due to
other faults at
the transport
network lay
1526732943 L.E- Number of BTS3900, L

el.TNL.Other.V releases of
oIP activated E-
RABs for voice
services due to
other faults at
the transport
network layer
1526732944 L.E- Number of BTS3900, L

el.Cong.Other releases of
activated E-
RABs due to
other radio
resource
congestion
reaso
1526732945 L.E- Number of BTS3900, L

el.Cong.Other. releases of
VoIP activated E-
RABs for voice
services due to
other radio
resource
congestion
reasons
Description
The counters measure the number of abnormal E-RAB releases for other causes 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.
The signaling flows involved in the counter(s) comply with sections 19.2.2.2, 19.2.2.4.3, and
19.2.2.4.4 in 3GPP TS 36.300 (V10.6.0).

Measurement Points
As shown at point A in Figure 1-81, the eNodeB sends an E-RAB RELEASE INDICATION
message with a cause value other than "Normal Release", "Detach", "User Inactivity", "Om-
Intervention","CS Fallback triggered", "UE Not Available for PS Service", "Inter-RAT
Redirection", or "Successful Handover", and the corresponding E-RAB carries data. If the
cause for the abnormal E-RAB release is not radio network layer fault, transport layer fault,
radio network congestion, or handover failure, the L.E-RAB.AbnormRel.Other counter is
incremented by 1. If the cause is radio network layer fault and the sub-cause is not DRB RLC
retransmission times reaching the maximum number, SRB RLC retransmission times reaching
the maximum number, uplink resynchronization failure, and air interface processing error (not
including those during handover and RRC reestablishment), the L.E-
RAB.AbnormRel.Radio.Other counter is incremented by 1. If the failure cause is transport
layer fault and the sub-cause is not transport resource being preempted or transport resource
insufficiency, the L.E-RAB.AbnormRel.TNL.Other counter is incremented by 1. If the failure
cause is radio network congestion and the sub-cause is not radio network resource being
preempted or radio network resource insufficiency, the L.E-RAB.AbnormRel.Cong.Other
counter is incremented by 1.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 required E-RAB releases for each cause.
As shown at point A in Figure 1-81, the eNodeB sends an E-RAB RELEASE INDICATION
message with a cause value other than "Normal Release", "Detach", "User Inactivity","Om-
Redirection", or "Successful Handover", and the corresponding E-RAB for services of QCI 1
carries data. If the cause for the abnormal E-RAB release is not radio network layer fault,
transport layer fault, radio network congestion, or handover failure, the L.E-
RAB.AbnormRel.Other.VoIP counter is incremented by 1. If the cause is radio network layer
fault and the sub-cause is not SRB RLC retransmission times reaching the maximum number,
uplink resynchronization failure, and air interface processing error (not including those during
handover and RRC reestablishment), the L.E-RAB.AbnormRel.Radio.Other.VoIP counter is
incremented by 1. If the failure cause is transport layer fault and the sub-cause is not transport
resource being preempted or transport resource insufficiency, the L.E-
RAB.AbnormRel.TNL.Other.VoIP counter is incremented by 1. If the failure cause is radio
network congestion and the sub-cause is not radio network resource being preempted or radio
network resource insufficiency, the L.E-RAB.AbnormRel.Cong.Other.VoIP counter is
incremented by 1.If the E-RAB RELEASE INDICATION message requires the release of
multiple E-RABs for services of QCI of 1 at the same time, the corresponding counter is
incremented according to the number of required E-RAB releases for each cause.
REQUEST message to the MME, all E-RABs of the UE are released.
If the cause value is not "Normal Release", "Detach", "User Inactivity","Om-Intervention",
critical handover", or "Handover Cancelled" , and the corresponding E-RAB carries data, the
counters are measured as follows:
If the cause for the abnormal E-RAB release is not radio network layer fault, transport layer
fault, radio network congestion, or handover failure, the L.E-RAB.AbnormRel.Other counter
is incremented by 1. If the cause is radio network layer fault and the sub-cause is not DRB
RLC retransmission times reaching the maximum number, SRB RLC retransmission times
reaching the maximum number, uplink resynchronization failure, and air interface processing
error (not including those during handover and RRC reestablishment), the L.E-
RAB.AbnormRel.Radio.Other counter is incremented by 1. If the failure cause is transport

layer fault and the sub-cause is not transport resource being preempted or transport resource
insufficiency, the L.E-RAB.AbnormRel.TNL.Other counter is incremented by 1. If the failure
cause is radio network congestion and the sub-cause is not radio network resource being
preempted or radio network resource insufficiency, the L.E-RAB.AbnormRel.Cong.Other
counter is incremented by 1.If multiple E-RAB releases are required at the same time, the
corresponding counter is incremented repeatedly. When the MME sends a UE CONTEXT
RELEASE COMMAND message back to the eNodeB, the corresponding counter is not
incremented repeatedly.
REQUEST message to the MME, all E-RABs of the UE are released.
If the cause value is not "Normal Release", "Detach", "User Inactivity","Om-Intervention",
critical handover", or "Handover Cancelled" , and the corresponding E-RAB for services of
QCI 1 carries data, the counters are measured as follows:
If the cause for the abnormal E-RAB release is not radio network layer fault, transport layer
fault, radio network congestion, or handover failure, the L.E-RAB.AbnormRel.Other.VoIP
counter is incremented by 1. If the cause is radio network layer fault and the sub-cause is not
DRB RLC retransmission times reaching the maximum number, SRB RLC retransmission
times reaching the maximum number, uplink resynchronization failure, and air interface
processing error (not including those during handover and RRC reestablishment), the L.E-
RAB.AbnormRel.Radio.Other.VoIP counter is incremented by 1. If the failure cause is
transport layer fault and the sub-cause is not transport resource being preempted or transport
resource insufficiency, the L.E-RAB.AbnormRel.TNL.Other.VoIP counter is incremented by
1. If the failure cause is radio network congestion and the sub-cause is not radio network
resource being preempted or radio network resource insufficiency, the L.E-
RAB.AbnormRel.Cong.Other.VoIP counter is incremented by 1.If multiple E-RABs for
services of QCI 1 are required to be released at the same time, the corresponding counter is
incremented repeatedly. When the MME sends a UE CONTEXT RELEASE COMMAND
message back to the eNodeB, the corresponding counter is not incremented repeatedly.
Figure 1-79

Figure 1-80
Figure 1-81
Figure 1-82
Formula
[L.E-RAB.AbnormRel]-[L.E-RAB.AbnormRel.Radio]-[L.E-RAB.AbnormRel.TNL]-[L.E-
RAB.AbnormRel.Cong]-[L.E-RAB.AbnormRel.HOFailure]
Unit
None

Related Features
L.E-RAB.AbnormRel.Other Multi-mode: None

GSM: None
UMTS: None

RAB.AbnormRel.Other.VoI GSM: None
P
UMTS: None

RAB.AbnormRel.Radio.Oth GSM: None
er
UMTS: None

RAB.AbnormRel.Radio.Oth GSM: None
er.VoIP
UMTS: None

RAB.AbnormRel.TNL.Othe GSM: None
r
UMTS: None

RAB.AbnormRel.TNL.Othe GSM: None
r.VoIP
UMTS: None

RAB.AbnormRel.Cong.Oth GSM: None
er
UMTS: None


RAB.AbnormRel.Cong.Oth GSM: None
er.VoIP
UMTS: None
1.6.16 Number of MME-initiated Abnormal Releases of E-RABs

During Handover Executions
Counters
1526736879 L.E- Number of BTS3900, L

RAB.AbnormR MME-initiated BTS3900 LTE
el.MME.HOOu abnormal
t.QCI.1 releases of E-
RABs for
services with a
QCI of 1 during
handover
executions
1526736880 L.E- Number of BTS3900, L

RABs for
services with a
QCI of 2 during
handover
executions
1526736881 L.E- Number of BTS3900, L

RABs for
services with a
QCI of 3 during
handover
executions


1526736882 L.E- Number of BTS3900, L

RABs for
services with a
QCI of 4 during
handover
executions
1526736883 L.E- Number of BTS3900, L

RABs for
services with a
QCI of 5 during
handover
executions
1526736884 L.E- Number of BTS3900, L

RABs for
services with a
QCI of 6 during
handover
executions
1526736885 L.E- Number of BTS3900, L

RABs for
services with a
QCI of 7 during
handover
executions
1526736886 L.E- Number of BTS3900, L

RABs for
services with a
QCI of 8 during
handover
executions


1526736887 L.E- Number of BTS3900, L

RABs for
services with a
QCI of 9 during
handover
executions

t releases of E-
RABs during
handover
executions
Description
The counters measure the number of MME-initiated abnormal releases of E-RABs per QCI
and the total number of MME-initiated abnormal releases of E-RABs during handover
executions.
3GPP TS 36.413 V10.4.0.
Measurement Points
As shown at point B in Figure 1-83, during an intra-eNodeB handover, if the target cell
receives a UE CONTEXT RELEASE COMMAND message from the MME before receiving
an RRC Connection Reconfiguration Complete message from the UE, the target cell releases
all E-RABs of the UE. If the eNodeB determines that the corresponding E-RABs transmit or
receive data, the corresponding counter is incremented by the number of E-RABs per QCI. In
addition, the L.E-RAB.AbnormRel.MME.HOOut counter is incremented by the number of all
E-RABs of all QCIs.
As shown at point C in Figure 1-84, during an X2-based handover, if the source eNodeB
receives a UE CONTEXT RELEASE COMMAND message from the MME before receiving
a UE CONTEXT RELEASE message from the target eNodeB, the source eNodeB releases all
E-RABs of the UE. If the source eNodeB determines that the corresponding E-RABs transmit
or receive data, the corresponding counter is incremented by the number of E-RABs per QCI.
In addition, the L.E-RAB.AbnormRel.MME.HOOut counter is incremented by the number of
all E-RABs of all QCIs.
As shown at point C in Figure 1-85, during an S1-based handover, the source eNodeB
releases all E-RABs of the UE when receiving a UE CONTEXT RELEASE COMMAND
message from the MME. If the source eNodeB determines that the corresponding E-RABs
transmit or receive data and the release cause is not "Successful Handover" or "Normal

Release", the corresponding counter is incremented by the number of E-RABs per QCI. In
addition, the L.E-RAB.AbnormRel.MME.HOOut counter is incremented by the number of all
E-RABs of all QCIs.
As shown at point C in Figure 1-86, during a handover from an E-UTRAN to a WCDMA
network, GERAN, or TD-SCDMA network, if the source eNodeB receives a UE CONTEXT
RELEASE COMMAND message from the MME, the source eNodeB releases all E-RABs for
the UE. If the source eNodeB determines that the corresponding E-RABs transmit or receive
data and the release cause is not "Successful Handover" or "Normal Release", the
corresponding counter is incremented by the number of E-RABs per QCI. In addition, the
L.E-RAB.AbnormRel.MME.HOOut counter is incremented by the number of all E-RABs of
all QCIs.
Figure 1-83
Figure 1-84

Figure 1-85
Figure 1-86
Formula
None
Unit
None

Related Features

RAB.AbnormRel.MME.HO GSM: None
Out.QCI.1
UMTS: None

Out.QCI.2
UMTS: None

Out.QCI.3
UMTS: None

Out.QCI.4
UMTS: None

Out.QCI.5
UMTS: None

Out.QCI.6
UMTS: None

Out.QCI.7
UMTS: None


Out.QCI.8
UMTS: None

Out.QCI.9
UMTS: None

Out
UMTS: None
1.6.17 Number of Normal E-RAB Releases Caused by Inactivity

Timer Expiration
Counters
1526737848 L.E- Number of BTS3900, L

RAB.Rel.eNod eNodeB- BTS3900 LTE
eB.Userinact triggered E-
RAB releases
with the cause
value of User
Inactivity
Description
The counters measure the number of normal E-RAB releases caused by UE inactivity timer
expiration.
The signaling procedures related to these counters comply with section 19.2.2.2 in 3GPP TS
36.300 (V10.6.0).

Measurement Points
As shown at point A in Figure 1, when the eNodeB initiates an E-RAB release and sends a
UE CONTEXT RELEASE REQEUST message to the MME, it releases all E-RABs of the
UE. If the release cause is "User Inactivity", the L.E-RAB.Rel.eNodeB.Userinact counter is
incremented by the number of E-RABs contained in the UE CONTEXT RELEASE
REQUEST message.
Formula
None
Unit
None
Related Features

RAB.Rel.eNodeB.Userinact GSM: None
UMTS: None
1.7 E-RAB Setup Failure Measurement (E-

RAB.EstFail.Cell)
Overview
An E-RAB is an access layer bearer for carrying service data of users. The E-RAB setup
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 1-87 shows the measurement points in a failed E-RAB setup procedure.

Figure 1-87
Counters
Description

RAB.FailEst.NoRe setup failures due to V100R008C00
ply no responses from BTS3900 LTE:
the UE in a cell version earlier than
V100R003C00

RAB.FailEst.MME setup failures V100R008C00
triggered by the BTS3900 LTE:
MME V100R003C00


Description

RAB.FailEst.TNL setup failures due to V100R008C00
faults at the BTS3900 LTE:
transport network V100R003C00
layer

RAB.FailEst.RNL setup failures due to V100R008C00
faults at the radio BTS3900 LTE:
network layer V100R003C00

RAB.FailEst.NoRa setup failures due to V100R008C00
dioRes insufficient radio BTS3900 LTE:
resources V100R003C00

RAB.FailEst.Secur setup failures due to V100R008C00
ModeFail security mode BTS3900 LTE:
configuration V100R003C00
failures

dioRes.SRS insufficient SRS BTS3900 LTE:

dioRes.PUCCH insufficient PUCCH BTS3900 LTE:

RAB.FailEst.SRBR setup failures V100R009C00
eset because the RLC BTS3900 LTE:
PDU for an SRB has V100R009C00
been retransmitted
for the maximum
number of times

RAB.FailEst.TNL. setup failures V100R009C00
DLRes because of BTS3900 LTE:
insufficient V100R009C00
downlink transport
resources

RAB.FailEst.TNL. setup failures V100R009C00
ULRes because of BTS3900 LTE:
insufficient uplink V100R009C00
transport resources


Description

RAB.FailEst.NoRa setup failures V100R009C00
dioRes.DLThrpLic because of BTS3900 LTE:
insufficient licensed V100R009C00
downlink traffic
volume

dioRes.ULThrpLic because of BTS3900 LTE:
insufficient licensed V100R009C00
uplink traffic
volume

dioRes.DLSatis because of a low BTS3900 LTE:
downlink V100R009C00
satisfaction rate

dioRes.ULSatis because of a low BTS3900 LTE:
uplink satisfaction V100R009C00
rate
1526729957 L.E- Number of setup BTS3900:

RAB.FailEst.NoRe failures of E-RABs V100R009C00
ply.VoIP for voice services BTS3900 LTE:
because of no V100R009C00
responses from the
UE in a cell

RAB.FailEst.MME triggered setup V100R009C00
.VoIP failures of E-RABs BTS3900 LTE:
for voice services V100R009C00

RAB.FailEst.TNL. failures of E-RABs V100R009C00
VoIP for voice services BTS3900 LTE:
because of faults at V100R009C00
the transport
network layer

RAB.FailEst.RNL. failures of E-RABs V100R009C00
because of faults at V100R009C00
the radio network
layer


Description

RAB.FailEst.NoRa failures of E-RABs V100R009C00
dioRes.VoIP for voice services BTS3900 LTE:
because of V100R009C00
insufficient radio
resources

RAB.FailEst.Secur failures of E-RABs V100R009C00
ModeFail.VoIP for voice services BTS3900 LTE:
because of security V100R009C00
mode configuration
failures

RAB.FailEst.SRBR failures of E-RABs V100R009C00
eset.VoIP for voice services BTS3900 LTE:
because the RLC V100R009C00
PDU for an SRB has
been retransmitted
for the maximum
number of times

dioRes.SRS.VoIP for voice services BTS3900 LTE:
insufficient SRS
resources

dioRes.PUCCH.Vo for voice services BTS3900 LTE:
IP because of V100R009C00
insufficient PUCCH
resources

dioRes.DLThrpLic. for voice services BTS3900 LTE:
VoIP because of V100R009C00
insufficient licensed
downlink traffic
volume


Description

dioRes.ULThrpLic. for voice services BTS3900 LTE:
VoIP because of V100R009C00
insufficient licensed
uplink traffic
volume

dioRes.DLSatis.VoI for voice services BTS3900 LTE:
P because of a low V100R009C00
downlink
satisfaction rate

dioRes.ULSatis.VoI for voice services BTS3900 LTE:
P because of a low V100R009C00
uplink satisfaction
rate

DLRes.VoIP for voice services BTS3900 LTE:
insufficient
downlink transport
resources

ULRes.VoIP for voice services BTS3900 LTE:
insufficient uplink
transport resources

RAB.FailEst.RNL. setup failures due to V100R009C00
eNodeB.NormRel normal release BTS3900 LTE:
initiated by eNodeB V100R009C00

eNodeB.AbnormRe abnormal release BTS3900 LTE:
l initiated by eNodeB V100R009C00

RAB.FailEst.Confli setup failures due to V100R010C00
ct.Hofail conflict with intra- BTS3900 LTE:
eNodeB handovers V100R010C00


Description

RAB.FailEst.Other setup failures due to V100R010C00
other reasons BTS3900 LTE:
V100R010C00

RAB.FailEst.Other. failures of E-RABs V100R010C00
due to other reasons V100R010C00

Other other reasons at the BTS3900 LTE:
radio network layer V100R010C00

RAB.FailEst.RNL. failures of E-RABs V100R010C00
Other.VoIP for voice services BTS3900 LTE:
at the radio network
layer

RAB.FailEst.TNL. setup failures due to V100R010C00
Other other reasons at the BTS3900 LTE:
transport network V100R010C00
layer

Other.VoIP for voice services BTS3900 LTE:
at the transport
network layer

dioRes.Other insufficiency of BTS3900 LTE:
other radio resources V100R010C00

dioRes.Other.VoIP for voice services BTS3900 LTE:
due to insufficiency V100R010C00
of other radio
resources


Description

dioRes.DLSatis.QC with a QCI of 2 BTS3900 LTE:
I2 because of a low V100R010C10
downlink
satisfaction rate

downlink
satisfaction rate

downlink
satisfaction rate

dioRes.ULSatis.QC with a QCI of 2 BTS3900 LTE:
uplink satisfaction
rate

uplink satisfaction
rate

uplink satisfaction
rate

RAB.FailEst.NoRa setup failures for V100R010C10
dioRes.DLSatis.PT PTT services BTS3900 LTE:
T because of a low V100R010C10
downlink
satisfaction rate


Description

dioRes.ULSatis.PT for PTT services BTS3900 LTE:
T because of a low V100R010C10
uplink satisfaction
rate
The E-RAB.EstFail.Cell function subset contains counters related to E-RAB setup failure.
The E-RAB setup failure can be caused by radio network layer faults, transport network layer
faults, faults on the MME side, and others. The preceding causes each can be further
categorized in terms of the sub-failure cause and whether the E-RAB is for VoIP service or
not. The following table shows the parent-child relationship of the counters.
Root Counter Level-1 Counter Level-2 Counter Level-3 Counter
L.E- L.E- - -
RAB.FailEst.MME RAB.FailEst.MME.
VoIP
L.E- L.E- L.E- -

RAB.FailEst.TNL RAB.FailEst.TNL.D RAB.FailEst.TNL.D
LRes LRes.VoIP
L.E- L.E- -
RAB.FailEst.TNL.U RAB.FailEst.TNL.U
LRes LRes.VoIP
L.E- L.E- -
RAB.FailEst.TNL.O RAB.FailEst.RNL.O
ther ther.VoIP
L.E- L.E- L.E- -

RAB.FailEst.TNL RAB.FailEst.TNL.V RAB.FailEst.TNL.D
oIP LRes.VoIP
L.E- -
RAB.FailEst.TNL.U
LRes.VoIP
L.E- L.E- L.E- -

RAB.FailEst.RNL RAB.FailEst.NoRep RAB.FailEst.NoRep
ly ly.VoIP
L.E- L.E- L.E-

RAB.FailEst.NoRad RAB.FailEst.NoRad RAB.FailEst.NoRad
ioRes ioRes.SRS ioRes.SRS.VoIP

L.E- L.E-
RAB.FailEst.NoRad RAB.FailEst.NoRad
ioRes.PUCCH ioRes.PUCCH.VoIP
L.E- L.E-
ioRes.DLThrpLic ioRes.DLThrpLic.Vo
IP
L.E- L.E-
ioRes.ULThrpLic ioRes.ULThrpLic.Vo
IP
L.E- L.E-
ioRes.DLSatis ioRes.DLSatis.VoIP
L.E-
RAB.FailEst.NoRad
ioRes.DLSatis.QCI2
L.E-
RAB.FailEst.NoRad
ioRes.DLSatis.QCI3
L.E-
RAB.FailEst.NoRad
ioRes.DLSatis.QCI4
L.E-
RAB.FailEst.NoRad
ioRes.DLSatis.PTT
L.E- L.E-
ioRes.ULSatis ioRes.ULSatis.VoIP
L.E-
RAB.FailEst.NoRad
ioRes.ULSatis.QCI2
L.E-
RAB.FailEst.NoRad
ioRes.ULSatis.QCI3
L.E-
RAB.FailEst.NoRad
ioRes.ULSatis.QCI4
L.E-
RAB.FailEst.NoRad
ioRes.ULSatis.PTT

L.E- L.E-
ioRes.Other ioRes.Other.VoIP
L.E- L.E- L.E-

RAB.FailEst.NoRad RAB.FailEst.NoRad RAB.FailEst.NoRad
ioRes ioRes.VoIP ioRes.SRS.VoIP
L.E-
RAB.FailEst.NoRad
ioRes.PUCCH.VoIP
L.E-
RAB.FailEst.NoRad
ioRes.DLThrpLic.Vo
IP
L.E-
RAB.FailEst.NoRad
ioRes.ULThrpLic.Vo
IP
L.E-
RAB.FailEst.NoRad
ioRes.DLSatis.VoIP
L.E-
RAB.FailEst.NoRad
ioRes.ULSatis.VoIP
L.E- L.E- -
RAB.FailEst.Secur RAB.FailEst.Secur
ModeFail ModeFail.VoIP
L.E- L.E- -
RAB.FailEst.SRBRe RAB.FailEst.SRBRe
set set.VoIP
L.E- L.E- -
RAB.FailEst.RNL.O RAB.FailEst.RNL.O
ther ther.VoIP
L.E- L.E- L.E- -

RAB.FailEst.RNL RAB.FailEst.RNL.V RAB.FailEst.NoRep
oIP ly.VoIP
L.E- L.E-
ioRes.VoIP ioRes.SRS.VoIP
L.E-
RAB.FailEst.NoRad
ioRes.PUCCH.VoIP

L.E-
RAB.FailEst.NoRad
ioRes.DLThrpLic.Vo
IP
L.E-
RAB.FailEst.NoRad
ioRes.ULThrpLic.Vo
IP
L.E-
RAB.FailEst.NoRad
ioRes.DLSatis.VoIP
L.E-
RAB.FailEst.NoRad
ioRes.ULSatis.VoIP
L.E- -
RAB.FailEst.Secur
ModeFail.VoIP
L.E- -
RAB.FailEst.SRBRe
set.VoIP
L.E- L.E- - -
RAB.FailEst.Other RAB.FailEst.Other.
VoIP
1.7.1 Number of E-RAB Setup Failures for Different Causes in a

Cell
Counters

RAB.FailEst.N RAB setup BTS3900 LTE
oReply failures due to
no responses
from the UE in
a cell



RAB.FailEst.M RAB setup BTS3900 LTE
ME failures
triggered by the
MME

RAB.FailEst.T RAB setup BTS3900 LTE
NL failures due to
faults at the
transport
network layer

RAB.FailEst.R RAB setup BTS3900 LTE
NL failures due to
faults at the
radio network
layer

oRadioRes failures due to
insufficient
radio resources

RAB.FailEst.Se RAB setup BTS3900 LTE
curModeFail failures due to
security mode
configuration
failures

oRadioRes.SRS failures due to
insufficient
SRS resources

oRadioRes.PU failures due to
CCH insufficient
PUCCH
resources



RAB.FailEst.S RAB setup BTS3900 LTE
RBReset failures because
the RLC PDU
for an SRB has
been
retransmitted
for the
maximum
number of
times

NL.DLRes failures because
of insufficient
downlink
transport
resources

NL.ULRes failures because
of insufficient
uplink transport
resources

oRadioRes.DLT failures because
hrpLic of insufficient
licensed
downlink traffic
volume

oRadioRes.ULT failures because
hrpLic of insufficient
licensed uplink
traffic volume

oRadioRes.DLS failures because
atis of a low
downlink
satisfaction rate



oRadioRes.ULS failures because
atis of a low uplink
satisfaction rate
1526729957 L.E- Number of BTS3900, L

RAB.FailEst.N setup failures of BTS3900 LTE
oReply.VoIP E-RABs for
voice services
because of no
responses from
the UE in a cell
1526729958 L.E- Number of BTS3900, L

RAB.FailEst.M MME-triggered BTS3900 LTE
ME.VoIP setup failures of
E-RABs for
voice services
1526729959 L.E- Number of BTS3900, L

RAB.FailEst.T setup failures of BTS3900 LTE
NL.VoIP E-RABs for
voice services
because of
faults at the
transport
network layer
1526729960 L.E- Number of BTS3900, L

RAB.FailEst.R setup failures of BTS3900 LTE
NL.VoIP E-RABs for
voice services
because of
faults at the
radio network
layer
1526729961 L.E- Number of BTS3900, L

oRadioRes.VoI E-RABs for
P voice services
because of
insufficient
radio resources


1526729962 L.E- Number of BTS3900, L

RAB.FailEst.Se setup failures of BTS3900 LTE
curModeFail.Vo E-RABs for
IP voice services
because of
security mode
configuration
failures
1526729963 L.E- Number of BTS3900, L

RAB.FailEst.S setup failures of BTS3900 LTE
RBReset.VoIP E-RABs for
voice services
because the
RLC PDU for
an SRB has
been
retransmitted
for the
maximum
number of
times
1526729964 L.E- Number of BTS3900, L

oRadioRes.SRS E-RABs for
.VoIP voice services
because of
insufficient
SRS resources
1526729965 L.E- Number of BTS3900, L

oRadioRes.PU E-RABs for
CCH.VoIP voice services
because of
insufficient
PUCCH
resources
1526729966 L.E- Number of BTS3900, L

oRadioRes.DLT E-RABs for
hrpLic.VoIP voice services
because of
insufficient
licensed
downlink traffic
volume


1526729967 L.E- Number of BTS3900, L

oRadioRes.ULT E-RABs for
hrpLic.VoIP voice services
because of
insufficient
licensed uplink
traffic volume
1526729968 L.E- Number of BTS3900, L

oRadioRes.DLS E-RABs for
atis.VoIP voice services
because of a
low downlink
satisfaction rate
1526729969 L.E- Number of BTS3900, L

oRadioRes.ULS E-RABs for
atis.VoIP voice services
because of a
low uplink
satisfaction rate
1526729970 L.E- Number of BTS3900, L

NL.DLRes.VoI E-RABs for
P voice services
because of
insufficient
downlink
transport
resources
1526729971 L.E- Number of BTS3900, L

NL.ULRes.VoI E-RABs for
P voice services
because of
insufficient
uplink transport
resources

NL.eNodeB.No failures due to
rmRel normal release
initiated by
eNodeB



NL.eNodeB.Ab failures due to
normRel abnormal
release initiated
by eNodeB

RAB.FailEst.C RAB setup BTS3900 LTE
onflict.Hofail failures due to
conflict with
intra-eNodeB
handovers
1526736694 L.E- Number of BTS3900, L

oRadioRes.DLS E-RABs with a
atis.QCI2 QCI of 2
because of a
low downlink
satisfaction rate
1526736695 L.E- Number of BTS3900, L

atis.QCI3 QCI of 3
because of a
low downlink
satisfaction rate
1526736696 L.E- Number of BTS3900, L

atis.QCI4 QCI of 4
because of a
low downlink
satisfaction rate
1526736697 L.E- Number of BTS3900, L

oRadioRes.ULS E-RABs with a
atis.QCI2 QCI of 2
because of a
low uplink
satisfaction rate


1526736698 L.E- Number of BTS3900, L

atis.QCI3 QCI of 3
because of a
low uplink
satisfaction rate
1526736699 L.E- Number of BTS3900, L

atis.QCI4 QCI of 4
because of a
low uplink
satisfaction rate

oRadioRes.DLS failures for PTT
atis.PTT services
because of a
low downlink
satisfaction rate
1526736857 L.E- Number of BTS3900, L

oRadioRes.ULS E-RABs for
atis.PTT PTT services
because of a
low uplink
satisfaction rate
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
connection setups for users. The counters indicate the number of E-RAB setup failures due to
different causes on the network.
3GPP TS 36.300 V10.6.0 and section 8.2.1 and 8.3.1.3 in 3GPP TS 36.413 V10.4.0.
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 because of 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 1-88, 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 validity check performed by the eNodeB fails or the INITIAL
CONTEXT SETUP REQUEST message cannot be processed because of a cross between 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 L.E-RAB.FailEst.MME 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, expect for ASN decoding errors. A message processing failure because of a cross
between 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 1-88, the L.E-RAB.FailEst.MME.VoIP counter is incremented

each time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST message for
services with the QCI of 1 and other QCIs from the MME but the message validity check
performed by the eNodeB fails or the INITIAL CONTEXT SETUP REQUEST message
cannot be processed because of a cross between the initial UE context setup procedure and
other S1AP-related procedures. If multiple E-RAB setups for services with the QCI of 1 fail
at the same time, the L.E-RAB.FailEst.MME.VoIP counter is incremented by the number of
failed E-RAB setups. A validity check failure may be caused by an error in the message or a
repeated E-RAB ID, expect for ASN decoding errors. A message processing failure because
of a cross between 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 1-89, the L.E-RAB.FailEst.MME counter is incremented each

time the eNodeB receives an E-RAB SETUP REQUEST message from the MME but the
message validity check performed by the eNodeB fails or the E-RAB SETUP REQUEST
message cannot be processed because a cross between interaction of the E-RAB setup
procedure and other S1AP-related procedures. If the E-RAB SETUP REQUEST message
requests to set up multiple E-RABs at the same time, the L.E-RAB.FailEst.MME 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, expect for ASN decoding errors.
A message processing failure because of a cross between the E-RAB setup procedure and
other S1AP-related procedures may occur when the eNodeB receives a UE CONTEXT
RELEASE COMMAND message from the MME during the E-RAB setup procedure.
As shown at point A in Figure 1-89, the L.E-RAB.FailEst.MME.VoIP counter is incremented

each time the eNodeB receives an E-RAB SETUP REQUEST message for services with the
QCI of 1 and other QCIs from the MME but the message validity check performed by the
eNodeB fails or the E-RAB SETUP REQUEST message cannot be processed because of a
cross between the E-RAB setup procedure and other S1AP-related procedures. If multiple E-
RAB setups for services with the QCI of 1 fail at the same time, the L.E-
RAB.FailEst.MME.VoIP counter is incremented by the number of failed E-RAB setups. A
validity check failure may be caused by an error in the message or a repeated E-RAB ID,
expect for ASN decoding errors. A message processing failure because of a cross between the
E-RAB setup procedure and other S1AP-related procedures may occur when the eNodeB
receives a UE CONTEXT RELEASE COMMAND message from the MME during the E-
RAB setup procedure.
failure cause each time the eNodeB fails to set up the E-RAB because of a message
processing error after the eNodeB receives an INITIAL CONTEXT SETUP REQUEST

message, and then the eNodeB sends an INITIAL CONTEXT SETUP RESPONSE or
INITIAL CONTEXT SETUP FAILURE message to the MME.
(1) The L.E-RAB.FailEst.TNL counter is incremented each time the E-RAB setup fails
because of faults at the transport network layer.
(2) The L.E-RAB.FailEst.TNL.DLRes counter is incremented each time the E-RAB setup
fails because of insufficient downlink transport resources.
(3) The L.E-RAB.FailEst.TNL.ULRes counter is incremented each time the E-RAB setup
fails because of insufficient uplink transport resources.
(4) The L.E-RAB.FailEst.RNL counter is incremented each time the E-RAB setup fails
because of faults at the radio network layer.
(5) The L.E-RAB.FailEst.NoRadioRes counter is incremented each time the E-RAB setup
fails because of insufficient radio resources.
(6) The L.E-RAB.FailEst.NoRadioRes.SRS counter is incremented each time the E-RAB
setup fails because of insufficient SRS resources.
(7) The L.E-RAB.FailEst.NoRadioRes.PUCCH counter is incremented each time the E-RAB
setup fails because of insufficient PUCCH resources.
(8) The L.E-RAB.FailEst.NoRadioRes.DLThrpLic counter is incremented each time the E-
RAB setup fails because of insufficient licensed traffic volume in the downlink.
(9) The L.E-RAB.FailEst.NoRadioRes.ULThrpLic counter is incremented each time the E-
RAB setup fails because of insufficient licensed traffic volume in the uplink.
(10) The L.E-RAB.FailEst.NoRadioRes.DLSatis counter is incremented each time the E-RAB
setup fails because of a low downlink satisfaction rate.
(11) The L.E-RAB.FailEst.NoRadioRes.ULSatis counter is incremented each time the E-RAB
setup fails because of a low uplink satisfaction rate.
For details about faults at the transport network layer and faults at the radio network layer, see
3GPP TS36.413. If multiple E-RABs fail to be set up, the corresponding counter is
incremented by the number of failed E-RAB setups. The measuring conditions of the L.E-
RAB.FailEst.RNL counter involve the measuring conditions of the counters L.E-
RAB.FailEst.NoRadioRes, L.E-RAB.FailEst.SecurModeFail, L.E-RAB.FailEst.NoReply,
L.E-RAB.FailEst.SRBReset, L.E-RAB.FailEst.RNL.eNodeB.NormRel and L.E-
RAB.FailEst.RNL.eNodeB.AbnormRel. The measuring conditions of the L.E-
RAB.FailEst.NoRadioRes counter involve the measuring conditions of the counters L.E-
RAB.FailEst.NoRadioRes.SRS, L.E-RAB.FailEst.NoRadioRes.PUCCH, L.E-
RAB.FailEst.NoRadioRes.DLThrpLic, L.E-RAB.FailEst.NoRadioRes.ULThrpLic, L.E-
RAB.FailEst.NoRadioRes.DLSatis, and L.E-RAB.FailEst.NoRadioRes.ULSatis. The
measuring conditions of the L.E-RAB.FailEst.TNL counter involve the measuring conditions
of the counters L.E-RAB.FailEst.TNL.DLRes and L.E-RAB.FailEst.TNL.ULRes.
processing error after the eNodeB receives an INITIAL CONTEXT SETUP REQUEST
message for services with the QCI of 1 and other QCIs, and then the eNodeB sends an
INITIAL CONTEXT SETUP RESPONSE or INITIAL CONTEXT SETUP FAILURE
message to the MME.
(1) The L.E-RAB.FailEst.TNL.VoIP counter is incremented each time the E-RAB setup fails

(2) The L.E-RAB.FailEst.TNL.DLRes.VoIP counter is incremented each time the E-RAB

setup fails because of insufficient downlink transport resources.
(3) The L.E-RAB.FailEst.TNL.ULRes.VoIP counter is incremented each time the E-RAB

setup fails because of insufficient uplink transport resources.
(4) The L.E-RAB.FailEst.RNL.VoIP counter is incremented each time the E-RAB setup fails
(5) The L.E-RAB.FailEst.NoRadioRes.VoIP counter is incremented each time the E-RAB

setup fails because of insufficient radio resources.
(6) The L.E-RAB.FailEst.NoRadioRes.SRS.VoIP counter is incremented each time the E-

RAB setup fails because of insufficient SRS resources.
(7) The L.E-RAB.FailEst.NoRadioRes.PUCCH.VoIP counter is incremented each time the E-

RAB setup fails because of insufficient PUCCH resources.
(8) The L.E-RAB.FailEst.NoRadioRes.DLThrpLic.VoIP counter is incremented each time the

E-RAB setup fails because of insufficient licensed traffic volume in the downlink.
(9) The L.E-RAB.FailEst.NoRadioRes.ULThrpLic.VoIP counter is incremented each time the

E-RAB setup fails because of insufficient licensed traffic volume in the uplink.
(10) The L.E-RAB.FailEst.NoRadioRes.DLSatis.VoIP counter is incremented each time the

E-RAB setup fails because of a low downlink satisfaction rate.
(11) The L.E-RAB.FailEst.NoRadioRes.ULSatis.VoIP counter is incremented each time the

E-RAB setup fails because of a low uplink satisfaction rate.
3GPP TS36.413.
If multiple E-RABs for services with the QCI of 1 fail to be set up, the corresponding counter
is incremented by the number of failed E-RAB setups for services with the QCI of 1. The
measuring conditions of the L.E-RAB.FailEst.RNL.VoIP counter involve the measuring
conditions of the counters L.E-RAB.FailEst.NoRadioRes.VoIP, L.E-
RAB.FailEst.SecurModeFail.VoIP, L.E-RAB.FailEst.NoReply.VoIP, and L.E-
RAB.FailEst.SRBReset.VoIP. The measuring conditions of the L.E-
RAB.FailEst.NoRadioRes.VoIP counter involve the measuring conditions of the counters L.E-
RAB.FailEst.NoRadioRes.SRS.VoIP, L.E-RAB.FailEst.NoRadioRes.PUCCH.VoIP, L.E-
RAB.FailEst.NoRadioRes.DLThrpLic.VoIP, L.E-RAB.FailEst.NoRadioRes.ULThrpLic.VoIP,
L.E-RAB.FailEst.NoRadioRes.DLSatis.VoIP, and L.E-
RAB.FailEst.NoRadioRes.ULSatis.VoIP. The measuring conditions of the L.E-
RAB.FailEst.TNL.VoIP counter involve the measuring conditions of the counters L.E-
RAB.FailEst.TNL.DLRes.VoIP and L.E-RAB.FailEst.TNL.ULRes.VoIP.
processing error after the eNodeB receives an E-RAB SETUP REQUEST message, and then
the eNodeB sends an E-RAB SETUP RESPONSE message to the MME. .
(1) The L.E-RAB.FailEst.TNL counter is incremented each time the E-RAB setup fails
(2) The L.E-RAB.FailEst.TNL.DLRes counter is incremented each time the E-RAB setup
fails because of insufficient downlink transport resources.

(3) The L.E-RAB.FailEst.TNL.ULRes counter is incremented each time the E-RAB setup
fails because of insufficient uplink transport resources.
(4) The L.E-RAB.FailEst.RNL counter is incremented each time the E-RAB setup fails
(5) The L.E-RAB.FailEst.NoRadioRes counter is incremented each time the E-RAB setup
fails because of insufficient radio resources.
(6) The L.E-RAB.FailEst.NoRadioRes.PUCCH counter is incremented each time the E-RAB
setup fails because of insufficient PUCCH resources.
(7) The L.E-RAB.FailEst.NoRadioRes.DLThrpLic counter is incremented each time the E-
RAB setup fails because of insufficient licensed traffic volume in the downlink.
(8) The L.E-RAB.FailEst.NoRadioRes.ULThrpLic counter is incremented each time the E-
RAB setup fails because of insufficient licensed traffic volume in the uplink.
(9) The L.E-RAB.FailEst.NoRadioRes.DLSatis counter is incremented each time the E-RAB
setup fails because of a low downlink satisfaction rate.
(10) The L.E-RAB.FailEst.NoRadioRes.ULSatis counter is incremented each time the E-RAB
setup fails because of a low uplink satisfaction rate.
3GPP TS36.413. If multiple E-RABs fail to be set up, the corresponding counter is
incremented by the number of failed E-RAB setups. The measuring conditions of the L.E-
RAB.FailEst.RNL counter involve the measuring conditions of the counters L.E-
RAB.FailEst.NoRadioRes, L.E-RAB.FailEst.SecurModeFail, L.E-RAB.FailEst.NoReply,
L.E-RAB.FailEst.SRBReset, L.E-RAB.FailEst.RNL.eNodeB.NormRel and L.E-
RAB.FailEst.RNL.eNodeB.AbnormRel. The measuring conditions of the L.E-
RAB.FailEst.NoRadioRes counter involve the measuring conditions of the counters L.E-
RAB.FailEst.NoRadioRes.SRS, L.E-RAB.FailEst.NoRadioRes.PUCCH, L.E-
RAB.FailEst.NoRadioRes.DLThrpLic, L.E-RAB.FailEst.NoRadioRes.ULThrpLic, L.E-
RAB.FailEst.NoRadioRes.DLSatis, and L.E-RAB.FailEst.NoRadioRes.ULSatis. The
measuring conditions of the L.E-RAB.FailEst.TNL counter involve the measuring conditions
of the counters L.E-RAB.FailEst.TNL.DLRes and L.E-RAB.FailEst.TNL.ULRes.
processing error after the eNodeB receives an E-RAB SETUP REQUEST message for
services with the QCI of 1 and other QCIs, and then the eNodeB sends an E-RAB SETUP
RESPONSE message to the MME.
(1) The L.E-RAB.FailEst.TNL.VoIP counter is incremented each time the E-RAB setup fails
(2) The L.E-RAB.FailEst.TNL.DLRes.VoIP counter is incremented each time the E-RAB
setup fails because of insufficient downlink transport resources.
(3) The L.E-RAB.FailEst.TNL.ULRes.VoIP counter is incremented each time the E-RAB
setup fails because of insufficient uplink transport resources.
(4) The L.E-RAB.FailEst.RNL.VoIP counter is incremented each time the E-RAB setup fails
(5) The L.E-RAB.FailEst.NoRadioRes.VoIP counter is incremented each time the E-RAB
setup fails because of insufficient radio resources.

(6) The L.E-RAB.FailEst.NoRadioRes.PUCCH.VoIP counter is incremented each time the E-

RAB setup fails because of insufficient PUCCH resources.
(7) The L.E-RAB.FailEst.NoRadioRes.DLThrpLic.VoIP counter is incremented each time the

E-RAB setup fails because of insufficient licensed traffic volume in the downlink.
(8) The L.E-RAB.FailEst.NoRadioRes.ULThrpLic.VoIP counter is incremented each time the

E-RAB setup fails because of insufficient licensed traffic volume in the uplink.
(9) The L.E-RAB.FailEst.NoRadioRes.DLSatis.VoIP counter is incremented each time the E-

RAB setup fails because of a low downlink satisfaction rate.
(10) The L.E-RAB.FailEst.NoRadioRes.ULSatis.VoIP counter is incremented each time the

E-RAB setup fails because of a low uplink satisfaction rate.
3GPP TS36.413.
If multiple E-RABs for services with the QCI of 1 fail to be set up, the corresponding counter
is incremented by the number of failed E-RAB setups for services with the QCI of 1. The
measuring conditions of the L.E-RAB.FailEst.RNL.VoIP counter involve the measuring
conditions of the counters L.E-RAB.FailEst.NoRadioRes.VoIP, L.E-
RAB.FailEst.SecurModeFail.VoIP, L.E-RAB.FailEst.NoReply.VoIP, and L.E-
RAB.FailEst.SRBReset.VoIP. The measuring conditions of the L.E-
RAB.FailEst.NoRadioRes.VoIP counter involve the measuring conditions of the counters L.E-
RAB.FailEst.NoRadioRes.SRS.VoIP, L.E-RAB.FailEst.NoRadioRes.PUCCH.VoIP, L.E-
RAB.FailEst.NoRadioRes.DLThrpLic.VoIP, L.E-RAB.FailEst.NoRadioRes.ULThrpLic.VoIP,
L.E-RAB.FailEst.NoRadioRes.DLSatis.VoIP, and L.E-
RAB.FailEst.NoRadioRes.ULSatis.VoIP. The measuring conditions of the L.E-
RAB.FailEst.TNL.VoIP counter involve the measuring conditions of the counters L.E-
RAB.FailEst.TNL.DLRes.VoIP and L.E-RAB.FailEst.TNL.ULRes.VoIP.
As shown at point A in Figure 1-90, the L.E-RAB.FailEst.SecurModeFail counter is

incremented each time the eNodeB sends a Security Mode Command message to a UE after
receiving an INITIAL CONTEXT SETUP REQUEST message from the MME and then the
eNodeB receives a Security Mode Failure message from the UE. If the INITIAL CONTEXT
SETUP REQUEST message requests to set up multiple E-RABs, the L.E-
RAB.FailEst.SecurModeFail counter is incremented by the number of requested E-RAB
setups.
As shown at point A in Figure 1-90, the L.E-RAB.FailEst.SecurModeFail.VoIP counter is

incremented each time the eNodeB sends a Security Mode Command message to a UE after
receiving an INITIAL CONTEXT SETUP REQUEST message for services with the QCI of 1
and other QCIs from the MME and then the eNodeB receives a Security Mode Failure
message from the UE. If multiple E-RABs for services with the QCI of 1 fail to be set up at
the same time, the L.E-RAB.FailEst.SecurModeFail counter is incremented by the number of
failed E-RAB setups for services with the QCI of 1.
As shown at point A, B, C, or D in Figure 1-91, during the initial UE context setup or E-RAB
setup procedure, the L.E-RAB.FailEst.NoReply counter is incremented each time the eNodeB
receives no response from the UE before the corresponding timer expires after the eNodeB
sends an RRC signaling message to the UE, and the L.E-RAB.FailEst.SRBReset counter is
incremented each time the E-RAB setup fails because the RLC PDU for an SRB has been
retransmitted for the maximum number of times. If the INITIAL CONTEXT SETUP
REQUEST or E-RAB SETUP REQUEST message requests to set up multiple E-RABs, the
corresponding counter is incremented by the number of requested E-RAB setups.

As shown at point A, B, C, or D in Figure 1-91, during the initial UE context setup or E-RAB
setup procedure for services with the QCI of 1 and other QCIs, the L.E-
RAB.FailEst.NoReply.VoIP counter is incremented each time the eNodeB receives no
response from the UE before the corresponding timer expires after the eNodeB sends an RRC
signaling message to the UE, and the L.E-RAB.FailEst.SRBReset.VoIP counter is
incremented each time the E-RAB setup fails because the RLC PDU for an SRB has been
retransmitted for the maximum number of times. If the INITIAL CONTEXT SETUP
REQUEST or E-RAB SETUP REQUEST message requests to set up multiple E-RABs for
services with the QCI of 1, the corresponding counter is incremented by the number of
requested E-RAB setups for services with the QCI of 1.
As shown at point A in Figure 1-92 or Figure 1-93, the L.E-
RAB.FailEst.RNL.eNodeB.NormRel counter is incremented by 1 each time if both of the
(1) After the eNodeB receives an INITIAL CONTEXT SETUP REQUEST or E-RAB SETUP
REQUEST message from the MME, the eNodeB sends the MME a UE CONTEXT
RELEASE REQUEST message during the E-RAB setup procedure. As a result, the E-RAB
setup procedure fails.
(2) 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"".
If multiple E-RABs fail to be set up at the same time, the L.E-
RAB.FailEst.RNL.eNodeB.NormRel counter is incremented by the number of failed E-RAB
setups.
As shown at point A in Figure 1-92 or Figure 1-93, the L.E-
RAB.FailEst.RNL.eNodeB.AbnormRel counter is incremented by 1 each time if both of the
(1) After the eNodeB receives an INITIAL CONTEXT SETUP REQUEST or E-RAB SETUP
REQUEST message from the MME, the eNodeB sends the MME a UE CONTEXT
RELEASE REQUEST message during the E-RAB setup procedure. As a result, the E-RAB
setup procedure fails.
(2) 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 fail to be set up at the same time, the L.E-
RAB.FailEst.RNL.eNodeB.AbnormRel counter is incremented by the number of failed E-
RAB setups.
During an intra-eNodeB handover, the MME triggers an E-RAB setup procedure, which is in
conflict with the handover. The eNodeB saves the E-RAB setup messages in the buffer. If the
handover is successful, the E-RAB setup procedure continues. If the handover procedure fails,
the eNodeB sends an E-RAB setup failure message to the MME, and the L.E-
RAB.FailEst.Conflict.Hofail counter is incremented by 1 in the source cell. If multiple E-
RABs fail to be set up due to conflict with intra-eNodeB handovers, the counter is
incremented by the number of failed E-RAB setups.

Figure 1-88
Figure 1-89

Figure 1-90

Figure 1-91

Figure 1-92
Figure 1-93
Formula
None
Unit
None

Related Features
L.E-RAB.FailEst.NoReply Multi-mode: None

GSM: None
UMTS: None
L.E-RAB.FailEst.MME Multi-mode: None

GSM: None
UMTS: None
L.E-RAB.FailEst.TNL Multi-mode: None

GSM: None
UMTS: None
L.E-RAB.FailEst.RNL Multi-mode: None

GSM: None
UMTS: None
LBFD-002023 Admission Control
TDLBFD-002023 Admission Control

RAB.FailEst.NoRadioRes GSM: None
UMTS: None

RAB.FailEst.SecurModeFail GSM: None
UMTS: None


RAB.FailEst.NoRadioRes.S GSM: None
RS
UMTS: None

RAB.FailEst.NoRadioRes.P GSM: None
UCCH
UMTS: None
L.E-RAB.FailEst.SRBReset Multi-mode: None

GSM: None
UMTS: None

RAB.FailEst.TNL.DLRes GSM: None
UMTS: None

RAB.FailEst.TNL.ULRes GSM: None
UMTS: None


RAB.FailEst.NoRadioRes.D GSM: None
LThrpLic
UMTS: None

RAB.FailEst.NoRadioRes.U GSM: None
LThrpLic
UMTS: None

LSatis
UMTS: None

LSatis
UMTS: None

RAB.FailEst.NoReply.VoIP GSM: None
UMTS: None


RAB.FailEst.MME.VoIP GSM: None
UMTS: None
L.E-RAB.FailEst.TNL.VoIP Multi-mode: None

GSM: None
UMTS: None
L.E-RAB.FailEst.RNL.VoIP Multi-mode: None

GSM: None
UMTS: None

RAB.FailEst.NoRadioRes.V GSM: None
oIP
UMTS: None

RAB.FailEst.SecurModeFail GSM: None
.VoIP
UMTS: None

RAB.FailEst.SRBReset.VoI GSM: None
P
UMTS: None


RAB.FailEst.NoRadioRes.S GSM: None
RS.VoIP
UMTS: None

RAB.FailEst.NoRadioRes.P GSM: None
UCCH.VoIP
UMTS: None

LThrpLic.VoIP
UMTS: None

LThrpLic.VoIP
UMTS: None

LSatis.VoIP
UMTS: None


LSatis.VoIP
UMTS: None

RAB.FailEst.TNL.DLRes.V GSM: None
oIP
UMTS: None

RAB.FailEst.TNL.ULRes.V GSM: None
oIP
UMTS: None

RAB.FailEst.RNL.eNodeB. GSM: None
NormRel
UMTS: None

RAB.FailEst.RNL.eNodeB. GSM: None
AbnormRel
UMTS: None


RAB.FailEst.Conflict.Hofail GSM: None
UMTS: None

LSatis.QCI2
UMTS: None

LSatis.QCI3
UMTS: None

LSatis.QCI4
UMTS: None

LSatis.QCI2
UMTS: None


LSatis.QCI3
UMTS: None

LSatis.QCI4
UMTS: None

LSatis.PTT
UMTS: None

LSatis.PTT
UMTS: None

1.7.2 Number of E-RAB Setup Failures for Other Causes in a Cell

Counters

RAB.FailEst.Ot RAB setup BTS3900 LTE
her failures due to
other reasons
1526732923 L.E- Number of BTS3900, L

RAB.FailEst.Ot setup failures of BTS3900 LTE
her.VoIP E-RABs for
voice services
due to other
reasons

NL.Other failures due to
other reasons at
the radio
network layer
1526732925 L.E- Number of BTS3900, L

RAB.FailEst.R setup failures of BTS3900 LTE
NL.Other.VoIP E-RABs for
voice services
due to other
reasons at the
radio network
layer

NL.Other failures due to
other reasons at
the transport
network layer
1526732927 L.E- Number of BTS3900, L

NL.Other.VoIP E-RABs for
voice services
due to other
reasons at the
transport
network layer



oRadioRes.Oth failures due to
er insufficiency of
other radio
resources
1526732929 L.E- Number of BTS3900, L

oRadioRes.Oth E-RABs for
er.VoIP voice services
due to
insufficiency of
other radio
resources
Description
The counters measure the number of E-RAB setup failures for other causes in a cell. An E-
RAB is the access layer bearer for carrying service data of a UE. The E-RAB setup success
rate in a cell directly represents the capability of the cell to provide E-RAB connections for
UEs. The counters indicate the number of E-RAB setup failures due to different causes on the
network.
3GPP TS 36.300 (V10.6.0) and sections 8.2.1 and 8.3.1.3 in 3GPP TS 36.413 (V10.4.0).
Measurement Points
As shown at point A in Figure 1-94, the eNodeB receives an INITIAL CONTEXT SETUP
REQUEST message from the MME, and the E-RAB fails to be set up due to a processing
error. Then, the eNodeB sends an INITIAL CONTEXT SETUP RESPONSE or INITIAL
CONTEXT SETUP FAILURE message to the MME. If the failure cause in the message is not
radio network layer fault, transport layer fault, or MME fault, the L.E-RAB.FailEst.Other
counter is incremented by 1. If the failure cause is radio network layer fault and the sub-cause
is not radio resource insufficiency, air interface no response, security mode configuring
failure, and SRB RLC reaching the maximum retransmission times, the L.E-
RAB.FailEst.RNL.Other counter is incremented by 1. If the failure cause is transport layer
fault and the sub-cause is not uplink transport resource insufficiency or downlink transport
resource insufficiency, the L.E-RAB.FailEst.TNL.Other counter is incremented by 1. If the
failure cause is radio resource insufficiency and the sub-cause is not SRS resource allocation
failure, PUCCH resource allocation failure, downlink traffic license limitation, uplink traffic
license limitation, low downlink satisfaction rate, or low uplink satisfaction rate, the L.E-
RAB.FailEst.NoRadioRes.Other counter is incremented by 1. If there are multiple E-RAB
setup failures, the corresponding counter is incremented according to the number of E-RAB
setup failures.
As shown at point A in Figure 1-94, the eNodeB receives an INITIAL CONTEXT SETUP
REQUEST message containing a service of QCI 1 from the MME, and the E-RAB fails to be

set up due to a processing error. Then, the eNodeB sends an INITIAL CONTEXT SETUP
RESPONSE or INITIAL CONTEXT SETUP FAILURE message to the MME. If the failure
cause in the message is not radio network layer fault, transport layer fault, or MME fault, the
L.E-RAB.FailEst.Other.VoIP counter is incremented by 1. If the failure cause is radio network
layer fault and the sub-cause is not radio resource insufficiency, air interface no response,
security mode configuring failure, and SRB RLC reaching the maximum retransmission
times, the L.E-RAB.FailEst.RNL.Other.VoIP counter is incremented by 1. If the failure cause
is transport layer fault and the sub-cause is not uplink transport resource insufficiency or
downlink transport resource insufficiency, the L.E-RAB.FailEst.TNL.Other.VoIP counter is
incremented by 1. If the failure cause is radio resource insufficiency and the sub-cause is not
SRS resource allocation failure, PUCCH resource allocation failure, downlink traffic license
limitation, uplink traffic license limitation, low downlink satisfaction rate, or low uplink
satisfaction rate, the L.E-RAB.FailEst.NoRadioRes.Other.VoIP counter is incremented by 1.
If there are multiple E-RAB setup failures for services of QCI 1, the corresponding counter is
incremented according to the number of E-RAB setup failures.
As shown at point A in Figure 1-95, the eNodeB receives an E-RAB SETUP REQUEST
message from the MME, and the E-RAB fails to be set up due to a processing error. Then, the
eNodeB sends an E-RAB SETUP RESPONSE message to the MME. If the failure cause in
the message is not radio network layer fault, transport layer fault, or MME fault, the L.E-
RAB.FailEst.Other counter is incremented by 1. If the failure cause is radio network layer
fault and the sub-cause is not radio resource insufficiency, air interface no response, security
mode configuring failure, and SRB RLC reaching the maximum retransmission times, the
L.E-RAB.FailEst.RNL.Other counter is incremented by 1. If the failure cause is transport
layer fault and the sub-cause is not uplink transport resource insufficiency or downlink
transport resource insufficiency, the L.E-RAB.FailEst.TNL.Other counter is incremented by
1. If the failure cause is radio resource insufficiency and the sub-cause is not SRS resource
allocation failure, PUCCH resource allocation failure, downlink traffic license limitation,
uplink traffic license limitation, low downlink satisfaction rate, or low uplink satisfaction rate,
the L.E-RAB.FailEst.NoRadioRes.Other counter is incremented by 1. If there are multiple E-
RAB setup failures, the corresponding counter is incremented according to the number of E-
RAB setup failures.
As shown at point A in Figure 1-95, the eNodeB receives an E-RAB SETUP REQUEST
message containing a service of QCI 1 from the MME, and the E-RAB fails to be set up due
to a processing error. Then, the eNodeB sends an E-RAB SETUP RESPONSE message to the
MME. If the failure cause in the message is not radio network layer fault, transport layer fault,
or MME fault, the L.E-RAB.FailEst.Other.VoIP counter is incremented by 1. If the failure
cause is radio network layer fault and the sub-cause is not radio resource insufficiency, air
interface no response, security mode configuring failure, and SRB RLC reaching the
maximum retransmission times, the L.E-RAB.FailEst.RNL.Other.VoIP counter is incremented
by 1. If the failure cause is transport layer fault and the sub-cause is not uplink transport
resource insufficiency or downlink transport resource insufficiency, the L.E-
RAB.FailEst.TNL.Other.VoIP counter is incremented by 1. If the failure cause is radio
resource insufficiency and the sub-cause is not SRS resource allocation failure, PUCCH
resource allocation failure, downlink traffic license limitation, uplink traffic license limitation,
low downlink satisfaction rate, or low uplink satisfaction rate, the L.E-
RAB.FailEst.NoRadioRes.Other.VoIP counter is incremented by 1. If there are multiple E-
RAB setup failures for services of QCI 1, the corresponding counter is incremented according
to the number of E-RAB setup failures.

Figure 1-94
Figure 1-95
Formula
[L.E-RAB.AttEst]-[L.E-RAB.SuccEst]-[L.E-RAB.FailEst.RNL]-[L.E-RAB.FailEst.TNL]-
[L.E-RAB.FailEst.MME]
Unit
None

Related Features
L.E-RAB.FailEst.Other Multi-mode: None

GSM: None
UMTS: None

RAB.FailEst.Other.VoIP GSM: None
UMTS: None

RAB.FailEst.RNL.Other GSM: None
UMTS: None

RAB.FailEst.RNL.Other.VoI GSM: None
P
UMTS: None

RAB.FailEst.TNL.Other GSM: None
UMTS: None

RAB.FailEst.TNL.Other.VoI GSM: None
P
UMTS: None

RAB.FailEst.NoRadioRes.O GSM: None
ther
UMTS: None


RAB.FailEst.NoRadioRes.O GSM: None
ther.VoIP
UMTS: None
1.8 E-RAB Modification Measurement (E-

RAB.Modify.Cell)
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 1-96 shows the measurement points in an E-RAB modification procedure.
Figure 1-96

Counters
Description

RAB.AttModify.Q modification V100R008C00
CI.1 attempts for QCI-1 BTS3900 LTE:
services version earlier than
V100R003C00
1526727514 L.E- Number of BTS3900:

RAB.SuccModify. successful E-RAB V100R008C00
QCI.1 modifications for BTS3900 LTE:
QCI-1 services version earlier than
V100R003C00

V100R003C00
1526727516 L.E- Number of BTS3900:

V100R003C00

V100R003C00
1526727518 L.E- Number of BTS3900:

V100R003C00

V100R003C00
1526727520 L.E- Number of BTS3900:

V100R003C00


Description

CI.5 attempts initiated by BTS3900 LTE:
a cell
1526727522 L.E- Number of BTS3900:

QCI.5 modifications BTS3900 LTE:
initiated by UEs for version earlier than
QCI of 5 in a cell

a cell
1526727524 L.E- Number of BTS3900:

QCI of 6 in a cell

a cell
1526727526 L.E- Number of BTS3900:

QCI of 7 in a cell

a cell


Description
1526727528 L.E- Number of BTS3900:

QCI of 8 in a cell

a cell
1526727530 L.E- Number of BTS3900:

QCI of 9 in a cell

RAB.AttModify RAB modification V100R008C00
attempts initiated by BTS3900 LTE:

RAB.SuccModify successful E-RAB V100R008C00
modifications BTS3900 LTE:
initiated by UEs in a V100R003C00
cell

RAB.FailModify.N modification failures V100R008C00
oRadioRes due to insufficient BTS3900 LTE:
radio resources V100R008C00
The E-RAB.Modify.Cell function subset contains counters related to E-RAB modification.
Some of these counters can be categorized in terms of the QCI. The following table shows the
parent-child relationship of the counters.
L.E-RAB.AttModify L.E-RAB.AttModify.QCI.1
L.E-RAB.AttModify.QCI.2

L.E-RAB.SuccModify L.E-RAB.SuccModify.QCI.1
L.E-RAB.SuccModify.QCI.2
1.8.1 Number of E-RAB Modification Attempts in a Cell

Counters

RAB.AttModif RAB BTS3900 LTE
y.QCI.1 modification
attempts for
QCI-1 services

attempts for
QCI-2 services



attempts for
QCI-3 services

attempts for
QCI-4 services

attempts
initiated by UEs
for services
with the QCI of
5 in a cell

attempts
initiated by UEs
for services
with the QCI of
6 in a cell

attempts
initiated by UEs
for services
with the QCI of
7 in a cell

attempts
initiated by UEs
for services
with the QCI of
8 in a cell



attempts
initiated by UEs
for services
with the QCI of
9 in a cell

RAB.AttModif E-RAB BTS3900 LTE
y modification
attempts
initiated by UEs
in a cell
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.
The signaling flows involved in the counter(s) comply with sections 19.2.2.4.2 in 3GPP TS
36.300 V10.6.0.
Measurement Points
As shown at point A in Figure 1-97, 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 1-97
Formula
None
Unit
None
Related Features
L.E-RAB.AttModify.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

L.E-RAB.AttModify Multi-mode: None

GSM: None
UMTS: None
1.8.2 Number of Successful E-RAB Modifications in a Cell

Counters
1526727514 L.E- Number of BTS3900, L

RAB.SuccModi successful E- BTS3900 LTE
fy.QCI.1 RAB
modifications
for QCI-1
services
1526727516 L.E- Number of BTS3900, L

fy.QCI.2 RAB
modifications
for QCI-2
services
1526727518 L.E- Number of BTS3900, L

fy.QCI.3 RAB
modifications
for QCI-3
services
1526727520 L.E- Number of BTS3900, L

fy.QCI.4 RAB
modifications
for QCI-4
services


1526727522 L.E- Number of BTS3900, L

fy.QCI.5 RAB
modifications
initiated by UEs
for services
with the QCI of
5 in a cell
1526727524 L.E- Number of BTS3900, L

fy.QCI.6 RAB
modifications
initiated by UEs
for services
with the QCI of
6 in a cell
1526727526 L.E- Number of BTS3900, L

fy.QCI.7 RAB
modifications
initiated by UEs
for services
with the QCI of
7 in a cell
1526727528 L.E- Number of BTS3900, L

fy.QCI.8 RAB
modifications
initiated by UEs
for services
with the QCI of
8 in a cell
1526727530 L.E- Number of BTS3900, L

fy.QCI.9 RAB
modifications
initiated by UEs
for services
with the QCI of
9 in a cell

fy RAB
modifications
initiated by UEs
in a cell

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.
The signaling flows involved in the counter(s) comply with sections 19.2.2.4.2 in 3GPP TS
36.300 V10.6.0.
Measurement Points
As shown at point B in Figure 1-98, 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 1-98
Formula
None
Unit
None

Related Features
L.E-RAB.SuccModify.QCI. Multi-mode: None

1 GSM: None
UMTS: None

2 GSM: None
UMTS: None

3 GSM: None
UMTS: None

4 GSM: None
UMTS: None

5 GSM: None
UMTS: None

6 GSM: None
UMTS: None

7 GSM: None
UMTS: None


8 GSM: None
UMTS: None

9 GSM: None
UMTS: None
L.E-RAB.SuccModify Multi-mode: None

GSM: None
UMTS: None
1.8.3 Number of E-RAB Modification Failures for Different

Causes in a Cell
Counters

RAB.FailModif RAB BTS3900 LTE
y.NoRadioRes modification
failures due to
insufficient
radio resources
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.
The signaling flows involved in the counter(s) comply with section 19.2.2.4.2 in 3GPP TS
36.300 V10.6.0 and section 8.2.2 in 3GPP TS 36.413 V10.4.0.

Measurement Points
As shown at point B in Figure 1-99, 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 1-99
Formula
None
Unit
None
Related Features

RAB.FailModify.NoRadioR GSM: None
es
UMTS: None

1.9 Cell Algorithm Measurement (Algo.Cell)

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
Description
1526726760 L.LC.ULCong.Nu Number of times BTS3900:

m.Cell uplink congestion V100R008C00
occurs in a cell BTS3900 LTE:
V100R003C00
1526726761 L.LC.ULCong.Dur. Duration of uplink BTS3900:

Cell congestion in a cell V100R008C00
BTS3900 LTE:
V100R003C00
1526726762 L.LC.DLCong.Nu Number of times BTS3900:

m.Cell downlink congestion V100R008C00
occurs in a cell BTS3900 LTE:
V100R003C00
1526726763 L.LC.DLCong.Dur. Duration of BTS3900:

Cell downlink congestion V100R008C00
V100R003C00
1526726764 L.LC.User.Rel Number of service BTS3900:

releases due to V100R008C00
congestion BTS3900 LTE:
V100R003C00
1526727209 L.Cell.Unavail.Dur. Duration of cell BTS3900:

Sys unavailability due to V100R008C00
system faults BTS3900 LTE:
V100R003C00


Description

Manual unavailability due to V100R008C00
human factors BTS3900 LTE:
V100R003C00
1526728320 L.Cell.Avail.Dur Duration of cell BTS3900:

availability V100R008C00
BTS3900 LTE:
V100R005C00
1526728465 L.Signal.Num.Uu Number of signaling BTS3900:

messages over the V100R008C00
Uu interface BTS3900 LTE:
V100R008C00
1526728466 L.Signal.Num.DRX Number of DRX BTS3900:

.Reconfig reconfiguration V100R008C00
messages BTS3900 LTE:
V100R008C00
1526728411 L.Voice.VQI.UL.Ex Number of times BTS3900:

cellent.Times uplink voice quality V100R008C00
is Excellent BTS3900 LTE:
V100R008C00
1526728412 L.Voice.VQI.UL.G Number of times BTS3900:

ood.Times uplink voice quality V100R008C00
is Good BTS3900 LTE:
V100R008C00
1526728413 L.Voice.VQI.UL.Ac Number of times BTS3900:

cept.Times uplink voice quality V100R008C00
is Accept BTS3900 LTE:
V100R008C00
1526728414 L.Voice.VQI.UL.Po Number of times BTS3900:

or.Times uplink voice quality V100R008C00
is Poor BTS3900 LTE:
V100R008C00
1526728415 L.Voice.VQI.UL.Ba Number of times BTS3900:

d.Times uplink voice quality V100R008C00
is Bad BTS3900 LTE:
V100R008C00
1526728416 L.Voice.VQI.DL.Ex Number of times BTS3900:

cellent.Times downlink voice V100R008C00
quality is Excellent BTS3900 LTE:
V100R008C00


Description
1526728417 L.Voice.VQI.DL.G Number of times BTS3900:

ood.Times downlink voice V100R008C00
quality is Good BTS3900 LTE:
V100R008C00
1526728418 L.Voice.VQI.DL.Ac Number of times BTS3900:

cept.Times downlink voice V100R008C00
quality is Accept BTS3900 LTE:
V100R008C00
1526728419 L.Voice.VQI.DL.Po Number of times BTS3900:

or.Times downlink voice V100R008C00
quality is Poor BTS3900 LTE:
V100R008C00
1526728420 L.Voice.VQI.DL.Ba Number of times BTS3900:

d.Times downlink voice V100R008C00
quality is Bad BTS3900 LTE:
V100R008C00
1526728538 L.RRCRel.Dedicat Number of times BTS3900:

edPri.LTE.High that E-UTRAN is V100R008C00
configured as the BTS3900 LTE:
highest frequency V100R008C00
priority in an
IMMCI IE

edPri.WCDMA.Hi that the WCDMA V100R008C00
gh network is BTS3900 LTE:
configured as the V100R008C00
highest frequency
priority in an
IMMCI IE

edPri.GERAN.Hig that GERAN is V100R008C00
h configured as the BTS3900 LTE:
highest frequency V100R008C00
priority in an
IMMCI IE
1526728444 L.Cell.UserLimit.P Number of BTS3900:

reEmp.Num successful V100R008C00
preemptions BTS3900 LTE:
triggered due to user V100R008C00
limitation

EnergySaving unavailability due to V100R008C00
energy saving BTS3900 LTE:
V100R008C00


Description
1526728494 L.Sps.UL.SchNum Number of uplink BTS3900:

semi-persistent V100R008C00
scheduling times in BTS3900 LTE:
a cell V100R008C00
1526728495 L.Sps.DL.SchNum Number of downlink BTS3900:

semi-persistent V100R008C00
a cell V100R008C00
1526728562 L.Sps.UL.ErrNum Number of failed BTS3900:

uplink semi- V100R008C00
persistent scheduling BTS3900 LTE:
transmissions in a V100R008C00
cell
1526728563 L.Sps.DL.ErrNum Number of failed BTS3900:

downlink semi- V100R008C00
transmission in a V100R008C00
cell
1526728547 L.Cdrx.Enter.Num Number of times a BTS3900:

UE in connected V100R008C00
mode enters DRX in BTS3900 LTE:
RRC_CONECTED V100R008C00
mode
1526728548 L.Cdrx.Exit.Num Number of times a BTS3900:

UE in connected V100R008C00
mode exits DRX in BTS3900 LTE:
RRC_CONECTED V100R008C00
mode
1526728549 L.Cdrx.Active.TtiN Total number of BTS3900:

um TTIs for DRX UEs V100R008C00
in active state BTS3900 LTE:
V100R008C00
1526728550 L.Cdrx.Sleep.TtiN Total number of BTS3900:

um TTIs for DRX UEs V100R008C00
in sleep state BTS3900 LTE:
V100R008C00
1526728551 L.Voip.Cdrx.Active Total number of BTS3900:

.TtiNum TTIs for DRX UEs V100R008C00
in active state and BTS3900 LTE:
performing VoIP V100R008C00
services


Description
1526728552 L.Voip.Cdrx.Sleep. Total number of BTS3900:

TtiNum TTIs for DRX UEs V100R008C00
in dormant state and BTS3900 LTE:
performing VoIP V100R008C00
services
1526728911 L.Signal.Num.TtiB Number of messages BTS3900:

undling.Enter sent for instructing V100R008C01
UEs to enter TTI BTS3900 LTE:
bundling mode V100R008C01
1526728912 L.Signal.Num.TtiB Number of messages BTS3900:

undling.Exit sent for instructing V100R008C01
UEs to exit TTI BTS3900 LTE:
bundling mode V100R008C01
1526729280 L.Signal.Num.SIB1 Times of ETWS- BTS3900:

.ETWS induced SIB1 V100R008C01
changes BTS3900 LTE:
V100R008C01
1526729291 L.Signal.Num.WR Number of ETWS- BTS3900:

WR.ETWS induced WRITE- V100R008C01
REPLACE BTS3900 LTE:
WARNING V100R008C01
REQUEST
messages
1526729471 L.AQM.PacketDro Number of packets BTS3900:

pNum.QCI.6 discarded by AQM V100R009C00
QCI of 6 V100R009C00



1526729499 L.Dyn.ACBar.Trig Number of times BTS3900:

ger.Num that dynamic AC V100R009C00
Barring is triggered BTS3900 LTE:
V100R009C00


Description
1526729500 L.Dyn.ACBar.Canc Number of times BTS3900:

el.Num that dynamic AC V100R009C00
Barring is cancelled BTS3900 LTE:
V100R009C00
1526729501 L.Dyn.ACBar.Adju Number of times BTS3900:

st.Num that parameters V100R009C00
related to dynamic BTS3900 LTE:
AC Barring are V100R009C00
adjusted
1526729502 L.Dyn.ACBar.Cont Control duration of BTS3900:

rol.Dur dynamic AC Barring V100R009C00
BTS3900 LTE:
V100R009C00

edPri.TDSCDMA. that the TDSCDMA V100R009C00
High network is BTS3900 LTE:
highest frequency
priority in an
IMMCI IE
1526729572 L.RRCRel.load.De Number of times BTS3900:

dicatedPri.TDSCD that the TDSCDMA V100R009C00
MA.High network is BTS3900 LTE:
highest frequency
priority in an
IMMCI IE
Triggered Because
of High Load
1526729659 L.Signal.Num.S1 Number of S1 BTS3900:

signaling messages V100R009C00
received or sent by a BTS3900 LTE:
cell V100R009C00
1526729660 L.Signal.Num.X2 Number of X2 BTS3900:

signaling messages V100R009C00
received or sent by a BTS3900 LTE:
cell V100R009C00


Description

dicatedPri.LTE.Hig that the E-UTRAN V100R009C00
h network is BTS3900 LTE:
highest frequency
priority in an
IMMCI IE
Triggered Because
of High Load

dicatedPri.WCDM that the WCDMA V100R009C00
A.High network is BTS3900 LTE:
highest frequency
priority in an
IMMCI IE
Triggered Because
of High Load
1526730104 L.User.UL.Unsync. Number of times the BTS3900:

Dur.Index0 duration of a UE in V100R009C00
the out-of- BTS3900 LTE:
state in a cell ranges
within index 0

within index 1

within index 2

within index 3


Description

within index 4

within index 5

within index 6

within index 7

within index 8
1526730236 L.Sps.UL.TB.Intvl Number of uplink BTS3900:

40ms semi-persistent V100R009C00
a cell (within 40 ms) V100R009C00
1526730237 L.Sps.UL.TB.Intvl Number of failed BTS3900:

40ms.Err uplink semi- V100R009C00
transmissions within V100R009C00
40 ms in a cell


Description
1526730526 L.InterFreq.Load. Number of times the BTS3900:

Meas.Num.Cell eNodeB delivers the V100R009C00
load-triggered inter- BTS3900 LTE:
frequency V100R009C00
measurement
configuration to a
UE
1526730527 L.InterFreq.Load. Number of times the BTS3900:

MeasSucc.Num.Cel load-triggered inter- V100R009C00
l frequency BTS3900 LTE:
measurement is V100R009C00
successful
1526730528 L.InterFreq.HighL Duration in which a BTS3900:

oad.Dur.Cell cell with inter- V100R009C00
frequency load BTS3900 LTE:
balancing enabled is V100R009C00
in the high-load state
1526730529 L.InterFreq.HighL Number of times a BTS3900:

oad.Num.Cell cell with inter- V100R009C00
frequency load BTS3900 LTE:
balancing enabled V100R009C00
enters from the low-
load state to the
high-load state
1526730558 L.Cell.DL.PDSCH. Number of TTIs on BTS3900:

Tti.Num the PDSCH V100R009C00
BTS3900 LTE:
V100R009C00
1526730559 L.Cell.UL.PUSCH. Number of TTIs on BTS3900:

Tti.Num the PUSCH V100R009C00
BTS3900 LTE:
V100R009C00
1526732089 L.Cell.Unavail.Nu Number of times BTS3900:

m that a cell is V100R009C00
unavailable BTS3900 LTE:
V100R009C00
1526732687 L.Voice.VQI.AMR Number of times BTS3900:

WB.UL.Excellent.T uplink voice quality V100R010C00
imes of AMR-WB BTS3900 LTE:
services is Excellent V100R010C00

WB.UL.Good.Time uplink voice quality V100R010C00
s of AMR-WB BTS3900 LTE:
services is Good V100R010C00


Description

WB.UL.Accept.Ti uplink voice quality V100R010C00
mes of AMR-WB BTS3900 LTE:
services is Accept V100R010C00

WB.UL.Poor.Times uplink voice quality V100R010C00
of AMR-WB BTS3900 LTE:
services is Poor V100R010C00

WB.UL.Bad.Times uplink voice quality V100R010C00
of AMR-WB BTS3900 LTE:
services is Bad V100R010C00

WB.DL.Excellent.T downlink voice V100R010C00
imes quality of AMR-WB BTS3900 LTE:
services is Excellent V100R010C00

WB.DL.Good.Time downlink voice V100R010C00
s quality of AMR-WB BTS3900 LTE:
services is Good V100R010C00

WB.DL.Accept.Ti downlink voice V100R010C00
mes quality of AMR-WB BTS3900 LTE:
services is Accept V100R010C00

WB.DL.Poor.Times downlink voice V100R010C00
quality of AMR-WB BTS3900 LTE:
services is Poor V100R010C00

WB.DL.Bad.Times downlink voice V100R010C00
quality of AMR-WB BTS3900 LTE:
services is Bad V100R010C00
1526732719 L.SRLTE.Status.H Number of times BTS3900:

OOut that a UE is detected V100R010C00
based on the SRLTE BTS3900 LTE:
optimization feature V100R010C00
to be switched out of
the state of
performing LTE
services


Description
1526732720 L.SRLTE.Status.H Number of times BTS3900:

OIn that a UE is detected V100R010C00
based on the SRLTE BTS3900 LTE:
optimization feature V100R010C00
to be switched back
to the state of
performing LTE
services
1526732890 L.Voice.NormRel.U Number of normal BTS3900:

L.LowQuality voice call releases in V100R010C00
the cell (poor uplink BTS3900 LTE:
voice quality) V100R010C00
1526732891 L.Voice.NormRel.D Number of normal BTS3900:

L.LowQuality voice call releases in V100R010C00
the cell (poor BTS3900 LTE:
downlink voice V100R010C00
quality)
1526732892 L.Voice.UL.Silent. Number of times BTS3900:

Num that a UE V100R010C00
experiences uplink BTS3900 LTE:
voice mute in the V100R010C00
cell
1526732893 L.Voice.DL.Silent. Number of times BTS3900:

Num that a UE V100R010C00
experiences BTS3900 LTE:
downlink voice V100R010C00
mute in the cell
1526732913 L.AISS.IntereNode Number of times BTS3900:

B.HoMeas.Att that an eNodeB V100R010C00
attempts to measure BTS3900 LTE:
the time difference V100R010C00
among eNodeBs by
using UEs
performing inter-
eNodeB handovers

B.CeMeas.Att that an eNodeB V100R010C00
attempts to measure BTS3900 LTE:
the time difference V100R010C00
among eNodeBs by
using inter-eNodeB
CEUs


Description

B.HoMeas.Succ that an eNodeB V100R010C00
successfully BTS3900 LTE:
measures the time V100R010C00
difference among
eNodeBs by using
UEs that are
performing inter-
eNodeB handovers

B.CeMeas.Succ that an eNodeB V100R010C00
successfully BTS3900 LTE:
measures the time V100R010C00
difference among
eNodeBs by using
inter-eNodeB CEUs
1526733010 L.Sig.PowerCfg.Fai Number of times BTS3900:

l.TimeOut when a cell receives V100R010C00
a power BTS3900 LTE:
message from the
centralized
scheduler but the
validation period
expires
1526733011 L.Sig.PowerCfg.Att Number of power BTS3900:

messages received BTS3900 LTE:
in a cell V100R010C00
1526733199 L.Signal.Num.Nas Number of NAS BTS3900:

messages V100R010C00
BTS3900 LTE:
V100R010C00
1526735577 L.PowerNull.DL.T Number of downlink BTS3900:

TI.Num subframes without V100R010C00
power BTS3900 LTE:
V100R010C00
1526736656 L.SSAC.Dyn.ACBa Number of times BTS3900:

r.Trigger.Num dynamic SSAC is V100R010C10
triggered BTS3900 LTE:
V100R010C10

r.Adjust.Num parameters related to V100R010C10
dynamic SSAC are BTS3900 LTE:
adjusted V100R010C10


Description

r.Cancel.Num dynamic SSAC is V100R010C10
canceled BTS3900 LTE:
V100R010C10
1526736659 L.SSAC.Dyn.ACBa Duration of dynamic BTS3900:

r.Control.Dur SSAC V100R010C10
BTS3900 LTE:
V100R010C10
1526736866 L.Cell.UserSpec.Pr Number of times BTS3900:

epEmp.PrepAtt.Nu preemptions are V100R010C10
m triggered by the BTS3900 LTE:
limitation of the UE V100R010C10
number specification
1526736869 L.Cell.UserLic.Lim Number of times the BTS3900:

it.Num licensed number of V100R010C10
UEs is limited BTS3900 LTE:
V100R010C10
1526736870 L.Cell.UserLic.Pre Number of BTS3900:

pEmp.Succ.Num successful V100R010C10
preemptions BTS3900 LTE:
triggered by the V100R010C10
limitation of the
licensed number of
UEs
1526736889 L.ULIRC.PUSCH. Number of times BTS3900:

MRC.Num MRC is used on the V100R010C10
PUSCH BTS3900 LTE:
V100R010C10
1526736890 L.ULIRC.PUSCH.I Number of times BTS3900:

RC.Num IRC is used on the V100R010C10
PUSCH BTS3900 LTE:
V100R010C10
1526736891 L.CtrlIRC.PUCCH Number of times BTS3900:

.MRC.Num MRC is used on the V100R010C10
PUCCH BTS3900 LTE:
V100R010C10
1526736892 L.CtrlIRC.PUCCH Number of times BTS3900:

.IRC.Num IRC is used on the V100R010C10
PUCCH BTS3900 LTE:
V100R010C10


Description
1526736893 L.CtrlIRC.PRACH Number of times BTS3900:

.MRC.Num MRC is used on the V100R010C10
PRACH BTS3900 LTE:
V100R010C10
1526736894 L.CtrlIRC.PRACH Number of times BTS3900:

.IRC.Num IRC is used on the V100R010C10
PRACH BTS3900 LTE:
V100R010C10
1526737744 L.ULIRC.PUSCH. Number of times BTS3900:

SmartIRC.Num smart IRC is used on V100R010C10
the PUSCH BTS3900 LTE:
V100R010C10
1526737821 L.SPID.SelectTgtP Number of SPID- BTS3900:

LMN.AttOut based target PLMN V100R010C10
selection attempts BTS3900 LTE:
V100R010C10

Sys.S1Fail unavailability due to V100R010C10
S1 interface faults BTS3900 LTE:
V100R010C10
1526737856 L.InterfHighSpeed. Number of times the BTS3900:

Trigger.Num eCoordinator V100R010C10
triggers interference BTS3900 LTE:
coordination in V100R010C10
high-speed railway
scenarios
1526737857 L.InterfHighSpeed. Number of times the BTS3900:

Cancel.Num eCoordinator stops V100R010C10
interference BTS3900 LTE:
coordination in V100R010C10
high-speed railway
scenarios
The Algo.Cell function subset contains counters related to cell algorithms. The following
table shows the parent-child relationship of the counters.
L.Voice.VQI.UL.Excellent.Times L.Voice.VQI.AMRWB.UL.Excellent.Times
L.Voice.VQI.UL.Good.Times L.Voice.VQI.AMRWB.UL.Good.Times

L.Voice.VQI.UL.Accept.Times L.Voice.VQI.AMRWB.UL.Accept.Times
L.Voice.VQI.UL.Poor.Times L.Voice.VQI.AMRWB.UL.Poor.Times
L.Voice.VQI.UL.Bad.Times L.Voice.VQI.AMRWB.UL.Bad.Times
L.Voice.VQI.DL.Excellent.Times L.Voice.VQI.AMRWB.DL.Excellent.Times
L.Voice.VQI.DL.Good.Times L.Voice.VQI.AMRWB.DL.Good.Times
L.Voice.VQI.DL.Accept.Times L.Voice.VQI.AMRWB.DL.Accept.Times
L.Voice.VQI.DL.Poor.Times L.Voice.VQI.AMRWB.DL.Poor.Times
L.Voice.VQI.DL.Bad.Times L.Voice.VQI.AMRWB.DL.Bad.Times
L.RRCRel.DedicatedPri.LTE.High L.RRCRel.load.DedicatedPri.LTE.High
L.RRCRel.DedicatedPri.WCDMA.High L.RRCRel.load.DedicatedPri.WCDMA.Hig
h
L.Sps.UL.SchNum L.Sps.UL.ErrNum
L.Sps.DL.SchNum L.Sps.DL.ErrNum
L.Cdrx.Active.TtiNum L.Voip.Cdrx.Active.TtiNum
L.Cdrx.Sleep.TtiNum L.Voip.Cdrx.Sleep.TtiNum
L.RRCRel.DedicatedPri.TDSCDMA.High L.RRCRel.load.DedicatedPri.TDSCDMA.H
igh
1.9.1 Number of Times Uplink or Downlink Congestion Occurs

in a Cell
Counters
1526726760 L.LC.ULCong. Number of BTS3900, L

Num.Cell times uplink BTS3900 LTE
congestion
occurs in a cell
1526726762 L.LC.DLCong. Number of BTS3900, L

Num.Cell times downlink BTS3900 LTE
congestion
occurs in a cell

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
L.LC.ULCong.Num.Cell Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002024 Congestion Control
L.LC.DLCong.Num.Cell Multi-mode: None

GSM: None
UMTS: None
1.9.2 Duration of Uplink or Downlink Congestion in a Cell
Counters
1526726761 L.LC.ULCong. Duration of BTS3900, L

Dur.Cell uplink BTS3900 LTE
congestion in a
cell


1526726763 L.LC.DLCong. Duration of BTS3900, L

Dur.Cell downlink BTS3900 LTE
congestion in a
cell
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
L.LC.ULCong.Dur.Cell Multi-mode: None

GSM: None
UMTS: None

L.LC.DLCong.Dur.Cell Multi-mode: None

GSM: None
UMTS: None
1.9.3 Number of Service Releases due to Congestion in a Cell

Counters
1526726764 L.LC.User.Rel Number of BTS3900, L

service releases BTS3900 LTE
due to
congestion
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
L.LC.User.Rel Multi-mode: None

GSM: None
UMTS: None
1.9.4 Duration of Cell Unavailability

Counters
1526727209 L.Cell.Unavail. Duration of cell BTS3900, L

Dur.Sys unavailability BTS3900 LTE
due to system
faults

Dur.Manual unavailability BTS3900 LTE
due to human
factors

Dur.EnergySavi unavailability BTS3900 LTE
ng due to energy
saving

Dur.Sys.S1Fail unavailability BTS3900 LTE
due to S1
interface faults
Description
The counters measure the duration of cell unavailability due to human operations, system
faults or energy conservation. Human operations include blocking and deactivating a cell by
using MML commands. 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, or unavailability of
clocks. Energy conservation includes the RF modules entering RF module regular time sleep
mode, 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 inter-RAT cell
shutdown mode, or cell shutdown in low power consumption mode.

Measurement Points
The cell status 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
accumulated counter value is reported. The following deviations may exist during the
performance measurement for the preceding counters:
(1) A deviation of one sampling period may exist in the sampling timer when the timer
performs time synchronization.
(2) If the sampling timer expires after the operator activates the cell but before the cell enters
the active state, the interval between the time that the operator activates the cell and the time
the sampling timer expires is counted as the duration of cell unavailability due to system
faults. That is, after the operator activates the cell, a deviation (smaller than one sampling
period) exists on the L.Cell.Unavail.Dur.Manual and L.Cell.Unavail.Dur.Sys counter values.
The deviations affect 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
L.Cell.Unavail.Dur.Sys None None
L.Cell.Unavail.Dur.Manual None None

L.Cell.Unavail.Dur.EnergyS Multi-mode: None

aving GSM: None
UMTS: None
LTE: LOFD-001025 Adaptive Power
LOFD-001040 Consumption
LOFD-001042 Low Power Consumption
Mode
LOFD-001074
Intelligent Power-Off of
TDLOFD-001042 Carriers in the Same
TDLOFD-001040 Coverage
Carriers in the Same
Coverage of UMTS
Network
Coverage
Low Power Consumption
Mode
L.Cell.Unavail.Dur.Sys.S1F None None

ail
1.9.5 Duration of Cell Availability
Counters
1526728320 L.Cell.Avail.Du Duration of cell BTS3900, L

r availability BTS3900 LTE
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 accumulated counter value 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
1.9.6 Number of Signaling Messages over the Uu Interface
Counters
1526728465 L.Signal.Num. Number of BTS3900, L

Uu signaling BTS3900 LTE
messages over
the Uu interface

Nas NAS messages BTS3900 LTE
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.
The L.Signal.Num.Nas counter is incremented by 1 each time an NAS message is received or
sent over the Uu interface in a cell.
Formula
None
Unit
None

Related Features
L.Signal.Num.Uu Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002017 DRX
TDLBFD-002017 DRX
L.Signal.Num.Nas Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
1.9.7 Number of DRX Reconfiguration Messages

Counters

DRX.Reconfig DRX BTS3900 LTE
reconfiguration
messages
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.

Figure 1-100
Formula
None
Unit
None
Related Features
L.Signal.Num.DRX.Reconfi Multi-mode: None

g GSM: None
UMTS: None
TDLBFD-002017 DRX
LOFD-001105 Dynamic DRX

1.9.8 Uplink or Downlink Voice Quality in a Cell

Counters
1526728411 L.Voice.VQI.U Number of BTS3900, L

L.Excellent.Tim times uplink BTS3900 LTE
es voice quality is
Excellent

L.Good.Times times uplink BTS3900 LTE
voice quality is
Good

L.Accept.Times times uplink BTS3900 LTE
voice quality is
Accept

L.Poor.Times times uplink BTS3900 LTE
voice quality is
Poor

L.Bad.Times times uplink BTS3900 LTE
voice quality is
Bad
1526728416 L.Voice.VQI.D Number of BTS3900, L

L.Excellent.Tim times downlink BTS3900 LTE
es voice quality is
Excellent

L.Good.Times times downlink BTS3900 LTE
voice quality is
Good

L.Accept.Times times downlink BTS3900 LTE
voice quality is
Accept

L.Poor.Times times downlink BTS3900 LTE
voice quality is
Poor



L.Bad.Times times downlink BTS3900 LTE
voice quality is
Bad
Description
The counters measure uplink and downlink voice quality of AMR-WB and AMR-NB services
in a cell, if voice quality monitoring (VQM) is enabled. VQM is controlled by the
VQMAlgoSwitch parameter in the ENodeBAlgoSwitch MO.
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
L.Voice.VQI.UL.Excellent. Multi-mode: None

Times GSM: None
UMTS: None
LTE: LBFD-004008 Performance Management
L.Voice.VQI.UL.Good.Time Multi-mode: None

s GSM: None
UMTS: None
L.Voice.VQI.UL.Accept.Ti Multi-mode: None

mes GSM: None
UMTS: None

L.Voice.VQI.UL.Poor.Times Multi-mode: None

GSM: None
UMTS: None
L.Voice.VQI.UL.Bad.Times Multi-mode: None

GSM: None
UMTS: None
L.Voice.VQI.DL.Excellent. Multi-mode: None

Times GSM: None
UMTS: None
L.Voice.VQI.DL.Good.Time Multi-mode: None

s GSM: None
UMTS: None
L.Voice.VQI.DL.Accept.Ti Multi-mode: None

mes GSM: None
UMTS: None
L.Voice.VQI.DL.Poor.Times Multi-mode: None

GSM: None
UMTS: None
L.Voice.VQI.DL.Bad.Times Multi-mode: None

GSM: None
UMTS: None

1.9.9 Number of Times that E-UTRAN is Configured as the

Highest Frequency Priority in an IMMCI IE
Counters
1526728538 L.RRCRel.Dedi Number of BTS3900, L

catedPri.LTE.Hi times that E- BTS3900 LTE
gh UTRAN is
configured as
the highest
frequency
priority in an
IMMCI IE
1526729877 L.RRCRel.load. Number of BTS3900, L

DedicatedPri.L times that the BTS3900 LTE
TE.High E-UTRAN
network is
configured as
the highest
frequency
priority in an
IMMCI IE
Triggered
Because of
High Load
Description
The counters measure the times the highest dedicated priority was assigned to E-UTRAN
frequencies as indicated in the IMMCI IE contained in RRC Connection Release messages
sent from a cell.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-101, the L.RRCRel.DedicatedPri.LTE.High counter is
incremented by 1 each time the cell sends an RRC Connection Release message to a UE and
the message contains an IMMCI IE that specifies the highest dedicated priority for an E-
UTRAN frequency.
The L.RRCRel.load.DedicatedPri.LTE.High counter is incremented by 1 each time the high-

load cell sends an RRC Connection Release message to a UE for MLB and the message
contains an IMMCI IE that specifies the highest dedicated priority for an E-UTRAN
frequency.

Figure 1-101
Formula
None
Unit
None
Related Features
L.RRCRel.DedicatedPri.LT Multi-mode: None

E.High GSM: None
UMTS: None
LTE: LOFD-00105401 Camp & Handover Based on
TDLOFD-00105401 SPID
LOFD-001112 Camp & Handover Based on
SPID
TDLOFD-001112
MOCN Flexible Priority
Based Camping
Based Camping
L.RRCRel.load.DedicatedPr Multi-mode: None

i.LTE.High GSM: None
UMTS: None
LTE: LOFD-001032 Intra-LTE Load Balancing
TDLOFD-001032 Intra-LTE Load Balancing

1.9.10 Number of Times that the WCDMA Network is Configured

as the Highest Frequency Priority in an IMMCI IE
Counters

catedPri.WCD times that the BTS3900 LTE
MA.High WCDMA
network is
configured as
the highest
frequency
priority in an
IMMCI IE

DedicatedPri.W times that the BTS3900 LTE
CDMA.High WCDMA
network is
configured as
the highest
frequency
priority in an
IMMCI IE
Triggered
Because of
High Load
Description
The counters measure the times the highest dedicated priority was assigned to WCDMA
sent from a cell.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-102, the L.RRCRel.DedicatedPri.WCDMA.High counter is
the message contains an IMMCI IE that specifies the highest dedicated priority for a
WCDMA frequency.
The L.RRCRel.load.DedicatedPri.WCDMA.High counter is incremented by 1 each time the

high-load cell sends an RRC Connection Release message to a UE for MLB and the message
contains an IMMCI IE that specifies the highest dedicated priority for a WCDMA frequency.

Figure 1-102
Formula
None
Unit
None
Related Features
L.RRCRel.DedicatedPri.W Multi-mode: None

CDMA.High GSM: None
UMTS: None
SPID
TDLOFD-001044
Inter-RAT Load Sharing to
LOFD-001112 UTRAN
TDLOFD-001112 Inter-RAT Load Sharing to
UTRAN
Based Camping
Based Camping

i.WCDMA.High GSM: None
UMTS: None
LTE: LOFD-001044 Inter-RAT Load Sharing to
TDLOFD-001044 UTRAN
UTRAN

1.9.11 Number of Times that GERAN is Configured as the

Highest Frequency Priority in an IMMCI IE
Counters

catedPri.GERA times that BTS3900 LTE
N.High GERAN is
configured as
the highest
frequency
priority in an
IMMCI IE
Description
The counters measure the times the highest dedicated priority was assigned to GERAN
sent from a cell.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-103, the L.RRCRel.DedicatedPri.GERAN.High counter is
the message contains an IMMCI IE that specifies the highest dedicated priority for a GERAN
frequency.
Figure 1-103

Formula
None
Unit
None
Related Features
L.RRCRel.DedicatedPri.GE Multi-mode: None

RAN.High GSM: None
UMTS: None
SPID
TDLOFD-001112
Based Camping
Based Camping
1.9.12 Number of Successful Preemptions Triggered due to User

Limitation
Counters
1526728444 L.Cell.UserLim Number of BTS3900, L

it.PreEmp.Num successful BTS3900 LTE
preemptions
triggered due to
user limitation
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
L.Cell.UserLimit.PreEmp.N Multi-mode: None

um GSM: None
UMTS: None
LTE: LOFD-00102901 Radio/transport resource
pre-emption
1.9.13 Number of Semi-Persistent Scheduling Times in a cell

Counters
1526728494 L.Sps.UL.SchN Number of BTS3900, L

um uplink semi- BTS3900 LTE
persistent
scheduling
times in a cell
1526728495 L.Sps.DL.SchN Number of BTS3900, L

um downlink semi- BTS3900 LTE
persistent
scheduling
times in a cell
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
L.Sps.UL.SchNum Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001016 VoIP Semi-persistent
TDLOFD-001016 Scheduling
VoIP Semi-persistent
Scheduling
L.Sps.DL.SchNum Multi-mode: None

GSM: None
UMTS: None
Scheduling
1.9.14 Number of Failed Semi-Persistent Scheduling

Transmissions in a Cell
Counters
1526728562 L.Sps.UL.ErrN Number of BTS3900, L

um failed uplink BTS3900 LTE
semi-persistent
scheduling
transmissions in
a cell


1526728563 L.Sps.DL.ErrN Number of BTS3900, L

um failed downlink BTS3900 LTE
semi-persistent
scheduling
transmission in
a cell
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
L.Sps.UL.ErrNum Multi-mode: None

GSM: None
UMTS: None
Scheduling
L.Sps.DL.ErrNum Multi-mode: None

GSM: None
UMTS: None
Scheduling

1.9.15 Number of Times a UE in Connected Mode Enters DRX in

RRC_CONECTED Mode
Counters
1526728547 L.Cdrx.Enter.N Number of BTS3900, L

um times a UE in BTS3900 LTE
connected mode
enters DRX in
RRC_CONECT
ED mode
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.
Figure 1-104
Formula
None

Unit
None
Related Features
L.Cdrx.Enter.Num Multi-mode: None

GSM: None
UMTS: None
TDLBFD-002017 DRX
1.9.16 Number of Times a UE in Connected Mode Exits DRX in

RRC_CONECTED Mode
Counters
1526728548 L.Cdrx.Exit.Nu Number of BTS3900, L

m times a UE in BTS3900 LTE
connected mode
exits DRX in
RRC_CONECT
ED mode
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.

Figure 1-105
Formula
None
Unit
None
Related Features
L.Cdrx.Exit.Num Multi-mode: None

GSM: None
UMTS: None
TDLBFD-002017 DRX

1.9.17 DRX Duration
Counters
1526728549 L.Cdrx.Active. Total number of BTS3900, L

TtiNum TTIs for DRX BTS3900 LTE
UEs in active
state
1526728550 L.Cdrx.Sleep.Tt Total number of BTS3900, L

iNum TTIs for DRX BTS3900 LTE
UEs in sleep
state
1526728551 L.Voip.Cdrx.Ac Total number of BTS3900, L

tive.TtiNum TTIs for DRX BTS3900 LTE
UEs in active
state and
performing
VoIP services
1526728552 L.Voip.Cdrx.Sle Total number of BTS3900, L

ep.TtiNum TTIs for DRX BTS3900 LTE
UEs in dormant
state and
performing
VoIP services
Description
The counters measure the numbers of transmission time intervals (TTIs) for the following
UEs:
- UEs in the DRX active state
- UEs in the DRX sleep state
- UEs in the DRX active state while performing VoIP services
- UEs in the DRX sleep state while performing VoIP services
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.

Formula
None
Unit
None
Related Features
L.Cdrx.Active.TtiNum Multi-mode: None

GSM: None
UMTS: None
LBFD-002017 DRX
TDLBFD-002017 DRX
L.Cdrx.Sleep.TtiNum Multi-mode: None

GSM: None
UMTS: None
LBFD-002017 DRX
TDLBFD-002017 DRX
L.Voip.Cdrx.Active.TtiNum Multi-mode: None

GSM: None
UMTS: None
LBFD-002017 DRX
TDLBFD-002017 DRX
L.Voip.Cdrx.Sleep.TtiNum Multi-mode: None

GSM: None
UMTS: None
LBFD-002017 DRX
TDLBFD-002017 DRX

1.9.18 Number of Messages Sent for Instructing UEs to Enter or

Exit TTI bundling Mode
Counters
1526728911 L.Signal.Num.T Number of BTS3900, L

tiBundling.Ente messages sent BTS3900 LTE
r for instructing
UEs to enter
TTI bundling
mode
1526728912 L.Signal.Num.T Number of BTS3900, L

tiBundling.Exit messages sent BTS3900 LTE
for instructing
UEs to exit TTI
bundling mode
Description
The counters measure the number of times that the eNodeB sends a message to a UE to
instruct the UE to enter or exit TTI bundling mode.
V10.4.0.
Measurement Points
The L.Signal.Num.TtiBundling.Enter counter is incremented by 1 each time the eNodeB
determines that a UE should enter TTI bundling mode based on the channel conditions and
sends an RRC Connection Reconfiguration message to the UE with the ttiBundling IE set to
TRUE.
The L.Signal.Num.TtiBundling.Exit counter is incremented by 1 each time the eNodeB
determines that a UE should exit TTI bundling mode based on the channel conditions and
sends an RRC Connection Reconfiguration message to the UE with the ttiBundling IE set to
FALSE.

Figure 1-106
Formula
None
Unit
None
Related Features
L.Signal.Num.TtiBundling. Multi-mode: None

Enter GSM: None
UMTS: None
LTE: LOFD-001048 TTI Bundling
TDLOFD-001048 TTI Bundling
L.Signal.Num.TtiBundling. Multi-mode: None

Exit GSM: None
UMTS: None

1.9.19 Times of ETWS-induced SIB1 changes

Counters
1526729280 L.Signal.Num.S Times of BTS3900, L

IB1.ETWS ETWS-induced BTS3900 LTE
SIB1 changes
Description
These counters measure the times of ETWS-induced SIB1 changes. Only the SIB1 delivered
for the first time is counted.
Measurement Points
As shown at point B, after processing a WRITE-REPLACE WARNING REQUEST message
sent from the MME, the eNodeB broadcasts a SIB1 message containing ETWS information
(SIB10 or SIB11) over the air interface. This counter measures only the number of SIB1s
containing the ETWS information delivered for the first time. For example, SIB1 messages
containing SIB10 are delivered first, then SIB1 messages containing SIB10 and SIB11, and
finally SIB1 messages containing SIB11. At each phase, SIB1 messages are delivered
repeatedly. However, only the SIB1 message delivered first at each phase is counted.
Therefore, the counter is incremented by 3. This counter is not applicable to TDD in
eRAN6.1.
Formula
None
Unit
None

Related Features
L.Signal.Num.SIB1.ETWS Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002029 Earthquake and Tsunami
TDLBFD-002029 Warning System (ETWS)
LBFD-002009 Earthquake and Tsunami
Warning System(ETWS)
TDLBFD-002009
Broadcast of system
information
Broadcast of system
information
1.9.20 Number of processed ETWS-induced WRITE-REPLACE

WARNING REQUEST messages in a cell
Counters

WRWR.ETWS ETWS-induced BTS3900 LTE
WRITE-
REPLACE
WARNING
REQUEST
messages
Description
These counters measure the number of processed ETWS-induced WRITE-REPLACE
WARNING REQUEST messages in a cell.
Measurement Points
As shown at point A in Figure 1, when the eNodeB receives an ETWS-induced WRITE-
REPLACE WARNING REQUEST message sent by the MME, it determines whether the
message has been sent in the current ETWS period or the integrity check fails. If the message
has been sent in the current ETWS period or the integrity check fails, the eNodeB discards the
message and does not process it. This counter is incremented by 1 each time the eNodeB
processes a WRITE-REPLACE WARNING REQUEST message.This counter is not
applicable to TDD in eRAN6.1.

Figure 1-107
Formula
None
Unit
None
Related Features
L.Signal.Num.WRWR.ETW Multi-mode: None

S GSM: None
UMTS: None
LTE: LBFD-002029 Earthquake and Tsunami
TDLBFD-002029 Warning System (ETWS)
Earthquake and Tsunami
Warning System(ETWS)

1.9.21 Number of Packets of Non-GBR Bearers Discarded by

AQM
Counters
1526729471 L.AQM.Packet Number of BTS3900, L

DropNum.QCI. packets BTS3900 LTE
6 discarded by
AQM for
services with
QCI of 6

7 discarded by
AQM for
services with
QCI of 7

8 discarded by
AQM for
services with
QCI of 8

9 discarded by
AQM for
services with
QCI of 9
Description
The counters measure the number of packets discarded by AQM for services with a specific
QCI to evaluate the operation of AQM.
Measurement Points
The corresponding counter is incremented by the number of packets discarded by AQM for
services with a specific QCI each time AQM discards packets of non-GBR bearers.
Formula
None

Unit
None
Related Features
L.AQM.PacketDropNum.Q Multi-mode: None

CI.6 GSM: None
UMTS: None
LTE: LOFD-001027 Active Queue Management
(AQM)

CI.7 GSM: None
UMTS: None
(AQM)

CI.8 GSM: None
UMTS: None
(AQM)

CI.9 GSM: None
UMTS: None
(AQM)
1.9.22 Number of Times That Dynamic AC Barring Is Triggered

Counters
1526729499 L.Dyn.ACBar.T Number of BTS3900, L

rigger.Num times that BTS3900 LTE
dynamic AC
Barring is
triggered

Description
The counter measures the number of times that dynamic AC Barring is triggered in a cell.
Measurement Points
The L.Dyn.ACBar.Trigger.Num counter is incremented by 1 in a cell within a measurement
period each time the eNodeB determines that the triggering conditions for dynamic AC
Barring are met and triggers dynamic AC Barring.
Formula
None
Unit
None
Related Features
L.Dyn.ACBar.Trigger.Num Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-070207 Intelligent Access Class
TDLOFD-080202 Control
Intelligent Access Class
Control
1.9.23 Number of Times That Dynamic AC Barring Is Cancelled
Counters
1526729500 L.Dyn.ACBar.C Number of BTS3900, L

ancel.Num times that BTS3900 LTE
dynamic AC
Barring is
cancelled
Description
The counter measures the number of times that dynamic AC Barring is cancelled in a cell.

Measurement Points
The L.Dyn.ACBar.Cancel.Num counter is incremented by 1 in a cell within a measurement
period each time the eNodeB determines that the cancellation conditions for dynamic AC
Barring are met and cancels dynamic AC Barring.
Formula
None
Unit
None
Related Features
L.Dyn.ACBar.Cancel.Num Multi-mode: None

GSM: None
UMTS: None
Control
1.9.24 Number of Times That Parameters Related to Dynamic AC

Barring Are Adjusted
Counters
1526729501 L.Dyn.ACBar. Number of BTS3900, L

Adjust.Num times that BTS3900 LTE
parameters
related to
dynamic AC
Barring are
adjusted
Description
The counter measures the number of times that the parameters related to dynamic AC Barring
are adjusted in a cell.

Measurement Points
The L.Dyn.ACBar.Adjust.Num counter is incremented by 1 each time the eNodeB adjusts the
parameters related to dynamic AC Barring after dynamic AC Barring is triggered.
Formula
None
Unit
None
Related Features
L.Dyn.ACBar.Adjust.Num Multi-mode: None

GSM: None
UMTS: None
Control
1.9.25 Control Duration of Dynamic AC Barring
Counters
1526729502 L.Dyn.ACBar.C Control BTS3900, L

ontrol.Dur duration of BTS3900 LTE
dynamic AC
Barring
Description
The counter measures the control duration of dynamic AC Barring in a cell.
Measurement Points
After dynamic AC Barring is triggered, the eNodeB checks whether dynamic AC Barring is
cancelled each second. The L.Dyn.ACBar.Control.Dur counter is incremented by 1 each time
dynamic AC Barring is not cancelled.

Formula
None
Unit
s
Related Features
L.Dyn.ACBar.Control.Dur Multi-mode: None

GSM: None
UMTS: None
Control
1.9.26 Number of Times that the TDSCDMA Network is

Configured as the Highest Frequency Priority in an IMMCI IE
Counters

catedPri.TDSC times that the BTS3900 LTE
DMA.High TDSCDMA
network is
configured as
the highest
frequency
priority in an
IMMCI IE



DedicatedPri.T times that the BTS3900 LTE
DSCDMA.High TDSCDMA
network is
configured as
the highest
frequency
priority in an
IMMCI IE
Triggered
Because of
High Load
Description
The counters measure the number of times that the TD-SCDMA network is configured as the
highest frequency priority in an IMMCI IE.
The signaling process involved in these counters complies with that described in 5.3.8 in
3GPP TS 36.331 (V10.4.0).
These counters apply only to LTE TDD.
Measurement Points
As shown at point A in Figure 1-108, the L.RRCRel.DedicatedPri.TDSCDMA.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 TDSCDMA
network is configured as the highest frequency priority in a cell.
The L.RRCRel.load.DedicatedPri.TDSCDMA.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 TDSCDMA network is configured as the
highest frequency priority in a high-load cell triggered by load balancing.
Figure 1-108

Formula
None
Unit
None
Related Features
L.RRCRel.DedicatedPri.TD Multi-mode: None

SCDMA.High GSM: None
UMTS: None
LTE: TDLOFD-001044 Inter-RAT Load Sharing to
UTRAN

i.TDSCDMA.High GSM: None
UMTS: None
UTRAN
1.9.27 Number of S1 Signaling Messages Received or Sent by a

Cell
Counters
1526729659 L.Signal.Num.S Number of S1 BTS3900, L

1 signaling BTS3900 LTE
messages
received or sent
by a cell
Description
The counter measures the number of S1 signaling messages received or sent by a cell for UEs.
Measurement Points
The L.Signal.Num.S1 counter is incremented by 1 each time the cell receives or sends an S1
signaling message (excluding the ERROR INDICATION message) for a UE. If the eNodeB

discards the S1 signaling messages because of overload, the cell to which the messages are
sent cannot be discriminated, and therefore this counter is not incremented.
Formula
None
Unit
None
Related Features
L.Signal.Num.S1 Multi-mode: None

GSM: None
UMTS: None
1.9.28 Number of X2 Signaling Messages Received or Sent by a

Cell
Counters
1526729660 L.Signal.Num. Number of X2 BTS3900, L

X2 signaling BTS3900 LTE
messages
received or sent
by a cell
Description
The counter measures the number of X2 signaling messages received or sent by a cell for
UEs.
Measurement Points
The L.Signal.Num.X2 counter is incremented by 1 each time the cell receives or sends an X2
signaling message (excluding the ERROR INDICATION message) for a UE. If the eNodeB
discards the X2 signaling messages because of overload, the cell to which the messages are
sent cannot be discriminated, and therefore this counter is not incremented.

Formula
None
Unit
None
Related Features
L.Signal.Num.X2 Multi-mode: None

GSM: None
UMTS: None
1.9.29 Distribution of Out-of-Synchronization Durations for UEs

in a Cell
Counters
1526730104 L.User.UL.Uns Number of BTS3900, L

ync.Dur.Index0 times the BTS3900 LTE
duration of a
UE in the out-
of-
synchronization
state in a cell
ranges within
index 0

duration of a
UE in the out-
of-
synchronization
state in a cell
ranges within
index 1



duration of a
UE in the out-
of-
synchronization
state in a cell
ranges within
index 2

duration of a
UE in the out-
of-
synchronization
state in a cell
ranges within
index 3

duration of a
UE in the out-
of-
synchronization
state in a cell
ranges within
index 4

duration of a
UE in the out-
of-
synchronization
state in a cell
ranges within
index 5

duration of a
UE in the out-
of-
synchronization
state in a cell
ranges within
index 6



duration of a
UE in the out-
of-
synchronization
state in a cell
ranges within
index 7

duration of a
UE in the out-
of-
synchronization
state in a cell
ranges within
index 8
Description
The counters measure the number of times the duration of a UE in the out-of-synchronization
state in a cell falls in a specific range.
Duration indexes (0 to 8) are defined as follows:
Index 0: (0, 10s]
Index 1: (10s, 20s]
Index 2: (20s, 30s]
Index 3: (30s, 40s]
Index 4: (40s, 50s]
Index 5: (50s, 60s]
Index 6: [60s, 120s]
Index 7: (120s, 200s]
Index 8: (200s, +)
Measurement Points
When a UE in a cell enters the out-of-synchronization state, the eNodeB starts to measure the
duration till the UE enters the synchronized state again. If the duration falls in a specific
range, the corresponding counter is incremented by 1, accordingly.

Formula
None
Unit
None
Related Features
L.User.UL.Unsync.Dur.Inde Multi-mode: None

x0 GSM: None
UMTS: None

x1 GSM: None
UMTS: None

x2 GSM: None
UMTS: None

x3 GSM: None
UMTS: None

x4 GSM: None
UMTS: None

x5 GSM: None
UMTS: None


x6 GSM: None
UMTS: None

x7 GSM: None
UMTS: None

x8 GSM: None
UMTS: None
1.9.30 Number of Semi-persistent Scheduling Times in a Cell

Counters
1526730236 L.Sps.UL.TB.In Number of BTS3900, L

tvl40ms uplink semi- BTS3900 LTE
persistent
scheduling
times in a cell
(within 40 ms)
Description
The counters measure the number of uplink or downlink semi-persistent scheduling times
performed in a cell.
Measurement Points
None
Formula
None

Unit
None
Related Features
L.Sps.UL.TB.Intvl40ms Multi-mode: None

GSM: None
UMTS: None
LTE: TDLOFD-001016 VoIP Semi-persistent
Scheduling
1.9.31 Number of Semi-persistent Scheduling Failures in a Cell
Counters
1526730237 L.Sps.UL.TB.In Number of BTS3900, L

tvl40ms.Err failed uplink BTS3900 LTE
semi-persistent
scheduling
transmissions
within 40 ms in
a cell
Description
The counters measure the number of times the transmission of uplink or downlink semi-
persistent scheduling fails in a cell.
Measurement Points
None
Formula
None
Unit
None

Related Features
L.Sps.UL.TB.Intvl40ms.Err Multi-mode: None

GSM: None
UMTS: None
LTE: TDLOFD-001016 VoIP Semi-persistent
Scheduling
1.9.32 Number of Times the eNodeB Delivers the Load-Triggered

Inter-Frequency Measurement Configuration to a UE
Counters
1526730526 L.InterFreq.Loa Number of BTS3900, L

d.Meas.Num.Ce times the BTS3900 LTE
ll eNodeB
delivers the
load-triggered
inter-frequency
measurement
configuration to
a UE
Description
The counter measures the number of times the eNodeB successfully delivered the load-
triggered inter-frequency measurement configuration to UEs in a cell.
V11.7.0.
Measurement Points
As shown at point A in Figure 1-109, the L.InterFreq.Load.Meas.Num.Cell counter is
incremented by 1 each time the eNodeB receives an RRC Connection Reconfiguration
Complete message as a response to an RRC Connection Reconfiguration message carrying
the MeasConfig IE for MLB and measIdToAddModList in the MeasConfig IE contains
measIDs that are intended for neighboring frequencies, regardless of the number of measIDs.

Figure 1-109
Formula
None
Unit
None
Related Features
L.InterFreq.Load.Meas.Num Multi-mode: None

.Cell GSM: None
UMTS: None
LOFD-070215 Intra-LTE User Number
TDLOFD-070215 Load Balancing
Intra-LTE User Number
Load Balancing

1.9.33 Number of Times the Load-Triggered Inter-Frequency

Measurement is Successful
Counters
1526730527 L.InterFreq.Loa Number of BTS3900, L

d.MeasSucc.Nu times the load- BTS3900 LTE
m.Cell triggered inter-
frequency
measurement is
successful
Description
The counter measures the number of times the load-triggered inter-frequency measurement
succeeded.
V11.7.0.
Measurement Points
As shown at point B in Figure 1-110, the L.InterFreq.Load.MeasSucc.Num.Cell counter is
incremented by 1 each time the following conditions are met: (1) The eNodeB sends an RRC
Connection Reconfiguration message carrying the MeasConfig IE to a UE because of load
balancing. (2) measIdToAddModList in the MeasConfig IE contains measIDs that are
intended for neighboring frequencies, regardless of the number of measIDs. (3) Then the
eNodeB receives a measurement report for any of the neighboring frequencies. The counter is
incremented by 1 at most for one measurement configuration.

Figure 1-110
Formula
None
Unit
None
Related Features
L.InterFreq.Load.MeasSucc. Multi-mode: None

Num.Cell GSM: None
UMTS: None
Load Balancing

1.9.34 Duration in Which a Cell with Inter-Frequency Load

Balancing Enabled Is in the High-Load State
Counters
1526730528 L.InterFreq.Hig Duration in BTS3900, L

hLoad.Dur.Cell which a cell BTS3900 LTE
with inter-
frequency load
balancing
enabled is in the
high-load state
Description
The counter measures the duration in which a cell is in the high-load state when inter-
frequency load balancing or inter-frequency blind load balancing is enabled.
Measurement Points
When inter-frequency load balancing or inter-frequency blind load balancing is enabled, the
load status of the cell is sampled per second. The L.InterFreq.HighLoad.Dur.Cell counter is
incremented by 1 each time the cell is in the high-load state.
Formula
None
Unit
s
Related Features
L.InterFreq.HighLoad.Dur.C Multi-mode: None

ell GSM: None
UMTS: None
Load Balancing

1.9.35 Number of Times a Cell with Inter-Frequency Load

Balancing Enabled Enters from the Low-Load State to the High-
Load State
Counters
1526730529 L.InterFreq.Hig Number of BTS3900, L

hLoad.Num.Cel times a cell BTS3900 LTE
l with inter-
frequency load
balancing
enabled enters
from the low-
load state to the
high-load state
Description
The counter measures the number of times a cell enters from the low-load state to the high-
load state when inter-frequency load balancing or inter-frequency blind load balancing is
enabled.
Measurement Points
When inter-frequency load balancing or inter-frequency blind load balancing is enabled, the
L.InterFreq.HighLoad.Num.Cell counter is incremented by 1 each time the cell enters from
the low-load state to the high-load state.
Formula
None
Unit
None

Related Features
L.InterFreq.HighLoad.Num. Multi-mode: None

Cell GSM: None
UMTS: None
Load Balancing
1.9.36 Number of Uplink and Downlink TTIs

Counters
1526730558 L.Cell.DL.PDS Number of BTS3900, L

CH.Tti.Num TTIs on the BTS3900 LTE
PDSCH
1526730559 L.Cell.UL.PUS Number of BTS3900, L

CH.Tti.Num TTIs on the BTS3900 LTE
PUSCH
Description
The counters measure the number of TTIs on the PUSCH and that on the PDSCH. The
number of TTIs in the special slot that can transmit service data is also counted.
Measurement Points
The number of TTIs on the PUSCH and that on the PDSCH are calculated respectively in
each measurement period. In the LTE TDD system, if downlink data can be transmitted in
DwPTS, the number of TTIs on the PDSCH is incremented by 1. The counters apply only to
the LTE TDD system.
Formula
None
Unit
None

Related Features
L.Cell.DL.PDSCH.Tti.Num Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002025 Basic Scheduling
TDLBFD-002025 Basic Scheduling
L.Cell.UL.PUSCH.Tti.Num Multi-mode: None

GSM: None
UMTS: None
1.9.37 Number of times that a cell is unavailable
Counters
1526732089 L.Cell.Unavail. Number of BTS3900, L

Num times that a cell BTS3900 LTE
is unavailable
Description
The counter measures the number of times that a cell is out of service.
Measurement Points
The counter is incremented by 1 each time the cell status changes from available to
unavailable.The counter is measured based on the cell status change. Therefore, when the cell
stays in the unavailable state, the cell status does not change and the counter value does not
increase.
Formula
None
Unit
None

Related Features
L.Cell.Unavail.Num Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001025 Adaptive Power
LOFD-001040 Consumption
LOFD-001042 Low Power Consumption
Mode
LOFD-001074
TDLOFD-001042 Carriers in the Same
TDLOFD-001040 Coverage
Coverage of UMTS
Network
Coverage
Low Power Consumption
Mode
1.9.38 Uplink and Downlink Voice Quality

Counters
1526732687 L.Voice.VQI.A Number of BTS3900, L

MRWB.UL.Exc times uplink BTS3900 LTE
ellent.Times voice quality of
AMR-WB
services is
Excellent

MRWB.UL.Go times uplink BTS3900 LTE
od.Times voice quality of
AMR-WB
services is
Good



MRWB.UL.Ac times uplink BTS3900 LTE
cept.Times voice quality of
AMR-WB
services is
Accept

MRWB.UL.Poo times uplink BTS3900 LTE
r.Times voice quality of
AMR-WB
services is Poor

MRWB.UL.Ba times uplink BTS3900 LTE
d.Times voice quality of
AMR-WB
services is Bad

MRWB.DL.Exc times downlink BTS3900 LTE
ellent.Times voice quality of
AMR-WB
services is
Excellent

MRWB.DL.Go times downlink BTS3900 LTE
od.Times voice quality of
AMR-WB
services is
Good

MRWB.DL.Ac times downlink BTS3900 LTE
cept.Times voice quality of
AMR-WB
services is
Accept

MRWB.DL.Poo times downlink BTS3900 LTE
r.Times voice quality of
AMR-WB
services is Poor

MRWB.DL.Ba times downlink BTS3900 LTE
d.Times voice quality of
AMR-WB
services is Bad

Description
The counters measure uplink and downlink voice quality of AMR-WB services in a cell, if
voice quality monitoring (VQM) is enabled. VQM is controlled by the VQMAlgoSwitch
parameter in the ENodeBAlgoSwitch MO.
Measurement Points
The eNodeB randomly samples UEs running voice services in an available cell per 2.5s.
Within each sampling period, if a sampled UE is running adaptive multirate wideband (AMR-
WB) or adaptive multirate narrowband (AMR-NB) services, the eNodeB evaluates the voice
quality of the UE. The voice quality can be classified into Bad, Poor, Accept, Good, and
Excellent. The corresponding counter is incremented by 1 each time the voice quality is
detected to be Bad, Poor, Accept, Good, or Excellent. For counters with the separation of the
AMR-WB and AMR-NB services, the eNodeB accumulates number of samples with different
voice quality for AMR-WB and AMR-NB services within separately.
Formula
None
Unit
None
Related Features
L.Voice.VQI.AMRWB.UL. Multi-mode: None

Excellent.Times GSM: None
UMTS: None

Good.Times GSM: None
UMTS: None

Accept.Times GSM: None
UMTS: None


Poor.Times GSM: None
UMTS: None

Bad.Times GSM: None
UMTS: None
L.Voice.VQI.AMRWB.DL. Multi-mode: None

Excellent.Times GSM: None
UMTS: None

Good.Times GSM: None
UMTS: None

Accept.Times GSM: None
UMTS: None

Poor.Times GSM: None
UMTS: None

Bad.Times GSM: None
UMTS: None

1.9.39 Number of Times that a UE Is Detected Based on the

SRLTE Optimization Feature to Be Switched Out of the State of
Performing LTE Services
Counters
1526732719 L.SRLTE.Status Number of BTS3900, L

.HOOut times that a UE BTS3900 LTE
is detected
based on the
SRLTE
optimization
feature to be
switched out of
the state of
performing LTE
services
1526732720 L.SRLTE.Status Number of BTS3900, L

.HOIn times that a UE BTS3900 LTE
is detected
based on the
SRLTE
optimization
feature to be
switched back
to the state of
performing LTE
services
Description
After an SRLTE UE camps on or is activated in the LTE network, it periodically leaves the
LTE network to monitor the paging channels of other RATs, and will return to the LTE
network after the monitoring. The eNodeB is not aware of the preceding procedure and
therefore schedules the UE even when the UE has leaved the LTE network. Therefore, the
SRLTE optimization feature is enabled to help the eNodeB to determine the UE state based on
DTX detection.
The counters measure the number of times that the eNodeB detects that state change (from the
state of performing LTE services to the state of paging monitoring in other RATs and from the
state of paging monitoring in other RATs back to the state of performing LTE services,
respectively) of UEs in the cell based on the SRLTE optimization feature so as to evaluate the
usage of this feature.
Measurement Points
When the eNodeB detects that the SRLTE UE meets the preconfigured consecutive DTX
count (total number of PUSCH DTXs and PDSCH DTXs), the eNodeB regards that the UE

has switched from the state of performing LTE services to the state of paging monitoring in
other RATs and stops scheduling, and the L.SRLTE.Status.HOOut counter is incremented by
1. Then, if the UE is scheduled in a TTI and is not in DTX state, the eNodeB regards that the
UE has changed from the state of paging monitoring in other RATs back to the state of
performing LTE services, and the L.SRLTE.Status.HOIn counter is incremented by 1.
Here, the number of consecutive DTX number and the period for not scheduling the UE are
specified by the DTXThrd and SuspendTime parameters. You can run the MOD CELLSRLTE
command to set them.
Formula
None
Unit
None
Related Features
L.SRLTE.Status.HOOut Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-080212 SRLTE Optimization
L.SRLTE.Status.HOIn Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-080212 SRLTE Optimization
1.9.40 Number of Normal Voice Call Releases in the Cell (Poor

Uplink Voice Quality)
Counters
1526732890 L.Voice.NormR Number of BTS3900, L

el.UL.LowQual normal voice BTS3900 LTE
ity call releases in
the cell (poor
uplink voice
quality)


1526732891 L.Voice.NormR Number of BTS3900, L

el.DL.LowQual normal voice BTS3900 LTE
ity call releases in
the cell (poor
downlink voice
quality)
Description
The counters measure the number of times UEs are normally released in a cell but the uplink
or downlink voice quality of the UEs is poor for AmrLowQualRelPeriodNum number of 2.5-
second periods before the UEs are released, if voice quality monitoring (VQM) is enabled.
VQM is controlled by the VQMAlgoSwitch parameter in the ENodeBAlgoSwitch MO.
Measurement Points
The eNodeB randomly samples UEs that have a bearer with QCI 1 and apply AMR. This
counter is incremented by 1 if any of the following conditions is met by a UE in each 2.5s
period for AmrLowQualRelPeriodNum times consecutively before the UE is released: 1. The
uplink VoIP packet loss rate over the air interface is higher than
AmrNbRadioLowQualRelThd/AmrWbRadioLowQualRelThd. 2. Number of uplink packets
received by the eNodeB/Theoretical number of uplink packets < AmrNbRcvLowQualRelThd/
AmrWbRcvLowQualRelThd. If multiple UEs meet the preceding condition simultaneously,
the counter is incremented by the number of UEs.
Formula
None
Unit
None
Related Features
L.Voice.NormRel.UL.LowQ Multi-mode: None

uality GSM: None
UMTS: None
L.Voice.NormRel.DL.LowQ Multi-mode: None

uality GSM: None
UMTS: None

1.9.41 Number of Times that a UE Experiences Uplink Voice Mute

in the Cell
Counters
1526732892 L.Voice.UL.Sile Number of BTS3900, L

nt.Num times that a UE BTS3900 LTE
experiences
uplink voice
mute in the cell
1526732893 L.Voice.DL.Sile Number of BTS3900, L

nt.Num times that a UE BTS3900 LTE
experiences
downlink voice
mute in the cell
Description
The counters measure the number of times that UEs experience uplink or downlink voice
mute in a cell, if voice quality monitoring (VQM) is enabled. VQM is controlled by the
VQMAlgoSwitch parameter in the ENodeBAlgoSwitch MO.
Measurement Points
The eNodeB randomly samples UEs that apply AMR. This counter is incremented by 1 if any
of the following conditions is met by a UE in each 2.5s period for AmrSilentPeriodNum times
consecutively: 1. The uplink packet loss rate over the air interface is higher than
AmrNbSilentThd/AmrWbSilentThd. 2. Number of uplink packets received by the eNodeB/
Theoretical number of uplink packets < AmrNbRcvLowQualRelThd/
AmrWbRcvLowQualRelThd. In this case, the eNodeB regards that the UE is experiencing
voice mute. If after a UE is detected as experiencing voice mute, the packet loss rates in later
2.5s-periods are all higher than the preceding threshold, this counter is not incremented for
later periods until the packet loss rate is lower than or equal to the preceding threshold again.
Formula
None
Unit
None

Related Features
L.Voice.UL.Silent.Num Multi-mode: None

GSM: None
UMTS: None
L.Voice.DL.Silent.Num Multi-mode: None

GSM: None
UMTS: None
1.9.42 Number of Times that an eNodeB Attempts to Measure the

Time Difference Among eNodeBs by Using UEs Performing
Inter-eNodeB Handovers
Counters
1526732913 L.AISS.IntereN Number of BTS3900, L

odeB.HoMeas. times that an BTS3900 LTE
Att eNodeB
attempts to
measure the
time difference
among
eNodeBs by
using UEs
performing
inter-eNodeB
handovers
Description
The measurement of the time difference among different eNodeBs is used to measure the start
time difference of the same radio frame among adjacent eNodeBs. When the time difference
does not meet the requirements for synchronization, the eNodeB automatically adjusts the
clock. This ensures that the start time difference of the same radio frame meets the
requirements of synchronization. This counter measures the number of times that the source
eNodeB attempts to measure the time difference among eNodeBs by using UEs performing
inter-eNodeB handovers.

Measurement Points
As shown at point A in Figure 1-111, the L.AISS.IntereNodeB.HoMeas.Att counter is
incremented by 1 each time the eNodeB decides to perform an inter-eNodeB handover and
initiates a timer different measurement when receiving a Measurement Report message from
the UE.
Figure 1-111
Formula
None
Unit
None
Related Features
L.AISS.IntereNodeB.HoMe Multi-mode: None

as.Att GSM: None
UMTS: None
LTE: LOFD-080216 Uu based Soft
Synchronization

1.9.43 Number of Times that an eNodeB Attempts to Measure the

Time Difference Among eNodeBs by Using Inter-eNodeB CEUs
Counters

odeB.CeMeas. times that an BTS3900 LTE
Att eNodeB
attempts to
measure the
time difference
among
eNodeBs by
using inter-
eNodeB CEUs
Description
requirements of synchronization. This counter measures the number of times that the serving
eNodeB attempts to measure the time difference among eNodeBs by using its inter-eNodeB
CEUs.
Measurement Points
As shown at point A in Figure 1-112, the L.AISS.IntereNodeB.CeMeas.Att counter is
incremented by 1 each time the eNodeB initiates a measurement of time difference among
eNodeBs using CEUs.

Figure 1-112
Formula
None
Unit
None
Related Features
L.AISS.IntereNodeB.CeMe Multi-mode: None

as.Att GSM: None
UMTS: None
Synchronization

1.9.44 Number of Times that an eNodeB Successfully Measures

the Time Difference Among eNodeBs by Using UEs that Are
Performing Inter-eNodeB Handovers
Counters

odeB.HoMeas. times that an BTS3900 LTE
Succ eNodeB
successfully
measures the
time difference
among
eNodeBs by
using UEs that
are performing
inter-eNodeB
handovers
Description
requirements of synchronization. The counter measures the number of times that an eNodeB
successfully measures the time difference among eNodeBs by using UEs that are performing
inter-eNodeB handovers.
Measurement Points
As shown at point B in Figure 1-113, the L.AISS.IntereNodeB.HoMeas.Succ counter is
incremented by 1 each time the eNodeB measures the time difference among eNodeBs by
using UEs that are performing handovers and then sends an AISS Measure RPT message to
the eCoordinator.

Figure 1-113
Formula
None
Unit
None
Related Features
L.AISS.IntereNodeB.HoMe Multi-mode: None

as.Succ GSM: None
UMTS: None
Synchronization

1.9.45 Number of Times that an eNodeB Successfully Measures

the Time Difference Among eNodeBs by Using Inter-eNodeB
CEUs
Counters

odeB.CeMeas.S times that an BTS3900 LTE
ucc eNodeB
successfully
measures the
time difference
among
eNodeBs by
using inter-
eNodeB CEUs
Description
requirements of synchronization. The counter measures the number of times that an eNodeB
successfully measures the time difference among eNodeBs by using inter-eNodeB CEUs.
Measurement Points
As shown at point B in Figure 1-114, the L.AISS.IntereNodeB.CeMeas.Succ counter is
incremented by 1 each time the eNodeB measures the time difference among eNodeBs by
using inter-eNodeB CEUs and then sends an AISS Measure RPT message to the
eCoordinator.

Figure 1-114
Formula
None
Unit
None
Related Features
L.AISS.IntereNodeB.CeMe Multi-mode: None

as.Succ GSM: None
UMTS: None
Synchronization

1.9.46 Number of times when a cell receives a power

configuration message from the centralized scheduler but the
validation period expires
Counters
1526733010 L.Sig.PowerCfg Number of BTS3900, L

.Fail.TimeOut times when a BTS3900 LTE
cell receives a
power
configuration
message from
the centralized
scheduler but
the validation
period expires
Description
The counter measures the number of times when a cell receives a power configuration
message from the centralized scheduler but the validation period expires.
The L.Sig.PowerCfg.Fail.TimeOut counter applies only to LTE TDD.
Measurement Points
The counter measures the number of power configuration messages received in a cell from the
centralized scheduler in each measurement period. At the end of the measurement period, the
measurement result is used as the value of the counter.
Formula
None
Unit
None

Related Features
L.Sig.PowerCfg.Fail.TimeO Multi-mode: None

ut GSM: None
UMTS: None
LTE: TDLOFD-080203 Coordinated Scheduling
based Power Control (Cloud
BB)
1.9.47 Number of cell received configuration message from centre

controller
Counters
1526733011 L.Sig.PowerCfg Number of BTS3900, L

.Att power BTS3900 LTE
configuration
messages
received in a
cell
Description
The counter measures the number of cell received configuration message from centre
controller.
The L.Sig.PowerCfg.Att counter applies only to LTE TDD.
Measurement Points
The counter measures the number of expired power configuration messages received in a cell
from the centralized scheduler in each. measurement period. At the end of the measurement
period, the measurement result is used as the value of the counter.
Formula
None
Unit
None

Related Features
L.Sig.PowerCfg.Att Multi-mode: None

GSM: None
UMTS: None
BB)
1.9.48 Number of Downlink Subframes Without Power on the

Power Spectrun of a Cell
Counters
1526735577 L.PowerNull.D Number of BTS3900, L

L.TTI.Num downlink BTS3900 LTE
subframes
without power
Description
The counter measures the number of downlink subframes without power on the power
spectrun of a cell.
The L.PowerNull.DL.TTI.Num counter applies only to LTE TDD.
Measurement Points
The number of downlink subframes wihout power on the power spectrum of a cell is
calculated in a measurement period.
Formula
None
Unit
None

Related Features
L.PowerNull.DL.TTI.Num Multi-mode: None

GSM: None
UMTS: None
BB)
1.9.49 Number of Times Dynamic SSAC Is Triggered

Counters
1526736656 L.SSAC.Dyn.A Number of BTS3900, L

CBar.Trigger.N times dynamic BTS3900 LTE
um SSAC is
triggered
Description
The counter measures the number of times dynamic SSAC is triggered for a cell.
Measurement Points
The L.SSAC.Dyn.ACBar.Trigger.Num counter is incremented by 1 in a cell each time the
eNodeB triggers dynamic SSAC for a cell when determining that the cell meets the triggering
condition for dynamic SSAC within a measurement period.
Formula
None
Unit
None

Related Features
L.SSAC.Dyn.ACBar.Trigge Multi-mode: None

r.Num GSM: None
UMTS: None
LTE: LBFD-002009 Broadcast of system
TDLBFD-002009 information
LOFD-008002 Broadcast of system
information
TDLOFD-081222
Dynamic Service-Specific
LOFD-070207 Access Control
Dynamic Service-specific
Access Control
Control
1.9.50 Number of Times Parameters Related to Dynamic SSAC are

Adjusted
Counters

CBar.Adjust.Nu times BTS3900 LTE
m parameters
related to
dynamic SSAC
are adjusted
Description
The counter measures the number of times parameters related to dynamic SSAC are adjusted
for a cell.
Measurement Points
The L.SSAC.Dyn.ACBar.Adjust.Num counter is incremented by 1 each time the eNodeB
adjusts the parameters related to dynamic SSAC after dynamic SSAC is triggered.
Formula
None

Unit
None
Related Features
L.SSAC.Dyn.ACBar.Adjust. Multi-mode: None

Num GSM: None
UMTS: None
information
TDLOFD-081222
Access Control
Control
1.9.51 Number of Times Dynamic SSAC Is Canceled

Counters

CBar.Cancel.N times dynamic BTS3900 LTE
um SSAC is
canceled
Description
The counter measures the number of times dynamic SSAC is cancelled for a cell.
Measurement Points
The L.SSAC.Dyn.ACBar.Cancel.Num counter is incremented by 1 in a cell each time the
eNodeB cancels dynamic SSAC for a cell when determining that the cell meets the
cancellation conditions for dynamic SSAC within a measurement period.
Formula
None

Unit
None
Related Features
L.SSAC.Dyn.ACBar.Cancel Multi-mode: None

.Num GSM: None
UMTS: None
information
TDLOFD-081222
Access Control
Control
1.9.52 Duration of Dynamic SSAC
Counters
1526736659 L.SSAC.Dyn.A Duration of BTS3900, L

CBar.Control.D dynamic SSAC BTS3900 LTE
ur
Description
The counter measures the duration of dynamic SSAC for a cell.
Measurement Points
After dynamic SSAC is triggered, the eNodeB checks whether dynamic SSAC is cancelled
for a cell each second. The L.SSAC.Dyn.ACBar.Control.Dur counter is incremented by 1
each time dynamic SSAC is not cancelled.
Formula
None

Unit
None
Related Features
L.SSAC.Dyn.ACBar.Contro Multi-mode: None

l.Dur GSM: None
UMTS: None
information
TDLOFD-081222
Access Control
Control
1.9.53 Number of Times Preemptions Are Triggered by the User

Number Specification.
Counters
1526736866 L.Cell.UserSpe Number of BTS3900, L

c.PrepEmp.Prep times BTS3900 LTE
Att.Num preemptions are
triggered by the
limitation of the
UE number
specification
Description
The counter measures the number of times preemptions are triggered by the user number
specification in a cell.
Measurement Points
As shown at point A in Figure 1-115, the L.Cell.UserSpec.PrepEmp.PrepAtt.Num counter is
incremented by 1 each time the eNodeB performs the UE-number-specification-based user

admission after receiving an RRC Connection Request message from a UE and the
preemption is triggered by the limitation of the UE number specification.
Figure 1-115
Formula
None
Unit
None
Related Features
L.Cell.UserSpec.PrepEmp.P Multi-mode: None

repAtt.Num GSM: None
UMTS: None
LTE: LBFD-002023 Admission Control
pre-emption

1.9.54 Number of Times the Licensed Number of UEs Is Limited
Counters
1526736869 L.Cell.UserLic. Number of BTS3900, L

Limit.Num times the BTS3900 LTE
licensed
number of UEs
is limited
Description
The counter measures the number of times the licensed number of UEs is limited in a cell.
Measurement Points
As shown at point A in Figure 1-116, in licensed-user-number-based user admission, the
L.Cell.UserLic.Limit.Num counter is incremented by 1 each time the RRC connection of a
UE is released or the resource of a UE is preempted due to the limitation of the licensed
number of UEs. If both the licensed number of UEs and the UE number specification are
limited, this counter is not incremented.
Figure 1-116

Formula
None
Unit
None
Related Features
L.Cell.UserLic.Limit.Num Multi-mode: None

GSM: None
UMTS: None
pre-emption
1.9.55 Number of Successful Preemptions Triggered by the

Limitation of the Licensed Number of Ues
Counters
1526736870 L.Cell.UserLic. Number of BTS3900, L

PrepEmp.Succ. successful BTS3900 LTE
Num preemptions
triggered by the
limitation of the
licensed
number of UEs
Description
The counter measures the number of times preemptions are triggered by the limitation of the
licensed number of UEs in a cell.
Measurement Points
As shown at point A in Figure 1-117, the L.Cell.UserLic.PrepEmp.Succ.Num counter is
incremented by 1 each time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST

message from the MME and a preemption is triggered by the limitation of the licensed
number of UEs and the preemption is successful. If both the licensed number of UEs and the
UE number specification are limited, this counter is not incremented.
Figure 1-117
Formula
None
Unit
None
Related Features
L.Cell.UserLic.PrepEmp.Su Multi-mode: None

cc.Num GSM: None
UMTS: None
pre-emption

1.9.56 Number of Times IRC, MRC, or Smart IRC Is Used on the

PUSCH
Counters
1526736889 L.ULIRC.PUS Number of BTS3900, L

CH.MRC.Num times MRC is BTS3900 LTE
used on the
PUSCH

CH.IRC.Num times IRC is BTS3900 LTE
used on the
PUSCH

CH.SmartIRC. times smart BTS3900 LTE
Num IRC is used on
the PUSCH
Description
The counters measure the number of times IRC is used on the PUSCH, the number of times
MRC is used on the PUSCH, and the number of times smart IRC is used on the PUSCH.
The number of times IRC is used on the PUSCH can be used to evaluate whether PUSCH
IRC takes effect. In addition, the ratio of the number of times IRC is used on the PUSCH to
the number of times MRC is used on the PUSCH can be used to evaluate the interference
from neighboring cells.
The L.ULIRC.PUSCH.SmartIRC.Num counter applies only to TDD UBBPd boards.
Measurement Points
The number of times MRC, IRC, smart IRC is used by all PRBs of all UEs on the PUSCH is
sampled at the sampling points per ten milliseconds. At the end of a measurement period, the
sum of these sampling results per algorithm is used as the values of the corresponding
counters.
Supplementary notes for special scenarios:
1. In SFN scenarios, the counters are measured by physical cell.
2. To ensure that all sampling points are evenly distributed from subframes 0 to 9, the
sampling times at different sampling periods are different and changed in a round robin
manner by subframe number. For example, in a sampling period, the sampling time is the first
millisecond (subframe 0). Then in the next sampling period, the sampling time is the second
millisecond (subframe 1).

3. In LTE TDD, if the sampling time is a downlink subframe or a special subframe, the
sampling time is delayed to the next uplink subframe within the same sampling period. The
sampling period is still ten milliseconds.
4. The counters do not apply to LBBPc boards or BTS3202E.
5. The L.ULIRC.PUSCH.SmartIRC.Num counter applies only to TDD UBBPd boards.
Formula
None
Unit
None
Related Features
L.ULIRC.PUSCH.MRC.Nu Multi-mode: None

m GSM: None
UMTS: None
LTE: LOFD-001012 UL Interference Rejection
TDLOFD-001012 Combining
UL Interference Rejection
Combining
L.ULIRC.PUSCH.IRC.Num Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001012 UL Interference Rejection
TDLOFD-001012 Combining
UL Interference Rejection
Combining
L.ULIRC.PUSCH.SmartIR Multi-mode: None

C.Num GSM: None
UMTS: None
LTE: TDLOFD-001012 UL Interference Rejection
Combining

1.9.57 Number of Times IRC or MRC Is Used on the PUCCH
Counters
1526736891 L.CtrlIRC.PUC Number of BTS3900, L

used on the
PUCCH
1526736892 L.CtrlIRC.PUC Number of BTS3900, L

used on the
PUCCH
Description
The counters measure the number of times IRC is used on the PUCCH and the number of
times MRC is used on the PUCCH.
The number of times IRC is used on the PUCCH can be used to evaluate whether PUCCH
IRC takes effect. In addition, the ratio of the number of times IRC is used on the PUCCH to
the number of times MRC is used can be used on the PUCCH to evaluate the interference
Measurement Points
The number of times MRC or IRC is used on the PUCCH is collected at the sampling points
per ten milliseconds. Which algorithm (MRC or IRC) is used on the PUCCH per code
channel per slot is a sample. At the end of a measurement period, the sum of these sampling
results per algorithm is used as the values of the corresponding counters.
2. To ensure that all sampling points are evenly distributed from subframes 0 to 9, the
sampling times at different sampling periods are different and changed in a round robin
manner by subframe number. For example, in a sampling period, the sampling time is the first
millisecond (subframe 0). Then in the next sampling period, the sampling time is the second
millisecond (subframe 1).
3. In LTE TDD, if the sampling time is a downlink subframe or a special subframe, the
sampling time is delayed to the next uplink subframe within the same sampling period. The
sampling period is still ten milliseconds.
4. The counters do not apply to LBBPc boards or BTS3202E.
Formula
None

Unit
None
Related Features
L.CtrlIRC.PUCCH.MRC.N Multi-mode: None

um GSM: None
UMTS: None
LTE: LOFD-001094 Control Channel IRC
TDLOFD-001094 Control Channel IRC
L.CtrlIRC.PUCCH.IRC.Nu Multi-mode: None

m GSM: None
UMTS: None
1.9.58 Number of Times IRC or MRC Is Used on the PRACH
Counters
1526736893 L.CtrlIRC.PRA Number of BTS3900, L

used on the
PRACH
1526736894 L.CtrlIRC.PRA Number of BTS3900, L

used on the
PRACH
Description
The counters measure the number of times IRC is used on the PRACH and the number of
times MRC is used on the PRACH.
The number of times IRC is used on the PRACH can be used to evaluate whether PRACH
IRC takes effect. In addition, the ratio of the number of times IRC is used on the PRACH to
the number of times MRC is used on the PRACH can be used to evaluate the interference

Measurement Points
The number of times PRACH MRC or IRC is used in each TTI when the PRACH exists is
sampled. Which algorithm (MRC or IRC) is used per RB on the PRACH is a sample. At the
end of a measurement period, the sum of these sampling results per algorithm is used as the
values of the corresponding counters.
2. For LBBPc boards and BTS3202E, these counters apply only to cells that use two antennas
for reception not to cells that use four antennas for reception.
Formula
None
Unit
None
Related Features
L.CtrlIRC.PRACH.MRC.N Multi-mode: None

um GSM: None
UMTS: None
L.CtrlIRC.PRACH.IRC.Nu Multi-mode: None

m GSM: None
UMTS: None

1.9.59 Number of SPID-based Target PLMN Selection Attempts

Counters
1526737821 L.SPID.SelectT Number of BTS3900, L

gtPLMN.AttOu SPID-based BTS3900 LTE
t target PLMN
selection
attempts
Description
The counter measures the number of SPID-based target PLMN selection attempts in a cell,
include intra-handover, inter-handover, redirection, CSFB, SRVCC, CCO, NACC. This
counter can be used to check the number of times the function of SPID-based PLMN selection
takes effect.
V10.4.0 and sections 5.3.8 and 5.4.3.3 in 3GPP TS 36.331 V8.21.0.
Measurement Points
As shown at point A in Figure 1-118, the L.SPID.SelectTgtPLMN.AttOut counter is
incremented by 1 each time the eNodeB determines to perform a blind intra-eNodeB
handover (the target cell is determined by the function of SPID-based PLMN selection) or a
measurement-based intra-eNodeB handover (the frequencies contained in the measurement
configuration are determined by the function of SPID-based PLMN selection).
incremented by 1 each time the source eNodeB determines to perform a blind X2-based
measurement-based X2-based handover (the frequencies contained in the measurement
incremented by 1 each time the source eNodeB determines to perform a blind S1-based
measurement-based S1-based handover (the frequencies contained in the measurement
incremented by 1 each time the eNodeB determines to perform a blind EUTRAN-to-
WCDMA handover, a blind EUTRAN-to-GERAN handover(the target cell is determined by
the function of SPID-based PLMN selection), or a NACC, or a blind CCO (the target cell is
determined by the function of SPID-based PLMN selection) or the eNodeB determines to
perform a measurement-based EUTRAN-to-WCDMA handover or a measurement-based
EUTRAN-to-GERAN handover (the frequencies contained in the measurement configuration
are determined by the function of SPID-based PLMN selection).
incremented by 1 each time the eNodeB determines to perform a redirection to an E-UTRAN,

WCDMA, or GERAN cell and sends an RRC Connection Release to the UE (the target
frequency is determined by the function of SPID-based PLMN selection).
Figure 1-118
Figure 1-119

Figure 1-120
Figure 1-121

Figure 1-122
Formula
None
Unit
None
Related Features
L.SPID.SelectTgtPLMN.Att Multi-mode: None

Out GSM: None
UMTS: None
Camp & Handover Based on
SPID

1.9.60 Number of times the eCoordinator triggers interference

coordination in high-speed railway scenarios
Counters
1526737856 L.InterfHighSp Number of BTS3900, L

eed.Trigger.Nu times the BTS3900 LTE
m eCoordinator
triggers
interference
coordination in
high-speed
railway
scenarios
Description
The counter measures the number of times that the eCoordinator triggers interference
coordination in high-speed railway scenarios, that is, the number of times the eCoordinator
triggers power decrease in a high-speed cell or PRB restriction in a common cell. This counter
applies only to LTE TDD.
Measurement Points
The L.InterfHighSpeed.Trigger.Num counter is incremented by 1 each time the eCoordinator
triggers power decrease or PRB restriction in a cell.
Formula
None
Unit
None
Related Features
L.InterfHighSpeed.Trigger. Multi-mode: None

Num GSM: None
UMTS: None
LTE: TDLOFD-081218 Interference Coordination in
High-Speed Railway
Scenarios

1.9.61 Number of times the eCoordinator stops interference

coordination in high-speed railway scenarios
Counters
1526737857 L.InterfHighSp Number of BTS3900, L

eed.Cancel.Nu times the BTS3900 LTE
m eCoordinator
stops
interference
coordination in
high-speed
railway
scenarios
Description
The counter measures the number of times that the eCoordinator stops interference
coordination in high-speed railway scenarios, that is, the number of times the eCoordinator
stops decreasing power in a high-speed cell or restricting PRBs in a common cell. This
counter applies only to LTE TDD.
Measurement Points
The L.InterfHighSpeed.Cancel.Num counter is incremented by 1 each time the eCoordinator
stops power decrease or PRB restriction in a cell.
Formula
None
Unit
None
Related Features
L.InterfHighSpeed.Cancel.N Multi-mode: None

um GSM: None
UMTS: None
LTE: TDLOFD-081218 Interference Coordination in
High-Speed Railway
Scenarios

1.10 DRB Measurement (Traffic.DRB.Cell)

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
Description
1526726767 L.Traffic.DRB.QCI Number of DRBs BTS3900:

.1 for services with the V100R008C00
QCI of 1 in a cell BTS3900 LTE:
V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00


Description

V100R003C00

V100R003C00

V100R003C00
1526728258 L.Traffic.DRB Number of DRBs in BTS3900:

a cell V100R008C00
BTS3900 LTE:
V100R003C00
1526730820 L.Traffic.DRB.Max Max number of BTS3900:

DRBs in a cell V100R008C01
BTS3900 LTE:
V100R008C01

.QCI.1 DRBs for services V100R008C01
with the QCI of 1 in BTS3900 LTE:
a cell V100R008C01

a cell V100R008C01

a cell V100R008C01

a cell V100R008C01

a cell V100R008C01


Description

a cell V100R008C01

a cell V100R008C01

a cell V100R008C01

a cell V100R008C01
The Traffic.DRB.Cell function subset contains counters related to DRB. Some of these
counters can be categorized in terms of the QCI. The following table shows the parent-child
relationship of the counters.
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
L.Traffic.DRB.Max L.Traffic.DRB.Max.QCI.1
L.Traffic.DRB.Max.QCI.2

1.10.1 Number of DRBs in a Cell

Counters
1526726767 L.Traffic.DRB. Number of BTS3900, L

QCI.1 DRBs for BTS3900 LTE
services with
the QCI of 1 in
a cell

services with
the QCI of 2 in
a cell

services with
the QCI of 3 in
a cell

services with
the QCI of 4 in
a cell

services with
the QCI of 5 in
a cell



services with
the QCI of 6 in
a cell

services with
the QCI of 7 in
a cell

services with
the QCI of 8 in
a cell

services with
the QCI of 9 in
a cell
1526728258 L.Traffic.DRB Number of BTS3900, L

DRBs in a cell BTS3900 LTE
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
L.Traffic.DRB.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None
L.Traffic.DRB Multi-mode: None

GSM: None
UMTS: None
1.10.2 Max number of DRBs in a Cell

Counters
1526730820 L.Traffic.DRB. Max number of BTS3900, L

Max DRBs in a cell BTS3900 LTE

Max.QCI.1 DRBs for BTS3900 LTE
services with
the QCI of 1 in
a cell

services with
the QCI of 2 in
a cell

services with
the QCI of 3 in
a cell



services with
the QCI of 4 in
a cell

services with
the QCI of 5 in
a cell

services with
the QCI of 6 in
a cell

services with
the QCI of 7 in
a cell

services with
the QCI of 8 in
a cell

services with
the QCI of 9 in
a cell
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
L.Traffic.DRB.Max Multi-mode: None

GSM: None
UMTS: None
L.Traffic.DRB.Max.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
1.11 Throughput and Data Volume Measurement

(Traffic.Thruput.Cell)
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
Description
1526726776 L.Thrp.bits.UL.QC Uplink traffic BTS3900:

I.1 volume for PDCP V100R008C00
PDUs of services BTS3900 LTE:
a cell V100R003C00


Description
1526726777 L.Thrp.Time.UL.Q Receive duration of BTS3900:

CI.1 uplink PDCP PDUs V100R008C00
for services with the BTS3900 LTE:

a cell V100R003C00


a cell V100R003C00


a cell V100R003C00


a cell V100R003C00



Description

a cell V100R003C00


a cell V100R003C00


a cell V100R003C00


a cell V100R003C00

1526726803 L.Thrp.bits.DL.QC Downlink traffic BTS3900:

SDUs of services BTS3900 LTE:
a cell V100R003C00


Description
1526726804 L.Thrp.Time.DL.Q Transmit duration of BTS3900:

CI.1 downlink PDCP V100R008C00
SDUs for services BTS3900 LTE:
a cell

a cell V100R003C00

a cell

a cell V100R003C00

a cell

a cell V100R003C00

a cell

a cell V100R003C00


Description

a cell

a cell V100R003C00

a cell

a cell V100R003C00

a cell

a cell V100R003C00

a cell

a cell V100R003C00


Description

a cell
1526727045 L.Thrp.bits.UL.QC Maximum uplink BTS3900:

I.1.Max traffic volume for V100R008C00
PDCP PDUs of BTS3900 LTE:








Description


1526727054 L.Thrp.bits.UL.Ma Maximum uplink BTS3900:

x traffic volume for V100R008C00
PDCP PDUs of all BTS3900 LTE:
V100R003C00
1526727055 L.Thrp.bits.DL.QC Maximum downlink BTS3900:

PDCP SDUs of BTS3900 LTE:






Description




1526727064 L.Thrp.bits.DL.Ma Maximum downlink BTS3900:

x traffic volume for V100R008C00
PDCP SDUs of all BTS3900 LTE:
V100R003C00
1526728178 L.Thrp.bits.DL.SR Total Bits of BTS3900:

B Transmitted V100R008C00
Signaling SDUs on BTS3900 LTE:
SRBs at the PDCP V100R003C00
Layer
1526728179 L.Thrp.bits.UL.SR Total Bits of BTS3900:

B Received Signaling V100R008C00
SDUs on SRBs at BTS3900 LTE:
the PDCP Layer V100R003C00
1526728232 L.Thrp.Time.Cell. Total duration of BTS3900:

DL downlink data V100R008C00
transmission in a BTS3900 LTE:
cell V100R003C00

UL uplink data V100R008C00
cell V100R003C00


Description
1526728234 L.E- Duration of data BTS3900:

RAB.SessionTime. transmission for V100R008C00
QCI1 services with the BTS3900 LTE:








1526728243 L.E- Total duration of UE BTS3900:

RAB.SessionTime. data transmission V100R008C00
UE time in a cell BTS3900 LTE:
V100R003C00


Description
1526728259 L.Thrp.bits.UL Total uplink traffic BTS3900:

volume for PDCP V100R008C00
PDUs in a cell BTS3900 LTE:
V100R003C00
1526728260 L.Thrp.Time.UL Total receive BTS3900:

duration of uplink V100R008C00
PDCP PDUs in a BTS3900 LTE:
cell V100R003C00
1526728261 L.Thrp.bits.DL Total downlink BTS3900:

traffic volume for V100R008C00
PDCP SDUs in a BTS3900 LTE:
cell V100R003C00
1526728262 L.Thrp.Time.DL Total transmit BTS3900:

duration of V100R008C00
downlink PDCP BTS3900 LTE:
SDUs in a cell V100R003C00
1526728475 L.Thrp.bits.UL.CE Total bits of uplink BTS3900:

U PDCP PDUs V100R008C00
received from CEUs BTS3900 LTE:
1526728476 L.Thrp.Time.UL.C Total duration in BTS3900:

EU which uplink user V100R008C00
data is received from BTS3900 LTE:
CEUs at the PDCP V100R008C00
layer in a cell
1526728477 L.Thrp.bits.DL.CE Total bits of BTS3900:

U downlink PDCP V100R008C00
SDUs sent to CEUs BTS3900 LTE:
1526728478 L.Thrp.Time.DL.C Total duration in BTS3900:

EU which downlink user V100R008C00
data is sent to CEUs BTS3900 LTE:
at the PDCP layer in V100R008C00
a cell
1526728564 L.Thrp.bits.DL.CA Total traffic volume BTS3900:

User for PDCP SDUs sent V100R008C00
to activated CA UEs BTS3900 LTE:
1526728565 L.Thrp.Time.DL.C Total duration for BTS3900:

AUser activated CA UEs V100R008C00
transmitting BTS3900 LTE:
downlink data at the V100R008C00
PDCP layer in a cell


Description

DL.HighPrecision downlink data V100R008C00
cell (with the V100R003C00
precision of 1 ms)

UL.HighPrecision uplink data V100R008C00
cell (with the V100R003C00
precision of 1 ms)
1526729005 L.Thrp.bits.DL.Las Downlink traffic BTS3900:

tTTI volume sent in the V100R008C00
last TTI for PDCP BTS3900 LTE:
SDUs before the V100R005C00
buffer is empty

tTTI.QCI.1 volume sent in the V100R008C00
SDUs of services V100R005C00
with the QCI 1
before the buffer is
empty

with the QCI 2
empty

with the QCI 3
empty

with the QCI 4
empty


Description

with the QCI 5
empty

with the QCI 6
empty

with the QCI 7
empty

with the QCI 8
empty

with the QCI 9
empty
1526729015 L.Thrp.Time.DL.R Data transmit BTS3900:

mvLastTTI duration except the V100R008C00
last TTI before the BTS3900 LTE:
downlink buffer is V100R005C00
empty


Description

mvLastTTI.QCI.1 duration except the V100R008C00
empty for services
with the QCI 1

empty for services
with the QCI 2

empty for services
with the QCI 3

empty for services
with the QCI 4

empty for services
with the QCI 5

empty for services
with the QCI 6

empty for services
with the QCI 7


Description

empty for services
with the QCI 8

empty for services
with the QCI 9
1526729049 L.Thrp.bits.UE.UL Traffic volume of BTS3900:

.LastTTI uplink PDCP PDUs V100R008C00
sent in the last TTI BTS3900 LTE:
before the UE buffer V100R003C00
is empty
1526729050 L.Thrp.Time.UE.U Uplink data transmit BTS3900:

L.RmvLastTTI duration except the V100R008C00
UE buffer is empty V100R003C00
1526729278 L.Thrp.bits.UL.UL Uplink throughput BTS3900:

ISch for PDCP PDUs of V100R008C01
uplink BTS3900 LTE:
independently- V100R008C01
scheduled UEs in an
SFN cell
1526729279 L.Thrp.bits.DL.DL Downlink BTS3900:

ISch throughput for V100R008C01
downlink V100R008C01
independently-
scheduled UEs in an
SFN cell
1526729415 L.Thrp.bits.UE.UL Uplink traffic BTS3900:

.SmallPkt volume of PDCP V100R008C00
PDUs scheduled for BTS3900 LTE:
small packets V100R008C00
1526729416 L.Thrp.Time.UE.U Uplink data BTS3900:

L.RmvSmallPkt transmission V100R008C00
duration except that BTS3900 LTE:
for small packets V100R008C00


Description
1526730560 L.Thrp.BitRate.DL Average rate of BTS3900:

.SRB transmitting V100R008C01
downlink signaling BTS3900 LTE:
data at the PDCP V100R008C01
layer in a cell
1526730561 L.Thrp.BitRate.UL Average rate of BTS3900:

.SRB receiving uplink V100R008C01
signaling data at the BTS3900 LTE:
PDCP layer in a cell V100R008C01
1526730836 L.Thrp.Time.UE.U Uplink data BTS3900:

L.RmvSpecificTTI transmission V100R009C00
duration except that BTS3900 LTE:
for specific small V100R009C00
packets transmitted
in the last TTI
1526730837 L.Thrp.bits.UE.UL Uplink traffic BTS3900:

.SpecificTTI volume at the PDCP V100R009C00
layer of specific BTS3900 LTE:
small packets V100R009C00
transmitted in the
last TTI
1526733012 L.Thrp.bits.DL. Downlink PDCP- BTS3900:

3CC.CAUser layer traffic volume V100R010C00
of CA UEs that are BTS3900 LTE:
in the 3CC CA state V100R010C00
and treat the local as
their PCell with two
SCells activated
1526733013 L.Thrp.bits.UL.CA Uplink PDCP-layer BTS3900:

User traffic volume of CA V100R010C00
UEs that are in the BTS3900 LTE:
uplink CA state and V100R010C00
treat the local as
their PCell with all
SCells activated
1526733184 L.Thrp.bits.DL.Rel Total PDCP-layer BTS3900:

axedBackhaulCAU traffic volume of V100R010C00
ser downlink data sent BTS3900 LTE:
to active relaxed- V100R010C00
backhaul-based
inter-eNodeB CA
UEs in a cell


Description
1526733185 L.Thrp.Time.DL.R Total duration for BTS3900:

elaxedBackhaulCA sending downlink V100R010C00
User data to active BTS3900 LTE:
downlink relaxed- V100R010C00
backhaul-based
inter-eNodeB CA
UEs at the PDCP
layer in a cell
1526735160 L.E- Total duration of UE BTS3900:

RAB.SessionTime. data transmission V100R008C00
UE.HighPrecision time with the BTS3900 LTE:
precision of 100 V100R008C00
milliseconds in a
cell
1526735161 L.E- Total duration of BTS3900:

RAB.SessionTime. transmission time V100R008C00
HighPrecision for services with all BTS3900 LTE:
the QCI with the V100R008C00
precision of 100
milliseconds in a
cell

HighPrecision.QCI services with the BTS3900 LTE:
1 QCI of 1 with the V100R008C00
precision of 100
milliseconds in a
cell

precision of 100
milliseconds in a
cell

precision of 100
milliseconds in a
cell


Description

precision of 100
milliseconds in a
cell

precision of 100
milliseconds in a
cell

precision of 100
milliseconds in a
cell

precision of 100
milliseconds in a
cell

precision of 100
milliseconds in a
cell

precision of 100
milliseconds in a
cell


Description
1526737745 L.Thrp.bits.UL.Fre Uplink PDCP-layer BTS3900:

qshare traffic volume of V100R010C10
CCUs in a cell using BTS3900 LTE:
the UMTS and LTE V100R010C10
shared spectrum
1526737746 L.Thrp.Time.UL.F Transmission BTS3900:

reqshare duration of uplink V100R010C10
PDCP-layer data for BTS3900 LTE:
CCUs in a cell using V100R010C10
the UMTS and LTE
shared spectrum
1526737807 L.Thrp.Time.DL.F Duration of BTS3900:

ddTddCAUser downlink PDCP- V100R010C10
layer data BTS3900 LTE:
transmission to CA V100R010C10
UEs that have all
SCells activated for
downlink FDD
+TDD CA in a cell
1526737808 L.Thrp.bits.DL.Fd Total traffic volume BTS3900:

dTddCAUser of downlink PDCP V100R010C10
SDUs to CA UEs BTS3900 LTE:
that have all SCells V100R010C10
activated for
downlink FDD
+TDD CA in a cell
1526737809 L.Thrp.Time.DL. Duration of BTS3900:

3CC.CAUser downlink PDCP- V100R010C10
UEs that have all
downlink 3CC CA
in a cell

3CC.FddTddCAUs downlink PDCP- V100R010C10
er layer data BTS3900 LTE:
UEs that have all
downlink FDD
+TDD 3CC CA in a
cell


Description
1526737811 L.Thrp.bits.DL. Total traffic volume BTS3900:

3CC.FddTddCAUs of downlink PDCP V100R010C10
er SDUs to CA UEs BTS3900 LTE:
activated for
downlink FDD
+TDD 3CC CA in a
cell

4CC.CAUser downlink PDCP- V100R010C10
UEs that have all
downlink 4CC CA
in a cell

4CC.CAUser of downlink PDCP V100R010C10
SDUs to CA UEs BTS3900 LTE:
activated for
downlink 4CC CA
in a cell

4CC.FddTddCAUs downlink PDCP- V100R010C10
er layer data BTS3900 LTE:
UEs that have all
downlink FDD
+TDD 4CC CA in a
cell

4CC.FddTddCAUs of downlink PDCP V100R010C10
er SDUs to CA UEs BTS3900 LTE:
activated for
downlink FDD
+TDD 4CC CA in a
cell
The Traffic.Thruput.Cell function subset contains counters related to throughput and data
transmission duration. Some of these counters can be categorized in terms of the QCI. The
following table shows the parent-child relationship of the counters.

L.Thrp.bits.UL L.Thrp.bits.UL.QCI.1
L.Thrp.bits.UL.QCI.2
L.Thrp.bits.UL L.Thrp.bits.UL.CEU
L.Thrp.Time.UL L.Thrp.Time.UL.QCI.1
L.Thrp.Time.UL.QCI.2
L.Thrp.Time.UL L.Thrp.Time.UL.CEU
L.Thrp.bits.DL L.Thrp.bits.DL.QCI.1
L.Thrp.bits.DL.QCI.2
L.Thrp.bits.DL L.Thrp.bits.DL.CEU

L.Thrp.bits.DL L.Thrp.bits.DL.CAUser
L.Thrp.Time.DL L.Thrp.Time.DL.QCI.1
L.Thrp.Time.DL.QCI.2
L.Thrp.Time.DL L.Thrp.Time.DL.CEU
L.Thrp.Time.DL L.Thrp.Time.DL.CAUser
L.Thrp.bits.DL.LastTTI L.Thrp.bits.DL.LastTTI.QCI.1
L.Thrp.bits.DL.LastTTI.QCI.2
L.Thrp.Time.DL.RmvLastTTI L.Thrp.Time.DL.RmvLastTTI.QCI.1
L.Thrp.Time.DL.RmvLastTTI.QCI.2

1.11.1 Maximum Uplink Traffic Volume for PDCP PDUs in a Cell

Counters
1526727045 L.Thrp.bits.UL. Maximum BTS3900, L

QCI.1.Max uplink traffic BTS3900 LTE
volume for
PDCP PDUs of
services with
the QCI of 1 in
a cell

volume for
PDCP PDUs of
services with
the QCI of 2 in
a cell

volume for
PDCP PDUs of
services with
the QCI of 3 in
a cell

volume for
PDCP PDUs of
services with
the QCI of 4 in
a cell

volume for
PDCP PDUs of
services with
the QCI of 5 in
a cell



volume for
PDCP PDUs of
services with
the QCI of 6 in
a cell

volume for
PDCP PDUs of
services with
the QCI of 7 in
a cell

volume for
PDCP PDUs of
services with
the QCI of 8 in
a cell

volume for
PDCP PDUs of
services with
the QCI of 9 in
a cell

Max uplink traffic BTS3900 LTE
volume for
PDCP PDUs of
all services
Description
The counters measure the maximum uplink traffic volume for received PDCP PDUs of
services with a specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The traffic volume of received uplink PDCP PDUs of services with a specific 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
L.Thrp.bits.UL.QCI.1.Max Multi-mode: None

GSM: None
UMTS: None
LBFD-002025 Basic Scheduling

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

L.Thrp.bits.UL.Max Multi-mode: None

GSM: None
UMTS: None
1.11.2 Maximum Downlink Traffic Volume for PDCP SDUs in a

Cell
Counters
1526727055 L.Thrp.bits.DL. Maximum BTS3900, L

QCI.1.Max downlink traffic BTS3900 LTE
volume for
PDCP SDUs of
services with
the QCI of 1 in
a cell

volume for
PDCP SDUs of
services with
the QCI of 2 in
a cell

volume for
PDCP SDUs of
services with
the QCI of 3 in
a cell



volume for
PDCP SDUs of
services with
the QCI of 4 in
a cell

volume for
PDCP SDUs of
services with
the QCI of 5 in
a cell

volume for
PDCP SDUs of
services with
the QCI of 6 in
a cell

volume for
PDCP SDUs of
services with
the QCI of 7 in
a cell

volume for
PDCP SDUs of
services with
the QCI of 8 in
a cell

volume for
PDCP SDUs of
services with
the QCI of 9 in
a cell



Max downlink traffic BTS3900 LTE
volume for
PDCP SDUs of
all services
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 traffic volume of downlink PDCP SDUs of services with a specific 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
L.Thrp.bits.DL.QCI.1.Max Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None
L.Thrp.bits.DL.Max Multi-mode: None

GSM: None
UMTS: None
1.11.3 Total Bits of Transmitted Signaling SDUs on SRBs at the

PDCP Layer in a Cell
Counters
1526728178 L.Thrp.bits.DL. Total Bits of BTS3900, L

SRB Transmitted BTS3900 LTE
Signaling SDUs
on SRBs at the
PDCP Layer
Description
The counter measures the total bits of transmitted signaling SDUs on SRBs at the PDCP layer
in a cell. As defined in 3GPP TS 36.323, PDCP is used for SRBs and DRBs mapped on

DCCH and DTCH type of logical channels. Therefore, SRBs at the PDCP layer include SRB1
and SRB2, but excludes SRB0. (SRB0 is carried on the CCCH.)
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
L.Thrp.bits.DL.SRB Multi-mode: None

GSM: None
UMTS: None
1.11.4 Total Bits of Received Signaling SDUs on SRBs at the

Counters
1526728179 L.Thrp.bits.UL. Total Bits of BTS3900, L

SRB Received BTS3900 LTE
Signaling SDUs
on SRBs at the
PDCP Layer
Description
The counter measures the total bits of received signaling SDUs on SRBs at the PDCP layer in
a cell. As defined in 3GPP TS 36.323, PDCP is used for SRBs and DRBs mapped on DCCH
and DTCH type of logical channels. Therefore, SRBs at the PDCP layer include SRB1 and
SRB2, but excludes SRB0. (SRB0 is carried on the CCCH.)

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
L.Thrp.bits.UL.SRB Multi-mode: None

GSM: None
UMTS: None
1.11.5 Total Duration of Uplink or Downlink Data Transmission

in a Cell
Counters
1526728232 L.Thrp.Time.Ce Total duration BTS3900, L

ll.DL of downlink BTS3900 LTE
data
transmission in
a cell

ll.UL of uplink data BTS3900 LTE
transmission in
a cell
Description
The counters measure the total duration of uplink data transmission and the total duration of
downlink data transmission in a cell with the precision of 1 second.

Measurement Points
The duration of uplink or downlink data transmission in a cell is sampled per second. If there
is uplink or downlink data transmission within a sampling period, the sampling result is 1s. 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 or L.Thrp.Time.Cell.DL counter.
Formula
None
Unit
s
Related Features
L.Thrp.Time.Cell.DL Multi-mode: None

GSM: None
UMTS: None
L.Thrp.Time.Cell.UL Multi-mode: None

GSM: None
UMTS: None

1.11.6 Duration of Data Transmission for Services with a Specific

QCI in a Cell
Counters
1526728234 L.E- Duration of BTS3900, L

RAB.SessionTi data BTS3900 LTE
me.QCI1 transmission for
services with
the QCI of 1 in
a cell

services with
the QCI of 2 in
a cell

services with
the QCI of 3 in
a cell

services with
the QCI of 4 in
a cell

services with
the QCI of 5 in
a cell

services with
the QCI of 6 in
a cell



services with
the QCI of 7 in
a cell

services with
the QCI of 8 in
a cell

services with
the QCI of 9 in
a cell
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

RAB.SessionTime.QCI1 GSM: None
UMTS: None

UMTS: None

UMTS: None

UMTS: None

UMTS: None


UMTS: None

UMTS: None

UMTS: None

UMTS: None

1.11.7 Total Duration of UE Data Transmission in a Cell
Counters
1526728243 L.E- Total duration BTS3900, L

RAB.SessionTi of UE data BTS3900 LTE
me.UE transmission
time in a cell
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
L.E-RAB.SessionTime.UE Multi-mode: None

GSM: None
UMTS: None

1.11.8 Uplink Traffic Volume for PDCP PDUs in a Cell

Counters
1526726776 L.Thrp.bits.UL. Uplink traffic BTS3900, L

QCI.1 volume for BTS3900 LTE
PDCP PDUs of
services with
the QCI of 1 in
a cell

PDCP PDUs of
services with
the QCI of 2 in
a cell

PDCP PDUs of
services with
the QCI of 3 in
a cell

PDCP PDUs of
services with
the QCI of 4 in
a cell

PDCP PDUs of
services with
the QCI of 5 in
a cell

PDCP PDUs of
services with
the QCI of 6 in
a cell



PDCP PDUs of
services with
the QCI of 7 in
a cell

PDCP PDUs of
services with
the QCI of 8 in
a cell

PDCP PDUs of
services with
the QCI of 9 in
a cell
1526728259 L.Thrp.bits.UL Total uplink BTS3900, L

traffic volume BTS3900 LTE
for PDCP
PDUs in a cell
Description
The counters measure the total traffic volume of received PDCP PDUs for services with a
specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The traffic volume of received uplink PDCP PDUs of services with a specific QCI ranging
from 1 to 9 is accumulated as the value of the corresponding counter.
Formula
None
Unit
bit

Related Features
L.Thrp.bits.UL.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
L.Thrp.bits.UL Multi-mode: None

GSM: None
UMTS: None

1.11.9 Receive Duration of Uplink PDCP PDUs in a Cell
Counters
1526726777 L.Thrp.Time.U Receive BTS3900, L

L.QCI.1 duration of BTS3900 LTE
uplink PDCP
PDUs for
services with
the QCI of 1 in
a cell

uplink PDCP
PDUs for
services with
the QCI of 2 in
a cell

uplink PDCP
PDUs for
services with
the QCI of 3 in
a cell

uplink PDCP
PDUs for
services with
the QCI of 4 in
a cell

uplink PDCP
PDUs for
services with
the QCI of 5 in
a cell

uplink PDCP
PDUs for
services with
the QCI of 6 in
a cell



uplink PDCP
PDUs for
services with
the QCI of 7 in
a cell

uplink PDCP
PDUs for
services with
the QCI of 8 in
a cell

uplink PDCP
PDUs for
services with
the QCI of 9 in
a cell
1526728260 L.Thrp.Time.U Total receive BTS3900, L

L duration of BTS3900 LTE
uplink PDCP
PDUs in a cell
Description
The counters measure the total uplink transmit duration of PDCP PDUs for all UEs in a cell.
Measurement Points
The receive duration of uplink PDCP PDUs for each service with a specific QCI is sampled
per millisecond in a cell. If there is uplink data to be transmitted within a millisecond, the
counter for the period of services with the corresponding QCI and the counter for the total
period are incremented by 1. The periods for each DRB of all UEs in the cell are accumulated.
Formula
None
Unit
ms

Related Features
L.Thrp.Time.UL.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
L.Thrp.Time.UL Multi-mode: None

GSM: None
UMTS: None

1.11.10 Downlink Traffic Volume for PDCP SDUs in a Cell
Counters
1526726803 L.Thrp.bits.DL. Downlink BTS3900, L

QCI.1 traffic volume BTS3900 LTE
for PDCP
SDUs of
services with
the QCI of 1 in
a cell

for PDCP
SDUs of
services with
the QCI of 2 in
a cell

for PDCP
SDUs of
services with
the QCI of 3 in
a cell

for PDCP
SDUs of
services with
the QCI of 4 in
a cell

for PDCP
SDUs of
services with
the QCI of 5 in
a cell

for PDCP
SDUs of
services with
the QCI of 6 in
a cell



for PDCP
SDUs of
services with
the QCI of 7 in
a cell

for PDCP
SDUs of
services with
the QCI of 8 in
a cell

for PDCP
SDUs of
services with
the QCI of 9 in
a cell
1526728261 L.Thrp.bits.DL Total downlink BTS3900, L

traffic volume BTS3900 LTE
for PDCP
SDUs in a cell
Description
The counters measure the total traffic volume of transmitted PDCP SDUs for services with a
Measurement Points
The traffic volume of transmitted PDCP SDUs of services with a specific QCI ranging from 1
to 9 is accumulated as the value of the corresponding counter.
Formula
None
Unit
bit

Related Features
L.Thrp.bits.DL.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
L.Thrp.bits.DL Multi-mode: None

GSM: None
UMTS: None

1.11.11 Transmit Duration of Downlink PDCP SDUs in a Cell
Counters
1526726804 L.Thrp.Time.D Transmit BTS3900, L

downlink PDCP
SDUs for
services with
the QCI of 1 in
a cell

downlink PDCP
SDUs for
services with
the QCI of 2 in
a cell

downlink PDCP
SDUs for
services with
the QCI of 3 in
a cell

downlink PDCP
SDUs for
services with
the QCI of 4 in
a cell

downlink PDCP
SDUs for
services with
the QCI of 5 in
a cell

downlink PDCP
SDUs for
services with
the QCI of 6 in
a cell



downlink PDCP
SDUs for
services with
the QCI of 7 in
a cell

downlink PDCP
SDUs for
services with
the QCI of 8 in
a cell

downlink PDCP
SDUs for
services with
the QCI of 9 in
a cell
1526728262 L.Thrp.Time.D Total transmit BTS3900, L

L duration of BTS3900 LTE
downlink PDCP
SDUs in a cell
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 is sampled per millisecond in a cell. If there is downlink data to be transmitted
within a millisecond, the counter for the period of services with the corresponding QCI and
the counter for the total period are incremented by 1. The periods for each DRB of all UEs in
the cell are accumulated.
Formula
None

Unit
ms
Related Features
L.Thrp.Time.DL.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

L.Thrp.Time.DL Multi-mode: None

GSM: None
UMTS: None
1.11.12 Total Bits of Uplink or Downlink User Data Received

from or Sent to ICIC CEUs at the PDCP Layer from CEUs in a Cell
Counters
1526728475 L.Thrp.bits.UL. Total bits of BTS3900, L

CEU uplink PDCP BTS3900 LTE
PDUs received
from CEUs in a
cell
1526728477 L.Thrp.bits.DL. Total bits of BTS3900, L

CEU downlink PDCP BTS3900 LTE
SDUs sent to
CEUs in a cell
Description
The counters measure the total bits of uplink user data received from cell edge users (ICIC
CEUs) and the total bits of downlink user data sent to ICIC CEUs at the PDCP layer in a cell.
Measurement Points
The number of bits of uplink PDCP PDUs received from ICIC CEUs and The number of bits
of downlink PDCP SDUs sent to CEUs in a cell within a measurement period is accumulated
as the value of the L.Thrp.bits.UL.CEU counter.
Formula
None
Unit
bit

Related Features
L.Thrp.bits.UL.CEU Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-00202202 Uplink Static Inter-Cell
TDLBFD-00202202 Interference Coordination
LOFD-00101402 Uplink Static Inter-Cell
Interference Coordination
LOFD-060201
Uplink Dynamic Inter-Cell
TDLOFD-060201 Interference Coordination
Adaptive Inter-Cell
Adaptive Inter-Cell
L.Thrp.bits.DL.CEU Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-00202201 Downlink Static Inter-Cell
LOFD-00101401 Downlink Static Inter-Cell
LOFD-060201
Downlink Dynamic Inter-
TDLOFD-060201 Cell Interference
Coordination
Adaptive Inter-Cell
Adaptive Inter-Cell

1.11.13 Total Duration in Which Uplink User Data Is Received

from or Downlink User Data Is Sent to ICIC CEUs at the PDCP
Layer in a Cell
Counters
1526728476 L.Thrp.Time.U Total duration BTS3900, L

L.CEU in which uplink BTS3900 LTE
user data is
received from
CEUs at the
PDCP layer in a
cell
1526728478 L.Thrp.Time.D Total duration BTS3900, L

L.CEU in which BTS3900 LTE
downlink user
data is sent to
CEUs at the
PDCP layer in a
cell
Description
The counters measure the total duration in which uplink user data is received from ICIC
CEUs and the total duration in which downlink user data is sent to ICIC CEUs at the PDCP
layer in a cell.
Measurement Points
The sum of the duration in which uplink user data is received from or downlink user data is
sent to ICIC CEUs at the PDCP layer in a cell within a measurement period is used as the
value of the L.Thrp.Time.UL.CEU or L.Thrp.Time.DL.CEU counter.
Formula
None
Unit
ms

Related Features
L.Thrp.Time.UL.CEU Multi-mode: None

GSM: None
UMTS: None
LOFD-060201
Adaptive Inter-Cell
Adaptive Inter-Cell
L.Thrp.Time.DL.CEU Multi-mode: None

GSM: None
UMTS: None
LOFD-060201
Coordination
Adaptive Inter-Cell
Adaptive Inter-Cell

1.11.14 Total Traffic Volume of Downlink PDCP SDUs

Transmitted to Activated CA UEs in a Cell
Counters
1526728564 L.Thrp.bits.DL. Total traffic BTS3900, L

CAUser volume for BTS3900 LTE
PDCP SDUs
sent to activated
CA UEs in a
cell
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 number of bits of downlink PDCP SDUs sent to activated CA UEs in a cell is
accumulated as the value of the L.Thrp.bits.DL.CAUser counter.
Formula
None
Unit
bit
Related Features
L.Thrp.bits.DL.CAUser Multi-mode: None

GSM: None
UMTS: None

1.11.15 Total Transmit Duration of Downlink PDCP SDUs

Transmitted to Activated CA UEs in a Cell
Counters

L.CAUser for activated BTS3900 LTE
CA UEs
transmitting
downlink data
at the PDCP
layer in a cell
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.
Formula
None
Unit
ms

Related Features
L.Thrp.Time.DL.CAUser Multi-mode: None

GSM: None
UMTS: None
1.11.16 Total Duration of Uplink or Downlink Data Transmission

in a Cell (with the Precision of 1 ms)
Counters

ll.DL.HighPreci of downlink BTS3900 LTE
sion data
transmission in
a cell (with the
precision of 1
ms)

ll.UL.HighPreci of uplink data BTS3900 LTE
sion transmission in
a cell (with the
precision of 1
ms)
Description
The counters measure the total duration of uplink data transmission and the total duration of
downlink data transmission in a cell with the precision of 1 millisecond.
Measurement Points
The duration of uplink or downlink data transmission in a cell is sampled per millisecond. If
there is uplink or downlink data transmission within a sampling period, the sampling result is
1 ms. 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 or L.Thrp.Time.Cell.DL.HighPrecision
counter.

Formula
None
Unit
ms
Related Features
L.Thrp.Time.Cell.DL.HighP Multi-mode: None

recision GSM: None
UMTS: None
L.Thrp.Time.Cell.UL.HighP Multi-mode: None

recision GSM: None
UMTS: None
1.11.17 Downlink traffic volume sent in the last TTI before the
buffer is empty
Counters

LastTTI traffic volume BTS3900 LTE
sent in the last
TTI for PDCP
SDUs before
the buffer is
empty



LastTTI.QCI.1 traffic volume BTS3900 LTE
sent in the last
TTI for PDCP
SDUs of
services with
the QCI 1
before the
buffer is empty

sent in the last
TTI for PDCP
SDUs of
services with
the QCI 2
before the
buffer is empty

sent in the last
TTI for PDCP
SDUs of
services with
the QCI 3
before the
buffer is empty

sent in the last
TTI for PDCP
SDUs of
services with
the QCI 4
before the
buffer is empty

sent in the last
TTI for PDCP
SDUs of
services with
the QCI 5
before the
buffer is empty



sent in the last
TTI for PDCP
SDUs of
services with
the QCI 6
before the
buffer is empty

sent in the last
TTI for PDCP
SDUs of
services with
the QCI 7
before the
buffer is empty

sent in the last
TTI for PDCP
SDUs of
services with
the QCI 8
before the
buffer is empty

sent in the last
TTI for PDCP
SDUs of
services with
the QCI 9
before the
buffer is empty
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 traffic volume of downlink PDCP SDUs sent in the last TTI for services with a specific
QCI ranging from 1 to 9 before the buffer is empty is accumulated in a cell as the value of the
corresponding counter.

Formula
None
Unit
bit
Related Features
L.Thrp.bits.DL.LastTTI Multi-mode: None

GSM: None
UMTS: None
L.Thrp.bits.DL.LastTTI.QC Multi-mode: None

I.1 GSM: None
UMTS: None

I.2 GSM: None
UMTS: None

I.3 GSM: None
UMTS: None


I.4 GSM: None
UMTS: None

I.5 GSM: None
UMTS: None

I.6 GSM: None
UMTS: None

I.7 GSM: None
UMTS: None

I.8 GSM: None
UMTS: None


I.9 GSM: None
UMTS: None
1.11.18 Data transmit duration except the last TTI before the
downlink buffer is empty
Counters
1526729015 L.Thrp.Time.D Data transmit BTS3900, L

L.RmvLastTTI duration except BTS3900 LTE
the last TTI
before the
downlink buffer
is empty

L.RmvLastTTI. duration except BTS3900 LTE
QCI.1 the last TTI
before the
downlink buffer
is empty for
services with
the QCI 1

QCI.2 the last TTI
before the
downlink buffer
is empty for
services with
the QCI 2



QCI.3 the last TTI
before the
downlink buffer
is empty for
services with
the QCI 3

QCI.4 the last TTI
before the
downlink buffer
is empty for
services with
the QCI 4

QCI.5 the last TTI
before the
downlink buffer
is empty for
services with
the QCI 5

QCI.6 the last TTI
before the
downlink buffer
is empty for
services with
the QCI 6

QCI.7 the last TTI
before the
downlink buffer
is empty for
services with
the QCI 7



QCI.8 the last TTI
before the
downlink buffer
is empty for
services with
the QCI 8

QCI.9 the last TTI
before the
downlink buffer
is empty for
services with
the QCI 9
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
Formula
None
Unit
ms

Related Features
L.Thrp.Time.DL.RmvLastT Multi-mode: None

TI GSM: None
UMTS: None

TI.QCI.1 GSM: None
UMTS: None

TI.QCI.2 GSM: None
UMTS: None

TI.QCI.3 GSM: None
UMTS: None

TI.QCI.4 GSM: None
UMTS: None


TI.QCI.5 GSM: None
UMTS: None

TI.QCI.6 GSM: None
UMTS: None

TI.QCI.7 GSM: None
UMTS: None

TI.QCI.8 GSM: None
UMTS: None

TI.QCI.9 GSM: None
UMTS: None

1.11.19 Traffic Volume of Uplink PDCP SDUs Sent in the Last

TTI Before the UE Buffer is Empty
Counters
1526729049 L.Thrp.bits.UE. Traffic volume BTS3900, L

UL.LastTTI of uplink PDCP BTS3900 LTE
PDUs sent in
the last TTI
before the UE
buffer is empty
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 traffic volume of uplink PDCP PDUs sent in the last TTI before the UE buffer is empty is
measured in a cell.
Formula
None
Unit
bit
Related Features
L.Thrp.bits.UE.UL.LastTTI Multi-mode: None

GSM: None
UMTS: None

1.11.20 Uplink Data Transmit Duration Except the Last TTI Before
the UE Buffer is Empty
Counters
1526729050 L.Thrp.Time.U Uplink data BTS3900, L

E.UL.RmvLast transmit BTS3900 LTE
TTI duration except
the last TTI
before the UE
buffer is empty
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
L.Thrp.Time.UE.UL.RmvLa Multi-mode: None

stTTI GSM: None
UMTS: None

1.11.21 Uplink PDCP throughput in an SFN cell

Counters
1526729278 L.Thrp.bits.UL. Uplink BTS3900, L

ULISch throughput for BTS3900 LTE
PDCP PDUs of
uplink
independently-
scheduled UEs
in an SFN cell
Description
These counters measure the throughput of received uplink PDCP PDUs for services in an
SFN cell.
Measurement Points
In an SFN cell, the eNodeB measures the uplink PDCP PDU throughput of an independently-
scheduled UE in the uplink.
Formula
None
Unit
bit
Related Features
L.Thrp.bits.UL.ULISch Multi-mode: None

GSM: None
UMTS: None
LTE: TDLBFD-002025 Basic Scheduling
TDLOFD-001075 SFN

1.11.22 Downlink PDCP throughput in an SFN cell

Counters

DLISch throughput for BTS3900 LTE
PDCP SDUs of
downlink
independently-
scheduled UEs
in an SFN cell
Description
These counters measure the throughput of received downlink PDCP SDUs for services in an
SFN cell.
Measurement Points
In an SFN cell, the eNodeB measures the downlink PDCP SDU throughput of an
independently-scheduled UE in the downlink.
Formula
None
Unit
bit
Related Features
L.Thrp.bits.DL.DLISch Multi-mode: None

GSM: None
UMTS: None
TDLOFD-001075 SFN

1.11.23 Uplink Traffic Volume of PDCP PDUs Scheduled for

Small Packets
Counters
1526729415 L.Thrp.bits.UE. Uplink traffic BTS3900, L

UL.SmallPkt volume of BTS3900 LTE
PDCP PDUs
scheduled for
small packets
Description
The counter measures the traffic volume of PDCP PDUs scheduled for small packets in a cell.
Measurement Points
An uplink packet that 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 uplink PDCP PDUs 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
L.Thrp.bits.UE.UL.SmallPk Multi-mode: None

t GSM: None
UMTS: None

1.11.24 Uplink Data Transmission Duration Except that for Small

Packets
Counters

E.UL.RmvSmal transmission BTS3900 LTE
lPkt duration except
that for small
packets
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. The duration of transmissions and the
scheduling waiting time are included in the sampling result. 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
L.Thrp.Time.UE.UL.RmvS Multi-mode: None

mallPkt GSM: None
UMTS: None

1.11.25 Average Rate of Transmitting Downlink Signaling Data at

the PDCP Layer in a Cell
Counters
1526730560 L.Thrp.BitRate. Average rate of BTS3900, L

DL.SRB transmitting BTS3900 LTE
downlink
signaling data
at the PDCP
layer in a cell
Description
The counter measures the average rate of successfully transmitting downlink signaling data at
the PDCP layer in a cell.
Measurement Points
The average rate of transmitting downlink SRBs at the PDCP layer is sampled per second in a
cell. At the end of a measurement period, the average of the non-zero sampling results is used
as the value of the L.Thrp.BitRate.DL.SRB counter.
Formula
None
Unit
bit/s
Related Features
L.Thrp.BitRate.DL.SRB Multi-mode: None

GSM: None
UMTS: None

1.11.26 Average Rate of Receiving Uplink Signaling Data at the

Counters
1526730561 L.Thrp.BitRate. Average rate of BTS3900, L

UL.SRB receiving uplink BTS3900 LTE
signaling data
at the PDCP
layer in a cell
Description
The counter measures the average rate of successfully receiving uplink signaling data at the
PDCP layer in a cell.
Measurement Points
The average rate of receiving uplink SRBs at the PDCP layer is sampled per second in a cell.
At the end of a measurement period, the average of the non-zero sampling results is used as
the value of the L.Thrp.BitRate.UL.SRB counter.
Formula
None
Unit
bit/s
Related Features
L.Thrp.BitRate.UL.SRB Multi-mode: None

GSM: None
UMTS: None

1.11.27 Uplink Data Transmission Duration Except that for

Specific Small Packets Transmitted in the Last TTI
Counters

E.UL.RmvSpec transmission BTS3900 LTE
ificTTI duration except
that for specific
small packets
transmitted in
the last TTI
Description
The counter measures the uplink data transmission duration except that for specific small
packets transmitted in the last TTI. If the valid DRB data amount of a data packet received by
the cell after the eNodeB clears the uplink buffer for a UE is less than SpecificPktSizeThd
during a scheduling procedure, such a data packet is a specific small data packet transmitted
in the last TTI.
Measurement Points
After a UE is scheduled in the uplink in a cell, the data amount in the uplink buffer of the UE
becomes zero. This means that in this scheduling procedure, the air interface resources can
meet the actual uplink data transmission requirement for the UE. This scheduling procedure is
regarded as a scheduling procedure in the last TTI in consecutive scheduling procedures. In
addition, if the valid DRB data amount of the uplink data packets received by the cell in this
scheduling procedure is less than SpecificPktSizeThd, these uplink data packets are regarded
as specific small packets transmitted in the last TTI. The
L.Thrp.Time.UE.UL.RmvSpecificTTI counter is incremented by 1 each time the cell receives
an uplink data packet that is not a specific small packet transmitted in the last TTI.
Formula
None
Unit
ms

Related Features
L.Thrp.Time.UE.UL.RmvSp Multi-mode: None

ecificTTI GSM: None
UMTS: None
1.11.28 Uplink Traffic Volume at the PDCP Layer of Specific

Small Packets Transmitted in the Last TTI
Counters
1526730837 L.Thrp.bits.UE. Uplink traffic BTS3900, L

UL.SpecificTTI volume at the BTS3900 LTE
PDCP layer of
specific small
packets
transmitted in
the last TTI
Description
The counter measures the uplink traffic volume at the PDCP layer of specific small packets
transmitted in the last TTI. If the valid DRB data amount of a data packet received by the cell
after the eNodeB clears the uplink buffer for a UE is less than SpecificPktSizeThd during a
scheduling procedure, such a data packet is a specific small data packet transmitted in the last
TTI.
Measurement Points
After a UE is scheduled in the uplink in a cell, the data amount in the uplink buffer of the UE
becomes zero. This means that in this scheduling procedure, the air interface resources can
meet the actual uplink data transmission requirement for the UE. This scheduling procedure is
regarded as a scheduling procedure in the last TTI in consecutive scheduling procedures. In
addition, if the valid DRB data amount of the uplink data packets received by the cell in this
scheduling procedure is less than SpecificPktSizeThd, these uplink data packets are regarded
as specific small packets transmitted in the last TTI. When the cell receives an uplink data
packet that is a specific small packet transmitted in the last TTI, its data amount at the PDCP
layer is accumulated as the L.Thrp.bits.UE.UL.SpecificTTI counter value.
Formula
None

Unit
bit
Related Features
L.Thrp.bits.UE.UL.Specific Multi-mode: None

TTI GSM: None
UMTS: None
1.11.29 Downlink PDCP-layer Traffic Volume of CA UEs that Are

in the 3CC CA State and Treat the Local as Their PCell with Two
SCell Activated
Counters

3CC.CAUser PDCP-layer BTS3900 LTE
traffic volume
of CA UEs that
are in the 3CC
CA state and
treat the local as
their PCell with
two SCells
activated
Description
The counter measures the downlink PDCP-layer traffic volume of CA UEs that in the 3CC
CA state, treat the local cell as their PCell, and have all SCells activated.
Measurement Points
For CA UEs that are in the 3CC CA state and treat the local cell as their PCell, the uplink
PCDP-layer traffic volume sent to these UEs that have their SCells activated is accumulated
as the L.Thrp.bits.DL.3CC.CAUser counter value.
Formula
None

Unit
bit
Related Features
L.Thrp.bits.DL. Multi-mode: None

3CC.CAUser GSM: None
UMTS: None
LTE: LAOFD-080208 Carrier Aggregation for
TDLAOFD-081405 Downlink 3CC in 60MHz
Carrier Aggregation for
Downlink 3CC
1.11.30 Uplink PDCP-layer Traffic Volume of CA UEs that Treat

the Local as Their PCell with All SCells Activated
Counters
1526733013 L.Thrp.bits.UL. Uplink PDCP- BTS3900, L

CAUser layer traffic BTS3900 LTE
volume of CA
UEs that are in
the uplink CA
state and treat
the local as
their PCell with
all SCells
activated
Description
The counter measures the uplink PDCP-layer traffic volume of CA UEs that treat the local
cell as their PCell and have all SCells activated.
Measurement Points
The eNodeB measures the uplink PDCP-layer traffic volume of sent by CA UEs that treat the
local cell as their PCell and have their SCells activated. The payloads of the successfully
transmitted data are accumulated as the L.Thrp.bits.UL.CAUser counter value.

Formula
None
Unit
bit
Related Features
L.Thrp.bits.UL.CAUser Multi-mode: None

GSM: None
UMTS: None
TDLAOFD-081407 Uplink 2CC
Uplink 2CC
1.11.31 Total Downlink Traffic Volume of Downlink Relaxed-

Backhaul-based Inter-eNodeB CA UEs in a Cell
Counters
1526733184 L.Thrp.bits.DL. Total PDCP- BTS3900, L

RelaxedBackha layer traffic BTS3900 LTE
ulCAUser volume of
downlink data
sent to active
relaxed-
backhaul-based
inter-eNodeB
CA UEs in a
cell
Description
The counter measures the traffic volume of downlink PDCP SDUs of DRB services sent to
active relaxed-backhaul-based CA UEs that treat the local cell as their PCell.

Measurement Points
The payload of successfully transmitted PDCP-layer downlink data sent to active relaxed-
backhaul-based inter-eNodeB CA UEs is accumulated in a cell and used as the
L.Thrp.bits.DL.RelaxedBackhaulCAUser counter value.
Formula
None
Unit
bit
Related Features
L.Thrp.bits.DL.RelaxedBac Multi-mode: None

khaulCAUser GSM: None
UMTS: None
LTE: LAOFD-080201 Inter-eNodeB CA based on
TDLAOFD-081402 Relaxed backhaul
Inter-eNodeB CA based on
Relaxed Backhaul
1.11.32 Total Duration for Sending Downlink Data to Active

Downlink Relaxed-Backhaul-based Inter-eNodeB CA UEs at the
Counters

L.RelaxedBack for sending BTS3900 LTE
haulCAUser downlink data
to active
downlink
relaxed-
backhaul-based
inter-eNodeB
CA UEs at the
PDCP layer in a
cell

Description
The counter measures the transmission duration of DRB services at the PDCP layer sent to
active relaxed-backhaul-based inter-eNodeB CA UEs that treat the local cell as their PCell in
a cell.
Measurement Points
Every millisecond, the eNodeB detects whether an active relaxed-backhaul-based inter-
eNodeB CA UE sends data on the DRBs in the downlink in a cell. If yes, the
L.Thrp.Time.DL.RelaxedBackhaulCAUser counter is incremented by 1ms. The DRB service
transmission duration of all active relaxed-backhaul-based inter-eNodeB CA UEs is
accumulated and used as the counter value. 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
L.Thrp.Time.DL.RelaxedBa Multi-mode: None

ckhaulCAUser GSM: None
UMTS: None
Relaxed Backhaul

1.11.33 Total Duration of UE Data Transmission with the

precision of 100 milliseconds in a Cell
Counters

RAB.SessionTi of UE data BTS3900 LTE
me.UE.HighPre transmission
cision time with the
precision of 100
milliseconds in
a cell
Description
The counter measures the total duration of UE data transmission with the precision of 100
milliseconds in a cell.
Measurement Points
The duration of UE data transmission in a cell is sampled per 100 milliseconds. If there is
uplink or downlink data transmission for a UE within the 100 milliseconds, the sampling
result is 100 milliseconds. At the end of a measurement period, the sum of these sampling
results for all UEs is used as the value of the counter.
Formula
None
Unit
100 ms
Related Features

RAB.SessionTime.UE.High GSM: None
Precision
UMTS: None

1.11.34 Total duration of transmission time for services with all

the QCI with the precision of 100 milliseconds in a cell
Counters

RAB.SessionTi of transmission BTS3900 LTE
me.HighPrecisi time for
on services with all
the QCI with
the precision of
100
milliseconds in
a cell

me.HighPrecisi transmission for
on.QCI1 services with
the QCI of 1
with the
precision of 100
milliseconds in
a cell

the QCI of 2
with the
precision of 100
milliseconds in
a cell

the QCI of 3
with the
precision of 100
milliseconds in
a cell



the QCI of 4
with the
precision of 100
milliseconds in
a cell

the QCI of 5
with the
precision of 100
milliseconds in
a cell

the QCI of 6
with the
precision of 100
milliseconds in
a cell

the QCI of 7
with the
precision of 100
milliseconds in
a cell

the QCI of 8
with the
precision of 100
milliseconds in
a cell



the QCI of 9
with the
precision of 100
milliseconds in
a cell
Description
The counter measures the duration of data transmission for services with all the QCI with the
precision of 100 milliseconds in a cell.
Measurement Points
The duration of data transmission for each service with all the QCI in a cell is sampled per
100 milliseconds. If there is uplink or downlink data transmission within this 100
milliseconds, the sampling result is 100 milliseconds.At the end of a measurement period, the
sum of these sampling results for all the QCI of all UEs is used as the value of the counter.
Formula
None
Unit
100 ms
Related Features

RAB.SessionTime.HighPrec GSM: None
ision
UMTS: None


ision.QCI1
UMTS: None

ision.QCI2
UMTS: None

ision.QCI3
UMTS: None

ision.QCI4
UMTS: None

ision.QCI5
UMTS: None


ision.QCI6
UMTS: None

ision.QCI7
UMTS: None

ision.QCI8
UMTS: None

ision.QCI9
UMTS: None

1.11.35 Uplink PDCP-layer Traffic Volume of CCUs in a Cell

Using the UMTS and LTE Shared Spectrum
Counters

Freqshare layer traffic BTS3900 LTE
volume of
CCUs in a cell
using the
UMTS and LTE
shared spectrum
Description
The counter measures the uplink PDCP-layer traffic volume of CCUs in a cell using the
UMTS and LTE shared spectrum.
Measurement Points
The number of bits of uplink PDCP-layer data for cell center users (CCUs) is accumulated in
a cell using the UMTS and LTE shared spectrum within a measurement period. At the end of
a measurement period, the accumulated value is used as the value of the
L.Thrp.bits.UL.Freqshare counter.
Formula
None
Unit
bit
Related Features
L.Thrp.bits.UL.Freqshare Multi-mode: MRFD-101221 UL Refarming Zero

GSM: None Bufferzone
UMTS: None
LTE: None

1.11.36 Transmission Duration of Uplink PDCP-layer Data for

CCUs in a Cell Using the UMTS and LTE Shared Spectrum
Counters
1526737746 L.Thrp.Time.U Transmission BTS3900, L

L.Freqshare duration of BTS3900 LTE
uplink PDCP-
layer data for
CCUs in a cell
using the
UMTS and LTE
shared spectrum
Description
The counter measures the transmission duration of uplink PDCP-layer data for CCUs in a cell
using the UMTS and LTE shared spectrum.
Measurement Points
The transmission duration of uplink PDCP-layer data for cell center users (CCUs) is
accumulated in a cell using the UMTS and LTE shared spectrum within a measurement
period. At the end of a measurement period, the accumulated value is used as the value of the
L.Thrp.Time.UL.Freqshare counter.
Formula
None
Unit
ms
Related Features
L.Thrp.Time.UL.Freqshare Multi-mode: MRFD-101221 UL Refarming Zero

GSM: None Bufferzone
UMTS: None
LTE: None

1.11.37 Duration of Downlink PDCP-Layer Data Transmission to

CA UEs That Have All SCells Activated for Downlink FDD+TDD
CA in a Cell.
Counters
1526737807 L.Thrp.Time.D Duration of BTS3900, L

L.FddTddCAUs downlink BTS3900 LTE
er PDCP-layer
data
transmission to
CA UEs that
have all SCells
activated for
downlink FDD
+TDD CA in a
cell
Description
The counter measures the duration of downlink PDCP-layer data transmission to CA UEs that
treat the local cell as their PCell and have all SCells activated for downlink FDD+TDD CA.
Measurement Points
Every millisecond, the eNodeB checks whether there is data transmitted on downlink DRBs
to CA UEs that have all SCells activated for downlink FDD+TDD state in a cell. If the
eNodeB determines that there is data transmitted to such CA UEs, the data transmission
duration is incremented by 1 ms. The transmission duration of DRB services for all such CA
UEs is accumulated and taken as the value of the L.Thrp.Time.DL.FddTddCAUser counter.
The internal timer of the eNodeB has a deviation of one period, and therefore the value of this
counter has a deviation to the actual duration.
Formula
None
Unit
ms

Related Features
L.Thrp.Time.DL.FddTddCA Multi-mode: MRFD-101231 FDD and TDD Carrier

User MRFD-101222 Aggregation(TDD)
GSM: None FDD+TDD Carrier
Aggregation(LTE FDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
LAOFD-070201 Aggregation for Downlink
LAOFD-070202 2CC in 20MHz
LAOFD-080201 Inter-Band Carrier
2CC in 20MHz
LAOFD-080208
Flexible CA from Multiple
LAOFD-081237 Carriers
TDLAOFD-00100111 Inter-eNodeB CA based on
TDLAOFD-001002 Coordinated BBU
TDLAOFD-081404 Carrier Aggregation for
Downlink 3CC in 40MHz
Carrier Aggregation with
DL 4x4 MIMO
Intra-band Carrier
Aggregation for Downlink
2CC in 30MHz
Support for UE Category 6
Carriers
Downlink 4CC

1.11.38 Total Traffic Volume of Downlink PDCP SDUs to CA UEs

That Have All SCells Activated for Downlink FDD+TDD CA.
Counters

FddTddCAUser volume of BTS3900 LTE
downlink PDCP
SDUs to CA
UEs that have
all SCells
activated for
downlink FDD
+TDD CA in a
cell
Description
The counter measures the traffic volume of downlink PDCP SDUs of DRB services sent to
CA UEs that treat the local cell as their PCell and have all SCells activated for downlink FDD
+TDD CA.
Measurement Points
The traffic volume of successfully transmitted PDCP SDUs to CA UEs that have all SCells
activated for downlink FDD+TDD CA in a cell is accumulated and taken as the value of the
L.Thrp.bits.DL.FddTddCAUser counter.
Formula
None
Unit
bit

Related Features
L.Thrp.bits.DL.FddTddCA Multi-mode: MRFD-101231 FDD and TDD Carrier

User MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC


CA UEs That Have All SCells Activated for Downlink 3CC CA in
a Cell
Counters

L.3CC.CAUser downlink BTS3900 LTE
PDCP-layer
data
transmission to
CA UEs that
have all SCells
activated for
downlink 3CC
CA in a cell
Description
treat the local cell as their PCell and have all SCells activated for downlink 3CC CA.
Measurement Points
to CA UEs that have all SCells activated for downlink 3CC CA in a cell. If the eNodeB
determines that there is data transmitted to such CA UEs, the data transmission duration is
incremented by 1 ms. The transmission duration of DRB services for all such CA UEs is
accumulated and taken as the value of the L.Thrp.Time.DL.3CC.CAUser counter.
Formula
None
Unit
ms

Related Features
L.Thrp.Time.DL. Multi-mode: MRFD-101231 FDD and TDD Carrier

3CC.CAUser MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC

1.11.40 Duration of downlink PDCP-Layer Data Transmission to

3CC CA in a Cell
Counters

L. downlink BTS3900 LTE
3CC.FddTddC PDCP-layer
AUser data
transmission to
CA UEs that
have all SCells
activated for
downlink FDD
+TDD 3CC CA
in a cell
Description
treat the local cell as their PCell and have all SCells activated for downlink FDD+TDD 3CC
CA.
Measurement Points
to CA UEs that have all SCells activated for downlink FDD+TDD 3CC CA in a cell. If the
UEs is accumulated and taken as the value of the L.Thrp.Time.DL.3CC.FddTddCAUser
counter.
Formula
None
Unit
ms

Related Features

3CC.FddTddCAUser MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC


That Have All SCells Activated for Downlink FDD+TDD 3CC
CA in a Cell
Counters

3CC.FddTddC volume of BTS3900 LTE
AUser downlink PDCP
SDUs to CA
UEs that have
all SCells
activated for
downlink FDD
+TDD 3CC CA
in a cell
Description
The counter measures the traffic volume of downlink PDCP SDUs sent to CA UEs that treat
the local cell as their PCell and have all SCells activated for downlink FDD+TDD 3CC CA.
Measurement Points
activated for downlink FDD+TDD 3CC CA in a cell is accumulated and taken as the value of
the L.Thrp.bits.DL.3CC.FddTddCAUser counter.
Formula
None
Unit
bit

Related Features
L.Thrp.bits.DL. Multi-mode: MRFD-101231 FDD and TDD Carrier

UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC


CA UEs That Have All SCells Activated for downlink 4CC CA in
a Cell
Counters

L.4CC.CAUser downlink BTS3900 LTE
PDCP-layer
data
transmission to
CA UEs that
have all SCells
activated for
downlink 4CC
CA in a cell
Description
treat the local cell as their PCell and have all SCells activated for downlink 4CC CA.
Measurement Points
to CA UEs that have all SCells activated for downlink 4CC CA in a cell. If the eNodeB
determines that there is data transmitted to such CA UEs, the data transmission duration is
incremented by 1 ms. The transmission duration of DRB services for all such CA UEs is
accumulated and taken as the value of the L.Thrp.Time.DL.4CC.CAUser counter.
Formula
None
Unit
ms

Related Features

UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC


That Have All SCells Activated for Downlink 4CC CA in a Cell
Counters

4CC.CAUser volume of BTS3900 LTE
downlink PDCP
SDUs to CA
UEs that have
all SCells
activated for
downlink 4CC
CA in a cell
Description
the local cell as their PCell and have all SCells activated for downlink 4CC CA.
Measurement Points
activated for downlink 4CC CA in a cell is accumulated and taken as the value of the
L.Thrp.bits.DL.4CC.CAUser counter.
Formula
None
Unit
bit

Related Features

UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC

1.11.44 Duration of downlink PDCP-Layer Data Transmission to

4CC CA in a Cell
Counters

L. downlink BTS3900 LTE
4CC.FddTddC PDCP-layer
AUser data
transmission to
CA UEs that
have all SCells
activated for
downlink FDD
+TDD 4CC CA
in a cell
Description
treat the local cell as their PCell and have all SCells activated for downlink FDD+TDD 4CC
CA.
Measurement Points
to CA UEs that have all SCells activated for downlink FDD+TDD 4CC CA in a cell. If the
UEs is accumulated and taken as the value of the L.Thrp.Time.DL.4CC.FddTddCAUser
counter.
Formula
None
Unit
ms

Related Features

UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC


That Have All SCells Activated for Downlink FDD+TDD 4CC
CA in a Cell
Counters

4CC.FddTddC volume of BTS3900 LTE
AUser downlink PDCP
SDUs to CA
UEs that have
all SCells
activated for
downlink FDD
+TDD 4CC CA
in a cell
Description
the local cell as their PCell and have all SCells activated for downlink FDD+TDD 4CC CA.
Measurement Points
activated for downlink FDD+TDD 4CC CA in a cell is accumulated and taken as the value of
the L.Thrp.bits.DL.4CC.FddTddCAUser counter.
Formula
None
Unit
bit

Related Features

UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC

1.12 Throughput and Data Volume Measurement 1

(Traffic.Thruput.Cell.1)
Overview
The Traffic.Thruput.Cell.1 function subset measures the uplink or downlink throughput of
services with a specific QCI in a cell and the duration of data transmission.
Counters
Description
1526730563 L.Thrp.bits.UL.PD Uplink traffic BTS3900:

CP.SDU.QCI.1 volume for PDCP V100R009C00
a cell

a cell

a cell

a cell

a cell

a cell


Description

a cell

a cell

a cell
1526730572 L.Thrp.bits.UL.PD Total uplink traffic BTS3900:

CP.SDU volume for PDCP V100R009C00
SDUs in a cell BTS3900 LTE:
V100R009C00
1526730573 L.Thrp.bits.DL.PD Downlink traffic BTS3900:

CP.PDU.QCI.1 volume for PDCP V100R009C00
a cell

a cell

a cell

a cell

a cell


Description

a cell

a cell

a cell

a cell
1526730582 L.Thrp.bits.DL.PD Total downlink BTS3900:

CP.PDU traffic volume of V100R009C00
PDCP PDUs in a BTS3900 LTE:
cell V100R009C00
1526734141 L.Thrp.bits.DL.Ph Total downlink BTS3900:

y traffic volume at the V100R009C00
physical layer in a BTS3900 LTE:
cell V100R009C00
1526734142 L.Thrp.bits.UL.Ph Total uplink traffic BTS3900:

y volume at the V100R009C00
physical layer in a BTS3900 LTE:
cell V100R009C00
1526734143 L.Thrp.bits.DL.Ph Maximum downlink BTS3900:

y.Max traffic volume of all V100R009C00
services at the BTS3900 LTE:
physical layer V100R009C00
1526734144 L.Thrp.bits.UL.Ph Maximum uplink BTS3900:

y.Max traffic volume of all V100R009C00
services at the BTS3900 LTE:
physical layer V100R009C00


Description
1526734145 L.Thrp.Time.Activ Total duration of BTS3900:

e.Cell.UL data storage in the V100R010C00
uplink buffer BTS3900 LTE:
V100R010C00
1526734146 L.Thrp.Time.Activ Total duration of BTS3900:

e.Cell.DL data storage in the V100R010C00
downlink buffer BTS3900 LTE:
V100R010C00
1526735568 L.Thrp.bits.DL.PD Total PDCP-layer BTS3900:

CP.Send traffic volume of to- V100R010C00
be-transmitted BTS3900 LTE:
downlink data in a V100R010C00
cell
1526735569 L.Thrp.bits.DL.PD Total PDCP-layer BTS3900:

CP.Discard traffic volume of V100R010C00
discarded to-be- BTS3900 LTE:
transmitted V100R010C00
downlink data in a
cell
1526735570 L.Thrp.bits.DL.RL Total RLC-layer BTS3900:

C.Send traffic volume of V100R010C00
downlink data in a BTS3900 LTE:
cell V100R010C00
1526735571 L.Thrp.bits.UL.RL Total RLC-layer BTS3900:

C.Send traffic volume of V100R010C00
uplink data in a cell BTS3900 LTE:
V100R010C00
1526735572 L.Thrp.bits.UL.PD Total PDCP-layer BTS3900:

CP.Discard traffic volume of V100R010C00
discarded uplink BTS3900 LTE:
data in a cell V100R010C00
1526735573 L.Thrp.bits.UL.PD Total PDCP-layer BTS3900:

CP.Send traffic volume of V100R010C00
uplink data in a cell BTS3900 LTE:
V100R010C00
1526737754 L.Thrp.bits.UL.Bo Uplink PDCP-layer BTS3900:

rderUE traffic volume V100R010C10
received for CEUs BTS3900 LTE:
1526737755 L.Thrp.bits.DL.Bo Downlink PDCP- BTS3900:

rderUE layer traffic volume V100R010C10
sent for CEUs in a BTS3900 LTE:
cell V100R010C10


Description
1526737756 L.Thrp.bits.UL.Sm PDCP-layer traffic BTS3900:

allPkt.BorderUE volume scheduled V100R010C10
for uplink small BTS3900 LTE:
packets for CEUs in V100R010C10
a cell
1526737757 L.Thrp.Time.UL.R Transmission BTS3900:

mvSmallPkt.Borde duration of uplink V100R010C10
rUE data except small BTS3900 LTE:
packets for CEUs in V100R010C10
a cell
1526737758 L.Thrp.bits.DL.Las Downlink PDCP- BTS3900:

tTTI.BorderUE layer traffic volume V100R010C10
sent in the last TTI BTS3900 LTE:
for CEUs before the V100R010C10
buffer is empty in a
cell
1526737759 L.Thrp.Time.DL.R Data transmission BTS3900:

mvLastTTI.Border duration for CEUs V100R010C10
UE except the last TTI BTS3900 LTE:
before the downlink V100R010C10
buffer is empty
The Traffic.Thruput.Cell.1 function subset contains counters related to throughput and data
transmission duration. Some of these counters can be categorized in terms of the QCI.
L.Thrp.bits.UL.PDCP.SDU L.Thrp.bits.UL.PDCP.SDU.QCI.1
L.Thrp.bits.UL.PDCP.SDU.QCI.2
L.Thrp.bits.DL.PDCP.PDU L.Thrp.bits.DL.PDCP.PDU.QCI.1

L.Thrp.bits.DL.PDCP.PDU.QCI.2
1.12.1 Uplink Traffic Volume at the PDCP layer

Counters

PDCP.SDU.QC volume for BTS3900 LTE
I.1 PDCP SDUs of
services with
the QCI of 1 in
a cell

I.2 PDCP SDUs of
services with
the QCI of 2 in
a cell

I.3 PDCP SDUs of
services with
the QCI of 3 in
a cell

I.4 PDCP SDUs of
services with
the QCI of 4 in
a cell



I.5 PDCP SDUs of
services with
the QCI of 5 in
a cell

I.6 PDCP SDUs of
services with
the QCI of 6 in
a cell

I.7 PDCP SDUs of
services with
the QCI of 7 in
a cell

I.8 PDCP SDUs of
services with
the QCI of 8 in
a cell

I.9 PDCP SDUs of
services with
the QCI of 9 in
a cell
1526730572 L.Thrp.bits.UL. Total uplink BTS3900, L

PDCP.SDU traffic volume BTS3900 LTE
for PDCP
SDUs in a cell
Description
The counters measure the uplink traffic volume of PDCP SDUs for each service with a
Measurement Points
The number of bits of uplink PDCP SDUs of services with a specific QCI ranging from 1 to 9
is accumulated in a cell as the value of the corresponding counter.

Formula
None
Unit
bit
Related Features
L.Thrp.bits.UL.PDCP.SDU. Multi-mode: None

QCI.1 GSM: None
UMTS: None

QCI.2 GSM: None
UMTS: None

QCI.3 GSM: None
UMTS: None

QCI.4 GSM: None
UMTS: None


QCI.5 GSM: None
UMTS: None

QCI.6 GSM: None
UMTS: None

QCI.7 GSM: None
UMTS: None

QCI.8 GSM: None
UMTS: None

QCI.9 GSM: None
UMTS: None

L.Thrp.bits.UL.PDCP.SDU Multi-mode: None

GSM: None
UMTS: None
1.12.2 Downlink Traffic Volume at the PDCP layer

Counters

PDCP.PDU.QC traffic volume BTS3900 LTE
I.1 for PDCP
PDUs of
services with
the QCI of 1 in
a cell

I.2 for PDCP
PDUs of
services with
the QCI of 2 in
a cell

I.3 for PDCP
PDUs of
services with
the QCI of 3 in
a cell

I.4 for PDCP
PDUs of
services with
the QCI of 4 in
a cell



I.5 for PDCP
PDUs of
services with
the QCI of 5 in
a cell

I.6 for PDCP
PDUs of
services with
the QCI of 6 in
a cell

I.7 for PDCP
PDUs of
services with
the QCI of 7 in
a cell

I.8 for PDCP
PDUs of
services with
the QCI of 8 in
a cell

I.9 for PDCP
PDUs of
services with
the QCI of 9 in
a cell
1526730582 L.Thrp.bits.DL. Total downlink BTS3900, L

PDCP.PDU traffic volume BTS3900 LTE
of PDCP PDUs
in a cell
Description
The counters measure the downlink traffic volume of PDCP PDUs for each service with a

Measurement Points
The number of bits of downlink PDCP PDUs of services with a specific QCI ranging from 1
to 9 is accumulated in a cell as the value of the corresponding counter.
Formula
None
Unit
bit
Related Features
L.Thrp.bits.DL.PDCP.PDU. Multi-mode: None

QCI.1 GSM: None
UMTS: None

QCI.2 GSM: None
UMTS: None

QCI.3 GSM: None
UMTS: None


QCI.4 GSM: None
UMTS: None

QCI.5 GSM: None
UMTS: None

QCI.6 GSM: None
UMTS: None

QCI.7 GSM: None
UMTS: None

QCI.8 GSM: None
UMTS: None


QCI.9 GSM: None
UMTS: None
L.Thrp.bits.DL.PDCP.PDU Multi-mode: None

GSM: None
UMTS: None
1.12.3 Downlink Traffic Volume at the Physical Layer
Counters
1526734141 L.Thrp.bits.DL. Total downlink BTS3900, L

Phy traffic volume BTS3900 LTE
at the physical
layer in a cell
Description
The counters measure the total downlink traffic volume at the physical layer in a cell.
Measurement Points
The number of downlink bits after rate matching transmitted at the physical layer, that is, the
actual downlink traffic volume over the air interface, is incremented in a cell and is used as
the counter value. The counter measurement involves only the LBBPd and UBBP, but not the
LBBPc.
Formula
None

Unit
bit
Related Features
L.Thrp.bits.DL.Phy Multi-mode: None

GSM: None
UMTS: None
1.12.4 Uplink Traffic Volume at the Physical Layer
Counters
1526734142 L.Thrp.bits.UL. Total uplink BTS3900, L

Phy traffic volume BTS3900 LTE
at the physical
layer in a cell
Description
The counters measure the total uplink traffic volume at the physical layer in a cell.
Measurement Points
The number of uplink bits before rate de-matching transmitted at the physical layer, that is,
the traffic volume before rate de-matching and after demodulation, is incremented in a cell
and is used as the counter value. The counter measurement involves only the LBBPd and
UBBP, but not the LBBPc.
Formula
None
Unit
bit

Related Features
L.Thrp.bits.UL.Phy Multi-mode: None

GSM: None
UMTS: None
1.12.5 Maximum Downlink Traffic Volume at the Physical Layer
Counters

Phy.Max downlink traffic BTS3900 LTE
volume of all
services at the
physical layer
Description
The counter measures the maximum downlink traffic volume of all services at the physical
layer in a cell.
Measurement Points
The number of bits after rate matching transmitted at the physical layer is sampled per
millisecond. At the end of the measurement period, the maximum sample value is used as the
counter value. The counter measurement only involves the LBBPd and UBBP boards and
does not involve the LBBPc board.
Formula
None
Unit
bit

Related Features
L.Thrp.bits.DL.Phy.Max Multi-mode: None

GSM: None
UMTS: None
1.12.6 Maximum Uplink Traffic Volume at the Physical Layer
Counters

Phy.Max uplink traffic BTS3900 LTE
volume of all
services at the
physical layer
Description
The counter measures the maximum uplink traffic volume of all services at the physical layer
in a cell.
Measurement Points
The number of bits before rate de-matching transmitted at the physical layer is sampled per
millisecond. At the end of the measurement period, the maximum sample value is used as the
counter value. The counter measurement only involves the LBBPd and UBBP boards and
does not involve the LBBPc board.
Formula
None
Unit
bit

Related Features
L.Thrp.bits.UL.Phy.Max Multi-mode: None

GSM: None
UMTS: None
1.12.7 Total Duration of Data Storage in the Uplink and

Downlink Buffer
Counters
1526734145 L.Thrp.Time.A Total duration BTS3900, L

ctive.Cell.UL of data storage BTS3900 LTE
in the uplink
buffer
1526734146 L.Thrp.Time.A Total duration BTS3900, L

ctive.Cell.DL of data storage BTS3900 LTE
in the downlink
buffer
Description
The counters measure the total uplink and downlink transmit duration of PDCP SDUs for all
UEs in a cell.
The counters are used only for LTE TDD.
Measurement Points
The transmit duration of uplink or downlink services is sampled per millisecond in a cell if
there is uplink or downlink data to be transmitted over a DRB within a millisecond. At the
end of a measurement period, the sum of these sampling results is used as the value of the
L.Thrp.Time.Active.Cell.UL or L.Thrp.Time.Active.Cell.DL counter.

Formula
None
Unit
ms
Related Features
L.Thrp.Time.Active.Cell.UL Multi-mode: None

GSM: None
UMTS: None
LTE: TDLBFD-002008 Radio Bearer Management
L.Thrp.Time.Active.Cell.DL Multi-mode: None

GSM: None
UMTS: None
LTE: TDLBFD-002008 Radio Bearer Management
1.12.8 Total PDCP-Layer Traffic Volume of To-Be-Transmitted

Downlink Data in a Cell
Counters

PDCP.Send layer traffic BTS3900 LTE
volume of to-
be-transmitted
downlink data
in a cell
Description
The counter measures the total PDCP-layer traffic volume of to-be-transmitted downlink data
in a cell.

Measurement Points
The payload of PDCP-layer downlink data to be transmitted is incremented in a cell and used
as the L.Thrp.bits.DL.PDCP.Send counter value.
Formula
None
Unit
bit
Related Features
L.Thrp.bits.DL.PDCP.Send Multi-mode: None

GSM: None
UMTS: None
1.12.9 Total PDCP-Layer Traffic Volume of Discarded To-Be-

Transmitted Downlink Data in a Cell
Counters

PDCP.Discard layer traffic BTS3900 LTE
volume of
discarded to-be-
transmitted
downlink data
in a cell
Description
The counter measures the total PDCP-layer traffic volume of discarded to-be-transmitted
downlink data in a cell.

Measurement Points
The payload of discarded PDCP-layer to-be-transmitted downlink data is incremented in a
cell and used as the L.Thrp.bits.DL.PDCP.Discard counter value.
Formula
None
Unit
bit
Related Features
L.Thrp.bits.DL.PDCP.Disca Multi-mode: None

rd GSM: None
UMTS: None
1.12.10 Total RLC-Layer Traffic Volume of Downlink Data in a

Cell
Counters
1526735570 L.Thrp.bits.DL. Total RLC- BTS3900, L

RLC.Send layer traffic BTS3900 LTE
volume of
downlink data
in a cell
Description
The counter measures the total RLC-layer traffic volume of downlink data in a cell.
Measurement Points
The payload of RLC-layer downlink data is incremented in a cell and used as the
L.Thrp.bits.DL.RLC.Send counter value.

Formula
None
Unit
bit
Related Features
L.Thrp.bits.DL.RLC.Send Multi-mode: None

GSM: None
UMTS: None
1.12.11 Total RLC-Layer Traffic Volume of Uplink Data in a Cell
Counters
1526735571 L.Thrp.bits.UL. Total RLC- BTS3900, L

RLC.Send layer traffic BTS3900 LTE
volume of
uplink data in a
cell
Description
The counter measures the total RLC-layer traffic volume of uplink data in a cell.
Measurement Points
The payload of RLC-layer uplink data is incremented in a cell and used as the
L.Thrp.bits.UL.RLC.Send counter value.
Formula
None

Unit
bit
Related Features
L.Thrp.bits.UL.RLC.Send Multi-mode: None

GSM: None
UMTS: None
1.12.12 Total PDCP-Layer Traffic Volume of Discarded Uplink

Data
Counters
1526735572 L.Thrp.bits.UL. Total PDCP- BTS3900, L

PDCP.Discard layer traffic BTS3900 LTE
volume of
discarded
uplink data in a
cell
Description
The counter measures the total PDCP-layer traffic volume of discarded uplink data in a cell.
Measurement Points
The payload of discarded PDCP-layer uplink data is incremented in a cell and used as the
L.Thrp.bits.UL.PDCP.Discard counter value.
Formula
None
Unit
bit

Related Features
L.Thrp.bits.UL.PDCP.Disca Multi-mode: None

rd GSM: None
UMTS: None
1.12.13 Total PDCP-Layer Traffic Volume of Uplink Data in a Cell

Counters
1526735573 L.Thrp.bits.UL. Total PDCP- BTS3900, L

PDCP.Send layer traffic BTS3900 LTE
volume of
uplink data in a
cell
Description
The counter measures the total PDCP-layer traffic volume of uplink data in a cell.
Measurement Points
The payload of PDCP-layer uplink data is incremented in a cell and used as the
L.Thrp.bits.UL.PDCP.Send counter value.
Formula
None
Unit
bit

Related Features
L.Thrp.bits.UL.PDCP.Send Multi-mode: None

GSM: None
UMTS: None
1.12.14 Uplink Traffic Volume Received for CEUs in a Cell
Counters

BorderUE layer traffic BTS3900 LTE
volume
received for
CEUs in a cell
Description
The counter measures the uplink PDCP-layer traffic volume received for cell edge users
(CEUs) in a cell.
Measurement Points
The traffic volume of uplink PDCP PDUs that are received for cell edge users (CEUs) in a
cell is accumulated and used as the value of the L.Thrp.bits.UL.BorderUE counter.
The eNodeB identifies a CEU based on the signal quality difference between the serving cell
and the strongest neighboring cell in the A3-related measurement report. This identification
function is controlled by the BasedA3EdgeUserSwitch option of the CellCounterAlgoSwitch
parameter in the CellCounterParaGroup MO.
Formula
None
Unit
bit

Related Features
L.Thrp.bits.UL.BorderUE Multi-mode: None

GSM: None
UMTS: None
1.12.15 Downlink Traffic Volume Sent for CEUs in a Cell
Counters

BorderUE PDCP-layer BTS3900 LTE
traffic volume
sent for CEUs
in a cell
Description
The counter measures the downlink PDCP-layer traffic volume sent for cell edge users
(CEUs) in a cell.
Measurement Points
The traffic volume of downlink PDCP SDUs that are sent for cell edge users (CEUs) in a cell
is accumulated and used as the value of the L.Thrp.bits.DL.BorderUE counter.
Formula
None
Unit
bit

Related Features
L.Thrp.bits.DL.BorderUE Multi-mode: None

GSM: None
UMTS: None
1.12.16 PDCP-layer Traffic Volume Scheduled for Uplink Small

Packets for CEUs in a Cell
Counters
1526737756 L.Thrp.bits.UL. PDCP-layer BTS3900, L

SmallPkt.Borde traffic volume BTS3900 LTE
rUE scheduled for
uplink small
packets for
CEUs in a cell
Description
The counter measures the PDCP-layer traffic volume scheduled for small packets for cell
edge users (CEUs) in a cell.
Measurement Points
The traffic volume of PDCP PDUs received for uplink small packets for cell edge users
(CEUs) in a cell is accumulated and used as the value of the
L.Thrp.bits.UL.SmallPkt.BorderUE counter. An uplink packet which is scheduled before the
eNodeB receives a buffer status report (BSR) or is received when the uplink buffer of the UE
becomes empty is determined as a small packet.
Formula
None

Unit
bit
Related Features
L.Thrp.bits.UL.SmallPkt.Bo Multi-mode: None

rderUE GSM: None
UMTS: None
1.12.17 Transmission Duration of Uplink Data Except Small

Packets for CEUs in a cell
Counters
1526737757 L.Thrp.Time.U Transmission BTS3900, L

L.RmvSmallPkt duration of BTS3900 LTE
.BorderUE uplink data
except small
packets for
CEUs in a cell
Description
The counter measures the uplink data transmission duration except that for small packets for
cell edge users (CEUs) in a cell.
Measurement Points
A buffer status report (BSR) indicates the data amount of the uplink buffer of a UE. Except
the last TTI before the UE buffer is empty, the duration from the time that the uplink buffer of
a cell edge user (CUE) is not empty to the time that the uplink buffer of the CUE is empty is
measured in a cell. The duration of transmissions and the scheduling waiting time are counted
in the measurement result. The measurement results are accumulated and used as the value of
the L.RmvSmallPkt.BorderUE counter.

Formula
None
Unit
ms
Related Features
L.Thrp.Time.UL.RmvSmall Multi-mode: None

Pkt.BorderUE GSM: None
UMTS: None
1.12.18 Downlink PDCP-layer Traffic Volume Sent in the Last

TTI for CEUs Before the Buffer is Empty in a Cell
Counters

LastTTI.Border PDCP-layer BTS3900 LTE
UE traffic volume
sent in the last
TTI for CEUs
before the
buffer is empty
in a cell
Description
The counter measures the PDCP-layer traffic volume sent in the last TTI for cell edge users
(CEUs) before the downlink buffer is empty in a cell.
Measurement Points
The traffic volume of downlink PDCP SDUs sent in the last TTI for cell edge users (CEUs)
performing services with various QCIs in a cell before the DRB buffer is empty is measured.
The measurement results are accumulated and used as the value of the
L.Thrp.bits.DL.LastTTI.BorderUE counter.


Formula
None
Unit
bit
Related Features
L.Thrp.bits.DL.LastTTI.Bor Multi-mode: None

derUE GSM: None
UMTS: None
1.12.19 Data Transmission Duration for CEUs Except the Last TTI
Before the Downlink Buffer Is Empty
Counters
1526737759 L.Thrp.Time.D Data BTS3900, L

L.RmvLastTTI. transmission BTS3900 LTE
BorderUE duration for
CEUs except
the last TTI
before the
downlink buffer
is empty
Description
The counter measures the data transmission duration for cell edge users (CEUs) except the
last TTI before the downlink buffer is empty in a cell.
Measurement Points
The data transmission status of cell edge users (CEUs) in a cell is evaluated per millisecond.
If there is downlink data to be transmitted on DRBs in a millisecond, the

L.Thrp.Time.DL.RmvLastTTI.BorderUE counter is incremented by one millisecond, except

the last TTI before the DRB buffer is empty.
Formula
None
Unit
ms
Related Features

TI.BorderUE GSM: None
UMTS: None
1.13 Paging Measurement (Paging.Cell)

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
Description
1526726884 L.Paging.S1.Rx Number of received BTS3900:

paging messages V100R008C00
over the S1 interface BTS3900 LTE:
in a cell version earlier than
V100R003C00


Description
1526726885 L.Paging.UU.Att Number of UEs BTS3900:

contained in paging V100R008C00
messages BTS3900 LTE:
transmitted over the version earlier than
Uu interface in a cell V100R003C00
1526726886 L.Paging.UU.Succ Number of BTS3900:

Successful Paging V100R008C00
Responses from the BTS3900 LTE:
UE in a Cell version earlier than
V100R003C00
1526727212 L.Paging.Dis.Num Number of BTS3900:

discarded paging V100R008C00
messages from the BTS3900 LTE:
MME to UEs version earlier than
V100R003C00
1526728337 L.Paging.UU.SIUp Number of paging BTS3900:

date messages V100R008C00
transmitted due to BTS3900 LTE:
system information V100R005C00
changes
1526728521 L.Paging.Dis.PchC Number of paging BTS3900:

ong messages discarded V100R008C00
due to paging BTS3900 LTE:
channel congestion V100R008C00
1526730140 L.Paging.UU.Succ. Number of paging BTS3900:

CSFB responses for CSFB V100R009C00
received from UEs BTS3900 LTE:
1526730145 L.Paging.S1.Rx.CS Number of received BTS3900:

paging messages V100R009C00
with the IE CN BTS3900 LTE:
DOMAIN set to CS V100R009C00
over the S1 interface
in a cell
1526730562 L.Paging.UU.Num Number of paging BTS3900:

messages sent over V100R008C01
the Uu interface in a BTS3900 LTE:
cell V100R008C01
The Paging.Cell function subset contains counters related to Paging. The following table
shows the parent-child relationship of the counters.

L.Paging.S1.Rx L.Paging.S1.Rx.CS
1.13.1 Number of Received Paging Messages over the S1 Interface

in a Cell
Counters
1526726884 L.Paging.S1.Rx Number of BTS3900, L

received paging BTS3900 LTE
messages over
the S1 interface
in a cell
1526730145 L.Paging.S1.Rx Number of BTS3900, L

.CS received paging BTS3900 LTE
messages with
the IE CN
DOMAIN set to
CS over the S1
interface in a
cell
Description
The counter measures the number of paging messages received by the eNodeB over the S1
interface in a cell.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-123, the L.Paging.S1.Rx counter is incremented by 1 each
time the eNodeB receives a paging message from the MME and at least on tracking area
identity (TAI) of the cell is in the TAI list in the paging message. In addition, if the IE CN
DOMAIN in the paging message is set to CS, the L.Paging.S1.Rx.CS counter is incremented
by 1.

Figure 1-123
Formula
None
Unit
None
Related Features
L.Paging.S1.Rx Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002011 Paging
TDLBFD-002011 Paging
L.Paging.S1.Rx.CS Multi-mode: None

GSM: None
UMTS: None

1.13.2 Number of UEs Contained in Paging Messages Transmitted

over the Uu Interface in a Cell
Counters
1526726885 L.Paging.UU.A Number of UEs BTS3900, L

tt contained in BTS3900 LTE
paging
messages
transmitted over
the Uu interface
in a cell
Description
The counter measures the number of UEs contained in paging messages that the eNodeB
sends to UEs over the Uu interface.According to 3GPP TS 36.304, after the eNodeB receives
a paging message from the MME over the S1 interface, the eNodeB does not send the paging
message to UEs over the Uu interface until the next paging cycle comes. Therefore, there is a
possibility that the number of paging messages measured over the S1 interface and that
measured over the Uu interface within the same measurement period are not the same.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-124, 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 1-124
Formula
None

Unit
None
Related Features
L.Paging.UU.Att Multi-mode: None

GSM: None
UMTS: None
1.13.3 Number of Successful Paging Responses from the UE in a

Cell
Counters
1526726886 L.Paging.UU.S Number of BTS3900, L

ucc Successful BTS3900 LTE
Paging
Responses from
the UE in a Cell
1526730140 L.Paging.UU.S Number of BTS3900, L

ucc.CSFB paging BTS3900 LTE
responses for
CSFB received
from UEs in a
cell
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 1-125, the L.Paging.UU.Succ counter is incremented by 1
each time the eNodeB receives an RRC Connection Request message with the IE
EstablishmentCause set to mt-Access from a UE in the RRC_IDLE state.

As shown at point B in Figure 1-125, the L.Paging.UU.Succ.CSFB counter is incremented by

1 each time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST message
containing the IE CS Fallback required from the MME.
Figure 1-125
Formula
None
Unit
None

Related Features
L.Paging.UU.Succ Multi-mode: None

GSM: None
UMTS: None
L.Paging.UU.Succ.CSFB Multi-mode: None

GSM: None
UMTS: None
1.13.4 Number of Discarded Paging Messages from the MME to

UEs in a Cell
Counters
1526727212 L.Paging.Dis.N Number of BTS3900, L

um discarded BTS3900 LTE
paging
messages from
the MME to
UEs
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
L.Paging.Dis.Num Multi-mode: None

GSM: None
UMTS: None
1.13.5 Number of Paging Messages Transmitted Due to System

Information Changes
Counters
1526728337 L.Paging.UU.SI Number of BTS3900, L

Update paging BTS3900 LTE
messages
transmitted due
to system
information
changes
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 1-126, 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 1-126

Formula
None
Unit
None
Related Features
L.Paging.UU.SIUpdate Multi-mode: None

GSM: None
UMTS: None
1.13.6 Number of Paging Messages Discarded due to Paging

Channel Congestion
Counters
1526728521 L.Paging.Dis.Pc Number of BTS3900, L

hCong paging BTS3900 LTE
messages
discarded due
to paging
channel
congestion
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
L.Paging.Dis.PchCong Multi-mode: None

GSM: None
UMTS: None
1.13.7 Number of Paging Messages Sent Over the Uu Interface in

a Cell
Counters
1526730562 L.Paging.UU.N Number of BTS3900, L

um paging BTS3900 LTE
messages sent
over the Uu
interface in a
cell
Description
The counter measures the number of paging messages sent over the Uu interface in a cell.
Measurement Points
As shown at point A in Figure 1-127, the L.Paging.UU.Num counter is incremented by 1
each time the eNodeB sends a paging message over the Uu interface in a cell.

Figure 1-127
Formula
None
Unit
None
Related Features
L.Paging.UU.Num Multi-mode: None

GSM: None
UMTS: None
1.14 Security Mode Measurement (SecurMode.Cell)

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 1-128 shows the measurement points of security mode configuration.

Figure 1-128
Counters
Description
1526727171 L.SecurMode.S1.R Number of security BTS3900:

x mode configurations V100R008C00
received over the S1 BTS3900 LTE:
interface V100R005C00
1526727172 L.SecurMode.Cmd Number of security BTS3900:

mode commands V100R008C00
sent over the Uu BTS3900 LTE:
interface V100R005C00
1526727173 L.SecurMode.Cmp Number of BTS3900:

successful security V100R008C00
mode configurations BTS3900 LTE:
received from the V100R005C00
UE
1526727174 L.SecurMode.Fail Number of security BTS3900:

mode configuration V100R008C00
failures received BTS3900 LTE:
from the UE V100R005C00
None

1.14.1 Number of Security Mode Setups in a Cell
Counters
1526727171 L.SecurMode.S Number of BTS3900, L

1.Rx security mode BTS3900 LTE
configurations
received over
the S1 interface
1526727172 L.SecurMode.C Number of BTS3900, L

md security mode BTS3900 LTE
commands sent
over the Uu
interface
1526727173 L.SecurMode.C Number of BTS3900, L

mp successful BTS3900 LTE
security mode
configurations
received from
the UE
1526727174 L.SecurMode.F Number of BTS3900, L

ail security mode BTS3900 LTE
configuration
failures
received from
the UE
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 1-129, 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 1-129, 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 1-129, 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 1-130, the L.SecurMode.Fail counter is incremented by 1 each
time the eNodeB receives a Security Mode Failure message from the UE.
Figure 1-129

Figure 1-130
Formula
None
Unit
None
Related Features
L.SecurMode.S1.Rx Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001010 Security Mechanism
TDLOFD-001010 Security Mechanism
L.SecurMode.Cmd Multi-mode: None

GSM: None
UMTS: None

L.SecurMode.Cmp Multi-mode: None

GSM: None
UMTS: None
L.SecurMode.Fail Multi-mode: None

GSM: None
UMTS: None
1.15 RA Measurement (RA.Cell)

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
Description
1526727215 L.RA.GrpA.Att Number of times the BTS3900:

contention preamble V100R008C00
in group A is BTS3900 LTE:
received version earlier than
V100R003C00
1526727216 L.RA.GrpA.Resp Number of times a BTS3900:

cell sends a Random V100R008C00
Access Response BTS3900 LTE:
message after version earlier than
receiving a preamble V100R003C00
in group A
1526727217 L.RA.GrpA.ContR Number of times a BTS3900:

esolution cell sends a V100R008C00
Contention BTS3900 LTE:
Resolution message version earlier than
after receiving a V100R003C00
preamble in group A


Description
1526727218 L.RA.GrpB.Att Number of times the BTS3900:

contention preamble V100R008C00
in group B is BTS3900 LTE:
V100R003C00
1526727219 L.RA.GrpB.Resp Number of times a BTS3900:

cell sends a Random V100R008C00
Access Response BTS3900 LTE:
message after version earlier than
receiving a preamble V100R003C00
in group B
1526727220 L.RA.GrpB.ContR Number of times a BTS3900:

esolution cell sends a V100R008C00
Contention BTS3900 LTE:
Resolution message version earlier than
after receiving a V100R003C00
preamble in group B
1526727221 L.RA.Dedicate.Att Number of times the BTS3900:

non-contention- V100R008C00
based preamble is BTS3900 LTE:
V100R003C00
1526727222 L.RA.Dedicate.HO. Number of times the BTS3900:

Att non-contention- V100R008C00
received (used in version earlier than
handover) V100R003C00
1526727223 L.RA.Dedicate.Res Number of times the BTS3900:

p Random Access V100R008C00
Response message is BTS3900 LTE:
sent after the non- version earlier than
contention-based V100R003C00
preamble is received

Resp Random Access V100R008C00
Response message is BTS3900 LTE:
sent after the non- version earlier than
contention-based V100R003C00
preamble is received
(used in handover)


Description

Msg3Rcv UE Msg3 Response V100R008C00
message is received BTS3900 LTE:
in the handover- version earlier than
triggered non- V100R003C00
contention-based
RA procedure
1526728913 L.RA.PreambleSen Number of random BTS3900:

tNum1 access procedures V100R008C01
with the preamble BTS3900 LTE:
sent by 1 time V100R008C01

sent by 2 times V100R008C01



tNum5or6 access procedures V100R008C01
sent by 5 or 6 times V100R008C01


1526728920 L.RA.UeRaInfoRs Number of received BTS3900:

p.Num UEInformationRes- V100R008C01
ponse messages BTS3900 LTE:
containing RACH V100R008C01
information


Description
1526728921 L.RA.UeRaInfoRs Number of received BTS3900:

pWithCon.Num UEInformationRes- V100R008C01
ponse messages BTS3900 LTE:
whose V100R008C01
"contentionDetec-
ted" is TRUE
1526728932 L.RA.GrpAandB.A Maximum number BTS3900:

tt.Max of times a V100R008C01
contention-based BTS3900 LTE:
preamble is received V100R008C01
1526728937 L.RA.Dedicate.Pre Number of times the BTS3900:

ambleReq.Num non-contention- V100R008C01
requested V100R008C01
1526728938 L.RA.Dedicate.Pre Maximum number BTS3900:

ambleReq.Num.Ma of times the non- V100R008C01
x contention-based BTS3900 LTE:
preamble is V100R008C01
requested
1526728939 L.RA.Dedicate.Pre Number of times the BTS3900:

ambleAssign.Num non-contention- V100R008C01
assigned V100R008C01
1526728954 L.RA.GrpA.ContR Number of times the BTS3900:

esolution.PDCCH Contention V100R008C00
Resolution message BTS3900 LTE:
is sent on the V100R008C00
PDCCH after the
contention-based
preamble in group A
is received
1526728955 L.RA.GrpB.ContR Number of times the BTS3900:

esolution.PDCCH Contention V100R008C00
Resolution message BTS3900 LTE:
is sent on the V100R008C00
PDCCH after the
contention-based
preamble in group B
is received
1526728956 L.RA.TA.UE.Index Number of times the BTS3900:

0 TA value is within V100R008C00
index 0 in a UE- BTS3900 LTE:
initiated random V100R008C00
access procedure


Description

access procedure

access procedure

access procedure

access procedure

access procedure

access procedure

access procedure

access procedure


Description

access procedure

access procedure

access procedure
1526730874 L.RA.GrpA.Disc.B Number of times BTS3900:

yTA.Num that the contention- V100R009C00
based preamble in BTS3900 LTE:
group A is discarded V100R009C00
based on the TA
1526730875 L.RA.GrpB.Disc.B Number of times BTS3900:

yTA.Num that the contention- V100R009C00
based preamble in BTS3900 LTE:
group B is discarded V100R009C00
based on the TA
The RA.Cell function subset contains counters related to random access. In terms of the
preamble group, some of these counters can be categorized as counters related to dedicated
preambles, random preambles in group A, and random preambles in group B. The following
table shows the parent-child relationship of the counters.
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
L.RA.UeRaInfoRsp.Num L.RA.UeRaInfoRspWithCon.Num

1.15.1 Number of Times the Contention Preamble Is Received
Counters
1526727215 L.RA.GrpA.Att Number of BTS3900, L

times the BTS3900 LTE
contention
preamble in
group A is
received
1526727218 L.RA.GrpB.Att Number of BTS3900, L

times the BTS3900 LTE
contention
preamble in
group B is
received
1526728932 L.RA.GrpAand Maximum BTS3900, L

B.Att.Max number of BTS3900 LTE
times a
contention-
based preamble
is received
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.
The signaling flows involved in the counter(s) comply with sections 10.1.5 in 3GPP TS
36.300 V10.6.0.
Measurement Points
As shown at point A in Figure 1-131, the corresponding counter is incremented by 1 each
time the eNodeB receives a Random Access Preamble message from a UE. The counters are
The L.RA.GrpA.Att counter is incremented by 1 if the preamble is a contention-based

preamble and belongs to group A.

The L.RA.GrpB.Att counter is incremented by 1 if the preamble is a contention-based

preamble and belongs to group B.
The number of times the contention preamble is received in a cell is sampled per second. At
the end of a measurement period, the maximum of these sampling results is used as the value
of the L.RA.GrpAandB.Att.Max counter.
Figure 1-131
Formula
None
Unit
None
Related Features
L.RA.GrpA.Att Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002010 Random Access Procedure
TDLBFD-002010 Random Access Procedure
L.RA.GrpB.Att Multi-mode: None

GSM: None
UMTS: None

L.RA.GrpAandB.Att.Max Multi-mode: None

GSM: None
UMTS: None
1.15.2 Number of Times the Random Access Response Message Is

Sent After the Contention Preamble Is Received
Counters
1526727216 L.RA.GrpA.Res Number of BTS3900, L

p times a cell BTS3900 LTE
sends a
Random Access
Response
message after
receiving a
preamble in
group A
1526727219 L.RA.GrpB.Res Number of BTS3900, L

p times a cell BTS3900 LTE
sends a
Random Access
Response
message after
receiving a
preamble in
group B
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.
36.300 V10.6.0.

Measurement Points
As shown at point B in Figure 1-132, 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:
The L.RA.GrpA.Resp counter is incremented by 1 if the preamble belongs to group A.
The L.RA.GrpB.Resp counter is incremented by 1 if the preamble belongs to group B.
Figure 1-132
Formula
None
Unit
None
Related Features
L.RA.GrpA.Resp Multi-mode: None

GSM: None
UMTS: None

L.RA.GrpB.Resp Multi-mode: None

GSM: None
UMTS: None
1.15.3 Number of Times the Contention Resolution Message Is

Sent After the Contention Preamble Is Received
Counters
1526727217 L.RA.GrpA.Co Number of BTS3900, L

ntResolution times a cell BTS3900 LTE
sends a
Contention
Resolution
message after
receiving a
preamble in
group A
1526727220 L.RA.GrpB.Co Number of BTS3900, L

ntResolution times a cell BTS3900 LTE
sends a
Contention
Resolution
message after
receiving a
preamble in
group B
1526728954 L.RA.GrpA.Co Number of BTS3900, L

ntResolution.P times the BTS3900 LTE
DCCH Contention
Resolution
message is sent
on the PDCCH
after the
contention-
based preamble
in group A is
received


1526728955 L.RA.GrpB.Co Number of BTS3900, L

ntResolution.P times the BTS3900 LTE
DCCH Contention
Resolution
message is sent
on the PDCCH
after the
contention-
based preamble
in group B is
received
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.
36.300 V10.6.0.
Measurement Points
As shown at point C in Figure 1-133, 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.
The L.RA.GrpB.ContResolution counter is incremented by 1 if the contention preamble
belongs to group B.
As shown at point C in Figure 1-133, 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:
The L.RA.GrpA.ContResolution.PDCCH counter is incremented by 1 if the contention-based
preamble belongs to group A.
The L.RA.GrpB.ContResolution.PDCCH counter is incremented by 1 if the contention-based
preamble belongs to group B.

Figure 1-133
Formula
None
Unit
None
Related Features
L.RA.GrpA.ContResolution Multi-mode: None

GSM: None
UMTS: None
L.RA.GrpB.ContResolution Multi-mode: None

GSM: None
UMTS: None
L.RA.GrpA.ContResolution. Multi-mode: None

PDCCH GSM: None
UMTS: None

L.RA.GrpB.ContResolution. Multi-mode: None

PDCCH GSM: None
UMTS: None
1.15.4 Number of Times the Non-Contention-Based Preamble Is

Received
Counters
1526727221 L.RA.Dedicate. Number of BTS3900, L

Att times the non- BTS3900 LTE
contention-
based preamble
is received

HO.Att times the non- BTS3900 LTE
contention-
based preamble
is received
(used in
handover)
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 1-134, the corresponding counter is incremented by 1 each
time the eNodeB receives a non-contention-based preamble:
The L.RA.Dedicate.Att counter is incremented by 1.

The L.RA.Dedicate.HO.Att counter is incremented by 1 in a handover.
Figure 1-134
Formula
None
Unit
None
Related Features
L.RA.Dedicate.Att Multi-mode: None

GSM: None
UMTS: None
L.RA.Dedicate.HO.Att Multi-mode: None

GSM: None
UMTS: None

1.15.5 Number of Times the Random Access Response Message Is

Sent After the Non-Contention-Based Preamble Is Received
Counters

Resp times the BTS3900 LTE
Random Access
Response
message is sent
after the non-
contention-
based preamble
is received

HO.Resp times the BTS3900 LTE
Random Access
Response
message is sent
after the non-
contention-
based preamble
is received
(used in
handover)
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.
36.300 V10.6.0.
Measurement Points
As shown at point C in Figure 1-135, 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:
The L.RA.Dedicate.Resp counter is incremented by 1 for non-contention-based preamble.
The L.RA.Dedicate.HO.Resp counter is incremented by 1 for non-contention-based preamble

and in a handover.

Figure 1-135
Formula
None
Unit
None
Related Features
L.RA.Dedicate.Resp Multi-mode: None

GSM: None
UMTS: None
L.RA.Dedicate.HO.Resp Multi-mode: None

GSM: None
UMTS: None

1.15.6 Number of Times the UE Msg3 Response Message Is

Received in the Handover-Triggered Non-Contention-Based RA
Procedure
Counters

HO.Msg3Rcv times the UE BTS3900 LTE
Msg3 Response
message is
received in the
handover-
triggered non-
contention-
based RA
procedure
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.
V10.6.0.
Measurement Points
As shown at point D in Figure 1-136, 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 1-136
Formula
None
Unit
None
Related Features
L.RA.Dedicate.HO.Msg3Rc Multi-mode: None

v GSM: None
UMTS: None

1.15.7 Number of Random Access Procedures

Counters
1526728913 L.RA.Preamble Number of BTS3900, L

SentNum1 random access BTS3900 LTE
procedures with
the preamble
sent by 1 time

procedures with
the preamble
sent by 2 times

procedures with
the preamble
sent by 3 times

procedures with
the preamble
sent by 4 times

SentNum5or6 random access BTS3900 LTE
procedures with
the preamble
sent by 5 or 6
times

procedures with
the preamble
sent by 7 or 8
times

procedures with
the preamble
sent by 9 or 10
times


1526728920 L.RA.UeRaInfo Number of BTS3900, L

Rsp.Num received BTS3900 LTE
UEInformation
Response
messages
containing
RACH
information
1526728921 L.RA.UeRaInfo Number of BTS3900, L

RspWithCon.N received BTS3900 LTE
um UEInformation
Response
messages
whose
"contentionDete
cted" is TRUE
Description
A UE may send the preamble for many times during a random access procedure. The counters
measure the number of random access procedures with the preamble sent by different times in
the cell.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-137, the corresponding counter is incremented each time the
eNodeB receives a UEInformationResponse message from a UE. The counters are measured
as follows:
If the value of the "numberOfPreamblesSent" IE in the message is 1, the

L.RA.PreambleSentNum1 counter is incremented by 1.




L.RA.PreambleSentNum5or6 counter is incremented by 1.



If the message contains the "rach-Report" IE, the L.RA.UeRaInfoRsp.Num counter is
incremented by 1.
If the value of the "contentionDetected" IE in the message is TRUE, the
L.RA.UeRaInfoRspWithCon.Num counter is incremented by 1.
Figure 1-137
Formula
None
Unit
None

Related Features
L.RA.PreambleSentNum1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
L.RA.PreambleSentNum5or Multi-mode: None

6 GSM: None
UMTS: None

8 GSM: None
UMTS: None

10 GSM: None
UMTS: None

L.RA.UeRaInfoRsp.Num Multi-mode: None

GSM: None
UMTS: None
L.RA.UeRaInfoRspWith- Multi-mode: None

Con.Num GSM: None
UMTS: None
1.15.8 Number of Times the Non-Contention-based Preamble is

Requested
Counters

PreambleReq.N times the non- BTS3900 LTE
um contention-
based preamble
is requested
1526728938 L.RA.Dedicate. Maximum BTS3900, L

PreambleReq.N number of BTS3900 LTE
um.Max times the non-
contention-
based preamble
is requested
Description
The non-contention-based random access (RA) procedure is used in handovers or uplink
synchronization recovery. The preamble used in the non-contention-based 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 number of times the non-contention-
based preamble is requested in a cell to evaluate its load status.

Measurement Points
The L.RA.Dedicate.PreambleReq.Num counter is incremented by 1 each time the non-
contention-based preamble is requested in a cell.
The number of times the non-contention-based preamble is requested in a cell is sampled per
second. At the end of a measurement period, the maximum of these sampling results is used
as the value of the L.RA.Dedicate.PreambleReq.Num.Max counter.
Formula
None
Unit
None
Related Features
L.RA.Dedicate.PreambleRe Multi-mode: None

q.Num GSM: None
UMTS: None
L.RA.Dedicate.PreambleRe Multi-mode: None

q.Num.Max GSM: None
UMTS: None
1.15.9 Number of Times the Non-Contention-based Preamble is

Assigned
Counters

PreambleAssig times the non- BTS3900 LTE
n.Num contention-
based preamble
is assigned

Description
The non-contention-based random access (RA) procedure is used in handovers or uplink
synchronization recovery. The preamble used in the non-contention-based 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 counter measures the number of times the non-contention-
based preamble is assigned in a cell.
Measurement Points
The L.RA.Dedicate.PreambleAssign.Num counter is incremented by 1 each time the non-
contention-based preamble is assigned in a cell.
Formula
None
Unit
None
Related Features
L.RA.Dedicate.PreambleAs Multi-mode: None

sign.Num GSM: None
UMTS: None
1.15.10 Number of Times the TA with a Specific Value Range in a

UE-Initiated Random Access Procedure in a Cell
Counters
1526728956 L.RA.TA.UE.In Number of BTS3900, L

dex0 times the TA BTS3900 LTE
value is within
index 0 in a
UE-initiated
random access
procedure



value is within
index 1 in a
UE-initiated
random access
procedure

value is within
index 2 in a
UE-initiated
random access
procedure

value is within
index 3 in a
UE-initiated
random access
procedure

value is within
index 4 in a
UE-initiated
random access
procedure

value is within
index 5 in a
UE-initiated
random access
procedure

value is within
index 6 in a
UE-initiated
random access
procedure



value is within
index 7 in a
UE-initiated
random access
procedure

value is within
index 8 in a
UE-initiated
random access
procedure

value is within
index 9 in a
UE-initiated
random access
procedure

value is within
index 10 in a
UE-initiated
random access
procedure

value is within
index 11 in a
UE-initiated
random access
procedure
Description
The counters measure the number of times the TA in the Random Access Response message
has a specific value range in a cell. TA indexes are defines as follows:
Index 0: [0, 1]
Index 1: [2, 3]
Index 2: [4, 7]

Index 3: [8, 13]
Index 4: [14, 25]
Index 5: [26, 45]
Index 6: [46, 85]
Index 7: [86, 185]
Index 8: [186, 385]
Index 9: [386, 685]
Index 10: [686, 985]
Index 11: (985, +)
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
L.RA.TA.UE.Index0 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
1.15.11 Number of Times that the Contention-based Preamble in

Group A is Discarded based on the TA
Counters
1526730874 L.RA.GrpA.Dis Number of BTS3900, L

c.ByTA.Num times that the BTS3900 LTE
contention-
based preamble
in group A is
discarded based
on the TA
Description
After receiving a contention-based preamble, the eNodeB discards the preamble if the
distance between the UE sending this preamble and the eNodeB is greater than the cell radius,
and does not send random access response (RAR) to the UE. This counter measures the
condition where preamble in group A is discarded in the cell.

Measurement Points
As shown at point A in Figure 1-138, this counter is incremented by 1 each time the eNodeB
receives a Random Access Preamble message from a UE, this preamble is a contention-based
preamble in group A, and the distance between the UE sending this preamble and the eNodeB
is greater than the cell radius.
Figure 1-138
Formula
None
Unit
None
Related Features
L.RA.GrpA.Disc.ByTA.Nu Multi-mode: None

m GSM: None
UMTS: None

1.15.12 Number of Times that the Contention-based Preamble in

Group B is Discarded Based on the TA
Counters
1526730875 L.RA.GrpB.Dis Number of BTS3900, L

c.ByTA.Num times that the BTS3900 LTE
contention-
based preamble
in group B is
discarded based
on the TA
Description
After receiving a contention-based preamble, the eNodeB discards the preamble if the
distance between the UE sending this preamble and the eNodeB is greater than the cell radius,
and does not send random access response (RAR) to the UE. This counter measures the
condition where preamble in group B is discarded in the cell.
Measurement Points
As shown at point A in Figure 1-139, this counter is incremented by 1 each time the eNodeB
receives a Random Access Preamble message from a UE, this preamble is a contention-based
preamble in group B, and the distance between the UE sending this preamble and the eNodeB
is greater than the cell radius.
Figure 1-139

Formula
None
Unit
None
Related Features
L.RA.GrpB.Disc.ByTA.Nu Multi-mode: None

m GSM: None
UMTS: None
1.16 Channel Quality Measurement (ChMeas.Pwr.Cell)

Overview
The ChMeas.Pwr.Cell function subset measures the power in a cell to analyze the overall
quality of the downlink channel.
Counters
Description
1526727388 L.DLPwr.Max Maximum downlink BTS3900:

transmit power in a V100R008C00
cell BTS3900 LTE:
V100R003C00
1526727389 L.DLPwr.Avg Average downlink BTS3900:

transmit power in a V100R008C00
cell BTS3900 LTE:
V100R003C00
1526728297 L.UL.Interference. Maximum uplink BTS3900:

Max interference and V100R008C00
noise received by BTS3900 LTE:
each PRB in a cell V100R005C00


Description
1526728298 L.UL.Interference. Average uplink BTS3900:

Avg interference and V100R008C00
1526728435 L.UL.Interference. Minimum uplink BTS3900:

Min interference and V100R008C00
1526728769 L.UpPTS.Interfere Power of BTS3900:

nce.Avg interference and V100R008C00
noise detected in BTS3900 LTE:
each PRB in the UL V100R008C00
UpPTS.
1526728770 L.UL.FirstUL0.Pw This counter BTS3900:

r indicates the receive V100R008C00
power of the first BTS3900 LTE:
symbol in the first V100R008C00
UL subframe.
1526728771 L.UL.FirstUL6(4). This counter BTS3900:

Pwr indicates the receive V100R008C00
power of the seventh BTS3900 LTE:
(or fifth) symbol in V100R008C00
the first UL
subframe.
1526728772 L.UL.LastUL0.Pwr This counter BTS3900:

indicates the receive V100R008C00
power of the first BTS3900 LTE:
symbol in the last V100R008C00
UL subframe.
1526728773 L.UL.LastUL11(9). This counter BTS3900:

Pwr indicates the receive V100R008C00
power of the twelfth BTS3900 LTE:
(or tenth) symbol in V100R008C00
the last UL
subframe.
1526732045 L.UL.RSSI.PUCC Number of times the BTS3900:

H.Index0 eNodeB detects a V100R008C01
PRB-level average BTS3900 LTE:
RSSI ranging within V100R008C01
index 0 on the
PUCCH


Description

index 1 on the
PUCCH

index 2 on the
PUCCH

index 3 on the
PUCCH

index 4 on the
PUCCH

index 5 on the
PUCCH

index 6 on the
PUCCH

index 7 on the
PUCCH


Description

index 8 on the
PUCCH

index 9 on the
PUCCH

index 10 on the
PUCCH

index 11 on the
PUCCH

index 12 on the
PUCCH

index 13 on the
PUCCH

index 14 on the
PUCCH


Description

index 15 on the
PUCCH

index 16 on the
PUCCH

index 17 on the
PUCCH

index 18 on the
PUCCH

index 19 on the
PUCCH

index 20 on the
PUCCH

index 21 on the
PUCCH


Description
1526732067 L.UL.RSSI.PUSCH Number of times the BTS3900:

.Index0 eNodeB detects a V100R008C01
index 0 on the
PUSCH

index 1 on the
PUSCH

index 2 on the
PUSCH

index 3 on the
PUSCH

index 4 on the
PUSCH

index 5 on the
PUSCH

index 6 on the
PUSCH


Description

index 7 on the
PUSCH

index 8 on the
PUSCH

index 9 on the
PUSCH

index 10 on the
PUSCH

index 11 on the
PUSCH

index 12 on the
PUSCH

index 13 on the
PUSCH


Description

index 14 on the
PUSCH

index 15 on the
PUSCH

index 16 on the
PUSCH

index 17 on the
PUSCH

index 18 on the
PUSCH

index 19 on the
PUSCH

index 20 on the
PUSCH


Description

index 21 on the
PUSCH
1526734045 L.UL.Interference. Number of times the BTS3900:

PUSCH.Index0 eNodeB detects a V100R008C01
PRB-level IN BTS3900 LTE:
ranging within index V100R008C01
0 on the PUSCH

1 on the PUSCH

2 on the PUSCH

3 on the PUSCH

4 on the PUSCH

5 on the PUSCH

6 on the PUSCH


Description

7 on the PUSCH

8 on the PUSCH

9 on the PUSCH

10 on the PUSCH

11 on the PUSCH

12 on the PUSCH

13 on the PUSCH

14 on the PUSCH


Description

15 on the PUSCH

PUCCH.Index0 eNodeB detects a V100R008C01
0 on the PUCCH

1 on the PUCCH

2 on the PUCCH

3 on the PUCCH

4 on the PUCCH

5 on the PUCCH

6 on the PUCCH


Description

7 on the PUCCH

8 on the PUCCH

9 on the PUCCH

10 on the PUCCH

11 on the PUCCH

12 on the PUCCH

13 on the PUCCH

14 on the PUCCH


Description

15 on the PUCCH

PRACH.Index0 eNodeB detects a V100R008C01
0 on the PRACH

1 on the PRACH

2 on the PRACH

3 on the PRACH

4 on the PRACH

5 on the PRACH

6 on the PRACH


Description

7 on the PRACH

8 on the PRACH

9 on the PRACH

10 on the PRACH

11 on the PRACH

12 on the PRACH

13 on the PRACH

14 on the PRACH


Description

15 on the PRACH
1526734093 L.UL.RSRP.PUSC Number of times the BTS3900:

UE-level RSRP BTS3900 LTE:
0 on the PUSCH

1 on the PUSCH

2 on the PUSCH

3 on the PUSCH

4 on the PUSCH

5 on the PUSCH

6 on the PUSCH


Description

7 on the PUSCH

8 on the PUSCH

9 on the PUSCH

10 on the PUSCH

11 on the PUSCH

12 on the PUSCH

13 on the PUSCH

14 on the PUSCH


Description

15 on the PUSCH

16 on the PUSCH

17 on the PUSCH

18 on the PUSCH

19 on the PUSCH

20 on the PUSCH

21 on the PUSCH

22 on the PUSCH


Description

23 on the PUSCH
1526734117 L.UL.RSRP.PUCC Number of times the BTS3900:

0 on the PUCCH

1 on the PUCCH

2 on the PUCCH

3 on the PUCCH

4 on the PUCCH

5 on the PUCCH

6 on the PUCCH


Description

7 on the PUCCH

8 on the PUCCH

9 on the PUCCH

10 on the PUCCH

11 on the PUCCH

12 on the PUCCH

13 on the PUCCH

14 on the PUCCH


Description

15 on the PUCCH

16 on the PUCCH

17 on the PUCCH

18 on the PUCCH

19 on the PUCCH

20 on the PUCCH

21 on the PUCCH

22 on the PUCCH


Description

23 on the PUCCH
None
1.16.1 Downlink Transmit Power
Counters
1526727388 L.DLPwr.Max Maximum BTS3900, L

downlink BTS3900 LTE
transmit power
in a cell
1526727389 L.DLPwr.Avg Average BTS3900, L

downlink BTS3900 LTE
transmit power
in a cell
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 and combination cells, the average downlink transmit power
of all physical cells is sampled.
Formula
None

Unit
dBm
Related Features
L.DLPwr.Max Multi-mode: None

GSM: None
UMTS: None
LOFD-070205 Adaptive SFN/SDMA
L.DLPwr.Avg Multi-mode: None

GSM: None
UMTS: None
1.16.2 Interference and Noise Received by Each PRB in a Cell

Counters
1526728297 L.UL.Interferen Maximum BTS3900, L

ce.Max uplink BTS3900 LTE
interference and
noise received
by each PRB in
a cell
1526728298 L.UL.Interferen Average uplink BTS3900, L

ce.Avg interference and BTS3900 LTE
noise received
by each PRB in
a cell
1526728435 L.UL.Interferen Minimum BTS3900, L

ce.Min uplink BTS3900 LTE
interference and
noise received
by each PRB in
a cell

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
L.UL.Interference.Max Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002003 Physical Channel
LOFD-070205 Physical Channel
Management
Adaptive SFN/SDMA
L.UL.Interference.Avg Multi-mode: None

GSM: None
UMTS: None
Management
Adaptive SFN/SDMA

L.UL.Interference.Min Multi-mode: None

GSM: None
UMTS: None
Management
Adaptive SFN/SDMA
1.16.3 Receive Power of interference and noise detected of each

PRB in the UL UpPTS
Counters
1526728769 L.UpPTS.Interf Power of BTS3900, L

erence.Avg interference and BTS3900 LTE
noise detected
in each PRB in
the UL UpPTS.
Description
Power of interference and noise detected in each PRB in the UL UpPTS.
The L.UpPTS.Interference.Avg counter applies only to LTE TDD.
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
L.UpPTS.Interference.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: TDLBFD-002003 Physical Channel
Management
1.16.4 Receive Power of the first Symbol in First UL Subframe

Counters
1526728770 L.UL.FirstUL0. This counter BTS3900, L

Pwr indicates the BTS3900 LTE
receive power
of the first
symbol in the
first UL
subframe.
Description
This counter indicates the receive power of the first symbol in the first UL subframe.
The L.UL.FirstUL0.Pwr counter applies only to LTE TDD.
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
L.UL.FirstUL0.Pwr Multi-mode: None

GSM: None
UMTS: None
Management
1.16.5 Receive Power of the seventh (or fifth) Symbol in First UL

Subframe
Counters
1526728771 L.UL.FirstUL6( This counter BTS3900, L

4).Pwr indicates the BTS3900 LTE
receive power
of the seventh
(or fifth)
symbol in the
first UL
subframe.
Description
This counter indicates the receive power of the seventh (or fifth) symbol in the first UL
subframe.
The L.UL.FirstUL6(4).Pwr counter applies only to LTE TDD.
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
L.UL.FirstUL6(4).Pwr Multi-mode: None

GSM: None
UMTS: None
Management
1.16.6 Receive Power of the first Symbol in Last UL Subframe

Counters
1526728772 L.UL.LastUL0. This counter BTS3900, L

Pwr indicates the BTS3900 LTE
receive power
of the first
symbol in the
last UL
subframe.
Description
This counter indicates the receive power of the first symbol in the last UL subframe.
The L.UL.LastUL0.Pwr counter applies only to LTE TDD.
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
L.UL.LastUL0.Pwr Multi-mode: None

GSM: None
UMTS: None
Management
1.16.7 Receive Power of the twelfth (or tenth) Symbol in the Last
UL Subframe
Counters
1526728773 L.UL.LastUL1 This counter BTS3900, L

1(9).Pwr indicates the BTS3900 LTE
receive power
of the twelfth
(or tenth)
symbol in the
last UL
subframe.
Description
This counter indicates the receive power of the twelfth (or tenth) symbol in the last UL
subframe.
The L.UL.LastUL0.Pwr counter applies only to LTE TDD.
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
L.UL.LastUL11(9).Pwr Multi-mode: None

GSM: None
UMTS: None
Management
1.16.8 Distribution of RSSIs on the PUCCH

Counters
1526732045 L.UL.RSSI.PU Number of BTS3900, L

CCH.Index0 times the BTS3900 LTE
eNodeB detects
a PRB-level
average RSSI
ranging within
index 0 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 1 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 2 on the
PUCCH



eNodeB detects
a PRB-level
average RSSI
ranging within
index 3 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 4 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 5 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 6 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 7 on the
PUCCH



eNodeB detects
a PRB-level
average RSSI
ranging within
index 8 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 9 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 10 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 11 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 12 on the
PUCCH



eNodeB detects
a PRB-level
average RSSI
ranging within
index 13 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 14 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 15 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 16 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 17 on the
PUCCH



eNodeB detects
a PRB-level
average RSSI
ranging within
index 18 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 19 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 20 on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 21 on the
PUCCH
Description
The counters measure the RSSI on the PUCCH in a cell. RSSI indexes (0 to 21) are defined as
follows:
Index 0: (RSSI -120 dBm)
Index 1: (-120dBm < RSSI -118 dBm)
Index 5: (-112dBm < RSSI-110 dBm)


Index 21: (RSSI > -80 dBm)
Measurement Points
The total RSSI on the PUCCH is sampled per 10 ms. The eNodeB divides the total RSSI by
the number of PUCCH PRBs, maps the average RSSI to an index, and increases the counter
with this index by 1. For an SFN cell, values of counters with the same index in physical cells
are accumulated. Because of the implementation mechanism, a deviation may be generated
when different modules perform time synchronization. As a result, a deviation may also be
generated in the values of these counters. However, the deviation does not affect the
distribution of RSSIs on the PUCCH.
Formula
None
Unit
None

Related Features
L.UL.RSSI.PUCCH.Index0 Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management


GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management


0 GSM: None
UMTS: None
Physical Channel
Management

1 GSM: None
UMTS: None
Physical Channel
Management

2 GSM: None
UMTS: None
Physical Channel
Management

3 GSM: None
UMTS: None
Physical Channel
Management

4 GSM: None
UMTS: None
Physical Channel
Management


5 GSM: None
UMTS: None
Physical Channel
Management

6 GSM: None
UMTS: None
Physical Channel
Management

7 GSM: None
UMTS: None
Physical Channel
Management

8 GSM: None
UMTS: None
Physical Channel
Management

9 GSM: None
UMTS: None
Physical Channel
Management


0 GSM: None
UMTS: None
Physical Channel
Management

1 GSM: None
UMTS: None
Physical Channel
Management
1.16.9 Distribution of RSSIs on the PUSCH

Counters

SCH.Index0 times the BTS3900 LTE
eNodeB detects
a PRB-level
average RSSI
ranging within
index 0 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 1 on the
PUSCH



eNodeB detects
a PRB-level
average RSSI
ranging within
index 2 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 3 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 4 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 5 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 6 on the
PUSCH



eNodeB detects
a PRB-level
average RSSI
ranging within
index 7 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 8 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 9 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 10 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 11 on the
PUSCH



eNodeB detects
a PRB-level
average RSSI
ranging within
index 12 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 13 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 14 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 15 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 16 on the
PUSCH



eNodeB detects
a PRB-level
average RSSI
ranging within
index 17 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 18 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 19 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 20 on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
ranging within
index 21 on the
PUSCH
Description
The counters measure the RSSI on the PUSCH in a cell. RSSI indexes (0 to 21) are defined as
follows:

Index 0: (RSSI -120 dBm)

Index 1: (-120 dBm < RSSI -118 dBm)
Index 21: (RSSI > -80 dBm)
Measurement Points
The total RSSI on the PUSCH is sampled per 10 ms. The eNodeB divides the total RSSI by
the number of PUSCH PRBs, maps the average RSSI to an index, and increases the counter
with this index by 1. For an SFN cell, values of counters with the same index in physical cells
are accumulated. Because of the implementation mechanism, a deviation may be generated
when different modules perform time synchronization. As a result, a deviation may also be
distribution of RSSIs on the PUSCH.
Formula
None
Unit
None

Related Features
L.UL.RSSI.PUSCH.Index0 Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management


GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management


GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management


GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management


GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management
1.16.10 Distribution of INs on the PUSCH
Counters
1526734045 L.UL.Interferen Number of BTS3900, L

ce.PUSCH.Inde times the BTS3900 LTE
x0 eNodeB detects
a PRB-level IN
ranging within
index 0 on the
PUSCH

x1 eNodeB detects
a PRB-level IN
ranging within
index 1 on the
PUSCH

x2 eNodeB detects
a PRB-level IN
ranging within
index 2 on the
PUSCH



x3 eNodeB detects
a PRB-level IN
ranging within
index 3 on the
PUSCH

x4 eNodeB detects
a PRB-level IN
ranging within
index 4 on the
PUSCH

x5 eNodeB detects
a PRB-level IN
ranging within
index 5 on the
PUSCH

x6 eNodeB detects
a PRB-level IN
ranging within
index 6 on the
PUSCH

x7 eNodeB detects
a PRB-level IN
ranging within
index 7 on the
PUSCH

x8 eNodeB detects
a PRB-level IN
ranging within
index 8 on the
PUSCH



x9 eNodeB detects
a PRB-level IN
ranging within
index 9 on the
PUSCH

x10 eNodeB detects
a PRB-level IN
ranging within
index 10 on the
PUSCH

x11 eNodeB detects
a PRB-level IN
ranging within
index 11 on the
PUSCH

x12 eNodeB detects
a PRB-level IN
ranging within
index 12 on the
PUSCH

x13 eNodeB detects
a PRB-level IN
ranging within
index 13 on the
PUSCH

x14 eNodeB detects
a PRB-level IN
ranging within
index 14 on the
PUSCH



x15 eNodeB detects
a PRB-level IN
ranging within
index 15 on the
PUSCH
Description
The counters measure the interference noise (IN) on the PUSCH in a cell. IN indexes (0 to 15)
are defined as follows:
Index 0: (IN -121dBm)
Index 1: (-121 dBm < IN -120 dBm)
Index 2: (-120 dBm < IN -119 dBm)
Index 3: (-119 dBm < IN -118 dBm)
Index 4: (-118 dBm < IN -117 dBm)
Index 5: (-117 dBm < N -116 dBm)
Index 6: (-116 dBm < IN -115 dBm)
Index 7: (-115 dBm < IN -114 dBm)
Index 8: (-114 dBm < IN -113 dBm)
Index 9: (-113 dBm < IN -112 dBm)
Index 10: (-112 dBm < IN -108 dBm)
Index 11: (-108 dBm < IN -104 dBm)
Index 12: (-104 dBm < IN -100 dBm)
Index 13: (-100 dBm < IN -96 dBm)
Index 14: (-96 dBm < IN -92 dBm)
Index 15: (IN > -92 dBm)
Measurement Points
The IN of each PRB on the PUSCH is sampled per 10 ms. The eNodeB maps the IN to an
index and increases the counter with this index by 1. For an SFN cell, values of counters with
the same index in physical cells are accumulated.Because of the implementation mechanism,
a deviation may be generated when different modules perform time synchronization. As a
result, a deviation may also be generated in the values of these counters. However, the
deviation does not affect the distribution of INs on the PUSCH.

Formula
None
Unit
None
Related Features
L.UL.Interference.PUSCH.I Multi-mode: None

ndex0 GSM: None
UMTS: None
Physical Channel
Management

ndex1 GSM: None
UMTS: None
Physical Channel
Management

ndex2 GSM: None
UMTS: None
Physical Channel
Management

ndex3 GSM: None
UMTS: None
Physical Channel
Management


ndex4 GSM: None
UMTS: None
Physical Channel
Management

ndex5 GSM: None
UMTS: None
Physical Channel
Management

ndex6 GSM: None
UMTS: None
Physical Channel
Management

ndex7 GSM: None
UMTS: None
Physical Channel
Management

ndex8 GSM: None
UMTS: None
Physical Channel
Management


ndex9 GSM: None
UMTS: None
Physical Channel
Management

ndex10 GSM: None
UMTS: None
Physical Channel
Management

ndex11 GSM: None
UMTS: None
Physical Channel
Management

ndex12 GSM: None
UMTS: None
Physical Channel
Management

ndex13 GSM: None
UMTS: None
Physical Channel
Management


ndex14 GSM: None
UMTS: None
Physical Channel
Management

ndex15 GSM: None
UMTS: None
Physical Channel
Management
1.16.11 Distribution of INs on the PUCCH
Counters

ce.PUCCH.Inde times the BTS3900 LTE
x0 eNodeB detects
a PRB-level IN
ranging within
index 0 on the
PUCCH

x1 eNodeB detects
a PRB-level IN
ranging within
index 1 on the
PUCCH

x2 eNodeB detects
a PRB-level IN
ranging within
index 2 on the
PUCCH



x3 eNodeB detects
a PRB-level IN
ranging within
index 3 on the
PUCCH

x4 eNodeB detects
a PRB-level IN
ranging within
index 4 on the
PUCCH

x5 eNodeB detects
a PRB-level IN
ranging within
index 5 on the
PUCCH

x6 eNodeB detects
a PRB-level IN
ranging within
index 6 on the
PUCCH

x7 eNodeB detects
a PRB-level IN
ranging within
index 7 on the
PUCCH

x8 eNodeB detects
a PRB-level IN
ranging within
index 8 on the
PUCCH



x9 eNodeB detects
a PRB-level IN
ranging within
index 9 on the
PUCCH

x10 eNodeB detects
a PRB-level IN
ranging within
index 10 on the
PUCCH

x11 eNodeB detects
a PRB-level IN
ranging within
index 11 on the
PUCCH

x12 eNodeB detects
a PRB-level IN
ranging within
index 12 on the
PUCCH

x13 eNodeB detects
a PRB-level IN
ranging within
index 13 on the
PUCCH

x14 eNodeB detects
a PRB-level IN
ranging within
index 14 on the
PUCCH



x15 eNodeB detects
a PRB-level IN
ranging within
index 15 on the
PUCCH
Description
The counters measure the interference noise (IN) on the PUCCH in a cell. IN indexes (0 to
15) are defined as follows:
Index 0: (IN -121 dBm)
Index 1: (-121 dBm < IN -120 dBm)
Index 2: (-120 dBm < IN -119 dBm)
Index 3: (-119 dBm < IN -118 dBm)
Index 4: (-118 dBm < IN -117 dBm)
Index 5: (-117 dBm < IN -116 dBm)
Index 6: (-116 dBm < IN -115 dBm)
Index 7: (-115 dBm < IN -114 dBm)
Index 8: (-114 dBm < IN -113 dBm)
Index 9: (-113 dBm < IN -112 dBm)
Index 10: (-112 dBm < IN -108 dBm)
Index 11: (-108 dBm < IN -104 dBm)
Index 12: (-104 dBm < IN -100 dBm)
Index 13: (-100 dBm < IN -96 dBm)
Index 14: (-9 6dBm < IN -92 dBm)
Measurement Points
PRB-level INs on the PUCCH can be classified into idle type, format 1 type, and format 2
type. Different types of PRB-level INs are measured in different methods. The IN of each
PRB, which can be measured, on the PUCCH is sampled per 10 ms. The eNodeB maps the IN
to an index and increases the counter with this index by 1. For an SFN cell, values of counters
with the same index in physical cells are accumulated. Because of the implementation
mechanism, a deviation may be generated when different modules perform time

synchronization. As a result, a deviation may also be generated in the values of these

counters. However, the deviation does not affect the distribution of INs on the PUCCH.
Formula
None
Unit
None
Related Features
L.UL.Interference.PUCCH.I Multi-mode: None

ndex0 GSM: None
UMTS: None
LBFD-002003 Physical Channel
Physical Channel
Management

ndex1 GSM: None
UMTS: None
Physical Channel
Management

ndex2 GSM: None
UMTS: None
Physical Channel
Management


ndex3 GSM: None
UMTS: None
Physical Channel
Management

ndex4 GSM: None
UMTS: None
Physical Channel
Management

ndex5 GSM: None
UMTS: None
Physical Channel
Management

ndex6 GSM: None
UMTS: None
Physical Channel
Management

ndex7 GSM: None
UMTS: None
Physical Channel
Management


ndex8 GSM: None
UMTS: None
Physical Channel
Management

ndex9 GSM: None
UMTS: None
Physical Channel
Management

ndex10 GSM: None
UMTS: None
Physical Channel
Management

ndex11 GSM: None
UMTS: None
Physical Channel
Management

ndex12 GSM: None
UMTS: None
Physical Channel
Management


ndex13 GSM: None
UMTS: None
Physical Channel
Management

ndex14 GSM: None
UMTS: None
Physical Channel
Management

ndex15 GSM: None
UMTS: None
Physical Channel
Management
1.16.12 Distribution of INs on the PRACH

Counters

ce.PRACH.Inde times the BTS3900 LTE
x0 eNodeB detects
a PRB-level IN
ranging within
index 0 on the
PRACH



x1 eNodeB detects
a PRB-level IN
ranging within
index 1 on the
PRACH

x2 eNodeB detects
a PRB-level IN
ranging within
index 2 on the
PRACH

x3 eNodeB detects
a PRB-level IN
ranging within
index 3 on the
PRACH

x4 eNodeB detects
a PRB-level IN
ranging within
index 4 on the
PRACH

x5 eNodeB detects
a PRB-level IN
ranging within
index 5 on the
PRACH

x6 eNodeB detects
a PRB-level IN
ranging within
index 6 on the
PRACH



x7 eNodeB detects
a PRB-level IN
ranging within
index 7 on the
PRACH

x8 eNodeB detects
a PRB-level IN
ranging within
index 8 on the
PRACH

x9 eNodeB detects
a PRB-level IN
ranging within
index 9 on the
PRACH

x10 eNodeB detects
a PRB-level IN
ranging within
index 10 on the
PRACH

x11 eNodeB detects
a PRB-level IN
ranging within
index 11 on the
PRACH

x12 eNodeB detects
a PRB-level IN
ranging within
index 12 on the
PRACH



x13 eNodeB detects
a PRB-level IN
ranging within
index 13 on the
PRACH

x14 eNodeB detects
a PRB-level IN
ranging within
index 14 on the
PRACH

x15 eNodeB detects
a PRB-level IN
ranging within
index 15 on the
PRACH
Description
The counters measure the interference noise (IN) on the PRACH in a cell. IN indexes (0 to
15) are defined as follows:
Index 0: (IN -121dBm)
Index 1: (-121 dBm < IN -120 dBm)
Index 2: (-120 dBm < IN -119 dBm)
Index 3: (-119 dBm < IN -118 dBm)
Index 4: (-118 dBm < IN -117 dBm)
Index 5: (-117 dBm < IN -116 dBm)
Index 6: (-116 dBm < IN -115 dBm)
Index 7: (-115 dBm < IN -114 dBm)
Index 8: (-114 dBm < IN -113 dBm)
Index 9: (-113 dBm < IN -112 dBm)
Index 10: (-112 dBm < IN -108 dBm)
Index 11: (-108 dBm < IN -104 dBm)
Index 12: (-104 dBm < IN -100 dBm)

Index 13: (-100 dBm < IN -96 dBm)

Index 14: (-96 dBm < IN -92 dBm)
Measurement Points
The total IN on the PRACH is sampled per TTI. The eNodeB divides the total IN by the
number of PARCH PRBs, maps the average IN to an index, and increases the counter with
this index by 1. For an SFN cell, values of counters with the same index in physical cells are
accumulated. Because of the implementation mechanism, a deviation may be generated when
different modules perform time synchronization. As a result, a deviation may also be
distribution of INs on the PRACH.
Formula
None
Unit
None
Related Features
L.UL.Interference.PRACH.I Multi-mode: None

ndex0 GSM: None
UMTS: None
Physical Channel
Management

ndex1 GSM: None
UMTS: None
Physical Channel
Management


ndex2 GSM: None
UMTS: None
Physical Channel
Management

ndex3 GSM: None
UMTS: None
Physical Channel
Management

ndex4 GSM: None
UMTS: None
Physical Channel
Management

ndex5 GSM: None
UMTS: None
Physical Channel
Management

ndex6 GSM: None
UMTS: None
Physical Channel
Management


ndex7 GSM: None
UMTS: None
Physical Channel
Management

ndex8 GSM: None
UMTS: None
Physical Channel
Management

ndex9 GSM: None
UMTS: None
Physical Channel
Management

ndex10 GSM: None
UMTS: None
Physical Channel
Management

ndex11 GSM: None
UMTS: None
Physical Channel
Management


ndex12 GSM: None
UMTS: None
Physical Channel
Management

ndex13 GSM: None
UMTS: None
Physical Channel
Management

ndex14 GSM: None
UMTS: None
Physical Channel
Management

ndex15 GSM: None
UMTS: None
Physical Channel
Management

1.16.13 Distribution of RSRPs on the PUSCH
Counters
1526734093 L.UL.RSRP.PU Number of BTS3900, L

eNodeB detects
a UE-level
RSRP ranging
within index 0
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 1
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 2
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 3
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 4
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 5
on the PUSCH



eNodeB detects
a UE-level
RSRP ranging
within index 6
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 7
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 8
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 9
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 10
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 11
on the PUSCH



eNodeB detects
a UE-level
RSRP ranging
within index 12
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 13
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 14
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 15
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 16
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 17
on the PUSCH



eNodeB detects
a UE-level
RSRP ranging
within index 18
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 19
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 20
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 21
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 22
on the PUSCH

eNodeB detects
a UE-level
RSRP ranging
within index 23
on the PUSCH

Description
The counters measure the RSRP on the PUSCH in a cell. RSRP indexes (0 to 23) are defined
as follows:
Index 0: (RSRP -146 dBm)
Index 1: (-146 dBm < RSRP -144 dBm)
Index 23: (RSRP > -90 dBm)
Measurement Points
The RSRP of each UE on the PUSCH is sampled per 10 ms. The eNodeB maps the RSRP to
an index and increases the counter with this index by 1. For an SFN cell, values of counters
with the same index in physical cells are accumulated. Because of the implementation
mechanism, a deviation may be generated when different modules perform time
synchronization. As a result, a deviation may also be generated in the values of these
counters. However, the deviation does not affect the distribution of RSRPs on the PUSCH.

Formula
None
Unit
None
Related Features
L.UL.RSRP.PUSCH.Index0 Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management


GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management


GSM: None
UMTS: None
Physical Channel
Management

0 GSM: None
UMTS: None
Physical Channel
Management

1 GSM: None
UMTS: None
Physical Channel
Management

2 GSM: None
UMTS: None
Physical Channel
Management

3 GSM: None
UMTS: None
Physical Channel
Management


4 GSM: None
UMTS: None
Physical Channel
Management

5 GSM: None
UMTS: None
Physical Channel
Management

6 GSM: None
UMTS: None
Physical Channel
Management

7 GSM: None
UMTS: None
Physical Channel
Management

8 GSM: None
UMTS: None
Physical Channel
Management


9 GSM: None
UMTS: None
Physical Channel
Management

0 GSM: None
UMTS: None
Physical Channel
Management

1 GSM: None
UMTS: None
Physical Channel
Management

2 GSM: None
UMTS: None
Physical Channel
Management

3 GSM: None
UMTS: None
Physical Channel
Management

1.16.14 Distribution of RSRPs on the PUCCH
Counters

eNodeB detects
a UE-level
RSRP ranging
within index 0
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 1
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 2
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 3
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 4
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 5
on the PUCCH



eNodeB detects
a UE-level
RSRP ranging
within index 6
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 7
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 8
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 9
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 10
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 11
on the PUCCH



eNodeB detects
a UE-level
RSRP ranging
within index 12
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 13
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 14
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 15
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 16
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 17
on the PUCCH



eNodeB detects
a UE-level
RSRP ranging
within index 18
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 19
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 20
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 21
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 22
on the PUCCH

eNodeB detects
a UE-level
RSRP ranging
within index 23
on the PUCCH

Description
The counters measure the RSRP on the PUCCH in a cell. RSRP indexes (0 to 23) are defined
as follows:
Index 0: (RSRP -146dBm)
Index 23: (RSRP > -90 dBm)
Measurement Points
The RSRP of each UE on the PUCCH is sampled per 10 ms. If a UE (including the DTX UE)
has multiple code channels, the RSRP of this UE on the PUCCH is sampled at the code
channel where the final demodulation result is transmitted. The eNodeB maps the RSRP of
each UE to an index and increases the counter with this index by 1. For an SFN cell, values of
counters with the same index in physical cells are accumulated. Because of the
implementation mechanism, a deviation may be generated when different modules perform
time synchronization. As a result, a deviation may also be generated in the values of these
counters. However, the deviation does not affect the distribution of RSRPs on the PUCCH.

Formula
None
Unit
None
Related Features
L.UL.RSRP.PUCCH.Index0 Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management


GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management

GSM: None
UMTS: None
Physical Channel
Management


GSM: None
UMTS: None
Physical Channel
Management

0 GSM: None
UMTS: None
Physical Channel
Management

1 GSM: None
UMTS: None
Physical Channel
Management

2 GSM: None
UMTS: None
Physical Channel
Management

3 GSM: None
UMTS: None
Physical Channel
Management


4 GSM: None
UMTS: None
Physical Channel
Management

5 GSM: None
UMTS: None
Physical Channel
Management

6 GSM: None
UMTS: None
Physical Channel
Management

7 GSM: None
UMTS: None
Physical Channel
Management

8 GSM: None
UMTS: None
Physical Channel
Management


9 GSM: None
UMTS: None
Physical Channel
Management

0 GSM: None
UMTS: None
Physical Channel
Management

1 GSM: None
UMTS: None
Physical Channel
Management

2 GSM: None
UMTS: None
Physical Channel
Management

3 GSM: None
UMTS: None
Physical Channel
Management

1.17 Channel Quality Measurement1 (ChMeas.Pwr1.Cell)

Overview
The ChMeas.Pwr1.Cell function subset measures the power in a cell to analyze the overall
quality of the downlink channel.
Counters
Description
1526730620 L.UL.Interference. Average interference BTS3900:

Avg.PRB0 and noise received V100R009C00
by PRB 0 in a cell BTS3900 LTE:
V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00


Description

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00


Description

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00


Description

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00


Description

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00


Description

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00


Description

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00


Description

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00


Description

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00


Description

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00

V100R009C00


Description

V100R009C00

V100R009C00
1526730720 L.UL.Interference. Maximum BTS3900:

Max.PRB0 interference and V100R009C00
PRB 0 in a cell V100R009C00









Description












Description












Description












Description












Description












Description












Description












Description












Description












Description


None
1.17.1 Average Interference and Noise Received by Each PRB in a

Cell
Counters
1526730620 L.UL.Interferen Average BTS3900, L

ce.Avg.PRB0 interference and BTS3900 LTE
noise received
by PRB 0 in a
cell

noise received
by PRB 1 in a
cell

noise received
by PRB 2 in a
cell

noise received
by PRB 3 in a
cell



noise received
by PRB 4 in a
cell

noise received
by PRB 5 in a
cell

noise received
by PRB 6 in a
cell

noise received
by PRB 7 in a
cell

noise received
by PRB 8 in a
cell

noise received
by PRB 9 in a
cell

noise received
by PRB 10 in a
cell

noise received
by PRB 11 in a
cell



noise received
by PRB 12 in a
cell

noise received
by PRB 13 in a
cell

noise received
by PRB 14 in a
cell

noise received
by PRB 15 in a
cell

noise received
by PRB 16 in a
cell

noise received
by PRB 17 in a
cell

noise received
by PRB 18 in a
cell

noise received
by PRB 19 in a
cell



noise received
by PRB 20 in a
cell

noise received
by PRB 21 in a
cell

noise received
by PRB 22 in a
cell

noise received
by PRB 23 in a
cell

noise received
by PRB 24 in a
cell

noise received
by PRB 25 in a
cell

noise received
by PRB 26 in a
cell

noise received
by PRB 27 in a
cell



noise received
by PRB 28 in a
cell

noise received
by PRB 29 in a
cell

noise received
by PRB 30 in a
cell

noise received
by PRB 31 in a
cell

noise received
by PRB 32 in a
cell

noise received
by PRB 33 in a
cell

noise received
by PRB 34 in a
cell

noise received
by PRB 35 in a
cell



noise received
by PRB 36 in a
cell

noise received
by PRB 37 in a
cell

noise received
by PRB 38 in a
cell

noise received
by PRB 39 in a
cell

noise received
by PRB 40 in a
cell

noise received
by PRB 41 in a
cell

noise received
by PRB 42 in a
cell

noise received
by PRB 43 in a
cell



noise received
by PRB 44 in a
cell

noise received
by PRB 45 in a
cell

noise received
by PRB 46 in a
cell

noise received
by PRB 47 in a
cell

noise received
by PRB 48 in a
cell

noise received
by PRB 49 in a
cell

noise received
by PRB 50 in a
cell

noise received
by PRB 51 in a
cell



noise received
by PRB 52 in a
cell

noise received
by PRB 53 in a
cell

noise received
by PRB 54 in a
cell

noise received
by PRB 55 in a
cell

noise received
by PRB 56 in a
cell

noise received
by PRB 57 in a
cell

noise received
by PRB 58 in a
cell

noise received
by PRB 59 in a
cell



noise received
by PRB 60 in a
cell

noise received
by PRB 61 in a
cell

noise received
by PRB 62 in a
cell

noise received
by PRB 63 in a
cell

noise received
by PRB 64 in a
cell

noise received
by PRB 65 in a
cell

noise received
by PRB 66 in a
cell

noise received
by PRB 67 in a
cell



noise received
by PRB 68 in a
cell

noise received
by PRB 69 in a
cell

noise received
by PRB 70 in a
cell

noise received
by PRB 71 in a
cell

noise received
by PRB 72 in a
cell

noise received
by PRB 73 in a
cell

noise received
by PRB 74 in a
cell

noise received
by PRB 75 in a
cell



noise received
by PRB 76 in a
cell

noise received
by PRB 77 in a
cell

noise received
by PRB 78 in a
cell

noise received
by PRB 79 in a
cell

noise received
by PRB 80 in a
cell

noise received
by PRB 81 in a
cell

noise received
by PRB 82 in a
cell

noise received
by PRB 83 in a
cell



noise received
by PRB 84 in a
cell

noise received
by PRB 85 in a
cell

noise received
by PRB 86 in a
cell

noise received
by PRB 87 in a
cell

noise received
by PRB 88 in a
cell

noise received
by PRB 89 in a
cell

noise received
by PRB 90 in a
cell

noise received
by PRB 91 in a
cell



noise received
by PRB 92 in a
cell

noise received
by PRB 93 in a
cell

noise received
by PRB 94 in a
cell

noise received
by PRB 95 in a
cell

noise received
by PRB 96 in a
cell

noise received
by PRB 97 in a
cell

noise received
by PRB 98 in a
cell

noise received
by PRB 99 in a
cell

Description
The counters measure the average interference and noise received by each uplink PRB in a
cell.
Measurement Points
The eNodeB measures the interference and noise from neighboring cells received by each
uplink PRB in a cell (or all physical cells that constitute an SFN cell or combination cell) and
calculates the average value as a sample per second. At the end of a measurement period, the
average of the sampling results is used as the average interference and noise received by the
PRB.
The measured value of the counter is incorrect because the internal timer of the eNodeB has a
deviation of one period.
Formula
None
Unit
dBm
Related Features
L.UL.Interference.Avg.PRB Multi-mode: None

0 GSM: None
UMTS: None
Physical Channel
Management

1 GSM: None
UMTS: None
Physical Channel
Management


2 GSM: None
UMTS: None
Physical Channel
Management

3 GSM: None
UMTS: None
Physical Channel
Management

4 GSM: None
UMTS: None
Physical Channel
Management

5 GSM: None
UMTS: None
Physical Channel
Management

6 GSM: None
UMTS: None
Physical Channel
Management


7 GSM: None
UMTS: None
Physical Channel
Management

8 GSM: None
UMTS: None
Physical Channel
Management

9 GSM: None
UMTS: None
Physical Channel
Management

10 GSM: None
UMTS: None
Physical Channel
Management

11 GSM: None
UMTS: None
Physical Channel
Management


12 GSM: None
UMTS: None
Physical Channel
Management

13 GSM: None
UMTS: None
Physical Channel
Management

14 GSM: None
UMTS: None
Physical Channel
Management

15 GSM: None
UMTS: None
Physical Channel
Management

16 GSM: None
UMTS: None
Physical Channel
Management


17 GSM: None
UMTS: None
Physical Channel
Management

18 GSM: None
UMTS: None
Physical Channel
Management

19 GSM: None
UMTS: None
Physical Channel
Management

20 GSM: None
UMTS: None
Physical Channel
Management

21 GSM: None
UMTS: None
Physical Channel
Management


22 GSM: None
UMTS: None
Physical Channel
Management

23 GSM: None
UMTS: None
Physical Channel
Management

24 GSM: None
UMTS: None
Physical Channel
Management

25 GSM: None
UMTS: None
Physical Channel
Management

26 GSM: None
UMTS: None
Physical Channel
Management


27 GSM: None
UMTS: None
Physical Channel
Management

28 GSM: None
UMTS: None
Physical Channel
Management

29 GSM: None
UMTS: None
Physical Channel
Management

30 GSM: None
UMTS: None
Physical Channel
Management

31 GSM: None
UMTS: None
Physical Channel
Management


32 GSM: None
UMTS: None
Physical Channel
Management

33 GSM: None
UMTS: None
Physical Channel
Management

34 GSM: None
UMTS: None
Physical Channel
Management

35 GSM: None
UMTS: None
Physical Channel
Management

36 GSM: None
UMTS: None
Physical Channel
Management


37 GSM: None
UMTS: None
Physical Channel
Management

38 GSM: None
UMTS: None
Physical Channel
Management

39 GSM: None
UMTS: None
Physical Channel
Management

40 GSM: None
UMTS: None
Physical Channel
Management

41 GSM: None
UMTS: None
Physical Channel
Management


42 GSM: None
UMTS: None
Physical Channel
Management

43 GSM: None
UMTS: None
Physical Channel
Management

44 GSM: None
UMTS: None
Physical Channel
Management

45 GSM: None
UMTS: None
Physical Channel
Management

46 GSM: None
UMTS: None
Physical Channel
Management


47 GSM: None
UMTS: None
Physical Channel
Management

48 GSM: None
UMTS: None
Physical Channel
Management

49 GSM: None
UMTS: None
Physical Channel
Management

50 GSM: None
UMTS: None
Physical Channel
Management

51 GSM: None
UMTS: None
Physical Channel
Management


52 GSM: None
UMTS: None
Physical Channel
Management

53 GSM: None
UMTS: None
Physical Channel
Management

54 GSM: None
UMTS: None
Physical Channel
Management

55 GSM: None
UMTS: None
Physical Channel
Management

56 GSM: None
UMTS: None
Physical Channel
Management


57 GSM: None
UMTS: None
Physical Channel
Management

58 GSM: None
UMTS: None
Physical Channel
Management

59 GSM: None
UMTS: None
Physical Channel
Management

60 GSM: None
UMTS: None
Physical Channel
Management

61 GSM: None
UMTS: None
Physical Channel
Management


62 GSM: None
UMTS: None
Physical Channel
Management

63 GSM: None
UMTS: None
Physical Channel
Management

64 GSM: None
UMTS: None
Physical Channel
Management

65 GSM: None
UMTS: None
Physical Channel
Management

66 GSM: None
UMTS: None
Physical Channel
Management


67 GSM: None
UMTS: None
Physical Channel
Management

68 GSM: None
UMTS: None
Physical Channel
Management

69 GSM: None
UMTS: None
Physical Channel
Management

70 GSM: None
UMTS: None
Physical Channel
Management

71 GSM: None
UMTS: None
Physical Channel
Management


72 GSM: None
UMTS: None
Physical Channel
Management

73 GSM: None
UMTS: None
Physical Channel
Management

74 GSM: None
UMTS: None
Physical Channel
Management

75 GSM: None
UMTS: None
Physical Channel
Management

76 GSM: None
UMTS: None
Physical Channel
Management


77 GSM: None
UMTS: None
Physical Channel
Management

78 GSM: None
UMTS: None
Physical Channel
Management

79 GSM: None
UMTS: None
Physical Channel
Management

80 GSM: None
UMTS: None
Physical Channel
Management

81 GSM: None
UMTS: None
Physical Channel
Management


82 GSM: None
UMTS: None
Physical Channel
Management

83 GSM: None
UMTS: None
Physical Channel
Management

84 GSM: None
UMTS: None
Physical Channel
Management

85 GSM: None
UMTS: None
Physical Channel
Management

86 GSM: None
UMTS: None
Physical Channel
Management


87 GSM: None
UMTS: None
Physical Channel
Management

88 GSM: None
UMTS: None
Physical Channel
Management

89 GSM: None
UMTS: None
Physical Channel
Management

90 GSM: None
UMTS: None
Physical Channel
Management

91 GSM: None
UMTS: None
Physical Channel
Management


92 GSM: None
UMTS: None
Physical Channel
Management

93 GSM: None
UMTS: None
Physical Channel
Management

94 GSM: None
UMTS: None
Physical Channel
Management

95 GSM: None
UMTS: None
Physical Channel
Management

96 GSM: None
UMTS: None
Physical Channel
Management


97 GSM: None
UMTS: None
Physical Channel
Management

98 GSM: None
UMTS: None
Physical Channel
Management

99 GSM: None
UMTS: None
Physical Channel
Management
1.17.2 Maximum Interference and Noise Received by Each PRB in

a Cell
Counters

ce.Max.PRB0 interference and BTS3900 LTE
noise received
by PRB 0 in a
cell

noise received
by PRB 1 in a
cell



noise received
by PRB 2 in a
cell

noise received
by PRB 3 in a
cell

noise received
by PRB 4 in a
cell

noise received
by PRB 5 in a
cell

noise received
by PRB 6 in a
cell

noise received
by PRB 7 in a
cell

noise received
by PRB 8 in a
cell

noise received
by PRB 9 in a
cell



noise received
by PRB 10 in a
cell

noise received
by PRB 11 in a
cell

noise received
by PRB 12 in a
cell

noise received
by PRB 13 in a
cell

noise received
by PRB 14 in a
cell

noise received
by PRB 15 in a
cell

noise received
by PRB 16 in a
cell

noise received
by PRB 17 in a
cell



noise received
by PRB 18 in a
cell

noise received
by PRB 19 in a
cell

noise received
by PRB 20 in a
cell

noise received
by PRB 21 in a
cell

noise received
by PRB 22 in a
cell

noise received
by PRB 23 in a
cell

noise received
by PRB 24 in a
cell

noise received
by PRB 25 in a
cell



noise received
by PRB 26 in a
cell

noise received
by PRB 27 in a
cell

noise received
by PRB 28 in a
cell

noise received
by PRB 29 in a
cell

noise received
by PRB 30 in a
cell

noise received
by PRB 31 in a
cell

noise received
by PRB 32 in a
cell

noise received
by PRB 33 in a
cell



noise received
by PRB 34 in a
cell

noise received
by PRB 35 in a
cell

noise received
by PRB 36 in a
cell

noise received
by PRB 37 in a
cell

noise received
by PRB 38 in a
cell

noise received
by PRB 39 in a
cell

noise received
by PRB 40 in a
cell

noise received
by PRB 41 in a
cell



noise received
by PRB 42 in a
cell

noise received
by PRB 43 in a
cell

noise received
by PRB 44 in a
cell

noise received
by PRB 45 in a
cell

noise received
by PRB 46 in a
cell

noise received
by PRB 47 in a
cell

noise received
by PRB 48 in a
cell

noise received
by PRB 49 in a
cell



noise received
by PRB 50 in a
cell

noise received
by PRB 51 in a
cell

noise received
by PRB 52 in a
cell

noise received
by PRB 53 in a
cell

noise received
by PRB 54 in a
cell

noise received
by PRB 55 in a
cell

noise received
by PRB 56 in a
cell

noise received
by PRB 57 in a
cell



noise received
by PRB 58 in a
cell

noise received
by PRB 59 in a
cell

noise received
by PRB 60 in a
cell

noise received
by PRB 61 in a
cell

noise received
by PRB 62 in a
cell

noise received
by PRB 63 in a
cell

noise received
by PRB 64 in a
cell

noise received
by PRB 65 in a
cell



noise received
by PRB 66 in a
cell

noise received
by PRB 67 in a
cell

noise received
by PRB 68 in a
cell

noise received
by PRB 69 in a
cell

noise received
by PRB 70 in a
cell

noise received
by PRB 71 in a
cell

noise received
by PRB 72 in a
cell

noise received
by PRB 73 in a
cell



noise received
by PRB 74 in a
cell

noise received
by PRB 75 in a
cell

noise received
by PRB 76 in a
cell

noise received
by PRB 77 in a
cell

noise received
by PRB 78 in a
cell

noise received
by PRB 79 in a
cell

noise received
by PRB 80 in a
cell

noise received
by PRB 81 in a
cell



noise received
by PRB 82 in a
cell

noise received
by PRB 83 in a
cell

noise received
by PRB 84 in a
cell

noise received
by PRB 85 in a
cell

noise received
by PRB 86 in a
cell

noise received
by PRB 87 in a
cell

noise received
by PRB 88 in a
cell

noise received
by PRB 89 in a
cell



noise received
by PRB 90 in a
cell

noise received
by PRB 91 in a
cell

noise received
by PRB 92 in a
cell

noise received
by PRB 93 in a
cell

noise received
by PRB 94 in a
cell

noise received
by PRB 95 in a
cell

noise received
by PRB 96 in a
cell

noise received
by PRB 97 in a
cell



noise received
by PRB 98 in a
cell

noise received
by PRB 99 in a
cell
Description
The counters measure the maximum interference and noise received by each uplink PRB in a
cell.
Measurement Points
The eNodeB measures the interference and noise from neighboring cells received by each
uplink PRB in a cell (or all physical cells that constitute an SFN cell or combination cell) and
calculates the average value as a sample per second. At the end of a measurement period, the
maximum of the sampling results is used as the maximum interference and noise received by
the PRB. The measured value of the counter is incorrect because the internal timer of the
eNodeB has a deviation of one period.
Formula
None
Unit
dBm
Related Features
L.UL.Interference.Max.PRB Multi-mode: None

0 GSM: None
UMTS: None
Physical Channel
Management


1 GSM: None
UMTS: None
Physical Channel
Management

2 GSM: None
UMTS: None
Physical Channel
Management

3 GSM: None
UMTS: None
Physical Channel
Management

4 GSM: None
UMTS: None
Physical Channel
Management

5 GSM: None
UMTS: None
Physical Channel
Management


6 GSM: None
UMTS: None
Physical Channel
Management

7 GSM: None
UMTS: None
Physical Channel
Management

8 GSM: None
UMTS: None
Physical Channel
Management

9 GSM: None
UMTS: None
Physical Channel
Management

10 GSM: None
UMTS: None
Physical Channel
Management


11 GSM: None
UMTS: None
Physical Channel
Management

12 GSM: None
UMTS: None
Physical Channel
Management

13 GSM: None
UMTS: None
Physical Channel
Management

14 GSM: None
UMTS: None
Physical Channel
Management

15 GSM: None
UMTS: None
Physical Channel
Management


16 GSM: None
UMTS: None
Physical Channel
Management

17 GSM: None
UMTS: None
Physical Channel
Management

18 GSM: None
UMTS: None
Physical Channel
Management

19 GSM: None
UMTS: None
Physical Channel
Management

20 GSM: None
UMTS: None
Physical Channel
Management


21 GSM: None
UMTS: None
Physical Channel
Management

22 GSM: None
UMTS: None
Physical Channel
Management

23 GSM: None
UMTS: None
Physical Channel
Management

24 GSM: None
UMTS: None
Physical Channel
Management

25 GSM: None
UMTS: None
Physical Channel
Management


26 GSM: None
UMTS: None
Physical Channel
Management

27 GSM: None
UMTS: None
Physical Channel
Management

28 GSM: None
UMTS: None
Physical Channel
Management

29 GSM: None
UMTS: None
Physical Channel
Management

30 GSM: None
UMTS: None
Physical Channel
Management


31 GSM: None
UMTS: None
Physical Channel
Management

32 GSM: None
UMTS: None
Physical Channel
Management

33 GSM: None
UMTS: None
Physical Channel
Management

34 GSM: None
UMTS: None
Physical Channel
Management

35 GSM: None
UMTS: None
Physical Channel
Management


36 GSM: None
UMTS: None
Physical Channel
Management

37 GSM: None
UMTS: None
Physical Channel
Management

38 GSM: None
UMTS: None
Physical Channel
Management

39 GSM: None
UMTS: None
Physical Channel
Management

40 GSM: None
UMTS: None
Physical Channel
Management


41 GSM: None
UMTS: None
Physical Channel
Management

42 GSM: None
UMTS: None
Physical Channel
Management

43 GSM: None
UMTS: None
Physical Channel
Management

44 GSM: None
UMTS: None
Physical Channel
Management

45 GSM: None
UMTS: None
Physical Channel
Management


46 GSM: None
UMTS: None
Physical Channel
Management

47 GSM: None
UMTS: None
Physical Channel
Management

48 GSM: None
UMTS: None
Physical Channel
Management

49 GSM: None
UMTS: None
Physical Channel
Management

50 GSM: None
UMTS: None
Physical Channel
Management


51 GSM: None
UMTS: None
Physical Channel
Management

52 GSM: None
UMTS: None
Physical Channel
Management

53 GSM: None
UMTS: None
Physical Channel
Management

54 GSM: None
UMTS: None
Physical Channel
Management

55 GSM: None
UMTS: None
Physical Channel
Management


56 GSM: None
UMTS: None
Physical Channel
Management

57 GSM: None
UMTS: None
Physical Channel
Management

58 GSM: None
UMTS: None
Physical Channel
Management

59 GSM: None
UMTS: None
Physical Channel
Management

60 GSM: None
UMTS: None
Physical Channel
Management


61 GSM: None
UMTS: None
Physical Channel
Management

62 GSM: None
UMTS: None
Physical Channel
Management

63 GSM: None
UMTS: None
Physical Channel
Management

64 GSM: None
UMTS: None
Physical Channel
Management

65 GSM: None
UMTS: None
Physical Channel
Management


66 GSM: None
UMTS: None
Physical Channel
Management

67 GSM: None
UMTS: None
Physical Channel
Management

68 GSM: None
UMTS: None
Physical Channel
Management

69 GSM: None
UMTS: None
Physical Channel
Management

70 GSM: None
UMTS: None
Physical Channel
Management


71 GSM: None
UMTS: None
Physical Channel
Management

72 GSM: None
UMTS: None
Physical Channel
Management

73 GSM: None
UMTS: None
Physical Channel
Management

74 GSM: None
UMTS: None
Physical Channel
Management

75 GSM: None
UMTS: None
Physical Channel
Management


76 GSM: None
UMTS: None
Physical Channel
Management

77 GSM: None
UMTS: None
Physical Channel
Management

78 GSM: None
UMTS: None
Physical Channel
Management

79 GSM: None
UMTS: None
Physical Channel
Management

80 GSM: None
UMTS: None
Physical Channel
Management


81 GSM: None
UMTS: None
Physical Channel
Management

82 GSM: None
UMTS: None
Physical Channel
Management

83 GSM: None
UMTS: None
Physical Channel
Management

84 GSM: None
UMTS: None
Physical Channel
Management

85 GSM: None
UMTS: None
Physical Channel
Management


86 GSM: None
UMTS: None
Physical Channel
Management

87 GSM: None
UMTS: None
Physical Channel
Management

88 GSM: None
UMTS: None
Physical Channel
Management

89 GSM: None
UMTS: None
Physical Channel
Management

90 GSM: None
UMTS: None
Physical Channel
Management


91 GSM: None
UMTS: None
Physical Channel
Management

92 GSM: None
UMTS: None
Physical Channel
Management

93 GSM: None
UMTS: None
Physical Channel
Management

94 GSM: None
UMTS: None
Physical Channel
Management

95 GSM: None
UMTS: None
Physical Channel
Management


96 GSM: None
UMTS: None
Physical Channel
Management

97 GSM: None
UMTS: None
Physical Channel
Management

98 GSM: None
UMTS: None
Physical Channel
Management

99 GSM: None
UMTS: None
Physical Channel
Management
1.18 CQI Measurement (ChMeas.CQI.Cell)

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
Description
1526727396 L.ChMeas.CQI.DL Number of BTS3900:

.0 wideband CQI V100R008C00
reports with the BTS3900 LTE:
value of 0 version earlier than
V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00


Description

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00


Description
1526729319 L.ChMeas.CQI.DL Number of periodic BTS3900:

.SingleCW.Periodic wideband CQI V100R008C00
.0 reports with the BTS3900 LTE:
value of 0 in single- V100R008C00
codeword
transmission

codeword
transmission

codeword
transmission

codeword
transmission

codeword
transmission

codeword
transmission

codeword
transmission


Description

codeword
transmission

codeword
transmission

codeword
transmission

value of 10 in V100R008C00
single-codeword
transmission

single-codeword
transmission

single-codeword
transmission

single-codeword
transmission


Description

single-codeword
transmission

single-codeword
transmission
1526729335 L.ChMeas.CQI.DL Number of aperiodic BTS3900:

.SingleCW.Aperiod wideband CQI V100R008C00
ic.0 reports with the BTS3900 LTE:
codeword
transmission

codeword
transmission

codeword
transmission

codeword
transmission

codeword
transmission


Description

codeword
transmission

codeword
transmission

codeword
transmission

codeword
transmission

codeword
transmission

single-codeword
transmission

single-codeword
transmission


Description

single-codeword
transmission

single-codeword
transmission

single-codeword
transmission

single-codeword
transmission

.DualCW.Code0.Pe wideband CQI V100R008C00
riodic.0 reports with the BTS3900 LTE:
value of 0 for V100R008C00
codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission


Description

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission


Description

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission


Description

codeword 0 in dual-
codeword
transmission

.DualCW.Code0.A wideband CQI V100R008C00
periodic.0 reports with the BTS3900 LTE:
codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission


Description

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission


Description

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 0 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission


Description

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission


Description

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission


Description

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission


Description

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission


Description

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission

codeword 1 in dual-
codeword
transmission


Description

codeword 1 in dual-
codeword
transmission
1526730141 L.ChMeas.RI.Rank Number of times BTS3900:

1 rank 1 is reported V100R008C01
BTS3900 LTE:
V100R008C01
1526730142 L.ChMeas.RI.Rank Number of times a BTS3900:

2 UE reports rank 2 V100R008C01
BTS3900 LTE:
V100R008C01

BTS3900 LTE:
V100R010C00

BTS3900 LTE:
V100R010C00
1526737710 L.ChMeas.CQI.DL Accumulated value BTS3900:

.BorderUE.Total of wideband CQIs V100R010C10
reported by CEUs BTS3900 LTE:
V100R010C10
1526737711 L.ChMeas.CQI.DL Number of times BTS3900:

.BorderUE.Num wideband CQIs are V100R010C10
reported by CEUs BTS3900 LTE:
V100R010C10
None

1.18.1 Number of Wideband CQI Reports in a Cell

Counters
1526727396 L.ChMeas.CQI. Number of BTS3900, L

DL.0 wideband CQI BTS3900 LTE
reports with the
value of 0

reports with the
value of 1

reports with the
value of 2

reports with the
value of 3

reports with the
value of 4

reports with the
value of 5

reports with the
value of 6

reports with the
value of 7

reports with the
value of 8



reports with the
value of 9

reports with the
value of 10

reports with the
value of 11

reports with the
value of 12

reports with the
value of 13

reports with the
value of 14

reports with the
value of 15
Description
Channel Quality Indicator (CQI) indicates downlink channel quality and is calculatd by the
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
L.ChMeas.CQI.DL.0 Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002016 Dynamic Downlink Power
LBFD-002025 Allocation
TDLBFD-002025 Dynamic Downlink Power
Allocation
Basic Scheduling

GSM: None
UMTS: None
Allocation
Basic Scheduling

GSM: None
UMTS: None
Allocation
Basic Scheduling


GSM: None
UMTS: None
Allocation
Basic Scheduling

GSM: None
UMTS: None
Allocation
Basic Scheduling

GSM: None
UMTS: None
Allocation
Basic Scheduling

GSM: None
UMTS: None
Allocation
Basic Scheduling


GSM: None
UMTS: None
Allocation
Basic Scheduling

GSM: None
UMTS: None
Allocation
Basic Scheduling

GSM: None
UMTS: None
Allocation
Basic Scheduling

GSM: None
UMTS: None
Allocation
Basic Scheduling


GSM: None
UMTS: None
Allocation
Basic Scheduling

GSM: None
UMTS: None
Allocation
Basic Scheduling

GSM: None
UMTS: None
Allocation
Basic Scheduling

GSM: None
UMTS: None
Allocation
Basic Scheduling


GSM: None
UMTS: None
Allocation
Basic Scheduling
1.18.2 Number of Periodic Wideband CQI Reports in Single-

Codeword Transmission in a Cell
Counters

DL.SingleCW.P periodic BTS3900 LTE
eriodic.0 wideband CQI
reports with the
value of 0 in
single-
codeword
transmission

reports with the
value of 1 in
single-
codeword
transmission

reports with the
value of 2 in
single-
codeword
transmission



reports with the
value of 3 in
single-
codeword
transmission

reports with the
value of 4 in
single-
codeword
transmission

reports with the
value of 5 in
single-
codeword
transmission

reports with the
value of 6 in
single-
codeword
transmission

reports with the
value of 7 in
single-
codeword
transmission



reports with the
value of 8 in
single-
codeword
transmission

reports with the
value of 9 in
single-
codeword
transmission

reports with the
value of 10 in
single-
codeword
transmission

reports with the
value of 11 in
single-
codeword
transmission

reports with the
value of 12 in
single-
codeword
transmission



reports with the
value of 13 in
single-
codeword
transmission

reports with the
value of 14 in
single-
codeword
transmission

reports with the
value of 15 in
single-
codeword
transmission
Description
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
each time the eNodeB receives a periodic wideband CQI report from a UE in single-codeword
transmission.
Formula
None
Unit
None

Related Features
L.ChMeas.CQI.DL.SingleC Multi-mode: None

W.Periodic.0 GSM: None
UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

1.18.3 Number of Aperiodic Wideband CQI Reports in Single-

Codeword Transmission in a Cell
Counters

DL.SingleCW. aperiodic BTS3900 LTE
Aperiodic.0 wideband CQI
reports with the
value of 0 in
single-
codeword
transmission

reports with the
value of 1 in
single-
codeword
transmission

reports with the
value of 2 in
single-
codeword
transmission

reports with the
value of 3 in
single-
codeword
transmission

reports with the
value of 4 in
single-
codeword
transmission



reports with the
value of 5 in
single-
codeword
transmission

reports with the
value of 6 in
single-
codeword
transmission

reports with the
value of 7 in
single-
codeword
transmission

reports with the
value of 8 in
single-
codeword
transmission

reports with the
value of 9 in
single-
codeword
transmission



reports with the
value of 10 in
single-
codeword
transmission

reports with the
value of 11 in
single-
codeword
transmission

reports with the
value of 12 in
single-
codeword
transmission

reports with the
value of 13 in
single-
codeword
transmission

reports with the
value of 14 in
single-
codeword
transmission



reports with the
value of 15 in
single-
codeword
transmission
Description
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
each time the eNodeB receives an aperiodic wideband CQI report in single-codeword
transmission from a UE.
Formula
None
Unit
None
Related Features

W.Aperiodic.0 GSM: None
UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

1.18.4 Number of Periodic Wideband CQI Reports for Codeword

0 in Dual-Codeword Transmission in a Cell
Counters

DL.DualCW.Co periodic BTS3900 LTE
de0.Periodic.0 wideband CQI
reports with the
value of 0 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 1 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 2 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 3 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 4 for
codeword 0 in
dual-codeword
transmission



reports with the
value of 5 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 6 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 7 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 8 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 9 for
codeword 0 in
dual-codeword
transmission



reports with the
value of 10 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 11 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 12 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 13 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 14 for
codeword 0 in
dual-codeword
transmission



reports with the
value of 15 for
codeword 0 in
dual-codeword
transmission
Description
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
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
L.ChMeas.CQI.DL.DualCW Multi-mode: None

.Code0.Periodic.0 GSM: None
UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

1.18.5 Number of Aperiodic Wideband CQI Reports for

Codeword 0 in Dual-Codeword Transmission in a Cell
Counters

DL.DualCW.Co aperiodic BTS3900 LTE
de0.Aperiodic.0 wideband CQI
reports with the
value of 0 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 1 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 2 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 3 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 4 for
codeword 0 in
dual-codeword
transmission



reports with the
value of 5 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 6 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 7 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 8 for
codeword 0 in
dual-codeword
transmission

reports with the
value of 9 for
codeword 0 in
dual-codeword
transmission



de0.Aperiodic. wideband CQI
10 reports with the
value of 10 for
codeword 0 in
dual-codeword
transmission

11 reports with the
value of 11 for
codeword 0 in
dual-codeword
transmission

12 reports with the
value of 12 for
codeword 0 in
dual-codeword
transmission

13 reports with the
value of 13 for
codeword 0 in
dual-codeword
transmission

14 reports with the
value of 14 for
codeword 0 in
dual-codeword
transmission



15 reports with the
value of 15 for
codeword 0 in
dual-codeword
transmission
Description
number of aperiodic wideband CQI reports with a specific value ranging from 0 to 15 for
downlink channel.
Measurement Points
each time the eNodeB receives an aperiodic wideband CQI report for codeword 0 in dual-
Formula
None
Unit
None
Related Features

.Code0.Aperiodic.0 GSM: None
UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

1.18.6 Number of Periodic Wideband CQI Reports for Codeword

1 in Dual-Codeword Transmission in a Cell
Counters

reports with the
value of 0 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 1 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 2 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 3 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 4 for
codeword 1 in
dual-codeword
transmission



reports with the
value of 5 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 6 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 7 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 8 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 9 for
codeword 1 in
dual-codeword
transmission



reports with the
value of 10 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 11 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 12 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 13 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 14 for
codeword 1 in
dual-codeword
transmission



reports with the
value of 15 for
codeword 1 in
dual-codeword
transmission
Description
number of periodic wideband CQI reports with a specific value ranging from 0 to 15 for
downlink channel.
Measurement Points
each time the eNodeB receives a periodic wideband CQI report for codeword 1 in dual-
Formula
None
Unit
None
Related Features

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

1.18.7 Number of Aperiodic Wideband CQI Reports for

Codeword 1 in Dual-Codeword Transmission in a Cell
Counters

reports with the
value of 0 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 1 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 2 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 3 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 4 for
codeword 1 in
dual-codeword
transmission



reports with the
value of 5 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 6 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 7 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 8 for
codeword 1 in
dual-codeword
transmission

reports with the
value of 9 for
codeword 1 in
dual-codeword
transmission



10 reports with the
value of 10 for
codeword 1 in
dual-codeword
transmission

11 reports with the
value of 11 for
codeword 1 in
dual-codeword
transmission

12 reports with the
value of 12 for
codeword 1 in
dual-codeword
transmission

13 reports with the
value of 13 for
codeword 1 in
dual-codeword
transmission

14 reports with the
value of 14 for
codeword 1 in
dual-codeword
transmission



15 reports with the
value of 15 for
codeword 1 in
dual-codeword
transmission
Description
number of aperiodic wideband CQI reports with a specific value ranging from 0 to 15 for
downlink channel.
Measurement Points
each time the eNodeB receives an aperiodic wideband CQI report for codeword 1 in dual-
Formula
None
Unit
None
Related Features

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling


UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling

UMTS: None
Allocation
Basic Scheduling
1.18.8 Number of Times a UE Reports a Rank Value in a Cell

Counters
1526730141 L.ChMeas.RI.R Number of BTS3900, L

ank1 times rank 1 is BTS3900 LTE
reported



ank2 times a UE BTS3900 LTE
reports rank 2

reports rank 3

reports rank 4
Description
Rank values are calculated by UEs and reported to the eNodeB through the uplink channel.
Rank values are used as the input of MAC scheduling of the eNodeB. The counters measure
the numbers of different rank values reported by UEs in a cell.
The L.ChMeas.RI.Rank3 and L.ChMeas.RI.Rank4 counters apply to only LTE FDD.
Measurement Points
The corresponding counter is incremented by 1 based on the rank value each time the eNodeB
receives a rank value from a UE.
Formula
None
Unit
None
Related Features
L.ChMeas.RI.Rank1 Multi-mode: None

GSM: None
UMTS: None
LOFD-001001 DL 2x2 MIMO
TDLOFD-001001 DL 2x2 MIMO


GSM: None
UMTS: None
TDLOFD-001001 DL 2x2 MIMO

GSM: None
UMTS: None
LOFD-001060 DL 4X4 MIMO

GSM: None
UMTS: None
LOFD-001060 DL 4X4 MIMO
1.18.9 wideband CQIs reported by CEUs in a Cell

Counters
1526737710 L.ChMeas.CQI. Accumulated BTS3900, L

DL.BorderUE. value of BTS3900 LTE
Total wideband CQIs
reported by
CEUs

DL.BorderUE. times wideband BTS3900 LTE
Num CQIs are
reported by
CEUs

Description
The counters measure the accumulated value of wideband CQIs reported by cell edge users
(CEUs) in a cell and the number of times wideband CQIs are reported by CEUs in a cell.
Measurement Points
The L.ChMeas.CQI.DL.BorderUE.Total counter is incremented by the CQI value each time
an eNodeB receives a wideband CQI from a cell edge user (CEU) in a cell. (If the rank value
is greater than 1, the counter is incremented by the CQI value per codeword.)
The L.ChMeas.CQI.DL.BorderUE.Num counter is incremented by 1 each time the eNodeB
receives a wideband CQI from a CEU in a cell. (If the rank value is greater than 1, the counter
is incremented by the number of codewords.) The eNodeB identifies a CEU based on the
signal quality difference between the serving cell and the strongest neighboring cell in the A3-
related measurement report. The difference threshold is specified by the EdgeUserA3Offset
parameter. This identification function is controlled by the BasedA3EdgeUserSwitch option
of the CellCounterAlgoSwitch parameter in the CellCounterParaGroup MO.
Formula
None
Unit
None
Related Features
L.ChMeas.CQI.DL.BorderU Multi-mode: None

E.Total GSM: None
UMTS: None
L.ChMeas.CQI.DL.BorderU Multi-mode: None

E.Num GSM: None
UMTS: None

1.19 MCS Measurement (ChMeas.MCS.Cell)

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
Description
1526727412 L.ChMeas.PUSCH. Number of times BTS3900:

MCS.0 MCS index 0 is V100R008C00
scheduled on the BTS3900 LTE:
PUSCH version earlier than
V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00


Description

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00


Description

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00


Description

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00


Description

V100R003C00

V100R003C00
1526727444 L.ChMeas.PDSCH. Number of times BTS3900:

PDSCH version earlier than
V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00


Description

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00


Description

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00


Description

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00

V100R003C00


Description

V100R003C00

V100R003C00
1526728566 L.ChMeas.PRB.UL Number of PRBs on BTS3900:

.MCS.0 the PUSCH using V100R008C00
MCS index 0 for BTS3900 LTE:
scheduling in a cell V100R008C00









Description












Description












Description




1526728599 L.ChMeas.PRB.DL Number of PRBs on BTS3900:

.RANK1.MCS.0 the PDSCH in rank V100R008C00
1 mode using MCS BTS3900 LTE:
index 0 for V100R008C00
scheduling in a cell






Description










Description










Description










Description










Description










Description










Description










Description










Description










Description










Description










Description










Description










Description










Description










Description



None
1.19.1 Number of Times an MCS Index Is Scheduled on the

PUSCH
Counters
1526727412 L.ChMeas.PUS Number of BTS3900, L

CH.MCS.0 times MCS BTS3900 LTE
index 0 is
scheduled on
the PUSCH

index 1 is
scheduled on
the PUSCH

index 2 is
scheduled on
the PUSCH



index 3 is
scheduled on
the PUSCH

index 4 is
scheduled on
the PUSCH

index 5 is
scheduled on
the PUSCH

index 6 is
scheduled on
the PUSCH

index 7 is
scheduled on
the PUSCH

index 8 is
scheduled on
the PUSCH

index 9 is
scheduled on
the PUSCH

index 10 is
scheduled on
the PUSCH



index 11 is
scheduled on
the PUSCH

index 12 is
scheduled on
the PUSCH

index 13 is
scheduled on
the PUSCH

index 14 is
scheduled on
the PUSCH

index 15 is
scheduled on
the PUSCH

index 16 is
scheduled on
the PUSCH

index 17 is
scheduled on
the PUSCH

index 18 is
scheduled on
the PUSCH



index 19 is
scheduled on
the PUSCH

index 20 is
scheduled on
the PUSCH

index 21 is
scheduled on
the PUSCH

index 22 is
scheduled on
the PUSCH

index 23 is
scheduled on
the PUSCH

index 24 is
scheduled on
the PUSCH

index 25 is
scheduled on
the PUSCH

index 26 is
scheduled on
the PUSCH



index 27 is
scheduled on
the PUSCH

index 28 is
scheduled on
the PUSCH

index 29 is
scheduled on
the PUSCH

index 30 is
scheduled on
the PUSCH

index 31 is
scheduled on
the PUSCH
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.
Formula
None

Unit
None
Related Features
L.ChMeas.PUSCH.MCS.0 Multi-mode: None

GSM: None
UMTS: None
LBFD-001005 Modulation: DL/UL QPSK,
TDLBFD-002025 DL/UL 16QAM, DL
64QAM
TDLBFD-001005
Basic Scheduling
Modulation: DL/UL QPSK,
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
LOFD-001006
TDLOFD-001006 DL/UL 16QAM, DL
64QAM
UL 64QAM
UL 64QAM

GSM: None
UMTS: None
64QAM
LOFD-001006
64QAM
UL 64QAM
UL 64QAM


GSM: None
UMTS: None
64QAM
LOFD-001006
64QAM
UL 64QAM
UL 64QAM

GSM: None
UMTS: None
64QAM
LOFD-001006
64QAM
UL 64QAM
UL 64QAM

GSM: None
UMTS: None
64QAM
LOFD-001006
64QAM
UL 64QAM
UL 64QAM


GSM: None
UMTS: None
64QAM
LOFD-001006
64QAM
UL 64QAM
UL 64QAM

GSM: None
UMTS: None
64QAM
LOFD-001006
64QAM
UL 64QAM
UL 64QAM
1.19.2 Number of Times a Specific MCS Index Is Scheduled on

the PDSCH
Counters
1526727444 L.ChMeas.PDS Number of BTS3900, L

index 0 is
scheduled on
the PDSCH



index 1 is
scheduled on
the PDSCH

index 2 is
scheduled on
the PDSCH

index 3 is
scheduled on
the PDSCH

index 4 is
scheduled on
the PDSCH

index 5 is
scheduled on
the PDSCH

index 6 is
scheduled on
the PDSCH

index 7 is
scheduled on
the PDSCH

index 8 is
scheduled on
the PDSCH



index 9 is
scheduled on
the PDSCH

index 10 is
scheduled on
the PDSCH

index 11 is
scheduled on
the PDSCH

index 12 is
scheduled on
the PDSCH

index 13 is
scheduled on
the PDSCH

index 14 is
scheduled on
the PDSCH

index 15 is
scheduled on
the PDSCH

index 16 is
scheduled on
the PDSCH



index 17 is
scheduled on
the PDSCH

index 18 is
scheduled on
the PDSCH

index 19 is
scheduled on
the PDSCH

index 20 is
scheduled on
the PDSCH

index 21 is
scheduled on
the PDSCH

index 22 is
scheduled on
the PDSCH

index 23 is
scheduled on
the PDSCH

index 24 is
scheduled on
the PDSCH



index 25 is
scheduled on
the PDSCH

index 26 is
scheduled on
the PDSCH

index 27 is
scheduled on
the PDSCH

index 28 is
scheduled on
the PDSCH

index 29 is
scheduled on
the PDSCH

index 30 is
scheduled on
the PDSCH

index 31 is
scheduled on
the PDSCH
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.These
counters do not involve simulated load.
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.
Formula
None
Unit
None
Related Features
L.ChMeas.PDSCH.MCS.0 Multi-mode: None

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

1.19.3 Number of PRBs on the PUSCH Using a Specified MCS for

Scheduling in a Cell
Counters
1526728566 L.ChMeas.PRB Number of BTS3900, L

.UL.MCS.0 PRBs on the BTS3900 LTE
PUSCH using
MCS index 0
for scheduling
in a cell

PUSCH using
MCS index 1
for scheduling
in a cell

PUSCH using
MCS index 2
for scheduling
in a cell

PUSCH using
MCS index 3
for scheduling
in a cell

PUSCH using
MCS index 4
for scheduling
in a cell

PUSCH using
MCS index 5
for scheduling
in a cell



PUSCH using
MCS index 6
for scheduling
in a cell

PUSCH using
MCS index 7
for scheduling
in a cell

PUSCH using
MCS index 8
for scheduling
in a cell

PUSCH using
MCS index 9
for scheduling
in a cell

PUSCH using
MCS index 10
for scheduling
in a cell

PUSCH using
MCS index 11
for scheduling
in a cell

PUSCH using
MCS index 12
for scheduling
in a cell



PUSCH using
MCS index 13
for scheduling
in a cell

PUSCH using
MCS index 14
for scheduling
in a cell

PUSCH using
MCS index 15
for scheduling
in a cell

PUSCH using
MCS index 16
for scheduling
in a cell

PUSCH using
MCS index 17
for scheduling
in a cell

PUSCH using
MCS index 18
for scheduling
in a cell

PUSCH using
MCS index 19
for scheduling
in a cell



PUSCH using
MCS index 20
for scheduling
in a cell

PUSCH using
MCS index 21
for scheduling
in a cell

PUSCH using
MCS index 22
for scheduling
in a cell

PUSCH using
MCS index 23
for scheduling
in a cell

PUSCH using
MCS index 24
for scheduling
in a cell

PUSCH using
MCS index 25
for scheduling
in a cell

PUSCH using
MCS index 26
for scheduling
in a cell



PUSCH using
MCS index 27
for scheduling
in a cell

PUSCH using
MCS index 28
for scheduling
in a cell

PUSCH using
MCS index 29
for scheduling
in a cell

PUSCH using
MCS index 30
for scheduling
in a cell

PUSCH using
MCS index 31
for scheduling
in a cell
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.(In an SFN cell, the number
of used PRBs in all physical cells is accumulated.)
In LTE TDD mode, only uplink subframes are measured.In a cell combination scenario, the
number of used PRBs in all physical cells is accumulated.

Formula
None
Unit
None
Related Features
L.ChMeas.PRB.UL.MCS.0 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

1.19.4 Number of PRBs on the PDSCH Using a Specific MCS

index for Scheduling in a Cell
Counters

.DL.RANK1.M PRBs on the BTS3900 LTE
CS.0 PDSCH in rank
1 mode using
MCS index 0
for scheduling
in a cell

CS.1 PDSCH in rank
1 mode using
MCS index 1
for scheduling
in a cell

CS.2 PDSCH in rank
1 mode using
MCS index 2
for scheduling
in a cell

CS.3 PDSCH in rank
1 mode using
MCS index 3
for scheduling
in a cell

CS.4 PDSCH in rank
1 mode using
MCS index 4
for scheduling
in a cell



CS.5 PDSCH in rank
1 mode using
MCS index 5
for scheduling
in a cell

CS.6 PDSCH in rank
1 mode using
MCS index 6
for scheduling
in a cell

CS.7 PDSCH in rank
1 mode using
MCS index 7
for scheduling
in a cell

CS.8 PDSCH in rank
1 mode using
MCS index 8
for scheduling
in a cell

CS.9 PDSCH in rank
1 mode using
MCS index 9
for scheduling
in a cell

CS.10 PDSCH in rank
1 mode using
MCS index 10
for scheduling
in a cell



CS.11 PDSCH in rank
1 mode using
MCS index 11
for scheduling
in a cell

CS.12 PDSCH in rank
1 mode using
MCS index 12
for scheduling
in a cell

CS.13 PDSCH in rank
1 mode using
MCS index 13
for scheduling
in a cell

CS.14 PDSCH in rank
1 mode using
MCS index 14
for scheduling
in a cell

CS.15 PDSCH in rank
1 mode using
MCS index 15
for scheduling
in a cell

CS.16 PDSCH in rank
1 mode using
MCS index 16
for scheduling
in a cell



CS.17 PDSCH in rank
1 mode using
MCS index 17
for scheduling
in a cell

CS.18 PDSCH in rank
1 mode using
MCS index 18
for scheduling
in a cell

CS.19 PDSCH in rank
1 mode using
MCS index 19
for scheduling
in a cell

CS.20 PDSCH in rank
1 mode using
MCS index 20
for scheduling
in a cell

CS.21 PDSCH in rank
1 mode using
MCS index 21
for scheduling
in a cell

CS.22 PDSCH in rank
1 mode using
MCS index 22
for scheduling
in a cell



CS.23 PDSCH in rank
1 mode using
MCS index 23
for scheduling
in a cell

CS.24 PDSCH in rank
1 mode using
MCS index 24
for scheduling
in a cell

CS.25 PDSCH in rank
1 mode using
MCS index 25
for scheduling
in a cell

CS.26 PDSCH in rank
1 mode using
MCS index 26
for scheduling
in a cell

CS.27 PDSCH in rank
1 mode using
MCS index 27
for scheduling
in a cell

CS.28 PDSCH in rank
1 mode using
MCS index 28
for scheduling
in a cell



CS.29 PDSCH in rank
1 mode using
MCS index 29
for scheduling
in a cell

CS.30 PDSCH in rank
1 mode using
MCS index 30
for scheduling
in a cell

CS.31 PDSCH in rank
1 mode using
MCS index 31
for scheduling
in a cell

CS.0 PDSCH in rank
2 mode using
MCS index 0
for scheduling
in a cell

CS.1 PDSCH in rank
2 mode using
MCS index 1
for scheduling
in a cell

CS.2 PDSCH in rank
2 mode using
MCS index 2
for scheduling
in a cell



CS.3 PDSCH in rank
2 mode using
MCS index 3
for scheduling
in a cell

CS.4 PDSCH in rank
2 mode using
MCS index 4
for scheduling
in a cell

CS.5 PDSCH in rank
2 mode using
MCS index 5
for scheduling
in a cell

CS.6 PDSCH in rank
2 mode using
MCS index 6
for scheduling
in a cell

CS.7 PDSCH in rank
2 mode using
MCS index 7
for scheduling
in a cell

CS.8 PDSCH in rank
2 mode using
MCS index 8
for scheduling
in a cell



CS.9 PDSCH in rank
2 mode using
MCS index 9
for scheduling
in a cell

CS.10 PDSCH in rank
2 mode using
MCS index 10
for scheduling
in a cell

CS.11 PDSCH in rank
2 mode using
MCS index 11
for scheduling
in a cell

CS.12 PDSCH in rank
2 mode using
MCS index 12
for scheduling
in a cell

CS.13 PDSCH in rank
2 mode using
MCS index 13
for scheduling
in a cell

CS.14 PDSCH in rank
2 mode using
MCS index 14
for scheduling
in a cell



CS.15 PDSCH in rank
2 mode using
MCS index 15
for scheduling
in a cell

CS.16 PDSCH in rank
2 mode using
MCS index 16
for scheduling
in a cell

CS.17 PDSCH in rank
2 mode using
MCS index 17
for scheduling
in a cell

CS.18 PDSCH in rank
2 mode using
MCS index 18
for scheduling
in a cell

CS.19 PDSCH in rank
2 mode using
MCS index 19
for scheduling
in a cell

CS.20 PDSCH in rank
2 mode using
MCS index 20
for scheduling
in a cell



CS.21 PDSCH in rank
2 mode using
MCS index 21
for scheduling
in a cell

CS.22 PDSCH in rank
2 mode using
MCS index 22
for scheduling
in a cell

CS.23 PDSCH in rank
2 mode using
MCS index 23
for scheduling
in a cell

CS.24 PDSCH in rank
2 mode using
MCS index 24
for scheduling
in a cell

CS.25 PDSCH in rank
2 mode using
MCS index 25
for scheduling
in a cell

CS.26 PDSCH in rank
2 mode using
MCS index 26
for scheduling
in a cell



CS.27 PDSCH in rank
2 mode using
MCS index 27
for scheduling
in a cell

CS.28 PDSCH in rank
2 mode using
MCS index 28
for scheduling
in a cell

CS.29 PDSCH in rank
2 mode using
MCS index 29
for scheduling
in a cell

CS.30 PDSCH in rank
2 mode using
MCS index 30
for scheduling
in a cell

CS.31 PDSCH in rank
2 mode using
MCS index 31
for scheduling
in a cell

CS.0 PDSCH in rank
3 mode using
MCS index 0
for scheduling
in a cell



CS.1 PDSCH in rank
3 mode using
MCS index 1
for scheduling
in a cell

CS.2 PDSCH in rank
3 mode using
MCS index 2
for scheduling
in a cell

CS.3 PDSCH in rank
3 mode using
MCS index 3
for scheduling
in a cell

CS.4 PDSCH in rank
3 mode using
MCS index 4
for scheduling
in a cell

CS.5 PDSCH in rank
3 mode using
MCS index 5
for scheduling
in a cell

CS.6 PDSCH in rank
3 mode using
MCS index 6
for scheduling
in a cell



CS.7 PDSCH in rank
3 mode using
MCS index 7
for scheduling
in a cell

CS.8 PDSCH in rank
3 mode using
MCS index 8
for scheduling
in a cell

CS.9 PDSCH in rank
3 mode using
MCS index 9
for scheduling
in a cell

CS.10 PDSCH in rank
3 mode using
MCS index 10
for scheduling
in a cell

CS.11 PDSCH in rank
3 mode using
MCS index 11
for scheduling
in a cell

CS.12 PDSCH in rank
3 mode using
MCS index 12
for scheduling
in a cell



CS.13 PDSCH in rank
3 mode using
MCS index 13
for scheduling
in a cell

CS.14 PDSCH in rank
3 mode using
MCS index 14
for scheduling
in a cell

CS.15 PDSCH in rank
3 mode using
MCS index 15
for scheduling
in a cell

CS.16 PDSCH in rank
3 mode using
MCS index 16
for scheduling
in a cell

CS.17 PDSCH in rank
3 mode using
MCS index 17
for scheduling
in a cell

CS.18 PDSCH in rank
3 mode using
MCS index 18
for scheduling
in a cell



CS.19 PDSCH in rank
3 mode using
MCS index 19
for scheduling
in a cell

CS.20 PDSCH in rank
3 mode using
MCS index 20
for scheduling
in a cell

CS.21 PDSCH in rank
3 mode using
MCS index 21
for scheduling
in a cell

CS.22 PDSCH in rank
3 mode using
MCS index 22
for scheduling
in a cell

CS.23 PDSCH in rank
3 mode using
MCS index 23
for scheduling
in a cell

CS.24 PDSCH in rank
3 mode using
MCS index 24
for scheduling
in a cell



CS.25 PDSCH in rank
3 mode using
MCS index 25
for scheduling
in a cell

CS.26 PDSCH in rank
3 mode using
MCS index 26
for scheduling
in a cell

CS.27 PDSCH in rank
3 mode using
MCS index 27
for scheduling
in a cell

CS.28 PDSCH in rank
3 mode using
MCS index 28
for scheduling
in a cell

CS.29 PDSCH in rank
3 mode using
MCS index 29
for scheduling
in a cell

CS.30 PDSCH in rank
3 mode using
MCS index 30
for scheduling
in a cell



CS.31 PDSCH in rank
3 mode using
MCS index 31
for scheduling
in a cell

CS.0 PDSCH in rank
4 mode using
MCS index 0
for scheduling
in a cell

CS.1 PDSCH in rank
4 mode using
MCS index 1
for scheduling
in a cell

CS.2 PDSCH in rank
4 mode using
MCS index 2
for scheduling
in a cell

CS.3 PDSCH in rank
4 mode using
MCS index 3
for scheduling
in a cell

CS.4 PDSCH in rank
4 mode using
MCS index 4
for scheduling
in a cell



CS.5 PDSCH in rank
4 mode using
MCS index 5
for scheduling
in a cell

CS.6 PDSCH in rank
4 mode using
MCS index 6
for scheduling
in a cell

CS.7 PDSCH in rank
4 mode using
MCS index 7
for scheduling
in a cell

CS.8 PDSCH in rank
4 mode using
MCS index 8
for scheduling
in a cell

CS.9 PDSCH in rank
4 mode using
MCS index 9
for scheduling
in a cell

CS.10 PDSCH in rank
4 mode using
MCS index 10
for scheduling
in a cell



CS.11 PDSCH in rank
4 mode using
MCS index 11
for scheduling
in a cell

CS.12 PDSCH in rank
4 mode using
MCS index 12
for scheduling
in a cell

CS.13 PDSCH in rank
4 mode using
MCS index 13
for scheduling
in a cell

CS.14 PDSCH in rank
4 mode using
MCS index 14
for scheduling
in a cell

CS.15 PDSCH in rank
4 mode using
MCS index 15
for scheduling
in a cell

CS.16 PDSCH in rank
4 mode using
MCS index 16
for scheduling
in a cell



CS.17 PDSCH in rank
4 mode using
MCS index 17
for scheduling
in a cell

CS.18 PDSCH in rank
4 mode using
MCS index 18
for scheduling
in a cell

CS.19 PDSCH in rank
4 mode using
MCS index 19
for scheduling
in a cell

CS.20 PDSCH in rank
4 mode using
MCS index 20
for scheduling
in a cell

CS.21 PDSCH in rank
4 mode using
MCS index 21
for scheduling
in a cell

CS.22 PDSCH in rank
4 mode using
MCS index 22
for scheduling
in a cell



CS.23 PDSCH in rank
4 mode using
MCS index 23
for scheduling
in a cell

CS.24 PDSCH in rank
4 mode using
MCS index 24
for scheduling
in a cell

CS.25 PDSCH in rank
4 mode using
MCS index 25
for scheduling
in a cell

CS.26 PDSCH in rank
4 mode using
MCS index 26
for scheduling
in a cell

CS.27 PDSCH in rank
4 mode using
MCS index 27
for scheduling
in a cell

CS.28 PDSCH in rank
4 mode using
MCS index 28
for scheduling
in a cell



CS.29 PDSCH in rank
4 mode using
MCS index 29
for scheduling
in a cell

CS.30 PDSCH in rank
4 mode using
MCS index 30
for scheduling
in a cell

CS.31 PDSCH in rank
4 mode using
MCS index 31
for scheduling
in a cell
Description
The counters measure the numbers of downlink MCS-specific PRBs to be allocated to UEs in
different ranks, including PRBs for HARQ retransmission. MCS indexes 29, 30, and 31 are
used for retransmission.
For UEs in rank 2, rank 3, and rank 4, multiple codewords are transmitted at the same time.
Each codeword is configured with an MSC index. Therefore, the numbers of PRBs in rank 2,
rank 3, and rank 4 in each codeword is counted separately. These counters do not involve
simulated load.
Measurement Points
The number of PRBs on the PDSCH in different ranks 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
L.ChMeas.PRB.DL.RANK1 Multi-mode: None

.MCS.0 GSM: None
UMTS: None
LTE: LBFD-001005 Modulation: DL/UL QPSK,
LOFD-001001 DL/UL 16QAM, DL
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.1 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.2 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.3 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.4 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.5 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.6 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.7 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.8 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.9 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.10 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.11 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.12 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.13 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.14 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.15 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.16 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.17 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.18 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.19 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.20 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.21 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.22 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.23 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.24 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.25 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.26 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.27 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.28 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.29 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.30 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.31 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.0 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.1 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.2 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.3 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.4 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.5 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.6 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.7 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.8 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.9 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.10 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.11 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.12 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.13 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.14 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.15 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.16 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.17 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.18 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.19 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.20 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.21 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.22 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.23 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.24 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.25 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.26 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.27 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.28 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.29 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.30 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.31 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.0 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.1 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.2 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.3 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.4 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.5 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.6 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.7 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.8 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.9 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.10 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.11 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.12 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.13 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.14 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.15 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.16 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.17 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.18 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.19 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.20 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.21 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.22 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.23 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.24 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.25 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.26 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.27 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.28 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.29 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.30 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.31 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.0 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.1 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.2 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.3 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.4 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.5 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.6 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.7 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.8 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.9 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.10 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.11 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.12 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.13 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.14 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.15 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.16 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.17 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.18 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.19 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.20 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.21 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.22 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.23 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.24 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.25 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.26 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.27 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.28 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.29 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO


.MCS.30 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO

.MCS.31 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO
1.20 PRB Measurement (ChMeas.PRB.Cell)

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
Description
1526726737 L.ChMeas.PRB.UL Average number of BTS3900:

.Used.Avg used uplink PRBs V100R008C00
BTS3900 LTE:
V100R003C00
1526726740 L.ChMeas.PRB.DL Average number of BTS3900:

.Used.Avg used PDSCH PRBs V100R008C00
BTS3900 LTE:
V100R003C00
1526727483 L.ChMeas.PRB.PU Average number of BTS3900:

CCH.Avg used PRBs over the V100R008C00
PUCCH BTS3900 LTE:
V100R003C00
1526728299 L.ChMeas.PDCCH Number of times the BTS3900:

.SymNum.1 PDCCH occupies V100R008C00
one symbol in a BTS3900 LTE:
measurement period V100R005C00

two symbols in a BTS3900 LTE:

three symbols in a BTS3900 LTE:

four symbols in a BTS3900 LTE:
1526728303 L.ChMeas.CCE.Co Number of PDCCH BTS3900:

mmUsed CCEs used for V100R008C00
common DCI BTS3900 LTE:
V100R005C00
1526728304 L.ChMeas.CCE.U Number of PDCCH BTS3900:

LUsed CCEs used for V100R008C00
uplink DCI in a BTS3900 LTE:


Description
1526728305 L.ChMeas.CCE.D Number of PDCCH BTS3900:

LUsed CCEs used for V100R008C00
downlink DCI in a BTS3900 LTE:
1526728340 L.ULCoMP.RB Average number of BTS3900:

scheduled PRBs for V100R008C00
UL CoMP BTS3900 LTE:
V100R005C00

.PCell.Used.Avg downlink PRBs V100R008C00
occupied by CA BTS3900 LTE:
UEs that use the V100R008C00
local cell as their
primary serving cell

.SCell.Used.Avg downlink PRBs V100R008C00
UEs that use the V100R008C00
local cell as their
secondary serving
cell
1526728433 L.ChMeas.PRB.DL Number of available BTS3900:

.Avail downlink PRBs V100R008C00
BTS3900 LTE:
V100R008C00
1526728434 L.ChMeas.PRB.UL Number of available BTS3900:

.Avail uplink PRBs V100R008C00
BTS3900 LTE:
V100R008C00

.CEU.Used.Avg PRBs used by uplink V100R008C00
CEUs in a cell BTS3900 LTE:
V100R008C00

.CEU.Used.Avg PRBs used by V100R008C00
downlink CEUs in a BTS3900 LTE:
cell V100R008C00

.FSS.Avg PRBs allocated for V100R008C00
uplink frequency BTS3900 LTE:
selective scheduling V100R008C00


Description

.FSS.Avg PRBs allocated for V100R008C00
downlink frequency BTS3900 LTE:
selective scheduling V100R008C00

.PreSch.Used.Avg PRBs allocated for V100R008C00
uplink pre- BTS3900 LTE:
scheduling V100R008C00
1526728664 L.ChMeas.PDCCH Number of times of BTS3900:

.DL.DTXNum.Agg DTX for PDCCH V100R008C00
Lvl1 resource allocation BTS3900 LTE:
with aggregation V100R008C00
level 1 in a cell

level 2 in a cell

level 4 in a cell

level 8 in a cell

.AggLvl1Num PDCCH resource V100R008C00
allocations with BTS3900 LTE:
aggregation level 1 V100R008C00




Description


.DrbUsed.Avg PRBs used by V100R008C00
PUSCH DRBs BTS3900 LTE:
V100R008C00

.DrbUsed.Avg PRBs used by V100R008C00
PDSCH DRBs BTS3900 LTE:
V100R008C00
1526728764 L.ChMeas.PRB.PU Average number of BTS3900:

SCH.Avg used PUSCH PRBs V100R008C00
BTS3900 LTE:
V100R008C00
1526728765 L.ChMeas.CCE.Av Number of available BTS3900:

ail PDCCH CCEs V100R008C00
BTS3900 LTE:
V100R008C00

LUsed.DRB CCEs used for initial V100R008C01
transmitted BTS3900 LTE:
downlink data in a V100R008C01
cell

LUsed.SRB CCEs used for initial V100R008C01
downlink signaling V100R008C01
in a cell

LUsed.MCE CCEs used for initial V100R008C01
downlink MCEs in a V100R008C01
cell

LUsed.Equivalent CCEs with the CCE V100R008C01
power equivalent to BTS3900 LTE:
the reference power V100R008C01
used for uplink DCI


Description

LUsed.Equivalent CCEs with the CCE V100R008C01
power equivalent to BTS3900 LTE:
the reference power V100R008C01
used for downlink
DCI

.DLComp.Used.Av PRBs used by V100R008C01
g downlink CoMP BTS3900 LTE:

.SrbUsed.Avg PRBs used by V100R009C00
downlink signaling BTS3900 LTE:

.PagingUsed.Avg PRBs used by V100R009C00
paging messages in BTS3900 LTE:
a cell V100R009C00
1526730557 L.ChMeas.PRB.UL Number of available BTS3900:

.PUSCH.Avail PUSCH PRBs V100R009C00
BTS3900 LTE:
V100R009C00
1526730842 L.ChMeas.PUSCH. Number of initial BTS3900:

DmrsTaSch uplink transmissions V100R009C00
of DMRS TA in a BTS3900 LTE:
cell V100R009C00
1526730843 L.ChMeas.PUSCH. Number of uplink BTS3900:

DmrsTaSch.Retran retransmissions of V100R009C00
s DMRS TA in a cell BTS3900 LTE:
V100R009C00
1526730844 L.ChMeas.CCE.U Number of uplink BTS3900:

L.AllocFail CCE allocation V100R009C00
failures in a cell BTS3900 LTE:
V100R009C00
1526730845 L.ChMeas.CCE.D Number of downlink BTS3900:

L.AllocFail CCE allocation V100R009C00
failures in a cell BTS3900 LTE:
V100R009C00

.DrbUsed.Avg.VoIP PRBs used by DRBs V100R010C00
on the PDSCH for BTS3900 LTE:
downlink VoIP V100R010C00
services


Description

.DrbUsed.Avg.VoIP PRBs used by DRBs V100R010C00
on the PUSCH for BTS3900 LTE:
uplink VoIP services V100R010C00
1526732697 L.ChMeas.PRB.PU Number of samples BTS3900:

SCH.Util.Samp.Ind with the PUSCH V100R010C00
ex0 PRB usage ranging BTS3900 LTE:
within index 0 V100R010C00










Description


.TaSch.Used.Avg PRBs allocated for V100R010C00
uplink TA BTS3900 LTE:
measurement V100R010C00

LUsed.TA CCEs allocated for V100R010C00
TA measurement BTS3900 LTE:
V100R010C00
1526732727 L.ChMeas.PRB.PD Number of samples BTS3900:

SCH.Util.Samp.Ind with the PDSCH V100R010C00








Description



1526732911 L.ChMeas.PRB.DL Number of downlink BTS3900:

.PCell.RelaxedBac PRBs occupied by V100R010C00
khaulCAUsed.Avg inter-eNodeB CA BTS3900 LTE:
UEs that treat the V100R010C00
local cell as their
PCell
1526732912 L.ChMeas.PRB.DL Number of downlink BTS3900:

.SCell.RelaxedBack PRBs occupied by V100R010C00
haulCAUsed.Avg inter-eNodeB CA BTS3900 LTE:
local cell as their
SCell

.PCell.Used.Avg uplink PRBs V100R010C00
local cell as their
PCell

.SCell.Used.Avg uplink PRBs V100R010C00
local cell as their
SCell
1526733175 L.ULCoMP.Hetnet Average number of BTS3900:

CoMP.RB scheduled RBs for V100R010C00
HetNet UL CoMP in BTS3900 LTE:
a cell V100R010C00


Description
1526733196 L.ChMeas.ULCoM Average number of BTS3900:

PPhase2.PRB.Avg scheduled PRBs for V100R010C00
intra-BBU inter- BTS3900 LTE:
BBP UL CoMP in a V100R010C00
cell
1526733197 L.ChMeas.ULOver Average number of BTS3900:

BBUCoMP.PRB.Av scheduled PRBs for V100R010C00
g inter-BBU UL BTS3900 LTE:
CoMP in a cell V100R010C00

LUsed.VoIP CCEs used for V100R010C10
uplink VoIP services BTS3900 LTE:
V100R010C10

LUsed.VoIP CCEs used for V100R010C10
downlink VoIP BTS3900 LTE:
services V100R010C10
1526737748 L.ChMeas.PRB.DL Number of PRBs of BTS3900:

.AICIC.CEB.Avg the downlink edge V100R010C10
band configured for BTS3900 LTE:
the cell in adaptive V100R010C10
ICIC
1526737753 L.ChMeas.PRB.Int Average number of BTS3900:

erEnbDLComp.Us PRBs used for inter- V100R010C10
ed.Avg eNodeB DL CoMP BTS3900 LTE:
1526737761 L.ChMeas.PRB.UL Number of used BTS3900:

.ULShared.Used.A uplink PRBs on the V100R010C10
vg PUSCH on the BTS3900 LTE:
UMTS and LTE V100R010C10
shared spectrum in a
cell
1526737762 L.ChMeas.ULRela Average number of BTS3900:

xedBHCoMP.PRB. PRBs scheduled for V100R010C10
Avg relaxed-backhaul- BTS3900 LTE:
based UL CoMP in V100R010C10
a cell
1526737816 L.ChMeas. Average number of BTS3900:

3SectorULCoMP.P scheduled PRBs for V100R010C10
RB.Avg 3-cell UL CoMP in BTS3900 LTE:
a cell V100R010C10


Description

LUsed.SRB CCEs used for initial V100R010C10
transmitted uplink BTS3900 LTE:
signaling in a cell V100R010C10

.DrbUsed.Avg.VoIP standardized PRBs V100R010C10
.Equivalent used for downlink BTS3900 LTE:
VoIP services V100R010C10

.DrbUsed.Avg.Equi standardized PRBs V100R010C10
valent used for downlink BTS3900 LTE:
services V100R010C10
The ChMeas.PRB.Cell function subset contains counters related to PRB and control channel
resources. For the measurement of the number of PRBs, some of these counters can be
categorized as uplink- related counters and downlink-related counters in terms of the
transmission direction. In terms of the applicable features, some of these counters can be
categorized as counters related to scheduling for CoMP, frequency selective scheduling, pre-
scheduling, and others. In terms of the channel type, some of these counters can be
categorized as counters related to PUSCH, PUCCH, and others. In terms of the object, some
of these counters can be categorized as counters related to CEU, PCell, and others. For the
measurement of the number of available CCEs, some of these counters can be categorized as
counters related to uplink DCI, downlink DCI, public DCI, and others in terms of the control
message type. The following table shows the parent-child relationship of the counters.
L.ChMeas.PRB.UL.Used.A L.ULCoMP.RB L.ChMeas.ULCoMPPhase2.

vg PRB.Avg
L.ULCoMP.RB L.ChMeas.ULOverBBUCo
MP.PRB.Avg
L.ChMeas.PRB.UL.Used.A L.ChMeas.PRB.PUSCH.Av L.ChMeas.PRB.UL.DrbUse

vg g d.Avg
L.ChMeas.PRB.PUCCH.Av -
g
L.ChMeas.PRB.UL.Used.A L.ChMeas.PRB.UL.CEU.Us -
vg ed.Avg
L.ChMeas.PRB.UL.Used.A L.ChMeas.PRB.UL.FSS.Av -
vg g

L.ChMeas.PRB.UL.Used.A L.ChMeas.PRB.UL.PreSch. -
vg Used.Avg
L.ChMeas.PRB.UL.Used.A L.ULCoMP.HetnetCoMP.R -
vg B
L.ChMeas.PRB.DL.Used.A L.ChMeas.PRB.DL.DrbUse -
vg d.Avg
L.ChMeas.PRB.DL.Used.A L.ChMeas.PRB.DL.PCell.U -
vg sed.Avg
L.ChMeas.PRB.DL.Used.A L.ChMeas.PRB.DL.SCell.U -
vg sed.Avg
L.ChMeas.PRB.DL.Used.A L.ChMeas.PRB.DL.CEU.Us -
vg ed.Avg
L.ChMeas.PRB.DL.Used.A L.ChMeas.PRB.DL.FSS.Av -
vg g
L.ChMeas.PRB.DL.Used.A L.ChMeas.PRB.DL.DLCom -
vg p.Used.Avg
L.ChMeas.CCE.Avail L.ChMeas.CCE.DLUsed L.ChMeas.CCE.DLUsed.D

RB
L.ChMeas.CCE.DLUsed.SR
B
L.ChMeas.CCE.DLUsed.M
CE
L.ChMeas.CCE.ULUsed -
L.ChMeas.CCE.CommUsed -
1.20.1 Number of Used Uplink PRBs
Counters
1526726737 L.ChMeas.PRB Average BTS3900, L

.UL.Used.Avg number of used BTS3900 LTE
uplink PRBs
1526728340 L.ULCoMP.RB Average BTS3900, L

number of BTS3900 LTE
scheduled PRBs
for UL CoMP



.UL.DrbUsed.A number of BTS3900 LTE
vg PRBs used by
PUSCH DRBs

.PUSCH.Avg number of used BTS3900 LTE
PUSCH PRBs

.UL.DrbUsed.A number of BTS3900 LTE
vg.VoIP PRBs used by
DRBs on the
PUSCH for
uplink VoIP
services
1526733175 L.ULCoMP.Het Average BTS3900, L

netCoMP.RB number of BTS3900 LTE
scheduled RBs
for HetNet UL
CoMP in a cell
1526733196 L.ChMeas.ULC Average BTS3900, L

oMPPhase2.PR number of BTS3900 LTE
B.Avg scheduled PRBs
for intra-BBU
inter-BBP UL
CoMP in a cell
1526733197 L.ChMeas.ULO Average BTS3900, L

verBBUCoMP. number of BTS3900 LTE
PRB.Avg scheduled PRBs
for inter-BBU
UL CoMP in a
cell
1526737762 L.ChMeas.ULR Average BTS3900, L

elaxedBHCoM number of BTS3900 LTE
P.PRB.Avg PRBs scheduled
for relaxed-
backhaul-based
UL CoMP in a
cell
1526737816 L.ChMeas. Average BTS3900, L

3SectorULCoM number of BTS3900 LTE
P.PRB.Avg scheduled PRBs
for 3-cell UL
CoMP in a cell

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.ChMeas.PRB.UL.DrbUsed.Avg.VoIP counter measures the average number of PRBs

used by uplink DRBs on the PUSCH for VoIP services. This counter is used to analyze the
uplink PRB usage of VoIP services.
The L.ULCoMP.RB counter measures the average number of PRBs used by CoMP UEs in a
cell. It is used to analyze the usage of uplink PRBs for CoMP UEs.
The L.ULCoMP.HetnetCoMP.RB counter measures the average number of PRBs used by UEs
selected for whom HetNet UL CoMP is performed in a cell. It is used to analyze the usage of
PRBs for UEs selected for whom HetNet UL CoMP is performed.
The L.ChMeas.ULCoMPPhase2.PRB.Avg counter measures the average number of PRBs

used by UEs selected for whom intra-BBU inter-BBP UL CoMP is performed and inter-BBU
UL CoMP is not performed in a cell. It is used to analyze the usage of PRBs for UEs for
whom intra-BBU inter-BBP UL CoMP is performed.
The L.ChMeas.ULOverBBUCoMP.PRB.Avg counter measures the average number of PRBs

used by UEs selected for whom inter-BBU UL CoMP based on Coordinated BBU is
performed. It is used to analyze the usage of PRBs for UEs for whom inter-BBU UL CoMP
based on Coordinated BBU is performed.
The L.ChMeas.ULRelaxedBHCoMP.PRB.Avg counter measures the average number of PRBs

used by UEs selected for whom inter-BBU UL CoMP Based on Relaxed Backhaul is
performed. It is used to analyze the usage of PRBs for UEs for whom inter-BBU UL CoMP
Based on Relaxed Backhaul is performed.
The L.ChMeas.3SectorULCoMP.PRB.Avg counter measures the average number of PRBs

used by UEs selected for whom 3-cell UL CoMP is performed. It is used to analyze the usage
of PRBs for UEs for whom 3-cell UL CoMP is performed.
The number of uplink used PRBs is determined by the uplink traffic volume and signal
quality.
The L.ULCoMP.HetnetCoMP.R, L.ChMeas.ULRelaxedBHCoMP.PRB.Avg, and L.ChMeas.

3SectorULCoMP.PRB.Avg counters apply to only LTE FDD.
Measurement Points
During a measurement period, the average number of PRBs used by all uplink channels, by
PUSCH, by PUSCH DRBs, by PUSCH DRBs for VoIP services (in an SFN cell, the number
of used PRBs of all physical cells corresponding to all sectors is accumulated), or by UL
CoMP UEs is measured 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
retransmissions fail, the eNodeB cannot recognize that the data is transmitted on DRBs and
the corresponding used PRBs are not counted. During the adaptive uplink retransmission, 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.

For UEs selected for whom HetNet UL CoMP is performed, the average number of used
PRBs per millisecond is included in both the L.ULCoMP.HetnetCoMP.RB and
L.ULCoMP.RB counters.
For UEs selected for whom intra-BBU inter-BBP UL CoMP is performed and inter-BBU UL
CoMP is not performed, the average number of used PRBs per millisecond is included in both
the L.ULCoMP.RB and L.ChMeas.ULCoMPPhase2.PRB.Avg counters.
For UEs selected for whom inter-BBU UL CoMP based on Coordinated BBU is performed,
the average number of used PRBs per millisecond is included in both the L.ULCoMP.RB and
L.ChMeas.ULOverBBUCoMP.PRB.Avgcounters.
For UEs selected for whom inter-BBU UL CoMP Based on Relaxed Backhaul is performed,
the average number of used PRBs per millisecond is included in both the L.ULCoMP.RB and
L.ChMeas.ULRelaxedBHCoMP.PRB.Avg counters.
For UEs selected for whom 3-cell UL CoMP is performed, the average number of used PRBs
per millisecond is included in both the L.ULCoMP.RB and L.ChMeas.
3SectorULCoMP.PRB.Avg counters.
In the LTE TDD system, only uplink subframes are measured. In cell combination scenarios,
the number of used PRBs in all available physical cells is accumulated and then divided by
the number of available physical cells.
Formula
None
Unit
None
Related Features
L.ChMeas.PRB.UL.Used.A Multi-mode: None

vg GSM: None
UMTS: None

L.ULCoMP.RB Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001066 Intra-eNodeB UL CoMP
LOFD-070222 Intra-eNodeB UL CoMP
LOFD-070223 Phase II
TDLOFD-001066 UL CoMP based on
Coordinated BBU
Intra-eNodeB UL CoMP
L.ChMeas.PRB.UL.DrbUse Multi-mode: None

d.Avg GSM: None
UMTS: None
L.ChMeas.PRB.PUSCH.Av Multi-mode: None

g GSM: None
UMTS: None
L.ChMeas.PRB.UL.DrbUse Multi-mode: None

d.Avg.VoIP GSM: None
UMTS: None
L.ULCoMP.HetnetCoMP.R Multi-mode: None

B GSM: None
UMTS: None
UL CoMP based on
Coordinated BBU

L.ChMeas.ULCoMPPhase2. Multi-mode: None

PRB.Avg GSM: None
UMTS: None
TDLOFD-001066 Phase II
L.ChMeas.ULOverBBUCo Multi-mode: None

MP.PRB.Avg GSM: None
UMTS: None
LTE: LOFD-070223 UL CoMP based on
TDLOFD-081207 Coordinated BBU
UL CoMP based on
Coordinated BBU
L.ChMeas.ULRelaxedBHC Multi-mode: None

oMP.PRB.Avg GSM: None
UMTS: None
LTE: LOFD-081219 UL CoMP Based on
Relaxed Backhaul
L.ChMeas. Multi-mode: None

3SectorULCoMP.PRB.Avg GSM: None
UMTS: None
LOFD-081219 UL CoMP based on
Coordinated BBU
UL CoMP Based on
Relaxed Backhaul
1.20.2 Number of Used Downlink PRBs

Counters

.DL.Used.Avg number of used BTS3900 LTE
PDSCH PRBs



.DL.DrbUsed.A number of BTS3900 LTE
vg PRBs used by
PDSCH DRBs

.DL.SrbUsed.A number of BTS3900 LTE
vg PRBs used by
downlink
signaling in a
cell

.DL.PagingUse number of BTS3900 LTE
d.Avg PRBs used by
paging
messages in a
cell

vg.VoIP PRBs used by
DRBs on the
PDSCH for
downlink VoIP
services
Description
The counters measure the average number of PDSCH PRBs used and the average number of
service-specific PDSCH PRBs used. These counters are used to analyze the usage of
downlink PRBs. The counters do not involve simulated load. The average number of service-
specific PDSCH PRBs used is described as follows:
The L.ChMeas.PRB.DL.DrbUsed.Avg counter is used to analyze the usage of PRBs occupied
by downlink data services. The number of downlink PRBs used on the PDSCH is determined
by the downlink traffic volume and signal quality.
The L.ChMeas.PRB.DL.SrbUsed.Avg counter is used to analyze the usage of PRBs occupied
by downlink signaling messages.
The L.ChMeas.PRB.DL.PagingUsed.Avg counter is used to analyze the usage of PRBs
occupied by paging messages.
The L.ChMeas.PRB.DL.DrbUsed.Avg.VoIP counter is used to analyze the PDSCH PRB
usage of VoIP services.
Measurement Points
During a measurement period, the average number of PRBs used by the PDSCH, the average
number of PRBs used by PDSCH DRBs, the average number of PRBs used by signaling

(including SRB0, SRB1, and SRB2) in the PDSCH, the average number of PRBs used by
paging messages in the PDSCH, and the average number of PRBs used by DRBs in the
PDSCH for VoIP services are sampled per millisecond in a cell. (In an SFN cell, the number
of used PRBs in all physical cells corresponding to all sectors is accumulated.)
In LTE TDD system, only downlink subframes are measured. In cell combination scenarios,
Formula
None
Unit
None
Related Features
L.ChMeas.PRB.DL.Used.A Multi-mode: None

vg GSM: None
UMTS: None
L.ChMeas.PRB.DL.DrbUse Multi-mode: None

d.Avg GSM: None
UMTS: None
L.ChMeas.PRB.DL.SrbUse Multi-mode: None

d.Avg GSM: None
UMTS: None

L.ChMeas.PRB.DL.Paging Multi-mode: None

Used.Avg GSM: None
UMTS: None

d.Avg.VoIP GSM: None
UMTS: None
1.20.3 Number of Used PUCCH PRBs

Counters

.PUCCH.Avg number of used BTS3900 LTE
PRBs over the
PUCCH
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.(In an SFN cell, the number of used PRBs in all physical cells
corresponding to all sectors is accumulated.)
In LTE TDD mode, only uplink subframes are measured.In cell combination scenarios, the
number of used PRBs in all available physical cells is accumulated and then divided by the
number of available physical cells.

Formula
None
Unit
None
Related Features
L.ChMeas.PRB.PUCCH.Av Multi-mode: None

g GSM: None
UMTS: None
1.20.4 Number of OFDM Symbols Occupied by the PDCCH
Counters
1526728299 L.ChMeas.PDC Number of BTS3900, L

CH.SymNum.1 times the BTS3900 LTE
PDCCH
occupies one
symbol in a
measurement
period

PDCCH
occupies two
symbols in a
measurement
period

PDCCH
occupies three
symbols in a
measurement
period



PDCCH
occupies four
symbols in a
measurement
period
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.
Formula
None
Unit
None
Related Features
L.ChMeas.PDCCH.SymNu Multi-mode: None

m.1 GSM: None
UMTS: None
Physical Channel
Management


m.2 GSM: None
UMTS: None
Physical Channel
Management

m.3 GSM: None
UMTS: None
Physical Channel
Management

m.4 GSM: None
UMTS: None
Physical Channel
Management
1.20.5 Number of PDCCH CCEs used in a cell

Counters
1526728303 L.ChMeas.CCE Number of BTS3900, L

.CommUsed PDCCH CCEs BTS3900 LTE
used for
common DCI

.ULUsed PDCCH CCEs BTS3900 LTE
used for uplink
DCI in a
measurement
period



.DLUsed PDCCH CCEs BTS3900 LTE
used for
downlink DCI
in a
measurement
period

.Avail available BTS3900 LTE
PDCCH CCEs

.DLUsed.DRB PDCCH CCEs BTS3900 LTE
used for initial
transmitted
downlink data
in a cell

.DLUsed.SRB PDCCH CCEs BTS3900 LTE
used for initial
transmitted
downlink
signaling in a
cell

.DLUsed.MCE PDCCH CCEs BTS3900 LTE
used for initial
transmitted
downlink
MCEs in a cell

.ULUsed.Equiv PDCCH CCEs BTS3900 LTE
alent with the CCE
power
equivalent to
the reference
power used for
uplink DCI

.DLUsed.Equiv PDCCH CCEs BTS3900 LTE
alent with the CCE
power
equivalent to
the reference
power used for
downlink DCI



.ULUsed.TA PDCCH CCEs BTS3900 LTE
allocated for TA
measurement

.ULUsed.VoIP PDCCH CCEs BTS3900 LTE
used for uplink
VoIP services

.DLUsed.VoIP PDCCH CCEs BTS3900 LTE
used for
downlink VoIP
services

.ULUsed.SRB PDCCH CCEs BTS3900 LTE
used for initial
transmitted
uplink signaling
in a cell
Description
The counters measure the following items:
- Number of available CCEs in a cell
- Numbers of PDCCH CCEs used for 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
- Number of PDCCH CCEs used for TA measurement in a cell
- Number of PDCCH CCEs used for initial transmitted downlink data in a cell
- Number of PDCCH CCEs used for initial transmitted downlink signaling in a cell
- Number of PDCCH CCEs used for initial transmitted uplink signaling in a cell
- Number of PDCCH CCEs used for initial transmitted downlink MCEs in a cell
- Number of PDCCH CCEs equivalent to the reference power used for DCI.
where
The L.ChMeas.CCE.DLUsed.DRB counter measures the number of PDCCH CCEs used for
initial transmitted data scheduled on DRBs.
The L.ChMeas.CCE.DLUsed.SRB counter measures the number of PDCCH CCEs used for
initial transmitted signaling scheduled on SRB0, SRB1, and SRB 2.

The value of the L.ChMeas.CCE.DLUsed.Equivalent or L.ChMeas.CCE.ULUsed.Equivalent

counter equals the total power consumed by PDCCH CCEs used for downlink or uplink DCI
divided by the reference power of a CCE, respectively.
The reference power is a fixed power calculated based on the offset of the DCI power related
to the cell-specific reference signal power when the PDCCH carries dedicated DCI if the
PdcchPcSwitch option in the DlPcAlgoSwitch parameter is cleared. The cell-specific
reference signal power is specified by the ReferenceSignalPwr parameter.
The counters measure the number of available CCEs in a cell, the numbers 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, the number of PDCCH CCEs used for TA measurement in a cell, the number of
PDCCH CCEs used by initial transmitted downlink data in a cell, the number of PDCCH
CCEs used by initial transmitted downlink signaling in a cell, the number of PDCCH CCEs
used by initial transmitted downlink MCEs in a cell, and the number of PDCCH CCEs
equivalent to the reference power used by DCI.
where
The L.ChMeas.CCE.DLUsed.DRB counter measures the number of PDCCH CCEs used for
initial transmitted data scheduled on DRBs.
The L.ChMeas.CCE.DLUsed.SRB counter measures the number of PDCCH CCEs used for
initial transmitted signaling scheduled on SRB0, SRB1, and SRB 2.
The value of the L.ChMeas.CCE.DLUsed.Equivalent or L.ChMeas.CCE.ULUsed.Equivalent
counter equals the total power consumed by PDCCH CCEs used for downlink or uplink DCI
divided by the reference power of a CCE, respectively.
The reference power is a fixed power calculated based on the offset of the DCI power related
to the cell-specific reference signal power when the PDCCH carries dedicated DCI if the
PdcchPcSwitch option in the DlPcAlgoSwitch parameter is cleared. The cell-specific
reference signal power is specified by the ReferenceSignalPwr parameter.
The L.ChMeas.CCE.ULUsed.VoIP counter measures the number of PDCCH CCEs used for
uplink VoIP services that are correctly demodulated. The L.ChMeas.CCE.DLUsed.VoIP
counter measures the number of PDCCH CCEs used for downlink VoIP services.
The L.ChMeas.CCE.ULUsed.TA counter applies only to LTE FDD.
Measurement Points
The following items are measured within a measurement period in a cell:
- Number of available PDCCH CCEs
- Number of PDCCH CCEs used by each category of DCI
- Number of PDCCH CCEs used for different purposes in the downlink
- Numbers of PDCCH CCEs with the CCE power equivalent to the reference power used for
uplink and downlink DCI
- Number of PDCCH CCEs allocated for TA measurement
- Numbers of PDCCH CCEs used for uplink and downlink VoIP services

Formula
None
Unit
None
Related Features
L.ChMeas.CCE.CommUsed Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management
L.ChMeas.CCE.ULUsed Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management
L.ChMeas.CCE.DLUsed Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management
L.ChMeas.CCE.Avail Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management

L.ChMeas.CCE.DLUsed.D Multi-mode: None

RB GSM: None
UMTS: None
LBFD-002016 Management
Allocation
Dynamic Downlink Power
Allocation
L.ChMeas.CCE.DLUsed.SR Multi-mode: None

B GSM: None
UMTS: None
Allocation
Allocation
L.ChMeas.CCE.DLUsed.M Multi-mode: None

CE GSM: None
UMTS: None
Allocation
Allocation
L.ChMeas.CCE.ULUsed.Eq Multi-mode: None

uivalent GSM: None
UMTS: None
Allocation
Allocation

L.ChMeas.CCE.DLUsed.Eq Multi-mode: None

uivalent GSM: None
UMTS: None
Allocation
Allocation
L.ChMeas.CCE.ULUsed.TA Multi-mode: None

GSM: None
UMTS: None
L.ChMeas.CCE.ULUsed.Vo Multi-mode: None

IP GSM: None
UMTS: None
Physical Channel
Management
L.ChMeas.CCE.DLUsed.Vo Multi-mode: None

IP GSM: None
UMTS: None
Physical Channel
Management
L.ChMeas.CCE.ULUsed.SR Multi-mode: None

B GSM: None
UMTS: None

1.20.6 Average Number of PRBs Occupied by CA UEs in a Cell

Counters

.DL.PCell.Used number of BTS3900 LTE
.Avg downlink PRBs
occupied by CA
UEs that use the
local cell as
their primary
serving cell

.DL.SCell.Used number of BTS3900 LTE
.Avg downlink PRBs
occupied by CA
UEs that use the
local cell as
their secondary
serving cell
Description
The counter measures the 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. Note that for SFN cells, the number of used PRBs in each physical cell
is accumulated.
Formula
None
Unit
None

Related Features
L.ChMeas.PRB.DL.PCell.U Multi-mode: None

sed.Avg GSM: None
UMTS: None
LTE: LAOFD-00100101 Intra-Band Carrier
2CC in 20MHz
LAOFD-070201
Inter-Band Carrier
TDLAOFD-00100111 2CC in 20MHz
TDLAOFD-001002 Flexible CA from Multiple
TDLAOFD-00100102 Carriers
Coordinated BBU
Intra-band Carrier
2CC in 30MHz
Carriers
L.ChMeas.PRB.DL.SCell.U Multi-mode: None

sed.Avg GSM: None
UMTS: None
2CC in 20MHz
LAOFD-070201
Inter-Band Carrier
Coordinated BBU
Intra-band Carrier
2CC in 30MHz
Carriers

1.20.7 Average Number of Available PRBs in a Cell

Counters

.DL.Avail available BTS3900 LTE
downlink PRBs

.UL.Avail available uplink BTS3900 LTE
PRBs
Description
The counters measure the number of available uplink or downlink PRBs, which is related to
the cell bandwidth. In a cell with non-standard bandwidth, the number of actual available
PRBs is measured. In GL dynamic spectrum sharing scenarios, the number of available uplink
PRBs is the number of available uplink PRBs corresponding to the dedicated E-UTRAN
bandwidth, and the number of available downlink PRBs is the number of available downlink
PRBs corresponding to the LTE cell bandwidth. In carrier aggregation scenarios, if a cell is
configured as a secondary serving cell (SCell) and is not configured with an uplink frequency
band, the number of available uplink PRBs is 0.
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.Note that for SFN cells, the number of used PRBs in each physical cell is accumulated.
Formula
None
Unit
None

Related Features
L.ChMeas.PRB.DL.Avail Multi-mode: MRFD-090202 GSM and LTE FDD

GSM: None Dynamic Spectrum
Sharing(LTE FDD)
UMTS: None
LTE: LAOFD-001001
LAOFD-001002
LTE-A Introduction
LOFD-070205
TDLOFD-001075 Downlink 2CC in 40MHz
Adaptive SFN/SDMA
SFN
L.ChMeas.PRB.UL.Avail Multi-mode: MRFD-090202 GSM and LTE FDD

Sharing(LTE FDD)
UMTS: None
LTE: LAOFD-001001
LAOFD-001002
LTE-A Introduction
LOFD-070205
TDLOFD-001075 Downlink 2CC in 40MHz
Adaptive SFN/SDMA
SFN
1.20.8 Average Number of PRBs Used by ICIC CEUs in a Cell

Counters

.UL.CEU.Used. number of BTS3900 LTE
Avg PRBs used by
uplink CEUs in
a cell

.DL.CEU.Used. number of BTS3900 LTE
Avg PRBs used by
downlink CEUs
in a cell

Description
The counters measure the average number of PRBs used by uplink or downlink ICIC CEUs in
a cell.
Measurement Points
The average number of PRBs used by uplink or downlink ICIC CEUs per millisecond in a
cell is measured within the measurement period.
Formula
None
Unit
None
Related Features
L.ChMeas.PRB.UL.CEU.Us Multi-mode: None

ed.Avg GSM: None
UMTS: None
LOFD-060201
Adaptive Inter-Cell
Adaptive Inter-Cell

L.ChMeas.PRB.DL.CEU.Us Multi-mode: None

ed.Avg GSM: None
UMTS: None
LOFD-060201
Coordination
Adaptive Inter-Cell
Adaptive Inter-Cell
1.20.9 Average Number of PRBs Allocated for Frequency Selective

Scheduling
Counters

.UL.FSS.Avg number of BTS3900 LTE
PRBs allocated
for uplink
frequency
selective
scheduling

.DL.FSS.Avg number of BTS3900 LTE
PRBs allocated
for downlink
frequency
selective
scheduling
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. Note that for SFN cells and combination cells, the
number of used PRBs in each physical cell is accumulated.

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
L.ChMeas.PRB.UL.FSS.Av Multi-mode: None

g GSM: None
UMTS: None
L.ChMeas.PRB.DL.FSS.Av Multi-mode: None

g GSM: None
UMTS: None
1.20.10 Average Number of PRBs Allocated for Uplink Pre-

scheduling
Counters

.UL.PreSch.Use number of BTS3900 LTE
d.Avg PRBs allocated
for uplink pre-
scheduling

Description
The counter measures the average number of PRBs allocated for uplink pre-scheduling in a
cell. Note that for SFN cells and combination cells, the number of used PRBs in each physical
cell is accumulated.
Measurement Points
During a measurement period, the average number of PRBs allocated for uplink pre-
scheduling is measured in a cell per millisecond.
In LTE TDD mode, only uplink subframes are measured.
Formula
None
Unit
None
Related Features
L.ChMeas.PRB.UL.PreSch. Multi-mode: None

Used.Avg GSM: None
UMTS: None
LOFD-001059 UL Pre-allocation Based on
TDLOFD-001059 SPID
UL Pre-allocation Based on
SPID

1.20.11 Number of Times of DTX for PDCCH Resource Allocation

with a Specific Aggregation Level in a Cell
Counters

CH.DL.DTXNu times of DTX BTS3900 LTE
m.AggLvl1 for PDCCH
resource
allocation with
aggregation
level 1 in a cell

m.AggLvl2 for PDCCH
resource
allocation with
aggregation
level 2 in a cell

m.AggLvl4 for PDCCH
resource
allocation with
aggregation
level 4 in a cell

m.AggLvl8 for PDCCH
resource
allocation with
aggregation
level 8 in a cell
Description
After allocating downlink PDCCH resources, the eNodeB detects the ACK, NACK, or DTX
state of the corresponding PDSCH resource on the PUCCH or PUSCH. Each time the
eNodeB detects the DTX state, the corresponding counter is incremented by 1. The times of
PDCCH resource allocation without feedback (such as SIB, RAR, and paging messages) are
not counted in the counter. The counter is incremented by 1 if one of the following conditions
is met: (1) The UE does not detect downlink PDCCH resource allocation messages. (2) The
eNodeB falsely determines that ACK or NACK messages as DTX messages.

Measurement Points
The corresponding counter is incremented by 1 each time the eNodeB detects the DTX state
for downlink PDCCH resource allocation with aggregation level 1, 2, 4, or 8.
Formula
None
Unit
None
Related Features
L.ChMeas.PDCCH.DL.DT Multi-mode: None

XNum.AggLvl1 GSM: None
UMTS: None
Physical Channel
Management

UMTS: None
Physical Channel
Management

UMTS: None
Physical Channel
Management

UMTS: None
Physical Channel
Management

1.20.12 Number of Times of Successful PDCCH Resource

Allocations with a Specific Aggregation Level
Counters

CH.AggLvl1Nu times of BTS3900 LTE
m PDCCH
resource
allocations with
aggregation
level 1

m PDCCH
resource
allocations with
aggregation
level 2

m PDCCH
resource
allocations with
aggregation
level 4

m PDCCH
resource
allocations with
aggregation
level 8
Description
The counters measure the number of times downlink PDCCH resources with aggregation
level 1, 2, 4, or 8 are allocated. The times of PDCCH resource allocation in aggregation level
without feedback (such as SIB, RAR, and paging messages) are not counted.
Measurement Points
The corresponding counter is incremented by 1 each time the downlink PDCCH resources
with aggregation level 1, 2, 4, or 8 are successfully allocated.

Formula
None
Unit
None
Related Features
L.ChMeas.PDCCH.AggLvl Multi-mode: None

1Num GSM: None
UMTS: None
Physical Channel
Management

2Num GSM: None
UMTS: None
Physical Channel
Management

4Num GSM: None
UMTS: None
Physical Channel
Management

8Num GSM: None
UMTS: None
Physical Channel
Management

1.20.13 Average number of PRBs used for downlink CoMP

Counters

.DL.DLComp. number of BTS3900 LTE
Used.Avg PRBs used by
downlink
CoMP UEs in a
cell
Description
These counters measure the average number of PRBs used for downlink CoMP scheduling in
a cell.
Measurement Points
For JT UEs and DCS UEs, the value of this counter equals the number of PDSCH PRBs used
for downlink scheduling. For CBF UEs, the value of this counter equals the number of
PDSCH PRBs paired in the downlink.
In a measurement period, the eNodeB measures the average number of PRBs used for
downlink CoMP scheduling per second.
Formula
None
Unit
None
Related Features
L.ChMeas.PRB.DL.DLCom Multi-mode: None

p.Used.Avg GSM: None
UMTS: None
LTE: TDLAOFD-00100103 Intra-eNodeB DL CoMP in
TDLAOFD-003002 DCS Mode
Intra-eNodeB DL CoMP in
Adaptive Mode

1.20.14 Average Number of Available PUSCH PRBs in a Cell

Counters

.UL.PUSCH.Av available BTS3900 LTE
ail PUSCH PRBs
Description
The counter measures the number of available PRBs in the uplink, which is related to the
system bandwidth. The number of available PRBs on the PUSCH fluctuate within certain
range because the PRBs are dynamically allocated to the PUSCH.
The L.ChMeas.PRB.UL.PUSCH.Avail counter applies only to LTE TDD.
Measurement Points
The number of available PUSCH PRBs is sampled per millisecond. At the end of a
measurement period, the average value of the sampling results is used as the value of the
counter.
In single frequency network (SFN) scenarios, the value of the counter equals the total number
of available PUSCH PRBs in all physical cells. In a cell with customized bandwidth, the
number of available PUSCH PRBs is measured. In carrier aggregation scenarios, 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.
In an LTE TDD system, only uplink subframes are measured. In cell combination scenarios,
Formula
None
Unit
None

Related Features
L.ChMeas.PRB.UL.PUSCH Multi-mode: None

.Avail GSM: None
UMTS: None
1.20.15 Number of Times of DMRS TA Scheduling in a cell

Counters

CH.DmrsTaSch initial uplink BTS3900 LTE
transmissions of
DMRS TA in a
cell

CH.DmrsTaSch uplink BTS3900 LTE
.Retrans retransmissions
of DMRS TA in
a cell
Description
The eNodeB allocates the PUSCH resources according to related algorithms for DMRS TA
scheduling and HARQ retransmission. The counters measure the number of times of DMRS
TA scheduling on the PUSCH in a cell. The counters are used to analyze the overheads for
DMRS TA scheduling.
Measurement Points
The L.ChMeas.PUSCH.DmrsTaSch or L.ChMeas.PUSCH.DmrsTaSch.Retrans counter is
incremented by 1 each time the cell allocates the PUSCH resources in the uplink for the
DMRS TA. If the resource is for initial transmission, the L.ChMeas.PUSCH.DmrsTaSch
counter is incremented. If the resource is for retransmission, the
L.ChMeas.PUSCH.DmrsTaSch.Retrans counter is incremented.
Formula
None

Unit
None
Related Features
L.ChMeas.PUSCH.DmrsTa Multi-mode: None

Sch GSM: None
UMTS: None
L.ChMeas.PUSCH.DmrsTa Multi-mode: None

Sch.Retrans GSM: None
UMTS: None
1.20.16 Number of CCE Allocation Failures in a Cell
Counters

.UL.AllocFail uplink CCE BTS3900 LTE
allocation
failures in a cell

.DL.AllocFail downlink CCE BTS3900 LTE
allocation
failures in a cell
Description
The counters measure the number of PDCCH resource allocation failures in the uplink and the
number of PDCCH resource allocation failures in the downlink in a cell.
Measurement Points
The L.ChMeas.CCE.UL.AllocFail or L.ChMeas.CCE.DL.AllocFail counter is incremented by
1 each time the cell fails to allocate CCEs in the uplink or downlink.

Formula
None
Unit
None
Related Features
L.ChMeas.CCE.UL.AllocFa Multi-mode: None

il GSM: None
UMTS: None
Management
L.ChMeas.CCE.DL.AllocFa Multi-mode: None

il GSM: None
UMTS: None
Management
1.20.17 PUSCH PRB Usage Distribution
Counters

.PUSCH.Util.Sa samples with BTS3900 LTE
mp.Index0 the PUSCH
PRB usage
ranging within
index 0

mp.Index1 the PUSCH
PRB usage
ranging within
index 1



mp.Index2 the PUSCH
PRB usage
ranging within
index 2

mp.Index3 the PUSCH
PRB usage
ranging within
index 3

mp.Index4 the PUSCH
PRB usage
ranging within
index 4

mp.Index5 the PUSCH
PRB usage
ranging within
index 5

mp.Index6 the PUSCH
PRB usage
ranging within
index 6

mp.Index7 the PUSCH
PRB usage
ranging within
index 7

mp.Index8 the PUSCH
PRB usage
ranging within
index 8



mp.Index9 the PUSCH
PRB usage
ranging within
index 9
Description
The counters measure the PUSCH PRB usage ranging in different indexes. PRB usage
indexes (0 to 9) are defined as follows:
Index 0: [0, 10%)
Index 1: [10%, 20%)
Index 2: [20%, 30%)
Index 3: [30%, 40%)
Index 4: [40%, 50%)
Index 5: [50%, 60%)
Index 6: [60%, 70%)
Index 7: [70%, 80%)
Index 8: [80%, 90%)
Index 9: [90%, 100%]
Measurement Points
The number of used PUSCH PRBs and the number of available PUSCH PRBs in each TTI in
a cell (for cells configured with SFN, the numbers of used PRBs and available PRBs in each
physical cell should be accumulated; in a cell with non-standard bandwidth, the numbers of
actual used PRBs and available PRBs are measured; in a cell that is configured as an SCell
and is not configured with an uplink frequency band, the numbers are not contained in
counters) is sampled and accumulated per second. Then, the PUSCH PRB usage is calculated
by dividing the number of used PRBs by the number of available PRBs. The corresponding
counter is incremented by 1 based on the PUSCH PRB usage.
In the LTE TDD system, only uplink subframes are involved. In cell combination scenarios,
the number of used PUSCH PRBs and the number of available PUSCH PRBs in all the
physical cells corresponding to all sectors that are combined into a cell are accumulated.
Formula
None

Unit
None
Related Features
L.ChMeas.PRB.PUSCH.Uti Multi-mode: None

l.Samp.Index0 GSM: None
UMTS: None
LTE: LAOFD-001001 LTE-A Introduction
LAOFD-001002 Carrier Aggregation for
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling

UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling

UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling


UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling

UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling

UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling

UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling


UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling

UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling

UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling

1.20.18 Average Number of PRBs Allocated for Uplink TA

Measurement
Counters

.UL.TaSch.Use number of BTS3900 LTE
d.Avg PRBs allocated
for uplink TA
measurement
Description
The counters measure the average number of PRBs allocated for uplink TA measurement to
indicate the use of PRBs by uplink TA measurement.
The L.ChMeas.PRB.UL.TaSch.Used.Avg counter applies only to LTE FDD.
Measurement Points
During a measurement period, the average number of PRBs allocated for uplink TA
measurement is measured in a cell per millisecond. Note that for SFN cells and combination
cells, the number of used PRBs in each physical cell corresponding to each sector is
accumulated.
Formula
None
Unit
None
Related Features
L.ChMeas.PRB.UL.TaSch. Multi-mode: None

Used.Avg GSM: None
UMTS: None

1.20.19 PDSCH PRB Usage Distribution

Counters

.PDSCH.Util.Sa samples with BTS3900 LTE
mp.Index0 the PDSCH
PRB usage
ranging within
index 0

mp.Index1 the PDSCH
PRB usage
ranging within
index 1

mp.Index2 the PDSCH
PRB usage
ranging within
index 2

mp.Index3 the PDSCH
PRB usage
ranging within
index 3

mp.Index4 the PDSCH
PRB usage
ranging within
index 4

mp.Index5 the PDSCH
PRB usage
ranging within
index 5



mp.Index6 the PDSCH
PRB usage
ranging within
index 6

mp.Index7 the PDSCH
PRB usage
ranging within
index 7

mp.Index8 the PDSCH
PRB usage
ranging within
index 8

mp.Index9 the PDSCH
PRB usage
ranging within
index 9
Description
The counters measure the PDSCH PRB usage ranging in different indexes. PRB usage
indexes (0 to 9) are defined as follows:
Index 0: [0, 10%)
Index 1: [10%, 20%)
Index 2: [20%, 30%)
Index 3: [30%, 40%)
Index 4: [40%, 50%)
Index 5: [50%, 60%)
Index 6: [60%, 70%)
Index 7: [70%, 80%)
Index 8: [80%, 90%)
Index 9: [90%, 100%]

Measurement Points
The number of used PDSCH PRBs and the number of available PDSCH PRBs in each TTI in
a cell (for cells configured with SFN, the numbers of used PRBs and available PRBs in each
physical cell should be accumulated; in a cell with non-standard bandwidth, the numbers of
actual used PRBs and available PRBs are measured) are sampled and accumulated per
second. Then, the PDSCH PRB usage is calculated by dividing the number of used PRBs by
the number of available PRBs. The corresponding counter is incremented by 1 based on the
PDSCH PRB usage.
In the LTE TDD system, only downlink subframes are involved. In cell combination
scenarios, the number of used PDSCH PRBs and the number of available PDSCH PRBs in all
the physical cells corresponding to all sectors that are combined into a cell are accumulated. If
downlink data is transmitted in the downlink pilot timeslot (DwPTS) of a special subframe,
the number of used PDSCH PRBs and the number of available PDSCH PRBs in the special
subframe are sampled. In cell combination scenarios, the number of used PDSCH PRBs and
the number of available PDSCH PRBs in all the physical cells corresponding to all sectors
that are combined into a cell are accumulated.
Formula
None
Unit
None
Related Features
L.ChMeas.PRB.PDSCH.Uti Multi-mode: None

UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling


UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling

UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling

UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling

UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling


UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling

UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling

UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling

UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling


UMTS: None
TDLOFD-001075
SFN
LBFD-002025
Basic Scheduling
TDLBFD-002025
Basic Scheduling
1.20.20 Number of PRBs Occupied by Inter-eNodeB CA UEs that

Treat the Local Cell as Their PCell or SCell
Counters

.DL.PCell.Rela downlink PRBs BTS3900 LTE
xedBackhaulC occupied by
AUsed.Avg inter-eNodeB
CA UEs that
treat the local
cell as their
PCell

.DL.SCell.Rela downlink PRBs BTS3900 LTE
xedBackhaulC occupied by
AUsed.Avg inter-eNodeB
CA UEs that
treat the local
cell as their
SCell
Description
The counters measures the number of PRBs occupies by inter-eNodeB CA UEs that treat the
local cell as their PCell or SCell.
Measurement Points
In a measurement period, the average number of PRBs occupied by CA UEs that treat the
local cell as their PCell or SCell on the PDSCH is measured.

Formula
None
Unit
None
Related Features
L.ChMeas.PRB.DL.PCell.R Multi-mode: None

elaxedBackhaulCAUsed.Av GSM: None
g
UMTS: None
Relaxed Backhaul
L.ChMeas.PRB.DL.SCell.R Multi-mode: None

elaxedBackhaulCAUsed.Av GSM: None
g
UMTS: None
Relaxed Backhaul
1.20.21 Average Number of Uplink PRBs Occupied by CA UEs

that Are in the Uplink CA State (Each with at Least One Uplink
SCC Configured) and Treat the Local Cell as Their PCell or SCell
Counters

.UL.PCell.Used number of BTS3900 LTE
.Avg uplink PRBs
occupied by CA
UEs that treat
the local cell as
their PCell



.UL.SCell.Used number of BTS3900 LTE
.Avg uplink PRBs
occupied by CA
UEs that treat
the local cell as
their SCell
Description
The counters measure the average number of uplink PRBs occupied by CA UEs that are in the
uplink CA state (each with at least one uplink SCC configured) and treat the local cell as their
PCell or SCell.
Measurement Points
In a measurement period, the average number of PUSCH PRBs occupied by CA UEs that are
in the uplink CA state (each with at least one uplink SCC configured) and treat the local cell
as their PCell or SCell is measured.
Formula
None
Unit
None
Related Features
L.ChMeas.PRB.UL.PCell.U Multi-mode: None

sed.Avg GSM: None
UMTS: None
Uplink 2CC

L.ChMeas.PRB.UL.SCell.U Multi-mode: None

sed.Avg GSM: None
UMTS: None
Uplink 2CC
1.20.22 Number of PRBs of the Downlink Edge Band in Adaptive

ICIC
Counters

.DL.AICIC.CE PRBs of the BTS3900 LTE
B.Avg downlink edge
band configured
for the cell in
adaptive ICIC
Description
The counter measures the number of PRBs of the downlink edge band configured for the cell.
Measurement Points
The number of PRBs of the downlink edge band configured for the cell in adaptive ICIC is
collected per second. At the end of a measurement period, the average of these collected
numbers is used as the L.ChMeas.PRB.DL.AICIC.CEB.Avg counter value.
Formula
None
Unit
None

Related Features
L.ChMeas.PRB.DL.AICIC. Multi-mode: None

CEB.Avg GSM: None
UMTS: None
LTE: LBFD-002002 Transport Channel
Transport Channel
Management
1.20.23 Average Number of PRBs Used for Inter-eNodeB DL

CoMP Scheduling in a Cell
Counters

.InterEnbDLCo number of BTS3900 LTE
mp.Used.Avg PRBs used for
inter-eNodeB
DL CoMP
scheduling in a
cell
Description
The counter measures the average number of PRBs scheduled for inter-eNodeB DL CoMP in
a cell.
The L.ChMeas.PRB.InterEnbDLComp.Used.Avg counter applies only to LTE TDD.
Measurement Points
Inter-eNodeB DL CoMP scheduling PRBs refer to the occupied PRBs in the resource position
pre-allocated to CBF UEs. In a measurement period, the eNodeB measures the average
number of PRBs used for inter-eNodeB DL CoMP scheduling each millisecond.
Formula
None
Unit
None

Related Features
L.ChMeas.PRB.InterEnbDL Multi-mode: None

Comp.Used.Avg GSM: None
UMTS: None
TDLAOFD-081411 Intra-eNodeB DL CoMP in
Adaptive Mode
TDLAOFD-110408
Inter-eNodeB DL CoMP
based on Relaxed backhaul
Based on Coordinated BBU
1.20.24 Number of Used Uplink PRBs on the PUSCH on the

UMTS and LTE Shared Spectrum in a Cell
Counters
1526737761 L.ChMeas.PRB Number of used BTS3900, L

.UL.ULShared. uplink PRBs on BTS3900 LTE
Used.Avg the PUSCH on
the UMTS and
LTE shared
spectrum in a
cell
Description
The counter measures the number of used uplink PRBs on the PUSCH on the UMTS and LTE
shared spectrum in a cell.
Measurement Points
The number of used uplink PRBs on the PUSCH on the UMTS and LTE shared spectrum in a
cell is sampled per millisecond within a measurement period. At the end of a measurement
period, the average of these sampling results is taken as the
L.ChMeas.PRB.UL.ULShared.Used.Avg counter value.
Formula
None

Unit
None
Related Features
L.ChMeas.PRB.UL.ULShar Multi-mode: MRFD-101221 UL Refarming Zero

ed.Used.Avg GSM: None Bufferzone
UMTS: None
LTE: None
1.20.25 Average Number of Standardized PRBs Used for

Downlink Services
Counters

vg.VoIP.Equival standardized
ent PRBs used for
downlink VoIP
services

vg.Equivalent standardized
PRBs used for
downlink
services
Description
The counters measure the average number of standardized PRBs used by the PDSCH DRBs
and the average number of standardized PRBs used by PDSCH DRBs for VoIP services. The
counters are used to analyze the usage of downlink PRBs.
The counters are used only for LTE TDD.
Measurement Points
During a measurement period, the average number of standardized PRBs used by the PDSCH
DRBs and the average number of standardized PRBs used by PDSCH DRBs for VoIP

services are sampled per millisecond in a cell. (In an SFN cell, the number of used PRBs in all
physical cells corresponding to all sectors is accumulated.)
In an LTE TDD system, only downlink subframes are measured. In cell combination
scenarios, the number of used PRBs in all available physical cells is accumulated and then
divided by the number of available physical cells.
measurement result of the corresponding counter has a deviation.
Formula
None
Unit
None
Related Features

d.Avg.VoIP.Equivalent GSM: None
UMTS: None

d.Avg.Equivalent GSM: None
UMTS: None
1.21 MAC Measurement (Traffic.MAC.Cell)

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
Description
1526727352 L.Traffic.BCH.TB. Total number of bits BTS3900:

bits of TBs transmitted V100R008C00
on the BCH BTS3900 LTE:
V100R003C00


Description
1526727353 L.Traffic.PCH.TB. Total number of bits BTS3900:

bits of TBs transmitted V100R008C00
on the PCH BTS3900 LTE:
V100R003C00
1526727354 L.Traffic.DL.SCH. Number of TBs BTS3900:

QPSK.TB initially transmitted V100R008C00
on the downlink BTS3900 LTE:
SCH in QPSK version earlier than
modulation mode V100R003C00

16QAM.TB initially transmitted V100R008C00
SCH in 16QAM version earlier than

1526727357 L.Traffic.DL.SCH. Number of bits of BTS3900:

QPSK.TB.bits TBs initially V100R008C00
transmitted on the BTS3900 LTE:
downlink SCH in version earlier than
QPSK modulation V100R003C00
mode

16QAM.TB.bits TBs initially V100R008C00
16QAM modulation V100R003C00
mode

mode

QPSK.TB.Retrans retransmitted on the V100R008C00
downlink SCH in BTS3900 LTE:
QPSK modulation version earlier than
mode V100R003C00


Description

16QAM.TB.Retran retransmitted on the V100R008C00
s downlink SCH in BTS3900 LTE:
16QAM modulation version earlier than
mode V100R003C00

s downlink SCH in BTS3900 LTE:
mode V100R003C00

QPSK.TB.Retrans. TBs retransmitted V100R008C00
bits on the downlink BTS3900 LTE:
SCH in QPSK version earlier than

16QAM.TB.Retran TBs retransmitted V100R008C00
s.bits on the downlink BTS3900 LTE:

s.bits on the downlink BTS3900 LTE:
1526727366 L.Traffic.UL.SCH. Number of TBs BTS3900:

QPSK.TB initially transmitted V100R008C00
on the uplink SCH BTS3900 LTE:
in QPSK modulation version earlier than
mode V100R003C00

in 16QAM version earlier than



Description
1526727369 L.Traffic.UL.SCH. Number of bits of BTS3900:

QPSK.TB.bits TBs initially V100R008C00
uplink SCH in version earlier than
QPSK modulation V100R003C00
mode

mode

mode

QPSK.TB.Retrans retransmitted on the V100R008C00
uplink SCH in BTS3900 LTE:
QPSK modulation version earlier than
mode V100R003C00

s uplink SCH in BTS3900 LTE:
mode V100R003C00

s uplink SCH in BTS3900 LTE:
mode V100R003C00

QPSK.TB.Retrans. TBs retransmitted V100R008C00
bits on the uplink SCH BTS3900 LTE:
in QPSK modulation version earlier than
mode V100R003C00

s.bits on the uplink SCH BTS3900 LTE:


Description

s.bits on the uplink SCH BTS3900 LTE:
1526728180 L.Traffic.DL.SCH. Number of downlink BTS3900:

QPSK.ErrTB.Ibler error TBs after V100R008C00
initial transmission BTS3900 LTE:
in QPSK modulation V100R003C00
mode

QPSK.ErrTB.Rble error TBs after the V100R008C00
r maximum number BTS3900 LTE:
of retransmissions in V100R003C00
QPSK modulation
mode is reached

16QAM.ErrTB.Ibl error TBs after V100R008C00
er initial transmission BTS3900 LTE:
in 16QAM V100R003C00
modulation mode

16QAM.ErrTB.Rbl error TBs after the V100R008C00
er maximum number BTS3900 LTE:
16QAM modulation
mode is reached

modulation mode

64QAM modulation
mode is reached
1526728186 L.Traffic.UL.SCH. Number of uplink BTS3900:

QPSK.ErrTB.Ibler error TBs after V100R008C00
initial transmission BTS3900 LTE:
in QPSK modulation V100R003C00
mode


Description

QPSK.ErrTB.Rble error TBs after the V100R008C00
r maximum number BTS3900 LTE:
QPSK modulation
mode is reached

modulation mode

16QAM modulation
mode is reached

modulation mode

64QAM modulation
mode is reached
1526728598 L.Traffic.UL.SCH. Maximum uplink BTS3900:

bits.Max traffic volume for V100R008C00
MAC TBs in a cell BTS3900 LTE:
V100R008C00
1526728663 L.Traffic.DL.SCH. Maximum downlink BTS3900:

bits.Max traffic volume for V100R008C00
MAC TBs in a cell BTS3900 LTE:
V100R008C00

Shared.TB.bits TBs initially V100R009C00
downlink SCH in V100R009C00
the shared spectrum


Description

Shared.TB initially transmitted V100R009C00
SCH in the shared V100R009C00
spectrum

Shared.ErrTB.Ible TBs failed to be V100R009C00
r.bits transmitted during BTS3900 LTE:
initial transmission V100R009C00
on the downlink
SCH in the shared
spectrum

Shared.ErrTB.Ible failed to be V100R009C00
r transmitted during BTS3900 LTE:
initial transmission V100R009C00
on the downlink
SCH in the shared
spectrum
1526729872 L.Thrp.Time.DL.S Duration of BTS3900:

hared downlink scheduling V100R009C00
in the shared BTS3900 LTE:
spectrum V100R009C00
1526729873 L.Thrp.Time.DL.D Duration of BTS3900:

edicated downlink scheduling V100R009C00
in the dedicated BTS3900 LTE:
1526729874 L.ChMeas.PRB.Sh Average number of BTS3900:

ared.DL.Used.Avg used downlink PRBs V100R009C00
1526729875 L.Traffic.Schedule. Number of times of BTS3900:

Shared.Avg downlink scheduling V100R009C00
1526729876 L.Traffic.Schedule. Number of times of BTS3900:

Dedicated.Avg downlink scheduling V100R009C00
in the dedicated BTS3900 LTE:
1526730124 L.Traffic.PktInterv Number of times the BTS3900:

al.Num.Index0 packet transmission V100R009C00
interval for a UE in BTS3900 LTE:
a cell ranges within V100R009C00
index 0


Description

index 1

index 2

index 3

index 4

index 5

index 6

index 7

index 8


Description

PoorChannelQuali- error TBs after the V100R010C00
ty.ErrTB.Rbler maximum number BTS3900 LTE:
of retransmissions is V100R010C00
reached for UEs
with poor channel
quality

PoorChannelQuali- error TBs after the V100R010C00
ty.ErrTB.Rbler maximum number BTS3900 LTE:
of retransmissions is V100R010C00
reached for UEs
with poor channel
quality

PoorChannelQuali- initially transmitted V100R010C00
ty.TB on the uplink SCH BTS3900 LTE:
for UEs with poor V100R010C00
channel quality

PoorChannelQuali- initially transmitted V100R010C00
ty.TB on the downlink BTS3900 LTE:
SCH for UEs with V100R010C00
poor channel quality
1526730872 L.Traffic.Sch.UL.N Number of times BTS3900:

um that UEs are V100R009C00
scheduled in a cell BTS3900 LTE:
in the uplink V100R009C00
1526730873 L.Traffic.Sch.DL.N Number of times BTS3900:

um that UEs are V100R009C00
scheduled in a cell BTS3900 LTE:
in the downlink V100R009C00
1526735156 L.Traffic.DL.SCH. Number of handover BTS3900:

HOCmd.TB command TBs V100R009C00
initially transmitted BTS3900 LTE:
on the downlink V100R009C00
SCH

HOCmd.ErrTB.Ibl error TBs for V100R009C00
er handover commands BTS3900 LTE:
after initial V100R009C00
transmission


Description

HOCmd.ErrTB.Rb error TBs for V100R009C00
ler handover commands BTS3900 LTE:
after the maximum V100R009C00
number of
retransmissions is
reached

RRCRel.ErrTB.Ibl failed to be V100R008C02
er transmitted for RRC BTS3900 LTE:
CONN REL V100R008C02
messages during
initial transmission
on the downlink
SCH

RRCRel.ErrTB.Rb failed to be V100R008C02
ler transmitted for RRC BTS3900 LTE:
CONN REL V100R008C02
messages after the
maximum number
of retransmissions is
reached on the
downlink SCH

RRCRel.TB initially transmitted V100R008C02
for RRC CONN BTS3900 LTE:
REL messages on V100R008C02
the downlink SCH

QPSK.TB.NACK TBs with a NACK- V100R010C10
HARQ feedback for BTS3900 LTE:
the initial V100R010C10
transmission in
QPSK modulation
mode

16QAM.TB.NACK TBs with a NACK- V100R010C10
transmission in
16QAM modulation
mode


Description

transmission in
64QAM modulation
mode

QPSK.TB.NACK TBs with a NACK- V100R010C10
transmission in
QPSK modulation
mode

transmission in
16QAM modulation
mode

transmission in
64QAM modulation
mode
1526737724 L.Traffic.UL.SCH. Number of QCI-1 BTS3900:

QPSK.TB.QCI.1 Service TBs initially V100R010C10
uplink SCH in V100R010C10
QPSK modulation
mode

16QAM.TB.QCI.1 Service TBs initially V100R010C10
16QAM modulation
mode


Description

64QAM modulation
mode

QPSK.TB.Retrans. Service TBs V100R010C10
QCI.1 retransmitted on the BTS3900 LTE:
QPSK modulation
mode

16QAM.TB.Retran Service TBs V100R010C10
s.QCI.1 retransmitted on the BTS3900 LTE:
16QAM modulation
mode

64QAMmodulation
mode

QPSK.ErrTB.Ibler. Service TBs with V100R010C10
QCI.1 initial transmission BTS3900 LTE:
failures on the V100R010C10
uplink SCH in
QPSK modulation
mode

16QAM.ErrTB.Ibl Service TBs with V100R010C10
er.QCI.1 initial transmission BTS3900 LTE:
uplink SCH in
16QAM modulation
mode

uplink SCH in
64QAM modulation
mode


Description
1526737733 L.Traffic.DL.SCH. Number of QCI-1 BTS3900:

QPSK.TB.QCI.1 Service TBs initially V100R010C10
QPSK modulation
mode

16QAM modulation
mode

64QAM modulation
mode

QPSK.TB.Retrans. Service TBs V100R010C10
QCI.1 retransmitted on the BTS3900 LTE:
QPSK modulation
mode

16QAM modulation
mode

64QAM modulation
mode

QPSK.ErrTB.Ibler. Service TBs with V100R010C10
QCI.1 initial transmission BTS3900 LTE:
downlink SCH in
QPSK modulation
mode


Description

downlink SCH in
16QAM modulation
mode

downlink SCH in
64QAM modulation
mode
1526737858 L.Traffic.DL.SCH. Number of service BTS3900:

QPSK.DRB.TB data TBs initially V100R010C10
QPSK modulation
mode

16QAM.DRB.TB data TBs initially V100R010C10
16QAM modulation
mode

64QAM.DRB.TB data TBs initially V100R010C10
64QAM modulation
mode

QPSK.DRB.TB.Ret data TBs V100R010C10
rans retransmitted on the BTS3900 LTE:
QPSK modulation
mode

16QAM.DRB.TB.R data TBs V100R010C10
etrans retransmitted on the BTS3900 LTE:
16QAM modulation
mode


Description

64QAM.DRB.TB.R data TBs V100R010C10
etrans retransmitted on the BTS3900 LTE:
64QAM modulation
mode

QPSK.DRB.ErrTB error service data V100R010C10
.Ibler TBs after initial BTS3900 LTE:
transmission in V100R010C10
QPSK modulation
mode

16QAM.DRB.ErrT error service data V100R010C10
B.Ibler TBs after initial BTS3900 LTE:
16QAM modulation
mode

B.Ibler TBs after initial BTS3900 LTE:
64QAM modulation
mode

QPSK.DRB.ErrTB error service data V100R010C10
.Rbler TBs after the BTS3900 LTE:
maximum number V100R010C10
of retransmissions in
QPSK modulation
mode is reached

B.Rbler TBs after the BTS3900 LTE:
16QAM modulation
mode is reached

B.Rbler TBs after the BTS3900 LTE:
64QAM modulation
mode is reached

L.Traffic.UL.SCH.QPSK.ErrTB.Ibler L.Traffic.UL.SCH.QPSK.TB.NACK
L.Traffic.UL.SCH.16QAM.ErrTB.Ibler L.Traffic.UL.SCH.16QAM.TB.NACK
L.Traffic.UL.SCH.64QAM.ErrTB.Ibler L.Traffic.UL.SCH.64QAM.TB.NACK
1.21.1 Total Number of Bits of TBs Transmitted on the BCH

Counters
1526727352 L.Traffic.BCH. Total number of BTS3900, L

TB.bits bits of TBs BTS3900 LTE
transmitted on
the BCH
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 ofsystem 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
L.Traffic.BCH.TB.bits Multi-mode: None

GSM: None
UMTS: None
TDLBFD-002002 Modulation: DL/UL QPSK,
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM
1.21.2 Total Number of Bits of TBs Transmitted on the PCH

Counters
1526727353 L.Traffic.PCH. Total number of BTS3900, L

TB.bits bits of TBs BTS3900 LTE
transmitted on
the PCH
Description
The air interface paging message is transmitted on the paging channel (PCH). The counter
measures the 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
L.Traffic.PCH.TB.bits Multi-mode: None

GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM
1.21.3 Number of TBs Initially Transmitted on the Downlink

SCH
Counters
1526727354 L.Traffic.DL.S Number of TBs BTS3900, L

CH.QPSK.TB initially BTS3900 LTE
transmitted on
the downlink
SCH in QPSK
modulation
mode

CH.16QAM.TB initially BTS3900 LTE
transmitted on
the downlink
SCH in
16QAM
modulation
mode



transmitted on
the downlink
SCH in
64QAM
modulation
mode
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.These counters do
not involve simulated load.
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.
Formula
None
Unit
None

Related Features
L.Traffic.DL.SCH.QPSK.T Multi-mode: None

B GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM
L.Traffic.DL.SCH. Multi-mode: None

16QAM.TB GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

64QAM.TB GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

1.21.4 Number of Bits of TBs Initially Transmitted on the

Downlink SCH
Counters
1526727357 L.Traffic.DL.S Number of bits BTS3900, L

CH.QPSK.TB.b of TBs initially BTS3900 LTE
its transmitted on
the downlink
SCH in QPSK
modulation
mode

CH. of TBs initially BTS3900 LTE
16QAM.TB.bit transmitted on
s the downlink
SCH in
16QAM
modulation
mode

s the downlink
SCH in
64QAM
modulation
mode
Description
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.These
counters do not involve simulated load.
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.

Formula
None
Unit
bit
Related Features

B.bits GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

16QAM.TB.bits GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM


UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM
1.21.5 Number of TBs Retransmitted on the Downlink SCH

Counters

CH.QPSK.TB. retransmitted on BTS3900 LTE
Retrans the downlink
SCH in QPSK
modulation
mode

CH. retransmitted on BTS3900 LTE
16QAM.TB.Ret the downlink
rans SCH in
16QAM
modulation
mode

64QAM.TB.Ret the downlink
rans SCH in
64QAM
modulation
mode

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
eNodeB retransmits a TB on the downlink SCH.
Formula
None
Unit
None
Related Features

B.Retrans GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM


16QAM.TB.Retrans GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM
1.21.6 Number of Bits of TBs Retransmitted on the Downlink

SCH
Counters

CH.QPSK.TB. of TBs BTS3900 LTE
Retrans.bits retransmitted on
the downlink
SCH in QPSK
modulation
mode



CH. of TBs BTS3900 LTE
16QAM.TB.Ret retransmitted on
rans.bits the downlink
SCH in
16QAM
modulation
mode

rans.bits the downlink
SCH in
64QAM
modulation
mode
Description
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
modulation mode each time the eNodeB retransmits a TB on the downlink SCH.
Formula
None
Unit
bit

Related Features

B.Retrans.bits GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

16QAM.TB.Retrans.bits GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

1.21.7 Number of TBs Initially Transmitted on the Uplink SCH
Counters
1526727366 L.Traffic.UL.S Number of TBs BTS3900, L

CH.QPSK.TB initially BTS3900 LTE
transmitted on
the uplink SCH
in QPSK
modulation
mode

transmitted on
the uplink SCH
in 16QAM
modulation
mode

transmitted on
the uplink SCH
in 64QAM
modulation
mode
Description
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
eNodeB receives a TB initially transmitted on the uplink SCH.
Formula
None

Unit
None
Related Features
L.Traffic.UL.SCH.QPSK.T Multi-mode: None

B GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM
L.Traffic.UL.SCH. Multi-mode: None

16QAM.TB GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

64QAM.TB GSM: None
UMTS: None
LOFD-001006 Management
TDLBFD-002002 UL 64QAM
TDLOFD-001006 Transport Channel
Management
UL 64QAM

1.21.8 Number of bits of TBs Initially Transmitted on the Uplink

SCH
Counters
1526727369 L.Traffic.UL.S Number of bits BTS3900, L

CH.QPSK.TB.b of TBs initially BTS3900 LTE
its transmitted on
the uplink SCH
in QPSK
modulation
mode

s the uplink SCH
in 16QAM
modulation
mode

s the uplink SCH
in 64QAM
modulation
mode
Description
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
modulation mode each time the eNodeB receives a TB initially transmitted on the uplink
SCH.
Formula
None

Unit
bit
Related Features

B.bits GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None
Management
UL 64QAM

1.21.9 Number of TBs Retransmitted on the Uplink SCH
Counters

CH.QPSK.TB. retransmitted on BTS3900 LTE
Retrans the uplink SCH
in QPSK
modulation
mode

16QAM.TB.Ret the uplink SCH
rans in 16QAM
modulation
mode

64QAM.TB.Ret the uplink SCH
rans in 64QAM
modulation
mode
Description
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 over the uplink
SCH in QPSK, 16QAM, and 64QAM modulation modes in a cell, respectively.
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.
Formula
None
Unit
None

Related Features

B.Retrans GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None
Management
UL 64QAM

1.21.10 Number of bits of TBs Retransmitted on the Uplink SCH
Counters

CH.QPSK.TB. of TBs BTS3900 LTE
Retrans.bits retransmitted on
the uplink SCH
in QPSK
modulation
mode

rans.bits the uplink SCH
in 16QAM
modulation
mode

rans.bits the uplink SCH
in 64QAM
modulation
mode
Description
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
modulation mode each time the eNodeB receives a TB retransmitted on the uplink SCH.
Formula
None

Unit
bit
Related Features

B.Retrans.bits GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None
Management
UL 64QAM

1.21.11 Number of Downlink Error TBs After Initial Transmission

Counters
1526728180 L.Traffic.DL.S Number of BTS3900, L

CH.QPSK.ErrT downlink error BTS3900 LTE
B.Ibler TBs after initial
transmission in
QPSK
modulation
mode

CH. downlink error BTS3900 LTE
16QAM.ErrTB. TBs after initial
Ibler transmission in
16QAM
modulation
mode

64QAM
modulation
mode

CH.QPSK.TB. downlink TBs BTS3900 LTE
NACK with a NACK-
HARQ
feedback for the
initial
transmission in
QPSK
modulation
mode

CH. downlink TBs BTS3900 LTE
16QAM.TB.N with a NACK-
ACK HARQ
feedback for the
initial
transmission in
16QAM
modulation
mode



CH. downlink TBs BTS3900 LTE
64QAM.TB.N with a NACK-
ACK HARQ
feedback for the
initial
transmission in
64QAM
modulation
mode
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
L.Traffic.DL.SCH.QPSK.Er Multi-mode: None

rTB.Ibler GSM: None
UMTS: None
Transport Channel
Management


16QAM.ErrTB.Ibler GSM: None
UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management

B.NACK GSM: None
UMTS: None
Transport Channel
Management

16QAM.TB.NACK GSM: None
UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management

1.21.12 Number of Downlink Error TBs After the Maximum

Number of Retransmissions Is Reached
Counters

CH.QPSK.ErrT downlink error BTS3900 LTE
B.Rbler TBs after the
maximum
number of
retransmissions
in QPSK
modulation
mode is reached

16QAM.ErrTB. TBs after the
Rbler maximum
number of
retransmissions
in 16QAM
modulation
mode is reached

Rbler maximum
number of
retransmissions
in 64QAM
modulation
mode is reached
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
eNodeB receives a downlink error TB indicator after the maximum number of retransmissions
is reached.

Formula
None
Unit
None
Related Features

rTB.Rbler GSM: None
UMTS: None
Transport Channel
Management

16QAM.ErrTB.Rbler GSM: None
UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management

1.21.13 Number of Uplink Error TBs After Initial Transmission

Counters
1526728186 L.Traffic.UL.S Number of BTS3900, L

CH.QPSK.ErrT uplink error BTS3900 LTE
B.Ibler TBs after initial
transmission in
QPSK
modulation
mode

CH. uplink error BTS3900 LTE
16QAM
modulation
mode

64QAM
modulation
mode

CH.QPSK.TB. uplink TBs with BTS3900 LTE
NACK a NACK-
HARQ
feedback for the
initial
transmission in
QPSK
modulation
mode

CH. uplink TBs with BTS3900 LTE
16QAM.TB.N a NACK-
ACK HARQ
feedback for the
initial
transmission in
16QAM
modulation
mode



CH. uplink TBs with BTS3900 LTE
64QAM.TB.N a NACK-
ACK HARQ
feedback for the
initial
transmission in
64QAM
modulation
mode
Description
The counters measure the number of uplink error TBs after initial transmission in QPSK,
16QAM, and 64QAM modulation mode.
Measurement Points
eNodeB receives an uplink error TB after initial transmission.The corresponding counter is
incremented by 1 based on the modulation mode each time the eNodeB receives an uplink TB
with a NACK-HARQ feedback after initial transmission.
Formula
None
Unit
None
Related Features
L.Traffic.UL.SCH.QPSK.Er Multi-mode: None

rTB.Ibler GSM: None
UMTS: None
Transport Channel
Management


UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management

B.NACK GSM: None
UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management

1.21.14 Number of Uplink Error TBs After the Maximum Number

of Retransmissions Is Reached
Counters

CH.QPSK.ErrT uplink error BTS3900 LTE
B.Rbler TBs after the
maximum
number of
retransmissions
in QPSK
modulation
mode is reached

Rbler maximum
number of
retransmissions
in 16QAM
modulation
mode is reached

Rbler maximum
number of
retransmissions
in 64QAM
modulation
mode is reached
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
eNodeB receives an uplink error TB after the maximum number of retransmissions is reached.
Formula
None

Unit
None
Related Features

rTB.Rbler GSM: None
UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management
1.21.15 Maximum Traffic Volume for MAC TBs in a Cell

Counters
1526728598 L.Traffic.UL.S Maximum BTS3900, L

CH.bits.Max uplink traffic BTS3900 LTE
volume for
MAC TBs in a
cell


1526728663 L.Traffic.DL.S Maximum BTS3900, L

CH.bits.Max downlink traffic BTS3900 LTE
volume for
MAC TBs in a
cell
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
L.Traffic.UL.SCH.bits.Max Multi-mode: None

GSM: None
UMTS: None
L.Traffic.DL.SCH.bits.Max Multi-mode: None

GSM: None
UMTS: None

1.21.16 Number of Bits of TBs Initially Transmitted on the

Downlink SCH in the Shared Spectrum
Counters

CH.Shared.TB. of TBs initially BTS3900 LTE
bits transmitted on
the downlink
SCH in the
shared spectrum
Description
The counter measures the number of bits of TBs initially transmitted on the downlink SCH in
the shared spectrum when GL dynamic spectrum sharing is enabled.
Measurement Points
When GL dynamic spectrum sharing is enabled, the L.Traffic.DL.SCH.Shared.TB.bits
counter is incremented by the number of bits of the TB each time the eNodeB sends a TB
initially transmitted on the downlink SCH in the shared spectrum.
Formula
None
Unit
bit
Related Features
L.Traffic.DL.SCH.Shared.T Multi-mode: MRFD-090202 GSM and LTE FDD

B.bits GSM: None Dynamic Spectrum
Sharing(LTE FDD)
UMTS: None
LTE: None

1.21.17 Number of TBs Initially Transmitted on the Downlink

SCH in the Shared Spectrum
Counters

CH.Shared.TB initially BTS3900 LTE
transmitted on
the downlink
SCH in the
shared spectrum
Description
The counter measures the number of TBs initially transmitted on the downlink SCH in the
shared spectrum when GL dynamic spectrum sharing is enabled.
Measurement Points
When GL dynamic spectrum sharing is enabled, the L.Traffic.DL.SCH.Shared.TB counter is
incremented by 1 each time the eNodeB sends a TB initially transmitted on the downlink
SCH in the shared spectrum.
Formula
None
Unit
None
Related Features
L.Traffic.DL.SCH.Shared.T Multi-mode: MRFD-090202 GSM and LTE FDD

B GSM: None Dynamic Spectrum
Sharing(LTE FDD)
UMTS: None
LTE: None

1.21.18 Number of Bits of TBs Failed to be Transmitted During

Initial Transmission on the Downlink SCH in the Shared
Spectrum
Counters

CH.Shared.Err of TBs failed to BTS3900 LTE
TB.Ibler.bits be transmitted
during initial
transmission on
the downlink
SCH in the
shared spectrum
Description
The counter measures the number of bits of TBs failed to be transmitted during initial
transmission on the downlink SCH in the shared spectrum when GL dynamic spectrum
sharing is enabled.
Measurement Points
When GL dynamic spectrum sharing is enabled, the
L.Traffic.DL.SCH.Shared.ErrTB.Ibler.bits counter is incremented by the number of bits of the
TB each time the eNodeB receives NACK for a TB initially transmitted on the downlink SCH
in the shared spectrum.
Formula
None
Unit
bit

Related Features
L.Traffic.DL.SCH.Shared.E Multi-mode: MRFD-090202 GSM and LTE FDD

rrTB.Ibler.bits GSM: None Dynamic Spectrum
Sharing(LTE FDD)
UMTS: None
LTE: None
1.21.19 Number of TBs Failed to be Transmitted During Initial

Transmission on the Downlink SCH in the Shared Spectrum
Counters

CH.Shared.Err failed to be BTS3900 LTE
TB.Ibler transmitted
during initial
transmission on
the downlink
SCH in the
shared spectrum
Description
The counter measures the number of TBs failed to be transmitted during initial transmission
on the downlink SCH in the shared spectrum when GL dynamic spectrum sharing is enabled.
Measurement Points
When GL dynamic spectrum sharing is enabled, the L.Traffic.DL.SCH.Shared.ErrTB.Ibler is
incremented by 1 each time the eNodeB receives NACK for a TB initially transmitted on the
downlink SCH in the shared spectrum.
Formula
None
Unit
None

Related Features
L.Traffic.DL.SCH.Shared.E Multi-mode: MRFD-090202 GSM and LTE FDD

rrTB.Ibler GSM: None Dynamic Spectrum
Sharing(LTE FDD)
UMTS: None
LTE: None
1.21.20 Duration of Downlink Scheduling in the Shared Spectrum

Counters

L.Shared downlink BTS3900 LTE
scheduling in
the shared
spectrum
Description
The counter measures the duration of downlink scheduling in the shared spectrum in an LTE
cell when GL dynamic spectrum sharing is enabled.
Measurement Points
The eNodeB checks whether scheduling is performed in the shared spectrum each
millisecond. The L.Thrp.Time.DL.Shared counter is incremented by 1 each time the eNodeB
performs scheduling in the shared spectrum within a millisecond in a cell.
Formula
None
Unit
ms

Related Features
L.Thrp.Time.DL.Shared Multi-mode: MRFD-090202 GSM and LTE FDD

Sharing(LTE FDD)
UMTS: None
LTE: None
1.21.21 Duration of Downlink Scheduling in the Dedicated

Spectrum
Counters

L.Dedicated downlink BTS3900 LTE
scheduling in
the dedicated
spectrum
Description
The counter measures the duration of downlink scheduling in the dedicated spectrum in an
LTE cell when GL dynamic spectrum sharing is enabled.
Measurement Points
The eNodeB checks whether scheduling is performed in the dedicated spectrum each
millisecond. The L.Thrp.Time.DL.Dedicated counter is incremented by 1 each time the
eNodeB performs scheduling in the dedicated spectrum within a millisecond in a cell. This
counter is counted regardless of whether GL dynamic spectrum sharing is enabled. 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
L.Thrp.Time.DL.Dedicated Multi-mode: MRFD-090202 GSM and LTE FDD

Sharing(LTE FDD)
UMTS: None
LTE: None
1.21.22 Average Number of Used Downlink PRBs in the Shared

Spectrum
Counters

.Shared.DL.Use number of used BTS3900 LTE
d.Avg downlink PRBs
in the shared
spectrum
Description
The counter measures the average number of used PRBs on the PDSCH in the shared
spectrum when GL dynamic spectrum sharing is enabled.
Measurement Points
After GL dynamic spectrum sharing is enabled, the number of used downlink PRBs in the
shared spectrum GL dynamic spectrum sharing enabled 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.ChMeas.PRB.Shared.DL.Used.Avg counter.
Formula
None
Unit
None

Related Features
L.ChMeas.PRB.Shared.DL. Multi-mode: MRFD-090202 GSM and LTE FDD

Used.Avg GSM: None Dynamic Spectrum
Sharing(LTE FDD)
UMTS: None
LTE: None
1.21.23 Number of Times of Downlink Scheduling in the Shared

Spectrum
Counters
1526729875 L.Traffic.Sched Number of BTS3900, L

ule.Shared.Avg times of BTS3900 LTE
downlink
scheduling in
the shared
spectrum
Description
The counter measures the number of times of downlink scheduling in the shared spectrum.
Measurement Points
The number of UEs scheduled in the shared spectrum is sampled. At the end of a
measurement period, the sampling result is used as the value of the
L.Traffic.schedule.Shared.Avg counter.
Formula
None
Unit
None

Related Features
L.Traffic.Schedule.Shared.A Multi-mode: MRFD-090202 GSM and LTE FDD

vg GSM: None Dynamic Spectrum
Sharing(LTE FDD)
UMTS: None
LTE: None
1.21.24 Number of Times of Downlink Scheduling in the

Dedicated Spectrum
Counters
1526729876 L.Traffic.Sched Number of BTS3900, L

ule.Dedicated.A times of BTS3900 LTE
vg downlink
scheduling in
the dedicated
spectrum
Description
The counter measures the number of times of downlink scheduling in the dedicated spectrum.
Measurement Points
The number of UEs scheduled in the dedicated spectrum is sampled. At the end of a
measurement period, the sampling result is used as the value of the
L.Traffic.schedule.Shared.Avg counter. This counter is counted regardless of whether GL
dynamic spectrum sharing is enabled.
Formula
None
Unit
None

Related Features
L.Traffic.Schedule.Dedicate Multi-mode: MRFD-090202 GSM and LTE FDD

d.Avg GSM: None Dynamic Spectrum
Sharing(LTE FDD)
UMTS: None
LTE: None
1.21.25 Distribution of Packet Transmission Intervals for UEs in a

Cell
Counters
1526730124 L.Traffic.PktInt Number of BTS3900, L

erval.Num.Inde times the packet BTS3900 LTE
x0 transmission
interval for a
UE in a cell
ranges within
index 0

x1 transmission
interval for a
UE in a cell
ranges within
index 1

x2 transmission
interval for a
UE in a cell
ranges within
index 2

x3 transmission
interval for a
UE in a cell
ranges within
index 3



x4 transmission
interval for a
UE in a cell
ranges within
index 4

x5 transmission
interval for a
UE in a cell
ranges within
index 5

x6 transmission
interval for a
UE in a cell
ranges within
index 6

x7 transmission
interval for a
UE in a cell
ranges within
index 7

x8 transmission
interval for a
UE in a cell
ranges within
index 8
Description
The counters measure the number of times the packet transmission interval for a UE ranges in
different indexes. Interval indexes (0 to 8) are defined as follows:
Index 0: [5s, 10s)
Index1: [10s, 20s)
Index 2: [20s, 30s)

Index 3: [30s, 40s)

Index 4: [40s, 50s)
Index 5: [50s, 60s)
Index 6: [60s, 20s)
Index 7: [120s, 200s)
Index 8: [200s, +)
Measurement Points
The eNodeB determines whether a UE in a cell transmits service packet in a cell (without
discriminating between the uplink and downlink) per second. If a UE transmits service packet,
the packet transmission interval is measured. If the interval falls in a specific range, the
corresponding counter is incremented by 1, accordingly.
Formula
None
Unit
None
Related Features
L.Traffic.PktInterval.Num.I Multi-mode: None

ndex0 GSM: None
UMTS: None
Dynamic DRX

ndex1 GSM: None
UMTS: None
Dynamic DRX


ndex2 GSM: None
UMTS: None
Dynamic DRX

ndex3 GSM: None
UMTS: None
Dynamic DRX

ndex4 GSM: None
UMTS: None
Dynamic DRX

ndex5 GSM: None
UMTS: None
Dynamic DRX

ndex6 GSM: None
UMTS: None
Dynamic DRX


ndex7 GSM: None
UMTS: None
Dynamic DRX

ndex8 GSM: None
UMTS: None
Dynamic DRX
1.21.26 Number of Error TBs After the Maximum Number of

Retransmissions Is Reached for UEs with Poor Channel Quality
Counters

CH.PoorChann uplink error BTS3900 LTE
elQuality.ErrTB TBs after the
.Rbler maximum
number of
retransmissions
is reached for
UEs with poor
channel quality

CH.PoorChann downlink error BTS3900 LTE
elQuality.ErrTB TBs after the
.Rbler maximum
number of
retransmissions
is reached for
UEs with poor
channel quality

Description
The counters measure the number of uplink error TBs and the number of downlink error TBs
after the maximum number of retransmissions is reached for UEs with poor channel quality.
Measurement Points
If the eNodeB determines that the channel quality of a UE is poor, the corresponding counter
is incremented by 1 each time the eNodeB receives an uplink error TB or a downlink error TB
indicator from the UE after the maximum number of retransmissions is reached.
Formula
None
Unit
None
Related Features
None
1.21.27 Number Of TBs Initially Transmitted for UEs with Poor

Channel Quality
Counters

CH.PoorChann initially BTS3900 LTE
elQuality.TB transmitted on
the uplink SCH
for UEs with
poor channel
quality

CH.PoorChann initially BTS3900 LTE
elQuality.TB transmitted on
the downlink
SCH for UEs
with poor
channel quality
Description
The counters measure the number of TBs initially transmitted on the uplink SCH and the
number of TBs initially transmitted on the downlink SCH for UEs with poor channel quality.

Measurement Points
If the eNodeB determines that the channel quality of a UE is poor, the corresponding counter
is incremented by 1 each time the eNodeB receives an initial TB from the UE on the uplink
SCH or initially sends a TB to the UE on the downlink SCH.
Formula
None
Unit
None
Related Features
None
1.21.28 Number of Times that UEs are Scheduled in a Cell in the

Uplink or Downlink
Counters
1526730872 L.Traffic.Sch.U Number of BTS3900, L

L.Num times that UEs BTS3900 LTE
are scheduled in
a cell in the
uplink
1526730873 L.Traffic.Sch.D Number of BTS3900, L

L.Num times that UEs BTS3900 LTE
are scheduled in
a cell in the
downlink
Description
The counters measure the number of times that UEs are scheduled in a cell in the uplink or
downlink.
Measurement Points
The number of TTIs in which there are UEs being scheduled on the PUSCH or PDSCH is
accumulated. The number of TTIs in which only common signaling messages are scheduled
in the downlink is not counted.
For LTE TDD, if the downlink user signaling messages or downlink data is transmitted in the
downlink pilot timeslot (DwPTS) of a special subframe, the L.Traffic.Sch.DL.Num counter is
incremented.

Formula
None
Unit
None
Related Features
L.Traffic.Sch.UL.Num Multi-mode: None

GSM: None
UMTS: None
L.Traffic.Sch.DL.Num Multi-mode: None

GSM: None
UMTS: None
1.21.29 Number of Handover Command TBs Initially Transmitted

on the Downlink SCH
Counters

CH.HOCmd.T handover BTS3900 LTE
B command TBs
initially
transmitted on
the downlink
SCH



CH.RRCRel.Er failed to be BTS3900 LTE
rTB.Ibler transmitted for
RRC CONN
REL messages
during initial
transmission on
the downlink
SCH
Description
The counter measures the number of TBs for handover command that are initially transmitted
over the downlink SCH.
Measurement Points
The corresponding counter is incremented by 1 each time the eNodeB initially transmits a TB
for handover command over the downlink SCH.
Formula
None
Unit
None
Related Features
L.Traffic.DL.SCH.HOCmd. Multi-mode: None

TB GSM: None
UMTS: None
Transport Channel
Management

L.Traffic.DL.SCH.RRCRel. Multi-mode: None

ErrTB.Ibler GSM: None
UMTS: None
Transport Channel
Management
1.21.30 Number of Downlink Error TBs for Handover Commands

After Initial Transmission
Counters

CH.HOCmd.Er downlink error BTS3900 LTE
rTB.Ibler TBs for
handover
commands after
initial
transmission

CH.RRCRel.Er failed to be BTS3900 LTE
rTB.Rbler transmitted for
RRC CONN
REL messages
after the
maximum
number of
retransmissions
is reached on
the downlink
SCH
Description
The counter measures the number of downlink error TBs for handover command after initial
transmissions.
Measurement Points
The corresponding counter is incremented by 1 each time the eNodeB receives a downlink
error TB indicator for handover command after initial transmission.

Formula
None
Unit
None
Related Features

ErrTB.Ibler GSM: None
UMTS: None
Transport Channel
Management

ErrTB.Rbler GSM: None
UMTS: None
Transport Channel
Management

1.21.31 Number of Downlink Error TBs for Handover Commands

After the Maximum Number of Retransmissions is Reached
Counters

CH.HOCmd.Er downlink error BTS3900 LTE
rTB.Rbler TBs for
handover
commands after
the maximum
number of
retransmissions
is reached

CH.RRCRel.T initially BTS3900 LTE
B transmitted for
RRC CONN
REL messages
on the downlink
SCH
Description
The counter measures number of downlink error TBs for handover command after the
maximum number of retransmissions is reached.
Measurement Points
The corresponding counter is incremented by 1 each time the eNodeB receives a downlink
error TB indicator for handover command after the maximum number of retransmissions is
reached.
Formula
None
Unit
None

Related Features

ErrTB.Rbler GSM: None
UMTS: None
Transport Channel
Management

TB GSM: None
UMTS: None
Transport Channel
Management
1.21.32 Number of Voice Service TBs Initially Transmitted on the

Uplink SCH
Counters

CH.QPSK.TB. QCI-1 Service BTS3900 LTE
QCI.1 TBs initially
transmitted on
the uplink SCH
in QPSK
modulation
mode

CH. QCI-1 Service BTS3900 LTE
16QAM.TB.QC TBs initially
I.1 transmitted on
the uplink SCH
in 16QAM
modulation
mode



I.1 transmitted on
the uplink SCH
in 64QAM
modulation
mode
Description
The eNodeB determines the MCS index for initial transmission based on the uplink channel
quality of a UE. Each MCS index maps to a modulation scheme (QPSK, 16QAM, or
64QAM). The counters measure the number of QCI-1 voice service TBs initially transmitted
on the uplink SCH with different modulation schemes.
Measurement Points
The corresponding counter is incremented by 1 based on the modulation scheme each time the
eNodeB receives a TB initially transmitted on the uplink SCH and determines that the TB
includes voice services with QCI 1.
An eNodeB can determine whether a TB includes voice services with QCI 1 only after the
uplink data is resolved correctly. If HARQ retransmissions fail, the eNodeB cannot determine
whether a TB includes voice services. In this case, the corresponding TBs are not counted as
the TBs occupied by the uplink SCH for transmitting services with QCI 1. Therefore, the
measurement results of the counters deviate from the actual value.
Formula
None
Unit
None

Related Features

B.QCI.1 GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

16QAM.TB.QCI.1 GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None
Management
UL 64QAM

1.21.33 Number of Voice Service TBs Retransmitted on the

Uplink SCH
Counters

Retrans.QCI.1 TBs
retransmitted on
the uplink SCH
in QPSK
modulation
mode

16QAM.TB.Ret TBs
rans.QCI.1 retransmitted on
the uplink SCH
in 16QAM
modulation
mode

64QAM.TB.Ret TBs
the uplink SCH
in
64QAMmodula
tion mode
Description
on the uplink SCH with different modulation schemes.
Measurement Points
When an eNodeB receives a TB on the uplink SCH, the eNodeB determines the number of
times (n) that the TB is retransmitted based on the number of NACK messages. If the eNodeB
determines that the TB includes voice services with QCI 1, the corresponding counter is
incremented by n based on the modulation scheme.

measurement result deviates from the actual value.
Formula
None
Unit
None
Related Features

B.Retrans.QCI.1 GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

16QAM.TB.Retrans.QCI.1 GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM


UMTS: None
Management
UL 64QAM
1.21.34 Number of Voice Service TBs with Initial Transmission

Failures on the Uplink SCH
Counters

CH.QPSK.ErrT QCI-1 Service BTS3900 LTE
B.Ibler.QCI.1 TBs with initial
transmission
failures on the
uplink SCH in
QPSK
modulation
mode

16QAM.ErrTB. TBs with initial
Ibler.QCI.1 transmission
failures on the
uplink SCH in
16QAM
modulation
mode



failures on the
uplink SCH in
64QAM
modulation
mode
Description
64QAM). The counters measure the number of QCI-1 voice service TBs with initial
transmission failures on the uplink SCH with different modulation schemes.
Measurement Points
When an eNodeB receives a TB on the uplink SCH, the eNodeB determines whether the TB
is retransmitted based on the HARQ message. If the eNodeB determines that the TB includes
voice services with QCI 1, the corresponding counter is incremented by 1 based on the
modulation scheme.
measurement result deviates from the actual value.
Formula
None
Unit
None

Related Features

rTB.Ibler.QCI.1 GSM: None
UMTS: None
Transport Channel
Management

16QAM.ErrTB.Ibler.QCI.1 GSM: None
UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management
1.21.35 Number of Voice Service TBs Initially Transmitted on the

Downlink SCH
Counters

QCI.1 TBs initially
transmitted on
the downlink
SCH in QPSK
modulation
mode



I.1 transmitted on
the downlink
SCH in
16QAM
modulation
mode

I.1 transmitted on
the downlink
SCH in
64QAM
modulation
mode
Description
The eNodeB determines the MCS index for initial transmission based on the downlink
channel quality of a UE. Each MCS index maps to a modulation scheme (QPSK, 16QAM, or
on the downlink SCH with different modulation schemes.
Measurement Points
The corresponding counter is incremented by 1 based on the modulation scheme each time a
TB is initially transmitted on the downlink SCH and the eNodeB determines that the TB
includes voice services with QCI 1.
Formula
None
Unit
None

Related Features

B.QCI.1 GSM: None
UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management
1.21.36 Number of Voice Service TBs Retransmitted on the

Downlink SCH
Counters

Retrans.QCI.1 TBs
retransmitted on
the downlink
SCH in QPSK
modulation
mode



16QAM.TB.Ret TBs
the downlink
SCH in
16QAM
modulation
mode

64QAM.TB.Ret TBs
the downlink
SCH in
64QAM
modulation
mode
Description
The eNodeB determines the MCS index for retransmission based on the downlink channel
64QAM). The counters measure the number of QCI-1 voice service TBs retransmitted on the
downlink SCH with different modulation schemes.
Measurement Points
The corresponding counter is incremented by 1 based on the modulation scheme each time a
TB is retransmitted on the downlink SCH and the eNodeB determines that the TB includes
voice services with QCI 1.
Formula
None
Unit
None

Related Features

B.Retrans.QCI.1 GSM: None
UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management
1.21.37 Number of Voice Service TBs with Initial Transmission

Failures on the Downlink SCH
Counters

CH.QPSK.ErrT QCI-1 Service BTS3900 LTE
B.Ibler.QCI.1 TBs with initial
transmission
failures on the
downlink SCH
in QPSK
modulation
mode



failures on the
downlink SCH
in 16QAM
modulation
mode

failures on the
downlink SCH
in 64QAM
modulation
mode
Description
64QAM). The counters measure the number of QCI-1 voice service TBs with initial
transmission failures on the downlink SCH with different modulation schemes.
Measurement Points
The corresponding counter is incremented by 1 based on the modulation scheme each time an
eNodeB receives a TB failed to be initially transmitted on the downlink SCH and determines
that the TB includes voice services with QCI 1.
Formula
None
Unit
None

Related Features

rTB.Ibler.QCI.1 GSM: None
UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management
1.21.38 Number of Service Data TBs Initially Transmitted on the

Downlink SCH
Counters

CH.QPSK.DRB service data BTS3900 LTE
.TB TBs initially
transmitted on
the downlink
SCH in QPSK
modulation
mode



CH. service data BTS3900 LTE
16QAM.DRB.T TBs initially
B transmitted on
the downlink
SCH in
16QAM
modulation
mode

64QAM.DRB.T TBs initially
B transmitted on
the downlink
SCH in
64QAM
modulation
mode
Description
64QAM). The counters measure the number of service data TBs initially transmitted on the
downlink SCH in QPSK, 16QAM, or 64QAM modulation mode in a cell.
Measurement Points
eNodeB initially transmits a service data TB on the downlink SCH.
Formula
None
Unit
None

Related Features
L.Traffic.DL.SCH.QPSK.D Multi-mode: None

RB.TB GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

16QAM.DRB.TB GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

64QAM.DRB.TB GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

1.21.39 Number of Service Data TBs Retransmitted on the

Downlink SCH
Counters

CH.QPSK.DRB service data BTS3900 LTE
.TB.Retrans TBs
retransmitted on
the downlink
SCH in QPSK
modulation
mode

16QAM.DRB.T TBs
B.Retrans retransmitted on
the downlink
SCH in
16QAM
modulation
mode

64QAM.DRB.T TBs
B.Retrans retransmitted on
the downlink
SCH in
64QAM
modulation
mode
Description
The eNodeB determines the MCS index for retransmission based on the downlink channel
64QAM). The counters measure the number of service data TBs retransmitted on the
downlink SCH in QPSK, 16QAM, or 64QAM modulation mode in a cell.
Measurement Points
eNodeB retransmits a service data TB on the downlink SCH.

Formula
None
Unit
None
Related Features

RB.TB.Retrans GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

16QAM.DRB.TB.Retrans GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM


64QAM.DRB.TB.Retrans GSM: None
UMTS: None
DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM
1.21.40 Number of Downlink Error Service Data TBs After Initial

Transmission
Counters

CH.QPSK.DRB downlink error BTS3900 LTE
.ErrTB.Ibler service data
TBs after initial
transmission in
QPSK
modulation
mode

16QAM.DRB.E service data
rrTB.Ibler TBs after initial
transmission in
16QAM
modulation
mode



rrTB.Ibler TBs after initial
transmission in
64QAM
modulation
mode
Description
The counters measure the number of downlink error service data TBs after initial transmission
in QPSK, 16QAM, or 64QAM modulation mode.
Measurement Points
eNodeB receives a downlink error service data TB indicator after initial transmission.
Formula
None
Unit
None
Related Features

RB.ErrTB.Ibler GSM: None
UMTS: None
Transport Channel
Management


16QAM.DRB.ErrTB.Ibler GSM: None
UMTS: None
Transport Channel
Management

64QAM.DRB.ErrTB.Ibler GSM: None
UMTS: None
Transport Channel
Management
1.21.41 Number of Downlink Error Service Data TBs After the

Maximum Number of Retransmissions Is Reached
Counters

CH.QPSK.DRB downlink error BTS3900 LTE
.ErrTB.Rbler service data
TBs after the
maximum
number of
retransmissions
in QPSK
modulation
mode is reached

rrTB.Rbler TBs after the
maximum
number of
retransmissions
in 16QAM
modulation
mode is reached



rrTB.Rbler TBs after the
maximum
number of
retransmissions
in 64QAM
modulation
mode is reached
Description
The counters measure the number of downlink error service data TBs after the maximum
number of retransmissions in QPSK, 16QAM, or 64QAM modulation mode is reached.
Measurement Points
eNodeB receives a downlink error service data TB indicator after the maximum number of
retransmissions is reached.
Formula
None
Unit
None
Related Features

RB.ErrTB.Rbler GSM: None
UMTS: None
Transport Channel
Management


16QAM.DRB.ErrTB.Rbler GSM: None
UMTS: None
Transport Channel
Management

64QAM.DRB.ErrTB.Rbler GSM: None
UMTS: None
Transport Channel
Management
1.22 Cell User Quantity Measurement (Traffic.User.Cell)

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.UL.Avg, L.Traffic.User.SCell.UL.Max,
L.Traffic.User.SCell.Active.UL.Avg, L.Traffic.User.SCell.Active.UL.Max,
L.Traffic.User.SCell.DL.Avg, L.Traffic.User.SCell.DL.Max,
L.Traffic.User.SCell.Active.DL.Avg and L.Traffic.User.SCell.Active.DL.Max counters are
used, but other counters related to the number of users are not used.
Counters
Description
1526727378 L.Traffic.User.Avg Average number of BTS3900:

users in a cell V100R008C00
BTS3900 LTE:
V100R003C00


Description
1526727379 L.Traffic.User.Max Maximum number BTS3900:

of users in a cell V100R008C00
BTS3900 LTE:
V100R003C00
1526727380 L.Traffic.CEU.Avg Average number of BTS3900:

downlink cell edge V100R008C00
users (CEUs) in a BTS3900 LTE:
cell version earlier than
V100R003C00
1526727381 L.Traffic.CEU.Max Maximum number BTS3900:

of downlink cell V100R008C00
edge users (CEUs) BTS3900 LTE:
in a cell version earlier than
V100R003C00
1526727382 L.Traffic.User.ULD Average number of BTS3900:

ata.Avg UEs with data in the V100R008C00
uplink buffer BTS3900 LTE:
V100R003C00
1526727383 L.Traffic.User.ULD Maximum number BTS3900:

ata.Max of UEs with data in V100R008C00
the uplink buffer BTS3900 LTE:
V100R003C00
1526727384 L.Traffic.User.DLD Average number of BTS3900:

ata.Avg UEs with data in the V100R008C00
downlink buffer BTS3900 LTE:
V100R003C00
1526727385 L.Traffic.User.DLD Maximum number BTS3900:

ata.Max of UEs with data in V100R008C00
the downlink buffer BTS3900 LTE:
V100R003C00
1526728333 L.Traffic.User.Ulsy Average number of BTS3900:

nc.Avg UL synchronized V100R008C00
users in a cell BTS3900 LTE:
V100R005C00
1526728335 L.Traffic.User.Data Maximum number BTS3900:

.Max of users with data in V100R008C00
the buffer BTS3900 LTE:
V100R005C00


Description
1526728336 L.Traffic.User.Data Average number of BTS3900:

.Avg users with data in V100R008C00
the buffer BTS3900 LTE:
V100R005C00
1526728338 L.ULCoMP.User.A Average number of BTS3900:

vg UL CoMP UEs in a V100R008C00
cell BTS3900 LTE:
V100R005C00
1526728339 L.ULCoMP.User.M Maximum number BTS3900:

ax of UL CoMP UEs in V100R008C00
a cell BTS3900 LTE:
V100R005C00
1526728426 L.Traffic.User.PCel Average number of BTS3900:

l.DL.Avg downlink CA UEs V100R008C00
that use the local BTS3900 LTE:
cell as their primary V100R008C00
serving cells
1526728427 L.Traffic.User.SCel Average number of BTS3900:

l.DL.Avg downlink CA UEs V100R008C00
cell as their V100R008C00
secondary serving
cells
1526728445 L.Traffic.ActiveUse Total number of BTS3900:

r.UL.QCI.Total activated UEs with a V100R008C00
QCI (or an extended BTS3900 LTE:
QCI) in the uplink V100R008C00
buffer
1526728446 L.Traffic.ActiveUse Number of activated BTS3900:

r.UL.QCI.1 UEs with the QCI of V100R008C00
1 in the uplink BTS3900 LTE:
buffer V100R008C00

buffer V100R008C00

buffer V100R008C00


Description

buffer V100R008C00

buffer V100R008C00

buffer V100R008C00

buffer V100R008C00

buffer V100R008C00

buffer V100R008C00
1526728455 L.Traffic.ActiveUse Total number of BTS3900:

r.DL.QCI.Total activated UEs with a V100R008C00
QCI (or an extended BTS3900 LTE:
QCI) in the V100R008C00
downlink buffer

r.DL.QCI.1 UEs with the QCI of V100R008C00
1 in the downlink BTS3900 LTE:
buffer V100R008C00

buffer V100R008C00

buffer V100R008C00


Description

buffer V100R008C00

buffer V100R008C00

buffer V100R008C00

buffer V100R008C00

buffer V100R008C00

buffer V100R008C00
1526728473 L.Traffic.ULCEU. Average number of BTS3900:

Avg uplink cell edge V100R008C00
cell V100R008C00
1526728474 L.Traffic.ULCEU. Maximum number BTS3900:

Max of uplink cell edge V100R008C00
cell V100R008C00
1526728481 L.Traffic.User.SRS. Average number of BTS3900:

Avg UEs configured with V100R008C00
sounding reference BTS3900 LTE:
signal (SRS) V100R008C00
resources in a cell
1526728482 L.Traffic.User.SRS. Maximum number BTS3900:

Max of UEs configured V100R008C00
with sounding BTS3900 LTE:
reference signal V100R008C00
(SRS) resources in a
cell


Description
1526728496 L.Traffic.User.TtiB Average number of BTS3900:

undling.Avg UEs on which TTI V100R008C00
bundling takes effect BTS3900 LTE:
1526728516 L.Traffic.User.PCel Maximum number BTS3900:

l.DL.Max of downlink CA V100R008C00
UEs that use the BTS3900 LTE:
local cell as their V100R008C00
primary serving
cells
1526728517 L.Traffic.User.SCel Maximum number BTS3900:

l.DL.Max of downlink CA V100R008C00
UEs that use the BTS3900 LTE:
secondary serving
cells
1526728524 L.Traffic.User.RoH Maximum number BTS3900:

C.Max of UEs on which V100R008C00
ROHC takes effect BTS3900 LTE:
1526728525 L.Traffic.User.RoH Average number of BTS3900:

C.Avg UEs on which V100R008C00
ROHC takes effect BTS3900 LTE:
1526728546 L.Traffic.User.Cdr Average number of BTS3900:

x.Avg UEs on which DRX V100R008C00
takes effect in a cell BTS3900 LTE:
V100R008C00
1526728942 L.Traffic.IICS.UL. Average number of BTS3900:

StrongIntfUser.Avg uplink strong V100R008C01
interference UE in a BTS3900 LTE:
cell V100R008C01
1526728943 L.Traffic.IICS.UL. Max number of BTS3900:

StrongIntfUser.Ma uplink strong V100R008C01
x interference UE in a BTS3900 LTE:
cell V100R008C01
1526728944 L.Traffic.IICS.UL. Average number of BTS3900:

WeakIntfUsewr.Av uplink weak V100R008C01
g interference UE in a BTS3900 LTE:
cell V100R008C01


Description
1526728945 L.Traffic.IICS.UL. Max number umber BTS3900:

WeakIntfUsewr.Ma of uplink weak V100R008C01
x interference UE in a BTS3900 LTE:
cell V100R008C01
1526728969 L.Traffic.ActiveUse Average number of BTS3900:

r.DL.Avg activated UEs in V100R008C00
downlink BTS3900 LTE:
V100R008C00
1526728970 L.Traffic.ActiveUse Maximum number BTS3900:

r.DL.Max of activated UEs in V100R008C00
downlink BTS3900 LTE:
V100R008C00

r.UL.Avg activated UEs in V100R008C00
uplink BTS3900 LTE:
V100R008C00

r.UL.Max of activated UEs in V100R008C00
uplink BTS3900 LTE:
V100R008C00

r.Avg activated UEs V100R008C00
BTS3900 LTE:
V100R008C00

r.Max of activated UEs V100R008C00
BTS3900 LTE:
V100R008C00
1526729297 L.Traffic.User.eICI Average number of BTS3900:

C.Avg UEs enabled with V100R008C01
the eICIC function BTS3900 LTE:
1526729298 L.Traffic.User.eICI Maximum number BTS3900:

C.Max of UEs enabled with V100R008C01
the eICIC function BTS3900 LTE:
1526729464 L.Traffic.User.DLC Average number of BTS3900:

omp.Avg downlink CoMP V100R008C01
UEs in a cell BTS3900 LTE:
V100R008C01


Description
1526729465 L.Traffic.User.DLC Maximum number BTS3900:

omp.Max of downlink CoMP V100R008C01
UEs in a cell BTS3900 LTE:
V100R008C01
1526729557 L.Traffic.HetnetCE Average number of BTS3900:

U.Avg UEs in a cell that are V100R009C00
close to the border BTS3900 LTE:
with the other type V100R009C00
of cells in a
heterogeneous
network

U.eICIC.Avg UEs in a cell that are V100R009C00
close to the border BTS3900 LTE:
with the other type V100R009C00
of cells and support
TDM eICIC in a
heterogeneous
network
1526730100 L.Traffic.Privilege. Average number of BTS3900:

User.avg privileged UEs in a V100R009C00
cell BTS3900 LTE:
V100R009C00
1526730101 L.Traffic.Privilege. Maximum number BTS3900:

User.max of privileged UEs in V100R009C00
a cell BTS3900 LTE:
V100R009C00
1526730143 L.Traffic.User.TA Average number of BTS3900:

Meas.PUCCH.Avg UEs whose uplink V100R009C00
timing offsets are BTS3900 LTE:
measured based on V100R009C00
the PUCCH
1526730144 L.Traffic.User.TA Maximum number BTS3900:

Meas.PUCCH.Max of UEs whose uplink V100R009C00
timing offsets are BTS3900 LTE:
measured based on V100R009C00
the PUCCH

r.DL.QCI.Total.Ma of activated UEs V100R009C00
x with a QCI (or an BTS3900 LTE:
extended QCI) in the V100R009C00
downlink buffer


Description

r.DL.QCI.1.Max of activated UEs V100R009C00
the downlink buffer V100R009C00









r.UL.QCI.Total.Ma of activated UEs V100R009C00
x with a QCI (or an BTS3900 LTE:
extended QCI) in the V100R009C00
uplink buffer


Description

r.UL.QCI.1.Max of activated UEs V100R009C00
the uplink buffer V100R009C00








1526730832 L.Traffic.SUNPT.D Average number of BTS3900:

L.Avg scheduled UEs per V100R009C00
TTI in the downlink BTS3900 LTE:


Description
1526730833 L.Traffic.SUNPT.D Maximum number BTS3900:

L.Max of scheduled UEs V100R009C00
per TTI in the BTS3900 LTE:
downlink in a cell V100R009C00
1526730838 L.Traffic.SUNPT.U Average number of BTS3900:

L.Avg scheduled UEs per V100R009C00
TTI in the uplink in BTS3900 LTE:
a cell V100R009C00
1526730839 L.Traffic.SUNPT.U Maximum number BTS3900:

L.Max of scheduled UEs V100R009C00
per TTI in the uplink BTS3900 LTE:
1526730840 L.Traffic.SUNPT.U Maximum total BTS3900:

LDL.Max number of scheduled V100R009C00
UEs per TTI in the BTS3900 LTE:
uplink and downlink V100R009C00
in a cell
1526730878 L.Traffic.User.Lice Average licensed BTS3900:

nse.Avg number of UEs in V100R009C00
RRC_CONNECTE BTS3900 LTE:
D mode V100R009C00
1526731537 L.Traffic.User.US. Average number of BTS3900:

Avg UEs running V100R010C00
unlimited services BTS3900 LTE:
V100R010C00
1526731538 L.Traffic.User.US. Maximum number BTS3900:

Max of UEs running V100R010C00
unlimited services BTS3900 LTE:
V100R010C00

l.Active.DL.Avg activated CA UEs V100R008C01
cell as their Scell V100R008C01

l.Active.DL.Max of activated CA UEs V100R008C01
1526732676 L.Traffic.User.Inde Number of times the BTS3900:

x0 UE quantity in a cell V100R010C00
falls within the BTS3900 LTE:
range indicated by V100R010C00
index 0


Description

index 1

index 2

index 3

index 4

index 5

index 6

index 7

index 8


Description

index 9

index 10
1526732721 L.Traffic.User.VoIP Average number of BTS3900:

.Avg VoIP UEs in a cell V100R010C00
BTS3900 LTE:
V100R010C00
1526732722 L.Traffic.User.VoIP Maximum number BTS3900:

.Max of VoIP UEs in a V100R010C00
cell BTS3900 LTE:
V100R010C00
1526732723 L.Traffic.User.TM9 Average number of BTS3900:

.Avg UEs that apply TM9 V100R010C00
V100R010C00

l.UL.Avg uplink CA UEs that V100R010C00
use the local cell as BTS3900 LTE:
their Scell V100R010C00

l.UL.Max of uplink CA UEs V100R010C00

l.UL.Avg CA UEs that use the V100R010C00
local cell as their BTS3900 LTE:
PCells in the uplink V100R010C00

l.UL.Max of CA UEs that use V100R010C00
the local cell as their BTS3900 LTE:
PCells in the uplink V100R010C00

l.DL.3CC.Avg 3CC CA UEs that V100R010C00
their PCells in the V100R010C00
downlink


Description

l.DL.3CC.Max of 3CC CA UEs that V100R010C00
their PCells in the V100R010C00
downlink

l.DL.RelaxedBackh downlink relaxed- V100R010C00
aulCA.Avg backhaul-based BTS3900 LTE:
inter-eNodeB CA V100R010C00
UEs that treat the
local cell as their
Pcell

l.DL.RelaxedBackh of downlink relaxed- V100R010C00
aulCA.Max backhaul-based BTS3900 LTE:
UEs that treat the
local cell as their
Pcell

l.DL. CA UEs with the V100R010C00
3CC.Active.Avg local cell as their BTS3900 LTE:
PCell and with all V100R010C00
configured two
SCCs activated

l.DL. of CA UEs with the V100R010C00
3CC.Active.Max local cell as PCell BTS3900 LTE:
and with all V100R010C00
configured two
SCCs activated

l.DL.RelaxedBackh of downlink relaxed- V100R010C00
aulCA.Max backhaul-based BTS3900 LTE:
UEs that treat the
local cell as their
SCell

l.DL.RelaxedBackh downlink relaxed- V100R010C00
aulCA.Avg backhaul-based BTS3900 LTE:
UEs that treat the
local cell as their
SCell


Description

l.Active.UL.Avg CA UEs that treat V100R010C00
SCell and have the V100R010C00
SCell activated in
the uplink

l.Active.UL.Max of CA UEs that treat V100R010C00
SCell and have the V100R010C00
SCell activated in
the uplink
1526733021 L.CA.UL.PCell.Act Duration of CA UEs BTS3900:

.Dur in the uplink CA V100R010C00
state that treat the BTS3900 LTE:
PCell and have the
SCell activated
1526733022 L.CA.UL.SCell.Act Duration of CA UEs BTS3900:

.Dur in the uplink CA V100R010C00
state that treat the BTS3900 LTE:
SCell and have the
SCell activated
1526733173 L.ULCoMP.Hetnet Average number of BTS3900:

CoMP.User.Avg UEs selected for V100R010C00
whom HetNet UL BTS3900 LTE:
CoMP is performed V100R010C00
in a cell
1526733174 L.ULCoMP.Hetnet Maximum number BTS3900:

CoMP.User.Max of UEs selected for V100R010C00
whom HetNet UL BTS3900 LTE:
CoMP is performed V100R010C00
in a cell
1526733198 L.Traffic.User.PCel Number of times BTS3900:

l.RelaxedBackhaul- inter-eNodeB CA V100R010C00
CA.OFF based on relaxed BTS3900 LTE:
backhaul stops V100R010C00
because the inter-
eNodeB
transmission delay
does not meet the
requirement


Description
1526735159 L.Traffic.User.Sma Average number of BTS3900:

rtdrx.Avg UEs on which Smart V100R009C00
DRX takes effect in BTS3900 LTE:
a cell V100R009C00
1526736781 L.Traffic.GBRUser. Number of UEs that BTS3900:

BitRate.Index0 are configured with V100R010C10
a GBR and whose BTS3900 LTE:
throughput falls V100R010C10
within range 0 in a
cell

within range 1 in a
cell

within range 2 in a
cell

within range 3 in a
cell

within range 4 in a
cell

within range 5 in a
cell


Description

within range 6 in a
cell
1526736790 L.Traffic.User.Ulsy Maximum number BTS3900:

nc.Max of UL-sync UEs in a V100R010C10
cell BTS3900 LTE:
V100R010C10
1526736871 L.Traffic.User.FeIC Average number of BTS3900:

IC.Avg FeICIC-capable UEs V100R010C10
V100R010C10

U.FeICIC.Avg FeICIC-capable UEs V100R010C10
in a cell that are BTS3900 LTE:
close to the border V100R010C10
with the other type
of cells in a HetNet
1526737747 L.Traffic.User.CEU Number of UEs BTS3900:

.DL.AICIC.Avg identified as CEUs V100R010C10
in downlink BTS3900 LTE:
adaptive ICIC V100R010C10
1526737749 L.ULCAMC.User. Average number of BTS3900:

Avg UEs for which V100R010C10
coordinated uplink BTS3900 LTE:
AMC is used in a V100R010C10
cell
1526737752 L.Traffic.User.Inter Average number of BTS3900:

EnbDLComp.Avg DL CoMP UEs in a V100R010C10
cell BTS3900 LTE:
V100R010C10
1526737760 L.Traffic.ULShare Average number of BTS3900:

d.USER.Avg UEs using the V100R010C10
UMTS and LTE BTS3900 LTE:
shared spectrum in a V100R010C10
cell
1526737763 L.ULCoMP.ULRel Average number of BTS3900:

axedBHCoMP.User UEs selected for V100R010C10
.Avg whom UL CoMP BTS3900 LTE:
based on relaxed V100R010C10
backhaul is
performed in a cell


Description
1526737776 L.Traffic.User.Fdd Average number of BTS3900:

TddCA. CA UEs that treat V100R010C10
3CC.PCell.DL.Avg the local cell as their BTS3900 LTE:
PCell in the V100R010C10
downlink FDD
+TDD 3CC CA state
1526737777 L.Traffic.User.Fdd Maximum number BTS3900:

TddCA. of CA UEs that treat V100R010C10
3CC.PCell.DL.Max the local cell as their BTS3900 LTE:
downlink FDD
+TDD 3CC CA state

4CC.PCell.DL.Avg the local cell as their BTS3900 LTE:
downlink FDD
+TDD 4CC CA state

4CC.PCell.DL.Max the local cell as their BTS3900 LTE:
downlink FDD
+TDD 4CC CA state

l.DL.4CC.Avg CA UEs that treat V100R010C10
downlink 4CC CA
state

l.DL.4CC.Max of CA UEs that treat V100R010C10
downlink 4CC CA
state

TddCA.PCell.DL.A CA UEs that treat V100R010C10
vg the local cell as their BTS3900 LTE:
downlink FDD
+TDD CA state


Description

TddCA.PCell.DL. of CA UEs that treat V100R010C10
Max the local cell as their BTS3900 LTE:
downlink FDD
+TDD CA state

l.DL.Active.Avg CA UEs that treat V100R010C10
PCell and have all V100R010C10
SCells activated

l.DL.Active.Max of CA UEs that treat V100R010C10
SCells activated
1526737793 L.Traffic.User.CA. Average number of BTS3900:

4CC.PCell.DL.Acti CA UEs that treat V100R010C10
ve.Avg the local cell as their BTS3900 LTE:
downlink 4CC CA
1526737794 L.Traffic.User.CA. Maximum number BTS3900:

4CC.PCell.DL.Acti of CA UEs that treat V100R010C10
ve.Max the local cell as their BTS3900 LTE:
downlink 4CC CA

TddCA.PCell.DL.A CA UEs that treat V100R010C10
ctive.Avg the local cell as their BTS3900 LTE:
downlink FDD
+TDD CA

TddCA.PCell.DL.A of CA UEs that treat V100R010C10
ctive.Max the local cell as their BTS3900 LTE:
downlink FDD
+TDD CA


Description

3CC.PCell.DL.Acti the local cell as their BTS3900 LTE:
ve.Avg PCell and have all V100R010C10
downlink FDD
+TDD 3CC CA

ve.Max PCell and have all V100R010C10
downlink FDD
+TDD 3CC CA

ve.Avg PCell and have all V100R010C10
downlink FDD
+TDD 4CC CA

ve.Max PCell and have all V100R010C10
downlink FDD
+TDD 4CC CA
1526737851 L.Traffic.User.InSe Average number of BTS3900:

ssion.Avg UEs with service V100R010C10
data to be BTS3900 LTE:
transmitted in a cell V100R010C10
1526737852 L.Traffic.User.InSe Maximum number BTS3900:

ssion.Max of UEs with service V100R010C10
data to be BTS3900 LTE:
transmitted in a cell V100R010C10
The Traffic.User.Cell function subset contains counters related to the number of UEs. Some of
these counters can be categorized in terms of the QCI. The following table shows the parent-
child relationship of the counters.

L.ULCoMP.User.Avg L.ULCoMP.HetnetCoMP.User.Avg
L.Traffic.ActiveUser.UL.QCI.Total L.Traffic.ActiveUser.UL.QCI.1
L.Traffic.ActiveUser.UL.QCI.2
L.Traffic.ActiveUser.DL.QCI.Total L.Traffic.ActiveUser.DL.QCI.1
L.Traffic.ActiveUser.DL.QCI.2
1.22.1 Number of Users in a Cell
Counters
1526727378 L.Traffic.User. Average BTS3900, L

Avg number of users BTS3900 LTE
in a cell
1526727379 L.Traffic.User. Maximum BTS3900, L

Max number of users BTS3900 LTE
in a cell

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 RRC_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
L.Traffic.User.Avg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.User.Max Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management

1.22.2 Number of ICIC Cell Edge Users in a Cell
Counters
1526727380 L.Traffic.CEU. Average BTS3900, L

Avg number of BTS3900 LTE
downlink cell
edge users
(CEUs) in a cell
1526727381 L.Traffic.CEU. Maximum BTS3900, L

Max number of BTS3900 LTE
downlink cell
edge users
(CEUs) in a cell
1526728473 L.Traffic.ULCE Average BTS3900, L

U.Avg number of BTS3900 LTE
uplink cell edge
users (CEUs) in
a cell
1526728474 L.Traffic.ULCE Maximum BTS3900, L

U.Max number of BTS3900 LTE
uplink cell edge
users (CEUs) in
a cell
Description
The counters measure the average and maximum number of uplink and downlink ICIC 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 ICIC 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
Formula
None
Unit
None

Related Features
L.Traffic.CEU.Avg Multi-mode: None

GSM: None
UMTS: None
LOFD-00101401 RRC Connection
Management
LBFD-00202201
TDLBFD-00202201 Cell Interference
LOFD-060201 Coordination
TDLOFD-060201 Downlink Static Inter-Cell
Downlink Static Inter-Cell
Adaptive Inter-Cell
Adaptive Inter-Cell
L.Traffic.CEU.Max Multi-mode: None

GSM: None
UMTS: None
Management
LBFD-00202201
TDLBFD-00202201 Cell Interference
LOFD-060201 Coordination
TDLOFD-060201 Downlink Static Inter-Cell
Downlink Static Inter-Cell
Adaptive Inter-Cell
Adaptive Inter-Cell

L.Traffic.ULCEU.Avg Multi-mode: None

GSM: None
UMTS: None
Management
LBFD-00202202
Uplink Static Inter-Cell
Adaptive Inter-Cell
Adaptive Inter-Cell
L.Traffic.ULCEU.Max Multi-mode: None

GSM: None
UMTS: None
Management
LBFD-00202202
Uplink Static Inter-Cell
Adaptive Inter-Cell
Adaptive Inter-Cell

1.22.3 Number of UEs with Data in the Uplink Buffer
Counters

ULData.Avg number of UEs BTS3900 LTE
with data in the
uplink buffer

ULData.Max number of UEs BTS3900 LTE
with data in the
uplink buffer
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
L.Traffic.User.ULData.Avg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management

L.Traffic.User.ULData.Max Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
1.22.4 Number of UEs with Data in the Downlink Buffer
Counters

DLData.Avg number of UEs BTS3900 LTE
with data in the
downlink buffer

DLData.Max number of UEs BTS3900 LTE
with data in the
downlink buffer
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
Formula
None
Unit
None

Related Features
L.Traffic.User.DLData.Avg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.User.DLData.Max Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
1.22.5 Number of UL Synchronized Users in a Cell
Counters

Ulsync.Avg number of UL BTS3900 LTE
synchronized
users in a cell

Ulsync.Max number of UL- BTS3900 LTE
sync UEs in a
cell
Description
The counter measures the 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
L.Traffic.User.Ulsync.Avg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.User.Ulsync.Max Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
1.22.6 Number of UEs Transmitting or Receiving Data in a Cell

Counters

Data.Max number of users BTS3900 LTE
with data in the
buffer

Data.Avg number of users BTS3900 LTE
with data in the
buffer

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
L.Traffic.User.Data.Max Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.User.Data.Avg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management

1.22.7 Number of UL CoMP UEs in a Cell
Counters
1526728338 L.ULCoMP.Use Average BTS3900, L

r.Avg number of UL BTS3900 LTE
CoMP UEs in a
cell
1526728339 L.ULCoMP.Use Maximum BTS3900, L

r.Max number of UL BTS3900 LTE
CoMP UEs in a
cell
1526733173 L.ULCoMP.Het Average BTS3900, L

netCoMP.User. number of UEs BTS3900 LTE
Avg selected for
whom HetNet
UL CoMP is
performed in a
cell
1526733174 L.ULCoMP.Het Maximum BTS3900, L

netCoMP.User. number of UEs BTS3900 LTE
Max selected for
whom HetNet
UL CoMP is
performed in a
cell
1526737763 L.ULCoMP.UL Average BTS3900, L

RelaxedBHCo number of UEs BTS3900 LTE
MP.User.Avg selected for
whom UL
CoMP based on
relaxed
backhaul is
performed in a
cell
Description
The counters measure the following numbers within a measurement period:
- Average number and maximum number of UEs selected for whom UL CoMP is performed
in a cell
- Average number and maximum number of UEs selected for whom HetNet UL CoMP is
performed in a cell (applicable only to LTE FDD)

- Average number of UEs selected for whom UL CoMP based on relaxed backhaul is
performed in a cell(applicable only to LTE FDD)
Measurement Points
The counters are measured based on the status of UEs in the sampling period. The number of
UEs selected for whom UL CoMP, HetNet UL CoMP, or relaxed-backhaul-based UL CoMP
is performed in a cell is sampled per second. At the end of a measurement period, the
maximum and average of these sampling results are used as the values of the corresponding
counters.
For UEs selected for whom HetNet UL CoMP is performed, the maximum number of these
UEs is included in both the L.ULCoMP.User.Max and L.ULCoMP.HetnetCoMP.User.Max
counters, and the average number of these UEs is included in both the L.ULCoMP.User.Avg
and L.ULCoMP.HetnetCoMP.User.Avg counters.
For UEs selected for whom UL CoMP based on relaxed backhaul is performed, the maximum
number of these UEs is included in the following counters: L.ULCoMP.User.Avg,
L.ULCoMP.User.Max, and L.ULCoMP.RelaxBHCoMP.User.Avg.
The counters L.ULCoMP.HetnetCoMP.User.Avg and L.ULCoMP.HetnetCoMP.User.Max
apply only to LTE FDD.
Formula
None
Unit
None
Related Features
L.ULCoMP.User.Avg Multi-mode: None

GSM: None
UMTS: None
Coordinated BBU

L.ULCoMP.User.Max Multi-mode: None

GSM: None
UMTS: None
Coordinated BBU
L.ULCoMP.HetnetCoMP.Us Multi-mode: None

er.Avg GSM: None
UMTS: None
UL CoMP based on
Coordinated BBU
L.ULCoMP.HetnetCoMP.Us Multi-mode: None

er.Max GSM: None
UMTS: None
UL CoMP based on
Coordinated BBU
L.ULCoMP.ULRelaxedBH Multi-mode: None

CoMP.User.Avg GSM: None
UMTS: None
LTE: LOFD-081219 UL CoMP Based on
Relaxed Backhaul

1.22.8 Number of CA UEs in a Cell
Counters
1526728426 L.Traffic.User.P Average BTS3900, L

Cell.DL.Avg number of BTS3900 LTE
downlink CA
UEs that use the
local cell as
their primary
serving cells
1526728427 L.Traffic.User.S Average BTS3900, L

Cell.DL.Avg number of BTS3900 LTE
downlink CA
UEs that use the
local cell as
their secondary
serving cells
1526728516 L.Traffic.User.P Maximum BTS3900, L

Cell.DL.Max number of BTS3900 LTE
downlink CA
UEs that use the
local cell as
their primary
serving cells
1526728517 L.Traffic.User.S Maximum BTS3900, L

Cell.DL.Max number of BTS3900 LTE
downlink CA
UEs that use the
local cell as
their secondary
serving cells

Cell.DL. number of 3CC BTS3900 LTE
3CC.Avg CA UEs that
use the local
cell as their
PCells in the
downlink

Cell.DL. number of 3CC BTS3900 LTE
3CC.Max CA UEs that
use the local
cell as their
PCells in the
downlink


1526737776 L.Traffic.User.F Average BTS3900, L

ddTddCA. number of CA BTS3900 LTE
3CC.PCell.DL. UEs that treat
Avg the local cell as
their PCell in
the downlink
FDD+TDD
3CC CA state
1526737777 L.Traffic.User.F Maximum BTS3900, L

Max the local cell as
their PCell in
the downlink
FDD+TDD
3CC CA state

Avg the local cell as
their PCell in
the downlink
FDD+TDD
4CC CA state

Max the local cell as
their PCell in
the downlink
FDD+TDD
4CC CA state

Cell.DL. number of CA BTS3900 LTE
4CC.Avg UEs that treat
the local cell as
their PCell in
the downlink
4CC CA state

4CC.Max UEs that treat
the local cell as
their PCell in
the downlink
4CC CA state



ddTddCA.PCell number of CA BTS3900 LTE
.DL.Avg UEs that treat
the local cell as
their PCell in
the downlink
FDD+TDD CA
state

.DL.Max UEs that treat
the local cell as
their PCell in
the downlink
FDD+TDD CA
state
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 status of UEs at the sampling time. The number of
CA UEs in connected mode that treat the local cell as their PCell or SCell in the downlink CA
state is sampled per second. At the end of a measurement period, the average and maximum
of these sampling results are taken as the values of the corresponding counters.
The sampling time for the number of CA UEs that treat the local cell as their SCell in the
downlink CA state is different from that for the number of CA UEs that treat the local cell as
their PCell in the downlink CA state. Therefore, the average or maximum number of CA UEs
that treat the local cell as their SCell in the downlink CA state may be greater than the average
or maximum number of CA UEs that treat the local cell as their PCell in the downlink CA
state, respectively.
In this set of counters, the number of UEs that treat the local cell as their PCell or SCell in the
downlink FDD+TDD CA state is measured separately; the number of UEs that treat the local
cell as their PCell or SCell in the downlink 3CC or 4CC CA state is measured separately. The
number of UEs that treat the local cell as their PCell or SCell in the downlink CA state minus
the number of UEs that treat the local cell as their PCell or SCell in the downlink FDD+TDD
CA state is the number of UEs that treat the local cell as their PCell or SCell in the downlink
single-duplex-mode CA state.
The following is an example:
The counter value of L.Traffic.User.PCell.DL.Avg includes the numbers of UEs that treat the
local cell as their PCell in the downlink 2CC, 3CC, 4CC, , CA state. The counter value of

L.Traffic.User.FddTddCA.PCell.DL.Avg includes the number of UEs that treat the local cell
as their PCell in the downlink FDD+TDD 2CC, 3CC, 4CC, , CA state.
L.Traffic.User.PCell.DL.Avg - L.Traffic.User.FddTddCA.PCell.DL.Avg = the number of UEs
that treat the local cell as their PCell in the downlink FDD or TDD CA state.
L.Traffic.User.PCell.DL.Avg - L.Traffic.User.PCell.DL.3CC.Avg - L.Traffic.User.PCell.DL.
4CC.Avg - (L.Traffic.User.PCell.DL.5CC.Avg, which is supported in later versions) = the
number of UEs that treat the local cell as their PCell in the downlink 2CC CA state.
Formula
None
Unit
None
Related Features
L.Traffic.User.PCell.DL.Av Multi-mode: None

g GSM: None
UMTS: None
2CC in 20MHz
LAOFD-070201
Inter-Band Carrier
Coordinated BBU
Intra-band Carrier
2CC in 30MHz
Carriers

L.Traffic.User.SCell.DL.Av Multi-mode: None

g GSM: None
UMTS: None
2CC in 20MHz
LAOFD-070201
Inter-Band Carrier
Coordinated BBU
Intra-band Carrier
2CC in 30MHz
Carriers
L.Traffic.User.PCell.DL.Ma Multi-mode: None

x GSM: None
UMTS: None
2CC in 20MHz
LAOFD-070201
Inter-Band Carrier
Coordinated BBU
Intra-band Carrier
2CC in 30MHz
Carriers

L.Traffic.User.SCell.DL.Ma Multi-mode: None

x GSM: None
UMTS: None
2CC in 20MHz
LAOFD-070201
Inter-Band Carrier
Coordinated BBU
Intra-band Carrier
2CC in 30MHz
Carriers
L.Traffic.User.PCell.DL. Multi-mode: None

3CC.Avg GSM: None
UMTS: None
Downlink 3CC

3CC.Max GSM: None
UMTS: None
Downlink 3CC

L.Traffic.User.FddTddCA. Multi-mode: MRFD-101231 FDD and TDD Carrier

3CC.PCell.DL.Avg MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC


3CC.PCell.DL.Max MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC


4CC.PCell.DL.Avg MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC


4CC.PCell.DL.Max MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC

L.Traffic.User.PCell.DL. Multi-mode: MRFD-101231 FDD and TDD Carrier

4CC.Avg MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC

L.Traffic.User.PCell.DL. Multi-mode: MRFD-101231 FDD and TDD Carrier

4CC.Max MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC

L.Traffic.User.FddTddCA.P Multi-mode: MRFD-101231 FDD and TDD Carrier

Cell.DL.Avg MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC


Cell.DL.Max MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC

1.22.9 Average Number of Activated UEs with a Specific QCI in

the Uplink Buffer
Counters
1526728445 L.Traffic.Active Total number of BTS3900, L

User.UL.QCI.T activated UEs BTS3900 LTE
otal with a QCI (or
an extended
QCI) in the
uplink buffer
1526728446 L.Traffic.Active Number of BTS3900, L

User.UL.QCI.1 activated UEs BTS3900 LTE
with the QCI of
1 in the uplink
buffer

with the QCI of
2 in the uplink
buffer

with the QCI of
3 in the uplink
buffer

with the QCI of
4 in the uplink
buffer

with the QCI of
5 in the uplink
buffer

with the QCI of
6 in the uplink
buffer



with the QCI of
7 in the uplink
buffer

with the QCI of
8 in the uplink
buffer

with the QCI of
9 in the uplink
buffer
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
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
L.Traffic.ActiveUser.UL.QC Multi-mode: None

I.Total GSM: None
UMTS: None
RRC Connection
Management

I.1 GSM: None
UMTS: None
RRC Connection
Management

I.2 GSM: None
UMTS: None
RRC Connection
Management

I.3 GSM: None
UMTS: None
RRC Connection
Management

I.4 GSM: None
UMTS: None
RRC Connection
Management


I.5 GSM: None
UMTS: None
RRC Connection
Management

I.6 GSM: None
UMTS: None
RRC Connection
Management

I.7 GSM: None
UMTS: None
RRC Connection
Management

I.8 GSM: None
UMTS: None
RRC Connection
Management

I.9 GSM: None
UMTS: None
RRC Connection
Management

1.22.10 Average Number of Activated UEs with a Specific QCI in

the Downlink Buffer
Counters
1526728455 L.Traffic.Active Total number of BTS3900, L

User.DL.QCI.T activated UEs BTS3900 LTE
otal with a QCI (or
an extended
QCI) in the
downlink buffer

User.DL.QCI.1 activated UEs BTS3900 LTE
with the QCI of
1 in the
downlink buffer

with the QCI of
2 in the
downlink buffer

with the QCI of
3 in the
downlink buffer

with the QCI of
4 in the
downlink buffer

with the QCI of
5 in the
downlink buffer

with the QCI of
6 in the
downlink buffer



with the QCI of
7 in the
downlink buffer

with the QCI of
8 in the
downlink buffer

with the QCI of
9 in the
downlink buffer
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
in RRC_CONNECTED mode that have data in the downlink buffer with a specific QCI
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
L.Traffic.ActiveUser.DL.QC Multi-mode: None

I.Total GSM: None
UMTS: None
RRC Connection
Management

I.1 GSM: None
UMTS: None
RRC Connection
Management

I.2 GSM: None
UMTS: None
RRC Connection
Management

I.3 GSM: None
UMTS: None
RRC Connection
Management

I.4 GSM: None
UMTS: None
RRC Connection
Management


I.5 GSM: None
UMTS: None
RRC Connection
Management

I.6 GSM: None
UMTS: None
RRC Connection
Management

I.7 GSM: None
UMTS: None
RRC Connection
Management

I.8 GSM: None
UMTS: None
RRC Connection
Management

I.9 GSM: None
UMTS: None
RRC Connection
Management

1.22.11 Number of UEs Configured with SRS Resources in a Cell

Counters

RS.Avg number of UEs BTS3900 LTE
configured with
sounding
reference signal
(SRS) resources
in a cell

RS.Max number of UEs BTS3900 LTE
configured with
sounding
reference signal
(SRS) resources
in a cell
Description
The counters measure the average and maximum number of UEs configured with SRS
resources in a cell.
Measurement Points
allocated SRS resources in connected mode in a cell is sampled per second. At the end of a
Formula
None
Unit
None

Related Features
L.Traffic.User.SRS.Avg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.User.SRS.Max Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
1.22.12 Number of UEs on Which TTI Bundling Takes Effect in a

Cell
Counters
1526728496 L.Traffic.User.T Average BTS3900, L

tiBundling.Avg number of UEs BTS3900 LTE
on which TTI
bundling takes
effect in a cell
Description
The counter measures the average number of UEs on which TTI bundling takes effect in a
cell.
Measurement Points
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
L.Traffic.User.TtiBundling. Multi-mode: None

Avg GSM: None
UMTS: None
1.22.13 Number of UEs on Which ROHC Takes Effect in a Cell

Counters

RoHC.Max number of UEs BTS3900 LTE
on which
ROHC takes
effect in a cell

RoHC.Avg number of UEs BTS3900 LTE
on which
ROHC takes
effect in a cell
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

Formula
None
Unit
None
Related Features
L.Traffic.User.RoHC.Max Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001017 RObust Header
TDLOFD-001017 Compression (ROHC)
RObust Header
Compression (ROHC)
L.Traffic.User.RoHC.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001017 RObust Header
TDLOFD-001017 Compression (ROHC)
RObust Header
Compression (ROHC)
1.22.14 Number of UEs on Which DRX Takes Effect in a Cell
Counters

Cdrx.Avg number of UEs BTS3900 LTE
on which DRX
takes effect in a
cell
Description
The counter measures the average number of UEs on which DRX takes effect in a cell.

Measurement Points
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
L.Traffic.User.Cdrx.Avg Multi-mode: None

GSM: None
UMTS: None
LBFD-002017 DRX
1.22.15 Number of Uplink IiCS UEs with Strong Interference in a

Cell
Counters
1526728942 L.Traffic.IICS. Average BTS3900, L

UL.StrongIntfU number of BTS3900 LTE
ser.Avg uplink strong
interference UE
in a cell
1526728943 L.Traffic.IICS. Max number of BTS3900, L

UL.StrongIntfU uplink strong BTS3900 LTE
ser.Max interference UE
in a cell
Description
These counters measure the average number of uplink IiCS UEs with strong uplink
interference.

Measurement Points
This counter is incremented by 1 each time the IicsUserAttrFlag filed is 0.
Formula
None
Unit
None
Related Features
None
1.22.16 Number of Uplink IiCS UEs with Weak Interference in a

Cell
Counters
1526728944 L.Traffic.IICS. Average BTS3900, L

UL.WeakIntfUs number of BTS3900 LTE
ewr.Avg uplink weak
interference UE
in a cell
1526728945 L.Traffic.IICS. Max number BTS3900, L

UL.WeakIntfUs umber of uplink BTS3900 LTE
ewr.Max weak
interference UE
in a cell
Description
These counters measure the average number of uplink IiCS UEs with weak interference in a
cell.
Measurement Points
This counter is incremented by 1 each time the IicsUserAttrFlag filed is 1.
Formula
None

Unit
None
Related Features
None
1.22.17 Number of Activated UEs in the Downlink in a Cell

Counters
1526728969 L.Traffic.Active Average BTS3900, L

User.DL.Avg number of BTS3900 LTE
activated UEs
in downlink
1526728970 L.Traffic.Active Maximum BTS3900, L

User.DL.Max number of BTS3900 LTE
activated UEs
in downlink
Description
The counters measure the number of UEs that have data in the downlink buffer in a cell.
Measurement Points
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
L.Traffic.ActiveUser.DL.Av Multi-mode: None

g GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.ActiveUser.DL.Ma Multi-mode: None

x GSM: None
UMTS: None
RRC Connection
Management
1.22.18 Number of Activated UEs in the Uplink in a Cell

Counters

User.UL.Avg number of BTS3900 LTE
activated UEs
in uplink

User.UL.Max number of BTS3900 LTE
activated UEs
in uplink
Description
The counters measure the number of UEs that have data in the uplink buffer in a cell.
Measurement Points
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

Formula
None
Unit
None
Related Features
L.Traffic.ActiveUser.UL.Av Multi-mode: None

g GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.ActiveUser.UL.Ma Multi-mode: None

x GSM: None
UMTS: None
RRC Connection
Management
1.22.19 Number of Activated UEs in a Cell
Counters

User.Avg number of BTS3900 LTE
activated UEs

User.Max number of BTS3900 LTE
activated UEs
Description
The counters measure the number UEs that have data in the buffer in a cell.

Measurement Points
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
L.Traffic.ActiveUser.Avg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.ActiveUser.Max Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
1.22.20 Number of UEs Enabled with the eICIC Function in a Cell
Counters
1526729297 L.Traffic.User.e Average BTS3900, L

ICIC.Avg number of UEs BTS3900 LTE
enabled with
the eICIC
function in a
cell


1526729298 L.Traffic.User.e Maximum BTS3900, L

ICIC.Max number of UEs BTS3900 LTE
enabled with
the eICIC
function in a
cell
Description
These counters measure the average number and maximum number of UEs enabled with the
eICIC function in a cell, respectively.
Measurement Points
In a cell, the eNodeB periodically measures the number of UEs in RRC connected state and
enabled with the eICIC function every 1s. At the end of each measurement period, the
eNodeB averages the measured numbers and regards the result as the value of
L.Traffic.User.eICIC.Avg. The eNodeB regards the maximum measured number as the value
of L.Traffic.User.eICIC.Max.
Formula
None
Unit
None
Related Features
L.Traffic.User.eICIC.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: LAOFD-002001 Static TDM eICIC
L.Traffic.User.eICIC.Max Multi-mode: None

GSM: None
UMTS: None

1.22.21 Average number of CoMP UEs in a cell
Counters

DLComp.Avg number of BTS3900 LTE
downlink
CoMP UEs in a
cell

DLComp.Max number of BTS3900 LTE
downlink
CoMP UEs in a
cell
Description
These counters measure the average number of downlink CoMP UEs in a cell.
Measurement Points
The number of UEs in connected mode on which downlink CoMP takes effect in a cell is
Formula
None
Unit
None
Related Features
L.Traffic.User.DLComp.Av Multi-mode: None

g GSM: None
UMTS: None
Adaptive Mode

L.Traffic.User.DLComp.Ma Multi-mode: None

x GSM: None
UMTS: None
Adaptive Mode
1.22.22 Number of UEs in a Cell That Are Close to the Border with
the Other Type of Cells in a Heterogeneous Network
Counters
1526729557 L.Traffic.Hetnet Average BTS3900, L

CEU.Avg number of UEs BTS3900 LTE
in a cell that are
close to the
border with the
other type of
cells in a
heterogeneous
network
Description
The counter measures the average number of UEs in a cell that are close to the border with the
other type of cells in a heterogeneous network.
Measurement Points
The number of UEs that are in RRC_CONNECTED mode and meet the following conditions
is sampled per second. The UE must report event A3, and the type of the neighboring cell
with the strongest reference signal received power (RSRP) in the measurement report is
different from that of the serving cell. At the end of the measurement period, the average of
these sampling results is used as the value of the L.Traffic.HetnetCEU.Avg counter.
Formula
None

Unit
None
Related Features
L.Traffic.HetnetCEU.Avg Multi-mode: None

GSM: None
UMTS: None
1.22.23 Number of UEs in a Cell That Are Close to the Border with
the Other Type of Cells and Support TDM eICIC in a
Heterogeneous Network
Counters

CEU.eICIC.Av number of UEs BTS3900 LTE
g in a cell that are
close to the
border with the
other type of
cells and
support TDM
eICIC in a
heterogeneous
network
Description
The counter measures the average number of UEs in a cell that are close to the border with the
other type of cells and support TDM eICIC in a heterogeneous network.
Measurement Points
The number of UEs that are in RRC_CONNECTED mode and meet the following conditions
is sampled per second. The UE must report event A3 and support time-domain enhanced
inter-cell interference coordination (TDM eICIC), and the type of the neighboring cells with
the strongest reference signal received power (RSRP) in the measurement report is different
from that of the serving cell. At the end of the measurement period, the average of these
sampling results is used as the value of the L.Traffic.HetnetCEU.eICIC.Avg counter.

Formula
None
Unit
None
Related Features
L.Traffic.HetnetCEU.eICIC. Multi-mode: None

Avg GSM: None
UMTS: None
1.22.24 Number of Privileged UEs in a Cell

Counters
1526730100 L.Traffic.Privile Average BTS3900, L

ge.User.avg number of BTS3900 LTE
privileged UEs
in a cell
1526730101 L.Traffic.Privile Maximum BTS3900, L

ge.User.max number of BTS3900 LTE
privileged UEs
in a cell
Description
The counters measure the average number and maximum number of privileged UEs in a cell.
Measurement Points
The counters are measured based on the status of UEs at the sampling point. The number of
privileged UEs in RRC_CONNECTED mode in a cell is sampled per second. At the end of a
measurement period, the maximum and average of these sampling results are used as the
values of the corresponding counters. Privileged UEs include UEs that perform emergency
calls and UEs with the RRC connection establishment cause value set to HighPriorityAccess.
Formula
None

Unit
None
Related Features
L.Traffic.Privilege.User.avg Multi-mode: None

GSM: None
UMTS: None
LBFD-002028 Emergency Call
TDLBFD-002028 Emergency call
L.Traffic.Privilege.User.max Multi-mode: None

GSM: None
UMTS: None
LBFD-002028 Emergency Call
TDLBFD-002028 Emergency call
1.22.25 Number of UEs Whose Uplink Timing Offsets are

Measured Based on the PUCCH
Counters

AMeas.PUCCH number of UEs BTS3900 LTE
.Avg whose uplink
timing offsets
are measured
based on the
PUCCH
1526730144 L.Traffic.User.T Maximum BTS3900, L

AMeas.PUCCH number of UEs BTS3900 LTE
.Max whose uplink
timing offsets
are measured
based on the
PUCCH

Description
The counters measure the average number and maximum number of UEs whose uplink timing
offsets are measured based on the PUCCH.
These counters apply only to LTE FDD.
Measurement Points
whose uplink timing offsets are measured based on the PUCCH 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 L.Traffic.User.TAMeas.PUCCH.Avg and
L.Traffic.User.TAMeas.PUCCH.Max counters, respectively.
Formula
None
Unit
None
Related Features
L.Traffic.User.TAMeas.PUC Multi-mode: None

CH.Avg GSM: None
UMTS: None
LTE: LBFD-070101 Uplink Timing Based on
PUCCH
L.Traffic.User.TAMeas.PUC Multi-mode: None

CH.Max GSM: None
UMTS: None
LTE: LBFD-070101 Uplink Timing Based on
PUCCH

1.22.26 Maximum Number of Activated UEs with a QCI in the

Downlink Buffer
Counters

User.DL.QCI.T number of BTS3900 LTE
otal.Max activated UEs
with a QCI (or
an extended
QCI) in the
downlink buffer

User.DL.QCI. number of BTS3900 LTE
1.Max activated UEs
with the QCI of
1 in the
downlink buffer

2.Max activated UEs
with the QCI of
2 in the
downlink buffer

3.Max activated UEs
with the QCI of
3 in the
downlink buffer

4.Max activated UEs
with the QCI of
4 in the
downlink buffer

5.Max activated UEs
with the QCI of
5 in the
downlink buffer



6.Max activated UEs
with the QCI of
6 in the
downlink buffer

7.Max activated UEs
with the QCI of
7 in the
downlink buffer

8.Max activated UEs
with the QCI of
8 in the
downlink buffer

9.Max activated UEs
with the QCI of
9 in the
downlink buffer
Description
The counters measure the maximum number of UEs that have data in the downlink buffer
area with a specific QCI 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
measurement period, the maximum of these sampling results is used as the value of the
corresponding counter. The sum of these values is used as the value of the
L.Traffic.ActiveUser.DL.QCI.Total.MAX counter.
Formula
None
Unit
None

Related Features

I.Total.Max GSM: None
UMTS: None
RRC Connection
Management

I.1.Max GSM: None
UMTS: None
RRC Connection
Management

I.2.Max GSM: None
UMTS: None
RRC Connection
Management

I.3.Max GSM: None
UMTS: None
RRC Connection
Management

I.4.Max GSM: None
UMTS: None
RRC Connection
Management


I.5.Max GSM: None
UMTS: None
RRC Connection
Management

I.6.Max GSM: None
UMTS: None
RRC Connection
Management

I.7.Max GSM: None
UMTS: None
RRC Connection
Management

I.8.Max GSM: None
UMTS: None
RRC Connection
Management

I.9.Max GSM: None
UMTS: None
RRC Connection
Management

1.22.27 Maximum Number of Activated UEs with a QCI in the

Uplink Buffer
Counters

User.UL.QCI.T number of BTS3900 LTE
otal.Max activated UEs
with a QCI (or
an extended
QCI) in the
uplink buffer

User.UL.QCI. number of BTS3900 LTE
1.Max activated UEs
with the QCI of
1 in the uplink
buffer

2.Max activated UEs
with the QCI of
2 in the uplink
buffer

3.Max activated UEs
with the QCI of
3 in the uplink
buffer

4.Max activated UEs
with the QCI of
4 in the uplink
buffer

5.Max activated UEs
with the QCI of
5 in the uplink
buffer



6.Max activated UEs
with the QCI of
6 in the uplink
buffer

7.Max activated UEs
with the QCI of
7 in the uplink
buffer

8.Max activated UEs
with the QCI of
8 in the uplink
buffer

9.Max activated UEs
with the QCI of
9 in the uplink
buffer
Description
The counters measure the maximum number of UEs that have data in the uplink buffer area
with a specific QCI in a cell.
Measurement Points
in RRC_CONNECTED mode that have data in the uplink buffer with a specific QCI
measurement period, the maximum of these sampling results is used as the value of the
corresponding counter. The sum of these values is used as the value of the
L.Traffic.ActiveUser.UL.QCI.Total.MAX counter.
Formula
None
Unit
None

Related Features

I.Total.Max GSM: None
UMTS: None
RRC Connection
Management

I.1.Max GSM: None
UMTS: None
RRC Connection
Management

I.2.Max GSM: None
UMTS: None
RRC Connection
Management

I.3.Max GSM: None
UMTS: None
RRC Connection
Management

I.4.Max GSM: None
UMTS: None
RRC Connection
Management


I.5.Max GSM: None
UMTS: None
RRC Connection
Management

I.6.Max GSM: None
UMTS: None
RRC Connection
Management

I.7.Max GSM: None
UMTS: None
RRC Connection
Management

I.8.Max GSM: None
UMTS: None
RRC Connection
Management

I.9.Max GSM: None
UMTS: None
RRC Connection
Management

1.22.28 Number of Scheduled UEs per TTI in the Downlink in a

Cell
Counters
1526730832 L.Traffic.SUNP Average BTS3900, L

T.DL.Avg number of BTS3900 LTE
scheduled UEs
per TTI in the
downlink in a
cell
1526730833 L.Traffic.SUNP Maximum BTS3900, L

T.DL.Max number of BTS3900 LTE
scheduled UEs
per TTI in the
downlink in a
cell
Description
The counters measure the average number of scheduled UEs per TTI in the downlink and the
maximum number of scheduled UEs per TTI in the downlink in a cell.
Measurement Points
The counters are measured based on the number of scheduled UEs in the sampling period.
The number of scheduled UEs within a TTI in the downlink in a cell (or a logical cell in SFN
scenarios) is sampled at the end of each TTI. A UE is regarded as being scheduled as long as
the cell successfully allocates air interface resources (CCEs or PRBs) for the UE. At the end
of a measurement period, the average and maximum of these sampling results are used as the
L.Traffic.SUNPT.DL.Avg and L.Traffic.SUNPT.DL.Max counter values, respectively. The
Formula
None
Unit
None

Related Features
L.Traffic.SUNPT.DL.Avg Multi-mode: None

GSM: None
UMTS: None
L.Traffic.SUNPT.DL.Max Multi-mode: None

GSM: None
UMTS: None
1.22.29 Number of Scheduled UEs per TTI in the Uplink in a Cell
Counters
1526730838 L.Traffic.SUNP Average BTS3900, L

T.UL.Avg number of BTS3900 LTE
scheduled UEs
per TTI in the
uplink in a cell
1526730839 L.Traffic.SUNP Maximum BTS3900, L

T.UL.Max number of BTS3900 LTE
scheduled UEs
per TTI in the
uplink in a cell
Description
The counters measure the average number of scheduled UEs per TTI in the uplink and the
maximum number of scheduled UEs per TTI in the uplink in a cell.
Measurement Points
The counters are measured based on the number of scheduled UEs in the sampling period.
The number of scheduled UEs within a TTI in the uplink in a cell (or a logical cell in SFN
scenarios) is sampled at the end of each TTI. A UE is regarded as being scheduled as long as
the cell successfully allocates air interface resources (CCEs or PRBs) for the UE. At the end
of a measurement period, the average and maximum of these sampling results are used as the
L.Traffic.SUNPT.UL.Avg and L.Traffic.SUNPT.UL.Max counter values, respectively. The

Formula
None
Unit
None
Related Features
L.Traffic.SUNPT.UL.Avg Multi-mode: None

GSM: None
UMTS: None
L.Traffic.SUNPT.UL.Max Multi-mode: None

GSM: None
UMTS: None
1.22.30 Maximum Total Number of Scheduled UEs per TTI in the

Uplink and Downlink in a Cell
Counters
1526730840 L.Traffic.SUNP Maximum total BTS3900, L

T.ULDL.Max number of BTS3900 LTE
scheduled UEs
per TTI in the
uplink and
downlink in a
cell
Description
The counter measures the maximum total number of scheduled UEs per TTI in the uplink and
downlink in a cell.

Measurement Points
The counter is measured based on the number of scheduled UEs in the sampling period. The
total number of scheduled UEs within a TTI in the uplink and downlink in a cell (or a logical
cell in SFN scenarios) is sampled at the end of each TTI. If the cell successfully allocates air
interface resources (CCEs or PRBs) for a UE, the UE is scheduled. At the end of a
measurement period, the maximum of these sampling results is used as the
L.Traffic.SUNPT.ULDL.Max counter value.
Formula
None
Unit
None
Related Features
L.Traffic.SUNPT.ULDL.Ma Multi-mode: None

x GSM: None
UMTS: None
1.22.31 Licensed Number of UEs in RRC_CONNECTED Mode

Counters
1526730878 L.Traffic.User.L Average BTS3900, L

icense.Avg licensed BTS3900 LTE
number of UEs
in
RRC_CONNE
CTED mode
Description
The counter measures the licensed number of UEs in RRC_CONNECTED mode.
Measurement Points
At the end of a measurement period, the eNodeB collects the licensed number of UEs in
RRC_CONNECTED mode of the cell and this number is used as the counter value. Currently,

the "RRC Connected User" license control item is an eNodeB-level license control item. The
counter measures the average licensed value of all activated cells in the eNodeB.
Formula
None
Unit
None
Related Features
L.Traffic.User.License.Avg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
1.22.32 Number of UEs running unlimited services
Counters

US.Avg number of UEs BTS3900 LTE
running
unlimited
services

US.Max number of UEs BTS3900 LTE
running
unlimited
services
Description
The counters measure the average and maximum number of UEs running unlimited services
in a cell.

Measurement Points
The counters are measured based on the state of UEs running unlimited services at the
sampling time. The number of UEs running unlimited services in connected mode in a cell is
Formula
None
Unit
None
Related Features
L.Traffic.User.US.Avg Multi-mode: None

GSM: None
UMTS: None
Management
L.Traffic.User.US.Max Multi-mode: None

GSM: None
UMTS: None
Management
1.22.33 Average and Maximum Numbers of Activated CA UEs

That Use the Local Cell As Their Scell
Counters

Cell.Active.DL. number of BTS3900 LTE
Avg activated CA
UEs that use the
local cell as
their Scell



Cell.Active.DL. number of BTS3900 LTE
Max activated CA
UEs that use the
local cell as
their Scell
Description
The counters measure the average and maximum numbers of CA UEs that use the local cell as
their secondary serving cell (SCell) which are activated for the CA UEs.
Measurement Points
The number of CA UEs in a cell that use the local cell as their secondary serving cells which
are activated for the CA UEs 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. According to 3GPP specifications, the activation and deactivation of a SCell is
controlled by the MAC control element. Therefore, this counter is measured at the MAC layer
and is not a counter related to RRC connection.
Formula
None
Unit
None

Related Features
L.Traffic.User.SCell.Active. Multi-mode: None

DL.Avg GSM: None
UMTS: None
2CC in 20MHz
LAOFD-070201
Inter-Band Carrier
Coordinated BBU
Intra-band Carrier
2CC in 30MHz
Carriers

DL.Max GSM: None
UMTS: None
2CC in 20MHz
LAOFD-070201
Inter-Band Carrier
Coordinated BBU
Intra-band Carrier
2CC in 30MHz
Carriers

1.22.34 Number of Times the UE Quantity in a Cell Falls Within

Different Ranges
Counters
1526732676 L.Traffic.User.I Number of BTS3900, L

ndex0 times the UE BTS3900 LTE
quantity in a
cell falls within
the range
indicated by
index 0

quantity in a
cell falls within
the range
indicated by
index 1

quantity in a
cell falls within
the range
indicated by
index 2

quantity in a
cell falls within
the range
indicated by
index 3

quantity in a
cell falls within
the range
indicated by
index 4



quantity in a
cell falls within
the range
indicated by
index 5

quantity in a
cell falls within
the range
indicated by
index 6

quantity in a
cell falls within
the range
indicated by
index 7

quantity in a
cell falls within
the range
indicated by
index 8

quantity in a
cell falls within
the range
indicated by
index 9

quantity in a
cell falls within
the range
indicated by
index 10

Description
The counters measure the distribution of the number of UEs in RRC_CONNECTED mode in
a cell.
Measurement Points
The CellUserNumPdfThd parameter specifies the UE quantity reference for performance
measurement related to these counters. The default value of this parameter is 400. Based on
the UE quantity reference, the UE quantity in a cell is divided into the following eleven
ranges as ranges 0 to 10: [0, N/10), [N/10, 2N/10), [2N/10, 3N/10), [3N/10, 4N/10), [4N/10,
5N/10), [5N/10, 6N/10), [6N/10, 7N/10), [7N/10, 8N/10), [8N/10, 9N/10), [9N/10, N), and
[N, infinity). N is specified by the CellUserNumPdfThd parameter. The number of UEs in
RRC_CONNECTED mode in a cell is sampled per second. If the UE quantity falls within a
specific range, the corresponding counter is incremented by 1. A deviation of one sampling
period may exist in the sampling timer when the timer performs time synchronization.
Formula
None
Unit
None
Related Features
L.Traffic.User.Index0 Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management

GSM: None
UMTS: None
RRC Connection
Management


GSM: None
UMTS: None
RRC Connection
Management

GSM: None
UMTS: None
RRC Connection
Management

GSM: None
UMTS: None
RRC Connection
Management

GSM: None
UMTS: None
RRC Connection
Management

GSM: None
UMTS: None
RRC Connection
Management


GSM: None
UMTS: None
RRC Connection
Management

GSM: None
UMTS: None
RRC Connection
Management

GSM: None
UMTS: None
RRC Connection
Management

GSM: None
UMTS: None
RRC Connection
Management
1.22.35 Number of VoIP UEs in a Cell

Counters

VoIP.Avg number of VoIP BTS3900 LTE
UEs in a cell



VoIP.Max number of VoIP BTS3900 LTE
UEs in a cell
Description
The counters measure the average number of VoIP UEs and maximum number of VoIP UEs
in a cell.
Measurement Points
The counters are measured based on the status of UEs at the sampling point. The number of
UEs in RRC_CONNECTED mode performing services with QCI 1 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 L.Traffic.User.VoIP.Avg and Traffic.User.VoIP.Max counter values,
respectively.
Formula
None
Unit
None
Related Features
L.Traffic.User.VoIP.Avg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.User.VoIP.Max Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management

1.22.36 Number of UEs that apply TM9 in a cell

Counters

M9.Avg number of UEs BTS3900 LTE
that apply TM9
in a cell
Description
The counter measures the average number of UEs that apply TM9 in a cell.
Measurement Points
The number of connected-mode UEs that apply TM9 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 this
counter.
Formula
None
Unit
None
Related Features
L.Traffic.User.TM9.Avg Multi-mode: None

GSM: None
UMTS: None
Management
LOFD-001001
DL 4x2 MIMO
DL 2x2 MIMO

1.22.37 Average Number and Maximum Number of Uplink CA

UEs that Use the Local Cell as Their Scell
Counters

Cell.UL.Avg number of BTS3900 LTE
uplink CA UEs
that use the
local cell as
their Scell

Cell.UL.Max number of BTS3900 LTE
uplink CA UEs
that use the
local cell as
their Scell
Description
The counters measure the average number and maximum number of uplink CA UEs that use
the local cell as their SCell.
Measurement Points
The counters are measured based on the status of UEs at the sampling time. The number of
uplink CA UEs that use the local cell as their SCell is sampled per second. At the end of a
Formula
None
Unit
None

Related Features
L.Traffic.User.SCell.UL.Av Multi-mode: None

g GSM: None
UMTS: None
Uplink 2CC
L.Traffic.User.SCell.UL.Ma Multi-mode: None

x GSM: None
UMTS: None
Uplink 2CC
1.22.38 Average and Maximum Number of CA UEs that Use the

Local Cell as Their PCells in the Uplink
Counters

Cell.UL.Avg number of CA BTS3900 LTE
UEs that use the
local cell as
their PCells in
the uplink

Cell.UL.Max number of CA BTS3900 LTE
UEs that use the
local cell as
their PCells in
the uplink
Description
The counters measure the average number and maximum number of UEs that are in the uplink
CA state and treat the local cell as their PCell.

Measurement Points
The counters are measured based on the status of UEs at the sampling time. The number of all
CA UEs in a cell that use the local cell as their primary serving cells is sampled per second.
At the end of a measurement period, the maximum and average of these sampling results are
used as the values of the corresponding counters.
Formula
None
Unit
None
Related Features
L.Traffic.User.PCell.UL.Av Multi-mode: None

g GSM: None
UMTS: None
Uplink 2CC
L.Traffic.User.PCell.UL.Ma Multi-mode: None

x GSM: None
UMTS: None
Uplink 2CC

1.22.39 Average Number and Maximum Number of Downlink

Relaxed-Backhaul-based Inter-eNodeB CA UEs that Treat the
Local Cell as Their PCell or Scell
Counters

Cell.DL.Relaxe number of BTS3900 LTE
dBackhaulCA. downlink
Avg relaxed-
backhaul-based
inter-eNodeB
CA UEs that
treat the local
cell as their
Pcell

Max relaxed-
backhaul-based
inter-eNodeB
CA UEs that
treat the local
cell as their
Pcell

Max relaxed-
backhaul-based
inter-eNodeB
CA UEs that
treat the local
cell as their
SCell

Avg relaxed-
backhaul-based
inter-eNodeB
CA UEs that
treat the local
cell as their
SCell

Description
The counters measure the average number and maximum number of downlink relaxed-
backhaul-based inter-eNodeB CA UEs that treat the local cell as their PCell or SCell.
Measurement Points
The counters are measured based on the status of UEs at the sampling time. The number of all
UEs in RRC_CONNECTED mode in a cell that are using downlink relaxed-backhaul-based
inter-eNodeB CA and treat the cell as their PCell or SCell is sampled per second. At the end
of a measurement period, the maximum and average of these sampling results are used as the
Formula
None
Unit
None
Related Features
L.Traffic.User.PCell.DL.Rel Multi-mode: None

axedBackhaulCA.Avg GSM: None
UMTS: None
Relaxed Backhaul
L.Traffic.User.PCell.DL.Rel Multi-mode: None

axedBackhaulCA.Max GSM: None
UMTS: None
Relaxed Backhaul

L.Traffic.User.SCell.DL.Rel Multi-mode: None

axedBackhaulCA.Max GSM: None
UMTS: None
Relaxed Backhaul
L.Traffic.User.SCell.DL.Rel Multi-mode: None

axedBackhaulCA.Avg GSM: None
UMTS: None
Relaxed Backhaul
1.22.40 Average and Maximum Number of CA UEs with the Local

Cell as Their PCell and with All Configured Two SCCs Activated
Counters

3CC.Active.Av UEs with the
g local cell as
their PCell and
with all
configured two
SCCs activated

3CC.Active.Ma UEs with the
x local cell as
PCell and with
all configured
two SCCs
activated

Description
The counters measure the average and maximum number of CA UEs with the local cell as
their PCell and with all configured two SCCs activated.
Measurement Points
The average and maximum number of UEs with the local cell as their PCell and with all
configured two SCCs activated are calculated in each measurement period.
Formula
None
Unit
None
Related Features

3CC.Active.Avg GSM: None
UMTS: None
Downlink 3CC

3CC.Active.Max GSM: None
UMTS: None
Downlink 3CC

1.22.41 Average Number and Maximum Number of CA UEs that

Treat the Local Cell as Their SCell and Have the Cell Activated in
the Uplink
Counters

Cell.Active.UL. number of CA BTS3900 LTE
Avg UEs that treat
the local cell as
their SCell and
have the SCell
activated in the
uplink

Cell.Active.UL. number of CA BTS3900 LTE
Max UEs that treat
the local cell as
their SCell and
have the SCell
activated in the
uplink
Description
The counters measure the average number and maximum number of CA UEs that treat the
local cell as their SCell and have the SCell activated in the uplink.
Measurement Points
The number of CA UEs that treat the local cell as their secondary serving cell (SCell) which is
activated for the CA UEs in the uplink 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. According to 3GPP specifications, the activation and deactivation of
an SCell is controlled by the MAC control element. Therefore, this counter is measured at the
MAC layer and is not a counter related to RRC connection.
Formula
None
Unit
None

Related Features

UL.Avg GSM: None
UMTS: None
Uplink 2CC

UL.Max GSM: None
UMTS: None
Uplink 2CC
1.22.42 Duration of CA UEs in the Uplink CA State that Treat the

Local Cell as Their PCell and Have the SCell Activated
Counters
1526733021 L.CA.UL.PCell Duration of CA BTS3900, L

.Act.Dur UEs in the BTS3900 LTE
uplink CA state
that treat the
local cell as
their PCell and
have the SCell
activated
Description
The counter measures the duration of CA UEs in the uplink CA state that treat the local cell as
their PCell and have the SCell activated.
Measurement Points
The duration in which CA UEs that are in the uplink CA state and treat the local cell as their
PCell have the SCell activated is accumulated as the counter value.

Formula
None
Unit
ms
Related Features
L.CA.UL.PCell.Act.Dur Multi-mode: None

GSM: None
UMTS: None
Uplink 2CC
1.22.43 Duration of CA UEs in the Uplink CA State that Treat the

Local Cell as Their SCell and Have the SCell Activated
Counters
1526733022 L.CA.UL.SCell Duration of CA BTS3900, L

.Act.Dur UEs in the BTS3900 LTE
uplink CA state
that treat the
local cell as
their SCell and
have the SCell
activated
Description
The counter measures the duration of CA UEs in the uplink CA state that treat the local cell as
their SCell and have the SCell activated.
Measurement Points
The duration in which CA UEs that are in the uplink CA state and treat the local cell as their
SCell have the SCell activated is accumulated as the counter value.

Formula
None
Unit
ms
Related Features
L.CA.UL.SCell.Act.Dur Multi-mode: None

GSM: None
UMTS: None
Uplink 2CC
1.22.44 Number of Times Inter-eNodeB CA based on Relaxed

Backhaul Stops Because the Inter-eNodeB Transmission Delay
Does Not Meet the Requirement
Counters
1526733198 L.Traffic.User.P Number of BTS3900, L

Cell.RelaxedBa times inter- BTS3900 LTE
ckhaulCA.OFF eNodeB CA
based on
relaxed
backhaul stops
because the
inter-eNodeB
transmission
delay does not
meet the
requirement
Description
The counter measures the number of times inter-eNodeB CA based on relaxed backhaul stops
because the inter-eNodeB transmission delay does not meet the requirement.

Measurement Points
The number of times inter-eNodeB CA based on relaxed backhaul stops for a CA UE that
treats the local cell as its PCell at the sampling time because the inter-eNodeB transmission
delay does not meet the requirement.
Formula
None
Unit
None
Related Features
L.Traffic.User.PCell.Relaxe Multi-mode: None

dBackhaulCA.OFF GSM: None
UMTS: None
Relaxed Backhaul
1.22.45 Number of UEs on Which Smart DRX Takes Effect in a

Cell
Counters

martdrx.Avg number of UEs BTS3900 LTE
on which Smart
DRX takes
effect in a cell
Description
The counter measures the average number of UEs on which Smart DRX takes effect in a cell.

Measurement Points
connected UEs on which Smart 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
None
1.22.46 Number of UEs that Are Configured with a GBR and

Whose Throughput Falls Within Different Ranges
Counters
1526736781 L.Traffic.GBR Number of UEs BTS3900, L

User.BitRate.In that are BTS3900 LTE
dex0 configured with
a GBR and
whose
throughput falls
within range 0
in a cell

a GBR and
whose
throughput falls
within range 1
in a cell

a GBR and
whose
throughput falls
within range 2
in a cell



a GBR and
whose
throughput falls
within range 3
in a cell

a GBR and
whose
throughput falls
within range 4
in a cell

a GBR and
whose
throughput falls
within range 5
in a cell

a GBR and
whose
throughput falls
within range 6
in a cell
Description
The counters measure the number of UEs that are configured with a GBR and whose
throughput falls within different ranges. The UE throughput ranges include:
Range 0: (0, 256 Kbit/s)
Range 1: [256 Kbit/s, 512 Kbit/s)
Range 2: [512 Kbit/s, 1 Mbit/s)
Range 3: [1 Mbit/s, 2 Mbit/s)

Range 6: [4 Mbit/s, plus infinity)
Measurement Points
The number of UEs that are configured with a GBR and whose throughput falls within per
range is sampled per second. At the end of a measurement period, the average of these
UE throughput is measured in the same way as the L.Thrp.DL.BitRate.Samp.Index0 counter.
The downlink throughput of a UE is sampled per second except the last TTI before the buffer
is empty, and the sampling result is marked as A. The data transmission duration except the
last TTI of a UE before the buffer is empty is sampled per second, and the sampling result is
marked as B. The UE throughput is calculated by using the formula: User_Throughput = A/B.
Formula
None
Unit
None
Related Features
L.Traffic.GBRUser.BitRate. Multi-mode: MRFD-101401 UL Unified Video Steering

Index0 GSM: None
UMTS: None
LTE: None

Index1 GSM: None
UMTS: None
LTE: None

Index2 GSM: None
UMTS: None
LTE: None

Index3 GSM: None
UMTS: None
LTE: None


Index4 GSM: None
UMTS: None
LTE: None

Index5 GSM: None
UMTS: None
LTE: None

Index6 GSM: None
UMTS: None
LTE: None
1.22.47 Average Number of FeICIC-capable UEs in a Cell

Counters

eICIC.Avg number of BTS3900 LTE
FeICIC-capable
UEs in a cell
Description
The counter measures the average number of FeICIC-capable UEs in a cell.
Measurement Points
The number of FeICIC-capable UEs in connected mode 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
L.Traffic.User.FeICIC.Avg counter.
Formula
None
Unit
None

Related Features
L.Traffic.User.FeICIC.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: LAOFD-081234 FeICIC
1.22.48 Average Number of FeICIC-capable UEs in a Cell that Are

Close to the Border with the Other Type of Cells in a HetNet
Counters

CEU.FeICIC.A number of BTS3900 LTE
vg FeICIC-capable
UEs in a cell
that are close to
the border with
the other type
of cells in a
HetNet
Description
The counter measures the average number of FeICIC-capable UEs in a cell that are close to
the border with the other type of cells in a HetNet.
Measurement Points
The number of UEs that are in RRC_CONNECTED mode and that meet the following
conditions are sampled per second:
1. UEs report event A3.
2. The type of the neighboring cells with the strongest reference signal received power
(RSRP) in the measurement report is different from that of the serving cell.
3. UEs support FeICIC.
At the end of a measurement period, the average of these sampling results is used as the value
of the L.Traffic.HetnetCEU.FeICIC.Avg counter.

Formula
None
Unit
None
Related Features
L.Traffic.HetnetCEU.FeICI Multi-mode: None

C.Avg GSM: None
UMTS: None
LTE: LAOFD-081234 FeICIC
1.22.49 Number of CEUs in Adaptive ICIC in a Cell
Counters
1526737747 L.Traffic.User. Number of UEs BTS3900, L

CEU.DL.AICI identified as BTS3900 LTE
C.Avg CEUs in
downlink
adaptive ICIC
Description
The counter measures the number of UEs that are identified as CEUs in a cell.
Measurement Points
The number of UEs that are identified as CEUs in downlink adaptive ICIC in a cell is
collected per second. At the end of a measurement period, the average of these collected
numbers is used as the L.Traffic.User.CEU.DL.AICIC.Avg counter value.
Formula
None
Unit
None

Related Features
L.Traffic.User.CEU.DL.AIC Multi-mode: None

IC.Avg GSM: None
UMTS: None
Transport Channel
Management
1.22.50 Average number of UEs for Which Coordinated Uplink

AMC Is Used in a Cell
Counters
1526737749 L.ULCAMC.Us Average BTS3900, L

er.Avg number of UEs BTS3900 LTE
for which
coordinated
uplink AMC is
used in a cell
Description
The counter measures the average number of UEs for which coordinated uplink AMC is used
in a cell.
This counter applies only to LTE FDD.
Measurement Points
The number of UEs that use coordinated uplink AMC is used 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 L.ULCAMC.User.Avg counter. If the MCS is selected for a UE based on the SINR
predicted by coordinated uplink AMC for any initial transmission within a sampling period,
this UE is considered as a UE that uses coordinated uplink AMC.
Formula
None

Unit
None
Related Features
L.ULCAMC.User.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-081206 Intra-eNodeB Coordinated
Uplink AMC
1.22.51 Average Number of Inter-eNodeB DL CoMP UEs in a Cell
Counters
1526737752 L.Traffic.User.I Average BTS3900, L

nterEnbDLCom number of DL BTS3900 LTE
p.Avg CoMP UEs in a
cell
Description
The counters measure the average number of inter-eNodeB DL CoMP UEs in a cell.
The L.Traffic.User.InterEnbDLComp.Avg counter applies only to LTE TDD.
Measurement Points
The number of UEs in connected mode on which inter-eNodeB DL CoMP 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 value of the counter.
Formula
None
Unit
None

Related Features
L.Traffic.User.InterEnbDLC Multi-mode: None

omp.Avg GSM: None
UMTS: None
TDLAOFD-081411 Intra-eNodeB DL CoMP in
Adaptive Mode
TDLAOFD-110408
based on Relaxed backhaul
Based on Coordinated BBU
1.22.52 Average Number of UEs Using the UMTS and LTE Shared
Spectrum in a Cell
Counters
1526737760 L.Traffic.ULSh Average BTS3900, L

ared.USER.Avg number of UEs BTS3900 LTE
using the
UMTS and LTE
shared spectrum
in a cell
Description
The counter measures the average number of UEs using the UMTS and LTE shared spectrum
in a cell.
Measurement Points
The counter is measured based on the status of UEs at the sampling time. The number of UEs
using the UMTS and LTE shared spectrum is sampled per second. At the end of a
measurement period, the average of these sampling results is taken as the
L.Traffic.ULShared.USER.Avg counter value.
Formula
None

Unit
None
Related Features
L.Traffic.ULShared.USER. Multi-mode: MRFD-101221 UL Refarming Zero

Avg GSM: None Bufferzone
UMTS: None
LTE: None
1.22.53 Number of CA UEs That Treat the Local Cell as Their

PCell and Have All SCells Activated
Counters

Cell.DL.Active. number of CA BTS3900 LTE
Avg UEs that treat
the local cell as
their PCell and
have all SCells
activated

Cell.DL.Active. number of CA BTS3900 LTE
Max UEs that treat
the local cell as
their PCell and
have all SCells
activated
Description
local cell as their PCell and have all SCells activated.
Measurement Points
The number of CA UEs that treat the local cell as their PCell and have all SCells activated is
sampling results are taken as the values of the corresponding counters.

Formula
None
Unit
None

Related Features
L.Traffic.User.PCell.DL.Act Multi-mode: MRFD-101231 FDD and TDD Carrier

ive.Avg MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC

L.Traffic.User.PCell.DL.Act Multi-mode: MRFD-101231 FDD and TDD Carrier

ive.Max MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC


PCell and Have All SCells Activated for Downlink 4CC CA
Counters

CA. number of CA BTS3900 LTE
Active.Avg the local cell as
their PCell and
have all SCells
activated for
downlink 4CC
CA

CA. number of CA BTS3900 LTE
Active.Max the local cell as
their PCell and
have all SCells
activated for
downlink 4CC
CA
Description
local cell as their PCell and have all SCells activated for downlink 4CC CA.
Measurement Points
The number of UEs that treat the local cell as their PCell and have all SCells activated for
downlink 4CC CA is sampled per second. At the end of a measurement period, the average
and maximum of these sampling results are taken as the values of the corresponding counters.
Formula
None
Unit
None

Related Features
L.Traffic.User.CA. Multi-mode: MRFD-101231 FDD and TDD Carrier

4CC.PCell.DL.Active.Avg MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC

L.Traffic.User.CA. Multi-mode: MRFD-101231 FDD and TDD Carrier

4CC.PCell.DL.Active.Max MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC


PCell and Have All SCells Activated for Downlink FDD+TDD
CA
Counters

.DL.Active.Avg UEs that treat
the local cell as
their PCell and
have all SCells
activated for
downlink FDD
+TDD CA

.DL.Active.Ma UEs that treat
x the local cell as
their PCell and
have all SCells
activated for
downlink FDD
+TDD CA
Description
local cell as their PCell and have all SCells activated for downlink FDD+TDD CA.
Measurement Points
The number of CA UEs that treat the local cell as their PCell and have all SCells activated for
downlink FDD+TDD CA is sampled per second. At the end of a measurement period, the
average and maximum of these sampling results are taken as the values of the corresponding
counters.
Formula
None
Unit
None

Related Features

Cell.DL.Active.Avg MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC


Cell.DL.Active.Max MRFD-101222 Aggregation(TDD)
UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC


3CC CA
Counters

their PCell and
have all SCells
activated for
downlink FDD
+TDD 3CC CA

their PCell and
have all SCells
activated for
downlink FDD
+TDD 3CC CA
Description
local cell as their PCell and have all SCells activated for downlink FDD+TDD 3CC CA.
Measurement Points
downlink FDD+TDD 3CC CA is sampled per second. At the end of a measurement period,
the average and maximum of these sampling results are taken as the values of the
Formula
None
Unit
None

Related Features

UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC


UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC


4CC CA
Counters

their PCell and
have all SCells
activated for
downlink FDD
+TDD 4CC CA

their PCell and
have all SCells
activated for
downlink FDD
+TDD 4CC CA
Description
local cell as their PCell and have all SCells activated for downlink FDD+TDD 4CC CA.
Measurement Points
downlink FDD+TDD 4CC CA is sampled per second. At the end of a measurement period,
the average and maximum of these sampling results are taken as the values of the
According to 3GPP specifications, the deactivation of an SCell is controlled by the MAC

control element. Therefore, this counter is measured at the MAC layer and is not a counter
related to RRC connection.
Formula
None

Unit
None
Related Features

UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC


UMTS: None
LTE: LAOFD-00100101
LAOFD-00100102
Intra-Band Carrier
2CC in 20MHz
LAOFD-080208
TDLAOFD-081405
DL 4x4 MIMO
Intra-band Carrier
2CC in 30MHz
Carriers
Downlink 4CC
Downlink 3CC

1.22.58 Number of UEs with Service Data to Be Transmitted in a

Cell
Counters
1526737851 L.Traffic.User.I Average BTS3900, L

nSession.Avg number of UEs BTS3900 LTE
with service
data to be
transmitted in a
cell
1526737852 L.Traffic.User.I Maximum BTS3900, L

nSession.Max number of UEs BTS3900 LTE
with service
data to be
transmitted in a
cell
Description
The counters measure the average number of UEs with service data to be transmitted in a cell.
Measurement Points
The counters are measured based on the UE state at the sampling time. The eNodeB samples
the number of UEs in RRC_CONNECTED mode with data in the buffer regardless of
whether the data is in the uplink or downlink every 100 ms in a cell. At the end of each
measurement period, the average value of these sampling results is used as the average
number of valid RRC connections and the maximum value of these sampling results is used
as the maximum number of valid RRC connections.
Formula
None
Unit
None

Related Features
L.Traffic.User.InSession.Av Multi-mode: None

g GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.User.InSession.Ma Multi-mode: None

x GSM: None
UMTS: None
RRC Connection
Management
1.23 Outgoing Inter-RAT Handover Measurement

(HO.IRAT.Out.Cell)
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 1-140, Figure 1-141, and Figure 1-142.

Figure 1-140
Figure 1-141

Figure 1-142
Counters
Description
1526726986 L.IRATHO.E2C.Pr Number of inter- BTS3900:

epAttOut RAT handover V100R008C00
attempts from E- BTS3900 LTE:
UTRAN to version earlier than
CDMA2000 V100R003C00
network
1526726987 L.IRATHO.E2C.E Number of inter- BTS3900:

xecAttOut RAT Handovers V100R008C00
executions from E- BTS3900 LTE:
CDMA2000 V100R003C00
network
1526726988 L.IRATHO.E2C.E Number of BTS3900:

xecSuccOut successful inter-RAT V100R008C00
handovers from E- BTS3900 LTE:
CDMA2000 V100R003C00
network
1526726989 L.IRATHO.E2W.P Number of inter- BTS3900:

repAttOut RAT handover V100R008C00
WCDMA network V100R003C00
1526726990 L.IRATHO.E2W.E Number of inter- BTS3900:

xecAttOut RAT handover V100R008C00


Description
1526726991 L.IRATHO.E2W.E Number of BTS3900:

1526726992 L.IRATHO.E2G.Pr Number of inter- BTS3900:

epAttOut RAT handover V100R008C00
UTRAN to GERAN version earlier than
V100R003C00
1526726993 L.IRATHO.E2G.E Number of inter- BTS3900:

xecAttOut RAT handover V100R008C00
V100R003C00
1526726994 L.IRATHO.E2G.E Number of BTS3900:

V100R003C00
1526727226 L.IRATHO.E2T.Pr Number of inter- BTS3900:

epAttOut RAT Handover V100R008C00
Attempts from E- BTS3900 LTE:
UTRAN to TD- version earlier than
SCDMA network V100R003C00
1526727227 L.IRATHO.E2T.Ex Number of inter- BTS3900:

ecAttOut RAT handover V100R008C00
1526727228 L.IRATHO.E2T.Ex Number of BTS3900:

ecSuccOut successful inter-RAT V100R008C00

ep.FailOut.MME RAT handover V100R008C00
preparation failures BTS3900 LTE:
from E-UTRAN to V100R005C00
GERAN because of
faults on the MME
side


Description

ep.FailOut.NoRepl RAT handover V100R008C00
y preparation failures BTS3900 LTE:
GERAN because of
no responses from
GERAN

ep.FailOut.PrepFai RAT handover V100R008C00
lure preparation failures BTS3900 LTE:
GERAN due
tobecause GERAN
cells send handover
preparation failure
messages

ep.FailOut.MME RAT handover V100R008C00
TD-SCDMA
network because of
faults on the MME
side

ep.FailOut.NoRepl RAT handover V100R008C00
y preparation failures BTS3900 LTE:
TD-SCDMA
network due
tobecause of no
responses from TD-
SCDMA network

ep.FailOut.PrepFai RAT handover V100R008C00
lure preparation failures BTS3900 LTE:
because TD- V100R005C00
SCDMA network
cells send handover
preparation failure
messages
1526728328 L.IRATHO.BlindH Number of inter- BTS3900:

O.E2W.PrepAttOu RAT blind handover V100R008C00
t attempts from E- BTS3900 LTE:
UTRAN to V100R005C00
WCDMA network


Description

O.E2W.ExecAttOu RAT blind V100R008C00
t handovers BTS3900 LTE:
executions from E- V100R005C00
UTRAN to
WCDMA network

O.E2G.ExecAttOut RAT blind V100R008C00
handovers BTS3900 LTE:
UTRAN to GERAN
1526728313 L.IRATHO.BlindH Number of BTS3900:

O.E2W.ExecSuccO successful inter-RAT V100R008C00
ut blind handovers BTS3900 LTE:
WCDMA network

O.E2G.ExecSuccO successful inter-RAT V100R008C00
GERAN

rep.FailOut.MME RAT handover V100R008C00
WCDMA network
because of faults on
the MME side

rep.FailOut.PrepFa RAT handover V100R008C00
ilure preparation failures BTS3900 LTE:
WCDMA network
because WCDMA
network cells send
handover
preparation failure
messages


Description

rep.FailOut.NoRep RAT handover V100R008C00
ly preparation failures BTS3900 LTE:
WCDMA network
because of no
responses from
WCDMA network
1526728321 L.CSFB.PrepAtt Number of CSFB BTS3900:

indicators received V100R008C00
by the eNodeB BTS3900 LTE:
V100R005C00
1526728322 L.CSFB.PrepSucc Number of BTS3900:

successful CSFB V100R008C00
responses from the BTS3900 LTE:
eNodeB V100R005C00
1526728323 L.CSFB.E2W Number of BTS3900:

procedures for V100R008C00
CSFB to WCDMA BTS3900 LTE:
network V100R005C00
1526728324 L.CSFB.E2G Number of BTS3900:

CSFB to GERAN BTS3900 LTE:
V100R005C00
1526728330 L.RRCRedirection. Number of BTS3900:

E2W.PrepAtt redirection V100R008C00
preparations from E- BTS3900 LTE:
WCDMA network

E2W redirections from E- V100R008C00
UTRAN to BTS3900 LTE:

E2G redirections from E- V100R008C00
UTRAN to GERAN BTS3900 LTE:
V100R005C00

O.E2G.PrepAttOut RAT blind handover V100R008C00
UTRAN to GERAN V100R005C00


Description

E2G.PrepAtt redirection V100R008C00
1526728386 L.CSFB.PrepAtt.Id Number of CSFB BTS3900:

le indicators received V100R008C00
by the eNodeB for BTS3900 LTE:
UEs in idle mode V100R005C01
1526728387 L.CSFB.PrepSucc.I Number of BTS3900:

dle successful CSFB V100R008C00
responses from the BTS3900 LTE:
eNodeB for UEs in V100R005C01
idle mode
1526728388 L.CSFB.E2W.Idle Number of BTS3900:

network for UEs in V100R005C01
idle mode
1526728400 L.IRATHO.SRVC Number of inter- BTS3900:

C.E2W.PrepAttOut RAT handover V100R008C00
WCDMA network
for SRVCC

C.E2W.ExecAttOut RAT handover V100R008C00
WCDMA network
for SRVCC
1526728402 L.IRATHO.SRVC Number of BTS3900:

C.E2W.ExecSuccO successful inter-RAT V100R008C00
ut handovers from E- BTS3900 LTE:
WCDMA network
for SRVCC

C.E2G.PrepAttOut RAT handover V100R008C00
for SRVCC


Description

C.E2G.ExecAttOut RAT handover V100R008C00
for SRVCC

C.E2G.ExecSuccO successful inter-RAT V100R008C00
ut handovers from E- BTS3900 LTE:
for SRVCC

C.E2T.PrepAttOut RAT handover V100R008C00
UTRAN to TD- V100R008C00
SCDMA network
for SRVCC

C.E2T.ExecAttOut RAT handover V100R008C00
SCDMA for SRVCC

C.E2T.ExecSuccOu successful inter-RAT V100R008C00
t handovers from E- BTS3900 LTE:
SCDMA network
for SRVCC
1526728409 L.CSFB.LCS.Prep Number of LCS- BTS3900:

Att triggered CS V100R008C00
fallback indicators BTS3900 LTE:
received by the V100R008C00
eNodeB
1526728410 L.CSFB.LCS.Prep Number of BTS3900:

Succ responses sent from V100R008C00
the eNodeB to BTS3900 LTE:
MMEs for CSFB V100R008C00
triggered by LCS
1526728441 L.CCO.E2G.ExecA Number of CCO BTS3900:

ttOut executions from E- V100R008C00
V100R008C00


Description
1526728442 L.CCO.E2G.ExecS Number of BTS3900:

uccOut successful CCOs V100R008C00
from E-UTRAN to BTS3900 LTE:
GERAN V100R008C00
1526728468 L.IRATHO.E2W.N Number of inter- BTS3900:

oNRT RAT initiation V100R008C00
failures from E- BTS3900 LTE:
WCDMA network
because the adjacent
cell is not on the
NRT of the source
cell
1526728469 L.IRATHO.E2T.No Number of inter- BTS3900:

NRT RAT initiation V100R008C00
SCDMA network
cell is not on the
NRT of the source
cell
1526728470 L.IRATHO.E2G.N Number of inter- BTS3900:

oNRT RAT initiation V100R008C00
cell is not on the
NRT of the source
cell
1526728471 L.IRATHO.E21xR Number of inter- BTS3900:

TT.NoNRT RAT initiation V100R008C00
CDMA2000 1xRTT
network because the
adjacent cell is not
on the NRT of the
source cell


Description
1526728472 L.IRATHO.E2HR Number of inter- BTS3900:

PD.NoNRT RAT initiation V100R008C00
CDMA2000 HRPD
network because the
adjacent cell is not
on the NRT of the
source cell
1526728497 L.RRCRedirection. Number of CSFB- BTS3900:

E2W.CSFB based redirections V100R008C00
from E-UTRANs to BTS3900 LTE:

E2G.CSFB based redirections V100R008C00
GERAN V100R008C00

E2C.CSFB based redirections V100R008C00
CDMA2000 V100R008C00
network

E2T.CSFB based redirections V100R008C00
TD-SCDMA V100R008C00
network
1526728501 L.IRATHO.E2C.C Number of CSFB- BTS3900:

SFB.PrepAttOut based inter-RAT V100R008C00
handover BTS3900 LTE:
preparation attempts V100R008C00
from E-UTRAN to
CDMA2000
network
1526728502 L.IRATHO.E2C.C Number of CSFB- BTS3900:

SFB.ExecAttOut based handover V100R008C00
execution attempts BTS3900 LTE:
CDMA2000
network


Description
1526728503 L.IRATHO.E2C.C Number of BTS3900:

SFB.ExecSuccOut successful CSFB- V100R008C00
based inter-RAT BTS3900 LTE:
handover executions V100R008C00
from E-UTRAN to
CDMA2000
network
1526728504 L.IRATHO.E2W.C Number of CSFB- BTS3900:

from E-UTRAN to
WCDMA network

SFB.ExecAttOut based inter-RAT V100R008C00
handover execution BTS3900 LTE:
attempts from E- V100R008C00
UTRAN to
WCDMA network
1526728506 L.IRATHO.E2W.C Number of BTS3900:

from E-UTRAN to
WCDMA network
1526728507 L.IRATHO.E2G.C Number of CSFB- BTS3900:

from E-UTRAN to
GERAN

UTRAN to GERAN
1526728509 L.IRATHO.E2G.C Number of BTS3900:

from E-UTRAN to
GERAN


Description
1526728510 L.IRATHO.E2T.C Number of CSFB- BTS3900:

from E-UTRAN to
TD-SCDMA
network

UTRAN to TD-
SCDMA network
1526728512 L.IRATHO.E2T.C Number of BTS3900:

from E-UTRAN to
TD-SCDMA
network
1526728513 L.CSFB.PrepFail.C Number of CSFB BTS3900:

onflict preparation failures V100R008C00
because of process BTS3900 LTE:
conflict V100R008C00
1526728529 L.IRATHO.E2W.L Number of inter- BTS3900:

oad.PrepAttOut RAT handover V100R008C00
preparation attempts BTS3900 LTE:
WCDMA network
triggered because of
high load
1526728530 L.IRATHO.E2W.L Number of inter- BTS3900:

oad.ExecAttOut RAT handover V100R008C00
WCDMA network
high load
1526728531 L.IRATHO.E2W.L Number of BTS3900:

oad.ExecSuccOut successful inter-RAT V100R008C00
handover executions BTS3900 LTE:
WCDMA network
high load


Description
1526728532 L.IRATHO.E2G.L Number of inter- BTS3900:

oad.PrepAttOut RAT handover V100R008C00
GERAN triggered
because of high load
1526728533 L.IRATHO.E2G.L Number of inter- BTS3900:

oad.ExecAttOut RAT handover V100R008C00
GERAN triggered
1526728534 L.IRATHO.E2G.L Number of BTS3900:

oad.ExecSuccOut successful inter-RAT V100R008C00
GERAN triggered

E2W.Load redirections from E- V100R008C00
high load

E2G.Load redirections from E- V100R008C00
triggered because of V100R008C00
high load
1526728542 L.IRATHO.E2W.R Number of inter- BTS3900:

egainHPLMN.Prep RAT handover V100R008C00
AttOut attempts from E- BTS3900 LTE:
WCDMA network
triggered for UEs to
go back to the
HPLMN
1526728543 L.IRATHO.E2W.R Number of inter- BTS3900:

egainHPLMN.Exec RAT handover V100R008C00
AttOut executions from E- BTS3900 LTE:
WCDMA network
go back to the
HPLMN


Description
1526728544 L.IRATHO.E2W.R Number of BTS3900:

egainHPLMN.Exec successful inter-RAT V100R008C00
SuccOut handovers from E- BTS3900 LTE:
WCDMA network
go back to the
HPLMN
1526728560 L.IRATHO.E2W.N Number of inter- BTS3900:

oData.ExecAttOut RAT handover V100R008C00
WCDMA network
triggered for UEs
that do not transmit
or receive data
1526728561 L.IRATHO.E2W.N Number of BTS3900:

oData.ExecSuccOu successful inter-RAT V100R008C00
t handovers from E- BTS3900 LTE:
WCDMA network
triggered for UEs
that do not transmit
or receive data
1526728705 L.FlashCSFB.E2W Number of BTS3900:

procedures for flash V100R008C00
network V100R008C00
1526728706 L.FlashCSFB.E2G Number of BTS3900:

procedures for flash V100R008C00
V100R008C00
1526728707 L.CSFB.PrepAtt.E Number of CSFB BTS3900:

mergency indicators received V100R008C00
by the eNodeB for BTS3900 LTE:
emergency calls V100R008C00
1526728708 L.CSFB.PrepSucc. Number of BTS3900:

Emergency responses sent from V100R008C00
the eNodeB for BTS3900 LTE:
CSFB triggered for V100R008C00
emergency calls


Description
1526728709 L.CSFB.E2W.Eme Number of BTS3900:

rgency procedures for V100R008C00
network triggered V100R008C00
for emergency calls
1526728710 L.CSFB.E2G.Emer Number of BTS3900:

gency procedures for V100R008C00
triggered for V100R008C00
emergency calls

O.E2T.PrepAttOut RAT blind handover V100R008C00
SCDMA network

O.E2T.ExecAttOut RAT blind handover V100R008C00
SCDMA network

O.E2T.ExecSuccO successful inter-RAT V100R008C00
TD-SCDMA
network
1526728749 L.CSFB.E2T Number of BTS3900:

SRVCC to TD- BTS3900 LTE:
1526728750 L.CSFB.E2T.Idle Number of BTS3900:

SRVCC to TD- BTS3900 LTE:
for UEs in idle mode

E2T.PrepAtt redirection V100R008C00
preparations to TD- BTS3900 LTE:

E2T redirections to TD- V100R008C00
SCDMA network BTS3900 LTE:
V100R008C00


Description
1526728753 L.IRATHO.SRVC Number of CSFB- BTS3900:

C.LCS.E2W.PrepA based handover V100R008C00
ttOut attempts from E- BTS3900 LTE:
WCDMA network
for SRVCC

C.LCS.E2W.ExecA based handover V100R008C00
ttOut executions from E- BTS3900 LTE:
WCDMA network
for SRVCC

C.LCS.E2W.ExecS successful CSFB- V100R008C00
uccOut based handovers BTS3900 LTE:
WCDMA network
for SRVCC

C.LCS.E2G.PrepA based handover V100R008C00
ttOut attempts from E- BTS3900 LTE:
for SRVCC

C.LCS.E2G.ExecA based handover V100R008C00
ttOut executions from E- BTS3900 LTE:
for SRVCC

C.LCS.E2G.ExecS successful CSFB- V100R008C00
uccOut based handovers BTS3900 LTE:
GERAN for SRVCC

C.LCS.E2T.PrepAt based handover V100R008C00
tOut attempts from E- BTS3900 LTE:
SCDMA network
for SRVCC

C.LCS.E2T.ExecAt based handover V100R008C00
tOut executions from E- BTS3900 LTE:
SCDMA network
for SRVCC


Description

C.LCS.E2T.ExecSu successful CSFB- V100R008C00
ccOut based handovers BTS3900 LTE:
TD-SCDMA
network for SRVCC
1526728889 L.IRATHO.E21xR Number of BTS3900:

TT.MMEAbnormR responses for V100R008C00
sp abnormal causes BTS3900 LTE:
eNodeB from the
MME during inter-
RAT handover
executions from E-
UTRAN to
CDMA2000 1xRTT
network
1526728890 L.IRATHO.E2HR Number of BTS3900:

PD.MMEAbnorm responses for V100R008C00
Rsp abnormal causes BTS3900 LTE:
eNodeB from the
MME during inter-
RAT handover
executions from E-
UTRAN to
CDMA2000 HRPD
network
1526728891 L.IRATHO.E2W.M Number of BTS3900:

MEAbnormRsp responses for V100R008C00
abnormal causes BTS3900 LTE:
eNodeB from the
MME during inter-
RAT handover
executions from E-
UTRAN to
WCDMA network
1526728892 L.IRATHO.E2G.M Number of BTS3900:

eNodeB from the
MME during inter-
RAT handover
executions from E-
UTRAN to GERAN


Description
1526728893 L.IRATHO.E2T.M Number of BTS3900:

eNodeB from the
MME during inter-
RAT handover
executions from E-
UTRAN to TD-
SCDMA network

C.E2W.MMEAbno responses for V100R008C00
rmRsp abnormal causes BTS3900 LTE:
eNodeB from the
MME during inter-
RAT handover
executions from E-
UTRAN to
WCDMA network
for SRVCC

C.E2G.MMEAbno responses for V100R008C00
eNodeB from the
MME during inter-
RAT handover
executions from E-
UTRAN to GERAN
for SRVCC

C.E2T.MMEAbnor responses for V100R008C00
mRsp abnormal causes BTS3900 LTE:
eNodeB from the
MME during inter-
RAT handover
executions from E-
UTRAN to TD-
SCDMA network
for SRVCC


Description
1526728897 L.CCO.E2G.MME Number of BTS3900:

AbnormRsp responses for V100R008C00
eNodeB from the
MME during CCO
executions from E-
UTRAN to GERAN
1526728898 L.IRATHO.E2C.C Number of BTS3900:

SFB.MMEAbnorm responses for V100R008C00
eNodeB from the
MME during CSFB-
based inter-RAT
handover executions
from E-UTRAN to
CDMA2000
network

eNodeB from the
MME during CSFB-
based inter-RAT
handover executions
from E-UTRAN to
WCDMA network

eNodeB from the
MME during CSFB-
based inter-RAT
handover executions
from E-UTRAN to
GERAN


Description
1526728901 L.IRATHO.E2T.C Number of BTS3900:

eNodeB from the
MME during CSFB-
based inter-RAT
handover executions
from E-UTRAN to
TD-SCDMA
network
1526729054 L.CSFB.E2C Number of BTS3900:

CSFB to BTS3900 LTE:
CDMA2000 1xRTT V100R008C01
network
1526729055 L.CSFB.E2C.Emer Number of BTS3900:

gency procedures for V100R008C01
CSFB to BTS3900 LTE:
network triggered
for emergency calls
1526729260 L.CSFB.E2G.Idle Number of BTS3900:

network for UEs in V100R008C01
idle mode

PD.PrepAttOut RAT handover V100R008C01
CDMA2000 HRPD
network

PD.ExecAttOut RAT handover V100R008C01
CDMA2000 HRPD
network
1526729424 L.IRATHO.E2HR Number of BTS3900:

PD.ExecSuccOut successful inter-RAT V100R008C01
CDMA2000 HRPD
network


Description

E21xRTT.PrepAtt redirection V100R008C01
CDMA2000 1xRTT
network

E2HRPD.PrepAtt redirection V100R008C01
CDMA2000 HRPD
network

E2HRPD.PrepAtt. redirection V100R008C01
PreRegNotComple- preparations from E- BTS3900 LTE:
ted UTRAN to V100R008C01
CDMA2000 HRPD
network triggered
because the UE does
not finish
preregistration with
a CDMA2000
HRPD network

E21xRTT redirections from E- V100R008C01
network

E2HRPD redirections from E- V100R008C01
CDMA2000 HRPD V100R008C01
network
1526729432 L.IRATHO.E2W.Ti Average handover BTS3900:

meAvg duration from E- V100R008C01
1526729433 L.IRATHO.E2G.Ti Average handover BTS3900:

V100R008C01
1526729434 L.IRATHO.E2T.Ti Average handover BTS3900:

UTRAN to TD- BTS3900 LTE:


Description

overage.PrepAttOu coverage-based V100R009C00
t handover BTS3900 LTE:
from E-UTRAN to
WCDMA network

overage.ExecAttOu coverage-based V100R009C00
t handover execution BTS3900 LTE:
UTRAN to
WCDMA network

overage.ExecSuccO successful coverage- V100R009C00
ut based handover BTS3900 LTE:
UTRAN to
WCDMA network

overage.PrepAttOu coverage-based V100R009C00
t handover BTS3900 LTE:
from E-UTRAN to
GERAN

overage.ExecAttOu coverage-based V100R009C00
t handover execution BTS3900 LTE:
UTRAN to GERAN

overage.ExecSuccO successful coverage- V100R009C00
UTRAN to GERAN

E2W.Coverage coverage-based V100R009C00
redirections from E- BTS3900 LTE:
WCDMA network

E2G.Coverage coverage-based V100R009C00


Description
1526729505 L.CCOwithNACC. Number of CSFB- BTS3900:

E2G.CSFB.ExecAt based CCO with V100R009C00
tOut NACC executions BTS3900 LTE:
GERAN
1526729506 L.CCOwithNACC. Number of BTS3900:

E2G.CSFB.ExecSu successful CSFB- V100R009C00
ccOut based CCOs with BTS3900 LTE:
NACC from E- V100R009C00
UTRAN to GERAN
1526729507 L.CCOwithoutNA Number of CSFB- BTS3900:

CC.E2G.CSFB.Exe based CCO without V100R009C00
cAttOut NACC executions BTS3900 LTE:
GERAN
1526729508 L.CCOwithoutNA Number of BTS3900:

CC.E2G.CSFB.Exe successful CSFB- V100R009C00
cSuccOut based CCOs without BTS3900 LTE:
NACC from E- V100R009C00
UTRAN to GERAN

SFB.PrepAttOut.E based handover V100R009C00
mergency preparation attempts BTS3900 LTE:
to WCDMA V100R009C00
network triggered
for emergency calls

SFB.ExecAttOut.E based handover V100R009C00
mergency execution attempts BTS3900 LTE:
to WCDMA V100R009C00
network triggered
for emergency calls

SFB.ExecSuccOut. successful CSFB- V100R009C00
Emergency based handover BTS3900 LTE:
executions to V100R009C00
WCDMA network
triggered for
emergency calls

SFB.PrepAttOut.E based handover V100R009C00
mergency preparation attempts BTS3900 LTE:
to GERAN triggered V100R009C00
for emergency calls


Description

SFB.ExecAttOut.E based handover V100R009C00
mergency execution attempts BTS3900 LTE:
to GERAN triggered V100R009C00
for emergency calls

SFB.ExecSuccOut. successful CSFB- V100R009C00
Emergency based handover BTS3900 LTE:
executions to V100R009C00
GERAN triggered
for emergency calls

E2W.CSFB.TimeO based blind V100R009C00
ut redirections from E- BTS3900 LTE:
WCDMA network
caused by CSFB
protection timer
expiration

E2G.CSFB.TimeO based blind V100R009C00
ut redirections from E- BTS3900 LTE:
caused by CSFB
protection timer
expiration
1526729544 L.CSFB.E2C.Dual Number of BTS3900:

Rx procedures for dual- V100R008C01
receiver CSFB to BTS3900 LTE:
CDMA 1xRTT V100R008C01
network

E2T.Load redirections from E- V100R009C00
TDSCDMA V100R009C00
high load
1526730017 L.RRCRedirection. Number of SPID- BTS3900:

E2W.RegainHPLM based redirections V100R009C00
N back to a WCDMA BTS3900 LTE:
network of the V100R009C00
HPLMN


Description
1526730018 L.IRATHO.E2W.S Number of service- BTS3900:

ervice.PrepAttOut based handover V100R009C00
WCDMA network
1526730019 L.IRATHO.E2W.S Number of service- BTS3900:

ervice.ExecAttOut based handover V100R009C00
WCDMA network
1526730020 L.IRATHO.E2W.S Number of BTS3900:

ervice.ExecSuccOu successful service- V100R009C00
t based handover BTS3900 LTE:
UTRAN to
WCDMA network
1526730021 L.IRATHO.E2G.Se Number of service- BTS3900:

rvice.PrepAttOut based handover V100R009C00
GERAN
1526730022 L.IRATHO.E2G.Se Number of service- BTS3900:

rvice.ExecAttOut based handover V100R009C00
GERAN
1526730023 L.IRATHO.E2G.Se Number of BTS3900:

rvice.ExecSuccOut successful service- V100R009C00
based handover BTS3900 LTE:
UTRAN to GERAN
1526730024 L.RRCRedirection. Number of service- BTS3900:

E2W.Service based redirections V100R009C00
1526730025 L.RRCRedirection. Number of service- BTS3900:

E2G.Service based redirections V100R009C00
GERAN V100R009C00


Description
1526730026 L.IRATHO.E2W.U Number of UL- BTS3900:

Lquality.PrepAttO quality-based V100R009C00
ut handover BTS3900 LTE:
from E-UTRAN to
WCDMA network
1526730027 L.IRATHO.E2W.U Number of UL- BTS3900:

Lquality.ExecAttO quality-based V100R009C00
ut handover execution BTS3900 LTE:
UTRAN to
WCDMA network
1526730028 L.IRATHO.E2W.U Number of BTS3900:

Lquality.ExecSucc successful UL- V100R009C00
Out quality-based BTS3900 LTE:
from E-UTRAN to
WCDMA network
1526730029 L.IRATHO.E2G.U Number of UL- BTS3900:

Lquality.PrepAttO quality-based V100R009C00
ut handover BTS3900 LTE:
from E-UTRAN to
GERAN
1526730030 L.IRATHO.E2G.U Number of UL- BTS3900:

Lquality.ExecAttO quality-based V100R009C00
ut handover execution BTS3900 LTE:
UTRAN to GERAN
1526730031 L.IRATHO.E2G.U Number of BTS3900:

Lquality.ExecSucc successful UL- V100R009C00
Out quality-based BTS3900 LTE:
from E-UTRAN to
GERAN
1526730032 L.RRCRedirection. Number of UL- BTS3900:

E2W.Ulquality quality-based V100R009C00
WCDMA network
1526730033 L.RRCRedirection. Number of UL- BTS3900:

E2G.Ulquality quality-based V100R009C00


Description
1526730034 L.IRATHO.E2W.D Number of distance- BTS3900:

istance.PrepAttOut based handover V100R009C00
WCDMA network
1526730035 L.IRATHO.E2W.D Number of distance- BTS3900:

istance.ExecAttOut based handover V100R009C00
WCDMA network
1526730036 L.IRATHO.E2W.D Number of BTS3900:

istance.ExecSuccO successful distance- V100R009C00
UTRAN to
WCDMA network
1526730037 L.IRATHO.E2G.Di Number of distance- BTS3900:

stance.PrepAttOut based handover V100R009C00
GERAN
1526730038 L.IRATHO.E2G.Di Number of distance- BTS3900:

stance.ExecAttOut based handover V100R009C00
GERAN
1526730039 L.IRATHO.E2G.Di Number of BTS3900:

stance.ExecSuccOu successful distance- V100R009C00
t based handover BTS3900 LTE:
UTRAN to GERAN
1526730040 L.RRCRedirection. Number of distance- BTS3900:

E2W.Distance based redirections V100R009C00
1526730041 L.RRCRedirection. Number of distance- BTS3900:

E2G.Distance based redirections V100R009C00
GERAN V100R009C00


Description

SFB.Prep.FailOut. based outgoing V100R009C00
MME handover BTS3900 LTE:
preparation failures V100R009C00
from E-UTRAN to
WCDMA network
because of the MME
side causes

PrepFailure handover BTS3900 LTE:
from E-UTRAN to
WCDMA network
because of the
response of
handover
preparation failure
from WCDMA
network

NoReply handover BTS3900 LTE:
from E-UTRAN to
WCDMA network
because of no
response from
WCDMA network

MME handover BTS3900 LTE:
from E-UTRAN to
TD-SCDMA
network because of
the MME side
causes


Description

PrepFailure handover BTS3900 LTE:
from E-UTRAN to
TD-SCDMA
network because of
the response of
handover
preparation failure
from TD-SCDMA
network

NoReply handover BTS3900 LTE:
from E-UTRAN to
TD-SCDMA
network because of
no response from
TD-SCDMA
network
1526730082 L.IRATHO.E2W.S Number of SRVCC- BTS3900:

RVCC.Prep.FailOu based outgoing V100R009C00
t.MME handover BTS3900 LTE:
from E-UTRAN to
WCDMA network
because of the MME
side causes

t.PrepFailure handover BTS3900 LTE:
from E-UTRAN to
WCDMA network
because of the
response of
handover
preparation failure
from WCDMA
network


Description

t.NoReply handover BTS3900 LTE:
from E-UTRAN to
WCDMA network
because of no
response from
WCDMA network
1526730085 L.IRATHO.E2T.S Number of SRVCC- BTS3900:

from E-UTRAN to
TD-SCDMA
network because of
the MME side
causes

from E-UTRAN to
TD-SCDMA
network because of
the response of
handover
preparation failure
from TD-SCDMA
network

from E-UTRAN to
TD-SCDMA
network because of
no response from
TD-SCDMA
network


Description
1526730088 L.IRATHO.E2G.S Number of SRVCC- BTS3900:

from E-UTRAN to
GERAN because of
the MME side
causes

from E-UTRAN to
GERAN because of
the response of
handover
preparation failure
from GERAN

from E-UTRAN to
GERAN because of
no response from
GERAN
1526730091 L.IRATHO.SRVC Number of CS-only BTS3900:

C.CSonly.E2W.Pre SRVCC-based V100R009C00
pAttOut outgoing handover BTS3900 LTE:
UTRAN to
WCDMA network

C.CSonly.E2W.Exe SRVCC-based V100R009C00
cAttOut outgoing handover BTS3900 LTE:
UTRAN to
WCDMA network

C.CSonly.E2W.Exe successful CS-only V100R009C00
cSuccOut SRVCC-based BTS3900 LTE:
outgoing handovers V100R009C00
from E-UTRAN to
WCDMA network


Description

C.CSonly.E2T.Prep SRVCC-based V100R009C00
AttOut outgoing handover BTS3900 LTE:
UTRAN to TD-
SCDMA network

C.CSonly.E2T.Exec SRVCC-based V100R009C00
AttOut outgoing handover BTS3900 LTE:
UTRAN to TD-
SCDMA network

C.CSonly.E2T.Exec successful CS-only V100R009C00
SuccOut SRVCC-based BTS3900 LTE:
from E-UTRAN to
TD-SCDMA
network

C.CSonly.E2G.Pre SRVCC-based V100R009C00
pAttOut outgoing handover BTS3900 LTE:
UTRAN to GERAN

C.CSonly.E2G.Exe SRVCC-based V100R009C00
cAttOut outgoing handover BTS3900 LTE:
UTRAN to GERAN

C.CSonly.E2G.Exe successful CS-only V100R009C00
cSuccOut SRVCC-based BTS3900 LTE:
from E-UTRAN to
GERAN
1526730146 L.IRATHO.CSFB. Number of SRVCC- BTS3900:

SRVCC.E2W.Prep based outgoing V100R009C00
AttOut handover attempts BTS3900 LTE:
WCDMA network
for ultra-flash CSFB


Description

SRVCC.E2W.Exec based outgoing V100R009C00
AttOut handover executions BTS3900 LTE:
WCDMA network
1526730148 L.IRATHO.CSFB. Number of BTS3900:

SRVCC.E2W.Exec successful SRVCC- V100R009C00
SuccOut based outgoing BTS3900 LTE:
handovers from E- V100R009C00
UTRAN to
WCDMA network

O.E2W.MMEAbno responses with V100R009C00
eNodeB from the
MME during inter-
RAT blind handover
executions from E-
UTRAN to
WCDMA network

O.E2G.MMEAbno responses with V100R009C00
eNodeB from the
MME during inter-
RAT blind handover
executions from E-
UTRAN to GERAN

SRVCC.E2G.Prep based outgoing V100R009C00
AttOut handover attempts BTS3900 LTE:
GERAN for ultra-
flash CSFB

SRVCC.E2G.Exec based outgoing V100R009C00
AttOut handover executions BTS3900 LTE:
GERAN for ultra-
flash CSFB


Description
1526733008 L.IRATHO.CSFB. Number of BTS3900:

SRVCC.E2G.Exec successful SRVCC- V100R009C00
SuccOut based outgoing BTS3900 LTE:
handovers from E- V100R009C00
UTRAN to GERAN
1526733009 L.IRATHO.CSFB. Number of abnormal BTS3900:

SRVCC.E2G.MME responses from the V100R009C00
AbnormRsp MME during BTS3900 LTE:
from E-UTRAN to
GERAN for ultra-
flash CSFB
1526733190 L.IRATHO.E2T.Lo Number of inter- BTS3900:

ad.PrepAttOut RAT handover V100R008C00
TD-SCDMA
network triggered
1526733191 L.IRATHO.E2T.Lo Number of inter- BTS3900:

ad.ExecAttOut RAT handover V100R008C00
TD-SCDMA
network triggered
1526733192 L.IRATHO.E2T.Lo Number of BTS3900:

ad.ExecSuccOut successful inter-RAT V100R008C00
TD-SCDMA
network triggered
The HO.IRAT.Out.Cell function subset contains counters related to inter-RAT outgoing
handover. In terms of the target system, some of these counters can be categorized as counters
related to handover to WCDMA network, handover to GERAN, handover to TD-SCDMA
network, and handover to CDMA2000 network. In terms of the triggering cause, some of
these counters can be categorized as counters related to coverage-based handover, load-based
handover, frequency-priority-based handover, CSFB-based handover, and others. In terms of
the handover method, some of these counters can be categorized as counters related to
SRVCC and others. The counters related to SRVCC can be categorized as counters related to
CSFB-based handover for SRVCC, CS-only SRVCC, and others. In terms of the procedure,

these counters can be categorized as counters related to handover, redirection, CCO, CSFB,
and others. In terms of the failure cause, the counters related to handover failure can be
categorized as counters related to handover failure because of MME cause, no response,
preparation failure, and others. The following table shows the parent-child relationship of the
counters.
L.IRATHO.E2C.PrepAttOut L.IRATHO.E2C.CSFB.Prep -
AttOut
L.IRATHO.E2C.PrepAttOut L.IRATHO.E2HRPD.PrepA -
ttOut
L.IRATHO.E2C.ExecAttOu L.IRATHO.E2C.CSFB.Exec -
t AttOut
L.IRATHO.E2C.ExecAttOu L.IRATHO.E2HRPD.ExecA -
t ttOut
L.IRATHO.E2C.ExecSuccO L.IRATHO.E2C.CSFB.Exec L.IRATHO.E2C.CSFB.MM

ut SuccOut EAbnormRsp
L.IRATHO.E2C.ExecSuccO L.IRATHO.E21xRTT.MME -
ut AbnormRsp
L.IRATHO.E2HRPD.MME -
AbnormRsp
L.IRATHO.E2C.ExecSuccO L.IRATHO.E2HRPD.ExecS -
ut uccOut
L.IRATHO.E2W.PrepAttOu L.IRATHO.BlindHO.E2W.P -
t repAttOut
L.IRATHO.E2W.PrepAttOu L.IRATHO.SRVCC.E2W.Pr L.IRATHO.SRVCC.LCS.E2

t epAttOut W.PrepAttOut
L.IRATHO.SRVCC.E2W.Pr L.IRATHO.CSFB.SRVCC.E
epAttOut 2W.PrepAttOut
L.IRATHO.SRVCC.E2W.Pr L.IRATHO.SRVCC.CSonly.
epAttOut E2W.PrepAttOut
L.IRATHO.E2W.PrepAttOu L.IRATHO.E2W.Load.Prep L.IRATHO.E2W.UeNumLo

t AttOut ad.PrepAttOut
L.IRATHO.E2W.RegainHP -
LMN.PrepAttOut
L.IRATHO.E2W.CSFB.Prep L.IRATHO.E2W.CSFB.Prep
AttOut AttOut.Emergency
L.IRATHO.E2W.CSFB.Prep L.IRATHO.CSFB.SRVCC.E
AttOut 2W.PrepAttOut
L.IRATHO.E2W.Coverage. -
PrepAttOut

L.IRATHO.E2W.Service.Pre -
pAttOut
L.IRATHO.E2W.ULquality. -
PrepAttOut
L.IRATHO.E2W.Distance.P -
repAttOut
L.IRATHO.E2W.QOE.Prep -
AttOut
L.IRATHO.E2W.ExecAttOu L.IRATHO.BlindHO.E2W.E -
t xecAttOut
L.IRATHO.E2W.ExecAttOu L.IRATHO.SRVCC.E2W.Ex L.IRATHO.SRVCC.LCS.E2

t ecAttOut W.ExecAttOut
L.IRATHO.SRVCC.E2W.Ex L.IRATHO.CSFB.SRVCC.E
ecAttOut 2W.ExecAttOut
L.IRATHO.SRVCC.E2W.Ex L.IRATHO.SRVCC.CSonly.
ecAttOut E2W.ExecAttOut
L.IRATHO.E2W.ExecAttOu L.IRATHO.E2W.Load.Exec L.IRATHO.E2W.UeNumLo

t AttOut ad.ExecAttOut
LMN.ExecAttOut
L.IRATHO.E2W.CSFB.Exe L.IRATHO.E2W.CSFB.Exe
cAttOut cAttOut.Emergency
L.IRATHO.E2W.CSFB.Exe L.IRATHO.CSFB.SRVCC.E
cAttOut 2W.ExecAttOut
ExecAttOut
L.IRATHO.E2W.Service.Ex -
ecAttOut
ExecAttOut
L.IRATHO.E2W.Distance.E -
xecAttOut
L.IRATHO.E2W.QOE.Exec -
AttOut
L.IRATHO.E2W.ExecSucc L.IRATHO.BlindHO.E2W.E -
Out xecSuccOut
L.IRATHO.E2W.ExecSucc L.IRATHO.SRVCC.E2W.Ex L.IRATHO.SRVCC.LCS.E2

Out ecSuccOut W.ExecSuccOut

L.IRATHO.SRVCC.E2W.Ex L.IRATHO.CSFB.SRVCC.E
ecSuccOut 2W.ExecSuccOut
L.IRATHO.SRVCC.E2W.Ex L.IRATHO.SRVCC.CSonly.
ecSuccOut E2W.ExecSuccOut
L.IRATHO.SRVCC.E2W.Ex L.IRATHO.SRVCC.E2W.M
ecSuccOut MEAbnormRsp
L.IRATHO.E2W.ExecSucc L.IRATHO.E2W.Load.Exec L.IRATHO.E2W.UeNumLo

Out SuccOut ad.ExecSuccOut
LMN.ExecSuccOut
cSuccOut cSuccOut.Emergency
cSuccOut 2W.ExecSuccOut
L.IRATHO.E2W.CSFB.Exe L.IRATHO.E2W.CSFB.MM
cSuccOut EAbnormRsp
ExecSuccOut
L.IRATHO.E2W.Service.Ex -
ecSuccOut
ExecSuccOut
L.IRATHO.E2W.Distance.E -
xecSuccOut
L.IRATHO.E2W.QOE.Exec L.IRATHO.E2W.QOE.MM
SuccOut EAbnormRsp
L.IRATHO.E2W.ExecSucc L.IRATHO.E2W.MMEAbn L.IRATHO.SRVCC.E2W.M

Out ormRsp MEAbnormRsp
L.IRATHO.E2G.PrepAttOut L.IRATHO.BlindHO.E2G.P -
repAttOut
L.IRATHO.E2G.PrepAttOut L.IRATHO.SRVCC.E2G.Pr L.IRATHO.SRVCC.LCS.E2

epAttOut G.PrepAttOut
L.IRATHO.SRVCC.E2G.Pr L.IRATHO.SRVCC.CSonly.
epAttOut E2G.PrepAttOut
L.IRATHO.E2G.PrepAttOut L.IRATHO.E2G.Load.Prep -
AttOut
L.IRATHO.E2G.CSFB.Prep L.IRATHO.E2G.CSFB.Prep

L.IRATHO.E2G.Coverage.P -
repAttOut
L.IRATHO.E2G.Service.Pre -
pAttOut
L.IRATHO.E2G.ULquality. -
PrepAttOut
L.IRATHO.E2G.Distance.Pr -
epAttOut
L.IRATHO.E2G.ExecAttOu L.IRATHO.BlindHO.E2G.E -
t xecAttOut
L.IRATHO.E2G.ExecAttOu L.IRATHO.SRVCC.E2G.Ex L.IRATHO.SRVCC.LCS.E2

t ecAttOut G.ExecAttOut
L.IRATHO.SRVCC.E2G.Ex L.IRATHO.SRVCC.CSonly.
ecAttOut E2G.ExecAttOut
L.IRATHO.E2G.ExecAttOu L.IRATHO.E2G.Load.Exec -
t AttOut
L.IRATHO.E2G.CSFB.Exec L.IRATHO.E2G.CSFB.Exec
L.IRATHO.E2G.Coverage.E -
xecAttOut
L.IRATHO.E2G.Service.Ex -
ecAttOut
ExecAttOut
L.IRATHO.E2G.Distance.E -
xecAttOut
L.IRATHO.E2G.ExecSuccO L.IRATHO.BlindHO.E2G.E -
ut xecSuccOut
L.IRATHO.E2G.ExecSuccO L.IRATHO.SRVCC.E2G.Ex L.IRATHO.SRVCC.LCS.E2

ut ecSuccOut G.ExecSuccOut
L.IRATHO.SRVCC.E2G.Ex L.IRATHO.SRVCC.CSonly.
ecSuccOut E2G.ExecSuccOut
L.IRATHO.SRVCC.E2G.Ex L.IRATHO.SRVCC.E2G.M
L.IRATHO.E2G.ExecSuccO L.IRATHO.E2G.Load.Exec -
ut SuccOut
SuccOut SuccOut.Emergency

L.IRATHO.E2G.CSFB.Exec L.IRATHO.E2G.CSFB.MM
SuccOut EAbnormRsp
L.IRATHO.E2G.Coverage.E -
xecSuccOut
L.IRATHO.E2G.Service.Ex -
ecSuccOut
ExecSuccOut
L.IRATHO.E2G.Distance.E -
xecSuccOut
L.IRATHO.E2G.ExecSuccO L.IRATHO.E2G.MMEAbno L.IRATHO.SRVCC.E2G.M

ut rmRsp MEAbnormRsp
L.IRATHO.E2T.PrepAttOut L.IRATHO.BlindHO.E2T.Pr -
epAttOut
L.IRATHO.E2T.PrepAttOut L.IRATHO.SRVCC.E2T.Pre L.IRATHO.SRVCC.LCS.E2

pAttOut T.PrepAttOut
L.IRATHO.SRVCC.E2T.Pre L.IRATHO.SRVCC.CSonly.
pAttOut E2T.PrepAttOut
L.IRATHO.E2T.PrepAttOut L.IRATHO.E2T.CSFB.Prep -
AttOut
L.IRATHO.E2T.ExecAttOut L.IRATHO.BlindHO.E2T.E -
xecAttOut
L.IRATHO.E2T.ExecAttOut L.IRATHO.SRVCC.E2T.Ex L.IRATHO.SRVCC.LCS.E2

ecAttOut T.ExecAttOut
L.IRATHO.SRVCC.E2T.Ex L.IRATHO.SRVCC.CSonly.
ecAttOut E2T.ExecAttOut
L.IRATHO.E2T.ExecAttOut L.IRATHO.E2T.CSFB.Exec -
AttOut
L.IRATHO.E2T.ExecSuccO L.IRATHO.BlindHO.E2T.E -
ut xecSuccOut
L.IRATHO.E2T.ExecSuccO L.IRATHO.SRVCC.E2T.Ex L.IRATHO.SRVCC.LCS.E2

ut ecSuccOut T.ExecSuccOut
L.IRATHO.SRVCC.E2T.Ex L.IRATHO.SRVCC.CSonly.
ecSuccOut E2T.ExecSuccOut
L.IRATHO.SRVCC.E2T.Ex L.IRATHO.SRVCC.E2T.M
L.IRATHO.E2T.ExecSuccO L.IRATHO.E2T.CSFB.Exec L.IRATHO.E2T.CSFB.MM

ut SuccOut EAbnormRsp

L.IRATHO.E2T.ExecSuccO L.IRATHO.E2T.MMEAbno L.IRATHO.SRVCC.E2T.M

ut rmRsp MEAbnormRsp
L.IRATHO.E2G.Prep.FailO L.IRATHO.E2G.SRVCC.Pr -
ut.MME ep.FailOut.MME
ut.NoReply ep.FailOut.NoReply
ut.PrepFailure ep.FailOut.PrepFailure
L.IRATHO.E2T.Prep.FailOu L.IRATHO.E2T.CSFB.Prep. -
t.MME FailOut.MME
L.IRATHO.E2T.Prep.FailOu L.IRATHO.E2T.SRVCC.Pre -
t.MME p.FailOut.MME
t.NoReply FailOut.NoReply
t.NoReply p.FailOut.NoReply
t.PrepFailure FailOut.PrepFailure
t.PrepFailure p.FailOut.PrepFailure
L.IRATHO.E2W.Prep.FailO L.IRATHO.E2W.CSFB.Prep -
ut.MME .FailOut.MME
L.IRATHO.E2W.Prep.FailO L.IRATHO.E2W.SRVCC.Pr -
ut.MME ep.FailOut.MME
ut.PrepFailure .FailOut.PrepFailure
ut.PrepFailure ep.FailOut.PrepFailure
ut.NoReply .FailOut.NoReply
ut.NoReply ep.FailOut.NoReply
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.Emergen -
cy

L.CSFB.E2W L.CSFB.E2W.Idle -
L.CSFB.E2W L.RRCRedirection.E2W.CS L.FlashCSFB.E2W

FB
L.RRCRedirection.E2W.CS L.RRCRedirection.E2W.CS
FB FB.TimeOut
cAttOut cAttOut.Emergency
cAttOut 2W.ExecAttOut
L.CSFB.E2W L.CSFB.E2W.Emergency -
L.CSFB.E2G L.CSFB.E2G.Idle -
L.CSFB.E2G L.RRCRedirection.E2G.CS L.FlashCSFB.E2G

FB
L.RRCRedirection.E2G.CS L.RRCRedirection.E2G.CS
FB FB.TimeOut
L.CSFB.E2G L.CSFB.E2G.Emergency -
L.RRCRedirection.E2W L.RRCRedirection.E2W.Loa -
d
L.RRCRedirection.E2W.CS L.FlashCSFB.E2W
FB
L.RRCRedirection.E2W.CS L.RRCRedirection.E2W.CS
FB FB.TimeOut
L.RRCRedirection.E2W.Co -
verage
L.RRCRedirection.E2W.Re -
gainHPLMN
L.RRCRedirection.E2W.Ser -
vice
L.RRCRedirection.E2W.Ulq -
uality
L.RRCRedirection.E2W.Dis -
tance
L.RRCRedirection.E2G L.RRCRedirection.E2G.Loa -
d

L.RRCRedirection.E2G.CS L.FlashCSFB.E2G
FB
L.RRCRedirection.E2G.CS L.RRCRedirection.E2G.CS
FB FB.TimeOut
L.RRCRedirection.E2G.Cov -
erage
L.RRCRedirection.E2G.Ser -
vice
L.RRCRedirection.E2G.Ulq -
uality
L.RRCRedirection.E2G.Dist -
ance
L.CCO.E2G.ExecAttOut L.CCOwithNACC.E2G.CS -
FB.ExecAttOut
L.CCOwithoutNACC.E2G. -
CSFB.ExecAttOut
L.CCO.E2G.ExecSuccOut L.CCO.E2G.MMEAbnorm -
Rsp
L.CCO.E2G.ExecSuccOut L.CCOwithNACC.E2G.CS -
FB.ExecSuccOut
L.CCOwithoutNACC.E2G. -
CSFB.ExecAttOut
L.CSFB.E2T L.CSFB.E2T.Idle -
L.CSFB.E2C L.RRCRedirection.E2C.CS -
FB
L.IRATHO.E2C.CSFB.Exec -
AttOut
L.CSFB.E2C L.CSFB.E2C.Emergency -
L.CSFB.E2C L.CSFB.E2C.DualRx -
L.RRCRedirection.E2HRPD L.RRCRedirection.E2HRPD -
.PrepAtt .PrepAtt.PreRegNotComple-
ted

1.23.1 Number of Inter-RAT Handover Attempts from E-UTRAN

to CDMA2000 Network
Counters
1526726986 L.IRATHO.E2 Number of BTS3900, L

C.PrepAttOut inter-RAT BTS3900 LTE
handover
attempts from
E-UTRAN to
CDMA2000
network
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to
CDMA2000 network.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-143, 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 network after the eNodeB receives a measurement report from a UE.

Figure 1-143
Formula
None
Unit
None
Related Features
L.IRATHO.E2C.PrepAttOut Multi-mode: None

GSM: None
UMTS: None
CDMA2000
between E-UTRAN and
CDMA2000

1.23.2 Number of Inter-RAT Handovers Executions from E-

UTRAN to CDMA2000 Network
Counters

C.ExecAttOut inter-RAT BTS3900 LTE
Handovers
executions from
E-UTRAN to
CDMA2000
network
Description
The counter measure the number of inter-RAT handovers executions from E-UTRAN to
CDMA2000 network.
V10.4.0.
Measurement Points
As shown at point B in Figure 1-144, 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 1-144
Formula
None
Unit
None
Related Features
L.IRATHO.E2C.ExecAttOu Multi-mode: None

t GSM: None
UMTS: None
CDMA2000
between E-UTRAN and
CDMA2000

1.23.3 Number of Successful Inter-RAT Handovers from E-

UTRAN to CDMA2000 Network
Counters

C.ExecSuccOut successful inter- BTS3900 LTE
RAT handovers
from E-
UTRAN to
CDMA2000
network
Description
The counter measures the number of successful inter-RAT handovers from E-UTRAN to
CDMA2000 network.
V10.4.0.
Measurement Points
As shown at point C in Figure 1-145, 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 1-145
Formula
None
Unit
None

Related Features
L.IRATHO.E2C.ExecSuccO Multi-mode: None

ut GSM: None
UMTS: None
LOFD-001035 between E-UTRAN and
CDMA2000
TDLOFD-001021
CS Fallback to CDMA2000
TDLOFD-001035 1xRTT
between E-UTRAN and
CDMA2000
1xRTT

to WCDMA Network
Counters

W.PrepAttOut inter-RAT BTS3900 LTE
handover
attempts from
E-UTRAN to
WCDMA
network
Description
WCDMA network.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-146, 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 1-146
Formula
None
Unit
None

Related Features
L.IRATHO.E2W.PrepAttOu Multi-mode: MRFD-101401 UL Unified Video Steering

t GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
CS Fallback to UTRAN
TDLOFD-001022
UTRAN
SRVCC to UTRAN

UTRAN to WCDMA Network
Counters

W.ExecAttOut inter-RAT BTS3900 LTE
handover
executions from
E-UTRAN to
WCDMA
network
Description
WCDMA network.
V10.4.0.
Measurement Points
WCDMA network the L.IRATHO.E2W.ExecAttOut counter is incremented by 1 each time

Figure 1-147
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.ExecAttOu Multi-mode: MRFD-101401 UL Unified Video Steering

t GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN


UTRAN to WCDMA Network
Counters

W.ExecSuccOu successful inter- BTS3900 LTE
t RAT handovers
from E-
UTRAN to
WCDMA
network
Description
WCDMA network.
V10.4.0.
Measurement Points
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 1-148
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.ExecSucc Multi-mode: MRFD-101401 UL Unified Video Steering

Out GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN


to GERAN
Counters

G.PrepAttOut inter-RAT BTS3900 LTE
handover
attempts from
E-UTRAN to
GERAN
Description
GERAN.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-149, the L.IRATHO.E2G.PrepAttOut counter is incremented
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 1-149
Formula
None
Unit
None
Related Features
L.IRATHO.E2G.PrepAttOut Multi-mode: None

GSM: None
UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN
TDLOFD-001020
CS Fallback to GERAN
TDLOFD-001023
GERAN
SRVCC to GERAN


UTRAN to GERAN
Counters

G.ExecAttOut inter-RAT BTS3900 LTE
handover
executions from
E-UTRAN to
GERAN
Description
GERAN.
V10.4.0.
Measurement Points
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 1-150
Formula
None
Unit
None
Related Features
L.IRATHO.E2G.ExecAttOu Multi-mode: None

t GSM: None
UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN
TDLOFD-001020
TDLOFD-001023
GERAN
SRVCC to GERAN


UTRAN to GERAN
Counters

G.ExecSuccOut successful inter- BTS3900 LTE
RAT handovers
from E-
UTRAN to
GERAN
Description
GERAN.
V10.4.0.
Measurement Points
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 1-151
Formula
None
Unit
None
Related Features
L.IRATHO.E2G.ExecSuccO Multi-mode: None

ut GSM: None
UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN
TDLOFD-001020
TDLOFD-001023
GERAN
SRVCC to GERAN


to TD-SCDMA Network
Counters
1526727226 L.IRATHO.E2T Number of BTS3900, L

.PrepAttOut inter-RAT BTS3900 LTE
Handover
Attempts from
E-UTRAN to
TD-SCDMA
network
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to TD-
SCDMA network.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-152, the L.IRATHO.E2T.PrepAttOut counter is incremented
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 1-152
Formula
None
Unit
None
Related Features
L.IRATHO.E2T.PrepAttOut Multi-mode: None

GSM: None
UMTS: None
UTRAN
TDLOFD-001019
SRVCC to UTRAN
TDLOFD-001022
between E-UTRAN and
UTRAN
SRVCC to UTRAN


UTRAN to TD-SCDMA Network
Counters

.ExecAttOut inter-RAT BTS3900 LTE
handover
executions from
E-UTRAN to
TD-SCDMA
network
Description
The counter measures the number of inter-RAT handovers executions from E-UTRAN to TD-
SCDMA network.
V10.4.0.
Measurement Points
As shown at point B in Figure 1-153, 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 1-153
Formula
None
Unit
None
Related Features
L.IRATHO.E2T.ExecAttOut Multi-mode: None

GSM: None
UMTS: None
UTRAN
TDLOFD-001019
SRVCC to UTRAN
TDLOFD-001022
between E-UTRAN and
UTRAN
SRVCC to UTRAN


UTRAN to TD-SCDMA Network
Counters

.ExecSuccOut successful inter- BTS3900 LTE
RAT handovers
from E-
UTRAN to TD-
SCDMA
network
Description
The counter measures the number of successful inter-RAT handovers from E-UTRAN to TD-
SCDMA network.
V10.4.0.
Measurement Points
As shown at point C in Figure 1-154, 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 UE is handed over from the E-UTRAN to a TD-SCDMA network.

Figure 1-154
Formula
None
Unit
None
Related Features
L.IRATHO.E2T.ExecSuccO Multi-mode: None

ut GSM: None
UMTS: None
UTRAN
TDLOFD-001019
SRVCC to UTRAN
TDLOFD-001022
between E-UTRAN and
UTRAN
SRVCC to UTRAN

1.23.13 Number of Inter-RAT Handover Failures for Different

Causes
Counters

G.Prep.FailOut. inter-RAT BTS3900 LTE
MME handover
preparation
failures from E-
UTRAN to
GERAN
because of
faults on the
MME side

NoReply handover
preparation
failures from E-
UTRAN to
GERAN
because of no
responses from
GERAN

PrepFailure handover
preparation
failures from E-
UTRAN to
GERAN due
tobecause
GERAN cells
send handover
preparation
failure
messages



.Prep.FailOut.M inter-RAT BTS3900 LTE
ME handover
preparation
failures from E-
UTRAN to TD-
SCDMA
network
because of
faults on the
MME side

.Prep.FailOut.N inter-RAT BTS3900 LTE
oReply handover
preparation
failures from E-
UTRAN to TD-
SCDMA
network due
tobecause of no
responses from
TD-SCDMA
network

.Prep.FailOut.Pr inter-RAT BTS3900 LTE
epFailure handover
preparation
failures because
TD-SCDMA
network cells
send handover
preparation
failure
messages

W.Prep.FailOut. inter-RAT BTS3900 LTE
MME handover
preparation
failures from E-
UTRAN to
WCDMA
network
because of
faults on the
MME side



PrepFailure handover
preparation
failures from E-
UTRAN to
WCDMA
network
because
WCDMA
network cells
send handover
preparation
failure
messages

NoReply handover
preparation
failures from E-
UTRAN to
WCDMA
network
because of no
responses from
WCDMA
network
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.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-155, 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.

the handover target system each time the eNodeB receives a HANDOVER PREPARATION
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

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


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.
If the target system is WCDMA network, the L.IRATHO.E2W.Prep.FailOut.MME counter is

incremented.
If the target system is GERAN, the L.IRATHO.E2G.Prep.FailOut.MME counter is

incremented.
If the target system is TD-SCDMA network, the L.IRATHO.E2T.Prep.FailOut.MME counter

is incremented.
Figure 1-155

Figure 1-156
Figure 1-157
Formula
None
Unit
None

Related Features
L.IRATHO.E2G.Prep.FailO Multi-mode: None

ut.MME GSM: None
UMTS: None
LTE: LOFD-001034 CS Fallback to GERAN
TDLOFD-001034 CS Fallback to GERAN
GERAN
LOFD-001046
LOFD-001073 GERAN
LOFD-001023 Service based inter-RAT
TDLOFD-001023 handover to GERAN
Service based Inter-RAT
handover to GERAN
Distance based Inter-RAT
handover to GERAN
SRVCC to GERAN
SRVCC to GERAN

ut.NoReply GSM: None
UMTS: None
GERAN
LOFD-001046
LOFD-001073 GERAN
handover to GERAN
handover to GERAN
SRVCC to GERAN
SRVCC to GERAN


ut.PrepFailure GSM: None
UMTS: None
GERAN
LOFD-001046
LOFD-001073 GERAN
handover to GERAN
handover to GERAN
SRVCC to GERAN
SRVCC to GERAN
L.IRATHO.E2T.Prep.FailOu Multi-mode: None

t.MME GSM: None
UMTS: None
LTE: LOFD-001033 CS Fallback to UTRAN
TDLOFD-001033 CS Fallback to UTRAN
UTRAN
LOFD-001043
LOFD-001072 UTRAN
TDLOFD-001022 handover to UTRAN
handover to UTRAN
handover to UTRAN
SRVCC to UTRAN
SRVCC to UTRAN


t.NoReply GSM: None
UMTS: None
UTRAN
LOFD-001043
LOFD-001072 UTRAN
handover to UTRAN
handover to UTRAN
SRVCC to UTRAN
SRVCC to UTRAN

t.PrepFailure GSM: None
UMTS: None
UTRAN
LOFD-001043
LOFD-001072 UTRAN
handover to UTRAN
handover to UTRAN
SRVCC to UTRAN
SRVCC to UTRAN

L.IRATHO.E2W.Prep.FailO Multi-mode: MRFD-101401 UL Unified Video Steering

ut.MME GSM: None
UMTS: None
UTRAN
LOFD-001043
LOFD-001072 UTRAN
handover to UTRAN
handover to UTRAN
SRVCC to UTRAN
SRVCC to UTRAN

ut.PrepFailure GSM: None
UMTS: None
UTRAN
LOFD-001043
LOFD-001072 UTRAN
handover to UTRAN
handover to UTRAN
SRVCC to UTRAN
SRVCC to UTRAN


ut.NoReply GSM: None
UMTS: None
UTRAN
LOFD-001043
LOFD-001072 UTRAN
handover to UTRAN
handover to UTRAN
SRVCC to UTRAN
SRVCC to UTRAN
1.23.14 Number of Inter-RAT Blind Handover Attempts from E-

UTRAN to Another System
Counters
1526728328 L.IRATHO.Blin Number of BTS3900, L

dHO.E2W.Prep inter-RAT blind BTS3900 LTE
AttOut handover
attempts from
E-UTRAN to
WCDMA
network

dHO.E2G.Prep inter-RAT blind BTS3900 LTE
AttOut handover
attempts from
E-UTRAN to
GERAN



dHO.E2T.Prep inter-RAT blind BTS3900 LTE
AttOut handover
attempts from
E-UTRAN to
TD-SCDMA
network
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.
V10.4.0.
Measurement Points
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.
If the target system is GERAN, the L.IRATHO.BlindHO.E2G.PrepAttOut counter is
incremented.
If the target system is TD-SCDMA network, the L.IRATHO.BlindHO.E2T.PrepAttOut
Figure 1-158

Formula
None
Unit
None
Related Features
L.IRATHO.BlindHO.E2W.P Multi-mode: None

repAttOut GSM: None
UMTS: None
UTRAN
between E-UTRAN and
UTRAN
L.IRATHO.BlindHO.E2G.P Multi-mode: None

repAttOut GSM: None
UMTS: None
GERAN
between E-UTRAN and
GERAN
L.IRATHO.BlindHO.E2T.Pr Multi-mode: None

epAttOut GSM: None
UMTS: None
UTRAN
between E-UTRAN and
UTRAN

1.23.15 Number of Blind Handover Executions from E-UTRAN to

Another System
Counters

dHO.E2W.Exec inter-RAT blind BTS3900 LTE
AttOut handovers
executions from
E-UTRAN to
WCDMA
network

dHO.E2G.Exec inter-RAT blind BTS3900 LTE
AttOut handovers
executions from
E-UTRAN to
GERAN

dHO.E2T.Exec inter-RAT blind BTS3900 LTE
AttOut handover
executions from
E-UTRAN to
TD-SCDMA
network
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 source cell.
V10.4.0.
Measurement Points
As shown at point B in Figure 1-159, 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.
If the target system is WCDMA network, the L.IRATHO.BlindHO.E2W.ExecSuccOut
If the target system is GERAN, the L.IRATHO.BlindHO.E2G.ExecSuccOut counter is
incremented.

If the target system is TD-SCDMA network, the L.IRATHO.BlindHO.E2T. ExecAttOut

Figure 1-159
Formula
None
Unit
None
Related Features
L.IRATHO.BlindHO.E2W.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN

L.IRATHO.BlindHO.E2G.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN
TDLOFD-001020
TDLOFD-001023
GERAN
SRVCC to GERAN
L.IRATHO.BlindHO.E2T.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN
1.23.16 Number of successful Inter-RAT Blind Handovers from E-

Counters

dHO.E2W.Exec successful inter- BTS3900 LTE
SuccOut RAT blind
handovers from
E-UTRAN to
WCDMA
network



dHO.E2G.Exec successful inter- BTS3900 LTE
SuccOut RAT blind
handovers from
E-UTRAN to
GERAN

dHO.E2T.Exec successful inter- BTS3900 LTE
SuccOut RAT blind
handovers from
E-UTRAN to
TD-SCDMA
network
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 source cell.
V10.4.0.
Measurement Points
As shown at point C in Figure 1-160, 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.
If the target system is WCDMA network, the L.IRATHO.BlindHO.E2W.ExecSuccOut
counter is increased.
If the target system is GERAN, the L.IRATHO.BlindHO.E2G.ExecSuccOut counter is
increased.
If the target system is TD-SCDMA network, the L.IRATHO.BlindHO.E2T. ExecSuccOut

Figure 1-160
Formula
None
Unit
None
Related Features
L.IRATHO.BlindHO.E2W.E Multi-mode: None

xecSuccOut GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN

L.IRATHO.BlindHO.E2G.E Multi-mode: None

UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN
TDLOFD-001020
TDLOFD-001023
GERAN
SRVCC to GERAN
L.IRATHO.BlindHO.E2T.E Multi-mode: None

UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN
1.23.17 Number of Indicators for CSFB to Another System

Counters
1526728321 L.CSFB.PrepAt Number of BTS3900, L

t CSFB BTS3900 LTE
indicators
received by the
eNodeB



t.Idle CSFB BTS3900 LTE
indicators
received by the
eNodeB for
UEs in idle
mode

t.Emergency CSFB BTS3900 LTE
indicators
received by the
eNodeB for
emergency calls
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 of the following items involve different protocol-defined procedures:
- Number of CSFB executions
- Number of CSFB procedures triggered
- Number of CSFB responses
Therefore, the triggering, response, and execution of a CSFB procedure may be counted in
different measurement periods. In a measurement period, the measurement results of the three
items may not match.
The signaling flows involved in the counter(s) comply with sections 8.3.1 and 8.3.4 in 3GPP
TS 36.413 V10.4.0.
Measurement Points
As shown at point A in Figure 1-161, 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.
As shown at point A in Figure 1-162, the L.CSFB.PrepAtt counter is incremented by 1 each
time the eNodeB receives a UE CONTEXT MODIFICATION REQUEST message
containing the IE "CS Fallback Indicator" from the MME and the eNodeB determines that the
CSFB procedure is for voice services.
As shown at point A in Figure 1-161, the L.CSFB.PrepAtt.Idle counter is incremented by 1
each time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST containing the IE

"CS Fallback Indicator" from the MME and the eNodeB determines that the CSFB procedure
is for voice services.
As shown at point A in Figure 1-161, the L.CSFB.PrepAtt.Emergency counter is incremented

by 1 each time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST message
containing the IE "CS Fallback High Priority" from the MME and the eNodeB determines
that the CSFB procedure is for voice services.
As shown at point A in Figure 1-162, the L.CSFB.PrepAtt.Emergency counter is incremented

by 1 each time the eNodeB receives a UE CONTEXT MODIFICATION REQUEST message
containing the IE "CS Fallback High Priority" from the MME and the eNodeB determines
that the CSFB procedure is for voice services.
Figure 1-161
Figure 1-162
Formula
None

Unit
None
Related Features
L.CSFB.PrepAtt Multi-mode: None

GSM: None
UMTS: None
LOFD-001034 CS Fallback to GERAN
LOFD-001035 CS Fallback to CDMA2000
TDLOFD-001035 1xRTT
1xRTT
L.CSFB.PrepAtt.Idle Multi-mode: None

GSM: None
UMTS: None
TDLOFD-001035 1xRTT
1xRTT
L.CSFB.PrepAtt.Emergency Multi-mode: None

GSM: None
UMTS: None
TDLOFD-001035 1xRTT
1xRTT

1.23.18 Number of CSFB Responses to MMEs
Counters
1526728322 L.CSFB.PrepSu Number of BTS3900, L

cc successful BTS3900 LTE
CSFB
responses from
the eNodeB

cc.Idle successful BTS3900 LTE
CSFB
responses from
the eNodeB for
UEs in idle
mode

cc.Emergency responses sent BTS3900 LTE
from the
eNodeB for
CSFB triggered
for emergency
calls
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.
TS 36.413 V10.4.0.

Measurement Points
As shown at point C in Figure 1-163, 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.
As shown at point C in Figure 1-164, the L.CSFB.PrepSucc counter is incremented by 1 each
time the eNodeB successfully sends a UE CONTEXT MODIFICATION RESPONSE
message to the MME and the eNodeB determines that the CSFB procedure is for voice
services.
As shown at point C in Figure 1-163, the L.CSFB.PrepSucc.Idle 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.
As shown at point C in Figure 1-163, the L.CSFB.PrepSucc.Emergency counter is
incremented by 1 each time the eNodeB successfully sends an INITIAL CONTEXT SETUP
RESPONE 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.
As shown at point C in Figure 1-164, the L.CSFB.PrepSucc.Emergency counter is
incremented by 1 each time the eNodeB successfully sends a UE CONTEXT
MODIFICATION RESPONSE message to the MME for an emergency call and the eNodeB
determines that the CSFB procedure is for voice services.
Figure 1-163

Figure 1-164
Formula
None
Unit
None
Related Features
L.CSFB.PrepSucc Multi-mode: None

GSM: None
UMTS: None
TDLOFD-001035 1xRTT
1xRTT

L.CSFB.PrepSucc.Idle Multi-mode: None

GSM: None
UMTS: None
TDLOFD-001035 1xRTT
1xRTT
L.CSFB.PrepSucc.Emergen Multi-mode: None

cy GSM: None
UMTS: None
TDLOFD-001035 1xRTT
1xRTT
1.23.19 Number of Procedures for CSFB to Another System

Counters
1526728323 L.CSFB.E2W Number of BTS3900, L

procedures for BTS3900 LTE
CSFB to
WCDMA
network
1526728324 L.CSFB.E2G Number of BTS3900, L

CSFB to
GERAN


1526728388 L.CSFB.E2W.I Number of BTS3900, L

dle procedures for BTS3900 LTE
CSFB to
WCDMA
network for
UEs in idle
mode
1526728497 L.RRCRedirecti Number of BTS3900, L

on.E2W.CSFB CSFB-based BTS3900 LTE
redirections
from E-
UTRANs to
WCDMA
network

on.E2G.CSFB CSFB-based BTS3900 LTE
redirections
from E-
UTRAN to
GERAN

on.E2C.CSFB CSFB-based BTS3900 LTE
redirections
from E-
UTRAN to
CDMA2000
network

on.E2T.CSFB CSFB-based BTS3900 LTE
redirections
from E-
UTRAN to TD-
SCDMA
network

C.CSFB.PrepAt CSFB-based BTS3900 LTE
tOut inter-RAT
handover
preparation
attempts from
E-UTRAN to
CDMA2000
network



C.CSFB.ExecA CSFB-based BTS3900 LTE
ttOut handover
execution
attempts from
E-UTRAN to
CDMA2000
network

C.CSFB.ExecS successful BTS3900 LTE
uccOut CSFB-based
inter-RAT
handover
executions from
E-UTRAN to
CDMA2000
network

W.CSFB.PrepA CSFB-based BTS3900 LTE
ttOut inter-RAT
handover
preparation
attempts from
E-UTRAN to
WCDMA
network

W.CSFB.ExecA CSFB-based BTS3900 LTE
ttOut inter-RAT
handover
execution
attempts from
E-UTRAN to
WCDMA
network

W.CSFB.ExecS successful BTS3900 LTE
uccOut CSFB-based
inter-RAT
handover
executions from
E-UTRAN to
WCDMA
network



G.CSFB.PrepAt CSFB-based BTS3900 LTE
tOut inter-RAT
handover
preparation
attempts from
E-UTRAN to
GERAN

G.CSFB.ExecA CSFB-based BTS3900 LTE
ttOut inter-RAT
handover
execution
attempts from
E-UTRAN to
GERAN

G.CSFB.ExecS successful BTS3900 LTE
uccOut CSFB-based
inter-RAT
handover
executions from
E-UTRAN to
GERAN

.CSFB.PrepAtt CSFB-based BTS3900 LTE
Out inter-RAT
handover
preparation
attempts from
E-UTRAN to
TD-SCDMA
network

.CSFB.ExecAtt CSFB-based BTS3900 LTE
Out inter-RAT
handover
execution
attempts from
E-UTRAN to
TD-SCDMA
network



.CSFB.ExecSuc successful BTS3900 LTE
cOut CSFB-based
inter-RAT
handover
executions from
E-UTRAN to
TD-SCDMA
network
1526728705 L.FlashCSFB.E Number of BTS3900, L

2W procedures for BTS3900 LTE
flash CSFB to
WCDMA
network
1526728706 L.FlashCSFB.E Number of BTS3900, L

2G procedures for BTS3900 LTE
flash CSFB to
GERAN
1526728709 L.CSFB.E2W.E Number of BTS3900, L

mergency procedures for BTS3900 LTE
CSFB to
WCDMA
network
triggered for
emergency calls
1526728710 L.CSFB.E2G.E Number of BTS3900, L

CSFB to
GERAN
triggered for
emergency calls
1526728749 L.CSFB.E2T Number of BTS3900, L

SRVCC to TD-
SCDMA
network
1526728750 L.CSFB.E2T.Id Number of BTS3900, L

le procedures for BTS3900 LTE
SRVCC to TD-
SCDMA
network for
UEs in idle
mode


1526729054 L.CSFB.E2C Number of BTS3900, L

CSFB to
CDMA2000
1xRTT network
1526729055 L.CSFB.E2C.E Number of BTS3900, L

CSFB to
CDMA2000
1xRTT network
triggered for
emergency calls
1526729260 L.CSFB.E2G.Id Number of BTS3900, L

le procedures for BTS3900 LTE
CSFB to
GERAN
network for
UEs in idle
mode
1526729505 L.CCOwithNA Number of BTS3900, L

CC.E2G.CSFB. CSFB-based BTS3900 LTE
ExecAttOut CCO with
NACC
executions from
E-UTRAN to
GERAN
1526729506 L.CCOwithNA Number of BTS3900, L

CC.E2G.CSFB. successful BTS3900 LTE
ExecSuccOut CSFB-based
CCOs with
NACC from E-
UTRAN to
GERAN
1526729507 L.CCOwithout Number of BTS3900, L

NACC.E2G.CS CSFB-based BTS3900 LTE
FB.ExecAttOut CCO without
NACC
executions from
E-UTRAN to
GERAN


1526729508 L.CCOwithout Number of BTS3900, L

NACC.E2G.CS successful BTS3900 LTE
FB.ExecSuccO CSFB-based
ut CCOs without
NACC from E-
UTRAN to
GERAN

W.CSFB.PrepA CSFB-based BTS3900 LTE
ttOut.Emergenc handover
y preparation
attempts to
WCDMA
network
triggered for
emergency calls

W.CSFB.ExecA CSFB-based BTS3900 LTE
y execution
attempts to
WCDMA
network
triggered for
emergency calls

W.CSFB.ExecS successful BTS3900 LTE
uccOut.Emerge CSFB-based
ncy handover
executions to
WCDMA
network
triggered for
emergency calls

G.CSFB.PrepAt CSFB-based BTS3900 LTE
tOut.Emergenc handover
y preparation
attempts to
GERAN
triggered for
emergency calls



G.CSFB.ExecA CSFB-based BTS3900 LTE
y execution
attempts to
GERAN
triggered for
emergency calls

G.CSFB.ExecS successful BTS3900 LTE
uccOut.Emerge CSFB-based
ncy handover
executions to
GERAN
triggered for
emergency calls

on.E2W.CSFB. CSFB-based BTS3900 LTE
TimeOut blind
redirections
from E-
UTRAN to
WCDMA
network caused
by CSFB
protection timer
expiration

on.E2G.CSFB. CSFB-based BTS3900 LTE
TimeOut blind
redirections
from E-
UTRAN to
GERAN caused
by CSFB
protection timer
expiration
1526729544 L.CSFB.E2C.D Number of BTS3900, L

ualRx procedures for BTS3900 LTE
dual-receiver
CSFB to
CDMA 1xRTT
network

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, redirection and handover. The CSFB to GERAN mechanism includes blind
redirection, blind handover, blind CCO, redirection, handover, and CCO. The CSFB to TD-
SCDMA network 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 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.
The signaling flows involved in the counter(s) comply with sections 5.3.8, and 5.4.3 in 3GPP
TS 36.331 V10.4.0.
Disuse Statement:
The L.CCOwithNACC.E2G.CSFB.ExecSuccOut counter will be deleted in later versions. In
this version, the counter value is normally reported (or the value 0 is reported), and it is
recommended that this counter not be used.
The L.CCOwithoutNACC.E2G.CSFB.ExecSuccOut counter will be deleted in later versions.
In this version, the counter value is normally reported (or the value 0 is reported), and it is
recommended that this counter not be used.
Measurement Points
As shown at point A in Figure 1-165, 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 1-165, 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 C in Figure 1-165, the L.IRATHO.E2W.CSFB.ExecSuccOut counter is
incremented by 1 each time the eNodeB receives a UE CONTEXT RELEASE COMMAND
message from the MME after the UE performs an inter-RAT handover for CSFB to WCDMA
network.
As shown at point A in Figure 1-166, the L.CSFB.E2W and L.RRCRedirection.E2W.CSFB
counters are incremented by 1 each time the eNodeB sends an RRC Connection Release

message to the UE and informs the UE to perform a CSFB procedure to WCDMA network.
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 A in Figure 1-165, the L.IRATHO.E2G.CSFB.PrepAttOut counter is

CSFB to GERAN or the eNodeB decides to perform an inter-RAT handover for CSFB to
GERAN after the eNodeB receives a measurement report from the UE.
As shown at point B in Figure 1-165, the L.CSFB.E2G and

L.IRATHO.E2G.CSFB.ExecAttOut counters are incremented by 1 each time the eNodeB
sends a Mobility From EUTRA Command message to the UE and informs the UE to perform
a CSFB procedure to GERAN.
As shown at point C in Figure 1-165, the L.IRATHO.E2G.CSFB.ExecSuccOut counter is

message from the MME after the UE performs an inter-RAT handover for CSFB to GERAN.
As shown at point A in Figure 1-166, the L.CSFB.E2G and L.RRCRedirection.E2G.CSFB

counters are incremented by 1 each time the eNodeB sends an RRC Connection Release
massage to the UE and informs the UE to perform a CSFB procedure to GERAN.
As shown at point A in Figure 1-167, the L.IRATHO.E2C.CSFB.PrepAttOut counter is

incremented by 1 each time the eNodeB decides to perform an inter-RAT handover for CSFB
to CDMA2000 network after the eNodeB receives a measurement report from the UE.
As shown at point B in Figure 1-167, the L.IRATHO.E2C.CSFB.ExecAttOut counter is

incremented by 1 each time the eNodeB sends a Mobility From EUTRA Command message
to the UE and informs the UE to perform a CSFB procedure to CDMA2000 network.
As shown at point C in Figure 1-167, the L.IRATHO.E2C.CSFB.ExecSuccOut counter is

incremented by 1 each time the eNodeB sends a UE CONTEXT RELEASE REQUEST
message to the MME after the UE performs an inter-RAT handover for CSFB to CDMA2000
network.
As shown at point A in Figure 1-166, the L.RRCRedirection.E2C.CSFB counter is

incremented by 1 each time the eNodeB sends an RRC Connection Release message to the
UE and informs the UE to perform a CSFB procedure to CDMA2000 network.
As shown at point A in Figure 1-165, the L.IRATHO.E2T.CSFB.PrepAttOut counter is

CSFB to TD-SCDMA network or the eNodeB decides to perform an inter-RAT handover for
CSFB to TD-SCDMA network after the eNodeB receives a measurement report from the UE.
As shown at point B in Figure 1-165, the L.IRATHO.E2T.CSFB.ExecAttOut counter is

to the UE and informs the UE to perform a CSFB procedure to TD-SCDMA network.
As shown at point C in Figure 1-165, the L.IRATHO.E2T.CSFB.ExecSuccOut counter is

message from the MME after the UE performs an inter-RAT handover for CSFB to TD-
SCDMA network.
As shown at point A in Figure 1-166, the L.RRCRedirection.E2T.CSFB counter is

UE and informs the UE to perform a CSFB procedure to TD-SCDMA network.

As shown at point A in Figure 1-166, the L.FlashCSFB.E2W counter is incremented by 1

each time the eNodeB sends an RRC Connection Release message (containing the
information of redirection and system information of the target cell) to the UE and informs the
UE to perform a flash CSFB procedure to WCDMA network.
As shown at point A in Figure 1-166, the L.FlashCSFB.E2G counter is incremented by 1
each time the eNodeB sends an RRC Connection Release message (containing the
information of redirection and system information of the target cell) to the UE and informs the
UE to perform a flash CSFB procedure to GERAN.
As shown at point B in Figure 1-165, the L.CSFB.E2W.Emergency counter is incremented by
1 each time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST or UE
CONTEXT MODIFICATION REQUEST message containing the IE "CS Fallback High
Priority" and the eNodeB performs a CSFB procedure to WCDMA network triggered for an
emergency call after the eNodeB sends a Mobility From EUTRA Command message to the
UE.
As shown at point A in Figure 1-166, the L.CSFB.E2W.Emergency counter is incremented by
Priority" and the eNodeB performs a CSFB procedure to WCDMA network triggered for an
emergency call after the eNodeB sends an RRC Connection Release message to the UE.
As shown at point B in Figure 1-165, the L.CSFB.E2G.Emergency counter is incremented by
Priority" and the eNodeB performs a CSFB procedure to GERAN triggered for an emergency
call after the eNodeB sends a Mobility From EUTRA Command message to the UE.
As shown at point A in Figure 1-166, the L.CSFB.E2G.Emergency counter is incremented by
Priority" and the eNodeB performs a CSFB procedure to GERAN triggered for an emergency
call after the eNodeB sends an RRC Connection Release message to the UE.
As shown at point B in Figure 1-165, 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 1-166, 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 1-165 or point A in Figure 1-166, 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.
As shown at point B in Figure 1-167, the L.CSFB.E2C counter is incremented by 1 each time
the eNodeB performs a CSFB procedure to CDMA2000 1xRTT network after sending a
Mobility From EUTRA Command message to the UE.
As shown at point A in Figure 1-166, the L.CSFB.E2C counter is incremented by 1 each time
the eNodeB performs a CSFB procedure to CDMA2000 1xRTT network after sending an
RRC Connection Release message to the UE.
As shown at point A in Figure 1-168, the L.CSFB.E2C counter is incremented by 1 each time
the eNodeB performs a CSFB procedure to CDMA2000 1xRTT network after sending an
RRC Connection Release message to the UE.

As shown at point B in Figure 1-167, the L.CSFB.E2C.Emergency counter is incremented by

Priority" and the eNodeB performs a CSFB procedure to CDMA2000 1xRTT network
triggered for an emergency call after the eNodeB sends a Mobility From EUTRA Command
message to the UE.
As shown at point A in Figure 1-166, the L.CSFB.E2C.Emergency counter is incremented by
triggered for an emergency call after the eNodeB sends an RRC Connection Release message
to the UE.
As shown at point A in Figure 1-168, the L.CSFB.E2C.Emergency counter is incremented by
triggered for an emergency call after the eNodeB sends an RRC Connection Release message
to the UE.
As shown at point B in Figure 1-165, the L.CSFB.E2G counter is incremented by 1 each time
the eNodeB performs a CSFB procedure to the GERAN after the eNodeB sends a Mobility
From EUTRA Command message to the UE,the initial state of the UE must be saved before
the measurement. The L.CSFB.E2G.Idle counter is incremented by 1 each time the UE in idle
mode performs a CSFB procedure to GERAN.
As shown at point A in Figure 1-166, the L.CSFB.E2G counter is incremented by 1 each time
the eNodeB performs a CSFB procedure to the GERAN after the eNodeB sends an RRC
Connection Release message to the UE.The L.CSFB.E2G.Idle counter is incremented by 1
each time the UE in idle mode performs a CSFB procedure to GERAN.
As shown at point B in Figure 1-165, during a CSFB-based CCO with NACC from the E-
UTRAN to a GERAN, the L.CCOwithNACC.E2G.CSFB.ExecAttOut counter is incremented
by 1 each time the eNodeB sends a Mobility From EUTRA Command message to the UE.
As shown at point C in Figure 1-165, during a CSFB-based CCO with NACC from the E-
UTRAN to a GERAN, the L.CCOwithNACC.E2G.CSFB.ExecSuccOut counter is
message from the MME after the UE is handed over from the E-UTRAN to the GERAN.
As shown at point B in Figure 1-165, during a CSFB-based CCO without NACC from the E-
UTRAN to a GERAN, the L.CCOwithoutNACC.E2G.CSFB.ExecAttOut counter is
to the UE.
As shown at point C in Figure 1-165, during a CSFB-based CCO without NACC from the E-
UTRAN to a GERAN, the L.CCOwithoutNACC.E2G.CSFB.ExecSuccOut counter is
message from the MME after the UE is handed over from the E-UTRAN to the GERAN.
As shown at point A in Figure 1-165, the L.IRATHO.E2W.CSFB.PrepAttOut.Emergency
counter is incremented by 1 each time the following conditions are met:
(1) The eNodeB decides to perform a CSFB-based blind handover from the E-UTRAN to a
WCDMA network or the eNodeB decides to perform a CSFB-based handover from the E-
UTRAN to a WCDMA network after receiving a measurement report from the UE.

(2) The INITIAL CONTEXT SETUP REQUEST or UE CONTEXT MODIFICATION

REQUEST message the eNodeB received contains the IE "CS Fallback High Priority".
As shown at point B in Figure 1-165, during an inter-RAT handover from the E-UTRAN to a
WCDMA network,the L.IRATHO.E2W.CSFB.ExecAttOut.Emergency counter is
to the UE and the INITIAL CONTEXT SETUP REQUEST or UE CONTEXT
MODIFICATION REQUEST message the eNodeB received contains the IE "CS Fallback
High Priority".
As shown at point C in Figure 1-165, during an inter-RAT handover from the E-UTRAN to a
WCDMA network, the L.IRATHO.E2W.CSFB.ExecSuccOut.Emergency counter is
incremented by 1 each time the eNodeB receive a UE CONTEXT RELEASE COMMAND
message from the MME and the INITIAL CONTEXT SETUP REQUEST or UE CONTEXT
MODIFICATION REQUEST message the eNodeB received contains the IE "CS Fallback
High Priority".
As shown at point A in Figure 1-165, the L.IRATHO.E2G.CSFB.PrepAttOut.Emergency
counter is incremented by 1 each time the following conditions are met:
(1) The eNodeB decides to perform a CSFB-based blind handover from the E-UTRAN to a
GERAN or decides to perform a CSFB-based handover from the E-UTRAN to a GERAN
after receiving a measurement report from the UE.
(2) The INITIAL CONTEXT SETUP REQUEST or UE CONTEXT MODIFICATION
GERAN,the L.IRATHO.E2G.CSFB.ExecAttOut.Emergency counter is incremented by 1 each
time the eNodeB sends a Mobility From EUTRA Command message to the UE and the
INITIAL CONTEXT SETUP REQUEST or UE CONTEXT MODIFICATION REQUEST
message the eNodeB received contains the IE "CS Fallback High Priority".
GERAN, the L.IRATHO.E2G.CSFB.ExecSuccOut.Emergency counter is incremented by 1
each time the eNodeB receive a UE CONTEXT RELEASE COMMAND message from the
MME and the INITIAL CONTEXT SETUP REQUEST or UE CONTEXT MODIFICATION
As shown at point A in Figure 1-166, the L.RRCRedirection.E2W.CSFB.TimeOut counter is
UE when the eNodeB decides to perform a blind redirection from the E-UTRAN to a
WCDMA network because the CSFB protection timer expires.
As shown at point A in Figure 1-166, the L.RRCRedirection.E2G.CSFB.TimeOut counter is
UE when the eNodeB decides to perform a blind redirection from the E-UTRAN to a GERAN
because the CSFB protection timer expires.
As shown at point A in Figure 1-168, the L.CSFB.E2C.DualRx counter is incremented by 1
each time the eNodeB performs a dual-receiver CSFB procedure to the CDMA2000 1xRTT
network after sending an RRC Connection Release message to the UE.
As shown at point B in Figure 1-169, the L.CSFB.E2W counter is incremented by 1 each
time the eNodeB performs a CSFB procedure to WCDMA network after sending a Mobility
From EUTRA Command message to a UE without a bearer of QCI 1. In this case, if the
CSFB procedure is initiated by a UE in idle mode (which is determined by the eNodeB), the
L.CSFB.E2W.Idle counter is incremented by 1.

As shown at point B in Figure 1-169, the L.CSFB.E2W.Emergency counter is incremented by

Priority" after sending a Mobility From EUTRA Command message to a UE and then the
eNodeB performs a CSFB procedure triggered for an emergency call to WCDMA network.
Figure 1-165

Figure 1-166
Figure 1-167

Figure 1-168
Figure 1-169

Formula
None
Unit
None
Related Features
L.CSFB.E2W Multi-mode: None

GSM: None
UMTS: None
LOFD-070202 Ultra-Flash CSFB to
TDLOFD-081223 UTRAN
Ultra-Flash CSFB to
UTRAN
L.CSFB.E2G Multi-mode: None

GSM: None
UMTS: None
L.CSFB.E2W.Idle Multi-mode: None

GSM: None
UMTS: None
TDLOFD-081223 UTRAN
Ultra-Flash CSFB to
UTRAN
L.RRCRedirection.E2W.CS Multi-mode: None

FB GSM: None
UMTS: None

L.RRCRedirection.E2G.CS Multi-mode: None

FB GSM: None
UMTS: None
L.RRCRedirection.E2C.CS Multi-mode: None

FB GSM: None
UMTS: None
LTE: LOFD-001035 CS Fallback to CDMA2000
TDLOFD-001035 1xRTT
1xRTT
L.RRCRedirection.E2T.CSF Multi-mode: None

B GSM: None
UMTS: None
L.IRATHO.E2C.CSFB.Prep Multi-mode: None

AttOut GSM: None
UMTS: None
TDLOFD-001035 1xRTT
1xRTT
L.IRATHO.E2C.CSFB.Exec Multi-mode: None

AttOut GSM: None
UMTS: None
TDLOFD-001035 1xRTT
1xRTT
L.IRATHO.E2C.CSFB.Exec Multi-mode: None

SuccOut GSM: None
UMTS: None
TDLOFD-001035 1xRTT
1xRTT

L.IRATHO.E2W.CSFB.Prep Multi-mode: None

AttOut GSM: None
UMTS: None
L.IRATHO.E2W.CSFB.Exe Multi-mode: None

cAttOut GSM: None
UMTS: None

cSuccOut GSM: None
UMTS: None
L.IRATHO.E2G.CSFB.Prep Multi-mode: None

AttOut GSM: None
UMTS: None
L.IRATHO.E2G.CSFB.Exec Multi-mode: None

AttOut GSM: None
UMTS: None

SuccOut GSM: None
UMTS: None
L.IRATHO.E2T.CSFB.Prep Multi-mode: None

AttOut GSM: None
UMTS: None

L.IRATHO.E2T.CSFB.Exec Multi-mode: None

AttOut GSM: None
UMTS: None
L.IRATHO.E2T.CSFB.Exec Multi-mode: None

SuccOut GSM: None
UMTS: None
L.FlashCSFB.E2W Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001052 Flash CS Fallback to
TDLOFD-001052 UTRAN
Flash CS Fallback to
UTRAN
L.FlashCSFB.E2G Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001053 Flash CS Fallback to
TDLOFD-001053 GERAN
Flash CS Fallback to
GERAN
L.CSFB.E2W.Emergency Multi-mode: None

GSM: None
UMTS: None
TDLOFD-081223 UTRAN
Ultra-Flash CSFB to
UTRAN
L.CSFB.E2G.Emergency Multi-mode: None

GSM: None
UMTS: None

L.CSFB.E2T Multi-mode: None

GSM: None
UMTS: None
L.CSFB.E2T.Idle Multi-mode: None

GSM: None
UMTS: None
L.CSFB.E2C Multi-mode: None

GSM: None
UMTS: None
TDLOFD-001035 1xRTT
1xRTT
TDLOFD-001090
Enhanced CS Fallback to
CDMA2000 1xRTT
CDMA2000 1xRTT
L.CSFB.E2C.Emergency Multi-mode: None

GSM: None
UMTS: None
TDLOFD-001035 1xRTT
1xRTT
TDLOFD-001090
CDMA2000 1xRTT
CDMA2000 1xRTT
L.CSFB.E2G.Idle Multi-mode: None

GSM: None
UMTS: None

L.CCOwithNACC.E2G.CS Multi-mode: None

FB.ExecAttOut GSM: None
UMTS: None
L.CCOwithNACC.E2G.CS Multi-mode: None

FB.ExecSuccOut GSM: None
UMTS: None
L.CCOwithoutNACC.E2G. Multi-mode: None

CSFB.ExecAttOut GSM: None
UMTS: None
L.CCOwithoutNACC.E2G. Multi-mode: None

CSFB.ExecSuccOut GSM: None
UMTS: None

AttOut.Emergency GSM: None
UMTS: None

cAttOut.Emergency GSM: None
UMTS: None

cSuccOut.Emergency GSM: None
UMTS: None

L.IRATHO.E2G.CSFB.Prep Multi-mode: None

UMTS: None

UMTS: None

SuccOut.Emergency GSM: None
UMTS: None
L.RRCRedirection.E2W.CS Multi-mode: None

FB.TimeOut GSM: None
UMTS: None
L.RRCRedirection.E2G.CS Multi-mode: None

FB.TimeOut GSM: None
UMTS: None
L.CSFB.E2C.DualRx Multi-mode: None

GSM: None
UMTS: None
LOFD-001090 1xRTT
TDLOFD-001035 Enhanced CS Fallback to
CDMA2000 1xRTT
TDLOFD-001090
1xRTT
CDMA2000 1xRTT

1.23.20 Number of Inter-RAT Redirection Preparations from E-

Counters

on.E2W.PrepAt redirection BTS3900 LTE
t preparations
from E-
UTRAN to
WCDMA
network

on.E2G.PrepAtt redirection BTS3900 LTE
preparations
from E-
UTRAN to
GERAN

on.E2T.PrepAtt redirection BTS3900 LTE
preparations to
TD-SCDMA
network

on.E21xRTT.Pr redirection BTS3900 LTE
epAtt preparations
from E-
UTRAN to
CDMA2000
1xRTT network

on.E2HRPD.Pr redirection BTS3900 LTE
epAtt preparations
from E-
UTRAN to
CDMA2000
HRPD network



on.E2HRPD.Pr redirection BTS3900 LTE
epAtt.PreRegN preparations
otCompleted from E-
UTRAN to
CDMA2000
HRPD network
triggered
because the UE
does not finish
preregistration
with a
CDMA2000
HRPD network
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.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-170, 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 1-170, the L.RRCRedirection.E2G.PrepAtt counter is
UTRAN to GERAN.
as shown at point A in Figure 1-170, the L.RRCRedirection.E2T.PrepAtt counter is
UTRAN to TD-SCDMA network.
As shown at point A in Figure 1-170, the L.RRCRedirection.E21xRTT.PrepAtt counter is
incremented by 1 each time the eNodeB decides to trigger an inter-RAT redirection from the
E-UTRAN to a CDMA2000 1xRTT network.
As shown at point A in Figure 1-170, the L.RRCRedirection.E2HRPD.PrepAtt counter is
incremented by 1 each time the eNodeB decides to trigger an inter-RAT redirection from the
E-UTRAN to a CDMA2000 HRPD network.
As shown at point A in Figure 1-170, the
L.RRCRedirection.E2HRPD.PrepAtt.PreRegNotCompleted counter is incremented by 1 each

time a redirection to a CDMA2000 HRPD network is triggered because the preregistration

status for the UE with the CDMA2000 HRPD network is false when the eNodeB receives a
measurement report from the UE and decides to perform an inter-RAT handover from the E-
UTRAN to the CDMA2000 HRPD network.
Figure 1-170
Formula
None
Unit
None
Related Features
L.RRCRedirection.E2W.Pre Multi-mode: None

pAtt GSM: None
UMTS: None
UTRAN
TDLOFD-001019
TDLOFD-001033
between E-UTRAN and
UTRAN

L.RRCRedirection.E2G.Pre Multi-mode: None

pAtt GSM: None
UMTS: None
GERAN
TDLOFD-001020
TDLOFD-001034
between E-UTRAN and
GERAN
L.RRCRedirection.E2T.Prep Multi-mode: None

Att GSM: None
UMTS: None
UTRAN
TDLOFD-001019
TDLOFD-001033
between E-UTRAN and
UTRAN
L.RRCRedirection.E21xRT Multi-mode: None

T.PrepAtt GSM: None
UMTS: None
CDMA2000
TDLOFD-001021
TDLOFD-001035 1xRTT
between E-UTRAN and
CDMA2000
1xRTT

L.RRCRedirection.E2HRPD Multi-mode: None

.PrepAtt GSM: None
UMTS: None
CDMA2000
TDLOFD-001021
TDLOFD-001035 1xRTT
between E-UTRAN and
CDMA2000
1xRTT

.PrepAtt.PreRegNotComple- GSM: None
ted
UMTS: None
CDMA2000
TDLOFD-001021
TDLOFD-001035 1xRTT
between E-UTRAN and
CDMA2000
1xRTT
1.23.21 Number of Inter-RAT Redirections from E-UTRAN to

Another System
Counters

on.E2W redirections BTS3900 LTE
from E-
UTRAN to
WCDMA
network



on.E2G redirections BTS3900 LTE
from E-
UTRAN to
GERAN

on.E2T redirections to BTS3900 LTE
TD-SCDMA
network

on.E21xRTT redirections BTS3900 LTE
from E-
UTRAN to
CDMA2000
1xRTT network

on.E2HRPD redirections BTS3900 LTE
from E-
UTRAN to
CDMA2000
HRPD network
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.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-171, 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.
As shown at point A in Figure 1-171, the L.RRCRedirection.E2G 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 GERAN.
As shown at point A in Figure 1-171, the L.RRCRedirection.E2T 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 TD-SCDMA network.

As shown at point A in Figure 1-171, the L.RRCRedirection.E21xRTT counter is

UE when the eNodeB triggers a redirection to a CDMA2000 1xRTT network.
As shown at point A in Figure 1-171, the L.RRCRedirection.E2HRPD 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 a CDMA2000 HRPD network.
Figure 1-171
Formula
None
Unit
None
Related Features
L.RRCRedirection.E2W Multi-mode: None

GSM: None
UMTS: None
UTRAN
TDLOFD-001019
TDLOFD-001033
between E-UTRAN and
UTRAN

L.RRCRedirection.E2G Multi-mode: None

GSM: None
UMTS: None
GERAN
TDLOFD-001020
TDLOFD-001034
between E-UTRAN and
GERAN
L.RRCRedirection.E2T Multi-mode: None

GSM: None
UMTS: None
UTRAN
TDLOFD-001019
TDLOFD-001033
between E-UTRAN and
UTRAN
L.RRCRedirection.E21xRT Multi-mode: None

T GSM: None
UMTS: None
CDMA2000
TDLOFD-001021
TDLOFD-001035 1xRTT
between E-UTRAN and
CDMA2000
1xRTT


GSM: None
UMTS: None
CDMA2000
TDLOFD-001021
TDLOFD-001035 1xRTT
between E-UTRAN and
CDMA2000
1xRTT

to WCDMA network for SRVCC
Counters
1526728400 L.IRATHO.SR Number of BTS3900, L

VCC.E2W.Prep inter-RAT BTS3900 LTE
AttOut handover
attempts from
E-UTRAN to
WCDMA
network for
SRVCC
Description
WCDMA network for SRVCC in a cell.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-172, the L.IRATHO.SRVCC.E2W.PrepAttOut counter is
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 1-172
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2W.Pr Multi-mode: None

epAttOut GSM: None
UMTS: None
LTE: LOFD-001022 SRVCC to UTRAN
TDLOFD-001022 SRVCC to UTRAN

1.23.23 Number of Inter-RAT Handover Executions from E-

UTRAN to WCDMA network for SRVCC
Counters

VCC.E2W.Exec inter-RAT BTS3900 LTE
AttOut handover
executions from
E-UTRAN to
WCDMA
network for
SRVCC
Description
The counter measures the number of inter-RAT handover executions from E-UTRAN to
V10.4.0.
Measurement Points
WCDMA network for SRVCC the L.IRATHO.SRVCC.E2W.ExecAttOut counter is
to the UE.

Figure 1-173
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2W.Ex Multi-mode: None

ecAttOut GSM: None
UMTS: None


UTRAN to WCDMA Network for SRVCC
Counters

VCC.E2W.Exec successful inter- BTS3900 LTE
SuccOut RAT handovers
from E-
UTRAN to
WCDMA
network for
SRVCC
Description
V10.4.0.
Measurement Points
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 1-174
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2W.Ex Multi-mode: None

ecSuccOut GSM: None
UMTS: None


to GERAN for SRVCC
Counters

VCC.E2G.Prep inter-RAT BTS3900 LTE
AttOut handover
attempts from
E-UTRAN to
GERAN for
SRVCC
Description
GERAN for SRVCC in a cell.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-175, the L.IRATHO.SRVCC.E2G.PrepAttOut counter is
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 1-175
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2G.Pr Multi-mode: None

epAttOut GSM: None
UMTS: None
LTE: LOFD-001023 SRVCC to GERAN
TDLOFD-001023 SRVCC to GERAN


UTRAN to GERAN for SRVCC
Counters

VCC.E2G.Exec inter-RAT BTS3900 LTE
AttOut handover
executions from
E-UTRAN to
GERAN for
SRVCC
Description
V10.4.0.
Measurement Points
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 1-176
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2G.Ex Multi-mode: None

ecAttOut GSM: None
UMTS: None


UTRAN to GERAN for SRVCC
Counters

VCC.E2G.Exec successful inter- BTS3900 LTE
from E-
UTRAN to
GERAN for
SRVCC
Description
V10.4.0.
Measurement Points
GERAN for SRVCC the L.IRATHO.SRVCC.E2G.ExecSuccOut counter is incremented by 1
MME after the UE is handed over from the E-UTRAN to a GERAN.

Figure 1-177
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2G.Ex Multi-mode: None

ecSuccOut GSM: None
UMTS: None


to TD-SCDMA Network for SRVCC
Counters

VCC.E2T.Prep inter-RAT BTS3900 LTE
AttOut handover
attempts from
E-UTRAN to
TD-SCDMA
network for
SRVCC
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to TD-
SCDMA network for SRVCC in a cell.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-178, 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 1-178
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2T.Pre Multi-mode: None

pAttOut GSM: None
UMTS: None


UTRAN to TD-SCDMA Network for SRVCC
Counters

VCC.E2T.Exec inter-RAT BTS3900 LTE
AttOut handover
executions from
E-UTRAN to
TD-SCDMA
for SRVCC
Description
The counter measures the number of inter-RAT handover executions from E-UTRAN to TD-
V10.4.0.
Measurement Points
As shown at point B in Figure 1-179, during an inter-RAT handover from E-UTRAN to TD-
SCDMA network for SRVCC the L.IRATHO.SRVCC.E2T.ExecAttOut counter is
to the UE.

Figure 1-179
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2T.Ex Multi-mode: None

ecAttOut GSM: None
UMTS: None


UTRAN to TD-SCDMA network for SRVCC
Counters

VCC.E2T.Exec successful inter- BTS3900 LTE
from E-
UTRAN to TD-
SCDMA
network for
SRVCC
Description
The counter measures the number of successful inter-RAT handovers from E-UTRAN to TD-
V10.4.0.
Measurement Points
As shown at point C in Figure 1-180, during an inter-RAT handover from E-UTRAN to TD-
SCDMA network for SRVCC the L.IRATHO.SRVCC.E2T.ExecSuccOut counter is
message from the MME after the UE is handed over from the E-UTRAN to a TD-SCDMA
network.

Figure 1-180
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2T.Ex Multi-mode: None

ecSuccOut GSM: None
UMTS: None

1.23.31 Number of LCS-triggered CS Fallback Indicators Received

by the eNodeB
Counters
1526728409 L.CSFB.LCS.Pr Number of BTS3900, L

epAtt LCS-triggered BTS3900 LTE
CS fallback
indicators
received by the
eNodeB
Description
The counter measures the number of LCS-triggered CS fallback indicators received by the
eNodeB in a cell.
TS 36.413 V10.4.0.
Measurement Points
As shown at point A in Figure 1-181, the L.CSFB.LCS.PrepAtt counter is incremented by 1
each time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST message
CSFB procedure is for LCS.
As shown at point A in Figure 1-182, the L.CSFB.LCS.PrepAtt counter is incremented by 1
each time the eNodeB receives a UE CONTEXT MODIFICATION REQUEST message
CSFB procedure is for LCS.

Figure 1-181
Figure 1-182
Formula
None
Unit
None

Related Features
L.CSFB.LCS.PrepAtt Multi-mode: None

GSM: None
UMTS: None
LOFD-001023 SRVCC to GERAN
1.23.32 Number of Responses Sent from the eNodeB to MMEs for

CSFB Triggered by LCS
Counters
1526728410 L.CSFB.LCS.Pr Number of BTS3900, L

epSucc responses sent BTS3900 LTE
from the
eNodeB to
MMEs for
CSFB triggered
by LCS
Description
The counter measures the number of responses sent from the eNodeB to MMEs for CSFB
triggered by LCS.
TS 36.413 V10.4.0.

Measurement Points
As shown at point C in Figure 1-183, 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.
As shown at point C in Figure 1-184, the L.CSFB.LCS.PrepSucc counter is incremented by

1each time the eNodeB successfully sends a UE CONTEXT MODIFICATION RESPONSE
message to the MME and the eNodeB determines that the CSFB procedure is for LCS.
Figure 1-183
Figure 1-184
Formula
None

Unit
None
Related Features
L.CSFB.LCS.PrepSucc Multi-mode: None

GSM: None
UMTS: None
LOFD-001023 SRVCC to GERAN
1.23.33 Number of CCO Executions from E-UTRAN to GERAN

Counters
1526728441 L.CCO.E2G.Ex Number of BTS3900, L

ecAttOut CCO BTS3900 LTE
executions from
E-UTRAN to
GERAN
Description
The counter measures the number of CCO executions from E-UTRAN to GERAN in a cell.
V10.4.0.
Measurement Points
As shown at point B in Figure 1-185, 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 1-185
Formula
None
Unit
None
Related Features
L.CCO.E2G.ExecAttOut Multi-mode: None

GSM: None
UMTS: None
GERAN
between E-UTRAN and
GERAN

1.23.34 Number of Successful CCOs from E-UTRAN to GERAN

Counters
1526728442 L.CCO.E2G.Ex Number of BTS3900, L

ecSuccOut successful BTS3900 LTE
CCOs from E-
UTRAN to
GERAN
Description
The counter measures the number of successful CCOs from E-UTRAN to GERAN in a cell.
V10.4.0.
Disuse Statement:
The L.CCO.E2G.ExecSuccOut counter will be deleted in later versions. In this version, the
counter value is normally reported (or the value 0 is reported), and it is recommended that this
counter not be used.
Measurement Points
As shown at point C in Figure 1-186, 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 1-186
Formula
None
Unit
None
Related Features
L.CCO.E2G.ExecSuccOut Multi-mode: None

GSM: None
UMTS: None
GERAN
between E-UTRAN and
GERAN

1.23.35 Number of Inter-RAT Handover Initiation Failures

Because the Adjacent Cell is not the NRT of the Source Cell
Counters

W.NoNRT inter-RAT BTS3900 LTE
initiation
failures from E-
UTRAN to
WCDMA
network
because the
adjacent cell is
not on the NRT
of the source
cell

.NoNRT inter-RAT BTS3900 LTE
initiation
failures from E-
UTRAN to TD-
SCDMA
network
because the
adjacent cell is
not on the NRT
of the source
cell

G.NoNRT inter-RAT BTS3900 LTE
initiation
failures from E-
UTRAN to
GERAN
because the
adjacent cell is
not on the NRT
of the source
cell



xRTT.NoNRT inter-RAT BTS3900 LTE
initiation
failures from E-
UTRAN to
CDMA2000
1xRTT network
because the
adjacent cell is
not on the NRT
of the source
cell

HRPD.NoNRT inter-RAT BTS3900 LTE
initiation
failures from E-
UTRAN to
CDMA2000
HRPD network
because the
adjacent cell is
not on the NRT
of the source
cell
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.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-187 or Figure 1-188, 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 1-187 shows the measurement procedure on a GERAN. Figure 1-188 shows
the measurement procedure on a UTRAN or a CDMA2000 network. The counters are

The L.IRATHO.E2W.NoNRT counter is incremented by 1 each time the eNodeB receives a

measurement report on WCDMA network adjacent cells from the UE.
The L.IRATHO.E2T.NoNRT counter is incremented by 1 each time the eNodeB receives a
measurement report on TD-SCDMA network adjacent cells from the UE.
The L.IRATHO.E2G.NoNRT counter is incremented by 1 each time the eNodeB receives a
measurement report on GERAN adjacent cells from the UE.
The L.IRATHO.E21xRTT.NoNRT counter is incremented by 1 each time the eNodeB
receives a measurement report on CDMA2000 1xRTT network adjacent cells from the UE.
The L.IRATHO.E2HRPD.NoNRT counter is incremented by 1 each time the eNodeB receives
a measurement report on CDMA2000 HRPD network adjacent cells from the UE.
Figure 1-187

Figure 1-188
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.NoNRT Multi-mode: None

GSM: None
UMTS: None
UTRAN
TDLOFD-001019
Inter-RAT ANR
TDLBFD-002002
TDLOFD-001022 UTRAN
Transport Channel
Management
SRVCC to UTRAN
SRVCC to UTRAN

L.IRATHO.E2T.NoNRT Multi-mode: None

GSM: None
UMTS: None
UTRAN
TDLOFD-001019
Inter-RAT ANR
TDLBFD-002002
TDLOFD-001022 UTRAN
Transport Channel
Management
SRVCC to UTRAN
SRVCC to UTRAN
L.IRATHO.E2G.NoNRT Multi-mode: None

GSM: None
UMTS: None
GERAN
TDLOFD-001020
Inter-RAT ANR
TDLBFD-002002
TDLOFD-001023 GERAN
Transport Channel
Management
SRVCC to GERAN
SRVCC to GERAN
L.IRATHO.E21xRTT.NoNR Multi-mode: None

T GSM: None
UMTS: None
CDMA2000
TDLOFD-001021
Inter-RAT ANR
TDLBFD-002002
between E-UTRAN and
CDMA2000
Transport Channel
Management

L.IRATHO.E2HRPD.NoNR Multi-mode: None

T GSM: None
UMTS: None
CDMA2000
TDLOFD-001021
Inter-RAT ANR
TDLBFD-002002
between E-UTRAN and
CDMA2000
Transport Channel
Management
1.23.36 Number of CSFB Preparation Failures Because of Process

Conflict
Counters
1526728513 L.CSFB.PrepFa Number of BTS3900, L

il.Conflict CSFB BTS3900 LTE
preparation
failures because
of process
conflict
Description
The counter measures the average number of CSFB Preparation Failures Because of Process
Conflict.
V10.4.0.
Measurement Points
As shown at point C in Figure 1-189, 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 1-189
Formula
None
Unit
None
Related Features
L.CSFB.PrepFail.Conflict Multi-mode: None

GSM: None
UMTS: None

TDLOFD-001034
LOFD-001035
1xRTT

1.23.37 Number of Handover Preparation Attempts from E-

UTRAN to WCDMA Network Triggered Because of High Load
Counters

W.Load.PrepAtt inter-RAT BTS3900 LTE
Out handover
preparation
attempts from
E-UTRAN to
WCDMA
network
triggered
because of high
load

G.Load.PrepAtt inter-RAT BTS3900 LTE
Out handover
preparation
attempts from
E-UTRAN to
GERAN
triggered
because of high
load

.Load.PrepAttO inter-RAT BTS3900 LTE
ut handover
preparation
attempts from
E-UTRAN to
TD-SCDMA
network
triggered
because of high
load
Description
The counter measures the number of inter-RAT handover preparation attempts triggered
because of high load in a cell.
V10.4.0.

Measurement Points
As shown at point A in Figure 1-190, 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 load balancing 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 load balancing.
As shown at point A in Figure 1-190, the L.IRATHO.E2G.Load.PrepAttOut counter is

to GERAN triggered because of load balancing or the eNodeB decides to perform a handover
from E-UTRAN to GERAN after the eNodeB receives a measurement report from the UE
triggered because of load balancing.
As shown at point A in Figure 1-190, the L.IRATHO.E2T.Load.PrepAttOut counter is

to TD-SCDMA network triggered because of load balancing or the eNodeB decides to
perform a handover from E-UTRAN to TD-SCDMA network after the eNodeB receives a
measurement report from the UE triggered because of load balancing.
Figure 1-190
Formula
None
Unit
None

Related Features
L.IRATHO.E2W.Load.Prep Multi-mode: None

AttOut GSM: None
UMTS: None
TDLOFD-001044 UTRAN
LOFD-001022 Inter-RAT Load Sharing to
UTRAN
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
L.IRATHO.E2G.Load.Prep Multi-mode: None

AttOut GSM: None
UMTS: None
TDLOFD-001045 GERAN
GERAN
TDLOFD-001023
SRVCC to GERAN
SRVCC to GERAN
L.IRATHO.E2T.Load.PrepA Multi-mode: None

ttOut GSM: None
UMTS: None
UTRAN

1.23.38 Number of Inter-RAT Handover Execution Attempts

Triggered Because of High Load
Counters

W.Load.ExecAt inter-RAT BTS3900 LTE
tOut handover
execution
attempts from
E-UTRAN to
WCDMA
network
triggered
because of high
load

G.Load.ExecAt inter-RAT BTS3900 LTE
tOut handover
execution
attempts from
E-UTRAN to
GERAN
triggered
because of high
load

.Load.ExecAtt inter-RAT BTS3900 LTE
Out handover
execution
attempts from
E-UTRAN to
TD-SCDMA
network
triggered
because of high
load
Description
The counter measures the number of inter-RAT handover execution attempts triggered
V10.4.0.

Measurement Points
As shown at point B in Figure 1-191, 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 load balancing and sends a Mobility From EUTRA
Command message to the UE.
As shown at point B in Figure 1-191, the L.IRATHO.E2G.Load.ExecAttOut counter is
GERAN triggered because of load balancing and sends a Mobility From EUTRA Command
message to the UE.
As shown at point B in Figure 1-191, the L.IRATHO.E2T.Load.ExecAttOut counter is
TD-SCDMA network triggered because of load balancing and sends a Mobility From
EUTRA Command message to the UE.
Figure 1-191
Formula
None
Unit
None

Related Features
L.IRATHO.E2W.Load.Exec Multi-mode: None

AttOut GSM: None
UMTS: None
TDLOFD-001044 UTRAN
UTRAN
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
L.IRATHO.E2G.Load.Exec Multi-mode: None

AttOut GSM: None
UMTS: None
TDLOFD-001045 GERAN
GERAN
TDLOFD-001023
SRVCC to GERAN
SRVCC to GERAN
L.IRATHO.E2T.Load.Exec Multi-mode: None

AttOut GSM: None
UMTS: None
UTRAN

1.23.39 Number of Successful Inter-RAT Handover Executions

Triggered Because of High Load
Counters

W.Load.ExecSu successful inter- BTS3900 LTE
ccOut RAT handover
executions from
E-UTRAN to
WCDMA
network
triggered
because of high
load

G.Load.ExecSu successful inter- BTS3900 LTE
ccOut RAT handover
executions from
E-UTRAN to
GERAN
triggered
because of high
load

.Load.ExecSucc successful inter- BTS3900 LTE
Out RAT handover
executions from
E-UTRAN to
TD-SCDMA
network
triggered
because of high
load
Description
The counter measures the number of successful inter-RAT handover executions triggered
V10.4.0.
Measurement Points
As shown at point C in Figure 1-192, the L.IRATHO.E2W.Load.ExecSuccOut counter is

WCDMA network triggered because of load balancing and the eNodeB receives a UE
CONTEXT RELEASE COMMAND message from the MME after the UE is handed over to a
WCDMA network.
As shown at point C in Figure 1-192, the L.IRATHO.E2G.Load.ExecSuccOut counter is
GERAN triggered because of load balancing and the eNodeB receives a UE CONTEXT
RELEASE COMMAND message from the MME after the UE is handed over to a GERAN.
As shown at point C in Figure 1-192, the L.IRATHO.E2T.Load.ExecSuccOut counter is
TD-SCDMA network triggered because of load balancing and the eNodeB receives a UE
TD-SCDMA network.
Figure 1-192
Formula
None
Unit
None

Related Features
L.IRATHO.E2W.Load.Exec Multi-mode: None

SuccOut GSM: None
UMTS: None
TDLOFD-001044 UTRAN
UTRAN
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
L.IRATHO.E2G.Load.Exec Multi-mode: None

SuccOut GSM: None
UMTS: None
TDLOFD-001045 GERAN
GERAN
TDLOFD-001023
SRVCC to GERAN
SRVCC to GERAN
L.IRATHO.E2T.Load.ExecS Multi-mode: None

uccOut GSM: None
UMTS: None
UTRAN

1.23.40 Number of Redirections from E-UTRAN to WCDMA

Network Triggered Because of High Load
Counters

on.E2W.Load redirections BTS3900 LTE
from E-
UTRAN to
WCDMA
network
triggered
because of high
load

on.E2G.Load redirections BTS3900 LTE
from E-
UTRAN to
GERAN
triggered
because of high
load

on.E2T.Load redirections BTS3900 LTE
from E-
UTRAN to
TDSCDMA
triggered
because of high
load
Description
The counters measure the number of redirections from E-UTRAN to another system triggered
V10.4.0.
Measurement Points
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 load balancing. If the target
system is WCDMA network, the L.RRCRedirection.E2W.Load counter is incremented by 1.
If the target system is TDSCDMA network, the L.RRCRedirection.E2T.Load counter is

incremented by 1. If the target system is GERAN, the L.RRCRedirection.E2G.Load counter is

incremented by 1.
Figure 1-193
Formula
None
Unit
None
Related Features
L.RRCRedirection.E2W.Loa Multi-mode: None

d GSM: None
UMTS: None
TDLOFD-001044 UTRAN
UTRAN
L.RRCRedirection.E2G.Loa Multi-mode: None

d GSM: None
UMTS: None
TDLOFD-001045 GERAN
GERAN
L.RRCRedirection.E2T.Loa Multi-mode: None

d GSM: None
UMTS: None
UTRAN


to WCDMA Network Triggered for UEs to Go back to the
HPLMN
Counters

W.RegainHPL inter-RAT BTS3900 LTE
MN.PrepAttOut handover
attempts from
E-UTRAN to
WCDMA
network
triggered for
UEs to go back
to the HPLMN
Description
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.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-194, 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 1-194
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.RegainHP Multi-mode: None

LMN.PrepAttOut GSM: None
UMTS: None
SPID


UTRAN to WCDMA Network Triggered for UEs to Go back to
the HPLMN
Counters

W.RegainHPL inter-RAT BTS3900 LTE
MN.ExecAttOu handover
t executions from
E-UTRAN to
WCDMA
network
triggered for
UEs to go back
to the HPLMN
Description
V10.4.0.
Measurement Points
As shown at point B in Figure 1-195, 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 1-195
Formula
None
Unit
None
Related Features

LMN.ExecAttOut GSM: None
UMTS: None
SPID

1.23.43 Number of Inter-RAT Handovers from E-UTRAN to

WCDMA Network Triggered for UEs to Go back to the HPLMN
Counters

W.RegainHPL successful inter- BTS3900 LTE
MN.ExecSuccO RAT handovers
ut from E-
UTRAN to
WCDMA
network
triggered for
UEs to go back
to the HPLMN
Description
V10.4.0.
Measurement Points
As shown at point C in Figure 1-196, 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 1-196
Formula
None
Unit
None
Related Features

LMN.ExecSuccOut GSM: None
UMTS: None
SPID


UTRAN to WCDMA Network Triggered for UEs That Do not
Transmit or Receive Data
Counters

W.NoData.Exec inter-RAT BTS3900 LTE
AttOut handover
executions from
E-UTRAN to
WCDMA
network
triggered for
UEs that do not
transmit or
receive data
Description
WCDMA network triggered for a UE that has no data transmission.
V10.4.0.
Measurement Points
As shown at point B in Figure 1-197, 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 1-197
Formula
None
Unit
None

Related Features
L.IRATHO.E2W.NoData.Ex Multi-mode: None

ecAttOut GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
LOFD-001105 UTRAN
Dynamic DRX
Dynamic DRX

UTRAN to WCDMA Network Triggered for UEs That Do not
Transmit or Receive Data
Counters

W.NoData.Exec successful inter- BTS3900 LTE
from E-
UTRAN to
WCDMA
network
triggered for
UEs that do not
transmit or
receive data
Description
WCDMA network triggered for UEs that do not transmit or receive data.

V10.4.0.
Measurement Points
As shown at point C in Figure 1-198, 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.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 a WCDMA network.
Figure 1-198
Formula
None
Unit
None

Related Features
L.IRATHO.E2W.NoData.Ex Multi-mode: None

ecSuccOut GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
LOFD-001105 UTRAN
Dynamic DRX
Dynamic DRX
1.23.46 Number of LCS-based Inter-RAT Handover Executions for

SRVCC
Counters

VCC.LCS.E2W CSFB-based BTS3900 LTE
.PrepAttOut handover
attempts from
E-UTRAN to
WCDMA
network for
SRVCC

VCC.LCS.E2W CSFB-based BTS3900 LTE
.ExecAttOut handover
executions from
E-UTRAN to
WCDMA
network for
SRVCC



VCC.LCS.E2W successful BTS3900 LTE
.ExecSuccOut CSFB-based
handovers from
E-UTRAN to
WCDMA
network for
SRVCC

VCC.LCS.E2G. CSFB-based BTS3900 LTE
PrepAttOut handover
attempts from
E-UTRAN to
GERAN for
SRVCC

VCC.LCS.E2G. CSFB-based BTS3900 LTE
ExecAttOut handover
executions from
E-UTRAN to
GERAN for
SRVCC

VCC.LCS.E2G. successful BTS3900 LTE
handovers from
E-UTRAN to
GERAN for
SRVCC

VCC.LCS.E2T. CSFB-based BTS3900 LTE
PrepAttOut handover
attempts from
E-UTRAN to
TD-SCDMA
network for
SRVCC

VCC.LCS.E2T. CSFB-based BTS3900 LTE
ExecAttOut handover
executions from
E-UTRAN to
TD-SCDMA
network for
SRVCC



VCC.LCS.E2T. successful BTS3900 LTE
handovers from
E-UTRAN to
TD-SCDMA
network for
SRVCC
Description
The counters measure the number of CSFB-based inter-RAT handover attempts from E-
UTRAN to another system. 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.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-199, 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.
As shown at point B in Figure 1-199, the L.IRATHO.SRVCC.LCS.E2W.ExecAttOut counter
is incremented by 1 each time the eNodeB decides to perform an SRVCC procedure from E-
UTRAN to WCDMA network triggered by CSFB and the eNodeB sends a Mobility From
As shown at point C in Figure 1-199, the L.IRATHO.SRVCC.LCS.E2W.ExecSuccOut
counter is incremented by 1 each time the eNodeB decides to perform an SRVCC procedure
from E-UTRAN to WCDMA network triggered by CSFB and the eNodeB receives a UE
WCDMA network.
As shown at point A in Figure 1-199, the L.IRATHO.SRVCC.LCS.E2G.PrepAttOut counter
to GERAN.
As shown at point B in Figure 1-199, the L.IRATHO.SRVCC.LCS.E2G.ExecAttOutOut
from E-UTRAN to GERAN triggered by CSFB and the eNodeB sends a Mobility From
As shown at point C in Figure 1-199, the L.IRATHO.SRVCC.LCS.E2G.ExecSuccOut
from E-UTRAN to GERAN triggered by CSFB and the eNodeB receives a UE CONTEXT
RELEASE COMMAND message from the MME after the UE is handed over to the GERAN.

As shown at point A in Figure 1-199, the L.IRATHO.SRVCC.LCS.E2T.PrepAttOut counter

to TD-SCDMA network.
As shown at point B in Figure 1-199, the L.IRATHO.SRVCC.LCS.E2T.ExecAttOut counter
UTRAN to TD-SCDMA network triggered by CSFB and the eNodeB sends a Mobility From
As shown at point C in Figure 1-199, the L.IRATHO.SRVCC.LCS.E2T.ExecSuccOut counter
UTRAN to TD-SCDMA network triggered by CSFB and the eNodeB receives a UE
TD-SCDMA network.
Figure 1-199
Formula
None
Unit
None

Related Features
L.IRATHO.SRVCC.LCS.E2 Multi-mode: None

W.PrepAttOut GSM: None
UMTS: None

W.ExecAttOut GSM: None
UMTS: None

W.ExecSuccOut GSM: None
UMTS: None

G.PrepAttOut GSM: None
UMTS: None

G.ExecAttOut GSM: None
UMTS: None

G.ExecSuccOut GSM: None
UMTS: None

T.PrepAttOut GSM: None
UMTS: None


T.ExecAttOut GSM: None
UMTS: None

T.ExecSuccOut GSM: None
UMTS: None
1.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

xRTT.MMEAb responses for BTS3900 LTE
normRsp abnormal
causes received
by the eNodeB
from the MME
during inter-
RAT handover
executions from
E-UTRAN to
CDMA2000
1xRTT network



HRPD.MMEAb responses for BTS3900 LTE
normRsp abnormal
causes received
by the eNodeB
from the MME
during inter-
RAT handover
executions from
E-UTRAN to
CDMA2000
HRPD network

W.MMEAbnor responses for BTS3900 LTE
mRsp abnormal
causes received
by the eNodeB
from the MME
during inter-
RAT handover
executions from
E-UTRAN to
WCDMA
network

G.MMEAbnor responses for BTS3900 LTE
mRsp abnormal
causes received
by the eNodeB
from the MME
during inter-
RAT handover
executions from
E-UTRAN to
GERAN

.MMEAbnorm responses for BTS3900 LTE
Rsp abnormal
causes received
by the eNodeB
from the MME
during inter-
RAT handover
executions from
E-UTRAN to
TD-SCDMA
network

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.
V10.4.0.
Measurement Points
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.
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 1-200

Figure 1-201
Formula
None
Unit
None
Related Features
L.IRATHO.E21xRTT.MME Multi-mode: None

AbnormRsp GSM: None
UMTS: None
CDMA2000
between E-UTRAN and
CDMA2000

L.IRATHO.E2HRPD.MME Multi-mode: None

AbnormRsp GSM: None
UMTS: None
CDMA2000
between E-UTRAN and
CDMA2000
L.IRATHO.E2W.MMEAbn Multi-mode: None

ormRsp GSM: None
UMTS: None
UTRAN
LOFD-001022
UTRAN
SRVCC to UTRAN
SRVCC to UTRAN
L.IRATHO.E2G.MMEAbno Multi-mode: None

rmRsp GSM: None
UMTS: None
GERAN
LOFD-001023
GERAN
SRVCC to GERAN
SRVCC to GERAN

L.IRATHO.E2T.MMEAbno Multi-mode: None

rmRsp GSM: None
UMTS: None
UTRAN
LOFD-001022
UTRAN
SRVCC to UTRAN
SRVCC to UTRAN

the eNodeB from the MME During Inter-RAT Handover
Executions from E-UTRAN to Another System for SRVCC
Counters

VCC.E2W.MM responses for BTS3900 LTE
EAbnormRsp abnormal
causes received
by the eNodeB
from the MME
during inter-
RAT handover
executions from
E-UTRAN to
WCDMA
network for
SRVCC



VCC.E2G.MM responses for BTS3900 LTE
EAbnormRsp abnormal
causes received
by the eNodeB
from the MME
during inter-
RAT handover
executions from
E-UTRAN to
GERAN for
SRVCC

VCC.E2T.MM responses for BTS3900 LTE
EAbnormRsp abnormal
causes received
by the eNodeB
from the MME
during inter-
RAT handover
executions from
E-UTRAN to
TD-SCDMA
network for
SRVCC
Description
from the MME during inter-RAT handover executions from E-UTRAN to another system for
SRVCC.
V10.4.0.
Measurement Points
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 1-202
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2W.M Multi-mode: None

MEAbnormRsp GSM: None
UMTS: None
L.IRATHO.SRVCC.E2G.M Multi-mode: None

UMTS: None

L.IRATHO.SRVCC.E2T.M Multi-mode: None

UMTS: None

the eNodeB from the MME During CCO Executions from E-
UTRAN to GERAN
Counters
1526728897 L.CCO.E2G.M Number of BTS3900, L

MEAbnormRsp responses for BTS3900 LTE
abnormal
causes received
by the eNodeB
from the MME
during CCO
executions from
E-UTRAN to
GERAN
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.
V10.4.0.
Disuse Statement:
The L.CCO.E2G.MMEAbnormRsp counter will be deleted in later versions. In this version,
the counter value is normally reported (or the value 0 is reported), and it is recommended that
this counter not be used.
Measurement Points
As shown at point C in Figure 1-203, 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 1-203
Formula
None
Unit
None
Related Features
L.CCO.E2G.MMEAbnorm Multi-mode: None

Rsp GSM: None
UMTS: None
GERAN
between E-UTRAN and
GERAN


the eNodeB from the MME During CSFB-based Inter-RAT
Handover Executions from E-UTRAN to Another System
Counters

C.CSFB.MME responses for BTS3900 LTE
AbnormRsp abnormal
causes received
by the eNodeB
from the MME
during CSFB-
based inter-
RAT handover
executions from
E-UTRAN to
CDMA2000
network

W.CSFB.MME responses for BTS3900 LTE
AbnormRsp abnormal
causes received
by the eNodeB
from the MME
during CSFB-
based inter-
RAT handover
executions from
E-UTRAN to
WCDMA
network

G.CSFB.MME responses for BTS3900 LTE
AbnormRsp abnormal
causes received
by the eNodeB
from the MME
during CSFB-
based inter-
RAT handover
executions from
E-UTRAN to
GERAN



.CSFB.MMEA responses for BTS3900 LTE
bnormRsp abnormal
causes received
by the eNodeB
from the MME
during CSFB-
based inter-
RAT handover
executions from
E-UTRAN to
TD-SCDMA
network
Description
from the MME during CSFB-based inter-RAT handover executions from E-UTRAN to
another system.
V10.4.0.
Measurement Points
As shown at point C in Figure 1-204, during an CSFB-based inter-RAT handover from E-
UTRAN to CDMA2000 network, the L.IRATHO.E2C.CSFB.MMEAbnormRsp counter is
message from the MME and the release cause is not "Successful Handover" or "Normal
Release".
As shown at point C in Figure 1-205, during an CSFB-based 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.CSFB.MMEAbnormRsp counter is incremented by 1. If the target system is
TD-SCDMA network, the L.IRATHO.E2T.CSFB.MMEAbnormRsp counter is incremented
by 1. If the target system is GERAN, the L.IRATHO.E2G.CSFB.MMEAbnormRsp counter is
incremented by 1.

Figure 1-204
Figure 1-205

Formula
None
Unit
None
Related Features
L.IRATHO.E2C.CSFB.MM Multi-mode: None

EAbnormRsp GSM: None
UMTS: None
TDLOFD-001035 1xRTT
1xRTT
L.IRATHO.E2W.CSFB.MM Multi-mode: None

UMTS: None
L.IRATHO.E2G.CSFB.MM Multi-mode: None

UMTS: None
L.IRATHO.E2T.CSFB.MM Multi-mode: None

UMTS: None


to CDMA2000 HRPD Network
Counters

HRPD.PrepAtt inter-RAT BTS3900 LTE
Out handover
attempts from
E-UTRAN to
CDMA2000
HRPD network
Description
CDMA2000 HRPD network in a cell.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-206, the L.IRATHO.E2HRPD.PrepAttOut counter is
the E-UTRAN to a CDMA2000 HRPD network or decides to perform an inter-RAT handover
from the E-UTRAN to a CDMA2000 HRPD network after receiving a measurement report
from a UE.

Figure 1-206
Formula
None
Unit
None

Related Features
L.IRATHO.E2HRPD.PrepA Multi-mode: None

ttOut GSM: None
UMTS: None
CDMA2000
TDLOFD-001021
TDLOFD-001035 1xRTT
between E-UTRAN and
CDMA2000
1xRTT

UTRAN to CDMA2000 HRPD Network
Counters

HRPD.ExecAtt inter-RAT BTS3900 LTE
Out handover
executions from
E-UTRAN to
CDMA2000
HRPD network
Description
V10.4.0.
Measurement Points
CDMA2000 HRPD network, the L.IRATHO.E2HRPD.ExecAttOut counter is incremented by
1 each time the eNodeB sends a Mobility From EUTRA Command message to the UE.

Figure 1-207
Formula
None
Unit
None

Related Features
L.IRATHO.E2HRPD.ExecA Multi-mode: None

ttOut GSM: None
UMTS: None
CDMA2000
TDLOFD-001021
TDLOFD-001035 1xRTT
between E-UTRAN and
CDMA2000
1xRTT

UTRAN to CDMA2000 HRPD Network
Counters

HRPD.ExecSuc successful inter- BTS3900 LTE
cOut RAT handovers
from E-
UTRAN to
CDMA2000
HRPD network
Description
V10.4.0.
Measurement Points
CDMA2000 HRPD network, the L.IRATHO.E2HRPD.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 the CDMA2000 HRPD
network.
Figure 1-208
Formula
None
Unit
None

Related Features
L.IRATHO.E2HRPD.ExecS Multi-mode: None

uccOut GSM: None
UMTS: None
CDMA2000
TDLOFD-001021
TDLOFD-001035 1xRTT
between E-UTRAN and
CDMA2000
1xRTT
1.23.54 Handover Time from E-UTRAN to Another RAT

Counters
1526729432 L.IRATHO.E2 Average BTS3900, L

W.TimeAvg handover BTS3900 LTE
duration from
E-UTRAN to
WCDMA
network
1526729433 L.IRATHO.E2 Average BTS3900, L

G.TimeAvg handover BTS3900 LTE
duration from
E-UTRAN to
GERAN
1526729434 L.IRATHO.E2T Average BTS3900, L

.TimeAvg handover BTS3900 LTE
duration from
E-UTRAN to
TD-SCDMA
network
Description
The counters measure the time of a successful handover from E-UTRAN to another RAT.

3GPP TS 36.300 V10.6.0 and section 8.3.3 in 3GPP TS 36.413 V10.4.0.
Measurement Points
As shown in Figure 1-209, the time of a handover equals the interval between the source
eNodeB sending a HANDOVER REQUIRED message to the MME and receiving a UE
CONTEXT RELEASE COMMAND message from the MME. At the end of a measurement
period, the average of these sampling results is used as the value of the counter. If the target
cell is a WCDMA cell, the L.IRATHO.E2W.TimeAvg counter is measured. During a
handover, the MME starts the timer and sends a UE CONTEXT RELEASE COMMAND to
the source eNodeB when the timer expires. Therefore, the value of the counter is affected by
the timer configuration.
cell is a GERAN cell, the L.IRATHO.E2G.TimeAvg counter is measured. During a handover,
the MME starts the timer and sends a UE CONTEXT RELEASE COMMAND to the source
eNodeB when the timer expires. Therefore, the value of the counter is affected by the timer
configuration.
cell is a TD-SCDMA cell, the L.IRATHO.E2T.TimeAvg counter is measured. During a
handover, the MME starts the timer and sends a UE CONTEXT RELEASE COMMAND to
the source eNodeB when the timer expires. Therefore, the value of the counter is affected by
the timer configuration.

Figure 1-209
Formula
None
Unit
ms
Related Features
L.IRATHO.E2W.TimeAvg Multi-mode: None

GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN

L.IRATHO.E2G.TimeAvg Multi-mode: None

GSM: None
UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN
TDLOFD-001020
TDLOFD-001023
GERAN
SRVCC to GERAN
L.IRATHO.E2T.TimeAvg Multi-mode: None

GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN

1.23.55 Number of Coverage-based Inter-RAT Handover Attempts

from E-UTRAN to Another System
Counters

W.Coverage.Pre coverage-based BTS3900 LTE
pAttOut handover
preparation
attempts from
E-UTRAN to
WCDMA
network

G.Coverage.Pre coverage-based BTS3900 LTE
pAttOut handover
preparation
attempts from
E-UTRAN to
GERAN
Description
The counters measure the number of coverage-based inter-RAT handover preparation
attempts from E-UTRAN to another system in a cell.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-210, the L.IRATHO.E2W.Coverage.PrepAttOut counter is
incremented by 1 each time the eNodeB decides to perform an inter-RAT handover to a
WCDMA network after receiving a measurement report from the UE triggered because of
coverage.
As shown at point A in Figure 1-210, the L.IRATHO.E2G.Coverage.PrepAttOut counter is
incremented by 1 each time the eNodeB decides to perform an inter-RAT handover to a
GERAN after receiving a measurement report from the UE triggered because of coverage.

Figure 1-210
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.Coverage. Multi-mode: None

PrepAttOut GSM: None
UMTS: None
UTRAN
LOFD-001022
UTRAN
SRVCC to UTRAN
SRVCC to UTRAN

L.IRATHO.E2G.Coverage.P Multi-mode: None

repAttOut GSM: None
UMTS: None
GERAN
LOFD-001023
GERAN
SRVCC to GERAN
SRVCC to GERAN
1.23.56 Number of Coverage-based Inter-RAT Handover

Counters

W.Coverage.Ex coverage-based BTS3900 LTE
ecAttOut handover
execution
attempts from
E-UTRAN to
WCDMA
network

G.Coverage.Ex coverage-based BTS3900 LTE
ecAttOut handover
execution
attempts from
E-UTRAN to
GERAN
Description
The counters measure the number of coverage-based inter-RAT handover execution attempts
from E-UTRAN to another system in a cell.
V10.4.0.

Measurement Points
As shown at point B in Figure 1-211, during a coverage-based inter-RAT handover from an
E-UTRAN to a WCDMA network, the L.IRATHO.E2W.Coverage.ExecAttOut counter is
to the UE.
As shown at point B in Figure 1-211, during a coverage-based inter-RAT handover from an
E-UTRAN to a GERAN, the L.IRATHO.E2G.Coverage.ExecAttOut counter is incremented
by 1 each time the eNodeB sends a Mobility From EUTRA Command message to the UE.
Figure 1-211
Formula
None
Unit
None

Related Features

ExecAttOut GSM: None
UMTS: None
UTRAN
LOFD-001022
UTRAN
SRVCC to UTRAN
SRVCC to UTRAN
L.IRATHO.E2G.Coverage.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
GERAN
LOFD-001023
GERAN
SRVCC to GERAN
SRVCC to GERAN
1.23.57 Number of Successful Coverage-based Inter-RAT

Handovers from E-UTRAN to Another System
Counters

W.Coverage.Ex successful BTS3900 LTE
ecSuccOut coverage-based
handover
executions from
E-UTRAN to
WCDMA
network



G.Coverage.Ex successful BTS3900 LTE
ecSuccOut coverage-based
handover
executions from
E-UTRAN to
GERAN
Description
The counters measure the number of successful coverage-based inter-RAT handover
executions from E-UTRAN to another system in a cell.
V10.4.0.
Measurement Points
As shown at point C in Figure 1-212, during a coverage-based inter-RAT handover from an
E-UTRAN to a WCDMA network, the L.IRATHO.E2W.Coverage.ExecSuccOut counter is
message from the MME after UE is handed over from the E-UTRAN to the WCDMA
network.
As shown at point C in Figure 1-212, during a coverage-based inter-RAT handover from an
E-UTRAN to a GERAN, the L.IRATHO.E2G.Coverage.ExecSuccOut counter is incremented
the MME after UE is handed over from the E-UTRAN to the GERAN.

Figure 1-212
Formula
None
Unit
None
Related Features

ExecSuccOut GSM: None
UMTS: None
UTRAN
LOFD-001022
UTRAN
SRVCC to UTRAN
SRVCC to UTRAN

L.IRATHO.E2G.Coverage.E Multi-mode: None

UMTS: None
GERAN
LOFD-001023
GERAN
SRVCC to GERAN
SRVCC to GERAN
1.23.58 Number of Coverage-based Inter-RAT Redirections from

E-UTRAN to Another System
Counters

on.E2W.Covera coverage-based BTS3900 LTE
ge redirections
from E-
UTRAN to
WCDMA
network

on.E2G.Covera coverage-based BTS3900 LTE
ge redirections
from E-
UTRAN to
GERAN
Description
The counters measure the number of coverage-based redirections from E-UTRAN to another
system in a cell.
V10.4.0.

Measurement Points
As shown at point A in Figure 1-213, during a coverage-based redirection to another system
initiated by the eNodeB, 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.
If the target system is WCDMA network, the L.RRCRedirection.E2W.Coverage counter is
incremented by 1.
If the target system is GERAN, the L.RRCRedirection.E2G.Coverage counter is incremented
by 1.
Figure 1-213
Formula
None
Unit
None
Related Features
L.RRCRedirection.E2W.Co Multi-mode: None

verage GSM: None
UMTS: None
UTRAN
between E-UTRAN and
UTRAN

L.RRCRedirection.E2G.Cov Multi-mode: None

erage GSM: None
UMTS: None
GERAN
between E-UTRAN and
GERAN
1.23.59 Number of SPID-based Inter-RAT Redirections Back to

the HPLMN
Counters

on.E2W.Regain SPID-based BTS3900 LTE
HPLMN redirections
back to a
WCDMA
network of the
HPLMN
Description
The counter measures the number of SPID-based inter-RAT redirections back to the HPLMN
in a cell.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-214, during a SPID-based inter-RAT redirection back to the
HPLMN initiated by the eNodeB, the L.RRCRedirection.E2W.RegainHPLMN counter is
UE and the target system is WCDMA network.

Figure 1-214
Formula
None
Unit
None
Related Features
L.RRCRedirection.E2W.Re Multi-mode: None

gainHPLMN GSM: None
UMTS: None
SPID
1.23.60 Number of Successful Service-based Inter-RAT Outgoing

Handover Attempts from E-UTRAN to Another System
Counters

W.Service.Prep service-based BTS3900 LTE
AttOut handover
preparation
attempts from
E-UTRAN to
WCDMA
network



G.Service.Prep service-based BTS3900 LTE
AttOut handover
preparation
attempts from
E-UTRAN to
GERAN
Description
The counters measure the number of service-based handover preparation attempts from E-
UTRAN to another system in a cell.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-215, the L.IRATHO.E2W.Service.PrepAttOut counter is
incremented by 1 each time the eNodeB decides to perform a handover to a WCDMA
network after receiving a measurement report from a UE because of services.
As shown at point A in Figure 1-215, the L.IRATHO.E2G.Service.PrepAttOut counter is
incremented by 1 each time the eNodeB decides to perform a handover to a GERAN after
receiving a measurement report from a UE because of services.
Figure 1-215

Formula
None
Unit
None
Related Features
L.IRATHO.E2W.Service.Pre Multi-mode: None

pAttOut GSM: None
UMTS: None
LTE: LOFD-001043 Service based inter-RAT
LOFD-001022 Service based Inter-RAT
handover to UTRAN
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
L.IRATHO.E2G.Service.Pre Multi-mode: None

pAttOut GSM: None
UMTS: None
handover to GERAN
TDLOFD-001023
SRVCC to GERAN
SRVCC to GERAN

1.23.61 Number of Service-based Inter-RAT Outgoing Handover

Counters

W.Service.Exec service-based BTS3900 LTE
AttOut handover
execution
attempts from
E-UTRAN to
WCDMA
network

G.Service.Exec service-based BTS3900 LTE
AttOut handover
execution
attempts from
E-UTRAN to
GERAN
Description
The counters measure the number of service-based handover execution attempts from E-
V10.4.0.
Measurement Points
As shown at point B in Figure 1-216, during a service-based handover from the E-UTRAN to
a WCDMA network, the L.IRATHO.E2W.Service.ExecAttOut counter is incremented by 1
each time the eNodeB sends a Mobility From EUTRA Command message to the UE.
As shown at point B in Figure 1-216, during a service-based handover from the E-UTRAN to
a GERAN, the L.IRATHO.E2G.Service.ExecAttOut counter is incremented by 1 each time

Figure 1-216
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.Service.Ex Multi-mode: None

ecAttOut GSM: None
UMTS: None
handover to UTRAN
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN

L.IRATHO.E2G.Service.Ex Multi-mode: None

ecAttOut GSM: None
UMTS: None
handover to GERAN
TDLOFD-001023
SRVCC to GERAN
SRVCC to GERAN
1.23.62 Number of Successful Service-based Inter-RAT Outgoing

Counters

W.Service.Exec successful BTS3900 LTE
SuccOut service-based
handover
executions from
E-UTRAN to
WCDMA
network

G.Service.Exec successful BTS3900 LTE
SuccOut service-based
handover
executions from
E-UTRAN to
GERAN
Description
The counters measure the number of successful service-based handover executions from E-
V10.4.0.

Measurement Points
As shown at point C in Figure 1-217, during a service-based handover from the E-UTRAN to
a WCDMA network, the L.IRATHO.E2W.Service.ExecSuccOut counter is incremented by 1
MME after UE is handed over from the E-UTRAN to the WCDMA network.
As shown at point C in Figure 1-217, during a service-based handover from the E-UTRAN to
a GERAN, the L.IRATHO.E2G.Service.ExecSuccOut counter is incremented by 1 each time
UE is handed over from the E-UTRAN to the GERAN.
Figure 1-217
Formula
None
Unit
None

Related Features
L.IRATHO.E2W.Service.Ex Multi-mode: None

ecSuccOut GSM: None
UMTS: None
handover to UTRAN
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
L.IRATHO.E2G.Service.Ex Multi-mode: None

ecSuccOut GSM: None
UMTS: None
handover to GERAN
TDLOFD-001023
SRVCC to GERAN
SRVCC to GERAN
1.23.63 Number of Service-based Inter-RAT Redirections from E-

Counters

on.E2W.Service service-based BTS3900 LTE
redirections
from E-
UTRAN to
WCDMA
network

on.E2G.Service service-based BTS3900 LTE
redirections
from E-
UTRAN to
GERAN

Description
The counters measure the total number of service-based redirections from E-UTRAN to
another system in a cell.
V10.4.0.
Measurement Points
As shown at point A in Figure 1-218, during a service-based redirection to another system
If the target system is WCDMA network, the L.RRCRedirection.E2W.Service counter is

incremented by 1.
If the target system is GERAN, the L.RRCRedirection.E2G.Service counter is incremented by

1.
Figure 1-218
Formula
None
Unit
None
Related Features
L.RRCRedirection.E2W.Ser Multi-mode: None

vice GSM: None
UMTS: None
handover to UTRAN

L.RRCRedirection.E2G.Ser Multi-mode: None

vice GSM: None
UMTS: None
handover to GERAN
1.23.64 Number of UL-Quality-based Outgoing Handover

Attempts from E-UTRAN to Another System
Counters
1526730026 L.IRATHO.E2 Number of UL- BTS3900, L

W.ULquality.Pr quality-based BTS3900 LTE
epAttOut handover
preparation
attempts from
E-UTRAN to
WCDMA
network

G.ULquality.Pr quality-based BTS3900 LTE
epAttOut handover
preparation
attempts from
E-UTRAN to
GERAN
Description
The counters measure the number of UL-quality-based handover preparation attempts from E-
V10.4.0.
Measurement Points
As shown at point A in Figure 1-219, the L.IRATHO.E2W.ULquality.PrepAttOut counter is
network after receiving a measurement report from a UE because of uplink signal quality.

As shown at point A in Figure 1-219, the L.IRATHO.E2G.ULquality.PrepAttOut counter is

receiving a measurement report from a UE because of uplink signal quality.
Figure 1-219
Formula
None
Unit
None

Related Features
L.IRATHO.E2W.ULquality. Multi-mode: None

UMTS: None
UTRAN
LOFD-001022
UTRAN
SRVCC to UTRAN
SRVCC to UTRAN
L.IRATHO.E2G.ULquality. Multi-mode: None

UMTS: None
GERAN
LOFD-001023
GERAN
SRVCC to GERAN
SRVCC to GERAN
1.23.65 Number of UL-Quality-based Outgoing Handover

Counters

W.ULquality.Ex quality-based BTS3900 LTE
ecAttOut handover
execution
attempts from
E-UTRAN to
WCDMA
network



G.ULquality.Ex quality-based BTS3900 LTE
ecAttOut handover
execution
attempts from
E-UTRAN to
GERAN
Description
The counters measure the number of UL-quality-based handover execution attempts from E-
V10.4.0.
Measurement Points
As shown at point B in Figure 1-220, during a UL-quality-based handover from the E-
UTRAN to a WCDMA network, the L.IRATHO.E2W.ULquality.ExecAttOut counter is
to the UE.
As shown at point B in Figure 1-220, during a UL-quality-based handover from the E-
UTRAN to a GERAN, the L.IRATHO.E2G.ULquality.ExecAttOut counter is incremented by
Figure 1-220

Formula
None
Unit
None
Related Features

UMTS: None
UTRAN
LOFD-001022
UTRAN
SRVCC to UTRAN
SRVCC to UTRAN

UMTS: None
GERAN
LOFD-001023
GERAN
SRVCC to GERAN
SRVCC to GERAN

1.23.66 Number of Successful UL-Quality-based Outgoing

Counters

W.ULquality.Ex successful UL- BTS3900 LTE
ecSuccOut quality-based
handover
executions from
E-UTRAN to
WCDMA
network

G.ULquality.Ex successful UL- BTS3900 LTE
ecSuccOut quality-based
handover
executions from
E-UTRAN to
GERAN
Description
The counters measure the number of successful UL-quality-based handover executions from
E-UTRAN to another system in a cell.
V10.4.0.
Measurement Points
As shown at point C in Figure 1-221, during a UL-quality-based handover from the E-
UTRAN to a WCDMA network, the L.IRATHO.E2W.ULquality.ExecSuccOut counter is
message from the MME after UE is handed over from the E-UTRAN to the WCDMA
network.
As shown at point C in Figure 1-221, during a UL-quality-based handover from the E-
UTRAN to a GERAN, the L.IRATHO.E2G.ULquality.ExecSuccOut counter is incremented
the MME after UE is handed over from the E-UTRAN to the GERAN.

Figure 1-221
Formula
None
Unit
None
Related Features

UMTS: None
UTRAN
LOFD-001022
UTRAN
SRVCC to UTRAN
SRVCC to UTRAN


UMTS: None
GERAN
LOFD-001023
GERAN
SRVCC to GERAN
SRVCC to GERAN
1.23.67 Number of UL-Quality-based Inter-RAT Redirections

from E-UTRAN to Another System
Counters
1526730032 L.RRCRedirecti Number of UL- BTS3900, L

on.E2W.Ulquali quality-based BTS3900 LTE
ty redirections
from E-
UTRAN to
WCDMA
network
1526730033 L.RRCRedirecti Number of UL- BTS3900, L

on.E2G.Ulquali quality-based BTS3900 LTE
ty redirections
from E-
UTRAN to
GERAN
Description
The counters measure the total number of UL-quality-based redirections from E-UTRAN to
V10.4.0.

Measurement Points
As shown at point A in Figure 1-222, during a UL-quality-based redirection to another
system initiated by the eNodeB, 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.
If the target system is WCDMA network, the L.RRCRedirection.E2W.ULquality counter is
incremented by 1.
If the target system is GERAN, the L.RRCRedirection.E2G.ULquality counter is incremented
by 1.
Figure 1-222
Formula
None
Unit
None
Related Features
L.RRCRedirection.E2W.Ulq Multi-mode: None

uality GSM: None
UMTS: None
UTRAN
between E-UTRAN and
UTRAN

L.RRCRedirection.E2G.Ulq Multi-mode: None

uality GSM: None
UMTS: None
GERAN
between E-UTRAN and
GERAN
1.23.68 Number of Distance-based Inter-RAT Outgoing Handover

Attempts from E-UTRAN to Another System
Counters

W.Distance.Pre distance-based BTS3900 LTE
pAttOut handover
preparation
attempts from
E-UTRAN to
WCDMA
network

G.Distance.Pre distance-based BTS3900 LTE
pAttOut handover
preparation
attempts from
E-UTRAN to
GERAN
Description
The counters measure the number of distance-based handover preparation attempts from E-
V10.4.0.

Measurement Points
As shown at point A in Figure 1-223, the L.IRATHO.E2W.Distance.PrepAttOut counter is
network after receiving a measurement report from a UE because of distance.
As shown at point A in Figure 1-223, the L.IRATHO.E2G.Distance.PrepAttOut counter is
receiving a measurement report from a UE because of distance.
Figure 1-223
Formula
None
Unit
None

Related Features
L.IRATHO.E2W.Distance.P Multi-mode: None

repAttOut GSM: None
UMTS: None
LTE: LOFD-001072 Distance based Inter-RAT
LOFD-001022 Distance based Inter-RAT
handover to UTRAN
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
L.IRATHO.E2G.Distance.Pr Multi-mode: None

epAttOut GSM: None
UMTS: None
handover to GERAN
TDLOFD-001023
SRVCC to GERAN
SRVCC to GERAN
1.23.69 Number of Distance-based Inter-RAT Outgoing Handover

Counters

W.Distance.Exe distance-based BTS3900 LTE
cAttOut handover
execution
attempts from
E-UTRAN to
WCDMA
network



G.Distance.Exe distance-based BTS3900 LTE
cAttOut handover
execution
attempts from
E-UTRAN to
GERAN
Description
The counters measure the number of distance-based handover execution attempts from E-
V10.4.0.
Measurement Points
As shown at point B in Figure 1-224, during a distance-based handover from the E-UTRAN
to a WCDMA network, the L.IRATHO.E2W.Distance.ExecAttOut counter is incremented by
As shown at point B in Figure 1-224, during a distance-based handover from the E-UTRAN
to a GERAN, the L.IRATHO.E2G.Distance.ExecAttOut counter is incremented by 1 each
time the eNodeB sends a Mobility From EUTRA Command message to the UE.
Figure 1-224

Formula
None
Unit
None
Related Features
L.IRATHO.E2W.Distance.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
handover to UTRAN
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN
L.IRATHO.E2G.Distance.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
handover to GERAN
TDLOFD-001023
SRVCC to GERAN
SRVCC to GERAN

1.23.70 Number of Successful Distance-based Inter-RAT

Outgoing Handovers from E-UTRAN to Another System
Counters

W.Distance.Exe successful BTS3900 LTE
cSuccOut distance-based
handover
executions from
E-UTRAN to
WCDMA
network

G.Distance.Exe successful BTS3900 LTE
cSuccOut distance-based
handover
executions from
E-UTRAN to
GERAN
Description
The counters measure the number of successful distance-based handovers from E-UTRAN to
V10.4.0.
Measurement Points
As shown at point C in Figure 1-225, during a distance-based handover from the E-UTRAN
to a WCDMA network, the L.IRATHO.E2W.Distance.ExecSuccOut counter is incremented
the MME after UE is handed over from the E-UTRAN to the WCDMA network.
As shown at point C in Figure 1-225, during a distance-based handover from the E-UTRAN
to a GERAN, the L.IRATHO.E2G.Distance.ExecSuccOut counter is incremented by 1 each
time the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME
after UE is handed over from the E-UTRAN to the GERAN.

Figure 1-225
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.Distance.E Multi-mode: None

UMTS: None
handover to UTRAN
TDLOFD-001022
SRVCC to UTRAN
SRVCC to UTRAN

L.IRATHO.E2G.Distance.E Multi-mode: None

UMTS: None
handover to GERAN
TDLOFD-001023
SRVCC to GERAN
SRVCC to GERAN
1.23.71 Number of Distance-based Inter-RAT Redirections from

E-UTRAN to Another System
Counters

on.E2W.Distanc distance-based BTS3900 LTE
e redirections
from E-
UTRAN to
WCDMA
network

on.E2G.Distanc distance-based BTS3900 LTE
e redirections
from E-
UTRAN to
GERAN
Description
The counters measure the total number of distance-based redirections from E-UTRAN to
V10.4.0.

Measurement Points
As shown at point A in Figure 1-226, during a distance-based redirection to another system
If the target system is WCDMA network, the L.RRCRedirection.E2W.Distance counter is
incremented by 1.
If the target system is GERAN, the L.RRCRedirection.E2G.Distance counter is incremented
by 1.
Figure 1-226
Formula
None
Unit
None
Related Features
L.RRCRedirection.E2W.Dis Multi-mode: None

tance GSM: None
UMTS: None
handover to UTRAN
L.RRCRedirection.E2G.Dist Multi-mode: None

ance GSM: None
UMTS: None
handover to GERAN

1.23.72 Number of Inter-RAT CSFB-based Handover Failures for

Different Causes
Counters

W.CSFB.Prep.F CSFB-based BTS3900 LTE
ailOut.MME outgoing
handover
preparation
failures from E-
UTRAN to
WCDMA
network
because of the
MME side
causes

ailOut.PrepFail outgoing
ure handover
preparation
failures from E-
UTRAN to
WCDMA
network
because of the
response of
handover
preparation
failure from
WCDMA
network

ailOut.NoReply outgoing
handover
preparation
failures from E-
UTRAN to
WCDMA
network
because of no
response from
WCDMA
network



.CSFB.Prep.Fai CSFB-based BTS3900 LTE
lOut.MME outgoing
handover
preparation
failures from E-
UTRAN to TD-
SCDMA
network
because of the
MME side
causes

lOut.PrepFailur outgoing
e handover
preparation
failures from E-
UTRAN to TD-
SCDMA
network
because of the
response of
handover
preparation
failure from
TD-SCDMA
network

lOut.NoReply outgoing
handover
preparation
failures from E-
UTRAN to TD-
SCDMA
network
because of no
response from
TD-SCDMA
network
Description
The counters measure the number of CSFB-based handover failures because of different
causes. CSFB-based outgoing handover failures mainly occur during the handover preparation
phase. The typical causes may be the MME side causes, no response from the target inter-

RAT cell, and a response of handover failure from the target inter-RAT cell. Handover
preparation is the procedure to prepare handover resources between the handover decision and
the handover execution. CSFB-based handover is a handover between E-UTRAN and another
system, and is a handover algorithm in the CSFB algorithm.
TS 36.413 V10.4.0.
Measurement Points
As shown at point A in Figure 1-227, in CSFB scenarios, based on the RAT of the target cell,
the corresponding counter is incremented by 1 each time the eNodeB does not receive a
HANDOVER COMMAND message from the MME after sending a HANDOVER
REQUIRED message to the MME. If the target cell is a WCDMA cell, the
L.IRATHO.E2W.CSFB.Prep.FailOut.NoReply counter is incremented by 1; if the target cell is
a TD-SCDMA cell, the L.IRATHO.E2T.CSFB.Prep.FailOut.NoReply counter is incremented
by 1.
the corresponding counter is incremented by 1 each time the eNodeB receives a HANDOVER
PREPARATION FAILURE message from the MME after sending a HANDOVER
L.IRATHO.E2W.CSFB.Prep.FailOut.PrepFailure counter is incremented by 1; if the target
cell is a TD-SCDMA cell, the L.IRATHO.E2T.CSFB.Prep.FailOut.PrepFailure counter is
incremented by 1.
the corresponding counter is incremented by one each time the eNodeB receives a UE
CONTEXT RELEASE COMMAND message from the MME after sending a HANDOVER
L.IRATHO.E2W.CSFB.Prep.FailOut.MME counter is incremented by 1; if the target cell is a
TD-SCDMA cell, the L.IRATHO.E2T.CSFB.Prep.FailOut.MME counter is incremented by 1.
Figure 1-227

Figure 1-228
Figure 1-229
Formula
None
Unit
None

Related Features

.FailOut.MME GSM: None
UMTS: None

.FailOut.PrepFailure GSM: None
UMTS: None

.FailOut.NoReply GSM: None
UMTS: None
L.IRATHO.E2T.CSFB.Prep. Multi-mode: None

FailOut.MME GSM: None
UMTS: None

FailOut.PrepFailure GSM: None
UMTS: None

FailOut.NoReply GSM: None
UMTS: None

1.23.73 Number of Inter-RAT SRVCC-based Handover Failures

for Different Causes
Counters

W.SRVCC.Prep SRVCC-based BTS3900 LTE
.FailOut.MME outgoing
handover
preparation
failures from E-
UTRAN to
WCDMA
network
because of the
MME side
causes

.FailOut.PrepFa outgoing
ilure handover
preparation
failures from E-
UTRAN to
WCDMA
network
because of the
response of
handover
preparation
failure from
WCDMA
network

.FailOut.NoRep outgoing
ly handover
preparation
failures from E-
UTRAN to
WCDMA
network
because of no
response from
WCDMA
network



.SRVCC.Prep.F SRVCC-based BTS3900 LTE
ailOut.MME outgoing
handover
preparation
failures from E-
UTRAN to TD-
SCDMA
network
because of the
MME side
causes

3900 Series Base Station ENodeBFunction Performance Counter Reference (V100R010C10 - 11) (PDF) - en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3900 Series Base Station ENodeBFunction Performance Counter Reference (V100R010C10 - 11) (PDF) - en

Uploaded by

Copyright:

Available Formats

3900 Series Base Station

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 11 (2016-12-05) Huawei Proprietary and Confidential i

1 Measurement of Cell Performance (Cell)................................................................................. 1

Issue 11 (2016-12-05) Huawei Proprietary and Confidential ii

Issue 11 (2016-12-05) Huawei Proprietary and Confidential iii

1.9.19 Times of ETWS-induced SIB1 changes................................................................................................................ 354

Issue 11 (2016-12-05) Huawei Proprietary and Confidential iv

Issue 11 (2016-12-05) Huawei Proprietary and Confidential v

Issue 11 (2016-12-05) Huawei Proprietary and Confidential vi

Issue 11 (2016-12-05) Huawei Proprietary and Confidential vii

1.17 Channel Quality Measurement1 (ChMeas.Pwr1.Cell)............................................................................................. 709

Issue 11 (2016-12-05) Huawei Proprietary and Confidential viii

Issue 11 (2016-12-05) Huawei Proprietary and Confidential ix

Issue 11 (2016-12-05) Huawei Proprietary and Confidential x

1.22.36 Number of UEs that apply TM9 in a cell.......................................................................................................... 1250

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xi

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xii

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xiii

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xiv

1.25.5 Number of Inter-RAT Handover Attempts from TD-SCDMA Network to E-UTRAN......................................1645

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xv

1.26.30 Inter-eNodeB Handover Time in a Cell.............................................................................................................1813

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xvi

1.26.71 Number of Successful Distance-based Inter-Duplex-Mode Handover Executions.......................................... 1972

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xvii

1.28.4 Number of Inter-eNodeB Incoming Handover Attempts in a Cell......................................................................2086

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xviii

1.33 Cell LCS Measurement (LCS.Cell)........................................................................................................................2264

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xix

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xx

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxi

1.40.40 L.Reserve.40...................................................................................................................................................... 2481

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxii

1.41.1 Number of Downlink Joint-scheduling UEs in a Combination Cell................................................................... 2510

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxiii

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxiv

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxv

1.55.10 Numbers of Used Downlink PRBs in Different Transmission Modes.............................................................. 3075

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxvi

2 Measurement of eNodeB Performance (eNodeB)............................................................. 3198

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxvii

2.5 eNodeB SCTP Measurement (SCTP.eNodeB)......................................................................................................... 3239

3 Measurement of S1 Link Performance (Sig.S1)................................................................. 3282

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxviii

4 Measurement of X2 Link Performance (Sig.X2)................................................................ 3288

5 Measurement of Intra-RAT Inter-Cell Handover Performance (NCell).......................3296

6 Measurement of CNOperator Performance (Cell.Operator)...........................................3359

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxix

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxx

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxxi

6.9 Throughput Distribution Measurement per CNOperator (Traffic.Thruput.PDF.Cell.Operator).............................. 3827

7 Measurement of EUTRAN Cell-to-GERAN Cell Handover Performance

8 Measurement of EUTRAN Cell-to-WCDMA Cell Handover Performance

9 Measurement of Cell Sector Equipment Performance (CellSectorEQUIP)................. 3982

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxxii

10 Measurement of Cell Sector Equipment Group Performance

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxxiii

11 Measurement of Board Service Performance (Board.Service)...................................... 4072

Issue 11 (2016-12-05) Huawei Proprietary and Confidential xxxiv

1 Measurement of Cell Performance (Cell)