3900 Series & 5900 Series Base V100R015C10SPC080 GNodeBFunction Performance Counter Reference

3900 Series & 5900 Series Base Station
V100R015C10
gNodeBFunction Performance
Counter Reference
Issue Draft C
Date 2019-04-10
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2019. 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 Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. i

gNodeBFunction Performance Counter Reference About This Document
About This Document
This section describes performance counters for 3900 and 5900 series base stations.
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
Object type One object type contains one or more function subsets.
One function subset contains one or more counters but

Function Subset
belongs to only one object type.
Counters are the basic elements of performance

Counter measurement. One counter can belong to only one function
subset.
Counter Item Description

Table 2 lists the description of each counter item.
Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. ii

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.
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 measuring related counters.
Subset
Counters Counters contained in a function subset.
Counter A table that lists parent counters and their child counters in
Relationship a 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.
NOTE
If the value of the parent counter exceeds the sum of the values of
the child counters, the value difference is the items that are not
counted.
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.
Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. iii

Item Description
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 version for which the counter was first available.
Network Element NE Type of a product displayed on the Network

Management. For a 3900 series base station (which is a
DBS3900, DBS3900 LampSite, BTS3900, BTS3900A,
BTS3900L, BTS3900AL, or BTS3900C), the value can be
BTS3900, BTS3900 WCDMA, BTS3900 LTE, and
BTS3900 5G. For a 5900 series base station (which is a
DBS5900, DBS5900 LampSite, BTS5900, BTS5900A,
BTS5900L or BTS5900AL), the value can be BTS5900,
BTS5900 WCDMA, BTS5900 LTE, and BTS5900 5G.
Among these values, BTS3900 or BTS5900 indicates a co-
MPT base station; BTS3900 WCDMA or BTS5900
WCDMA indicates a UMTS base station; BTS3900 LTE or
BTS5900 LTE indicates an LTE base station; BTS3900 5G
or BTS5900 5G indicates an 5G base station.
Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. iv

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

1 gNodeBFunction Performance Counter Measurement.......................................................... 1
1.1 Measurement of Cell Performance (NRCELL)..............................................................................................................1
1.1.1 DC Measurement (DC.Cell)........................................................................................................................................ 3
1.1.1.1 Number of SgNB Additions in the LTE-NR NSA DC Scenario..............................................................................6
1.1.1.2 Number of PSCell Changes in the LTE-NR NSA DC Scenario...............................................................................8
1.1.1.3 Number of SgNB Releases in the LTE-NR NSA DC Scenario..............................................................................10
1.1.1.4 Number of DRB Additions for LTE-NR NSA DC UEs.........................................................................................14
1.1.1.5 Number of DRB Releases for LTE-NR NSA DC UEs...........................................................................................16
1.1.1.6 Number of Coverage-based SgNB Releases in LTE-NR NSA DC Scenarios....................................................... 19
1.1.2 DRB Measurement (Traffic.DRB.Cell).....................................................................................................................20
1.1.2.1 Number of DRBs Occupied in an NR Cell.............................................................................................................21
1.1.3 PDCP Measurement (PDCP.Cell)..............................................................................................................................21
1.1.3.1 Number of PDCP SDUs Transmitted to the Upper Layer in a Cell....................................................................... 24
1.1.3.2 Number of SDUs Received at the PDCP Layer in a Cell.......................................................................................25
1.1.3.3 Traffic of PDCP SDUs Transmitted to the Upper Layer in a Cell......................................................................... 26
1.1.3.4 Traffic of SDUs Received at the PDCP Layer in a Cell......................................................................................... 27
1.1.3.5 Number of PDCP PDUs Transmitted to the RLC Layer in a Cell (Retransmission Included).............................. 28
1.1.3.6 Number of RLC PDUs Received at the PDCP Layer in a Cell.............................................................................. 29
1.1.3.7 Traffic of PDCP PDUs Transmitted to the RLC Layer in a Cell............................................................................30
1.1.3.8 Traffic of RLC PDUs Received at the PDCP Layer in a Cell................................................................................ 31
1.1.3.9 Number of Lost PDCP SDUs in a Cell...................................................................................................................32
1.1.3.10 Number of PDCP PDUs Transmitted over the X2 Interface in a Cell (Retransmission Included)...................... 33
1.1.3.11 Number of PDCP PDUs Received over the X2 Interface in a Cell......................................................................34
1.1.3.12 Traffic of PDCP PDUs Transmitted over the X2 interface in a cell.....................................................................35
1.1.3.13 Traffic of PDCP PDUs Received over the X2 Interface in a Cell........................................................................ 36
1.1.4 PDU Session Modification Measurement (PDUSession.Modify.Cell)..................................................................... 37
1.1.4.1 Number of PDU Session Modifications in SA Scenarios...................................................................................... 38
1.1.5 PDU Session Setup Measurement (PDUSession.Est.Cell)....................................................................................... 39
1.1.5.1 Number of PDU Session Setups in SA Scenarios.................................................................................................. 40
1.1.6 PDU Session Release Measurement (PDUSession.Rel.Cell)....................................................................................42
1.1.6.1 Number of PDU Session Releases in SA Scenarios...............................................................................................43
1.1.7 QoS Flow Modification Measurement (QosFlow.Modify.Cell)................................................................................46
Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. v

1.1.7.1 Number of QoS Flow Modifications in SA Scenarios........................................................................................... 47

1.1.8 QoS Flow Setup Failure Measurement (QosFlow.EstFail.Cell)................................................................................49
1.1.8.1 Number of QoS Flow Setup Failures in SA Scenarios...........................................................................................50
1.1.9 QoS Flow Setup Measurement (QosFlow.Est.Cell).................................................................................................. 57
1.1.9.1 Number of QoS Flow Setups in SA Scenarios....................................................................................................... 57
1.1.10 QoS Flow Release Measurement (QosFlow.Rel.Cell)............................................................................................ 60
1.1.10.1 Number of QoS Flow Releases in SA Networking.............................................................................................. 62
1.1.11 RRC Setup Failure Measurement (RRC.SetupFail.Cell).........................................................................................68
1.1.11.1 Number of RRC Setup Failures in SA Scenarios................................................................................................. 68
1.1.12 RRC Setup Measurement (RRC.Setup.Cell)........................................................................................................... 71
1.1.12.1 Number of RRC Connection Setups in SA Scenarios.......................................................................................... 75
1.1.13 RRC Reestablishment Failure Measurement (RRC.ReEstFail.Cell).......................................................................83
1.1.13.1 Number of RRC Connection Reestablishment Failures in SA Scenarios............................................................ 84
1.1.14 RRC Reestablishment Measurement (RRC.ReEst.Cell)......................................................................................... 85
1.1.14.1 Number of RRC Connection Reestablishment Times in SA Scenarios............................................................... 86
1.1.15 UE Context Modification Measurement (UeCntx.Modify.Cell)............................................................................. 88
1.1.15.1 Number of UE Context Modifications in SA Scenarios.......................................................................................88
1.1.16 UE Context Setup Failure Measurement (UeCntx.EstFail.Cell)............................................................................. 90
1.1.16.1 Number of UE Context Setup Failures in SA Scenarios...................................................................................... 91
1.1.17 UE Context Setup Measurement (UeCntx.Est.Cell)............................................................................................... 94
1.1.17.1 Number of UE Context Setups in SA Scenarios.................................................................................................. 95
1.1.18 UE Context Release Measurement (UeCntx.Rel.Cell)............................................................................................97
1.1.18.1 Number of UE Context Releases in SA Scenarios............................................................................................... 98
1.1.19 UL DL Decoupling Measurement (Decoupling.Cell)........................................................................................... 101
1.1.19.1 Number of PUCCH Frequency Changes in the NR Uplink and Downlink Decoupling Cells.......................... 102
1.1.20 Secure Mode Measurement (SecurMode.Cell)......................................................................................................104
1.1.20.1 Number of Security Mode Setups in a Cell........................................................................................................ 105
1.1.21 Cell CA Measurement (CA.Cell).......................................................................................................................... 107
1.1.21.1 Number of Times CA UEs Add, Remove, or Change SCells............................................................................ 109
1.1.22 Cell User Quantity Measurement (User.Cell)........................................................................................................113
1.1.22.1 Number of Decoupling UEs in a Downlink Cell................................................................................................115
1.1.22.2 Average Number of LTE-NR NSA UEs in the PSCell.......................................................................................116
1.1.22.3 Number of UEs in a Cell.....................................................................................................................................117
1.1.22.4 Number of CA UEs in a Cell.............................................................................................................................. 118
1.1.22.5 Number of B2H UEs in a Cell............................................................................................................................120
1.1.23 Cell Algorithm Measurement (Algo.Cell).............................................................................................................121
1.1.23.1 Cell Unavailability Duration.............................................................................................................................. 122
1.1.24 Cell Reserved Counter Measurement (Reserve.Cell)............................................................................................123
1.1.24.1 Reserved Counter 1 for the Cell......................................................................................................................... 130
Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. vi


1.1.24.10 Reserved Counter 10 for the Cell..................................................................................................................... 136
1.1.24.11 Reserved Counter 11 for the Cell......................................................................................................................137
Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. vii


1.1.25 Incoming Intra-RAT Handover Measurement (HO.NR.In.Cell)........................................................................... 164
1.1.25.1 Number of Intra-NR Incoming Handover Executions........................................................................................165
1.1.25.2 Number of Failed Intra-NR Incoming Handovers..............................................................................................168
1.1.25.3 Number of Successful Intra-NR Incoming Handovers.......................................................................................170
1.1.25.4 Number of Intra-NR Incoming Handover Attempts...........................................................................................175
1.1.26 Outgoing Intra-RAT Handover Measurement (HO.NR.Out.Cell).........................................................................178
1.1.26.1 Number of Intra-NR Intra-Frequency Outgoing Handover Executions............................................................. 180
1.1.26.2 Number of Successful Intra-NR Intra-Frequency Outgoing Handovers............................................................ 184
1.1.26.3 Number of Intra-NR Intra-Frequency Outgoing Handover Attempts................................................................ 190
1.1.26.4 Number of Failed Intra-NR Intra-Frequency Outgoing Handovers................................................................... 193
1.1.27 Outgoing Inter-RAT Handover Measurement (N.HO.InterRAT)..........................................................................201
1.1.27.1 Number of Redirections from NR to E-UTRAN................................................................................................204
1.1.27.2 Number of Outgoing Handovers from NR to E-UTRAN.................................................................................. 205
1.1.27.3 Number of EPS Fallback Executions from NR to an Inter-RAT System........................................................... 213
1.2 Measurement of DU Cell Performance (NRDUCELL)............................................................................................. 215
1.2.1 Measurement of CQIs in the CQI Table with 256QAM (ChMeas.256QAM.CQI.DuCell)....................................216
1.2.1.1 Number of Wideband CQI Reports with 256QAM in Single-Codeword Transmission in a Cell....................... 230
1.2.2 Measurement of CQIs in the CQI Table with 64QAM (ChMeas.64QAM.CQI.DuCell)........................................261
1.2.2.1 Number of Wideband CQI Reports with Different CQI indexes in the CQI Table with 64QAM in Singe-
Codeword Transmission in a Cell.....................................................................................................................................274
1.2.3 CQI Measurement (ChMeas.CQI.DuCell).............................................................................................................. 305
1.2.3.1 Number of Wideband CQI Reports in Single-Codeword Transmission in a Cell................................................ 312
1.2.3.2 Number of Wideband CQI Reports for Codeword 0 in Dual-Codeword Transmission in a Cell........................ 318
1.2.3.3 Number of Wideband CQI Reports for Codeword 1 in Dual-Codeword Transmission in a Cell........................ 324
1.2.4 DU Cell Algorithm Measurement (Algo.DuCell)................................................................................................... 329
1.2.4.1 Duration of Radio Resource Evaluation in Heavy Load State............................................................................. 330
1.2.5 MAC Measurement (MAC.DuCell)........................................................................................................................ 331
1.2.5.1 Number of TBs Initially Transmitted on the Uplink SCH....................................................................................336
1.2.5.2 Number of TBs Retransmitted on the Uplink SCH.............................................................................................. 339
1.2.5.3 Number of Uplink TBs That Fail to Be Correctly Received After the Maximum Number of Retransmissions Is
Reached............................................................................................................................................................................ 341
1.2.5.4 Number of TBs Initially Transmitted on the Downlink SCH...............................................................................344
1.2.5.5 Number of TBs Retransmitted on the Downlink SCH......................................................................................... 346
1.2.5.6 Number of Downlink TBs That Fail to Be Correctly Received After the Maximum Number of Retransmissions
Is Reached.........................................................................................................................................................................348
1.2.5.7 Number of TBs Failing To Be Initially Transmitted on the Downlink SCH........................................................350
1.2.6 MCS Measurement (ChMeas.MCS.DuCell)........................................................................................................... 352
1.2.6.1 Number of Times a Specific MCS Index Is Scheduled on the PUSCH............................................................... 367
1.2.6.2 Number of Times a Specific MCS Index Is Scheduled on the PDSCH............................................................... 376
Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. viii

1.2.6.3 Number of Times an MCS Index Is Selected for PUSCH Scheduling for UEs Configured to Use 256QAM.... 385
1.2.7 MIMO Channel Measurement (MIMO.DuCell)..................................................................................................... 391
1.2.7.1 Number of PRBs Paired for Downlink MIMO in a Cell...................................................................................... 393
1.2.7.2 Number of Layers Paired for Downlink MIMO in a Cell.................................................................................... 394
1.2.7.3 Number of Transmission Layers for Downlink MIMO in a Cell......................................................................... 395
1.2.7.4 Maximum Number of Transmission Layers for Downlink MIMO in a Cell....................................................... 396
1.2.7.5 Number of PRBs Paired for Uplink MIMO in a Cell...........................................................................................397
1.2.7.6 Number of Layers Paired for Uplink MIMO in a Cell......................................................................................... 398
1.2.7.7 Number of Transmission Layers for Uplink MIMO in a Cell..............................................................................399
1.2.7.8 Maximum Number of Transmission Layers for Uplink MIMO in a Cell............................................................ 400
1.2.8 NR DU Cell Scheduled User Quantity Measurement (ScheUser.DuCell).............................................................. 401
1.2.8.1 Number of Active UEs in the Uplink in an NR DU Cell..................................................................................... 403
1.2.8.2 Number of Active UEs in the Downlink in an NR DU Cell................................................................................ 404
1.2.8.3 Number of Active UEs in an NR DU Cell........................................................................................................... 405
1.2.8.4 Total Number of Scheduled UEs in the Downlink in an NR DU Cell................................................................. 406
1.2.8.5 Total Number of Scheduled UEs in the Uplink in an NR DU Cell...................................................................... 407
1.2.8.6 Number of Active B2H UEs in an NR DU Cell...................................................................................................408
1.2.8.7 Number of Uplink and Downlink CA UEs That Use the Local Cell as Their PCell and Have Activated Scells
.......................................................................................................................................................................................... 409
1.2.8.8 Number of Uplink and Downlink CA UEs That Use the Local Cell as Their SCell and Have the SCell Activated
.......................................................................................................................................................................................... 410
1.2.9 NR DU Cell Reserved Counter Measurement (Reserve.DuCell)............................................................................411
1.2.9.1 Reserved Counter 1 for the Local Cell................................................................................................................. 419
1.2.9.10 Reserved Counter 10 for the Local Cell............................................................................................................. 425
Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. ix


1.2.10 Measurement per MCS Index in the MCS Index Table for PDSCH with 256QAM (ChMeas.PDSCH.
256QAM.MCS.DuCell)....................................................................................................................................................452
1.2.10.1 Number of RBs Allocated for PDSCH with Different MCS Indexes in the MCS Index Table with 256QAM
.......................................................................................................................................................................................... 469
1.2.11 Measurement per MCS Index in the MCS Index Table for PDSCH with 64QAM (ChMeas.PDSCH.
64QAM.MCS.DuCell)......................................................................................................................................................508
1.2.11.1 Number of RBs Allocated for PDSCH with Different MCS Indexes in the MCS Index Table with 64QAM...525
1.2.12 PRB Measurement (PRB.DuCell)......................................................................................................................... 565
1.2.12.1 Number of Downlink PRBs Used in a Cell........................................................................................................ 569
1.2.12.2 Number of Used Uplink PRBs in a Cell.............................................................................................................570
1.2.12.3 Number of PDCCH CCEs used in a Cell........................................................................................................... 571
1.2.12.4 Number of Available PRBs in a Cell..................................................................................................................573
1.2.12.5 Number of Times of Successful PDCCH Resource Allocations with a Specific Aggregation Level................575
1.2.12.6 Number of CCEs with More Than One PDCCH Spatial Multiplexing Layer................................................... 579
Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. x

1.2.13 Measurement per MCS Index in the MCS Index Table for PUSCH with 256QAM (ChMeas.PUSCH.
256QAM.MCS.DuCell)....................................................................................................................................................580
1.2.13.1 Number of RBs Allocated for PUSCH with Different MCS Indexes in the MCS Index Table with 256QAM 596
1.2.14 Measurement per MCS Index in the MCS Index Table for PUSCH with Transform Precoding and 64QAM
(ChMeas.PUSCH.64QAMTP.MCS.DuCell)....................................................................................................................635
1.2.14.1 Number of RBs Allocated for PUSCH with Different MCS Indexes in the MCS Index Table with Transform
Precoding and 64QAM..................................................................................................................................................... 658
1.2.15 Measurement per MCS Index in the MCS Index Table for PUSCH with 64QAM (ChMeas.PUSCH.
64QAM.MCS.DuCell)......................................................................................................................................................703
1.2.15.1 Number of RBs Allocated for PUSCH with Different MCS Indexes in the MCS Index Table with 64QAM.. 720
1.2.16 RLC Measurement (RLC.DuCell).........................................................................................................................760
1.2.16.1 Number of Downlink SDUs Received at the RLC Layer in a Cell.................................................................... 761
1.2.16.2 Number of Uplink SDUs Sent at the RLC Layer in a Cell.................................................................................761
1.2.16.3 Number of Downlink SDUs Lost at the RLC Layer over the Radio Interface in a Cell.................................... 762
1.2.17 Channel Quality Measurement (ChMeas.Pwr.DuCell)......................................................................................... 763
1.2.17.1 Interference Received on Each Uplink PRB...................................................................................................... 765
1.2.17.2 Uplink RSSI Measurement................................................................................................................................. 766
1.2.17.3 Cell Downlink Transmit Power.......................................................................................................................... 767
1.2.17.4 Power of the Thirteenth Symbol on the Last Uplink Slot.................................................................................. 768
1.2.17.5 Power of the Sixth Symbol on the Last Uplink Slot...........................................................................................769
1.2.17.6 Power of the Last Symbol in a GAP...................................................................................................................770
1.2.18 DU Cell CA Measurement (CA.DuCell)...............................................................................................................771
1.2.18.1 Number of SCell Activation and Deactivation Executions for CA UEs............................................................ 772
1.2.19 UE Throughput Distribution Measurement (Thp.PDF.DuCell)............................................................................ 774
1.2.19.1 RLC-Layer Downlink UE Throughput Distribution.......................................................................................... 778
1.2.19.2 RLC-Layer Uplink UE Throughput Distribution............................................................................................... 782
1.2.20 Throughput and Data Volume Measurement (Thp.DuCell).................................................................................. 786
1.2.20.1 Volume of Downlink Data Sent at the RLC Layer in a Cell.............................................................................. 789
1.2.20.2 Duration of Downlink Data Transmission at the RLC Layer in a Cell.............................................................. 789
1.2.20.3 Volume of Uplink Data Received at the RLC Layer in a Cell............................................................................790
1.2.20.4 Duration of Uplink Data Transmission at the RLC Layer in a Cell................................................................... 791
1.2.20.5 Volume of Downlink Data Sent at the MAC Layer in a Cell............................................................................. 792
1.2.20.6 Duration of Downlink Data Transmission at the MAC Layer in a Cell............................................................. 792
1.2.20.7 Volume of Uplink Data Received at the MAC Layer in a Cell.......................................................................... 793
1.2.20.8 Duration of Uplink Data Transmission at the MAC Layer in a Cell..................................................................794
1.2.20.9 Volume of Downlink Data Sent at the RLC Layer for B2H UEs in a Cell........................................................ 795
1.2.20.10 Volume of Uplink Data Received at the RLC Layer for B2H UEs in a Cell................................................... 796
1.2.20.11 Downlink Volume of RLC SDUs Sent in the Last Timeslot During Which the Buffer Becomes Empty........797
1.2.20.12 Data Transmission Duration Excluding the Last Timeslot During Which the Downlink Buffer Becomes
Empty................................................................................................................................................................................798
1.2.20.13 Uplink Volume of Small Packets Received at the RLC Layer......................................................................... 799
1.2.20.14 Uplink Data Transmission Duration Excluding That of Small Packets........................................................... 799
1.2.20.15 Duration of Correct Downlink Data Transmission Excluding the Last Timeslot............................................ 800
1.2.20.16 Duration of Correct Uplink Data Transmission Excluding That of Small Packets.......................................... 801
Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. xi

1.2.21 Cell Service Quality Measurement (QoS.Cell)..................................................................................................... 802

1.2.21.1 Total Delay of Downlink Packets for DRB Services Processed by the gNodeB DU in a Cell.......................... 803
1.2.21.2 Number of Successfully Transmitted Downlink RLC SDUs for DRB Services over the Uu Interface in a Cell
.......................................................................................................................................................................................... 804
1.2.21.3 Total Transmission Delay of Downlink RLC SDUs for DRB Services over the Uu Interface in a Cell........... 805
1.2.21.4 Total Number of Downlink RLC SDUs for DRB Services Processed by the gNodeB DU in a Cell................ 806
1.2.21.5 Total Number of Downlink RLC SDUs That Are for DRB Services and Enter the Empty Buffer in a Cell.....807
1.2.21.6 Total Transmission Delay of the First Downlink RLC SDUs for DRB Services in the Empty Buffer in a Cell
.......................................................................................................................................................................................... 808
1.2.22 Paging Measurement (Paging.Cell)....................................................................................................................... 808
1.2.22.1 Paging in SA Networking...................................................................................................................................809
1.2.23 Random Access Measurement (RA.DuCell).........................................................................................................810
1.2.23.1 Number of Random Preamble Receptions......................................................................................................... 813
1.2.23.2 Number of successful contention resolution delivery times...............................................................................815
1.2.23.3 Number of Dedicated Preamble Receptions.......................................................................................................817
1.2.23.4 Number of Msg3 Receptions During Non-Contention Based Random Access................................................. 819
1.2.23.5 Number of Random Access Times When the TA Values are in a Range in a Cell............................................ 820
1.3 Measurement of gNodeB Performance (gNodeB)..................................................................................................... 825
1.3.1 gNodeB Transmission Interface Measurement (Traffic.TRPIP.gNodeB)............................................................... 826
1.3.1.1 Transmit and Receive Rates of the X2-U Interface on a gNodeB........................................................................830
1.3.1.2 Traffic Transmitted and Received over the X2-U Interface on a gNodeB........................................................... 831
1.3.1.3 Transmit and Receive Rates of the S1-U Interface on a gNodeB........................................................................ 833
1.3.1.4 Traffic Transmitted and Received over the S1-U Interface on a gNodeB............................................................835
1.3.1.5 Transmit and Receive Rates of the Xn-U Interface on a gNodeB........................................................................836
1.3.1.6 Transmit and Receive Rates of the NG-U Interface on a gNodeB.......................................................................837
1.3.1.7 Traffic Transmitted and Received over the Xn-U Interface on a gNodeB........................................................... 838
1.3.1.8 Traffic Transmitted and Received over the NG-U Interface on a gNodeB.......................................................... 839
1.3.2 gNodeB Call Processing Times (CallAtt.gNodeB)................................................................................................. 840
1.3.2.1 gNodeB Call Processing Times............................................................................................................................ 841
1.3.3 gNodeB User Quantity Measurement (User.gNodeB)............................................................................................ 842
1.3.3.1 Number of UEs Under gNodeB............................................................................................................................843
1.3.4 gNodeB Algorithm Measurement (Algo.gNodeB)................................................................................................. 844
1.3.4.1 gNodeB Unavailability Duration..........................................................................................................................844
1.4 Measurement of gNodeB DU Logical Node Performance (gNBDU)........................................................................845
1.4.1 gNBDU Transmission Interface Measurement (Traffic.TRPIP.gNBDU)............................................................... 845
1.4.1.1 Transmit and Receive Rates of the F1-U Interface on a gNodeB DU..................................................................847
1.4.1.2 Traffic Transmitted and Received on the F1-U Interface on a gNodeB DU........................................................ 848
1.5 Measurement of NSA DU Cell QCI Performance (NRDUCELL.NSAQCI).............................................................849
1.5.1 DU Cell QCI User Number Measurement (User.DuCell.QCI)............................................................................... 849
1.5.1.1 Number of Active Users in NSA Networking......................................................................................................850
1.5.2 QCI Throughput Measurement (Thp.DuCell.QCI)................................................................................................. 851
1.5.2.1 Volume of Downlink Data Sent at the RLC Layer in a Cell in NSA Networking............................................... 852
Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. xii

1.5.2.2 Downlink Volume of RLC SDUs Sent in the Last Timeslot During Which the Buffer Becomes Empty in NSA
Networking....................................................................................................................................................................... 853
1.5.2.3 Data Transmission Duration Excluding the Last Timeslot During Which the Downlink Buffer Becomes Empty
in NSA Networking.......................................................................................................................................................... 854
1.6 Measurement of Neighboring NR Cell Performance (NRCellRelation)....................................................................855
1.6.1 Intra-NR Inter-Cell Outgoing Handover Measurement (HO.NRCellRelation.Out.Cell)........................................855
1.6.1.1 Number of Intra-NR Outgoing Handovers Between Two Specific Cells.............................................................856
1.7 Measurement of Operator-Specific NR DU Cell Performance (NRDUCell.Operator)............................................. 863
1.7.1 Operator RLC Traffic Measurement (Traffic.RLC.DuCell.Operator).....................................................................863
1.7.1.1 Total RLC-layer SDU Duration of All UEs Served by an Operator.................................................................... 864
1.7.1.2 Total volume of data transmission at the RLC layer for UEs of an Operator...................................................... 865
1.8 Measurement of Operator-Specific NR CU Cell Performance (NRCell.Operator)................................................... 867
1.8.1 Cell User Quantity Measurement per Operator (Traffic.User.Cell.Operator)......................................................... 867
1.8.1.1 Number of Users of Operator in a Cell.................................................................................................................868
1.9 Measurement of NR Cell-to-E-UTRAN Cell Handover Performance (NRCELLtoECELL).................................... 869
1.9.1 Inter-RAT Inter-Cell E-UTRAN Handover Measurement (IRATHO.NrCell.ECell).............................................. 869
1.9.1.1 Number of Handovers from a Specific NR Cell to a Specific E-UTRAN Cell................................................... 870
Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. xiii

gNodeBFunction Performance Counter Reference 1 gNodeBFunction Performance Counter Measurement
1 gNodeBFunction Performance Counter

Measurement
About This Chapter
This section describes gNodeBFunction performance counters.
1.1 Measurement of Cell Performance (NRCELL)

1.2 Measurement of DU Cell Performance (NRDUCELL)
1.3 Measurement of gNodeB Performance (gNodeB)
1.4 Measurement of gNodeB DU Logical Node Performance (gNBDU)
1.5 Measurement of NSA DU Cell QCI Performance (NRDUCELL.NSAQCI)
1.6 Measurement of Neighboring NR Cell Performance (NRCellRelation)
1.7 Measurement of Operator-Specific NR DU Cell Performance (NRDUCell.Operator)
1.8 Measurement of Operator-Specific NR CU Cell Performance (NRCell.Operator)
1.9 Measurement of NR Cell-to-E-UTRAN Cell Handover Performance (NRCELLtoECELL)
1.1 Measurement of Cell Performance (NRCELL)

Overview
The NRCELL measurement object contains cell-level function subsets. Cells are deployed on
gNodeB central units (CUs).
FunctionSubSets
FunctionSubSet FunctionSubSet Name
DC.Cell DC Measurement(DC.Cell)
Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. 1

Traffic.DRB.Cell DRB Measurement (Traffic.DRB.Cell)
PDCP.Cell PDCP Measurement(PDCP.Cell)
PDUSession.Modify.Cell PDU Session Modification Measurement

(PDUSession.Modify.Cell)
PDUSession.Est.Cell PDU Session Setup Measurement

(PDUSession.Est.Cell)
PDUSession.Rel.Cell PDU Session Release Measurement

(PDUSession.Rel.Cell)
QosFlow.Modify.Cell QoS Flow Modification Measurement

(QosFlow.Modify.Cell)
QosFlow.EstFail.Cell QoS Flow Setup Failure Measurement

(QosFlow.EstFail.Cell)
QosFlow.Est.Cell QoS Flow Setup Measurement

(QosFlow.Est.Cell)
QosFlow.Rel.Cell QoS Flow Release Measurement

(QosFlow.Rel.Cell)
RRC.SetupFail.Cell RRC Setup Failure Measurement

(RRC.SetupFail.Cell)
RRC.Setup.Cell RRC Setup Measurement (RRC.Setup.Cell)
RRC.ReEstFail.Cell RRC Reestablishment Failure Measurement

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

(RRC.ReEst.Cell)
UeCntx.Modify.Cell UE Context Modification Measurement

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

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

(UeCntx.Est.Cell)
UeCntx.Rel.Cell UE Context Release Measurement

(UeCntx.Rel.Cell)
Decoupling.Cell UL DL Decoupling
Measurement(Decoupling.Cell)
SecurMode.Cell Secure Mode Measurement

(SecurMode.Cell)
CA.Cell Cell CA Measurement(CA.Cell)
User.Cell Cell User Quantity Measurement(User.Cell)

Algo.Cell Cell Algorithm Measurement(Algo.Cell)
Reserve.Cell Cell Reserved Counter

Measurement(Reserve.Cell)
HO.NR.In.Cell Incoming Intra-RAT Handover

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

Measurement (HO.NR.Out.Cell)
N.HO.InterRAT Outgoing Inter-RAT Handover

Measurement (N.HO.InterRAT)
1.1.1 DC Measurement (DC.Cell)

Overview
The DC Measurement(DC.Cell) function subset measures the items for DC UEs in a cell.
Counters
Counter ID Counter Name Counter Introduced in
Description Version...
1911816746 N.NsaDc.SgNB.Ad Number of SgNB BTS5900 5G:

d.Att addition requests in V100R013C10
the LTE-NR NSA BTS5900:
DC scenario V100R013C10
BTS3900:
V100R015C00
1911816747 N.NsaDc.SgNB.Ad Number of BTS5900 5G:

d.Succ successful SgNB V100R013C10
additions in the BTS5900:
LTE-NR NSA DC V100R013C10
scenario BTS3900:
V100R015C00
1911816748 N.NsaDc.InterSgN Number of inter- BTS5900 5G:

B.PSCell.Change.A SgNB PSCell V100R013C10
tt change requests in BTS5900:
the LTE-NR NSA V100R013C10
DC scenario BTS3900:
V100R015C00


1911816749 N.NsaDc.InterSgN Number of BTS5900 5G:

B.PSCell.Change.S successful inter- V100R013C10
ucc SgNB PSCell BTS5900:
changes in the LTE- V100R013C10
NR NSA DC BTS3900:
scenario V100R015C00
1911816750 N.NsaDc.IntraSgN Number of intra- BTS5900 5G:

B.PSCell.Change.A SgNB PSCell V100R013C10
tt change requests in BTS5900:
the LTE-NR NSA V100R013C10
DC scenario BTS3900:
V100R015C00
1911816751 N.NsaDc.IntraSgN Number of BTS5900 5G:

B.PSCell.Change.S successful intra- V100R013C10
ucc SgNB PSCell BTS5900:
changes in the LTE- V100R013C10
NR NSA DC BTS3900:
1911816752 N.NsaDc.SgNB.Rel Total number of BTS5900 5G:

SgNB releases in the V100R013C10
LTE-NR NSA DC BTS5900:
BTS3900:
V100R015C00
1911816753 N.NsaDc.SgNB.Ab Total number of BTS5900 5G:

normRel.Radio abnormal SgNB V100R013C10
releases in the LTE- BTS5900:
NR NSA DC V100R013C10
scenarios caused by BTS3900:
radio layer issues V100R015C00
1911816754 N.NsaDc.DRB.Add Number of DRB BTS5900 5G:

.Att addition requests for V100R013C10
UEs on the SgNB V100R013C10
BTS3900:
V100R015C00
1911816755 N.NsaDc.DRB.Add Number of BTS5900 5G:

.Succ successful DRB V100R013C10
additions for LTE- BTS5900:
NR NSA DC UEs V100R013C10
on the SgNB BTS3900:
V100R015C00


1911816756 N.NsaDc.DRB.Rel Number of DRB BTS5900 5G:

releases for LTE-NR V100R013C10
NSA DC UEs on the BTS5900:
SgNB V100R013C10
BTS3900:
V100R015C00
1911816757 N.NsaDc.DRB.Abn Number of abnormal BTS5900 5G:

ormRel DRB releases for V100R013C10
UEs on the SgNB V100R013C10
BTS3900:
V100R015C00
1911816836 N.NsaDc.SgNB.Ab Total number of BTS5900 5G:

normRel.Radio.SU abnormal SgNB V100R015C00
L releases in the LTE- BTS5900:
NR NSA DC V100R015C00
scenarios caused by BTS3900:
radio layer issues of V100R015C00
the SUL
1911816843 N.NsaDc.SgNB.Rel. Number of BTS5900 5G:

Coverage coverage-based V100R015C00
SgNB releases in BTS5900:
LTE-NR NSA DC V100R015C00
scenarios BTS3900:
V100R015C00
1911817841 N.NsaDc.SgNB.Rel. Total number of BTS3900:

SgNBTrigger SgNB releases V100R015C10
triggered by SgNB BTS5900:
in LTE-NR NSA DC V100R015C10
scenarios BTS5900 5G:
V100R015C10
1911817842 N.NsaDc.SgNB.Ab Total Number of BTS3900:

normRel.Trans abnormal SgNB V100R015C10
releases due to the BTS5900:
transport layer in V100R015C10
LTE-NR NSA DC BTS5900 5G:
scenarios V100R015C10
1911817843 N.NsaDc.SgNB.Ab Total number of BTS3900:

normRel abnormal SgNB V100R015C10
releases triggered by BTS5900:
SgNB in LTE-NR V100R015C10
NSA DC scenarios BTS5900 5G:
V100R015C10

Counter Relationship
None
1.1.1.1 Number of SgNB Additions in the LTE-NR NSA DC Scenario
Counters
Counter ID Counter Counter Network Applicable
Name Description Element Mode
1911816746 N.NsaDc.SgNB Number of BTS3900, N

.Add.Att SgNB addition BTS3900 5G,
requests in the BTS5900,
LTE-NR NSA
DC scenario BTS5900 5G

.Add.Succ successful BTS3900 5G,
SgNB additions BTS5900,
in the LTE-NR
NSA DC BTS5900 5G
scenario
Description
These counters measure the number of SgNB addition requests and successful SgNB
additions in the LTE-NR NSA DC scenario. The signaling procedures related to these
counters comply with section 10.2.1 in 3GPP TS 37.340 and section 5.3.5 in 3GPP TS
36.331.
Measurement Points
As shown at point A in Figure 1-1, the N.NsaDc.SgNB.Add.Att counter is incremented by 1
each time the gNodeB receives an SgNB Addition Request message from the eNodeB. As
shown at point B in Figure 1-1, the N.NsaDc.SgNB.Add.Succ counter is incremented by 1
each time the gNodeB receives an SgNB Reconfiguration Complete message from the
eNodeB. These counter values are accumulated in the PSCell specified by the gNodeB.

Figure 1-1
Formula
None
Unit
None
Related Features
Counter Name Feature ID Feature Name
N.NsaDc.SgNB.Add.Att Multi-mode: MRFD-131162 NSA Networking based on

GSM: None EPC (NR)
UMTS: None
LTE: None
NR: None
N.NsaDc.SgNB.Add.Succ Multi-mode: MRFD-131162 NSA Networking based on

GSM: None EPC (NR)
UMTS: None
LTE: None
NR: None

1.1.1.2 Number of PSCell Changes in the LTE-NR NSA DC Scenario
Counters
1911816748 N.NsaDc.InterS Number of BTS3900, N

gNB.PSCell.Ch inter-SgNB BTS3900 5G,
ange.Att PSCell change BTS5900,
requests in the
LTE-NR NSA BTS5900 5G
DC scenario
1911816749 N.NsaDc.InterS Number of BTS3900, N

gNB.PSCell.Ch successful inter- BTS3900 5G,
ange.Succ SgNB PSCell BTS5900,
changes in the
DC scenario
1911816750 N.NsaDc.IntraS Number of BTS3900, N

gNB.PSCell.Ch intra-SgNB BTS3900 5G,
ange.Att PSCell change BTS5900,
requests in the
DC scenario
1911816751 N.NsaDc.IntraS Number of BTS3900, N

gNB.PSCell.Ch successful intra- BTS3900 5G,
ange.Succ SgNB PSCell BTS5900,
changes in the
DC scenario
Description
These counters measure the number of inter-SgNB and intra-SgNB PSCell change requests
and successful PSCell changes in the LTE-NR NSA DC scenario. The signaling procedures
related to these counters comply with sections 10.5.1 and 10.3.1 in 3GPP TS 37.340 and
section 5.3.5 in 3GPP TS 36.331.
Measurement Points
As shown at point A in Figure 1-2, the N.NsaDc.InterSgNB.PSCell.Change.Att counter is
incremented by 1 each time the gNodeB sends an SgNB Change Required message to the
eNodeB. As shown at point B in Figure 1-2, the N.NsaDc.InterSgNB.PSCell.Change.Succ
counter is incremented by 1 each time the gNodeB receives an SgNB Change Confirm
message from the eNodeB. As shown at point A in Figure 1-3, the
N.NsaDc.IntraSgNB.PSCell.Change.Att counter is incremented by 1 each time the gNodeB
sends an SgNB Modification Required message to the eNodeB to request a PSCell change. As
shown at point B in Figure 1-3, the N.NsaDc.IntraSgNB.PSCell.Change.Succ counter is

incremented by 1 each time the gNodeB is notified of a PSCell change via an SgNB
Modification Confirm message from the eNodeB. These counter values are accumulated in
the PSCell of the LTE-NR NSA DC UE.
Figure 1-2
Figure 1-3
Formula
None
Unit
None

Related Features
N.NsaDc.InterSgNB.PSCell. Multi-mode: MRFD-131162 NSA Networking based on

Change.Att GSM: None EPC (NR)
UMTS: None
LTE: None
NR: None
N.NsaDc.InterSgNB.PSCell. Multi-mode: MRFD-131162 NSA Networking based on

Change.Succ GSM: None EPC (NR)
UMTS: None
LTE: None
NR: None
N.NsaDc.IntraSgNB.PSCell. Multi-mode: MRFD-131162 NSA Networking based on

Change.Att GSM: None EPC (NR)
UMTS: None
LTE: None
NR: None
N.NsaDc.IntraSgNB.PSCell. Multi-mode: MRFD-131162 NSA Networking based on

Change.Succ GSM: None EPC (NR)
UMTS: None
LTE: None
NR: None
1.1.1.3 Number of SgNB Releases in the LTE-NR NSA DC Scenario
Counters
1911816752 N.NsaDc.SgNB Total number of BTS3900, N

.Rel SgNB releases BTS3900 5G,
in the LTE-NR BTS5900,
NSA DC
scenario BTS5900 5G



.AbnormRel.Ra abnormal SgNB BTS3900 5G,
dio releases in the BTS5900,
LTE-NR NSA
DC scenarios BTS5900 5G
caused by radio
layer issues

.AbnormRel.Ra abnormal SgNB BTS3900 5G,
dio.SUL releases in the BTS5900,
LTE-NR NSA
DC scenarios BTS5900 5G
caused by radio
layer issues of
the SUL

.Rel.SgNBTrigg SgNB releases BTS3900 5G,
er triggered by BTS5900,
SgNB in LTE-
NR NSA DC BTS5900 5G
scenarios
1911817842 N.NsaDc.SgNB Total Number BTS3900, N

.AbnormRel.Tr of abnormal BTS3900 5G,
ans SgNB releases BTS5900,
due to the
transport layer BTS5900 5G
in LTE-NR
NSA DC
scenarios

.AbnormRel abnormal SgNB BTS3900 5G,
releases BTS5900,
triggered by
SgNB in LTE- BTS5900 5G
NR NSA DC
scenarios
Description
These counters measure the total number of SgNB releases, the number of SgNB releases
initiated by the SgNB, the number of abnormal SgNB releases, and the number of abnormal
SgNB releases due to the radio layer and transport layer in LTE-NR NSA DC scenarios. The
signaling procedures related to these counters comply with section 10.4.1 in 3GPP TS 37.340
and section 9.1.4 in 3GPP TS 36.423.

Measurement Points
As shown at point A in Figure 1-4, the N.NsaDc.SgNB.Rel counter is incremented by 1 each
time the gNodeB receives an SgNB Release Request message from the eNodeB. As shown at
point A in Figure 1-5, the N.NsaDc.SgNB.Rel and N.NsaDc.SgNB.Rel.SgNBTrigger
counters are incremented by 1 each time the gNodeB sends an SgNB Release Required
message to the eNodeB. when the gNodeB sends an SgNB Release Required message to the
eNodeB, the counter value differs depending on the cause value in the message. If the cause
value is "Radio Connection With UE Lost" or "Failure in the Radio Interface", the
N.NsaDc.SgNB.AbnormRel.Radio counter is incremented by 1. If the uplink NARFCN of the
UEs on the gNodeB is on the SUL frequency, the N.NsaDc.SgNB.AbnormRel.Radio.SUL
counter is incremented by 1. The counter value is accumulated in the PSCell of the LTE-NR
NSA DC UE. if the cause value is "Transport Resource Unavailable", the
N.NsaDc.SgNB.AbnormRel.Trans counter is incremented by 1. If the cause value is "Radio
Connection With UE Lost", "Failure in the Radio Interface", "TDCoverall Expiry", "Transport
Resource Unavailable", or "Unspecified", the N.NsaDc.SgNB.AbnormRel counter is
incremented by 1.
Figure 1-4
Figure 1-5
Formula
None

Unit
None
Related Features
N.NsaDc.SgNB.Rel Multi-mode: MRFD-131162 NSA Networking based on

GSM: None EPC (NR)
UMTS: None
LTE: None
NR: None
N.NsaDc.SgNB.AbnormRel Multi-mode: MRFD-131162 NSA Networking based on

.Radio GSM: None EPC (NR)
UMTS: None
LTE: None
NR: FOFD-010205
UL and DL Decoupling

.Radio.SUL GSM: None EPC (NR)
UMTS: None
LTE: None
NR: FOFD-010205
N.NsaDc.SgNB.Rel.SgNBT Multi-mode: MRFD-131162 NSA Networking based on

rigger GSM: None EPC (NR)
UMTS: None
LTE: None
NR: None

.Trans GSM: None EPC (NR)
UMTS: None
LTE: None
NR: None


GSM: None EPC (NR)
UMTS: None
LTE: None
NR: None
1.1.1.4 Number of DRB Additions for LTE-NR NSA DC UEs
Counters
1911816754 N.NsaDc.DRB. Number of BTS3900, N

Add.Att DRB addition BTS3900 5G,
requests for BTS5900,
LTE-NR NSA
DC UEs on the BTS5900 5G
SgNB

Add.Succ successful DRB BTS3900 5G,
additions for BTS5900,
LTE-NR NSA
SgNB
Description
These counters measure the number of DRB addition requests and successful DRB additions
for LTE-NR NSA DC UEs in the PSCell. The signaling procedures related to these counters
comply with section 10.2.1 in 3GPP TS 37.340 and section 5.3.5 in 3GPP TS 36.331.
Measurement Points
As shown at point A in Figure 1-6, when the gNodeB receives an SgNB Addition Request
message from the eNodeB, the gNodeB adds the value of E-RAB number contained in "E-
RABs To Be Added List" to the N.NsaDc.DRB.Add.Att counter. As shown at point A in
Figure 1-7, when the gNodeB receives an SgNB Modification Request message from the
eNodeB, the gNodeB adds the value of E-RAB number contained in "E-RABs To Be Added
List" to the N.NsaDc.DRB.Add.Att counter. As shown at points B and C in Figure 1-6, when
the gNodeB receives an SgNB Reconfiguration Complete message from the eNodeB, the
gNodeB adds the value of E-RAB number contained in "E-RABs Admitted To Be Added
Item" of the SgNB Addition Request Acknowledge message to the N.NsaDc.DRB.Add.Succ
counter. As shown at points B and C in Figure 1-7, when the gNodeB receives an SgNB

Reconfiguration Complete message from the eNodeB, the gNodeB adds the value of E-RAB
number contained in "E-RABs Admitted To Be Added Item" of the SgNB Modification
Request Acknowledge message to the N.NsaDc.DRB.Add.Succ counter. These counter values
are accumulated in the PSCell of LTE-NR NSA DC UEs.
Figure 1-6
Figure 1-7
Formula
None
Unit
None

Related Features
N.NsaDc.DRB.Add.Att Multi-mode: MRFD-131162 NSA Networking based on

GSM: None EPC (NR)
UMTS: None
LTE: None
NR: None
N.NsaDc.DRB.Add.Succ Multi-mode: MRFD-131162 NSA Networking based on

GSM: None EPC (NR)
UMTS: None
LTE: None
NR: None
1.1.1.5 Number of DRB Releases for LTE-NR NSA DC UEs
Counters

Rel DRB releases BTS3900 5G,
for LTE-NR BTS5900,
NSA DC UEs
on the SgNB BTS5900 5G

AbnormRel abnormal DRB BTS3900 5G,
releases for BTS5900,
LTE-NR NSA
SgNB
Description
These counters measure the number of DRB releases and abnormal DRB releases for LTE-NR
NSA DC UEs in the PSCell. The signaling procedures related to these counters comply with
section 10.4.1 in 3GPP TS 37.340 and section 5.3.5 in 3GPP TS 36.331.
Measurement Points
As shown at points A and B in Figure 1-8, when the gNodeB receives an SgNB Modification
Confirm message from the eNodeB, the gNodeB adds the value of E-RAB number in "E-

RABs To Be Released Item" of the SgNB Modification Required message to the

N.NsaDc.DRB.Rel counter. As shown at point B in Figure 1-9, when the gNodeB receives an
SgNB Release Confirm message from the eNodeB, the gNodeB adds the value of E-RAB
number contained in "E-RABs To Be Released Item" to the N.NsaDc.DRB.Rel counter. As
shown at points B and C in Figure 1-10, when the gNodeB receives an SgNB
Reconfiguration Complete message from the eNodeB, the gNodeB adds the value of E-RAB
number contained in "E-RABs Admitted To Be Released Item" of the SgNB Modification
Request Acknowledge message to the N.NsaDc.DRB.Rel counter. As shown at point A in
Figure 1-11, when the gNodeB receives an SgNB Release Request message from the
eNodeB, the gNodeB adds the value of E-RAB number contained in "E-RABs To Be
Released Item" to the N.NsaDc.DRB.Rel counter. As shown at points A and B in Figure 1-8,
when the gNodeB receives an SgNB Modification Confirm message from the eNodeB, the
gNodeB adds the value of E-RAB number contained in "E-RABs To Be Released Item" to the
N.NsaDc.DRB.AbnormRel counter if the cause value contained in the SgNB Modification
Required message is "Radio Connection With UE Lost" or "Failure in the Radio Interface".
As shown at points A and B in Figure 1-9, when the gNodeB receives an SgNB Release
Confirm message from the eNodeB, the gNodeB adds the value of E-RAB number contained
in "E-RABs To Be Released Item" to the N.NsaDc.DRB.AbnormRel counter if the cause
value contained in the SgNB Release Required message is "Radio Connection With UE Lost"
or "Failure in the Radio Interface". These counter values are accumulated in the PSCell of
LTE-NR NSA DC UEs.
Figure 1-8

Figure 1-9
Figure 1-10
Figure 1-11
Formula
None
Unit
None

Related Features
N.NsaDc.DRB.Rel Multi-mode: MRFD-131162 NSA Networking based on

GSM: None EPC (NR)
UMTS: None
LTE: None
NR: None
N.NsaDc.DRB.AbnormRel Multi-mode: MRFD-131162 NSA Networking based on

GSM: None EPC (NR)
UMTS: None
LTE: None
NR: None
1.1.1.6 Number of Coverage-based SgNB Releases in LTE-NR NSA DC Scenarios
Counters

.Rel.Coverage coverage-based BTS3900 5G,
SgNB releases BTS5900,
in LTE-NR
NSA DC BTS5900 5G
scenarios
Description
These counters measure the total number of coverage-based SgNB releases in LTE-NR NSA
DC scenarios. The signaling procedures related to these counters comply with section 10.4.1
in 3GPP TS 37.340.
Measurement Points
As shown at point B in Figure 1-12, the N.NsaDc.SgNB.Rel.Coverage counter is incremented
by 1 each time the gNodeB receives an SgNB Release Confirm message from the eNodeB
after sending the eNodeB an SgNB Release Required message with the cause value of "SCG
Mobility". This cause value indicates PSCell release caused by coverage issues. These
counters are accumulated in the PSCell of LTE-NR NSA DC UEs.

Figure 1-12
Formula
None
Unit
None
Related Features
N.NsaDc.SgNB.Rel.Covera Multi-mode: MRFD-131162 NSA Networking based on

ge GSM: None EPC (NR)
UMTS: None
LTE: None
NR: None
1.1.2 DRB Measurement (Traffic.DRB.Cell)

Overview
The Traffic.DRB.Cell function subset measures the number of data radio bearers (DRBs) for
services with a specific QCI in a cell.
Counters
1911816972 N.Cell.Traffic.DRB Number of DRBs in BTS5900 5G:

a cell V100R015C10

None
1.1.2.1 Number of DRBs Occupied in an NR Cell
Counters
1911816972 N.Cell.Traffic. Number of BTS3900, N

DRB DRBs in a cell BTS3900 5G,
BTS5900,
BTS5900 5G
Description
This counter measures the number of DRBs occupied in an NR cell in a measurement period.
Measurement Points
The number of DRBs for services is sampled per second in a cell. At the end of a
measurement period, the average of these sampling results is used as the counter value.
Formula
None
Unit
None
Related Features
None
1.1.3 PDCP Measurement (PDCP.Cell)
Overview
The PDCP Measurement(PDCP.Cell) function subset measures the number and traffic of
SDUs received by the PDCP layer from the upper layer, the number and traffic of SDUs sent
by the PDCP layer to the upper layer, the number and traffic of PDUs sent by the PDCP layer
to the lower layer, the number and traffic of PDUs received by the PDCP layer from the lower
layer, and the number of SDUs lost in the uplink. This function subset belongs to the CU
Function.

Counters
1911816724 N.PDCP.UL.TrfSD Number of PDCP BTS5900 5G:

U.TxPackets SDUs for DRBs V100R013C10
transmitted to the BTS5900:
upper layer in a cell V100R013C10
BTS3900:
V100R015C00
1911816725 N.PDCP.DL.TrfSD Number of SDUs for BTS5900 5G:

U.RxPackets DRBs received at V100R013C10
the PDCP layer in a BTS5900:
cell V100R013C10
BTS3900:
V100R015C00
1911816726 N.PDCP.Vol.UL.Tr Traffic of PDCP BTS5900 5G:

fSDU.Tx SDUs for DRBs V100R013C10
upper layer in a cell V100R013C10
BTS3900:
V100R015C00
1911816727 N.PDCP.Vol.DL.Tr Traffic of SDUs for BTS5900 5G:

fSDU.Rx DRBs received at V100R013C10
the PDCP layer in a BTS5900:
cell V100R013C10
BTS3900:
V100R015C00
1911816728 N.PDCP.DL.TrfPD Number of PDCP BTS5900 5G:

U.TxPackets PDUs for DRBs V100R013C10
RLC layer in a cell V100R013C10
BTS3900:
V100R015C00
1911816729 N.PDCP.DL.TrfPD Number of PDCP BTS5900 5G:

U.ReTxPackets PDUs retransmitted V100R013C10
to the RLC layer in a BTS5900:
cell V100R013C10
BTS3900:
V100R015C00


1911816730 N.PDCP.UL.TrfPD Number of RLC BTS5900 5G:

U.RxPackets PDUs for DRBs V100R013C10
received at the BTS5900:
PDCP layer in a cell V100R013C10
BTS3900:
V100R015C00
1911816731 N.PDCP.Vol.DL.Tr Traffic of PDCP BTS5900 5G:

fPDU.Tx PDUs for DRBs V100R013C10
BTS3900:
V100R015C00
1911816732 N.PDCP.Vol.UL.Tr Traffic of RLC BTS5900 5G:

fPDU.Rx PDUs for DRBs V100R013C10
received at the BTS5900:
PDCP layer in a cell V100R013C10
BTS3900:
V100R015C00
1911816733 N.PDCP.UL.TrfSD Number of lost BTS5900 5G:

U.RxPacket.Loss uplink PDCP SDUs V100R013C10
for DRBs in a cell BTS5900:
V100R013C10
BTS3900:
V100R015C00
1911816734 N.PDCP.DL.X2U.T Number of PDCP BTS5900 5G:

rfPDU.TxPackets PDUs transmitted in V100R013C10
the downlink over BTS5900:
the X2 interface in a V100R013C10
cell BTS3900:
V100R015C00
1911816735 N.PDCP.DL.X2U.R Number of PDCP BTS5900 5G:

eqRetransPackets PDUs retransmitted V100R013C10
in the downlink over BTS5900:
the X2 interface in a V100R013C10
cell BTS3900:
V100R015C00
1911816736 N.PDCP.UL.X2U.T Number of PDCP BTS5900 5G:

rfPDU.RxPackets PDUs for DRBs V100R013C10
received in the BTS5900:
uplink over the X2 V100R013C10
interface in a cell BTS3900:
V100R015C00


1911816737 N.PDCP.Vol.DL.X2 Traffic of PDCP BTS5900 5G:

U.TrfPDU.Tx PDUs for DRBs V100R013C10
transmitted in the BTS5900:
downlink over the V100R013C10
X2 interface in a cell BTS3900:
V100R015C00
1911816738 N.PDCP.Vol.UL.X2 Traffic of PDCP BTS5900 5G:

U.TrfPDU.Rx PDUs for DRBs V100R013C10
received in the BTS5900:
uplink over the X2 V100R013C10
V100R015C00
None
1.1.3.1 Number of PDCP SDUs Transmitted to the Upper Layer in a Cell
Counters
1911816724 N.PDCP.UL.Trf Number of BTS3900, N

SDU.TxPackets PDCP SDUs BTS3900 5G,
for DRBs BTS5900,
transmitted to
the upper layer BTS5900 5G
in a cell
Description
This counter measures the total number of PDCP SDUs for DRBs transmitted to the upper
layer in a cell.
Measurement Points
This counter is incremented by 1 each time the PDCP layer transmits an SDU for DRBs to the
upper layer in a cell.
Formula
None

Unit
None
Related Features
N.PDCP.UL.TrfSDU.TxPac Multi-mode: None

kets GSM: None
UMTS: None
LTE: None
NR: FBFD-010011 Scheduling
1.1.3.2 Number of SDUs Received at the PDCP Layer in a Cell
Counters
1911816725 N.PDCP.DL.Trf Number of BTS3900, N

SDU.RxPackets SDUs for DRBs BTS3900 5G,
received at the BTS5900,
PDCP layer in a
cell BTS5900 5G
Description
This counter measures the total number of SDUs for DRBs received at the PDCP layer in a
cell.
Measurement Points
This counter is incremented by 1 each time the PDCP layer receives an SDU for DRBs from
the upper layer in a cell.
Formula
None
Unit
None

Related Features
N.PDCP.DL.TrfSDU.RxPac Multi-mode: None

kets GSM: None
UMTS: None
LTE: None
1.1.3.3 Traffic of PDCP SDUs Transmitted to the Upper Layer in a Cell
Counters
1911816726 N.PDCP.Vol.U Traffic of BTS3900, N

L.TrfSDU.Tx PDCP SDUs BTS3900 5G,
for DRBs BTS5900,
transmitted to
the upper layer BTS5900 5G
in a cell
Description
This counter measures the total traffic of PDCP SDUs for DRBs transmitted to the upper layer
in a cell.
Measurement Points
The total traffic of PDCP SDUs for DRBs transmitted to the upper layer is accumulated in a
cell, and the accumulated result is used as the value of this counter.
Formula
None
Unit
kbit

Related Features
N.PDCP.Vol.UL.TrfSDU.Tx Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.1.3.4 Traffic of SDUs Received at the PDCP Layer in a Cell
Counters
1911816727 N.PDCP.Vol.D Traffic of SDUs BTS3900, N

L.TrfSDU.Rx for DRBs BTS3900 5G,
PDCP layer in a
cell BTS5900 5G
Description
This counter measures the total traffic of SDUs for DRBs received at the PDCP layer in a cell.
Measurement Points
The total traffic of SDUs for DRBs received at the PDCP layer is accumulated in a cell, and
the accumulated result is used as the value of this counter.
Formula
None
Unit
kbit

Related Features
N.PDCP.Vol.DL.TrfSDU.Rx Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.1.3.5 Number of PDCP PDUs Transmitted to the RLC Layer in a Cell

(Retransmission Included)
Counters

PDU.TxPackets PDCP PDUs BTS3900 5G,
for DRBs BTS5900,
transmitted to
the RLC layer BTS5900 5G
in a cell

PDU.ReTxPack PDCP PDUs BTS3900 5G,
ets retransmitted to BTS5900,
the RLC layer
in a cell BTS5900 5G
Description
These counters measure the number of PDCP PDUs for DRBs transmitted to the RLC layer in
a cell. Note that the number of transmitted PDCP PDUs includes retransmitted ones.
Measurement Points
Note that the number of transmitted PDCP PDUs includes the number of retransmitted ones.
Formula
None
Unit
None

Related Features
N.PDCP.DL.TrfPDU.TxPac Multi-mode: None

kets GSM: None
UMTS: None
LTE: None
N.PDCP.DL.TrfPDU.ReTxP Multi-mode: None

ackets GSM: None
UMTS: None
LTE: None
1.1.3.6 Number of RLC PDUs Received at the PDCP Layer in a Cell
Counters
1911816730 N.PDCP.UL.Trf Number of BTS3900, N

PDU.RxPackets RLC PDUs for BTS3900 5G,
DRBs received BTS5900,
at the PDCP
layer in a cell BTS5900 5G
Description
This counter measures the total number of RLC PDUs for DRBs received at the PDCP layer
in a cell.
Measurement Points
This counter is incremented by 1 each time the PDCP layer receives a PDU for DRBs from
the RLC layer in a cell.
Formula
None
Unit
None

Related Features
N.PDCP.UL.TrfPDU.RxPac Multi-mode: None

kets GSM: None
UMTS: None
LTE: None
1.1.3.7 Traffic of PDCP PDUs Transmitted to the RLC Layer in a Cell
Counters
1911816731 N.PDCP.Vol.D Traffic of BTS3900, N

L.TrfPDU.Tx PDCP PDUs BTS3900 5G,
for DRBs BTS5900,
transmitted to
the RLC layer BTS5900 5G
in a cell
Description
This counter measures the total traffic of PDCP PDUs for DRBs transmitted to the RLC layer
in a cell.
Measurement Points
The total traffic of PDCP PDUs for DRBs transmitted to the RLC layer is accumulated in a
cell, and the accumulated result is used as the value of this counter.
Formula
None
Unit
kbit

Related Features
N.PDCP.Vol.DL.TrfPDU.Tx Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.1.3.8 Traffic of RLC PDUs Received at the PDCP Layer in a Cell
Counters
1911816732 N.PDCP.Vol.U Traffic of RLC BTS3900, N

L.TrfPDU.Rx PDUs for DRBs BTS3900 5G,
PDCP layer in a
cell BTS5900 5G
Description
This counter measures the total traffic of RLC PDUs for DRBs received at the PDCP layer in
a cell.
Measurement Points
The total traffic of RLC PDUs for DRBs received at the PDCP layer is accumulated in a cell,
and the accumulated result is used as the value of this counter.
Formula
None
Unit
kbit

Related Features
N.PDCP.Vol.UL.TrfPDU.Rx Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.1.3.9 Number of Lost PDCP SDUs in a Cell
Counters
1911816733 N.PDCP.UL.Trf Number of lost BTS3900, N

SDU.RxPacket. uplink PDCP BTS3900 5G,
Loss SDUs for DRBs BTS5900,
in a cell
BTS5900 5G
Description
This counter measures the total number of lost uplink PDCP SDUs for DRBs in a cell.
Measurement Points
This counter is incremented by 1 each time a PDCP SDU for DRBs is lost in the uplink in a
cell.
Formula
None
Unit
None

Related Features
N.PDCP.UL.TrfSDU.RxPac Multi-mode: None

ket.Loss GSM: None
UMTS: None
LTE: None
1.1.3.10 Number of PDCP PDUs Transmitted over the X2 Interface in a Cell

(Retransmission Included)
Counters
1911816734 N.PDCP.DL.X2 Number of BTS3900, N

U.TrfPDU.TxP PDCP PDUs BTS3900 5G,
ackets transmitted in BTS5900,
the downlink
over the X2 BTS5900 5G
interface in a
cell
1911816735 N.PDCP.DL.X2 Number of BTS3900, N

U.ReqRetransP PDCP PDUs BTS3900 5G,
ackets retransmitted in BTS5900,
the downlink
over the X2 BTS5900 5G
interface in a
cell
Description
This counter measures the total number of PDCP PDUs for DRBs transmitted in the downlink
over the X2 interface in a cell. Note that the number of transmitted PDCP PDUs includes the
retransmitted ones.
Measurement Points
The total number of downlink PDCP PDUs for DRBs transmitted over the X2 interface is
accumulated in a cell, and the accumulated result is used as the value of the corresponding
counter. Note that the number of transmitted PDCP PDUs includes the retransmitted ones.

Formula
None
Unit
None
Related Features
N.PDCP.DL.X2U.TrfPDU.T Multi-mode: None

xPackets GSM: None
UMTS: None
LTE: None
N.PDCP.DL.X2U.ReqRetra Multi-mode: None

nsPackets GSM: None
UMTS: None
LTE: None
1.1.3.11 Number of PDCP PDUs Received over the X2 Interface in a Cell
Counters
1911816736 N.PDCP.UL.X2 Number of BTS3900, N

U.TrfPDU.RxP PDCP PDUs BTS3900 5G,
ackets for DRBs BTS5900,
received in the
uplink over the BTS5900 5G
X2 interface in
a cell
Description
This counter measures the total number of PDCP PDUs for DRBs received in the uplink over
the X2 interface in a cell.

Measurement Points
This counter is incremented by 1 each time the PDCP layer receives a PDU for DRBs over the
X2 interface in a cell.
Formula
None
Unit
None
Related Features
N.PDCP.UL.X2U.TrfPDU.R Multi-mode: None

xPackets GSM: None
UMTS: None
LTE: None
1.1.3.12 Traffic of PDCP PDUs Transmitted over the X2 interface in a cell
Counters
1911816737 N.PDCP.Vol.D Traffic of BTS3900, N

L.X2U.TrfPDU PDCP PDUs BTS3900 5G,
.Tx for DRBs BTS5900,
transmitted in
the downlink BTS5900 5G
over the X2
interface in a
cell
Description
This counter measures the total traffic of PDCP PDUs for DRBs transmitted in the downlink
over the X2 interface in a cell.
Measurement Points
The total traffic of PDCP PDUs for DRBs transmitted over the X2 interface is accumulated in
a cell, and the accumulated result is used as the value of this counter.

Formula
None
Unit
kbit
Related Features
N.PDCP.Vol.DL.X2U.TrfPD Multi-mode: None

U.Tx GSM: None
UMTS: None
LTE: None
1.1.3.13 Traffic of PDCP PDUs Received over the X2 Interface in a Cell
Counters
1911816738 N.PDCP.Vol.U Traffic of BTS3900, N

L.X2U.TrfPDU PDCP PDUs BTS3900 5G,
.Rx for DRBs BTS5900,
received in the
uplink over the BTS5900 5G
X2 interface in
a cell
Description
This counter measures the total traffic of PDCP PDUs for DRBs received in the uplink over
the X2 interface in a cell.
Measurement Points
The total traffic of the PDUs for DRBs received at the PDCP layer over the X2 interface is
accumulated in a cell, and the accumulated result is used as the value of this counter.
Formula
None

Unit
kbit
Related Features
N.PDCP.Vol.UL.X2U.TrfPD Multi-mode: None

U.Rx GSM: None
UMTS: None
LTE: None
1.1.4 PDU Session Modification Measurement

(PDUSession.Modify.Cell)
Overview
The PDU session is the association between a UE and the data network that provides the PDU
connectivity service. The PDU session modification procedure is triggered by the core
network. The modification success rate in a cell represents the capability of the cell to provide
PDU session modification for users.
Counters
1911816964 N.PDUSession.AM Number of PDU BTS5900 5G:

F.Mod.Att session modification V100R015C10
attempts initiated by BTS3900:
the AMF V100R015C10
BTS5900:
V100R015C10
1911816965 N.PDUSession.AM Number of BTS5900 5G:

F.Mod.Succ successful PDU V100R015C10
session BTS3900:
modifications V100R015C10
initiated by the AMF BTS5900:
V100R015C10
None

1.1.4.1 Number of PDU Session Modifications in SA Scenarios
Counters
1911816964 N.PDUSession. Number of BTS3900, N

AMF.Mod.Att PDU session BTS3900 5G,
modification BTS5900,
attempts
initiated by the BTS5900 5G
AMF

AMF.Mod.Succ successful PDU BTS3900 5G,
session BTS5900,
modifications
AMF
Description
These counters measure the number of PDU session modification attempts and number of
successful PDU session modifications in a cell.
The signaling procedures related to these counters comply with section 8.2.3 in 3GPP TS
38.413.
Measurement Points
As shown at point A in Figure 1-13, when the gNodeB receives a PDU SESSION
RESOURCE MODIFY REQUEST message from the AMF, the measurement of
N.PDUSession.AMF.Mod.Att is triggered. If the PDU SESSION RESOURCE MODIFY
REQUEST message requests the modification of multiple PDU sessions, the number of PDU
sessions to be modified is accumulated into the value of N.PDUSession.AMF.Mod.Att.
As shown at point B in Figure 1-13, when the gNodeB sends a PDU SESSION RESOURCE
MODIFY RESPONSE message to the AMF, if this message indicates the successful
modification of multiple PDU sessions, the number of PDU sessions successfully modified is
accumulated into the value of N.PDUSession.AMF.Mod.Succ.

Figure 1-13
Formula
None
Unit
None
Related Features
None
1.1.5 PDU Session Setup Measurement (PDUSession.Est.Cell)

Overview
connectivity service. The setup success rate of PDU sessions in a cell represents the capability
of the cell to provide PDU sessions for users. The PDUSession.Est.Cell function subset
measures the number of PDU session requests, number of PDU session setup attempts, and
number of successful PDU session setups in a cell. The setup success rate of PDU sessions
can be calculated on the basis of the reported counters.

Counters
1911817003 N.PDUSession.Est. Number of PDU BTS5900 5G:

Att session setup V100R015C10
attempts BTS3900:
V100R015C10
BTS5900:
V100R015C10
1911817005 N.PDUSession.Est. Number of BTS5900 5G:

Succ successful PDU V100R015C10
session setups BTS3900:
V100R015C10
BTS5900:
V100R015C10
None
1.1.5.1 Number of PDU Session Setups in SA Scenarios
Counters

Est.Att PDU session BTS3900 5G,
setup attempts BTS5900,
BTS5900 5G

Est.Succ successful PDU BTS3900 5G,
session setups BTS5900,
BTS5900 5G
Description
These counters measure the total number of PDU session setup attempts and the total number
of successful PDU session setups in a cell. The PDU session setup process is generally
initiated by the UE when the UE needs to apply for services from the radio network. The PDU
session is set up by using the initial UE context setup procedure or a PDU session setup
procedure.

The signaling procedures related to these counters comply with sections 8.2.1 and 8.3.1 in
3GPP TS 38.413.
Measurement Points
As shown at point A in Figure 1-14 or Figure 1-15, when the gNodeB receives an INITIAL
CONTEXT SETUP REQUEST or PDU SESSION RESOURCE SETUP REQUEST message
from the AMF, the measurement of the N.PDUSession.Est.Att counter is triggered. If the
INITIAL CONTEXT SETUP REQUEST or PDU SESSION RESOURCE SETUP
REQUEST message requests the simultaneous setup of multiple PDU sessions, the total
number of PDU session setup attempts is accumulated based on the number of PDU sessions
setups in the message.
As shown at point B in Figure 1-14 or Figure 1-15, when the gNodeB sends an INITIAL
CONTEXT SETUP RESPONSE or PDU SESSION RESOURCE SETUP RESPONSE
message to the AMF, the measurement of the N.PDUSession.Est.Succ counter is triggered. If
the INITIAL CONTEXT SETUP RESPONSE or PDU SESSION RESOURCE SETUP
RESPONSE message indicates the successful setup of multiple PDU sessions, the number of
PDU sessions successfully set up is accumulated into the value of the counter.
Figure 1-14

Figure 1-15
Formula
None
Unit
None
Related Features
None
1.1.6 PDU Session Release Measurement (PDUSession.Rel.Cell)

Overview
connectivity service. The PDU session release measurement in a cell represents the capability
of the cell to release PDU sessions for users. The PDU Session.Rel.Cell function subset
measures the number of normal and abnormal PDU session releases in a cell. The counter is
incremented by 1 each time a PDU session is released.

Counters
1911816975 N.PDUSession.Abn Number of abnormal BTS5900 5G:

ormRel PDU session V100R015C10
releases BTS3900:
V100R015C10
BTS5900:
V100R015C10
1911816976 N.PDUSession.Nor Number of normal BTS5900 5G:

mRel PDU session V100R015C10
releases BTS3900:
V100R015C10
BTS5900:
V100R015C10
None
1.1.6.1 Number of PDU Session Releases in SA Scenarios
Counters

AbnormRel abnormal PDU BTS3900 5G,
session releases BTS5900,
BTS5900 5G

NormRel normal PDU BTS3900 5G,
session releases BTS5900,
BTS5900 5G
Description
These counters measure the total number of normal PDU session releases and the total
number of abnormal PDU session releases in a cell.
The signaling procedures related to these counters comply with sections 8.2.2, 8.3.2, and 8.3.3
in 3GPP TS 38.413.

Measurement Points
When the gNodeB initiates a release with the cause being "Successful handover", "Partial
handover", "Time critical handover", "User inactivity", "Redirection", "Normal release", or
"O&M intervention", the release is regarded as a normal release. Otherwise, the release is
regarded as an abnormal release.
As shown at point A in Figure 1-16, when the gNodeB sends a UE CONTEXT RELEASE
REQUEST message to the AMF, all the PDU sessions of the concerned UE are released. If
this release is regarded as a normal release, the measurement of the N.PDUSession.NormRel
counter is triggered. This counter will not be repeatedly measured when the AMF returns a
UE CONTEXT RELEASE COMMAND message to the gNodeB.
REQUEST message to the AMF, all the PDU sessions of the concerned UE are released. If
this release is regarded as an abnormal release, the measurement of the
N.PDUSession.AbnormRel counter is triggered.
If the UE has multiple PDU sessions, all the number of these PDU sessions is accumulated
into the value of the counter. This counter will not be repeatedly measured when the AMF
returns a UE CONTEXT RELEASE COMMAND message to the gNodeB.
As shown at point A in Figure 1-17, when the gNodeB receives a UE CONTEXT RELEASE
COMMAND message from the AMF, all the PDU sessions of the concerned UE are released.
The number of normal PDU session releases by the gNodeB is accumulated into the
N.PDUSession.NormRel counter.
RESOURCE RELEASE COMMAND message from the AMF, the measurement of the
N.PDUSession.NormRel counter is triggered. If the PDU SESSION RESOURCE RELEASE
COMMAND message requests the simultaneous release of multiple PDU sessions, the total
number of normal PDU session releases by the gNodeB is accumulated.
As shown at point A in Figure 1-19, when the gNodeB internally releases a PDU session by
sending a PDU SESSION RESOURCE NOTIFY message to the CN, the measurement of the
N.PDUSession.AbnormRel counter is triggered. If the PDU SESSION RESOURCE NOTIFY
message requests the simultaneous release of multiple PDU sessions, the total number of
abnormal PDU session releases by the gNodeB is accumulated into the
N.PDUSession.AbnormRel counter.
Figure 1-16

Figure 1-17
Figure 1-18

Figure 1-19
Formula
None
Unit
None
Related Features
None
1.1.7 QoS Flow Modification Measurement

(QosFlow.Modify.Cell)
Overview
The QosFlow.Modify.Cell function subset measures the number of QoS flow modification
attempts and the number of successful QoS flow modifications in a cell. The counter is
incremented by 1 each time a QoS flow is modified.

Counters
1911817070 N.QosFlow.AMF.M Number of BTS5900 5G:

od.Succ successful QoS flow V100R015C10
modifications BTS3900:
initiated by the AMF V100R015C10
BTS5900:
V100R015C10
1911817071 N.QosFlow.AMF.M Number of QoS BTS5900 5G:

od.Att flow modification V100R015C10
attempts initiated by BTS3900:
the AMF V100R015C10
BTS5900:
V100R015C10
None
1.1.7.1 Number of QoS Flow Modifications in SA Scenarios
Counters
1911817070 N.QosFlow.AM Number of BTS3900, N

F.Mod.Succ successful QoS BTS3900 5G,
flow BTS5900,
modifications
AMF
1911817071 N.QosFlow.AM Number of QoS BTS3900, N

F.Mod.Att flow BTS3900 5G,
attempts
AMF
Description
The counters measure the total numbers of QoS flow modification attempts and successful
QoS flow modifications in a cell.

The signaling procedures related to the counters comply with section 8.2.3 in 3GPP TS
38.413.
Measurement Points
RESOURCE MODIFY REQUEST message from the AMF, the measurement of
N.QosFlow.AMF.Mod.Att is triggered. If the PDU SESSION RESOURCE MODIFY
REQUEST message requests the modification of multiple QoS flows, the number of QoS
flows to be modified is accumulated into the value of N.QosFlow.AMF.Mod.Att.
MODIFY RESPONSE message to the AMF, if this message indicates the successful
modification of multiple QoS flows, the number of QoS flows successfully modified is
accumulated into the value of N.QosFlow.AMF.Mod.Succ.
Figure 1-20
Formula
None
Unit
None
Related Features
None

1.1.8 QoS Flow Setup Failure Measurement

(QosFlow.EstFail.Cell)
Overview
QoS flow is a service flow with the same QoS attribute (indicated by 5QI in 5G). The
QosFlow.EstFail.Cell function subset measures the number of QoS flow setup failures for
different causes in a cell. The counter is incremented by 1 each time a QoS flow setup fails.
Counters
1911817033 N.QosFlow.FailEst. Number of QoS BTS5900 5G:

AMF flow setup failures V100R015C10
because of faults on BTS3900:
the core network V100R015C10
BTS5900:
V100R015C10

RNL flow setup failures V100R015C10
because of faults at BTS3900:
the radio network V100R015C10
layer BTS5900:
V100R015C10

TNL flow setup failures V100R015C10
the transport V100R015C10
network layer BTS3900:
V100R015C10

UeNoReply flow setup failures V100R015C10
because of no BTS3900:
responses from the V100R015C10
UE BTS5900:
V100R015C10

SecurModeFail flow setup failures V100R015C10
because of security BTS3900:
mode configuration V100R015C10
failures BTS5900:
V100R015C10

None
1.1.8.1 Number of QoS Flow Setup Failures in SA Scenarios
Counters
1911817033 N.QosFlow.Fail Number of QoS BTS3900, N

Est.AMF flow setup BTS3900 5G,
failures because BTS5900,
of faults on the
core network BTS5900 5G

Est.RNL flow setup BTS3900 5G,
of faults at the
radio network BTS5900 5G
layer

Est.TNL flow setup BTS3900 5G,
of faults at the
transport BTS5900 5G
network layer

Est.UeNoReply flow setup BTS3900 5G,
of no responses
from the UE BTS5900 5G

Est.SecurMode flow setup BTS3900 5G,
Fail failures because BTS5900,
of security
mode BTS5900 5G
configuration
failures
Description
These counters measure the number of QoS flow setup failures for different causes in a cell.
in 3GPP TS 38.413.

Measurement Points
A validity check failure may be caused by an error in the message (excluding ASN decoding
error). A cross between the initial UE context setup procedure and other procedures occurs
when the gNodeB receives a UE CONTEXT RELEASE COMMAND message from the
AMF during an initial UE context setup procedure.
As shown at point A in Figure 1-21, the measurement of the N.QosFlow.FailEst.AMF

counter is triggered each time the gNodeB fails to check the validity of the INITIAL
CONTEXT SETUP REQUEST message received from the AMF or the message cannot be
processed because of a cross between the initial UE context setup procedure and other
procedures. If the INITIAL CONTEXT SETUP REQUEST message requests the
simultaneous setup of multiple QoS flows, this counter is incremented by the number of failed
QoS flow setups.

counter is triggered each time the gNodeB fails to check the validity of the PDU SESSION
RESOURCE SETUP REQUEST message received from the AMF or the message cannot be
processed because of a cross between the PDU session setup procedure and other procedures.
If the PDU SESSION RESOURCE SETUP REQUEST message requests the simultaneous
setup of multiple QoS flows, this counter is incremented by the number of failed QoS flow
setups. A validity check failure may be caused by an error in the message (excluding ASN
decoding error). A message handling failure because of a cross between the PDU session
setup procedure and other procedures may occur when the gNodeB receives a UE CONTEXT
RELEASE COMMAND message from the AMF during a PDU session setup procedure.

counter is triggered each time the gNodeB fails to check the validity of the PDU SESSION
RESOURCE MODIFY REQUEST message received from the AMF, or the message cannot
be processed because of a cross between the PDU session modification procedure and other
procedures. If the PDU SESSION RESOURCE MODIFY REQUEST message requests the
simultaneous setup of multiple QoS flows, this counter is incremented by the number of failed
QoS flow setups. A validity check failure may be caused by an error in the message
(excluding ASN decoding error). A message handling failure because of a cross between the
PDU session modification procedure and other procedures may occur when the gNodeB
receives a UE CONTEXT RELEASE COMMAND message from the AMF during a PDU
session modification procedure.
As shown at point A in Figure 1-21, the measurement of the corresponding counter is

triggered each time the gNodeB fails to set up a QoS flow because of a message handling
error after the gNodeB receives an INITIAL CONTEXT SETUP REQUEST message from
the AMF, and then sends an INITIAL CONTEXT SETUP RESPONSE message or an
INITIAL CONTEXT SETUP FAILURE message to the AMF. If the QoS flow setup fails
because of faults at the transport network layer, the N.QosFlow.FailEst.TNL counter is
measured. For details on the faults at the transport network layer, see 3GPP TS 38.413. If the
QoS flow setup fails because of faults at the radio network layer, the N.QosFlow.FailEst.RNL
counter is measured. For details on faults at the radio network layer, see 3GPP TS 38.413.

error after the gNodeB receives a PDU SESSION RESOURCE SETUP REQUEST message
from the AMF, and then sends a PDU SESSION RESOURCE SETUP RESPONSE message
to the AMF. If the QoS flow setup fails because of faults at the transport network layer, the
N.QosFlow.FailEst.TNL counter is measured. For details on the faults at the transport
network layer, see 3GPP TS 38.413. If the QoS flow setup fails because of faults at the radio

network layer, the N.QosFlow.FailEst.RNL counter is measured. For details on faults at the
radio network layer, see 3GPP TS 38.413.

error after the gNodeB receives a PDU SESSION RESOURCE MODIFY REQUEST
message from the AMF, and then sends a PDU SESSION RESOURCE MODIFY
RESPONSE message to the AMF. If the QoS flow setup fails because of faults at the transport
network layer, the N.QosFlow.FailEst.TNL counter is measured. For details on the faults at
the transport network layer, see 3GPP TS 38.413. If the QoS flow setup fails because of faults
at the radio network layer, the N.QosFlow.FailEst.RNL counter is measured. For details about
faults at the radio network layer, see 3GPP TS 38.413.
As shown at point A in Figure 1-24, the measurement of the

N.QosFlow.FailEst.SecurModeFail counter is triggered each time the gNodeB sends a
Security Mode Command message to the UE after receiving an INITIAL CONTEXT SETUP
REQUEST message from the AMF but receives a Security Mode Failure message from the
UE. If the INITIAL CONTEXT SETUP REQUEST message requests the simultaneous setup
of multiple QoS flows, the counter is incremented according to the number of required QoS
flow setups.
As shown at point A, B, or C in Figure 1-25, the measurement of the

N.QosFlow.FailEst.UeNoReply counter is triggered each time the gNodeB receives no
response from a UE before the corresponding timer expires after the gNodeB sends a
signaling message to the UE in an initial UE context setup procedure. If the INITIAL
CONTEXT SETUP REQUEST message requests the simultaneous setup of multiple QoS
flows, this counter is incremented by the number of failed QoS flow setups.
As shown at point A in Figure 1-26 or Figure 1-27, the measurement of the

N.QosFlow.FailEst.UeNoReply counter is triggered each time the gNodeB receives no
response from a UE before the corresponding timer expires after the gNodeB sends a
signaling message to the UE in a PDU session setup or modification procedure. If the PDU
SESSION RESOURCE SETUP REQUEST message or the PDU SESSION RESOURCE
MODIFY REQUEST message requests the simultaneous setup of multiple QoS flows, this
counter is incremented by the number of failed QoS flow setups.
Figure 1-21

Figure 1-22
Figure 1-23

Figure 1-24

Figure 1-25

Figure 1-26
Figure 1-27
Formula
None
Unit
None

Related Features
None
1.1.9 QoS Flow Setup Measurement (QosFlow.Est.Cell)
Overview
QoS flow is a service flow with the same QoS attribute (indicated by 5QI in 5G). The success
rate of the QoS flow setup represents the capability of a cell to set up QoS flows. The
QosFlow.Est.Cell function subset measures the number of QoS flow setup attempts and the
number of successful QoS flow setups in a cell. The counter is incremented by 1 each time a
QoS flow is set up.
Counters
1911816962 N.QosFlow.Est.Att Number of QoS BTS5900 5G:

flow setup attempts V100R015C10
BTS3900:
V100R015C10
BTS5900:
V100R015C10
1911816963 N.QosFlow.Est.Suc Number of BTS5900 5G:

c successful QoS flow V100R015C10
setups BTS3900:
V100R015C10
BTS5900:
V100R015C10
None
1.1.9.1 Number of QoS Flow Setups in SA Scenarios
Counters
1911816962 N.QosFlow.Est. Number of QoS BTS3900, N

Att flow setup BTS3900 5G,
attempts BTS5900,
BTS5900 5G


1911816963 N.QosFlow.Est. Number of BTS3900, N

Succ successful QoS BTS3900 5G,
flow setups BTS5900,
BTS5900 5G
Description
These counters measure the number of QoS flow setup attempts and number of successful
QoS flow setups in a cell.
in 3GPP TS 38.413.
Measurement Points
As shown at point A in Figure 1-28 or Figure 1-29, when the gNodeB receives an INITIAL
from the AMF, the measurement of N.QosFlow.Est.Att is triggered. If the INITIAL
requests the setup of multiple QoS flows, the number of QoS flows to be set up is
accumulated into the value of the counter.
RESOURCE MODIFY REQUEST message from the AMF, requesting the setup of QoS
flows, the measurement of N.QosFlow.Est.Att is triggered. If the message requests the setup
of multiple QoS flows, the number of QoS flows to be set up is accumulated into the value of
the counter.
As shown at point B in Figure 1-28 or Figure 1-29, when the gNodeB sends an INITIAL
message to the AMF, the measurement of N.QosFlow.Est.Succ is triggered. If the INITIAL
message indicates the successful setup of multiple QoS flows, the number of QoS flows
successfully set up is accumulated into the value of the counter.
MODIFY RESPONSE message to the AMF, the measurement of N.QosFlow.Est.Succ is
triggered. If the PDU SESSION RESOURCE MODIFY RESPONSE message indicates the
successful setup of multiple QoS flows, the number of QoS flows successfully set up is
accumulated into the value of the counter.

Figure 1-28
Figure 1-29

Figure 1-30
Formula
None
Unit
None
Related Features
None
1.1.10 QoS Flow Release Measurement (QosFlow.Rel.Cell)

Overview
QoS flow is a service flow with the same QoS attribute (indicated by 5QI in 5G). The QoS
flow release measurement represents the capability of a cell to release QoS flows. The
QosFlow.Rel.Cell function subset measures the number of normal and abnormal QoS flow
releases in a cell. The counter is incremented by 1 each time a QoS flow is released.

Counters
1911816966 N.QosFlow.NormR Number of normal BTS5900 5G:

el QoS flow releases V100R015C10
BTS3900:
V100R015C10
BTS5900:
V100R015C10
1911816967 N.QosFlow.Abnor Number of abnormal BTS5900 5G:

mRel QoS flow releases V100R015C10
BTS3900:
V100R015C10
BTS5900:
V100R015C10

mRel.AMF QoS flow releases V100R015C10
triggered by the core BTS3900:
network V100R015C10
BTS5900:
V100R015C10
1911816969 N.QosFlow.NormR Number of normal BTS5900 5G:

el.AMF QoS flow releases V100R015C10
network V100R015C10
BTS5900:
V100R015C10

mRel.RNL QoS flow releases V100R015C10
the radio network V100R015C10
layer BTS5900:
V100R015C10

mRel.TNL QoS flow releases V100R015C10
the transport V100R015C10
V100R015C10

Root Counter Level-1 Counter
N.QosFlow.AbnormRel N.QosFlow.AbnormRel.TNL
N.QosFlow.AbnormRel N.QosFlow.AbnormRel.RNL
1.1.10.1 Number of QoS Flow Releases in SA Networking
Counters
1911816966 N.QosFlow.Nor Number of BTS3900, N

mRel normal QoS BTS3900 5G,
flow releases BTS5900,
BTS5900 5G
1911816967 N.QosFlow.Ab Number of BTS3900, N

normRel abnormal QoS BTS3900 5G,
BTS5900 5G

normRel.AMF abnormal QoS BTS3900 5G,
triggered by the
1911816969 N.QosFlow.Nor Number of BTS3900, N

mRel.AMF normal QoS BTS3900 5G,
triggered by the

normRel.RNL abnormal QoS BTS3900 5G,
because of
faults at the BTS5900 5G
radio network
layer



normRel.TNL abnormal QoS BTS3900 5G,
because of
faults at the BTS5900 5G
transport
network layer
Description
These counters measure the total number of normal QoS flow releases, total number of
abnormal QoS flow releases, and number of abnormal QoS flow releases due to different
faults in a cell.
The signaling procedures related to these counters comply with sections 8.2.2, 8.2.3, 8.3.2,
and 8.3.3 in 3GPP TS 38.413.
Measurement Points
"O&M intervention", the release is regarded as a normal release. All other release causes are
regarded as abnormal releases.
When the AMF initiates a release with the cause being "User inactivity", "Load balancing
TAU required", "Release due to CN-detected mobility", "Normal release", or "O&M
intervention", the release is regarded as a normal release. All other release causes are regarded
as abnormal releases.
REQUEST message to the AMF, all the QoS flows of the concerned UE are released. If this
release is regarded as a normal release, the value of the N.QosFlow.NormRel counter is
incremented by 1. This counter will not be repeatedly measured when the AMF returns a UE
CONTEXT RELEASE COMMAND message to the gNodeB.
COMMAND message from the AMF, all the QoS flows of the concerned UE are released.
The number of normally released QoS flows is accumulated into the value of the
N.QosFlow.NormRel counter.
RESOURCE RELEASE COMMAND message from the AMF, the measurement of
N.QosFlow.NormRel is triggered. If the PDU SESSION RESOURCE RELEASE
COMMAND message requests the simultaneous release of multiple QoS flows, the total
number of QoS flows to be released is accumulated into the counter value.
RESOURCE MODIFY REQUEST message from the AMF, requesting the release of QoS
flows, the measurement of N.QosFlow.NormRel is triggered. If the PDU SESSION
RESOURCE MODIFY REQUEST message requests the simultaneous release of multiple

QoS flows, the total number of QoS flows to be released is accumulated into the counter
value.
As shown at point A in Figure 1-32, when the AMF proactively sends a UE CONTEXT
RELEASE COMMAND message to the gNodeB, all the QoS flows of the concerned UE are
released. If the UE CONTEXT RELEASE COMMAND message requests the release of
multiple QoS flows, and if the release cause indicates normal releases, the total number of
normal QoS flow releases initiated by the AMF is accumulated into the value of the
N.QosFlow.NormRel.AMF counter.
As shown at point A in Figure 1-33, when the AMF proactively sends a PDU SESSION
RESOURCE RELEASE COMMAND message to the gNodeB, with a cause indicating
normal release, the total number of QoS flows requested to be released by the AMF is
accumulated into the value of the N.QosFlow.NormRel.AMF counter.
As shown at point A in Figure 1-34, when the AMF proactively sends a PDU SESSION
RESOURCE MODIFY REQUEST message to the gNodeB, with a cause indicating normal
release, the total number of QoS flows requested to be released by the AMF is accumulated
into the value of the N.QosFlow.NormRel.AMF counter.
REQUEST message to the AMF, all the QoS flows of the concerned UE are released. If the
release cause indicates abnormal release, the measurement of the N.QosFlow.AbnormRel
counter is triggered.
If the concerned UE has multiple QoS flows, all the number of these QoS flows is
accumulated into the value of the counter. This counter will not be repeatedly measured when
the AMF returns a UE CONTEXT RELEASE COMMAND message to the gNodeB.
As shown at point A in Figure 1-35, when the gNodeB internally releases QoS flows by
sending a PDU SESSION RESOURCE NOTIFY message to the CN, the measurement of the
N.QosFlow.AbnormRel counter is triggered. If the PDU SESSION RESOURCE NOTIFY
message requests the simultaneous release of multiple QoS flows, the total number of
abnormal QoS flow releases by the gNodeB is accumulated into the counter value. When the
release is caused by faults at the transport network layer, the measurement of the
N.QosFlow.AbnormRel.TNL counter is triggered. For details on faults at the transport
network layer, see 3GPP TS 36.413.
REQUEST message to the AMF, all the QoS flows of the concerned UE are released.
When the release is caused by faults at the radio network layer and the release cause indicates
abnormal release, the measurement of N.QosFlow.AbnormRel.RNL is triggered. For details
on faults at the radio network layer, see 3GPP TS 38.413.
When the release is caused by faults at the transport network layer and the release cause
indicates abnormal release, the measurement of N.QosFlow.AbnormRel.TNL is triggered. For
details on faults at the transport network layer, see 3GPP TS 38.413. The corresponding
counter value is accumulated, and will not be repeatedly measured when the AMF responds
with a UE CONTEXT RELEASE COMMAND message.
As shown at point A in Figure 1-32, the AMF proactively initiates a UE context release
procedure by sending a UE CONTEXT RELEASE COMMAND message to the gNodeB. On
receiving the message, the gNodeB releases all QoS flows of the concerned UE. If the release
cause indicates abnormal release, the measurement of the N.QosFlow.AbnormRel.AMF
counter is triggered. If the concerned UE has multiple QoS flows, all the number of these QoS
flows is accumulated into the value of the counter.

As shown at point A in Figure 1-33, the AMF proactively initiates a PDU session release
procedure by sending a PDU SESSION RESOURCE RELEASE COMMAND message to the
gNodeB. On receiving the message, the gNodeB determines that the release is an abnormal
release according to the cause value, and the measurement of the
N.QosFlow.AbnormRel.AMF counter is triggered. If the PDU SESSION RESOURCE
RELEASE COMMAND message requests the simultaneous release of multiple QoS flows,
all the number of these QoS flows is accumulated into the N.QosFlow.AbnormRel.AMF
counter.
As shown at point A in Figure 1-34, the AMF proactively initiates a PDU session
modification procedure by sending a PDU SESSION RESOURCE MODIFY REQUEST
message to the gNodeB. On receiving the message, the gNodeB determines that the release is
an abnormal release according to the cause value, and the measurement of the
N.QosFlow.AbnormRel.AMF counter is triggered. If the PDU SESSION RESOURCE
MODIFY REQUEST message requests the simultaneous release of multiple QoS flows, all
the number of these QoS flows is accumulated into the N.QosFlow.AbnormRel.AMF counter.
Figure 1-31

Figure 1-32
Figure 1-33

Figure 1-34
Figure 1-35
Formula
None
Unit
None
Related Features
None

1.1.11 RRC Setup Failure Measurement (RRC.SetupFail.Cell)

Overview
An RRC connection is a Uu interface connection for carrying user signaling messages. The
setup success rate of RRC connections in a cell represents the capability of the cell to provide
RRC connections for users. The RRC.SetupFail.Cell function subset measures the number of
RRC connection setup failures for different causes in a cell.
Counters
1911816998 N.RRC.SetupReqF Number of RRC BTS5900 5G:

ail.Rej Setup Request V100R015C10
rejections
1911816999 N.RRC.SetupReqF Number of RRC BTS5900 5G:

ail.UeNoReply connection setup V100R015C10
failures due to no
responses from the
UE
1911817001 N.RRC.SetupReq. Number of times the BTS5900 5G:

Msg.Disc.FlowCtrl RRC connection V100R015C10
request message is
discarded due to
flow control
None
1.1.11.1 Number of RRC Setup Failures in SA Scenarios
Counters
1911816998 N.RRC.SetupR Number of BTS3900 5G, N

eqFail.Rej RRC Setup BTS5900 5G
Request
rejections



eqFail.UeNoRe RRC BTS5900 5G
ply connection
setup failures
due to no
responses from
the UE

eq.Msg.Disc.Fl times the RRC BTS5900 5G
owCtrl connection
request message
is discarded due
to flow control
Description
The counters measure the number of RRC connection setup failures due to different causes in
a cell and the number of times the RRC connection request message is discarded due to flow
control. The RRC Reject message is an RRC signaling message sent from the gNodeB to the
UE to inform the UE that the access is rejected by the gNodeB.
38.331.
Measurement Points
As shown at point A in Figure 1-36, the N.RRC.SetupReqFail.Rej counter is incremented by
1 each time the cell sends an RRC Reject message to a UE after receiving an RRC Setup
Request message from the UE.
As shown at point A in Figure 1-37, the N.RRC.SetupReqFail.UeNoReply counter is
incremented by 1 each time the cell sends an RRC Setup message to a UE after receiving an
RRC Setup Request message from the UE and the cell does not receive an RRC Setup
Complete within the specified time.
As shown at point A in Figure 1-38, the N.RRC.SetupReq.Msg.Disc.FlowCtrl counter is
incremented by 1 each time the cell discards an RRC Setup Request message sent from the
UE due to flow control. This counter includes the number of retransmitted RRC Setup
Request messages.

Figure 1-36
Figure 1-37

Figure 1-38
Formula
None
Unit
None
Related Features
None
1.1.12 RRC Setup Measurement (RRC.Setup.Cell)

Overview
An RRC connection is a Uu interface connection for carrying user signaling messages. The
setup success rate of RRC connections in a cell represents the capability of the cell to provide
RRC connections for users. The RRC.Setup.Cell function subset measures the number of
RRC connection setup requests, number of RRC connection setup attempts, and number of
successful RRC connection setups in a cell. The setup success rate of RRC connections can be
calculated on the basis of the reported counters.

Counters
1911816942 N.RRC.SetupReq.S Number of BTS5900 5G:

ucc.Emc successful RRC V100R015C10
connection setups
with a cause value
of emergency

ucc.MoVoiceCall successful RRC V100R015C10
connection setups
with a cause value
of mo-VoiceCall
1911816944 N.RRC.SetupReq. Number of RRC BTS5900 5G:

Att.MoSig connection setup V100R015C10
requests with a
cause value of mo-
Signalling
1911816945 N.RRC.SetupSucc. Number of BTS5900 5G:

ReEst successful RRC V100R015C10
connection setups
caused by RRC
reestablishment

Att.HighPri connection setup V100R015C10
requests with a
cause value of
highPriorityAccess

Att.Emc connection setup V100R015C10
requests with a
cause value of
emergency

ucc.Mt successful RRC V100R015C10
connection setups
with a cause value
of mt-Access

ucc.MoSig successful RRC V100R015C10
connection setups
with a cause value
of mo-Signalling



ucc successful RRC V100R015C10
connection setups

Att.MoData connection setup V100R015C10
requests with a
cause value of mo-
Data

Msg connection setup V100R015C10
requests
(retransmission
included)

ucc.MoData successful RRC V100R015C10
connection setups
with a cause value
of mo-Data

Att connection setup V100R015C10
requests

Att.MoVoiceCall connection setup V100R015C10
requests with a
cause value of mo-
VoiceCall
1911816956 N.RRC.Setup.ReEs Number of RRC BTS5900 5G:

t connection setups V100R015C10
caused by RRC
reestablishment

ucc.HighPri successful RRC V100R015C10
connection setups
with a cause value
of
highPriorityAccess

Att.Mt connection setup V100R015C10
requests with a
cause value of mt-
Access
1911816959 N.RRC.Setup Number of RRC BTS5900 5G:

connection setups V100R015C10



Att.MoVideoCall connection setup V100R015C10
requests with a
cause value of mo-
VideoCall

Att.MoSms connection setup V100R015C10
requests with a
cause value of mo-
SMS

Att.MpsPri connection setup V100R015C10
requests with a
cause value of mps-
PriorityAccess

ucc.MoVideoCall successful RRC V100R015C10
connection setups
with a cause value
of mo-VideoCall

ucc.MoSms successful RRC V100R015C10
connection setups
with a cause value
of mo-SMS

ucc.MpsPri successful RRC V100R015C10
connection setups
with a cause value
of mps-
PriorityAccess

ucc.McsPri successful RRC V100R015C10
connection setups
with a cause value
of mcs-
PriorityAccess

Att.McsPri connection setup V100R015C10
requests with a
cause value of mcs-
PriorityAccess

None
1.1.12.1 Number of RRC Connection Setups in SA Scenarios
Counters

eq.Succ.Emc successful RRC BTS5900 5G
connection
setups with a
cause value of
emergency

eq.Succ.MoVoi successful RRC BTS5900 5G
ceCall connection
setups with a
cause value of
mo-VoiceCall

eq.Att.MoSig RRC BTS5900 5G
connection
setup requests
with a cause
value of mo-
Signalling
1911816945 N.RRC.SetupS Number of BTS3900 5G, N

ucc.ReEst successful RRC BTS5900 5G
connection
setups caused
by RRC
reestablishment

eq.Att.HighPri RRC BTS5900 5G
connection
setup requests
with a cause
value of
highPriorityAcc
ess



eq.Att.Emc RRC BTS5900 5G
connection
setup requests
with a cause
value of
emergency

eq.Succ.Mt successful RRC BTS5900 5G
connection
setups with a
cause value of
mt-Access

eq.Succ.MoSig successful RRC BTS5900 5G
connection
setups with a
cause value of
mo-Signalling

eq.Succ successful RRC BTS5900 5G
connection
setups

eq.Att.MoData RRC BTS5900 5G
connection
setup requests
with a cause
value of mo-
Data

eq.Msg RRC BTS5900 5G
connection
setup requests
(retransmission
included)

eq.Succ.MoDat successful RRC BTS5900 5G
a connection
setups with a
cause value of
mo-Data



eq.Att RRC BTS5900 5G
connection
setup requests

eq.Att.MoVoice RRC BTS5900 5G
Call connection
setup requests
with a cause
value of mo-
VoiceCall
1911816956 N.RRC.Setup.R Number of BTS3900 5G, N

eEst RRC BTS5900 5G
connection
setups caused
by RRC
reestablishment

eq.Succ.HighPr successful RRC BTS5900 5G
i connection
setups with a
cause value of
highPriorityAcc
ess

eq.Att.Mt RRC BTS5900 5G
connection
setup requests
with a cause
value of mt-
Access
1911816959 N.RRC.Setup Number of BTS3900 5G, N

RRC BTS5900 5G
connection
setups

eq.Att.MoVideo RRC BTS5900 5G
Call connection
setup requests
with a cause
value of mo-
VideoCall



eq.Att.MoSms RRC BTS5900 5G
connection
setup requests
with a cause
value of mo-
SMS

eq.Att.MpsPri RRC BTS5900 5G
connection
setup requests
with a cause
value of mps-
PriorityAccess

eq.Succ.MoVid successful RRC BTS5900 5G
eoCall connection
setups with a
cause value of
mo-VideoCall

eq.Succ.MoSms successful RRC BTS5900 5G
connection
setups with a
cause value of
mo-SMS

eq.Succ.MpsPri successful RRC BTS5900 5G
connection
setups with a
cause value of
mps-
PriorityAccess

eq.Succ.McsPri successful RRC BTS5900 5G
connection
setups with a
cause value of
mcs-
PriorityAccess



eq.Att.McsPri RRC BTS5900 5G
connection
setup requests
with a cause
value of mcs-
PriorityAccess
Description
These counters measure the number of RRC connection setup requests with different causes
received by a gNodeB in different cells. The RRC Setup Request message is the first RRC
signaling message sent from the UE to the gNodeB. This message is used to request the setup
of an RRC connection.
This counter measures the total number of RRC connection setup attempts, that is, the number
of times the gNodeB responds to the message received from the UE (retransmission excluded)
and sends an RRC Setup message to the UE. The RRC Setup message is an RRC signaling
message sent from the gNodeB to a UE. The message is used to inform the UE of the related
configuration information and the result of the RRC connection setup.
These counters measure the number of successful RRC connection setups with different
causes, that is, the number of times the gNodeB receives an RRC Setup Complete message
from the UE. The RRC Setup Complete message is an RRC signaling message sent from a
UE to the gNodeB. The message is used to inform the gNodeB that the RRC connection setup
is complete and informs the gNodeB of the carried NAS signaling information and the
information about PLMN selection.
38.331.
This counter measures the number of RRC connection setups caused by RRC reestablishment,
that is, the number of times the gNodeB sends an RRC Setup message to the UE after
receiving an RRC Reestablishment Request message from the UE but failing to query the
UE's context information.
This counter measures the number of successful RRC connection setups caused by RRC
reestablishment, that is, the number of times the gNodeB receives an RRC Setup Complete
message from the UE after sending an RRC Setup message to the UE in the following
scenarios: The gNodeB receives an RRC Reestablishment Request message from the UE but
fails to query the UE's context information.
38.331.
Measurement Points
As shown at point A in Figure 1-39, when the gNodeB receives an RRC Setup Request
message from a UE, the corresponding counter is measured. Details are as follows:

The N.RRC.SetupReq.Msg counter is incremented by 1, and the measurement includes the

number of retransmitted RRC Setup Request messages.
The N.RRC.SetupReq.Att counter is incremented by 1, and the measurement does not include
the number of retransmitted RRC Setup Request messages.
If the value of the Establishment Cause information element (IE) in the RRC Setup Request
message is "emergency", the N.RRC.SetupReq.Att.Emc counter is incremented by 1. The
measurement does not include the number of retransmitted RRC Setup Request messages.
If the value of the Establishment Cause IE in the RRC Setup Request message is
"highPriorityAccess", the N.RRC.SetupReq.Att.HighPri counter is incremented by 1. The
If the value of the Establishment Cause IE in the RRC Setup Request message is "mt-Access",
the N.RRC.SetupReq.Att.Mt counter is incremented by 1. The measurement does not include
the number of retransmitted RRC Setup Request messages.
If the value of the Establishment Cause IE in the RRC Setup Request message is "mo-
VoiceCall", the N.RRC.SetupReq.Att.MoVoiceCall counter is incremented by 1. The
Signalling", the N.RRC.SetupReq.Att.MoSig counter is incremented by 1. The measurement
does not include the number of retransmitted RRC Setup Request messages.
If the value of the Establishment Cause IE in the RRC Setup Request message is "mo-Data",
the N.RRC.SetupReq.Att.MoData counter is incremented by 1. The measurement does not
include the number of retransmitted RRC Setup Request messages.
VideoCall", the N.RRC.SetupReq.Att.MoVideoCall counter is incremented by 1. The
If the value of the Establishment Cause IE in the RRC Setup Request message is "mo-SMS",
the N.RRC.SetupReq.Att.MoSms counter is incremented by 1. The measurement does not
include the number of retransmitted RRC Setup Request messages.
If the value of the Establishment Cause IE in the RRC Setup Request message is "mps-
PriorityAccess", the N.RRC.SetupReq.Att.MpsPri counter is incremented by 1. The
If the value of the Establishment Cause IE in the RRC Setup Request message is "mcs-
PriorityAccess", the N.RRC.SetupReq.Att.McsPri counter is incremented by 1. The
As shown at point B in Figure 1-39, when the gNodeB sends an RRC Setup message to the
UE after receiving an RRC Setup Request message (retransmission excluded) from the UE,
the N.RRC.Setup counter is incremented by 1.
As shown at point C in Figure 1-39, when the gNodeB receives an RRC Setup Complete
message from a UE, the corresponding counter is measured. Details are as follows:
The N.RRC.SetupReq.Succ counter is incremented by 1.
When the value of the Establishment Cause IE in the previous received RRC Setup Request
message is "emergency", the N.RRC.SetupReq.Succ.Emc counter is incremented by 1.

message is "highPriorityAccess", the N.RRC.SetupReq.Succ.HighPri counter is incremented
by 1.
message is "mt-Access", the N.RRC.SetupReq.Succ.Mt counter is incremented by 1.
message is "mo-VoiceCall", the N.RRC.SetupReq.Succ.MoVoiceCall counter is incremented
by 1.
message is "mo-Signalling", the N.RRC.SetupReq.Succ.MoSig counter is incremented by 1.
message is "mo-Data", the N.RRC.SetupReq.Succ.MoData counter is incremented by 1.
message is "mo-VideoCall", the N.RRC.SetupReq.Succ.MoVideoCall counter is incremented
by 1.
message is "mo-SMS", the N.RRC.SetupReq.Succ.MoSms counter is incremented by 1.
message is "mps-PriorityAccess", the N.RRC.SetupReq.Succ.MpsPri counter is incremented
by 1.
message is "mcs-PriorityAccess", the N.RRC.SetupReq.Succ.McsPri counter is incremented
by 1.
As shown at point A in Figure 1-40, when the gNodeB receives an RRC Reestablishment
Request message from a UE and determines that it does not have the UE's context
information, the gNodeB sends an RRC Setup message to the UE. Under these circumstances,
the N.RRC.Setup.ReEst counter is incremented by 1.
As shown at point B in Figure 1-40, when the gNodeB receives an RRC Reestablishment
Request message from a UE and determines that it does not have the UE's context
information, the gNodeB sends an RRC Setup message to the UE. After the gNodeB receives
an RRC Setup Complete message from the UE, the N.RRC.SetupSucc.ReEst counter is
incremented by 1.

Figure 1-39

Figure 1-40
Formula
None
Unit
None
Related Features
None
1.1.13 RRC Reestablishment Failure Measurement

(RRC.ReEstFail.Cell)
Overview
An RRC connection reestablishment is a UE-initiated process of recovering an RRC
connection. The RRC.ReEstFail.Cell function subset measures the number of RRC
connection reestablishment failures for different causes in a cell.

Counters
1911816979 N.RRC.ReEst.Msg. Number of times the BTS5900 5G:

Disc.FlowCtrl RRC connection V100R015C10
reestablishment
message is discarded
due to flow control
1911816980 N.RRC.ReEstFail. Number of RRC BTS5900 5G:

NoReply connection V100R015C10
reestablishment
failures due to no
responses from the
UE
None
1.1.13.1 Number of RRC Connection Reestablishment Failures in SA Scenarios
Counters
1911816979 N.RRC.ReEst. Number of BTS3900 5G, N

Msg.Disc.Flow times the RRC BTS5900 5G
Ctrl connection
reestablishment
message is
discarded due
to flow control
1911816980 N.RRC.ReEstF Number of BTS3900 5G, N

ail.NoReply RRC BTS5900 5G
connection
reestablishment
failures due to
no responses
from the UE
Description
These counters measure the number of RRC connection reestablishment failures of UEs in a
cell.

38.331.
Measurement Points
As shown at point A in Figure 1-41, when the gNodeB does not receive an RRC
Reestablishment Complete message from the UE within the specified period of time, the
value of N.RRC.ReEstFail.NoReply is incremented by 1.
When an RRC connection reestablishment message is discarded due to flow control, the value
of N.RRC.ReEst.Msg.Disc.FlowCtrl is incremented by 1.
These counters are measured in the cell where the UEs camp.
Figure 1-41
Formula
None
Unit
None
Related Features
None
1.1.14 RRC Reestablishment Measurement (RRC.ReEst.Cell)

Overview
An RRC connection reestablishment is a UE-initiated process of recovering an RRC
connection. The RRC.ReEst.Cell function subset measures the number of RRC connection

reestablishment requests for different causes and number of successful RRC connection
reestablishment times in a cell.
Counters
1911816993 N.RRC.ReEst.Succ Number of BTS5900 5G:

successful RRC V100R015C10
connection
reestablishment
times
1911816994 N.RRC.ReEst.Att Number of RRC BTS5900 5G:

connection V100R015C10
reestablishment
requests
None
1.1.14.1 Number of RRC Connection Reestablishment Times in SA Scenarios
Counters
1911816993 N.RRC.ReEst.S Number of BTS3900 5G, N

ucc successful RRC BTS5900 5G
connection
reestablishment
times
1911816994 N.RRC.ReEst. Number of BTS3900 5G, N

Att RRC BTS5900 5G
connection
reestablishment
requests
Description
The counter measures the number of RRC connection reestablishment requests of UEs in a
cell. The RRC Reestablishment Request message is an RRC signaling message sent by the
UE. The message is used to recover the RRC connection.
The counter measures the number of successful RRC connection reestablishment times of
UEs in a cell. The RRC Connection Reestablishment Complete message is an RRC signaling

message sent from the UE to the gNodeB. The message is used to inform the gNodeB that the
RRC connection reestablishment is completed.
38.331.
Measurement Points
As shown at point A in Figure 1-42, the N.RRC.ReEst.Att counter is incremented by 1 each
time the gNodeB receives an RRC Reestablishment Request message from a UE in a cell.
As shown at point B in Figure 1-42, the N.RRC.ReEst.Succ counter is incremented by 1 each
time the gNodeB receives an RRC Reestablishment Complete message from a UE in a cell.
Figure 1-42
Formula
None
Unit
None
Related Features
None

1.1.15 UE Context Modification Measurement

(UeCntx.Modify.Cell)
Overview
UE context contains user-specific context information throughout the network. The context
modification is caused by modification of information on the core network side. The UE
context modification success rate in a cell represents the UE context modification capability
of a cell.
Counters
1911816981 N.UECntx.Mod.Su Number of BTS5900 5G:

cc successful UE V100R015C10
context BTS3900:
modifications V100R015C10
BTS5900:
V100R015C10
1911816982 N.UECntx.Mod.Att Number of UE BTS5900 5G:

context modification V100R015C10
attempts BTS3900:
V100R015C10
BTS5900:
V100R015C10
None
1.1.15.1 Number of UE Context Modifications in SA Scenarios
Counters
1911816981 N.UECntx.Mod Number of BTS3900, N

.Succ successful UE BTS3900 5G,
context BTS5900,
modifications
BTS5900 5G


1911816982 N.UECntx.Mod Number of UE BTS3900, N

.Att context BTS3900 5G,
attempts
BTS5900 5G
Description
The counters measure the number of UE context modification attempts and the number of
successful UE context modifications in a cell.
The signaling procedures involved in the counters comply with section 8.3.4 in 3GPP TS
38.413.
Measurement Points
As shown at point A in Figure 1-43, the N.UECntx.Mod.Att counter is incremented by 1 each
time the gNodeB receives a UE CONTEXT MODIFICATION REQUEST message from the
AMF.
As shown at point B in Figure 1-43, the N.UECntx.Mod.Succ counter is incremented by 1

each time the gNodeB replies the AMF with a UE CONTEXT MODIFICATION RESPONSE
message.
Figure 1-43

Formula
None
Unit
None
Related Features
None
1.1.16 UE Context Setup Failure Measurement

(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 up UE contexts. The
UeCntx.EstFail.Cell function subset measures the number of UE context setup failures due to
different causes in a cell. The counter is incremented by 1 each time the UE context setup
fails.
Counters
1911816996 N.UECntx.FailEst. Number of UE BTS5900 5G:

RNL context setup V100R015C10
failures because of BTS3900:
faults at the radio V100R015C10
V100R015C10
1911817082 N.UECntx.FailEst. Number of initial BTS5900 5G:

NoRadioRes UE context setup V100R015C10
insufficient radio V100R015C10
resources BTS5900:
V100R015C10
1911817083 N.UECntx.FailEst. Number of initial BTS5900 5G:

UeNoReply UE context setup V100R015C10
no response from V100R015C10
UE BTS5900:
V100R015C10

None
1.1.16.1 Number of UE Context Setup Failures in SA Scenarios
Counters
1911816996 N.UECntx.Fail Number of UE BTS3900, N

Est.RNL context setup BTS3900 5G,
of faults at the
radio network BTS5900 5G
layer
1911817082 N.UECntx.Fail Number of BTS3900, N

Est.NoRadioRe initial UE BTS3900 5G,
s context setup BTS5900,
failures because
of insufficient BTS5900 5G
radio resources
1911817083 N.UECntx.Fail Number of BTS3900, N

Est.UeNoReply initial UE BTS3900 5G,
context setup BTS5900,
failures because
of no response BTS5900 5G
from UE
Description
The counter measures the number of UE context setup failures of UEs for a specific cause in a
cell.
The signaling procedures related to the counter comply with section 8.3.1 in 3GPP TS 38.413.
Measurement Points
As shown at point A in Figure 1-44, the corresponding counter is incremented based on the
failure cause each time the gNodeB fails to set up the UE context because of a message
processing error after the gNodeB receives an INITIAL CONTEXT SETUP REQUEST
message from the AMF, and then the gNodeB sends an INITIAL CONTEXT SETUP
FAILURE message to the AMF. The N.UECntx.FailEst.RNL counter is incremented each
time the UE context setup fails due to faults at the radio network layer. For details about faults
at the radio network layer, see 3GPP TS 38.413. The N.UECntx.FailEst.NoRadioRes counter
is incremented each time the UE context setup fails due to insufficient radio resources.
As shown at points A, B, and C in Figure 1-45, during the initial UE context setup procedure,
the N.UECntx.FailEst.UeNoReply counter is incremented each time the gNodeB receives no

response from the UE before the corresponding timer expires after the gNodeB sends an RRC
signaling message to the UE and the UE context setup fails.
Figure 1-44

Figure 1-45
Formula
None
Unit
None
Related Features
None

1.1.17 UE Context Setup Measurement (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.
Counters
1911816960 N.UECntx.Est.Att Number of UE BTS5900 5G:

context setup V100R015C10
attempts BTS3900:
V100R015C10
BTS5900:
V100R015C10
1911816961 N.UECntx.Est.Succ Number of BTS5900 5G:

successful UE V100R015C10
context setups BTS3900:
V100R015C10
BTS5900:
V100R015C10
1911817092 N.NGSig.ConnEst. Number of NG BTS3900:

Att signaling connection V100R015C10
setup attempts BTS5900:
V100R015C10
BTS5900 5G:
V100R015C10
1911817093 N.NGSig.ConnEst. Number of BTS3900:

Succ successful NG V100R015C10
signaling connection BTS5900:
setups V100R015C10
BTS5900 5G:
V100R015C10
None

1.1.17.1 Number of UE Context Setups in SA Scenarios
Counters
1911816960 N.UECntx.Est. Number of UE BTS3900, N

Att context setup BTS3900 5G,
attempts BTS5900,
BTS5900 5G
1911816961 N.UECntx.Est. Number of BTS3900, N

Succ successful UE BTS3900 5G,
context setups BTS5900,
BTS5900 5G
1911817092 N.NGSig.Conn Number of NG BTS3900, N

Est.Att signaling BTS3900 5G,
connection BTS5900,
setup attempts
BTS5900 5G
1911817093 N.NGSig.Conn Number of BTS3900, N

Est.Succ successful NG BTS3900 5G,
signaling BTS5900,
connection
setups BTS5900 5G
Description
These counters measure the number of UE context setup attempts and number of successful
UE context setups in a cell.
The number of setup times of NG signaling connections related to UEs is incremented by 1

each time the gNodeB sends an INITIAL UE MESSAGE to the AMF and receives the first
NG message from the AMF. INITIAL UE MESSAGE is the first NG message that the
gNodeB sends to the AMF. It contains the NAS configuration information related to UEs,
based on which the AMF sets up NG signaling connections for UEs. The first NG interface
message received from the AMF may be an INITIAL CONTEXT SETUP REQUEST,
DOWNLINK NAS TRANSPORT, or UE CONTEXT RELEASE COMMAND message. If
the message is received, an NG signaling connection is set up successfully.
38.413.
Measurement Points
As shown at point A in Figure 1-46, the value of the N.NGSig.ConnEst.Att counter is
incremented by 1 each time the gNodeB sends an INITIAL UE MESSAGE message to the
AMF.

As shown at point B in Figure 1-46, the value of the N.NGSig.ConnEst.Succ counter is

incremented by 1 each time the gNodeB receives the first NG message for a UE from the
AMF after sending an INITIAL UE MESSAGE message to the AMF.
As shown at point A in Figure 1-47, the value of the N.UECntx.Est.Att counter is
incremented by 1 each time the gNodeB receives an INITIAL CONTEXT SETUP REQUEST
message from the AMF.
As shown at point B in Figure 1-47, the value of the N.UECntx.Est.Succ counter is
incremented by 1 each time the gNodeB sends an INITIAL CONTEXT SETUP RESPONSE
message to the AMF.
Figure 1-46

Figure 1-47
Formula
None
Unit
None
Related Features
None
1.1.18 UE Context Release Measurement (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 UE context releases for
different causes in a cell. Based on the values of the counters, the release success rate of UE
contexts in a cell is determined.

Counters
1911816986 N.UECntx.Abnorm Number of abnormal BTS5900 5G:

Rel.AMF UE context releases V100R015C10
network V100R015C10
BTS5900:
V100R015C10
1911816987 N.UECntx.Abnorm Number of abnormal BTS5900 5G:

Rel UE context releases V100R015C10
BTS3900:
V100R015C10
BTS5900:
V100R015C10
1911816989 N.UECntx.NormRe Number of UE BTS5900 5G:

l.AMF context releases V100R015C10
network V100R015C10
BTS5900:
V100R015C10
1911816991 N.UECntx.NormRe Number of normal BTS5900 5G:

l UE context releases V100R015C10
BTS3900:
V100R015C10
BTS5900:
V100R015C10
None
1.1.18.1 Number of UE Context Releases in SA Scenarios
Counters
1911816986 N.UECntx.Abn Number of BTS3900, N

ormRel.AMF abnormal UE BTS3900 5G,
context releases BTS5900,
triggered by the


1911816987 N.UECntx.Abn Number of BTS3900, N

ormRel abnormal UE BTS3900 5G,
BTS5900 5G
1911816989 N.UECntx.Nor Number of UE BTS3900, N

mRel.AMF context releases BTS3900 5G,
triggered by the BTS5900,
core network
BTS5900 5G
1911816991 N.UECntx.Nor Number of BTS3900, N

mRel normal UE BTS3900 5G,
BTS5900 5G
Description
These counters measure the total number of normal UE context releases, total number of
abnormal UE context releases, and number of abnormal UE context releases due to different
faults in a cell.
The signaling procedures related to these counters comply with sections 8.3.2 and 8.3.3 in
3GPP TS 38.413.
Measurement Points
"O&M intervention", the release is regarded as a normal release. Otherwise, the release is
regarded as an abnormal release.
When the AMF initiates a release with the cause being "User inactivity", "Load balancing
TAU required", "Release due to CN-detected mobility", "Normal release", or "O&M
intervention", the release is regarded as a normal release. Otherwise, the release is regarded as
an abnormal release.
REQUEST message to the AMF and the release is regarded as a normal release, the release is
accumulated into the N.UECntx.NormRel counter. This counter will not be repeatedly
measured when the AMF returns a UE CONTEXT RELEASE COMMAND message to the
gNodeB.
COMMAND message from the AMF, the measurement of the N.UECntx.NormRel counter is
triggered.
As shown at point A in Figure 1-49, when the AMF proactively sends a UE CONTEXT
RELEASE COMMAND message to the gNodeB with a cause value indicating a normal
release, the measurement of the N.UECntx.NormRel.AMF counter is triggered.

REQUEST message to the AMF with a cause value indicating an abnormal release, the
measurement of the N.UECntx.AbnormRel counter is triggered. This counter will not be
repeatedly measured when the AMF returns a UE CONTEXT RELEASE COMMAND
message to the gNodeB.
As shown at point A in Figure 1-49, the AMF proactively initiates a UE context release
procedure by sending a UE CONTEXT RELEASE COMMAND message to the gNodeB. On
receiving the message from the AMF, the gNodeB determines that the release is an abnormal
release according to the cause value, and the measurement of the N.UECntx.AbnormRel.AMF
counter is triggered.
Figure 1-48
Figure 1-49

Formula
None
Unit
None
Related Features
None
1.1.19 UL DL Decoupling Measurement (Decoupling.Cell)
Overview
The Decoupling.Cell function subset measures the number of times UL and DL Decoupling
messages are sent and received between the gNodeB and UEs. This function subset belongs to
the CU Function.
Counters
1911816832 N.Decoupling.PUC Number of non-SUL BTS5900 5G:

CH.IntraCell.NonS to SUL change V100R015C00
ultoSul.Att attempts of UE BTS5900:
PUCCH frequency V100R015C00
in a decoupling cell BTS3900:
V100R015C00
1911816833 N.Decoupling.PUC Number of BTS5900 5G:

CH.IntraCell.NonS successful non-SUL V100R015C00
ultoSul.Succ to SUL changes of BTS5900:
UE PUCCH V100R015C00
frequency in a BTS3900:
decoupling cell V100R015C00
1911816834 N.Decoupling.PUC Number of SUL to BTS5900 5G:

CH.IntraCell.Sulto non-SUL change V100R015C00
NonSul.Att attempts of UE BTS5900:
PUCCH frequency V100R015C00
in a decoupling cell BTS3900:
V100R015C00
1911816835 N.Decoupling.PUC Number of BTS5900 5G:

CH.IntraCell.Sulto successful SUL to V100R015C00
NonSul.Succ non-SUL changes of BTS5900:
UE PUCCH V100R015C00
frequency in a BTS3900:
decoupling cell V100R015C00

None
1.1.19.1 Number of PUCCH Frequency Changes in the NR Uplink and Downlink

Decoupling Cells
Counters
1911816832 N.Decoupling.P Number of non- BTS3900, N

UCCH.IntraCel SUL to SUL BTS3900 5G,
l.NonSultoSul. change attempts BTS5900,
Att of UE PUCCH
frequency in a BTS5900 5G
decoupling cell
1911816833 N.Decoupling.P Number of BTS3900, N

UCCH.IntraCel successful non- BTS3900 5G,
l.NonSultoSul.S SUL to SUL BTS5900,
ucc changes of UE
PUCCH BTS5900 5G
frequency in a
decoupling cell
1911816834 N.Decoupling.P Number of SUL BTS3900, N

UCCH.IntraCel to non-SUL BTS3900 5G,
l.SultoNonSul. change attempts BTS5900,
Att of UE PUCCH
frequency in a BTS5900 5G
decoupling cell
1911816835 N.Decoupling.P Number of BTS3900, N

UCCH.IntraCel successful SUL BTS3900 5G,
l.SultoNonSul.S to non-SUL BTS5900,
ucc changes of UE
PUCCH BTS5900 5G
frequency in a
decoupling cell
Description
These counters measure the number of changes between SUL and non-SUL of UE PUCCH
frequency in a decoupling cell.
Measurement Points
As shown at point A in Figure 1-50, when the gNodeB determines that the PUCCH of a UE
meets the conditions of changing from non-SUL to SUL and the RRC reconfiguration

procedure is triggered, the N.Decoupling.PUCCH.IntraCell.NonSultoSul.Att counter is

incremented by 1. As shown at point B in Figure 1-50, when the gNodeB subsequently
receives an RRC Reconfiguration Complete message from the UE, the
N.Decoupling.PUCCH.IntraCell.NonSultoSul.Succ counter is incremented by 1. As shown at
point A in Figure 1-50, when the gNodeB determines that the PUCCH of a UE meets the
conditions of changing from SUL to non-SUL and the RRC reconfiguration procedure is
triggered, the N.Decoupling.PUCCH.IntraCell.SultoNonSul.Att counter is incremented by 1.
As shown at point B in Figure 1-50, when the gNodeB subsequently receives an RRC
Reconfiguration Complete message from the UE, the
N.Decoupling.PUCCH.IntraCell.SultoNonSul.Succ counter is incremented by 1.
Figure 1-50
Formula
None
Unit
None
Related Features
N.Decoupling.PUCCH.Intra Multi-mode: None

Cell.NonSultoSul.Att GSM: None
UMTS: None
LTE: None
NR: FOFD-010205 UL and DL Decoupling

Cell.NonSultoSul.Succ GSM: None
UMTS: None
LTE: None


Cell.SultoNonSul.Att GSM: None
UMTS: None
LTE: None

Cell.SultoNonSul.Succ GSM: None
UMTS: None
LTE: None
1.1.20 Secure Mode Measurement (SecurMode.Cell)

Overview
The security mode configuration provides integrity protection and ciphering for signaling
messages and ciphering for user data. It directly represents the capability of the cell to provide
security mode configurations for users. The SecurMode.Cell function subset measures the
number of security mode configurations received over the N2 interface, the number of
security mode commands sent over the Uu interface, and the number of responses to security
modes from the UE.
Counters
1911817072 N.SecurMode.Fail Number of security BTS3900:

mode configuration V100R0015C10
failures received by BTS5900:
the gNodeB from V100R0015C10
the UE BTS5900 5G:
V100R0015C10
1911817073 N.SecurMode.Cmd Number of security BTS3900:

mode commands V100R0015C10
sent from the BTS5900:
gNodeB to the UE V100R0015C10
BTS5900 5G:
V100R0015C10


1911817074 N.SecurMode.Cmp Number of BTS3900:

successful security V100R0015C10
mode configurations BTS5900:
received by the V100R0015C10
gNodeB from the BTS5900 5G:
UE V100R0015C10
1911817075 N.SecurMode.Req Number of times BTS3900:

that the gNodeB V100R0015C10
receives the security BTS5900:
mode sent by the V100R0015C10
AMF BTS5900 5G:
V100R0015C10
None
1.1.20.1 Number of Security Mode Setups in a Cell
Counters
1911817072 N.SecurMode.F Number of BTS3900, N

ail security mode BTS3900 5G,
configuration BTS5900,
failures
received by the BTS5900 5G
gNodeB from
the UE
1911817073 N.SecurMode.C Number of BTS3900, N

md security mode BTS3900 5G,
commands sent BTS5900,
from the
gNodeB to the BTS5900 5G
UE
1911817074 N.SecurMode.C Number of BTS3900, N

mp successful BTS3900 5G,
security mode BTS5900,
configurations
received by the BTS5900 5G
gNodeB from
the UE


1911817075 N.SecurMode.R Number of BTS3900, N

eq times that the BTS3900 5G,
gNodeB BTS5900,
receives the
security mode BTS5900 5G
sent by the
AMF
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 AMF, gNodeB, and UE with the purpose to provide integrity protection
and ciphering for signaling messages and user data over the Uu interface.
The signaling flows involved in the counters comply with section 5.3.4 in 3GPP TS 38.331
and section 8.3.1 in 3GPP TS 38.413.
Measurement Points
As shown at point A in Figure 1-51, the N.SecurMode.Req counter is incremented by 1 each
time the gNodeB receives an Initial Context Setup Request message from the AMF.
As shown at point B in Figure 1-51, the N.SecurMode.Cmd counter is incremented by 1 each
time the gNodeB sends an AS Security Mode Command message to the UE.
As shown at point C in Figure 1-51, the N.SecurMode.Cmp counter is incremented by 1 each
time the gNodeB receives an AS Security Mode Complete message from the UE.
As shown at point D in Figure 1-51, the N.SecurMode.Fail counter is incremented by 1 each
time the gNodeB receives an AS Security Mode Failure message from the UE.

Figure 1-51
Formula
None
Unit
None
Related Features
None
1.1.21 Cell CA Measurement (CA.Cell)

Overview
The Cell CA Measurement (CA.Cell) function subset measures the number of times a
secondary component carrier (SCC) is configured or deconfigured and other related
performance counters.

Counters
1911816777 N.CA.SCell.Add.At Number of SCell BTS5900 5G:

t addition attempts for V100R015C00
CA UEs BTS5900:
V100R015C00
BTS3900:
V100R015C00
1911816778 N.CA.SCell.Add.Su Number of BTS5900 5G:

cc successful SCell V100R015C00
additions for CA BTS5900:
UEs V100R015C00
BTS3900:
V100R015C00
1911816779 N.CA.SCell.Rmv.A Number of SCell BTS5900 5G:

tt removal attempts for V100R015C00
CA UEs BTS5900:
V100R015C00
BTS3900:
V100R015C00
1911816780 N.CA.SCell.Rmv.S Number of BTS5900 5G:

ucc successful SCell V100R015C00
removals for CA BTS5900:
UEs V100R015C00
BTS3900:
V100R015C00
1911816781 N.CA.SCell.Mod.A Number of SCell BTS5900 5G:

tt change attempts for V100R015C00
CA UEs BTS5900:
V100R015C00
BTS3900:
V100R015C00
1911816782 N.CA.SCell.Mod.S Number of BTS5900 5G:

ucc successful SCell V100R015C00
changes for CA UEs BTS5900:
V100R015C00
BTS3900:
V100R015C00
None

1.1.21.1 Number of Times CA UEs Add, Remove, or Change SCells
Counters
1911816777 N.CA.SCell.Ad Number of BTS3900, N

d.Att SCell addition BTS3900 5G,
attempts for CA BTS5900,
UEs
BTS5900 5G
1911816778 N.CA.SCell.Ad Number of BTS3900, N

d.Succ successful BTS3900 5G,
SCell additions BTS5900,
for CA UEs
BTS5900 5G
1911816779 N.CA.SCell.Rm Number of BTS3900, N

v.Att SCell removal BTS3900 5G,
UEs
BTS5900 5G
1911816780 N.CA.SCell.Rm Number of BTS3900, N

v.Succ successful BTS3900 5G,
SCell removals BTS5900,
for CA UEs
BTS5900 5G
1911816781 N.CA.SCell.Mo Number of BTS3900, N

d.Att SCell change BTS3900 5G,
UEs
BTS5900 5G
1911816782 N.CA.SCell.Mo Number of BTS3900, N

d.Succ successful BTS3900 5G,
SCell changes BTS5900,
for CA UEs
BTS5900 5G
Description
These counters measure the number of SCell addition attempts, the number of successful
SCell additions, the number of SCell removal attempts, the number of successful SCell
removals, the number of SCell change attempts, and the number of successful SCell changes
for CA UEs.
Measurement Points
As shown at point A in Figure 1-52, when the gNodeB delivers an RRC Connection
Reconfiguration message carrying the sCellToAddModList IE based on CA event A5 or in a

blind manner, the N.CA.SCell.Add.Att counter is incremented by the number of SCells to be

added indicated by the IE.
In addition, as shown at point B in Figure 1-52, when the gNodeB receives an RRC
Connection Reconfiguration Complete message from the UE, the N.CA.SCell.Add.Succ
counter is incremented in the PCell by the number of added SCells.
If the RRC Connection Reconfiguration message is delivered during a handover, the
N.CA.SCell.Add.Att counter is incremented in the target cell for the PCell by the number of
SCells to be added indicated by the IE. In addition, when the gNodeB determines that the
handover is successful, the N.CA.SCell.Add.Succ counter is incremented in the target cell for
the PCell by the number of added SCells.
If the RRC Connection Reconfiguration message carrying the SCellToAddModList IE is
delivered because of system information update or event A6 reported by a CA UE, the
counters are not incremented.
Reconfiguration message carrying the sCellToReleaseList IE, the N.CA.SCell.Rmv.Att
counter is incremented by the number of SCells to be removed indicated by the IE.
In addition, as shown at point B in Figure 1-53, when the gNodeB receives an RRC
Connection Reconfiguration Complete message from the UE, the N.CA.SCell.Rmv.Succ
counter is incremented in the PCell by the number of removed SCells.
If the RRC Connection Reconfiguration message is delivered during a handover, this counter
is incremented in the target cell for the PCell by the number of SCells to be removed indicated
by the sCellToReleaseList IE when the gNodeB determines that the handover is successful.
If the RRC Connection Reconfiguration message carrying the SCellToReleaseList IE is
delivered because of system information update or event A6 reported by a CA UE, the
counters are not incremented.
Reconfiguration message to change the SCell for a CA UE after receiving an event A6-related
measurement report, the N.CA.SCell.Mod.Att counter is incremented by 1 in the PCell. In
addition, as shown at point B in Figure 1-54, when the gNodeB receives an RRC Connection
Reconfiguration Complete message, the N.CA.SCell.Mod.Succ counter is incremented by 1
in the PCell.

Figure 1-52
Figure 1-53

Figure 1-54
Formula
None
Unit
None
Related Features
N.CA.SCell.Add.Att Multi-mode: None

GSM: None
UMTS: None
LTE: None
NR: FOFD-020205 Intra-band CA
N.CA.SCell.Add.Succ Multi-mode: None

GSM: None
UMTS: None
LTE: None

N.CA.SCell.Rmv.Att Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.CA.SCell.Rmv.Succ Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.CA.SCell.Mod.Att Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.CA.SCell.Mod.Succ Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.1.22 Cell User Quantity Measurement (User.Cell)

Overview
The Cell User Quantity Measurement(User.Cell) function subset measures the number of
RRC_Connected UEs in different uplink or downlink scenarios in a cell. The user quantity
can be measured using two different mechanisms. The first mechanism measures the user
quantity based on the UE status within a sampling period. The second mechanism measures
the user quantity based on the UE status at the time samples are taken. Different measurement
mechanisms may lead to different counter values in certain scenarios.

Counters
1911816547 N.User.Decouple.A Average number of BTS5900:

vg decoupling UEs that V100R013C10
treat the local cell as BTS5900 5G:
their downlink cell V100R013C10
BTS3900:
V100R015C00
1911816745 N.User.NsaDc.PSC Average Number of BTS5900 5G:

ell.Avg LTE-NR NSA DC V100R013C10
UEs Using the BTS5900:
Current Cell as V100R013C10
PSCell BTS3900:
V100R015C00
1911816771 N.User.RRCConn. Average number of BTS5900 5G:

Avg UEs in V100R015C00
RRC_CONNECTE BTS5900:
D mode in a cell V100R015C00
BTS3900:
V100R015C00
1911816772 N.User.RRCConn. Maximum number BTS5900 5G:

Max of UEs in V100R015C00
D mode in a cell V100R015C00
BTS3900:
V100R015C00
1911816773 N.User.CA.PCell.D Average number of BTS5900 5G:

L.Avg downlink CA UEs V100R015C00
that use the local BTS5900:
cell as their primary V100R015C00
serving cells BTS3900:
V100R015C00
1911816774 N.User.CA.SCell.D Average number of BTS5900 5G:

L.Avg downlink CA UEs V100R015C00
cell as their V100R015C00
secondary serving BTS3900:
cells V100R015C00


1911816775 N.User.CA.PCell.U Average number of BTS5900 5G:

L.Avg uplink CA UEs that V100R015C00
use the local cell as BTS5900:
their primary V100R015C00
V100R015C00
1911816776 N.User.CA.SCell.U Average number of BTS5900 5G:

L.Avg uplink CA UEs that V100R015C00
their secondary V100R015C00
V100R015C00

B2H.Avg B2H UEs in a cell V100R015C00
BTS5900:
V100R015C00
BTS3900:
V100R015C00
None
1.1.22.1 Number of Decoupling UEs in a Downlink Cell
Counters
1911816547 N.User.Decoupl Average BTS3900, N

e.Avg number of BTS3900 5G,
decoupling UEs BTS5900,
that treat the
local cell as BTS5900 5G
their downlink
cell
Description
The counter measures the average number of decoupling UEs that treat the local cell as their
downlink cell.

Measurement Points
The number of UEs (in RRC_CONNECTED mode) in the cell is sampled per second, and the
number of decoupling UEs that treat the local cell as their downlink cell is measured from the
sample. At the end of a measurement period, the average of these samples is used as the
counter value.
Formula
None
Unit
None
Related Features
N.User.Decouple.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.1.22.2 Average Number of LTE-NR NSA UEs in the PSCell
Counters
1911816745 N.User.NsaDc. Average BTS3900, N

PSCell.Avg Number of BTS3900 5G,
LTE-NR NSA BTS5900,
DC UEs Using
the Current Cell BTS5900 5G
as PSCell
Description
This counter measures the average number of LTE-NR NSA DC UEs using the current cell as
the PSCell.

Measurement Points
The number of UEs using LTE-NR NSA DC for data transmission and using the current cell
as the PSCell is sampled every second in a cell. 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
N.User.NsaDc.PSCell.Avg Multi-mode: MRFD-131162 NSA Networking based on

GSM: None EPC (NR)
UMTS: None
LTE: None
NR: FOFD-010205
1.1.22.3 Number of UEs in a Cell
Counters
1911816771 N.User.RRCCo Average BTS3900, N

nn.Avg number of UEs BTS3900 5G,
in BTS5900,
RRC_CONNE
CTED mode in BTS5900 5G
a cell
1911816772 N.User.RRCCo Maximum BTS3900, N

nn.Max number of UEs BTS3900 5G,
in BTS5900,
RRC_CONNE
CTED mode in BTS5900 5G
a cell

Description
These counters measure the average and maximum numbers of RRC_CONNECTED UEs in a
cell.
Measurement Points
The counter values are generated based on the status of UEs at the sampling time. The number
of UEs in RRC_CONNECTED mode in a cell is sampled per second. At the end of a
measurement period, the average and maximum of these sampling results are taken as the
values of the corresponding counters. For DC users, one user is counted for each of the master
base station and the secondary base station.
Formula
None
Unit
None
Related Features
None
1.1.22.4 Number of CA UEs in a Cell
Counters
1911816773 N.User.CA.PCe Average BTS3900, N

ll.DL.Avg number of BTS3900 5G,
downlink CA BTS5900,
UEs that use the
their primary
serving cells
1911816774 N.User.CA.SCe Average BTS3900, N

ll.DL.Avg number of BTS3900 5G,
downlink CA BTS5900,
UEs that use the
their secondary
serving cells



ll.UL.Avg number of BTS3900 5G,
uplink CA UEs BTS5900,
that use the
their primary
serving cells

ll.UL.Avg number of BTS3900 5G,
uplink CA UEs BTS5900,
that use the
their secondary
serving cells
Description
These counters measure the average number of CA UEs that treat the local cell as their PCell
or SCell in the uplink or downlink CA state.
Measurement Points
The number of CA UEs in a cell that treat the local cell as their PCell or SCell in uplink and
downlink CA states 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. The sampling time for the
number of CA UEs that treat the local cell as their SCell in the uplink and downlink CA states
is different from that for the number of CA UEs that treat the local cell as their PCell in the
uplink and downlink CA states. Therefore, the number of CA UEs that treat the local cell as
their SCell in the uplink and downlink CA states may be greater than the number of CA UEs
that treat the local cell as their PCell in the uplink and downlink CA states.
Formula
None
Unit
None

Related Features
N.User.CA.PCell.DL.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.User.CA.SCell.DL.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.User.CA.PCell.UL.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.User.CA.SCell.UL.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.1.22.5 Number of B2H UEs in a Cell
Counters

nn.B2H.Avg number of B2H BTS3900 5G,
UEs in a cell BTS5900,
BTS5900 5G
Description
These counters measure the average number of B2H UEs in a cell.

Measurement Points
The counter values are measured based on the status of UEs at the sampling time. The number
of business to home (B2H) UEs in the RRC_CONNECTED state (including UEs in the
synchronized state and UEs in the out-of-synchronization state) in a cell is sampled per
second. At the end of a measurement period, the average of these sampling results are used as
the corresponding counter values.
Formula
None
Unit
None
Related Features
None
1.1.23 Cell Algorithm Measurement (Algo.Cell)
Overview
The Cell Algorithm Measurement (Algo.Cell) function subset measures the number of times
the uplink AMR speech coding rate increases or decreases, to check whether uplink AMR
speech coding rate control takes effect. This function subset also measures the distribution of
the numbers of uplink and downlink voice packets in different speech coding schemes, to
monitor the basic characteristics of voice services on the live network. With uplink AMR
speech coding rate control enabled, this function subset can be used to monitor the
distribution changes of speech coding schemes.
Counters
1911816766 N.Cell.Unavail.Dur. Duration of cell BTS5900 5G:

System unavailability due to V100R015C00
system faults BTS5900:
V100R015C00
BTS3900:
V100R015C00
1911816767 N.Cell.Unavail.Dur. Duration of cell BTS5900 5G:

Manual unavailability V100R015C00
caused by manual BTS5900:
OM operations V100R015C00
BTS3900:
V100R015C00

None
1.1.23.1 Cell Unavailability Duration
Counters
1911816766 N.Cell.Unavail. Duration of cell BTS3900, N

Dur.System unavailability BTS3900 5G,
due to system BTS5900,
faults
BTS5900 5G
1911816767 N.Cell.Unavail. Duration of cell BTS3900, N

Dur.Manual unavailability BTS3900 5G,
caused by BTS5900,
manual OM
operations BTS5900 5G
Description
These counters measure the duration of cell unavailability due to human operations and
system faults. Human operations include blocking and deactivating a cell by using MML
commands. System faults include board faults, faults on a CPRI link, faults on the baseband
processing board carrying services of the cell, faults on TX or RX channels of an RF module,
unavailability of control-plane (F1 links) transmission resources, Ng interface fault in SA
networking, exception of internal software module carrying cell services, insufficiency of
license resources, and unavailability of clocks.
Measurement Points
The cell status is sampled per five seconds. If the cell status is unavailable at a sampling point,
the corresponding counter is incremented by 5s. At the end of a measurement period, the
accumulated counter value is reported. A deviation of one sampling period may exist in the
sampling timer when the timer performs time synchronization.
Formula
None
Unit
s
Related Features
None

1.1.24 Cell Reserved Counter Measurement (Reserve.Cell)

Overview
Reserved counters are temporarily used in patch versions and will be replaced with new
counters in later versions. For details about the reserved counters in use, see Used Reserved
Counter List of the corresponding version.
Counters
1911816392 N.Cell.Reserve.1 Reserved counter 1 BTS5900 5G:

for the cell V100R013C10
BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00



BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00



BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00



BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00



BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00



BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00



BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00



BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00
None
1.1.24.1 Reserved Counter 1 for the Cell
Counters
1911816392 N.Cell.Reserve. Reserved BTS3900, N

1 counter 1 for BTS3900 5G,
the cell BTS5900,
BTS5900 5G
Description
Reserved counter 1 for the cell
Measurement Points

Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description

Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description

Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description

Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description

Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description

Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description

Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description

Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description

Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description

Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description

Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description

Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description

Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description

Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description

Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description

Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description

Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

the cell BTS5900,
BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None

1.1.25 Incoming Intra-RAT Handover Measurement

(HO.NR.In.Cell)
Overview
The HO.NR.In.Cell function subset measures the performance of intra-frequency, inter-
frequency, and inter-duplex-mode incoming handovers in a cell. If the source and target cells
work on the same frequency in the same duplex mode, the handover is an intra-frequency
handover. If the source and target cells work on different frequencies in the same duplex
mode, the handover is an inter-frequency handover. If the source and target cells work in
different duplex modes, the handover is an inter-duplex-mode handover.
Counters
1911816906 N.HO.IntragNB.Pr Number of intra- BTS5900 5G:

epAttIn gNodeB incoming V100R015C10
handover attempts
1911816913 N.HO.Xn.IntergNB Number of Xn- BTS5900 5G:

.ExecAttIn based inter-gNodeB V100R015C10
incoming handover
executions
1911816914 N.HO.FailIn.HOCa Number of failed BTS5900 5G:

ncel incoming handovers V100R015C10
due to handover
cancellation
messages received
by the target cell
1911816915 N.HO.Xn.IntergNB Number of BTS5900 5G:

.ExecSuccIn successful Xn-based V100R015C10
inter-gNodeB
incoming handovers
1911816916 N.HO.Ng.IntergNB Number of Ng- BTS5900 5G:

.PrepAttIn based inter-gNodeB V100R015C10
incoming handover
attempts
1911816918 N.HO.IntragNB.Ex Number of intra- BTS5900 5G:

ecAttIn gNodeB incoming V100R015C10
handover executions
1911816919 N.HO.Ng.IntergNB Number of Ng- BTS5900 5G:

.ExecAttIn based inter-gNodeB V100R015C10
incoming handover
executions


1911816922 N.HO.Ng.IntergNB Number of BTS5900 5G:

.ExecSuccIn successful Ng-based V100R015C10
inter-gNodeB
incoming handovers
1911816923 N.HO.IntragNB.Ex Number of BTS5900 5G:

ecSuccIn successful intra- V100R015C10
gNodeB incoming
handovers
1911817052 N.HO.Xn.IntergNB Number of Xn- BTS5900 5G:

.PrepAttIn based inter-gNodeB V100R015C10
incoming handover
attempts
None
1.1.25.1 Number of Intra-NR Incoming Handover Executions
Counters
1911816913 N.HO.Xn.Interg Number of Xn- BTS3900 5G, N

NB.ExecAttIn based inter- BTS5900 5G
gNodeB
incoming
handover
executions
1911816918 N.HO.IntragNB Number of BTS3900 5G, N

.ExecAttIn intra-gNodeB BTS5900 5G
incoming
handover
executions
1911816919 N.HO.Ng.Interg Number of Ng- BTS3900 5G, N

NB.ExecAttIn based inter- BTS5900 5G
gNodeB
incoming
handover
executions

Description
The counters measure the number of intra-NR incoming handover executions in a cell. If the
source cell and target cell for a handover are under the same gNodeB, the handover is an
intra-gNodeB handover. If the source cell and target cell perform handover preparation
through the Xn interface, the handover is an Xn-based inter-gNodeB handover. If the source
cell and target cell perform handover preparation through the Ng interface, the handover is an
Ng-based inter-gNodeB handover.
Measurement Points
As shown at point B in Figure 1-55, the N.HO.IntragNB.ExecAttIn counter is incremented by
1 in the target cell each time the source cell sends an RRC Reconfiguration message to a UE
in the event of an intra-gNodeB handover.
As shown at point B in Figure 1-56, the N.HO.Xn.IntergNB.ExecAttIn counter is
incremented by 1 each time the target gNodeB sends a HANDOVER REQUEST
ACKNOWLEDGE message to the source gNodeB over the Xn interface.
As shown at point B in Figure 1-57, the N.HO.Ng.IntergNB.ExecAttIn counter is
incremented by 1 each time the target gNodeB sends a HANDOVER REQUEST
ACKNOWLEDGE message to the source gNodeB over the Ng interface.
Figure 1-55

Figure 1-56
Figure 1-57
Formula
None
Unit
None

Related Features
N.HO.Xn.IntergNB.ExecAtt Multi-mode: None

In GSM: None
UMTS: None
LTE: None
NR: FBFD-010014 Mobility Management
N.HO.IntragNB.ExecAttIn Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.HO.Ng.IntergNB.ExecAtt Multi-mode: None

In GSM: None
UMTS: None
LTE: None
1.1.25.2 Number of Failed Intra-NR Incoming Handovers
Counters
1911816914 N.HO.FailIn.H Number of BTS3900 5G, N

OCancel failed incoming BTS5900 5G
handovers due
to handover
cancellation
messages
received by the
target cell
Description
The counter measures the number of failed incoming handovers in a cell.
Measurement Points
As shown at point B in Figure 1-58, during an Xn-based handover, when the target gNodeB
receives a HANDOVER CANCEL message from the source gNodeB, or as shown at B in

Figure 1-59, during an Ng-based handover, the N.HO.FailIn.HOCancel counter is

incremented by 1 in the target cell each time the target gNodeB receives a UE CONTEXT
RELEASE COMMAND message from the AMF with release cause being Handover
Cancelled.
Figure 1-58
Figure 1-59
Formula
None
Unit
None

Related Features
N.HO.FailIn.HOCancel Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.1.25.3 Number of Successful Intra-NR Incoming Handovers
Counters
1911816915 N.HO.Xn.Interg Number of BTS3900 5G, N

NB.ExecSuccIn successful Xn- BTS5900 5G
based inter-
gNodeB
incoming
handovers
1911816922 N.HO.Ng.Interg Number of BTS3900 5G, N

NB.ExecSuccIn successful Ng- BTS5900 5G
based inter-
gNodeB
incoming
handovers

.ExecSuccIn successful intra- BTS5900 5G
gNodeB
incoming
handovers
Description
The counters measure the number of successful intra-NR incoming handovers in a cell. If the
Measurement Points
As shown at point C in Figure 1-60, the N.HO.IntragNB.ExecSuccIn counter is incremented
by 1 in the target cell each time the target cell receives an RRC Reconfiguration Complete

message from a UE and the subsequent processing is successful in the event of an intra-
gNodeB handover. As shown at point C in Figure 1-63, this counter is incremented by 1 in
the target cell each time the target cell receives an RRC Connection Reestablishment
Complete message from a UE and the subsequent reestablishment processing is successful in
the event of an intra-gNodeB handover.
As shown at point C in Figure 1-61, during an Xn-based inter-gNodeB handover, the
N.HO.Xn.IntergNB.ExecSuccIn counter is incremented by 1 in the target cell when the target
gNodeB receives a PATH SWITCH REQUEST ACKNOWLEDGE message from the AMF
and sends a UE CONTEXT RELEASE message to the source gNodeB over the Xn interface.
As shown at point C in Figure 1-64, during an Xn-based inter-gNodeB handover where the
UE is successfully established on the target gNodeB, the N.HO.Xn.IntergNB.ExecSuccIn
counter is incremented by 1 in the target cell when the target gNodeB receives a PATH
SWITCH REQUEST ACKNOWLEDGE message from the AMF and sends a UE CONTEXT
RELEASE message to the source gNodeB over the Xn interface.
As shown at point C in Figure 1-62, during an Ng-based inter-gNodeB handover, the
N.HO.Ng.IntergNB.ExecSuccIn counter is incremented by 1 in the target cell each time the
target gNodeB sends a HANDOVER NOTIFY message to the AMF. As shown at point C in
Figure 1-65, during an Ng-based inter-gNodeB handover where the UE is successfully
established on the target gNodeB, the N.HO.Ng.IntergNB.ExecSuccIn counter is incremented
by 1 in the target cell each time the target gNodeB sends a HANDOVER NOTIFY message to
the AMF.
Figure 1-60

Figure 1-61
Figure 1-62

Figure 1-63
Figure 1-64

Figure 1-65
Formula
None
Unit
None
Related Features
N.HO.Xn.IntergNB.ExecSu Multi-mode: None

ccIn GSM: None
UMTS: None
LTE: None
N.HO.Ng.IntergNB.ExecSu Multi-mode: None

ccIn GSM: None
UMTS: None
LTE: None
N.HO.IntragNB.ExecSuccIn Multi-mode: None

GSM: None
UMTS: None
LTE: None

1.1.25.4 Number of Intra-NR Incoming Handover Attempts
Counters

.PrepAttIn intra-gNodeB BTS5900 5G
incoming
handover
attempts
1911816916 N.HO.Ng.Interg Number of Ng- BTS3900 5G, N

NB.PrepAttIn based inter- BTS5900 5G
gNodeB
incoming
handover
attempts
1911817052 N.HO.Xn.Interg Number of Xn- BTS3900 5G, N

NB.PrepAttIn based inter- BTS5900 5G
gNodeB
incoming
handover
attempts
Description
The counters measure the number of intra-NR incoming handover attempts in a cell. If the
Measurement Points
As shown at point A in Figure 1-66, the N.HO.IntragNB.PrepAttIn counter is incremented by
1 in the target cell each time the gNodeB receives a Measurement Report message from the
UE and decides to perform a handover when the source cell and the target cell are under the
same gNodeB.
As shown at point A in Figure 1-67, the N.HO.Xn.IntergNB.PrepAttIn counter is

incremented by 1 in the target cell each time the gNodeB receives a Measurement Report
message from the UE, decides to perform a handover, and prepares to initiate Xn-based
handover preparation when the source cell and the target cell are under different gNodeBs.
As shown at point A in Figure 1-68, the N.HO.Ng.IntergNB.PrepAttIn counter is

incremented by 1 in the target cell each time the gNodeB receives a Measurement Report
message from the UE, decides to perform a handover, and prepares to initiate Ng-based
handover preparation when the source cell and the target cell are under different gNodeBs.

Figure 1-66
Figure 1-67

Figure 1-68
Formula
None
Unit
None
Related Features
N.HO.IntragNB.PrepAttIn Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.HO.Ng.IntergNB.PrepAtt Multi-mode: None

In GSM: None
UMTS: None
LTE: None
N.HO.Xn.IntergNB.PrepAtt Multi-mode: None

In GSM: None
UMTS: None
LTE: None

1.1.26 Outgoing Intra-RAT Handover Measurement

(HO.NR.Out.Cell)
Overview
The HO.NR.Out.Cell function subset measures the performance of intra-frequency, inter-
frequency, and inter-duplex-mode outgoing handovers in a cell. If the source and target cells
work on the same frequency in the same duplex mode, the handover is an intra-frequency
handover. If the source and target cells work on different frequencies in the same duplex
mode, the handover is an inter-frequency handover. If the source and target cells work in
different duplex modes, the handover is an inter-duplex-mode handover.
Counters
1911816904 N.HO.IntraFreq.X Number of Xn- BTS5900 5G:

n.IntergNB.ExecAt based intra- V100R015C10
tOut frequency inter-
gNodeB outgoing
handover executions
1911816905 N.HO.IntraFreq.In Number of intra- BTS5900 5G:

tragNB.ExecAttOu frequency intra- V100R015C10
t gNodeB outgoing
handover executions
1911816907 N.HO.IntraFreq.In Number of BTS5900 5G:

tragNB.ExecSuccO successful intra- V100R015C10
ut frequency intra-
gNodeB outgoing
handovers
1911816908 N.HO.IntraFreq.N Number of Ng- BTS5900 5G:

g.IntergNB.PrepAt based intra- V100R015C10
gNodeB outgoing
handover attempts
1911816909 N.HO.IntraFreq.X Number of BTS5900 5G:

n.IntergNB.ExecSu successful Xn-based V100R015C10
ccOut intra-frequency
inter-gNodeB
outgoing handovers
1911816910 N.HO.IntraFreq.X Number of Xn- BTS5900 5G:

n.IntergNB.PrepAt based intra- V100R015C10
gNodeB outgoing
handover attempts


1911816911 N.HO.IntraFreq.Pr Number of failed BTS5900 5G:

ep.FailOut.HOCan intra-frequency V100R015C10
cel outgoing handover BTS3900:
preparations due to V100R015C10
handover BTS5900:
cancellation V100R015C10
messages sent by the
source cell
1911816912 N.HO.IntraFreq.In Number of intra- BTS5900 5G:

tragNB.PrepAttOu frequency intra- V100R015C10
t gNodeB outgoing
handover attempts
1911816917 N.HO.IntraFreq.N Number of Ng- BTS5900 5G:

g.IntergNB.ExecAt based intra- V100R015C10
gNodeB outgoing
handover executions
1911816920 N.HO.IntraFreq.Fa Number of failed BTS5900 5G:

ilOut.PrepFailure outgoing handover V100R015C10
preparations due to BTS3900:
handover V100R015C10
preparation failure BTS5900:
messages replied by V100R015C10
the target cell
1911816921 N.HO.IntraFreq.N Number of BTS5900 5G:

g.IntergNB.ExecSu successful Ng-based V100R015C10
ccOut intra-frequency
inter-gNodeB
outgoing handovers
1911817088 N.HO.IntraFreq.Fa Number of times the BTS5900 5G:

ilOut.HOCancel source cell sends a V100R015C10
handover BTS3900:
cancellation V100R015C10
message in intra- BTS5900:
frequency handovers V100R015C10
1911817089 N.HO.IntraFreq.Pr Number of intra- BTS5900 5G:

ep.FailOut.AMF frequency outgoing V100R015C10
handover BTS3900:
preparation failures V100R015C10
because of core BTS5900:
network reasons V100R015C10



ep.FailOut.NoRepl frequency outgoing V100R015C10
y handover BTS3900:
because of no BTS5900:
responses from the V100R015C10
target cell

ep.FailOut.TargetIl frequency outgoing V100R015C10
legal handover BTS3900:
because the received BTS5900:
handover response V100R015C10
messages fail the
validity check
None
1.1.26.1 Number of Intra-NR Intra-Frequency Outgoing Handover Executions
Counters
1911816904 N.HO.IntraFreq Number of Xn- BTS3900 5G, N

.Xn.IntergNB.E based intra- BTS5900 5G
xecAttOut frequency inter-
gNodeB
outgoing
handover
executions
1911816905 N.HO.IntraFreq Number of BTS3900 5G, N

.IntragNB.Exec intra-frequency BTS5900 5G
AttOut intra-gNodeB
outgoing
handover
executions


1911816917 N.HO.IntraFreq Number of Ng- BTS3900 5G, N

.Ng.IntergNB.E based intra- BTS5900 5G
xecAttOut frequency inter-
gNodeB
outgoing
handover
executions
Description
The counters measure the number of intra-NR intra-frequency outgoing handovers executed
in a cell. If the source cell and target cell work on the same frequency in the same duplex
mode, the handover is an intra-frequency handover. If the source cell and target cell for a
handover are under the same gNodeB, the handover is an intra-gNodeB handover. If the
source cell and target cell perform handover preparation through the Xn interface, the
handover is an Xn-based inter-gNodeB handover. If the source cell and target cell perform
handover preparation through the Ng interface, the handover is an Ng-based inter-gNodeB
handover.
Measurement Points
As shown at point B in Figure 1-69, the N.HO.IntraFreq.IntragNB.ExecAttOut counter is
incremented by 1 each time the source cell sends an RRC Reconfiguration message to a UE in
the event of an intra-gNodeB handover.
As shown at point B in Figure 1-70, the N.HO.IntraFreq.Xn.IntergNB.ExecAttOut counter is
incremented by 1 each time the source gNodeB sends an RRC Reconfiguration message to a
UE after receiving a HANDOVER REQUEST ACKNOWLEDGE message from the target
gNodeB in the event of an Xn-based inter-gNodeB handover.
As shown at point B in Figure 1-71, the N.HO.IntraFreq.Ng.IntergNB.ExecAttOut counter is
incremented by 1 each time the source gNodeB sends an RRC Reconfiguration message to a
UE after receiving a HANDOVER COMMAND message from the AMF in the event of an

Figure 1-69
Figure 1-70

Figure 1-71
Formula
None
Unit
None
Related Features
N.HO.IntraFreq.Xn.IntergN Multi-mode: None

B.ExecAttOut GSM: None
UMTS: None
LTE: None
N.HO.IntraFreq.IntragNB.E Multi-mode: None

xecAttOut GSM: None
UMTS: None
LTE: None
N.HO.IntraFreq.Ng.IntergN Multi-mode: None

UMTS: None
LTE: None

1.1.26.2 Number of Successful Intra-NR Intra-Frequency Outgoing Handovers
Counters

.IntragNB.Exec successful intra- BTS5900 5G
SuccOut frequency intra-
gNodeB
outgoing
handovers

.Xn.IntergNB.E successful Xn- BTS5900 5G
xecSuccOut based intra-
frequency inter-
gNodeB
outgoing
handovers

.Ng.IntergNB.E successful Ng- BTS5900 5G
xecSuccOut based intra-
frequency inter-
gNodeB
outgoing
handovers
Description
The counters measure the number of successful intra-NR intra-frequency outgoing handovers
in a cell. If the source cell and target cell work on the same frequency in the same duplex
mode, the handover is an intra-frequency handover. If the source cell and target cell for a
handover are under the same gNodeB, the handover is an intra-gNodeB handover. If the
source cell and target cell perform handover preparation through the Xn interface, the
handover is an Xn-based inter-gNodeB handover. If the source cell and target cell perform
handover preparation through the Ng interface, the handover is an Ng-based inter-gNodeB
handover.
Measurement Points
As shown at point C in Figure 1-72 and Figure 1-75, the
N.HO.IntraFreq.IntragNB.ExecSuccOut counter is incremented by 1 each time the target cell
under the gNodeB receives an RRC Reconfiguration Complete or RRC Connection
Reestablishment Complete message from a UE in the event of an intra-gNodeB handover.
The N.HO.IntraFreq.Xn.IntergNB.ExecSuccOut counter is incremented by 1 in the event of
an Xn-based inter-gNodeB handover in the following scenarios: As shown at point C in
Figure 1-73, the source gNodeB receives a UE CONTEXT RELEASE message from the
target gNodeB; as shown at point C in Figure 1-76, the UE is successfully reestablished on

the source gNodeB; as shown at point C in Figure 1-78, the UE is successfully reestablished
on the target gNodeB, and the source gNodeB receives a UE CONTEXT RELEASE message
from the target gNodeB.
The N.HO.IntraFreq.Ng.IntergNB.ExecSuccOut counter is incremented by 1 in the event of
an Ng-based inter-gNodeB handover in the following scenarios: As shown at point C in
Figure 1-74, the source gNodeB receives a UE CONTEXT RELEASE message from the
AMF; as shown at point C in Figure 1-77, the UE is successfully reestablished on the source
gNodeB; as shown at point C in Figure 1-79, the UE is successfully reestablished on the
target gNodeB, and the source gNodeB receives a UE CONTEXT RELEASE message from
the AMF.
Figure 1-72

Figure 1-73
Figure 1-74

Figure 1-75
Figure 1-76

Figure 1-77
Figure 1-78

Figure 1-79
Formula
None
Unit
None
Related Features
N.HO.IntraFreq.IntragNB.E Multi-mode: None

xecSuccOut GSM: None
UMTS: None
LTE: None

B.ExecSuccOut GSM: None
UMTS: None
LTE: None


UMTS: None
LTE: None
1.1.26.3 Number of Intra-NR Intra-Frequency Outgoing Handover Attempts
Counters
1911816908 N.HO.IntraFreq Number of Ng- BTS3900 5G, N

.Ng.IntergNB.P based intra- BTS5900 5G
repAttOut frequency inter-
gNodeB
outgoing
handover
attempts
1911816910 N.HO.IntraFreq Number of Xn- BTS3900 5G, N

.Xn.IntergNB.P based intra- BTS5900 5G
repAttOut frequency inter-
gNodeB
outgoing
handover
attempts

.IntragNB.Prep intra-frequency BTS5900 5G
AttOut intra-gNodeB
outgoing
handover
attempts
Description
The counters measure the number of intra-NR intra-frequency outgoing handover attempts in
a cell. If the source cell and target cell work on the same frequency in the same duplex mode,
the handover is an intra-frequency handover. If the source cell and target cell for a handover
are under the same gNodeB, the handover is an intra-gNodeB handover. If the source cell and
target cell perform handover preparation through the Xn interface, the handover is an Xn-
based inter-gNodeB handover. If the source cell and target cell perform handover preparation
through the Ng interface, the handover is an Ng-based inter-gNodeB handover.

Measurement Points
As shown at point A in Figure 1-80, the N.HO.IntraFreq.IntragNB.PrepAttOut counter is
incremented by 1 each time the gNodeB decides to perform an intra-gNodeB handover after
the cell receives a Measurement Report message from the UE.
As shown at point A in Figure 1-81, the N.HO.IntraFreq.Xn.IntergNB.PrepAttOut counter is
incremented by 1 each time the source gNodeB decides to perform an Xn-based inter-gNodeB
handover after the cell under the source gNodeB receives a Measurement Report message
from the UE.
As shown at point A in Figure 1-82, the N.HO.IntraFreq.Ng.IntergNB.PrepAttOut counter is
incremented by 1 each time the source gNodeB decides to perform an Ng-based inter-gNodeB
handover after the cell under the source gNodeB receives a Measurement Report message
from the UE.
Figure 1-80

Figure 1-81
Figure 1-82
Formula
None
Unit
None

Related Features

B.PrepAttOut GSM: None
UMTS: None
LTE: None

UMTS: None
LTE: None
N.HO.IntraFreq.IntragNB.Pr Multi-mode: None

epAttOut GSM: None
UMTS: None
LTE: None
1.1.26.4 Number of Failed Intra-NR Intra-Frequency Outgoing Handovers
Counters
1911816911 N.HO.IntraFreq Number of BTS3900, N

.Prep.FailOut.H failed intra- BTS3900 5G,
OCancel frequency BTS5900,
outgoing
handover BTS5900 5G
preparations
due to handover
cancellation
messages sent
by the source
cell



.FailOut.PrepFa failed outgoing BTS3900 5G,
ilure handover BTS5900,
preparations
due to handover BTS5900 5G
preparation
failure
messages
replied by the
target cell

.FailOut.HOCa times the source BTS3900 5G,
ncel cell sends a BTS5900,
handover
cancellation BTS5900 5G
message in
intra-frequency
handovers

.Prep.FailOut.A intra-frequency BTS3900 5G,
MF outgoing BTS5900,
handover
preparation BTS5900 5G
failures because
of core network
reasons

.Prep.FailOut.N intra-frequency BTS3900 5G,
oReply outgoing BTS5900,
handover
failures because
of no responses
from the target
cell

.Prep.FailOut.T intra-frequency BTS3900 5G,
argetIllegal outgoing BTS5900,
handover
failures because
the received
handover
response
messages fail
the validity
check

Description
These counters measure the number of intra-frequency outgoing handover failures in a cell.
Measurement Points
As shown at point B in Figure 1-83 and Figure 1-84, the value of the
N.HO.IntraFreq.FailOut.PrepFailure counter is incremented by 1 when the source cell
receives a HANDOVER PREPARATION FAILURE message from the AMF during the
preparation of an NG handover, and is incremented by 1 when the source cell, which works
on the same frequency as the target cell, receives a HANDOVER PREPARATION FAILURE
message from the target cell during the preparation of an Xn handover.
As shown at point B in Figure 1-85 and Figure 1-86, during an Xn or NG handover, the
source cell decides to cancel the handover and sends a HANDOVER CANCEL message
before the handover preparation is complete. If the source cell and the target cell work on the
same frequency, the value of the N.HO.IntraFreq.Prep.FailOut.HOCancel counter is
incremented by 1.
As shown at point B in Figure 1-87 and Figure 1-88, during an NG or Xn handover, if the
source cell sends a HANDOVER CANCEL message and the source cell and the target cell
work on the same frequency, the value of the N.HO.IntraFreq.FailOut.HOCancel counter is
incremented by 1. This counter is measured as long as the source cell sends a HANDOVER
CANCEL message, regardless of whether the handover preparation is complete.
As shown at point B in Figure 1-89 and Figure 1-90, the source cell receives a UE
CONTEXT RELEASE COMMAND message from the AMF during the preparation of an NG
or Xn handover. If the source cell and the target cell work on the same frequency, the value of
the N.HO.IntraFreq.Prep.FailOut.AMF counter is incremented by 1.
As shown at point B in Figure 1-91 and Figure 1-92, the source cell does not receive any
message from the target gNodeB before the preparation of an NG or Xn handover is
complete. Specifically, during an NG handover, the source cell receives neither a
HANDOVER COMMAND message nor a HANDOVER PREPARATION FAILURE
message from the AMF; during an Xn handover, the source cell receives neither a
HANDOVER REQUEST ACKNOWLEDGE message nor a HANDOVER PREPARATION
FAILURE message. If the source cell and the target cell work on the same frequency, the
value of the N.HO.IntraFreq.Prep.FailOut.NoReply counter is incremented by 1.
As shown at point B in Figure 1-93 and Figure 1-94, the source cell receives a HANDOVER
COMMAND message from the AMF during the preparation of an NG handover, or receives a
HANDOVER REQUEST ACKNOWLEDGE message from the target cell during the
preparation of an Xn handover. The received message fails the validity check and the source
cell decides to cancel this handover. If the source cell and the target cell work on the same
frequency, the value of the N.HO.IntraFreq.Prep.FailOut.TargetIllegal counter is incremented
by 1.

Figure 1-83
Figure 1-84
Figure 1-85

Figure 1-86
Figure 1-87
Figure 1-88

Figure 1-89
Figure 1-90
Figure 1-91

Figure 1-92
Figure 1-93
Figure 1-94
Formula
None

Unit
None
Related Features
N.HO.IntraFreq.Prep.FailOu Multi-mode: None

t.HOCancel GSM: None
UMTS: None
LTE: None
N.HO.IntraFreq.FailOut.Pre Multi-mode: None

pFailure GSM: None
UMTS: None
LTE: None
N.HO.IntraFreq.FailOut.HO Multi-mode: None

Cancel GSM: None
UMTS: None
LTE: None

t.AMF GSM: None
UMTS: None
LTE: None

t.NoReply GSM: None
UMTS: None
LTE: None

t.TargetIllegal GSM: None
UMTS: None
LTE: None

1.1.27 Outgoing Inter-RAT Handover Measurement

(N.HO.InterRAT)
Overview
The N.HO.InterRAT function subset measures the performance related to handovers from NR
to E-UTRAN.
Counters
1911817044 N.RRCRedirection. Total number of BTS5900 5G:

N2E.Coverage coverage-based V100R015C10
redirections to E- BTS3900:
UTRAN V100R015C10
BTS5900:
V100R015C10
1911817056 N.HO.InterRAT.N2 Number of handover BTS5900 5G:

E.PrepAttOut preparation attempts V100R015C10
from NR to E- BTS3900:
UTRAN V100R015C10
BTS5900:
V100R015C10
1911817057 N.HO.InterRAT.N2 Number of BTS5900 5G:

E.AMFAbnormRsp responses for V100R015C10
abnormal causes BTS3900:
received by the V100R015C10
gNodeB from the BTS5900:
NGC during V100R015C10
outgoing handover
executions from NR
to E-UTRAN

E.Coverage.PrepAt coverage-based V100R015C10
tOut handover BTS3900:
preparation attempts V100R015C10
UTRAN V100R015C10
1911817059 N.HO.InterRAT.N2 Number of failed BTS5900 5G:

E.Prep.FailOut.No outgoing handover V100R015C10
Reply preparations due to BTS3900:
no responses from V100R015C10
E-UTRAN BTS5900:
V100R015C10



E.Coverage.ExecSu successful coverage- V100R015C10
ccOut based outgoing BTS3900:
handovers from NR V100R015C10
to E-UTRAN BTS5900:
V100R015C10
1911817061 N.HO.InterRAT.N2 Number of outgoing BTS5900 5G:

E.ExecAttOut handover executions V100R015C10
UTRAN V100R015C10
BTS5900:
V100R015C10

E.Coverage.ExecAt coverage-based V100R015C10
tOut outgoing handover BTS3900:
executions from NR V100R015C10
to E-UTRAN BTS5900:
V100R015C10

E.ExecSuccOut successful outgoing V100R015C10
handovers from NR BTS3900:
to E-UTRAN V100R015C10
BTS5900:
V100R015C10

E.Prep.FailOut.A handover V100R015C10
MF preparation failures BTS3900:
from NR to E- V100R015C10
UTRAN due to BTS5900:
faults in the core V100R015C10
network
1911817065 N.HO.InterRAT.N2 Number of failed BTS5900 5G:

E.Prep.FailOut.Pre outgoing handover V100R015C10
pFailure preparations due to BTS3900:
handover V100R015C10
preparation failure BTS5900:
replied by E- V100R015C10
UTRAN

E.EPSFB.ExecSucc successful outgoing V100R015C10
Out EPS fallbacks from BTS3900:
NR to E-UTRAN V100R015C10
BTS5900:
V100R015C10



E.EPSFB.ExecAtt EPS fallback V100R015C10
Out executions from NR BTS3900:
to E-UTRAN V100R015C10
BTS5900:
V100R015C10
1911817069 N.HO.InterRAT.N2 Number of EPS BTS5900 5G:

E.EPSFB.PrepAtt fallback preparation V100R015C10
Out attempts from NR to BTS3900:
E-UTRAN V100R015C10
BTS5900:
V100R015C10
1911817084 N.RRCRedirection. Total number of EPS BTS3900:

N2E.EPSFB fallback redirections V100R015C10
UTRAN V100R015C10
BTS5900 5G:
V100R015C10
Root Counter Level-1 Counter
N.HO.InterRAT.N2E.PrepAttOut N.HO.InterRAT.N2E.Coverage.PrepAttOut
N.HO.InterRAT.N2E.PrepAttOut N.HO.InterRAT.N2E.EPSFB.PrepAttOut
N.HO.InterRAT.N2E.ExecAttOut N.HO.InterRAT.N2E.Coverage.ExecAttOut
N.HO.InterRAT.N2E.ExecAttOut N.HO.InterRAT.N2E.EPSFB.ExecAttOut
N.HO.InterRAT.N2E.ExecSuccOut N.HO.InterRAT.N2E.Coverage.ExecSuccO
ut
N.HO.InterRAT.N2E.ExecSuccOut N.HO.InterRAT.N2E.EPSFB.ExecSuccOut

1.1.27.1 Number of Redirections from NR to E-UTRAN
Counters
1911817044 N.RRCRedirect Total number of BTS3900, N

ion.N2E.Covera coverage-based BTS3900 5G,
ge redirections to BTS5900,
E-UTRAN
BTS5900 5G
1911817084 N.RRCRedirect Total number of BTS3900, N

ion.N2E.EPSF EPS fallback BTS3900 5G,
B redirections BTS5900,
from NR to E-
UTRAN BTS5900 5G
Description
The counter measures the total number of inter-RAT redirections triggered by the gNodeB.
The signaling procedures involved in the counters comply with section 5.3.8 in 3GPP TS
38.331 V15.1.0.
Measurement Points
As shown at point A in Figure 1-95, when the gNodeB sends an RRC Release message to the
UE during an inter-RAT coverage-based redirection procedure, if the target system is E-
UTRAN, the value of N.RRCRedirection.N2E.Coverage is incremented by 1.
As shown at point A in Figure 1-95, when the gNodeB determines to perform an EPS
fallback procedure to E-UTRAN and sends an RRC Release message to the concerned UE,
the value of N.RRCRedirection.N2E.EPSFB is incremented by 1.
Figure 1-95

Formula
None
Unit
None
Related Features
N.RRCRedirection.N2E.Co Multi-mode: None

verage GSM: None
UMTS: None
LTE: None
NR: FOFD-021209 Inter-RAT Mobility from
NG-RAN to E-UTRAN
N.RRCRedirection.N2E.EP Multi-mode: None

SFB GSM: None
UMTS: None
LTE: None
NR: FOFD-021210 Voice Fallback
1.1.27.2 Number of Outgoing Handovers from NR to E-UTRAN
Counters
1911817056 N.HO.InterRAT Number of BTS3900, N

.N2E.PrepAttO handover BTS3900 5G,
ut preparation BTS5900,
attempts from
NR to E- BTS5900 5G
UTRAN



.N2E.AMFAbn responses for BTS3900 5G,
ormRsp abnormal BTS5900,
causes received
by the gNodeB BTS5900 5G
from the NGC
during outgoing
handover
executions from
NR to E-
UTRAN

.N2E.Coverage. coverage-based BTS3900 5G,
PrepAttOut handover BTS5900,
preparation
attempts from BTS5900 5G
NR to E-
UTRAN

.N2E.Prep.Fail failed outgoing BTS3900 5G,
Out.NoReply handover BTS5900,
preparations
due to no BTS5900 5G
responses from
E-UTRAN

.N2E.Coverage. successful BTS3900 5G,
ExecSuccOut coverage-based BTS5900,
outgoing
handovers from BTS5900 5G
NR to E-
UTRAN

.N2E.ExecAttO outgoing BTS3900 5G,
ut handover BTS5900,
executions from
NR to E- BTS5900 5G
UTRAN

.N2E.Coverage. coverage-based BTS3900 5G,
ExecAttOut outgoing BTS5900,
handover
executions from BTS5900 5G
NR to E-
UTRAN



.N2E.ExecSucc successful BTS3900 5G,
Out outgoing BTS5900,
handovers from
NR to E- BTS5900 5G
UTRAN

.N2E.Prep.Fail outgoing BTS3900 5G,
Out.AMF handover BTS5900,
preparation
failures from BTS5900 5G
NR to E-
UTRAN due to
faults in the
core network

.N2E.Prep.Fail failed outgoing BTS3900 5G,
Out.PrepFailure handover BTS5900,
preparations
due to handover BTS5900 5G
preparation
failure replied
by E-UTRAN
Description
The counters measure the numbers related to outgoing handovers from NR to E-UTRAN. The
signaling procedures involved in the counters comply with section 5.4 in 3GPP TS 38.331
V15.1.0.
Measurement Points
As shown at point A in Figure 1-96, the N.HO.InterRAT.N2E.PrepAttOut counter is
incremented by 1 each time the gNodeB decides to perform a blind handover to E-UTRAN or
decides to perform a handover to E-UTRAN after receiving a measurement report sent from
the UE.
As shown at point B in Figure 1-96, the N.HO.InterRAT.N2E.ExecAttOut counter is
incremented by 1 each time the gNodeB sends a HANDOVER COMMAND message to the
UE to execute a handover from NR to E-UTRAN.
As shown at point C in Figure 1-96, the N.HO.InterRAT.N2E.ExecSuccOut counter is
incremented by 1 each time the gNodeB receives a UE CONTEXT RELEASE COMMAND
message from the AMF after a UE is handed over from NR to E-UTRAN.
As shown at point A in Figure 1-96, the N.HO.InterRAT.N2E.Coverage.PrepAttOut counter
is incremented by 1 each time the gNodeB decides to perform a handover to E-UTRAN after
receiving a coverage-based measurement report from a UE.

As shown at point B in Figure 1-96, the N.HO.InterRAT.N2E.Coverage.ExecAttOut counter

is incremented by 1 each time the gNodeB sends a HANDOVER COMMAND message to the
UE to execute a coverage-based handover from NR to E-UTRAN.
As shown at point C in Figure 1-96, the N.HO.InterRAT.N2E.Coverage.ExecSuccOut counter
is incremented by 1 each time the gNodeB receives a UE CONTEXT RELEASE
COMMAND message from the AMF after a UE is handed over from NR to E-UTRAN by a
coverage-based handover.
As shown at point A in Figure 1-97, when the gNodeB does not receive a HANDOVER
COMMAND message from the AMF after sending a HANDOVER REQUIRED message to
the AMF, the N.HO.InterRAT.N2E.Prep.FailOut.NoReply counter is incremented by 1 if the
target RAT is E-UTRAN.
As shown at point A in Figure 1-98, when the gNodeB receives a HANDOVER
PREPARATION FAILURE message from the AMF after sending a HANDOVER
REQUIRED message to the AMF, the N.HO.InterRAT.N2E.Prep.FailOut.PrepFailure counter
is incremented by 1 if the target RAT is E-UTRAN.
COMMAND message from the AMF after sending a HANDOVER REQUIRED message to
the AMF, the N.HO.InterRAT.N2E.Prep.FailOut.AMF counter is incremented by 1 if the
target RAT is E-UTRAN.
As shown at point C in Figure 1-96, during a handover from NR to E-UTRAN, the
N.HO.InterRAT.N2E.AMFAbnormRsp counter is incremented by 1 when the gNodeB
receives a UE CONTEXT RELEASE COMMAND message from the AMF with the release
cause value not being "Successful Handover" or "Normal Release".

Figure 1-96
Figure 1-97

Figure 1-98
Figure 1-99
Formula
None

Unit
None
Related Features
N.HO.InterRAT.N2E.PrepAt Multi-mode: None

tOut GSM: None
UMTS: None
LTE: None
NG-RAN to E-UTRAN
N.HO.InterRAT.N2E.AMFA Multi-mode: None

bnormRsp GSM: None
UMTS: None
LTE: None
NG-RAN to E-UTRAN
N.HO.InterRAT.N2E.Cover Multi-mode: None

age.PrepAttOut GSM: None
UMTS: None
LTE: None
NG-RAN to E-UTRAN
N.HO.InterRAT.N2E.Prep.F Multi-mode: None

ailOut.NoReply GSM: None
UMTS: None
LTE: None
NG-RAN to E-UTRAN

age.ExecSuccOut GSM: None
UMTS: None
LTE: None
NG-RAN to E-UTRAN

N.HO.InterRAT.N2E.ExecA Multi-mode: None

ttOut GSM: None
UMTS: None
LTE: None
NG-RAN to E-UTRAN

age.ExecAttOut GSM: None
UMTS: None
LTE: None
NG-RAN to E-UTRAN
N.HO.InterRAT.N2E.ExecS Multi-mode: None

uccOut GSM: None
UMTS: None
LTE: None
NG-RAN to E-UTRAN

ailOut.AMF GSM: None
UMTS: None
LTE: None
NG-RAN to E-UTRAN

ailOut.PrepFailure GSM: None
UMTS: None
LTE: None
NG-RAN to E-UTRAN

1.1.27.3 Number of EPS Fallback Executions from NR to an Inter-RAT System
Counters

.N2E.EPSFB.E successful BTS3900 5G,
xecSuccOut outgoing EPS BTS5900,
fallbacks from
NR to E- BTS5900 5G
UTRAN

.N2E.EPSFB.E outgoing EPS BTS3900 5G,
xecAttOut fallback BTS5900,
executions from
NR to E- BTS5900 5G
UTRAN
1911817069 N.HO.InterRAT Number of EPS BTS3900, N

.N2E.EPSFB.Pr fallback BTS3900 5G,
epAttOut preparation BTS5900,
attempts from
NR to E- BTS5900 5G
UTRAN
Description
The counters measure the number of EPS fallbacks from NR to an inter-RAT system. The
signaling procedures involved in the counters comply with section 4.13.6 in 3GPP TS 23.502
V15.2.0.
Measurement Points
As shown at point A in Figure 1-100, when the gNodeB receives a Measurement Report
message from the UE, if the gNodeB determines to execute an EPS fallback to E-UTRAN, the
value of N.HO.InterRAT.N2E.EPSFB.PrepAttOut is incremented by 1.
As shown at point B in Figure 1-100, when the gNodeB sends a Mobility From NR
Command message to the UE and executes an EPS fallback procedure to E-UTRAN, the
value of N.HO.InterRAT.N2E.EPSFB.ExecAttOut is incremented by 1.
As shown at point C in Figure 1-100, when the gNodeB receives a UE CONTEXT
RELEASE COMMAND message from the AMF during the UE's EPS fallback procedure to
E-UTRAN, the value of N.HO.InterRAT.N2E.EPSFB.ExecSuccOut is incremented by 1.

Figure 1-100
Formula
None
Unit
None
Related Features
N.HO.InterRAT.N2E.EPSF Multi-mode: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None
1.2 Measurement of DU Cell Performance (NRDUCELL)

Overview
The NRDUCELL object type contains NR DU cell-level function subsets.
FunctionSubSets
ChMeas.256QAM.CQI.DuCell Measurement of CQIs in the CQI Table with

256QAM (ChMeas.256QAM.CQI.DuCell)
ChMeas.64QAM.CQI.DuCell Measurement of CQIs in the CQI Table with

64QAM (ChMeas.64QAM.CQI.DuCell)
ChMeas.CQI.DuCell CQI Measurement(ChMeas.CQI.DuCell)
Algo.DuCell DU Cell Algorithm Measurement

(Algo.DuCell)
MAC.DuCell MAC Measurement(MAC.DuCell)
ChMeas.MCS.DuCell MCS Measurement(ChMeas.MCS.DuCell)
MIMO.DuCell MIMO Channel Measurement

(MIMO.DuCell)
ScheUser.DuCell NR DU Cell Schedule User Quantity

Measurement(ScheUser.DuCell)
Reserve.DuCell NR DU Cell Reserved Counter

Measurement(Reserve.DuCel)

ChMeas.PDSCH.256QAM.MCS.DuCell Measurement per MCS Index in the MCS

Index Table for PDSCH with 256QAM
(ChMeas.PDSCH.256QAM.MCS.DuCell)
ChMeas.PDSCH.64QAM.MCS.DuCell Measurement per MCS Index in the MCS

Index Table for PDSCH with 64QAM
(ChMeas.PDSCH.64QAM.MCS.DuCell)
PRB.DuCell PRB Measurement(PRB.DuCell)
ChMeas.PUSCH.256QAM.MCS.DuCell Measurement per MCS Index in the MCS

Index Table for PUSCH with 256QAM
(ChMeas.PUSCH.256QAM.MCS.DuCell)
ChMeas.PUSCH.64QAMTP.MCS.DuCell Measurement per MCS Index in the MCS

Index Table for PUSCH with Transform
Precoding and 64QAM (ChMeas.PUSCH.
64QAMTP.MCS.DuCell)
ChMeas.PUSCH.64QAM.MCS.DuCell Measurement per MCS Index in the MCS

Index Table for PUSCH with 64QAM
(ChMeas.PUSCH.64QAM.MCS.DuCell)
RLC.DuCell RLC Measurement(RLC.DuCell)
ChMeas.Pwr.DuCell Channel Quality

Measurement(ChMeas.Pwr.DuCell)
CA.DuCell DU Cell CA Measurement(CA.DuCell)
Thp.PDF.DuCell UE Throughput Distribution

Measurement(Thp.PDF.DuCell)
Thp.DuCell Throughput and Data Volume

Measurement(Thp.DuCell)
QoS.Cell Cell Service Quality Measurement

(QoS.Cell)
Paging.Cell Paging Measurement (Paging.Cell)
RA.DuCell Random Access Measurement(RA.DuCell)
1.2.1 Measurement of CQIs in the CQI Table with 256QAM

(ChMeas.256QAM.CQI.DuCell)
Overview
Channel quality indicator (CQI) indicates downlink channel quality. The UE calculates the
CQI value and reports it to the gNodeB through an uplink channel. The gNodeB uses the CQI
as the input for MAC scheduling. The ChMeas.256QAM.CQI.DuCell function subset
measures the number of times wideband CQIs with different indexes are reported. The result

indicates the overall quality of the downlink channel in the NR DU cell. For details, see "4-bit
CQI Table 2" in 3GPP TS 38.214.
Counters
1911817120 N.ChMeas.CQI. Number of BTS3900:

256QAM.RANK1. wideband CQI V100R015C10
SingleCW.0 reports with CQI BTS5900 5G:
index 0 in the CQI V100R015C10
table with 256QAM BTS5900:
indicating channel V100R015C10
quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission



quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission



quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission



quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission



quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission



quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission



quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission



quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission



quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission



quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-4
transmission



quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission



quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission



quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

None
1.2.1.1 Number of Wideband CQI Reports with 256QAM in Single-Codeword

Transmission in a Cell
Counters
1911817120 N.ChMeas.CQI. Number of BTS3900, N

256QAM.RAN wideband CQI BTS3900 5G,
K1.SingleCW.0 reports with BTS5900,
CQI index 0 in
the CQI table BTS5900 5G
with 256QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 1 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 2 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-1
transmission



CQI index 3 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 4 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 5 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-1
transmission



CQI index 6 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 7 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 8 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-1
transmission



CQI index 9 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

K1.SingleCW. reports with BTS5900,
10 CQI index 10 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

11 CQI index 11 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-1
transmission



12 CQI index 12 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

13 CQI index 13 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

14 CQI index 14 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-1
transmission



15 CQI index 15 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 0 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 1 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-2
transmission



CQI index 2 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 3 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 4 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-2
transmission



CQI index 5 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 6 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 7 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-2
transmission



CQI index 8 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 9 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

10 CQI index 10 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-2
transmission



11 CQI index 11 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

12 CQI index 12 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

13 CQI index 13 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-2
transmission



14 CQI index 14 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

15 CQI index 15 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 0 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-3
transmission



CQI index 1 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 2 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 3 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-3
transmission



CQI index 4 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 5 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 6 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-3
transmission



CQI index 7 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 8 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 9 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-3
transmission



10 CQI index 10 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

11 CQI index 11 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

12 CQI index 12 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-3
transmission



13 CQI index 13 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

14 CQI index 14 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

15 CQI index 15 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-3
transmission



CQI index 0 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

CQI index 1 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

CQI index 2 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-4
transmission



CQI index 3 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

CQI index 4 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

CQI index 5 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-4
transmission



CQI index 6 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

CQI index 7 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

CQI index 8 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-4
transmission



CQI index 9 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

10 CQI index 10 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

11 CQI index 11 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-4
transmission



12 CQI index 12 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

13 CQI index 13 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

14 CQI index 14 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-4
transmission



15 CQI index 15 in
with 256QAM
indicating
channel quality
of single-
codeword
rank-4
transmission
Description
Channel Quality Indicator (CQI) indicates downlink channel quality. The UE calculates the
report as the input of MAC scheduling. Each counter measures the number of wideband CQI
reports with a specific CQI index received from UEs using the 4-bit CQI table 2 in 3GPP TS
38.214 in single-codeword transmission in a cell. They are used to evaluate the overall quality
of downlink channels.
Measurement Points
Based on the rank value and CQI value, the corresponding counter is incremented by 1 each
time the gNodeB receives a wideband CQI report from a UE with 256QAM enabled in single-
codeword transmission. The CQI value ranges from 0 to 15.
Formula
None
Unit
None
Related Features
N.ChMeas.CQI. Multi-mode: None

256QAM.RANK1.SingleC GSM: None
W.0
UMTS: None
LTE: None


W.1
UMTS: None
LTE: None

W.2
UMTS: None
LTE: None

W.3
UMTS: None
LTE: None

W.4
UMTS: None
LTE: None

W.5
UMTS: None
LTE: None

W.6
UMTS: None
LTE: None

W.7
UMTS: None
LTE: None


W.8
UMTS: None
LTE: None

W.9
UMTS: None
LTE: None

W.10
UMTS: None
LTE: None

W.11
UMTS: None
LTE: None

W.12
UMTS: None
LTE: None

W.13
UMTS: None
LTE: None

W.14
UMTS: None
LTE: None


W.15
UMTS: None
LTE: None

W.0
UMTS: None
LTE: None

W.1
UMTS: None
LTE: None

W.2
UMTS: None
LTE: None

W.3
UMTS: None
LTE: None

W.4
UMTS: None
LTE: None

W.5
UMTS: None
LTE: None


W.6
UMTS: None
LTE: None

W.7
UMTS: None
LTE: None

W.8
UMTS: None
LTE: None

W.9
UMTS: None
LTE: None

W.10
UMTS: None
LTE: None

W.11
UMTS: None
LTE: None

W.12
UMTS: None
LTE: None


W.13
UMTS: None
LTE: None

W.14
UMTS: None
LTE: None

W.15
UMTS: None
LTE: None

W.0
UMTS: None
LTE: None

W.1
UMTS: None
LTE: None

W.2
UMTS: None
LTE: None

W.3
UMTS: None
LTE: None


W.4
UMTS: None
LTE: None

W.5
UMTS: None
LTE: None

W.6
UMTS: None
LTE: None

W.7
UMTS: None
LTE: None

W.8
UMTS: None
LTE: None

W.9
UMTS: None
LTE: None

W.10
UMTS: None
LTE: None


W.11
UMTS: None
LTE: None

W.12
UMTS: None
LTE: None

W.13
UMTS: None
LTE: None

W.14
UMTS: None
LTE: None

W.15
UMTS: None
LTE: None

W.0
UMTS: None
LTE: None

W.1
UMTS: None
LTE: None


W.2
UMTS: None
LTE: None

W.3
UMTS: None
LTE: None

W.4
UMTS: None
LTE: None

W.5
UMTS: None
LTE: None

W.6
UMTS: None
LTE: None

W.7
UMTS: None
LTE: None

W.8
UMTS: None
LTE: None


W.9
UMTS: None
LTE: None

W.10
UMTS: None
LTE: None

W.11
UMTS: None
LTE: None

W.12
UMTS: None
LTE: None

W.13
UMTS: None
LTE: None

W.14
UMTS: None
LTE: None

W.15
UMTS: None
LTE: None

1.2.2 Measurement of CQIs in the CQI Table with 64QAM

(ChMeas.64QAM.CQI.DuCell)
Overview
as the input for MAC scheduling. The ChMeas.64QAM.CQI.DuCell function subset measures
the number of times wideband CQIs with different indexes are reported. The result indicates
the overall quality of the downlink channel in the NR DU cell. For details, see "4-bit CQI
Table" in 3GPP TS 38.214.
Counters

64QAM.RANK1.Si wideband CQI V100R015C10
ngleCW.0 reports with CQI BTS5900:
table with 64QAM BTS5900 5G:
quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission



quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission



quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission



quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-1
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission



quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission



quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission



quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-2
transmission

quality of single-
codeword rank-3
transmission



quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission



quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission



quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission

quality of single-
codeword rank-3
transmission



quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission



quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission



quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission

quality of single-
codeword rank-4
transmission



quality of single-
codeword rank-4
transmission
None
1.2.2.1 Number of Wideband CQI Reports with Different CQI indexes in the CQI
Table with 64QAM in Singe-Codeword Transmission in a Cell
Counters

64QAM.RANK wideband CQI BTS3900 5G,
1.SingleCW.0 reports with BTS5900,
CQI index 0 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 1 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-1
transmission



CQI index 2 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 3 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 4 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-1
transmission



CQI index 5 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 6 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 7 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-1
transmission



CQI index 8 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 9 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 10 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-1
transmission



CQI index 11 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 12 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 13 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-1
transmission



CQI index 14 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 15 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-1
transmission

CQI index 0 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-2
transmission



CQI index 1 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 2 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 3 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-2
transmission



CQI index 4 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 5 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 6 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-2
transmission



CQI index 7 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 8 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 9 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-2
transmission



CQI index 10 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 11 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 12 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-2
transmission



CQI index 13 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 14 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-2
transmission

CQI index 15 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-2
transmission



CQI index 0 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 1 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 2 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-3
transmission



CQI index 3 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 4 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 5 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-3
transmission



CQI index 6 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 7 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 8 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-3
transmission



CQI index 9 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 10 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 11 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-3
transmission



CQI index 12 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 13 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 14 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-3
transmission



CQI index 15 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-3
transmission

CQI index 0 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

CQI index 1 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-4
transmission



CQI index 2 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

CQI index 3 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

CQI index 4 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-4
transmission



CQI index 5 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

CQI index 6 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

CQI index 7 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-4
transmission



CQI index 8 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

CQI index 9 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

CQI index 10 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-4
transmission



CQI index 11 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

CQI index 12 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

CQI index 13 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-4
transmission



CQI index 14 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-4
transmission

CQI index 15 in
with 64QAM
indicating
channel quality
of single-
codeword
rank-4
transmission
Description
report as the input of MAC scheduling. Each counter measures the number of wideband CQI
reports with a specific CQI index received from UEs using the 4-bit CQI table in 3GPP TS
38.214 in single-codeword transmission in a cell. They are used to evaluate the overall quality
of downlink channels.
Measurement Points
Based on the rank value and CQI value, the corresponding counter is incremented by 1 each
time the gNodeB receives a wideband CQI report from a UE with 64QAM enabled in single-
codeword transmission. The CQI value ranges from 0 to 15.
Formula
None
Unit
None

Related Features

64QAM.RANK1.SingleCW. GSM: None
0
UMTS: None
LTE: None

1
UMTS: None
LTE: None

2
UMTS: None
LTE: None

3
UMTS: None
LTE: None

4
UMTS: None
LTE: None

5
UMTS: None
LTE: None

6
UMTS: None
LTE: None


7
UMTS: None
LTE: None

8
UMTS: None
LTE: None

9
UMTS: None
LTE: None

10
UMTS: None
LTE: None

11
UMTS: None
LTE: None

12
UMTS: None
LTE: None

13
UMTS: None
LTE: None


14
UMTS: None
LTE: None

15
UMTS: None
LTE: None

0
UMTS: None
LTE: None

1
UMTS: None
LTE: None

2
UMTS: None
LTE: None

3
UMTS: None
LTE: None

4
UMTS: None
LTE: None


5
UMTS: None
LTE: None

6
UMTS: None
LTE: None

7
UMTS: None
LTE: None

8
UMTS: None
LTE: None

9
UMTS: None
LTE: None

10
UMTS: None
LTE: None

11
UMTS: None
LTE: None


12
UMTS: None
LTE: None

13
UMTS: None
LTE: None

14
UMTS: None
LTE: None

15
UMTS: None
LTE: None

0
UMTS: None
LTE: None

1
UMTS: None
LTE: None

2
UMTS: None
LTE: None


3
UMTS: None
LTE: None

4
UMTS: None
LTE: None

5
UMTS: None
LTE: None

6
UMTS: None
LTE: None

7
UMTS: None
LTE: None

8
UMTS: None
LTE: None

9
UMTS: None
LTE: None


10
UMTS: None
LTE: None

11
UMTS: None
LTE: None

12
UMTS: None
LTE: None

13
UMTS: None
LTE: None

14
UMTS: None
LTE: None

15
UMTS: None
LTE: None

0
UMTS: None
LTE: None


1
UMTS: None
LTE: None

2
UMTS: None
LTE: None

3
UMTS: None
LTE: None

4
UMTS: None
LTE: None

5
UMTS: None
LTE: None

6
UMTS: None
LTE: None

7
UMTS: None
LTE: None


8
UMTS: None
LTE: None

9
UMTS: None
LTE: None

10
UMTS: None
LTE: None

11
UMTS: None
LTE: None

12
UMTS: None
LTE: None

13
UMTS: None
LTE: None

14
UMTS: None
LTE: None


15
UMTS: None
LTE: None
1.2.3 CQI Measurement (ChMeas.CQI.DuCell)

Overview
as the input for MAC scheduling. The CQI Measurement(ChMeas.CQI.DuCell) function
subset measures the number of CQI reports with different values separately in an NR DU cell.
It is used to evaluate overall downlink channel quality.
Counters
1911816595 N.ChMeas.CQI.Sin Number of BTS5900 5G:

gleCW.0 wideband CQI V100R013C10
reports with a value BTS5900:
of 0 in single- V100R013C10
codeword BTS3900:
transmission V100R015C00

codeword BTS3900:

codeword BTS3900:



codeword BTS3900:

codeword BTS3900:

codeword BTS3900:

codeword BTS3900:

codeword BTS3900:

codeword BTS3900:

codeword BTS3900:



codeword BTS3900:

codeword BTS3900:

codeword BTS3900:

codeword BTS3900:

codeword BTS3900:

codeword BTS3900:
1911816611 N.ChMeas.CQI.Du Number of BTS5900 5G:

alCW.Code0.0 wideband CQI V100R013C10
of 0 for codeword 0 V100R013C10
in dual-codeword BTS3900:














of 10 for codeword V100R013C10
0 in dual-codeword BTS3900:



























None
1.2.3.1 Number of Wideband CQI Reports in Single-Codeword Transmission in a

Cell
Counters

SingleCW.0 wideband CQI BTS3900 5G,
reports with a BTS5900,
value of 0 in
single- BTS5900 5G
codeword
transmission



value of 1 in
single- BTS5900 5G
codeword
transmission

value of 2 in
single- BTS5900 5G
codeword
transmission

value of 3 in
single- BTS5900 5G
codeword
transmission

value of 4 in
single- BTS5900 5G
codeword
transmission

value of 5 in
single- BTS5900 5G
codeword
transmission

value of 6 in
single- BTS5900 5G
codeword
transmission



value of 7 in
single- BTS5900 5G
codeword
transmission

value of 8 in
single- BTS5900 5G
codeword
transmission

value of 9 in
single- BTS5900 5G
codeword
transmission

value of 10 in
single- BTS5900 5G
codeword
transmission

value of 11 in
single- BTS5900 5G
codeword
transmission

value of 12 in
single- BTS5900 5G
codeword
transmission



value of 13 in
single- BTS5900 5G
codeword
transmission

value of 14 in
single- BTS5900 5G
codeword
transmission

value of 15 in
single- BTS5900 5G
codeword
transmission
Description
as the input for MAC scheduling. Each counter measures the number of wideband CQI
reports with a specific value in single-codeword transmission in a cell. They are used to
evaluate the overall quality of downlink channels.
Measurement Points
Based on the CQI value, the corresponding counter is incremented by 1 each time the gNodeB
receives a wideband CQI report from a UE in single-codeword transmission. The CQI value
ranges from 0 to 15.
Formula
None
Unit
None

Related Features
N.ChMeas.CQI.SingleCW.0 Multi-mode: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None


GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None
N.ChMeas.CQI.SingleCW. Multi-mode: None

10 GSM: None
UMTS: None
LTE: None

11 GSM: None
UMTS: None
LTE: None

12 GSM: None
UMTS: None
LTE: None

13 GSM: None
UMTS: None
LTE: None


14 GSM: None
UMTS: None
LTE: None

15 GSM: None
UMTS: None
LTE: None
1.2.3.2 Number of Wideband CQI Reports for Codeword 0 in Dual-Codeword

Counters

DualCW.Code0 wideband CQI BTS3900 5G,
.0 reports with a BTS5900,
value of 0 for
codeword 0 in BTS5900 5G
dual-codeword
transmission

value of 1 for
dual-codeword
transmission

value of 2 for
dual-codeword
transmission



value of 3 for
dual-codeword
transmission

value of 4 for
dual-codeword
transmission

value of 5 for
dual-codeword
transmission

value of 6 for
dual-codeword
transmission

value of 7 for
dual-codeword
transmission

value of 8 for
dual-codeword
transmission



value of 9 for
dual-codeword
transmission

value of 10 for
dual-codeword
transmission

value of 11 for
dual-codeword
transmission

value of 12 for
dual-codeword
transmission

value of 13 for
dual-codeword
transmission

value of 14 for
dual-codeword
transmission



value of 15 for
dual-codeword
transmission
Description
reports with a specific value for codeword 0 in dual-codeword transmission in a cell. They are
used to evaluate the overall quality of downlink channels.
Measurement Points
receives a wideband CQI report from a UE for codeword 0 in dual-codeword transmission.
The CQI value ranges from 0 to 15.
Formula
None
Unit
None
Related Features
N.ChMeas.CQI.DualCW.Co Multi-mode: None

de0.0 GSM: None
UMTS: None
LTE: None

de0.1 GSM: None
UMTS: None
LTE: None


de0.2 GSM: None
UMTS: None
LTE: None

de0.3 GSM: None
UMTS: None
LTE: None

de0.4 GSM: None
UMTS: None
LTE: None

de0.5 GSM: None
UMTS: None
LTE: None

de0.6 GSM: None
UMTS: None
LTE: None

de0.7 GSM: None
UMTS: None
LTE: None

de0.8 GSM: None
UMTS: None
LTE: None


de0.9 GSM: None
UMTS: None
LTE: None

de0.10 GSM: None
UMTS: None
LTE: None

de0.11 GSM: None
UMTS: None
LTE: None

de0.12 GSM: None
UMTS: None
LTE: None

de0.13 GSM: None
UMTS: None
LTE: None

de0.14 GSM: None
UMTS: None
LTE: None

de0.15 GSM: None
UMTS: None
LTE: None

1.2.3.3 Number of Wideband CQI Reports for Codeword 1 in Dual-Codeword

Counters

value of 0 for
dual-codeword
transmission

value of 1 for
dual-codeword
transmission

value of 2 for
dual-codeword
transmission

value of 3 for
dual-codeword
transmission

value of 4 for
dual-codeword
transmission



value of 5 for
dual-codeword
transmission

value of 6 for
dual-codeword
transmission

value of 7 for
dual-codeword
transmission

value of 8 for
dual-codeword
transmission

value of 9 for
dual-codeword
transmission

value of 10 for
dual-codeword
transmission



value of 11 for
dual-codeword
transmission

value of 12 for
dual-codeword
transmission

value of 13 for
dual-codeword
transmission

value of 14 for
dual-codeword
transmission

value of 15 for
dual-codeword
transmission
Description
reports with a specific value for codeword 1 in dual-codeword transmission in a cell. They are
used to evaluate the overall quality of downlink channels.

Measurement Points
receives a wideband CQI report from a UE for codeword 1 in dual-codeword transmission.
The CQI value ranges from 0 to 15.
Formula
None
Unit
None
Related Features

de1.0 GSM: None
UMTS: None
LTE: None

de1.1 GSM: None
UMTS: None
LTE: None

de1.2 GSM: None
UMTS: None
LTE: None

de1.3 GSM: None
UMTS: None
LTE: None

de1.4 GSM: None
UMTS: None
LTE: None


de1.5 GSM: None
UMTS: None
LTE: None

de1.6 GSM: None
UMTS: None
LTE: None

de1.7 GSM: None
UMTS: None
LTE: None

de1.8 GSM: None
UMTS: None
LTE: None

de1.9 GSM: None
UMTS: None
LTE: None

de1.10 GSM: None
UMTS: None
LTE: None

de1.11 GSM: None
UMTS: None
LTE: None


de1.12 GSM: None
UMTS: None
LTE: None

de1.13 GSM: None
UMTS: None
LTE: None

de1.14 GSM: None
UMTS: None
LTE: None

de1.15 GSM: None
UMTS: None
LTE: None
1.2.4 DU Cell Algorithm Measurement (Algo.DuCell)

Overview
The DU Cell Algorithm Measurement (Algo.DuCell) function subset measures the
measurement results related to the DU cell algorithm.
Counters
1911816762 N.RaidoRes.Heavy Duration of uplink BTS5900 5G:

Load.Dur.UL radio resource V100R015C00
evaluation in heavy BTS5900:
load state V100R015C00
BTS3900:
V100R015C00


1911816763 N.RaidoRes.Heavy Duration of BTS5900 5G:

Load.Dur.DL downlink radio V100R015C00
resource evaluation BTS5900:
in heavy load state V100R015C00
BTS3900:
V100R015C00
None
1.2.4.1 Duration of Radio Resource Evaluation in Heavy Load State
Counters
1911816762 N.RaidoRes.He Duration of BTS3900, N

avyLoad.Dur.U uplink radio BTS3900 5G,
L resource BTS5900,
evaluation in
heavy load state BTS5900 5G
1911816763 N.RaidoRes.He Duration of BTS3900, N

avyLoad.Dur.D downlink radio BTS3900 5G,
L resource BTS5900,
evaluation in
heavy load state BTS5900 5G
Description
The counters measure the duration of uplink and downlink radio resources in the heavy load
state.
Radio resource overload is evaluated based on the ratio of the sum of the minimum acceptable
rate of each bearer in a cell to the rate that can be provided by the current cell. The sum of the
minimum acceptable rate of each bearer is the quotient of DlMinAcceptableRate/
UlMinAcceptableRate of each bearer. The rate that can be provided by the current cell is
calculated based on the historical rates of the cell. When the ratio is greater than 100%, the
cell enters the heavy load state. When the ratio is less than 90%, the cell exits the heavy load
state.
Measurement Points
The uplink and downlink load status of a cell is sampled per second. If the sampled uplink or
downlink load of a cell is heavy, the corresponding counter is incremented by 1s.

Formula
None
Unit
s
Related Features
None
1.2.5 MAC Measurement (MAC.DuCell)
Overview
The MAC Measurement(MAC.DuCell) function subset is used for measurements on logical
channels and transport channels for different modulation schemes in an NR DU cell.
Counters
1911816583 N.UL.SCH.HalfPiB Number of TBs BTS5900 5G:

PSK.TB initially transmitted V100R013C10
on the uplink SCH BTS5900:
using the Pi/2 BPSK V100R013C10
modulation scheme BTS3900:
V100R015C00
1911816584 N.UL.SCH.QPSK. Number of TBs BTS5900 5G:

TB initially transmitted V100R013C10
using the QPSK V100R013C10
V100R015C00
1911816585 N.UL.SCH. Number of TBs BTS5900 5G:

16QAM.TB initially transmitted V100R013C10
using the 16QAM V100R013C10
V100R015C00

V100R015C00


1911816587 N.UL.SCH.HalfPiB Number of TBs BTS5900 5G:

PSK.TB.Retrans retransmitted on the V100R013C10
uplink SCH using BTS5900:
the Pi/2 BPSK V100R013C10
V100R015C00
1911816588 N.UL.SCH.QPSK. Number of TBs BTS5900 5G:

TB.Retrans retransmitted on the V100R013C10
uplink SCH using BTS5900:
the QPSK V100R013C10
V100R015C00

16QAM.TB.Retran retransmitted on the V100R013C10
s uplink SCH using BTS5900:
the 16QAM V100R013C10
V100R015C00

s uplink SCH using BTS5900:
V100R015C00
1911816591 N.UL.SCH.HalfPiB Number of uplink BTS5900 5G:

PSK.ErrTB.Rbler TBs that fail to be V100R013C10
correctly received BTS5900:
after the maximum V100R013C10
number of BTS3900:
retransmissions for V100R015C00
the Pi/2 BPSK
modulation scheme
is reached
1911816592 N.UL.SCH.QPSK. Number of uplink BTS5900 5G:

ErrTB.Rbler TBs that fail to be V100R013C10
number of BTS3900:
the QPSK
modulation scheme
is reached


1911816593 N.UL.SCH. Number of uplink BTS5900 5G:

16QAM.ErrTB.Rbl TBs that fail to be V100R013C10
er correctly received BTS5900:
number of BTS3900:
the 16QAM
modulation scheme
is reached

number of BTS3900:
the 64QAM
modulation scheme
is reached
1911816680 N.DL.SCH.QPSK. Number of TBs BTS5900 5G:

TB initially transmitted V100R013C10
on the downlink BTS5900:
SCH using the V100R013C10
QPSK modulation BTS3900:
scheme V100R015C00
1911816681 N.DL.SCH. Number of TBs BTS5900 5G:

16QAM modulation BTS3900:
scheme V100R015C00

64QAM modulation BTS3900:
scheme V100R015C00

256QAM BTS3900:
modulation scheme V100R015C00


1911816684 N.DL.SCH.QPSK. Number of TBs BTS5900 5G:

TB.Retrans retransmitted on the V100R013C10
downlink SCH using BTS5900:
the QPSK V100R013C10
V100R015C00

s downlink SCH using BTS5900:
V100R015C00

s downlink SCH using BTS5900:
V100R015C00

256QAM.TB.Retra retransmitted on the V100R013C10
ns downlink SCH using BTS5900:
V100R015C00
1911816688 N.DL.SCH.QPSK. Number of downlink BTS5900 5G:

ErrTB.Rbler TBs that fail to be V100R013C10
number of BTS3900:
the QPSK
modulation scheme
is reached
1911816689 N.DL.SCH. Number of downlink BTS5900 5G:

number of BTS3900:
the 16QAM
modulation scheme
is reached



number of BTS3900:
the 64QAM
modulation scheme
is reached

256QAM.ErrTB.R TBs that fail to be V100R013C10
bler correctly received BTS5900:
number of BTS3900:
the 256QAM
modulation scheme
is reached

V100R015C00

256QAM.TB.Retra retransmitted on the V100R015C00
ns uplink SCH using BTS5900:
V100R015C00

256QAM.ErrTB.R TBs that fail to be V100R015C00
bler retransmitted after BTS5900:
the maximum V100R015C00
number of BTS3900:
the 256QAM
modulation scheme
is reached
1911817360 N.DL.SCH.QPSK. Number of TBs BTS3900:

ErrTB.Ibler failing to be initially V100R015C10
transmitted on the BTS5900:
downlink SCH in V100R015C10
the QPSK BTS5900 5G:


1911817361 N.DL.SCH. Number of TBs BTS3900:

16QAM.ErrTB.Ibl failing to be initially V100R015C10
er transmitted on the BTS5900:
the 16QAM BTS5900 5G:

64QAM.ErrTB.Ibl failing to be initially V100R015C10
er transmitted on the BTS5900:

256QAM.ErrTB.Ib failing to be initially V100R015C10
ler transmitted on the BTS5900:
None
1.2.5.1 Number of TBs Initially Transmitted on the Uplink SCH
Counters
1911816583 N.UL.SCH.Half Number of TBs BTS3900, N

PiBPSK.TB initially BTS3900 5G,
transmitted on BTS5900,
the uplink SCH
using the Pi/2 BTS5900 5G
BPSK
modulation
scheme


1911816584 N.UL.SCH.QP Number of TBs BTS3900, N

SK.TB initially BTS3900 5G,
the uplink SCH
using the QPSK BTS5900 5G
modulation
scheme
1911816585 N.UL.SCH. Number of TBs BTS3900, N

16QAM.TB initially BTS3900 5G,
the uplink SCH
using the BTS5900 5G
16QAM
modulation
scheme

the uplink SCH
64QAM
modulation
scheme

the uplink SCH
256QAM
modulation
scheme
Description
The gNodeB determines an MCS index for initial transmission by a UE based on the uplink
channel quality. Each MCS index maps to a modulation scheme, such as Pi/2 BPSK, QPSK,
16QAM, 64QAM, and 256QAM. Each counter measures the number of TBs initially
transmitted on the uplink SCH using a specific modulation scheme in a cell within a
measurement period.
Measurement Points
Based on the modulation scheme, the corresponding counter is incremented by 1 each time
the gNodeB receives a TB initially transmitted on the uplink SCH. The internal timer of the
gNodeB has a deviation of one period, and therefore the measurement result of the counter
has a deviation.

Formula
None
Unit
None
Related Features
N.UL.SCH.HalfPiBPSK.TB Multi-mode: None

GSM: None
UMTS: None
LTE: None
NR: FBFD-010008 Basic Modulation Schemes
FBFD-010011 Scheduling
N.UL.SCH.QPSK.TB Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.UL.SCH.16QAM.TB Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.UL.SCH.64QAM.TB Multi-mode: None

GSM: None
UMTS: None
LTE: None

1.2.5.2 Number of TBs Retransmitted on the Uplink SCH
Counters
1911816587 N.UL.SCH.Half Number of TBs BTS3900, N

PiBPSK.TB.Ret retransmitted on BTS3900 5G,
rans the uplink SCH BTS5900,
using the Pi/2
BPSK BTS5900 5G
modulation
scheme
1911816588 N.UL.SCH.QP Number of TBs BTS3900, N

SK.TB.Retrans retransmitted on BTS3900 5G,
the uplink SCH BTS5900,
using the QPSK
modulation BTS5900 5G
scheme

16QAM.TB.Ret retransmitted on BTS3900 5G,
using the
16QAM BTS5900 5G
modulation
scheme

using the
64QAM BTS5900 5G
modulation
scheme

256QAM.TB.R retransmitted on BTS3900 5G,
etrans the uplink SCH BTS5900,
using the
256QAM BTS5900 5G
modulation
scheme
Description
The gNodeB determines an MCS index for retransmission by a UE based on the uplink
channel quality. Each MCS index maps to a modulation scheme, such as Pi/2 BPSK, QPSK,
16QAM, 64QAM, and 256QAM. Each counter measures the number of TBs retransmitted on
the uplink SCH using a specific modulation scheme in a cell within a measurement period.

Measurement Points
the gNodeB receives a TB retransmitted on the uplink SCH. The internal timer of the gNodeB
has a deviation of one period, and therefore the measurement result of the counter has a
deviation.
Formula
None
Unit
None
Related Features
N.UL.SCH.HalfPiBPSK.TB Multi-mode: None

.Retrans GSM: None
UMTS: None
LTE: None
N.UL.SCH.QPSK.TB.Retra Multi-mode: None

ns GSM: None
UMTS: None
LTE: None
N.UL.SCH. Multi-mode: None

16QAM.TB.Retrans GSM: None
UMTS: None
LTE: None

UMTS: None
LTE: None

1.2.5.3 Number of Uplink TBs That Fail to Be Correctly Received After the
Maximum Number of Retransmissions Is Reached
Counters
1911816591 N.UL.SCH.Half Number of BTS3900, N

PiBPSK.ErrTB. uplink TBs that BTS3900 5G,
Rbler fail to be BTS5900,
correctly
received after BTS5900 5G
the maximum
number of
retransmissions
for the Pi/2
BPSK
modulation
scheme is
reached
1911816592 N.UL.SCH.QP Number of BTS3900, N

SK.ErrTB.Rble uplink TBs that BTS3900 5G,
r fail to be BTS5900,
correctly
the maximum
number of
retransmissions
for the QPSK
modulation
scheme is
reached
1911816593 N.UL.SCH. Number of BTS3900, N

16QAM.ErrTB. uplink TBs that BTS3900 5G,
correctly
the maximum
number of
retransmissions
for the 16QAM
modulation
scheme is
reached



64QAM.ErrTB. uplink TBs that BTS3900 5G,
correctly
the maximum
number of
retransmissions
for the 64QAM
modulation
scheme is
reached

256QAM.ErrT uplink TBs that BTS3900 5G,
B.Rbler fail to be BTS5900,
retransmitted
after the BTS5900 5G
maximum
number of
retransmissions
for the
256QAM
modulation
scheme is
reached
Description
Each counter measures the number of uplink TBs that fail to be correctly received after the
maximum number of retransmissions for a specific modulation scheme is reached.
Measurement Points
the gNodeB determines that a TB fails to be correctly received after the maximum number of
retransmissions is reached on the uplink. The internal timer of the gNodeB has a deviation of
one period, and therefore the measurement result of the counter has a deviation.
Formula
None
Unit
None

Related Features
N.UL.SCH.HalfPiBPSK.Err Multi-mode: None

TB.Rbler GSM: None
UMTS: None
LTE: None
N.UL.SCH.QPSK.ErrTB.Rb Multi-mode: None

ler GSM: None
UMTS: None
LTE: None

16QAM.ErrTB.Rbler GSM: None
UMTS: None
LTE: None

UMTS: None
LTE: None

1.2.5.4 Number of TBs Initially Transmitted on the Downlink SCH
Counters
1911816680 N.DL.SCH.QP Number of TBs BTS3900, N

SK.TB initially BTS3900 5G,
the downlink
SCH using the BTS5900 5G
QPSK
modulation
scheme
1911816681 N.DL.SCH. Number of TBs BTS3900, N

the downlink
16QAM
modulation
scheme

the downlink
64QAM
modulation
scheme

the downlink
256QAM
modulation
scheme
Description
The gNodeB determines an MCS index for initial transmission by a UE based on the
downlink channel quality. Each MCS index maps to a modulation scheme, such as QPSK,
16QAM, 64QAM, and 256QAM. Each counter measures the number of TBs initially
transmitted on the downlink SCH using a specific modulation scheme in a cell within a
measurement period.

Measurement Points
the gNodeB initially transmits a TB on the downlink SCH.The internal timer of the gNodeB
has a deviation of one period, and therefore the measurement result of the counter has a
deviation.
Formula
None
Unit
None
Related Features
N.DL.SCH.QPSK.TB Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.DL.SCH.16QAM.TB Multi-mode: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

1.2.5.5 Number of TBs Retransmitted on the Downlink SCH
Counters

SK.TB.Retrans retransmitted on BTS3900 5G,
the downlink BTS5900,
SCH using the
QPSK BTS5900 5G
modulation
scheme

rans the downlink BTS5900,
SCH using the
16QAM BTS5900 5G
modulation
scheme

rans the downlink BTS5900,
SCH using the
64QAM BTS5900 5G
modulation
scheme

256QAM.TB.R retransmitted on BTS3900 5G,
etrans the downlink BTS5900,
SCH using the
256QAM BTS5900 5G
modulation
scheme
Description
The gNodeB determines an MCS index for retransmission by a UE based on the downlink
channel quality. Each MCS index maps to a modulation scheme, such as QPSK, 16QAM,
64QAM, and 256QAM. Each counter measures the number of TBs retransmitted on the
downlink SCH using a specific modulation scheme in a cell within a measurement period.
Measurement Points
the gNodeB retransmits a TB on the downlink SCH.The internal timer of the gNodeB has a
deviation of one period, and therefore the measurement result of the counter has a deviation.

Formula
None
Unit
None
Related Features
N.DL.SCH.QPSK.TB.Retra Multi-mode: None

ns GSM: None
UMTS: None
LTE: None
N.DL.SCH. Multi-mode: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

1.2.5.6 Number of Downlink TBs That Fail to Be Correctly Received After the
Maximum Number of Retransmissions Is Reached
Counters
1911816688 N.DL.SCH.QP Number of BTS3900, N

SK.ErrTB.Rble downlink TBs BTS3900 5G,
r that fail to be BTS5900,
correctly
the maximum
number of
retransmissions
for the QPSK
modulation
scheme is
reached
1911816689 N.DL.SCH. Number of BTS3900, N

16QAM.ErrTB. downlink TBs BTS3900 5G,
Rbler that fail to be BTS5900,
correctly
the maximum
number of
retransmissions
for the 16QAM
modulation
scheme is
reached

64QAM.ErrTB. downlink TBs BTS3900 5G,
Rbler that fail to be BTS5900,
correctly
the maximum
number of
retransmissions
for the 64QAM
modulation
scheme is
reached



256QAM.ErrT downlink TBs BTS3900 5G,
B.Rbler that fail to be BTS5900,
correctly
the maximum
number of
retransmissions
for the
256QAM
modulation
scheme is
reached
Description
Each counter measures the number of downlink TBs that fail to be correctly received after the
maximum number of retransmissions for a specific modulation scheme is reached.
Measurement Points
the gNodeB receives a TB transmission failure indication after the maximum number of
retransmissions is reached on the downlink.The internal timer of the gNodeB has a deviation
of one period, and therefore the measurement result of the counter has a deviation.
Formula
None
Unit
None
Related Features
N.DL.SCH.QPSK.ErrTB.Rb Multi-mode: None

ler GSM: None
UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None
1.2.5.7 Number of TBs Failing To Be Initially Transmitted on the Downlink SCH
Counters

SK.ErrTB.Ibler failing to be BTS3900 5G,
initially BTS5900,
transmitted on
SCH in the
QPSK
modulation
scheme



16QAM.ErrTB. failing to be BTS3900 5G,
Ibler initially BTS5900,
transmitted on
SCH in the
16QAM
modulation
scheme

64QAM.ErrTB. failing to be BTS3900 5G,
Ibler initially BTS5900,
transmitted on
SCH in the
64QAM
modulation
scheme

256QAM.ErrT failing to be BTS3900 5G,
B.Ibler initially BTS5900,
transmitted on
SCH in the
256QAM
modulation
scheme
Description
The gNodeB determines an MCS index for initial transmission by a UE based on the
downlink channel quality. Each MCS index maps to a modulation scheme, such as QPSK,
16QAM, 64QAM, and 256QAM. Each counter measures the number of TBs failing to be
initially transmitted on the downlink SCH using a specific modulation scheme in a cell within
a measurement period.
Measurement Points
the gNodeB receives a NACK message for an initially transmitted TB on the downlink SCH.
The internal timer of the gNodeB has a deviation of one period, and therefore the
measurement result of this counter has a deviation.
Formula
None

Unit
None
Related Features
N.DL.SCH.QPSK.ErrTB.Ibl Multi-mode: None

er GSM: None
UMTS: None
LTE: None

16QAM.ErrTB.Ibler GSM: None
UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None
1.2.6 MCS Measurement (ChMeas.MCS.DuCell)

Overview
Modulation and coding scheme (MCS) is the basic output of MAC scheduling. The MCS
Measurement(ChMeas.MCS.DuCell) function subset measures the number of times each
MCS index is scheduled on the uplink or downlink in an NR DU cell. It is used to analyze
overall uplink and downlink scheduling.

Counters
1911816550 N.ChMeas.PUSCH. Number of times BTS5900 5G:

MCS.0 MCS index 0 is V100R013C10
scheduled on the BTS5900:
PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00



PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00



PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00



PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00



PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00

PUSCH V100R013C10
BTS3900:
V100R015C00
1911816647 N.ChMeas.PDSCH. Number of times BTS5900 5G:

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00



PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00



PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00



PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00



PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00



PDSCH V100R013C10
BTS3900:
V100R015C00

PDSCH V100R013C10
BTS3900:
V100R015C00

256QAM.MCS.0 MCS index 0 is V100R015C00
selected for PUSCH BTS5900:
scheduling for UEs V100R015C00
configured to use BTS3900:
256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00



256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00



256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00



256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00



256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00

256QAM V100R015C00
None

1.2.6.1 Number of Times a Specific MCS Index Is Scheduled on the PUSCH
Counters
1911816550 N.ChMeas.PUS Number of BTS3900, N

CH.MCS.0 times MCS BTS3900 5G,
index 0 is BTS5900,
scheduled on
the PUSCH BTS5900 5G

index 1 is BTS5900,
scheduled on

index 2 is BTS5900,
scheduled on

index 3 is BTS5900,
scheduled on

index 4 is BTS5900,
scheduled on

index 5 is BTS5900,
scheduled on

index 6 is BTS5900,
scheduled on

index 7 is BTS5900,
scheduled on



index 8 is BTS5900,
scheduled on

index 9 is BTS5900,
scheduled on

index 10 is BTS5900,
scheduled on

scheduled on

scheduled on

scheduled on

scheduled on

scheduled on



scheduled on

scheduled on

scheduled on

scheduled on

scheduled on

scheduled on

scheduled on

scheduled on



scheduled on

scheduled on

scheduled on

scheduled on

scheduled on

scheduled on

scheduled on

scheduled on

Description
Each counter measures the number of times that a specific MCS index is scheduled on the
uplink in a cell. The MCS index ranges from 0 to 31. These counters are used to analyze
uplink scheduling conditions.
Measurement Points
The corresponding counter is incremented by 1 each time the gNodeB schedules a specific
MCS index for a UE on the uplink within a TTI. The internal timer of the gNodeB has a
Formula
None
Unit
None
Related Features
N.ChMeas.PUSCH.MCS.0 Multi-mode: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None


GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None


GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None


GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None


GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

1.2.6.2 Number of Times a Specific MCS Index Is Scheduled on the PDSCH
Counters
1911816647 N.ChMeas.PDS Number of BTS3900, N

index 0 is BTS5900,
scheduled on
the PDSCH BTS5900 5G

index 1 is BTS5900,
scheduled on

index 2 is BTS5900,
scheduled on

index 3 is BTS5900,
scheduled on

index 4 is BTS5900,
scheduled on

index 5 is BTS5900,
scheduled on

index 6 is BTS5900,
scheduled on

index 7 is BTS5900,
scheduled on



index 8 is BTS5900,
scheduled on

index 9 is BTS5900,
scheduled on

scheduled on

scheduled on

scheduled on

scheduled on

scheduled on

scheduled on



scheduled on

scheduled on

scheduled on

scheduled on

scheduled on

scheduled on

scheduled on

scheduled on



scheduled on

scheduled on

scheduled on

scheduled on

scheduled on

scheduled on

scheduled on

scheduled on
Description
Each counter measures the number of times that a specific MCS index is scheduled on the
downlink in a cell. The MCS index ranges from 0 to 31. These counters are used to analyze

downlink scheduling conditions. In dual-codeword transmission, each codeword is configured

with an MCS. Therefore, the MCS for each codeword is counted separately.
Measurement Points
The corresponding counter is incremented by 1 each time the gNodeB schedules a specific
MCS index for a UE on the downlink within a TTI.The internal timer of the gNodeB has a
Formula
None
Unit
None
Related Features
N.ChMeas.PDSCH.MCS.0 Multi-mode: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None


GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None


GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None


GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None


GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

1.2.6.3 Number of Times an MCS Index Is Selected for PUSCH Scheduling for
UEs Configured to Use 256QAM
Counters

CH. times MCS BTS3900 5G,
256QAM.MCS. index 0 is BTS5900,
0 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

1 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

2 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

3 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

4 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM



5 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

6 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

7 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

8 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

9 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM



10 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

11 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

12 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

13 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

14 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM



15 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

16 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

17 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

18 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

19 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM



20 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

21 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

22 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

23 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

24 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM



25 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

26 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

27 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

28 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

29 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM



30 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM

31 selected for
PUSCH BTS5900 5G
scheduling for
UEs configured
to use 256QAM
Description
Number of Times an MCS Index Is Selected for PUSCH Scheduling for UEs Configured to
Use 256QAM
Measurement Points
The corresponding counter is incremented by 1 each time the gNodeB selects a specific MCS
index for a UE configured to use 256QAM (specifically, use the MCS index table
corresponding to 256QAM) on the uplink within a TTI.
Formula
None
Unit
None
Related Features
None
1.2.7 MIMO Channel Measurement (MIMO.DuCell)
Overview
The MIMO.DuCell function subset measures the numbers of pairing RBs, pairing layers, and
transmission layers in MIMO.

Counters
1911816819 N.ChMeas.MIMO. Total number of BTS5900 5G:

DL.Pair.PRB PRBs that are paired V100R015C00
for downlink MIMO BTS5900:
V100R015C00
BTS3900:
V100R015C00

DL.Pair.Layer layers that are paired V100R015C00
for downlink MIMO BTS5900:
V100R015C00
BTS3900:
V100R015C00

DL.Transmission.L transmission layers V100R015C00
ayer for downlink MIMO BTS5900:
V100R015C00
BTS3900:
V100R015C00
1911816822 N.ChMeas.MIMO. Maximum number BTS5900 5G:

DL.Transmission.L of transmission V100R015C00
ayer.Max layers for downlink BTS5900:
MIMO V100R015C00
BTS3900:
V100R015C00

UL.Pair.PRB PRBs That Are V100R015C00
Paired for uplink BTS5900:
MIMO V100R015C00
BTS3900:
V100R015C00

UL.Pair.Layer layers that are paired V100R015C00
for uplink MIMO BTS5900:
V100R015C00
BTS3900:
V100R015C00



UL.Trans.Layer transmission layers V100R015C00
for uplink MIMO BTS5900:
V100R015C00
BTS3900:
V100R015C00
1911816826 N.ChMeas.MIMO. Maximum number BTS5900 5G:

UL.Trans.Layer.M of transmission V100R015C00
ax layers for uplink BTS5900:
MIMO V100R015C00
BTS3900:
V100R015C00
None
1.2.7.1 Number of PRBs Paired for Downlink MIMO in a Cell
Counters
1911816819 N.ChMeas.MI Total number of BTS3900, N

MO.DL.Pair.PR PRBs that are BTS3900 5G,
B paired for BTS5900,
downlink
MIMO BTS5900 5G
Description
This counter measures the total number of PRBs that are paired for downlink MIMO. It is
used to analyze the pairing status of downlink PRBs.
Measurement Points
The number of PRBs that are paired for downlink MIMO in each timeslot for downlink
scheduling is accumulated. At the end of a measurement period, the accumulated value is
used as the value of this counter.
Formula
None

Unit
None
Related Features
N.ChMeas.MIMO.DL.Pair. Multi-mode: None

PRB GSM: None
UMTS: None
LTE: None
NR: FOFD-010010 MU-MIMO Basic Pairing
1.2.7.2 Number of Layers Paired for Downlink MIMO in a Cell
Counters

MO.DL.Pair.La layers that are BTS3900 5G,
yer paired for BTS5900,
downlink
MIMO BTS5900 5G
Description
This counter measures the total number of layers that are paired for downlink MIMO. It is
used to analyze the pairing status of layers on downlink paired PRBs.
Measurement Points
The number of layers paired on PRBs that are paired for downlink MIMO in each timeslot for
downlink scheduling is accumulated. At the end of a measurement period, the accumulated
value is used as the value of this counter.
Formula
None
Unit
None

Related Features
N.ChMeas.MIMO.DL.Pair. Multi-mode: None

Layer GSM: None
UMTS: None
LTE: None
1.2.7.3 Number of Transmission Layers for Downlink MIMO in a Cell
Counters

MO.DL.Transm transmission BTS3900 5G,
ission.Layer layers for BTS5900,
downlink
MIMO BTS5900 5G
Description
This counter measures the total number of downlink transmission layers for MIMO UEs,
including SU-MIMO and MU-MIMO UEs. It is used to analyze the multiplexing of PRBs
scheduled in the downlink.
Measurement Points
The total number of PRBs that are scheduled for downlink MIMO UEs in each downlink
timeslot is multiplied by the rank value. At the end of a measurement period, the multiplied
value for each downlink timeslot is accumulated, and the accumulated value is used as the
value of this counter.
Formula
None
Unit
None

Related Features
N.ChMeas.MIMO.DL.Trans Multi-mode: None

mission.Layer GSM: None
UMTS: None
LTE: None
1.2.7.4 Maximum Number of Transmission Layers for Downlink MIMO in a Cell
Counters
1911816822 N.ChMeas.MI Maximum BTS3900, N

MO.DL.Transm number of BTS3900 5G,
ission.Layer.Ma transmission BTS5900,
x layers for
downlink BTS5900 5G
MIMO
Description
This counter provides the maximum number of transmission layers in the downlink. It is used
to analyze the downlink transmission capability.
Measurement Points
The maximum number of transmission layers on each PRB in each timeslot is sampled per
second. At the end of a measurement period, the maximum of these sampling results is used
as the value of this counter.
Formula
None
Unit
None

Related Features
N.ChMeas.MIMO.DL.Trans Multi-mode: None

mission.Layer.Max GSM: None
UMTS: None
LTE: None
1.2.7.5 Number of PRBs Paired for Uplink MIMO in a Cell
Counters

MO.UL.Pair.PR PRBs That Are BTS3900 5G,
B Paired for BTS5900,
uplink MIMO
BTS5900 5G
Description
This counter measures the total number of PRBs that are paired for uplink MIMO. It is used
to observe the effectiveness and pairing status of uplink MU-MIMO.
Measurement Points
The total number of PRBs that are paired for uplink MIMO in each timeslot for uplink
Formula
None
Unit
None

Related Features
N.ChMeas.MIMO.UL.Pair. Multi-mode: None

PRB GSM: None
UMTS: None
LTE: None
1.2.7.6 Number of Layers Paired for Uplink MIMO in a Cell
Counters

MO.UL.Pair.La layers that are BTS3900 5G,
yer paired for BTS5900,
uplink MIMO
BTS5900 5G
Description
This counter measures the total number of layers that are paired for uplink MIMO. This
counter can be used to analyze the average number of paired layers, together with the
N.ChMeas.MIMO.UL.Pair.PRB counter.
Measurement Points
The total number of layers that are paired for uplink MIMO in each timeslot for uplink
Formula
None
Unit
None

Related Features
N.ChMeas.MIMO.UL.Pair. Multi-mode: None

Layer GSM: None
UMTS: None
LTE: None
1.2.7.7 Number of Transmission Layers for Uplink MIMO in a Cell
Counters

MO.UL.Trans. transmission BTS3900 5G,
Layer layers for BTS5900,
uplink MIMO
BTS5900 5G
Description
This counter measures the total number of transmission layers for uplink MIMO. It is used to
evaluate the space division capability of uplink MIMO.
Measurement Points
The number of PRBs for each UE in each timeslot for uplink scheduling is multiplied by the
number of scheduling layers. At the end of a measurement period, the multiplied value for
each timeslot is accumulated, and the accumulated value is used as the value of this counter.
Formula
None
Unit
None

Related Features
N.ChMeas.MIMO.UL.Trans Multi-mode: None

.Layer GSM: None
UMTS: None
LTE: None
1.2.7.8 Maximum Number of Transmission Layers for Uplink MIMO in a Cell
Counters
1911816826 N.ChMeas.MI Maximum BTS3900, N

MO.UL.Trans. number of BTS3900 5G,
Layer.Max transmission BTS5900,
layers for
uplink MIMO BTS5900 5G
Description
This counter measures the maximum number of transmission layers for uplink MIMO. It is
used to evaluate the maximum specifications of uplink MIMO.
Measurement Points
The maximum number of transmission layers on each PRB in each timeslot is sampled per
second. At the end of a measurement period, the maximum of these sampling results is used
as the value of this counter.
Formula
None
Unit
None

Related Features
N.ChMeas.MIMO.UL.Trans Multi-mode: None

.Layer.Max GSM: None
UMTS: None
LTE: None
1.2.8 NR DU Cell Scheduled User Quantity Measurement

(ScheUser.DuCell)
Overview
The NR DU Cell Scheduled User Quantity Measurement(ScheUser.DuCell) function subset
measures the number of UEs scheduled in different uplink and downlink scenarios in an NR
DU cell.
Counters

Active.UL.Max of active UEs in the V100R015C00
uplink in a cell BTS5900:
V100R015C00
BTS3900:
V100R015C00

Active.UL.Avg active UEs in the V100R015C00
uplink in a cell BTS5900:
V100R015C00
BTS3900:
V100R015C00

Active.DL.Max of active UEs in the V100R015C00
downlink in a cell BTS5900:
V100R015C00
BTS3900:
V100R015C00



Active.DL.Avg active UEs in the V100R015C00
downlink in a cell BTS5900:
V100R015C00
BTS3900:
V100R015C00

Active.Max of active UEs in a V100R015C00
cell BTS5900:
V100R015C00
BTS3900:
V100R015C00

Active.Avg active UEs in a cell V100R015C00
BTS5900:
V100R015C00
BTS3900:
V100R015C00
1911816806 N.User.Schedule.Dl Total number of BTS5900 5G:

.Sum scheduled UEs in V100R015C00
the downlink in a BTS5900:
cell V100R015C00
BTS3900:
V100R015C00
1911816807 N.User.Schedule.Ul Total number of BTS5900 5G:

.Sum scheduled UEs in V100R015C00
the uplink in a cell BTS5900:
V100R015C00
BTS3900:
V100R015C00

Active.B2H.Avg active B2H UEs in a V100R015C00
cell BTS5900:
V100R015C00
BTS3900:
V100R015C00
1911816900 N.User.CA.PCell.D Average number of BTS5900 5G:

L.SCellAct.Avg downlink CA UEs V100R015C00
cell as their PCell V100R015C00
and have activated BTS3900:
Scells V100R015C00


1911816901 N.User.CA.PCell.U Average number of BTS5900 5G:

L.SCellAct.Avg uplink CA UEs that V100R015C00
their PCell and have V100R015C00
activated Scells BTS3900:
V100R015C00
1911816902 N.User.CA.SCell.D Average number of BTS5900 5G:

L.Act.Avg downlink CA UEs V100R015C00
cell as their SCell V100R015C00
and have the SCell BTS3900:
activated V100R015C00
1911816903 N.User.CA.SCell.U Average number of BTS5900 5G:

L.Act.Avg uplink CA UEs that V100R015C00
their SCell and have V100R015C00
the SCell activated BTS3900:
V100R015C00
None
1.2.8.1 Number of Active UEs in the Uplink in an NR DU Cell
Counters

nn.Active.UL. number of BTS3900 5G,
Max active UEs in BTS5900,
the uplink in a
cell BTS5900 5G

nn.Active.UL.A number of BTS3900 5G,
vg active UEs in BTS5900,
the uplink in a
cell BTS5900 5G

Description
These counters measure the number of UEs that have data in the uplink buffer in an NR DU
cell.
Measurement Points
These counters are measured based on the UE status at the sampling time. The number of
RRC_CONNECTED UEs that have data in the uplink buffer in a cell is sampled every 100
ms. At the end of a measurement period, the average and maximum of these sampling results
are used as the values of the corresponding counters.
For a CA UE, the counters are measured only in the PCell of the DU cell. For a UE for which
UL and DL Decoupling takes effect, the counters are measured only in the NUL DU cell.
Formula
None
Unit
None
Related Features
None
1.2.8.2 Number of Active UEs in the Downlink in an NR DU Cell
Counters

nn.Active.DL. number of BTS3900 5G,
Max active UEs in BTS5900,
the downlink in
a cell BTS5900 5G

nn.Active.DL.A number of BTS3900 5G,
vg active UEs in BTS5900,
the downlink in
a cell BTS5900 5G
Description
These counters measure the number of UEs that have data in the downlink buffer in an NR
DU cell.

Measurement Points
RRC_CONNECTED UEs that have data in the downlink buffer in a cell is sampled every 100
ms. 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
None
1.2.8.3 Number of Active UEs in an NR DU Cell
Counters

nn.Active.Max number of BTS3900 5G,
active UEs in a BTS5900,
cell
BTS5900 5G

nn.Active.Avg number of BTS3900 5G,
active UEs in a BTS5900,
cell
BTS5900 5G
Description
These counters measure the number of UEs that have data in the buffer in an NR DU cell.
Measurement Points
RRC_CONNECTED UEs that have data in either the downlink or uplink buffer in a cell is
sampled every 100 ms. 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
None
1.2.8.4 Total Number of Scheduled UEs in the Downlink in an NR DU Cell
Counters
1911816806 N.User.Schedul Total number of BTS3900, N

e.Dl.Sum scheduled UEs BTS3900 5G,
in the downlink BTS5900,
in a cell
BTS5900 5G
Description
This counter measures the total number of scheduled UEs in the downlink in an NR DU cell.
Measurement Points
This counter is measured based on the number of scheduled UEs in the sampling period. The
total number of scheduled UEs in the downlink is accumulated per timeslot in a cell. A
scheduled UE that is successfully allocated air interface resources (CCE or PRB) in the
downlink in a timeslot. The accumulated value of all timeslots in a measurement period is
used as the value of this counter. The internal timer of the gNodeB has a deviation of one
period, and therefore the measurement result of this counter has a deviation.
Formula
None
Unit
None

Related Features
N.User.Schedule.Dl.Sum Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.2.8.5 Total Number of Scheduled UEs in the Uplink in an NR DU Cell
Counters
1911816807 N.User.Schedul Total number of BTS3900, N

e.Ul.Sum scheduled UEs BTS3900 5G,
in the uplink in BTS5900,
a cell
BTS5900 5G
Description
This counter measures the total number of scheduled UEs in the uplink in an NR DU cell.
Measurement Points
This counter is measured based on the number of scheduled UEs in the sampling period. The
total number of scheduled UEs in the uplink is accumulated per timeslot in a cell. A scheduled
UE that is successfully allocated air interface resources (CCE or PRB) in the uplink in a
timeslot. The accumulated value of all timeslots in a measurement period is used as the value
of this counter. The internal timer of the gNodeB has a deviation of one period, and therefore
the measurement result of this counter has a deviation.
Formula
None
Unit
None

Related Features
N.User.Schedule.Ul.Sum Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.2.8.6 Number of Active B2H UEs in an NR DU Cell
Counters

nn.Active.B2H. number of BTS3900 5G,
Avg active B2H UEs BTS5900,
in a cell
BTS5900 5G
Description
This counter measures the number of B2H UEs that have data in the buffer in an NR DU cell.
Measurement Points
The counter is measured based on the UE status at the sampling time. The number of UEs that
are identified as B2H UEs, are in RRC_CONNECTED mode, and have data (in the uplink or
downlink buffer) in a cell is sampled per millisecond. At the end of a measurement period, the
average of these sampling results is taken as the value of this counter.
Formula
None
Unit
None
Related Features
None

1.2.8.7 Number of Uplink and Downlink CA UEs That Use the Local Cell as
Their PCell and Have Activated Scells
Counters

ll.DL.SCellAct. number of BTS5900,
Avg downlink CA BTS5900 5G
UEs that use the
local cell as
their PCell and
have activated
Scells

ll.UL.SCellAct. number of BTS5900,
Avg uplink CA UEs BTS5900 5G
that use the
local cell as
their PCell and
have activated
Scells
Description
These counters measure the average number of uplink and downlink CA UEs that use the
local cell as their PCell and have activated SCells.
Measurement Points
The number of uplink and downlink CA UEs that use the local cell as their PCell and have
activated SCells is sampled per second. At the end of a measurement period, the average of
these sampling results is used as the value of the corresponding counter.
Formula
None
Unit
None

Related Features
N.User.CA.PCell.DL.SCell Multi-mode: None

Act.Avg GSM: None
UMTS: None
LTE: None
N.User.CA.PCell.UL.SCell Multi-mode: None

Act.Avg GSM: None
UMTS: None
LTE: None
1.2.8.8 Number of Uplink and Downlink CA UEs That Use the Local Cell as
Their SCell and Have the SCell Activated
Counters

ll.DL.Act.Avg number of BTS5900,
downlink CA BTS5900 5G
UEs that use the
local cell as
their SCell and
have the SCell
activated

ll.UL.Act.Avg number of BTS5900,
uplink CA UEs BTS5900 5G
that use the
local cell as
their SCell and
have the SCell
activated
Description
These counters measure the average number of uplink and downlink CA UEs that use the
local cell as their SCell and have the SCell activated.

Measurement Points
The number of uplink and downlink CA UEs that use the local cell as their SCell and have the
SCell activated is sampled per second. At the end of a measurement period, the average of
these sampling results is used as the value of the corresponding counter.
Formula
None
Unit
None
Related Features
N.User.CA.SCell.DL.Act.A Multi-mode: None

vg GSM: None
UMTS: None
LTE: None
N.User.CA.SCell.UL.Act.A Multi-mode: None

vg GSM: None
UMTS: None
LTE: None
1.2.9 NR DU Cell Reserved Counter Measurement

(Reserve.DuCell)
Overview
Reserved counters are temporarily used in patch versions and will be replaced with new
counters in later versions. For details about the reserved counters in use, see Used Reserved
Counter List of the corresponding version.

Counters
1911816442 N.DuCell.Reserve.1 Reserved counter 1 BTS5900 5G:

for the local cell V100R013C10
BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00



BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00
1911816451 N.DuCell.Reserve. Reserved counter 10 BTS5900 5G:

10 for the local cell V100R013C10
BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00



BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00



BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00



BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00



BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00



BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00



BTS5900:
V100R013C10
BTS3900:
V100R015C00

BTS5900:
V100R013C10
BTS3900:
V100R015C00
None
1.2.9.1 Reserved Counter 1 for the Local Cell
Counters
1911816442 N.DuCell.Reser Reserved BTS3900, N

ve.1 counter 1 for BTS3900 5G,
the local cell BTS5900,
BTS5900 5G
Description
Reserved counter 1 for the local cell
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G

Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G

Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G

Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G

Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G

Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G

Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G

Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G

Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G

Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G

Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G

Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G

Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G

Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G

Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G

Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G

Description
Measurement Points
Formula
None
Unit
None
Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None

Related Features
None
Counters

BTS5900 5G
Description
Measurement Points
Formula
None
Unit
None
Related Features
None
1.2.10 Measurement per MCS Index in the MCS Index Table for
PDSCH with 256QAM (ChMeas.PDSCH.256QAM.MCS.DuCell)
Overview
Modulation and coding scheme (MCS) is the basic output of MAC scheduling. The
ChMeas.PDSCH.256QAM.MCS.DuCell function subset measures the total number of RBs
used by different MCS indexes in the downlink. The result indicates the overall downlink
quality for scheduling in the cell. For details, see "MCS index table 2 for PDSCH" in 3GPP
TS 38.214.

Counters
1911817184 N.ChMeas.RB.PDS Number of RBs BTS3900:

CH. allocated for V100R015C10
256QAM.RANK1. PDSCH with rank 1 BTS5900:
MCS.0 and MCS index 0 in V100R015C10
the MCS index table BTS5900 5G:
with 256QAM V100R015C10












MCS.10 and MCS index 10 V100R015C10
in the MCS index BTS5900 5G:
table with 256QAM V100R015C10



































































































































None
1.2.10.1 Number of RBs Allocated for PDSCH with Different MCS Indexes in the
MCS Index Table with 256QAM
Counters
1911817184 N.ChMeas.RB. Number of RBs BTS3900, N

PDSCH. allocated for BTS3900 5G,
256QAM.RAN PDSCH with BTS5900,
K1.MCS.0 rank 1 and
MCS index 0 in BTS5900 5G
the MCS index
table with
256QAM

K1.MCS.1 rank 1 and
the MCS index
table with
256QAM

K1.MCS.2 rank 1 and
the MCS index
table with
256QAM



K1.MCS.3 rank 1 and
the MCS index
table with
256QAM

K1.MCS.4 rank 1 and
the MCS index
table with
256QAM

K1.MCS.5 rank 1 and
the MCS index
table with
256QAM

K1.MCS.6 rank 1 and
the MCS index
table with
256QAM

K1.MCS.7 rank 1 and
the MCS index
table with
256QAM



K1.MCS.8 rank 1 and
the MCS index
table with
256QAM

K1.MCS.9 rank 1 and
the MCS index
table with
256QAM

K1.MCS.10 rank 1 and
MCS index 10 BTS5900 5G
in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



K2.MCS.0 rank 2 and
the MCS index
table with
256QAM

K2.MCS.1 rank 2 and
the MCS index
table with
256QAM

K2.MCS.2 rank 2 and
the MCS index
table with
256QAM

K2.MCS.3 rank 2 and
the MCS index
table with
256QAM

K2.MCS.4 rank 2 and
the MCS index
table with
256QAM



K2.MCS.5 rank 2 and
the MCS index
table with
256QAM

K2.MCS.6 rank 2 and
the MCS index
table with
256QAM

K2.MCS.7 rank 2 and
the MCS index
table with
256QAM

K2.MCS.8 rank 2 and
the MCS index
table with
256QAM

K2.MCS.9 rank 2 and
the MCS index
table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

K3.MCS.0 rank 3 and
the MCS index
table with
256QAM

K3.MCS.1 rank 3 and
the MCS index
table with
256QAM



K3.MCS.2 rank 3 and
the MCS index
table with
256QAM

K3.MCS.3 rank 3 and
the MCS index
table with
256QAM

K3.MCS.4 rank 3 and
the MCS index
table with
256QAM

K3.MCS.5 rank 3 and
the MCS index
table with
256QAM

K3.MCS.6 rank 3 and
the MCS index
table with
256QAM



K3.MCS.7 rank 3 and
the MCS index
table with
256QAM

K3.MCS.8 rank 3 and
the MCS index
table with
256QAM

K3.MCS.9 rank 3 and
the MCS index
table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

K4.MCS.0 rank 4 and
the MCS index
table with
256QAM

K4.MCS.1 rank 4 and
the MCS index
table with
256QAM

K4.MCS.2 rank 4 and
the MCS index
table with
256QAM

K4.MCS.3 rank 4 and
the MCS index
table with
256QAM



K4.MCS.4 rank 4 and
the MCS index
table with
256QAM

K4.MCS.5 rank 4 and
the MCS index
table with
256QAM

K4.MCS.6 rank 4 and
the MCS index
table with
256QAM

K4.MCS.7 rank 4 and
the MCS index
table with
256QAM

K4.MCS.8 rank 4 and
the MCS index
table with
256QAM



K4.MCS.9 rank 4 and
the MCS index
table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM
Description
These counters measure the total number of RBs used in downlink scheduling of different
MCS indexes using different ranks with 256QAM. For details about the MCS index table
corresponding to 256QAM, see "MCS index table 2 for PDSCH" in 3GPP TS 38.214.
Measurement Points
In a measurement period, the gNodeB measures the number of RBs used in downlink
scheduling of different MCS indexes using different ranks with 256QAM.

Formula
None
Unit
None
Related Features
N.ChMeas.RB.PDSCH. Multi-mode: None

256QAM.RANK1.MCS.0 GSM: None
UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None
PDSCH with 64QAM (ChMeas.PDSCH.64QAM.MCS.DuCell)
Overview
ChMeas.PDSCH.64QAM.MCS.DuCell function subset measures the total number of RBs
used by different MCS indexes in the downlink. The result indicates the overall downlink
quality for scheduling in the cell. For details, see "MCS index table 1 for PDSCH" in 3GPP
TS 38.214.
Counters

64QAM.RANK1.M PDSCH with rank 1 BTS5900 5G:
CS.0 and MCS index 0 in V100R015C10
the MCS index table BTS3900:














CS.10 and MCS index 10 V100R015C10
in the MCS index BTS3900:







































































































































None
1.2.11.1 Number of RBs Allocated for PDSCH with Different MCS Indexes in the
Counters

64QAM.RANK PDSCH with BTS5900,
1.MCS.0 rank 1 and
the MCS index
table with
64QAM

1.MCS.1 rank 1 and
the MCS index
table with
64QAM

1.MCS.2 rank 1 and
the MCS index
table with
64QAM



1.MCS.3 rank 1 and
the MCS index
table with
64QAM

1.MCS.4 rank 1 and
the MCS index
table with
64QAM

1.MCS.5 rank 1 and
the MCS index
table with
64QAM

1.MCS.6 rank 1 and
the MCS index
table with
64QAM

1.MCS.7 rank 1 and
the MCS index
table with
64QAM



1.MCS.8 rank 1 and
the MCS index
table with
64QAM

1.MCS.9 rank 1 and
the MCS index
table with
64QAM

1.MCS.10 rank 1 and
in the MCS
index table with
64QAM

1.MCS.11 rank 1 and
in the MCS
index table with
64QAM

1.MCS.12 rank 1 and
in the MCS
index table with
64QAM



1.MCS.13 rank 1 and
in the MCS
index table with
64QAM

1.MCS.14 rank 1 and
in the MCS
index table with
64QAM

1.MCS.15 rank 1 and
in the MCS
index table with
64QAM

1.MCS.16 rank 1 and
in the MCS
index table with
64QAM

1.MCS.17 rank 1 and
in the MCS
index table with
64QAM



1.MCS.18 rank 1 and
in the MCS
index table with
64QAM

1.MCS.19 rank 1 and
in the MCS
index table with
64QAM

1.MCS.20 rank 1 and
in the MCS
index table with
64QAM

1.MCS.21 rank 1 and
in the MCS
index table with
64QAM

1.MCS.22 rank 1 and
in the MCS
index table with
64QAM



1.MCS.23 rank 1 and
in the MCS
index table with
64QAM

1.MCS.24 rank 1 and
in the MCS
index table with
64QAM

1.MCS.25 rank 1 and
in the MCS
index table with
64QAM

1.MCS.26 rank 1 and
in the MCS
index table with
64QAM

1.MCS.27 rank 1 and
in the MCS
index table with
64QAM



1.MCS.28 rank 1 and
in the MCS
index table with
64QAM

2.MCS.0 rank 2 and
the MCS index
table with
64QAM

2.MCS.1 rank 2 and
the MCS index
table with
64QAM

2.MCS.2 rank 2 and
the MCS index
table with
64QAM

2.MCS.3 rank 2 and
the MCS index
table with
64QAM



2.MCS.4 rank 2 and
the MCS index
table with
64QAM

2.MCS.5 rank 2 and
the MCS index
table with
64QAM

2.MCS.6 rank 2 and
the MCS index
table with
64QAM

2.MCS.7 rank 2 and
the MCS index
table with
64QAM

2.MCS.8 rank 2 and
the MCS index
table with
64QAM



2.MCS.9 rank 2 and
the MCS index
table with
64QAM

2.MCS.10 rank 2 and
in the MCS
index table with
64QAM

2.MCS.11 rank 2 and
in the MCS
index table with
64QAM

2.MCS.12 rank 2 and
in the MCS
index table with
64QAM

2.MCS.13 rank 2 and
in the MCS
index table with
64QAM



2.MCS.14 rank 2 and
in the MCS
index table with
64QAM

2.MCS.15 rank 2 and
in the MCS
index table with
64QAM

2.MCS.16 rank 2 and
in the MCS
index table with
64QAM

2.MCS.17 rank 2 and
in the MCS
index table with
64QAM

2.MCS.18 rank 2 and
in the MCS
index table with
64QAM



2.MCS.19 rank 2 and
in the MCS
index table with
64QAM

2.MCS.20 rank 2 and
in the MCS
index table with
64QAM

2.MCS.21 rank 2 and
in the MCS
index table with
64QAM

2.MCS.22 rank 2 and
in the MCS
index table with
64QAM

2.MCS.23 rank 2 and
in the MCS
index table with
64QAM



2.MCS.24 rank 2 and
in the MCS
index table with
64QAM

2.MCS.25 rank 2 and
in the MCS
index table with
64QAM

2.MCS.26 rank 2 and
in the MCS
index table with
64QAM

2.MCS.27 rank 2 and
in the MCS
index table with
64QAM

2.MCS.28 rank 2 and
in the MCS
index table with
64QAM



3.MCS.0 rank 3 and
the MCS index
table with
64QAM

3.MCS.1 rank 3 and
the MCS index
table with
64QAM

3.MCS.2 rank 3 and
the MCS index
table with
64QAM

3.MCS.3 rank 3 and
the MCS index
table with
64QAM

3.MCS.4 rank 3 and
the MCS index
table with
64QAM



3.MCS.5 rank 3 and
the MCS index
table with
64QAM

3.MCS.6 rank 3 and
the MCS index
table with
64QAM

3.MCS.7 rank 3 and
the MCS index
table with
64QAM

3.MCS.8 rank 3 and
the MCS index
table with
64QAM

3.MCS.9 rank 3 and
the MCS index
table with
64QAM



3.MCS.10 rank 3 and
in the MCS
index table with
64QAM

3.MCS.11 rank 3 and
in the MCS
index table with
64QAM

3.MCS.12 rank 3 and
in the MCS
index table with
64QAM

3.MCS.13 rank 3 and
in the MCS
index table with
64QAM

3.MCS.14 rank 3 and
in the MCS
index table with
64QAM



3.MCS.15 rank 3 and
in the MCS
index table with
64QAM

3.MCS.16 rank 3 and
in the MCS
index table with
64QAM

3.MCS.17 rank 3 and
in the MCS
index table with
64QAM

3.MCS.18 rank 3 and
in the MCS
index table with
64QAM

3.MCS.19 rank 3 and
in the MCS
index table with
64QAM



3.MCS.20 rank 3 and
in the MCS
index table with
64QAM

3.MCS.21 rank 3 and
in the MCS
index table with
64QAM

3.MCS.22 rank 3 and
in the MCS
index table with
64QAM

3.MCS.23 rank 3 and
in the MCS
index table with
64QAM

3.MCS.24 rank 3 and
in the MCS
index table with
64QAM



3.MCS.25 rank 3 and
in the MCS
index table with
64QAM

3.MCS.26 rank 3 and
in the MCS
index table with
64QAM

3.MCS.27 rank 3 and
in the MCS
index table with
64QAM

3.MCS.28 rank 3 and
in the MCS
index table with
64QAM

4.MCS.0 rank 4 and
the MCS index
table with
64QAM



4.MCS.1 rank 4 and
the MCS index
table with
64QAM

4.MCS.2 rank 4 and
the MCS index
table with
64QAM

4.MCS.3 rank 4 and
the MCS index
table with
64QAM

4.MCS.4 rank 4 and
the MCS index
table with
64QAM

4.MCS.5 rank 4 and
the MCS index
table with
64QAM



4.MCS.6 rank 4 and
the MCS index
table with
64QAM

4.MCS.7 rank 4 and
the MCS index
table with
64QAM

4.MCS.8 rank 4 and
the MCS index
table with
64QAM

4.MCS.9 rank 4 and
the MCS index
table with
64QAM

4.MCS.10 rank 4 and
in the MCS
index table with
64QAM



4.MCS.11 rank 4 and
in the MCS
index table with
64QAM

4.MCS.12 rank 4 and
in the MCS
index table with
64QAM

4.MCS.13 rank 4 and
in the MCS
index table with
64QAM

4.MCS.14 rank 4 and
in the MCS
index table with
64QAM

4.MCS.15 rank 4 and
in the MCS
index table with
64QAM



4.MCS.16 rank 4 and
in the MCS
index table with
64QAM

4.MCS.17 rank 4 and
in the MCS
index table with
64QAM

4.MCS.18 rank 4 and
in the MCS
index table with
64QAM

4.MCS.19 rank 4 and
in the MCS
index table with
64QAM

4.MCS.20 rank 4 and
in the MCS
index table with
64QAM



4.MCS.21 rank 4 and
in the MCS
index table with
64QAM

4.MCS.22 rank 4 and
in the MCS
index table with
64QAM

4.MCS.23 rank 4 and
in the MCS
index table with
64QAM

4.MCS.24 rank 4 and
in the MCS
index table with
64QAM

4.MCS.25 rank 4 and
in the MCS
index table with
64QAM



4.MCS.26 rank 4 and
in the MCS
index table with
64QAM

4.MCS.27 rank 4 and
in the MCS
index table with
64QAM

4.MCS.28 rank 4 and
in the MCS
index table with
64QAM
Description
These counters measure the total number of RBs used in downlink scheduling of different
MCS indexes using different ranks with 64QAM. For details about the MCS index table
corresponding to 64QAM, see "MCS index table 1 for PDSCH" in 3GPP TS 38.214.
Measurement Points
In a measurement period, the gNodeB measures the total number of RBs used in downlink
scheduling of different MCS indexes using different ranks with 64QAM in a cell.
Formula
None
Unit
None

Related Features

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None
1.2.12 PRB Measurement (PRB.DuCell)
Overview
Physical resource blocks (PRBs) are basic air interface resources. The PRB
Measurement(PRB.DuCell) function subset measures uplink and downlink PRB usages in an
NR DU cell.
Counters
1911816540 N.PRB.DL.Used.Av Average number of BTS5900 5G:

g used downlink PRBs V100R013C10
BTS5900:
V100R013C10
BTS3900:
V100R015C00


1911816541 N.PRB.UL.Used.Av Average number of BTS5900 5G:

g used uplink PRBs V100R013C10
BTS5900:
V100R013C10
BTS3900:
V100R015C00
1911816548 N.CCE.DLDCI.Use Average number of BTS5900 5G:

d.Avg PDCCH CCEs used V100R013C10
for downlink DCI BTS5900:
V100R013C10
BTS3900:
V100R015C00
1911816549 N.CCE.ULDCI.Use Average number of BTS5900 5G:

d.Avg PDCCH CCEs used V100R013C10
for uplink DCI BTS5900:
V100R013C10
BTS3900:
V100R015C00
1911816582 N.PRB.UL.Avail.A Average number of BTS5900 5G:

vg available uplink V100R013C10
PRBs BTS5900:
V100R013C10
BTS3900:
V100R015C00
1911816679 N.PRB.DL.Avail.A Average number of BTS5900 5G:

vg available downlink V100R013C10
PRBs BTS5900:
V100R013C10
BTS3900:
V100R015C00
1911816810 N.CCE.CommDCI. Average number of BTS5900 5G:

Used.Avg PDCCH CCEs used V100R015C00
for common DCI BTS5900:
V100R015C00
BTS3900:
V100R015C00
1911816812 N.CCE.SRSDCI.Us Average number of BTS5900 5G:

ed.Avg PDCCH CCEs used V100R015C00
for SRS DCI BTS5900:
V100R015C00
BTS3900:
V100R015C00


1911816814 N.CCE.CSIRSDCI. Average number of BTS5900 5G:

Used.Avg PDCCH CCEs used V100R015C00
for CSI-RS DCI BTS5900:
V100R015C00
BTS3900:
V100R015C00
1911816816 N.CCE.Used.Avg Average number of BTS5900 5G:

used PDCCH CCEs V100R015C00
BTS5900:
V100R015C00
BTS3900:
V100R015C00
1911816818 N.CCE.Avail.Avg Average number of BTS5900 5G:

available PDCCH V100R015C00
CCEs BTS5900:
V100R015C00
BTS3900:
V100R015C00
1911817110 N.CCE.DL.AggLvl Number of times of BTS3900:

1Num successful PDCCH V100R015C10
downlink DCI BTS5900:
allocations with V100R015C10
aggregation level 1 BTS5900 5G:
V100R015C10

V100R015C10

V100R015C10

V100R015C10



V100R015C10
1911817115 N.CCE.UL.AggLvl Number of times of BTS3900:

uplink DCI BTS5900:
V100R015C10

uplink DCI BTS5900:
V100R015C10

uplink DCI BTS5900:
V100R015C10

uplink DCI BTS5900:
V100R015C10

uplink DCI BTS5900:
V100R015C10
1911817480 N.CCE.MU.Layer Number of CCEs BTS3900:

GreaterThan1.Nu with more than one V100R015C10
m PDCCH spatial BTS5900:
multiplexing layer V100R015C10
BTS5900 5G:
V100R015C10

None
1.2.12.1 Number of Downlink PRBs Used in a Cell
Counters
1911816540 N.PRB.DL.Use Average BTS3900, N

d.Avg number of used BTS3900 5G,
downlink PRBs BTS5900,
BTS5900 5G
Description
This counter measures the average number of used downlink PRBs. This counter is used to
analyze the downlink PRB usage.
Measurement Points
The number of used downlink PRBs is sampled per slot. At the end of a measurement period,
the average of these samples is used as the counter value.
Formula
None
Unit
None
Related Features
N.PRB.DL.Used.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: None

1.2.12.2 Number of Used Uplink PRBs in a Cell
Counters
1911816541 N.PRB.UL.Use Average BTS3900, N

d.Avg number of used BTS3900 5G,
uplink PRBs BTS5900,
BTS5900 5G
Description
The counter measures the average number of used uplink PRBs. This counter is used to
analyze the uplink PRB usage.
Measurement Points
The number of used uplink PRBs is sampled per slot. At the end of a measurement period, the
average of these samples is used as the counter value.
Formula
None
Unit
None
Related Features
N.PRB.UL.Used.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: None

1.2.12.3 Number of PDCCH CCEs used in a Cell
Counters
1911816548 N.CCE.DLDCI. Average BTS3900, N

Used.Avg number of BTS3900 5G,
PDCCH CCEs BTS5900,
used for
downlink DCI BTS5900 5G
1911816549 N.CCE.ULDCI. Average BTS3900, N

Used.Avg number of BTS3900 5G,
PDCCH CCEs BTS5900,
used for uplink
DCI BTS5900 5G
1911816810 N.CCE.Comm Average BTS3900, N

DCI.Used.Avg number of BTS3900 5G,
PDCCH CCEs BTS5900,
used for
common DCI BTS5900 5G
1911816812 N.CCE.SRSDC Average BTS3900, N

I.Used.Avg number of BTS3900 5G,
PDCCH CCEs BTS5900,
used for SRS
DCI BTS5900 5G
1911816814 N.CCE.CSIRS Average BTS3900, N

DCI.Used.Avg number of BTS3900 5G,
PDCCH CCEs BTS5900,
used for CSI-
RS DCI BTS5900 5G
1911816816 N.CCE.Used.A Average BTS3900, N

vg number of used BTS3900 5G,
PDCCH CCEs BTS5900,
BTS5900 5G
1911816818 N.CCE.Avail.A Average BTS3900, N

vg number of BTS3900 5G,
available BTS5900,
PDCCH CCEs
BTS5900 5G
Description
These counters measure the average number of CCEs currently available in the NR DU cell
and the number of PDCCH CCEs used by each type of DCI. Currently, the number of
PDCCH CCEs used by five types of DCI is measured. The five types of DCI are as follows:

- Common DCI
DCI for common messages, such as system messages and RAR
- Downlink DCI
DCI for downlink data, or for downlink data plus reference signals
- Uplink DCI
DCI for uplink data, or for uplink data plus reference signals
- SRS DCI
DCI for SRS only
- CSI-RS DCI
DCI for CSI-RS only
Measurement Points
The numbers of PDCCH CCEs used for downlink DCI, uplink DCI, CSI-RS DCI, SRS DCI,
and common DCI and the number of available PDCCH CCEs are sampled per TTI. At the
end of a measurement period, the averages of these sampling results are used as the values of
the corresponding counters.
Formula
None
Unit
None
Related Features
N.CCE.DLDCI.Used.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.CCE.ULDCI.Used.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: None

N.CCE.CommDCI.Used.Av Multi-mode: None

g GSM: None
UMTS: None
LTE: None
N.CCE.SRSDCI.Used.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.CCE.CSIRSDCI.Used.Av Multi-mode: None

g GSM: None
UMTS: None
LTE: None
N.CCE.Used.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.CCE.Avail.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.2.12.4 Number of Available PRBs in a Cell
Counters
1911816582 N.PRB.UL.Ava Average BTS3900, N

il.Avg number of BTS3900 5G,
available uplink BTS5900,
PRBs
BTS5900 5G


1911816679 N.PRB.DL.Ava Average BTS3900, N

il.Avg number of BTS3900 5G,
available BTS5900,
downlink PRBs
BTS5900 5G
Description
The counters separately measure the numbers of available uplink and downlink PRBs, which
are related to the cell bandwidth.
Measurement Points
The numbers of available uplink and downlink PRBs are separately sampled per slot. At the
end of a measurement period, the averages of these sampling results are used as the counter
values.
Formula
None
Unit
None
Related Features
N.PRB.UL.Avail.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.PRB.DL.Avail.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: None

1.2.12.5 Number of Times of Successful PDCCH Resource Allocations with a

Specific Aggregation Level
Counters
1911817110 N.CCE.DL.Agg Number of BTS3900, N

Lvl1Num times of BTS3900 5G,
successful BTS5900,
PDCCH
allocations with
aggregation
level 1

successful BTS5900,
PDCCH
allocations with
aggregation
level 2

successful BTS5900,
PDCCH
allocations with
aggregation
level 4

successful BTS5900,
PDCCH
allocations with
aggregation
level 8

successful BTS5900,
PDCCH
allocations with
aggregation
level 16


1911817115 N.CCE.UL.Agg Number of BTS3900, N

successful BTS5900,
PDCCH uplink
DCI allocations BTS5900 5G
with
aggregation
level 1

successful BTS5900,
PDCCH uplink
with
aggregation
level 2

successful BTS5900,
PDCCH uplink
with
aggregation
level 4

successful BTS5900,
PDCCH uplink
with
aggregation
level 8

successful BTS5900,
PDCCH uplink
with
aggregation
level 16
Description
These counters measure the number of times of successful PDCCH uplink and downlink DCI
allocations with different aggregation levels

Measurement Points
The number of successful uplink DCI and downlink DCI allocations with different
aggregation levels are independently measured in a measurement period.
Formula
None
Unit
None
Related Features
N.CCE.DL.AggLvl1Num Multi-mode: None

GSM: None
UMTS: None
LTE: None
NR: FBFD-010009 Channel Management

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

N.CCE.UL.AggLvl1Num Multi-mode: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

1.2.12.6 Number of CCEs with More Than One PDCCH Spatial Multiplexing
Layer
Counters
1911817480 N.CCE.MU.La Number of BTS3900, N

yerGreaterThan CCEs with BTS3900 5G,
1.Num more than one BTS5900,
PDCCH spatial
multiplexing BTS5900 5G
layer
Description
This counter measures the number of CCEs with more than one spatial multiplexing layer on
the downlink control channel in a cell.
Measurement Points
The number of CCEs with more than one spatial multiplexing layer is sampled per slot. At the
end of a measurement period, the total number of CCEs with more than one spatial
multiplexing layer is accumulated on the downlink control channel in a cell. For example, if a
CCE is spatially multiplexed by multiple UEs in a slot, the value of this counter is
incremented by 1.
Formula
None
Unit
None
Related Features
N.CCE.MU.LayerGreaterTh Multi-mode: None

an1.Num GSM: None
UMTS: None
LTE: None

PUSCH with 256QAM (ChMeas.PUSCH.256QAM.MCS.DuCell)
Overview
ChMeas.PUSCH.256QAM.MCS.DuCell function subset measures the total number of RBs
used by different MCS indexes with 256QAM in the uplink. The result indicates the overall
uplink quality for scheduling in the cell.
Counters
1911817713 N.ChMeas.RB.PUS Number of RBs BTS3900:

256QAM.RANK1. PUSCH with rank 1 BTS5900:















































































































































None
1.2.13.1 Number of RBs Allocated for PUSCH with Different MCS Indexes in the
Counters

PUSCH. allocated for BTS3900 5G,
256QAM.RAN PUSCH with BTS5900,
K1.MCS.0 rank 1 and
the MCS index
table with
256QAM

K1.MCS.1 rank 1 and
the MCS index
table with
256QAM



K1.MCS.2 rank 1 and
the MCS index
table with
256QAM

K1.MCS.3 rank 1 and
the MCS index
table with
256QAM

K1.MCS.4 rank 1 and
the MCS index
table with
256QAM

K1.MCS.5 rank 1 and
the MCS index
table with
256QAM

K1.MCS.6 rank 1 and
the MCS index
table with
256QAM



K1.MCS.7 rank 1 and
the MCS index
table with
256QAM

K1.MCS.8 rank 1 and
the MCS index
table with
256QAM

K1.MCS.9 rank 1 and
the MCS index
table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

K2.MCS.0 rank 2 and
the MCS index
table with
256QAM

K2.MCS.1 rank 2 and
the MCS index
table with
256QAM

K2.MCS.2 rank 2 and
the MCS index
table with
256QAM

K2.MCS.3 rank 2 and
the MCS index
table with
256QAM



K2.MCS.4 rank 2 and
the MCS index
table with
256QAM

K2.MCS.5 rank 2 and
the MCS index
table with
256QAM

K2.MCS.6 rank 2 and
the MCS index
table with
256QAM

K2.MCS.7 rank 2 and
the MCS index
table with
256QAM

K2.MCS.8 rank 2 and
the MCS index
table with
256QAM



K2.MCS.9 rank 2 and
the MCS index
table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

K3.MCS.0 rank 3 and
the MCS index
table with
256QAM



K3.MCS.1 rank 3 and
the MCS index
table with
256QAM

K3.MCS.2 rank 3 and
the MCS index
table with
256QAM

K3.MCS.3 rank 3 and
the MCS index
table with
256QAM

K3.MCS.4 rank 3 and
the MCS index
table with
256QAM

K3.MCS.5 rank 3 and
the MCS index
table with
256QAM



K3.MCS.6 rank 3 and
the MCS index
table with
256QAM

K3.MCS.7 rank 3 and
the MCS index
table with
256QAM

K3.MCS.8 rank 3 and
the MCS index
table with
256QAM

K3.MCS.9 rank 3 and
the MCS index
table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

K4.MCS.0 rank 4 and
the MCS index
table with
256QAM

K4.MCS.1 rank 4 and
the MCS index
table with
256QAM

K4.MCS.2 rank 4 and
the MCS index
table with
256QAM



K4.MCS.3 rank 4 and
the MCS index
table with
256QAM

K4.MCS.4 rank 4 and
the MCS index
table with
256QAM

K4.MCS.5 rank 4 and
the MCS index
table with
256QAM

K4.MCS.6 rank 4 and
the MCS index
table with
256QAM

K4.MCS.7 rank 4 and
the MCS index
table with
256QAM



K4.MCS.8 rank 4 and
the MCS index
table with
256QAM

K4.MCS.9 rank 4 and
the MCS index
table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM



in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM

in the MCS
index table with
256QAM
Description
The counters measure the total number of RBs used in uplink scheduling of different MCS
indexes using different ranks with 256QAM. For details about the MCS index table
corresponding to 256QAM, see "MCS index table 2 for PDSCH" in 3GPP 38.214.

Measurement Points
The total number of RBs used in uplink scheduling of different MCS indexes using different
ranks with 256QAM are sampled within a measurement period. For details about the MCS
index table corresponding to 256QAM, see "MCS index table 2 for PDSCH" in 3GPP 38.214.
Formula
None
Unit
None
Related Features
N.ChMeas.RB.PUSCH. Multi-mode: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None
PUSCH with Transform Precoding and 64QAM (ChMeas.PUSCH.
64QAMTP.MCS.DuCell)
Overview
Measurement per MCS Index in the MCS Index Table for PUSCH with Transform Precoding
and 64QAM (ChMeas.PUSCH.64QAMTP.MCS.DuCell) function subset measures the
number of RBs used in uplink scheduling when different MCS indexes in the MCS index
table with transform precoding and 64QAM (DFT-S-OFDM waveform 64QAM table) are
used in an NR DU cell. This function subset is used to analyze the overall status of uplink
scheduling.
Counters

64QAMTP.RANK1 PUSCH with rank 1 BTS5900:
.MCS.0 and MCS index 0 in V100R015C10
with transform V100R015C10
precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

.MCS.10 and MCS index 10 V100R015C10
table with transform V100R015C10
precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM

precoding and
64QAM



precoding and
64QAM
None
MCS Index Table with Transform Precoding and 64QAM
Counters

64QAMTP.RA PUSCH with BTS5900,
NK1.MCS.0 rank 1 and
the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM



the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM



the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM



the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM



the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM



the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM



the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM



the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM



the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM

the MCS index
table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM



in the MCS
index table with
transform
precoding and
64QAM

in the MCS
index table with
transform
precoding and
64QAM
Description
indexes using different ranks with transform precoding and 64QAM. For details about the
MCS index table corresponding to transform precoding and 64QAM, see "MCS index table
for PUSCH with transform precoding and 64QAM" in 3GPP 38.214.
Measurement Points
ranks with transform precoding and 64QAM are sampled within a measurement period. For
details about the MCS index table corresponding to transform precoding and 64QAM, see
"MCS index table for PUSCH with transform precoding and 64QAM" in 3GPP 38.214.
Formula
None
Unit
None

Related Features

64QAMTP.RANK1.MCS.0 GSM: None
UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

64QAMTP.RANK1.MCS. GSM: None
10
UMTS: None
LTE: None

UMTS: None
LTE: None

12
UMTS: None
LTE: None

13
UMTS: None
LTE: None


14
UMTS: None
LTE: None

15
UMTS: None
LTE: None

16
UMTS: None
LTE: None

17
UMTS: None
LTE: None

18
UMTS: None
LTE: None

19
UMTS: None
LTE: None

20
UMTS: None
LTE: None


21
UMTS: None
LTE: None

22
UMTS: None
LTE: None

23
UMTS: None
LTE: None

24
UMTS: None
LTE: None

25
UMTS: None
LTE: None

26
UMTS: None
LTE: None

27
UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

10
UMTS: None
LTE: None

UMTS: None
LTE: None

12
UMTS: None
LTE: None

13
UMTS: None
LTE: None


14
UMTS: None
LTE: None

15
UMTS: None
LTE: None

16
UMTS: None
LTE: None

17
UMTS: None
LTE: None

18
UMTS: None
LTE: None

19
UMTS: None
LTE: None

20
UMTS: None
LTE: None


21
UMTS: None
LTE: None

22
UMTS: None
LTE: None

23
UMTS: None
LTE: None

24
UMTS: None
LTE: None

25
UMTS: None
LTE: None

26
UMTS: None
LTE: None

27
UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

10
UMTS: None
LTE: None

UMTS: None
LTE: None

12
UMTS: None
LTE: None

13
UMTS: None
LTE: None


14
UMTS: None
LTE: None

15
UMTS: None
LTE: None

16
UMTS: None
LTE: None

17
UMTS: None
LTE: None

18
UMTS: None
LTE: None

19
UMTS: None
LTE: None

20
UMTS: None
LTE: None


21
UMTS: None
LTE: None

22
UMTS: None
LTE: None

23
UMTS: None
LTE: None

24
UMTS: None
LTE: None

25
UMTS: None
LTE: None

26
UMTS: None
LTE: None

27
UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

10
UMTS: None
LTE: None

UMTS: None
LTE: None

12
UMTS: None
LTE: None

13
UMTS: None
LTE: None


14
UMTS: None
LTE: None

15
UMTS: None
LTE: None

16
UMTS: None
LTE: None

17
UMTS: None
LTE: None

18
UMTS: None
LTE: None

19
UMTS: None
LTE: None

20
UMTS: None
LTE: None


21
UMTS: None
LTE: None

22
UMTS: None
LTE: None

23
UMTS: None
LTE: None

24
UMTS: None
LTE: None

25
UMTS: None
LTE: None

26
UMTS: None
LTE: None

27
UMTS: None
LTE: None

PUSCH with 64QAM (ChMeas.PUSCH.64QAM.MCS.DuCell)
Overview
ChMeas.PUSCH.64QAM.MCS.DuCell function subset measures the total number of RBs
used by different MCS indexes with 64QAM in the uplink. The result indicates the overall
uplink quality for scheduling in the cell. For details, see "64QAM for transform precoding
disable" in 3GPP TS 38.214.
Counters

64QAM.RANK1.M PUSCH with rank 1 BTS5900:



















































































































































None

Counters

64QAM.RANK PUSCH with BTS5900,
1.MCS.0 rank 1 and
the MCS index
table with
64QAM

1.MCS.1 rank 1 and
the MCS index
table with
64QAM

1.MCS.2 rank 1 and
the MCS index
table with
64QAM

1.MCS.3 rank 1 and
the MCS index
table with
64QAM

1.MCS.4 rank 1 and
the MCS index
table with
64QAM



1.MCS.5 rank 1 and
the MCS index
table with
64QAM

1.MCS.6 rank 1 and
the MCS index
table with
64QAM

1.MCS.7 rank 1 and
the MCS index
table with
64QAM

1.MCS.8 rank 1 and
the MCS index
table with
64QAM

1.MCS.9 rank 1 and
the MCS index
table with
64QAM



1.MCS.10 rank 1 and
in the MCS
index table with
64QAM

1.MCS.11 rank 1 and
in the MCS
index table with
64QAM

1.MCS.12 rank 1 and
in the MCS
index table with
64QAM

1.MCS.13 rank 1 and
in the MCS
index table with
64QAM

1.MCS.14 rank 1 and
in the MCS
index table with
64QAM



1.MCS.15 rank 1 and
in the MCS
index table with
64QAM

1.MCS.16 rank 1 and
in the MCS
index table with
64QAM

1.MCS.17 rank 1 and
in the MCS
index table with
64QAM

1.MCS.18 rank 1 and
in the MCS
index table with
64QAM

1.MCS.19 rank 1 and
in the MCS
index table with
64QAM



1.MCS.20 rank 1 and
in the MCS
index table with
64QAM

1.MCS.21 rank 1 and
in the MCS
index table with
64QAM

1.MCS.22 rank 1 and
in the MCS
index table with
64QAM

1.MCS.23 rank 1 and
in the MCS
index table with
64QAM

1.MCS.24 rank 1 and
in the MCS
index table with
64QAM



1.MCS.25 rank 1 and
in the MCS
index table with
64QAM

1.MCS.26 rank 1 and
in the MCS
index table with
64QAM

1.MCS.27 rank 1 and
in the MCS
index table with
64QAM

1.MCS.28 rank 1 and
in the MCS
index table with
64QAM

2.MCS.0 rank 2 and
the MCS index
table with
64QAM



2.MCS.1 rank 2 and
the MCS index
table with
64QAM

2.MCS.2 rank 2 and
the MCS index
table with
64QAM

2.MCS.3 rank 2 and
the MCS index
table with
64QAM

2.MCS.4 rank 2 and
the MCS index
table with
64QAM

2.MCS.5 rank 2 and
the MCS index
table with
64QAM



2.MCS.6 rank 2 and
the MCS index
table with
64QAM

2.MCS.7 rank 2 and
the MCS index
table with
64QAM

2.MCS.8 rank 2 and
the MCS index
table with
64QAM

2.MCS.9 rank 2 and
the MCS index
table with
64QAM

2.MCS.10 rank 2 and
in the MCS
index table with
64QAM



2.MCS.11 rank 2 and
in the MCS
index table with
64QAM

2.MCS.12 rank 2 and
in the MCS
index table with
64QAM

2.MCS.13 rank 2 and
in the MCS
index table with
64QAM

2.MCS.14 rank 2 and
in the MCS
index table with
64QAM

2.MCS.15 rank 2 and
in the MCS
index table with
64QAM



2.MCS.16 rank 2 and
in the MCS
index table with
64QAM

2.MCS.17 rank 2 and
in the MCS
index table with
64QAM

2.MCS.18 rank 2 and
in the MCS
index table with
64QAM

2.MCS.19 rank 2 and
in the MCS
index table with
64QAM

2.MCS.20 rank 2 and
in the MCS
index table with
64QAM



2.MCS.21 rank 2 and
in the MCS
index table with
64QAM

2.MCS.22 rank 2 and
in the MCS
index table with
64QAM

2.MCS.23 rank 2 and
in the MCS
index table with
64QAM

2.MCS.24 rank 2 and
in the MCS
index table with
64QAM

2.MCS.25 rank 2 and
in the MCS
index table with
64QAM



2.MCS.26 rank 2 and
in the MCS
index table with
64QAM

2.MCS.27 rank 2 and
in the MCS
index table with
64QAM

2.MCS.28 rank 2 and
in the MCS
index table with
64QAM

3.MCS.0 rank 3 and
the MCS index
table with
64QAM

3.MCS.1 rank 3 and
the MCS index
table with
64QAM



3.MCS.2 rank 3 and
the MCS index
table with
64QAM

3.MCS.3 rank 3 and
the MCS index
table with
64QAM

3.MCS.4 rank 3 and
the MCS index
table with
64QAM

3.MCS.5 rank 3 and
the MCS index
table with
64QAM

3.MCS.6 rank 3 and
the MCS index
table with
64QAM



3.MCS.7 rank 3 and
the MCS index
table with
64QAM

3.MCS.8 rank 3 and
the MCS index
table with
64QAM

3.MCS.9 rank 3 and
the MCS index
table with
64QAM

3.MCS.10 rank 3 and
in the MCS
index table with
64QAM

3.MCS.11 rank 3 and
in the MCS
index table with
64QAM



3.MCS.12 rank 3 and
in the MCS
index table with
64QAM

3.MCS.13 rank 3 and
in the MCS
index table with
64QAM

3.MCS.14 rank 3 and
in the MCS
index table with
64QAM

3.MCS.15 rank 3 and
in the MCS
index table with
64QAM

3.MCS.16 rank 3 and
in the MCS
index table with
64QAM



3.MCS.17 rank 3 and
in the MCS
index table with
64QAM

3.MCS.18 rank 3 and
in the MCS
index table with
64QAM

3.MCS.19 rank 3 and
in the MCS
index table with
64QAM

3.MCS.20 rank 3 and
in the MCS
index table with
64QAM

3.MCS.21 rank 3 and
in the MCS
index table with
64QAM



3.MCS.22 rank 3 and
in the MCS
index table with
64QAM

3.MCS.23 rank 3 and
in the MCS
index table with
64QAM

3.MCS.24 rank 3 and
in the MCS
index table with
64QAM

3.MCS.25 rank 3 and
in the MCS
index table with
64QAM

3.MCS.26 rank 3 and
in the MCS
index table with
64QAM



3.MCS.27 rank 3 and
in the MCS
index table with
64QAM

3.MCS.28 rank 3 and
in the MCS
index table with
64QAM

4.MCS.0 rank 4 and
the MCS index
table with
64QAM

4.MCS.1 rank 4 and
the MCS index
table with
64QAM

4.MCS.2 rank 4 and
the MCS index
table with
64QAM



4.MCS.3 rank 4 and
the MCS index
table with
64QAM

4.MCS.4 rank 4 and
the MCS index
table with
64QAM

4.MCS.5 rank 4 and
the MCS index
table with
64QAM

4.MCS.6 rank 4 and
the MCS index
table with
64QAM

4.MCS.7 rank 4 and
the MCS index
table with
64QAM



4.MCS.8 rank 4 and
the MCS index
table with
64QAM

4.MCS.9 rank 4 and
the MCS index
table with
64QAM

4.MCS.10 rank 4 and
in the MCS
index table with
64QAM

4.MCS.11 rank 4 and
in the MCS
index table with
64QAM

4.MCS.12 rank 4 and
in the MCS
index table with
64QAM



4.MCS.13 rank 4 and
in the MCS
index table with
64QAM

4.MCS.14 rank 4 and
in the MCS
index table with
64QAM

4.MCS.15 rank 4 and
in the MCS
index table with
64QAM

4.MCS.16 rank 4 and
in the MCS
index table with
64QAM

4.MCS.17 rank 4 and
in the MCS
index table with
64QAM



4.MCS.18 rank 4 and
in the MCS
index table with
64QAM

4.MCS.19 rank 4 and
in the MCS
index table with
64QAM

4.MCS.20 rank 4 and
in the MCS
index table with
64QAM

4.MCS.21 rank 4 and
in the MCS
index table with
64QAM

4.MCS.22 rank 4 and
in the MCS
index table with
64QAM



4.MCS.23 rank 4 and
in the MCS
index table with
64QAM

4.MCS.24 rank 4 and
in the MCS
index table with
64QAM

4.MCS.25 rank 4 and
in the MCS
index table with
64QAM

4.MCS.26 rank 4 and
in the MCS
index table with
64QAM

4.MCS.27 rank 4 and
in the MCS
index table with
64QAM



4.MCS.28 rank 4 and
in the MCS
index table with
64QAM
Description
indexes using different ranks with 64QAM. For details about the MCS index table
corresponding to 64QAM, see "MCS index table 1 for PDSCH" in 3GPP 38.214.
Measurement Points
ranks with 64QAM are sampled within a measurement period. For details about the MCS
index table corresponding to 64QAM, see "MCS index table 1 for PDSCH" in 3GPP 38.214.
Formula
None
Unit
None
Related Features

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None

UMTS: None
LTE: None


UMTS: None
LTE: None

UMTS: None
LTE: None
1.2.16 RLC Measurement (RLC.DuCell)
Overview
The RLC Measurement(RLC.DuCell) function subset is used for measurements at the RLC
layer.
Counters
1911816718 N.RLC.DL.TrfSDU Number of downlink BTS5900 5G:

.RxPackets SDUs received at V100R013C10
the RLC layer in a BTS5900:
cell V100R013C10
BTS3900:
V100R015C00
1911816719 N.RLC.UL.TrfSDU Number of uplink BTS5900 5G:

.TxPackets SDUs sent at the V100R013C10
RLC layer in a cell BTS5900:
V100R013C10
BTS3900:
V100R015C00
1911816720 N.RLC.DL.TrfSDU Number of downlink BTS5900 5G:

.PktUuTrans.Loss SDUs lost at the V100R013C10
RLC layer over the BTS5900:
radio interface in a V100R013C10
cell BTS3900:
V100R015C00

None
1.2.16.1 Number of Downlink SDUs Received at the RLC Layer in a Cell
Counters
1911816718 N.RLC.DL.Trf Number of BTS3900, N

SDU.RxPackets downlink SDUs BTS3900 5G,
RLC layer in a
cell BTS5900 5G
Description
The counter measures the number of downlink SDUs received at the RLC layer in a cell.
Measurement Points
The number of downlink SDUs received at the RLC layer accumulates in a cell. The
accumulation result is used as the counter value.
Formula
None
Unit
None
Related Features
None
1.2.16.2 Number of Uplink SDUs Sent at the RLC Layer in a Cell
Counters
1911816719 N.RLC.UL.Trf Number of BTS3900, N

SDU.TxPackets uplink SDUs BTS3900 5G,
sent at the RLC BTS5900,
layer in a cell
BTS5900 5G

Description
The counter measures the number of uplink SDUs sent at the RLC layer in a cell.
Measurement Points
The number of uplink SDUs sent at the RLC layer accumulates in a cell. The accumulation
result is used as the counter value.
Formula
None
Unit
None
Related Features
None
1.2.16.3 Number of Downlink SDUs Lost at the RLC Layer over the Radio
Interface in a Cell
Counters
1911816720 N.RLC.DL.Trf Number of BTS3900, N

SDU.PktUuTra downlink SDUs BTS3900 5G,
ns.Loss lost at the RLC BTS5900,
layer over the
radio interface BTS5900 5G
in a cell
Description
The counter measures the number of downlink SDUs lost at the RLC layer over the radio
interface in a cell.
Measurement Points
The number of downlink SDUs lost at the RLC layer over the radio interface accumulates in a
cell. The accumulation result is used as the counter value.
Formula
None

Unit
None
Related Features
None
1.2.17 Channel Quality Measurement (ChMeas.Pwr.DuCell)

Overview
The Channel Quality Measurement(ChMeas.Pwr.DuCell) function subset measures the power
usage in an NR DU cell. It is used to analyze the overall downlink channel quality.
Counters
1911816721 N.UL.NI.Max Maximum BTS5900 5G:

interference received V100R013C10
on each uplink PRB BTS5900:
V100R013C10
BTS3900:
V100R015C00
1911816722 N.UL.NI.Avg Average interference BTS5900 5G:

received on each V100R013C10
uplink PRB BTS5900:
V100R013C10
BTS3900:
V100R015C00
1911816723 N.UL.NI.Min Minimum BTS5900 5G:

interference received V100R013C10
on each uplink PRB BTS5900:
V100R013C10
BTS3900:
V100R015C00
1911816764 N.UL.RSSI.Avg Average uplink BTS5900 5G:

RSSI of channels V100R015C00
BTS5900:
V100R015C00
BTS3900:
V100R015C00


1911816765 N.UL.RSSI.Min Minimum uplink BTS5900 5G:

RSSI of channels V100R015C00
BTS5900:
V100R015C00
BTS3900:
V100R015C00
1911817481 N.DL.AvgPrdPwr. Maximum average BTS3900:

Max downlink transmit V100R015C10
power in a cell BTS5900:
V100R015C10
BTS5900 5G:
V100R015C10
1911817482 N.DL.Pwr.Max Maximum downlink BTS3900:

transmit power in a V100R015C10
cell BTS5900:
V100R015C10
BTS5900 5G:
V100R015C10
1911817833 N.UL.Last.Symbol Power of the BTS5900 5G:

13.Pwr thirteenth symbol on V100R015C10
the last uplink slot BTS3900:
V100R015C10
BTS5900:
V100R015C10
1911817834 N.UL.Last.Symbol Power of the sixth BTS5900 5G:

6.Pwr symbol on the last V100R015C10
uplink slot BTS3900:
V100R015C10
BTS5900:
V100R015C10
1911817835 N.GAP.LastSymbol Power of the Last BTS5900 5G:

.Pwr Symbol in a GAP V100R015C10
BTS3900:
V100R015C10
BTS5900:
V100R015C10
None

1.2.17.1 Interference Received on Each Uplink PRB
Counters
1911816721 N.UL.NI.Max Maximum BTS3900, N

interference BTS3900 5G,
received on BTS5900,
each uplink
PRB BTS5900 5G
1911816722 N.UL.NI.Avg Average BTS3900, N

each uplink
PRB BTS5900 5G
1911816723 N.UL.NI.Min Minimum BTS3900, N

each uplink
PRB BTS5900 5G
Description
These counters measure the maximum, average, and minimum interference received on each
uplink PRB.
Measurement Points
The gNodeB measures the total power of interference received on each uplink PRB and
calculates the average value as a sample every second. At the end of a measurement period,
the maximum, average, and minimum of these sampling results are used as the maximum,
average, and minimum interference received on each uplink PRB, respectively.
Formula
None
Unit
dBm

Related Features
N.UL.NI.Max Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.UL.NI.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.UL.NI.Min Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.2.17.2 Uplink RSSI Measurement
Counters
1911816764 N.UL.RSSI.Av Average uplink BTS3900, N

g RSSI of BTS3900 5G,
channels BTS5900,
BTS5900 5G
1911816765 N.UL.RSSI.Mi Minimum BTS3900, N

n uplink RSSI of BTS3900 5G,
channels BTS5900,
BTS5900 5G
Description
The counters measure the average and minimum RSSIs of uplink channels in a cell.

Measurement Points
The average of channel RSSIs is sampled every 10 ms. Within a measurement period, the
average and minimum of these samples are used as the corresponding counter values.
Formula
None
Unit
dBm
Related Features
N.UL.RSSI.Avg Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.UL.RSSI.Min Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.2.17.3 Cell Downlink Transmit Power
Counters
1911817481 N.DL.AvgPrdP Maximum BTS3900, N

wr.Max average BTS3900 5G,
downlink BTS5900,
transmit power


1911817482 N.DL.Pwr.Max Maximum BTS3900, N

downlink BTS3900 5G,
transmit power BTS5900,
in a cell
BTS5900 5G
Description
These counters are used to analyze the usage of downlink transmit power in a cell.
Measurement Points
These counters are used to measure the transmit power in a cell.
In a measurement period, the average power within the period of time specified by the
AveragePeriod parameter in the NRDUCellSmartPwrLock MO is calculated. At the end of the
measurement period, the maximum average power is used as the value of the
N.DL.AvgPrdPwr.Max counter.
The maximum downlink transmit power is sampled per second in a measurement period in a
cell, and used as the value of the N.DL.Pwr.Max counter.
Formula
None
Unit
dBm
Related Features
None
1.2.17.4 Power of the Thirteenth Symbol on the Last Uplink Slot
Counters
1911817833 N.UL.Last.Sym Power of the BTS3900, N

bol13.Pwr thirteenth BTS3900 5G,
symbol on the BTS5900,
last uplink slot
BTS5900 5G

Description
This counter measures the power of the thirteenth symbol on the last uplink slot.
Measurement Points
The total power of idle RBs on the thirteenth symbol of the last uplink slot is sampled in a
cell, and the average value of the sampling values in a measurement period is used as the
counter value.
Formula
None
Unit
dBm
Related Features
N.UL.Last.Symbol13.Pwr Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.2.17.5 Power of the Sixth Symbol on the Last Uplink Slot
Counters
1911817834 N.UL.Last.Sym Power of the BTS3900, N

bol6.Pwr sixth symbol on BTS3900 5G,
the last uplink BTS5900,
slot
BTS5900 5G
Description
This counter measures the power of the sixth symbol on the last uplink slot.
Measurement Points
The total interference power on the sixth symbol of the last uplink slot is sampled, and the
average value of the sampling results in a measurement period is used as the counter value.

Formula
None
Unit
dBm
Related Features
N.UL.Last.Symbol6.Pwr Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.2.17.6 Power of the Last Symbol in a GAP
Counters
1911817835 N.GAP.LastSy Power of the BTS3900, N

mbol.Pwr Last Symbol in BTS3900 5G,
a GAP BTS5900,
BTS5900 5G
Description
This counter measures the interference noise detected on the last symbol in a GAP.
Measurement Points
The total power on the last symbol in a GAP is sampled, and the average value of the
sampling results in a measurement period is used as the counter value.
Formula
None
Unit
dBm

Related Features
N.GAP.LastSymbol.Pwr Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.2.18 DU Cell CA Measurement (CA.DuCell)
Overview
The DU Cell CA Measurement (CA.DuCell) function subset measures the number of SCell
activation and deactivation times and other related items for CA UEs in a DU cell.
Counters
1911816896 N.CA.SCell.Act.Att Number of SCell BTS5900 5G:

activation V100R015C00
executions for CA BTS5900:
UEs V100R015C00
BTS3900:
V100R015C00
1911816897 N.CA.SCell.Act.Su Number of BTS5900 5G:

cc successful SCell V100R015C00
activations for CA BTS5900:
UEs V100R015C00
BTS3900:
V100R015C00
1911816898 N.CA.SCell.Deact. Number of SCell BTS5900 5G:

Att deactivation V100R015C00
executions for CA BTS5900:
UEs V100R015C00
BTS3900:
V100R015C00
1911816899 N.CA.SCell.Deact. Number of BTS5900 5G:

Succ successful SCell V100R015C00
deactivations for CA BTS5900:
UEs V100R015C00
BTS3900:
V100R015C00

None
1.2.18.1 Number of SCell Activation and Deactivation Executions for CA UEs
Counters
1911816896 N.CA.SCell.Act Number of BTS3900, N

.Att SCell activation BTS5900,
executions for BTS5900 5G
CA UEs
1911816897 N.CA.SCell.Act Number of BTS3900, N

.Succ successful BTS5900,
SCell BTS5900 5G
activations for
CA UEs
1911816898 N.CA.SCell.De Number of BTS3900, N

act.Att SCell BTS5900,
deactivation BTS5900 5G
executions for
CA UEs
1911816899 N.CA.SCell.De Number of BTS3900, N

act.Succ successful BTS5900,
SCell BTS5900 5G
deactivations
for CA UEs
Description
These counters measure the number of SCell activation attempts, the number of successful
SCell activations, the number of SCell deactivation attempts, the number of successful SCell
deactivations for CA UEs.
Measurement Points
The N.CA.SCell.Act.Att counter is incremented by 1 each time the gNodeB sends an SCell
activation command to the UE via a Media Access Control control element (MAC CE).
The N.CA.SCell.Act.Succ counter is incremented by 1 each time the gNodeB receives an
ACK message from the UE after sending an SCell activation command to the UE via a MAC
CE.
The N.CA.SCell.Deact.Att counter is incremented by 1 each time the gNodeB sends an SCell
deactivation command to the UE via a MAC CE.

The N.CA.SCell.Deact.Succ counter is incremented by 1 each time the gNodeB receives an

ACK message from the UE after sending an SCell deactivation command to the UE via a
MAC CE.
All these counters are measured in the PCell.
Formula
None
Unit
None
Related Features
N.CA.SCell.Act.Att Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.CA.SCell.Act.Succ Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.CA.SCell.Deact.Att Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.CA.SCell.Deact.Succ Multi-mode: None

GSM: None
UMTS: None
LTE: None

1.2.19 UE Throughput Distribution Measurement

(Thp.PDF.DuCell)
Overview
The UE Throughput Distribution Measurement(Thp.PDF.DuCell) function subset measures
the UE throughput within a specified sampling period, and provides the throughput
distribution for network-level performance evaluation.
Counters
1911816698 N.Thp.DL.Samp.In Number of samples BTS5900 5G:

dex0 with the downlink V100R015C10
throughput falling BTS5900:
into range 0 V100R015C10
BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10



BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10
1911816708 N.Thp.UL.Samp.In Number of samples BTS5900 5G:

dex0 with the uplink V100R015C10
BTS3900:
V100R015C10

BTS3900:
V100R015C10



BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10



BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10



BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10

BTS3900:
V100R015C10
None
1.2.19.1 RLC-Layer Downlink UE Throughput Distribution
Counters
1911816698 N.Thp.DL.Sam Number of BTS3900, N

p.Index0 samples with BTS3900 5G,
throughput
falling into BTS5900 5G
range 0



throughput
range 1

throughput
range 2

throughput
range 3

throughput
range 4

throughput
range 5

throughput
range 6

throughput
range 7



throughput
range 8

throughput
range 9

throughput
range 14

throughput
range 11

throughput
range 12

throughput
range 10

throughput
range 13

Description
These counters measure the RLC-layer downlink SDU throughput of DRB bearers for all UEs
in a cell, and describe throughput distribution.
These counters correspond to 15 ranges. You can use the ThptThldId parameter in the
gNBThptCounterThld MO to specify a range index, and use the DlThptThld parameter to
modify the threshold for a specific range. When this parameter uses the default values, the
downlink throughput ranges are as follows:
Range 0: (0, 1024 kbit/s)
Range 1: [1024 kbit/s, 5120 kbit/s)
Range 14: [1024000 kbit/s, Infinity)
Measurement Points
The downlink traffic volume and data transmission duration over DRB bearers are sampled
for each UE per second in a cell, excluding the last timeslot during which the downlink buffer
becomes empty. If there is downlink data transmission in a sample, the downlink throughput
is calculated for the UE and the corresponding counter is incremented by 1 based on the
throughput.The following table describes the measurement points of each counter.
The following table describes the Measurement Points of each counter.
Counter Name Measurement Points
N.Thp.DL.Samp.Index0 wait for translate

Formula
None
Unit
None
Related Features
None
1.2.19.2 RLC-Layer Uplink UE Throughput Distribution
Counters
1911816708 N.Thp.UL.Sam Number of BTS3900, N

the uplink BTS5900,
throughput
range 0

the uplink BTS5900,
throughput
range 1



the uplink BTS5900,
throughput
range 2

the uplink BTS5900,
throughput
range 3

the uplink BTS5900,
throughput
range 4

the uplink BTS5900,
throughput
range 5

the uplink BTS5900,
throughput
range 6

the uplink BTS5900,
throughput
range 7

the uplink BTS5900,
throughput
range 8



the uplink BTS5900,
throughput
range 9

the uplink BTS5900,
throughput
range 10

the uplink BTS5900,
throughput
range 12

the uplink BTS5900,
throughput
range 13

the uplink BTS5900,
throughput
range 14

the uplink BTS5900,
throughput
range 11
Description
These counters measure the RLC-layer uplink SDU throughput for all UEs in a cell, and
describe throughput distribution.
These counters correspond to 15 ranges. You can use the ThptThldId parameter in the
gNBThptCounterThld MO to specify a range index, and use the UlThptThld parameter to
modify the threshold for a specific range. When this parameter uses the default values, the
uplink throughput ranges are as follows:

Range 0: (0, 512 kbit/s)
Range 14: [512000 kbit/s, Infinity)
Measurement Points
The uplink traffic volume and data transmission duration are sampled for each UE per second
in a cell, excluding the last timeslot during which the uplink buffer becomes empty and
excluding the small packet scheduling before a valid buffer status report (BSR) is received. If
there is uplink data transmission in a sample, the uplink throughput is calculated for the UE
and the corresponding counter is incremented by 1 based on the throughput.The following
table describes the measurement points of each counter.
The following table describes the Measurement Points of each counter.
N.Thp.UL.Samp.Index0 wait for translate

Formula
None
Unit
None
Related Features
None
1.2.20 Throughput and Data Volume Measurement (Thp.DuCell)
Overview
The Throughput and Data Volume Measurement(Thp.DuCell) function subset measures the
uplink and downlink data volumes and durations of data transmission in an NR DU cell.
Counters
1911816643 N.ThpVol.DL Total volume of BTS5900 5G:

downlink data sent V100R013C10
at the RLC layer in a BTS5900:
cell V100R013C10
BTS3900:
V100R015C00
1911816644 N.ThpTime.DL Duration of BTS5900 5G:

downlink data V100R013C10
transmission at the BTS5900:
BTS3900:
V100R015C00


1911816645 N.ThpVol.UL Total volume of BTS5900 5G:

uplink data received V100R013C10
cell V100R013C10
BTS3900:
V100R015C00
1911816646 N.ThpTime.UL Duration of uplink BTS5900 5G:

data transmission at V100R013C10
the RLC layer in a BTS5900:
cell V100R013C10
BTS3900:
V100R015C00
1911816694 N.ThpVol.DL.Cell Total volume of BTS5900 5G:

downlink data sent V100R013C10
at the MAC layer in BTS5900:
a cell V100R013C10
BTS3900:
V100R015C00
1911816695 N.ThpTime.DL.Cel Duration of BTS5900 5G:

l downlink data V100R013C10
transmission at the BTS5900:
MAC layer in a cell V100R013C10
BTS3900:
V100R015C00
1911816696 N.ThpVol.UL.Cell Total volume of BTS5900 5G:

uplink data received V100R013C10
at the MAC layer in BTS5900:
a cell V100R013C10
BTS3900:
V100R015C00
1911816697 N.ThpTime.UL.Cel Duration of uplink BTS5900 5G:

l data transmission at V100R013C10
the MAC layer in a BTS5900:
cell V100R013C10
BTS3900:
V100R015C00
1911816839 N.ThpVol.DL.B2H Volume of downlink BTS5900 5G:

data sent at the RLC V100R015C00
layer for B2H UEs BTS5900:
in a cell V100R015C00
BTS3900:
V100R015C00


1911816841 N.ThpVol.UL.B2H Volume of uplink BTS5900 5G:

data received at the V100R015C00
RLC layer for B2H BTS5900:
UEs in a cell V100R015C00
BTS3900:
V100R015C00
1911816848 N.ThpVol.DL.Last Downlink volume of BTS5900 5G:

Slot RLC SDUs sent in V100R015C00
the last timeslot BTS5900:
during which the V100R015C00
buffer becomes BTS3900:
empty V100R015C00
1911816850 N.ThpTime.DL.Rm Data transmission BTS5900 5G:

vLastSlot duration excluding V100R015C00
downlink buffer BTS3900:
becomes empty V100R015C00
1911816851 N.ThpVol.UE.UL.S Uplink volume of BTS5900 5G:

mallPkt small packets V100R015C00
received at the RLC BTS5900:
layer V100R015C00
BTS3900:
V100R015C00
1911816853 N.ThpTime.UE.UL Uplink data BTS5900 5G:

.RmvSmallPkt transmission V100R015C00
duration excluding BTS5900:
that of small packets V100R015C00
BTS3900:
V100R015C00
1911816854 N.ThpTime.DL.Tra Duration of correct BTS5900 5G:

nsfer.RmvLastSlot downlink data V100R015C00
transmission BTS5900:
excluding the last V100R015C00
timeslot BTS3900:
V100R015C00
1911816855 N.ThpTime.UE.UL Duration of correct BTS5900 5G:

.Transfer.RmvSmal uplink data V100R015C00
lPkt transmission BTS5900:
excluding that of V100R015C00
small packets BTS3900:
V100R015C00

None
1.2.20.1 Volume of Downlink Data Sent at the RLC Layer in a Cell
Counters
1911816643 N.ThpVol.DL Total volume of BTS3900, N

downlink data BTS3900 5G,
layer in a cell
BTS5900 5G
Description
The counter measures the total volume of downlink data sent at the RLC layer in a cell.
Measurement Points
The SDU payload of downlink data sent at the RLC layer accumulates in a cell. The
Formula
None
Unit
kbit
Related Features
None
1.2.20.2 Duration of Downlink Data Transmission at the RLC Layer in a Cell
Counters
1911816644 N.ThpTime.DL Duration of BTS3900, N

downlink data BTS3900 5G,
transmission at BTS5900,
the RLC layer

Description
The counter measures the sum of all UEs' durations in which the RLC-layer buffer is not
empty in a cell.
Measurement Points
The duration in which the RLC-layer downlink buffer is not empty accumulates for all UEs in
a cell. The accumulation result is used as the counter value.
Formula
None
Unit
microsecond
Related Features
None
1.2.20.3 Volume of Uplink Data Received at the RLC Layer in a Cell
Counters
1911816645 N.ThpVol.UL Total volume of BTS3900, N

uplink data BTS3900 5G,
RLC layer in a
cell BTS5900 5G
Description
The counter measures the total volume of uplink data received at the RLC layer in a cell.
Measurement Points
The SDU payload of uplink data received at the RLC layer accumulates in a cell. The
Formula
None
Unit
kbit

Related Features
None
1.2.20.4 Duration of Uplink Data Transmission at the RLC Layer in a Cell
Counters
1911816646 N.ThpTime.UL Duration of BTS3900, N

uplink data BTS3900 5G,
the RLC layer
Description
The counter measures the sum of all UEs' durations of receiving uplink data at the RLC layer
in a cell.
Measurement Points
The duration of receiving uplink data at the RLC layer accumulates for all UEs in a cell. The
Formula
None
Unit
microsecond
Related Features
None

1.2.20.5 Volume of Downlink Data Sent at the MAC Layer in a Cell
Counters
1911816694 N.ThpVol.DL.C Total volume of BTS3900, N

ell downlink data BTS3900 5G,
sent at the BTS5900,
MAC layer in a
cell BTS5900 5G
Description
The counter measures the total volume of downlink data correctly sent at the MAC layer in a
cell.
Measurement Points
The volume of downlink TBs correctly sent at the MAC layer accumulates in a cell, and the
accumulation result is used as the counter value. A downlink TB is correctly sent if an ACK
message is received for this TB.
Formula
None
Unit
kbit
Related Features
None
1.2.20.6 Duration of Downlink Data Transmission at the MAC Layer in a Cell
Counters
1911816695 N.ThpTime.DL. Duration of BTS3900, N

Cell downlink data BTS3900 5G,
the MAC layer

Description
The counter measures the total downlink transmit duration at the MAC layer in a cell.
Measurement Points
If data is transmitted on the downlink at the MAC layer within a timeslot, this counter is
incremented by the timeslot length.
Formula
None
Unit
microsecond
Related Features
N.ThpTime.DL.Cell Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.2.20.7 Volume of Uplink Data Received at the MAC Layer in a Cell
Counters
1911816696 N.ThpVol.UL.C Total volume of BTS3900, N

ell uplink data BTS3900 5G,
MAC layer in a
cell BTS5900 5G
Description
The counter measures the total volume of uplink data correctly received at the MAC layer in a
cell.

Measurement Points
The volume of uplink TBs correctly received at the MAC layer accumulates in a cell. The
Formula
None
Unit
kbit
Related Features
None
1.2.20.8 Duration of Uplink Data Transmission at the MAC Layer in a Cell
Counters
1911816697 N.ThpTime.UL. Duration of BTS3900, N

Cell uplink data BTS3900 5G,
the MAC layer
Description
The counter measures the total uplink receive duration at the MAC layer in a cell.
Measurement Points
If data is transmitted on the uplink at the MAC layer within a timeslot, this counter is
incremented by the timeslot length.
Formula
None
Unit
microsecond

Related Features
N.ThpTime.UL.Cell Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.2.20.9 Volume of Downlink Data Sent at the RLC Layer for B2H UEs in a Cell
Counters
1911816839 N.ThpVol.DL.B Volume of BTS3900, N

2H downlink data BTS3900 5G,
layer for B2H
UEs in a cell BTS5900 5G
Description
This counter measures the total volume of downlink data sent at the RLC layer for B2H UEs
in a cell.
Measurement Points
The SDU payload of downlink data sent at the RLC layer is accumulated for all B2H UEs in a
cell. The accumulation result is used as the counter value.
Formula
None
Unit
kbit
Related Features
None

1.2.20.10 Volume of Uplink Data Received at the RLC Layer for B2H UEs in a
Cell
Counters
1911816841 N.ThpVol.UL.B Volume of BTS3900, N

2H uplink data BTS3900 5G,
RLC layer for
B2H UEs in a BTS5900 5G
cell
Description
This counter measures the total volume of uplink data received at the RLC layer for B2H UEs
in a cell.
Measurement Points
The SDU payload of uplink data received at the RLC layer is accumulated for all B2H UEs in
a cell. The accumulation result is used as the counter value.
Formula
None
Unit
kbit
Related Features
None

1.2.20.11 Downlink Volume of RLC SDUs Sent in the Last Timeslot During
Which the Buffer Becomes Empty
Counters
1911816848 N.ThpVol.DL.L Downlink BTS3900, N

astSlot volume of RLC BTS3900 5G,
SDUs sent in BTS5900,
the last timeslot
during which BTS5900 5G
the buffer
becomes empty
Description
This counter measures the downlink volume of RLC SDUs sent in the last timeslot during
which the buffer becomes empty.
Measurement Points
The downlink volume of RLC SDUs sent in the last timeslot is accumulated for all QCIs in a
cell. The last timeslot is the one during which the DRB buffer becomes empty. The
Formula
None
Unit
kbit
Related Features
None

1.2.20.12 Data Transmission Duration Excluding the Last Timeslot During Which
the Downlink Buffer Becomes Empty
Counters
1911816850 N.ThpTime.DL. Data BTS3900, N

RmvLastSlot transmission BTS3900 5G,
duration BTS5900,
excluding the
last timeslot BTS5900 5G
during which
the downlink
buffer becomes
empty
Description
This counter measures the duration of data transmission excluding the last timeslot during
which the downlink buffer becomes empty.
Measurement Points
The duration of timeslots starting from the transmission of downlink data in the DRB buffer at
the RLC layer to the last timeslot is accumulated in a cell. The last timeslot is the one during
which the DRB buffer becomes empty. The accumulated duration excludes the last timeslot. If
retransmission and waiting occur, the counter value includes the retransmission and waiting
time.
Formula
None
Unit
microsecond
Related Features
None

1.2.20.13 Uplink Volume of Small Packets Received at the RLC Layer
Counters
1911816851 N.ThpVol.UE.U Uplink volume BTS3900, N

L.SmallPkt of small packets BTS3900 5G,
RLC layer
BTS5900 5G
Description
This counter measures the uplink volume of small packets received at the RLC layer in a cell.
Measurement Points
An uplink packet is considered as a small packet if it is received before the base station
receives a buffer status report (BSR), or if it is received by the base station when the uplink
buffer of the UE is empty, as indicated by the received BSR. The volume of these small
packets is accumulated at the RLC layer in a cell, and the accumulation result is used as the
counter value.
Formula
None
Unit
kbit
Related Features
None
1.2.20.14 Uplink Data Transmission Duration Excluding That of Small Packets
Counters
1911816853 N.ThpTime.UE. Uplink data BTS3900, N

UL.RmvSmallP transmission BTS3900 5G,
kt duration BTS5900,
excluding that
of small packets BTS5900 5G

Description
This counter measures the uplink data transmission duration excluding that of 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 becomes empty is measured. The measurement is performed based on
the value carried in the BSR received from the UE. The measurement result excludes the last
timeslot during which the uplink buffer of the UE becomes empty. If retransmission and
waiting occur, the counter value includes the retransmission and waiting time.
Formula
None
Unit
microsecond
Related Features
None
1.2.20.15 Duration of Correct Downlink Data Transmission Excluding the Last

Timeslot
Counters
1911816854 N.ThpTime.DL. Duration of BTS3900, N

Transfer.RmvL correct BTS3900 5G,
astSlot downlink data BTS5900,
transmission
excluding the BTS5900 5G
last timeslot
Description
This counter measures the duration of correct downlink data transmission at the RLC layer in
a cell. It excludes the last timeslot during which the buffer becomes empty.
Measurement Points
The value of this counter is incremented by the duration of a timeslot each time a DRB is
correctly transmitted and the buffer does not become empty in this timeslot. This counter is
measured based on all DRBs of UEs in a cell.

Formula
None
Unit
microsecond
Related Features
None
1.2.20.16 Duration of Correct Uplink Data Transmission Excluding That of Small

Packets
Counters
1911816855 N.ThpTime.UE. Duration of BTS3900, N

UL.Transfer.R correct uplink BTS3900 5G,
mvSmallPkt data BTS5900,
transmission
excluding that BTS5900 5G
of small packets
Description
This counter measures the duration of correct uplink data transmission at the RLC layer in a
cell. It excludes the last timeslot during which the buffer becomes empty.
Measurement Points
The value of this counter is incremented by the duration of a timeslot each time a DRB is
correctly transmitted and the buffer does not become empty in this timeslot. This counter is
measured based on all DRBs of UEs in a cell.
Formula
None
Unit
microsecond
Related Features
None

1.2.21 Cell Service Quality Measurement (QoS.Cell)

Overview
The QoS.Cell function subset measures the average SDU packet delays for DRB services at
the RLC and MAC layers.
Counters
1911816924 N.QoS.DL.PktDela Total delay of BTS3900:

ygNBDU.Time downlink packets V100R015C10
for DRB services BTS5900:
processed by the V100R015C10
gNodeB DU in a BTS5900 5G:
cell V100R015C10
1911816925 N.QoS.DL.PktDela Number of BTS3900:

yAirInterface.Num successfully V100R015C10
transmitted BTS5900:
downlink RLC V100R015C10
SDUs for DRB BTS5900 5G:
services over the Uu V100R015C10
interface in a cell
1911816926 N.QoS.DL.PktDela Total transmission BTS3900:

yAirInterface.Time delay of downlink V100R015C10
RLC SDUs for DRB BTS5900:
services over the Uu V100R015C10
interface in a cell BTS5900 5G:
V100R015C10
1911816927 N.QoS.DL.PktDela Total number of BTS3900:

ygNBDU.Num downlink RLC V100R015C10
SDUs for DRB BTS5900:
services processed V100R015C10
by the gNodeB DU BTS5900 5G:
in a cell V100R015C10
1911816930 N.Qos.DL.RlcFirst Total number of BTS3900:

PktDelay.Num downlink RLC V100R015C10
SDUs that enter the BTS5900:
empty buffer V100R015C10
BTS5900 5G:
V100R015C10


1911816931 N.Traffic.DL.RlcFi Total transmission BTS3900:

rstPktDelay.Time delay of the first V100R015C10
downlink RLC BTS5900:
SDUs for DRB V100R015C10
services in the BTS5900 5G:
empty buffer in a V100R015C10
cell
None
1.2.21.1 Total Delay of Downlink Packets for DRB Services Processed by the
gNodeB DU in a Cell
Counters
1911816924 N.QoS.DL.Pkt Total delay of BTS3900, N

DelaygNBDU. downlink BTS3900 5G,
Time packets for BTS5900,
DRB services
processed by BTS5900 5G
the gNodeB DU
in a cell
Description
This counter measures the delay of downlink RLC SDUs for DRB services successfully sent
by the gNodeB DU in a cell.
Measurement Points
This counter is the numerator used to calculate the average delay DL in gNB DU, as specified
in 3GPP TS 28.552. The total processing delay of all downlink RLC SDUs for DRB services
on the gNodeB DU is calculated in a measurement period. The delay measurement starts at
the time the RLC layer receives a data packet and ends at the time the last fragment of the
packet is delivered to the MAC layer.
Formula
None

Unit
microsecond
Related Features
None
1.2.21.2 Number of Successfully Transmitted Downlink RLC SDUs for DRB

Services over the Uu Interface in a Cell
Counters
1911816925 N.QoS.DL.Pkt Number of BTS3900, N

DelayAirInterfa successfully BTS3900 5G,
ce.Num transmitted BTS5900,
downlink RLC
SDUs for DRB BTS5900 5G
services over
the Uu interface
in a cell
Description
This counter measures the number of successfully transmitted downlink RLC SDUs for
services carried on DRBs over the Uu interface in a cell.
Measurement Points
In a measurement period, this counter is incremented by 1 each time the MAC layer receives a
HARQ ACK message after a fragment of RLC SDU or an RLC SDU is transmitted in the
downlink. The HARQ ACK message indicates that the fragment of RLC SDU or the RLC
SDU is successfully transmitted. According to what stipulated in TS 28.552, this counter is
the denominator of the formula used to calculate the average delay of the air interface in the
downlink.
Formula
None
Unit
None
Related Features
None

1.2.21.3 Total Transmission Delay of Downlink RLC SDUs for DRB Services over
the Uu Interface in a Cell
Counters
1911816926 N.QoS.DL.Pkt Total BTS3900, N

DelayAirInterfa transmission BTS3900 5G,
ce.Time delay of BTS5900,
downlink RLC
SDUs for DRB BTS5900 5G
services over
the Uu interface
in a cell
Description
This counter measures the total transmission delay of downlink RLC SDUs for services
carried on DRBs over the Uu interface in a cell.
Measurement Points
In a measurement period, the difference between the time that the MAC layer receives the last
fragment of RLC SDUs and the time that the MAC layer of the base station successfully
transmits an RLC SDU is measured. The measured value is accumulated and used as the
value of this counter. According to what stipulated in TS 28.552, this counter is the numerator
of the formula used to calculate the average delay of the air interface in the downlink.
Formula
None
Unit
microsecond
Related Features
None

1.2.21.4 Total Number of Downlink RLC SDUs for DRB Services Processed by
the gNodeB DU in a Cell
Counters
1911816927 N.QoS.DL.Pkt Total number of BTS3900, N

DelaygNBDU. downlink RLC BTS3900 5G,
Num SDUs for DRB BTS5900,
services
processed by BTS5900 5G
the gNodeB DU
in a cell
Description
This counter measures the total number of successfully transmitted downlink RLC SDUs for
services carried on DRBs in a DU cell.
Measurement Points
In a measurement period, this counter is incremented by 1 when the last fragment of RLC
SDUs for services carried on DRBs is transmitted to the MAC layer. According to what
stipulated in 3GPP TS 28.551, this counter is the denominator of the formula used to calculate
the average delay of the gNodeB DU in the downlink.
Formula
None
Unit
None
Related Features
None

1.2.21.5 Total Number of Downlink RLC SDUs That Are for DRB Services and
Enter the Empty Buffer in a Cell
Counters
1911816930 N.Qos.DL.RlcF Total number of BTS3900, N

irstPktDelay.Nu downlink RLC BTS3900 5G,
m SDUs that enter BTS5900,
the empty
buffer BTS5900 5G
Description
This counter measures the total number of downlink RLC SDUs that are for services carried
on DRBs and enter the empty buffer in a cell.
Measurement Points
In a measurement period, the counter is incremented by 1 each time a downlink RLC SDU
enters the empty buffer in a cell.
Formula
None
Unit
packet
Related Features
None

1.2.21.6 Total Transmission Delay of the First Downlink RLC SDUs for DRB
Services in the Empty Buffer in a Cell
Counters
1911816931 N.Traffic.DL.Rl Total BTS3900, N

cFirstPktDelay. transmission BTS3900 5G,
Time delay of the BTS5900,
first downlink
RLC SDUs for BTS5900 5G
DRB services
in the empty
buffer in a cell
Description
This counter measures the total transmission delay of downlink RLC SDUs that are for
services carried on DRBs and enter the empty buffer in a cell.
Measurement Points
In a measurement period, when the downlink RLC SDUs enter the empty buffer, the
difference between the time that the downlink RLC SDUs enter the empty buffer and the time
that the first RLC SDU of these RLC SDUs is transmitted over the Uu interface is measured.
The measured value is accumulated and used as this counter value.
Formula
None
Unit
microsecond
Related Features
None
1.2.22 Paging Measurement (Paging.Cell)
Overview
The Paging Measurement (Paging.Cell) function subset measures the number of times paging
messages are discarded due to PCH congestion and the number of paged UEs over the Uu
interface in a cell.

Counters
1911816891 N.Paging.Dis.PchC Number of paging BTS5900 5G:

ong messages discarded V100R015C10
due to PCH BTS5900:
congestion in a cell V100R015C10
BTS3900:
V100R015C10
1911817045 N.Paging.UU.Ue.N Number of paged BTS5900 5G:

um UEs over the Uu V100R015C10
V100R015C10
BTS5900:
V100R015C10
None
1.2.22.1 Paging in SA Networking
Counters
1911816891 N.Paging.Dis.P Number of BTS3900, N

chCong paging BTS3900 5G,
messages BTS5900,
discarded due
to PCH BTS5900 5G
congestion in a
cell
1911817045 N.Paging.UU.U Number of BTS3900, N

e.Num paged UEs over BTS3900 5G,
the Uu interface BTS5900,
in a cell
BTS5900 5G
Description
These counters measure the number of paging messages discarded due to PCH congestion and
number of paged UEs over the Uu interface in a cell in SA networking.

38.413.
Measurement Points
The first counter is incremented by one each time the gNodeB discards a paging message in a
cell because the paging traffic is so heavy that no storage space is available on the paging data
buffer.
The second counter is incremented based on the number of UEs paged via each paging
message transmitted over the Uu interface.
The counter values are accumulated in the cell where the UE camps.
Formula
None
Unit
None
Related Features
None
1.2.23 Random Access Measurement (RA.DuCell)
Overview
The random access procedure is classified into contention-based random access and non-
contention based random access. The Random Access Measurement (RA.DuCell) function
subset measures the number of preamble receptions separately for the two types of random
access procedures as well as the number of successful contention resolutions during
contention-based random access. It is used to analyze the load and success rate of random
access.
Counters
1911816542 N.RA.Contention.A Number of random BTS5900 5G:

tt preamble receptions V100R013C10
BTS5900:
V100R013C10
BTS3900:
V100R015C00


1911816543 N.RA.Contention.A Maximum number BTS5900 5G:

tt.Max of random preamble V100R013C10
receptions BTS5900:
V100R013C10
BTS3900:
V100R015C00
1911816544 N.RA.Contention.R Number of BTS5900 5G:

esolution.Succ successful V100R013C10
contention BTS5900:
resolutions V100R013C10
BTS3900:
V100R015C00
1911816545 N.RA.Dedicated.At Number of BTS5900 5G:

t dedicated preamble V100R013C10
receptions BTS5900:
V100R013C10
BTS3900:
V100R015C00
1911816546 N.RA.Dedicated.M Number of Msg3 BTS5900 5G:

sg3 receptions during V100R013C10
non-contention BTS5900:
based random access V100R013C10
BTS3900:
V100R015C00
1911817097 N.RA.TA.UE.Index Number of random BTS5900:

0 access times when V100R015C10
the TA values are in BTS5900 5G:
the range indicated V100R015C10
by index 0 BTS3900:
V100R015C10

by index 1 BTS3900:
V100R015C10

by index 2 BTS3900:
V100R015C10



by index 3 BTS3900:
V100R015C10

by index 4 BTS3900:
V100R015C10

by index 5 BTS3900:
V100R015C10

by index 6 BTS3900:
V100R015C10

by index 7 BTS3900:
V100R015C10

by index 8 BTS3900:
V100R015C10

by index 9 BTS3900:
V100R015C10



by index 10 BTS3900:
V100R015C10

V100R015C10

V100R015C10
None
1.2.23.1 Number of Random Preamble Receptions
Counters
1911816542 N.RA.Contenti Number of BTS3900, N

on.Att random BTS3900 5G,
preamble BTS5900,
receptions
BTS5900 5G
1911816543 N.RA.Contenti Maximum BTS3900, N

on.Att.Max number of BTS3900 5G,
random BTS5900,
preamble
receptions BTS5900 5G

Description
The counters measure the number of random preamble receptions. They indicate the load of
random preambles for contention-based random access in a cell.
Measurement Points
As shown at point A in Figure 1-101, the N.RA.Contention.Att counter is incremented by 1
each time the gNodeB receives a random preamble from a UE.
The number of times the gNodeB receives a random preamble is sampled per second. At the
end of a measurement period, the maximum of these samples is used as the value of the
N.RA.Contention.Att.Max counter.
Figure 1-101

Formula
None
Unit
None
Related Features
N.RA.Contention.Att Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.RA.Contention.Att.Max Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.2.23.2 Number of successful contention resolution delivery times
Counters
1911816544 N.RA.Contenti Number of BTS3900, N

on.Resolution.S successful BTS3900 5G,
ucc contention BTS5900,
resolutions
BTS5900 5G
Description
The counter measures the number of times the gNodeB successfully delivers the Contention
Resolution message during contention-based random access procedures. This counter is used
to evaluate the success rate of contention-based random access in a cell.
Measurement Points
As shown at point C in Figure 1-102, in a contention-based random access procedure, the
N.RA.Contention.Resolution.Succ counter is incremented by 1 each time the gNodeB

successfully delivers a Contention Resolution message to a UE performing contention-based

access.
Figure 1-102
Formula
None
Unit
None

Related Features
N.RA.Contention.Resolutio Multi-mode: None

n.Succ GSM: None
UMTS: None
LTE: None
1.2.23.3 Number of Dedicated Preamble Receptions
Counters
1911816545 N.RA.Dedicate Number of BTS3900, N

d.Att dedicated BTS3900 5G,
preamble BTS5900,
receptions
BTS5900 5G
Description
The counter measures the number of dedicated preamble receptions.
Measurement Points
As shown at point B in Figure 1-103, the N.RA.Dedicated.Att counter is incremented by 1
each time the gNodeB receives a dedicated preamble from a UE.

Figure 1-103
Formula
None
Unit
None
Related Features
N.RA.Dedicated.Att Multi-mode: None

GSM: None
UMTS: None
LTE: None

1.2.23.4 Number of Msg3 Receptions During Non-Contention Based Random

Access
Counters
1911816546 N.RA.Dedicate Number of BTS3900, N

d.Msg3 Msg3 BTS3900 5G,
receptions BTS5900,
during non-
contention BTS5900 5G
based random
access
Description
The counter measures the number of Msg3 receptions during non-contention based random
access. This counter is used to evaluate the success rate of non-contention based random
access.
Measurement Points
As shown at point D in Figure 1-104, the N.RA.Dedicated.Msg3 counter is incremented by 1
each time the gNodeB receives Msg3 from a UE during non-contention based random access.
Figure 1-104

Formula
None
Unit
None
Related Features
N.RA.Dedicated.Msg3 Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.2.23.5 Number of Random Access Times When the TA Values are in a Range in
a Cell
Counters
1911817097 N.RA.TA.UE.In Number of BTS3900, N

dex0 random access BTS3900 5G,
times when the BTS5900,
TA values are
in the range BTS5900 5G
indicated by
index 0

TA values are
indicated by
index 1

TA values are
indicated by
index 2



TA values are
indicated by
index 3

TA values are
indicated by
index 4

TA values are
indicated by
index 5

TA values are
indicated by
index 6

TA values are
indicated by
index 7

TA values are
indicated by
index 8



TA values are
indicated by
index 9

TA values are
indicated by
index 10

TA values are
indicated by
index 11

TA values are
indicated by
index 12
Description
These counters measure the number of random access times when the TA values indicated in
random access responses are in a specific range. TA indicates the index of the timing advance.
The value range is 0-3846. For details, see 3GPP TS 38.213. The TA ranges are indicated by
indexes 0 to 12:
Index 0: [0, 1]
Index 1: [2, 3]
Index 2: [4, 7]
Index 3: [8, 13]
Index 4: [14, 25]
Index 5: [26, 45]
Index 6: [46, 85]

Index 7: [86, 185]
Index 8: [186, 385]
Index 9: [386, 785]
Index 10: [786, 1485]
Index 11: [1486, 2585]
Index 12: [2586, +∞)
Measurement Points
The corresponding counter is incremented by 1 based on the TA value each time the gNodeB
receives the first uplink data with a correct CRC result after receiving a random access
preamble from a UE and sending a random access response to the UE. The TA value is
indicated in the random access response.
Formula
None
Unit
None
Related Features
N.RA.TA.UE.Index0 Multi-mode: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None


GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None


GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None

GSM: None
UMTS: None
LTE: None
1.3 Measurement of gNodeB Performance (gNodeB)

Overview
The gNodeB measurement object contains gNodeB-level function subsets, which indicate the
operating status of gNodeBs.
FunctionSubSets
Traffic.TRPIP.gNodeB gNodeB Transmission Interface

Measurement(Traffic.TRPIP.gNodeB)
CallAtt.gNodeB gNodeB Call Processing

Times(CallAtt.gNodeB)
User.gNodeB gNodeB User Quantity Measurement

(User.gNodeB)
Algo.gNodeB gNodeB Algorithm

Measurement(Algo.gNodeB)

1.3.1 gNodeB Transmission Interface Measurement

(Traffic.TRPIP.gNodeB)
Overview
The gNodeB Transmission Interface Measurement(Traffic.TRPIP.gNodeB) function subset
measures the traffic and transmission rates of the user planes over different interfaces on a
gNodeB.
Counters
1911816492 N.TRPIP.gNB.X2U Average transmit BTS5900 5G:

TxMeanSpeed rate of the X2-U V100R013C10
interface on a BTS5900:
gNodeB V100R013C10
BTS3900:
V100R015C00
1911816493 N.TRPIP.gNB.X2U Maximum transmit BTS5900 5G:

TxMaxSpeed rate of the X2-U V100R013C10
gNodeB V100R013C10
BTS3900:
V100R015C00
1911816494 N.TRPIP.gNB.X2U Average receive rate BTS5900 5G:

RxMeanSpeed of the X2-U V100R013C10
gNodeB V100R013C10
BTS3900:
V100R015C00
1911816495 N.TRPIP.gNB.X2U Maximum receive BTS5900 5G:

RxMaxSpeed rate of the X2-U V100R013C10
gNodeB V100R013C10
BTS3900:
V100R015C00
1911816496 N.TRPIP.gNB.X2U Total amount of BTS5900 5G:

TxBytes traffic transmitted V100R013C10
over the X2-U BTS5900:
interface on a V100R013C10
gNodeB BTS3900:
V100R015C00


1911816497 N.TRPIP.gNB.X2U Total amount of BTS5900 5G:

RxBytes traffic received over V100R013C10
the X2-U interface BTS5900:
on a gNodeB V100R013C10
BTS3900:
V100R015C00
1911816504 N.TRPIP.gNB.S1U Average transmit BTS5900 5G:

TxMeanSpeed rate of the S1-U V100R013C10
gNodeB V100R013C10
BTS3900:
V100R015C00
1911816505 N.TRPIP.gNB.S1U Maximum transmit BTS5900 5G:

TxMaxSpeed rate of the S1-U V100R013C10
gNodeB V100R013C10
BTS3900:
V100R015C00
1911816506 N.TRPIP.gNB.S1U Average receive rate BTS5900 5G:

RxMeanSpeed of the S1-U interface V100R013C10
on a gNodeB BTS5900:
V100R013C10
BTS3900:
V100R015C00
1911816507 N.TRPIP.gNB.S1U Maximum receive BTS5900 5G:

RxMaxSpeed rate of the S1-U V100R013C10
gNodeB V100R013C10
BTS3900:
V100R015C00
1911816508 N.TRPIP.gNB.S1U Total amount of BTS5900 5G:

TxBytes traffic transmitted V100R013C10
over the S1-U BTS5900:
interface on a V100R013C10
gNodeB BTS3900:
V100R015C00
1911816509 N.TRPIP.gNB.S1U Total amount of BTS5900 5G:

RxBytes traffic received over V100R013C10
the S1-U interface BTS5900:
BTS3900:
V100R015C00


1911817006 N.TRPIP.gNB.XnU Maximum receive BTS3900:

RxMaxSpeed rate of the Xn-U V100R015C10
gNodeB V100R015C10
BTS5900 5G:
V100R015C10
1911817007 N.TRPIP.gNB.XnU Maximum transmit BTS3900:

TxMaxSpeed rate of the Xn-U V100R015C10
gNodeB V100R015C10
BTS5900 5G:
V100R015C10
1911817008 N.TRPIP.gNB.XnU Average transmit BTS3900:

TxMeanSpeed rate of the Xn-U V100R015C10
gNodeB V100R015C10
BTS5900 5G:
V100R015C10
1911817009 N.TRPIP.gNB.XnU Average receive rate BTS3900:

RxMeanSpeed of the Xn-U V100R015C10
gNodeB V100R015C10
BTS5900 5G:
V100R015C10
1911817010 N.TRPIP.gNB.NG Maximum receive BTS3900:

URxMaxSpeed rate of the NG-U V100R015C10
gNodeB V100R015C10
BTS5900 5G:
V100R015C10
1911817011 N.TRPIP.gNB.NG Maximum transmit BTS3900:

UTxMaxSpeed rate of the NG-U V100R015C10
gNodeB V100R015C10
BTS5900 5G:
V100R015C10
1911817012 N.TRPIP.gNB.NG Average receive rate BTS3900:

URxMeanSpeed of the NG-U V100R015C10
gNodeB V100R015C10
BTS5900 5G:
V100R015C10


1911817013 N.TRPIP.gNB.NG Average transmit BTS3900:

UTxMeanSpeed rate of the NG-U V100R015C10
gNodeB V100R015C10
BTS5900 5G:
V100R015C10
1911817014 N.TRPIP.gNB.XnU Total amount of BTS3900:

TxBytes traffic transmitted on V100R015C10
the Xn-U interface BTS5900:
BTS5900 5G:
V100R015C10
1911817015 N.TRPIP.gNB.XnU Total amount of BTS3900:

RxBytes traffic received on V100R015C10
the Xn-U interface BTS5900:
BTS5900 5G:
V100R015C10
1911817016 N.TRPIP.gNB.NG Total amount of BTS3900:

URxBytes traffic received on V100R015C10
the NG-U interface BTS5900:
BTS5900 5G:
V100R015C10
1911817017 N.TRPIP.gNB.NG Total amount of BTS3900:

UTxBytes traffic transmitted on V100R015C10
the NG-U interface BTS5900:
BTS5900 5G:
V100R015C10
None

1.3.1.1 Transmit and Receive Rates of the X2-U Interface on a gNodeB
Counters
1911816492 N.TRPIP.gNB. Average BTS3900, N

X2UTxMeanSp transmit rate of BTS3900 5G,
eed the X2-U BTS5900,
interface on a
gNodeB BTS5900 5G
1911816493 N.TRPIP.gNB. Maximum BTS3900, N

X2UTxMaxSpe transmit rate of BTS3900 5G,
ed the X2-U BTS5900,
interface on a
gNodeB BTS5900 5G
1911816494 N.TRPIP.gNB. Average receive BTS3900, N

X2URxMeanSp rate of the X2- BTS3900 5G,
eed U interface on a BTS5900,
gNodeB
BTS5900 5G

X2URxMaxSpe receive rate of BTS3900 5G,
ed the X2-U BTS5900,
interface on a
gNodeB BTS5900 5G
Description
These counters measure the maximum and average transmit and receive rates at the IP layer
of the X2-U interface on a gNodeB. When the gNodeB X2 and Xn interfaces share the user-
plane local IP address, the user-plane rate of the gNodeB X2 interface also includes the user-
plane rate of the gNodeB Xn interface.
Measurement Points
The transmit and receive rates of the X2-U interface on a gNodeB are sampled at the IP layer
every 10s. At the end of a measurement period, the maximum and average of these sampling
results are used as the values of the corresponding counters.
Formula
None
Unit
kbit/s

Related Features
N.TRPIP.gNB.X2UTxMean Multi-mode: MRFD-131161 LTE and NR X2 Interface

Speed GSM: None Self-Configuration (NR)
UMTS: None
LTE: None
NR: None
N.TRPIP.gNB.X2UTxMaxS Multi-mode: MRFD-131161 LTE and NR X2 Interface

peed GSM: None Self-Configuration (NR)
UMTS: None
LTE: None
NR: None
N.TRPIP.gNB.X2URxMean Multi-mode: MRFD-131161 LTE and NR X2 Interface

UMTS: None
LTE: None
NR: None
N.TRPIP.gNB.X2URxMaxS Multi-mode: MRFD-131161 LTE and NR X2 Interface

UMTS: None
LTE: None
NR: None
1.3.1.2 Traffic Transmitted and Received over the X2-U Interface on a gNodeB
Counters
1911816496 N.TRPIP.gNB. Total amount of BTS3900, N

X2UTxBytes traffic BTS3900 5G,
transmitted over BTS5900,
the X2-U
interface on a BTS5900 5G
gNodeB



X2URxBytes traffic received BTS3900 5G,
over the X2-U BTS5900,
interface on a
gNodeB BTS5900 5G
Description
These counters measure the traffic transmitted and received over the X2-U interface on a
gNodeB. If packets need to be fragmented, the transmitted traffic is measured before
fragmentation, and received traffic is measured after reassembly. If packets need to be
encrypted using IPsec, the transmitted traffic is measured before encryption, and the received
traffic is measured after decryption. When the gNodeB X2 and Xn interfaces share the user-
plane local IP address, the user-plane traffic of the gNodeB X2 interface also includes the
user-plane traffic of the gNodeB Xn interface.
Measurement Points
The amounts of traffic transmitted and received at the IP layer of the X2-U interface on a
gNodeB are sampled every 10s. At the end of a measurement period, the total amounts of
Formula
None
Unit
kbit
Related Features
N.TRPIP.gNB.X2UTxBytes Multi-mode: MRFD-131161 LTE and NR X2 Interface

GSM: None Self-Configuration (NR)
UMTS: None
LTE: None
NR: None

N.TRPIP.gNB.X2URxBytes Multi-mode: MRFD-131161 LTE and NR X2 Interface

UMTS: None
LTE: None
NR: None
1.3.1.3 Transmit and Receive Rates of the S1-U Interface on a gNodeB
Counters
1911816504 N.TRPIP.gNB.S Average BTS3900, N

1UTxMeanSpe transmit rate of BTS3900 5G,
ed the S1-U BTS5900,
interface on a
gNodeB BTS5900 5G
1911816505 N.TRPIP.gNB.S Maximum BTS3900, N

1UTxMaxSpee transmit rate of BTS3900 5G,
d the S1-U BTS5900,
interface on a
gNodeB BTS5900 5G
1911816506 N.TRPIP.gNB.S Average receive BTS3900, N

1URxMeanSpe rate of the S1-U BTS3900 5G,
ed interface on a BTS5900,
gNodeB
BTS5900 5G
1911816507 N.TRPIP.gNB.S Maximum BTS3900, N

1URxMaxSpee receive rate of BTS3900 5G,
d the S1-U BTS5900,
interface on a
gNodeB BTS5900 5G
Description
These counters measure the maximum and average transmit and receive rates at the IP layer
of the S1-U interface on a gNodeB.

Measurement Points
The transmit and receive rates of the S1-U interface on a gNodeB are sampled at the IP layer
every 10s. At the end of a measurement period, the maximum and average of these sampling
Formula
None
Unit
kbit/s
Related Features
N.TRPIP.gNB.S1UTxMean Multi-mode: MRFD-131161 LTE and NR X2 Interface

UMTS: None
LTE: None
NR: None
N.TRPIP.gNB.S1UTxMaxS Multi-mode: MRFD-131161 LTE and NR X2 Interface

UMTS: None
LTE: None
NR: None
N.TRPIP.gNB.S1URxMean Multi-mode: MRFD-131161 LTE and NR X2 Interface

UMTS: None
LTE: None
NR: None
N.TRPIP.gNB.S1URxMaxS Multi-mode: MRFD-131161 LTE and NR X2 Interface

UMTS: None
LTE: None
NR: None

1.3.1.4 Traffic Transmitted and Received over the S1-U Interface on a gNodeB
Counters
1911816508 N.TRPIP.gNB.S Total amount of BTS3900, N

1UTxBytes traffic BTS3900 5G,
transmitted over BTS5900,
the S1-U
gNodeB
1911816509 N.TRPIP.gNB.S Total amount of BTS3900, N

1URxBytes traffic received BTS3900 5G,
over the S1-U BTS5900,
interface on a
gNodeB BTS5900 5G
Description
These counters measure the traffic transmitted and received over the S1-U interface on a
gNodeB. If packets need to be fragmented, the transmitted traffic is measured before
traffic is measured after decryption.
Measurement Points
The amounts of traffic transmitted and received at the IP layer of the S1-U interface on a
Formula
None
Unit
kbit

Related Features
N.TRPIP.gNB.S1UTxBytes Multi-mode: MRFD-131161 LTE and NR X2 Interface

UMTS: None
LTE: None
NR: None
N.TRPIP.gNB.S1URxBytes Multi-mode: MRFD-131161 LTE and NR X2 Interface

UMTS: None
LTE: None
NR: None
1.3.1.5 Transmit and Receive Rates of the Xn-U Interface on a gNodeB
Counters

XnURxMaxSpe receive rate of BTS3900 5G,
ed the Xn-U BTS5900,
interface on a
gNodeB BTS5900 5G

XnUTxMaxSpe transmit rate of BTS3900 5G,
ed the Xn-U BTS5900,
interface on a
gNodeB BTS5900 5G

XnUTxMeanSp transmit rate of BTS3900 5G,
eed the Xn-U BTS5900,
interface on a
gNodeB BTS5900 5G

XnURxMeanSp rate of the Xn- BTS3900 5G,
eed U interface on a BTS5900,
gNodeB
BTS5900 5G

Description
The counters measure the maximum and average transmit and receive rates at the IP layer of
the Xn-U interface on a gNodeB. When the gNodeB Xn and X2 interfaces share the user-
plane local IP address, the user-plane rate of the gNodeB Xn interface also includes the user-
plane rate of the gNodeB X2 interface.
Measurement Points
The transmit and receive rates of an Xn-U interface on a gNodeB are sampled at the IP layer
per 10s. At the end of a measurement period, the average and maximum of these sampling
Formula
None
Unit
kbit/s
Related Features
None
1.3.1.6 Transmit and Receive Rates of the NG-U Interface on a gNodeB
Counters

NGURxMaxSp receive rate of BTS3900 5G,
eed the NG-U BTS5900,
interface on a
gNodeB BTS5900 5G

NGUTxMaxSp transmit rate of BTS3900 5G,
eed the NG-U BTS5900,
interface on a
gNodeB BTS5900 5G

NGURxMeanS rate of the NG- BTS3900 5G,
peed U interface on a BTS5900,
gNodeB
BTS5900 5G



NGUTxMeanS transmit rate of BTS3900 5G,
peed the NG-U BTS5900,
interface on a
gNodeB BTS5900 5G
Description
The counters measure the maximum and average transmit and receive rates at the IP layer of
the NG-U interface on a gNodeB.
Measurement Points
The transmit and receive rates of an NG-U interface on a gNodeB are sampled at the IP layer
per 10s. At the end of a measurement period, the average and maximum of these sampling
Formula
None
Unit
kbit/s
Related Features
None
1.3.1.7 Traffic Transmitted and Received over the Xn-U Interface on a gNodeB
Counters

XnUTxBytes traffic BTS3900 5G,
the Xn-U
gNodeB



XnURxBytes traffic received BTS3900 5G,
on the Xn-U BTS5900,
interface on a
gNodeB BTS5900 5G
Description
These counters measure the traffic transmitted and received at the IP layer on the Xn-U
interface on a gNodeB. If packets need to be fragmented, the transmitted traffic is measured
before fragmentation, and received traffic is measured after reassembly. If packets need to be
traffic is measured after decryption. When the gNodeB Xn and X2 interfaces share the user-
plane local IP address, the user-plane traffic of the gNodeB Xn interface also includes the
user-plane traffic of the gNodeB X2 interface.
Measurement Points
The amounts of traffic transmitted and received at the IP layer of the Xn-U interface on a
Formula
None
Unit
kbit
Related Features
None
1.3.1.8 Traffic Transmitted and Received over the NG-U Interface on a gNodeB
Counters

NGURxBytes traffic received BTS3900 5G,
on the NG-U BTS5900,
interface on a
gNodeB BTS5900 5G



NGUTxBytes traffic BTS3900 5G,
the NG-U
gNodeB
Description
The counters measure the traffic transmitted and received at the IP layer on the NG-U
interface on a gNodeB. If packets need to be fragmented, the transmitted traffic is measured
before fragmentation, and received traffic is measured after reassembly. If packets need to be
traffic is measured after decryption.
Measurement Points
The amounts of traffic transmitted and received at the IP layer of the NG-U interface on a
Formula
None
Unit
kbit
Related Features
None
1.3.2 gNodeB Call Processing Times (CallAtt.gNodeB)

Overview
The gNodeB Call Processing Times (CallAtt.gNodeB) function subset measures the number
of calls processed by the gNodeB. It indicates the signaling traffic processed by the gNodeB.

Counters
1911816769 N.SIG.gNB.CallAtt Number of call BTS5900 5G:

processing times in a V100R015C00
gNodeB BTS5900:
V100R015C00
BTS3900:
V100R015C00
1911816770 N.SIG.gNB.CallAtt Maximum number BTS5900 5G:

.Max of call processing V100R015C00
times in a gNodeB BTS5900:
V100R015C00
BTS3900:
V100R015C00
None
1.3.2.1 gNodeB Call Processing Times
Counters
1911816769 N.SIG.gNB.Cal Number of call BTS3900, N

lAtt processing BTS3900 5G,
times in a BTS5900,
gNodeB
BTS5900 5G
1911816770 N.SIG.gNB.Cal Maximum BTS3900, N

lAtt.Max number of call BTS3900 5G,
processing BTS5900,
times in a
gNodeB BTS5900 5G
Description
These counters measure the number of calls processed by a gNodeB, which reflects the traffic
volume of signaling messages processed by the gNodeB.

Measurement Points
The gNodeB regards that a call access is performed if it has completed any of the following
message interactions:
1. The NGC sends an INITIAL CONTEXT SETUP REQUEST message, and the gNodeB
replies with an INITIAL CONTEXT SETUP RESPONSE message.
2. In NSA networking, the MeNB sends an SGNB ADDITION REQUEST message
(excluding SgNB UE X2AP ID), and the gNodeB replies with an SGNB ADDITION
REQUEST ACKNOWLEDGE message.
3. The MgNB sends an S-NODE ADDITION REQUEST message (excluding S-NG-RAN
node UE XnAP ID), and the gNodeB replies with an S-NODE ADDITION REQUEST
ACKNOWLEDGE message.
4. The NGC sends a HANDOVER REQUEST message, and the gNodeB replies with a
HANDOVER REQUEST ACKNOWLEDGE message.
5. A neighboring gNodeB sends a HANDOVER REQUEST message, and the gNodeB replies
with a HANDOVER REQUEST ACKNOWLEDGE message.
The gNodeB accumulates the number of call access times within a measurement period and
takes the value as the N.SIG.gNB.CallAtt counter value. In a measurement period, the
gNodeB uses the maximum number of calls processed within 1 second as the value of the
N.SIG.gNB.CallAtt.Max counter.
Formula
None
Unit
None
Related Features
None
1.3.3 gNodeB User Quantity Measurement (User.gNodeB)

Overview
The User.gNodeB function subset measures the maximum number of UEs in
RRC_CONNECTED mode under a gNodeB.

Counters
1911816929 N.User.gNodeB.RR Maximum number BTS3900:

CConn.Max of UEs in V100R015C10
D mode under a V100R015C10
gNodeB BTS5900 5G:
V100R015C10
None
1.3.3.1 Number of UEs Under gNodeB
Counters
1911816929 N.User.gNodeB Maximum BTS3900, N

.RRCConn.Max number of UEs BTS3900 5G,
in BTS5900,
RRC_CONNE
CTED mode BTS5900 5G
under a
gNodeB
Description
This counter measures the maximum number of UEs in RRC_CONNECTED mode under a
gNodeB.
Measurement Points
of UEs in RRC_CONNECTED mode under a gNodeB is sampled per second. At the end of a
measurement period, the maximum of these sampling results is taken as the counter value. For
DC users, one user is counted for each of the master base station and the secondary base
station.
Formula
None

Unit
None
Related Features
None
1.3.4 gNodeB Algorithm Measurement (Algo.gNodeB)
Overview
The gNodeB Algorithm Measurement (Algo.gNodeB) function subset measures the number
of times a gNodeB becomes unavailable and the duration of gNodeB unavailability.
Counters
1911816768 N.gNB.Unavail.Dur Duration of gNodeB BTS5900 5G:

unavailability V100R015C00
BTS5900:
V100R015C00
BTS3900:
V100R015C00
None
1.3.4.1 gNodeB Unavailability Duration
Counters
1911816768 N.gNB.Unavail. Duration of BTS3900, N

Dur gNodeB BTS3900 5G,
unavailability BTS5900,
BTS5900 5G
Description
The counter measures the duration in which a gNodeB is unavailable. If all cells served by the
gNodeB are out of service, the gNodeB is regarded as unavailable.

Measurement Points
The gNodeB status is sampled per five seconds. If the status of all cells served by the gNodeB
are unavailable at a sampling point, the counter is incremented by 5s. A deviation of one
sampling period may be caused when the timer performs time synchronization. As a result, a
deviation of one sampling period will also be generated in the counter value. If the gNodeB is
unavailable because, for example, the gNodeB or the RANCU is powered off, the counter
value does not increase.
Formula
None
Unit
s
Related Features
None
1.4 Measurement of gNodeB DU Logical Node

Performance (gNBDU)
Overview
The gNBDU measurement object contains function subsets related to gNodeB distributed
units (DUs). These function subsets indicate the operating status of gNodeB DUs.
FunctionSubSets
Traffic.TRPIP.gNBDU gNBDU Transmission Interface

Measurement(Traffic.TRPIP.gNBDU)
1.4.1 gNBDU Transmission Interface Measurement

(Traffic.TRPIP.gNBDU)
Overview
The gNBDU Transmission Interface Measurement(Traffic.TRPIP.gNBDU) function subset
measures the traffic and transmission rates of the user planes over different interfaces on a
gNodeB DU.

Counters
1911816783 N.TRPIP.gNBDU.F Average transmit BTS5900 5G:

1UTxMeanSpeed rate of the F1-U V100R015C00
gNodeB DU V100R015C00
BTS3900:
V100R015C00
1911816784 N.TRPIP.gNBDU.F Maximum transmit BTS5900 5G:

1UTxMaxSpeed rate of the F1-U V100R015C00
BTS3900:
V100R015C00
1911816785 N.TRPIP.gNBDU.F Average receive rate BTS5900 5G:

1URxMeanSpeed of the F1-U interface V100R015C00
on a gNodeB DU BTS5900:
V100R015C00
BTS3900:
V100R015C00
1911816786 N.TRPIP.gNBDU.F Maximum receive BTS5900 5G:

1URxMaxSpeed rate of the F1-U V100R015C00
BTS3900:
V100R015C00
1911816787 N.TRPIP.gNBDU.F Total amount of BTS5900 5G:

1UTxBytes traffic transmitted on V100R015C00
the F1-U interface BTS5900:
on a gNodeB DU V100R015C00
BTS3900:
V100R015C00
1911816788 N.TRPIP.gNBDU.F Total amount of BTS5900 5G:

1URxBytes traffic received on V100R015C00
the F1-U interface BTS5900:
on a gNodeB DU V100R015C00
BTS3900:
V100R015C00
None

1.4.1.1 Transmit and Receive Rates of the F1-U Interface on a gNodeB DU
Counters
1911816783 N.TRPIP.gNBD Average BTS3900, N

U.F1UTxMean transmit rate of BTS3900 5G,
Speed the F1-U BTS5900,
interface on a
gNodeB DU BTS5900 5G
1911816784 N.TRPIP.gNBD Maximum BTS3900, N

U.F1UTxMaxS transmit rate of BTS3900 5G,
peed the F1-U BTS5900,
interface on a
1911816785 N.TRPIP.gNBD Average receive BTS3900, N

U.F1URxMean rate of the F1-U BTS3900 5G,
Speed interface on a BTS5900,
gNodeB DU
BTS5900 5G
1911816786 N.TRPIP.gNBD Maximum BTS3900, N

U.F1URxMaxS receive rate of BTS3900 5G,
peed the F1-U BTS5900,
interface on a
Description
These counters measure the average and maximum transmit and receive rates at the IP layer
of the F1-U interface on a gNodeB DU.
Measurement Points
The transmit and receive rates of an F1-U interface on a gNodeB DU are sampled at the IP
layer per 10s. 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
kbit/s
Related Features
None

1.4.1.2 Traffic Transmitted and Received on the F1-U Interface on a gNodeB DU
Counters
1911816787 N.TRPIP.gNBD Total amount of BTS3900, N

U.F1UTxBytes traffic BTS3900 5G,
the F1-U
gNodeB DU
1911816788 N.TRPIP.gNBD Total amount of BTS3900, N

U.F1URxBytes traffic received BTS3900 5G,
on the F1-U BTS5900,
interface on a
Description
These counters measure the traffic transmitted and received on the F1-U interface on a
gNodeB DU. If packets need to be fragmented, the transmitted traffic is measured before
packets are measured after decryption.
Measurement Points
The amounts of traffic transmitted and received at the IP layer of the F1-U interface on a
gNodeB DU are sampled per 10s. At the end of a measurement period, the total amounts of
Formula
None
Unit
kbit
Related Features
None

1.5 Measurement of NSA DU Cell QCI Performance

(NRDUCELL.NSAQCI)
Overview
The NRDUCELL.NSAQCI measurement object measures the QCI performance of DU cells
in NSA networking. You can activate the required QCI measurement objects via the
gNBQciBearer.CounterObjSubscriptionInd parameter.
FunctionSubSets
User.DuCell.QCI DU Cell QCI User Number Measurement

(User.DuCell.QCI)
Thp.DuCell.QCI QCI Throughput Measurement

(Thp.DuCell.QCI)
1.5.1 DU Cell QCI User Number Measurement (User.DuCell.QCI)
Overview
The DU Cell QCI User Number Measurement (User.DuCell.QCI) function subset measures
the number of active NSA users in a DU cell.
Counters
1911817085 N.User.RRCConn. Maximum number BTS3900:

Active.QCI.Max of active QCI users V100R015C10
in NSA networking BTS5900:
V100R015C10
BTS5900 5G:
V100R015C10
1911817086 N.User.RRCConn. Average number of BTS3900:

Active.QCI.Avg active QCI users in V100R015C10
NSA networking BTS5900:
V100R015C10
BTS5900 5G:
V100R015C10

None
1.5.1.1 Number of Active Users in NSA Networking
Counters

nn.Active.QCI. number of BTS3900 5G,
Max active QCI BTS5900,
users in NSA
networking BTS5900 5G

nn.Active.QCI. number of BTS3900 5G,
Avg active QCI BTS5900,
users in NSA
networking BTS5900 5G
Description
These counters measure the number of UEs that have data buffered in NSA networking.
Measurement Points
RRC_CONNECTED UEs that have bearers of a certain QCI type and have data in the
downlink buffer in a cell is sampled every 100 ms. At the end of a measurement period, the
average and maximum of these sampling results are used as the values of the corresponding
counters.
UL and DL Decoupling takes effect, the counter is measured only in the NUL DU cell.
Formula
None
Unit
None
Related Features
None

1.5.2 QCI Throughput Measurement (Thp.DuCell.QCI)

Overview
The QCI Throughput Measurement (Thp.DuCell.QCI) function subset measures the
throughput and data transmission duration of uplink and downlink services of NSA UEs in a
DU cell.
Counters
1911817047 N.ThpVol.DL.QCI Total volume of BTS5900 5G:

downlink data V100R015C10
carried on NSA UE BTS5900:
bearers sent at the V100R015C10
RLC layer BTS3900:
V100R015C10
1911817050 N.ThpVol.DL.Last Downlink volume of BTS5900 5G:

Slot.QCI RLC SDUs sent in V100R015C10
buffer becomes BTS3900:
empty for bearers of V100R015C10
NSA UEs
1911817051 N.ThpTime.DL.Rm Data transmission BTS5900 5G:

vLastSlot.QCI duration for QCI V100R015C10
bearers excluding BTS5900:
the last timeslot V100R015C10
during which the BTS3900:
downlink buffer V100R015C10
becomes empty
None

1.5.2.1 Volume of Downlink Data Sent at the RLC Layer in a Cell in NSA
Networking
Counters
1911817047 N.ThpVol.DL.Q Total volume of BTS3900, N

CI downlink data BTS3900 5G,
carried on NSA BTS5900,
UE bearers sent
at the RLC BTS5900 5G
layer
Description
This counter measures the total volume of downlink SDUs sent at the RLC layer carried on
the subscribed bearers of all NSA UEs in a DU cell.
Measurement Points
The volume of downlink SDUs sent at the RLC layer carried on the subscribed bearers of all
NSA UEs in a DU cell is measured and accumulated in the N.ThpVol.DL.QCI counter value.
Formula
None
Unit
kbit
Related Features
N.ThpVol.DL.QCI Multi-mode: None

GSM: None
UMTS: None
LTE: None
NR: FBFD-020102 Radio QoS Management

1.5.2.2 Downlink Volume of RLC SDUs Sent in the Last Timeslot During Which
the Buffer Becomes Empty in NSA Networking
Counters
1911817050 N.ThpVol.DL.L Downlink BTS3900, N

astSlot.QCI volume of RLC BTS3900 5G,
SDUs sent in BTS5900,
the last timeslot
during which BTS5900 5G
the buffer
becomes empty
for bearers of
NSA UEs
Description
This counter measures the downlink volume of RLC SDUs sent in the last timeslot during
which the buffer becomes empty for the subscribed bearers of all NSA UEs in a DU cell.
Measurement Points
The downlink volume of RLC SDUs sent in the last timeslot during which the buffer becomes
empty for the subscribed bearers of all NSA UEs in a DU cell is measured and accumulated in
the N.ThpVol.DL.LastSlot.QCI counter value.
Formula
None
Unit
kbit
Related Features
N.ThpVol.DL.LastSlot.QCI Multi-mode: None

GSM: None
UMTS: None
LTE: None

1.5.2.3 Data Transmission Duration Excluding the Last Timeslot During Which
the Downlink Buffer Becomes Empty in NSA Networking
Counters
1911817051 N.ThpTime.DL. Data BTS3900, N

RmvLastSlot.Q transmission BTS3900 5G,
CI duration for BTS5900,
QCI bearers
excluding the BTS5900 5G
last timeslot
during which
the downlink
buffer becomes
empty
Description
This counter measures the duration of data transmission excluding the last timeslot during
which the downlink buffer becomes empty for the subscribed bearers of all NSA UEs in a DU
cell.
Measurement Points
The duration of timeslots starting from the transmission of downlink data in the DRB buffer at
the RLC layer to the last timeslot is accumulated for the subscribed bearers of all NSA UEs in
a DU cell. The last timeslot is the one during which the DRB buffer becomes empty. The
accumulated duration excludes the last timeslot. If retransmission and waiting occur, the
counter value includes the retransmission and waiting time.
Formula
None
Unit
microsecond

Related Features
N.ThpTime.DL.RmvLastSlo Multi-mode: None

t.QCI GSM: None
UMTS: None
LTE: None
1.6 Measurement of Neighboring NR Cell Performance

(NRCellRelation)
Overview
The Measurement of Neighboring NR Cell Performance (NRCellRelation) object type
measures the number of intra-NR handovers between two specific cells. It reflects the
handover performance of specific cells. You can manually subscribe to and activate the
required measurement objects of two specific cells on the EMS. The default specifications of
this measurement object are 384. If the gNodeB is configured with the UMPT, the
specifications of this measurement object can be improved on the EMS. The UMPTe and
UMPTg support a maximum of 2304 measurement objects. The base station uploads
configuration data to the U2020 background database. The U2020 synchronizes base station
configuration data from the background database and delivers neighboring cell measurement
objects. The base station activates neighboring cell measurement objects according to the
sequence they are delivered by the U2020. When the number of neighboring cells configured
for a site exceeds the maximum specifications N (N = 384 or 2304) of this measurement
object, only N measurement objects can be activated. The activated measurement objects do
not change unless the configuration changes.
FunctionSubSets
HO.NRCellRelation.Out.Cell Intra-NR Inter-Cell Outgoing Handover

Measurement
(HO.NRCellRelation.Out.Cell)
1.6.1 Intra-NR Inter-Cell Outgoing Handover Measurement

(HO.NRCellRelation.Out.Cell)
Overview
The HO.NRCellRelation.Out.Cell function subset measures the performance of intra-NR
outgoing handovers between two specific cells.

Counters
1911817030 N.HO.NCell.ExecS Number of BTS5900 5G:

uccOut successful intra-NR V100R015C00
outgoing handovers
between two
specific cells
1911817031 N.HO.NCell.PrepA Number of intra-NR BTS5900 5G:

ttOut outgoing handover V100R015C00
attempts between
two specific cells
1911817032 N.HO.NCell.ExecA Number of intra-NR BTS5900 5G:

ttOut outgoing handover V100R015C00
executions between
two specific cells
None
1.6.1.1 Number of Intra-NR Outgoing Handovers Between Two Specific Cells
Counters
1911817030 N.HO.NCell.Ex Number of BTS3900 5G, N

ecSuccOut successful intra- BTS5900 5G
NR outgoing
handovers
between two
specific cells
1911817031 N.HO.NCell.Pr Number of BTS3900 5G, N

epAttOut intra-NR BTS5900 5G
outgoing
handover
attempts
between two
specific cells


1911817032 N.HO.NCell.Ex Number of BTS3900 5G, N

ecAttOut intra-NR BTS5900 5G
outgoing
handover
executions
between two
specific cells
Description
The counters measure the performance of intra-NR outgoing handovers between two specific
cells.
Measurement Points
As shown at point A in Figure 1-105, Figure 1-106, and Figure 1-107, the
N.HO.NCell.PrepAttOut counter is incremented by 1 in the source cell each time the gNodeB
decides to perform an outgoing handover after receiving a measurement report from the UE
and the source cell and the target cell are two specific neighboring cells.
As shown at point B in Figure 1-105, Figure 1-106, and Figure 1-107, the
N.HO.NCell.ExecAttOut counter is incremented by 1 in the source cell each time an intra-
gNodeB handover, Xn-based handover, or NG-based handover is performed after the source
gNodeB sends an RRC Reconfiguration to the UE.
As shown at point C in Figure 1-105, the N.HO.NCell.ExecSuccOut counter is incremented
by 1 in the source cell each time an intra-gNodeB handover is performed after the target cell
receives an RRC Reconfiguration Complete message replied by the UE and the source cell
and the target cell are two specific neighboring cells.
by 1 in the source cell each time an inter-gNodeB Xn-based handover is performed after the
source gNodeB receives a UE CONTEXT RELEASE message from the target gNodeB and
the source cell and the target cell are two specific neighboring cells.
by 1 in the source cell each time an inter-gNodeB NG-based handover is performed after the
source gNodeB receives a UE CONTEXT RELEASE COMMAND message from the AMF
and the source cell and the target cell are two specific neighboring cells.
by 1 in the source cell each time an intra-gNodeB handover is performed after the RRC
Connection Reestablishment Complete message replied by the UE is received and the source
cell and the target cell are two specific neighboring cells.
by 1 in the source cell each time the UE is successfully reestablished to the source gNodeB
during an inter-gNodeB Xn-based handover and the source cell and the target cell are two
specific neighboring cells.
by 1 in the source cell each time the UE is successfully reestablished to the source gNodeB

during an inter-gNodeB NG-based handover and the source cell and the target cell are two
specific neighboring cells.
by 1 in the source cell each time the UE is successfully reestablished to the target gNodeB
during an inter-gNodeB Xn-based handover after the source gNodeB receives a UE
CONTEXT RELEASE message from the target gNodeB and the source cell and the target cell
are two specific neighboring cells.
by 1 in the source cell each time the UE is successfully reestablished to the target gNodeB
during an inter-gNodeB NG-based handover after the source gNodeB receives a UE
CONTEXT RELEASE COMMAND message from the AMF and the source cell and the
target cell are two specific neighboring cells.
Figure 1-105

Figure 1-106
Figure 1-107

Figure 1-108
Figure 1-109

Figure 1-110
Figure 1-111

Figure 1-112
Formula
None
Unit
None
Related Features
N.HO.NCell.ExecSuccOut Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.HO.NCell.PrepAttOut Multi-mode: None

GSM: None
UMTS: None
LTE: None

N.HO.NCell.ExecAttOut Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.7 Measurement of Operator-Specific NR DU Cell

Performance (NRDUCell.Operator)
Overview
The Measurement of Operator-Specific NR DU Cell Performance (NRDUCell.Operator)
object type contains function subsets used to measure the quality of services provided by
different operators in an NR DU cell.
FunctionSubSets
Traffic.RLC.DuCell.Operator Operator RLC Traffic Measurement

(Traffic.RLC.DuCell.Operator)
1.7.1 Operator RLC Traffic Measurement

(Traffic.RLC.DuCell.Operator)
Overview
The Operator RLC Traffic Measurement (Traffic.RLC.DuCell.Operator) function subset
measures the total traffic at the RLC layer in a cell of a specific operator.
Counters
1911817036 N.ThpTime.DL.PL Total RLC-layer BTS5900 5G:

MN transmit duration of V100R015C10
downlink data for a BTS3900:
specific operator in a V100R015C10
cell BTS5900:
V100R015C10


1911817037 N.ThpTime.UL.PL Total RLC-layer BTS5900 5G:

MN receive duration of V100R015C10
uplink data for a BTS3900:
specific operator in a V100R015C10
cell BTS5900:
V100R015C10
1911817038 N.ThpVol.DL.PLM Total volume of BTS5900 5G:

N downlink data sent V100R015C10
cell of a specific V100R015C10
operator BTS5900:
V100R015C10
1911817039 N.ThpVol.UL.PLM Total volume of BTS5900 5G:

N uplink data received V100R015C10
cell of a specific V100R015C10
operator BTS5900:
V100R015C10
None
1.7.1.1 Total RLC-layer SDU Duration of All UEs Served by an Operator
Counters
1911817036 N.ThpTime.DL. Total RLC- BTS3900, N

PLMN layer transmit BTS3900 5G,
duration of BTS5900,
downlink data
for a specific BTS5900 5G
operator in a
cell
1911817037 N.ThpTime.UL. Total RLC- BTS3900, N

PLMN layer receive BTS3900 5G,
duration of BTS5900,
uplink data for
a specific BTS5900 5G
operator in a
cell

Description
The counters measure the total duration for receiving RLC-layer SDUs of all UEs of an
operator in a cell.
Measurement Points
The SDU duration of uplink and downlink data of all UEs served by a specific operator sent at
the RLC layer accumulates in a cell. The accumulation result is used as the corresponding
counter value.
Formula
None
Unit
microsecond
Related Features
N.ThpTime.DL.PLMN Multi-mode: None

GSM: None
UMTS: None
LTE: None
NR: FOFD-021211 Multi-Operator Sharing
N.ThpTime.UL.PLMN Multi-mode: None

GSM: None
UMTS: None
LTE: None
1.7.1.2 Total volume of data transmission at the RLC layer for UEs of an Operator
Counters
1911817038 N.ThpVol.DL.P Total volume of BTS3900, N

LMN downlink data BTS3900 5G,
layer in a cell of
a specific BTS5900 5G
operator


1911817039 N.ThpVol.UL.P Total volume of BTS3900, N

LMN uplink data BTS3900 5G,
RLC layer in a
cell of a BTS5900 5G
specific
operator
Description
These counters measure the total volume of data transmission at the RLC layer for UEs of an
operator.
Measurement Points
The SDU payload of uplink or downlink data received or sent at the RLC layer is
accumulated for a specific operator in a cell. The accumulation results are used as the values
of the corresponding counters.
Formula
None
Unit
kbit
Related Features
N.ThpVol.DL.PLMN Multi-mode: None

GSM: None
UMTS: None
LTE: None
N.ThpVol.UL.PLMN Multi-mode: None

GSM: None
UMTS: None
LTE: None

1.8 Measurement of Operator-Specific NR CU Cell

Performance (NRCell.Operator)
Overview
The Measurement of Operator-Specific NR CU Cell Performance (NRCell.Operator) object
type contains function subsets used to measure the quality of services provided by different
operators in an NR CU cell.
FunctionSubSets
Traffic.User.Cell.Operator Cell User Quantity Measurement per

Operator (Traffic.User.Cell.Operator)
1.8.1 Cell User Quantity Measurement per Operator

(Traffic.User.Cell.Operator)
Overview
The Traffic.User.Cell.Operator function subset measures the number of users in a cell based
on the operator.
Counters

Max.Operator of users of an V100R015C10
operator in a cell BTS3900:
V100R015C10
BTS5900:
V100R015C10

Avg.Operator users of an operator V100R015C10
in a cell BTS3900:
V100R015C10
BTS5900:
V100R015C10

None
1.8.1.1 Number of Users of Operator in a Cell
Counters

nn.Max.Operat number of users BTS3900 5G,
or of an operator BTS5900,
in a cell
BTS5900 5G

nn.Avg.Operato number of users BTS3900 5G,
r of an operator BTS5900,
in a cell
BTS5900 5G
Description
The counters measure the number of users of different operators in a cell.
Measurement Points
of UEs in connected mode of different operators in a cell is sampled per second. At the end of
a measurement period, the average and maximum of these sampling results are taken as the
corresponding counter values. For DC users, one user is counted for each of the master base
station and the secondary base station.
Formula
None
Unit
None

Related Features
N.User.RRCConn.Max.Oper Multi-mode: None

ator GSM: None
UMTS: None
LTE: None
N.User.RRCConn.Avg.Oper Multi-mode: None

ator GSM: None
UMTS: None
LTE: None
1.9 Measurement of NR Cell-to-E-UTRAN Cell Handover

Performance (NRCELLtoECELL)
Overview
The NRCELLtoECELL measurement object contains function subsets used to measure the
handovers from a specific NR cell to a specific neighboring E-UTRAN cell. An
NRCELLtoECELL measurement object is activated when a neighbor relationship is added,
and an NRCELLtoECELL measurement object is deactivated when a neighbor relationship is
removed. A gNodeB supports a maximum of 9216 NRCELLtoECELL measurement objects.
If a gNodeB is configured with more than 9216 inter-RAT neighboring cells, the
NRCELLtoECELL measurement objects fail to be activated for the excess neighboring cells,
and the counters under these measurement objects are not reported to the EMS.
FunctionSubSets
IRATHO.NrCell.ECell Inter-RAT Inter-Cell E-UTRAN Handover

Measurement (IRATHO.NrCell.ECell)
1.9.1 Inter-RAT Inter-Cell E-UTRAN Handover Measurement

(IRATHO.NrCell.ECell)
Overview
The Inter-RAT Inter-Cell E-UTRAN Handover Measurement (IRATHO.NrCell.ECell)
function subset measures the handovers from an NR cell to a specific neighboring E-UTRAN
cell.

Counters
1911817053 N.HO.InterRAT.N Number of handover BTS5900 5G:

Cell.N2E.ExecAttO executions from a V100R015C10
ut specific NR cell to a BTS3900:
specific E-UTRAN V100R015C10
cell BTS5900:
V100R015C10
1911817054 N.HO.InterRAT.N Number of handover BTS5900 5G:

Cell.N2E.PrepAttO preparation attempts V100R015C10
ut from a specific NR BTS3900:
cell to a specific E- V100R015C10
UTRAN cell BTS5900:
V100R015C10
1911817055 N.HO.InterRAT.N Number of BTS5900 5G:

Cell.N2E.ExecSucc successful V100R015C10
Out handovers from a BTS3900:
specific NR cell to a V100R015C10
specific E-UTRAN BTS5900:
cell V100R015C10
None
1.9.1.1 Number of Handovers from a Specific NR Cell to a Specific E-UTRAN

Cell
Counters

.NCell.N2E.Exe handover BTS3900 5G,
cAttOut executions from BTS5900,
a specific NR
cell to a specific BTS5900 5G
E-UTRAN cell



.NCell.N2E.Pre handover BTS3900 5G,
pAttOut preparation BTS5900,
attempts from a
specific NR cell BTS5900 5G
to a specific E-
UTRAN cell

.NCell.N2E.Exe successful BTS3900 5G,
cSuccOut handovers from BTS5900,
a specific NR
cell to a specific BTS5900 5G
E-UTRAN cell
Description
These counters measure the number of handovers from a specific NR cell to a specific E-
UTRAN cell. The signaling procedures related to these counters comply with section 5.4 in
3GPP TS 38.331 (V15.1.0).
Measurement Points
As shown at point A in Figure 1-113, when the gNodeB determines to perform a handover to
a specific neighboring E-UTRAN cell after receiving a Measurement Report message from
the UE, the value of N.HO.InterRAT.NCell.N2E.PrepAttOut is incremented by 1.
As shown at point B in Figure 1-113, when the gNodeB sends a Mobility From NR
Command message to the UE during a handover from a specific NR cell to a neighboring E-
UTRAN cell, the value of N.HO.InterRAT.NCell.N2E.ExecAttOut is incremented by 1.
As shown at point C in Figure 1-113, when the gNodeB receives a UE CONTEXT
RELEASE COMMAND message from the AMF after the UE is handed over to the
neighboring E-UTRAN cell, the value of N.HO.InterRAT.NCell.N2E.ExecSuccOut is
incremented by 1.

Figure 1-113
Formula
None
Unit
None
Related Features
N.HO.InterRAT.NCell.N2E. Multi-mode: None

ExecAttOut GSM: None
UMTS: None
LTE: None
NG-RAN to E-UTRAN


PrepAttOut GSM: None
UMTS: None
LTE: None
NG-RAN to E-UTRAN

ExecSuccOut GSM: None
UMTS: None
LTE: None
NG-RAN to E-UTRAN

3900 Series &amp; 5900 Series Base V100R015C10SPC080 GNodeBFunction Performance Counter Reference

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

3900 Series &amp; 5900 Series Base V100R015C10SPC080 GNodeBFunction Performance Counter Reference

Загружено:

Авторское право:

Доступные форматы

3900 Series & 5900 Series Base Station

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. i

About This Document

Figure 1 Document structure

Table 1 explains the terms shown in Figure 1.

One function subset contains one or more counters but

Counters are the basic elements of performance

Counter Item Description

Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. ii

Table 2 Description of each counter item

Object Overview Definition and function of a object type.

Functio FunctionSet Name of the function set.

Functio Overview Definition of a function subset and the flowchart for

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.

Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. iii

Related Features Features related to a counter are listed in feature ID and

Network Element NE Type of a product displayed on the Network

Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. iv

About This Document.....................................................................................................................ii

Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. v

1.1.7.1 Number of QoS Flow Modifications in SA Scenarios........................................................................................... 47

Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. vi

1.1.24.5 Reserved Counter 5 for the Cell......................................................................................................................... 133

Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. vii

1.1.24.47 Reserved Counter 47 for the Cell..................................................................................................................... 161

Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. viii

Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. ix

1.2.9.22 Reserved Counter 22 for the Local Cell............................................................................................................. 433

Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. x

Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. xi

1.2.21 Cell Service Quality Measurement (QoS.Cell)..................................................................................................... 802

Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. xii

Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. xiii

1 gNodeBFunction Performance Counter

About This Chapter

This section describes gNodeBFunction performance counters.

1.1 Measurement of Cell Performance (NRCELL)

1.1 Measurement of Cell Performance (NRCELL)

Issue Draft C (2019-04-10) Copyright © Huawei Technologies Co., Ltd. 1

FunctionSubSet FunctionSubSet Name

Traffic.DRB.Cell DRB Measurement (Traffic.DRB.Cell)

PDCP.Cell PDCP Measurement(PDCP.Cell)

PDUSession.Modify.Cell PDU Session Modification Measurement

PDUSession.Est.Cell PDU Session Setup Measurement

PDUSession.Rel.Cell PDU Session Release Measurement

QosFlow.Modify.Cell QoS Flow Modification Measurement

QosFlow.EstFail.Cell QoS Flow Setup Failure Measurement

QosFlow.Est.Cell QoS Flow Setup Measurement

QosFlow.Rel.Cell QoS Flow Release Measurement

RRC.SetupFail.Cell RRC Setup Failure Measurement

RRC.Setup.Cell RRC Setup Measurement (RRC.Setup.Cell)

RRC.ReEstFail.Cell RRC Reestablishment Failure Measurement

RRC.ReEst.Cell RRC Reestablishment Measurement

UeCntx.Modify.Cell UE Context Modification Measurement

UeCntx.EstFail.Cell UE Context Setup Failure Measurement

3900 Series & 5900 Series Base V100R015C10SPC080 GNodeBFunction Performance Counter Reference

3900 Series & 5900 Series Base V100R015C10SPC080 GNodeBFunction Performance Counter Reference