BTS3203E V100R012C10SPH116 ENodeBFunction Performance Counter Reference

BTS3203E
V100R012C10
eNodeBFunction Performance
Counter Reference
Issue 03
Date 2017-03-10
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. 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 03 (2017-03-10) Huawei Proprietary and Confidential i

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

1.1 RRC Setup Measurement (RRC.Setup.Cell).................................................................................................................. 5
1.1.1 Number of RRC Connection Setup Requests in a Cell............................................................................................. 11
1.1.2 Number of Successful RRC Connection Setups in a Cell......................................................................................... 20
1.1.3 Number of RRC Connection Setup Attempts in a Cell............................................................................................. 25
1.1.4 Number of Times a UE switch from the Uplink-Synchronized State to the Uplink Out-of-Synchronization State. 26
1.1.5 Number of Times a UE switch from the Uplink Out-of-Synchronization state to the Uplink-Synchronized State..27
1.1.6 RRC Connection Setup Duration in a Cell................................................................................................................ 28
1.1.7 Number of Successfully Recovered RRC Connections When UEs switch from the Uplink Out-of-Synchronization
State to Uplink-Synchronized State....................................................................................................................................30
1.1.8 Maximum Number of RRC Connection Setup Requests in a Cell............................................................................32
1.2 RRC Setup Failure Measurement (RRC.SetupFail.Cell)............................................................................................. 33
1.2.1 Number of RRC Connection Setup Failures for Different Causes in a Cell............................................................. 36
1.3 RRC Reestablishment Measurement (RRC.ReEst.Cell).............................................................................................. 43
1.3.1 Number of RRC Connection Reestablishment Requests in a Cell............................................................................ 47
1.3.2 Number of Successful RRC Connection Reestablishments in a Cell........................................................................51
1.4 RRC Reestablishment Failure Measurement (RRC.ReEstFail.Cell)............................................................................55
1.4.1 Number of RRC Connection Reestablishment Failures for Different Causes in a Cell............................................ 58
1.5 E-RAB Setup Measurement (E-RAB.Est.Cell)............................................................................................................ 63
1.5.1 Number of E-RAB Setup Attempts in a Cell............................................................................................................ 83
1.5.2 Number of Successful E-RAB Setups in a Cell........................................................................................................ 89
1.5.3 Number of Initial E-RAB Setup Attempts in a Cell.................................................................................................. 95
1.5.4 Number of Successful Initial E-RAB Setups in a Cell............................................................................................ 100
1.5.5 Number of E-RAB Setup Attempts for Incoming Handovers in a Cell.................................................................. 106
1.5.6 Number of Successful E-RAB Setups for Incoming Handovers in a Cell.............................................................. 115
1.5.7 Number of UE-related Signaling Connection Setups over the S1 Interface........................................................... 125
1.5.8 E-RAB Setup Duration in a Cell............................................................................................................................. 131
1.5.9 Number of E-RAB Recovery Attempts When UEs switch from the Uplink Out-of-Synchronization State to
Uplink-Synchronized State...............................................................................................................................................136
1.5.10 Number of Successfully Recovered E-RABs When UEs switch from the Uplink Out-of-Synchronization State to
Uplink-Synchronized State...............................................................................................................................................138
1.6 E-RAB Release Measurement (E-RAB.Rel.Cell)...................................................................................................... 140
1.6.1 Number of Abnormal E-RAB Releases in a Cell.................................................................................................... 181
1.6.2 Number of Normal E-RAB Releases in a Cell........................................................................................................ 191
Issue 03 (2017-03-10) Huawei Proprietary and Confidential ii

BTS3203E
1.6.3 Number of Normal E-RAB Releases for Outgoing Handovers in a Cell................................................................ 197
1.6.4 Number of Abnormal E-RAB Releases for Outgoing Handovers in a Cell............................................................ 210
1.6.5 Total Number of Abnormal E-RAB Releases in a Cell...........................................................................................219
1.6.6 Number of Abnormal E-RAB Releases for Different Causes in a Cell.................................................................. 222
1.6.7 Number of Released E-RABs of UEs in the Uplink Out-of-Synchronization State............................................... 238
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....................................................................................................................................................... 240
1.6.9 Number of E-RAB Releases Initiated by the eNodeB in a Cell.............................................................................. 241
1.6.10 Number of E-RAB Releases Initiated by the MME in a Cell............................................................................... 245
1.6.11 Number of Remaining E-RABs in a Cell.............................................................................................................. 249
1.6.12 Number of E-RAB Releases Initiated by the eNodeB Because of the S1 RESET in a Cell................................. 253
1.6.13 Number of E-RAB Releases Initiated by the MME Because of the S1 RESET in a Cell.....................................258
1.6.14 Number of MME-triggered Abnormal E-RAB Releases...................................................................................... 262
1.6.15 Number of Abnormal E-RAB Releases for Other Reasons in a Cell.................................................................... 266
1.6.16 Number of MME-initiated Abnormal Releases of E-RABs During Handover Executions..................................272
1.6.17 Number of Normal E-RAB Releases Caused by Inactivity Timer Expiration...................................................... 278
1.6.18 Number of Normal Releases of E-RABs for Inter-RAT Outgoing Handovers..................................................... 279
1.6.19 Number of E-RABs Released by Defective UEs in a Cell....................................................................................284
1.6.20 Number of Normal Releases of E-RABs for Inter-Duplex-mode Outgoing Handovers.......................................286
1.7 E-RAB Setup Failure Measurement (E-RAB.EstFail.Cell)....................................................................................... 293
1.7.1 Number of E-RAB Setup Failures for Different Causes in a Cell...........................................................................306
1.7.2 Number of E-RAB Setup Failures for Other Causes in a Cell................................................................................ 332
1.8 E-RAB Modification Measurement (E-RAB.Modify.Cell)........................................................................................338
1.8.1 Number of E-RAB Modification Attempts in a Cell...............................................................................................342
1.8.2 Number of Successful E-RAB Modifications in a Cell...........................................................................................347
1.8.3 Number of E-RAB Modification Failures for Different Causes in a Cell............................................................... 351
1.9 Cell Algorithm Measurement (Algo.Cell)..................................................................................................................352
1.9.1 Number of Times Uplink or Downlink Congestion Occurs in a Cell..................................................................... 370
1.9.2 Duration of Uplink or Downlink Congestion in a Cell........................................................................................... 371
1.9.3 Number of Service Releases due to Congestion in a Cell....................................................................................... 372
1.9.4 Duration of Cell Unavailability............................................................................................................................... 373
1.9.5 Duration of Cell Availability................................................................................................................................... 374
1.9.6 Number of Signaling Messages over the Uu Interface............................................................................................375
1.9.7 Number of DRX Reconfiguration Messages...........................................................................................................376
1.9.8 Uplink or Downlink Voice Quality..........................................................................................................................377
1.9.9 Number of Times that E-UTRAN is Configured as the Highest Frequency Priority in an IMMCI IE...................380
1.9.10 Number of Times that the WCDMA Network is Configured as the Highest Frequency Priority in an IMMCI IE
.......................................................................................................................................................................................... 383
1.9.11 Number of Times that GERAN is Configured as the Highest Frequency Priority in an IMMCI IE.....................385
1.9.12 Number of Successful Preemptions Triggered due to User Limitation.................................................................386
1.9.13 Number of Times Semi-Persistent Scheduling is Performed in a Cell..................................................................387
1.9.14 Number of Failed Semi-Persistent Scheduling Transmissions in a Cell............................................................... 390
1.9.15 Number of Times UEs in Connected Mode Enter DRX for UEs in RRC_CONNECTED Mode........................ 393
Issue 03 (2017-03-10) Huawei Proprietary and Confidential iii

BTS3203E
1.9.16 Number of Times a UE in Connected Mode Exits DRX in RRC_CONECTED Mode........................................394

1.9.17 DRX Duration........................................................................................................................................................395
1.9.18 Number of Messages Sent for Instructing UEs to Enter or Exit TTI bundling Mode...........................................397
1.9.19 Times of ETWS-induced SIB1 changes................................................................................................................ 398
1.9.20 Number of processed ETWS-induced WRITE-REPLACE WARNING REQUEST messages in a cell..............399
1.9.21 Number of Packets of Non-GBR Bearers Discarded by AQM............................................................................. 401
1.9.22 Number of Times That Dynamic AC Barring Is Triggered...................................................................................402
1.9.23 Number of Times That Dynamic AC Barring Is Cancelled.................................................................................. 403
1.9.24 Number of Times That Parameters Related to Dynamic AC Barring Are Adjusted.............................................404
1.9.25 Control Duration of Dynamic AC Barring............................................................................................................ 405
1.9.26 Number of Times that the TDSCDMA Network is Configured as the Highest Frequency Priority in an IMMCI IE
.......................................................................................................................................................................................... 406
1.9.27 Number of S1 Signaling Messages Received or Sent by a Cell............................................................................ 408
1.9.28 Number of X2 Signaling Messages Received or Sent by a Cell........................................................................... 409
1.9.29 Distribution of Out-of-Synchronization Durations for UEs in a Cell................................................................... 410
1.9.30 Number of Times the eNodeB Delivers the Load-Triggered Inter-Frequency Measurement Configuration to a UE
.......................................................................................................................................................................................... 414
1.9.31 Number of Times the Load-Triggered Inter-Frequency Measurement is Successful............................................416
1.9.32 Duration in Which a Cell with Inter-Frequency Load Balancing Enabled Is in the High-Load State.................. 417
1.9.33 Number of Times a Cell with Inter-Frequency Load Balancing Enabled Enters from the Low-Load State to the
High-Load State................................................................................................................................................................418
1.9.34 Number of times that a cell is unavailable.............................................................................................................419
1.9.35 Uplink or Downlink Voice Quality of AMR-WB Services................................................................................... 420
1.9.36 Number of Normal Voice Call Releases in the Cell.............................................................................................. 423
1.9.37 Number of Times that a UE Experiences Voice Mute in the Cell......................................................................... 425
1.9.38 Number of Times that an eNodeB Attempts to Measure the Time Difference Among eNodeBs by Using UEs
Performing Inter-eNodeB Handovers...............................................................................................................................427
1.9.39 Number of Times that an eNodeB Attempts to Measure the Time Difference Among eNodeBs by Using Inter-
eNodeB CEUs...................................................................................................................................................................429
1.9.40 Number of Times that an eNodeB Successfully Measures the Time Difference Among eNodeBs by Using UEs
that Are Performing Inter-eNodeB Handovers.................................................................................................................431
1.9.41 Number of Times that an eNodeB Successfully Measures the Time Difference Among eNodeBs by Using Inter-
eNodeB CEUs...................................................................................................................................................................433
1.9.42 Number of cell received configuration message from centre controller but receive time was expired................ 434
1.9.43 Number of cell received configuration message from centre controller............................................................... 435
1.9.44 Number of Downlink Subframes Without Power on the Power Spectrun of a Cell............................................. 436
1.9.45 Number of Times Dynamic SSAC Is Triggered....................................................................................................437
1.9.46 Number of Times Parameters Related to Dynamic SSAC are Adjusted ..............................................................438
1.9.47 Number of Times Dynamic SSAC Is Canceled.....................................................................................................439
1.9.48 Duration of Dynamic SSAC.................................................................................................................................. 440
1.9.49 Number of Times Preemptions Are Triggered by the User Number Specification...............................................441
1.9.50 Number of Times the Licensed Number of UEs Is Limited..................................................................................442
1.9.51 Number of Successful Preemptions Triggered by the Limitation of the Licensed Number of Ues...................... 444
1.9.52 Number of Times IRC, MRC, or Smart IRC Is Used on the PUSCH................................................................... 446
Issue 03 (2017-03-10) Huawei Proprietary and Confidential iv

BTS3203E
1.9.53 Number of Times IRC or MRC Is Used on the PUCCH.......................................................................................447

1.9.54 Number of Times IRC or MRC Is Used on the PRACH.......................................................................................449
1.9.55 Number of SPID-based Target PLMN Selection Attempts................................................................................... 450
1.9.56 Number of times the eCoordinator triggers interference coordination in high-speed railway scenarios.............. 454
1.9.57 Number of times the eCoordinator stops interference coordination in high-speed railway scenarios.................. 455
1.9.58 Number of successful preferential accesses performed by voice service UEs......................................................456
1.9.59 Number of ABSs in a Cell with eICIC Enabled.................................................................................................... 459
1.9.60 Number of Uplink PDCP SDUs of QCI 1 Discarded Because of SN Disorder or Changes in a Cell.................. 460
1.9.61 UDC Service Throughput or Throughput Rate Measurement...............................................................................461
1.9.62 Average Number of DRBs for UDC Services....................................................................................................... 462
1.9.63 E2E VQI Distribution at Different Speech Quality Levels................................................................................... 463
1.9.64 E2E VQI Distribution of AMR-WB Services at Different Speech Quality Levels.............................................. 465
1.9.65 Total Value of E2E VQIs....................................................................................................................................... 467
1.9.66 Total Value of E2E VQIs of AMR-WB Services.................................................................................................. 468
1.9.67 Total Value of Uplink or Downlink VQIs..............................................................................................................469
1.9.68 Total Value of Uplink or Downlink VQIs of AMR-WB Services.........................................................................470
1.9.69 Number of Times CMAS WRITE-REPLACE WARNING REQUEST Messages Are Received in a Cell......... 472
1.9.70 Number of Times CMAS Warning Notifications Are Requested to Be Broadcast in a Cell................................ 473
1.9.71 Number of Times CMAS KILL REQUEST Messages Are Received in a Cell....................................................475
1.9.72 Number of Times CMAS WARNING REQUEST messages Are Successfully Processed in a Cell....................476
1.9.73 Number of Times CMAS Waring Notifications Are Successfully Broadcast in a Cell........................................ 478
1.9.74 Number of Times CMAS KILL REQUEST Messages Are Successfully Processed in a Cell............................. 479
1.9.75 Number of Successful Responses to UEs' Requests for Configuring DRX Parameters in a Cell.........................481
1.9.76 Number of Successful Responses to UEs' Requests for Restoring DRX Parameters in a Cell.............................482
1.9.77 Number of TTIs in Which Elastic Carrier Takes Effect in a Cell..........................................................................484
1.9.78 Number of Times MLB-Triggered Measurements of WCDMA Frequencies Time Out...................................... 485
1.9.79 Duration in Which an E-UTRAN Cell with Inter-RAT MLB Enabled Is in the High-Load State........................486
1.9.80 Number of TTIs in which some CRSs are not transmitted....................................................................................487
1.9.81 Air Interface Load of a Cell...................................................................................................................................488
1.9.82 Number of Times ETWS Messages Are Sent....................................................................................................... 489
1.10 DRB Measurement (Traffic.DRB.Cell)....................................................................................................................490
1.10.1 Number of DRBs in a Cell.................................................................................................................................... 493
1.10.2 Maximum number of DRBs in a Cell....................................................................................................................496
1.11 Throughput and Data Volume Measurement (Traffic.Thruput.Cell)........................................................................ 499
1.11.1 Maximum Uplink Traffic Volume for PDCP SDUs in a Cell................................................................................519
1.11.2 Maximum Downlink Traffic Volume for PDCP SDUs in a Cell...........................................................................522
1.11.3 Total Bits of Transmitted Signaling SDUs on SRBs at the PDCP Layer in a Cell................................................526
1.11.4 Total Bits of Received Signaling SDUs on SRBs at the PDCP Layer in a Cell.................................................... 527
1.11.5 Total Duration of Uplink or Downlink Data Transmission in a Cell.....................................................................528
1.11.6 Duration of Data Transmission for Services with a Specific QCI in a Cell.......................................................... 530
1.11.7 Total Duration of UE Data Transmission in a Cell................................................................................................534
1.11.8 Uplink Traffic Volume for PDCP PDUs in a Cell................................................................................................. 535
Issue 03 (2017-03-10) Huawei Proprietary and Confidential v

BTS3203E
1.11.9 Receive Duration of Uplink PDCP SDUs in a Cell...............................................................................................540

1.11.10 Downlink Traffic Volume for PDCP SDUs in a Cell.......................................................................................... 545
1.11.11 Transmit Duration of Downlink PDCP SDUs in a Cell.......................................................................................550
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.................................................................................................................................................................. 555
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................................................................................................................................................. 556
1.11.14 Total Duration of Uplink or Downlink Data Transmission in a Cell (with the Precision of 1 ms)..................... 557
1.11.15 Downlink traffic volume sent in the last TTI before the buffer is empty............................................................ 559
1.11.16 Data transmit duration except the last TTI before the downlink buffer is empty................................................563
1.11.17 Traffic Volume of Uplink PDCP SDUs Received in the Last TTI Before the UE Buffer is Empty................... 568
1.11.18 Uplink Data Transmit Duration Except the Last TTI Before the UE Buffer is Empty....................................... 569
1.11.19 Uplink Traffic Volume of PDCP SDUs Scheduled for Small Packets................................................................ 570
1.11.20 Uplink Data Transmission Duration Except that for Small Packets....................................................................571
1.11.21 Uplink Data Transmission Duration Except that for Specific Small Packets Transmitted in the Last TTI........ 572
1.11.22 Uplink Traffic Volume at the PDCP Layer of Specific Small Packets Transmitted in the Last TTI...................573
1.11.23 Total Duration of UE Data Transmission with the precision of 100 milliseconds in a Cell................................574
1.11.24 Total duration of transmission time for services with all the QCI with the precision of 100 milliseconds in a cell
.......................................................................................................................................................................................... 575
1.11.25 Uplink PDCP-layer Traffic Volume of CCUs in a Cell Using the UMTS and LTE Shared Spectrum............... 579
1.11.26 Transmission Duration of Uplink PDCP-layer Data for CCUs in a Cell Using the UMTS and LTE Shared
Spectrum........................................................................................................................................................................... 580
1.11.27 Total Duration of Receiving Data from Cell Edge UEs in the Uplink at the PDCP Layer in a Cell...................581
1.11.28 Total Duration of Sending Data to Cell Edges UEs in the Downlink at the PDCP Layer in a Cell.................... 582
1.11.29 Duration of Downlink PDCP-Layer Data Transmission to CA UEs that Have All SCells Activated for
Downlink LAA CA in a Cell............................................................................................................................................ 583
1.11.30 Downlink PDCP-Layer Traffic Volume of CA UEs that Have All SCells Activated for Downlink LAA CA in a
Cell....................................................................................................................................................................................584
1.11.31 Downlink data transmission duration with converted downlink small-packet transmission duration................ 585
1.11.32 Total Duration of Receiving PDCP PDUs from Joint Reception CEUs in a Cell............................................... 586
1.11.33 Total Duration of Sending PDCP SDUs to Joint Transmission CEUs in a Cell..................................................587
1.11.34 Downlink PDCP-Layer Transmission Duration.................................................................................................. 588
1.12 PDCP Measurement (Traffic.PDCP.Cell).................................................................................................................589
1.12.1 Number of Discarded Downlink PDCP SDUs...................................................................................................... 596
1.12.2 Downlink ROHC Compression Rate of Headers.................................................................................................. 602
1.12.3 Downlink ROHC Compression Rate.....................................................................................................................603
1.12.4 Decompression Failure Rate of Uplink PDCP SDUs After the ROHC................................................................ 604
1.12.5 Number of Transmitted Downlink Traffic PDCP SDUs for DRB Services in a Cell over the Uu Interface........ 605
1.12.6 Uplink ROHC Compression Rate of Headers....................................................................................................... 611
1.12.7 Uplink ROHC Compression Rate..........................................................................................................................612
1.12.8 Number of PDCP-layer Signaling SDUs Sent in the Downlink or Received in the Uplink................................. 613
1.12.9 Number of Bytes of SDUs that a Cell Receives from or Sends to the S-GW....................................................... 614
1.12.10 Number of Bytes of SDUs Transmitted During Inter-eNodeB Handovers......................................................... 615
1.12.11 Number of Uplink VoLTE Packets that Fail to Be Decompressed by ROHC in a Cell...................................... 616
Issue 03 (2017-03-10) Huawei Proprietary and Confidential vi

BTS3203E
1.12.12 Number of Uplink VoLTE Packets that Need to Be Decompressed by ROHC in a Cell.................................... 617
1.13 Paging Measurement (Paging.Cell).......................................................................................................................... 618
1.13.1 Number of Received Paging Messages over the S1 Interface in a Cell................................................................ 620
1.13.2 Number of UEs Contained in Paging Messages Transmitted over the Uu Interface in a Cell..............................621
1.13.3 Number of Successful Paging Responses from the UE in a Cell.......................................................................... 623
1.13.4 Number of Discarded Paging Messages from the MME to UEs in a Cell............................................................ 625
1.13.5 Number of Paging Messages Transmitted Due to System Information Changes..................................................626
1.13.6 Number of Paging Messages Discarded due to Paging Channel Congestion....................................................... 627
1.13.7 Number of Paging Messages Sent Over the Uu Interface in a Cell.......................................................................628
1.14 Security Mode Measurement (SecurMode.Cell)...................................................................................................... 629
1.14.1 Number of Security Mode Setups in a Cell........................................................................................................... 630
1.15 RA Measurement (RA.Cell)..................................................................................................................................... 634
1.15.1 Number of Exceeding-Cell-Radius Random Accesses......................................................................................... 642
1.15.2 Number of Times the Contention Preamble Is Received...................................................................................... 644
1.15.3 Number of Random Access Response Messages that a Cell Sends after Receiving Contention-based Preambles
.......................................................................................................................................................................................... 647
1.15.4 Number of Times the Contention Resolution Message Is Sent After the Contention Preamble Is Received....... 651
1.15.5 Number of Times the Non-Contention-Based Preamble Is Received................................................................... 653
1.15.6 Number of Random Access Response Messages that a Cell Sends after Receiving Non-contention-based
Preambles..........................................................................................................................................................................656
1.15.7 Number of Times the UE Msg3 Response Message Is Received in the Handover-Triggered Non-Contention-
Based RA Procedure.........................................................................................................................................................659
1.15.8 Number of Random Access Procedures................................................................................................................ 660
1.15.9 Number of Times the Non-Contention-based Preamble is Requested.................................................................. 664
1.15.10 Number of Times the Non-Contention-based Preamble is Assigned.................................................................. 666
1.15.11 Number of Times the TA with a Specific Value Range in a UE-Initiated Random Access Procedure in a Cell 667
1.15.12 Number of Times that the Contention-based Preamble in Group A is Discarded based on the TA....................672
1.15.13 Number of Times that the Contention-based Preamble in Group B is Discarded Based on the TA................... 674
1.15.14 Number of Times the UE Msg3 Response Messages are Received in Non-Contention-based Random Access
Procedures........................................................................................................................................................................ 675
1.16 Channel Quality Measurement (ChMeas.Pwr.Cell)................................................................................................. 677
1.16.1 Downlink Transmit Power.....................................................................................................................................702
1.16.2 Interference and Noise Received by Each PRB in a Cell......................................................................................704
1.16.3 Distribution of RSSIs on the PUCCH................................................................................................................... 705
1.16.4 Distribution of RSSIs on the PUSCH....................................................................................................................715
1.16.5 Distribution of INs on the PUSCH........................................................................................................................ 724
1.16.6 Distribution of INs on the PUCCH........................................................................................................................730
1.16.7 Distribution of INs on the PRACH........................................................................................................................737
1.16.8 Distribution of RSRPs on the PUSCH.................................................................................................................. 743
1.16.9 Distribution of RSRPs on the PUCCH.................................................................................................................. 753
1.16.10 Linear Value of Interference Noise Received per PRB....................................................................................... 763
1.17 MIMO Measurement (ChMeas.MIMO.Cell)........................................................................................................... 764
1.17.1 Number of Used Downlink PRBs in MIMO Mode...............................................................................................768
Issue 03 (2017-03-10) Huawei Proprietary and Confidential vii

BTS3203E
1.17.2 Number of TBs Transmitted in Downlink MIMO Mode...................................................................................... 771

1.17.3 Numbers of Bits Transmitted in the Downlink in Different Transmission Modes................................................775
1.17.4 Numbers of Used Downlink PRBs in Different Transmission Modes.................................................................. 777
1.18 CQI Measurement (ChMeas.CQI.Cell).................................................................................................................... 779
1.18.1 Number of Wideband CQI Reports in a Cell.........................................................................................................801
1.18.2 Number of Reports that Contain wideband CQIs for ABSs..................................................................................806
1.18.3 Number of Periodic Wideband CQI Reports in Single-Codeword Transmission in a Cell...................................809
1.18.4 Number of Aperiodic Wideband CQI Reports in Single-Codeword Transmission in a Cell................................ 815
1.18.5 Number of Periodic Wideband CQI Reports for Codeword 0 in Dual-Codeword Transmission in a Cell...........822
1.18.6 Number of Aperiodic Wideband CQI Reports for Codeword 0 in Dual-Codeword Transmission in a Cell........ 829
1.18.7 Number of Periodic Wideband CQI Reports for Codeword 1 in Dual-Codeword Transmission in a Cell...........836
1.18.8 Number of Aperiodic Wideband CQI Reports for Codeword 1 in Dual-Codeword Transmission in a Cell........ 843
1.18.9 Number of Times a UE Reports a Rank Value in a Cell........................................................................................850
1.18.10 wideband CQIs reported by CEUs in a Cell........................................................................................................851
1.18.11 Number of Wideband CQI Reports Sent by Downlink-256QAM-enabled UEs in a Cell.................................. 853
1.19 MCS Measurement (ChMeas.MCS.Cell)................................................................................................................. 860
1.19.1 Number of Times an MCS Index Is Scheduled on the PUSCH............................................................................ 886
1.19.2 Number of Times a Specific MCS Index Is Scheduled on the PDSCH................................................................ 897
1.19.3 Number of PRBs on the PUSCH Using a Specified MCS for Scheduling in a Cell.............................................908
1.19.4 Number of PRBs on the PDSCH Using a Specific MCS index for Scheduling in a Cell..................................... 917
1.20 PRB Measurement (ChMeas.PRB.Cell)...................................................................................................................965
1.20.1 Number of Used Uplink PRBs.............................................................................................................................. 980
1.20.2 Number of Used Downlink PRBs......................................................................................................................... 987
1.20.3 Number of Used PUCCH PRBs............................................................................................................................ 991
1.20.4 Number of OFDM Symbols Occupied by the PDCCH.........................................................................................992
1.20.5 Number of PDCCH CCEs used in a cell............................................................................................................... 994
1.20.6 Average Number of PRBs Occupied by CA UEs in a Cell................................................................................. 1000
1.20.7 Average Number of Available PRBs in a Cell.....................................................................................................1001
1.20.8 Average Number of PRBs Used by ICIC CEUs in a Cell................................................................................... 1002
1.20.9 Average Number of PRBs Allocated for Frequency Selective Scheduling.........................................................1003
1.20.10 Average Number of PRBs Allocated for Uplink Pre-scheduling...................................................................... 1004
1.20.11 Number of Times of DTX for PDCCH Resource Allocation with a Specific Aggregation Level in a Cell..... 1005
1.20.12 Number of Times of Successful PDCCH Resource Allocations with a Specific Aggregation Level...............1007
1.20.13 Average Number of PRBs Used on an ABS by UEs in a Cell that Are Close to the Border with the Other Type
of Cells and Support eICIC in a Heterogeneous Network..............................................................................................1010
1.20.14 Average Number of PRBs Used on an ABS by UEs in a Cell that Are Close to the Border with the Other Type
of Cells and Support eICIC in a Heterogeneous Network..............................................................................................1011
1.20.15 Number of Times of DMRS TA Scheduling in a cell........................................................................................1012
1.20.16 Number of Times of DMRS TA Scheduling in a cell........................................................................................1013
1.20.17 Number of CCE Allocation Failures in a Cell...................................................................................................1014
1.20.18 Number of CCE Allocation Failures in a Cell...................................................................................................1015
1.20.19 PUSCH PRB Usage Distribution...................................................................................................................... 1016
1.20.20 Average Number of PRBs Allocated for Uplink TA Measurement.................................................................. 1020
Issue 03 (2017-03-10) Huawei Proprietary and Confidential viii

BTS3203E
1.20.21 PDSCH PRB Usage Distribution...................................................................................................................... 1021

1.20.22 Number of Downlink PRBs Occupied by CA UEs in the Relaxed-Backhaul-based Inter-eNodeB CA State. 1025
1.20.23 Number of PRBs of the Downlink Edge Band in Adaptive ICIC..................................................................... 1026
1.20.24 Average Number of PRBs Used for Inter-eNodeB DL CoMP Scheduling in a Cell........................................ 1027
1.20.25 Number of Used Uplink PRBs on the PUSCH on the UMTS and LTE Shared Spectrum in a Cell.................1028
1.20.26 Number of Times an eNodeB Successfully Allocates the PDCCHs with a Specified Aggregation Level for
Uplink Scheduling.......................................................................................................................................................... 1029
1.20.27 Number of Times of Successful ePDCCH Resource Allocations with a Specific Aggregation Level............. 1031
1.20.28 Number of Times DTX Is Detected for Downlink ePDCCH Resource Allocations with a Specific Aggregation
Level............................................................................................................................................................................... 1035
1.20.29 Number of PDCCH eCCEs Used in the Cell.................................................................................................... 1038
1.20.30 Average Number of PRBs Occupied by CEUs in a Cell................................................................................... 1039
1.20.31 Average Number of PRBs Used by the PUSCH for Joint Reception CEUs in a Cell.......................................1040
1.20.32 Average Number of PRBs Used by the PDSCH for Joint Transmission CEUs in a Cell................................. 1041
1.20.33 Number of Available PDCCH CCEs in a Cell.................................................................................................. 1042
1.20.34 Number of Available PDCCH CCEs in a Cell.................................................................................................. 1043
1.21 MAC Measurement (Traffic.MAC.Cell)................................................................................................................ 1044
1.21.1 Total Number of Bits of TBs Transmitted on the BCH....................................................................................... 1063
1.21.2 Total Number of Bits of TBs Transmitted on the PCH....................................................................................... 1064
1.21.3 Number of TBs Initially Transmitted on the Downlink SCH..............................................................................1065
1.21.4 Number of Bits of TBs Initially Transmitted on the Downlink SCH..................................................................1068
1.21.5 Number of TBs Retransmitted on the Downlink SCH........................................................................................ 1070
1.21.6 Number of Bits of TBs Retransmitted on the Downlink SCH............................................................................ 1072
1.21.7 Number of TBs Initially Transmitted on the Uplink SCH...................................................................................1075
1.21.8 Number of bits of TBs Initially Transmitted on the Uplink SCH....................................................................... 1077
1.21.9 Number of TBs Retransmitted on the Uplink SCH............................................................................................. 1078
1.21.10 Number of bits of TBs Retransmitted on the Uplink SCH................................................................................1080
1.21.11 Number of Downlink Error TBs After Initial Transmission............................................................................. 1082
1.21.12 Number of Downlink Error TBs After the Maximum Number of Retransmissions Is Reached...................... 1086
1.21.13 Number of Uplink Error TBs After Initial Transmission.................................................................................. 1088
1.21.14 Number of Uplink Error TBs After the Maximum Number of Retransmissions Is Reached........................... 1091
1.21.15 Maximum Traffic Volume for MAC TBs in a Cell........................................................................................... 1093
1.21.16 Number of Bits of TBs Initially Transmitted on the Downlink SCH in the Shared Spectrum......................... 1094
1.21.17 Number of TBs Initially Transmitted on the Downlink SCH in the Shared Spectrum..................................... 1095
1.21.18 Number of Bits of TBs Failed to be Transmitted During Initial Transmission on the Downlink SCH in the
Shared Spectrum.............................................................................................................................................................1097
1.21.19 Number of TBs Failed to be Transmitted During Initial Transmission on the Downlink SCH in the Shared
Spectrum......................................................................................................................................................................... 1099
1.21.20 Duration of Downlink Scheduling in the Shared Spectrum.............................................................................. 1100
1.21.21 Duration of Downlink Scheduling in the Dedicated Spectrum......................................................................... 1102
1.21.22 Average Number of Used Downlink PRBs in the Shared Spectrum................................................................. 1103
1.21.23 Distribution of Packet Transmission Intervals for UEs in a Cell.......................................................................1105
1.21.24 Number of Error TBs After the Maximum Number of Retransmissions Is Reached for UEs with Poor Channel
Quality.............................................................................................................................................................................1110
Issue 03 (2017-03-10) Huawei Proprietary and Confidential ix

BTS3203E
1.21.25 Number Of TBs Initially Transmitted for UEs with Poor Channel Quality...................................................... 1111
1.21.26 Number of Times that UEs are Scheduled in a Cell in the Uplink or Downlink...............................................1112
1.21.27 Number of Handover Command TBs Initially Transmitted on the Downlink SCH......................................... 1114
1.21.28 Number of Downlink Error TBs for Handover Commands After Initial Transmission.................................... 1115
1.21.29 Number of Downlink Error TBs for Handover Commands After the Maximum Number of Retransmissions is
Reached...........................................................................................................................................................................1117
1.21.30 Number of Voice Service TBs Initially Transmitted on the Uplink SCH..........................................................1118
1.21.31 Number of Voice Service TBs Retransmitted on the Uplink SCH.................................................................... 1120
1.21.32 Number of Voice Service TBs with Initial Transmission Failures on the Uplink SCH.....................................1122
1.21.33 Number of Voice Service TBs Initially Transmitted on the Downlink SCH.....................................................1124
1.21.34 Number of Voice Service TBs Retransmitted on the Downlink SCH............................................................... 1126
1.21.35 Number of Voice Service TBs with Initial Transmission Failures on the Downlink SCH................................1128
1.21.36 Number of Service Data TBs Initially Transmitted on the Downlink SCH...................................................... 1130
1.21.37 Number of Service Data TBs Retransmitted on the Downlink SCH.................................................................1132
1.21.38 Number of Downlink Error Service Data TBs After Initial Transmission........................................................ 1134
1.21.39 Number of Downlink Error Service Data TBs After the Maximum Number of Retransmissions Is Reached. 1136
1.21.40 Number of Bits of Downlink TBs that Fail to Be Transmitted After the Maximum Number of Retransmissions
Is Reached.......................................................................................................................................................................1138
1.21.41 Number of TBs initially transmitted for cell edge UEs on the uplink SCH...................................................... 1140
1.21.42 Number of uplink erroneous TBs after initial transmission for cell edge Ues.................................................. 1141
1.21.43 L.Traffic.UL.SCH.ErrTB.Rbler.BorderUE........................................................................................................1142
1.21.44 Number of TBs Initially Transmitted to Cell Edge UEs on the Downlink SCH...............................................1143
1.21.45 Number of Downlink Erroneous TBs After Initial Transmission to Cell Edge Ues......................................... 1144
1.21.46 Number of Downlink Erroneous TBs After the Maximum number of Retransmissions to Cell Edge UEs Is
Reached...........................................................................................................................................................................1145
1.21.47 Number of QCI-2 Service TBs Initially Transmitted on the Uplink SCH........................................................ 1146
1.21.48 Number of QCI-2 Service TBs Initially Transmitted on the Uplink SCH........................................................ 1148
1.21.49 Number of QCI-2 Service TBs Initially Transmitted on the Downlink SCH Using QPSK..............................1150
1.21.50 Number of QCI-2 Service TBs Retransmitted on the Downlink SCH Using QPSK........................................ 1152
1.22 Cell User Quantity Measurement (Traffic.User.Cell).............................................................................................1153
1.22.1 Number of Users in a Cell................................................................................................................................... 1169
1.22.2 Number of ICIC Cell Edge Users in a Cell......................................................................................................... 1170
1.22.3 Number of UEs with Data in the Uplink Buffer.................................................................................................. 1172
1.22.4 Number of UEs with Data in the Downlink Buffer............................................................................................. 1174
1.22.5 Number of UL Synchronized Users in a Cell...................................................................................................... 1175
1.22.6 Number of UEs Transmitting or Receiving Data in a Cell..................................................................................1176
1.22.7 Number of UL CoMP UEs in a Cell....................................................................................................................1177
1.22.8 Number of CA UEs in a Cell............................................................................................................................... 1180
1.22.9 Average Number of Activated UEs with a Specific QCI in the Uplink Buffer................................................... 1181
1.22.10 Average Number of Activated UEs with a Specific QCI in the Downlink Buffer............................................ 1185
1.22.11 Number of UEs Configured with SRS Resources in a Cell...............................................................................1188
1.22.12 Number of UEs on Which TTI Bundling Takes Effect in a Cell.......................................................................1190
1.22.13 Number of UEs on Which ROHC Takes Effect in a Cell..................................................................................1191
Issue 03 (2017-03-10) Huawei Proprietary and Confidential x

BTS3203E
1.22.14 Number of UEs on Which DRX Takes Effect in a Cell.................................................................................... 1192

1.22.15 Number of Activated UEs in the Downlink in a Cell........................................................................................ 1193
1.22.16 Number of Activated UEs in the Uplink in a Cell.............................................................................................1194
1.22.17 Number of Activated UEs in a Cell................................................................................................................... 1196
1.22.18 Number of eICIC-Capable UEs in a Cell.......................................................................................................... 1197
1.22.19 Number of UEs in a Cell that are Close to the Border with the Other Type of Cells in a HetNet.................... 1198
1.22.20 Number of eICIC-Capable UEs in a Cell that are Close to the Border with the Other Type of Cells in a HetNet
........................................................................................................................................................................................ 1199
1.22.21 Number of Privileged UEs in a Cell.................................................................................................................. 1200
1.22.22 Number of UEs Whose Uplink Timing Offsets are Measured Based on the PUCCH...................................... 1202
1.22.23 Maximum Number of Activated UEs with a QCI in the Downlink Buffer.......................................................1203
1.22.24 Maximum Number of Activated UEs with a QCI in the Uplink Buffer........................................................... 1207
1.22.25 Number of Scheduled UEs per TTI in the Downlink in a Cell......................................................................... 1210
1.22.26 Number of Scheduled UEs per TTI in the Uplink in a Cell.............................................................................. 1211
1.22.27 Maximum Total Number of Scheduled UEs per TTI in the Uplink and Downlink in a Cell............................1213
1.22.28 Licensed Number of UEs in RRC_CONNECTED Mode.................................................................................1214
1.22.29 Number of UEs running unlimited services...................................................................................................... 1215
1.22.30 Average and Maximum Numbers of Activated CA UEs That Use the Local Cell As Their Scell................... 1216
1.22.31 Number of Times the UE Quantity in a Cell Falls Within Different Ranges.................................................... 1217
1.22.32 Number of VoIP UEs in a Cell.......................................................................................................................... 1221
1.22.33 Number of UEs that apply TM9 in a cell.......................................................................................................... 1222
1.22.34 Number of CA UEs in the Relaxed-Backhaul-based Inter-eNodeB CA State.................................................. 1223
1.22.35 Number of UEs that Are Configured with a GBR and Whose Throughput Falls Within Different Ranges.....1225
1.22.36 Number of FeICIC-Capable UEs in a Cell........................................................................................................ 1228
1.22.37 Number of FeICIC-capable UEs in a Cell that Are Close to the Border with the Other Type of Cells in a HetNet
........................................................................................................................................................................................ 1229
1.22.38 Number of CEUs in Adaptive ICIC in a Cell.................................................................................................... 1230
1.22.39 Average number of UEs for Which Coordinated Uplink AMC Is Used in a Cell.............................................1231
1.22.40 Average Number of Inter-eNodeB DL CoMP UEs in a Cell............................................................................ 1232
1.22.41 Average Number of UEs Using the UMTS and LTE Shared Spectrum in a Cell............................................. 1232
1.22.42 Number of UEs with Service Data to Be Transmitted in a Cell........................................................................ 1233
1.22.43 Number of Times the Number of UEs in RRC_CONNECTED Mode Is Not Zero..........................................1234
1.22.44 Number of UEs Configured with Out-of-Synchronization DRX Parameters in a Cell.....................................1235
1.22.45 Number of Dedicated Service Users..................................................................................................................1236
1.22.46 Number of CEUs in a Cell.................................................................................................................................1237
1.22.47 Average Number of UEs that Apply Requested DRX Parameters in a Cell..................................................... 1239
1.22.48 Average Number of NAICS-Capable UEs in a Cell..........................................................................................1240
1.22.49 Average Number of CRS-IC-Capable UEs in a Cell.........................................................................................1241
1.22.50 Number of UEs Performing MCPTT Voice Services in a Cell......................................................................... 1242
1.22.51 Average Number and Maximum Number of UEs Supporting Specific-UE Device-pipe Synergy in a Cell.... 1243
1.23 Outgoing Inter-RAT Handover Measurement (HO.IRAT.Out.Cell).......................................................................1244
1.23.1 Number of Inter-RAT Handover Attempts from E-UTRAN to CDMA2000 Network.......................................1283
1.23.2 Number of Inter-RAT Handovers Executions from E-UTRAN to CDMA2000 Network.................................. 1285
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xi

BTS3203E
1.23.3 Number of Successful Inter-RAT Handovers from E-UTRAN to CDMA2000 Network...................................1286

1.23.4 Number of Inter-RAT Handover Attempts from E-UTRAN to WCDMA Network...........................................1288
1.23.5 Number of Inter-RAT Handovers Executions from E-UTRAN to WCDMA Network...................................... 1289
1.23.6 Number of Successful Inter-RAT Handovers from E-UTRAN to WCDMA Network.......................................1291
1.23.7 Number of Inter-RAT Handover Attempts from E-UTRAN to GERAN............................................................1292
1.23.8 Number of Inter-RAT Handovers Executions from E-UTRAN to GERAN....................................................... 1294
1.23.9 Number of Successful Inter-RAT Handovers from E-UTRAN to GERAN........................................................1295
1.23.10 Number of Inter-RAT Handover Attempts from E-UTRAN to TD-SCDMA Network....................................1297
1.23.11 Number of Inter-RAT Handovers Executions from E-UTRAN to TD-SCDMA Network............................... 1298
1.23.12 Number of Successful Inter-RAT Handovers from E-UTRAN to TD-SCDMA Network................................1300
1.23.13 Number of Inter-RAT Handover Failures for Different Causes........................................................................ 1301
1.23.14 Number of Inter-RAT Blind Handover Attempts from E-UTRAN to Another System....................................1309
1.23.15 Number of Blind Handover Executions from E-UTRAN to Another System.................................................. 1311
1.23.16 Number of successful Inter-RAT Blind Handovers from E-UTRAN to Another System ............................... 1313
1.23.17 Number of Indicators for CSFB to Another System......................................................................................... 1316
1.23.18 Number of CSFB Responses to MMEs............................................................................................................. 1319
1.23.19 Number of Procedures for CSFB to Another System........................................................................................1322
1.23.20 Number of Inter-RAT Redirection Preparations from E-UTRAN to Another System..................................... 1342
1.23.21 Number of Inter-RAT Redirections from E-UTRAN to Another System......................................................... 1346
1.23.22 Number of Inter-RAT Handover Attempts from E-UTRAN to WCDMA network for SRVCC...................... 1349
1.23.23 Number of Inter-RAT Handover Executions from E-UTRAN to WCDMA network for SRVCC................... 1351
1.23.24 Number of Successful Inter-RAT Handovers from E-UTRAN to WCDMA Network for SRVCC................. 1352
1.23.25 Number of Inter-RAT Handover Attempts from E-UTRAN to GERAN for SRVCC...................................... 1354
1.23.26 Number of Inter-RAT Handover Executions from E-UTRAN to GERAN for SRVCC................................... 1355
1.23.27 Number of Successful Inter-RAT Handovers from E-UTRAN to GERAN for SRVCC.................................. 1357
1.23.28 Number of Inter-RAT Handover Attempts from E-UTRAN to TD-SCDMA Network for SRVCC................ 1358
1.23.29 Number of Inter-RAT Handover Executions from E-UTRAN to TD-SCDMA Network for SRVCC............. 1360
1.23.30 Number of Successful Inter-RAT Handovers from E-UTRAN to TD-SCDMA network for SRVCC............. 1361
1.23.31 Number of LCS-triggered CS Fallback Indicators Received by the eNodeB................................................... 1363
1.23.32 Number of Responses Sent from the eNodeB to MMEs for CSFB Triggered by LCS.................................... 1365
1.23.33 Number of CCO Executions from E-UTRAN to GERAN................................................................................1366
1.23.34 Number of Inter-RAT Handover Initiation Failures Because the Adjacent Cell is not the NRT of the Source Cell
........................................................................................................................................................................................ 1368
1.23.35 Number of CSFB Preparation Failures Because of Process Conflict................................................................1372
1.23.36 Number of Handover Preparation Attempts from E-UTRAN to WCDMA Network Triggered Because of High
Load................................................................................................................................................................................ 1374
1.23.37 Number of Inter-RAT Handover Execution Attempts Triggered Because of High Load................................. 1376
1.23.38 Number of Successful Inter-RAT Handover Executions Triggered Because of High Load............................. 1378
1.23.39 Number of Redirections from E-UTRAN to WCDMA Network Triggered Because of High Load................1380
1.23.40 Number of Inter-RAT Handover Attempts from E-UTRAN to WCDMA Network Triggered for UEs to Go back
to the HPLMN................................................................................................................................................................ 1381
1.23.41 Number of Inter-RAT Handover Executions from E-UTRAN to WCDMA Network Triggered for UEs to Go
back to the HPLMN........................................................................................................................................................1383
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xii

BTS3203E
1.23.42 Number of Inter-RAT Handovers from E-UTRAN to WCDMA Network Triggered for UEs to Go back to the
HPLMN.......................................................................................................................................................................... 1385
1.23.43 Number of Inter-RAT Handover Executions from E-UTRAN to WCDMA Network Triggered for UEs That Do
not Transmit or Receive Data......................................................................................................................................... 1387
1.23.44 Number of Successful Inter-RAT Handovers from E-UTRAN to WCDMA Network Triggered for UEs That Do
not Transmit or Receive Data......................................................................................................................................... 1389
1.23.45 Number of LCS-based Inter-RAT Handover Executions for SRVCC...............................................................1391
1.23.46 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During Inter-RAT
Handover Executions from E-UTRAN to Another System........................................................................................... 1396
Handover Executions from E-UTRAN to Another System for SRVCC........................................................................ 1400
1.23.48 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.......................................................................... 1402
1.23.49 Number of Inter-RAT Handover Attempts from E-UTRAN to CDMA2000 HRPD Network......................... 1406
1.23.50 Number of Inter-RAT Handover Executions from E-UTRAN to CDMA2000 HRPD Network......................1408
1.23.51 Number of Successful Inter-RAT Handovers from E-UTRAN to CDMA2000 HRPD Network..................... 1409
1.23.52 Handover Time from E-UTRAN to Another RAT............................................................................................ 1411
1.23.53 Number of Coverage-based Inter-RAT Handover Attempts from E-UTRAN to Another System................... 1414
1.23.54 Number of Coverage-based Inter-RAT Handover Executions from E-UTRAN to Another System................1416
1.23.55 Number of Successful Coverage-based Inter-RAT Handovers from E-UTRAN to Another System............... 1418
1.23.56 Number of Coverage-based Inter-RAT Redirections from E-UTRAN to Another System.............................. 1420
1.23.57 Number of SPID-based Inter-RAT Redirections Back to the HPLMN............................................................. 1422
1.23.58 Number of Successful Service-based Inter-RAT Outgoing Handover Attempts from E-UTRAN to Another
System............................................................................................................................................................................ 1423
1.23.59 Number of Service-based Inter-RAT Outgoing Handover Executions from E-UTRAN to Another System... 1425
1.23.60 Number of Successful Service-based Inter-RAT Outgoing Handovers from E-UTRAN to Another System.. 1427
1.23.61 Number of Service-based Inter-RAT Redirections from E-UTRAN to Another System................................. 1429
1.23.62 Number of UL-Quality-based Outgoing Handover Attempts from E-UTRAN to Another System.................1430
1.23.63 Number of UL-Quality-based Outgoing Handover Executions from E-UTRAN to Another System..............1432
1.23.64 Number of Successful UL-Quality-based Outgoing Handovers from E-UTRAN to Another System.............1434
1.23.65 Number of UL-Quality-based Inter-RAT Redirections from E-UTRAN to Another System...........................1436
1.23.66 Number of Inter-RAT CSFB-based Handover Failures for Different Causes................................................... 1438
1.23.67 Number of Inter-RAT SRVCC-based Handover Failures for Different Causes................................................ 1443
1.23.68 Number of Outgoing CS-Only SRVCC-based Handover Attempts from E-UTRAN to WCDMA Network...1450
1.23.69 Number of Outgoing CS-Only SRVCC-based Handover Executions from E-UTRAN to WCDMA Network
........................................................................................................................................................................................ 1452
1.23.70 Number of Successful Outgoing CS-Only SRVCC-based Handovers from E-UTRAN to WCDMA Network
........................................................................................................................................................................................ 1453
1.23.71 Number of Outgoing CS-Only SRVCC-based Handover Attempts from E-UTRAN to TD-SCDMA Network
........................................................................................................................................................................................ 1455
1.23.72 Number of Outgoing CS-Only SRVCC-based Handover Executions from E-UTRAN to TD-SCDMA Network
........................................................................................................................................................................................ 1456
1.23.73 Number of Successful Outgoing CS-Only SRVCC-based Handovers from E-UTRAN to TD-SCDMA Network
........................................................................................................................................................................................ 1458
1.23.74 Number of Outgoing CS-Only SRVCC-based Handover Attempts from E-UTRAN to GERAN....................1459
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xiii

BTS3203E
1.23.75 Number of Outgoing CS-Only SRVCC-based Handover Executions from E-UTRAN to GERAN................ 1461
1.23.76 Number of Successful Outgoing CS-Only SRVCC-based Handovers from E-UTRAN to GERAN................1462
1.23.77 Number of SRVCC-based Outgoing Handover Attempts from E-UTRAN to WCDMA Network for Ultra-Flash
CSFB.............................................................................................................................................................................. 1464
1.23.78 Number of SRVCC-based Outgoing Handover Executions from E-UTRAN to WCDMA Network for Ultra-
Flash CSFB.....................................................................................................................................................................1466
1.23.79 Number of Successful SRVCC-based Outgoing Handovers from E-UTRAN to WCDMA Network for Ultra-
Flash CSFB.....................................................................................................................................................................1468
1.23.80 Number of Responses with Abnormal Causes Received by the eNodeB from the MME During Inter-RAT Blind
1.23.81 Number of Ultra-Flash CSFB Attempts............................................................................................................ 1472
1.23.82 Number of Ultra-Flash CSFB Executions......................................................................................................... 1474
1.23.83 Number of Successful Ultra-Flash CSFBs........................................................................................................ 1475
1.23.84 Number of Abnormal Responses from the MME During Ultra-Flash CSFB to GERAN................................ 1477
1.24 Incoming Inter-RAT Handover Measurement (HO.IRAT.In.Cell)......................................................................... 1479
1.24.1 Number of Inter-RAT Handover Attempts from GERAN to E-UTRAN............................................................1484
1.24.2 Number of Inter-RAT Handover Preparation from GERAN to E-UTRAN........................................................ 1486
1.24.3 Number of Successful Inter-RAT Handovers from GERAN to E-UTRAN........................................................1487
1.24.4 Number of Inter-RAT inter-RAT Handover Preparation Failures for Different Causes in a Cell....................... 1489
1.24.5 Number of Inter-RAT Handover Attempts from TD-SCDMA Network to E-UTRAN......................................1497
1.24.6 Number of Inter-RAT Handover Preparation from TD-SCDMA Network to E-UTRAN.................................. 1499
1.24.7 Number of Successful Inter-RAT Handovers from TD-SCDMA Network to E-UTRAN..................................1500
1.24.8 Number of Inter-RAT Handover Attempts from WCDMA Network to E-UTRAN...........................................1502
1.24.9 Number of Inter-RAT Handover Preparation from WCDMA Network to E-UTRAN....................................... 1503
1.24.10 Number of Successful Inter-RAT Handovers from WCDMA Network to E-UTRAN.....................................1505
1.25 Outgoing Intra-RAT Handover Measurement (HO.eRAN.Out.Cell).....................................................................1506
1.25.1 Number of Inter-eNodeB Outgoing Handover Attempts in a Cell......................................................................1530
1.25.2 Number of Inter-eNodeB Outgoing Handovers Executions in a Cell................................................................. 1534
1.25.3 Number of Successful Inter-eNodeB Outgoing Handovers in a Cell..................................................................1538
1.25.4 Number of Outgoing Blind Handover Attempts in a Cell...................................................................................1545
1.25.5 Number of Outgoing Blind Handovers Executions in a Cell.............................................................................. 1548
1.25.6 Number of Successful Outgoing Blind Handovers in a Cell...............................................................................1551
1.25.7 Number of Outgoing Handover Failures for Different Causes in a Cell............................................................. 1557
1.25.8 Number of Intra-RAT Redirections..................................................................................................................... 1571
1.25.9 Number of Intra-RAT Handover Initiation Failures Because the Adjacent Cell is not on the NRT of the Source
Cell..................................................................................................................................................................................1575
1.25.10 Number of Load-based Inter-Frequency Handover Preparation Attempts........................................................1578
1.25.11 Number of Load-based Inter-Frequency Handover Execution Attempts.......................................................... 1581
1.25.12 Number of Successful Load-based Inter-Frequency Handover Executions......................................................1583
1.25.13 Number of Inter-Frequency Outgoing Handover Attempts Triggered for UEs to Go back to the HPLMN.....1589
1.25.14 Number of Inter-Frequency Outgoing Handover Executions Triggered for UEs to Go back to the HPLMN..1591
1.25.15 Number of Successful Inter-Frequency Outgoing Handovers Triggered for UEs to Go Back to the HPLMN 1593
1.25.16 Number of Intra-Frequency Handover Execution Attempts Triggered for UEs that do not transmit or receive
data..................................................................................................................................................................................1599
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xiv

BTS3203E
1.25.17 Number of Successful Intra-Frequency Handover Executions Triggered for UEs that do not transmit or receive
data..................................................................................................................................................................................1601
1.25.18 Number of Inter-Frequency Handover Execution Attempts Triggered for UEs That Do not Transmit or Receive
Data.................................................................................................................................................................................1607
1.25.19 Number of Successful Inter-Frequency Handover Executions Triggered for UEs That Do not Transmit or
Receive Data...................................................................................................................................................................1609
1.25.20 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During S1-based
Outgoing Handover Executions......................................................................................................................................1615
1.25.21 Number of Successful Inter-eNodeB Outgoing Handovers Where RRC Connections Are Reestablished to the
Source Cell for UEs in a Cell......................................................................................................................................... 1618
1.25.22 Number of Successful Blind Outgoing Handovers Where RRC Connections Are Reestablished to the Source
Cell for UEs in a cell...................................................................................................................................................... 1622
1.25.23 Number of Coverage-based Inter-Frequency Handover Preparation Attempts................................................ 1626
1.25.24 Number of Coverage-based Inter-Frequency Handover Execution Attempts...................................................1628
1.25.25 Number of Successful Coverage-based Inter-Frequency Handovers................................................................ 1630
1.25.26 Inter-eNodeB Handover Time in a Cell.............................................................................................................1636
1.25.27 Number of Service-based Inter-Frequency Handover Preparation Attempts....................................................1639
1.25.28 Number of Service-based Inter-Frequency Handover Execution Attempts...................................................... 1642
1.25.29 Number of Successful Service-based Inter-Frequency Handover Executions.................................................. 1644
1.25.30 Number of Frequency-Priority-based Inter-Frequency Handover Preparation Attempts................................. 1649
1.25.31 Number of Frequency-Priority-based Inter-Frequency Handover Execution Attempts....................................1651
1.25.32 Number of Successful Frequency-Priority-based Inter-Frequency Handover Executions................................1653
1.25.33 Number of Inter-eNodeB Outgoing Handover Attempts for UEs Performing Voice Services in a Cell.......... 1659
1.25.34 Number of Inter-eNodeB Outgoing Handover Executions for UEs Performing Voice Services in a Cell....... 1662
1.25.35 Number of Successful Inter-eNodeB Outgoing Handovers for UEs Performing Voice Services in a Cell...... 1665
1.25.36 Number of Inter-Duplex-Mode Handover Execution Attempts Triggered for UEs that Do Not Transmit or
Receive Data...................................................................................................................................................................1672
1.25.37 Number of Successful Inter-Duplex-Mode Handover Executions Triggered for UEs that Do Not Transmit or
Receive Data...................................................................................................................................................................1674
1.25.38 Number of Load-based Inter-Duplex-Mode Handover Preparation Attempts.................................................. 1680
1.25.39 Number of Load-based Inter-Duplex-Mode Handover Execution Attempts.................................................... 1682
1.25.40 Number of Successful Load-based Inter-Duplex-Mode Handover Executions................................................ 1685
1.25.41 Number of Coverage-based Inter-Duplex-Mode Handover Preparation Attempts........................................... 1692
1.25.42 Number of Coverage-based Inter-Duplex-Mode Handover Execution Attempts............................................. 1694
1.25.43 Number of Successful Coverage-based Inter-Duplex-Mode Handover Executions......................................... 1696
1.25.44 Number of SPID-based Inter-Duplex-Mode Outgoing Handover Attempts back to the HPLMN................... 1702
1.25.45 Number of SPID-based Inter-Duplex-Mode Outgoing Handover Executions back to the HPLMN................ 1704
1.25.46 Number of Successful SPID-based Inter-Duplex-Mode Outgoing Handovers back to the HPLMN............... 1707
1.25.47 Number of UL-Quality-based Inter-Frequency Handover Preparation Attempts............................................. 1714
1.25.48 Number of UL-Quality-based Inter-Duplex-Mode Handover Preparation Attempts........................................1716
1.25.49 Number of UL-Quality-based Inter-Frequency Handover Execution Attempts............................................... 1718
1.25.50 Number of UL-Quality-based Inter-Duplex-Mode Handover Execution Attempts..........................................1720
1.25.51 Number of Successful UL-Quality-based Inter-Frequency Handover Executions........................................... 1722
1.25.52 Number of Successful UL-Quality-based Inter-Duplex-Mode Handover Executions......................................1728
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xv

BTS3203E
1.25.53 Number of Service-Based Inter-Duplex-Mode Handover Preparation Attempts..............................................1734

1.25.54 Number of Service-based Inter-Duplex-Mode Handover Execution Attempts................................................ 1736
1.25.55 Number of Successful Service-based Inter-Duplex-Mode Handover Executions............................................ 1738
1.25.56 Number of Frequency-Priority-based Inter-Duplex-Mode Handover Preparation Attempts............................1744
1.25.57 Number of Frequency-Priority-based Inter-Duplex-Mode Handover Execution Attempts.............................. 1746
1.25.58 Number of Successful Frequency-Priority-based Inter-Duplex-Mode Handover Executions.......................... 1748
1.25.59 Number of Responses With Abnormal Causes Received by the eNodeB from the MME During S1-based
Outgoing Blind Handover Executions............................................................................................................................1754
1.25.60 Number of Inter-Frequency Outgoing Handover Preparation Attempts Triggered by Interests in MBMS
Services...........................................................................................................................................................................1756
1.25.61 Number of Inter-Frequency Outgoing Handover Execution Attempts Triggered by Interests in MBMS Services
........................................................................................................................................................................................ 1758
1.25.62 Number of Successful Inter-Frequency Handovers Triggered by Interests in MBMS Services.......................1761
1.25.63 Number of Inter-Duplex-Mode Outgoing Handover Preparation Attempts Triggered by Interests in MBMS
Services...........................................................................................................................................................................1768
1.25.64 Number of Inter-Duplex-Mode Outgoing Handover Execution Attempts Triggered by Interests in MBMS
Services...........................................................................................................................................................................1770
1.25.65 Number of Successful Inter-Duplex-Mode Handovers Triggered by Interests in MBMS Services................. 1773
1.25.66 Number of Inter-Frequency Outgoing Handover Preparation Attempts of Low-Speed UEs in a Cell............. 1780
1.25.67 Number of Inter-Frequency Outgoing Handover Execution Attempts of Low-Speed UEs in a Cell............... 1783
1.25.68 Number of Successful Inter-Frequency Outgoing Handover Executions of Low-Speed UEs in a Cell........... 1786
1.25.69 Number of Times when the eNodeB receives Messages from the MME with Abnormal Reasons During Inter-
Frequency Outgoing Handover Executions of Low-Speed UEs.................................................................................... 1795
1.25.70 Number of Intra-eNodeB Inter-SFN-Cell Outgoing Handover Attempts in a Super Combined Cell...............1797
1.25.71 Number of Successful Intra-eNodeB Inter-SFN-Cell Outgoing Handovers in a Super Combined Cell...........1798
1.25.72 Number of Inter-eNodeB Inter-SFN-Cell Outgoing Handover Attempts in a Super Combined Cell...............1800
1.25.73 Number of Successful Inter-eNodeB Inter-SFN-Cell Outgoing Handovers in a Super Combined Cell...........1802
1.25.74 Number of Inter-duplex-mode Handover Preparation Attempts Triggered by MLB Based on the Number of
Low-Efficiency UEs....................................................................................................................................................... 1804
1.25.75 Number of Inter-duplex-mode Handover Execution Attempts Triggered by MLB Based on the Number of Low-
Efficiency UEs................................................................................................................................................................1807
1.25.76 Number of Successful Inter-duplex-mode Handovers Triggered by MLB Based on the Number of Low-
Efficiency UEs................................................................................................................................................................1809
1.25.77 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.... 1816
1.25.78 Number of Inter-eNodeB Inter-SFN-Cell outgoing Handover Executions in a Super Combined Cell............ 1817
1.25.79 Number of Service-triggered Inter-duplex-mode Measurement Expiration Times...........................................1819
1.25.80 Number of unsuccessful service-triggered inter-duplex-mode handover initiation request attempts due to lack of
neighboring relationship between two cells................................................................................................................... 1820
1.26 Incoming Intra-RAT Handover Measurement (HO.eRAN.In.Cell)....................................................................... 1821
1.26.1 Number of Inter-eNodeB Incoming Handover Attempts in a Cell......................................................................1835
1.26.2 Number of Inter-eNodeB Incoming Handovers Executions in a Cell................................................................. 1838
1.26.3 Number of Successful Inter-eNodeB Incoming Handovers in a Cell..................................................................1841
1.26.4 Number of Incoming Handover Failures for Different Causes in a Cell.............................................................1846
1.26.5 Number of Path Switch Requests for Inter-eNodeB Incoming Handovers in a Cell.......................................... 1868
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xvi

BTS3203E
1.26.6 Number of Successful Path Switches for inter-eNodeB Incoming Handovers in a Cell.....................................1870
1.26.7 Number of HANDOVER CANCEL Messages Received by the Target Cell from the Source Cell During Inter-
eNodeB Incoming Handover Executions in a Cell.........................................................................................................1873
1.26.8 Number of Successful Inter-eNodeB Incoming Handovers Where RRC Connections Are Reestablished to the
Target Cell for UEs in a Cell.......................................................................................................................................... 1878
1.26.9 Number of conflicts with inter-eNodeB incoming handovers in a cell............................................................... 1881
1.26.10 Number of Incoming Handover Preparation Failures for 3GPP-Defined Causes.............................................1883
1.27 Outgoing Intra-RAT Handover Measurement over X2 (HO.eRAN.X2Out.Cell).................................................. 1886
1.27.1 Number of X2-based Outgoing Handover Attempts in a Cell............................................................................ 1894
1.27.2 Number of X2-based Outgoing Handover Executions in a Cell......................................................................... 1897
1.27.3 Number of Successful X2-based Outgoing Handovers in a Cell........................................................................ 1900
1.27.4 Number of X2-based Outgoing Handover Failures for Different Causes in a Cell.............................................1905
1.27.5 Number of Successful X2-based Outgoing Handovers Where RRC Connections Are Reestablished to the Source
Cell for UEs in a Cell..................................................................................................................................................... 1918
1.27.6 Number of Inter-eNodeB X2-based Voice Service Outgoing Handover Attempts in a Cell.............................. 1920
1.27.7 Number of Inter-eNodeB X2-based Voice Service Outgoing Handover Executions in a Cell........................... 1923
1.27.8 Number of Successful X2-based Voice Service Outgoing Handovers in a Cell................................................. 1925
1.27.9 Number of Successful X2-based Inter-Frequency Voice Service Outgoing Handovers by Reestablishing RRC
Connections in the Source Cell...................................................................................................................................... 1929
1.27.10 Number of X2-based Outgoing Handover Failures for Different Causes in a Cell...........................................1931
1.28 Outgoing Intra-RAT Handover Measurement in DRX (HO.DRX.Out.Cell)......................................................... 1933
1.28.1 Number of Inter-eNodeB Outgoing Handovers Executions in the DRX State................................................... 1935
1.28.2 Number of Successful Inter-eNodeB Outgoing Handovers in the DRX State.................................................... 1938
1.29 Packet Measurement (Traffic.Packet.Cell)............................................................................................................. 1945
1.29.1 Total Processing Delay of Downlink PDCP SDUs for DRB Services in a Cell................................................. 1966
1.29.2 Number of Successfully Transmitted Downlink PDCP SDUs for DRB Services in a Cell................................1970
1.29.3 Total Number of Discarded Downlink PDCP SDUs for DRB Services in a Cell...............................................1974
1.29.4 Total Number of Transmitted Downlink PDCP SDUs for DRB Services in a Cell............................................ 1980
1.29.5 Total Number of Discarded Uplink PDCP SDUs for DRB Services in a Cell....................................................1986
1.29.6 Total Number of Expected Uplink Data Packets for DRB Services in a Cell.....................................................1991
1.29.7 Total Number of Downlink PDCP SDUs that Are for DRB Services and Enter the Empty Buffer in a Cell.....1997
1.29.8 Total Transmission Delay of the First PDCP SDUs of DRB Services in the Empty Buffer in a Cell................ 2001
1.29.9 Number of Uplink PDCP SDUs Discarded for Services Carried on DRBs of Cell Edge UEs in a Cell............ 2005
1.29.10 Number of Expected Uplink PDCP SDUs for Services Carried on DRBs of Cell Edge UEs in a Cell............2006
1.29.11 Number of Lost Uplink PDCP SDUs for Services Carried on DRBs for UEs Far Away from the Cell Center in a
Cell..................................................................................................................................................................................2007
1.29.12 Number of Expected To-Be-Received Uplink PDCP SDUs for Services Carried on DRBs for UEs Far Away
from the Cell Center in a Cell.........................................................................................................................................2009
1.29.13 Consecutively Lost Downlink Packet Statistics................................................................................................ 2010
1.29.14 Consecutively Lost Uplink Packet Statistics..................................................................................................... 2012
1.30 DFEE Measurement (ChMeas.DFEE.Cell)............................................................................................................2014
1.30.1 Duration of Energy Saving and Emission Reduction.......................................................................................... 2015
1.31 Cell LCS Measurement (LCS.Cell)........................................................................................................................2016
1.31.1 Number of E-CID Measurement Requests in a Cell........................................................................................... 2018
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xvii

BTS3203E
1.31.2 Number of Successful E-CID Measurement Requests in a Cell......................................................................... 2019

1.31.3 Number of Successful OTDOA Inter-Frequency RSTD Measurement Requests in a Cell................................ 2021
1.32 Cell Emergency Call Measurement (EMC.Cell).................................................................................................... 2022
1.32.1 Number of Outgoing Handover Attempts for Emergency Calls in a Cell...........................................................2026
1.32.2 Number of Executed Outgoing Handovers for Emergency Calls in a Cell......................................................... 2028
1.32.3 Number of Successful Outgoing Handovers for Emergency Calls in a Cell.......................................................2030
1.32.4 Number of E-RAB Setup Attempts for Emergency Calls in a Cell.................................................................... 2036
1.32.5 Number of Successful E-RAB Setups for Emergency Calls in a Cell................................................................ 2038
1.32.6 Number of Normal E-RAB Releases Due to Outgoing Handovers for Emergency Calls in a Cell....................2040
1.32.7 Number of Abnormal E-RAB Releases Due to Outgoing Handovers for Emergency Calls in a Cell................2042
1.32.8 Number of Abnormal Releases of E-RABs for Emergency Calls in a Cell........................................................ 2044
1.32.9 Number of Normal E-RAB Releases for Emergency Calls in a Cell.................................................................. 2046
1.32.10 Number of Handover Attempts from E-UTRAN to WCDMA Network for SRVCC Triggered for Emergency
Calls................................................................................................................................................................................ 2048
1.32.11 Number of Handover Executions from E-UTRAN to WCDMA Network for SRVCC Triggered for Emergency
Calls................................................................................................................................................................................ 2050
1.32.12 Number of Successful Handovers from E-UTRAN to WCDMA Network for SRVCC Triggered for Emergency
Calls................................................................................................................................................................................ 2052
1.32.13 Number of Handover Attempts from E-UTRAN to GERAN for SRVCC Triggered for Emergency Calls..... 2054
1.32.14 Number of Handover Executions from E-UTRAN to GERAN for SRVCC Triggered for Emergency Calls.. 2055
1.32.15 Number of Successful Handovers from E-UTRAN to GERAN for SRVCC Triggered for Emergency Calls. 2057
1.32.16 Number of Handover Attempts from E-UTRAN to TD-SCDMA Network for SRVCC Triggered for Emergency
Calls................................................................................................................................................................................ 2058
1.32.17 Number of Handover Executions from E-UTRAN to TD-SCDMA Network for SRVCC Triggered for
Emergency Calls.............................................................................................................................................................2060
1.32.18 Number of Successful Handovers from E-UTRAN to TD-SCDMA Network for SRVCC Triggered for
Emergency Calls.............................................................................................................................................................2062
1.33 UE Context Release Measurement (UeCntx.Rel.Cell)...........................................................................................2063
1.33.1 Number of Abnormal UE Context Releases in a Cell......................................................................................... 2068
1.33.2 Number of Normal UE Context Releases in a Cell............................................................................................. 2071
1.33.3 Number of UE Context Releases due to High Mobility of UEs..........................................................................2073
1.33.4 Number of UE Context Releases During an Inter-RAT Measurement................................................................2074
1.33.5 Number of UE Context Releases Initiated by the eNodeB in a Cell................................................................... 2076
1.33.6 Number of UE Context Releases Initiated by the eNodeB due to Different Causes in a Cell............................ 2077
1.33.7 Number of UE Context Releases Initiated by the MME in a Cell.......................................................................2081
1.33.8 Number of UE Context Releases Initiated by the MME due to a Normal Cause in a Cell.................................2083
1.33.9 Number of Remaining UE Context in a Cell.......................................................................................................2084
1.34 UE Context Modification Measurement (UeCntx.Mod.Cell)................................................................................ 2085
1.34.1 Number of UE Context Modification Attempts.................................................................................................. 2086
1.34.2 Number of Successful UE Context Modifications.............................................................................................. 2088
1.35 CA Measurement (CA.Cell)................................................................................................................................... 2089
1.35.1 Total Downlink Activation Duration of CA UEs That Use the Local Cell as Their Scell.................................. 2090
1.35.2 Total Downlink Traffic Volume of MAC TBs in the DL-SCH Transmitted to CA UEs That Use the Local Cell as
Their Scell.......................................................................................................................................................................2091
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xviii

BTS3203E
1.35.3 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............................................................................2092
1.36 RLC Measurement (Traffic.RLC.Cell)...................................................................................................................2094
1.36.1 Number of Bits of Uplink RLC ARQ PDUs Retransmitted by UEs...................................................................2096
1.36.2 Number of Bits of Downlink RLC ARQ PDUs Retransmitted by the eNodeB..................................................2097
1.36.3 Number of Received Uplink RLC ARQ PDUs................................................................................................... 2099
1.36.4 Number of Transmitted Downlink RLC ARQ PDUs..........................................................................................2100
1.36.5 Number of Received Uplink RLC ARQ PDUs Retransmitted by UEs...............................................................2101
1.36.6 Number of Downlink RLC ARQ PDUs Retransmitted by the eNodeB..............................................................2102
1.36.7 Number of Downlink RLC PDUs Failed to Be Sent to UEs in AM Mode in a Cell.......................................... 2103
1.36.8 Distribution of Delay of the First RLC SDUs for Non-GBR Bearers.................................................................2104
1.36.9 Number of downlink SpecificSRB PDUs retransmitted in ARQ mode.............................................................. 2107
1.37 Cell Reserved Counter Measurement (Reserve.Cell).............................................................................................2108
1.37.1 L.Reserve.1.......................................................................................................................................................... 2112
1.37.2 L.Reserve.2.......................................................................................................................................................... 2113
1.37.3 L.Reserve.3.......................................................................................................................................................... 2114
1.37.4 L.Reserve.4.......................................................................................................................................................... 2114
1.37.5 L.Reserve.5.......................................................................................................................................................... 2115
1.37.6 L.Reserve.6.......................................................................................................................................................... 2115
1.37.7 L.Reserve.7.......................................................................................................................................................... 2116
1.37.8 L.Reserve.8.......................................................................................................................................................... 2117
1.37.9 L.Reserve.9.......................................................................................................................................................... 2117
1.37.10 L.Reserve.10...................................................................................................................................................... 2118
1.37.11 L.Reserve.11...................................................................................................................................................... 2118
1.37.12 L.Reserve.12...................................................................................................................................................... 2119
1.37.13 L.Reserve.13...................................................................................................................................................... 2120
1.37.14 L.Reserve.14...................................................................................................................................................... 2120
1.37.15 L.Reserve.15...................................................................................................................................................... 2121
1.37.16 L.Reserve.16...................................................................................................................................................... 2121
1.37.17 L.Reserve.17...................................................................................................................................................... 2122
1.37.18 L.Reserve.18...................................................................................................................................................... 2123
1.37.19 L.Reserve.19...................................................................................................................................................... 2123
1.37.20 L.Reserve.20...................................................................................................................................................... 2124
1.37.21 L.Reserve.21...................................................................................................................................................... 2124
1.37.22 L.Reserve.22...................................................................................................................................................... 2125
1.37.23 L.Reserve.23...................................................................................................................................................... 2126
1.37.24 L.Reserve.24...................................................................................................................................................... 2126
1.37.25 L.Reserve.25...................................................................................................................................................... 2127
1.37.26 L.Reserve.26...................................................................................................................................................... 2127
1.37.27 L.Reserve.27...................................................................................................................................................... 2128
1.37.28 L.Reserve.28...................................................................................................................................................... 2129
1.37.29 L.Reserve.29...................................................................................................................................................... 2129
1.37.30 L.Reserve.30...................................................................................................................................................... 2130
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xix

BTS3203E
1.37.31 L.Reserve.31...................................................................................................................................................... 2130

1.37.32 L.Reserve.32...................................................................................................................................................... 2131
1.37.33 L.Reserve.33...................................................................................................................................................... 2132
1.37.34 L.Reserve.34...................................................................................................................................................... 2132
1.37.35 L.Reserve.35...................................................................................................................................................... 2133
1.37.36 L.Reserve.36...................................................................................................................................................... 2133
1.37.37 L.Reserve.37...................................................................................................................................................... 2134
1.37.38 L.Reserve.38...................................................................................................................................................... 2135
1.37.39 L.Reserve.39...................................................................................................................................................... 2135
1.37.40 L.Reserve.40...................................................................................................................................................... 2136
1.37.41 L.Reserve.41...................................................................................................................................................... 2136
1.37.42 L.Reserve.42...................................................................................................................................................... 2137
1.37.43 L.Reserve.43...................................................................................................................................................... 2138
1.37.44 L.Reserve.44...................................................................................................................................................... 2138
1.37.45 L.Reserve.45...................................................................................................................................................... 2139
1.37.46 L.Reserve.46...................................................................................................................................................... 2139
1.37.47 L.Reserve.47...................................................................................................................................................... 2140
1.37.48 L.Reserve.48...................................................................................................................................................... 2141
1.37.49 L.Reserve.49...................................................................................................................................................... 2141
1.37.50 L.Reserve.50...................................................................................................................................................... 2142
1.37.51 L.Reserve.51...................................................................................................................................................... 2142
1.37.52 L.Reserve.52...................................................................................................................................................... 2143
1.37.53 L.Reserve.53...................................................................................................................................................... 2144
1.37.54 L.Reserve.54...................................................................................................................................................... 2144
1.37.55 L.Reserve.55...................................................................................................................................................... 2145
1.37.56 L.Reserve.56...................................................................................................................................................... 2145
1.37.57 L.Reserve.57...................................................................................................................................................... 2146
1.37.58 L.Reserve.58...................................................................................................................................................... 2147
1.37.59 L.Reserve.59...................................................................................................................................................... 2147
1.37.60 L.Reserve.60...................................................................................................................................................... 2148
1.37.61 L.Reserve.61...................................................................................................................................................... 2148
1.37.62 L.Reserve.62...................................................................................................................................................... 2149
1.37.63 L.Reserve.63...................................................................................................................................................... 2150
1.37.64 L.Reserve.64...................................................................................................................................................... 2150
1.37.65 L.Reserve.65...................................................................................................................................................... 2151
1.37.66 L.Reserve.66...................................................................................................................................................... 2151
1.37.67 L.Reserve.67...................................................................................................................................................... 2152
1.37.68 L.Reserve.68...................................................................................................................................................... 2153
1.37.69 L.Reserve.69...................................................................................................................................................... 2153
1.37.70 L.Reserve.70...................................................................................................................................................... 2154
1.37.71 L.Reserve.71...................................................................................................................................................... 2154
1.37.72 L.Reserve.72...................................................................................................................................................... 2155
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xx

BTS3203E
1.37.73 L.Reserve.73...................................................................................................................................................... 2156

1.37.74 L.Reserve.74...................................................................................................................................................... 2156
1.37.75 L.Reserve.75...................................................................................................................................................... 2157
1.37.76 L.Reserve.76...................................................................................................................................................... 2157
1.37.77 L.Reserve.77...................................................................................................................................................... 2158
1.37.78 L.Reserve.78...................................................................................................................................................... 2159
1.37.79 L.Reserve.79...................................................................................................................................................... 2159
1.37.80 L.Reserve.80...................................................................................................................................................... 2160
1.38 MR Measurement (ChMeas.MeasRpt.Cell)........................................................................................................... 2160
1.38.1 Number of Measurement Control Messages Sent by the eNodeB in a Cell........................................................2162
1.38.2 Number of Times UEs Send Intra-Frequency Measurement Reports in a Cell...................................................2166
1.39 UE Context Setup Measurement (UeCntx.Est.Cell).............................................................................................. 2167
1.39.1 Number of UE Context Setup Attempts in a Cell............................................................................................... 2168
1.39.2 Number of Successful UE Context Setups in a Cell........................................................................................... 2170
1.40 UE Context Setup Failure Measurement (UeCntx.EstFail.Cell)............................................................................ 2172
1.40.1 Number of UE Context Setup Failures for Different Causes in a Cell ...............................................................2173
1.41 Incoming Intra-RAT Handover Measurement over X2 (HO.eRAN.X2In.Cell).................................................... 2178
1.41.1 Number of X2-based Incoming Handover Attempts in a Cell............................................................................ 2182
1.41.2 Number of X2-based Incoming Handover Executions in a Cell......................................................................... 2184
1.41.3 Number of Successful X2-based Incoming Handovers in a Cell........................................................................ 2187
1.41.4 Number of X2-based Incoming Handover Failures for Different Causes in a Cell............................................ 2190
1.41.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......................................................................................................... 2193
1.41.6 Number of X2-based Incoming Handover Failures for Different Causes in a Cell............................................ 2195
1.42 Throughput Distribution Measurement (Traffic.Thruput.PDF.Cell)...................................................................... 2198
1.42.1 Distribution of the Downlink Throughput in a Cell............................................................................................ 2219
1.42.2 Distribution of the Uplink Throughput in a Cell................................................................................................. 2257
1.42.3 Downlink UE-Perceived Data Rate Distribution in a Cell.................................................................................. 2261
1.43 Packet Size Distribution Measurement (Traffic.Packet.PDF.Cell).........................................................................2262
1.43.1 Downlink PDCP SDU Size Distribution............................................................................................................. 2296
1.43.2 Uplink PDCP SDU Size Distribution.................................................................................................................. 2331
1.44 Cell MBMS Measurement (MBMS.Cell).............................................................................................................. 2365
1.44.1 Number of Bits for MBMS Services Scheduled in a Cell................................................................................... 2366
1.44.2 Number of Bits for MBMS Services Received in a Cell.....................................................................................2367
1.44.3 Number of SYNC PDUs for MBMS Services Received in a Cell...................................................................... 2368
1.44.4 Number of SYNC PDUs for MBMS Services Discarded in a Cell.....................................................................2369
1.44.5 Number of SYNC PDUs for MBMS Services Discarded Because Data Received Exceeds Within an MSP the
Bearing Capability in a Cell........................................................................................................................................... 2370
1.44.6 Number of SYNC PDUs for MBMS Services Discarded Because of Incorrect Time Stamps in a Cell............ 2371
1.44.7 Number of SYNC PDUs for MBMS Services Discarded for Transmission-related Causes in a Cell................ 2372
1.45 SCell CQI Measurement (ChMeas.CQI.CA.SCell)............................................................................................... 2373
1.45.1 Number of Periodic Wideband CQI Reports in Single-Codeword Transmission Sent by CA UEs that Use the
Local Cell as Their Scell................................................................................................................................................ 2396
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxi

BTS3203E
1.45.2 Number of Aperiodic Wideband CQI Reports in Single-Codeword Transmission Sent by CA UEs that Use the
Local Cell as Their Scell................................................................................................................................................ 2410
1.45.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 Scell............................................................................................................................ 2424
1.45.4 Number of Aperiodic Wideband CQI Reports for Codeword 0 in Dual-Codeword Transmission Sent by CA UEs
1.45.5 Number of Periodic Wideband CQI Reports for Codeword 1 in Dual-Codeword Transmission Sent by CA UEs
1.45.6 Number of Aperiodic Wideband CQI Reports for Codeword 1 in Dual-Codeword Transmission Sent by CA UEs
1.46 SCell MCS Measurement (ChMeas.MCS.CA.SCell)............................................................................................ 2479
1.46.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...........................................................................................................................................................2496
1.46.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..........................................................................................................................................................2519
1.46.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................................................................................................................................................................. 2531
1.47 CA Cell MAC Measurement (Traffic.MAC.CA.Cell)........................................................................................... 2544
1.47.1 Number of TBs Initially Transmitted on the Downlink SCH for CA UEs that Use the Local Cell as Their Scell
........................................................................................................................................................................................ 2548
1.47.2 Number of Downlink Error TBs After Initial Transmission for CA UEs that Use the Local Cell as Their Scell
........................................................................................................................................................................................ 2551
1.47.3 Number of Downlink Error TBs After the Maximum number of Transmissions for CA UEs that Use the Local
Cell as Their Scell...........................................................................................................................................................2554
1.47.4 Number of TBs Initially Transmitted on the Uplink SCH for CA UEs that Treat the Local Cell as Their SCell
........................................................................................................................................................................................ 2557
1.47.5 Number of TBs to Which CA UEs That Treat the Local Cell as Their SCell in the Downlink CA State Respond
with NACKs................................................................................................................................................................... 2559
1.47.6 Number of Bits of Downlink TBs with Bit Errors after the Maximum Number of Retransmissions for CA UEs
that Treat the Local as Their Scell.................................................................................................................................. 2561
1.48 Throughput and Data Volume Measurement 1 (Traffic.Thruput.Cell.1)................................................................2562
1.48.1 Uplink Traffic Volume at the PDCP layer........................................................................................................... 2569
1.48.2 Downlink Traffic Volume at the PDCP layer...................................................................................................... 2572
1.48.3 Downlink Traffic Volume at the Physical Layer................................................................................................. 2576
1.48.4 Uplink Traffic Volume at the Physical Layer...................................................................................................... 2577
1.48.5 Maximum Downlink Traffic Volume at the Physical Layer................................................................................2578
1.48.6 Maximum Uplink Traffic Volume at the Physical Layer.....................................................................................2579
1.48.7 Total Duration of Data Storage in the Uplink and Downlink Buffer...................................................................2580
1.48.8 Total PDCP-Layer Traffic Volume of To-Be-Transmitted Downlink Data in a Cell.......................................... 2581
1.48.9 Total PDCP-Layer Traffic Volume of Discarded To-Be-Transmitted Downlink Data in a Cell......................... 2582
1.48.10 Total RLC-Layer Traffic Volume of Downlink Data in a Cell.......................................................................... 2583
1.48.11 Total RLC-Layer Traffic Volume of Uplink Data in a Cell............................................................................... 2584
1.48.12 Total PDCP-Layer Traffic Volume of Discarded Uplink Data.......................................................................... 2585
1.48.13 Total PDCP-Layer Traffic Volume of Uplink Data in a Cell.............................................................................2586
1.48.14 Uplink Traffic Volume Received for CEUs in a Cell........................................................................................ 2587
1.48.15 Downlink Traffic Volume Sent for CEUs in a Cell........................................................................................... 2588
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxii

BTS3203E
1.48.16 PDCP-layer Traffic Volume Scheduled for Uplink Small Packets for CEUs in a Cell.....................................2589
1.48.17 Transmission Duration of Uplink Data Except Small Packets for CEUs in a cell............................................ 2590
1.48.18 Downlink PDCP-layer Traffic Volume Sent in the Last TTI for CEUs Before the Buffer is Empty in a Cell. 2591
1.48.19 Data Transmission Duration for CEUs Except the Last TTI Before the Downlink Buffer Is Empty............... 2592
1.48.20 Uplink Data Transmission Duration from the Time the UE Buffer is Not Empty to the Time the UE Buffer is
Empty in a Cell............................................................................................................................................................... 2593
1.48.21 Uplink Traffic Volume of PDCP PDUs Received from the Time the UE Buffer is Not Empty to the Time the UE
Buffer is Empty in a Cell................................................................................................................................................ 2595
1.48.22 Total Uplink Traffic Volume of PDCP PDUs for Joint Reception CEUs in a Cell........................................... 2596
1.48.23 Total Downlink Traffic Volume of PDCP SDUs for Joint Transmission CEUs in a Cell................................. 2597
1.48.24 Traffic Volume of PDCP PDUs Scheduled for Uplink Small Packets for Joint Reception CEUs....................2598
1.48.25 Duration of Transmitting Uplink Data Except Small Packets for Joint Reception CEUs in a Cell.................. 2599
1.48.26 Downlink Traffic Volume of PDCP SDUs Sent in the Last TTI Before the Buffer of the UE Is Empty for Joint
Transmission CEUs in a Cell..........................................................................................................................................2601
1.48.27 Duration of Transmitting Data for Joint Transmission CEUs in a Cell Except the Last TTI Before the Downlink
Buffer of the UE is Empty.............................................................................................................................................. 2602
1.48.28 PDCP-Layer Traffic Volume Transmitted per Measurement Object.................................................................2603
1.48.29 PDCP-Layer Data Transmission Duration per Measurement Object................................................................2604
1.49 MCS Measurement 1 (ChMeas.MCS1.Cell).......................................................................................................... 2605
1.49.1 Number of Times a Specific MCS Index Is Selected for Scheduling Downlink-256QAM-enabled UEs on the
PDSCH in a Cell............................................................................................................................................................. 2611
1.50 Outgoing Inter-RAT Handover Measurement 1 (HO.IRAT.Out.Cell.1).................................................................2626
1.50.1 Number of Handover Preparation Attempts from E-UTRAN to WCDMA Network Triggered by UE-Number-
Based MLB.....................................................................................................................................................................2636
1.50.2 Number of Handover Execution Attempts from E-UTRAN to WCDMA Network Triggered by UE-Number-
Based MLB.....................................................................................................................................................................2638
1.50.3 Number of Successful Handover Executions from E-UTRAN to WCDMA Network Triggered by UE-Number-
based MLB..................................................................................................................................................................... 2640
Outgoing Handovers for Ultra-Flash CSFB................................................................................................................... 2642
1.50.5 Number of Inter-RAT Outgoing Handover Failures for Ultra-Flash CSFB for Different Causes...................... 2644
1.50.6 Number of QoE-based EUTRAN-to-WCDMA Handover Attempts..................................................................2649
1.50.7 Number of QoE-based EUTRAN-to-WCDMA Handover Executions...............................................................2650
1.50.8 Number of Successful QoE-based EUTRAN-to-WCDMA Handovers..............................................................2652
1.50.9 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During QoE-based
EUTRAN-to-WCDMA Handover Executions............................................................................................................... 2653
1.50.10 Number of Coverage-based Inter-RAT Handover Executions from E-UTRAN to Another System................2655
1.50.11 Number of Successful Coverage-based Inter-RAT Handovers from E-UTRAN to Another System............... 2657
1.50.12 Number of Coverage-based Inter-RAT Handover Attempts from E-UTRAN to Another System................... 2659
1.50.13 Number of Successful Service-based Inter-RAT Handover Attempts from E-UTRAN to Another System.... 2661
1.50.14 Number of Service-based Inter-RAT Handover Executions from E-UTRAN to Another System................... 2663
1.50.15 Number of Successful Service-based Inter-RAT Handovers from E-UTRAN to Another System.................. 2665
1.50.16 Number of Coverage-based Inter-RAT Redirections from E-UTRAN to Another System.............................. 2667
1.50.17 Number of Service-based Inter-RAT Redirections from E-UTRAN to TD-SCDMA Network....................... 2668
1.50.18 Number of CSFB Executions from E-UTRAN to Another System.................................................................. 2669
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxiii

BTS3203E
1.50.20 Number of Inter-RAT Blind Redirections......................................................................................................... 2673
1.50.21 Number of Attempts to Read CGIs for Inter-RAT Neighboring Cells of a Cell............................................... 2675
1.50.22 Number of Successful Attempts to Read CGIs for Inter-RAT Neighboring Cells of a Cell............................. 2677
1.50.23 Number of Outgoing EUTRAN-to-WCDMA Handover Attempts Triggered by Experience-based Load
Balancing........................................................................................................................................................................ 2679
1.50.24 Number of Outgoing EUTRAN-to-WCDMA Handover Executions Triggered by Experience-based Load
Balancing........................................................................................................................................................................ 2681
1.50.25 Number of Successful Outgoing EUTRAN-to-WCDMA Handovers Triggered by Experience-based Load
Balancing........................................................................................................................................................................ 2683
1.50.26 Number of Times Inter-RAT Handovers Fail for a Specific Reason.................................................................2685
1.50.27 Number of Load-based Inter-RAT Handover Preparation Attempts for UEs Performing Voice Services........2688
1.50.28 Number of Load-based Inter-RAT Handover Execution Attempts for UEs Performing Voice Services..........2690
1.50.29 Number of Successful Load-based Inter-RAT Handover Executions for UEs Performing Voice Services......2692
1.50.30 Number of Preparation Attempts for Voice Quality-based Inter-RAT Handovers from E-UTRAN.................2694
1.50.31 Number of Voice Quality-based E-UTRAN-to-Inter-RAT Handover Executions............................................ 2696
1.50.32 Number of Successful Voice Quality-based E-UTRAN-to-Inter-RAT Handover Executions.......................... 2698
1.50.33 Number of Handover Attempts from An E-UTRAN Cell to High-Load WCDMA Cells................................2700
1.51 Outgoing Intra-RAT Handover Measurement 1 (HO.eRAN.Out.Cell.1)...............................................................2702
1.51.1 Number of Successful Intra-eNodeB Voice Service Outgoing Handovers by Reestablishing RRC Connections in
the Source Cell................................................................................................................................................................2719
1.51.2 Number of Successful Inter-eNodeB Voice Service Outgoing Handovers by Reestablishing RRC Connections in
the Source Cell................................................................................................................................................................2721
1.51.3 Number of Outgoing Handover Failures for Different Causes in a Cell............................................................. 2725
1.51.4 Number of Intra-RAT Redirections Triggered by High-Speed UEs....................................................................2727
1.51.5 Number of Outgoing Handover Preparation Failures for 3GPP-Defined Causes............................................... 2728
1.51.6 Number of Fast-Mobility-triggered Inter-Frequency Handover Preparation Attempts...................................... 2730
1.51.7 Number of Fast-Mobility-triggered Inter-Frequency Handover Execution Attempts.........................................2732
1.51.8 Number of Successful Fast-Mobility-triggered Inter-Frequency Handover Executions.....................................2735
1.51.9 Number of Fast-Mobility-triggered Inter-Duplex-Mode Handover Preparation Attempts................................. 2742
1.51.10 Number of Fast-Mobility-triggered Inter-Duplex-Mode Handover Execution Attempts................................. 2744
1.51.11 Number of Successful Fast-Mobility-triggered Inter-Duplex-Mode Handover Executions............................. 2746
1.51.12 Number of PCC-Anchoring-based Inter-Frequency Handover Preparation Attempts......................................2753
1.51.13 Number of PCC-Anchoring-based Inter-Frequency Handover Execution Attempts........................................ 2755
1.51.14 Number of Successful PCC-Anchoring-based Inter-Frequency Handover Executions.................................... 2758
1.51.15 Number of PCC-Anchoring-based Inter-duplex-mode Handover Preparation Attempts..................................2765
1.51.16 Number of PCC-Anchoring-based Inter-Duplex-mode Handover Execution Attempts................................... 2768
1.51.17 Number of Successful PCC-Anchoring-based Inter-Duplex-mode Handover Executions............................... 2771
1.51.18 Number of Inter-Frequency Handover Preparation Attempts Triggered by Carrier Attributes........................ 2778
1.51.19 Number of Inter-Duplex-Mode Handover Preparation Attempts Triggered by Carrier Attributes...................2781
1.51.20 Number of Inter-Frequency Handover Execution Attempts Triggered by Carrier Attributes...........................2784
1.51.21 Number of Inter-Duplex-Mode Handover Execution Attempts Triggered by Carrier Attributes..................... 2787
1.51.22 Number of Successful Inter-Frequency Handover Executions Triggered by Carrier Attributes.......................2790
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxiv

BTS3203E
1.51.23 Number of Successful Inter-Duplex-Mode Handover Executions Triggered by Carrier Attributes................. 2797
1.51.24 Number of Intra-RAT Redirections Triggered by Carrier Attributes................................................................ 2804
1.51.25 Number of Intra-RAT Redirections Triggered by Carrier Attributes................................................................ 2805
1.51.26 Number of Inter-eNodeB Outgoing Handover Attempts for UEs Performing QCI 2 Services in a Cell..........2807
1.51.27 Number of X2-based Outgoing Handover Attempts for UEs Performing QCI 2 Services in a Cell................ 2810
1.51.28 Number of Successful X2-based Outgoing Handovers for UEs Performing QCI 2 Services in a Cell............ 2812
1.51.29 Number of Successful Inter-eNodeB Outgoing Handovers for UEs Performing QCI 2 Services in a Cell......2816
1.51.30 Number of Successful X2-based Outgoing Handovers Where RRC Connections Are Reestablished to the
Source Cell for UEs Performing QCI 2 Services in a Cell.............................................................................................2823
1.51.31 Number of Successful Inter-eNodeB Outgoing Handovers Where RRC Connections Are Reestablished to the
1.51.32 Number of X2-based Outgoing Handover Executions for UEs Performing QCI 2 Services in a Cell............. 2829
1.51.33 Number of Successful Intra-eNodeB Outgoing Handovers for UEs Performing QCI 2 Services in a Cell......2831
1.51.34 Number of Intra-eNodeB Outgoing Handovers Executions for UEs Performing QCI 2 Services in a Cell.....2834
1.51.35 Number of Successful Intra-eNodeB Outgoing Handovers Where RRC Connections Are Reestablished to the
1.51.36 Number of Attempts to Read CGIs for Intra-RAT Neighboring Cells of a Cell............................................... 2839
1.51.37 Number of Successful Attempts to Read CGIs for Intra-RAT Neighboring Cells of a Cell............................. 2841
1.51.38 Number of Times RRC Connections Are Reestablished to the Source Cell During Load-based Handovers...2842
1.51.39 Number of Successful Intra-eNodeB Outgoing Handovers Where RRC Connections Are Reestablished to Intra-
eNodeB Non-Source Cells for UEs in a Cell................................................................................................................. 2846
1.51.40 Number of Successful Inter-eNodeB Outgoing Handovers Where RRC Connections Are Reestablished to
Source-eNodeB Non-Source Cells for UEs in a Cell..................................................................................................... 2849
1.51.41 Number of Load-based Handover Preparation Attempts for CA UEs.............................................................. 2853
1.51.42 Number of Successful Load-based Handover Executions for CA UEs............................................................ 2856
1.51.43 Number of Load-based Handover Execution Attempts for CA UEs................................................................ 2863
1.51.44 Number of Video-Load-Control-based Handover Preparation Attempts..........................................................2866
1.51.45 Number of Video-Load-Control-based Handover Execution Attempts............................................................ 2868
1.51.46 Number of Successful Video-Load-Control-based Handover Executions........................................................ 2871
1.51.47 Number of Load-based Intra-RAT Handover Preparation Attempts for UEs Performing Voice Services....... 2877
1.51.48 Number of Load-based Intra-RAT Handover Execution Attempts for UEs Performing Voice Services..........2880
1.51.49 Number of Successful Load-based Intra-RAT Handover Executions for UEs Performing Voice Services......2883
1.51.50 Number of Intra-Cell Outgoing Handover Execution Attempts in a Cell......................................................... 2890
1.51.51 Number of Successful Intra-Cell Outgoing Handover Executions in a Cell..................................................... 2892
1.51.52 Number of Intra-RAT Redirections of UEs Performing Voice Services........................................................... 2894
1.51.53 Number of Outgoing Handover Preparation Attempts for UEs Performing MCPTT Voice Services.............. 2896
1.51.54 Number of Outgoing Handover Execution Attempts for UEs Performing MCPTT Voice Services................ 2899
1.51.55 Number of Successful Outgoing Handovers for UEs Performing MCPTT Voice Services..............................2902
1.51.56 Number of Voice Quality-based Handover Preparation Attempts.................................................................... 2908
1.51.57 Number of Voice Quality-based Handover Execution Attempts.......................................................................2910
1.51.58 Number of Successful Voice Quality-based Handover Executions...................................................................2913
1.52 Channel Quality Measurement1 (ChMeas.Pwr1.Cell)........................................................................................... 2919
1.52.1 Average Interference and Noise Received by Each PRB in a Cell......................................................................2938
1.52.2 Maximum Interference and Noise Received by Each PRB in a Cel................................................................... 2965
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxv

BTS3203E
1.53 Resource Optimization Measurement (ResOpt.Cell)............................................................................................. 2993

1.53.1 Ratio of Times the Number of Scheduled UEs per TTI in the Downlink Is Limited in a Cell........................... 2994
1.53.2 Ratio of Remaining PDSCH RBs When the Number of Scheduled UEs per TTI in the Downlink Is Limited in a
Cell..................................................................................................................................................................................2996
1.53.3 Ratio of Remaining Downlink PDSCH RBs When CCE Resources Are Limited............................................. 2997
1.53.4 Ratio of Times the Number of Scheduled UEs per TTI in the Uplink Is Limited in a Cell................................ 2999
1.53.5 Ratio of Remaining PUSCH RBs When the Number of Scheduled UEs per TTI in the Uplink Is Limited in a Cell
........................................................................................................................................................................................ 3000
1.53.6 Ratio of Remaining Uplink PUSCH RBs When CCE Resources Are Limited.................................................. 3002
1.53.7 Ratio of Remaining CCEs When the Number of Scheduled UEs per TTI Is Limited in a Cell..........................3003
1.54 UE Traffic Rate Distribution Measurement (Traffic.User.Thruput.Cell)............................................................... 3004
1.54.1 Downlink PS Service Traffic Distribution...........................................................................................................3007
1.54.2 Downlink PS Service Throughput Distribution...................................................................................................3011
1.55 Throughput and Data Volume Measurement per Path Loss Range (PL.Traffic.Thruput.Cell).............................. 3014
1.55.1 Distribution of Total Uplink Traffic Volume of PDCP PDUs for UEs with Different Path Loss Ranges.......... 3023
1.55.2 Distribution of Data Transmission Duration of Uplink PDCP PDUs (Excluding Small Packets) for UEs with
Different Path Loss Ranges............................................................................................................................................ 3030
1.55.3 Distribution of Traffic Volume of Uplink Small Packets at the PDCP Layer for UEs With Different Path Loss
Ranges............................................................................................................................................................................ 3037
1.55.4 Distribution of UEs that Are Performing Services with Different Path Loss Ranges.........................................3044
1.56 Service Setup Measurement (Traffic.Service.AttEst.Cell)..................................................................................... 3050
1.56.1 Average Access Delay for Downlink Data Services Successfully Initiated by Idle-Mode Ues..........................3052
1.56.2 Access Delay Distribution for Downlink Data Services Successfully Initiated by Idle-Mode Ues....................3053
1.56.3 Average Access Delay for Uplink Data Services Successfully Initiated by Idle-Mode UEs in the Cell............ 3055
1.57 Differentiated Service Throughput Measurement (Traffic.Thruput.Diff.Cell).......................................................3057
1.57.1 Downlink Data Transmission Duration of Services per Priority.........................................................................3059
1.57.2 Downlink Traffic Volume of Services per Priority..............................................................................................3063
1.57.3 Downlink Transmission Duration of Services Identified by SC in a Cell...........................................................3066
1.57.4 Downlink Traffic Volume of Services Identified by SC in Cell..........................................................................3067
1.58 E-RAB Data Volume Distribution Measurement (Traffic.Volume.PDF.Cell)........................................................3068
1.58.1 Distribution of Downlink Traffic Volume of E-RABs........................................................................................ 3074
1.58.2 Distribution of Uplink Traffic Volume of E-RABs............................................................................................. 3082
1.59 Inter-RAT MRO Measurement (MroMeas.InterRat.Cell)...................................................................................... 3090
1.59.1 Number of Delayed Inter-RAT Handovers..........................................................................................................3094
1.59.2 Number of Unnecessary Inter-RAT Handovers...................................................................................................3097
1.59.3 Number of Ping-Pong Inter-RAT Handovers...................................................................................................... 3099
1.59.4 Number of Premature Inter-RAT Handovers.......................................................................................................3101
1.60 MDT Measurement (ChMeas.MDT.Cell).............................................................................................................. 3103
1.60.1 Number of Times MDT Measurement Configurations Are Delivered and Number of Times MDT Measurement
Reports Are Sent.............................................................................................................................................................3106
1.61 Cell Algorithm Measurement1 (Algo1.Cell)..........................................................................................................3109
1.61.1 Number of Times the Uplink Speech Coding Rate Changes...............................................................................3117
1.61.2 Speech Coding Scheme Distribution................................................................................................................... 3119
1.61.3 VQI Distribution of EVS at Different Speech Quality Levels............................................................................ 3130
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxvi

BTS3203E
1.61.4 Total Values of VQIs of EVS...............................................................................................................................3133

1.61.5 UE TA Distribution..............................................................................................................................................3134
1.62 Extended QCI Measurement (ExtendedQci.Cell).................................................................................................. 3137
1.62.1 Number of E-RAB Setup Attempts for Services with a Specific Extended QCI in a Cell................................. 3145
1.62.2 Number of Successful E-RAB Setups for Services with a Specific Extended QCI in a Cell............................. 3149
1.62.3 Number of Abnormal E-RAB Releases for Services with a Specific Extended QCI in a Cell...........................3153
1.62.4 Number of Normal E-RAB Releases for Services with a Specific Extended QCI in a Cell...............................3156
1.62.5 Uplink Traffic Volume of PDCP PDUs of Services with a Specific Extended QCI........................................... 3160
1.62.6 Uplink PDCP-Layer Transmission Duration of a Specific Extended QCI..........................................................3163
1.62.7 Downlink Traffic Volume of PDCP SDUs of Services with a Specific Extended QCI...................................... 3165
1.62.8 Downlink PDCP-Layer Transmission Duration of a Specific Extended QCI.....................................................3168
1.62.9 Average number of Activated UEs with a Specific Extended QCI in the Uplink............................................... 3170
1.62.10 Average number of Activated UEs with a Specific Extended QCI in the Downlink........................................ 3173
1.62.11 Number of Used Extended-QCI Uplink PRBs.................................................................................................. 3175
1.62.12 Number of Used Extended-QCI Downlink PRBs............................................................................................. 3178
1.63 Intra-RAT MRO Measurement (MroMeas.IntraRat.Cell)...................................................................................... 3180
1.63.1 Number of Intra-RAT Ping-Pong Handovers...................................................................................................... 3184
1.63.2 Number of Intra-RAT Handovers to Wrong Cells...............................................................................................3190
1.63.3 Number of Premature Intra-RAT Handovers.......................................................................................................3193
1.63.4 Number of Delayed Intra-RAT Handovers..........................................................................................................3196
1.64 Channel Quality Measurement2 (ChMeas.Pwr2.Cell)........................................................................................... 3199
1.64.1 Numbers of Times the eNodeB Detects that PUCCH SINR Values Fall into Specific Ranges in a Cell........... 3202
1.64.2 Numbers of Times the eNodeB Detects that PUSCH SINR Values Fall into Specific Ranges in a Cell............3207
1.65 AMBR Measurement (AMBR.Cell).......................................................................................................................3210
1.65.1 Downlink UE-AMBR Distribution in a Cell....................................................................................................... 3212
2 Measurement of eNodeB Performance (eNodeB)............................................................. 3216

2.1 eNodeB LCS Measurement (LCS.ENODEB)..........................................................................................................3218
2.1.1 Number of OTDOA Measurement Attempts Received by an eNodeB.................................................................3218
2.1.2 Number of Successful Responses Sent by an eNodeB to OTDOA Measurement Requests.................................3219
2.2 eNodeB User Quantity Measurement (Traffic.User.eNodeB)..................................................................................3220
2.2.1 Maximum Number of UL-Sync UEs in an eNodeB..............................................................................................3221
2.2.2 Maximum Number of UEs Served by an eNodeB................................................................................................ 3222
2.3 eNodeB RIM Measurement (RIM.eNodeB)............................................................................................................ 3223
2.3.1 Number of times the eNodeB sends a system information request to a WCDMA network................................. 3226
2.3.2 Number of times the eNodeB receives a system information response from a WCDMA network......................3228
2.3.3 Number of times the eNodeB receives a system information update from a WCDMA network......................... 3230
2.3.4 Number of times the eNodeB sends a load information request to a WCDMA network..................................... 3232
2.3.5 Number of times the eNodeB receives a load information response from a WCDMA network.......................... 3234
2.3.6 Number of times the eNodeB receives a load information update from a WCDMA network............................. 3236
2.3.7 Number of times the eNodeB receives a load information request from a WCDMA network.............................3238
2.3.8 Number of times the eNodeB sends a load information response to a WCDMA network................................... 3240
2.3.9 Number of times the eNodeB sends a load information update to a WCDMA network...................................... 3242
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxvii

BTS3203E
2.3.10 Number of times the eNodeB receives a load information update acknowledgment from a WCDMA network
........................................................................................................................................................................................ 3244
2.3.11 Number of times the eNodeB sends a load information request to a GERAN....................................................3246
2.3.12 Number of times the eNodeB receives a load information response from a GERAN........................................ 3248
2.3.13 Number of times the eNodeB sends a system information request to a GERAN............................................... 3250
2.3.14 Number of times the eNodeB receives a system information response from a GERAN.................................... 3252
2.3.15 Number of times the eNodeB receives a system information update from a GERAN....................................... 3254
2.4 eNodeB Throughput Measurement (Traffic.Thruput.eNodeB)................................................................................ 3255
2.4.1 Maximum Traffic Volume for PDCP SDUs in an eNodeB................................................................................... 3256
2.5 eNodeB SCTP Measurement (SCTP.eNodeB)......................................................................................................... 3257
2.5.1 Number of Times of Downlink SCTP Congestion Control...................................................................................3258
2.5.2 Number of UE Context Releases Because of S1 SCTP Link Disconnection........................................................3259
2.6 MBMS Session Measurement (MBMS.eNodeB).................................................................................................... 3260
2.6.1 Number of MBMS Session Setup Attempts in an eNodeB...................................................................................3261
2.6.2 Number of Successfully Set up MBMS Sessions in an eNodeB...........................................................................3262
2.6.3 Number of MBMS Session Setup Failures............................................................................................................3264
2.6.4 Number of MBMS Session Stop Attempts in an eNodeB.....................................................................................3266
2.6.5 Number of MBMS Sessions in an eNodeB........................................................................................................... 3267
2.7 eNodeB Reserved Counter Measurement (Reserve.eNodeB).................................................................................. 3268
2.7.1 L.eNodeB.Reserve.1..............................................................................................................................................3269
2.7.2 L.eNodeB.Reserve.2..............................................................................................................................................3270
2.7.3 L.eNodeB.Reserve.3..............................................................................................................................................3270
2.7.4 L.eNodeB.Reserve.4..............................................................................................................................................3271
2.7.5 L.eNodeB.Reserve.5..............................................................................................................................................3272
2.7.6 L.eNodeB.Reserve.6..............................................................................................................................................3272
2.7.7 L.eNodeB.Reserve.7..............................................................................................................................................3273
2.7.8 L.eNodeB.Reserve.8..............................................................................................................................................3274
2.7.9 L.eNodeB.Reserve.9..............................................................................................................................................3274
2.7.10 L.eNodeB.Reserve.10..........................................................................................................................................3275
2.8 EPC-Inside User Quantity Measurement (EPCInside.User).................................................................................... 3275
2.8.1 Maximum number of users attached to the EPC-inside........................................................................................ 3276
2.8.2 Average Number of Users Attached to the EPC-Inside.........................................................................................3277
2.8.3 Average Number of Dual-PDN Connection-enabled Users Attached to the EPC-Inside..................................... 3278
2.9 EPC-Inside Attach Measurement (EPCInside.Attach)............................................................................................. 3278
2.9.1 Number of Attachment Requests of UEs in the EPC-Inside................................................................................. 3280
2.9.2 Number of Successful Attachments in the EPC-Inside......................................................................................... 3281
2.9.3 Number of Attachment Failures in the EPC-Inside...............................................................................................3282
2.10 EPC-Inside Authentication Measurement (EPCInside.Authentication).................................................................3283
2.10.1 Number of authentication requests on the EPC inside........................................................................................ 3284
2.10.2 Number of successful authentication times on the EPC inside........................................................................... 3285
2.11 eNodeB Algorithm Measurement (Algo.eNodeB)................................................................................................. 3285
2.11.1 Number of Times an eNodeB Becomes Unavailable.......................................................................................... 3286
2.11.2 Duration of eNodeB Unavailability.....................................................................................................................3287
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxviii

BTS3203E
3 Measurement of S1 Link Performance (Sig.S1)................................................................. 3289

3.1 S1 Link Measurement (Sig.S1)................................................................................................................................ 3290
3.1.1 Number of S1 Interface Setups..............................................................................................................................3291
3.1.2 Duration of S1 Link Unavailability....................................................................................................................... 3292
3.1.3 Number of Times an eNodeB Selects S1 Interfaces for UEs................................................................................ 3293
4 Measurement of X2 Link Performance (Sig.X2)................................................................ 3296

4.1 X2 Link Measurement (Sig.X2)............................................................................................................................... 3297
4.1.1 Number of X2 Link Setup Attempts......................................................................................................................3298
4.1.2 Number of Successful X2 Link Setups..................................................................................................................3300
4.1.3 Duration of X2 Link Unavailability...................................................................................................................... 3302
5 Measurement of Intra-RAT Inter-Cell Handover Performance (NCell).......................3304

5.1 LTE Cell-to-LTE Cell Outgoing Handover Measurement (HO.NCell.Cell)............................................................ 3305
5.1.1 Number of Outgoing Handover Attempts Between Two Specific Cells...............................................................3309
5.1.2 Number of Outgoing Handover Executions Between Two Specific Cells............................................................3312
5.1.3 Number of Successful Outgoing Handovers Between Two Specific Cells...........................................................3315
5.1.4 Number of Ping-Pong Handovers Between Two Specific Cells........................................................................... 3322
5.1.5 Number of Delayed Intra-RAT Handovers between two specific cells.................................................................3329
5.1.6 Number of Premature Intra-RAT Handovers between two specific cells..............................................................3331
5.1.7 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During Outgoing Handover
Executions Between Two Specific Cells........................................................................................................................ 3334
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........................................................................................................ 3336
5.1.9 Number of intra-RAT handovers to a wrong cell between two specific cells....................................................... 3339
5.1.10 Reasons of Outgoing Handover Failures Between Two Specific Cells.............................................................. 3343
5.2 LTE Cell-to-LTE Cell Incoming Handover Measurement (HO.NCell.In.Cell)....................................................... 3346
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......................................................................................................... 3348
5.2.2 Number of Incoming Handover Attempts Between Two Cells.............................................................................3351
5.2.3 Number of Incoming Handovers Performed Between Two Cells......................................................................... 3353
5.2.4 Number of Successful Incoming Handovers Between Two Cells.........................................................................3355
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...............................................................3373
6.1.3 Total Number of E-RAB Setup Attempts for Incoming Handovers for a Specific Operator................................3379
6.1.4 Total Number of Successful E-RAB Setups for Incoming Handovers for a Specific Operator............................3383
6.1.5 E-RAB Setup Duration of a Specific Operator in a Cell....................................................................................... 3389
6.2 E-RAB Release Measurement per CNOperator (E-RAB.Rel.Cell.Operator).......................................................... 3391
6.2.1 Number of Abnormal E-RAB Releases for a Specific Operator...........................................................................3415
6.2.2 Number of Normal E-RAB Releases for a Specific Operator...............................................................................3420
6.2.3 Number of Normal E-RAB Releases for Outgoing Handovers for a Specific Operator in a Cell........................ 3427
6.2.4 Number of Abnormal E-RAB Releases for Outgoing Handovers for a Specific Operator...................................3433
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxix

BTS3203E
6.2.5 Number of Abnormal E-RAB Releases for Different Causes for a specific operator in a cell............................. 3440
6.2.6 Number of E-RAB Releases Initiated by the eNodeB Because of the S1 RESET for a Specific Operator..........3459
6.2.7 Number of Abnormal E-RAB Releases for Other Causes for a Specified Operator.............................................3465
6.3 Throughput and Data Volume Measurement per CNOperator (Traffic.Thruput.Cell.Operator)..............................3471
6.3.1 Uplink Traffic Volume for PDCP SDUs for a specified operator......................................................................... 3485
6.3.2 Receive Duration of Uplink PDCP SDUs for a specific Operator in a Cell..........................................................3490
6.3.3 Downlink Traffic Volume for PDCP SDUs for a Specific Operator in a Cell...................................................... 3495
6.3.4 Transmit Duration of Downlink PDCP SDUs for a Specific Operator in a Cell...................................................3500
6.3.5 Downlink Traffic Volume Sent in the Last TTI Before the Buffer Is empty for a Specific Operator................... 3505
6.3.6 Data Transmit Duration Except the Last TTI Before the Downlink Buffer Is Empty for a Specific Operator.....3510
6.3.7 Traffic Volume of Uplink PDCP PDUs Received in the Last TTI Before the UE Buffer is Empty for a Specific
Operator.......................................................................................................................................................................... 3515
6.3.8 Uplink Data Transmit Duration Except the Last TTI Before the UE Buffer is Empty for a Specific Operator... 3516
6.3.9 Uplink Traffic Volume of PDCP SDUs Scheduled for Small Packets for a Specific Operator............................ 3517
6.3.10 Uplink Data Transmission Duration Except that for Small Packets for a Specific Operator..............................3518
6.3.11 Total Duration of Data Transmission for a Specific Operator in a cell (with the Sampling Period of 1
Millisecond)....................................................................................................................................................................3519
6.3.12 Total Duration of UE Data Transmission for a Specific Operator in a Cell (with the Precision of 100 ms)...... 3521
6.3.13 Total Duration of Data Transmission for a Specific Operator in a Cell (with the Precision of 100 ms).............3522
6.3.14 Downlink MAC Traffic Volume for CA UEs of a Specific Operator................................................................. 3527
6.3.15 Downlink MAC Traffic volume of a Specific Operator in a Cell....................................................................... 3528
6.4 Cell User Quantity Measurement per CNOperator (Traffic.User.Cell.Operator).....................................................3530
6.4.1 Number of Users for a Specific Operator in a Cell............................................................................................... 3531
6.4.2 Number of UL Synchronized Users for a Specific Operator in a Cell.................................................................. 3532
6.4.3 Number of VoIP UEs of a Specific Operator in a Cell.......................................................................................... 3533
6.4.4 Number of times the licensed number of UEs is limited for a specific operator...................................................3535
6.4.5 Number of successful preemptions triggered by the limitation of the licensed number of UEs for a specific
operator........................................................................................................................................................................... 3537
6.5 PRB Measurement per CNOperator (Traffic.RB.Cell.Operator)............................................................................. 3539
6.5.1 Average Number of PDSCH PRBs Used by a Specific Operator......................................................................... 3540
6.5.2 Average Number of PUSCH PRBs Used by a Specific Operator......................................................................... 3542
6.5.3 Average Number of Uplink PRBs Used by PTT Services for a Specific Operator...............................................3544
6.5.4 Average Number of Downlink PRBs Used by PTT Services for a Specific Operator..........................................3545
6.5.5 Average Number of Other Operator Groups' Uplink PRBs Used by a Specific Operator in an Operator Resource
Group in a Cell............................................................................................................................................................... 3546
6.5.6 Average Number of Other Operator Groups' Downlink PRBs Used by a Specific Operator in an Operator
Resource Group in a Cell................................................................................................................................................3547
6.6 Outgoing Intra-RAT Handover Measurement per CNOperator (HO.eRAN.Out.Cell.Operator).............................3548
6.6.1 Number of Inter-eNodeB Outgoing Handover Attempts for a specified operator................................................ 3560
6.6.2 Number of Inter-eNodeB Outgoing Handover Executions for a Specific Operator............................................. 3563
6.6.3 Number of Successful Inter-eNodeB Outgoing Handovers for a specified operator............................................ 3567
6.6.4 Number of X2-based Outgoing Handover Attempts for a Specific Operator....................................................... 3573
6.6.5 Number of X2-based Outgoing Handover Executions for a Specific Operator.................................................... 3576
6.6.6 Number of Successful X2-based Outgoing Handovers for a specific operator.....................................................3579
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxx

BTS3203E
6.6.7 Number of Outgoing Blind Handover Attempts for a Specific Operator..............................................................3583

6.6.8 Number of Outgoing Blind Handover Executions for a Specific Operator...........................................................3586
6.6.9 Number of Successful Outgoing Blind Handovers for a Specific Operator..........................................................3589
6.6.10 Number of Load-based Inter-Frequency Handover Preparation Attempts for a Specific Operator....................3595
6.6.11 Number of Load-based Inter-Frequency Handover Executions for a Specific Operator.................................... 3598
6.6.12 Number of Successful Load-based Inter-Frequency Handovers for a Specific Operator................................... 3601
6.6.13 Number of Inter-eNodeB Outgoing Handover Attempts for UEs Performing Voice Services for a Specific
Operator in a Cell........................................................................................................................................................... 3607
6.6.14 Number of Inter-eNodeB Outgoing Handovers Executions for UEs Performing Voice Services for a Specific
Operator in a Cell............................................................................................................................................................3611
6.6.15 Number of Successful Inter-eNodeB Outgoing Handovers for UEs Performing Voice Services for a Specific
6.6.16 Number of Intra-eNodeB Outgoing Handover Attempts for UEs Performing Voice Services for a Specific
6.6.17 Number of Intra-eNodeB Outgoing Handovers Executions for UEs Performing Voice Services for a Specific
6.6.18 Number of Successful Intra-eNodeB Outgoing Handovers for UEs Performing Voice Services for a Specific
6.6.19 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During S1-based Outgoing
Handover Executions for a Specific Operator................................................................................................................ 3632
6.7 Outgoing Inter-RAT Handover Measurement per CNOperator (HO.IRAT.Out.Cell.Operator).............................. 3635
6.7.1 Number of Inter-RAT Handover Attempts from E-UTRAN to WCDMA Network for a Specific Operator....... 3644
6.7.2 Number of Inter-RAT Handover Executions from E-UTRAN to WCDMA Network for a Specific Operator.... 3646
6.7.3 Number of Successful Inter-RAT Handovers from E-UTRAN to WCDMA Network for a Specific Operator... 3648
6.7.4 Number of Inter-RAT Handover Attempts from E-UTRAN to GERAN for a Specific Operator........................ 3650
6.7.5 Number of Inter-RAT Handover Executions from E-UTRAN to GERAN for a Specific Operator..................... 3652
6.7.6 Number of Successful Inter-RAT Handovers from E-UTRAN to GERAN for a Specific Operator.................... 3653
6.7.7 Number of Inter-RAT Blind Handover Attempts from E-UTRAN to Another System for a Specific Operator.. 3655
6.7.8 Number of Inter-RAT Blind Handover Executions from E-UTRAN to Another System for a Specific Operator
........................................................................................................................................................................................ 3657
6.7.9 Number of Successful Inter-RAT Blind Handovers from E-UTRAN to Another System for a Specific Operator
........................................................................................................................................................................................ 3660
6.7.10 Number of Inter-RAT Redirections from E-UTRAN to Another System for a Specific Operator..................... 3662
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............................................................................................................................................3664
6.7.12 Number of Indicators for CSFB to Another System for a Specific Operator......................................................3667
6.7.13 Number of CSFB Responses to MMEs for a Specific Operator......................................................................... 3669
6.7.14 Number of Times of CSFB to Another System...................................................................................................3671
6.7.15 Number of SRVCC-based Outgoing Handover Attempts from E-UTRAN to WCDMA Network for a Specific
Operator.......................................................................................................................................................................... 3676
6.7.16 Number of SRVCC-based Outgoing Handover Executions from E-UTRAN to WCDMA Network for a Specific
Operator.......................................................................................................................................................................... 3678
6.7.17 Number of Successful Outgoing Handovers from E-UTRAN to WCDMA Network for a Specified Operator 3680
6.7.18 Number of SRVCC-based Outgoing Handover Attempts from E-UTRAN to GERAN for a Specific Operator
........................................................................................................................................................................................ 3682
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxxi

BTS3203E
6.7.19 Number of SRVCC-based Outgoing Handover Executions from E-UTRAN to GERAN for a Specific Operator
........................................................................................................................................................................................ 3684
6.7.20 Number of Successful SRVCC-based Outgoing Handovers from E-UTRAN to GERAN for a Specific Operator
........................................................................................................................................................................................ 3686
Handover Executions for a Specific Operator................................................................................................................ 3688
Handover Executions for SRVCC for a Specific Operator............................................................................................ 3690
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....................................................................................................... 3693
6.8 E-RAB Establish Failure Measurement per CNOperator (E-RAB.EstFail.Cell.Operator)......................................3694
6.8.1 Number of E-RAB Setup Failures for Different Causes for a Specific Operator in a Cell................................... 3706
6.8.2 Number of E-RAB Setup Failures for Other Causes in a Cell for a Specific Operator........................................ 3730
6.9 Throughput Distribution Measurement per CNOperator (Traffic.Thruput.PDF.Cell.Operator).............................. 3735
6.9.1 Distribution of the Downlink Throughput in a Cell for a Specific Operator.........................................................3762
6.9.2 Distribution of the Uplink Throughput in a Cell for a Specific Operator............................................................. 3812
6.10 Paging Measurement per CNOperator (Paging.Cell.Operator)..............................................................................3817
6.10.1 Number of Received Paging Messages over the S1 Interface for a Specific Operator in a Cell.........................3818
6.11 Voice Quality Measurementper CNOperator (VoiceQuality.Cell.Operator).......................................................... 3819
6.11.1 Uplink and Downlink Voice Quality for a Specific Operator..............................................................................3822
6.12 Packet Measurement per CNOperator (Traffic.Packet.Cell.Operator)...................................................................3830
6.12.1 Total Number of Discarded Uplink PDCP SDUs for DRB Services for a Specific Operator in a Cell.............. 3833
6.12.2 Total Number of Expected Uplink Data Packets for DRB Services for a Specific Operator in a Cell............... 3834
6.12.3 Number of Successfully Transmitted Downlink PDCP SDUs for DRB Services for a Specific Operator in a Cell
........................................................................................................................................................................................ 3836
6.12.4 Total Processing Delay of Downlink PDCP SDUs for DRB Services for a Specific Operator in a Cell............3837
6.12.5 Total Number of Discarded downlink PDCP SDUs for DRB Services for a Specific Operator in a Cell.......... 3839
6.12.6 Total Number of Expected downlink Data Packets for DRB Services for a Specific Operator in a Cell........... 3841
6.13 PDCP Measurement per CNOperator (Traffic.PDCP.Cell.Operator).....................................................................3842
6.13.1 Number of Discarded Downlink PDCP SDUs for a Specific Operator.............................................................. 3844
6.13.2 Number of Transmitted Downlink Traffic PDCP SDUs for a Specific Operator............................................... 3845
6.14 Cell MBMS Measurement per CNOperator (MBMS.Cell.Operator).................................................................... 3846
6.14.1 Number of Bits of MBMS Services Scheduled for a Specific Operator in a Cell...............................................3848
6.14.2 Number of Bits of MBMS Services Received for a Specific Operator in a Cell................................................ 3849
6.14.3 Number of SYNC SDUs Received for MBMS Services for a Specific Operator in a Cell................................ 3850
6.14.4 Number of SYNC PDUs of MBMS Services Discarded for a Specific Operator in a Cell................................ 3851
6.15 CA Measurement per CNOperator (CA.Cell.Operator)......................................................................................... 3852
6.15.1 Number of Abnormal E-RAB Releases for CA UEs in the Downlink CA State of a Specific Operator............3853
6.15.2 Number of Normal E-RAB Releases for CA UEs in the Downlink CA State of a Specific Operator................3856
6.15.3 Average Number of CA UEs of a Specific Operator in the Downlink CA State................................................ 3859
6.15.4 Numbers of SCell Additions and Removals for UEs in the Downlink CA State of a Specific Operator........... 3860
6.15.5 Number Downlink PRBs Occupied by CA UEs of a Specific Operator in a Cell.............................................. 3866
6.16 Cell Algorithm Measurement per CNOperator (Algo.Cell.Operator)....................................................................3867
6.16.1 Duration of Cell Unavailability Due to S1 Interface Faults for a Specific Operator.......................................... 3868
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxxii

BTS3203E
7 Measurement of EUTRAN Cell-to-GERAN Cell Handover Performance

(ECELL_GCELL)......................................................................................................................... 3870
7.1 EUTRAN Cell-to-GERAN Cell Handover Measurement (IRATHO.NCell.GCell)................................................ 3871
7.1.1 Number of Handover Attempts from a Specific E-UTRAN Cell to a Specific GERAN Cell.............................. 3872
7.1.2 Number of Handover Executions from a Specific E-UTRAN Cell to a Specific GERAN Cell........................... 3874
7.1.3 Number of Successful Handovers from a Specific E-UTRAN Cell to a Specific GERAN Cell.......................... 3875
8 Measurement of EUTRAN Cell-to-WCDMA Cell Handover Performance

(ECELL_WCELL).........................................................................................................................3877
8.1 EUTRAN Cell-to-WCDMA Cell Handover Measurement (IRATHO.NCell.WCell)............................................. 3878
8.1.1 Number of Handover Attempts from a Specific E-UTRAN Cell to a Specific WCDMA Cell............................ 3879
8.1.2 Number of Handover Executions from a Specific E-UTRAN Cell to a Specific WCDMA Cell......................... 3881
8.1.3 Number of Successful Handovers from a Specific E-UTRAN Cell to a Specific WCDMA Cell........................ 3882
9 Measurement of Cell Sector Equipment Performance (CellSectorEQUIP)................. 3884

9.1 Cell Sector Equipment Physical Layer Measurement (ChMeas.PHY.CellSectorEQUIP)....................................... 3885
9.1.1 RSSI of Every Antenna in a Set of Cell Sector Equipment...................................................................................3888
9.1.2 Average IN of a Receive Antenna Channel in a Set of Cell Sector Equipment.................................................... 3895
10 Measurement of Board Service Performance (Board.Service)...................................... 3898

10.1 Board User Quantity Measurement (L.Traffic.Board)........................................................................................... 3899
10.1.1 Maximum Number of Scheduled UEs per TTI in the Downlink in Cells Served by a Baseband Processing Unit
........................................................................................................................................................................................ 3900
10.1.2 Maximum Total Number of Scheduled UEs per TTI in the Uplink and Downlink in Cells Served by a Baseband
Processing Unit...............................................................................................................................................................3901
10.1.3 Maximum Number of Scheduled UEs per TTI in the Uplink in Cells Served by a Baseband Processing Unit. 3902
10.1.4 Maximum Number of UL-Sync UEs Served by a BBP...................................................................................... 3903
10.1.5 Maximum Number of UEs Served by a BBP......................................................................................................3904
10.2 eNodeB Board Call Processing Measurement (Call Attempt.Board).................................................................... 3905
10.2.1 Number of Call Processing Times in a Board..................................................................................................... 3906
10.3 eNodeB Board User-Plane CPU Measurement (UserPlane.CPU.Board).............................................................. 3908
10.3.1 Maximum and Average User-Plane CPU Usage of a Board in an eNodeB........................................................ 3909
10.3.2 Number of Times the User-Plane CPU Usage of a Board in an eNodeB Is Greater Than the Preset Threshold.
........................................................................................................................................................................................ 3910
Index..............................................................................................................................................3911
Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxxiii

BTS3203E
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 Setup Measurement(RRC.Setup.Cell)
RRC.SetupFail.Cell RRC Setup Failure

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

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

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

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

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

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

RAB.Modify.Cell)
Algo.Cell Cell Algorithm Measurement(Algo.Cell)
Traffic.DRB.Cell DRB Measurement(Traffic.DRB.Cell)
Issue 03 (2017-03-10) Huawei Proprietary and Confidential 1

BTS3203E
Traffic.Thruput.Cell Throughput and Data Volume

Measurement(Traffic.Thruput.Cell)
Traffic.PDCP.Cell PDCP Measurement(Traffic.PDCP.Cell)
Paging.Cell Paging Measurement(Paging.Cell)
SecurMode.Cell Security Mode

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

Measurement(ChMeas.Pwr.Cell)
ChMeas.MIMO.Cell MIMO Measurement(ChMeas.MIMO.Cell)
ChMeas.CQI.Cell CQI Measurement(ChMeas.CQI.Cell)
ChMeas.MCS.Cell MCS Measurement(ChMeas.MCS.Cell)
ChMeas.PRB.Cell PRB Measurement(ChMeas.PRB.Cell)
Traffic.MAC.Cell MAC Measurement(Traffic.MAC.Cell)
Traffic.User.Cell Cell User Quantity

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

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

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

Measurement(HO.eRAN.Out.Cell)
HO.eRAN.In.Cell Incoming Intra-RAT Handover

Measurement(HO.eRAN.In.Cell)
HO.eRAN.X2Out.Cell Outgoing Intra-RAT Handover

Measurement over
X2(HO.eRAN.X2Out.Cell)
HO.DRX.Out.Cell Outgoing Intra-RAT Handover

Measurement in DRX(HO.DRX.Out.Cell)
Traffic.Packet.Cell Packet Measurement(Traffic.Packet.Cell)
ChMeas.DFEE.Cell DFEE Measurement(ChMeas.DFEE.Cell)
LCS.Cell Cell LCS Measurement(LCS.Cell)
EMC.Cell Cell Emergency Call

Measurement(EMC.Cell)

BTS3203E
UeCntx.Rel.Cell UE Context Release

Measurement(UeCntx.Rel.Cell)
UeCntx.Mod.Cell UE Context Modification

Measurement(UeCntx.Mod.Cell)
CA.Cell CA Measurement(CA.Cell)
Traffic.RLC.Cell RLC Measurement(Traffic.RLC.Cell)
Reserve.Cell Cell Reserved Counter

Measurement(Reserve.Cell)
ChMeas.MeasRpt.Cell MR Measurement(ChMeas.MeasRpt.Cell)
UeCntx.Est.Cell UE Context Setup

Measurement(UeCntx.Est.Cell)
UeCntx.EstFail.Cell UE Context Setup Failure

Measurement(UeCntx.EstFail.Cell)
HO.eRAN.X2In.Cell Incoming Intra-RAT Handover

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

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

Measurement(Traffic.Packet.PDF.Cell)
MBMS.Cell Cell MBMS Measurement(MBMS.Cell)
ChMeas.CQI.CA.SCell SCell CQI

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

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

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

1(Traffic.Thruput.Cell.1)
ChMeas.MCS1.Cell MCS Measurement 1(ChMeas.MCS1.Cell)
HO.IRAT.Out.Cell.1 Outgoing Inter-RAT Handover

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

Measurement 1(HO.eRAN.Out.Cell.1)
ChMeas.Pwr1.Cell Channel Quality

Measurement1(ChMeas.Pwr1.Cell)

BTS3203E
ResOpt.Cell Resource Optimization

Measurement(ResOpt.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)
Traffic.Service.AttEst.Cell Service Setup

Measurement(Traffic.Service.AttEst.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)
ChMeas.MDT.Cell MDT Measurement(ChMeas.MDT.Cell)
Algo1.Cell Cell Algorithm Measurement1(Algo1.Cell)
ExtendedQci.Cell Extended QCI

Measurement(ExtendedQci.Cell)
MroMeas.IntraRat.Cell Intra-RAT MRO

Measurement(MroMeas.IntraRat.Cell)
ChMeas.Pwr2.Cell Channel Quality

Measurement2(ChMeas.Pwr2.Cell)
AMBR.Cell AMBR Measurement(AMBR.Cell)

BTS3203E
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 Introduced in
Description Version...
1526726657 L.RRC.ConnReq. Number of RRC BTS3203E LTE:

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

tt connection setup V100R006C00
attempts performed
by UEs in a cell
(retransmission
excluded)
1526726659 L.RRC.ConnReq.S Number of RRC BTS3203E LTE:

ucc connection setup version earlier than
completion times V100R003C00

BTS3203E

1526728216 L.RRC.ConnSetup Number of RRC BTS3203E LTE:

Connection Setup V100R006C00
messages sent to
UEs in a cell

tt.Emc connection setup V100R006C00
attempts with a
cause value of
emergency
performed by UEs in
a cell
(retransmission
excluded)

tt.HighPri connection setup V100R006C00
attempts with a
cause value of
highPriorityAccess
performed by UEs in
a cell
(retransmission
excluded)

tt.Mt connection setup V100R006C00
attempts with a
cause value of mt-
Access performed
by UEs in a cell
(retransmission
excluded)

tt.MoSig connection setup V100R006C00
attempts with a
cause value of mo-
Signalling
performed by UEs in
a cell
(retransmission
excluded)

BTS3203E


tt.MoData connection setup V100R006C00
attempts with a
cause value of mo-
Data performed by
UEs in a cell
(retransmission
excluded)

ucc.Emc Connection Setup V100R006C00
Complete messages
with a cause value
of emergency
received from UEs
in a cell

ucc.HighPri Connection Setup V100R006C00
Complete messages
with a cause value
of
highPriorityAccess
received from UEs
in a cell

ucc.Mt Connection Setup V100R006C00
Complete messages
with a cause value
of mt-Access
received from UEs
in a cell

ucc.MoSig Connection Setup V100R006C00
Complete messages
with a cause value
of mo-signalling
received from UEs
in a cell

ucc.MoData Connection Setup V100R006C00
Complete messages
with a cause value
of mo-Data received
from UEs in a cell

BTS3203E


tt.DelayTol connection setup V100R006C00
attempts with a
cause value of
delayTolerantAc-
cess-v1020
performed by UEs in
a cell
(retransmission
excluded)

ucc.DelayTol Connection Setup V100R006C00
Complete messages
with a cause value
of delayTolerantAc-
cess-v1020 received
from UEs in a cell
1526728438 L.RRC.StateTrans. Number of times a BTS3203E LTE:

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

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

TimeAvg connection setup V100R006C00
duration
1526728775 L.RRC.ConnSetup. Maximum RRC BTS3203E LTE:

TimeMax connection setup V100R006C00
duration
1526729656 L.RRC.StateTrans. Number of BTS3203E LTE:

Unsyn2Syn.Succ successfully V100R007C00
recovered RRC
connections when
UEs switch from the
uplink out-of-
synchronization
synchronized state

BTS3203E


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

Msg.HighPri connection setup V100R009C00
attempts with a
cause value of
highPriorityAccess
performed by UEs in
a cell
(retransmission
included)

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

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

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

BTS3203E


Msg.DelayTol connection setup V100R009C00
attempts with a
cause value of
delayTolerantAc-
cess-v1020
performed by UEs in
a cell
(retransmission
included)
1526730846 L.RRC.ConnReq. Maximum number BTS3203E LTE:

Max of RRC Connection V100R011C10
Request messages
received by a cell
from UEs (including
the discarded ones)

Msg.MoVoiceCall connection setup V100R012C10
attempts with a
cause value mo-
VoiceCall-v1280
(retransmission
included)

tt.MoVoiceCall connection setup V100R012C10
attempts with a
cause value mo-
VoiceCall-v1280
1526745658 L.RRC.ConnReq.S Number of BTS3203E LTE:

ucc.MoVoiceCall successful RRC V100R012C10
connection setups
with a cause value
mo-VoiceCall-v1280
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

BTS3203E
L.RRC.ConnReq.Msg.Mt
L.RRC.ConnReq.Msg.MoSig
L.RRC.ConnReq.Msg.MoData
L.RRC.ConnReq.Msg.DelayTol
L.RRC.ConnReq.Msg.MoVoiceCall
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
L.RRC.ConnReq.Succ.MoVoiceCall
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 BTS3203E LTE L

q.Msg RRC
connection
setup requests
(retransmission
included)

BTS3203E


q.Att RRC
connection
setup attempts
performed by
UEs in a cell
(retransmission
excluded)

q.Att.Emc RRC
connection
setup attempts
with a cause
value of
emergency
performed by
UEs in a cell
(retransmission
excluded)

q.Att.HighPri RRC
connection
setup attempts
with a cause
value of
highPriorityAcc
ess performed
by UEs in a cell
(retransmission
excluded)

q.Att.Mt RRC
connection
setup attempts
with a cause
value of mt-
Access
performed by
UEs in a cell
(retransmission
excluded)

BTS3203E


q.Att.MoSig RRC
connection
setup attempts
with a cause
value of mo-
Signalling
performed by
UEs in a cell
(retransmission
excluded)

q.Att.MoData RRC
connection
setup attempts
with a cause
value of mo-
Data performed
by UEs in a cell
(retransmission
excluded)

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

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

BTS3203E


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

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

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

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

BTS3203E


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

q.Msg.MoVoice RRC
Call connection
setup attempts
with a cause
value mo-
VoiceCall-
v1280
(retransmission
included)

q.Att.MoVoice RRC
Call connection
setup attempts
with a cause
value mo-
VoiceCall-
v1280
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.

BTS3203E
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.
The L.RRC.ConnReq.Msg.MoVoiceCall counter is incremented by 1 each time the
Establishment Cause IE in the RRC Connection Request message is "mo-VoiceCall-v1280".
The number of retransmitted RRC Connection Request messages is also calculated.
The L.RRC.ConnReq.Att.MoVoiceCall counter is incremented by 1 each time the
Establishment Cause IE in the RRC Connection Request message is "mo-VoiceCall-v1280".
The number of retransmitted RRC Connection Request messages is not calculated.

BTS3203E
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
Management
L.RRC.ConnReq.Att Multi-mode: None

GSM: None
UMTS: None
Management

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

GSM: None
UMTS: None
LOFD-00110501 Management
Dynamic DRX
L.RRC.ConnReq.Att.HighPr Multi-mode: None

i GSM: None
UMTS: None
Dynamic DRX
L.RRC.ConnReq.Att.Mt Multi-mode: None

GSM: None
UMTS: None
Dynamic DRX
L.RRC.ConnReq.Att.MoSig Multi-mode: None

GSM: None
UMTS: None
Dynamic DRX
L.RRC.ConnReq.Att.MoDat Multi-mode: None

a GSM: None
UMTS: None
Dynamic DRX
L.RRC.ConnReq.Att.Delay Multi-mode: None

Tol GSM: None
UMTS: None
Dynamic DRX

BTS3203E
L.RRC.ConnReq.Msg.Emc Multi-mode: None

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

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

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

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

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

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

oiceCall GSM: None
UMTS: None
Dynamic DRX

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

ceCall GSM: None
UMTS: None
Dynamic DRX
1.1.2 Number of Successful RRC Connection Setups in a Cell

Counters

q.Succ RRC
connection
setup
completion
times

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

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

BTS3203E


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

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

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

q.Succ.DelayTo RRC
l Connection
Setup Complete
messages with a
cause value of
delayTolerantA
ccess-v1020
received from
UEs in a cell

q.Succ.MoVoic successful RRC
eCall connection
setups with a
cause value mo-
VoiceCall-
v1280

BTS3203E
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".
The L.RRC.ConnReq.Succ.MoVoiceCall counter is incremented by 1 each time the eNodeB
receives the message from a UE and the Establishment Cause IE in the RRC Connection
Request message is "mo-VoiceCall-v1280".

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

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

GSM: None
UMTS: None
Management

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

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

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

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

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

yTol GSM: None
UMTS: None
Management
L.RRC.ConnReq.Succ.MoV Multi-mode: None

oiceCall GSM: None
UMTS: None
Management

BTS3203E
1.1.3 Number of RRC Connection Setup Attempts in a Cell

Counters
1526728216 L.RRC.ConnSe Number of BTS3203E LTE L

tup RRC
Connection
Setup messages
sent to UEs in a
cell
Description
The counter measures the number of RRC connection setup attempts in a cell. That is, the
counter measures the number of times that the eNodeB sends an RRC Connection Setup
message to the UE after receiving a non-retransmitted RRC Connection Request message
from the UE. The RRC Connection Setup message is an RRC signaling message that the
eNodeB sends to the UE. The message is used to inform the UE of the RRC connection setup
result and the related configuration information.
Measurement Points
As shown at point B in Figure 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

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

GSM: None
UMTS: None
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 BTS3203E LTE L

ns.Syn2Unsyn times a UE
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.

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

yn GSM: None
UMTS: None
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
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.

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

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

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

tup.TimeMax connection
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 Complete message.
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.

BTS3203E
Figure 1-5
Formula
None
Unit
ms
Related Features
L.RRC.ConnSetup.TimeAvg Multi-mode: None

GSM: None
UMTS: None
Management
L.RRC.ConnSetup.TimeMa Multi-mode: None

x GSM: None
UMTS: None
Management

BTS3203E
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
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.
Measurement Points
As shown at point B in Figure 1-6 and Figure 1-7, 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 or an RRC Connection
Reestablishment Request message from a UE which indicating that the eNodeB finishes
uplink PUCCH resource allocation for the UE.

BTS3203E
Figure 1-6
Figure 1-7
Formula
None
Unit
None
Related Features
L.RRC.StateTrans.Unsyn2S Multi-mode: None

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

BTS3203E
1.1.8 Maximum Number of RRC Connection Setup Requests in a

Cell
Counters
1526730846 L.RRC.ConnRe Maximum BTS3203E LTE L

q.Max number of RRC
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
Management

BTS3203E
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-8 shows the
measurement points in a failed RRC connection setup procedure.
Figure 1-8
Counters
1526727083 L.RRC.SetupFail.R Number of RRC BTS3203E LTE:

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

oReply connection setup V100R006C00
failures due to no
responses from the
UE

ej Connection Reject V100R006C00
messages sent to
UEs in a cell

BTS3203E


esFail.SRS connection setup V100R006C00
failures due to SRS
resource allocation
failure

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

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

ej.FlowCtrl eNodeB sends an V100R006C00
RRC Connection
Reject message to
the UE due to flow
control

esFail.UserSpec connection setup V100R007C00
failures because of
limitation of UE
number specification

ej.MMEOverload eNodeB sends an V100R007C00
RRC Connection
Reject message to
the UE due to MME
overload

ej.Other connection setup V100R011C10
requests rejected due
to other causes

esFail.Other connection setup V100R011C10
failures due to other
resource allocation
failure

BTS3203E

1526737854 L.RRC.ReEstFail. Number of times the BTS3203E LTE:

Disc.FlowCtrl RRC Connection V100R011C10
Reestablishment
Request messages
are discarded due to
flow control
1526741885 L.RRC.ConnReq. Number of times BTS3203E LTE:

Msg.disc.Illegal RRC Connection V100R011C10
Request messages
are discarded
because the
messages are illegal

ej.ForbidAc eNodeB sends RRC V100R011C10
Connection Reject
messages because
the distance between
UEs access the cell
out of the coverage
area
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

BTS3203E
L.RRC.SetupFail.Rej.MME -
Overload
L.RRC.SetupFail.Rej.Forbid -
Ac
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 BTS3203E LTE L

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

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

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

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

BTS3203E


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

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

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

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

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

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

BTS3203E


il.ResFail.Other RRC
connection
setup failures
due to other
resource
allocation
failure

q.Msg.disc.Illeg times RRC
al Connection
Request
messages are
discarded
because the
messages are
illegal

il.Rej.ForbidAc times the
eNodeB sends
RRC
Connection
Reject
messages
because the
distance
between UEs
access the cell
out of the
coverage area
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-9, 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

BTS3203E
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-10, 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-9, 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-9, 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-9, 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-9, 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, the distance between UEs
access the cell out of the coverage area, or MME overloaded.
As shown at point A in Figure 1-9, 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-11, 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.
As shown at point A in Figure 1-11, the L.RRC.ConnReq.Msg.disc.Illegal counter is
incremented by 1 each time the cell discards an RRC Connection Request message sent from
a UE because the message is illegal. The measurement counts retransmitted RRC Connection
Request messages in.
As shown at point A in Figure 1-9, the L.RRC.SetupFail.Rej.ForbidAc counter is
incremented by 1 each time the cell receives an RRC Connection Request message and the
distance from the UE access point to the cell center exceeds the cell radius.

BTS3203E
Figure 1-9
Figure 1-10
Figure 1-11

BTS3203E
Formula
None
Unit
None
Related Features
L.RRC.SetupFail.ResFail Multi-mode: None

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

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

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

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

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

FlowCtrl GSM: None
UMTS: None
Management

BTS3203E
L.RRC.SetupFail.Rej.FlowC Multi-mode: None

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

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

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

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

her GSM: None
UMTS: None
Management
L.RRC.ConnReq.Msg.disc.I Multi-mode: None

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

Ac GSM: None
UMTS: None
LTE: LOFD-002015 RACH Optimization

BTS3203E
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-12 shows the measurement points in an RRC
connection reestablishment procedure.
Figure 1-12
Counters
1526727085 L.RRC.ReEst.Att Number of RRC BTS3203E LTE:

connection V100R006C00
reestablishment
requests

BTS3203E

1526727086 L.RRC.ReEst.Succ Number of BTS3203E LTE:

successful RRC V100R006C00
connection
reestablishments
1526727087 L.RRC.ReEst.Reco Number of RRC BTS3203E LTE:

nfFail.Att connection V100R006C00
reestablishment
requests triggered by
reconfiguration
failures
1526727088 L.RRC.ReEst.Reco Number of BTS3203E LTE:

nfFail.Succ successful RRC V100R006C00
connection
reestablishments
triggered by
reconfiguration
failures
1526727090 L.RRC.ReEst.HoF Number of RRC BTS3203E LTE:

ail.Att connection V100R006C00
reestablishment
requests triggered by
failed handovers
1526727091 L.RRC.ReEst.HoF Number of BTS3203E LTE:

ail.Succ successful RRC V100R006C00
connection
reestablishments
triggered by failed
handovers
1526730536 L.RRC.ReEst.Non Number of RRC BTS3203E LTE:

Srccell.Att connection V100R007C00
reestablishment
requests to another
cell
1526730537 L.RRC.ReEst.Non Number of BTS3203E LTE:

Srccell.Succ successful RRC V100R007C00
connection
reestablishment
times to another cell
1526741802 L.RRC.NoCntxRe Number of RRC BTS3203E LTE:

Est.Att connection V100R011C10
reestablishment
attempts without UE
contexts

BTS3203E


Est.ReconfFail.Att connection V100R011C10
reestablishment
attempts without UE
contexts triggered
by reconfiguration
failures

Est.HoFail.Att connection V100R011C10
reestablishment
attempts without UE
contexts triggered
by handover failures
1526741805 L.RRC.NoCntxRe Number of BTS3203E LTE:

Est.Succ successful RRC V100R011C10
connection
reestablishments
without UE contexts

Est.ReconfFail.Suc successful RRC V100R011C10
c connection
reestablishments
without UE contexts
triggered by
reconfiguration
failures

Est.HoFail.Succ successful RRC V100R011C10
connection
reestablishments
without UE contexts
triggered by
handover failures
1526745675 L.RRC.ReEst.Succ. Number of BTS3203E LTE:

QCI.1 successful RRC V100R012C10
connection
reestablishments
with QCI 1 bearers
1526745976 L.RRC.ReEst.Att. Number of BTS3203E LTE:

Act reestablishment V100R012C10
requests of active
RRC connections

BTS3203E

1526745977 L.RRC.ReEst.Succ. Number of BTS3203E LTE:

Act successful V100R012C10
reestablishments of
active RRC
connections
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.Att.Act
L.RRC.ReEst.Succ L.RRC.ReEst.ReconfFail.Succ
L.RRC.ReEst.HoFail.Succ
L.RRC.ReEst.NonSrccell.Succ
L.RRC.ReEst.Succ.Act
L.RRC.NoCntxReEst.Att L.RRC.NoCntxReEst.ReconfFail.Att
L.RRC.NoCntxReEst.HoFail.Att
L.RRC.NoCntxReEst.Succ L.RRC.NoCntxReEst.ReconfFail.Succ
L.RRC.NoCntxReEst.HoFail.Succ

BTS3203E
1.3.1 Number of RRC Connection Reestablishment Requests in a

Cell
Counters
1526727085 L.RRC.ReEst.A Number of BTS3203E LTE L

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

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

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

onSrccell.Att RRC
connection
reestablishment
requests to
another cell
1526741802 L.RRC.NoCntx Number of BTS3203E LTE L

ReEst.Att RRC
connection
reestablishment
attempts
without UE
contexts

BTS3203E


ReEst.ReconfFa RRC
il.Att connection
reestablishment
attempts
without UE
contexts
triggered by
reconfiguration
failures

ReEst.HoFail.A RRC
tt connection
reestablishment
attempts
without UE
contexts
triggered by
handover
failures
1526745976 L.RRC.ReEst.A Number of BTS3203E LTE L

tt.Act reestablishment
requests of
active RRC
connections
Description
The counters measure the number of RRC connection reestablishment requests for different
causes in a cell. The RRC Connection Reestablishment Request message is an RRC signaling
message sent by the UE. The message is used to recover the RRC signaling connection.
Measurement Points
As shown at point A in Figure 1-13, 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. In addition, the
L.RRC.ReEst.Att.Act counter is incremented by 1 if any E-RAB of the UE carries data in the
uplink or downlink.
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".

BTS3203E
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-13
Formula
None
Unit
None
Related Features
L.RRC.ReEst.Att Multi-mode: None

GSM: None
UMTS: None
Management

BTS3203E
L.RRC.ReEst.ReconfFail.At Multi-mode: None

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

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

t GSM: None
UMTS: None
Management
L.RRC.NoCntxReEst.Att Multi-mode: None

GSM: None
UMTS: None
Management
L.RRC.NoCntxReEst.Recon Multi-mode: None

fFail.Att GSM: None
UMTS: None
Management
L.RRC.NoCntxReEst.HoFai Multi-mode: None

l.Att GSM: None
UMTS: None
Management
L.RRC.ReEst.Att.Act Multi-mode: None

GSM: None
UMTS: None
Management

BTS3203E
1.3.2 Number of Successful RRC Connection Reestablishments in

a Cell
Counters
1526727086 L.RRC.ReEst.S Number of BTS3203E LTE L

ucc successful RRC
connection
reestablishment
s

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

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

onSrccell.Succ successful RRC
connection
reestablishment
times to another
cell

ReEst.Succ successful RRC
connection
reestablishment
s without UE
contexts

ReEst.ReconfFa successful RRC
il.Succ connection
reestablishment
s without UE
contexts
triggered by
reconfiguration
failures

BTS3203E


ReEst.HoFail.S successful RRC
ucc connection
reestablishment
s without UE
contexts
triggered by
handover
failures

ucc.QCI.1 successful RRC
connection
reestablishment
s with QCI 1
bearers

ucc.Act successful
reestablishment
s of active RRC
connections
Description
The counters measure the number of successful RRC connection reestablishments for
different causes in a cell. The RRC Connection Reestablishment Complete message is an
RRC signaling message sent from the UE to the eNodeB. The message is used to inform the
eNodeB that the RRC connection reestablishment is completed.
Measurement Points
As shown at point B in Figure 1-14, the corresponding counter is incremented by 1 each time
the eNodeB receives an RRC Connection Reestablishment Complete message from the UE.
The L.RRC.ReEst.Succ counter is incremented by 1 each time the eNodeB receives the
message from the UE. In addition, the L.RRC.ReEst.Succ.Act counter is incremented by 1 if
any E-RAB of the UE carries data in the uplink or downlink. If the UE has QCI 1 bearers, the
L.RRC.ReEst.Succ.QCI.1 counter is incremented by 1.
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.

BTS3203E
Figure 1-14
Formula
None
Unit
None
Related Features
L.RRC.ReEst.Succ Multi-mode: None

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

cc GSM: None
UMTS: None
Management

BTS3203E
L.RRC.ReEst.HoFail.Succ Multi-mode: None

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

cc GSM: None
UMTS: None
Management
L.RRC.NoCntxReEst.Succ Multi-mode: None

GSM: None
UMTS: None
Management
L.RRC.NoCntxReEst.Recon Multi-mode: None

fFail.Succ GSM: None
UMTS: None
Management
L.RRC.NoCntxReEst.HoFai Multi-mode: None

l.Succ GSM: None
UMTS: None
Management
L.RRC.ReEst.Succ.QCI.1 Multi-mode: None

GSM: None
UMTS: None
Management
L.RRC.ReEst.Succ.Act Multi-mode: None

GSM: None
UMTS: None
Management

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

BTS3203E
Counters
1526727089 L.RRC.ReEst.Reco Number of rejected BTS3203E LTE:

nfFail.Rej RRC connection V100R006C00
reestablishment
attempts triggered
by reconfiguration
failures
1526727092 L.RRC.ReEst.HoF Number of rejected BTS3203E LTE:

ail.Rej RRC connection V100R006C00
reestablishment
attempts triggered
by handover failures
1526727093 L.RRC.ReEstFail. Number of RRC BTS3203E LTE:

ResFail connection V100R006C00
reestablishment
failures due to failed
resource allocations

NoReply connection V100R006C00
reestablishment
failures due to no
responses from the
UE
1526728270 L.RRC.ReEstFail. Total number of BTS3203E LTE:

Rej RRC connection V100R006C00
reestablishment
rejections

NoCntx connection V100R006C00
reestablishment
failures due to
unavailability of UE
contexts

NoCntx.PreProcFa connection V100R011C10
il reestablishment
failures due to UE
context
unavailability
caused by the pre-
processing failure

BTS3203E


VoIPPref reestablishment V100R011C10
failures caused by
voice service
preferential access
1526741808 L.RRC.NoCntxRe Number of rejected BTS3203E LTE:

EstFail.Rej RRC connection V100R011C10
reestablishment
attempts without UE
contexts

EstFail.ResFail RRC connection V100R011C10
reestablishment
attempts without UE
contexts due to
resource allocation
failures

EstFail.NoReply RRC connection V100R011C10
reestablishment
attempts without UE
contexts due to no
responses from Ues
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.Rej
L.RRC.ReEst.HoFail.Rej
L.RRC.ReEstFail.Rej L.RRC.ReEstFail.ResFail
L.RRC.ReEstFail.NoCntx
L.RRC.NoCntxReEstFail.Rej L.RRC.NoCntxReEstFail.ResFail
L.RRC.NoCntxReEstFail.NoReply

BTS3203E
1.4.1 Number of RRC Connection Reestablishment Failures for

Different Causes in a Cell
Counters
1526737854 L.RRC.ReEstFa Number of BTS3203E LTE L

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

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

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

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

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

BTS3203E

1526728270 L.RRC.ReEstFa Total number of BTS3203E LTE L

il.Rej RRC
connection
reestablishment
rejections

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

il.NoCntx.PrePr RRC
ocFail connection
reestablishment
failures due to
UE context
unavailability
caused by the
pre-processing
failure

il.VoIPPref RRC
reestablishment
failures caused
by voice service
preferential
access

ReEstFail.Rej rejected RRC
connection
reestablishment
attempts
without UE
contexts

ReEstFail.ResF rejected RRC
ail connection
reestablishment
attempts
without UE
contexts due to
resource
allocation
failures

BTS3203E


ReEstFail.NoRe rejected RRC
ply connection
reestablishment
attempts
without UE
contexts due to
no responses
from Ues
Description
The counters measure the number of RRC connection reestablishment failures due to different
causes in a cell. The RRC Connection Reestablishment Reject message is an RRC signaling
message sent from the eNodeB to the UE to inform the UE that the reestablishment is rejected
by the eNodeB.
Measurement Points
As shown at point A in Figure 1-16, 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.
As shown at point A in Figure 1-17, 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.

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

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

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

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

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

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

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

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

GSM: None
UMTS: None
Management

BTS3203E
L.RRC.ReEstFail.NoCntx.P Multi-mode: None

reProcFail GSM: None
UMTS: None
Management
L.RRC.NoCntxReEstFail.R Multi-mode: None

ej GSM: None
UMTS: None
Management
L.RRC.NoCntxReEstFail.R Multi-mode: None

esFail GSM: None
UMTS: None
Management
L.RRC.NoCntxReEstFail.N Multi-mode: None

oReply GSM: None
UMTS: None
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.

BTS3203E
Figure 1-18

BTS3203E
Figure 1-19
Counters
1526726668 L.E- Number of E-RAB BTS3203E LTE:

RAB.AttEst.QCI.1 setup attempts V100R006C00
initiated by UEs for
services with the
QCI of 1 in a cell
1526726669 L.E- Number of BTS3203E LTE:

RAB.SuccEst.QCI. successful E-RAB V100R006C00
1 setups initiated by
UEs for services
with the QCI of 1 in
a cell

services with the
QCI of 2 in a cell

UEs for services
a cell

BTS3203E


services with the
QCI of 3 in a cell

UEs for services
a cell

services with the
QCI of 4 in a cell

UEs for services
a cell

services with the
QCI of 5 in a cell

UEs for services
a cell

services with the
QCI of 6 in a cell

UEs for services
a cell

BTS3203E


services with the
QCI of 7 in a cell

UEs for services
a cell

services with the
QCI of 8 in a cell

UEs for services
a cell

services with the
QCI of 9 in a cell

UEs for services
a cell
1526727544 L.E-RAB.SuccEst Total number of BTS3203E LTE:

successful E-RAB V100R006C00
setups initiated by
UEs in a cell
1526727545 L.E-RAB.AttEst Total number of E- BTS3203E LTE:

RAB setup attempts V100R006C00
initiated by UEs in a
cell

BTS3203E

1526728192 L.E- Number of initial E- BTS3203E LTE:

RAB.InitAttEst.Q RAB setup attempts V100R006C00
CI.1 initiated by UEs for
services with the
QCI of 1 in a cell

RAB.InitSuccEst.Q successful initial E- V100R006C00
CI.1 RAB setups initiated
by UEs for services
a cell

services with the
QCI of 2 in a cell

by UEs for services
a cell

services with the
QCI of 3 in a cell

by UEs for services
a cell

services with the
QCI of 4 in a cell

by UEs for services
a cell

BTS3203E


services with the
QCI of 5 in a cell

by UEs for services
a cell

services with the
QCI of 6 in a cell

by UEs for services
a cell

services with the
QCI of 7 in a cell

by UEs for services
a cell

services with the
QCI of 8 in a cell

by UEs for services
a cell

BTS3203E


services with the
QCI of 9 in a cell

by UEs for services
a cell
1526728244 L.E- Total number of E- BTS3203E LTE:

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

RAB.SuccEst.HOI successful E-RAB V100R006C00
n setups for incoming
handovers in a cell
1526728272 L.S1Sig.ConnEst.A Number of UE- BTS3203E LTE:

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

ucc successful UE- V100R006C00
related signaling
connection setups
over the S1 interface

RAB.InitAttEst initial E-RAB setup V100R006C00
attempts initiated by
UEs in a cell

RAB.InitSuccEst successful initial E- V100R006C00
RAB setups initiated
by UEs in a cell
1526728776 L.E- Average E-RAB BTS3203E LTE:

RAB.Est.TimeAvg setup duration in a V100R006C00
cell
1526728777 L.E- Maximum E-RAB BTS3203E LTE:

RAB.Est.TimeMax setup duration in a V100R006C00
cell

BTS3203E


n.QCI.1 setups for incoming
handovers of
services with QCI of
1 in a cell

handovers of
2 in a cell

handovers of
3 in a cell

handovers of
4 in a cell

handovers of
5 in a cell

handovers of
6 in a cell

handovers of
7 in a cell

BTS3203E


handovers of
8 in a cell

handovers of
9 in a cell
1526728879 L.E- Average initial E- BTS3203E LTE:

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

RAB.InitEst.Time RAB setup duration V100R006C00
Max in a cell

RAB.AttEst.HOIn. setups attempts for V100R006C00
QCI.1 incoming handovers
of services with QCI
of 1 in a cell

of 2 in a cell

of 3 in a cell

of 4 in a cell

of 5 in a cell

BTS3203E


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 V100R007C00
nsyn2Syn.Att when UEs switch
from the uplink out-
of-synchronization
synchronized state

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

PTT setups initiated by
UEs for PTT
services

RAB.AttEst.QCI.P setup attempts V100R011C10
TT initiated by UEs for
PTT services

BTS3203E


CI.PTT initiated by UEs for
PTT services

CI.PTT RAB setups initiated
by UEs for PTT
services

QCI.PTT incoming handovers
of PTT services

n.QCI.PTT setups for incoming
handovers of PTT
services
1526741845 L.S1Sig.ConnEst.A Number of S1 BTS3203E LTE:

tt.Emc signaling connection V100R011C10
setup attempts for
the cause of
"emergency"

tt.HighPri signaling connection V100R011C10
setup attempts for
the cause of
"highPriorityAccess
"

tt.Mt signaling connection V100R011C10
setup attempts for
the cause of "mt-
Access"

tt.MoSig signaling connection V100R011C10
setup attempts for
the cause of "mo-
Signalling"

tt.MoData signaling connection V100R011C10
setup attempts for
the cause of "mo-
Data"

BTS3203E


tt.DelayTol signaling connection V100R011C10
setup attempts for
the cause of
"delayTolerantAc-
cess-v1020"

ucc.Emc successful S1 V100R011C10
signaling connection
setups for the cause
of "emergency"

ucc.HighPri successful S1 V100R011C10
of
"highPriorityAccess
"

ucc.Mt successful S1 V100R011C10
of "mt-Access"

ucc.MoSig successful S1 V100R011C10
of "mo-Signalling"

ucc.MoData successful S1 V100R011C10
of "mo-Data"

ucc.DelayTol successful S1 V100R011C10
of
"delayTolerantAc-
cess-v1020"

RAB.AttEst.QCI. setup attempts for V100R011C10
65 QCI 65 services in a
cell

BTS3203E


65 setups for QCI 65
services in a cell

cell

services in a cell

cell

services in a cell

cell

services in a cell

CI.65 for QCI 65 services
in a cell

CI.65 RAB setups for QCI
65 services in a cell

in a cell

BTS3203E



in a cell


in a cell


RAB.Est.TimeAvg. setup duration for V100R011C10
QCI.65 QCI 65 services in a
cell

cell

cell

cell

RAB.Est.TimeMax. setup duration for V100R011C10
cell

BTS3203E


cell

cell

cell

RAB.AttEst.HOIn. setup attempts for V100R011C10
of QCI 65 services

of QCI 66 services

of QCI 69 services

of QCI 70 services

handovers of QCI 65
services

handovers of QCI 66
services

handovers of QCI 69
services

BTS3203E


handovers of QCI 70
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.65 L.E-RAB.InitSuccEst.QCI.
65
66
69
70
L.E-RAB.SuccEst.QCI.PTT L.E-
RAB.InitSuccEst.QCI.PTT
L.E-RAB.SuccEst L.E-RAB.InitSuccEst L.E-RAB.InitSuccEst.QCI.1
L.E-RAB.InitSuccEst.QCI.2

BTS3203E
L.E-RAB.InitSuccEst.QCI.
65
66
69
70
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.InitAttEst.QCI.PTT
L.E-RAB.AttEst L.E-RAB.InitAttEst L.E-RAB.InitAttEst.QCI.1

BTS3203E
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
65

BTS3203E
66
69
70
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- -
L.E- -
L.E- -
L.E- -
L.S1Sig.ConnEst.Att L.S1Sig.ConnEst.Att.Emc -
L.S1Sig.ConnEst.Att.HighP -
ri
L.S1Sig.ConnEst.Att.Mt -
L.S1Sig.ConnEst.Att.MoSig -

BTS3203E
L.S1Sig.ConnEst.Att.MoDat -
a
L.S1Sig.ConnEst.Att.Delay -
Tol
1.5.1 Number of E-RAB Setup Attempts in a Cell

Counters
1526726668 L.E- Number of E- BTS3203E LTE L

RAB.AttEst.QC RAB setup
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

BTS3203E


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 BTS3203E LTE L

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

BTS3203E


I.PTT attempts
initiated by UEs
for PTT
services

I.65 attempts for
QCI 65 services
in a cell

I.66 attempts for
QCI 66 services
in a cell

I.69 attempts for
QCI 69 services
in a cell

I.70 attempts for
QCI 70 services
in a cell
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.
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.

BTS3203E
Figure 1-20
Figure 1-21

BTS3203E
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

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

BTS3203E

GSM: None
UMTS: None

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

GSM: None
UMTS: None
LOFD-00110501 Dynamic DRX
L.E-RAB.AttEst.QCI.PTT Multi-mode: None

GSM: None
UMTS: None
LOFD-081218 Enhanced Extended QCI
LTROFD-111201 MCPTT QoS Management

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

BTS3203E
1.5.2 Number of Successful E-RAB Setups in a Cell
Counters
1526726669 L.E- Number of BTS3203E LTE L

RAB.SuccEst.Q successful E-
CI.1 RAB setups
initiated by UEs
for services
with the QCI of
1 in a cell

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

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

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

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

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

BTS3203E


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

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

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

RAB.SuccEst successful E-
RAB setups
initiated by UEs
in a cell

CI.PTT RAB setups
initiated by UEs
for PTT
services

CI.65 RAB setups for
QCI 65 services
in a cell

QCI 66 services
in a cell

BTS3203E


QCI 69 services
in a cell

QCI 70 services
in a cell
Description
The counters measure the number of successful E-RAB setups initiated by UEs for services
with a specific QCI ranging from 1 to 9 and the total number of successful E-RAB setups
initiated by UEs in a cell. The E-RAB setup is initiated by a UE when the UE requests a
service from the radio network. The setup is implemented through the initial UE context setup
or the E-RAB setup procedure.
Measurement Points
As shown at point B in Figure 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.

BTS3203E
Figure 1-22
Figure 1-23

BTS3203E
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

BTS3203E

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

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

BTS3203E
1.5.3 Number of Initial E-RAB Setup Attempts in a Cell
Counters

RAB.InitAttEst. initial E-RAB
QCI.1 setup attempts
initiated by UEs
for services
with the QCI of
1 in a cell

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

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

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

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

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

BTS3203E


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

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

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

RAB.InitAttEst initial E-RAB
setup attempts
initiated by UEs
in a cell

QCI.PTT setup attempts
initiated by UEs
for PTT
services

for QCI 65
services in a
cell

for QCI 66
services in a
cell

BTS3203E


for QCI 69
services in a
cell

for QCI 70
services in a
cell
Description
The counters measure the number of initial E-RAB setup attempts initiated by UEs for
services with a specific QCI ranging from 1 to 9 and the total number of initial E-RAB setup
attempts initiated by UEs in a cell. The initial E-RAB setup is initiated by a UE when the UE
requests a service from the radio network. The setup is implemented through the initial UE
context setup procedure.
Measurement Points
As shown at point A in Figure 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.

BTS3203E
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

BTS3203E

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

BTS3203E
L.E- Multi-mode: None

RAB.InitAttEst.QCI.PTT GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

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

Counters

RAB.InitSuccE successful
st.QCI.1 initial E-RAB
setups initiated
by UEs for
services with
the QCI of 1 in
a cell

BTS3203E


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

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

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

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

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

BTS3203E


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

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

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

st.QCI.PTT initial E-RAB
setups initiated
by UEs for PTT
services

setups for QCI
65 services in a
cell

BTS3203E


setups for QCI
66 services in a
cell

setups for QCI
69 services in a
cell

setups for QCI
70 services in a
cell
Description
The counters measure the number of successful initial E-RAB setups initiated by UEs for
services with a specific QCI ranging from 1 to 9 and the total number of successful initial E-
RAB setups initiated by UEs in a cell. The initial E-RAB setup is initiated by a UE when the
UE requests a service from the radio network. The setup is implemented through the initial
UE context setup procedure.
Measurement Points
As shown at point B in Figure 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.

BTS3203E
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

BTS3203E

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

BTS3203E

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

65 GSM: None
UMTS: None

66 GSM: None
UMTS: None

69 GSM: None
UMTS: None

70 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
OIn attempts for
incoming
handovers in a
cell

BTS3203E


RAB.AttEst.H RAB setups
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

BTS3203E


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

RAB.AttEst.H RAB setup
incoming
handovers of
QCI 65 services

BTS3203E


incoming
handovers of
QCI 66 services

incoming
handovers of
QCI 69 services

incoming
handovers of
QCI 70 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.
Measurement Points
Figure 1-26 shows an X2-based handover ,Figure 1-27 shows an S1-based handover, and
Figure 1-28 shows an inter-RAT incoming handover. As shown at point A in Figure 1-26 or
Figure 1-27, 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-28, 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.

BTS3203E
Figure 1-26
Figure 1-27

BTS3203E
Figure 1-28
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
LBFD-00201805 Coverage Based Inter-
frequency Handover
Service Based Inter-
frequency Handover

BTS3203E
L.E-RAB.AttEst.HOIn.QCI. Multi-mode: None

1 GSM: None
UMTS: None
frequency Handover
frequency Handover

2 GSM: None
UMTS: None
frequency Handover
frequency Handover

3 GSM: None
UMTS: None
frequency Handover
frequency Handover

4 GSM: None
UMTS: None
frequency Handover
frequency Handover

BTS3203E

5 GSM: None
UMTS: None
frequency Handover
frequency Handover

6 GSM: None
UMTS: None
frequency Handover
frequency Handover

7 GSM: None
UMTS: None
frequency Handover
frequency Handover

8 GSM: None
UMTS: None
frequency Handover
frequency Handover

BTS3203E

9 GSM: None
UMTS: None
frequency Handover
frequency Handover

RAB.AttEst.HOIn.QCI.PTT GSM: None
UMTS: None
LOFD-081218 Coverage Based Inter-
frequency Handover
LTROFD-111201
Enhanced Extended QCI
MCPTT QoS Management

65 GSM: None
UMTS: None
Coverage Based Inter-
frequency Handover

66 GSM: None
UMTS: None
frequency Handover

69 GSM: None
UMTS: None
frequency Handover

BTS3203E

70 GSM: None
UMTS: None
frequency Handover
1.5.6 Number of Successful E-RAB Setups for Incoming

Handovers in a Cell
Counters

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

OIn.QCI.1 RAB setups for
incoming
handovers of
services with
QCI of 1 in a
cell

incoming
handovers of
services with
QCI of 2 in a
cell

BTS3203E


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

BTS3203E


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

incoming
handovers of
QCI 65 services

incoming
handovers of
QCI 66 services

incoming
handovers of
QCI 69 services

BTS3203E


incoming
handovers of
QCI 70 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.
Measurement Points
As shown at point C in Figure 1-29, 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-30, 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-31, 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.
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-33, 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.

BTS3203E
Figure 1-29
Figure 1-30

BTS3203E
Figure 1-31
Figure 1-32

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

GSM: None
UMTS: None
frequency Handover
frequency Handover

BTS3203E

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

UMTS: None
frequency Handover
frequency Handover

UMTS: None
frequency Handover
frequency Handover

UMTS: None
frequency Handover
frequency Handover

BTS3203E

UMTS: None
frequency Handover
frequency Handover

UMTS: None
frequency Handover
frequency Handover

UMTS: None
frequency Handover
frequency Handover

UMTS: None
frequency Handover
frequency Handover

BTS3203E

UMTS: None
frequency Handover
frequency Handover

RAB.SuccEst.HOIn.QCI.PT GSM: None
T
UMTS: None
frequency Handover
LTROFD-111201

UMTS: None
frequency Handover

UMTS: None
frequency Handover

UMTS: None
frequency Handover

BTS3203E

UMTS: None
frequency Handover
1.5.7 Number of UE-related Signaling Connection Setups over the

S1 Interface
Counters
1526728272 L.S1Sig.ConnE Number of UE- BTS3203E LTE L

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

st.Succ successful UE-
related
signaling
connection
setups over the
S1 interface
1526741845 L.S1Sig.ConnE Number of S1 BTS3203E LTE L

st.Att.Emc signaling
connection
setup attempts
for the cause of
"emergency"

st.Att.HighPri signaling
connection
setup attempts
for the cause of
"highPriorityAc
cess"

BTS3203E


st.Att.Mt signaling
connection
setup attempts
for the cause of
"mt-Access"

st.Att.MoSig signaling
connection
setup attempts
for the cause of
"mo-
Signalling"

st.Att.MoData signaling
connection
setup attempts
for the cause of
"mo-Data"

st.Att.DelayTol signaling
connection
setup attempts
for the cause of
"delayTolerant
Access-v1020"

st.Succ.Emc successful S1
signaling
connection
setups for the
cause of
"emergency"

st.Succ.HighPri successful S1
signaling
connection
setups for the
cause of
"highPriorityAc
cess"

BTS3203E


st.Succ.Mt successful S1
signaling
connection
setups for the
cause of "mt-
Access"

st.Succ.MoSig successful S1
signaling
connection
setups for the
cause of "mo-
Signalling"

st.Succ.MoData successful S1
signaling
connection
setups for the
cause of "mo-
Data"

st.Succ.DelayT successful S1
ol signaling
connection
setups for the
cause of
"delayTolerant
Access-v1020"
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.

BTS3203E
Measurement Points
As shown at point A in Figure 1-34, the L.S1Sig.ConnEst.Att counter is incremented by 1
each time the eNodeB sends an INITIAL UE MESSAGE message to the MME. In addition,
the following counters are incremented based on the RRC connection setup causes:
If the RRC connection setup cause is "emergency", the L.S1Sig.ConnEst.Att.Emc counter is
incremented by 1.
If the RRC connection setup cause is "highPriorityAccess", the L.S1Sig.ConnEst.Att.HighPri
counter is incremented by 1.
If the RRC connection setup cause is "mt-Access", the L.S1Sig.ConnEst.Att.Mt counter is
incremented by 1.
If the RRC connection setup cause is "mo-Signalling", the L.S1Sig.ConnEst.Att.MoSig
If the RRC connection setup cause is "mo-Data", the L.S1Sig.ConnEst.Att.MoData counter is
incremented by 1.
If the RRC connection setup cause is "delayTolerantAccess-v1020", the
L.S1Sig.ConnEst.Att.DelayTol counter is incremented by 1.
As shown at point B in Figure 1-34, 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. In addition, the following
counters are incremented based on the RRC connection setup causes:
If the RRC connection setup cause is "emergency", the L.S1Sig.ConnEst.Succ.Emc counter is
incremented by 1.
If the RRC connection setup cause is "highPriorityAccess", the
L.S1Sig.ConnEst.Succ.HighPri counter is incremented by 1.
If the RRC connection setup cause is "mt-Access", the L.S1Sig.ConnEst.Succ.Mt counter is
incremented by 1.
If the RRC connection setup cause is "mo-Signalling", the L.S1Sig.ConnEst.Succ.MoSig
If the RRC connection setup cause is "mo-Data", the L.S1Sig.ConnEst.Succ.MoData counter
is incremented by 1.
If the RRC connection setup cause is "delayTolerantAccess-v1020", the
L.S1Sig.ConnEst.Succ.DelayTol counter is incremented by 1.

BTS3203E
Figure 1-34
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
L.S1Sig.ConnEst.Att.Emc Multi-mode: None

GSM: None
UMTS: None
L.S1Sig.ConnEst.Att.HighP Multi-mode: None

ri GSM: None
UMTS: None

BTS3203E
L.S1Sig.ConnEst.Att.Mt Multi-mode: None

GSM: None
UMTS: None
L.S1Sig.ConnEst.Att.MoSig Multi-mode: None

GSM: None
UMTS: None
L.S1Sig.ConnEst.Att.MoDat Multi-mode: None

a GSM: None
UMTS: None
L.S1Sig.ConnEst.Att.Delay Multi-mode: None

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

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

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

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

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

ata GSM: None
UMTS: None

BTS3203E
L.S1Sig.ConnEst.Succ.Dela Multi-mode: None

yTol GSM: None
UMTS: None
1.5.8 E-RAB Setup Duration in a Cell
Counters
1526728776 L.E- Average E- BTS3203E LTE L

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

Max duration in a
cell
1526728879 L.E- Average initial BTS3203E LTE L

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

RAB.InitEst.Ti initial E-RAB
meMax setup duration
in a cell

Avg.QCI.65 duration for
QCI 65 services
in a cell

QCI 66 services
in a cell

QCI 69 services
in a cell

BTS3203E


QCI 70 services
in a cell

Max.QCI.65 duration for
QCI 65 services
in a cell

QCI 66 services
in a cell

QCI 69 services
in a cell

QCI 70 services
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.
Measurement Points
As shown at points A and B in Figure 1-35, 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-36, 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.

BTS3203E
As shown at points A and B in Figure 1-35, 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-35

BTS3203E
Figure 1-36
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

BTS3203E
L.E-RAB.InitEst.TimeMax Multi-mode: None

GSM: None
UMTS: None

RAB.Est.TimeAvg.QCI.65 GSM: None
UMTS: None

UMTS: None

UMTS: None

UMTS: None

RAB.Est.TimeMax.QCI.65 GSM: None
UMTS: None

UMTS: None

UMTS: None

UMTS: None

BTS3203E
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
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-37 and Figure 1-38, 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.

BTS3203E
Figure 1-37
Figure 1-38
Formula
None
Unit
None
Related Features

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

BTS3203E
1.5.10 Number of Successfully Recovered E-RABs When UEs

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

RAB.StateTran successfully
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-39 and Figure 1-40, 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 or an RRC Connection Reestablishment Request message from a UE
which indicating that the eNodeB finishes uplink PUCCH resource allocation for the UE.

BTS3203E
Figure 1-39
Figure 1-40
Formula
None
Unit
None
Related Features

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

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

BTS3203E
Figure 1-43
Counters
1526726686 L.E- Number of abnormal BTS3203E LTE:

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

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

RAB.AbnormRel. releases of activated V100R006C00
QCI.2 E-RABs for services
a cell

RAB.NormRel.QC E-RAB releases for V100R006C00
I.2 services with the
QCI of 2 in a cell

a cell

BTS3203E


QCI of 3 in a cell

a cell

QCI of 4 in a cell

a cell

QCI of 5 in a cell

a cell

QCI of 6 in a cell

a cell

QCI of 7 in a cell

BTS3203E


a cell

QCI of 8 in a cell

a cell

QCI of 9 in a cell

RAB.NormRel.HO E-RAB releases for V100R006C00
Out.QCI.1 outgoing handovers
of services with the
QCI of 1 in a cell

QCI of 2 in a cell

QCI of 3 in a cell

QCI of 4 in a cell

QCI of 5 in a cell

BTS3203E


QCI of 6 in a cell

QCI of 7 in a cell

QCI of 8 in a cell

QCI of 9 in a cell

RAB.AbnormRel. E-RAB releases for V100R006C00
HOOut.QCI.1 outgoing handovers
QCI of 1 in a cell

QCI of 2 in a cell

QCI of 3 in a cell

QCI of 4 in a cell

BTS3203E


QCI of 5 in a cell

QCI of 6 in a cell

QCI of 7 in a cell

QCI of 8 in a cell

QCI of 9 in a cell

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

normal E-RAB V100R006C00
releases initiated by
the eNodeB in a cell

RAB.NormRel.HO normal E-RAB V100R006C00
Out releases for outgoing
handovers in a cell

RAB.AbnormRel. abnormal E-RAB V100R006C00
HOOut releases for outgoing
handovers in a cell

BTS3203E


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

RAB.AbnormRel.T releases of activated V100R006C00
NL E-RABs due to
faults at the
transport network
layer

RAB.AbnormRel.C releases of activated V100R006C00
ong E-RABs due to
network congestion

HOFailure E-RABs due to
handover failures

MME E-RABs due to
faults on the MME
side

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

RAB.Release.Unsy E-RABs of UEs in V100R006C00
n the uplink out-of-
synchronization
state

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

BTS3203E


RAB.Rel.eNodeB.Q releases initiated by V100R006C00
CI.1 the eNodeB for
1 in a cell

CI.2 the eNodeB for
2 in a cell

CI.3 the eNodeB for
3 in a cell

CI.4 the eNodeB for
4 in a cell

CI.5 the eNodeB for
5 in a cell

CI.6 the eNodeB for
6 in a cell

CI.7 the eNodeB for
7 in a cell

CI.8 the eNodeB for
8 in a cell

BTS3203E


CI.9 the eNodeB for
9 in a cell

RAB.Rel.eNodeB RAB releases V100R006C00
initiated by the
eNodeB in a cell

RAB.Rel.MME.QC releases initiated by V100R006C00
I.1 the MME for
1 in a cell

I.2 the MME for
2 in a cell

I.3 the MME for
3 in a cell

I.4 the MME for
4 in a cell

I.5 the MME for
5 in a cell

I.6 the MME for
6 in a cell

I.7 the MME for
7 in a cell

BTS3203E


I.8 the MME for
8 in a cell

I.9 the MME for
9 in a cell

RAB.Rel.MME RAB releases V100R006C00
initiated by the
MME

RAB.Left.QCI.1 remaining E-RABs V100R006C00
for services with
QCI of 1 in a cell

for services with
QCI of 2 in a cell

for services with
QCI of 3 in a cell

for services with
QCI of 4 in a cell

for services with
QCI of 5 in a cell

for services with
QCI of 6 in a cell

for services with
QCI of 7 in a cell

BTS3203E


for services with
QCI of 8 in a cell

for services with
QCI of 9 in a cell
1526728817 L.E-RAB.Left Total number of BTS3203E LTE:

remaining E-RABs V100R006C00
in a cell

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

eNodeB for services
with QCI of 2
because of the S1
RESET in a cell

eNodeB for services
with QCI of 3
because of the S1
RESET in a cell

eNodeB for services
with QCI of 4
because of the S1
RESET in a cell

BTS3203E


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

eNodeB for services
with QCI of 6
because of the S1
RESET in a cell

eNodeB for services
with QCI of 7
because of the S1
RESET in a cell

eNodeB for services
with QCI of 8
because of the S1
RESET in a cell

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

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

BTS3203E


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

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

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

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

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

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

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

BTS3203E


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

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

RAB.Rel.S1Reset. abnormal E-RAB V100R006C00
MME releases initiated by
the MME because of
the S1 RESET in a
cell

RAB.AbnormRel. abnormal E-RAB V100R006C00
MMETot releases due to faults
on the MME side

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

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

adio.ULSyncFail E-RABs due to
uplink
resynchronization
failures

BTS3203E


adio.UuNoReply E-RABs because of
no responses from
the UE

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

ong.PreEmp E-RABs because of
radio resource
preemption

ong.Load E-RABs because of
radio resource
overload

NL.PreEmp E-RABs because of
transport resource
preemption

NL.Load E-RABs because of
transport resource
overload

RAB.AbnormRel. releases of E-RABs V100R007C00
MMETot.VoIP for voice services
because of faults on
the MME side

BTS3203E


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

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

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

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

adio.VoIP E-RABs for voice
services because of
faults at the radio
network layer

HOFailure.VoIP E-RABs for voice
services because of
handover failures

BTS3203E


ong.VoIP E-RABs for voice
services because of
radio network
congestion

MME.VoIP E-RABs for voice
services because of
faults on the MME
side

NL.VoIP E-RABs for voice
services because of
faults at the
transport network
layer

ong.PreEmp.VoIP E-RABs for voice
services because of
radio resource
preemption

ong.Load.VoIP E-RABs for voice
services because of
radio resource
overload

NL.PreEmp.VoIP E-RABs for voice
services because of
transport resource
preemption

NL.Load.VoIP E-RABs for voice
services because of
transport resource
overload

BTS3203E


RAB.AbnormRel.e releases of E-RABs V100R007C00
NBTot.QCI.1 for services with the
QCI of 1 in a cell

QCI of 2 in a cell

QCI of 3 in a cell

QCI of 4 in a cell

QCI of 5 in a cell

QCI of 6 in a cell

QCI of 7 in a cell

QCI of 8 in a cell

QCI of 9 in a cell

RAB.AbnormRel.U releases of activated V100R011C10
lWeak.VoIP E-RABs for voice
services because of
uplink weak
coverage

BTS3203E

1526730864 L.E- Number of MME- BTS3203E LTE:

RAB.AbnormRel. triggered abnormal V100R009C00
MME.QCI.2 releases of activated
E-RABs for services
with the QCI of 2

E-RABs for services
with the QCI of 3

E-RABs for services
with the QCI of 4

E-RABs for services
with the QCI of 5

E-RABs for services
with the QCI of 6

E-RABs for services
with the QCI of 7

E-RABs for services
with the QCI of 8

E-RABs for services
with the QCI of 9

Other E-RABs due to other
reasons

BTS3203E


Other.VoIP E-RABs for voice
services due to other
reasons

adio.Other E-RABs due to other
faults at the radio
network layer

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

NL.Other E-RABs due to other
faults at the
transport network
lay

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

ong.Other E-RABs due to other
radio resource
congestion reaso

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

QCI.PTT for PTT services

BTS3203E


I.PTT PTT services in a
cell

Out.QCI.PTT outgoing handovers
of PTT services

HOOut.QCI.PTT outgoing handovers
of PTT services

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

QCI of 2 during
handover executions

QCI of 3 during
handover executions

QCI of 4 during
handover executions

QCI of 5 during
handover executions

BTS3203E


QCI of 6 during
handover executions

QCI of 7 during
handover executions

QCI of 8 during
handover executions

QCI of 9 during
handover executions

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

RAB.Rel.eNodeB.U triggered E-RAB V100R011C10
serinact releases with the
cause value of User
Inactivity

RAB.NormRel.IRa releases of QCI 1 E- V100R011C10
tHOOut.QCI.1 RABs for inter-RAT
outgoing handovers

outgoing handovers

BTS3203E


outgoing handovers

outgoing handovers

outgoing handovers

outgoing handovers

outgoing handovers

outgoing handovers

outgoing handovers

RAB.NormRel.IRa normal releases of V100R011C10
tHOOut E-RABs for inter-
RAT outgoing
handovers

QCI.65 for QCI 65 services
in a cell

in a cell

BTS3203E


in a cell

in a cell

RAB.NormRel.QC releases of E-RABs V100R011C10
I.65 for QCI 65 services
in a cell

in a cell

in a cell

in a cell

of QCI 65 services

of QCI 66 services

of QCI 69 services

of QCI 70 services

BTS3203E


of QCI 65 services

of QCI 66 services

of QCI 69 services

of QCI 70 services
1526742091 L.E- Number of E-RABs BTS3203E LTE:

RAB.AbnormRel.e released by V100R011C00
NBTot.UEAbnorm defective UEs in a
al cell

RAB.NormRel.Inte normal releases of V100R012C00
rFddTddHOOut E-RABs for inter-
duplex-mode
outgoing handovers

RAB.NormRel.Inte releases of QCI 1 E- V100R012C00
rFddTddHOOut.Q RABs for inter-
CI.1 duplex-mode
outgoing handovers

CI.2 duplex-mode
outgoing handovers

CI.3 duplex-mode
outgoing handovers

BTS3203E


CI.4 duplex-mode
outgoing handovers

CI.5 duplex-mode
outgoing handovers

CI.6 duplex-mode
outgoing handovers

CI.7 duplex-mode
outgoing handovers

CI.8 duplex-mode
outgoing handovers

CI.9 duplex-mode
outgoing handovers

RAB.AbnormRel.e triggered abnormal V100R012C10
NBTot.QCI.65 releases of E-RABs
for QCI-65 services

for QCI-66 services

for QCI-69 services

BTS3203E


for QCI-70 services
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 Level-1 Level-2 Level-3 Level-4 Level-5

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

RAB.Abnor RAB.Abnor RAB.Abnor RAB.Abnor
mRel mRel.QCI.1 mRel.Radio. mRel.Radio.
VoIP SRBReset.V
oIP
L.E- - -
RAB.Abnor
mRel.Radio.
NoReply.VoI
P
L.E- - -
RAB.Abnor
mRel.Radio.
ULSyncFail.
VoIP
L.E- L.E- - -
RAB.Abnor RAB.Abnor
mRel.Cong. mRel.Cong.
VoIP PreEmp.VoI
P

BTS3203E

L.E- - -
RAB.Abnor
mRel.Cong.
Load.VoIP
L.E- L.E- - -
RAB.Abnor RAB.Abnor
mRel.TNL. mRel.TNL.P
VoIP reEmp.VoIP
L.E- - -
RAB.Abnor
mRel.TNL.L
oad.VoIP
L.E- - - -
RAB.Abnor
mRel.HOFai
lure.VoIP
L.E- - - -
RAB.Abnor
mRel.UlWea
k.VoIP
L.E- - - - -
RAB.Abnor
mRel.QCI.2
L.E- - - - -
RAB.Abnor
mRel.QCI.3
L.E- - - - -
RAB.Abnor
mRel.QCI.4
L.E- - - - -
RAB.Abnor
mRel.QCI.5
L.E- - - - -
RAB.Abnor
mRel.QCI.6
L.E- - - - -
RAB.Abnor
mRel.QCI.7
L.E- - - - -
RAB.Abnor
mRel.QCI.8

BTS3203E

L.E- - - - -
RAB.Abnor
mRel.QCI.9
L.E- - - - -
RAB.Abnor
mRel.QCI.
65
L.E- - - - -
RAB.Abnor
mRel.QCI.
66
L.E- - - - -
RAB.Abnor
mRel.QCI.
69
L.E- - - - -
RAB.Abnor
mRel.QCI.
70
L.E- L.E- L.E- L.E- - -

mRel mRel.Radio mRel.Radio. mRel.Radio.
SRBReset SRBReset.V
oIP
L.E- - - -
RAB.Abnor
mRel.Radio.
DRBReset
L.E- L.E- - -
RAB.Abnor RAB.Abnor
mRel.Radio. mRel.Radio.
ULSyncFail ULSyncFail.
VoIP
L.E- L.E- - -
RAB.Abnor RAB.Abnor
UuNoReply NoReply.VoI
P
L.E- L.E- - -
RAB.Abnor RAB.Abnor
Other Other.VoIP

BTS3203E

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

RAB.Abnor RAB.Abnor RAB.Abnor
mRel.Radio mRel.Radio. mRel.Radio.
VoIP SRBReset.V
oIP
L.E- - -
RAB.Abnor
mRel.Radio.
NoReply.VoI
P
L.E- - -
RAB.Abnor
mRel.Radio.
ULSyncFail.
VoIP
L.E- L.E- L.E- - -

mRel.TNL mRel.TNL.P mRel.TNL.P
reEmp reEmp.VoIP
L.E- L.E- - -
RAB.Abnor RAB.Abnor
mRel.TNL.L mRel.TNL.L
oad oad.VoIP
L.E- L.E- L.E- - -

mRel.TNL mRel.TNL. mRel.TNL.P
VoIP reEmp.VoIP
L.E- - -
RAB.Abnor
mRel.TNL.L
oad.VoIP
L.E- L.E- L.E- - -

mRel.Cong mRel.Cong. mRel.Cong.
PreEmp PreEmp.VoI
P
L.E- L.E- - -
RAB.Abnor RAB.Abnor
Load Load.VoIP

BTS3203E

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

mRel.Cong mRel.Cong. mRel.Cong.
VoIP PreEmp.VoI
P
L.E- - -
RAB.Abnor
mRel.Cong.
Load.VoIP
L.E- L.E- - - -
RAB.Abnor RAB.Abnor
mRel.HOFai mRel.HOFai
lure lure.VoIP
L.E- L.E- - - -
RAB.Abnor RAB.Abnor
mRel.Other mRel.Other.
VoIP
L.E- - - - -
RAB.Abnor
mRel.QCI.P
TT
L.E- L.E- L.E- L.E- L.E- L.E-

RAB.Norm RAB.Norm RAB.Rel.M RAB.Abnor RAB.Abnor RAB.Abnor
Rel Rel.QCI.1 ME.QCI.1 mRel.MME mRel.MME. mRel.MME.
Tot.VoIP VoIP EUtranGen.
VoIP
L.E- L.E- - - -
RAB.Norm RAB.Rel.M
Rel.QCI.2 ME.QCI.2
L.E- L.E- - - -
RAB.Norm RAB.Rel.M
Rel.QCI.3 ME.QCI.3
L.E- L.E- - - -
RAB.Norm RAB.Rel.M
Rel.QCI.4 ME.QCI.4
L.E- L.E- - - -
RAB.Norm RAB.Rel.M
Rel.QCI.5 ME.QCI.5
L.E- L.E- - - -
RAB.Norm RAB.Rel.M
Rel.QCI.6 ME.QCI.6

BTS3203E

L.E- L.E- - - -
RAB.Norm RAB.Rel.M
Rel.QCI.7 ME.QCI.7
L.E- L.E- - - -
RAB.Norm RAB.Rel.M
Rel.QCI.8 ME.QCI.8
L.E- L.E- - - -
RAB.Norm RAB.Rel.M
Rel.QCI.9 ME.QCI.9
L.E- - - - -
RAB.Norm
Rel.QCI.PT
T
L.E- - - - -
RAB.Norm
Rel.QCI.65
L.E- - - - -
RAB.Norm
Rel.QCI.66
L.E- - - - -
RAB.Norm
Rel.QCI.69
L.E- - - - -
RAB.Norm
Rel.QCI.70
L.E- L.E- L.E- L.E- L.E- L.E-

RAB.Norm RAB.Rel.M RAB.Rel.M RAB.Abnor RAB.Abnor RAB.Abnor
Rel ME ME.QCI.1 mRel.MME mRel.MME. mRel.MME.
Tot.VoIP VoIP EUtranGen.
VoIP
L.E- - - -
RAB.Rel.M
ME.QCI.2
L.E- - - -
RAB.Rel.M
ME.QCI.3
L.E- - - -
RAB.Rel.M
ME.QCI.4

BTS3203E

L.E- - - -
RAB.Rel.M
ME.QCI.5
L.E- - - -
RAB.Rel.M
ME.QCI.6
L.E- - - -
RAB.Rel.M
ME.QCI.7
L.E- - - -
RAB.Rel.M
ME.QCI.8
L.E- - - -
RAB.Rel.M
ME.QCI.9
L.E- L.E- L.E- L.E- L.E-

RAB.Rel.M RAB.Abnor RAB.Abnor RAB.Abnor RAB.Abnor
ME mRel.MME mRel.MME mRel.MME. mRel.MME.
Tot EUtranGen EUtranGen.
VoIP
L.E- L.E- L.E-

mRel.MME mRel.MME. mRel.MME.
VoIP EUtranGen.
VoIP
L.E- L.E- L.E- L.E-

mRel.MME mRel.MME mRel.MME. mRel.MME.
Tot Tot.VoIP VoIP EUtranGen.
VoIP
L.E- L.E- - - - -
RAB.Norm RAB.Norm
Rel.HOOut Rel.HOOut.
QCI.1
L.E- - - - -
RAB.Norm
Rel.HOOut.
QCI.2
L.E- - - - -
RAB.Norm
Rel.HOOut.
QCI.3

BTS3203E

L.E- - - - -
RAB.Norm
Rel.HOOut.
QCI.4
L.E- - - - -
RAB.Norm
Rel.HOOut.
QCI.5
L.E- - - - -
RAB.Norm
Rel.HOOut.
QCI.6
L.E- - - - -
RAB.Norm
Rel.HOOut.
QCI.7
L.E- - - - -
RAB.Norm
Rel.HOOut.
QCI.8
L.E- - - - -
RAB.Norm
Rel.HOOut.
QCI.9
L.E- L.E- - - - -
RAB.Abnor RAB.Abnor
mRel.HOOu mRel.HOOu
t t.QCI.1
L.E- - - - -
RAB.Abnor
mRel.HOOu
t.QCI.2
L.E- - - - -
RAB.Abnor
mRel.HOOu
t.QCI.3
L.E- - - - -
RAB.Abnor
mRel.HOOu
t.QCI.4

BTS3203E

L.E- - - - -
RAB.Abnor
mRel.HOOu
t.QCI.5
L.E- - - - -
RAB.Abnor
mRel.HOOu
t.QCI.6
L.E- - - - -
RAB.Abnor
mRel.HOOu
t.QCI.7
L.E- - - - -
RAB.Abnor
mRel.HOOu
t.QCI.8
L.E- - - - -
RAB.Abnor
mRel.HOOu
t.QCI.9
L.E- L.E- - - - -
RAB.Abnor RAB.Abnor
mRel.eNBT mRel.eNBT
ot ot.QCI.1
L.E- - - - -
RAB.Abnor
mRel.eNBT
ot.QCI.2
L.E- - - - -
RAB.Abnor
mRel.eNBT
ot.QCI.3
L.E- - - - -
RAB.Abnor
mRel.eNBT
ot.QCI.4
L.E- - - - -
RAB.Abnor
mRel.eNBT
ot.QCI.5

BTS3203E

L.E- - - - -
RAB.Abnor
mRel.eNBT
ot.QCI.6
L.E- - - - -
RAB.Abnor
mRel.eNBT
ot.QCI.7
L.E- - - - -
RAB.Abnor
mRel.eNBT
ot.QCI.8
L.E- - - - -
RAB.Abnor
mRel.eNBT
ot.QCI.9
L.E- - - - -
RAB.Abnor
mRel.eNBT
ot.QCI.65
L.E- - - - -
RAB.Abnor
mRel.eNBT
ot.QCI.66
L.E- - - - -
RAB.Abnor
mRel.eNBT
ot.QCI.69
L.E- - - - -
RAB.Abnor
mRel.eNBT
ot.QCI.70
L.E- L.E- - - - -
RAB.Rel.eN RAB.Rel.eN
odeB odeB.QCI.1
L.E- - - - -
RAB.Rel.eN
odeB.QCI.2
L.E- - - - -
RAB.Rel.eN
odeB.QCI.3

BTS3203E

L.E- - - - -
RAB.Rel.eN
odeB.QCI.4
L.E- - - - -
RAB.Rel.eN
odeB.QCI.5
L.E- - - - -
RAB.Rel.eN
odeB.QCI.6
L.E- - - - -
RAB.Rel.eN
odeB.QCI.7
L.E- - - - -
RAB.Rel.eN
odeB.QCI.8
L.E- - - - -
RAB.Rel.eN
odeB.QCI.9
L.E- L.E- - - - -
RAB.Left RAB.Left.Q
CI.1
L.E- - - - -
RAB.Left.Q
CI.2
L.E- - - - -
RAB.Left.Q
CI.3
L.E- - - - -
RAB.Left.Q
CI.4
L.E- - - - -
RAB.Left.Q
CI.5
L.E- - - - -
RAB.Left.Q
CI.6
L.E- - - - -
RAB.Left.Q
CI.7

BTS3203E

L.E- - - - -
RAB.Left.Q
CI.8
L.E- - - - -
RAB.Left.Q
CI.9
L.E- L.E- - - - -
RAB.Rel.S1 RAB.Rel.S1
Reset.eNode Reset.eNode
B B.QCI.1
L.E- - - - -
RAB.Rel.S1
Reset.eNode
B.QCI.2
L.E- - - - -
RAB.Rel.S1
Reset.eNode
B.QCI.3
L.E- - - - -
RAB.Rel.S1
Reset.eNode
B.QCI.4
L.E- - - - -
RAB.Rel.S1
Reset.eNode
B.QCI.5
L.E- - - - -
RAB.Rel.S1
Reset.eNode
B.QCI.6
L.E- - - - -
RAB.Rel.S1
Reset.eNode
B.QCI.7
L.E- - - - -
RAB.Rel.S1
Reset.eNode
B.QCI.8
L.E- - - - -
RAB.Rel.S1
Reset.eNode
B.QCI.9

BTS3203E

L.E- L.E- - - - -
RAB.Rel.S1 RAB.Rel.S1
Reset.MME Reset.MME.
QCI.1
L.E- - - - -
RAB.Rel.S1
Reset.MME.
QCI.2
L.E- - - - -
RAB.Rel.S1
Reset.MME.
QCI.3
L.E- - - - -
RAB.Rel.S1
Reset.MME.
QCI.4
L.E- - - - -
RAB.Rel.S1
Reset.MME.
QCI.5
L.E- - - - -
RAB.Rel.S1
Reset.MME.
QCI.6
L.E- - - - -
RAB.Rel.S1
Reset.MME.
QCI.7
L.E- - - - -
RAB.Rel.S1
Reset.MME.
QCI.8
L.E- - - - -
RAB.Rel.S1
Reset.MME.
QCI.9
L.E- L.E- - - - -
RAB.Abnor RAB.Abnor
mRel.TNL. mRel.TNL.
Other Other.VoIP

BTS3203E

L.E- L.E- - - - -
RAB.Abnor RAB.Abnor
Other Other.VoIP
L.E- L.E- - - - -
RAB.Abnor RAB.Abnor
mRel.MME. mRel.MME.
HOOut HOOut.QCI.
1
L.E- - - - -
RAB.Abnor
mRel.MME.
HOOut.QCI.
2
L.E- - - - -
RAB.Abnor
mRel.MME.
HOOut.QCI.
3
L.E- - - - -
RAB.Abnor
mRel.MME.
HOOut.QCI.
4
L.E- - - - -
RAB.Abnor
mRel.MME.
HOOut.QCI.
5
L.E- - - - -
RAB.Abnor
mRel.MME.
HOOut.QCI.
6
L.E- - - - -
RAB.Abnor
mRel.MME.
HOOut.QCI.
7
L.E- - - - -
RAB.Abnor
mRel.MME.
HOOut.QCI.
8

BTS3203E

L.E- - - - -
RAB.Abnor
mRel.MME.
HOOut.QCI.
9
L.E- L.E- - - - -
RAB.Norm RAB.Norm
Rel.InterFdd Rel.InterFdd
TddHOOut TddHOOut.
QCI.1
L.E- - - - -
RAB.Norm
Rel.InterFdd
TddHOOut.
QCI.2
L.E- - - - -
RAB.Norm
Rel.InterFdd
TddHOOut.
QCI.3
L.E- - - - -
RAB.Norm
Rel.InterFdd
TddHOOut.
QCI.4
L.E- - - - -
RAB.Norm
Rel.InterFdd
TddHOOut.
QCI.5
L.E- - - - -
RAB.Norm
Rel.InterFdd
TddHOOut.
QCI.6
L.E- - - - -
RAB.Norm
Rel.InterFdd
TddHOOut.
QCI.7

BTS3203E

L.E- - - - -
RAB.Norm
Rel.InterFdd
TddHOOut.
QCI.8
L.E- - - - -
RAB.Norm
Rel.InterFdd
TddHOOut.
QCI.9
1.6.1 Number of Abnormal E-RAB Releases in a Cell

Counters

RAB.AbnormR abnormal
el.QCI.1 releases of
activated E-
RABs for
services with
the QCI of 1 in
a cell

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

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

BTS3203E


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

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

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

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

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

BTS3203E


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

el.eNBTot.QCI. releases of E-
1 RABs for
services with
the QCI of 1 in
a cell

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

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

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

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

BTS3203E


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

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

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

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

el.QCI.PTT releases of E-
RABs for PTT
services

el.QCI.65 releases of E-
RABs for QCI
65 services in a
cell

RABs for QCI
66 services in a
cell

BTS3203E


RABs for QCI
69 services in a
cell

RABs for QCI
70 services in a
cell

RAB.AbnormR eNodeB-
el.eNBTot.QCI. triggered
65 abnormal
releases of E-
RABs for
QCI-65 services

RAB.AbnormR eNodeB-
66 abnormal
releases of E-
RABs for
QCI-66 services

RAB.AbnormR eNodeB-
69 abnormal
releases of E-
RABs for
QCI-69 services

RAB.AbnormR eNodeB-
70 abnormal
releases of E-
RABs for
QCI-70 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

BTS3203E
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-44, the corresponding counter (L.E-
RAB.AbnormRel.eNBTot.QCI.1 to L.E-RAB.AbnormRel.eNBTot.QCI.9,L.E-
RAB.AbnormRel.eNBTot.QCI.65,L.E-RAB.AbnormRel.eNBTot.QCI.66,L.E-
RAB.AbnormRel.eNBTot.QCI.69 or L.E-RAB.AbnormRel.eNBTot.QCI.70) 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", "Successful Handover", or "Redirection towards 1xRTT".
If the eNodeB determines that the E-RAB to be released carries data, the corresponding
counter (L.E-RAB.AbnormRel.QCI.1 to L.E-RAB.AbnormRel.QCI.9, L.E-
RAB.AbnormRel.QCI.65, L.E-RAB.AbnormRel.QCI.66, L.E-RAB.AbnormRel.QCI.69 or
L.E-RAB.AbnormRel.QCI.70) 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. If the UE is in high-speed movement, the number of abnormal releases of QCI-1
E-RABs is counted in the L.E-RAB.AbnormRel.QCI.Hst.1 counter.
As shown at point A in Figure 1-45, 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,L.E-RAB.AbnormRel.eNBTot.QCI.65,L.E-
RAB.AbnormRel.eNBTot.QCI.66,L.E-RAB.AbnormRel.eNBTot.QCI.69 or L.E-
RAB.AbnormRel.eNBTot.QCI.70) 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", "Handover Cancelled", or
"Redirection towards 1xRTT". If the eNodeB determines that the E-RABs to be released carry
data, the corresponding counter (L.E-RAB.AbnormRel.QCI.1 to L.E-RAB.AbnormRel.QCI.
9, L.E-RAB.AbnormRel.QCI.65, L.E-RAB.AbnormRel.QCI.66, L.E-RAB.AbnormRel.QCI.
69 or L.E-RAB.AbnormRel.QCI.70) is incremented. If the UE is in high-speed movement,
the number of abnormal releases of QCI-1 E-RABs is counted in the L.E-
RAB.AbnormRel.QCI.Hst.1 counter. If the cause value of an E-RAB release for load-based
redirection is "Reduce load in serving cell", the corresponding counter is not incremented. If
multiple E-RABs have been set up for the UE, the corresponding counters are incremented by
the number of E-RABs. When the MME sends a UE CONTEXT RELEASE COMMAND
message to the eNodeB, the corresponding counter is not incremented repeatedly.
The description about E-RABs with data in a buffer is from the description of "4.2.2.6"
chapters in 3GPP TS 36.425 (V10.7.0) and "6.2.1" chapters in 3GPP TS 36.450 (V10.1.0).

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

GSM: None
UMTS: None

BTS3203E

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

BTS3203E

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

BTS3203E

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

65 GSM: None
UMTS: None

66 GSM: None
UMTS: None

69 GSM: None
UMTS: None

70 GSM: None
UMTS: None

CI.65
UMTS: None

CI.66
UMTS: None

BTS3203E

CI.69
UMTS: None

CI.70
UMTS: None
1.6.2 Number of Normal E-RAB Releases in a Cell

Counters

RAB.NormRel. normal E-RAB
QCI.1 releases for
services with
the QCI of 1 in
a cell

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

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

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

BTS3203E


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

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

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

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

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

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

QCI.PTT releases for
PTT services in
a cell

BTS3203E


RAB.NormRel. normal releases
QCI.65 of E-RABs for
QCI 65 services
in a cell

QCI 66 services
in a cell

QCI 69 services
in a cell

QCI 70 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-46, 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

BTS3203E
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-47, 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-48, 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", or "Reduce load
in serving cell" by load-based redirection.
(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-48, 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-46

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

GSM: None
UMTS: None

GSM: None
UMTS: None

BTS3203E

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

BTS3203E

RAB.NormRel.QCI.PTT GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
1.6.3 Number of Normal E-RAB Releases for Outgoing Handovers

in a Cell
Counters

HOOut.QCI.1 releases for
outgoing
handovers of
services with
the QCI of 1 in
a cell

BTS3203E


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

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

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

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

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

BTS3203E


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

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

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

HOOut releases for
outgoing
handovers in a
cell

HOOut.QCI.PT releases for
T outgoing
handovers of
PTT services

outgoing
handovers of
QCI 65 services

BTS3203E


outgoing
handovers of
QCI 66 services

outgoing
handovers of
QCI 69 services

outgoing
handovers of
QCI 70 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.
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, 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-49 shows an intra-eNodeB handover, Figure 1-50 shows an X2-based handover,
Figure 1-51 shows an S1-based handover, Figure 1-52 shows a handover from E-UTRAN to
WCDMA network, GERAN, or TD-SCDMA network, Figure 1-53 shows an intra-eNodeB
handover where the RRC connection is reestablished to the target cell for the UE, Figure 1-54
shows an X2-based handover where the RRC connection is reestablished to the target eNodeB
for the UE, and Figure 1-55 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-49, Figure 1-50, Figure 1-51, or Figure 1-52, 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.

BTS3203E
As shown at point C in Figure 1-53, Figure 1-54, or Figure 1-55, 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-49
Figure 1-50

BTS3203E
Figure 1-51
Figure 1-52

BTS3203E
Figure 1-53
Figure 1-54

BTS3203E
Figure 1-55
Formula
None
Unit
None

BTS3203E
Related Features

RAB.NormRel.HOOut.QCI. GSM: None
1
UMTS: None
frequency Handover
LOFD-001020
PS Inter-RAT Mobility
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

2
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

3
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

BTS3203E

4
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

5
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

6
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

BTS3203E

7
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

8
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

9
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

BTS3203E
L.E-RAB.NormRel.HOOut Multi-mode: None

GSM: None
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

PTT
UMTS: None
LTE: LOFD-001019 PS Inter-RAT Mobility
LBFD-00201801 between E-UTRAN and
UTRAN
LBFD-00201802
Coverage Based Intra-
LOFD-081218 frequency Handover
LTROFD-111201 Coverage Based Inter-
frequency Handover

65
UMTS: None
UTRAN
LBFD-00201802
frequency Handover
frequency Handover

BTS3203E

66
UMTS: None
UTRAN
LBFD-00201802
frequency Handover
frequency Handover

69
UMTS: None
UTRAN
LBFD-00201802
frequency Handover
frequency Handover

70
UMTS: None
UTRAN
LBFD-00201802
frequency Handover
frequency Handover

BTS3203E
1.6.4 Number of Abnormal E-RAB Releases for Outgoing

Handovers in a Cell
Counters

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

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

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

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

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

BTS3203E


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

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

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

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

el.HOOut RAB releases
for outgoing
handovers in a
cell

PTT for outgoing
handovers of
PTT services

BTS3203E


65 for outgoing
handovers of
QCI 65 services

66 for outgoing
handovers of
QCI 66 services

69 for outgoing
handovers of
QCI 69 services

70 for outgoing
handovers of
QCI 70 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.
Measurement Points
Figure 1-56 shows an X2-based handover, Figure 1-57 shows an S1-based handover, and
Figure 1-58 shows a handover from E-UTRAN to WCDMA network, GERAN, or TD-
SCDMA network. As shown at point C in Figure 1-56, Figure 1-57, or Figure 1-58, 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.

BTS3203E
Figure 1-56
Figure 1-57

BTS3203E
Figure 1-58
Formula
None
Unit
None
Related Features

RAB.AbnormRel.HOOut.Q GSM: None
CI.1
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

BTS3203E

CI.2
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

CI.3
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

CI.4
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

BTS3203E

CI.5
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

CI.6
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

CI.7
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

BTS3203E

CI.8
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

CI.9
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

RAB.AbnormRel.HOOut GSM: None
UMTS: None
frequency Handover
LOFD-001020
between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

BTS3203E

CI.PTT
UMTS: None
UTRAN
LBFD-00201802
LTROFD-111201 Coverage Based Inter-
frequency Handover

CI.65
UMTS: None
UTRAN
LBFD-00201802
frequency Handover
frequency Handover

CI.66
UMTS: None
UTRAN
LBFD-00201802
frequency Handover
frequency Handover

BTS3203E

CI.69
UMTS: None
UTRAN
LBFD-00201802
frequency Handover
frequency Handover

CI.70
UMTS: None
UTRAN
LBFD-00201802
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

BTS3203E
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-59, 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 addition:
The L.E-RAB.AbnormRel counter is incremented if the eNodeB determines that the E-RAB
to be released carries data.
The L.E-RAB.AbnormRel.Hst counter is incremented if the UE is in high-speed movement
and the E-RAB to be released carries 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.
As shown at point A in Figure 1-60, all E-RABs of the UE are released if the eNodeB sends a
UE CONTEXT RELEASE REQUEST message to the MME. 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",
"Handover Cancelled", "Redirection towards 1xRTT", or "Reduce load in serving cell" by
load-based redirection, the L.E-RAB.AbnormRel.eNBTot counter is incremented. In addition,
if the eNodeB determines that the E-RABs to be released carry data, the L.E-
RAB.AbnormRel counter is incremented. If the UE is in high-speed movement and the
eNodeB determines that the E-RABs to be released carry data, the L.E-RAB.AbnormRel.Hst
counter is incremented. If multiple E-RABs have been set up for the UE, the corresponding
counters are incremented by the number of E-RABs. When the MME sends a UE CONTEXT
RELEASE COMMAND message back to the eNodeB, the corresponding counters are not
incremented repeatedly.

BTS3203E
Figure 1-59
Figure 1-60
Formula
None
Unit
None
Related Features
L.E-RAB.AbnormRel Multi-mode: None

GSM: None
UMTS: None

BTS3203E

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

in a Cell
Counters

el.Radio releases of
activated E-
RABs due to
faults at the
radio network
layer

el.TNL releases of
activated E-
RABs due to
faults at the
transport
network layer

el.Cong releases of
activated E-
RABs due to
network
congestion

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

BTS3203E


el.MME releases of
activated E-
RABs due to
faults on the
MME side

el.MMETot RAB releases
due to faults on
the MME side

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

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

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

BTS3203E


el.Radio.UuNo releases of
Reply activated E-
RABs because
of no responses
from the UE

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

el.Cong.PreEm releases of
p activated E-
RABs because
of radio
resource
preemption

el.Cong.Load releases of
activated E-
RABs because
of radio
resource
overload

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

BTS3203E


el.TNL.Load releases of
activated E-
RABs because
of transport
resource
overload

el.MMETot.VoI releases of E-
P RABs for voice
services
because of
faults on the
MME side

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

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

BTS3203E


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

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

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

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

BTS3203E


el.Cong.VoIP releases of
activated E-
RABs for voice
services
because of
radio network
congestion

el.MME.VoIP releases of
activated E-
RABs for voice
services
because of
faults on the
MME side

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

el.Cong.PreEm releases of
p.VoIP activated E-
RABs for voice
services
because of
radio resource
preemption

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

BTS3203E


el.TNL.PreEmp releases of
.VoIP activated E-
RABs for voice
services
because of
transport
resource
preemption

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

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

BTS3203E
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-62, 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-62, 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-63, when the eNodeB sends an E-RAB RELEASE
INDICATION message to the MME, the counters are measured as follows:

BTS3203E
(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-63, 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.

BTS3203E
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).

BTS3203E
(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-61

BTS3203E
Figure 1-62
Figure 1-63
Figure 1-64
Formula
None
Unit
None

BTS3203E
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
LOFD-00102901 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

BTS3203E

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

BTS3203E

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

BTS3203E

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

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

Synchronization State
Counters

RAB.Release.U released E-
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-65, Figure 1-66, Figure 1-67, or Figure 1-68, 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-65

BTS3203E
Figure 1-66
Figure 1-67
Figure 1-68
Formula
None
Unit
None

BTS3203E
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
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

BTS3203E
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
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

BTS3203E


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
eB initiated by the
eNodeB in a
cell

BTS3203E
Description
The counters measure the number of E-RAB releases initiated by eNodeB for services with a
specific QCI ranging from 1 to 9 and the total number of E-RAB releases initiated by the
eNodeB in a cell.
Measurement Points
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-69
Figure 1-70
Formula
None

BTS3203E
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

BTS3203E

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

BTS3203E


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

BTS3203E


RAB.Rel.MME E-RAB releases
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.
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-71

BTS3203E
Figure 1-72
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

BTS3203E

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

RAB.Left.QCI. remaining E-
1 RABs for
services with
QCI of 1 in a
cell

BTS3203E


2 RABs for
services with
QCI of 2 in a
cell

3 RABs for
services with
QCI of 3 in a
cell

4 RABs for
services with
QCI of 4 in a
cell

5 RABs for
services with
QCI of 5 in a
cell

6 RABs for
services with
QCI of 6 in a
cell

7 RABs for
services with
QCI of 7 in a
cell

8 RABs for
services with
QCI of 8 in a
cell

BTS3203E


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

remaining E-
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

BTS3203E

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

BTS3203E
1.6.12 Number of E-RAB Releases Initiated by the eNodeB

Because of the S1 RESET in a Cell
Counters

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

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

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

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

BTS3203E


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

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

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

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

BTS3203E


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

BTS3203E
Figure 1-73
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

BTS3203E

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

BTS3203E
1.6.13 Number of E-RAB Releases Initiated by the MME Because

of the S1 RESET in a Cell
Counters

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

initiated by the
MME with QCI
of 2 because of
the S1 RESET
in a cell

initiated by the
MME with QCI
of 3 because of
the S1 RESET
in a cell

initiated by the
MME with QCI
of 4 because of
the S1 RESET
in a cell

initiated by the
MME with QCI
of 5 because of
the S1 RESET
in a cell

BTS3203E


initiated by the
MME with QCI
of 6 because of
the S1 RESET
in a cell

initiated by the
MME with QCI
of 7 because of
the S1 RESET
in a cell

initiated by the
MME with QCI
of 8 because of
the S1 RESET
in a cell

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.

BTS3203E
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-74
Formula
None
Unit
None
Related Features

RAB.Rel.S1Reset.MME.QC GSM: None
I.1
UMTS: None

I.2
UMTS: None

BTS3203E

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

BTS3203E
1.6.14 Number of MME-triggered Abnormal E-RAB Releases

Counters

RAB.AbnormR MME-triggered
el.MME.QCI.2 abnormal
releases of
activated E-
RABs for
services with
the QCI of 2

releases of
activated E-
RABs for
services with
the QCI of 3

releases of
activated E-
RABs for
services with
the QCI of 4

releases of
activated E-
RABs for
services with
the QCI of 5

releases of
activated E-
RABs for
services with
the QCI of 6

BTS3203E


releases of
activated E-
RABs for
services with
the QCI of 7

releases of
activated E-
RABs for
services with
the QCI of 8

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-76, 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

BTS3203E
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-75
Figure 1-76
Formula
None
Unit
None

BTS3203E
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

BTS3203E
1.6.15 Number of Abnormal E-RAB Releases for Other Reasons in

a Cell
Counters

el.Other releases of
activated E-
RABs due to
other reasons

el.Other.VoIP releases of
activated E-
RABs for voice
services due to
other reasons

el.Radio.Other releases of
activated E-
RABs due to
other faults at
the radio
network layer

el.Radio.Other. releases of
VoIP activated E-
RABs for voice
services due to
other faults at
the radio
network layer

el.TNL.Other releases of
activated E-
RABs due to
other faults at
the transport
network lay

BTS3203E


el.TNL.Other.V releases of
oIP activated E-
RABs for voice
services due to
other faults at
the transport
network layer

el.Cong.Other releases of
activated E-
RABs due to
other radio
resource
congestion
reaso

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-79, 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

BTS3203E
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-79, 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", "Handover Cancelled", or "Reduce load in serving cell" by load-based
redirection, 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

BTS3203E
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", "Handover Cancelled",or "Reduce load in serving cell" by load-based
redirection, and the corresponding E-RAB for services of QCI 1 carries data, the counters are
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-77

BTS3203E
Figure 1-78
Figure 1-79
Figure 1-80
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

BTS3203E
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

BTS3203E
1.6.16 Number of MME-initiated Abnormal Releases of E-RABs

During Handover Executions
Counters

RAB.AbnormR MME-initiated
el.MME.HOOu abnormal
t.QCI.1 releases of E-
RABs for
services with a
QCI of 1 during
handover
executions

RABs for
services with a
QCI of 2 during
handover
executions

RABs for
services with a
QCI of 3 during
handover
executions

RABs for
services with a
QCI of 4 during
handover
executions

BTS3203E


RABs for
services with a
QCI of 5 during
handover
executions

RABs for
services with a
QCI of 6 during
handover
executions

RABs for
services with a
QCI of 7 during
handover
executions

RABs for
services with a
QCI of 8 during
handover
executions

RABs for
services with a
QCI of 9 during
handover
executions

BTS3203E


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-81, 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-82, 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-83, 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-84, 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

BTS3203E
L.E-RAB.AbnormRel.MME.HOOut counter is incremented by the number of all E-RABs of

all QCIs.
Figure 1-81
Figure 1-82

BTS3203E
Figure 1-83
Figure 1-84
Formula
None
Unit
None

BTS3203E
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

BTS3203E

Out.QCI.9
UMTS: None

Out
UMTS: None
1.6.17 Number of Normal E-RAB Releases Caused by Inactivity

Timer Expiration
Counters

RAB.Rel.eNod eNodeB-
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

BTS3203E
Unit
None
Related Features

RAB.Rel.eNodeB.Userinact GSM: None
UMTS: None
1.6.18 Number of Normal Releases of E-RABs for Inter-RAT

Outgoing Handovers
Counters

IRatHOOut.QC of QCI 1 E-
I.1 RABs for inter-
RAT outgoing
handovers

I.2 RABs for inter-
RAT outgoing
handovers

I.3 RABs for inter-
RAT outgoing
handovers

I.4 RABs for inter-
RAT outgoing
handovers

BTS3203E


I.5 RABs for inter-
RAT outgoing
handovers

I.6 RABs for inter-
RAT outgoing
handovers

I.7 RABs for inter-
RAT outgoing
handovers

I.8 RABs for inter-
RAT outgoing
handovers

I.9 RABs for inter-
RAT outgoing
handovers

IRatHOOut of E-RABs for
inter-RAT
outgoing
handovers
Description
The counters measure the total number of normal releases of E-RABs and the numbers of
normal releases of E-RABs based on the QCIs for inter-RAT outgoing handovers in a cell.
3GPP TS 36.413 V10.4.0.

BTS3203E
Measurement Points
Figure 1-85 shows an inter-RAT handover to a WCDMA, GERAN, or TD-SCDMA cell. As
shown at point C in Figure 1-85, when the eNodeB receives a UE CONTEXT RELEASE
COMMAND message from the MME indicating that the inter-RAT handover succeeded, the
corresponding counter is incremented per QCI in the source cell if the source cell normally
releases E-RABs. In addition, the total number of normal releases of E-RABs in the source
cell is incremented and taken as the RAB.NormRel.IRatHOOut counter value.
Figure 1-85
Formula
None
Unit
None

BTS3203E
Related Features

RAB.NormRel.IRatHOOut. GSM: None
QCI.1
UMTS: None
LOFD-001020 between E-UTRAN and
UTRAN
between E-UTRAN and
GERAN

QCI.2
UMTS: None
UTRAN
between E-UTRAN and
GERAN

QCI.3
UMTS: None
UTRAN
between E-UTRAN and
GERAN

QCI.4
UMTS: None
UTRAN
between E-UTRAN and
GERAN

BTS3203E

QCI.5
UMTS: None
UTRAN
between E-UTRAN and
GERAN

QCI.6
UMTS: None
UTRAN
between E-UTRAN and
GERAN

QCI.7
UMTS: None
UTRAN
between E-UTRAN and
GERAN

QCI.8
UMTS: None
UTRAN
between E-UTRAN and
GERAN

BTS3203E

QCI.9
UMTS: None
UTRAN
between E-UTRAN and
GERAN

RAB.NormRel.IRatHOOut GSM: None
UMTS: None
UTRAN
between E-UTRAN and
GERAN
1.6.19 Number of E-RABs Released by Defective UEs in a Cell
Counters

RAB.AbnormR RABs released
el.eNBTot.UEA by defective
bnormal UEs in a cell
Description
This counter measures the number of times abnormal UEs release E-RAB in a cell when an
eNodeB can identify abnormal UEs based on service drops.
Measurement Points
As shown at point A in Figure 1-86, all E-RABs of the UE are released if the eNodeB sends a
UE CONTEXT RELEASE REQUEST message to the MME. If the identification of service
drops for defective UEs is enabled, the RAB.AbnormRel.eNBTot.UEAbnormal counter is
incremented if the UE is identified as a defective UE. If multiple E-RABs have been set up
for the UE, the counter is incremented by the number of E-RABs. When the MME sends a

BTS3203E
UE CONTEXT RELEASE COMMAND message back to the eNodeB, the counter is not
Figure 1-86
Figure 1-87
Formula
None
Unit
None
Related Features

RAB.AbnormRel.eNBTot.U GSM: None
EAbnormal
UMTS: None

BTS3203E
1.6.20 Number of Normal Releases of E-RABs for Inter-Duplex-

mode Outgoing Handovers
Counters

InterFddTddHO of E-RABs for
Out inter-duplex-
mode outgoing
handovers

InterFddTddHO of QCI 1 E-
Out.QCI.1 RABs for inter-
duplex-mode
outgoing
handovers

duplex-mode
outgoing
handovers

duplex-mode
outgoing
handovers

duplex-mode
outgoing
handovers

BTS3203E


duplex-mode
outgoing
handovers

duplex-mode
outgoing
handovers

duplex-mode
outgoing
handovers

duplex-mode
outgoing
handovers

duplex-mode
outgoing
handovers
Description
The counters measure the total number of normal releases of E-RABs and the numbers of
normal releases of E-RABs per QCI for inter-duplex-mode outgoing handovers in a cell.
3GPP TS 36.413 V10.4.0.

BTS3203E
Measurement Points
Figure 1-88 shows an intra-eNodeB handover. Figure 1-89 shows an X2-based handover.
Figure 1-90 shows an S1-based handover. Figure 1-91 shows an intra-eNodeB handover
where the RRC connection is reestablished to a target cell for the UE. Figure 1-92 shows an
X2-based handover where the RRC connection is reestablished to a target eNodeB. Figure
1-93 shows an S1-based handover where the RRC connection is reestablished to a target
eNodeB. In all these handovers, the source and target cells work in different duplex modes.
is incremented by 1 per QCI in the source cell each time the source cell normally releases an
E-RAB that corresponds to the successful E-RAB setup in the target cell after an outgoing
handover is successfully performed. In addition, the total number of normal releases of E-
RABs in the source cell is incremented and taken as the L.E-
RAB.NormRel.InterFddTddHOOut counter value.
is incremented by 1 per QCI in the source cell each time the source cell normally releases an
E-RAB that corresponds to the successful E-RAB setup in the target cell after the RRC
connection is successfully reestablished to the target cell. In addition, the total number of
normal releases of E-RABs in the source cell is incremented and taken as the L.E-
RAB.NormRel.InterFddTddHOOut counter value.
Figure 1-88

BTS3203E
Figure 1-89
Figure 1-90

BTS3203E
Figure 1-91
Figure 1-92

BTS3203E
Figure 1-93
Formula
None
Unit
None
Related Features

RAB.NormRel.InterFddTdd GSM: None
HOOut
UMTS: None
LTE: LBFD-00201802 Coverage Based Inter-
frequency Handover

BTS3203E

HOOut.QCI.1
UMTS: None
frequency Handover

HOOut.QCI.2
UMTS: None
frequency Handover

HOOut.QCI.3
UMTS: None
frequency Handover

HOOut.QCI.4
UMTS: None
frequency Handover

HOOut.QCI.5
UMTS: None
frequency Handover

HOOut.QCI.6
UMTS: None
frequency Handover

HOOut.QCI.7
UMTS: None
frequency Handover

BTS3203E

HOOut.QCI.8
UMTS: None
frequency Handover

HOOut.QCI.9
UMTS: None
frequency Handover
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-94 shows the measurement points in a failed E-RAB setup procedure.

BTS3203E
Figure 1-94
Counters

RAB.FailEst.NoRe setup failures due to version earlier than
ply no responses from V100R003C00
the UE in a cell

RAB.FailEst.MME setup failures due to V100R006C00
faults on the MME
side

BTS3203E


RAB.FailEst.TNL setup failures due to V100R006C00
faults at the
transport network
layer

RAB.FailEst.RNL setup failures due to V100R006C00
faults at the radio
network layer

RAB.FailEst.NoRa setup failures due to V100R006C00
dioRes insufficient radio
resources

RAB.FailEst.Secur setup failures due to V100R006C00
ModeFail security mode
configuration
failures

dioRes.SRS insufficient SRS
resources

dioRes.PUCCH insufficient PUCCH
resources

RAB.FailEst.SRBR setup failures V100R007C00
eset because the RLC
PDU for an SRB has
been retransmitted
for the maximum
number of times

RAB.FailEst.TNL. setup failures V100R007C00
DLRes because of
insufficient
downlink transport
resources

RAB.FailEst.TNL. setup failures V100R007C00
ULRes because of
insufficient uplink
transport resources

BTS3203E


RAB.FailEst.NoRa setup failures V100R007C00
dioRes.DLThrpLic because of
insufficient licensed
downlink traffic
volume

dioRes.ULThrpLic because of
uplink traffic
volume

dioRes.DLSatis because of a low
downlink
satisfaction rate

dioRes.ULSatis because of a low
uplink satisfaction
rate
1526729957 L.E- Number of setup BTS3203E LTE:

RAB.FailEst.NoRe failures of E-RABs V100R007C00
ply.VoIP for voice services
because of no
responses from the
UE in a cell

RAB.FailEst.MME failures of E-RABs V100R007C00
.VoIP for voice services
the MME side

RAB.FailEst.TNL. failures of E-RABs V100R007C00
VoIP for voice services
because of faults at
the transport
network layer

RAB.FailEst.RNL. failures of E-RABs V100R007C00
because of faults at
the radio network
layer

BTS3203E


RAB.FailEst.NoRa failures of E-RABs V100R007C00
dioRes.VoIP for voice services
because of
insufficient radio
resources

RAB.FailEst.Secur failures of E-RABs V100R007C00
ModeFail.VoIP for voice services
because of security
mode configuration
failures

RAB.FailEst.SRBR failures of E-RABs V100R007C00
eset.VoIP for voice services
because the RLC
PDU for an SRB has
been retransmitted
for the maximum
number of times

dioRes.SRS.VoIP for voice services
because of
insufficient SRS
resources

dioRes.PUCCH.Vo for voice services
IP because of
insufficient PUCCH
resources

dioRes.DLThrpLic. for voice services
VoIP because of
downlink traffic
volume

BTS3203E


dioRes.ULThrpLic. for voice services
VoIP because of
uplink traffic
volume

dioRes.DLSatis.VoI for voice services
P because of a low
downlink
satisfaction rate

dioRes.ULSatis.VoI for voice services
P because of a low
uplink satisfaction
rate

DLRes.VoIP for voice services
because of
insufficient
downlink transport
resources

ULRes.VoIP for voice services
because of
insufficient uplink
transport resources

RAB.FailEst.RNL. setup failures due to V100R011C10
eNodeB.NormRel normal release
initiated by eNodeB

eNodeB.AbnormRe abnormal release
l initiated by eNodeB

RAB.FailEst.Other setup failures due to V100R011C10
other reasons

BTS3203E


RAB.FailEst.Other. failures of E-RABs V100R011C10
due to other reasons

Other other reasons at the
radio network layer

RAB.FailEst.RNL. failures of E-RABs V100R011C10
Other.VoIP for voice services
at the radio network
layer

RAB.FailEst.TNL. setup failures due to V100R011C10
Other other reasons at the
transport network
layer

Other.VoIP for voice services
at the transport
network layer

dioRes.Other insufficiency of
other radio resources

dioRes.Other.VoIP for voice services
due to insufficiency
of other radio
resources

dioRes.DLSatis.QC with a QCI of 2
I2 because of a low
downlink
satisfaction rate

BTS3203E


I3 because of a low
downlink
satisfaction rate

I4 because of a low
downlink
satisfaction rate

dioRes.ULSatis.QC with a QCI of 2
I2 because of a low
uplink satisfaction
rate

I3 because of a low
uplink satisfaction
rate

I4 because of a low
uplink satisfaction
rate

RAB.FailEst.NoRa setup failures for V100R011C10
dioRes.DLSatis.PT PTT services
T because of a low
downlink
satisfaction rate

dioRes.ULSatis.PT for PTT services
T because of a low
uplink satisfaction
rate

BTS3203E


RAB.FailEst.X2AP setup failures V100R011C10
because of conflicts
with X2AP-related
procedures
1526739741 L.E- Number of voice- BTS3203E LTE:

RAB.FailEst.X2AP. service E-RAB V100R011C10
VoIP setup failures
because of conflicts
with X2AP-related
procedures

dioRes.DLSatis.QC QCI 65 services
I65 because of a low
downlink
satisfaction rate

dioRes.DLSatis.QC QCI 66 services
downlink
satisfaction rate

dioRes.ULSatis.QC QCI 65 services
uplink satisfaction
rate

dioRes.ULSatis.QC QCI 66 services
uplink satisfaction
rate

dioRes.UserSpec because of the
limitation of the
maximum number
of Ues

BTS3203E


dioRes.RrcUserLic because of
number of UEs in
the
RRC_CONNECTE
D state

RAB.FailEst.Poor failures of E-RABs V100R011C10
Cover.VoIP for voice services
due to weak
coverage
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- 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

BTS3203E
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.QCI6
5
L.E-
RAB.FailEst.NoRad
ioRes.DLSatis.QCI6
6
L.E-
RAB.FailEst.NoRad
ioRes.DLSatis.PTT
L.E- L.E-
ioRes.ULSatis ioRes.ULSatis.VoIP

BTS3203E
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.QCI6
5
L.E-
RAB.FailEst.NoRad
ioRes.ULSatis.QCI6
6
L.E-
RAB.FailEst.NoRad
ioRes.ULSatis.PTT
L.E- -
RAB.FailEst.NoRad
ioRes.RrcUserLic
L.E- -
RAB.FailEst.NoRad
ioRes.UserSpec
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

BTS3203E
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- 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

BTS3203E
L.E- L.E- - -
RAB.FailEst.Other RAB.FailEst.Other.
VoIP
L.E- L.E- - -
RAB.FailEst.RNL.O RAB.FailEst.RNL.O
ther ther.VoIP
L.E- L.E- - -
RAB.FailEst.TNL.O RAB.FailEst.RNL.O
ther ther.VoIP
L.E- - -
RAB.FailEst.TNL.O
ther.VoIP
L.E- L.E- - -
ioRes.Other ioRes.Other.VoIP
L.E- L.E- - -
RAB.FailEst.X2AP RAB.FailEst.X2AP.
VoIP
1.7.1 Number of E-RAB Setup Failures for Different Causes in a

Cell
Counters

RAB.FailEst.N RAB setup
oReply failures due to
no responses
from the UE in
a cell

RAB.FailEst.M RAB setup
ME failures due to
faults on the
MME side

BTS3203E


RAB.FailEst.T RAB setup
NL failures due to
faults at the
transport
network layer

RAB.FailEst.R RAB setup
NL failures due to
faults at the
radio network
layer

oRadioRes failures due to
insufficient
radio resources

RAB.FailEst.Se RAB setup
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
RBReset failures because
the RLC PDU
for an SRB has
been
retransmitted
for the
maximum
number of
times

BTS3203E


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

RAB.FailEst.N setup failures of
oReply.VoIP E-RABs for
voice services
because of no
responses from
the UE in a cell

BTS3203E


RAB.FailEst.M setup failures of
ME.VoIP E-RABs for
voice services
because of
faults on the
MME side

RAB.FailEst.T setup failures of
NL.VoIP E-RABs for
voice services
because of
faults at the
transport
network layer

RAB.FailEst.R setup failures of
NL.VoIP E-RABs for
voice services
because of
faults at the
radio network
layer

oRadioRes.VoI E-RABs for
P voice services
because of
insufficient
radio resources

RAB.FailEst.Se setup failures of
curModeFail.Vo E-RABs for
IP voice services
because of
security mode
configuration
failures

BTS3203E


RAB.FailEst.S setup failures of
RBReset.VoIP E-RABs for
voice services
because the
RLC PDU for
an SRB has
been
retransmitted
for the
maximum
number of
times

oRadioRes.SRS E-RABs for
.VoIP voice services
because of
insufficient
SRS resources

oRadioRes.PU E-RABs for
CCH.VoIP voice services
because of
insufficient
PUCCH
resources

oRadioRes.DLT E-RABs for
hrpLic.VoIP voice services
because of
insufficient
licensed
downlink traffic
volume

oRadioRes.ULT E-RABs for
hrpLic.VoIP voice services
because of
insufficient
licensed uplink
traffic volume

BTS3203E


oRadioRes.DLS E-RABs for
atis.VoIP voice services
because of a
low downlink
satisfaction rate

oRadioRes.ULS E-RABs for
atis.VoIP voice services
because of a
low uplink
satisfaction rate

NL.DLRes.VoI E-RABs for
P voice services
because of
insufficient
downlink
transport
resources

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

BTS3203E


oRadioRes.DLS E-RABs with a
atis.QCI2 QCI of 2
because of a
low downlink
satisfaction rate

atis.QCI3 QCI of 3
because of a
low downlink
satisfaction rate

atis.QCI4 QCI of 4
because of a
low downlink
satisfaction rate

oRadioRes.ULS E-RABs with a
atis.QCI2 QCI of 2
because of a
low uplink
satisfaction rate

atis.QCI3 QCI of 3
because of a
low uplink
satisfaction rate

atis.QCI4 QCI of 4
because of a
low uplink
satisfaction rate

BTS3203E


oRadioRes.DLS failures for PTT
atis.PTT services
because of a
low downlink
satisfaction rate

oRadioRes.ULS E-RABs for
atis.PTT PTT services
because of a
low uplink
satisfaction rate

RAB.FailEst.X RAB setup
2AP failures because
of conflicts
with X2AP-
related
procedures

RAB.FailEst.X voice-service E-
2AP.VoIP RAB setup
failures because
of conflicts
with X2AP-
related
procedures

oRadioRes.DLS failures for QCI
atis.QCI65 65 services
because of a
low downlink
satisfaction rate

oRadioRes.DLS failures for QCI
because of a
low downlink
satisfaction rate

BTS3203E


oRadioRes.ULS failures for QCI
because of a
low uplink
satisfaction rate

oRadioRes.ULS failures for QCI
because of a
low uplink
satisfaction rate

oRadioRes.User failures because
Spec of the limitation
of the
maximum
number of Ues

oRadioRes.Rrc failures because
UserLic of insufficient
licensed
number of UEs
in the
RRC_CONNE
CTED state

RAB.FailEst.Po setup failures of
orCover.VoIP E-RABs for
voice services
due to weak
coverage
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.

BTS3203E
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 and section 8.2.1 and 8.3.1.3 in 3GPP TS 36.413 V10.4.0.
The L.E-RAB.FailEst.ServiceMeas.VoIP counter applies only to LTE TDD.
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-95, 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(Not including ASN decoding error). 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-95, 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(Not including ASN decoding error). 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-96, 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(Not including ASN decoding
error). 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-96, 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

BTS3203E
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(Not
including ASN decoding error). 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.
(12) The L.E-RAB.FailEst.NoRadioRes.UserSpec counter is incremented each time the E-

RAB setup fails because of the limitation of the maximum number of UE.
(13) The L.E-RAB.FailEst.NoRadioRes.RrcUserLic counter is incremented each time the E-

RAB setup fails because of insufficient licensed number of UEs in the RRC_CONNECTED
state.
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.

BTS3203E
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, L.E-
RAB.FailEst.NoRadioRes.ULSatis, L.E-RAB.FailEst.NoRadioRes.UserSpec, and L.E-
RAB.FailEst.NoRadioRes.RrcUserLic.
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

BTS3203E
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

BTS3203E
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.
(11) The L.E-RAB.FailEst.PoorCover.VoIP counter is incremented each time a voice service
E-RAB fails to be set up because the eNodeB determines that the UE resides in a weak
coverage area during flash SRVCC.
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, L.E-RAB.FailEst.NoRadioRes.ULSatis.VoIP,
and L.E-RAB.FailEst.PoorCover.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.

BTS3203E
As shown at point A in Figure 1-97, 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-97, 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-98, 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-98, 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-99 or Figure 1-100, the L.E-
RAB.FailEst.RNL.eNodeB.NormRel counter is incremented by 1 each time if both of the
following conditions are met:
(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-99 or Figure 1-100, the L.E-
RAB.FailEst.RNL.eNodeB.AbnormRel counter is incremented by 1 each time if both of the
following conditions are met:

BTS3203E
(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.
As shown at point A in Figure 1-96, the L.E-RAB.FailEst.X2AP counter is incremented each
time the eNodeB receives an E-RAB SETUP REQUEST message from the MME but the
message cannot be handled because a cross between the E-RAB setup procedure and other
X2AP-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 cross between the E-RAB setup procedure and other
X2AP-related procedures occur when the source eNodeB receives an E-RAB SETUP
REQUEST message after sending a Handover Request message during an X2-based
handover.
As shown at point A in Figure 1-96, the L.E-RAB.FailEst.X2AP.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 cannot be handled because of a
cross between the E-RAB setup procedure and other X2AP-related procedures. If multiple E-
RAB setups for services with the QCI of 1 fail at the same time, the L.E-
RAB.FailEst.X2AP.VoIP counter is incremented by the number of failed E-RAB setups. A
cross between the E-RAB setup procedure and other X2AP-related procedures occur when the
source eNodeB receives an E-RAB SETUP REQUEST message after sending a Handover
Request message during an X2-based handover.
As shown at point A in Figure 1-96, the L.E-RAB.FailEst.ServiceMeas.VoIP counter is
incremented by 1 each time the eNodeB receives the E-RAB SETUP REQUEST message
including QCI 1 from the MME and has delivered service request-based measurement control
message but has not initiated service-triggered handover request.

BTS3203E
Figure 1-95
Figure 1-96

BTS3203E
Figure 1-97

BTS3203E
Figure 1-98

BTS3203E
Figure 1-99
Figure 1-100
Formula
None
Unit
None

BTS3203E
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

RAB.FailEst.NoRadioRes GSM: None
UMTS: None

RAB.FailEst.SecurModeFail GSM: None
UMTS: None

RAB.FailEst.NoRadioRes.S GSM: None
RS
UMTS: None

BTS3203E

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

BTS3203E

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

BTS3203E

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

BTS3203E

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

LSatis.QCI2
UMTS: None

LSatis.QCI3
UMTS: None

LSatis.QCI4
UMTS: None

LSatis.QCI2
UMTS: None

BTS3203E

LSatis.QCI3
UMTS: None

LSatis.QCI4
UMTS: None

LSatis.PTT
UMTS: None

LSatis.PTT
UMTS: None
L.E-RAB.FailEst.X2AP Multi-mode: None

GSM: None
UMTS: None

RAB.FailEst.X2AP.VoIP GSM: None
UMTS: None

LSatis.QCI65
UMTS: None

BTS3203E

LSatis.QCI66
UMTS: None

LSatis.QCI65
UMTS: None

LSatis.QCI66
UMTS: None

serSpec
UMTS: None

RAB.FailEst.NoRadioRes.R GSM: None
rcUserLic
UMTS: None
1.7.2 Number of E-RAB Setup Failures for Other Causes in a Cell

Counters

RAB.FailEst.Ot RAB setup
her failures due to
other reasons

BTS3203E


RAB.FailEst.Ot setup failures of
her.VoIP E-RABs for
voice services
due to other
reasons

NL.Other failures due to
other reasons at
the radio
network layer

RAB.FailEst.R setup failures of
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

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

BTS3203E


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.
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) 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-101, 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-101, 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

BTS3203E
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-102, 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-102, 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.

BTS3203E
Figure 1-101
Figure 1-102
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

BTS3203E
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

BTS3203E
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-103 shows the measurement points in an E-RAB modification procedure.
Figure 1-103
Counters

RAB.AttModify.Q modification V100R006C00
CI.1 attempts initiated by
UEs for services
a cell

BTS3203E


RAB.SuccModify. successful E-RAB V100R006C00
QCI.1 modifications
services with the
QCI of 1 in a cell

UEs for services
a cell

QCI.2 modifications
services with the
QCI of 2 in a cell

UEs for services
a cell

QCI.3 modifications
services with the
QCI of 3 in a cell

UEs for services
a cell

QCI.4 modifications
services with the
QCI of 4 in a cell

BTS3203E


UEs for services
a cell

QCI.5 modifications
services with the
QCI of 5 in a cell

UEs for services
a cell

QCI.6 modifications
services with the
QCI of 6 in a cell

UEs for services
a cell

QCI.7 modifications
services with the
QCI of 7 in a cell

UEs for services
a cell

BTS3203E


QCI.8 modifications
services with the
QCI of 8 in a cell

UEs for services
a cell

QCI.9 modifications
services with the
QCI of 9 in a cell

RAB.AttModify RAB modification V100R006C00
attempts initiated by
UEs in a cell

RAB.SuccModify successful E-RAB V100R006C00
modifications
initiated by UEs in a
cell

RAB.FailModify.N modification failures V100R006C00
oRadioRes due to insufficient
radio resources
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

BTS3203E
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
y.QCI.1 modification
attempts
initiated by UEs
for services
with the QCI of
1 in a cell

BTS3203E


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

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

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

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

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

BTS3203E


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

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

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

RAB.AttModif E-RAB
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.
Measurement Points
As shown at point A in Figure 1-104, 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.

BTS3203E
Figure 1-104
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

BTS3203E

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

BTS3203E
1.8.2 Number of Successful E-RAB Modifications in a Cell

Counters

RAB.SuccModi successful E-
fy.QCI.1 RAB
modifications
initiated by UEs
for services
with the QCI of
1 in a cell

fy.QCI.2 RAB
modifications
initiated by UEs
for services
with the QCI of
2 in a cell

fy.QCI.3 RAB
modifications
initiated by UEs
for services
with the QCI of
3 in a cell

fy.QCI.4 RAB
modifications
initiated by UEs
for services
with the QCI of
4 in a cell

fy.QCI.5 RAB
modifications
initiated by UEs
for services
with the QCI of
5 in a cell

BTS3203E


fy.QCI.6 RAB
modifications
initiated by UEs
for services
with the QCI of
6 in a cell

fy.QCI.7 RAB
modifications
initiated by UEs
for services
with the QCI of
7 in a cell

fy.QCI.8 RAB
modifications
initiated by UEs
for services
with the QCI of
8 in a cell

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.

BTS3203E
Measurement Points
As shown at point B in Figure 1-105, 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-105
Formula
None
Unit
None
Related Features
L.E-RAB.SuccModify.QCI. Multi-mode: None

1 GSM: None
UMTS: None

BTS3203E

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

BTS3203E
1.8.3 Number of E-RAB Modification Failures for Different

Causes in a Cell
Counters

RAB.FailModif RAB
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.
Measurement Points
As shown at point B in Figure 1-106, 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-106

BTS3203E
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
1526726760 L.LC.ULCong.Nu Number of times BTS3203E LTE:

m.Cell uplink congestion V100R006C00
occurs in a cell
1526726761 L.LC.ULCong.Dur. Duration of uplink BTS3203E LTE:

Cell congestion in a cell V100R006C00
1526726762 L.LC.DLCong.Nu Number of times BTS3203E LTE:

m.Cell downlink congestion V100R006C00
occurs in a cell
1526726763 L.LC.DLCong.Dur. Duration of BTS3203E LTE:

Cell downlink congestion V100R006C00
in a cell
1526726764 L.LC.User.Rel Number of GBR BTS3203E LTE:

service releases due V100R006C00
to congestion in a
cell

BTS3203E

1526727209 L.Cell.Unavail.Dur. Duration of cell BTS3203E LTE:

Sys unavailability due to V100R006C00
system faults

Manual unavailability due to V100R006C00
human factors
1526728320 L.Cell.Avail.Dur Duration of cell BTS3203E LTE:

availability V100R005C00
1526728465 L.Signal.Num.Uu Number of signaling BTS3203E LTE:

messages over the V100R006C00
Uu interface
1526728466 L.Signal.Num.DRX Number of DRX BTS3203E LTE:

.Reconfig reconfiguration V100R006C00
messages
1526728411 L.Voice.VQI.UL.Ex Number of times BTS3203E LTE:

cellent.Times uplink voice quality V100R006C00
is Excellent
1526728412 L.Voice.VQI.UL.G Number of times BTS3203E LTE:

ood.Times uplink voice quality V100R006C00
is Good
1526728413 L.Voice.VQI.UL.Ac Number of times BTS3203E LTE:

cept.Times uplink voice quality V100R006C00
is Accept
1526728414 L.Voice.VQI.UL.Po Number of times BTS3203E LTE:

or.Times uplink voice quality V100R006C00
is Poor
1526728415 L.Voice.VQI.UL.Ba Number of times BTS3203E LTE:

d.Times uplink voice quality V100R006C00
is Bad
1526728416 L.Voice.VQI.DL.Ex Number of times BTS3203E LTE:

cellent.Times downlink voice V100R006C00
quality is Excellent
1526728417 L.Voice.VQI.DL.G Number of times BTS3203E LTE:

ood.Times downlink voice V100R006C00
quality is Good
1526728418 L.Voice.VQI.DL.Ac Number of times BTS3203E LTE:

cept.Times downlink voice V100R006C00
quality is Accept

BTS3203E

1526728419 L.Voice.VQI.DL.Po Number of times BTS3203E LTE:

or.Times downlink voice V100R006C00
quality is Poor
1526728420 L.Voice.VQI.DL.Ba Number of times BTS3203E LTE:

d.Times downlink voice V100R006C00
quality is Bad
1526728538 L.RRCRel.Dedicat Number of times BTS3203E LTE:

edPri.LTE.High that E-UTRAN is V100R006C00
configured as the
highest frequency
priority in an
IMMCI IE

edPri.WCDMA.Hi that the WCDMA V100R006C00
gh network is
configured as the
highest frequency
priority in an
IMMCI IE

edPri.GERAN.Hig that GERAN is V100R006C00
h configured as the
highest frequency
priority in an
IMMCI IE
1526728444 L.Cell.UserLimit.P Number of BTS3203E LTE:

reEmp.Num successful V100R006C00
preemptions
triggered due to user
limitation

EnergySaving unavailability due to V100R006C00
energy saving
1526728494 L.Sps.UL.SchNum Number of uplink BTS3203E LTE:

semi-persistent V100R006C00
scheduling times in
a cell
1526728495 L.Sps.DL.SchNum Number of downlink BTS3203E LTE:

semi-persistent V100R006C00
scheduling times in
a cell

BTS3203E

1526728562 L.Sps.UL.ErrNum Number of failed BTS3203E LTE:

uplink semi- V100R006C00
persistent scheduling
transmissions in a
cell
1526728563 L.Sps.DL.ErrNum Number of failed BTS3203E LTE:

downlink semi- V100R006C00
transmissions in a
cell
1526728547 L.Cdrx.Enter.Num Number of times a BTS3203E LTE:

UE in connected V100R006C00
mode enters DRX in
RRC_CONECTED
mode
1526728548 L.Cdrx.Exit.Num Number of times a BTS3203E LTE:

UE in connected V100R006C00
mode exits DRX in
RRC_CONECTED
mode
1526728549 L.Cdrx.Active.TtiN Total number of BTS3203E LTE:

um TTIs for DRX UEs V100R006C00
in active state
1526728550 L.Cdrx.Sleep.TtiN Total number of BTS3203E LTE:

um TTIs for DRX UEs V100R006C00
in sleep state
1526728551 L.Voip.Cdrx.Active Total number of BTS3203E LTE:

.TtiNum TTIs for DRX UEs V100R006C00
in active state and
performing VoIP
services
1526728552 L.Voip.Cdrx.Sleep. Total number of BTS3203E LTE:

TtiNum TTIs for DRX UEs V100R006C00
in dormant state and
performing VoIP
services
1526728911 L.Signal.Num.TtiB Number of messages BTS3203E LTE:

undling.Enter sent for instructing V100R006C00
UEs to enter TTI
bundling mode

BTS3203E

1526728912 L.Signal.Num.TtiB Number of messages BTS3203E LTE:

undling.Exit sent for instructing V100R006C00
UEs to exit TTI
bundling mode
1526729280 L.Signal.Num.SIB1 Times of ETWS- BTS3203E LTE:

.ETWS induced SIB1 V100R006C00
changes
1526729291 L.Signal.Num.WR Number of ETWS- BTS3203E LTE:

WR.ETWS induced WRITE- V100R006C00
REPLACE
WARNING
REQUEST
messages
1526729471 L.AQM.PacketDro Number of packets BTS3203E LTE:

pNum.QCI.6 discarded by AQM V100R007C00
for services with
QCI of 6

for services with
QCI of 7

for services with
QCI of 8

for services with
QCI of 9
1526729499 L.Dyn.ACBar.Trig Number of times BTS3203E LTE:

ger.Num that dynamic AC V100R007C00
Barring is triggered
1526729500 L.Dyn.ACBar.Canc Number of times BTS3203E LTE:

el.Num that dynamic AC V100R007C00
Barring is cancelled
1526729501 L.Dyn.ACBar.Adju Number of times BTS3203E LTE:

st.Num that parameters V100R007C00
related to dynamic
AC Barring are
adjusted
1526729502 L.Dyn.ACBar.Cont Control duration of BTS3203E LTE:

rol.Dur dynamic AC Barring V100R007C00

BTS3203E


edPri.TDSCDMA. that the TDSCDMA V100R007C00
High network is
configured as the
highest frequency
priority in an
IMMCI IE
1526729572 L.RRCRel.load.De Number of times BTS3203E LTE:

dicatedPri.TDSCD that the TDSCDMA V100R007C00
MA.High network is
configured as the
highest frequency
priority in an
IMMCI IE
Triggered Because
of High Load
1526729659 L.Signal.Num.S1 Number of S1 BTS3203E LTE:

signaling messages V100R007C00
received or sent by a
cell
1526729660 L.Signal.Num.X2 Number of X2 BTS3203E LTE:

signaling messages V100R007C00
received or sent by a
cell

dicatedPri.LTE.Hig that the E-UTRAN V100R007C00
h network is
configured as the
highest frequency
priority in an
IMMCI IE
Triggered Because
of High Load

dicatedPri.WCDM that the WCDMA V100R007C00
A.High network is
configured as the
highest frequency
priority in an
IMMCI IE
Triggered Because
of High Load

BTS3203E

1526730104 L.User.UL.Unsync. Number of times the BTS3203E LTE:

Dur.Index0 duration of a UE in V100R007C00
the out-of-
synchronization
state in a cell ranges
from 0s to 10s
(excluding 0s and
including 10s)

the out-of-
synchronization
from 10s to 20s
(excluding 10s and
including 20s)

the out-of-
synchronization
from 20s to 30s
(excluding 20s and
including 30s)

the out-of-
synchronization
from 30s to 40s
(excluding 30s and
including 40s)

the out-of-
synchronization
from 40s to 50s
(excluding 40s and
including 50s)

BTS3203E


the out-of-
synchronization
from 50s to 60s
(excluding 50s and
including 60s)

the out-of-
synchronization
from 60s to 120s
(excluding 60s and
including 120s)

the out-of-
synchronization in a
cell state ranges
from 120s to 200s
(excluding 120s and
including 200s)

the out-of-
synchronization
state in a cell is
greater than 200s
1526730236 L.Sps.UL.TB.Intvl Number of uplink BTS3203E LTE:

40ms semi-persistent V100R007C00
scheduling times in
a cell (within 40 ms)
1526730237 L.Sps.UL.TB.Intvl Number of failed BTS3203E LTE:

40ms.Err uplink semi- V100R007C00
transmissions within
40 ms in a cell

BTS3203E

1526730526 L.InterFreq.Load. Number of times the BTS3203E LTE:

Meas.Num.Cell eNodeB delivers the V100R007C00
load-triggered inter-
frequency
measurement
configuration to a
UE
1526730527 L.InterFreq.Load. Number of times the BTS3203E LTE:

MeasSucc.Num.Cel load-triggered inter- V100R007C00
l frequency
measurement is
successful
1526730528 L.InterFreq.HighL Duration in which a BTS3203E LTE:

oad.Dur.Cell cell with inter- V100R007C00
frequency load
balancing enabled is
in the high-load state
1526730529 L.InterFreq.HighL Number of times a BTS3203E LTE:

oad.Num.Cell cell with inter- V100R007C00
frequency load
balancing enabled
enters from the low-
load state to the
high-load state
1526732089 L.Cell.Unavail.Nu Number of times BTS3203E LTE:

m that a cell is V100R011C10
unavailable
1526732687 L.Voice.VQI.AMR Number of times BTS3203E LTE:

WB.UL.Excellent.T uplink voice quality V100R011C10
imes of AMR-WB
services is Excellent

WB.UL.Good.Time uplink voice quality V100R011C10
s of AMR-WB
services is Good

WB.UL.Accept.Ti uplink voice quality V100R011C10
mes of AMR-WB
services is Accept

WB.UL.Poor.Times uplink voice quality V100R011C10
of AMR-WB
services is Poor

BTS3203E


WB.UL.Bad.Times uplink voice quality V100R011C10
of AMR-WB
services is Bad

WB.DL.Excellent.T downlink voice V100R011C10
imes quality of AMR-WB
services is Excellent

WB.DL.Good.Time downlink voice V100R011C10
s quality of AMR-WB
services is Good

WB.DL.Accept.Ti downlink voice V100R011C10
mes quality of AMR-WB
services is Accept

WB.DL.Poor.Times downlink voice V100R011C10
quality of AMR-WB
services is Poor

WB.DL.Bad.Times downlink voice V100R011C10
quality of AMR-WB
services is Bad
1526732890 L.Voice.NormRel.U Number of normal BTS3203E LTE:

L.LowQuality voice call releases in V100R011C10
the cell (poor uplink
voice quality)
1526732891 L.Voice.NormRel.D Number of normal BTS3203E LTE:

L.LowQuality voice call releases in V100R011C10
the cell (poor
downlink voice
quality)
1526732892 L.Voice.UL.Silent. Number of times BTS3203E LTE:

Num that a UE V100R011C10
experiences uplink
voice mute in the
cell
1526732893 L.Voice.DL.Silent. Number of times BTS3203E LTE:

Num that a UE V100R011C10
experiences
downlink voice
mute in the cell

BTS3203E

1526732913 L.AISS.IntereNode Number of times BTS3203E LTE:

B.HoMeas.Att that an eNodeB V100R011C10
attempts to measure
the time difference
among eNodeBs by
using UEs
performing inter-
eNodeB handovers

B.CeMeas.Att that an eNodeB V100R011C10
attempts to measure
the time difference
among eNodeBs by
using inter-eNodeB
CEUs

B.HoMeas.Succ that an eNodeB V100R011C10
successfully
measures the time
difference among
eNodeBs by using
UEs that are
performing inter-
eNodeB handovers

B.CeMeas.Succ that an eNodeB V100R011C10
successfully
measures the time
difference among
eNodeBs by using
inter-eNodeB CEUs
1526733010 L.Sig.PowerCfg.Fai Number of cell BTS3203E LTE:

l.TimeOut received V100R011C10
configuration
message from centre
controller but
receive time was
expired
1526733011 L.Sig.PowerCfg.Att Number of cell BTS3203E LTE:

received V100R011C10
configuration
message from centre
controller
1526733199 L.Signal.Num.Nas Number of NAS BTS3203E LTE:

messages V100R011C10

BTS3203E

1526735577 L.PowerNull.DL.T Number of downlink BTS3203E LTE:

TI.Num subframes without V100R011C10
power
1526736656 L.SSAC.Dyn.ACBa Number of times BTS3203E LTE:

r.Trigger.Num dynamic SSAC is V100R011C10
triggered

r.Adjust.Num parameters related to V100R011C10
dynamic SSAC are
adjusted

r.Cancel.Num dynamic SSAC is V100R011C10
canceled
1526736659 L.SSAC.Dyn.ACBa Duration of dynamic BTS3203E LTE:

r.Control.Dur SSAC V100R011C10
1526736866 L.Cell.UserSpec.Pr Number of times BTS3203E LTE:

epEmp.PrepAtt.Nu preemptions are V100R011C10
m triggered by the
limitation of the UE
number specification
1526736869 L.Cell.UserLic.Lim Number of times the BTS3203E LTE:

it.Num licensed number of V100R011C10
UEs is limited
1526736870 L.Cell.UserLic.Pre Number of BTS3203E LTE:

pEmp.Succ.Num successful V100R011C10
preemptions
triggered by the
limitation of the
licensed number of
UEs
1526736889 L.ULIRC.PUSCH. Number of times BTS3203E LTE:

MRC.Num MRC is used on the V100R011C10
PUSCH
1526736890 L.ULIRC.PUSCH.I Number of times BTS3203E LTE:

RC.Num IRC is used on the V100R011C10
PUSCH
1526736891 L.CtrlIRC.PUCCH Number of times BTS3203E LTE:

.MRC.Num MRC is used on the V100R011C10
PUCCH
1526736892 L.CtrlIRC.PUCCH Number of times BTS3203E LTE:

.IRC.Num IRC is used on the V100R011C10
PUCCH

BTS3203E

1526736893 L.CtrlIRC.PRACH Number of times BTS3203E LTE:

.MRC.Num MRC is used on the V100R011C10
PRACH
1526736894 L.CtrlIRC.PRACH Number of times BTS3203E LTE:

.IRC.Num IRC is used on the V100R011C10
PRACH
1526737744 L.ULIRC.PUSCH. Number of times BTS3203E LTE:

SmartIRC.Num smart IRC is used on V100R011C10
the PUSCH
1526737821 L.SPID.SelectTgtP Number of SPID- BTS3203E LTE:

LMN.AttOut based target PLMN V100R011C10
selection attempts

Sys.S1Fail unavailability due to V100R011C10
S1 interface faults
1526737856 L.InterfHighSpeed. Number of times the BTS3203E LTE:

Trigger.Num eCoordinator V100R011C10
triggers interference
coordination in
high-speed railway
scenarios
1526737857 L.InterfHighSpeed. Number of times the BTS3203E LTE:

Cancel.Num eCoordinator stops V100R011C10
interference
coordination in
high-speed railway
scenarios
1526739725 L.VoiceUser.VoIPP Number of BTS3203E LTE:

ref.Succ successful V100R011C10
preferential accesses
performed by voice
service UEs
1526739752 L.Cell.eICIC.ABS. Number of ABSs in BTS3203E LTE:

Num a cell with eICIC V100R011C10
enabled
1526739788 L.Traffic.UL.PktDi Number of uplink BTS3203E LTE:

sorderLoss.Loss.Q PDCP SDUs of QCI V100R011C10
CI.1 1 discarded because
of SN disorder or
changes in a cell

BTS3203E

1526739807 L.Thrp.bits.UL.PD Total throughput of BTS3203E LTE:

CP.SDU.UDC.BefD uplink SDUs before V100R011C00
ecompn the decompression
of UDC services at
the PDCP layer
1526739808 L.Traffic.DRB.Avg. Average number of BTS3203E LTE:

UDC DRBs for UDC V100R011C00
services in a cell
1526740480 L.Sps.UL.SchNum. Number of times BTS3203E LTE:

Ptt uplink semi- V100R011C10
is performed for
PTT UEs in a cell
1526740481 L.Sps.DL.SchNum. Number of times BTS3203E LTE:

Ptt downlink semi- V100R011C10
is performed for
PTT UEs in a cell
1526740482 L.Sps.UL.ErrNum. Number of failed BTS3203E LTE:

Ptt uplink semi- V100R011C10
transmissions for
PTT UEs in a cell
1526740483 L.Sps.DL.ErrNum. Number of failed BTS3203E LTE:

Ptt downlink semi- V100R011C10
transmissions for
PTT UEs in a cell

CP.SDU.UDC.AftD uplink SDUs after V100R011C00
ecompn the decompression
of UDC services at
the PDCP layer

CP.SDU.BefUdcDe uplink SDUs before V100R011C00
compn the decompression
of UDC services at
the PDCP layer
1526741669 L.Voice.E2EVQI.E Number of times BTS3203E LTE:

xcellent.Times E2E VQIs are V100R011C10
Excellent
1526741670 L.Voice.E2EVQI.G Number of times BTS3203E LTE:

ood.Times E2E VQIs are Good V100R011C10

BTS3203E

1526741671 L.Voice.E2EVQI.A Number of times BTS3203E LTE:

ccept.Times E2E VQIs are V100R011C10
Accept
1526741672 L.Voice.E2EVQI.P Number of times BTS3203E LTE:

oor.Times E2E VQIs are Poor V100R011C10
1526741673 L.Voice.E2EVQI.B Number of times BTS3203E LTE:

ad.Times E2E VQIs are Bad V100R011C10

MRWB.Excellent.T E2E VQIs of AMR- V100R011C10
imes WB services are
Excellent

MRWB.Good.Time E2E VQIs of AMR- V100R011C10
s WB services are
Good

MRWB.Accept.Ti E2E VQIs of AMR- V100R011C10
mes WB services are
Accept

MRWB.Poor.Times E2E VQIs of AMR- V100R011C10
WB services are
Poor

MRWB.Bad.Times E2E VQIs of AMR- V100R011C10
WB services are Bad
1526741679 L.Voice.E2EVQI.T Total value of E2E BTS3203E LTE:

otalValue VQIs V100R011C10
1526741680 L.Voice.E2EVQI.A Total value of E2E BTS3203E LTE:

MRWB.TotalValue VQIs of AMR-WB V100R011C10
services
1526741681 L.Voice.VQI.UL.To Total value of uplink BTS3203E LTE:

talValue VQIs V100R011C10
1526741682 L.Voice.VQI.DL.To Total value of BTS3203E LTE:

talValue downlink VQIs V100R011C10
1526741683 L.Voice.VQI.AMR Total value of uplink BTS3203E LTE:

WB.UL.TotalValue VQIs of AMR-WB V100R011C10
services

BTS3203E

1526741684 L.Voice.VQI.AMR Total value of BTS3203E LTE:

WB.DL.TotalValue downlink VQIs of V100R011C10
AMR-WB services
1526741728 L.RRCRel.Lowloa Number of times the BTS3203E LTE:

d.DedicatedPri.LT highest dedicated V100R011C10
E.High priority was
assigned to E-UTRA
frequencies as
indicated in an
IMMCI IE sent from
a low-load cell
1526741841 L.Sps.DL.TB.Intvl Number of TBs BTS3203E LTE:

40ms transmitted using V100R011C10
downlink semi-
with a period of 40
ms in a cell
1526741842 L.Sps.DL.TB.Intvl Number of TBs BTS3203E LTE:

40ms.Err failed to be V100R011C10
transmitted using
downlink semi-
with a period of 40
ms in a cell
1526742133 L.Signal.CMAS.W Number of times BTS3203E LTE:

RWR.Num CMAS WRITE- V100R011C10
REPLACE
WARNING
REQUEST
messages are
received
1526742134 L.Signal.CMAS.Br Number of times BTS3203E LTE:

oadcastReq.Num CMAS warning V100R011C10
notifications are
requested to be
broadcast
1526742135 L.Signal.CMAS.Kil Number of times BTS3203E LTE:

lReq.Num CMAS KILL V100R011C10
REQUEST
messages are
received

BTS3203E

1526742136 L.Signal.CMAS.W Number of times BTS3203E LTE:

RWRProcSucc.Nu CMAS WARNING V100R011C10
m REQUEST
messages are
successfully
processed
1526742137 L.Signal.CMAS.Br Number of times BTS3203E LTE:

oadcastSucc.Num CMAS warning V100R011C10
notifications are
successfully
broadcast
1526742138 L.Signal.CMAS.Kil Number of times BTS3203E LTE:

lProcSucc.Num CMAS KILL V100R011C10
REQUEST
messages are
successfully
processed
1526742154 L.UE.Req.Drx.Rec Number of BTS3203E LTE:

onfig.Succ.Num successful responses V100R011C10
to UEs' requests for
configuring DRX
parameters in a cell
1526742155 L.UE.Req.Default. Number of BTS3203E LTE:

Drx.Succ.Num successful responses V100R011C10
to UEs' requests for
restoring DRX
1526742169 L.Cell.ElasticCarri Number of TTIs in BTS3203E LTE:

erEnableTti.Num which Elastic V100R011C10
Carrier takes effect
in a cell
1526743656 L.E2W.Load.Meas Number of times BTS3203E LTE:

TimeOut.Num.Cell MLB-triggered V100R012C00
measurements of
WCDMA
frequencies time out
1526743657 L.IRAT.HighLoad. Duration in which BTS3203E LTE:

Dur.Cell an E-UTRAN cell V100R012C00
with inter-RAT
MLB enabled is in
the high-load state
1526743747 L.Cell.PilotOffTti. Number of TTIs in BTS3203E LTE:

Num which some CRSs V100R012C00
are not transmitted

BTS3203E

1526745660 L.Radio.Load.Cell. Average downlink BTS3203E LTE:

Dl.Avg air interface load of V100R012C10
a cell
1526745956 L.Cdrx.UeDiffConf Number of UE- BTS3203E LTE:

ig.Num specific DRX V100R012C10
reconfiguration
times
1526746000 L.Signal.Num.PN. Number of PNs sent BTS3203E LTE:

ETWS due to ETWS in a V100R012C10
cell
1526746001 L.Signal.Num.SN.E Number of SNs sent BTS3203E LTE:

TWS due to ETWS in a V100R012C10
cell
The Algo.Cell function subset contains counters related to cell algorithms. The following
table shows the parent-child relationship of the counters.
L.Signal.Num.Uu L.Signal.Num.Nas
L.RRCRel.DedicatedPri.LTE.High L.RRCRel.load.DedicatedPri.LTE.High
L.RRCRel.Lowload.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.Enter.Num L.Cdrx.UeDiffConfig.Num
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
L.Voice.E2EVQI.Excellent.Times L.Voice.E2EVQI.AMRWB.Excellent.Times
L.Voice.E2EVQI.Good.Times L.Voice.E2EVQI.AMRWB.Good.Times
L.Voice.E2EVQI.Accept.Times L.Voice.E2EVQI.AMRWB.Accept.Times
L.Voice.E2EVQI.Poor.Times L.Voice.E2EVQI.AMRWB.Poor.Times

BTS3203E
L.Voice.E2EVQI.Bad.Times L.Voice.E2EVQI.AMRWB.Bad.Times
L.Voice.E2EVQI.TotalValue L.Voice.E2EVQI.AMRWB.TotalValue
L.Voice.VQI.UL.TotalValue L.Voice.VQI.AMRWB.UL.TotalValue
L.Voice.VQI.DL.TotalValue L.Voice.VQI.AMRWB.DL.TotalValue
1.9.1 Number of Times Uplink or Downlink Congestion Occurs

in a Cell
Counters
1526726760 L.LC.ULCong. Number of BTS3203E LTE L

Num.Cell times uplink
congestion
occurs in a cell
1526726762 L.LC.DLCong. Number of BTS3203E LTE L

Num.Cell times downlink
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

BTS3203E
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 BTS3203E LTE L

Dur.Cell uplink
congestion in a
cell
1526726763 L.LC.DLCong. Duration of BTS3203E LTE L

Dur.Cell downlink
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.

BTS3203E
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 BTS3203E LTE L

GBR service
releases due to
congestion in a
cell
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

BTS3203E
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 BTS3203E LTE L

Dur.Sys unavailability
due to system
faults

Dur.Manual unavailability
due to human
factors

Dur.EnergySavi unavailability
ng due to energy
saving

Dur.Sys.S1Fail unavailability
due to S1
interface faults
Description
The counters measure the duration of cell unavailability due to human operations, system
faults.Human operations include blocking and deactivating a cell by using MML commands.
System faults include board faults, 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), insufficiency of license resources, or unavailability of clocks.

BTS3203E
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.EnergyS Multi-mode: None

aving GSM: None
UMTS: None
LTE: LOFD-001025 Adaptive Power
LOFD-001042 Consumption
Intelligent Power-Off of
Carriers in the Same
Coverage
1.9.5 Duration of Cell Availability
Counters
1526728320 L.Cell.Avail.Du Duration of cell BTS3203E LTE L

r availability

BTS3203E
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 BTS3203E LTE L

Uu signaling
messages over
the Uu interface

Nas NAS messages
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.

BTS3203E
Measurement Points
The L.Signal.Num.Uu counter is incremented by 1 each time the eNodeB receives or sends a
UE-level air interface signaling message, including a non-access stratum (NAS) message in a
cell.
Formula
None
Unit
None
Related Features
L.Signal.Num.Uu Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002017 DRX
L.Signal.Num.Nas Multi-mode: None

GSM: None
UMTS: None
Management
1.9.7 Number of DRX Reconfiguration Messages
Counters

DRX.Reconfig DRX
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.

BTS3203E
Measurement Points
The L.Signal.Num.DRX.Reconfig counter is incremented by 1 each time the eNodeB sends
an RRC Connection Reconfiguration message to the UE to reconfigure DRX.
Formula
None
Unit
None
Related Features
L.Signal.Num.DRX.Reconfi Multi-mode: None

g GSM: None
UMTS: None
1.9.8 Uplink or Downlink Voice Quality
Counters
1526728411 L.Voice.VQI.U Number of BTS3203E LTE L

L.Excellent.Tim times uplink
es voice quality is
Excellent

L.Good.Times times uplink
voice quality is
Good

L.Accept.Times times uplink
voice quality is
Accept

L.Poor.Times times uplink
voice quality is
Poor

BTS3203E


L.Bad.Times times uplink
voice quality is
Bad
1526728416 L.Voice.VQI.D Number of BTS3203E LTE L

L.Excellent.Tim times downlink
es voice quality is
Excellent

L.Good.Times times downlink
voice quality is
Good

L.Accept.Times times downlink
voice quality is
Accept

L.Poor.Times times downlink
voice quality is
Poor

L.Bad.Times times downlink
voice quality is
Bad
Description
The counters measure the uplink or downlink voice quality of AMR-WB and AMR-NB
speech services in a cell when the VQMAlgoSwitch parameter in the ENodeBAlgoSwitch
MO is set to VQM_ALGO_SWITCH_AMR_ON or
VQM_ALGO_SWITCH_ADAPTIVE_ON.
Measurement Points
In a voice quality monitoring (VQM) period specified by VQMALGO.VQMAlgoPeriod, the
uplink and downlink VQIs of VoLTE UEs running AMR-WB services and AMR-NB services
are calculated. The corresponding counter is incremented by 1 each time the E2E VQI of a
VoLTE UE running an AMR-WB service is at a specified speech quality level. The speech
quality can be classified into five levels: Bad, Poor, Accept, Good, and Excellent.
Formula
None

BTS3203E
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

BTS3203E
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 BTS3203E LTE L

catedPri.LTE.Hi times that E-
gh UTRAN is
configured as
the highest
frequency
priority in an
IMMCI IE
1526729877 L.RRCRel.load. Number of BTS3203E LTE L

DedicatedPri.L times that the
TE.High E-UTRAN
network is
configured as
the highest
frequency
priority in an
IMMCI IE
Triggered
Because of
High Load

BTS3203E

1526741728 L.RRCRel.Low Number of BTS3203E LTE L

load.Dedicated times the
Pri.LTE.High highest
dedicated
priority was
assigned to E-
UTRA
frequencies as
indicated in an
IMMCI IE sent
from a low-load
cell
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.
The signaling flows involved in the counter(s) comply with section 5.3.8 in 3GPP TS 36.331
V10.4.0.
Measurement Points
As shown at point A in Figure 1-107, the eNodeB checks whether the RRC Connection
Release messages sent to UEs in a cell contain the dedicated priority as indicated in the
IMMCI IE. The L.RRCRel.DedicatedPri.LTE.High counter is incremented by 1 each time the
dedicated priority is contained in the message and the highest dedicated priority was assigned
to E-UTRAN frequencies.
Release messages sent to UEs in a high-load cell for load balancing contain the dedicated
priority as indicated in the IMMCI IE. The L.RRCRel.load.DedicatedPri.LTE.High counter is
incremented by 1 each time the dedicated priority is contained in the message and the highest
dedicated priority was assigned to E-UTRAN frequencies.
Release messages sent to UEs in a low-load cell for preventing UE reselection to high-load
cells in load balancing contain the dedicated priority as indicated in the IMMCI IE. The
L.RRCRel.Lowload.DedicatedPri.LTE.High counter is incremented by 1 each time the
dedicated priority is contained in the message and the highest dedicated priority was assigned
to E-UTRAN frequencies.

BTS3203E
Figure 1-107
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
LOFD-001112 SPID
MOCN Flexible Priority
Based Camping
L.RRCRel.load.DedicatedPr Multi-mode: None

i.LTE.High GSM: None
UMTS: None
LTE: LOFD-070215 Intra-LTE User Number
Load Balancing
L.RRCRel.Lowload.Dedicat Multi-mode: None

edPri.LTE.High GSM: None
UMTS: None
LTE: LOFD-001032 Intra-LTE Load Balancing

BTS3203E
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
MA.High WCDMA
network is
configured as
the highest
frequency
priority in an
IMMCI IE

DedicatedPri.W times that the
CDMA.High WCDMA
network is
configured as
the highest
frequency
priority in an
IMMCI IE
Triggered
Because of
High Load
Description
The counter measures the times that an RRC Connection Release message contains an
idleModeMobilityControlInfo IE in which the WCDMA network is configured with the
highest frequency priority in a cell.
Measurement Points
As shown at point A in Figure 1-108, the L.RRCRel.DedicatedPri.WCDMA.High counter is
incremented by 1 each time the eNodeB sends an RRC Connection Release message to the
UE and the message contains an idleModeMobilityControlInfo IE in which the WCDMA
network is configured as the highest frequency priority in a cell.
The L.RRCRel.load.DedicatedPri.WCDMA.High counter is incremented by 1 each time the
eNodeB sends an RRC Connection Release message to the UE and the message contains an
idleModeMobilityControlInfo IE in which the WCDMA network is configured as the highest
frequency priority in a high-load cell triggered by load balancing.

BTS3203E
Figure 1-108
Formula
None
Unit
None
Related Features
L.RRCRel.DedicatedPri.W Multi-mode: None

CDMA.High GSM: None
UMTS: None
LOFD-001044 SPID
LOFD-001112 Inter-RAT Load Sharing to
UTRAN
Based Camping
L.RRCRel.load.DedicatedPr Multi-mode: None

i.WCDMA.High GSM: None
UMTS: None
LTE: LOFD-001044 Inter-RAT Load Sharing to
UTRAN

BTS3203E
1.9.11 Number of Times that GERAN is Configured as the

Highest Frequency Priority in an IMMCI IE
Counters

catedPri.GERA times that
N.High GERAN is
configured as
the highest
frequency
priority in an
IMMCI IE
Description
The counter measure the times that an RRC Connection Release message contains an
idleModeMobilityControlInfo IE in which GERAN is configured as the highest frequency
priority in a cell.
Measurement Points
As shown at point A in Figure 1-109, the L.RRCRel.DedicatedPri.GERAN.High counter is
UE and the message contains an idleModeMobilityControlInfo IE in which the GERAN is
configured as the highest frequency priority in a cell.
Figure 1-109
Formula
None

BTS3203E
Unit
None
Related Features
L.RRCRel.DedicatedPri.GE Multi-mode: None

RAN.High GSM: None
UMTS: None
LOFD-001112 SPID
Based Camping
1.9.12 Number of Successful Preemptions Triggered due to User

Limitation
Counters
1526728444 L.Cell.UserLim Number of BTS3203E LTE L

it.PreEmp.Num successful
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

BTS3203E
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 Times Semi-Persistent Scheduling is Performed

in a Cell
Counters
1526728494 L.Sps.UL.SchN Number of BTS3203E LTE L

um uplink semi-
persistent
scheduling
times in a cell
1526728495 L.Sps.DL.SchN Number of BTS3203E LTE L

um downlink semi-
persistent
scheduling
times in a cell
1526730236 L.Sps.UL.TB.In Number of BTS3203E LTE L

tvl40ms uplink semi-
persistent
scheduling
times in a cell
(within 40 ms)
1526740480 L.Sps.UL.SchN Number of BTS3203E LTE L

um.Ptt times uplink
semi-persistent
scheduling is
performed for
PTT UEs in a
cell

BTS3203E

1526740481 L.Sps.DL.SchN Number of BTS3203E LTE L

um.Ptt times downlink
semi-persistent
scheduling is
performed for
PTT UEs in a
cell
1526741841 L.Sps.DL.TB.In Number of TBs BTS3203E LTE L

tvl40ms transmitted
using downlink
semi-persistent
scheduling with
a period of 40
ms in a cell
Description
The counters measure the number of times uplink or downlink semi-persistent scheduling is
performed in a cell.
Measurement Points
The L.Sps.UL.SchNum or L.Sps.DL.SchNum counter is incremented by 1 each time semi-
persistent scheduling is performed for a VoLTE service in the uplink or downlink,
respectively.
The L.Sps.UL.SchNum.Ptt or L.Sps.DL.SchNum.Ptt counter is incremented by 1 each time
semi-persistent scheduling is performed for an enhanced-extended-QCI-based PTT service in
the uplink or downlink in a cell, respectively.
The L.Sps.UL.TB.Intvl40ms or L.Sps.DL.TB.Intvl40ms counter is incremented by 1 each
time semi-persistent scheduling with a period of 40 ms is performed for a VoLTE service in
the uplink or downlink in a cell, respectively.
The internal timer of the eNodeB has a deviation of one period, and therefore the values of the
counters have deviation to the actual duration.
Formula
None
Unit
None

BTS3203E
Related Features
L.Sps.UL.SchNum Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001016 VoIP Semi-persistent
Scheduling
L.Sps.DL.SchNum Multi-mode: None

GSM: None
UMTS: None
Scheduling
L.Sps.UL.TB.Intvl40ms Multi-mode: None

GSM: None
UMTS: None
Scheduling
L.Sps.UL.SchNum.Ptt Multi-mode: None

GSM: None
UMTS: None
LOFD-081218 Scheduling
LTROFD-111201 Enhanced Extended QCI
L.Sps.DL.SchNum.Ptt Multi-mode: None

GSM: None
UMTS: None
L.Sps.DL.TB.Intvl40ms Multi-mode: None

GSM: None
UMTS: None
Scheduling

BTS3203E
1.9.14 Number of Failed Semi-Persistent Scheduling

Transmissions in a Cell
Counters
1526728562 L.Sps.UL.ErrN Number of BTS3203E LTE L

um failed uplink
semi-persistent
scheduling
transmissions in
a cell
1526728563 L.Sps.DL.ErrN Number of BTS3203E LTE L

um failed downlink
semi-persistent
scheduling
transmissions in
a cell
1526730237 L.Sps.UL.TB.In Number of BTS3203E LTE L

tvl40ms.Err failed uplink
semi-persistent
scheduling
transmissions
within 40 ms in
a cell
1526740482 L.Sps.UL.ErrN Number of BTS3203E LTE L

um.Ptt failed uplink
semi-persistent
scheduling
transmissions
for PTT UEs in
a cell
1526740483 L.Sps.DL.ErrN Number of BTS3203E LTE L

um.Ptt failed downlink
semi-persistent
scheduling
transmissions
for PTT UEs in
a cell

BTS3203E

1526741842 L.Sps.DL.TB.In Number of TBs BTS3203E LTE L

tvl40ms.Err failed to be
transmitted
using downlink
semi-persistent
scheduling with
a period of 40
ms in a cell
Description
The counters measure the number of failed uplink or downlink semi-persistent scheduling
transmissions in a cell.
Measurement Points
The L.Sps.UL.ErrNum or L.Sps.DL.ErrNum counter is incremented by 1 each time semi-
persistent scheduling is performed for a VoLTE service in the uplink or downlink,
respectively, and the transmission fails.
The L.Sps.UL.ErrNum.Ptt or L.Sps.DL.ErrNum.Ptt counter is incremented by 1 each time
semi-persistent scheduling is performed for an enhanced-extended-QCI-based PTT service in
the uplink or downlink, respectively, and the transmission fails.
The L.Sps.UL.TB.Intvl40ms.Err or L.Sps.DL.TB.Intvl40ms.Err counter is incremented by 1
each time semi-persistent scheduling with a period of 40 ms is performed for a VoLTE service
in the uplink or downlink in a cell, respectively, and the transmission fails.
Formula
None
Unit
None

BTS3203E
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
L.Sps.UL.TB.Intvl40ms.Err Multi-mode: None

GSM: None
UMTS: None
Scheduling
L.Sps.UL.ErrNum.Ptt Multi-mode: None

GSM: None
UMTS: None
L.Sps.DL.ErrNum.Ptt Multi-mode: None

GSM: None
UMTS: None
L.Sps.DL.TB.Intvl40ms.Err Multi-mode: None

GSM: None
UMTS: None
Scheduling

BTS3203E
1.9.15 Number of Times UEs in Connected Mode Enter DRX for

UEs in RRC_CONNECTED Mode
Counters
1526728547 L.Cdrx.Enter.N Number of BTS3203E LTE L

um times a UE in
connected mode
enters DRX in
RRC_CONECT
ED mode
1526745956 L.Cdrx.UeDiff Number of UE- BTS3203E LTE L

Config.Num specific DRX
reconfiguration
times
Description
The counters measure the number of times UEs enter DRX for UEs in RRC_CONNECTED
mode and number of UE-specific DRX reconfiguration times (excluding DRX for UEs in the
out-of-synchronization state).
V10.4.0.
Measurement Points
The L.Cdrx.Enter.Num counter is incremented by 1 each time the eNodeB sends an RRC
Connection Reconfiguration message to a UE in RRC_CONNECTED mode, instructing the
UE to enter DRX for UEs in RRC_CONNECTED mode (excluding DRX for UEs in the out-
of-synchronization state). In addition, if the DRX parameters come from the UeDiffConfig
MO, the L.Cdrx.UeDiffConfig.Num counter is incremented by 1.
Formula
None
Unit
None

BTS3203E
Related Features
L.Cdrx.Enter.Num Multi-mode: None

GSM: None
UMTS: None
L.Cdrx.UeDiffConfig.Num Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-081103 Terminal Awareness
Differentiation
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 BTS3203E LTE L

m times a UE in
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.
Formula
None

BTS3203E
Unit
None
Related Features
L.Cdrx.Exit.Num Multi-mode: None

GSM: None
UMTS: None
1.9.17 DRX Duration

Counters
1526728549 L.Cdrx.Active. Total number of BTS3203E LTE L

TtiNum TTIs for DRX
UEs in active
state
1526728550 L.Cdrx.Sleep.Tt Total number of BTS3203E LTE L

iNum TTIs for DRX
UEs in sleep
state
1526728551 L.Voip.Cdrx.Ac Total number of BTS3203E LTE L

tive.TtiNum TTIs for DRX
UEs in active
state and
performing
VoIP services
1526728552 L.Voip.Cdrx.Sle Total number of BTS3203E LTE L

ep.TtiNum TTIs for DRX
UEs in dormant
state and
performing
VoIP services
Description
The counters measure the numbers of transmission time intervals (TTIs) for the following
UEs:

BTS3203E
- 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.
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.Cdrx.Active.TtiNum Multi-mode: None

GSM: None
UMTS: None
LBFD-002017 DRX
L.Cdrx.Sleep.TtiNum Multi-mode: None

GSM: None
UMTS: None
LBFD-002017 DRX
L.Voip.Cdrx.Active.TtiNum Multi-mode: None

GSM: None
UMTS: None
LBFD-002017 DRX

BTS3203E
L.Voip.Cdrx.Sleep.TtiNum Multi-mode: None

GSM: None
UMTS: None
LBFD-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 BTS3203E LTE L

tiBundling.Ente messages sent
r for instructing
UEs to enter
TTI bundling
mode
1526728912 L.Signal.Num.T Number of BTS3203E LTE L

tiBundling.Exit messages sent
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.
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
trig intra cell handover 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 trig
intra cell handover sends an RRC Connection Reconfiguration message to the UE with the
ttiBundling IE set to FALSE.

BTS3203E
Formula
None
Unit
None
Related Features
L.Signal.Num.TtiBundling. Multi-mode: None

Enter GSM: None
UMTS: None
LTE: LOFD-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 BTS3203E LTE L

IB1.ETWS ETWS-induced
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.

BTS3203E
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
LBFD-002009 Warning System (ETWS)
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
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 receiving an ETWS-induced WRITE-REPLACE
WARNING REQUEST message sent by the MME, the eNodeB checks the message. If the

BTS3203E
message has already been sent in the current ETWS period, or fails the integrity check, or the
notification area indicated by the message is out of the eNodeB coverage area, the eNodeB
discards the message without processing it. This counter is incremented by 1 each time the
eNodeB processes a WRITE-REPLACE WARNING REQUEST message.
Figure 1-110
Formula
None
Unit
None
Related Features
L.Signal.Num.WRWR.ETW Multi-mode: None

S GSM: None
UMTS: None
Warning System (ETWS)

BTS3203E
1.9.21 Number of Packets of Non-GBR Bearers Discarded by

AQM
Counters
1526729471 L.AQM.Packet Number of BTS3203E LTE L

DropNum.QCI. packets
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.L.AQM.PacketDropNum.QCI.
6,L.AQM.PacketDropNum.QCI.7,L.AQM.PacketDropNum.QCI.8 and
L.AQM.PacketDropNum.QCI.9 counters apply to only LTE FDD.
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

BTS3203E
Unit
None
Related Features
L.AQM.PacketDropNum.Q Multi-mode: None

CI.6 GSM: None
UMTS: None
LTE: LBFD-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 BTS3203E LTE L

rigger.Num times that
dynamic AC
Barring is
triggered

BTS3203E
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
Control
1.9.23 Number of Times That Dynamic AC Barring Is Cancelled
Counters
1526729500 L.Dyn.ACBar.C Number of BTS3203E LTE L

ancel.Num times that
dynamic AC
Barring is
cancelled
Description
The counter measures the number of times that dynamic AC Barring is cancelled in a cell.

BTS3203E
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 BTS3203E LTE L

Adjust.Num times that
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.

BTS3203E
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 BTS3203E LTE L

ontrol.Dur duration of
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

BTS3203E
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
DMA.High TDSCDMA
network is
configured as
the highest
frequency
priority in an
IMMCI IE

DedicatedPri.T times that the
DSCDMA.High TDSCDMA
network is
configured as
the highest
frequency
priority in an
IMMCI IE
Triggered
Because of
High Load

BTS3203E
Description
Number of times that the TDSCDMA network is configured as the highest frequency priority
in an IMMCI IE
Measurement Points
As shown at point A in Figure 1-111, 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-111
Formula
None
Unit
None
Related Features
None

BTS3203E
1.9.27 Number of S1 Signaling Messages Received or Sent by a

Cell
Counters
1526729659 L.Signal.Num.S Number of S1 BTS3203E LTE L

1 signaling
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

BTS3203E
1.9.28 Number of X2 Signaling Messages Received or Sent by a

Cell
Counters
1526729660 L.Signal.Num. Number of X2 BTS3203E LTE L

X2 signaling
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

BTS3203E
1.9.29 Distribution of Out-of-Synchronization Durations for UEs

in a Cell
Counters
1526730104 L.User.UL.Uns Number of BTS3203E LTE L

ync.Dur.Index0 times the
duration of a
UE in the out-
of-
synchronization
state in a cell
ranges from 0s
to 10s
(excluding 0s
and including
10s)

duration of a
UE in the out-
of-
synchronization
state in a cell
ranges from 10s
to 20s
(excluding 10s
and including
20s)

duration of a
UE in the out-
of-
synchronization
state in a cell
ranges from 20s
to 30s
(excluding 20s
and including
30s)

BTS3203E


duration of a
UE in the out-
of-
synchronization
state in a cell
ranges from 30s
to 40s
(excluding 30s
and including
40s)

duration of a
UE in the out-
of-
synchronization
state in a cell
ranges from 40s
to 50s
(excluding 40s
and including
50s)

duration of a
UE in the out-
of-
synchronization
state in a cell
ranges from 50s
to 60s
(excluding 50s
and including
60s)

BTS3203E


duration of a
UE in the out-
of-
synchronization
state in a cell
ranges from 60s
to 120s
(excluding 60s
and including
120s)

duration of a
UE in the out-
of-
synchronization
in a cell state
ranges from
120s to 200s
(excluding 120s
and including
200s)

duration of a
UE in the out-
of-
synchronization
state in a cell is
greater than
200s
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.
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.

BTS3203E
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

BTS3203E

x7 GSM: None
UMTS: None

x8 GSM: None
UMTS: None
1.9.30 Number of Times the eNodeB Delivers the Load-Triggered

Inter-Frequency Measurement Configuration to a UE
Counters
1526730526 L.InterFreq.Loa Number of BTS3203E LTE L

d.Meas.Num.Ce times the
ll eNodeB
delivers the
load-triggered
inter-frequency
measurement
configuration to
a UE
Description
The counter measures the number of times the eNodeB delivers the load-triggered inter-
frequency measurement configuration to a UE in a cell.
Measurement Points
As shown at point A in Figure 1-112, the L.InterFreq.Load.Meas.Num.Cell counter is
incremented by 1 each time the eNodeB sends an RRC Connection Reconfiguration message
carrying the MeasConfig IE to a UE because of load balancing and measIdToAddModList in
the MeasConfig IE contains measIDs that are intended for neighboring frequencies, regardless
of the number of measIDs.

BTS3203E
Figure 1-112
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
Load Balancing

BTS3203E
1.9.31 Number of Times the Load-Triggered Inter-Frequency

Measurement is Successful
Counters
1526730527 L.InterFreq.Loa Number of BTS3203E LTE L

d.MeasSucc.Nu times the load-
m.Cell triggered inter-
frequency
measurement is
successful
Description
The counter measures the number of times the load-triggered inter-frequency measurement is
successful in a cell.
Measurement Points
As shown at point B in Figure 1-113, 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-113

BTS3203E
Formula
None
Unit
None
Related Features
L.InterFreq.Load.MeasSucc. Multi-mode: None

Num.Cell GSM: None
UMTS: None
Load Balancing
1.9.32 Duration in Which a Cell with Inter-Frequency Load

Balancing Enabled Is in the High-Load State
Counters
1526730528 L.InterFreq.Hig Duration in BTS3203E LTE L

hLoad.Dur.Cell which a cell
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. 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.

BTS3203E
Formula
None
Unit
s
Related Features
L.InterFreq.HighLoad.Dur.C Multi-mode: None

ell GSM: None
UMTS: None
Load Balancing
1.9.33 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 BTS3203E LTE L

hLoad.Num.Cel times a cell
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.

BTS3203E
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.34 Number of times that a cell is unavailable
Counters
1526732089 L.Cell.Unavail. Number of BTS3203E LTE L

Num times that a cell
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.

BTS3203E
Formula
None
Unit
None
Related Features
L.Cell.Unavail.Num Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001025 Adaptive Power
LOFD-001042 Consumption
Intelligent Power-Off of
Carriers in the Same
Coverage
1.9.35 Uplink or Downlink Voice Quality of AMR-WB Services
Counters
1526732687 L.Voice.VQI.A Number of BTS3203E LTE L

MRWB.UL.Exc times uplink
ellent.Times voice quality of
AMR-WB
services is
Excellent

MRWB.UL.Go times uplink
od.Times voice quality of
AMR-WB
services is
Good

MRWB.UL.Ac times uplink
cept.Times voice quality of
AMR-WB
services is
Accept

BTS3203E


MRWB.UL.Poo times uplink
r.Times voice quality of
AMR-WB
services is Poor

MRWB.UL.Ba times uplink
d.Times voice quality of
AMR-WB
services is Bad

MRWB.DL.Exc times downlink
ellent.Times voice quality of
AMR-WB
services is
Excellent

MRWB.DL.Go times downlink
od.Times voice quality of
AMR-WB
services is
Good

MRWB.DL.Ac times downlink
cept.Times voice quality of
AMR-WB
services is
Accept

MRWB.DL.Poo times downlink
r.Times voice quality of
AMR-WB
services is Poor

MRWB.DL.Ba times downlink
d.Times voice quality of
AMR-WB
services is Bad
Description
The counters measure the uplink or downlink voice quality of AMR-WB speech services in a
cell when the VQMAlgoSwitch parameter in the ENodeBAlgoSwitch MO is set to
VQM_ALGO_SWITCH_AMR_ON or VQM_ALGO_SWITCH_ADAPTIVE_ON.

BTS3203E
Measurement Points
uplink and downlink VQIs of VoLTE UEs running AMR-WB services are calculated. The
corresponding counter is incremented by 1 each time the E2E VQI of a VoLTE UE running an
AMR-WB service is at a specified speech quality level. The speech quality can be classified
into five levels: Bad, Poor, Accept, Good, and Excellent.
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

BTS3203E
L.Voice.VQI.AMRWB.DL. Multi-mode: None

UMTS: None

UMTS: None

UMTS: None

UMTS: None

Bad.Times GSM: None
UMTS: None
1.9.36 Number of Normal Voice Call Releases in the Cell
Counters
1526732890 L.Voice.NormR Number of BTS3203E LTE L

el.UL.LowQual normal voice
ity call releases in
the cell (poor
uplink voice
quality)
1526732891 L.Voice.NormR Number of BTS3203E LTE L

el.DL.LowQual normal voice
ity call releases in
the cell (poor
downlink voice
quality)

BTS3203E
Description
The counters measure the number of times uplink or downlink voice quality of AMR speech
services is poor in a cell when the VQMAlgoSwitch parameter in the ENodeBAlgoSwitch
MO is set to VQM_ALGO_SWITCH_AMR_ON.
The counters measure the number of times uplink or downlink voice quality of AMR and
EVS speech services is poor in a cell when the VQMAlgoSwitch parameter in the
ENodeBAlgoSwitch MO is set to VQM_ALGO_SWITCH_ADAPTIVE_ON.
Measurement Points
When the VQMAlgoSwitch parameter in the ENodeBAlgoSwitch MO is set to
VQM_ALGO_SWITCH_AMR_ON, the eNodeB measures VoLTE UEs performing AMR
speech services in a cell.
VQM_ALGO_SWITCH_ADAPTIVE_ON, the eNodeB measures VoLTE UEs performing
AMR speech services and UEs performing EVS speech services in a cell.
The corresponding counter is incremented by 1 for a VoLTE UE if either of the following
conditions in the corresponding transmission direction for the UE is met for
AmrLowQualRelPeriodNum consecutive periods defined by VQMAlgoPeriod before the UE
is normally released. Each UE is counted only once.
1. Packet loss rate > AmrNbRadioLowQualRelThd (AMR-NB) or
AmrWbRadioLowQualRelThd (AMR-WB)
2 (Theoretical total number of packets - Number of packets received by the eNodeB)/
Theoretical total number of packets > AmrNbRcvLowQualRelThd (AMR-NB) or
AmrWbRcvLowQualRelThd (AMR-WB)
If multiple UEs meet either of the conditions simultaneously, the counter is incremented by
the number of UEs.
The AMR-NB threshold of the packet loss rate over the Uu interface is used for VoLTE UEs
performing AMR-NB speech services. The AMR-WB threshold of the packet loss rate over
the Uu interface is used for VoLTE UEs performing AMR-WB or EVS speech services.
Formula
None
Unit
None

BTS3203E
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.37 Number of Times that a UE Experiences Voice Mute in the

Cell
Counters
1526732892 L.Voice.UL.Sile Number of BTS3203E LTE L

nt.Num times that a UE
experiences
uplink voice
mute in the cell
1526732893 L.Voice.DL.Sile Number of BTS3203E LTE L

nt.Num times that a UE
experiences
downlink voice
mute in the cell
Description
The counters measure the number of times UEs performing AMR speech services experience
an uplink or downlink voice mute in a cell when the VQMAlgoSwitch parameter in the
ENodeBAlgoSwitch MO is set to VQM_ALGO_SWITCH_AMR_ON.
The counters measure the number of times UEs performing AMR speech services and UEs
performing EVS speech services experience an uplink or downlink voice mute in a cell when
the VQMAlgoSwitch parameter in the ENodeBAlgoSwitch MO is set to
VQM_ALGO_SWITCH_ADAPTIVE_ON.

BTS3203E
Measurement Points
VQM_ALGO_SWITCH_AMR_ON, the eNodeB measures VoLTE UEs performing AMR
speech services in a cell.

VQM_ALGO_SWITCH_ADAPTIVE_ON, the eNodeB measures VoLTE UEs performing
AMR speech services and UEs performing EVS speech services in a cell.
The corresponding counter is incremented by 1 for a VoLTE UE if either of the following

conditions in the corresponding transmission direction for the UE is met for
AmrSilentPeriodNum consecutive periods defined by VQMAlgoPeriod. In this case, the UE
experiences a voice mute. Each UE is counted only once.
1. Packet loss rate > AmrNbSilentThd (AMR-NB) or AmrWbSilentThd (AMR-WB)
2 (Theoretical total number of packets - Number of packets received by the eNodeB)/

Theoretical total number of packets > AmrNbSilentThd (AMR-NB) or AmrWbSilentThd
(AMR-WB)
If multiple UEs meet either of the conditions simultaneously, the counter is incremented by
the number of UEs. The AMR-NB threshold of the packet loss rate over the Uu interface is
used for VoLTE UEs performing AMR-NB speech services. The AMR-WB threshold of the
packet loss rate over the Uu interface is used for VoLTE UEs performing AMR-WB or EVS
speech services.
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

BTS3203E
1.9.38 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 BTS3203E LTE L

odeB.HoMeas. times that an
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-114, 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.

BTS3203E
Figure 1-114
Formula
None
Unit
None
Related Features
None

BTS3203E
1.9.39 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
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-115, 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.

BTS3203E
Figure 1-115
Formula
None
Unit
None
Related Features
None

BTS3203E
1.9.40 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
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-116, 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.

BTS3203E
Figure 1-116
Formula
None
Unit
None
Related Features
None

BTS3203E
1.9.41 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
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-117, 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.

BTS3203E
Figure 1-117
Formula
None
Unit
None
Related Features
None
1.9.42 Number of cell received configuration message from centre

controller but receive time was expired
Counters
1526733010 L.Sig.PowerCfg Number of cell BTS3203E LTE L

.Fail.TimeOut received
configuration
message from
centre
controller but
receive time
was expired

BTS3203E
Description
The counter measures the number of cell received configuration message from centre
controller but receive time was expired
Measurement Points
None
Formula
None
Unit
None
Related Features
None
1.9.43 Number of cell received configuration message from centre

controller
Counters
1526733011 L.Sig.PowerCfg Number of cell BTS3203E LTE L

.Att received
configuration
message from
centre
controller
Description
The counter measures the number of cell received configuration message from centre
controller
Measurement Points
None
Formula
None

BTS3203E
Unit
None
Related Features
None
1.9.44 Number of Downlink Subframes Without Power on the

Power Spectrun of a Cell
Counters
1526735577 L.PowerNull.D Number of BTS3203E LTE L

L.TTI.Num downlink
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
None

BTS3203E
1.9.45 Number of Times Dynamic SSAC Is Triggered

Counters
1526736656 L.SSAC.Dyn.A Number of BTS3203E LTE L

CBar.Trigger.N times dynamic
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: LOFD-008002 Dynamic Service-specific
Access Control

BTS3203E
1.9.46 Number of Times Parameters Related to Dynamic SSAC are

Adjusted
Counters

CBar.Adjust.Nu times
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
Access Control

BTS3203E
1.9.47 Number of Times Dynamic SSAC Is Canceled

Counters

CBar.Cancel.N times dynamic
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
Access Control

BTS3203E
1.9.48 Duration of Dynamic SSAC

Counters
1526736659 L.SSAC.Dyn.A Duration of BTS3203E LTE L

CBar.Control.D dynamic SSAC
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
Access Control

BTS3203E
1.9.49 Number of Times Preemptions Are Triggered by the User

Number Specification.
Counters
1526736866 L.Cell.UserSpe Number of BTS3203E LTE L

c.PrepEmp.Prep times
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-118, 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-118

BTS3203E
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.50 Number of Times the Licensed Number of UEs Is Limited

Counters
1526736869 L.Cell.UserLic. Number of BTS3203E LTE L

Limit.Num times the
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-119, 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.

BTS3203E
Figure 1-119
Formula
None
Unit
None
Related Features
L.Cell.UserLic.Limit.Num Multi-mode: None

GSM: None
UMTS: None
pre-emption

BTS3203E
1.9.51 Number of Successful Preemptions Triggered by the

Limitation of the Licensed Number of Ues
Counters
1526736870 L.Cell.UserLic. Number of BTS3203E LTE L

PrepEmp.Succ. successful
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-120, 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.

BTS3203E
Figure 1-120
Formula
None
Unit
None
Related Features
L.Cell.UserLic.PrepEmp.Su Multi-mode: None

cc.Num GSM: None
UMTS: None
pre-emption

BTS3203E
1.9.52 Number of Times IRC, MRC, or Smart IRC Is Used on the

PUSCH
Counters
1526736889 L.ULIRC.PUS Number of BTS3203E LTE L

CH.MRC.Num times MRC is
used on the
PUSCH

CH.IRC.Num times IRC is
used on the
PUSCH

CH.SmartIRC. times smart
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).

BTS3203E
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
Combining
L.ULIRC.PUSCH.IRC.Num Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001012 UL Interference Rejection
Combining
1.9.53 Number of Times IRC or MRC Is Used on the PUCCH
Counters
1526736891 L.CtrlIRC.PUC Number of BTS3203E LTE L

used on the
PUCCH
1526736892 L.CtrlIRC.PUC Number of BTS3203E LTE L

used on the
PUCCH

BTS3203E
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

BTS3203E
L.CtrlIRC.PUCCH.IRC.Nu Multi-mode: None

m GSM: None
UMTS: None
1.9.54 Number of Times IRC or MRC Is Used on the PRACH
Counters
1526736893 L.CtrlIRC.PRA Number of BTS3203E LTE L

used on the
PRACH
1526736894 L.CtrlIRC.PRA Number of BTS3203E LTE 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.

BTS3203E
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.55 Number of SPID-based Target PLMN Selection Attempts

Counters
1526737821 L.SPID.SelectT Number of BTS3203E LTE L

gtPLMN.AttOu SPID-based
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-121, the L.SPID.SelectTgtPLMN.AttOut counter is
incremented by 1 each time the eNodeB determines to perform a blind intra-eNodeB

BTS3203E
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-121

BTS3203E
Figure 1-122
Figure 1-123

BTS3203E
Figure 1-124
Figure 1-125
Formula
None
Unit
None

BTS3203E
Related Features
L.SPID.SelectTgtPLMN.Att Multi-mode: None

Out GSM: None
UMTS: None
SPID
1.9.56 Number of times the eCoordinator triggers interference

coordination in high-speed railway scenarios
Counters
1526737856 L.InterfHighSp Number of BTS3203E LTE L

eed.Trigger.Nu times the
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

BTS3203E
Related Features
None
1.9.57 Number of times the eCoordinator stops interference

coordination in high-speed railway scenarios
Counters
1526737857 L.InterfHighSp Number of BTS3203E LTE L

eed.Cancel.Nu times the
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
None

BTS3203E
1.9.58 Number of successful preferential accesses performed by

voice service UEs
Counters
1526739725 L.VoiceUser.Vo Number of BTS3203E LTE L

IPPref.Succ successful
preferential
accesses
performed by
voice service
UEs
Description
The counters measure the number of times that voice service UEs successfully perform
preferential access in a cell using reserved resources. The signaling procedures related to
these counters comply with sections 5.3.3 and 5.3.7 in 3GPP TS 36.331 (V10.4.0) and section
10.1.2 in 3GPP TS 36.300 (V10.6.0).
Measurement Points
As shown at Point B in Figure 1-126, the L.VoiceUser.VoIPPref.Succ counter is incremented
by 1 each time the eNodeB sends the MME an E-RAB SETUP RESPONSE message which
contains the information indicating that the E-RAB with QCI 1 is successfully established and
the UE accesses the network using resources reserved for voice service UEs.
As shown in point C in Figure 1-127, the L.VoiceUser.VoIPPref.Succ counter is incremented
by 1 each time the cell receives an RRC Connection Reconfiguration Complete message
which contains the information indicating that the voice bearer with QCI 1 is successfully
established and the RRC connection of the UE is reestablished using resources reserved for
voice services.
As shown at point C in Figure 1-128 and Figure 1-129, the L.VoiceUser.VoIPPref.Succ
counter is incremented by 1 each time the eNodeB determines that the UE is handed over to
the target cell using resources reserved for voice service UEs and the voice bearer with QCI 1
is successfully established.

BTS3203E
Figure 1-126
Figure 1-127

BTS3203E
Figure 1-128
Figure 1-129
Formula
None
Unit
None

BTS3203E
Related Features
None
1.9.59 Number of ABSs in a Cell with eICIC Enabled
Counters
1526739752 L.Cell.eICIC.A Number of BTS3203E LTE L

BS.Num ABSs in a cell
with eICIC
enabled
Description
The counter measures the number of ABSs in a macro cell or the number of protected
subframes in a micro cell. The counter value can be used to evaluate whether eICIC takes
effect.
This counter applies only to LTE FDD.
Measurement Points
For a macro cell with TDM eICIC enabled, the counter value is incremented by 1 each time
an ABS appears within a measurement period. For a micro cell with TDM eICIC enabled, the
counter value is incremented by 1 each time a protect ed subframe appears.
The internal timer of the eNodeB has a deviation of one period, and therefore the value of the
counter has a deviation to the actual number.
Formula
None
Unit
None
Related Features
L.Cell.eICIC.ABS.Num Multi-mode: None

GSM: None
UMTS: None
LTE: LAOFD-081233 Dynamic TDM eICIC
LAOFD-081234 FeICIC

BTS3203E
1.9.60 Number of Uplink PDCP SDUs of QCI 1 Discarded

Because of SN Disorder or Changes in a Cell
Counters
1526739788 L.Traffic.UL.Pk Number of BTS3203E LTE L

tDisorderLoss.L uplink PDCP
oss.QCI.1 SDUs of QCI 1
discarded
because of SN
disorder or
changes in a
cell
Description
The counter measures the number of uplink PDCP SDUs of QCI 1 discarded because of
PDCP SN disorder of changes in a cell.
Measurement Points
The number of uplink PDCP SDUs of QCI 1 discarded because of PDCP SN changes or
disorder is sampled per second in a cell. At the end of a measurement period, the sum of these
sampling results is taken as the value of the L.Traffic.UL.PktDisorderLoss.Loss.QCI.1
counter.
Formula
None
Unit
None
Related Features
L.Traffic.UL.PktDisorderLo Multi-mode: None

ss.Loss.QCI.1 GSM: None
UMTS: None
LBFD-002025 Basic Scheduling

BTS3203E
1.9.61 UDC Service Throughput or Throughput Rate

Measurement
Counters
1526739807 L.Thrp.bits.UL. Total BTS3203E LTE L

PDCP.SDU.UD throughput of
C.BefDecompn uplink SDUs
before the
decompression
of UDC
services at the
PDCP layer

PDCP.SDU.UD throughput of
C.AftDecompn uplink SDUs
after the
decompression
of UDC
services at the
PDCP layer

PDCP.SDU.Bef throughput of
UdcDecompn uplink SDUs
before the
decompression
of UDC
services at the
PDCP layer
Description
This counter measures the total throughput of uplink SDUs of the UDC services at the PDCP
layer. UDC is short for uplink data compression, which improves uplink throughput.
Measurement Points
If the UdcAlgoSwitch parameter in the CellAlgoSwitch MO is set to ON(On) and packets are
successfully decompressed, the L.Thrp.bits.UL.PDCP.SDU.UDC.BefDecomp counter
measures the number of bits in PDCP packets received over all UDC bearers before the
decompression, and the L.Thrp.bits.UL.PDCP.SDU.UDC.AftDecompn counter measures the
number of bits in PDCP packets received over these bearers after the decompression.
If the UdcAlgoSwitch parameter in the CellAlgoSwitch MO is set to ON(On), the
L.Thrp.bits.UL.PDCP.SDU.BefUdcDecompn counter measures the number of bits in PDCP

BTS3203E
packets (including the bits in packets fail to be decompressed) received over all UDC bearers
before the decompression.
Formula
None
Unit
bit
Related Features
None
1.9.62 Average Number of DRBs for UDC Services
Counters
1526739808 L.Traffic.DRB. Average BTS3203E LTE L

Avg.UDC number of
DRBs for UDC
services in a
cell
Description
This counter measures the number of DRBs for UDC services. UDC is short for uplink data
compression, which improves uplink throughput.
Measurement Points
The number of DRBs of UDC services in a cell is measured per second. At the end of a
measurement period, the average of these measurement results is used as the value of the
counter.
Formula
None
Unit
None
Related Features
None

BTS3203E
1.9.63 E2E VQI Distribution at Different Speech Quality Levels

Counters
1526741669 L.Voice.E2EV Number of BTS3203E LTE L

QI.Excellent.Ti times E2E
mes VQIs are
Excellent

QI.Good.Times times E2E
VQIs are Good

QI.Accept.Time times E2E
s VQIs are
Accept

QI.Poor.Times times E2E
VQIs are Poor

QI.Bad.Times times E2E
VQIs are Bad
Description
The counters measure the number of times end-to-end (E2E) voice quality indicators (VQIs)
of AMR-WB speech services and E2E VQIs of AMR-NB speech services are Excellent,
Good, Accept, Poor, or Bad in a cell when the VQMAlgoSwitch parameter in the
ENodeBAlgoSwitch MO is set to VQM_ALGO_SWITCH_AMR_ON or
VQM_ALGO_SWITCH_ADAPTIVE_ON and the E2EVQIAlgoSwitch parameter in the
same MO is set to ON. The E2E VQI represents the E2E voice quality calculated by the
network. The mapping between VQIs and voice quality levels is as follows:
[500, VQMAlgo.VqiExcellentThd) = Excellent
[VQMAlgo.VqiExcellentThd, VQMAlgo.VqiGoodThd) = Good
[VQMAlgo.VqiGoodThd, VQMAlgo.VqiPoorThd) = Accept
[VQMAlgo.VqiPoorThd, VQMAlgo.VqiBadThd) = Poor
[VQMAlgo.VqiBadThd, 0) = Bad
Measurement Points
E2E VQIs of VoLTE UEs running AMR-WB services and AMR-NB services are calculated.
The corresponding counter is incremented by 1 each time the E2E VQI of a VoLTE UE

BTS3203E
running an AMR-WB service is at a specified speech quality level. The speech quality can be
classified into five levels: Bad, Poor, Accept, Good, and Excellent.
Formula
None
Unit
None
Related Features
L.Voice.E2EVQI.Excellent. Multi-mode: None

Times GSM: None
UMTS: None
L.Voice.E2EVQI.Good.Tim Multi-mode: None

es GSM: None
UMTS: None
L.Voice.E2EVQI.Accept.Ti Multi-mode: None

mes GSM: None
UMTS: None
L.Voice.E2EVQI.Poor.Time Multi-mode: None

s GSM: None
UMTS: None
L.Voice.E2EVQI.Bad.Times Multi-mode: None

GSM: None
UMTS: None

BTS3203E
1.9.64 E2E VQI Distribution of AMR-WB Services at Different

Speech Quality Levels
Counters

QI.AMRWB.Ex times E2E
cellent.Times VQIs of AMR-
WB services
are Excellent

QI.AMRWB.G times E2E
ood.Times VQIs of AMR-
WB services
are Good

QI.AMRWB.A times E2E
ccept.Times VQIs of AMR-
WB services
are Accept

QI.AMRWB.Po times E2E
or.Times VQIs of AMR-
WB services
are Poor

QI.AMRWB.Ba times E2E
d.Times VQIs of AMR-
WB services
are Bad
Description
The counters measure the number of times end-to-end (E2E) voice quality indicators (VQIs)
of AMR-WB speech services are Excellent, Good, Accept, Poor, or Bad in a cell when the
VQMAlgoSwitch parameter in the ENodeBAlgoSwitch MO is set to
VQM_ALGO_SWITCH_AMR_ON or VQM_ALGO_SWITCH_ADAPTIVE_ON and the
E2EVQIAlgoSwitch parameter in the same MO is set to ON. The E2E VQI represents the
E2E voice quality calculated by the network. The mapping between VQIs and voice quality
levels is as follows:
[500, VQMAlgo.VqiExcellentThd) = Excellent
[VQMAlgo.VqiExcellentThd, VQMAlgo.VqiGoodThd) = Good
[VQMAlgo.VqiGoodThd, VQMAlgo.VqiPoorThd) = Accept

BTS3203E
[VQMAlgo.VqiPoorThd, VQMAlgo.VqiBadThd) = Poor
[VQMAlgo.VqiBadThd, 0) = Bad
Measurement Points
E2E VQIs of VoLTE UEs running AMR-WB services are calculated. The corresponding
counter is incremented by 1 each time the E2E VQI of a VoLTE UE running an AMR-WB
service is at a specified speech quality level. The speech quality can be classified into five
levels: Bad, Poor, Accept, Good, and Excellent.
Formula
None
Unit
None
Related Features
L.Voice.E2EVQI.AMRWB. Multi-mode: None

UMTS: None

UMTS: None

UMTS: None

UMTS: None

Bad.Times GSM: None
UMTS: None

BTS3203E
1.9.65 Total Value of E2E VQIs
Counters
1526741679 L.Voice.E2EV Total value of BTS3203E LTE L

QI.TotalValue E2E VQIs
Description
The counters measure the total value of end to end (E2E) voice quality indicators (VQIs) of
AMR-WB and AMR-NB speech services in a cell when the VQMAlgoSwitch parameter in
the ENodeBAlgoSwitch MO is set to VQM_ALGO_SWITCH_AMR_ON or
network. The average E2E VQI of AMR-WB and AMR-NB speech services in a cell can be
calculated by using the following formula:
E2E VQI (Average) = L.Voice.E2EVQI.TotalValue/[(L.Voice.E2EVQI.Excellent.Times +

L.Voice.E2EVQI.Good.Times + L.Voice.E2EVQI.Accept.Times +
L.Voice.E2EVQI.Poor.Times + L.Voice.E2EVQI.Bad.Times) x 100]
Measurement Points
The E2E VQIs of VoLTE UEs running AMR-WB and AMR-NB services in a cell are
sampled in each voice quality monitoring (VQM) period specified by
VQMALGO.VQMAlgoPeriod. At the end of a measurement period, the E2E VQIs of VoLTE
UEs running AMR-WB and AMR-NB services are accumulated and taken as the
L.Voice.E2EVQI.TotalValue counter value.
Formula
None
Unit
None
Related Features
L.Voice.E2EVQI.TotalValue Multi-mode: None

GSM: None
UMTS: None

BTS3203E
1.9.66 Total Value of E2E VQIs of AMR-WB Services

Counters
1526741680 L.Voice.E2EV Total value of BTS3203E LTE L

QI.AMRWB.To E2E VQIs of
talValue AMR-WB
services
Description
The counters measure the total value of end to end (E2E) voice quality indicators (VQIs) of
AMR-WB speech services in a cell when the VQMAlgoSwitch parameter in the
network. The average E2E VQI of AMR-WB speech services in a cell can be calculated by
using the following formula:
AMR-WB E2E VQI (Average) = L.Voice.E2EVQI.AMRWB.TotalValue/
[(L.Voice.E2EVQI.AMRWB.Excellent.Times + L.Voice.E2EVQI.AMRWB.Good.Times +
L.Voice.E2EVQI.AMRWB.Accept.Times + L.Voice.E2EVQI.AMRWB.Poor.Times +
L.Voice.E2EVQI.AMRWB.Bad.Times) x 100]
Measurement Points
The E2E VQIs of VoLTE UEs running AMR-WB services in a cell are sampled in each voice
quality monitoring (VQM) period specified by VQMALGO.VQMAlgoPeriod. At the end of a
measurement period, the E2E VQIs of VoLTE UEs running AMR-WB services are
accumulated and taken as the L.Voice.E2EVQI.AMRWB.TotalValue counter value.
Formula
None
Unit
None

BTS3203E
Related Features

TotalValue GSM: None
UMTS: None
1.9.67 Total Value of Uplink or Downlink VQIs

Counters
1526741681 L.Voice.VQI.U Total value of BTS3203E LTE L

L.TotalValue uplink VQIs
1526741682 L.Voice.VQI.D Total value of BTS3203E LTE L

L.TotalValue downlink VQIs
Description
The counters measure the total value of uplink or downlink voice quality indicators (VQIs) of
AMR-WB and AMR-NB speech services in a cell when the VQMAlgoSwitch parameter in
the ENodeBAlgoSwitch MO is set to VQM_ALGO_SWITCH_AMR_ON or
VQM_ALGO_SWITCH_ADAPTIVE_ON. The average uplink and downlink VQI of AMR-
WB and AMR-NB speech services in a cell can be calculated by using the following
formulas:
UL VQI (Average) = L.Voice.VQI.UL.TotalValue/[(L.Voice.VQI.UL.Excellent.Times +
L.Voice.VQI.UL.Good.Times + L.Voice.VQI.UL.Accept.Times +
L.Voice.VQI.UL.Poor.Times + L.Voice.VQI.UL.Bad.Times) x 100]
DL VQI (Average) = L.Voice.VQI.DL.TotalValue/[(L.Voice.VQI.DL.Excellent.Times +
L.Voice.VQI.DL.Good.Times + L.Voice.VQI.DL.Accept.Times +
L.Voice.VQI.DL.Poor.Times + L.Voice.VQI.DL.Bad.Times) x 100]
Measurement Points
The uplink or downlink VQIs of VoLTE UEs running AMR-WB and AMR-NB services in a
cell are sampled in each voice quality monitoring (VQM) period specified by
VQMALGO.VQMAlgoPeriod. At the end of a measurement period, the uplink or downlink
VQIs of VoLTE UEs running AMR-WB and AMR-NB services are accumulated and taken as
the L.Voice.VQI.UL.TotalValue or L.Voice.VQI.DL.TotalValue counter value, respectively.

BTS3203E
Formula
None
Unit
None
Related Features
L.Voice.VQI.UL.TotalValue Multi-mode: None

GSM: None
UMTS: None
L.Voice.VQI.DL.TotalValue Multi-mode: None

GSM: None
UMTS: None
1.9.68 Total Value of Uplink or Downlink VQIs of AMR-WB

Services
Counters
1526741683 L.Voice.VQI.A Total value of BTS3203E LTE L

MRWB.UL.Tot uplink VQIs of
alValue AMR-WB
services
1526741684 L.Voice.VQI.A Total value of BTS3203E LTE L

MRWB.DL.Tot downlink VQIs
alValue of AMR-WB
services
Description
The counters measure the total value of uplink or downlink voice quality indicators (VQIs) of
AMR-WB speech services in a cell when the VQMAlgoSwitch parameter in the
VQM_ALGO_SWITCH_ADAPTIVE_ON. The average uplink and downlink VQIs of AMR-
WB speech services in a cell can be calculated by using the following formulas:

BTS3203E
AMR-WB UL VQI (Average) = L.Voice.VQI.AMRWB.UL.TotalValue/

[(L.Voice.VQI.AMRWB.UL.Excellent.Times + L.Voice.VQI.AMRWB.UL.Good.Times +
L.Voice.VQI.AMRWB.UL.Accept.Times + L.Voice.VQI.AMRWB.UL.Poor.Times +
L.Voice.VQI.AMRWB.UL.Bad.Times) x 100]
DL VQI (Average) = L.Voice.VQI.AMRWB.DL.TotalValue/
[(L.Voice.VQI.AMRWB.DL.Excellent.Times + L.Voice.VQI.AMRWB.DL.Good.Times +
L.Voice.VQI.AMRWB.DL.Accept.Times + L.Voice.VQI.AMRWB.DL.Poor.Times +
L.Voice.VQI.AMRWB.DL.Bad.Times) x 100]
Measurement Points
The uplink or downlink VQIs of VoLTE UEs running AMR-WB services in a cell are
sampled in each voice quality monitoring (VQM) period specified by
VQMALGO.VQMAlgoPeriod. At the end of a measurement period, the uplink or downlink
VQIs of VoLTE UEs running AMR-WB services are accumulated and taken as the
L.Voice.VQI.AMRWB.UL.TotalValue or L.Voice.VQI.AMRWB.DL.TotalValue counter
value.
Formula
None
Unit
None
Related Features

UMTS: None

UMTS: None

BTS3203E
1.9.69 Number of Times CMAS WRITE-REPLACE WARNING

REQUEST Messages Are Received in a Cell
Counters
1526742133 L.Signal.CMAS Number of BTS3203E LTE L

.WRWR.Num times CMAS
WRITE-
REPLACE
WARNING
REQUEST
messages are
received
Description
The counter measures the number of times WRITE-REPLACE WARNING REQUEST
messages are received from the MME for CMAS warning in a cell.
Measurement Points
As shown at point A in Figure 1-130, the counter is incremented by 1 each time the eNodeB
receives a WRITE-REPLACE WARNING REQUEST message from the MME for CMAS
warning. The repeatedly received messages are not involved in the measurement.
Figure 1-130
Formula
None

BTS3203E
Unit
None
Related Features
L.Signal.CMAS.WRWR.Nu Multi-mode: None

m GSM: None
UMTS: None
LTE: LBFD-001092 CMAS Support
1.9.70 Number of Times CMAS Warning Notifications Are

Requested to Be Broadcast in a Cell
Counters

.BroadcastReq. times CMAS
Num warning
notifications are
requested to be
broadcast
Description
The counter measures the total number of times CMAS warning notifications are requested to
be broadcast indicated by the WRITE-REPLACE WARNING REQUEST messages that are
received from the MME for CMAS warning in a cell.
Measurement Points
As shown at point A in Figure 1-131, each time the eNodeB receives a WRITE-REPLACE
WARNING REQUEST message from the MME for CMAS warning, the counter is
incremented by the number of CMAS warning notifications are requested to be broadcast
indicated by the message. The repeatedly received messages are not involved in the
measurement.

BTS3203E
Figure 1-131
Formula
None
Unit
None
Related Features
L.Signal.CMAS.BroadcastR Multi-mode: None

eq.Num GSM: None
UMTS: None

BTS3203E
1.9.71 Number of Times CMAS KILL REQUEST Messages Are

Received in a Cell
Counters

.KillReq.Num times CMAS
KILL
REQUEST
messages are
received
Description
The counter measures the number of times KILL REQUEST messages are received from the
MME for CMAS warning in a cell.
Measurement Points
As shown at point A in Figure 1-132, the counter is incremented by 1 each time the eNodeB
receives a KILL REQUEST message from the MME for CMAS warning. The repeatedly
received messages are not involved in the measurement.
Figure 1-132
Formula
None

BTS3203E
Unit
None
Related Features
L.Signal.CMAS.KillReq.Nu Multi-mode: None

m GSM: None
UMTS: None
1.9.72 Number of Times CMAS WARNING REQUEST messages

Are Successfully Processed in a Cell
Counters

.WRWRProcSu times CMAS
cc.Num WARNING
REQUEST
messages are
successfully
processed
Description
The counter measures the number of times a cell broadcasts the first CMAS warning
notification after receiving WRITE-REPLACE WARNING REQUEST messages from the
MME for CMAS warning.
Measurement Points
As shown at point B in Figure 1-133, the counter is incremented by 1 each time the eNodeB
broadcasts the first CMAS warning notification over the Uu interface after receiving a
WRITE-REPLACE WARNING REQUEST message from the MME for CMAS warning.

BTS3203E
Figure 1-133
Formula
None
Unit
None
Related Features
L.Signal.CMAS.WRWRPro Multi-mode: None

cSucc.Num GSM: None
UMTS: None

BTS3203E
1.9.73 Number of Times CMAS Waring Notifications Are

Successfully Broadcast in a Cell
Counters

.BroadcastSucc. times CMAS
Num warning
notifications are
successfully
broadcast
Description
The counter measures the number of times a cell broadcasts CMAS warning notifications
after receiving WRITE-REPLACE WARNING REQUEST messages from the MME for
CMAS warning.
Measurement Points
As shown at points B and C in Figure 1-134, the counter is incremented by 1 each time the
eNodeB broadcasts a CMAS warning notification over the Uu interface after receiving a
WRITE-REPLACE WARNING REQUEST message from the MME for CMAS warning.
Figure 1-134
Formula
None

BTS3203E
Unit
None
Related Features
L.Signal.CMAS.BroadcastS Multi-mode: None

ucc.Num GSM: None
UMTS: None
1.9.74 Number of Times CMAS KILL REQUEST Messages Are

Successfully Processed in a Cell
Counters

.KillProcSucc. times CMAS
Num KILL
REQUEST
messages are
successfully
processed
Description
The counter measures the number of times a cell stops broadcasting CMAS warning
notifications after receiving KILL REQUEST messages from the MME for CMAS warning.
Measurement Points
As shown at point B in Figure 1-135, the counter is incremented by 1 each time the eNodeB
stops broadcasting CMAS warning notifications after receiving a KILL REQUEST message
from the MME for CMAS warning.

BTS3203E
Figure 1-135
Formula
None
Unit
None
Related Features
L.Signal.CMAS.KillProcSu Multi-mode: None

cc.Num GSM: None
UMTS: None

BTS3203E
1.9.75 Number of Successful Responses to UEs' Requests for

Configuring DRX Parameters in a Cell
Counters
1526742154 L.UE.Req.Drx. Number of BTS3203E LTE L

Reconfig.Succ. successful
Num responses to
UEs' requests
for configuring
DRX
parameters in a
cell
Description
The counter measures the number of times the eNodeB accepts UEs' requests and sends RRC
Connection Reconfiguration messages to reconfigure DRX parameters of the UEs after
receiving CDRX Request messages from the UEs in a cell. A UE sends a CDRX Request
message to the eNodeB to request DRX parameters specified by the UE.
Measurement Points
As shown at point A in Figure 1-136, the L.UE.Req.Drx.Reconfig.Succ.Num counter is
with DRX parameters to a UE after receiving a CDRX Request message from the UE.
Figure 1-136

BTS3203E
Formula
None
Unit
None
Related Features
L.UE.Req.Drx.Reconfig.Suc Multi-mode: None

c.Num GSM: None
UMTS: None
LTE: LAOFD-111208 Smartphone App-Aware
Coordinated Control
1.9.76 Number of Successful Responses to UEs' Requests for

Restoring DRX Parameters in a Cell
Counters
1526742155 L.UE.Req.Defa Number of BTS3203E LTE L

ult.Drx.Succ.Nu successful
m responses to
UEs' requests
for restoring
DRX
parameters in a
cell
Description
The counter measures the number of times the eNodeB accepts UEs' requests and sends RRC
Connection Reconfiguration messages to reconfigure DRX parameters of the UEs after
receiving Default CDRX Request messages from the UEs in a cell. A UE sends a CDRX
Request message to the eNodeB to request DRX parameters specified by the eNodeB.
Measurement Points
As shown at point A in Figure 1-137, the L.UE.Req.Default.Drx.Succ.Num counter is
to restore the DRX parameters to those specified by the eNodeB to a UE after receiving a
Default DRX Request message from the UE.

BTS3203E
Figure 1-137
Formula
None
Unit
None
Related Features
L.UE.Req.Default.Drx.Succ. Multi-mode: None

Num GSM: None
UMTS: None
Coordinated Control

BTS3203E
1.9.77 Number of TTIs in Which Elastic Carrier Takes Effect in a

Cell
Counters
1526742169 L.Cell.ElasticC Number of BTS3203E LTE L

arrierEnableTti. TTIs in which
Num Elastic Carrier
takes effect in a
cell
Description
The counter measures the number of TTIs in which Elastic Carrier takes effect in a cell.
Disuse Statement:
The counter L.Cell.ElasticCarrierEnableTti.Num (ID: 1526742169) will be replaced by the
counter L.Cell.PilotOffTti.Num (ID: 1526743747). In the current version, both counters are
valid and the counter values are normally reported. In later versions, this counter will be
removed. It is not recommended that this counter be used in the current version.
Measurement Points
The counter is incremented by 1 each time the breathing pilot or coordinated pilot scheduling
is enabled and the eNodeB transmits only CRSs for measuring the bandwidth in a cell in a
millisecond.
Formula
None
Unit
None
Related Features
None

BTS3203E
1.9.78 Number of Times MLB-Triggered Measurements of

WCDMA Frequencies Time Out
Counters
1526743656 L.E2W.Load.M Number of BTS3203E LTE L

easTimeOut.Nu times MLB-
m.Cell triggered
measurements
of WCDMA
frequencies
time out
Description
The counter measures the number of times the eNodeB does not receive any measurement
report related to any WCDMA frequency from a UE after the UE starts performing
measurements of WCDMA frequencies triggered by MLB in a cell.
Measurement Points
When an eNodeB sends an RRC Connection Reconfiguration message containing the IE
MeasConfig triggered by MLB, the UE starts to perform measurements of WCDMA
frequencies if measIdToAddModList in the IE MeasConfig contains measIDs of WCDMA
frequencies. The L.E2W.Load.MeasTimeOut.Num.Cell counter is incremented by 1 each time
the eNodeB does not receive any measurement report related to any WCDMA frequency
within a measurement period.
Formula
None
Unit
None
Related Features
L.E2W.Load.MeasTimeOut. Multi-mode: None

Num.Cell GSM: None
UMTS: None
UTRAN

BTS3203E
1.9.79 Duration in Which an E-UTRAN Cell with Inter-RAT MLB

Enabled Is in the High-Load State
Counters
1526743657 L.IRAT.HighLo Duration in BTS3203E LTE L

ad.Dur.Cell which an E-
UTRAN cell
with inter-RAT
MLB enabled is
in the high-load
state
Description
The counter measures the duration in which an E-UTRAN cell with inter-RAT MLB enabled
is in the high-load state.
Measurement Points
When inter-RAT MLB is enabled for an E-UTRAN cell, the load status of the cell is sampled
per second. The L.IRAT.HighLoad.Dur.Cell counter is incremented by 1 each time a sampling
result indicates that the cell is in the high-load state.
Formula
None
Unit
s
Related Features
L.IRAT.HighLoad.Dur.Cell Multi-mode: None

GSM: None
UMTS: None
UTRAN

BTS3203E
1.9.80 Number of TTIs in which some CRSs are not transmitted

Counters
1526743747 L.Cell.PilotOff Number of BTS3203E LTE L

Tti.Num TTIs in which
some CRSs are
not transmitted
Description
The counter measures the number of TTIs in which some cell-specific reference signals
(CRSs) are not transmitted.
Measurement Points
The counter is incremented by 1 each time the BreathingPilotSwitch option of the
BreathingPilotAlgoSwitch parameter or the EmimoCpsSwitch option of the EmimoSwitch
parameter is selected and layer 2 instructs layer 1 to transmit only CRSs for measuring the
bandwidth in a cell in a millisecond.
Formula
None
Unit
None
Related Features
L.Cell.PilotOffTti.Num Multi-mode: None

GSM: None
UMTS: None
LTE: LEOFD-111306 Breathing Pilot
LEOFD-111307 eMIMO

BTS3203E
1.9.81 Air Interface Load of a Cell

Counters
1526745660 L.Radio.Load.C Average BTS3203E LTE L

ell.Dl.Avg downlink air
interface load
of a cell
Description
The counter measures the air interface load of a cell and is used for comparing inter-cell air
interface load differences.
Measurement Points
The air interface load of a cell is sampled per second within a measurement period. At the end
of a measurement period, the average of the sampling results in the downlink is taken as the
L.Radio.Load.Cell.Dl.Avg counter value. The downlink air interface load of a cell is the
measurement result of load evaluation of a cell in user-number-based MLB.
Formula
None
Unit
None
Related Features
L.Radio.Load.Cell.Dl.Avg Multi-mode: None

GSM: None
UMTS: None

BTS3203E
1.9.82 Number of Times ETWS Messages Are Sent

Counters
1526746000 L.Signal.Num.P Number of PNs BTS3203E LTE L

N.ETWS sent due to
ETWS in a cell
1526746001 L.Signal.Num.S Number of SNs BTS3203E LTE L

N.ETWS sent due to
ETWS in a cell
Description
The counters measure the number of primary notifications (PNs) and secondary notifications
(SNs) sent due to ETWS in a cell. PNs with the same contents are counted only once, and SNs
with the same contents are counted only once within a repetition period.
Measurement Points
When the eNodeB processes a WRITE-REPLACE WARNING REQUEST message from the
MME due to ETWS:
- If the message contains a PN, the eNodeB broadcasts the PN in SIB10. The
L.Signal.Num.PN.ETWS counter measures the number of initially delivered PNs in SIB10.
The counter does not measure the PNs with the same contents.
- If the message contains an SN, the eNodeB broadcasts the SN in SIB11. The
L.Signal.Num.SN.ETWS counter measures the number of initially delivered SNs in SIB11
within a period. The counter does not measure the SNs with the same contents.
Formula
None
Unit
None

BTS3203E
Related Features
L.Signal.Num.PN.ETWS Multi-mode: None

GSM: None
UMTS: None
L.Signal.Num.SN.ETWS Multi-mode: None

GSM: None
UMTS: None
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
1526726767 L.Traffic.DRB.QCI Number of DRBs BTS3203E LTE:

.1 for services with the V100R006C00
QCI of 1 in a cell

QCI of 2 in a cell

QCI of 3 in a cell

QCI of 4 in a cell

QCI of 5 in a cell

BTS3203E


QCI of 6 in a cell

QCI of 7 in a cell

QCI of 8 in a cell

QCI of 9 in a cell
1526728258 L.Traffic.DRB Number of DRBs in BTS3203E LTE:

a cell V100R006C00
1526730820 L.Traffic.DRB.Max Maximum number BTS3203E LTE:

of DRBs in a cell V100R011C10

.QCI.1 of DRBs for services V100R011C10
with QCI 1 in a cell








BTS3203E


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

BTS3203E
1.10.1 Number of DRBs in a Cell

Counters
1526726767 L.Traffic.DRB. Number of BTS3203E LTE L

QCI.1 DRBs for
services with
the QCI of 1 in
a cell

QCI.2 DRBs for
services with
the QCI of 2 in
a cell

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

QCI.4 DRBs for
services with
the QCI of 4 in
a cell

QCI.5 DRBs for
services with
the QCI of 5 in
a cell

QCI.6 DRBs for
services with
the QCI of 6 in
a cell

QCI.7 DRBs for
services with
the QCI of 7 in
a cell

QCI.8 DRBs for
services with
the QCI of 8 in
a cell

BTS3203E


QCI.9 DRBs for
services with
the QCI of 9 in
a cell
1526728258 L.Traffic.DRB Number of BTS3203E LTE L

DRBs 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.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

BTS3203E

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

BTS3203E
1.10.2 Maximum number of DRBs in a Cell

Counters
1526730820 L.Traffic.DRB. Maximum BTS3203E LTE L

Max number of
DRBs in a cell

Max.QCI.1 number of
DRBs for
services with
QCI 1 in a cell

Max.QCI.2 number of
DRBs for
services with
QCI 2 in a cell

Max.QCI.3 number of
DRBs for
services with
QCI 3 in a cell

Max.QCI.4 number of
DRBs for
services with
QCI 4 in a cell

Max.QCI.5 number of
DRBs for
services with
QCI 5 in a cell

Max.QCI.6 number of
DRBs for
services with
QCI 6 in a cell

Max.QCI.7 number of
DRBs for
services with
QCI 7 in a cell

BTS3203E


Max.QCI.8 number of
DRBs for
services with
QCI 8 in a cell

Max.QCI.9 number of
DRBs for
services with
QCI 9 in a cell
Description
The counters measure the maximum number of DRBs for services with a specific QCI in a
cell.
Measurement Points
The number of DRBs for services with each QCI ranging from 1 to 9 in a cell is sampled per
second. At the end of a measurement period, the maximum of these sampling results is used
as the corresponding counter value.
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

BTS3203E

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

BTS3203E
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
1526726776 L.Thrp.bits.UL.QC Uplink traffic BTS3203E LTE:

I.1 volume for PDCP V100R006C00
SDUs of services
a cell
1526726777 L.Thrp.Time.UL.Q Receive duration of BTS3203E LTE:

CI.1 uplink PDCP SDUs V100R006C00
for services with the
QCI of 1 in a cell

SDUs of services
a cell

QCI of 2 in a cell

SDUs of services
a cell

QCI of 3 in a cell

SDUs of services
a cell

BTS3203E


QCI of 4 in a cell

SDUs of services
a cell

QCI of 5 in a cell

SDUs of services
a cell

QCI of 6 in a cell

SDUs of services
a cell

QCI of 7 in a cell

SDUs of services
a cell

QCI of 8 in a cell

BTS3203E


SDUs of services
a cell

QCI of 9 in a cell
1526726803 L.Thrp.bits.DL.QC Downlink traffic BTS3203E LTE:

SDUs of services
a cell
1526726804 L.Thrp.Time.DL.Q Transmit duration of BTS3203E LTE:

CI.1 downlink PDCP V100R006C00
SDUs for services
a cell

SDUs of services
a cell

SDUs for services
a cell

SDUs of services
a cell

SDUs for services
a cell

SDUs of services
a cell

BTS3203E


SDUs for services
a cell

SDUs of services
a cell

SDUs for services
a cell

SDUs of services
a cell

SDUs for services
a cell

SDUs of services
a cell

SDUs for services
a cell

SDUs of services
a cell

BTS3203E


SDUs for services
a cell

SDUs of services
a cell

SDUs for services
a cell
1526727045 L.Thrp.bits.UL.QC Maximum uplink BTS3203E LTE:

I.1.Max traffic volume for V100R006C00
PDCP SDUs of
services with the
QCI of 1 in a cell

PDCP SDUs of
services with the
QCI of 2 in a cell

PDCP SDUs of
services with the
QCI of 3 in a cell

PDCP SDUs of
services with the
QCI of 4 in a cell

PDCP SDUs of
services with the
QCI of 5 in a cell

BTS3203E


PDCP SDUs of
services with the
QCI of 6 in a cell

PDCP SDUs of
services with the
QCI of 7 in a cell

PDCP SDUs of
services with the
QCI of 8 in a cell

PDCP SDUs of
services with the
QCI of 9 in a cell
1526727054 L.Thrp.bits.UL.Ma Maximum uplink BTS3203E LTE:

x traffic volume for V100R006C00
PDCP SDUs of all
services
1526727055 L.Thrp.bits.DL.QC Maximum downlink BTS3203E LTE:

PDCP SDUs of
services with the
QCI of 1 in a cell

PDCP SDUs of
services with the
QCI of 2 in a cell

PDCP SDUs of
services with the
QCI of 3 in a cell

PDCP SDUs of
services with the
QCI of 4 in a cell

BTS3203E


PDCP SDUs of
services with the
QCI of 5 in a cell

PDCP SDUs of
services with the
QCI of 6 in a cell

PDCP SDUs of
services with the
QCI of 7 in a cell

PDCP SDUs of
services with the
QCI of 8 in a cell

PDCP SDUs of
services with the
QCI of 9 in a cell
1526727064 L.Thrp.bits.DL.Ma Maximum downlink BTS3203E LTE:

x traffic volume for V100R006C00
PDCP SDUs of all
services
1526728178 L.Thrp.bits.DL.SR Total Bits of BTS3203E LTE:

B Transmitted V100R006C00
Signaling SDUs on
SRBs at the PDCP
Layer
1526728179 L.Thrp.bits.UL.SR Total Bits of BTS3203E LTE:

B Received Signaling V100R006C00
SDUs on SRBs at
the PDCP Layer
1526728232 L.Thrp.Time.Cell. Total duration of BTS3203E LTE:

DL downlink data V100R006C00
transmission in a
cell

BTS3203E


UL uplink data V100R006C00
transmission in a
cell
1526728234 L.E- Duration of data BTS3203E LTE:

RAB.SessionTime. transmission for V100R006C00
QCI1 services with the
QCI of 1 in a cell

QCI of 2 in a cell

QCI of 3 in a cell

QCI of 4 in a cell

QCI of 5 in a cell

QCI of 6 in a cell

QCI of 7 in a cell

QCI of 8 in a cell

QCI of 9 in a cell

BTS3203E

1526728243 L.E- Total duration of UE BTS3203E LTE:

RAB.SessionTime. data transmission V100R006C00
UE time in a cell
1526728259 L.Thrp.bits.UL Total uplink traffic BTS3203E LTE:

volume for PDCP V100R003C00
PDUs in a cell
1526728260 L.Thrp.Time.UL Total receive BTS3203E LTE:

duration of uplink V100R006C00
PDCP SDUs in a
cell
1526728261 L.Thrp.bits.DL Total downlink BTS3203E LTE:

traffic volume for V100R003C00
PDCP SDUs in a
cell
1526728262 L.Thrp.Time.DL Total transmit BTS3203E LTE:

duration of V100R006C00
downlink PDCP
SDUs in a cell
1526728475 L.Thrp.bits.UL.CE Total bits of uplink BTS3203E LTE:

U PDCP PDUs V100R006C00
received from CEUs
in a cell
1526728476 L.Thrp.Time.UL.C Total duration in BTS3203E LTE:

EU which uplink user V100R006C00
data is received from
CEUs at the PDCP
layer in a cell
1526728477 L.Thrp.bits.DL.CE Total bits of BTS3203E LTE:

U downlink PDCP V100R006C00
SDUs sent to CEUs
in a cell
1526728478 L.Thrp.Time.DL.C Total duration in BTS3203E LTE:

EU which downlink user V100R006C00
data is sent to CEUs
at the PDCP layer in
a cell

DL.HighPrecision uplink data V100R006C00
transmission in a
cell (with the
precision of 1 ms)

BTS3203E


UL.HighPrecision downlink data V100R006C00
transmission in a
cell (with the
precision of 1 ms)
1526729005 L.Thrp.bits.DL.Las Downlink traffic BTS3203E LTE:

tTTI volume sent in the V100R005C00
last TTI for PDCP
SDUs before the
buffer is empty

tTTI.QCI.1 volume sent in the V100R006C00
last TTI for services
with the QCI 1
before the buffer is
empty

with the QCI 2
empty

with the QCI 3
empty

with the QCI 4
empty

with the QCI 5
empty

BTS3203E


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 BTS3203E LTE:

mvLastTTI duration except the V100R005C00
last TTI before the
downlink buffer is
empty

mvLastTTI.QCI.1 duration except the V100R006C00
last TTI before the
downlink buffer is
empty for services
with the QCI 1

last TTI before the
downlink buffer is
empty for services
with the QCI 2

BTS3203E


last TTI before the
downlink buffer is
empty for services
with the QCI 3

last TTI before the
downlink buffer is
empty for services
with the QCI 4

last TTI before the
downlink buffer is
empty for services
with the QCI 5

last TTI before the
downlink buffer is
empty for services
with the QCI 6

last TTI before the
downlink buffer is
empty for services
with the QCI 7

last TTI before the
downlink buffer is
empty for services
with the QCI 8

last TTI before the
downlink buffer is
empty for services
with the QCI 9

BTS3203E

1526729049 L.Thrp.bits.UE.UL Traffic volume of BTS3203E LTE:

.LastTTI uplink PDCP PDUs V100R003C00
received in the last
TTI before the UE
buffer is empty
1526729050 L.Thrp.Time.UE.U Uplink data transmit BTS3203E LTE:

L.RmvLastTTI duration except the V100R003C00
last TTI before the
UE buffer is empty
1526729415 L.Thrp.bits.UE.UL Uplink traffic BTS3203E LTE:

.SmallPkt volume of PDCP V100R006C00
SDUs scheduled for
small packets
1526729416 L.Thrp.Time.UE.U Uplink data BTS3203E LTE:

L.RmvSmallPkt transmission V100R006C00
duration except that
for small packets
1526730836 L.Thrp.Time.UE.U Uplink data BTS3203E LTE:

L.RmvSpecificTTI transmission V100R011C10
duration except that
for specific small
packets transmitted
in the last TTI
1526730837 L.Thrp.bits.UE.UL Uplink traffic BTS3203E LTE:

.SpecificTTI volume at the PDCP V100R011C10
layer of specific
small packets
transmitted in the
last TTI
1526735160 L.E- Total duration of UE BTS3203E LTE:

RAB.SessionTime. data transmission V100R007C00
UE.HighPrecision time with the
precision of 100
milliseconds in a
cell
1526735161 L.E- Total duration of BTS3203E LTE:

RAB.SessionTime. transmission time V100R007C00
HighPrecision for services with all
the QCI with the
precision of 100
milliseconds in a
cell

BTS3203E


HighPrecision.QCI services with the
1 QCI of 1 with the
precision of 100
milliseconds in a
cell

2 QCI of 2 with the
precision of 100
milliseconds in a
cell

3 QCI of 3 with the
precision of 100
milliseconds in a
cell

4 QCI of 4 with the
precision of 100
milliseconds in a
cell

5 QCI of 5 with the
precision of 100
milliseconds in a
cell

6 QCI of 6 with the
precision of 100
milliseconds in a
cell

BTS3203E


7 QCI of 7 with the
precision of 100
milliseconds in a
cell

8 QCI of 8 with the
precision of 100
milliseconds in a
cell

9 QCI of 9 with the
precision of 100
milliseconds in a
cell
1526737745 L.Thrp.bits.UL.Fre Uplink PDCP-layer BTS3203E LTE:

qshare traffic volume of V100R011C10
CCUs in a cell using
the UMTS and LTE
shared spectrum
1526737746 L.Thrp.Time.UL.F Transmission BTS3203E LTE:

reqshare duration of uplink V100R011C10
PDCP-layer data for
CCUs in a cell using
the UMTS and LTE
shared spectrum
1526741759 L.Thrp.Time.UL.B Total duration of BTS3203E LTE:

orderUE receiving data from V100R011C10
cell edge UEs in the
uplink at the PDCP
layer in a cell
1526741760 L.Thrp.Time.DL.B Total duration of BTS3203E LTE:

orderUE sending data to cell V100R011C10
edge UEs in the
downlink at the
PDCP layer in a cell

BTS3203E

1526741874 L.Thrp.Time.DL.L Total duration for BTS3203E LTE:

teLaaCAUser LTE+LAA activated V100R011C10
CA UEs
transmitting
downlink data at the
PDCP layer in a cell
1526741875 L.Thrp.bits.DL.Lte Total traffic volume BTS3203E LTE:

LaaCAUser for PDCP SDUs sent V100R011C10
to LTE+LAA
activated CA UEs in
a cell

PDUs of services
with the QCI of 65
in a cell

PDUs of services
with the QCI of 66
in a cell

PDUs of services
with the QCI of 69
in a cell

PDUs of services
with the QCI of 70
in a cell

CI.65 uplink PDCP PDUs V100R011C10
QCI of 65 in a cell

QCI of 66 in a cell

QCI of 69 in a cell

BTS3203E


QCI of 70 in a cell

SDUs of services
with the QCI of 65
in a cell

SDUs of services
with the QCI of 66
in a cell

SDUs of services
with the QCI of 69
in a cell

SDUs of services
with the QCI of 70
in a cell

SDUs for services
with the QCI of 65
in a cell

SDUs for services
with the QCI of 66
in a cell

SDUs for services
with the QCI of 69
in a cell

SDUs for services
with the QCI of 70
in a cell

BTS3203E

1526742186 L.Thrp.Time.DL.S Downlink data BTS3203E LTE:

mallPktConverted transmission V100R011C10
duration with
converted downlink
small-packet
transmission
duration
1526743764 L.Thrp.Time.UL.B Total duration of BTS3203E LTE:

orderUE.JointRece receiving PDCP V100R012C00
ption PDUs from joint
reception CEUs in a
cell
1526743765 L.Thrp.Time.DL.B Total duration of BTS3203E LTE:

orderUE.JointTran sending PDCP V100R012C00
smit SDUs to joint
transmission CEUs
in a cell
1526745879 L.Thrp.bits.DL.W Downlink traffic BTS3203E LTE:

BB volume for PDCP V100R012C10
SDUs of WBB UEs
in a cell

tTTI.WBB volume sent in the V100R012C10
last TTI for PDCP
SDUs of WBB UEs
empty

mvLastTTI.WBB duration except the V100R012C10
last TTI of WBB
UEs before the
downlink buffer is
empty
1526745988 L.Thrp.TransferTi Downlink PDCP- BTS3203E LTE:

me.DL.RmvLastT layer data V100R012C10
TI transmission
duration excluding
the last TTI before
the buffer is empty

BTS3203E
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

BTS3203E
L.Thrp.bits.DL L.Thrp.bits.DL.CEU
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.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

BTS3203E
1.11.1 Maximum Uplink Traffic Volume for PDCP SDUs in a Cell

Counters
1526727045 L.Thrp.bits.UL. Maximum BTS3203E LTE L

QCI.1.Max uplink traffic
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

BTS3203E


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 uplink traffic
volume for
PDCP SDUs of
all services
Description
The counters measure the maximum uplink traffic volume for received PDCP SDUs of
services with a specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The size of the payloads in the received PDCP SDUs of each service with a specific QCI
ranging from 1 to 9 is sampled per second in a cell. The size is accumulated at each sampling
point. At the end of a measurement period, the maximum of these sampling results is used as
the value of the corresponding counter. The counter value may exceed the air interface
capability. This is because the uplink data must be ordered before it is transmitted.

BTS3203E
Formula
None
Unit
bit
Related Features
L.Thrp.bits.UL.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

BTS3203E

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 BTS3203E LTE L

QCI.1.Max downlink traffic
volume for
PDCP SDUs of
services with
the QCI of 1 in
a cell

BTS3203E


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

BTS3203E


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
volume for
PDCP SDUs of
all services
Description
The counters measure the maximum downlink traffic volume for transmitted PDCP SDUs of
Measurement Points
The size of the payloads in the transmitted PDCP SDUs of each service with a different QCI
ranging from 1 to 9 is sampled per second in a cell. At the end of a measurement period, the
maximum of these sampling results is used as the value of the corresponding counter.
Formula
None
Unit
bit

BTS3203E
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

BTS3203E

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 BTS3203E LTE L

SRB Transmitted
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.
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.

BTS3203E
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

PDCP Layer in a Cell
Counters
1526728179 L.Thrp.bits.UL. Total Bits of BTS3203E LTE L

SRB Received
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.
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

BTS3203E
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 BTS3203E LTE L

ll.DL of downlink
data
transmission in
a cell

ll.UL of uplink data
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.
Disuse Statement:
The counter L.Thrp.Time.Cell.DL (ID: 1526728232) will be replaced by the counter

L.Thrp.Time.Cell.DL.HighPrecision (ID: 1526728997) in later versions. In the current
version, both counters are valid and the counter values are normally reported. In later
versions, the L.Thrp.Time.Cell.DL counter will be removed. It is not recommended that the
L.Thrp.Time.Cell.DL counter be used in the current version.
The counter L.Thrp.Time.Cell.UL (ID: 1526728233) will be replaced by the counter

L.Thrp.Time.Cell.UL.HighPrecision (ID: 1526728998) in later versions. In the current

BTS3203E
versions, the L.Thrp.Time.Cell.UL counter will be removed. It is not recommended that the
L.Thrp.Time.Cell.UL counter be used in the current version.
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

BTS3203E
1.11.6 Duration of Data Transmission for Services with a Specific

QCI in a Cell
Counters
1526728234 L.E- Duration of BTS3203E LTE L

RAB.SessionTi data
me.QCI1 transmission for
services with
the QCI of 1 in
a cell

RAB.SessionTi data
services with
the QCI of 2 in
a cell

RAB.SessionTi data
services with
the QCI of 3 in
a cell

RAB.SessionTi data
services with
the QCI of 4 in
a cell

RAB.SessionTi data
services with
the QCI of 5 in
a cell

RAB.SessionTi data
services with
the QCI of 6 in
a cell

BTS3203E


RAB.SessionTi data
services with
the QCI of 7 in
a cell

RAB.SessionTi data
services with
the QCI of 8 in
a cell

RAB.SessionTi data
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.
Disuse Statement:
The counter L.E-RAB.SessionTime.QCI1 (ID: 1526728234) will be replaced by the counter
L.E-RAB.SessionTime.HighPrecision.QCI1 (ID: 1526735162) in later versions. In the current
versions, the L.E-RAB.SessionTime.QCI1 counter will be removed. It is not recommended
that the L.E-RAB.SessionTime.QCI1 counter be used in the current version
that the L.E-RAB.SessionTime.QCI2 counter be used in the current version.

BTS3203E

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

BTS3203E
Related Features

RAB.SessionTime.QCI1 GSM: None
UMTS: None

UMTS: None

UMTS: None

UMTS: None

UMTS: None

UMTS: None

UMTS: None

BTS3203E

UMTS: None

UMTS: None
1.11.7 Total Duration of UE Data Transmission in a Cell

Counters
1526728243 L.E- Total duration BTS3203E LTE L

RAB.SessionTi of UE data
me.UE transmission
time in a cell
Description
The counter measures the total duration of UE data transmission in a cell.
Disuse Statement:
The counter L.E-RAB.SessionTime.UE (ID: 1526728243) will be replaced by the counter
L.E-RAB.SessionTime.UE.HighPrecision (ID: 1526735160) in later versions. In the current
versions, the L.E-RAB.SessionTime.UE counter will be removed. It is not recommended that
the L.E-RAB.SessionTime.UE counter be used in the current version.
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.

BTS3203E
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 BTS3203E LTE L

QCI.1 volume for
PDCP SDUs of
services with
the QCI of 1 in
a cell

QCI.2 volume for
PDCP SDUs of
services with
the QCI of 2 in
a cell

QCI.3 volume for
PDCP SDUs of
services with
the QCI of 3 in
a cell

BTS3203E


QCI.4 volume for
PDCP SDUs of
services with
the QCI of 4 in
a cell

QCI.5 volume for
PDCP SDUs of
services with
the QCI of 5 in
a cell

QCI.6 volume for
PDCP SDUs of
services with
the QCI of 6 in
a cell

QCI.7 volume for
PDCP SDUs of
services with
the QCI of 7 in
a cell

QCI.8 volume for
PDCP SDUs of
services with
the QCI of 8 in
a cell

QCI.9 volume for
PDCP SDUs of
services with
the QCI of 9 in
a cell
1526728259 L.Thrp.bits.UL Total uplink BTS3203E LTE L

traffic volume
for PDCP
PDUs in a cell

BTS3203E


QCI.65 volume for
PDCP PDUs of
services with
the QCI of 65
in a cell

QCI.66 volume for
PDCP PDUs of
services with
the QCI of 66
in a cell

QCI.69 volume for
PDCP PDUs of
services with
the QCI of 69
in a cell

QCI.70 volume for
PDCP PDUs of
services with
the QCI of 70
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 number of bits of received uplink PDCP PDUs of services with a specific QCI within the
range of 1 to 9, 65, 66, 69, and 70 is accumulated in a cell and taken as the value of the
corresponding counter. The total number is taken as the value of the L.Thrp.bits.UL counter.
If a UE is initialized as a high-speed UE (that is, UE in high-speed movement), the total
number of bits of received uplink PDCP PDUs of services with QCIs of 1 to 9 for such UEs
in a cell is accumulated and taken as the value of the L.Thrp.bits.UL.Hst counter.
Formula
None
Unit
bit

BTS3203E
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

BTS3203E

GSM: None
UMTS: None

GSM: None
UMTS: None
L.Thrp.bits.UL Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

BTS3203E
1.11.9 Receive Duration of Uplink PDCP SDUs in a Cell
Counters
1526726777 L.Thrp.Time.U Receive BTS3203E LTE L

L.QCI.1 duration of
uplink PDCP
SDUs for
services with
the QCI of 1 in
a cell

L.QCI.2 duration of
uplink PDCP
SDUs for
services with
the QCI of 2 in
a cell

L.QCI.3 duration of
uplink PDCP
SDUs for
services with
the QCI of 3 in
a cell

L.QCI.4 duration of
uplink PDCP
SDUs for
services with
the QCI of 4 in
a cell

L.QCI.5 duration of
uplink PDCP
SDUs for
services with
the QCI of 5 in
a cell

L.QCI.6 duration of
uplink PDCP
SDUs for
services with
the QCI of 6 in
a cell

BTS3203E


L.QCI.7 duration of
uplink PDCP
SDUs for
services with
the QCI of 7 in
a cell

L.QCI.8 duration of
uplink PDCP
SDUs for
services with
the QCI of 8 in
a cell

L.QCI.9 duration of
uplink PDCP
SDUs for
services with
the QCI of 9 in
a cell
1526728260 L.Thrp.Time.U Total receive BTS3203E LTE L

L duration of
uplink PDCP
SDUs in a cell

L.QCI.65 duration of
uplink PDCP
PDUs for
services with
the QCI of 65
in a cell

uplink PDCP
PDUs for
services with
the QCI of 66
in a cell

BTS3203E


uplink PDCP
PDUs for
services with
the QCI of 69
in a cell

uplink PDCP
PDUs for
services with
the QCI of 70
in a cell
Description
The counters measure the total uplink receive 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 received 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

BTS3203E

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

BTS3203E

GSM: None
UMTS: None
L.Thrp.Time.UL Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

BTS3203E
1.11.10 Downlink Traffic Volume for PDCP SDUs in a Cell
Counters
1526726803 L.Thrp.bits.DL. Downlink BTS3203E LTE L

QCI.1 traffic volume
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

BTS3203E


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 BTS3203E LTE L

traffic volume
for PDCP
SDUs in a cell

for PDCP
SDUs of
services with
the QCI of 65
in a cell

for PDCP
SDUs of
services with
the QCI of 66
in a cell

BTS3203E


for PDCP
SDUs of
services with
the QCI of 69
in a cell

for PDCP
SDUs of
services with
the QCI of 70
in a cell

WBB traffic volume
for PDCP
SDUs of WBB
UEs in a cell
Description
The counters measure the total traffic volume of transmitted PDCP SDUs for services with a
specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The number of bits of transmitted downlink PDCP SDUs of services with a specific QCI
within the range of 1 to 9, 65, 66, 69, and 70 is accumulated in a cell and taken as the value of
the corresponding counter. The total number is taken as the value of the L.Thrp.bits.DL
counter.

number of bits of transmitted downlink PDCP SDUs of services with QCIs 1 to 9 for such
UEs in a cell is accumulated and taken as the value of the L.Thrp.bits.DL.Hst counter.
If a UE is identified as a WBB UE, the total number of bits of transmitted downlink PDCP
SDUs for such UEs in a cell is accumulated as the L.Thrp.bits.DL.WBB counter value.
Formula
None
Unit
bit

BTS3203E
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

BTS3203E

GSM: None
UMTS: None

GSM: None
UMTS: None
L.Thrp.bits.DL Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

BTS3203E
L.Thrp.bits.DL.WBB Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-110223 WBB Specified Policy
Management
1.11.11 Transmit Duration of Downlink PDCP SDUs in a Cell

Counters
1526726804 L.Thrp.Time.D Transmit BTS3203E LTE L

L.QCI.1 duration of
downlink PDCP
SDUs for
services with
the QCI of 1 in
a cell

L.QCI.2 duration of
downlink PDCP
SDUs for
services with
the QCI of 2 in
a cell

L.QCI.3 duration of
downlink PDCP
SDUs for
services with
the QCI of 3 in
a cell

L.QCI.4 duration of
downlink PDCP
SDUs for
services with
the QCI of 4 in
a cell

BTS3203E


L.QCI.5 duration of
downlink PDCP
SDUs for
services with
the QCI of 5 in
a cell

L.QCI.6 duration of
downlink PDCP
SDUs for
services with
the QCI of 6 in
a cell

L.QCI.7 duration of
downlink PDCP
SDUs for
services with
the QCI of 7 in
a cell

L.QCI.8 duration of
downlink PDCP
SDUs for
services with
the QCI of 8 in
a cell

L.QCI.9 duration of
downlink PDCP
SDUs for
services with
the QCI of 9 in
a cell
1526728262 L.Thrp.Time.D Total transmit BTS3203E LTE L

L duration of
downlink PDCP
SDUs in a cell

BTS3203E


downlink PDCP
SDUs for
services with
the QCI of 65
in a cell

downlink PDCP
SDUs for
services with
the QCI of 66
in a cell

downlink PDCP
SDUs for
services with
the QCI of 69
in a cell

downlink PDCP
SDUs for
services with
the QCI of 70
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.

BTS3203E
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

BTS3203E

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
L.Thrp.Time.DL Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

BTS3203E

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 BTS3203E LTE L

CEU uplink PDCP
PDUs received
from CEUs in a
cell
1526728477 L.Thrp.bits.DL. Total bits of BTS3203E LTE L

CEU downlink PDCP
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.
Disuse Statement:
The counter L.Thrp.bits.UL.CEU (ID: 1526728475) will be replaced by the counter
L.Thrp.bits.UL.BorderUE (ID: 1526737754) in later versions. In the current version, both
counters are valid and the counter values are normally reported. In later versions, this counter
will be removed. It is not recommended that the L.Thrp.bits.UL.CEU counter be used in the
current version.
The counter L.Thrp.bits.DL.CEU (ID: 1526728477) will be replaced by the counter
L.Thrp.bits.DL.BorderUE (ID: 1526737755) in later versions. In the current version, both
will be removed. It is not recommended that the L.Thrp.bits.DL.CEU counter be used in the
current version.

BTS3203E
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
None
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 BTS3203E LTE L

L.CEU in which uplink
user data is
received from
CEUs at the
PDCP layer in a
cell
1526728478 L.Thrp.Time.D Total duration BTS3203E LTE L

L.CEU in which
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.
Disuse Statement:

BTS3203E
The counter L.Thrp.Time.UL.CEU (ID: 1526728476) will be replaced by the counter

L.Thrp.Time.UL.BorderUE (ID: 1526741759) in later versions. In the current version, both
will be removed. It is not recommended that the L.Thrp.Time.UL.CEU counter be used in the
current version.
The counter L.Thrp.Time.DL.CEU (ID: 1526728478) will be replaced by the counter
L.Thrp.Time.DL.BorderUE (ID: 1526741760) in later versions. In the current version, both
will be removed. It is not recommended that the L.Thrp.Time.DL.CEU counter be used in the
current version.
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
None
1.11.14 Total Duration of Uplink or Downlink Data Transmission

in a Cell (with the Precision of 1 ms)
Counters

ll.DL.HighPreci of uplink data
sion transmission in
a cell (with the
precision of 1
ms)

BTS3203E


ll.UL.HighPreci of downlink
sion data
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

BTS3203E
L.Thrp.Time.Cell.UL.HighP Multi-mode: None

recision GSM: None
UMTS: None
1.11.15 Downlink traffic volume sent in the last TTI before the
buffer is empty
Counters

LastTTI traffic volume
sent in the last
TTI for PDCP
SDUs before
the buffer is
empty

LastTTI.QCI.1 traffic volume
sent in the last
TTI for services
with the QCI 1
before the
buffer is empty

sent in the last
TTI for services
with the QCI 2
before the
buffer is empty

sent in the last
TTI for services
with the QCI 3
before the
buffer is empty

BTS3203E


sent in the last
TTI for services
with the QCI 4
before the
buffer is empty

sent in the last
TTI for services
with the QCI 5
before the
buffer is empty

sent in the last
TTI for services
with the QCI 6
before the
buffer is empty

sent in the last
TTI for services
with the QCI 7
before the
buffer is empty

sent in the last
TTI for services
with the QCI 8
before the
buffer is empty

sent in the last
TTI for services
with the QCI 9
before the
buffer is empty

BTS3203E


LastTTI.WBB traffic volume
sent in the last
TTI for PDCP
SDUs of WBB
UEs 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 number of bits of downlink PDCP SDUs sent in the last TTI for services with a specific
QCI within the range of 1 to 9 before the DRB buffer is empty is accumulated in a cell and
taken as the value of the corresponding counter. The total number is taken as the value of the
L.Thrp.bits.DL.LastTTI counter.

number of bits of downlink PDCP SDUs sent in the last TTI before the DRB buffer is empty
for such UEs in a cell is accumulated and taken as the value of the
L.Thrp.bits.DL.LastTTI.Hst counter.
If a UE is identified as a WBB UE, the total number of bits of downlink PDCP SDUs sent in
the last TTI before the DRB buffer is empty for such UEs in a cell is accumulated and taken
as the L.Thrp.bits.DL.LastTTI.WBB counter value.
Formula
None
Unit
bit
Related Features
L.Thrp.bits.DL.LastTTI Multi-mode: None

GSM: None
UMTS: None

BTS3203E
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

BTS3203E

I.8 GSM: None
UMTS: None

I.9 GSM: None
UMTS: None
L.Thrp.bits.DL.LastTTI.WB Multi-mode: None

B GSM: None
UMTS: None
Management
1.11.16 Data transmit duration except the last TTI before the
downlink buffer is empty
Counters
1526729015 L.Thrp.Time.D Data transmit BTS3203E LTE L

L.RmvLastTTI duration except
the last TTI
before the
downlink buffer
is empty

L.RmvLastTTI. duration except
QCI.1 the last TTI
before the
downlink buffer
is empty for
services with
the QCI 1

BTS3203E


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

BTS3203E


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

WBB the last TTI of
WBB UEs
before the
downlink buffer
is empty
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 downlink data transmit duration for services with a specific QCI within the range of 1 to
9 in a cell is sampled per millisecond. If there is data to be sent in the DRB buffer at the
downlink PDCP layer within a millisecond, the corresponding counter is incremented by 1
ms, excluding the last TTI before the DRB buffer is empty. The total downlink data transmit
duration of services with QCIs 1 to 9 is taken as the value of the
L.Thrp.Time.DL.RmvLastTTI counter.

BTS3203E
For UEs initialized as high-speed UEs (that is, UEs in high-speed movement), the
L.Thrp.Time.UE.DL.RmvLastTTI.Hst counter is incremented by 1.
For UEs identified as WBB UEs, the L.Thrp.Time.DL.RmvLastTTI.WBB counter is

incremented by 1.
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

BTS3203E

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

TI.WBB GSM: None
UMTS: None
Management

BTS3203E
1.11.17 Traffic Volume of Uplink PDCP SDUs Received in the

Last TTI Before the UE Buffer is Empty
Counters
1526729049 L.Thrp.bits.UE. Traffic volume BTS3203E LTE L

UL.LastTTI of uplink PDCP
PDUs received
in the last TTI
before the UE
buffer is empty
Description
The counter measures the uplink traffic volume received in the last TTI before the UE buffer
is empty in a cell.
Measurement Points
The number of bits of PDCP PDUs received in the last TTI before the UE uplink buffer is
empty is measured in a cell and taken as the value of the L.Thrp.bits.UE.UL.LastTTI counter.
If a UE is initialized as a high-speed UE (that is, UE in high-speed movement), the number of

bits of PDCP PDUs received in the last TTI before the UE uplink buffer is empty for such
UEs is measured in a cell and taken as the value of the L.Thrp.bits.UE.UL.LastTTI counter.
Formula
None
Unit
bit
Related Features
L.Thrp.bits.UE.UL.LastTTI Multi-mode: None

GSM: None
UMTS: None

BTS3203E
1.11.18 Uplink Data Transmit Duration Except the Last TTI Before
the UE Buffer is Empty
Counters
1526729050 L.Thrp.Time.U Uplink data BTS3203E LTE L

E.UL.RmvLast transmit
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 uplink data transmit duration in a cell is sampled per millisecond. If there is uplink data
to be sent within this millisecond, the L.Thrp.Time.UE.UL.RmvLastTTI counter is
incremented by 1 ms, excluding the last TTI before the UE buffer is empty.
For UEs initialized as high-speed UEs (that is, UEs in high-speed movement), the
L.Thrp.Time.UE.UL.RmvLastTTI.Hst counter is incremented by 1.
Formula
None
Unit
ms
Related Features
L.Thrp.Time.UE.UL.RmvLa Multi-mode: None

stTTI GSM: None
UMTS: None

BTS3203E
1.11.19 Uplink Traffic Volume of PDCP SDUs Scheduled for

Small Packets
Counters
1526729415 L.Thrp.bits.UE. Uplink traffic BTS3203E LTE L

UL.SmallPkt volume of
PDCP SDUs
scheduled for
small packets
Description
The counter measures the traffic volume of PDCP SDUs scheduled for small packets in a cell.
Measurement Points
An uplink packet whose PDCP SDU is scheduled before the eNodeB receives a buffer status
report (BSR) or is received by the eNodeB when the uplink buffer of the UE is empty is a
small packet. The traffic volume of these small packets received in a measurement period in a
cell is accumulated as the value of the L.Thrp.bits.UE.UL.SmallPkt counter.
Formula
None
Unit
bit
Related Features
L.Thrp.bits.UE.UL.SmallPk Multi-mode: None

t GSM: None
UMTS: None

BTS3203E
1.11.20 Uplink Data Transmission Duration Except that for Small

Packets
Counters

E.UL.RmvSmal transmission
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

BTS3203E
1.11.21 Uplink Data Transmission Duration Except that for

Specific Small Packets Transmitted in the Last TTI
Counters

E.UL.RmvSpec transmission
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. The L.Thrp.Time.UE.UL.RmvSpecificTTI counter applies only to LTE FDD.
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

BTS3203E
Related Features
L.Thrp.Time.UE.UL.RmvSp Multi-mode: None

ecificTTI GSM: None
UMTS: None
LTE: LBFD-002025 Basic Scheduling
1.11.22 Uplink Traffic Volume at the PDCP Layer of Specific

Small Packets Transmitted in the Last TTI
Counters
1526730837 L.Thrp.bits.UE. Uplink traffic BTS3203E LTE L

UL.SpecificTTI volume at the
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. The L.Thrp.bits.UE.UL.SpecificTTI counter applies only to LTE FDD.
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

BTS3203E
Unit
bit
Related Features
L.Thrp.bits.UE.UL.Specific Multi-mode: None

TTI GSM: None
UMTS: None
1.11.23 Total Duration of UE Data Transmission with the

precision of 100 milliseconds in a Cell
Counters

RAB.SessionTi of UE data
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

BTS3203E
Related Features

RAB.SessionTime.UE.High GSM: None
Precision
UMTS: None
1.11.24 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
me.HighPrecisi time for
on services with all
the QCI with
the precision of
100
milliseconds in
a cell

RAB.SessionTi data
me.HighPrecisi transmission for
on.QCI1 services with
the QCI of 1
with the
precision of 100
milliseconds in
a cell

RAB.SessionTi data
the QCI of 2
with the
precision of 100
milliseconds in
a cell

BTS3203E


RAB.SessionTi data
the QCI of 3
with the
precision of 100
milliseconds in
a cell

RAB.SessionTi data
the QCI of 4
with the
precision of 100
milliseconds in
a cell

RAB.SessionTi data
the QCI of 5
with the
precision of 100
milliseconds in
a cell

RAB.SessionTi data
the QCI of 6
with the
precision of 100
milliseconds in
a cell

RAB.SessionTi data
the QCI of 7
with the
precision of 100
milliseconds in
a cell

BTS3203E


RAB.SessionTi data
the QCI of 8
with the
precision of 100
milliseconds in
a cell

RAB.SessionTi data
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

BTS3203E
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

BTS3203E

ision.QCI7
UMTS: None

ision.QCI8
UMTS: None

ision.QCI9
UMTS: None
1.11.25 Uplink PDCP-layer Traffic Volume of CCUs in a Cell

Using the UMTS and LTE Shared Spectrum
Counters
1526737745 L.Thrp.bits.UL. Uplink PDCP- BTS3203E LTE L

Freqshare layer traffic
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

BTS3203E
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
None
1.11.26 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 BTS3203E LTE L

L.Freqshare duration of
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

BTS3203E
Related Features
None
1.11.27 Total Duration of Receiving Data from Cell Edge UEs in

the Uplink at the PDCP Layer in a Cell
Counters

L.BorderUE of receiving
data from cell
edge UEs in the
uplink at the
PDCP layer in a
cell
Description
The counter measures the total duration of receiving data from cell edge UEs in the uplink at
the PDCP layer in a cell.
Measurement Points
The transmission duration of uplink PDCP-layer data for CEUs is accumulated in a cell
within a measurement period. At the end of a measurement period, the accumulation value is
taken as the value of the L.Thrp.Time.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 and the RSRP value of the serving cell. This
identification function is controlled by the BasedA3EdgeUserSwitch option of the
CellCounterAlgoSwitch parameter in the CellCounterParaGroup MO. The threshold is
specified by the EdgeUserA3Offset and EdgeUserServRSRPThd parameters.
Formula
None
Unit
ms

BTS3203E
Related Features
L.Thrp.Time.UL.BorderUE Multi-mode: None

GSM: None
UMTS: None
1.11.28 Total Duration of Sending Data to Cell Edges UEs in the

Downlink at the PDCP Layer in a Cell
Counters

L.BorderUE of sending data
to cell edge
UEs in the
downlink at the
PDCP layer in a
cell
Description
The counter measures the total duration of sending data to cell edge UEs in the downlink at
the PDCP layer in a cell.
Measurement Points
The transmission duration of downlink PDCP-layer data for CEUs is accumulated in a cell
within a measurement period. At the end of a measurement period, the accumulation value is
taken as the value of the L.Thrp.Time.DL.BorderUE counter.
counter has deviation to the actual duration. 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 and the RSRP value of the serving cell. This identification
function is controlled by the BasedA3EdgeUserSwitch option of the CellCounterAlgoSwitch
parameter in the CellCounterParaGroup MO. The threshold is specified by the
EdgeUserA3Offset and EdgeUserServRSRPThd parameters.
Formula
None

BTS3203E
Unit
ms
Related Features
L.Thrp.Time.DL.BorderUE Multi-mode: None

GSM: None
UMTS: None
1.11.29 Duration of Downlink PDCP-Layer Data Transmission to

CA UEs that Have All SCells Activated for Downlink LAA CA in
a Cell
Counters

L.LteLaaCAUs for LTE+LAA
er activated CA
UEs
transmitting
downlink data
at the PDCP
layer 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 in the downlink LAA CA state and have all SCells activated
in a cell.
Measurement Points
The eNodeB detects whether there is data transmitted on downlink DRBs for CA UEs that
have SCells activated for downlink LAA CA every millisecond in a cell. If the eNodeB
determines that there is data transmitted for such a CA UE, the data transmission duration for
the CA UE is incremented by 1 ms. The duration of downlink data transmission to CA UEs
that have all SCells activated for downlink LAA CA is accumulated and taken as the value of
the L.Thrp.Time.DL.LteLaaCAUser counter.
counter has deviation to the actual duration.

BTS3203E
Formula
None
Unit
ms
Related Features
L.Thrp.Time.DL.LteLaaCA Multi-mode: None

User GSM: None
UMTS: None
LTE: LEOFD-111301 Licensed Assisted Access
(LAA) for CA
1.11.30 Downlink PDCP-Layer Traffic Volume of CA UEs that

Have All SCells Activated for Downlink LAA CA in a Cell
Counters
1526741875 L.Thrp.bits.DL. Total traffic BTS3203E LTE L

LteLaaCAUser volume for
PDCP SDUs
sent to LTE
+LAA activated
CA UEs in a
cell
Description
The counter measures the downlink traffic volume of PDCP SDUs to CA UEs that treat the
local cell as their PCell and have all SCells activated for downlink LAA CA in a cell.
Measurement Points
The traffic volume of successfully transmitted PDCP SDUs for CA UEs that are in the
downlink LAA CA state and have SCells activated in a cell is accumulated and taken as the
value of the L.Thrp.bits.DL.LteLaaCAUser counter.
Formula
None

BTS3203E
Unit
bit
Related Features
L.Thrp.bits.DL.LteLaaCAU Multi-mode: None

ser GSM: None
UMTS: None
LTE: LEOFD-111301 Licensed Assisted Access
(LAA) for CA
1.11.31 Downlink data transmission duration with converted

downlink small-packet transmission duration
Counters
1526742186 L.Thrp.Time.D Downlink data BTS3203E LTE L

L.SmallPktCon transmission
verted duration with
converted
downlink small-
packet
transmission
duration
Description
This counter measures the downlink PDCP-layer data transmission duration of all UEs in a
cell. The TTIs in which downlink small packets are transmitted must be converted and then
accumulated in the counter.
Measurement Points
The eNodeB monitors the downlink data transmission per millisecond in a cell. If the
downlink PDCP-layer DRB buffer has data to be transmitted in a millisecond, the counter is
incremented by 1. If the DRB buffer becomes empty in a TTI, the eNodeB is regarded as
transmitting downlink small packets in this TTI. The ratio of the downlink data volume
transmitted in this TTI to the maximum volume of data that can be transmitted by using
wideband RBs in a TTI is taken as the converted transmission duration of the small packets
and is accumulated.

BTS3203E
Formula
None
Unit
ms
Related Features
L.Thrp.Time.DL.SmallPktC Multi-mode: None

onverted GSM: None
UMTS: None
1.11.32 Total Duration of Receiving PDCP PDUs from Joint

Reception CEUs in a Cell
Counters

L.BorderUE.Joi of receiving
ntReception PDCP PDUs
from joint
reception CEUs
in a cell
Description
The counter measures the total duration of receiving PDCP PDUs from uplink joint reception
CEUs in a cell.
Measurement Points
The total duration of receiving PDCP PDUs from all uplink joint reception CEUs in a cell in a
measurement period is measured and used as the value of the counter. The eNodeB
determines whether a UE is a joint reception CEU based on the uplink equivalent RSRP
difference between the serving cell of the UE and the neighboring cell with strongest signals.
The threshold of the uplink equivalent RSRP difference is specified by the
EdgeUserSRSOffse parameter in the CellCounterParaGroup MO.

BTS3203E
Formula
None
Unit
ms
Related Features
L.Thrp.Time.UL.BorderUE. Multi-mode: None

JointReception GSM: None
UMTS: None
LTE: LEOFD-111305 Virtual 4T4R
1.11.33 Total Duration of Sending PDCP SDUs to Joint

Transmission CEUs in a Cell
Counters

L.BorderUE.Joi of sending
ntTransmit PDCP SDUs to
joint
transmission
CEUs in a cell
Description
The counter measures the total duration of sending PDCP SDUs to downlink joint
transmission CEUs in a cell
Measurement Points
The total duration of transmitting PDCP SDUs to all downlink joint transmission CEUs in a
cell in a measurement period is measured and used as the value of the counter.
The internal timer of the eNodeB has a deviation of one period, causing a deviation to the
measurement result of the counter.
The eNodeB determines whether a UE is a joint transmission CEU based on the downlink
equivalent RSRP difference between the serving cell of the UE and the neighboring cell with
strongest signals. The threshold of the downlink equivalent RSRP difference is specified by
the EdgeUserSRSOffse parameter in the CellCounterParaGroup MO.

BTS3203E
Formula
None
Unit
ms
Related Features
L.Thrp.Time.DL.BorderUE. Multi-mode: None

JointTransmit GSM: None
UMTS: None
1.11.34 Downlink PDCP-Layer Transmission Duration
Counters
1526745988 L.Thrp.Transfer Downlink BTS3203E LTE L

Time.DL.RmvL PDCP-layer
astTTI data
transmission
duration
excluding the
last TTI before
the buffer is
empty
Description
The counter measures the accumulative PDCP-layer transmission duration of services carried
on DRBs of all UEs in a cell.
Measurement Points
The L.Thrp.TransferTime.DL.RmvLastTTI counter is incremented by 1 each time services
carried on DRBs are scheduled within a TTI and the TTI is not the last TTI before the buffer
is empty. The transmission duration of all DRBs of all UEs in the cell is accumulated.
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.

BTS3203E
Formula
None
Unit
ms
Related Features
L.Thrp.TransferTime.DL.R Multi-mode: None

mvLastTTI GSM: None
UMTS: None
1.12 PDCP Measurement (Traffic.PDCP.Cell)

Overview
The Traffic.PDCP.Cell function subset measures the number of downlink signaling SDUs
transmitted from the PDCP layer to the RLC layer, number of downlink traffic SDUs
transmitted from the PDCP layer to the RLC layer for services with a specific QCI, number of
discarded downlink signaling SDUs transmitted from the PDCP layer to the RLC layer,
number of discarded downlink traffic SDUs transmitted from the PDCP layer to the RLC
layer for services with a specific QCI, number of uplink signaling SDUs received by the
PDCP layer from the RLC layer, or number of discarded uplink signaling SDUs received by
the PDCP layer from the RLC layer.
Counters
1526726833 L.PDCP.Tx.Disc.Tr Number of downlink BTS3203E LTE:

f.SDU.QCI.1 traffic SDUs V100R006C00
discarded by the
PDCP layer for
services with the
QCI of 1 in a cell

discarded by the
PDCP layer for
services with the
QCI of 2 in a cell

BTS3203E


discarded by the
PDCP layer for
services with the
QCI of 3 in a cell

discarded by the
PDCP layer for
services with the
QCI of 4 in a cell

discarded by the
PDCP layer for
services with the
QCI of 5 in a cell

discarded by the
PDCP layer for
services with the
QCI of 6 in a cell

discarded by the
PDCP layer for
services with the
QCI of 7 in a cell

discarded by the
PDCP layer for
services with the
QCI of 8 in a cell

discarded by the
PDCP layer for
services with the
QCI of 9 in a cell

BTS3203E

1526727349 L.PDCP.DL.RoHC. Compression rate of BTS3203E LTE:

HdrCompRatio headers of all V100R006C00
downlink PDCP
SDUs after the
ROHC
1526727350 L.PDCP.DL.RoHC. Compression rate of BTS3203E LTE:

PktCompRatio all downlink PDCP V100R006C00
SDUs (including
headers and
payloads) after the
ROHC
1526727351 L.PDCP.UL.RoHC. Decompression BTS3203E LTE:

FailDecompRatio failure rate of all V100R006C00
uplink PDCP SDUs
after the ROHC
1526727889 L.PDCP.Tx.TotRev Number of BTS3203E LTE:

.Trf.SDU.QCI.1 transmitted V100R006C00
downlink traffic
PDCP SDUs for
services with the
QCI of 1 in a cell

downlink traffic
PDCP SDUs for
services with the
QCI of 2 in a cell

downlink traffic
PDCP SDUs for
services with the
QCI of 3 in a cell

downlink traffic
PDCP SDUs for
services with the
QCI of 4 in a cell

downlink traffic
PDCP SDUs for
services with the
QCI of 5 in a cell

BTS3203E


downlink traffic
PDCP SDUs for
services with the
QCI of 6 in a cell

downlink traffic
PDCP SDUs for
services with the
QCI of 7 in a cell

downlink traffic
PDCP SDUs for
services with the
QCI of 8 in a cell

downlink traffic
PDCP SDUs for
services with the
QCI of 9 in a cell
1526728522 L.PDCP.UL.RoHC. Compression rate of BTS3203E LTE:

HdrCompRatio headers of all uplink V100R006C00
PDCP SDUs
1526728523 L.PDCP.UL.RoHC. Compression rate of BTS3203E LTE:

PktCompRatio all uplink PDCP V100R006C00
SDUs (including
headers and
payloads) after the
ROHC.
1526730876 L.Thrp.Pkts.DL.S Number of downlink BTS3203E LTE:

RB.SDU PDCP-layer V100R011C10
signaling SDUs sent
in a cell
1526730877 L.Thrp.Pkts.UL.S Number of uplink BTS3203E LTE:

RB.SDU PDCP-layer V100R011C10
signaling SDUs
received in a cell

BTS3203E

1526730879 L.Traffic.SGW.Rx. Number of bytes of BTS3203E LTE:

SDU.Bytes SDUs that a cell V100R011C10
receives from the S-
GW
1526730880 L.Traffic.SGW.Tx. Number of bytes of BTS3203E LTE:

SDU.Bytes SDUs that a cell V100R011C10
sends to the S-GW
1526730881 L.Traffic.IntereNB. Number of bytes of BTS3203E LTE:

Transfer.Tx.SDU.B SDUs sent to target V100R011C10
ytes cells during inter-
eNodeB handovers
1526730882 L.Traffic.IntereNB. Number of bytes of BTS3203E LTE:

Transfer.Rx.SDU.B SDUs received from V100R011C10
ytes source cells during
inter-eNodeB
handovers
1526736797 L.PDCP.Tx.Disc.Tr Total number of BTS3203E LTE:

f.SDU downlink PDCP V100R011C10
SDUs discarded for
services carried on
DRBs with all QCIs
(including the QCI
for PTT services and
extended QCIs) in a
cell
1526736798 L.PDCP.Tx.TotRev Number of downlink BTS3203E LTE:

.Trf.SDU PDCP SDUs V100R011C10
transmitted for
services carried on
DRBs with all QCIs
(including the QCI
for PTT services and
extended QCIs) in a
cell

.Trf.SDU.QCI.PTT PDCP SDUs V100R011C10
transmitted for PTT
services in a cell

f.SDU.QCI.PTT PDCP SDUs V100R011C10
discarded for PTT
services in a cell

BTS3203E


.Trf.SDU.QCI.65 PDCP SDUs V100R011C10
transmitted for
services carried on
DRBs with a QCI of
65 in a cell

transmitted for
services carried on
DRBs with a QCI of
66 in a cell

transmitted for
services carried on
DRBs with a QCI of
69 in a cell

transmitted for
services carried on
DRBs with a QCI of
70 in a cell

f.SDU.QCI.65 PDCP SDUs V100R011C10
discarded for
services carried on
DRBs with a QCI of
65 in a cell

discarded for
services carried on
DRBs with a QCI of
66 in a cell

discarded for
services carried on
DRBs with a QCI of
69 in a cell

BTS3203E


discarded for
services carried on
DRBs with a QCI of
70 in a cell
1526745690 L.PDCP.UL.RoHC. Number of uplink BTS3203E LTE:

FailDecomp.VoLT VoLTE packets that V100R012C10
E fail to be
decompressed in
ROHC
1526746015 L.PDCP.UL.RoHC. Number of uplink BTS3203E LTE:

TotalDecomp.VoLT VoLTE packets that V100R012C10
E need to be
decompressed in
ROHC
L.PDCP.Tx.Disc.Trf.SDU L.PDCP.Tx.Disc.Trf.SDU.QCI.1
L.PDCP.Tx.Disc.Trf.SDU.QCI.2
L.PDCP.Tx.Disc.Trf.SDU.QCI.PTT
L.PDCP.Tx.TotRev.Trf.SDU L.PDCP.Tx.TotRev.Trf.SDU.QCI.1
L.PDCP.Tx.TotRev.Trf.SDU.QCI.2

BTS3203E
L.PDCP.Tx.TotRev.Trf.SDU.QCI.PTT
1.12.1 Number of Discarded Downlink PDCP SDUs

Counters
1526726833 L.PDCP.Tx.Dis Number of BTS3203E LTE L

c.Trf.SDU.QCI. downlink traffic
1 SDUs discarded
by the PDCP
layer for
services with
the QCI of 1 in
a cell

2 SDUs discarded
by the PDCP
layer for
services with
the QCI of 2 in
a cell

3 SDUs discarded
by the PDCP
layer for
services with
the QCI of 3 in
a cell

BTS3203E


4 SDUs discarded
by the PDCP
layer for
services with
the QCI of 4 in
a cell

5 SDUs discarded
by the PDCP
layer for
services with
the QCI of 5 in
a cell

6 SDUs discarded
by the PDCP
layer for
services with
the QCI of 6 in
a cell

7 SDUs discarded
by the PDCP
layer for
services with
the QCI of 7 in
a cell

8 SDUs discarded
by the PDCP
layer for
services with
the QCI of 8 in
a cell

BTS3203E


9 SDUs discarded
by the PDCP
layer for
services with
the QCI of 9 in
a cell
1526736797 L.PDCP.Tx.Dis Total number of BTS3203E LTE L

c.Trf.SDU downlink PDCP
SDUs discarded
for services
carried on
DRBs with all
QCIs (including
the QCI for
PTT services
and extended
QCIs) in a cell

c.Trf.SDU.QCI. downlink PDCP
PTT SDUs discarded
for PTT
services in a
cell

65 SDUs discarded
for services
carried on
DRBs with a
QCI of 65 in a
cell

66 SDUs discarded
for services
carried on
DRBs with a
QCI of 66 in a
cell

BTS3203E


69 SDUs discarded
for services
carried on
DRBs with a
QCI of 69 in a
cell

70 SDUs discarded
for services
carried on
DRBs with a
QCI of 70 in a
cell
Description
PDCP SDUs may be discarded after being received and before being sent over the air
interface. The counters measure the number of discarded downlink traffic PDCP SDUs for
Measurement Points
The corresponding counter is incremented by 1 each time a PDCP SDU is discarded before
being sent over the air interface.
Formula
None
Unit
packet
Related Features
L.PDCP.Tx.Disc.Trf.SDU.Q Multi-mode: None

CI.1 GSM: None
UMTS: None

BTS3203E

CI.2 GSM: None
UMTS: None

CI.3 GSM: None
UMTS: None

CI.4 GSM: None
UMTS: None

CI.5 GSM: None
UMTS: None

CI.6 GSM: None
UMTS: None

CI.7 GSM: None
UMTS: None

CI.8 GSM: None
UMTS: None

BTS3203E

CI.9 GSM: None
UMTS: None
L.PDCP.Tx.Disc.Trf.SDU Multi-mode: None

GSM: None
UMTS: None

CI.PTT GSM: None
UMTS: None

CI.65 GSM: None
UMTS: None

CI.66 GSM: None
UMTS: None

CI.69 GSM: None
UMTS: None

CI.70 GSM: None
UMTS: None

BTS3203E
1.12.2 Downlink ROHC Compression Rate of Headers
Counters
1526727349 L.PDCP.DL.Ro Compression BTS3203E LTE L

HC.HdrCompR rate of headers
atio of all downlink
PDCP SDUs
after the ROHC
Description
The counter measures the compression rate of headers of all downlink PDCP SDUs after the
Robust Header Compression (ROHC) in a cell. Only the PDCP SDUs whose headers are
compressed by the ROHC algorithm are measured.
Measurement Points
When ROHC is used to compress the headers of downlink PDCP SDUs to be transmitted in a
cell, the total sizes of the headers before and after compression are counted within a
measurement period. The rate of the total size of the headers after compression to the total
size of the headers before compression is used as the value of the counter. If ROHC is
disabled within a measurement period, the value of this counter is invalid.
Formula
None
Unit
%
Related Features
L.PDCP.DL.RoHC.HdrCom Multi-mode: None

pRatio GSM: None
UMTS: None
LTE: LOFD-001017 RObust Header
Compression (ROHC)

BTS3203E
1.12.3 Downlink ROHC Compression Rate
Counters
1526727350 L.PDCP.DL.Ro Compression BTS3203E LTE L

HC.PktCompRa rate of all
tio downlink PDCP
SDUs
(including
headers and
payloads) after
the ROHC
Description
The counter measures the compression rate of headers and payloads of all downlink PDCP
SDUs after the ROHC in a cell. Only the PDCP SDUs that are compressed by the ROHC
algorithm are measured.
Measurement Points
When ROHC is used to compress the headers of downlink PDCP SDUs to be transmitted in a
cell, the total sizes of the PDCP SDUs before and after compression are counted within a
measurement period. The rate of the total size of the PDCP SDUs after compression to the
total size of the PDCP SDUs before compression is used as the value of the counter. If ROHC
is disabled within a measurement period, the value of this counter is invalid.
Formula
None
Unit
%
Related Features
L.PDCP.DL.RoHC.PktCom Multi-mode: None

pRatio GSM: None
UMTS: None
Compression (ROHC)

BTS3203E
1.12.4 Decompression Failure Rate of Uplink PDCP SDUs After

the ROHC
Counters
1526727351 L.PDCP.UL.Ro Decompression BTS3203E LTE L

HC.FailDecom failure rate of
pRatio all uplink
PDCP SDUs
after the ROHC
Description
The counter measures the decompression failure rate of all uplink PDCP SDUs after the
ROHC in a cell.Only the PDCP SDUs that are compressed by the ROHC algorithm are
measured.
Disuse Statement:
The counter L.PDCP.UL.RoHC.FailDecompRatio (ID: 1526727351) will be replaced by the
counters L.PDCP.UL.RoHC.FailDecomp.VoLTE and
L.PDCP.UL.RoHC.TotalDecomp.VoLTE in later versions. In the current version, the
L.PDCP.UL.RoHC.FailDecompRatio counter value is normally reported. In later versions,
this counter will be removed. It is not recommended that the
L.PDCP.UL.RoHC.FailDecompRatio counter be used in the current version.
Measurement Points
When the received SDUs need to be decompressed by the PDCP in a cell, the ratio of the
number of SDUs that fail to be decompressed to the total number of SDUs that need to be
decompressed is sampled per second. At the end of a measurement period, the average of
these sampling results is taken as the counter value. If ROHC is disabled within a
measurement period, the counter value reported is invalid.
Formula
None
Unit
%

BTS3203E
Related Features
L.PDCP.UL.RoHC.FailDeco Multi-mode: None

mpRatio GSM: None
UMTS: None
Compression (ROHC)
1.12.5 Number of Transmitted Downlink Traffic PDCP SDUs for

DRB Services in a Cell over the Uu Interface
Counters
1526727889 L.PDCP.Tx.Tot Number of BTS3203E LTE L

Rev.Trf.SDU.Q transmitted
CI.1 downlink traffic
PDCP SDUs
for services
with the QCI of
1 in a cell

PDCP SDUs
for services
with the QCI of
2 in a cell

PDCP SDUs
for services
with the QCI of
3 in a cell

PDCP SDUs
for services
with the QCI of
4 in a cell

BTS3203E


PDCP SDUs
for services
with the QCI of
5 in a cell

PDCP SDUs
for services
with the QCI of
6 in a cell

PDCP SDUs
for services
with the QCI of
7 in a cell

PDCP SDUs
for services
with the QCI of
8 in a cell

PDCP SDUs
for services
with the QCI of
9 in a cell

BTS3203E


Rev.Trf.SDU downlink PDCP
SDUs
transmitted for
services carried
on DRBs with
all QCIs
(including the
QCI for PTT
services and
extended QCIs)
in a cell

Rev.Trf.SDU.Q downlink PDCP
CI.PTT SDUs
transmitted for
PTT services in
a cell

CI.65 SDUs
transmitted for
services carried
on DRBs with a
QCI of 65 in a
cell

CI.66 SDUs
transmitted for
services carried
on DRBs with a
QCI of 66 in a
cell

CI.69 SDUs
transmitted for
services carried
on DRBs with a
QCI of 69 in a
cell

BTS3203E


CI.70 SDUs
transmitted for
services carried
on DRBs with a
QCI of 70 in a
cell
Description
The counters measure the number of transmitted downlink traffic PDCP SDUs for DRB
Measurement Points
The number of transmitted downlink traffic PDCP SDUs for DRB services with a specific
QCI ranging from 1 to 9 is sampled per second. At the end of a measurement period, the sum
of these sampling results is used as the value of the corresponding counter.
Formula
None
Unit
packet
Related Features
L.PDCP.Tx.TotRev.Trf.SDU Multi-mode: None

.QCI.1 GSM: None
UMTS: None

.QCI.2 GSM: None
UMTS: None

BTS3203E

.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

BTS3203E

GSM: None
UMTS: None

.QCI.PTT GSM: None
UMTS: None

.QCI.65 GSM: None
UMTS: None

.QCI.66 GSM: None
UMTS: None

.QCI.69 GSM: None
UMTS: None

.QCI.70 GSM: None
UMTS: None

BTS3203E
1.12.6 Uplink ROHC Compression Rate of Headers

Counters
1526728522 L.PDCP.UL.Ro Compression BTS3203E LTE L

HC.HdrCompR rate of headers
atio of all uplink
PDCP SDUs
Description
The counter measures the decompression rate of headers of all uplink PDCP SDUs after
robust header compression (ROHC) in a cell. Only the PDCP SDUs whose headers are
compressed by the ROHC algorithm are measured.
Measurement Points
When ROHC is used to decompress the headers of uplink PDCP SDUs received in a cell, the
total sizes of the headers before and after decompression are counted within a measurement
period. The rate of the total size of the headers before decompression to the total size of the
headers after decompression is used as the value of the counter. If ROHC is disabled within a
measurement period, the value of this counter is invalid.
Formula
None
Unit
%
Related Features
L.PDCP.UL.RoHC.HdrCom Multi-mode: None

pRatio GSM: None
UMTS: None
Compression (ROHC)

BTS3203E
1.12.7 Uplink ROHC Compression Rate
Counters
1526728523 L.PDCP.UL.Ro Compression BTS3203E LTE L

HC.PktCompRa rate of all
tio uplink PDCP
SDUs
(including
headers and
payloads) after
the ROHC.
Description
The counter measures the decompression rate of headers and payloads of all downlink PDCP
SDUs after the robust header compression (ROHC) in a cell. Only the PDCP SDUs whose
headers are compressed by the ROHC algorithm are measured.
Measurement Points
When ROHC is used to decompress the headers of uplink PDCP SDUs received in a cell, the
total sizes of the PDCP SDUs before and after decompression are counted within a
measurement period. The rate of the total size of the PDCP SDUs before decompression to
the total size of the PDCP SDUs after decompression is used as the value of the counter. If
ROHC is disabled within a measurement period, the value of this counter is invalid.
Formula
None
Unit
%
Related Features
L.PDCP.UL.RoHC.PktCom Multi-mode: None

pRatio GSM: None
UMTS: None
Compression (ROHC)

BTS3203E
1.12.8 Number of PDCP-layer Signaling SDUs Sent in the

Downlink or Received in the Uplink
Counters
1526730876 L.Thrp.Pkts.DL Number of BTS3203E LTE L

.SRB.SDU downlink
PDCP-layer
signaling SDUs
sent in a cell
1526730877 L.Thrp.Pkts.UL Number of BTS3203E LTE L

.SRB.SDU uplink PDCP-
layer signaling
SDUs received
in a cell
Description
The counters measure the number of signaling SDUs received in the uplink or sent in the
downlink at the PDCP layer in a cell.
Measurement Points
The number of signaling SDUs that a cell successfully sends in the downlink or receives in
the uplink at the PDCP layer is accumulated and used as the corresponding counter value.
Formula
None
Unit
packet
Related Features
L.Thrp.Pkts.DL.SRB.SDU Multi-mode: None

GSM: None
UMTS: None

BTS3203E
L.Thrp.Pkts.UL.SRB.SDU Multi-mode: None

GSM: None
UMTS: None
1.12.9 Number of Bytes of SDUs that a Cell Receives from or

Sends to the S-GW
Counters
1526730879 L.Traffic.SGW. Number of BTS3203E LTE L

Rx.SDU.Bytes bytes of SDUs
that a cell
receives from
the S-GW
1526730880 L.Traffic.SGW. Number of BTS3203E LTE L

Tx.SDU.Bytes bytes of SDUs
that a cell sends
to the S-GW
Description
The counters measure the number of bytes of SDUs that a cell receives from or sends to the S-
GW.
Measurement Points
The number of bytes of user-plane SDUs received from or sent to the S-GW is accumulated in
a cell and used as the corresponding counter value.
Formula
None
Unit
byte

BTS3203E
Related Features
L.Traffic.SGW.Rx.SDU.Byt Multi-mode: None

es GSM: None
UMTS: None
L.Traffic.SGW.Tx.SDU.Byt Multi-mode: None

es GSM: None
UMTS: None
1.12.10 Number of Bytes of SDUs Transmitted During Inter-

eNodeB Handovers
Counters
1526730881 L.Traffic.Intere Number of BTS3203E LTE L

NB.Transfer.Tx bytes of SDUs
.SDU.Bytes sent to target
cells during
inter-eNodeB
handovers
1526730882 L.Traffic.Intere Number of BTS3203E LTE L

NB.Transfer.Rx bytes of SDUs
.SDU.Bytes received from
source cells
during inter-
eNodeB
handovers
Description
The counters measure the number of bytes of SDUs transmitted during inter-eNodeB
handovers in a cell.

BTS3203E
Measurement Points
The number of bytes of user-plane SDUs that a cell sends to the target cells or that a cell
receives from the source cells during inter-eNodeB handovers is accumulated and used as the
corresponding counter value.
Formula
None
Unit
byte
Related Features
L.Traffic.IntereNB.Transfer. Multi-mode: None

Tx.SDU.Bytes GSM: None
UMTS: None
L.Traffic.IntereNB.Transfer. Multi-mode: None

Rx.SDU.Bytes GSM: None
UMTS: None
1.12.11 Number of Uplink VoLTE Packets that Fail to Be

Decompressed by ROHC in a Cell
Counters
1526745690 L.PDCP.UL.Ro Number of BTS3203E LTE L

HC.FailDecom uplink VoLTE
p.VoLTE packets that fail
to be
decompressed
in ROHC

BTS3203E
Description
The counter measures the number of uplink QCI-1 PDCP SDUs that fail to be decompressed
at the PDCP layer in a cell. The measurement involves only PDCP SDUs that are compressed
by the ROHC algorithm.
Measurement Points
When the received uplink voice-service SDUs need to be decompressed by the PDCP in a
cell, the number of SDUs that fail to be decompressed is accumulated. If ROHC is disabled
within a measurement period, the counter value reported is invalid.
Formula
None
Unit
None
Related Features
L.PDCP.UL.RoHC.FailDeco Multi-mode: None

mp.VoLTE GSM: None
UMTS: None
Compression (ROHC)
1.12.12 Number of Uplink VoLTE Packets that Need to Be

Decompressed by ROHC in a Cell
Counters
1526746015 L.PDCP.UL.Ro Number of BTS3203E LTE L

HC.TotalDeco uplink VoLTE
mp.VoLTE packets that
need to be
decompressed
in ROHC

BTS3203E
Description
The counter measures the number of uplink QCI-1 PDCP SDUs that need to be decompressed
at the PDCP layer in a cell. The measurement involves only PDCP SDUs that are compressed
by the ROHC algorithm.
Measurement Points
When the received uplink voice-service SDUs need to be decompressed by the PDCP in a
cell, the number of SDUs that need to be decompressed is accumulated. If ROHC is disabled
within a measurement period, the counter value reported is invalid.
Formula
None
Unit
None
Related Features
L.PDCP.UL.RoHC.TotalDec Multi-mode: None

omp.VoLTE GSM: None
UMTS: None
Compression (ROHC)
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
1526726884 L.Paging.S1.Rx Number of received BTS3203E LTE:

paging messages V100R006C00
in a cell

BTS3203E

1526726885 L.Paging.UU.Att Number of UEs BTS3203E LTE:

contained in paging V100R006C00
messages
transmitted over the
Uu interface in a cell
1526726886 L.Paging.UU.Succ Number of BTS3203E LTE:

Successful Paging V100R006C00
Responses from the
UE in a Cell
1526727212 L.Paging.Dis.Num Number of BTS3203E LTE:

discarded paging V100R006C00
messages from the
MME to UEs due to
flow control in a cell
1526728337 L.Paging.UU.SIUp Number of paging BTS3203E LTE:

date messages V100R006C00
transmitted due to
system information
changes
1526728521 L.Paging.Dis.PchC Number of paging BTS3203E LTE:

ong messages discarded V100R006C00
due to paging
channel congestion
1526730140 L.Paging.UU.Succ. Number of paging BTS3203E LTE:

CSFB responses for CSFB V100R007C00
received from UEs
in a cell
1526730145 L.Paging.S1.Rx.CS Number of received BTS3203E LTE:

paging messages V100R007C00
with the IE CN
DOMAIN set to CS
in a cell
1526730562 L.Paging.UU.Num Number of paging BTS3203E LTE:

messages sent over V100R007C00
the Uu interface in a
cell
L.Paging.S1.Rx L.Paging.S1.Rx.CS

BTS3203E
1.13.1 Number of Received Paging Messages over the S1 Interface

in a Cell
Counters
1526726884 L.Paging.S1.Rx Number of BTS3203E LTE L

received paging
messages over
the S1 interface
in a cell
1526730145 L.Paging.S1.Rx Number of BTS3203E LTE L

.CS received paging
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.
Measurement Points
As shown at point A in Figure 1-138, 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-138

BTS3203E
Formula
None
Unit
None
Related Features
L.Paging.S1.Rx Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002011 Paging
L.Paging.S1.Rx.CS Multi-mode: None

GSM: None
UMTS: None
LOFD-001033 CS Fallback to UTRAN
LOFD-001034 CS Fallback to GERAN
LOFD-001035 CS Fallback to CDMA2000
1xRTT
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 BTS3203E LTE L

tt contained in
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.

BTS3203E
Measurement Points
As shown at point A in Figure 1-139, 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-139
Formula
None
Unit
None
Related Features
L.Paging.UU.Att Multi-mode: None

GSM: None
UMTS: None

BTS3203E
1.13.3 Number of Successful Paging Responses from the UE in a

Cell
Counters
1526726886 L.Paging.UU.S Number of BTS3203E LTE L

ucc Successful
Paging
Responses from
the UE in a Cell
1526730140 L.Paging.UU.S Number of BTS3203E LTE L

ucc.CSFB paging
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-140, 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.
As shown at point B in Figure 1-140, 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.

BTS3203E
Figure 1-140
Formula
None
Unit
None
Related Features
L.Paging.UU.Succ Multi-mode: None

GSM: None
UMTS: None

BTS3203E
L.Paging.UU.Succ.CSFB Multi-mode: None

GSM: None
UMTS: None
LOFD-001033 CS Fallback to UTRAN
1xRTT
1.13.4 Number of Discarded Paging Messages from the MME to

UEs in a Cell
Counters
1526727212 L.Paging.Dis.N Number of BTS3203E LTE L

um discarded
paging
messages from
the MME to
UEs due to flow
control in a cell
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

BTS3203E
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 BTS3203E LTE L

Update paging
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-141, 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-141

BTS3203E
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 BTS3203E LTE L

hCong paging
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

BTS3203E
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 BTS3203E LTE L

um paging
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-142, 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-142

BTS3203E
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-143 shows the measurement points of security mode configuration.
Figure 1-143

BTS3203E
Counters
1526727171 L.SecurMode.S1.R Number of security BTS3203E LTE:

x mode configurations V100R006C00
received over the S1
interface
1526727172 L.SecurMode.Cmd Number of security BTS3203E LTE:

mode commands V100R006C00
sent over the Uu
interface
1526727173 L.SecurMode.Cmp Number of BTS3203E LTE:

successful security V100R006C00
mode configurations
received from the
UE
1526727174 L.SecurMode.Fail Number of security BTS3203E LTE:

mode configuration V100R006C00
failures received
from the UE
None
1.14.1 Number of Security Mode Setups in a Cell

Counters
1526727171 L.SecurMode.S Number of BTS3203E LTE L

1.Rx security mode
configurations
received over
the S1 interface
1526727172 L.SecurMode.C Number of BTS3203E LTE L

md security mode
commands sent
over the Uu
interface

BTS3203E

1526727173 L.SecurMode.C Number of BTS3203E LTE L

mp successful
security mode
configurations
received from
the UE
1526727174 L.SecurMode.F Number of BTS3203E LTE L

ail security mode
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-144, 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-144, 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-144, 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-145, the L.SecurMode.Fail counter is incremented by 1 each
time the eNodeB receives a Security Mode Failure message from the UE.

BTS3203E
Figure 1-144

BTS3203E
Figure 1-145
Formula
None
Unit
None
Related Features
L.SecurMode.S1.Rx Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002004 Integrity Protection
L.SecurMode.Cmd Multi-mode: None

GSM: None
UMTS: None

BTS3203E
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
1526745746 L.RA.ExceedRadiu Number of BTS3203E LTE:

sContention.Access contention-based V100R012C10
.Num exceeding-cell-
radius accesses
1526745747 L.RA.ExceedRadiu Number of BTS3203E LTE:

sContention.Pream contention-based V100R012C10
ble.Num exceeding-cell-
radius preamble
receptions
1526745748 L.RA.ExceedRadiu Number of times a BTS3203E LTE:

sContention.Resp cell sends Random V100R012C10
Access Response
messages after
contention-based
exceeding-cell-
radius preamble
receptions

BTS3203E

1526727215 L.RA.GrpA.Att Number of times the BTS3203E LTE:

contention preamble version earlier than
in group A is V100R003C00
received
1526727216 L.RA.GrpA.Resp Number of times a BTS3203E LTE:

cell sends a Random version earlier than
Access Response V100R003C00
message after
receiving a preamble
in group A
1526727217 L.RA.GrpA.ContR Number of times the BTS3203E LTE:

esolution Contention V100R006C00
Resolution message
is sent after the
contention preamble
in group A is
received
1526727218 L.RA.GrpB.Att Number of times the BTS3203E LTE:

contention preamble version earlier than
in group B is V100R003C00
received
1526727219 L.RA.GrpB.Resp Number of times a BTS3203E LTE:

cell sends a Random version earlier than
Access Response V100R003C00
message after
receiving a preamble
in group B
1526727220 L.RA.GrpB.ContR Number of times the BTS3203E LTE:

esolution Contention V100R006C00
Resolution message
is sent after the
contention preamble
in group B is
received
1526727221 L.RA.Dedicate.Att Number of times the BTS3203E LTE:

non-contention- version earlier than
based preamble is V100R003C00
received
1526727222 L.RA.Dedicate.HO. Number of times the BTS3203E LTE:

Att non-contention- version earlier than
based preamble is V100R003C00
received (used in
handover)

BTS3203E

1526727223 L.RA.Dedicate.Res Number of times the BTS3203E LTE:

p Random Access version earlier than
Response message is V100R003C00
sent after the non-
contention-based
preamble is received

Resp Random Access version earlier than
Response message is V100R003C00
sent after the non-
contention-based
preamble is received
(used in handover)

Msg3Rcv UE Msg3 Response V100R006C00
message is received
in the handover-
triggered non-
contention-based
RA procedure
1526728913 L.RA.PreambleSen Number of random BTS3203E LTE:

tNum1 access procedures V100R006C00
with the preamble
sent by 1 time

with the preamble
sent by 2 times

with the preamble
sent by 3 times

with the preamble
sent by 4 times

tNum5or6 access procedures V100R006C00
with the preamble
sent by 5 or 6 times

with the preamble

BTS3203E


with the preamble
1526728920 L.RA.UeRaInfoRs Number of received BTS3203E LTE:

p.Num UEInformationRes- V100R006C00
ponse messages
containing RACH
information
1526728921 L.RA.UeRaInfoRs Number of received BTS3203E LTE:

pWithCon.Num UEInformationRes- V100R006C00
ponse messages
whose
"contentionDetec-
ted" is TRUE
1526728932 L.RA.GrpAandB.A Maximum number BTS3203E LTE:

tt.Max of times the V100R006C00
contention-based
preamble in group A
and group B is
received
1526728937 L.RA.Dedicate.Pre Number of times the BTS3203E LTE:

ambleReq.Num non-contention- V100R006C00
based preamble is
requested
1526728938 L.RA.Dedicate.Pre Maximum number BTS3203E LTE:

ambleReq.Num.Ma of times the non- V100R006C00
x contention-based
preamble is
requested

ambleAssign.Num non-contention- V100R006C00
based preamble is
assigned
1526728954 L.RA.GrpA.ContR Number of times the BTS3203E LTE:

esolution.PDCCH Contention V100R006C00
Resolution message
is sent on the
PDCCH after the
contention-based
preamble in group A
is received

BTS3203E

1526728955 L.RA.GrpB.ContR Number of times the BTS3203E LTE:

esolution.PDCCH Contention V100R006C00
Resolution message
is sent on the
PDCCH after the
contention-based
preamble in group B
is received
1526728956 L.RA.TA.UE.Index Number of times the BTS3203E LTE:

0 TA value is 0 or 1 V100R006C00
(index 0) in a UE-
initiated random
access procedure in
a cell

1 TA value is 2 or 3 V100R006C00
(index 1) in a UE-
initiated random
access procedure in
a cell

2 TA value is ranging V100R006C00
from 4 to 7 (index 2)
in a UE-initiated
random access
procedure in a cell

from 8 to 13 (index
3) in a UE-initiated
random access
procedure in a cell

from 14 to 25 (index
random access
procedure in a cell

random access
procedure in a cell

BTS3203E


random access
procedure in a cell

from 86 to 185
(index 7) in a UE-
initiated random
access procedure in
a cell

from 186 to 385
(index 8) in a UE-
initiated random
access procedure in
a cell

from 386 to 685
(index 9) in a UE-
initiated random
access procedure in
a cell

from 686 to 985
(index 10) in a UE-
initiated random
access procedure in
a cell

11 TA value is greater V100R006C00
than 985 (index 11)
in a UE-initiated
random access
procedure in a cell
1526730874 L.RA.GrpA.Disc.B Number of times BTS3203E LTE:

yTA.Num that the contention- V100R011C10
based preamble in
group A is discarded
based on the TA

BTS3203E

1526730875 L.RA.GrpB.Disc.B Number of times BTS3203E LTE:

yTA.Num that the contention- V100R011C10
based preamble in
group B is discarded
based on the TA

ambleReq.HO.Nu non-contention- V100R011C10
m based preamble is
requested based on a
handover

ambleAssign.HO.N non-contention- V100R011C10
um based preamble is
assigned based on a
handover
1526739751 L.RA.Dedicate.Msg Number of times the BTS3203E LTE:

3Rcv UE Msg3 Response V100R011C10
messages are
received in non-
contention-based
random access
procedures
1526742172 L.RA.GrpA.Initial Number of times BTS3203E LTE:

initially transmitted V100R011C10
contention-based
preambles in group
A are received
1526742173 L.RA.GrpB.Initial Number of times BTS3203E LTE:

initially transmitted V100R011C10
contention-based
preambles in group
B are received
1526742174 L.RA.GrpA.Initial. Number of Random BTS3203E LTE:

Resp Access Response V100R011C10
messages that a cell
sends after receiving
initially transmitted
contention-based
preambles in group
A

BTS3203E

1526742175 L.RA.GrpB.Initial. Number of Random BTS3203E LTE:

Resp Access Response V100R011C10
contention-based
preambles in group
B
1526742176 L.RA.Dedicate.Initi Number of times BTS3203E LTE:

al initially transmitted V100R011C10
non-contention-
based preambles are
received
1526742177 L.RA.Dedicate.HO. Number of times BTS3203E LTE:

Initial initially transmitted V100R011C10
handover-induced
non-contention-
based preambles are
received
1526742178 L.RA.Dedicate.Initi Number of Random BTS3203E LTE:

al.Resp Access Response V100R011C10
non-contention-
based preambles
1526742179 L.RA.Dedicate.HO. Number of Random BTS3203E LTE:

Initial.Resp Access Response V100R011C10
handover-induced
non-contention-
based preambles
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.Att L.RA.GrpA.Initial -

BTS3203E
L.RA.GrpA.Resp L.RA.GrpA.Initial.Resp -
L.RA.GrpA.ContResolution L.RA.GrpA.ContResolution. -
PDCCH
L.RA.GrpB.Att L.RA.GrpB.Initial -
L.RA.GrpB.Resp L.RA.GrpB.Initial.Resp -
L.RA.GrpB.ContResolution L.RA.GrpB.ContResolution. -
PDCCH
L.RA.Dedicate.Att L.RA.Dedicate.HO.Att L.RA.Dedicate.HO.Initial
L.RA.Dedicate.Att L.RA.Dedicate.Initial -
L.RA.Dedicate.Resp L.RA.Dedicate.HO.Resp L.RA.Dedicate.HO.Initial.R

esp
L.RA.Dedicate.Resp L.RA.Dedicate.Initial.Resp -
L.RA.UeRaInfoRsp.Num L.RA.UeRaInfoRspWith- -
Con.Num
L.RA.Dedicate.Msg3Rcv L.RA.Dedicate.HO.Msg3Rc -
v
1.15.1 Number of Exceeding-Cell-Radius Random Accesses

Counters
1526745746 L.RA.ExceedR Number of BTS3203E LTE L

adiusContentio contention-
n.Access.Num based
exceeding-cell-
radius accesses
Description
The counter measures the number of exceeding-cell-radius random accesses in a cell. The
signaling flows involved in the counter(s) comply with section 10.1.5 in 3GPP TS 36.300
V10.6.0.

BTS3203E
Measurement Points
As shown at point A in Figure 1-146, the L.RA.ExceedRadiusContention.Access.Num
counter is incremented by 1 each time the eNodeB receives a Msg3 from the UE during a
contention-based exceeding-cell-radius access.
Figure 1-146
Formula
None
Unit
None
Related Features
L.RA.ExceedRadiusConten- Multi-mode: None

tion.Access.Num GSM: None
UMTS: None
LTE: LBFD-002010 Random Access Procedure

BTS3203E
1.15.2 Number of Times the Contention Preamble Is Received
Counters

adiusContentio contention-
n.Preamble.Nu based
m exceeding-cell-
radius preamble
receptions
1526727215 L.RA.GrpA.Att Number of BTS3203E LTE L

times the
contention
preamble in
group A is
received
1526727218 L.RA.GrpB.Att Number of BTS3203E LTE L

times the
contention
preamble in
group B is
received
1526728932 L.RA.GrpAand Maximum BTS3203E LTE L

B.Att.Max number of
times the
contention-
based preamble
in group A and
group B is
received
1526742172 L.RA.GrpA.Init Number of BTS3203E LTE L

ial times initially
transmitted
contention-
based
preambles in
group A are
received
1526742173 L.RA.GrpB.Init Number of BTS3203E LTE L

ial times initially
transmitted
contention-
based
preambles in
group B are
received

BTS3203E
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-147, 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 L.RA.GrpA.Initial counter is incremented by 1 if the preamble is an initially transmitted
contention-based preamble and belongs to group A.
The L.RA.GrpB.Initial counter is incremented by 1 if the preamble is an initially transmitted
contention-based preamble and belongs to group B.
The L.RA.ExceedRadiusContention.Preamble.Num counter is incremented by 1 if the
preamble is used in a contention-based exceeding-cell-radius access.
The number of contention-based preambles that a cell receives is sampled per second. At the
end of a measurement period, the maximum of these sampling results is taken as the value of
the L.RA.GrpAandB.Att.Max counter.

BTS3203E
Figure 1-147
Formula
None
Unit
None
Related Features

tion.Preamble.Num GSM: None
UMTS: None
L.RA.GrpA.Att Multi-mode: None

GSM: None
UMTS: None
L.RA.GrpB.Att Multi-mode: None

GSM: None
UMTS: None

BTS3203E
L.RA.GrpAandB.Att.Max Multi-mode: None

GSM: None
UMTS: None
L.RA.GrpA.Initial Multi-mode: None

GSM: None
UMTS: None
L.RA.GrpB.Initial Multi-mode: None

GSM: None
UMTS: None
1.15.3 Number of Random Access Response Messages that a Cell

Sends after Receiving Contention-based Preambles
Counters

adiusContentio times a cell
n.Resp sends Random
Access
Response
messages after
contention-
based
exceeding-cell-
radius preamble
receptions
1526727216 L.RA.GrpA.Res Number of BTS3203E LTE L

p times a cell
sends a
Random Access
Response
message after
receiving a
preamble in
group A

BTS3203E

1526727219 L.RA.GrpB.Res Number of BTS3203E LTE L

p times a cell
sends a
Random Access
Response
message after
receiving a
preamble in
group B
1526742174 L.RA.GrpA.Init Number of BTS3203E LTE L

ial.Resp Random Access
Response
messages that a
cell sends after
receiving
initially
transmitted
contention-
based
preambles in
group A
1526742175 L.RA.GrpB.Init Number of BTS3203E LTE L

ial.Resp Random Access
Response
messages that a
cell sends after
receiving
initially
transmitted
contention-
based
preambles 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.

BTS3203E
Measurement Points
As shown at point B in Figure 1-148, the corresponding counter is incremented by 1 each
time the eNodeB sends a Random Access Response message to a UE after receiving a
Random Access Preamble message from the UE. The counters are measured as follows:
The L.RA.GrpA.Resp counter is incremented by 1 if the preamble is a contention-based
preamble and belongs to group A.
The L.RA.GrpB.Resp counter is incremented by 1 if the preamble is a contention-based
preamble and belongs to group B.
The L.RA.GrpA.Initial.Resp counter is incremented by 1 if the preamble is an initially
transmitted contention-based preamble and belongs to group A.
The L.RA.GrpA.Initial.Resp counter is incremented by 1 if the preamble is an initially
transmitted contention-based preamble and belongs to group B.
The L.RA.ExceedRadiusContention.Resp counter is incremented by 1 if the preamble is used
in a contention-based exceeding-cell-radius access.
Figure 1-148
Formula
None
Unit
None

BTS3203E
Related Features

tion.Resp GSM: None
UMTS: None
L.RA.GrpA.Resp Multi-mode: None

GSM: None
UMTS: None
L.RA.GrpB.Resp Multi-mode: None

GSM: None
UMTS: None
L.RA.GrpA.Initial.Resp Multi-mode: None

GSM: None
UMTS: None
L.RA.GrpB.Initial.Resp Multi-mode: None

GSM: None
UMTS: None

BTS3203E
1.15.4 Number of Times the Contention Resolution Message Is

Sent After the Contention Preamble Is Received
Counters
1526727217 L.RA.GrpA.Co Number of BTS3203E LTE L

ntResolution times the
Contention
Resolution
message is sent
after the
contention
preamble in
group A is
received
1526727220 L.RA.GrpB.Co Number of BTS3203E LTE L

ntResolution times the
Contention
Resolution
message is sent
after the
contention
preamble in
group B is
received
1526728954 L.RA.GrpA.Co Number of BTS3203E LTE L

ntResolution.P times the
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 BTS3203E LTE L

ntResolution.P times the
DCCH Contention
Resolution
message is sent
on the PDCCH
after the
contention-
based preamble
in group B is
received

BTS3203E
Description
The counters measure the number of times the Contention Resolution message is sent after the
contention preamble in group A or group B is received. They indicate the success rate of the
contention RA procedure.
Measurement Points
As shown at point C in Figure 1-149, 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.

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-149
Formula
None

BTS3203E
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.5 Number of Times the Non-Contention-Based Preamble Is

Received
Counters
1526727221 L.RA.Dedicate. Number of BTS3203E LTE L

Att times the non-
contention-
based preamble
is received

BTS3203E


HO.Att times the non-
contention-
based preamble
is received
(used in
handover)

Initial times initially
transmitted
non-contention-
based
preambles are
received

HO.Initial times initially
transmitted
handover-
induced non-
contention-
based
preambles are
received
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-150, 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.Dedicate.Att counter is incremented by 1 if the preamble is a non-contention-based

preamble.
The L.RA.Dedicate.HO.Att counter is incremented by 1 if the preamble is a non-contention-

based preamble that is used for a handover.

BTS3203E
The L.RA.Dedicate.Initial counter is incremented by 1 if the preamble is an initially

transmitted non-contention-based preamble.
The L.RA.Dedicate.HO.Initial counter is incremented if by 1 if the preamble is an initially
transmitted non-contention-based preamble that is used for a handover.
Figure 1-150
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

BTS3203E
L.RA.Dedicate.Initial Multi-mode: None

GSM: None
UMTS: None
L.RA.Dedicate.HO.Initial Multi-mode: None

GSM: None
UMTS: None
1.15.6 Number of Random Access Response Messages that a Cell

Sends after Receiving Non-contention-based Preambles
Counters

Resp times the
Random Access
Response
message is sent
after the non-
contention-
based preamble
is received

HO.Resp times the
Random Access
Response
message is sent
after the non-
contention-
based preamble
is received
(used in
handover)

BTS3203E


Initial.Resp Random Access
Response
messages that a
cell sends after
receiving
initially
transmitted
non-contention-
based
preambles

HO.Initial.Resp Random Access
Response
messages that a
cell sends after
receiving
handover-
induced initially
transmitted
non-contention-
based
preambles
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-151, the corresponding counter is increment by 1 each time
the eNodeB sends a Random Access Response message to a UE after receiving a Random
Access Preamble message from the UE. The counters are measured as follows:
The L.RA.Dedicate.Resp counter is incremented by 1 if the preamble is a non-contention-
based preamble.
The L.RA.Dedicate.HO.Resp counter is incremented by 1 if the preamble is a non-contention-
based preamble that is used for a handover.
The L.RA.Dedicate.Initial.Resp counter is incremented by 1 if the preamble is an initially
transmitted non-contention-based preamble.

BTS3203E
The L.RA.Dedicate.HO.Initial.Resp counter is incremented if by 1 if the preamble is an

initially transmitted non-contention-based preamble that is used for a handover.
Figure 1-151
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
L.RA.Dedicate.Initial.Resp Multi-mode: None

GSM: None
UMTS: None

BTS3203E
L.RA.Dedicate.HO.Initial.R Multi-mode: None

esp GSM: None
UMTS: None
1.15.7 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
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.
Measurement Points
As shown at point D in Figure 1-152, 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.

BTS3203E
Figure 1-152
Formula
None
Unit
None
Related Features
L.RA.Dedicate.HO.Msg3Rc Multi-mode: None

v GSM: None
UMTS: None
1.15.8 Number of Random Access Procedures
Counters
1526728913 L.RA.Preamble Number of BTS3203E LTE L

SentNum1 random access
procedures with
the preamble
sent by 1 time

BTS3203E


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
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 BTS3203E LTE L

Rsp.Num received
UEInformation
Response
messages
containing
RACH
information

BTS3203E

1526728921 L.RA.UeRaInfo Number of BTS3203E LTE L

RspWithCon.N received
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.
Measurement Points
As shown at point A in Figure 1-153, 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.

BTS3203E
If the value of the "contentionDetected" IE in the message is TRUE, the

L.RA.UeRaInfoRspWithCon.Num counter is incremented by 1.
Figure 1-153
Formula
None
Unit
None
Related Features
L.RA.PreambleSentNum1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

BTS3203E

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.9 Number of Times the Non-Contention-based Preamble is

Requested
Counters

PreambleReq.N times the non-
um contention-
based preamble
is requested

BTS3203E

1526728938 L.RA.Dedicate. Maximum BTS3203E LTE L

PreambleReq.N number of
um.Max times the non-
contention-
based preamble
is requested

PreambleReq.H times the non-
O.Num contention-
based preamble
is requested
based on a
handover
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

BTS3203E
Related Features
L.RA.Dedicate.PreambleRe Multi-mode: None

q.Num GSM: None
UMTS: None

q.Num.Max GSM: None
UMTS: None

q.HO.Num GSM: None
UMTS: None
1.15.10 Number of Times the Non-Contention-based Preamble is

Assigned
Counters

PreambleAssig times the non-
n.Num contention-
based preamble
is assigned

PreambleAssig times the non-
n.HO.Num contention-
based preamble
is assigned
based on a
handover
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

BTS3203E
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
L.RA.Dedicate.PreambleAs Multi-mode: None

sign.HO.Num GSM: None
UMTS: None
1.15.11 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 BTS3203E LTE L

dex0 times the TA
value is 0 or 1
(index 0) in a
UE-initiated
random access
procedure in a
cell

BTS3203E


dex1 times the TA
value is 2 or 3
(index 1) in a
UE-initiated
random access
procedure in a
cell

dex2 times the TA
value is ranging
from 4 to 7
(index 2) in a
UE-initiated
random access
procedure in a
cell

dex3 times the TA
value is ranging
from 8 to 13
(index 3) in a
UE-initiated
random access
procedure in a
cell

dex4 times the TA
value is ranging
from 14 to 25
(index 4) in a
UE-initiated
random access
procedure in a
cell

dex5 times the TA
value is ranging
from 26 to 45
(index 5) in a
UE-initiated
random access
procedure in a
cell

BTS3203E


dex6 times the TA
value is ranging
from 46 to 85
(index 6) in a
UE-initiated
random access
procedure in a
cell

dex7 times the TA
value is ranging
from 86 to 185
(index 7) in a
UE-initiated
random access
procedure in a
cell

dex8 times the TA
value is ranging
from 186 to 385
(index 8) in a
UE-initiated
random access
procedure in a
cell

dex9 times the TA
value is ranging
from 386 to 685
(index 9) in a
UE-initiated
random access
procedure in a
cell

dex10 times the TA
value is ranging
from 686 to 985
(index 10) in a
UE-initiated
random access
procedure in a
cell

BTS3203E


dex11 times the TA
value is greater
than 985 (index
11) in a UE-
initiated
random access
procedure in a
cell
Description
The counters measure the number of times the TA with a specific value range contained in the
Random Access Response message in a UE-initiated random access procedure in a cell. One
TA equals 0.52 microsecond.
Measurement Points
In a UE-initiated random access procedure, when the eNodeB sends a Random Access
Response (RAR) message to the UE after receiving a Random Access Preamble message, the
corresponding counter is incremented based on the TA value contained in the RAR message
each time the eNodeB receives the first uplink data packet that passes the cyclic redundancy
check (CRC).
Formula
None
Unit
None
Related Features
L.RA.TA.UE.Index0 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

BTS3203E

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

BTS3203E

GSM: None
UMTS: None
1.15.12 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 BTS3203E LTE L

c.ByTA.Num times that the
contention-
based preamble
in group A is
discarded based
on the TA
Description
Assume that the eNodeB receives a contention-based preamble from a UE and the distance
between the UE and the eNodeB is greater than the cell radius. When the eNodeB receives an
RRC Connection Request message from the UE, the eNodeB sends an RRC Connection
Reject message to the UE. The counter measures the number of rejected exceeding-cell-radius
UE access requests with group-A preambles in a cell.
Measurement Points
As shown at point A in Figure 1-154, 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.

BTS3203E
Figure 1-154
Formula
None
Unit
None
Related Features
L.RA.GrpA.Disc.ByTA.Nu Multi-mode: None

m GSM: None
UMTS: None

BTS3203E
1.15.13 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 BTS3203E LTE L

c.ByTA.Num times that the
contention-
based preamble
in group B is
discarded based
on the TA
Description
Assume that the eNodeB receives a contention-based preamble from a UE and the distance
between the UE and the eNodeB is greater than the cell radius. When the eNodeB receives an
RRC Connection Request message from the UE, the eNodeB sends an RRC Connection
Reject message to the UE. The counter measures the number of rejected exceeding-cell-radius
UE access requests with group-B preambles in a cell.
Measurement Points
As shown at point A in Figure 1-155, 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-155

BTS3203E
Formula
None
Unit
None
Related Features
L.RA.GrpB.Disc.ByTA.Nu Multi-mode: None

m GSM: None
UMTS: None
1.15.14 Number of Times the UE Msg3 Response Messages are

Received in Non-Contention-based Random Access Procedures
Counters

Msg3Rcv times the UE
Msg3 Response
messages are
received in non-
contention-
based random
access
procedures
Description
The counters measure the number of times the UE Msg3 Response messages are received in
non-contention-based random access procedures and the number of times the UE Msg3
Response messages are received in handover-triggered non-contention-based random access
procedures. The counters are used to evaluate the success rate of non-contention-based
random access and handover-triggered non-contention-based random access.
V10.6.0.

BTS3203E
Measurement Points
As shown at point D in Figure 1-156, the L.RA.Dedicate.Msg3Rcv counter is incremented by
1 each time the eNodeB receives a UE Msg3 Response message from a UE in a non-
contention-based random access procedure. In addition, if the random access procedure is
triggered by a handover, the L.RA.Dedicate.HO.Msg3Rcv is incremented by 1.
Figure 1-156
Formula
None
Unit
None
Related Features
L.RA.Dedicate.Msg3Rcv Multi-mode: None

GSM: None
UMTS: None

BTS3203E
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
1526727388 L.DLPwr.Max Maximum downlink BTS3203E LTE:

transmit power in a V100R006C00
cell
1526727389 L.DLPwr.Avg Average downlink BTS3203E LTE:

transmit power in a V100R006C00
cell
1526728297 L.UL.Interference. Maximum uplink BTS3203E LTE:

Max interference and V100R006C00
noise received by
each PRB in a cell
1526728298 L.UL.Interference. Average uplink BTS3203E LTE:

Avg interference and V100R006C00
noise received by
each PRB in a cell
1526728435 L.UL.Interference. Minimum uplink BTS3203E LTE:

Min interference and V100R006C00
noise received by
each PRB in a cell
1526732045 L.UL.RSSI.PUCC Number of times BTS3203E LTE:

H.Index0 that the eNodeB V100R006C00
detects a PRB-level
average RSSI with
the index of 0 (RSSI
≤ -120 dBm) on the
PUCCH

detects a PRB-level
average RSSI with
the index of 1 (-120
dBm < RSSI ≤ -118
dBm) on the
PUCCH

BTS3203E


detects a PRB-level
average RSSI with
dBm < RSSI ≤ -116
dBm) on the
PUCCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -114
dBm) on the
PUCCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -112
dBm) on the
PUCCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -110
dBm) on the
PUCCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -108
dBm) on the
PUCCH

BTS3203E


detects a PRB-level
average RSSI with
dBm < RSSI ≤ -106
dBm) on the
PUCCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -104
dBm) on the
PUCCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -102
dBm) on the
PUCCH

detects a PRB-level
average RSSI with
the index of 10
(-102 dBm < RSSI ≤
-100 dBm) on the
PUCCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -98
dBm) on the
PUCCH

BTS3203E


detects a PRB-level
average RSSI with
dBm < RSSI ≤ -96
dBm) on the
PUCCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -94
dBm) on the
PUCCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -92
dBm) on the
PUCCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -90
dBm) on the
PUCCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -88
dBm) on the
PUCCH

BTS3203E


detects a PRB-level
average RSSI with
dBm < RSSI ≤ -86
dBm) on the
PUCCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -84
dBm) on the
PUCCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -82
dBm) on the
PUCCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -80
dBm) on the
PUCCH

detects a PRB-level
average RSSI with
the index of 21
(RSSI > -80 dBm)
on the PUCCH
1526732067 L.UL.RSSI.PUSCH Number of times BTS3203E LTE:

.Index0 that the eNodeB V100R006C00
detects a PRB-level
average RSSI with
the index of 0 (RSSI
PUSCH

BTS3203E


detects a PRB-level
average RSSI with
dBm < RSSI ≤ - 118
dBm) on the
PUSCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -116
dBm) on the
PUSCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -114
dBm) on the
PUSCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -112
dBm) on the
PUSCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -110
dBm) on the
PUSCH

BTS3203E


detects a PRB-level
average RSSI with
dBm < RSSI ≤ -108
dBm) on the
PUSCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -106
dBm) on the
PUSCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -104
dBm) on the
PUSCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -102
dBm) on the
PUSCH

detects a PRB-level
average RSSI with
the index of 10
(-102 dBm < RSSI ≤
-100 dBm) on the
PUSCH

BTS3203E


detects a PRB-level
average RSSI with
dBm < RSSI ≤ -98
dBm) on the
PUSCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -96
dBm) on the
PUSCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -94
dBm) on the
PUSCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -92
dBm) on the
PUSCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -90
dBm) on the
PUSCH

BTS3203E


detects a PRB-level
average RSSI with
dBm < RSSI ≤ -88
dBm) on the
PUSCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -86
dBm) on the
PUSCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -84
dBm) on the
PUSCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -82
dBm) on the
PUSCH

detects a PRB-level
average RSSI with
dBm < RSSI ≤ -80
dBm) on the
PUSCH

BTS3203E


detects a PRB-level
average RSSI with
the index of 21
(RSSI > -80 dBm)
on the PUSCH
1526734045 L.UL.Interference. Number of times BTS3203E LTE:

PUSCH.Index0 that the eNodeB V100R006C00
detects a PRB-level
IN with the index of
0 (IN ≤ -121 dBm)
on the PUSCH

detects a PRB-level
1 (-121 dBm < RSSI
PUSCH

detects a PRB-level
2 (-120 dBm < IN ≤
-119 dBm) on the
PUSCH

detects a PRB-level
3 (-119 dBm < IN ≤
-118 dBm) on the
PUSCH

detects a PRB-level
4 (-118 dBm < IN ≤
-117 dBm) on the
PUSCH

BTS3203E


detects a PRB-level
5 (-117 dBm < IN ≤
-116 dBm) on the
PUSCH

detects a PRB-level
6 (-116 dBm < IN ≤
-115 dBm) on the
PUSCH

detects a PRB-level
7 (-115 dBm < IN ≤
-114 dBm) on the
PUSCH

detects a PRB-level
8 (-114 dBm < IN ≤
-113 dBm) on the
PUSCH

detects a PRB-level
9 (-113 dBm < IN ≤
-112 dBm) on the
PUSCH

detects a PRB-level
10 (-112 dBm < IN
PUSCH

BTS3203E


detects a PRB-level
11 (-108 dBm < IN
PUSCH

detects a PRB-level
12 (-104 dBm < IN
PUSCH

detects a PRB-level
13 (-100 dBm < IN
≤ -96 dBm) on the
PUSCH

detects a PRB-level
14 (-96 dBm < IN ≤
-92 dBm) on the
PUSCH

detects a PRB-level
15 (IN > -92 dBm)
on the PUSCH

PUCCH.Index0 that the eNodeB V100R006C00
detects a PRB-level
0 (IN ≤ -121 dBm)
on the PUCCH

BTS3203E


detects a PRB-level
1 (-121 dBm < IN ≤
-120 dBm) on the
PUCCH

detects a PRB-level
2 (-120 dBm < IN ≤
-119 dBm) on the
PUCCH

detects a PRB-level
3 (-119 dBm < IN ≤
-118 dBm) on the
PUCCH

detects a PRB-level
4 (-118 dBm < IN ≤
-117 dBm) on the
PUCCH

detects a PRB-level
5 (-117 dBm < IN ≤
-116 dBm) on the
PUCCH

detects a PRB-level
6 (-116 dBm < IN ≤
-115 dBm) on the
PUCCH

BTS3203E


detects a PRB-level
7 (-115 dBm < IN ≤
-114 dBm) on the
PUCCH

detects a PRB-level
8 (-114 dBm < IN ≤
-113 dBm) on the
PUCCH

detects a PRB-level
9 (-113 dBm < IN ≤
-112 dBm) on the
PUCCH

detects a PRB-level
10 (-112 dBm < IN
PUCCH

detects a PRB-level
11 (-108 dBm < IN
PUCCH

detects a PRB-level
12 (-104 dBm < IN
PUCCH

BTS3203E


detects a PRB-level
13 (-100 dBm < IN
≤ -96 dBm) on the
PUCCH

detects a PRB-level
14 (-96 dBm < IN ≤
-92 dBm) on the
PUCCH

detects a PRB-level
15 (IN > -92 dBm)
on the PUCCH

PRACH.Index0 that the eNodeB V100R006C00
detects a PRB-level
average IN with the
index of 0 (IN ≤
-121 dBm) on the
PRACH

detects a PRB-level
average IN with the
index of 1 (-121
dBm < RSSI ≤ -120
dBm) on the
PRACH

detects a PRB-level
average IN with the
index of 2 (-120
dBm < IN ≤ -119
dBm) on the
PRACH

BTS3203E


detects a PRB-level
average IN with the
index of 3 (-119
dBm < IN ≤ -118
dBm) on the
PRACH

detects a PRB-level
average IN with the
index of 4 (-118
dBm < IN ≤ -117
dBm) on the
PRACH

detects a PRB-level
average IN with the
index of 5 (-117
dBm < IN ≤ -116
dBm) on the
PRACH

detects a PRB-level
average IN with the
index of 6 (-116
dBm < IN ≤ -115
dBm) on the
PRACH

detects a PRB-level
average IN with the
index of 7 (-115
dBm < IN ≤ -114
dBm) on the
PRACH

BTS3203E


detects a PRB-level
average IN with the
index of 8 (-114
dBm < IN ≤ -113
dBm) on the
PRACH

detects a PRB-level
average IN with the
index of 9 (-113
dBm < IN ≤ -112
dBm) on the
PRACH

detects a PRB-level
average IN with the
index of 10 (-112
dBm < IN ≤ -108
dBm) on the
PRACH

detects a PRB-level
average IN with the
index of 11 (-108
dBm < IN ≤ -104
dBm) on the
PRACH

detects a PRB-level
average IN with the
index of 12 (-104
dBm < IN ≤ -100
dBm) on the
PRACH

BTS3203E


detects a PRB-level
average IN with the
index of 13 (-100
dBm < IN ≤ -96
dBm) on the
PRACH

detects a PRB-level
average IN with the
index of 14 (-96
dBm < IN ≤ -92
dBm) on the
PRACH

detects a PRB-level
average IN with the
index of 15 (IN >
-92 dBm) on the
PRACH
1526734093 L.UL.RSRP.PUSC Number of times BTS3203E LTE:

detects a UE-level
RSRP with the index
of 0 (RSRP ≤ -146
dBm) on the
PUSCH

detects a UE-level
RSRP with the index
of 1 (-146 dBm <
RSRP ≤ -144 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 2 (-144 dBm <
RSRP ≤ -142 dBm)
on the PUSCH

BTS3203E


detects a UE-level
RSRP with the index
of 3 (-142 dBm <
RSRP ≤ -140 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 4 (-140 dBm <
RSRP ≤ -138 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 5 (-138 dBm <
RSRP ≤ -136 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 6 (-136 dBm <
RSRP ≤ -134 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 7 (-134 dBm <
RSRP ≤ -132 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 8 (-132 dBm <
RSRP ≤ -130 dBm)
on the PUSCH

BTS3203E


detects a UE-level
RSRP with the index
of 9 (-130 dBm <
RSRP ≤ -128 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 10 (-128 dBm <
RSRP ≤ -126 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 11 (-126 dBm <
RSRP ≤ -124 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 12 (-124 dBm <
RSRP ≤ -122 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 13 (-122 dBm <
RSRP ≤ -120 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 14 (-120 dBm <
RSRP ≤ -118 dBm)
on the PUSCH

BTS3203E


detects a UE-level
RSRP with the index
of 15 (-118 dBm <
RSRP ≤ -116 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 16 (-116 dBm <
RSRP ≤ -114 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 17 (-114 dBm <
RSRP ≤ -112 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 18 (-112 dBm <
RSRP ≤ -110 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 19 (-110 dBm <
RSRP ≤ -105 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 20 (-105 dBm <
RSRP ≤ -100 dBm)
on the PUSCH

BTS3203E


detects a UE-level
RSRP with the index
of 21 (-100 dBm <
RSRP ≤ -95 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 22 (-95 dBm <
RSRP ≤ -90 dBm)
on the PUSCH

detects a UE-level
RSRP with the index
of 23 (RSRP > -90
dBm) on the
PUSCH
1526734117 L.UL.RSRP.PUCC Number of times BTS3203E LTE:

detects a UE-level
RSRP with the index
of 0 (RSRP ≤ -146
dBm) on the
PUCCH

detects a UE-level
RSRP with the index
of 1 (-146 dBm <
RSRP ≤ -144 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 2 (-144 dBm <
RSRP ≤ -142 dBm)
on the PUCCH

BTS3203E


detects a UE-level
RSRP with the index
of 3 (-142 dBm <
RSRP ≤ -140 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 4 (-140 dBm <
RSRP ≤ -138 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 5 (-138 dBm <
RSRP ≤ -136 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 6 (-136 dBm <
RSRP ≤ -134 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 7 (-134 dBm <
RSRP ≤ -132 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 8 (-132 dBm <
RSRP ≤ -130 dBm)
on the PUCCH

BTS3203E


detects a UE-level
RSRP with the index
of 9 (-130 dBm <
RSRP ≤ -128 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 10 (-128 dBm <
RSRP ≤ -126 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 11 (-126 dBm <
RSRP ≤ -124 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 12 (-124 dBm <
RSRP ≤ -122 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 13 (-122 dBm <
RSRP ≤ -120 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 14 (-120 dBm <
RSRP ≤ -118 dBm)
on the PUCCH

BTS3203E


detects a UE-level
RSRP with the index
of 15 (-118 dBm <
RSRP ≤ -116 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 16 (-116 dBm <
RSRP ≤ -114 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 17 (-114 dBm <
RSRP ≤ -112 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 18 (-112 dBm <
RSRP ≤ -110 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 19 (-110 dBm <
RSRP ≤ -105 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 20 (-105 dBm <
RSRP ≤ -100 dBm)
on the PUCCH

BTS3203E


detects a UE-level
RSRP with the index
of 21 (-100 dBm <
RSRP ≤ -95 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 22 (-95 dBm <
RSRP ≤ -90 dBm)
on the PUCCH

detects a UE-level
RSRP with the index
of 23 (RSRP > -90
dBm) on the
PUCCH
1526743709 L.UL.Interference. Linear average value BTS3203E LTE:

LinearAvg of PRB-level V100R012C00
interference noise
detected in the
uplink
None
1.16.1 Downlink Transmit Power

Counters
1526727388 L.DLPwr.Max Maximum BTS3203E LTE L

downlink
transmit power
in a cell

BTS3203E

1526727389 L.DLPwr.Avg Average BTS3203E LTE L

downlink
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. 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.
Formula
None
Unit
dBm
Related Features
L.DLPwr.Max Multi-mode: None

GSM: None
UMTS: None
L.DLPwr.Avg Multi-mode: None

GSM: None
UMTS: None

BTS3203E
1.16.2 Interference and Noise Received by Each PRB in a Cell

Counters
1526728297 L.UL.Interferen Maximum BTS3203E LTE L

ce.Max uplink
interference and
noise received
by each PRB in
a cell
1526728298 L.UL.Interferen Average uplink BTS3203E LTE L

ce.Avg interference and
noise received
by each PRB in
a cell
1526728435 L.UL.Interferen Minimum BTS3203E LTE L

ce.Min uplink
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.
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

BTS3203E
Related Features
L.UL.Interference.Max Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002003 Physical Channel
Management
L.UL.Interference.Avg Multi-mode: None

GSM: None
UMTS: None
Management
L.UL.Interference.Min Multi-mode: None

GSM: None
UMTS: None
Management
1.16.3 Distribution of RSSIs on the PUCCH

Counters
1526732045 L.UL.RSSI.PU Number of BTS3203E LTE L

CCH.Index0 times that the
eNodeB detects
a PRB-level
average RSSI
with the index
of 0 (RSSI ≤
-120 dBm) on
the PUCCH

BTS3203E


eNodeB detects
a PRB-level
average RSSI
with the index
of 1 (-120 dBm
< RSSI ≤ -118
dBm) on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 2 (-118 dBm
< RSSI ≤ -116
dBm) on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 3 (-116 dBm
< RSSI ≤ -114
dBm) on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 4 (-114 dBm
< RSSI ≤ -112
dBm) on the
PUCCH

BTS3203E


eNodeB detects
a PRB-level
average RSSI
with the index
of 5 (-112 dBm
< RSSI ≤ -110
dBm) on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 6 (-110 dBm
< RSSI ≤ -108
dBm) on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 7 (-108 dBm
< RSSI ≤ -106
dBm) on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 8 (-106 dBm
< RSSI ≤ -104
dBm) on the
PUCCH

BTS3203E


eNodeB detects
a PRB-level
average RSSI
with the index
of 9 (-104 dBm
< RSSI ≤ -102
dBm) on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 10 (-102
dBm < RSSI ≤
-100 dBm) on
the PUCCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 11 (-100
dBm < RSSI ≤
-98 dBm) on
the PUCCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 12 (-98 dBm
< RSSI ≤ -96
dBm) on the
PUCCH

BTS3203E


eNodeB detects
a PRB-level
average RSSI
with the index
of 13 (-96 dBm
< RSSI ≤ -94
dBm) on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 14 (-94 dBm
< RSSI ≤ -92
dBm) on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 15 (-92 dBm
< RSSI ≤ -90
dBm) on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 16 (-90 dBm
< RSSI ≤ -88
dBm) on the
PUCCH

BTS3203E


eNodeB detects
a PRB-level
average RSSI
with the index
of 17 (-88 dBm
< RSSI ≤ -86
dBm) on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 18 (-86 dBm
< RSSI ≤ -84
dBm) on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 19 (-84 dBm
< RSSI ≤ -82
dBm) on the
PUCCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 20 (-82 dBm
< RSSI ≤ -80
dBm) on the
PUCCH

BTS3203E


eNodeB detects
a PRB-level
average RSSI
with the index
of 21 (RSSI >
-80 dBm) on
the PUCCH
Description
The counters measure the distribution of received signal strength indicators (RSSIs) on the
PUCCH in a cell.
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. 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
Management

BTS3203E

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

BTS3203E

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

0 GSM: None
UMTS: None
Management

1 GSM: None
UMTS: None
Management

2 GSM: None
UMTS: None
Management

3 GSM: None
UMTS: None
Management

4 GSM: None
UMTS: None
Management

BTS3203E

5 GSM: None
UMTS: None
Management

6 GSM: None
UMTS: None
Management

7 GSM: None
UMTS: None
Management

8 GSM: None
UMTS: None
Management

9 GSM: None
UMTS: None
Management

0 GSM: None
UMTS: None
Management

1 GSM: None
UMTS: None
Management

BTS3203E
1.16.4 Distribution of RSSIs on the PUSCH

Counters

SCH.Index0 times that the
eNodeB detects
a PRB-level
average RSSI
with the index
of 0 (RSSI ≤
-120 dBm) on
the PUSCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 1 (-120 dBm
< RSSI ≤ - 118
dBm) on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 2 (-118 dBm
< RSSI ≤ -116
dBm) on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 3 (-116 dBm
< RSSI ≤ -114
dBm) on the
PUSCH

BTS3203E


eNodeB detects
a PRB-level
average RSSI
with the index
of 4 (-114 dBm
< RSSI ≤ -112
dBm) on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 5 (-112 dBm
< RSSI ≤ -110
dBm) on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 6 (-110 dBm
< RSSI ≤ -108
dBm) on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 7 (-108 dBm
< RSSI ≤ -106
dBm) on the
PUSCH

BTS3203E


eNodeB detects
a PRB-level
average RSSI
with the index
of 8 (-106 dBm
< RSSI ≤ -104
dBm) on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 9 (-104 dBm
< RSSI ≤ -102
dBm) on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 10 (-102
dBm < RSSI ≤
-100 dBm) on
the PUSCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 11 (-100
dBm < RSSI ≤
-98 dBm) on
the PUSCH

BTS3203E


eNodeB detects
a PRB-level
average RSSI
with the index
of 12 (-98 dBm
< RSSI ≤ -96
dBm) on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 13 (-96 dBm
< RSSI ≤ -94
dBm) on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 14 (-94 dBm
< RSSI ≤ -92
dBm) on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 15 (-92 dBm
< RSSI ≤ -90
dBm) on the
PUSCH

BTS3203E


eNodeB detects
a PRB-level
average RSSI
with the index
of 16 (-90 dBm
< RSSI ≤ -88
dBm) on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 17 (-88 dBm
< RSSI ≤ -86
dBm) on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 18 (-86 dBm
< RSSI ≤ -84
dBm) on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 19 (-84 dBm
< RSSI ≤ -82
dBm) on the
PUSCH

BTS3203E


eNodeB detects
a PRB-level
average RSSI
with the index
of 20 (-82 dBm
< RSSI ≤ -80
dBm) on the
PUSCH

eNodeB detects
a PRB-level
average RSSI
with the index
of 21 (RSSI >
-80 dBm) on
the PUSCH
Description
The counters measure the distribution of received signal strength indicators (RSSIs) on the
PUSCH in a cell.
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. 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 PUSCH.
Formula
None
Unit
None

BTS3203E
Related Features
L.UL.RSSI.PUSCH.Index0 Multi-mode: None

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

BTS3203E

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

BTS3203E

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

BTS3203E

GSM: None
UMTS: None
Management
1.16.5 Distribution of INs on the PUSCH

Counters
1526734045 L.UL.Interferen Number of BTS3203E LTE L

ce.PUSCH.Inde times that the
x0 eNodeB detects
a PRB-level IN
with the index
of 0 (IN ≤ -121
dBm) on the
PUSCH

x1 eNodeB detects
a PRB-level IN
with the index
of 1 (-121 dBm
< RSSI ≤ -120
dBm) on the
PUSCH

x2 eNodeB detects
a PRB-level IN
with the index
of 2 (-120 dBm
< IN ≤ -119
dBm) on the
PUSCH

BTS3203E


x3 eNodeB detects
a PRB-level IN
with the index
of 3 (-119 dBm
< IN ≤ -118
dBm) on the
PUSCH

x4 eNodeB detects
a PRB-level IN
with the index
of 4 (-118 dBm
< IN ≤ -117
dBm) on the
PUSCH

x5 eNodeB detects
a PRB-level IN
with the index
of 5 (-117 dBm
< IN ≤ -116
dBm) on the
PUSCH

x6 eNodeB detects
a PRB-level IN
with the index
of 6 (-116 dBm
< IN ≤ -115
dBm) on the
PUSCH

x7 eNodeB detects
a PRB-level IN
with the index
of 7 (-115 dBm
< IN ≤ -114
dBm) on the
PUSCH

BTS3203E


x8 eNodeB detects
a PRB-level IN
with the index
of 8 (-114 dBm
< IN ≤ -113
dBm) on the
PUSCH

x9 eNodeB detects
a PRB-level IN
with the index
of 9 (-113 dBm
< IN ≤ -112
dBm) on the
PUSCH

x10 eNodeB detects
a PRB-level IN
with the index
of 10 (-112
dBm < IN ≤
-108 dBm) on
the PUSCH

x11 eNodeB detects
a PRB-level IN
with the index
of 11 (-108
dBm < IN ≤
-104 dBm) on
the PUSCH

x12 eNodeB detects
a PRB-level IN
with the index
of 12 (-104
dBm < IN ≤
-100 dBm) on
the PUSCH

BTS3203E


x13 eNodeB detects
a PRB-level IN
with the index
of 13 (-100
dBm < IN ≤ -96
dBm) on the
PUSCH

x14 eNodeB detects
a PRB-level IN
with the index
of 14 (-96 dBm
< IN ≤ -92
dBm) on the
PUSCH

x15 eNodeB detects
a PRB-level IN
with the index
of 15 (IN > -92
dBm) on the
PUSCH
Description
The counters measure the distribution of interference noises (INs) on the PUSCH in a cell.
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. 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

BTS3203E
Related Features
L.UL.Interference.PUSCH.I Multi-mode: None

ndex0 GSM: None
UMTS: None
Management

ndex1 GSM: None
UMTS: None
Management

ndex2 GSM: None
UMTS: None
Management

ndex3 GSM: None
UMTS: None
Management

ndex4 GSM: None
UMTS: None
Management

ndex5 GSM: None
UMTS: None
Management

ndex6 GSM: None
UMTS: None
Management

BTS3203E

ndex7 GSM: None
UMTS: None
Management

ndex8 GSM: None
UMTS: None
Management

ndex9 GSM: None
UMTS: None
Management

ndex10 GSM: None
UMTS: None
Management

ndex11 GSM: None
UMTS: None
Management

ndex12 GSM: None
UMTS: None
Management

ndex13 GSM: None
UMTS: None
Management

BTS3203E

ndex14 GSM: None
UMTS: None
Management

ndex15 GSM: None
UMTS: None
Management
1.16.6 Distribution of INs on the PUCCH
Counters

ce.PUCCH.Inde times that the
x0 eNodeB detects
a PRB-level IN
with the index
of 0 (IN ≤ -121
dBm) on the
PUCCH

x1 eNodeB detects
a PRB-level IN
with the index
of 1 (-121 dBm
< IN ≤ -120
dBm) on the
PUCCH

x2 eNodeB detects
a PRB-level IN
with the index
of 2 (-120 dBm
< IN ≤ -119
dBm) on the
PUCCH

BTS3203E


x3 eNodeB detects
a PRB-level IN
with the index
of 3 (-119 dBm
< IN ≤ -118
dBm) on the
PUCCH

x4 eNodeB detects
a PRB-level IN
with the index
of 4 (-118 dBm
< IN ≤ -117
dBm) on the
PUCCH

x5 eNodeB detects
a PRB-level IN
with the index
of 5 (-117 dBm
< IN ≤ -116
dBm) on the
PUCCH

x6 eNodeB detects
a PRB-level IN
with the index
of 6 (-116 dBm
< IN ≤ -115
dBm) on the
PUCCH

x7 eNodeB detects
a PRB-level IN
with the index
of 7 (-115 dBm
< IN ≤ -114
dBm) on the
PUCCH

BTS3203E


x8 eNodeB detects
a PRB-level IN
with the index
of 8 (-114 dBm
< IN ≤ -113
dBm) on the
PUCCH

x9 eNodeB detects
a PRB-level IN
with the index
of 9 (-113 dBm
< IN ≤ -112
dBm) on the
PUCCH

x10 eNodeB detects
a PRB-level IN
with the index
of 10 (-112
dBm < IN ≤
-108 dBm) on
the PUCCH

x11 eNodeB detects
a PRB-level IN
with the index
of 11 (-108
dBm < IN ≤
-104 dBm) on
the PUCCH

x12 eNodeB detects
a PRB-level IN
with the index
of 12 (-104
dBm < IN ≤
-100 dBm) on
the PUCCH

BTS3203E


x13 eNodeB detects
a PRB-level IN
with the index
of 13 (-100
dBm < IN ≤ -96
dBm) on the
PUCCH

x14 eNodeB detects
a PRB-level IN
with the index
of 14 (-96 dBm
< IN ≤ -92
dBm) on the
PUCCH

x15 eNodeB detects
a PRB-level IN
with the index
of 15 (IN > -92
dBm) on the
PUCCH
Description
The counters measure the distribution of interference noises (INs) on the PUCCH in a cell.
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. Because of the implementation
counters. However, the deviation does not affect the distribution of INs on the PUCCH.
Formula
None

BTS3203E
Unit
None
Related Features
L.UL.Interference.PUCCH.I Multi-mode: None

ndex0 GSM: None
UMTS: None
LBFD-002003 Physical Channel
Management

ndex1 GSM: None
UMTS: None
Management

ndex2 GSM: None
UMTS: None
Management

ndex3 GSM: None
UMTS: None
Management

ndex4 GSM: None
UMTS: None
Management

BTS3203E

ndex5 GSM: None
UMTS: None
Management

ndex6 GSM: None
UMTS: None
Management

ndex7 GSM: None
UMTS: None
Management

ndex8 GSM: None
UMTS: None
Management

ndex9 GSM: None
UMTS: None
Management

ndex10 GSM: None
UMTS: None
Management

BTS3203E

ndex11 GSM: None
UMTS: None
Management

ndex12 GSM: None
UMTS: None
Management

ndex13 GSM: None
UMTS: None
Management

ndex14 GSM: None
UMTS: None
Management

ndex15 GSM: None
UMTS: None
Management

BTS3203E
1.16.7 Distribution of INs on the PRACH

Counters

ce.PRACH.Inde times that the
x0 eNodeB detects
a PRB-level
average IN with
the index of 0
(IN ≤ -121
dBm) on the
PRACH

x1 eNodeB detects
a PRB-level
average IN with
the index of 1
(-121 dBm <
RSSI ≤ -120
dBm) on the
PRACH

x2 eNodeB detects
a PRB-level
average IN with
the index of 2
(-120 dBm < IN
≤ -119 dBm) on
the PRACH

x3 eNodeB detects
a PRB-level
average IN with
the index of 3
(-119 dBm < IN
≤ -118 dBm) on
the PRACH

BTS3203E


x4 eNodeB detects
a PRB-level
average IN with
the index of 4
(-118 dBm < IN
≤ -117 dBm) on
the PRACH

x5 eNodeB detects
a PRB-level
average IN with
the index of 5
(-117 dBm < IN
≤ -116 dBm) on
the PRACH

x6 eNodeB detects
a PRB-level
average IN with
the index of 6
(-116 dBm < IN
≤ -115 dBm) on
the PRACH

x7 eNodeB detects
a PRB-level
average IN with
the index of 7
(-115 dBm < IN
≤ -114 dBm) on
the PRACH

x8 eNodeB detects
a PRB-level
average IN with
the index of 8
(-114 dBm < IN
≤ -113 dBm) on
the PRACH

BTS3203E


x9 eNodeB detects
a PRB-level
average IN with
the index of 9
(-113 dBm < IN
≤ -112 dBm) on
the PRACH

x10 eNodeB detects
a PRB-level
average IN with
the index of 10
(-112 dBm < IN
≤ -108 dBm) on
the PRACH

x11 eNodeB detects
a PRB-level
average IN with
the index of 11
(-108 dBm < IN
≤ -104 dBm) on
the PRACH

x12 eNodeB detects
a PRB-level
average IN with
the index of 12
(-104 dBm < IN
≤ -100 dBm) on
the PRACH

x13 eNodeB detects
a PRB-level
average IN with
the index of 13
(-100 dBm < IN
≤ -96 dBm) on
the PRACH

BTS3203E


x14 eNodeB detects
a PRB-level
average IN with
the index of 14
(-96 dBm < IN
≤ -92 dBm) on
the PRACH

x15 eNodeB detects
a PRB-level
average IN with
the index of 15
(IN > -92 dBm)
on the PRACH
Description
The counters measure the distribution of interference noises (INs) on the PRACH in a cell.
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. 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 PRACH.
Formula
None
Unit
None

BTS3203E
Related Features
L.UL.Interference.PRACH.I Multi-mode: None

ndex0 GSM: None
UMTS: None
Management

ndex1 GSM: None
UMTS: None
Management

ndex2 GSM: None
UMTS: None
Management

ndex3 GSM: None
UMTS: None
Management

ndex4 GSM: None
UMTS: None
Management

ndex5 GSM: None
UMTS: None
Management

BTS3203E

ndex6 GSM: None
UMTS: None
Management

ndex7 GSM: None
UMTS: None
Management

ndex8 GSM: None
UMTS: None
Management

ndex9 GSM: None
UMTS: None
Management

ndex10 GSM: None
UMTS: None
Management

ndex11 GSM: None
UMTS: None
Management

BTS3203E

ndex12 GSM: None
UMTS: None
Management

ndex13 GSM: None
UMTS: None
Management

ndex14 GSM: None
UMTS: None
Management

ndex15 GSM: None
UMTS: None
Management
1.16.8 Distribution of RSRPs on the PUSCH
Counters
1526734093 L.UL.RSRP.PU Number of BTS3203E LTE L

eNodeB detects
a UE-level
RSRP with the
index of 0
(RSRP ≤ -146
dBm) on the
PUSCH

BTS3203E


eNodeB detects
a UE-level
RSRP with the
index of 1 (-146
dBm < RSRP ≤
-144 dBm) on
the PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 2 (-144
dBm < RSRP ≤
-142 dBm) on
the PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 3 (-142
dBm < RSRP ≤
-140 dBm) on
the PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 4 (-140
dBm < RSRP ≤
-138 dBm) on
the PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 5 (-138
dBm < RSRP ≤
-136 dBm) on
the PUSCH

BTS3203E


eNodeB detects
a UE-level
RSRP with the
index of 6 (-136
dBm < RSRP ≤
-134 dBm) on
the PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 7 (-134
dBm < RSRP ≤
-132 dBm) on
the PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 8 (-132
dBm < RSRP ≤
-130 dBm) on
the PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 9 (-130
dBm < RSRP ≤
-128 dBm) on
the PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 10
(-128 dBm <
RSRP ≤ -126
dBm) on the
PUSCH

BTS3203E


eNodeB detects
a UE-level
RSRP with the
index of 11
(-126 dBm <
RSRP ≤ -124
dBm) on the
PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 12
(-124 dBm <
RSRP ≤ -122
dBm) on the
PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 13
(-122 dBm <
RSRP ≤ -120
dBm) on the
PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 14
(-120 dBm <
RSRP ≤ -118
dBm) on the
PUSCH

BTS3203E


eNodeB detects
a UE-level
RSRP with the
index of 15
(-118 dBm <
RSRP ≤ -116
dBm) on the
PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 16
(-116 dBm <
RSRP ≤ -114
dBm) on the
PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 17
(-114 dBm <
RSRP ≤ -112
dBm) on the
PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 18
(-112 dBm <
RSRP ≤ -110
dBm) on the
PUSCH

BTS3203E


eNodeB detects
a UE-level
RSRP with the
index of 19
(-110 dBm <
RSRP ≤ -105
dBm) on the
PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 20
(-105 dBm <
RSRP ≤ -100
dBm) on the
PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 21
(-100 dBm <
RSRP ≤ -95
dBm) on the
PUSCH

eNodeB detects
a UE-level
RSRP with the
index of 22 (-95
dBm < RSRP ≤
-90 dBm) on
the PUSCH

BTS3203E


eNodeB detects
a UE-level
RSRP with the
index of 23
(RSRP > -90
dBm) on the
PUSCH
Description
The counters measure the distribution of reference signal received powers (RSRPs) on the
PUSCH in a cell.
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. Because of the implementation
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
Management

GSM: None
UMTS: None
Management

BTS3203E

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

BTS3203E

GSM: None
UMTS: None
Management

0 GSM: None
UMTS: None
Management

1 GSM: None
UMTS: None
Management

2 GSM: None
UMTS: None
Management

3 GSM: None
UMTS: None
Management

4 GSM: None
UMTS: None
Management

5 GSM: None
UMTS: None
Management

BTS3203E

6 GSM: None
UMTS: None
Management

7 GSM: None
UMTS: None
Management

8 GSM: None
UMTS: None
Management

9 GSM: None
UMTS: None
Management

0 GSM: None
UMTS: None
Management

1 GSM: None
UMTS: None
Management

2 GSM: None
UMTS: None
Management

BTS3203E

3 GSM: None
UMTS: None
Management
1.16.9 Distribution of RSRPs on the PUCCH

Counters

eNodeB detects
a UE-level
RSRP with the
index of 0
(RSRP ≤ -146
dBm) on the
PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 1 (-146
dBm < RSRP ≤
-144 dBm) on
the PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 2 (-144
dBm < RSRP ≤
-142 dBm) on
the PUCCH

BTS3203E


eNodeB detects
a UE-level
RSRP with the
index of 3 (-142
dBm < RSRP ≤
-140 dBm) on
the PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 4 (-140
dBm < RSRP ≤
-138 dBm) on
the PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 5 (-138
dBm < RSRP ≤
-136 dBm) on
the PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 6 (-136
dBm < RSRP ≤
-134 dBm) on
the PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 7 (-134
dBm < RSRP ≤
-132 dBm) on
the PUCCH

BTS3203E


eNodeB detects
a UE-level
RSRP with the
index of 8 (-132
dBm < RSRP ≤
-130 dBm) on
the PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 9 (-130
dBm < RSRP ≤
-128 dBm) on
the PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 10
(-128 dBm <
RSRP ≤ -126
dBm) on the
PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 11
(-126 dBm <
RSRP ≤ -124
dBm) on the
PUCCH

BTS3203E


eNodeB detects
a UE-level
RSRP with the
index of 12
(-124 dBm <
RSRP ≤ -122
dBm) on the
PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 13
(-122 dBm <
RSRP ≤ -120
dBm) on the
PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 14
(-120 dBm <
RSRP ≤ -118
dBm) on the
PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 15
(-118 dBm <
RSRP ≤ -116
dBm) on the
PUCCH

BTS3203E


eNodeB detects
a UE-level
RSRP with the
index of 16
(-116 dBm <
RSRP ≤ -114
dBm) on the
PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 17
(-114 dBm <
RSRP ≤ -112
dBm) on the
PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 18
(-112 dBm <
RSRP ≤ -110
dBm) on the
PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 19
(-110 dBm <
RSRP ≤ -105
dBm) on the
PUCCH

BTS3203E


eNodeB detects
a UE-level
RSRP with the
index of 20
(-105 dBm <
RSRP ≤ -100
dBm) on the
PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 21
(-100 dBm <
RSRP ≤ -95
dBm) on the
PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 22 (-95
dBm < RSRP ≤
-90 dBm) on
the PUCCH

eNodeB detects
a UE-level
RSRP with the
index of 23
(RSRP > -90
dBm) on the
PUCCH
Description
The counters measure the distribution of reference signal received powers (RSRPs) on the
PUCCH in a cell.

BTS3203E
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. 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
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

BTS3203E

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

BTS3203E

0 GSM: None
UMTS: None
Management

1 GSM: None
UMTS: None
Management

2 GSM: None
UMTS: None
Management

3 GSM: None
UMTS: None
Management

4 GSM: None
UMTS: None
Management

5 GSM: None
UMTS: None
Management

BTS3203E

6 GSM: None
UMTS: None
Management

7 GSM: None
UMTS: None
Management

8 GSM: None
UMTS: None
Management

9 GSM: None
UMTS: None
Management

0 GSM: None
UMTS: None
Management

1 GSM: None
UMTS: None
Management

BTS3203E

2 GSM: None
UMTS: None
Management

3 GSM: None
UMTS: None
Management
1.16.10 Linear Value of Interference Noise Received per PRB

Counters
1526743709 L.UL.Interferen Linear average BTS3203E LTE L

ce.LinearAvg value of PRB-
level
interference
noise detected
in the uplink
Description
The counter measures the linear average value of PRB-level interference noise detected in the
uplink. The definitive value of this counter is equal to the measurement result multiplied by a
normalization coefficient 10^-15 and is in the unit of mW.
Measurement Points
The total power of noise floor and neighboring cell interference received by each PRB is
measured per 10 ms in the uplink. For SFN cells, the interference power of each PRB is
measured for all physical cells. The average measured value per PRB in the unit of mW is
taken as a sampling result. At the end of a measurement period, the average of the sampling
results is taken as the counter value.
Formula
None

BTS3203E
Unit
mW
Related Features
L.UL.Interference.LinearAv Multi-mode: None

g GSM: None
UMTS: None
Management
1.17 MIMO Measurement (ChMeas.MIMO.Cell)

Overview
The ChMeas.MIMO.Cell function subset measures the number of used PRBs in different
Multiple Input Multiple Output (MIMO) modes in a cell.
Counters
1526727391 L.ChMeas.MIMO. Total number of BTS3203E LTE:

PRB.CL.Rank1 used downlink PRBs version earlier than
in closed-loop rank V100R003C00
1 mode

PRB.CL.Rank2 used downlink PRBs version earlier than
in closed-loop rank V100R003C00
2 mode

PRB.OL.Rank1 used downlink PRBs V100R006C00
in open-loop rank 1
mode

in open-loop rank 2
mode

PRB.CL.Rank3 used downlink PRBs V100R003C00
in closed-loop rank
3 mode

BTS3203E


PRB.CL.Rank4 used downlink PRBs V100R003C00
in closed-loop rank
4 mode

in open-loop rank 3
mode

in open-loop rank 4
mode
1526729281 L.Traffic.DL.SCH. Number of TBs BTS3203E LTE:

TB.CL.Rank1 transmitted in V100R006C00
downlink closed-
loop rank 1 mode

downlink closed-
loop rank 2 mode

TB.OL.Rank1 transmitted in V100R006C00
downlink open-loop
rank 1 mode

downlink open-loop
rank 2 mode

downlink closed-
loop rank 3 mode

downlink closed-
loop rank 4 mode

downlink open-loop
rank 3 mode

BTS3203E


downlink open-loop
rank 4 mode

TB.TM1 transmitted in V100R006C00
downlink TM1
mode

downlink TM2
mode

downlink TM3
mode

downlink TM4
mode

downlink TM6
mode
1526737831 L.Traffic.DL.SCH. Number of bits BTS3203E LTE:

TB.TM1.bits transmitted in the V100R011C10
downlink in TM1

downlink in TM2

downlink in TM3

downlink in TM4

downlink in TM5

downlink in TM6

BTS3203E


downlink in TM7

downlink in TM8
1526737839 L.ChMeas.PRB.T Total number of BTS3203E LTE:

M1 used downlink PRBs V100R011C10
in TM1

in TM2

in TM3

in TM4

in TM5

in TM6

in TM7

in TM8
None

BTS3203E
1.17.1 Number of Used Downlink PRBs in MIMO Mode

Counters
1526727391 L.ChMeas.MI Total number of BTS3203E LTE L

MO.PRB.CL.R used downlink
ank1 PRBs in closed-
loop rank 1
mode

loop rank 2
mode

MO.PRB.OL.R used downlink
ank1 PRBs in open-
loop rank 1
mode

ank2 PRBs in open-
loop rank 2
mode

loop rank 3
mode

loop rank 4
mode

ank3 PRBs in open-
loop rank 3
mode

ank4 PRBs in open-
loop rank 4
mode

BTS3203E
Description
Downlink MIMO is divided into eight modes: open-loop modes with the rank ranging from 1
to 4 and closed-loop modes with the rank ranging from 1 to 4. The counters measure the
number of used downlink PRBs in different MIMO modes for analyzing the PRB usage in
different scenarios.
Measurement Points
The number of used downlink PRBs in each MIMO mode is measured within the
measurement period. In an SFN cell, the number of PRBs used in each physical cell is
accumulated. In a cell with Virtual 4T4R enabled, the number of PRBs used on all beams is
accumulated.
In the LTE TDD system, the number of PRBs used by each related physical cell is
incremented for cells configured with Cell Combination.
Formula
None
Unit
None
Related Features
L.ChMeas.MIMO.PRB.CL. Multi-mode: None

Rank1 GSM: None
UMTS: None
LOFD-001001 DL 2x2 MIMO
LEOFD-111305 Virtual 4T4R

Rank2 GSM: None
UMTS: None

BTS3203E
L.ChMeas.MIMO.PRB.OL. Multi-mode: None

Rank1 GSM: None
UMTS: None

Rank2 GSM: None
UMTS: None

Rank3 GSM: None
UMTS: None

Rank4 GSM: None
UMTS: None

Rank3 GSM: None
UMTS: None

Rank4 GSM: None
UMTS: None

BTS3203E
1.17.2 Number of TBs Transmitted in Downlink MIMO Mode

Counters
1526729281 L.Traffic.DL.S Number of TBs BTS3203E LTE L

CH.TB.CL.Ran transmitted in
k1 downlink
closed-loop
rank 1 mode

k2 downlink
closed-loop
rank 2 mode

CH.TB.OL.Ran transmitted in
k1 downlink open-
loop rank 1
mode

k2 downlink open-
loop rank 2
mode

k3 downlink
closed-loop
rank 3 mode

k4 downlink
closed-loop
rank 4 mode

k3 downlink open-
loop rank 3
mode

k4 downlink open-
loop rank 4
mode

BTS3203E


CH.TB.TM1 transmitted in
downlink TM1
mode

downlink TM2
mode

downlink TM3
mode

downlink TM4
mode

downlink TM6
mode
Description
The downlink MIMO modes can be classified into eight modes by closed-loop and open-loop
modes with the rank ranging from 1 to 4. The downlink MIMO modes can be classified into
five modes by TM mode: TM1, TM2, TM3, TM4, TM6.
Measurement Points
The number of TBs, including retransmitted TBs, for downlink data transmission in open-
loop and closed-loop modes with different ranks and TM modes is calculated within a
measurement period.
Formula
None
Unit
None

BTS3203E
Related Features
L.Traffic.DL.SCH.TB.CL.R Multi-mode: None

ank1 GSM: None
UMTS: None
LTE: LOFD-001001 DL 2x2 MIMO
LBFD-002002 Transport Channel
Management

ank2 GSM: None
UMTS: None
Management
L.Traffic.DL.SCH.TB.OL.R Multi-mode: None

ank1 GSM: None
UMTS: None
Management

ank2 GSM: None
UMTS: None
Management

ank3 GSM: None
UMTS: None
Management

ank4 GSM: None
UMTS: None
Management

BTS3203E

ank3 GSM: None
UMTS: None
Management

ank4 GSM: None
UMTS: None
Management
L.Traffic.DL.SCH.TB.TM1 Multi-mode: None

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

BTS3203E

GSM: None
UMTS: None
Management
1.17.3 Numbers of Bits Transmitted in the Downlink in Different

Transmission Modes
Counters
1526737831 L.Traffic.DL.S Number of bits BTS3203E LTE L

CH.TB.TM1.bit transmitted in
s the downlink in
TM1

s the downlink in
TM2

s the downlink in
TM3

s the downlink in
TM4

s the downlink in
TM5

s the downlink in
TM6

BTS3203E


s the downlink in
TM7

s the downlink in
TM8
Description
The counters measure the number of bits of TBs transmitted in the downlink per transmission
mode.The following counters apply only to LTE TDD:
- L.Traffic.DL.SCH.TB.TM5.bits
Measurement Points
During downlink data transmission, the eNodeB counts the number of bits of downlink TBs,
including retransmitted TBs, per transmission mode in a cell within a measurement period.
Formula
None
Unit
bit
Related Features
L.Traffic.DL.SCH.TB.TM1. Multi-mode: None

bits GSM: None
UMTS: None
LTE: LBFD-002002 Transport Channel
Management

BTS3203E

bits GSM: None
UMTS: None
Management

bits GSM: None
UMTS: None
Management

bits GSM: None
UMTS: None
Management

bits GSM: None
UMTS: None
Management
1.17.4 Numbers of Used Downlink PRBs in Different

Transmission Modes
Counters
1526737839 L.ChMeas.PRB Total number of BTS3203E LTE L

.TM1 used downlink
PRBs in TM1

.TM2 used downlink
PRBs in TM2

.TM3 used downlink
PRBs in TM3

BTS3203E


.TM4 used downlink
PRBs in TM4

.TM5 used downlink
PRBs in TM5

.TM6 used downlink
PRBs in TM6

.TM7 used downlink
PRBs in TM7

.TM8 used downlink
PRBs in TM8
Description
The counters measure the number of used downlink PRBs in different transmission modes for
analyzing the downlink PRB usage in different transmission modes.The following counters
apply only to LTE TDD:
- L.ChMeas.PRB.TM5
- L.ChMeas.PRB.TM7
- L.ChMeas.PRB.TM8
Measurement Points
The eNodeB counts the total number of used downlink PRBs per transmission mode in a cell
within a measurement period.
Formula
None
Unit
None

BTS3203E
Related Features
L.ChMeas.PRB.TM1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
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.

BTS3203E
Counters
1526727396 L.ChMeas.CQI.DL Number of BTS3203E LTE:

.0 wideband CQI V100R006C00
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

BTS3203E


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
1526728679 L.ChMeas.CQI.AB Number of reports BTS3203E LTE:

S.DL.0 that contain V100R006C00
wideband CQIs of 0
for ABSs

wideband CQIs of 1
for ABSs

wideband CQIs of 2
for ABSs

wideband CQIs of 3
for ABSs

BTS3203E


wideband CQIs of 4
for ABSs

wideband CQIs of 5
for ABSs

wideband CQIs of 6
for ABSs

wideband CQIs of 7
for ABSs

wideband CQIs of 8
for ABSs

wideband CQIs of 9
for ABSs

wideband CQIs of
10 for ABSs

wideband CQIs of
11 for ABSs

wideband CQIs of
12 for ABSs

wideband CQIs of
13 for ABSs

BTS3203E


wideband CQIs of
14 for ABSs

wideband CQIs of
15 for ABSs
1526729319 L.ChMeas.CQI.DL Number of periodic BTS3203E LTE:

.SingleCW.Periodic wideband CQI V100R006C00
.0 reports with the
value of 0 in single-
codeword
transmission

.1 reports with the
codeword
transmission

.2 reports with the
codeword
transmission

.3 reports with the
codeword
transmission

.4 reports with the
codeword
transmission

.5 reports with the
codeword
transmission

BTS3203E


.6 reports with the
codeword
transmission

.7 reports with the
codeword
transmission

.8 reports with the
codeword
transmission

.9 reports with the
codeword
transmission

.10 reports with the
value of 10 in
single-codeword
transmission

value of 11 in
single-codeword
transmission

value of 12 in
single-codeword
transmission

BTS3203E


value of 13 in
single-codeword
transmission

value of 14 in
single-codeword
transmission

value of 15 in
single-codeword
transmission
1526729335 L.ChMeas.CQI.DL Number of aperiodic BTS3203E LTE:

.SingleCW.Aperiod wideband CQI V100R006C00
ic.0 reports with the
codeword
transmission

codeword
transmission

codeword
transmission

codeword
transmission

BTS3203E


codeword
transmission

codeword
transmission

codeword
transmission

codeword
transmission

codeword
transmission

codeword
transmission

value of 10 in
single-codeword
transmission

BTS3203E


value of 11 in
single-codeword
transmission

value of 12 in
single-codeword
transmission

value of 13 in
single-codeword
transmission

value of 14 in
single-codeword
transmission

value of 15 in
single-codeword
transmission

.DualCW.Code0.Pe wideband CQI V100R006C00
riodic.0 reports with the
value of 0 for
codeword 0 in dual-
codeword
transmission

value of 1 for
codeword 0 in dual-
codeword
transmission

BTS3203E


value of 2 for
codeword 0 in dual-
codeword
transmission

value of 3 for
codeword 0 in dual-
codeword
transmission

value of 4 for
codeword 0 in dual-
codeword
transmission

value of 5 for
codeword 0 in dual-
codeword
transmission

value of 6 for
codeword 0 in dual-
codeword
transmission

value of 7 for
codeword 0 in dual-
codeword
transmission

BTS3203E


value of 8 for
codeword 0 in dual-
codeword
transmission

value of 9 for
codeword 0 in dual-
codeword
transmission

value of 10 for
codeword 0 in dual-
codeword
transmission

value of 11 for
codeword 0 in dual-
codeword
transmission

value of 12 for
codeword 0 in dual-
codeword
transmission

value of 13 for
codeword 0 in dual-
codeword
transmission

BTS3203E


value of 14 for
codeword 0 in dual-
codeword
transmission

value of 15 for
codeword 0 in dual-
codeword
transmission

.DualCW.Code0.A wideband CQI V100R006C00
periodic.0 reports with the
value of 0 for
codeword 0 in dual-
codeword
transmission

value of 1 for
codeword 0 in dual-
codeword
transmission

value of 2 for
codeword 0 in dual-
codeword
transmission

value of 3 for
codeword 0 in dual-
codeword
transmission

BTS3203E


value of 4 for
codeword 0 in dual-
codeword
transmission

value of 5 for
codeword 0 in dual-
codeword
transmission

value of 6 for
codeword 0 in dual-
codeword
transmission

value of 7 for
codeword 0 in dual-
codeword
transmission

value of 8 for
codeword 0 in dual-
codeword
transmission

value of 9 for
codeword 0 in dual-
codeword
transmission

BTS3203E


value of 10 for
codeword 0 in dual-
codeword
transmission

value of 11 for
codeword 0 in dual-
codeword
transmission

value of 12 for
codeword 0 in dual-
codeword
transmission

value of 13 for
codeword 0 in dual-
codeword
transmission

value of 14 for
codeword 0 in dual-
codeword
transmission

value of 15 for
codeword 0 in dual-
codeword
transmission

BTS3203E


value of 0 for
codeword 1 in dual-
codeword
transmission

value of 1 for
codeword 1 in dual-
codeword
transmission

value of 2 for
codeword 1 in dual-
codeword
transmission

value of 3 for
codeword 1 in dual-
codeword
transmission

value of 4 for
codeword 1 in dual-
codeword
transmission

value of 5 for
codeword 1 in dual-
codeword
transmission

BTS3203E


value of 6 for
codeword 1 in dual-
codeword
transmission

value of 7 for
codeword 1 in dual-
codeword
transmission

value of 8 for
codeword 1 in dual-
codeword
transmission

value of 9 for
codeword 1 in dual-
codeword
transmission

value of 10 for
codeword 1 in dual-
codeword
transmission

value of 11 for
codeword 1 in dual-
codeword
transmission

BTS3203E


value of 12 for
codeword 1 in dual-
codeword
transmission

value of 13 for
codeword 1 in dual-
codeword
transmission

value of 14 for
codeword 1 in dual-
codeword
transmission

value of 15 for
codeword 1 in dual-
codeword
transmission

value of 0 for
codeword 1 in dual-
codeword
transmission

value of 1 for
codeword 1 in dual-
codeword
transmission

BTS3203E


value of 2 for
codeword 1 in dual-
codeword
transmission

value of 3 for
codeword 1 in dual-
codeword
transmission

value of 4 for
codeword 1 in dual-
codeword
transmission

value of 5 for
codeword 1 in dual-
codeword
transmission

value of 6 for
codeword 1 in dual-
codeword
transmission

value of 7 for
codeword 1 in dual-
codeword
transmission

BTS3203E


value of 8 for
codeword 1 in dual-
codeword
transmission

value of 9 for
codeword 1 in dual-
codeword
transmission

value of 10 for
codeword 1 in dual-
codeword
transmission

value of 11 for
codeword 1 in dual-
codeword
transmission

value of 12 for
codeword 1 in dual-
codeword
transmission

value of 13 for
codeword 1 in dual-
codeword
transmission

BTS3203E


value of 14 for
codeword 1 in dual-
codeword
transmission

value of 15 for
codeword 1 in dual-
codeword
transmission
1526730141 L.ChMeas.RI.Rank Number of times a BTS3203E LTE:

1 UE reports rank 1 V100R007C00



1526737710 L.ChMeas.CQI.DL Accumulated value BTS3203E LTE:

.BorderUE.Total of wideband CQIs V100R011C10
reported by CEUs
1526737711 L.ChMeas.CQI.DL Number of times BTS3203E LTE:

.BorderUE.Num wideband CQIs are V100R011C10
reported by CEUs
1526739662 L.ChMeas.DL. Number of BTS3203E LTE:

256QAM.CQI.DL. wideband CQI V100R011C10
0 reports with the
value of 0 sent by
downlink-256QAM-
enabled UEs

1 reports with the
value of 1 sent by
downlink-256QAM-
enabled UEs

BTS3203E


2 reports with the
value of 2 sent by
downlink-257QAM-
enabled UEs

3 reports with the
value of 3 sent by
downlink-258QAM-
enabled UEs

4 reports with the
value of 4 sent by
downlink-259QAM-
enabled UEs

5 reports with the
value of 5 sent by
downlink-260QAM-
enabled UEs

6 reports with the
value of 6 sent by
downlink-261QAM-
enabled UEs

7 reports with the
value of 7 sent by
downlink-262QAM-
enabled UEs

8 reports with the
value of 8 sent by
downlink-263QAM-
enabled UEs

BTS3203E


9 reports with the
value of 9 sent by
downlink-264QAM-
enabled UEs

10 reports with the
value of 10 sent by
downlink-265QAM-
enabled UEs

11 reports with the
value of 11 sent by
downlink-266QAM-
enabled UEs

12 reports with the
value of 12 sent by
downlink-267QAM-
enabled UEs

13 reports with the
value of 13 sent by
downlink-268QAM-
enabled UEs

14 reports with the
value of 14 sent by
downlink-269QAM-
enabled UEs

15 reports with the
value of 15 sent by
downlink-270QAM-
enabled UEs

BTS3203E
None
1.18.1 Number of Wideband CQI Reports in a Cell
Counters
1526727396 L.ChMeas.CQI. Number of BTS3203E LTE L

DL.0 wideband CQI
reports with the
value of 0

DL.1 wideband CQI
reports with the
value of 1

DL.2 wideband CQI
reports with the
value of 2

DL.3 wideband CQI
reports with the
value of 3

DL.4 wideband CQI
reports with the
value of 4

DL.5 wideband CQI
reports with the
value of 5

DL.6 wideband CQI
reports with the
value of 6

DL.7 wideband CQI
reports with the
value of 7

DL.8 wideband CQI
reports with the
value of 8

BTS3203E


DL.9 wideband CQI
reports with the
value of 9

DL.10 wideband CQI
reports with the
value of 10

DL.11 wideband CQI
reports with the
value of 11

DL.12 wideband CQI
reports with the
value of 12

DL.13 wideband CQI
reports with the
value of 13

DL.14 wideband CQI
reports with the
value of 14

DL.15 wideband CQI
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.

BTS3203E
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-00101502 Allocation
Dynamic Scheduling

GSM: None
UMTS: None
Dynamic Scheduling

GSM: None
UMTS: None
Dynamic Scheduling

GSM: None
UMTS: None
Dynamic Scheduling

GSM: None
UMTS: None
Dynamic Scheduling

BTS3203E

GSM: None
UMTS: None
Dynamic Scheduling

GSM: None
UMTS: None
Dynamic Scheduling

GSM: None
UMTS: None
Dynamic Scheduling

GSM: None
UMTS: None
Dynamic Scheduling

GSM: None
UMTS: None
Dynamic Scheduling

GSM: None
UMTS: None
Dynamic Scheduling

BTS3203E

GSM: None
UMTS: None
Dynamic Scheduling

GSM: None
UMTS: None
Dynamic Scheduling

GSM: None
UMTS: None
Dynamic Scheduling

GSM: None
UMTS: None
Dynamic Scheduling

GSM: None
UMTS: None
Dynamic Scheduling

BTS3203E
1.18.2 Number of Reports that Contain wideband CQIs for ABSs

Counters

ABS.DL.0 reports that
contain
wideband CQIs
of 0 for ABSs

contain
wideband CQIs
of 1 for ABSs

contain
wideband CQIs
of 2 for ABSs

contain
wideband CQIs
of 3 for ABSs

contain
wideband CQIs
of 4 for ABSs

contain
wideband CQIs
of 5 for ABSs

contain
wideband CQIs
of 6 for ABSs

contain
wideband CQIs
of 7 for ABSs

BTS3203E


contain
wideband CQIs
of 8 for ABSs

contain
wideband CQIs
of 9 for ABSs

contain
wideband CQIs
of 10 for ABSs

contain
wideband CQIs
of 11 for ABSs

contain
wideband CQIs
of 12 for ABSs

contain
wideband CQIs
of 13 for ABSs

contain
wideband CQIs
of 14 for ABSs

contain
wideband CQIs
of 15 for ABSs
Description
Chanel Quality Indicator (CQI) is used to evaluate the quality of the downlink channel and is
used as the input of MAC scheduling. The UE sends the evaluation result to the eNodeB

BTS3203E
through the uplink channel. The counters measure the number of reports with a specific CQI
index ranging from 0 to 15 in ABS pattern subframes in a cell. It is used to evaluate the
overall quality of the downlink channel for ABS pattern.
Measurement Points
The corresponding counter is incremented by 1 based on the CQI index each time the eNodeB
receives a wideband CQI report from the UE and the measurement subframes are in ABS
pattern. A deviation of one sampling period may be generated in the sampling timer when the
timer performs time synchronization. As a result, a deviation of one sampling period will also
be generated in the value of the corresponding counter. The deviation affects the values of the
KPIs that are calculated by using the counter. The effects vary depending on the deviation in
the value of the counter and calculation formulas for the KPIs.
Formula
None
Unit
None
Related Features
L.ChMeas.CQI.ABS.DL.0 Multi-mode: None

GSM: None
UMTS: None
LAOFD-081234 FeICIC

GSM: None
UMTS: None
LAOFD-081234 FeICIC

GSM: None
UMTS: None
LAOFD-081234 FeICIC

BTS3203E
1.18.3 Number of Periodic Wideband CQI Reports in Single-

Codeword Transmission in a Cell
Counters

DL.SingleCW.P periodic
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

BTS3203E


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

BTS3203E


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

BTS3203E


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
Dynamic Scheduling

BTS3203E

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

BTS3203E

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

BTS3203E

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling
1.18.4 Number of Aperiodic Wideband CQI Reports in Single-

Codeword Transmission in a Cell
Counters

DL.SingleCW. aperiodic
Aperiodic.0 wideband CQI
reports with the
value of 0 in
single-
codeword
transmission

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E
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
LBFD-002031 Dynamic Scheduling
Support of aperiodic CQI
reports

UMTS: None
reports

UMTS: None
reports

BTS3203E

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

BTS3203E

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

BTS3203E

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports
1.18.5 Number of Periodic Wideband CQI Reports for Codeword

0 in Dual-Codeword Transmission in a Cell
Counters

DL.DualCW.Co periodic
de0.Periodic.0 wideband CQI
reports with the
value of 0 for
codeword 0 in
dual-codeword
transmission

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E
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
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

BTS3203E

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

BTS3203E

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

BTS3203E

UMTS: None
Dynamic Scheduling
1.18.6 Number of Aperiodic Wideband CQI Reports for

Codeword 0 in Dual-Codeword Transmission in a Cell
Counters

DL.DualCW.Co aperiodic
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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E
Related Features

.Code0.Aperiodic.0 GSM: None
UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

BTS3203E

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

BTS3203E

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

BTS3203E

UMTS: None
reports

UMTS: None
reports
1.18.7 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

BTS3203E


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

BTS3203E


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

BTS3203E


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-

BTS3203E
Formula
None
Unit
None
Related Features

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

BTS3203E

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

BTS3203E

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

UMTS: None
Dynamic Scheduling

BTS3203E
1.18.8 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

BTS3203E


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

BTS3203E


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

BTS3203E


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
reports

BTS3203E

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

BTS3203E

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

BTS3203E

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

UMTS: None
reports

BTS3203E
1.18.9 Number of Times a UE Reports a Rank Value in a Cell

Counters
1526730141 L.ChMeas.RI.R Number of BTS3203E LTE L

ank1 times a UE
reports rank 1

ank2 times a UE
reports rank 2

ank3 times a UE
reports rank 3

ank4 times a UE
reports rank 4
Description
Rank values are calculated and reported by UEs whose transmission mode is TM3 or TM4 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.
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

BTS3203E
Related Features
L.ChMeas.RI.Rank1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
1.18.10 wideband CQIs reported by CEUs in a Cell

Counters
1526737710 L.ChMeas.CQI. Accumulated BTS3203E LTE L

DL.BorderUE. value of
Total wideband CQIs
reported by
CEUs

DL.BorderUE. times wideband
Num CQIs are
reported by
CEUs

BTS3203E
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 and the RSRP value of the serving cell. This identification
function is controlled by the BasedA3EdgeUserSwitch option of the CellCounterAlgoSwitch
parameter in the CellCounterParaGroup MO.The threshold is specified by the
EdgeUserA3Offset and EdgeUserServRSRPThd parameters.
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

BTS3203E
1.18.11 Number of Wideband CQI Reports Sent by

Downlink-256QAM-enabled UEs in a Cell
Counters
1526739662 L.ChMeas.DL. Number of BTS3203E LTE L

256QAM.CQI. wideband CQI
DL.0 reports with the
value of 0 sent
by
downlink-256Q
AM-enabled
UEs

value of 1 sent
by
downlink-256Q
AM-enabled
UEs

value of 2 sent
by
downlink-257Q
AM-enabled
UEs

value of 3 sent
by
downlink-258Q
AM-enabled
UEs

value of 4 sent
by
downlink-259Q
AM-enabled
UEs

BTS3203E


value of 5 sent
by
downlink-260Q
AM-enabled
UEs

value of 6 sent
by
downlink-261Q
AM-enabled
UEs

value of 7 sent
by
downlink-262Q
AM-enabled
UEs

value of 8 sent
by
downlink-263Q
AM-enabled
UEs

value of 9 sent
by
downlink-264Q
AM-enabled
UEs

BTS3203E


value of 10 sent
by
downlink-265Q
AM-enabled
UEs

value of 11 sent
by
downlink-266Q
AM-enabled
UEs

value of 12 sent
by
downlink-267Q
AM-enabled
UEs

value of 13 sent
by
downlink-268Q
AM-enabled
UEs

value of 14 sent
by
downlink-269Q
AM-enabled
UEs

BTS3203E


value of 15 sent
by
downlink-270Q
AM-enabled
UEs
Description
The counters measure the number of periodic and aperiodic wideband CQI reports with a
specific value sent by UEs with the downlink 256QAM modulation scheme enabled in cell
and indicate the overall quality of the downlink channel in the cell.
Measurement Points
each time the eNodeB receives a periodic or aperiodic wideband CQI report from a UE with
the downlink 256QAM modulation scheme enabled. If the rank value that the UE reports is
greater than 1, CQI for each of the two codewords is calculated separately.
Formula
None
Unit
None
Related Features
L.ChMeas.DL. Multi-mode: None

256QAM.CQI.DL.0 GSM: None
UMTS: None
LEOFD-110301 Basic Scheduling
DL 256QAM

BTS3203E

UMTS: None
DL 256QAM

UMTS: None
DL 256QAM

UMTS: None
DL 256QAM

UMTS: None
DL 256QAM

UMTS: None
DL 256QAM

BTS3203E

UMTS: None
DL 256QAM

UMTS: None
DL 256QAM

UMTS: None
DL 256QAM

UMTS: None
DL 256QAM

UMTS: None
DL 256QAM

BTS3203E

UMTS: None
DL 256QAM

UMTS: None
DL 256QAM

UMTS: None
DL 256QAM

UMTS: None
DL 256QAM

UMTS: None
DL 256QAM

BTS3203E
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
1526727412 L.ChMeas.PUSCH. Number of times BTS3203E LTE:

MCS.0 MCS index 0 is V100R006C00
scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

BTS3203E


scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

BTS3203E


scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

BTS3203E


scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH

scheduled on the
PUSCH
1526727444 L.ChMeas.PDSCH. Number of times BTS3203E LTE:

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

BTS3203E


scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

BTS3203E


scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

BTS3203E


scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH

scheduled on the
PDSCH
1526728566 L.ChMeas.PRB.UL Number of PRBs on BTS3203E LTE:

.MCS.0 the PUSCH using V100R006C00
MCS index 0 for
scheduling in a cell

MCS index 1 for

MCS index 2 for

MCS index 3 for

BTS3203E


MCS index 4 for

MCS index 5 for

MCS index 6 for

MCS index 7 for

MCS index 8 for

MCS index 9 for

MCS index 10 for

MCS index 11 for

MCS index 12 for

MCS index 13 for

BTS3203E


MCS index 14 for

MCS index 15 for

MCS index 16 for

MCS index 17 for

MCS index 18 for

MCS index 19 for

MCS index 20 for

MCS index 21 for

MCS index 22 for

MCS index 23 for

BTS3203E


MCS index 24 for

MCS index 25 for

MCS index 26 for

MCS index 27 for

MCS index 28 for

MCS index 29 for

MCS index 30 for

MCS index 31 for
1526728599 L.ChMeas.PRB.DL Number of PRBs on BTS3203E LTE:

.RANK1.MCS.0 the PDSCH in rank V100R006C00
1 mode using MCS
index 0 for

1 mode using MCS
index 1 for

BTS3203E


1 mode using MCS
index 2 for

1 mode using MCS
index 3 for

1 mode using MCS
index 4 for

1 mode using MCS
index 5 for

1 mode using MCS
index 6 for

1 mode using MCS
index 7 for

1 mode using MCS
index 8 for

1 mode using MCS
index 9 for

BTS3203E


1 mode using MCS
index 10 for

1 mode using MCS
index 11 for

1 mode using MCS
index 12 for

1 mode using MCS
index 13 for

1 mode using MCS
index 14 for

1 mode using MCS
index 15 for

1 mode using MCS
index 16 for

1 mode using MCS
index 17 for

BTS3203E


1 mode using MCS
index 18 for

1 mode using MCS
index 19 for

1 mode using MCS
index 20 for

1 mode using MCS
index 21 for

1 mode using MCS
index 22 for

1 mode using MCS
index 23 for

1 mode using MCS
index 24 for

1 mode using MCS
index 25 for

BTS3203E


1 mode using MCS
index 26 for

1 mode using MCS
index 27 for

1 mode using MCS
index 28 for

1 mode using MCS
index 29 for

1 mode using MCS
index 30 for

1 mode using MCS
index 31 for

2 mode using MCS
index 0 for

2 mode using MCS
index 1 for

BTS3203E


2 mode using MCS
index 2 for

2 mode using MCS
index 3 for

2 mode using MCS
index 4 for

2 mode using MCS
index 5 for

2 mode using MCS
index 6 for

2 mode using MCS
index 7 for

2 mode using MCS
index 8 for

2 mode using MCS
index 9 for

BTS3203E


2 mode using MCS
index 10 for

2 mode using MCS
index 11 for

2 mode using MCS
index 12 for

2 mode using MCS
index 13 for

2 mode using MCS
index 14 for

2 mode using MCS
index 15 for

2 mode using MCS
index 16 for

2 mode using MCS
index 17 for

BTS3203E


2 mode using MCS
index 18 for

2 mode using MCS
index 19 for

2 mode using MCS
index 20 for

2 mode using MCS
index 21 for

2 mode using MCS
index 22 for

2 mode using MCS
index 23 for

2 mode using MCS
index 24 for

2 mode using MCS
index 25 for

BTS3203E


2 mode using MCS
index 26 for

2 mode using MCS
index 27 for

2 mode using MCS
index 28 for

2 mode using MCS
index 29 for

2 mode using MCS
index 30 for

2 mode using MCS
index 31 for

3 mode using MCS
index 0 for

3 mode using MCS
index 1 for

BTS3203E


3 mode using MCS
index 2 for

3 mode using MCS
index 3 for

3 mode using MCS
index 4 for

3 mode using MCS
index 5 for

3 mode using MCS
index 6 for

3 mode using MCS
index 7 for

3 mode using MCS
index 8 for

3 mode using MCS
index 9 for

BTS3203E


3 mode using MCS
index 10 for

3 mode using MCS
index 11 for

3 mode using MCS
index 12 for

3 mode using MCS
index 13 for

3 mode using MCS
index 14 for

3 mode using MCS
index 15 for

3 mode using MCS
index 16 for

3 mode using MCS
index 17 for

BTS3203E


3 mode using MCS
index 18 for

3 mode using MCS
index 19 for

3 mode using MCS
index 20 for

3 mode using MCS
index 21 for

3 mode using MCS
index 22 for

3 mode using MCS
index 23 for

3 mode using MCS
index 24 for

3 mode using MCS
index 25 for

BTS3203E


3 mode using MCS
index 26 for

3 mode using MCS
index 27 for

3 mode using MCS
index 28 for

3 mode using MCS
index 29 for

3 mode using MCS
index 30 for

3 mode using MCS
index 31 for

4 mode using MCS
index 0 for

4 mode using MCS
index 1 for

BTS3203E


4 mode using MCS
index 2 for

4 mode using MCS
index 3 for

4 mode using MCS
index 4 for

4 mode using MCS
index 5 for

4 mode using MCS
index 6 for

4 mode using MCS
index 7 for

4 mode using MCS
index 8 for

4 mode using MCS
index 9 for

BTS3203E


4 mode using MCS
index 10 for

4 mode using MCS
index 11 for

4 mode using MCS
index 12 for

4 mode using MCS
index 13 for

4 mode using MCS
index 14 for

4 mode using MCS
index 15 for

4 mode using MCS
index 16 for

4 mode using MCS
index 17 for

BTS3203E


4 mode using MCS
index 18 for

4 mode using MCS
index 19 for

4 mode using MCS
index 20 for

4 mode using MCS
index 21 for

4 mode using MCS
index 22 for

4 mode using MCS
index 23 for

4 mode using MCS
index 24 for

4 mode using MCS
index 25 for

BTS3203E


4 mode using MCS
index 26 for

4 mode using MCS
index 27 for

4 mode using MCS
index 28 for

4 mode using MCS
index 29 for

4 mode using MCS
index 30 for

4 mode using MCS
index 31 for
None

BTS3203E
1.19.1 Number of Times an MCS Index Is Scheduled on the

PUSCH
Counters
1526727412 L.ChMeas.PUS Number of BTS3203E LTE L

CH.MCS.0 times MCS
index 0 is
scheduled on
the PUSCH

CH.MCS.1 times MCS
index 1 is
scheduled on
the PUSCH

CH.MCS.2 times MCS
index 2 is
scheduled on
the PUSCH

CH.MCS.3 times MCS
index 3 is
scheduled on
the PUSCH

CH.MCS.4 times MCS
index 4 is
scheduled on
the PUSCH

CH.MCS.5 times MCS
index 5 is
scheduled on
the PUSCH

CH.MCS.6 times MCS
index 6 is
scheduled on
the PUSCH

BTS3203E


CH.MCS.7 times MCS
index 7 is
scheduled on
the PUSCH

CH.MCS.8 times MCS
index 8 is
scheduled on
the PUSCH

CH.MCS.9 times MCS
index 9 is
scheduled on
the PUSCH

CH.MCS.10 times MCS
index 10 is
scheduled on
the PUSCH

CH.MCS.11 times MCS
index 11 is
scheduled on
the PUSCH

CH.MCS.12 times MCS
index 12 is
scheduled on
the PUSCH

CH.MCS.13 times MCS
index 13 is
scheduled on
the PUSCH

CH.MCS.14 times MCS
index 14 is
scheduled on
the PUSCH

BTS3203E


CH.MCS.15 times MCS
index 15 is
scheduled on
the PUSCH

CH.MCS.16 times MCS
index 16 is
scheduled on
the PUSCH

CH.MCS.17 times MCS
index 17 is
scheduled on
the PUSCH

CH.MCS.18 times MCS
index 18 is
scheduled on
the PUSCH

CH.MCS.19 times MCS
index 19 is
scheduled on
the PUSCH

CH.MCS.20 times MCS
index 20 is
scheduled on
the PUSCH

CH.MCS.21 times MCS
index 21 is
scheduled on
the PUSCH

CH.MCS.22 times MCS
index 22 is
scheduled on
the PUSCH

BTS3203E


CH.MCS.23 times MCS
index 23 is
scheduled on
the PUSCH

CH.MCS.24 times MCS
index 24 is
scheduled on
the PUSCH

CH.MCS.25 times MCS
index 25 is
scheduled on
the PUSCH

CH.MCS.26 times MCS
index 26 is
scheduled on
the PUSCH

CH.MCS.27 times MCS
index 27 is
scheduled on
the PUSCH

CH.MCS.28 times MCS
index 28 is
scheduled on
the PUSCH

CH.MCS.29 times MCS
index 29 is
scheduled on
the PUSCH

CH.MCS.30 times MCS
index 30 is
scheduled on
the PUSCH

BTS3203E


CH.MCS.31 times MCS
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,
DL/UL 16QAM, DL
64QAM

BTS3203E

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
LOFD-001006 DL/UL 16QAM, DL
64QAM
UL 64QAM

BTS3203E

GSM: None
UMTS: None
64QAM
UL 64QAM

GSM: None
UMTS: None
64QAM
UL 64QAM

GSM: None
UMTS: None
64QAM
UL 64QAM

GSM: None
UMTS: None
64QAM
UL 64QAM

GSM: None
UMTS: None
64QAM
UL 64QAM

BTS3203E

GSM: None
UMTS: None
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 BTS3203E LTE L

CH.MCS.0 times MCS
index 0 is
scheduled on
the PDSCH

CH.MCS.1 times MCS
index 1 is
scheduled on
the PDSCH

CH.MCS.2 times MCS
index 2 is
scheduled on
the PDSCH

CH.MCS.3 times MCS
index 3 is
scheduled on
the PDSCH

CH.MCS.4 times MCS
index 4 is
scheduled on
the PDSCH

BTS3203E


CH.MCS.5 times MCS
index 5 is
scheduled on
the PDSCH

CH.MCS.6 times MCS
index 6 is
scheduled on
the PDSCH

CH.MCS.7 times MCS
index 7 is
scheduled on
the PDSCH

CH.MCS.8 times MCS
index 8 is
scheduled on
the PDSCH

CH.MCS.9 times MCS
index 9 is
scheduled on
the PDSCH

CH.MCS.10 times MCS
index 10 is
scheduled on
the PDSCH

CH.MCS.11 times MCS
index 11 is
scheduled on
the PDSCH

CH.MCS.12 times MCS
index 12 is
scheduled on
the PDSCH

BTS3203E


CH.MCS.13 times MCS
index 13 is
scheduled on
the PDSCH

CH.MCS.14 times MCS
index 14 is
scheduled on
the PDSCH

CH.MCS.15 times MCS
index 15 is
scheduled on
the PDSCH

CH.MCS.16 times MCS
index 16 is
scheduled on
the PDSCH

CH.MCS.17 times MCS
index 17 is
scheduled on
the PDSCH

CH.MCS.18 times MCS
index 18 is
scheduled on
the PDSCH

CH.MCS.19 times MCS
index 19 is
scheduled on
the PDSCH

CH.MCS.20 times MCS
index 20 is
scheduled on
the PDSCH

BTS3203E


CH.MCS.21 times MCS
index 21 is
scheduled on
the PDSCH

CH.MCS.22 times MCS
index 22 is
scheduled on
the PDSCH

CH.MCS.23 times MCS
index 23 is
scheduled on
the PDSCH

CH.MCS.24 times MCS
index 24 is
scheduled on
the PDSCH

CH.MCS.25 times MCS
index 25 is
scheduled on
the PDSCH

CH.MCS.26 times MCS
index 26 is
scheduled on
the PDSCH

CH.MCS.27 times MCS
index 27 is
scheduled on
the PDSCH

CH.MCS.28 times MCS
index 28 is
scheduled on
the PDSCH

BTS3203E


CH.MCS.29 times MCS
index 29 is
scheduled on
the PDSCH

CH.MCS.30 times MCS
index 30 is
scheduled on
the PDSCH

CH.MCS.31 times MCS
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.
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

BTS3203E
Related Features
L.ChMeas.PDSCH.MCS.0 Multi-mode: None

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E

GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
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 BTS3203E LTE L

.UL.MCS.0 PRBs on the
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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E

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

BTS3203E

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

BTS3203E

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

BTS3203E

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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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

BTS3203E


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 DL 256QAM-enabled UEs, MCS index 28 is also 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,

BTS3203E
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,
64QAM
DL 2x2 MIMO

.MCS.1 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.2 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.3 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.4 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.5 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.6 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.7 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.8 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.9 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.10 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.11 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.12 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.13 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.14 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.15 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.16 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.17 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.18 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.19 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.20 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.21 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.22 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.23 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.24 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.25 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.26 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.27 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.28 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.29 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.30 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.31 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.0 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.1 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.2 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.3 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.4 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.5 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.6 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.7 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.8 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.9 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.10 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.11 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.12 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.13 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.14 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.15 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.16 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.17 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.18 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.19 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.20 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.21 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.22 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.23 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.24 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.25 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.26 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.27 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.28 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.29 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.30 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.31 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.0 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.1 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.2 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.3 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.4 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.5 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.6 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.7 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.8 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.9 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.10 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.11 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.12 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.13 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.14 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.15 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.16 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.17 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.18 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.19 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.20 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.21 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.22 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.23 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.24 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.25 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.26 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.27 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.28 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.29 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.30 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.31 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.0 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.1 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.2 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.3 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.4 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.5 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.6 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.7 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.8 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.9 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.10 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.11 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.12 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.13 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.14 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.15 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.16 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.17 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.18 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.19 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.20 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.21 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.22 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.23 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.24 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.25 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.26 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E

.MCS.27 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.28 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.29 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.30 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

.MCS.31 GSM: None
UMTS: None
64QAM
DL 2x2 MIMO

BTS3203E
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
1526726737 L.ChMeas.PRB.UL Average number of BTS3203E LTE:

.Used.Avg used uplink PRBs version earlier than
V100R003C00
1526726740 L.ChMeas.PRB.DL Average number of BTS3203E LTE:

.Used.Avg used PDSCH PRBs V100R006C00
1526727483 L.ChMeas.PRB.PU Average number of BTS3203E LTE:

CCH.Avg used PRBs over the V100R006C00
PUCCH
1526728299 L.ChMeas.PDCCH Number of times BTS3203E LTE:

.SymNum.1 that the PDCCH V100R006C00
occupies one OFDM
symbol

occupies two OFDM
symbols

occupies three
OFDM symbols

occupies four
OFDM symbols
1526728303 L.ChMeas.CCE.Co Number of PDCCH BTS3203E LTE:

mmUsed CCEs used for V100R005C00
common DCI
1526728304 L.ChMeas.CCE.U Number of PDCCH BTS3203E LTE:

LUsed CCEs used for V100R006C00
uplink DCI

BTS3203E

1526728305 L.ChMeas.CCE.D Number of PDCCH BTS3203E LTE:

LUsed CCEs used for V100R006C00
downlink DCI
1526728340 L.ULCoMP.RB Average number of BTS3203E LTE:

scheduled PRBs for V100R006C00
UL CoMP

.SCell.Used.Avg downlink PRBs V100R006C00
occupied by CA
UEs that use the
local cell as their
secondary serving
cell
1526728433 L.ChMeas.PRB.DL Number of available BTS3203E LTE:

.Avail downlink PRBs V100R006C00
1526728434 L.ChMeas.PRB.UL Number of available BTS3203E LTE:

.Avail uplink PRBs V100R006C00

.CEU.Used.Avg PRBs used by uplink V100R006C00
CEUs in a cell

.CEU.Used.Avg PRBs used by V100R006C00
downlink CEUs in a
cell

.FSS.Avg PRBs allocated for V100R006C00
uplink frequency
selective scheduling

.FSS.Avg PRBs allocated for V100R006C00
downlink frequency
selective scheduling

.PreSch.Used.Avg PRBs allocated for V100R006C00
uplink pre-
scheduling
1526728664 L.ChMeas.PDCCH Number of times of BTS3203E LTE:

.DL.DTXNum.Agg DTX for PDCCH V100R006C00
Lvl1 resource allocation
with aggregation
level 1 in a cell

BTS3203E


with aggregation
level 2 in a cell

with aggregation
level 4 in a cell

with aggregation
level 8 in a cell

.AggLvl1Num PDCCH resource V100R006C00
allocations with
aggregation level 1

allocations with
aggregation level 2

allocations with
aggregation level 4

allocations with
aggregation level 8

.DrbUsed.Avg PRBs used by V100R006C00
PUSCH DRBs

.DrbUsed.Avg PRBs used by V100R006C00
PDSCH DRBs

SCH.Avg used PUSCH PRBs V100R006C00
1526728765 L.ChMeas.CCE.Av Number of available BTS3203E LTE:

ail PDCCH CCEs V100R006C00

BTS3203E


LUsed.DRB CCEs used for initial V100R006C00
transmitted
downlink data in a
cell

LUsed.SRB CCEs used for initial V100R006C00
transmitted
downlink signaling
in a cell

LUsed.MCE CCEs used for initial V100R006C00
transmitted
downlink MCEs in a
cell

LUsed.Equivalent CCEs with the CCE V100R006C00
power equivalent to
the reference power
used for uplink DCI

LUsed.Equivalent CCEs with the CCE V100R006C00
power equivalent to
the reference power
used for downlink
DCI
1526729909 L.ChMeas.PRB.eI Average number of BTS3203E LTE:

CIC.CEU.DL.Used downlink PRBs used V100R007C00
.Avg on an ABS by UEs
in a cell that are
close to the border
with the other type
of cells and support
eICIC in a
heterogeneous
network
1526729910 L.ChMeas.PRB.eI Average number of BTS3203E LTE:

CIC.CEU.UL.Used uplink PRBs used on V100R007C00
.Avg an ABS by users in a
cell that are close to
the border with the
other type of cells
and support eICIC in
a heterogeneous
network

BTS3203E


.SrbUsed.Avg PRBs used by V100R007C00
downlink signaling
in a cell

.PagingUsed.Avg PRBs used by V100R007C00
paging messages in
a cell
1526730842 L.ChMeas.PUSCH. Number of initial BTS3203E LTE:

DmrsTaSch uplink transmissions V100R011C10
of DMRS TA in a
cell
1526730843 L.ChMeas.PUSCH. Number of uplink BTS3203E LTE:

DmrsTaSch.Retran retransmissions of V100R011C10
s DMRS TA in a cell
1526730844 L.ChMeas.CCE.U Number of uplink BTS3203E LTE:

L.AllocFail CCE allocation V100R011C10
failures in a cell
1526730845 L.ChMeas.CCE.D Number of downlink BTS3203E LTE:

L.AllocFail CCE allocation V100R011C10
failures in a cell

.DrbUsed.Avg.VoIP PRBs used by DRBs V100R011C10
on the PDSCH for
downlink VoIP
services

.DrbUsed.Avg.VoIP PRBs used by DRBs V100R011C10
on the PUSCH for
uplink VoIP services
1526732697 L.ChMeas.PRB.PU Number of samples BTS3203E LTE:

SCH.Util.Samp.Ind where the PUSCH V100R011C10
ex0 PRB usage is within
the range of [0,
10%)

the range of [10%,
20%)

BTS3203E


the range of [20%,
30%)

the range of [30%,
40%)

the range of [40%,
50%)

the range of [50%,
60%)

the range of [60%,
70%)

the range of [70%,
80%)

the range of [80%,
90%)

ex9 PRB usage is greater
than or equal to 90%

.TaSch.Used.Avg PRBs allocated for V100R011C10
uplink TA
measurement

BTS3203E


LUsed.TA CCEs allocated for V100R011C10
TA measurement
1526732727 L.ChMeas.PRB.PD Number of samples BTS3203E LTE:

SCH.Util.Samp.Ind where the PDSCH V100R011C10
ex0 PRB usage falls
within the range of
[0, 10%)

ex1 PRB usage falls
within the range of
[10%, 20%)

ex2 PRB usage falls
within the range of
[20%, 30%)

ex3 PRB usage falls
within the range of
[30%, 40%)

ex4 PRB usage falls
within the range of
[40%, 50%)

ex5 PRB usage falls
within the range of
[50%, 60%)

ex6 PRB usage falls
within the range of
[60%, 70%)

ex7 PRB usage falls
within the range of
[70%, 80%)

BTS3203E


ex8 PRB usage falls
within the range of
[80%, 90%)

ex9 PRB usage is greater
than or equal to 90%
1526732912 L.ChMeas.PRB.DL Number of downlink BTS3203E LTE:

.SCell.RelaxedBack PRBs occupied by V100R011C10
haulCAUsed.Avg inter-eNodeB CA
UEs that treat the
local cell as their
SCell
1526733175 L.ULCoMP.Hetnet Average number of BTS3203E LTE:

CoMP.RB scheduled RBs for V100R011C10
HetNet UL CoMP in
a cell
1526733196 L.ChMeas.ULCoM Average number of BTS3203E LTE:

PPhase2.PRB.Avg scheduled PRBs for V100R011C10
intra-BBU inter-
BBP UL CoMP in a
cell
1526733197 L.ChMeas.ULOver Average number of BTS3203E LTE:

BBUCoMP.PRB.Av scheduled PRBs for V100R011C10
g inter-BBU UL
CoMP in a cell

LUsed.VoIP CCEs used for V100R011C10
uplink VoIP services

LUsed.VoIP CCEs used for V100R011C10
downlink VoIP
services
1526737748 L.ChMeas.PRB.DL Number of PRBs of BTS3203E LTE:

.AICIC.CEB.Avg the downlink edge V100R011C10
band configured for
the cell in adaptive
ICIC

BTS3203E

1526737753 L.ChMeas.PRB.Int Average number of BTS3203E LTE:

erEnbDLComp.Us PRBs used for inter- V100R011C10
ed.Avg eNodeB DL CoMP
1526737761 L.ChMeas.PRB.UL Number of used BTS3203E LTE:

.ULShared.Used.A uplink PRBs on the V100R011C10
vg PUSCH on the
UMTS and LTE
shared spectrum in a
cell
1526737762 L.ChMeas.ULRela Average number of BTS3203E LTE:

xedBHCoMP.PRB. PRBs scheduled for V100R011C10
Avg relaxed-backhaul-
based UL CoMP in
a cell
1526737816 L.ChMeas. Average number of BTS3203E LTE:

3SectorULCoMP.P scheduled PRBs for V100R011C10
RB.Avg 3-cell UL CoMP in
a cell

LUsed.SRB CCEs used for initial V100R011C10
transmitted uplink
signaling in a cell
1526739747 L.ChMeas.PDCCH Number of times an BTS3203E LTE:

.UL.AggLvl1Num eNodeB allocates V100R011C10
the PDCCHs with
aggregation level 1
for uplink
scheduling

the PDCCHs with
aggregation level 2
for uplink
scheduling

the PDCCHs with
aggregation level 4
for uplink
scheduling

BTS3203E


the PDCCHs with
aggregation level 8
for uplink
scheduling
1526739817 L.ChMeas.Dl.ePD Number of times BTS3203E LTE:

CCH.AggLvl1Num downlink ePDCCH V100R011C10
with aggregation
level 1

with aggregation
level 2

with aggregation
level 4

with aggregation
level 8

CCH.AggLvl16Nu downlink ePDCCH V100R011C10
m resource allocations
with aggregation
level 16

CCH.AggLvl32Nu downlink ePDCCH V100R011C10
with aggregation
level 32
1526739823 L.ChMeas.Ul.ePD Number of times BTS3203E LTE:

CCH.AggLvl1Num uplink ePDCCH V100R011C10
with aggregation
level 1

BTS3203E


with aggregation
level 2

with aggregation
level 4

with aggregation
level 8

CCH.AggLvl16Nu uplink ePDCCH V100R011C10
with aggregation
level 16

CCH.AggLvl32Nu uplink ePDCCH V100R011C10
with aggregation
level 32
1526739829 L.ChMeas.ePDCC Number of times BTS3203E LTE:

H.DL.DTXNum.Ag DTX is detected for V100R011C10
gLvl1 downlink ePDCCH
with aggregation
level 1 in a cell

with aggregation
level 2 in a cell

with aggregation
level 4 in a cell

BTS3203E


with aggregation
level 8 in a cell

with aggregation
level 16 in a cell

with aggregation
level 32 in a cell
1526740435 L.ChMeas.eCCE.D Number of ePDCCH BTS3203E LTE:

LUsed.DRB eCCEs used by V100R011C10
downlink data

LUsed.MCE eCCEs used by V100R011C10
downlink MCEs

LUsed.SRB eCCEs used by V100R011C10
downlink signaling
messages

SCH.Avg.BorderU PUSCH PRBs V100R011C10
E occupied by CEUs
in a cell
1526741767 L.ChMeas.PRB.PD Average number of BTS3203E LTE:

SCH.Avg.BorderU PDSCH PRBs V100R011C10
E occupied by CEUs
in a cell

.DrbUsed.Avg.QCI PRBs used by DRBs V100R011C10
2 on the PUSCH for
uplink QCI2
services

BTS3203E


SCH.Avg.BorderU PRBs used by the V100R012C00
E.JointReception PUSCH for joint
reception CEUs in a
cell
1526743767 L.ChMeas.PRB.PD Average number of BTS3203E LTE:

SCH.Avg.BorderU PRBs used by the V100R012C00
E.JointTransmit PDSCH for joint
transmission CEUs
in a cell
1526745765 L.ChMeas.CCE.Av Maximum number BTS3203E LTE:

ail.Max of available PDCCH V100R012C10
CCEs in a cell
1526745766 L.ChMeas.CCE.U Maximum number BTS3203E LTE:

L.Avail.Max of available uplink V100R012C10
PDCCH CCEs in a
cell

.PDSCH.WBBUsed downlink PDSCH V100R012C10
.Avg PRBs used by WBB
Ues

SCH.WBBUsed.Av uplink PUSCH V100R012C10
g PRBs used by WBB
Ues

6 on the PDSCH for
downlink QCI6
services

7 on the PDSCH for
downlink QCI7
services

8 on the PDSCH for
downlink QCI8
services

BTS3203E


9 on the PDSCH for
downlink QCI9
services

6 on the PUSCH for
uplink QCI6
services

7 on the PUSCH for
uplink QCI7
services

8 on the PUSCH for
uplink QCI8
services

9 on the PUSCH for
uplink QCI9
services

.DrbUsed.Avg.QCI uplink PUSCH V100R012C10
65 PRBs used by DRBs
for QCI 65 services

.DrbUsed.Avg.QCI uplink PUSCH V100R012C10
for QCI 66 services

.DrbUsed.Avg.QCI downlink PDSCH V100R012C10
for QCI 65 services

.DrbUsed.Avg.QCI downlink PDSCH V100R012C10
for QCI 66 services

BTS3203E
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.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.DL.Used.A L.ChMeas.PRB.DL.DrbUse -
vg d.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.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 -

BTS3203E
1.20.1 Number of Used Uplink PRBs

Counters
1526726737 L.ChMeas.PRB Average BTS3203E LTE L

.UL.Used.Avg number of used
uplink PRBs
1526728340 L.ULCoMP.RB Average BTS3203E LTE L

number of
scheduled PRBs
for UL CoMP

.UL.DrbUsed.A number of
vg PRBs used by
PUSCH DRBs

.PUSCH.Avg number of used
PUSCH PRBs

vg.VoIP PRBs used by
DRBs on the
PUSCH for
uplink VoIP
services
1526733175 L.ULCoMP.Het Average BTS3203E LTE L

netCoMP.RB number of
scheduled RBs
for HetNet UL
CoMP in a cell
1526733196 L.ChMeas.ULC Average BTS3203E LTE L

oMPPhase2.PR number of
B.Avg scheduled PRBs
for intra-BBU
inter-BBP UL
CoMP in a cell
1526733197 L.ChMeas.ULO Average BTS3203E LTE L

verBBUCoMP. number of
PRB.Avg scheduled PRBs
for inter-BBU
UL CoMP in a
cell

BTS3203E

1526737762 L.ChMeas.ULR Average BTS3203E LTE L

elaxedBHCoM number of
P.PRB.Avg PRBs scheduled
for relaxed-
backhaul-based
UL CoMP in a
cell
1526737816 L.ChMeas. Average BTS3203E LTE L

3SectorULCoM number of
P.PRB.Avg scheduled PRBs
for 3-cell UL
CoMP in a cell

vg.QCI2 PRBs used by
DRBs on the
PUSCH for
uplink QCI2
services

.PUSCH.WBB number of
Used.Avg uplink PUSCH
PRBs used by
WBB Ues

DRBs on the
PUSCH for
uplink QCI6
services

DRBs on the
PUSCH for
uplink QCI7
services

DRBs on the
PUSCH for
uplink QCI8
services

BTS3203E


DRBs on the
PUSCH for
uplink QCI9
services

vg.QCI65 uplink PUSCH
PRBs used by
DRBs for QCI
65 services

vg.QCI66 uplink PUSCH
PRBs used by
DRBs for QCI
66 services
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-eNodeB inter-BBP UL CoMP is performed and inter-
eNodeB UL CoMP is not performed in a cell. It is used to analyze the usage of PRBs for UEs
for whom intra-eNodeB inter-BBP UL CoMP is performed.
The L.ULIC.RB counter measures the average number of PRBs used by UEs for which uplink
IC is used. It is used to analyze the usage of PRBs for such UEs.
L.ChMeas.ULOverBBUCoMP.PRB.Avg counter measures the average number of PRBs used
by UEs selected for whom inter-eNodeB UL CoMP based on coordinated eNodeB is
performed. It is used to analyze the usage of PRBs for UEs for whom inter-eNodeB UL
CoMP based on coordinated eNodeB is performed.
The L.ChMeas.ULRelaxedBHCoMP.PRB.Avg counter measures the average number of PRBs
used by UEs selected for whom inter-eNodeB UL CoMP Based on Relaxed Backhaul is

BTS3203E
performed. It is used to analyze the usage of PRBs for UEs for whom inter-eNodeB 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.ChMeas.PRB.UL.CoordResAllocProtectUser.Used.Avg counter measures the average
number of PRBs used by UL-CRA-protected UEs within a measurement period in a cell. This
counter is used to analyze the PRB usage of UL-CRA-protected UEs. UL CRA is short for
uplink coordinated resource allocation.
The L.ChMeas.PRB.UL.DrbUsed.Avg.QCI65 and L.ChMeas.PRB.UL.DrbUsed.Avg.QCI66
counters measure the number of uplink PRBs used by LiTRA services.
The L.ULCoMP.HetnetCoMP.RB, L.ChMeas.ULRelaxedBHCoMP.PRB.Avg, and
L.ChMeas.PRB.UL.CoordResAllocProtectUser.Used.Avg counters apply to only LTE FDD.
Measurement Points
During a measurement period, the following are measured in a cell:
- Average number of PRBs used by all uplink channels per millisecond
- Average number of used PUSCH PRBs per millisecond
- Average number of PUSCH PRBs used by DRBs per millisecond
- Average number of PUSCH PRBs used by DRBs for VoLTE services per millisecond
- Average number of PRBs used by WBB UEs per millisecond
- Average number of PRBs used by DRBs on the PUSCH for QCIs 6, 7, 8, and 9 services per
millisecond(in an SFN cell, the number of used PRBs of all physical cells corresponding to all
sectors is accumulated)
- Average number of PRBs used by UL CoMP UEs per millisecond.
- Average number of PUSCH PRBs used by DRBs for QCI 65 services per millisecond
- Average number of PUSCH PRBS used by DRBs for QCI 66 services per millisecond
Only after the uplink data is correctly parsed and recognized that it is transmitted on DRBs,
the number of PUSCH PRBs used by 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 feedback was NACK and then ACK at last, the number of used PRBs
for data with NACK feedback is estimated based on the data with ACK feedback. 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-eNodeB inter-BBP UL CoMP is performed and inter-
eNodeB 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.

BTS3203E
For UEs selected for whom inter-eNodeB UL CoMP based on coordinated eNodeB 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-eNodeB 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.
The average number of PRBs per millisecond used by UL-CRA-protected UEs is measured in
a measurement period and is taken as the
L.ChMeas.PRB.UL.CoordResAllocProtectUser.Used.Avg counter value.
For UEs selected for which uplink IC is used, the average number of PRBs per millisecond is
measured and taken as the L.ULIC.RB counter value.
For LTE TDD, the L.ChMeas.PRB.UL.Used.Avg and L.ChMeas.PRB.UL.DrbUsed.Avg

counters measure the number of PRBs used for a cell. These counters are incremented only by
1 if a PRB is used simultaneously. Other counters in this function subset measure the actual
number of PRBs used for UE scheduling in a cell. These counters are incremented by the
number of UEs if these UEs use the same PRB.
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-081219 Inter-eNodeB VoLTE CoMP
LOFD-120205 Deep Coverage
Improvement for Video

BTS3203E
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

d.Avg.VoIP GSM: None
UMTS: None
L.ULCoMP.HetnetCoMP.R Multi-mode: None

B GSM: None
UMTS: None
L.ChMeas.ULCoMPPhase2. Multi-mode: None

PRB.Avg GSM: None
UMTS: None
L.ChMeas.ULRelaxedBHC Multi-mode: None

oMP.PRB.Avg GSM: None
UMTS: None
L.ChMeas. Multi-mode: None

3SectorULCoMP.PRB.Avg GSM: None
UMTS: None

d.Avg.QCI2 GSM: None
UMTS: None

BTS3203E
L.ChMeas.PRB.PUSCH.W Multi-mode: None

BBUsed.Avg GSM: None
UMTS: None
Management

UMTS: None

UMTS: None

UMTS: None

UMTS: None

UMTS: None
LTE: LTROFD-111201 MCPTT QoS Management

UMTS: None

BTS3203E
1.20.2 Number of Used Downlink PRBs

Counters

.DL.Used.Avg number of used
PDSCH PRBs

.DL.DrbUsed.A number of
vg PRBs used by
PDSCH DRBs

.DL.SrbUsed.A number of
vg PRBs used by
downlink
signaling in a
cell

.DL.PagingUse number of
d.Avg PRBs used by
paging
messages in a
cell

vg.VoIP PRBs used by
DRBs on the
PDSCH for
downlink VoIP
services

.DL.PDSCH.W number of
BBUsed.Avg downlink
PDSCH PRBs
used by WBB
Ues

DRBs on the
PDSCH for
downlink QCI6
services

BTS3203E


DRBs on the
PDSCH for
downlink QCI7
services

DRBs on the
PDSCH for
downlink QCI8
services

DRBs on the
PDSCH for
downlink QCI9
services

vg.QCI65 downlink
PDSCH PRBs
used by DRBs
for QCI 65
services

vg.QCI66 downlink
PDSCH PRBs
used by DRBs
for QCI 66
services
Description
The counters measure the average number of used PDSCH PRBs and the average number of
service-specific used PDSCH PRBs. 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.

BTS3203E
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.
The L.ChMeas.PRB.DL.DrbUsed.Avg.QCI.6 to L.ChMeas.PRB.DL.DrbUsed.Avg.QCI.9
counters are used to analyze the PDSCH PRB usage of specific services.
The L.ChMeas.PRB.DL.PDSCH.WBBUsed.Avg counter is used to analyze the downlink
PRB usage of WBB UEs.
L.ChMeas.PRB.DL.DrbUsed.Avg.QCI65 and L.ChMeas.PRB.DL.DrbUsed.Avg.QCI66
counters measure the number of downlink PRBs used by LiTRA services.
Measurement Points
During a measurement period, the following are measured in a cell:
- Average number of used PDSCH PRBs per millisecond
- Average number of PDSCH PRBs used by DRBs per millisecond
- Average number of PDSCH PRBs used by signaling (including SRB0, SRB1, and SRB2)
per millisecond
- Average number of PDSCH PRBs used by paging messages per millisecond
- Average number of PDSCH PRBs used by DRBs for VoLTE services per millisecond
- Average number of PDSCH PRBs used by DRBs for specific QCI services per millisecond
- Average number of PDSCH PRBs used by WBB UEs per millisecond
- Average number of PRBs used by DRBs on the PDSCH for QCIs 6, 7, 8, and 9 services per
millisecond(if SFN cells are configured, the number of PRBs used for physical cells of each
sector is accumulated; if virtual 4T4R cells are configured, the number of PRBs used for each
beam is accumulated)
- Average number of PDSCH PRBs used by DRBs for QCI 65 services per millisecond
- Average number of PDSCH PRBS used by DRBs for QCI 66 services per millisecond
In an SFN cell, the number of PRBs used in each physical cell is accumulated. In a cell with
virtual 4T4R enabled, the number of PRBs used on all beams is accumulated.
In 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.
For LTE TDD, the L.ChMeas.PRB.DL.Used.Avg, L.ChMeas.PRB.DL.DrbUsed.Avg, and
L.ChMeas.PRB.DL.SrbUsed.Avg counters measure the number of PRBs used for a cell.
These counters are incremented only by 1 if a PRB is used simultaneously. Other counters in
this function subset measure the actual number of PRBs used for UE scheduling in a cell.
These counters are incremented by the number of UEs if these UEs use the same PRB.

BTS3203E
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
L.ChMeas.PRB.DL.PDSCH Multi-mode: None

.WBBUsed.Avg GSM: None
UMTS: None
Management

BTS3203E

UMTS: None

UMTS: None

UMTS: None

UMTS: None

UMTS: None

UMTS: None
1.20.3 Number of Used PUCCH PRBs

Counters

.PUCCH.Avg number of used
PRBs over the
PUCCH

BTS3203E
Description
The counter measures the average number of used PUCCH PRBs in a cell. It is used to
analyze the usage of PRBs over the PUCCH.
Measurement Points
During a measurement period, the average number of used PUCCH PRBs is measured in a
cell per millisecond.
Formula
None
Unit
None
Related Features
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 BTS3203E LTE L

CH.SymNum.1 times that the
PDCCH
occupies one
OFDM symbol

PDCCH
occupies two
OFDM symbols

BTS3203E


PDCCH
occupies three
OFDM symbols

PDCCH
occupies four
OFDM symbols
Description
The counters measure the number of times that the PDCCH occupies n OFDM symbols in a
cell, where n ranges from 1 to 3.
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
Management

BTS3203E

m.2 GSM: None
UMTS: None
Management

m.3 GSM: None
UMTS: None
Management

m.4 GSM: None
UMTS: None
Management
1.20.5 Number of PDCCH CCEs used in a cell

Counters
1526728303 L.ChMeas.CCE Number of BTS3203E LTE L

.CommUsed PDCCH CCEs
used for
common DCI

.ULUsed PDCCH CCEs
used for uplink
DCI

.DLUsed PDCCH CCEs
used for
downlink DCI

.Avail available
PDCCH CCEs

BTS3203E


.DLUsed.DRB PDCCH CCEs
used for initial
transmitted
downlink data
in a cell

.DLUsed.SRB PDCCH CCEs
used for initial
transmitted
downlink
signaling in a
cell

.DLUsed.MCE PDCCH CCEs
used for initial
transmitted
downlink
MCEs in a cell

.ULUsed.Equiv PDCCH CCEs
alent with the CCE
power
equivalent to
the reference
power used for
uplink DCI

.DLUsed.Equiv PDCCH CCEs
alent with the CCE
power
equivalent to
the reference
power used for
downlink DCI

.ULUsed.TA PDCCH CCEs
allocated for TA
measurement

.ULUsed.VoIP PDCCH CCEs
used for uplink
VoIP services

BTS3203E


.DLUsed.VoIP PDCCH CCEs
used for
downlink VoIP
services

.ULUsed.SRB PDCCH CCEs
used for initial
transmitted
uplink signaling
in a cell
Description
The counters measure the following items:
- Number of available CCEs in a cell
- Number of PDCCH CCEs used for uplink DCI in a cell
- Number of PDCCH CCEs used for downlink DCI in a cell (including only downlink
PDCCH CCEs in the UE-specific search spaces)
- Number of PDCCH CCEs used for common DCI in a cell (including downlink PDCCH
CCEs in the common search spaces such as CCEs used for power control in semi-persistent
scheduling, CCEs used by paging messages, CCEs used by system information, and CCEs
used by RAR messages)
- 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

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

BTS3203E
Unit
None
Related Features
L.ChMeas.CCE.CommUsed Multi-mode: None

GSM: None
UMTS: None
Management
L.ChMeas.CCE.ULUsed Multi-mode: None

GSM: None
UMTS: None
Management
L.ChMeas.CCE.DLUsed Multi-mode: None

GSM: None
UMTS: None
Management
L.ChMeas.CCE.Avail Multi-mode: None

GSM: None
UMTS: None
Management
L.ChMeas.CCE.DLUsed.D Multi-mode: None

RB GSM: None
UMTS: None
LBFD-002016 Management
Dynamic Downlink Power
Allocation
L.ChMeas.CCE.DLUsed.SR Multi-mode: None

B GSM: None
UMTS: None
Allocation

BTS3203E
L.ChMeas.CCE.DLUsed.M Multi-mode: None

CE GSM: None
UMTS: None
Allocation
L.ChMeas.CCE.ULUsed.Eq Multi-mode: None

uivalent GSM: None
UMTS: None
Allocation
L.ChMeas.CCE.DLUsed.Eq Multi-mode: None

uivalent GSM: None
UMTS: None
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
Allocation
L.ChMeas.CCE.DLUsed.Vo Multi-mode: None

IP GSM: None
UMTS: None
Allocation

BTS3203E
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.SCell.Used number of
.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 treat the local cell as
their SCell.
Measurement Points
The average number of PDSCH PRBs per millisecond occupied by CA UEs that treat the
local cell as their SCell is measured within a measurement period.
Formula
None
Unit
None

BTS3203E
Related Features
L.ChMeas.PRB.DL.SCell.U Multi-mode: None

sed.Avg GSM: None
UMTS: None
LTE: LAOFD-00100101 Intra-Band Carrier
LAOFD-00100102 Aggregation for Downlink
2CC in 20MHz
LAOFD-070201
Inter-Band Carrier
Aggregation for Downlink
2CC in 20MHz
Flexible CA from Multiple
Carriers
1.20.7 Average Number of Available PRBs in a Cell
Counters

.DL.Avail available
downlink PRBs

.UL.Avail available uplink
PRBs
Description
The counters measure the number of available uplink or downlink PRBs, the counter values
are the total number of PRBs in each physical cell. In a cell with customized bandwidth, the
actually usable PRBs are measured.
Measurement Points
The number of available downlink or uplink PRBs in a cell is sampled per second. At the end
of a measurement period, the average of these sampling results is used as the counter value.
Formula
None

BTS3203E
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
LEOFD-111305
Carrier Aggregation for
Downlink 2CC in 40MHz
Virtual 4T4R
L.ChMeas.PRB.UL.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
Carrier Aggregation for
Downlink 2CC in 40MHz
1.20.8 Average Number of PRBs Used by ICIC CEUs in a Cell

Counters

.UL.CEU.Used. number of
Avg PRBs used by
uplink CEUs in
a cell

.DL.CEU.Used. number of
Avg PRBs used by
downlink CEUs
in a cell

BTS3203E
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
None
1.20.9 Average Number of PRBs Allocated for Frequency Selective

Scheduling
Counters

.UL.FSS.Avg number of
PRBs allocated
for uplink
frequency
selective
scheduling

.DL.FSS.Avg number of
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.

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

BTS3203E
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.
For LTE TDD, this counter measures the actual number of PRBs used for UE scheduling in a
cell. This counter is incremented by the number of UEs if these UEs use the same PRB.
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
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
m.AggLvl1 for PDCCH
resource
allocation with
aggregation
level 1 in a cell

BTS3203E


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

BTS3203E
Related Features
L.ChMeas.PDCCH.DL.DT Multi-mode: None

XNum.AggLvl1 GSM: None
UMTS: None
Management

UMTS: None
Management

UMTS: None
Management

UMTS: None
Management
1.20.12 Number of Times of Successful PDCCH Resource

Allocations with a Specific Aggregation Level
Counters

CH.AggLvl1Nu times of
m PDCCH
resource
allocations with
aggregation
level 1

BTS3203E


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

BTS3203E
Related Features
L.ChMeas.PDCCH.AggLvl Multi-mode: None

1Num GSM: None
UMTS: None
Management

2Num GSM: None
UMTS: None
Management

4Num GSM: None
UMTS: None
Management

8Num GSM: None
UMTS: None
Management

BTS3203E
1.20.13 Average Number of PRBs Used on an ABS by UEs in a

Cell that Are Close to the Border with the Other Type of Cells
and Support eICIC in a Heterogeneous Network
Counters

.eICIC.CEU.DL number of
.Used.Avg downlink PRBs
used on an ABS
by UEs in a cell
that are close to
the border with
the other type
of cells and
support eICIC
in a
heterogeneous
network
Description
The counter measures the average number of downlink PRBs used on an ABS by UEs in a
cell that are close to the border with the other type of cells and support eICIC in a
heterogeneous network.
Measurement Points
Within a performance measurement period, the eNodeB measures and accumulates the
number of downlink PRBs used on each ABS by UEs in a cell that are close to the border
with the other type of cells and support eICIC in a heterogeneous network. At the end of the
measurement period, the average number of used downlink PRBs is reported.
Formula
None
Unit
None
Related Features
None

BTS3203E
1.20.14 Average Number of PRBs Used on an ABS by UEs in a

Cell that Are Close to the Border with the Other Type of Cells
and Support eICIC in a Heterogeneous Network
Counters

.eICIC.CEU.UL number of
.Used.Avg uplink PRBs
used on an ABS
by users in a
cell that are
close to the
border with the
other type of
cells and
support eICIC
in a
heterogeneous
network
Description
The counter measures the average number of uplink PRBs used on an ABS by UEs in a cell
that are close to the border with the other type of cells and support eICIC in a heterogeneous
network.
Measurement Points
Within a performance measurement period, the eNodeB measures and accumulates the
number of uplink PRBs used on each ABS by UEs in a cell that are close to the border with
the other type of cells and support eICIC in a heterogeneous network. At the end of the
measurement period, the average number of used uplink PRBs is reported.
Formula
None
Unit
None
Related Features
None

BTS3203E
1.20.15 Number of Times of DMRS TA Scheduling in a cell
Counters

CH.DmrsTaSch initial uplink
transmissions 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

BTS3203E
1.20.16 Number of Times of DMRS TA Scheduling in a cell
Counters

CH.DmrsTaSch uplink
.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.Retrans GSM: None
UMTS: None

BTS3203E
1.20.17 Number of CCE Allocation Failures in a Cell

Counters

.UL.AllocFail uplink CCE
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

BTS3203E
1.20.18 Number of CCE Allocation Failures in a Cell

Counters

.DL.AllocFail downlink CCE
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.DL.AllocFa Multi-mode: None

il GSM: None
UMTS: None
Management

BTS3203E
1.20.19 PUSCH PRB Usage Distribution

Counters

.PUSCH.Util.Sa samples where
mp.Index0 the PUSCH
PRB usage is
within the range
of [0, 10%)

mp.Index1 the PUSCH
PRB usage is
within the range
of [10%, 20%)

mp.Index2 the PUSCH
PRB usage is
within the range
of [20%, 30%)

mp.Index3 the PUSCH
PRB usage is
within the range
of [30%, 40%)

mp.Index4 the PUSCH
PRB usage is
within the range
of [40%, 50%)

mp.Index5 the PUSCH
PRB usage is
within the range
of [50%, 60%)

BTS3203E


mp.Index6 the PUSCH
PRB usage is
within the range
of [60%, 70%)

mp.Index7 the PUSCH
PRB usage is
within the range
of [70%, 80%)

mp.Index8 the PUSCH
PRB usage is
within the range
of [80%, 90%)

mp.Index9 the PUSCH
PRB usage is
greater than or
equal to 90%
Description
The counters measure the distribution of the PUSCH PRB usage in different ranges to
indicate the use of uplink PRBs.
Measurement Points
The number of used PUSCH PRBs and the number of available PUSCH PRBs in each TTI in
a cell (in a cell with non-standard bandwidth, the numbers of actual used PRBs and available
PRBs are measureds) 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.
Formula
None
Unit
None

BTS3203E
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
LBFD-002025 Downlink 2CC in 40MHz
Basic Scheduling

UMTS: None
Basic Scheduling

UMTS: None
Basic Scheduling

UMTS: None
Basic Scheduling

UMTS: None
Basic Scheduling

BTS3203E

UMTS: None
Basic Scheduling

UMTS: None
Basic Scheduling

UMTS: None
Basic Scheduling

UMTS: None
Basic Scheduling

UMTS: None
Basic Scheduling

BTS3203E
1.20.20 Average Number of PRBs Allocated for Uplink TA

Measurement
Counters

.UL.TaSch.Use number of
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.
Measurement Points
During a measurement period, the average number of PRBs allocated for uplink TA
measurement is measured in a cell per millisecond.
Formula
None
Unit
None
Related Features
L.ChMeas.PRB.UL.TaSch. Multi-mode: None

Used.Avg GSM: None
UMTS: None

BTS3203E
1.20.21 PDSCH PRB Usage Distribution

Counters

.PDSCH.Util.Sa samples where
mp.Index0 the PDSCH
PRB usage falls
within the range
of [0, 10%)

mp.Index1 the PDSCH
PRB usage falls
within the range
of [10%, 20%)

mp.Index2 the PDSCH
PRB usage falls
within the range
of [20%, 30%)

mp.Index3 the PDSCH
PRB usage falls
within the range
of [30%, 40%)

mp.Index4 the PDSCH
PRB usage falls
within the range
of [40%, 50%)

mp.Index5 the PDSCH
PRB usage falls
within the range
of [50%, 60%)

BTS3203E


mp.Index6 the PDSCH
PRB usage falls
within the range
of [60%, 70%)

mp.Index7 the PDSCH
PRB usage falls
within the range
of [70%, 80%)

mp.Index8 the PDSCH
PRB usage falls
within the range
of [80%, 90%)

mp.Index9 the PDSCH
PRB usage is
greater than or
equal to 90%
Description
The counters measure the distribution of the PDSCH PRB usage in different ranges to
indicate the use of downlink PRBs.
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 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 that are combined into a cell are accumulated.

BTS3203E
Formula
None
Unit
None
Related Features
L.ChMeas.PRB.PDSCH.Uti Multi-mode: None

UMTS: None
Basic Scheduling

UMTS: None
Basic Scheduling

UMTS: None
Basic Scheduling

UMTS: None
Basic Scheduling

BTS3203E

UMTS: None
Basic Scheduling

UMTS: None
Basic Scheduling

UMTS: None
Basic Scheduling

UMTS: None
Basic Scheduling

UMTS: None
Basic Scheduling

BTS3203E

UMTS: None
Basic Scheduling
1.20.22 Number of Downlink PRBs Occupied by CA UEs in the

Relaxed-Backhaul-based Inter-eNodeB CA State
Counters

.DL.SCell.Rela downlink PRBs
xedBackhaulC occupied by
AUsed.Avg inter-eNodeB
CA UEs that
treat the local
cell as their
SCell
Description
The counter measures the number of downlink PRBs occupied by CA UEs that treat the local
cell as their SCell in the relaxed-backhaul-based inter-eNodeB CA state.
Measurement Points
The average number of PDSCH PRBs per millisecond occupied by CA UEs that treat the
local cell as their PCell or SCell in the relaxed-backhaul-based inter-eNodeB CA state is
measured within a measurement period.
For LTE TDD, these counters measure the actual number of PRBs used for UE scheduling in
a cell. These counters are incremented by the number of UEs if these UEs use the same PRB.
Formula
None

BTS3203E
Unit
None
Related Features
L.ChMeas.PRB.DL.SCell.R Multi-mode: None

elaxedBackhaulCAUsed.Av GSM: None
g
UMTS: None
LTE: LAOFD-080201 Inter-eNodeB CA based on
Relaxed backhaul
1.20.23 Number of PRBs of the Downlink Edge Band in Adaptive

ICIC
Counters

.DL.AICIC.CE PRBs of the
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

BTS3203E
Related Features
None
1.20.24 Average Number of PRBs Used for Inter-eNodeB DL

CoMP Scheduling in a Cell
Counters

.InterEnbDLCo number of
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
None

BTS3203E
1.20.25 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 BTS3203E LTE L

.UL.ULShared. uplink PRBs on
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
None

BTS3203E
1.20.26 Number of Times an eNodeB Successfully Allocates the

PDCCHs with a Specified Aggregation Level for Uplink
Scheduling
Counters

CH.UL.AggLvl times an
1Num eNodeB
allocates the
PDCCHs with
aggregation
level 1 for
uplink
scheduling

2Num eNodeB
allocates the
PDCCHs with
aggregation
level 2 for
uplink
scheduling

4Num eNodeB
allocates the
PDCCHs with
aggregation
level 4 for
uplink
scheduling

8Num eNodeB
allocates the
PDCCHs with
aggregation
level 8 for
uplink
scheduling

BTS3203E
Description
The counters measure the numbers of times an eNodeB allocates the PDCCHs with
aggregation levels 1, 2, 4, and 8 for uplink scheduling.
Measurement Points
The corresponding counter is incremented by 1 each time the eNodeB allocates a PDCCH
with aggregation level 1, 2, 4, or 8 for uplink scheduling in a cell.
counters have a deviation to the actual number of times.
Formula
None
Unit
None
Related Features
L.ChMeas.PDCCH.UL.Agg Multi-mode: None

Lvl1Num GSM: None
UMTS: None
Management

Lvl2Num GSM: None
UMTS: None
Management

Lvl4Num GSM: None
UMTS: None
Management

Lvl8Num GSM: None
UMTS: None
Management

BTS3203E
1.20.27 Number of Times of Successful ePDCCH Resource

Allocations with a Specific Aggregation Level
Counters
1526739817 L.ChMeas.Dl.e Number of BTS3203E LTE L

PDCCH.AggLv times downlink
l1Num ePDCCH
resource
allocations with
aggregation
level 1

l2Num ePDCCH
resource
allocations with
aggregation
level 2

l4Num ePDCCH
resource
allocations with
aggregation
level 4

l8Num ePDCCH
resource
allocations with
aggregation
level 8

l16Num ePDCCH
resource
allocations with
aggregation
level 16

BTS3203E


l32Num ePDCCH
resource
allocations with
aggregation
level 32
1526739823 L.ChMeas.Ul.e Number of BTS3203E LTE L

PDCCH.AggLv times uplink
l1Num ePDCCH
resource
allocations with
aggregation
level 1

l2Num ePDCCH
resource
allocations with
aggregation
level 2

l4Num ePDCCH
resource
allocations with
aggregation
level 4

l8Num ePDCCH
resource
allocations with
aggregation
level 8

l16Num ePDCCH
resource
allocations with
aggregation
level 16

BTS3203E


l32Num ePDCCH
resource
allocations with
aggregation
level 32
Description
The corresponding counter is incremented by 1 each time the ePDCCH resources with
aggregation level 1, 2, 4, 8, 16, or 32 are successfully allocated.
The internal timer of the eNodeB has a deviation of one period, and therefore the values of
these counters have a deviation to the actual values.
Measurement Points
The corresponding counter is incremented by 1 each time the ePDCCH resources with
aggregation level 1, 2, 4, 8, 16, or 32 are successfully allocated.
Formula
None
Unit
None
Related Features
L.ChMeas.Dl.ePDCCH.Agg Multi-mode: None

Lvl1Num GSM: None
UMTS: None
LTE: LAOFD-110203 ePDCCH

Lvl2Num GSM: None
UMTS: None

BTS3203E

Lvl4Num GSM: None
UMTS: None

Lvl8Num GSM: None
UMTS: None

Lvl16Num GSM: None
UMTS: None

Lvl32Num GSM: None
UMTS: None
L.ChMeas.Ul.ePDCCH.Agg Multi-mode: None

Lvl1Num GSM: None
UMTS: None

Lvl2Num GSM: None
UMTS: None

Lvl4Num GSM: None
UMTS: None

Lvl8Num GSM: None
UMTS: None

Lvl16Num GSM: None
UMTS: None

BTS3203E

Lvl32Num GSM: None
UMTS: None
1.20.28 Number of Times DTX Is Detected for Downlink

ePDCCH Resource Allocations with a Specific Aggregation Level
Counters
1526739829 L.ChMeas.ePD Number of BTS3203E LTE L

CCH.DL.DTX times DTX is
Num.AggLvl1 detected for
downlink
ePDCCH
resource
allocations with
aggregation
level 1 in a cell

downlink
ePDCCH
resource
allocations with
aggregation
level 2 in a cell

downlink
ePDCCH
resource
allocations with
aggregation
level 4 in a cell

BTS3203E


downlink
ePDCCH
resource
allocations with
aggregation
level 8 in a cell

downlink
ePDCCH
resource
allocations with
aggregation
level 16 in a
cell

downlink
ePDCCH
resource
allocations with
aggregation
level 32 in a
cell
Description
For downlink ePDCCH resource allocations with aggregation level 1, 2, 4, 8, 16, or 32, the
corresponding counter is incremented by 1 each time the eNodeB detects a DTX.
Measurement Points
For downlink ePDCCH resource allocations with aggregation level 1, 2, 4, 8, 16, or 32, the
corresponding counter is incremented by 1 each time the eNodeB detects a DTX.
Formula
None
Unit
None

BTS3203E
Related Features
L.ChMeas.ePDCCH.DL.DT Multi-mode: None

UMTS: None

UMTS: None

UMTS: None

UMTS: None

UMTS: None

UMTS: None

BTS3203E
1.20.29 Number of PDCCH eCCEs Used in the Cell

Counters
1526740435 L.ChMeas.eCC Number of BTS3203E LTE L

E.DLUsed.DR ePDCCH
B eCCEs used by
initially
transmitted
downlink data

E.DLUsed.MC ePDCCH
E eCCEs used by
initially
transmitted
downlink
MCEs

E.DLUsed.SRB ePDCCH
eCCEs used by
initially
transmitted
downlink
signaling
messages
Description
The corresponding counter measures the number of ePDCCH eCCEs used by initially
transmitted downlink data, downlink MCEs, or downlink signaling messages within a
measurement period.
Measurement Points
The corresponding counter measures the number of ePDCCH eCCEs used by initially
transmitted downlink data, downlink MCEs, or downlink signaling messages within a
measurement period.
Formula
None

BTS3203E
Unit
None
Related Features
L.ChMeas.eCCE.DLUsed.D Multi-mode: None

RB GSM: None
UMTS: None
L.ChMeas.eCCE.DLUsed. Multi-mode: None

MCE GSM: None
UMTS: None
L.ChMeas.eCCE.DLUsed.S Multi-mode: None

RB GSM: None
UMTS: None
1.20.30 Average Number of PRBs Occupied by CEUs in a Cell
Counters

.PUSCH.Avg.B number of
orderUE PUSCH PRBs
occupied by
CEUs in a cell

.PDSCH.Avg.B number of
orderUE PDSCH PRBs
occupied by
CEUs in a cell
Description
The counters measure the average number of PUSCH or PDSCH PRBs occupied by cell edge
users (CEUs) in a cell.

BTS3203E
Measurement Points
In a measurement period, the average number of PUSCH or PDSCH PRBs per millisecond
used by CEUs is measured and taken as the corresponding counter value.
Formula
None
Unit
None
Related Features

g.BorderUE GSM: None
UMTS: None
L.ChMeas.PRB.PDSCH.Av Multi-mode: None

g.BorderUE GSM: None
UMTS: None
1.20.31 Average Number of PRBs Used by the PUSCH for Joint

Reception CEUs in a Cell
Counters

.PUSCH.Avg.B number of
orderUE.JointR PRBs used by
eception the PUSCH for
joint reception
CEUs in a cell
Description
The counters measure the average number of PRBs used by the PUSCH for joint reception
CEUs in a cell.

BTS3203E
Measurement Points
The number of PRBs used by the PUSCH for joint reception CEUs in a cell is sampled per
millisecond. The average of all sampling results in a measurement period is calculated and
used as the value of the counter. The eNodeB determines whether a UE is a joint reception
CEU based on the uplink equivalent RSRP difference between the serving cell of the UE and
the neighboring cell with strongest signals. The threshold of the uplink equivalent RSRP
difference is specified by the EdgeUserSRSOffse parameter in the CellCounterParaGroup
MO.
Formula
None
Unit
None
Related Features

g.BorderUE.JointReception GSM: None
UMTS: None
1.20.32 Average Number of PRBs Used by the PDSCH for Joint

Transmission CEUs in a Cell
Counters

.PDSCH.Avg.B number of
orderUE.JointT PRBs used by
ransmit the PDSCH for
joint
transmission
CEUs in a cell
Description
The counters measure the average number of PRBs used by the PDSCH for joint transmission
CEUs in a cell.

BTS3203E
Measurement Points
The number of PRBs used by the PDSCH for joint transmission CEUs in a cell is sampled per
millisecond. The average of all sampling results in a measurement period is calculated and
used as the value of the counter. The eNodeB determines whether a UE is a joint transmission
CEU based on the downlink equivalent RSRP difference between the serving cell of the UE
and the neighboring cell with strongest signals. The threshold of the downlink equivalent
RSRP difference is specified by the EdgeUserSRSOffse parameter in the
CellCounterParaGroup MO.
Formula
None
Unit
None
Related Features
L.ChMeas.PRB.PDSCH.Av Multi-mode: None

g.BorderUE.JointTransmit GSM: None
UMTS: None
1.20.33 Number of Available PDCCH CCEs in a Cell
Counters
1526745765 L.ChMeas.CCE Maximum BTS3203E LTE L

.Avail.Max number of
available
PDCCH CCEs
in a cell
Description
The counters measure the total number of available PDCCH CCEs in a cell in a measurement
period when the number of OFDM symbols is adjusted to the maximum value. The
L.ChMeas.CCE.UL.Avail.Max counter applies only to LTE TDD.

BTS3203E
Measurement Points
The maximum number of available PDCCH CCEs in a cell is measured and taken as the
counter value within a measurement period.
Formula
None
Unit
None
Related Features
None
1.20.34 Number of Available PDCCH CCEs in a Cell
Counters
1526745766 L.ChMeas.CCE Maximum BTS3203E LTE L

.UL.Avail.Max number of
available uplink
PDCCH CCEs
in a cell
Description
The counters measure the total number of available PDCCH CCEs in a cell in a measurement
period when the number of OFDM symbols is adjusted to the maximum value. The
L.ChMeas.CCE.UL.Avail.Max counter applies only to LTE TDD.
Measurement Points
The maximum number of available PDCCH CCEs in a cell is measured and taken as the
counter value within a measurement period.
Formula
None
Unit
None

BTS3203E
Related Features
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
1526727352 L.Traffic.BCH.TB. Total number of bits BTS3203E LTE:

bits of TBs transmitted V100R006C00
on the BCH
1526727353 L.Traffic.PCH.TB. Total number of bits BTS3203E LTE:

bits of TBs transmitted V100R006C00
on the PCH

QPSK.TB initially transmitted V100R006C00
on the downlink
SCH in QPSK
modulation mode

16QAM.TB initially transmitted V100R006C00
on the downlink
SCH in 16QAM
modulation mode

on the downlink
SCH in 64QAM
modulation mode
1526727357 L.Traffic.DL.SCH. Number of bits of BTS3203E LTE:

QPSK.TB.bits TBs initially V100R006C00
transmitted on the
downlink SCH in
QPSK modulation
mode

BTS3203E


16QAM.TB.bits TBs initially V100R006C00
transmitted on the
downlink SCH in
16QAM modulation
mode

transmitted on the
downlink SCH in
64QAM modulation
mode

QPSK.TB.Retrans retransmitted on the V100R006C00
downlink SCH in
QPSK modulation
mode

16QAM.TB.Retran retransmitted on the V100R006C00
s downlink SCH in
16QAM modulation
mode

s downlink SCH in
64QAM modulation
mode

QPSK.TB.Retrans. TBs retransmitted V100R006C00
bits on the downlink
SCH in QPSK
modulation mode

16QAM.TB.Retran TBs retransmitted V100R006C00
s.bits on the downlink
SCH in 16QAM
modulation mode

s.bits on the downlink
SCH in 64QAM
modulation mode

BTS3203E

1526727366 L.Traffic.UL.SCH. Number of TBs BTS3203E LTE:

QPSK.TB initially transmitted V100R006C00
on the uplink SCH
in QPSK modulation
mode

on the uplink SCH
in 16QAM
modulation mode

on the uplink SCH
in 64QAM
modulation mode
1526727369 L.Traffic.UL.SCH. Number of bits of BTS3203E LTE:

QPSK.TB.bits TBs initially V100R006C00
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

QPSK.TB.Retrans retransmitted on the V100R006C00
uplink SCH in
QPSK modulation
mode

s uplink SCH in
16QAM modulation
mode

BTS3203E


s uplink SCH in
64QAM modulation
mode

QPSK.TB.Retrans. TBs retransmitted V100R006C00
bits on the uplink SCH
in QPSK modulation
mode

s.bits on the uplink SCH
in 16QAM
modulation mode

s.bits on the uplink SCH
in 64QAM
modulation mode
1526728180 L.Traffic.DL.SCH. Number of downlink BTS3203E LTE:

QPSK.ErrTB.Ibler error TBs after V100R006C00
initial transmission
in QPSK modulation
mode

QPSK.ErrTB.Rble error TBs after the V100R006C00
r maximum number
of retransmissions in
QPSK modulation
mode is reached

16QAM.ErrTB.Ibl error TBs after V100R006C00
er initial transmission
in 16QAM
modulation mode

16QAM.ErrTB.Rbl error TBs after the V100R006C00
er maximum number
16QAM modulation
mode is reached

BTS3203E


in 64QAM
modulation mode

er maximum number
64QAM modulation
mode is reached
1526728186 L.Traffic.UL.SCH. Number of uplink BTS3203E LTE:

QPSK.ErrTB.Ibler error TBs after V100R006C00
in QPSK modulation
mode

QPSK.ErrTB.Rble error TBs after the V100R006C00
r maximum number
QPSK modulation
mode is reached

in 16QAM
modulation mode

er maximum number
16QAM modulation
mode is reached

in 64QAM
modulation mode

er maximum number
64QAM modulation
mode is reached

BTS3203E

1526728598 L.Traffic.UL.SCH. Maximum uplink BTS3203E LTE:

bits.Max traffic volume for V100R006C00
MAC TBs in a cell
1526728663 L.Traffic.DL.SCH. Maximum downlink BTS3203E LTE:

bits.Max traffic volume for V100R006C00
MAC TBs in a cell

Shared.TB.bits TBs initially V100R007C00
transmitted on the
downlink SCH in
the shared spectrum

Shared.TB initially transmitted V100R007C00
on the downlink
SCH in the shared
spectrum

Shared.ErrTB.Ible TBs failed to be V100R007C00
r.bits transmitted during
on the downlink
SCH in the shared
spectrum

Shared.ErrTB.Ible failed to be V100R007C00
r transmitted during
on the downlink
SCH in the shared
spectrum
1526729872 L.Thrp.Time.DL.S Duration of BTS3203E LTE:

hared downlink scheduling V100R007C00
in the shared
spectrum
1526729873 L.Thrp.Time.DL.D Duration of BTS3203E LTE:

edicated downlink scheduling V100R007C00
in the dedicated
spectrum
1526729874 L.ChMeas.PRB.Sh Average number of BTS3203E LTE:

ared.DL.Used.Avg used downlink PRBs V100R007C00
in the shared
spectrum

BTS3203E

1526730124 L.Traffic.PktInterv Number of times the BTS3203E LTE:

al.Num.Index0 packet transmission V100R007C00
interval for a UE in
a cell ranges from 5s
to 10s (including 5s
and excluding 10s)

a cell ranges from
10s to 20s (including
10s and excluding
20s)

a cell ranges from
20s and excluding
30s) in a cell

a cell ranges from
30s and excluding
40s)

a cell ranges from
40s and excluding
50s)

a cell ranges from
50s and excluding
60s)

BTS3203E


al.Num.index6 packet transmission V100R007C00
a cell ranges from
60s to 120s
(including 60s and
excluding 120s)

a cell ranges from
120s to 200s
(including 120s and
excluding 200s)

a cell is greater than
or equal to 200s

PoorChannelQuali- error TBs after the V100R011C10
ty.ErrTB.Rbler maximum number
of retransmissions is
reached for UEs
with poor channel
quality

PoorChannelQuali- error TBs after the V100R011C10
ty.ErrTB.Rbler maximum number
reached for UEs
with poor channel
quality

PoorChannelQuali- initially transmitted V100R011C10
ty.TB on the uplink SCH
for UEs with poor
channel quality

PoorChannelQuali- initially transmitted V100R011C10
ty.TB on the downlink
SCH for UEs with
poor channel quality

BTS3203E

1526730872 L.Traffic.Sch.UL.N Number of times BTS3203E LTE:

um that UEs are V100R011C10
scheduled in a cell
in the uplink
1526730873 L.Traffic.Sch.DL.N Number of times BTS3203E LTE:

um that UEs are V100R011C10
scheduled in a cell
in the downlink
1526735156 L.Traffic.DL.SCH. Number of handover BTS3203E LTE:

HOCmd.TB command TBs V100R007C00
on the downlink
SCH

HOCmd.ErrTB.Ibl error TBs for V100R007C00
er handover commands
after initial
transmission

HOCmd.ErrTB.Rb error TBs for V100R007C00
ler handover commands
after the maximum
number of
retransmissions is
reached

RRCRel.ErrTB.Ibl failed to be V100R007C00
er transmitted for RRC
CONN REL
messages during
on the downlink
SCH

RRCRel.ErrTB.Rb failed to be V100R007C00
ler transmitted for RRC
CONN REL
messages after the
maximum number
reached on the
downlink SCH

BTS3203E


RRCRel.TB initially transmitted V100R007C00
for RRC CONN
REL messages on
the downlink SCH

QPSK.TB.NACK TBs with a NACK- V100R011C10
HARQ feedback for
the initial
transmission in
QPSK modulation
mode

16QAM.TB.NACK TBs with a NACK- V100R011C10
HARQ feedback for
the initial
transmission in
16QAM modulation
mode

HARQ feedback for
the initial
transmission in
64QAM modulation
mode

QPSK.TB.NACK TBs with a NACK- V100R011C10
HARQ feedback for
the initial
transmission in
QPSK modulation
mode

HARQ feedback for
the initial
transmission in
16QAM modulation
mode

BTS3203E


HARQ feedback for
the initial
transmission in
64QAM modulation
mode
1526737724 L.Traffic.UL.SCH. Number of QCI-1 BTS3203E LTE:

QPSK.TB.QCI.1 Service TBs initially V100R011C10
transmitted on the
uplink SCH in
QPSK modulation
mode

16QAM.TB.QCI.1 Service TBs initially V100R011C10
transmitted on the
uplink SCH in
16QAM modulation
mode

transmitted on the
uplink SCH in
64QAM modulation
mode

QPSK.TB.Retrans. Service TBs V100R011C10
QCI.1 retransmitted on the
uplink SCH in
QPSK modulation
mode

16QAM.TB.Retran Service TBs V100R011C10
s.QCI.1 retransmitted on the
uplink SCH in
16QAM modulation
mode

uplink SCH in
64QAMmodulation
mode

BTS3203E


QPSK.ErrTB.Ibler. Service TBs with V100R011C10
QCI.1 initial transmission
failures on the
uplink SCH in
QPSK modulation
mode

16QAM.ErrTB.Ibl Service TBs with V100R011C10
er.QCI.1 initial transmission
failures on the
uplink SCH in
16QAM modulation
mode

failures on the
uplink SCH in
64QAM modulation
mode
1526737733 L.Traffic.DL.SCH. Number of QCI-1 BTS3203E LTE:

QPSK.TB.QCI.1 Service TBs initially V100R011C10
transmitted on the
downlink SCH in
QPSK modulation
mode

transmitted on the
downlink SCH in
16QAM modulation
mode

transmitted on the
downlink SCH in
64QAM modulation
mode

QPSK.TB.Retrans. Service TBs V100R011C10
downlink SCH in
QPSK modulation
mode

BTS3203E


downlink SCH in
16QAM modulation
mode

downlink SCH in
64QAM modulation
mode

QPSK.ErrTB.Ibler. Service TBs with V100R011C10
QCI.1 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
1526737858 L.Traffic.DL.SCH. Number of service BTS3203E LTE:

QPSK.DRB.TB data TBs initially V100R011C10
transmitted on the
downlink SCH in
QPSK modulation
mode

16QAM.DRB.TB data TBs initially V100R011C10
transmitted on the
downlink SCH in
16QAM modulation
mode

BTS3203E


64QAM.DRB.TB data TBs initially V100R011C10
transmitted on the
downlink SCH in
64QAM modulation
mode

QPSK.DRB.TB.Ret data TBs V100R011C10
rans retransmitted on the
downlink SCH in
QPSK modulation
mode

16QAM.DRB.TB.R data TBs V100R011C10
etrans retransmitted on the
downlink SCH in
16QAM modulation
mode

64QAM.DRB.TB.R data TBs V100R011C10
etrans retransmitted on the
downlink SCH in
64QAM modulation
mode

QPSK.DRB.ErrTB error service data V100R011C10
.Ibler TBs after initial
transmission in
QPSK modulation
mode

16QAM.DRB.ErrT error service data V100R011C10
B.Ibler TBs after initial
transmission in
16QAM modulation
mode

transmission in
64QAM modulation
mode

BTS3203E


QPSK.DRB.ErrTB error service data V100R011C10
.Rbler TBs after the
maximum number
QPSK modulation
mode is reached

B.Rbler TBs after the
maximum number
16QAM modulation
mode is reached

maximum number
64QAM modulation
mode is reached

on the downlink
SCH in 256QAM
modulation scheme

transmitted on the
downlink SCH in
256QAM
modulation scheme

256QAM.TB.Retra retransmitted on the V100R011C10
ns downlink SCH in
256QAM
modulation scheme

256QAM.TB.Retra TBs retransmitted V100R011C10
ns.bits on the downlink
SCH in 256QAM
modulation scheme

BTS3203E


256QAM.ErrTB.Ib erroneous TBs after V100R011C10
ler initial transmission
in 256QAM
modulation scheme

256QAM.ErrTB.R erroneous TBs after V100R011C10
bler the maximum
number of
retransmissions in
256QAM
modulation scheme
is reached

256QAM.TB.NAC TBs with NACK- V100R011C10
K HARQ feedback for
the initial
transmission in the
256QAM
modulation scheme

QPSK.ErrTB.bits. downlink TBs that V100R011C10
Rbler fail to be
retransmitted after
the maximum
number of
retransmissions is
reached in the QPSK
modulation scheme

16QAM.ErrTB.bits downlink TBs that V100R011C10
.Rbler fail to be
retransmitted after
the maximum
number of
retransmissions is
reached in the
16QAM modulation
scheme

BTS3203E


64QAM.ErrTB.bits downlink TBs that V100R011C10
.Rbler fails to be
retransmitted after
the maximum
number of
retransmissions is
reached in the
64QAM modulation
scheme

Shared.TB.bits TBs initially V100R011C10
transmitted on the
uplink SCH in the
shared spectrum in
an LTE cell

Shared.TB initially transmitted V100R011C10
on the uplink SCH
in the shared
spectrum in an LTE
cell

Shared.ErrTB.Ible TBs failed to be V100R011C10
r.bits transmitted during
on the uplink SCH
in the shared
spectrum in an LTE
cell

Shared.ErrTB.Ible failed to be V100R011C10
r transmitted during
on the uplink SCH
in the shared
spectrum in an LTE
cell
1526741740 L.Thrp.Time.UL.S Duration of uplink BTS3203E LTE:

hared scheduling in the V100R011C10
shared spectrum in
an LTE cell

BTS3203E

1526741741 L.Thrp.Time.UL.D Duration of uplink BTS3203E LTE:

edicated scheduling in the V100R011C10
dedicated spectrum
in an LTE cell
1526741742 L.ChMeas.PRB.Sh Average number of BTS3203E LTE:

ared.UL.Used.Avg used uplink PRBs in V100R011C10
the shared spectrum
in an LTE cell

TB.BorderUE Initially Transmitted V100R011C10
for Cell Edge UEs
on the Uplink SCH

ErrTB.Ibler.Borde erroneous TBs after V100R011C10
rUE initial transmission
for cell edge Ues

ErrTB.Rbler.Borde erroneous TBs after V100R011C10
rUE the maximum
number of
retransmissions for
cell edge UEs is
reached
1526741768 L.Traffic.DL.SCH. L.Traffic.DL.SCH.T BTS3203E LTE:

TB.BorderUE B.BorderUE V100R011C10
1526741769 L.Traffic.DL.SCH. L.Traffic.DL.SCH.E BTS3203E LTE:

ErrTB.Ibler.Borde rrTB.Ibler.BorderUE V100R011C10
rUE
1526741770 L.Traffic.DL.SCH. L.Traffic.DL.SCH.E BTS3203E LTE:

ErrTB.Rbler.Borde rrTB.Rbler.BorderU V100R011C10
rUE E

QPSK.TB.QCI.2 service TBs initially V100R011C10
transmitted on the
uplink SCH using
QPSK

16QAM.TB.QCI.2 service TBs initially V100R011C10
transmitted on the
uplink SCH in
16QAM modulation
mode

BTS3203E


transmitted on the
uplink SCH in
64QAM modulation
mode

QPSK.TB.Retrans. service TBs V100R011C10
uplink SCH in
QPSK modulation
mode

16QAM.TB.Retran service TBs V100R011C10
uplink SCH in
16QAM modulation
mode

uplink SCH in
64QAM modulation
mode

QPSK.TB.QCI.2 service TBs initially V100R011C10
transmitted on the
downlink SCH in
QPSK modulation
mode

transmitted on the
downlink SCH in
16QAM modulation
mode

transmitted on the
downlink SCH in
64QAM modulation
mode

BTS3203E


QPSK.TB.Retrans. service TBs V100R011C10
downlink SCH in
QPSK modulation
mode

downlink SCH in
16QAM modulation
mode

downlink SCH in
64QAM modulation
mode

a cell ranges within
index 9
None
1.21.1 Total Number of Bits of TBs Transmitted on the BCH

Counters
1526727352 L.Traffic.BCH. Total number of BTS3203E LTE L

TB.bits bits of TBs
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

BTS3203E
(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
Modulation: DL/UL QPSK,
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 BTS3203E LTE L

TB.bits bits of TBs
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.

BTS3203E
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
64QAM
1.21.3 Number of TBs Initially Transmitted on the Downlink

SCH
Counters

CH.QPSK.TB initially
transmitted on
the downlink
SCH in QPSK
modulation
mode

BTS3203E


CH.16QAM.TB initially
transmitted on
the downlink
SCH in
16QAM
modulation
mode

transmitted on
the downlink
SCH in
64QAM
modulation
mode

CH. initially
256QAM.TB transmitted on
the downlink
SCH in
256QAM
modulation
scheme
Description
The eNodeB determines an MCS index for initial transmission of the UE based on the quality
of the downlink channel. Each MCS index corresponds to a modulation mode, such as QPSK,
16QAM, and 64QAM. The counters measure the number of TBs initially transmitted on the
downlink SCH in QPSK, 16QAM, and 64QAM modulation modes in a cell.
Measurement Points
The corresponding counter is incremented by 1 based on modulation mode each time the
eNodeB initially transmits a TB on the downlink SCH.
measurement result of the corresponding counter has a deviation.
Formula
None
Unit
None

BTS3203E
Related Features
L.Traffic.DL.SCH.QPSK.T Multi-mode: None

B GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM
CQI Adjustment
L.Traffic.DL.SCH. Multi-mode: None

16QAM.TB GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM
CQI Adjustment

64QAM.TB GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM
CQI Adjustment

256QAM.TB GSM: None
UMTS: None
LEOFD-110301 Modulation: DL/UL QPSK,
DL/UL 16QAM, DL
64QAM
DL 256QAM

BTS3203E
1.21.4 Number of Bits of TBs Initially Transmitted on the

Downlink SCH
Counters

CH.QPSK.TB.b of TBs initially
its transmitted on
the downlink
SCH in QPSK
modulation
mode

CH. of TBs initially
16QAM.TB.bit transmitted on
s the downlink
SCH in
16QAM
modulation
mode

s the downlink
SCH in
64QAM
modulation
mode

256QAM.TB.bi transmitted on
ts the downlink
SCH in
256QAM
modulation
scheme
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.

BTS3203E
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
64QAM

16QAM.TB.bits GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E

UMTS: None
DL/UL 16QAM, DL
64QAM
DL 256QAM
1.21.5 Number of TBs Retransmitted on the Downlink SCH

Counters

CH.QPSK.TB. retransmitted on
Retrans the downlink
SCH in QPSK
modulation
mode

CH. retransmitted on
16QAM.TB.Ret the downlink
rans SCH in
16QAM
modulation
mode

64QAM.TB.Ret the downlink
rans SCH in
64QAM
modulation
mode

256QAM.TB.R the downlink
etrans SCH in
256QAM
modulation
scheme

BTS3203E
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
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
64QAM

16QAM.TB.Retrans GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E

UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
64QAM
DL 256QAM
1.21.6 Number of Bits of TBs Retransmitted on the Downlink

SCH
Counters

CH.QPSK.TB. of TBs
Retrans.bits retransmitted on
the downlink
SCH in QPSK
modulation
mode

CH. of TBs
16QAM.TB.Ret retransmitted on
rans.bits the downlink
SCH in
16QAM
modulation
mode

BTS3203E


CH. of TBs
rans.bits the downlink
SCH in
64QAM
modulation
mode

CH. of TBs
256QAM.TB.R retransmitted on
etrans.bits the downlink
SCH in
256QAM
modulation
scheme
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
Measurement Points
modulation mode each time the eNodeB retransmits a TB on the downlink SCH.
Formula
None
Unit
bit

BTS3203E
Related Features

B.Retrans.bits GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

16QAM.TB.Retrans.bits GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
64QAM
DL 256QAM

BTS3203E
1.21.7 Number of TBs Initially Transmitted on the Uplink SCH
Counters
1526727366 L.Traffic.UL.S Number of TBs BTS3203E LTE L

CH.QPSK.TB initially
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

BTS3203E
Unit
None
Related Features
L.Traffic.UL.SCH.QPSK.T Multi-mode: None

B GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM
L.Traffic.UL.SCH. Multi-mode: None

16QAM.TB GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

64QAM.TB GSM: None
UMTS: None
UL 64QAM

BTS3203E
1.21.8 Number of bits of TBs Initially Transmitted on the Uplink

SCH
Counters
1526727369 L.Traffic.UL.S Number of bits BTS3203E LTE L

CH.QPSK.TB.b of TBs initially
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

BTS3203E
Unit
bit
Related Features

B.bits GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
UL 64QAM
1.21.9 Number of TBs Retransmitted on the Uplink SCH
Counters

CH.QPSK.TB. retransmitted on
Retrans the uplink SCH
in QPSK
modulation
mode

BTS3203E


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

BTS3203E
Related Features

B.Retrans GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
UL 64QAM
1.21.10 Number of bits of TBs Retransmitted on the Uplink SCH

Counters

CH.QPSK.TB. of TBs
Retrans.bits retransmitted on
the uplink SCH
in QPSK
modulation
mode

BTS3203E


CH. of TBs
rans.bits the uplink SCH
in 16QAM
modulation
mode

CH. of TBs
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

BTS3203E
Related Features

B.Retrans.bits GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
UL 64QAM
1.21.11 Number of Downlink Error TBs After Initial Transmission

Counters
1526728180 L.Traffic.DL.S Number of BTS3203E LTE L

CH.QPSK.ErrT downlink error
transmission in
QPSK
modulation
mode

BTS3203E


CH. downlink error
16QAM.ErrTB. TBs after initial
Ibler transmission in
16QAM
modulation
mode

CH. downlink error
64QAM
modulation
mode

CH.QPSK.TB. downlink TBs
NACK with a NACK-
HARQ
feedback for the
initial
transmission in
QPSK
modulation
mode

CH. downlink TBs
16QAM.TB.N with a NACK-
ACK HARQ
feedback for the
initial
transmission in
16QAM
modulation
mode

CH. downlink TBs
64QAM.TB.N with a NACK-
ACK HARQ
feedback for the
initial
transmission in
64QAM
modulation
mode

BTS3203E


CH. downlink
256QAM.ErrT erroneous TBs
B.Ibler after initial
transmission in
256QAM
modulation
scheme

CH. downlink TBs
256QAM.TB.N with NACK-
ACK HARQ
feedback for the
initial
transmission in
the 256QAM
modulation
scheme
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

BTS3203E
Related Features
L.Traffic.DL.SCH.QPSK.Er Multi-mode: None

rTB.Ibler GSM: None
UMTS: None
CQI Adjustment

16QAM.ErrTB.Ibler GSM: None
UMTS: None
CQI Adjustment

UMTS: None
CQI Adjustment

B.NACK GSM: None
UMTS: None
Management

16QAM.TB.NACK GSM: None
UMTS: None
Management

UMTS: None
Management

BTS3203E

UMTS: None
LEOFD-110301 Management
DL 256QAM

UMTS: None
DL 256QAM
1.21.12 Number of Downlink Error TBs After the Maximum

Number of Retransmissions Is Reached
Counters

CH.QPSK.ErrT downlink error
maximum
number of
retransmissions
in QPSK
modulation
mode is reached

CH. downlink error
16QAM.ErrTB. TBs after the
Rbler maximum
number of
retransmissions
in 16QAM
modulation
mode is reached

BTS3203E


CH. downlink error
Rbler maximum
number of
retransmissions
in 64QAM
modulation
mode is reached

CH. downlink
256QAM.ErrT erroneous TBs
B.Rbler after the
maximum
number of
retransmissions
in 256QAM
modulation
scheme 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

BTS3203E
Related Features

rTB.Rbler GSM: None
UMTS: None
Management

16QAM.ErrTB.Rbler GSM: None
UMTS: None
Management

UMTS: None
Management

UMTS: None
DL 256QAM
1.21.13 Number of Uplink Error TBs After Initial Transmission

Counters
1526728186 L.Traffic.UL.S Number of BTS3203E LTE L

CH.QPSK.ErrT uplink error
transmission in
QPSK
modulation
mode

BTS3203E


CH. uplink error
16QAM
modulation
mode

CH. uplink error
64QAM
modulation
mode

CH.QPSK.TB. uplink TBs with
NACK a NACK-
HARQ
feedback for the
initial
transmission in
QPSK
modulation
mode

CH. uplink TBs with
16QAM.TB.N a NACK-
ACK HARQ
feedback for the
initial
transmission in
16QAM
modulation
mode

CH. uplink TBs with
64QAM.TB.N a NACK-
ACK HARQ
feedback for the
initial
transmission in
64QAM
modulation
mode

BTS3203E
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.
Formula
None
Unit
None
Related Features
L.Traffic.UL.SCH.QPSK.Er Multi-mode: None

rTB.Ibler GSM: None
UMTS: None
Management

UMTS: None
Management

UMTS: None
Management

B.NACK GSM: None
UMTS: None
Management

BTS3203E

UMTS: None
Management

UMTS: None
Management
1.21.14 Number of Uplink Error TBs After the Maximum Number

of Retransmissions Is Reached
Counters

CH.QPSK.ErrT uplink error
maximum
number of
retransmissions
in QPSK
modulation
mode is reached

CH. uplink error
Rbler maximum
number of
retransmissions
in 16QAM
modulation
mode is reached

BTS3203E


CH. uplink error
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
Management

UMTS: None
Management

BTS3203E

UMTS: None
Management
1.21.15 Maximum Traffic Volume for MAC TBs in a Cell
Counters
1526728598 L.Traffic.UL.S Maximum BTS3203E LTE L

CH.bits.Max uplink traffic
volume for
MAC TBs in a
cell
1526728663 L.Traffic.DL.S Maximum BTS3203E LTE L

CH.bits.Max downlink traffic
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

BTS3203E
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
bits transmitted on
the downlink
SCH in the
shared spectrum

CH.Shared.TB. of TBs initially
bits transmitted on
the uplink SCH
in the shared
spectrum in an
LTE cell
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.

BTS3203E
Formula
None
Unit
bit
Related Features
L.Traffic.DL.SCH.Shared.T Multi-mode: MRFD-090202 GSM and LTE FDD

B.bits MRFD-111401 Dynamic Spectrum
Sharing(LTE FDD)
GSM: None
GSM and LTE Zero
UMTS: None Bufferzone
LTE: LOFD-111205
CDMA and LTE Zero

Bufferzone (LTE FDD)
L.Traffic.UL.SCH.Shared.T Multi-mode: MRFD-090202 GSM and LTE FDD

B.bits MRFD-111401 Dynamic Spectrum
Sharing(LTE FDD)
GSM: None
GSM and LTE Zero
LTE: LOFD-111205
CDMA and LTE Zero

1.21.17 Number of TBs Initially Transmitted on the Downlink

SCH in the Shared Spectrum
Counters

CH.Shared.TB initially
transmitted on
the downlink
SCH in the
shared spectrum

BTS3203E


CH.Shared.TB initially
transmitted on
the uplink SCH
in the shared
spectrum in an
LTE cell
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 MRFD-111401 Dynamic Spectrum
Sharing(LTE FDD)
GSM: None
GSM and LTE Zero
LTE: LOFD-111205
CDMA and LTE Zero


BTS3203E
L.Traffic.UL.SCH.Shared.T Multi-mode: MRFD-090202 GSM and LTE FDD

B MRFD-111401 Dynamic Spectrum
Sharing(LTE FDD)
GSM: None
GSM and LTE Zero
LTE: LOFD-111205
CDMA and LTE Zero

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
TB.Ibler.bits be transmitted
during initial
transmission on
the downlink
SCH in the
shared spectrum

CH.Shared.Err of TBs failed to
TB.Ibler.bits be transmitted
during initial
transmission on
the uplink SCH
in the shared
spectrum in an
LTE cell
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.

BTS3203E
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 MRFD-111401 Dynamic Spectrum
Sharing(LTE FDD)
GSM: None
GSM and LTE Zero
LTE: LOFD-111205
CDMA and LTE Zero

L.Traffic.UL.SCH.Shared.E Multi-mode: MRFD-090202 GSM and LTE FDD

rrTB.Ibler.bits MRFD-111401 Dynamic Spectrum
Sharing(LTE FDD)
GSM: None
GSM and LTE Zero
LTE: LOFD-111205
CDMA and LTE Zero


BTS3203E
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
TB.Ibler transmitted
during initial
transmission on
the downlink
SCH in the
shared spectrum

CH.Shared.Err failed to be
TB.Ibler transmitted
during initial
transmission on
the uplink SCH
in the shared
spectrum in an
LTE cell
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

BTS3203E
Related Features
L.Traffic.DL.SCH.Shared.E Multi-mode: MRFD-090202 GSM and LTE FDD

rrTB.Ibler MRFD-111401 Dynamic Spectrum
Sharing(LTE FDD)
GSM: None
GSM and LTE Zero
LTE: LOFD-111205
CDMA and LTE Zero

L.Traffic.UL.SCH.Shared.E Multi-mode: MRFD-090202 GSM and LTE FDD

rrTB.Ibler MRFD-111401 Dynamic Spectrum
Sharing(LTE FDD)
GSM: None
GSM and LTE Zero
LTE: LOFD-111205
CDMA and LTE Zero

1.21.20 Duration of Downlink Scheduling in the Shared Spectrum

Counters
1526729872 L.Thrp.Time.D Duration of BTS3203E LTE L

L.Shared downlink
scheduling in
the shared
spectrum
1526741740 L.Thrp.Time.U Duration of BTS3203E LTE L

L.Shared uplink
scheduling in
the shared
spectrum in an
LTE cell
Description
The counter measures the duration of downlink scheduling in the shared spectrum in an LTE
cell when GL dynamic spectrum sharing is enabled.

BTS3203E
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

MRFD-111401 Dynamic Spectrum
Sharing(LTE FDD)
GSM: None
GSM and LTE Zero
LTE: LOFD-111205
CDMA and LTE Zero

L.Thrp.Time.UL.Shared Multi-mode: MRFD-090202 GSM and LTE FDD

Sharing(LTE FDD)
GSM: None
GSM and LTE Zero
LTE: LOFD-111205
CDMA and LTE Zero


BTS3203E
1.21.21 Duration of Downlink Scheduling in the Dedicated

Spectrum
Counters
1526729873 L.Thrp.Time.D Duration of BTS3203E LTE L

L.Dedicated downlink
scheduling in
the dedicated
spectrum
1526741741 L.Thrp.Time.U Duration of BTS3203E LTE L

L.Dedicated uplink
scheduling in
the dedicated
spectrum in an
LTE cell
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.
Formula
None
Unit
ms

BTS3203E
Related Features
L.Thrp.Time.DL.Dedicated Multi-mode: MRFD-090202 GSM and LTE FDD

Sharing(LTE FDD)
GSM: None
GSM and LTE Zero
LTE: LOFD-111205
CDMA and LTE Zero

L.Thrp.Time.UL.Dedicated Multi-mode: MRFD-090202 GSM and LTE FDD

Sharing(LTE FDD)
GSM: None
GSM and LTE Zero
LTE: LOFD-111205
CDMA and LTE Zero

1.21.22 Average Number of Used Downlink PRBs in the Shared

Spectrum
Counters

.Shared.DL.Use number of used
d.Avg downlink PRBs
in the shared
spectrum

.Shared.UL.Use number of used
d.Avg uplink PRBs in
the shared
spectrum in an
LTE cell

BTS3203E
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 MRFD-111401 Dynamic Spectrum
Sharing(LTE FDD)
GSM: None
GSM and LTE Zero
LTE: LOFD-111205
CDMA and LTE Zero

L.ChMeas.PRB.Shared.UL. Multi-mode: MRFD-090202 GSM and LTE FDD

Used.Avg MRFD-111401 Dynamic Spectrum
Sharing(LTE FDD)
GSM: None
GSM and LTE Zero
LTE: LOFD-111205
CDMA and LTE Zero


BTS3203E
1.21.23 Distribution of Packet Transmission Intervals for UEs in a

Cell
Counters
1526730124 L.Traffic.PktInt Number of BTS3203E LTE L

erval.Num.Inde times the packet
x0 transmission
interval for a
UE in a cell
ranges from 5s
to 10s
(including 5s
and excluding
10s)

x1 transmission
interval for a
UE in a cell
ranges from 10s
to 20s
(including 10s
and excluding
20s)

x2 transmission
interval for a
UE in a cell
ranges from 20s
to 30s
(including 20s
and excluding
30s) in a cell

x3 transmission
interval for a
UE in a cell
ranges from 30s
to 40s
(including 30s
and excluding
40s)

BTS3203E


x4 transmission
interval for a
UE in a cell
ranges from 40s
to 50s
(including 40s
and excluding
50s)

x5 transmission
interval for a
UE in a cell
ranges from 50s
to 60s
(including 50s
and excluding
60s)

erval.Num.inde times the packet
x6 transmission
interval for a
UE in a cell
ranges from 60s
to 120s
(including 60s
and excluding
120s)

x7 transmission
interval for a
UE in a cell
ranges from
120s to 200s
(including 120s
and excluding
200s)

x8 transmission
interval for a
UE in a cell is
greater than or
equal to 200s

BTS3203E


x9 transmission
interval for a
UE in a cell
ranges within
index 9
Description
The counters measure the number of times the packet transmission interval for a UE ranges in
different indexes. Interval indexes (0 to 9) are defined as follows:
Index 0: [5s, 10s)
Index 1: [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, +∞)
Index 9: (0s, 5s)
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

BTS3203E
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

BTS3203E
L.Traffic.PktInterval.Num.in Multi-mode: None

dex6 GSM: None
UMTS: None
Dynamic DRX

dex7 GSM: None
UMTS: None
Dynamic DRX

dex8 GSM: None
UMTS: None
Dynamic DRX

ndex9 GSM: None
UMTS: None
Dynamic DRX

BTS3203E
1.21.24 Number of Error TBs After the Maximum Number of

Retransmissions Is Reached for UEs with Poor Channel Quality
Counters

CH.PoorChann uplink error
elQuality.ErrTB TBs after the
.Rbler maximum
number of
retransmissions
is reached for
UEs with poor
channel quality

CH.PoorChann downlink error
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

BTS3203E
Related Features
L.Traffic.UL.SCH.PoorCha Multi-mode: None

nnelQuality.ErrTB.Rbler GSM: None
UMTS: None
Management
L.Traffic.DL.SCH.PoorCha Multi-mode: None

nnelQuality.ErrTB.Rbler GSM: None
UMTS: None
Management
1.21.25 Number Of TBs Initially Transmitted for UEs with Poor

Channel Quality
Counters

CH.PoorChann initially
elQuality.TB transmitted on
the uplink SCH
for UEs with
poor channel
quality

CH.PoorChann initially
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.

BTS3203E
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
L.Traffic.UL.SCH.PoorCha Multi-mode: None

nnelQuality.TB GSM: None
UMTS: None
Management
L.Traffic.DL.SCH.PoorCha Multi-mode: None

nnelQuality.TB GSM: None
UMTS: None
Management
1.21.26 Number of Times that UEs are Scheduled in a Cell in the

Uplink or Downlink
Counters
1526730872 L.Traffic.Sch.U Number of BTS3203E LTE L

L.Num times that UEs
are scheduled in
a cell in the
uplink

BTS3203E

1526730873 L.Traffic.Sch.D Number of BTS3203E LTE L

L.Num times that UEs
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

BTS3203E
1.21.27 Number of Handover Command TBs Initially Transmitted

on the Downlink SCH
Counters

CH.HOCmd.T handover
B command TBs
initially
transmitted on
the downlink
SCH

CH.RRCRel.Er failed to be
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

BTS3203E
Related Features
L.Traffic.DL.SCH.HOCmd. Multi-mode: None

TB GSM: None
UMTS: None
Management
L.Traffic.DL.SCH.RRCRel. Multi-mode: None

ErrTB.Ibler GSM: None
UMTS: None
Management
1.21.28 Number of Downlink Error TBs for Handover Commands

After Initial Transmission
Counters

CH.HOCmd.Er downlink error
rTB.Ibler TBs for
handover
commands after
initial
transmission

CH.RRCRel.Er failed to be
rTB.Rbler transmitted for
RRC CONN
REL messages
after the
maximum
number of
retransmissions
is reached on
the downlink
SCH

BTS3203E
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
Management

ErrTB.Rbler GSM: None
UMTS: None
Management

BTS3203E
1.21.29 Number of Downlink Error TBs for Handover Commands

After the Maximum Number of Retransmissions is Reached
Counters

CH.HOCmd.Er downlink error
rTB.Rbler TBs for
handover
commands after
the maximum
number of
retransmissions
is reached

CH.RRCRel.T initially
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

BTS3203E
Related Features

ErrTB.Rbler GSM: None
UMTS: None
Management

TB GSM: None
UMTS: None
Management
1.21.30 Number of Voice Service TBs Initially Transmitted on the

Uplink SCH
Counters

CH.QPSK.TB. QCI-1 Service
QCI.1 TBs initially
transmitted on
the uplink SCH
in QPSK
modulation
mode

CH. QCI-1 Service
16QAM.TB.QC TBs initially
I.1 transmitted on
the uplink SCH
in 16QAM
modulation
mode

BTS3203E


CH. QCI-1 Service
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

BTS3203E
Related Features

B.QCI.1 GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

16QAM.TB.QCI.1 GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
UL 64QAM
1.21.31 Number of Voice Service TBs Retransmitted on the

Uplink SCH
Counters

Retrans.QCI.1 TBs
retransmitted on
the uplink SCH
in QPSK
modulation
mode

BTS3203E


CH. QCI-1 Service
16QAM.TB.Ret TBs
rans.QCI.1 retransmitted on
the uplink SCH
in 16QAM
modulation
mode

CH. QCI-1 Service
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

BTS3203E
Related Features

B.Retrans.QCI.1 GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

16QAM.TB.Retrans.QCI.1 GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
UL 64QAM
1.21.32 Number of Voice Service TBs with Initial Transmission

Failures on the Uplink SCH
Counters

CH.QPSK.ErrT QCI-1 Service
B.Ibler.QCI.1 TBs with initial
transmission
failures on the
uplink SCH in
QPSK
modulation
mode

BTS3203E


CH. QCI-1 Service
16QAM.ErrTB. TBs with initial
Ibler.QCI.1 transmission
failures on the
uplink SCH in
16QAM
modulation
mode

CH. QCI-1 Service
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

BTS3203E
Unit
None
Related Features

rTB.Ibler.QCI.1 GSM: None
UMTS: None
Management

16QAM.ErrTB.Ibler.QCI.1 GSM: None
UMTS: None
Management

UMTS: None
Management
1.21.33 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

BTS3203E


CH. QCI-1 Service
I.1 transmitted on
the downlink
SCH in
16QAM
modulation
mode

CH. QCI-1 Service
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

BTS3203E
Related Features

B.QCI.1 GSM: None
UMTS: None
Management

UMTS: None
Management

UMTS: None
Management
1.21.34 Number of Voice Service TBs Retransmitted on the

Downlink SCH
Counters

Retrans.QCI.1 TBs
retransmitted on
the downlink
SCH in QPSK
modulation
mode

CH. QCI-1 Service
16QAM.TB.Ret TBs
the downlink
SCH in
16QAM
modulation
mode

BTS3203E


CH. QCI-1 Service
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

UMTS: None
Management

BTS3203E

UMTS: None
Management

UMTS: None
Management
1.21.35 Number of Voice Service TBs with Initial Transmission

Failures on the Downlink SCH
Counters

CH.QPSK.ErrT QCI-1 Service
B.Ibler.QCI.1 TBs with initial
transmission
failures on the
downlink SCH
in QPSK
modulation
mode

CH. QCI-1 Service
failures on the
downlink SCH
in 16QAM
modulation
mode

BTS3203E


CH. QCI-1 Service
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
Management

BTS3203E

UMTS: None
Management

UMTS: None
Management
1.21.36 Number of Service Data TBs Initially Transmitted on the

Downlink SCH
Counters

CH.QPSK.DRB service data
.TB TBs initially
transmitted on
the downlink
SCH in QPSK
modulation
mode

CH. service data
16QAM.DRB.T TBs initially
B transmitted on
the downlink
SCH in
16QAM
modulation
mode

BTS3203E


CH. service data
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
64QAM

BTS3203E

16QAM.DRB.TB GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

64QAM.DRB.TB GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM
1.21.37 Number of Service Data TBs Retransmitted on the

Downlink SCH
Counters

CH.QPSK.DRB service data
.TB.Retrans TBs
retransmitted on
the downlink
SCH in QPSK
modulation
mode

CH. service data
16QAM.DRB.T TBs
B.Retrans retransmitted on
the downlink
SCH in
16QAM
modulation
mode

BTS3203E


CH. service data
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
64QAM

BTS3203E

16QAM.DRB.TB.Retrans GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

64QAM.DRB.TB.Retrans GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM
1.21.38 Number of Downlink Error Service Data TBs After Initial

Transmission
Counters

CH.QPSK.DRB downlink error
.ErrTB.Ibler service data
TBs after initial
transmission in
QPSK
modulation
mode

CH. downlink error
16QAM.DRB.E service data
rrTB.Ibler TBs after initial
transmission in
16QAM
modulation
mode

BTS3203E


CH. downlink error
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
Management

16QAM.DRB.ErrTB.Ibler GSM: None
UMTS: None
Management

BTS3203E

64QAM.DRB.ErrTB.Ibler GSM: None
UMTS: None
Management
1.21.39 Number of Downlink Error Service Data TBs After the

Maximum Number of Retransmissions Is Reached
Counters

CH.QPSK.DRB downlink error
.ErrTB.Rbler service data
TBs after the
maximum
number of
retransmissions
in QPSK
modulation
mode is reached

CH. downlink error
rrTB.Rbler TBs after the
maximum
number of
retransmissions
in 16QAM
modulation
mode is reached

CH. downlink error
rrTB.Rbler TBs after the
maximum
number of
retransmissions
in 64QAM
modulation
mode is reached

BTS3203E
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
Management

16QAM.DRB.ErrTB.Rbler GSM: None
UMTS: None
Management

64QAM.DRB.ErrTB.Rbler GSM: None
UMTS: None
Management

BTS3203E
1.21.40 Number of Bits of Downlink TBs that Fail to Be

Transmitted After the Maximum Number of Retransmissions Is
Reached
Counters

CH.QPSK.ErrT of downlink
B.bits.Rbler TBs that fail to
be retransmitted
after the
maximum
number of
retransmissions
is reached in the
QPSK
modulation
scheme

CH. of downlink
16QAM.ErrTB. TBs that fail to
bits.Rbler be retransmitted
after the
maximum
number of
retransmissions
is reached in the
16QAM
modulation
scheme

CH. of downlink
64QAM.ErrTB. TBs that fails to
bits.Rbler be retransmitted
after the
maximum
number of
retransmissions
is reached in the
64QAM
modulation
scheme

BTS3203E
Description
The counters measure the numbers of bits of downlink TBs that fail to be retransmitted after
the maximum number of retransmissions is reached in different modulation schemes.
Measurement Points
The corresponding counter is incremented based on the modulation schemes by the number of
bits of the TB each time a TB fails to be retransmitted after the maximum number of
retransmissions is reached.
Formula
None
Unit
bit
Related Features

rTB.bits.Rbler GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

16QAM.ErrTB.bits.Rbler GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

64QAM.ErrTB.bits.Rbler GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E
1.21.41 Number of TBs initially transmitted for cell edge UEs on

the uplink SCH
Counters

CH.TB.Border Initially
UE Transmitted for
Cell Edge UEs
on the Uplink
SCH
Description
The counter measures the number of TBs initially transmitted for cell edge UEs on the uplink
SCH in a cell.
Measurement Points
The counter is incremented by 1 each time a TB initially transmitted is received from a cell
edge UE on the uplink SCH in a cell.
Formula
None
Unit
None
Related Features
L.Traffic.UL.SCH.TB.Bord Multi-mode: None

erUE GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E
1.21.42 Number of uplink erroneous TBs after initial transmission

for cell edge Ues
Counters

CH.ErrTB.Ibler. uplink
BorderUE erroneous TBs
after initial
transmission for
cell edge Ues
Description
The counter measures the number of erroneous TBs initially transmitted for cell edge UEs on
the uplink SCH in a cell.
Measurement Points
The counter is incremented by 1 each time the eNodeB receives an uplink erroneous TB after
initial transmission for a cell edge UE on the uplink SCH in a cell.
Formula
None
Unit
None
Related Features
L.Traffic.UL.SCH.ErrTB.Ibl Multi-mode: None

er.BorderUE GSM: None
UMTS: None
Management

BTS3203E
1.21.43 L.Traffic.UL.SCH.ErrTB.Rbler.BorderUE
Counters

CH.ErrTB.Rble uplink
r.BorderUE erroneous TBs
after the
maximum
number of
retransmissions
for cell edge
UEs is reached
Description
The counter measures the number of erroneous TBs after the maximum number of
retransmissions for cell edge UEs on the uplink SCH is reached in a cell.
Measurement Points
The counter is incremented by 1 each time the eNodeB receives an uplink erroneous TB after
the maximum number of retransmissions for a cell edge UE on the uplink SCH is reached in a
cell.
Formula
None
Unit
None
Related Features
L.Traffic.UL.SCH.ErrTB.R Multi-mode: None

bler.BorderUE GSM: None
UMTS: None
Management

BTS3203E
1.21.44 Number of TBs Initially Transmitted to Cell Edge UEs on

the Downlink SCH
Counters
1526741768 L.Traffic.DL.S L.Traffic.DL.S BTS3203E LTE L

CH.TB.Border CH.TB.Border
UE UE
Description
The counter measures the number of TBs initially transmitted to cell edge UEs on the
downlink SCH in a cell. The measurement does not involve eMTC UEs.
Measurement Points
The counter is incremented by 1 each time a TB is initially transmitted to a cell edge UE on
the downlink SCH in a cell. The internal timer of the eNodeB has a deviation of one period,
and therefore the value of the counter has deviation to the actual duration.
Formula
None
Unit
None
Related Features
L.Traffic.DL.SCH.TB.Bord Multi-mode: None

erUE GSM: None
UMTS: None
Management

BTS3203E
1.21.45 Number of Downlink Erroneous TBs After Initial

Transmission to Cell Edge Ues
Counters

CH.ErrTB.Ibler. CH.ErrTB.Ibler.
BorderUE BorderUE
Description
The counter measures the number of erroneous TBs initially transmitted to cell edge UEs on
the downlink SCH in a cell. The measurement does not involve eMTC UEs.
Measurement Points
The counter is incremented by 1 each time the eNodeB receives a downlink erroneous TB
indicator after initial transmission to a cell edge UE on the downlink SCH in a cell.
Formula
None
Unit
None
Related Features
L.Traffic.DL.SCH.ErrTB.Ibl Multi-mode: None

er.BorderUE GSM: None
UMTS: None
Management

BTS3203E
1.21.46 Number of Downlink Erroneous TBs After the Maximum

number of Retransmissions to Cell Edge UEs Is Reached
Counters

CH.ErrTB.Rble CH.ErrTB.Rble
r.BorderUE r.BorderUE
Description
The counter measures the number of erroneous TBs after the maximum number of
retransmissions to cell edge UEs on the downlink SCH is reached in a cell. The measurement
does not involve eMTC UEs.
Measurement Points
The counter is incremented by 1 each time the eNodeB receives a downlink erroneous TB
indicator after the maximum number of retransmissions to a cell edge UE on the downlink
SCH is reached in a cell.
Formula
None
Unit
None
Related Features
L.Traffic.DL.SCH.ErrTB.R Multi-mode: None

bler.BorderUE GSM: None
UMTS: None
Management

BTS3203E
1.21.47 Number of QCI-2 Service TBs Initially Transmitted on the

Uplink SCH
Counters

CH.QPSK.TB. QCI-2 service
QCI.2 TBs initially
transmitted on
the uplink SCH
using QPSK

CH. QCI-2 service
I.2 transmitted on
the uplink SCH
in 16QAM
modulation
mode

CH. QCI-2 service
I.2 transmitted on
the uplink SCH
in 64QAM
modulation
mode
Description
Number of QCI-2 Service TBs Initially Transmitted on the Uplink SCH
Measurement Points
The corresponding counter is incremented by 1 based on the MCS each time the eNodeB
receives a TB initially transmitted on the uplink SCH and determines that the TB includes
services with QCI 2.
An eNodeB can determine whether a TB includes services with QCI 2 only after the uplink
data is resolved correctly. If HARQ retransmissions fail, the eNodeB cannot determine
whether a TB includes services with QCI 2. In this case, the corresponding TBs are not
counted as the TBs occupied by the uplink SCH for transmitting services with QCI 2.
Therefore, the measurement result deviates from the actual value.

BTS3203E
Formula
None
Unit
None
Related Features

B.QCI.2 GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E

Uplink SCH
Counters

Retrans.QCI.2 TBs
retransmitted on
the uplink SCH
in QPSK
modulation
mode

CH. QCI-2 service
16QAM.TB.Ret TBs
the uplink SCH
in 16QAM
modulation
mode

CH. QCI-2 service
64QAM.TB.Ret TBs
the uplink SCH
in 64QAM
modulation
mode
Description
Number of QCI-2 Service TBs Initially Transmitted on the Uplink SCH
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 services with QCI 2, the corresponding counter is
incremented by n based on the MCS.
An eNodeB can determine whether a TB includes services with QCI 2 only after the uplink
data is resolved correctly. If HARQ retransmissions fail, the eNodeB cannot determine
whether a TB includes services with QCI 2. In this case, the corresponding TBs are not
counted as the TBs occupied by the uplink SCH for transmitting services with QCI 2.
Therefore, the measurement result deviates from the actual value.

BTS3203E
Formula
None
Unit
None
Related Features

UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E

Downlink SCH Using QPSK
Counters

QCI.2 TBs initially
transmitted on
the downlink
SCH in QPSK
modulation
mode

CH. QCI-2 service
I.2 transmitted on
the downlink
SCH in
16QAM
modulation
mode

CH. QCI-2 service
I.2 transmitted on
the downlink
SCH in
64QAM
modulation
mode
Description
Number of QCI-2 Service TBs Initially Transmitted on the Downlink SCH Using QPSK
Measurement Points
The corresponding counter is incremented by 1 based on the MCS each time a TB is initially
transmitted on the downlink SCH and the eNodeB determines that the TB includes services
with QCI 2.

BTS3203E
Formula
None
Unit
None
Related Features

B.QCI.2 GSM: None
UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
64QAM

BTS3203E
1.21.50 Number of QCI-2 Service TBs Retransmitted on the

Downlink SCH Using QPSK
Counters

Retrans.QCI.2 TBs
retransmitted on
the downlink
SCH in QPSK
modulation
mode

CH. QCI-2 service
16QAM.TB.Ret TBs
the downlink
SCH in
16QAM
modulation
mode

CH. QCI-2 service
64QAM.TB.Ret TBs
the downlink
SCH in
64QAM
modulation
mode
Description
Number of QCI-2 Service TBs Retransmitted on the Downlink SCH Using QPSK
Measurement Points
The corresponding counter is incremented by 1 based on the MCS each time a TB is
retransmitted on the downlink SCH and the eNodeB determines that the TB includes services
with QCI 2.

BTS3203E
Formula
None
Unit
None
Related Features

UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
64QAM

UMTS: None
DL/UL 16QAM, DL
64QAM
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.

BTS3203E
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.
Counters
1526727378 L.Traffic.User.Avg Average number of BTS3203E LTE:

users in a cell V100R006C00
1526727379 L.Traffic.User.Max Maximum number BTS3203E LTE:

of users in a cell V100R006C00
1526727380 L.Traffic.CEU.Avg Average number of BTS3203E LTE:

downlink cell edge version earlier than
users (CEUs) in a V100R003C00
cell
1526727381 L.Traffic.CEU.Max Maximum number BTS3203E LTE:

of downlink cell version earlier than
edge users (CEUs) V100R003C00
in a cell
1526727382 L.Traffic.User.ULD Average number of BTS3203E LTE:

ata.Avg UEs with data in the V100R006C00
uplink buffer
1526727383 L.Traffic.User.ULD Maximum number BTS3203E LTE:

ata.Max of UEs with data in V100R006C00
the uplink buffer
1526727384 L.Traffic.User.DLD Average number of BTS3203E LTE:

ata.Avg UEs with data in the V100R006C00
downlink buffer
1526727385 L.Traffic.User.DLD Maximum number BTS3203E LTE:

ata.Max of UEs with data in V100R006C00
the downlink buffer
1526728333 L.Traffic.User.Ulsy Average number of BTS3203E LTE:

nc.Avg UL synchronized V100R006C00
users in a cell
1526728335 L.Traffic.User.Data Maximum number BTS3203E LTE:

.Max of users with data in V100R006C00
the buffer
1526728336 L.Traffic.User.Data Average number of BTS3203E LTE:

.Avg users with data in V100R006C00
the buffer

BTS3203E

1526728338 L.ULCoMP.User.A Average number of BTS3203E LTE:

vg UL CoMP UEs in a V100R006C00
cell
1526728339 L.ULCoMP.User.M Maximum number BTS3203E LTE:

ax of UL CoMP UEs in V100R006C00
a cell
1526728427 L.Traffic.User.SCel Average number of BTS3203E LTE:

l.DL.Avg downlink CA UEs V100R006C00
that use the local
cell as their
secondary serving
cells
1526728445 L.Traffic.ActiveUse Total number of BTS3203E LTE:

r.UL.QCI.Total activated UEs with a V100R006C00
QCI (or an extended
QCI) in the uplink
buffer
1526728446 L.Traffic.ActiveUse Number of activated BTS3203E LTE:

r.UL.QCI.1 UEs with the QCI of V100R006C00
1 in the uplink
buffer

2 in the uplink
buffer

3 in the uplink
buffer

4 in the uplink
buffer

5 in the uplink
buffer

6 in the uplink
buffer

BTS3203E


7 in the uplink
buffer

8 in the uplink
buffer

9 in the uplink
buffer
1526728455 L.Traffic.ActiveUse Total number of BTS3203E LTE:

r.DL.QCI.Total activated UEs with a V100R006C00
QCI (or an extended
QCI) in the
downlink buffer

r.DL.QCI.1 UEs with the QCI of V100R006C00
1 in the downlink
buffer

2 in the downlink
buffer

3 in the downlink
buffer

4 in the downlink
buffer

5 in the downlink
buffer

6 in the downlink
buffer

BTS3203E


7 in the downlink
buffer

8 in the downlink
buffer

9 in the downlink
buffer
1526728473 L.Traffic.ULCEU. Average number of BTS3203E LTE:

Avg uplink cell edge V100R008C00
users (CEUs) in a
cell
1526728474 L.Traffic.ULCEU. Maximum number BTS3203E LTE:

Max of uplink cell edge V100R008C00
users (CEUs) in a
cell
1526728481 L.Traffic.User.SRS. Average number of BTS3203E LTE:

Avg UEs configured with V100R006C00
sounding reference
signal (SRS)
resources in a cell
1526728482 L.Traffic.User.SRS. Maximum number BTS3203E LTE:

Max of UEs configured V100R006C00
with sounding
reference signal
(SRS) resources in a
cell
1526728496 L.Traffic.User.TtiB Average number of BTS3203E LTE:

undling.Avg UEs on which TTI V100R006C00
bundling takes effect
in a cell
1526728517 L.Traffic.User.SCel Maximum number BTS3203E LTE:

l.DL.Max of downlink CA V100R006C00
UEs that use the
local cell as their
secondary serving
cells

BTS3203E

1526728524 L.Traffic.User.RoH Maximum number BTS3203E LTE:

C.Max of UEs on which V100R006C00
ROHC takes effect
in a cell
1526728525 L.Traffic.User.RoH Average number of BTS3203E LTE:

C.Avg UEs on which V100R006C00
ROHC takes effect
in a cell
1526728546 L.Traffic.User.Cdr Average number of BTS3203E LTE:

x.Avg UEs on which DRX V100R006C00
takes effect in a cell
1526728969 L.Traffic.ActiveUse Average number of BTS3203E LTE:

r.DL.Avg activated UEs in V100R006C00
downlink
1526728970 L.Traffic.ActiveUse Maximum number BTS3203E LTE:

r.DL.Max of activated UEs in V100R006C00
downlink

r.UL.Avg activated UEs in V100R006C00
uplink

r.UL.Max of activated UEs in V100R006C00
uplink

r.Avg activated UEs V100R006C00

r.Max of activated UEs V100R006C00
1526729297 L.Traffic.User.eICI Average number of BTS3203E LTE:

C.Avg eICIC-capable UEs V100R008C01
in a cell
1526729298 L.Traffic.User.eICI Maximum number BTS3203E LTE:

C.Max of eICIC-capable V100R008C01
UEs in a cell
1526729557 L.Traffic.HetnetCE Average number of BTS3203E LTE:

U.Avg UEs in a cell that are V100R009C00
close to the border
with the other type
of cells in a HetNet

BTS3203E


U.eICIC.Avg eICIC-capable UEs V100R009C00
in a cell that are
close to the border
with the other type
1526730100 L.Traffic.Privilege. Average number of BTS3203E LTE:

User.avg privileged UEs in a V100R007C00
cell
1526730101 L.Traffic.Privilege. Maximum number BTS3203E LTE:

User.max of privileged UEs in V100R007C00
a cell
1526730143 L.Traffic.User.TA Average number of BTS3203E LTE:

Meas.PUCCH.Avg UEs whose uplink V100R007C00
timing offsets are
measured based on
the PUCCH
1526730144 L.Traffic.User.TA Maximum number BTS3203E LTE:

Meas.PUCCH.Max of UEs whose uplink V100R007C00
timing offsets are
measured based on
the PUCCH

r.DL.QCI.Total.Ma of activated UEs V100R011C10
x with a QCI (or an
extended QCI) in the
downlink buffer

r.DL.QCI.1.Max of activated UEs V100R011C10
the downlink buffer

the downlink buffer

the downlink buffer

the downlink buffer

BTS3203E


the downlink buffer

the downlink buffer

the downlink buffer

the downlink buffer

the downlink buffer

r.UL.QCI.Total.Ma of activated UEs V100R011C10
x with a QCI (or an
extended QCI) in the
uplink buffer

r.UL.QCI.1.Max of activated UEs V100R011C10
the uplink buffer

the uplink buffer

the uplink buffer

the uplink buffer

BTS3203E


the uplink buffer

the uplink buffer

the uplink buffer

the uplink buffer

the uplink buffer
1526730832 L.Traffic.SUNPT.D Average number of BTS3203E LTE:

L.Avg scheduled UEs per V100R011C10
TTI in the downlink
in a cell
1526730833 L.Traffic.SUNPT.D Maximum number BTS3203E LTE:

L.Max of scheduled UEs V100R011C10
per TTI in the
downlink in a cell
1526730838 L.Traffic.SUNPT.U Average number of BTS3203E LTE:

L.Avg scheduled UEs per V100R011C10
TTI in the uplink in
a cell
1526730839 L.Traffic.SUNPT.U Maximum number BTS3203E LTE:

L.Max of scheduled UEs V100R011C10
per TTI in the uplink
in a cell
1526730840 L.Traffic.SUNPT.U Maximum total BTS3203E LTE:

LDL.Max number of scheduled V100R011C10
UEs per TTI in the
uplink and downlink
in a cell

BTS3203E

1526730878 L.Traffic.User.Lice Average licensed BTS3203E LTE:

nse.Avg number of UEs in V100R011C10
RRC_CONNECTE
D mode
1526731537 L.Traffic.User.US. Average number of BTS3203E LTE:

Avg UEs running V100R011C10
unlimited services
1526731538 L.Traffic.User.US. Maximum number BTS3203E LTE:

Max of UEs running V100R011C10
unlimited services

l.Active.DL.Avg activated CA UEs V100R006C00
that use the local
cell as their Scell

l.Active.DL.Max of activated CA UEs V100R006C00
that use the local
cell as their Scell
1526732676 L.Traffic.User.Inde Number of times the BTS3203E LTE:

x0 UE quantity in a cell V100R011C10
falls within the
range indicated by
index 0

falls within the
range indicated by
index 1

falls within the
range indicated by
index 2

falls within the
range indicated by
index 3

falls within the
range indicated by
index 4

BTS3203E


falls within the
range indicated by
index 5

falls within the
range indicated by
index 6

falls within the
range indicated by
index 7

falls within the
range indicated by
index 8

falls within the
range indicated by
index 9

falls within the
range indicated by
index 10
1526732721 L.Traffic.User.VoIP Average number of BTS3203E LTE:

.Avg VoIP UEs in a cell V100R011C10
1526732722 L.Traffic.User.VoIP Maximum number BTS3203E LTE:

.Max of VoIP UEs in a V100R011C10
cell
1526732723 L.Traffic.User.TM9 Average number of BTS3203E LTE:

.Avg UEs that apply TM9 V100R011C10
in a cell

BTS3203E


l.DL.RelaxedBackh of CA UEs that treat V100R011C10
aulCA.Max the local cell as their
SCell in the relaxed-
backhaul-based
inter-eNodeB CA
state

l.DL.RelaxedBackh CA UEs that treat V100R011C10
aulCA.Avg the local cell as their
SCell in the relaxed-
backhaul-based
inter-eNodeB CA
state
1526733173 L.ULCoMP.Hetnet Average number of BTS3203E LTE:

CoMP.User.Avg UEs selected for V100R011C10
whom HetNet UL
CoMP is performed
in a cell
1526733174 L.ULCoMP.Hetnet Maximum number BTS3203E LTE:

CoMP.User.Max of UEs selected for V100R011C10
whom HetNet UL
CoMP is performed
in a cell
1526736781 L.Traffic.GBRUser. Number of UEs that BTS3203E LTE:

BitRate.Index0 are configured with V100R011C10
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

BTS3203E


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
1526736790 L.Traffic.User.Ulsy Maximum number BTS3203E LTE:

nc.Max of UL-sync UEs in a V100R011C10
cell
1526736871 L.Traffic.User.FeIC Average number of BTS3203E LTE:

IC.Avg FeICIC-capable UEs V100R010C10
in a cell

U.FeICIC.Avg FeICIC-capable UEs V100R010C10
in a cell that are
close to the border
with the other type
1526737747 L.Traffic.User.CEU Number of UEs BTS3203E LTE:

.DL.AICIC.Avg identified as CEUs V100R011C10
in downlink
adaptive ICIC

BTS3203E

1526737749 L.ULCAMC.User. Average number of BTS3203E LTE:

Avg UEs for which V100R011C10
coordinated uplink
AMC is used in a
cell
1526737752 L.Traffic.User.Inter Average number of BTS3203E LTE:

EnbDLComp.Avg DL CoMP UEs in a V100R011C10
cell
1526737760 L.Traffic.ULShare Average number of BTS3203E LTE:

d.USER.Avg UEs using the V100R011C10
UMTS and LTE
shared spectrum in a
cell
1526737763 L.ULCoMP.ULRel Average number of BTS3203E LTE:

axedBHCoMP.User UEs selected for V100R011C10
.Avg whom UL CoMP
based on relaxed
backhaul is
performed in a cell
1526737851 L.Traffic.User.InSe Average number of BTS3203E LTE:

ssion.Avg UEs with service V100R011C10
data to be
transmitted in a cell
1526737852 L.Traffic.User.InSe Maximum number BTS3203E LTE:

ssion.Max of UEs with service V100R011C10
data to be
transmitted in a cell
1526739724 L.Traffic.User.Sam Number of times the BTS3203E LTE:

ple.Num number of UEs in V100R011C10
RRC_CONNECTE
D mode is not zero
1526739742 L.Traffic.User.Unsy Number of UEs BTS3203E LTE:

n.Drx.Avg configured with out- V100R011C10
of-synchronization
DRX parameters in
a cell
1526740478 L.Traffic.SpecSerU Average number of BTS3203E LTE:

ser.Avg dedicated service V100R011C10
users
1526741888 L.Traffic.User.Bord Average number of BTS3203E LTE:

erUE.Avg CEUs in a cell V100R011C10

BTS3203E

1526741889 L.Traffic.User.Bord Maximum number BTS3203E LTE:

erUE.Max of CEUs in a cell V100R011C10
1526741890 L.Traffic.User.Intr Average number of BTS3203E LTE:

aBoard.BorderUE. intra-BBP CEUs in a V100R011C10
Avg cell
1526741891 L.Traffic.User.Intr Average number of BTS3203E LTE:

aBBUInterBoard.B intra-BBU inter- V100R011C10
orderUE.Avg BBP CEUs in a cell
1526741892 L.Traffic.User.Inter Average number of BTS3203E LTE:

BBU.BorderUE.Av inter-BBU CEUs in V100R011C10
g a cell
1526742153 L.Traffic.User.UE. Average number of BTS3203E LTE:

Req.Drx.Avg UEs that apply V100R011C10
requested DRX
1526743746 L.Traffic.User.NAI Average number of BTS3203E LTE:

CS.Avg NAICS-capable UEs V100R012C00
in a cell
1526745666 L.Traffic.CRSIC.U Average number of BTS3203E LTE:

ser.Avg CRS-IC-capable V100R012C10
UEs in a cell
1526745700 L.Traffic.User.MC Average number of BTS3203E LTE:

PTT.Avg UEs performing V100R012C10
MCPTT voice
services in a cell
1526745701 L.Traffic.User.MC Maximum number BTS3203E LTE:

PTT.Max of UEs performing V100R012C10
MCPTT voice
services in a cell
1526745761 L.Traffic.User.UEC Average number of BTS3203E LTE:

ooperation.Avg UEs supporting V100R012C10
specific-UE device-
pipe synergy in a
cell
1526745762 L.Traffic.User.UEC Maximum number BTS3203E LTE:

ooperation.Max of UEs supporting V100R012C10
specific-UE device-
pipe synergy in a
cell

r.DL.WBB.Avg activated WBB UEs V100R012C10
in the downlink

BTS3203E


r.UL.WBB.Avg activated WBB UEs V100R012C10
in the uplink
1526745955 L.Traffic.User.WB Average number of BTS3203E LTE:

B.Avg WBB UEs in a cell V100R012C10
1526746002 L.Traffic.User.R12 Average number of BTS3203E LTE:

TtiBundling.Avg UEs on which R12 V100R012C10
TTI bundling takes
effect in a cell
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

BTS3203E
1.22.1 Number of Users in a Cell
Counters
1526727378 L.Traffic.User. Average BTS3203E LTE L

Avg number of users
in a cell
1526727379 L.Traffic.User. Maximum BTS3203E LTE L

Max number of users
in a cell

WBB.Avg number of
WBB UEs 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 the RRC_CONNECTED state 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 corresponding
counter values.The number of WBB UEs in the RRC_CONNECTED state in a cell is
sampled per second. At the end of a measurement period, the average of these sampling
results is taken as the corresponding counter value.
Formula
None
Unit
None

BTS3203E
Related Features
L.Traffic.User.Avg Multi-mode: None

GSM: None
UMTS: None
Management
L.Traffic.User.Max Multi-mode: None

GSM: None
UMTS: None
Management
L.Traffic.User.WBB.Avg Multi-mode: None

GSM: None
UMTS: None
Management
1.22.2 Number of ICIC Cell Edge Users in a Cell

Counters
1526727380 L.Traffic.CEU. Average BTS3203E LTE L

Avg number of
downlink cell
edge users
(CEUs) in a cell
1526727381 L.Traffic.CEU. Maximum BTS3203E LTE L

Max number of
downlink cell
edge users
(CEUs) in a cell
1526728473 L.Traffic.ULCE Average BTS3203E LTE L

U.Avg number of
uplink cell edge
users (CEUs) in
a cell

BTS3203E

1526728474 L.Traffic.ULCE Maximum BTS3203E LTE L

U.Max number of
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.
Disuse Statement:
The counter L.Traffic.CEU.Avg (ID: 1526727380) will be replaced by the counter

L.Traffic.User.BorderUE.Avg (ID: 1526741888) in later versions. In the current version, both
will be removed. It is not recommended that the L.Traffic.CEU.Avg counter be used in the
current version.
The counter L.Traffic.CEU.Max (ID: 1526727381) will be replaced by the counter

L.Traffic.User.BorderUE.Max (ID: 1526741889) in later versions. In the current version, both
will be removed. It is not recommended that the L.Traffic.CEU.Max counter be used in the
current version.
The counter L.Traffic.ULCEU.Avg (ID: 1526728473) will be replaced by the counter

L.Traffic.User.BorderUE.Avg (ID: 1526741888) in later versions. In the current version, both
will be removed. It is not recommended that the L.Traffic.ULCEU.Avg counter be used in the
current version.
The counter L.Traffic.ULCEU.Max (ID: 1526728474) will be replaced by the counter

L.Traffic.User.BorderUE.Max (ID: 1526741889) in later versions. In the current version, both
will be removed. It is not recommended that the L.Traffic.ULCEU.Max counter be used in the
current version.
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

BTS3203E
Unit
None
Related Features
L.Traffic.CEU.Avg Multi-mode: None

GSM: None
UMTS: None
Management
L.Traffic.CEU.Max Multi-mode: None

GSM: None
UMTS: None
Management
L.Traffic.ULCEU.Avg Multi-mode: None

GSM: None
UMTS: None
Management
L.Traffic.ULCEU.Max Multi-mode: None

GSM: None
UMTS: None
Management
1.22.3 Number of UEs with Data in the Uplink Buffer
Counters

ULData.Avg number of UEs
with data in the
uplink buffer

ULData.Max number of UEs
with data in the
uplink buffer

BTS3203E
Description
The counters measure the average and maximum number of UEs with data in the uplink
buffer in a cell.
Disuse Statement:
The counter L.Traffic.User.ULData.Avg (ID: 1526727382) will be replaced by the counter
L.Traffic.ActiveUser.UL.Avg (ID: 1526728972) in later versions. In the current version, both
counters are valid and the counter values are normally reported. In later versions, the
L.Traffic.User.ULData.Avg counter will be removed. It is not recommended that the
L.Traffic.User.ULData.Avg counter be used in the current version.
The counter L.Traffic.User.ULData.Max (ID: 1526727383) will be replaced by the counter
L.Traffic.ActiveUser.UL.Max (ID: 1526728973) in later versions. In the current version, both
L.Traffic.User.ULData.Max counter will be removed. It is not recommended that the
L.Traffic.User.ULData.Max counter be used in the current version.
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
Management
L.Traffic.User.ULData.Max Multi-mode: None

GSM: None
UMTS: None
Management

BTS3203E
1.22.4 Number of UEs with Data in the Downlink Buffer
Counters

DLData.Avg number of UEs
with data in the
downlink buffer

DLData.Max number of UEs
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.
Disuse Statement:
The counter L.Traffic.User.DLData.Avg (ID: 1526727384) will be replaced by the counter

L.Traffic.ActiveUser.DL.Avg (ID: 1526728969) in later versions. In the current version, both
L.Traffic.User.DLData.Avg counter will be removed. It is not recommended that the
L.Traffic.User.DLData.Avg counter be used in the current version.
The counter L.Traffic.User.DLData.Max (ID: 1526727385) will be replaced by the counter

L.Traffic.ActiveUser.DL.Max (ID: 1526728970) in later versions. In the current version, both
L.Traffic.User.DLData.Max counter will be removed. It is not recommended that the
L.Traffic.User.DLData.Max counter be used in the current version.
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

BTS3203E
Related Features
L.Traffic.User.DLData.Avg Multi-mode: None

GSM: None
UMTS: None
Management
L.Traffic.User.DLData.Max Multi-mode: None

GSM: None
UMTS: None
Management
1.22.5 Number of UL Synchronized Users in a Cell
Counters

Ulsync.Avg number of UL
synchronized
users in a cell

Ulsync.Max number of UL-
sync UEs in a
cell
Description
The counter measures the average number of UL synchronized users in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of all UL
synchronized users in a cell is sampled per second. At the end of a measurement period, the
average of these sampling results is used as the value of the counter.
Formula
None

BTS3203E
Unit
None
Related Features
L.Traffic.User.Ulsync.Avg Multi-mode: None

GSM: None
UMTS: None
Management
L.Traffic.User.Ulsync.Max Multi-mode: None

GSM: None
UMTS: None
Management
1.22.6 Number of UEs Transmitting or Receiving Data in a Cell

Counters

Data.Max number of users
with data in the
buffer

Data.Avg number of users
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.

BTS3203E
Formula
None
Unit
None
Related Features
L.Traffic.User.Data.Max Multi-mode: None

GSM: None
UMTS: None
Management
L.Traffic.User.Data.Avg Multi-mode: None

GSM: None
UMTS: None
Management
1.22.7 Number of UL CoMP UEs in a Cell
Counters
1526728338 L.ULCoMP.Use Average BTS3203E LTE L

r.Avg number of UL
CoMP UEs in a
cell
1526728339 L.ULCoMP.Use Maximum BTS3203E LTE L

r.Max number of UL
CoMP UEs in a
cell
1526733173 L.ULCoMP.Het Average BTS3203E LTE L

netCoMP.User. number of UEs
Avg selected for
whom HetNet
UL CoMP is
performed in a
cell

BTS3203E

1526733174 L.ULCoMP.Het Maximum BTS3203E LTE L

netCoMP.User. number of UEs
Max selected for
whom HetNet
UL CoMP is
performed in a
cell
1526737763 L.ULCoMP.UL Average BTS3203E LTE L

RelaxedBHCo number of UEs
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.

BTS3203E
Formula
None
Unit
None
Related Features
L.ULCoMP.User.Avg Multi-mode: None

GSM: None
UMTS: None
L.ULCoMP.User.Max Multi-mode: None

GSM: None
UMTS: None
L.ULCoMP.HetnetCoMP.Us Multi-mode: None

er.Avg GSM: None
UMTS: None
L.ULCoMP.HetnetCoMP.Us Multi-mode: None

er.Max GSM: None
UMTS: None
L.ULCoMP.ULRelaxedBH Multi-mode: None

CoMP.User.Avg GSM: None
UMTS: None

BTS3203E
1.22.8 Number of CA UEs in a Cell

Counters
1526728427 L.Traffic.User.S Average BTS3203E LTE L

Cell.DL.Avg number of
downlink CA
UEs that use the
local cell as
their secondary
serving cells
1526728517 L.Traffic.User.S Maximum BTS3203E LTE L

Cell.DL.Max number of
downlink CA
UEs that use the
local cell as
their secondary
serving cells
Description
The counters measure the average number and maximum number of CA UEs that treat the
local cell as their SCell in the downlink CA state.
Measurement Points
The counter values are generated 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 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.
Formula
None
Unit
None

BTS3203E
Related Features
L.Traffic.User.SCell.DL.Av Multi-mode: None

g GSM: None
UMTS: None
2CC in 20MHz
LAOFD-070201
Inter-Band Carrier
2CC in 20MHz
Carriers
L.Traffic.User.SCell.DL.Ma Multi-mode: None

x GSM: None
UMTS: None
2CC in 20MHz
LAOFD-070201
Inter-Band Carrier
2CC in 20MHz
Carriers
1.22.9 Average Number of Activated UEs with a Specific QCI in

the Uplink Buffer
Counters
1526728445 L.Traffic.Active Total number of BTS3203E LTE L

User.UL.QCI.T activated UEs
otal with a QCI (or
an extended
QCI) in the
uplink buffer

BTS3203E

1526728446 L.Traffic.Active Number of BTS3203E LTE L

User.UL.QCI.1 activated UEs
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

BTS3203E


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
Management

I.1 GSM: None
UMTS: None
Management

BTS3203E

I.2 GSM: None
UMTS: None
Management

I.3 GSM: None
UMTS: None
Management

I.4 GSM: None
UMTS: None
Management

I.5 GSM: None
UMTS: None
Management

I.6 GSM: None
UMTS: None
Management

I.7 GSM: None
UMTS: None
Management

I.8 GSM: None
UMTS: None
Management

BTS3203E

I.9 GSM: None
UMTS: None
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 BTS3203E LTE L

User.DL.QCI.T activated UEs
otal with a QCI (or
an extended
QCI) in the
downlink buffer

User.DL.QCI.1 activated UEs
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

BTS3203E


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

BTS3203E
Unit
None
Related Features
L.Traffic.ActiveUser.DL.QC Multi-mode: None

I.Total GSM: None
UMTS: None
Management

I.1 GSM: None
UMTS: None
Management

I.2 GSM: None
UMTS: None
Management

I.3 GSM: None
UMTS: None
Management

I.4 GSM: None
UMTS: None
Management

I.5 GSM: None
UMTS: None
Management

BTS3203E

I.6 GSM: None
UMTS: None
Management

I.7 GSM: None
UMTS: None
Management

I.8 GSM: None
UMTS: None
Management

I.9 GSM: None
UMTS: None
Management
1.22.11 Number of UEs Configured with SRS Resources in a Cell

Counters

RS.Avg number of UEs
configured with
sounding
reference signal
(SRS) resources
in a cell

BTS3203E


RS.Max number of UEs
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
Management
L.Traffic.User.SRS.Max Multi-mode: None

GSM: None
UMTS: None
Management

BTS3203E
1.22.12 Number of UEs on Which TTI Bundling Takes Effect in a

Cell
Counters
1526728496 L.Traffic.User.T Average BTS3203E LTE L

tiBundling.Avg number of UEs
on which TTI
bundling takes
effect in a cell

R12TtiBundlin number of UEs
g.Avg on which R12
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

BTS3203E
L.Traffic.User.R12TtiBundli Multi-mode: None

ng.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
on which
ROHC takes
effect in a cell

RoHC.Avg number of UEs
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

BTS3203E
Related Features
L.Traffic.User.RoHC.Max Multi-mode: None

GSM: None
UMTS: None
Compression (ROHC)
L.Traffic.User.RoHC.Avg Multi-mode: None

GSM: None
UMTS: None
Compression (ROHC)
1.22.14 Number of UEs on Which DRX Takes Effect in a Cell
Counters

Cdrx.Avg number of UEs
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
The counters are measured based on the user state at the sampling time. The number of
connected UEs on which DRX takes effect in a cell is sampled per second. At the end of a
measurement period, the average of these sampling results is used as the counter value.
Formula
None
Unit
None

BTS3203E
Related Features
L.Traffic.User.Cdrx.Avg Multi-mode: None

GSM: None
UMTS: None
LBFD-002017 DRX
1.22.15 Number of Activated UEs in the Downlink in a Cell

Counters
1526728969 L.Traffic.Active Average BTS3203E LTE L

User.DL.Avg number of
activated UEs
in downlink
1526728970 L.Traffic.Active Maximum BTS3203E LTE L

User.DL.Max number of
activated UEs
in downlink

User.DL.WBB. number of
Avg activated WBB
UEs in the
downlink
Description
The counters measure the number of UEs that have data in the downlink buffer in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time.
The number of UEs that are in RRC_CONNECTED mode and have data in the downlink
buffer in a cell is sampled per millisecond. At the end of a measurement period, the average
and maximum of these sampling results are taken as the corresponding counter values.
The number of UEs that are identified as WBB UEs, are in the 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 of these sampling results is taken as the
L.Traffic.ActiveUser.DL.WBB.Avg counter value.

BTS3203E
Formula
None
Unit
None
Related Features
L.Traffic.ActiveUser.DL.Av Multi-mode: None

g GSM: None
UMTS: None
Management
L.Traffic.ActiveUser.DL.Ma Multi-mode: None

x GSM: None
UMTS: None
Management
L.Traffic.ActiveUser.DL.W Multi-mode: None

BB.Avg GSM: None
UMTS: None
Management
1.22.16 Number of Activated UEs in the Uplink in a Cell

Counters

User.UL.Avg number of
activated UEs
in uplink

User.UL.Max number of
activated UEs
in uplink

BTS3203E


User.UL.WBB. number of
Avg activated WBB
UEs in the
uplink
Description
The counters measure the number of UEs that have data in the uplink buffer in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time.
The number of UEs that are in RRC_CONNECTED mode and have data in the uplink buffer
in a cell is sampled per millisecond. At the end of a measurement period, the average and
maximum of these sampling results are taken as corresponding counter values.
The number of UEs that are identified as WBB UEs, are in the RRC_CONNECTED mode,
and have data in the uplink buffer in a cell is sampled per millisecond.At the end of a
L.Traffic.ActiveUser.UL.WBB.Avg counter value.
Formula
None
Unit
None
Related Features
L.Traffic.ActiveUser.UL.Av Multi-mode: None

g GSM: None
UMTS: None
Management
L.Traffic.ActiveUser.UL.Ma Multi-mode: None

x GSM: None
UMTS: None
Management

BTS3203E
L.Traffic.ActiveUser.UL.W Multi-mode: None

BB.Avg GSM: None
UMTS: None
Management
1.22.17 Number of Activated UEs in a Cell

Counters

User.Avg number of
activated UEs

User.Max number of
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

BTS3203E
Related Features
L.Traffic.ActiveUser.Avg Multi-mode: None

GSM: None
UMTS: None
Management
L.Traffic.ActiveUser.Max Multi-mode: None

GSM: None
UMTS: None
Management
1.22.18 Number of eICIC-Capable UEs in a Cell
Counters
1526729297 L.Traffic.User.e Average BTS3203E LTE L

ICIC.Avg number of
eICIC-capable
UEs in a cell
1526729298 L.Traffic.User.e Maximum BTS3203E LTE L

ICIC.Max number of
eICIC-capable
UEs in a cell
Description
The counters measure the average and maximum numbers of eICIC-capable UEs in a cell.
Measurement Points
The number of eICIC-capable UEs in RRC_CONNECTED mode is sampled per second in a
cell. At the end of a measurement period, the average and maximum of these sampling results
are taken as the corresponding counter values.
Formula
None

BTS3203E
Unit
None
Related Features
L.Traffic.User.eICIC.Avg Multi-mode: None

GSM: None
UMTS: None
L.Traffic.User.eICIC.Max Multi-mode: None

GSM: None
UMTS: None
1.22.19 Number of UEs in a Cell that are Close to the Border with
the Other Type of Cells in a HetNet
Counters
1526729557 L.Traffic.Hetnet Average BTS3203E LTE L

CEU.Avg number of 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 UEs in a cell that are close to the border with the
other type of cells in a heterogeneous network (HetNet).
The L.Traffic.HetnetCEU.Avg counter applies only to LTE FDD.
Measurement Points
The number of UEs in RRC_CONNECTED mode that meet the following conditions is
sampled per second:

BTS3203E
The UE must report eICIC event A3, and the eNodeB 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.
Formula
None
Unit
None
Related Features
L.Traffic.HetnetCEU.Avg Multi-mode: None

GSM: None
UMTS: None
LAOFD-081234 FeICIC
1.22.20 Number of eICIC-Capable UEs in a Cell that are Close to

the Border with the Other Type of Cells in a HetNet
Counters

CEU.eICIC.Av number of
g eICIC-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 eICIC-capable UEs in a cell that are close to the
border with the other type of cells in a heterogeneous network (HetNet).
The L.Traffic.HetnetCEU.eICIC.Avg counter applies only to LTE FDD.

BTS3203E
Measurement Points
sampled per second:
- The UE must report eICIC event A3.
- The eNodeB 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.
- The UE supports enhanced inter-cell interference coordination (TDM eICIC).
At the end of a measurement period, the average of these sampling results is taken as the
counter value.
Formula
None
Unit
None
Related Features
L.Traffic.HetnetCEU.eICIC. Multi-mode: None

Avg GSM: None
UMTS: None
1.22.21 Number of Privileged UEs in a Cell
Counters
1526730100 L.Traffic.Privile Average BTS3203E LTE L

ge.User.avg number of
privileged UEs
in a cell
1526730101 L.Traffic.Privile Maximum BTS3203E LTE L

ge.User.max number of
privileged UEs
in a cell

BTS3203E
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
L.Traffic.Privilege.User.max Multi-mode: None

GSM: None
UMTS: None
LBFD-002028 Emergency Call

BTS3203E
1.22.22 Number of UEs Whose Uplink Timing Offsets are

Measured Based on the PUCCH
Counters

AMeas.PUCCH number of UEs
.Avg whose uplink
timing offsets
are measured
based on the
PUCCH
1526730144 L.Traffic.User.T Maximum BTS3203E LTE L

AMeas.PUCCH number of UEs
.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.
Measurement Points
The number of UEs whose uplink timing offsets are measured based on the PUCCH in a cell
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

BTS3203E
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.23 Maximum Number of Activated UEs with a QCI in the

Downlink Buffer
Counters

User.DL.QCI.T number of
otal.Max activated UEs
with a QCI (or
an extended
QCI) in the
downlink buffer

User.DL.QCI. number of
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

BTS3203E


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

BTS3203E
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
Management

I.1.Max GSM: None
UMTS: None
Management

I.2.Max GSM: None
UMTS: None
Management

I.3.Max GSM: None
UMTS: None
Management

BTS3203E

I.4.Max GSM: None
UMTS: None
Management

I.5.Max GSM: None
UMTS: None
Management

I.6.Max GSM: None
UMTS: None
Management

I.7.Max GSM: None
UMTS: None
Management

I.8.Max GSM: None
UMTS: None
Management

I.9.Max GSM: None
UMTS: None
Management

BTS3203E
1.22.24 Maximum Number of Activated UEs with a QCI in the

Uplink Buffer
Counters

User.UL.QCI.T number of
otal.Max activated UEs
with a QCI (or
an extended
QCI) in the
uplink buffer

User.UL.QCI. number of
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

BTS3203E


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

BTS3203E
Related Features

I.Total.Max GSM: None
UMTS: None
Management

I.1.Max GSM: None
UMTS: None
Management

I.2.Max GSM: None
UMTS: None
Management

I.3.Max GSM: None
UMTS: None
Management

I.4.Max GSM: None
UMTS: None
Management

I.5.Max GSM: None
UMTS: None
Management

I.6.Max GSM: None
UMTS: None
Management

BTS3203E

I.7.Max GSM: None
UMTS: None
Management

I.8.Max GSM: None
UMTS: None
Management

I.9.Max GSM: None
UMTS: None
Management
1.22.25 Number of Scheduled UEs per TTI in the Downlink in a

Cell
Counters
1526730832 L.Traffic.SUNP Average BTS3203E LTE L

T.DL.Avg number of
scheduled UEs
per TTI in the
downlink in a
cell
1526730833 L.Traffic.SUNP Maximum BTS3203E LTE L

T.DL.Max number of
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. These counters apply
only to LTE FDD.

BTS3203E
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
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.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.26 Number of Scheduled UEs per TTI in the Uplink in a Cell

Counters
1526730838 L.Traffic.SUNP Average BTS3203E LTE L

T.UL.Avg number of
scheduled UEs
per TTI in the
uplink in a cell

BTS3203E

1526730839 L.Traffic.SUNP Maximum BTS3203E LTE L

T.UL.Max number of
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. These counters apply only
to LTE FDD.
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
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.Traffic.SUNPT.UL.Avg Multi-mode: None

GSM: None
UMTS: None
L.Traffic.SUNPT.UL.Max Multi-mode: None

GSM: None
UMTS: None

BTS3203E
1.22.27 Maximum Total Number of Scheduled UEs per TTI in the

Uplink and Downlink in a Cell
Counters
1526730840 L.Traffic.SUNP Maximum total BTS3203E LTE L

T.ULDL.Max number of
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. This counter applies to only LTE FDD.
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

BTS3203E
1.22.28 Licensed Number of UEs in RRC_CONNECTED Mode

Counters
1526730878 L.Traffic.User.L Average BTS3203E LTE L

icense.Avg licensed
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
Management

BTS3203E
1.22.29 Number of UEs running unlimited services
Counters

US.Avg number of UEs
running
unlimited
services

US.Max number of UEs
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

BTS3203E
L.Traffic.User.US.Max Multi-mode: None

GSM: None
UMTS: None
Management
1.22.30 Average and Maximum Numbers of Activated CA UEs

That Use the Local Cell As Their Scell
Counters

Cell.Active.DL. number of
Avg activated CA
UEs that use the
local cell as
their Scell

Cell.Active.DL. number of
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

BTS3203E
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
2CC in 20MHz
Carriers
L.Traffic.User.SCell.Active. Multi-mode: None

DL.Max GSM: None
UMTS: None
2CC in 20MHz
LAOFD-070201
Inter-Band Carrier
2CC in 20MHz
Carriers
1.22.31 Number of Times the UE Quantity in a Cell Falls Within

Different Ranges
Counters
1526732676 L.Traffic.User.I Number of BTS3203E LTE L

ndex0 times the UE
quantity in a
cell falls within
the range
indicated by
index 0

BTS3203E


ndex1 times the UE
quantity in a
cell falls within
the range
indicated by
index 1

ndex2 times the UE
quantity in a
cell falls within
the range
indicated by
index 2

ndex3 times the UE
quantity in a
cell falls within
the range
indicated by
index 3

ndex4 times the UE
quantity in a
cell falls within
the range
indicated by
index 4

ndex5 times the UE
quantity in a
cell falls within
the range
indicated by
index 5

ndex6 times the UE
quantity in a
cell falls within
the range
indicated by
index 6

BTS3203E


ndex7 times the UE
quantity in a
cell falls within
the range
indicated by
index 7

ndex8 times the UE
quantity in a
cell falls within
the range
indicated by
index 8

ndex9 times the UE
quantity in a
cell falls within
the range
indicated by
index 9

ndex10 times the UE
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.

BTS3203E
Formula
None
Unit
None
Related Features
L.Traffic.User.Index0 Multi-mode: None

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

BTS3203E

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management

GSM: None
UMTS: None
Management
1.22.32 Number of VoIP UEs in a Cell

Counters

VoIP.Avg number of VoIP
UEs in a cell

VoIP.Max number of VoIP
UEs in a cell

BTS3203E
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
Management
L.Traffic.User.VoIP.Max Multi-mode: None

GSM: None
UMTS: None
Management
1.22.33 Number of UEs that apply TM9 in a cell

Counters

M9.Avg number of UEs
that apply TM9
in a cell

BTS3203E
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
DL 2x2 MIMO
1.22.34 Number of CA UEs in the Relaxed-Backhaul-based Inter-

eNodeB CA State
Counters

Cell.DL.Relaxe number of CA
dBackhaulCA. UEs that treat
Max the local cell as
their SCell in
the relaxed-
backhaul-based
inter-eNodeB
CA state

BTS3203E


Cell.DL.Relaxe number of CA
dBackhaulCA. UEs that treat
Avg the local cell as
their SCell in
the relaxed-
backhaul-based
inter-eNodeB
CA state
Description
The counters measure the average number and maximum number of CA UEs that treat the
local cell as their SCell in the relaxed-backhaul-based inter-eNodeB CA state.
Measurement Points
of CA UEs in connected mode that treat the local cell as their SCell in the relaxed-backhaul-
based inter-eNodeB 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.
Formula
None
Unit
None
Related Features
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

BTS3203E
1.22.35 Number of UEs that Are Configured with a GBR and

Whose Throughput Falls Within Different Ranges
Counters
1526736781 L.Traffic.GBR Number of UEs BTS3203E LTE L

User.BitRate.In that are
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

BTS3203E


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
sampling results is used as the value of the corresponding counter.

BTS3203E
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

BTS3203E

Index6 GSM: None
UMTS: None
LTE: None
1.22.36 Number of FeICIC-Capable UEs in a Cell

Counters
1526736871 L.Traffic.User.F Average BTS3203E LTE L

eICIC.Avg number of
FeICIC-capable
UEs in a cell
Description
The counter measures the average number of FeICIC-capable UEs in a cell.
Disuse Statement:
This counter will be replaced by the L.Traffic.User.CRSIC.Avg counter in later versions. In
the current version, both counters are valid and the counter values are normally reported. In
later versions, this counter will be removed. It is not recommended that this counter be used in
the current version.
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

BTS3203E
Related Features
L.Traffic.User.FeICIC.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: LAOFD-081234 FeICIC
1.22.37 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
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 heterogeneous network (HetNet).
Measurement Points
sampled per second:
- The UE must report eICIC event A3.
- The eNodeB 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.
- The UE supports further enhanced inter-cell interference coordination (FeICIC).
At the end of a measurement period, the average of these sampling results is taken as the
counter value.

BTS3203E
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.38 Number of CEUs in Adaptive ICIC in a Cell
Counters
1526737747 L.Traffic.User. Number of UEs BTS3203E LTE L

CEU.DL.AICI identified as
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

BTS3203E
Related Features
None
1.22.39 Average number of UEs for Which Coordinated Uplink

AMC Is Used in a Cell
Counters
1526737749 L.ULCAMC.Us Average BTS3203E LTE L

er.Avg number of UEs
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 TDD.
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
None

BTS3203E
1.22.40 Average Number of Inter-eNodeB DL CoMP UEs in a Cell

Counters
1526737752 L.Traffic.User.I Average BTS3203E LTE L

nterEnbDLCom number of DL
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
None
1.22.41 Average Number of UEs Using the UMTS and LTE Shared
Spectrum in a Cell
Counters
1526737760 L.Traffic.ULSh Average BTS3203E LTE L

ared.USER.Avg number of UEs
using the
UMTS and LTE
shared spectrum
in a cell

BTS3203E
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
L.Traffic.ULShared.USER.Avg counter value.
Formula
None
Unit
None
Related Features
None
1.22.42 Number of UEs with Service Data to Be Transmitted in a

Cell
Counters

nSession.Avg number of UEs
with service
data to be
transmitted in a
cell
1526737852 L.Traffic.User.I Maximum BTS3203E LTE L

nSession.Max number of UEs
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.

BTS3203E
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
Management
L.Traffic.User.InSession.Ma Multi-mode: None

x GSM: None
UMTS: None
Management
1.22.43 Number of Times the Number of UEs in

RRC_CONNECTED Mode Is Not Zero
Counters
1526739724 L.Traffic.User.S Number of BTS3203E LTE L

ample.Num times the
number of UEs
in
RRC_CONNE
CTED mode is
not zero

BTS3203E
Description
The counter measures the number of times the number of UEs in RRC_CONNECTED mode
in a cell is not zero.
Measurement Points
The number of UEs in RRC_CONNECTED mode in a cell is sampled per second. For each
non-zero sampling result, the L.Traffic.User.Sample.Num counter is incremented by 1.
Formula
None
Unit
None
Related Features
L.Traffic.User.Sample.Num Multi-mode: None

GSM: None
UMTS: None
Management
1.22.44 Number of UEs Configured with Out-of-Synchronization

DRX Parameters in a Cell
Counters
1526739742 L.Traffic.User. Number of UEs BTS3203E LTE L

Unsyn.Drx.Avg configured with
out-of-
synchronization
DRX
parameters in a
cell
Description
The counter measures the average number of UEs configured with out-of-synchronization
DRX parameters in a cell.

BTS3203E
Measurement Points
The number of UEs that are in RRC_CONNECTED mode and are configured with out-of-
synchronization DRX parameters in a cell is sampled per second. At the end of a
L.Traffic.User.Unsyn.Drx.Avg counter value.
Formula
None
Unit
None
Related Features
L.Traffic.User.Unsyn.Drx.A Multi-mode: None

vg GSM: None
UMTS: None
1.22.45 Number of Dedicated Service Users

Counters
1526740478 L.Traffic.SpecS Average BTS3203E LTE L

erUser.Avg number of
dedicated
service users
Description
The counters measure the average number of dedicated service users, which is used to
evaluate the distribution of dedicated service users in a cell.
Measurement Points
The number of RRC_CONNECTED UEs in a cell is sampled per second. The average of
these sampling results is used as the value of the L.Traffic.SpecSerUser.Avg counter.
Dedicated service subscribers can be identified if the following requirements are met: (1) The
dedicated service subscribers are identified by the SPID. (2) The SpecifiedUserFlag parameter
in the SpidCfg is set to SPECSERUSER.

BTS3203E
Formula
None
Unit
None
Related Features
L.Traffic.SpecSerUser.Avg Multi-mode: None

GSM: None
UMTS: None
Management
1.22.46 Number of CEUs in a Cell
Counters

BorderUE.Avg number of
CEUs in a cell

BorderUE.Max number of
CEUs in a cell

ntraBoard.Bord number of
erUE.Avg intra-BBP
CEUs in a cell

ntraBBUInterB number of
oard.BorderUE. intra-BBU
Avg inter-BBP
CEUs in a cell

nterBBU.Borde number of inter-
rUE.Avg BBU CEUs in a
cell

BTS3203E
Description
The counters measure the average number and maximum number of cell edge users (CEUs) in
a cell, the average number of intra-BBP CEUs, the number of intra-BBU inter-BBP CEUs,
and the number of inter-BBU CEUs in a cell.
Measurement Points
Average number of CEUs in a cell The counters are measured based on the status of UEs at
the sampling time. The number of CEUs in a cell is sampled per second, at the end of a
measurement period, the average and maximum of these sampling results are taken as the
corresponding counter values. The numbers of intra-BBP, intra-BBU inter-BBP, and inter-
BBU CEUs in the cell are sampled per second, at the end of a measurement period, the
average of these sampling results are taken as the corresponding counter values.
Formula
None
Unit
None
Related Features
L.Traffic.User.BorderUE.Av Multi-mode: None

g GSM: None
UMTS: None
L.Traffic.User.BorderUE.M Multi-mode: None

ax GSM: None
UMTS: None
L.Traffic.User.IntraBoard.B Multi-mode: None

orderUE.Avg GSM: None
UMTS: None
L.Traffic.User.IntraBBUInte Multi-mode: None

rBoard.BorderUE.Avg GSM: None
UMTS: None

BTS3203E
L.Traffic.User.InterBBU.Bo Multi-mode: None

rderUE.Avg GSM: None
UMTS: None
1.22.47 Average Number of UEs that Apply Requested DRX

Parameters in a Cell
Counters

UE.Req.Drx.Av number of UEs
g that apply
requested DRX
parameters in a
cell
Description
The counter measures the number of UEs that apply requested DRX parameters in a cell.
Measurement Points
The number of UEs that apply requested DRX parameters in the RRC_CONNECTED state in
a cell is sampled per second. At the end of a measurement period, the average of these
sampling results is taken as the L.Traffic.User.UE.Req.Drx.Avg counter value.
Formula
None
Unit
None

BTS3203E
Related Features
L.Traffic.User.UE.Req.Drx. Multi-mode: None

Avg GSM: None
UMTS: None
Coordinated Control
1.22.48 Average Number of NAICS-Capable UEs in a Cell

Counters

NAICS.Avg number of
NAICS-capable
UEs in a cell
Description
The counter measures the average number of network-assisted interference cancellation and
suppression-capable (NAICS-capable) UEs in a cell.
Measurement Points
The number of NAICS-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.NAICS.Avg counter.
Formula
None
Unit
None

BTS3203E
Related Features
L.Traffic.User.NAICS.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: LAOFD-120202 NAICS
1.22.49 Average Number of CRS-IC-Capable UEs in a Cell

Counters
1526745666 L.Traffic.CRSI Average BTS3203E LTE L

C.User.Avg number of
CRS-IC-
capable UEs in
a cell
Description
The counter measures the average number of network-assisted interference cancellation and
suppression-capable (CRS-IC-capable) UEs in a cell.
Measurement Points
The number of CRS-IC-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.CRS-IC.User.Avg counter.
Formula
None
Unit
None

BTS3203E
Related Features
L.Traffic.CRSIC.User.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: LAOFD-111206 Network-Assisted CRS IC
1.22.50 Number of UEs Performing MCPTT Voice Services in a

Cell
Counters

MCPTT.Avg number of UEs
performing
MCPTT voice
services in a
cell

MCPTT.Max number of UEs
performing
MCPTT voice
services in a
cell
Description
The counters measure the average number and maximum number of UEs performing MCPTT
voice services in a cell.
Measurement Points
of all UEs in RRC_CONNECTED mode that have QCI 65 bearers is sampled per second in a
cell. At the end of a measurement period, the average and maximum of these sampling results
are taken as the corresponding counter values. If the UE has several QCI 65 bearers, the
eNodeB counts only once for the UE.
Formula
None

BTS3203E
Unit
None
Related Features
L.Traffic.User.MCPTT.Avg Multi-mode: None

GSM: None
UMTS: None
L.Traffic.User.MCPTT.Max Multi-mode: None

GSM: None
UMTS: None
1.22.51 Average Number and Maximum Number of UEs

Supporting Specific-UE Device-pipe Synergy in a Cell
Counters

UECooperation. number of UEs
Avg supporting
specific-UE
device-pipe
synergy in a
cell

UECooperation. number of UEs
Max supporting
specific-UE
device-pipe
synergy in a
cell
Description
The counters measure the average number and maximum number of UEs supporting specific-
UE device-pipe synergy in a cell.

BTS3203E
Measurement Points
The counter values are generated based on the status of UEs at the sampling time.The number
of UEs (in RRC_CONNECTED mode) that support specific-UE device-pipe synergy in a cell
these sampling results are taken as the values of the corresponding counters.
Formula
None
Unit
None
Related Features
L.Traffic.User.UECooperati Multi-mode: None

on.Avg GSM: None
UMTS: None
LTE: LOFD-121203 WTTx Uplink Data
Compression
L.Traffic.User.UECooperati Multi-mode: None

on.Max GSM: None
UMTS: None
LTE: LOFD-121203 WTTx Uplink Data
Compression
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-157, Figure 1-158, and Figure 1-159.

BTS3203E
Figure 1-157
Figure 1-158

BTS3203E
Figure 1-159
Counters
1526726986 L.IRATHO.E2C.Pr Number of inter- BTS3203E LTE:

epAttOut RAT handover V100R006C00
attempts from E-
UTRAN to
CDMA2000
network
1526726987 L.IRATHO.E2C.E Number of inter- BTS3203E LTE:

xecAttOut RAT Handovers V100R006C00
executions from E-
UTRAN to
CDMA2000
network
1526726988 L.IRATHO.E2C.E Number of BTS3203E LTE:

xecSuccOut successful inter-RAT V100R006C00
handovers from E-
UTRAN to
CDMA2000
network
1526726989 L.IRATHO.E2W.P Number of inter- BTS3203E LTE:

repAttOut RAT handover V100R006C00
attempts from E-
UTRAN to
WCDMA network
1526726990 L.IRATHO.E2W.E Number of inter- BTS3203E LTE:

xecAttOut RAT handover V100R006C00
executions from E-
UTRAN to
WCDMA network

BTS3203E

1526726991 L.IRATHO.E2W.E Number of BTS3203E LTE:

handovers from E-
UTRAN to
WCDMA network
1526726992 L.IRATHO.E2G.Pr Number of inter- BTS3203E LTE:

epAttOut RAT handover V100R006C00
attempts from E-
UTRAN to GERAN
1526726993 L.IRATHO.E2G.E Number of inter- BTS3203E LTE:

xecAttOut RAT handover V100R006C00
executions from E-
UTRAN to GERAN
1526726994 L.IRATHO.E2G.E Number of BTS3203E LTE:

handovers from E-
UTRAN to GERAN
1526727226 L.IRATHO.E2T.Pr Number of inter- BTS3203E LTE:

epAttOut RAT Handover V100R006C00
Attempts from E-
UTRAN to TD-
SCDMA network
1526727227 L.IRATHO.E2T.Ex Number of inter- BTS3203E LTE:

ecAttOut RAT handover V100R006C00
executions from E-
UTRAN to TD-
SCDMA network
1526727228 L.IRATHO.E2T.Ex Number of BTS3203E LTE:

ecSuccOut successful inter-RAT V100R006C00
handovers from E-
UTRAN to TD-
SCDMA network

ep.FailOut.MME RAT handover V100R006C00
preparation failures
from E-UTRAN to
GERAN because of
faults on the MME
side

BTS3203E


ep.FailOut.NoRepl RAT handover V100R006C00
y preparation failures
from E-UTRAN to
GERAN because of
no responses from
GERAN

ep.FailOut.PrepFai RAT handover V100R006C00
lure preparation failures
from E-UTRAN to
GERAN due
tobecause GERAN
cells send handover
preparation failure
messages

ep.FailOut.MME RAT handover V100R006C00
from E-UTRAN to
TD-SCDMA
network because of
faults on the MME
side

ep.FailOut.NoRepl RAT handover V100R006C00
y preparation failures
from E-UTRAN to
TD-SCDMA
network due
tobecause of no
responses from TD-
SCDMA network

ep.FailOut.PrepFai RAT handover V100R006C00
lure preparation failures
because TD-
SCDMA network
cells send handover
preparation failure
messages
1526728328 L.IRATHO.BlindH Number of inter- BTS3203E LTE:

O.E2W.PrepAttOu RAT blind handover V100R006C00
t attempts from E-
UTRAN to
WCDMA network

BTS3203E


O.E2W.ExecAttOu RAT blind V100R006C00
t handovers
executions from E-
UTRAN to
WCDMA network

O.E2G.ExecAttOut RAT blind V100R006C00
handovers
executions from E-
UTRAN to GERAN
1526728313 L.IRATHO.BlindH Number of BTS3203E LTE:

O.E2W.ExecSuccO successful inter-RAT V100R006C00
ut blind handovers
from E-UTRAN to
WCDMA network

O.E2G.ExecSuccO successful inter-RAT V100R006C00
ut blind handovers
from E-UTRAN to
GERAN

rep.FailOut.MME RAT handover V100R006C00
from E-UTRAN to
WCDMA network
the MME side

rep.FailOut.PrepFa RAT handover V100R006C00
ilure preparation failures
from E-UTRAN to
WCDMA network
because WCDMA
network cells send
handover
preparation failure
messages

BTS3203E


rep.FailOut.NoRep RAT handover V100R006C00
ly preparation failures
from E-UTRAN to
WCDMA network
because of no
responses from
WCDMA network
1526728321 L.CSFB.PrepAtt Number of CSFB BTS3203E LTE:

indicators received V100R006C00
by the eNodeB
1526728322 L.CSFB.PrepSucc Number of BTS3203E LTE:

successful CSFB V100R006C00
responses from the
eNodeB
1526728323 L.CSFB.E2W Number of BTS3203E LTE:

procedures for V100R006C00
CSFB to WCDMA
network
1526728324 L.CSFB.E2G Number of BTS3203E LTE:

CSFB to GERAN
1526728330 L.RRCRedirection. Number of BTS3203E LTE:

E2W.PrepAtt redirection V100R006C00
preparations from E-
UTRAN to
WCDMA network

E2W redirections from E- V100R006C00
UTRAN to
WCDMA network

E2G redirections from E- V100R006C00
UTRAN to GERAN

O.E2G.PrepAttOut RAT blind handover V100R006C00
attempts from E-
UTRAN to GERAN

E2G.PrepAtt redirection V100R006C00
UTRAN to GERAN

BTS3203E

1526728386 L.CSFB.PrepAtt.Id Number of CSFB BTS3203E LTE:

le indicators received V100R006C00
by the eNodeB for
UEs in idle mode
1526728387 L.CSFB.PrepSucc.I Number of BTS3203E LTE:

dle successful CSFB V100R006C00
responses from the
eNodeB for UEs in
idle mode
1526728388 L.CSFB.E2W.Idle Number of BTS3203E LTE:

CSFB to WCDMA
network for UEs in
idle mode
1526728400 L.IRATHO.SRVC Number of inter- BTS3203E LTE:

C.E2W.PrepAttOut RAT handover V100R006C00
attempts from E-
UTRAN to
WCDMA network
for SRVCC

C.E2W.ExecAttOut RAT handover V100R006C00
executions from E-
UTRAN to
WCDMA network
for SRVCC
1526728402 L.IRATHO.SRVC Number of BTS3203E LTE:

C.E2W.ExecSuccO successful inter-RAT V100R006C00
ut handovers from E-
UTRAN to
WCDMA network
for SRVCC

C.E2G.PrepAttOut RAT handover V100R006C00
attempts from E-
UTRAN to GERAN
for SRVCC

C.E2G.ExecAttOut RAT handover V100R006C00
executions from E-
UTRAN to GERAN
for SRVCC

BTS3203E


C.E2G.ExecSuccO successful inter-RAT V100R006C00
ut handovers from E-
UTRAN to GERAN
for SRVCC

C.E2T.PrepAttOut RAT handover V100R006C00
attempts from E-
UTRAN to TD-
SCDMA network
for SRVCC

C.E2T.ExecAttOut RAT handover V100R006C00
executions from E-
UTRAN to TD-
SCDMA for SRVCC

C.E2T.ExecSuccOu successful inter-RAT V100R006C00
t handovers from E-
UTRAN to TD-
SCDMA network
for SRVCC
1526728409 L.CSFB.LCS.Prep Number of LCS- BTS3203E LTE:

Att triggered CS V100R006C00
fallback indicators
received by the
eNodeB
1526728410 L.CSFB.LCS.Prep Number of BTS3203E LTE:

Succ responses sent from V100R006C00
the eNodeB to
MMEs for CSFB
triggered by LCS
1526728441 L.CCO.E2G.ExecA Number of CCO BTS3203E LTE:

ttOut executions from E- V100R006C00
UTRAN to GERAN
1526728468 L.IRATHO.E2W.N Number of inter- BTS3203E LTE:

oNRT RAT initiation V100R006C00
failures from E-
UTRAN to
WCDMA network
because the adjacent
cell is not on the
NRT of the source
cell

BTS3203E

1526728469 L.IRATHO.E2T.No Number of inter- BTS3203E LTE:

NRT RAT initiation V100R006C00
failures from E-
UTRAN to TD-
SCDMA network
cell is not on the
NRT of the source
cell
1526728470 L.IRATHO.E2G.N Number of inter- BTS3203E LTE:

oNRT RAT initiation V100R006C00
failures from E-
UTRAN to GERAN
cell is not on the
NRT of the source
cell
1526728471 L.IRATHO.E21xR Number of inter- BTS3203E LTE:

TT.NoNRT RAT initiation V100R006C00
failures from E-
UTRAN to
CDMA2000 1xRTT
network because the
adjacent cell is not
on the NRT of the
source cell
1526728472 L.IRATHO.E2HR Number of inter- BTS3203E LTE:

PD.NoNRT RAT initiation V100R006C00
failures from E-
UTRAN to
CDMA2000 HRPD
network because the
on the NRT of the
source cell
1526728497 L.RRCRedirection. Number of CSFB- BTS3203E LTE:

E2W.CSFB based redirections V100R006C00
from E-UTRANs to
WCDMA network

E2G.CSFB based redirections V100R006C00
from E-UTRAN to
GERAN

BTS3203E


E2C.CSFB based redirections V100R006C00
from E-UTRAN to
CDMA2000
network

E2T.CSFB based redirections V100R006C00
from E-UTRAN to
TD-SCDMA
network
1526728501 L.IRATHO.E2C.C Number of CSFB- BTS3203E LTE:

SFB.PrepAttOut based inter-RAT V100R006C00
handover
preparation attempts
from E-UTRAN to
CDMA2000
network
1526728502 L.IRATHO.E2C.C Number of CSFB- BTS3203E LTE:

SFB.ExecAttOut based handover V100R006C00
execution attempts
from E-UTRAN to
CDMA2000
network
1526728503 L.IRATHO.E2C.C Number of BTS3203E LTE:

SFB.ExecSuccOut successful CSFB- V100R006C00
based inter-RAT
handover executions
from E-UTRAN to
CDMA2000
network
1526728504 L.IRATHO.E2W.C Number of CSFB- BTS3203E LTE:

handover
from E-UTRAN to
WCDMA network

SFB.ExecAttOut based inter-RAT V100R006C00
handover execution
attempts from E-
UTRAN to
WCDMA network

BTS3203E

1526728506 L.IRATHO.E2W.C Number of BTS3203E LTE:

based inter-RAT
handover executions
from E-UTRAN to
WCDMA network
1526728507 L.IRATHO.E2G.C Number of CSFB- BTS3203E LTE:

handover
from E-UTRAN to
GERAN

handover execution
attempts from E-
UTRAN to GERAN
1526728509 L.IRATHO.E2G.C Number of BTS3203E LTE:

based inter-RAT
handover executions
from E-UTRAN to
GERAN
1526728510 L.IRATHO.E2T.C Number of CSFB- BTS3203E LTE:

handover
from E-UTRAN to
TD-SCDMA
network

handover execution
attempts from E-
UTRAN to TD-
SCDMA network
1526728512 L.IRATHO.E2T.C Number of BTS3203E LTE:

based inter-RAT
handover executions
from E-UTRAN to
TD-SCDMA
network

BTS3203E

1526728513 L.CSFB.PrepFail.C Number of CSFB BTS3203E LTE:

onflict preparation failures V100R006C00
because of process
conflict
1526728529 L.IRATHO.E2W.L Number of inter- BTS3203E LTE:

oad.PrepAttOut RAT handover V100R006C00
from E-UTRAN to
WCDMA network
triggered because of
high load
1526728530 L.IRATHO.E2W.L Number of inter- BTS3203E LTE:

oad.ExecAttOut RAT handover V100R006C00
execution attempts
from E-UTRAN to
WCDMA network
high load
1526728531 L.IRATHO.E2W.L Number of BTS3203E LTE:

oad.ExecSuccOut successful inter-RAT V100R006C00
handover executions
from E-UTRAN to
WCDMA network
high load

E2W.Load redirections from E- V100R006C00
UTRAN to
WCDMA network
high load
1526728542 L.IRATHO.E2W.R Number of inter- BTS3203E LTE:

egainHPLMN.Prep RAT handover V100R006C00
AttOut attempts from E-
UTRAN to
WCDMA network
triggered for UEs to
go back to the
HPLMN

BTS3203E

1526728543 L.IRATHO.E2W.R Number of inter- BTS3203E LTE:

egainHPLMN.Exec RAT handover V100R006C00
AttOut executions from E-
UTRAN to
WCDMA network
go back to the
HPLMN
1526728544 L.IRATHO.E2W.R Number of BTS3203E LTE:

egainHPLMN.Exec successful inter-RAT V100R006C00
SuccOut handovers from E-
UTRAN to
WCDMA network
go back to the
HPLMN
1526728560 L.IRATHO.E2W.N Number of inter- BTS3203E LTE:

oData.ExecAttOut RAT handover V100R006C00
executions from E-
UTRAN to
WCDMA network
triggered for UEs
that do not transmit
or receive data
1526728561 L.IRATHO.E2W.N Number of BTS3203E LTE:

oData.ExecSuccOu successful inter-RAT V100R006C00
t handovers from E-
UTRAN to
WCDMA network
triggered for UEs
or receive data
1526728705 L.FlashCSFB.E2W Number of BTS3203E LTE:

procedures for flash V100R006C00
CSFB to WCDMA
network
1526728706 L.FlashCSFB.E2G Number of BTS3203E LTE:

procedures for flash V100R006C00
CSFB to GERAN
1526728707 L.CSFB.PrepAtt.E Number of CSFB BTS3203E LTE:

mergency indicators received V100R006C00
by the eNodeB for
emergency calls

BTS3203E

1526728708 L.CSFB.PrepSucc. Number of BTS3203E LTE:

Emergency responses sent from V100R006C00
the eNodeB for
CSFB triggered for
emergency calls
1526728709 L.CSFB.E2W.Eme Number of BTS3203E LTE:

rgency procedures for V100R006C00
CSFB to WCDMA
network triggered
for emergency calls
1526728710 L.CSFB.E2G.Emer Number of BTS3203E LTE:

gency procedures for V100R006C00
CSFB to GERAN
triggered for
emergency calls

O.E2T.PrepAttOut RAT blind handover V100R006C00
attempts from E-
UTRAN to TD-
SCDMA network

O.E2T.ExecAttOut RAT blind handover V100R006C00
executions from E-
UTRAN to TD-
SCDMA network

O.E2T.ExecSuccO successful inter-RAT V100R006C00
ut blind handovers
from E-UTRAN to
TD-SCDMA
network
1526728749 L.CSFB.E2T Number of BTS3203E LTE:

SRVCC to TD-
SCDMA network
1526728750 L.CSFB.E2T.Idle Number of BTS3203E LTE:

SRVCC to TD-
SCDMA network
for UEs in idle mode

E2T.PrepAtt redirection V100R006C00
preparations to TD-
SCDMA network

BTS3203E


E2T redirections to TD- V100R006C00
SCDMA network
1526728753 L.IRATHO.SRVC Number of CSFB- BTS3203E LTE:

C.LCS.E2W.PrepA based handover V100R006C00
ttOut attempts from E-
UTRAN to
WCDMA network
for SRVCC

C.LCS.E2W.ExecA based handover V100R006C00
ttOut executions from E-
UTRAN to
WCDMA network
for SRVCC

C.LCS.E2W.ExecS successful CSFB- V100R006C00
uccOut based handovers
from E-UTRAN to
WCDMA network
for SRVCC

C.LCS.E2G.PrepA based handover V100R006C00
ttOut attempts from E-
UTRAN to GERAN
for SRVCC

C.LCS.E2G.ExecA based handover V100R006C00
ttOut executions from E-
UTRAN to GERAN
for SRVCC

C.LCS.E2G.ExecS successful CSFB- V100R006C00
uccOut based handovers
from E-UTRAN to
GERAN for SRVCC

C.LCS.E2T.PrepAt based handover V100R006C00
tOut attempts from E-
UTRAN to TD-
SCDMA network
for SRVCC

BTS3203E


C.LCS.E2T.ExecAt based handover V100R006C00
tOut executions from E-
UTRAN to TD-
SCDMA network
for SRVCC

C.LCS.E2T.ExecSu successful CSFB- V100R006C00
ccOut based handovers
from E-UTRAN to
TD-SCDMA
network for SRVCC
1526728889 L.IRATHO.E21xR Number of BTS3203E LTE:

TT.MMEAbnormR responses for V100R006C00
sp abnormal causes
received by the
eNodeB from the
MME during inter-
RAT handover
executions from E-
UTRAN to
CDMA2000 1xRTT
network
1526728890 L.IRATHO.E2HR Number of BTS3203E LTE:

PD.MMEAbnorm responses for V100R006C00
Rsp abnormal causes
received by the
eNodeB from the
MME during inter-
RAT handover
executions from E-
UTRAN to
CDMA2000 HRPD
network
1526728891 L.IRATHO.E2W.M Number of BTS3203E LTE:

MEAbnormRsp responses for V100R006C00
abnormal causes
received by the
eNodeB from the
MME during inter-
RAT handover
executions from E-
UTRAN to
WCDMA network

BTS3203E

1526728892 L.IRATHO.E2G.M Number of BTS3203E LTE:

abnormal causes
received by the
eNodeB from the
MME during inter-
RAT handover
executions from E-
UTRAN to GERAN
1526728893 L.IRATHO.E2T.M Number of BTS3203E LTE:

abnormal causes
received by the
eNodeB from the
MME during inter-
RAT handover
executions from E-
UTRAN to TD-
SCDMA network

C.E2W.MMEAbno responses for V100R006C00
rmRsp abnormal causes
received by the
eNodeB from the
MME during inter-
RAT handover
executions from E-
UTRAN to
WCDMA network
for SRVCC

C.E2G.MMEAbno responses for V100R006C00
received by the
eNodeB from the
MME during inter-
RAT handover
executions from E-
UTRAN to GERAN
for SRVCC

BTS3203E


C.E2T.MMEAbnor responses for V100R006C00
mRsp abnormal causes
received by the
eNodeB from the
MME during inter-
RAT handover
executions from E-
UTRAN to TD-
SCDMA network
for SRVCC
1526728898 L.IRATHO.E2C.C Number of BTS3203E LTE:

SFB.MMEAbnorm responses for V100R006C00
Rsp abnormal causes
received by the
eNodeB from the
MME during CSFB-
based inter-RAT
handover executions
from E-UTRAN to
CDMA2000
network

Rsp abnormal causes
received by the
eNodeB from the
MME during CSFB-
based inter-RAT
handover executions
from E-UTRAN to
WCDMA network

Rsp abnormal causes
received by the
eNodeB from the
MME during CSFB-
based inter-RAT
handover executions
from E-UTRAN to
GERAN

BTS3203E

1526728901 L.IRATHO.E2T.C Number of BTS3203E LTE:

Rsp abnormal causes
received by the
eNodeB from the
MME during CSFB-
based inter-RAT
handover executions
from E-UTRAN to
TD-SCDMA
network
1526729054 L.CSFB.E2C Number of BTS3203E LTE:

CSFB to
CDMA2000 1xRTT
network
1526729055 L.CSFB.E2C.Emer Number of BTS3203E LTE:

gency procedures for V100R006C00
CSFB to
CDMA2000 1xRTT
network triggered
for emergency calls
1526729260 L.CSFB.E2G.Idle Number of BTS3203E LTE:

CSFB to GERAN
network for UEs in
idle mode

PD.PrepAttOut RAT handover V100R006C00
attempts from E-
UTRAN to
CDMA2000 HRPD
network

PD.ExecAttOut RAT handover V100R006C00
executions from E-
UTRAN to
CDMA2000 HRPD
network
1526729424 L.IRATHO.E2HR Number of BTS3203E LTE:

PD.ExecSuccOut successful inter-RAT V100R006C00
handovers from E-
UTRAN to
CDMA2000 HRPD
network

BTS3203E


E21xRTT.PrepAtt redirection V100R006C00
UTRAN to
CDMA2000 1xRTT
network

E2HRPD.PrepAtt redirection V100R006C00
UTRAN to
CDMA2000 HRPD
network

E2HRPD.PrepAtt. redirection V100R006C00
PreRegNotComple- preparations from E-
ted UTRAN to
CDMA2000 HRPD
network triggered
because the UE does
not finish
preregistration with
a CDMA2000
HRPD network

E21xRTT redirections from E- V100R006C00
UTRAN to
CDMA2000 1xRTT
network

E2HRPD redirections from E- V100R006C00
UTRAN to
CDMA2000 HRPD
network
1526729432 L.IRATHO.E2W.Ti Average handover BTS3203E LTE:

meAvg duration from E- V100R008C01
UTRAN to
WCDMA network
1526729433 L.IRATHO.E2G.Ti Average handover BTS3203E LTE:

UTRAN to GERAN
1526729434 L.IRATHO.E2T.Ti Average handover BTS3203E LTE:

UTRAN to TD-
SCDMA network

BTS3203E


overage.PrepAttOu coverage-based V100R007C00
t handover
from E-UTRAN to
WCDMA network

overage.ExecAttOu coverage-based V100R007C00
t handover execution
attempts from E-
UTRAN to
WCDMA network

overage.ExecSuccO successful coverage- V100R007C00
ut based handover
executions from E-
UTRAN to
WCDMA network

overage.PrepAttOu coverage-based V100R007C00
t handover
from E-UTRAN to
GERAN

overage.ExecAttOu coverage-based V100R007C00
t handover execution
attempts from E-
UTRAN to GERAN

overage.ExecSuccO successful coverage- V100R007C00
ut based handover
executions from E-
UTRAN to GERAN

E2W.Coverage coverage-based V100R007C00
redirections from E-
UTRAN to
WCDMA network

E2G.Coverage coverage-based V100R007C00
UTRAN to GERAN

BTS3203E

1526729505 L.CCOwithNACC. Number of CSFB- BTS3203E LTE:

E2G.CSFB.ExecAt based CCO with V100R007C00
tOut NACC executions
from E-UTRAN to
GERAN
1526729507 L.CCOwithoutNA Number of CSFB- BTS3203E LTE:

CC.E2G.CSFB.Exe based CCO without V100R007C00
cAttOut NACC executions
from E-UTRAN to
GERAN

SFB.PrepAttOut.E based handover V100R007C00
mergency preparation attempts
to WCDMA
network triggered
for emergency calls

SFB.ExecAttOut.E based handover V100R007C00
mergency execution attempts
to WCDMA
network triggered
for emergency calls

SFB.ExecSuccOut. successful CSFB- V100R007C00
Emergency based handover
executions to
WCDMA network
triggered for
emergency calls

SFB.PrepAttOut.E based handover V100R007C00
mergency preparation attempts
to GERAN triggered
for emergency calls

SFB.ExecAttOut.E based handover V100R007C00
mergency execution attempts
to GERAN triggered
for emergency calls

SFB.ExecSuccOut. successful CSFB- V100R007C00
Emergency based handover
executions to
GERAN triggered
for emergency calls

BTS3203E


E2W.CSFB.TimeO based blind V100R007C00
ut redirections from E-
UTRAN to
WCDMA network
caused by CSFB
protection timer
expiration

E2G.CSFB.TimeO based blind V100R007C00
ut redirections from E-
UTRAN to GERAN
caused by CSFB
protection timer
expiration
1526729544 L.CSFB.E2C.Dual Number of BTS3203E LTE:

Rx procedures for dual- V100R007C00
receiver CSFB to
CDMA 1xRTT
network

E2T.Load redirections from E- V100R007C00
UTRAN to
TDSCDMA
high load
1526730017 L.RRCRedirection. Number of SPID- BTS3203E LTE:

E2W.RegainHPLM based redirections V100R007C00
N back to a WCDMA
network of the
HPLMN
1526730018 L.IRATHO.E2W.S Number of service- BTS3203E LTE:

ervice.PrepAttOut based handover V100R007C00
from E-UTRAN to
WCDMA network
1526730019 L.IRATHO.E2W.S Number of service- BTS3203E LTE:

ervice.ExecAttOut based handover V100R007C00
execution attempts
from E-UTRAN to
WCDMA network

BTS3203E

1526730020 L.IRATHO.E2W.S Number of BTS3203E LTE:

ervice.ExecSuccOu successful service- V100R007C00
t based handover
executions from E-
UTRAN to
WCDMA network
1526730021 L.IRATHO.E2G.Se Number of service- BTS3203E LTE:

rvice.PrepAttOut based handover V100R007C00
from E-UTRAN to
GERAN
1526730022 L.IRATHO.E2G.Se Number of service- BTS3203E LTE:

rvice.ExecAttOut based handover V100R007C00
execution attempts
from E-UTRAN to
GERAN
1526730023 L.IRATHO.E2G.Se Number of BTS3203E LTE:

rvice.ExecSuccOut successful service- V100R007C00
based handover
executions from E-
UTRAN to GERAN
1526730024 L.RRCRedirection. Number of service- BTS3203E LTE:

E2W.Service based redirections V100R007C00
from E-UTRAN to
WCDMA network

E2G.Service based redirections V100R007C00
from E-UTRAN to
GERAN
1526730026 L.IRATHO.E2W.U Number of UL- BTS3203E LTE:

Lquality.PrepAttO quality-based V100R007C00
ut handover
from E-UTRAN to
WCDMA network
1526730027 L.IRATHO.E2W.U Number of UL- BTS3203E LTE:

Lquality.ExecAttO quality-based V100R007C00
ut handover execution
attempts from E-
UTRAN to
WCDMA network

BTS3203E

1526730028 L.IRATHO.E2W.U Number of BTS3203E LTE:

Lquality.ExecSucc successful UL- V100R007C00
Out quality-based
handover executions
from E-UTRAN to
WCDMA network
1526730029 L.IRATHO.E2G.U Number of UL- BTS3203E LTE:

Lquality.PrepAttO quality-based V100R007C00
ut handover
from E-UTRAN to
GERAN
1526730030 L.IRATHO.E2G.U Number of UL- BTS3203E LTE:

Lquality.ExecAttO quality-based V100R007C00
ut handover execution
attempts from E-
UTRAN to GERAN
1526730031 L.IRATHO.E2G.U Number of BTS3203E LTE:

Lquality.ExecSucc successful UL- V100R007C00
Out quality-based
handover executions
from E-UTRAN to
GERAN
1526730032 L.RRCRedirection. Number of UL- BTS3203E LTE:

E2W.Ulquality quality-based V100R007C00
UTRAN to
WCDMA network

E2G.Ulquality quality-based V100R007C00
UTRAN to GERAN

SFB.Prep.FailOut. based outgoing V100R007C00
MME handover
from E-UTRAN to
WCDMA network
because of the MME
side causes

BTS3203E


PrepFailure handover
from E-UTRAN to
WCDMA network
because of the
response of
handover
preparation failure
from WCDMA
network

NoReply handover
from E-UTRAN to
WCDMA network
because of no
response from
WCDMA network

MME handover
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

BTS3203E


NoReply handover
from E-UTRAN to
TD-SCDMA
network because of
no response from
TD-SCDMA
network
1526730082 L.IRATHO.E2W.S Number of SRVCC- BTS3203E LTE:

RVCC.Prep.FailOu based outgoing V100R007C00
t.MME handover
from E-UTRAN to
WCDMA network
because of the MME
side causes

t.PrepFailure handover
from E-UTRAN to
WCDMA network
because of the
response of
handover
preparation failure
from WCDMA
network

t.NoReply handover
from E-UTRAN to
WCDMA network
because of no
response from
WCDMA network

BTS3203E

1526730085 L.IRATHO.E2T.S Number of SRVCC- BTS3203E LTE:

t.MME handover
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

t.NoReply handover
from E-UTRAN to
TD-SCDMA
network because of
no response from
TD-SCDMA
network
1526730088 L.IRATHO.E2G.S Number of SRVCC- BTS3203E LTE:

t.MME handover
from E-UTRAN to
GERAN because of
the MME side
causes

BTS3203E


from E-UTRAN to
GERAN because of
the response of
handover
preparation failure
from GERAN

t.NoReply handover
from E-UTRAN to
GERAN because of
no response from
GERAN
1526730091 L.IRATHO.SRVC Number of CS-only BTS3203E LTE:

C.CSonly.E2W.Pre SRVCC-based V100R007C00
pAttOut outgoing handover
attempts from E-
UTRAN to
WCDMA network

C.CSonly.E2W.Exe SRVCC-based V100R007C00
cAttOut outgoing handover
executions from E-
UTRAN to
WCDMA network

C.CSonly.E2W.Exe successful CS-only V100R007C00
cSuccOut SRVCC-based
outgoing handovers
from E-UTRAN to
WCDMA network

C.CSonly.E2T.Prep SRVCC-based V100R007C00
AttOut outgoing handover
attempts from E-
UTRAN to TD-
SCDMA network

BTS3203E


C.CSonly.E2T.Exec SRVCC-based V100R007C00
AttOut outgoing handover
executions from E-
UTRAN to TD-
SCDMA network

C.CSonly.E2T.Exec successful CS-only V100R007C00
SuccOut SRVCC-based
outgoing handovers
from E-UTRAN to
TD-SCDMA
network

C.CSonly.E2G.Pre SRVCC-based V100R007C00
pAttOut outgoing handover
attempts from E-
UTRAN to GERAN

C.CSonly.E2G.Exe SRVCC-based V100R007C00
cAttOut outgoing handover
executions from E-
UTRAN to GERAN

C.CSonly.E2G.Exe successful CS-only V100R007C00
cSuccOut SRVCC-based
outgoing handovers
from E-UTRAN to
GERAN
1526730146 L.IRATHO.CSFB. Number of SRVCC- BTS3203E LTE:

SRVCC.E2W.Prep based outgoing V100R007C00
AttOut handover attempts
from E-UTRAN to
WCDMA network
for ultra-flash CSFB

SRVCC.E2W.Exec based outgoing V100R007C00
AttOut handover executions
from E-UTRAN to
WCDMA network

BTS3203E

1526730148 L.IRATHO.CSFB. Number of BTS3203E LTE:

SRVCC.E2W.Exec successful SRVCC- V100R007C00
SuccOut based outgoing
handovers from E-
UTRAN to
WCDMA network

O.E2W.MMEAbno responses with V100R011C10
received by the
eNodeB from the
MME during inter-
RAT blind handover
executions from E-
UTRAN to
WCDMA network

O.E2G.MMEAbno responses with V100R011C10
received by the
eNodeB from the
MME during inter-
RAT blind handover
executions from E-
UTRAN to GERAN

SRVCC.E2G.Prep based outgoing V100R011C10
AttOut handover attempts
from E-UTRAN to
GERAN for ultra-
flash CSFB

SRVCC.E2G.Exec based outgoing V100R011C10
AttOut handover executions
from E-UTRAN to
GERAN for ultra-
flash CSFB
1526733008 L.IRATHO.CSFB. Number of BTS3203E LTE:

SRVCC.E2G.Exec successful SRVCC- V100R011C10
SuccOut based outgoing
handovers from E-
UTRAN to GERAN

BTS3203E

1526733009 L.IRATHO.CSFB. Number of abnormal BTS3203E LTE:

SRVCC.E2G.MME responses from the V100R011C10
AbnormRsp MME during
outgoing handovers
from E-UTRAN to
GERAN for ultra-
flash CSFB
1526733190 L.IRATHO.E2T.Lo Number of inter- BTS3203E LTE:

ad.PrepAttOut RAT handover V100R011C10
from E-UTRAN to
TD-SCDMA
network triggered
because of high load
1526733191 L.IRATHO.E2T.Lo Number of inter- BTS3203E LTE:

ad.ExecAttOut RAT handover V100R011C10
execution attempts
from E-UTRAN to
TD-SCDMA
network triggered
1526733192 L.IRATHO.E2T.Lo Number of BTS3203E LTE:

ad.ExecSuccOut successful inter-RAT V100R011C10
handover executions
from E-UTRAN to
TD-SCDMA
network triggered
1526742170 L.IRATHO.SRVC Number of SRVCC- BTS3203E LTE:

C.FailOut.HOCanc based Outgoing V100R011C10
el.ReEst Handover
Cancellations Due to
RRC Connection
Re-establishments
1526745999 L.IRATHO.E2G.E Average EUTRAN- BTS3203E LTE:

xecSuccOutTimeAv to-GERAN V100R012C10
g handover execution
duration
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

BTS3203E
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 -
t AttOut
L.IRATHO.E2W.RegainHP -
LMN.PrepAttOut
L.IRATHO.E2W.CSFB.Prep L.IRATHO.E2W.CSFB.Prep
AttOut AttOut.Emergency

BTS3203E
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.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 -
t AttOut
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.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

BTS3203E
L.IRATHO.SRVCC.E2W.Ex L.IRATHO.SRVCC.E2W.M
ecSuccOut MEAbnormRsp
L.IRATHO.E2W.ExecSucc L.IRATHO.E2W.Load.Exec -
Out SuccOut
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.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.CSFB.Prep L.IRATHO.E2G.CSFB.Prep

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.CSFB.Exec L.IRATHO.E2G.CSFB.Exec

t AttOut AttOut.Emergency
L.IRATHO.E2G.ExecSuccO L.IRATHO.BlindHO.E2G.E -
ut xecSuccOut

BTS3203E
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.CSFB.Exec L.IRATHO.E2G.CSFB.Exec

ut SuccOut SuccOut.Emergency
L.IRATHO.E2G.CSFB.Exec L.IRATHO.E2G.CSFB.MM
SuccOut EAbnormRsp
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

BTS3203E
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

BTS3203E
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.IRATHO.E2G.CSFB.Exec L.IRATHO.E2G.CSFB.Exec
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.CCO.E2G.ExecAttOut L.CCOwithNACC.E2G.CS -
FB.ExecAttOut
L.CCOwithoutNACC.E2G. -
CSFB.ExecAttOut
L.CSFB.E2T L.CSFB.E2T.Idle -

BTS3203E
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 BTS3203E LTE L

C.PrepAttOut inter-RAT
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.
Measurement Points
As shown at point A in Figure 1-160, 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.

BTS3203E
Figure 1-160
Formula
None
Unit
None
Related Features
L.IRATHO.E2C.PrepAttOut Multi-mode: None

GSM: None
UMTS: None
CDMA2000
Enhanced CS Fallback to
CDMA2000 1xRTT

BTS3203E
1.23.2 Number of Inter-RAT Handovers Executions from E-

UTRAN to CDMA2000 Network
Counters

C.ExecAttOut inter-RAT
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.
Measurement Points
As shown at point B in Figure 1-161, 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-161

BTS3203E
Formula
None
Unit
None
Related Features
L.IRATHO.E2C.ExecAttOu Multi-mode: None

t GSM: None
UMTS: None
CDMA2000
CDMA2000 1xRTT
1.23.3 Number of Successful Inter-RAT Handovers from E-

UTRAN to CDMA2000 Network
Counters

C.ExecSuccOut successful inter-
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.
Measurement Points
As shown at point C in Figure 1-162, 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.

BTS3203E
Figure 1-162
Formula
None
Unit
None
Related Features
L.IRATHO.E2C.ExecSuccO Multi-mode: None

ut GSM: None
UMTS: None
CDMA2000
CDMA2000 1xRTT

BTS3203E

to WCDMA Network
Counters

W.PrepAttOut inter-RAT
handover
attempts from
E-UTRAN to
WCDMA
network
Description
WCDMA network.
Measurement Points
As shown at point A in Figure 1-163, 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-163

BTS3203E
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
CS Fallback to UTRAN

UTRAN to WCDMA Network
Counters

W.ExecAttOut inter-RAT
handover
executions from
E-UTRAN to
WCDMA
network
Description
WCDMA network.
Measurement Points
WCDMA network the L.IRATHO.E2W.ExecAttOut counter is incremented by 1 each time

BTS3203E
Figure 1-164
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

BTS3203E

UTRAN to WCDMA Network
Counters

W.ExecSuccOu successful inter-
t RAT handovers
from E-
UTRAN to
WCDMA
network
Description
WCDMA network.
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-165

BTS3203E
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

to GERAN
Counters

G.PrepAttOut inter-RAT
handover
attempts from
E-UTRAN to
GERAN
Description
GERAN.
Measurement Points
As shown at point A in Figure 1-166, 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.

BTS3203E
Figure 1-166
Formula
None
Unit
None
Related Features
L.IRATHO.E2G.PrepAttOut Multi-mode: None

GSM: None
UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN
CS Fallback to GERAN

BTS3203E

UTRAN to GERAN
Counters

G.ExecAttOut inter-RAT
handover
executions from
E-UTRAN to
GERAN
Description
GERAN.
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-167

BTS3203E
Formula
None
Unit
None
Related Features
L.IRATHO.E2G.ExecAttOu Multi-mode: None

t GSM: None
UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN

UTRAN to GERAN
Counters

G.ExecSuccOut successful inter-
RAT handovers
from E-
UTRAN to
GERAN
Description
GERAN.
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.

BTS3203E
Figure 1-168
Formula
None
Unit
None
Related Features
L.IRATHO.E2G.ExecSuccO Multi-mode: None

ut GSM: None
UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN

BTS3203E

to TD-SCDMA Network
Counters
1526727226 L.IRATHO.E2T Number of BTS3203E LTE L

.PrepAttOut inter-RAT
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.
Measurement Points
As shown at point A in Figure 1-169, 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-169

BTS3203E
Formula
None
Unit
None
Related Features
L.IRATHO.E2T.PrepAttOut Multi-mode: None

GSM: None
UMTS: None
UTRAN
SRVCC to UTRAN

UTRAN to TD-SCDMA Network
Counters

.ExecAttOut inter-RAT
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.
Measurement Points
As shown at point B in Figure 1-170, 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.

BTS3203E
Figure 1-170
Formula
None
Unit
None
Related Features
L.IRATHO.E2T.ExecAttOut Multi-mode: None

GSM: None
UMTS: None
UTRAN
SRVCC to UTRAN

BTS3203E

UTRAN to TD-SCDMA Network
Counters

.ExecSuccOut successful inter-
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.
Measurement Points
As shown at point C in Figure 1-171, 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-171

BTS3203E
Formula
None
Unit
None
Related Features
L.IRATHO.E2T.ExecSuccO Multi-mode: None

ut GSM: None
UMTS: None
UTRAN
SRVCC to UTRAN
1.23.13 Number of Inter-RAT Handover Failures for Different

Causes
Counters

G.Prep.FailOut. inter-RAT
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

BTS3203E


preparation
failures from E-
UTRAN to
GERAN due
tobecause
GERAN cells
send handover
preparation
failure
messages

.Prep.FailOut.M inter-RAT
ME handover
preparation
failures from E-
UTRAN to TD-
SCDMA
network
because of
faults on the
MME side

.Prep.FailOut.N inter-RAT
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
epFailure handover
preparation
failures because
TD-SCDMA
network cells
send handover
preparation
failure
messages

BTS3203E


W.Prep.FailOut. inter-RAT
MME handover
preparation
failures from E-
UTRAN to
WCDMA
network
because of
faults on the
MME side

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,

BTS3203E
the handover resources are prepared. In an inter-RAT handover, a UE is handed over from the
E-UTRAN to another system to ensure service continuity in multi-RAT networking scenarios.
Measurement Points
As shown at point A in Figure 1-172, 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.

BTS3203E
Figure 1-172
Figure 1-173

BTS3203E
Figure 1-174
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
LOFD-001020 PS Inter-RAT Mobility
GERAN
LOFD-001023
Service based inter-RAT
handover to GERAN
SRVCC to GERAN

BTS3203E

ut.NoReply GSM: None
UMTS: None
GERAN
LOFD-001023
handover to GERAN
SRVCC to GERAN

ut.PrepFailure GSM: None
UMTS: None
GERAN
LOFD-001023
handover 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
UTRAN
LOFD-001022
handover to UTRAN
SRVCC to UTRAN

t.NoReply GSM: None
UMTS: None
UTRAN
LOFD-001022
handover to UTRAN
SRVCC to UTRAN

BTS3203E

t.PrepFailure GSM: None
UMTS: None
UTRAN
LOFD-001022
handover 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-001022
handover to UTRAN
SRVCC to UTRAN

ut.PrepFailure GSM: None
UMTS: None
UTRAN
LOFD-001022
handover to UTRAN
SRVCC to UTRAN

ut.NoReply GSM: None
UMTS: None
UTRAN
LOFD-001022
handover to UTRAN
SRVCC to UTRAN

BTS3203E
1.23.14 Number of Inter-RAT Blind Handover Attempts from E-

UTRAN to Another System
Counters
1526728328 L.IRATHO.Blin Number of BTS3203E LTE L

dHO.E2W.Prep inter-RAT blind
AttOut handover
attempts from
E-UTRAN to
WCDMA
network

dHO.E2G.Prep inter-RAT blind
AttOut handover
attempts from
E-UTRAN to
GERAN

dHO.E2T.Prep inter-RAT blind
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.
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.

BTS3203E
If the target system is TD-SCDMA network, the L.IRATHO.BlindHO.E2T.PrepAttOut

Figure 1-175
Formula
None
Unit
None
Related Features
L.IRATHO.BlindHO.E2W.P Multi-mode: None

repAttOut GSM: None
UMTS: None
between E-UTRAN and
UTRAN
L.IRATHO.BlindHO.E2G.P Multi-mode: None

repAttOut GSM: None
UMTS: None

BTS3203E
L.IRATHO.BlindHO.E2T.Pr Multi-mode: None

epAttOut GSM: None
UMTS: None
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
AttOut handovers
executions from
E-UTRAN to
WCDMA
network

dHO.E2G.Exec inter-RAT blind
AttOut handovers
executions from
E-UTRAN to
GERAN

dHO.E2T.Exec inter-RAT blind
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.

BTS3203E
Measurement Points
As shown at point B in Figure 1-176, 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-176
Formula
None
Unit
None

BTS3203E
Related Features
L.IRATHO.BlindHO.E2W.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
L.IRATHO.BlindHO.E2G.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN
L.IRATHO.BlindHO.E2T.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
1.23.16 Number of successful Inter-RAT Blind Handovers from E-

Counters

dHO.E2W.Exec successful inter-
SuccOut RAT blind
handovers from
E-UTRAN to
WCDMA
network

BTS3203E


dHO.E2G.Exec successful inter-
SuccOut RAT blind
handovers from
E-UTRAN to
GERAN

dHO.E2T.Exec successful inter-
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.
Measurement Points
As shown at point C in Figure 1-177, 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

BTS3203E
Figure 1-177
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
L.IRATHO.BlindHO.E2G.E Multi-mode: None

UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN

BTS3203E
L.IRATHO.BlindHO.E2T.E Multi-mode: None

UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
1.23.17 Number of Indicators for CSFB to Another System

Counters
1526728321 L.CSFB.PrepAt Number of BTS3203E LTE L

t CSFB
indicators
received by the
eNodeB

t.Idle CSFB
indicators
received by the
eNodeB for
UEs in idle
mode

t.Emergency CSFB
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.

BTS3203E
Measurement Points
As shown at point A in Figure 1-178, 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-179, 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-178, 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-178, 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-179, 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-178

BTS3203E
Figure 1-179
Formula
None
Unit
None
Related Features
L.CSFB.PrepAtt Multi-mode: None

GSM: None
UMTS: None
1xRTT
L.CSFB.PrepAtt.Idle Multi-mode: None

GSM: None
UMTS: None
1xRTT

BTS3203E
L.CSFB.PrepAtt.Emergency Multi-mode: None

GSM: None
UMTS: None
1xRTT
1.23.18 Number of CSFB Responses to MMEs
Counters
1526728322 L.CSFB.PrepSu Number of BTS3203E LTE L

cc successful
CSFB
responses from
the eNodeB

cc.Idle successful
CSFB
responses from
the eNodeB for
UEs in idle
mode

cc.Emergency responses sent
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.

BTS3203E
Measurement Points
As shown at point C in Figure 1-180, 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-181, 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-180, 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-180, 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-181, 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-180

BTS3203E
Figure 1-181
Formula
None
Unit
None
Related Features
L.CSFB.PrepSucc Multi-mode: None

GSM: None
UMTS: None
1xRTT
L.CSFB.PrepSucc.Idle Multi-mode: None

GSM: None
UMTS: None
1xRTT

BTS3203E
L.CSFB.PrepSucc.Emergen Multi-mode: None

cy GSM: None
UMTS: None
1xRTT
1.23.19 Number of Procedures for CSFB to Another System

Counters
1526728323 L.CSFB.E2W Number of BTS3203E LTE L

procedures for
CSFB to
WCDMA
network
1526728324 L.CSFB.E2G Number of BTS3203E LTE L

procedures for
CSFB to
GERAN
1526728388 L.CSFB.E2W.I Number of BTS3203E LTE L

dle procedures for
CSFB to
WCDMA
network for
UEs in idle
mode
1526728497 L.RRCRedirecti Number of BTS3203E LTE L

on.E2W.CSFB CSFB-based
redirections
from E-
UTRANs to
WCDMA
network

on.E2G.CSFB CSFB-based
redirections
from E-
UTRAN to
GERAN

BTS3203E


on.E2C.CSFB CSFB-based
redirections
from E-
UTRAN to
CDMA2000
network

on.E2T.CSFB CSFB-based
redirections
from E-
UTRAN to TD-
SCDMA
network

C.CSFB.PrepAt CSFB-based
tOut inter-RAT
handover
preparation
attempts from
E-UTRAN to
CDMA2000
network

C.CSFB.ExecA CSFB-based
ttOut handover
execution
attempts from
E-UTRAN to
CDMA2000
network

C.CSFB.ExecS successful
uccOut CSFB-based
inter-RAT
handover
executions from
E-UTRAN to
CDMA2000
network

BTS3203E


W.CSFB.PrepA CSFB-based
ttOut inter-RAT
handover
preparation
attempts from
E-UTRAN to
WCDMA
network

W.CSFB.ExecA CSFB-based
ttOut inter-RAT
handover
execution
attempts from
E-UTRAN to
WCDMA
network

W.CSFB.ExecS successful
uccOut CSFB-based
inter-RAT
handover
executions from
E-UTRAN to
WCDMA
network

G.CSFB.PrepAt CSFB-based
tOut inter-RAT
handover
preparation
attempts from
E-UTRAN to
GERAN

G.CSFB.ExecA CSFB-based
ttOut inter-RAT
handover
execution
attempts from
E-UTRAN to
GERAN

BTS3203E


G.CSFB.ExecS successful
uccOut CSFB-based
inter-RAT
handover
executions from
E-UTRAN to
GERAN

.CSFB.PrepAtt CSFB-based
Out inter-RAT
handover
preparation
attempts from
E-UTRAN to
TD-SCDMA
network

.CSFB.ExecAtt CSFB-based
Out inter-RAT
handover
execution
attempts from
E-UTRAN to
TD-SCDMA
network

.CSFB.ExecSuc successful
cOut CSFB-based
inter-RAT
handover
executions from
E-UTRAN to
TD-SCDMA
network
1526728705 L.FlashCSFB.E Number of BTS3203E LTE L

2W procedures for
flash CSFB to
WCDMA
network
1526728706 L.FlashCSFB.E Number of BTS3203E LTE L

2G procedures for
flash CSFB to
GERAN

BTS3203E

1526728709 L.CSFB.E2W.E Number of BTS3203E LTE L

mergency procedures for
CSFB to
WCDMA
network
triggered for
emergency calls
1526728710 L.CSFB.E2G.E Number of BTS3203E LTE L

CSFB to
GERAN
triggered for
emergency calls
1526728749 L.CSFB.E2T Number of BTS3203E LTE L

procedures for
SRVCC to TD-
SCDMA
network
1526728750 L.CSFB.E2T.Id Number of BTS3203E LTE L

le procedures for
SRVCC to TD-
SCDMA
network for
UEs in idle
mode
1526729054 L.CSFB.E2C Number of BTS3203E LTE L

procedures for
CSFB to
CDMA2000
1xRTT network
1526729055 L.CSFB.E2C.E Number of BTS3203E LTE L

CSFB to
CDMA2000
1xRTT network
triggered for
emergency calls
1526729260 L.CSFB.E2G.Id Number of BTS3203E LTE L

le procedures for
CSFB to
GERAN
network for
UEs in idle
mode

BTS3203E

1526729505 L.CCOwithNA Number of BTS3203E LTE L

CC.E2G.CSFB. CSFB-based
ExecAttOut CCO with
NACC
executions from
E-UTRAN to
GERAN
1526729507 L.CCOwithout Number of BTS3203E LTE L

NACC.E2G.CS CSFB-based
FB.ExecAttOut CCO without
NACC
executions from
E-UTRAN to
GERAN

W.CSFB.PrepA CSFB-based
ttOut.Emergenc handover
y preparation
attempts to
WCDMA
network
triggered for
emergency calls

W.CSFB.ExecA CSFB-based
y execution
attempts to
WCDMA
network
triggered for
emergency calls

W.CSFB.ExecS successful
uccOut.Emerge CSFB-based
ncy handover
executions to
WCDMA
network
triggered for
emergency calls

BTS3203E


G.CSFB.PrepAt CSFB-based
tOut.Emergenc handover
y preparation
attempts to
GERAN
triggered for
emergency calls

G.CSFB.ExecA CSFB-based
y execution
attempts to
GERAN
triggered for
emergency calls

G.CSFB.ExecS successful
uccOut.Emerge CSFB-based
ncy handover
executions to
GERAN
triggered for
emergency calls

on.E2W.CSFB. CSFB-based
TimeOut blind
redirections
from E-
UTRAN to
WCDMA
network caused
by CSFB
protection timer
expiration

on.E2G.CSFB. CSFB-based
TimeOut blind
redirections
from E-
UTRAN to
GERAN caused
by CSFB
protection timer
expiration

BTS3203E

1526729544 L.CSFB.E2C.D Number of BTS3203E LTE L

ualRx procedures for
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.
Measurement Points
As shown at point A in Figure 1-182, 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-182, 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-182, 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-183, 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-182, 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.

BTS3203E
As shown at point B in Figure 1-182, 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-182, 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-183, 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-184, 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-184, 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-184, the L.IRATHO.E2C.CSFB.ExecSuccOut counter is

message from the MME after the UE performs an inter-RAT handover for CSFB to
CDMA2000 network.
As shown at point A in Figure 1-183, the L.RRCRedirection.E2C.CSFB counter is

UE and informs the UE to perform a CSFB procedure to CDMA2000 network.
As shown at point A in Figure 1-182, 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-182, 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-182, 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-183, 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-183, 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-183, 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.

BTS3203E
As shown at point B in Figure 1-182, 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-183, 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-182, 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-183, 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-182, 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-183, 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-182 or point A in Figure 1-183, 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-184, 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-183, 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-185, 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-184, 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-183, the L.CSFB.E2C.Emergency counter is incremented by

BTS3203E

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-185, 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-182, 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-183, 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-182, 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 B in Figure 1-182, 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 A in Figure 1-182, 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-182, 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-182, 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-182, the L.IRATHO.E2G.CSFB.PrepAttOut.Emergency

BTS3203E
(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-183, 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-183, 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-185, 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-186, 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-186, 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.

BTS3203E
Figure 1-182
Figure 1-183

BTS3203E
Figure 1-184
Figure 1-185

BTS3203E
Figure 1-186
Formula
None
Unit
None
Related Features
L.CSFB.E2W Multi-mode: None

GSM: None
UMTS: None
LOFD-070202 Ultra-Flash CSFB to
UTRAN

BTS3203E
L.CSFB.E2G Multi-mode: None

GSM: None
UMTS: None
GERAN
L.CSFB.E2W.Idle Multi-mode: None

GSM: None
UMTS: None
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
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
1xRTT

BTS3203E
L.IRATHO.E2C.CSFB.Exec Multi-mode: None

AttOut GSM: None
UMTS: None
1xRTT
L.IRATHO.E2C.CSFB.Exec Multi-mode: None

SuccOut GSM: None
UMTS: None
1xRTT
L.IRATHO.E2W.CSFB.Prep Multi-mode: None

AttOut GSM: None
UMTS: None
UTRAN
L.IRATHO.E2W.CSFB.Exe Multi-mode: None

cAttOut GSM: None
UMTS: None
UTRAN

cSuccOut GSM: None
UMTS: None
UTRAN
L.IRATHO.E2G.CSFB.Prep Multi-mode: None

AttOut GSM: None
UMTS: None
GERAN

BTS3203E
L.IRATHO.E2G.CSFB.Exec Multi-mode: None

AttOut GSM: None
UMTS: None
GERAN

SuccOut GSM: None
UMTS: None
GERAN
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
UTRAN
L.FlashCSFB.E2G Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001053 Flash CS Fallback to
GERAN

BTS3203E
L.CSFB.E2W.Emergency Multi-mode: None

GSM: None
UMTS: None
L.CSFB.E2G.Emergency Multi-mode: None

GSM: None
UMTS: None
GERAN
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
LOFD-001090 1xRTT
CDMA2000 1xRTT
L.CSFB.E2C.Emergency Multi-mode: None

GSM: None
UMTS: None
LOFD-001090 1xRTT
CDMA2000 1xRTT
L.CSFB.E2G.Idle Multi-mode: None

GSM: None
UMTS: None
GERAN

BTS3203E
L.CCOwithNACC.E2G.CS Multi-mode: None

FB.ExecAttOut GSM: None
UMTS: None
L.CCOwithoutNACC.E2G. Multi-mode: None

CSFB.ExecAttOut GSM: None
UMTS: None

AttOut.Emergency GSM: None
UMTS: None
UTRAN

cAttOut.Emergency GSM: None
UMTS: None
UTRAN

cSuccOut.Emergency GSM: None
UMTS: None
UTRAN
L.IRATHO.E2G.CSFB.Prep Multi-mode: None

UMTS: None
GERAN

UMTS: None
GERAN

BTS3203E

SuccOut.Emergency GSM: None
UMTS: None
GERAN
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
CDMA2000 1xRTT
1.23.20 Number of Inter-RAT Redirection Preparations from E-

Counters

on.E2W.PrepAt redirection
t preparations
from E-
UTRAN to
WCDMA
network

BTS3203E


on.E2G.PrepAtt redirection
preparations
from E-
UTRAN to
GERAN

on.E2T.PrepAtt redirection
preparations to
TD-SCDMA
network

on.E21xRTT.Pr redirection
epAtt preparations
from E-
UTRAN to
CDMA2000
1xRTT network

on.E2HRPD.Pr redirection
epAtt preparations
from E-
UTRAN to
CDMA2000
HRPD network

on.E2HRPD.Pr redirection
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.

BTS3203E
During the procedure, the UE is released by the source cell and accesses the target cell to
continue its services.
Measurement Points
As shown at point A in Figure 1-187, 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-187, the L.RRCRedirection.E2G.PrepAtt counter is

UTRAN to GERAN.
as shown at point A in Figure 1-187, the L.RRCRedirection.E2T.PrepAtt counter is

UTRAN to TD-SCDMA network.
As shown at point A in Figure 1-187, 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-187, 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-187, 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-187
Formula
None
Unit
None

BTS3203E
Related Features
L.RRCRedirection.E2W.Pre Multi-mode: None

pAtt GSM: None
UMTS: None
UTRAN
L.RRCRedirection.E2G.Pre Multi-mode: None

pAtt GSM: None
UMTS: None
GERAN
L.RRCRedirection.E2T.Prep Multi-mode: None

Att GSM: None
UMTS: None
UTRAN
L.RRCRedirection.E21xRT Multi-mode: None

T.PrepAtt GSM: None
UMTS: None
1xRTT
L.RRCRedirection.E2HRPD Multi-mode: None

.PrepAtt GSM: None
UMTS: None
between E-UTRAN and
CDMA2000

.PrepAtt.PreRegNotComple- GSM: None
ted
UMTS: None
between E-UTRAN and
CDMA2000

BTS3203E
1.23.21 Number of Inter-RAT Redirections from E-UTRAN to

Another System
Counters

on.E2W redirections
from E-
UTRAN to
WCDMA
network

on.E2G redirections
from E-
UTRAN to
GERAN

on.E2T redirections to
TD-SCDMA
network

on.E21xRTT redirections
from E-
UTRAN to
CDMA2000
1xRTT network

on.E2HRPD redirections
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.

BTS3203E
Measurement Points
As shown at point A in Figure 1-188, 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-188, 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-188, 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-188, 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-188, 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-188
Formula
None
Unit
None
Related Features
L.RRCRedirection.E2W Multi-mode: None

GSM: None
UMTS: None
UTRAN

BTS3203E
L.RRCRedirection.E2G Multi-mode: None

GSM: None
UMTS: None
GERAN
L.RRCRedirection.E2T Multi-mode: None

GSM: None
UMTS: None
UTRAN
L.RRCRedirection.E21xRT Multi-mode: None

T GSM: None
UMTS: None
1xRTT

GSM: None
UMTS: None
between E-UTRAN and
CDMA2000

BTS3203E

to WCDMA network for SRVCC
Counters
1526728400 L.IRATHO.SR Number of BTS3203E LTE L

VCC.E2W.Prep inter-RAT
AttOut handover
attempts from
E-UTRAN to
WCDMA
network for
SRVCC
Description
WCDMA network for SRVCC in a cell.
Measurement Points
As shown at point A in Figure 1-189, 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.

BTS3203E
Figure 1-189
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
UTRAN

BTS3203E
1.23.23 Number of Inter-RAT Handover Executions from E-

UTRAN to WCDMA network for SRVCC
Counters

VCC.E2W.Exec inter-RAT
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
Measurement Points
WCDMA network for SRVCC the L.IRATHO.SRVCC.E2W.ExecAttOut counter is
to the UE.
Figure 1-190

BTS3203E
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2W.Ex Multi-mode: None

ecAttOut GSM: None
UMTS: None
UTRAN

UTRAN to WCDMA Network for SRVCC
Counters

VCC.E2W.Exec successful inter-
SuccOut RAT handovers
from E-
UTRAN to
WCDMA
network for
SRVCC
Description
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.

BTS3203E
Figure 1-191
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2W.Ex Multi-mode: None

ecSuccOut GSM: None
UMTS: None
UTRAN

BTS3203E

to GERAN for SRVCC
Counters

VCC.E2G.Prep inter-RAT
AttOut handover
attempts from
E-UTRAN to
GERAN for
SRVCC
Description
GERAN for SRVCC in a cell.
Measurement Points
As shown at point A in Figure 1-192, 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-192

BTS3203E
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
GERAN

UTRAN to GERAN for SRVCC
Counters

VCC.E2G.Exec inter-RAT
AttOut handover
executions from
E-UTRAN to
GERAN for
SRVCC
Description
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.

BTS3203E
Figure 1-193
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2G.Ex Multi-mode: None

ecAttOut GSM: None
UMTS: None
GERAN

BTS3203E

UTRAN to GERAN for SRVCC
Counters

VCC.E2G.Exec successful inter-
from E-
UTRAN to
GERAN for
SRVCC
Description
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-194

BTS3203E
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2G.Ex Multi-mode: None

ecSuccOut GSM: None
UMTS: None
GERAN

to TD-SCDMA Network for SRVCC
Counters

VCC.E2T.Prep inter-RAT
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.
Measurement Points
As shown at point A in Figure 1-195, 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.

BTS3203E
Figure 1-195
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2T.Pre Multi-mode: None

pAttOut GSM: None
UMTS: None

BTS3203E

UTRAN to TD-SCDMA Network for SRVCC
Counters

VCC.E2T.Exec inter-RAT
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-
Measurement Points
As shown at point B in Figure 1-196, 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-196

BTS3203E
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-
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-
Measurement Points
As shown at point C in Figure 1-197, 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.

BTS3203E
Figure 1-197
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2T.Ex Multi-mode: None

ecSuccOut GSM: None
UMTS: None

BTS3203E
1.23.31 Number of LCS-triggered CS Fallback Indicators Received

by the eNodeB
Counters
1526728409 L.CSFB.LCS.Pr Number of BTS3203E LTE L

epAtt LCS-triggered
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.
Measurement Points
As shown at point A in Figure 1-198, 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-199, 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-198

BTS3203E
Figure 1-199
Formula
None
Unit
None
Related Features
L.CSFB.LCS.PrepAtt Multi-mode: None

GSM: None
UMTS: None
LOFD-001023 SRVCC to GERAN

BTS3203E
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 BTS3203E LTE L

epSucc responses sent
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.
Measurement Points
As shown at point C in Figure 1-200, 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-201, 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-200

BTS3203E
Figure 1-201
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 BTS3203E LTE L

ecAttOut CCO
executions from
E-UTRAN to
GERAN

BTS3203E
Description
The counter measures the number of CCO executions from E-UTRAN to GERAN in a cell.
Measurement Points
As shown at point B in Figure 1-202, 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-202
Formula
None
Unit
None

BTS3203E
Related Features
L.CCO.E2G.ExecAttOut Multi-mode: None

GSM: None
UMTS: None
between E-UTRAN and
GERAN
1.23.34 Number of Inter-RAT Handover Initiation Failures

Because the Adjacent Cell is not the NRT of the Source Cell
Counters

W.NoNRT inter-RAT
initiation
failures from E-
UTRAN to
WCDMA
network
because the
adjacent cell is
not on the NRT
of the source
cell

.NoNRT inter-RAT
initiation
failures from E-
UTRAN to TD-
SCDMA
network
because the
adjacent cell is
not on the NRT
of the source
cell

BTS3203E


G.NoNRT inter-RAT
initiation
failures from E-
UTRAN to
GERAN
because the
adjacent cell is
not on the NRT
of the source
cell

xRTT.NoNRT inter-RAT
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
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.
Measurement Points
As shown at point A in Figure 1-203 or Figure 1-204, the corresponding counter is
incremented by 1 each time the source cell receives the first measurement report from the UE

BTS3203E
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-203 shows the measurement procedure on a GERAN. Figure 1-204 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-203

BTS3203E
Figure 1-204
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.NoNRT Multi-mode: None

GSM: None
UMTS: None
UTRAN
LOFD-001022
Inter-RAT ANR
SRVCC to UTRAN
L.IRATHO.E2T.NoNRT Multi-mode: None

GSM: None
UMTS: None
UTRAN
LOFD-001022
Inter-RAT ANR
SRVCC to UTRAN

BTS3203E
L.IRATHO.E2G.NoNRT Multi-mode: None

GSM: None
UMTS: None
GERAN
LOFD-001023
Inter-RAT ANR
SRVCC to GERAN
L.IRATHO.E21xRTT.NoNR Multi-mode: None

T GSM: None
UMTS: None
LTE: LOFD-001090 Enhanced CS Fallback to
CDMA2000 1xRTT
L.IRATHO.E2HRPD.NoNR Multi-mode: None

T GSM: None
UMTS: None
between E-UTRAN and
CDMA2000
1.23.35 Number of CSFB Preparation Failures Because of Process

Conflict
Counters
1526728513 L.CSFB.PrepFa Number of BTS3203E LTE L

il.Conflict CSFB
preparation
failures because
of process
conflict
Description
The counter measures the number of CSFB preparation failures because of process conflict.
Measurement Points
As shown at point C in Figure 1-205, the L.CSFB.PrepFail.Conflict counter is incremented
by 1 each time the eNodeB sends a UE CONTEXT MODIFICATION FAILURE message to

BTS3203E
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-205
Formula
None
Unit
None
Related Features
L.CSFB.PrepFail.Conflict Multi-mode: None

GSM: None
UMTS: None
1xRTT

BTS3203E
1.23.36 Number of Handover Preparation Attempts from E-

UTRAN to WCDMA Network Triggered Because of High Load
Counters

W.Load.PrepAtt inter-RAT
Out handover
preparation
attempts from
E-UTRAN to
WCDMA
network
triggered
because of high
load

.Load.PrepAttO inter-RAT
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.
Measurement Points
As shown at point A in Figure 1-206, the L.IRATHO.E2W.Load.PrepAttOut counter is
incremented by 1 each time the eNodeB decides to perform a blind handover from E-UTRAN
to WCDMA network triggered because of high load 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 high load.

BTS3203E
Figure 1-206
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.Load.Prep Multi-mode: None

AttOut GSM: None
UMTS: None
LOFD-001022 UTRAN
SRVCC to UTRAN

BTS3203E
1.23.37 Number of Inter-RAT Handover Execution Attempts

Triggered Because of High Load
Counters

W.Load.ExecAt inter-RAT
tOut handover
execution
attempts from
E-UTRAN to
WCDMA
network
triggered
because of high
load

.Load.ExecAtt inter-RAT
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
Measurement Points
As shown at point B in Figure 1-207, the L.IRATHO.E2W.Load.ExecAttOut counter is
incremented by 1 each time the eNodeB performs an inter-RAT handover from E-UTRAN to
WCDMA network triggered because of high load balancing and sends a Mobility From
EUTRA Command message to the UE.

BTS3203E
Figure 1-207
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.Load.Exec Multi-mode: None

AttOut GSM: None
UMTS: None
LOFD-001022 UTRAN
SRVCC to UTRAN

BTS3203E
1.23.38 Number of Successful Inter-RAT Handover Executions

Triggered Because of High Load
Counters

W.Load.ExecSu successful inter-
ccOut RAT handover
executions from
E-UTRAN to
WCDMA
network
triggered
because of high
load

.Load.ExecSucc successful inter-
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
Measurement Points
As shown at point C in Figure 1-208, the L.IRATHO.E2W.Load.ExecSuccOut counter is
incremented by 1 each time the eNodeB performs an inter-RAT handover from E-UTRAN to
WCDMA network triggered because of high load balancing and the eNodeB receives a UE
CONTEXT RELEASE COMMAND message from the MME after the UE is handed over to a
WCDMA network.

BTS3203E
Figure 1-208
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.Load.Exec Multi-mode: None

SuccOut GSM: None
UMTS: None
LOFD-001022 UTRAN
SRVCC to UTRAN

BTS3203E
1.23.39 Number of Redirections from E-UTRAN to WCDMA

Network Triggered Because of High Load
Counters

on.E2W.Load redirections
from E-
UTRAN to
WCDMA
network
triggered
because of high
load

on.E2T.Load redirections
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
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 high 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.
Figure 1-209

BTS3203E
Formula
None
Unit
None
Related Features
L.RRCRedirection.E2W.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
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.

BTS3203E
Measurement Points
As shown at point A in Figure 1-210, 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-210
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.RegainHP Multi-mode: None

LMN.PrepAttOut GSM: None
UMTS: None
SPID

BTS3203E

UTRAN to WCDMA Network Triggered for UEs to Go back to
the HPLMN
Counters

W.RegainHPL inter-RAT
MN.ExecAttOu handover
t executions from
E-UTRAN to
WCDMA
network
triggered for
UEs to go back
to the HPLMN
Description
Measurement Points
As shown at point B in Figure 1-211, 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.

BTS3203E
Figure 1-211
Formula
None
Unit
None
Related Features

LMN.ExecAttOut GSM: None
UMTS: None
SPID

BTS3203E
1.23.42 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-
MN.ExecSuccO RAT handovers
ut from E-
UTRAN to
WCDMA
network
triggered for
UEs to go back
to the HPLMN
Description
Measurement Points
As shown at point C in Figure 1-212, 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.

BTS3203E
Figure 1-212
Formula
None
Unit
None
Related Features

LMN.ExecSuccOut GSM: None
UMTS: None
SPID

BTS3203E

UTRAN to WCDMA Network Triggered for UEs That Do not
Transmit or Receive Data
Counters

W.NoData.Exec inter-RAT
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.
Measurement Points
As shown at point B in Figure 1-213, 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.

BTS3203E
Figure 1-213
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
LOFD-001105
Dynamic DRX

BTS3203E

UTRAN to WCDMA Network Triggered for UEs That Do not
Transmit or Receive Data
Counters

W.NoData.Exec successful inter-
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.
Measurement Points
As shown at point C in Figure 1-214, 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.

BTS3203E
Figure 1-214
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
LOFD-001105
Dynamic DRX

BTS3203E
1.23.45 Number of LCS-based Inter-RAT Handover Executions for

SRVCC
Counters

VCC.LCS.E2W CSFB-based
.PrepAttOut handover
attempts from
E-UTRAN to
WCDMA
network for
SRVCC

VCC.LCS.E2W CSFB-based
.ExecAttOut handover
executions from
E-UTRAN to
WCDMA
network for
SRVCC

VCC.LCS.E2W successful
.ExecSuccOut CSFB-based
handovers from
E-UTRAN to
WCDMA
network for
SRVCC

VCC.LCS.E2G. CSFB-based
PrepAttOut handover
attempts from
E-UTRAN to
GERAN for
SRVCC

VCC.LCS.E2G. CSFB-based
ExecAttOut handover
executions from
E-UTRAN to
GERAN for
SRVCC

BTS3203E


VCC.LCS.E2G. successful
ExecSuccOut CSFB-based
handovers from
E-UTRAN to
GERAN for
SRVCC

VCC.LCS.E2T. CSFB-based
PrepAttOut handover
attempts from
E-UTRAN to
TD-SCDMA
network for
SRVCC

VCC.LCS.E2T. CSFB-based
ExecAttOut handover
executions from
E-UTRAN to
TD-SCDMA
network for
SRVCC

VCC.LCS.E2T. successful
ExecSuccOut CSFB-based
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.
Measurement Points
As shown at point A in Figure 1-215, 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-215, the L.IRATHO.SRVCC.LCS.E2W.ExecAttOut counter
is incremented by 1 each time the eNodeB decides to perform an SRVCC procedure from E-

BTS3203E
UTRAN to WCDMA network triggered by CSFB and the eNodeB sends a Mobility From
As shown at point C in Figure 1-215, 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-215, the L.IRATHO.SRVCC.LCS.E2G.PrepAttOut counter
to GERAN.
As shown at point B in Figure 1-215, 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-215, 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-215, the L.IRATHO.SRVCC.LCS.E2T.PrepAttOut counter
to TD-SCDMA network.
As shown at point B in Figure 1-215, 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-215, 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.

BTS3203E
Figure 1-215
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

BTS3203E

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

BTS3203E
1.23.46 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
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
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
mRsp abnormal
causes received
by the eNodeB
from the MME
during inter-
RAT handover
executions from
E-UTRAN to
WCDMA
network

BTS3203E


G.MMEAbnor responses for
mRsp abnormal
causes received
by the eNodeB
from the MME
during inter-
RAT handover
executions from
E-UTRAN to
GERAN

.MMEAbnorm responses for
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.
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.

BTS3203E
Figure 1-216
Figure 1-217

BTS3203E
Formula
None
Unit
None
Related Features
L.IRATHO.E21xRTT.MME Multi-mode: None

AbnormRsp GSM: None
UMTS: None
CDMA2000 1xRTT
L.IRATHO.E2HRPD.MME Multi-mode: None

AbnormRsp GSM: None
UMTS: None
between E-UTRAN and
CDMA2000
L.IRATHO.E2W.MMEAbn Multi-mode: None

ormRsp GSM: None
UMTS: None
UTRAN
SRVCC to UTRAN
L.IRATHO.E2G.MMEAbno Multi-mode: None

rmRsp GSM: None
UMTS: None
GERAN
SRVCC to GERAN
L.IRATHO.E2T.MMEAbno Multi-mode: None

rmRsp GSM: None
UMTS: None
UTRAN
SRVCC to UTRAN

BTS3203E

the eNodeB from the MME During Inter-RAT Handover
Executions from E-UTRAN to Another System for SRVCC
Counters

VCC.E2W.MM responses for
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
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
EAbnormRsp abnormal
causes received
by the eNodeB
from the MME
during inter-
RAT handover
executions from
E-UTRAN to
TD-SCDMA
network for
SRVCC

BTS3203E
Description
from the MME during inter-RAT handover executions from E-UTRAN to another system for
SRVCC.
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-218
Formula
None
Unit
None

BTS3203E
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 CSFB-based Inter-RAT
Handover Executions from E-UTRAN to Another System
Counters

C.CSFB.MME responses for
AbnormRsp abnormal
causes received
by the eNodeB
from the MME
during CSFB-
based inter-
RAT handover
executions from
E-UTRAN to
CDMA2000
network

BTS3203E


W.CSFB.MME responses for
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
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
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.

BTS3203E
Measurement Points
As shown at point C in Figure 1-219, 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-220, 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
"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-219

BTS3203E
Figure 1-220
Formula
None
Unit
None
Related Features
L.IRATHO.E2C.CSFB.MM Multi-mode: None

EAbnormRsp GSM: None
UMTS: None
CDMA2000 1xRTT
L.IRATHO.E2W.CSFB.MM Multi-mode: None

UMTS: None
UTRAN

BTS3203E
L.IRATHO.E2G.CSFB.MM Multi-mode: None

UMTS: None
GERAN
L.IRATHO.E2T.CSFB.MM Multi-mode: None

UMTS: None

to CDMA2000 HRPD Network
Counters

HRPD.PrepAtt inter-RAT
Out handover
attempts from
E-UTRAN to
CDMA2000
HRPD network
Description
CDMA2000 HRPD network in a cell.
Measurement Points
As shown at point A in Figure 1-221, 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.

BTS3203E
Figure 1-221
Formula
None
Unit
None
Related Features
L.IRATHO.E2HRPD.PrepA Multi-mode: None

ttOut GSM: None
UMTS: None
between E-UTRAN and
CDMA2000

BTS3203E

UTRAN to CDMA2000 HRPD Network
Counters

HRPD.ExecAtt inter-RAT
Out handover
executions from
E-UTRAN to
CDMA2000
HRPD network
Description
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-222

BTS3203E
Formula
None
Unit
None
Related Features
L.IRATHO.E2HRPD.ExecA Multi-mode: None

ttOut GSM: None
UMTS: None
between E-UTRAN and
CDMA2000

UTRAN to CDMA2000 HRPD Network
Counters

HRPD.ExecSuc successful inter-
cOut RAT handovers
from E-
UTRAN to
CDMA2000
HRPD network
Description
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.

BTS3203E
Figure 1-223
Formula
None
Unit
None
Related Features
L.IRATHO.E2HRPD.ExecS Multi-mode: None

uccOut GSM: None
UMTS: None
between E-UTRAN and
CDMA2000

BTS3203E
1.23.52 Handover Time from E-UTRAN to Another RAT

Counters
1526729432 L.IRATHO.E2 Average BTS3203E LTE L

W.TimeAvg handover
duration from
E-UTRAN to
WCDMA
network

G.TimeAvg handover
duration from
E-UTRAN to
GERAN
1526729434 L.IRATHO.E2T Average BTS3203E LTE L

.TimeAvg handover
duration from
E-UTRAN to
TD-SCDMA
network

G.ExecSuccOut EUTRAN-to-
TimeAvg GERAN
handover
execution
duration
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-224, 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.

BTS3203E
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
As shown in Figure 1-224, the duration of a handover execution equals the interval between
the time the source eNodeB receives a HANDOVER COMMAND message from the MME
and the time the source eNodeB receives a UE CONTEXT RELEASE COMMAND message
from the MME. The duration is taken as a sample. At the end of a measurement period, the
average of these sampling results of handovers to GERAN cells is taken as the
L.IRATHO.E2G.ExecSuccOutTimeAvg counter value.
Figure 1-224
Formula
None

BTS3203E
Unit
ms
Related Features
L.IRATHO.E2W.TimeAvg Multi-mode: None

GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
L.IRATHO.E2G.TimeAvg Multi-mode: None

GSM: None
UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN
L.IRATHO.E2T.TimeAvg Multi-mode: None

GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
L.IRATHO.E2G.ExecSuccO Multi-mode: None

utTimeAvg GSM: None
UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN

BTS3203E
1.23.53 Number of Coverage-based Inter-RAT Handover Attempts

from E-UTRAN to Another System
Counters

W.Coverage.Pre coverage-based
pAttOut handover
preparation
attempts from
E-UTRAN to
WCDMA
network

G.Coverage.Pre coverage-based
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.
Measurement Points
As shown at point A in Figure 1-225, 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-225, 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.
Number of Coverage-based Inter-RAT Handover Attempts from E-UTRAN to Another
System The counters measure the number of coverage-based inter-RAT handover preparation
attempts from E-UTRAN to another system in a cell.

BTS3203E
Figure 1-225
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.Coverage. Multi-mode: None

PrepAttOut GSM: None
UMTS: None
UTRAN
SRVCC to UTRAN

BTS3203E
L.IRATHO.E2G.Coverage.P Multi-mode: None

repAttOut GSM: None
UMTS: None
GERAN
SRVCC to GERAN
1.23.54 Number of Coverage-based Inter-RAT Handover

Counters

W.Coverage.Ex coverage-based
ecAttOut handover
execution
attempts from
E-UTRAN to
WCDMA
network

G.Coverage.Ex coverage-based
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.
Measurement Points
As shown at point B in Figure 1-226, 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.

BTS3203E
As shown at point B in Figure 1-226, 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-226
Formula
None
Unit
None
Related Features

ExecAttOut GSM: None
UMTS: None
UTRAN
SRVCC to UTRAN

BTS3203E
L.IRATHO.E2G.Coverage.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
GERAN
SRVCC to GERAN
1.23.55 Number of Successful Coverage-based Inter-RAT

Handovers from E-UTRAN to Another System
Counters

W.Coverage.Ex successful
ecSuccOut coverage-based
handover
executions from
E-UTRAN to
WCDMA
network

G.Coverage.Ex successful
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.
Measurement Points
As shown at point C in Figure 1-227, 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.

BTS3203E
As shown at point C in Figure 1-227, 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-227
Formula
None
Unit
None
Related Features

ExecSuccOut GSM: None
UMTS: None
UTRAN
SRVCC to UTRAN

BTS3203E
L.IRATHO.E2G.Coverage.E Multi-mode: None

UMTS: None
GERAN
SRVCC to GERAN
1.23.56 Number of Coverage-based Inter-RAT Redirections from

E-UTRAN to Another System
Counters

on.E2W.Covera coverage-based
ge redirections
from E-
UTRAN to
WCDMA
network

on.E2G.Covera coverage-based
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.
Measurement Points
As shown at point A in Figure 1-228, 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.

BTS3203E
If the target system is GERAN, the L.RRCRedirection.E2G.Coverage counter is incremented

by 1.
Figure 1-228
Formula
None
Unit
None
Related Features
L.RRCRedirection.E2W.Co Multi-mode: None

verage GSM: None
UMTS: None
between E-UTRAN and
UTRAN
L.RRCRedirection.E2G.Cov Multi-mode: None

erage GSM: None
UMTS: None
between E-UTRAN and
GERAN

BTS3203E
1.23.57 Number of SPID-based Inter-RAT Redirections Back to

the HPLMN
Counters

on.E2W.Regain SPID-based
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.
Measurement Points
As shown at point A in Figure 1-229, 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-229
Formula
None
Unit
None

BTS3203E
Related Features
L.RRCRedirection.E2W.Re Multi-mode: None

gainHPLMN GSM: None
UMTS: None
SPID
1.23.58 Number of Successful Service-based Inter-RAT Outgoing

Handover Attempts from E-UTRAN to Another System
Counters

W.Service.Prep service-based
AttOut handover
preparation
attempts from
E-UTRAN to
WCDMA
network

G.Service.Prep service-based
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.
Measurement Points
As shown at point A in Figure 1-230, 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-230, 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.

BTS3203E
Figure 1-230
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 handover to UTRAN
SRVCC to UTRAN
L.IRATHO.E2G.Service.Pre Multi-mode: None

pAttOut GSM: None
UMTS: None
LOFD-001023 handover to GERAN
SRVCC to GERAN

BTS3203E
1.23.59 Number of Service-based Inter-RAT Outgoing Handover

Counters

W.Service.Exec service-based
AttOut handover
execution
attempts from
E-UTRAN to
WCDMA
network

G.Service.Exec service-based
AttOut handover
execution
attempts from
E-UTRAN to
GERAN
Description
The counters measure the number of service-based handover execution attempts from E-
Measurement Points
As shown at point B in Figure 1-231, 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-231, 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

BTS3203E
Figure 1-231
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.Service.Ex Multi-mode: None

ecAttOut GSM: None
UMTS: None
SRVCC to UTRAN
L.IRATHO.E2G.Service.Ex Multi-mode: None

ecAttOut GSM: None
UMTS: None
SRVCC to GERAN

BTS3203E
1.23.60 Number of Successful Service-based Inter-RAT Outgoing

Counters

W.Service.Exec successful
SuccOut service-based
handover
executions from
E-UTRAN to
WCDMA
network

G.Service.Exec successful
handover
executions from
E-UTRAN to
GERAN
Description
The counters measure the number of successful service-based handover executions from E-
Measurement Points
As shown at point C in Figure 1-232, 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-232, 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.

BTS3203E
Figure 1-232
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.Service.Ex Multi-mode: None

ecSuccOut GSM: None
UMTS: None
SRVCC to UTRAN
L.IRATHO.E2G.Service.Ex Multi-mode: None

ecSuccOut GSM: None
UMTS: None
SRVCC to GERAN

BTS3203E
1.23.61 Number of Service-based Inter-RAT Redirections from E-

Counters

on.E2W.Service service-based
redirections
from E-
UTRAN to
WCDMA
network

on.E2G.Service service-based
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.
Measurement Points
As shown at point A in Figure 1-233, during a service-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.Service counter is

incremented by 1.
If the target system is GERAN, the L.RRCRedirection.E2G.Service counter is incremented by

1.
Figure 1-233

BTS3203E
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.62 Number of UL-Quality-based Outgoing Handover

Attempts from E-UTRAN to Another System
Counters
1526730026 L.IRATHO.E2 Number of UL- BTS3203E LTE L

W.ULquality.Pr quality-based
epAttOut handover
preparation
attempts from
E-UTRAN to
WCDMA
network

G.ULquality.Pr quality-based
epAttOut handover
preparation
attempts from
E-UTRAN to
GERAN

BTS3203E
Description
The counters measure the number of UL-quality-based handover preparation attempts from E-
Measurement Points
As shown at point A in Figure 1-234, the L.IRATHO.E2W.ULquality.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 uplink signal quality.
As shown at point A in Figure 1-234, the L.IRATHO.E2G.ULquality.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 uplink signal quality.
Figure 1-234
Formula
None
Unit
None

BTS3203E
Related Features
L.IRATHO.E2W.ULquality. Multi-mode: None

UMTS: None
UTRAN
SRVCC to UTRAN
L.IRATHO.E2G.ULquality. Multi-mode: None

UMTS: None
GERAN
SRVCC to GERAN
1.23.63 Number of UL-Quality-based Outgoing Handover

Counters

W.ULquality.Ex quality-based
ecAttOut handover
execution
attempts from
E-UTRAN to
WCDMA
network

G.ULquality.Ex quality-based
ecAttOut handover
execution
attempts from
E-UTRAN to
GERAN

BTS3203E
Description
The counters measure the number of UL-quality-based handover execution attempts from E-
Measurement Points
As shown at point B in Figure 1-235, 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-235, during a UL-quality-based handover from the E-
UTRAN to a GERAN, the L.IRATHO.E2G.ULquality.ExecAttOut counter is incremented by
1 each time the eNodeB sends a Mobility From EUTRA Command message to the UE.
Figure 1-235
Formula
None
Unit
None

BTS3203E
Related Features

UMTS: None
UTRAN
SRVCC to UTRAN

UMTS: None
GERAN
SRVCC to GERAN
1.23.64 Number of Successful UL-Quality-based Outgoing

Counters

W.ULquality.Ex successful UL-
ecSuccOut quality-based
handover
executions from
E-UTRAN to
WCDMA
network

G.ULquality.Ex successful UL-
handover
executions from
E-UTRAN to
GERAN

BTS3203E
Description
The counters measure the number of successful UL-quality-based handover executions from
E-UTRAN to another system in a cell.
Measurement Points
As shown at point C in Figure 1-236, 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-236, 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-236
Formula
None
Unit
None

BTS3203E
Related Features

UMTS: None
UTRAN
SRVCC to UTRAN

UMTS: None
GERAN
SRVCC to GERAN
1.23.65 Number of UL-Quality-based Inter-RAT Redirections

from E-UTRAN to Another System
Counters
1526730032 L.RRCRedirecti Number of UL- BTS3203E LTE L

on.E2W.Ulquali quality-based
ty redirections
from E-
UTRAN to
WCDMA
network

on.E2G.Ulquali quality-based
ty redirections
from E-
UTRAN to
GERAN
Description
The counters measure the total number of UL-quality-based redirections from E-UTRAN to
another system in a cell.

BTS3203E
Measurement Points
As shown at point A in Figure 1-237, 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-237
Formula
None
Unit
None
Related Features
L.RRCRedirection.E2W.Ulq Multi-mode: None

uality GSM: None
UMTS: None
between E-UTRAN and
UTRAN
L.RRCRedirection.E2G.Ulq Multi-mode: None

uality GSM: None
UMTS: None
between E-UTRAN and
GERAN

BTS3203E
1.23.66 Number of Inter-RAT CSFB-based Handover Failures for

Different Causes
Counters

W.CSFB.Prep.F CSFB-based
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

BTS3203E


.CSFB.Prep.Fai CSFB-based
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-

BTS3203E
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.
Measurement Points
As shown at point A in Figure 1-238, 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-238

BTS3203E
Figure 1-239
Figure 1-240
Formula
None
Unit
None

BTS3203E
Related Features

.FailOut.MME GSM: None
UMTS: None
UTRAN

.FailOut.PrepFailure GSM: None
UMTS: None
UTRAN

.FailOut.NoReply GSM: None
UMTS: None
UTRAN
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

BTS3203E
1.23.67 Number of Inter-RAT SRVCC-based Handover Failures

for Different Causes
Counters

W.SRVCC.Prep SRVCC-based
.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

BTS3203E


.SRVCC.Prep.F SRVCC-based
ailOut.MME outgoing
handover
preparation
failures from E-
UTRAN to TD-
SCDMA
network
because of the
MME side
causes

ailOut.PrepFail outgoing
ure handover
preparation
failures from E-
UTRAN to TD-
SCDMA
network
because of the
response of
handover
preparation
failure from
TD-SCDMA
network

ailOut.NoReply outgoing
handover
preparation
failures from E-
UTRAN to TD-
SCDMA
network
because of no
response from
TD-SCDMA
network

BTS3203E


G.SRVCC.Prep. SRVCC-based
FailOut.MME outgoing
handover
preparation
failures from E-
UTRAN to
GERAN
because of the
MME side
causes

FailOut.PrepFai outgoing
lure handover
preparation
failures from E-
UTRAN to
GERAN
because of the
response of
handover
preparation
failure from
GERAN

FailOut.NoRepl outgoing
y handover
preparation
failures from E-
UTRAN to
GERAN
because of no
response from
GERAN

VCC.FailOut.H SRVCC-based
OCancel.ReEst Outgoing
Handover
Cancellations
Due to RRC
Connection Re-
establishments

BTS3203E
Description
The counters measure the number of SRVCC-based handover failures based-on the failure
cause. SRVCC-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. SRVCC-based handover is a process during which UEs
are handed over from the E-UTRAN to other systems to ensure continuity of QCI-1 services
in inter-RAT networking scenarios.
Measurement Points
As shown at point A in Figure 1-241, in SRVCC 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
L.IRATHO.E2W.SRVCC.Prep.FailOut.NoReply counter is incremented by 1; if the target cell
is a TD-SCDMA cell, the L.IRATHO.E2T.SRVCC.Prep.FailOut.NoReply counter is
incremented by 1; if the target cell is a GERAN cell, the
L.IRATHO.E2G.SRVCC.Prep.FailOut.NoReply counter is incremented by 1.
cell, the corresponding counter is incremented by 1 each time the eNodeB receives a
HANDOVER PREPARATION FAILURE 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.SRVCC.Prep.FailOut.PrepFailure counter is incremented by 1; if the target
cell is a TD-SCDMA cell, the L.IRATHO.E2T.SRVCC.Prep.FailOut.PrepFailure counter is
incremented by 1; if the target cell is a GERAN cell, the
L.IRATHO.E2G.SRVCC.Prep.FailOut.PrepFailure counter is incremented by 1.
cell, 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.SRVCC.Prep.FailOut.MME counter is incremented by 1; if the target cell is
a TD-SCDMA cell, the L.IRATHO.E2T.SRVCC.Prep.FailOut.MME counter is incremented
by 1; if the target cell is a GERAN cell, the L.IRATHO.E2G.SRVCC.Prep.FailOut.MME
As shown at point A in Figure 4, if the RRC connection of a UE is re-established in an
SRVCC scenario, the eNodeB cancels the handover and sends a HANDOVER CANCEL
message. The L.IRATHO.SRVCC.FailOut.HOCancel.ReEst counter is incremented by 1.

BTS3203E
Figure 1-241
Figure 1-242

BTS3203E
Figure 1-243
Figure 1-244
Formula
None
Unit
None

BTS3203E
Related Features
L.IRATHO.E2W.SRVCC.Pr Multi-mode: None

ep.FailOut.MME GSM: None
UMTS: None
UTRAN

ep.FailOut.PrepFailure GSM: None
UMTS: None
UTRAN

ep.FailOut.NoReply GSM: None
UMTS: None
UTRAN
L.IRATHO.E2T.SRVCC.Pre Multi-mode: None

p.FailOut.MME GSM: None
UMTS: None

p.FailOut.PrepFailure GSM: None
UMTS: None

p.FailOut.NoReply GSM: None
UMTS: None
L.IRATHO.E2G.SRVCC.Pr Multi-mode: None

ep.FailOut.MME GSM: None
UMTS: None
GERAN

BTS3203E

ep.FailOut.PrepFailure GSM: None
UMTS: None
GERAN

ep.FailOut.NoReply GSM: None
UMTS: None
GERAN
L.IRATHO.SRVCC.FailOut. Multi-mode: None

HOCancel.ReEst GSM: None
UMTS: None
UTRAN
1.23.68 Number of Outgoing CS-Only SRVCC-based Handover

Attempts from E-UTRAN to WCDMA Network
Counters
1526730091 L.IRATHO.SR Number of CS- BTS3203E LTE L

VCC.CSonly.E only SRVCC-
2W.PrepAttOut based outgoing
handover
attempts from
E-UTRAN to
WCDMA
network
Description
The counter measures the number of CS-only SRVCC-based outgoing handover attempts
from E-UTRAN to WCDMA network.

BTS3203E
Measurement Points
As shown at point A in Figure 1-245, the L.IRATHO.SRVCC.CSonly.E2W.PrepAttOut
counter is incremented by 1 each time the eNodeB determines to perform a CS-only SRVCC-
based handover to a WCDMA network.
Figure 1-245
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.CSonly. Multi-mode: None

E2W.PrepAttOut GSM: None
UMTS: None

BTS3203E

Executions from E-UTRAN to WCDMA Network
Counters

2W.ExecAttOut based outgoing
handover
executions from
E-UTRAN to
WCDMA
network
Description
The counter measures the number of CS-only SRVCC-based outgoing handover executions
Measurement Points
As shown at point B in Figure 1-246, the L.IRATHO.SRVCC.CSonly.E2W.ExecAttOut
counter is incremented by 1 each time the eNodeB sends a Mobility From EUTRA Command
message to the UE during a CS-only SRVCC-based handover from the E-UTRAN to a
WCDMA network.
Figure 1-246

BTS3203E
Formula
None
Unit
None
Related Features

E2W.ExecAttOut GSM: None
UMTS: None
1.23.70 Number of Successful Outgoing CS-Only SRVCC-based

Handovers from E-UTRAN to WCDMA Network
Counters

VCC.CSonly.E successful CS-
2W.ExecSuccO only SRVCC-
ut based outgoing
handovers from
E-UTRAN to
WCDMA
network
Description
The counter measures the number of successful CS-only SRVCC-based outgoing handovers
Measurement Points
As shown at point C in Figure 1-247, during a CS-only SRVCC-based handover from the E-
UTRAN to a WCDMA network, the L.IRATHO.SRVCC.CSonly.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.

BTS3203E
Figure 1-247
Formula
None
Unit
None
Related Features

E2W.ExecSuccOut GSM: None
UMTS: None

BTS3203E

Attempts from E-UTRAN to TD-SCDMA Network
Counters

2T.PrepAttOut based outgoing
handover
attempts from
E-UTRAN to
TD-SCDMA
network
Description
from E-UTRAN to TD-SCDMA network.
Measurement Points
As shown at point A in Figure 1-248, the L.IRATHO.SRVCC.CSonly.E2T.PrepAttOut
counter is incremented by 1 each time the eNodeB determines to start a CS-only SRVCC-
based handover to a TD-SCDMA network.
Figure 1-248

BTS3203E
Formula
None
Unit
None
Related Features

E2T.PrepAttOut GSM: None
UMTS: None

Executions from E-UTRAN to TD-SCDMA Network
Counters

2T.ExecAttOut based outgoing
handover
executions from
E-UTRAN to
TD-SCDMA
network
Description
Measurement Points
As shown at point B in Figure 1-249, the L.IRATHO.SRVCC.CSonly.E2T.ExecAttOut
message to the UE during a CS-only SRVCC procedure from E-UTRAN to a TD-SCDMA
network.

BTS3203E
Figure 1-249
Formula
None
Unit
None
Related Features

E2T.ExecAttOut GSM: None
UMTS: None

BTS3203E

Handovers from E-UTRAN to TD-SCDMA Network
Counters

2T.ExecSuccOu only SRVCC-
t based outgoing
handovers from
E-UTRAN to
TD-SCDMA
network
Description
Measurement Points
As shown at point C in Figure 1-250, the L.IRATHO.SRVCC.CSonly.E2T.ExecSuccOut
COMMAND message from the MME after the UE is handed over from E-UTRAN to a TD-
SCDMA network through CS-only SRVCC.
Figure 1-250

BTS3203E
Formula
None
Unit
None
Related Features

E2T.ExecSuccOut GSM: None
UMTS: None

Attempts from E-UTRAN to GERAN
Counters

2G.PrepAttOut based outgoing
handover
attempts from
E-UTRAN to
GERAN
Description
from E-UTRAN to GERAN.
Measurement Points
As shown at point A in Figure 1-251, the L.IRATHO.SRVCC.CSonly.E2G.PrepAttOut
counter is incremented by 1 each time the eNodeB determines to start a CS-only SRVCC-
based handover to GERAN.

BTS3203E
Figure 1-251
Formula
None
Unit
None
Related Features

E2G.PrepAttOut GSM: None
UMTS: None

BTS3203E

Executions from E-UTRAN to GERAN
Counters

2G.ExecAttOut based outgoing
handover
executions from
E-UTRAN to
GERAN
Description
Measurement Points
As shown at point B in Figure 1-252, the L.IRATHO.SRVCC.CSonly.E2G.ExecAttOut
message to the UE during a CS-only SRVCC procedure from E-UTRAN to GERAN.
Figure 1-252

BTS3203E
Formula
None
Unit
None
Related Features

E2G.ExecAttOut GSM: None
UMTS: None

Handovers from E-UTRAN to GERAN
Counters

2G.ExecSuccO only SRVCC-
ut based outgoing
handovers from
E-UTRAN to
GERAN
Description
Measurement Points
As shown at point C in Figure 1-253, the L.IRATHO.SRVCC.CSonly.E2G.ExecSuccOut
COMMAND message from the MME after the UE is handed over from E-UTRAN to
GERAN through CS-only SRVCC.

BTS3203E
Figure 1-253
Formula
None
Unit
None
Related Features

E2G.ExecSuccOut GSM: None
UMTS: None

BTS3203E
1.23.77 Number of SRVCC-based Outgoing Handover Attempts

from E-UTRAN to WCDMA Network for Ultra-Flash CSFB
Counters
1526730146 L.IRATHO.CS Number of BTS3203E LTE L

FB.SRVCC.E2 SRVCC-based
W.PrepAttOut outgoing
handover
attempts from
E-UTRAN to
WCDMA
network for
ultra-flash
CSFB
Description
The counter measures the number of outgoing handover attempts from E-UTRAN to
WCDMA network for ultra-flash CSFB in a cell.
Measurement Points
As shown at point A in Figure 1-254, the L.IRATHO.CSFB.SRVCC.E2W.PrepAttOut
counter is incremented by 1 each time the eNodeB decides to perform a handover from the E-
UTRAN to a WCDMA network for ultra-flash CSFB after receiving a measurement report
from a UE.

BTS3203E
Figure 1-254
Formula
None
Unit
None
Related Features
L.IRATHO.CSFB.SRVCC.E Multi-mode: None

2W.PrepAttOut GSM: None
UMTS: None
LTE: LOFD-070202 Ultra-Flash CSFB to
UTRAN

BTS3203E
1.23.78 Number of SRVCC-based Outgoing Handover Executions

Counters

W.ExecAttOut outgoing
handover
executions from
E-UTRAN to
WCDMA
network for
ultra-flash
CSFB
Description
The counter measures the number of outgoing handover executions from E-UTRAN to
Measurement Points
As shown at point B in Figure 1-255, during a handover from the E-UTRAN to a WCDMA
network for ultra-flash CSFB, the L.IRATHO.CSFB.SRVCC.E2W.ExecAttOut counter is
to the UE.

BTS3203E
Figure 1-255
Formula
None
Unit
None
Related Features

2W.ExecAttOut GSM: None
UMTS: None
UTRAN

BTS3203E
1.23.79 Number of Successful SRVCC-based Outgoing Handovers

Counters

FB.SRVCC.E2 successful
W.ExecSuccOu SRVCC-based
t outgoing
handovers from
E-UTRAN to
WCDMA
network for
ultra-flash
CSFB
Description
The counter measures the number of successful outgoing handovers from E-UTRAN to
Measurement Points
As shown at point C in Figure 1-256, during a handover from the E-UTRAN to a WCDMA
network for ultra-flash CSFB, the L.IRATHO.CSFB.SRVCC.E2W.ExecSuccOut counter is
message from the MME.

BTS3203E
Figure 1-256
Formula
None
Unit
None
Related Features

2W.ExecSuccOut GSM: None
UMTS: None
UTRAN

BTS3203E
1.23.80 Number of Responses with Abnormal Causes Received by

the eNodeB from the MME During Inter-RAT Blind Handover
Counters

dHO.E2W.MM responses with
EAbnormRsp abnormal
causes received
by the eNodeB
from the MME
during inter-
RAT blind
handover
executions from
E-UTRAN to
WCDMA
network

dHO.E2G.MM responses with
EAbnormRsp abnormal
causes received
by the eNodeB
from the MME
during inter-
RAT blind
handover
executions from
E-UTRAN to
GERAN
Description
The counter measures the number of responses with abnormal causes received by the eNodeB
from the MME during outgoing blind handover executions from E-UTRAN to Another
System.
Measurement Points
As shown at point C in Figure 1-257, during an inter-RAT outgoing blind handover, the
corresponding counter is incremented by 1 each time the source eNodeB receives a UE
CONTEXT RELEASE COMMAND message from the MME and the release cause is not
"Successful Handover" or "Normal Release".
If the target system is WCDMA network, the L.IRATHO.BlindHO.E2W.MMEAbnormRsp

BTS3203E
If the target system is GERAN, the L.IRATHO.BlindHO.E2G.MMEAbnormRsp counter is

incremented by 1.
Figure 1-257
Formula
None
Unit
None
Related Features
L.IRATHO.BlindHO.E2W. Multi-mode: None

MMEAbnormRsp GSM: None
UMTS: None
between E-UTRAN and
UTRAN

BTS3203E
L.IRATHO.BlindHO.E2G. Multi-mode: None

MMEAbnormRsp GSM: None
UMTS: None
between E-UTRAN and
GERAN
1.23.81 Number of Ultra-Flash CSFB Attempts

Counters

G.PrepAttOut outgoing
handover
attempts from
E-UTRAN to
GERAN for
ultra-flash
CSFB
Description
The counter measures the number of ultra-flash CSFB-triggered handover requests in a cell.
Measurement Points
As shown at point A in Figure 1-258, the L.IRATHO.CSFB.SRVCC.E2G.PrepAttOut counter
is incremented by 1 each time the eNodeB receives a Measurement Report message from the
UE and decides to perform ultra-flash CSFB from E-UTRAN to GERAN.

BTS3203E
Figure 1-258
Formula
None
Unit
None
Related Features

2G.PrepAttOut GSM: None
UMTS: None
GERAN

BTS3203E
1.23.82 Number of Ultra-Flash CSFB Executions

Counters

G.ExecAttOut outgoing
handover
executions from
E-UTRAN to
GERAN for
ultra-flash
CSFB
Description
The counter measures the number of ultra-flash CSFB-triggered handover commands in a
cell.
Measurement Points
As shown at point B in Figure 1-259, the L.IRATHO.CSFB.SRVCC.E2G.ExecAttOut
counter is incremented by 1 each time the eNodeB sends a Mobility from EUTRA Command
message to the UE during ultra-flash CSFB from E-UTRAN to GERAN.
Figure 1-259

BTS3203E
Formula
None
Unit
None
Related Features

2G.ExecAttOut GSM: None
UMTS: None
GERAN
1.23.83 Number of Successful Ultra-Flash CSFBs
Counters

FB.SRVCC.E2 successful
G.ExecSuccOut SRVCC-based
outgoing
handovers from
E-UTRAN to
GERAN for
ultra-flash
CSFB
Description
The counter measures the number of successful handovers triggered by ultra-flash CSFB in a
cell.
Measurement Points
As shown at point C in Figure 1-260, the L.IRATHO.CSFB.SRVCC.E2G.ExecSuccOut
COMMAND message from the MME during ultra-flash CSFB from E-UTRAN to GERAN.

BTS3203E
Figure 1-260
Formula
None
Unit
None
Related Features

2G.ExecSuccOut GSM: None
UMTS: None
GERAN

BTS3203E
1.23.84 Number of Abnormal Responses from the MME During

Ultra-Flash CSFB to GERAN
Counters

FB.SRVCC.E2 abnormal
G.MMEAbnor responses from
mRsp the MME
during outgoing
handovers from
E-UTRAN to
GERAN for
ultra-flash
CSFB
Description
The counter measures the number of abnormal responses from the MME during ultra-flash
CSFB in a cell.
Measurement Points
As shown at point C in Figure 1-261, the counter is incremented by 1 each time the eNodeB
receives a UE CONTEXT RELEASE COMMAND message from the MME during ultra-
flash CSFB from E-UTRAN to GERAN and the release cause value is not Successful
Handover or Normal Release.

BTS3203E
Figure 1-261
Formula
None
Unit
None
Related Features

2G.MMEAbnormRsp GSM: None
UMTS: None
GERAN

BTS3203E
1.24 Incoming Inter-RAT Handover Measurement

(HO.IRAT.In.Cell)
Overview
The HO.IRAT.In.Cell function subset measures the performance of inter-RAT handovers from
WCDMA network, GERAN, or TD-SCDMA network to E-UTRAN, as shown in Figure
1-262.
Figure 1-262
Counters
1526728866 L.IRATHO.G2E.Pr Number of inter- BTS3203E LTE:

epAttIn RAT handover V100R006C00
attempts from
GERAN to E-
UTRAN
1526728867 L.IRATHO.G2E.Pr Number of BTS3203E LTE:

epInSucc successful inter-RAT V100R006C00
handover
preparations from
GERAN to E-
UTRAN

BTS3203E

1526728868 L.IRATHO.G2E.E Number of BTS3203E LTE:

xecSuccIn successful inter-RAT V100R006C00
handovers from
GERAN to E-
UTRAN
1526728869 L.IRATHO.G2E.Pr Number of inter- BTS3203E LTE:

epInFail.TgtNotAll RAT handover V100R006C00
ow preparation failures
from GERAN in the
target cell due to
Handover Target not
allowed
1526728870 L.IRATHO.T2E.Pr Number of inter- BTS3203E LTE:

epAttIn RAT handover V100R006C00
attempts from TD-
SCDMA network to
E-UTRAN
1526728871 L.IRATHO.T2E.Pr Number of BTS3203E LTE:

epInSucc successful inter-RAT V100R006C00
handover
preparations from
TD-SCDMA
network to E-
UTRAN
1526728872 L.IRATHO.T2E.Ex Number of BTS3203E LTE:

ecSuccIn successful inter-RAT V100R006C00
handovers from TD-
SCDMA network to
E-UTRAN
1526728873 L.IRATHO.T2E.Pr Number of inter- BTS3203E LTE:

epInFail.TgtNotAll RAT handover V100R006C00
ow preparation failures
from TD-SCDMA
network in the target
cell due to Handover
Target not allowed
1526728874 L.IRATHO.W2E.P Number of inter- BTS3203E LTE:

repAttIn RAT handover V100R006C00
attempts from
WCDMA network
to E-UTRAN

BTS3203E

1526728875 L.IRATHO.W2E.P Number of BTS3203E LTE:

repInSucc successful inter-RAT V100R006C00
handover
preparations from
WCDMA network
to E-UTRAN
1526728876 L.IRATHO.W2E.E Number of BTS3203E LTE:

xecSuccIn successful inter-RAT V100R006C00
handovers from
WCDMA network
to E-UTRAN
1526728877 L.IRATHO.W2E.P Number of inter- BTS3203E LTE:

repInFail.TgtNotAl RAT handover V100R006C00
low preparation failures
from WCDMA
network in the target
cell due to Handover
Target not allowed
1526736741 L.IRATHO.G2E.Pr Number of GERAN- BTS3203E LTE:

epInFail.AdmitFail to-EUTRAN V100R011C10
handover
because of
admission failure

epInFail.FlowCtrl to-EUTRAN V100R011C10
handover
because of flow
control

epInFail.HOCancel to-EUTRAN V100R011C10
handover
because the target
cell receives
handover
cancelation
messages

BTS3203E

1526736744 L.IRATHO.G2E.Pr Number of times BTS3203E LTE:

epInFail.disc.Flow GERAN-to- V100R011C10
Ctrl EUTRAN handover
preparation
messages are
discarded because of
flow control

epInFail.AdmitFail TDSCDMA-to- V100R011C10
EUTRAN handover
because of
admission failure

epInFail.FlowCtrl TDSCDMA-to- V100R011C10
EUTRAN handover
because of flow
control

epInFail.HOCancel TDSCDMA-to- V100R011C10
EUTRAN handover
because the target
cell receives
handover
cancelation
messages
1526736748 L.IRATHO.T2E.Pr Number of times BTS3203E LTE:

epInFail.disc.Flow TDSCDMA-to- V100R011C10
messages are
flow control

repInFail.AdmitFai WCDMA-to- V100R011C10
l EUTRAN handover
because of
admission failure

BTS3203E


repInFail.FlowCtrl WCDMA-to- V100R011C10
EUTRAN handover
because of flow
control

repInFail.HOCanc WCDMA-to- V100R011C10
el EUTRAN handover
because the target
cell receives
handover
cancelation
messages
1526736752 L.IRATHO.W2E.P Number of times BTS3203E LTE:

repInFail.disc.Flow WCDMA-to- V100R011C10
messages are
flow control

epInFail to-EUTRAN V100R011C10
handover

epInFail TDSCDMA-to- V100R011C10
EUTRAN handover

repInFail WCDMA-to- V100R011C10
EUTRAN handover
L.IRATHO.G2E.PrepInFail L.IRATHO.G2E.PrepInFail.AdmitFail
L.IRATHO.G2E.PrepInFail.FlowCtrl
L.IRATHO.G2E.PrepInFail.HOCancel
L.IRATHO.G2E.PrepInFail.disc.FlowCtrl

BTS3203E
L.IRATHO.T2E.PrepInFail L.IRATHO.T2E.PrepInFail.AdmitFail
L.IRATHO.T2E.PrepInFail.FlowCtrl
L.IRATHO.T2E.PrepInFail.HOCancel
L.IRATHO.T2E.PrepInFail.disc.FlowCtrl
L.IRATHO.W2E.PrepInFail L.IRATHO.W2E.PrepInFail.AdmitFail
L.IRATHO.W2E.PrepInFail.FlowCtrl
L.IRATHO.W2E.PrepInFail.HOCancel
L.IRATHO.W2E.PrepInFail.disc.FlowCtrl
1.24.1 Number of Inter-RAT Handover Attempts from GERAN to

E-UTRAN
Counters
1526728866 L.IRATHO.G2 Number of BTS3203E LTE L

E.PrepAttIn inter-RAT
handover
attempts from
GERAN to E-
UTRAN
Description
The counter measures the number of inter-RAT handover attempts from GERAN to E-
UTRAN in a cell.
Measurement Points
As shown at point A in Figure 1-263, the L.IRATHO.G2E.PrepAttIn counter is incremented
by 1 each time the eNodeB receives a HANDOVER REQUEST message from the MME and
this message indicates an inter-RAT handover preparation from GERAN to E-UTRAN.

BTS3203E
Figure 1-263
Formula
None
Unit
None
Related Features
L.IRATHO.G2E.PrepAttIn Multi-mode: None

GSM: None
UMTS: None
GERAN
SRVCC to GERAN

BTS3203E
1.24.2 Number of Inter-RAT Handover Preparation from GERAN

to E-UTRAN
Counters

E.PrepInSucc successful inter-
RAT handover
preparations
from GERAN
to E-UTRAN
Description
The counter measures the number of successful inter-RAT handover preparations from
GERAN to E-UTRAN in a cell.
Measurement Points
As shown at point B in Figure 1-264, the L.IRATHO.G2E.PrepInSucc counter is incremented
by 1 each time the eNodeB sends a HANDOVER REQUEST ACKNOWLEDGE message to
the MME and this message indicates a successful inter-RAT handover preparation from
GERAN to E-UTRAN.
Figure 1-264

BTS3203E
Formula
None
Unit
None
Related Features
L.IRATHO.G2E.PrepInSucc Multi-mode: None

GSM: None
UMTS: None
GERAN
SRVCC to GERAN
1.24.3 Number of Successful Inter-RAT Handovers from GERAN

to E-UTRAN
Counters

E.ExecSuccIn successful inter-
RAT handovers
from GERAN
to E-UTRAN
Description
The counter measures the number of successful inter-RAT handovers from GERAN to E-
UTRAN in a cell.
Measurement Points
As shown at point C in Figure 1-265, the L.IRATHO.G2E.ExecSuccIn counter is
incremented by 1 each time the eNodeB sends a HANDOVER NOTIFY message to the MME
and this message indicates a successful inter-RAT handover from GERAN to E-UTRAN.

BTS3203E
Figure 1-265
Formula
None
Unit
None
Related Features
L.IRATHO.G2E.ExecSuccI Multi-mode: None

n GSM: None
UMTS: None
GERAN
SRVCC to GERAN

BTS3203E
1.24.4 Number of Inter-RAT inter-RAT Handover Preparation

Failures for Different Causes in a Cell
Counters

E.PrepInFail.Tg inter-RAT
tNotAllow handover
preparation
failures from
GERAN in the
target cell due
to Handover
Target not
allowed
1526728873 L.IRATHO.T2E Number of BTS3203E LTE L

.PrepInFail.Tgt inter-RAT
NotAllow handover
preparation
failures from
TD-SCDMA
network in the
target cell due
to Handover
Target not
allowed
1526728877 L.IRATHO.W2 Number of BTS3203E LTE L

E.PrepInFail.Tg inter-RAT
tNotAllow handover
preparation
failures from
WCDMA
network in the
target cell due
to Handover
Target not
allowed

E.PrepInFail.A GERAN-to-
dmitFail EUTRAN
handover
preparation
failures because
of admission
failure

BTS3203E


E.PrepInFail.Fl GERAN-to-
owCtrl EUTRAN
handover
preparation
failures because
of flow control

E.PrepInFail.H GERAN-to-
OCancel EUTRAN
handover
preparation
failures because
the target cell
receives
handover
cancelation
messages

E.PrepInFail.dis times GERAN-
c.FlowCtrl to-EUTRAN
handover
preparation
messages are
discarded
because of flow
control

.PrepInFail.Ad TDSCDMA-to-
mitFail EUTRAN
handover
preparation
failures because
of admission
failure

.PrepInFail.Flo TDSCDMA-to-
wCtrl EUTRAN
handover
preparation
failures because
of flow control

BTS3203E


.PrepInFail.HO TDSCDMA-to-
Cancel EUTRAN
handover
preparation
failures because
the target cell
receives
handover
cancelation
messages

.PrepInFail.disc times
.FlowCtrl TDSCDMA-to-
EUTRAN
handover
messages are
discarded
because of flow
control

E.PrepInFail.A WCDMA-to-
dmitFail EUTRAN
handover
preparation
failures because
of admission
failure

E.PrepInFail.Fl WCDMA-to-
owCtrl EUTRAN
handover
preparation
failures because
of flow control

E.PrepInFail.H WCDMA-to-
OCancel EUTRAN
handover
preparation
failures because
the target cell
receives
handover
cancelation
messages

BTS3203E


E.PrepInFail.dis times
c.FlowCtrl WCDMA-to-
EUTRAN
handover
messages are
discarded
because of flow
control

E.PrepInFail GERAN-to-
EUTRAN
handover
preparation
failures

.PrepInFail TDSCDMA-to-
EUTRAN
handover
preparation
failures

E.PrepInFail WCDMA-to-
EUTRAN
handover
preparation
failures
Description
The counters measure the number of inter-RAT handover preparation failures with the cause
of "Handover Target not allowed".
Measurement Points
As shown at point A in Figure 1-266, the corresponding counter is incremented by 1 each
time the eNodeB sends a HANDOVER FAILURE message to the MME and this message
indicates an inter-RAT incoming handover preparation failure with the cause of " Handover
Target Not Allowed". The counters are measured as follows:
If the source system is GERAN, the L.IRATHO.G2E.PrepInFail.TgtNotAllow counter is
incremented by 1.
If the source system is TD-SCDMA, the L.IRATHO.T2E.PrepInFail.TgtNotAllow counter is
incremented by 1.
If the source system is WCDMA network, the L.IRATHO.W2E.PrepInFail.TgtNotAllow

BTS3203E
Figure 1-266
Formula
None
Unit
None
Related Features
L.IRATHO.G2E.PrepInFail. Multi-mode: None

TgtNotAllow GSM: None
UMTS: None
GERAN
SRVCC to GERAN
L.IRATHO.T2E.PrepInFail. Multi-mode: None

UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN

BTS3203E
L.IRATHO.W2E.PrepInFail. Multi-mode: None

UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN

AdmitFail GSM: None
UMTS: None
GERAN
SRVCC to GERAN

FlowCtrl GSM: None
UMTS: None
GERAN
SRVCC to GERAN

HOCancel GSM: None
UMTS: None
GERAN
SRVCC to GERAN

disc.FlowCtrl GSM: None
UMTS: None
GERAN
SRVCC to GERAN

BTS3203E

AdmitFail GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN

FlowCtrl GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN

HOCancel GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN

UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN

AdmitFail GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN

BTS3203E

FlowCtrl GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN

HOCancel GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN

UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
L.IRATHO.G2E.PrepInFail Multi-mode: None

GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
L.IRATHO.T2E.PrepInFail Multi-mode: None

GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN

BTS3203E
L.IRATHO.W2E.PrepInFail Multi-mode: None

GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
1.24.5 Number of Inter-RAT Handover Attempts from TD-

SCDMA Network to E-UTRAN
Counters

.PrepAttIn inter-RAT
handover
attempts from
TD-SCDMA
network to E-
UTRAN
Description
The counter measures the number of inter-RAT handover attempts from TD-SCDMA network
to E-UTRAN in a cell.
Measurement Points
As shown at point A in Figure 1-267, the L.IRATHO.T2E.PrepAttIn counter is incremented
this message indicates an inter-RAT handover preparation from TD-SCDMA network to E-
UTRAN.

BTS3203E
Figure 1-267
Formula
None
Unit
None
Related Features
L.IRATHO.T2E.PrepAttIn Multi-mode: None

GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN

BTS3203E
1.24.6 Number of Inter-RAT Handover Preparation from TD-

Counters

.PrepInSucc successful inter-
RAT handover
preparations
from TD-
SCDMA
network to E-
UTRAN
Description
The counter measures the number of successful inter-RAT handover preparations from TD-
SCDMA network to E-UTRAN in a cell.
Measurement Points
As shown at point B in Figure 1-268, the L.IRATHO.T2E.PrepInSucc counter is incremented
by 1 each time the eNodeB sends a HANDOVER REQUEST ACKNOWLEDGE message to
the MME and this message indicates a successful inter-RAT handover preparation from TD-
SCDMA network to E-UTRAN.
Figure 1-268

BTS3203E
Formula
None
Unit
None
Related Features
L.IRATHO.T2E.PrepInSucc Multi-mode: None

GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
1.24.7 Number of Successful Inter-RAT Handovers from TD-

Counters

.ExecSuccIn successful inter-
RAT handovers
from TD-
SCDMA
network to E-
UTRAN
Description
The counter measures the number of successful inter-RAT handovers from TD-SCDMA
network to E-UTRAN in a cell.
Measurement Points
As shown at point C in Figure 1-269, the L.IRATHO.T2E.ExecSuccIn counter is incremented
by 1 each time the eNodeB sends a HANDOVER NOTIFY message from the MME and this

BTS3203E
maessage indicates a successful inter-RAT handover from TD-SCDMA network to E-

UTRAN.
Figure 1-269
Formula
None
Unit
None
Related Features
L.IRATHO.T2E.ExecSuccIn Multi-mode: None

GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN

BTS3203E
1.24.8 Number of Inter-RAT Handover Attempts from WCDMA

Network to E-UTRAN
Counters

E.PrepAttIn inter-RAT
handover
attempts from
WCDMA
network to E-
UTRAN
Description
The counter measures the number of inter-RAT handover attempts from WCDMA network to
E-UTRAN in a cell.
Measurement Points
As shown at point A in Figure 1-270, the L.IRATHO.W2E.PrepAttIn counter is incremented
this message indicates an inter-RAT handover preparation from WCDMA network to E-
UTRAN.
Figure 1-270

BTS3203E
Formula
None
Unit
None
Related Features
L.IRATHO.W2E.PrepAttIn Multi-mode: None

GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
1.24.9 Number of Inter-RAT Handover Preparation from

WCDMA Network to E-UTRAN
Counters

E.PrepInSucc successful inter-
RAT handover
preparations
from WCDMA
network to E-
UTRAN
Description
The counter measures the number of successful inter-RAT handover preparations from
WCDMA network to E-UTRAN in a cell.
Measurement Points
As shown at point B in Figure 1-271, the L.IRATHO.W2E.PrepInSucc counter is
incremented by 1 each time the eNodeB sends a HANDOVER REQUEST

BTS3203E
ACKNOWLEDGE message to the MME and this message indicates a successful inter-RAT
handover preparation from WCDMA network to E-UTRAN.
Figure 1-271
Formula
None
Unit
None
Related Features
L.IRATHO.W2E.PrepInSuc Multi-mode: None

c GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN

BTS3203E
1.24.10 Number of Successful Inter-RAT Handovers from

WCDMA Network to E-UTRAN
Counters

E.ExecSuccIn successful inter-
RAT handovers
from WCDMA
network to E-
UTRAN
Description
The counter measures the number of successful inter-RAT handovers from WCDMA network
to E-UTRAN in a cell.
Measurement Points
As shown at point C in Figure 1-272, the L.IRATHO.W2E.ExecSuccIn counter is
incremented by 1 each time the eNodeB sends a HANDOVER NOTIFY message from the
MME and this message indicates a successful inter-RAT handover from WCDMA network to
E-UTRAN.
Figure 1-272

BTS3203E
Formula
None
Unit
None
Related Features
L.IRATHO.W2E.ExecSuccI Multi-mode: None

n GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
1.25 Outgoing Intra-RAT Handover Measurement

(HO.eRAN.Out.Cell)
Overview
The HO.eRAN.Out.Cell function subset measures the performance of intra-frequency and
inter-frequency of intra E-UTRAN outgoing handovers in a cell, as shown in Figure 1-273,
Figure 1-274, and Figure 1-275.

BTS3203E
Figure 1-273
Figure 1-274
Figure 1-275

BTS3203E
Counters
1526727001 L.HHO.IntereNB.I Number of inter- BTS3203E LTE:

ntraFreq.PrepAttO eNodeB intra- version earlier than
ut frequency outgoing V100R003C00
handover attempts in
a cell

ntraFreq.ExecAttO eNodeB intra- version earlier than
ut frequency outgoing V100R003C00
handovers
executions in a cell
1526727003 L.HHO.IntereNB.I Number of BTS3203E LTE:

ntraFreq.ExecSucc successful inter- version earlier than
Out eNodeB intra- V100R003C00
frequency outgoing
handovers in a cell

nterFreq.PrepAttO eNodeB inter- V100R006C00
ut frequency outgoing
a cell

nterFreq.ExecAttO eNodeB inter- V100R006C00
ut frequency outgoing
handovers

nterFreq.ExecSucc successful inter- V100R006C00
Out eNodeB inter-
frequency outgoing
handovers in a cell
1526728229 L.HHO.BlindHO.P Number of intra- BTS3203E LTE:

repAttOut duplex-mode V100R006C00
outgoing blind
a cell
1526728230 L.HHO.BlindHO.E Number of intra- BTS3203E LTE:

xecAttOut duplex-mode V100R006C00
outgoing blind
handover executions
in a cell

BTS3203E

1526728231 L.HHO.BlindHO.E Number of BTS3203E LTE:

xecSuccOut successful intra- V100R006C00
duplex-mode
outgoing blind
handovers in a cell
1526728285 L.HHO.Prep.FailO Number of intra- BTS3203E LTE:

ut.MME duplex-mode V100R006C00
outgoing handover
the MME side

ut.NoReply duplex-mode V100R006C00
outgoing handover
because of no
responses from the
target cell

ut.PrepFailure duplex-mode V100R006C00
outgoing handover
because of the
handover
preparation failure
messages sent from
the target cell
1526728288 L.HHO.Prep.FailO Number of failed BTS3203E LTE:

ut.HOCancel intra-duplex-mode V100R006C00
outgoing handover
preparations because
of the handover
cancellation
messages sent from
the source cell
1526728325 L.RRCRedirection. Number of intra- BTS3203E LTE:

IntraLTE RAT intra-duplex- V100R005C00
mode redirections
1526728398 L.IntraFreqHO.No Number of intra- BTS3203E LTE:

NRT frequency handover V100R006C00
initiation failures
cell is not on the
NRT of the source
cell

BTS3203E

1526728399 L.InterFreqHO.No Number of inter- BTS3203E LTE:

NRT frequency handover V100R006C00
initiation failures
because the target
cell is not
configured as a
neighboring cell for
the source cell
1526728526 L.HHO.InterFreq. Number of load- BTS3203E LTE:

Load.PrepAttOut based inter- V100R006C00
frequency handover
1526728527 L.HHO.InterFreq. Number of load- BTS3203E LTE:

Load.ExecAttOut based inter- V100R006C00
frequency handover
execution attempts
1526728528 L.HHO.InterFreq. Number of BTS3203E LTE:

Load.ExecSuccOut successful load- V100R006C00
based inter-
frequency handover
executions
1526728539 L.HHO.InterFreq. Number of inter- BTS3203E LTE:

RegainHPLMN.Pr frequency outgoing V100R006C00
epAttOut handover attempts
go back to the
HPLMN

RegainHPLMN.Ex frequency outgoing V100R006C00
ecAttOut handover executions
go back to the
HPLMN

RegainHPLMN.Ex successful inter- V100R006C00
ecSuccOut frequency outgoing
handovers triggered
for UEs to go back
to the HPLMN
1526728554 L.HHO.IntraFreq. Number of intra- BTS3203E LTE:

NoData.ExecAttOu frequency handover V100R006C00
t execution attempts
triggered for UEs
or receive data

BTS3203E

1526728555 L.HHO.IntraFreq. Number of BTS3203E LTE:

NoData.ExecSuccO successful intra- V100R006C00
ut frequency handover
executions triggered
for UEs that do not
transmit or receive
data

NoData.ExecAttOu frequency handover V100R006C00
t execution attempts
triggered for UEs
or receive data

NoData.ExecSuccO successful inter- V100R006C00
ut frequency handover
executions triggered
for UEs that do not
transmit or receive
data
1526728863 L.HHO.FailOut.H Number of inter- BTS3203E LTE:

OCancel eNodeB intra- V100R006C00
duplex-mode
outgoing handover
cancellations
1526728883 L.HHO.S1.IntraFr Number of BTS3203E LTE:

eq.MMEAbnormR responses for V100R006C00
sp abnormal causes
received by the
eNodeB from the
MME during S1-
based outgoing
intra-frequency
handover executions
in a cell
1526728884 L.HHO.S1.InterFr Number of BTS3203E LTE:

eq.MMEAbnormR responses for V100R006C00
sp abnormal causes
received by the
eNodeB from the
MME during S1-
based outgoing
inter-frequency
handover executions
in a cell

BTS3203E


ntraFreq.Succ.ReE successful inter- V100R006C00
st2Src eNodeB intra-
frequency outgoing
handovers where
RRC connections
are reestablished to
the source cell for
UEs in a cell

nterFreq.Succ.ReE successful inter- V100R006C00
st2Src eNodeB inter-
frequency outgoing
handovers where
RRC connections
are reestablished to
the source cell for
UEs in a cell
1526728922 L.HHO.BlindHO.S Number of BTS3203E LTE:

ucc.ReEst2Src successful intra- V100R006C00
duplex-mode blind
outgoing handovers
where RRC
connections are
reestablished to the
source cell for UEs
in a cell

nterFddTdd.PrepA eNodeB inter- V100R006C00
ttOut duplex-mode
outgoing handover
attempts in a cell

nterFddTdd.ExecA eNodeB inter- V100R006C00
ttOut duplex-mode
outgoing handover

nterFddTdd.ExecS successful inter- V100R006C00
uccOut eNodeB inter-
duplex-mode
outgoing handovers
in a cell

BTS3203E


Coverage.PrepAtt coverage-based V100R006C00
Out inter-frequency
handover

Coverage.ExecAtt coverage-based V100R006C00
Out inter-frequency
handover execution
attempts

Coverage.ExecSucc successful coverage- V100R006C00
Out based inter-
frequency handovers

IntraLTE.Coverag coverage-based V100R006C00
e intra-RAT intra-
duplex-mode
redirections
1526729430 L.HHO.IntereNB.S Average duration of BTS3203E LTE:

1.TimeAvg S1-based intra- V100R006C00
duplex-mode
outgoing handovers
in a cell
1526729431 L.HHO.IntereNB. Average duration of BTS3203E LTE:

X2.TimeAvg X2-based intra- V100R006C00
duplex-mode
outgoing handovers
in a cell
1526729479 L.HHO.InterFreq. Number of service- BTS3203E LTE:

Service.PrepAttOu based inter- V100R007C00
t frequency handover
1526729480 L.HHO.InterFreq. Number of service- BTS3203E LTE:

Service.ExecAttOu based inter- V100R007C00
t frequency handover
execution attempts

Service.ExecSuccO successful service- V100R007C00
ut based inter-
frequency handover
executions

BTS3203E


FreqPri.PrepAttOu frequency-priority- V100R007C00
t based inter-
frequency handover

FreqPri.ExecAttOu frequency-priority- V100R007C00
t based inter-
frequency handover
execution attempts

FreqPri.ExecSucc successful V100R007C00
Out frequency-priority-
based inter-
frequency handover
executions

ntraFreq.PrepAttO eNodeB intra- V100R007C00
ut.VoIP frequency outgoing
handover attempts
for UEs performing
voice services in a
cell

nterFreq.PrepAttO eNodeB inter- V100R007C00
handover attempts
for UEs performing
voice services in a
cell

nterFddTdd.PrepA eNodeB inter- V100R007C00
ttOut.VoIP duplex-mode
outgoing handover
attempts for UEs
performing voice
services in a cell

ntraFreq.ExecAttO eNodeB intra- V100R007C00
handover executions
for UEs performing
voice services in a
cell

BTS3203E


nterFreq.ExecAttO eNodeB inter- V100R007C00
handover executions
for UEs performing
voice services in a
cell

nterFddTdd.ExecA eNodeB inter- V100R007C00
ttOut.VoIP duplex-mode
outgoing handover
executions for UEs
performing voice
services in a cell

ntraFreq.ExecSucc successful inter- V100R007C00
Out.VoIP eNodeB intra-
frequency outgoing
handovers for UEs
performing voice
services in a cell

nterFreq.ExecSucc successful inter- V100R007C00
Out.VoIP eNodeB inter-
frequency outgoing
handovers for UEs
performing voice
services in a cell

nterFddTdd.ExecS successful inter- V100R007C00
uccOut.VoIP eNodeB inter-
duplex-mode
outgoing handovers
for UEs performing
voice services in a
cell
1526729559 L.HHO.InterFreq. Number of user- BTS3203E LTE:

UeNumLoad.Prep number-load-based V100R007C00
AttOut inter-frequency
handover

BTS3203E

1526729560 L.HHO.InterFreq. Number of user- BTS3203E LTE:

UeNumLoad.Exec number-load-based V100R007C00
handover execution
attempts

UeNumLoad.ExecS successful user- V100R007C00
uccOut number-load-based
inter-frequency
handover executions
1526729574 L.RRCRedirection. Number of Intra- BTS3203E LTE:

IntraLTE.Load RAT Redirections V100R007C00
Triggered Because
of High Load
1526729584 L.HHO.InterFddT Number of inter- BTS3203E LTE:

dd.NoData.ExecAtt duplex-mode V100R007C00
Out handover execution
attempts triggered
for UEs that do not
transmit or receive
data
1526729585 L.HHO.InterFddT Number of BTS3203E LTE:

dd.NoData.ExecSu successful inter- V100R007C00
ccOut duplex-mode
handover executions
triggered for UEs
or receive data
1526729590 L.HHO.InterFddT Number of load- BTS3203E LTE:

dd.Load.PrepAttO based inter-duplex- V100R007C00
ut mode handover
1526729591 L.HHO.InterFddT Number of load- BTS3203E LTE:

dd.Load.ExecAttO based inter-duplex- V100R007C00
ut mode handover
execution attempts

dd.Load.ExecSucc successful load- V100R007C00
Out based inter-duplex-
mode handover
executions

BTS3203E

1526729593 L.HHO.InterFddT Number of user- BTS3203E LTE:

dd.UeNumLoad.Pr number-load-based V100R007C00
epAttOut inter-duplex-mode
handover
1526729594 L.HHO.InterFddT Number of user- BTS3203E LTE:

dd.UeNumLoad.Ex number-load-based V100R007C00
ecAttOut inter-duplex-mode
handover execution
attempts

dd.UeNumLoad.Ex successful user- V100R007C00
ecSuccOut number-load-based
inter-duplex-mode
handover executions
1526729605 L.HHO.InterFddT Average duration of BTS3203E LTE:

dd.IntereNB.S1.Ti S1-based inter- V100R007C00
meAvg duplex-mode
outgoing handovers
in a cell
1526729606 L.HHO.InterFddT Average duration of BTS3203E LTE:

dd.IntereNB.X2.Ti X2-based inter- V100R007C00
meAvg duplex-mode
outgoing handovers
in a cell

dd.Coverage.PrepA coverage-based V100R007C00
ttOut inter-duplex-mode
handover

dd.Coverage.Exec coverage-based V100R007C00
AttOut inter-duplex-mode
handover execution
attempts

dd.Coverage.ExecS successful coverage- V100R007C00
uccOut based inter-duplex-
mode handover
executions

BTS3203E

1526729615 L.InterFddTddHO. Number of inter- BTS3203E LTE:

NoNRT duplex-mode V100R007C00
handover initiation
failures because the
on the NRT of the
source cell
1526729616 L.HHO.S1.InterFd Number of BTS3203E LTE:

dTdd.MMEAbnor responses for V100R007C00
mRsp abnormal causes
received by the
eNodeB from the
MME during S1-
based inter-duplex-
mode outgoing
handover executions
in a cell

nterFddTdd.Succ. successful inter- V100R007C00
ReEst2Src eNodeB inter-
duplex-mode
outgoing handovers
where RRC
connections are
source cell for UEs
in a cell
1526729619 L.HHO.X2.InterFd Number of BTS3203E LTE:

dTdd.Succ.ReEst2 successful X2-based V100R007C00
Src inter-duplex-mode
outgoing handovers
where RRC
connections are
source cell for UEs
in a cell
1526729620 L.HHO.InterFddT Number of SPID- BTS3203E LTE:

dd.RegainHPLMN. based inter-duplex- V100R007C00
PrepAttOut mode outgoing
handover attempts
back to the HPLMN
1526729621 L.HHO.InterFddT Number of SPID- BTS3203E LTE:

dd.RegainHPLMN. based inter-duplex- V100R007C00
ExecAttOut mode outgoing
handover executions
back to the HPLMN

BTS3203E


dd.RegainHPLMN. successful SPID- V100R007C00
ExecSuccOut based inter-duplex-
mode outgoing
handovers back to
the HPLMN

dd.BlindHO.PrepA duplex-mode V100R007C00
ttOut outgoing blind
a cell

dd.BlindHO.ExecA duplex-mode V100R007C00
ttOut outgoing blind
handover executions
in a cell

dd.BlindHO.ExecS successful inter- V100R007C00
uccOut duplex-mode
outgoing blind
handovers in a cell

dd.Prep.FailOut.M duplex-mode V100R007C00
ME outgoing handover
the MME side

dd.Prep.FailOut.N duplex-mode V100R007C00
oReply outgoing handover
because of no
responses from the
target cell

dd.Prep.FailOut.Pr duplex-mode V100R007C00
epFailure outgoing handover
because of the
handover
preparation failure
messages sent from
the target cell

BTS3203E

1526729629 L.HHO.InterFddT Number of failed BTS3203E LTE:

dd.Prep.FailOut.H inter-duplex-mode V100R007C00
OCancel outgoing handover
preparations because
of the handover
cancellation
messages sent from
the source cell

dd.FailOut.HOCan eNodeB inter- V100R007C00
cel duplex-mode
outgoing handover
cancellations
1526729631 L.RRCRedirection. Number of intra- BTS3203E LTE:

InterFddTdd RAT inter-duplex- V100R009C00
mode redirections

InterFddTdd.Cove coverage-based V100R007C00
rage intra-RAT inter-
duplex-mode
redirections

dd.BlindHO.Succ. successful inter- V100R007C00
ReEst2Src duplex-mode blind
outgoing handovers
where RRC
connections are
source cell for UEs
in a cell
1526729879 L.RRCRedirection. Number of load- BTS3203E LTE:

InterFddTdd.Load based intra-RAT V100R007C00
inter-duplex-mode
redirections
1526729994 L.HHO.InterFreq. Number of UL- BTS3203E LTE:

ULquality.PrepAtt quality-based inter- V100R007C00
Out frequency handover
1526729995 L.HHO.InterFddT Number of UL- BTS3203E LTE:

dd.ULquality.Prep quality-based inter- V100R007C00
AttOut duplex-mode
handover

BTS3203E

1526729996 L.HHO.InterFreq. Number of UL- BTS3203E LTE:

ULquality.ExecAtt quality-based inter- V100R007C00
Out frequency handover
execution attempts
1526729997 L.HHO.InterFddT Number of UL- BTS3203E LTE:

dd.ULquality.Exec quality-based inter- V100R007C00
AttOut duplex-mode
handover execution
attempts

ULquality.ExecSuc successful UL- V100R007C00
cOut quality-based inter-
frequency handover
executions

dd.ULquality.Exec successful UL- V100R007C00
SuccOut quality-based inter-
duplex-mode
handover executions

IntraLTE.Ulquality quality-based intra- V100R007C00
RAT redirections

InterFddTdd.Ulqu quality-based inter- V100R007C00
ality duplex-mode
redirections
1526730002 L.HHO.InterFddT Number of service- BTS3203E LTE:

dd.Service.PrepAtt based inter-duplex- V100R007C00
Out mode handover

dd.Service.ExecAtt based inter-duplex- V100R007C00
Out mode handover
execution attempts

dd.Service.ExecSuc successful service- V100R007C00
cOut based inter-duplex-
mode handover
executions

InterFddTdd.Servi based inter-duplex- V100R007C00
ce mode redirections

BTS3203E


dd.FreqPri.PrepAtt frequency-priority- V100R007C00
mode handover

dd.FreqPri.ExecAtt frequency-priority- V100R007C00
mode handover
execution attempts

dd.FreqPri.ExecSu successful V100R007C00
ccOut frequency-priority-
based inter-duplex-
mode handover
executions

InterFddTdd.Freq frequency-priority- V100R007C00
Pri based inter-duplex-
mode redirections
1526730016 L.RRCRedirection. Number of SPID- BTS3203E LTE:

InterFddTdd.Regai based inter-duplex- V100R007C00
nHPLMN mode redirections
back to the HPLMN
1526730847 L.HHO.S1.BlindH Number of BTS3203E LTE:

O.MMEAbnormRs responses with V100R011C10
p abnormal causes
received by the
eNodeB from the
MME during S1-
based outgoing blind
handover executions

ut.Other duplex-mode V100R011C10
outgoing handover
due to other causes

dd.Prep.FailOut.Ot duplex-mode V100R011C10
her outgoing handover
due to other causes

BTS3203E


MBMSInterest.Pre frequency outgoing V100R011C10
pAttOut handover
triggered by
interests in MBMS
services

MBMSInterest.Exe frequency outgoing V100R011C10
cAttOut handover execution
attempts triggered
by interests in
MBMS services

MBMSInterest.Exe successful inter- V100R011C10
cSuccOut frequency handovers
triggered by
interests in MBMS
services

dd.MBMSInterest. duplex-mode V100R011C10
PrepAttOut outgoing handover
triggered by
interests in MBMS
services

dd.MBMSInterest. duplex-mode V100R011C10
ExecAttOut outgoing handover
execution attempts
triggered by
interests in MBMS
services

dd.MBMSInterest. successful inter- V100R011C10
ExecSuccOut duplex-mode
handovers triggered
by interests in
MBMS services

LowSpeed.PrepAtt frequency outgoing V100R011C10
Out handover
of low-speed UEs

BTS3203E


LowSpeed.ExecAtt frequency outgoing V100R011C10
attempts of low-
speed UEs

LowSpeed.ExecSuc successful inter- V100R011C10
cOut frequency outgoing
handover executions
of low-speed UEs
1526733189 L.HHO.InterFreq. Number of times BTS3203E LTE:

LowSpeed.MMEA when the eNodeB V100R011C10
bnormRsp receives messages
from the MME with
abnormal reasons
during inter-
frequency outgoing
handover executions
of low-speed UEs

Prep.FailOut.MME frequency outgoing V100R007C00
handover
because of the MME
side causes

Prep.FailOut.NoRe frequency outgoing V100R007C00
ply handover
because the target
cell does not
respond

Prep.FailOut.Prep frequency outgoing V100R007C00
Failure handover
because the target
cell sends handover
preparation failure
messages

BTS3203E


Prep.FailOut.HOC frequency outgoing V100R007C00
ancel handover
because the source
cell sends handover
cancellation
messages
1526735524 L.HHO.Prep.FailO Number of outgoing BTS3203E LTE:

ut.TargetIllegal handover V100R007C00
because the
handover response
messages sent by the
target eNodeB fail
the validity check

Prep.FailOut.Targe frequency outgoing V100R007C00
tIllegal handover
because the
handover response
messages sent by the
target eNodeB fail
the validity check
1526737702 L.HHO.SuperCom Number of intra- BTS3203E LTE:

bCell.IntraeNB.Pre eNodeB inter-SFN- V100R011C10
pAttOut cell outgoing
a super combined
cell
1526737703 L.HHO.SuperCom Number of BTS3203E LTE:

bCell.IntraeNB.Ex successful intra- V100R011C10
ecSuccOut eNodeB inter-SFN-
cell outgoing
handovers in a super
combined cell
1526737704 L.HHO.SuperCom Number of inter- BTS3203E LTE:

bCell.IntereNB.Pre eNodeB inter-SFN- V100R011C10
pAttOut cell outgoing
a super combined
cell

BTS3203E

1526737705 L.HHO.SuperCom Number of BTS3203E LTE:

bCell.IntereNB.Exe successful inter- V100R011C10
cSuccOut eNodeB inter-SFN-
cell outgoing
handovers in a super
combined cell

dd.Backoff.PrepAtt duplex-mode V100R011C10
Out handover
triggered by MLB
based on the number
of low-efficiency
UEs

dd.Backoff.ExecAtt duplex-mode V100R011C10
attempts triggered
by MLB based on
the number of low-
efficiency UEs

dd.Backoff.ExecSu successful inter- V100R011C10
ccOut duplex-mode
handovers triggered
by MLB based on
the number of low-
efficiency UEs
1526737709 L.HHO.S1.InterFd Number of times BTS3203E LTE:

dTdd.Backoff.MM that the eNodeB V100R011C10
EAbnormRsp 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
1526737751 L.HHO.SuperCom Number of inter- BTS3203E LTE:

bCell.IntereNB.Exe eNodeB inter-SFN- V100R011C10
cAttOut cell outgoing
handover executions
in a super combined
cell

BTS3203E


dd.Service.Meas.Ti triggered inter- V100R011C10
meout duplex-mode
measurement
expiration times

dd.Service.AttFail. unsuccessful V100R011C10
NoNRT service-triggered
inter-duplex-mode
handover initiation
request attempts due
to lack of
neighboring
relationship between
two cells
1526741920 L.HHO.FailOut.H Number of times BTS3203E LTE:

OCancel.FlowConf inter-eNodeB intra- V100R011C10
lict duplex-mode
outgoing handovers
are canceled due to
flow conflicts
1526741921 L.HHO.InterFddT Number of times BTS3203E LTE:

dd.FailOut.HOCan inter-eNodeB inter- V100R011C10
cel.FlowConflict duplex-mode
outgoing handovers
are canceled due to
flow conflicts

dd.UlExperienceLo duplex-mode V100R012C10
ad.PrepAttOut handover
triggered by uplink-
experience-based
load balancing

dd.UlExperienceLo duplex-mode V100R012C10
ad.ExecAttOut handover execution
attempts triggered
by uplink-
experience-based
load balancing

BTS3203E


dd.UlExperienceLo successful inter- V100R012C10
ad.ExecSuccOut duplex-mode
handover executions
triggered by uplink-
experience-based
load balancing
1526746054 L.HHO.SpePciCell. Number of inter- BTS3203E LTE:

PrepAttOut eNodeB intra- V100R012C10
duplex-mode
outgoing handover
attempts from a
local cell to
specified-PCI cells
1526746055 L.HHO.SpePciCell. Number of inter- BTS3203E LTE:

ExecAttOut eNodeB intra- V100R012C10
duplex-mode
outgoing handover
executions from a
local cell to
specified-PCI cells
1526746056 L.HHO.SpePciCell. Number of BTS3203E LTE:

ExecSuccOut successful inter- V100R012C10
eNodeB intra-
duplex-mode
outgoing handovers
from a local cell to
specified-PCI cells
The HO.eRAN.Out.Cell function subset contains counters related to intra-RAT outgoing
handover. In terms of the duplex mode of the source and target cell, these counters can be
categorized as counters related to intra-duplex-mode (including intra-frequency and inter-
frequency) outgoing handover and inter-duplex-mode outgoing handover. In terms of whether
the source and target cells belong to the same eNodeB, some of these counters can be
categorized as counters related to intra-eNodeB outgoing handover and inter-eNodeB
outgoing handover. In terms of the procedure, these counters can be categorized as counters
related to handover and redirection. In terms of the triggering cause, some of these counters
can be categorized as counter related to coverage-based handover, load-based handover,
frequency-priority-based handover, and others. In terms of the scenario, some of these
counters can be categorized as counters in VoIP scenarios and others. The following table
shows the parent-child relationship of the counters.

BTS3203E
L.HHO.IntereNB.IntraFreq.PrepAttOut L.HHO.IntereNB.IntraFreq.PrepAttOut.VoI
P
L.HHO.IntereNB.IntraFreq.ExecAttOut L.HHO.IntereNB.IntraFreq.ExecAttOut.VoI
P
L.HHO.IntereNB.IntraFreq.ExecSuccOut L.HHO.IntereNB.IntraFreq.Succ.ReEst2Src
L.HHO.IntereNB.IntraFreq.ExecSuccOut L.HHO.S1.IntraFreq.MMEAbnormRsp
L.HHO.IntereNB.IntraFreq.ExecSuccOut L.HHO.IntereNB.IntraFreq.ExecSuccOut.V
oIP
L.HHO.IntereNB.InterFreq.PrepAttOut L.HHO.IntereNB.InterFreq.PrepAttOut.VoI
P
L.HHO.IntereNB.InterFreq.ExecAttOut L.HHO.IntereNB.InterFreq.ExecAttOut.VoI
P
L.HHO.IntereNB.InterFreq.ExecSuccOut L.HHO.IntereNB.InterFreq.Succ.ReEst2Src
L.HHO.IntereNB.InterFreq.ExecSuccOut L.HHO.S1.InterFreq.MMEAbnormRsp
L.HHO.IntereNB.InterFreq.ExecSuccOut L.HHO.IntereNB.InterFreq.ExecSuccOut.V
oIP
L.HHO.BlindHO.ExecSuccOut L.HHO.BlindHO.Succ.ReEst2Src
L.HHO.Prep.FailOut.MME L.HHO.IntraFreq.Prep.FailOut.MME
L.HHO.Prep.FailOut.NoReply L.HHO.IntraFreq.Prep.FailOut.NoReply
L.HHO.Prep.FailOut.PrepFailure L.HHO.IntraFreq.Prep.FailOut.PrepFailure
L.HHO.Prep.FailOut.HOCancel L.HHO.IntraFreq.Prep.FailOut.HOCancel
L.RRCRedirection.IntraLTE L.RRCRedirection.IntraLTE.Coverage
L.RRCRedirection.IntraLTE.load
L.RRCRedirection.IntraLTE.Ulquality
L.RRCRedirection.IntraLTE.HighSpeedUse
r
L.RRCRedirection.IntraLTE.QCI1
L.HHO.InterFreq.Load.PrepAttOut L.HHO.InterFreq.UeNumLoad.PrepAttOut
L.HHO.InterFreq.Load.ExecAttOut L.HHO.InterFreq.UeNumLoad.ExecAttOut
L.HHO.InterFreq.Load.ExecSuccOut L.HHO.InterFreq.UeNumLoad.ExecSuccO
ut
L.HHO.IntereNB.InterFddTdd.PrepAttOut L.HHO.IntereNB.InterFddTdd.PrepAttOut.
VoIP

BTS3203E
L.HHO.IntereNB.InterFddTdd.ExecAttOut L.HHO.IntereNB.InterFddTdd.ExecAttOut.
VoIP
L.HHO.IntereNB.InterFddTdd.ExecSuccOu L.HHO.IntereNB.InterFddTdd.ExecSuccOu
t t.VoIP
L.HHO.InterFddTdd.Load.PrepAttOut L.HHO.InterFddTdd.UeNumLoad.PrepAtt
Out
L.HHO.InterFddTdd.Load.ExecAttOut L.HHO.InterFddTdd.UeNumLoad.ExecAtt
Out
L.HHO.InterFddTdd.Load.ExecSuccOut L.HHO.InterFddTdd.UeNumLoad.ExecSuc
cOut
L.RRCRedirection.InterFddTdd L.RRCRedirection.InterFddTdd.Coverage
L.RRCRedirection.InterFddTdd.load
L.RRCRedirection.InterFddTdd.Ulquality
L.RRCRedirection.InterFddTdd.Service
L.RRCRedirection.InterFddTdd.FreqPri
L.RRCRedirection.InterFddTdd.RegainHPL
MN
L.RRCRedirection.InterFddTdd.QCI1
L.HHO.Prep.FailOut.TargetIllegal L.HHO.IntraFreq.Prep.FailOut.TargetIllegal
1.25.1 Number of Inter-eNodeB Outgoing Handover Attempts in a

Cell
Counters
1526727001 L.HHO.IntereN Number of BTS3203E LTE L

B.IntraFreq.Pre inter-eNodeB
pAttOut intra-frequency
outgoing
handover
attempts in a
cell

BTS3203E


B.InterFreq.Pre inter-eNodeB
pAttOut inter-frequency
outgoing
handover
attempts in a
cell

B.InterFddTdd. inter-eNodeB
PrepAttOut inter-duplex-
mode outgoing
handover
attempts in a
cell
1526746054 L.HHO.SpePci Number of BTS3203E LTE L

Cell.PrepAttOut inter-eNodeB
intra-duplex-
mode outgoing
handover
attempts from a
local cell to
specified-PCI
cells
Description
The counters measure the following:
Number of inter-eNodeB intra-frequency outgoing handover attempts in a cell
Number of inter-eNodeB inter-frequency outgoing handover attempts in a cell
Number of inter-eNodeB inter-duplex-mode outgoing handover attempts in a cell
Number of inter-eNodeB outgoing handover attempts from a local cell to specified-PCI cells
In an inter-eNodeB handover, the source cell and target cell are controlled by different
eNodeBs. Such a handover is performed between different eNodeBs over the S1 or X2
interface. If the source cell and target cell work on the same frequency in the same duplex
mode, the handover is an intra-frequency handover. If the source cell and target cell work on
different frequencies in the same duplex mode, the handover is an inter-frequency handover.
If the source cell and the target cell work in different duplex modes, the handover is an inter-
duplex-mode handover.

BTS3203E
Measurement Points
As shown at point A in Figure 1-276, during an X2-based handover the corresponding
counter is incremented by 1 each time the source eNodeB decides to perform an X2-based
blind handover or the source eNodeB decides to perform an X2-based handover after the
source cell receives a measurement report from the UE.
As shown at point A in Figure 1-277, during an S1-based handover the corresponding counter
is incremented by 1 each time the source eNodeB decides to perform an S1-based blind
handover or the source eNodeB decides to perform an S1-based handover after the source cell
receives a measurement report from the UE.
If the source cell and the target cell work on the same frequency, the
L.HHO.IntereNB.IntraFreq.PrepAttOut counter is incremented by 1.
If the source cell and the target cell work on different frequencies, the
L.HHO.IntereNB.InterFreq.PrepAttOut counter is incremented by 1.
If the source cell and the target cell work in different duplex modes, the
L.HHO.IntereNB.InterFddTdd.PrepAttOut counter is incremented by 1.
If the target cell has a PCI in a specified PCI group, the L.HHO.SpePciCell.PrepAttOut
Figure 1-276

BTS3203E
Figure 1-277
Formula
None
Unit
None
Related Features
L.HHO.IntereNB.IntraFreq. Multi-mode: None

UMTS: None
frequency Handover
L.HHO.IntereNB.InterFreq. Multi-mode: None

UMTS: None
frequency Handover

BTS3203E
L.HHO.IntereNB.InterFddT Multi-mode: None

dd.PrepAttOut GSM: None
UMTS: None
frequency Handover
L.HHO.SpePciCell.PrepAtt Multi-mode: None

Out GSM: None
UMTS: None
frequency Handover
frequency Handover
1.25.2 Number of Inter-eNodeB Outgoing Handovers Executions

in a Cell
Counters

B.IntraFreq.Exe inter-eNodeB
cAttOut intra-frequency
outgoing
handovers
executions in a
cell

B.InterFreq.Exe inter-eNodeB
cAttOut inter-frequency
outgoing
handovers
executions in a
cell

BTS3203E


ExecAttOut inter-duplex-
mode outgoing
handover
executions in a
cell

Cell.ExecAttOu inter-eNodeB
t intra-duplex-
mode outgoing
handover
executions from
a local cell to
specified-PCI
cells
Description
Number of inter-eNodeB intra-frequency outgoing handover executions in a cell
Number of inter-eNodeB inter-frequency outgoing handover executions in a cell
Number of inter-eNodeB inter-duplex-mode outgoing handover executions in a cell
Number of inter-eNodeB outgoing handover executions from a local cell to specified-PCI

cells
Measurement Points
As shown at point B in Figure 1-278, during an X2-based handover the corresponding
counter is incremented by 1 each time the source eNodeB sends an RRC Connection
Reconfiguration message to the UE after receiving a HANDOVER REQUEST
ACKNOWLEDGE message from the target eNodeB.

BTS3203E
As shown at point B in Figure 1-279, during an S1-based handover the corresponding counter
is incremented by 1 each time the source eNodeB sends an RRC Connection Reconfiguration
message to the UE after receiving a HANDOVER COMMAND message from the MME.
L.HHO.IntereNB.IntraFreq.ExecAttOut counter is incremented by 1.
L.HHO.IntereNB.InterFreq.ExecAttOut counter is incremented by 1.
L.HHO.IntereNB.InterFddTdd.ExecAttOut counter is incremented by 1.
If the target cell has a PCI in a specified PCI group, the L.HHO.SpePciCell.ExecAttOut
Figure 1-278

BTS3203E
Figure 1-279
Formula
None
Unit
None
Related Features

UMTS: None
frequency Handover

UMTS: None
frequency Handover

BTS3203E

dd.ExecAttOut GSM: None
UMTS: None
frequency Handover
L.HHO.SpePciCell.ExecAtt Multi-mode: None

Out GSM: None
UMTS: None
frequency Handover
frequency Handover
1.25.3 Number of Successful Inter-eNodeB Outgoing Handovers

in a Cell
Counters

B.IntraFreq.Exe successful inter-
cSuccOut eNodeB intra-
frequency
outgoing
handovers in a
cell

B.InterFreq.Exe successful inter-
cSuccOut eNodeB inter-
frequency
outgoing
handovers in a
cell

BTS3203E


B.InterFddTdd. successful inter-
ExecSuccOut eNodeB inter-
duplex-mode
outgoing
handovers in a
cell

Cell.ExecSucc successful inter-
Out eNodeB intra-
duplex-mode
outgoing
handovers from
a local cell to
specified-PCI
cells
Description
Number of successful inter-eNodeB intra-frequency outgoing handovers in a cell
Number of successful inter-eNodeB inter-frequency outgoing handovers in a cell
Number of successful inter-eNodeB inter-duplex-mode outgoing handovers in a cell
Number of successful inter-eNodeB outgoing handovers from a local cell to specified-PCI
cells
3GPP TS 36.300 V10.6.0, section 5.3.7 in 3GPP TS 36.331 V10.4.0, and section 8.3.3 in
3GPP TS 36.413 V10.4.0.
Measurement Points
As shown at point C in Figure 1-280, during an X2-based handover the corresponding
counter is incremented by 1 each time data in the buffer is forwarded during the handover
after the source eNodeB receives a UE CONTEXT RELEASE message from the target
eNodeB.
As shown at point C in Figure 1-281, during an X2-based handover after an RRC connection
is successfully reestablished to the target eNodeB for the UE, the corresponding counter is

BTS3203E
incremented by 1 each time data in the buffer is forwarded during the handover after the
source eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB.
is successfully reestablished to the source eNodeB for the UE, the corresponding counter is
incremented by 1 each time.
is incremented by 1 each time data in the buffer is forwarded during the handover after the
source eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME.
As shown at point C in Figure 1-283, during an S1-based handover after an RRC connection
incremented by 1 each time data in the buffer is forwarded during the handover after the
source eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME.
is successfully reestablished to the source eNodeB for the UE, the corresponding counter is
L.HHO.IntereNB.IntraFreq.ExecSuccOut counter is incremented by 1.
L.HHO.IntereNB.InterFreq.ExecSuccOut counter is incremented by 1.
L.HHO.IntereNB.InterFddTdd.ExecSuccOut counter is incremented by 1.
If the target cell has a PCI in a specified PCI group, the L.HHO.SpePciCell.ExecSuccOut
Figure 1-280

BTS3203E
Figure 1-281
Figure 1-282

BTS3203E
Figure 1-283

BTS3203E
Figure 1-284

BTS3203E
Figure 1-285
Formula
None
Unit
None
Related Features

UMTS: None
frequency Handover

BTS3203E

UMTS: None
frequency Handover

dd.ExecSuccOut GSM: None
UMTS: None
frequency Handover
L.HHO.SpePciCell.ExecSuc Multi-mode: None

cOut GSM: None
UMTS: None
frequency Handover
frequency Handover
1.25.4 Number of Outgoing Blind Handover Attempts in a Cell

Counters
1526728229 L.HHO.BlindH Number of BTS3203E LTE L

O.PrepAttOut intra-duplex-
mode outgoing
blind handover
attempts in a
cell

BTS3203E

1526729623 L.HHO.InterFd Number of BTS3203E LTE L

dTdd.BlindHO. inter-duplex-
PrepAttOut mode outgoing
blind handover
attempts in a
cell
Description
The counters measure the number of intra-RAT outgoing blind handover attempts in a cell.
Not triggered on the basis of UE measurement reports, the blind handover is a handover in
which the eNodeB specifies the target cell for the UE. In specific networking scenarios, the
eNodeB performs a blind handover to actively hand over the UE from the source cell. If the
source and target cells work in the same duplex mode, the blind handover is an intra-duplex-
mode blind handover. If the source and target cells work in different duplex modes, the blind
handover is an inter-duplex-mode blind handover.
Measurement Points
As shown at point A in Figure 1-286, Figure 1-287, the L.HHO.BlindHO.PrepAttOut or
L.HHO.InterFddTdd.BlindHO.PrepAttOut counter is incremented by 1 each time the eNodeB
decides to perform a blind handover.
If the source and target cells work in the same duplex mode, the L.HHO.BlindHO.PrepAttOut
If the source and target cells work in different duplex modes, the
L.HHO.InterFddTdd.BlindHO.PrepAttOut counter is incremented by 1.
Figure 1-286 shows an X2-based blind handover, and Figure 1-287 shows an S1-based blind
handover.

BTS3203E
Figure 1-286
Figure 1-287
Formula
None
Unit
None

BTS3203E
Related Features
L.HHO.BlindHO.PrepAttOu Multi-mode: None

t GSM: None
UMTS: None
frequency Handover
frequency Handover
L.HHO.InterFddTdd.BlindH Multi-mode: None

O.PrepAttOut GSM: None
UMTS: None
frequency Handover
1.25.5 Number of Outgoing Blind Handovers Executions in a Cell

Counters

O.ExecAttOut intra-duplex-
mode outgoing
blind handover
executions in a
cell

dTdd.BlindHO. inter-duplex-
ExecAttOut mode outgoing
blind handover
executions in a
cell
Description
The counters measure the number of intra-RAT outgoing blind handover executions in a cell.

BTS3203E
Measurement Points
As shown at point B in Figure 1-288, Figure 1-289, the L.HHO.BlindHO.ExecAttOut or
L.HHO.InterFddTdd.BlindHO.ExecAttOut counter is incremented by 1 each time the eNodeB
decides to perform a blind handover and sends an RRC Connection Reconfiguration message
to the UE.
If the source and target cells work in the same duplex mode, the L.HHO.BlindHO.ExecAttOut
L.HHO.InterFddTdd.BlindHO.ExecAttOut counter is incremented by 1.
Figure 1-288 shows an X2-based blind handover, and Figure 1-289 shows an S1-based blind
handover.
Figure 1-288

BTS3203E
Figure 1-289
Formula
None
Unit
None
Related Features
L.HHO.BlindHO.ExecAttO Multi-mode: None

ut GSM: None
UMTS: None
frequency Handover
frequency Handover

O.ExecAttOut GSM: None
UMTS: None
frequency Handover

BTS3203E
1.25.6 Number of Successful Outgoing Blind Handovers in a Cell
Counters

O.ExecSuccOut successful intra-
duplex-mode
outgoing blind
handovers in a
cell

dTdd.BlindHO. successful inter-
ExecSuccOut duplex-mode
outgoing blind
handovers in a
cell
Description
The counters measure the number of successful intra-RAT outgoing blind handovers in a cell.
Measurement Points
time the eNodeB decides to perform an X2-based blind handover and the source eNodeB
receives a UE CONTEXT RELEASE message from the target eNodeB.
As shown at point C in Figure 1-291, during an X2-based blind handover, the corresponding
counter is incremented by 1 each time the source eNodeB receives a UE CONTEXT
RELEASE message from the target eNodeB after an RRC connection is successfully
As shown at point C in Figure 1-294, during an X2-based blind handover, the corresponding
counter is incremented by 1 each time an RRC connection is successfully reestablished to the
source eNodeB for the UE.

time the eNodeB decides to perform an S1-based blind handover and the source eNodeB
receives a UE CONTEXT RELEASE COMMAND message from the MME.

BTS3203E
As shown at point C in Figure 1-293, during an S1-based handover, the corresponding

counter is incremented by 1 each time the source eNodeB receives a UE CONTEXT
RELEASE COMMAND message from the MME after an RRC connection is successfully
counter is incremented by 1 each time after an RRC connection is successfully reestablished
to the source eNodeB for the UE.
If the source and target cells work in the same duplex mode, the
L.HHO.BlindHO.ExecSuccOut counter is incremented by 1.
L.HHO.InterFddTdd.BlindHO.ExecSuccOut counter is incremented by 1.
Figure 1-290

BTS3203E
Figure 1-291
Figure 1-292

BTS3203E
Figure 1-293

BTS3203E
Figure 1-294

BTS3203E
Figure 1-295
Formula
None
Unit
None
Related Features
L.HHO.BlindHO.ExecSucc Multi-mode: None

Out GSM: None
UMTS: None
frequency Handover
frequency Handover

BTS3203E

O.ExecSuccOut GSM: None
UMTS: None
frequency Handover
1.25.7 Number of Outgoing Handover Failures for Different

Causes in a Cell
Counters
1526728285 L.HHO.Prep.Fa Number of BTS3203E LTE L

ilOut.MME intra-duplex-
mode outgoing
handover
preparation
failures because
of faults on the
MME side

ilOut.NoReply intra-duplex-
mode outgoing
handover
preparation
failures because
of no responses
from the target
cell

ilOut.PrepFailur intra-duplex-
e mode outgoing
handover
preparation
failures because
of the handover
preparation
failure
messages sent
from the target
cell

BTS3203E


ilOut.HOCancel failed intra-
duplex-mode
outgoing
handover
preparations
because of the
handover
cancellation
messages sent
from the source
cell
1526728863 L.HHO.FailOut Number of BTS3203E LTE L

.HOCancel inter-eNodeB
intra-duplex-
mode outgoing
handover
cancellations

dTdd.Prep.Fail inter-duplex-
Out.MME mode outgoing
handover
preparation
failures because
of faults on the
MME side

Out.NoReply mode outgoing
handover
preparation
failures because
of no responses
from the target
cell

Out.PrepFailure mode outgoing
handover
preparation
failures because
of the handover
preparation
failure
messages sent
from the target
cell

BTS3203E


dTdd.Prep.Fail failed inter-
Out.HOCancel duplex-mode
outgoing
handover
preparations
because of the
handover
cancellation
messages sent
from the source
cell

dTdd.FailOut.H inter-eNodeB
OCancel inter-duplex-
mode outgoing
handover
cancellations

ilOut.Other intra-duplex-
mode outgoing
handover
preparation
failures due to
other causes

Out.Other mode outgoing
handover
preparation
failures due to
other causes
1526735520 L.HHO.IntraFre Number of BTS3203E LTE L

q.Prep.FailOut. intra-frequency
MME outgoing
handover
preparation
failures because
of the MME
side causes

BTS3203E


NoReply outgoing
handover
preparation
failures because
the target cell
does not
respond

PrepFailure outgoing
handover
preparation
failures because
the target cell
sends handover
preparation
failure
messages

HOCancel outgoing
handover
preparation
failures because
the source cell
sends handover
cancellation
messages

ilOut.TargetIlle outgoing
gal handover
preparation
failures because
the handover
response
messages sent
by the target
eNodeB fail the
validity check

BTS3203E


TargetIllegal outgoing
handover
preparation
failures because
the handover
response
messages sent
by the target
eNodeB fail the
validity check
1526741920 L.HHO.FailOut Number of BTS3203E LTE L

.HOCancel.Flo times inter-
wConflict eNodeB intra-
duplex-mode
outgoing
handovers are
canceled due to
flow conflicts

dTdd.FailOut.H times inter-
OCancel.FlowC eNodeB inter-
onflict duplex-mode
outgoing
handovers are
canceled due to
flow conflicts
Description
The counters measure the number of outgoing handover failures based on the failure cause in
a cell. Outgoing handover failures usually occur during handover preparation and are caused
by faults on the MME side, no responses from the target cell, the target cell sending handover
preparation failure messages, or the source cell sending handover cancellation messages.
Handover preparation is the procedure to prepare handover resources between the handover
decision and the handover execution. If the source and target cells work in the same duplex
mode, the handover is an intra-duplex-mode handover. If the source and target cells work in
different duplex modes, the handover is an inter-duplex-mode handover.
Measurement Points
As shown at point B in Figure 1-296 during the preparation phase of an S1-based handover or
as shown at point B in Figure 1-297 during the preparation phase of an X2-based handover,
the corresponding counter is incremented by 1 each time the source cell receives a UE
CONTEXT RELEASE COMMAND message from the MME. No matter whether the source
and target cells work on the same frequency or different frequencies, the

BTS3203E
L.HHO.Prep.FailOut.MME counter is incremented by 1. If the source and target cells work on

the same frequency, the L.HHO.IntraFreq.Prep.FailOut.MME counter is incremented by 1. If
the source and target cells work in different duplex modes, the
L.HHO.InterFddTdd.Prep.FailOut.MME counter is incremented by 1.
As shown at point B in Figure 1-298 at the end of the preparation phase of an S1-based
handover or as shown at point B in Figure 1-299 at the end of the preparation phase of an X2-
based handover, the corresponding counter is incremented by 1 each time the source cell does
not receive any messages from the target eNodeB, such as the HANDOVER REQUEST
ACKNOWLEDEG and HANDOVER PREPARATION FAILURE messages sent from the
target eNodeB during the X2-based handover and the HANDOVER COMMAND and
HANDOVER PREPARATION FAILURE messages sent from the MME during the S1-based
handover.
No matter whether the source and target cells work on the same frequency or different
frequencies, the L.HHO.Prep.FailOut.NoReply counter is incremented by 1.
If the source and target cells work on the same frequency, the
L.HHO.IntraFreq.Prep.FailOut.NoReply counter is incremented by 1.
L.HHO.InterFddTdd.Prep.FailOut.NoReply counter is incremented by 1.
At the handover preparation phase of an S1- or X2-based handover, the
L.HHO.Prep.FailOut.PrepFailure, L.HHO.IntraFreq.Prep.FailOut.PrepFailure, and
L.HHO.InterFddTdd.Prep.FailOut.PrepFailure counters are measured in two conditions: (1)
As shown at point B in Figure 1-300, during the handover preparation phase of an S1-based
handover, the corresponding counter is incremented by 1 each time the source cell receives a
HANDOVER PREPARATION FAILURE message from the MME.
(2) As shown at point B in Figure 1-301, during the handover preparation phase of an X2-
based handover, the corresponding counter is incremented by 1 each time the source cell
receives a HANDOVER PREPARATION FAILURE message from the target cell.
frequencies, the L.HHO.Prep.FailOut.PrepFailure counter is incremented by 1.
If the source and target cells work on the same frequency,
the .HHO.IntraFreq.Prep.FailOut.PrepFailure counter is incremented by 1.
L.HHO.InterFddTdd.Prep.FailOut.PrepFailure counter is incremented by 1.
As show at point B in Figure 1-302 during an S1-based handover or as shown at point B in
Figure 1-303 during an X2-based handover, the corresponding counter is incremented by 1
each time the source cell cancels the handover and sends a HANDOVER CANCEL message
before the preparation phase ends. However, if the handover preparation phase ends and the
handover for the UE is not finished for other abnormal reasons, the corresponding counter is
not incremented when the source cell sends a HANDOVER CANCEL message to the target
cell.
frequencies, the L.HHO.Prep.FailOut.HOCancel counter is incremented by 1.
L.HHO.IntraFreq.Prep.FailOut.HOCancel counter is incremented by 1.
L.HHO.InterFddTdd.Prep.FailOut.HOCancel counter is incremented by 1.

BTS3203E
As shown at point B in Figure 1-302 during an S1-based handover or as shown at point B in

Figure 1-303 during an X2-based handover, the corresponding counter is incremented by 1
each time the source cell sends a HANDOVER CANCEL regardless of the completion of the
handover preparation.
frequencies, the L.HHO.FailOut.HOCancel counter is incremented by 1.
L.HHO.InterFddTdd.FailOut.HOCancel counter is incremented by 1.
During the handover preparation phase of an S1- or X2-based handover, the
L.HHO.Prep.FailOut.TargetIllegal and L.HHO.IntraFreq.Prep.FailOut.TargetIllegal counters
are measured in two conditions: (1) As shown at point B in Figure 1-304, during the
preparation phase of an S1-based handover, the corresponding counter is incremented by 1
each time the source cell receives a HANDOVER COMMAND message from the MME and
then decides to cancel the handover because the message validity check fails. (2) As shown at
point B in Figure 1-305, during the handover preparation phase of an X2-based handover, the
corresponding counter is incremented by 1 each time the source cell receives a HANDOVER
REQUEST ACKNOWLEDGE message from the target cell and then decides to cancel the
handover because the message validity check fails.
frequencies, the L.HHO.Prep.FailOut.TargetIllegal counter is incremented by 1.
L.HHO.IntraFreq.Prep.FailOut.TargetIllegal counter is incremented by 1.
Figure 1-296

BTS3203E
Figure 1-297
Figure 1-298
Figure 1-299

BTS3203E
Figure 1-300
Figure 1-301
Figure 1-302

BTS3203E
Figure 1-303
Figure 1-304
Figure 1-305

BTS3203E
Formula
None
Unit
None
Related Features
L.HHO.Prep.FailOut.MME Multi-mode: None

GSM: None
UMTS: None
frequency Handover
frequency Handover
L.HHO.Prep.FailOut.NoRep Multi-mode: None

ly GSM: None
UMTS: None
frequency Handover
frequency Handover
L.HHO.Prep.FailOut.PrepFa Multi-mode: None

ilure GSM: None
UMTS: None
frequency Handover
frequency Handover

BTS3203E
L.HHO.Prep.FailOut.HOCa Multi-mode: None

ncel GSM: None
UMTS: None
frequency Handover
frequency Handover
L.HHO.FailOut.HOCancel Multi-mode: None

GSM: None
UMTS: None
frequency Handover
frequency Handover
L.HHO.InterFddTdd.Prep.F Multi-mode: None

ailOut.MME GSM: None
UMTS: None
frequency Handover

ailOut.NoReply GSM: None
UMTS: None
frequency Handover

ailOut.PrepFailure GSM: None
UMTS: None
frequency Handover

BTS3203E

ailOut.HOCancel GSM: None
UMTS: None
frequency Handover
L.HHO.InterFddTdd.FailOu Multi-mode: None

t.HOCancel GSM: None
UMTS: None
frequency Handover
L.HHO.Prep.FailOut.Other Multi-mode: None

GSM: None
UMTS: None
frequency Handover
frequency Handover

ailOut.Other GSM: None
UMTS: None
frequency Handover
L.HHO.IntraFreq.Prep.Fail Multi-mode: None

Out.MME GSM: None
UMTS: None
frequency Handover

Out.NoReply GSM: None
UMTS: None
frequency Handover

BTS3203E

Out.PrepFailure GSM: None
UMTS: None
frequency Handover

Out.HOCancel GSM: None
UMTS: None
frequency Handover
L.HHO.Prep.FailOut.TargetI Multi-mode: None

llegal GSM: None
UMTS: None
frequency Handover
frequency Handover

Out.TargetIllegal GSM: None
UMTS: None
frequency Handover
frequency Handover
L.HHO.FailOut.HOCancel. Multi-mode: None

FlowConflict GSM: None
UMTS: None
frequency Handover
LOFD-001034

BTS3203E
L.HHO.InterFddTdd.FailOu Multi-mode: None

t.HOCancel.FlowConflict GSM: None
UMTS: None
frequency Handover
LOFD-001034
1.25.8 Number of Intra-RAT Redirections

Counters

on.IntraLTE intra-RAT intra-
duplex-mode
redirections

on.IntraLTE.Co coverage-based
verage intra-RAT intra-
duplex-mode
redirections

on.IntraLTE.Lo Intra-RAT
ad Redirections
Triggered
Because of
High Load

on.InterFddTdd intra-RAT inter-
duplex-mode
redirections

on.InterFddTdd coverage-based
.Coverage intra-RAT inter-
duplex-mode
redirections

BTS3203E


on.InterFddTdd load-based
.Load intra-RAT inter-
duplex-mode
redirections

on.IntraLTE.Ul quality-based
quality intra-RAT
redirections

on.InterFddTdd quality-based
.Ulquality inter-duplex-
mode
redirections

on.InterFddTdd service-based
.Service inter-duplex-
mode
redirections

on.InterFddTdd frequency-
.FreqPri priority-based
inter-duplex-
mode
redirections

on.InterFddTdd SPID-based
.RegainHPLM inter-duplex-
N mode
redirections
back to the
HPLMN
Description
The counters measure the number of intra-RAT redirections initiated by the eNodeB. In a
redirection, the eNodeB sends an RRC Connection Release message containing the target
frequency and other information to a UE, releases the RRC connection with the source cell for
the UE, and then directs the UE to access the target cell to continue its services. If the source
and target cells work in the same duplex mode, the redirection is an intra-duplex-mode
redirection. If the source and target cells work in different duplex modes, the redirection is an
inter-duplex-mode redirection.
V10.4.0.

BTS3203E
Measurement Points
As shown at point A in Figure 1-306, the L.RRCRedirection.IntraLTE counter is incremented
by 1 each time the eNodeB sends an RRC Connection Release message to a UE and the target
frequency is an intra-duplex-mode frequency different from the source cell's frequency. In
addition, if the redirection is triggered by coverage, the L.RRCRedirection.IntraLTE.Coverage
counter is incremented by 1. If the redirection is triggered by load balancing, the
L.RRCRedirection.IntraLTE.Load counter is incremented by 1. If the handover is triggered by
uplink channel quality, the L.RRCRedirection.IntraLTE.ULquality counter is incremented by
1.
As shown at point A in Figure 1-306, the L.RRCRedirection.InterFddTdd counter is
incremented by 1 each time the eNodeB sends an RRC Connection Release message to a UE
and the target frequency is an inter-duplex-mode frequency different from the source cell's
frequency. In addition, if the redirection is triggered by coverage, the
L.RRCRedirection.InterFddTdd.Coverage counter is incremented by 1. If the redirection is
triggered by load balancing, the L.RRCRedirection.InterFddTdd.Load counter is incremented
by 1. If the redirection is triggered by uplink channel quality, the
L.RRCRedirection.InterFddTdd.ULquality counter is incremented by 1. If the redirection is
triggered by services, the L.RRCRedirection.InterFddTdd.Service counter is incremented by
1. If the redirection is triggered by frequency priority, the
L.RRCRedirection.InterFddTdd.FreqPri counter is incremented by 1. If the redirection is an
SPID-based handover to the HPLMN, the L.RRCRedirection.InterFddTdd.RegainHPLMN
Figure 1-306
Formula
None
Unit
None

BTS3203E
Related Features
L.RRCRedirection.IntraLTE Multi-mode: None

GSM: None
UMTS: None
frequency Handover

.Coverage GSM: None
UMTS: None
frequency Handover
L.RRCRedirection.InterFdd Multi-mode: None

Tdd GSM: None
UMTS: None
frequency Handover

Tdd.Coverage GSM: None
UMTS: None
frequency Handover

.Ulquality GSM: None
UMTS: None
frequency Handover

Tdd.Ulquality GSM: None
UMTS: None
frequency Handover

Tdd.Service GSM: None
UMTS: None
LTE: LBFD-00201805 Service Based Inter-
frequency Handover

BTS3203E

Tdd.FreqPri GSM: None
UMTS: None
LTE: LBFD-002018 Mobility Management
LOFD-081227 Intra-LTE Load Balancing
for Non-cosited Cells

Tdd.RegainHPLMN GSM: None
UMTS: None
SPID
1.25.9 Number of Intra-RAT Handover Initiation Failures Because

the Adjacent Cell is not on the NRT of the Source Cell
Counters
1526728398 L.IntraFreqHO. Number of BTS3203E LTE L

NoNRT intra-frequency
handover
initiation
failures because
the adjacent cell
is not on the
NRT of the
source cell
1526728399 L.InterFreqHO. Number of BTS3203E LTE L

NoNRT inter-frequency
handover
initiation
failures because
the target cell is
not configured
as a
neighboring cell
for the source
cell

BTS3203E

1526729615 L.InterFddTdd Number of BTS3203E LTE L

HO.NoNRT inter-duplex-
mode handover
initiation
failures because
the adjacent cell
is not on the
NRT of the
source cell
Description
The counters measure the number of intra-RAT handover initiation failures in a cell because
the adjacent cell is not on the neighboring relation table (NRT) of the source cell. If the source
cell and target cell work on the same frequency, the handover is an intra-frequency handover.
If the source cell and target cell work on different frequencies, the handover is an inter-
frequency handover. If the source and target cells work in different duplex modes, the
handover is an inter-duplex-mode handover.
Measurement Points
As shown at point A in Figure 1-307, Figure 1-308, the corresponding counter is
incremented by 1 each time the eNodeB receives the first measurement report from a UE in
the source cell and decides to perform a handover, but the handover initiation fails because
that the adjacent cell has the best signal quality in the first measurement report is not on the
NRT of the source cell.
Figure 1-307 shows an X2-based handover, and Figure 1-308 shows an S1-based handover.
If the eNodeB receives a measurement report on intra-frequency adjacent cells, the
L.IntraFreqHO.NoNRT counter is incremented by 1.
If the eNodeB receives a measurement report on inter-frequency adjacent cells, the
L.InterFreqHO.NoNRT counter is incremented by 1.
If the eNodeB receives a measurement report on inter-duplex-mode adjacent cells, the
L.InterFddTddHO.NoNRT counter is incremented by 1.

BTS3203E
Figure 1-307
Figure 1-308
Formula
None
Unit
None

BTS3203E
Related Features
L.IntraFreqHO.NoNRT Multi-mode: None

GSM: None
UMTS: None
frequency Handover
L.InterFreqHO.NoNRT Multi-mode: None

GSM: None
UMTS: None
LOFD-002001 Service Based Inter-
frequency Handover
LOFD-002002
Automatic Neighbour
Relation (ANR)
Inter-RAT ANR
L.InterFddTddHO.NoNRT Multi-mode: None

GSM: None
UMTS: None
frequency Handover
1.25.10 Number of Load-based Inter-Frequency Handover

Preparation Attempts
Counters
1526728526 L.HHO.InterFre Number of BTS3203E LTE L

q.Load.PrepAtt load-based
Out inter-frequency
handover
preparation
attempts

BTS3203E


q.UeNumLoad. user-number-
PrepAttOut load-based
inter-frequency
handover
preparation
attempts
Description
The counters measure the number of load-based inter-frequency handover preparation
attempts in a cell.
Measurement Points
As shown at point A in Figure 1-309, Figure 1-310, the L.HHO.InterFreq.Load.PrepAttOut
counter is incremented by 1 each time the eNodeB decides to perform an inter-frequency
handover after receiving a measurement report from a UE or the eNodeB decides to perform
an inter-frequency blind handover because of load balancing. As shown at point A in Figure
1-309, Figure 1-310, the L.HHO.InterFreq.UeNumLoad.PrepAttOut counter is incremented
by 1 each time the eNodeB decides to perform an inter-frequency handover after receiving a
measurement report from a UE or the eNodeB decides to perform an inter-frequency blind
handover because of the number of UEs. Figure 1-309 shows an X2-based inter-frequency
handover, and Figure 1-310 shows an S1-based inter-frequency handover.
Figure 1-309

BTS3203E
Figure 1-310
Formula
None
Unit
None
Related Features
L.HHO.InterFreq.Load.Prep Multi-mode: None

AttOut GSM: None
UMTS: None
Load Balancing
L.HHO.InterFreq.UeNumLo Multi-mode: None

ad.PrepAttOut GSM: None
UMTS: None
Load Balancing

BTS3203E
1.25.11 Number of Load-based Inter-Frequency Handover

Execution Attempts
Counters

q.Load.ExecAtt load-based
Out inter-frequency
handover
execution
attempts

q.UeNumLoad. user-number-
ExecAttOut load-based
inter-frequency
handover
execution
attempts
Description
The counters measure the number of load-based inter-frequency handover execution attempts
in a cell.
Measurement Points
As shown at point B in Figure 1-311, Figure 1-312, the L.HHO.InterFreq.Load.ExecAttOut
handover because of load balancing and sends an RRC Connection Reconfiguration message
to the UE. As shown at point B in Figure 1-311, Figure 1-312, the
L.HHO.InterFreq.UeNumLoad.ExecAttOut counter is incremented by 1 each time the
eNodeB decides to perform an inter-frequency handover because of the number of UEs and
sends an RRC Connection Reconfiguration message to the UE. Figure 1-311 shows an X2-
based inter-frequency handover, and Figure 1-312 shows an S1-based inter-frequency
handover.

BTS3203E
Figure 1-311
Figure 1-312
Formula
None
Unit
None

BTS3203E
Related Features
L.HHO.InterFreq.Load.Exec Multi-mode: None

AttOut GSM: None
UMTS: None
Load Balancing

ad.ExecAttOut GSM: None
UMTS: None
Load Balancing
1.25.12 Number of Successful Load-based Inter-Frequency

Handover Executions
Counters

q.Load.ExecSu successful load-
ccOut based inter-
frequency
handover
executions

q.UeNumLoad. successful user-
ExecSuccOut number-load-
based inter-
frequency
handover
executions
Description
The counters measure the number of successful load-based inter-frequency handover
executions in a cell.

BTS3203E
Measurement Points
As shown at point C in Figure 1-313, the L.HHO.InterFreq.Load.ExecSuccOut counter is
incremented by 1 each time the source eNodeB decides to perform a load-balancing-based
X2-based inter-frequency handover and the source eNodeB receives a UE CONTEXT
RELEASE message from the target eNodeB. In addition, if the handover is triggered by the
number of UEs, the L.HHO.InterFreq.UeNumLoad.ExecSuccOut counter is incremented by
1.
inter-frequency handover and the source eNodeB receives a UE CONTEXT RELEASE
message from the target eNodeB after the RRC connection is successfully reestablished to the
target eNodeB for the UE. In addition, if the handover is triggered by the number of UEs, the
L.HHO.InterFreq.UeNumLoad.ExecSuccOut counter is incremented by 1.
X2-based inter-frequency handover and an RRC connection is successfully reestablished to
the source eNodeB for the UE. In addition, if the handover is triggered by the number of UEs,
the L.HHO.InterFreq.UeNumLoad.ExecSuccOut counter is incremented by 1.
incremented by 1 each time the source eNodeB decides to perform a load-balancing-based S1-
based inter-frequency handover and receives a UE CONTEXT RELEASE message from the
MME. In addition, if the handover is triggered by the number of UEs, the
inter-frequency handover and the source eNodeB receives a UE CONTEXT RELEASE
message from the MME after the RRC connection is successfully reestablished to the target
eNodeB for the UE. In addition, if the handover is triggered by the number of UEs, the
incremented by 1 each time the source eNodeB decides to perform a load-balancing-based S1-
based inter-frequency handover and an RRC connection is successfully reestablished to the
source eNodeB for the UE. In addition, if the handover is triggered by the number of UEs, the

BTS3203E
Figure 1-313
Figure 1-314

BTS3203E
Figure 1-315
Figure 1-316

BTS3203E
Figure 1-317

BTS3203E
Figure 1-318
Formula
None
Unit
None
Related Features
L.HHO.InterFreq.Load.Exec Multi-mode: None

SuccOut GSM: None
UMTS: None
Load Balancing

BTS3203E

ad.ExecSuccOut GSM: None
UMTS: None
Load Balancing
1.25.13 Number of Inter-Frequency Outgoing Handover Attempts

Triggered for UEs to Go back to the HPLMN
Counters

q.RegainHPLM inter-frequency
N.PrepAttOut outgoing
handover
attempts
triggered for
UEs to go back
to the HPLMN
Description
The counter measures the number of inter-frequency outgoing handover attempts triggered for
UEs to go back to the HPLMN in a cell. In national roaming scenarios, if the handovers back
to the HPLMN for UEs is enabled, a roaming UE can be handed over to the HPLMN when
this UE moves back to the HPLMN.
Measurement Points
As shown at point A in Figure 1-319, during an X2-based handover the
L.HHO.InterFreq.RegainHPLMN.PrepAttOut counter is incremented by 1 each time the
source eNodeB determines to perform an X2-based handover after the source eNodeB
receives a measurement report from the UE. The corresponding measurement control message
is triggered for the UE to go back to the HPLMN.
As shown at point A in Figure 1-320, during an S1-based handover the
L.HHO.InterFreq.RegainHPLMN.PrepAttOut counter is incremented by 1 each time the
source eNodeB determines to perform an S1-based handover after the source eNodeB
receives a measurement report from the UE. The corresponding measurement control message
is triggered for the UE to go back to the HPLMN.

BTS3203E
Figure 1-319
Figure 1-320
Formula
None
Unit
None

BTS3203E
Related Features
L.HHO.InterFreq.RegainHP Multi-mode: None

LMN.PrepAttOut GSM: None
UMTS: None
SPID
1.25.14 Number of Inter-Frequency Outgoing Handover

Executions Triggered for UEs to Go back to the HPLMN
Counters

q.RegainHPLM inter-frequency
N.ExecAttOut outgoing
handover
executions
triggered for
UEs to go back
to the HPLMN
Description
The counter measures the number of inter-frequency outgoing handover executions triggered
for UEs to go back to the HPLMN in a cell. In national roaming scenarios, if the handovers
back to the HPLMN for UEs is enabled, a roaming UE can be handed over to the HPLMN
when this UE moves back to the HPLMN.
Measurement Points
As shown at point B in Figure 1-321, during an X2-based handover the
L.HHO.InterFreq.RegainHPLMN.ExecAttOut counter is incremented by 1 each time the
source eNodeB sends an RRC Connection Reconfiguration message to the UE after the source
eNodeB receives a HANDOVER REQUEST ACKNOWLEDGE message from the target
eNodeB.
As shown at point B in Figure 1-322, during an S1-based handover the

L.HHO.InterFreq.RegainHPLMN.ExecAttOut counter is incremented by 1 each time the
source eNodeB sends an RRC Connection Reconfiguration message to the UE after the source
eNodeB receives a HANDOVER COMMAND from the MME.

BTS3203E
Figure 1-321
Figure 1-322
Formula
None
Unit
None

BTS3203E
Related Features

LMN.ExecAttOut GSM: None
UMTS: None
SPID
1.25.15 Number of Successful Inter-Frequency Outgoing

Handovers Triggered for UEs to Go Back to the HPLMN
Counters

q.RegainHPLM successful inter-
N.ExecSuccOut frequency
outgoing
handovers
triggered for
UEs to go back
to the HPLMN
Description
The counter measures the number of successful inter-frequency outgoing handovers triggered
for UEs to go back to the HPLMN in a cell. In national roaming scenarios, if the handovers
back to the HPLMN for UEs is enabled, a roaming UE can be handed over to the HPLMN
when this UE moves back to the HPLMN.
Measurement Points
As shown at point C in Figure 1-323, during an X2-based handover the
L.HHO.InterFreq.RegainHPLMN.ExecSuccOut counter is incremented by 1 each time data in
the buffer is forwarded during the handover after the source eNodeB receives a UE
CONTEXT RELEASE message from the target eNodeB.
is successfully reestablished to the target eNodeB for the UE, the

BTS3203E
is successfully reestablished to the source eNodeB for the UE, the
L.HHO.InterFreq.RegainHPLMN.ExecSuccOut counter is incremented by 1 each time.
As shown at point C in Figure 1-325, during an S1-based handover the
CONTEXT RELEASE COMMAND message from the MME.
is successfully reestablished to the target eNodeB for the UE, the
is successfully reestablished to the source eNodeB for the UE, the
L.HHO.InterFreq.RegainHPLMN.ExecSuccOut counter is incremented by 1 each time.
Figure 1-323

BTS3203E
Figure 1-324
Figure 1-325

BTS3203E
Figure 1-326

BTS3203E
Figure 1-327

BTS3203E
Figure 1-328
Formula
None
Unit
None
Related Features

LMN.ExecSuccOut GSM: None
UMTS: None
SPID

BTS3203E
1.25.16 Number of Intra-Frequency Handover Execution Attempts

Triggered for UEs that do not transmit or receive data
Counters

q.NoData.Exec intra-frequency
AttOut handover
execution
attempts
triggered for
UEs that do not
transmit or
receive data
Description
The counter measures the number of intra-frequency handover execution attempts triggered
for UEs that do not transmit or receive data.
Measurement Points
"This counter is measured in a handover where the source cell and the target cell work on the
same frequency.
As shown at point B in Figure 1-329, during an X2-based handover that the UE does not
transmit or receive data, the L.HHO.IntraFreq.NoData.ExecAttOut counter is incremented by
1 each time the source eNodeB sends an RRC Connection Reconfiguration message to the UE
after the source eNodeB receives a HANDOVER REQUEST ACKNOWLEDGE message
from the target eNodeB.
L.HHO.IntraFreq.NoData.ExecAttOut counter is incremented by 1 each time the source
eNodeB sends an RRC Connection Reconfiguration message to the UE and the eNodeB
determines that the UE does not transmit or receive data after the source eNodeB receives a
HANDOVER COMMAND message from the MME."

BTS3203E
Figure 1-329
Figure 1-330
Formula
None
Unit
None

BTS3203E
Related Features
L.HHO.IntraFreq.NoData.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
Dynamic DRX
1.25.17 Number of Successful Intra-Frequency Handover

Executions Triggered for UEs that do not transmit or receive data
Counters

q.NoData.Exec successful intra-
SuccOut frequency
handover
executions
triggered for
UEs that do not
transmit or
receive data
Description
The counter measures the number of successful intra-frequency handover executions triggered
Measurement Points
same frequency.
As shown at point C in Figure 1-331, during an X2-based handoverthat the UE does not
transmit or receive data, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented
by 1 each time the source eNodeB receives a UE CONTEXT RELEASE message from the
target eNodeB.
As shown at point C in Figure 1-332, during an X2-based inter-eNodeB handover that the UE
does not transmit or receive data, after an RRC connection is successfully reestablished to the
target eNodeB for the UE, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented

BTS3203E
target eNodeB.
As shown at point C in Figure 1-335, during an X2-based inter-eNodeB handover that the UE
does not transmit or receive data, after an RRC connection is successfully reestablished to the
source eNodeB for the UE, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is
As shown at point C in Figure 1-333, during an S1-based handover that the UE does not
transmit or receive data, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented
by 1 each time the source eNodeB receives a UE CONTEXT RELEASE COMMAND from
the MME.
transmit or receive data, after an RRC connection is successfully reestablished to the target
eNodeB for the UE, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented by 1
each time the source eNodeB receives a UE CONTEXT RELEASE COMMAND message
from the MME.
transmit or receive data, after an RRC connection is successfully reestablished to the source
eNodeB for the UE, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented by 1
each time."
Figure 1-331

BTS3203E
Figure 1-332
Figure 1-333

BTS3203E
Figure 1-334

BTS3203E
Figure 1-335

BTS3203E
Figure 1-336
Formula
None
Unit
None
Related Features
L.HHO.IntraFreq.NoData.E Multi-mode: None

UMTS: None
Dynamic DRX

BTS3203E
1.25.18 Number of Inter-Frequency Handover Execution Attempts

Triggered for UEs That Do not Transmit or Receive Data
Counters

q.NoData.Exec inter-frequency
AttOut handover
execution
attempts
triggered for
UEs that do not
transmit or
receive data
Description
The counter measures the number of inter-frequency handover execution attempts triggered
Measurement Points
different frequency.
As shown at point B in Figure 1-337, during an X2-based handover that the UE does not
transmit or receive data, the L.HHO.InterFreq.NoData.ExecAttOut counter is incremented by
1 each time the source eNodeB sends an RRC Connection Reconfiguration message to the UE
after the source eNodeB receives a HANDOVER REQUEST ACKNOWLEDGE message
L.HHO.InterFreq.NoData.ExecAttOut counter is incremented by 1 each time the source
eNodeB sends an RRC Connection Reconfiguration message to the UE and the eNodeB
determines that the UE does not transmit or receive data after the source eNodeB receives a
HANDOVER COMMAND message from the MME."

BTS3203E
Figure 1-337
Figure 1-338
Formula
None
Unit
None

BTS3203E
Related Features
L.HHO.InterFreq.NoData.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
frequency Handover
Dynamic DRX
1.25.19 Number of Successful Inter-Frequency Handover

Executions Triggered for UEs That Do not Transmit or Receive
Data
Counters

q.NoData.Exec successful inter-
SuccOut frequency
handover
executions
triggered for
UEs that do not
transmit or
receive data
Description
The counter measures the number of successful inter-frequency handover executions triggered
Measurement Points
"This counter is measured in a handover where the source cell and the target cell work on
different frequencies.
As shown at point C in Figure 1-339, during an X2-based handover that the UE does not
transmit or receive data, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented
target eNodeB.

BTS3203E
transmit or receive data, after an RRC connection is successfully reestablished to the target
eNodeB for the UE, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented by 1
each time the source eNodeB receives a UE CONTEXT RELEASE message from the target
eNodeB.
transmit or receive data, after an RRC connection is successfully reestablished to the source
each time.
transmit or receive data, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented
by 1 each time the source eNodeB receives a UE CONTEXT RELEASE COMMAND from
the MME.
transmit or receive data, after an RRC connection is successfully reestablished to target
each time the source eNodeB receives a UE CONTEXT RELEASE COMMAND message
from the MME.
transmit or receive data, after an RRC connection is successfully reestablished to source
each time."
Figure 1-339

BTS3203E
Figure 1-340
Figure 1-341

BTS3203E
Figure 1-342

BTS3203E
Figure 1-343

BTS3203E
Figure 1-344
Formula
None
Unit
None
Related Features
L.HHO.InterFreq.NoData.E Multi-mode: None

UMTS: None
frequency Handover
Dynamic DRX

BTS3203E

the eNodeB from the MME During S1-based Outgoing Handover
Executions
Counters
1526728883 L.HHO.S1.Intra Number of BTS3203E LTE L

Freq.MMEAbn responses for
ormRsp abnormal
causes received
by the eNodeB
from the MME
during S1-based
outgoing intra-
frequency
handover
executions in a
cell
1526728884 L.HHO.S1.Inter Number of BTS3203E LTE L

Freq.MMEAbn responses for
ormRsp abnormal
causes received
by the eNodeB
from the MME
during S1-based
outgoing inter-
frequency
handover
executions in a
cell
1526729616 L.HHO.S1.Inter Number of BTS3203E LTE L

FddTdd.MMEA responses for
bnormRsp abnormal
causes received
by the eNodeB
from the MME
during S1-based
inter-duplex-
mode outgoing
handover
executions in a
cell
Description
from the MME during S1-based outgoing handover executions. If the source and target cells

BTS3203E
work on the same frequency in the same duplex mode, the handover is an intra-frequency
handover. If the source and target cells work on different frequencies in the same duplex
mode, the handover is an inter-frequency handover. If the source and target cells work in
Measurement Points
is incremented by 1 each time the source eNodeB receives a UE CONTEXT RELEASE
"Normal Release". The counters are measured as follows:
L.HHO.S1.IntraFreq.MMEAbnormRsp counter is incremented by 1.
If the source and target cells work on different frequencies, the

L.HHO.S1.InterFreq.MMEAbnormRsp counter is incremented by 1.
L.HHO.S1.InterFddTdd.MMEAbnormRsp counter is incremented by 1.
Figure 1-345
Formula
None
Unit
None

BTS3203E
Related Features
L.HHO.S1.IntraFreq.MME Multi-mode: None

AbnormRsp GSM: None
UMTS: None
frequency Handover
L.HHO.S1.InterFreq.MME Multi-mode: None

AbnormRsp GSM: None
UMTS: None
frequency Handover
L.HHO.S1.InterFddTdd.M Multi-mode: None

UMTS: None
frequency Handover

BTS3203E

Where RRC Connections Are Reestablished to the Source Cell for
UEs in a Cell
Counters

B.IntraFreq.Suc successful inter-
c.ReEst2Src eNodeB intra-
frequency
outgoing
handovers
where RRC
connections are
reestablished to
the source cell
for UEs in a
cell

B.InterFreq.Suc successful inter-
c.ReEst2Src eNodeB inter-
frequency
outgoing
handovers
where RRC
connections are
reestablished to
the source cell
for UEs in a
cell

Succ.ReEst2Src eNodeB inter-
duplex-mode
outgoing
handovers
where RRC
connections are
reestablished to
the source cell
for UEs in a
cell
Description
The counters measure the number of successful inter-eNodeB outgoing handovers where RRC
connections are reestablished to the source cell for UEs in a cell. If the source and target cells

BTS3203E
work on the same frequency in the same duplex mode, the handover is an intra-frequency
handover. If the source and target cells work on different frequencies in the same duplex
mode, the handover is an inter-frequency handover. If the source and target cells work in
Measurement Points
As shown at point C in Figure 1-346, during an X2-based handover, the corresponding
counter is incremented by 1 each time the source cell receives an RRC Connection
Reestablishment Complete message from the UE. The counters are measured as follows:
L.HHO.IntereNB.IntraFreq.Succ.ReEst2Src counter is incremented by 1.
L.HHO.IntereNB.InterFreq.Succ.ReEst2Src counter is incremented by 1.
L.HHO.IntereNB.InterFddTdd.Succ.ReEst2Src counter is incremented by 1.
counter is incremented by 1 each time the source cell receives an RRC Connection
Reestablishment Complete message from the UE. The counters are measured as follows:
L.HHO.IntereNB.IntraFreq.Succ.ReEst2Src counter is incremented by 1.
L.HHO.IntereNB.InterFreq.Succ.ReEst2Src counter is incremented by 1.
L.HHO.IntereNB.InterFddTdd.Succ.ReEst2Src counter is incremented by 1.

BTS3203E
Figure 1-346

BTS3203E
Figure 1-347
Formula
None
Unit
None
Related Features

Succ.ReEst2Src GSM: None
UMTS: None
frequency Handover

BTS3203E

Succ.ReEst2Src GSM: None
UMTS: None
frequency Handover

dd.Succ.ReEst2Src GSM: None
UMTS: None
frequency Handover
1.25.22 Number of Successful Blind Outgoing Handovers Where

RRC Connections Are Reestablished to the Source Cell for UEs in
a cell
Counters

O.Succ.ReEst2 successful intra-
Src duplex-mode
blind outgoing
handovers
where RRC
connections are
reestablished to
the source cell
for UEs in a
cell

BTS3203E


dTdd.BlindHO. successful inter-
Succ.ReEst2Src duplex-mode
blind outgoing
handovers
where RRC
connections are
reestablished to
the source cell
for UEs in a
cell
Description
The counters measure the number of successful blind outgoing handovers where RRC
connections are reestablished to the source cell for UEs in a cell. Not triggered on the basis of
UE measurement reports, the blind handover is a handover in which the eNodeB specifies the
target cell for the UE. In specific networking scenarios, the eNodeB performs a blind
handover to actively hand over the UE from the source cell. If the source and target cells work
in the same duplex mode, the blind handover is an intra-duplex-mode blind handover. If the
source and target cells work in different duplex modes, the blind handover is an inter-duplex-
mode blind handover.
Measurement Points
As shown at point C in Figure 1-348, the L.HHO.BlindHO.Succ.ReEst2Src or
L.HHO.InterFddTdd.BlindHO.Succ.ReEst2Src counter is incremented by 1 each time the
eNodeB decides to perform an X2-based blind handover and the source cell receives an RRC
Connection Reestablishment Complete message from the UE. If the source and target cells
work in the same duplex mode, the L.HHO.BlindHO.Succ.ReEst2Src counter is incremented
by 1. If the source and target cells work in different duplex modes, the
L.HHO.InterFddTdd.BlindHO.Succ.ReEst2Src counter is incremented by 1.
As shown at point C in Figure 1-349, the L.HHO.BlindHO.Succ.ReEst2Src or
L.HHO.InterFddTdd.BlindHO.Succ.ReEst2Src counter is incremented by 1 each time the
eNodeB decides to perform an S1-based blind handover and the source cell receives an RRC
Connection Reestablishment Complete message from the UE. If the source and target cells
work in the same duplex mode, the L.HHO.BlindHO.Succ.ReEst2Src counter is incremented
by 1. If the source and target cells work in different duplex modes, the
L.HHO.InterFddTdd.BlindHO.Succ.ReEst2Src counter is incremented by 1.

BTS3203E
Figure 1-348

BTS3203E
Figure 1-349
Formula
None
Unit
None
Related Features
L.HHO.BlindHO.Succ.ReEs Multi-mode: None

t2Src GSM: None
UMTS: None
frequency Handover
frequency Handover

BTS3203E

O.Succ.ReEst2Src GSM: None
UMTS: None
frequency Handover
1.25.23 Number of Coverage-based Inter-Frequency Handover

Counters

q.Coverage.Pre coverage-based
handover
preparation
attempts
Description
The counter measures the number of coverage-based inter-frequency handover preparation
attempts in a cell.
Measurement Points
As shown at point A in Figure 1-350, Figure 1-351, the
L.HHO.InterFreq.Coverage.PrepAttOut counter is incremented by 1 each time the eNodeB
decides to perform an inter-frequency handover after receiving a measurement report from the
UE triggered by weak coverage. Figure 1-350 shows an X2-based inter-frequency handover,
and Figure 1-351 shows an S1-based inter-frequency handover.

BTS3203E
Figure 1-350
Figure 1-351
Formula
None
Unit
None

BTS3203E
Related Features
L.HHO.InterFreq.Coverage. Multi-mode: None

UMTS: None
frequency Handover
1.25.24 Number of Coverage-based Inter-Frequency Handover

Execution Attempts
Counters

q.Coverage.Exe coverage-based
cAttOut inter-frequency
handover
execution
attempts
Description
The counter measures the number of coverage-based inter-frequency handover execution
attempts in a cell.
Measurement Points
As shown at point B in Figure 1-352, Figure 1-353, the
L.HHO.InterFreq.Coverage.ExecAttOut counter is incremented by 1 each time when the
eNodeB decides to perform an inter-frequency handover triggered by weak coverage and send
RRC Connection Reconfiguration to UE. Figure 1-352 shows an X2-based inter-frequency

BTS3203E
Figure 1-352
Figure 1-353
Formula
None
Unit
None

BTS3203E
Related Features

UMTS: None
frequency Handover
1.25.25 Number of Successful Coverage-based Inter-Frequency

Handovers
Counters

q.Coverage.Exe successful
cSuccOut coverage-based
inter-frequency
handovers
Description
The counter measures the number of successful coverage-based inter-frequency handovers in
a cell.
Measurement Points
As shown at point C in Figure 1-354, the L.HHO.InterFreq.Coverage.ExecSuccOut counter is
incremented by 1 each time the eNodeB decides to perform an X2-based handover because of
poor coverage and the source eNodeB receives a UE CONTEXT RELEASE message from
the target eNodeB.
L.HHO.InterFreq.Coverage.ExecSuccOut counter is incremented by 1 each time the eNodeB
decides to perform an X2-based handover because of poor coverage and the source eNodeB
receives a UE CONTEXT RELEASE message from the target eNodeB after an RRC
connection is successfully reestablished to the target eNodeB for the UE.
decides to perform an X2-based handover because of poor coverage and after an RRC
connection is successfully reestablished to the source eNodeB for the UE.
As shown at point C in Figure 1-357, the L.HHO.InterFreq.Coverage.ExecSuccOut counter is
incremented by 1 each time the eNodeB decides to perform an S1-based handover because of

BTS3203E
poor coverage and the source eNodeB receives a UE CONTEXT RELEASE message from
MME.
decides to perform an S1-based handover because of poor coverage and the source eNodeB
receives a UE CONTEXT RELEASE message from MME after an RRC connection is
successfully reestablished to the target eNodeB for the UE.
decides to perform an S1-based handover because of poor coverage and after an RRC
Figure 1-354

BTS3203E
Figure 1-355

BTS3203E
Figure 1-356
Figure 1-357

BTS3203E
Figure 1-358

BTS3203E
Figure 1-359
Formula
None
Unit
None
Related Features

UMTS: None
frequency Handover

BTS3203E
1.25.26 Inter-eNodeB Handover Time in a Cell

Counters
1526729430 L.HHO.IntereN Average BTS3203E LTE L

B.S1.TimeAvg duration of S1-
based intra-
duplex-mode
outgoing
handovers in a
cell
1526729431 L.HHO.IntereN Average BTS3203E LTE L

B.X2.TimeAvg duration of X2-
based intra-
duplex-mode
outgoing
handovers in a
cell
1526729605 L.HHO.InterFd Average BTS3203E LTE L

dTdd.IntereNB. duration of S1-
S1.TimeAvg based inter-
duplex-mode
outgoing
handovers in a
cell
1526729606 L.HHO.InterFd Average BTS3203E LTE L

dTdd.IntereNB. duration of X2-
X2.TimeAvg based inter-
duplex-mode
outgoing
handovers in a
cell
Description
The counters measure the time of a successful S1-based or X2-based inter-eNodeB handover
in a cell.
Measurement Points
As shown in Figure 1-360, the duration of an S1-based handover equals the interval between
the time the source eNodeB sends a HANDOVER REQUIRED message to the MME and the
time the source eNodeB receives a UE CONTEXT RELEASE COMMAND message from
the MME. At the end of a measurement period, the average of these sampling results for S1-
based intra-duplex-mode handovers is used as the value of the L.HHO.IntereNB.S1.TimeAvg
counter, and the average of these sampling results for S1-based inter-duplex-mode handovers

BTS3203E
is used as the value of the L.HHO.InterFddTdd.IntereNB.S1.TimeAvg counter. During a

As shown in Figure 1-361, the duration of an X2-based handover equals the interval between
the time the source eNodeB sends a HANDOVER REQUEST message to the target eNodeB
and the time the source eNodeB receives a UE CONTEXT RELEASE message from the
target eNodeB. At the end of a measurement period, the average of these sampling results for
X2-based intra-duplex-mode handovers is used as the value of the
L.HHO.IntereNB.X2.TimeAvg counter, and the average of these sampling results for X2-
based inter-duplex-mode handovers is used as the value of the
L.HHO.InterFddTdd.IntereNB.X2.TimeAvg counter.
Figure 1-360

BTS3203E
Figure 1-361
Formula
None
Unit
ms
Related Features
L.HHO.IntereNB.S1.TimeA Multi-mode: None

vg GSM: None
UMTS: None
frequency Handover
frequency Handover

BTS3203E
L.HHO.IntereNB.X2.TimeA Multi-mode: None

vg GSM: None
UMTS: None
frequency Handover
frequency Handover
L.HHO.InterFddTdd.Intere Multi-mode: None

NB.S1.TimeAvg GSM: None
UMTS: None
frequency Handover
L.HHO.InterFddTdd.Intere Multi-mode: None

NB.X2.TimeAvg GSM: None
UMTS: None
frequency Handover
1.25.27 Number of Service-based Inter-Frequency Handover

Counters

q.Service.Prep service-based
handover
preparation
attempts

BTS3203E
Description
The counter measures the number of service-based inter-frequency handover preparation
attempts in a cell.
Measurement Points
As shown at point A in Figure 1-362, Figure 1-363,the L.HHO.InterFreq.Service.PrepAttOut
handover after receiving a measurement report from the UE triggered because of services.
Figure 1-362 shows an X2-based inter-frequency handover, and Figure 1-363 shows an S1-
based inter-frequency handover.
Figure 1-362

BTS3203E
Figure 1-363
Formula
None
Unit
None
Related Features
L.HHO.InterFreq.Service.Pr Multi-mode: None

epAttOut GSM: None
UMTS: None
frequency Handover

BTS3203E
1.25.28 Number of Service-based Inter-Frequency Handover

Execution Attempts
Counters

q.Service.Exec service-based
handover
execution
attempts
Description
The counter measures the number of service-based inter-frequency handover execution
attempts in a cell.
Measurement Points
L.HHO.InterFreq.Service.ExecAttOut counter is incremented by 1 each time the eNodeB
decides to perform an inter-frequency handover triggered because of services and sends an
RRC Connection Reconfiguration message to the UE. Figure 1-364 shows an X2-based inter-
frequency handover, and Figure 1-365 shows an S1-based inter-frequency handover.
Figure 1-364

BTS3203E
Figure 1-365
Formula
None
Unit
None
Related Features
L.HHO.InterFreq.Service.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
frequency Handover

BTS3203E
1.25.29 Number of Successful Service-based Inter-Frequency

Handover Executions
Counters

q.Service.Exec successful
inter-frequency
handover
executions
Description
The counter measures the number of successful service-based inter-frequency handover
Measurement Points
As shown at point C in Figure 1-366, during a service-based X2-based handover, the
L.HHO.InterFreq.Service.ExecSuccOut counter is incremented by 1 each time data in the
buffer is forwarded after the source eNodeB receives a UE CONTEXT RELEASE message
As shown at point C in Figure 1-367, during a service-based X2-based handover, after an

RRC connection is successfully reestablished to the target eNodeB for the UE, the
As shown at point C in Figure 1-370, during a service-based X2-based handover, the

L.HHO.InterFreq.Service.ExecSuccOut counter is incremented by 1 each time an RRC
As shown at point C in Figure 1-368, during a service-based S1-based handover, the

buffer is forwarded after the source eNodeB receives a UE CONTEXT RELEASE
COMMAND message from the MME.
As shown at point C in Figure 1-369, during a service-based S1-based handover, after an

RRC connection is successfully reestablished to the target eNodeB for the UE, the
As shown at point C in Figure 1-371, during a service-based S1-based handover, the

L.HHO.InterFreq.Service.ExecSuccOut counter is incremented by 1 each time an RRC

BTS3203E
Figure 1-366
Figure 1-367

BTS3203E
Figure 1-368
Figure 1-369

BTS3203E
Figure 1-370

BTS3203E
Figure 1-371
Formula
None
Unit
None
Related Features
L.HHO.InterFreq.Service.E Multi-mode: None

UMTS: None
frequency Handover

BTS3203E
1.25.30 Number of Frequency-Priority-based Inter-Frequency

Handover Preparation Attempts
Counters

q.FreqPri.Prep frequency-
AttOut priority-based
inter-frequency
handover
preparation
attempts
Description
The counter measures the number of frequency-priority-based inter-frequency handover
preparation attempts in a cell.
Measurement Points
L.HHO.InterFreq.FreqPri.PrepAttOut counter is incremented by 1 each time the eNodeB
decides to perform an inter-frequency blind handover triggered because of the frequency
priority or the eNodeB receives a measurement report from the UE triggered because of the
frequency priority and decides to perform an inter-frequency handover. Figure 1-372 shows
an X2-based inter-frequency handover, and Figure 1-373 shows an S1-based inter-frequency
handover.

BTS3203E
Figure 1-372
Figure 1-373
Formula
None
Unit
None

BTS3203E
Related Features
L.HHO.InterFreq.FreqPri.Pr Multi-mode: None

epAttOut GSM: None
UMTS: None
1.25.31 Number of Frequency-Priority-based Inter-Frequency

Handover Execution Attempts
Counters

q.FreqPri.Exec frequency-
AttOut priority-based
inter-frequency
handover
execution
attempts
Description
The counter measures the number of frequency-priority-based inter-frequency handover
execution attempts in a cell.
Measurement Points
L.HHO.InterFreq.FreqPri.ExecAttOut counter is incremented by 1 each time the eNodeB
decides to perform an inter-frequency handover triggered because of the frequency priority
and sends an RRC Connection Reconfiguration message to the UE. Figure 1-374 shows an
X2-based inter-frequency handover, and Figure 1-375 shows an S1-based inter-frequency
handover.

BTS3203E
Figure 1-374
Figure 1-375
Formula
None
Unit
None

BTS3203E
Related Features
L.HHO.InterFreq.FreqPri.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
1.25.32 Number of Successful Frequency-Priority-based Inter-

Frequency Handover Executions
Counters

q.FreqPri.Exec successful
SuccOut frequency-
priority-based
inter-frequency
handover
executions
Description
The counter measures the number of successful frequency-priority-based inter-frequency
handover executions in a cell.
Measurement Points
As shown at point C in Figure 1-376, during a frequency-priority-based X2-based handover,
the L.HHO.InterFreq.FreqPri.ExecSuccOut counter is incremented by 1 each time data in the
the L.HHO.InterFreq.FreqPri.ExecSuccOut counter is incremented by 1 each time an RRC
after an RRC connection is successfully reestablished to the target eNodeB for the UE, the
L.HHO.InterFreq.FreqPri.ExecSuccOut counter is incremented by 1 each time data in the
As shown at point C in Figure 1-378, during a frequency-priority-based S1-based handover,
the L.HHO.InterFreq.FreqPri.ExecSuccOut counter is incremented by 1 each time data in the

BTS3203E

after an RRC connection is successfully reestablished to the target eNodeB for the UE, the
L.HHO.InterFreq.FreqPri.ExecSuccOut counter is incremented by 1 each time data in the
the L.HHO.InterFreq.FreqPri.ExecSuccOut counter is incremented by 1 each time an RRC
Figure 1-376

BTS3203E
Figure 1-377
Figure 1-378

BTS3203E
Figure 1-379

BTS3203E
Figure 1-380

BTS3203E
Figure 1-381
Formula
None
Unit
None
Related Features
L.HHO.InterFreq.FreqPri.E Multi-mode: None

UMTS: None

BTS3203E
1.25.33 Number of Inter-eNodeB Outgoing Handover Attempts

for UEs Performing Voice Services in a Cell
Counters

B.IntraFreq.Pre inter-eNodeB
pAttOut.VoIP intra-frequency
outgoing
handover
attempts for
UEs performing
voice services
in a cell

B.InterFreq.Pre inter-eNodeB
pAttOut.VoIP inter-frequency
outgoing
handover
attempts for
UEs performing
voice services
in a cell

PrepAttOut.VoI inter-duplex-
P mode outgoing
handover
attempts for
UEs performing
voice services
in a cell
Description
The counters measure the number of inter-eNodeB intra-frequency outgoing handover
attempts, the number of inter-eNodeB inter-frequency outgoing handover attempts, and the
number of inter-eNodeB inter-duplex-mode outgoing handover attempts for UEs performing
voice services in a cell. If the source cell and the target cell work on the same frequency and
in the same duplex mode, the handover is an intra-frequency handover. If the source cell and
the target cell work on different frequencies and in the same duplex mode, the handover is an
inter-frequency handover. If the source cell and the target cell work in different duplex modes,
the handover is an inter-duplex-mode handover.

BTS3203E
Measurement Points
As shown at point A in Figure 1-382, during an X2-based handover, the corresponding
(1) The source eNodeB decides to perform an X2-based blind handover or decides to perform
an X2-based handover after the source cell receives a measurement report from the UE.
(2) The source eNodeB determines that the UE is performing services with the QCI of 1.
As shown at point A in Figure 1-383, during an S1-based handover, the corresponding
(1) The source eNodeB decides to perform an S1-based blind handover or decides to perform
an S1-based handover after the source cell receives a measurement report from the UE.
(2) The source eNodeB determines that the UE is performing services with the QCI of 1.
L.HHO.IntereNB.IntraFreq.PrepAttOut.VoIP counter is incremented by 1.
L.HHO.IntereNB.InterFreq.PrepAttOut.VoIP counter is incremented by 1.
L.HHO.IntereNB.InterFddTdd.PrepAttOut.VoIP counter is incremented by 1.
Figure 1-382

BTS3203E
Figure 1-383
Formula
None
Unit
None
Related Features

PrepAttOut.VoIP GSM: None
UMTS: None
frequency Handover

PrepAttOut.VoIP GSM: None
UMTS: None
frequency Handover

BTS3203E

dd.PrepAttOut.VoIP GSM: None
UMTS: None
frequency Handover
1.25.34 Number of Inter-eNodeB Outgoing Handover Executions

Counters

B.IntraFreq.Exe inter-eNodeB
cAttOut.VoIP intra-frequency
outgoing
handover
executions for
UEs performing
voice services
in a cell

B.InterFreq.Exe inter-eNodeB
cAttOut.VoIP inter-frequency
outgoing
handover
executions for
UEs performing
voice services
in a cell

ExecAttOut.VoI inter-duplex-
P mode outgoing
handover
executions for
UEs performing
voice services
in a cell

BTS3203E
Description
The counters measure the number of inter-eNodeB intra-frequency outgoing handover
executions, the number of inter-eNodeB inter-frequency outgoing handover executions, and
the number of inter-eNodeB inter-duplex-mode outgoing handover executions for UEs
performing voice services in a cell. If the source cell and the target cell work on the same
frequency and in the same duplex mode, the handover is an intra-frequency handover. If the
source cell and the target cell work on different frequencies and in the same duplex mode, the
handover is an inter-frequency handover. If the source cell and the target cell work in different
duplex modes, the handover is an inter-duplex-mode handover.
Measurement Points
As shown at point B in Figure 1-384, during an X2-based handover, the corresponding
Reconfiguration message to the UE after receiving a HANDOVER REQUEST
ACKNOWLEDGE message from the target eNodeB and source eNodeB determines that the
UE is performing services with the QCI of 1.
As shown at point B in Figure 1-385, during an S1-based handover, the corresponding
Reconfiguration message to the UE after receiving a HANDOVER COMMAND message
from the MME and source eNodeB determines that the UE is performing services with the
QCI of 1.
L.HHO.IntereNB.IntraFreq.ExecAttOut.VoIP counter is incremented by 1.
L.HHO.IntereNB.InterFreq.ExecAttOut.VoIP counter is incremented by 1.
L.HHO.IntereNB.InterFddTdd.ExecAttOut.VoIP counter is incremented by 1.

BTS3203E
Figure 1-384
Figure 1-385
Formula
None
Unit
None

BTS3203E
Related Features

ExecAttOut.VoIP GSM: None
UMTS: None
frequency Handover

ExecAttOut.VoIP GSM: None
UMTS: None
frequency Handover

dd.ExecAttOut.VoIP GSM: None
UMTS: None
frequency Handover

Counters

B.IntraFreq.Exe successful inter-
cSuccOut.VoIP eNodeB intra-
frequency
outgoing
handovers for
UEs performing
voice services
in a cell

BTS3203E


B.InterFreq.Exe successful inter-
cSuccOut.VoIP eNodeB inter-
frequency
outgoing
handovers for
UEs performing
voice services
in a cell

ExecSuccOut.V eNodeB inter-
oIP duplex-mode
outgoing
handovers for
UEs performing
voice services
in a cell
Description
The counters measure the number of successful inter-eNodeB intra-frequency outgoing
handovers, the number of successful inter-eNodeB inter-frequency outgoing handovers, and
the number of successful inter-eNodeB inter-duplex-mode outgoing handovers for UEs
performing voice services in a cell. If the source cell and the target cell work on the same
frequency and in the same duplex mode, the handover is an intra-frequency handover. If the
source cell and the target cell work on different frequencies and in the same duplex mode, the
handover is an inter-frequency handover. If the source cell and the target cell work in different
duplex modes, the handover is an inter-duplex-mode handover.
Measurement Points
Figure 1-386 shows an X2-based handover, Figure 1-387 shows that the RRC connection is
successfully reestablished to the target eNodeB for a UE during an X2-based handover,
Figure 1-388 shows an S1-based handover, Figure 1-389 shows that the RRC connection is
successfully reestablished to the target eNodeB for a UE during an S1-based handover,
Figure 1-390 shows that the RRC connection is successfully reestablished to the source
eNodeB for a UE during an X2-based handover, Figure 1-391 shows that the RRC connection
is successfully reestablished to the source eNodeB for a UE during an S1-based handover.
counter is incremented by 1 each time data in the buffer is forwarded after the source eNodeB
receives a UE CONTEXT RELEASE message from the target eNodeB and the source
eNodeB determines that the UE is performing services with the QCI of 1.
As shown at point C in Figure 1-387, during an X2-based handover, after an RRC connection
incremented by 1 each time data in the buffer is forwarded after the source eNodeB receives a

BTS3203E
UE CONTEXT RELEASE message from the target eNodeB and the source eNodeB
determines that the UE is performing services with the QCI of 1.
source eNodeB for the UE and the source eNodeB determines that the UE is performing
services with the QCI of 1.
counter is incremented by 1 each time data in the buffer is forwarded after the source eNodeB
receives a UE CONTEXT RELEASE COMMAND message from the MME and the source
eNodeB determines that the UE is performing services with the QCI of 1.
As shown at point C in Figure 1-389, during an S1-based handover, after an RRC connection
incremented by 1 each time data in the buffer is forwarded after the source eNodeB receives a
UE CONTEXT RELEASE COMMAND message from the MME and the source eNodeB
determines that the UE is performing services with the QCI of 1.
source eNodeB for the UE and the source eNodeB determines that the UE is performing
services with the QCI of 1.
L.HHO.IntereNB.IntraFreq.ExecSuccOut.VoIP counter is incremented by 1.
L.HHO.IntereNB.InterFreq.ExecSuccOut.VoIP counter is incremented by 1.
L.HHO.IntereNB.InterFddTdd.ExecSuccOut.VoIP counter is incremented by 1.
Figure 1-386

BTS3203E
Figure 1-387
Figure 1-388

BTS3203E
Figure 1-389

BTS3203E
Figure 1-390

BTS3203E
Figure 1-391
Formula
None
Unit
None
Related Features

ExecSuccOut.VoIP GSM: None
UMTS: None
frequency Handover

BTS3203E

ExecSuccOut.VoIP GSM: None
UMTS: None
frequency Handover

dd.ExecSuccOut.VoIP GSM: None
UMTS: None
frequency Handover
1.25.36 Number of Inter-Duplex-Mode Handover Execution

Attempts Triggered for UEs that Do Not Transmit or Receive Data
Counters

dTdd.NoData.E inter-duplex-
xecAttOut mode handover
execution
attempts
triggered for
UEs that do not
transmit or
receive data
Description
The counter measures the number of inter-duplex-mode handover execution attempts
triggered for UEs that do not transmit or receive data.
Measurement Points
As shown at point B in Figure 1-392, during an X2-based inter-duplex-mode handover
triggered for a UE that does not transmit or receive data, the
L.HHO.InterFddTdd.NoData.ExecAttOut counter is incremented by 1 each time the source

BTS3203E
eNodeB sends an RRC Connection Reconfiguration message to the UE after receiving a

HANDOVER REQUEST ACKNOWLEDGE message from the target eNodeB.
As shown at point B in Figure 1-393, during an S1-based inter-duplex-mode handover, the

L.HHO.InterFddTdd.NoData.ExecAttOut counter is incremented by 1 each time the source
eNodeB sends an RRC Connection Reconfiguration message to the UE after receiving a
HANDOVER COMMAND message from the MME.
Figure 1-392
Figure 1-393

BTS3203E
Formula
None
Unit
None
Related Features
L.HHO.InterFddTdd.NoDat Multi-mode: None

a.ExecAttOut GSM: None
UMTS: None
frequency Handover
Dynamic DRX
1.25.37 Number of Successful Inter-Duplex-Mode Handover

Executions Triggered for UEs that Do Not Transmit or Receive
Data
Counters

dTdd.NoData.E successful inter-
xecSuccOut duplex-mode
handover
executions
triggered for
UEs that do not
transmit or
receive data
Description
The counter measures the number of successful inter-duplex-mode handover executions
triggered for UEs that do not transmit or receive data.

BTS3203E
Measurement Points
As shown at point C in Figure 1-394, during an X2-based inter-duplex-mode handover
L.HHO.InterFddTdd.NoData.ExecSuccOut counter is incremented by 1 each time the source
eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB.
eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB after an RRC
connection is successfully reestablished to the target eNodeB for the UE.
L.HHO.InterFddTdd.NoData.ExecSuccOut counter is incremented by 1 each time an RRC
As shown at point C in Figure 1-396, during an S1-based inter-duplex-mode handover
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME.
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME after an
RRC connection is successfully reestablished to the target eNodeB for the UE.
L.HHO.InterFddTdd.NoData.ExecSuccOut counter is incremented by 1 each time an RRC

BTS3203E
Figure 1-394
Figure 1-395

BTS3203E
Figure 1-396
Figure 1-397

BTS3203E
Figure 1-398

BTS3203E
Figure 1-399
Formula
None
Unit
None
Related Features
L.HHO.InterFddTdd.NoDat Multi-mode: None

a.ExecSuccOut GSM: None
UMTS: None
frequency Handover
Dynamic DRX

BTS3203E
1.25.38 Number of Load-based Inter-Duplex-Mode Handover

Counters

dTdd.Load.Prep load-based
AttOut inter-duplex-
mode handover
preparation
attempts

dTdd.UeNumL user-number-
oad.PrepAttOut load-based
inter-duplex-
mode handover
preparation
attempts

dTdd.UlExperie inter-duplex-
nceLoad.PrepAt mode handover
tOut preparation
attempts
triggered by
uplink-
experience-
based load
balancing
Description
The counters measure the number of load-based inter-duplex-mode handover preparation
attempts in a cell.
Measurement Points
L.HHO.InterFddTdd.Load.PrepAttOut counter is incremented by 1 each time the eNodeB
decides to perform an inter-duplex-mode handover after receiving a measurement report from
a UE or the eNodeB decides to perform an inter-duplex-mode blind handover because of load
balancing, and the L.HHO.InterFddTdd.UeNumLoad.PrepAttOut counter is incremented by 1
each time the eNodeB decides to perform an inter-duplex-mode handover after receiving a
measurement report from a UE because of user number load balancing or the eNodeB decides
to perform an inter-duplex-mode blind handover because of user number load balancing, and
the L.HHO.InterFddTdd.UlExperienceLoad.PrepAttOut counter is incremented by 1 each
time the eNodeB decides to perform an inter-duplex-mode handover after receiving a

BTS3203E
measurement report from a UE because of uplink-experience-based load balancing or the

eNodeB decides to perform an inter-duplex-mode blind handover because of uplink-
experience-based load balancing. Figure 1-400 shows an X2-based inter-duplex-mode
handover, and Figure 1-401 shows an S1-based inter-duplex-mode handover.
Figure 1-400
Figure 1-401

BTS3203E
Formula
None
Unit
None
Related Features
L.HHO.InterFddTdd.Load.P Multi-mode: None

repAttOut GSM: None
UMTS: None
Load Balancing
L.HHO.InterFddTdd.UeNu Multi-mode: None

mLoad.PrepAttOut GSM: None
UMTS: None
Load Balancing
1.25.39 Number of Load-based Inter-Duplex-Mode Handover

Execution Attempts
Counters

dTdd.Load.Exe load-based
cAttOut inter-duplex-
mode handover
execution
attempts

dTdd.UeNumL user-number-
oad.ExecAttOut load-based
inter-duplex-
mode handover
execution
attempts

BTS3203E


dTdd.UlExperie inter-duplex-
nceLoad.ExecA mode handover
ttOut execution
attempts
triggered by
uplink-
experience-
based load
balancing
Description
The counters measure the number of load-based inter-duplex-mode handover execution
attempts in a cell.
Measurement Points
As shown at point B in Figure 1-402, Figure 1-403,the
L.HHO.InterFddTdd.Load.ExecAttOut counter is incremented by 1 each time the source
eNodeB decides to perform a load-balancing-based inter-duplex-mode handover and sends an
RRC Connection Reconfiguration message to the UE, and the
L.HHO.InterFddTdd.UeNumLoad.ExecAttOut counter is incremented by 1 each time the
source eNodeB decides to perform a user-number-load-balancing-based inter-duplex-mode
handover and sends an RRC Connection Reconfiguration message to the UE, and the
L.HHO.InterFddTdd.UlExperienceLoad.ExecAttOut counter is incremented by 1 each time
the source eNodeB decides to perform an inter-duplex-mode handover because of uplink-
experience-based load balancing and sends an RRC Connection Reconfiguration message to
the UE.Figure 1-402 shows an X2-based inter-duplex-mode handover, and Figure 1-403
shows an S1-based inter-duplex-mode handover.

BTS3203E
Figure 1-402
Figure 1-403
Formula
None
Unit
None

BTS3203E
Related Features
L.HHO.InterFddTdd.Load.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
Load Balancing

mLoad.ExecAttOut GSM: None
UMTS: None
Load Balancing
1.25.40 Number of Successful Load-based Inter-Duplex-Mode

Handover Executions
Counters

dTdd.Load.Exe successful load-
cSuccOut based inter-
duplex-mode
handover
executions

dTdd.UeNumL successful user-
oad.ExecSuccO number-load-
ut based inter-
duplex-mode
handover
executions

BTS3203E


dTdd.UlExperie successful inter-
nceLoad.ExecS duplex-mode
uccOut handover
executions
triggered by
uplink-
experience-
based load
balancing
Description
The counters measure the number of successful load-based inter-duplex-mode handover
Measurement Points
As shown at point C in Figure 1-404, the L.HHO.InterFddTdd.Load.ExecSuccOut counter is
incremented by 1 each time the source eNodeB decides to perform a load-based X2-based
inter-duplex-mode handover and receives a UE CONTEXT RELEASE message from the
target eNodeB. In addition, if the handover is triggered by the user number load, the
L.HHO.InterFddTdd.UeNumLoad.ExecSuccOut counter is incremented by 1. If the handover
is triggered by the uplink-experience-based load balancing, the
L.HHO.InterFddTdd.UlExperienceLoad.ExecSuccOut counter is incremented by 1.
incremented by 1 each time the source eNodeB decides to perform a load-based inter-duplex-
mode handover and receives a UE CONTEXT RELEASE message from the target eNodeB
after an RRC connection is successfully reestablished to the target eNodeB for the UE. In
addition, if the handover is triggered by the user number load, the
incremented by 1 each time the source eNodeB decides to perform a load-based X2-based
inter-duplex-mode handover and an RRC connection is successfully reestablished to the
source eNodeB for the UE. In addition, if the handover is triggered by the user number load,
the L.HHO.InterFddTdd.UeNumLoad.ExecSuccOut counter is incremented by 1. If the
handover is triggered by the uplink-experience-based load balancing, the
incremented by 1 each time the source eNodeB decides to perform a load-based S1-based
inter-duplex-mode handover and receives a UE CONTEXT RELEASE message from the
MME. In addition, if the handover is triggered by the user number load, the

BTS3203E

incremented by 1 each time the source eNodeB decides to perform a load-based inter-duplex-
mode handover and receives a UE CONTEXT RELEASE message from the MME after an
RRC connection is successfully reestablished to the target eNodeB for the UE. In addition, if
the handover is triggered by the user number load, the
incremented by 1 each time the source eNodeB decides to perform a load-based S1-based
inter-duplex-mode handover and an RRC connection is successfully reestablished to the
source eNodeB for the UE. In addition, if the handover is triggered by the user number load,
the L.HHO.InterFddTdd.UeNumLoad.ExecSuccOut counter is incremented by 1.If the
handover is triggered by the uplink-experience-based load balancing, the
Figure 1-404

BTS3203E
Figure 1-405

BTS3203E
Figure 1-406
Figure 1-407

BTS3203E
Figure 1-408

BTS3203E
Figure 1-409
Formula
None
Unit
None
Related Features
L.HHO.InterFddTdd.Load.E Multi-mode: None

UMTS: None
Load Balancing

BTS3203E

mLoad.ExecSuccOut GSM: None
UMTS: None
Load Balancing
1.25.41 Number of Coverage-based Inter-Duplex-Mode Handover

Counters

dTdd.Coverage. coverage-based
PrepAttOut inter-duplex-
mode handover
preparation
attempts
Description
The counter measures the number of coverage-based inter-duplex-mode handover preparation
attempts in a cell.
Measurement Points
L.HHO.InterFddTdd.Coverage.PrepAttOut counter is incremented by 1 each time the eNodeB
decides to perform an inter-duplex-mode handover after receiving a measurement report from
a UE because of coverage. Figure 1-410 shows an X2-based inter-duplex-mode handover,
and Figure 1-411 shows an S1-based inter-duplex-mode handover.

BTS3203E
Figure 1-410
Figure 1-411
Formula
None
Unit
None

BTS3203E
Related Features
L.HHO.InterFddTdd.Covera Multi-mode: None

ge.PrepAttOut GSM: None
UMTS: None
frequency Handover
1.25.42 Number of Coverage-based Inter-Duplex-Mode Handover

Execution Attempts
Counters

dTdd.Coverage. coverage-based
ExecAttOut inter-duplex-
mode handover
execution
attempts
Description
The counter measures the number of coverage-based inter-duplex-mode handover execution
attempts in a cell.
Measurement Points
As shown at point B in Figure 1-412, Figure 1-413 the
L.HHO.InterFddTdd.Coverage.ExecAttOut counter is incremented by 1 each time the
eNodeB decides to perform an inter-duplex-mode handover because of coverage and sends an
RRC Connection Reconfiguration message to the UE. Figure 1-412 shows an X2-based inter-
duplex-mode handover, and Figure 1-413 shows an S1-based inter-duplex-mode handover.

BTS3203E
Figure 1-412
Figure 1-413
Formula
None
Unit
None

BTS3203E
Related Features

ge.ExecAttOut GSM: None
UMTS: None
frequency Handover
1.25.43 Number of Successful Coverage-based Inter-Duplex-Mode

Handover Executions
Counters

dTdd.Coverage. successful
ExecSuccOut coverage-based
inter-duplex-
mode handover
executions
Description
The counter measures the number of successful coverage-based inter-duplex-mode handover
Measurement Points
As shown at point C in Figure 1-414, during a coverage-based X2-based inter-duplex-mode
handover, the L.HHO.InterFddTdd.Coverage.ExecSuccOut counter is incremented by 1 each
time the source eNodeB receives a UE CONTEXT RELEASE message from the target
eNodeB.
eNodeB after an RRC connection is successfully reestablished to the target eNodeB for the
UE.
time the source eNodeB receives an RRC Connection Reestablishment Complete message
from the UE after an RRC connection is successfully reestablished to the source eNodeB for
the UE.

BTS3203E
As shown at point C in Figure 1-416, during a coverage-based S1-based inter-duplex-mode

the MME.
the MME after an RRC connection is successfully reestablished to the target eNodeB for the
UE.
the UE.
Figure 1-414

BTS3203E
Figure 1-415
Figure 1-416

BTS3203E
Figure 1-417

BTS3203E
Figure 1-418

BTS3203E
Figure 1-419
Formula
None
Unit
None
Related Features

ge.ExecSuccOut GSM: None
UMTS: None
frequency Handover

BTS3203E
1.25.44 Number of SPID-based Inter-Duplex-Mode Outgoing

Handover Attempts back to the HPLMN
Counters

dTdd.RegainHP SPID-based
LMN.PrepAttO inter-duplex-
ut mode outgoing
handover
attempts back
to the HPLMN
Description
The counter measures the number of SPID-based inter-duplex-mode outgoing handover
attempts in a cell back to the HPLMN. In national roaming scenarios, if the handover back to
the HPLMN for UEs is enabled, a roaming UE can be handed over to the HPLMN when this
UE moves back to the HPLMN.
Measurement Points
As shown at point A in Figure 1-420, during an X2-based handover, the
L.HHO.InterFddTdd.RegainHPLMN.PrepAttOut counter is incremented by 1 each time the
source eNodeB decides to perform an X2-based inter-duplex-mode handover after receiving a
measurement report from the UE. The corresponding measurement control message is
As shown at point A in Figure 1-421, during an S1-based handover, the
L.HHO.InterFddTdd.RegainHPLMN.PrepAttOut counter is incremented by 1 each time the
source eNodeB decides to perform an S1-based inter-duplex-mode handover after receiving a
measurement report from the UE. The corresponding measurement control message is

BTS3203E
Figure 1-420
Figure 1-421

BTS3203E
Formula
None
Unit
None
Related Features
L.HHO.InterFddTdd.Regain Multi-mode: None

HPLMN.PrepAttOut GSM: None
UMTS: None
SPID
1.25.45 Number of SPID-based Inter-Duplex-Mode Outgoing

Handover Executions back to the HPLMN
Counters

dTdd.RegainHP SPID-based
LMN.ExecAttO inter-duplex-
ut mode outgoing
handover
executions back
to the HPLMN
Description
The counter measures the number of SPID-based inter-duplex-mode outgoing handover
executions in a cell back to the HPLMN. In national roaming scenarios, if the handover back
Measurement Points
As shown at point B in Figure 1-422, during an X2-based inter-duplex-mode handover, the
L.HHO.InterFddTdd.RegainHPLMN.ExecAttOut counter is incremented by 1 each time the
source eNodeB sends an RRC Connection Reconfiguration message to the UE after receiving
a HANDOVER REQUEST ACKNOWLEDGE message from the target eNodeB.

BTS3203E
As shown at point B in Figure 1-423, during an S1-based inter-duplex-mode handover, the

L.HHO.InterFddTdd.RegainHPLMN.ExecAttOut counter is incremented by 1 each time the
source eNodeB sends an RRC Connection Reconfiguration message to the UE after receiving
a HANDOVER COMMAND message from the MME.
Figure 1-422

BTS3203E
Figure 1-423
Formula
None
Unit
None
Related Features

HPLMN.ExecAttOut GSM: None
UMTS: None
SPID

BTS3203E
1.25.46 Number of Successful SPID-based Inter-Duplex-Mode

Outgoing Handovers back to the HPLMN
Counters

dTdd.RegainHP successful
LMN.ExecSucc SPID-based
Out inter-duplex-
mode outgoing
handovers back
to the HPLMN
Description
The counter measures the number of successful SPID-based inter-duplex-mode outgoing
handovers in a cell back to the HPLMN. In national roaming scenarios, if the handover back
Measurement Points
As shown at point C in Figure 1-424, during an X2-based inter-duplex-mode handover, the
L.HHO.InterFddTdd.RegainHPLMN.ExecSuccOut counter is incremented by 1 each time
data in the buffer is forwarded during the handover after the source eNodeB receives a UE
As shown at point C in Figure 1-425, during an X2-based inter-duplex-mode handover, after

an RRC connection is successfully reestablished to the target eNodeB for the UE, the
As shown at point C in Figure 1-428, during an X2-based inter-duplex-mode handover, the

L.HHO.InterFddTdd.RegainHPLMN.ExecSuccOut counter is incremented by 1 each time the
source eNodeB receives an RRC Connection Reestablishment Complete message from the
UE after an RRC connection is successfully reestablished to the source eNodeB for the UE.
As shown at point C in Figure 1-426, during an S1-based inter-duplex-mode handover, the

As shown at point C in Figure 1-427, during an S1-based inter-duplex-mode handover, after

an RRC connection is successfully reestablished to the target eNodeB for the UE, the

BTS3203E
As shown at point C in Figure 1-429, during an S1-based inter-duplex-mode handover, the

L.HHO.InterFddTdd.RegainHPLMN.ExecSuccOut counter is incremented by 1 each time the
source eNodeB receives an RRC Connection Reestablishment Complete message from the
UE after an RRC connection is successfully reestablished to the source eNodeB for the UE.
Figure 1-424

BTS3203E
Figure 1-425

BTS3203E
Figure 1-426

BTS3203E
Figure 1-427

BTS3203E
Figure 1-428

BTS3203E
Figure 1-429
Formula
None
Unit
None
Related Features

HPLMN.ExecSuccOut GSM: None
UMTS: None
SPID

BTS3203E
1.25.47 Number of UL-Quality-based Inter-Frequency Handover

Counters
1526729994 L.HHO.InterFre Number of UL- BTS3203E LTE L

q.ULquality.Pre quality-based
handover
preparation
attempts
Description
The counter measures the number of UL-quality-based inter-frequency handover preparation
attempts in a cell.
Measurement Points
As shown at point A in Figure 1-430, Figure 1-431 the
L.HHO.InterFreq.ULquality.PrepAttOut counter is incremented by 1 each time the eNodeB
decides to perform an inter-frequency handover after receiving a measurement report from a
UE because of uplink signal quality.Figure 1-430 shows an X2-based inter-frequency
Figure 1-430

BTS3203E
Figure 1-431
Formula
None
Unit
None
Related Features
L.HHO.InterFreq.ULquality. Multi-mode: None

UMTS: None
frequency Handover

BTS3203E
1.25.48 Number of UL-Quality-based Inter-Duplex-Mode

Handover Preparation Attempts
Counters
1526729995 L.HHO.InterFd Number of UL- BTS3203E LTE L

dTdd.ULquality quality-based
.PrepAttOut inter-duplex-
mode handover
preparation
attempts
Description
The counter measures the number of UL-quality-based inter-duplex-mode handover
preparation attempts in a cell.
Measurement Points
L.HHO.InterFddTdd.ULquality.PrepAttOut counter is incremented by 1 each time the
eNodeB decides to perform an inter-duplex-mode handover after receiving a measurement
report from a UE because of uplink signal quality. Figure 1-432 shows an X2-based inter-
duplex-mode handover, and Figure 1-433 shows an S1-based inter-duplex-mode handover.
Figure 1-432

BTS3203E
Figure 1-433
Formula
None
Unit
None
Related Features
L.HHO.InterFddTdd.ULqua Multi-mode: None

lity.PrepAttOut GSM: None
UMTS: None
frequency Handover

BTS3203E
1.25.49 Number of UL-Quality-based Inter-Frequency Handover

Execution Attempts
Counters
1526729996 L.HHO.InterFre Number of UL- BTS3203E LTE L

q.ULquality.Ex quality-based
ecAttOut inter-frequency
handover
execution
attempts
Description
The counter measures the number of UL-quality-based inter-frequency handover execution
attempts in a cell.
Measurement Points
L.HHO.InterFreq.ULquality.ExecAttOut counter is incremented by 1 each time the eNodeB
decides to perform an inter-frequency handover based on the uplink signal quality and sends
an RRC Connection Reconfiguration message to the UE. Figure 1-434 shows an X2-based
inter-frequency handover, and Figure 1-435 shows an S1-based inter-frequency handover.
Figure 1-434

BTS3203E
Figure 1-435
Formula
None
Unit
None
Related Features

UMTS: None
frequency Handover

BTS3203E
1.25.50 Number of UL-Quality-based Inter-Duplex-Mode

Handover Execution Attempts
Counters
1526729997 L.HHO.InterFd Number of UL- BTS3203E LTE L

dTdd.ULquality quality-based
.ExecAttOut inter-duplex-
mode handover
execution
attempts
Description
The counter measures the number of UL-quality-based inter-duplex-mode handover execution
attempts in a cell.
Measurement Points
L.HHO.InterFddTdd.ULquality.ExecAttOut counter is incremented by 1 each time the
eNodeB decides to perform an inter-duplex-mode handover based on the uplink signal quality
and sends an RRC Connection Reconfiguration message to the UE. Figure 1-436 shows an
X2-based inter-duplex-mode handover, and Figure 1-437 shows an S1-based inter-duplex-
mode handover.
Figure 1-436

BTS3203E
Figure 1-437
Formula
None
Unit
None
Related Features

lity.ExecAttOut GSM: None
UMTS: None
frequency Handover

BTS3203E
1.25.51 Number of Successful UL-Quality-based Inter-Frequency

Handover Executions
Counters

q.ULquality.Ex successful UL-
inter-frequency
handover
executions
Description
The counter measures the number of successful UL-quality-based inter-frequency handover
Measurement Points
As shown at point C in Figure 1-438, during a UL-quality-based X2-based inter-frequency
handover, the L.HHO.InterFreq.ULquality.ExecSuccOut counter is incremented by 1 each
eNodeB.
UE.
the UE.
As shown at point C in Figure 1-440, during a UL-quality-based S1-based inter-frequency
the MME.
UE.

BTS3203E
the UE.
Figure 1-438

BTS3203E
Figure 1-439
Figure 1-440

BTS3203E
Figure 1-441

BTS3203E
Figure 1-442

BTS3203E
Figure 1-443
Formula
None
Unit
None
Related Features

UMTS: None
frequency Handover

BTS3203E
1.25.52 Number of Successful UL-Quality-based Inter-Duplex-

Mode Handover Executions
Counters

dTdd.ULquality successful UL-
.ExecSuccOut quality-based
inter-duplex-
mode handover
executions
Description
The counter measures the number of successful UL-quality-based inter-duplex-mode
handover executions in a cell.
Measurement Points
As shown at point C in Figure 1-444, during a UL-quality-based X2-based inter-duplex-mode
handover, the L.HHO.InterFddTdd.ULquality.ExecSuccOut counter is incremented by 1 each
eNodeB.
UE.
the UE.
As shown at point C in Figure 1-446, during a UL-quality-based S1-based inter-duplex-mode
the MME.
UE.

BTS3203E
the UE.
Figure 1-444

BTS3203E
Figure 1-445
Figure 1-446

BTS3203E
Figure 1-447

BTS3203E
Figure 1-448

BTS3203E
Figure 1-449
Formula
None
Unit
None
Related Features

lity.ExecSuccOut GSM: None
UMTS: None
frequency Handover

BTS3203E
eNodeBFunction Performance Counter Reference

BTS3203E V100R012C10SPH116 ENodeBFunction Performance Counter Reference

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

BTS3203E V100R012C10SPH116 ENodeBFunction Performance Counter Reference

Încărcat de

Drepturi de autor:

Formate disponibile

BTS3203E

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2017-03-10) Huawei Proprietary and Confidential i

1 Measurement of Cell Performance (Cell)................................................................................. 1

Issue 03 (2017-03-10) Huawei Proprietary and Confidential ii

Issue 03 (2017-03-10) Huawei Proprietary and Confidential iii

1.9.16 Number of Times a UE in Connected Mode Exits DRX in RRC_CONECTED Mode........................................394

Issue 03 (2017-03-10) Huawei Proprietary and Confidential iv

1.9.53 Number of Times IRC or MRC Is Used on the PUCCH.......................................................................................447

Issue 03 (2017-03-10) Huawei Proprietary and Confidential v

1.11.9 Receive Duration of Uplink PDCP SDUs in a Cell...............................................................................................540

Issue 03 (2017-03-10) Huawei Proprietary and Confidential vi

Issue 03 (2017-03-10) Huawei Proprietary and Confidential vii

1.17.2 Number of TBs Transmitted in Downlink MIMO Mode...................................................................................... 771

Issue 03 (2017-03-10) Huawei Proprietary and Confidential viii

1.20.21 PDSCH PRB Usage Distribution...................................................................................................................... 1021

Issue 03 (2017-03-10) Huawei Proprietary and Confidential ix

Issue 03 (2017-03-10) Huawei Proprietary and Confidential x

1.22.14 Number of UEs on Which DRX Takes Effect in a Cell.................................................................................... 1192

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xi

1.23.3 Number of Successful Inter-RAT Handovers from E-UTRAN to CDMA2000 Network...................................1286

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xii

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xiii

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xiv

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xv

1.25.53 Number of Service-Based Inter-Duplex-Mode Handover Preparation Attempts..............................................1734

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xvi

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xvii

1.31.2 Number of Successful E-CID Measurement Requests in a Cell......................................................................... 2019

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xviii

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xix

1.37.31 L.Reserve.31...................................................................................................................................................... 2130

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xx

1.37.73 L.Reserve.73...................................................................................................................................................... 2156

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxi

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxii

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxiii

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxiv

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxv

1.53 Resource Optimization Measurement (ResOpt.Cell)............................................................................................. 2993

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxvi

1.61.4 Total Values of VQIs of EVS...............................................................................................................................3133

2 Measurement of eNodeB Performance (eNodeB)............................................................. 3216

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxvii

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxviii

3 Measurement of S1 Link Performance (Sig.S1)................................................................. 3289

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

5 Measurement of Intra-RAT Inter-Cell Handover Performance (NCell).......................3304

6 Measurement of CNOperator Performance (Cell.Operator)...........................................3359

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxix

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxx

6.6.7 Number of Outgoing Blind Handover Attempts for a Specific Operator..............................................................3583

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxxi

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxxii

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)................. 3884

10 Measurement of Board Service Performance (Board.Service)...................................... 3898

Issue 03 (2017-03-10) Huawei Proprietary and Confidential xxxiii

1 Measurement of Cell Performance (Cell)

About This Chapter

RRC.Setup.Cell RRC Setup Measurement(RRC.Setup.Cell)