3900 Series Base Station Performance Counter Reference (V100R008C00 - 08, eNodeB) (PDF) - EN PDF

3900 Series Base Station
V100R008C00 (eNodeB)
Performance Counter Reference
Issue 08
Date 2014-03-14
HUAWEI TECHNOLOGIES CO., LTD.

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

Copyright © Huawei Technologies Co., Ltd.
Performance Counter Reference About This Document
About This Document
Purpose
This document describes all the performance counters of the eNodeB.
Product Version
The following table lists the product version involved in this document.
Product Name Product Version
DBS3900 V100R008C00
The mapping single-mode base station version
BTS3900A
is:
DBS3900 eNodeB: V100R006C00
BTS3900L
BTS3900AL
Intended Audience
This document is intended for:
l Network planners
l System engineers
Change History
For detailed performance counter changes, see Performance Counter Changes document of the
release notes.
Issue 08 (2014-03-14) Huawei Proprietary and Confidential ii

Document Structure
Figure 1 shows the document structure.
Figure 1 Document structure
Table 1 explains the terms shown in Figure 1.
Table 1 Terms
Term Explanation
On the top level, object types are classified into three

categories: Radio Network Related Measurement, Transport
Classification of object type
Network Related Measurement, Hardware Platform Related
Measurement.
Object types are located at the second level of the document

Object type structure.
One object type contains one or more function subsets.
Function Subsets are located at the third level of the document

structure.
Function Subset
One function subset contains one or more counters but
belongs to only one object type.
Counters are located at the fourth level of the document

structure.
Counter
Counters are the basic elements of performance measurement.
One counter can belong to only one function subset.
Counter Item Description

Table 2 Description of each counter item
Item Description
Object Overview Definition and function of a object type.

type
Function SubSets Function subsets contained in a object type.
Issue 08 (2014-03-14) Huawei Proprietary and Confidential iii

Item Description
Functio FunctionSet Name of the function set.

n Set Name One function set contains one or more function subsets.
Functio Overview Definition of a function subset and the flowchart for

n Subset measuring related counters.
Counters Counters contained in a function subset.
Counter A table that lists parent counters and their child counters in a
Relationship table. Note that the child counters listed in the table cover only
typical scenarios. That is, some scenarios are not covered by
any counter. Therefore, the value of a parent counter is larger
than or equal to the sum of the values of its child counters.
Some counters may not be involved in any counter
relationship.
Counter Counter ID A string of digits that uniquely identifies a counter.
Counter Name Name of a counter. It is composed of a string of uppercase

letters, lowercase letters, and dots.
Counter A phrase that provides a simple description about a counter.

Description
Description Detailed description about a counter.
Measurement Condition for triggering counter measurement.

Point
Formula Relationship among counters.
Unit Unit of a counter.
Related Features Features related to a counter are listed in feature ID and feature
name. A counter is used to estimate related features. Related
features are listed as follows in different scenarios:
l If a counter has no related features, no features are listed.
l A counter has related features,
– If this counter applies only to GSM, UMTS, LTE, or
SingleRAN, the features are related to such RAT.
– If this counter applies to multiple RATs in GSM,
UMTS, LTE, and SingleRAN, the features are a set of
features related to all associated RATs. Only the
feature IDs and feature names of the features for related
RATs are listed.
Original Release The number of version for which the counter was first
available.
Network Element Name of the NE to which the counter applies.
Issue 08 (2014-03-14) Huawei Proprietary and Confidential iv

Measurement Period
The measurement period is 15 minutes or 60 minutes.
Issue 08 (2014-03-14) Huawei Proprietary and Confidential v

Performance Counter Reference Contents
Contents
About This Document.....................................................................................................................ii

1 Equipment and Transport Network Related Measurement.................................................1
1.1 Measurement of Ethernet port performance (ETHPORT).............................................................................................3
1.1.1 Measurement related to Ethernet port (Physical.FEGE).............................................................................................3
1.1.1.1 Number of Bytes on the Ethernet Port......................................................................................................................8
1.1.1.2 Number of Packets on the Ethernet Port................................................................................................................10
1.1.1.3 Rate on the Ethernet Port........................................................................................................................................12
1.1.1.4 Available Bandwidth on the Ethernet Port.............................................................................................................16
1.2 Measurement of E1/T1 port performance (E1T1)........................................................................................................18
1.2.1 Measurement related to E1T1 port (Physical.E1T1).................................................................................................18
1.2.1.1 Number of Code Type Errors on the E1/T1 Electrical Port...................................................................................23
1.2.1.2 Number of Base Frame Alignment Errors on the E1/T1 Electrical Port................................................................24
1.2.1.3 Number of CRC Errors on the E1/T1 Electrical Port.............................................................................................25
1.2.1.4 Number of Ebit Errors on the E1/T1 Port...............................................................................................................27
1.2.1.5 Number of Sa6 Errors on the E1/T1 Port...............................................................................................................28
1.2.1.6 Number of multiframe cycles at the E1/T1 port.....................................................................................................29
1.2.1.7 Number of Times that Frames Are Not Aligned....................................................................................................30
1.2.1.8 Total Errored Seconds in the TX Direction............................................................................................................32
1.2.1.9 Total Severely Errored Seconds in the TX Direction.............................................................................................33
1.2.1.10 Total Unavailable Seconds in the TX Direction...................................................................................................34
1.2.1.11 Total Errored Seconds in the RX Direction..........................................................................................................36
1.2.1.12 Total Severely Errored Seconds in the RX Direction...........................................................................................37
1.2.1.13 Total Unavailable Seconds in the RX Direction..................................................................................................38
1.3 Measurement of PPP Link performance (PPP)............................................................................................................40
1.3.1 Measurement related to PPP link (DataLink.PPP)....................................................................................................40
1.3.1.1 Number of Packets on the PPP Link......................................................................................................................46
1.3.1.2 Number of Bytes on the PPP Link..........................................................................................................................49
1.3.1.3 Rate on the PPP Link..............................................................................................................................................52
1.3.1.4 Total bandwidth of the PPP link.............................................................................................................................56
1.4 Measurement of MP Group performance (MPGRP)....................................................................................................58
1.4.1 Measurement related to MP (DataLink.MPGRP).....................................................................................................59
1.4.1.1 Number of Packets on the MP Group.....................................................................................................................64
Issue 08 (2014-03-14) Huawei Proprietary and Confidential vi

1.4.1.2 Number of Bytes on the MP Group........................................................................................................................68

1.4.1.3 Rate on the MP Group............................................................................................................................................70
1.4.1.4 Available Bandwidth on the MP Group.................................................................................................................75
1.5 Measurement of IP layer performance (IP)..................................................................................................................77
1.5.1 Measurement related to IP (Network.IP)...................................................................................................................77
1.5.1.1 Number of IP Packets.............................................................................................................................................80
1.5.1.2 Number of Bytes in the IP Packets.........................................................................................................................83
1.6 Measurement of IP path performance (IPPath)............................................................................................................86
1.6.1 Measurement related to IP path (Transport.IPPath)..................................................................................................87
1.6.1.1 Number of real-time service packets on the IP path...............................................................................................89
1.6.1.2 Number of bytes of real-time service on the IP Path..............................................................................................91
1.6.1.3 Number of non-real-time service packets on the IP path.......................................................................................92
1.6.1.4 Number of bytes of non-real-time services on the IP path.....................................................................................93
1.7 Measurement of Resource Group performance (RscGroup)........................................................................................94
1.7.1 Measurement related to Resource Group (Transport.RscGroup)..............................................................................94
1.7.1.1 Number of Bytes in the Packets Transmitted by the Resource Group...................................................................98
1.7.1.2 Number of Packets Transmitted by the Resource Group.......................................................................................99
1.7.1.3 Rates of the Resource Group................................................................................................................................101
1.8 Measurement of IP PM performance (IPPM).............................................................................................................104
1.8.1 Measurement related to IPPM (Transport.IPPM)....................................................................................................104
1.8.1.1 Byte Rate Measurements on the IP PM ...............................................................................................................111
1.8.1.2 Packet Rate Measurements on the IP PM ............................................................................................................114
1.8.1.3 Forward Packet Loss Rate Measurements on the IP PM......................................................................................116
1.8.1.4 Jitter Measurements on the IP PM........................................................................................................................118
1.8.1.5 RTT Measurements on the IP PM........................................................................................................................120
1.8.1.6 Number of Packets on the IP PM.........................................................................................................................123
1.9 Measurement of SCTP performance (SCTP).............................................................................................................124
1.9.1 Measurement related to SCTP link (Transport.SCTP)............................................................................................125
1.9.1.1 Number of Bytes in the IP Packets on the SCTP Link.........................................................................................129
1.9.1.2 Number of IP Packets on the SCTP Link.............................................................................................................132
1.9.1.3 IP Packet Rate Measurements on the SCTP Link................................................................................................134
1.10 Measurement of IPv6 performance (IPv6)...............................................................................................................138
1.10.1 Measurement related to IPv6 (Network.IPv6).......................................................................................................138
1.10.1.1 Number of IPv6 Packets.....................................................................................................................................141
1.10.1.2 Number of Bytes in the IPv6 Packets.................................................................................................................143
1.11 Measurement of IPv6Path performance (IPv6Path).................................................................................................145
1.11.1 Measurement related to IPv6Path (Transport.IPv6Path).......................................................................................146
1.11.1.1 Number of Real-Time Service Packets on the IPv6 Path...................................................................................148
1.11.1.2 Number of Bytes in the Real-Time Service Packets on the IPv6 Path...............................................................150
1.11.1.3 Number of Non-Real-Time Service Packets on the IPv6 Path...........................................................................152
1.11.1.4 Number of Bytes in the Non-Real-Time Service Packets on the IPv6 Path.......................................................154
Issue 08 (2014-03-14) Huawei Proprietary and Confidential vii

1.12 Measurement of OMCH performance (OMCH)......................................................................................................156

1.12.1 Measurement related to OMCH (Transport.OMCH)............................................................................................156
1.12.1.1 Total Number of Packets Received on the OM Channel....................................................................................164
1.12.1.2 VS.OMCH.RxInSeqPkts....................................................................................................................................165
1.12.1.3 VS.OMCH.RxWndProbePkts............................................................................................................................166
1.12.1.4 VS.OMCH.RxWndUpdatePkts..........................................................................................................................167
1.12.1.5 VS.OMCH.RxDupPkts.......................................................................................................................................168
1.12.1.6 VS.OMCH.RxPartDupPkts................................................................................................................................170
1.12.1.7 VS.OMCH.RxOutOfOrderPkts..........................................................................................................................171
1.12.1.8 VS.OMCH.RxAfterWndPkts.............................................................................................................................172
1.12.1.9 VS.OMCH.RxAfterClosePkts............................................................................................................................173
1.12.1.10 Number of ACKs Received on the OM Channel.............................................................................................175
1.12.1.11 VS.OMCH.RxDupAckPkts..............................................................................................................................176
1.12.1.12 VS.OMCH.RxTooMuchAckPkts.....................................................................................................................177
1.12.1.13 Total Number of Packets Transmitted on the OM Channel.............................................................................178
1.12.1.14 VS.OMCH.TxUrgentPkts.................................................................................................................................180
1.12.1.15 Number of Control Packets Transmitted on the OM Channel.........................................................................181
1.12.1.16 VS.OMCH.TxWndProbePkts...........................................................................................................................182
1.12.1.17 VS.OMCH.TxWndUpdatePkts........................................................................................................................183
1.12.1.18 Number of Data Packets Transmitted on the OM Channel..............................................................................185
1.12.1.19 Number of Packets Retransmitted on the OM Channel...................................................................................186
1.12.1.20 Number of ACKs Transmitted on the OM Channel.........................................................................................187
1.13 Measurement of Tunnel performance (TUNNEL)...................................................................................................188
1.13.1 Measurement related to TUNNEL (Network.Tunnel)...........................................................................................188
1.13.1.1 Number of Bytes on the TUNNEL.....................................................................................................................192
1.13.1.2 Number of Packets on the TUNNEL..................................................................................................................195
1.13.1.3 Rate on the TUNNEL.........................................................................................................................................197
1.14 Measurement of TRUNK performance (TRUNK)...................................................................................................203
1.14.1 Measurement related to TRUNK (Datalink.TRUNK)...........................................................................................204
1.14.1.1 Available Bandwidth on the TRUNK................................................................................................................206
1.14.1.2 Rate on the TRUNK...........................................................................................................................................208
1.15 Measurement of firewall performance (Firewall).....................................................................................................211
1.15.1 Measurement related to firewall (Transport.Firewall)...........................................................................................211
1.15.1.1 Number of discarded packets due to L2 ACL filter based on port.....................................................................212
1.15.1.2 Number of discarded packets due to advanced ACL filter based on port..........................................................214
1.16 Measurement of IKE performance (IKE).................................................................................................................215
1.16.1 Measurement related to IKE (Transport.IKE).......................................................................................................215
1.16.1.1 Number of IKE packets received........................................................................................................................217
1.16.1.2 Number of IKE packets transmitted...................................................................................................................218
1.16.1.3 Times of IKE sub SA rekey completed..............................................................................................................219
1.16.1.4 Times of DPD session fail..................................................................................................................................221
Issue 08 (2014-03-14) Huawei Proprietary and Confidential viii

1.17 Measurement of IPSec performance (IPSec)............................................................................................................222

1.17.1 Measurement related to IPSec (Transport.IPSec)..................................................................................................222
1.17.1.1 Number of discarded packets received due to replay checking fail...................................................................225
1.17.1.2 Number of discarded packets received due to AH checking fail........................................................................227
1.17.1.3 Number of discarded packets received due to ESP fail......................................................................................228
1.17.1.4 Number of discarded packets received due to decrypt ACL fail........................................................................229
1.17.1.5 Number of decrypt success packets received.....................................................................................................230
1.17.1.6 Number of discarded packets transmitted due to outbound SA miss.................................................................231
1.17.1.7 Number of discarded packets transmitted due to sequence number overflow...................................................232
1.17.1.8 Number of encrypt success packets transmitted.................................................................................................234
1.18 Measurement of SCTP Link performance (SCTPLNK)..........................................................................................235
1.18.1 Measurement related to SCTPLNK (Transport.SCTPLNK).................................................................................235
1.18.1.1 Number of Bytes in the IP Packets on the SCTP link........................................................................................242
1.18.1.2 Number of IP Packets on the SCTP link............................................................................................................245
1.18.1.3 IP Packet Rate Measurements on the SCTP link................................................................................................248
1.18.1.4 Number of packets on the SCTP link from the application layer.......................................................................253
1.18.1.5 Number of chunks retransmitted from the SCTP link........................................................................................254
1.18.1.6 Congestion Duration of an SCTP Link...............................................................................................................256
1.18.1.7 Number of Congestions on an SCTP Link.........................................................................................................257
1.18.1.8 Duration of SCTP Link Unavailable..................................................................................................................258
1.18.1.9 Number of Times SCTP Link Unavailable........................................................................................................259
1.19 Measurement of UserPlaneHostIP performance (UserPlaneHostIP).......................................................................261
1.19.1 Measurement related to UserPlaneHostIP (Transport.UserPlaneHostIP).............................................................261
1.19.1.1 Number of IP Packets on the User-Plane Local IP Address...............................................................................264
1.19.1.2 Number of Bytes in the IP Packets on the User-Plane Local IP Address...........................................................266
1.19.1.3 Rate of IP Packets on the User-Plane Local IP Address....................................................................................269
1.20 Measurement of GTP-U performance (GTP-U).......................................................................................................272
1.20.1 Measurement related to GTP-U (Transport.GTPU)..............................................................................................273
1.20.1.1 Number of Bytes in the Packets on the GTP-U Link.........................................................................................274
1.20.1.2 Number of Packets on the GTP-U Link.............................................................................................................276
1.21 Measurement of Board performance (Board)...........................................................................................................278
1.21.1 Measurement related to CPU of board (Measurement related to CPU of board)..................................................278
1.21.1.1 Maximum and Average Board CPU Usage........................................................................................................279
1.21.1.2 Number of Times that the CPU Usage of Boards Exceeds the Preconfigured Threshold.................................280
1.22 Measurement of RRU performance (RRU)..............................................................................................................282
1.22.1 Measurement related to RRU (Measurement related to RRU)..............................................................................282
1.22.1.1 RRU or RFU Power Consumption.....................................................................................................................283
1.23 Measurement of eNodeB performance (eNodeB)....................................................................................................284
1.23.1 Measurement related to eNodeB (eNodeB.Device)..............................................................................................285
1.23.1.1 eNodeB Power Consumption.............................................................................................................................286
1.23.1.2 eNodeB Power Consumption Calculated by the PMU.......................................................................................287
Issue 08 (2014-03-14) Huawei Proprietary and Confidential ix

1.23.1.3 PSU shutdown total time....................................................................................................................................288

1.23.2 Measurement related to BBU (Measurement related to BBU)..............................................................................290
1.23.2.1 BBU Power Consumption..................................................................................................................................290
1.24 Measurement of PMU performance (PMU).............................................................................................................292
1.24.1 Measurement related to PMU (Measurement related to PMU).............................................................................292
1.24.1.1 PMU Power Consumption..................................................................................................................................292
1.25 NODE (NODE)........................................................................................................................................................294
1.25.1 Node Equipment Performance Measurement (Equipment.Node).........................................................................294
1.25.1.1 PSU shutdown total time....................................................................................................................................295
1.25.1.2 The sum of power consumption of all boards in the LTE..................................................................................296
1.25.1.3 Power consumption measured by the power system of the LTE........................................................................297
1.26 BBUBoard (BBUBoard)...........................................................................................................................................298
1.26.1 BBU Board Load Performance Measurement (Load.BBUBoard)........................................................................298
1.26.1.1 The number of times of CPU Use Rate Overload..............................................................................................300
1.26.1.2 Maximum and Average Board CPU Usage........................................................................................................301
1.26.1.3 Percentage of Cpu Use Rate Overload...............................................................................................................303
1.27 GNSS (GNSS)..........................................................................................................................................................304
1.27.1 Traced GNSS Satellites Performance Measurement (SatellitesTraced.GNSS)....................................................305
1.27.1.1 Number of times that the number of traced GNSS satellites falls in level 0......................................................306
1.27.1.6 Average number of traced GNSS satellites........................................................................................................311
2 Radio Network Related Measurement..................................................................................313

2.1 Measurement of eNodeB performance (eNodeB)......................................................................................................314
2.1.1 Measurement related to LCS in eNodeB (LCS.ENODEB).....................................................................................314
2.1.1.1 Number of OTDOA Measurement Attempts Received by an eNodeB................................................................315
2.1.1.2 Number of Successful Responses Sent by an eNodeB to OTDOA Measurement Requests................................316
2.1.2 Measurement related to user traffic in eNodeB (Traffic.User.eNodeB).................................................................317
2.1.2.1 Maximum Number of Users Under an eNodeB...................................................................................................318
2.1.3 Measurement related to RIM in eNodeB (RIM.eNodeB).......................................................................................319
2.1.3.1 Number of System Information Requests from eNodeB to WCDMA Network..................................................320
2.1.3.2 Number of system information responses from WCDMA network to eNodeB..................................................322
2.1.3.3 Number of System Information Updates from eNodeB to WCDMA Network...................................................323
2.1.3.4 Number of Load Requests from eNodeB to WCDMA Network.........................................................................325
2.1.3.5 Number of Load Responses from WCDMA Network to eNodeB.......................................................................326
2.1.3.6 Number of Load Updates from eNodeB to WCDMA Network...........................................................................327
2.1.4 Measurement related to eNodeB Thruput (Traffic.Thruput.eNodeB).....................................................................329
2.1.4.1 Maximum Traffic Volume for PDCP SDUs in an eNodeB.................................................................................330
2.1.5 eNodeB SCTP Measurement (SCTP.eNodeB).......................................................................................................332
Issue 08 (2014-03-14) Huawei Proprietary and Confidential x

2.1.5.1 Number of Times of Downlink SCTP Congestion Control.................................................................................332

2.2 Measurement of Cell performance (Cell)...................................................................................................................333
2.2.1 Measurement related to RRC setup (RRC.Setup.Cell)............................................................................................336
2.2.1.1 Number of RRC Connection Setup Requests in a Cell........................................................................................341
2.2.1.2 Number of Successful RRC Connection Setups in a Cell....................................................................................346
2.2.1.3 Success Rate of RRC Connection Setups for Services.........................................................................................350
2.2.1.4 Number of RRC Connection Setup Attempts in a Cell........................................................................................351
2.2.1.5 Number of Times a UE Transits from the Uplink-Synchronized State to the Uplink Out-of-Synchronization State
..........................................................................................................................................................................................353
2.2.1.6 Number of Times a UE Transits from the Uplink Out-of-Synchronization state to the Uplink-Synchronized State
..........................................................................................................................................................................................353
2.2.1.7 RRC Connection Setup Duration in a Cell...........................................................................................................354
2.2.2 Measurement related to RRC setup failure (RRC.SetupFail.Cell)..........................................................................357
2.2.2.1 Number of RRC Connection Setup Failures for Different Causes in a Cell........................................................359
2.2.3 Measurement related to RRC reestablish (RRC.ReEst.Cell)..................................................................................364
2.2.3.1 Number of RRC Connection Reestablishment Requests in a Cell.......................................................................366
2.2.3.2 Number of Successful RRC Connection Reestablishments in a Cell...................................................................369
2.2.4 Measurement related to RRC reestablish fail (RRC.ReEstFail.Cell)......................................................................371
2.2.4.1 Number of RRC Connection Reestablishment Failures for Different Causes in a Cell.......................................374
2.2.5 Measurement related to E-RAB establish (E-RAB.Est.Cell)..................................................................................377
2.2.5.1 Number of E-RAB Setup Attempts in a Cell.......................................................................................................393
2.2.5.2 Number of Successful E-RAB Setups in a Cell...................................................................................................398
2.2.5.3 E-RAB Setup Success Rate in a Cell....................................................................................................................403
2.2.5.4 Number of Initial E-RAB Setup Attempts in a Cell.............................................................................................404
2.2.5.5 Number of Successful Initial E-RAB Setups in a Cell.........................................................................................409
2.2.5.6 Total Number of E-RAB Setup Attempts for Incoming Handovers in a Cell......................................................413
2.2.5.7 Number of Successful E-RAB Setups for Incoming Handovers in a Cell...........................................................415
2.2.5.8 Number of UE-related Signaling Connection Setups over the S1 Interface........................................................424
2.2.5.9 E-RAB Setup Duration in a Cell..........................................................................................................................426
2.2.6 Measurement related to E-RAB release (E-RAB.Rel.Cell).....................................................................................430
2.2.6.1 Number of Abnormal E-RAB Releases in a Cell.................................................................................................454
2.2.6.2 Number of Normal E-RAB Releases in a Cell.....................................................................................................459
2.2.6.3 Number of Normal E-RAB Releases for Outgoing Handovers in a Cell.............................................................464
2.2.6.4 Number of Abnormal E-RAB Releases for Outgoing Handovers in a Cell.........................................................473
2.2.6.5 Total Number of Abnormal E-RAB Releases in a Cell........................................................................................482
2.2.6.6 Number of Abnormal E-RAB Releases for Different Causes in a Cell...............................................................485
2.2.6.7 Number of Released E-RABs of UEs in the Uplink Out-of-Synchronization State............................................490
2.2.6.8 Total Number of E-RABs of UEs When the UEs Transit from the Uplink-synchronized State to the Uplink Out-
of-Synchronization State..................................................................................................................................................493
2.2.6.9 Number of E-RAB Releases Initiated by the eNodeB in a Cell...........................................................................494
2.2.6.10 Number of E-RAB Releases Initiated by the MME in a Cell............................................................................498
2.2.6.11 Number of Remaining E-RABs in a Cell...........................................................................................................503
Issue 08 (2014-03-14) Huawei Proprietary and Confidential xi

2.2.6.12 Number of E-RAB Releases Initiated by the eNodeB Because of the S1 RESET in a Cell..............................506
2.2.6.13 Number of E-RAB Releases Initiated by the MME Because of the S1 RESET in a Cell..................................510
2.2.7 Measurement related to E-RAB establish failure (E-RAB.EstFail.Cell)................................................................515
2.2.7.1 Number of E-RAB Setup Failures for Different Causes in a Cell........................................................................517
2.2.8 Measurement related to E-RAB modify (E-RAB.Modify.Cell)..............................................................................524
2.2.8.1 Number of E-RAB Modification Attempts in a Cell............................................................................................529
2.2.8.2 Number of Successful E-RAB Modifications in a Cell........................................................................................533
2.2.8.3 Number of E-RAB Modification Failures for Different Causes in a Cell............................................................538
2.2.9 Measurement related to Cell Algorithm (Algo.Cell)...............................................................................................539
2.2.9.1 Number of Times Uplink or Downlink Congestion Occurs in a Cell..................................................................547
2.2.9.2 Duration of Uplink or Downlink Congestion in a Cell........................................................................................548
2.2.9.3 Number of Service Releases due to Congestion in a Cell....................................................................................549
2.2.9.4 Duration of Cell Unavailability............................................................................................................................550
2.2.9.5 Duration of Cell Availability................................................................................................................................552
2.2.9.6 Number of Signaling Messages over the Uu Interface.........................................................................................553
2.2.9.7 Number of DRX Reconfiguration Messages........................................................................................................554
2.2.9.8 Uplink or Downlink Voice Quality in a Cell........................................................................................................555
2.2.9.9 Number of Times that E-UTRAN is Configured as the Highest Frequency Priority in an IMMCI IE................559
2.2.9.10 Number of Times that the WCDMA Network is Configured as the Highest Frequency Priority in an IMMCI IE
..........................................................................................................................................................................................560
2.2.9.11 Number of Times that GERAN is Configured as the Highest Frequency Priority in an IMMCI IE.................562
2.2.9.12 Number of Successful Preemptions Triggered due to User Limitation..............................................................563
2.2.9.13 Number of Semi-Persistent Scheduling Times in a cell.....................................................................................564
2.2.9.14 Number of Failed Semi-Persistent Scheduling Transmissions in a Cell............................................................566
2.2.9.15 Number of Times a UE in Connected Mode Enters DRX in RRC_CONECTED Mode...................................567
2.2.9.16 Number of Times a UE in Connected Mode Exits DRX in RRC_CONECTED Mode.....................................569
2.2.9.17 DRX Duration.....................................................................................................................................................570
2.2.10 Measurement related to DRB (Traffic.DRB.Cell).................................................................................................572
2.2.10.1 Number of DRBs in a Cell.................................................................................................................................575
2.2.11 Measurement related to Thruput (Traffic.Thruput.Cell).......................................................................................578
2.2.11.1 Maximum Uplink Traffic Volume for PDCP SDUs in a Cell............................................................................601
2.2.11.2 Maximum Downlink Traffic Volume for PDCP SDUs in a Cell.......................................................................605
2.2.11.3 Total Bits of Transmitted Signaling SDUs on SRBs at the PDCP Layer in a Cell............................................609
2.2.11.4 Total Bits of Received Signaling SDUs on SRBs at the PDCP Layer in a Cell................................................609
2.2.11.5 Total Duration of Downlink Data Transmission in a Cell..................................................................................610
2.2.11.6 Total Duration of Uplink Data Transmission in a Cell......................................................................................612
2.2.11.7 Duration of Data Transmission for Services with a Specific QCI in a Cell.......................................................613
2.2.11.8 Total Duration of UE Data Transmission in a Cell............................................................................................617
2.2.11.9 Uplink Traffic Volume for PDCP SDUs in a Cell.............................................................................................618
2.2.11.10 Receive Duration of Uplink PDCP SDUs in a Cell..........................................................................................622
2.2.11.11 Downlink Traffic Volume for PDCP SDUs in a Cell......................................................................................626
2.2.11.12 Transmit Duration of Downlink PDCP SDUs in a Cell...................................................................................630
Issue 08 (2014-03-14) Huawei Proprietary and Confidential xii

2.2.11.13 Total Bits of User Data Received at the PDCP Layer from CEUs in a Cell....................................................635
2.2.11.14 Total Duration in Which User Data From CEUs Is Received at the PDCP Layer in a Cell............................636
2.2.11.15 Total Bits of User Data Transmitted at the PDCP Layer to CEUs in a Cell....................................................637
2.2.11.16 Total Duration in Which User Data Is Transmitted to CEUs at the PDCP Layer in a Cell.............................638
2.2.11.17 Total Traffic Volume of Downlink PDCP SDUs Transmitted to Activated CA UEs in a Cell.......................639
2.2.11.18 Total Transmit Duration of Downlink PDCP SDUs Transmitted to Activated CA UEs in a Cell..................640
2.2.11.19 Total Duration of Downlink Data Transmission with the Precision of 1 Millisecond in a Cell......................642
2.2.11.20 Total Duration of Uplink Data Transmission with the Precision of 1 Millisecond in a Cell...........................643
2.2.11.21 Downlink traffic volume sent in the last TTI before the buffer is empty.........................................................644
2.2.11.22 Data transmit duration except the last TTI before the downlink buffer is empty.............................................648
2.2.11.23 Traffic Volume of Uplink PDCP SDUs Sent in the Last TTI Before the UE Buffer is Empty.......................653
2.2.11.24 Uplink Data Transmit Duration Except the Last TTI Before the UE Buffer is Empty....................................654
2.2.11.25 Uplink Traffic Volume of PDCP SDUs Scheduled for Small Packets............................................................655
2.2.11.26 Uplink Data Transmission Duration Except that for Small Packets.................................................................656
2.2.12 Measurement related to PDCP (Traffic.PDCP.Cell).............................................................................................657
2.2.12.1 Number of Discarded Downlink PDCP SDUs...................................................................................................662
2.2.12.2 Downlink ROHC Compression Rate of Headers...............................................................................................665
2.2.12.3 Downlink ROHC Compression Rate..................................................................................................................667
2.2.12.4 Decompression Failure Rate of Uplink PDCP SDUs After the ROHC.............................................................668
2.2.12.5 Number of Transmitted Downlink Traffic PDCP SDUs for DRB Services in a Cell over the Uu Interface
..........................................................................................................................................................................................669
2.2.12.6 Uplink ROHC Compression Rate of Headers....................................................................................................672
2.2.12.7 Uplink ROHC Compression Rate.......................................................................................................................674
2.2.13 Measurement related to Paging (Paging.Cell).......................................................................................................675
2.2.13.1 Number of Received Paging Messages over the S1 Interface in a Cell.............................................................676
2.2.13.2 Number of UEs Contained in Paging Messages Transmitted over the Uu Interface in a Cell...........................677
2.2.13.3 Number of Successful Paging Responses from the UE in a Cell.......................................................................679
2.2.13.4 Number of Discarded Paging Messages from the MME to UEs in a Cell.........................................................680
2.2.13.5 Number of Paging Messages Transmitted Due to System Information Changes..............................................681
2.2.13.6 Number of Paging Messages Discarded due to Paging Channel Congestion....................................................682
2.2.14 Measurement related to securmode (SecurMode.Cell).........................................................................................683
2.2.14.1 Number of Security Mode Setups in a Cell........................................................................................................684
2.2.15 Measurement related to RA (RA.Cell)..................................................................................................................688
2.2.15.1 Number of Times the Contention Preamble Is Received...................................................................................694
2.2.15.2 Number of Times the Random Access Response Message Is Sent After the Contention Preamble Is Received
..........................................................................................................................................................................................695
2.2.15.3 Number of Times the Contention Resolution Message Is Sent After the Contention Preamble Is Received
..........................................................................................................................................................................................697
2.2.15.4 Number of Times the Non-Contention-Based Preamble Is Received................................................................700
2.2.15.5 Number of Times the Random Access Response Message Is Sent After the Non-Contention-Based Preamble Is
Received...........................................................................................................................................................................702
2.2.15.6 Number of Times the UE Msg3 Response Message Is Received in the Handover-Triggered Non-Contention-
Based RA Procedure.........................................................................................................................................................704
Issue 08 (2014-03-14) Huawei Proprietary and Confidential xiii

2.2.15.7 Number of Times the TA with a Specific Value Range in a UE-Initiated Random Access Procedure in a Cell
..........................................................................................................................................................................................705
2.2.16 Measurement related to PWR (ChMeas.Pwr.Cell)................................................................................................710
2.2.16.1 Downlink Transmit Power..................................................................................................................................712
2.2.16.2 Interference and Noise Received by Each PRB in a Cell...................................................................................713
2.2.16.3 Receive Power of interference and noise detected of each PRB in the UL UpPTS...........................................715
2.2.16.4 Receive Power of the first Symbol in First UL Subframe..................................................................................716
2.2.16.5 Receive Power of the seventh (or fifth) Symbol in First UL Subframe.............................................................717
2.2.16.6 Receive Power of the first Symbol in Last UL Subframe..................................................................................718
2.2.16.7 Receive Power of the twelfth (or tenth) Symbol in the Last UL Subframe.......................................................719
2.2.17 Measurement related to MIMO (ChMeas.MIMO.Cell)........................................................................................720
2.2.17.1 Number of Used Downlink PRBs in MIMO Mode............................................................................................723
2.2.17.2 Number of RBs That Are Successfully Paired for VMIMO UEs in a Cell........................................................727
2.2.17.3 Number of RBs That Can Be Paired for VMIMO UEs in a Cell.......................................................................728
2.2.17.4 Number of RBs for MIMO UEs That Are Successfully Paired for MUBF in a Cell.........................................729
2.2.17.5 Number of RBs for MIMO UEs That Can Be Paired for MUBF in a Cell........................................................730
2.2.17.6 Number of Used Downlink PRBs in BF Mode..................................................................................................731
2.2.18 Measurement related to CQI (ChMeas.CQI.Cell).................................................................................................732
2.2.18.1 Number of Wideband CQI Reports in a Cell.....................................................................................................755
2.2.18.2 Number of Periodic Wideband CQI Reports in Single-Codeword Transmission in a Cell...............................762
2.2.18.3 Number of Aperiodic Wideband CQI Reports in Single-Codeword Transmission in a Cell.............................770
2.2.18.4 Number of Periodic Wideband CQI Reports for Codeword 0 in Dual-Codeword Transmission in a Cell.......777
2.2.18.5 Number of Aperiodic Wideband CQI Reports for Codeword 0 in Dual-Codeword Transmission in a Cell
..........................................................................................................................................................................................784
2.2.18.6 Number of Periodic Wideband CQI Reports for Codeword 1 in Dual-Codeword Transmission in a Cell.......791
2.2.18.7 Number of Aperiodic Wideband CQI Reports for Codeword 1 in Dual-Codeword Transmission in a Cell
..........................................................................................................................................................................................798
2.2.19 Measurement related to MCS (ChMeas.MCS.Cell)..............................................................................................805
2.2.19.1 Number of Times an MCS Index Is Scheduled on the PUSCH.........................................................................837
2.2.19.2 Number of Times a Specific MCS Index Is Scheduled on the PDSCH.............................................................853
2.2.19.3 Number of PRBs on the PUSCH Using a Specified MCS for Scheduling in a Cell..........................................869
2.2.19.4 Number of PRBs on the PDSCH Using a Specific MCS index for Scheduling in a Cell..................................879
2.2.20 Measurement related to PRB (ChMeas.PRB.Cell)................................................................................................921
2.2.20.1 Number of Used Uplink PRBs...........................................................................................................................928
2.2.20.2 Number of Used Downlink PRBs......................................................................................................................930
2.2.20.3 Number of Used PUCCH...................................................................................................................................931
2.2.20.4 Number of OFDM Symbols Occupied by the PDCCH......................................................................................932
2.2.20.5 Number of PDCCH CCEs used in a cell............................................................................................................934
2.2.20.6 Average Number of PRBs Occupied by CA UEs in a Cell................................................................................936
2.2.20.7 Average Number of Available PRBs in a Cell...................................................................................................938
2.2.20.8 Average Number of PRBs Used by CEUs in a Cell...........................................................................................940
2.2.20.9 Average Number of PRBs Allocated for Frequency Selective Scheduling.......................................................941
Issue 08 (2014-03-14) Huawei Proprietary and Confidential xiv

2.2.20.10 Average Number of PRBs Allocated for Uplink Pre-scheduling.....................................................................943

2.2.20.11 Number of Times of DTX for PDCCH Resource Allocation with a Specific Aggregation Level in a Cell
..........................................................................................................................................................................................944
2.2.20.12 Number of Times of Successful PDCCH Resource Allocations with a Specific Aggregation Level..............946
2.2.21 Measurement related to MAC (Traffic.MAC.Cell)...............................................................................................948
2.2.21.1 Total Number of Bits of TBs Transmitted on the BCH.....................................................................................957
2.2.21.2 Total Number of Bits of TBs Transmitted on the PCH......................................................................................958
2.2.21.3 Number of TBs Initially Transmitted on the Downlink SCH............................................................................959
2.2.21.4 Number of Bits of TBs Initially Transmitted on the Downlink SCH.................................................................962
2.2.21.5 Number of TBs Retransmitted on the Downlink SCH.......................................................................................964
2.2.21.6 Number of Bits of TBs Retransmitted on the Downlink SCH...........................................................................966
2.2.21.7 Number of TBs Initially Transmitted on the Uplink SCH.................................................................................968
2.2.21.8 Number of Bits of TBs Initially Transmitted on the Uplink SCH......................................................................969
2.2.21.9 Number of TBs Retransmitted over the Uplink SCH.........................................................................................971
2.2.21.10 Number of Bits of TBs Retransmitted on the Uplink SCH..............................................................................973
2.2.21.11 Number of Downlink Error TBs After Initial Transmission............................................................................975
2.2.21.12 Number of Downlink Error TBs After the Maximum Number of Retransmissions Is Reached.....................977
2.2.21.13 Number of Uplink Error TBs After Initial Transmission.................................................................................979
2.2.21.14 Number of Uplink Error TBs After the Maximum Number of Retransmissions Is Reached..........................981
2.2.21.15 Maximum Traffic Volume for MAC TBs in a Cell..........................................................................................982
2.2.22 Measurement related to the number of User (Traffic.User.Cell)...........................................................................984
2.2.22.1 Number of Users in a Cell..................................................................................................................................994
2.2.22.2 Number of Cell Edge Users in a Cell.................................................................................................................996
2.2.22.3 Number of UEs with Data in the Uplink Buffer.................................................................................................998
2.2.22.4 Number of UEs with Data in the Downlink Buffer..........................................................................................1000
2.2.22.5 Number of UL Synchronized Users in a Cell...................................................................................................1001
2.2.22.6 Number of UEs Transmitting or Receiving Data in a Cell...............................................................................1002
2.2.22.7 Number of UL CoMP UEs in a Cell.................................................................................................................1004
2.2.22.8 Number of CA UEs in a Cell............................................................................................................................1005
2.2.22.9 Average Number of Activated UEs with a Specific QCI in the Uplink Buffer...............................................1008
2.2.22.10 Average Number of Activated UEs with a Specific QCI in the Downlink Buffer.........................................1012
2.2.22.11 Number of UEs Configured with SRS Resources in a Cell...........................................................................1016
2.2.22.12 Number of UEs on Which TTI Bundling Takes Effect in a Cell...................................................................1018
2.2.22.13 Number of UEs on Which ROHC Takes Effect in a Cell..............................................................................1019
2.2.22.14 Number of UEs on Which DRX Takes Effect in a Cell.................................................................................1020
2.2.22.15 Number of Activated UEs in the Downlink in a Cell.....................................................................................1021
2.2.22.16 Number of Activated UEs in the Uplink in a Cell..........................................................................................1022
2.2.22.17 Number of Activated UEs in a Cell................................................................................................................1024
2.2.23 Measurement related to IRATHOOUT (HO.IRAT.Out.Cell).............................................................................1025
2.2.23.1 Number of Inter-RAT Handover Attempts from E-UTRAN to CDMA2000 Network...................................1055
2.2.23.2 Number of Inter-RAT Handovers Executions from E-UTRAN to CDMA2000 Network..............................1056
2.2.23.3 Number of Successful Inter-RAT Handovers from E-UTRAN to CDMA2000 Network...............................1058
Issue 08 (2014-03-14) Huawei Proprietary and Confidential xv

2.2.23.4 Number of Inter-RAT Handover Attempts from E-UTRAN to WCDMA Network.......................................1060

2.2.23.5 Number of Inter-RAT Handovers Executions from E-UTRAN to WCDMA Network...................................1061
2.2.23.6 Number of Successful Inter-RAT Handovers from E-UTRAN to WCDMA Network...................................1063
2.2.23.7 Number of Inter-RAT Handover Attempts from E-UTRAN to GERAN........................................................1065
2.2.23.8 Number of Inter-RAT Handovers Executions from E-UTRAN to GERAN....................................................1067
2.2.23.9 Number of Successful Inter-RAT Handovers from E-UTRAN to GERAN....................................................1069
2.2.23.10 Number of Inter-RAT Handover Attempts from E-UTRAN to TD-SCDMA Network................................1071
2.2.23.11 Number of Inter-RAT Handovers Executions from E-UTRAN to TD-SCDMA Network............................1073
2.2.23.12 Number of Successful Inter-RAT Handovers from E-UTRAN to TD-SCDMA Network............................1074
2.2.23.13 Number of Inter-RAT Handover Failures for Different Causes.....................................................................1076
2.2.23.14 Number of Inter-RAT Blind Handover Attempts from E-UTRAN to Another System................................1084
2.2.23.15 Number of Blind Handover Executions from E-UTRAN to Another System...............................................1087
2.2.23.16 Number of successful Inter-RAT Blind Handovers from E-UTRAN to Another System ............................1090
2.2.23.17 Number of Indicators for CSFB to Another System......................................................................................1093
2.2.23.18 Number of CSFB Responses to MMEs..........................................................................................................1096
2.2.23.19 Number of Procedures for CSFB to Another System.....................................................................................1099
2.2.23.20 Number of Inter-RAT Redirection Preparations from E-UTRAN to Another System..................................1111
2.2.23.21 Number of Inter-RAT Redirections from E-UTRAN to Another System.....................................................1113
2.2.23.22 Number of Inter-RAT Handover Attempts from E-UTRAN to WCDMA network for SRVCC..................1116
2.2.23.23 Number of Inter-RAT Handover Executions from E-UTRAN to WCDMA network for SRVCC...............1117
2.2.23.24 Number of Successful Inter-RAT Handovers from E-UTRAN to WCDMA Network for SRVCC..............1119
2.2.23.25 Number of Inter-RAT Handover Attempts from E-UTRAN to GERAN for SRVCC..................................1120
2.2.23.26 Number of Inter-RAT Handover Executions from E-UTRAN to GERAN for SRVCC...............................1122
2.2.23.27 Number of Successful Inter-RAT Handovers from E-UTRAN to GERAN for SRVCC...............................1123
2.2.23.28 Number of Inter-RAT Handover Attempts from E-UTRAN to TD-SCDMA Network for SRVCC............1125
2.2.23.29 Number of Inter-RAT Handover Executions from E-UTRAN to TD-SCDMA Network for SRVCC.........1126
2.2.23.30 Number of Successful Inter-RAT Handovers from E-UTRAN to TD-SCDMA network for SRVCC.........1128
2.2.23.31 Number of LCS-triggered CS Fallback Indicators Received by the eNodeB................................................1129
2.2.23.32 Number of Responses Sent from the eNodeB to MMEs for CSFB Triggered by LCS.................................1131
2.2.23.33 Number of CCO Executions from E-UTRAN to GERAN.............................................................................1133
2.2.23.34 Number of Successful CCOs from E-UTRAN to GERAN............................................................................1135
2.2.23.35 Number of Inter-RAT Handover Initiation Failures Because the Adjacent Cell is not the NRT of the Source Cell
........................................................................................................................................................................................1137
2.2.23.36 Number of CSFB Preparation Failures Because of Process Conflict.............................................................1141
2.2.23.37 Number of Handover Preparation Attempts from E-UTRAN to WCDMA Network Triggered Because of High
Load................................................................................................................................................................................1142
2.2.23.38 Number of Inter-RAT Handover Execution Attempts Triggered Because of High Load..............................1145
2.2.23.39 Number of Successful Inter-RAT Handover Executions Triggered Because of High Load..........................1147
2.2.23.40 Number of Redirections from E-UTRAN to WCDMA Network Triggered Because of High Load.............1149
2.2.23.41 Number of Inter-RAT Handover Attempts from E-UTRAN to WCDMA Network Triggered for UEs to Go back
to the HPLMN................................................................................................................................................................1151
Issue 08 (2014-03-14) Huawei Proprietary and Confidential xvi

2.2.23.42 Number of Inter-RAT Handover Executions from E-UTRAN to WCDMA Network Triggered for UEs to Go
back to the HPLMN........................................................................................................................................................1152
2.2.23.43 Number of Inter-RAT Handovers from E-UTRAN to WCDMA Network Triggered for UEs to Go back to the
HPLMN..........................................................................................................................................................................1154
2.2.23.44 Number of Inter-RAT Handover Executions from E-UTRAN to WCDMA Network Triggered for UEs That Do
not Transmit or Receive Data.........................................................................................................................................1156
2.2.23.45 Number of Successful Inter-RAT Handovers from E-UTRAN to WCDMA Network Triggered for UEs That Do
not Transmit or Receive Data.........................................................................................................................................1158
2.2.23.46 Number of LCS-based Inter-RAT Handover Executions for SRVCC...........................................................1160
2.2.23.47 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During Inter-RAT
Handover Executions from E-UTRAN to Another System...........................................................................................1165
2.2.23.48 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During Inter-RAT
Handover Executions from E-UTRAN to Another System for SRVCC........................................................................1169
2.2.23.49 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During CCO Executions
from E-UTRAN to GERAN...........................................................................................................................................1172
2.2.23.50 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During CSFB-based Inter-
RAT Handover Executions from E-UTRAN to Another System..................................................................................1174
2.2.24 Measurement related to IRATHOIN (HO.IRAT.In.Cell)...................................................................................1177
2.2.24.1 Success Rate of Inter-RAT Handovers from E-UTRAN to CDMA2000 Network.........................................1181
2.2.24.2 Success Rate of Inter-RAT Handovers from E-UTRAN to WCDMA Network..............................................1182
2.2.24.3 Success Rate of Inter-RAT Handovers from E-UTRAN to GERAN...............................................................1183
2.2.24.4 Number of Inter-RAT Handover Attempts from GERAN to E-UTRAN........................................................1184
2.2.24.5 Number of Inter-RAT Handover Preparation from GERAN to E-UTRAN.....................................................1186
2.2.24.6 Number of Successful Inter-RAT Handovers from GERAN to E-UTRAN....................................................1187
2.2.24.7 Number of Inter-RAT inter-RAT Handover Preparation Failures for Different Causes in a Cell...................1189
2.2.24.8 Number of Inter-RAT Handover Attempts from TD-SCDMA Network to E-UTRAN..................................1192
2.2.24.9 Number of Inter-RAT Handover Preparation from TD-SCDMA Network to E-UTRAN..............................1194
2.2.24.10 Number of Successful Inter-RAT Handovers from TD-SCDMA Network to E-UTRAN............................1195
2.2.24.11 Number of Inter-RAT Handover Attempts from WCDMA Network to E-UTRAN.....................................1197
2.2.24.12 Number of Inter-RAT Handover Preparation from WCDMA Network to E-UTRAN..................................1199
2.2.24.13 Number of Successful Inter-RAT Handovers from WCDMA Network to E-UTRAN.................................1200
2.2.25 Measurement related to Intra eRan HOOUT (HO.eRAN.Out.Cell)...................................................................1202
2.2.25.1 Number of Intra-eNodeB Outgoing Handover Attempts in a Cell...................................................................1213
2.2.25.2 Number of Intra-eNodeB Outgoing Handovers Executions in a Cell..............................................................1214
2.2.25.3 Number of Successful Intra-eNodeB Outgoing Handovers in a Cell...............................................................1216
2.2.25.4 Number of Inter-eNodeB Outgoing Handover Attempts in a Cell...................................................................1219
2.2.25.5 Number of Inter-eNodeB Outgoing Handovers Executions in a Cell..............................................................1222
2.2.25.6 Number of Successful Inter-eNodeB Outgoing Handovers in a Cell...............................................................1224
2.2.25.7 Intra-Frequency Handover Success Rate..........................................................................................................1230
2.2.25.8 Inter-Frequency Handover Success Rate..........................................................................................................1231
2.2.25.9 Number of Outgoing Blind Handover Attempts in a Cell................................................................................1232
2.2.25.10 Number of Outgoing Blind Handovers Executions in a Cell.........................................................................1234
2.2.25.11 Number of Successful Outgoing Blind Handovers in a Cell..........................................................................1237
Issue 08 (2014-03-14) Huawei Proprietary and Confidential xvii

2.2.25.12 Number of Outgoing Handover Failures for Different Causes in a Cell........................................................1244

2.2.25.13 Number of Intra-RAT Redirections................................................................................................................1250
2.2.25.14 Number of Intra-RAT Handover Initiation Failures Because the Adjacent Cell is not on the NRT of the Source
Cell..................................................................................................................................................................................1251
2.2.25.15 Number of Inter-Frequency Handover Preparation Attempts Triggered Because of High Load...................1255
2.2.25.16 Number of Inter-Frequency Handover Execution Attempts Triggered Because of High Load.....................1257
2.2.25.17 Number of Successful Inter-Frequency Handover Executions Triggered Because of High Load.................1259
2.2.25.18 Number of Inter-Frequency Outgoing Handover Attempts Triggered for UEs to Go back to the HPLMN
........................................................................................................................................................................................1266
2.2.25.19 Number of Inter-Frequency Outgoing Handover Executions Triggered for UEs to Go back to the HPLMN
........................................................................................................................................................................................1268
2.2.25.20 Number of Successful Inter-Frequency Outgoing Handovers Triggered for UEs to Go Back to the HPLMN
........................................................................................................................................................................................1270
2.2.25.21 Number of Intra-Frequency Handover Execution Attempts Triggered for UEs that do not transmit or receive
data..................................................................................................................................................................................1276
2.2.25.22 Number of Successful Intra-Frequency Handover Executions Triggered for UEs that do not transmit or receive
data..................................................................................................................................................................................1278
2.2.25.23 Number of Inter-Frequency Handover Execution Attempts Triggered for UEs That Do not Transmit or Receive
Data.................................................................................................................................................................................1285
2.2.25.24 Number of Successful Inter-Frequency Handover Executions Triggered for UEs That Do not Transmit or Receive
Data.................................................................................................................................................................................1287
2.2.25.25 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During S1-based Outgoing
Handover Executions......................................................................................................................................................1294
2.2.25.26 Number of Successful Intra-eNodeB Outgoing Handovers Where RRC Connections Are Reestablished to the
Source Cell for UEs in a Cell.........................................................................................................................................1296
2.2.25.27 Number of Successful Inter-eNodeB Outgoing Handovers Where RRC Connections Are Reestablished to the
Source Cell for UEs in a Cell.........................................................................................................................................1298
2.2.25.28 Number of successful blind outgoing handovers where RRC connections are reestablished to the source cell for
UEs in a cell....................................................................................................................................................................1302
2.2.26 Measurement related to Intra eRan HOIN (HO.eRAN.In.Cell)..........................................................................1306
2.2.26.1 Number of Intra-eNodeB Incoming Handover Attempts in a Cell...................................................................1311
2.2.26.2 Number of Intra-eNodeB Incoming Handovers Executions in a Cell..............................................................1312
2.2.26.3 Number of Successful Intra-eNodeB Incoming Handovers in a Cell...............................................................1314
2.2.26.4 Number of Inter-eNodeB Incoming Handover Attempts in a Cell...................................................................1316
2.2.26.5 Number of Inter-eNodeB Incoming Handovers Executions in a Cell..............................................................1318
2.2.26.6 Number of Successful Inter-eNodeB Incoming Handovers in a Cell...............................................................1320
2.2.26.7 Number of Incoming Handover Failures for Different Causes in a Cell..........................................................1324
2.2.26.8 Number of Path Switch Requests for Inter-eNodeB Incoming Handovers in a Cell.......................................1329
2.2.26.9 Number of Successful Path Switches for inter-eNodeB Incoming Handovers in a Cell..................................1331
2.2.26.10 Number of Incoming Handover Failures Because of High Load in a Cell....................................................1332
2.2.26.11 Number of HANDOVER CANCEL Messages Received by the Target Cell from the Source Cell During Inter-
eNodeB Incoming Handover Executions in a Cell.........................................................................................................1334
2.2.27 Measurement related to Intra eRan X2 HOOUT (HO.eRAN.X2Out.Cell).........................................................1337
2.2.27.1 Number of X2-based Outgoing Handover Attempts in a Cell.........................................................................1340
2.2.27.2 Number of X2-based Outgoing Handover Executions in a Cell......................................................................1342
Issue 08 (2014-03-14) Huawei Proprietary and Confidential xviii

2.2.27.3 Number of Successful X2-based Outgoing Handovers in a Cell.....................................................................1344

2.2.27.4 Number of X2-based Outgoing Handover Failures for Different Causes in a Cell..........................................1348
2.2.27.5 Number of Successful X2-based Outgoing Handovers Where RRC Connections Are Reestablished to the Source
Cell for UEs in a Cell.....................................................................................................................................................1349
2.2.28 Measurement related to Intra eRan DRX HOOUT (HO.DRX.Out.Cell)............................................................1352
2.2.28.1 Number of Intra-eNodeB Outgoing Handovers Executions in the DRX State................................................1355
2.2.28.2 Number of Successful Intra-eNodeB Outgoing Handovers in the DRX State.................................................1357
2.2.28.3 Number of Inter-eNodeB Outgoing Handovers Executions in the DRX State................................................1360
2.2.28.4 Number of Successful Inter-eNodeB Outgoing Handovers in the DRX State.................................................1362
2.2.29 Measurement related to Packet (Traffic.Packet.Cell)..........................................................................................1369
2.2.29.1 Total Processing Delay of Downlink PDCP SDUs for DRB Services in a Cell..............................................1380
2.2.29.2 Number of Successfully Transmitted Downlink PDCP SDUs for DRB Services in a Cell.............................1384
2.2.29.3 Total Number of Discarded Downlink PDCP SDUs for DRB Services in a Cell............................................1388
2.2.29.4 Total Number of Transmitted Downlink PDCP SDUs for DRB Services in a Cell........................................1392
2.2.29.5 Total Number of Discarded Uplink PDCP SDUs for DRB Services in a Cell................................................1396
2.2.29.6 Total Number of Expected Uplink Data Packets for DRB Services in a Cell..................................................1400
2.2.30 Measurement related to DFEE (ChMeas.DFEE.Cell).........................................................................................1404
2.2.30.1 Duration of Energy Saving and Emission Reduction.......................................................................................1405
2.2.31 Measurement related to LCS in a cell (LCS.Cell)...............................................................................................1407
2.2.31.1 Number of E-CID Measurement Requests in a Cell........................................................................................1408
2.2.31.2 Number of Successful E-CID Measurement Requests in a Cell......................................................................1410
2.2.32 Measurements related to EMC (EMC.Cell)........................................................................................................1411
2.2.32.1 Number of Outgoing Handover Attempts for Emergency Calls in a Cell........................................................1413
2.2.32.2 Number of Executed Outgoing Handovers for Emergency Calls in a Cell......................................................1416
2.2.32.3 Number of Successful Outgoing Handovers for Emergency Calls in a Cell....................................................1419
2.2.32.4 Number of E-RAB Setup Attempts for Emergency Calls in a Cell.................................................................1425
2.2.32.5 Number of Successful E-RAB Setups for Emergency Calls in a Cell.............................................................1427
2.2.32.6 Number of Normal E-RAB Releases Due to Outgoing Handovers for Emergency Calls in a Cell.................1430
2.2.32.7 Number of Abnormal E-RAB Releases Due to Outgoing Handovers for Emergency Calls in a Cell.............1432
2.2.32.8 Number of Abnormal Releases of E-RABs for Emergency Calls in a Cell.....................................................1434
2.2.32.9 Number of Normal E-RAB Releases for Emergency Calls in a Cell...............................................................1436
2.2.33 Measurements related to UECNTX (UeCntx.Rel.Cell)......................................................................................1439
2.2.33.1 Number of Abnormal UE Context Releases in a Cell......................................................................................1442
2.2.33.2 Number of Normal UE Context Releases in a Cell..........................................................................................1445
2.2.33.3 Number of UE Context Releases due to High Mobility of UEs.......................................................................1446
2.2.33.4 Number of UE Context Releases During an Inter-RAT Measurement............................................................1448
2.2.33.5 Number of UE Context Releases Initiated by the eNodeB in a Cell................................................................1450
2.2.33.6 Number of UE Context Releases Initiated by the eNodeB due to Different Causes in a Cell.........................1451
2.2.33.7 Number of UE Context Releases Initiated by the MME in a Cell....................................................................1454
2.2.33.8 Number of UE Context Releases Initiated by the MME due to a Normal Cause in a Cell..............................1455
2.2.34 Measurement related to SFN (SFN.Cell)............................................................................................................1456
Issue 08 (2014-03-14) Huawei Proprietary and Confidential xix

2.2.34.1 Number of Times When the Downlink Attribute of a UE Changes from Independent-scheduling to Joint-
scheduling.......................................................................................................................................................................1459
2.2.34.2 Number of Times When the Downlink Attribute of a UE Changes from Joint-scheduling to Independent-
scheduling.......................................................................................................................................................................1459
2.2.34.3 Number of Times that the Downlink Target RRU of a UE in an SFN Cell Changes......................................1460
2.2.34.4 Average Number of Joint-scheduling UEs in the Uplink.................................................................................1461
2.2.34.5 Average number of working RRUs for a joint-scheduling UE in the uplink...................................................1462
2.2.34.6 Number of Times When the Uplink Attribute of a UE Changes from Independent Scheduling to Joint Scheduling
in an SFN Cell................................................................................................................................................................1463
2.2.34.7 Number of Times When the Uplink Attribute of a UE Changes from Joint-scheduling to Independent-scheduling
in an SFN cell.................................................................................................................................................................1464
2.2.34.8 Number of Times that the Uplink Target RRU of a UE in an SFN Cell Changes...........................................1465
2.2.34.9 Average Number of Joint-scheduling UEs in the Downlink............................................................................1466
2.2.34.10 Average Number of Working RRUs for a Joint-scheduling UE in the Downlink.........................................1467
2.2.35 Measurements related to UECNTX Modify (UeCntx.Mod.Cell).......................................................................1469
2.2.35.1 Number of UE Context Modification Attempts...............................................................................................1470
2.2.35.2 Number of Successful UE Context Modifications...........................................................................................1471
2.2.36 Measurement related to CA (CA.Cell)................................................................................................................1472
2.2.36.1 Total Number of Abnormal E-RAB Releases for CA UEs in a Cell................................................................1474
2.2.36.2 Total Number of Normal E-RAB Releases for CA UEs in a Cell....................................................................1476
2.2.36.3 Number of Handover Attempts for CA UEs in a Cell......................................................................................1479
2.2.36.4 Number of Handover Executions for CA UEs in a Cell...................................................................................1482
2.2.36.5 Number of Successful Handovers for CA UEs in a Cell..................................................................................1484
2.2.37 Measurement related to RLC (Traffic.RLC.Cell)................................................................................................1491
2.2.37.1 Number of Bits of Uplink RLC ARQ PDUs Retransmitted by UEs................................................................1493
2.2.37.2 Number of Bits of Downlink RLC ARQ PDUs Retransmitted by the eNodeB...............................................1494
2.2.37.3 Number of Received Uplink RLC ARQ PDUs................................................................................................1495
2.2.37.4 Number of Transmitted Downlink RLC ARQ PDUs.......................................................................................1495
2.2.37.5 Number of Received Uplink RLC ARQ PDUs Retransmitted by UEs............................................................1496
2.2.37.6 Number of Downlink RLC ARQ PDUs Retransmitted by UEs.......................................................................1497
2.2.37.7 Number of Downlink RLC PDUs Failed to Be Sent to UEs in AM Mode in a Cell.......................................1498
2.2.38 Measurement related to Reserve Cell (Reserve.Cell)..........................................................................................1499
2.2.38.1 L.Reserve.1.......................................................................................................................................................1506
2.2.38.2 L.Reserve.2.......................................................................................................................................................1506
2.2.38.3 L.Reserve.3.......................................................................................................................................................1507
2.2.38.4 L.Reserve.4.......................................................................................................................................................1508
2.2.38.5 L.Reserve.5.......................................................................................................................................................1508
2.2.38.6 L.Reserve.6.......................................................................................................................................................1509
2.2.38.7 L.Reserve.7.......................................................................................................................................................1510
2.2.38.8 L.Reserve.8.......................................................................................................................................................1511
2.2.38.9 L.Reserve.9.......................................................................................................................................................1511
2.2.38.10 L.Reserve.10...................................................................................................................................................1512
Issue 08 (2014-03-14) Huawei Proprietary and Confidential xx

2.2.38.11 L.Reserve.11...................................................................................................................................................1513
2.2.38.12 L.Reserve.12...................................................................................................................................................1514
2.2.38.13 L.Reserve.13...................................................................................................................................................1514
2.2.38.14 L.Reserve.14...................................................................................................................................................1515
2.2.38.15 L.Reserve.15...................................................................................................................................................1516
2.2.38.16 L.Reserve.16...................................................................................................................................................1517
2.2.38.17 L.Reserve.17...................................................................................................................................................1517
2.2.38.18 L.Reserve.18...................................................................................................................................................1518
2.2.38.19 L.Reserve.19...................................................................................................................................................1519
2.2.38.20 L.Reserve.20...................................................................................................................................................1520
2.2.38.21 L.Reserve.21...................................................................................................................................................1520
2.2.38.22 L.Reserve.22...................................................................................................................................................1521
2.2.38.23 L.Reserve.23...................................................................................................................................................1522
2.2.38.24 L.Reserve.24...................................................................................................................................................1523
2.2.38.25 L.Reserve.25...................................................................................................................................................1523
2.2.38.26 L.Reserve.26...................................................................................................................................................1524
2.2.38.27 L.Reserve.27...................................................................................................................................................1525
2.2.38.28 L.Reserve.28...................................................................................................................................................1526
2.2.38.29 L.Reserve.29...................................................................................................................................................1526
2.2.38.30 L.Reserve.30...................................................................................................................................................1527
2.2.39 Measurement related to CellComb (CellComb.Cell)..........................................................................................1528
2.2.39.1 Number of Downlink Joint-scheduling UEs in a Combination Cell................................................................1530
2.2.39.2 Average Number of Work Physical Cells of Downlink Joint-scheduling UEs in a Combination Cell...........1531
2.2.39.3 Number of Times an Independent-scheduling UE Becomes a Joint-scheduling UE in Downlink in a Combination
Cell..................................................................................................................................................................................1532
2.2.39.4 Number of Times a Joint-scheduling UE Becomes an Independent-scheduling UE in Downlink in a Combination
Cell..................................................................................................................................................................................1533
2.2.39.5 Number of Times the Downlink Target Physical Cell of a UE in a Combination Cell Changes in a Combination
Cell..................................................................................................................................................................................1533
2.2.39.6 Number of Uplink Joint-scheduling UEs in a Combination Cell.....................................................................1534
2.2.39.7 Average Number of Work Physical Cells of Uplink Joint-scheduling UEs in a Combination Cell in a Combination
Cell..................................................................................................................................................................................1535
2.2.39.8 Number of Times an Independent-scheduling UE Becomes a Joint-scheduling UE in Uplink in a Combination
cell..................................................................................................................................................................................1536
2.2.39.9 Number of Times a Joint-scheduling UE Becomes an Independent-scheduling UE in Uplink in a Combination
Cell..................................................................................................................................................................................1537
2.2.39.10 Number of Times the Uplink Target Physical Cell of a UE in a Combination Cell Changes in a Combination
Cell..................................................................................................................................................................................1537
2.2.40 Measurement related to Measure Reports (ChMeas.MeasRpt.Cell)...................................................................1538
2.2.40.1 Number of Measurement Control Messages Sent by the eNodeB in a Cell.....................................................1539
2.2.41 Measurement related to UECNTX establish (UeCntx.Est.Cell).........................................................................1541
2.2.41.1 Number of UE Context Setup Attempts in a Cell............................................................................................1542
2.2.41.2 Number of Successful UE Context Setups in a Cell........................................................................................1544
Issue 08 (2014-03-14) Huawei Proprietary and Confidential xxi

2.2.42 Measurement related to UECNTX establish failure (UeCntx.EstFail.Cell)........................................................1546

2.2.42.1 Number of UE Context Setup Failures for Different Causes in a Cell ............................................................1547
2.2.43 Measurement related to Intra eRan X2 HOIN (HO.eRAN.X2In.Cell)...............................................................1552
2.2.43.1 Number of X2-based Incoming Handover Attempts in a Cell.........................................................................1553
2.2.43.2 Number of X2-based Incoming Handover Executions in a Cell......................................................................1555
2.2.43.3 Number of Successful X2-based Incoming Handovers in a Cell.....................................................................1556
2.2.44 Measurement related to Thruput Distribution (Traffic.Thruput.PDF.Cell).........................................................1559
2.2.44.1 Distribution of the Downlink Throughput in a Cell.........................................................................................1581
2.2.44.2 Distribution of the Uplink Throughput in a Cell..............................................................................................1620
2.3 Measurement of S1-LINK performance between eNodeB and MME (Sig.S1).......................................................1624
2.3.1 Measurement related to S1 link (Sig.S1)...............................................................................................................1624
2.3.1.1 Number of S1 Interface Setups...........................................................................................................................1625
2.3.1.2 Duration of S1 Link Unavailability....................................................................................................................1627
2.4 Measurement of X2-LINK performance between eNodeB and neighbor eNodeB (Sig.X2)...................................1628
2.4.1 Measurement related to X2 link (Sig.X2).............................................................................................................1629
2.4.1.1 Number of X2 Link Setup Attempts...................................................................................................................1630
2.4.1.2 Number of Successful X2 Link Setups...............................................................................................................1632
2.4.1.3 Duration of X2 Link Unavailability...................................................................................................................1635
2.5 Measurement between two neighbor cell (NCell)....................................................................................................1636
2.5.1 Measurement related to Intra eRan NCELL HOOUT (HO.NCell.Cell)...............................................................1636
2.5.1.1 Number of Outgoing Handover Attempts Between Two Specific Cells............................................................1641
2.5.1.2 Number of Outgoing Handover Executions Between Two Specific Cells.........................................................1643
2.5.1.3 Number of Successful Outgoing Handovers Between Two Specific Cells........................................................1646
2.5.1.4 Number of Ping-Pong Handovers Between Two Specific Cells........................................................................1653
2.5.1.5 Number of Delayed Intra-RAT Handovers between two specific cells.............................................................1658
2.5.1.6 Number of Premature Intra-RAT Handovers between two specific cells..........................................................1660
2.5.1.7 Number of Responses for Abnormal Causes Received by the eNodeB from the MME During Outgoing Handover
Executions Between Two Specific Cells........................................................................................................................1663
2.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........................................................................................................1665
2.5.1.9 Number of intra-RAT handovers to a wrong cell between two specific cells....................................................1668
2.6 Measurement of Operator (Cell.Operator)...............................................................................................................1671
2.6.1 Measurement related to E-RAB establish for the operator (E-RAB.Est.Cell.Operator).......................................1672
2.6.1.1 Number of E-RAB Setup Attempts for a Specific Operator in a Cell................................................................1679
2.6.1.2 Number of Successful E-RAB Setups for a Specific Operator in a Cell............................................................1686
2.6.1.3 Total Number of E-RAB Setup Attempts for Incoming Handovers for a Specific Operator.............................1693
2.6.1.4 Total Number of Successful E-RAB Setups for Incoming Handovers for a Specific Operator.........................1696
2.6.2 Measurement related to E-RAB release for the operator (E-RAB.Rel.Cell.Operator).........................................1701
2.6.2.1 Number of Abnormal E-RAB Releases for a Specific Operator........................................................................1714
2.6.2.2 Number of Normal E-RAB Releases for a Specific Operator............................................................................1721
2.6.2.3 Number of Normal E-RAB Releases for Outgoing Handovers for a Specific Operator in a Cell.....................1729
2.6.2.4 Number of Abnormal E-RAB Releases for Outgoing Handovers for a Specific Operator................................1737
Issue 08 (2014-03-14) Huawei Proprietary and Confidential xxii

2.6.2.5 Number of Abnormal E-RAB Releases for Different Causes for a specific operator in a cell..........................1745
2.6.2.6 Number of E-RAB Releases Initiated by the eNodeB Because of the S1 RESET for a Specific Operator
........................................................................................................................................................................................1748
2.6.3 Measurement related to Thruput for the Operator (Traffic.Thruput.Cell.Operator).............................................1754
2.6.3.1 Uplink Traffic Volume for PDCP SDUs for a specified operator......................................................................1769
2.6.3.2 Receive Duration of Uplink PDCP SDUs for a specific Operator in a Cell.......................................................1775
2.6.3.3 Downlink Traffic Volume for PDCP SDUs for a Specific Operator in a Cell...................................................1782
2.6.3.4 Transmit Duration of Downlink PDCP SDUs for a Specific Operator in a Cell...............................................1789
2.6.3.5 Downlink Traffic Volume Sent in the Last TTI Before the Buffer Is empty for a Specific Operator...............1796
2.6.3.6 Data Transmit Duration Except the Last TTI Before the Downlink Buffer Is Empty for a Specific Operator
........................................................................................................................................................................................1803
2.6.3.7 Traffic Volume of Uplink PDCP SDUs Sent in the Last TTI Before the UE Buffer is Empty for a Specific Operator
........................................................................................................................................................................................1810
2.6.3.8 Uplink Data Transmit Duration Except the Last TTI Before the UE Buffer is Empty for a Specific Operator
........................................................................................................................................................................................1811
2.6.3.9 Uplink Traffic Volume of PDCP SDUs Scheduled for Small Packets for a Specific Operator.........................1813
2.6.3.10 Uplink Data Transmission Duration Except that for Small Packets for a Specific Operator...........................1814
2.6.4 Measurement related to the number of User for the Operator (Traffic.User.Cell.Operator).................................1815
2.6.4.1 Number of Users for a Specific Operator in a Cell............................................................................................1816
2.6.5 Measurement related to the RB number for the Operator (Traffic.RB.Cell.Operator).........................................1818
2.6.5.1 Average Number of PDSCH PRBs Used by a Specific Operator......................................................................1819
2.6.5.2 Average Number of PUSCH PRBs Used by a Specific Operator......................................................................1821
2.6.6 Measurement related to Intra eRan HOOUT for the operator (HO.eRAN.Out.Cell.Operator)............................1823
2.6.6.1 Number of Intra-eNodeB Outgoing Handover Attempts for a Specific Operator..............................................1830
2.6.6.2 Number of Intra-eNodeB Outgoing Handover Executions for a Specific Operator..........................................1832
2.6.6.3 Number of Successful Intra-eNodeB Outgoing Handovers for a Specific Operator..........................................1834
2.6.6.4 Number of Inter-eNodeB Outgoing Handover Attempts for a specified operator.............................................1837
2.6.6.5 Number of Performed Inter-eNodeB Outgoing Handovers for a specified operator.........................................1840
2.6.6.6 Number of Successful Inter-eNodeB Outgoing Handovers for a specified operator.........................................1843
2.6.6.7 Number of X2-based Outgoing Handover Attempts for a Specific Operator....................................................1850
2.6.6.8 Number of X2-based Outgoing Handover Executions for a Specific Operator.................................................1853
2.6.6.9 Number of Successful X2-based Outgoing Handovers for a specific operator..................................................1856
2.6.6.10 Number of Outgoing Blind Handover Attempts for a Specific Operator.........................................................1860
2.6.6.11 Number of Outgoing Blind Handover Executions for a Specific Operator......................................................1863
2.6.6.12 Number of Successful Outgoing Blind Handovers for a Specific Operator.....................................................1866
2.6.7 Measurement related to IRATHOOUT for the operator (HO.IRAT.Out.Cell.Operator)......................................1872
2.6.7.1 Number of Inter-RAT Handover Attempts from E-UTRAN to WCDMA Network for a Specific Operator
........................................................................................................................................................................................1876
2.6.7.2 Number of Inter-RAT Handover Executions from E-UTRAN to WCDMA Network for a Specific Operator
........................................................................................................................................................................................1878
2.6.7.3 Number of Successful Inter-RAT Handovers from E-UTRAN to WCDMA Network for a Specific Operator
........................................................................................................................................................................................1880
2.6.7.4 Number of Inter-RAT Handover Attempts from E-UTRAN to GERAN for a Specific Operator.....................1882
Issue 08 (2014-03-14) Huawei Proprietary and Confidential xxiii

2.6.7.5 Number of Inter-RAT Handover Executions from E-UTRAN to GERAN for a Specific Operator.................1884
2.6.7.6 Number of Successful Inter-RAT Handovers from E-UTRAN to GERAN for a Specific Operator.................1886
2.6.7.7 Number of Inter-RAT Blind Handover Attempts from E-UTRAN to Another System for a Specific Operator
........................................................................................................................................................................................1888
2.6.7.8 Number of Inter-RAT Blind Handover Executions from E-UTRAN to Another System for a Specific Operator
........................................................................................................................................................................................1891
2.6.7.9 Number of Successful Inter-RAT Blind Handovers from E-UTRAN to Another System for a Specific Operator
........................................................................................................................................................................................1894
2.6.8 Measurement related to Thruput Distribution for the Operator (Traffic.Thruput.PDF.Cell.Operator).................1897
2.6.8.1 Distribution of the Downlink Throughput in a Cell for a Specific Operator......................................................1920
2.6.8.2 Distribution of the Uplink Throughput in a Cell for a Specific Operator..........................................................1990
Issue 08 (2014-03-14) Huawei Proprietary and Confidential xxiv

Performance Counter Reference 1 Equipment and Transport Network Related Measurement
1 Equipment and Transport Network Related

Measurement
About This Chapter
1.1 Measurement of Ethernet port performance (ETHPORT)

1.2 Measurement of E1/T1 port performance (E1T1)
1.3 Measurement of PPP Link performance (PPP)
1.4 Measurement of MP Group performance (MPGRP)
1.5 Measurement of IP layer performance (IP)
1.6 Measurement of IP path performance (IPPath)
1.7 Measurement of Resource Group performance (RscGroup)
1.8 Measurement of IP PM performance (IPPM)
1.9 Measurement of SCTP performance (SCTP)
1.10 Measurement of IPv6 performance (IPv6)
1.11 Measurement of IPv6Path performance (IPv6Path)
1.12 Measurement of OMCH performance (OMCH)
1.13 Measurement of Tunnel performance (TUNNEL)
1.14 Measurement of TRUNK performance (TRUNK)
1.15 Measurement of firewall performance (Firewall)
1.16 Measurement of IKE performance (IKE)
1.17 Measurement of IPSec performance (IPSec)
1.18 Measurement of SCTP Link performance (SCTPLNK)
1.19 Measurement of UserPlaneHostIP performance (UserPlaneHostIP)
Issue 08 (2014-03-14) Huawei Proprietary and Confidential 1

1.20 Measurement of GTP-U performance (GTP-U)
1.21 Measurement of Board performance (Board)
1.22 Measurement of RRU performance (RRU)
1.23 Measurement of eNodeB performance (eNodeB)
1.24 Measurement of PMU performance (PMU)
1.25 NODE (NODE)
1.26 BBUBoard (BBUBoard)
1.27 GNSS (GNSS)

1.1 Measurement of Ethernet port performance (ETHPORT)

Overview
The object type FEGE Measurement contains the function subset related to the Ethernet port. It
represents the traffic volume of services and communication quality of the Ethernet port on the
transmission board in the base station.
FunctionSubSets
FunctionSubSet FunctionSubSet Name
Physical.FEGE Measurement related to Ethernet port
1.1.1 Measurement related to Ethernet port (Physical.FEGE)
Overview
The ETHPORT function subset measures the traffic volumes at the data link layer on an Ethernet
port, helping users to plan network. Figure 1-1 shows the position of the Ethernet port in the
TCP/IP model.
Figure 1-1

Counters
Counter ID Counter Name Counter Original Release
Description
1542455297 VS.FEGE.TxBytes Number of bytes in V100R008C00,and

the packets the mapping single-
successfully mode base station
transmitted on the versions that
Ethernet port introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455298 VS.FEGE.TxPack- Number of packets V100R008C00,and

ets successfully the mapping single-
transmitted on the mode base station
Ethernet port versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455299 VS.FEGE.RxBytes Number of bytes in V100R008C00,and

successfully received mode base station
on the Ethernet port versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455300 VS.FEGE.RxPack- Number of packets V100R008C00,and

ets successfully received the mapping single-
on the Ethernet port mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455301 VS.FEGE.RxErr- Number of error V100R008C00,and

Packets packets received on the mapping single-
the Ethernet port mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455302 VS.FEGE.TxMax- Maximum transmit V100R008C00,and

Speed rate on the Ethernet the mapping single-
port mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455303 VS.FEGE.TxMin- Minimum transmit V100R008C00,and

versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455304 VS.FEGE.TxMean Average transmit V100R008C00,and

versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455305 VS.FEGE.RxMax- Maximum receive V100R008C00,and

versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455306 VS.FEGE.RxMin- Minimum receive V100R008C00,and

versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455307 VS.FEGE.RxMean Average receive rate V100R008C00,and

Speed on the Ethernet port the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542460296 VS.FEGE.TxTo- Total transmit V100R008C00,and

talBW bandwidth on the the mapping single-
Ethernet port mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00


Description
1542460297 VS.FEGE.RxTo- Total receive V100R008C00,and

talBW bandwidth on the the mapping single-
Ethernet port mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
Counter Relationship
None
1.1.1.1 Number of Bytes on the Ethernet Port
Counters
Counter ID Counter Name Counter Network Element
Description
1542455297 VS.FEGE.TxBytes Number of bytes in DBS3900 WCDMA/

the packets BTS3900 WCDMA/
successfully BTS3900A
transmitted on the WCDMA/
Ethernet port BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455299 VS.FEGE.RxBytes Number of bytes in DBS3900 WCDMA/

the packets BTS3900 WCDMA/
successfully received BTS3900A
on the Ethernet port WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters provide the number of bytes in the packets successfully transmitted and the
number of bytes in the packets successfully received on an Ethernet port within a measurement
period, respectively. They reflect the traffic on the Ethernet port at the data link layer. The counter
value includes the number of bytes in the MAC header, VLAN flag, payload, and CRC field
that is at the end of a packet.
Measurement Points
The number of bytes in the packets successfully transmitted or successfully received on the
Ethernet port is sampled per second. At the end of a measurement period, the sum of these
sampling results is used as the value of the corresponding counter.
Formula
None
Unit
byte

Related Features
Counter Name Feature ID Feature Name
VS.FEGE.TxBytes Multi-mode: None

GSM: GBFD-118601 IP Transmission Introduction
UMTS: WRFD-050402 on Abis Interface
LTE: None IP Transmission Introduction

on Iub Interface
VS.FEGE.RxBytes Multi-mode: None


on Iub Interface
1.1.1.2 Number of Packets on the Ethernet Port
Counters
Description
1542455298 VS.FEGE.TxPack- Number of packets DBS3900 WCDMA/

ets successfully BTS3900 WCDMA/
transmitted on the BTS3900A
Ethernet port WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455300 VS.FEGE.RxPack- Number of packets DBS3900 WCDMA/

ets successfully received BTS3900 WCDMA/
on the Ethernet port BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455301 VS.FEGE.RxErr- Number of error DBS3900 WCDMA/

Packets packets received on BTS3900 WCDMA/
the Ethernet port BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters provide the number of transmitted packets, received packets, or error packets on
an Ethernet port within a measurement period. They reflect the traffic on and the transmission
quality of the Ethernet port at the data link layer. The FEGE.RxErrPackets counter provides the
number of error packets received on physical links and failed in CRC checks.
Measurement Points
The number of transmitted packets, received packets, or error packets is sampled per second. At
the end of a measurement period, the sum of these sampling results is used as the value of the
corresponding counter.
Formula
None

Unit
packet
Related Features
VS.FEGE.TxPackets Multi-mode: None


on Iub Interface
VS.FEGE.RxPackets Multi-mode: None


on Iub Interface
VS.FEGE.RxErrPackets Multi-mode: None


on Iub Interface
1.1.1.3 Rate on the Ethernet Port

Counters
Description
1542455302 VS.FEGE.TxMax- Maximum transmit DBS3900 WCDMA/

Speed rate on the Ethernet BTS3900 WCDMA/
port BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455303 VS.FEGE.TxMin- Minimum transmit DBS3900 WCDMA/

port BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455304 VS.FEGE.TxMean- Average transmit DBS3900 WCDMA/

port BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455305 VS.FEGE.RxMax- Maximum receive DBS3900 WCDMA/

port BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455306 VS.FEGE.RxMin- Minimum receive DBS3900 WCDMA/

port BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455307 VS.FEGE.RxMean- Average receive rate DBS3900 WCDMA/

Speed on the Ethernet port BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
The counters measure the transmit rate and the receive rate on the Ethernet port within a
measurement period. They indicate the traffic on the Ethernet port at the data link layer.
Measurement Points
The transmit rate or the receive rate on the Ethernet port is sampled per second. At the end of a
measurement period, the maximum, minimum, or average of these sampling results is used as
the value of the corresponding counter.
Formula
None
Unit
bit/s
Related Features
VS.FEGE.TxMaxSpeed Multi-mode: None


on Iub Interface
VS.FEGE.TxMinSpeed Multi-mode: None


on Iub Interface
VS.FEGE.TxMeanSpeed Multi-mode: None


on Iub Interface

VS.FEGE.RxMaxSpeed Multi-mode: None


on Iub Interface
VS.FEGE.RxMinSpeed Multi-mode: None


on Iub Interface
VS.FEGE.RxMeanSpeed Multi-mode: None


on Iub Interface
1.1.1.4 Available Bandwidth on the Ethernet Port
Counters
Description
1542460296 VS.FEGE.TxTo- Total transmit DBS3900 WCDMA/

talBW bandwidth on the BTS3900 WCDMA/
Ethernet port BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542460297 VS.FEGE.RxTo- Total receive DBS3900 WCDMA/

talBW bandwidth on the BTS3900 WCDMA/
Ethernet port BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters provide total transmit and receive bandwidth in Ethernet in the current
measurement period, reflecting the ETH bandwidth.
Measurement Points
Available bandwidth in the transmit and receive directions of the Ethernet per second. At the
end of a measurement period, the average of these sampling results is used as the value of the
Formula
None
Unit
kbit/s
Related Features
VS.FEGE.TxTotalBW Multi-mode: None


on Iub Interface

VS.FEGE.RxTotalBW Multi-mode: None


on Iub Interface
1.2 Measurement of E1/T1 port performance (E1T1)

Overview
The object type E1T1 Measurement contains the E1/T1 port-related function subset. It represents
the traffic volume of services and communication quality of the E1/T1 port on the transmission
board in the base station.
FunctionSubSets
Physical.E1T1 Measurement related to E1T1 port
1.2.1 Measurement related to E1T1 port (Physical.E1T1)

Overview
The E1T1 function subset helps analyze the transmission quality of the system and ensure the
stable and reliable running of the system. Figure 1-2 shows the position of the E1/T1 port in the
TCP/IP model.
Figure 1-2

Counters
Description
1542455312 VS.E1T1.CodeVio- Number of Code V100R008C00,and

late Type Errors on the the mapping single-
E1/T1 Electrical Port mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455313 VS.E1T1.Framin- Number of Base V100R008C00,and

gError Frame Alignment the mapping single-
Errors on the E1/T1 mode base station
Electrical Port versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455314 VS.E1T1.CrcError Number of CRC V100R008C00,and

Errors on the E1/T1 the mapping single-
Electrical Port mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455315 VS.E1T1.EbitEr- Number of Ebit V100R008C00,and

ror Errors on the E1/T1 the mapping single-
Port mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455316 VS.E1T1.Sa6Error Number of Sa6 V100R008C00,and

Errors on the E1/T1 the mapping single-
Port mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455320 VS.E1T1.Multi- Number of V100R008C00,and

frame multiframe cycles at the mapping single-
the E1/T1 port mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455321 VS.E1T1.FrameA- Number of Times V100R008C00,and

lignChanged that Frames Are Not the mapping single-
Aligned mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455866 VS.E1T1.ES.TES Total Errored V100R008C00,and

Seconds in the TX the mapping single-
Direction mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:V100R006
C00
1542455867 VS.E1T1.ES.TSES Total Severely V100R008C00,and

Errored Seconds in the mapping single-
the TX Direction mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:V100R006
C00


Description
1542455868 VS.E1T1.ES.TUAS Total Unavailable V100R008C00,and

Seconds in the TX the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:V100R006
C00
1542455869 VS.E1T1.ES.RES Total Errored V100R008C00,and

Seconds in the RX the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:V100R006
C00
1542455870 VS.E1T1.ES.RSES Total Severely V100R008C00,and

Errored Seconds in the mapping single-
the RX Direction mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:V100R006
C00


Description
1542455871 VS.E1T1.ES.RUAS Total Unavailable V100R008C00,and

Seconds in the RX the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:V100R006
C00
None
1.2.1.1 Number of Code Type Errors on the E1/T1 Electrical Port
Counters
Description
1542455312 VS.E1T1.CodeVio- Number of Code DBS3900 WCDMA/

late Type Errors on the BTS3900 WCDMA/
E1/T1 Electrical Port BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of code type errors on the E1/T1 electrical port within a
measurement period. A code type error occurs if the line coding modes at two communicating
E1/T1 electrical ports mismatch.

Measurement Points
The number of code type errors on the E1/T1 electrical port is sampled per second. At the end
of a measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
None
Related Features
VS.E1T1.CodeViolate Multi-mode: None

GSM: GBFD-118611 Abis IP over E1/T1
UMTS: WRFD-05030101 ATM over E1T1 on Iub
WRFD-050402 Interface

on Iub Interface
1.2.1.2 Number of Base Frame Alignment Errors on the E1/T1 Electrical Port
Counters
Description
1542455313 VS.E1T1.Framin- Number of Base DBS3900 WCDMA/

gError Frame Alignment BTS3900 WCDMA/
Errors on the E1/T1 BTS3900A
Electrical Port WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
This counter measures the number of base frame alignment errors on the E1/T1 electrical port
within a measurement period. A base frame alignment error prohibits the precise location of
frames.
Measurement Points
The number of base frame alignment errors on the E1/T1 electrical port is sampled per second.
At the end of a measurement period, the sum of these sampling results is used as the value of
the counter.
Formula
None
Unit
None
Related Features
VS.E1T1.FramingError Multi-mode: None


on Iub Interface
1.2.1.3 Number of CRC Errors on the E1/T1 Electrical Port

Counters
Description
1542455314 VS.E1T1.CrcError Number of CRC DBS3900 WCDMA/

Errors on the E1/T1 BTS3900 WCDMA/
Electrical Port BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of CRC errors on the E1/T1 electrical port within a
measurement period. This counter is relevant only for CRC multiframes (E1) or extended
superframes (T1).
Measurement Points
The measurement is performed per second to count the number of CRC errors on the E1/T1
electrical port, and the sum of these sampling results is calculated as the result of the
corresponding counter at the end of a measurement period.
Formula
None
Unit
None

Related Features
VS.E1T1.CrcError Multi-mode: None


on Iub Interface
1.2.1.4 Number of Ebit Errors on the E1/T1 Port
Counters
Description
1542455315 VS.E1T1.EbitError Number of Ebit DBS3900 WCDMA/

Port BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of Ebit errors, that is the number of cyclic redundancy check
(CRC) failures reported by the peer end, within a measurement period. The counter measures
the number of Ebit errors for CRC multi-frames (E1) or extended super-frames (T1).
Measurement Points
The number of Ebit errors on the E1/T1 port is sampled per second. At the end of a measurement
period, the sum of these sampling results is used as the value of the counter.

Formula
None
Unit
None
Related Features
VS.E1T1.EbitError Multi-mode: None


on Iub Interface
1.2.1.5 Number of Sa6 Errors on the E1/T1 Port
Counters
Description
1542455316 VS.E1T1.Sa6Error Number of Sa6 DBS3900 WCDMA/

Port BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of Sa6 errors on the E1 port within a measurement period.
This counter is relevant only for CRC multiframes (E1 port).

Measurement Points
The measurement is performed per second to count the number of Sa6 errors on the E1 port, and
the sum of these sampling results is calculated as the result of the corresponding counter at the
end of a measurement period.
Formula
None
Unit
None
Related Features
VS.E1T1.Sa6Error Multi-mode: None


on Iub Interface
1.2.1.6 Number of multiframe cycles at the E1/T1 port
Counters
Description
1542455320 VS.E1T1.Multi- Number of DBS3900 WCDMA/

frame multiframe cycles at BTS3900 WCDMA/
the E1/T1 port BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
This counter measures the number of multiframe cycles on the E1/T1 electrical port within a
measurement period.
Measurement Points
The measurement is performed per second to count the number of multiframe cycles on the E1/
T1 electrical port, and the sum of these sampling results is calculated as the result of the
corresponding counter at the end of a measurement period.
Formula
None
Unit
None
Related Features
VS.E1T1.Multiframe Multi-mode: None


on Iub Interface
1.2.1.7 Number of Times that Frames Are Not Aligned

Counters
Description
1542455321 VS.E1T1.FrameA- Number of Times DBS3900 WCDMA/

lignChanged that Frames Are Not BTS3900 WCDMA/
Aligned BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of times that frames are not aligned within a measurement
period. It indicates the multiframe variable. This counter is relevant only for CRC multiframes
(E1) or extended superframes (T1).
Measurement Points
The measurement is performed per second to count the number of times that frames are not
aligned on the E1/T1 electrical port. Every time the multi-frames (E1) or extended super-frames
(T1) change, the counter increases by one.
Formula
None
Unit
None

Related Features
VS.E1T1.FrameAlign- Multi-mode: None

Changed GSM: GBFD-118611 Abis IP over E1/T1

on Iub Interface
1.2.1.8 Total Errored Seconds in the TX Direction
Counters
Description
1542455866 VS.E1T1.ES.TES Total Errored DBS3900 WCDMA/

Seconds in the TX BTS3900 WCDMA/
Direction BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter provides the total error seconds in the TX direction on an E1/T1 link. It reflects the
quality on the E1/T1 link. A second is considered an error second in the TX direction if an e-bit
error occurs or an RDI alarm is generated in this second.
Measurement Points
This counter is sampled per second in the TX direction. This counter is increased by one each
time a second is considered as a errored second.

Formula
None
Unit
s
Related Features
VS.E1T1.ES.TES Multi-mode: None


on Iub Interface
1.2.1.9 Total Severely Errored Seconds in the TX Direction
Counters
Description
1542455867 VS.E1T1.ES.TSES Total Severely DBS3900 WCDMA/

Errored Seconds in BTS3900 WCDMA/
the TX Direction BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter provides the total severely errored seconds (SESs) in the TX direction on an E1/
T1 link. It reflects the quality on the E1/T1 link. A second is considered a severe error bit second

in the TX direction if the e-bit error rate is larger than 30% or an RDI alarm is generated in this
second.
Measurement Points
This counter is sampled per second in the TX direction. This counter is increased by one each
time a second is considered as a severely errored second.
Formula
None
Unit
s
Related Features
VS.E1T1.ES.TSES Multi-mode: None


on Iub Interface
1.2.1.10 Total Unavailable Seconds in the TX Direction

Counters
Description
1542455868 VS.E1T1.ES.TUAS Total Unavailable DBS3900 WCDMA/

Seconds in the TX BTS3900 WCDMA/
Direction BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter provides the total severely errored seconds (SESs) in the TX direction on an E1/
T1 link. If there are more than 10 consecutive seconds with severe bit errors, these seconds are
considered as SESs.
Measurement Points
This counter is sampled per second in the TX direction.
Formula
None
Unit
s

Related Features
VS.E1T1.ES.TUAS Multi-mode: None


on Iub Interface
1.2.1.11 Total Errored Seconds in the RX Direction
Counters
Description
1542455869 VS.E1T1.ES.RES Total Errored DBS3900 WCDMA/

Seconds in the RX BTS3900 WCDMA/
Direction BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter provides the total errored seconds in the RX direction on an E1/T1 link. It reflects
the quality on the E1/T1 link. A second is considered an error second in the RX direction if an
error occurs or an LOS/AIS/LOF alarm is generated in this second.
Measurement Points
This counter is sampled per second in the RX direction. This counter is increased by one each
time a second is considered as a errored second.

Formula
None
Unit
s
Related Features
VS.E1T1.ES.RES Multi-mode: None


on Iub Interface
1.2.1.12 Total Severely Errored Seconds in the RX Direction
Counters
Description
1542455870 VS.E1T1.ES.RSES Total Severely DBS3900 WCDMA/

Errored Seconds in BTS3900 WCDMA/
the RX Direction BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter provides the total severely errored seconds (SESs) in the RX direction on an E1/
T1 link. It reflects the quality on the E1/T1 link. A second is considered a severe error bit second

in the RX direction if the bit error rate is larger than 30% or an LOS/AIS/LOF alarm is generated
in this second.
Measurement Points
This counter is sampled per second in the RX direction. This counter is increased by one each
time a second is considered as a severely errored second.
Formula
None
Unit
s
Related Features
VS.E1T1.ES.RSES Multi-mode: None


on Iub Interface
1.2.1.13 Total Unavailable Seconds in the RX Direction

Counters
Description
1542455871 VS.E1T1.ES.RUAS Total Unavailable DBS3900 WCDMA/

Seconds in the RX BTS3900 WCDMA/
Direction BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter provides the total severely errored seconds (SESs) in the RX direction on an E1/
T1 link. If there are more than 10 consecutive seconds with severe bit errors, these seconds are
considered as SESs.
Measurement Points
This counter is sampled per second in the RX direction.
Formula
None
Unit
s

Related Features
VS.E1T1.ES.RUAS Multi-mode: None


on Iub Interface
1.3 Measurement of PPP Link performance (PPP)

Overview
The object type PPP Measurement contains the PPP link-related function subset. It represents
the traffic volume of services carried by the PPP link of the transmission board in the base station
and the quality of service.
FunctionSubSets
DataLink.PPP Measurement related to PPP link
1.3.1 Measurement related to PPP link (DataLink.PPP)
Overview
The DataLink.PPP function subset measures the number of packets transmitted on the PPP link
of the base station and evaluates the information about the rates, for example, the number of
received packets, the number of transmitted packets, and the rate. It represents the traffic volume
and quality of services carried by the PPP link. Figure 1-3 shows the position of the PPP link
in the TCP/IP model.

Figure 1-3
Counters
Description
1542455334 VS.PPP.TxPackets Number of Packets V100R008C00,and

Successfully the mapping single-
Transmitted on the mode base station
PPP Link versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:Version
earlier than
V100R003C00
1542455335 VS.PPP.TxBytes Number of Bytes in V100R008C00,and

the Packets the mapping single-
Successfully mode base station
Transmitted on the versions that
PPP Link introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455336 VS.PPP.TxDropPk Number of Packets to V100R008C00,and

ts Be Transmitted but the mapping single-
Discarded on the PPP mode base station
Link versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:Version
earlier than
V100R003C00
1542455337 VS.PPP.RxPackets Number of Packets V100R008C00,and

Received on the PPP mode base station
Link versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:Version
earlier than
V100R003C00
1542455338 VS.PPP.RxBytes Number of Bytes in V100R008C00,and

Received on the PPP versions that
Link introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455339 VS.PPP.RxDropPk Number of Packets V100R008C00,and

ts Received but the mapping single-
Discarded on the PPP mode base station
Link versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:Version
earlier than
V100R003C00
1542455343 VS.PPP.TxMax- Maximum Transmit V100R008C00,and

Speed Rate on the PPP Link the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:Version
earlier than
V100R003C00
1542455344 VS.PPP.TxMin- Minimum Transmit V100R008C00,and

mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455345 VS.PPP.TxMean- Average Transmit V100R008C00,and

mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:Version
earlier than
V100R003C00
1542455346 VS.PPP.RxMax- Maximum Receive V100R008C00,and

mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:Version
earlier than
V100R003C00
1542455347 VS.PPP.RxMin- Minimum Receive V100R008C00,and

mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455348 VS.PPP.RxMean- Average Receive V100R008C00,and

mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:Version
earlier than
V100R003C00
1542460298 VS.PPP.TxTotalB Total transmit V100R008C00,and

W bandwidth of the PPP the mapping single-
link mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460299 VS.PPP.RxTotalB Total receive V100R008C00,and

W bandwidth of the PPP the mapping single-
link mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
None

1.3.1.1 Number of Packets on the PPP Link
Counters
Description
1542455334 VS.PPP.TxPackets Number of Packets DBS3900 WCDMA/

Successfully BTS3900 WCDMA/
Transmitted on the BTS3900A
PPP Link WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455336 VS.PPP.TxDropPkts Number of Packets to DBS3900 WCDMA/

Be Transmitted but BTS3900 WCDMA/
Discarded on the PPP BTS3900A
Link WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455337 VS.PPP.RxPackets Number of Packets DBS3900 WCDMA/

Received on the PPP BTS3900A
Link WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455339 VS.PPP.RxDropPkts Number of Packets DBS3900 WCDMA/

Received but BTS3900 WCDMA/
Discarded on the PPP BTS3900A
Link WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The following table describes the meanings of each counter.
Counter Name Description
VS.PPP.TxPackets This counter measures the number of packets

successfully transmitted on the PPP link
within a measurement period. It indicates the
traffic on the PPP link.

VS.PPP.TxDropPkts This counter measures the number of packets

that are to be transmitted but discarded on the
PPP link within a measurement period. It
indicates the traffic on the PPP link. Packet
losses occur in the following situations: 1.
The PPP link is not stable or activated. 2. The
protocol number of transmitted packets is
invalid. For example, the protocol number is
not one of 0x0021, 0x0061, 0x0065, 0x0059,
and 0x003d.
VS.PPP.RxPackets This counter measures the number of packets

successfully received on the PPP link within
a measurement period. It indicates the traffic
on the PPP link.
VS.PPP.RxDropPkts This counter measures the number of packets

that are to be received but discarded on the
PPP link within a measurement period. It
indicates the traffic on the PPP link. Packet
losses occur in the following situations: 1.
The PPP link is not stable or activated. 2. The
protocol number of received packets is
invalid. For example, the protocol number is
not one of 0x0021, 0x0061, 0x0065, 0x0059,
and 0x003d.
Measurement Points
Number of successfully transmitted packets, packets discarded by the transmit direction,
successfully received packets, and packets discarded by the receive direction on the PPP link
per second. At the end of a measurement period, the sum of these sampling results is used as the
value of the corresponding counter.
Formula
None
Unit
packet

Related Features
VS.PPP.TxPackets Multi-mode: None

UMTS: WRFD-050402 IP Transmission Introduction
LTE: LBFD-003004 on Iub Interface
TDLBFD-003004 Compression &

Multiplexing over E1/T1
Compression &
VS.PPP.TxDropPkts Multi-mode: None


Compression &
VS.PPP.RxPackets Multi-mode: None


Compression &
VS.PPP.RxDropPkts Multi-mode: None


Compression &
1.3.1.2 Number of Bytes on the PPP Link

Counters
Description
1542455335 VS.PPP.TxBytes Number of Bytes in DBS3900 WCDMA/

the Packets BTS3900 WCDMA/
Successfully BTS3900A
Transmitted on the WCDMA/
PPP Link BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455338 VS.PPP.RxBytes Number of Bytes in DBS3900 WCDMA/

Received on the PPP WCDMA/
Link BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
VS.PPP.TxBytes This counter measures the number of bytes

successfully transmitted on the PPP link
within a measurement period. This counter
measures the total number of bytes in the
address field, control field, protocol field, and
information field in a packet. It indicates the
traffic on the PPP link.

VS.PPP.RxBytes This counter measures the number of bytes

successfully received on the PPP link within
a measurement period. This counter measures
the total number of bytes in the address field,
control field, protocol field, and information
field in a packet. It indicates the traffic on the
PPP link.
Measurement Points
Number of bytes successfully transmitted and received on the PPP link per second. At the end
of a measurement period, the sum of these sampling results is used as the value of the
Formula
None
Unit
byte
Related Features
VS.PPP.TxBytes Multi-mode: None


Compression &
VS.PPP.RxBytes Multi-mode: None


Compression &

1.3.1.3 Rate on the PPP Link
Counters
Description
1542455343 VS.PPP.TxMax- Maximum Transmit DBS3900 WCDMA/

Speed Rate on the PPP Link BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455344 VS.PPP.TxMin- Minimum Transmit DBS3900 WCDMA/

BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455345 VS.PPP.TxMean- Average Transmit DBS3900 WCDMA/

BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455346 VS.PPP.RxMax- Maximum Receive DBS3900 WCDMA/

BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455347 VS.PPP.RxMin- Minimum Receive DBS3900 WCDMA/

BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455348 VS.PPP.RxMean- Average Receive DBS3900 WCDMA/

BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
VS.PPP.TxMaxSpeed This counter measures the maximum transmit

rate on the PPP link within a measurement
period. It counter indicates the traffic on the
PPP link.
VS.PPP.TxMinSpeed This counter measures the minimum transmit

period. It counter indicates the traffic on the
PPP link.
VS.PPP.TxMeanSpeed This counter measures the average transmit

period. It indicates the traffic on the PPP link.
VS.PPP.RxMaxSpeed This counter measures the maximum receive

VS.PPP.RxMinSpeed This counter measures the minimum receive

VS.PPP.RxMeanSpeed This counter measures the average receive


Measurement Points
Number of bytes transmitted and received on the PPP link per second. At the end of a
measurement period, the maximum, minimum, and average sampling results are reported.
Formula
None
Unit
bit/s
Related Features
VS.PPP.TxMaxSpeed Multi-mode: None


Compression &
VS.PPP.TxMinSpeed Multi-mode: None


Compression &
VS.PPP.TxMeanSpeed Multi-mode: None


Compression &

VS.PPP.RxMaxSpeed Multi-mode: None


Compression &
VS.PPP.RxMinSpeed Multi-mode: None


Compression &
VS.PPP.RxMeanSpeed Multi-mode: None


Compression &
1.3.1.4 Total bandwidth of the PPP link

Counters
Description
1542460298 VS.PPP.TxTotalBW Total transmit DBS3900 WCDMA/

bandwidth of the PPP BTS3900 WCDMA/
link BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542460299 VS.PPP.RxTotalBW Total receive DBS3900 WCDMA/

bandwidth of the PPP BTS3900 WCDMA/
link BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
VS.PPP.TxTotalBW Total transmission bandwidth in PPP link is

measured in the current measurement period,
reflecting the PPP bandwidth.
VS.PPP.RxTotalBW Total receive bandwidth in PPP link is

reflecting the PPP bandwidth.

Measurement Points
Available bandwidth in the transmit and receive directions of the PPP link per second. At the
Formula
None
Unit
kbit/s
Related Features
VS.PPP.TxTotalBW Multi-mode: None


Compression &
VS.PPP.RxTotalBW Multi-mode: None


Compression &
1.4 Measurement of MP Group performance (MPGRP)

Overview
The object type MP Group Measurement (MPGRP) contains the function subset related to the
MP group. It represents the traffic volume and service quality of the transmission board in the
base station.

FunctionSubSets
DataLink.MPGRP Measurement related to MP
1.4.1 Measurement related to MP (DataLink.MPGRP)
Overview
The MPGRP function subset measures traffic volumes of the services carried by the MPGRP
links and the service quality. Figure 1-4 shows the position of the MP group in the TCP/IP
model.
Figure 1-4

Counters
Description
1542455349 VS.MP.TxPackets Number of Packets V100R008C00,and

Transmitted by the mode base station
MP Group versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455350 VS.MP.TxBytes Number of Bytes in V100R008C00,and

Transmitted by the versions that
MP Group introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455351 VS.MP.TxDropPkt Number of Packets V100R008C00,and

s That Are to Be the mapping single-
Transmitted But mode base station
Discarded by the MP versions that
Group introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455352 VS.MP.RxPackets Number of Packets V100R008C00,and

Received by the MP mode base station
Group versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455353 VS.MP.RxBytes Number of Bytes in V100R008C00,and

Received by the MP versions that
Group introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455354 VS.MP.RxDropPkt Number of Packets V100R008C00,and

s That Are Received the mapping single-
But Discarded by the mode base station
MP Group versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455358 VS.MP.TxMaxSpe Maximum Transmit V100R008C00,and

ed Rate of the MP the mapping single-
Group mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455359 VS.MP.TxMinSpee Minimum Transmit V100R008C00,and

d Rate of the MP the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455360 VS.MP.TxMean- Average Transmit V100R008C00,and

Speed Rate of the MP the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455361 VS.MP.RxMaxSpe Maximum Receive V100R008C00,and

ed Rate of the MP the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455362 VS.MP.RxMinSpee Minimum Receive V100R008C00,and

d Rate of the MP the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455363 VS.MP.RxMean- Average Receive V100R008C00,and

Speed Rate of the MP the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542460300 VS.MP.TxTotalB Total transmit V100R008C00,and

W bandwidth of the MP the mapping single-
group mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460301 VS.MP.RxTotalB Total receive V100R008C00,and

W bandwidth of the MP the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
None
1.4.1.1 Number of Packets on the MP Group

Counters
Description
1542455349 VS.MP.TxPackets Number of Packets DBS3900 WCDMA/

Transmitted by the BTS3900A
MP Group WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455351 VS.MP.TxDropPkts Number of Packets DBS3900 WCDMA/

That Are to Be BTS3900 WCDMA/
Transmitted But BTS3900A
Discarded by the MP WCDMA/
Group BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455352 VS.MP.RxPackets Number of Packets DBS3900 WCDMA/

Received by the MP BTS3900A
Group WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455354 VS.MP.RxDropPkts Number of Packets DBS3900 WCDMA/

That Are Received BTS3900 WCDMA/
But Discarded by the BTS3900A
MP Group WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
VS.MP.TxPackets This counter provides the number of packets

successfully transmitted on an MP group
within a measurement period. It reflects the
traffic and transmission capability on the MP
group.
VS.MP.TxDropPkts This counter provides the number of packets

that are to be transmitted but discarded on an
MP group when MP links are not activated
group.
VS.MP.RxPackets This counter provides the number of packets

successfully received on an MP group within
a measurement period. It reflects the traffic
and transmission capability on the MP group.
VS.MP.RxDropPkts This counter provides the number of packets

that are to be received but discarded due to
failed reassembling of disordered packets on
MP links on an MP group within a
measurement period. It reflects the traffic and
transmission capability on the MP group.

Measurement Points
Number of successfully transmitted packets, packets discarded by the transmit direction,
successfully received packets, and packets discarded by the receive direction by the MP group
is sampled per second. At the end of a measurement period, the average of these sampling results
is used as the value of the counter.
Formula
None
Unit
packet
Related Features
VS.MP.TxPackets Multi-mode: None


Compression &
VS.MP.TxDropPkts Multi-mode: None


Compression &
VS.MP.RxPackets Multi-mode: None


Compression &

VS.MP.RxDropPkts Multi-mode: None


Compression &
1.4.1.2 Number of Bytes on the MP Group
Counters
Description
1542455350 VS.MP.TxBytes Number of Bytes in DBS3900 WCDMA/

Transmitted by the WCDMA/
MP Group BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455353 VS.MP.RxBytes Number of Bytes in DBS3900 WCDMA/

Received by the MP WCDMA/
Group BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
VS.MP.TxBytes This counter provides the number of bytes

successfully transmitted on an MP group
group. The counter value includes the number
of bytes in the MP group header and payload
of a packet.
VS.MP.RxBytes This counter provides the number of bytes

successfully received on an MP group within
a measurement period. It reflects the traffic
and transmission capability on the MP group.
The counter value includes the number of
bytes in the MP group header and payload of
a packet.
Measurement Points
Number of bytes successfully transmitted and received by the MP group is sampled per second.
the counter.
Formula
None
Unit
byte

Related Features
VS.MP.TxBytes Multi-mode: None


Compression &
VS.MP.RxBytes Multi-mode: None


Compression &
1.4.1.3 Rate on the MP Group
Counters
Description
1542455358 VS.MP.TxMaxSpee Maximum Transmit DBS3900 WCDMA/

d Rate of the MP BTS3900 WCDMA/
Group BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455359 VS.MP.TxMinSpee Minimum Transmit DBS3900 WCDMA/

Group BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455360 VS.MP.TxMean- Average Transmit DBS3900 WCDMA/

Speed Rate of the MP BTS3900 WCDMA/
Group BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455361 VS.MP.RxMaxSpee Maximum Receive DBS3900 WCDMA/

Group BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455362 VS.MP.RxMinSpee Minimum Receive DBS3900 WCDMA/

Group BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455363 VS.MP.RxMean- Average Receive DBS3900 WCDMA/

Speed Rate of the MP BTS3900 WCDMA/
Group BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
VS.MP.TxMaxSpeed The counter measures the maximum transmit

rate of the MP group within a measurement
period. This counter represents the traffic on
the MP link.
VS.MP.TxMinSpeed The counter measures the minimum transmit

the MP link.

VS.MP.TxMeanSpeed The counter measures the average transmit

the MP link.
VS.MP.RxMaxSpeed The counter measures the maximum receive

the MP link.
VS.MP.RxMinSpeed The counter measures the minimum receive

the MP link.
VS.MP.RxMeanSpeed The counter measures the average receive

the MP link.
Measurement Points
The number of bytes transmitted and received by the MP group is sampled per second. At the
end of a measurement period, the maximum, minimum, and average sampling results are
reported.
Formula
None
Unit
bit/s
Related Features
VS.MP.TxMaxSpeed Multi-mode: None


Compression &

VS.MP.TxMinSpeed Multi-mode: None


Compression &
VS.MP.TxMeanSpeed Multi-mode: None


Compression &
VS.MP.RxMaxSpeed Multi-mode: None


Compression &
VS.MP.RxMinSpeed Multi-mode: None


Compression &
VS.MP.RxMeanSpeed Multi-mode: None


Compression &

1.4.1.4 Available Bandwidth on the MP Group
Counters
Description
1542460300 VS.MP.TxTotalBW Total transmit DBS3900 WCDMA/

bandwidth of the MP BTS3900 WCDMA/
group BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542460301 VS.MP.RxTotalBW Total receive DBS3900 WCDMA/

bandwidth of the MP BTS3900 WCDMA/
group BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
VS.MP.TxTotalBW Total transmit bandwidth in MP group is

reflecting the MP bandwidth.

VS.MP.RxTotalBW Total receive bandwidth in MP group is

reflecting the MP bandwidth.
Measurement Points
Available bandwidth in the transmit and receive directions on the MP group per second. At the
Formula
None
Unit
kbit/s
Related Features
VS.MP.TxTotalBW Multi-mode: None


Compression &
VS.MP.RxTotalBW Multi-mode: None


Compression &

1.5 Measurement of IP layer performance (IP)

Overview
The object type IP Measurement contains the function subset related to the IP layer of the
transmission board in the base station. It represents the traffic volume and the service qualities
of the IP layer.
FunctionSubSets
Network.IP Measurement related to IP
1.5.1 Measurement related to IP (Network.IP)
Overview
The Network.IP function subset measures the IP packet traffic, such as the number of
successfully transmitted or received IP packets or the number of bytes in the transmitted or
received IP packets. It represents the traffic volume and quality of services at the IP layer. Figure
1-5 shows the position of the IP layer in the TCP/IP model.
Figure 1-5

Counters
Description
1542455326 VS.IP.TxPackets Number of V100R008C00,and

successfully the mapping single-
transmitted IP mode base station
packets versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R005
C00
1542455327 VS.IP.TxBytes Number of bytes in V100R008C00,and

the successfully the mapping single-
transmitted IP mode base station
packets versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R005
C00
1542455328 VS.IP.TxDropPkts Number of discarded V100R008C00,and

IP packets the mapping single-
transmitted mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R005
C00


Description
1542455329 VS.IP.TxDrop- Number of bytes in V100R008C00,and

Bytes the discarded IP the mapping single-
packets transmitted mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R005
C00
1542455330 VS.IP.RxPackets Number of V100R008C00,and

successfully received the mapping single-
IP packets mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R005
C00
1542455331 VS.IP.RxBytes Number of bytes in V100R008C00,and

received IP packets mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R005
C00


Description
1542455332 VS.IP.RxDropPkts Number of discarded V100R008C00,and

IP packets received the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R005
C00
1542455333 VS.IP.RxDrop- Number of bytes in V100R008C00,and

Bytes the discarded IP the mapping single-
packets received mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R005
C00
None
1.5.1.1 Number of IP Packets

Counters
Description
1542455326 VS.IP.TxPackets Number of DBS3900 WCDMA/

successfully BTS3900 WCDMA/
transmitted IP BTS3900A
packets WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455328 VS.IP.TxDropPkts Number of discarded DBS3900 WCDMA/

IP packets BTS3900 WCDMA/
transmitted BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455330 VS.IP.RxPackets Number of DBS3900 WCDMA/

successfully received BTS3900 WCDMA/
IP packets BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455332 VS.IP.RxDropPkts Number of discarded DBS3900 WCDMA/

IP packets received BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters measure the number of IP packets successfully transmitted, successfully
received, or discarded within a measurement period. They indicate the traffic on and the
processing capability of the base station at the network layer.
Measurement Points
The number of IP packets successfully transmitted, successfully received, or discarded is
sampled per second. At the end of a measurement period, the sum of these sampling results is
used as the value of the corresponding counter.
The VS.IP.TxPackets counter measures the number of IP packets successfully transmitted when
the routing table and ARP table are found successfully. The counter is incremented after
fragment.
The VS.IP.RxPackets counter measures the number of IP packets successfully received from
the data link layer. This counter is incremented before reassembly.
The VS.IP.TxDropPkts counter measures the number of transmitted IP packets discarded. It is
incremented in any of the following conditions: (1) The forward information base (FIB) fails to
be found. (2) The address of the FIB table is invalid. (3) The FIB table is invalid. (4) During the
configuration of the routing load sharing, the configuration is incorrect or the routing table is
invalid.
The VS.IP.RxDropPkts counter measures the number of received IP packets discarded. It is
incremented in any of the following conditions: (1) The IP header check fails. (2) Packet
reassembly fails. (3) Broadcast packets are discarded when the access control list (ACL) filtering
function is enabled.
Formula
None

Unit
packet
Related Features
VS.IP.TxPackets Multi-mode: None


on Iub Interface
VS.IP.TxDropPkts Multi-mode: None


on Iub Interface
VS.IP.RxPackets Multi-mode: None


on Iub Interface
VS.IP.RxDropPkts Multi-mode: None


on Iub Interface
1.5.1.2 Number of Bytes in the IP Packets

Counters
Description
1542455327 VS.IP.TxBytes Number of bytes in DBS3900 WCDMA/

the successfully BTS3900 WCDMA/
transmitted IP BTS3900A
packets WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455329 VS.IP.TxDropBytes Number of bytes in DBS3900 WCDMA/

the discarded IP BTS3900 WCDMA/
packets transmitted BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455331 VS.IP.RxBytes Number of bytes in DBS3900 WCDMA/

the successfully BTS3900 WCDMA/
received IP packets BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455333 VS.IP.RxDropBytes Number of bytes in DBS3900 WCDMA/

the discarded IP BTS3900 WCDMA/
packets received BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters measure the number of bytes in the successfully transmitted, successfully
received, or discarded IP packets within a measurement period. They indicate the traffic and the
Measurement Points
The number of bytes in the successfully transmitted, successfully received, or discarded IP
packets is sampled per second. At the end of a measurement period, the sum of these sampling
results is used as the value of the corresponding counter.
The VS.IP.TxBytes counter measures the number of bytes in the IP packets successfully
transmitted when the routing table and ARP table are found successfully. It includes the IP header
and payload (or IPSec-related payload such as AH header and ESP header in IPSec scenarios).
If packets need to be fragmented, this counter is incremented after fragment.
The VS.IP.RxBytes counter measures the number of bytes in the IP packets successfully received
from the data link layer. It includes the IP header and payload (or IPSec-related payload such
as AH header and ESP header in IPSec scenarios). If packets are fragmented, this counter is
incremented before packet reassembly.
The VS.IP.TxDropBytes counter is incremented in any of the following conditions: (1) The
forward information base (FIB) fails to be found. (2) The address of the FIB table is invalid. (3)
The FIB table is invalid. (4) During the configuration of the routing load sharing, the
configuration is incorrect or the routing table is invalid.
The VS.IP.RxDropBytes counter is incremented in any of the following conditions: (1) The IP
header check fails. (2) Packet reassembly fails. (3) Broadcast packets are discarded when the
access control list (ACL) filtering function is enabled.

Formula
None
Unit
byte
Related Features
VS.IP.TxBytes Multi-mode: None


on Iub Interface
VS.IP.TxDropBytes Multi-mode: None


on Iub Interface
VS.IP.RxBytes Multi-mode: None


on Iub Interface
VS.IP.RxDropBytes Multi-mode: None


on Iub Interface
1.6 Measurement of IP path performance (IPPath)

Overview
The object type IP Path Measurement contains the function subset related to the IP path in the
base station. It represents the traffic volume and service qualities of IP paths that are configured

on the transmission board. It represents the traffic volume of the packets that follow the General
Packet Radio Service Tunneling Protocol for User Plane (GTP-U). It provides a fine-grained
flow monitoring mechanism, which facilitates the user-data based Qos management.
FunctionSubSets
Transport.IPPath Measurement related to IP path
1.6.1 Measurement related to IP path (Transport.IPPath)
Overview
The IP Path function subset provides the measurements on an IP path in the base station. It
measures the traffic volumes of services carried by an IP path and the service quality at a smaller
granularity, and supports QoS management based on the traffic volumes. Figure 1-6 shows the
position of the IP path in the TCP/IP model.
Figure 1-6

Counters
Description
1542455392 VS.IPPath.TxRtPk Number of real-time V100R008C00,and

ts service packets the mapping single-
transmitted on the IP version that
path introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1542455393 VS.IPPath.TxRtBy Number of bytes in V100R008C00,and

tes the real-time service the mapping single-
packets successfully mode base station
path introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1542455396 VS.IPPath.RxRtPk Number of real-time V100R008C00,and

ts service packets the mapping single-
on the IP path version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1542455397 VS.IPPath.RxRtBy Number of bytes in V100R008C00,and

tes the real-time service the mapping single-
packets successfully mode base station
received on the IP version that
path introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1542455400 VS.IPPath.TxNrtP Number of non-real- V100R008C00,and

kts time service packets the mapping single-
path introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1542455401 VS.IPPath.TxNrtB Number of bytes in V100R008C00,and

ytes the non-real-time the mapping single-
service packets mode base station
successfully version that
transmitted on the IP introduce this
path counter is:
eNodeB:Version
earlier than
V100R003C00
1542455404 VS.IPPath.RxNrtP Number of non-real- V100R008C00,and

kts time service packets the mapping single-
on the IP path version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1542455405 VS.IPPath.RxNrtB Number of bytes in V100R008C00,and

ytes the non-real-time the mapping single-
service packets mode base station
successfully received version that
on the IP path introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
None
1.6.1.1 Number of real-time service packets on the IP path

Counters
Description
1542455392 VS.IPPath.TxRtPkts Number of real-time DBS3900 LTE/

service packets BTS3900 LTE/
successfully BTS3900A LTE/
transmitted on the IP BTS3900L LTE/
path BTS3900AL LTE,
BTS3900
1542455396 VS.IPPath.RxRtPkts Number of real-time DBS3900 LTE/

service packets BTS3900 LTE/
successfully received BTS3900A LTE/
on the IP path BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters measure the number of IP packets successfully transmitted and received on an
IP path within a measurement period, respectively. They indicate the real-time service traffic at
the IP layer on the IP path. Real-time services include voice services, video on demand (real-
time streams), and real-time games. Real-time service data is generally the UDP-based stream
media data.
Measurement Points
The number of real-time service packets transmitted or received on the IP path is sampled per
second. At the end of a measurement period, the sum of these sampling results is used as the
The measurement is triggered in the following conditions:
(1) IP path performance measurement is enabled.
(2) Real-time services are provided.
Formula
None
Unit
packet
Related Features
None

1.6.1.2 Number of bytes of real-time service on the IP Path
Counters
Description
1542455393 VS.IPPath.TxRtByte Number of bytes in DBS3900 LTE/

s the real-time service BTS3900 LTE/
packets successfully BTS3900A LTE/
path BTS3900AL LTE,
BTS3900
1542455397 VS.IPPath.RxRtByt Number of bytes in DBS3900 LTE/

es the real-time service BTS3900 LTE/
packets successfully BTS3900A LTE/
received on the IP BTS3900L LTE/
path BTS3900AL LTE,
BTS3900
Description
These counters measure the number of bytes in the IP packets successfully transmitted and
received on an IP path within a measurement period, respectively. They indicate the real-time
service traffic at the IP layer on the IP path. Real-time services include voice services, video on
demand (real-time streams), and real-time games. Real-time service data is generally the UDP-
based stream media data.
Measurement Points
The number of bytes in the real-time service packets successfully transmitted or successfully
received on the IP path is sampled per second. At the end of a measurement period, the sum of
these sampling results is used as the value of the corresponding counter.
The counter includes the IP header and payload.
In IPSec scenarios, the IPPath.RxRtBytes counter measures the number of bytes in the decrypted
IP packets successfully received after reassembly, and the IPPath.TxRtBytes counter measures
the number of bytes in the encrypted IP packets successfully transmitted before fragment.
In non-IPSec scenarios, the IPPath.RxRtBytes counter measures the number of bytes in the IP
packets successfully received after reassembly, and the IPPath.TxRtBytes counter measures the
number of bytes in the IP packets successfully transmitted before fragment.
(2) Real-time services are provided.

Formula
None
Unit
byte
Related Features
None
1.6.1.3 Number of non-real-time service packets on the IP path
Counters
Description
1542455400 VS.IPPath.TxNrtPkt Number of non-real- DBS3900 LTE/

s time service packets BTS3900 LTE/
successfully BTS3900A LTE/
path BTS3900AL LTE,
BTS3900
1542455404 VS.IPPath.RxNrtPkt Number of non-real- DBS3900 LTE/

s time service packets BTS3900 LTE/
successfully received BTS3900A LTE/
on the IP path BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
IP path within a measurement period, respectively. They indicate the non-real-time service traffic
at the IP layer on the IP path. Non-real-time services include video on demand (that is, buffer
streams), interactive games, and TCP-based data streams.
Measurement Points
The number of non-real-time service packets transmitted or received on the IP path is sampled
(2) Non-real-time services are provided.

Formula
None
Unit
packet
Related Features
None
1.6.1.4 Number of bytes of non-real-time services on the IP path
Counters
Description
1542455401 VS.IPPath.TxNrtByt Number of bytes in DBS3900 LTE/

es the non-real-time BTS3900 LTE/
service packets BTS3900A LTE/
successfully BTS3900L LTE/
transmitted on the IP BTS3900AL LTE,
path BTS3900
1542455405 VS.IPPath.RxNrtByt Number of bytes in DBS3900 LTE/

es the non-real-time BTS3900 LTE/
service packets BTS3900A LTE/
successfully received BTS3900L LTE/
on the IP path BTS3900AL LTE,
BTS3900
Description
received on an IP path within a measurement period, respectively. They indicate the non-real-
time service traffic at the IP layer on the IP path. Non-real-time services include video on demand
(that is, buffer streams), interactive games, and TCP-based data streams.
Measurement Points
The number of bytes in the non-real-time service packets successfully transmitted or successfully
received on the IP path is sampled per second. At the end of a measurement period, the sum of
In IPSec scenarios, the IPPath.RxNrtBytes counter measures the number of bytes in the
decrypted IP packets successfully received after reassembly, and the IPPath.TxNrtBytes counter

measures the number of bytes in the encrypted IP packets successfully transmitted before
fragment.
In non-IPSec scenarios, the IPPath.RxNrtBytes counter measures the number of bytes in the IP
packets successfully received after reassembly, and the IPPath.TxNrtBytes counter measures
the number of bytes in the IP packets successfully transmitted before fragment.
(2) Non-real-time services are provided.
Formula
None
Unit
byte
Related Features
None
1.7 Measurement of Resource Group performance

(RscGroup)
Overview
The object type Resource Group Measurement contains the function subset related to the
resource group. It represents the traffic volume and service processing capability of the resource
group on the transmission board in the base station.
FunctionSubSets
Transport.RscGroup Measurement related to Resource Group
1.7.1 Measurement related to Resource Group

(Transport.RscGroup)
Overview
The resource group of an base station is a set of data streams. The data streams can be related
to control plane services, user plane services, OM services, IP clock services, or bypass services
(regardless of control plane services or user plane services). The transmission quality affects the

services of the base station. The base station manages bandwidths based on resource groups.
The base station can configure the bandwidth, flow shaping, admission control, and flow control
for the resource group. Multiple resource groups can be configured on one physical link, the
bandwidth of which is shared among these resource groups. Multiple transport-layer bearers can
be configured for one resource group, the configured bandwidth of which is shared among these
bearers. The Transport.RscGroup function subset measures the number of bytes or packets
transmitted by the resource group of the base station. It represents the service processing
capability of the resource group. Figure 1-7 shows the position of the resource group in the TCP/
IP model. The Transport.RscGroup function subset measures only the data transmitted from a
resource group.The counters of function subset Transport.RscGourp report valid values in IP
transmission, and reports zero in ATM transmission.
Figure 1-7
Counters
Description
1542455365 VS.RscGroup.TxB Number of bytes in V100R008C00,and

ytes the packets the mapping single-
transmitted by the versions that
resource group introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455367 VS.RscGroup.TxP Number of packets V100R008C00,and

kts successfully the mapping single-
transmitted by the mode base station
resource group versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455369 VS.RscGroup.TxD Number of bytes in V100R008C00,and

ropBytes the packets discarded the mapping single-
by the resource group mode base station
due to transmission versions that
failures introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455371 VS.RscGroup.TxD Number of packets V100R008C00,and

ropPkts discarded by the the mapping single-
resource group due to mode base station
transmission failures versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455375 VS.RscGroup.TxM Maximum transmit V100R008C00,and

axSpeed rate of the resource the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455376 VS.RscGroup.TxM Minimum transmit V100R008C00,and

inSpeed rate of the resource the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455377 VS.RscGroup.TxM Average transmit V100R008C00,and

eanSpeed rate of the resource the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
None

1.7.1.1 Number of Bytes in the Packets Transmitted by the Resource Group
Counters
Description
1542455365 VS.RscGroup.TxByt Number of bytes in DBS3900 WCDMA/

es the packets BTS3900 WCDMA/
successfully BTS3900A
transmitted by the WCDMA/
resource group BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455369 VS.RscGroup.TxDr Number of bytes in DBS3900 WCDMA/

opBytes the packets discarded BTS3900 WCDMA/
by the resource group BTS3900A
due to transmission WCDMA/
failures BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters measure the number of bytes in the packets transmitted by all the queues of a
resource group at the data link layer within a measurement period and the number of bytes in
the packets discarded due to congestion in the queues within a measurement period. They
represent the transmit traffic on the resource group at the data link layer. If the resource group
is carried on an Ethernet port, the counters measure the MAC headers and payloads in the packets.
If the resource group is carried on a port carrying a PPP link or MP link, the counters measure
the data parts of the PPP frames or MP frames. The measurement of the counters remains
unchanged in packet fragment or IPSec scenarios.

Measurement Points
Number of transmitted bytes and discarded bytes in the resource group per second. At the end
Formula
None
Unit
byte
Related Features
VS.RscGroup.TxBytes Multi-mode: None

GSM: GBFD-118605 IP QOS
LTE: LOFD-003011 on Iub Interface
TDLOFD-003011 Enhanced Transport QoS

Management
Enhanced Transport QoS
Management
VS.RscGroup.TxDropBytes Multi-mode: None


Management
Management
1.7.1.2 Number of Packets Transmitted by the Resource Group

Counters
Description
1542455367 VS.RscGroup.TxPkt Number of packets DBS3900 WCDMA/

s successfully BTS3900 WCDMA/
transmitted by the BTS3900A
resource group WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455371 VS.RscGroup.TxDr Number of packets DBS3900 WCDMA/

opPkts discarded by the BTS3900 WCDMA/
resource group due to BTS3900A
transmission failures WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters measure the number of IP packets transmitted by all the queues of a resource
group at the data link layer within a measurement period and the number of packets discarded
due to congestion in the queues within a measurement period. They represent the transmit traffic
on the resource group at the data link layer.
Measurement Points
Number of transmitted and discarded packets in the resource group per second. At the end of a
measurement period, the sum of these sampling results is used as the value of the corresponding
counter.

Formula
None
Unit
packet
Related Features
VS.RscGroup.TxPkts Multi-mode: None


Management
Management
VS.RscGroup.TxDropPkts Multi-mode: None


Management
Management
1.7.1.3 Rates of the Resource Group

Counters
Description
1542455375 VS.RscGroup.TxMa Maximum transmit DBS3900 WCDMA/

xSpeed rate of the resource BTS3900 WCDMA/
group BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455376 VS.RscGroup.TxMi Minimum transmit DBS3900 WCDMA/

nSpeed rate of the resource BTS3900 WCDMA/
group BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455377 VS.RscGroup.TxMe Average transmit DBS3900 WCDMA/

anSpeed rate of the resource BTS3900 WCDMA/
group BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
These counters measure the transmit rate of a resource group within a measurement period. They
represent the transmission rate of the resource group. If the resource group is carried on an
Ethernet port, the counters measure the MAC headers and payloads. If the resource group is
carried on the PPP or MP group port, the counters measure the information part of the PPP frame
or MP frame.
Measurement Points
The transmit rate of the resource group is sampled per second. At the end of a measurement
period, the maximum, minimum, or average of these sampling results is used as the value of the
Formula
None
Unit
bit/s
Related Features
VS.RscGroup.TxMaxSpeed Multi-mode: None


Management
Management
VS.RscGroup.TxMinSpeed Multi-mode: None


Management
Management

VS.RscGroup.TxMean- Multi-mode: None

Speed GSM: GBFD-118605 IP QOS

Management
Management
1.8 Measurement of IP PM performance (IPPM)

Overview
The object type IP PM measurement contains the function subset related to the IP performance
monitoring (PM). It represents the traffic volume and the service qualities of the transmission
board in the base station.
FunctionSubSets
Transport.IPPM Measurement related to IPPM
1.8.1 Measurement related to IPPM (Transport.IPPM)
Overview
The IP PM function subset provides the measurements on an IP PM in the base station. It
measures the quality of traffic carried on the transmission boards. Figure 1-8 shows the position
of the IP PM in the TCP/IP model. Figure 1-9 shows the principles of the IP PM. The IP PM
checks the packet loss, delay, and jitter condition of a link by the local end transmitting forward
monitoring (FM) frames and the peer end responding with backward reporting (BR) frames. The
number of FM frames is used to represent the number of frames transmitted by the local end,
whereas that of BR frames is used to represent the number of frames received by the peer end.
The local end calculates the delay, jitter, and packet loss rate along the local-to-peer direction
based on the received BR frames. Ultimately, the bandwidth condition is obtained.

Figure 1-8
Figure 1-9
Counters
Description
1542455408 VS.IPPM.Bits.Mea Average bit transmit V100R008C00,and

nsTx rate on the IP PM the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455409 VS.IPPM.Pkts.Mea Average packet V100R008C00,and

nsTx transmit rate on the the mapping single-
IP PM mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455410 VS.IPPM.Peak.Bits Peak bit transmit rate V100R008C00,and

.RateTx on the IP PM the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455411 VS.IPPM.Peak.Pkt Peak packet transmit V100R008C00,and

s.RateTx rate on the IP PM the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455412 VS.IPPM.Peer.Bits Average peer bit V100R008C00,and

.MeansRx receive rate on the IP the mapping single-
PM mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455413 VS.IPPM.Peer.Pkts Average peer packet V100R008C00,and

.MeansRx receive rate on the IP the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455414 VS.IPPM.Peer.Pea Peak peer bit receive V100R008C00,and

k.Bits.RateRx rate on the IP PM the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455415 VS.IPPM.Peer.Pea Peak peer packet V100R008C00,and

k.Pkts.RateRx receive rate on the IP the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455416 VS.IPPM.Forword. Average forward V100R008C00,and

DropMeans packet loss rate on the mapping single-
the IP PM mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455417 VS.IPPM.Forword. Peak forward packet V100R008C00,and

Peak.DropRates loss rate on the IP PM the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455418 VS.IPPM.Forward. Standard deviation of V100R008C00,and

JitterStandardDe- forward jitter on the the mapping single-
viation IP PM mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455419 VS.IPPM.Back.Jit- Standard deviation of V100R008C00,and

terStandardDevia- backward jitter on the mapping single-
tion the IP PM mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455420 VS.IPPM.Rtt.Mean Average RTT on the V100R008C00,and

s IP PM the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455421 VS.IPPM.MaxRtt- Maximum RTT on V100R008C00,and

Delay the IP PM the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455452 VS.IPPM.Min- Minimum RTT on V100R008C00,and

RttDelay the IP PM the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455911 VS.IPPM.Local.Tx Number of packets V100R008C00,and

Pkts sent by the IP PM the mapping single-
local end mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455912 VS.IPPM.Peer.RxP Number of packets V100R008C00,and

kts received by the IP the mapping single-
PM peer end mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
None
1.8.1.1 Byte Rate Measurements on the IP PM
Counters
Description
1542455408 VS.IPPM.Bits.Mean Average bit transmit DBS3900 WCDMA/

sTx rate on the IP PM BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455410 VS.IPPM.Peak.Bits. Peak bit transmit rate DBS3900 WCDMA/

RateTx on the IP PM BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455412 VS.IPPM.Peer.Bits. Average peer bit DBS3900 WCDMA/

MeansRx receive rate on the IP BTS3900 WCDMA/
PM BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455414 VS.IPPM.Peer.Peak. Peak peer bit receive DBS3900 WCDMA/

Bits.RateRx rate on the IP PM BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
These counters provide transmit byte rates and receive byte rates of the transport network on the
IP performance monitor (IP PM) within a measurement period. They indicate the transmission
capability of the transport network.
Measurement Points
The transmit byte rate or receive byte rate at the local or peer end is sampled per second on the
IP PM. At the end of a measurement period, the average or maximum of these sampling results
is used as the value of the corresponding counter.
Formula
None
Unit
bit/s
Related Features
VS.IPPM.Bits.MeansTx Multi-mode: None

GSM: GBFD-118607 IP Performance Monitor
TDLOFD-003012 IP Performance Monitoring

IP Performance Monitoring
VS.IPPM.Peak.Bits.RateTx Multi-mode: None


VS.IPPM.Peer.Bits.MeansR Multi-mode: None

x GSM: GBFD-118607 IP Performance Monitor


VS.IPPM.Peer.Peak.Bits.Ra Multi-mode: None

teRx GSM: GBFD-118607 IP Performance Monitor

1.8.1.2 Packet Rate Measurements on the IP PM
Counters
Description
1542455409 VS.IPPM.Pkts.Mean Average packet DBS3900 WCDMA/

sTx transmit rate on the BTS3900 WCDMA/
IP PM BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455411 VS.IPPM.Peak.Pkts. Peak packet transmit DBS3900 WCDMA/

RateTx rate on the IP PM BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455413 VS.IPPM.Peer.Pkts. Average peer packet DBS3900 WCDMA/

MeansRx receive rate on the IP BTS3900 WCDMA/
PM BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455415 VS.IPPM.Peer.Peak. Peak peer packet DBS3900 WCDMA/

Pkts.RateRx receive rate on the IP BTS3900 WCDMA/
PM BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters provide transmit packet rates and receive packet rates of the transport network
on the IP performance monitor (IP PM) within a measurement period. They indicate the
transmission capability of the transport network.
Measurement Points
The transmit packet rate or receive packet rate at the local or peer end is sampled per second on
the IP PM. At the end of a measurement period, the average or maximum of these sampling
Formula
None

Unit
packet/s
Related Features
VS.IPPM.Pkts.MeansTx Multi-mode: None


VS.IPPM.Peak.Pkts.RateTx Multi-mode: None


VS.IPPM.Peer.Pkts.MeansR Multi-mode: None

x GSM: GBFD-118607 IP Performance Monitor

VS.IPPM.Peer.Peak.Pkts.Ra Multi-mode: None

teRx GSM: GBFD-118607 IP Performance Monitor

1.8.1.3 Forward Packet Loss Rate Measurements on the IP PM

Counters
Description
1542455416 VS.IPPM.Forword. Average forward DBS3900 WCDMA/

DropMeans packet loss rate on BTS3900 WCDMA/
the IP PM BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455417 VS.IPPM.Forword.P Peak forward packet DBS3900 WCDMA/

eak.DropRates loss rate on the IP PM BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters provide packet loss rate on the transport network by using the IP performance
monitor (IP PM) within a measurement period. They reflect the quality on the detected IP path.
Measurement Points
The number of forward packets transmitted and the number of forward packets lost over the link
are sampled and accumulated every second, respectively. The packet loss rate in a second is
obtained by dividing the number of forward packets lost in one second by the number of forward
packets transmitted in one second. At the end of the measurement period, the maximum packet
loss rate is the maximum one among all the packet loss rates in the measurement period, and the
average packet loss rate is obtained by dividing the total number of lost forward packets by the
total number of forward packets transmitted in the measurement period.

Formula
(([VS.IPPM.Local.TxPkts]-[VS.IPPM.Peer.RxPkts])/[VS.IPPM.Local.TxPkts])*{100}
Unit
%
Related Features
VS.IPPM.Forword.Drop- Multi-mode: None

Means GSM: GBFD-118607 IP Performance Monitor

VS.IPPM.Forword.Peak.Dro Multi-mode: None

pRates GSM: GBFD-118607 IP Performance Monitor

1.8.1.4 Jitter Measurements on the IP PM

Counters
Description
1542455418 VS.IPPM.Forward.Ji Standard deviation of DBS3900 WCDMA/

tterStandardDevia- forward jitter on the BTS3900 WCDMA/
tion IP PM BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455419 VS.IPPM.Back.Jit- Standard deviation of DBS3900 WCDMA/

terStandardDevia- backward jitter on BTS3900 WCDMA/
tion the IP PM BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters provide the standard delay deviation of the round trip time (RTT) for the IP PM
packets on the transport network within a measurement period. They reflect the stabilization of
the transmission delay of a detected data flow. A larger counter value reflects a larger fluctuation
in transmission delay. The forward delay variation represents the delay variation in the RTT of
IP PM packets from the local end to the peer end. The backward delay variation represents the
delay variation in the RTT of IP PM packets from the peer end to the local end.
Measurement Points
A sample is taken every 1 second to obtain the forward jitter and backward jitter of the IP PM
for calculating the forward jitter standard deviation and backward jitter standard deviation at the
end of a measurement period based on the standard deviation formula.

The counter VS.IPPM.Forward.JitterStandardDeviation provides the jitter standard deviation of

FM frames on a link at the end of a measurement period. The forward jitter is calculated by using
the following formula: Forward jitter = T2 - T1 - T, where T2 is the time when the FM frame is
received, T1 is the time when the FM frame is sent, and T is the standard delay.
The counter VS.IPPM.Back.JitterStandardDeviation provides the jitter standard deviation of BR

frames on a link at the end of a measurement period. The backward jitter is calculated by using
the following formula: Backward jitter = T4 - T3 - T, where T4 is the time when the BR frame
is received, T3 is the time when the BR frame is sent, and T is the standard delay.
Formula
None
Unit
ms
Related Features
VS.IPPM.Forward.Jitter- Multi-mode: None

StandardDeviation GSM: GBFD-118607 IP Performance Monitor

VS.IPPM.Back.JitterStan- Multi-mode: None

dardDeviation GSM: GBFD-118607 IP Performance Monitor

1.8.1.5 RTT Measurements on the IP PM

Counters
Description
1542455420 VS.IPPM.Rtt.Means Average RTT on the DBS3900 WCDMA/

IP PM BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455421 VS.IPPM.MaxRtt- Maximum RTT on DBS3900 WCDMA/

Delay the IP PM BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455452 VS.IPPM.Min- Minimum RTT on DBS3900 WCDMA/

RttDelay the IP PM BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
These counters provide the latency of the round trip time (RTT) for the IP PM packets on the
transport network within a measurement period. They reflect the time delay on the transport
network.
Measurement Points
The RTT is sampled and calculated by the IP PM mechanism every second.
After forward activation is performed for an IP PM link, the local end sends FM frames and
receives BR frames periodically.
The value of the VS.IPPM.Rtt.Means counter can be calculated in the following formula:
VS.IPPM.Rtt.Means counter = Total delay of FM and BR frames/Total number of transmitted
FM frames.
The maximum delay of the sampling delays of FM frames and BR frames is used as the value
of the VS.IPPM.MaxRttDelay counter.
The minimum delay of the sampling delays of FM frames and BR frames is used as the value
of the VS.IPPM.MinRttDelay counter.
Formula
None
Unit
ms
Related Features
VS.IPPM.Rtt.Means Multi-mode: None


VS.IPPM.MaxRttDelay Multi-mode: None



VS.IPPM.MinRttDelay Multi-mode: None


1.8.1.6 Number of Packets on the IP PM
Counters
Description
1542455911 VS.IPPM.Local.TxP Number of packets DBS3900 WCDMA/

kts sent by the IP PM BTS3900 WCDMA/
local end BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455912 VS.IPPM.Peer.RxPk Number of packets DBS3900 WCDMA/

ts received by the IP BTS3900 WCDMA/
PM peer end BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
These counters provide the number of packets sent by the local end of an IP PM session and the
number of packets received by the peer end of an IP PM session. They reflect the service traffic
volume on IP paths measured by IP PM.
Measurement Points
The base station takes samples of the number of packets sent by the local end of an IP PM session
and the number of packets received by the peer end of an IP PM session every measurement
period of 1 second. At the end of each measurement period, the base station adds up all sampled
values to obtain the value of the corresponding counter.
Formula
None
Unit
packet
Related Features
VS.IPPM.Local.TxPkts Multi-mode: None


VS.IPPM.Peer.RxPkts Multi-mode: None


1.9 Measurement of SCTP performance (SCTP)

Overview
The object type SCTP Measurement contains the function subset related to the Stream Control
Transmission Protocol (SCTP) link of the base station. It represents the traffic volume of
signaling services carried by the SCTP link and the quality of service.

FunctionSubSets
Transport.SCTP Measurement related to SCTP link
1.9.1 Measurement related to SCTP link (Transport.SCTP)
Overview
The SCTP function subset measures the traffic volumes of IP packets transmitted and received
on an SCTP link inside the base station. It measures traffic volumes of the signaling services
carried on base station transmission boards and the service quality. Figure 1-10 shows the
position of the SCTP layer in the TCP/IP model.
Figure 1-10

Counters
Description
1542455422 VS.Sctp.RxBytes Number of bytes in version earlier than

the IP packets V100R008C00,and
received on the the mapping single-
SCTP mode base station
versions that
introduce this
counter are:
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455423 VS.Sctp.TxBytes Number of bytes in version earlier than

the IP packets V100R008C00,and
transmitted on the the mapping single-
SCTP mode base station
versions that
introduce this
counter are:
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455424 VS.Sctp.RxPkts Number of IP version earlier than

packets received on V100R008C00,and
the SCTP the mapping single-
mode base station
versions that
introduce this
counter are:
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455425 VS.Sctp.TxPkts Number of IP version earlier than

packets transmitted V100R008C00,and
on the SCTP the mapping single-
mode base station
versions that
introduce this
counter are:
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455426 VS.Sctp.RxDrop- Number of bytes in version earlier than

Bytes the IP packets V100R008C00,and
received but the mapping single-
discarded on the mode base station
SCTP version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1542455428 VS.Sctp.RxDropPk Number of discarded version earlier than

ts IP packets received V100R008C00,and
on the SCTP the mapping single-
mode base station
versions that
introduce this
counter are:
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455430 VS.Sctp.RxMax- Maximum IP packet version earlier than

Speed receive rate on the V100R008C00,and
SCTP the mapping single-
mode base station
versions that
introduce this
counter are:
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455431 VS.Sctp.RxMin- Minimum IP packet version earlier than

mode base station
versions that
introduce this
counter are:
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455432 VS.Sctp.RxMean- Average IP packet version earlier than

mode base station
versions that
introduce this
counter are:
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455433 VS.Sctp.TxMax- Maximum IP packet version earlier than

Speed transmit rate on the V100R008C00,and
mode base station
versions that
introduce this
counter are:
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455434 VS.Sctp.TxMin- Minimum IP packet version earlier than

mode base station
versions that
introduce this
counter are:
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455435 VS.Sctp.TxMean- Average IP packet version earlier than

mode base station
versions that
introduce this
counter are:
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
None
1.9.1.1 Number of Bytes in the IP Packets on the SCTP Link

Counters
Description
1542455422 VS.Sctp.RxBytes Number of bytes in DBS3900 WCDMA/

the IP packets BTS3900 WCDMA/
received on the BTS3900A
SCTP WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE
1542455423 VS.Sctp.TxBytes Number of bytes in DBS3900 WCDMA/

the IP packets BTS3900 WCDMA/
SCTP WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE
1542455426 VS.Sctp.RxDrop- Number of bytes in DBS3900 LTE/

Bytes the IP packets BTS3900 LTE/
received but BTS3900A LTE/
discarded on the BTS3900L LTE/
SCTP BTS3900AL LTE
Description
These counters provide the number of bytes in the packets received from or transmitted to the
IP layer on an SCTP link within a measurement period. They reflect the traffic of signaling
services. The counter VS.Sctp.RxDropBytes is not supported currently and the value of the
counter is always 0.
The counter 1542455422 VS.Sctp.RxBytes will be replaced with the VS.SctpLnk.RxBytes

counter in a later version. In the current version, either this counter or the VS.SctpLnk.RxBytes
counter is used, or they can both be used. The reported value of this counter may be normal or
invalid, and therefore this counter is not recommended for used. In later versions, only the
VS.SctpLnk.RxBytes counter is used.

The counter 1542455423 VS.Sctp.TxBytes will be replaced with the VS.SctpLnk.TxBytes

counter in a later version. In the current version, either this counter or the VS.SctpLnk.TxBytes
counter is used, or they can both be used. The reported value of this counter may be normal or
invalid, and therefore this counter is not recommended for used. In later versions, only the
VS.SctpLnk.TxBytes counter is used.
The counter 1542455426 VS.Sctp.RxDropBytes will be replaced with the

VS.SctpLnk.RxDropBytes counter in a later version. In the current version, either this counter
or the VS.SctpLnk.RxDropBytes counter is used, or they can both be used. The reported value
of this counter may be normal or invalid, and therefore this counter is not recommended for
used. In later versions, only the VS.SctpLnk.RxDropBytes counter is used.
Measurement Points
The number of bytes in the IP packets successfully transmitted or successfully received on the
SCTP link is sampled per second. At the end of a measurement period, the sum of these sampling
results is used as the value of the corresponding counter. The counter value includes the number
of bytes in user data (the data field of a user data packet, excluding the MAC header, IP header,
and SCTP header). This counter excludes the number of bytes in the following SCTP
management messages: Heartbeat messages, Link establishment messages, Link disconnection
messages, Handshake messages.
Formula
None
Unit
byte
Related Features
VS.Sctp.RxBytes Multi-mode: None

GSM: None
LTE: None on Iub Interface
VS.Sctp.TxBytes Multi-mode: None

GSM: None
VS.Sctp.RxDropBytes None None

1.9.1.2 Number of IP Packets on the SCTP Link
Counters
Description
1542455424 VS.Sctp.RxPkts Number of IP DBS3900 WCDMA/

packets received on BTS3900 WCDMA/
the SCTP BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE
1542455425 VS.Sctp.TxPkts Number of IP DBS3900 WCDMA/

packets transmitted BTS3900 WCDMA/
on the SCTP BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE
1542455428 VS.Sctp.RxDropPkt Number of discarded DBS3900 WCDMA/

s IP packets received BTS3900 WCDMA/
on the SCTP BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE

Description
These counters provide the number of packets received from or transmitted to the IP layer on
an SCTP link within a measurement period. They reflect the traffic of signaling services. IP
packets with any of the following errors are discarded on the SCTP link: parsing error, block
type error, and association query failure.
The counter 1542455424 VS.Sctp.RxPkts will be replaced with the VS.SctpLnk.RxPkts counter
in a later version. In the current version, either this counter or the VS.SctpLnk.RxPkts counter
is used, or they can both be used. The reported value of this counter may be normal or invalid,
and therefore this counter is not recommended for used. In later versions, only the
VS.SctpLnk.RxPkts is used.
The counter 1542455425 VS.Sctp.TxPkts will be replaced with the VS.SctpLnk.TxPkts counter
in a later version. In the current version, either this counter or the VS.SctpLnk.TxPkts counter
is used, or they can both be used. The reported value of this counter may be normal or invalid,
and therefore this counter is not recommended for used. In later versions, only the
VS.SctpLnk.TxPkts counter is used.
The counter 1542455428 VS.Sctp.RxDropPkts will be replaced with the

VS.SctpLnk.RxDropPkts counter in a later version. In the current version, either this counter or
the VS.SctpLnk.RxDropPkts counter is used, or they can both be used. The reported value of
this counter may be normal or invalid, and therefore this counter is not recommended for used.
In later versions, only the VS.SctpLnk.RxDropPkts counter is used.
Measurement Points
The number of IP packets successfully transmitted, successfully received, or discarded on the
of all the packets transmitted and received over an SCTP link. The packets include SCTP
management messages, such as heartbeat messages, link establishment messages, link
disconnection messages, and handshake messages. However, the received packets on an SCTP
link are not measured in any of the following cases: (1) The SCTP link is not configured. (2)
There is no signaling bearer at the upper layer of the SCTP link. (3) The SCTP link is blocked.
The VS.Sctp.RxPkts counter provides the number of IP packets received on the SCTP link.
The VS.Sctp.RxDropPkts counter provides the number of discarded IP packets received on the
SCTP link. An IP packet is discarded when any of the following occurs: (1) The chunk length
is incorrect in the packet. (2) The chunktype length is incorrect and the highest two bits are 10
in the packet. (3) The binding function of the packet is abnormal. For example, the DATA chunk
and ABORT chunk are in the same packet. (4) The packet can be parsed but an exception occurs
during the data check. For example, the V-tag is incorrect.
Formula
None
Unit
packet

Related Features
VS.Sctp.RxPkts Multi-mode: None

GSM: None
VS.Sctp.TxPkts Multi-mode: None

GSM: None
VS.Sctp.RxDropPkts Multi-mode: None

GSM: None
1.9.1.3 IP Packet Rate Measurements on the SCTP Link
Counters
Description
1542455430 VS.Sctp.RxMax- Maximum IP packet DBS3900 WCDMA/

Speed receive rate on the BTS3900 WCDMA/
SCTP BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE


Description
1542455431 VS.Sctp.RxMin- Minimum IP packet DBS3900 WCDMA/

SCTP BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE
1542455432 VS.Sctp.RxMean- Average IP packet DBS3900 WCDMA/

SCTP BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE
1542455433 VS.Sctp.TxMax- Maximum IP packet DBS3900 WCDMA/

Speed transmit rate on the BTS3900 WCDMA/
SCTP BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE


Description
1542455434 VS.Sctp.TxMin- Minimum IP packet DBS3900 WCDMA/

SCTP BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE
1542455435 VS.Sctp.TxMean- Average IP packet DBS3900 WCDMA/

SCTP BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE
Description
These counters provide the maximum rate, minimum rate, and average rate for transmitting or
receiving packets received from or transmitted to the IP layer on an SCTP link within a
measurement period. These rates are calculated on a per-byte basis. They reflect the transmission
capability on the SCTP link.
The counter 1542455430 VS.Sctp.RxMaxSpeed will be replaced with the
VS.SctpLnk.RxMaxSpeed counter in a later version. In the current version, either this counter
or the VS.SctpLnk.RxMaxSpeed counter is used, or they can both be used. The reported value
used. In later versions, only the VS.SctpLnk.RxMaxSpeed is used.
The counter 1542455431 VS.Sctp.RxMinSpeed will be replaced with the
VS.SctpLnk.RxMinSpeed counter in a later version. In the current version, either this counter
or the VS.SctpLnk.RxMinSpeed is used, or they can both be used. The reported value of this
counter may be normal or invalid, and therefore this counter is not recommended for used. In
later versions, only the VS.SctpLnk.RxMinSpeed counter is used.
The counter 1542455432 VS.Sctp.RxMeanSpeed will be replaced with the
VS.SctpLnk.RxMeanSpeed counter in a later version. In the current version, either this counter

or the VS.SctpLnk.RxMeanSpeed is used, or they can both be used. The reported value of this
later versions, only the VS.SctpLnk.RxMeanSpeed counter is used.
The counter 1542455433 VS.Sctp.TxMaxSpeed will be replaced with the

VS.SctpLnk.TxMaxSpeed counter in a later version. In the current version, either this counter
or the VS.SctpLnk.TxMaxSpeed counter is used, or they can both be used. The reported value
used. In later versions, only the VS.SctpLnk.TxMaxSpeed is used.
The counter 1542455434 VS.Sctp.TxMinSpeed will be replaced with the

VS.SctpLnk.TxMinSpeed counter in a later version. In the current version, either this counter
or the VS.SctpLnk.TxMinSpeed is used, or they can both be used. The reported value of this
later versions, only the VS.SctpLnk.TxMinSpeed counter is used.
The counter 1542455435 VS.Sctp.TxMeanSpeed will be replaced with the

VS.SctpLnk.TxMeanSpeed counter in a later version. In the current version, either this counter
or the VS.SctpLnk.TxMeanSpeed is used, or they can both be used. The reported value of this
later versions, only the VS.SctpLnk.TxMeanSpeed counter is used.
Measurement Points
The transmit rate or the receive rate on the SCTP link is sampled per second. At the end of a
Formula
None
Unit
bit/s
Related Features
VS.Sctp.RxMaxSpeed Multi-mode: None

GSM: None
VS.Sctp.RxMinSpeed Multi-mode: None

GSM: None

VS.Sctp.RxMeanSpeed Multi-mode: None

GSM: None
VS.Sctp.TxMaxSpeed Multi-mode: None

GSM: None
VS.Sctp.TxMinSpeed Multi-mode: None

GSM: None
VS.Sctp.TxMeanSpeed Multi-mode: None

GSM: None
1.10 Measurement of IPv6 performance (IPv6)

Overview
The IPv6 object type measures the function subset related to IPv6 packets on the transmission
board in the base station. It represents the throughput of IPv6 packets.
FunctionSubSets
Network.IPv6 Measurement related to IPv6
1.10.1 Measurement related to IPv6 (Network.IPv6)

Overview
The Network.IPv6 function subset measures the traffic volumes of IPv6 packets, such as the
number of successfully transmitted or received IPv6 packets or the number of bytes in the

transmitted or received IPv6 packets. It represents the throughput of IPv6 packets on the
transmission board in the base station. Figure 1-11 shows the position of the IPv6 in the TCP/
IP model.
Figure 1-11
Counters
Description
1542455796 VS.IPv6.TxPackets Number of V100R008C00,and

successfully the mapping single-
transmitted IPv6 mode base station
packets version that
introduce this
counter is:
eNodeB:V100R005
C00
1542455797 VS.IPv6.TxBytes Number of bytes in V100R008C00,and

transmitted IPv6 mode base station
introduce this
counter is:
eNodeB:V100R005
C00


Description
1542455798 VS.IPv6.TxDropPk Number of discarded V100R008C00,and

ts IPv6 packets the mapping single-
version that
introduce this
counter is:
eNodeB:V100R005
C00
1542455799 VS.IPv6.TxDrop- Number of bytes in V100R008C00,and

Bytes the discarded IPv6 the mapping single-
packets transmitted mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00
1542455800 VS.IPv6.RxPackets Number of V100R008C00,and

successfully received the mapping single-
IPv6 packets mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00
1542455801 VS.IPv6.RxBytes Number of bytes in V100R008C00,and

received IPv6 mode base station
introduce this
counter is:
eNodeB:V100R005
C00
1542455802 VS.IPv6.RxDropPk Number of discarded V100R008C00,and

ts IPv6 packets the mapping single-
received mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00


Description
1542455803 VS.IPv6.RxDrop- Number of bytes in V100R008C00,and

Bytes the discarded IPv6 the mapping single-
packets received mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00
None
1.10.1.1 Number of IPv6 Packets
Counters
Description
1542455796 VS.IPv6.TxPackets Number of DBS3900 LTE/

successfully BTS3900 LTE/
transmitted IPv6 BTS3900A LTE/
packets BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455798 VS.IPv6.TxDropPkt Number of discarded DBS3900 LTE/

s IPv6 packets BTS3900 LTE/
transmitted BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455800 VS.IPv6.RxPackets Number of DBS3900 LTE/

successfully received BTS3900 LTE/
IPv6 packets BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455802 VS.IPv6.RxDropPkt Number of discarded DBS3900 LTE/

s IPv6 packets BTS3900 LTE/
received BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters measure the number of IPv6 packets successfully transmitted, successfully
received, or discarded within a measurement period. They indicate the traffic on and the
Measurement Points
Number of successfully transmitted packets, discarded packets due to transmission failures,
successfully received packets, and discarded packets due to receive failures on the IPv6 path per
value of the corresponding counter. If packets need to be fragmented, the number of TX packets
is measured after the packets are fragmented and the number of RX packets is measured before
the packets are reassembled.
Formula
None
Unit
packet
Related Features
VS.IPv6.TxPackets Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-003006 IPv4/IPv6 Dual Stack
LOFD-003017 S1 and X2 over IPv6
TDLBFD-003006 IPv4/IPv6 Dual Stack
TDLOFD-003017 S1 and X2 over IPv6

VS.IPv6.TxDropPkts Multi-mode: None

GSM: None
UMTS: None
VS.IPv6.RxPackets Multi-mode: None

GSM: None
UMTS: None
VS.IPv6.RxDropPkts Multi-mode: None

GSM: None
UMTS: None
1.10.1.2 Number of Bytes in the IPv6 Packets
Counters
Description
1542455797 VS.IPv6.TxBytes Number of bytes in DBS3900 LTE/

the successfully BTS3900 LTE/
transmitted IPv6 BTS3900A LTE/
BTS3900AL LTE,
BTS3900


Description
1542455799 VS.IPv6.TxDrop- Number of bytes in DBS3900 LTE/

Bytes the discarded IPv6 BTS3900 LTE/
packets transmitted BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455801 VS.IPv6.RxBytes Number of bytes in DBS3900 LTE/

the successfully BTS3900 LTE/
received IPv6 BTS3900A LTE/
BTS3900AL LTE,
BTS3900
1542455803 VS.IPv6.RxDrop- Number of bytes in DBS3900 LTE/

Bytes the discarded IPv6 BTS3900 LTE/
packets received BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters measure the number of bytes in the successfully transmitted, successfully
received, or discarded IPv6 packets within a measurement period. They indicate the traffic and
the processing capability of the base station at the network layer.
Measurement Points
Number of successfully transmitted bytes, discarded bytes due to transmission failures,
successfully received bytes, and discarded bytes due to receive failures on the IPv6 path per
value of the corresponding counter. If packets need to be fragmented, the number of TX bytes
is measured after the packets are fragmented and the number of RX bytes is measured before
the packets are reassembled.
Formula
None
Unit
byte

Related Features
VS.IPv6.TxBytes Multi-mode: None

GSM: None
UMTS: None
VS.IPv6.TxDropBytes Multi-mode: None

GSM: None
UMTS: None
VS.IPv6.RxBytes Multi-mode: None

GSM: None
UMTS: None
VS.IPv6.RxDropBytes Multi-mode: None

GSM: None
UMTS: None
1.11 Measurement of IPv6Path performance (IPv6Path)

Overview
The IPv6Path object type measures the function subset related to the IPv6 path on the
transmission board in the base station. It represents traffic volumes of the services carried by
the IPv6 path and the service quality.

FunctionSubSets
Transport.IPv6Path Measurement related to IPv6Path
1.11.1 Measurement related to IPv6Path (Transport.IPv6Path)
Overview
The Transport.IPv6Path function subset measures the traffic volumes of real-time or non-real-
time services on the IPv6 path, such as the number of successfully received, successfully
transmitted, or discarded packets. It represents the traffic volumes of the services carried by the
IPv6 path on the transmission board in the base station and the service quality. Figure 1-12
shows the position of the IPv6Path in the TCP/IP model.
Figure 1-12
Counters
Description
1542455804 VS.IPv6Path.TxRt Number of Real- V100R008C00,and

Pkts Time Service the mapping single-
Packets Successfully mode base station
Transmitted on the version that
IPv6 Path introduce this
counter is:
eNodeB:V100R005
C00


Description
1542455805 VS.IPv6Path.TxRt Number of Bytes in V100R008C00,and

Bytes the Real-Time the mapping single-
Service Packets mode base station
Successfully version that
Transmitted on the introduce this
IPv6 Path counter is:
eNodeB:V100R005
C00
1542455808 VS.IPv6Path.RxRt Number of Real- V100R008C00,and

Pkts Time Service the mapping single-
Received on the IPv6 version that
Path introduce this
counter is:
eNodeB:V100R005
C00
1542455809 VS.IPv6Path.RxRt Number of Bytes in V100R008C00,and

Bytes the Real-Time the mapping single-
Received on the IPv6 introduce this
Path counter is:
eNodeB:V100R005
C00
1542455812 VS.IPv6Path.TxNr Number of Non- V100R008C00,and

tPkts Real-Time Service the mapping single-
Transmitted on the version that
IPv6 Path introduce this
counter is:
eNodeB:V100R005
C00
1542455813 VS.IPv6Path.TxNr Number of Bytes in V100R008C00,and

tBytes the Non-Real-Time the mapping single-
Transmitted on the introduce this
IPv6 Path counter is:
eNodeB:V100R005
C00


Description
1542455816 VS.IPv6Path.RxNr Number of Non- V100R008C00,and

tPkts Real-Time Service the mapping single-
Received on the IPv6 version that
Path introduce this
counter is:
eNodeB:V100R005
C00
1542455817 VS.IPv6Path.RxNr Number of Bytes in V100R008C00,and

tBytes the Non-Real-Time the mapping single-
Received on the IPv6 introduce this
Path counter is:
eNodeB:V100R005
C00
None
1.11.1.1 Number of Real-Time Service Packets on the IPv6 Path
Counters
Description
1542455804 VS.IPv6Path.TxRtP Number of Real- DBS3900 LTE/

kts Time Service BTS3900 LTE/
Packets Successfully BTS3900A LTE/
Transmitted on the BTS3900L LTE/
IPv6 Path BTS3900AL LTE,
BTS3900
1542455808 VS.IPv6Path.RxRtP Number of Real- DBS3900 LTE/

kts Time Service BTS3900 LTE/
Received on the IPv6 BTS3900L LTE/
Path BTS3900AL LTE,
BTS3900

Description
IPv6Path within a measurement period, respectively. They indicate the real-time service traffic
at the IP layer on the IPv6Path. Real-time services include voice services, video on demand
(real-time streams), and real-time games. Real-time service data is generally the UDP-based
stream media data.
VS.IPv6Path.TxRtPkts The number of real-time service packets that

are successfully transmitted on the IPv6 path
is sampled per second. At the end of a
measurement period, the sum of these
sampling results is used as the value of the
counter.
VS.IPv6Path.RxRtPkts The number of real-time service packets that

are successfully received on the IPv6 path is
sampled per second. At the end of a
counter.
Measurement Points
The number of real-time service packets that are successfully transmitted or received on the IPv6
path is sampled per second. At the end of a measurement period, the sum of these sampling
results is used as the value of the counter.
Formula
None
Unit
packet

Related Features
VS.IPv6Path.TxRtPkts Multi-mode: None

GSM: None
UMTS: None
VS.IPv6Path.RxRtPkts Multi-mode: None

GSM: None
UMTS: None
1.11.1.2 Number of Bytes in the Real-Time Service Packets on the IPv6 Path
Counters
Description
1542455805 VS.IPv6Path.TxRtB Number of Bytes in DBS3900 LTE/

ytes the Real-Time BTS3900 LTE/
Service Packets BTS3900A LTE/
Successfully BTS3900L LTE/
Transmitted on the BTS3900AL LTE,
IPv6 Path BTS3900
1542455809 VS.IPv6Path.RxRtB Number of Bytes in DBS3900 LTE/

ytes the Real-Time BTS3900 LTE/
Received on the IPv6 BTS3900AL LTE,
Path BTS3900
Description
received on an IPv6Path within a measurement period, respectively. They indicate the real-time

service traffic at the IP layer on the IPv6Path. Real-time services include voice services, video
on demand (real-time streams), and real-time games. Real-time service data is generally the
UDP-based stream media data.
VS.IPv6Path.TxRtBytes The number of bytes in the real-time service

packets that are successfully transmitted on
the IPv6 path is sampled per second. At the
end of a measurement period, the sum of these
counter.
VS.IPv6Path.RxRtBytes The number of bytes in the real-time service

packets that are successfully received on the
IPv6 path is sampled per second. At the end
of a measurement period, the sum of these
counter.
Measurement Points
The number of bytes in the real-time service packets that are successfully transmitted or received
on the IPv6 path is sampled per second. At the end of a measurement period, the sum of these
sampling results is used as the value of the counter.
In IPSec scenarios, the IPv6Path.RxRtBytes counter measures the number of bytes in the
decrypted IP packets successfully received after reassembly, and the IPv6Path.TxRtBytes
counter measures the number of bytes in the encrypted IP packets successfully transmitted before
fragment.
In non-IPSec scenarios, the IPv6Path.RxRtBytes counter measures the number of bytes in the
IP packets successfully received after reassembly, and the IPv6Path.TxRtBytes counter
measures the number of bytes in the IP packets successfully transmitted before fragment.
Formula
None
Unit
byte

Related Features
VS.IPv6Path.TxRtBytes Multi-mode: None

GSM: None
UMTS: None
VS.IPv6Path.RxRtBytes Multi-mode: None

GSM: None
UMTS: None
1.11.1.3 Number of Non-Real-Time Service Packets on the IPv6 Path
Counters
Description
1542455812 VS.IPv6Path.TxNrt Number of Non- DBS3900 LTE/

Pkts Real-Time Service BTS3900 LTE/
Transmitted on the BTS3900L LTE/
IPv6 Path BTS3900AL LTE,
BTS3900
1542455816 VS.IPv6Path.RxNrt Number of Non- DBS3900 LTE/

Pkts Real-Time Service BTS3900 LTE/
Received on the IPv6 BTS3900L LTE/
Path BTS3900AL LTE,
BTS3900
Description
IPv6Path within a measurement period, respectively. They indicate the non-real-time service

traffic at the IP layer on the IPv6Path. Non-real-time services include video on demand (that is,
buffer streams), interactive games, and TCP-based data streams.
VS.IPv6Path.TxNrtPkts The number of non-real-time service packets

that are successfully transmitted on the IPv6
path is sampled per second. At the end of a
counter.
VS.IPv6Path.RxNrtPkts The number of non-real-time service packets

that are successfully received on the IPv6
path is sampled per second. At the end of a
counter.
Measurement Points
The number of non-real-time service packets that are successfully transmitted or received on the
IPv6 path is sampled per second. At the end of a measurement period, the sum of these sampling
results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
VS.IPv6Path.TxNrtPkts Multi-mode: None

GSM: None
UMTS: None

VS.IPv6Path.RxNrtPkts Multi-mode: None

GSM: None
UMTS: None
1.11.1.4 Number of Bytes in the Non-Real-Time Service Packets on the IPv6 Path
Counters
Description
1542455813 VS.IPv6Path.TxNrt Number of Bytes in DBS3900 LTE/

Bytes the Non-Real-Time BTS3900 LTE/
Transmitted on the BTS3900AL LTE,
IPv6 Path BTS3900
1542455817 VS.IPv6Path.RxNrt Number of Bytes in DBS3900 LTE/

Bytes the Non-Real-Time BTS3900 LTE/
Received on the IPv6 BTS3900AL LTE,
Path BTS3900
Description
received on an IPv6Path within a measurement period, respectively. They indicate the non-real-
time service traffic at the IP layer on the IPv6Path. Non-real-time services include video on
demand (that is, buffer streams), interactive games, and TCP-based data streams.

VS.IPv6Path.TxNrtBytes The number of bytes in the non-real-time

service packets that are successfully
transmitted on the IPv6 path is sampled per
second. At the end of a measurement period,
the sum of these sampling results is used as
the value of the counter.
VS.IPv6Path.RxNrtBytes The number of bytes in the non-real-time

service packets that are successfully received
on the IPv6 path is sampled per second. At the
end of a measurement period, the sum of these
counter.
Measurement Points
The number of bytes in the non-real-time service packets that are successfully transmitted or
received on the IPv6 path is sampled per second. At the end of a measurement period, the sum
of these sampling results is used as the value of the counter.
In IPSec scenarios, the IPv6Path.RxNrtBytes counter measures the number of bytes in the
decrypted IP packets successfully received after reassembly, and the IPv6Path.TxNrtBytes
counter measures the number of bytes in the encrypted IP packets successfully transmitted before
fragment.
In non-IPSec scenarios, the IPv6Path.RxNrtBytes counter measures the number of bytes in the
IP packets successfully received after reassembly, and the IPv6Path.TxNrtBytes counter
measures the number of bytes in the IP packets successfully transmitted before fragment.
Formula
None
Unit
byte

Related Features
VS.IPv6Path.TxNrtBytes Multi-mode: None

GSM: None
UMTS: None
VS.IPv6Path.RxNrtBytes Multi-mode: None

GSM: None
UMTS: None
1.12 Measurement of OMCH performance (OMCH)

Overview
The object type OMCH measurement contains the OM channel-related function subset. It
represents the traffic volume of services carried by the OM channel in the base station and the
quality of service.
FunctionSubSets
Transport.OMCH Measurement related to OMCH
1.12.1 Measurement related to OMCH (Transport.OMCH)
Overview
The OMCH function subset provides the measurements on an OM channel in the base station.
It measures traffic volumes of the services carried on the OM channel in the base station and the
service quality. The OM channel uses TCP packets for transmission. Figure 1-13 shows the
position of the OM channel in the TCP/IP model.

Figure 1-13
Counters
Description
1542455826 VS.OMCH.RxTo- Total Number of V100R008C00,and

talPkts Packets Received on the mapping single-
the OM Channel mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455827 VS.OMCH.RxIn- Number of In-Order V100R008C00,and

SeqPkts Packets Received on the mapping single-
the OM Channel mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455828 VS.OMCH.RxWnd Number of Window V100R008C00,and

ProbePkts Probe Packets the mapping single-
Received on the OM mode base station
Channel versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455829 VS.OMCH.RxWnd Number of the V100R008C00,and

UpdatePkts Window Size Update the mapping single-
Packets Received on mode base station
the OM Channel versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455833 VS.OMCH.RxDup Number of Fully V100R008C00,and

Pkts Duplicated Packets the mapping single-
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455834 VS.OMCH.RxPart Number of Partially V100R008C00,and

DupPkts Duplicated Packets the mapping single-
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455835 VS.OMCH.RxOut Number of Out-of- V100R008C00,and

OfOrderPkts Order Packets the mapping single-
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455836 VS.OMCH.RxAf- Number of Packets V100R008C00,and

terWndPkts Beyond the Receive the mapping single-
Window of the OM mode base station
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455837 VS.OMCH.RxAfte Number of Packets V100R008C00,and

rClosePkts Received on the OM the mapping single-
Channel After the mode base station
Connection Is versions that
Released introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455838 VS.OMCH.RxAck Number of ACKs V100R008C00,and

Pkts Received on the OM the mapping single-
Channel mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455839 VS.OMCH.RxDu- Number of V100R008C00,and

pAckPkts Duplicated ACKs the mapping single-
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455840 VS.OMCH.RxToo Number of Received V100R008C00,and

MuchAckPkts ACKs for the Non- the mapping single-
Transmitted Data on mode base station
the OM Channel versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455841 VS.OMCH.TxTo- Total Number of V100R008C00,and

talPkts Packets Transmitted the mapping single-
on the OM Channel mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455842 VS.OMCH.TxUr- Number of Urgent V100R008C00,and

gentPkts Data Packets the mapping single-
OM Channel versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455843 VS.OMCH.TxCtrl Number of Control V100R008C00,and

Pkts Packets Transmitted the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455844 VS.OMCH.TxWnd Number of Window V100R008C00,and

ProbePkts Probe Packets the mapping single-
OM Channel versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455845 VS.OMCH.TxWnd Number of the V100R008C00,and

UpdatePkts Window Size Update the mapping single-
Packets Transmitted mode base station
on the OM Channel versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00


Description
1542455846 VS.OMCH.TxDa- Number of Data V100R008C00,and

taPkts Packets Transmitted the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455847 VS.OMCH.TxData Number of Packets V100R008C00,and

RexntPkts Retransmitted on the the mapping single-
OM Channel mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
1542455848 VS.OMCH.TxAck Number of ACKs V100R008C00,and

OnlyPkts Transmitted on the the mapping single-
OM Channel mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:Version
earlier than
V100R003C00
None

1.12.1.1 Total Number of Packets Received on the OM Channel
Counters
Description
1542455826 VS.OMCH.RxTo- Total Number of DBS3900 WCDMA/

talPkts Packets Received on BTS3900 WCDMA/
the OM Channel BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the total number of TCP packets received on the OM channel within a
measurement period. It represents the traffic on the OM channel.
Measurement Points
The number of packets received on the OM channel is sampled per second. At the end of a
measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet

Related Features
VS.OMCH.RxTotalPkts Multi-mode: None


on Iub Interface
1.12.1.2 VS.OMCH.RxInSeqPkts
Counters
Description
1542455827 VS.OMCH.RxIn- Number of In-Order DBS3900 WCDMA/

SeqPkts Packets Received on BTS3900 WCDMA/
the OM Channel BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of in-order TCP packets with lengths of non-zero received
on the OM channel within a measurement period. It represents the quality of the OM channel.
Measurement Points
The number of in-order packets received on the OM channel is sampled per second. At the end
Formula
None

Unit
packet
Related Features
VS.OMCH.RxInSeqPkts Multi-mode: None


on Iub Interface
1.12.1.3 VS.OMCH.RxWndProbePkts
Counters
Description
1542455828 VS.OMCH.RxWnd Number of Window DBS3900 WCDMA/

ProbePkts Probe Packets BTS3900 WCDMA/
Received on the OM BTS3900A
Channel WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the total number of window probe packets received on the OM channel
within a measurement period. It represents the traffic on the OM channel. After the local end
informs the peer end that the receiving window size is zero, the peer end periodically sends
window probe packets to check the size of the receiving window at the local end.

Measurement Points
The number of window probe packets received on the OM channel is sampled per second. At
counter.
Formula
None
Unit
packet
Related Features
VS.OMCH.RxWndPro- Multi-mode: None

bePkts GSM: GBFD-118601 IP Transmission Introduction

on Iub Interface
1.12.1.4 VS.OMCH.RxWndUpdatePkts
Counters
Description
1542455829 VS.OMCH.RxWnd Number of the DBS3900 WCDMA/

UpdatePkts Window Size Update BTS3900 WCDMA/
Packets Received on BTS3900A
the OM Channel WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
This counter measures the number of the window size update packets received on the OM
channel within a measurement period. The peer end transmits such a packet when the peer end
receives a probe packet from the local end or when the window size at the peer end changes.
This counter represents the quality of the OM channel.
Measurement Points
The number of the window size update packets received on the OM channel is sampled per
value of the counter.
Formula
None
Unit
packet
Related Features
VS.OMCH.RxWndUpda- Multi-mode: None

tePkts GSM: GBFD-118601 IP Transmission Introduction

on Iub Interface
1.12.1.5 VS.OMCH.RxDupPkts

Counters
Description
1542455833 VS.OMCH.RxDupP Number of Fully DBS3900 WCDMA/

kts Duplicated Packets BTS3900 WCDMA/
Channel WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of fully duplicated ACKs received on the OM channel within
a measurement period. It represents the quality of the OM channel. Two packets are fully
duplicated if they have the same sequence number and the same data. This counter indicates the
channel quality and the receive capability of the transmitter.
Measurement Points
The number of fully duplicated packets received on the OM channel is sampled per second. At
counter.
Formula
None
Unit
packet

Related Features
VS.OMCH.RxDupPkts Multi-mode: None


on Iub Interface
1.12.1.6 VS.OMCH.RxPartDupPkts
Counters
Description
1542455834 VS.OMCH.RxPart- Number of Partially DBS3900 WCDMA/

DupPkts Duplicated Packets BTS3900 WCDMA/
Channel WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of partially duplicated packets received on the OM channel
within a measurement period. It represents the quality of the OM channel. Two packets are
partially duplicated if they have the same data. This counter indicates the channel quality and
the receive capability of the transmitter.
Measurement Points
The number of partially duplicated packets received on the OM channel is sampled per second.
the counter.

Formula
None
Unit
packet
Related Features
VS.OMCH.RxPartDupPkts Multi-mode: None


on Iub Interface
1.12.1.7 VS.OMCH.RxOutOfOrderPkts
Counters
Description
1542455835 VS.OMCH.RxOutO Number of Out-of- DBS3900 WCDMA/

fOrderPkts Order Packets BTS3900 WCDMA/
Channel WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of out-of-order packets received on the OM channel within
a measurement period. It represents the quality of the OM channel.

Measurement Points
The number of out-of-order packets received on the OM channel is sampled per second. At the
end of a measurement period, the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
VS.OMCH.RxOutOfOr- Multi-mode: None

derPkts GSM: GBFD-118601 IP Transmission Introduction

on Iub Interface
1.12.1.8 VS.OMCH.RxAfterWndPkts
Counters
Description
1542455836 VS.OMCH.RxAf- Number of Packets DBS3900 WCDMA/

terWndPkts Beyond the Receive BTS3900 WCDMA/
Window of the OM BTS3900A
Channel WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
This counter measures the number of packets beyond the receive window of the OM channel
within the measurement period. A packet falls beyond the receive window of the OM channel
when its size is larger than the receive capacity of the receive window. This counter indicates
the quality of service of the OM channel.
Measurement Points
The number of packets beyond the receive window of the OM channel is sampled per second.
the counter.
Formula
None
Unit
packet
Related Features
VS.OMCH.RxAf- Multi-mode: None

terWndPkts GSM: GBFD-118601 IP Transmission Introduction

on Iub Interface
1.12.1.9 VS.OMCH.RxAfterClosePkts

Counters
Description
1542455837 VS.OMCH.RxAfter- Number of Packets DBS3900 WCDMA/

ClosePkts Received on the OM BTS3900 WCDMA/
Channel After the BTS3900A
Connection Is WCDMA/
Released BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of packets with the FIN bit set to 1 that are received on the
OM channel within a measurement period. The FIN packet indicates the packet received on the
OM channel after the connection is released. Certain data is buffered during transmission, which
causes the receiver to receive some packets after the connection is released. This counter
represents the quality of the OM channel and the network.
Measurement Points
The number of packets received on the OM channel after the connection is released is sampled
Formula
None
Unit
packet

Related Features
VS.OMCH.RxAfterClo- Multi-mode: None

sePkts GSM: GBFD-118601 IP Transmission Introduction

on Iub Interface
1.12.1.10 Number of ACKs Received on the OM Channel
Counters
Description
1542455838 VS.OMCH.RxAckP Number of ACKs DBS3900 WCDMA/

kts Received on the OM BTS3900 WCDMA/
Channel BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of acknowledge messages (ACKs), that is, messages have
only ACK information or other information, received on the OM channel within a measurement
period. An acknowledge message is a message with the ACK flag being set. It represents the
quality of the OM channel.
Measurement Points
The number of ACKs received on the OM channel is sampled per second. At the end of a

Formula
None
Unit
packet
Related Features
VS.OMCH.RxAckPkts Multi-mode: None


on Iub Interface
1.12.1.11 VS.OMCH.RxDupAckPkts
Counters
Description
1542455839 VS.OMCH.RxDu- Number of DBS3900 WCDMA/

pAckPkts Duplicated ACKs BTS3900 WCDMA/
Channel WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of duplicated ACKs received on the OM channel within a
measurement period. It represents the quality of the OM channel.

Measurement Points
The number of duplicated ACKs received on the OM channel is sampled per second. At the end
Formula
None
Unit
packet
Related Features
VS.OMCH.RxDupAckPkts Multi-mode: None


on Iub Interface
1.12.1.12 VS.OMCH.RxTooMuchAckPkts
Counters
Description
1542455840 VS.OMCH.RxToo Number of Received DBS3900 WCDMA/

MuchAckPkts ACKs for the Non- BTS3900 WCDMA/
Transmitted Data on BTS3900A
the OM Channel WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
This counter measures the number of received ACKs for the data that has not been transmitted
on the OM channel within a measurement period. This counter indicates the quality of the OM
channel.
Measurement Points
The number of received ACKs for the data that has not been transmitted on the OM channel is
used as the value of the counter.
Formula
None
Unit
packet
Related Features
VS.OMCH.RxTooMu- Multi-mode: None

chAckPkts GSM: GBFD-118601 IP Transmission Introduction

on Iub Interface
1.12.1.13 Total Number of Packets Transmitted on the OM Channel

Counters
Description
1542455841 VS.OMCH.TxTo- Total Number of DBS3900 WCDMA/

talPkts Packets Transmitted BTS3900 WCDMA/
on the OM Channel BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the total number of TCP packets successfully transmitted on the OM
channel within a measurement period. The TCP packet includes the control packet, data packet,
and keep-alive packet. This counter represents the traffic on the OM channel.
Measurement Points
The number of packets transmitted on the OM channel is sampled per second. At the end of a
Formula
None
Unit
packet

Related Features
VS.OMCH.TxTotalPkts Multi-mode: None


on Iub Interface
1.12.1.14 VS.OMCH.TxUrgentPkts
Counters
Description
1542455842 VS.OMCH.TxUr- Number of Urgent DBS3900 WCDMA/

gentPkts Data Packets BTS3900 WCDMA/
OM Channel WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of all urgent data packets transmitted on the OM channel
within a measurement period. It represents the traffic on the OM channel. An urgent data packet
is a TCP packet with the URG bit set to 1.
Measurement Points
The number of urgent data packets transmitted on the OM channel is sampled per second. At
counter.

Formula
None
Unit
packet
Related Features
VS.OMCH.TxUrgentPkts Multi-mode: None


on Iub Interface
1.12.1.15 Number of Control Packets Transmitted on the OM Channel
Counters
Description
1542455843 VS.OMCH.TxCtrlP Number of Control DBS3900 WCDMA/

kts Packets Transmitted BTS3900 WCDMA/
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of control all packets transmitted on the OM channel within
a measurement period. It represents the traffic on the OM channel. The control packet is used
for connection setup or connection release. It is a TCP packet with the SYN bit, FIN bit, and
RST bit all set and with no data.

Measurement Points
The number of control packets transmitted on the OM channel is sampled per second. At the
Formula
None
Unit
packet
Related Features
VS.OMCH.TxCtrlPkts Multi-mode: None


on Iub Interface
1.12.1.16 VS.OMCH.TxWndProbePkts
Counters
Description
1542455844 VS.OMCH.TxWndP Number of Window DBS3900 WCDMA/

robePkts Probe Packets BTS3900 WCDMA/
OM Channel WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
This counter measures the number of all window probe packets transmitted on the OM channel
within a measurement period. It represents the traffic on the OM channel. If the local end receives
an ACK from the peer end indicating that the receiving window size is zero, the local end will
send a one-byte TCP packet, that is, a window probe packet, to the peer end after waiting for a
period of time. Window probe packets transmitted on the OM channel are used to determine
whether the receiver can still receive packets, that is, whether the actual receiving window size
is zero. In general, a larger value of this counter indicates a larger extent that the receive capability
is stronger than the transmit capability.
Measurement Points
The number of detection packets transmitted on the OM channel is sampled per second. At the
Formula
None
Unit
packet
Related Features
VS.OMCH.TxWndPro- Multi-mode: None

bePkts GSM: GBFD-118601 IP Transmission Introduction

on Iub Interface
1.12.1.17 VS.OMCH.TxWndUpdatePkts

Counters
Description
1542455845 VS.OMCH.TxWnd Number of the DBS3900 WCDMA/

UpdatePkts Window Size Update BTS3900 WCDMA/
Packets Transmitted BTS3900A
on the OM Channel WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of all window size update packets transmitted on the OM
channel within a measurement period. Such a packet is transmitted as a response to the window
probe packet. It only includes the window size update information and has no data. This counter
represents the quality of the OM channel.
Measurement Points
The number of window size update packets transmitted on the OM channel is sampled per
Formula
None
Unit
packet

Related Features
VS.OMCH.TxWndUpda- Multi-mode: None

tePkts GSM: GBFD-118601 IP Transmission Introduction

on Iub Interface
1.12.1.18 Number of Data Packets Transmitted on the OM Channel
Counters
Description
1542455846 VS.OMCH.TxDa- Number of Data DBS3900 WCDMA/

taPkts Packets Transmitted BTS3900 WCDMA/
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of all data packets transmitted on the OM channel within a
measurement period. It represents the traffic on the OM channel.
Measurement Points
The number of data packets transmitted on the OM channel is sampled per second. At the end
Formula
None

Unit
packet
Related Features
VS.OMCH.TxDataPkts Multi-mode: None


on Iub Interface
1.12.1.19 Number of Packets Retransmitted on the OM Channel
Counters
Description
1542455847 VS.OMCH.TxData Number of Packets DBS3900 WCDMA/

RexntPkts Retransmitted on the BTS3900 WCDMA/
OM Channel BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of all packets retransmitted on the OM channel within a
measurement period. The transmitter retransmits a packet if no ACK message for the packet is
received within a specified time. This counter represents the quality of the OM channel.
Measurement Points
The number of packets retransmitted on the OM channel is sampled per second. At the end of
a measurement period, the sum of these sampling results is used as the value of the counter.

Formula
None
Unit
packet
Related Features
VS.OMCH.TxDataR- Multi-mode: None

exntPkts GSM: GBFD-118601 IP Transmission Introduction

on Iub Interface
1.12.1.20 Number of ACKs Transmitted on the OM Channel
Counters
Description
1542455848 VS.OMCH.TxAckO Number of ACKs DBS3900 WCDMA/

nlyPkts Transmitted on the BTS3900 WCDMA/
OM Channel BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of all ACKs, that is, the packets only include ACK
information and have no data, transmitted on the OM channel within a measurement period.
This counter represents the quality of the OM channel.

Measurement Points
The number of ACKs transmitted on the OM channel is sampled per second. At the end of a
Formula
None
Unit
packet
Related Features
VS.OMCH.TxAckOnlyPkts Multi-mode: None


on Iub Interface
1.13 Measurement of Tunnel performance (TUNNEL)

Overview
The object type Tunnel Measurement contains the tunnel-related function subset. It represents
the traffic volume of services carried by the tunnel in the base station and the quality of service.
FunctionSubSets
Network.Tunnel Measurement related to TUNNEL
1.13.1 Measurement related to TUNNEL (Network.Tunnel)
Overview
The Network.Tunnel function subset measures the traffic and data rate in the tunnel. It represents
the traffic volume of services carried by the tunnel in the base station and the quality of data
transmission. Figure 1-14 shows the position of the tunnel in the TCP/IP model.

Figure 1-14
Counters
Description
1542455856 VS.TUNNEL.TxBy Number of Bytes V100R008C00,and

tes Transmitted in the the mapping single-
Tunnel mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:V100R005
C00
1542455857 VS.TUNNEL.TxPa Number of Packets V100R008C00,and

ckets Transmitted in the the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:V100R005
C00


Description
1542455858 VS.TUNNEL.RxBy Number of Bytes V100R008C00,and

tes Received in the the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:V100R005
C00
1542455859 VS.TUNNEL.RxPa Number of Packets V100R008C00,and

ckets Received in the the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:V100R005
C00
1542455860 VS.TUNNEL.TxM Maximum Transmit V100R008C00,and

axSpeed Rate in the Tunnel the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:V100R005
C00


Description
1542455861 VS.TUNNEL.TxMi Minimum Transmit V100R008C00,and

nSpeed Rate in the Tunnel the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:V100R005
C00
1542455862 VS.TUNNEL.TxM Average Transmit V100R008C00,and

eanSpeed Rate in the Tunnel the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:V100R005
C00
1542455863 VS.TUNNEL.RxM Maximum Receive V100R008C00,and

axSpeed Rate in the Tunnel the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:V100R005
C00


Description
1542455864 VS.TUNNEL.RxMi Minimum Receive V100R008C00,and

nSpeed Rate in the Tunnel the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:V100R005
C00
1542455865 VS.TUNNEL.RxM Average Receive V100R008C00,and

eanSpeed Rate in the Tunnel the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R014C
00
eNodeB:V100R005
C00
None
1.13.1.1 Number of Bytes on the TUNNEL

Counters
Description
1542455856 VS.TUNNEL.TxByt Number of Bytes DBS3900 WCDMA/

es Transmitted in the BTS3900 WCDMA/
Tunnel BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455858 VS.TUNNEL.RxByt Number of Bytes DBS3900 WCDMA/

es Received in the BTS3900 WCDMA/
Tunnel BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
VS.TUNNEL.TxBytes This counter measures the number of bytes

transmitted in the tunnel at the network layer
traffic in the tunnel at the network layer
within the measurement period.

VS.TUNNEL.RxBytes This counter measures the number of bytes

received in the tunnel at the network layer
traffic in the tunnel at the network layer
Measurement Points
The number of bytes in the packets successfully transmitted or received in the tunnel is sampled
Formula
None
Unit
byte
Related Features
VS.TUNNEL.TxBytes Multi-mode: MRFD-211501 IP-Based Multi-mode Co-

MRFD-221501 Transmission on BS side
(GBTS)
MRFD-231501
IP-Based Multi-mode Co-
GSM: None (NodeB)
UMTS: None IP-Based Multi-mode Co-
LTE: None Transmission on BS side
(eNodeB)
Transmission on BS side
(LTE TDD)

VS.TUNNEL.RxBytes Multi-mode: MRFD-211501 IP-Based Multi-mode Co-

(GBTS)
MRFD-231501
GSM: None (NodeB)
(eNodeB)
(LTE TDD)
1.13.1.2 Number of Packets on the TUNNEL
Counters
Description
1542455857 VS.TUNNEL.TxPac Number of Packets DBS3900 WCDMA/

kets Transmitted in the BTS3900 WCDMA/
Tunnel BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455859 VS.TUNNEL.RxPac Number of Packets DBS3900 WCDMA/

kets Received in the BTS3900 WCDMA/
Tunnel BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
VS.TUNNEL.TxPackets This counter measures the number of packets

transmitted in the tunnel at the network layer
traffic and transmission quality in the tunnel
at the network layer within the measurement
period.
VS.TUNNEL.RxPackets This counter measures the number of packets

received in the tunnel at the network layer is
measured within a measurement period. It
indicates the traffic and transmission quality
in the tunnel at the network layer within the
measurement period.
Measurement Points
The number of packets successfully transmitted or received in the tunnel is sampled per second.
the counter.
Formula
None

Unit
packet
Related Features
VS.TUNNEL.TxPackets Multi-mode: MRFD-211501 IP-Based Multi-mode Co-

(GBTS)
MRFD-231501
GSM: None (NodeB)
(eNodeB)
(LTE TDD)
VS.TUNNEL.RxPackets Multi-mode: MRFD-211501 IP-Based Multi-mode Co-

(GBTS)
MRFD-231501
GSM: None (NodeB)
(eNodeB)
(LTE TDD)
1.13.1.3 Rate on the TUNNEL

Counters
Description
1542455860 VS.TUNNEL.TxMa Maximum Transmit DBS3900 WCDMA/

xSpeed Rate in the Tunnel BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455861 VS.TUNNEL.TxMi Minimum Transmit DBS3900 WCDMA/

nSpeed Rate in the Tunnel BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455862 VS.TUNNEL.TxMe Average Transmit DBS3900 WCDMA/

anSpeed Rate in the Tunnel BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455863 VS.TUNNEL.RxMa Maximum Receive DBS3900 WCDMA/

xSpeed Rate in the Tunnel BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455864 VS.TUNNEL.RxMi Minimum Receive DBS3900 WCDMA/

nSpeed Rate in the Tunnel BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455865 VS.TUNNEL.RxMe Average Receive DBS3900 WCDMA/

anSpeed Rate in the Tunnel BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
VS.TUNNEL.TxMaxSpeed This counter measures the maximum transmit

rate in the tunnel at the network layer within
measurement period.
VS.TUNNEL.TxMinSpeed This counter measures the minimum transmit

measurement period.
VS.TUNNEL.TxMeanSpeed This counter measures the average transmit

measurement period.
VS.TUNNEL.RxMaxSpeed This counter measures the maximum receive

measurement period.
VS.TUNNEL.RxMinSpeed This counter measures the minimum receive

measurement period.
VS.TUNNEL.RxMeanSpeed This counter measures the average receive

measurement period.
Measurement Points
Transmit rate and receive rate in the TUNNEL per second. At the end of a measurement period,
the maximum, minimum, average sampling results are reported.
Formula
None

Unit
bit/s
Related Features
VS.TUNNEL.TxMaxSpeed Multi-mode: MRFD-211501 IP-Based Multi-mode Co-

(GBTS)
MRFD-231501
GSM: None (NodeB)
(eNodeB)
(LTE TDD)
VS.TUNNEL.TxMinSpeed Multi-mode: MRFD-211501 IP-Based Multi-mode Co-

(GBTS)
MRFD-231501
GSM: None (NodeB)
(eNodeB)
(LTE TDD)

VS.TUNNEL.TxMean- Multi-mode: MRFD-211501 IP-Based Multi-mode Co-

Speed MRFD-221501 Transmission on BS side
(GBTS)
MRFD-231501
GSM: None (NodeB)
(eNodeB)
(LTE TDD)
VS.TUNNEL.RxMaxSpeed Multi-mode: MRFD-211501 IP-Based Multi-mode Co-

(GBTS)
MRFD-231501
GSM: None (NodeB)
(eNodeB)
(LTE TDD)

VS.TUNNEL.RxMinSpeed Multi-mode: MRFD-211501 IP-Based Multi-mode Co-

(GBTS)
MRFD-231501
GSM: None (NodeB)
(eNodeB)
(LTE TDD)
VS.TUNNEL.RxMean- Multi-mode: MRFD-211501 IP-Based Multi-mode Co-

Speed MRFD-221501 Transmission on BS side
(GBTS)
MRFD-231501
GSM: None (NodeB)
(eNodeB)
(LTE TDD)
1.14 Measurement of TRUNK performance (TRUNK)

Overview
The object type TRUNK measurement contains the TRUNK-related function subset. It
represents the traffic volume of services carried by the TRUNK in the base station and the quality
of service.

FunctionSubSets
Datalink.TRUNK Measurement related to TRUNK
1.14.1 Measurement related to TRUNK (Datalink.TRUNK)
Overview
The Datalink.TRUNK function subset measures the data rate in the TRUNK. It represents the
traffic volume of services carried by the TRUNK in the base station and the quality of service.
Counters
Description
1542460302 VS.TRUNK.TxTo- Total transmission V100R008C00,and

talBW bandwidth in the mapping single-
TRUNK link mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460303 VS.TRUNK.RxTo- Total receive V100R008C00,and

talBW bandwidth in the mapping single-
TRUNK link mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00


Description
1542460304 VS.TRUNK.RxMa Maximum Receive V100R008C00,and

xSpeed Rate in TRUNK the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460305 VS.TRUNK.RxMe Mean Receive Rate V100R008C00,and

anSpeed in the Tunnel the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460306 VS.TRUNK.TxMa Maximum transmit V100R008C00,and

xSpeed Rate in TRUNK the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00


Description
1542460307 VS.TRUNK.TxMe Mean transmit Rate V100R008C00,and

anSpeed in TRUNK the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
None
1.14.1.1 Available Bandwidth on the TRUNK
Counters
Description
1542460302 VS.TRUNK.TxTo- Total transmission DBS3900 WCDMA/

talBW bandwidth in BTS3900 WCDMA/
TRUNK link BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542460303 VS.TRUNK.RxTo- Total receive DBS3900 WCDMA/

talBW bandwidth in BTS3900 WCDMA/
TRUNK link BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters provide total transmit and receive bandwidth in TRUNK link in the current
measurement period, reflecting the TRUNK bandwidth.
VS.TRUNK.TxTotalBW Total transmission bandwidth in TRUNK

link is measured in the current measurement
period, reflecting the TRUNK bandwidth.
VS.TRUNK.RxTotalBW Total receive bandwidth in TRUNK link is

reflecting the TRUNK bandwidth.
Measurement Points
Available bandwidth in the transmit and receive directions of the trunk group per second. At the
Formula
None
Unit
kbit/s

Related Features
VS.TRUNK.TxTotalBW Multi-mode: MRFD-210103 Link Aggregation

GSM: None
UMTS: None
LTE: LOFD-003008 Ethernet Link Aggregation
TDLOFD-003008 (IEEE 802.3ad)
Ethernet Link Aggregation
(IEEE 802.3ad)
VS.TRUNK.RxTotalBW Multi-mode: MRFD-210103 Link Aggregation

GSM: None
UMTS: None
(IEEE 802.3ad)
1.14.1.2 Rate on the TRUNK
Counters
Description
1542460304 VS.TRUNK.RxMax Maximum Receive DBS3900 WCDMA/

Speed Rate in TRUNK BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542460305 VS.TRUNK.RxMea Mean Receive Rate DBS3900 WCDMA/

nSpeed in the Tunnel BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542460306 VS.TRUNK.TxMax Maximum transmit DBS3900 WCDMA/

Speed Rate in TRUNK BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542460307 VS.TRUNK.TxMea Mean transmit Rate DBS3900 WCDMA/

nSpeed in TRUNK BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
These counters provide the transmit rate and the receive rate in TRUNK in the current
measurement period, reflecting the TRUNK link quality.
VS.TRUNK.RxMaxSpeed Maximum Receive Rate in TRUNK is

reflecting the TRUNK link quality.
VS.TRUNK.RxMeanSpeed Mean Receive Rate in the Tunnel is measured

in the current measurement period, reflecting
the TRUNK link quality.
VS.TRUNK.TxMaxSpeed Maximum transmit Rate in TRUNK is

reflecting the TRUNK link quality.
VS.TRUNK.TxMeanSpeed Mean transmit Rate in TRUNK is measured

in the current measurement period, reflecting
the TRUNK link quality.
Measurement Points
The transmit rate or the receive rate on the trunk is sampled per second. At the end of a
Formula
None
Unit
kbit/s
Related Features
VS.TRUNK.RxMaxSpeed Multi-mode: MRFD-210103 Link Aggregation

GSM: None
UMTS: None
(IEEE 802.3ad)

VS.TRUNK.RxMeanSpeed Multi-mode: MRFD-210103 Link Aggregation

GSM: None
UMTS: None
(IEEE 802.3ad)
VS.TRUNK.TxMaxSpeed Multi-mode: MRFD-210103 Link Aggregation

GSM: None
UMTS: None
(IEEE 802.3ad)
VS.TRUNK.TxMeanSpeed Multi-mode: MRFD-210103 Link Aggregation

GSM: None
UMTS: None
(IEEE 802.3ad)
1.15 Measurement of firewall performance (Firewall)

Overview
The Firewall object type contains the function subsets related to the built-in firewall. It indicates
the security status of the base station.
FunctionSubSets
Transport.Firewall Measurement related to firewall
1.15.1 Measurement related to firewall (Transport.Firewall)

Overview
The firewall function subset measures the state of firewall, It helps to analyze the firewall state.

Counters
Description
1542460338 VS.Firewall.RxL2 Number of discarded V100R008C00,and

ACLFilter- packets due to L2 the mapping single-
DropPkts ACL filter based on mode base station
port versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460339 VS.Firewall.RxAd- Number of discarded V100R008C00,and

vACLFilter- packets due to the mapping single-
DropPkts advanced ACL filter mode base station
based on port versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
None
1.15.1.1 Number of discarded packets due to L2 ACL filter based on port

Counters
Description
1542460338 VS.Firewall.RxL2A Number of discarded DBS3900 WCDMA/

CLFilterDropPkts packets due to L2 BTS3900 WCDMA/
ACL filter based on BTS3900A
port WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of discarded packets due to L2 ACL filter based on port.
Measurement Points
The number of discarded packets received due to L2 ACL filter based on port is sampled per
Formula
None
Unit
packet

Related Features
VS.Firewall.RxL2ACLFil- Multi-mode: None

terDropPkts GSM: GBFD-118601 IP Transmission Introduction
LTE: LOFD-003014 IP Transmission Introduction

on Iub Interface
TDLOFD-003014
Integrated Firewall
Integrated Firewall
1.15.1.2 Number of discarded packets due to advanced ACL filter based on port
Counters
Description
1542460339 VS.Firewall.RxAd- Number of discarded DBS3900 WCDMA/

vACLFilter- packets due to BTS3900 WCDMA/
DropPkts advanced ACL filter BTS3900A
based on port WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of discarded packets due to advanced ACL filter based on
port. Advanced ACLs refer to L3 and L4 ACLs.
Measurement Points
The number of discarded packets received due to advanced ACL filter based on port is sampled

Formula
None
Unit
packet
Related Features
VS.Firewall.RxAdvACLFil- Multi-mode: None

terDropPkts GSM: GBFD-118601 IP Transmission Introduction

on Iub Interface
TDLOFD-003014
Integrated Firewall
Integrated Firewall
1.16 Measurement of IKE performance (IKE)

Overview
The IKE object type contains the function subsets related to the IKE. It indicates the IKE
negotiation traffic and the service quality.
FunctionSubSets
Transport.IKE Measurement related to IKE
1.16.1 Measurement related to IKE (Transport.IKE)
Overview
The IKE function subset measures the state of IKE.It helps to analyze the IKE state.

Counters
Description
1542460340 VS.IKE.RxPackets Number of IKE V100R008C00,and

packets received the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460341 VS.IKE.TxPackets Number of IKE V100R008C00,and

packets transmitted the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460342 VS.IKE.SubSARek Times of IKE sub SA V100R008C00,and

ey.Times rekey completed the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00


Description
1542460343 VS.IKE.DPDSessio Times of DPD V100R008C00,and

nFail.Times session fail the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
None
1.16.1.1 Number of IKE packets received
Counters
Description
1542460340 VS.IKE.RxPackets Number of IKE DBS3900 WCDMA/

packets received BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of IKE packets received by the base station.

Measurement Points
The number of IKE packets received is sampled per second. At the end of a measurement period,
the sum of these sampling results is used as the value of the counter.
Formula
None
Unit
packet
Related Features
VS.IKE.RxPackets Multi-mode: None

GSM: GBFD-113524 BTS Integrated IPsec
UMTS: WRFD-140209 NodeB Integrated IPsec
LTE: LOFD-003009 IPsec
TDLOFD-003009 IPsec
1.16.1.2 Number of IKE packets transmitted
Counters
Description
1542460341 VS.IKE.TxPackets Number of IKE DBS3900 WCDMA/

BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
This counter measures the number of IKE packets transmitted.
Measurement Points
The number of IKE packets transmitted is sampled per second. At the end of a measurement
Formula
None
Unit
packet
Related Features
VS.IKE.TxPackets Multi-mode: None

GSM: GBFD-113524 BTS Integrated IPsec
TDLOFD-003009 IPsec
1.16.1.3 Times of IKE sub SA rekey completed

Counters
Description
1542460342 VS.IKE.SubSAReke Times of IKE sub SA DBS3900 WCDMA/

y.Times rekey completed BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the times of IKE child SA rekey completed by the base station.
Measurement Points
When sub SA rekey completed, the counter will be added 1.
Formula
None
Unit
None
Related Features
VS.IKE.SubSARekey.Time Multi-mode: None

s GSM: GBFD-113524 BTS Integrated IPsec
TDLOFD-003009 IPsec

1.16.1.4 Times of DPD session fail
Counters
Description
1542460343 VS.IKE.DPDSessio Times of DPD DBS3900 WCDMA/

nFail.Times session fail BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the failure times of base station DPD session.
Measurement Points
Times of DPD session fail is sampled in 30 seconds. At the end of a measurement period, the
sum of these sampling results is used as the value of the counter.
Formula
None
Unit
None

Related Features
VS.IKE.DPDSessionFail.Ti Multi-mode: None

mes GSM: GBFD-113524 BTS Integrated IPsec
TDLOFD-003009 IPsec
1.17 Measurement of IPSec performance (IPSec)

Overview
The IPSec object type contains the function subsets related to IPSec. It indicates the IPSec traffic
and the service quality.
FunctionSubSets
Transport.IPSec Measurement related to IPSec
1.17.1 Measurement related to IPSec (Transport.IPSec)
Overview
The IPSec function subset measures the state of IPSec,It helps to analyze the IPSec state.

Counters
Description
1542460344 VS.IPSec.RxCheck Number of discarded V100R008C00,and

ReplayFail- packets received due the mapping single-
DropPkts to replay checking mode base station
fail versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460345 VS.IPSec.RxAH- Number of discarded V100R008C00,and

CheckFail- packets received due the mapping single-
DropPkts to AH checking fail mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460346 VS.IPSec.RxESP- Number of discarded V100R008C00,and

FailDropPkts packets received due the mapping single-
to ESP fail mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00


Description
1542460347 VS.IPSec.RxDe- Number of discarded V100R008C00,and

cryptACLFail- packets received due the mapping single-
DropPkts to decrypt ACL fail mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460348 VS.IPSec.RxDe- Number of decrypt V100R008C00,and

cryptSuccessPkts success packets the mapping single-
received mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460349 VS.IPSec.TxOut- Number of discarded V100R008C00,and

boundSAMiss- packets transmitted the mapping single-
DropPkts due to outbound SA mode base station
miss versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00


Description
1542460350 VS.IPSec.TxAntiR- Number of discarded V100R008C00,and

eplaySnWrapped- packets transmitted the mapping single-
DropPkts due to sequence mode base station
number overflow versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460351 VS.IPSec.TxEn- Number of encrypt V100R008C00,and

cryptSuccessPkts success packets the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
None
1.17.1.1 Number of discarded packets received due to replay checking fail

Counters
Description
1542460344 VS.IPSec.RxCheck- Number of discarded DBS3900 WCDMA/

ReplayFailDropPkts packets received due BTS3900 WCDMA/
to replay checking BTS3900A
fail WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of packets discarded by the base station RX due to the replay
checking.
Measurement Points
The number of discarded packets received due to replay checking fail is sampled per second. At
counter.
Formula
None
Unit
packet
Related Features
VS.IPSec.RxCheckReplay- Multi-mode: None

FailDropPkts GSM: GBFD-113524 BTS Integrated IPsec
TDLOFD-003009 IPsec

1.17.1.2 Number of discarded packets received due to AH checking fail
Counters
Description
1542460345 VS.IPSec.RxAH- Number of discarded DBS3900 WCDMA/

CheckFailDropPkts packets received due BTS3900 WCDMA/
to AH checking fail BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of packets discarded by the base station RX due to the AH
authentication failure.
Measurement Points
The number of discarded packets received due to AH checking fail is sampled per second. At
counter.
Formula
None
Unit
packet

Related Features
VS.IPSec.RxAHCheckFail- Multi-mode: None

DropPkts GSM: GBFD-113524 BTS Integrated IPsec
TDLOFD-003009 IPsec
1.17.1.3 Number of discarded packets received due to ESP fail
Counters
Description
1542460346 VS.IPSec.RxESP- Number of discarded DBS3900 WCDMA/

FailDropPkts packets received due BTS3900 WCDMA/
to ESP fail BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of packets discarded by the base station RX due to the ESP
authentication failure or decryption failure.
Measurement Points
The number of discarded packets received due to ESP fail is sampled per second. At the end of
Formula
None

Unit
packet
Related Features
VS.IPSec.RxESPFail- Multi-mode: None

DropPkts GSM: GBFD-113524 BTS Integrated IPsec
TDLOFD-003009 IPsec
1.17.1.4 Number of discarded packets received due to decrypt ACL fail
Counters
Description
1542460347 VS.IPSec.RxDe- Number of discarded DBS3900 WCDMA/

cryptACLFail- packets received due BTS3900 WCDMA/
DropPkts to decrypt ACL fail BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of packets discarded by the base station RX due to packets
that should not have been encrypted.
Measurement Points
The number of discarded packets received due to decrypt ACL fail is sampled per second. At
counter.

Formula
None
Unit
packet
Related Features
VS.IPSec.RxDecryptACL- Multi-mode: None

FailDropPkts GSM: GBFD-113524 BTS Integrated IPsec
TDLOFD-003009 IPsec
1.17.1.5 Number of decrypt success packets received
Counters
Description
1542460348 VS.IPSec.RxDe- Number of decrypt DBS3900 WCDMA/

cryptSuccessPkts success packets BTS3900 WCDMA/
received BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of packets successfully decrypted by the base station RX.

Measurement Points
The number of packets decryption successful received is sampled per second. At the end of a
Formula
None
Unit
packet
Related Features
VS.IPSec.RxDecryptSuc- Multi-mode: None

cessPkts GSM: GBFD-113524 BTS Integrated IPsec
TDLOFD-003009 IPsec
1.17.1.6 Number of discarded packets transmitted due to outbound SA miss
Counters
Description
1542460349 VS.IPSec.TxOut- Number of discarded DBS3900 WCDMA/

boundSAMiss- packets transmitted BTS3900 WCDMA/
DropPkts due to outbound SA BTS3900A
miss WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
This counter measures the number of packets discarded by the base station TX due to outbound
SA miss.
Measurement Points
The number of discarded packets transmitted due to outbound SA miss is sampled per second.
the counter.
Formula
None
Unit
packet
Related Features
VS.IPSec.TxOutboundSA- Multi-mode: None

MissDropPkts GSM: GBFD-113524 BTS Integrated IPsec
TDLOFD-003009 IPsec
1.17.1.7 Number of discarded packets transmitted due to sequence number

overflow

Counters
Description
1542460350 VS.IPSec.TxAntiR- Number of discarded DBS3900 WCDMA/

eplaySnWrapped- packets transmitted BTS3900 WCDMA/
DropPkts due to sequence BTS3900A
number overflow WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of packets discarded by the base station TX due to sequence
number overflow.
Measurement Points
The number of discarded packets transmitted due to sequence number overflow is sampled per
Formula
None
Unit
packet
Related Features
VS.IPSec.TxAntiReplaySn- Multi-mode: None

WrappedDropPkts GSM: GBFD-113524 BTS Integrated IPsec
TDLOFD-003009 IPsec

1.17.1.8 Number of encrypt success packets transmitted
Counters
Description
1542460351 VS.IPSec.TxEn- Number of encrypt DBS3900 WCDMA/

cryptSuccessPkts success packets BTS3900 WCDMA/
transmitted BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of packets successfully encrypted by the base station TX.
Measurement Points
The number of packets encryption successful transmitted is sampled per second. At the end of
Formula
None
Unit
packet

Related Features
VS.IPSec.TxEncryptSuc- Multi-mode: None

cessPkts GSM: GBFD-113524 BTS Integrated IPsec
TDLOFD-003009 IPsec
1.18 Measurement of SCTP Link performance (SCTPLNK)

Overview
The object type SCTPLNK Measurement contains the function subset related to the Stream
Control Transmission Protocol (SCTP) link of the base station. It represents the traffic volume
of signaling services carried by the SCTP link and the quality of service.
FunctionSubSets
Transport.SCTPLNK Measurement related to SCTPLNK
1.18.1 Measurement related to SCTPLNK (Transport.SCTPLNK)
Overview
The SCTPLNK function subset measures the traffic volumes of IP packets transmitted and
received on an SCTP link inside the base station. It measures traffic volumes of the signaling
services carried on base station transmission boards and the service quality.Figure 1-15 shows
the position of the SCTP layer in the TCP/IP model.

Figure 1-15
Counters
Description
1542460356 VS.SctpLnk.RxByt Number of bytes in V100R008C00,and

es the IP packets the mapping single-
received on the mode base station
SCTP link versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460357 VS.SctpLnk.TxByt Number of bytes in V100R008C00,and

es the IP packets the mapping single-
SCTP link versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00


Description
1542460358 VS.SctpLnk.RxPkt Number of IP V100R008C00,and

s packets received on the mapping single-
the SCTP link mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460359 VS.SctpLnk.TxPkt Number of IP V100R008C00,and

s packets transmitted the mapping single-
on the SCTP link mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460360 VS.SctpLnk.RxDro Number of discarded V100R008C00,and

pPkts IP packets received the mapping single-
on the SCTP link mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00


Description
1542460361 VS.SctpLnk.RxMa Maximum IP packet V100R008C00,and

xSpeed receive rate on the the mapping single-
SCTP link mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460362 VS.SctpLnk.RxMi Minimum IP packet V100R008C00,and

nSpeed receive rate on the the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460363 VS.SctpLnk.RxMe Average IP packet V100R008C00,and

anSpeed receive rate on the the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00


Description
1542460364 VS.SctpLnk.TxMa Maximum IP packet V100R008C00,and

xSpeed transmit rate on the the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460365 VS.SctpLnk.TxMin Minimum IP packet V100R008C00,and

Speed transmit rate on the the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460366 VS.SctpLnk.TxMe Average IP packet V100R008C00,and

anSpeed transmit rate on the the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00


Description
1542460367 VS.SctpLnk.ToU- Number of packets V100R008C00,and

serPkts transmitted from an the mapping single-
SCTP link to the mode base station
application layer versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460368 VS.SctpLnk.Fro- Number of packets V100R008C00,and

mUserPkts received on the the mapping single-
SCTP link from the mode base station
application layer versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460369 VS.SctpLnk.RePkt Number of chunks V100R008C00,and

s retransmitted from the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00


Description
1542460370 VS.SctpLnk.RxDro Number of discarded V100R008C00,and

pBytes IP bytes received on the mapping single-
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460371 VS.SctpLnk.Cong. Congestion Duration V100R008C00,and

Dur of an SCTP Link the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460372 VS.SctpLnk.Cong Number of V100R008C00,and

Congestions on an the mapping single-
SCTP Link mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00


Description
1542460373 VS.SctpLnk.Unava Duration of SCTP V100R008C00,and

il.Dur Link Unavailable the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542460374 VS.SctpLnk.Un- Number of Times V100R008C00,and

avail SCTP Link the mapping single-
Unavailable mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
None
1.18.1.1 Number of Bytes in the IP Packets on the SCTP link

Counters
Description
1542460356 VS.SctpLnk.RxByte Number of bytes in DBS3900 WCDMA/

s the IP packets BTS3900 WCDMA/
received on the BTS3900A
SCTP link WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542460357 VS.SctpLnk.TxByte Number of bytes in DBS3900 WCDMA/

s the IP packets BTS3900 WCDMA/
SCTP link WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542460370 VS.SctpLnk.RxDrop Number of discarded DBS3900 WCDMA/

Bytes IP bytes received on BTS3900 WCDMA/
the SCTP link BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
These counters measure the number of bytes in the IP packets transmitted or received on the
SCTP link within a measurement period. They represent the traffic volume of signaling services.
The counter measure the number of bytes discarded on the SCTP link within a measurement
period is not supported currently and the value of the counter VS.SctpLnk.RxDropBytes is
always 0.
VS.SctpLnk.RxBytes The counters measure the number of bytes in

the IP packets received on the SCTP link
within a measurement period.
VS.SctpLnk.TxBytes The counters measure the number of bytes in

the IP packets transmitted on the SCTP link
VS.SctpLnk.RxDropBytes The counters measure the number of bytes

discarded on the SCTP link within a
measurement period. The function is not
supported currently and the value of the
counter is always 0.
Measurement Points
The number of bytes in the IP packets successfully transmitted, successfully received or
discarded on the SCTP link is sampled per second. At the end of a measurement period, the sum
of these sampling results is used as the value of the corresponding counter. The counter value
includes the number of bytes in user data (the data field of a user data packet, excluding the
MAC header, IP header, and SCTP header). This counter excludes the number of bytes in the
following SCTP management messages: Heartbeat messages, Link establishment messages,
Link disconnection messages, Handshake messages.
Formula
None
Unit
byte

Related Features
VS.SctpLnk.RxBytes Multi-mode: None


on Iub Interface
VS.SctpLnk.TxBytes Multi-mode: None


on Iub Interface
VS.SctpLnk.RxDropBytes Multi-mode: None


on Iub Interface
1.18.1.2 Number of IP Packets on the SCTP link
Counters
Description
1542460358 VS.SctpLnk.RxPkts Number of IP DBS3900 WCDMA/

packets received on BTS3900 WCDMA/
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542460359 VS.SctpLnk.TxPkts Number of IP DBS3900 WCDMA/

on the SCTP link BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542460360 VS.SctpLnk.RxDrop Number of discarded DBS3900 WCDMA/

Pkts IP packets received BTS3900 WCDMA/
on the SCTP link BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters measure the number of IP packets transmitted or received or discarded on the
SCTP link within a measurement period. They represent the traffic volume of signaling services.
VS.SctpLnk.RxPkts The counters measure the number of IP

packets successfully received on the SCTP
link within a measurement period.
VS.SctpLnk.TxPkts The counters measure the number of IP

packets transmitted on the SCTP link within
a measurement period.

VS.SctpLnk.RxDropPkts The counters measure the number of IP

packets discarded on the SCTP link within a
measurement period, This counter excludes
the number of packets when the SCTP Link
is down.
Measurement Points
The number of IP packets successfully transmitted, successfully received or discarded on the
of all the packets received over an SCTP link. The packets include SCTP management messages,
such as heartbeat messages, link establishment messages, link disconnection messages, and
handshake messages. However, the received packets on an SCTP link are not measured in any
of the following cases: (1) The SCTP link is not configured. (2) There is no signaling bearer at
the upper layer of the SCTP link. (3) The SCTP link is blocked.
The VS.SctpLnk.RxPkts counter provides the number of IP packets received on the SCTP link.
A measured IP packet must carry the IP addresses and port numbers that can identify an SCTP
association. The following packets are measured: (1) ABORT packets. (2) Packets that pass the
code check (excluding the V-tag check) and can be sent to the corresponding association.
The VS.SctpLnk.RxDropPkts counter provides the number of discarded IP packets received on

the SCTP link. A measured IP packet must carry the IP addresses and port numbers that can
identify an SCTP association. An IP packet is discarded when any of the following occurs: (1)
The checksum is incorrect in the packet. (2) The chunk length is incorrect in the packet. (3) The
chunktype is abnormal and the highest two bits are 10 in the packet. (4) The chunktype is
abnormal and the highest two bits are not 10 in the packet. (5) The binding function of the packet
is abnormal. For example, the DATA chunk and ABORT chunk are in the same packet.
Formula
None
Unit
packet

Related Features
VS.SctpLnk.RxPkts Multi-mode: None


on Iub Interface
VS.SctpLnk.TxPkts Multi-mode: None


on Iub Interface
VS.SctpLnk.RxDropPkts Multi-mode: None


on Iub Interface
1.18.1.3 IP Packet Rate Measurements on the SCTP link
Counters
Description
1542460361 VS.SctpLnk.RxMax Maximum IP packet DBS3900 WCDMA/

SCTP link BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542460362 VS.SctpLnk.RxMin- Minimum IP packet DBS3900 WCDMA/

SCTP link BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542460363 VS.SctpLnk.RxMea Average IP packet DBS3900 WCDMA/

nSpeed receive rate on the BTS3900 WCDMA/
SCTP link BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542460364 VS.SctpLnk.TxMax Maximum IP packet DBS3900 WCDMA/

SCTP link BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542460365 VS.SctpLnk.TxMin- Minimum IP packet DBS3900 WCDMA/

SCTP link BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542460366 VS.SctpLnk.TxMea Average IP packet DBS3900 WCDMA/

nSpeed transmit rate on the BTS3900 WCDMA/
SCTP link BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters measure the maximum rate, minimum rate, and average rate for transmitting or
receiving IP packets on an SCTP link within a measurement period. These rates are calculated
on a per-byte basis. They represent the transmission capability of the SCTP link.
VS.SctpLnk.RxMaxSpeed These counters measure the maximum rate

receiving IP packets on an SCTP link within
a measurement period. These rates are
calculated on a per-byte basis.

VS.SctpLnk.RxMinSpeed These counters measure the minimum rate

VS.SctpLnk.RxMeanSpeed These counters measure the average rate

VS.SctpLnk.TxMaxSpeed These counters measure the maximum for

transmitting IP packets on an SCTP link
within a measurement period. These rates are
VS.SctpLnk.TxMinSpeed These counters measure the minimum for

VS.SctpLnk.TxMeanSpeed These counters measure the average for

Measurement Points
The transmit rate or the receive rate on the SCTP link is sampled per second. At the end of a
measurement period, the maximum rate, minimum rate or average rate of these sampling results
Formula
None
Unit
bit/s

Related Features
VS.SctpLnk.RxMaxSpeed Multi-mode: None


on Iub Interface
VS.SctpLnk.RxMinSpeed Multi-mode: None


on Iub Interface
VS.SctpLnk.RxMeanSpeed Multi-mode: None


on Iub Interface
VS.SctpLnk.TxMaxSpeed Multi-mode: None


on Iub Interface
VS.SctpLnk.TxMinSpeed Multi-mode: None


on Iub Interface
VS.SctpLnk.TxMeanSpeed Multi-mode: None


on Iub Interface

1.18.1.4 Number of packets on the SCTP link from the application layer
Counters
Description
1542460367 VS.SctpLnk.ToU- Number of packets DBS3900 WCDMA/

serPkts transmitted from an BTS3900 WCDMA/
SCTP link to the BTS3900A
application layer WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542460368 VS.SctpLnk.FromU- Number of packets DBS3900 WCDMA/

serPkts received on the BTS3900 WCDMA/
SCTP link from the BTS3900A
application layer WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters measure the number of user packets transmitted or received on the SCTP link
within a measurement period. They represent the traffic volume of signaling services.
VS.SctpLnk.ToUserPkts The counters measure the number of user

packets transmitted on the SCTP link within

VS.SctpLnk.FromUserPkts The counters measure the number of user

packets received on the SCTP link within a
measurement period.
Measurement Points
The number of packets received from or transmitted to the application layer on an SCTP link is
used as the value of the corresponding counters.
Formula
None
Unit
packet
Related Features
VS.SctpLnk.ToUserPkts Multi-mode: None


on Iub Interface
VS.SctpLnk.FromUserPkts Multi-mode: None


on Iub Interface
1.18.1.5 Number of chunks retransmitted from the SCTP link

Counters
Description
1542460369 VS.SctpLnk.RePkts Number of chunks DBS3900 WCDMA/

retransmitted from BTS3900 WCDMA/
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters measure the number of chunks retransmitted from the SCTP link. They represent
the transmission capability of the SCTP link.
VS.SctpLnk.RePkts The counters measure the number of chunks

retransmitted from the SCTP link.
Measurement Points
The number of packets retransmitted on an SCTP link is sampled per second. At the end of a
counters.
Formula
None
Unit
packet

Related Features
VS.SctpLnk.RePkts Multi-mode: None


on Iub Interface
1.18.1.6 Congestion Duration of an SCTP Link
Counters
Description
1542460371 VS.SctpLnk.Cong.D Congestion Duration DBS3900 WCDMA/

ur of an SCTP Link BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter provides the duration through which an SCTP link is in the congested state in a
measurement period.
Measurement Points
The congestion duration is sampled per second. At the end of a measurement period, the sum of
these sampling results is used as the value of the corresponding counter. An SCTP link is
considered congested when the buffered data of the SCTP link reaches the threshold.
Formula
None

Unit
s
Related Features
VS.SctpLnk.Cong.Dur Multi-mode: None


on Iub Interface
1.18.1.7 Number of Congestions on an SCTP Link
Counters
Description
1542460372 VS.SctpLnk.Cong Number of DBS3900 WCDMA/

Congestions on an BTS3900 WCDMA/
SCTP Link BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter provides the number of times that an SCTP link enters the congested state in a
measurement period.
Measurement Points
The number of congestion times is sampled per second. At the end of a measurement period,
the sum of these sampling results is used as the value of the corresponding counter. An SCTP
link is considered congested when the buffered data of the SCTP link reaches the threshold.

Formula
None
Unit
None
Related Features
VS.SctpLnk.Cong Multi-mode: None


on Iub Interface
1.18.1.8 Duration of SCTP Link Unavailable
Counters
Description
1542460373 VS.SctpLnk.Unavail Duration of SCTP DBS3900 WCDMA/

.Dur Link Unavailable BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter provides the duration through which an SCTP link is in the unavailable state.

Measurement Points
The duration through which an SCTP link is unavailable is sampled per second. At the end of a
counter. When an SCTP link is in the unavailable state, the link may be faulty or deactivated.
Due to time adjustment and measurement precision, the measurement result of the counter
VS.SctpLnk.Unavail.Dur may have an error of several seconds.
Formula
None
Unit
s
Related Features
VS.SctpLnk.Unavail.Dur Multi-mode: None


on Iub Interface
1.18.1.9 Number of Times SCTP Link Unavailable

Counters
Description
1542460374 VS.SctpLnk.Unavail Number of Times DBS3900 WCDMA/

SCTP Link BTS3900 WCDMA/
Unavailable BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter provides the number of times that an SCTP link is unavailable due to link
disconnection.
Measurement Points
The number of times that an SCTP link becomes unavailable is sampled per second. At the end
corresponding counter. When an SCTP link is in the unavailable state, the link may be faulty or
deactivated.
Formula
None
Unit
None

Related Features
VS.SctpLnk.Unavail Multi-mode: None


on Iub Interface
1.19 Measurement of UserPlaneHostIP performance

(UserPlaneHostIP)
Overview
The UserPlaneHostIP object type contains the function subsets related to the local IP addresses
on the user plane. It indicates the traffic of the user-plane services.
FunctionSubSets
Transport.UserPlaneHostIP Measurement related to UserPlaneHostIP
1.19.1 Measurement related to UserPlaneHostIP

(Transport.UserPlaneHostIP)
Overview
The UserPlaneHostIP function subset measures the IP packets and bytes in the IP packets
transmitted from and received by a user-plane local IP address. It helps analyze the transmission
quality of the system and ensure stable and reliable operation of the system.

Counters
Description
1542455526 VS.UserPlaneHostI Number of IP V100R008C00,and

P.TxPkts packets transmitted the mapping single-
on the user-plane mode base station
local IP address versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542455527 VS.UserPlaneHostI Number of IP V100R008C00,and

P.RxPkts packets received on the mapping single-
the user-plane local mode base station
IP address versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542455528 VS.UserPlaneHostI Number of bytes in V100R008C00,and

P.TxBytes the IP Packets the mapping single-
user-plane local IP versions that
address introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00


Description
1542455529 VS.UserPlaneHostI Number of bytes in V100R008C00,and

P.RxBytes the IP Packets the mapping single-
received on the user- mode base station
plane local IP versions that
address introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542455530 VS.UserPlaneHostI Maximum transmit V100R008C00,and

P.TxMaxSpeed rate of IP Packets on the mapping single-
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542455531 VS.UserPlaneHostI Average transmit V100R008C00,and

P.TxMeanSpeed rate of IP Packets on the mapping single-
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00


Description
1542455532 VS.UserPlaneHostI Maximum receive V100R008C00,and

P.RxMaxSpeed rate of IP Packets on the mapping single-
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1542455533 VS.UserPlaneHostI Average receive rate V100R008C00,and

P.RxMeanSpeed of IP Packets on the the mapping single-
user-plane local IP mode base station
address versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
None
1.19.1.1 Number of IP Packets on the User-Plane Local IP Address

Counters
Description
1542455526 VS.UserPlaneHostIP Number of IP DBS3900 WCDMA/

.TxPkts packets transmitted BTS3900 WCDMA/
on the user-plane BTS3900A
local IP address WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455527 VS.UserPlaneHostIP Number of IP DBS3900 WCDMA/

.RxPkts packets received on BTS3900 WCDMA/
the user-plane local BTS3900A
IP address WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters measure the number of packets received and transmitted based on the user-plane
local IP address at the IP layer within a measurement period. It indicates the traffic of a user-
plane local IP address at the IP layer.
VS.UserPlaneHostIP.TxPkts This counter measures the number of packets

transmitted based on the user-plane local IP
address at the IP layer within a measurement
period. It indicates the traffic of a user-plane
local IP address at the IP layer.

VS.UserPlaneHostIP.RxPkts This counter measures the number of packets

received based on the user-plane local IP
Measurement Points
The number of packets successfully transmitted or received on the user-plane local IP address
is sampled per second. At the end of a measurement period, the sum of these sampling results
is used as the value of the corresponding counter. The packets to be measured are IP packets. If
IP packets need to be fragmented, the number of TX packets is measured before the packets are
fragmented and the number of RX packets is measured after the packets are reassembled.
Formula
None
Unit
packet
Related Features
VS.UserPlaneHostIP.TxPkts Multi-mode: None


on Iub Interface
TDLOFD-002004
Self-configuration
Self-configuration
VS.UserPlaneHostIP.RxPkts Multi-mode: None


on Iub Interface
TDLOFD-002004
Self-configuration
Self-configuration
1.19.1.2 Number of Bytes in the IP Packets on the User-Plane Local IP Address

Counters
Description
1542455528 VS.UserPlaneHostIP Number of bytes in DBS3900 WCDMA/

.TxBytes the IP Packets BTS3900 WCDMA/
user-plane local IP WCDMA/
address BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455529 VS.UserPlaneHostIP Number of bytes in DBS3900 WCDMA/

.RxBytes the IP Packets BTS3900 WCDMA/
received on the user- BTS3900A
plane local IP WCDMA/
address BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters measure the number of bytes received and transmitted based on the user-plane
local IP address at the IP layer within a measurement period. It indicates the traffic of a user-
plane local IP address at the IP layer.
VS.UserPlaneHostIP.TxBytes This counter measures the number of bytes

transmitted based on the user-plane local IP

VS.UserPlaneHostIP.RxBytes This counter measures the number of bytes

received based on the user-plane local IP
Measurement Points
The number of bytes in the packets successfully transmitted or received on the user-plane local
IP address is sampled per second. At the end of a measurement period, the sum of these sampling
results is used as the value of the corresponding counter. The bytes to be measured include IP
packet header and payload. When IPSec is used, the bytes to be measured include IPSec-related
payloads, such as AH header and ESP header. If packets need to be fragmented, the number of
TX bytes is measured before the packets are fragmented and the number of RX bytes is measured
after the packets are reassembled.
Formula
None
Unit
byte
Related Features
VS.UserPlaneHostIP.TxByt Multi-mode: None

es GSM: GBFD-118601 IP Transmission Introduction

on Iub Interface
TDLOFD-002004
Self-configuration
Self-configuration
VS.UserPlaneHostIP.RxByt Multi-mode: None

es GSM: GBFD-118601 IP Transmission Introduction

on Iub Interface
TDLOFD-002004
Self-configuration
Self-configuration

1.19.1.3 Rate of IP Packets on the User-Plane Local IP Address
Counters
Description
1542455530 VS.UserPlaneHostIP Maximum transmit DBS3900 WCDMA/

.TxMaxSpeed rate of IP Packets on BTS3900 WCDMA/
IP address WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455531 VS.UserPlaneHostIP Average transmit DBS3900 WCDMA/

.TxMeanSpeed rate of IP Packets on BTS3900 WCDMA/
IP address WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1542455532 VS.UserPlaneHostIP Maximum receive DBS3900 WCDMA/

.RxMaxSpeed rate of IP Packets on BTS3900 WCDMA/
IP address WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1542455533 VS.UserPlaneHostIP Average receive rate DBS3900 WCDMA/

.RxMeanSpeed of IP Packets on the BTS3900 WCDMA/
user-plane local IP BTS3900A
address WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters measure receive and transmit rate based on the user-plane local IP address at the
IP layer within a measurement period. It indicates the load of a user-plane local IP address at
the IP layer.
VS.UserPlaneHostIP.TxMaxSpeed This counter measures the maximum transmit

rate based on the user-plane local IP address
at the IP layer within a measurement period.
It indicates the load of a user-plane local IP
address at the IP layer.

VS.UserPlaneHostIP.TxMeanSpeed This counter measures the average transmit

VS.UserPlaneHostIP.RxMaxSpeed This counter measures the maximum receive

VS.UserPlaneHostIP.RxMeanSpeed This counter measures the average receive

Measurement Points
The transmit rate or the receive rate on the user-plane local IP address is sampled per second.
At the end of a measurement period, the maximum and average sampling results are reported.
Formula
None
Unit
bit/s
Related Features
VS.UserPlaneHostIP.TxMa Multi-mode: None

xSpeed GSM: GBFD-118601 IP Transmission Introduction

on Iub Interface
TDLOFD-002004
Self-configuration
Self-configuration

VS.UserPlaneHostIP.TxMea Multi-mode: None

nSpeed GSM: GBFD-118601 IP Transmission Introduction

on Iub Interface
TDLOFD-002004
Self-configuration
Self-configuration
VS.UserPlaneHostIP.RxMa Multi-mode: None

xSpeed GSM: GBFD-118601 IP Transmission Introduction

on Iub Interface
TDLOFD-002004
Self-configuration
Self-configuration
VS.UserPlaneHostIP.RxMe Multi-mode: None

anSpeed GSM: GBFD-118601 IP Transmission Introduction

on Iub Interface
TDLOFD-002004
Self-configuration
Self-configuration
1.20 Measurement of GTP-U performance (GTP-U)

Overview
The object type NCell Measurement contains function subset related to the handover between
two specific cells in the base station. It represents the quality of each type of handover between
two specific cells.
FunctionSubSets
Transport.GTPU Measurement related to GTP-U

1.20.1 Measurement related to GTP-U (Transport.GTPU)
Overview
The Transport.Gtpu function subset measures the number of packets or the number of bytes in
the packets received or transmitted on the GTP-U link. It represents the data volume on the user
plane of the base station. The GTP-U layer uses UDP packets for transmission. Figure 1-16
shows the position of the GTP-U layer in the TCP/IP model.
Figure 1-16
Counters
Description
1526727075 VS.Gtpu.RxBytes Number of bytes in V100R008C00,and

the packets received the mapping single-
on the GTP-U link mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727076 VS.Gtpu.TxBytes Number of bytes in V100R008C00,and

GTP-U link version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526727077 VS.Gtpu.RxPkts Number of packets V100R008C00,and

received on the GTP- the mapping single-
U link mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727078 VS.Gtpu.TxPkts Number of packets V100R008C00,and

transmitted on the the mapping single-
GTP-U link mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727079 VS.Gtpu.RxDrop- Number of bytes in V100R008C00,and

Bytes the error packets the mapping single-
received on the GTP- mode base station
U link version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
None
1.20.1.1 Number of Bytes in the Packets on the GTP-U Link

Counters
Description
1526727075 VS.Gtpu.RxBytes Number of bytes in DBS3900 LTE/

the packets received BTS3900 LTE/
on the GTP-U link BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526727076 VS.Gtpu.TxBytes Number of bytes in DBS3900 LTE/

the packets BTS3900 LTE/
transmitted on the BTS3900A LTE/
GTP-U link BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526727079 VS.Gtpu.RxDrop- Number of bytes in DBS3900 LTE/

Bytes the error packets BTS3900 LTE/
received on the GTP- BTS3900A LTE/
U link BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters measure the number of bytes in the packets transmitted, received, and erroneous
in the receive direction respectively within a measurement period. Both GTP-U control messages
and user data are measured, as shown in Figure 1. These counters indicate the data volume
(including the GTP-U header) on the user plane.
VS.Gtpu.RxBytes The number of bytes in correctly received

packets on GTPU link in one measurement
period.
VS.Gtpu.TxBytes The number of bytes in correctly transmitted

period.
VS.Gtpu.RxDropBytes The number of bytes in incorrectly received

period.

Measurement Points
The number of bytes in the packets transmitted, received, or erroneous in the receive direction
on the GTP-U link is sampled per second. At the end of a measurement period, the sum of these
The counter VS.Gtpu.RxDropBytes measures the number of bytes in the erroneous packets
received at the GTP-U layer in the following cases:(1) Searching the inter working (ITW) table
fails.(2) Errors occur in version check.(3) The protocol type is incorrect.(4) The packet length
is incorrect.(5) The TEID is not a configured one.(6) An extra layer of extension header exist in
the packet.(7) The extension header is invalid.
Figure 1-17
Formula
None
Unit
byte
Related Features
None
1.20.1.2 Number of Packets on the GTP-U Link
Counters
Description
1526727077 VS.Gtpu.RxPkts Number of packets DBS3900 LTE/

received on the GTP- BTS3900 LTE/
U link BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1526727078 VS.Gtpu.TxPkts Number of packets DBS3900 LTE/

transmitted on the BTS3900 LTE/
GTP-U link BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
These counters measure the number of packets successfully received or transmitted on the GTP-
U link within a measurement period. They indicate the data volume on the user plane.
VS.Gtpu.RxPkts The number of correctly received packets on

GTPU link in one measurement period.
VS.Gtpu.TxPkts The number of correctly transmitted packets

on GTPU link in one measurement period.
Measurement Points
The number of packets successfully transmitted or received on the GTP-U link is sampled per
Formula
None
Unit
packet
Related Features
None

1.21 Measurement of Board performance (Board)

Overview
The object type Board Measurement contains the board-related function subset. It represents the
operating status of each board.
FunctionSubSets
Measurement related to CPU of board Board CPU Measurement (Board.CPU)
1.21.1 Measurement related to CPU of board (Measurement related

to CPU of board)
Overview
The Board.CPU function subset measures the CPU usage of the LMPT, UMPT and LBBP.
Counters
Description
1526727013 VS.Board.CPUload Maximum Board version earlier than

.Max CPU Usage V100R008C00,and
the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727014 VS.Board.CPUload Average Board CPU version earlier than

.Mean Usage V100R008C00,and
the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526728332 VS.Board.CPULoa Number of Times version earlier than

d.CumulativeHigh- that the CPU Usage V100R008C00,and
loadCount of Boards Exceeds the mapping single-
the Preconfigured mode base station
Threshold version that
introduce this
counter is:
eNodeB:V100R005
C00
None
1.21.1.1 Maximum and Average Board CPU Usage
Counters
Description
1526727013 VS.Board.CPUload. Maximum Board DBS3900 LTE/

Max CPU Usage BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE
1526727014 VS.Board.CPUload. Average Board CPU DBS3900 LTE/

Mean Usage BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE
Description
The counter measures the maximum and average CPU usage of the LMPT, UMPT and LBBP
In the current version, either counter 1526727013 VS.Board.CPUload.Max or the 1593835632
VS.BBUBoard.CPULoad.Max counter is used, or they can both be used. The reported value of
counter 1526727013 VS.Board.CPUload.Max is normal but counter 1526727013
VS.Board.CPUload.Max is not recommended for use. In a later version, only the 1593835632
VS.BBUBoard.CPUload.Max counter is used.
In the current version, either counter 1526727014 VS.Board.CPUload.Mean or the 1593835633
VS.BBUBoard.CPUload.Mean counter is used, or they can both be used. The reported value of

counter 1526727014 VS.Board.CPUload.Mean is normal but counter 1526727014

VS.Board.CPUload.Mean is not recommended for use. In a later version, only the 1593835633
VS.BBUBoard.CPUload.Mean counter is used.
Measurement Points
In the sampling interval of 5s, the CPU usage is sampled many times, and the average of these
sampling results is used as the average CPU usage of this sampling interval. The maximum or
the average of the final sampling results is used as the value of this counter. Each sampling result
is based on the maximum usage among multiple CPUs in the board. For example, if the number
of times that the average CPU usage exceeds the preconfigured threshold in the measurement
period is X1, X2, X3, ..., and Xn, the value of the VS.Board.CPUload.Max and
VS.Board.CPUload.Mean counters are calculated using the following formulae:
VS.Board.CPUload.Max = MAX(Xi), VS.Board.CPUload.Mean =(X1+X2+...+Xn)/n.
Formula
None
Unit
%
Related Features
VS.Board.CPUload.Max Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-004009 Real-time Monitoring of
TDLBFD-004009 System Running Information
Real-time Monitoring of
System Running Information
VS.Board.CPUload.Mean Multi-mode: None

GSM: None
UMTS: None
1.21.1.2 Number of Times that the CPU Usage of Boards Exceeds the Preconfigured
Threshold

Counters
Description
1526728332 VS.Board.CPULoad Number of Times DBS3900 LTE/

.CumulativeHigh- that the CPU Usage BTS3900 LTE/
loadCount of Boards Exceeds BTS3900A LTE/
the Preconfigured BTS3900L LTE/
Threshold BTS3900AL LTE
Description
The counter measures the number of times that the CPU usage of the LMPT, UMPT and the
LBBP exceeds the preconfigured threshold. It indicates the load status of boards during a
measurement period.
In the current version, either counter 1526728332

VS.Board.CPULoad.CumulativeHighloadCount or the 1593835630
VS.BBUBoard.CPULoad.CumulativeHighloadCount counter is used, or they can both be used.
The reported value of counter 1526728332 VS.Board.CPULoad.CumulativeHighloadCount is
normal but counter 1526728332 VS.Board.CPULoad.CumulativeHighloadCount is not
recommended for use. In a later version, only the 1593835630
VS.BBUBoard.CPULoad.CumulativeHighloadCount counter is used.
Measurement Points
sampling results is used as the average CPU usage of this sampling interval. At the end of a
measurement period, the number of times that the average CPU usage exceeds the preconfigured
threshold is used as the value of the counter. The preconfigured threshold is 85%. For example,
if the number of times that the average CPU usage exceeds the preconfigured threshold in the
measurement period is X1, X2, X3, ..., and Xn, the value of the
VS.Board.CPULoad.CumulativeHighloadCount counter is the sum of X1, X2, X3, ..., and Xn.
Formula
None
Unit
None

Related Features
VS.Board.CPULoad.Cumu- Multi-mode: None

lativeHighloadCount GSM: None
UMTS: None
1.22 Measurement of RRU performance (RRU)

Overview
The object type RRU Measurement contains the RRU or RFU-related function subset. It
represents the operating status of each RRU or RFU.
FunctionSubSets
Measurement related to RRU RRU Measurement (RRU.Device)
1.22.1 Measurement related to RRU (Measurement related to RRU)
Overview
The RRU.Device function subset measures the performance of the RRU, such as power
consumption.

Counters
Description
1526727065 VS.EnergyCons.R The counter version earlier than

RU measures the total V100R008C00,and
power consumption the mapping single-
of the RRU or RFU mode base station
within a version that
measurement period. introduce this
It provides data basis counter is:
for energy eNodeB:Version
conservation earlier than
policies. V100R003C00
None
1.22.1.1 RRU or RFU Power Consumption
Counters
Description
1526727065 VS.EnergyCons.RR The counter DBS3900 LTE/

U measures the total BTS3900 LTE/
power consumption BTS3900A LTE/
of the RRU or RFU BTS3900L LTE/
within a BTS3900AL LTE
measurement period.
It provides data basis
for energy
conservation
policies.
Description
The counter measures the total power consumption of the RRU or RFU within a measurement
period. It provides data basis for energy conservation policies.
The counter 1526727065 VS.EnergyCons.RRU can report in current version and will be
removed in later version. Counter 1526727065 VS.EnergyCons.RRU is not recommended for
use.

Measurement Points
The RRU or RFU power consumption is sampled every 5 minutes. At the end of a measurement
Formula
None
Unit
kWh
Related Features
VS.EnergyCons.RRU Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001041 Power Consumption
TDLOFD-001041 Monitoring
Power Consumption
Monitoring

Overview
The object type eNodeB Measurement contains the eNodeB-related function subsets. It
represents the operating status of the eNodeB.
FunctionSubSets
eNodeB.Device eNodeB Measurement (eNodeB.Device)
Measurement related to BBU BBU Measurement (BBU.Device)
LCS.ENODEB eNodeB LCS Measurement (LCS.ENODEB)
Traffic.User.eNodeB User Number Measurement (eNodeB)

(Traffic.User.eNodeB)
RIM.eNodeB eNodeB RIM Measurement

(RIM.ENODEB)

Traffic.Thruput.eNodeB eNodeB Throughput Measurement

(Traffic.Thruput.eNodeB)
SCTP.eNodeB eNodeB SCTP Measurement

(SCTP.eNodeB)
1.23.1 Measurement related to eNodeB (eNodeB.Device)
Overview
The eNodeB.Device function subset measures the performance of the eNodeB, such as power
consumption.
Counters
Description
1526728153 VS.EnergyCons.BT eNodeB Power version earlier than

S.Adding Consumption V100R008C00,and
the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526728210 VS.EnergyCons.BT eNodeB Power version earlier than

S.Measuring Consumption V100R008C00,and
Calculated by the the mapping single-
PMU mode base station
version that
introduce this
counter is:
eNodeB:V100R003
C00


Description
1526728215 VS.PSU.Shutdown- PSU shutdown total version earlier than

Time time V100R008C00,and
the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R003
C00
None
1.23.1.1 eNodeB Power Consumption
Counters
Description
1526728153 VS.EnergyCons.BT eNodeB Power DBS3900 LTE/

S.Adding Consumption BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE
Description
The counter measures the total power consumption of the eNodeB within a measurement period.
It provides data basis for energy conservation policies.
Counter 1526728153 VS.EnergyCons.BTS.Adding will be replaced by counter 1593835637
VS.EnergyCons.BTS.Adding.LTE in later versions. In the current version, counters
1526728153 VS.EnergyCons.BTS.Adding and 1593835637 VS.EnergyCons.BTS.Adding.LTE
are both valid, and the value of counter 1526728153 VS.EnergyCons.BTS.Adding is properly
reported. Counter 1526728153 VS.EnergyCons.BTS.Adding will be deleted in later versions.
Using counter 1526728153 VS.EnergyCons.BTS.Adding is not recommended.
Measurement Points
The estimated eNodeB power consumption is sampled every 5 minutes based on the power
consumption of the BBU, RRUs/RFUs, and peripheral devices such as electromechanical
devices and ALDs. At the end of a measurement period, the sum of these sampling results is
used as the value of this counter.

Formula
None
Unit
kWh
Related Features
VS.EnergyCons.BTS.Add- Multi-mode: None

ing GSM: None
UMTS: None
Power Consumption
Monitoring
1.23.1.2 eNodeB Power Consumption Calculated by the PMU
Counters
Description
1526728210 VS.EnergyCons.BT eNodeB Power DBS3900 LTE/

S.Measuring Consumption BTS3900 LTE/
Calculated by the BTS3900A LTE/
PMU BTS3900L LTE/
BTS3900AL LTE
Description
The counter measures the total power consumption monitored by all the PMUs within a
measurement period. It provides a reference for energy conservation policies.The power
consumption of the eNodeB can be classified into DC power consumption and AC power
consumption, and you can run the SET ECMP command to set the power consumption type.
The PMU monitors the DC power consumption by default. The dependence of this counter on
the PMU is as follows:
For the PMU01B, this counter is reported only when the software version of the PMU is 138 or
later.
For the PMU10A or PMU11A, this counter is reported regardless of the software version of the
PMU.

For other types of PMUs, this counter is not reported.
You can run the DSP PMU command to query the type and software version of a PMU.
If a BS contains multiple PMUs and one or more PMUs do not support reporting this counter,
the measurement results of this counter are inaccurate.
Counter 1526728210 VS.EnergyCons.BTS.Measuring will be replaced by counter 1593835638

VS.EnergyCons.BTS.Measuring.LTE in later versions. In the current version, counters
1526728210 VS.EnergyCons.BTS.Measuring and 1593835638
VS.EnergyCons.BTS.Measuring.LTE are both valid, and the value of counter 1526728210
VS.EnergyCons.BTS.Measuring is properly reported. Counter 1526728210
VS.EnergyCons.BTS.Measuring will be deleted in later versions. Using counter 1526728210
VS.EnergyCons.BTS.Measuring is not recommended.
Measurement Points
The power consumption monitored by all the PMUs is sampled every 5 minutes. At the end of
Formula
None
Unit
kWh
Related Features
VS.EnergyCons.BTS.Meas- Multi-mode: None

uring GSM: None
UMTS: None
Power Consumption
Monitoring
1.23.1.3 PSU shutdown total time

Counters
Description
1526728215 VS.PSU.Shutdown- PSU shutdown total DBS3900 LTE/

Time time BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE
Description
This counter measures the shutdown duration of all power supplying units (PSUs) in the NodeB
Counter 1526728215 VS.PSU.ShutdownTime will be replaced by counter 1593835620

VS.PSU.ShutdownTime in later versions. In the current version, counters 1526728215
VS.PSU.ShutdownTime and 1593835620 VS.PSU.ShutdownTime are both valid, and the value
of counter VS.ShutdownTime.PSU is properly reported . Counter 1526728215
VS.PSU.ShutdownTime will be deleted in later versions. Using counter 1526728215
VS.PSU.ShutdownTime is not recommended.
Measurement Points
The duration of PSU intelligent shutdown is sampled per minute. At the end of a measurement
A deviation of one sampling period may be caused in the sampling timer when the timer performs
time synchronization. As a result, a deviation of one sampling period will also be generated in
the value of this counter, which affects the values of the KPIs that are calculated by using this
counter. The effects vary depending on the deviation in the value of this counter and calculation
formulas for the KPIs.
Formula
None
Unit
s

Related Features
VS.PSU.ShutdownTime Multi-mode: None

GSM: None
UMTS: None
Power Consumption
Monitoring
1.23.2 Measurement related to BBU (Measurement related to BBU)
Overview
The BBU.Device function subset measures the performance of the BBU, such as power
consumption.
Counters
Description
1526727551 VS.EnergyCons.BB The counter version earlier than

U measures the total V100R008C00,and
power consumption the mapping single-
of the BBU within a mode base station
measurement period. version that
It provides data basis introduce this
for energy counter is:
conservation eNodeB:Version
policies. earlier than
V100R003C00
None
1.23.2.1 BBU Power Consumption

Counters
Description
1526727551 VS.EnergyCons.BB The counter DBS3900 LTE/

U measures the total BTS3900 LTE/
power consumption BTS3900A LTE/
of the BBU within a BTS3900L LTE/
measurement period. BTS3900AL LTE
It provides data basis
for energy
conservation
policies.
Description
The counter measures the total power consumption of the BBU within a measurement period.
It provides data basis for energy conservation policies.
The counter 1526727551 VS.EnergyCons.BBU can report in current version and will be
removed in later version. Counter 1526727551 VS.EnergyCons.BBU is not recommended for
use.
Measurement Points
The BBU power consumption is sampled every 5 minutes based on the power of all configured
and detected boards in the BBU subrack. At the end of a measurement period, the sum of these
sampling results is used as the value of the counter.
Formula
None
Unit
kWh
Related Features
VS.EnergyCons.BBU Multi-mode: None

GSM: None
UMTS: None
Power Consumption
Monitoring

1.24 Measurement of PMU performance (PMU)

Overview
The object type PMU Measurement contains the PMU-related function subset. It represents the
operating status of each PMU.
FunctionSubSets
Measurement related to PMU PMU Measurement (PMU.Device)
1.24.1 Measurement related to PMU (Measurement related to PMU)
Overview
The PMU.Device function subset measures the performance of the Power Monitoring Unit
(PMU), such as its power consumption.
Counters
Description
1526727549 VS.EnergyCons.P PMU Power version earlier than

MU Consumption V100R008C00,and
the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
None
1.24.1.1 PMU Power Consumption

Counters
Description
1526727549 VS.EnergyCons.PM PMU Power DBS3900 LTE/

U Consumption BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE
Description
The counter measures the total DC power consumption monitored by a power monitoring unit
(PMU) within a measurement period. It provides data basis for energy conservation policies.
The counter 1526727549 VS.EnergyCons.PMU can report in current version and will be
removed in later version. Counter 1526727549 VS.EnergyCons.PMU is not recommended for
use.
Measurement Points
The power consumption of each PMU is sampled every 30 seconds. At the end of a measurement
Formula
None
Unit
kWh
Related Features
VS.EnergyCons.PMU Multi-mode: None

GSM: None
UMTS: None
Power Consumption
Monitoring

1.25 NODE (NODE)

Overview
The object type NODE contains node-related function subset.
FunctionSubSets
Equipment.Node Node Equipment Performance Measurement
1.25.1 Node Equipment Performance Measurement

(Equipment.Node)
Overview
The Node Equipment Performance Measurement function subset measures the node equipment
performance measurement.
Counters
Description
1593835620 VS.PSU.Shutdown- PSU shutdown total V100R008C00,and

Time time the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1593835637 VS.EnergyCons.BT The sum of power V100R008C00,and

S.Adding.LTE consumption of all the mapping single-
boards in the LTE mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description
1593835638 VS.EnergyCons.BT Power consumption V100R008C00,and

S.Measuring.LTE measured by the the mapping single-
power system of the mode base station
LTE version that
introduce this
counter is:
eNodeB:V100R006
C00
None
1.25.1.1 PSU shutdown total time
Counters
Description
1593835620 VS.PSU.Shutdown- PSU shutdown total DBS3900 WCDMA/

Time time BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the shutdown duration of all power supplying units (PSUs) in the base
station within the measurement period.
Measurement Points
In a measurement period, the intelligent shutdown status of each PSU is sampled every second.
When one or more PSUs are intelligently shut down, this counter is added by one.

Formula
None
Unit
s
Related Features
VS.PSU.ShutdownTime Multi-mode: None

GSM: GBFD-111608 PSU Intelligent Shutdown
UMTS: WRFD-020121 Intelligent Power
LTE: LOFD-001056 Management
TDLOFD-001056 PSU Intelligent Sleep Mode

PSU Intelligent Sleep Mode
1.25.1.2 The sum of power consumption of all boards in the LTE
Counters
Description
1593835637 VS.EnergyCons.BT The sum of power DBS3900 LTE/

S.Adding.LTE consumption of all BTS3900 LTE/
boards in the LTE BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the power consumption of the LTE within a measurement period, which
equals the sum of the power consumption of boards and RF modules working in LTE mode. In
a LTE only base station, the value of this counter equals the base station power consumption.
In a multimode base station, the value of this counter is a part of the base station power
consumption.
Measurement Points
The system samples the power consumption of boards and RF modules working in LTE mode
every 5 minutes. At the end of a measurement period, the sum of these estimated sampling results
is used as the value of this counter.

Formula
None
Unit
kWh
Related Features
VS.EnergyCons.BTS.Addin Multi-mode: None

g.LTE GSM: None
UMTS: None
Power Consumption
Monitoring
1.25.1.3 Power consumption measured by the power system of the LTE
Counters
Description
1593835638 VS.EnergyCons.BT Power consumption DBS3900 LTE/

S.Measuring.LTE measured by the BTS3900 LTE/
power system of the BTS3900A LTE/
LTE BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the power consumption of the LTE within a measurement period. In a
LTE only base station, the value of this counter equals the base station power consumption. In
a multimode base station, the value of this counter is a part of the base station power consumption.
Measurement Points
The system samples the power consumption measured by the power system every 5 minutes. At
the end of a measurement period, the sum of these sampling results divided by the number of
modes where the PMU is configured equals to the LTE power consumption and is used as the

Formula
None
Unit
kWh
Related Features
VS.EnergyCons.BTS.Measu Multi-mode: None

ring.LTE GSM: None
UMTS: None
Power Consumption
Monitoring
1.26 BBUBoard (BBUBoard)

Overview
The object type BBU Board contains function subset related to the BBU board.
FunctionSubSets
Load.BBUBoard BBU Board Load Performance Measurement
1.26.1 BBU Board Load Performance Measurement

(Load.BBUBoard)
Overview
The BBU Board Load Performance Measurement function subset measures the load on a BBU
board.

Counters
Description
1593835630 VS.BBUBoard.CP The number of times V100R008C00,and

ULoad.Cumulati- of CPU Use Rate the mapping single-
veHighloadCount Overload mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1593835632 VS.BBUBoard.CP Maximum Board V100R008C00,and

ULoad.Max CPU Usage the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
1593835633 VS.BBUBoard.CP Average Board CPU V100R008C00,and

ULoad.Mean Usage the mapping single-
mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00


Description
1593835634 VS.BBUBoard.CP Board CPU Usage V100R008C00,and

ULoad.Over Exceeding the the mapping single-
Threshold (%) mode base station
versions that
introduce this
counter are:
eGBTS:V100R015C
00
NodeB:V200R015C
00
eNodeB:V100R006
C00
None
1.26.1.1 The number of times of CPU Use Rate Overload
Counters
Description
1593835630 VS.BBUBoard.CPU The number of times DBS3900 WCDMA/

Load.Cumulative- of CPU Use Rate BTS3900 WCDMA/
HighloadCount Overload BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter provides the number of times of CPU use rate overload.

Measurement Points
sampling results is used as the average CPU usage of this sampling interval. At the end of a
measurement period, the number of times that the average CPU usage exceeds the preconfigured
threshold is used as the value of the counter. The preconfigured threshold is 85%. For example,
if the number of times that the average CPU usage exceeds the preconfigured threshold in the
measurement period is X1, X2, X3, ..., and Xn, the value of the
VS.BBUBoard.CPULoad.CumulativeHighloadCount counter is the sum of X1, X2, X3, ..., and
Xn.
Formula
None
Unit
None
Related Features
VS.BBUBoard.CPULoad.C Multi-mode: MRFD-210302 Performance Management

umulativeHighloadCount GSM: GBFD-111202 O&M of BTS
UMTS: None
LTE: None
1.26.1.2 Maximum and Average Board CPU Usage

Counters
Description
1593835632 VS.BBUBoard.CPU Maximum Board DBS3900 WCDMA/

Load.Max CPU Usage BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1593835633 VS.BBUBoard.CPU Average Board CPU DBS3900 WCDMA/

Load.Mean Usage BTS3900 WCDMA/
BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter provides the maximum and average CPU usage of a board in a specified
measurement period.
Measurement Points
sampling results is used as the average CPU usage of this sampling interval. The maximum or
the average of the final sampling results is used as the value of this counter. Each sampling result
is based on the maximum usage among multiple CPUs in the board. For example, if the number
of times that the average CPU usage exceeds the preconfigured threshold in the measurement
period is X1, X2, X3, ..., and Xn, the value of the VS.BBUBoard.CPUload.Max and
VS.BBUBoard.CPUload.Mean counters are calculated using the following formulae:

VS.BBUBoard.CPUload.Max = MAX(Xi), VS.BBUBoard.CPUload.Mean =(X1+X2+...+Xn)/

n.
Formula
None
Unit
%
Related Features
VS.BBUBoard.CPULoad.M Multi-mode: MRFD-210302 Performance Management

ax GSM: GBFD-111202 O&M of BTS
UMTS: None
LTE: None
VS.BBUBoard.CPULoad.M Multi-mode: MRFD-210302 Performance Management

ean GSM: GBFD-111202 O&M of BTS
UMTS: None
LTE: None
1.26.1.3 Percentage of Cpu Use Rate Overload
Counters
Description
1593835634 VS.BBUBoard.CPU Board CPU Usage DBS3900 WCDMA/

Load.Over Exceeding the BTS3900 WCDMA/
Threshold (%) BTS3900A
WCDMA/
BTS3900L
WCDMA/
BTS3900AL
WCDMA,
DBS3900 LTE/
BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
This counter provides the percentage of the period during which the CPU usage of a board
exceeds the threshold to the entire measurement period.
Measurement Points
In the measurement period of 5s, the CPU usage is sampled many times, and the average of these
sampling results is used as the final sampling result of this measurement period. The percentage
of the period during which the CPU usage of a board exceeds the threshold to the entire
measurement period is used as the value of this counter. Each sampling result is based on the
maximum usage among multiple CPUs in the board.
Formula
None
Unit
%
Related Features
VS.BBUBoard.CPULoad.O Multi-mode: MRFD-210302 Performance Management

ver GSM: GBFD-111202 O&M of BTS
UMTS: None
LTE: None
1.27 GNSS (GNSS)

Overview
The object type GNSS contains function subset related to the GNSS.
FunctionSubSets
SatellitesTraced.GNSS Traced GNSS Satellites Performance

1.27.1 Traced GNSS Satellites Performance Measurement

(SatellitesTraced.GNSS)
Overview
This counter provides the number of GNSS satellites that can be traced. It helps users identify
GNSS cards that can trace few satellites.
Counters
Description
1593835641 VS.GNSS.Satelli- Number of times no V100R008C00,and

tesTraced.0 GNSS satellites are the mapping single-
traced mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1593835642 VS.GNSS.Satelli- Number of times one V100R008C00,and

tesTraced.1 to three GNSS the mapping single-
satellites are traced mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1593835643 VS.GNSS.Satelli- Number of times four V100R008C00,and

version that
introduce this
counter is:
eNodeB:V100R006
C00
1593835644 VS.GNSS.Satelli- Number of times five V100R008C00,and

version that
introduce this
counter is:
eNodeB:V100R006
C00


Description
1593835645 VS.GNSS.Satelli- Number of times V100R008C00,and

tesTraced.4 more than five GNSS the mapping single-
satellites are traced mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1593835646 VS.GNSS.Satellites Average number of V100R008C00,and

Traced.Mean traced GNSS the mapping single-
satellites mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
None
1.27.1.1 Number of times that the number of traced GNSS satellites falls in level 0
Counters
Description
1593835641 VS.GNSS.Satellites- Number of times no DBS3900 LTE/

Traced.0 GNSS satellites are BTS3900 LTE/
traced BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of times no satellites are traced by this satellite card.
Measurement Points
The number of times that no satellites are traced by the satellite card is sampled every 3s. At the
end of a measurement period, the sum of these sampling results is used as the value of this
counter.

Formula
None
Unit
None
Related Features
VS.GNSS.SatellitesTraced.0 Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-00300503 Synchronization with GPS
TDLBFD-00300503 Synchronization with GPS
Counters
Description
1593835642 VS.GNSS.Satellites- Number of times one DBS3900 LTE/

Traced.1 to three GNSS BTS3900 LTE/
satellites are traced BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of times one to three satellites are traced by this satellite card.
Measurement Points
The number of times that one to three satellites are traced by the satellite card is sampled every
3s. At the end of a measurement period, the sum of these sampling results is used as the value
of this counter.
Formula
None

Unit
None
Related Features

GSM: None
UMTS: None
Counters
Description
1593835643 VS.GNSS.Satellites- Number of times four DBS3900 LTE/

BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of times four satellites are traced by this satellite card.
Measurement Points
The number of times that four satellites are traced by the satellite card is sampled every 3s. At
the end of a measurement period, the sum of these sampling results is used as the value of this
counter.
Formula
None
Unit
None

Related Features

GSM: None
UMTS: None
Counters
Description
1593835644 VS.GNSS.Satellites- Number of times five DBS3900 LTE/

BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of times five satellites are traced by this satellite card.
Measurement Points
The number of times that five satellites are traced by the satellite card is sampled every 3s. At
the end of a measurement period, the sum of these sampling results is used as the value of this
counter.
Formula
None
Unit
None

Related Features

GSM: None
UMTS: None
Counters
Description
1593835645 VS.GNSS.Satellites- Number of times DBS3900 LTE/

Traced.4 more than five GNSS BTS3900 LTE/
satellites are traced BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of times more than five satellites are traced by this satellite
card.
Measurement Points
The number of times that more than five satellites are traced by the satellite card is sampled
every 3s. At the end of a measurement period, the sum of these sampling results is used as the
value of this counter.
Formula
None
Unit
None

Related Features

GSM: None
UMTS: None
1.27.1.6 Average number of traced GNSS satellites
Counters
Description
1593835646 VS.GNSS.Satellites Average number of DBS3900 LTE/

Traced.Mean traced GNSS BTS3900 LTE/
satellites BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the average number of satellites traced by this satellite card.
Measurement Points
The number of satellites traced by the satellite card is sampled every 3s. At the end of a
measurement period, the average of these sampling results is used as the value of this counter.
Formula
None
Unit
None

Related Features
VS.GNSS.SatellitesTraced. Multi-mode: None

Mean GSM: None
UMTS: None

Performance Counter Reference 2 Radio Network Related Measurement
2 Radio Network Related Measurement
About This Chapter
2.2 Measurement of Cell performance (Cell)
2.3 Measurement of S1-LINK performance between eNodeB and MME (Sig.S1)
2.4 Measurement of X2-LINK performance between eNodeB and neighbor eNodeB (Sig.X2)
2.5 Measurement between two neighbor cell (NCell)
2.6 Measurement of Operator (Cell.Operator)


Overview
The object type eNodeB Measurement contains the eNodeB-related function subsets. It
represents the operating status of the eNodeB.
FunctionSubSets
eNodeB.Device eNodeB Measurement (eNodeB.Device)
Measurement related to BBU BBU Measurement (BBU.Device)
LCS.ENODEB eNodeB LCS Measurement (LCS.ENODEB)
Traffic.User.eNodeB User Number Measurement (eNodeB)

RIM.eNodeB eNodeB RIM Measurement

(RIM.ENODEB)
Traffic.Thruput.eNodeB eNodeB Throughput Measurement

SCTP.eNodeB eNodeB SCTP Measurement

(SCTP.eNodeB)
2.1.1 Measurement related to LCS in eNodeB (LCS.ENODEB)
Overview
Location Service (LCS) provides a means to determine the geographic position and velocity of
a UE based on measuring radio signals. The eNodeB supports the E-CID and OTDOA
positioning techniques. The LCS.ENODEB function subset measures the number of OTDOA
measurement attempts and successful OTDOA measurement requests in an eNodeB.

Counters
Description
1526728156 L.LCS.OtdoaMeas. Number of OTDOA V100R008C00,and

Req measurement the mapping single-
attempts received by mode base station
an eNodeB version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728157 L.LCS.OtdoaMeas. Number of V100R008C00,and

Succ successful responses the mapping single-
sent by an eNodeB to mode base station
OTDOA version that
measurement introduce this
requests counter is:
eNodeB:V100R003
C00
None
2.1.1.1 Number of OTDOA Measurement Attempts Received by an eNodeB
Counters
Description
1526728156 L.LCS.OtdoaMeas. Number of OTDOA DBS3900 LTE/

Req measurement BTS3900 LTE/
attempts received by BTS3900A LTE/
an eNodeB BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of LCS OTDOA Information Request messages received by
the eNodeB. The LCS OTDOA Information Request message is an LPPa signaling message sent
from the E-SMLC to an eNodeB. The messaged is used to request the OTDOA assistance data
for positioning a target UE of the eNodeB.

Measurement Points
The L.LCS.OtdoaMeas.Req counter is incremented by 1 each time the eNodeB receives an LCS
OTDOA Information Request message.
Formula
None
Unit
None
Related Features
L.LCS.OtdoaMeas.Req Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001047 LoCation Services (LCS)
TDLOFD-001047 LoCation Services(LCS)
2.1.1.2 Number of Successful Responses Sent by an eNodeB to OTDOA

Measurement Requests
Counters
Description
1526728157 L.LCS.OtdoaMeas.S Number of DBS3900 LTE/

ucc successful responses BTS3900 LTE/
sent by an eNodeB to BTS3900A LTE/
OTDOA BTS3900L LTE/
measurement BTS3900AL LTE,
requests BTS3900
Description
This counter measures the number of LCS OTDOA Information Response messages sent by the
eNodeB. The LCS OTDOA Information Response message is an LPPa signaling message sent
from an eNodeB to the E-SMLC. The messaged is used to report the OTDOA-related
configuration data of the associated cell controlled by the eNodeB.

Measurement Points
The L.LCS.OtdoaMeas.Succ counter is incremented by 1 each time the eNodeB sends an LCS
OTDOA Information Response message.
Formula
None
Unit
None
Related Features
L.LCS.OtdoaMeas.Succ Multi-mode: None

GSM: None
UMTS: None
2.1.2 Measurement related to user traffic in eNodeB

Overview
The Traffic.User.eNodeB function subset measures the number of users under an eNodeB within
Counters
Description
1526728334 L.Traffic.eNodeB. Maximum Number V100R008C00,and

User.Max of Users Under an the mapping single-
eNodeB mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00

None
2.1.2.1 Maximum Number of Users Under an eNodeB
Counters
Description
1526728334 L.Traffic.eNodeB.U Maximum Number DBS3900 LTE/

ser.Max of Users Under an BTS3900 LTE/
eNodeB BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the maximum number of licenses that the eNodeB has allocated to all
UEs, including UEs experiencing admission successes, admission failures, incoming-handover
successes, and incoming handover failures. This counter helps operators to determine whether
user licenses need capacity expansion.
Measurement Points
The number of UEs in connected mode under an eNodeB is sampled per second. At the end of
a measurement period, the maximum of these sampling results is used as the value of the counter.
Formula
None
Unit
None

Related Features
L.Traffic.eNodeB.User.Max Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002007 RRC Connection
TDLBFD-002007 Management
RRC Connection
Management
2.1.3 Measurement related to RIM in eNodeB (RIM.eNodeB)
Overview
The RIM.eNodeB function subset measures the performance of the requests and transfers of
RAN information between eNodeB and other RAN nodes via the core network.
Counters
Description
1526728946 L.RIM.SI.E2W.Re Number of system V100R008C00,and

q information requests the mapping single-
from eNodeB to mode base station
WCDMA network version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728947 L.RIM.SI.E2W.Res Number of system V100R008C00,and

p information the mapping single-
responses from mode base station
WCDMA network to version that
eNodeB introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728948 L.RIM.SI.E2W.Up Number of system V100R008C00,and

date information updates the mapping single-
from eNodeB to mode base station
introduce this
counter is:
eNodeB:V100R006
C00
1526728949 L.RIM.Load.E2W. Number of load V100R008C00,and

Req requests from the mapping single-
eNodeB to WCDMA mode base station
network version that
introduce this
counter is:
eNodeB:V100R006
C00

Resp responses from the mapping single-
WCDMA network to mode base station
eNodeB version that
introduce this
counter is:
eNodeB:V100R006
C00

Update updates from the mapping single-
eNodeB to WCDMA mode base station
introduce this
counter is:
eNodeB:V100R006
C00
None
2.1.3.1 Number of System Information Requests from eNodeB to WCDMA

Network

Counters
Description
1526728946 L.RIM.SI.E2W.Req Number of system DBS3900 LTE/

information requests BTS3900 LTE/
from eNodeB to BTS3900A LTE/
WCDMA network BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of system information requests from eNodeB to WCDMA
network.
Measurement Points
As shown at point A in Figure 2-1, the L.RIM.SI.E2W.Req counter is incremented by 1 each
time the eNodeB sends an eNB DIRECT INFORMATION TRANSFER message to WCDMA
to request the system information.
Figure 2-1
Formula
None
Unit
None

Related Features
L.RIM.SI.E2W.Req Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001052 Flash CS Fallback to
TDLOFD-001052 UTRAN
Flash CS Fallback to
UTRAN
2.1.3.2 Number of system information responses from WCDMA network to

eNodeB
Counters
Description
1526728947 L.RIM.SI.E2W.Res Number of system DBS3900 LTE/

p information BTS3900 LTE/
responses from BTS3900A LTE/
WCDMA network to BTS3900L LTE/
eNodeB BTS3900AL LTE,
BTS3900
Description
The counter measures the number of system information responses from WCDMA network to
eNodeB.
Measurement Points
As shown at point B in Figure 2-2, the L.RIM.SI.E2W.Resp counter is incremented by 1 each
time the eNodeB receives an MME DIRECT INFORMATION TRANSFER message
transferring RAN INFORMATION RESPONSE for system information from WCDMA.

Figure 2-2
Formula
None
Unit
None
Related Features
L.RIM.SI.E2W.Resp Multi-mode: None

GSM: None
UMTS: None
TDLOFD-001052 UTRAN
UTRAN
2.1.3.3 Number of System Information Updates from eNodeB to WCDMA Network

Counters
Description
1526728948 L.RIM.SI.E2W.Up- Number of system DBS3900 LTE/

date information updates BTS3900 LTE/
from eNodeB to BTS3900A LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of system information updates from eNodeB to WCDMA
network.
Measurement Points
As shown at point A in Figure 2-3, the L.RIM.SI.E2W.Update counter is incremented by 1 each
time the eNodeB receives an MME DIRECT INFORMATION TRANSFER message
transferring RAN INFORMATION UPDATE for system information from WCDMA.
Figure 2-3
Formula
None
Unit
None

Related Features
L.RIM.SI.E2W.Update Multi-mode: None

GSM: None
UMTS: None
TDLOFD-001052 UTRAN
UTRAN
2.1.3.4 Number of Load Requests from eNodeB to WCDMA Network
Counters
Description
1526728949 L.RIM.Load.E2W.R Number of load DBS3900 LTE/

eq requests from BTS3900 LTE/
eNodeB to WCDMA BTS3900A LTE/
network BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of load requests from eNodeB to WCDMA network.
Measurement Points
As shown at point A in Figure 2-4, the L.RIM.Load.E2W.Req counter is incremented by 1 each
time the eNodeB sends an eNB DIRECT INFORMATION TRANSFER message transferring
RAN INFORMATION REQUEST to WCDMA for load information request.
Figure 2-4

Formula
None
Unit
None
Related Features
L.RIM.Load.E2W.Req Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001044 Inter-RAT Load Sharing to
TDLOFD-001044 UTRAN
Inter-RAT Load Sharing to
UTRAN
2.1.3.5 Number of Load Responses from WCDMA Network to eNodeB
Counters
Description
1526728950 L.RIM.Load.E2W.R Number of load DBS3900 LTE/

esp responses from BTS3900 LTE/
WCDMA network to BTS3900A LTE/
eNodeB BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of load responses from WCDMA network to eNodeB.
Measurement Points
As shown at point B in Figure 2-5, the L.RIM.Load.E2W.Resp counter is incremented by 1
each time the eNodeB receives an MME DIRECT INFORMATION TRANSFER message
transferring RAN INFORMATION UPDATE for load information from WCDMA.

Figure 2-5
Formula
None
Unit
None
Related Features
L.RIM.Load.E2W.Resp Multi-mode: None

GSM: None
UMTS: None
TDLOFD-001044 UTRAN
UTRAN
2.1.3.6 Number of Load Updates from eNodeB to WCDMA Network

Counters
Description
1526728951 L.RIM.Load.E2W.U Number of load DBS3900 LTE/

pdate updates from BTS3900 LTE/
eNodeB to WCDMA BTS3900A LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of load updates from eNodeB to WCDMA network.
Measurement Points
As shown at point A in Figure 2-6, the L.RIM.Load.E2W.Update counter is incremented by 1
each time the eNodeB receives an MME DIRECT INFORMATION TRANSFER message
transferring RAN INFORMATION UPDATE for load information from WCDMA.
Figure 2-6
Formula
None
Unit
None

Related Features
L.RIM.Load.E2W.Update Multi-mode: None

GSM: None
UMTS: None
TDLOFD-001044 UTRAN
UTRAN
2.1.4 Measurement related to eNodeB Thruput

Overview
The Traffic.Thruput.eNodeB function subset measures the uplink or downlink throughput in an
eNodeB.
Counters
Description
1526729256 L.Thrp.eNodeB.bit Maximum downlink V100R008C00,and

s.DL.Max traffic volume for the mapping single-
PDCP SDUs in an mode base station
eNodeB version that
introduce this
counter is:
eNodeB:V100R006
C00
1526729257 L.Thrp.eNodeB.bit Maximum uplink V100R008C00,and

s.UL.Max traffic volume for the mapping single-
PDCP SDUs in an mode base station
eNodeB version that
introduce this
counter is:
eNodeB:V100R006
C00


Description
1526729258 L.Thrp.eNodeB.bit Maximum sum of the V100R008C00,and

s.Max uplink and downlink the mapping single-
traffic volume for mode base station
PDCP SDUs in an version that
counter is:
eNodeB:V100R006
C00
None
2.1.4.1 Maximum Traffic Volume for PDCP SDUs in an eNodeB
Counters
Description
1526729256 L.Thrp.eNodeB.bits. Maximum downlink DBS3900 LTE/

DL.Max traffic volume for BTS3900 LTE/
PDCP SDUs in an BTS3900A LTE/
BTS3900AL LTE,
BTS3900
1526729257 L.Thrp.eNodeB.bits. Maximum uplink DBS3900 LTE/

UL.Max traffic volume for BTS3900 LTE/
PDCP SDUs in an BTS3900A LTE/
BTS3900AL LTE,
BTS3900
1526729258 L.Thrp.eNodeB.bits. Maximum sum of the DBS3900 LTE/

Max uplink and downlink BTS3900 LTE/
traffic volume for BTS3900A LTE/
PDCP SDUs in an BTS3900L LTE/
BTS3900
Description
The counters measure the maximum of uplink, downlink, and the sum of uplink and downlink
traffic volumes for PDCP SDUs in an eNodeB.

Measurement Points
The sizes of the payloads in the uplink, downlink, and the sum of uplink and downlink PDCP
SDUs are sampled per second in an eNodeB. At the end of a measurement period, the maximum
of these sampling results per type is used as the value of the corresponding counter.
Formula
None
Unit
bit
Related Features
L.Thrp.eNodeB.bits.DL.Ma Multi-mode: None

x GSM: None
UMTS: None
LTE: LBFD-002008 Radio Bearer Management
TDLBFD-002008 Radio Bearer Management
LBFD-002025 Basic Scheduling
TDLBFD-002025 Basic Scheduling
L.Thrp.eNodeB.bits.UL.Ma Multi-mode: None

x GSM: None
UMTS: None
L.Thrp.eNodeB.bits.Max Multi-mode: None

GSM: None
UMTS: None

2.1.5 eNodeB SCTP Measurement (SCTP.eNodeB)
Overview
The SCTP.eNodeB measurement unit measures the traffic over the SCTP link.
Counters
Description
1526729664 L.DLSctpCong.Nu Number of times of V100R008C00,and

m downlink SCTP the mapping single-
congestion control mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
None
2.1.5.1 Number of Times of Downlink SCTP Congestion Control
Counters
Description
1526729664 L.DLSctpCong.Num Number of times of DBS3900 LTE/

downlink SCTP BTS3900 LTE/
congestion control BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of times that the eNodeB triggers downlink SCTP congestion
control.

L.DLSctpCong.Num The counter measures the number of times

that the eNodeB triggers downlink SCTP
congestion control.
Measurement Points
The counter is incremented by 1 each time the eNodeB triggers downlink SCTP congestion
control when the CPU usage reaches 85% and the downlink SCTP message rate reaches 4550
pkts/s because a plenty of packets are sent from the EPC.
Formula
None
Unit
None
Related Features
L.DLSctpCong.Num Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002033 SCTP Congestion Control
2.2 Measurement of Cell performance (Cell)

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
RRC.Setup.Cell RRC Connection Setup Measurement (Cell)

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

(Cell) (RRC.SetupFail.Cell)

RRC.ReEst.Cell RRC Connection Reestablishment

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

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

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

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

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

RAB.Modify.Cell)
Algo.Cell Cell Algo Measurement (Algo.Cell)
Traffic.DRB.Cell DRB Measurement (Cell)

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

(Traffic.Thruput.Cell)
Traffic.PDCP.Cell PDCP Measurement (Cell)

(Traffic.PDCP.Cell)
Paging.Cell Paging Measurement (Cell) (Paging.Cell)
SecurMode.Cell SecurMode Measurement (Cell)

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

(ChMeas.Pwr.Cell)
ChMeas.MIMO.Cell MIMO Measurement (Cell)

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

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

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

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

(Traffic.User.Cell)

HO.IRAT.Out.Cell Inter-RAT Outgoing Handover Measurement

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

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

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

(HO.eRAN.In.Cell)
HO.eRAN.X2Out.Cell Measurement of Outgoing Handovers over

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

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

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

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

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

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

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

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

(Cell) (UECNTX.EstFail.Cell)

HO.eRAN.X2In.Cell Measurement of Incoming Handovers over

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

(Traffic.Thruput.PDF.Cell)
2.2.1 Measurement related to RRC setup (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 2-7 shows the measurement points in an RRC
connection setup procedure.
Figure 2-7

Counters
Description
1526726657 L.RRC.ConnReq. Number of RRC V100R008C00,and

Msg Connection Request the mapping single-
messages received mode base station
from UEs in a cell, version that
including the number introduce this
of retransmitted counter is:
messages eNodeB:Version
earlier than
V100R003C00
1526726658 L.RRC.ConnReq.A Number of RRC V100R008C00,and

tt Connection Request the mapping single-
messages received mode base station
from UEs in a cell, version that
excluding the introduce this
number of counter is:
retransmitted eNodeB:Version
messages earlier than
V100R003C00
1526726659 L.RRC.ConnReq.S Number of RRC V100R008C00,and

ucc Connection Setup the mapping single-
Complete messages mode base station
received from UEs in version that
a cell introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727025 Service RRC Success rate of RRC V100R008C00,and

Connect Success connection setups for the mapping single-
Rate services mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526728216 L.RRC.ConnSetup Number of RRC V100R008C00,and

Connection Setup the mapping single-
messages sent to UEs mode base station
in a cell version that
introduce this
counter is:
eNodeB:V100R003
C00

tt.Emc Connection Request the mapping single-
messages with a mode base station
cause value of version that
emergency received introduce this
from UEs in a cell counter is:
eNodeB:V100R003
C00

tt.HighPri Connection Request the mapping single-
highPriorityAccess introduce this
received from UEs in counter is:
a cell eNodeB:V100R003
C00

tt.Mt Connection Request the mapping single-
cause value of mt- version that
Access received introduce this
eNodeB:V100R003
C00

tt.MoSig Connection Request the mapping single-
cause value of mo- version that
Signalling received introduce this
eNodeB:V100R003
C00


Description

tt.MoData Connection Request the mapping single-
cause value of mo- version that
Data received from introduce this
UEs in a cell counter is:
eNodeB:V100R003
C00

ucc.Emc Connection Setup the mapping single-
with a cause value of version that
emergency received introduce this
eNodeB:V100R003
C00

ucc.HighPri Connection Setup the mapping single-
highPriorityAccess introduce this
C00

ucc.Mt Connection Setup the mapping single-
mt-Access received introduce this
eNodeB:V100R003
C00

ucc.MoSig Connection Setup the mapping single-
mo-signalling introduce this
C00


Description

ucc.MoData Connection Setup the mapping single-
mo-Data received introduce this
eNodeB:V100R003
C00

tt.DelayTol Connection Request the mapping single-
delayTolerantAc- introduce this
cess-v1020 received counter is:
from UEs in a cell eNodeB:V100R005
C01

ucc.DelayTol Connection Setup the mapping single-
delayTolerantAc- introduce this
cess-v1020 received counter is:
from UEs in a cell eNodeB:V100R005
C01
1526728438 L.RRC.StateTrans. Number of times a V100R008C00,and

Syn2Unsyn UE transits from the the mapping single-
Uplink- mode base station
Synchronized state to version that
the uplink out-of- introduce this
synchronization state counter is:
eNodeB:V100R006
C00
1526728439 L.RRC.StateTrans. Number of times a V100R008C00,and

Unsyn2Syn UE transits from the the mapping single-
out-of- mode base station
synchronization state version that
to the uplink- introduce this
synchronized state counter is:
eNodeB:V100R006
C00


Description
1526728774 L.RRC.ConnSetup. Average RRC V100R008C00,and

TimeAvg connection setup the mapping single-
duration mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728775 L.RRC.ConnSetup. Maximum RRC V100R008C00,and

TimeMax connection setup the mapping single-
duration mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
Counter Sub Counter
L.RRC.ConnReq.Att L.RRC.ConnReq.Att.Emc
L.RRC.ConnReq.Att.HighPri
L.RRC.ConnReq.Att.Mt
L.RRC.ConnReq.Att.MoSig
L.RRC.ConnReq.Att.MoData
L.RRC.ConnReq.Att.DelayTol
L.RRC.ConnReq.Succ L.RRC.ConnReq.Succ.Emc
L.RRC.ConnReq.Succ.HighPri
L.RRC.ConnReq.Succ.Mt
L.RRC.ConnReq.Succ.MoSig
L.RRC.ConnReq.Succ.MoData
L.RRC.ConnReq.Succ.DelayTol
2.2.1.1 Number of RRC Connection Setup Requests in a Cell

Counters
Description
1526726657 L.RRC.ConnReq.Ms Number of RRC DBS3900 LTE/

g Connection Request BTS3900 LTE/
messages received BTS3900A LTE/
from UEs in a cell, BTS3900L LTE/
including the number BTS3900AL LTE,
of retransmitted BTS3900
messages
1526726658 L.RRC.ConnReq.Att Number of RRC DBS3900 LTE/

Connection Request BTS3900 LTE/
messages received BTS3900A LTE/
from UEs in a cell, BTS3900L LTE/
excluding the BTS3900AL LTE,
number of BTS3900
retransmitted
messages

.Emc Connection Request BTS3900 LTE/
messages with a BTS3900A LTE/
cause value of BTS3900L LTE/
emergency received BTS3900AL LTE,
from UEs in a cell BTS3900

.HighPri Connection Request BTS3900 LTE/
highPriorityAccess BTS3900AL LTE,
received from UEs in BTS3900
a cell

.Mt Connection Request BTS3900 LTE/
cause value of mt- BTS3900L LTE/
Access received BTS3900AL LTE,

.MoSig Connection Request BTS3900 LTE/
cause value of mo- BTS3900L LTE/
Signalling received BTS3900AL LTE,


Description

.MoData Connection Request BTS3900 LTE/
cause value of mo- BTS3900L LTE/
Data received from BTS3900AL LTE,
UEs in a cell BTS3900

.DelayTol Connection Request BTS3900 LTE/
delayTolerantAc- BTS3900AL LTE,
cess-v1020 received BTS3900
from UEs in a cell
Description
The counters measure the number of RRC connection setup requests for different causes in a
cell. The RRC Connection Request message is the first RRC signaling message sent from the
UE to the eNodeB. The message is used to request the setup of an RRC connection.
Measurement Points
As shown at point A in Figure 2-8, the corresponding counter is incremented by 1 each time
the eNodeB receives an RRC Connection Request message from a UE. The counters are
measured as follows:
The L.RRC.ConnReq.Msg is incremented by 1 each time the eNodeB receives an RRC

Connection Request message.
The L.RRC.ConnReq.Att is incremented by 1 only when the eNodeB receives a non-

retransmitted RRC Connection Request message.
The L.RRC.ConnReq.Att.Emc counter is incremented by 1 only when the eNodeB receives a

non-retransmitted RRC Connection Request message and the Establishment Cause information
element (IE) of the message is "emergency".
The L.RRC.ConnReq.Att.HighPri counter is incremented by 1 only when the eNodeB receives

a non-retransmitted RRC Connection Request message and the Establishment Cause IE of the
message is "highPriorityAccess".
The L.RRC.ConnReq.Att.Mt counter is incremented by 1 only when the eNodeB receives a non-
retransmitted RRC Connection Request message and the Establishment Cause IE of the message
is "mt-Access".
The L.RRC.ConnReq.Att.MoSig counter is incremented by 1 only when the eNodeB receives

message is "mo-Signalling".

The L.RRC.ConnReq.Att.MoData counter is incremented by 1 only when the eNodeB receives

message is "mo-Data".
The L.RRC.ConnReq.Att.DelayTol counter is incremented by 1 only when the eNodeB receives

message is "delayTolerantAccess-v1020".
Figure 2-8
Formula
None
Unit
None
Related Features
L.RRC.ConnReq.Msg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management

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

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

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

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

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

GSM: None
UMTS: None
RRC Connection
Management

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

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

Tol GSM: None
UMTS: None
RRC Connection
Management
2.2.1.2 Number of Successful RRC Connection Setups in a Cell
Counters
Description
1526726659 L.RRC.ConnReq.Su Number of RRC DBS3900 LTE/

cc Connection Setup BTS3900 LTE/
Complete messages BTS3900A LTE/
received from UEs in BTS3900L LTE/
a cell BTS3900AL LTE,
BTS3900

cc.Emc Connection Setup BTS3900 LTE/
with a cause value of BTS3900L LTE/
emergency received BTS3900AL LTE,

cc.HighPri Connection Setup BTS3900 LTE/
highPriorityAccess BTS3900AL LTE,
a cell


Description

cc.Mt Connection Setup BTS3900 LTE/
mt-Access received BTS3900AL LTE,

cc.MoSig Connection Setup BTS3900 LTE/
mo-signalling BTS3900AL LTE,
a cell

cc.MoData Connection Setup BTS3900 LTE/
mo-Data received BTS3900AL LTE,

cc.DelayTol Connection Setup BTS3900 LTE/
delayTolerantAc- BTS3900AL LTE,
cess-v1020 received BTS3900
from UEs in a cell
Description
The counters measure the number of successful RRC connection setups for different causes in
a cell. That is, the counters measure the number of RRC Connection Setup Complete messages
received by the eNodeB from a UE. The RRC Connection Setup Complete message is an RRC
signaling message sent from a UE to the eNodeB. The message is used to inform the eNodeB
that the RRC connection setup is completed and informs the eNodeB of the carried NAS
signaling information and the information about PLMN selection.
Measurement Points
As shown at point C in Figure 2-9, the corresponding counter is incremented by 1 each time the
eNodeB receives an RRC Connection Setup Complete message from a UE. The counters are
measured as follows:
The L.RRC.ConnReq.Succ counter is incremented by 1 each time the eNodeB receives the
message from a UE.

The L.RRC.ConnReq.Succ.Emc counter is incremented by 1 each time the eNodeB receives the
message from a UE and the Establishment Cause information element (IE) of the RRC
Connection Request message is "emergency call".
The L.RRC.ConnReq.Succ.HighPri counter is incremented by 1 each time the eNodeB receives
the message from a UE and the Establishment Cause IE of the RRC Connection Request message
is "highPriorityAccess".
The L.RRC.ConnReq.Succ.Mt counter is incremented by 1 each time the eNodeB receives the
message from a UE and the Establishment Cause IE of the RRC Connection Request message
is "mt-Access".
The L.RRC.ConnReq.Succ.MoSig counter is incremented by 1 each time the eNodeB receives
is "mo-Signalling".
The L.RRC.ConnReq.Succ.MoData counter is incremented by 1 each time the eNodeB receives
is "mo-Data".
The L.RRC.ConnReq.Succ.DelayTol counter is incremented by 1 each time the eNodeB
receives the message from a UE and the Establishment Cause IE of the RRC Connection Request
message is "delayTolerantAccess-v1020".
Figure 2-9
Formula
None
Unit
None

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

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

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

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

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

Sig GSM: None
UMTS: None
RRC Connection
Management

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

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

layTol GSM: None
UMTS: None
RRC Connection
Management
2.2.1.3 Success Rate of RRC Connection Setups for Services
Counters
Description
1526727025 Service RRC Success rate of RRC DBS3900 LTE/

Connect Success connection setups for BTS3900 LTE/
Rate services BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the success rate of RRC connection setups for services in a cell.
This counter will be deleted in later versions. It is reported normally in the current version but
the measurement value is invalid. You are advised not to use this counter.
Measurement Points
The success rate of RRC connection setups for services in a cell is calculated by using the
following formula based on the values of the counters L.RRC.ConnReq.Succ.Emc,
L.RRC.ConnReq.Succ.HighPri, L.RRC.ConnReq.Succ.Mt, and
L.RRC.ConnReq.Succ.MoData.

Formula
{100}*([L.RRC.ConnReq.Succ.Emc] + [L.RRC.ConnReq.Succ.HighPri] +
[L.RRC.ConnReq.Succ.Mt] + [L.RRC.ConnReq.Succ.MoData])/ ([L.RRC.ConnReq.Att.Emc]
+ [L.RRC.ConnReq.Att.HighPri] + [L.RRC.ConnReq.Att.Mt] +
[L.RRC.ConnReq.Att.MoData])
Unit
%
Related Features
Service RRC Connect Multi-mode: None

Success Rate GSM: None
UMTS: None
RRC Connection
Management
2.2.1.4 Number of RRC Connection Setup Attempts in a Cell
Counters
Description
1526728216 L.RRC.ConnSetup Number of RRC DBS3900 LTE/

Connection Setup BTS3900 LTE/
messages sent to UEs BTS3900A LTE/
in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of RRC connection setup attempts in a cell. That is, the counter
measures the number of times that the eNodeB sends an RRC Connection Setup message to the
UE after receiving a non-retransmitted RRC Connection Request message from the UE. The
RRC Connection Setup message is an RRC signaling message that the eNodeB sends to the UE.
The message is used to inform the UE of the RRC connection setup result and the related
configuration information.

Measurement Points
As shown at point B in Figure 2-10, the L.RRC.ConnSetup counter is incremented by 1 each
time the eNodeB sends an RRC Connection Setup message to a UE after receiving a non-
retransmitted RRC Connection Request message from the UE.
Figure 2-10
Formula
None
Unit
None
Related Features
L.RRC.ConnSetup Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management

2.2.1.5 Number of Times a UE Transits from the Uplink-Synchronized State to the

Uplink Out-of-Synchronization State
Counters
Description
1526728438 L.RRC.StateTrans.S Number of times a DBS3900 LTE/

yn2Unsyn UE transits from the BTS3900 LTE/
Uplink- BTS3900A LTE/
Synchronized state to BTS3900L LTE/
the uplink out-of- BTS3900AL LTE,
synchronization state BTS3900
Description
The counter measures the number of times a UE transits from the uplink-synchronized state to
the uplink out-of-synchronization state in the cell.
Measurement Points
The L.RRC.StateTrans.Syn2Unsyn counter is incremented by 1 each time a UE transits from
the uplink-synchronized state to the uplink out-of-synchronization state.
Formula
None
Unit
None
Related Features
L.RRC.StateTrans.Syn2Un- Multi-mode: None

syn GSM: None
UMTS: None
LTE: LOFD-001105 Dynamic DRX
TDLOFD-001105 Dynamic DRX
2.2.1.6 Number of Times a UE Transits from the Uplink Out-of-Synchronization

state to the Uplink-Synchronized State

Counters
Description
1526728439 L.RRC.StateTrans.U Number of times a DBS3900 LTE/

nsyn2Syn UE transits from the BTS3900 LTE/
out-of- BTS3900A LTE/
synchronization state BTS3900L LTE/
to the uplink- BTS3900AL LTE,
synchronized state BTS3900
Description
The counter measures the number of times a UE transits from the uplink out-of-synchronization
state to the uplink-synchronized state in the cell.
Measurement Points
The L.RRC.StateTrans.Unsyn2Syn counter is incremented by 1 each time a UE transits from
the uplink out-of-synchronization state to the uplink-synchronized state.
Formula
None
Unit
None
Related Features
L.RRC.StateTrans.Unsyn2S Multi-mode: None

yn GSM: None
UMTS: None
2.2.1.7 RRC Connection Setup Duration in a Cell

Counters
Description
1526728774 L.RRC.ConnSetup.T Average RRC DBS3900 LTE/

imeAvg connection setup BTS3900 LTE/
duration BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728775 L.RRC.ConnSetup.T Maximum RRC DBS3900 LTE/

imeMax connection setup BTS3900 LTE/
duration BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the RRC connection setup duration in a cell. The RRC connection setup
duration indicates the interval between the receiving of the RRC Connection Request message
and RRC Connection Setup Complet message.
Measurement Points
As shown at points A and B in Figure 2-11, the eNodeB records the time when it receives the
RRC Connection Request or RRC Connection Setup Complete message. The RRC connection
setup duration is the interval between the time when the two messages are received in an RRC
connection setup procedure. At the end of a measurement period, the average and maximum
RRC connection setup duration are the average and maximum duration of all durations,
respectively.

Figure 2-11
Formula
None
Unit
ms
Related Features
L.RRC.ConnSetup.Time- Multi-mode: None

Avg GSM: None
UMTS: None
RRC Connection
Management
L.RRC.ConnSetup.Time- Multi-mode: None

Max GSM: None
UMTS: None
RRC Connection
Management

2.2.2 Measurement related to RRC setup failure

(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 2-12 shows the measurement
points in a failed RRC connection setup procedure.
Figure 2-12
Counters
Description
1526727083 L.RRC.SetupFail.R Number of RRC V100R008C00,and

esFail connection setup the mapping single-
failures due to mode base station
resource allocation version that
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526727084 L.RRC.SetupFail.N Number of RRC V100R008C00,and

oReply connection setup the mapping single-
failures due to no mode base station
responses from the version that
UE introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

ej Connection Reject the mapping single-
messages sent to UEs mode base station
introduce this
counter is:
eNodeB:V100R003
C00

esFail.SRS connection setup the mapping single-
failures due to SRS mode base station
resource allocation version that
failure introduce this
counter is:
eNodeB:V100R006
C00

esFail.PUCCH connection setup the mapping single-
failures due to mode base station
PUCCH resource version that
allocation failure introduce this
counter is:
eNodeB:V100R006
C00
1526728489 L.RRC.ConnReq. Number of times the V100R008C00,and

Msg.disc.FlowCtrl RRC Connection the mapping single-
Request message is mode base station
discarded due to flow version that
control introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728490 L.RRC.SetupFail.R Number of times the V100R008C00,and

ej.FlowCtrl eNodeB sends an the mapping single-
RRC Connection mode base station
Reject message to the version that
UE due to flow introduce this
control counter is:
eNodeB:V100R006
C00
Counter Sub Counter
L.RRC.SetupFail.ResFail L.RRC.SetupFail.ResFail.SRS
L.RRC.SetupFail.ResFail.PUCCH
L.RRC.SetupFail.Rej L.RRC.SetupFail.ResFail
L.RRC.SetupFail.Rej.FlowCtrl
2.2.2.1 Number of RRC Connection Setup Failures for Different Causes in a Cell
Counters
Description
1526727083 L.RRC.SetupFail.Re Number of RRC DBS3900 LTE/

sFail connection setup BTS3900 LTE/
failures due to BTS3900A LTE/
resource allocation BTS3900L LTE/
failures BTS3900AL LTE,
BTS3900
1526727084 L.RRC.SetupFail.No Number of RRC DBS3900 LTE/

Reply connection setup BTS3900 LTE/
failures due to no BTS3900A LTE/
responses from the BTS3900L LTE/
UE BTS3900AL LTE,
BTS3900


Description

j Connection Reject BTS3900 LTE/
messages sent to UEs BTS3900A LTE/
BTS3900AL LTE,
BTS3900

sFail.SRS connection setup BTS3900 LTE/
failures due to SRS BTS3900A LTE/
resource allocation BTS3900L LTE/
failure BTS3900AL LTE,
BTS3900

sFail.PUCCH connection setup BTS3900 LTE/
failures due to BTS3900A LTE/
PUCCH resource BTS3900L LTE/
allocation failure BTS3900AL LTE,
BTS3900
1526728489 L.RRC.ConnReq.Ms Number of times the DBS3900 LTE/

g.disc.FlowCtrl RRC Connection BTS3900 LTE/
Request message is BTS3900A LTE/
discarded due to flow BTS3900L LTE/
control BTS3900AL LTE,
BTS3900
1526728490 L.RRC.SetupFail.Re Number of times the DBS3900 LTE/

j.FlowCtrl eNodeB sends an BTS3900 LTE/
RRC Connection BTS3900A LTE/
Reject message to the BTS3900L LTE/
UE due to flow BTS3900AL LTE,
control BTS3900
Description
The counters measure the number of RRC connection setup failures due to different causes in a
cell and the number of RRC Connection Request messages that are discarded due to flow control
in the cell. The RRC Connection Reject message is an RRC signaling message sent from the
eNodeB to the UE to inform the UE that the access is rejected by the eNodeB.
Measurement Points
As shown at point A in Figure 2-13, the L.RRC.SetupFail.ResFail,
L.RRC.SetupFail.ResFail.SRS, or L.RRC.SetupFail.ResFail.PUCCH counter is incremented by
1 each time the eNodeB sends an RRC Connection Reject message to the UE due to resource

allocation failure, SRS resource allocation failure, PUCCH resource allocation failure,
respectively, after receiving an RRC Connection Request message from the UE.
As shown at point A in Figure 2-14, 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 2-13, 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 2-13, 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 2-15, the L.RRC.ConnReq.Msg.disc.FlowCtrl counter is

incremented by 1 each time the eNodeB discards an RRC Connection Request message
(including retransmissions) from a UE due to flow control.
Figure 2-13

Figure 2-14
Figure 2-15
Formula
None
Unit
None

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

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

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

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

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

UCCH GSM: None
UMTS: None
RRC Connection
Management

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

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

trl GSM: None
UMTS: None
RRC Connection
Management
2.2.3 Measurement related to RRC reestablish (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 2-16 shows the measurement points in an RRC connection reestablishment
procedure.
Figure 2-16

Counters
Description
1526727085 L.RRC.ReEst.Att Number of RRC V100R008C00,and

connection the mapping single-
reestablishment mode base station
requests version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727086 L.RRC.ReEst.Succ Number of V100R008C00,and

successful RRC the mapping single-
connection mode base station
reestablishments version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727087 L.RRC.ReEst.Reco Number of RRC V100R008C00,and

nfFail.Att connection the mapping single-
requests triggered by version that
reconfiguration introduce this
failures counter is:
eNodeB:Version
earlier than
V100R003C00
1526727088 L.RRC.ReEst.Reco Number of V100R008C00,and

nfFail.Succ successful RRC the mapping single-
triggered by introduce this
reconfiguration counter is:
failures eNodeB:Version
earlier than
V100R003C00


Description
1526727090 L.RRC.ReEst.HoF Number of RRC V100R008C00,and

ail.Att connection the mapping single-
requests triggered by version that
failed handovers introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727091 L.RRC.ReEst.HoF Number of V100R008C00,and

ail.Succ successful RRC the mapping single-
triggered by failed introduce this
handovers counter is:
eNodeB:Version
earlier than
V100R003C00
Counter Sub Counter
L.RRC.ReEst.Att L.RRC.ReEst.ReconfFail.Att
L.RRC.ReEst.HoFail.Att
L.RRC.ReEst.Succ L.RRC.ReEst.ReconfFail.Succ
L.RRC.ReEst.HoFail.Succ
2.2.3.1 Number of RRC Connection Reestablishment Requests in a Cell
Counters
Description
1526727085 L.RRC.ReEst.Att Number of RRC DBS3900 LTE/

connection BTS3900 LTE/
reestablishment BTS3900A LTE/
requests BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1526727087 L.RRC.ReEst.Recon Number of RRC DBS3900 LTE/

fFail.Att connection BTS3900 LTE/
requests triggered by BTS3900L LTE/
reconfiguration BTS3900AL LTE,
failures BTS3900
1526727090 L.RRC.ReEst.HoFai Number of RRC DBS3900 LTE/

l.Att connection BTS3900 LTE/
requests triggered by BTS3900L LTE/
failed handovers BTS3900AL LTE,
BTS3900
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
the eNodeB receives an RRC Connection Reestablishment Request message from the UE. The
counters are measured as follows:
The L.RRC.ReEst.Att counter is incremented by 1 only when the eNodeB receives a non-
retransmitted RRC Connection Reestablishment Request message.
The L.RRC.ReEst.ReconfFail.Att counter is incremented by 1 each time the eNodeB receives

a non-retransmitted RRC Connection Reestablishment Request message from the UE and the
ReestablishmentCause information element (IE) in the message is "reconfigurationFailure".
The L.RRC.ReEst.HoFail.Att counter is incremented by 1 each time the eNodeB receives a non-
retransmitted RRC Connection Reestablishment Request message from the UE and the
ReestablishmentCause IE in the message is "handoverFailure".

Figure 2-17
Formula
None
Unit
None
Related Features
L.RRC.ReEst.Att Multi-mode: None

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

t GSM: None
UMTS: None
RRC Connection
Management

L.RRC.ReEst.HoFail.Att Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
2.2.3.2 Number of Successful RRC Connection Reestablishments in a Cell
Counters
Description
1526727086 L.RRC.ReEst.Succ Number of DBS3900 LTE/

successful RRC BTS3900 LTE/
connection BTS3900A LTE/
reestablishments BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526727088 L.RRC.ReEst.Recon Number of DBS3900 LTE/

fFail.Succ successful RRC BTS3900 LTE/
triggered by BTS3900AL LTE,
reconfiguration BTS3900
failures
1526727091 L.RRC.ReEst.HoFai Number of DBS3900 LTE/

l.Succ successful RRC BTS3900 LTE/
triggered by failed BTS3900AL LTE,
handovers BTS3900
Description
The counters measure the number of successful RRC connection reestablishments for different
causes in a cell. The RRC Connection Reestablishment Complete message is an RRC signaling
message sent from the UE to the eNodeB. The message is used to inform the eNodeB that the
RRC connection reestablishment is completed.

Measurement Points
As shown at point B in Figure 2-18, the corresponding counter is incremented by 1 each time
the eNodeB receives an RRC Connection Reestablishment Complete message from the UE. The
counters are measured as follows:
The L.RRC.ReEst.Succ counter is incremented by 1 each time the eNodeB receives the message
from the UE.
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."
Figure 2-18
Formula
None
Unit
None

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

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

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

GSM: None
UMTS: None
RRC Connection
Management
2.2.4 Measurement related to RRC reestablish fail

(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 2-19 shows the measurement points
in a failed RRC connection reestablishment procedure.

Figure 2-19
Counters
Description
1526727089 L.RRC.ReEst.Reco Number of rejected V100R008C00,and

nfFail.Rej RRC connection the mapping single-
attempts triggered by version that
reconfiguration introduce this
failures counter is:
eNodeB:Version
earlier than
V100R003C00
1526727092 L.RRC.ReEst.HoF Number of rejected V100R008C00,and

ail.Rej RRC connection the mapping single-
attempts triggered by version that
handover failures introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526727093 L.RRC.ReEstFail. Number of RRC V100R008C00,and

ResFail connection the mapping single-
failures due to failed version that
resource allocations introduce this
counter is:
eNodeB:V100R003
C00

NoReply connection the mapping single-
failures due to no version that
responses from the introduce this
UE counter is:
eNodeB:V100R003
C00
1526728270 L.RRC.ReEstFail. Total number of V100R008C00,and

Rej RRC connection the mapping single-
rejections version that
introduce this
counter is:
eNodeB:V100R003
C00

NoCntx connection the mapping single-
failures due to version that
unavailability of UE introduce this
contexts counter is:
eNodeB:V100R003
C00
Counter Sub Counter
L.RRC.ReEstFail.Rej L.RRC.ReEst.ReconfFail.Rej
L.RRC.ReEst.HoFail.Rej
L.RRC.ReEstFail.Rej L.RRC.ReEstFail.ResFail
L.RRC.ReEstFail.NoCntx

2.2.4.1 Number of RRC Connection Reestablishment Failures for Different Causes

in a Cell
Counters
Description
1526727089 L.RRC.ReEst.Recon Number of rejected DBS3900 LTE/

fFail.Rej RRC connection BTS3900 LTE/
attempts triggered by BTS3900L LTE/
reconfiguration BTS3900AL LTE,
failures BTS3900
1526727092 L.RRC.ReEst.HoFai Number of rejected DBS3900 LTE/

l.Rej RRC connection BTS3900 LTE/
attempts triggered by BTS3900L LTE/
handover failures BTS3900AL LTE,
BTS3900
1526727093 L.RRC.ReEstFail.Re Number of RRC DBS3900 LTE/

sFail connection BTS3900 LTE/
failures due to failed BTS3900L LTE/
resource allocations BTS3900AL LTE,
BTS3900
1526727094 L.RRC.ReEstFail.N Number of RRC DBS3900 LTE/

oReply connection BTS3900 LTE/
failures due to no BTS3900L LTE/
responses from the BTS3900AL LTE,
UE BTS3900
1526728270 L.RRC.ReEstFail.Re Total number of DBS3900 LTE/

j RRC connection BTS3900 LTE/
rejections BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728271 L.RRC.ReEstFail.N Number of RRC DBS3900 LTE/

oCntx connection BTS3900 LTE/
failures due to BTS3900L LTE/
unavailability of UE BTS3900AL LTE,
contexts BTS3900

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
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 2-21, 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.
Figure 2-20

Figure 2-21
Formula
None
Unit
None
Related Features
L.RRC.ReEst.ReconfFail.Re Multi-mode: None

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

GSM: None
UMTS: None
RRC Connection
Management

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

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

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

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

GSM: None
UMTS: None
RRC Connection
Management
2.2.5 Measurement related to E-RAB establish (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 2-22 shows the measurement points of an E-
RAB setup procedure during a non-handover process. Figure 2-23 shows the measurement
points of an E-RAB setup procedure initiated by the target eNodeB during a handover.

Figure 2-22

Figure 2-23
Counters
Description
1526726668 L.E- Number of E-RAB V100R008C00,and

RAB.AttEst.QCI.1 setup attempts the mapping single-
initiated by UEs for mode base station
services with the QCI version that
of 1 in a cell introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526726669 L.E- Number of V100R008C00,and

RAB.SuccEst.QCI. successful E-RAB the mapping single-
1 setups initiated by mode base station
UEs for services with version that
the QCI of 1 in a cell introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00


Description

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00


Description

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00


Description

counter is:
eNodeB:Version
earlier than
V100R003C00
1526727027 E-RAB Establish E-RAB setup success V100R008C00,and

Success Rate rate in a cell the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727544 L.E-RAB.SuccEst Total number of V100R008C00,and

successful E-RAB the mapping single-
setups initiated by mode base station
UEs in a cell version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727545 L.E-RAB.AttEst Total number of E- V100R008C00,and

RAB setup attempts the mapping single-
initiated by UEs in a mode base station
cell version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526728192 L.E- Number of initial E- V100R008C00,and

RAB.InitAttEst.Q RAB setup attempts the mapping single-
CI.1 initiated by UEs for mode base station
counter is:
eNodeB:V100R003
C00


Description

RAB.InitSuccEst.Q successful initial E- the mapping single-
CI.1 RAB setups initiated mode base station
by UEs for services version that
with the QCI of 1 in introduce this
a cell counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00

a cell counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00

a cell counter is:
eNodeB:V100R003
C00


Description

counter is:
eNodeB:V100R003
C00

a cell counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00

a cell counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00


Description

a cell counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00

a cell counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00

a cell counter is:
eNodeB:V100R003
C00


Description

counter is:
eNodeB:V100R003
C00

a cell counter is:
eNodeB:V100R003
C00
1526728244 L.E- Total number of E- V100R008C00,and

RAB.AttEst.HOIn RAB setup attempts the mapping single-
for incoming mode base station
handovers in a cell version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728245 L.E- Total number of V100R008C00,and

RAB.SuccEst.HOI successful E-RAB the mapping single-
n setups for incoming mode base station
introduce this
counter is:
eNodeB:V100R003
C00
1526728272 L.S1Sig.ConnEst.A Number of UE- V100R008C00,and

tt related signaling the mapping single-
connection setup mode base station
attempts over the S1 version that
interface introduce this
counter is:
eNodeB:V100R003
C00


Description
1526728273 L.S1Sig.ConnEst.S Number of V100R008C00,and

ucc successful UE- the mapping single-
related signaling mode base station
connection setups version that
over the S1 interface introduce this
counter is:
eNodeB:V100R003
C00

RAB.InitAttEst initial E-RAB setup the mapping single-
attempts initiated by mode base station
introduce this
counter is:
eNodeB:V100R003
C00

RAB.InitSuccEst successful initial E- the mapping single-
RAB setups initiated mode base station
by UEs in a cell version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728776 L.E- Average E-RAB V100R008C00,and

RAB.Est.TimeAvg setup duration in a the mapping single-
cell mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728777 L.E- Maximum E-RAB V100R008C00,and

RAB.Est.TimeMax setup duration in a the mapping single-
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description

n.QCI.1 setups for incoming mode base station
handovers of version that
services with QCI of introduce this
1 in a cell counter is:
eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00
1526728879 L.E- Average initial E- V100R008C00,and

RAB.InitEst.Time- RAB setup duration the mapping single-
Avg in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728880 L.E- Maximum initial E- V100R008C00,and

RAB.InitEst.Time- RAB setup duration the mapping single-
Max in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
Counter Sub Counter
L.E-RAB.AttEst.QCI.1 L.E-RAB.InitAttEst.QCI.1
L.E-RAB.SuccEst.QCI.1 L.E-RAB.InitSuccEst.QCI.1

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

Counter Sub Counter
L.E-RAB.InitSuccEst L.E-RAB.InitSuccEst.QCI.1
L.E-RAB.InitSuccEst.QCI.2
2.2.5.1 Number of E-RAB Setup Attempts in a Cell
Counters
Description
1526726668 L.E- Number of E-RAB DBS3900 LTE/

RAB.AttEst.QCI.1 setup attempts BTS3900 LTE/
initiated by UEs for BTS3900A LTE/
services with the QCI BTS3900L LTE/
of 1 in a cell BTS3900AL LTE,
BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900
1526727545 L.E-RAB.AttEst Total number of E- DBS3900 LTE/

RAB setup attempts BTS3900 LTE/
initiated by UEs in a BTS3900A LTE/
cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of E-RAB setup attempts initiated by UEs for services with
a specific QCI ranging from 1 to 9 and the total number of E-RABsetup attempts initiated by
UEs in a cell. The E-RAB setup is initiated by a UE when the UE requests a service from the
radio network. The setup is implemented through the initial UE context setup or the E-RAB
setup procedure.

Measurement Points
As shown at point A in Figure 2-24 or Figure 2-25, the corresponding counter is incremented
based on the QCI of each service each time the eNodeB receives an INITIAL CONTEXT SETUP
REQUEST or an E-RAB SETUP REQUEST message from the MME. If the INITIAL
CONTEXT SETUP REQUEST or E-RAB SETUP REQUEST message requests multiple E-
RAB setups at the same time, the corresponding counter is incremented by the number of
requested E-RAB setups in the message based on the QCI of each service. In addition the number
of requested E-RAB setups contained in the INITIAL CONTEXT SETUP REQUEST and E-
RAB SETUP REQUEST messages is accumulated as the value of the L.E-RAB.AttEst counter.
Figure 2-24

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

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

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

GSM: None
UMTS: None
2.2.5.2 Number of Successful E-RAB Setups in a Cell
Counters
Description
1526726669 L.E- Number of DBS3900 LTE/

RAB.SuccEst.QCI.1 successful E-RAB BTS3900 LTE/
setups initiated by BTS3900A LTE/
UEs for services with BTS3900L LTE/
the QCI of 1 in a cell BTS3900AL LTE,
BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900
1526727544 L.E-RAB.SuccEst Total number of DBS3900 LTE/

successful E-RAB BTS3900 LTE/
UEs in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of successful E-RAB setups initiated by UEs for services with
a specific QCI ranging from 1 to 9 and the total number of successful E-RAB setups initiated
by UEs in a cell. The E-RAB setup is initiated by a UE when the UE requests a service from the
radio network. The setup is implemented through the initial UE context setup or the E-RAB
setup procedure.

Measurement Points
As shown at point B in Figure 2-26 or Figure 2-27, the corresponding counter is incremented
based on the QCI of each service each time the eNodeB sends an E-RAB SETUP RESPONSE
or an INITIAL CONTEXT SETUP RESPONSE message to the MME. If the E-RAB SETUP
RESPONSE or INITIAL CONTEXT SETUP RESPONSE message reports multiple successful
E-RAB setups at the same time, the corresponding counter is incremented by the number of
successful E-RAB setups in the message based on the QCI of each service. In addition, the
number of successful E-RAB setups contained in the E-RAB SETUP RESPONSE and INITIAL
CONTEXT SETUP RESPONSE messages is accumulated as the value of the L.E-RAB.SuccEst
counter.
Figure 2-26

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

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


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

GSM: None
UMTS: None
2.2.5.3 E-RAB Setup Success Rate in a Cell
Counters
Description
1526727027 E-RAB Establish E-RAB setup success DBS3900 LTE/

Success Rate rate in a cell BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the E-RAB setup success rate in a cell.
Measurement Points
The E-RAB setup success rate in a cell is calculated by using the corresponding KPI calculation
formula based on the values of the counters L.E-RAB.SuccEst.QCI.1, L.E-RAB.SuccEst.QCI.
2, L.E-RAB.SuccEst.QCI.3, L.E-RAB.SuccEst.QCI.4, L.E-RAB.SuccEst.QCI.5, L.E-
RAB.SuccEst.QCI.6, L.E-RAB.SuccEst.QCI.7, L.E-RAB.SuccEst.QCI.8, L.E-
RAB.SuccEst.QCI.9, L.E-RAB.AttEst.QCI.1, L.E-RAB.AttEst.QCI.2, L.E-RAB.AttEst.QCI.
3, L.E-RAB.AttEst.QCI.4, L.E-RAB.AttEst.QCI.5, L.E-RAB.AttEst.QCI.6, L.E-
RAB.AttEst.QCI.7, L.E-RAB.AttEst.QCI.8, and L.E-RAB.AttEst.QCI.9.

Formula
{100}*([L.E-RAB.SuccEst.QCI.1]+[L.E-RAB.SuccEst.QCI.2]+[L.E-RAB.SuccEst.QCI.3]+
[L.E-RAB.SuccEst.QCI.4]+[L.E-RAB.SuccEst.QCI.5]+[L.E-RAB.SuccEst.QCI.6]+[L.E-
RAB.SuccEst.QCI.7]+[L.E-RAB.SuccEst.QCI.8]+[L.E-RAB.SuccEst.QCI.9])/([L.E-
RAB.AttEst.QCI.1]+[L.E-RAB.AttEst.QCI.2]+[L.E-RAB.AttEst.QCI.3]+[L.E-
RAB.AttEst.QCI.4]+[L.E-RAB.AttEst.QCI.5]+[L.E-RAB.AttEst.QCI.6]+[L.E-
RAB.AttEst.QCI.7]+[L.E-RAB.AttEst.QCI.8]+[L.E-RAB.AttEst.QCI.9])
Unit
%
Related Features
E-RAB Establish Success Multi-mode: None

Rate GSM: None
UMTS: None
2.2.5.4 Number of Initial E-RAB Setup Attempts in a Cell
Counters
Description
1526728192 L.E- Number of initial E- DBS3900 LTE/

RAB.InitAttEst.QCI RAB setup attempts BTS3900 LTE/
.1 initiated by UEs for BTS3900A LTE/
BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description
1526728274 L.E-RAB.InitAttEst Total number of DBS3900 LTE/

initial E-RAB setup BTS3900 LTE/
attempts initiated by BTS3900A LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of initial E-RAB setup attempts initiated by UEs for services
with a specific QCI ranging from 1 to 9 and the total number of initial E-RAB setup attempts
initiated by UEs in a cell. The initial E-RAB setup is initiated by a UE when the UE requests a
service from the radio network. The setup is implemented through the initial UE context setup
procedure.
Measurement Points
As shown at point A in Figure 2-28, the corresponding counter is incremented based on the QCI
of each service each time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST
message from the MME. If the INITIAL CONTEXT SETUP REQUEST message requests to
set up multiple initial E-RABs at the same time, the corresponding counter is incremented by
the number of requested initial E-RAB setups in the message based on the QCI of each service.
In addition, the number of requested initial E-RAB setups contained in the INITIAL CONTEXT
SETUP REQUEST messages is accumulated as the value of the L.E-RAB.InitAttEst counter.

Figure 2-28
Formula
None
Unit
None
Related Features
L.E-RAB.InitAttEst.QCI.1 Multi-mode: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


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

GSM: None
UMTS: None
2.2.5.5 Number of Successful Initial E-RAB Setups in a Cell
Counters
Description

RAB.InitSuccEst.Q successful initial E- BTS3900 LTE/
CI.1 RAB setups initiated BTS3900A LTE/
by UEs for services BTS3900L LTE/
with the QCI of 1 in BTS3900AL LTE,
a cell BTS3900

a cell BTS3900

a cell BTS3900


Description

a cell BTS3900

a cell BTS3900

a cell BTS3900

a cell BTS3900

a cell BTS3900

a cell BTS3900
1526728275 L.E- Total number of DBS3900 LTE/

RAB.InitSuccEst successful initial E- BTS3900 LTE/
RAB setups initiated BTS3900A LTE/
by UEs in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
The counters measure the number of successful initial E-RAB setups initiated by UEs for
services with a specific QCI ranging from 1 to 9 and the total number of successful initial E-
RAB setups initiated by UEs in a cell. The initial E-RAB setup is initiated by a UE when the
UE requests a service from the radio network. The setup is implemented through the initial UE
context setup procedure.
Measurement Points
As shown at point B in Figure 2-29, the corresponding counter is incremented based on the QCI
of each service each time the eNodeB sends an INITIAL CONTEXT SETUP RESPONSE
message to the MME. If the INITIAL CONTEXT SETUP RESPONSE message reports multiple
successful initial E-RAB setups at the same time, the corresponding counter is incremented by
the number of successful initial E-RAB setups in the message based on the QCI of each service.
In addition, the number of successful initial E-RAB setups contained in the INITIAL CONTEXT
SETUP RESPONSE messages is accumulated as the value of the L.E-RAB.InitSuccEst counter.
Figure 2-29
Formula
None

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

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

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

GSM: None
UMTS: None
2.2.5.6 Total Number of E-RAB Setup Attempts for Incoming Handovers in a Cell
Counters
Description
1526728244 L.E- Total number of E- DBS3900 LTE/

RAB.AttEst.HOIn RAB setup attempts BTS3900 LTE/
for incoming BTS3900A LTE/
handovers in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the total number of E-RAB setup attempts for incoming handovers in a
cell.

Measurement Points
Figure 2-30 shows an intra-eNodeB handover, Figure 2-31 shows anX2-based handover, and
Figure 2-32 shows an S1-bases handover. As shown at point A in Figure 2-30, Figure 2-31, or
Figure 2-32, the L.E-RAB.AttEst.HOIn counter is incremented in the target cell each time the
eNodeB decides to perform a handover after receiving a measurement report from a UE. If
multiple E-RABs are attempted to be set up in the target cell, the counter is incremented in the
target cell by the number of requested E-RAB setups.
Figure 2-30
Figure 2-31

Figure 2-32
Formula
None
Unit
None
Related Features
L.E-RAB.AttEst.HOIn Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-00201801 Coverage Based Intra-
LBFD-00201802 frequency Handover
TDLBFD-00201801 Coverage Based Inter-

frequency Handover
TDLBFD-00201802
Coverage Based Intra-
frequency Handover
Coverage Based Inter-
frequency Handover
2.2.5.7 Number of Successful E-RAB Setups for Incoming Handovers in a Cell

Counters
Description

RAB.SuccEst.HOIn successful E-RAB BTS3900 LTE/
setups for incoming BTS3900A LTE/
BTS3900AL LTE,
BTS3900

RAB.SuccEst.HOIn. successful E-RAB BTS3900 LTE/
QCI.1 setups for incoming BTS3900A LTE/
handovers of BTS3900L LTE/
services with QCI of BTS3900AL LTE,
1 in a cell BTS3900

2 in a cell BTS3900

3 in a cell BTS3900

4 in a cell BTS3900

5 in a cell BTS3900

6 in a cell BTS3900


Description

7 in a cell BTS3900

8 in a cell BTS3900

9 in a cell BTS3900
Description
The counters measure the number of successful E-RAB setups for services with a specific QCI
ranging from 1 to 9 for incoming handovers and the total number of successful E-RAB setups
for incoming handovers in a cell.
Measurement Points
As shown at point C in Figure 2-33, during an intra-eNodeB handover the corresponding counter
is incremented in the target cell based on the QCI of each service each time the target cell receives
an RRC Connection Reconfiguration Complete message from a UE and the subsequent
processing is successful. If multiple E-RABs are set up in the target cell, the corresponding
counter is incremented by the number of successful E-RAB setups in the target cell based on
the QCI of each service.
As shown at point C in Figure 2-34, the corresponding counter is incremented in the target cell
based on the QCI of each service each time the target cell receives an RRC Connection
Reestablishment Complete message from a UE and the subsequent processing is successful. If
multiple E-RABs are set up in the target cell, the corresponding counter is incremented by the
number of successful E-RAB setups in the target cell based on the QCI of each service.
As shown at point C in Figure 2-35, during an X2-based handover the corresponding counter
is incremented in the target cell based on the QCI of each service each time the target eNodeB
receives a PATH SWITCH REQUEST ACKNOWLEDGE message from the MME and sends
a UE CONTEXT RELEASE message to the source eNodeB over the X2 interface. If multiple
E-RABs are set up in the target cell, the corresponding counter is incremented by the number
of successful E-RAB setups in the target cell based on the QCI of each service.

is incremented in the target cell based on the QCI of each service each time the target eNodeB
receives a PATH SWITCH REQUEST ACKNOWLEDGE message from the MME and sends
a UE CONTEXT RELEASE message to the source eNodeB over the X2 interface after the RRC
connection for the UE is successfully reestablished to the target eNodeB. If multiple E-RABs
are set up in the target cell, the corresponding counter is incremented by the number of successful
E-RAB setups in the target cell based on the QCI of each service.
As shown at point C in Figure 2-37, during an S1-based handover the corresponding counter is
incremented in the target cell based on the QCI of each service each time the target eNodeB
sends a HANDOVER NOTIFY message to the MME. If multiple E-RABs are set up in the target
cell, the corresponding counter is incremented by the number of successful E-RAB setups in the
target cell based on the QCI of each service.
As shown at point C in Figure 2-38, during an S1-based handover the corresponding counter is
incremented in the target cell based on the QCI of each service each time the target eNodeB
sends a HANDOVER NOTIFY message to the MME after the RRC connection for the UE is
successfully to the target eNodeB. If multiple E-RABs are set up in the target cell, the
corresponding counter is incremented by the number of successful E-RAB setups in the target
cell based on the QCI of each service.
Figure 2-33

Figure 2-34
Figure 2-35

Figure 2-36
Figure 2-37

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

GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

L.E- Multi-mode: None

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

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover


UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover


UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.5.8 Number of UE-related Signaling Connection Setups over the S1 Interface

Counters
Description
1526728272 L.S1Sig.ConnEst.At Number of UE- DBS3900 LTE/

t related signaling BTS3900 LTE/
connection setup BTS3900A LTE/
attempts over the S1 BTS3900L LTE/
interface BTS3900AL LTE,
BTS3900
1526728273 L.S1Sig.ConnEst.Su Number of DBS3900 LTE/

cc successful UE- BTS3900 LTE/
related signaling BTS3900A LTE/
connection setups BTS3900L LTE/
over the S1 interface BTS3900AL LTE,
BTS3900
Description
The counters measure the number of UE-related signaling connection setup attempts and the
number of successful UE-specific signaling connection setups over the S1 interface, that is, the
number of times that the eNodeB sends an INITIAL UE MESSAGE message to the MME and
the number of times the eNodeB receives the first message over the S1 interface from the MME,
respectively. The INITIAL UE MESSAGE message is the first message that the eNodeB sends
to the MME over the S1 interface. This message is used to transmit UE-related NAS layer
configuration data to the MME. The MME sets up S1 signaling connections based on NAS
information in the message. The first message that the eNodeB received from the MME over
the S1 interface can be the INITIAL CONTEXT SETUP REQUEST, DOWNLINK NAS
TRANSPORT, or UE CONTEXT RELEASE COMMAND message. If the message is received,
an S1 signaling connection is set up successfully.
Measurement Points
As shown at point A in Figure 2-39, the L.S1Sig.ConnEst.Att counter is incremented by 1 each
time the eNodeB sends an INITIAL UE MESSAGE message to the MME.
As shown at point B in Figure 2-39, the L.S1Sig.ConnEst.Succ counter is incremented by 1

each time the eNodeB receives the first message from the MME over the S1 interface after
sending an INITIAL UE MESSAGE message to the MME.

Figure 2-39
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
2.2.5.9 E-RAB Setup Duration in a Cell

Counters
Description
1526728776 L.E- Average E-RAB DBS3900 LTE/

RAB.Est.TimeAvg setup duration in a BTS3900 LTE/
cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728777 L.E- Maximum E-RAB DBS3900 LTE/

RAB.Est.TimeMax setup duration in a BTS3900 LTE/
cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728879 L.E- Average initial E- DBS3900 LTE/

RAB.InitEst.Time- RAB setup duration BTS3900 LTE/
Avg in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728880 L.E- Maximum initial E- DBS3900 LTE/

RAB.InitEst.Time- RAB setup duration BTS3900 LTE/
Max in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the E-RAB setup duration. The E-RAB setup is initiated by a UE when
the UE requests a service from the radio network. The setup is implemented through the initial
UE context setup or the E-RAB setup procedure.
Measurement Points
As shown at points A and B in Figure 2-40, the eNodeB records the time points when the eNodeB
receives an INITIAL CONTEXT SETUP REQUEST message from the MME and sends the
corresponding INITIAL CONTEXT SETUP RESPONSE message to the MME and saves the
interval between them as a sample regardless of the number of E-RABs indicated by the
messages. As shown at points A and B in Figure 2-41, the eNodeB records the time points when
the eNodeB receives an E-RAB SETUP REQUEST message from the MME and sends the
corresponding E-RAB SETUP RESPONSE message to the MME and saves the interval between
them as a sample regardless of the number of E-RABs indicated by the messages. At the end of
a measurement period, the average and maximum of these sampling results are used as the values

of the L.E-RAB.Est.TimeAvg and L.E-RAB.Est.TimeMax counters, respectively. The E-RAB

setup duration is not counted if the setup fails.
As shown at points A and B in Figure 2-40, the eNodeB records the time points when the eNodeB
receives an INITIAL CONTEXT SETUP REQUEST message from the MME and sends the
corresponding INITIAL CONTEXT SETUP RESPONSE message to the MME and saves the
interval between them as a sample regardless of the number of E-RABs indicated by the
messages. At the end of a measurement period, the average and maximum of these sampling
results are used as the values of the L.E-RAB.InitEst.TimeAvg and L.E-RAB.InitEst.TimeMax
counters, respectively. The initial E-RAB setup duration is not counted if the initial E-RAB setup
fails.
Figure 2-40

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

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

GSM: None
UMTS: None

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

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

GSM: None
UMTS: None
2.2.6 Measurement related to E-RAB release (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
2-42 and Figure 2-43 shows the measurement points of an E-RAB release procedure during a
non-handover process. Figure 2-44 shows the measurement points of an E-RAB release
procedure initiated by the source eNodeB during a handover.
Figure 2-42

Figure 2-43
Figure 2-44
Counters
Description
1526726686 L.E- Number of abnormal V100R008C00,and

RAB.AbnormRel. releases of activated the mapping single-
QCI.1 E-RABs for services mode base station
with the QCI of 1 in version that
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526726687 L.E- Number of normal E- V100R008C00,and

RAB.NormRel.QC RAB releases for the mapping single-
I.1 services with the QCI mode base station
of 1 in a cell version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

counter is:
eNodeB:Version
earlier than
V100R003C00

introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00


Description

introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

counter is:
eNodeB:Version
earlier than
V100R003C00

introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

RAB.NormRel.HO RAB releases for the mapping single-
Out.QCI.1 outgoing handovers mode base station
of services with the version that
QCI of 1 in a cell introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00


Description

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00


Description

counter is:
eNodeB:Version
earlier than
V100R003C00

RAB.AbnormRel. E-RAB releases for the mapping single-
HOOut.QCI.1 outgoing handovers mode base station
counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00


Description

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00


Description

RAB.AbnormRel abnormal releases of the mapping single-
activated E-RABs mode base station
initiated by the version that
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727547 L.E-RAB.NormRel Total number of V100R008C00,and

normal E-RAB the mapping single-
releases initiated by mode base station
the eNodeB in a cell version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

RAB.NormRel.HO normal E-RAB the mapping single-
Out releases for outgoing mode base station
introduce this
counter is:
eNodeB:V100R003
C00

RAB.AbnormRel. abnormal E-RAB the mapping single-
HOOut releases for outgoing mode base station
introduce this
counter is:
eNodeB:V100R003
C00

RAB.AbnormRel.R releases of activated the mapping single-
adio E-RABs because of mode base station
faults at the radio version that
network layer introduce this
counter is:
eNodeB:V100R003
C00


Description

RAB.AbnormRel.T releases of activated the mapping single-
NL E-RABs because of mode base station
faults at the transport version that
network layer introduce this
counter is:
eNodeB:V100R003
C00

RAB.AbnormRel.C releases of activated the mapping single-
ong E-RABs because of mode base station
network congestion version that
introduce this
counter is:
eNodeB:V100R003
C00

HOFailure E-RABs because of mode base station
handover failures version that
introduce this
counter is:
eNodeB:V100R003
C00

MME E-RABs due to faults mode base station
on the MME side version that
introduce this
counter is:
eNodeB:V100R003
C00

RAB.AbnormRel.e abnormal releases of the mapping single-
NBTot E-RABs initiated by mode base station
the eNodeB version that
introduce this
counter is:
eNodeB:V100R005
C00


Description
1526728436 L.E- Number of released V100R008C00,and

RAB.Release.Un- E-RABs of UEs in the mapping single-
syn the uplink out-of- mode base station
synchronization state version that
introduce this
counter is:
eNodeB:V100R006
C00

RAB.Num.Syn2Un RABs in UE contexts the mapping single-
syn when the UEs switch mode base station
from the uplink version that
synchronized state to introduce this
the uplink out-of- counter is:
synchronization state eNodeB:V100R006
in a cell C00

RAB.Rel.eNodeB.Q releases initiated by the mapping single-
CI.1 the eNodeB for mode base station
services with QCI of version that
1 in a cell introduce this
counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

RAB.Rel.eNodeB RAB releases the mapping single-
initiated by the mode base station
eNodeB in a cell version that
introduce this
counter is:
eNodeB:V100R006
C00

RAB.Rel.MME.QC releases initiated by the mapping single-
I.1 the MME for mode base station
counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

RAB.Rel.MME RAB releases the mapping single-
initiated by the MME mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

RAB.Left.QCI.1 remaining E-RABs the mapping single-
for services with QCI mode base station
introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00


Description

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00


Description

introduce this
counter is:
eNodeB:V100R006
C00
1526728817 L.E-RAB.Left Total number of V100R008C00,and

remaining E-RABs the mapping single-
in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

RAB.Rel.S1Reset.e E-RAB releases the mapping single-
NodeB.QCI.1 initiated by the mode base station
eNodeB for services version that
with QCI of 1 introduce this
because of the S1 counter is:
RESET in a cell eNodeB:V100R006
C00

C00

C00


Description

C00

C00

C00

C00

C00


Description

C00

RAB.Rel.S1Reset.e abnormal E-RAB the mapping single-
NodeB releases initiated by mode base station
the eNodeB because version that
of the S1 RESET in a introduce this
cell counter is:
eNodeB:V100R006
C00

RAB.Rel.S1Reset. E-RAB releases the mapping single-
MME.QCI.1 initiated by the MME mode base station
with QCI of 1 version that
because of the S1 introduce this
RESET in a cell counter is:
eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

RAB.Rel.S1Reset. abnormal E-RAB the mapping single-
MME releases initiated by mode base station
the MME because of version that
the S1 RESET in a introduce this
cell counter is:
eNodeB:V100R006
C00

RAB.AbnormRel. abnormal E-RAB the mapping single-
MMETot releases due to faults mode base station
on the MME side version that
introduce this
counter is:
eNodeB:V100R006
C00
Counter Sub Counter
L.E-RAB.NormRel.QCI.1 L.E-RAB.Rel.MME.QCI.1

Counter Sub Counter
L.E-RAB.AbnormRel L.E-RAB.AbnormRel.QCI.1
L.E-RAB.AbnormRel.QCI.2
L.E-RAB.AbnormRel L.E-RAB.AbnormRel.Radio
L.E-RAB.AbnormRel.TNL
L.E-RAB.AbnormRel.Cong
L.E-RAB.AbnormRel.HOFailure
L.E-RAB.NormRel L.E-RAB.NormRel.QCI.1
L.E-RAB.NormRel.QCI.2
L.E-RAB.NormRel L.E-RAB.Rel.MME
L.E-RAB.NormRel.HOOut L.E-RAB.NormRel.HOOut.QCI.1
L.E-RAB.NormRel.HOOut.QCI.2

Counter Sub Counter
L.E-RAB.AbnormRel.HOOut L.E-RAB.AbnormRel.HOOut.QCI.1
L.E-RAB.AbnormRel.HOOut.QCI.2
L.E-RAB.AbnormRel.eNBTot L.E-RAB.AbnormRel
L.E-RAB.Rel.eNodeB L.E-RAB.Rel.eNodeB.QCI.1
L.E-RAB.Rel.eNodeB.QCI.2
L.E-RAB.Rel.MME L.E-RAB.Rel.MME.QCI.1
L.E-RAB.Rel.MME.QCI.2
L.E-RAB.Rel.MME L.E-RAB.AbnormRel.MME
L.E-RAB.Rel.MME L.E-RAB.AbnormRel.MMETot

Counter Sub Counter
L.E-RAB.Left L.E-RAB.Left.QCI.1
L.E-RAB.Left.QCI.2
L.E-RAB.Left.QCI.3
L.E-RAB.Left.QCI.4
L.E-RAB.Left.QCI.5
L.E-RAB.Left.QCI.6
L.E-RAB.Left.QCI.7
L.E-RAB.Left.QCI.8
L.E-RAB.Left.QCI.9
L.E-RAB.Rel.S1Reset.eNodeB L.E-RAB.Rel.S1Reset.eNodeB.QCI.1
L.E-RAB.Rel.S1Reset.eNodeB.QCI.2
L.E-RAB.Rel.S1Reset.MME L.E-RAB.Rel.S1Reset.MME.QCI.1
L.E-RAB.Rel.S1Reset.MME.QCI.2
L.E-RAB.AbnormRel.MMETot L.E-RAB.AbnormRel.MME
2.2.6.1 Number of Abnormal E-RAB Releases in a Cell

Counters
Description
1526726686 L.E- Number of abnormal DBS3900 LTE/

RAB.AbnormRel.Q releases of activated BTS3900 LTE/
CI.1 E-RABs for services BTS3900A LTE/
with the QCI of 1 in BTS3900L LTE/
BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900
Description
The counters measure the number of abnormal E-RAB releases for services with a specific QCI
ranging from 1 to 9 in a cell. An E-RAB is the access layer bearer for carrying service data of a
UE. The E-RAB release is a process of releasing the access layer bearer resources of UEs. It
represents the capability of a cell to release access layer bearer resources for UEs.
Measurement Points
As shown at point A in Figure 2-45, when the eNodeB sends an E-RAB RELEASE
INDICATION message to the MME, the corresponding counter is incremented based on the
QCI of each service each time the eNodeB determines that the E-RAB to be released carries
data and the release cause is not "Normal Release", "Detach", "User Inactivity", "CS Fallback
triggered", "UE Not Available For PS Service", "Inter-RAT Redirection", or "Successful
Handover". If the E-RAB RELEASE INDICATION message requests to release multiple E-
RABs at the same time, the corresponding counter is incremented by the number of requested
E-RAB releases in the message based on the QCI of each service.
As shown at point A in Figure 2-46, when the eNodeB sends a UE CONTEXT RELEASE
REQUEST message to the MME, all E-RABs of the UE are released. In this case, the
corresponding counter is incremented by the number of E-RABs to be released based on the
QCI of each service if the eNodeB determines that the E-RABs to be released carry data and the
release cause is not "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered",
"UE Not Available For PS Service", "Inter-RAT Redirection", "Time Critical Handover", or
"Handover Cancelled". When the MME sends a UE CONTEXT RELEASE COMMAND
message to the eNodeB, the corresponding counter is not incremented.

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

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None
2.2.6.2 Number of Normal E-RAB Releases in a Cell
Counters
Description
1526726687 L.E- Number of normal E- DBS3900 LTE/

RAB.NormRel.QCI. RAB releases for BTS3900 LTE/
1 services with the QCI BTS3900A LTE/
of 1 in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900


Description

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900
1526727547 L.E-RAB.NormRel Total number of DBS3900 LTE/

normal E-RAB BTS3900 LTE/
releases initiated by BTS3900A LTE/
the eNodeB in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of normal E-RAB releases for services with a specific QCI
ranging from 1 to 9 and the total number of normal E-RAB releases in a cell. An E-RAB is the
access layer bearer for carrying service data of a UE. The E-RAB release is a process of releasing
the access layer bearer resources of UEs. It represents the capability of a cell to release access
layer bearer resources for UEs.

Measurement Points
As shown at point A in Figure 2-47, in an E-RAB release procedure initiated by the eNodeB,
the corresponding counter is incremented based on the QCI of each service each time the eNodeB
sends an E-RAB RELEASE INDICATION message to the MME and one of the following
conditions is met:
(1) The release cause is "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered",
"UE Not Available For PS Service", or "Inter-RAT Redirection".
(2) The eNodeB determines that the E-RAB to be released does not carry data. If the E-RAB
RELEASE INDICATION message requests to release multiple E-RABs at the same time, the
corresponding counter is incremented by the number of E-RABs to be released in the message
based on the QCI of each service. In addition, the number of requested E-RAB releases contained
in the E-RAB RELEASE INDICATION messages is accumulated as the value of the L.E-
RAB.NormRel counter.
As shown at point A in Figure 2-48, in an E-RAB release procedure initiated by the MME, the
corresponding counter is incremented based on the QCI of each service each time the the eNodeB
receives an E-RAB RELEASE COMMAND message from the MME. If the E-RAB RELEASE
COMMAND message requests to release multiple E-RABs at the same time, the corresponding
counter is incremented by the number of requested E-RAB releases in the message based on the
QCI of each service. In addition, the number of requested E-RAB releases contained in the E-
RAB RELEASE COMMAND messages is accumulated as the value of the L.E-RAB.NormRel
counter.
As shown at point A in Figure 2-49, in an E-RAB releases procedure initiated by the eNodeB,
all E-RABs of the UE are released when the eNodeB sends a UE CONTEXT RELEASE
REQEUST message to the MME. In this case, the corresponding counter is incremented based
on the QCI of each service each time one the following conditions is met:
(1) The release cause is "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered",
"UE Not Available for PS Service", "Inter-RAT Redirection", "Time Critical Handover", or
"Handover Cancelled".
(2) The eNodeB determines that the E-RABs to be released do not carry data. In addition, the
number of requested E-RAB releases contained in the UE CONTEXT RELEASE REQEUST
messages is accumulated as the value of the L.E-RAB.NormRel counter. When the MME sends
a UE CONTEXT RELEASE COMMAND message to the eNodeB, the corresponding counter
is not incremented.
As shown at point B in Figure 2-49, in an E-RAB release procedure initiated by the MME, all
E-RABs of the UE are released when the eNodeB receives a UE CONTEXT RELEASE
COMMAND message from the MME. The corresponding counter is incremented based on the
QCI if the release cause is not "Successful Handover ", "Partial Handover ", "S1 intra system
Handover triggered ", "S1 inter system Handover triggered ", or "X2 Handover triggered ". The
L.E-RAB.NormRel counter is incremented based on the number of services.

Figure 2-47
Figure 2-48
Figure 2-49
Formula
None
Unit
None

Related Features
L.E-RAB.NormRel.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

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

GSM: None
UMTS: None
2.2.6.3 Number of Normal E-RAB Releases for Outgoing Handovers in a Cell
Counters
Description

RAB.NormRel.HO RAB releases for BTS3900 LTE/
Out.QCI.1 outgoing handovers BTS3900A LTE/
of services with the BTS3900L LTE/
QCI of 1 in a cell BTS3900AL LTE,
BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

RAB.NormRel.HO- normal E-RAB BTS3900 LTE/
Out releases for outgoing BTS3900A LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of normal E-RAB releases for outgoing handovers of services
with a specific QCI ranging from 1 to 9 and the total number of normal E-RAB releases for
outgoing handovers in the source cell when the E-RABs for incoming handovers are successfully
set up in the target cell and the corresponding E-RABs in the source cell are normally released
for outgoing handovers.
Measurement Points
Figure 2-50 shows an intra-eNodeB handover, Figure 2-51 shows an X2-based handover,
Figure 2-52 shows an S1-based handover, and Figure 2-53 shows a handover from E-UTRAN
to WCDMA network, GERAN, or TD-SCDMA network. As shown at point C in Figure 2-50,
Figure 2-51, Figure 2-52, or Figure 2-53, the corresponding counter is incremented by the
number of normal E-RAB releases in the source cell based on the QCI of each service each time
a handover is successfully executed and the source cell normally releases the E-RABs that
correspond to the E-RABs successfully set up in the target cell. The number of normal E-RAB
releases in the target cell is accumulated as the value of the L.E-RAB.NormRel.HOOut counter.
Figure 2-50

Figure 2-51
Figure 2-52

Figure 2-53
Formula
None
Unit
None

Related Features

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

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


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

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


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

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


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

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


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

GSM: None
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover
2.2.6.4 Number of Abnormal E-RAB Releases for Outgoing Handovers in a Cell

Counters
Description

RAB.AbnormRel.H E-RAB releases for BTS3900 LTE/
OOut.QCI.1 outgoing handovers BTS3900A LTE/
BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900

RAB.AbnormRel.H abnormal E-RAB BTS3900 LTE/
OOut releases for outgoing BTS3900A LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of abnormal E-RAB releases for outgoing handovers of
services with a specific QCI and the total number of abnormal E-RAB releases for outgoing
handovers in the source cell when the E-RABs for incoming handovers fail to be set up in the
target cell and the corresponding E-RABs for outgoing handovers are abnormally released in
the source cell.
Measurement Points
Figure 2-56 shows an S1-based handover, and Figure 2-57 shows a handover from E-UTRAN
to WCDMA network, GERAN, or TD-SCDMA network. As shown at point C in Figure 2-54,
Figure 2-55, Figure 2-56, or Figure 2-57, the corresponding counter is incremented by the
number of abnormal E-RAB releases in the source cell based on the QCI of each service each
time a handover is successfully executed and the source cell abnormally releases the E-RABs
that correspond to the E-RABs failed to be set up in the target cell. The number of corresponding
abnormal E-RAB releases in the source cell is accumulated as the value of the L.E-
RAB.AbnormRel.HOOut counter.

Figure 2-54
Figure 2-55

Figure 2-56
Figure 2-57
Formula
None

Unit
None
Related Features

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

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


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

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


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

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


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

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


CI.9
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover
L.E-RAB.AbnormRel.HO- Multi-mode: None

Out GSM: None
UMTS: None
UTRAN
LBFD-00201802
between E-UTRAN and
UTRAN
frequency Handover
frequency Handover
2.2.6.5 Total Number of Abnormal E-RAB Releases in a Cell

Counters
Description

RAB.AbnormRel abnormal releases of BTS3900 LTE/
activated E-RABs BTS3900A LTE/
initiated by the BTS3900L LTE/
BTS3900

RAB.AbnormRel.e abnormal releases of BTS3900 LTE/
NBTot E-RABs initiated by BTS3900A LTE/
the eNodeB BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the total number of abnormal E-RAB releases in a cell based on the release
cause and user data transmission. An E-RAB is the access layer bearer for carrying service data
of a UE. The E-RAB release is a process of releasing the access layer bearer resources of UEs.
It represents the capability of a cell to release access layer bearer resources for UEs.
Measurement Points
As shown at point A in Figure 2-58, the L.E-RAB.AbnormRel.eNBTot counter is incremented
each time the eNodeB sends an E-RAB RELEASE INDICATION message to the MME and the
release cause is not "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered",
"UE Not Available For PS Service", "Inter-RAT Redirection", or "Successful Handover". In this
case, if the E-RAB RELEASE INDICATION message requests to release multiple E-RABs at
the same time, the L.E-RAB.AbnormRel.eNBTot counter is incremented by the number of
requested E-RAB releases contained in the message.
As shown at point A in Figure 2-58, the L.E-RAB.AbnormRel counter is incremented each time
the eNodeB sends an E-RAB RELEASE INDICATION message to the MME and the following
conditions are met:
(1) the release cause is not "Normal Release", "Detach", "User Inactivity", "CS Fallback
triggered", "UE Not Available For PS Service", "Inter-RAT Redirection", or "Successful
Handover".
(2) The eNodeB determines that the E-RAB to be released carries data.
In this case, if the E-RAB RELEASE INDICATION message requests to release multiple E-
RABs at the same time, the L.E-RAB.AbnormRel counter is incremented by the number
requested E-RAB releases contained in the message.
REQUEST message to the MME, all E-RABs of the UE are released. In this case, the L.E-

RAB.AbnormRel.eNBTot counter is incremented each time the release cause is not "Normal
Release", "Detach", "User Inactivity", "CS Fallback triggered", "UE Not Available For PS
Service", "Inter-RAT Redirection", "Time Critical Handover", or "Handover Cancelled". If
multiple E-RABs of the UE are released, the L.E-RAB.AbnormRel.eNBTot counter is
incremented by the number of E-RAB releases. When the MME sends a UE CONTEXT
RELEASE COMMAND message to the eNodeB, the corresponding counter is not incremented.
REQUEST message to the MME, all E-RABs of the UE are released. In this case, the L.E-
RAB.AbnormRel.eNBTot counter is incremented each time the following two conditions are
met:
(1) The release cause is not "Normal Release", "Detach", "User Inactivity", "CS Fallback
triggered", "UE Not Available For PS Service", "Inter-RAT Redirection", "Time Critical
Handover", or "Handover Cancelled".
(2) The eNodeB determines that the E-RABs to be released carry data.
If multiple E-RABs of the UE are released, the L.E-RAB.AbnormRel.eNBTot counter is

incremented by the number of E-RAB releases. When the MME sends a UE CONTEXT
RELEASE COMMAND message to the eNodeB, the corresponding counter is not incremented.
Figure 2-58
Figure 2-59

Formula
None
Unit
None
Related Features
L.E-RAB.AbnormRel Multi-mode: None

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

Tot GSM: None
UMTS: None
2.2.6.6 Number of Abnormal E-RAB Releases for Different Causes in a Cell
Counters
Description

RAB.AbnormRel.Ra releases of activated BTS3900 LTE/
dio E-RABs because of BTS3900A LTE/
faults at the radio BTS3900L LTE/
network layer BTS3900AL LTE,
BTS3900

RAB.AbnormRel.T releases of activated BTS3900 LTE/
NL E-RABs because of BTS3900A LTE/
faults at the transport BTS3900L LTE/
network layer BTS3900AL LTE,
BTS3900


Description

RAB.AbnormRel.C releases of activated BTS3900 LTE/
ong E-RABs because of BTS3900A LTE/
network congestion BTS3900L LTE/
BTS3900AL LTE,
BTS3900

RAB.AbnormRel.H releases of activated BTS3900 LTE/
OFailure E-RABs because of BTS3900A LTE/
handover failures BTS3900L LTE/
BTS3900AL LTE,
BTS3900

RAB.AbnormRel.M releases of activated BTS3900 LTE/
ME E-RABs due to faults BTS3900A LTE/
on the MME side BTS3900L LTE/
BTS3900AL LTE,
BTS3900

RAB.AbnormRel.M abnormal E-RAB BTS3900 LTE/
METot releases due to faults BTS3900A LTE/
on the MME side BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of abnormal E-RAB releases based on the release cause in a
cell. An E-RAB is the access layer bearer for carrying service data of a UE. The E-RAB release
is a process of releasing the access layer bearer resources of UEs.
Measurement Points
As shown at point A in Figure 2-60, in an E-RAB release procedure initiated by the MME, the
L.E-RAB.AbnormRel.MMETot counter is incremented each time the eNodeB receives an E-
RAB RELEASE COMMAND message from the MME and the release cause is not "Normal
Release", "Detach, User Inactivity", "CS Fallback triggered", "UE Not Available for PS
Service", "Inter-RAT Redirection", or "Successful Handover". In addition, the L.E-
RAB.AbnormRel.MME counter is incremented each time the preceding condition is met and
the corresponding bearer carries data. If the E-RAB RELEASE COMMAND message requests
to release multiple E-RABs at the same time, the L.E-RAB.AbnormRel.MMETot and L.E-
RAB.AbnormRel.MME counters are incremented by the number of requested E-RAB releases
in the message.
As shown at point A in Figure 2-61, in a UE context release procedure initiated by the MME,
all E-RABs of the UE are released when the eNodeB receives a UE CONTEXT RELEASE

COMMAND message from the MME. In this case, the L.E-RAB.AbnormRel.MMETot counter
is incremented by the number of requested E-RAB releases in the message each time the release
cause is not "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered", "UE Not
Available for PS Service", "Inter-RAT Redirection", or "Successful Handover". In addition, the
L.E-RAB.AbnormRel.MME counter is incremented each time the preceding condition is met
and the corresponding bearer carries data.
As shown at point A in Figure 2-62, when the eNodeB sends an E-RAB RELEASE
INDICATION message to the MME, the counters are measured as follows:
(1) The L.E-RAB.AbnormRel.Radio counter is incremented each time the E-RAB is abnormally
released due to faults at the radio network layer and the eNodeB determines that the E-RAB to
be released carries data.
(2) The L.E-RAB.AbnormRel.TNL counter is incremented each time the E-RAB is abnormally
released due to faults at the transport network layer and the eNodeB determines that the E-RAB
to be released carries data.
(3) The L.E-RAB.AbnormRel.Cong counter is incremented each time the E-RAB is abnormally
released due to network congestion and the eNodeB determines that the E-RAB to be released
carries data.
For details about faults at the radio network layer and the transport network layer as well as
network congestion faults, see 3GPP TS 36.413. In addition, if the E-RAB RELEASE
INDICATION message requests to release multiple E-RABs at the same time, the corresponding
counter is incremented by the number of requested E-RAB releases based on the release cause.
REQUEST message to the MME, all E-RABs of the UE are released. The counters are measured
as follows:
(1) The L.E-RAB.AbnormRel.Radio counter is incremented each time the E-RABs are
abnormally released due to faults at the radio network layer and the eNodeB determines that the
E-RABs to be released carry data.
(2) The L.E-RAB.AbnormRel.TNL counter is incremented each time the E-RABs are
abnormally released due to faults at the transport network layer and the eNodeB determines that
the E-RABs to be released carry data.
(3) The L.E-RAB.AbnormRel.Cong counter is incremented each time the E-RABs are
abnormally released due to network congestion (including preemption and resource insufficient)
and the eNodeB determines that the E-RABs to be released carry data.
For details about faults at the radio network layer and the transport network layer as well as
network congestion faults, see 3GPP TS 36.413.
(4) The L.E-RAB.AbnormRel.HOFailure counter is incremented each time the E-RABs are
abnormally released due to handover failures and the eNodeB determines that the E-RABs to
be released carry data.
The corresponding counters are incremented by the number of requested E-RAB releases based
on the release cause. When the MME sends a UE CONTEXT RELEASE COMMAND message
to the eNodeB, the corresponding counter is not incremented.

Figure 2-60
Figure 2-61
Figure 2-62

Figure 2-63
Formula
None
Unit
None
Related Features
L.E-RAB.AbnormRel.Radio Multi-mode: None

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

GSM: None
UMTS: None

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

GSM: None
UMTS: None
LBFD-002024 Congestion Control
TDLBFD-002024 Congestion Control
LOFD-00102901 Radio/transport resource pre-
TDLOFD-00102901 emption
Radio/transport resource pre-
emption
L.E-RAB.AbnormRel.HO- Multi-mode: None

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

GSM: None
UMTS: None

RAB.AbnormRel.MMETot GSM: None
UMTS: None
2.2.6.7 Number of Released E-RABs of UEs in the Uplink Out-of-Synchronization

State

Counters
Description
1526728436 L.E- Number of released DBS3900 LTE/

RAB.Release.Unsyn E-RABs of UEs in BTS3900 LTE/
the uplink out-of- BTS3900A LTE/
synchronization state BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of released E-RABs of UEs in the uplink out-of-
synchronization state in a cell.
Measurement Points
As shown at point A in Figure 2-64, Figure 2-65, Figure 2-66, or Figure 2-67, when the UE
is in the uplink out-of-synchronization state, the L.E-RAB.Release.Unsyn counter is
incremented by 1 in any of the following scenarios:
- The eNodeB 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 2-64

Figure 2-65
Figure 2-66
Figure 2-67
Formula
None
Unit
None

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

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

RAB.Num.Syn2Un- RABs in UE contexts BTS3900 LTE/
syn when the UEs switch BTS3900A LTE/
from the uplink BTS3900L LTE/
synchronized state to BTS3900AL LTE,
the uplink out-of- BTS3900
synchronization state
in a cell
Description
The counter measures the total number of E-RABs of UEs when the UEs transit from the uplink-
synchronized state to the uplink out-of-synchronization state in a cell.
Measurement Points
When UEs transit from the uplink-synchronized state to the uplink out-of-synchronization state
in a cell, the total number of E-RABs contained in the UE contexts is used as the value of the
counter.
Formula
None
Unit
None

Related Features
L.E-RAB.Num.Syn2Unsyn Multi-mode: None

GSM: None
UMTS: None
2.2.6.9 Number of E-RAB Releases Initiated by the eNodeB in a Cell
Counters
Description

RAB.Rel.eNodeB.Q releases initiated by BTS3900 LTE/
CI.1 the eNodeB for BTS3900A LTE/
services with QCI of BTS3900L LTE/
1 in a cell BTS3900AL LTE,
BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

RAB.Rel.eNodeB RAB releases BTS3900 LTE/
initiated by the BTS3900A LTE/
eNodeB in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
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
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.
of each service each time the eNodeB sends the UE CONTEXT RELEASE REQUEST message
to the MME and all E-RABs of the UE are released. If multiple E-RABs of the UE have been
set up, the corresponding counter is incremented by the number of requested E-RAB releases
based on the QCI of each service.
Figure 2-68
Figure 2-69
Formula
None
Unit
None

Related Features
L.E-RAB.Rel.eNodeB.QCI. Multi-mode: None

1 GSM: None
UMTS: None

2 GSM: None
UMTS: None

3 GSM: None
UMTS: None

4 GSM: None
UMTS: None

5 GSM: None
UMTS: None

6 GSM: None
UMTS: None

7 GSM: None
UMTS: None


8 GSM: None
UMTS: None

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

GSM: None
UMTS: None
2.2.6.10 Number of E-RAB Releases Initiated by the MME in a Cell
Counters
Description

RAB.Rel.MME.QCI releases initiated by BTS3900 LTE/
.1 the MME for BTS3900A LTE/
BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description
1526728807 L.E-RAB.Rel.MME Total number of E- DBS3900 LTE/

RAB releases BTS3900 LTE/
initiated by the MME BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
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
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.
of each service each time the MME sends the UE CONTEXT RELEASE COMMAND message
to the eNodeB and all E-RABs of the UE are released. If multiple E-RABs of the UE have been
set up, the corresponding counter is incremented by the number of requested E-RAB releases
based on the QCI of each service.
Figure 2-70

Figure 2-71
Formula
None
Unit
None
Related Features
L.E-RAB.Rel.MME.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

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

GSM: None
UMTS: None

2.2.6.11 Number of Remaining E-RABs in a Cell
Counters
Description
1526728808 L.E-RAB.Left.QCI. Number of DBS3900 LTE/

1 remaining E-RABs BTS3900 LTE/
for services with QCI BTS3900A LTE/
BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900


Description

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900
1526728817 L.E-RAB.Left Total number of DBS3900 LTE/

remaining E-RABs BTS3900 LTE/
in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
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
Formula
None
Unit
None

Related Features
L.E-RAB.Left.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

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

GSM: None
UMTS: None
2.2.6.12 Number of E-RAB Releases Initiated by the eNodeB Because of the S1

RESET in a Cell
Counters
Description

RAB.Rel.S1Reset.e E-RAB releases BTS3900 LTE/
NodeB.QCI.1 initiated by the BTS3900A LTE/
eNodeB for services BTS3900L LTE/
with QCI of 1 BTS3900AL LTE,
because of the S1 BTS3900
RESET in a cell

RESET in a cell


Description

RESET in a cell

RESET in a cell

RESET in a cell

RESET in a cell

RESET in a cell

RESET in a cell


Description

RESET in a cell

RAB.Rel.S1Reset.e abnormal E-RAB BTS3900 LTE/
NodeB releases initiated by BTS3900A LTE/
the eNodeB because BTS3900L LTE/
of the S1 RESET in a BTS3900AL LTE,
cell BTS3900
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
of each service each time the eNodeB sends a S1 RESET message to the MME. If the S1 RESET
message request to release multiple E-RABs at the same time, the corresponding counter is
incremented by the number of requested E-RAB releases based on the QCI of each service. In
addition, the number of E-RAB releases initiated by the eNodeB because of the S1 RESET is
accumulated as the value of the L.E-RAB.Rel.S1Reset.eNodeB counter.
Figure 2-72

Formula
None
Unit
None
Related Features

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

QCI.2
UMTS: None

QCI.3
UMTS: None

QCI.4
UMTS: None

QCI.5
UMTS: None


QCI.6
UMTS: None

QCI.7
UMTS: None

QCI.8
UMTS: None

QCI.9
UMTS: None
L.E-RAB.Rel.S1Reset.eNo- Multi-mode: None

deB GSM: None
UMTS: None
2.2.6.13 Number of E-RAB Releases Initiated by the MME Because of the S1 RESET
in a Cell

Counters
Description

RAB.Rel.S1Reset.M E-RAB releases BTS3900 LTE/
ME.QCI.1 initiated by the MME BTS3900A LTE/
with QCI of 1 BTS3900L LTE/
because of the S1 BTS3900AL LTE,
RESET in a cell BTS3900








Description



RAB.Rel.S1Reset.M abnormal E-RAB BTS3900 LTE/
ME releases initiated by BTS3900A LTE/
the MME because of BTS3900L LTE/
the S1 RESET in a BTS3900AL LTE,
cell BTS3900
Description
The counters measure the number of E-RAB releases initiated by the MME for services with a
specific QCI ranging from 1 to 9 because of the S1 RESET in a cell. An E-RAB is the access
layer bearer for carrying service data of a UE. The E-RAB release is a process of releasing the
access layer bearer resources of UEs.
Measurement Points
of each service each time the MME sends a S1 RESET message to the eNodeB. If the S1 RESET
message requests to release multiple E-RABs at the same time, the corresponding counter is
incremented by the number of requested E-RAB releases based on the QCI of each service. In
addition, the number of E-RAB releases initiated by the MME because of the S1 RESET is
accumulated as the value of the L.E-RAB.Rel.S1Reset.MME counter.

Figure 2-73
Formula
None
Unit
None
Related Features

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

I.2
UMTS: None

I.3
UMTS: None


I.4
UMTS: None

I.5
UMTS: None

I.6
UMTS: None

I.7
UMTS: None

I.8
UMTS: None

I.9
UMTS: None

RAB.Rel.S1Reset.MME GSM: None
UMTS: None

2.2.7 Measurement related to E-RAB establish failure (E-

RAB.EstFail.Cell)
Overview
An E-RAB is an access layer bearer for carrying service data of users. The E-RAB setup success
rate in a cell directly represents the capability of the cell to provide E-RAB connections for users.
The E-RAB.EstFail.Cell function subset measures the number of E-RAB setup failures for
different causes in a cell. One E-RAB setup failure is counted once. Figure 2-74 shows the
measurement points in a failed E-RAB setup procedure.
Figure 2-74

Counters
Description

RAB.FailEst.NoRe- setup failures due to the mapping single-
ply no responses from mode base station
the UE in a cell version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

RAB.FailEst.MME setup failures due to the mapping single-
faults on the MME mode base station
side version that
introduce this
counter is:
eNodeB:V100R003
C00

RAB.FailEst.TNL setup failures due to the mapping single-
faults at the transport mode base station
network layer version that
introduce this
counter is:
eNodeB:V100R003
C00

RAB.FailEst.RNL setup failures due to the mapping single-
faults at the radio mode base station
network layer version that
introduce this
counter is:
eNodeB:V100R003
C00

RAB.FailEst.NoR- setup failures due to the mapping single-
adioRes insufficient radio mode base station
resources version that
introduce this
counter is:
eNodeB:V100R003
C00


Description

RAB.FailEst.Se- setup failures due to the mapping single-
curModeFail security mode mode base station
configuration version that
counter is:
eNodeB:V100R003
C00
Counter Sub Counter
L.E-RAB.FailEst.RNL L.E-RAB.FailEst.NoReply
L.E-RAB.FailEst.NoRadioRes
L.E-RAB.FailEst.SecurModeFail
2.2.7.1 Number of E-RAB Setup Failures for Different Causes in a Cell
Counters
Description

RAB.FailEst.NoRe- setup failures due to BTS3900 LTE/
ply no responses from BTS3900A LTE/
the UE in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900

RAB.FailEst.MME setup failures due to BTS3900 LTE/
faults on the MME BTS3900A LTE/
side BTS3900L LTE/
BTS3900AL LTE,
BTS3900

RAB.FailEst.TNL setup failures due to BTS3900 LTE/
faults at the transport BTS3900A LTE/
network layer BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

RAB.FailEst.RNL setup failures due to BTS3900 LTE/
faults at the radio BTS3900A LTE/
network layer BTS3900L LTE/
BTS3900AL LTE,
BTS3900

RAB.FailEst.NoRa- setup failures due to BTS3900 LTE/
dioRes insufficient radio BTS3900A LTE/
resources BTS3900L LTE/
BTS3900AL LTE,
BTS3900

RAB.FailEst.Secur- setup failures due to BTS3900 LTE/
ModeFail security mode BTS3900A LTE/
configuration BTS3900L LTE/
failures BTS3900AL LTE,
BTS3900
Description
The counters measure the number of E-RAB setup failures due to different causes in a cell. An
E-RAB is the access layer bearer for carrying service data of users. The E-RAB setup success
rate in a cell directly represents the capability of the cell to provide E-RAB connection setups
for users. The counters indicate the number of E-RAB setup failures due to different causes on
the network.
Measurement Points
During the initial UE context setup procedure or the E-RAB setup procedure, the corresponding
counter is incremented each time the E-RAB setup is failed due to faults on the MME side, faults
at the transport network layer, faults at the radio network layer, radio resource allocation failures,
security mode configuration failures, or no responses from the UE. The counters are measured
as follows:
As shown at point A in Figure 2-75, the L.E-RAB.FailEst.MME counter is incremented each
time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST message from the MME
but the message fails the validity check performed by the eNodeB, or the INITIAL CONTEXT
SETUP REQUEST message cannot be processed due to an interaction of the initial UE context
setup procedure and other S1AP-related procedures. If the INITIAL CONTEXT SETUP
REQUEST message requests to set up multiple E-RABs at the same time, the counter is
incremented by the number of requested E-RAB setups. A validity check failure may be caused
by an error in the message or a repeated E-RAB ID. A failure to process the message due to an
interaction of the initial UE context setup procedure and other S1AP-related procedures may
occur when the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the
MME during the UE context setup procedure.

As shown at point A in Figure 2-76, 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 fails the validity check performed by the eNodeB, or the INITIAL CONTEXT SETUP
REQUEST message cannot be processed due to an interaction of the initial UE context setup
procedure and other S1AP-related procedures. If the E-RAB SETUP REQUEST message
requests to set up multiple E-RABs at the same time, the counter is incremented by the number
of requested E-RAB setups. A validity check failure may be caused by an error in the message
or a repeated E-RAB ID. A failure to process the message due to an interaction of the 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 2-75, the corresponding counter is incremented each time the
eNodeB fails to set up the E-RAB and sends an INITIAL CONTEXT SETUP RESPONSE
message or an INITIAL CONTEXT SETUP FAILURE message to the MME after receiving an
INITIAL CONTEXT SETUP REQUEST message from the MME. The L.E-RAB.FailEst.TNL
counter is incremented each time the E-RAB setup failure is caused by faults at the transport
network layer. The L.E-RAB.FailEst.RNL counter is incremented each time the failure is caused
by faults at the radio network layer. For details about faults at the transport network layer and
the radio network layer, see 3GPP TS36.413. The L.E-RAB.FailEst.NoRadioRes counter is
incremented each time the failure is caused by insufficient radio resources. If there are multiple
E-RAB setup failures, the corresponding counter is incremented by the number of E-RAB setup
failures. The measuring conditions of the L.E-RAB.FailEst.RNL counter involve the measuring
conditions of the L.E-RAB.FailEst.NoRadioRes, L.E-RAB.FailEst.SecurModeFail, and L.E-
RAB.FailEst.NoReply counters.
eNodeB fails to set up the E-RAB and sends an E-RAB SETUP RESPONSE message to the
MME after receiving an E-RAB SETUP REQUEST message from the MME. The L.E-
RAB.FailEst.TNL counter is incremented each time the failure is caused by faults at the transport
network layer. The L.E-RAB.FailEst.RNL counter is incremented each time the failure is caused
by faults at the radio network layer. For details about faults at the transport network layer and
the radio network layer, see 3GPP TS36.413. The L.E-RAB.FailEst.NoRadioRes counter is
incremented each time the failure is caused by insufficient radio resources. If there are multiple
E-RAB setup failures, the corresponding counter is incremented by the number of E-RAB setup
failures. The measuring conditions of the L.E-RAB.FailEst.RNL counter involve the measuring
conditions of the L.E-RAB.FailEst.NoRadioRes, L.E-RAB.FailEst.SecurModeFail, and L.E-
RAB.FailEst.NoReply counters.
As shown at point A in Figure 2-77, the L.E-RAB.FailEst.SecurModeFail counter is

incremented each time the eNodeB sends a Security Mode Command message to the UE but
receives a Security Mode Failure message from the UE after receiving an INITIAL CONTEXT
SETUP REQUEST message from the MME. If the INITIAL CONTEXT SETUP REQUEST
message requires to set up multiple E-RABs at the same time, the counter is incremented by the
number of requested E-RAB setups.
As shown at points A, B, C, and D in Figure 2-78, the L.E-RAB.FailEst.NoReply counter is

incremented each time the eNodeB receives no responses from the UE before the corresponding
timer expires after sending an RRC signaling message to the UE during the initial UE context
setup procedure or the E-RAB setup procedure. If the INITIAL CONTEXT SETUP REQUEST
or E-RAB SETUP REQUEST message requests to set up multiple E-RABs at the same time,
the counter is incremented by the number of requested E-RAB setups.

Figure 2-75
Figure 2-76

Figure 2-77

Figure 2-78
Formula
None
Unit
None

Related Features
L.E-RAB.FailEst.NoReply Multi-mode: None

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

GSM: None
UMTS: None
L.E-RAB.FailEst.TNL Multi-mode: None

GSM: None
UMTS: None
L.E-RAB.FailEst.RNL Multi-mode: None

GSM: None
UMTS: None
LBFD-002023 Admission Control
TDLBFD-002023 Admission Control
L.E-RAB.FailEst.NoRa- Multi-mode: None

dioRes GSM: None
UMTS: None
LBFD-002023 Admission Control
L.E-RAB.FailEst.SecurMo- Multi-mode: None

deFail GSM: None
UMTS: None

2.2.8 Measurement related to E-RAB modify (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 2-79 shows the
measurement points in an E-RAB modification procedure.
Figure 2-79
Counters
Description

RAB.AttModify.Q modification the mapping single-
CI.1 attempts initiated by mode base station
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

RAB.SuccModify. successful E-RAB the mapping single-
QCI.1 modifications mode base station
initiated by UEs for version that
services with the QCI introduce this
of 1 in a cell counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

eNodeB:Version
earlier than
V100R003C00


Description

counter is:
eNodeB:Version
earlier than
V100R003C00

eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00


Description

eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

eNodeB:Version
earlier than
V100R003C00


Description

counter is:
eNodeB:Version
earlier than
V100R003C00

eNodeB:Version
earlier than
V100R003C00

RAB.AttModify RAB modification the mapping single-
attempts initiated by mode base station
introduce this
counter is:
eNodeB:V100R003
C00

RAB.SuccModify successful E-RAB the mapping single-
modifications mode base station
initiated by UEs in a version that
cell introduce this
counter is:
eNodeB:V100R003
C00

RAB.FailModify.N modification failures the mapping single-
oRadioRes due to insufficient mode base station
radio resources version that
introduce this
counter is:
eNodeB:V100R006
C00

Counter Sub Counter
L.E-RAB.AttModify L.E-RAB.AttModify.QCI.1
L.E-RAB.AttModify.QCI.2
L.E-RAB.SuccModify L.E-RAB.SuccModify.QCI.1
L.E-RAB.SuccModify.QCI.2
2.2.8.1 Number of E-RAB Modification Attempts in a Cell
Counters
Description

RAB.AttModify.QC modification BTS3900 LTE/
I.1 attempts initiated by BTS3900A LTE/
BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description
1526728248 L.E-RAB.AttModify Total number of E- DBS3900 LTE/

RAB modification BTS3900 LTE/
attempts initiated by BTS3900A LTE/
BTS3900AL LTE,
BTS3900
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
eNodeB receives an E-RAB MODIFY REQUEST message from the MME. If the E-RAB
MODIFY REQUEST message requests to modify multiple E-RABs at the same time, the
corresponding counter is incremented by the number of requested E-RAB modifications based
on the QCI of each service. In addition, the number of requested E-RAB modifications contained
in the E-RAB MODIFY REQUEST messages is accumulated as the value of the L.E-
RAB.AttModify counter.
Figure 2-80
Formula
None

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

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

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

GSM: None
UMTS: None
2.2.8.2 Number of Successful E-RAB Modifications in a Cell
Counters
Description

RAB.SuccModify.Q successful E-RAB BTS3900 LTE/
CI.1 modifications BTS3900A LTE/
initiated by UEs for BTS3900L LTE/
services with the QCI BTS3900AL LTE,
of 1 in a cell BTS3900


Description









Description


RAB.SuccModify successful E-RAB BTS3900 LTE/
modifications BTS3900A LTE/
initiated by UEs in a BTS3900L LTE/
cell BTS3900AL LTE,
BTS3900
Description
The counters measure the number of successful E-RAB modifications for each service with a
specific QCI ranging from 1 to 9 and the total number of successful E-RAB modifications in a
cell.
Measurement Points
As shown at point B in Figure 2-81, the corresponding counter is incremented each time the
eNodeB sends an E-RAB MODIFY RESPONSE message to the MME. If the E-RAB MODIFY
RESPONSE message indicates multiple successful E-RAB modifications at the same time, the
corresponding counter is incremented by the number of successful E-RAB modifications in the
message based on the QCI of each service. In addition, the number of successful E-RAB
modifications in the message is accumulated as the value of the L.E-RAB.SuccModify counter.

Figure 2-81
Formula
None
Unit
None
Related Features
L.E-RAB.SuccModify.QCI. Multi-mode: None

1 GSM: None
UMTS: None

2 GSM: None
UMTS: None


3 GSM: None
UMTS: None

4 GSM: None
UMTS: None

5 GSM: None
UMTS: None

6 GSM: None
UMTS: None

7 GSM: None
UMTS: None

8 GSM: None
UMTS: None

9 GSM: None
UMTS: None

L.E-RAB.SuccModify Multi-mode: None

GSM: None
UMTS: None
2.2.8.3 Number of E-RAB Modification Failures for Different Causes in a Cell
Counters
Description

RAB.FailModify.No modification failures BTS3900 LTE/
RadioRes due to insufficient BTS3900A LTE/
radio resources BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of E-RAB modification failures due to insufficient radio
resources in a cell. The eNodeB sends the E-RAB MODIFY RESPONSE message to inform the
MME of failure causes. For details, see 3GPP TS36.413.
Measurement Points
As shown at point B in Figure 2-82, when the eNodeB sends the E-RAB MODIFY RESPONSE
message to the MME, the L.E-RAB.FailModify.NoRadioRes counter is incremented if the
message indicates that the E-RAB fails to be modified and the modification failure is caused by
insufficient radio resources. If the E-RAB MODIFY RESPONSE message indicates multiple
E-RAB modification failures, this counter is incremented by the number of E-RAB modification
failures.

Figure 2-82
Formula
None
Unit
None
Related Features
L.E-RAB.FailModify.NoR- Multi-mode: None

adioRes GSM: None
UMTS: None
2.2.9 Measurement related to Cell Algorithm (Algo.Cell)
Overview
The Algo.Cell function subset measures the duration of cell unavailability and cell availability
and the measurements related to load control, including congestion times and duration.

Counters
Description
1526726760 L.LC.ULCong.Nu Number of times V100R008C00,and

m.Cell uplink congestion the mapping single-
occurs in a cell mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526726761 L.LC.ULCong.Dur Duration of uplink V100R008C00,and

.Cell congestion in a cell the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526726762 L.LC.DLCong.Nu Number of times V100R008C00,and

m.Cell downlink congestion the mapping single-
occurs in a cell mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526726763 L.LC.DLCong.Dur Duration of V100R008C00,and

.Cell downlink congestion the mapping single-
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526726764 L.LC.User.Rel Number of GBR V100R008C00,and

service releases due the mapping single-
to congestion in a cell mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727209 L.Cell.Unavail.Dur Duration of cell V100R008C00,and

.Sys unavailability due to the mapping single-
system faults mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

.Manual unavailability due to the mapping single-
human factors mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526728320 L.Cell.Avail.Dur Duration of cell V100R008C00,and

availability the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00
1526728465 L.Signal.Num.Uu Number of signaling V100R008C00,and

messages over the the mapping single-
Uu interface mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728466 L.Signal.Num.DRX Number of DRX V100R008C00,and

.Reconfig reconfiguration the mapping single-
messages mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728411 L.Voice.VQI.UL.E Number of times V100R008C00,and

xcellent.Times uplink voice quality the mapping single-
is Excellent mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728412 L.Voice.VQI.UL.G Number of times V100R008C00,and

ood.Times uplink voice quality the mapping single-
is Good mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728413 L.Voice.VQI.UL.A Number of times V100R008C00,and

ccept.Times uplink voice quality the mapping single-
is Accept mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728414 L.Voice.VQI.UL.P Number of times V100R008C00,and

oor.Times uplink voice quality the mapping single-
is Poor mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728415 L.Voice.VQI.UL.B Number of times V100R008C00,and

ad.Times uplink voice quality the mapping single-
is Bad mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728416 L.Voice.VQI.DL.E Number of times V100R008C00,and

xcellent.Times downlink voice the mapping single-
quality is Excellent mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728417 L.Voice.VQI.DL.G Number of times V100R008C00,and

ood.Times downlink voice the mapping single-
quality is Good mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728418 L.Voice.VQI.DL.A Number of times V100R008C00,and

ccept.Times downlink voice the mapping single-
quality is Accept mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728419 L.Voice.VQI.DL.P Number of times V100R008C00,and

oor.Times downlink voice the mapping single-
quality is Poor mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728420 L.Voice.VQI.DL.B Number of times V100R008C00,and

ad.Times downlink voice the mapping single-
quality is Bad mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728538 L.RRCRel.Dedicat Number of times that V100R008C00,and

edPri.LTE.High E-UTRAN is the mapping single-
configured as the mode base station
highest frequency version that
priority in an IMMCI introduce this
IE counter is:
eNodeB:V100R006
C00

edPri.WCDMA.Hi the WCDMA the mapping single-
gh network is mode base station
configured as the version that
highest frequency introduce this
priority in an IMMCI counter is:
IE eNodeB:V100R006
C00

edPri.GERAN.Hig GERAN is the mapping single-
h configured as the mode base station
highest frequency version that
priority in an IMMCI introduce this
IE counter is:
eNodeB:V100R006
C00
1526728444 L.Cell.UserLimit.P Number of V100R008C00,and

reEmp.Num successful the mapping single-
preemptions mode base station
triggered due to user version that
limitation introduce this
counter is:
eNodeB:V100R006
C00


Description

.EnergySaving unavailability due to the mapping single-
energy saving mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728494 L.Sps.UL.SchNum Number of uplink V100R008C00,and

semi-persistent the mapping single-
scheduling times in a mode base station
cell version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728495 L.Sps.DL.SchNum Number of downlink V100R008C00,and

semi-persistent the mapping single-
scheduling times in a mode base station
cell version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728562 L.Sps.UL.ErrNum Number of failed V100R008C00,and

uplink semi- the mapping single-
persistent scheduling mode base station
transmissions in a version that
cell introduce this
counter is:
eNodeB:V100R006
C00
1526728563 L.Sps.DL.ErrNum Number of failed V100R008C00,and

downlink semi- the mapping single-
persistent scheduling mode base station
transmission in a cell version that
introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728547 L.Cdrx.Enter.Num Number of times a V100R008C00,and

UE in connected the mapping single-
mode enters DRX in mode base station
RRC_CONECTED version that
mode introduce this
counter is:
eNodeB:V100R006
C00
1526728548 L.Cdrx.Exit.Num Number of times a V100R008C00,and

UE in connected the mapping single-
mode exits DRX in mode base station
RRC_CONECTED version that
mode introduce this
counter is:
eNodeB:V100R006
C00
1526728549 L.Cdrx.Active.Tti- Total number of TTIs V100R008C00,and

Num for DRX UEs in the mapping single-
active state mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728550 L.Cdrx.Sleep.Tti- Total number of TTIs V100R008C00,and

Num for DRX UEs in the mapping single-
sleep state mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728551 L.Voip.Cdrx.Active Total number of TTIs V100R008C00,and

.TtiNum for DRX UEs in the mapping single-
active state and mode base station
performing VoIP version that
services introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728552 L.Voip.Cdrx.Sleep. Total number of TTIs V100R008C00,and

TtiNum for DRX UEs in the mapping single-
dormant state and mode base station
performing VoIP version that
services introduce this
counter is:
eNodeB:V100R006
C00
None
2.2.9.1 Number of Times Uplink or Downlink Congestion Occurs in a Cell
Counters
Description
1526726760 L.LC.ULCong.Num. Number of times DBS3900 LTE/

Cell uplink congestion BTS3900 LTE/
occurs in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526726762 L.LC.DLCong.Num. Number of times DBS3900 LTE/

Cell downlink congestion BTS3900 LTE/
occurs in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of times that uplink or downlink congestion occurs in a cell
after the congestion control feature is enabled.
Measurement Points
After the congestion control feature is enabled, the corresponding counter is incremented by 1
each time uplink or downlink congestion occurs in a cell. If the cell is in RAN sharing mode,
the corresponding counter is incremented by the number of times that uplink or downlink
congestion occurs for each operator.

Formula
None
Unit
None
Related Features
L.LC.ULCong.Num.Cell Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002024 Congestion Control
L.LC.DLCong.Num.Cell Multi-mode: None

GSM: None
UMTS: None
2.2.9.2 Duration of Uplink or Downlink Congestion in a Cell
Counters
Description
1526726761 L.LC.ULCong.Dur. Duration of uplink DBS3900 LTE/

Cell congestion in a cell BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526726763 L.LC.DLCong.Dur. Duration of DBS3900 LTE/

Cell downlink congestion BTS3900 LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
The counters measure the duration of downlink and uplink congestion in a cell after the
congestion control feature is enabled.
Measurement Points
The uplink and downlink congestion status are sampled per five seconds. If the cell is in uplink
or downlink congestion, the corresponding counter is incremented by 5 at that sampling point.
At the end of a measurement period, the accumulated counter values are reported. A deviation
of one sampling period may exist in the sampling timer when the timer performs time
synchronization. As a result, a deviation of one sampling period will also be generated in the
value of this counter, which affects the values of the KPIs that are calculated by using this
counter. The effects vary with the deviation in the value of the counter and calculation formulas
for the KPIs. If the cell is in RAN sharing mode and the uplink or downlink for a specified
operator is in congestion, the whole cell is in uplink or downlink congestion, respectively.
Formula
None
Unit
s
Related Features
L.LC.ULCong.Dur.Cell Multi-mode: None

GSM: None
UMTS: None
L.LC.DLCong.Dur.Cell Multi-mode: None

GSM: None
UMTS: None
2.2.9.3 Number of Service Releases due to Congestion in a Cell

Counters
Description
1526726764 L.LC.User.Rel Number of GBR DBS3900 LTE/

service releases due BTS3900 LTE/
to congestion in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of times that a GBR service is released due to congestion in
a cell.
Measurement Points
The counter is incremented by 1 each time a GBR service is released due to congestion in a cell.
Formula
None
Unit
None
Related Features
L.LC.User.Rel Multi-mode: None

GSM: None
UMTS: None
2.2.9.4 Duration of Cell Unavailability

Counters
Description
1526727209 L.Cell.Unavail.Dur. Duration of cell DBS3900 LTE/

Sys unavailability due to BTS3900 LTE/
system faults BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Manual unavailability due to BTS3900 LTE/
human factors BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

EnergySaving unavailability due to BTS3900 LTE/
energy saving BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the duration of cell unavailability due to human operations, system faults,
or energy saving.
Human operations include blocking and deactivating a cell by using MML commands (BLK
CELL and DEA CELL, respectively). System faults include board faults, faults on a CPRI link,
faults on the LBBP carrying services of the cell, faults on TX or RX channels of an RF module,
unavailability of control-plane transmission resources (S1 links), unavailability of user-plane
transmission resources (IP paths), insufficiency of license resources, unavailability of clocks, or
running the BLK BRD, RST BRD, or RST BTSNODE command. Energy saving includes RF
module regular time sleep, the cell entering intelligent power-off of carriers in the same coverage
mode, intelligent power-off of carriers in the same coverage of UMTS network mode, or cell
shutdown in low power consumption mode.
Measurement Points
The duration of cell unavailability is sampled per five seconds. If a cell is unavailable, the
corresponding counter is incremented by 5 at that sampling point.At the end of a measurement
period, the sum of these sampling results is reported.A deviation of one sampling period may
exist in the sampling timer when the timer performs time synchronization. As a result, a deviation
of one sampling period will also be generated in the value of the counters, which affects the
values of the KPIs that are calculated by using the counters. The effects vary depending on the
deviation in the value of the counters and calculation formulas for the KPIs.

Formula
None
Unit
s
Related Features
L.Cell.Unavail.Dur.Sys None None
L.Cell.Unavail.Dur.Manual None None
L.Cell.Unavail.Dur.Energy- Multi-mode: None

Saving GSM: None
UMTS: None
LTE: LOFD-001025 Adaptive Power
LOFD-001040 Consumption
LOFD-001042 Low Power Consumption

Mode
LOFD-001074
Intelligent Power-Off of
TDLOFD-001042 Carriers in the Same
TDLOFD-001040 Coverage
Carriers in the Coverage of
GSM/UMTS Network
Carriers in the Same
Coverage
Low Power Consumption
Mode
2.2.9.5 Duration of Cell Availability

Counters
Description
1526728320 L.Cell.Avail.Dur Duration of cell DBS3900 LTE/

availability BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the availability duration of a cell.
Measurement Points
The duration of cell availability in a cell is sampled per five seconds. If the cell is available, the
counter is incremented by 5 at that sampling point. At the end of a measurement period, the sum
of these sampling results is reported. A deviation of one sampling period may exist in the
sampling timer when the timer performs time synchronization. As a result, a deviation of one
sampling period will also be generated in the value of the counter, which affects the values of
the KPIs that are calculated by using the counter. The effects vary depending on the deviation
in the value of the counter and calculation formulas for the KPIs.
Formula
None
Unit
s
Related Features
None
2.2.9.6 Number of Signaling Messages over the Uu Interface

Counters
Description
1526728465 L.Signal.Num.Uu Number of signaling DBS3900 LTE/

messages over the BTS3900 LTE/
Uu interface BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of UE level signaling messages including the non-access
stratum (NAS) messages over the Uu interface in a cell.
Measurement Points
The L.Signal.Num.Uu counter is incremented by 1 each time the eNodeB receives or sends a
UE-level air interface signaling message, including a non-access stratum (NAS) message in a
cell.
Formula
None
Unit
None
Related Features
L.Signal.Num.Uu Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002017 DRX
TDLBFD-002017 DRX
2.2.9.7 Number of DRX Reconfiguration Messages

Counters
Description
1526728466 L.Signal.Num.DRX. Number of DRX DBS3900 LTE/

Reconfig reconfiguration BTS3900 LTE/
messages BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of RRC Connection Reconfiguration messages sent in a cell
to reconfigure DRX. DRX reconfiguration includes DRX activation, DRX deactivation, or DRX
parameter reconfiguration.
Measurement Points
The L.Signal.Num.DRX.Reconfig counter is incremented by 1 each time the eNodeB sends an
RRC Connection Reconfiguration message to the UE to reconfigure DRX.
Formula
None
Unit
None
Related Features
L.Signal.Num.DRX.Recon- Multi-mode: None

fig GSM: None
UMTS: None
TDLBFD-002017 DRX
LOFD-001105 Dynamic DRX
2.2.9.8 Uplink or Downlink Voice Quality in a Cell

Counters
Description
1526728411 L.Voice.VQI.UL.Ex Number of times DBS3900 LTE/

cellent.Times uplink voice quality BTS3900 LTE/
is Excellent BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728412 L.Voice.VQI.UL.Go Number of times DBS3900 LTE/

od.Times uplink voice quality BTS3900 LTE/
is Good BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728413 L.Voice.VQI.UL.Ac Number of times DBS3900 LTE/

cept.Times uplink voice quality BTS3900 LTE/
is Accept BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728414 L.Voice.VQI.UL.Po Number of times DBS3900 LTE/

or.Times uplink voice quality BTS3900 LTE/
is Poor BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728415 L.Voice.VQI.UL.Ba Number of times DBS3900 LTE/

d.Times uplink voice quality BTS3900 LTE/
is Bad BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728416 L.Voice.VQI.DL.Ex Number of times DBS3900 LTE/

cellent.Times downlink voice BTS3900 LTE/
quality is Excellent BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728417 L.Voice.VQI.DL.Go Number of times DBS3900 LTE/

od.Times downlink voice BTS3900 LTE/
quality is Good BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1526728418 L.Voice.VQI.DL.Ac Number of times DBS3900 LTE/

cept.Times downlink voice BTS3900 LTE/
quality is Accept BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728419 L.Voice.VQI.DL.Po Number of times DBS3900 LTE/

or.Times downlink voice BTS3900 LTE/
quality is Poor BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728420 L.Voice.VQI.DL.Ba Number of times DBS3900 LTE/

d.Times downlink voice BTS3900 LTE/
quality is Bad BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure uplink and downlink voice quality.
Measurement Points
The voice quality can be classified into Bad, Poor, Accept, Good or Excellent. The uplink and
downlink voice quality is sampled per 2.5 second in an available cell. A corresponding counter
is incremented by 1 each time the voice quality is sampled. At the end of a measurement period,
the accumulated result is used as the value of the corresponding counter.
Formula
None
Unit
None

Related Features
L.Voice.VQI.UL.Excellent. Multi-mode: None

Times GSM: None
UMTS: None
LTE: LBFD-004008 Performance Management
L.Voice.VQI.UL.Good.Tim Multi-mode: None

es GSM: None
UMTS: None
L.Voice.VQI.UL.Accept.Ti Multi-mode: None

mes GSM: None
UMTS: None
L.Voice.VQI.UL.Poor.Time Multi-mode: None

s 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.Tim Multi-mode: None

es GSM: None
UMTS: None
L.Voice.VQI.DL.Accept.Ti Multi-mode: None

mes GSM: None
UMTS: None

L.Voice.VQI.DL.Poor.Time Multi-mode: None

s GSM: None
UMTS: None
L.Voice.VQI.DL.Bad.Times Multi-mode: None

GSM: None
UMTS: None
2.2.9.9 Number of Times that E-UTRAN is Configured as the Highest Frequency

Priority in an IMMCI IE
Counters
Description
1526728538 L.RRCRel.Dedicate Number of times that DBS3900 LTE/

dPri.LTE.High E-UTRAN is BTS3900 LTE/
configured as the BTS3900A LTE/
highest frequency BTS3900L LTE/
priority in an IMMCI BTS3900AL LTE,
IE BTS3900
Description
The counter measure the times that an RRC Connection Release message contains an
idleModeMobilityControlInfo IE in which E-UTRAN is configured as the highest frequency
priority in a cell.
Measurement Points
As shown at point A in Figure 2-83, the L.RRCRel.DedicatedPri.LTE.High counter is
incremented by 1 each time the eNodeB sends an RRC Connection Release message to the UE
and the message contains an idleModeMobilityControlInfo IE in which the E-UTRAN is
configured as the highest frequency priority in a cell.

Figure 2-83
Formula
None
Unit
None
Related Features
L.RRCRel.DedicatedPri.LT Multi-mode: None

E.High GSM: None
UMTS: None
LTE: LOFD-00105401 Camp & Handover Based on
TDLOFD-00105401 SPID
LOFD-001112 Camp & Handover Based on

SPID
MOCN Flexible Priority
Based Camping
2.2.9.10 Number of Times that the WCDMA Network is Configured as the Highest
Frequency Priority in an IMMCI IE

Counters
Description

dPri.WCDMA.High the WCDMA BTS3900 LTE/
network is BTS3900A LTE/
configured as the BTS3900L LTE/
highest frequency BTS3900AL LTE,
priority in an IMMCI BTS3900
IE
Description
The counter measures the times that an RRC Connection Release message contains an
idleModeMobilityControlInfo IE in which the WCDMA network is configured with the highest
frequency priority in a cell.
Measurement Points
As shown at point A in Figure 2-84, the L.RRCRel.DedicatedPri.WCDMA.High counter is
and the message contains an idleModeMobilityControlInfo IE in which the WCDMA network
is configured as the highest frequency priority in a cell.
Figure 2-84
Formula
None
Unit
None

Related Features
L.RRCRel.DedicatedPri.W Multi-mode: None

CDMA.High GSM: None
UMTS: None

SPID
TDLOFD-001044
LOFD-001112 UTRAN
UTRAN
Based Camping
2.2.9.11 Number of Times that GERAN is Configured as the Highest Frequency

Priority in an IMMCI IE
Counters
Description

dPri.GERAN.High GERAN is BTS3900 LTE/
configured as the BTS3900A LTE/
highest frequency BTS3900L LTE/
priority in an IMMCI BTS3900AL LTE,
IE BTS3900
Description
The counter measure the times that an RRC Connection Release message contains an
idleModeMobilityControlInfo IE in which GERAN is configured as the highest frequency
priority in a cell.
Measurement Points
As shown at point A in Figure 2-85, the L.RRCRel.DedicatedPri.GERAN.High counter is
and the message contains an idleModeMobilityControlInfo IE in which the GERAN is
configured as the highest frequency priority in a cell.

Figure 2-85
Formula
None
Unit
None
Related Features
L.RRCRel.DedicatedPri.GE Multi-mode: None

RAN.High GSM: None
UMTS: None

SPID
Based Camping
2.2.9.12 Number of Successful Preemptions Triggered due to User Limitation

Counters
Description
1526728444 L.Cell.UserLimit.Pr Number of DBS3900 LTE/

eEmp.Num successful BTS3900 LTE/
preemptions BTS3900A LTE/
triggered due to user BTS3900L LTE/
limitation BTS3900AL LTE,
BTS3900
Description
The counter measures the number of successful inter-operator or intra-operator preemptions
triggered due to user limitation.
Measurement Points
The L.Cell.UserLimit.PreEmp.Num counter is incremented by 1 each time an inter-operator or
intra-operator preemption triggered due to user limitation is successfully executed.
Formula
None
Unit
None
Related Features
L.Cell.UserLimit.PreEmp.N Multi-mode: None

um GSM: None
UMTS: None
LTE: LOFD-00102901 Radio/transport resource pre-
emption
2.2.9.13 Number of Semi-Persistent Scheduling Times in a cell

Counters
Description
1526728494 L.Sps.UL.SchNum Number of uplink DBS3900 LTE/

semi-persistent BTS3900 LTE/
scheduling times in a BTS3900A LTE/
cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728495 L.Sps.DL.SchNum Number of downlink DBS3900 LTE/

semi-persistent BTS3900 LTE/
scheduling times in a BTS3900A LTE/
cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of uplink or downlink semi-persistent scheduling times
performed in a cell.
Measurement Points
The corresponding counter is incremented by 1 each time VoIP services use uplink or downlink
semi-persistent scheduling in a cell.
The internal timer of the eNodeB has a deviation of one period, and therefore the measurement
result of the counter has a deviation.
Formula
None
Unit
None

Related Features
L.Sps.UL.SchNum Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001016 VoIP Semi-persistent
TDLOFD-001016 Scheduling
VoIP Semi-persistent
Scheduling
L.Sps.DL.SchNum Multi-mode: None

GSM: None
UMTS: None
Scheduling
2.2.9.14 Number of Failed Semi-Persistent Scheduling Transmissions in a Cell
Counters
Description
1526728562 L.Sps.UL.ErrNum Number of failed DBS3900 LTE/

uplink semi- BTS3900 LTE/
persistent scheduling BTS3900A LTE/
transmissions in a BTS3900L LTE/
cell BTS3900AL LTE,
BTS3900
1526728563 L.Sps.DL.ErrNum Number of failed DBS3900 LTE/

downlink semi- BTS3900 LTE/
persistent scheduling BTS3900A LTE/
transmission in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of times the transmission of uplink or downlink semi-
persistent scheduling fails in a cell.

Measurement Points
The corresponding counter is incremented by 1 each time the transmission of uplink or downlink
semi-persistent scheduling for VoIP services fails in a cell.
Formula
None
Unit
None
Related Features
L.Sps.UL.ErrNum Multi-mode: None

GSM: None
UMTS: None
Scheduling
L.Sps.DL.ErrNum Multi-mode: None

GSM: None
UMTS: None
Scheduling
2.2.9.15 Number of Times a UE in Connected Mode Enters DRX in

RRC_CONECTED Mode

Counters
Description
1526728547 L.Cdrx.Enter.Num Number of times a DBS3900 LTE/

UE in connected BTS3900 LTE/
mode enters DRX in BTS3900A LTE/
RRC_CONECTED BTS3900L LTE/
mode BTS3900AL LTE,
BTS3900
Description
The counter measures the number of times that the UE enters the discontinuous reception (DRX)
in RRC_CONNECTED mode. DRX in RRC_CONNECTED mode does not include out-of-
synchronization DRX.
Measurement Points
The L.Cdrx.Enter.Num counter is incremented by 1 each time the eNodeB sends an RRC
Connection Reconfiguration message to the UE in connected mode, instructing the UE to enter
the DRX in RRC_CONNECTED mode.
Formula
None
Unit
None
Related Features
L.Cdrx.Enter.Num Multi-mode: None

GSM: None
UMTS: None
TDLBFD-002017 DRX

2.2.9.16 Number of Times a UE in Connected Mode Exits DRX in RRC_CONECTED

Mode
Counters
Description
1526728548 L.Cdrx.Exit.Num Number of times a DBS3900 LTE/

UE in connected BTS3900 LTE/
mode exits DRX in BTS3900A LTE/
RRC_CONECTED BTS3900L LTE/
mode BTS3900AL LTE,
BTS3900
Description
The counter measures the number of times the UE exits discontinuous reception (DRX) in
RRC_CONNECTED mode.
Measurement Points
The L.Cdrx.Exit.Num counter is incremented by 1 each time the eNodeB sends an RRC
Connection Reconfiguration message to the UE in connected mode to inform the UE to exit
DRX in RRC_CONNECTED mode.
Formula
None
Unit
None
Related Features
L.Cdrx.Exit.Num Multi-mode: None

GSM: None
UMTS: None
TDLBFD-002017 DRX

2.2.9.17 DRX Duration
Counters
Description
1526728549 L.Cdrx.Active.Tti- Total number of TTIs DBS3900 LTE/

Num for DRX UEs in BTS3900 LTE/
active state BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728550 L.Cdrx.Sleep.Tti- Total number of TTIs DBS3900 LTE/

Num for DRX UEs in BTS3900 LTE/
sleep state BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728551 L.Voip.Cdrx.Active. Total number of TTIs DBS3900 LTE/

TtiNum for DRX UEs in BTS3900 LTE/
active state and BTS3900A LTE/
performing VoIP BTS3900L LTE/
services BTS3900AL LTE,
BTS3900
1526728552 L.Voip.Cdrx.Sleep. Total number of TTIs DBS3900 LTE/

TtiNum for DRX UEs in BTS3900 LTE/
dormant state and BTS3900A LTE/
performing VoIP BTS3900L LTE/
services BTS3900AL LTE,
BTS3900
Description
The counters measure the numbers of transmission time intervals (TTIs) for the following UEs:
- UEs in the DRX active state
- UEs in the DRX sleep state
- UEs in the DRX active state while performing VoIP services
- UEs in the DRX sleep state while performing VoIP services
Measurement Points
The total number of TTIs for UEs in active state, in active state while performing VoIP services,
in sleep state, or in sleep state while performing VoIP services after entering the DRX mode is

sampled per TTI. At the end of a measurement period, the sum of these sampling results is used
as the value of the corresponding counter.
Formula
None
Unit
None
Related Features
L.Cdrx.Active.TtiNum Multi-mode: None

GSM: None
UMTS: None
LBFD-002017 DRX
TDLBFD-002017 DRX
L.Cdrx.Sleep.TtiNum Multi-mode: None

GSM: None
UMTS: None
LBFD-002017 DRX
TDLBFD-002017 DRX
L.Voip.Cdrx.Active.TtiNum Multi-mode: None

GSM: None
UMTS: None
LBFD-002017 DRX
TDLBFD-002017 DRX

L.Voip.Cdrx.Sleep.TtiNum Multi-mode: None

GSM: None
UMTS: None
LBFD-002017 DRX
TDLBFD-002017 DRX
2.2.10 Measurement related to DRB (Traffic.DRB.Cell)
Overview
The Traffic.DRB.Cell function subset measures the number of Data Radio Bearers (DRBs) for
services with a specific QCI in a cell.
Counters
Description
1526726767 L.Traffic.DRB.QCI Number of DRBs for V100R008C00,and

.1 services with the QCI the mapping single-
of 1 in a cell mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526728258 L.Traffic.DRB Number of DRBs in V100R008C00,and

a cell the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R003
C00
Counter Sub Counter
L.Traffic.DRB L.Traffic.DRB.QCI.1
L.Traffic.DRB.QCI.2
L.Traffic.DRB.QCI.3
L.Traffic.DRB.QCI.4
L.Traffic.DRB.QCI.5
L.Traffic.DRB.QCI.6
L.Traffic.DRB.QCI.7
L.Traffic.DRB.QCI.8
L.Traffic.DRB.QCI.9

2.2.10.1 Number of DRBs in a Cell
Counters
Description
1526726767 L.Traffic.DRB.QCI. Number of DRBs for DBS3900 LTE/

1 services with the QCI BTS3900 LTE/
of 1 in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728258 L.Traffic.DRB Number of DRBs in DBS3900 LTE/

a cell BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
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
Formula
None
Unit
None

Related Features
L.Traffic.DRB.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None
L.Traffic.DRB Multi-mode: None

GSM: None
UMTS: None
2.2.11 Measurement related to Thruput (Traffic.Thruput.Cell)
Overview
The Traffic.Thruput.Cell function subset measures the uplink or downlink throughput of services
with a specific QCI in a cell and the duration of data transmission.
Counters
Description
1526726776 L.Thrp.bits.UL.QC Uplink traffic V100R008C00,and

I.1 volume for PDCP the mapping single-
SDUs of services mode base station
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526726777 L.Thrp.Time.UL.Q Receive duration of V100R008C00,and

CI.1 uplink PDCP SDUs the mapping single-
for services with the mode base station
QCI of 1 in a cell version that
introduce this
counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:Version
earlier than
V100R003C00

introduce this
counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:Version
earlier than
V100R003C00

introduce this
counter is:
eNodeB:V100R003
C00


Description

counter is:
eNodeB:Version
earlier than
V100R003C00

introduce this
counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:Version
earlier than
V100R003C00

introduce this
counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:Version
earlier than
V100R003C00


Description

introduce this
counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:Version
earlier than
V100R003C00

introduce this
counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:Version
earlier than
V100R003C00

introduce this
counter is:
eNodeB:V100R003
C00


Description

counter is:
eNodeB:Version
earlier than
V100R003C00

introduce this
counter is:
eNodeB:V100R003
C00
1526726803 L.Thrp.bits.DL.QC Downlink traffic V100R008C00,and

counter is:
eNodeB:Version
earlier than
V100R003C00
1526726804 L.Thrp.Time.DL.Q Transmit duration of V100R008C00,and

CI.1 downlink PDCP the mapping single-
SDUs for services mode base station
counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:Version
earlier than
V100R003C00


Description

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:V100R003
C00


Description

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:Version
earlier than
V100R003C00


Description

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:V100R003
C00


Description
1526727045 L.Thrp.bits.UL.QC Maximum uplink V100R008C00,and

I.1.Max traffic volume for the mapping single-
PDCP SDUs of mode base station
counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00


Description

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00
1526727054 L.Thrp.bits.UL.Ma Maximum uplink V100R008C00,and

x traffic volume for the mapping single-
PDCP SDUs of all mode base station
services version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526727055 L.Thrp.bits.DL.QC Maximum downlink V100R008C00,and

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00


Description

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00

counter is:
eNodeB:Version
earlier than
V100R003C00
1526727064 L.Thrp.bits.DL.Ma Maximum downlink V100R008C00,and

x traffic volume for the mapping single-
PDCP SDUs of all mode base station
services version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526728178 L.Thrp.bits.DL.SR Total Bits of V100R008C00,and

B Transmitted the mapping single-
Signaling SDUs on mode base station
SRBs at the PDCP version that
Layer introduce this
counter is:
eNodeB:V100R003
C00
1526728179 L.Thrp.bits.UL.SR Total Bits of V100R008C00,and

B Received Signaling the mapping single-
SDUs on SRBs at the mode base station
PDCP Layer version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728232 L.Thrp.Time.Cell. Total duration of V100R008C00,and

DL downlink data the mapping single-
transmission in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R003
C00

UL uplink data the mapping single-
transmission in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728234 L.E- Duration of data V100R008C00,and

RAB.SessionTime. transmission for the mapping single-
QCI1 services with the QCI mode base station
introduce this
counter is:
eNodeB:V100R003
C00


Description

introduce this
counter is:
eNodeB:V100R003
C00

introduce this
counter is:
eNodeB:V100R003
C00

introduce this
counter is:
eNodeB:V100R003
C00

introduce this
counter is:
eNodeB:V100R003
C00

introduce this
counter is:
eNodeB:V100R003
C00


Description

introduce this
counter is:
eNodeB:V100R003
C00

introduce this
counter is:
eNodeB:V100R003
C00

introduce this
counter is:
eNodeB:V100R003
C00
1526728243 L.E- Total duration of UE V100R008C00,and

RAB.SessionTime. data transmission the mapping single-
UE time in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728259 L.Thrp.bits.UL Total uplink traffic V100R008C00,and

volume for PDCP the mapping single-
SDUs in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R003
C00


Description
1526728260 L.Thrp.Time.UL Total receive V100R008C00,and

duration of uplink the mapping single-
PDCP SDUs in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728261 L.Thrp.bits.DL Total downlink V100R008C00,and

traffic volume for the mapping single-
version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728262 L.Thrp.Time.DL Total transmit V100R008C00,and

duration of downlink the mapping single-
version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728475 L.Thrp.bits.UL.CE Total bits of user data V100R008C00,and

U received at the PDCP the mapping single-
layer from cell edge mode base station
UEs (CEUs) in a cell version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728476 L.Thrp.Time.UL.C Total duration in V100R008C00,and

EU which user data from the mapping single-
cell edge UEs mode base station
(CEUs) is received at version that
the PDCP layer in a introduce this
cell counter is:
eNodeB:V100R006
C00


Description
1526728477 L.Thrp.bits.DL.CE Total bits of user data V100R008C00,and

U transmitted at the the mapping single-
PDCP layer to cell mode base station
edge UEs (CEUs) in version that
counter is:
eNodeB:V100R006
C00
1526728478 L.Thrp.Time.DL.C Total duration in V100R008C00,and

EU which user data is the mapping single-
transmitted to cell mode base station
edge UEs (CEUs) at version that
cell counter is:
eNodeB:V100R006
C00
1526728564 L.Thrp.bits.DL.CA Total volume of V100R008C00,and

User downlink data the mapping single-
transmitted to mode base station
activated CA UEs at version that
cell counter is:
eNodeB:V100R006
C00
1526728565 L.Thrp.Time.DL.C Total duration for V100R008C00,and

AUser activated CA UEs the mapping single-
transmitting mode base station
downlink data at the version that
PDCP layer in a cell introduce this
counter is:
eNodeB:V100R006
C00

DL.HighPrecision downlink data the mapping single-
transmission with the mode base station
precision of 1 version that
millisecond in a cell introduce this
counter is:
eNodeB:V100R003
C00


Description

UL.HighPrecision uplink data the mapping single-
transmission with the mode base station
precision of 1 version that
millisecond in a cell introduce this
counter is:
eNodeB:V100R003
C00
1526729005 L.Thrp.bits.DL.Las Downlink traffic V100R008C00,and

tTTI volume sent in the the mapping single-
last TTI before the mode base station
buffer is empty version that
introduce this
counter is:
eNodeB:V100R005
C00

tTTI.QCI.1 volume sent in the the mapping single-
last TTI for services mode base station
with the QCI 1 before version that
the buffer is empty introduce this
counter is:
eNodeB:V100R005
C00

counter is:
eNodeB:V100R005
C00

counter is:
eNodeB:V100R005
C00


Description

counter is:
eNodeB:V100R005
C00

counter is:
eNodeB:V100R005
C00

counter is:
eNodeB:V100R005
C00

counter is:
eNodeB:V100R005
C00

counter is:
eNodeB:V100R005
C00


Description

counter is:
eNodeB:V100R005
C00
1526729015 L.Thrp.Time.DL.R Data transmit V100R008C00,and

mvLastTTI duration except the the mapping single-
downlink buffer is version that
empty introduce this
counter is:
eNodeB:V100R005
C00

mvLastTTI.QCI.1 duration except the the mapping single-
empty for services introduce this
with the QCI 1 counter is:
eNodeB:V100R005
C00

eNodeB:V100R005
C00

eNodeB:V100R005
C00


Description

eNodeB:V100R005
C00

eNodeB:V100R005
C00

eNodeB:V100R005
C00

eNodeB:V100R005
C00

eNodeB:V100R005
C00


Description

eNodeB:V100R005
C00
1526729049 L.Thrp.bits.UE.UL Traffic volume of V100R008C00,and

.LastTTI uplink PDCP SDUs the mapping single-
sent in the last TTI mode base station
before the UE buffer version that
is empty introduce this
counter is:
eNodeB:V100R003
C00
1526729050 L.Thrp.Time.UE.U Uplink data transmit V100R008C00,and

L.RmvLastTTI duration except the the mapping single-
UE buffer is empty version that
introduce this
counter is:
eNodeB:V100R003
C00
1526729415 L.Thrp.bits.UE.UL Uplink traffic V100R008C00,and

.SmallPkt volume of PDCP the mapping single-
SDUs scheduled for mode base station
small packets version that
introduce this
counter is:
eNodeB:V100R006
C00
1526729416 L.Thrp.Time.UE.U Uplink data V100R008C00,and

L.RmvSmallPkt transmission the mapping single-
duration except that mode base station
for small packets version that
introduce this
counter is:
eNodeB:V100R006
C00

Counter Sub Counter
L.Thrp.bits.UL L.Thrp.bits.UL.QCI.1
L.Thrp.bits.UL.QCI.2
L.Thrp.Time.UL L.Thrp.Time.UL.QCI.1
L.Thrp.Time.UL.QCI.2
L.Thrp.bits.DL L.Thrp.bits.DL.QCI.1
L.Thrp.bits.DL.QCI.2
L.Thrp.Time.DL L.Thrp.Time.DL.QCI.1
L.Thrp.Time.DL.QCI.2

2.2.11.1 Maximum Uplink Traffic Volume for PDCP SDUs in a Cell
Counters
Description
1526727045 L.Thrp.bits.UL.QCI. Maximum uplink DBS3900 LTE/

1.Max traffic volume for BTS3900 LTE/
PDCP SDUs of BTS3900A LTE/
BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900
1526727054 L.Thrp.bits.UL.Max Maximum uplink DBS3900 LTE/

traffic volume for BTS3900 LTE/
PDCP SDUs of all BTS3900A LTE/
services BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the maximum uplink traffic volume for received PDCP SDUs of services
with a specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The size of the payloads in the received PDCP SDUs of each service with a specific QCI ranging
from 1 to 9 is sampled per second in a cell. The size is accumulated at each sampling point. At
the end of a measurement period, the maximum of these sampling results is used as the value of
the corresponding counter.
Formula
None
Unit
bit

Related Features
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

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
L.Thrp.bits.UL.Max Multi-mode: None

GSM: None
UMTS: None

2.2.11.2 Maximum Downlink Traffic Volume for PDCP SDUs in a Cell
Counters
Description
1526727055 L.Thrp.bits.DL.QCI. Maximum downlink DBS3900 LTE/

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900
1526727064 L.Thrp.bits.DL.Max Maximum downlink DBS3900 LTE/

PDCP SDUs of all BTS3900A LTE/
services BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the maximum downlink traffic volume for transmitted PDCP SDUs of
services with a specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The size of the payloads in the transmitted PDCP SDUs of each service with a different QCI
ranging from 1 to 9 is sampled per second in a cell. At the end of a measurement period, the
maximum of these sampling results is used as the value of the corresponding counter.
Formula
None
Unit
bit

Related Features
L.Thrp.bits.DL.QCI.1.Max Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
L.Thrp.bits.DL.Max Multi-mode: None

GSM: None
UMTS: None

2.2.11.3 Total Bits of Transmitted Signaling SDUs on SRBs at the PDCP Layer in a
Cell
Counters
Description
1526728178 L.Thrp.bits.DL.SRB Total Bits of DBS3900 LTE/

Transmitted BTS3900 LTE/
Signaling SDUs on BTS3900A LTE/
SRBs at the PDCP BTS3900L LTE/
Layer BTS3900AL LTE,
BTS3900
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
Formula
None
Unit
bit
Related Features
L.Thrp.bits.DL.SRB Multi-mode: None

GSM: None
UMTS: None
2.2.11.4 Total Bits of Received Signaling SDUs on SRBs at the PDCP Layer in a Cell

Counters
Description
1526728179 L.Thrp.bits.UL.SRB Total Bits of DBS3900 LTE/

Received Signaling BTS3900 LTE/
SDUs on SRBs at the BTS3900A LTE/
PDCP Layer BTS3900L LTE/
BTS3900AL LTE,
BTS3900
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
Formula
None
Unit
bit
Related Features
L.Thrp.bits.UL.SRB Multi-mode: None

GSM: None
UMTS: None
2.2.11.5 Total Duration of Downlink Data Transmission in a Cell

Counters
Description
1526728232 L.Thrp.Time.Cell.D Total duration of DBS3900 LTE/

L downlink data BTS3900 LTE/
transmission in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the total duration of downlink data transmission in a cell. The sampling
period is 1 second.
Measurement Points
The duration of data transmission in a cell is sampled per second. If there is downlink data
transmission within a sampling period, the sampling result is 1. At the end of a measurement
period, the sum of these sampling results is used as the value of the L.Thrp.Time.Cell.DL
counter.
Formula
None
Unit
s
Related Features
L.Thrp.Time.Cell.DL Multi-mode: None

GSM: None
UMTS: None

2.2.11.6 Total Duration of Uplink Data Transmission in a Cell
Counters
Description
1526728233 L.Thrp.Time.Cell.U Total duration of DBS3900 LTE/

L uplink data BTS3900 LTE/
transmission in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the total duration of uplink data transmission in a cell. The sampling period
is 1 second.
Measurement Points
The duration of data transmission in a cell is sampled per second. If there is uplink data
period, the sum of these sampling results is used as the value of the L.Thrp.Time.Cell.UL
counter.
Formula
None
Unit
s

Related Features
L.Thrp.Time.Cell.UL Multi-mode: None

GSM: None
UMTS: None
2.2.11.7 Duration of Data Transmission for Services with a Specific QCI in a Cell
Counters
Description
1526728234 L.E- Duration of data DBS3900 LTE/

RAB.SessionTime. transmission for BTS3900 LTE/
QCI1 services with the QCI BTS3900A LTE/
BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900


Description

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900
Description
The counters measure the duration of data transmission for services with a specific QCI ranging
from 1 to 9 in a cell.
Measurement Points
The duration of data transmission for each service with a specific QCI ranging from 1 to 9 in a
cell is sampled per second. If there is uplink or downlink data transmission within this second,
the sampling result is 1. At the end of a measurement period, the sum of these sampling results
is used as the value of the corresponding counter based on the QCI. A deviation of one sampling
period may exist in the sampling timer when the timer performs time synchronization. As a
result, a deviation of one sampling period will also be generated in the value of the corresponding

counter, which affects the values of the KPIs that are calculated by using the counter. The effects
vary with the deviation in the value of the counter and calculation formulas for the KPIs.
Formula
None
Unit
s
Related Features

RAB.SessionTime.QCI1 GSM: None
UMTS: None

UMTS: None

UMTS: None


UMTS: None

UMTS: None

UMTS: None

UMTS: None

UMTS: None


UMTS: None
2.2.11.8 Total Duration of UE Data Transmission in a Cell
Counters
Description
1526728243 L.E- Total duration of UE DBS3900 LTE/

RAB.SessionTime. data transmission BTS3900 LTE/
UE time in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the total duration of UE data transmission in a cell.
Measurement Points
The duration of UE data transmission in a cell is sampled per second. If there is uplink or
downlink data transmission for a UE within the second, the sampling result is one second. At
the end of a measurement period, the sum of these sampling results for all UEs is used as the
value of the counter. A deviation of one sampling period may exist in the sampling timer when
the timer performs time synchronization. As a result, a deviation of one sampling period will
also be generated in the value of the counter, which affects the values of the KPIs that are
calculated by using the counter. The effects vary depending on the deviation in the value of the
counter and calculation formulas for the KPIs.
Formula
None
Unit
s

Related Features
L.E-RAB.SessionTime.UE Multi-mode: None

GSM: None
UMTS: None
2.2.11.9 Uplink Traffic Volume for PDCP SDUs in a Cell
Counters
Description
1526726776 L.Thrp.bits.UL.QCI. Uplink traffic DBS3900 LTE/

1 volume for PDCP BTS3900 LTE/
SDUs of services BTS3900A LTE/
BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900
1526728259 L.Thrp.bits.UL Total uplink traffic DBS3900 LTE/

volume for PDCP BTS3900 LTE/
SDUs in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the total traffic volume of received PDCP SDUs for services with a specific
QCI ranging from 1 to 9 in a cell.

Measurement Points
The size of the payloads in the received PDCP SDUs of each service with a specific QCI is
sampled in a cell. At the end of a measurement period, the sum of these sampling results is used
Formula
None
Unit
bit
Related Features
L.Thrp.bits.UL.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None
L.Thrp.bits.UL Multi-mode: None

GSM: None
UMTS: None
2.2.11.10 Receive Duration of Uplink PDCP SDUs in a Cell
Counters
Description
1526726777 L.Thrp.Time.UL.QC Receive duration of DBS3900 LTE/

I.1 uplink PDCP SDUs BTS3900 LTE/
for services with the BTS3900A LTE/
QCI of 1 in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900


Description

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900
1526728260 L.Thrp.Time.UL Total receive DBS3900 LTE/

duration of uplink BTS3900 LTE/
PDCP SDUs in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
The counters measure the total uplink transmit duration of PDCP SDUs for all UEs in a cell.
Measurement Points
The receive duration of uplink PDCP SDUs for each service with a specific QCI ranging from
1 to 9 in a cell is sampled per millisecond. If there is uplink data transmission within this
millisecond, the sampling result of the corresponding counter is 1. At the end of a measurement
period, the sum of these sampling results is used as the value of the corresponding counter.
Formula
None
Unit
ms
Related Features
L.Thrp.Time.UL.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None
L.Thrp.Time.UL Multi-mode: None

GSM: None
UMTS: None
2.2.11.11 Downlink Traffic Volume for PDCP SDUs in a Cell
Counters
Description
1526726803 L.Thrp.bits.DL.QCI. Downlink traffic DBS3900 LTE/

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900
1526728261 L.Thrp.bits.DL Total downlink DBS3900 LTE/

BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the total traffic volume of transmitted PDCP SDUs for services with a
specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The size of the payloads in the transmitted PDCP SDUs of each service with a specific QCI is
sampled in a cell. At the end of a measurement period, the sum of these sampling results is used
Formula
None
Unit
bit
Related Features
L.Thrp.bits.DL.QCI.1 Multi-mode: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
L.Thrp.bits.DL Multi-mode: None

GSM: None
UMTS: None
2.2.11.12 Transmit Duration of Downlink PDCP SDUs in a Cell

Counters
Description
1526726804 L.Thrp.Time.DL.QC Transmit duration of DBS3900 LTE/

I.1 downlink PDCP BTS3900 LTE/
SDUs for services BTS3900A LTE/
BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900
1526728262 L.Thrp.Time.DL Total transmit DBS3900 LTE/

duration of downlink BTS3900 LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the total downlink transmit duration of PDCP SDUs for all UEs in a cell.
Measurement Points
The transmit duration of downlink PDCP SDUs transmitted to all UEs for each service with a
specific QCI ranging from 1 to 9 is sampled per millisecond in a cell. If there is downlink data
to be transmitted within a millisecond, the corresponding counter is incremented by 1.
Formula
None
Unit
ms

Related Features
L.Thrp.Time.DL.QCI.1 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
L.Thrp.Time.DL Multi-mode: None

GSM: None
UMTS: None

2.2.11.13 Total Bits of User Data Received at the PDCP Layer from CEUs in a Cell
Counters
Description
1526728475 L.Thrp.bits.UL.CEU Total bits of user data DBS3900 LTE/

received at the PDCP BTS3900 LTE/
layer from cell edge BTS3900A LTE/
UEs (CEUs) in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the total bits of user data received at the PDCP layer from CEUs in a cell.
Measurement Points
The sum of the bits of user data received at the PDCP layer from all CEUs in a cell within a
measurement period is used as the value of the L.Thrp.bits.UL.CEU counter.
Formula
None
Unit
bit
Related Features
L.Thrp.bits.UL.CEU Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-00202202 Uplink Static Inter-Cell
TDLBFD-00202202 Interference Coordination
LOFD-00101402 Uplink Static Inter-Cell

Interference Coordination
TDLOFD-00101402
Uplink Dynamic Inter-Cell

2.2.11.14 Total Duration in Which User Data From CEUs Is Received at the PDCP
Layer in a Cell
Counters
Description
1526728476 L.Thrp.Time.UL.CE Total duration in DBS3900 LTE/

U which user data from BTS3900 LTE/
cell edge UEs BTS3900A LTE/
(CEUs) is received at BTS3900L LTE/
the PDCP layer in a BTS3900AL LTE,
cell BTS3900
Description
The counter measures the total duration in which user data from CEUs is received at the PDCP
layer in a cell.
Measurement Points
The sum of the duration in which user data from CEUs is received at the PDCP layer in a cell
within a measurement period is used as the value of the L.Thrp.Time.UL.CEU counter.
Formula
None
Unit
ms

Related Features
L.Thrp.Time.UL.CEU Multi-mode: None

GSM: None
UMTS: None

TDLOFD-00101402
2.2.11.15 Total Bits of User Data Transmitted at the PDCP Layer to CEUs in a Cell
Counters
Description
1526728477 L.Thrp.bits.DL.CEU Total bits of user data DBS3900 LTE/

transmitted at the BTS3900 LTE/
PDCP layer to cell BTS3900A LTE/
edge UEs (CEUs) in BTS3900L LTE/
BTS3900
Description
The counter measures the total bits of user data transmitted at the PDCP layer to downlink CEUs
in a cell.
Measurement Points
The sum of the bits of user data transmitted at the PDCP layer to CEUs in a cell within a
measurement period is used as the value of the L.Thrp.bits.DL.CEU counter.
Formula
None

Unit
bit
Related Features
L.Thrp.bits.DL.CEU Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-00202201 Downlink Static Inter-Cell
LOFD-00101401 Downlink Static Inter-Cell

TDLOFD-00101401
Downlink Dynamic Inter-
Cell Interference
Coordination
Cell Interference
Coordination
2.2.11.16 Total Duration in Which User Data Is Transmitted to CEUs at the PDCP
Layer in a Cell
Counters
Description
1526728478 L.Thrp.Time.DL.CE Total duration in DBS3900 LTE/

U which user data is BTS3900 LTE/
transmitted to cell BTS3900A LTE/
edge UEs (CEUs) at BTS3900L LTE/
cell BTS3900
Description
The counter measures the total duration in which user data is transmitted to CEUs at the PDCP
layer in a cell.
Measurement Points
The sum of the duration in which user data is transmitted at the PDCP layer to CEUs in a cell
within a measurement period is used as the value of the L.Thrp.Time.DL.CEU counter.

Formula
None
Unit
ms
Related Features
L.Thrp.Time.DL.CEU Multi-mode: None

GSM: None
UMTS: None

TDLOFD-00101401
Cell Interference
Coordination
Cell Interference
Coordination
2.2.11.17 Total Traffic Volume of Downlink PDCP SDUs Transmitted to Activated

CA UEs in a Cell
Counters
Description
1526728564 L.Thrp.bits.DL.CA Total volume of DBS3900 LTE/

User downlink data BTS3900 LTE/
transmitted to BTS3900A LTE/
activated CA UEs at BTS3900L LTE/
cell BTS3900
Description
The counter measures the total volume of downlink SDUs transmitted by activated CA UEs at
the PDCP layer in a cell.

Measurement Points
The payloads of downlink data successfully transmitted at the PDCP layer to activated CA UEs
in a cell are measured. The sum of these measurement results is used as the value of the
L.Thrp.bits.DL.CAUser counter.
Formula
None
Unit
bit
Related Features
L.Thrp.bits.DL.CAUser Multi-mode: None

GSM: None
UMTS: None
LTE: LAOFD-00100101 Intra-Band Carrier
LAOFD-00100102 Aggregation for Downlink
2CC in 20MHz
LAOFD-00100201
Inter-Band Carrier
TDLBFD-002008 2CC in 20MHz
TDLBFD-002025 Carrier Aggregation for
Downlink 2CC in 40MHz
Support of UE Category 6
Radio Bearer Management
Basic Scheduling
2.2.11.18 Total Transmit Duration of Downlink PDCP SDUs Transmitted to

Activated CA UEs in a Cell

Counters
Description
1526728565 L.Thrp.Time.DL.CA Total duration for DBS3900 LTE/

User activated CA UEs BTS3900 LTE/
transmitting BTS3900A LTE/
downlink data at the BTS3900L LTE/
PDCP layer in a cell BTS3900AL LTE,
BTS3900
Description
The counters measure the duration for activated CA UEs transmitting downlink data at the PDCP
layer in a cell.
Measurement Points
The transmit duration of downlink PDCP SDUs transmitted to activated CA UEs is sampled per
millisecond. The eNodeB determines that an activated CA UE transmits downlink PDCP SDUs
within a millisecond, the L.Thrp.Time.DL.CAUser counter is incremented by 1. At the end of
a measurement period, the sum of these sampling results is used as the value of the corresponding
counter.
Formula
None
Unit
ms

Related Features
L.Thrp.Time.DL.CAUser Multi-mode: None

GSM: None
UMTS: None
2CC in 20MHz
LAOFD-00100201
Inter-Band Carrier
TDLBFD-002008 2CC in 20MHz
TDLBFD-002025 Carrier Aggregation for
Basic Scheduling
2.2.11.19 Total Duration of Downlink Data Transmission with the Precision of 1

Millisecond in a Cell
Counters
Description
1526728997 L.Thrp.Time.Cell.D Total duration of DBS3900 LTE/

L.HighPrecision downlink data BTS3900 LTE/
transmission with the BTS3900A LTE/
precision of 1 BTS3900L LTE/
millisecond in a cell BTS3900AL LTE,
BTS3900
Description
The counter measures the total duration of downlink data transmission in a cell. The sampling
period is 1 millisecond.
Measurement Points
The duration of data transmission in a cell is sampled per millisecond. If there is downlink data
period, the sum of these sampling results is used as the value of the
L.Thrp.Time.Cell.DL.HighPrecision counter.

Formula
None
Unit
ms
Related Features
L.Thrp.Time.Cell.DL.High- Multi-mode: None

Precision GSM: None
UMTS: None
2.2.11.20 Total Duration of Uplink Data Transmission with the Precision of 1

Millisecond in a Cell
Counters
Description
1526728998 L.Thrp.Time.Cell.U Total duration of DBS3900 LTE/

L.HighPrecision uplink data BTS3900 LTE/
transmission with the BTS3900A LTE/
precision of 1 BTS3900L LTE/
millisecond in a cell BTS3900AL LTE,
BTS3900
Description
The counter measures the total duration of uplink data transmission in a cell. The sampling period
is 1 millisecond.
Measurement Points
The duration of data transmission in a cell is sampled per millisecond. If there is uplink data

period, the sum of these sampling results is used as the value of the
L.Thrp.Time.Cell.UL.HighPrecision counter.
Formula
None
Unit
ms
Related Features
L.Thrp.Time.Cell.UL.High- Multi-mode: None

Precision GSM: None
UMTS: None
2.2.11.21 Downlink traffic volume sent in the last TTI before the buffer is empty
Counters
Description
1526729005 L.Thrp.bits.DL.Last Downlink traffic DBS3900 LTE/

TTI volume sent in the BTS3900 LTE/
last TTI before the BTS3900A LTE/
buffer is empty BTS3900L LTE/
BTS3900AL LTE,
BTS3900

TTI.QCI.1 volume sent in the BTS3900 LTE/
last TTI for services BTS3900A LTE/
with the QCI 1 before BTS3900L LTE/
the buffer is empty BTS3900AL LTE,
BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900
Description
The counters measure the traffic volume sent in the last TTI before the DRB downlink buffer is
empty for services with a specific QCI.
Measurement Points
The downlink traffic volume sent in the last TTI for services with a specific QCI ranging from
1 to 9 before the buffer is empty is measured in the cell.
Formula
None
Unit
bit
Related Features
L.Thrp.bits.DL.LastTTI Multi-mode: None

GSM: None
UMTS: None

L.Thrp.bits.DL.LastTTI.QC Multi-mode: None

I.1 GSM: None
UMTS: None

I.2 GSM: None
UMTS: None

I.3 GSM: None
UMTS: None

I.4 GSM: None
UMTS: None

I.5 GSM: None
UMTS: None


I.6 GSM: None
UMTS: None

I.7 GSM: None
UMTS: None

I.8 GSM: None
UMTS: None

I.9 GSM: None
UMTS: None
2.2.11.22 Data transmit duration except the last TTI before the downlink buffer is
empty

Counters
Description
1526729015 L.Thrp.Time.DL.R Data transmit DBS3900 LTE/

mvLastTTI duration except the BTS3900 LTE/
downlink buffer is BTS3900L LTE/
empty BTS3900AL LTE,
BTS3900

mvLastTTI.QCI.1 duration except the BTS3900 LTE/
empty for services BTS3900AL LTE,
with the QCI 1 BTS3900







Description



Description
The counters measure the data transmit duration except the last TTI before the DRB downlink
buffer is empty for services with a specific QCI.
Measurement Points
The data transmit duration of downlink PDCP SDUs for each service with a specific QCI ranging
from 1 to 9 in a cell is sampled per millisecond. If there is downlink data transmission within
this millisecond, the sampling result of the corresponding counter is 1, excluding the last TTI
before the buffer is empty. At the end of a measurement period, the sum of these sampling results
Formula
None
Unit
ms

Related Features
L.Thrp.Time.DL.RmvLastT Multi-mode: None

TI GSM: None
UMTS: None

TI.QCI.1 GSM: None
UMTS: None

TI.QCI.2 GSM: None
UMTS: None

TI.QCI.3 GSM: None
UMTS: None

TI.QCI.4 GSM: None
UMTS: None


TI.QCI.5 GSM: None
UMTS: None

TI.QCI.6 GSM: None
UMTS: None

TI.QCI.7 GSM: None
UMTS: None

TI.QCI.8 GSM: None
UMTS: None

TI.QCI.9 GSM: None
UMTS: None

2.2.11.23 Traffic Volume of Uplink PDCP SDUs Sent in the Last TTI Before the UE
Buffer is Empty
Counters
Description
1526729049 L.Thrp.bits.UE.UL. Traffic volume of DBS3900 LTE/

LastTTI uplink PDCP SDUs BTS3900 LTE/
sent in the last TTI BTS3900A LTE/
before the UE buffer BTS3900L LTE/
is empty BTS3900AL LTE,
BTS3900
Description
The counter measures the uplink traffic volume sent in the last TTI before the UE buffer is empty
in a cell.
Measurement Points
The uplink traffic volume sent in the last TTI before the UE buffer is empty is measured in a
cell.
Formula
None
Unit
bit
Related Features
L.Thrp.bits.UE.UL.LastTTI Multi-mode: None

GSM: None
UMTS: None

2.2.11.24 Uplink Data Transmit Duration Except the Last TTI Before the UE Buffer
is Empty
Counters
Description
1526729050 L.Thrp.Time.UE.UL Uplink data transmit DBS3900 LTE/

.RmvLastTTI duration except the BTS3900 LTE/
UE buffer is empty BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the uplink data transmit duration except the last TTI before the UE buffer
is empty in a cell.
Measurement Points
The data transmit duration of uplink PDCP SDUs in a cell is sampled per millisecond. If there
is uplink data transmission within this millisecond, the sampling result of the corresponding
counter is 1, excluding the last TTI before the UE buffer is empty. At the end of a measurement
period, the sum of the sampling results is used as the value of the
L.Thrp.Time.UE.UL.RmvLastTTI counter.
Formula
None
Unit
ms
Related Features
L.Thrp.Time.UE.UL.RmvL Multi-mode: None

astTTI GSM: None
UMTS: None

2.2.11.25 Uplink Traffic Volume of PDCP SDUs Scheduled for Small Packets
Counters
Description
1526729415 L.Thrp.bits.UE.UL. Uplink traffic DBS3900 LTE/

SmallPkt volume of PDCP BTS3900 LTE/
SDUs scheduled for BTS3900A LTE/
small packets BTS3900L LTE/
BTS3900AL LTE,
BTS3900
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

2.2.11.26 Uplink Data Transmission Duration Except that for Small Packets
Counters
Description
1526729416 L.Thrp.Time.UE.UL Uplink data DBS3900 LTE/

.RmvSmallPkt transmission BTS3900 LTE/
duration except that BTS3900A LTE/
for small packets BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the uplink data transmission duration except that for small packets in a
cell.
Measurement Points
The duration from the time that the uplink buffer of the UE is not empty to the time that the
uplink buffer of the UE is empty is sampled in a cell. A buffer status report (BSR) indicates the
data amount of the uplink buffer of the UE. The sampling result excluding the last TTI before
the UE buffer is empty is used as the value of the L.Thrp.Time.UE.UL.RmvSmallPkt counter.
Formula
None
Unit
ms
Related Features
L.Thrp.Time.UE.UL.RmvS Multi-mode: None

mallPkt GSM: None
UMTS: None

2.2.12 Measurement related to PDCP (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
Description
1526726833 L.PDCP.Tx.Disc.T Number of downlink V100R008C00,and

rf.SDU.QCI.1 traffic SDUs the mapping single-
discarded by the mode base station
PDCP layer for version that
eNodeB:Version
earlier than
V100R003C00

eNodeB:Version
earlier than
V100R003C00

eNodeB:Version
earlier than
V100R003C00


Description

eNodeB:Version
earlier than
V100R003C00

eNodeB:Version
earlier than
V100R003C00

eNodeB:Version
earlier than
V100R003C00

eNodeB:Version
earlier than
V100R003C00

eNodeB:Version
earlier than
V100R003C00


Description

eNodeB:Version
earlier than
V100R003C00
1526727349 L.PDCP.DL.RoHC Compression rate of V100R008C00,and

.HdrCompRatio headers of all the mapping single-
downlink PDCP mode base station
SDUs after the version that
ROHC introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727350 L.PDCP.DL.RoHC Compression rate of V100R008C00,and

.PktCompRatio all downlink PDCP the mapping single-
SDUs (including mode base station
headers and version that
payloads) after the introduce this
ROHC counter is:
eNodeB:Version
earlier than
V100R003C00
1526727351 L.PDCP.UL.RoHC Decompression V100R008C00,and

.FailDecompRatio failure rate of all the mapping single-
uplink PDCP SDUs mode base station
after the ROHC version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727889 L.PDCP.Tx.TotRev Number of V100R008C00,and

.Trf.SDU.QCI.1 transmitted the mapping single-
downlink traffic mode base station
PDCP SDUs for version that
eNodeB:V100R003
C00


Description

eNodeB:V100R003
C00

eNodeB:V100R003
C00

eNodeB:V100R003
C00

eNodeB:V100R003
C00

eNodeB:V100R003
C00


Description

eNodeB:V100R003
C00

eNodeB:V100R003
C00

eNodeB:V100R003
C00
1526728522 L.PDCP.UL.RoHC Compression rate of V100R008C00,and

.HdrCompRatio headers of all uplink the mapping single-
PDCP SDUs mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728523 L.PDCP.UL.RoHC Compression rate of V100R008C00,and

.PktCompRatio all uplink PDCP the mapping single-
SDUs (including mode base station
headers and version that
payloads) after the introduce this
ROHC. counter is:
eNodeB:V100R006
C00
None

2.2.12.1 Number of Discarded Downlink PDCP SDUs
Counters
Description
1526726833 L.PDCP.Tx.Disc.Trf Number of downlink DBS3900 LTE/

.SDU.QCI.1 traffic SDUs BTS3900 LTE/
discarded by the BTS3900A LTE/
PDCP layer for BTS3900L LTE/







Description



Description
PDCP SDUs may be discarded after being received and before being sent over the air interface.
The counters measure the number of discarded downlink traffic PDCP SDUs for services with
a specific QCI ranging from 1 to 9 in a cell. If this cell is an SCell of a CA UE, SDUs that are
discarded at the MAC layer by the CA UE are also counted in this counter.
Measurement Points
The corresponding counter is incremented by 1 each time a PDCP SDU is discarded before being
sent over the air interface.
Formula
None
Unit
packet

Related Features
L.PDCP.Tx.Disc.Trf.SDU.Q Multi-mode: None

CI.1 GSM: None
UMTS: None

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

CI.9 GSM: None
UMTS: None
2.2.12.2 Downlink ROHC Compression Rate of Headers

Counters
Description
1526727349 L.PDCP.DL.RoHC. Compression rate of DBS3900 LTE/

HdrCompRatio headers of all BTS3900 LTE/
downlink PDCP BTS3900A LTE/
SDUs after the BTS3900L LTE/
ROHC BTS3900AL LTE,
BTS3900
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
TDLOFD-001017 (ROHC)
RObust Header Compression
(ROHC)

2.2.12.3 Downlink ROHC Compression Rate
Counters
Description
1526727350 L.PDCP.DL.RoHC. Compression rate of DBS3900 LTE/

PktCompRatio all downlink PDCP BTS3900 LTE/
SDUs (including BTS3900A LTE/
headers and BTS3900L LTE/
payloads) after the BTS3900AL LTE,
ROHC BTS3900
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
(ROHC)

2.2.12.4 Decompression Failure Rate of Uplink PDCP SDUs After the ROHC
Counters
Description
1526727351 L.PDCP.UL.RoHC. Decompression DBS3900 LTE/

FailDecompRatio failure rate of all BTS3900 LTE/
uplink PDCP SDUs BTS3900A LTE/
after the ROHC BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the decompression failure rate of all uplink PDCP SDUs after the ROHC
in a cell.Only the PDCP SDUs that are compressed by the ROHC algorithm are measured.
Measurement Points
When the received uplink PDCP SDUs need to be decompressed in a cell, the number of PDCP
SDUs that fail to be decompressed and the number of uplink PDCP SDUs to be decompressed
are calculated respectively. The decompression failure rate is counted within a measurement
period.The rate of the number of PDCP SDUs that fail to be decompressed to the number of
uplink PDCP SDUs to be decompressed is used as the value of the counter. If ROHC is disabled
within a measurement period, the value of this counter is invalid.
Formula
None
Unit
%
Related Features
L.PDCP.UL.RoHC.FailDe- Multi-mode: None

compRatio GSM: None
UMTS: None
(ROHC)

2.2.12.5 Number of Transmitted Downlink Traffic PDCP SDUs for DRB Services
in a Cell over the Uu Interface
Counters
Description
1526727889 L.PDCP.Tx.TotRev. Number of DBS3900 LTE/

Trf.SDU.QCI.1 transmitted BTS3900 LTE/
downlink traffic BTS3900A LTE/
PDCP SDUs for BTS3900L LTE/







Description



Description
The counters measure the number of transmitted downlink traffic PDCP SDUs for DRB services
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
Formula
None
Unit
packet

Related Features
L.PDCP.Tx.TotRev.Trf.SD Multi-mode: None

U.QCI.1 GSM: None
UMTS: None

U.QCI.2 GSM: None
UMTS: None

U.QCI.3 GSM: None
UMTS: None

U.QCI.4 GSM: None
UMTS: None

U.QCI.5 GSM: None
UMTS: None


U.QCI.6 GSM: None
UMTS: None

U.QCI.7 GSM: None
UMTS: None

U.QCI.8 GSM: None
UMTS: None

U.QCI.9 GSM: None
UMTS: None
2.2.12.6 Uplink ROHC Compression Rate of Headers

Counters
Description
1526728522 L.PDCP.UL.RoHC. Compression rate of DBS3900 LTE/

HdrCompRatio headers of all uplink BTS3900 LTE/
PDCP SDUs BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
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
(ROHC)

2.2.12.7 Uplink ROHC Compression Rate
Counters
Description
1526728523 L.PDCP.UL.RoHC. Compression rate of DBS3900 LTE/

PktCompRatio all uplink PDCP BTS3900 LTE/
SDUs (including BTS3900A LTE/
headers and BTS3900L LTE/
payloads) after the BTS3900AL LTE,
ROHC. BTS3900
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
(ROHC)

2.2.13 Measurement related to Paging (Paging.Cell)
Overview
The Paging.Cell function subset measures the number of received paging messages over the S1
interface, number of paging attempts to UEs over the Uu interface, and number of discarded
paging messages from the MME to UEs in a cell.
Counters
Description
1526726884 L.Paging.S1.Rx Number of received V100R008C00,and

paging messages the mapping single-
over the S1 interface mode base station
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526726885 L.Paging.UU.Att Number of UEs V100R008C00,and

contained in paging the mapping single-
messages mode base station
transmitted over the version that
Uu interface in a cell introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526726886 L.Paging.UU.Succ Number of V100R008C00,and

Successful Paging the mapping single-
Responses from the mode base station
UE in a Cell version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526727212 L.Paging.Dis.Num Number of discarded V100R008C00,and

paging messages the mapping single-
from the MME to mode base station
UEs due to flow version that
control in a cell introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526728337 L.Paging.UU.SIUp- Number of paging V100R008C00,and

date messages the mapping single-
transmitted due to mode base station
system information version that
changes introduce this
counter is:
eNodeB:V100R005
C00
1526728521 L.Paging.Dis.PchC Number of paging V100R008C00,and

ong messages discarded the mapping single-
due to paging mode base station
channel congestion version that
introduce this
counter is:
eNodeB:V100R006
C00
None
2.2.13.1 Number of Received Paging Messages over the S1 Interface in a Cell
Counters
Description
1526726884 L.Paging.S1.Rx Number of received DBS3900 LTE/

paging messages BTS3900 LTE/
over the S1 interface BTS3900A LTE/
BTS3900AL LTE,
BTS3900

Description
The counter measures the number of paging messages received by the eNodeB over the S1
interface in a cell.
Measurement Points
As shown at point A in Figure 2-86, the counter is incremented by 1 each time the eNodeB
receives a paging message from the MME and at least one tracking area identifier (TAI) of the
cell is contained in the TAI list in the paging message.
Figure 2-86
Formula
None
Unit
None
Related Features
L.Paging.S1.Rx Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002011 Paging
TDLBFD-002011 Paging
2.2.13.2 Number of UEs Contained in Paging Messages Transmitted over the Uu

Interface in a Cell

Counters
Description
1526726885 L.Paging.UU.Att Number of UEs DBS3900 LTE/

contained in paging BTS3900 LTE/
messages BTS3900A LTE/
transmitted over the BTS3900L LTE/
Uu interface in a cell BTS3900AL LTE,
BTS3900
Description
The counter measures the number of UEs contained in paging messages that the eNodeB sends
to UEs over the Uu interface.
Measurement Points
As shown at point A in Figure 2-87, the counter is incremented based on the number of UEs
contained in paging messages each time the eNodeB sends a paging message to UEs over the
Uu interface.
Figure 2-87
Formula
None
Unit
None

Related Features
L.Paging.UU.Att Multi-mode: None

GSM: None
UMTS: None
2.2.13.3 Number of Successful Paging Responses from the UE in a Cell
Counters
Description
1526726886 L.Paging.UU.Succ Number of DBS3900 LTE/

Successful Paging BTS3900 LTE/
Responses from the BTS3900A LTE/
UE in a Cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of successful paging responses from the UE in a cell.
Measurement Points
as shown at point A in Figure 2-88, the counter is incremented by 1 each time the eNodeB
receives an RRC Connection Request message from the UE and the Establishment Cause
information element of the message is "mt-Access".
Figure 2-88

Formula
None
Unit
None
Related Features
L.Paging.UU.Succ Multi-mode: None

GSM: None
UMTS: None
2.2.13.4 Number of Discarded Paging Messages from the MME to UEs in a Cell
Counters
Description
1526727212 L.Paging.Dis.Num Number of discarded DBS3900 LTE/

paging messages BTS3900 LTE/
from the MME to BTS3900A LTE/
UEs due to flow BTS3900L LTE/
control in a cell BTS3900AL LTE,
BTS3900
Description
The counter measures the number of paging messages discarded by the eNodeB due to flow
control in a cell. The messages are sent from the MME to UEs in a cell.
Measurement Points
The counter is incremented by 1 each time the eNodeB discards a paging message due to flow
control in a cell.
Formula
None

Unit
None
Related Features
L.Paging.Dis.Num Multi-mode: None

GSM: None
UMTS: None
2.2.13.5 Number of Paging Messages Transmitted Due to System Information

Changes
Counters
Description
1526728337 L.Paging.UU.SIUp- Number of paging DBS3900 LTE/

date messages BTS3900 LTE/
transmitted due to BTS3900A LTE/
system information BTS3900L LTE/
changes BTS3900AL LTE,
BTS3900
Description
The counter measures the number of paging messages that are transmitted from the eNodeB to
UEs due to system information changes.
Measurement Points
As shown at point A in Figure 2-89, the counter is incremented each time the eNodeB sends a
paging message to UEs over the Uu interface and the paging message contains a field indicating
system information changes.
Figure 2-89

Formula
None
Unit
None
Related Features
L.Paging.UU.SIUpdate Multi-mode: None

GSM: None
UMTS: None
2.2.13.6 Number of Paging Messages Discarded due to Paging Channel Congestion
Counters
Description
1526728521 L.Paging.Dis.PchCo Number of paging DBS3900 LTE/

ng messages discarded BTS3900 LTE/
due to paging BTS3900A LTE/
channel congestion BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of paging messages discarded due to paging channel
congestion in a cell.
Measurement Points
When the traffic volume of paging message is too large, the buffer is insufficient for these paging
messages and some paging messages are discarded. The counter is incremented by 1 each time
a paging message is discarded in this case.
Formula
None

Unit
None
Related Features
L.Paging.Dis.PchCong Multi-mode: None

GSM: None
UMTS: None
2.2.14 Measurement related to securmode (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 2-90 shows the measurement points of security mode configuration.
Figure 2-90

Counters
Description
1526727171 L.SecurMode.S1.R Number of security V100R008C00,and

x mode configurations the mapping single-
received over the S1 mode base station
interface version that
introduce this
counter is:
eNodeB:V100R005
C00
1526727172 L.SecurMode.Cmd Number of security V100R008C00,and

mode commands the mapping single-
sent over the Uu mode base station
interface version that
introduce this
counter is:
eNodeB:V100R005
C00
1526727173 L.SecurMode.Cmp Number of V100R008C00,and

successful security the mapping single-
mode configurations mode base station
received from the UE version that
introduce this
counter is:
eNodeB:V100R005
C00
1526727174 L.SecurMode.Fail Number of security V100R008C00,and

mode configuration the mapping single-
failures received mode base station
from the UE version that
introduce this
counter is:
eNodeB:V100R005
C00
None
2.2.14.1 Number of Security Mode Setups in a Cell

Counters
Description
1526727171 L.SecurMode.S1.Rx Number of security DBS3900 LTE/

mode configurations BTS3900 LTE/
received over the S1 BTS3900A LTE/
interface BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526727172 L.SecurMode.Cmd Number of security DBS3900 LTE/

mode commands BTS3900 LTE/
sent over the Uu BTS3900A LTE/
interface BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526727173 L.SecurMode.Cmp Number of DBS3900 LTE/

successful security BTS3900 LTE/
mode configurations BTS3900A LTE/
received from the UE BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526727174 L.SecurMode.Fail Number of security DBS3900 LTE/

mode configuration BTS3900 LTE/
failures received BTS3900A LTE/
from the UE BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of security mode setups in different scenarios in a cell. During
a security mode configuration process, parameters related to integrity and security are negotiated
among the MME, eNodeB, and UE with the purpose to provide integrity protection and ciphering
for signaling messages and user data over the Uu interface.
Measurement Points
as shown at point A in Figure 2-91, the L.SecurMode.S1.Rx counter is incremented by 1 each
time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST message from the MME.
as shown at point B in Figure 2-91, the L.SecurMode.Cmd counter is incremented by 1 each
time the eNodeB sends a Security Mode Command message to the UE.
as shown at point C in Figure 2-91, the L.SecurMode.Cmp counter is incremented by 1 each
time the eNodeB receives a Security Mode Complete message from the UE.
as shown at point A in Figure 2-92, the L.SecurMode.Fail counter is incremented by 1 each
time the eNodeB receives a Security Mode Failure message from the UE.

Figure 2-91

Figure 2-92
Formula
None
Unit
None
Related Features
L.SecurMode.S1.Rx Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001010 Security Mechanism
TDLOFD-001010 Security Mechanism
L.SecurMode.Cmd Multi-mode: None

GSM: None
UMTS: None

L.SecurMode.Cmp Multi-mode: None

GSM: None
UMTS: None
L.SecurMode.Fail Multi-mode: None

GSM: None
UMTS: None
2.2.15 Measurement related to RA (RA.Cell)
Overview
Random access (RA) can be classified into contention-based RA and non-contention-based RA.
The RA.Cell function subset measures the number of times the preamble is received and the
number of times the Random Access Response message is sent in two RA procedures, as well
as the number of times the Contention Resolution message is sent during the contention-based
RA procedure. It is used to analyze the RA load and success rate.
Counters
Description
1526727215 L.RA.GrpA.Att Number of times the V100R008C00,and

contention preamble the mapping single-
in group A is mode base station
received version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526727216 L.RA.GrpA.Resp Number of times the V100R008C00,and

Random Access the mapping single-
Response message is mode base station
sent after the version that
contention preamble introduce this
in group A is counter is:
received eNodeB:Version
earlier than
V100R003C00
1526727217 L.RA.GrpA.Con- Number of times the V100R008C00,and

tResolution Contention the mapping single-
Resolution message mode base station
is sent after the version that
in group A is counter is:
earlier than
V100R003C00
1526727218 L.RA.GrpB.Att Number of times the V100R008C00,and

contention preamble the mapping single-
in group B is mode base station
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727219 L.RA.GrpB.Resp Number of times the V100R008C00,and

Random Access the mapping single-
sent after the version that
in group B is counter is:
earlier than
V100R003C00
1526727220 L.RA.GrpB.Con- Number of times the V100R008C00,and

tResolution Contention the mapping single-
is sent after the version that
in group B is counter is:
earlier than
V100R003C00


Description
1526727221 L.RA.Dedicate.Att Number of times the V100R008C00,and

non-contention- the mapping single-
based preamble is mode base station
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727222 L.RA.Dedicate.HO. Number of times the V100R008C00,and

Att non-contention- the mapping single-
based preamble is mode base station
received (used in version that
handover) introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727223 L.RA.Dedicate.Res Number of times the V100R008C00,and

p Random Access the mapping single-
sent after the non- version that
contention-based introduce this
preamble is received counter is:
eNodeB:Version
earlier than
V100R003C00

Resp Random Access the mapping single-
sent after the non- version that
contention-based introduce this
preamble is received counter is:
(used in handover) eNodeB:Version
earlier than
V100R003C00

Msg3Rcv UE Msg3 Response the mapping single-
message is received mode base station
in the handover- version that
triggered non- introduce this
contention-based RA counter is:
procedure eNodeB:Version
earlier than
V100R003C00


Description
1526728954 L.RA.GrpA.ContR Number of times the V100R008C00,and

esolution.PDCCH Contention the mapping single-
is sent on the version that
PDCCH after the introduce this
contention-based counter is:
preamble in group A eNodeB:V100R006
is received C00
1526728955 L.RA.GrpB.ContR Number of times the V100R008C00,and

esolution.PDCCH Contention the mapping single-
is sent on the version that
PDCCH after the introduce this
contention-based counter is:
preamble in group B eNodeB:V100R006
is received C00
1526728956 L.RA.TA.UE.Index Number of times the V100R008C00,and

0 TA value is 0 or 1 the mapping single-
(index 0) in a UE- mode base station
initiated random version that
access procedure in a introduce this
cell counter is:
eNodeB:V100R006
C00

1 TA value is 2 or 3 the mapping single-
(index 1) in a UE- mode base station
initiated random version that
access procedure in a introduce this
cell counter is:
eNodeB:V100R006
C00

2 TA value is ranging the mapping single-
from 4 to 7 (index 2) mode base station
in a UE-initiated version that
random access introduce this
procedure in a cell counter is:
eNodeB:V100R006
C00


Description

from 8 to 13 (index 3) mode base station
eNodeB:V100R006
C00

from 14 to 25 (index mode base station
4) in a UE-initiated version that
eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

from 186 to 385 mode base station
(index 8) in a UE- version that
initiated random introduce this
access procedure in a counter is:
cell eNodeB:V100R006
C00

C00

C00

11 TA value is greater the mapping single-
than 985 (index 11) mode base station
eNodeB:V100R006
C00
Counter Sub Counter
L.RA.GrpA.ContResolution L.RA.GrpA.ContResolution.PDCCH
L.RA.GrpB.ContResolution L.RA.GrpB.ContResolution.PDCCH
L.RA.Dedicate.Att L.RA.Dedicate.HO.Att
L.RA.Dedicate.Resp L.RA.Dedicate.HO.Resp

2.2.15.1 Number of Times the Contention Preamble Is Received
Counters
Description
1526727215 L.RA.GrpA.Att Number of times the DBS3900 LTE/

contention preamble BTS3900 LTE/
in group A is BTS3900A LTE/
received BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526727218 L.RA.GrpB.Att Number of times the DBS3900 LTE/

contention preamble BTS3900 LTE/
in group B is BTS3900A LTE/
BTS3900AL LTE,
BTS3900
Description
Contention-based preambles may belong to either group A or group B. Contention-based
preambles in group A are mandatory, and contention-based preambles in group B are optional.
The number of contention-based preambles that can be assigned to each cell and the grouping
of preambles are set by the eNodeB, and the information is broadcast on the BCH. In the UE-
initiated contention-based RA procedure, the UE determines the group of preambles based on
the eNodeB configuration on group A and group B and the UE's radio environment. Then, the
UE randomly selects a preamble and transmit it. The counters measure the number of times the
contention-based preamble in group A or B is received. They indicate the reception load of
contention-based preambles.
Measurement Points
the eNodeB receives a contention preamble:
The L.RA.GrpA.Att counter is incremented by 1 if the preamble belongs to group A.
The L.RA.GrpB.Att counter is incremented by 1 if the preamble belongs to group B.

Figure 2-93
Formula
None
Unit
None
Related Features
L.RA.GrpA.Att Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002010 Random Access Procedure
TDLBFD-002010 Random Access Procedure
L.RA.GrpB.Att Multi-mode: None

GSM: None
UMTS: None
2.2.15.2 Number of Times the Random Access Response Message Is Sent After the
Contention Preamble Is Received

Counters
Description
1526727216 L.RA.GrpA.Resp Number of times the DBS3900 LTE/

Random Access BTS3900 LTE/
Response message is BTS3900A LTE/
sent after the BTS3900L LTE/
contention preamble BTS3900AL LTE,
in group A is BTS3900
received
1526727219 L.RA.GrpB.Resp Number of times the DBS3900 LTE/

sent after the BTS3900L LTE/
in group B is BTS3900
received
Description
After receiving a contention preamble, the eNodeB sends a Random Access Response (RAR)
message to the UE if system resources are sufficient. The counters measure the number of times
the Random Access Response message is sent after the contention preamble in group A or group
B is received. They indicate the eNodeB's response to the contention preamble.
Measurement Points
the eNodeB sends a Random Access Response message to the UE after receiving a contention
preamble:
The L.RA.GrpA.Resp counter is incremented by 1 if the preamble belongs to group A.
The L.RA.GrpB.Resp counter is incremented by 1 if the preamble belongs to group B.

Figure 2-94
Formula
None
Unit
None
Related Features
L.RA.GrpA.Resp Multi-mode: None

GSM: None
UMTS: None
L.RA.GrpB.Resp Multi-mode: None

GSM: None
UMTS: None
2.2.15.3 Number of Times the Contention Resolution Message Is Sent After the
Contention Preamble Is Received

Counters
Description
1526727217 L.RA.GrpA.ContRe- Number of times the DBS3900 LTE/

solution Contention BTS3900 LTE/
Resolution message BTS3900A LTE/
is sent after the BTS3900L LTE/
in group A is BTS3900
received
1526727220 L.RA.GrpB.ContRe- Number of times the DBS3900 LTE/

solution Contention BTS3900 LTE/
is sent after the BTS3900L LTE/
in group B is BTS3900
received
1526728954 L.RA.GrpA.ContRe Number of times the DBS3900 LTE/

solution.PDCCH Contention BTS3900 LTE/
is sent on the BTS3900L LTE/
PDCCH after the BTS3900AL LTE,
contention-based BTS3900
preamble in group A
is received
1526728955 L.RA.GrpB.ContRes Number of times the DBS3900 LTE/

olution.PDCCH Contention BTS3900 LTE/
is sent on the BTS3900L LTE/
PDCCH after the BTS3900AL LTE,
contention-based BTS3900
preamble in group B
is received
Description
The counters measure the number of times the Contention Resolution message is sent after the
contention preamble in group A or group B is received. They indicate the success rate of the
contention RA procedure.
Measurement Points
As shown at point C in Figure 2-95, the corresponding counter is incremented by 1 each time
the eNodeB sends a Contention Resolution message to the UE after receiving a preamble:
The L.RA.GrpA.ContResolution counter is incremented by 1 if the contention preamble belongs
to group A.

The L.RA.GrpB.ContResolution counter is incremented by 1 if the contention preamble belongs

to group B.
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 2-95
Formula
None
Unit
None
Related Features
L.RA.GrpA.ContResolution Multi-mode: None

GSM: None
UMTS: None

L.RA.GrpB.ContResolution Multi-mode: None

GSM: None
UMTS: None
L.RA.GrpA.ContResolution. Multi-mode: None

PDCCH GSM: None
UMTS: None
L.RA.GrpB.ContResolution. Multi-mode: None

PDCCH GSM: None
UMTS: None
2.2.15.4 Number of Times the Non-Contention-Based Preamble Is Received
Counters
Description
1526727221 L.RA.Dedicate.Att Number of times the DBS3900 LTE/

non-contention- BTS3900 LTE/
based preamble is BTS3900A LTE/
BTS3900AL LTE,
BTS3900
1526727222 L.RA.Dedicate.HO. Number of times the DBS3900 LTE/

Att non-contention- BTS3900 LTE/
based preamble is BTS3900A LTE/
received (used in BTS3900L LTE/
handover) BTS3900AL LTE,
BTS3900
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
the eNodeB receives a non-contention-based preamble:
The L.RA.Dedicate.Att counter is incremented by 1.
The L.RA.Dedicate.HO.Att counter is incremented by 1 in a handover.
Figure 2-96
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
2.2.15.5 Number of Times the Random Access Response Message Is Sent After the
Non-Contention-Based Preamble Is Received
Counters
Description
1526727223 L.RA.Dedicate.Resp Number of times the DBS3900 LTE/

sent after the non- BTS3900L LTE/
contention-based BTS3900AL LTE,
preamble is received BTS3900

Resp Random Access BTS3900 LTE/
sent after the non- BTS3900L LTE/
contention-based BTS3900AL LTE,
preamble is received BTS3900
(used in handover)
Description
After receiving the non-contention-based preamble, the eNodeB sends a Random Access
Response (RAR) message to the UE if system resources are sufficient. The counters measure
the total number of times the RAR message is sent and the number of times the RAR message
is sent due to handovers. They indicate the eNodeB's response to the non-contention-based
preamble.

Measurement Points
As shown at point C in Figure 2-97, the corresponding counter is increment by 1 each time the
eNodeB sends a Random Access Response message to the UE after receiving a Random Access
Preamble:
The L.RA.Dedicate.Resp counter is incremented by 1 for non-contention-based preamble.
The L.RA.Dedicate.HO.Resp counter is incremented by 1 for non-contention-based preamble

and in a handover.
Figure 2-97
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
2.2.15.6 Number of Times the UE Msg3 Response Message Is Received in the

Handover-Triggered Non-Contention-Based RA Procedure
Counters
Description

Msg3Rcv UE Msg3 Response BTS3900 LTE/
message is received BTS3900A LTE/
in the handover- BTS3900L LTE/
triggered non- BTS3900AL LTE,
contention-based RA BTS3900
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 2-98, in the handover-triggered non-contention-based RA
procedure, the L.RA.Dedicate.HO.Msg3Rcv counter is incremented by 1 each time the eNodeB
receives a UE Msg3 Response message from the UE.

Figure 2-98
Formula
None
Unit
None
Related Features
L.RA.Dedicate.HO.Msg3Rc Multi-mode: None

v GSM: None
UMTS: None
2.2.15.7 Number of Times the TA with a Specific Value Range in a UE-Initiated

Random Access Procedure in a Cell

Counters
Description
1526728956 L.RA.TA.UE.Index Number of times the DBS3900 LTE/

0 TA value is 0 or 1 BTS3900 LTE/
(index 0) in a UE- BTS3900A LTE/
initiated random BTS3900L LTE/
access procedure in a BTS3900AL LTE,
cell BTS3900

1 TA value is 2 or 3 BTS3900 LTE/
(index 1) in a UE- BTS3900A LTE/
initiated random BTS3900L LTE/
access procedure in a BTS3900AL LTE,
cell BTS3900

2 TA value is ranging BTS3900 LTE/
from 4 to 7 (index 2) BTS3900A LTE/
in a UE-initiated BTS3900L LTE/
random access BTS3900AL LTE,
procedure in a cell BTS3900

from 8 to 13 (index 3) BTS3900A LTE/

from 14 to 25 (index BTS3900A LTE/
4) in a UE-initiated BTS3900L LTE/




Description


from 186 to 385 BTS3900A LTE/
(index 8) in a UE- BTS3900L LTE/
initiated random BTS3900AL LTE,
access procedure in a BTS3900
cell

cell

cell

11 TA value is greater BTS3900 LTE/
than 985 (index 11) BTS3900A LTE/
Description
The counter measures the number of times the TA with a specific value range contained in the
Random Access Response message in a UE-initiated random access procedure in a cell. One
TA equals 0.52 microsecond.
Measurement Points
In a UE-initiated random access procedure, when the eNodeB sends a Random Access Response
(RAR) message to the UE after receiving a Random Access Preamble message, the

corresponding counter is incremented based on the TA value contained in the RAR message
each time the eNodeB receives the first uplink data packet that passes the cyclic redundancy
check (CRC).
Formula
None
Unit
None
Related Features
L.RA.TA.UE.Index0 Multi-mode: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

2.2.16 Measurement related to PWR (ChMeas.Pwr.Cell)
Overview
The ChMeas.Pwr.Cell function subset measures the power in a cell to analyze the overall quality
of the downlink channel.
Counters
Description
1526727388 L.DLPwr.Max Maximum downlink V100R008C00,and

transmit power in a the mapping single-
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727389 L.DLPwr.Avg Average downlink V100R008C00,and

transmit power in a the mapping single-
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526728297 L.UL.Interference. Maximum uplink V100R008C00,and

Max interference and the mapping single-
noise received by mode base station
each PRB in a cell version that
introduce this
counter is:
eNodeB:V100R005
C00
1526728298 L.UL.Interference. Average uplink V100R008C00,and

Avg interference and the mapping single-
introduce this
counter is:
eNodeB:V100R005
C00


Description
1526728435 L.UL.Interference. Minimum uplink V100R008C00,and

Min interference and the mapping single-
introduce this
counter is:
eNodeB:V100R006
C00
1526728769 L.UpPTS.Interfere Power of V100R008C00,and

nce.Avg interference and the mapping single-
noise detected in mode base station
each PRB in the UL version that
UpPTS introduce this
counter is:
eNodeB:V100R006
C00
1526728770 L.UL.FirstUL0.Pw This counter V100R008C00,and

r indicates the receive the mapping single-
power of the first mode base station
symbol in the first version that
UL subframe introduce this
counter is:
eNodeB:V100R006
C00
1526728771 L.UL.FirstUL6 This counter V100R008C00,and

(4).Pwr indicates the receive the mapping single-
power of the seventh mode base station
(or fifth) symbol in version that
the first UL subframe introduce this
counter is:
eNodeB:V100R006
C00
1526728772 L.UL.LastUL0.Pwr This counter V100R008C00,and

indicates the receive the mapping single-
power of the first mode base station
symbol in the last UL version that
subframe introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728773 L.UL.LastUL11 This counter V100R008C00,and

(9).Pwr indicates the receive the mapping single-
power of the twelfth mode base station
(or tenth) symbol in version that
the last UL subframe introduce this
counter is:
eNodeB:V100R006
C00
None
2.2.16.1 Downlink Transmit Power
Counters
Description
1526727388 L.DLPwr.Max Maximum downlink DBS3900 LTE/

transmit power in a BTS3900 LTE/
cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526727389 L.DLPwr.Avg Average downlink DBS3900 LTE/

transmit power in a BTS3900 LTE/
cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
Downlink transmit power is allocated dynamically by the eNodeB at the MAC layer within each
TTI. The transmit power of only the PDSCH is involved in these counters. In LTE-TDD, if the
TTI at a sampling point is an uplink subframe, the measurement is sampled at the closest next
downlink subframe. The counters measure the maximum and average downlink transmit power
respectively. They are used to analyze the usage of PDSCH power.
Measurement Points
The downlink transmit power is sampled per second. At the end of a measurement period, the
maximum or average of these sampling results is used as the value of the corresponding

counter.Note that for SFN cells, the maximum or average of downlink transmit power should
be measured for all physical cells.
Formula
None
Unit
dBm
Related Features
L.DLPwr.Max Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002025 Basic Scheduling
L.DLPwr.Avg Multi-mode: None

GSM: None
UMTS: None
2.2.16.2 Interference and Noise Received by Each PRB in a Cell
Counters
Description
1526728297 L.UL.Interference.M Maximum uplink DBS3900 LTE/

ax interference and BTS3900 LTE/
noise received by BTS3900A LTE/
each PRB in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728298 L.UL.Interference.A Average uplink DBS3900 LTE/

vg interference and BTS3900 LTE/
BTS3900AL LTE,
BTS3900


Description
1526728435 L.UL.Interference.M Minimum uplink DBS3900 LTE/

in interference and BTS3900 LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the uplink interference and noise received by each PRB in a cell.
Measurement Points
The total power of noise floor and neighboring cell interference received by each PRB is
measured per TTI in the uplink, the eNodeB divides the total power of noise floor and
neighboring cell interference by the number of PRBs, the value is used as a sampling result.
Note for SFN cells, the average interference power and neighboring cell interference of each
PRB should be measured for all physical cells. At the end of a measurement period, the
maximum, average, and minimum of these sampling results are used as the values of the
L.UL.Interference.Max, L.UL.Interference.Avg, and L.UL.Interference.Min counters,
respectively.
Formula
None
Unit
dBm
Related Features
L.UL.Interference.Max Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002003 Physical Channel
Physical Channel
Management

L.UL.Interference.Avg Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management
L.UL.Interference.Min Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management
2.2.16.3 Receive Power of interference and noise detected of each PRB in the UL
UpPTS
Counters
Description
1526728769 L.UpPTS.Interferen Power of DBS3900 LTE/

ce.Avg interference and BTS3900 LTE/
noise detected in BTS3900A LTE/
each PRB in the UL BTS3900L LTE/
UpPTS BTS3900AL LTE,
BTS3900
Description
Power of interference and noise detected in each PRB in the UL UpPTS.
Measurement Points
This eNodeB measures the power of interference and noise detected in the UpPTS of a selected
RRU in every 2s and calculates the average value, which indicates the average power of the
interference and noise of each PRB. The average value is used as a sampling result. At the end
of a measurement period, the average of these sampling results is used as the value of the counter.

Formula
None
Unit
dBm
Related Features
L.UpPTS.Interference.Avg Multi-mode: None

GSM: None
UMTS: None
Management
2.2.16.4 Receive Power of the first Symbol in First UL Subframe
Counters
Description
1526728770 L.UL.FirstUL0.Pwr This counter DBS3900 LTE/

indicates the receive BTS3900 LTE/
power of the first BTS3900A LTE/
symbol in the first BTS3900L LTE/
UL subframe BTS3900AL LTE,
BTS3900
Description
This counter indicates the receive power of the first symbol in the first UL subframe.
Measurement Points
The eNodeB measures the power of the first symbol in the first UL subframe of a selected RRU
in every 2s and uses the value as a sampling result. At the end of a measurement period, the
average of these sampling results is used as the value of the counter.
Formula
None

Unit
dBm
Related Features
L.UL.FirstUL0.Pwr Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management
2.2.16.5 Receive Power of the seventh (or fifth) Symbol in First UL Subframe
Counters
Description
1526728771 L.UL.FirstUL6 This counter DBS3900 LTE/

(4).Pwr indicates the receive BTS3900 LTE/
power of the seventh BTS3900A LTE/
(or fifth) symbol in BTS3900L LTE/
the first UL subframe BTS3900AL LTE,
BTS3900
Description
This counter indicates the receive power of the seventh (or fifth) symbol in the first UL subframe.
Measurement Points
The eNodeB measures the power of the seventh symbol (or the fifth symbol if extended CP is
used) in the first UL subframe of a selected RRU in every 2s and uses the value as a sampling
result. At the end of a measurement period, the average of these sampling results is used as the
Formula
None

Unit
dBm
Related Features
L.UL.FirstUL6(4).Pwr Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management
2.2.16.6 Receive Power of the first Symbol in Last UL Subframe
Counters
Description
1526728772 L.UL.LastUL0.Pwr This counter DBS3900 LTE/

indicates the receive BTS3900 LTE/
power of the first BTS3900A LTE/
symbol in the last UL BTS3900L LTE/
subframe BTS3900AL LTE,
BTS3900
Description
This counter indicates the receive power of the first symbol in the last UL subframe.
Measurement Points
The eNodeB measures the power of the first symbol in the last UL subframe of a selected RRU
in every 2s and uses the value as a sampling result. At the end of a measurement period, the
Formula
None
Unit
dBm

Related Features
L.UL.LastUL0.Pwr Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management
2.2.16.7 Receive Power of the twelfth (or tenth) Symbol in the Last UL Subframe
Counters
Description
1526728773 L.UL.LastUL11 This counter DBS3900 LTE/

(9).Pwr indicates the receive BTS3900 LTE/
power of the twelfth BTS3900A LTE/
(or tenth) symbol in BTS3900L LTE/
the last UL subframe BTS3900AL LTE,
BTS3900
Description
This counter indicates the receive power of the twelfth (or tenth) symbol in the last UL subframe.
Measurement Points
The eNodeB measures the power of the twelfth symbol (or the tenth symbol if extended CP is
used) in the last UL subframe of a selected RRU in every 2s and uses the value as a sampling
result. At the end of a measurement period, the average of these sampling results is used as the
Formula
None
Unit
dBm

Related Features
L.UL.LastUL11(9).Pwr Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management
2.2.17 Measurement related to MIMO (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
Description
1526727391 L.ChMeas.MIMO. Total number of used V100R008C00,and

PRB.CL.Rank1 downlink PRBs in the mapping single-
closed-loop rank 1 mode base station
mode version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

mode version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

PRB.OL.Rank1 downlink PRBs in the mapping single-
open-loop rank 1 mode base station
mode version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

mode version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

mode version that
introduce this
counter is:
eNodeB:V100R003
C00

mode version that
introduce this
counter is:
eNodeB:V100R003
C00

mode version that
introduce this
counter is:
eNodeB:V100R003
C00


Description

mode version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728349 L.ChMeas.VMIM Number of RBs that V100R008C00,and

O.PairPRB.Succ are successfully the mapping single-
paired for VMIMO mode base station
introduce this
counter is:
eNodeB:V100R005
C01
1526728350 L.ChMeas.VMIM Number of RBs that V100R008C00,and

O.PairPRB.Tot can be paired for the mapping single-
VMIMO UEs in a mode base station
cell version that
introduce this
counter is:
eNodeB:V100R005
C01
1526728351 L.ChMeas.MUBF. Number of RBs that V100R008C00,and

PairPRB.Succ are successfully the mapping single-
paired for MUBF mode base station
introduce this
counter is:
eNodeB:V100R005
C01
1526728352 L.ChMeas.MUBF. Number of RBs that V100R008C00,and

PairPRB.Tot can be paired for the mapping single-
MUBF UEs in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C01


Description
1526728881 L.ChMeas.BF.PRB Total number of used V100R008C00,and

.OL.Rank1 downlink PRBs in the mapping single-
BF rank 1 mode mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728882 L.ChMeas.BF.PRB Total number of used V100R008C00,and

.OL.Rank2 downlink PRBs in the mapping single-
BF rank 2 mode mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
None
2.2.17.1 Number of Used Downlink PRBs in MIMO Mode
Counters
Description
1526727391 L.ChMeas.MIMO.P Total number of used DBS3900 LTE/

RB.CL.Rank1 downlink PRBs in BTS3900 LTE/
closed-loop rank 1 BTS3900A LTE/
mode BTS3900L LTE/
BTS3900AL LTE,
BTS3900

mode BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

RB.OL.Rank1 downlink PRBs in BTS3900 LTE/
open-loop rank 1 BTS3900A LTE/
mode BTS3900L LTE/
BTS3900AL LTE,
BTS3900

mode BTS3900L LTE/
BTS3900AL LTE,
BTS3900

mode BTS3900L LTE/
BTS3900AL LTE,
BTS3900

mode BTS3900L LTE/
BTS3900AL LTE,
BTS3900

mode BTS3900L LTE/
BTS3900AL LTE,
BTS3900

mode BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
Downlink MIMO is divided into eight modes: open-loop modes with the rank ranging from 1
to 4 and closed-loop modes with the rank ranging from 1 to 4. The counters measure the number
of used downlink PRBs in different MIMO modes for analyzing the PRB usage in different
scenarios.

Measurement Points
The number of used downlink PRBs in each MIMO mode is measured within the measurement
period. For cells configured with single frequency network (SFN), the number of PRBs used in
each physical cell is incremented.
In the TDD LTE system, the number of PRBs used by each related physical cell is incremented
for cells configured with Cell Combination.
Formula
None
Unit
None
Related Features
L.ChMeas.MIMO.PRB.CL. Multi-mode: None

Rank1 GSM: None
UMTS: None
LOFD-001001 DL 2x2 MIMO
LOFD-001060 DL 4X4 MIMO

Rank2 GSM: None
UMTS: None

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
2.2.17.2 Number of RBs That Are Successfully Paired for VMIMO UEs in a Cell
Counters
Description
1526728349 L.ChMeas.VMIMO. Number of RBs that DBS3900 LTE/

PairPRB.Succ are successfully BTS3900 LTE/
paired for VMIMO BTS3900A LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of RBs that are successfully paired for VMIMO UEs in a
cell. The number of RBs that are successfully paired for VMIMO UEs is accumulated during
each subframe for uplink scheduling. Only the number of RBs for one out of each pair of UEs
is accumulated and the number of RBs in each related RRU is accumulated for an SFN cell.
Measurement Points
The number of RBs that are successfully paired for VMIMO UEs during each subframe for
uplink scheduling in a cell is sampled per second. At the end of the measurement period, the
average of these sampling results is used as the value of the L.ChMeas.VMIMO.PairPRB.Succ
counter.
Formula
None
Unit
None

Related Features
L.ChMeas.VMIMO.PairPR Multi-mode: None

B.Succ GSM: None
UMTS: None
LTE: TDLOFD-001075 SFN
2.2.17.3 Number of RBs That Can Be Paired for VMIMO UEs in a Cell
Counters
Description
1526728350 L.ChMeas.VMIMO. Number of RBs that DBS3900 LTE/

PairPRB.Tot can be paired for BTS3900 LTE/
VMIMO UEs in a BTS3900A LTE/
cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of RBs that can be paired for VMIMO UEs in a cell. The
number of RBs that can be paired for VMIMO UEs is accumulated during each subframe for
uplink scheduling. The number of RBs in each related RRU is accumulated for an SFN cell.
Measurement Points
The number of RBs that can be paired for VMIMO UEs during each subframe for uplink
scheduling in a cell is sampled per second. At the end of the measurement period, the average
of these sampling results is used as the value of the L.ChMeas.VMIMO.PairPRB.Tot counter.
Formula
None
Unit
None

Related Features
L.ChMeas.VMIMO.PairPR Multi-mode: None

B.Tot GSM: None
UMTS: None
2.2.17.4 Number of RBs for MIMO UEs That Are Successfully Paired for MUBF in
a Cell
Counters
Description
1526728351 L.ChMeas.MUBF.P Number of RBs that DBS3900 LTE/

airPRB.Succ are successfully BTS3900 LTE/
paired for MUBF BTS3900A LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of RBs that are successfully paired for MUBF UEs in a cell.
The number of RBs that are successfully paired for MUBF UEs is accumulated during each
subframe for downlink scheduling. Only the number of RBs for one out of each pair of UEs is
accumulated and the number of RBs in each related RRU is accumulated for an SFN cell.
Measurement Points
The number of RBs that are successfully paired for MUBF UEs during each subframe for
downlink scheduling in a cell is sampled per second. At the end of the measurement period, the
average of these sampling results is used as the value of the L.ChMeas.MUBF.PairPRB.Succ
counter.
Formula
None
Unit
None

Related Features
L.ChMeas.MUBF.PairPRB. Multi-mode: None

Succ GSM: None
UMTS: None
2.2.17.5 Number of RBs for MIMO UEs That Can Be Paired for MUBF in a Cell
Counters
Description
1526728352 L.ChMeas.MUBF.P Number of RBs that DBS3900 LTE/

airPRB.Tot can be paired for BTS3900 LTE/
MUBF UEs in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of RBs that can be paired for MUBF UEs in a cell. The number
of RBs that can be paired for MUBF UEs is accumulated during each subframe for downlink
scheduling. The number of RBs in each related RRU is accumulated for an SFN cell.
Measurement Points
The number of RBs that can be paired for MUBF UEs during each subframe for downlink
scheduling in a cell is sampled per second. At the end of the measurement period, the average
of these sampling results is used as the value of the L.ChMeas.MUBF.PairPRB.Tot counter.
Formula
None
Unit
None

Related Features
L.ChMeas.MUBF.PairPRB. Multi-mode: None

Tot GSM: None
UMTS: None
2.2.17.6 Number of Used Downlink PRBs in BF Mode
Counters
Description
1526728881 L.ChMeas.BF.PRB. Total number of used DBS3900 LTE/

OL.Rank1 downlink PRBs in BTS3900 LTE/
BF rank 1 mode BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728882 L.ChMeas.BF.PRB. Total number of used DBS3900 LTE/

OL.Rank2 downlink PRBs in BTS3900 LTE/
BF rank 2 mode BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
Downlink BF is divided into two modes: rank 1 and rank 2. The counters measure the number
of used downlink PRBs in different BF modes
Measurement Points
The number of used downlink PRBs in each BF mode is sampled per second. At the end of a
counter. A deviation of one sampling period may exist in the sampling timer when the timer
performs time synchronization. As a result, a deviation of one sampling period will also be
generated in the value of this counter, which affects the values of the KPIs that are calculated
by using this counter. The effects vary depending on the deviation in the value of this counter
and calculation formulas for the KPIs.

Formula
None
Unit
None
Related Features
L.ChMeas.BF.PRB.OL.Ran Multi-mode: None

k1 GSM: None
UMTS: None
TDLOFD-001049 Single Streaming
TDLOFD-001061 Beamforming
Dual streaming
Beamforming
L.ChMeas.BF.PRB.OL.Ran Multi-mode: None

k2 GSM: None
UMTS: None
TDLOFD-001049 Single Streaming
TDLOFD-001061 Beamforming
Dual streaming
Beamforming
2.2.18 Measurement related to CQI (ChMeas.CQI.Cell)
Overview
Channel Quality Indicator (CQI) indicates downlink channel quality and is calculated by the
UE. The UE sends the evaluation result to the eNodeB through the uplink channel. The CQI
report is used as the input of MAC scheduling of the eNodeB. The ChMeas.CQI.Cell function
subset measures the number CQI reports with a specific value ranging from 0 to 15 in a cell and
indicates the overall quality of the downlink channel.

Counters
Description
1526727396 L.ChMeas.CQI.DL Number of wideband V100R008C00,and

.0 CQI reports with the the mapping single-
value of 0 mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526729319 L.ChMeas.CQI.DL Number of periodic V100R008C00,and

.SingleCW.Period- wideband CQI the mapping single-
ic.0 reports with the value mode base station
of 0 in single- version that
codeword introduce this
transmission counter is:
eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00
1526729335 L.ChMeas.CQI.DL Number of aperiodic V100R008C00,and

.SingleCW.Aperi- wideband CQI the mapping single-
odic.0 reports with the value mode base station
eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

.DualCW.Code0.Pe wideband CQI the mapping single-
riodic.0 reports with the value mode base station
of 0 for codeword 0 version that
in dual-codeword introduce this
eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

.DualCW.Code0.A wideband CQI the mapping single-
periodic.0 reports with the value mode base station
eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00


Description

eNodeB:V100R006
C00

eNodeB:V100R006
C00

eNodeB:V100R006
C00
None
2.2.18.1 Number of Wideband CQI Reports in a Cell
Counters
Description
1526727396 L.ChMeas.CQI.DL. Number of wideband DBS3900 LTE/

0 CQI reports with the BTS3900 LTE/
value of 0 BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
Channel Quality Indicator (CQI) indicates downlink channel quality and is calculatd by the UE.
The UE sends the evaluation result to the eNodeB through the uplink channel. The CQI report
is used as the input of MAC scheduling of the eNodeB. The counters measure the number of
wideband CQI reports with a specific value ranging from 0 to 15 in a cell (if RI > 1, CQI for
each of the two codewords is calculated separately) and indicate the overall quality of the
downlink channel.
Measurement Points
The corresponding counter is incremented by 1 based on the CQI value ranging from 0 to 15
each time the eNodeB receives a wideband CQI report from a UE.
Formula
None
Unit
None
Related Features
L.ChMeas.CQI.DL.0 Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002016 Dynamic Downlink Power
LBFD-002025 Allocation
TDLBFD-002025 Dynamic Downlink Power

Allocation
Basic Scheduling


GSM: None
UMTS: None

Allocation
Basic Scheduling

GSM: None
UMTS: None

Allocation
Basic Scheduling

GSM: None
UMTS: None

Allocation
Basic Scheduling

GSM: None
UMTS: None

Allocation
Basic Scheduling


GSM: None
UMTS: None

Allocation
Basic Scheduling

GSM: None
UMTS: None

Allocation
Basic Scheduling

GSM: None
UMTS: None

Allocation
Basic Scheduling

GSM: None
UMTS: None

Allocation
Basic Scheduling


GSM: None
UMTS: None

Allocation
Basic Scheduling

GSM: None
UMTS: None

Allocation
Basic Scheduling

GSM: None
UMTS: None

Allocation
Basic Scheduling

GSM: None
UMTS: None

Allocation
Basic Scheduling


GSM: None
UMTS: None

Allocation
Basic Scheduling

GSM: None
UMTS: None

Allocation
Basic Scheduling

GSM: None
UMTS: None

Allocation
Basic Scheduling
2.2.18.2 Number of Periodic Wideband CQI Reports in Single-Codeword

Transmission in a Cell

Counters
Description
1526729319 L.ChMeas.CQI.DL. Number of periodic DBS3900 LTE/

SingleCW.Periodic. wideband CQI BTS3900 LTE/
0 reports with the value BTS3900A LTE/
of 0 in single- BTS3900L LTE/
codeword BTS3900AL LTE,
transmission BTS3900








Description









Description


Description
report is used as the input of MAC scheduling of the eNodeB. The counters measure the number
of periodic wideband CQI reports with a specific value ranging from 0 to 15 in single-codeword
transmission in a cell and indicate the overall quality of the downlink channel.
Measurement Points
each time the eNodeB receives a periodic wideband CQI report from a UE in single-codeword
transmission.
Formula
None
Unit
None

Related Features
L.ChMeas.CQI.DL.SingleC Multi-mode: None

W.Periodic.0 GSM: None
UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

2.2.18.3 Number of Aperiodic Wideband CQI Reports in Single-Codeword

Transmission in a Cell
Counters
Description
1526729335 L.ChMeas.CQI.DL. Number of aperiodic DBS3900 LTE/

SingleCW.Aperiod- wideband CQI BTS3900 LTE/
ic.0 reports with the value BTS3900A LTE/







Description









Description



Description
of aperiodic wideband CQI reports with a specific value ranging from 0 to 15 in single-codeword
transmission in a cell and indicate the overall quality of the downlink channel.
Measurement Points
each time the eNodeB receives an aperiodic wideband CQI report in single-codeword
transmission from a UE.
Formula
None
Unit
None

Related Features

W.Aperiodic.0 GSM: None
UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

2.2.18.4 Number of Periodic Wideband CQI Reports for Codeword 0 in Dual-

Codeword Transmission in a Cell
Counters
Description

DualCW.Code0.Pe- wideband CQI BTS3900 LTE/
riodic.0 reports with the value BTS3900A LTE/
of 0 for codeword 0 BTS3900L LTE/
in dual-codeword BTS3900AL LTE,







Description









Description



Description
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
Formula
None
Unit
None

Related Features
L.ChMeas.CQI.DL.DualCW Multi-mode: None

.Code0.Periodic.0 GSM: None
UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

2.2.18.5 Number of Aperiodic Wideband CQI Reports for Codeword 0 in Dual-

Counters
Description

DualCW.Code0.Ape wideband CQI BTS3900 LTE/







Description









Description



Description
of aperiodic wideband CQI reports with a specific value ranging from 0 to 15 for codeword 0
in dual-codeword transmission in a cell and indicate the overall quality of the downlink channel.
Measurement Points
each time the eNodeB receives an aperiodic wideband CQI report for codeword 0 in dual-
codeword transmission from a UE.
Formula
None
Unit
None

Related Features

.Code0.Aperiodic.0 GSM: None
UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

2.2.18.6 Number of Periodic Wideband CQI Reports for Codeword 1 in Dual-

Counters
Description








Description









Description



Description
of periodic wideband CQI reports with a specific value ranging from 0 to 15 for codeword 1 in
dual-codeword transmission in a cell and indicate the overall quality of the downlink channel.
Measurement Points
each time the eNodeB receives a periodic wideband CQI report for codeword 1 in dual-codeword
Formula
None
Unit
None

Related Features

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

2.2.18.7 Number of Aperiodic Wideband CQI Reports for Codeword 1 in Dual-

Counters
Description








Description









Description



Description
of aperiodic wideband CQI reports with a specific value ranging from 0 to 15 for codeword 1
in dual-codeword transmission in a cell and indicate the overall quality of the downlink channel.
Measurement Points
each time the eNodeB receives an aperiodic wideband CQI report for codeword 1 in dual-
codeword transmission from a UE.
Formula
None
Unit
None

Related Features

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling


UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

UMTS: None

Allocation
Basic Scheduling

2.2.19 Measurement related to MCS (ChMeas.MCS.Cell)
Overview
Modulation and Coding Scheme (MCS) is the basic output of MAC scheduling. The
ChMeas.MCS.Cell function subset measures the number of times an MCS index is scheduled
in the uplink or downlink in a cell.
Counters
Description
1526727412 L.ChMeas.PUSCH. Number of times V100R008C00,and

MCS.0 MCS index 0 is the mapping single-
scheduled on the mode base station
PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PUSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727444 L.ChMeas.PDSCH. Number of times V100R008C00,and

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

PDSCH version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526728566 L.ChMeas.PRB.UL Number of PRBs on V100R008C00,and

.MCS.0 the PUSCH using the mapping single-
MCS index 0 for mode base station
scheduling in a cell version that
introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00


Description

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00


Description

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00


Description

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00


Description

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00


Description

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00


Description

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00
1526728599 L.ChMeas.PRB.DL Number of PRBs on V100R008C00,and

.RANK1.MCS.0 the PDSCH in rank 1 the mapping single-
mode using MCS mode base station
index 0 for version that
scheduling in a cell introduce this
counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00
None
2.2.19.1 Number of Times an MCS Index Is Scheduled on the PUSCH
Counters
Description
1526727412 L.ChMeas.PUSCH. Number of times DBS3900 LTE/

MCS.0 MCS index 0 is BTS3900 LTE/
scheduled on the BTS3900A LTE/
PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PUSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The uplink MCS index is an output of uplink scheduling. It corresponds to a unique modulation
order, TBS index, and redundancy version. The counters measure the number of times that the
eNodeB schedules an MCS index for a UE in the uplink, and the MCS index ranges from 0 to
31.
Measurement Points
The corresponding counter is incremented by 1 each time the eNodeB schedules an MCS index
for a UE in the uplink within a TTI.
Formula
None
Unit
None

Related Features
L.ChMeas.PUSCH.MCS.0 Multi-mode: None

GSM: None
UMTS: None
LBFD-001005 Modulation: DL/UL QPSK,
TDLBFD-002025 DL/UL 16QAM, DL
64QAM
TDLBFD-001005
Basic Scheduling
Modulation: DL/UL QPSK,
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
LOFD-001006
DL/UL 16QAM, DL
64QAM
UL 64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
LOFD-001006
DL/UL 16QAM, DL
64QAM
UL 64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
LOFD-001006
DL/UL 16QAM, DL
64QAM
UL 64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
LOFD-001006
DL/UL 16QAM, DL
64QAM
UL 64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
LOFD-001006
DL/UL 16QAM, DL
64QAM
UL 64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
LOFD-001006
DL/UL 16QAM, DL
64QAM
UL 64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
LOFD-001006
DL/UL 16QAM, DL
64QAM
UL 64QAM
2.2.19.2 Number of Times a Specific MCS Index Is Scheduled on the PDSCH
Counters
Description
1526727444 L.ChMeas.PDSCH. Number of times DBS3900 LTE/

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900

PDSCH BTS3900L LTE/
BTS3900AL LTE,
BTS3900
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

Related Features
L.ChMeas.PDSCH.MCS.0 Multi-mode: None

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM


GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM

GSM: None
UMTS: None
64QAM
TDLBFD-001005
Basic Scheduling
DL/UL 16QAM, DL
64QAM
2.2.19.3 Number of PRBs on the PUSCH Using a Specified MCS for Scheduling in
a Cell
Counters
Description
1526728566 L.ChMeas.PRB.UL. Number of PRBs on DBS3900 LTE/

MCS.0 the PUSCH using BTS3900 LTE/
MCS index 0 for BTS3900A LTE/
scheduling in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900


Description

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900


Description

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900


Description

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900


Description

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900
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

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None


GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None

GSM: None
UMTS: None
2.2.19.4 Number of PRBs on the PDSCH Using a Specific MCS index for Scheduling
in a Cell
Counters
Description
1526728599 L.ChMeas.PRB.DL. Number of PRBs on DBS3900 LTE/

RANK1.MCS.0 the PDSCH in rank 1 BTS3900 LTE/
mode using MCS BTS3900A LTE/
index 0 for BTS3900L LTE/
scheduling in a cell BTS3900AL LTE,
BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

Description
The counters measure the numbers of PRBs in different modes to be allocated using a specified
MCS for downlink scheduling, including HARQ retransmission. For UEs in rank 2 mode, two
codewords are transmitted at the same time. Each codeword is configured with an MCS.
Therefore, the number of PRBs in rank 2 mode for scheduling in each codeword is counted
separately.
Measurement Points
The number of PRBs on the PDSCH in rank 1 or rank 2 to be allocated using a specified MCS
for downlink scheduling in a cell is measured within the measurement period.
Formula
None
Unit
None
Related Features
L.ChMeas.PRB.DL.RANK1 Multi-mode: None

.MCS.0 GSM: None
UMTS: None
LTE: LBFD-001005 Modulation: DL/UL QPSK,
LOFD-001001 DL/UL 16QAM, DL
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
TDLOFD-001003 DL/UL 16QAM, DL
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.1 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.2 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.3 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.4 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.5 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.6 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.7 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.8 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.9 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.10 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.11 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.12 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.13 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.14 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.15 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.16 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.17 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.18 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.19 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.20 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.21 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.22 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.23 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.24 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.25 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.26 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.27 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.28 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.29 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.30 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.31 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.0 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.1 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.2 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.3 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.4 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.5 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.6 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.7 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.8 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.9 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.10 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.11 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.12 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.13 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.14 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.15 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.16 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.17 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.18 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.19 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.20 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.21 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.22 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.23 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.24 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.25 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.26 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.27 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.28 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.29 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO

.MCS.30 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO


.MCS.31 GSM: None
UMTS: None
64QAM
LOFD-001003
DL 2x2 MIMO
LOFD-001060
DL 4x2 MIMO
TDLBFD-001005
DL 4X4 MIMO
TDLOFD-001001
64QAM
DL 2x2 MIMO
DL 4x2 MIMO
2.2.20 Measurement related to PRB (ChMeas.PRB.Cell)
Overview
Physical resource blocks (PRBs) are the basic air interface resources. The ChMeas.PRB.Cell
function subset measures the usage of uplink or downlink PRBs in a cell.
Counters
Description
1526726737 L.ChMeas.PRB.UL Average number of V100R008C00,and

.Used.Avg used uplink PRBs the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526726740 L.ChMeas.PRB.DL Average number of V100R008C00,and

.Used.Avg used PDSCH PRBs the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727483 L.ChMeas.PRB.PU Average number of V100R008C00,and

CCH.Avg used PUCCH PRBs the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526728299 L.ChMeas.PDCCH Number of times that V100R008C00,and

.SymNum.1 the PDCCH occupies the mapping single-
one OFDM symbol mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00

two OFDM symbols mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00

three OFDM mode base station
symbols version that
introduce this
counter is:
eNodeB:V100R005
C00


Description

four OFDM symbols mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00
1526728303 L.ChMeas.CCE.Co Number of PDCCH V100R008C00,and

mmUsed CCEs used for the mapping single-
common DCI mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00
1526728304 L.ChMeas.CCE.U Number of PDCCH V100R008C00,and

LUsed CCEs used for uplink the mapping single-
DCI mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00
1526728305 L.ChMeas.CCE.D Number of PDCCH V100R008C00,and

LUsed CCEs used for the mapping single-
downlink DCI mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00
1526728340 L.ULCoMP.RB Average number of V100R008C00,and

scheduled PRBs for the mapping single-
UL CoMP mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00


Description

.PCell.Used.Avg downlink PRBs the mapping single-
occupied by CA UEs mode base station
that use the local cell version that
as their primary introduce this
serving cell counter is:
eNodeB:V100R006
C00

.SCell.Used.Avg downlink PRBs the mapping single-
occupied by CA UEs mode base station
that use the local cell version that
as their secondary introduce this
serving cell counter is:
eNodeB:V100R006
C00
1526728433 L.ChMeas.PRB.DL Number of available V100R008C00,and

.Avail downlink PRBs the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728434 L.ChMeas.PRB.UL Number of available V100R008C00,and

.Avail uplink PRBs the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

.CEU.Used.Avg PRBs used by uplink the mapping single-
CEUs in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description

.CEU.Used.Avg PRBs used by the mapping single-
downlink CEUs in a mode base station
cell version that
introduce this
counter is:
eNodeB:V100R006
C00

.FSS.Avg PRBs allocated for the mapping single-
uplink frequency mode base station
selective scheduling version that
introduce this
counter is:
eNodeB:V100R006
C00

.FSS.Avg PRBs allocated for the mapping single-
downlink frequency mode base station
selective scheduling version that
introduce this
counter is:
eNodeB:V100R006
C00

.PreSch.Used.Avg PRBs allocated for the mapping single-
uplink pre- mode base station
scheduling version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728664 L.ChMeas.PDCCH Number of times of V100R008C00,and

.DL.DTXNum.Agg DTX for PDCCH the mapping single-
Lvl1 resource allocation mode base station
with aggregation version that
level 1 in a cell introduce this
counter is:
eNodeB:V100R006
C00


Description

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

counter is:
eNodeB:V100R006
C00

.AggLvl1Num PDCCH resource the mapping single-
allocations with mode base station
aggregation level 1 version that
introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00


Description

introduce this
counter is:
eNodeB:V100R006
C00

introduce this
counter is:
eNodeB:V100R006
C00

.DrbUsed.Avg PRBs used by the mapping single-
PUSCH DRBs mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

.DrbUsed.Avg PRBs used by the mapping single-
PDSCH DRBs mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728764 L.ChMeas.PRB.PU Average number of V100R008C00,and

SCH.Avg used PUSCH PRBs the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728765 L.ChMeas.CCE.Av Number of available V100R008C00,and

ail PDCCH CCEs the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
None
2.2.20.1 Number of Used Uplink PRBs
Counters
Description
1526726737 L.ChMeas.PRB.UL. Average number of DBS3900 LTE/

Used.Avg used uplink PRBs BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728340 L.ULCoMP.RB Average number of DBS3900 LTE/

scheduled PRBs for BTS3900 LTE/
UL CoMP BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

DrbUsed.Avg PRBs used by BTS3900 LTE/
PUSCH DRBs BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1526728764 L.ChMeas.PRB.PUS Average number of DBS3900 LTE/

CH.Avg used PUSCH PRBs BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The L.ChMeas.PRB.UL.Used.Avg counter measures the average number of uplink PRBs used
by PUSCH, PRACH, and PUCCH. It is used to analyze the usage of uplink PRBs.
The L.ULCoMP.RB counter measures the average number of PRBs used by UL CoMP UEs in
a cell. It is used to analyze the usage of uplink PRBs for UL CoMP UEs.
The number of uplink used PRBs is determined by the uplink traffic volume and signal quality.
Measurement Points
During a measurement period, the average number of PRBs used by all uplink channels, by
PUSCH, by PUSCH DRBs (in an SFN cell, the number of used PRBs is accumulated), and by
UL CoMP UEs is measured in a cell per millisecond.
Only after the uplink data is correctly parsed and recognized that it is transmitted on DRBs, the
number of PRBs used by PUSCH DRBs can be calculated. Therefore, if all HARQ
retransmission fails, the eNodeB cannot recognize that the data is transmitted on DRBs and the
corresponding used PRBs are not counted. During the adaptive uplink transmission, if HARQ
retransmission feedbacks were NACK and then ACK at last, the number of used PRBs is
estimated based on the data transmitted with ACK messages. As a result, the number of PRBs
actually used may differ from that calculated in these two scenarios.
In LTE TDD mode, only uplink subframes are measured. In a cell combination scenario, the
number of used PRBs in each physical cell is accumulated.
Formula
None
Unit
None

Related Features
L.ChMeas.PRB.UL.Used.A Multi-mode: None

vg GSM: None
UMTS: None
L.ULCoMP.RB Multi-mode: None

GSM: None
UMTS: None
LTE: LOFD-001066 Intra-eNodeB UL CoMP
TDLOFD-001066 Intra-eNodeB UL CoMP
L.ChMeas.PRB.UL.DrbUse Multi-mode: None

d.Avg GSM: None
UMTS: None
L.ChMeas.PRB.PUSCH.Av Multi-mode: None

g GSM: None
UMTS: None
2.2.20.2 Number of Used Downlink PRBs
Counters
Description
1526726740 L.ChMeas.PRB.DL. Average number of DBS3900 LTE/

Used.Avg used PDSCH PRBs BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

DrbUsed.Avg PRBs used by BTS3900 LTE/
PDSCH DRBs BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
The counters measure the average number of PRBs used by PDSCH and by PDSCH DRBs in
a cell. They are used to analyze the usage of downlink PRBs.
The number of downlink PDSCH PRBs is determined by the downlink traffic and quality of
signals.
Measurement Points
During a measurement period, the average number of PRBs used by PDSCH and by PDSCH
DRBs (in an SFN cell, the number of used PRBs is accumulated) is measured per millisecond
in a cell.
In LTE TDD mode, only the downlink subframes are recorded. In a cell combination scenario,
the number of used PRBs in each physical cell is accumulated.
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
2.2.20.3 Number of Used PUCCH

Counters
Description
1526727483 L.ChMeas.PRB.PU Average number of DBS3900 LTE/

CCH.Avg used PUCCH PRBs BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the average number of used PUCCH PRBs in a cell. It is used to analyze
the usage of PRBs over the PUCCH.
Measurement Points
During a measurement period, the average number of used PUCCH PRBs is measured in a cell
per millisecond.
In LTE TDD mode, only uplink subframes are measured.
Formula
None
Unit
None
Related Features
L.ChMeas.PRB.PUCCH.Av Multi-mode: None

g GSM: None
UMTS: None
2.2.20.4 Number of OFDM Symbols Occupied by the PDCCH

Counters
Description
1526728299 L.ChMeas.PDCCH. Number of times that DBS3900 LTE/

SymNum.1 the PDCCH occupies BTS3900 LTE/
one OFDM symbol BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

two OFDM symbols BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

three OFDM BTS3900A LTE/
symbols BTS3900L LTE/
BTS3900AL LTE,
BTS3900

four OFDM symbols BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of times that the PDCCH occupies n OFDM symbols in a cell,
where n ranges from 1 to 4.
Measurement Points
The number of OFDM symbols occupied by the PDCCH in a cell is measured within the
measurement period.
Formula
None

Unit
None
Related Features
L.ChMeas.PDCCH.Sym- Multi-mode: None

Num.1 GSM: None
UMTS: None
Physical Channel
Management

Num.2 GSM: None
UMTS: None
Physical Channel
Management

Num.3 GSM: None
UMTS: None
Physical Channel
Management

Num.4 GSM: None
UMTS: None
Physical Channel
Management
2.2.20.5 Number of PDCCH CCEs used in a cell

Counters
Description
1526728303 L.ChMeas.CCE.Co Number of PDCCH DBS3900 LTE/

mmUsed CCEs used for BTS3900 LTE/
common DCI BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728304 L.ChMeas.CCE.UL Number of PDCCH DBS3900 LTE/

Used CCEs used for uplink BTS3900 LTE/
DCI BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728305 L.ChMeas.CCE.DL Number of PDCCH DBS3900 LTE/

Used CCEs used for BTS3900 LTE/
downlink DCI BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728765 L.ChMeas.CCE.Ava Number of available DBS3900 LTE/

il PDCCH CCEs BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of available CCEs in a cell and the number of PDCCH CCEs
used by uplink DCI (including DCI 0), downlink DCI (including DCI 1, DCI 1A, DCI 1B, DCI
1C, DCI 1D, DCI 2, DCI 2A, and DCI 2B), and common DCI (including DCI 3 and DCI 3A)
in a cell.
Measurement Points
During a measurement period, these counters measure the number of available PDCCH CCEs
and the PDCCH CCEs used by each category of DCI in a cell.
Formula
None

Unit
None
Related Features
L.ChMeas.CCE.CommUsed Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management
L.ChMeas.CCE.ULUsed Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management
L.ChMeas.CCE.DLUsed Multi-mode: None

GSM: None
UMTS: None
Physical Channel
Management
L.ChMeas.CCE.Avail Multi-mode: None

GSM: None
UMTS: None
Management
2.2.20.6 Average Number of PRBs Occupied by CA UEs in a Cell

Counters
Description

PCell.Used.Avg downlink PRBs BTS3900 LTE/
occupied by CA UEs BTS3900A LTE/
that use the local cell BTS3900L LTE/
as their primary BTS3900AL LTE,
serving cell BTS3900

SCell.Used.Avg downlink PRBs BTS3900 LTE/
occupied by CA UEs BTS3900A LTE/
that use the local cell BTS3900L LTE/
as their secondary BTS3900AL LTE,
serving cell BTS3900
Description
The counters measure the average number of PRBs occupied by CA UEs that use the local cell
as their primary and that occupied by CA UEs that use the local cell as their secondary serving
cell in a cell.
Measurement Points
The average number of PRBs occupied by the CA UEs that use the local cell as their primary
or secondary serving cells on downlink PDSCHs is measured per millisecond within the
measurement period.
Formula
None
Unit
None

Related Features
L.ChMeas.PRB.DL.PCell.U Multi-mode: None

sed.Avg GSM: None
UMTS: None
2CC in 20MHz
LAOFD-00100201
Inter-Band Carrier
TDLAOFD-001002 2CC in 20MHz
TDLAOFD-001003 Carrier Aggregation for
Carrier Aggregation for
L.ChMeas.PRB.DL.SCell.U Multi-mode: None

sed.Avg GSM: None
UMTS: None
2CC in 20MHz
LAOFD-00100201
Inter-Band Carrier
2.2.20.7 Average Number of Available PRBs in a Cell

Counters
Description
1526728433 L.ChMeas.PRB.DL. Number of available DBS3900 LTE/

Avail downlink PRBs BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728434 L.ChMeas.PRB.UL. Number of available DBS3900 LTE/

Avail uplink PRBs BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of available uplink or downlink PRBs, which is related to the
system bandwidth. In single frequency network (SFN) or cell combination scenarios, the counter
values are the total number of PRBs in each physical cell. In a cell with customized bandwidth,
the actually usable PRBs are measured. In the carrier aggregation scenario, if a cell is configured
as a secondary serving cell and is not configured with an uplink frequency band, the number of
available PRBs is zero.
Measurement Points
The number of available downlink or uplink PRBs in a cell is sampled per second. At the end
of a measurement period, the average of these sampling results is used as the counter value.
Formula
None
Unit
None

Related Features
L.ChMeas.PRB.DL.Avail Multi-mode: None

GSM: None
UMTS: None
LTE: LAOFD-001001 Carrier Aggregation for
LAOFD-001002 Downlink 2CC in 20MHz
TDLOFD-001075 Carrier Aggregation for

SFN
L.ChMeas.PRB.UL.Avail Multi-mode: None

GSM: None
UMTS: None
LTE: LAOFD-001001 Carrier Aggregation for
LAOFD-001002 Downlink 2CC in 20MHz
TDLOFD-001075 Carrier Aggregation for

SFN
2.2.20.8 Average Number of PRBs Used by CEUs in a Cell
Counters
Description

CEU.Used.Avg PRBs used by uplink BTS3900 LTE/
CEUs in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

CEU.Used.Avg PRBs used by BTS3900 LTE/
downlink CEUs in a BTS3900A LTE/
cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the average number of PRBs used by uplink or downlink CEUs in a cell.

Measurement Points
The average number of PRBs used by uplink or downlink CEUs per millisecond in a cell is
measured within the measurement period.
Formula
None
Unit
None
Related Features
L.ChMeas.PRB.UL.CEU.Us Multi-mode: None

ed.Avg GSM: None
UMTS: None

TDLOFD-00101402
L.ChMeas.PRB.DL.CEU.Us Multi-mode: None

ed.Avg GSM: None
UMTS: None

TDLOFD-00101401
Cell Interference
Coordination
Cell Interference
Coordination
2.2.20.9 Average Number of PRBs Allocated for Frequency Selective Scheduling

Counters
Description

FSS.Avg PRBs allocated for BTS3900 LTE/
uplink frequency BTS3900A LTE/
selective scheduling BTS3900L LTE/
BTS3900AL LTE,
BTS3900

FSS.Avg PRBs allocated for BTS3900 LTE/
downlink frequency BTS3900A LTE/
selective scheduling BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the average number of PRBs allocated for uplink or downlink frequency
selective scheduling. They are used to analyze the PRB usage in uplink or downlink frequency
selective scheduling.
Measurement Points
The average number of PRBs allocated for uplink or downlink frequency selective scheduling
per millisecond in a cell is measured within the measurement period.
Formula
None
Unit
None
Related Features
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
2.2.20.10 Average Number of PRBs Allocated for Uplink Pre-scheduling
Counters
Description

PreSch.Used.Avg PRBs allocated for BTS3900 LTE/
uplink pre- BTS3900A LTE/
scheduling BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the average number of PRBs allocated for uplink pre-scheduling in a cell.
Measurement Points
During a measurement period, the average number of PRBs allocated for uplink pre-scheduling
is measured in a cell per millisecond.
In LTE TDD mode, only uplink subframes are measured.
Formula
None
Unit
None

Related Features
L.ChMeas.PRB.UL.PreSch. Multi-mode: None

Used.Avg GSM: None
UMTS: None
LOFD-001059 UL Pre-allocation Based on
TDLOFD-001059 SPID
UL Pre-allocation Based on
SPID
2.2.20.11 Number of Times of DTX for PDCCH Resource Allocation with a Specific
Aggregation Level in a Cell
Counters
Description
1526728664 L.ChMeas.PDCCH. Number of times of DBS3900 LTE/

DL.DTXNum.AggL DTX for PDCCH BTS3900 LTE/
vl1 resource allocation BTS3900A LTE/
with aggregation BTS3900L LTE/
level 1 in a cell BTS3900AL LTE,
BTS3900

BTS3900

BTS3900


Description

BTS3900
Description
After allocating PDCCH resources, the eNodeB detects the ACK, NACK, or DTX status of the
corresponding PDSCH resource on the PUCCH or PUSCH. Each time the eNodeB detects the
DTX, the corresponding counter is incremented by 1. The PDCCH resource allocations without
feedbacks (such as SIB, RAR, and paging messages) are not counted in the counter. The counter
is incremented if one of the following conditions is met: (1)The UE does not detect the PDCCH
resource allocation messages. (2) The eNodeB falsely determines that the ACK or NACK
messages as DTX messages.
Measurement Points
The corresponding counter is incremented by 1 each time the eNodeB detects DTX for PDCCH
resource allocation with aggregation level 1, 2, 4, or 8.
Formula
None
Unit
None
Related Features
L.ChMeas.PDCCH.DL.DT Multi-mode: None

XNum.AggLvl1 GSM: None
UMTS: None
Physical Channel
Management


UMTS: None
Physical Channel
Management

UMTS: None
Physical Channel
Management

UMTS: None
Physical Channel
Management
2.2.20.12 Number of Times of Successful PDCCH Resource Allocations with a

Specific Aggregation Level
Counters
Description

AggLvl1Num PDCCH resource BTS3900 LTE/
allocations with BTS3900A LTE/
aggregation level 1 BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900
Description
The counters measure the number of times PDCCH resource allocation with aggregation level
1, 2, 4, or 8. The PDCCH resource allocations in aggregation level without feedbacks (such as
SIB, RAR, and paging messages) are not counted.
Measurement Points
The corresponding counter is incremented by 1 each time the PDCCH resources with aggregation
level 1, 2, 4 or 8 are successfully allocated.
Formula
None
Unit
None

Related Features
L.ChMeas.PDCCH.AggLvl Multi-mode: None

1Num GSM: None
UMTS: None
Physical Channel
Management

2Num GSM: None
UMTS: None
Physical Channel
Management

4Num GSM: None
UMTS: None
Physical Channel
Management

8Num GSM: None
UMTS: None
Physical Channel
Management
2.2.21 Measurement related to MAC (Traffic.MAC.Cell)
Overview
The Traffic.MAC.Cell function subset measures the traffic volume on logical channels and
transport channels in different modulation modes in a cell.

Counters
Description
1526727352 L.Traffic.BCH.TB. Total number of bits V100R008C00,and

bits of TBs transmitted the mapping single-
on the BCH mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727353 L.Traffic.PCH.TB. Total number of bits V100R008C00,and

bits of TBs transmitted the mapping single-
on the PCH mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727354 L.Traffic.DL.SCH. Number of TBs V100R008C00,and

QPSK.TB initially transmitted the mapping single-
on the downlink SCH mode base station
in QPSK modulation version that
mode introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

16QAM.TB initially transmitted the mapping single-
in 16QAM version that
modulation mode introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

in 64QAM version that
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727357 L.Traffic.DL.SCH. Number of bits of V100R008C00,and

QPSK.TB.bits TBs initially the mapping single-
downlink SCH in version that
QPSK modulation introduce this
mode counter is:
eNodeB:Version
earlier than
V100R003C00

16QAM.TB.bits TBs initially the mapping single-
16QAM modulation introduce this
mode counter is:
eNodeB:Version
earlier than
V100R003C00

mode counter is:
eNodeB:Version
earlier than
V100R003C00

QPSK.TB.Retrans retransmitted on the the mapping single-
downlink SCH in mode base station
QPSK modulation version that
mode introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

16QAM.TB.Retran retransmitted on the the mapping single-
s downlink SCH in mode base station
16QAM modulation version that
mode introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

s downlink SCH in mode base station
mode introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

QPSK.TB.Retrans. TBs retransmitted on the mapping single-
bits the downlink SCH in mode base station
mode introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

16QAM.TB.Retran TBs retransmitted on the mapping single-
s.bits the downlink SCH in mode base station
mode introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

s.bits the downlink SCH in mode base station
mode introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526727366 L.Traffic.UL.SCH. Number of TBs V100R008C00,and

QPSK.TB initially transmitted the mapping single-
on the uplink SCH in mode base station
mode introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

mode introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

mode introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727369 L.Traffic.UL.SCH. Number of bits of V100R008C00,and

QPSK.TB.bits TBs initially the mapping single-
uplink SCH in QPSK version that
counter is:
eNodeB:Version
earlier than
V100R003C00

uplink SCH in version that
mode counter is:
eNodeB:Version
earlier than
V100R003C00


Description

uplink SCH in version that
mode counter is:
eNodeB:Version
earlier than
V100R003C00

QPSK.TB.Retrans retransmitted on the the mapping single-
uplink SCH in QPSK mode base station
modulation mode version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

s uplink SCH in mode base station
mode introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

s uplink SCH in mode base station
mode introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

QPSK.TB.Retrans. TBs retransmitted on the mapping single-
bits the uplink SCH in mode base station
mode introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

s.bits the uplink SCH in mode base station
mode introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

s.bits the uplink SCH in mode base station
mode introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526728180 L.Traffic.DL.SCH. Number of downlink V100R008C00,and

QPSK.ErrTB.Ibler error TBs after initial the mapping single-
transmission in mode base station
mode introduce this
counter is:
eNodeB:V100R003
C00

QPSK.ErrTB.Rble error TBs after the the mapping single-
r maximum number of mode base station
retransmissions in version that
mode is reached counter is:
eNodeB:V100R003
C00

16QAM.ErrTB.Ibl error TBs after initial the mapping single-
er transmission in mode base station
mode introduce this
counter is:
eNodeB:V100R003
C00


Description

16QAM.ErrTB.Rbl error TBs after the the mapping single-
er maximum number of mode base station
eNodeB:V100R003
C00

mode introduce this
counter is:
eNodeB:V100R003
C00

eNodeB:V100R003
C00
1526728186 L.Traffic.UL.SCH. Number of uplink V100R008C00,and

QPSK.ErrTB.Ibler error TBs after initial the mapping single-
transmission in mode base station
mode introduce this
counter is:
eNodeB:V100R003
C00

QPSK.ErrTB.Rble error TBs after the the mapping single-
r maximum number of mode base station
eNodeB:V100R003
C00


Description

mode introduce this
counter is:
eNodeB:V100R003
C00

eNodeB:V100R003
C00

mode introduce this
counter is:
eNodeB:V100R003
C00

eNodeB:V100R003
C00
1526728598 L.Traffic.UL.SCH. Maximum uplink V100R008C00,and

bits.Max traffic volume for the mapping single-
MAC TBs in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728663 L.Traffic.DL.SCH. Maximum downlink V100R008C00,and

bits.Max traffic volume for the mapping single-
MAC TBs in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
None
2.2.21.1 Total Number of Bits of TBs Transmitted on the BCH
Counters
Description
1526727352 L.Traffic.BCH.TB.b Total number of bits DBS3900 LTE/

its of TBs transmitted BTS3900 LTE/
on the BCH BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the total number of bits of transport blocks(TBs) transmitted on the
broadcast channel (BCH) in a cell. It is the sum of bits of system information block type 1 (SIB1)
and system information (SI) transmitted on the broadcast control channel (BCCH) over the air
interface.
Measurement Points
The counter is incremented by the number of bits of the TB each time the eNodeB transmits a
TB on the BCH in a cell.
Formula
None

Unit
bit
Related Features
L.Traffic.BCH.TB.bits Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002002 Transport Channel
LBFD-001005 Management
TDLBFD-002002 Modulation: DL/UL QPSK,

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM
2.2.21.2 Total Number of Bits of TBs Transmitted on the PCH
Counters
Description
1526727353 L.Traffic.PCH.TB.bi Total number of bits DBS3900 LTE/

ts of TBs transmitted BTS3900 LTE/
on the PCH BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The air interface paging message is transmitted on the paging channel (PCH). The counter
measures the total number of bits of TBs transmitted on the PCH in a cell.
Measurement Points
The counter is incremented by the number of bits of the TB each time the eNodeB transmits a
TB on the PCH in a cell.

Formula
None
Unit
bit
Related Features
L.Traffic.PCH.TB.bits Multi-mode: None

GSM: None
UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM
2.2.21.3 Number of TBs Initially Transmitted on the Downlink SCH
Counters
Description
1526727354 L.Traffic.DL.SCH.Q Number of TBs DBS3900 LTE/

PSK.TB initially transmitted BTS3900 LTE/
on the downlink SCH BTS3900A LTE/
in QPSK modulation BTS3900L LTE/
mode BTS3900AL LTE,
BTS3900
1526727355 L.Traffic.DL.SCH. Number of TBs DBS3900 LTE/

16QAM.TB initially transmitted BTS3900 LTE/
in 16QAM BTS3900L LTE/
modulation mode BTS3900AL LTE,
BTS3900


Description

in 64QAM BTS3900L LTE/
BTS3900
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.
result of the corresponding counter has a deviation.
Formula
None
Unit
None

Related Features
L.Traffic.DL.SCH.QPSK.T Multi-mode: None

B GSM: None
UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM
L.Traffic.DL.SCH. Multi-mode: None

16QAM.TB GSM: None
UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

64QAM.TB GSM: None
UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

2.2.21.4 Number of Bits of TBs Initially Transmitted on the Downlink SCH
Counters
Description
1526727357 L.Traffic.DL.SCH.Q Number of bits of DBS3900 LTE/

PSK.TB.bits TBs initially BTS3900 LTE/
downlink SCH in BTS3900L LTE/
QPSK modulation BTS3900AL LTE,
mode BTS3900
1526727358 L.Traffic.DL.SCH. Number of bits of DBS3900 LTE/

16QAM.TB.bits TBs initially BTS3900 LTE/
16QAM modulation BTS3900AL LTE,
mode BTS3900

mode BTS3900
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.
Measurement Points
The corresponding counter is incremented by the number of bits of the TB based on modulation
mode each time the eNodeB initially transmits a TB on the downlink SCH.
Formula
None
Unit
bit

Related Features

B.bits GSM: None
UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

16QAM.TB.bits GSM: None
UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

2.2.21.5 Number of TBs Retransmitted on the Downlink SCH
Counters
Description
1526727360 L.Traffic.DL.SCH.Q Number of TBs DBS3900 LTE/

PSK.TB.Retrans retransmitted on the BTS3900 LTE/
downlink SCH in BTS3900A LTE/
QPSK modulation BTS3900L LTE/
mode BTS3900AL LTE,
BTS3900

16QAM.TB.Retrans retransmitted on the BTS3900 LTE/
16QAM modulation BTS3900L LTE/
mode BTS3900AL LTE,
BTS3900

mode BTS3900AL LTE,
BTS3900
Description
The eNodeB determines an MCS index for retransmission of the UE based on the quality of the
downlink channel. Each MCS index corresponds to a modulation mode, such as QPSK, 16QAM,
and 64QAM. The counters measure the number of TBs retransmitted on the downlink SCH in
QPSK, 16QAM, and 64QAM modulation modes in a cell.
Measurement Points
retransmits a TB on the downlink SCH.
Formula
None
Unit
None

Related Features

B.Retrans GSM: None
UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

16QAM.TB.Retrans GSM: None
UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

2.2.21.6 Number of Bits of TBs Retransmitted on the Downlink SCH
Counters
Description
1526727363 L.Traffic.DL.SCH.Q Number of bits of DBS3900 LTE/

PSK.TB.Retrans.bits TBs retransmitted on BTS3900 LTE/
the downlink SCH in BTS3900A LTE/
mode BTS3900AL LTE,
BTS3900

16QAM.TB.Retrans. TBs retransmitted on BTS3900 LTE/
bits the downlink SCH in BTS3900A LTE/
mode BTS3900AL LTE,
BTS3900

bits the downlink SCH in BTS3900A LTE/
mode BTS3900AL LTE,
BTS3900
Description
downlink channel. Each MCS index corresponds to a modulation mode, such as QPSK, 16QAM,
and 64QAM. The counters measure the number of bits of TBs retransmitted on the downlink
SCH in QPSK, 16QAM, and 64QAM modulation modes in a cell.
Measurement Points
mode each time the eNodeB retransmits a TB on the downlink SCH.
Formula
None
Unit
bit

Related Features

B.Retrans.bits GSM: None
UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

16QAM.TB.Retrans.bits GSM: None
UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

2.2.21.7 Number of TBs Initially Transmitted on the Uplink SCH
Counters
Description
1526727366 L.Traffic.UL.SCH.Q Number of TBs DBS3900 LTE/

PSK.TB initially transmitted BTS3900 LTE/
on the uplink SCH in BTS3900A LTE/
mode BTS3900AL LTE,
BTS3900
1526727367 L.Traffic.UL.SCH. Number of TBs DBS3900 LTE/

mode BTS3900AL LTE,
BTS3900

mode BTS3900AL LTE,
BTS3900
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
receives a TB initially transmitted on the uplink SCH.
Formula
None
Unit
None

Related Features
L.Traffic.UL.SCH.QPSK.T Multi-mode: None

B GSM: None
UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM
L.Traffic.UL.SCH. Multi-mode: None

16QAM.TB GSM: None
UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

64QAM.TB GSM: None
UMTS: None
LOFD-001006 Management
TDLBFD-002002 UL 64QAM
TDLOFD-001006 Transport Channel

Management
UL 64QAM
2.2.21.8 Number of Bits of TBs Initially Transmitted on the Uplink SCH

Counters
Description
1526727369 L.Traffic.UL.SCH.Q Number of bits of DBS3900 LTE/

PSK.TB.bits TBs initially BTS3900 LTE/
uplink SCH in QPSK BTS3900L LTE/
BTS3900
1526727370 L.Traffic.UL.SCH. Number of bits of DBS3900 LTE/

uplink SCH in BTS3900L LTE/
mode BTS3900

uplink SCH in BTS3900L LTE/
mode BTS3900
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
mode each time the eNodeB receives a TB initially transmitted on the uplink SCH.
Formula
None
Unit
bit

Related Features

B.bits GSM: None
UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None

Management
UL 64QAM
2.2.21.9 Number of TBs Retransmitted over the Uplink SCH

Counters
Description
1526727372 L.Traffic.UL.SCH.Q Number of TBs DBS3900 LTE/

PSK.TB.Retrans retransmitted on the BTS3900 LTE/
uplink SCH in QPSK BTS3900A LTE/
modulation mode BTS3900L LTE/
BTS3900AL LTE,
BTS3900

uplink SCH in BTS3900A LTE/
mode BTS3900AL LTE,
BTS3900

uplink SCH in BTS3900A LTE/
mode BTS3900AL LTE,
BTS3900
Description
uplink channel. Each MCS index corresponds to a modulation mode, such as QPSK, 16QAM,
and 64QAM. The counters measure the number of TBs retransmitted on the uplink SCH in
QPSK, 16QAM, and 64QAM modulation modes in a cell.
Measurement Points
The number of TBs is incremented by 1 based on the modulation mode each time the eNodeB
receives a TB retransmitted over the uplink SCH.
Formula
None
Unit
None

Related Features

B.Retrans GSM: None
UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None

Management
UL 64QAM
2.2.21.10 Number of Bits of TBs Retransmitted on the Uplink SCH

Counters
Description
1526727375 L.Traffic.UL.SCH.Q Number of bits of DBS3900 LTE/

PSK.TB.Retrans.bits TBs retransmitted on BTS3900 LTE/
the uplink SCH in BTS3900A LTE/
mode BTS3900AL LTE,
BTS3900

bits the uplink SCH in BTS3900A LTE/
mode BTS3900AL LTE,
BTS3900

bits the uplink SCH in BTS3900A LTE/
mode BTS3900AL LTE,
BTS3900
Description
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
mode each time the eNodeB receives a TB retransmitted on the uplink SCH.
Formula
None
Unit
bit

Related Features

B.Retrans.bits GSM: None
UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None

DL/UL 16QAM, DL
TDLBFD-001005 64QAM
Transport Channel
Management
DL/UL 16QAM, DL
64QAM

UMTS: None

Management
UL 64QAM
2.2.21.11 Number of Downlink Error TBs After Initial Transmission

Counters
Description
1526728180 L.Traffic.DL.SCH.Q Number of downlink DBS3900 LTE/

PSK.ErrTB.Ibler error TBs after initial BTS3900 LTE/
transmission in BTS3900A LTE/
mode BTS3900AL LTE,
BTS3900
1526728182 L.Traffic.DL.SCH. Number of downlink DBS3900 LTE/

16QAM.ErrTB.Ibler error TBs after initial BTS3900 LTE/
mode BTS3900AL LTE,
BTS3900

mode BTS3900AL LTE,
BTS3900
Description
The counters measure the number of downlink error TBs after initial transmission in QPSK,
16QAM, and 64QAM modulation mode.
Measurement Points
The corresponding counter is incremented by 1 based on the modulation mode each time the
eNodeB receives a downlink error TB indicator after initial transmission.
Formula
None
Unit
None

Related Features
L.Traffic.DL.SCH.QPSK.Er Multi-mode: None

rTB.Ibler GSM: None
UMTS: None
Transport Channel
Management

16QAM.ErrTB.Ibler GSM: None
UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management
2.2.21.12 Number of Downlink Error TBs After the Maximum Number of

Retransmissions Is Reached
Counters
Description
1526728181 L.Traffic.DL.SCH.Q Number of downlink DBS3900 LTE/

PSK.ErrTB.Rbler error TBs after the BTS3900 LTE/
maximum number of BTS3900A LTE/
retransmissions in BTS3900L LTE/
mode is reached BTS3900


Description

16QAM.ErrTB.Rble error TBs after the BTS3900 LTE/
r maximum number of BTS3900A LTE/

Description
The counters measure the number of downlink error TBs after the maximum number of
retransmissions in QPSK, 16QAM, or 64QAM modulation mode is reached.
Measurement Points
eNodeB receives a downlink error TB indicator after the maximum number of retransmissions
is reached.
Formula
None
Unit
None
Related Features
L.Traffic.DL.SCH.QPSK.Er Multi-mode: None

rTB.Rbler GSM: None
UMTS: None
Transport Channel
Management


16QAM.ErrTB.Rbler GSM: None
UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management
2.2.21.13 Number of Uplink Error TBs After Initial Transmission
Counters
Description
1526728186 L.Traffic.UL.SCH.Q Number of uplink DBS3900 LTE/

PSK.ErrTB.Ibler error TBs after initial BTS3900 LTE/
mode BTS3900AL LTE,
BTS3900
1526728188 L.Traffic.UL.SCH. Number of uplink DBS3900 LTE/

mode BTS3900AL LTE,
BTS3900

mode BTS3900AL LTE,
BTS3900

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
Transport Channel
Management

UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management

2.2.21.14 Number of Uplink Error TBs After the Maximum Number of

Retransmissions Is Reached
Counters
Description
1526728187 L.Traffic.UL.SCH.Q Number of uplink DBS3900 LTE/

PSK.ErrTB.Rbler error TBs after the BTS3900 LTE/
maximum number of BTS3900A LTE/


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
L.Traffic.UL.SCH.QPSK.Er Multi-mode: None

rTB.Rbler GSM: None
UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management

UMTS: None
Transport Channel
Management
2.2.21.15 Maximum Traffic Volume for MAC TBs in a Cell
Counters
Description
1526728598 L.Traffic.UL.SCH.b Maximum uplink DBS3900 LTE/

its.Max traffic volume for BTS3900 LTE/
MAC TBs in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1526728663 L.Traffic.DL.SCH.b Maximum downlink DBS3900 LTE/

its.Max traffic volume for BTS3900 LTE/
MAC TBs in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the maximum uplink and downlink traffic volumes for MAC SDUs in a
cell.
Measurement Points
The number of bits of payloads transmitted in uplink or downlink (excluding retransmission) at
the MAC layer is sampled per second in a cell. At the end of a measurement period, the maximum
of the sampling results per type is used as the value of the corresponding counter.
Formula
None
Unit
bit
Related Features
L.Traffic.UL.SCH.bits.Max Multi-mode: None

GSM: None
UMTS: None
L.Traffic.DL.SCH.bits.Max Multi-mode: None

GSM: None
UMTS: None

2.2.22 Measurement related to the number of User

(Traffic.User.Cell)
Overview
The Traffic.User.Cell function subset measures the number of users in different uplink or
downlink scenarios in a cell. The numbers of users are measured in different mechanisms. One
mechanism is based on the user state within the sampling period. For example, the
L.Traffic.User.Data.Avg counter measures data transmission within a sampling period. Another
mechanism is based on the user state at the sampling time. For example, the L.Traffic.User.Avg
counter measures the number of users in RRC_CONNECTED mode at the sampling time. The
two mechanisms determine that the two kinds of counters may have different impacts on inter-
counter relationships in different scenarios. To count the number of CA users in an SCell, only
the L.Traffic.User.SCell.DL.Avg and L.Traffic.User.SCell.DL.Max counters are used, but other
counters related to the number of users are not used.
Counters
Description
1526727378 L.Traffic.User.Avg Average number of V100R008C00,and

users in a cell the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727379 L.Traffic.User.Max Maximum number of V100R008C00,and

users in a cell the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727380 L.Traffic.CEU.Avg Average number of V100R008C00,and

downlink cell edge the mapping single-
users (CEUs) in a cell mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526727381 L.Traffic.CEU.Ma Maximum number of V100R008C00,and

x downlink cell edge the mapping single-
users (CEUs) in a cell mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727382 L.Traffic.User.UL Average number of V100R008C00,and

Data.Avg UEs with data in the the mapping single-
uplink buffer mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727383 L.Traffic.User.UL Maximum number of V100R008C00,and

Data.Max UEs with data in the the mapping single-
uplink buffer mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727384 L.Traffic.User.DL Average number of V100R008C00,and

Data.Avg UEs with data in the the mapping single-
downlink buffer mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727385 L.Traffic.User.DL Maximum number of V100R008C00,and

Data.Max UEs with data in the the mapping single-
downlink buffer mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526728333 L.Traffic.User.Ulsy Average number of V100R008C00,and

nc.Avg UL synchronized the mapping single-
users in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00
1526728335 L.Traffic.User.Dat Maximum number of V100R008C00,and

a.Max users with data in the the mapping single-
buffer mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00
1526728336 L.Traffic.User.Dat Average number of V100R008C00,and

a.Avg users with data in the the mapping single-
buffer mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00
1526728338 L.ULCoMP.User.A Average number of V100R008C00,and

vg UL CoMP UEs in a the mapping single-
version that
introduce this
counter is:
eNodeB:V100R005
C00
1526728339 L.ULCoMP.User. Maximum number of V100R008C00,and

Max UL CoMP UEs in a the mapping single-
version that
introduce this
counter is:
eNodeB:V100R005
C00


Description
1526728426 L.Traffic.User.PCe Average number of V100R008C00,and

ll.DL.Avg downlink CA UEs the mapping single-
that use the local cell mode base station
as their primary version that
serving cells introduce this
counter is:
eNodeB:V100R006
C00
1526728427 L.Traffic.User.SCel Average number of V100R008C00,and

l.DL.Avg downlink CA UEs the mapping single-
as their secondary version that
counter is:
eNodeB:V100R006
C00
1526728445 L.Traffic.ActiveUs Total number of V100R008C00,and

er.UL.QCI.Total activated UEs with a the mapping single-
QCI (or an extended mode base station
QCI) in the uplink version that
buffer introduce this
counter is:
eNodeB:V100R006
C00
1526728446 L.Traffic.ActiveUs Number of activated V100R008C00,and

er.UL.QCI.1 UEs with the QCI of the mapping single-
1 in the uplink buffer mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

version that
introduce this
counter is:
eNodeB:V100R006
C00


Description

version that
introduce this
counter is:
eNodeB:V100R006
C00

version that
introduce this
counter is:
eNodeB:V100R006
C00

version that
introduce this
counter is:
eNodeB:V100R006
C00

version that
introduce this
counter is:
eNodeB:V100R006
C00

version that
introduce this
counter is:
eNodeB:V100R006
C00


Description

version that
introduce this
counter is:
eNodeB:V100R006
C00

version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728455 L.Traffic.ActiveUs Total number of V100R008C00,and

er.DL.QCI.Total activated UEs with a the mapping single-
QCI (or an extended mode base station
QCI) in the downlink version that
buffer introduce this
counter is:
eNodeB:V100R006
C00

er.DL.QCI.1 UEs with the QCI of the mapping single-
1 in the downlink mode base station
buffer version that
introduce this
counter is:
eNodeB:V100R006
C00

buffer version that
introduce this
counter is:
eNodeB:V100R006
C00


Description

buffer version that
introduce this
counter is:
eNodeB:V100R006
C00

buffer version that
introduce this
counter is:
eNodeB:V100R006
C00

buffer version that
introduce this
counter is:
eNodeB:V100R006
C00

buffer version that
introduce this
counter is:
eNodeB:V100R006
C00

buffer version that
introduce this
counter is:
eNodeB:V100R006
C00


Description

buffer version that
introduce this
counter is:
eNodeB:V100R006
C00

buffer version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728473 L.Traffic.ULCEU. Average number of V100R008C00,and

Avg uplink cell edge users the mapping single-
(CEUs) in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728474 L.Traffic.ULCEU. Maximum number of V100R008C00,and

Max uplink cell edge users the mapping single-
(CEUs) in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728481 L.Traffic.User.SRS Average number of V100R008C00,and

.Avg UEs configured with the mapping single-
sounding reference mode base station
signal (SRS) version that
resources in a cell introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728482 L.Traffic.User.SRS Maximum number of V100R008C00,and

.Max UEs configured with the mapping single-
sounding reference mode base station
signal (SRS) version that
resources in a cell introduce this
counter is:
eNodeB:V100R006
C00
1526728496 L.Traffic.User.TtiB Average number of V100R008C00,and

undling.Avg UEs on which TTI the mapping single-
bundling takes effect mode base station
introduce this
counter is:
eNodeB:V100R006
C00
1526728516 L.Traffic.User.PCe Maximum number of V100R008C00,and

ll.DL.Max downlink CA UEs the mapping single-
as their primary version that
counter is:
eNodeB:V100R006
C00
1526728517 L.Traffic.User.SCel Maximum number of V100R008C00,and

l.DL.Max downlink CA UEs the mapping single-
as their secondary version that
counter is:
eNodeB:V100R006
C00
1526728524 L.Traffic.User.RoH Maximum number of V100R008C00,and

C.Max UEs on which ROHC the mapping single-
takes effect in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728525 L.Traffic.User.RoH Average number of V100R008C00,and

C.Avg UEs on which ROHC the mapping single-
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728546 L.Traffic.User.Cdr Average number of V100R008C00,and

x.Avg UEs on which DRX the mapping single-
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728969 L.Traffic.ActiveUs Average number of V100R008C00,and

er.DL.Avg activated UEs in the mapping single-
downlink mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728970 L.Traffic.ActiveUs Maximum number of V100R008C00,and

er.DL.Max activated UEs in the mapping single-
downlink mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

er.UL.Avg activated UEs in the mapping single-
uplink mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description

er.UL.Max activated UEs in the mapping single-
uplink mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

er.Avg activated UEs the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

er.Max activated UEs the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
None
2.2.22.1 Number of Users in a Cell
Counters
Description
1526727378 L.Traffic.User.Avg Average number of DBS3900 LTE/

users in a cell BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1526727379 L.Traffic.User.Max Maximum number of DBS3900 LTE/

users in a cell BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the average and maximum number of UEs in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of UEs in
connected mode in a cell is sampled per second. At the end of a measurement period, the average
and maximum of these sampling results are used as the values of the corresponding counters.
Formula
None
Unit
None
Related Features
L.Traffic.User.Avg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.User.Max Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management

2.2.22.2 Number of Cell Edge Users in a Cell
Counters
Description
1526727380 L.Traffic.CEU.Avg Average number of DBS3900 LTE/

downlink cell edge BTS3900 LTE/
users (CEUs) in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526727381 L.Traffic.CEU.Max Maximum number of DBS3900 LTE/

downlink cell edge BTS3900 LTE/
users (CEUs) in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728473 L.Traffic.ULCEU.A Average number of DBS3900 LTE/

vg uplink cell edge users BTS3900 LTE/
(CEUs) in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728474 L.Traffic.ULCEU.M Maximum number of DBS3900 LTE/

ax uplink cell edge users BTS3900 LTE/
(CEUs) in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the average and maximum number of uplink and downlink CEUs in a
cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of uplink
and downlink CEUs in connected mode in a cell is sampled per second. At the end of a
measurement period, the average and maximum of these sampling results are used as the values
of the corresponding counters.

Formula
None
Unit
None
Related Features
L.Traffic.CEU.Avg Multi-mode: None

GSM: None
UMTS: None
LOFD-00101401 RRC Connection

Management
TDLOFD-00101401
LBFD-00202201 Cell Interference
TDLBFD-00202201 Coordination
Cell Interference
Coordination
Downlink Static Inter-Cell
L.Traffic.CEU.Max Multi-mode: None

GSM: None
UMTS: None

Management
TDLOFD-00101401
LBFD-00202201 Cell Interference
TDLBFD-00202201 Coordination
Cell Interference
Coordination

L.Traffic.ULCEU.Avg Multi-mode: None

GSM: None
UMTS: None

Management
TDLOFD-00101402
LBFD-00202202 Interference Coordination
TDLBFD-00202202 Uplink Dynamic Inter-Cell
Uplink Static Inter-Cell
L.Traffic.ULCEU.Max Multi-mode: None

GSM: None
UMTS: None

Management
TDLOFD-00101402
LBFD-00202202 Interference Coordination
TDLBFD-00202202 Uplink Dynamic Inter-Cell
2.2.22.3 Number of UEs with Data in the Uplink Buffer

Counters
Description
1526727382 L.Traffic.User.ULD Average number of DBS3900 LTE/

ata.Avg UEs with data in the BTS3900 LTE/
uplink buffer BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526727383 L.Traffic.User.ULD Maximum number of DBS3900 LTE/

ata.Max UEs with data in the BTS3900 LTE/
uplink buffer BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the average and maximum number of UEs with data in the uplink buffer
in a cell.
Measurement Points
The counters are measured based on the user state within the sampling period. The number of
UEs that are in RRC_CONNECTED mode and have data in the uplink buffer in a cell is sampled
per second. At the end of a measurement period, the average and maximum of these sampling
results are used as the values of the corresponding counters.
Formula
None
Unit
None

Related Features
L.Traffic.User.ULData.Avg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.User.ULData.Max Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
2.2.22.4 Number of UEs with Data in the Downlink Buffer
Counters
Description
1526727384 L.Traffic.User.DLD Average number of DBS3900 LTE/

ata.Avg UEs with data in the BTS3900 LTE/
downlink buffer BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526727385 L.Traffic.User.DLD Maximum number of DBS3900 LTE/

ata.Max UEs with data in the BTS3900 LTE/
downlink buffer BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the average and maximum number of UEs with data in the downlink buffer
in a cell.

Measurement Points
The counters are measured based on the user state within the sampling period. The number of
UEs that are in RRC_CONNECTED mode and have data in the downlink buffer in a cell is
sampled per second. At the end of a measurement period, the average and maximum of these
sampling results are used as the values of the corresponding counters.
Formula
None
Unit
None
Related Features
L.Traffic.User.DLData.Avg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.User.DLData.Max Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
2.2.22.5 Number of UL Synchronized Users in a Cell

Counters
Description
1526728333 L.Traffic.User.Ulsyn Average number of DBS3900 LTE/

c.Avg UL synchronized BTS3900 LTE/
users in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
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
Formula
None
Unit
None
Related Features
L.Traffic.User.Ulsync.Avg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
2.2.22.6 Number of UEs Transmitting or Receiving Data in a Cell

Counters
Description
1526728335 L.Traffic.User.Data. Maximum number of DBS3900 LTE/

Max users with data in the BTS3900 LTE/
buffer BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728336 L.Traffic.User.Data. Average number of DBS3900 LTE/

Avg users with data in the BTS3900 LTE/
buffer BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the average and maximum number of users transmitting or receiving data
in a cell.
Measurement Points
The counters are measured based on the status of users within the sampling period. The number
of users in connected mode and with data in the buffer in a cell is sampled per second. At the
end of a measurement period, the average and maximum of these sampling results is used as the
value of the corresponding counters.
Formula
None
Unit
None

Related Features
L.Traffic.User.Data.Max Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.User.Data.Avg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
2.2.22.7 Number of UL CoMP UEs in a Cell
Counters
Description
1526728338 L.ULCoMP.User.Av Average number of DBS3900 LTE/

g UL CoMP UEs in a BTS3900 LTE/
cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728339 L.ULCoMP.User.M Maximum number of DBS3900 LTE/

ax UL CoMP UEs in a BTS3900 LTE/
cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the maximum number and the average number of UEs using uplink (UL)
coordinated multi-point (CoMP) in a cell within a measurement period.

Measurement Points
This kind of counters are measured based on the status of users in the sampling period. The
number of all UEs using UL CoMP in a cell is sampled per second. At the end of a measurement
period, the maximum and the average of these sampling results are used as the values of the
corresponding counters.
Formula
None
Unit
None
Related Features
L.ULCoMP.User.Avg Multi-mode: None

GSM: None
UMTS: None
L.ULCoMP.User.Max Multi-mode: None

GSM: None
UMTS: None
2.2.22.8 Number of CA UEs in a Cell
Counters
Description
1526728426 L.Traffic.User.PCell Average number of DBS3900 LTE/

.DL.Avg downlink CA UEs BTS3900 LTE/
that use the local cell BTS3900A LTE/
as their primary BTS3900L LTE/
serving cells BTS3900AL LTE,
BTS3900


Description
1526728427 L.Traffic.User.SCell Average number of DBS3900 LTE/

.DL.Avg downlink CA UEs BTS3900 LTE/
as their secondary BTS3900L LTE/
BTS3900
1526728516 L.Traffic.User.PCell Maximum number of DBS3900 LTE/

.DL.Max downlink CA UEs BTS3900 LTE/
as their primary BTS3900L LTE/
BTS3900
1526728517 L.Traffic.User.SCell Maximum number of DBS3900 LTE/

.DL.Max downlink CA UEs BTS3900 LTE/
as their secondary BTS3900L LTE/
BTS3900
Description
The counters measure the average and maximum number of downlink CA UEs that use the local
cell as their primary serving cells and the average and maximum number of downlink CA UEs
that use the local cell as their secondary serving cells.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of all
downlink CA UEs in connected mode in a cell that use the local cell as their primary serving
cells or secondary serving cells is sampled per second. At the end of a measurement period, the
average and maximum of these sampling results are used as the values of the corresponding
counters.
Formula
None
Unit
None

Related Features
L.Traffic.User.PCell.DL.Av Multi-mode: None

g GSM: None
UMTS: None
2CC in 20MHz
LAOFD-00100201
Inter-Band Carrier
L.Traffic.User.SCell.DL.Av Multi-mode: None

g GSM: None
UMTS: None
2CC in 20MHz
LAOFD-00100201
Inter-Band Carrier

L.Traffic.User.PCell.DL.Ma Multi-mode: None

x GSM: None
UMTS: None
2CC in 20MHz
LAOFD-00100201
Inter-Band Carrier
L.Traffic.User.SCell.DL.Ma Multi-mode: None

x GSM: None
UMTS: None
2CC in 20MHz
LAOFD-00100201
Inter-Band Carrier
2.2.22.9 Average Number of Activated UEs with a Specific QCI in the Uplink Buffer

Counters
Description
1526728445 L.Traffic.ActiveUse Total number of DBS3900 LTE/

r.UL.QCI.Total activated UEs with a BTS3900 LTE/
QCI (or an extended BTS3900A LTE/
QCI) in the uplink BTS3900L LTE/
buffer BTS3900AL LTE,
BTS3900
1526728446 L.Traffic.ActiveUse Number of activated DBS3900 LTE/

r.UL.QCI.1 UEs with the QCI of BTS3900 LTE/
1 in the uplink buffer BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900L LTE/
BTS3900AL LTE,
BTS3900
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
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.Q Multi-mode: None

CI.Total GSM: None
UMTS: None
RRC Connection
Management

CI.1 GSM: None
UMTS: None
RRC Connection
Management

CI.2 GSM: None
UMTS: None
RRC Connection
Management

CI.3 GSM: None
UMTS: None
RRC Connection
Management

CI.4 GSM: None
UMTS: None
RRC Connection
Management


CI.5 GSM: None
UMTS: None
RRC Connection
Management

CI.6 GSM: None
UMTS: None
RRC Connection
Management

CI.7 GSM: None
UMTS: None
RRC Connection
Management

CI.8 GSM: None
UMTS: None
RRC Connection
Management

CI.9 GSM: None
UMTS: None
RRC Connection
Management
2.2.22.10 Average Number of Activated UEs with a Specific QCI in the Downlink
Buffer

Counters
Description
1526728455 L.Traffic.ActiveUse Total number of DBS3900 LTE/

r.DL.QCI.Total activated UEs with a BTS3900 LTE/
QCI (or an extended BTS3900A LTE/
QCI) in the downlink BTS3900L LTE/
buffer BTS3900AL LTE,
BTS3900

r.DL.QCI.1 UEs with the QCI of BTS3900 LTE/
1 in the downlink BTS3900A LTE/
buffer BTS3900L LTE/
BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900


Description

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900

BTS3900AL LTE,
BTS3900
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
RRC_CONNECTED mode that have data in the downlink buffer with a specific QCI
(standardized or extended QCI) in a cell is sampled per millisecond. At the end of a measurement
period, the average of these sampling results is used as the values of the corresponding counters.
The sum of these values is used as the value of the L.Traffic.ActiveUser.DL.QCI.Total counter.
Formula
None
Unit
None

Related Features
L.Traffic.ActiveUser.DL.Q Multi-mode: None

CI.Total GSM: None
UMTS: None
RRC Connection
Management

CI.1 GSM: None
UMTS: None
RRC Connection
Management

CI.2 GSM: None
UMTS: None
RRC Connection
Management

CI.3 GSM: None
UMTS: None
RRC Connection
Management

CI.4 GSM: None
UMTS: None
RRC Connection
Management


CI.5 GSM: None
UMTS: None
RRC Connection
Management

CI.6 GSM: None
UMTS: None
RRC Connection
Management

CI.7 GSM: None
UMTS: None
RRC Connection
Management

CI.8 GSM: None
UMTS: None
RRC Connection
Management

CI.9 GSM: None
UMTS: None
RRC Connection
Management
2.2.22.11 Number of UEs Configured with SRS Resources in a Cell

Counters
Description
1526728481 L.Traffic.User.SRS. Average number of DBS3900 LTE/

Avg UEs configured with BTS3900 LTE/
sounding reference BTS3900A LTE/
signal (SRS) BTS3900L LTE/
resources in a cell BTS3900AL LTE,
BTS3900
1526728482 L.Traffic.User.SRS. Maximum number of DBS3900 LTE/

Max UEs configured with BTS3900 LTE/
sounding reference BTS3900A LTE/
signal (SRS) BTS3900L LTE/
resources in a cell BTS3900AL LTE,
BTS3900
Description
The counters measure the average and maximum number of UEs configured with SRS resources
in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of UEs
allocated SRS resources in connected mode in a cell is sampled per second. At the end of a
measurement period, the average and maximum of these sampling results are used as the values
of the corresponding counters.
Formula
None
Unit
None

Related Features
L.Traffic.User.SRS.Avg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.User.SRS.Max Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
2.2.22.12 Number of UEs on Which TTI Bundling Takes Effect in a Cell
Counters
Description
1526728496 L.Traffic.User.TtiBu Average number of DBS3900 LTE/

ndling.Avg UEs on which TTI BTS3900 LTE/
bundling takes effect BTS3900A LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the average number of UEs on which TTI bundling takes effect in a cell.
Measurement Points
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
LTE: LOFD-001048 TTI Bundling
TDLOFD-001048 TTI Bundling
2.2.22.13 Number of UEs on Which ROHC Takes Effect in a Cell
Counters
Description
1526728524 L.Traffic.User.RoH Maximum number of DBS3900 LTE/

C.Max UEs on which ROHC BTS3900 LTE/
takes effect in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728525 L.Traffic.User.RoH Average number of DBS3900 LTE/

C.Avg UEs on which ROHC BTS3900 LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the average and maximum number of UEs on which ROHC takes effect
in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of connected
UEs on which ROHC takes effect in a cell is sampled per second. At the end of a measurement

period, the average and maximum of these sampling results are used as the values of the
corresponding counters.
Formula
None
Unit
None
Related Features
L.Traffic.User.RoHC.Max Multi-mode: None

GSM: None
UMTS: None
(ROHC)
L.Traffic.User.RoHC.Avg Multi-mode: None

GSM: None
UMTS: None
(ROHC)
2.2.22.14 Number of UEs on Which DRX Takes Effect in a Cell
Counters
Description
1526728546 L.Traffic.User.Cdrx. Average number of DBS3900 LTE/

Avg UEs on which DRX BTS3900 LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
The counter measures the average number of UEs on which DRX takes effect in a cell.
Measurement Points
The counters are measured based on the user state at the sampling time. The number of connected
UEs on which DRX takes effect in a cell is sampled per second. At the end of a measurement
period, the average of these sampling results is used as the counter value.
Formula
None
Unit
None
Related Features
L.Traffic.User.Cdrx.Avg Multi-mode: None

GSM: None
UMTS: None
LBFD-002017 DRX
2.2.22.15 Number of Activated UEs in the Downlink in a Cell
Counters
Description
1526728969 L.Traffic.ActiveUse Average number of DBS3900 LTE/

r.DL.Avg activated UEs in BTS3900 LTE/
downlink BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728970 L.Traffic.ActiveUse Maximum number of DBS3900 LTE/

r.DL.Max activated UEs in BTS3900 LTE/
downlink BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

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
Formula
None
Unit
None
Related Features
L.Traffic.ActiveUser.DL.Av Multi-mode: None

g GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.ActiveUser.DL.M Multi-mode: None

ax GSM: None
UMTS: None
RRC Connection
Management
2.2.22.16 Number of Activated UEs in the Uplink in a Cell

Counters
Description

r.UL.Avg activated UEs in BTS3900 LTE/
uplink BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

r.UL.Max activated UEs in BTS3900 LTE/
uplink BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of UEs that have data in the uplink buffer in a cell.
Measurement Points
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
Formula
None
Unit
None

Related Features
L.Traffic.ActiveUser.UL.Av Multi-mode: None

g GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.ActiveUser.UL.M Multi-mode: None

ax GSM: None
UMTS: None
RRC Connection
Management
2.2.22.17 Number of Activated UEs in a Cell
Counters
Description

r.Avg activated UEs BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

r.Max activated UEs BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of UEs that have data in the buffer in a cell.

Measurement Points
are in RRC_CONNECTED mode and have data in either the downlink or uplink buffer in a cell
is sampled per millisecond. At the end of a measurement period, the average and maximum of
these sampling results are used as the values of the corresponding counters.
Formula
None
Unit
None
Related Features
L.Traffic.ActiveUser.Avg Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
L.Traffic.ActiveUser.Max Multi-mode: None

GSM: None
UMTS: None
RRC Connection
Management
2.2.23 Measurement related to IRATHOOUT (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 2-99, Figure 2-100, and Figure 2-101.

Figure 2-99
Figure 2-100

Figure 2-101
Counters
Description
1526726986 L.IRATHO.E2C.Pr Number of inter- V100R008C00,and

epAttOut RAT handover the mapping single-
attempts from E- mode base station
UTRAN to version that
CDMA2000 introduce this
network counter is:
eNodeB:Version
earlier than
V100R003C00
1526726987 L.IRATHO.E2C.E Number of inter- V100R008C00,and

xecAttOut RAT Handovers the mapping single-
executions from E- mode base station
network counter is:
eNodeB:Version
earlier than
V100R003C00
1526726988 L.IRATHO.E2C.E Number of V100R008C00,and

xecSuccOut successful inter- the mapping single-
RAT handovers from mode base station
E-UTRAN to version that
network counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526726989 L.IRATHO.E2W.P Number of inter- V100R008C00,and

repAttOut RAT handover the mapping single-
WCDMA network introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526726990 L.IRATHO.E2W.E Number of inter- V100R008C00,and

xecAttOut RAT handover the mapping single-
counter is:
eNodeB:Version
earlier than
V100R003C00
1526726991 L.IRATHO.E2W.E Number of V100R008C00,and

counter is:
eNodeB:Version
earlier than
V100R003C00
1526726992 L.IRATHO.E2G.P Number of inter- V100R008C00,and

repAttOut RAT handover the mapping single-
UTRAN to GERAN version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526726993 L.IRATHO.E2G.E Number of inter- V100R008C00,and

introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526726994 L.IRATHO.E2G.E Number of V100R008C00,and

GERAN introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727226 L.IRATHO.E2T.Pr Number of inter- V100R008C00,and

epAttOut RAT Handover the mapping single-
Attempts from E- mode base station
UTRAN to TD- version that
SCDMA network introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727227 L.IRATHO.E2T.E Number of inter- V100R008C00,and

counter is:
eNodeB:Version
earlier than
V100R003C00
1526727228 L.IRATHO.E2T.E Number of V100R008C00,and

E-UTRAN to TD- version that
counter is:
eNodeB:Version
earlier than
V100R003C00

rep.FailOut.MME RAT handover the mapping single-
preparation failures mode base station
from E-UTRAN to version that
GERAN because of introduce this
faults on the MME counter is:
side eNodeB:V100R005
C00


Description

rep.FailOut.NoRe- RAT handover the mapping single-
ply preparation failures mode base station
GERAN because of introduce this
no responses from counter is:
GERAN eNodeB:V100R005
C00

rep.FailOut.Pre- RAT handover the mapping single-
pFailure preparation failures mode base station
GERAN due introduce this
tobecause GERAN counter is:
cells send handover eNodeB:V100R005
preparation failure C00
messages

ep.FailOut.MME RAT handover the mapping single-
TD-SCDMA introduce this
network because of counter is:
faults on the MME eNodeB:V100R005
side C00

ep.FailOut.NoRe- RAT handover the mapping single-
network due counter is:
tobecause of no eNodeB:V100R005
responses from TD- C00
SCDMA network

ep.FailOut.Pre- RAT handover the mapping single-
because TD- version that
cells send handover counter is:
preparation failure eNodeB:V100R005
messages C00


Description
1526728328 L.IRATHO.BlindH Number of inter- V100R008C00,and

O.E2W.PrepAttOu RAT blind handover the mapping single-
t attempts from E- mode base station
counter is:
eNodeB:V100R005
C00

O.E2W.ExecAttOu RAT blind the mapping single-
t handovers mode base station
executions from E- version that
UTRAN to introduce this
WCDMA network counter is:
eNodeB:V100R005
C00

O.E2G.ExecAttOut RAT blind the mapping single-
handovers mode base station
UTRAN to GERAN introduce this
counter is:
eNodeB:V100R005
C00
1526728313 L.IRATHO.BlindH Number of V100R008C00,and

O.E2W.ExecSucc- successful inter- the mapping single-
Out RAT blind mode base station
handovers from E- version that
eNodeB:V100R005
C00

O.E2G.ExecSucc- successful inter- the mapping single-
counter is:
eNodeB:V100R005
C00


Description

rep.FailOut.MME RAT handover the mapping single-
because of faults on counter is:
the MME side eNodeB:V100R005
C00

rep.FailOut.Pre- RAT handover the mapping single-
because WCDMA counter is:
network cells send eNodeB:V100R005
handover preparation C00
failure messages

rep.FailOut.NoRe- RAT handover the mapping single-
because of no counter is:
responses from eNodeB:V100R005
WCDMA network C00
1526728321 L.CSFB.PrepAtt Number of CSFB V100R008C00,and

indicators received the mapping single-
by the eNodeB mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00
1526728322 L.CSFB.PrepSucc Number of V100R008C00,and

successful CSFB the mapping single-
responses from the mode base station
eNodeB version that
introduce this
counter is:
eNodeB:V100R005
C00


Description
1526728323 L.CSFB.E2W Number of V100R008C00,and

procedures for CSFB the mapping single-
to WCDMA network mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00
1526728324 L.CSFB.E2G Number of V100R008C00,and

to GERAN mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00
1526728330 L.RRCRedirection. Number of V100R008C00,and

E2W.PrepAtt redirection the mapping single-
preparations from E- mode base station
counter is:
eNodeB:V100R005
C00

E2W redirections from E- the mapping single-
UTRAN to mode base station
introduce this
counter is:
eNodeB:V100R005
C00

E2G redirections from E- the mapping single-
UTRAN to GERAN mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00


Description

O.E2G.PrepAttOut RAT blind handover the mapping single-
introduce this
counter is:
eNodeB:V100R005
C00

E2G.PrepAtt redirection the mapping single-
preparations from E- mode base station
introduce this
counter is:
eNodeB:V100R005
C00
1526728386 L.CSFB.PrepAtt.Id Number of CSFB V100R008C00,and

le indicators received the mapping single-
by the eNodeB for mode base station
UEs in idle mode version that
introduce this
counter is:
eNodeB:V100R005
C01
1526728387 L.CSFB.PrepSucc.I Number of V100R008C00,and

dle successful CSFB the mapping single-
responses from the mode base station
eNodeB for UEs in version that
idle mode introduce this
counter is:
eNodeB:V100R005
C01
1526728388 L.CSFB.E2W.Idle Number of V100R008C00,and

for UEs in idle mode version that
introduce this
counter is:
eNodeB:V100R005
C01


Description
1526728400 L.IRATHO.SRVC Number of inter- V100R008C00,and

C.E2W.PrepAttOu RAT handover the mapping single-
t attempts from E- mode base station
for SRVCC counter is:
eNodeB:V100R006
C00

C.E2W.ExecAttOu RAT handover the mapping single-
t executions from E- mode base station
eNodeB:V100R006
C00
1526728402 L.IRATHO.SRVC Number of V100R008C00,and

C.E2W.ExecSucc- successful inter- the mapping single-
Out RAT handovers from mode base station
eNodeB:V100R006
C00

C.E2G.PrepAttOut RAT handover the mapping single-
for SRVCC introduce this
counter is:
eNodeB:V100R006
C00

C.E2G.ExecAttOut RAT handover the mapping single-
counter is:
eNodeB:V100R006
C00


Description

C.E2G.ExecSucc- successful inter- the mapping single-
GERAN for SRVCC introduce this
counter is:
eNodeB:V100R006
C00

C.E2T.PrepAttOut RAT handover the mapping single-
SCDMA network for introduce this
SRVCC counter is:
eNodeB:V100R006
C00

C.E2T.ExecAttOut RAT handover the mapping single-
SCDMA for SRVCC introduce this
counter is:
eNodeB:V100R006
C00

C.E2T.ExecSucc- successful inter- the mapping single-
E-UTRAN to TD- version that
counter is:
eNodeB:V100R006
C00
1526728409 L.CSFB.LCS.Pre- Number of LCS- V100R008C00,and

pAtt triggered CS fallback the mapping single-
indicators received mode base station
by the eNodeB version that
introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728410 L.CSFB.LCS.Pre- Number of responses V100R008C00,and

pSucc sent from the the mapping single-
eNodeB to MMEs mode base station
for CSFB triggered version that
by LCS introduce this
counter is:
eNodeB:V100R006
C00
1526728441 L.CCO.E2G.Exe- Number of CCO V100R008C00,and

cAttOut executions from E- the mapping single-
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728442 L.CCO.E2G.Exe- Number of V100R008C00,and

cSuccOut successful CCOs the mapping single-
from E-UTRAN to mode base station
GERAN version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728468 L.IRATHO.E2W.N Number of inter- V100R008C00,and

oNRT RAT initiation the mapping single-
failures from E- mode base station
because the adjacent counter is:
cell is not on the NRT eNodeB:V100R006
of the source cell C00
1526728469 L.IRATHO.E2T.N Number of inter- V100R008C00,and

because the adjacent counter is:
cell is not on the NRT eNodeB:V100R006
of the source cell C00


Description
1526728470 L.IRATHO.E2G.N Number of inter- V100R008C00,and

because the adjacent introduce this
cell is not on the NRT counter is:
of the source cell eNodeB:V100R006
C00
1526728471 L.IRATHO.E21xR Number of inter- V100R008C00,and

TT.NoNRT RAT initiation the mapping single-
CDMA2000 1xRTT introduce this
network because the counter is:
adjacent cell is not on eNodeB:V100R006
the NRT of the C00
source cell
1526728472 L.IRATHO.E2HR Number of inter- V100R008C00,and

PD.NoNRT RAT initiation the mapping single-
CDMA2000 HRPD introduce this
network because the counter is:
adjacent cell is not on eNodeB:V100R006
the NRT of the C00
source cell
1526728497 L.RRCRedirection. Number of CSFB- V100R008C00,and

E2W.CSFB based redirections the mapping single-
from E-UTRANs to mode base station
introduce this
counter is:
eNodeB:V100R006
C00

E2G.CSFB based redirections the mapping single-
GERAN version that
introduce this
counter is:
eNodeB:V100R006
C00


Description

E2C.CSFB based redirections the mapping single-
CDMA2000 version that
introduce this
counter is:
eNodeB:V100R006
C00

E2T.CSFB based redirections the mapping single-
TD-SCDMA version that
network introduce this
counter is:
eNodeB:V100R006
C00
1526728501 L.IRATHO.E2C.C Number of CSFB- V100R008C00,and

SFB.PrepAttOut based inter-RAT the mapping single-
handover preparation mode base station
attempts from E- version that
CDMA2000 counter is:
network eNodeB:V100R006
C00
1526728502 L.IRATHO.E2C.C Number of CSFB- V100R008C00,and

SFB.ExecAttOut based handover the mapping single-
execution attempts mode base station
network counter is:
eNodeB:V100R006
C00
1526728503 L.IRATHO.E2C.C Number of V100R008C00,and

SFB.ExecSuccOut successful CSFB- the mapping single-
based inter-RAT mode base station
handover executions version that
from E-UTRAN to introduce this
CDMA2000 counter is:
C00


Description
1526728504 L.IRATHO.E2W.C Number of CSFB- V100R008C00,and

eNodeB:V100R006
C00
1526728505 L.IRATHO.E2W.C Number of CSFB- V100R008C00,and

SFB.ExecAttOut based inter-RAT the mapping single-
handover execution mode base station
eNodeB:V100R006
C00
1526728506 L.IRATHO.E2W.C Number of V100R008C00,and

eNodeB:V100R006
C00
1526728507 L.IRATHO.E2G.C Number of CSFB- V100R008C00,and

counter is:
eNodeB:V100R006
C00
1526728508 L.IRATHO.E2G.C Number of CSFB- V100R008C00,and

counter is:
eNodeB:V100R006
C00


Description
1526728509 L.IRATHO.E2G.C Number of V100R008C00,and

GERAN counter is:
eNodeB:V100R006
C00
1526728510 L.IRATHO.E2T.C Number of CSFB- V100R008C00,and

UTRAN to TD- introduce this
SCDMA network counter is:
eNodeB:V100R006
C00
1526728511 L.IRATHO.E2T.C Number of CSFB- V100R008C00,and

eNodeB:V100R006
C00
1526728512 L.IRATHO.E2T.C Number of V100R008C00,and

TD-SCDMA counter is:
C00
1526728513 L.CSFB.PrepFail.C Number of CSFB V100R008C00,and

onflict preparation failures the mapping single-
because of process mode base station
conflict version that
introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728529 L.IRATHO.E2W.L Number of inter- V100R008C00,and

oad.PrepAttOut RAT handover the mapping single-
preparation attempts mode base station
triggered because of counter is:
high load eNodeB:V100R006
C00
1526728530 L.IRATHO.E2W.L Number of inter- V100R008C00,and

oad.ExecAttOut RAT handover the mapping single-
C00
1526728531 L.IRATHO.E2W.L Number of V100R008C00,and

oad.ExecSuccOut successful inter- the mapping single-
RAT handover mode base station
triggered because of eNodeB:V100R006
high load C00
1526728532 L.IRATHO.E2G.L Number of inter- V100R008C00,and

oad.PrepAttOut RAT handover the mapping single-
GERAN triggered introduce this
because of high load counter is:
eNodeB:V100R006
C00
1526728533 L.IRATHO.E2G.L Number of inter- V100R008C00,and

oad.ExecAttOut RAT handover the mapping single-
GERAN triggered introduce this
because of high load counter is:
eNodeB:V100R006
C00


Description
1526728534 L.IRATHO.E2G.L Number of V100R008C00,and

oad.ExecSuccOut successful inter- the mapping single-
C00

E2W.Load redirections from E- the mapping single-
UTRAN to mode base station
triggered because of introduce this
high load counter is:
eNodeB:V100R006
C00

E2G.Load redirections from E- the mapping single-
triggered because of version that
high load introduce this
counter is:
eNodeB:V100R006
C00
1526728542 L.IRATHO.E2W.R Number of inter- V100R008C00,and

egainHPLMN.Pre- RAT handover the mapping single-
pAttOut attempts from E- mode base station
triggered for UEs to counter is:
go back to the eNodeB:V100R006
HPLMN C00
1526728543 L.IRATHO.E2W.R Number of inter- V100R008C00,and

egainHPLMN.Exe- RAT handover the mapping single-
cAttOut executions from E- mode base station
HPLMN C00


Description
1526728544 L.IRATHO.E2W.R Number of V100R008C00,and

egainHPLMN.Exe- successful inter- the mapping single-
cSuccOut RAT handovers from mode base station
HPLMN C00
1526728560 L.IRATHO.E2W.N Number of inter- V100R008C00,and

oData.ExecAttOut RAT handover the mapping single-
triggered for UEs counter is:
that do not transmit eNodeB:V100R006
or receive data C00
1526728561 L.IRATHO.E2W.N Number of V100R008C00,and

oData.ExecSucc- successful inter- the mapping single-
triggered for UEs counter is:
that do not transmit eNodeB:V100R006
or receive data C00
1526728705 L.FlashCSFB.E2W Number of V100R008C00,and

procedures for flash the mapping single-
CSFB to WCDMA mode base station
introduce this
counter is:
eNodeB:V100R006
C00
1526728706 L.FlashCSFB.E2G Number of V100R008C00,and

procedures for flash the mapping single-
CSFB to GERAN mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728707 L.CSFB.PrepAtt.E Number of CSFB V100R008C00,and

mergency indicators received the mapping single-
by the eNodeB for mode base station
emergency calls version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728708 L.CSFB.PrepSucc. Number of responses V100R008C00,and

Emergency sent from the the mapping single-
eNodeB for CSFB mode base station
triggered for version that
emergency calls introduce this
counter is:
eNodeB:V100R006
C00
1526728709 L.CSFB.E2W.Eme Number of V100R008C00,and

rgency procedures for CSFB the mapping single-
triggered for version that
emergency calls introduce this
counter is:
eNodeB:V100R006
C00
1526728710 L.CSFB.E2G.Emer Number of V100R008C00,and

gency procedures for CSFB the mapping single-
to GERAN triggered mode base station
for emergency calls version that
introduce this
counter is:
eNodeB:V100R006
C00

O.E2T.PrepAttOut RAT blind handover the mapping single-
counter is:
eNodeB:V100R006
C00


Description

O.E2T.ExecAttOut RAT blind handover the mapping single-
counter is:
eNodeB:V100R006
C00

O.E2T.ExecSucc- successful inter- the mapping single-
eNodeB:V100R006
C00
1526728749 L.CSFB.E2T Number of V100R008C00,and

procedures for the mapping single-
SRVCC to TD- mode base station
SCDMA network version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728750 L.CSFB.E2T.Idle Number of V100R008C00,and

procedures for the mapping single-
SRVCC to TD- mode base station
SCDMA for UEs in version that
idle mode introduce this
counter is:
eNodeB:V100R006
C00

E2T.PrepAtt redirection the mapping single-
preparations to TD- mode base station
SCDMA network version that
introduce this
counter is:
eNodeB:V100R006
C00


Description

E2T redirections to TD- the mapping single-
SCDMA network mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728753 L.IRATHO.SRVC Number of CSFB- V100R008C00,and

C.LCS.E2W.Pre- based handover the mapping single-
eNodeB:V100R006
C00

C.LCS.E2W.Exe- based handover the mapping single-
eNodeB:V100R006
C00

C.LCS.E2W.Exe- successful CSFB- the mapping single-
cSuccOut based handovers mode base station
eNodeB:V100R006
C00

C.LCS.E2G.Pre- based handover the mapping single-
counter is:
eNodeB:V100R006
C00


Description

C.LCS.E2G.Exe- based handover the mapping single-
counter is:
eNodeB:V100R006
C00

C.LCS.E2G.Exe- successful CSFB- the mapping single-
GERAN for SRVCC introduce this
counter is:
eNodeB:V100R006
C00

C.LCS.E2T.Pre- based handover the mapping single-
SCDMA network for introduce this
SRVCC counter is:
eNodeB:V100R006
C00

C.LCS.E2T.Exe- based handover the mapping single-
counter is:
eNodeB:V100R006
C00

C.LCS.E2T.Exe- successful CSFB- the mapping single-
network for SRVCC counter is:
eNodeB:V100R006
C00


Description
1526728889 L.IRATHO.E21xR Number of responses V100R008C00,and

TT.MMEAbnorm for abnormal causes the mapping single-
Rsp received by the mode base station
eNodeB from the version that
MME during inter- introduce this
RAT handover counter is:
executions from E- eNodeB:V100R006
UTRAN to C00
CDMA2000 1xRTT
network
1526728890 L.IRATHO.E2HR Number of responses V100R008C00,and

PD.MMEAbnorm for abnormal causes the mapping single-
UTRAN to C00
CDMA2000 HRPD
network
1526728891 L.IRATHO.E2W. Number of responses V100R008C00,and

MMEAbnormRsp for abnormal causes the mapping single-
received by the mode base station
UTRAN to C00
WCDMA network
1526728892 L.IRATHO.E2G.M Number of responses V100R008C00,and

MEAbnormRsp for abnormal causes the mapping single-
UTRAN to GERAN C00


Description
1526728893 L.IRATHO.E2T.M Number of responses V100R008C00,and

MEAbnormRsp for abnormal causes the mapping single-
UTRAN to TD- C00
SCDMA network
1526728894 L.IRATHO.SRVC Number of responses V100R008C00,and

C.E2W.MMEAb- for abnormal causes the mapping single-
normRsp received by the mode base station
UTRAN to C00
WCDMA network
for SRVCC

C.E2G.MMEAb- for abnormal causes the mapping single-
UTRAN to GERAN C00
for SRVCC

C.E2T.MMEAb- for abnormal causes the mapping single-
UTRAN to TD- C00
SCDMA network for
SRVCC


Description
1526728897 L.CCO.E2G.MME Number of responses V100R008C00,and

AbnormRsp for abnormal causes the mapping single-
MME during CCO introduce this
executions from E- counter is:
UTRAN to GERAN eNodeB:V100R006
C00
1526728898 L.IRATHO.E2C.C Number of responses V100R008C00,and

SFB.MMEAbnorm for abnormal causes the mapping single-
MME during CSFB- introduce this
based inter-RAT counter is:
handover executions eNodeB:V100R006
from E-UTRAN to C00
CDMA2000
network
1526728899 L.IRATHO.E2W.C Number of responses V100R008C00,and

from E-UTRAN to C00
WCDMA network
1526728900 L.IRATHO.E2G.C Number of responses V100R008C00,and

from E-UTRAN to C00
GERAN


Description
1526728901 L.IRATHO.E2T.C Number of responses V100R008C00,and

from E-UTRAN to C00
TD-SCDMA
network
Counter Sub Counter
L.IRATHO.E2C.PrepAttOut L.IRATHO.E2C.CSFB.PrepAttOut
L.IRATHO.E2C.ExecAttOut L.IRATHO.E2C.CSFB.ExecAttOut
L.IRATHO.E2C.ExecSuccOut L.IRATHO.E2C.CSFB.ExecSuccOut
L.IRATHO.E2C.ExecSuccOut L.IRATHO.E21xRTT.MMEAbnormRsp
L.IRATHO.E2HRPD.MMEAbnormRsp
L.IRATHO.E2W.PrepAttOut L.IRATHO.BlindHO.E2W.PrepAttOut
L.IRATHO.E2W.PrepAttOut L.IRATHO.SRVCC.E2W.PrepAttOut
L.IRATHO.E2W.PrepAttOut L.IRATHO.E2W.CSFB.PrepAttOut
L.IRATHO.E2W.PrepAttOut L.IRATHO.E2W.Load.PrepAttOut
L.IRATHO.E2W.RegainHPLMN.PrepAtt-
Out
L.IRATHO.E2W.ExecAttOut L.IRATHO.BlindHO.E2W.ExecAttOut
L.IRATHO.E2W.ExecAttOut L.IRATHO.SRVCC.E2W.ExecAttOut
L.IRATHO.E2W.ExecAttOut L.IRATHO.E2W.CSFB.ExecAttOut
L.IRATHO.E2W.ExecAttOut L.IRATHO.E2W.Load.ExecAttOut
L.IRATHO.E2W.RegainHPLMN.ExecAtt-
Out
L.IRATHO.E2W.ExecSuccOut L.IRATHO.BlindHO.E2W.ExecSuccOut
L.IRATHO.E2W.ExecSuccOut L.IRATHO.SRVCC.E2W.ExecSuccOut
L.IRATHO.E2W.ExecSuccOut L.IRATHO.E2W.CSFB.ExecSuccOut

Counter Sub Counter
L.IRATHO.E2W.ExecSuccOut L.IRATHO.E2W.Load.ExecSuccOut
L.IRATHO.E2W.RegainHPLMN.Exe-
cSuccOut
L.IRATHO.E2W.ExecSuccOut L.IRATHO.E2W.MMEAbnormRsp
L.IRATHO.E2G.PrepAttOut L.IRATHO.BlindHO.E2G.PrepAttOut
L.IRATHO.E2G.PrepAttOut L.IRATHO.SRVCC.E2G.PrepAttOut
L.IRATHO.E2G.PrepAttOut L.IRATHO.E2G.CSFB.PrepAttOut
L.IRATHO.E2G.PrepAttOut L.IRATHO.E2G.Load.PrepAttOut
L.IRATHO.E2G.ExecAttOut L.IRATHO.BlindHO.E2G.ExecAttOut
L.IRATHO.E2G.ExecAttOut L.IRATHO.SRVCC.E2G.ExecAttOut
L.IRATHO.E2G.ExecAttOut L.IRATHO.E2G.CSFB.ExecAttOut
L.IRATHO.E2G.ExecAttOut L.IRATHO.E2G.Load.ExecAttOut
L.IRATHO.E2G.ExecSuccOut L.IRATHO.BlindHO.E2G.ExecSuccOut
L.IRATHO.E2G.ExecSuccOut L.IRATHO.SRVCC.E2G.ExecSuccOut
L.IRATHO.E2G.ExecSuccOut L.IRATHO.E2G.CSFB.ExecSuccOut
L.IRATHO.E2G.ExecSuccOut L.IRATHO.E2G.Load.ExecSuccOut
L.IRATHO.E2G.ExecSuccOut L.IRATHO.E2G.MMEAbnormRsp
L.IRATHO.E2T.PrepAttOut L.IRATHO.BlindHO.E2T.PrepAttOut
L.IRATHO.E2T.PrepAttOut L.IRATHO.SRVCC.E2T.PrepAttOut
L.IRATHO.E2T.PrepAttOut L.IRATHO.E2T.CSFB.PrepAttOut
L.IRATHO.E2T.ExecAttOut L.IRATHO.BlindHO.E2T.ExecAttOut
L.IRATHO.E2T.ExecAttOut L.IRATHO.SRVCC.E2T.ExecAttOut
L.IRATHO.E2T.ExecAttOut L.IRATHO.E2T.CSFB.ExecAttOut
L.IRATHO.E2T.ExecSuccOut L.IRATHO.BlindHO.E2T.ExecSuccOut
L.IRATHO.E2T.ExecSuccOut L.IRATHO.SRVCC.E2T.ExecSuccOut
L.IRATHO.E2T.ExecSuccOut L.IRATHO.E2T.CSFB.ExecSuccOut
L.IRATHO.E2T.ExecSuccOut L.IRATHO.E2T.MMEAbnormRsp
L.CSFB.PrepAtt L.CSFB.PrepAtt.Idle
L.CSFB.PrepAtt L.CSFB.PrepAtt.Emergency
L.CSFB.PrepSucc L.CSFB.PrepSucc.Idle

Counter Sub Counter
L.CSFB.PrepSucc L.CSFB.PrepSucc.Emergency
L.CSFB.E2W L.CSFB.E2W.Idle
L.CSFB.E2W L.RRCRedirection.E2W.CSFB
L.IRATHO.E2W.CSFB.ExecAttOut
L.CSFB.E2W L.CSFB.E2W.Emergency
L.CSFB.E2G L.RRCRedirection.E2G.CSFB
L.IRATHO.E2G.CSFB.ExecAttOut
L.CSFB.E2G L.CSFB.E2G.Emergency
L.RRCRedirection.E2W L.RRCRedirection.E2W.Load
L.RRCRedirection.E2G L.RRCRedirection.E2G.Load
L.IRATHO.SRVCC.E2W.PrepAttOut L.IRATHO.SRVCC.LCS.E2W.PrepAttOut
L.IRATHO.SRVCC.E2W.ExecAttOut L.IRATHO.SRVCC.LCS.E2W.ExecAttOut
L.IRATHO.SRVCC.E2W.ExecSuccOut L.IRATHO.SRVCC.LCS.E2W.ExecSucc-
Out
L.IRATHO.SRVCC.E2W.ExecSuccOut L.IRATHO.SRVCC.E2W.MMEAb-
normRsp
L.IRATHO.SRVCC.E2G.PrepAttOut L.IRATHO.SRVCC.LCS.E2G.PrepAttOut
L.IRATHO.SRVCC.E2G.ExecAttOut L.IRATHO.SRVCC.LCS.E2G.ExecAttOut
L.IRATHO.SRVCC.E2G.ExecSuccOut L.IRATHO.SRVCC.LCS.E2G.ExecSucc-
Out
L.IRATHO.SRVCC.E2G.ExecSuccOut L.IRATHO.SRVCC.E2G.MMEAbnormRsp
L.IRATHO.SRVCC.E2T.PrepAttOut L.IRATHO.SRVCC.LCS.E2T.PrepAttOut
L.IRATHO.SRVCC.E2T.ExecAttOut L.IRATHO.SRVCC.LCS.E2T.ExecAttOut
L.IRATHO.SRVCC.E2T.ExecSuccOut L.IRATHO.SRVCC.LCS.E2T.ExecSucc-
Out
L.IRATHO.SRVCC.E2T.ExecSuccOut L.IRATHO.SRVCC.E2T.MMEAbnormRsp
L.CCO.E2G.ExecSuccOut L.CCO.E2G.MMEAbnormRsp
L.RRCRedirection.E2W.CSFB L.FlashCSFB.E2W
L.RRCRedirection.E2G.CSFB L.FlashCSFB.E2G
L.IRATHO.E2C.CSFB.ExecSuccOut L.IRATHO.E2C.CSFB.MMEAbnormRsp
L.IRATHO.E2W.CSFB.ExecSuccOut L.IRATHO.E2W.CSFB.MMEAbnormRsp
L.IRATHO.E2G.CSFB.ExecSuccOut L.IRATHO.E2G.CSFB.MMEAbnormRsp

Counter Sub Counter
L.IRATHO.E2T.CSFB.ExecSuccOut L.IRATHO.E2T.CSFB.MMEAbnormRsp
L.CSFB.E2T L.CSFB.E2T.Idle
L.IRATHO.E2W.MMEAbnormRsp L.IRATHO.SRVCC.E2W.MMEAb-
normRsp
L.IRATHO.E2G.MMEAbnormRsp L.IRATHO.SRVCC.E2G.MMEAbnormRsp
L.IRATHO.E2T.MMEAbnormRsp L.IRATHO.SRVCC.E2T.MMEAbnormRsp
2.2.23.1 Number of Inter-RAT Handover Attempts from E-UTRAN to CDMA2000

Network
Counters
Description
1526726986 L.IRATHO.E2C.Pre Number of inter- DBS3900 LTE/

pAttOut RAT handover BTS3900 LTE/
attempts from E- BTS3900A LTE/
UTRAN to BTS3900L LTE/
CDMA2000 BTS3900AL LTE,
network BTS3900
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to
CDMA2000 network.
Measurement Points
As shown at point A in Figure 2-102, the L.IRATHO.E2C.PrepAttOut counter is incremented
by 1 each time the eNodeB decides to perform an inter-RAT blind handover from E-UTRAN
to CDMA2000 network or decides to perform an inter-RAT handover from E-UTRAN to
CDMA2000 after the eNodeB receives a measurement report from a UE.

Figure 2-102
Formula
None
Unit
None
Related Features
L.IRATHO.E2C.PrepAttOut Multi-mode: None

GSM: None
UMTS: None
between E-UTRAN and
CDMA2000
2.2.23.2 Number of Inter-RAT Handovers Executions from E-UTRAN to

CDMA2000 Network

Counters
Description
1526726987 L.IRATHO.E2C.Ex- Number of inter- DBS3900 LTE/

ecAttOut RAT Handovers BTS3900 LTE/
executions from E- BTS3900A LTE/
network BTS3900
Description
The counter measure the number of inter-RAT handovers executions from E-UTRAN to
CDMA2000 network.
Measurement Points
As shown at point B in Figure 2-103, during an inter-RAT handover from E-UTRAN to
CDMA2000 network the L.IRATHO.E2C.ExecAttOut counter is incremented by 1 each time
the eNodeB sends a Mobility From EUTRA Command message to the UE.
Figure 2-103

Formula
None
Unit
None
Related Features
L.IRATHO.E2C.ExecAtt- Multi-mode: None

Out GSM: None
UMTS: None
between E-UTRAN and
CDMA2000
2.2.23.3 Number of Successful Inter-RAT Handovers from E-UTRAN to

CDMA2000 Network
Counters
Description
1526726988 L.IRATHO.E2C.Ex- Number of DBS3900 LTE/

ecSuccOut successful inter- BTS3900 LTE/
RAT handovers from BTS3900A LTE/
E-UTRAN to BTS3900L LTE/
network BTS3900
Description
The counter measures the number of successful inter-RAT handovers from E-UTRAN to
CDMA2000 network.
Measurement Points
As shown at point C in Figure 2-104, during an inter-RAT handover from E-UTRAN to
CDMA2000 network the L.IRATHO.E2C.ExecSuccOut counter is incremented by 1 each time
the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME after
the UE is handed over from the E-UTRAN to a CDMA2000 network.

Figure 2-104
Formula
None
Unit
None
Related Features
L.IRATHO.E2C.ExecSucc- Multi-mode: None

Out GSM: None
UMTS: None
LOFD-001035 between E-UTRAN and
CDMA2000
CS Fallback to CDMA2000
1xRTT

2.2.23.4 Number of Inter-RAT Handover Attempts from E-UTRAN to WCDMA

Network
Counters
Description
1526726989 L.IRATHO.E2W.Pr Number of inter- DBS3900 LTE/

epAttOut RAT handover BTS3900 LTE/
WCDMA network BTS3900AL LTE,
BTS3900
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to WCDMA
network.
Measurement Points
As shown at point A in Figure 2-105, the L.IRATHO.E2W.PrepAttOut counter is incremented
to WCDMA network or decides to perform an inter-RAT handover from E-UTRAN to WCDMA
network after the eNodeB receives a measurement report from a UE.
Figure 2-105

Formula
None
Unit
None
Related Features
L.IRATHO.E2W.PrepAtt- Multi-mode: None

Out GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
CS Fallback to UTRAN
TDLOFD-001022
TDLOFD-001033 between E-UTRAN and
UTRAN
SRVCC to UTRAN
2.2.23.5 Number of Inter-RAT Handovers Executions from E-UTRAN to WCDMA

Network
Counters
Description
1526726990 L.IRATHO.E2W.Ex Number of inter- DBS3900 LTE/

ecAttOut RAT handover BTS3900 LTE/
BTS3900
Description
WCDMA network.

Measurement Points
WCDMA network the L.IRATHO.E2W.ExecAttOut counter is incremented by 1 each time the
eNodeB sends a Mobility From EUTRA Command message to the UE.
Figure 2-106
Formula
None
Unit
None

Related Features
L.IRATHO.E2W.ExecAtt- Multi-mode: None

Out GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN
2.2.23.6 Number of Successful Inter-RAT Handovers from E-UTRAN to WCDMA

Network
Counters
Description
1526726991 L.IRATHO.E2W.Ex Number of DBS3900 LTE/

BTS3900
Description
WCDMA network.
Measurement Points
WCDMA network the L.IRATHO.E2W.ExecSuccOut counter is incremented by 1 each time
the UE is handed over from the E-UTRAN to a WCDMA network.

Figure 2-107
Formula
None
Unit
None

Related Features
L.IRATHO.E2W.ExecSucc- Multi-mode: None

Out GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN
2.2.23.7 Number of Inter-RAT Handover Attempts from E-UTRAN to GERAN
Counters
Description
1526726992 L.IRATHO.E2G.Pre Number of inter- DBS3900 LTE/

pAttOut RAT handover BTS3900 LTE/
UTRAN to GERAN BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to GERAN.
Measurement Points
As shown at point A in Figure 2-108, the L.IRATHO.E2G.PrepAttOut counter is incremented
to GERAN or decides to perform an inter-RAT handover from E-UTRAN to GERAN after the
eNodeB receives a measurement report from a UE.

Figure 2-108
Formula
None
Unit
None

Related Features
L.IRATHO.E2G.PrepAtt- Multi-mode: None

Out GSM: None
UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN
TDLOFD-001020
CS Fallback to GERAN
TDLOFD-001023
GERAN
SRVCC to GERAN
2.2.23.8 Number of Inter-RAT Handovers Executions from E-UTRAN to GERAN
Counters
Description
1526726993 L.IRATHO.E2G.Ex- Number of inter- DBS3900 LTE/

BTS3900AL LTE,
BTS3900
Description
GERAN.
Measurement Points
As shown at point B in Figure 2-109, during an inter-RAT handover from E-UTRAN to GERAN
the L.IRATHO.E2G.ExecAttOut counter is incremented by 1 each time the eNodeB sends a
Mobility From EUTRA Command message to the UE.

Figure 2-109
Formula
None
Unit
None

Related Features
L.IRATHO.E2G.ExecAtt- Multi-mode: None

Out GSM: None
UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN
TDLOFD-001020
TDLOFD-001023
GERAN
SRVCC to GERAN
2.2.23.9 Number of Successful Inter-RAT Handovers from E-UTRAN to GERAN
Counters
Description
1526726994 L.IRATHO.E2G.Ex- Number of DBS3900 LTE/

GERAN BTS3900AL LTE,
BTS3900
Description
GERAN.
Measurement Points
As shown at point C in Figure 2-110, during an inter-RAT handover from E-UTRAN to GERAN
the L.IRATHO.E2G.ExecSuccOut counter is incremented by 1 each time the eNodeB receives
a UE CONTEXT RELEASE COMMAND message from the MME after the UE is handed over
from the E-UTRAN to a GERAN.

Figure 2-110
Formula
None
Unit
None

Related Features
L.IRATHO.E2G.ExecSucc- Multi-mode: None

Out GSM: None
UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN
TDLOFD-001020
TDLOFD-001023
GERAN
SRVCC to GERAN
2.2.23.10 Number of Inter-RAT Handover Attempts from E-UTRAN to TD-SCDMA

Network
Counters
Description
1526727226 L.IRATHO.E2T.Pre Number of inter- DBS3900 LTE/

pAttOut RAT Handover BTS3900 LTE/
Attempts from E- BTS3900A LTE/
UTRAN to TD- BTS3900L LTE/
SCDMA network BTS3900AL LTE,
BTS3900
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to TD-
SCDMA network.
Measurement Points
As shown at point A in Figure 2-111, the L.IRATHO.E2T.PrepAttOut counter is incremented
to TD-SCDMA network or decides to perform an inter-RAT handover from E-UTRAN to TD-
SCDMA network after the eNodeB receives a measurement report from a UE.

Figure 2-111
Formula
None
Unit
None
Related Features
L.IRATHO.E2T.PrepAttOut Multi-mode: None

GSM: None
UMTS: None
UTRAN
TDLOFD-001019
SRVCC to UTRAN
TDLOFD-001022
between E-UTRAN and
UTRAN
SRVCC to UTRAN

2.2.23.11 Number of Inter-RAT Handovers Executions from E-UTRAN to TD-

SCDMA Network
Counters
Description
1526727227 L.IRATHO.E2T.Ex- Number of inter- DBS3900 LTE/

BTS3900
Description
The counter measures the number of inter-RAT handovers executions from E-UTRAN to TD-
SCDMA network.
Measurement Points
As shown at point B in Figure 2-112, during an inter-RAT handover from E-UTRAN to TD-
SCDMA network the L.IRATHO.E2T.ExecAttOut counter is incremented by 1 each time the
Figure 2-112

Formula
None
Unit
None
Related Features
L.IRATHO.E2T.ExecAtt- Multi-mode: None

Out GSM: None
UMTS: None
UTRAN
TDLOFD-001019
SRVCC to UTRAN
TDLOFD-001022
between E-UTRAN and
UTRAN
SRVCC to UTRAN
2.2.23.12 Number of Successful Inter-RAT Handovers from E-UTRAN to TD-

SCDMA Network
Counters
Description
1526727228 L.IRATHO.E2T.Ex- Number of DBS3900 LTE/

E-UTRAN to TD- BTS3900L LTE/
BTS3900
Description
The counter measures the number of successful inter-RAT handovers from E-UTRAN to TD-
SCDMA network.

Measurement Points
As shown at point C in Figure 2-113, during an inter-RAT handover from E-UTRAN to TD-
SCDMA network the L.IRATHO.E2T.ExecSuccOut counter is incremented by 1 each time the
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME after the
UE is handed over from the E-UTRAN to a TD-SCDMA network.
Figure 2-113
Formula
None
Unit
None

Related Features
L.IRATHO.E2T.ExecSucc- Multi-mode: None

Out GSM: None
UMTS: None
UTRAN
TDLOFD-001019
SRVCC to UTRAN
TDLOFD-001022
between E-UTRAN and
UTRAN
SRVCC to UTRAN
2.2.23.13 Number of Inter-RAT Handover Failures for Different Causes
Counters
Description

p.FailOut.MME RAT handover BTS3900 LTE/
preparation failures BTS3900A LTE/
from E-UTRAN to BTS3900L LTE/
GERAN because of BTS3900AL LTE,
faults on the MME BTS3900
side

p.FailOut.NoReply RAT handover BTS3900 LTE/
GERAN because of BTS3900AL LTE,
no responses from BTS3900
GERAN

p.FailOut.PrepFai- RAT handover BTS3900 LTE/
lure preparation failures BTS3900A LTE/
GERAN due BTS3900AL LTE,
tobecause GERAN BTS3900
cells send handover
preparation failure
messages


Description

p.FailOut.MME RAT handover BTS3900 LTE/
TD-SCDMA BTS3900AL LTE,
network because of BTS3900
faults on the MME
side

p.FailOut.NoReply RAT handover BTS3900 LTE/
network due BTS3900
tobecause of no
responses from TD-
SCDMA network

p.FailOut.PrepFai- RAT handover BTS3900 LTE/
because TD- BTS3900L LTE/
cells send handover BTS3900
preparation failure
messages

ep.FailOut.MME RAT handover BTS3900 LTE/
because of faults on BTS3900
the MME side

ep.FailOut.PrepFai- RAT handover BTS3900 LTE/
because WCDMA BTS3900
network cells send
handover preparation
failure messages


Description

ep.FailOut.NoReply RAT handover BTS3900 LTE/
because of no BTS3900
responses from
WCDMA network
Description
The counters measure the number of inter-RAT handover failures for different causes. Inter-
RAT outgoing handover failures usually occur during the handover preparation phase and are
caused by faults on the MME side, no responses from the target cell of another system, or the
target cell of another system sending handover failure messages. During the handover
preparation phase, between the handover decision phase and the handover execution phase, the
handover resources are prepared. In an inter-RAT handover, a UE is handed over from the E-
UTRAN to another system to ensure service continuity in multi-RAT networking scenarios.
Measurement Points
As shown at point A in Figure 2-114, the corresponding counter is incremented by 1 based on
the handover target system each time the eNodeB does not receive a HANDOVER COMMAND
message from the MME after the eNodeB sends a HANDOVER REQUIRED message to the
MME.
If the target system is WCDMA network, the L.IRATHO.E2W.Prep.FailOut.NoReply counter
is incremented.
If the target system is GERAN, the L.IRATHO.E2G.Prep.FailOut.NoReply counter is
incremented.
If the target system is TD-SCDMA network, the L.IRATHO.E2T.Prep.FailOut.NoReply counter
is incremented.
the handover target system each time the eNodeB receives a HANDOVER PREPARE
FAILURE message from the MME after the eNodeB sends a HANDOVER REQUIRED
message to the MME.
If the target system is WCDMA network, the L.IRATHO.E2W.Prep.FailOut.PrepFailure
counter is incremented.
If the target system is GERAN, the L.IRATHO.E2G.Prep.FailOut.PrepFailure counter is
incremented.
If the target system is TD-SCDMA network, the L.IRATHO.E2T.Prep.FailOut.PrepFailure
the target system each time the eNodeB receives a UE CONTEXT RELEASE COMMAND

message from the MME after the eNodeB sends a HANDOVER REQUIRED message to the
MME.
If the target system is WCDMA network, the L.IRATHO.E2W.Prep.FailOut.MME counter is

incremented.
If the target system is GERAN, the L.IRATHO.E2G.Prep.FailOut.MME counter is incremented.
If the target system is TD-SCDMA network, the L.IRATHO.E2T.Prep.FailOut.MME counter

is incremented.
Figure 2-114
Figure 2-115

Figure 2-116
Formula
None
Unit
None
Related Features
L.IRATHO.E2G.Prep.FailO Multi-mode: None

ut.MME GSM: None
UMTS: None
LTE: LOFD-001034 CS Fallback to GERAN
TDLOFD-001034 CS Fallback to GERAN
LOFD-001020 PS Inter-RAT Mobility
GERAN
LOFD-001046
LOFD-001073 GERAN
Service based inter-RAT
handover to GERAN
handover to GERAN
Distance based inter-RAT
handover to GERAN


ut.NoReply GSM: None
UMTS: None
GERAN
LOFD-001046
LOFD-001073 GERAN
handover to GERAN
handover to GERAN
handover to GERAN

ut.PrepFailure GSM: None
UMTS: None
GERAN
LOFD-001046
LOFD-001073 GERAN
handover to GERAN
handover to GERAN
handover to GERAN

L.IRATHO.E2T.Prep.FailO Multi-mode: None

ut.MME GSM: None
UMTS: None
LTE: LOFD-001033 CS Fallback to UTRAN
TDLOFD-001033 CS Fallback to UTRAN
UTRAN
LOFD-001043
LOFD-001072 UTRAN
handover to UTRAN
handover to UTRAN
handover to UTRAN

UMTS: None
UTRAN
LOFD-001043
LOFD-001072 UTRAN
handover to UTRAN
handover to UTRAN
handover to UTRAN


UMTS: None
UTRAN
LOFD-001043
LOFD-001072 UTRAN
handover to UTRAN
handover to UTRAN
handover to UTRAN
L.IRATHO.E2W.Prep.FailO Multi-mode: None

ut.MME GSM: None
UMTS: None
UTRAN
LOFD-001043
LOFD-001072 UTRAN
handover to UTRAN
handover to UTRAN
handover to UTRAN


UMTS: None
UTRAN
LOFD-001043
LOFD-001072 UTRAN
handover to UTRAN
handover to UTRAN
handover to UTRAN

UMTS: None
UTRAN
LOFD-001043
LOFD-001072 UTRAN
handover to UTRAN
handover to UTRAN
handover to UTRAN
2.2.23.14 Number of Inter-RAT Blind Handover Attempts from E-UTRAN to

Another System

Counters
Description
1526728328 L.IRATHO.BlindH Number of inter- DBS3900 LTE/

O.E2W.PrepAttOut RAT blind handover BTS3900 LTE/
BTS3900

O.E2G.PrepAttOut RAT blind handover BTS3900 LTE/
BTS3900AL LTE,
BTS3900

O.E2T.PrepAttOut RAT blind handover BTS3900 LTE/
BTS3900
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.
If the target system is TD-SCDMA, the L.IRATHO.BlindHO.E2T.PrepAttOut counter is

incremented.

Figure 2-117
Formula
None
Unit
None
Related Features
L.IRATHO.BlindHO.E2W. Multi-mode: None

PrepAttOut GSM: None
UMTS: None
UTRAN
between E-UTRAN and
UTRAN

L.IRATHO.BlindHO.E2G.P Multi-mode: None

repAttOut GSM: None
UMTS: None
GERAN
between E-UTRAN and
GERAN
L.IRATHO.BlindHO.E2T.P Multi-mode: None

repAttOut GSM: None
UMTS: None
UTRAN
between E-UTRAN and
UTRAN
2.2.23.15 Number of Blind Handover Executions from E-UTRAN to Another System
Counters
Description

O.E2W.ExecAttOut RAT blind BTS3900 LTE/
handovers BTS3900A LTE/
executions from E- BTS3900L LTE/
UTRAN to BTS3900AL LTE,
WCDMA network BTS3900


Description

O.E2G.ExecAttOut RAT blind BTS3900 LTE/
UTRAN to GERAN BTS3900AL LTE,
BTS3900

O.E2T.ExecAttOut RAT blind handover BTS3900 LTE/
BTS3900
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
the target cell.
Measurement Points
As shown at point B in Figure 2-118, the corresponding counter is incremented by 1 based on
the blind handover target system each time the eNodeB decides to perform a blind handover and
sends a Mobility From EUTRA Command message to the UE.
If the target system is WCDMA network, the L.IRATHO.BlindHO.E2W.ExecSuccOut counter

is incremented.
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 counter

is incremented.

Figure 2-118
Formula
None
Unit
None
Related Features

ExecAttOut GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN

L.IRATHO.BlindHO.E2G.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN
TDLOFD-001020
TDLOFD-001023
GERAN
SRVCC to GERAN
L.IRATHO.BlindHO.E2T.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN
2.2.23.16 Number of successful Inter-RAT Blind Handovers from E-UTRAN to

Another System

Counters
Description
1526728313 L.IRATHO.BlindH Number of DBS3900 LTE/

O.E2W.ExecSucc- successful inter- BTS3900 LTE/
Out RAT blind BTS3900A LTE/
handovers from E- BTS3900L LTE/

O.E2G.ExecSucc- successful inter- BTS3900 LTE/
Out RAT blind BTS3900A LTE/
BTS3900

O.E2T.ExecSuccOut successful inter- BTS3900 LTE/
RAT blind BTS3900A LTE/
UTRAN to TD- BTS3900AL LTE,
SCDMA network BTS3900
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
the target cell.
Measurement Points
As shown at point C in Figure 2-119, the corresponding counter is increased by 1based on the
blind handover target system each time the eNodeB decides to perform a blind handover and
receives s a UE CONTEXT RELEASE COMMAND message from the MME.
If the target system is WCDMA network, the L.IRATHO.BlindHO.E2W.ExecSuccOut counter

is increased.
If the target system is GERAN, the L.IRATHO.BlindHO.E2G.ExecSuccOut counter is

increased.
If the target system is TD-SCDMA network, the L.IRATHO.BlindHO.E2T. ExecSuccOut


Figure 2-119
Formula
None
Unit
None
Related Features

ExecSuccOut GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN

L.IRATHO.BlindHO.E2G.E Multi-mode: None

xecSuccOut GSM: None
UMTS: None
GERAN
LOFD-001034
SRVCC to GERAN
TDLOFD-001020
TDLOFD-001023
GERAN
SRVCC to GERAN
L.IRATHO.BlindHO.E2T.E Multi-mode: None

UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN
2.2.23.17 Number of Indicators for CSFB to Another System
Counters
Description
1526728321 L.CSFB.PrepAtt Number of CSFB DBS3900 LTE/

indicators received BTS3900 LTE/
by the eNodeB BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1526728386 L.CSFB.PrepAtt.Idl Number of CSFB DBS3900 LTE/

e indicators received BTS3900 LTE/
by the eNodeB for BTS3900A LTE/
UEs in idle mode BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728707 L.CSFB.PrepAtt.Em Number of CSFB DBS3900 LTE/

ergency indicators received BTS3900 LTE/
by the eNodeB for BTS3900A LTE/
emergency calls BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of CSFB indicators received by the eNodeB. The MME sends
an INITIAL CONTEXT SETUP REQUEST or UE CONTEXT MODIFICATION REQUEST
message containing the information element (IE) "CS Fallback Indicator" to the eNodeB. Then,
the eNodeB triggers a CSFB based on the IE.
Measurement Points
As shown at point A in Figure 2-120, the L.CSFB.PrepAtt counter is incremented by 1 each
time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST message containing the
IE "CS Fallback Indicator" from the MME and the eNodeB determines that the CSFB procedure
is for voice services.
As shown at point A in Figure 2-121, 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 2-120, 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 2-120, 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 2-121, 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 2-120
Figure 2-121
Formula
None
Unit
None

Related Features
L.CSFB.PrepAtt Multi-mode: None

GSM: None
UMTS: None
LOFD-001034 CS Fallback to GERAN

TDLOFD-001034
LOFD-001035
1xRTT
L.CSFB.PrepAtt.Idle Multi-mode: None

GSM: None
UMTS: None

TDLOFD-001034
LOFD-001035
1xRTT
L.CSFB.PrepAtt.Emergency Multi-mode: None

GSM: None
UMTS: None

TDLOFD-001034
LOFD-001035
1xRTT
2.2.23.18 Number of CSFB Responses to MMEs

Counters
Description
1526728322 L.CSFB.PrepSucc Number of DBS3900 LTE/

successful CSFB BTS3900 LTE/
responses from the BTS3900A LTE/
BTS3900AL LTE,
BTS3900
1526728387 L.CSFB.PrepSucc.Id Number of DBS3900 LTE/

le successful CSFB BTS3900 LTE/
responses from the BTS3900A LTE/
eNodeB for UEs in BTS3900L LTE/
idle mode BTS3900AL LTE,
BTS3900
1526728708 L.CSFB.PrepSucc.E Number of responses DBS3900 LTE/

mergency sent from the BTS3900 LTE/
eNodeB for CSFB BTS3900A LTE/
triggered for BTS3900L LTE/
emergency calls BTS3900AL LTE,
BTS3900
Description
The counter measures the number of CSFB responses from the eNodeB to MMEs. During a
CSFB procedure, the eNodeB sends an INITIAL CONTEXT SETUP RESPONSE or UE
CONTEXT MODIFICATION RESPONSE message to the MME.
The eNodeB initiates a CSFB procedure based on the CS fallback indicator sent from the MME.
Measurement Points
As shown at point C in Figure 2-122, the L.CSFB.PrepSucc counter is incremented by 1 each
time the eNodeB successfully sends an INITIAL CONTEXT SETUP RESPONSE message to
the MME and the corresponding INITIAL CONTEXT SETUP REQUEST message is
determined that the CSFB procedure is for voice services.
As shown at point C in Figure 2-123, 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 2-122, 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 2-122, 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 2-123, 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 2-122
Figure 2-123
Formula
None
Unit
None

Related Features
L.CSFB.PrepSucc Multi-mode: None

GSM: None
UMTS: None

TDLOFD-001034
LOFD-001035
1xRTT
L.CSFB.PrepSucc.Idle Multi-mode: None

GSM: None
UMTS: None

TDLOFD-001034
LOFD-001035
1xRTT
L.CSFB.PrepSucc.Emergen- Multi-mode: None

cy GSM: None
UMTS: None

TDLOFD-001034
LOFD-001035
1xRTT
2.2.23.19 Number of Procedures for CSFB to Another System

Counters
Description
1526728323 L.CSFB.E2W Number of DBS3900 LTE/

procedures for CSFB BTS3900 LTE/
to WCDMA network BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728324 L.CSFB.E2G Number of DBS3900 LTE/

to GERAN BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728388 L.CSFB.E2W.Idle Number of DBS3900 LTE/

for UEs in idle mode BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728497 L.RRCRedirection.E Number of CSFB- DBS3900 LTE/

2W.CSFB based redirections BTS3900 LTE/
from E-UTRANs to BTS3900A LTE/
BTS3900AL LTE,
BTS3900

2G.CSFB based redirections BTS3900 LTE/
from E-UTRAN to BTS3900A LTE/
GERAN BTS3900L LTE/
BTS3900AL LTE,
BTS3900

2C.CSFB based redirections BTS3900 LTE/
CDMA2000 BTS3900L LTE/
BTS3900AL LTE,
BTS3900

2T.CSFB based redirections BTS3900 LTE/
TD-SCDMA BTS3900L LTE/
network BTS3900AL LTE,
BTS3900


Description
1526728501 L.IRATHO.E2C.CS Number of CSFB- DBS3900 LTE/

FB.PrepAttOut based inter-RAT BTS3900 LTE/
handover preparation BTS3900A LTE/
attempts from E- BTS3900L LTE/
CDMA2000 BTS3900
network
1526728502 L.IRATHO.E2C.CS Number of CSFB- DBS3900 LTE/

FB.ExecAttOut based handover BTS3900 LTE/
execution attempts BTS3900A LTE/
network BTS3900
1526728503 L.IRATHO.E2C.CS Number of DBS3900 LTE/

FB.ExecSuccOut successful CSFB- BTS3900 LTE/
based inter-RAT BTS3900A LTE/
handover executions BTS3900L LTE/
from E-UTRAN to BTS3900AL LTE,
CDMA2000 BTS3900
network
1526728504 L.IRATHO.E2W.CS Number of CSFB- DBS3900 LTE/

1526728505 L.IRATHO.E2W.CS Number of CSFB- DBS3900 LTE/

FB.ExecAttOut based inter-RAT BTS3900 LTE/
handover execution BTS3900A LTE/
1526728506 L.IRATHO.E2W.CS Number of DBS3900 LTE/

1526728507 L.IRATHO.E2G.CS Number of CSFB- DBS3900 LTE/

BTS3900


Description
1526728508 L.IRATHO.E2G.CS Number of CSFB- DBS3900 LTE/

BTS3900
1526728509 L.IRATHO.E2G.CS Number of DBS3900 LTE/

GERAN BTS3900
1526728510 L.IRATHO.E2T.CS Number of CSFB- DBS3900 LTE/

1526728511 L.IRATHO.E2T.CS Number of CSFB- DBS3900 LTE/

1526728512 L.IRATHO.E2T.CS Number of DBS3900 LTE/

TD-SCDMA BTS3900
network
1526728705 L.FlashCSFB.E2W Number of DBS3900 LTE/

procedures for flash BTS3900 LTE/
CSFB to WCDMA BTS3900A LTE/
BTS3900AL LTE,
BTS3900
1526728706 L.FlashCSFB.E2G Number of DBS3900 LTE/

procedures for flash BTS3900 LTE/
CSFB to GERAN BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1526728709 L.CSFB.E2W.Emer- Number of DBS3900 LTE/

gency procedures for CSFB BTS3900 LTE/
triggered for BTS3900L LTE/
emergency calls BTS3900AL LTE,
BTS3900
1526728710 L.CSFB.E2G.Emer- Number of DBS3900 LTE/

gency procedures for CSFB BTS3900 LTE/
to GERAN triggered BTS3900A LTE/
for emergency calls BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728749 L.CSFB.E2T Number of DBS3900 LTE/

procedures for BTS3900 LTE/
SRVCC to TD- BTS3900A LTE/
SCDMA network BTS3900L LTE/
BTS3900AL LTE,
BTS3900
1526728750 L.CSFB.E2T.Idle Number of DBS3900 LTE/

procedures for BTS3900 LTE/
SRVCC to TD- BTS3900A LTE/
SCDMA for UEs in BTS3900L LTE/
idle mode BTS3900AL LTE,
BTS3900
Description
The counter measures the number of Procedures for CSFB from E-UTRAN to Another System.
The CSFB to WCDMA network mechanism include blind redirection, blind handover, and
handover. The CSFB to GERAN mechanism includes blind redirection, blind handover, blind
CCO, redirection, handover, and CCO. The CSFB to TD-SCDMA mechanism includes blind
redirection, blind handover, redirection, and handover. The counter that measures the total
number of CSFB procedures performed by UEs and the number of CSFB procedures performed
by UEs in idle mode are measured are separately. The number of CSFB procedures performed
by UEs in the connected mode can be calculated by deducting the number of CSFB procedures
performed by UEs in idle mode from the total number of CSFB procedures performed by UEs.
Measurement Points
As shown at point A in Figure 2-124, the L.IRATHO.E2W.CSFB.PrepAttOut counter is
incremented by 1 each time the eNodeB decides to perform an inter-RAT blind handover for
CSFB to WCDMA network or the eNodeB decides to perform an inter-RAT handover for CSFB
to WCDMA network after the eNodeB receives a measurement report from the UE.
As shown at point B in Figure 2-124, the L.CSFB.E2W and
L.IRATHO.E2W.CSFB.ExecAttOut counters are incremented by 1 each time the eNodeB

performs a CSFB procedure to WCDMA network after the eNodeB sends a Mobility From
EUTRA Command message to the UE. In this case, if the CSFB procedure is initiated by a UE
in idle mode (when the UE initiates a CSFB, the initial state is determined by the eNodeB), the
L.CSFB.E2W.Idle counter is incremented by 1.
As shown at point C in Figure 2-124, 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 2-125, 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 2-124, the L.IRATHO.E2G.CSFB.PrepAttOut counter is

CSFB to GERAN or the eNodeB decides to perform an inter-RAT handover for CSFB to
GERAN after the eNodeB receives a measurement report from the UE.
As shown at point B in Figure 2-124, 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 2-124, 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 2-125, 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 2-126, 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 2-126, 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 2-126, 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 2-125, the L.RRCRedirection.E2C.CSFB counter is incremented

by 1 each time the eNodeB sends an RRC Connection Release message to the UE and informs
the UE to perform a CSFB procedure to CDMA2000 network.
As shown at point A in Figure 2-124, 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 2-124, the L.IRATHO.E2T.CSFB.ExecAttOut counter is

the UE and informs the UE to perform a CSFB procedure to TD-SCDMA network.
As shown at point C in Figure 2-124, 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.
As shown at point A in Figure 2-125, the L.RRCRedirection.E2T.CSFB counter is incremented

by 1 each time the eNodeB sends an RRC Connection Release message to the UE and informs
the UE to perform a CSFB procedure to TD-SCDMA network.
As shown at point A in Figure 2-125, 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 2-125, the L.FlashCSFB.E2G counter is incremented by 1 each

time the eNodeB sends an RRC Connection Release message (containing the information of
redirection and system information of the target cell) to the UE and informs the UE to perform
a flash CSFB procedure to GERAN.
As shown at point B in Figure 2-124, 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
As shown at point A in Figure 2-125, the L.CSFB.E2W.Emergency counter is incremented by

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 2-124, the L.CSFB.E2G.Emergency counter is incremented by

eNodeB performs a CSFB procedure to GERAN triggered for an emergency call after the
As shown at point A in Figure 2-125, the L.CSFB.E2G.Emergency counter is incremented by

eNodeB performs a CSFB procedure to GERAN 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 2-124, the L.CSFB.E2T counter is incremented by 1 each time
the eNodeB performs a CSFB procedure to the TD-SCDMA network after the eNodeB sends a
Mobility From EUTRA Command message to the UE.
As shown at point A in Figure 2-125, the L.CSFB.E2T counter is incremented by 1 each time
the eNodeB performs a CSFB procedure to the TD-SCDMA network after the eNodeB sends
an RRC Connection Release message to the UE.

As shown at point B in Figure 2-124 or point A in Figure 2-125, the initial state of the UE must
be saved before the measurement. The L.CSFB.E2T.idle counter is incremented by 1 each time
the UE in idle mode performs a CSFB procedure to TD-SCDMA network.
Figure 2-124
Figure 2-125

Figure 2-126
Formula
None
Unit
None
Related Features
L.CSFB.E2W Multi-mode: None

GSM: None
UMTS: None
L.CSFB.E2G Multi-mode: None

GSM: None
UMTS: None

L.CSFB.E2W.Idle Multi-mode: None

GSM: None
UMTS: None
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.Pre- Multi-mode: None

pAttOut GSM: None
UMTS: None
1xRTT
L.IRATHO.E2C.CSFB.Exe- Multi-mode: None

cAttOut GSM: None
UMTS: None
1xRTT

L.IRATHO.E2C.CSFB.Exe- Multi-mode: None

cSuccOut GSM: None
UMTS: None
1xRTT
L.IRATHO.E2W.CSFB.Pre- Multi-mode: None

pAttOut GSM: None
UMTS: None
L.IRATHO.E2W.CSFB.Ex- Multi-mode: None

ecAttOut GSM: None
UMTS: None
L.IRATHO.E2W.CSFB.Ex- Multi-mode: None

ecSuccOut GSM: None
UMTS: None
L.IRATHO.E2G.CSFB.Pre- Multi-mode: None

pAttOut GSM: None
UMTS: None
L.IRATHO.E2G.CSFB.Exe- Multi-mode: None

cAttOut GSM: None
UMTS: None
L.IRATHO.E2G.CSFB.Exe- Multi-mode: None

cSuccOut GSM: None
UMTS: None

L.IRATHO.E2T.CSFB.Pre- Multi-mode: None

pAttOut GSM: None
UMTS: None
L.IRATHO.E2T.CSFB.Exe- Multi-mode: None

cAttOut GSM: None
UMTS: None
L.IRATHO.E2T.CSFB.Exe- Multi-mode: None

cSuccOut GSM: None
UMTS: None
L.FlashCSFB.E2W Multi-mode: None

GSM: None
UMTS: None
TDLOFD-001052 UTRAN
UTRAN
L.FlashCSFB.E2G Multi-mode: None

GSM: None
UMTS: None
TDLOFD-001053 GERAN
GERAN
L.CSFB.E2W.Emergency Multi-mode: None

GSM: None
UMTS: None

L.CSFB.E2G.Emergency Multi-mode: None

GSM: None
UMTS: None
L.CSFB.E2T Multi-mode: None

GSM: None
UMTS: None
L.CSFB.E2T.Idle Multi-mode: None

GSM: None
UMTS: None
2.2.23.20 Number of Inter-RAT Redirection Preparations from E-UTRAN to

Another System
Counters
Description
1526728330 L.RRCRedirection.E Number of DBS3900 LTE/

2W.PrepAtt redirection BTS3900 LTE/
preparations from E- BTS3900A LTE/
BTS3900

2G.PrepAtt redirection BTS3900 LTE/
preparations from E- BTS3900A LTE/
BTS3900AL LTE,
BTS3900


Description

2T.PrepAtt redirection BTS3900 LTE/
preparations to TD- BTS3900A LTE/
SCDMA network BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of inter-RAT redirection preparations triggered by the
eNodeB. In a redirection, the eNodeB sends an RRC Connection Release message containing
the target frequency and other access information to a UE to perform a redirection procedure.
During the procedure, the UE is released by the source cell and accesses the target cell to continue
its services.
Measurement Points
As shown at point A in Figure 2-127, the L.RRCRedirection.E2W.PrepAtt counter is
incremented by 1 each time the eNodeB decides to trigger an inter-RAT redirection from E-
UTRAN to WCDMA network.
As shown at point A in Figure 2-127, the L.RRCRedirection.E2G.PrepAtt counter is
incremented by 1 each time the eNodeB decides to trigger an inter-RAT redirection from E-
UTRAN to GERAN.
as shown at point A in Figure 2-127, the L.RRCRedirection.E2T.PrepAtt counter is incremented
by 1 each time the eNodeB decides to trigger an inter-RAT redirection from E-UTRAN to TD-
SCDMA network.
Figure 2-127
Formula
None
Unit
None

Related Features
L.RRCRedirection.E2W.Pre Multi-mode: None

pAtt GSM: None
UMTS: None
UTRAN
TDLOFD-001019
TDLOFD-001033
between E-UTRAN and
UTRAN
L.RRCRedirection.E2G.Pre- Multi-mode: None

pAtt GSM: None
UMTS: None
GERAN
TDLOFD-001020
TDLOFD-001034
between E-UTRAN and
GERAN
L.RRCRedirection.E2T.Pre- Multi-mode: None

pAtt GSM: None
UMTS: None
UTRAN
TDLOFD-001019
TDLOFD-001033
between E-UTRAN and
UTRAN
2.2.23.21 Number of Inter-RAT Redirections from E-UTRAN to Another System

Counters
Description

2W redirections from E- BTS3900 LTE/
UTRAN to BTS3900A LTE/
BTS3900AL LTE,
BTS3900

2G redirections from E- BTS3900 LTE/
UTRAN to GERAN BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

2T redirections to TD- BTS3900 LTE/
SCDMA network BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of inter-RAT redirections triggered by the eNodeB. In a
redirection, the eNodeB sends an RRC Connection Release message containing the target
frequency and other access information to a UE to perform a redirection procedure. During the
procedure, the UE is released by the source cell and accesses the target cell to continue its
services.
Measurement Points
As shown at point A in Figure 2-128, the L.RRCRedirection.E2W counter is incremented by 1
each time the eNodeB sends an RRC Connection Release message to the UE when the eNodeB
triggers a redirection to WCDMA network.
As shown at point A in Figure 2-128, the L.RRCRedirection.E2G counter is incremented by 1

triggers a redirection to GERAN.
As shown at point A in Figure 2-128, the L.RRCRedirection.E2T counter is incremented by 1

triggers a redirection to TD-SCDMA network.

Figure 2-128
Formula
None
Unit
None
Related Features
L.RRCRedirection.E2W Multi-mode: None

GSM: None
UMTS: None
UTRAN
TDLOFD-001019
TDLOFD-001033
between E-UTRAN and
UTRAN
L.RRCRedirection.E2G Multi-mode: None

GSM: None
UMTS: None
GERAN
TDLOFD-001020
TDLOFD-001034
between E-UTRAN and
GERAN

L.RRCRedirection.E2T Multi-mode: None

GSM: None
UMTS: None
UTRAN
TDLOFD-001019
TDLOFD-001033
between E-UTRAN and
UTRAN

network for SRVCC
Counters
Description
1526728400 L.IRATHO.SRVCC. Number of inter- DBS3900 LTE/

E2W.PrepAttOut RAT handover BTS3900 LTE/
for SRVCC BTS3900
Description
network for SRVCC in a cell.
Measurement Points
As shown at point A in Figure 2-129, the L.IRATHO.SRVCC.E2W.PrepAttOut counter is
incremented by 1 each time the eNodeB decides to perform an inter-RAT blind handover from
E-UTRAN to WCDMA network or the eNodeB decides to perform an inter-RAT handover from
E-UTRAN to WCDMA network for SRVCC after the eNodeB receives a measurement report
from the UE.

Figure 2-129
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2W.P Multi-mode: None

repAttOut GSM: None
UMTS: None
LTE: LOFD-001022 SRVCC to UTRAN
TDLOFD-001022 SRVCC to UTRAN
2.2.23.23 Number of Inter-RAT Handover Executions from E-UTRAN to WCDMA

network for SRVCC

Counters
Description

E2W.ExecAttOut RAT handover BTS3900 LTE/
for SRVCC BTS3900
Description
The counter measures the number of inter-RAT handover executions from E-UTRAN to
WCDMA network for SRVCC in a cell.
Measurement Points
WCDMA network for SRVCC the L.IRATHO.SRVCC.E2W.ExecAttOut counter is
the UE.
Figure 2-130

Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2W.E Multi-mode: None

xecAttOut GSM: None
UMTS: None

Network for SRVCC
Counters
Description
1526728402 L.IRATHO.SRVCC. Number of DBS3900 LTE/

E2W.ExecSuccOut successful inter- BTS3900 LTE/
for SRVCC BTS3900
Description
WCDMA network for SRVCC in a cell.
Measurement Points
WCDMA network the L.IRATHO.SRVCC.E2W.ExecSuccOut counter is incremented by 1
each time the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the
MME after the UE is handed over from the E-UTRAN to a WCDMA network.

Figure 2-131
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2W.E Multi-mode: None

UMTS: None
2.2.23.25 Number of Inter-RAT Handover Attempts from E-UTRAN to GERAN for

SRVCC

Counters
Description

E2G.PrepAttOut RAT handover BTS3900 LTE/
for SRVCC BTS3900AL LTE,
BTS3900
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to GERAN
for SRVCC in a cell.
Measurement Points
As shown at point A in Figure 2-132, the L.IRATHO.SRVCC.E2G.PrepAttOut counter is
incremented by 1 each time the eNodeB decides to perform an inter-RAT blind handover from
E-UTRAN to GERAN or the eNodeB decides to perform an inter-RAT handover from E-
UTRAN to GERAN for SRVCC after the eNodeB receives a measurement report from the UE.
Figure 2-132

Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2G.Pr Multi-mode: None

epAttOut GSM: None
UMTS: None
LTE: LOFD-001023 SRVCC to GERAN
TDLOFD-001023 SRVCC to GERAN
2.2.23.26 Number of Inter-RAT Handover Executions from E-UTRAN to GERAN

for SRVCC
Counters
Description

E2G.ExecAttOut RAT handover BTS3900 LTE/
BTS3900
Description
GERAN for SRVCC in a cell.
Measurement Points
As shown at point B in Figure 2-133, during an inter-RAT handover from E-UTRAN to GERAN
for SRVCC the L.IRATHO.SRVCC.E2G.ExecAttOut counter is incremented by 1 each time

Figure 2-133
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2G.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
2.2.23.27 Number of Successful Inter-RAT Handovers from E-UTRAN to GERAN

for SRVCC

Counters
Description

E2G.ExecSuccOut successful inter- BTS3900 LTE/
GERAN for SRVCC BTS3900AL LTE,
BTS3900
Description
GERAN for SRVCC in a cell.
Measurement Points
As shown at point C in Figure 2-134, during an inter-RAT handover from E-UTRAN to GERAN
for SRVCC the L.IRATHO.SRVCC.E2G.ExecSuccOut counter is incremented by 1 each time
the UE is handed over from the E-UTRAN to a GERAN.
Figure 2-134

Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2G.E Multi-mode: None

UMTS: None
2.2.23.28 Number of Inter-RAT Handover Attempts from E-UTRAN to TD-SCDMA

Network for SRVCC
Counters
Description

E2T.PrepAttOut RAT handover BTS3900 LTE/
SCDMA network for BTS3900AL LTE,
SRVCC BTS3900
Description
The counter measures the number of inter-RAT handover attempts from E-UTRAN to TD-
SCDMA network for SRVCC in a cell.
Measurement Points
As shown at point A in Figure 2-135, the L.IRATHO.SRVCC.E2T.PrepAttOut counter is
incremented by 1 each time the eNodeB decides to perform an inter-RAT handover from E-
UTRAN to TD-SCDMA network after the eNodeB receives a measurement report from the UE.

Figure 2-135
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2T.Pr Multi-mode: None

epAttOut GSM: None
UMTS: None
2.2.23.29 Number of Inter-RAT Handover Executions from E-UTRAN to TD-

SCDMA Network for SRVCC

Counters
Description

E2T.ExecAttOut RAT handover BTS3900 LTE/
SCDMA for SRVCC BTS3900AL LTE,
BTS3900
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 2-136, during an inter-RAT handover from E-UTRAN to TD-
SCDMA network for SRVCC the L.IRATHO.SRVCC.E2T.ExecAttOut counter is incremented
by 1 each time the eNodeB sends a Mobility From EUTRA Command message to the UE.
Figure 2-136
Formula
None

Unit
None
Related Features
L.IRATHO.SRVCC.E2T.Ex Multi-mode: None

ecAttOut GSM: None
UMTS: None
2.2.23.30 Number of Successful Inter-RAT Handovers from E-UTRAN to TD-

SCDMA network for SRVCC
Counters
Description

E2T.ExecSuccOut successful inter- BTS3900 LTE/
E-UTRAN to TD- BTS3900L LTE/
BTS3900
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 2-137, during an inter-RAT handover from E-UTRAN to TD-
SCDMA network for SRVCC the L.IRATHO.SRVCC.E2T.ExecSuccOut counter is
message from the MME after the UE is handed over from the E-UTRAN to a TD-SCDMA
network.

Figure 2-137
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2T.Ex Multi-mode: None

ecSuccOut GSM: None
UMTS: None
2.2.23.31 Number of LCS-triggered CS Fallback Indicators Received by the eNodeB

Counters
Description
1526728409 L.CSFB.LCS.Pre- Number of LCS- DBS3900 LTE/

pAtt triggered CS fallback BTS3900 LTE/
indicators received BTS3900A LTE/
by the eNodeB BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of LCS-triggered CS fallback indicators received by the
eNodeB in a cell.
Measurement Points
As shown at point A in Figure 2-138, the L.CSFB.LCS.PrepAtt counter is incremented by 1
each time the eNodeB receives an INITIAL CONTEXT SETUP REQUEST message containing
the IE "CS Fallback Indicator" from the MME and the eNodeB determines that the CSFB
procedure is for LCS.
As shown at point A in Figure 2-139, the L.CSFB.LCS.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 LCS.
Figure 2-138

Figure 2-139
Formula
None
Unit
None
Related Features
L.CSFB.LCS.PrepAtt Multi-mode: None

GSM: None
UMTS: None
LOFD-001023 SRVCC to GERAN
2.2.23.32 Number of Responses Sent from the eNodeB to MMEs for CSFB Triggered
by LCS

Counters
Description
1526728410 L.CSFB.LCS.Pre- Number of responses DBS3900 LTE/

pSucc sent from the BTS3900 LTE/
eNodeB to MMEs BTS3900A LTE/
for CSFB triggered BTS3900L LTE/
by LCS BTS3900AL LTE,
BTS3900
Description
The counter measures the number of responses sent from the eNodeB to MMEs for CSFB
triggered by LCS.
Measurement Points
As shown at point C in Figure 2-140, the L.CSFB.LCS.PrepSucc counter is incremented by 1
each time the eNodeB successfully sends an INITIAL CONTEXT SETUP RESPONSE message
to the MME and the corresponding INITIAL CONTEXT SETUP REQUEST message is
determined that the CSFB procedure is for LCS.
As shown at point C in Figure 2-141, 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 2-140

Figure 2-141
Formula
None
Unit
None
Related Features
L.CSFB.LCS.PrepSucc Multi-mode: None

GSM: None
UMTS: None
LOFD-001023 SRVCC to GERAN
2.2.23.33 Number of CCO Executions from E-UTRAN to GERAN

Counters
Description
1526728441 L.CCO.E2G.Exe- Number of CCO DBS3900 LTE/

cAttOut executions from E- BTS3900 LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of CCO executions from E-UTRAN to GERAN in a cell.
Measurement Points
As shown at point B in Figure 2-142, during a CCO procedure from E-UTRAN to GERAN the
L.CCO.E2G.ExecAttOut counter is incremented by 1 each time the eNodeB sends a Mobility
From EUTRA Command message to the UE.
Figure 2-142
Formula
None

Unit
None
Related Features
L.CCO.E2G.ExecAttOut Multi-mode: None

GSM: None
UMTS: None
GERAN
between E-UTRAN and
GERAN
2.2.23.34 Number of Successful CCOs from E-UTRAN to GERAN
Counters
Description
1526728442 L.CCO.E2G.Exe- Number of DBS3900 LTE/

cSuccOut successful CCOs BTS3900 LTE/
GERAN BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of successful CCOs from E-UTRAN to GERAN in a cell.
Measurement Points
As shown at point C in Figure 2-143, during a CCO procedure from E-UTRAN to GERAN the
L.CCO.E2G.ExecSuccOut counter is incremented by 1 each time the eNodeB receives a UE
CONTEXT RELEASE COMMAND message from the MME after the UE is handed over from
E-UTRAN to GERAN.

Figure 2-143
Formula
None
Unit
None
Related Features
L.CCO.E2G.ExecSuccOut Multi-mode: None

GSM: None
UMTS: None
GERAN
between E-UTRAN and
GERAN

2.2.23.35 Number of Inter-RAT Handover Initiation Failures Because the Adjacent

Cell is not the NRT of the Source Cell
Counters
Description
1526728468 L.IRATHO.E2W.No Number of inter- DBS3900 LTE/

NRT RAT initiation BTS3900 LTE/
failures from E- BTS3900A LTE/
because the adjacent BTS3900
cell is not on the NRT
of the source cell
1526728469 L.IRATHO.E2T.No Number of inter- DBS3900 LTE/

because the adjacent BTS3900
cell is not on the NRT
of the source cell
1526728470 L.IRATHO.E2G.No Number of inter- DBS3900 LTE/

because the adjacent BTS3900AL LTE,
cell is not on the NRT BTS3900
of the source cell
1526728471 L.IRATHO.E21xRT Number of inter- DBS3900 LTE/

T.NoNRT RAT initiation BTS3900 LTE/
CDMA2000 1xRTT BTS3900AL LTE,
network because the BTS3900
adjacent cell is not on
the NRT of the
source cell


Description
1526728472 L.IRATHO.E2HRP Number of inter- DBS3900 LTE/

D.NoNRT RAT initiation BTS3900 LTE/
CDMA2000 HRPD BTS3900AL LTE,
network because the BTS3900
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 2-144 or Figure 2-145, the corresponding counter is incremented
by 1 each time the source cell receives the first measurement report from the UE and determines
to initiate a handover, but the handover initiation fails because the adjacent cell that has the best
signal quality in the first measurement report is not on the NRT of the source cell. On GERANs,
measurement is reported based on the measurement mechanism configured by the corresponding
handover module. On UTRANs and CDMA2000 network, measurement is reported based on
the measurement mechanism configured by the SON module. Figure 2-144 shows the
measurement procedure on a GERAN. Figure 2-145 shows the measurement procedure on a
UTRAN or a CDMA2000 network. The counters are measured as follows:
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 2-144
Figure 2-145
Formula
None
Unit
None

Related Features
L.IRATHO.E2W.NoNRT Multi-mode: None

GSM: None
UMTS: None
UTRAN
TDLOFD-001019
Inter-RAT ANR
TDLBFD-002002
between E-UTRAN and
UTRAN
Transport Channel
Management
L.IRATHO.E2T.NoNRT Multi-mode: None

GSM: None
UMTS: None
UTRAN
TDLOFD-001019
Inter-RAT ANR
TDLBFD-002002
between E-UTRAN and
UTRAN
Transport Channel
Management
L.IRATHO.E2G.NoNRT Multi-mode: None

GSM: None
UMTS: None
GERAN
TDLOFD-001020
Inter-RAT ANR
TDLBFD-002002
between E-UTRAN and
GERAN
Transport Channel
Management

L.IRATHO.E21xRTT.NoN Multi-mode: None

RT GSM: None
UMTS: None
CDMA2000
TDLBFD-002002
Inter-RAT ANR
Transport Channel
Management
L.IRATHO.E2HRPD.NoNR Multi-mode: None

T GSM: None
UMTS: None
CDMA2000
TDLBFD-002002
Inter-RAT ANR
Transport Channel
Management
2.2.23.36 Number of CSFB Preparation Failures Because of Process Conflict
Counters
Description
1526728513 L.CSFB.PrepFail.Co Number of CSFB DBS3900 LTE/

nflict preparation failures BTS3900 LTE/
because of process BTS3900A LTE/
conflict BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of CSFB preparation failures because of process conflict.
Measurement Points
As shown at point C in Figure 2-146, the L.CSFB.PrepFail.Conflict counter is incremented by
1 each time the eNodeB sends a UE CONTEXT MODIFICATION FAILURE message to the
MME containing the cause value "X2 Handover triggered", "S1 intra system Handover

triggered", or "S1 inter system Handover triggered" and the eNodeB determines that the CSFB
procedure is for voice services.
Figure 2-146
Formula
None
Unit
None
Related Features
L.CSFB.PrepFail.Conflict Multi-mode: None

GSM: None
UMTS: None

TDLOFD-001034
LOFD-001035
1xRTT
2.2.23.37 Number of Handover Preparation Attempts from E-UTRAN to WCDMA

Network Triggered Because of High Load

Counters
Description
1526728529 L.IRATHO.E2W.Lo Number of inter- DBS3900 LTE/

ad.PrepAttOut RAT handover BTS3900 LTE/
preparation attempts BTS3900A LTE/
triggered because of BTS3900
high load
1526728532 L.IRATHO.E2G.Lo Number of inter- DBS3900 LTE/

ad.PrepAttOut RAT handover BTS3900 LTE/
GERAN triggered BTS3900AL LTE,
because of high load BTS3900
Description
The counter measures the number of inter-RAT handover preparation attempts triggered because
of high load in a cell.
Measurement Points
As shown at point A in Figure 2-147, the L.IRATHO.E2W.Load.PrepAttOut counter is
incremented by 1 each time the eNodeB decides to perform a blind handover from E-UTRAN
to WCDMA network triggered because of high load or the eNodeB decides to perform a
handover from E-UTRAN to WCDMA network after the eNodeB receives a measurement report
from the UE triggered because of high load.
As shown at point A in Figure 2-147, the L.IRATHO.E2G.Load.PrepAttOut counter is

incremented by 1 each time the eNodeB decides to perform a blind handover from E-UTRAN
to GERAN triggered because of high load or the eNodeB decides to perform a handover from
E-UTRAN to GERAN after the eNodeB receives a measurement report from the UE triggered
because of high load.

Figure 2-147
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.Load.Pre- Multi-mode: None

pAttOut GSM: None
UMTS: None
TDLOFD-001044 UTRAN
UTRAN

L.IRATHO.E2G.Load.Pre- Multi-mode: None

pAttOut GSM: None
UMTS: None
TDLOFD-001045 GERAN
GERAN
2.2.23.38 Number of Inter-RAT Handover Execution Attempts Triggered Because

of High Load
Counters
Description
1526728530 L.IRATHO.E2W.Lo Number of inter- DBS3900 LTE/

ad.ExecAttOut RAT handover BTS3900 LTE/
high load
1526728533 L.IRATHO.E2G.Lo Number of inter- DBS3900 LTE/

ad.ExecAttOut RAT handover BTS3900 LTE/
GERAN triggered BTS3900AL LTE,
because of high load BTS3900
Description
The counter measures the number of inter-RAT handover execution attempts triggered because
of high load in a cell.
Measurement Points
As shown at point B in Figure 2-148, the L.IRATHO.E2W.Load.ExecAttOut counter is
incremented by 1 each time the eNodeB performs an inter-RAT handover from E-UTRAN to
WCDMA network triggered because of high load and sends a Mobility From EUTRA Command
message to the UE.
As shown at point B in Figure 2-148, the L.IRATHO.E2G.Load.ExecAttOut counter is

GERAN triggered because of high load and sends a Mobility From EUTRA Command message
to the UE.
Figure 2-148
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.Load.Exe- Multi-mode: None

cAttOut GSM: None
UMTS: None
TDLOFD-001044 UTRAN
UTRAN

L.IRATHO.E2G.Load.Exe- Multi-mode: None

cAttOut GSM: None
UMTS: None
TDLOFD-001045 GERAN
GERAN
2.2.23.39 Number of Successful Inter-RAT Handover Executions Triggered Because

of High Load
Counters
Description
1526728531 L.IRATHO.E2W.Lo Number of DBS3900 LTE/

ad.ExecSuccOut successful inter- BTS3900 LTE/
RAT handover BTS3900A LTE/
triggered because of
high load
1526728534 L.IRATHO.E2G.Lo Number of DBS3900 LTE/

high load
Description
The counter measures the number of successful inter-RAT handover executions triggered
because of high load in a cell.
Measurement Points
As shown at point C in Figure 2-149, the L.IRATHO.E2W.Load.ExecSuccOut counter is
WCDMA network triggered because of high load and the eNodeB receives a UE CONTEXT

RELEASE COMMAND message from the MME after the UE is handed over to a WCDMA
network.
As shown at point C in Figure 2-149, the L.IRATHO.E2G.Load.ExecSuccOut counter is

GERAN triggered because of high load and the eNodeB receives a UE CONTEXT RELEASE
COMMAND message from the MME after the UE is handed over to a GERAN.
Figure 2-149
Formula
None
Unit
None

Related Features
L.IRATHO.E2W.Load.Exe- Multi-mode: None

cSuccOut GSM: None
UMTS: None
TDLOFD-001044 UTRAN
UTRAN
L.IRATHO.E2G.Load.Exe- Multi-mode: None

cSuccOut GSM: None
UMTS: None
TDLOFD-001045 GERAN
GERAN
2.2.23.40 Number of Redirections from E-UTRAN to WCDMA Network Triggered

Because of High Load
Counters
Description

2W.Load redirections from E- BTS3900 LTE/
UTRAN to BTS3900A LTE/
triggered because of BTS3900AL LTE,
high load BTS3900

2G.Load redirections from E- BTS3900 LTE/
triggered because of BTS3900L LTE/
high load BTS3900AL LTE,
BTS3900
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. If the target system
is WCDMA network, the L.RRCRedirection.E2W.Load counter is incremented by 1. If the
target system is GERAN, the L.RRCRedirection.E2G.Load counter is incremented by 1.
Figure 2-150
Formula
None
Unit
None
Related Features
L.RRCRedirection.E2W.Lo Multi-mode: None

ad GSM: None
UMTS: None
TDLOFD-001044 UTRAN
UTRAN
L.RRCRedirection.E2G.Loa Multi-mode: None

d GSM: None
UMTS: None
TDLOFD-001045 GERAN
GERAN


Network Triggered for UEs to Go back to the HPLMN
Counters
Description
1526728542 L.IRATHO.E2W.Re Number of inter- DBS3900 LTE/

gainHPLMN.Pre- RAT handover BTS3900 LTE/
pAttOut attempts from E- BTS3900A LTE/
triggered for UEs to BTS3900
go back to the
HPLMN
Description
network triggered for UEs to go back to the HPLMN in a cell. In national roaming scenarios, if
the handovers back to the HPLMN for UEs are enabled, a roaming UE can be handed over to
the HPLMN when this UE moves back to the HPLMN.
Measurement Points
As shown at point A in Figure 2-151, the L.IRATHO.E2W.RegainHPLMN.PrepAttOut counter
is incremented by 1 each time the eNodeB decides to perform an inter-RAT handover to
WCDMA network after the eNodeB receives a measurement report from the UE. The
corresponding Measurement Control message is triggered for the UE to go back to the HPLMN.

Figure 2-151
Formula
None
Unit
None
Related Features
L.IRATHO.E2W.RegainHP Multi-mode: None

LMN.PrepAttOut GSM: None
UMTS: None
Camp & Handover Based on
SPID

Network Triggered for UEs to Go back to the HPLMN

Counters
Description
1526728543 L.IRATHO.E2W.Re Number of inter- DBS3900 LTE/

gainHPLMN.Exe- RAT handover BTS3900 LTE/
cAttOut executions from E- BTS3900A LTE/
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.
Measurement Points
As shown at point B in Figure 2-152, the L.IRATHO.E2W.RegainHPLMN.ExecAttOut counter
is incremented by 1 each time the eNodeB performs an inter-RAT handover from E-UTRAN to
WCDMA network after the eNodeB receive a HANDOVER COMMAND from the MME and
sends a Mobility From EUTRA Command message to the UE. The handover is triggered for the
UE to go back to the HPLMN.
Figure 2-152

Formula
None
Unit
None
Related Features

LMN.ExecAttOut GSM: None
UMTS: None
SPID
2.2.23.43 Number of Inter-RAT Handovers from E-UTRAN to WCDMA Network

Triggered for UEs to Go back to the HPLMN
Counters
Description
1526728544 L.IRATHO.E2W.Re Number of DBS3900 LTE/

gainHPLMN.Exe- successful inter- BTS3900 LTE/
cSuccOut RAT handovers from BTS3900A LTE/
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.

Measurement Points
As shown at point C in Figure 2-153, the L.IRATHO.E2W.RegainHPLMN.ExecSuccOut
counter is incremented by 1 each time the eNodeB receives a UE CONTEXT RELEASE
COMMAND message from the MME after the UE is handed over to WCDMA network. The
corresponding handover is triggered for the UE to go back to the HPLMN.
Figure 2-153
Formula
None
Unit
None
Related Features

LMN.ExecSuccOut GSM: None
UMTS: None
SPID


Network Triggered for UEs That Do not Transmit or Receive Data
Counters
Description
1526728560 L.IRATHO.E2W.No Number of inter- DBS3900 LTE/

Data.ExecAttOut RAT handover BTS3900 LTE/
triggered for UEs BTS3900
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 2-154, during an inter-RAT handover that the UE does not transmit
or receive data, from an E-UTRAN to a WCDMA network the
L.IRATHO.E2W.NoData.ExecAttOut counter is incremented by 1 each time the eNodeB sends
a Mobility From EUTRA Command message to the UE.

Figure 2-154
Formula
None
Unit
None

Related Features
L.IRATHO.E2W.NoData.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
LOFD-001105 UTRAN
Dynamic DRX
Dynamic DRX

Network Triggered for UEs That Do not Transmit or Receive Data
Counters
Description
1526728561 L.IRATHO.E2W.No Number of DBS3900 LTE/

Data.ExecSuccOut successful inter- BTS3900 LTE/
triggered for UEs BTS3900
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 2-155, during an inter-RAT handover that the UE does not transmit
or receive data, from an E-UTRAN to a WCDMA network the

L.IRATHO.E2W.NoData.ExecSuccOut counter is incremented by 1 each time the eNodeB

receives a UE CONTEXT RELEASE COMMAND message from the MME after the UE is
handed over to a WCDMA network.
Figure 2-155
Formula
None
Unit
None

Related Features
L.IRATHO.E2W.NoData.E Multi-mode: None

UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
LOFD-001105 UTRAN
Dynamic DRX
Dynamic DRX
2.2.23.46 Number of LCS-based Inter-RAT Handover Executions for SRVCC
Counters
Description
1526728753 L.IRATHO.SRVCC. Number of CSFB- DBS3900 LTE/

LCS.E2W.PrepAtt- based handover BTS3900 LTE/
Out attempts from E- BTS3900A LTE/
for SRVCC BTS3900

LCS.E2W.ExecAtt- based handover BTS3900 LTE/
Out executions from E- BTS3900A LTE/
for SRVCC BTS3900


Description

LCS.E2W.Exe- successful CSFB- BTS3900 LTE/
cSuccOut based handovers BTS3900A LTE/
for SRVCC BTS3900

LCS.E2G.PrepAtt- based handover BTS3900 LTE/
BTS3900

LCS.E2G.ExecAtt- based handover BTS3900 LTE/
BTS3900

LCS.E2G.Exe- successful CSFB- BTS3900 LTE/
cSuccOut based handovers BTS3900A LTE/
GERAN for SRVCC BTS3900AL LTE,
BTS3900

LCS.E2T.PrepAtt- based handover BTS3900 LTE/
SCDMA network for BTS3900AL LTE,
SRVCC BTS3900

LCS.E2T.ExecAtt- based handover BTS3900 LTE/
BTS3900

LCS.E2T.ExecSucc- successful CSFB- BTS3900 LTE/
Out based handovers BTS3900A LTE/
network for SRVCC BTS3900

Description
The counters measure the number of CSFB-based inter-RAT handover attempts from E-UTRAN
to WCDMA network. If the UE is performing services with the QCI of 1, the SRVCC procedure
is triggered to retain the services with the QCI of 1 after the eNodeB receives a CS fallback
indicator.
Measurement Points
As shown at point A in Figure 2-156, the L.IRATHO.SRVCC.LCS.E2W.PrepAttOut counter
is incremented by 1 each time the eNodeB receives a measurement report from the UE triggered
by CSFB and the eNodeB decides to perform an SRVCC procedure from E-UTRAN to WCDMA
network.
As shown at point B in Figure 2-156, the L.IRATHO.SRVCC.LCS.E2W.ExecAttOut counter

is incremented by 1 each time the eNodeB decides to perform an SRVCC procedure from E-
UTRAN to WCDMA network triggered by CSFB and the eNodeB sends a Mobility From
EUTRA Command message to the UE.
As shown at point C in Figure 2-156, the L.IRATHO.SRVCC.LCS.E2W.ExecSuccOut counter

UTRAN to WCDMA network triggered by CSFB and the eNodeB receives a UE CONTEXT
RELEASE COMMAND message from the MME after the UE is handed over to a WCDMA
network.
As shown at point A in Figure 2-156, the L.IRATHO.SRVCC.LCS.E2G.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 GERAN.
As shown at point B in Figure 2-156, the L.IRATHO.SRVCC.LCS.E2G.ExecAttOutOut

counter is incremented by 1 each time the eNodeB decides to perform an SRVCC procedure
from E-UTRAN to GERAN triggered by CSFB and the eNodeB sends a Mobility From EUTRA
Command message to the UE.
As shown at point C in Figure 2-156, the L.IRATHO.SRVCC.LCS.E2G.ExecSuccOut counter

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 2-156, the L.IRATHO.SRVCC.LCS.E2T.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 TD-
SCDMA network.
As shown at point B in Figure 2-156, the L.IRATHO.SRVCC.LCS.E2T.ExecAttOut counter is

incremented by 1 each time the eNodeB decides to perform an SRVCC procedure from E-
UTRAN to TD-SCDMA network triggered by CSFB and the eNodeB sends a Mobility From
EUTRA Command message to the UE.
As shown at point C in Figure 2-156, the L.IRATHO.SRVCC.LCS.E2T.ExecSuccOut counter

UTRAN to TD-SCDMA network triggered by CSFB and the eNodeB receives a UE CONTEXT
RELEASE COMMAND message from the MME after the UE is handed over to a TD-SCDMA
network.

Figure 2-156
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.LCS.E Multi-mode: None

2W.PrepAttOut GSM: None
UMTS: None

2W.ExecAttOut GSM: None
UMTS: None


2W.ExecSuccOut GSM: None
UMTS: None

2G.PrepAttOut GSM: None
UMTS: None

2G.ExecAttOut GSM: None
UMTS: None

2G.ExecSuccOut GSM: None
UMTS: None

2T.PrepAttOut GSM: None
UMTS: None

2T.ExecAttOut GSM: None
UMTS: None

2T.ExecSuccOut GSM: None
UMTS: None

2.2.23.47 Number of Responses for Abnormal Causes Received by the eNodeB from
the MME During Inter-RAT Handover Executions from E-UTRAN to Another
System
Counters
Description
1526728889 L.IRATHO.E21xRT Number of responses DBS3900 LTE/

T.MMEAbnormRsp for abnormal causes BTS3900 LTE/
received by the BTS3900A LTE/
eNodeB from the BTS3900L LTE/
MME during inter- BTS3900AL LTE,
RAT handover BTS3900
executions from E-
UTRAN to
CDMA2000 1xRTT
network
1526728890 L.IRATHO.E2HRP Number of responses DBS3900 LTE/

D.MMEAbnormRsp for abnormal causes BTS3900 LTE/
executions from E-
UTRAN to
CDMA2000 HRPD
network
1526728891 L.IRATHO.E2W.M Number of responses DBS3900 LTE/

MEAbnormRsp for abnormal causes BTS3900 LTE/
executions from E-
UTRAN to
WCDMA network
1526728892 L.IRATHO.E2G.M Number of responses DBS3900 LTE/

executions from E-
UTRAN to GERAN


Description
1526728893 L.IRATHO.E2T.M Number of responses DBS3900 LTE/

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
As shown at point C in Figure 2-157, during an inter-RAT handover from E-UTRAN to another
system the corresponding counter is incremented by 1 based on the handover target system each
time the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME
and the release cause is not "Successful Handover" or "Normal Release". If the target system is
CDMA2000 1xRTT network, the L.IRATHO.E21xRTT.MMEAbnormRsp counter is
incremented by 1. If the target system is CDMA2000 HRPD network, the
L.IRATHO.E21HRPD.MMEAbnormRsp counter is incremented by 1.
system the corresponding counter is incremented by 1 based on the handover target system each
time the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME
and the release cause is not "Successful Handover" or "Normal Release". If the target system is
WCDMA network, the L.IRATHO.E2W.MMEAbnormRsp counter is incremented by 1. If the
target system is TD-SCDMA network, the L.IRATHO.E2T.MMEAbnormRsp counter is
incremented by 1. If the target system is GERAN, the L.IRATHO.E2G.MMEAbnormRsp
counter is incremented by 1.

Figure 2-157
Figure 2-158

Formula
None
Unit
None
Related Features
L.IRATHO.E21xRTT.MME Multi-mode: None

AbnormRsp GSM: None
UMTS: None
between E-UTRAN and
CDMA2000
L.IRATHO.E2HRPD.MME Multi-mode: None

AbnormRsp GSM: None
UMTS: None
between E-UTRAN and
CDMA2000
L.IRATHO.E2W.MMEAb- Multi-mode: None

normRsp GSM: None
UMTS: None
UTRAN
between E-UTRAN and
UTRAN
L.IRATHO.E2G.MMEAb- Multi-mode: None

normRsp GSM: None
UMTS: None
GERAN
between E-UTRAN and
GERAN

L.IRATHO.E2T.MMEAb- Multi-mode: None

normRsp GSM: None
UMTS: None
UTRAN
between E-UTRAN and
UTRAN
the MME During Inter-RAT Handover Executions from E-UTRAN to Another
System for SRVCC
Counters
Description
1526728894 L.IRATHO.SRVCC. Number of responses DBS3900 LTE/

E2W.MMEAbnorm for abnormal causes BTS3900 LTE/
Rsp received by the BTS3900A LTE/
executions from E-
UTRAN to
WCDMA network
for SRVCC

E2G.MMEAbnorm for abnormal causes BTS3900 LTE/
Rsp received by the BTS3900A LTE/
executions from E-
UTRAN to GERAN
for SRVCC


Description

E2T.MMEAbnormR for abnormal causes BTS3900 LTE/
sp received by the BTS3900A LTE/
executions from E-
UTRAN to TD-
SCDMA network for
SRVCC
Description
from the MME during inter-RAT handover executions from E-UTRAN to another system for
SRVCC.
Measurement Points
system for SRVCC, the corresponding counter is incremented by 1 based on the handover target
system each time the eNodeB receives a UE CONTEXT RELEASE COMMAND message from
the MME and the release cause is not "Successful Handover" or "Normal Release". If the target
system is WCDMA network, the L.IRATHO.SRVCC.E2W.MMEAbnormRsp counter is
incremented by 1. If the target system is TD-SCDMA network, the
L.IRATHO.SRVCC.E2T.MMEAbnormRsp counter is incremented by 1. If the target system is
GERAN, the L.IRATHO.SRVCC.E2G.MMEAbnormRsp counter is incremented by 1.

Figure 2-159
Formula
None
Unit
None
Related Features
L.IRATHO.SRVCC.E2W. Multi-mode: None

MMEAbnormRsp GSM: None
UMTS: None
L.IRATHO.SRVCC.E2G.M Multi-mode: None

MEAbnormRsp GSM: None
UMTS: None

L.IRATHO.SRVCC.E2T.M Multi-mode: None

UMTS: None
the MME During CCO Executions from E-UTRAN to GERAN
Counters
Description
1526728897 L.CCO.E2G.MMEA Number of responses DBS3900 LTE/

bnormRsp for abnormal causes BTS3900 LTE/
MME during CCO BTS3900AL LTE,
executions from E- BTS3900
UTRAN to GERAN
Description
The counter measures the number of responses for abnormal causes received by the eNodeB
from the MME during CCO executions from E-UTRAN to GERAN.
Measurement Points
As shown at point C in Figure 2-160, during a CCO execution from E-UTRAN to GERAN the
L.CCO.E2G.MMEAbnormRsp counter is incremented by 1 each time the eNodeB receives a
UE CONTEXT RELEASE COMMAND message from the MME and the release cause is not
"Successful Handover" or "Normal Release".

Figure 2-160
Formula
None
Unit
None
Related Features
L.CCO.E2G.MMEAb- Multi-mode: None

normRsp GSM: None
UMTS: None
GERAN
between E-UTRAN and
GERAN

the MME During CSFB-based Inter-RAT Handover Executions from E-UTRAN to
Another System
Counters
Description
1526728898 L.IRATHO.E2C.CS Number of responses DBS3900 LTE/

FB.MMEAbnormRs for abnormal causes BTS3900 LTE/
p received by the BTS3900A LTE/
MME during CSFB- BTS3900AL LTE,
based inter-RAT BTS3900
handover executions
from E-UTRAN to
CDMA2000
network
1526728899 L.IRATHO.E2W.CS Number of responses DBS3900 LTE/

handover executions
from E-UTRAN to
WCDMA network
1526728900 L.IRATHO.E2G.CS Number of responses DBS3900 LTE/

handover executions
from E-UTRAN to
GERAN
1526728901 L.IRATHO.E2T.CS Number of responses DBS3900 LTE/

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.
Measurement Points
As shown at point C in Figure 2-161, during an CSFB-based inter-RAT handover from E-
UTRAN to CDMA2000 network, the L.IRATHO.E2C.CSFB.MMEAbnormRsp counter is
message from the MME and the release cause is not "Successful Handover" or "Normal Release".
As shown at point C in Figure 2-162, during an CSFB-based inter-RAT handover from E-

UTRAN to another system, the corresponding counter is incremented by 1 based on the handover
target system each time the eNodeB receives a UE CONTEXT RELEASE COMMAND message
from the MME and the release cause is not "Successful Handover" or "Normal Release". If the
target system is WCDMA network, the L.IRATHO.E2W.CSFB.MMEAbnormRsp counter is
incremented by 1. If the target system is TD-SCDMA network, the
L.IRATHO.E2T.CSFB.MMEAbnormRsp counter is incremented by 1. If the target system is
GERAN, the L.IRATHO.E2G.CSFB.MMEAbnormRsp counter is incremented by 1.
Figure 2-161

Figure 2-162
Formula
None
Unit
None
Related Features
L.IRATHO.E2C.CSFB.MM Multi-mode: None

EAbnormRsp GSM: None
UMTS: None
1xRTT
L.IRATHO.E2W.CSFB.M Multi-mode: None

UMTS: None

L.IRATHO.E2G.CSFB.MM Multi-mode: None

UMTS: None
L.IRATHO.E2T.CSFB.MM Multi-mode: None

UMTS: None
2.2.24 Measurement related to IRATHOIN (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
2-163.
Figure 2-163

Counters
Description
1526727033 Handover from E- Success rate of inter- V100R008C00,and

UTRAN to RAT handovers from the mapping single-
CDMA2000 E-UTRAN to mode base station
Success Rate CDMA2000 version that
network introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

UTRAN to RAT handovers from the mapping single-
WCDMA Success E-UTRAN to mode base station
Rate WCDMA network version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

UTRAN to GERAN RAT handovers from the mapping single-
Success Rate E-UTRAN to mode base station
GERAN version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526728866 L.IRATHO.G2E.P Number of inter- V100R008C00,and

repAttIn RAT handover the mapping single-
attempts from mode base station
GERAN to E- version that
UTRAN introduce this
counter is:
eNodeB:V100R006
C00
1526728867 L.IRATHO.G2E.P Number of V100R008C00,and

repInSucc successful inter- the mapping single-
preparations from version that
GERAN to E- introduce this
UTRAN counter is:
eNodeB:V100R006
C00


Description
1526728868 L.IRATHO.G2E.E Number of V100R008C00,and

xecSuccIn successful inter- the mapping single-
GERAN to E- version that
UTRAN introduce this
counter is:
eNodeB:V100R006
C00
1526728869 L.IRATHO.G2E.P Number of inter- V100R008C00,and

repInFail.TgtNo- RAT handover the mapping single-
tAllow preparation failures mode base station
from GERAN in the version that
target cell due to introduce this
Handover Target not counter is:
allowed eNodeB:V100R006
C00
1526728870 L.IRATHO.T2E.Pr Number of inter- V100R008C00,and

epAttIn RAT handover the mapping single-
attempts from TD- mode base station
SCDMA network to version that
E-UTRAN introduce this
counter is:
eNodeB:V100R006
C00
1526728871 L.IRATHO.T2E.Pr Number of V100R008C00,and

epInSucc successful inter- the mapping single-
network to E- counter is:
UTRAN eNodeB:V100R006
C00
1526728872 L.IRATHO.T2E.E Number of V100R008C00,and

TD-SCDMA version that
network to E- introduce this
UTRAN counter is:
eNodeB:V100R006
C00


Description
1526728873 L.IRATHO.T2E.Pr Number of inter- V100R008C00,and

epInFail.TgtNotAl- RAT handover the mapping single-
low preparation failures mode base station
from TD-SCDMA version that
network with the introduce this
cause of "Handover counter is:
Target not allowed" eNodeB:V100R006
in the target cell C00
1526728874 L.IRATHO.W2E.P Number of inter- V100R008C00,and

repAttIn RAT handover the mapping single-
attempts from mode base station
counter is:
eNodeB:V100R006
C00
1526728875 L.IRATHO.W2E.P Number of V100R008C00,and

repInSucc successful inter- the mapping single-
WCDMA network to introduce this
E-UTRAN counter is:
eNodeB:V100R006
C00
1526728876 L.IRATHO.W2E.E Number of V100R008C00,and

counter is:
eNodeB:V100R006
C00
1526728877 L.IRATHO.W2E.P Number of inter- V100R008C00,and

repInFail.TgtNo- RAT handover the mapping single-
tAllow preparation failures mode base station
from WCDMA version that
network in the target introduce this
cell due to Handover counter is:
Target not allowed eNodeB:V100R006
C00
None

2.2.24.1 Success Rate of Inter-RAT Handovers from E-UTRAN to CDMA2000

Network
Counters
Description
1526727033 Handover from E- Success rate of inter- DBS3900 LTE/

UTRAN to RAT handovers from BTS3900 LTE/
CDMA2000 Success E-UTRAN to BTS3900A LTE/
Rate CDMA2000 BTS3900L LTE/
network BTS3900AL LTE,
BTS3900
Description
The counter measures the success rate of inter-RAT handovers from E-UTRAN to CDMA2000
network in a cell.
The counter will be deleted in later versions. It is reported normally in the current version but
Measurement Points
The success rate of inter-RAT handovers from E-UTRAN to CDMA2000 network in a cell is
calculated by using the corresponding KPI calculation formula based on the values of the
counters L.IRATHO.E2C.ExecSuccOut and L.IRATHO.E2C.ExecAttOut.
Formula
{100}*[L.IRATHO.E2C.ExecSuccOut]/ [L.IRATHO.E2C.ExecAttOut]
Unit
%

Related Features
Handover from E-UTRAN to Multi-mode: None

CDMA2000 Success Rate GSM: None
UMTS: None
CDMA2000
1xRTT
2.2.24.2 Success Rate of Inter-RAT Handovers from E-UTRAN to WCDMA

Network
Counters
Description

UTRAN to RAT handovers from BTS3900 LTE/
WCDMA Success E-UTRAN to BTS3900A LTE/
Rate WCDMA network BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the success rate of inter-RAT handovers from E-UTRAN to WCDMA
network in a cell.
Measurement Points
The success rate of inter-RAT handovers from E-UTRAN to WCDMA network in a cell is
calculated by using the corresponding KPI calculation formula based on the values of the
counters L.IRATHO.E2W.ExecSuccOut and L.IRATHO.E2W.ExecAttOut.
Formula
{100}*[L.IRATHO.E2W.ExecSuccOut]/ [L.IRATHO.E2W.ExecAttOut]

Unit
%
Related Features

WCDMA Success Rate GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN
2.2.24.3 Success Rate of Inter-RAT Handovers from E-UTRAN to GERAN
Counters
Description

UTRAN to GERAN RAT handovers from BTS3900 LTE/
Success Rate E-UTRAN to BTS3900A LTE/
GERAN BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the success rate of inter-RAT handovers from E-UTRAN to GERAN in
a cell.

Measurement Points
The success rate of inter-RAT handovers from E-UTRAN to GERAN in a cell is calculated by
using the corresponding KPI calculation formula based on the values of the counters
L.IRATHO.E2G.ExecSuccOut and L.IRATHO.E2G.ExecAttOut.
Formula
{100}*[L.IRATHO.E2G.ExecSuccOut]/ [L.IRATHO.E2G.ExecAttOut]
Unit
%
Related Features

GERAN Success Rate GSM: None
UMTS: None
GERAN
TDLOFD-001020
SRVCC to GERAN
TDLOFD-001023
between E-UTRAN and
GERAN
SRVCC to GERAN
2.2.24.4 Number of Inter-RAT Handover Attempts from GERAN to E-UTRAN
Counters
Description
1526728866 L.IRATHO.G2E.Pre Number of inter- DBS3900 LTE/

pAttIn RAT handover BTS3900 LTE/
attempts from BTS3900A LTE/
GERAN to E- BTS3900L LTE/
UTRAN BTS3900AL LTE,
BTS3900

Description
The counter measures the number of inter-RAT handover attempts from GERAN to E-UTRAN
in a cell.
Measurement Points
As shown at point A in Figure 2-164, the L.IRATHO.G2E.PrepAttIn counter is incremented by
1 each time the eNodeB receives a HANDOVER REQUEST message from the MME and this
message indicates an inter-RAT handover preparation from GERAN to E-UTRAN.
Figure 2-164
Formula
None
Unit
None

Related Features
L.IRATHO.G2E.PrepAttIn Multi-mode: None

GSM: None
UMTS: None
GERAN
TDLOFD-001020
SRVCC to GERAN
TDLOFD-001023
between E-UTRAN and
GERAN
SRVCC to GERAN
2.2.24.5 Number of Inter-RAT Handover Preparation from GERAN to E-UTRAN
Counters
Description
1526728867 L.IRATHO.G2E.Pre Number of DBS3900 LTE/

pInSucc successful inter- BTS3900 LTE/
preparations from BTS3900L LTE/
GERAN to E- BTS3900AL LTE,
UTRAN BTS3900
Description
The counter measures the number of successful inter-RAT handover preparations from GERAN
to E-UTRAN in a cell.
Measurement Points
As shown at point B in Figure 2-165, the L.IRATHO.G2E.PrepInSucc counter is incremented
by 1 each time the eNodeB sends a HANDOVER REQUEST ACKNOWLEDGE message to
the MME and this message indicates a successful inter-RAT handover preparation from GERAN
to E-UTRAN.

Figure 2-165
Formula
None
Unit
None
Related Features
L.IRATHO.G2E.PrepIn- Multi-mode: None

Succ GSM: None
UMTS: None
GERAN
TDLOFD-001020
SRVCC to GERAN
TDLOFD-001023
between E-UTRAN and
GERAN
SRVCC to GERAN
2.2.24.6 Number of Successful Inter-RAT Handovers from GERAN to E-UTRAN

Counters
Description
1526728868 L.IRATHO.G2E.Ex- Number of DBS3900 LTE/

ecSuccIn successful inter- BTS3900 LTE/
GERAN to E- BTS3900L LTE/
UTRAN BTS3900AL LTE,
BTS3900
Description
The counter measures the number of successful inter-RAT handovers from GERAN to E-
UTRAN in a cell.
Measurement Points
As shown at point C in Figure 2-166, the L.IRATHO.G2E.ExecSuccIn counter is incremented
by 1 each time the eNodeB sends a HANDOVER NOTIFY message to the MME and this
message indicates a successful inter-RAT handover from GERAN to E-UTRAN.
Figure 2-166
Formula
None
Unit
None

Related Features
L.IRATHO.G2E.ExecSuc- Multi-mode: None

cIn GSM: None
UMTS: None
GERAN
TDLOFD-001020
SRVCC to GERAN
TDLOFD-001023
between E-UTRAN and
GERAN
SRVCC to GERAN
2.2.24.7 Number of Inter-RAT inter-RAT Handover Preparation Failures for

Different Causes in a Cell
Counters
Description
1526728869 L.IRATHO.G2E.Pre Number of inter- DBS3900 LTE/

pInFail.TgtNotAl- RAT handover BTS3900 LTE/
low preparation failures BTS3900A LTE/
from GERAN in the BTS3900L LTE/
target cell due to BTS3900AL LTE,
Handover Target not BTS3900
allowed
1526728873 L.IRATHO.T2E.Pre Number of inter- DBS3900 LTE/

pInFail.TgtNotAl- RAT handover BTS3900 LTE/
from TD-SCDMA BTS3900L LTE/
network with the BTS3900AL LTE,
cause of "Handover BTS3900
Target not allowed"
in the target cell


Description
1526728877 L.IRATHO.W2E.Pr Number of inter- DBS3900 LTE/

epInFail.TgtNotAl- RAT handover BTS3900 LTE/
from WCDMA BTS3900L LTE/
network in the target BTS3900AL LTE,
cell due to Handover BTS3900
Target not allowed
Description
The counters measure the number of inter-RAT handover preparation failures with the cause of
"Handover Target not allowed."
Measurement Points
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

counter is incremented by 1.
Figure 2-167

Formula
None
Unit
None
Related Features
L.IRATHO.G2E.PrepInFail. Multi-mode: None

TgtNotAllow GSM: None
UMTS: None
GERAN
TDLOFD-001020
SRVCC to GERAN
TDLOFD-001023
between E-UTRAN and
GERAN
SRVCC to GERAN
L.IRATHO.T2E.PrepInFail. Multi-mode: None

TgtNotAllow GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN

L.IRATHO.W2E.PrepInFail Multi-mode: None

.TgtNotAllow GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN
2.2.24.8 Number of Inter-RAT Handover Attempts from TD-SCDMA Network to

E-UTRAN
Counters
Description
1526728870 L.IRATHO.T2E.Pre Number of inter- DBS3900 LTE/

pAttIn RAT handover BTS3900 LTE/
attempts from TD- BTS3900A LTE/
SCDMA network to BTS3900L LTE/
E-UTRAN BTS3900AL LTE,
BTS3900
Description
The counter measures the number of inter-RAT handover attempts from TD-SCDMA network
Measurement Points
As shown at point A in Figure 2-168, the L.IRATHO.T2E.PrepAttIn counter is incremented by
1 each time the eNodeB receives a HANDOVER REQUEST message from the MME and this
message indicates an inter-RAT handover preparation from TD-SCDMA network to E-UTRAN.

Figure 2-168
Formula
None
Unit
None
Related Features
L.IRATHO.T2E.PrepAttIn Multi-mode: None

GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN

2.2.24.9 Number of Inter-RAT Handover Preparation from TD-SCDMA Network

to E-UTRAN
Counters
Description
1526728871 L.IRATHO.T2E.Pre Number of DBS3900 LTE/

pInSucc successful inter- BTS3900 LTE/
network to E- BTS3900
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 2-169, the L.IRATHO.T2E.PrepInSucc counter is incremented
the MME and this message indicates a successful inter-RAT handover preparation from TD-
SCDMA network to E-UTRAN.
Figure 2-169

Formula
None
Unit
None
Related Features
L.IRATHO.T2E.PrepInSucc Multi-mode: None

GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN
2.2.24.10 Number of Successful Inter-RAT Handovers from TD-SCDMA Network

to E-UTRAN
Counters
Description
1526728872 L.IRATHO.T2E.Ex- Number of DBS3900 LTE/

TD-SCDMA BTS3900L LTE/
network to E- BTS3900AL LTE,
UTRAN BTS3900
Description
The counter measures the number of successful inter-RAT handovers from TD-SCDMA
network to E-UTRAN in a cell.

Measurement Points
As shown at point C in Figure 2-170, the L.IRATHO.T2E.ExecSuccIn counter is incremented
by 1 each time the eNodeB sends a HANDOVER NOTIFY message from the MME and this
maessage indicates a successful inter-RAT handover from TD-SCDMA network to E-UTRAN.
Figure 2-170
Formula
None
Unit
None

Related Features
L.IRATHO.T2E.ExecSuc- Multi-mode: None

cIn GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN
2.2.24.11 Number of Inter-RAT Handover Attempts from WCDMA Network to E-

UTRAN
Counters
Description
1526728874 L.IRATHO.W2E.Pr Number of inter- DBS3900 LTE/

epAttIn RAT handover BTS3900 LTE/
attempts from BTS3900A LTE/
BTS3900
Description
The counter measures the number of inter-RAT handover attempts from WCDMA network to
E-UTRAN in a cell.
Measurement Points
As shown at point A in Figure 2-171, the L.IRATHO.W2E.PrepAttIn counter is incremented
by 1 each time the eNodeB receives a HANDOVER REQUEST message from the MME and
this message indicates an inter-RAT handover preparation from WCDMA network to E-
UTRAN.

Figure 2-171
Formula
None
Unit
None
Related Features
L.IRATHO.W2E.PrepAttIn Multi-mode: None

GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN

2.2.24.12 Number of Inter-RAT Handover Preparation from WCDMA Network to

E-UTRAN
Counters
Description
1526728875 L.IRATHO.W2E.Pr Number of DBS3900 LTE/

epInSucc successful inter- BTS3900 LTE/
WCDMA network to BTS3900AL LTE,
E-UTRAN BTS3900
Description
The counter measures the number of successful inter-RAT handover preparations from
WCDMA network to E-UTRAN in a cell.
Measurement Points
As shown at point B in Figure 2-172, the L.IRATHO.W2E.PrepInSucc counter is incremented
the MME and this message indicates a successful inter-RAT handover preparation from
WCDMA network to E-UTRAN.
Figure 2-172

Formula
None
Unit
None
Related Features
L.IRATHO.W2E.PrepIn- Multi-mode: None

Succ GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN
2.2.24.13 Number of Successful Inter-RAT Handovers from WCDMA Network to

E-UTRAN
Counters
Description
1526728876 L.IRATHO.W2E.Ex Number of DBS3900 LTE/

BTS3900
Description
The counter measures the number of successful inter-RAT handovers from WCDMA network

Measurement Points
As shown at point C in Figure 2-173, the L.IRATHO.W2E.ExecSuccIn counter is incremented
by 1 each time the eNodeB sends a HANDOVER NOTIFY message from the MME and this
message indicates a successful inter-RAT handover from WCDMA network to E-UTRAN.
Figure 2-173
Formula
None
Unit
None

Related Features
L.IRATHO.W2E.ExecSuc- Multi-mode: None

cIn GSM: None
UMTS: None
UTRAN
LOFD-001033
SRVCC to UTRAN
TDLOFD-001019
TDLOFD-001022
UTRAN
SRVCC to UTRAN
2.2.25 Measurement related to Intra eRan HOOUT

(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 2-174, Figure
2-175, Figure 2-176, and Figure 2-177.
Figure 2-174

Figure 2-175
Figure 2-176
Figure 2-177

Counters
Description
1526726995 L.HHO.IntraeNB.I Number of intra- V100R008C00,and

ntraFreq.PrepAtt- eNodeB intra- the mapping single-
Out frequency outgoing mode base station
handover attempts in version that
counter is:
eNodeB:Version
earlier than
V100R003C00

ntraFreq.ExecAtt- eNodeB intra- the mapping single-
handovers version that
executions in a cell introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526726997 L.HHO.IntraeNB.I Number of V100R008C00,and

ntraFreq.Exe- successful intra- the mapping single-
cSuccOut eNodeB intra- mode base station
frequency outgoing version that
handovers in a cell introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00

nterFreq.PrepAtt- eNodeB inter- the mapping single-
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

nterFreq.ExecAtt- eNodeB inter- the mapping single-
counter is:
eNodeB:Version
earlier than
V100R003C00

nterFreq.Exe- successful intra- the mapping single-
cSuccOut eNodeB inter- mode base station
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727001 L.HHO.IntereNB.I Number of inter- V100R008C00,and

ntraFreq.PrepAtt- eNodeB intra- the mapping single-
counter is:
eNodeB:Version
earlier than
V100R003C00

ntraFreq.ExecAtt- eNodeB intra- the mapping single-
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727003 L.HHO.IntereNB.I Number of V100R008C00,and

ntraFreq.Exe- successful inter- the mapping single-
cSuccOut eNodeB intra- mode base station
counter is:
eNodeB:Version
earlier than
V100R003C00


Description

nterFreq.PrepAtt- eNodeB inter- the mapping single-
counter is:
eNodeB:Version
earlier than
V100R003C00

nterFreq.ExecAtt- eNodeB inter- the mapping single-
counter is:
eNodeB:Version
earlier than
V100R003C00

nterFreq.Exe- successful inter- the mapping single-
cSuccOut eNodeB inter- mode base station
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727031 Intra-frequency Intra-Frequency V100R008C00,and

Handover Success handover success the mapping single-
Rate rate mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727032 Inter-frequency Inter-Frequency V100R008C00,and

Handover Success handover success the mapping single-
Rate rate mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526728229 L.HHO.BlindHO.P Number of outgoing V100R008C00,and

repAttOut blind handover the mapping single-
attempts in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728230 L.HHO.BlindHO.E Number of outgoing V100R008C00,and

xecAttOut blind handovers the mapping single-
executions in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728231 L.HHO.BlindHO.E Number of V100R008C00,and

xecSuccOut successful outgoing the mapping single-
blind handovers in a mode base station
cell version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728285 L.HHO.Prep.FailO Number of outgoing V100R008C00,and

ut.MME handover preparation the mapping single-
failures because of mode base station
faults on the MME version that
side introduce this
counter is:
eNodeB:V100R003
C00

ut.NoReply handover preparation the mapping single-
no responses from version that
the target cell introduce this
counter is:
eNodeB:V100R003
C00


Description

ut.PrepFailure handover preparation the mapping single-
failures because the mode base station
target cell sending version that
handover preparation introduce this
failure messages counter is:
eNodeB:V100R003
C00
1526728288 L.HHO.Prep.FailO Number of failed V100R008C00,and

ut.HOCancel outgoing handover the mapping single-
preparations because mode base station
the source cell version that
sending handover introduce this
cancellation counter is:
messages eNodeB:V100R003
C00
1526728325 L.RRCRedirection. Number of intra- V100R008C00,and

IntraLTE RAT redirections the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C00
1526728398 L.IntraFreqHO.No Number of intra- V100R008C00,and

NRT frequency handover the mapping single-
initiation failures mode base station
because the adjacent version that
cell is not on the NRT introduce this
of the source cell counter is:
eNodeB:V100R006
C00
1526728399 L.InterFreqHO.No Number of inter- V100R008C00,and

NRT frequency handover the mapping single-
initiation failures mode base station
because the target version that
cell is not configured introduce this
as a neighboring cell counter is:
for the source cell eNodeB:V100R006
C00


Description
1526728526 L.HHO.InterFreq. Number of inter- V100R008C00,and

Load.PrepAttOut frequency handover the mapping single-
counter is:
eNodeB:V100R005
C00

Load.ExecAttOut frequency handover the mapping single-
counter is:
eNodeB:V100R005
C00
1526728528 L.HHO.InterFreq. Number of V100R008C00,and

Load.ExecSuccOut successful inter- the mapping single-
frequency handover mode base station
executions triggered version that
because of high load introduce this
counter is:
eNodeB:V100R005
C00

RegainHPLMN.Pr frequency outgoing the mapping single-
epAttOut handover attempts mode base station
triggered for UEs to version that
go back to the introduce this
HPLMN counter is:
eNodeB:V100R006
C00

RegainHPLMN.Ex frequency outgoing the mapping single-
ecAttOut handover executions mode base station
triggered for UEs to version that
go back to the introduce this
HPLMN counter is:
eNodeB:V100R006
C00


Description

RegainHPLMN.Ex successful inter- the mapping single-
ecSuccOut frequency outgoing mode base station
handovers triggered version that
for UEs to go back to introduce this
the HPLMN counter is:
eNodeB:V100R006
C00
1526728554 L.HHO.IntraFreq. Number of intra- V100R008C00,and

NoData.ExecAtt- frequency handover the mapping single-
Out execution attempts mode base station
triggered for UEs version that
that do not transmit introduce this
or receive data counter is:
eNodeB:V100R006
C00
1526728555 L.HHO.IntraFreq. Number of V100R008C00,and

NoData.ExecSucc- successful intra- the mapping single-
Out frequency handover mode base station
for UEs that do not introduce this
transmit or receive counter is:
data eNodeB:V100R006
C00

NoData.ExecAtt- frequency handover the mapping single-
Out execution attempts mode base station
triggered for UEs version that
that do not transmit introduce this
or receive data counter is:
eNodeB:V100R006
C00

NoData.ExecSucc- successful inter- the mapping single-
Out frequency handover mode base station
for UEs that do not introduce this
transmit or receive counter is:
data eNodeB:V100R006
C00


Description
1526728863 L.HHO.FailOut.H Number of inter- V100R008C00,and

OCancel eNodeB outgoing the mapping single-
handover mode base station
cancellation version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728883 L.HHO.S1.IntraFr Number of responses V100R008C00,and

eq.MMEAbnormR for abnormal causes the mapping single-
sp received by the mode base station
MME during S1- introduce this
based outgoing intra- counter is:
frequency handover eNodeB:V100R006
executions in a cell C00
1526728884 L.HHO.S1.InterFr Number of responses V100R008C00,and

eq.MMEAbnormR for abnormal causes the mapping single-
sp received by the mode base station
MME during S1- introduce this
based outgoing inter- counter is:
frequency handover eNodeB:V100R006

ntraFreq.Succ.ReE successful intra- the mapping single-
st2Src eNodeB intra- mode base station
handovers where introduce this
RRC connections are counter is:
reestablished to the eNodeB:V100R006
source cell for UEs in C00
a cell

nterFreq.Succ.ReE successful intra- the mapping single-
st2Src eNodeB inter- mode base station
a cell


Description

ntraFreq.Succ.ReE successful inter- the mapping single-
st2Src eNodeB intra- mode base station
a cell

nterFreq.Succ.ReE successful inter- the mapping single-
st2Src eNodeB inter- mode base station
a cell
1526728922 L.HHO.BlindHO.S Number of V100R008C00,and

ucc.ReEst2Src successful blind the mapping single-
outgoing handovers mode base station
where RRC version that
connections are introduce this
reestablished to the counter is:
source cell for UEs in eNodeB:V100R006
a cell C00
Counter Sub Counter
L.HHO.IntraeNB.IntraFreq.ExecSuccOut L.HHO.IntraeNB.IntraFreq.Succ.ReEst2Src
L.HHO.IntraeNB.InterFreq.ExecSuccOut L.HHO.IntraeNB.InterFreq.Succ.ReEst2Src
L.HHO.IntereNB.IntraFreq.ExecSuccOut L.HHO.IntereNB.IntraFreq.Succ.ReEst2Src
L.HHO.IntereNB.IntraFreq.ExecSuccOut L.HHO.S1.IntraFreq.MMEAbnormRsp
L.HHO.IntereNB.InterFreq.ExecSuccOut L.HHO.IntereNB.InterFreq.Succ.ReEst2Src
L.HHO.IntereNB.InterFreq.ExecSuccOut L.HHO.S1.InterFreq.MMEAbnormRsp
L.HHO.BlindHO.ExecSuccOut L.HHO.BlindHO.Succ.ReEst2Src

2.2.25.1 Number of Intra-eNodeB Outgoing Handover Attempts in a Cell
Counters
Description
1526726995 L.HHO.IntraeNB.Int Number of intra- DBS3900 LTE/

raFreq.PrepAttOut eNodeB intra- BTS3900 LTE/
frequency outgoing BTS3900A LTE/
handover attempts in BTS3900L LTE/
BTS3900

erFreq.PrepAttOut eNodeB inter- BTS3900 LTE/
BTS3900
Description
The counters measure the number of intra-eNodeB intra-frequency outgoing handover attempts
and the number of intra-eNodeB inter-frequency outgoing handover attempts in a cell. In an
intra-eNodeB handover, the source cell and target cell are controlled by the same eNodeB. If
the source cell and target cell work on the same frequency, the handover is an intra-frequency
handover. If the source cell and target cell work on different frequencies, the handover is an
inter-frequency handover.
Measurement Points
As shown at point A in Figure 2-178, during an intra-eNodeB handover the corresponding
counter is incremented by 1 each time the eNodeB decides to perform an intra-eNodeB blind
handover or decides to perform an intra-eNodeB handover after the cell receives a measurement
report from the UE.
The counters are measured as follows:
If the source cell and target cell work on the same frequency, the
L.HHO.IntraeNB.IntraFreq.PrepAttOut counter is incremented by 1.
If the source cell and target cell work on different frequencies, the
L.HHO.IntraeNB.InterFreq.PrepAttOut counter is incremented by 1.

Figure 2-178
Formula
None
Unit
None
Related Features
L.HHO.IntraeNB.IntraFreq. Multi-mode: None

UMTS: None
frequency Handover
L.HHO.IntraeNB.InterFreq. Multi-mode: None

UMTS: None
LTE: LBFD-00201802 Coverage Based Inter-
frequency Handover
2.2.25.2 Number of Intra-eNodeB Outgoing Handovers Executions in a Cell

Counters
Description

raFreq.ExecAttOut eNodeB intra- BTS3900 LTE/
handovers BTS3900L LTE/
executions in a cell BTS3900AL LTE,
BTS3900

erFreq.ExecAttOut eNodeB inter- BTS3900 LTE/
BTS3900
Description
The counters measure the number of intra-eNodeB intra-frequency outgoing handover
executions and the number of intra-eNodeB inter-frequency outgoing handover executions in a
cell. In an intra-eNodeB handover, the source cell and target cell are controlled by the same
eNodeB. If the source cell and target cell work on the same frequency, the handover is an intra-
frequency handover. If the source cell and target cell work on different frequencies, the handover
is an inter-frequency handover.
Measurement Points
As shown at point B in Figure 2-179, during an intra-eNodeB handover the corresponding
counter is incremented by 1 each time the source cell sends an RRC Connection Reconfiguration
message to the UE.
L.HHO.IntraeNB.IntraFreq.ExecAttOut counter is incremented by 1.
L.HHO.IntraeNB.InterFreq.ExecAttOut counter is incremented by 1.

Figure 2-179
Formula
None
Unit
None
Related Features

UMTS: None
frequency Handover

UMTS: None
frequency Handover
2.2.25.3 Number of Successful Intra-eNodeB Outgoing Handovers in a Cell

Counters
Description
1526726997 L.HHO.IntraeNB.Int Number of DBS3900 LTE/

raFreq.ExecSuccOut successful intra- BTS3900 LTE/
eNodeB intra- BTS3900A LTE/
frequency outgoing BTS3900L LTE/
handovers in a cell BTS3900AL LTE,
BTS3900

erFreq.ExecSuccOut successful intra- BTS3900 LTE/
eNodeB inter- BTS3900A LTE/
BTS3900
Description
The counters measure the number of successful intra-eNodeB intra-frequency outgoing
handovers and the number of successful intra-eNodeB inter-frequency outgoing handovers in a
cell. In an intra-eNodeB handover, the source cell and target cell are controlled by the same
eNodeB. If the source cell and target cell work on the same frequency, the handover is an intra-
frequency handover. If the source cell and target cell work on different frequencies, the handover
is an inter-frequency handover.
Measurement Points
As shown at point C in Figure 2-180, during an intra-eNodeB handover the corresponding
counter is incremented by 1 each time data in the buffer is forwarded during the handover after
the target cell receives an RRC Connection Reconfiguration Complete message from the UE.

counter is incremented by 1 each time the target cell receives an RRC Connection
Reestablishment Complete message from the UE.

counter is incremented by 1 each time the source cell receives an RRC Connection
Reestablishment Complete message from the UE.
If the source cell and the target cell work on the same frequency, the
L.HHO.IntraeNB.IntraFreq.ExecSuccOut counter is incremented by 1.
If the source cell and the target cell work on different frequencies, the
L.HHO.IntraeNB.InterFreq.ExecSuccOut counter is incremented by 1.

Figure 2-180
Figure 2-181
Formula
None
Unit
None

Related Features

UMTS: None
frequency Handover

UMTS: None
frequency Handover
2.2.25.4 Number of Inter-eNodeB Outgoing Handover Attempts in a Cell
Counters
Description
1526727001 L.HHO.IntereNB.Int Number of inter- DBS3900 LTE/

raFreq.PrepAttOut eNodeB intra- BTS3900 LTE/
BTS3900

erFreq.PrepAttOut eNodeB inter- BTS3900 LTE/
BTS3900
Description
The counters measure the number of inter-eNodeB intra-frequency outgoing handover attempts
and the number of inter-eNodeB inter-frequency outgoing handover attempts in a cell. In an
inter-eNodeB handover, the source cell and target cell are controlled by different eNodeBs. Such

a handover is performed between different eNodeBs over the S1 or X2 interface. If the source
cell and target cell work on the same frequency, the handover is an intra-frequency handover.
If the source cell and target cell work on different frequencies, the handover is an inter-frequency
handover.
Measurement Points
As shown at point A in Figure 2-182, during an X2-based handover the corresponding counter
is incremented by 1 each time the source eNodeB decides to perform an X2-based blind handover
or the source eNodeB decides to perform an X2-based handover after the source cell receives a
measurement report from the UE.
As shown at point A in Figure 2-183, during an S1-based handover the corresponding counter
is incremented by 1 each time the source eNodeB decides to perform an S1-based blind handover
or the source eNodeB decides to perform an S1-based handover after the source cell receives a
L.HHO.IntereNB.IntraFreq.PrepAttOut counter is incremented by 1.
L.HHO.IntereNB.InterFreq.PrepAttOut counter is incremented by 1.
Figure 2-182

Figure 2-183
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

2.2.25.5 Number of Inter-eNodeB Outgoing Handovers Executions in a Cell
Counters
Description

raFreq.ExecAttOut eNodeB intra- BTS3900 LTE/
BTS3900

erFreq.ExecAttOut eNodeB inter- BTS3900 LTE/
BTS3900
Description
The counters measure the number of inter-eNodeB intra-frequency outgoing handover
executions and the number of inter-eNodeB inter-frequency outgoing handover executions in a
cell. In an inter-eNodeB handover, the source cell and target cell are controlled by different
eNodeBs. Such a handover is performed between different eNodeBs over the S1 or X2 interface.
If the source cell and target cell work on the same frequency, the handover is an intra-frequency
Measurement Points
As shown at point B in Figure 2-184, during an X2-based handover the corresponding counter
is incremented by 1 each time the source eNodeB sends an RRC Connection Reconfiguration
message to the UE after receiving a HANDOVER REQUEST ACKNOWLEDGE message from
the target eNodeB.
As shown at point B in Figure 2-185, during an S1-based handover the corresponding counter
is incremented by 1 each time the source eNodeB sends an RRC Connection Reconfiguration
message to the UE after receiving a HANDOVER COMMAND message from the MME.
L.HHO.IntereNB.IntraFreq.ExecAttOut counter is incremented by 1.
L.HHO.IntereNB.InterFreq.ExecAttOut counter is incremented by 1.

Figure 2-184
Figure 2-185
Formula
None
Unit
None

Related Features

UMTS: None
frequency Handover

UMTS: None
frequency Handover
2.2.25.6 Number of Successful Inter-eNodeB Outgoing Handovers in a Cell
Counters
Description
1526727003 L.HHO.IntereNB.Int Number of DBS3900 LTE/

raFreq.ExecSuccOut successful inter- BTS3900 LTE/
eNodeB intra- BTS3900A LTE/
BTS3900

erFreq.ExecSuccOut successful inter- BTS3900 LTE/
eNodeB inter- BTS3900A LTE/
BTS3900
Description
The counters measure the number of successful inter-eNodeB intra-frequency outgoing
handovers and the number of successful inter-eNodeB inter-frequency outgoing handovers in a
cell. In an inter-eNodeB handover, the source cell and target cell are controlled by different

eNodeBs. Such a handover is performed between different eNodeBs over the S1 or X2 interface.
If the source cell and target cell work on the same frequency, the handover is an intra-frequency
Measurement Points
is incremented by 1 each time data in the buffer is forwarded during the handover after the source
eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB.
As shown at point C in Figure 2-187, during an X2-based handover after an RRC connection
is successfully reestablished to the target eNodeB for the UE, the corresponding counter is
incremented by 1 each time data in the buffer is forwarded during the handover after the source
is successfully reestablished to the source eNodeB for the UE, the corresponding counter is
incremented by 1 each time.
As shown at point C in Figure 2-188, during an S1-based handover the corresponding counter
is incremented by 1 each time data in the buffer is forwarded during the handover after the source
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME.
As shown at point C in Figure 2-189, during an S1-based handover after an RRC connection is
successfully reestablished to the target eNodeB for the UE, the corresponding counter is
incremented by 1 each time data in the buffer is forwarded during the handover after the source
successfully reestablished to the source eNodeB for the UE, the corresponding counter is
incremented by 1 each time.
L.HHO.IntereNB.IntraFreq.ExecSuccOut counter is incremented by 1.
L.HHO.IntereNB.InterFreq.ExecSuccOut counter is incremented by 1.

Figure 2-186
Figure 2-187

Figure 2-188
Figure 2-189

Figure 2-190

Figure 2-191
Formula
None
Unit
None
Related Features

UMTS: None
frequency Handover


UMTS: None
frequency Handover
2.2.25.7 Intra-Frequency Handover Success Rate
Counters
Description
1526727031 Intra-frequency Intra-Frequency DBS3900 LTE/

Handover Success handover success BTS3900 LTE/
Rate rate BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the intra-frequency handover success rate in a cell.
Measurement Points
The intra-frequency handover success rate in a cell is calculated by using the corresponding KPI
calculation formula based on the values of the counters
L.HHO.IntereNB.IntraFreq.ExecSuccOut, L.HHO.IntraeNB.IntraFreq.ExecSuccOut,
L.HHO.IntereNB.IntraFreq.ExecAttOut, and L.HHO.IntraeNB.IntraFreq.ExecAttOut.
Formula
{100}*([L.HHO.IntereNB.IntraFreq.ExecSuccOut]+
[L.HHO.IntraeNB.IntraFreq.ExecSuccOut])/([L.HHO.IntereNB.IntraFreq.ExecAttOut]+
[L.HHO.IntraeNB.IntraFreq.ExecAttOut])
Unit
%

Related Features
Intra-frequency Handover Multi-mode: None

UMTS: None
frequency Handover
2.2.25.8 Inter-Frequency Handover Success Rate
Counters
Description
1526727032 Inter-frequency Inter-Frequency DBS3900 LTE/

Handover Success handover success BTS3900 LTE/
Rate rate BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the inter-frequency handover success rate in a cell.
Measurement Points
The inter-frequency handover success rate in a cell is calculated by using the corresponding KPI
calculation formula based on the values of the counters
L.HHO.IntereNB.InterFreq.ExecSuccOut, L.HHO.IntraeNB.InterFreq.ExecSuccOut,
L.HHO.IntereNB.InterFreq.ExecAttOut, and L.HHO.IntraeNB.InterFreq.ExecAttOut.
Formula
{100}*([L.HHO.IntereNB.InterFreq.ExecSuccOut]+
[L.HHO.IntraeNB.InterFreq.ExecSuccOut])/([L.HHO.IntereNB.InterFreq.ExecAttOut]+
[L.HHO.IntraeNB.InterFreq.ExecAttOut])

Unit
%
Related Features
Inter-frequency Handover Multi-mode: None

UMTS: None
frequency Handover
2.2.25.9 Number of Outgoing Blind Handover Attempts in a Cell
Counters
Description
1526728229 L.HHO.BlindHO.Pr Number of outgoing DBS3900 LTE/

epAttOut blind handover BTS3900 LTE/
attempts in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of intra-RAT outgoing blind handover attempts in a cell. Not
triggered on the basis of UE measurement reports, the blind handover is a handover in which
the eNodeB specifies the target cell for the UE. In specific networking scenarios, the eNodeB
performs a blind handover to actively hand over the UE from the target cell.
Measurement Points
As shown at point A in Figure 2-192, Figure 2-193, or Figure 2-194, the
L.HHO.BlindHO.PrepAttOut counter is incremented by 1 each time the eNodeB decides to
perform a blind handover. Figure 2-192 shows an intra-eNodeB blind handover, Figure
2-193 shows an X2-based blind handover, and Figure 2-194 shows an S1-based blind handover.

Figure 2-192
Figure 2-193

Figure 2-194
Formula
None
Unit
None
Related Features
L.HHO.BlindHO.PrepAtt- Multi-mode: None

Out GSM: None
UMTS: None
frequency Handover
2.2.25.10 Number of Outgoing Blind Handovers Executions in a Cell

Counters
Description
1526728230 L.HHO.BlindHO.Ex Number of outgoing DBS3900 LTE/

ecAttOut blind handovers BTS3900 LTE/
executions in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of intra-RAT outgoing blind handover executions in a cell.
Not triggered on the basis of UE measurement reports, the blind handover is a handover in which
Measurement Points
As shown at point B in Figure 2-195, Figure 2-196, or Figure 2-197, the
L.HHO.BlindHO.ExecAttOut counter is incremented by 1 each time the eNodeB decides to
perform a blind handover and sends an RRC Connection Reconfiguration message to the UE.
Figure 2-195 shows an intra-eNodeB blind handover, Figure 2-196 shows an X2-based blind
handover, and Figure 2-197 shows an S1-based blind handover.
Figure 2-195

Figure 2-196
Figure 2-197
Formula
None
Unit
None

Related Features
L.HHO.BlindHO.ExecAtt- Multi-mode: None

Out GSM: None
UMTS: None
frequency Handover
2.2.25.11 Number of Successful Outgoing Blind Handovers in a Cell
Counters
Description
1526728231 L.HHO.BlindHO.Ex Number of DBS3900 LTE/

ecSuccOut successful outgoing BTS3900 LTE/
blind handovers in a BTS3900A LTE/
cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of successful intra-RAT outgoing blind handovers in a cell.
Not triggered on the basis of UE measurement reports, the blind handover is a handover in which
Measurement Points
As shown at point C in Figure 2-198, the L.HHO.BlindHO.ExecSuccOut counter is incremented
by 1 each time the eNodeB decides to perform an intra-eNodeB blind handover and target cell
receives an RRC Connection Reconfiguration Complete message from the UE.

by 1 each time the target cell receives an RRC Connection Reestablishment Complete message
from the UE.

by 1 each time the source cell receives an RRC Connection Reestablishment Complete message
from the UE.


by 1 each time the eNodeB decides to perform an X2-based blind handover and the source
As shown at point C in Figure 2-201, during an X2-based blind handover the

L.HHO.BlindHO.ExecSuccOut 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 reestablished to the target eNodeB for the UE.

L.HHO.BlindHO.ExecSuccOut counter is incremented by 1 each time after an RRC connection
is successfully reestablished to the source eNodeB for the UE.

by 1 each time the eNodeB decides to perform an S1-based blind handover and the source
As shown at point C in Figure 2-203, during an S1-based handover the

L.HHO.BlindHO.ExecSuccOut 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 reestablished to the target eNodeB for the UE.

L.HHO.BlindHO.ExecSuccOut counter is incremented by 1 each time after an RRC connection
is successfully reestablished to the source eNodeB for the UE.
Figure 2-198

Figure 2-199
Figure 2-200

Figure 2-201
Figure 2-202

Figure 2-203

Figure 2-204

Figure 2-205
Formula
None
Unit
None
Related Features
L.HHO.BlindHO.ExecSucc- Multi-mode: None

Out GSM: None
UMTS: None
frequency Handover

2.2.25.12 Number of Outgoing Handover Failures for Different Causes in a Cell
Counters
Description
1526728285 L.HHO.Prep.FailOut Number of outgoing DBS3900 LTE/

.MME handover preparation BTS3900 LTE/
failures because of BTS3900A LTE/
faults on the MME BTS3900L LTE/
side BTS3900AL LTE,
BTS3900

.NoReply handover preparation BTS3900 LTE/
no responses from BTS3900L LTE/
the target cell BTS3900AL LTE,
BTS3900

.PrepFailure handover preparation BTS3900 LTE/
failures because the BTS3900A LTE/
target cell sending BTS3900L LTE/
handover preparation BTS3900AL LTE,
failure messages BTS3900
1526728288 L.HHO.Prep.FailOut Number of failed DBS3900 LTE/

.HOCancel outgoing handover BTS3900 LTE/
preparations because BTS3900A LTE/
the source cell BTS3900L LTE/
sending handover BTS3900AL LTE,
cancellation BTS3900
messages
1526728863 L.HHO.FailOut.HO- Number of inter- DBS3900 LTE/

Cancel eNodeB outgoing BTS3900 LTE/
handover BTS3900A LTE/
cancellation BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of outgoing handover failures based on the failure cause in a
cell. Outgoing handover failures usually occur during handover preparation and are caused by
faults on the MME side, no responses from the target cell, the target cell sending handover
preparation failure messages, or the source cell sending handover cancellation messages. During
the handover preparation phase, between the handover decision phase and the handover
execution phase, the handover resources are prepared.

Measurement Points
As shown at point B in Figure 2-206 during an S1-based handover preparation phase or as shown
at point B in Figure 2-207 during an X2-based handover preparation phase, the
L.HHO.Prep.FailOut.MME counter is incremented by 1 each time the source cell receives a UE
CONTEXT RELEASE COMMAND message from the MME.
As shown at point B in Figure 2-208 at the end of an S1-based handover preparation phase or
as shown at point B in Figure 2-209 at the end of an X2-based handover preparation phase, the
L.HHO.Prep.FailOut.NoReply counter is incremented by 1 each time the source cell does not
receive any message from the target eNodeB, such as the HANDOVER REQUEST
ACKNOWLEDEG and HANDOVER PREPARATION FAILURE messages sent from the
target eNodeB during the X2-based handover and the HANDOVER COMMAND and
HANDOVER PREPARATION FAILURE messages sent from the MME during the S1-based
handover.
As shown at point B in Figure 2-211, during an X2-based handover preparation phase the
L.HHO.Prep.FailOut.PrepFailure counter is incremented by 1 each time the source cell receives
a HANDOVER PREPARATION FAILURE message from the target cell. As shown at point B
in Figure 2-210, during an S1-based handover preparation phase the
L.HHO.Prep.FailOut.PrepFailure counter is incremented by 1 each time the source cell receives
a HANDOVER PREPARATION FAILURE message from the MME.
As show at point B in Figure 2-212 during an S1-based handover or as shown at point B in

Figure 2-213 during an X2-based handover, the L.HHO.Prep.FailOut.HOCancel counter is
incremented by 1 each time the source cell cancels the handover and sends a HANDOVER
CANCEL message if the source eNodeB does not receive any messages from the target side
before the preparation phase ends. However, if the handover preparation phase ends and the
handover of the UE is not finished for other abnormal reasons, the
L.HHO.Prep.FailOut.HOCancel counter is not incremented when the source cell sends a
HANDOVER CANCEL message to the target cell.
As shown at point B in Figure 2-212 during an S1-based handover or as shown at point B in

Figure 2-213 during an X2-based handover, the L.HHO.FailOut.HOCancel counter is
incremented by 1 each time the source cell sends a HANDOVER CANCEL regardless of the
completion of the handover preparation.
Figure 2-206

Figure 2-207
Figure 2-208
Figure 2-209

Figure 2-210
Figure 2-211
Figure 2-212

Figure 2-213
Formula
None
Unit
None
Related Features
L.HHO.Prep.FailOut.MME Multi-mode: None

GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

L.HHO.Prep.FailOut.NoRe- Multi-mode: None

ply GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
L.HHO.Prep.FailOut.Pre- Multi-mode: None

pFailure GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
L.HHO.Prep.FailOut.HO- Multi-mode: None

Cancel GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

L.HHO.FailOut.HOCancel Multi-mode: None

GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.25.13 Number of Intra-RAT Redirections
Counters
Description
1526728325 L.RRCRedirection.I Number of intra- DBS3900 LTE/

ntraLTE RAT redirections BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of intra-RAT redirections initiated by the eNodeB. In an
redirection, the eNodeB sends an RRC Connection Release message containing the target
frequency and other information to a UE, releases the RRC connection to the source cell for the
UE, and then directs the UE to access the target cell to continue its services.
Measurement Points
As shown at point A in Figure 2-214, the L.RRCRedirection.IntraLTE counter is incremented
by 1 each time the eNodeB sends an RRC Connection Release message to the UE and the
handover target cell is an intra-RAT inter-frequency cell of the source cell.

Figure 2-214
Formula
None
Unit
None
Related Features
L.RRCRedirection.IntraLTE Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002023 Admission Control
LBFD-00201802 Coverage Based Inter-

frequency Handover
Distance Based Inter-
frequency Handover
2.2.25.14 Number of Intra-RAT Handover Initiation Failures Because the Adjacent

Cell is not on the NRT of the Source Cell

Counters
Description
1526728398 L.IntraFreqHO.NoN Number of intra- DBS3900 LTE/

RT frequency handover BTS3900 LTE/
initiation failures BTS3900A LTE/
because the adjacent BTS3900L LTE/
cell is not on the NRT BTS3900AL LTE,
of the source cell BTS3900
1526728399 L.InterFreqHO.NoN Number of inter- DBS3900 LTE/

RT frequency handover BTS3900 LTE/
initiation failures BTS3900A LTE/
because the target BTS3900L LTE/
cell is not configured BTS3900AL LTE,
as a neighboring cell BTS3900
for 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.
Measurement Points
As shown at point A in Figure 2-215, Figure 2-216, or Figure 2-217, the corresponding counter
is incremented by 1 each time the eNodeB receives the first measurement report from a UE in
the source cell and decides to perform a handover, but the handover initiation fails because that
the adjacent cell has the best signal quality in the first measurement report is not on the NRT of
the source cell.
and Figure 2-217 shows an S1-based handover. The counters are measured as follows:
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.

Figure 2-215
Figure 2-216

Figure 2-217
Formula
None
Unit
None
Related Features
L.IntraFreqHO.NoNRT Multi-mode: None

GSM: None
UMTS: None
frequency Handover
L.InterFreqHO.NoNRT Multi-mode: None

GSM: None
UMTS: None
frequency Handover

2.2.25.15 Number of Inter-Frequency Handover Preparation Attempts Triggered

Counters
Description
1526728526 L.HHO.InterFreq.Lo Number of inter- DBS3900 LTE/

ad.PrepAttOut frequency handover BTS3900 LTE/
BTS3900
Description
The counter measures the number of inter-frequency handover preparation attempts triggered
Measurement Points
As shown at point A in Figure 2-218, Figure 2-219 or Figure 2-220, the
L.HHO.InterFreq.Load.PrepAttOut counter is incremented by 1 each time the eNodeB decides
to perform an inter-frequency blind handover because of high load or the eNodeB receives a
measurement report from the UE because of high load and decides to perform an inter-frequency
handover. Figure 2-218 shows an intra-eNodeB inter-frequency handover, Figure 2-219 shows
an X2-based inter-frequency handover and Figure 2-220 shows an S1-based inter-frequency
handover.
Figure 2-218

Figure 2-219
Figure 2-220
Formula
None
Unit
None

Related Features
L.HHO.InterFreq.Load.Pre- Multi-mode: None

pAttOut GSM: None
UMTS: None
LTE: LOFD-001032 Intra-LTE Load Balancing
TDLOFD-001032 Intra-LTE Load Balancing
2.2.25.16 Number of Inter-Frequency Handover Execution Attempts Triggered

Counters
Description
1526728527 L.HHO.InterFreq.Lo Number of inter- DBS3900 LTE/

ad.ExecAttOut frequency handover BTS3900 LTE/
BTS3900
Description
The counter measures the number of inter-frequency handover execution attempts triggered
Measurement Points
As shown at point B in Figure 2-221, Figure 2-222 or Figure 2-223, the
L.HHO.InterFreq.Load.ExecAttOut counter is incremented by 1 each time the eNodeB decides
to perform an inter-frequency handover because of high load and sends an RRC Connection
Reconfiguration message to the UE. Figure 2-221 shows an intra-eNodeB inter-frequency
handover, Figure 2-222 shows an X2-based inter-frequency handover and Figure 2-223 shows
an S1-based inter-frequency handover.

Figure 2-221
Figure 2-222

Figure 2-223
Formula
None
Unit
None
Related Features
L.HHO.InterFreq.Load.Exe- Multi-mode: None

cAttOut GSM: None
UMTS: None
2.2.25.17 Number of Successful Inter-Frequency Handover Executions Triggered


Counters
Description
1526728528 L.HHO.InterFreq.Lo Number of DBS3900 LTE/

frequency handover BTS3900A LTE/
executions triggered BTS3900L LTE/
because of high load BTS3900AL LTE,
BTS3900
Description
The counter measures the number of successful inter-frequency handover executions triggered
Measurement Points
As shown at point C in Figure 2-224, the L.HHO.InterFreq.Load.ExecSuccOut counter is
incremented by 1 each time the eNodeB decides to perform an intra-eNodeB handover because
of high load and target cell receives an RRC Connection Reconfiguration Complete message
from the UE.
of high load and the target cell receives an RRC Connection Reestablishment Complete message
from the UE.
of high load and the source cell receives an RRC Connection Reestablishment Complete message
from the UE.
incremented by 1 each time the eNodeB decides to perform an X2-based blind handover because
of high load and the source eNodeB receives a UE CONTEXT RELEASE message from the
target eNodeB.
L.HHO.InterFreq.Load.ExecSuccOut counter is incremented by 1 each time the eNodeB decides
to perform an X2-based blind handover because of high load and the source eNodeB receives a
UE CONTEXT RELEASE message from the target eNodeB after an RRC connection is
successfully reestablished to the target eNodeB for the UE.
to perform an X2-based blind handover because of high load and after an RRC connection is
successfully reestablished to the source eNodeB for the UE.
incremented by 1 each time the eNodeB decides to perform an s1-based blind handover because
of high load and the source eNodeB receives a UE CONTEXT RELEASE message from MME.


to perform an S1-based blind handover because of high load 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.

to perform an S1-based blind handover because of high load and after an RRC connection is
successfully reestablished to the source eNodeB for the UE.
Figure 2-224
Figure 2-225

Figure 2-226
Figure 2-227

Figure 2-228
Figure 2-229

Figure 2-230

Figure 2-231
Formula
None
Unit
None
Related Features
L.HHO.InterFreq.Load.Exe- Multi-mode: None

cSuccOut GSM: None
UMTS: None

2.2.25.18 Number of Inter-Frequency Outgoing Handover Attempts Triggered for

UEs to Go back to the HPLMN
Counters
Description
1526728539 L.HHO.InterFreq.Re Number of inter- DBS3900 LTE/

gainHPLMN.Pre- frequency outgoing BTS3900 LTE/
pAttOut handover attempts BTS3900A LTE/
triggered for UEs to BTS3900L LTE/
go back to the BTS3900AL LTE,
HPLMN BTS3900
Description
The counter measures the number of inter-frequency outgoing handover attempts triggered for
UEs to go back to the HPLMN in a cell. In national roaming scenarios, if the handovers back to
the HPLMN for UEs is enabled, a roaming UE can be handed over to the HPLMN when this
UE moves back to the HPLMN.
Measurement Points
As shown at point A in Figure 2-232, during an X2-based handover the
L.HHO.InterFreq.RegainHPLMN.PrepAttOut counter is incremented by 1 each time the source
eNodeB determines to perform an X2-based handover after the source eNodeB receives a
measurement report from the UE. The corresponding measurement control message is triggered
for the UE to go back to the HPLMN.
As shown at point A in Figure 2-233, 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.

Figure 2-232
Figure 2-233
Formula
None
Unit
None

Related Features
L.HHO.InterFreq.RegainHP Multi-mode: None

LMN.PrepAttOut GSM: None
UMTS: None
SPID
2.2.25.19 Number of Inter-Frequency Outgoing Handover Executions Triggered for

UEs to Go back to the HPLMN
Counters
Description
1526728540 L.HHO.InterFreq.Re Number of inter- DBS3900 LTE/

gainHPLMN.Exe- frequency outgoing BTS3900 LTE/
cAttOut handover executions BTS3900A LTE/
triggered for UEs to BTS3900L LTE/
go back to the BTS3900AL LTE,
HPLMN BTS3900
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
Measurement Points
As shown at point B in Figure 2-234, during an X2-based handover the
L.HHO.InterFreq.RegainHPLMN.ExecAttOut counter is incremented by 1 each time the source
eNodeB sends an RRC Connection Reconfiguration message to the UE after the source eNodeB
receives a HANDOVER REQUEST ACKNOWLEDGE message from the target eNodeB.
As shown at point B in Figure 2-235, 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.

Figure 2-234
Figure 2-235
Formula
None
Unit
None

Related Features

LMN.ExecAttOut GSM: None
UMTS: None
SPID
2.2.25.20 Number of Successful Inter-Frequency Outgoing Handovers Triggered

for UEs to Go Back to the HPLMN
Counters
Description
1526728541 L.HHO.InterFreq.Re Number of DBS3900 LTE/

gainHPLMN.Exe- successful inter- BTS3900 LTE/
cSuccOut frequency outgoing BTS3900A LTE/
handovers triggered BTS3900L LTE/
for UEs to go back to BTS3900AL LTE,
the HPLMN BTS3900
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
Measurement Points
As shown at point C in Figure 2-236, during an X2-based handover the
L.HHO.InterFreq.RegainHPLMN.ExecSuccOut counter is incremented by 1 each time data in
the buffer is forwarded during the handover after the source eNodeB receives a UE CONTEXT
RELEASE message from the target eNodeB.
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.

RELEASE COMMAND message from the MME.
successfully reestablished to the target eNodeB for the UE, the
successfully reestablished to the source eNodeB for the UE, the
L.HHO.InterFreq.RegainHPLMN.ExecSuccOut counter is incremented by 1 each time.
Figure 2-236

Figure 2-237
Figure 2-238

Figure 2-239

Figure 2-240

Figure 2-241
Formula
None
Unit
None
Related Features

LMN.ExecSuccOut GSM: None
UMTS: None
SPID

2.2.25.21 Number of Intra-Frequency Handover Execution Attempts Triggered for

UEs that do not transmit or receive data
Counters
Description
1526728554 L.HHO.IntraFreq.N Number of intra- DBS3900 LTE/

oData.ExecAttOut frequency handover BTS3900 LTE/
triggered for UEs BTS3900L LTE/
that do not transmit BTS3900AL LTE,
or receive data BTS3900
Description
The counter measures the number of intra-frequency handover execution attempts triggered for
UEs that do not transmit or receive data.
Measurement Points
This counter is measured in a handover where the source cell and the target cell work on the
same frequency.
As shown at point B in Figure 2-242, during an intra-eNodeB handover that the UE does not
transmit or receive data, the L.HHO.IntraFreq.NoData.ExecAttOut counter is incremented by 1
each time the source eNodeB sends an RRC Connection Reconfiguration message to the UE.
As shown at point B in Figure 2-243, during an X2-based handover that the UE does not transmit
or receive data, the L.HHO.IntraFreq.NoData.ExecAttOut counter is incremented by 1 each time
the source eNodeB sends an RRC Connection Reconfiguration message to the UE after the
source eNodeB receives a HANDOVER REQUEST ACKNOWLEDGE message from the
target eNodeB.

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.

Figure 2-242
Figure 2-243

Figure 2-244
Formula
None
Unit
None
Related Features
L.HHO.IntraFreq.NoData.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
LOFD-001105 Coverage Based Intra-

frequency Handover
TDLOFD-001105
Dynamic DRX
Dynamic DRX
2.2.25.22 Number of Successful Intra-Frequency Handover Executions Triggered

for UEs that do not transmit or receive data

Counters
Description
1526728555 L.HHO.IntraFreq.N Number of DBS3900 LTE/

oData.ExecSuccOut successful intra- BTS3900 LTE/
for UEs that do not BTS3900AL LTE,
transmit or receive BTS3900
data
Description
The counter measures the number of successful intra-frequency handover executions triggered
for UEs that do not transmit or receive data.
Measurement Points
same frequency.
As shown at point C in Figure 2-245, during an intra-eNodeB handover that the UE does not
transmit or receive data, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented by
1 each time the target cell receives an RRC Connection Reconfiguration Complete message from
the UE.
1 each time the target cell receives an RRC Connection Reestablishment Complete message
from the UE.
1 each time the source cell receives an RRC Connection Reestablishment Complete message
from the UE.
As shown at point C in Figure 2-247, during an X2-based handoverthat the UE does not transmit
or receive data, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented by 1 each
time the source eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB.
As shown at point C in Figure 2-248, during an X2-based inter-eNodeB handover that the UE
does not transmit or receive data, after an RRC connection is successfully reestablished to the
target eNodeB for the UE, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented
by 1 each time the source eNodeB receives a UE CONTEXT RELEASE message from the target
eNodeB.
As shown at point C in Figure 2-251, during an X2-based inter-eNodeB handover that the UE
does not transmit or receive data, after an RRC connection is successfully reestablished to the
source eNodeB for the UE, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented
by 1 each time.

As shown at point C in Figure 2-249, during an S1-based handover that the UE does not transmit
or receive data, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented by 1 each
time the source eNodeB receives a UE CONTEXT RELEASE COMMAND from the MME.
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.
or receive data, after an RRC connection is successfully reestablished to the source eNodeB for
the UE, the L.HHO.IntraFreq.NoData.ExecSuccOut counter is incremented by 1 each time.
Figure 2-245
Figure 2-246

Figure 2-247
Figure 2-248

Figure 2-249
Figure 2-250

Figure 2-251

Figure 2-252
Formula
None
Unit
None

Related Features
L.HHO.IntraFreq.NoData.E Multi-mode: None

UMTS: None
LOFD-001105 Coverage Based Intra-

frequency Handover
TDLOFD-001105
Dynamic DRX
Dynamic DRX
2.2.25.23 Number of Inter-Frequency Handover Execution Attempts Triggered for

UEs That Do not Transmit or Receive Data
Counters
Description
1526728557 L.HHO.InterFreq.N Number of inter- DBS3900 LTE/

oData.ExecAttOut frequency handover BTS3900 LTE/
triggered for UEs BTS3900L LTE/
that do not transmit BTS3900AL LTE,
or receive data BTS3900
Description
The counter measures the number of inter-frequency handover execution attempts triggered for
UEs that do not transmit or receive data.
Measurement Points
different frequency.
As shown at point B in Figure 2-253, during an intra-eNodeB handover that the UE does not
transmit or receive data, the L.HHO.InterFreq.NoData.ExecAttOut counter is incremented by 1
each time the source eNodeB sends an RRC Connection Reconfiguration message to the UE.
As shown at point B in Figure 2-254, during an X2-based handover that the UE does not transmit
or receive data, the L.HHO.InterFreq.NoData.ExecAttOut counter is incremented by 1 each time
the source eNodeB sends an RRC Connection Reconfiguration message to the UE after the

source eNodeB receives a HANDOVER REQUEST ACKNOWLEDGE message from the

target eNodeB.

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.
Figure 2-253
Figure 2-254

Figure 2-255
Formula
None
Unit
None
Related Features
L.HHO.InterFreq.NoData.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
LOFD-001105 Coverage Based Inter-

frequency Handover
TDLOFD-001105
Dynamic DRX
Dynamic DRX
2.2.25.24 Number of Successful Inter-Frequency Handover Executions Triggered

for UEs That Do not Transmit or Receive Data

Counters
Description
1526728558 L.HHO.InterFreq.N Number of DBS3900 LTE/

oData.ExecSuccOut successful inter- BTS3900 LTE/
for UEs that do not BTS3900AL LTE,
transmit or receive BTS3900
data
Description
The counter measures the number of successful inter-frequency handover executions triggered
for UEs that do not transmit or receive data.
Measurement Points
This counter is measured in a handover where the source cell and the target cell work on different
frequencies.
transmit or receive data, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented by
1 each time the target cell receives an RRC Connection Reconfiguration Complete message from
the UE.
1 each time the target cell receives an RRC Connection Reestablishment Complete message
from the UE.
1 each time the source cell receives an RRC Connection Reestablishment Complete message
from the UE.
As shown at point C in Figure 2-258, during an X2-based handover that the UE does not transmit
or receive data, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented by 1 each
time the source eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB.
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.
or receive data, after an RRC connection is successfully reestablished to the source eNodeB for
the UE, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented by 1 each time.

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.
or receive data, after an RRC connection is successfully reestablished to target eNodeB for the
UE, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented by 1 each time the
source eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME.
or receive data, after an RRC connection is successfully reestablished to source eNodeB for the
UE, the L.HHO.InterFreq.NoData.ExecSuccOut counter is incremented by 1 each time.
Figure 2-256
Figure 2-257

Figure 2-258
Figure 2-259

Figure 2-260
Figure 2-261

Figure 2-262

Figure 2-263
Formula
None
Unit
None

Related Features
L.HHO.InterFreq.NoData.E Multi-mode: None

UMTS: None
LOFD-001105 Coverage Based Inter-

frequency Handover
TDLOFD-001105
Dynamic DRX
Dynamic DRX
the MME During S1-based Outgoing Handover Executions
Counters
Description
1526728883 L.HHO.S1.IntraFreq Number of responses DBS3900 LTE/

.MMEAbnormRsp for abnormal causes BTS3900 LTE/
MME during S1- BTS3900AL LTE,
based outgoing intra- BTS3900
frequency handover
executions in a cell
1526728884 L.HHO.S1.InterFreq Number of responses DBS3900 LTE/

.MMEAbnormRsp for abnormal causes BTS3900 LTE/
MME during S1- BTS3900AL LTE,
based outgoing inter- BTS3900
frequency handover
Description
from the MME during S1-based outgoing handover executions.

Measurement Points
is incremented by 1 each time the source eNodeB receives a UE CONTEXT RELEASE
COMMAND message from the MME and the release cause is not "Successful Handover" or
"Normal Release". The counters are measured as follows:
L.HHO.S1.IntraFreq.MMEAbnormRsp counter is incremented by 1.
L.HHO.S1.InterFreq.MMEAbnormRsp counter is incremented by 1.
Figure 2-264
Formula
None
Unit
None

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
2.2.25.26 Number of Successful Intra-eNodeB Outgoing Handovers Where RRC

Connections Are Reestablished to the Source Cell for UEs in a Cell
Counters
Description

raFreq.Succ.ReEst2 successful intra- BTS3900 LTE/
Src eNodeB intra- BTS3900A LTE/
handovers where BTS3900AL LTE,
RRC connections are BTS3900
reestablished to the
source cell for UEs in
a cell

erFreq.Succ.ReEst2 successful intra- BTS3900 LTE/
Src eNodeB inter- BTS3900A LTE/
a cell

Description
The counters measure the number of successful intra-eNodeB outgoing handovers where RRC
connections are reestablished to the source cell for UEs in a cell.
Measurement Points
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.IntraeNB.IntraFreq.Succ.ReEst2Src counter is incremented by 1.
L.HHO.IntraeNB.InterFreq.Succ.ReEst2Src counter is incremented by 1.
Figure 2-265
Formula
None
Unit
None

Related Features

Succ.ReEst2Src GSM: None
UMTS: None
frequency Handover

UMTS: None
frequency Handover
2.2.25.27 Number of Successful Inter-eNodeB Outgoing Handovers Where RRC

Counters
Description

raFreq.Succ.ReEst2 successful inter- BTS3900 LTE/
Src eNodeB intra- BTS3900A LTE/
a cell

erFreq.Succ.ReEst2 successful inter- BTS3900 LTE/
Src eNodeB inter- BTS3900A LTE/
a cell

Description
The counters measure the number of successful inter-eNodeB outgoing handovers where RRC
Measurement Points
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.IntraFreq.Succ.ReEst2Src counter is incremented by 1.
L.HHO.IntereNB.InterFreq.Succ.ReEst2Src counter is incremented by 1.

Figure 2-266

Figure 2-267
Formula
None
Unit
None
Related Features

UMTS: None
frequency Handover


UMTS: None
frequency Handover
2.2.25.28 Number of successful blind outgoing handovers where RRC connections

are reestablished to the source cell for UEs in a cell
Counters
Description
1526728922 L.HHO.BlindHO.Su Number of DBS3900 LTE/

cc.ReEst2Src successful blind BTS3900 LTE/
outgoing handovers BTS3900A LTE/
where RRC BTS3900L LTE/
connections are BTS3900AL LTE,
reestablished to the BTS3900
a cell
Description
The counter measures the number of successful blind outgoing handovers where RRC
connections are reestablished to the source cell for UEs in a cell. Not triggered on the basis of
UE measurement reports, the blind handover is a handover in which the eNodeB specifies the
target cell for the UE. In specific networking scenarios, the eNodeB performs a blind handover
to actively hand over the UE from the target cell.
Measurement Points
As shown at point C in Figure 2-268, during an intra-eNodeB blind handover the
L.HHO.BlindHO.Succ.ReEst2Src counter is incremented by 1 each time the source cell receives
an RRC Connection Reestablishment Complete message from the UE.


As shown at point C in Figure 2-270, during an S1-based blind handover the

Figure 2-268

Figure 2-269

Figure 2-270
Formula
None
Unit
None

Related Features
L.HHO.BlindHO.Succ.ReEs Multi-mode: None

t2Src GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.26 Measurement related to Intra eRan HOIN

(HO.eRAN.In.Cell)
Overview
The HO.eRAN.In.Cell function subset measures the performance of intra-frequency and inter-
frequency of intra E-UTRAN incoming handovers in a cell, as shown in Figure 2-271, Figure
2-272, and Figure 2-273.
Figure 2-271

Figure 2-272
Figure 2-273
Counters
Description
1526727253 L.HHO.IntraeNB.P Number of intra- V100R008C00,and

repAttIn eNodeB incoming the mapping single-
handover attempts in mode base station
a cell version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526727254 L.HHO.IntraeNB. Number of intra- V100R008C00,and

ExecAttIn eNodeB incoming the mapping single-
executions in a cell version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727255 L.HHO.IntraeNB. Number of V100R008C00,and

ExecSuccIn successful intra- the mapping single-
eNodeB incoming mode base station
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727256 L.HHO.IntereNB.P Number of inter- V100R008C00,and

repAttIn eNodeB incoming the mapping single-
handover attempts in mode base station
a cell version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727257 L.HHO.IntereNB.E Number of inter- V100R008C00,and

xecAttIn eNodeB incoming the mapping single-
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727258 L.HHO.IntereNB.E Number of V100R008C00,and

eNodeB incoming mode base station
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526728289 L.HHO.Prep.FailIn Number of incoming V100R008C00,and

.AdmitFail handover preparation the mapping single-
admission rejection version that
introduce this
counter is:
eNodeB:V100R003
C00

.HOCancel handover preparation the mapping single-
failures because the mode base station
target cell receives version that
handover introduce this
cancellation counter is:
messages eNodeB:V100R003
C00
1526728353 L.HHO.IntereNB.P Number of path V100R008C00,and

athSwAtt switch requests for the mapping single-
inter-eNodeB mode base station
incoming handovers version that
in a cell introduce this
counter is:
eNodeB:V100R005
C01
1526728354 L.HHO.IntereNB.P Number of V100R008C00,and

athSwSucc successful path the mapping single-
switches for inter- mode base station
eNodeB incoming version that
counter is:
eNodeB:V100R005
C01
1526728491 L.HHO.PrepAttIn. Number of times the V100R008C00,and

disc.FlowCtrl HANDOVER the mapping single-
REQUEST message mode base station
is discarded over the version that
S1 or X2 interface introduce this
because of flow counter is:
control eNodeB:V100R006
C00


Description
1526728492 L.HHO.Prep.FailIn Number of times that V100R008C00,and

.FlowCtrl the target eNodeB the mapping single-
sends a handover mode base station
preparation failure version that
message over the S1 introduce this
or X2 interface to the counter is:
source eNodeB eNodeB:V100R003
because of flow C00
control

.AdmitFail.Load handover preparation the mapping single-
high load version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728865 L.HHO.Prep.FailIn Number of eNodeB V100R008C00,and

incoming handover the mapping single-
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728909 L.HHO.S1.Cancel. Number of UE V100R008C00,and

ExecIn CONTEXT the mapping single-
RELEASE mode base station
COMMAND version that
messages with the introduce this
cause value of counter is:
"Handover eNodeB:V100R006
Cancellation" C00
received by the target
eNodeB from the
MME during S1-
based incoming
handover executions
in a cell


Description
1526728910 L.HHO.X2.Cancel. Number of V100R008C00,and

ExecIn HANDOVER the mapping single-
CANCEL messages mode base station
received by the target version that
cell from the source introduce this
cell during X2-based counter is:
incoming handover eNodeB:V100R006
Counter Sub Counter
L.HHO.Prep.FailIn.AdmitFail L.HHO.Prep.FailIn.AdmitFail.Load
2.2.26.1 Number of Intra-eNodeB Incoming Handover Attempts in a Cell
Counters
Description
1526727253 L.HHO.IntraeNB.Pr Number of intra- DBS3900 LTE/

epAttIn eNodeB incoming BTS3900 LTE/
handover attempts in BTS3900A LTE/
a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of intra-eNodeB incoming handover attempts in a cell. In an
intra-eNodeB handover, the source cell and target cell are controlled by the same eNodeB.
Measurement Points
As shown at point A in Figure 2-274, the L.HHO.IntraeNB.PrepAttIn counter is incremented
by 1 in the target cell each time the eNodeB decides to perform an intra-eNodeB incoming
handover after receiving a measurement report from the UE.

Figure 2-274
Formula
None
Unit
None
Related Features
L.HHO.IntraeNB.PrepAttIn Multi-mode: None

GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.26.2 Number of Intra-eNodeB Incoming Handovers Executions in a Cell

Counters
Description
1526727254 L.HHO.IntraeNB.Ex Number of intra- DBS3900 LTE/

ecAttIn eNodeB incoming BTS3900 LTE/
executions in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of intra-eNodeB incoming handover executions in a cell. In
an intra-eNodeB handover, the source cell and target cell are controlled by the same eNodeB.
Measurement Points
As shown at point B in Figure 2-275, the L.HHO.IntraeNB.ExecAttIn counter is incremented
by 1 in the target cell each time the eNodeB sends an RRC Connection Reconfiguration message
to the UE.
Figure 2-275
Formula
None
Unit
None

Related Features
L.HHO.IntraeNB.ExecAttIn Multi-mode: None

GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.26.3 Number of Successful Intra-eNodeB Incoming Handovers in a Cell
Counters
Description
1526727255 L.HHO.IntraeNB.Ex Number of DBS3900 LTE/

ecSuccIn successful intra- BTS3900 LTE/
eNodeB incoming BTS3900A LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of successful intra-eNodeB incoming handovers in a cell. In
an intra-eNodeB handover, the source cell and target cell are controlled by the same eNodeB.
Measurement Points
As shown at point C in Figure 2-276, the L.HHO.IntraeNB.ExecSuccIn counter is incremented
by 1 in the target cell each time the eNodeB receives an RRC Connection Reconfiguration
Complete message from the UE and the subsequent processing is successful.
As shown at point C in Figure 2-277, the L.HHO.IntraeNB.ExecSuccIn counter is incremented

by 1 in the target cell each time the eNodeB receives an RRC Connection Reestablishment
Complete message from the UE and the subsequent processing is successful.

Figure 2-276
Figure 2-277
Formula
None
Unit
None

Related Features
L.HHO.IntraeNB.ExecSuc- Multi-mode: None

cIn GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.26.4 Number of Inter-eNodeB Incoming Handover Attempts in a Cell
Counters
Description
1526727256 L.HHO.IntereNB.Pr Number of inter- DBS3900 LTE/

epAttIn eNodeB incoming BTS3900 LTE/
handover attempts in BTS3900A LTE/
a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of inter-eNodeB incoming handover attempts in a cell. In an
inter-eNodeB handover, the source cell and target cell are controlled by different eNodeBs. Such
a handover is performed between different eNodeBs over the S1 or X2 interface.
Measurement Points
Figure 2-278 shows an X2-based handover, and Figure 2-279 shows an S1-based handover. As
shown at point A in Figure 2-278, the L.HHO.IntereNB.PrepAttIn counter is incremented by 1
in the target cell each time the target eNodeB receives a HANDOVER REQUEST message from
the source eNodeB over the X2 interface.
As shown at point A in Figure 2-279, the L.HHO.IntereNB.PrepAttIn counter is incremented

by 1 in the target cell each time the target eNodeB receives a HANDOVER REQUEST message
from the MME over the S1 interface.

Figure 2-278
Figure 2-279
Formula
None
Unit
None

Related Features
L.HHO.IntereNB.PrepAttIn Multi-mode: None

GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.26.5 Number of Inter-eNodeB Incoming Handovers Executions in a Cell
Counters
Description
1526727257 L.HHO.IntereNB.Ex Number of inter- DBS3900 LTE/

ecAttIn eNodeB incoming BTS3900 LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of inter-eNodeB incoming handover executions in a cell. In
an inter-eNodeB handover, the source cell and target cell are controlled by different eNodeBs.
Such a handover is performed between different eNodeBs over the S1 or X2 interface.
Measurement Points
Figure 2-280 shows an X2-based handover, and Figure 2-281 shows an S1-based handover. As
shown at point B in Figure 2-280 or Figure 2-281, the L.HHO.IntereNB.ExecAttIn counter is
incremented by 1 in the target cell each time the target eNodeB sends a HANDOVER REQUEST
ACKNOWLEDGE message to the source eNodeB over the X2 interface>
As shown at point B in Figure 2-281, the L.HHO.IntereNB.ExecAttIn counter is incremented

by 1 in the target cell each time the target eNodeB sends a HANDOVER REQUEST
ACKNOWLEDGE message to the MME over the S1 interface.

Figure 2-280
Figure 2-281
Formula
None
Unit
None

Related Features
L.HHO.IntereNB.ExecAttIn Multi-mode: None

GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.26.6 Number of Successful Inter-eNodeB Incoming Handovers in a Cell
Counters
Description
1526727258 L.HHO.IntereNB.Ex Number of DBS3900 LTE/

eNodeB incoming BTS3900A LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of successful inter-eNodeB incoming handovers in a cell. In
an inter-eNodeB handover, the source cell and target cell are controlled by different eNodeBs.
Such a handover is performed between different eNodeBs over the S1 or X2 interface.
Measurement Points
L.HHO.IntereNB.ExecSuccIn counter is incremented by 1 in the target cell each time the target
eNodeB sends a UE CONTEXT RELEASE message to the source eNodeB over the X2 interface
after the target eNodeB receives a PATH SWITCH REQUEST ACKNOWLEDGE message
from the MME.
As shown at point E in Figure 2-283, during an X2-based handover after an RRC connection is
successfully reestablished to the target eNodeB for the UE, the L.HHO.IntereNB.ExecSuccIn

counter is incremented by 1 in the target cell each time the target eNodeB receives a PATH
SWITCH REQUEST ACKNOWLEDGE message from the MME and sends a UE CONTEXT
RELEASE message to the source eNodeB over the X2 interface.
As shown at in point C in Figure 2-284, during an S1-based handover the

L.HHO.IntereNB.ExecSuccIn counter is incremented by 1 in the target cell each time the target
eNodeB sends a HANDOVER NOTIFY message to the MME.
As shown at in point C in Figure 2-285, during an S1-based handover after an RRC connection
is successfully reestablished to the target eNodeB for the UE, the L.HHO.IntereNB.ExecSuccIn
counter is incremented by 1 in the target cell each time the target eNodeB sends a HANDOVER
NOTIFY message to the MME.
Figure 2-282

Figure 2-283
Figure 2-284

Figure 2-285
Formula
None
Unit
None
Related Features
L.HHO.IntereNB.ExecSuc- Multi-mode: None

cIn GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

2.2.26.7 Number of Incoming Handover Failures for Different Causes in a Cell
Counters
Description
1526728289 L.HHO.Prep.FailIn. Number of incoming DBS3900 LTE/

AdmitFail handover preparation BTS3900 LTE/
admission rejection BTS3900L LTE/
BTS3900AL LTE,
BTS3900

HOCancel handover preparation BTS3900 LTE/
failures because the BTS3900A LTE/
target cell receives BTS3900L LTE/
handover BTS3900AL LTE,
cancellation BTS3900
messages
1526728491 L.HHO.PrepAttIn.di Number of times the DBS3900 LTE/

sc.FlowCtrl HANDOVER BTS3900 LTE/
REQUEST message BTS3900A LTE/
is discarded over the BTS3900L LTE/
S1 or X2 interface BTS3900AL LTE,
because of flow BTS3900
control
1526728492 L.HHO.Prep.FailIn. Number of times that DBS3900 LTE/

FlowCtrl the target eNodeB BTS3900 LTE/
sends a handover BTS3900A LTE/
preparation failure BTS3900L LTE/
message over the S1 BTS3900AL LTE,
or X2 interface to the BTS3900
source eNodeB
because of flow
control
1526728865 L.HHO.Prep.FailIn Number of eNodeB DBS3900 LTE/

incoming handover BTS3900 LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of incoming handover failures for different causes in a cell.
Outgoing handover failures usually occur during handover preparation and are caused by faults

on the MME side, no responses from the target cell, handover preparation failures at the target
cell, or handover cancellation messages sent by the source cell. Handover preparation is the
procedure to prepare handover resources between the handover decision and the handover
execution.
Measurement Points
As shown at point B in Figure 2-286, during an S1-based handover preparation phase the
L.HHO.Prep.FailIn.AdmitFail counter is incremented by 1 in the target cell each time the target
eNodeB receives a HANDOVER REQUEST message over the S1 interface and sends a
HANDOVER FAILURE message to the MME over the S1 interface because of admission
rejection in the target cell.
L.HHO.Prep.FailIn.AdmitFail counter in incremented by 1 in the target cell each time the target
eNodeB receives a HANDOVER REQUEST message over the X2 interface and sends a
HANDOVER PREPARATION FAILURE message to the target eNodeB over the X2 interface
because of admission rejection in the target cell.

L.HHO.Prep.FailIn.HOCancel counter is incremented by 1 in the target cell each time the target
eNodeB receives a UE CONTEXT RELEASE COMMAND message with the release cause of
"Handover Cancelled" from the MME.

L.HHO.Prep.FailIn.HOCancel counter is incremented by 1 in the target cell each time the target
eNodeB receives a HANDOVER CANCEL message from the source eNodeB.
As shown at point A in Figure 2-290, the L.HHO.PrepAttIn.disc.FlowCtrl counter is

incremented by 1 in the target cell each time the target eNodeB discards an HANDOVER
REQUEST message received from the MME over the S1 interface because of flow control (In
this case, the target eNodeB does not send a handover preparation failure message to the source
eNodeB.)
As shown at point A in Figure 2-291, the L.HHO.PrepAttIn.disc.FlowCtrl counter is

incremented by 1 in the target cell each time the target eNodeB discards an HANDOVER
REQUEST message received from the source eNodeB over the X2 interface because of flow
control (In this case, the target eNodeB does not send a handover preparation failure message
to the source eNodeB.)
L.HHO.Prep.FailIn.FlowCtrl counter is incremented by 1 in the target cell each time the target
eNodeB receives a HANDOVER REQUEST message over the S1 interface and sends a
HANDOVER FAILURE message to the MME over the S1 interface if the incoming handover
fails because of flow control in the target cell.
L.HHO.Prep.FailIn.FlowCtrl counter in incremented by 1 in the target cell each time the target
eNodeB receives a HANDOVER REQUEST message over the X2 interface and sends a
if the incoming handover fails because of flow control in the target cell.
As shown at point B in Figure 2-286, during an S1-based handover preparation phase, the
L.HHO.Prep.FailIn counter is incremented by 1 in the target cell each time the target eNodeB

receives a HANDOVER REQUEST message over the S1 interface and the target cell sends a
HANDOVER PREPARATION FAILURE message to the source MME.
As shown at point in B in Figure 2-286, during an X2-based handover preparation phase, the
L.HHO.Prep.FailIn counter is incremented by 1 in the target cell each time the target eNodeB
receives a HANDOVER REQUEST message over the X2 interface and the target cell sends a
HANDOVER PREPARATION FAILURE message to the source eNodeB.
The L.HHO.Prep.FailIn counter involves the measurement of the L.HHO.Prep.FailIn.AdmitFail

and L.HHO.Prep.FailIn.FlowCtrll counters.
Figure 2-286
Figure 2-287

Figure 2-288
Figure 2-289
Figure 2-290

Figure 2-291
Formula
None
Unit
None
Related Features
L.HHO.Prep.FailIn.Admit- Multi-mode: None

Fail GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
L.HHO.Prep.FailIn.HOCan- Multi-mode: None

cel GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover

L.HHO.PrepAttIn.disc.Flow Multi-mode: None

Ctrl GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
L.HHO.Prep.FailIn.FlowCtr Multi-mode: None

l GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
L.HHO.Prep.FailIn Multi-mode: None

GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.26.8 Number of Path Switch Requests for Inter-eNodeB Incoming Handovers

in a Cell

Counters
Description
1526728353 L.HHO.IntereNB.Pa Number of path DBS3900 LTE/

thSwAtt switch requests for BTS3900 LTE/
inter-eNodeB BTS3900A LTE/
incoming handovers BTS3900L LTE/
in a cell BTS3900AL LTE,
BTS3900
Description
The counter measures the number of path switch requests for X2-based incoming handovers in
a cell. In an X2-based handover, the source and target cells are controlled by different eNodeBs.
Such a handover is performed between different eNodeBs over the X2 interface.
Measurement Points
As shown at point D in Figure 2-292, during an X2-based handover the
L.HHO.IntereNB.PathSwAtt counter is incremented by 1 in the target cell each time the target
eNodeB sends a PATH SWITCH REQUEST message to the MME over the S1 interface.
Figure 2-292
Formula
None

Unit
None
Related Features
L.HHO.IntereNB.PathS- Multi-mode: None

wAtt GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.26.9 Number of Successful Path Switches for inter-eNodeB Incoming

Handovers in a Cell
Counters
Description
1526728354 L.HHO.IntereNB.Pa Number of DBS3900 LTE/

thSwSucc successful path BTS3900 LTE/
switches for inter- BTS3900A LTE/
eNodeB incoming BTS3900L LTE/
BTS3900
Description
The counter measures the number of successful path switches for X2-based incoming handovers
in a cell. In an X2-based handover, the source and target cells are controlled by different
eNodeBs. Such a handover is performed between different eNodeBs over the X2 interface.
Measurement Points
As shown at point E in Figure 2-293, during an X2-based handover the
L.HHO.IntereNB.PathSwSucc counter is incremented by 1 in the target cell each time the target
eNodeB receives a PATH SWITCH REQUEST ACKNOWLEDGE message from the MME.

Figure 2-293
Formula
None
Unit
None
Related Features
L.HHO.IntereNB.PathSw- Multi-mode: None

Succ GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.26.10 Number of Incoming Handover Failures Because of High Load in a Cell

Counters
Description

AdmitFail.Load handover preparation BTS3900 LTE/
high load BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of incoming handover failures because of high load in a cell.
Measurement Points
L.HHO.Prep.FailIn.AdmitFail.Load counter is incremented by 1 in the target cell each time the
target eNodeB receives a HANDOVER REQUEST message over the S1 interface and sends a
HANDOVER FAILURE message to the MME over the S1 interface if the access is rejected
because of high load in the target cell.
L.HHO.Prep.FailIn.AdmitFail.Load counter is incremented by 1 in the target cell each time the
target eNodeB receives a HANDOVER REQUEST message over the X2 interface and sends a
if the access is rejected because of high load in the target cell.
Figure 2-294

Figure 2-295
Formula
None
Unit
None
Related Features
L.HHO.Prep.FailIn.AdmitFa Multi-mode: None

il.Load GSM: None
UMTS: None
LTE: LBFD-002018 Mobility Management
2.2.26.11 Number of HANDOVER CANCEL Messages Received by the Target Cell

from the Source Cell During Inter-eNodeB Incoming Handover Executions in a
Cell

Counters
Description
1526728909 L.HHO.S1.Cancel.E Number of UE DBS3900 LTE/

xecIn CONTEXT BTS3900 LTE/
RELEASE BTS3900A LTE/
COMMAND BTS3900L LTE/
messages with the BTS3900AL LTE,
cause value of BTS3900
"Handover
Cancellation"
received by the target
eNodeB from the
MME during S1-
based incoming
handover executions
in a cell
1526728910 L.HHO.X2.Cancel.E Number of DBS3900 LTE/

xecIn HANDOVER BTS3900 LTE/
CANCEL messages BTS3900A LTE/
received by the target BTS3900L LTE/
cell from the source BTS3900AL LTE,
cell during X2-based BTS3900
incoming handover
Description
The counters measure the number of times that the target cell receives a HANDOVER CANCEL
message from the source cell during inter-eNodeB handover executions in a cell.
Measurement Points
L.HHO.X2.Cancel.ExecIn counter is incremented by 1 each time the target cell sends a
HANDOVER REQUEST ACKNOWLEDGE message to the source cell and receives a
HANDOVER CANCEL message from the source cell.

L.HHO.S1.Cancel.ExecIn counter is incremented by 1 each time the target cell sends a
HANDOVER REQUEST ACKNOWLEDGE message to the MME and receives a UE
CONTEXT RELEASE COMMAND message from the MME with the release cause of
"Handover Cancellation."

Figure 2-296
Figure 2-297
Formula
None
Unit
None

Related Features
L.HHO.S1.Cancel.ExecIn Multi-mode: None

GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
L.HHO.X2.Cancel.ExecIn Multi-mode: None

GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.27 Measurement related to Intra eRan X2 HOOUT

(HO.eRAN.X2Out.Cell)
Overview
The HO.eRAN.X2Out.Cell function subset measures the performance of X2-based intra-
frequency and X2-based inter-frequency outgoing handovers over the X2 interface in a cell, as
shown in Figure 2-298.

Figure 2-298
Counters
Description
1526727264 L.HHO.X2.IntraFr Number of X2-based V100R008C00,and

eq.PrepAttOut intra-frequency the mapping single-
outgoing handover mode base station
attempts in a cell version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727265 L.HHO.X2.IntraFr Number of X2-based V100R008C00,and

eq.ExecAttOut intra-frequency the mapping single-
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00


Description
1526727266 L.HHO.X2.IntraFr Number of V100R008C00,and

eq.ExecSuccOut successful X2-based the mapping single-
intra-frequency mode base station
outgoing handovers version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727267 L.HHO.X2.InterFr Number of X2-based V100R008C00,and

eq.PrepAttOut inter-frequency the mapping single-
attempts in a cell version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727268 L.HHO.X2.InterFr Number of X2-based V100R008C00,and

eq.ExecAttOut inter-frequency the mapping single-
outgoing handovers mode base station
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526727269 L.HHO.X2.InterFr Number of V100R008C00,and

eq.ExecSuccOut successful X2-based the mapping single-
inter-frequency mode base station
counter is:
eNodeB:Version
earlier than
V100R003C00
1526728864 L.HHO.X2.FailOut Number of X2-based V100R008C00,and

.HOCancel outgoing handover the mapping single-
cancellation in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728906 L.HHO.X2.IntraFr Number of V100R008C00,and

eq.Succ.ReEst2Src successful X2-based the mapping single-
intra-frequency mode base station
where RRC introduce this
connections are counter is:
a cell
1526728907 L.HHO.X2.InterFr Number of V100R008C00,and

eq.Succ.ReEst2Src successful X2-based the mapping single-
inter-frequency mode base station
where RRC introduce this
connections are counter is:
a cell
Counter Sub Counter
L.HHO.X2.IntraFreq.ExecSuccOut L.HHO.X2.IntraFreq.Succ.ReEst2Src
L.HHO.X2.InterFreq.ExecSuccOut L.HHO.X2.InterFreq.Succ.ReEst2Src
2.2.27.1 Number of X2-based Outgoing Handover Attempts in a Cell
Counters
Description
1526727264 L.HHO.X2.IntraFre Number of X2-based DBS3900 LTE/

q.PrepAttOut intra-frequency BTS3900 LTE/
outgoing handover BTS3900A LTE/
attempts in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1526727267 L.HHO.X2.InterFre Number of X2-based DBS3900 LTE/

q.PrepAttOut inter-frequency BTS3900 LTE/
attempts in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number ofX2-based intra-frequency outgoing handover attempts and
X2-basedinter-frequency outgoing handover attempts in a cell.
Measurement Points
As shown at point A in Figure 2-299, the corresponding counter is incremented by 1 in the
source cell each time the source eNodeB decides to perform an X2-based blind handover or the
source eNodeB decides to perform an X2-based handover after receiving a measurement report
from the UE. The counters are measured as follows: If the source cell and the target cell work
on the same frequency, the L.HHO.X2.IntraFreq.PrepAttOut counter is incremented by 1. If the
source cell and the target cell work on different frequencies, the
L.HHO.X2.InterFreq.PrepAttOut counter is incremented by 1.
Figure 2-299

Formula
None
Unit
None
Related Features
L.HHO.X2.IntraFreq.Pre- Multi-mode: None

pAttOut GSM: None
UMTS: None
frequency Handover
L.HHO.X2.InterFreq.Pre- Multi-mode: None

pAttOut GSM: None
UMTS: None
frequency Handover
2.2.27.2 Number of X2-based Outgoing Handover Executions in a Cell
Counters
Description
1526727265 L.HHO.X2.IntraFre Number of X2-based DBS3900 LTE/

q.ExecAttOut intra-frequency BTS3900 LTE/
BTS3900AL LTE,
BTS3900


Description
1526727268 L.HHO.X2.InterFre Number of X2-based DBS3900 LTE/

q.ExecAttOut inter-frequency BTS3900 LTE/
outgoing handovers BTS3900A LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of X2-based intra-frequency outgoing handover executions
and X2-basedinter-frequency outgoing handover executions in a cell.
Measurement Points
As shown at point B in Figure 2-300, during an X2-basded handover the corresponding counter
is incremented by 1 in the target cell each time the source eNodeB sends an RRC Connection
Reconfiguration message to the UE after receiving a HANDOVER REQUEST
ACKNOWLEDGE message from the target eNodeB. The counters are measured as follows:
L.HHO.X2.IntraFreq.ExecAttOut counter is incremented by 1.
L.HHO.X2.InterFreq.ExecAttOut counter is incremented by 1.
Figure 2-300

Formula
None
Unit
None
Related Features
L.HHO.X2.IntraFreq.Exe- Multi-mode: None

cAttOut GSM: None
UMTS: None
frequency Handover
L.HHO.X2.InterFreq.Exe- Multi-mode: None

cAttOut GSM: None
UMTS: None
frequency Handover
2.2.27.3 Number of Successful X2-based Outgoing Handovers in a Cell
Counters
Description
1526727266 L.HHO.X2.IntraFre Number of DBS3900 LTE/

q.ExecSuccOut successful X2-based BTS3900 LTE/
intra-frequency BTS3900A LTE/
outgoing handovers BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1526727269 L.HHO.X2.InterFre Number of DBS3900 LTE/

q.ExecSuccOut successful X2-based BTS3900 LTE/
inter-frequency BTS3900A LTE/
BTS3900
Description
The counters measure the number of successful X2-based intra-frequency outgoing handovers
and the number of successful X2-based inter-frequency outgoing handovers in a cell.
Measurement Points
is incremented by 1 in the source cell each time the source eNodeB receives an UE CONTEXT
As shown at point C in Figure 2-302, the corresponding counter is incremented by 1 in the target
cell each time the source eNodeB receives a UE CONTEXT RELESE message from the target
eNodeB after an RRC connection is successfully reestablished to the target eNodeB for the UE.
As shown at point C in Figure 2-303, the corresponding counter is incremented by 1 in the

source cell each time after an RRC connection is successfully reestablished to the source eNodeB
for the UE.
L.HHO.X2.IntraFreq.ExecSuccOut counter is incremented by 1.
L.HHO.X2.InterFreq.ExecSuccOut counter is incremented by 1.

Figure 2-301
Figure 2-302

Figure 2-303
Formula
None
Unit
None
Related Features
L.HHO.X2.IntraFreq.Exe- Multi-mode: None

cSuccOut GSM: None
UMTS: None
frequency Handover

L.HHO.X2.InterFreq.Exe- Multi-mode: None

cSuccOut GSM: None
UMTS: None
frequency Handover
2.2.27.4 Number of X2-based Outgoing Handover Failures for Different Causes in

a Cell
Counters
Description
1526728864 L.HHO.X2.FailOut. Number of X2-based DBS3900 LTE/

HOCancel outgoing handover BTS3900 LTE/
cancellation in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of X2-based incoming handover failures for different causes
in a cell. The incoming handover failure usually occurs during the handover preparation phase.
During the handover preparation phase, between the handover decision phase and the handover
execution phase, the handover resources are prepared.
Measurement Points
L.HHO.X2.FailOut.HOCancel counter is incremented by 1 each time the source cell decides to
cancel the handover and sends a HANDOVER CANCEL message to the target eNodeB.

Figure 2-304
Formula
None
Unit
None
Related Features
L.HHO.X2.FailOut.HOCan- Multi-mode: None

cel GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.27.5 Number of Successful X2-based Outgoing Handovers Where RRC


Counters
Description
1526728906 L.HHO.X2.IntraFre Number of DBS3900 LTE/

q.Succ.ReEst2Src successful X2-based BTS3900 LTE/
intra-frequency BTS3900A LTE/
where RRC BTS3900AL LTE,
connections are BTS3900
a cell
1526728907 L.HHO.X2.InterFre Number of DBS3900 LTE/

q.Succ.ReEst2Src successful X2-based BTS3900 LTE/
inter-frequency BTS3900A LTE/
where RRC BTS3900AL LTE,
connections are BTS3900
a cell
Description
The counters measure the number of successful X2-based outgoing handovers where RRC
Measurement Points
L.HHO.X2.IntraFreq.Succ.ReEst2Src counter is incremented by 1.
L.HHO.X2.InterFreq.Succ.ReEst2Src counter is incremented by 1.

Figure 2-305
Formula
None
Unit
None
Related Features
L.HHO.X2.IntraFreq.Succ. Multi-mode: None

ReEst2Src GSM: None
UMTS: None
frequency Handover

L.HHO.X2.InterFreq.Succ. Multi-mode: None

ReEst2Src GSM: None
UMTS: None
frequency Handover
2.2.28 Measurement related to Intra eRan DRX HOOUT

(HO.DRX.Out.Cell)
Overview
The HO.DRX.Out.Cell function subset measures the performance of outgoing handovers of the
UE in the DRX state in a cell, as shown in Figure 2-306, Figure 2-307, and Figure 2-308.
Figure 2-306

Figure 2-307
Figure 2-308

Counters
Description
1526727285 L.HHO.DRX.Intra Number of intra- V100R008C00,and

eNB.IntraFreq.Ex- eNodeB intra- the mapping single-
ecAttOut frequency outgoing mode base station
executions in the introduce this
DRX state counter is:
eNodeB:Version
earlier than
V100R003C00
1526727286 L.HHO.DRX.Intra Number of V100R008C00,and

eNB.IntraFreq.Ex- successful intra- the mapping single-
ecSuccOut eNodeB intra- mode base station
handovers in the introduce this
eNodeB:Version
earlier than
V100R003C00
1526727287 L.HHO.DRX.Intra Number of intra- V100R008C00,and

eNB.InterFreq.Ex- eNodeB inter- the mapping single-
eNodeB:Version
earlier than
V100R003C00
1526727288 L.HHO.DRX.Intra Number of V100R008C00,and

eNB.InterFreq.Ex- successful intra- the mapping single-
ecSuccOut eNodeB inter- mode base station
eNodeB:Version
earlier than
V100R003C00


Description
1526727289 L.HHO.DRX.Inter Number of inter- V100R008C00,and

eNB.IntraFreq.Ex- eNodeB intra- the mapping single-
eNodeB:Version
earlier than
V100R003C00
1526727290 L.HHO.DRX.Inter Number of V100R008C00,and

eNB.IntraFreq.Ex- successful inter- the mapping single-
ecSuccOut eNodeB intra- mode base station
eNodeB:Version
earlier than
V100R003C00
1526727291 L.HHO.DRX.Inter Number of inter- V100R008C00,and

eNB.InterFreq.Ex- eNodeB inter- the mapping single-
eNodeB:Version
earlier than
V100R003C00
1526727292 L.HHO.DRX.Inter Number of V100R008C00,and

eNB.InterFreq.Ex- successful inter- the mapping single-
ecSuccOut eNodeB inter- mode base station
eNodeB:Version
earlier than
V100R003C00
None
2.2.28.1 Number of Intra-eNodeB Outgoing Handovers Executions in the DRX State

Counters
Description
1526727285 L.HHO.DRX.Intrae Number of intra- DBS3900 LTE/

NB.IntraFreq.Exe- eNodeB intra- BTS3900 LTE/
cAttOut frequency outgoing BTS3900A LTE/
executions in the BTS3900AL LTE,
DRX state BTS3900
1526727287 L.HHO.DRX.Intrae Number of intra- DBS3900 LTE/

NB.InterFreq.Exe- eNodeB inter- BTS3900 LTE/
DRX state BTS3900
Description
The counters measure the number of executed intra-eNodeB intra-frequency and intra-eNodeB
inter-frequency outgoing handovers, respectively. The source cell and target cell of such a
handover are controlled by the same eNodeB and the UE enters the discontinuous reception
(DRX) state when the eNodeB decides to perform a handover.
Measurement Points
During such a handover, the source cell and target cell are controlled by the same eNodeBs and
the UE enters the DRX state when the eNodeB decides to perform a handover. As shown at point
B in Figure 2-309, if the source cell and target cell work on the same frequency, the
L.HHO.DRX.IntraeNB.IntraFreq.ExecAttOut counter is incremented by 1 in the source cell
each time the eNodeB sends an RRC Connection Reconfiguration message to the UE. If the
source cell and target cell work on different frequencies, the
L.HHO.DRX.IntraeNB.InterFreq.ExecAttOut counter is incremented by 1 accordingly.
Figure 2-309

Formula
None
Unit
None
Related Features
L.HHO.DRX.IntraeNB.Intra Multi-mode: None

Freq.ExecAttOut GSM: None
UMTS: None
LBFD-00201801 Coverage Based Intra-
TDLBFD-00201801 DRX
frequency Handover
L.HHO.DRX.IntraeNB.Inter Multi-mode: None

UMTS: None
TDLBFD-00201802 DRX
frequency Handover
2.2.28.2 Number of Successful Intra-eNodeB Outgoing Handovers in the DRX State
Counters
Description
1526727286 L.HHO.DRX.Intrae Number of DBS3900 LTE/

NB.IntraFreq.Exe- successful intra- BTS3900 LTE/
cSuccOut eNodeB intra- BTS3900A LTE/
handovers in the BTS3900AL LTE,
DRX state BTS3900


Description
1526727288 L.HHO.DRX.Intrae Number of DBS3900 LTE/

NB.InterFreq.Exe- successful intra- BTS3900 LTE/
cSuccOut eNodeB inter- BTS3900A LTE/
DRX state BTS3900
Description
The counters measure the number of successful intra-eNodeB intra-frequency and intra-eNodeB
handover are controlled by the same eNodeB and the UE enters the discontinuous reception
(DRX) state when the eNodeB decides to perform a handover.
Measurement Points
During such a handover, the source cell and target cell are controlled by the same eNodeB and
the UE enters the DRX state when the eNodeB decides to perform a handover. As shown at point
C in Figure 2-310 or Figure 2-311, the corresponding counter is incremented by 1 each time
data in the buffer is forwarded during the handover after the target or source cell receives an
RRC Connection Reconfiguration Complete or RRC Connection Reestablishment Complete
message from the UE. If the source cell and target cell work on the same frequency, the
L.HHO.DRX.IntraeNB.IntraFreq.ExecSuccOut counter is incremented by 1 in the source cell.
L.HHO.DRX.IntraeNB.InterFreq.ExecSuccOut counter is incremented by 1 in the source cell.
Figure 2-310

Figure 2-311
Formula
None
Unit
None
Related Features
L.HHO.DRX.IntraeNB.Intra Multi-mode: None

Freq.ExecSuccOut GSM: None
UMTS: None
LBFD-00201801 Coverage Based Intra-
TDLBFD-00201801 DRX
frequency Handover

L.HHO.DRX.IntraeNB.Inter Multi-mode: None

UMTS: None
TDLBFD-00201802 DRX
frequency Handover
2.2.28.3 Number of Inter-eNodeB Outgoing Handovers Executions in the DRX State
Counters
Description
1526727289 L.HHO.DRX.Intere Number of inter- DBS3900 LTE/

NB.IntraFreq.Exe- eNodeB intra- BTS3900 LTE/
DRX state BTS3900
1526727291 L.HHO.DRX.Intere Number of inter- DBS3900 LTE/

NB.InterFreq.Exe- eNodeB inter- BTS3900 LTE/
DRX state BTS3900
Description
The counters measure the number of executed inter-eNodeB intra-frequency and inter-eNodeB
handover are controlled by different eNodeBs and the UE enters the discontinuous reception
(DRX) state when the source eNodeB decides to perform a handover.
Measurement Points
During such a handover, the source cell and target cell are controlled by different eNodeBs and
the UE enters the DRX state when the source eNodeB decides to perform a handover. As shown
at point B in Figure 2-312 or Figure 2-313, if the source cell and target cell work on the same
frequency, the L.HHO.DRX.IntereNB.IntraFreq.ExecAttOut counter is incremented by 1 in the

source cell each time the source eNodeB sends an RRC Connection Reconfiguration message
to the UE after receiving a HANDOVER REQUEST ACKNOWLEDGE message from the
target eNodeB or receiving a HANDOVER COMMAND message from the MME. If the source
cell and target cell work on different frequencies, the
L.HHO.DRX.IntereNB.InterFreq.ExecAttOut counter is incremented by 1 accordingly.
Figure 2-312
Figure 2-313

Formula
None
Unit
None
Related Features
L.HHO.DRX.IntereNB.Intra Multi-mode: None

UMTS: None
frequency Handover
L.HHO.DRX.IntereNB.Inter Multi-mode: None

UMTS: None

frequency Handover
TDLBFD-00201801
DRX
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.28.4 Number of Successful Inter-eNodeB Outgoing Handovers in the DRX State

Counters
Description
1526727290 L.HHO.DRX.Intere Number of DBS3900 LTE/

NB.IntraFreq.Exe- successful inter- BTS3900 LTE/
cSuccOut eNodeB intra- BTS3900A LTE/
DRX state BTS3900
1526727292 L.HHO.DRX.Intere Number of DBS3900 LTE/

NB.InterFreq.Exe- successful inter- BTS3900 LTE/
cSuccOut eNodeB inter- BTS3900A LTE/
DRX state BTS3900
Description
The counters measure the number of successful inter-eNodeB intra-frequency and inter-eNodeB
handover are controlled by different eNodeBs and the UE enters the discontinuous reception
(DRX) state when the source eNodeB decides to perform a handover.
Measurement Points
During such a handover, the source cell and target cell are controlled by different eNodeBs and
the UE enters the DRX state when the source eNodeB decides to perform a handover.
data in the buffer is completely forwarded during the handover after the source eNodeB receives
a UE CONTEXT RELEASE message from the target eNodeB during an X2-based handover.
data in the buffer is completely forwarded during the handover after the UE is successfully
reestablished towards the target eNodeB during an X2-based handover and after the source
after the UE is successfully reestablished towards the source eNodeB during an X2-based
handover.
data in the buffer is completely forwarded during the handover after the source eNodeB receives
a UE CONTEXT RELEASE COMMAND message from the MME during an S1-based
handover.
data in the buffer is completely forwarded during the handover after the UE is successfully
reestablished towards the target eNodeB during an S1-based handover and after the source

after the UE is successfully reestablished towards the source eNodeB during an S1-based
handover.
L.HHO.DRX.IntereNB.IntraFreq.ExecSuccOut counter is incremented by 1.
L.HHO.DRX.IntereNB.InterFreq.ExecSuccOut counter is incremented by 1.
Figure 2-314

Figure 2-315
Figure 2-316

Figure 2-317

Figure 2-318

Figure 2-319
Formula
None
Unit
None

Related Features
L.HHO.DRX.IntereNB.Intra Multi-mode: None

UMTS: None

frequency Handover
TDLBFD-00201801
DRX
TDLBFD-00201802
frequency Handover
frequency Handover
L.HHO.DRX.IntereNB.Inter Multi-mode: None

UMTS: None
TDLBFD-00201801 DRX
TDLBFD-00201802 Coverage Based Intra-

frequency Handover
frequency Handover
2.2.29 Measurement related to Packet (Traffic.Packet.Cell)
Overview
The Traffic.Packet.Cell function subset measures the processing delay and loss rate of uplink
or downlink PDCP SDUs of each service with a different QCI in a cell.

Counters
Description
1526727907 L.Traffic.DL.PktD Total processing V100R008C00,and

elay.Time.QCI.1 delay of downlink the mapping single-
PDCP SDUs for mode base station
DRB services with version that
counter is:
eNodeB:V100R003
C00
1526727908 L.Traffic.DL.PktD Number of V100R008C00,and

elay.Num.QCI.1 successfully the mapping single-
downlink PDCP version that
SDUs for DRB introduce this
services with the QCI counter is:
of 1 in a cell eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00

C00

counter is:
eNodeB:V100R003
C00


Description

C00

counter is:
eNodeB:V100R003
C00

C00

counter is:
eNodeB:V100R003
C00

C00


Description

counter is:
eNodeB:V100R003
C00

C00

counter is:
eNodeB:V100R003
C00

C00

counter is:
eNodeB:V100R003
C00


Description

C00

counter is:
eNodeB:V100R003
C00

C00
1526727934 L.Traffic.DL.PktU Total number of V100R008C00,and

uLoss.Loss.QCI.1 discarded downlink the mapping single-
over the Uu interface counter is:
eNodeB:V100R003
C00

uLoss.Tot.QCI.1 transmitted the mapping single-
SDUs for DRB version that
of 1 in a cell over the counter is:
Uu interface eNodeB:V100R003
C00


Description

eNodeB:V100R003
C00

C00

eNodeB:V100R003
C00

C00

eNodeB:V100R003
C00


Description

C00

eNodeB:V100R003
C00

C00

eNodeB:V100R003
C00

C00


Description

eNodeB:V100R003
C00

C00

eNodeB:V100R003
C00

C00

eNodeB:V100R003
C00


Description

C00
1526727961 L.Traffic.UL.PktL Total number of V100R008C00,and

oss.Loss.QCI.1 discarded uplink the mapping single-
counter is:
eNodeB:V100R003
C00

oss.Tot.QCI.1 expected uplink data the mapping single-
packets for DRB mode base station
counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00


Description

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00


Description

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00


Description

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00

counter is:
eNodeB:V100R003
C00
None
2.2.29.1 Total Processing Delay of Downlink PDCP SDUs for DRB Services in a
Cell

Counters
Description
1526727907 L.Traffic.DL.PktDel Total processing DBS3900 LTE/

ay.Time.QCI.1 delay of downlink BTS3900 LTE/
PDCP SDUs for BTS3900A LTE/
DRB services with BTS3900L LTE/
BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900
Description
The counters measure the total processing delay of downlink PDCP SDUs for DRB services
with a specific QCI ranging from 1 to 9 in a cell. If this cell is an SCell of a CA UE, the processing
delay of downlink PDCP SDUs for the CA UE is also counted in the corresponding counter.
Measurement Points
The total processing delay of downlink PDCP SDUs for DRB services with a specific QCI
ranging from 1 to 9 is sampled in a cell. At the end of a measurement period, the sum of these
Formula
None
Unit
ms

Related Features
L.Traffic.DL.PktDelay.Time Multi-mode: None

.QCI.1 GSM: None
UMTS: None

.QCI.2 GSM: None
UMTS: None

.QCI.3 GSM: None
UMTS: None

.QCI.4 GSM: None
UMTS: None

.QCI.5 GSM: None
UMTS: None


.QCI.6 GSM: None
UMTS: None

.QCI.7 GSM: None
UMTS: None

.QCI.8 GSM: None
UMTS: None

.QCI.9 GSM: None
UMTS: None
2.2.29.2 Number of Successfully Transmitted Downlink PDCP SDUs for DRB

Services in a Cell

Counters
Description
1526727908 L.Traffic.DL.PktDel Number of DBS3900 LTE/

ay.Num.QCI.1 successfully BTS3900 LTE/
downlink PDCP BTS3900L LTE/
SDUs for DRB BTS3900AL LTE,
services with the QCI BTS3900
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

of 6 in a cell


Description

of 7 in a cell

of 8 in a cell

of 9 in a cell
Description
The counters measure the number of successfully transmitted downlink PDCP SDUs for DRB
services with a specific QCI ranging from 1 to 9 in a cell. If this cell is an SCell of a CA UE,
the number of successfully transmitted downlink PDCP SDUs for the CA UE is also counted in
the corresponding counter.
Measurement Points
The corresponding counter is incremented by 1 based on the QCI each time a PDCP SDU is
successfully sent. A PDCP SDU is successfully sent if an HARQ ACK is received.
Formula
None
Unit
packet

Related Features
L.Traffic.DL.PktDelay.Num Multi-mode: None

.QCI.1 GSM: None
UMTS: None

.QCI.2 GSM: None
UMTS: None

.QCI.3 GSM: None
UMTS: None

.QCI.4 GSM: None
UMTS: None

.QCI.5 GSM: None
UMTS: None


.QCI.6 GSM: None
UMTS: None

.QCI.7 GSM: None
UMTS: None

.QCI.8 GSM: None
UMTS: None

.QCI.9 GSM: None
UMTS: None
2.2.29.3 Total Number of Discarded Downlink PDCP SDUs for DRB Services in a
Cell

Counters
Description
1526727934 L.Traffic.DL.PktUu Total number of DBS3900 LTE/

Loss.Loss.QCI.1 discarded downlink BTS3900 LTE/
over the Uu interface BTS3900








Description


Description
The counters measure the total number of discarded downlink PDCP SDUs for DRB services
Measurement Points
The total number of discarded downlink PDCP SDUs for DRB services with a specific QCI
Formula
None
Unit
packet
Related Features
L.Traffic.DL.PktUuLoss.Lo Multi-mode: None

ss.QCI.1 GSM: None
UMTS: None


ss.QCI.2 GSM: None
UMTS: None

ss.QCI.3 GSM: None
UMTS: None

ss.QCI.4 GSM: None
UMTS: None

ss.QCI.5 GSM: None
UMTS: None

ss.QCI.6 GSM: None
UMTS: None


ss.QCI.7 GSM: None
UMTS: None

ss.QCI.8 GSM: None
UMTS: None

ss.QCI.9 GSM: None
UMTS: None
2.2.29.4 Total Number of Transmitted Downlink PDCP SDUs for DRB Services in
a Cell
Counters
Description

Loss.Tot.QCI.1 transmitted BTS3900 LTE/
SDUs for DRB BTS3900L LTE/
of 1 in a cell over the BTS3900
Uu interface


Description

Uu interface

Uu interface

Uu interface

Uu interface

Uu interface

Uu interface


Description

Uu interface

Uu interface
Description
The counters measure the total number of transmitted downlink PDCP SDUs for DRB services
Measurement Points
The total number of transmitted downlink PDCP SDUs for DRB services with a specific QCI
Formula
None
Unit
packet

Related Features
L.Traffic.DL.PktUuLoss.Tot Multi-mode: None

.QCI.1 GSM: None
UMTS: None

.QCI.2 GSM: None
UMTS: None

.QCI.3 GSM: None
UMTS: None

.QCI.4 GSM: None
UMTS: None

.QCI.5 GSM: None
UMTS: None


.QCI.6 GSM: None
UMTS: None

.QCI.7 GSM: None
UMTS: None

.QCI.8 GSM: None
UMTS: None

.QCI.9 GSM: None
UMTS: None
2.2.29.5 Total Number of Discarded Uplink PDCP SDUs for DRB Services in a Cell

Counters
Description
1526727961 L.Traffic.UL.PktLos Total number of DBS3900 LTE/

s.Loss.QCI.1 discarded uplink BTS3900 LTE/
BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900

BTS3900
Description
The counters measure the total number of discarded uplink PDCP SDUs for DRB services with
a specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The total number of discarded uplink PDCP SDUs for DRB services with a specific QCI ranging
from 1 to 9 is sampled per second. At the end of a measurement period, the sum of these sampling
Formula
None
Unit
packet
Related Features
L.Traffic.UL.PktLoss.Loss. Multi-mode: None

QCI.1 GSM: None
UMTS: None


QCI.2 GSM: None
UMTS: None

QCI.3 GSM: None
UMTS: None

QCI.4 GSM: None
UMTS: None

QCI.5 GSM: None
UMTS: None

QCI.6 GSM: None
UMTS: None


QCI.7 GSM: None
UMTS: None

QCI.8 GSM: None
UMTS: None

QCI.9 GSM: None
UMTS: None
2.2.29.6 Total Number of Expected Uplink Data Packets for DRB Services in a Cell
Counters
Description

s.Tot.QCI.1 expected uplink data BTS3900 LTE/
packets for DRB BTS3900A LTE/
BTS3900


Description

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900

BTS3900


Description

BTS3900
Description
The counters measure the total number of expected uplink data packets for DRB services with
a specific QCI ranging from 1 to 9 in a cell.
Measurement Points
The total number of expected uplink data packets for DRB services with a specific QCI ranging
from 1 to 9 is sampled per second. The sampling result is calculated by accumulating the
difference between the sequence numbers of the current PDCP PDU and previous PDCP PDU
once the PDCP layer receives a PDCP PDU. At the end of a measurement period, the sum of
Formula
None
Unit
packet
Related Features
L.Traffic.UL.PktLoss.Tot.Q Multi-mode: None

CI.1 GSM: None
UMTS: None


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

CI.9 GSM: None
UMTS: None
2.2.30 Measurement related to DFEE (ChMeas.DFEE.Cell)
Overview
The ChMeas.DFEE.Cell function subset measures the duration when a cell enters the energy
saving and emission reduction state, including RF channel intelligent shutdown, and intelligent
power-off of carriers in the same coverage of UMTS network or intelligent power-off of carriers.

Counters
Description
1526728150 L.ChMeas.DFEE.R Duration of RF V100R008C00,and

FOFF.Dur channel intelligent the mapping single-
shutdown mode base station
version that
introduce this
counter is:
eNodeB:Version
earlier than
V100R003C00
1526728151 L.ChMeas.DFEE.C Duration of V100R008C00,and

arrierOFF.Dur intelligent power-off the mapping single-
of carriers in the mode base station
same coverage of version that
UMTS network or introduce this
intelligent power-off counter is:
of carriers in the eNodeB:Version
same coverage in a earlier than
cell V100R003C00
None
2.2.30.1 Duration of Energy Saving and Emission Reduction
Counters
Description
1526728150 L.ChMeas.DFEE.RF Duration of RF DBS3900 LTE/

OFF.Dur channel intelligent BTS3900 LTE/
shutdown BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1526728151 L.ChMeas.DFEE.Ca Duration of DBS3900 LTE/

rrierOFF.Dur intelligent power-off BTS3900 LTE/
of carriers in the BTS3900A LTE/
same coverage of BTS3900L LTE/
UMTS network or BTS3900AL LTE,
intelligent power-off BTS3900
of carriers in the
same coverage in a
cell
Description
The counters measure the duration when the cell is in the energy saving and emission reduction
state (including RF channel intelligent shutdown, and intelligent power-off of carriers in the
same coverage of UMTS network or intelligent power-off of carriers in the same coverage).
Measurement Points
The energy saving mode of a cell is sampled per second. If the cell is in the energy saving and
emission reduction state (including RF channel intelligent shutdown, and intelligent power-off
of carriers in the same coverage of UMTS network or intelligent power-off of carriers in the
same coverage), the sampling result is 1 second. At the end of a measurement period, the sum
of these sampling results is used as the value of the corresponding counter. A deviation of one
sampling period may exist in the sampling timer when the timer performs time synchronization.
As a result, a deviation of one sampling period will also be generated in the value of the
corresponding counter. The deviation affects the values of the KPIs that are calculated by using
the counter. The effects vary with the deviation in the value of the counter and calculation
formulas for the KPIs.
Formula
None
Unit
s

Related Features
L.ChMeas.DFEE.RFOFF.D Multi-mode: None

ur GSM: None
UMTS: None
LTE: LOFD-001039 RF Channel Intelligent
TDLOFD-001039 Shutdown
RF Channel Intelligent
Shutdown
L.ChMeas.DFEE.CarrierOF Multi-mode: None

F.Dur GSM: None
UMTS: None
LTE: LOFD-001042 Intelligent Power-Off of
TDLOFD-001042 Carriers in the Same
Coverage
LOFD-001074
Carriers in the Same
Coverage
Carriers in the Coverage of
GSM/UMTS Network
2.2.31 Measurement related to LCS in a cell (LCS.Cell)
Overview
Location Service (LCS) provides a means to determine the geographic position and velocity of
the UE based on measuring radio signals. The Enhanced Cell ID (E-CID) and Observed Time
Difference of Arrival (OTDOA) positioning techniques are supported by the eNodeB. The
LCS.Cell function subset measures the number of E-CID measurement requests and successful
E-CID measurement requests in a cell. The values of the two counters are used to calculate the
successful E-CID measurement rate.

Figure 2-320
Counters
Description
1526728154 L.LCS.EcidMeas.R Number of E-CID V100R008C00,and

eq measurement the mapping single-
requests in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728155 L.LCS.EcidMeas.S Number of V100R008C00,and

ucc successful E-CID the mapping single-
measurement mode base station
requests in a cell version that
introduce this
counter is:
eNodeB:V100R003
C00
None
2.2.31.1 Number of E-CID Measurement Requests in a Cell

Counters
Description
1526728154 L.LCS.EcidMeas.Re Number of E-CID DBS3900 LTE/

q measurement BTS3900 LTE/
requests in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of LCS E-CID MEASUREMENT INITIATION REQUEST
messages received by the eNodeB from the E-SMLC. The LCS E-CID MEASUREMENT
INITIATION REQUEST message is an LPPa signaling message. The message is sent by the E-
SMLC to an eNodeB, requesting the E-CID measurement.
Measurement Points
as shown at point A in Figure 2-321, the L.LCS.EcidMeas.Req counter is incremented by 1
each time the eNodeB receives an E-CID MEASUREMENT INITIATION REQUEST message.
Figure 2-321
Formula
None

Unit
None
Related Features
L.LCS.EcidMeas.Req Multi-mode: None

GSM: None
UMTS: None
2.2.31.2 Number of Successful E-CID Measurement Requests in a Cell
Counters
Description
1526728155 L.LCS.EcidMeas.Su Number of DBS3900 LTE/

cc successful E-CID BTS3900 LTE/
measurement BTS3900A LTE/
requests in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of E-CID MEASUREMENT INITIATION RESPONSE
messages in a cell. The E-CID MEASUREMENT INITIATION RESPONSE message is an
LPPa signaling message sent from an eNodeB to the E-SMLC. The message is used to notify
the E-SMLC that the E-CID measuring is successfully performed and report the E-CID
measurement data.
Measurement Points
as shown at point B in Figure 2-322, the L.LCS.EcidMeas.Succ counter is incremented by 1
each time the eNodeB sends an E-CID MEASUREMENT INITIATION RESPONSE message.

Figure 2-322
Formula
None
Unit
None
Related Features
L.LCS.EcidMeas.Succ Multi-mode: None

GSM: None
UMTS: None
2.2.32 Measurements related to EMC (EMC.Cell)
Overview
The EMC.Cell function subset measures the counters related to emergency calls in a cell.

Counters
Description
1526728162 L.EMC.HHO.Pre- Number of outgoing V100R008C00,and

pAttOut handover attempts the mapping single-
for emergency calls mode base station
introduce this
counter is:
eNodeB:V100R003
C00
1526728163 L.EMC.HHO.Exe- Number of executed V100R008C00,and

cAttOut outgoing handovers the mapping single-
for emergency calls mode base station
introduce this
counter is:
eNodeB:V100R003
C00
1526728164 L.EMC.HHO.Exe- Number of V100R008C00,and

cSuccOut successful outgoing the mapping single-
handovers for mode base station
emergency calls in a version that
cell introduce this
counter is:
eNodeB:V100R003
C00
1526728167 L.EMC.E- Number of E-RAB V100R008C00,and

RAB.AttEst setup attempts for the mapping single-
emergency calls in a mode base station
cell version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728168 L.EMC.E- Number of V100R008C00,and

RAB.SuccEst successful E-RAB the mapping single-
setups for emergency mode base station
calls in a cell version that
introduce this
counter is:
eNodeB:V100R003
C00


Description
1526728169 L.EMC.E- Number of normal E- V100R008C00,and

RAB.NormRel.Ho- RAB releases due to the mapping single-
Out outgoing handovers mode base station
for emergency calls version that
counter is:
eNodeB:V100R003
C00
1526728170 L.EMC.E- Number of abnormal V100R008C00,and

RAB.AbnormRel. E-RAB releases due the mapping single-
HoOut to outgoing mode base station
handovers for version that
emergency calls in a introduce this
cell counter is:
eNodeB:V100R003
C00
1526728171 L.EMC.E- Number of abnormal V100R008C00,and

RAB.Abnormrel E-RAB releases for the mapping single-
cell version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728172 L.EMC.E- Number of normal E- V100R008C00,and

RAB.NormRel RAB releases for the mapping single-
cell version that
introduce this
counter is:
eNodeB:V100R003
C00
None
2.2.32.1 Number of Outgoing Handover Attempts for Emergency Calls in a Cell

Counters
Description
1526728162 L.EMC.HHO.Pre- Number of outgoing DBS3900 LTE/

pAttOut handover attempts BTS3900 LTE/
for emergency calls BTS3900A LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of intra-eNodeB and inter-eNodeB outgoing handover
attempts. Intra-eNodeB outgoing handovers include intra-eNodeB intra-frequency and intra-
eNodeB inter-frequency outgoing handovers. Similarly, inter-eNodeB outgoing handovers
include inter-eNodeB intra-frequency and inter-eNodeB inter-frequency outgoing handovers.
Measurement Points
During a handover where the source cell and target cell are controlled by the same eNodeB, as
shown at point A in Figure 2-323, the counter is incremented by 1 each time the eNodeB decides
to perform an intra-eNodeB outgoing handover for an emergency call after receiving a
Figure 2-324 shows a handover over the X2 interface. During such a handover where the source
cell and target cell are controlled by different eNodeBs, as shown at point A in Figure 2-324,
the counter is incremented by 1 each time the source eNodeB decides to perform an inter-eNodeB
handover over the X2 interface for an emergency call after receiving a measurement report from
the UE.
Figure 2-325 shows a handover over the S1 interface. During such a handover where the source
cell and target cell are controlled by different eNodeBs, as shown at point A in Figure 2-325,
the counter is incremented by 1 each time the source eNodeB decides to perform an inter-eNodeB
handover over the S1 interface for an emergency call after receiving a measurement report from
the UE.

Figure 2-323
Figure 2-324

Figure 2-325
Formula
None
Unit
None
Related Features
L.EMC.HHO.PrepAttOut Multi-mode: None

GSM: None
UMTS: None
LTE: LBFD-002028 Emergency Call
TDLBFD-002028 Emergency call
2.2.32.2 Number of Executed Outgoing Handovers for Emergency Calls in a Cell

Counters
Description
1526728163 L.EMC.HHO.Exe- Number of executed DBS3900 LTE/

cAttOut outgoing handovers BTS3900 LTE/
for emergency calls BTS3900A LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of executed intra-eNodeB and inter-eNodeB outgoing
handovers. Intra-eNodeB outgoing handovers include intra-eNodeB intra-frequency and intra-
eNodeB inter-frequency outgoing handovers. Similarly, inter-eNodeB outgoing handovers
include inter-eNodeB intra-frequency and inter-eNodeB inter-frequency outgoing handovers.
Measurement Points
The counter is incremented if any of the following conditions occurs:
(1) During an intra-eNodeB handover, as shown at point B in Figure 2-326, the source cell sends
an RRC Connection Reconfiguration message to the UE for an emergency call.
(2) During a handover over the X2 interface, as shown at point B in Figure 2-327, the source
eNodeB sends an RRC Connection Reconfiguration message to the UE for an emergency call
after receiving a HANDOVER REQUEST ACKNOWLEDGE message from the target eNodeB.
(3) During a handover over the S1 interface, as shown at point B in Figure 2-328, the source
eNodeB sends an RRC Connection Reconfiguration message to the UE for an emergency call
after receiving a HANDOVER COMMAND message from the MME.
Figure 2-326

Figure 2-327
Figure 2-328
Formula
None
Unit
None

Related Features
L.EMC.HHO.ExecAttOut Multi-mode: None

GSM: None
UMTS: None
2.2.32.3 Number of Successful Outgoing Handovers for Emergency Calls in a Cell
Counters
Description
1526728164 L.EMC.HHO.Exe- Number of DBS3900 LTE/

cSuccOut successful outgoing BTS3900 LTE/
handovers for BTS3900A LTE/
emergency calls in a BTS3900L LTE/
cell BTS3900AL LTE,
BTS3900
Description
The counter measures the number of successful intra-eNodeB and inter-eNodeB outgoing
handovers in a cell. Intra-eNodeB outgoing handovers include intra-eNodeB intra-frequency
and intra-eNodeB inter-frequency outgoing handovers. Similarly, inter-eNodeB outgoing
handovers include inter-eNodeB intra-frequency and inter-eNodeB inter-frequency outgoing
handovers.
Measurement Points
As shown at point C in Figure 2-329, the counter is incremented by 1 each time the eNodeB
receives an RRC Connection Reconfiguration Complete message from the UE for an emergency
call after the eNodeB decides to perform an intra-eNodeB handover.
As shown at point C in Figure 2-330, the counter is incremented by 1 each time the target cell
receives an RRC Connection Reestablishment Complete message from the UE for an emergency
call.
As shown at point C in Figure 2-330, the counter is incremented by 1 each time the source cell
receives an RRC Connection Reestablishment Complete message from the UE for an emergency
call.

As shown at point C in Figure 2-331, the counter is incremented by 1 each time the source
eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB for an
emergency call after the eNodeB decides to perform an X2-based handover.
eNodeB receives a UE CONTEXT RELEASE message from the target eNodeB for an
emergency call after an RRC connection is successfully reestablished for the UE towards the
target eNodeB during X2-based handover.
As shown at point C in Figure 2-335, the counter is incremented by 1 each time for an emergency
call after an RRC connection is successfully reestablished for the UE towards the source eNodeB
during X2-based handover.
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME for an
emergency call after the eNodeB decides to perform an S1-based handover.
eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME for an
emergency call after an RRC connection is successfully reestablished for the UE towards the
target eNodeB during S1-based handover.
As shown at point C in Figure 2-336, the counter is incremented by 1 each time for an emergency
call after an RRC connection is successfully reestablished for the UE towards the source eNodeB
during S1-based handover.
Figure 2-329

Figure 2-330
Figure 2-331

Figure 2-332
Figure 2-333

Figure 2-334

Figure 2-335

Figure 2-336
Formula
None
Unit
None
Related Features
L.EMC.HHO.ExecSuccOut Multi-mode: None

GSM: None
UMTS: None
2.2.32.4 Number of E-RAB Setup Attempts for Emergency Calls in a Cell

Counters
Description
1526728167 L.EMC.E- Number of E-RAB DBS3900 LTE/

RAB.AttEst setup attempts for BTS3900 LTE/
emergency calls in a BTS3900A LTE/
cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of E-RAB setup attempts for emergency calls in a cell.
Measurement Points
As shown at point A in Figure 2-337 or Figure 2-338, the counter is incremented by 1 each
time the eNodeB receives an E-RAB SETUP REQUEST message or an INITIAL CONTEXT
SETUP REQUEST message from the MME for an emergency call.
Figure 2-337

Figure 2-338
Formula
None
Unit
None
Related Features
L.EMC.E-RAB.AttEst Multi-mode: None

GSM: None
UMTS: None
2.2.32.5 Number of Successful E-RAB Setups for Emergency Calls in a Cell

Counters
Description
1526728168 L.EMC.E- Number of DBS3900 LTE/

RAB.SuccEst successful E-RAB BTS3900 LTE/
setups for emergency BTS3900A LTE/
calls in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of successful E-RAB setups for emergency calls in a cell.
Measurement Points
As shown at point B in Figure 2-339 or Figure 2-340, the counter is incremented by 1 each time
the eNodeB sends an E-RAB SETUP RESPONSE message or an INITIAL CONTEXT SETUP
RESPONSE message to the MME for a successfully established emergency call.
Figure 2-339

Figure 2-340
Formula
None
Unit
None
Related Features
L.EMC.E-RAB.SuccEst Multi-mode: None

GSM: None
UMTS: None

2.2.32.6 Number of Normal E-RAB Releases Due to Outgoing Handovers for

Emergency Calls in a Cell
Counters
Description
1526728169 L.EMC.E- Number of normal E- DBS3900 LTE/

RAB.NormRel.Ho- RAB releases due to BTS3900 LTE/
Out outgoing handovers BTS3900A LTE/
for emergency calls BTS3900L LTE/
BTS3900
Description
The counter measures the number of normal E-RAB releases due to outgoing handovers for
emergency calls.
Measurement Points
Figure 2-341 shows an intra-eNodeB handover, Figure 2-342 shows a handover over the X2
interface, and Figure 2-343 shows a handover over the S1 interface. As shown at point C in
Figure 2-341, Figure 2-342, or Figure 2-343, the counter is incremented by 1 in the source cell
each time the source cell normally releases an E-RAB that corresponds to a successful E-RAB
setup in the target cell after a handover is successfully performed and the E-RAB is released for
an emergency call.
Figure 2-341

Figure 2-342
Figure 2-343
Formula
None
Unit
None

Related Features
L.EMC.E- Multi-mode: None

RAB.NormRel.HoOut GSM: None
UMTS: None
2.2.32.7 Number of Abnormal E-RAB Releases Due to Outgoing Handovers for

Emergency Calls in a Cell
Counters
Description
1526728170 L.EMC.E- Number of abnormal DBS3900 LTE/

RAB.AbnormRel.H E-RAB releases due BTS3900 LTE/
oOut to outgoing BTS3900A LTE/
handovers for BTS3900L LTE/
emergency calls in a BTS3900AL LTE,
cell BTS3900
Description
The counter measures the number of abnormal E-RAB releases due to outgoing handovers for
emergency calls in a cell.
Measurement Points
Figure 2-344 shows an intra-eNodeB handover, Figure 2-345 shows a handover over the X2
interface, and Figure 2-346 shows a handover over the S1 interface. As shown at point C in
Figure 2-344, Figure 2-345, or Figure 2-346, the counter is incremented by 1 in the source cell
each time the source cell abnormally releases an E-RAB that corresponds to a failed E-RAB
setup in the target cell after a handover is successfully performed, and the E-RAB is released
for an emergency call.

Figure 2-344
Figure 2-345

Figure 2-346
Formula
None
Unit
None
Related Features
L.EMC.E- Multi-mode: None

RAB.AbnormRel.HoOut GSM: None
UMTS: None
2.2.32.8 Number of Abnormal Releases of E-RABs for Emergency Calls in a Cell

Counters
Description
1526728171 L.EMC.E- Number of abnormal DBS3900 LTE/

RAB.Abnormrel E-RAB releases for BTS3900 LTE/
cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of abnormal E-RAB releases for emergency calls in a cell.
Measurement Points
sends an E-RAB RELEASE INDICATION message to the MME for an E-RAB that carries data
for an emergency call and the release cause is not "Normal Release", "Detach", "User Inactivity",
"CS Fallback triggered", "UE Not Available For PS Service", or "Inter-RAT Redirection". If
the E-RAB RELEASE INDICATION message requires multiple E-RAB releases at the same
time, the corresponding counter is incremented based on the number of services.
As shown at point A in Figure 2-348, all E-RABs of the UE are released each time the eNodeB
sends a UE CONTEXT RELEASE REQUEST message to the MME. The counter is incremented
by 1 each time the eNodeB determines that the E-RAB carries data for an emergency call and
the release cause is not "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered",
"UE Not Available For PS Service", "Inter-RAT Redirection", "Time Critical Handover" or
"Handover Cancelled". The corresponding counter is incremented repeatedly based on the
number of services. When the MME responds to the eNodeB with a UE CONTEXT RELEASE
COMMAND message, the counter is not incremented.
Figure 2-347

Figure 2-348
Formula
None
Unit
None
Related Features
L.EMC.E-RAB.Abnormrel Multi-mode: None

GSM: None
UMTS: None
2.2.32.9 Number of Normal E-RAB Releases for Emergency Calls in a Cell
Counters
Description
1526728172 L.EMC.E- Number of normal E- DBS3900 LTE/

RAB.NormRel RAB releases for BTS3900 LTE/
cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
The counter measures the number of normal E-RAB releases for emergency calls in a cell.
Measurement Points
As shown at point A in Figure 2-349, the eNodeB sends an E-RAB RELEASE INDICATION
message to the MME. The L.EMC.E-RAB.NormRel counter is incremented by 1 each time the
release cause is "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered", "UE
Not Available For PS Service" or "Inter-RAT Redirection" for an emergency call, or the eNodeB
determines that the E-RAB to be released does not carry data. If the E-RAB RELEASE
INDICATION message requires multiple E-RAB releases at the same time, the L.EMC.E-
RAB.NormRel counter is incremented based on the number of services.
As shown at point A in Figure 2-350, the L.EMC.E-RAB.NormRel counter is incremented by

1 each time the eNodeB receives an E-RAB RELEASE COMMAND message from the MME.
If the E-RAB RELEASE COMMAND message requires multiple E-RAB releases at the same
time, the L.EMC.E-RAB.NormRel counter is incremented based on the number of services.
As shown at point A in Figure 2-351, all E-RABs of the UE will be released each time the
eNodeB sends a UE CONTEXT RELEASE REQEUST message to the MME during an eNodeB-
initiated UE context release. The L.EMC.E-RAB.NormRel counter is incremented by 1 each
time the release cause is "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered",
"UE Not Available For PS Service", "Inter-RAT Redirection", "Time Critical Handover", or
"Handover Cancelled" for an emergency call, or the eNodeB determines that the E-RAB to be
released does not carry data. The corresponding counter is incremented repeatedly based on the
number of services. When the MME responds to the eNodeB with a UE CONTEXT RELEASE
COMMAND message, the counter is not incremented.
As shown at point B in Figure 2-351, all E-RABs of the UE will be released when the eNodeB
receives a UE CONTEXT RELEASE COMMAND message from the MME. The L.EMC.E-
RAB.NormRel counter is incremented by one each time the released E-RAB is used for an
emergency call and the release cause is not "Successful Handover ", "Partial Handover ", "S1
intra system Handover triggered ", "S1 inter system Handover triggered ", or "X2 Handover
triggered ".
Figure 2-349

Figure 2-350
Figure 2-351
Formula
None
Unit
None
Related Features
L.EMC.E-RAB.NormRel Multi-mode: None

GSM: None
UMTS: None

2.2.33 Measurements related to UECNTX (UeCntx.Rel.Cell)
Overview
UE context contains user-specific context information throughout the network. The release
success rate of UE contexts represents the capability of a cell to retrieve the UE resources. The
UeCntx.Rel.Cell function subset measures the number of abnormal or normal UE context
releases in a cell. Based on the values of the counters, the release success rate of UE contexts in
a cell is determined. The measurement point of the function subset is shown in Figure 2-352.
Figure 2-352
Counters
Description
1526728227 L.UECNTX.Abnor Number of abnormal V100R008C00,and

mRel UE context releases the mapping single-
version that
introduce this
counter is:
eNodeB:V100R003
C00
1526728228 L.UECNTX.Norm Number of normal V100R008C00,and

Rel UE context releases the mapping single-
version that
introduce this
counter is:
eNodeB:V100R003
C00


Description
1526728440 L.UECNTX.Releas Number of UE V100R008C00,and

e.HighSpeed context releases due the mapping single-
to high mobility of mode base station
UEs version that
introduce this
counter is:
eNodeB:V100R006
C00

e.DurMeasU context releases the mapping single-
during WCDMA mode base station
measurement introduce this
counter is:
eNodeB:V100R005
C00

e.DurMeasG context releases the mapping single-
during a GERAN mode base station
measurement version that
introduce this
counter is:
eNodeB:V100R005
C00
1526728838 L.UECNTX.Rel.S1 Number of abnormal V100R008C00,and

Reset.eNodeB UE context releases the mapping single-
eNodeB due to S1 version that
RESET introduce this
counter is:
eNodeB:V100R006
C00
1526728839 L.UECNTX.Rel.S1 Number of abnormal V100R008C00,and

Reset.MME UE context releases the mapping single-
due to S1 RESET version that
introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728856 L.UECNTX.Rel.eN Number of UE V100R008C00,and

odeB context releases the mapping single-
eNodeB version that
introduce this
counter is:
eNodeB:V100R006
C00

odeB.Rnl context releases the mapping single-
eNodeB due to faults version that
at the radio network introduce this
layer counter is:
eNodeB:V100R006
C00

odeB.Userinact context releases the mapping single-
eNodeB due to user version that
inactivity introduce this
counter is:
eNodeB:V100R006
C00

odeB.UeLost context releases the mapping single-
eNodeB due to UE version that
lost introduce this
counter is:
eNodeB:V100R006
C00

odeB.HOFailure context releases the mapping single-
eNodeB due to a version that
handover failure introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728861 L.UECNTX.Rel.M Number of UE V100R008C00,and

ME context releases the mapping single-
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728862 L.UECNTX.Rel.M Number of UE V100R008C00,and

ME.Normalrel context releases the mapping single-
due to Normal version that
Release introduce this
counter is:
eNodeB:V100R006
C00
Counter Sub Counter
L.UECNTX.Rel.eNodeB L.UECNTX.Rel.eNodeB.Rnl
L.UECNTX.Rel.eNodeB.Userinact
L.UECNTX.Rel.eNodeB.Rnl L.UECNTX.Rel.eNodeB.UeLost
L.UECNTX.Rel.eNodeB.HOFailure
L.UECNTX.Rel.MME L.UECNTX.Rel.MME.Normalrel
2.2.33.1 Number of Abnormal UE Context Releases in a Cell
Counters
Description
1526728227 L.UECNTX.Abnor Number of abnormal DBS3900 LTE/

mRel UE context releases BTS3900 LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900


Description
1526728838 L.UECNTX.Rel.S1 Number of abnormal DBS3900 LTE/

Reset.eNodeB UE context releases BTS3900 LTE/
eNodeB due to S1 BTS3900L LTE/
RESET BTS3900AL LTE,
BTS3900
1526728839 L.UECNTX.Rel.S1 Number of abnormal DBS3900 LTE/

Reset.MME UE context releases BTS3900 LTE/
due to S1 RESET BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of abnormal UE context releases in a cell. Abnormal UE
context releases are releases initiated by the eNodeB due to exceptions and the releases due to
the S1 RESET initiated by the eNodeB or MME.
Measurement Points
As shown at point A in Figure 2-353, all E-RABs of the UE are released if the eNodeB sends
a UE CONTEXT RELEASE REQUEST message to the MME for the UE. The
L.UECNTX.AbnormRel counter is incremented by 1 each time the cause value is not "Normal
Release", "Detach", "User Inactivity", "CS Fallback triggered", "UE Not Available for PS
Service", "Inter-RAT Redirection", "Time Critical Handover", or "Handover Cancelled".
As shown at point A in Figure 2-354, when the eNodeB sends a S1 RESET message to the
MME, the L.UECNTX.Rel.S1Reset.eNodeB counter is accumulated by the number of contexts
in the message.
As shown at point A in Figure 2-355, when the MME sends a S1 RESET message to the eNodeB,
the L.UECNTX.Rel.S1Reset.MME counter is accumulated by the number of contexts in the
message.
Figure 2-353

Figure 2-354
Figure 2-355
Formula
None
Unit
None

Related Features
L.UECNTX.AbnormRel Multi-mode: None

GSM: None
UMTS: None
L.UECNTX.Rel.S1Reset.eN Multi-mode: None

odeB GSM: None
UMTS: None
L.UECNTX.Rel.S1Reset.M Multi-mode: None

ME GSM: None
UMTS: None
2.2.33.2 Number of Normal UE Context Releases in a Cell
Counters
Description
1526728228 L.UECNTX.NormR Number of normal DBS3900 LTE/

el UE context releases BTS3900 LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of normal UE context releases in a cell. A normal UE context
release is initiated by the MME or by the eNodeB due to a normal cause.
Measurement Points
sends a UE CONTEXT RELEASE REQEUST message to the MME and the cause value is
"Normal Release", "Detach", "User Inactivity", "CS Fallback triggered", "UE Not Available for
PS Service", "Inter-RAT Redirection", "Time Critical Handover", or "Handover Cancelled". In

this case, the counter is not incremented again when the eNodeB receives the UE CONTEXT
As shown at point B in Figure 2-356, the counter is incremented by 1 each time the MME sends
the UE CONTEXT RELEASE COMMAND message to the eNodeB to release the UE context
and the release cause is not "Successful Handover ", "Partial Handover ", "S1 intra system
Handover triggered ", "S1 inter system Handover triggered ", or "X2 Handover triggered ".
Figure 2-356
Formula
None
Unit
None
Related Features
L.UECNTX.NormRel Multi-mode: None

GSM: None
UMTS: None
2.2.33.3 Number of UE Context Releases due to High Mobility of UEs

Counters
Description
1526728440 L.UECNTX.Release Number of UE DBS3900 LTE/

.HighSpeed context releases due BTS3900 LTE/
to high mobility of BTS3900A LTE/
UEs BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of UE context releases due to high mobility of UEs with no
data transmission.
Measurement Points
As shown at point A in Figure 2-357, The L.UECNTX.Release.HighSpeed counter is
incremented by 1 each time the eNodeB actively releases the context of a high-mobility UE
without data transmission and sends a UE CONTEXT RELEASE REQUEST message to the
MME.
Figure 2-357
Formula
None
Unit
None

Related Features
L.UECNTX.Release.High- Multi-mode: None

Speed GSM: None
UMTS: None
LTE: LOFD-001106 High-Mobility-Triggered
TDLOFD-001106 Idle Mode
LBFD-002008 High-Mobility-Triggered
Idle Mode
TDLBFD-002008
2.2.33.4 Number of UE Context Releases During an Inter-RAT Measurement
Counters
Description

.DurMeasU context releases BTS3900 LTE/
during WCDMA BTS3900A LTE/
measurement BTS3900AL LTE,
BTS3900

.DurMeasG context releases BTS3900 LTE/
during a GERAN BTS3900A LTE/
measurement BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of UE context releases during an inter-RAT measurement in
a cell.
Measurement Points
As shown at point A in Figure 2-358, after the eNodeB sends the UE a measurement control
message for the WCDMA network due to poor coverage, the eNodeB sends a UE CONTEXT
RELEASE REQUEST message to the MME before receiving a measurement report for the
WCDMA network from the UE. The L.UECNTX.Release.DurMeasU counter is incremented

by 1 each time the cause value contained in the message is "Radio Connection With UE Lost"
or "Failure in the Radio Interface Procedure".
As shown at point A in Figure 2-358, after the eNodeB sends the UE a measurement control
message for the GERAN due to poor coverage, the eNodeB sends a UE CONTEXT RELEASE
REQUEST message to the MME before receiving a measurement report for the GERAN from
the UE. The L.UECNTX.Release.DurMeasG counter is incremented by 1 each time the cause
value contained in the message is "Radio Connection With UE Lost" or "Failure in the Radio
Interface Procedure".
Figure 2-358
Formula
None
Unit
None
Related Features
L.UECNTX.Release.Dur- Multi-mode: None

MeasU GSM: None
UMTS: None
TDLBFD-002008 between E-UTRAN and
UTRAN
TDLOFD-001019
between E-UTRAN and
UTRAN

L.UECNTX.Release.Dur- Multi-mode: None

MeasG GSM: None
UMTS: None
TDLBFD-002008 between E-UTRAN and
GERAN
TDLOFD-001020
between E-UTRAN and
GERAN
2.2.33.5 Number of UE Context Releases Initiated by the eNodeB in a Cell
Counters
Description
1526728856 L.UECNTX.Rel.eN Number of UE DBS3900 LTE/

odeB context releases BTS3900 LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of UE context releases initiated by the eNodeB in a cell.
Measurement Points
As shown at point A in Figure 2-359, this counter is incremented by 1 each time the eNodeB
sends the UE CONTEXT RELEASE REQUEST message to the MME to release a UE context
that has been successfully set up.

Figure 2-359
Formula
None
Unit
None
Related Features
L.UECNTX.Rel.eNodeB Multi-mode: None

GSM: None
UMTS: None
2.2.33.6 Number of UE Context Releases Initiated by the eNodeB due to Different

Causes in a Cell
Counters
Description

odeB.Rnl context releases BTS3900 LTE/
eNodeB due to faults BTS3900L LTE/
at the radio network BTS3900AL LTE,
layer BTS3900


Description

odeB.Userinact context releases BTS3900 LTE/
eNodeB due to user BTS3900L LTE/
inactivity BTS3900AL LTE,
BTS3900

odeB.UeLost context releases BTS3900 LTE/
eNodeB due to UE BTS3900L LTE/
lost BTS3900AL LTE,
BTS3900

odeB.HOFailure context releases BTS3900 LTE/
eNodeB due to a BTS3900L LTE/
handover failure BTS3900AL LTE,
BTS3900
Description
The counters measure the number of UE context releases initiated by the eNodeB due to different
causes.
Measurement Points
As shown at point A in Figure 2-360, after a UE context is successfully set up, it is released if
the eNodeB sends the UE CONTEXT RELEASE REQUEST message to the MME. The
L.UECNTX.Rel.eNodeB.Rnl counter is incremented by 1 if the release is caused by faults at
the radio network layer. The L.UECNTX.Rel.eNodeB.Userinact counter is incremented by 1 if
the release cause is "User Inactivity". The L.UECNTX.Rel.eNodeB.UeLost counter in
incremented if the release cause is "Radio Connection With UE Lost". The
L.UECNTX.Rel.eNodeB.HOFailure counter is incremented by 1 if the release is caused by a
handover failure.

Figure 2-360
Formula
None
Unit
None
Related Features
L.UECNTX.Rel.eNodeB.Rn Multi-mode: None

l GSM: None
UMTS: None
L.UECNTX.Rel.eNodeB.Us Multi-mode: None

erinact GSM: None
UMTS: None
L.UECNTX.Rel.eNodeB.Ue Multi-mode: None

Lost GSM: None
UMTS: None

L.UECNTX.Rel.eNodeB.H Multi-mode: None

OFailure GSM: None
UMTS: None
2.2.33.7 Number of UE Context Releases Initiated by the MME in a Cell
Counters
Description
1526728861 L.UECNTX.Rel.M Number of UE DBS3900 LTE/

ME context releases BTS3900 LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of UE context releases initiated by the MME in a cell.
Measurement Points
As shown at point A in Figure 2-361,this counter is incremented by 1 each time the MME sends
the UE CONTEXT RELEASE COMMAND message to the eNodeB to release the UE context
and the release cause is not "Successful Handover ", "Partial Handover ", "S1 intra system
Handover triggered ", "S1 inter system Handover triggered ", or "X2 Handover triggered ".
Figure 2-361

Formula
None
Unit
None
Related Features
L.UECNTX.Rel.MME Multi-mode: None

GSM: None
UMTS: None
2.2.33.8 Number of UE Context Releases Initiated by the MME due to a Normal

Cause in a Cell
Counters
Description
1526728862 L.UECNTX.Rel.M Number of UE DBS3900 LTE/

ME.Normalrel context releases BTS3900 LTE/
due to Normal BTS3900L LTE/
Release BTS3900AL LTE,
BTS3900
Description
This counter measures the number of UE context releases due to "Normal Release".
Measurement Points
As shown at point A in Figure 2-362, this counter is incremented by 1 each time the MME sends
the UE CONTEXT RELEASE COMMAND message to the eNodeB to release a UE context
that has been successfully set up and the release cause is "Normal Release".

Figure 2-362
Formula
None
Unit
None
Related Features
L.UECNTX.Rel.MME.Nor- Multi-mode: None

malrel GSM: None
UMTS: None
2.2.34 Measurement related to SFN (SFN.Cell)
Overview
The SFN.Cell function subset measures the used resources and number of scheduled resources
in an SFN cell, indicating the operating status of the SFN cell.

Counters
Description
1526728341 L.SFN.User.DLI2J Number of times V100R008C00,and

when the downlink the mapping single-
attribute of a UE mode base station
changes from version that
independent- introduce this
scheduling to joint- counter is:
scheduling eNodeB:V100R005
C01
1526728342 L.SFN.User.DLJ2I Number of times V100R008C00,and

when the downlink the mapping single-
changes from joint - version that
scheduling to introduce this
independent- counter is:
C01
1526728343 L.SFN.DLTRRU.C Number of times that V100R008C00,and

hg the downlink target the mapping single-
RRU of a UE in an mode base station
SFN cell changes version that
introduce this
counter is:
eNodeB:V100R005
C01
1526728344 L.SFN.ULJSch.Use Average number of V100R008C00,and

r.Avg joint-scheduling UEs the mapping single-
in uplink mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C01
1526728345 L.SFN.ULJSch.RR Average number of V100R008C00,and

U.Avg working RRUs used the mapping single-
by joint-scheduling mode base station
Ues in uplink version that
introduce this
counter is:
eNodeB:V100R005
C01


Description
1526728346 L.SFN.User.ULI2J Number of times V100R008C00,and

when the uplink the mapping single-
changes from version that
independent- introduce this
scheduling to joint- counter is:
C01
1526728347 L.SFN.User.ULJ2I Number of times V100R008C00,and

when the uplink the mapping single-
changes from joint - version that
scheduling to introduce this
independent- counter is:
C01
1526728348 L.SFN.ULTRRU.C Number of times that V100R008C00,and

hg the uplink target the mapping single-
RRU of a UE in an mode base station
SFN cell changes version that
introduce this
counter is:
eNodeB:V100R005
C01
1526728384 L.SFN.DLJSch.Use Average number of V100R008C00,and

r.Avg joint-scheduling UEs the mapping single-
in downlink mode base station
version that
introduce this
counter is:
eNodeB:V100R005
C01
1526728385 L.SFN.DLJSch.RR Average number of V100R008C00,and

U.Avg working RRUs used the mapping single-
by joint-scheduling mode base station
UEs in downlink version that
introduce this
counter is:
eNodeB:V100R005
C01
None

2.2.34.1 Number of Times When the Downlink Attribute of a UE Changes from

Independent-scheduling to Joint-scheduling
Counters
Description
1526728341 L.SFN.User.DLI2J Number of times DBS3900 LTE/

when the downlink BTS3900 LTE/
attribute of a UE BTS3900A LTE/
changes from BTS3900L LTE/
independent- BTS3900AL LTE,
scheduling to joint- BTS3900
scheduling
Description
The coutners measures the number of times when the downlink attribute of a UE changes from
independent-scheduling to joint-scheduling
Measurement Points
The counter is incremented by 1 each time the downlink attribute of a UE changes from
independent-scheduling to joint-scheduling.
Formula
None
Unit
None
Related Features
L.SFN.User.DLI2J Multi-mode: None

GSM: None
UMTS: None
2.2.34.2 Number of Times When the Downlink Attribute of a UE Changes from

Joint-scheduling to Independent-scheduling

Counters
Description
1526728342 L.SFN.User.DLJ2I Number of times DBS3900 LTE/

when the downlink BTS3900 LTE/
changes from joint - BTS3900L LTE/
scheduling to BTS3900AL LTE,
independent- BTS3900
scheduling
Description
The counters measures the number of times when the downlink attribute of a UE changes from
joint -scheduling to independent-scheduling
Measurement Points
The counter is incremented by 1 each time the downlink attribute of a UE changes from joint-
scheduling to independent-scheduling.
Formula
None
Unit
None
Related Features
L.SFN.User.DLJ2I Multi-mode: None

GSM: None
UMTS: None
2.2.34.3 Number of Times that the Downlink Target RRU of a UE in an SFN Cell
Changes

Counters
Description
1526728343 L.SFN.DLTRRU.Ch Number of times that DBS3900 LTE/

g the downlink target BTS3900 LTE/
RRU of a UE in an BTS3900A LTE/
SFN cell changes BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures number of times that the downlink target RRU of a UE in an SFN cell
changes
Measurement Points
The L.SFN.DLTRRU.Chg couner is incremented by 1 each time the downlink target RRU of a
UE in an SFN cell changes.
Formula
None
Unit
None
Related Features
L.SFN.DLTRRU.Chg Multi-mode: None

GSM: None
UMTS: None
2.2.34.4 Average Number of Joint-scheduling UEs in the Uplink

Counters
Description
1526728344 L.SFN.ULJSch.User Average number of DBS3900 LTE/

.Avg joint-scheduling UEs BTS3900 LTE/
in uplink BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the average number of joint-scheduling UEs in uplink
Measurement Points
The number of uplink joint-scheduling UEs in an SFN cell is sampled per second. At the end of
an measurement period, the average of these sampling results is used as the value of the counter.
Formula
None
Unit
None
Related Features
L.SFN.ULJSch.User.Avg Multi-mode: None

GSM: None
UMTS: None
2.2.34.5 Average number of working RRUs for a joint-scheduling UE in the uplink

Counters
Description
1526728345 L.SFN.ULJSch.RR Average number of DBS3900 LTE/

U.Avg working RRUs used BTS3900 LTE/
by joint-scheduling BTS3900A LTE/
Ues in uplink BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the average number of work RRUs for a UE involved in uplink joint
scheduling in an SFN cell. After a UE accesses the network, the number of work RRUs for the
UE is added to this counter. Each time when a UE decides the uplink attribute of an SFN cell,
this counter increases or decreases correspondingly if a UE work RRU set changes. After the
UE exits the network, the number of RRUs for the UE is deducted from this counter.
Measurement Points
The number of working RRUs used by uplink joint-scheduling UEs in an SFN cell is sample
as the value of the counter.
Formula
None
Unit
None
Related Features
L.SFN.ULJSch.RRU.Avg Multi-mode: None

GSM: None
UMTS: None
2.2.34.6 Number of Times When the Uplink Attribute of a UE Changes from

Independent Scheduling to Joint Scheduling in an SFN Cell

Counters
Description
1526728346 L.SFN.User.ULI2J Number of times DBS3900 LTE/

when the uplink BTS3900 LTE/
changes from BTS3900L LTE/
independent- BTS3900AL LTE,
scheduling to joint- BTS3900
scheduling
Description
The counters measures the number of times when the uplink attribute of a UE changes from
independent-scheduling to joint-scheduling
Measurement Points
The counter is incremented by 1 each time the uplink attribute of a UE changes from independent-
scheduling to joint-scheduling.
Formula
None
Unit
None
Related Features
L.SFN.User.ULI2J Multi-mode: None

GSM: None
UMTS: None
2.2.34.7 Number of Times When the Uplink Attribute of a UE Changes from Joint-
scheduling to Independent-scheduling in an SFN cell

Counters
Description
1526728347 L.SFN.User.ULJ2I Number of times DBS3900 LTE/

when the uplink BTS3900 LTE/
changes from joint - BTS3900L LTE/
scheduling to BTS3900AL LTE,
independent- BTS3900
scheduling
Description
The counte measures the number of times when the uplink attribute of a UE changes from joint
-scheduling to independent-scheduling
Measurement Points
The counter is incremented by 1 each time the uplink attribute of a UE changes from joint-
scheduling to independent-scheduling.
Formula
None
Unit
None
Related Features
L.SFN.User.ULJ2I Multi-mode: None

GSM: None
UMTS: None
2.2.34.8 Number of Times that the Uplink Target RRU of a UE in an SFN Cell
Changes

Counters
Description
1526728348 L.SFN.ULTRRU.Ch Number of times that DBS3900 LTE/

g the uplink target BTS3900 LTE/
RRU of a UE in an BTS3900A LTE/
SFN cell changes BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of times that the uplink target RRU of a UE in an SFN cell
changes
Measurement Points
The L.SFN.ULTRRU.Chg couner is incremented by 1 each time the uplink target RRU of a UE
in an SFN cell changes.
Formula
None
Unit
None
Related Features
L.SFN.ULTRRU.Chg Multi-mode: None

GSM: None
UMTS: None
2.2.34.9 Average Number of Joint-scheduling UEs in the Downlink

Counters
Description
1526728384 L.SFN.DLJSch.User Average number of DBS3900 LTE/

.Avg joint-scheduling UEs BTS3900 LTE/
in downlink BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the average number of joint-scheduling UEs in downlink
Measurement Points
The number of downlink joint-scheduling UEs in an SFN cell is sampled per second. At the end
of an measurement period, the average of these sampling results is used as the value of the
counter.
Formula
None
Unit
None
Related Features
L.SFN.DLJSch.User.Avg Multi-mode: None

GSM: None
UMTS: None
2.2.34.10 Average Number of Working RRUs for a Joint-scheduling UE in the

Downlink

Counters
Description
1526728385 L.SFN.DLJSch.RR Average number of DBS3900 LTE/

U.Avg working RRUs used BTS3900 LTE/
by joint-scheduling BTS3900A LTE/
UEs in downlink BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the average number of work RRUs for a UE involved in downlink joint
scheduling in an SFN cell.After a UE accesses the network, the number of work RRUs for the
UE is added to this counter. Each time when a UE decides the downlink attribute of an SFN cell,
this counter increases or decreases correspondingly if a UE work RRU set changes. After the
UE exits the network, the number of work RRUs for the UE is deducted from this counter.
Measurement Points
The number of working RRUs used by downlink joint-scheduling UEs in an SFN cell is sample
as the value of the counter.
Formula
None
Unit
None
Related Features
L.SFN.DLJSch.RRU.Avg Multi-mode: None

GSM: None
UMTS: None

2.2.35 Measurements related to UECNTX Modify

(UeCntx.Mod.Cell)
Overview
UE context contains user-specific context information throughout the network. The context
modification can be caused by modification of information, such as AMBR of a UE, on the
MME side or by a CS fallback procedure. The UE context modification success rate in a cell
represents the UE context modification capability of a cell.
Figure 2-363
Counters
Description
1526728487 L.UECNTX.Modif Number of UE V100R008C00,and

y.Att context modification the mapping single-
attempts mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728488 L.UECNTX.Modif Number of V100R008C00,and

y.Succ successful UE the mapping single-
context mode base station
modifications version that
introduce this
counter is:
eNodeB:V100R006
C00

None
2.2.35.1 Number of UE Context Modification Attempts
Counters
Description
1526728487 L.UECNTX.Modify. Number of UE DBS3900 LTE/

Att context modification BTS3900 LTE/
attempts BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of UE context modification attempts.
Measurement Points
As shown at point A in Figure 2-364, the L.UECNTX.Modify.Att counter is incremented by 1
each time the eNodeB receives a UE CONTEXT MODIFICATION REQUEST message from
the MME.
Figure 2-364

Formula
None
Unit
None
Related Features
L.UECNTX.Modify.Att Multi-mode: None

GSM: None
UMTS: None
2.2.35.2 Number of Successful UE Context Modifications
Counters
Description
1526728488 L.UECNTX.Modify. Number of DBS3900 LTE/

Succ successful UE BTS3900 LTE/
context BTS3900A LTE/
modifications BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of successful UE context modifications.
Measurement Points
As shown at point B in Figure 2-365, the L.UECNTX.Modify.Succ counter is incremented by
1 each time the eNodeB sends a UE CONTEXT MODIFICATION RESPONSE message to the
MME.

Figure 2-365
Formula
None
Unit
None
Related Features
L.UECNTX.Modify.Succ Multi-mode: None

GSM: None
UMTS: None
2.2.36 Measurement related to CA (CA.Cell)
Overview
The CA.Cell function subset measures the service drop rate and handover success rate of CA
UEs in a cell.

Counters
Description

RAB.AbnormRel.C E-RAB releases for the mapping single-
AUser CA UEs mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

RAB.NormRel.CA RAB releases for CA the mapping single-
User UEs mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728518 L.HHO.PrepAttOu Number of PCC V100R008C00,and

t.CAUser.PCC outgoing handover the mapping single-
of CA UEs version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728519 L.HHO.ExecAttOu Number of PCC V100R008C00,and

t.CAUser.PCC outgoing handover the mapping single-
executions of CA mode base station
UEs version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728520 L.HHO.ExecSuccO Number of V100R008C00,and

ut.CAUser.PCC successful PCC the mapping single-
executions of CA version that
UEs introduce this
counter is:
eNodeB:V100R006
C00

None
2.2.36.1 Total Number of Abnormal E-RAB Releases for CA UEs in a Cell
Counters
Description

RAB.AbnormRel.C E-RAB releases for BTS3900 LTE/
AUser CA UEs BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of abnormal E-RAB releases for CA UEs in a cell. An E-RAB
is the access layer bearer for carrying service data of UEs. The E-RAB release is a process of
releasing the access layer bearer resources of UEs. It represents the capability of a cell to release
access layer bearer resources for UEs.
Measurement Points
As shown at point A in Figure 2-366, the eNodeB sends an E-RAB RELEASE INDICATION
message to the MME. The L.E-RAB.AbnormRel.CAUser counter is incremented by 1 each time
the eNodeB determines that the E-RAB to be released carries data and the Release Cause
information element of the message is not "Normal Release", "Detach", "User Inactivity", "CS
Fallback triggered", "UE Not Available For PS Service", or "Inter-RAT Redirection". If the E-
RAB RELEASE INDICATION message requires multiple E-RAB releases at the same time,
the corresponding counter is incremented according to the number of E-RABs.
As shown at point A in Figure 2-367, all E-RABs of the UE are released each time the eNodeB
sends a UE CONTEXT RELEASE REQUEST message to the MME. The L.E-
RAB.AbnormRel.CAUser counter is incremented by 1 each time the eNodeB determines that
the E-RAB to be released carries data and the Release Cause information element of the message
is not "Normal Release", "Detach", "User Inactivity", "CS Fallback triggered", "UE Not
Available For PS Service", "Inter-RAT Redirection", "Time Critical Handover", or "Handover
Cancelled". When the MME sends a UE CONTEXT RELEASE COMMAND message to the
eNodeB, the L.E-RAB.AbnormRel.CAUser counter is not incremented.

Figure 2-366
Figure 2-367
Formula
None
Unit
None

Related Features

RAB.AbnormRel.CAUser GSM: None
UMTS: None
2CC in 20MHz
LAOFD-00100201
Inter-Band Carrier
2CC in 20MHz
2.2.36.2 Total Number of Normal E-RAB Releases for CA UEs in a Cell
Counters
Description

RAB.NormRel.CAU RAB releases for CA BTS3900 LTE/
ser UEs BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of normal E-RAB releases for CA UEs in a cell. An E-RAB
is the access layer bearer for carrying service data of UEs. The E-RAB release is a process of
releasing the access layer bearer resources of UEs. It represents the capability of a cell to release
access layer bearer resources for UEs.
Measurement Points
As shown at point A in Figure 2-368, the eNodeB initiates E-RAB release and sends an E-RAB
RELEASE INDICATION message to the MME. The L.E-RAB.NormRel.CAUser counter is
incremented when either of the following conditions is met: (1) The UE is a CA UE and the
Release Cause IE in the E-RAB RELEASE INDICATION message is "Normal Release",
"Detach", "User Inactivity", "CS Fallback triggered", "UE Not Available For PS Service", or

"Inter-RAT Redirection". (2) The eNodeB determines that no data is transmitted on the
associated E-RAB.
If the E-RAB RELEASE INDICATION message requires multiple E-RAB releases at the same
time, the L.E-RAB.NormRel.CAUser counter is incremented based on the number of E-RABs.
As shown at point A in Figure 2-369, L.E-RAB.NormRel.CAUser counter is incremented when

the MME initiates E-RAB release for a CA UE and the eNodeB receives an E-RAB RELEASE
COMMAND message from the MME. If the E-RAB RELEASE COMMAND message requires
multiple E-RAB releases at the same time, the L.E-RAB.NormRel.CAUser counter is
incremented based on the number of E-RABs.
As shown at point A in Figure 2-370, in the eNodeB-initiated E-RAB release, all E-RABs of a
UE are released when the eNodeB sends a UE CONTEXT RELEASE REQUEST message to
the MME. The L.E-RAB.NormRel.CAUser counter is incremented when either of the following
conditions is met: (1) The UE is a CA UE and the Release Cause IE in the UE CONTEXT
RELEASE REQUEST message is "Normal Release", "Detach", "User Inactivity", "CS Fallback
triggered", "UE Not Available for PS Service", "Inter-RAT Redirection", "Time Critical
Handover", or "Handover Cancelled". (2) The eNodeB determines that no data is transmitted on
the associated E-RAB. The L.E-RAB.NormRel.CAUser counter is incremented based on the
number of E-RABs. When the MME sends a UE CONTEXT RELEASE COMMAND message
to the eNodeB, the L.E-RAB.NormRel.CAUser counter is not incremented.
As shown at point B in Figure 2-370, in the MME-initiated E-RAB release, all E-RABs of a
UE are released, when the eNodeB receives a UE CONTEXT RELEASE COMMAND message
from the MME and the UE is a CA UE. The L.E-RAB.NormRel.CAUser counter is incremented
if the release cause is not "Successful Handover ", "Partial Handover ", "S1 intra system
Handover triggered ", "S1 inter system Handover triggered ", or "X2 Handover triggered ". The
L.E-RAB.NormRel.CAUser counter is incremented based on the number of E-RABs.
Figure 2-368

Figure 2-369
Figure 2-370
Formula
None
Unit
None

Related Features
L.E-RAB.NormRel.CAUser Multi-mode: None

GSM: None
UMTS: None
2CC in 20MHz
LAOFD-00100201
Inter-Band Carrier
2CC in 20MHz
2.2.36.3 Number of Handover Attempts for CA UEs in a Cell
Counters
Description
1526728518 L.HHO.PrepAttOut. Number of PCC DBS3900 LTE/

CAUser.PCC outgoing handover BTS3900 LTE/
of CA UEs BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
attempts of CA UEs.
Measurement Points
As shown at point A in Figure 2-371, the L.HHO.PrepAttOut.CAUser.PCC counter is
incremented by 1 each time the eNodeB determines to perform an intra-eNodeB blind handover
during an intra-eNodeB handover trigger of a CA UE or the eNodeB determines to perform an
intra-eNodeB handover after the serving cell receives a Measurement Report message from the
UE.

incremented by 1 each time the eNodeB determines to perform an X2-based blind handover

during an X2-based handover trigger of a CA UE or the source eNodeB determines to perform

an X2-based handover after the source eNodeB receives a Measurement Report message from
the UE.

incremented by 1 each time the eNodeB determines to perform an S1-based blind handover
during an S1-based handover trigger of a CA UE or the source eNodeB determines to perform
an S1-based handover after the source eNodeB receives a Measurement Report message from
the UE.
Figure 2-371
Figure 2-372

Figure 2-373
Formula
None
Unit
None
Related Features
L.HHO.PrepAttOut.CAUser Multi-mode: None

.PCC GSM: None
UMTS: None
2CC in 20MHz
LAOFD-00100201
Inter-Band Carrier
2CC in 20MHz

2.2.36.4 Number of Handover Executions for CA UEs in a Cell
Counters
Description
1526728519 L.HHO.ExecAttOut. Number of PCC DBS3900 LTE/

CAUser.PCC outgoing handover BTS3900 LTE/
executions of CA BTS3900A LTE/
UEs BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
executions of CA UEs.
Measurement Points
As shown at point B in Figure 2-374, the L.HHO.ExecAttOut.CAUser.PCC counter is
incremented by 1 each time the source eNodeB sends an RRC Connection Reconfiguration
message to the CA UE during intra-eNodeB handover.
L.HHO.ExecAttOut.CAUser.PCC counter is incremented by 1 each time the source eNodeB
sends an RRC Connection Reconfiguration message to the CA UE after the source eNodeB
receives a HANDOVER REQUEST ACKNOWLEDGE message from the target eNodeB.
L.HHO.ExecAttOut.CAUser.PCC counter is incremented by 1 each time the source eNodeB
sends an RRC Connection Reconfiguration message to the CA UE after the source eNodeB
receives a HANDOVER COMMAND from the MME.
Figure 2-374

Figure 2-375
Figure 2-376
Formula
None
Unit
None

Related Features
L.HHO.ExecAttOut.CAUse Multi-mode: None

r.PCC GSM: None
UMTS: None
2CC in 20MHz
LAOFD-00100201
Inter-Band Carrier
2CC in 20MHz
2.2.36.5 Number of Successful Handovers for CA UEs in a Cell
Counters
Description
1526728520 L.HHO.ExecSuccO Number of DBS3900 LTE/

ut.CAUser.PCC successful PCC BTS3900 LTE/
executions of CA BTS3900L LTE/
UEs BTS3900AL LTE,
BTS3900
Description
The counter measures the number of successful intra-eNodeB and inter-eNodeB outgoing
handover executions of CA UEs.
Measurement Points
As shown at point C in Figure 2-377, during an intra-eNodeB handover the
L.HHO.ExecSuccOut.CAUser.PCC counter is incremented by 1 each time data in the buffer is
forwarded after the source cell receives an RRC Connection Reconfiguration Complete message
from the CA UE.

L.HHO.ExecSuccOut.CAUser.PCC counter is incremented by 1 each time the target cell
receives an RRC Connection Reestablishment Complete message from the CA UE.


L.HHO.ExecSuccOut.CAUser.PCC counter is incremented by 1 each time the source cell
receives an RRC Connection Reestablishment Complete message from the CA UE.
As shown at point C in Figure 2-379, during an X2-based inter-eNodeB handover the

forwarded after the source eNodeB receives a UE CONTEXT RELEASE message from the
target eNodeB.
As shown at point C in Figure 2-380, during an X2-based handover, after the RRC connection
to the target eNodeB for a CA UE is reestablished, the L.HHO.ExecSuccOut.CAUser.PCC
counter is incremented by 1 each time data in the buffer is forwarded after the source eNodeB
receives a UE CONTEXT RELEASE message from the target eNodeB.

forwarded after the source eNodeB receives a UE CONTEXT RELEASE COMMAND message
from the MME.
As shown at point C in Figure 2-382, during an S1-based handover, after the RRC connection
to the target eNodeB for a CA UE is reestablished, the L.HHO.ExecSuccOut.CAUser.PCC
counter is incremented by 1 each time data in the buffer is forwarded after the source eNodeB
receives a UE CONTEXT RELEASE COMMAND message from the MME.
As shown at point C in Figure 2-383, during an X2-based handover, the

L.HHO.ExecSuccOut.CAUser.PCC counter is incremented by 1 each time the RRC connection
to the source eNodeB for a CA UE is reestablished.

L.HHO.ExecSuccOut.CAUser.PCC counter is incremented by 1 each time the RRC connection
to the source eNodeB for a CA UE is reestablished.
Figure 2-377

Figure 2-378
Figure 2-379

Figure 2-380
Figure 2-381

Figure 2-382

Figure 2-383

Figure 2-384
Formula
None
Unit
None

Related Features
L.HHO.ExecSuccOut.CAUs Multi-mode: None

er.PCC GSM: None
UMTS: None
2CC in 20MHz
LAOFD-00100201
Inter-Band Carrier
2CC in 20MHz
2.2.37 Measurement related to RLC (Traffic.RLC.Cell)
Overview
The Traffic.RLC.Cell function subset measures the numbers of retransmitted packets, discarded
packets, total packets, and retransmitted bytes in AM mode at the RLC layer in a cell.
Counters
Description
1526728672 L.Traffic.UL.AM. Number of bits of V100R008C00,and

Retrans.bits uplink RLC PDUs the mapping single-
retransmitted in AM mode base station
mode (including version that
multiple introduce this
retransmissions) in a counter is:
C00
1526728673 L.Traffic.DL.AM. Number of bits of V100R008C00,and

Retrans.bits downlink RLC PDUs the mapping single-
C00


Description
1526728674 L.Traffic.UL.AM. Number of uplink V100R008C00,and

RxPackets RLC PDUs received the mapping single-
in AM mode mode base station
(including multiple version that
retransmissions) in a introduce this
cell counter is:
eNodeB:V100R006
C00
1526728675 L.Traffic.DL.AM.T Number of downlink V100R008C00,and

xPackets RLC PDUs the mapping single-
transmitted in AM mode base station
C00
1526728676 L.Traffic.UL.AM. Number of uplink V100R008C00,and

Retrans.RxPackets RLC PDUs received the mapping single-
in AM mode mode base station
(including multiple version that
retransmissions) introduce this
retransmitted by UEs counter is:
in a cell eNodeB:V100R006
C00
1526728677 L.Traffic.DL.AM. Number of downlink V100R008C00,and

Retrans.TxPackets RLC PDUs the mapping single-
C00
1526728678 L.Traffic.DL.AM.T Number of downlink V100R008C00,and

xDropPackets RLC PDUs failed to the mapping single-
be sent to UEs in AM mode base station
mode in a cell version that
introduce this
counter is:
eNodeB:V100R006
C00
None

2.2.37.1 Number of Bits of Uplink RLC ARQ PDUs Retransmitted by UEs
Counters
Description
1526728672 L.Traffic.UL.AM.R Number of bits of DBS3900 LTE/

etrans.bits uplink RLC PDUs BTS3900 LTE/
retransmitted in AM BTS3900A LTE/
mode (including BTS3900L LTE/
multiple BTS3900AL LTE,
retransmissions) in a BTS3900
cell
Description
The volume of retransmitted data at the RLC layer in AM mode is influenced by the channel
quality. The counter measures the total bits of retransmitted uplink RLC PDUs in AM mode.
The counter value is used to analyze the radio resources used for retransmission.
Measurement Points
The number of bits of retransmitted RLC PDUs in AM mode received from UEs in a cell is
sampled in a measurement period. At the end of a measurement period, the sum of these sampling
results is used as the value of the L.Traffic.UL.AM.Retrans.bits counter.
Formula
None
Unit
bit
Related Features
L.Traffic.UL.AM.Retrans.bi Multi-mode: None

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

2.2.37.2 Number of Bits of Downlink RLC ARQ PDUs Retransmitted by the

eNodeB
Counters
Description
1526728673 L.Traffic.DL.AM.R Number of bits of DBS3900 LTE/

etrans.bits downlink RLC PDUs BTS3900 LTE/
cell
Description
quality. The counter measures the total bits of retransmitted downlink RLC PDUs in AM mode.
Measurement Points
The number of bits of retransmitted RLC PDUs in AM mode sent to UEs in a cell is sampled in
a measurement period. At the end of a measurement period, the sum of these sampling results
is used as the value of the L.Traffic.DL.AM.Retrans.bits counter.
Formula
None
Unit
bit
Related Features
L.Traffic.DL.AM.Retrans.bi Multi-mode: None

ts GSM: None
UMTS: None

2.2.37.3 Number of Received Uplink RLC ARQ PDUs
Counters
Description
1526728674 L.Traffic.UL.AM.R Number of uplink DBS3900 LTE/

xPackets RLC PDUs received BTS3900 LTE/
in AM mode BTS3900A LTE/
(including multiple BTS3900L LTE/
retransmissions) in a BTS3900AL LTE,
cell BTS3900
Description
quality. The counter measures the total number of uplink RLC PDUs in AM mode. The counter
value is used to compare with the data traffic.
Measurement Points
The number of RLC PDUs received in AM mode from UEs in a cell is sampled in a measurement
period. At the end of a measurement period, the sum of these sampling results is used as the
value of the L.Traffic.UL.AM.RxPackets counter. The resegmented RLC PDUs are also counted
in the counter.
Formula
None
Unit
packet
Related Features
L.Traffic.UL.AM.RxPackets Multi-mode: None

GSM: None
UMTS: None
2.2.37.4 Number of Transmitted Downlink RLC ARQ PDUs

Counters
Description
1526728675 L.Traffic.DL.AM.T Number of downlink DBS3900 LTE/

xPackets RLC PDUs BTS3900 LTE/
transmitted in AM BTS3900A LTE/
cell
Description
quality. The counter measures the total number of downlink RLC PDUs in AM mode. The
counter value is used to compare with the data traffic.
Measurement Points
The number of RLC PDUs sent in AM mode to UEs in a cell is sampled in a measurement period.
the L.Traffic.DL.AM.TxPackets counter. The resegmented RLC PDUs are also counted in the
counter.
Formula
None
Unit
packet
Related Features
L.Traffic.DL.AM.TxPackets Multi-mode: None

GSM: None
UMTS: None
2.2.37.5 Number of Received Uplink RLC ARQ PDUs Retransmitted by UEs

Counters
Description
1526728676 L.Traffic.UL.AM.R Number of uplink DBS3900 LTE/

etrans.RxPackets RLC PDUs received BTS3900 LTE/
in AM mode BTS3900A LTE/
(including multiple BTS3900L LTE/
retransmissions) BTS3900AL LTE,
retransmitted by UEs BTS3900
in a cell
Description
quality. The counter measures the total number of retransmitted uplink RLC PDUs in AM mode.
Measurement Points
The total number of retransmitted RLC PDUs in AM mode received from UEs in a cell is sampled
in a measurement period. At the end of a measurement period, the sum of these sampling results
is used as the value of the L.Traffic.UL.AM.Retrans.RxPackets counter. The resegmented RLC
PDUs are also counted in the counter.
Formula
None
Unit
packet
Related Features
L.Traffic.UL.AM.Retrans.R Multi-mode: None

xPackets GSM: None
UMTS: None
2.2.37.6 Number of Downlink RLC ARQ PDUs Retransmitted by UEs

Counters
Description
1526728677 L.Traffic.DL.AM.R Number of downlink DBS3900 LTE/

etrans.TxPackets RLC PDUs BTS3900 LTE/
cell
Description
quality. The counter measures the total number of retransmitted downlink RLC PDUs in AM
mode. The counter value is used to analyze the radio resources used for retransmission.
Measurement Points
The total number of retransmitted RLC PDUs in AM mode sent to UEs in a cell is sampled in
a measurement period. At the end of a measurement period, the sum of these sampling results
is used as the value of the L.Traffic.DL.AM.Retrans.TxPackets counter. The resegmented RLC
PDUs are also counted in the counter.
Formula
None
Unit
packet
Related Features
L.Traffic.DL.AM.Retrans.T Multi-mode: None

xPackets GSM: None
UMTS: None
2.2.37.7 Number of Downlink RLC PDUs Failed to Be Sent to UEs in AM Mode in

a Cell

Counters
Description
1526728678 L.Traffic.DL.AM.T Number of downlink DBS3900 LTE/

xDropPackets RLC PDUs failed to BTS3900 LTE/
be sent to UEs in AM BTS3900A LTE/
mode in a cell BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
quality. The counter measures the number of downlink RLC PDUs that fail to be sent to UEs
after retransmission and are discarded in a cell.
Measurement Points
The total number of downlink RLC PDUs failed to be sent to UEs after retransmission in AM
mode in a cell is sampled in a measurement period. At the end of a measurement period, the sum
of these sampling results is used as the value of the L.Traffic.DL.AM.TxDropPackets counter.
Formula
None
Unit
packet
Related Features
L.Traffic.DL.AM.TxDrop- Multi-mode: None

Packets GSM: None
UMTS: None
2.2.38 Measurement related to Reserve Cell (Reserve.Cell)
Overview
The Reserve.Cell function subset is reserved.

Counters
Description
1526728712 L.Reserve.1 L.Reserve.1 V100R008C00,and

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00


Description

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00

the mapping single-
mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
None

2.2.38.1 L.Reserve.1
Counters
Description
1526728712 L.Reserve.1 L.Reserve.1 DBS3900 LTE/

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.1
Measurement Points
L.Reserve.1
Formula
None
Unit
None
Related Features
None
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
L.Reserve.2
Measurement Points
L.Reserve.2
Formula
None
Unit
None
Related Features
None
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.3
Measurement Points
L.Reserve.3
Formula
None
Unit
None

Related Features
None
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.4
Measurement Points
L.Reserve.4
Formula
None
Unit
None
Related Features
None

Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.5
Measurement Points
L.Reserve.5
Formula
None
Unit
None
Related Features
None
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
L.Reserve.6
Measurement Points
L.Reserve.6
Formula
None
Unit
None
Related Features
None
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.7
Measurement Points
L.Reserve.7
Formula
None
Unit
None

Related Features
None
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.8
Measurement Points
L.Reserve.8
Formula
None
Unit
None
Related Features
None

Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.9
Measurement Points
L.Reserve.9
Formula
None
Unit
None
Related Features
None
2.2.38.10 L.Reserve.10
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
L.Reserve.10
Measurement Points
L.Reserve.10
Formula
None
Unit
None
Related Features
None
2.2.38.11 L.Reserve.11
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.11
Measurement Points
L.Reserve.11
Formula
None
Unit
None

Related Features
None
2.2.38.12 L.Reserve.12
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.12
Measurement Points
L.Reserve.12
Formula
None
Unit
None
Related Features
None
2.2.38.13 L.Reserve.13

Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.13
Measurement Points
L.Reserve.13
Formula
None
Unit
None
Related Features
None
2.2.38.14 L.Reserve.14
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
L.Reserve.14
Measurement Points
L.Reserve.14
Formula
None
Unit
None
Related Features
None
2.2.38.15 L.Reserve.15
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.15
Measurement Points
L.Reserve.15
Formula
None
Unit
None

Related Features
None
2.2.38.16 L.Reserve.16
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.16
Measurement Points
L.Reserve.16
Formula
None
Unit
None
Related Features
None
2.2.38.17 L.Reserve.17

Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.17
Measurement Points
L.Reserve.17
Formula
None
Unit
None
Related Features
None
2.2.38.18 L.Reserve.18
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
L.Reserve.18
Measurement Points
L.Reserve.18
Formula
None
Unit
None
Related Features
None
2.2.38.19 L.Reserve.19
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.19
Measurement Points
L.Reserve.19
Formula
None
Unit
None

Related Features
None
2.2.38.20 L.Reserve.20
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.20
Measurement Points
L.Reserve.20
Formula
None
Unit
None
Related Features
None
2.2.38.21 L.Reserve.21

Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.21
Measurement Points
L.Reserve.21
Formula
None
Unit
None
Related Features
None
2.2.38.22 L.Reserve.22
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
L.Reserve.22
Measurement Points
L.Reserve.22
Formula
None
Unit
None
Related Features
None
2.2.38.23 L.Reserve.23
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.23
Measurement Points
L.Reserve.23
Formula
None
Unit
None

Related Features
None
2.2.38.24 L.Reserve.24
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.24
Measurement Points
L.Reserve.24
Formula
None
Unit
None
Related Features
None
2.2.38.25 L.Reserve.25

Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.25
Measurement Points
L.Reserve.25
Formula
None
Unit
None
Related Features
None
2.2.38.26 L.Reserve.26
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
L.Reserve.26
Measurement Points
L.Reserve.26
Formula
None
Unit
None
Related Features
None
2.2.38.27 L.Reserve.27
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.27
Measurement Points
L.Reserve.27
Formula
None
Unit
None

Related Features
None
2.2.38.28 L.Reserve.28
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.28
Measurement Points
L.Reserve.28
Formula
None
Unit
None
Related Features
None
2.2.38.29 L.Reserve.29

Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
L.Reserve.29
Measurement Points
L.Reserve.29
Formula
None
Unit
None
Related Features
None
2.2.38.30 L.Reserve.30
Counters
Description

BTS3900 LTE/
BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
L.Reserve.30
Measurement Points
L.Reserve.30
Formula
None
Unit
None
Related Features
None
2.2.39 Measurement related to CellComb (CellComb.Cell)
Overview
The CellComb.Cell function subset measures the used resources and number of scheduled
resources in a combined cell, indicating the operating status of the combined cell.
Counters
Description
1526728695 L.CellComb.DLJSc Number of downlink V100R008C00,and

h.User.Avg joint-scheduling UEs the mapping single-
in a combination cell mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728696 L.CellComb.DLJSc Average number of V100R008C00,and

h.PhyCell.Avg work physical cells the mapping single-
of downlink joint- mode base station
scheduling UEs in a version that
combination cell introduce this
counter is:
eNodeB:V100R006
C00


Description
1526728697 L.CellComb.User. Number of Times an V100R008C00,and

DLI2J Independent- the mapping single-
scheduling UE mode base station
Becomes a Joint- version that
scheduling UE in introduce this
Downlink in a counter is:
Combination Cell eNodeB:V100R006
C00
1526728698 L.CellComb.User. Number of times a V100R008C00,and

DLJ2I joint-scheduling UE the mapping single-
becomes an mode base station
independent- version that
downlink in a counter is:
combination cell eNodeB:V100R006
C00
1526728699 L.CellComb.DLTP Number of times the V100R008C00,and

hyCell.Chg downlink target the mapping single-
physical cell of a UE mode base station
in a combination cell version that
changes in a introduce this
combination cell counter is:
eNodeB:V100R006
C00
1526728700 L.CellComb.ULJSc Number of uplink V100R008C00,and

h.User.Avg joint-scheduling UEs the mapping single-
in a combination cell mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728701 L.CellComb.ULJSc Average number of V100R008C00,and

h.PhyCell.Avg work physical cells the mapping single-
of uplink joint- mode base station
scheduling UEs in a version that
combination cell in a introduce this
eNodeB:V100R006
C00


Description
1526728702 L.CellComb.User. Number of times an V100R008C00,and

ULI2J independent- the mapping single-
scheduling UE mode base station
becomes a joint- version that
uplink in a counter is:
C00
1526728703 L.CellComb.User. Number of times a V100R008C00,and

ULJ2I joint-scheduling UE the mapping single-
becomes an mode base station
independent- version that
uplink in a counter is:
C00
1526728704 L.CellComb.ULTP Number of times the V100R008C00,and

hyCell.Chg uplink target the mapping single-
physical cell of a UE mode base station
in a combination cell version that
changes in a introduce this
eNodeB:V100R006
C00
None
2.2.39.1 Number of Downlink Joint-scheduling UEs in a Combination Cell
Counters
Description
1526728695 L.CellComb.DLJSc Number of downlink DBS3900 LTE/

h.User.Avg joint-scheduling UEs BTS3900 LTE/
in a combination cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
This counter measures the number of downlink joint-scheduling UEs in a combination cell.
Measurement Points
The number of downlink joint-scheduling UEs in a combination cell is sampled per second. At
the end of a measurement period, the average of these sampling results is used as the value of
the counter.
Formula
None
Unit
None
Related Features
None
2.2.39.2 Average Number of Work Physical Cells of Downlink Joint-scheduling

UEs in a Combination Cell
Counters
Description
1526728696 L.CellComb.DLJSc Average number of DBS3900 LTE/

h.PhyCell.Avg work physical cells BTS3900 LTE/
of downlink joint- BTS3900A LTE/
scheduling UEs in a BTS3900L LTE/
combination cell BTS3900AL LTE,
BTS3900
Description
This counter measures the average number of work physical cells of downlink joint-scheduling
UEs in a combination cell. The number of work physical cells of downlink joint-scheduling UEs
is calculated by adding the measurement result to the number of cells in the work cell set of the
UE after the UE accesses the network. Each time a UE decides the downlink attribute of a
combination cell, this counter increases or decreases correspondingly if the UE work physical
cell set changes. After the UE exits the network, the number of cells in the work cell set for the
UE is deducted from this counter.

Measurement Points
The average number of work physical cells per downlink joint-scheduling UE in a combination
cell is sampled per second. At the end of a measurement period, the average of these sampling
results is used as the value of the L.CellComb.DLJSch.PhyCell.Avg counter
Formula
None
Unit
None
Related Features
None
2.2.39.3 Number of Times an Independent-scheduling UE Becomes a Joint-

scheduling UE in Downlink in a Combination Cell
Counters
Description
1526728697 L.CellComb.User.D Number of Times an DBS3900 LTE/

LI2J Independent- BTS3900 LTE/
scheduling UE BTS3900A LTE/
Becomes a Joint- BTS3900L LTE/
scheduling UE in BTS3900AL LTE,
Downlink in a BTS3900
Combination Cell
Description
This counter measures the number of times the downlink attribute of a UE changes from
independent scheduling to joint scheduling in a combination cell.
Measurement Points
The L.CellComb.User.DLI2J counter is incremented by 1 each time the downlink attribute of a
UE changes from independent scheduling to joint scheduling in a combination cell.
Formula
None

Unit
None
Related Features
None
2.2.39.4 Number of Times a Joint-scheduling UE Becomes an Independent-

scheduling UE in Downlink in a Combination Cell
Counters
Description
1526728698 L.CellComb.User.D Number of times a DBS3900 LTE/

LJ2I joint-scheduling UE BTS3900 LTE/
becomes an BTS3900A LTE/
independent- BTS3900L LTE/
downlink in a BTS3900
combination cell
Description
This counter measures the number of times the downlink attribute of a UE changes from joint
scheduling to independent scheduling in a combination cell.
Measurement Points
The L.CellComb.User.DLJ2I counter is incremented by 1 each time the downlink attribute of a
UE changes from joint scheduling to independent scheduling in a combination cell
Formula
None
Unit
None
Related Features
None
2.2.39.5 Number of Times the Downlink Target Physical Cell of a UE in a

Combination Cell Changes in a Combination Cell

Counters
Description
1526728699 L.CellComb.DLTPh Number of times the DBS3900 LTE/

yCell.Chg downlink target BTS3900 LTE/
physical cell of a UE BTS3900A LTE/
in a combination cell BTS3900L LTE/
changes in a BTS3900AL LTE,
combination cell BTS3900
Description
This counter measures the number of times the downlink target physical cell of a UE in a
combination cell changes.
Measurement Points
The L.CellComb.DLTPhyCell.Chg counter is incremented by 1 each time the downlink target
physical cell of a UE in a combination cell changes.
Formula
None
Unit
None
Related Features
None
2.2.39.6 Number of Uplink Joint-scheduling UEs in a Combination Cell
Counters
Description
1526728700 L.CellComb.ULJSc Number of uplink DBS3900 LTE/

h.User.Avg joint-scheduling UEs BTS3900 LTE/
in a combination cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
This counter measures the number of uplink joint-scheduling UEs in a combination cell.
Measurement Points
The number of uplink joint-scheduling UEs in a combination cell is sampled per second. At the
counter.
Formula
None
Unit
None
Related Features
None
2.2.39.7 Average Number of Work Physical Cells of Uplink Joint-scheduling UEs

in a Combination Cell in a Combination Cell
Counters
Description
1526728701 L.CellComb.ULJSc Average number of DBS3900 LTE/

h.PhyCell.Avg work physical cells BTS3900 LTE/
of uplink joint- BTS3900A LTE/
scheduling UEs in a BTS3900L LTE/
combination cell in a BTS3900AL LTE,
Description
This counter measures the average number of work physical cells of uplink joint-scheduling
UEs in a combination cell. The number of work physical cells of uplink joint-scheduling UEs
is calculated by adding the measurement result to the number of cells in the work cell set of the
UE after the UE accesses the network. Each time a UE decides the uplink attribute of a
combination cell, this counter increases or decreases correspondingly if the UE work physical
cell set changes. After the UE exits the network, the number of cells in the work cell set for the
UE is deducted from this counter.

Measurement Points
The average number of work physical cells per uplink joint-scheduling UE in a combination cell
is sampled per second. At the end of a measurement period, the average of these sampling results
is used as the value of the L.CellComb.ULJSch.PhyCell.Avg counter.
Formula
None
Unit
None
Related Features
None
2.2.39.8 Number of Times an Independent-scheduling UE Becomes a Joint-

scheduling UE in Uplink in a Combination cell
Counters
Description
1526728702 L.CellComb.User.U Number of times an DBS3900 LTE/

LI2J independent- BTS3900 LTE/
scheduling UE BTS3900A LTE/
becomes a joint- BTS3900L LTE/
uplink in a BTS3900
combination cell
Description
This counter measures the number of times the uplink attribute of a UE changes from independent
scheduling to joint scheduling in a combination cell.
Measurement Points
The L.CellComb.User.ULI2J counter is incremented by 1 each time the uplink attribute of a UE
changes from independent scheduling to joint scheduling in a combination cell.
Formula
None

Unit
None
Related Features
None
2.2.39.9 Number of Times a Joint-scheduling UE Becomes an Independent-

scheduling UE in Uplink in a Combination Cell
Counters
Description
1526728703 L.CellComb.User.U Number of times a DBS3900 LTE/

LJ2I joint-scheduling UE BTS3900 LTE/
becomes an BTS3900A LTE/
independent- BTS3900L LTE/
uplink in a BTS3900
combination cell
Description
This counter measures the number of times the uplink attribute of a UE changes from joint
scheduling to independent scheduling in a combination cell.
Measurement Points
The L.CellComb.User.ULJ2I counter is incremented by 1 each time the uplink attribute of a UE
changes from joint scheduling to independent scheduling in a combination cell.
Formula
None
Unit
None
Related Features
None
2.2.39.10 Number of Times the Uplink Target Physical Cell of a UE in a

Combination Cell Changes in a Combination Cell

Counters
Description
1526728704 L.CellComb.ULTPh Number of times the DBS3900 LTE/

yCell.Chg uplink target BTS3900 LTE/
physical cell of a UE BTS3900A LTE/
in a combination cell BTS3900L LTE/
changes in a BTS3900AL LTE,
Description
This counter measures the number of times the uplink target physical cell of a UE in a
combination cell changes.
Measurement Points
The L.CellComb.ULTPhyCell.Chg counter is incremented by 1 each time the uplink target
physical cell of a UE in a combination cell changes.
Formula
None
Unit
None
Related Features
None
2.2.40 Measurement related to Measure Reports

(ChMeas.MeasRpt.Cell)
Overview
The ChMeas.MeasRpt.Cell function subset measures the number of measurement controls in a
cell.

Counters
Description
1526728742 L.MeasCtrl.WCD Number of V100R008C00,and

MA.Add measurement control the mapping single-
messages delivered mode base station
to WCDMA network version that
triggered by poor introduce this
coverage in a cell counter is:
eNodeB:V100R005
C00
1526728743 L.MeasCtrl.GERA Number of V100R008C00,and

N.Add measurement control the mapping single-
messages delivered mode base station
to GERAN triggered version that
by poor coverage in a introduce this
cell counter is:
eNodeB:V100R005
C00
None
2.2.40.1 Number of Measurement Control Messages Sent by the eNodeB in a Cell
Counters
Description
1526728742 L.MeasCtrl.WCDM Number of DBS3900 LTE/

A.Add measurement control BTS3900 LTE/
messages delivered BTS3900A LTE/
to WCDMA network BTS3900L LTE/
triggered by poor BTS3900AL LTE,
coverage in a cell BTS3900
1526728743 L.MeasCtrl.GERAN Number of DBS3900 LTE/

.Add measurement control BTS3900 LTE/
messages delivered BTS3900A LTE/
to GERAN triggered BTS3900L LTE/
by poor coverage in a BTS3900AL LTE,
cell BTS3900

Description
The counter measures the number of measurement control messages triggered by poor coverage
during inter-RAT measurement in a cell.
Measurement Points
As shown at point A in Figure 2-385, the eNodeB sends the UE a measurement control message
RRC Connection Reconfiguration due to poor coverage, and this message contains the
information element "MeasConfig". The L.MeasCtrl.WCDMA.Add counter is incremented by
1 each time the information element list measIdToAddModList contains any information
element measID dedicated to WCDMA network. The L.MeasCtrl.GERAN.Add counter is
incremented by 1 each time the information element list measIdToAddModList contains any
information element measID dedicated to GERAN.
Figure 2-385
Formula
None
Unit
None
Related Features
L.MeasCtrl.WCDMA.Add Multi-mode: None

GSM: None
UMTS: None
UTRAN
between E-UTRAN and
UTRAN

L.MeasCtrl.GERAN.Add Multi-mode: None

GSM: None
UMTS: None
GERAN
between E-UTRAN and
GERAN
2.2.41 Measurement related to UECNTX establish (UeCntx.Est.Cell)
Overview
UE context contains user-specific context information throughout the network. The success rate
of the UE context setup represents the capability of a cell to set up UE contexts. The
UECNTX.Est.Cell function subset measures the number of UE context setups in a cell. The
counter is incremented by 1 each time the UE context is set up. The measurement points in a
UE context setup process is shown in Figure 2-386.
Figure 2-386

Counters
Description
1526728850 L.UECNTX.AttEst Number of UE V100R008C00,and

context setup the mapping single-
attempts mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728851 L.UECNTX.SuccE Number of V100R008C00,and

st successful UE the mapping single-
context setups mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
None
2.2.41.1 Number of UE Context Setup Attempts in a Cell
Counters
Description
1526728850 L.UECNTX.AttEst Number of UE DBS3900 LTE/

context setup BTS3900 LTE/
attempts BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of UE context setup attempts in a cell.

Measurement Points
receives the INITIAL CONTEXT SETUP REQUEST message from the MME. Even if the
message contains multiple E-RABs, the counter is incremented only once.
Figure 2-387
Formula
None
Unit
None

Related Features
L.UECNTX.AttEst Multi-mode: None

GSM: None
UMTS: None
2.2.41.2 Number of Successful UE Context Setups in a Cell
Counters
Description
1526728851 L.UECNTX.SuccEst Number of DBS3900 LTE/

successful UE BTS3900 LTE/
context setups BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
This counter measures the number of successful UE context setups in a cell.
Measurement Points
As shown at point B in Figure 2-388, the counter is incremented by 1 each time the eNodeB
sends the INITIAL CONTEXT SETUP RESPONSE message to the MME. Even if the message
contains multiple E-RABs, the counter is incremented only once.

Figure 2-388
Formula
None
Unit
None
Related Features
L.UECNTX.SuccEst Multi-mode: None

GSM: None
UMTS: None

2.2.42 Measurement related to UECNTX establish failure

(UeCntx.EstFail.Cell)
Overview
UE context contains user-specific context information throughout the network. The success rate
of the UE context setup represents the capability of a cell to set UE contexts. The
UECNTX.EstFail.Cell function subset measures the number of UE context setup failures due
to different causes. The counter is incremented by 1 each time the UE context setup fails. The
measurement points in a UE context setup failure process is shown in Figure 2-389.
Figure 2-389
Counters
Description
1526728852 L.UECNTX.FailEs Number of initial V100R008C00,and

t.RNL context setup failures the mapping single-
due to faults at the mode base station
radio network layer version that
introduce this
counter is:
eNodeB:V100R006
C00


Description

t.SecurModeFail context setup failures the mapping single-
due to the security mode base station
mode configuration version that
failure introduce this
counter is:
eNodeB:V100R006
C00

t.NoRadioRes context setup failures the mapping single-
due to insufficient mode base station
radio resources version that
introduce this
counter is:
eNodeB:V100R006
C00

t.UeNoReply context setup failures the mapping single-
due to no response mode base station
from the UE version that
introduce this
counter is:
eNodeB:V100R006
C00
Counter Sub Counter
L.UECNTX.FailEst.RNL L.UECNTX.FailEst.SecurModeFail
L.UECNTX.FailEst.NoRadioRes
L.UECNTX.FailEst.UeNoReply
2.2.42.1 Number of UE Context Setup Failures for Different Causes in a Cell

Counters
Description
1526728852 L.UECNTX.FailEst. Number of initial DBS3900 LTE/

RNL context setup failures BTS3900 LTE/
due to faults at the BTS3900A LTE/
radio network layer BTS3900L LTE/
BTS3900AL LTE,
BTS3900

SecurModeFail context setup failures BTS3900 LTE/
due to the security BTS3900A LTE/
mode configuration BTS3900L LTE/
failure BTS3900AL LTE,
BTS3900

NoRadioRes context setup failures BTS3900 LTE/
due to insufficient BTS3900A LTE/
radio resources BTS3900L LTE/
BTS3900AL LTE,
BTS3900

UeNoReply context setup failures BTS3900 LTE/
due to no response BTS3900A LTE/
from the UE BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counters measure the number of UE context setup failures due to different causes in a cell.
The measurement of the counters reflect different causes of UE context setup failures.
Measurement Points
The corresponding counter is incremented if the context setup fails due to a cause such as a fault
at the radio network layer, radio resource allocation failure, security mode configuration failure,
or no response from the UE. The counters are measured as follows:
As shown at point A in Figure 2-390, after receiving the INITIAL CONTEXT SETUP
REQUEST message from the MME, the eNodeB starts initial context setup. If the UE context
setup fails, the eNodeB sends the INITIAL CONTEXT SETUP FAILURE message to the MME
and a corresponding counter is incremented based on the failure cause. The L.E-
UECNTX.FailEst.RNL counter is incremented by 1 each time the UE context setup failure is
caused by faults at the radio network layer. For details, see 3GPP TS36.413. The
L.UECNTX.FailEst.NoRadioRes counter is incremented if the UE context setup failure is
caused by insufficient radio resources. The measurement of the L.UECNTX.FailEst.RNL

counter includes the measurement of the L.UECNTX.FailEst.NoRadioRes,

L.UECNTX.FailEst.SecurModeFail, and L.UECNTX.FailEst.NoReply counters.
As shown at point A in Figure 2-391, the L.UECNTX.FailEst.SecurModeFail counter is

incremented by 1 each time the eNodeB receives the Security Mode Failure message from the
UE. Before that, the eNodeB has received the INITIAL CONTEXT SETUP REQUEST message
from the MME and sent the Security Mode Command message to the UE.
As shown at points A, B, and C in Figure 2-392, the L.UECNTX.FailEst.NoReply counter is

incremented by 1 each time the UE does not respond to the eNodeB before the timer expires
after the eNodeB sends the RRC Connection Setup message to the UE and the context setup
fails.
Figure 2-390

Figure 2-391

Figure 2-392
Formula
None
Unit
None
Related Features
L.UECNTX.FailEst.RNL Multi-mode: None

GSM: None
UMTS: None

L.UECNTX.FailEst.Secur- Multi-mode: None

ModeFail GSM: None
UMTS: None
L.UECNTX.FailEst.NoRa- Multi-mode: None

dioRes GSM: None
UMTS: None
L.UECNTX.FailEst.Ue- Multi-mode: None

NoReply GSM: None
UMTS: None
2.2.43 Measurement related to Intra eRan X2 HOIN

(HO.eRAN.X2In.Cell)
Overview
The HO.eRAN.X2In.Cell function subset measures the performance of X2-based intra-
frequency and X2-based inter-frequency incoming handovers over the X2 interface in a cell, as
shown in Figure 2-393.
Figure 2-393

Counters
Description
1526728885 L.HHO.X2.PrepAt- Number of X2-based V100R008C00,and

tIn incoming handover the mapping single-
attempts in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728886 L.HHO.X2.ExecAt- Number of X2-based V100R008C00,and

tIn incoming handover the mapping single-
executions in a cell mode base station
version that
introduce this
counter is:
eNodeB:V100R006
C00
1526728887 L.HHO.X2.Exe- Number of V100R008C00,and

cSuccIn successful X2-based the mapping single-
incoming handovers mode base station
introduce this
counter is:
eNodeB:V100R006
C00
None
2.2.43.1 Number of X2-based Incoming Handover Attempts in a Cell
Counters
Description
1526728885 L.HHO.X2.PrepAt- Number of X2-based DBS3900 LTE/

tIn incoming handover BTS3900 LTE/
attempts in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900

Description
The counter measures the number of X2-based incoming handover attempts in a cell.
Measurement Points
As shown at point A in Figure 2-394, the L.HHO.X2.PrepAttIn counter is incremented by 1 in
the target cell each time the target eNodeB receives a HANDOVER REQUEST message from
the source eNodeB over the X2-interface.
Figure 2-394
Formula
None
Unit
None

Related Features
L.HHO.X2.PrepAttIn Multi-mode: None

GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.43.2 Number of X2-based Incoming Handover Executions in a Cell
Counters
Description
1526728886 L.HHO.X2.ExecAt- Number of X2-based DBS3900 LTE/

tIn incoming handover BTS3900 LTE/
executions in a cell BTS3900A LTE/
BTS3900L LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of X2-based incoming handover executions in a cell.
Measurement Points
As shown at point B in Figure 2-395, the L.HHO.X2.ExecAttIn counter is incremented by 1 in
the target cell each time the target eNodeB sends a HANDOVER REQUEST ACKNOWLEDGE
message to the source eNodeB over the X2-interface.

Figure 2-395
Formula
None
Unit
None
Related Features
L.HHO.X2.ExecAttIn Multi-mode: None

GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.43.3 Number of Successful X2-based Incoming Handovers in a Cell

Counters
Description
1526728887 L.HHO.X2.Exe- Number of DBS3900 LTE/

cSuccIn successful X2-based BTS3900 LTE/
incoming handovers BTS3900A LTE/
BTS3900AL LTE,
BTS3900
Description
The counter measures the number of successful X2-based incoming handovers in a cell.
Measurement Points
As shown at point C in Figure 2-396, during an X2-based handover the L.HHO.X2.ExecSuccIn
counter is incremented by 1 each time the target eNodeB receives a PATH SWITCH REQUEST
ACKNOWLEDGE message from the MME and sends a UE CONTEXT RELEASE message
to the source eNodeB over the X2-interface.
As shown at point E in Figure 2-397, after an RRC connection is reestablished to the target
eNodeB for the UE during an X2-based handover, the L.HHO.X2.ExecSuccIn counter is
incremented by 1 each time the target eNodeB receives a PATH SWITCH REQUEST
ACKNOWLEDGE message from the MME and sends a UE CONTEXT RELEASE message
to the source eNodeB over the X2-interface.
Figure 2-396

Figure 2-397
Formula
None
Unit
None

Related Features
L.HHO.X2.ExecSuccIn Multi-mode: None

GSM: None
UMTS: None

frequency Handover
TDLBFD-00201802
frequency Handover
frequency Handover
2.2.44 Measurement related to Thruput Distribution

(Traffic.Thruput.PDF.Cell)
Overview
The Traffic.Thruput.PDF.Cell function subset measures the Throughput of services per QCI
within a measurement period. According to the Throughput distribution, a probability density
function (PDF) is generated and helps the network-level performance evaluation.
Counters
Description
1526729056 L.Thrp.DL.BitRate Number of samples V100R008C00,and

.Samp.Index0 with the downlink the mapping single-
throughput ranging mode base station
from 0 to 512 Kbit/s version that
(excluding 0 and 512 introduce this
Kbit/s) counter is:
eNodeB:V100R006
C00

from 512 Kbit/s to 1 version that
Mbit/s(excluding 1 introduce this
Mbit/s) counter is:
eNodeB:V100R006
C00


Description

from 1 Mbit/s to 2 version that
Mbit/s) counter is:
eNodeB:V100R006
C00

Mbit/s) counter is:
eNodeB:V100R006
C00

Mbit/s) counter is:
eNodeB:V100R006
C00

Mbit/s) counter is:
eNodeB:V100R006
C00

Mbit/s) counter is:
eNodeB:V100R006
C00


Description

Mbit/s) counter is:
eNodeB:V100R006
C00

Mbit/s) counter is:
eNodeB:V100R006
C00

more than 80 Mbit/s version that
introduce this
counter is:
eNodeB:V100R006
C00

.QCI1.Samp.Index with the downlink the mapping single-
0 throughput of mode base station
services of QCI 1 version that
ranging from 0 to 512 introduce this
Kbit/s(excluding 0 counter is:
and 512 Kbit/s) eNodeB:V100R006
C00

ranging from 512 introduce this
Kbit/s to 1 Mbit/s counter is:
(excluding 1 Mbit/s) eNodeB:V100R006
C00


Description

ranging from 1 Mbit/ introduce this
s to 2 Mbit/s counter is:
C00

C00

(excluding 10 Mbit/ eNodeB:V100R006
s) C00

Mbit/s to 15 Mbit/s counter is:
s) C00

s) C00


Description

s) C00

s) C00

ranging more than 80 introduce this
Mbit/s counter is:
eNodeB:V100R006
C00

C00

C00


Description

C00

C00

s) C00

s) C00

s) C00


Description

s) C00

s) C00

Mbit/s counter is:
eNodeB:V100R006
C00

C00

C00


Description

C00

C00

s) C00

s) C00

s) C00


Description

s) C00

s) C00

Mbit/s counter is:
eNodeB:V100R006
C00

C00

C00


Description

C00

C00

s) C00

s) C00

s) C00


Description

s) C00

s) C00

Mbit/s counter is:
eNodeB:V100R006
C00

C00

C00


Description

C00

C00

s) C00

s) C00

s) C00


Description

s) C00

s) C00

Mbit/s counter is:
eNodeB:V100R006
C00

C00

C00


Description

C00

C00

s) C00

s) C00

s) C00


Description

s) C00

s) C00

Mbit/s counter is:
eNodeB:V100R006
C00

C00

C00


Description

C00

C00

s) C00

s) C00

s) C00


Description

s) C00

s) C00

Mbit/s counter is:
eNodeB:V100R006
C00

C00

C00


Description

C00

C00

s) C00

s) C00

s) C00


Description

s) C00

s) C00

Mbit/s counter is:
eNodeB:V100R006
C00

C00

C00


Description

C00

C00

s) C00

s) C00

s) C00


Description

s) C00

s) C00

Mbit/s counter is:
eNodeB:V100R006
C00
1526729435 L.Thrp.UL.BitRate Number of samples V100R008C00,and

.Samp.Index0 with the uplink the mapping single-
from 0 to 256 Kbit/s version that
(excluding 0 and 256 introduce this
Kbit/s) counter is:
eNodeB:V100R006
C00

from 256 Kbit/s to version that
512 Kbit/s(excluding introduce this
512 Kbit/s) counter is:
eNodeB:V100R006
C00


Description

from 512 Kbit/s to 1 version that
Mbit/s) counter is:
eNodeB:V100R006
C00

Mbit/s) counter is:
eNodeB:V100R006
C00

Mbit/s) counter is:
eNodeB:V100R006
C00

Mbit/s) counter is:
eNodeB:V100R006
C00

Mbit/s) counter is:
eNodeB:V100R006
C00


Description

Mbit/s) counter is:
eNodeB:V100R006
C00

Mbit/s) counter is:
eNodeB:V100R006
C00

no less than 40 Mbit/ version that
s introduce this
counter is:
eNodeB:V100R006
C00
None
2.2.44.1 Distribution of the Downlink Throughput in a Cell
Counters
Description
1526729056 L.Thrp.DL.BitRate. Number of samples DBS3900 LTE/

Samp.Index0 with the downlink BTS3900 LTE/
throughput ranging BTS3900A LTE/
from 0 to 512 Kbit/s BTS3900L LTE/
(excluding 0 and 512 BTS3900AL LTE,
Kbit/s) BTS3900


Description

from 512 Kbit/s to 1 BTS3900L LTE/
Mbit/s(excluding 1 BTS3900AL LTE,
Mbit/s) BTS3900

from 1 Mbit/s to 2 BTS3900L LTE/
Mbit/s) BTS3900

Mbit/s) BTS3900

Mbit/s) BTS3900

Mbit/s) BTS3900

Mbit/s) BTS3900

Mbit/s) BTS3900


Description

Mbit/s) BTS3900

more than 80 Mbit/s BTS3900L LTE/
BTS3900AL LTE,
BTS3900

QCI1.Samp.Index0 with the downlink BTS3900 LTE/
throughput of BTS3900A LTE/
services of QCI 1 BTS3900L LTE/
ranging from 0 to 512 BTS3900AL LTE,
Kbit/s(excluding 0 BTS3900
and 512 Kbit/s)

ranging from 512 BTS3900AL LTE,
Kbit/s to 1 Mbit/s BTS3900
(excluding 1 Mbit/s)

ranging from 1 Mbit/ BTS3900AL LTE,
s to 2 Mbit/s BTS3900



Description

(excluding 10 Mbit/
s)

Mbit/s to 15 Mbit/s BTS3900
(excluding 15 Mbit/
s)

(excluding 20 Mbit/
s)

(excluding 40 Mbit/
s)

(excluding 80 Mbit/
s)


Description

ranging more than 80 BTS3900AL LTE,
Mbit/s BTS3900

and 512 Kbit/s)




(excluding 10 Mbit/
s)


Description

(excluding 15 Mbit/
s)

(excluding 20 Mbit/
s)

(excluding 40 Mbit/
s)

(excluding 80 Mbit/
s)

Mbit/s BTS3900


Description

and 512 Kbit/s)




(excluding 10 Mbit/
s)

(excluding 15 Mbit/
s)


Description

(excluding 20 Mbit/
s)

(excluding 40 Mbit/
s)

(excluding 80 Mbit/
s)

Mbit/s BTS3900

and 512 Kbit/s)



Description



(excluding 10 Mbit/
s)

(excluding 15 Mbit/
s)

(excluding 20 Mbit/
s)


Description

(excluding 40 Mbit/
s)

(excluding 80 Mbit/
s)

Mbit/s BTS3900

and 512 Kbit/s)




Description


(excluding 10 Mbit/
s)

(excluding 15 Mbit/
s)

(excluding 20 Mbit/
s)

(excluding 40 Mbit/
s)


Description

(excluding 80 Mbit/
s)

Mbit/s BTS3900

and 512 Kbit/s)





Description

(excluding 10 Mbit/
s)

(excluding 15 Mbit/
s)

(excluding 20 Mbit/
s)

(excluding 40 Mbit/
s)

(excluding 80 Mbit/
s)


Description

Mbit/s BTS3900

and 512 Kbit/s)




(excluding 10 Mbit/
s)


Description

(excluding 15 Mbit/
s)

(excluding 20 Mbit/
s)

(excluding 40 Mbit/
s)

(excluding 80 Mbit/
s)

Mbit/s BTS3900


Description

and 512 Kbit/s)




(excluding 10 Mbit/
s)

(excluding 15 Mbit/
s)


Description

(excluding 20 Mbit/
s)

(excluding 40 Mbit/
s)

(excluding 80 Mbit/
s)

Mbit/s BTS3900

and 512 Kbit/s)



Description



(excluding 10 Mbit/
s)

(excluding 15 Mbit/
s)

(excluding 20 Mbit/
s)


Description

(excluding 40 Mbit/
s)

(excluding 80 Mbit/
s)

Mbit/s BTS3900
Description
The counters measure the downlink Throughput of services per QCI and indicate the distribution
of the downlink Throughput in a cell.
Measurement Points
The downlink traffic volume and data transmission duration of services per QCI are sampled
per second except the last TTI before the DRB buffer is empty. If there is data transmission for
a service within a measurement period, the corresponding counter is incremented by 1 at the end
of a measurement period based on the downlink throughput of the service.
Formula
None
Unit
None

Related Features

3900 Series Base Station Performance Counter Reference (V100R008C00 - 08, eNodeB) (PDF) - EN PDF

Încărcat de

Informații document

Titlu original

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

3900 Series Base Station Performance Counter Reference (V100R008C00 - 08, eNodeB) (PDF) - EN PDF

Încărcat de

Drepturi de autor:

Formate disponibile

3900 Series Base Station

Performance Counter Reference

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 08 (2014-03-14) Huawei Proprietary and Confidential i

About This Document

Product Name Product Version

Issue 08 (2014-03-14) Huawei Proprietary and Confidential ii

Figure 1 Document structure

Table 1 explains the terms shown in Figure 1.

On the top level, object types are classified into three

Object types are located at the second level of the document

Function Subsets are located at the third level of the document

Counters are located at the fourth level of the document

Counter Item Description

Object Overview Definition and function of a object type.

Issue 08 (2014-03-14) Huawei Proprietary and Confidential iii

Functio FunctionSet Name of the function set.

Functio Overview Definition of a function subset and the flowchart for

Counters Counters contained in a function subset.

Counter Counter ID A string of digits that uniquely identifies a counter.

Counter Name Name of a counter. It is composed of a string of uppercase

Counter A phrase that provides a simple description about a counter.

Description Detailed description about a counter.

Measurement Condition for triggering counter measurement.

Formula Relationship among counters.

Unit Unit of a counter.

Network Element Name of the NE to which the counter applies.

Issue 08 (2014-03-14) Huawei Proprietary and Confidential iv

Issue 08 (2014-03-14) Huawei Proprietary and Confidential v

About This Document.....................................................................................................................ii

Issue 08 (2014-03-14) Huawei Proprietary and Confidential vi

1.4.1.2 Number of Bytes on the MP Group........................................................................................................................68

Issue 08 (2014-03-14) Huawei Proprietary and Confidential vii

1.12 Measurement of OMCH performance (OMCH)......................................................................................................156

Issue 08 (2014-03-14) Huawei Proprietary and Confidential viii

1.17 Measurement of IPSec performance (IPSec)............................................................................................................222

Issue 08 (2014-03-14) Huawei Proprietary and Confidential ix

1.23.1.3 PSU shutdown total time....................................................................................................................................288

2 Radio Network Related Measurement..................................................................................313

Issue 08 (2014-03-14) Huawei Proprietary and Confidential x

2.1.5.1 Number of Times of Downlink SCTP Congestion Control.................................................................................332

Issue 08 (2014-03-14) Huawei Proprietary and Confidential xi

Issue 08 (2014-03-14) Huawei Proprietary and Confidential xii

Issue 08 (2014-03-14) Huawei Proprietary and Confidential xiii

Issue 08 (2014-03-14) Huawei Proprietary and Confidential xiv

2.2.20.10 Average Number of PRBs Allocated for Uplink Pre-scheduling.....................................................................943

Issue 08 (2014-03-14) Huawei Proprietary and Confidential xv

2.2.23.4 Number of Inter-RAT Handover Attempts from E-UTRAN to WCDMA Network.......................................1060

Issue 08 (2014-03-14) Huawei Proprietary and Confidential xvi

Issue 08 (2014-03-14) Huawei Proprietary and Confidential xvii

2.2.25.12 Number of Outgoing Handover Failures for Different Causes in a Cell........................................................1244

Issue 08 (2014-03-14) Huawei Proprietary and Confidential xviii

2.2.27.3 Number of Successful X2-based Outgoing Handovers in a Cell.....................................................................1344

Issue 08 (2014-03-14) Huawei Proprietary and Confidential xix

Issue 08 (2014-03-14) Huawei Proprietary and Confidential xx

Issue 08 (2014-03-14) Huawei Proprietary and Confidential xxi

2.2.42 Measurement related to UECNTX establish failure (UeCntx.EstFail.Cell)........................................................1546

Issue 08 (2014-03-14) Huawei Proprietary and Confidential xxii

Issue 08 (2014-03-14) Huawei Proprietary and Confidential xxiii

Issue 08 (2014-03-14) Huawei Proprietary and Confidential xxiv

1 Equipment and Transport Network Related