This page describes KPI-related measurements implemented in the Legba Yate-based eNodeB.
KPI-Related Measurements vs. Actual KPIs
As per the standard, the eNodeB does not produce KPIs directly, but instead produces measurements that can be used to compute KPIs for different sets of eNodeBs.
The calculation of KPIs from raw measurements is normally done by a “middleware” called an Element Manager.
Standard and Vendor-Specific Measurements
Beyond standard measurements specified by 3GPP, vendors are also free to add their own measurements to the eNodeB.
In the Legba implementation, vendor-specific measurements are put into the same measurement groups with the standard measurements and follow a similar naming scheme.
In this documentation, you can tell standard measurements from vendor-specific measurements because the descriptions of standard measurements reference the specifications that define them.
- Locally – via Telnet/Rmanager: Measurements are accessed locally via rmanager with the enb measurements command or with status enb. See YateeNB commands for details.
- Remotely – via JSON: Yate provides a JSON/HTTP interface for remote monitoring, which is also based on the status enb command. See this page for more information.
Time Period Covered By Measurements
The ENB measurement system is cleared with
enb measurements clear or with the
clear option on the
status enb command.
This clearing begins a new measurement period which continues until the next clearing.
When measurements are reported with
enb measurements> or
status enb, the report includes the Unix time that the measurement period started (“LastClearTime”) and the current Unix time (“CurrentTime”).
These times are the last items given in the report.
RRC connection related measurements (RRC)
Measurements in this group track the reliability of RRC connections.
As of Dec 2017, YateeNB does not implement most of the measurements in this group.
|RRC.MeasReportRSRQ||Mean RSRQ reported by UEs|
|RRC.MeasReportRSRP||Mean RSRP reported by UEs|
|RRC.MeasReportNbr||Number of UE measurement reports received|
|RRC.ConnMean||Mean number of active RRC connections. See 3GPP 32.425 Section 18.104.22.168.|
|RRC.ConnMax||Maximum number of active RRC conections. See 3GPP 32.425 Section 22.214.171.124.|
E-RAB related measurements (ERAB)
An “E-RAB” is the combination of a DRB in the ENB and the corresponding S1 bearer in the EPC. Measurements in this group track E-RAB reliability.
|ERAB.EstabInitAttNbr.||Total number of initial E-RAB UE establishment attempts. See 3GPP 32.425 Section 126.96.36.199.|
|ERAB.EstabInitSuccNbr.||Number of successful initial E-RAB UE establishment attempts. See 3GPP 32.425 Section 188.8.131.52.|
|ERAB.EstabAddSuccNbr.||Number of successful additional E-RAB UE establishment attempts. See 3GPP 32.425 Section 184.108.40.206.|
|ERAB.SessionTimeUE||Total UE session time in seconds. See 3GPP 32.425 Section 220.127.116.11.|
|ERAB.SessionTimeQCI.||E-RAB session times in seconds. See 3GPP 32.425 Section 18.104.22.168.|
|ERAB.UsageNbrMean.||Average number of active E-RABs. See 3GPP 32.425 Section 22.214.171.124.|
|ERAB.UsageNbrMax.||Maximum number of active E-RABs. See 3GPP 32.425. Section 126.96.36.199.|
Handover related measurements (HO)
As of December 2017, YateeNB does not support handover and does not produce measurements in this group.
Cell level radio bearer QoS related measurements (DRB)
This group measures performance in the RLC and PDCP layers.
Many parameters in this group are tracked per-QCI.
|DL bit rate in kbit/sec. |
See 3GPP Section 188.8.131.52.
|UL bit rate in kbit/sec. |
See 3GPP Section 184.108.40.206.
|Delay on DL from PDCP to transmission in ms. |
See 3GPP Section 220.127.116.11.
|See 3GPP Section 18.104.22.168.|
|See 3GPP Section 22.214.171.124.|
|DRB.PdcpSduLossRateUl.||UL packet loss rate in percent x100. |
See 3GPP Section 126.96.36.199.
|DRB.IPLatDl.||See 3GPP Section 188.8.131.52.|
|See 3GPP Section 184.108.40.206. |
The sum is a vendor-specific addition.
|See 3GPP Section 220.127.116.11. |
The sum is a vendor-specific addition.
|See 3GPP 32.425 Section 4.4.2.|
|Number of RLC PDUs sent on DL.|
|Number of bytes sent on RLC in DL.|
|DRB.RlcDlSdus||Number of DL SDUs and DL SDU bytes consumed from by RLC from PDCP.|
|Number of DL PDUs and DL PDU bytes retransmitted by RLC.|
|Number of SDUs and SDU bytes produced by UL RLC into PDCP.|
|Number of PDUs and number of bytes received in UL by RLC, not counting rejected PDUs.|
|DRB.RlcUlNacks||Number of UL RLC PDUs for which RLC generated a NACK.|
|DRB.RlcUlRtxBytes||Number of bytes retransmitted in UL by RLC.|
|DRB.RlcUlPdusRejected DRB.RlcUlPdusRejectedBtes||Number of UL PDUs received and rejected by RLC and the number of bytes in those rejected PDUs. |
These are usually RLC PDUs with duplicated sequence numbers.
|DRB.PdcpDlSdus DRB.PdcpDlSduBytes||Number of DL PDCP PDUs and the number of bytes in those PDUs, delivered from PDCP to RLC in DL.|
|DRB.PdcpDlSdusDropped DRB.PdcpDlSduBytesDropped||Number of DL PDCP SDUs that were dropped and the number of bytes in those SDUs. |
These are usually dropped due to excessive delay in the DL.
|DRB.PdcpUlSdus DRB.PdcpUlSduBytes||Number of UL PDCP PDUs and the number of bytes in those PDUs, delivered from RLC to PDCP in UL.|
|DRB.PdcpUlSdusDropped||Number of UL PDCP SDUs that were dropped in the UE. |
These are usually dropped due to excessive delay in the UL.
Radio resource utilization related measurements (RRU and TB)
|RRU.PrbTotDl||Total PRBs scheduled by the MAC in DL. |
See 3GPP 32.425 Section 4.5.3.
|RRU.PrbTotUl||Total PRBs scheduled by the MAC in UL. |
See 3GPP 32.425 Section 4.5.4.
|RRU.RachPreambleAMean||Total number of PRACH preambles from set "A". |
See 3GPP 32.425 Section 18.104.22.168.
|PRACH delays in TAC units. |
One TAC unit is 0.52 microseconds.
See 3GPP 32.425 Section 22.214.171.124.
|RRU.RachDedicatedPreamblesAssigned||Percentage of PRACH subframes (x100) when all available PRACH preambles are in use. |
See 3GPP 32.425 Section 126.96.36.199.
|RRU.PrbCongestionDl||Percentage of subframes (x100) when all DL PRBs are allocated. See 3Gpp 32.425 188.8.131.52.|
|RRU.PrbCongestionUl||Percentage of subframes (x100) when all UL PRBs are allocated. See 3Gpp 32.425 184.108.40.206.|
|RRU.RachRx||Total number of PRACH events detected.|
|RRU.RachMsg3Rx||Total number of msg3 events detected.|
|RRU.PdcchCongestion||Percentage of subframes (x100) where DCIs were dropped due to congestion in PDCCH.|
|RRU.PucchSnr||PUCCH SNR in dB.|
|RRU.PucchRssi||PUCCH RSSI in dB relative to receiver saturation.|
|RRU.PuschSnr||PUSCH SNR in dB.|
|RRU.PuschRssi||PUSCH RSSI in dB relative to receiver saturation.|
|MCS values used in UL.|
|MCS values used in DL.|
|Total number of TBs received, not including HARQ RTX. |
See 3GPP 32.425 Section 220.127.116.11.
"Bytes" count is vendor-specific addition.
|Total number of TBs failing CRC check, not including HARQ RTX. |
See 3GPP 32.425 Section 18.104.22.168.
"Bytes" count is vendor-specific addition.
|Total number of TBs scheduled in UL and total bytes carried in those TBs, including HARQ RTX and decoding failures.|
|TB.PuschUlFer||Average TB decode failure rate on PUSCH, including HARQ RTX.|
|Total number of TB used for HARQ RTX and bytes carried.|
|TB.MacUlMces||Total number of MAC Control Elements received in UL.|
|Total number of MAC UL PDUs received and total bytes carried.|
|Total number of MAC UL SDUs (RLC PDUs) received and total bytes carried.|
|TB.UlEmptyBsr||Count of UL "long" BSRs reporting zero bytes.|
|TB.PhyTotalUlBytes||Total number of bytes received from PHY, including MAC MCEs, padding, and HARQ RTX.|
|TB.DroppedNbrUl||Count of UL TBs that were scheduled but not decoded due to late processing.|
|Total number of TBs sent on DL, not counting HARQ RTX. |
See 3GPP 32.425 Section 22.214.171.124.
Bytes count is vendor-specific addition.
|TB.UnansweredDlHarq||Total number of DL TBs for which no HARQ feedback was received.|
|TB.PucchNackConf||HARQ feedback confidence, the percent (x100) of PDSCH TBs where the ENB received HARQ feedback.|
|TB.ErrNbrDl||Total number of DL TBs for which UE reported HARQ NACK, not including HARQ RTX.|
|Total counts of HARQ ACKs and NACKs for TBs sent on PDSCH.|
|Total count of DL HARQ RTX TBs and the bytes carried in those TBs.|
|TB.MacDlMces||Total count of MAC MCEs sent on DL.|
|Total number of MAC PDUs (TBs) scheduled on DL PDSCH and the bytes carried in those PDUs.|
|Total number of MAC SDUs (RLC PDUs) scheduled on DL PDSCH and the bytes carried in those PDUs.|
|TB.PhyTotalDlBytes||Total number of bytes sent on PDSCH, including MAC MCEs and HARQ RTX.|
|TB.DroppedNbrDl||Count of DL TBs that were scheduled but not transmitted due to late processing.|
UE-associated logical S1-connection related measurements (S1SIG)
Measurements in this group track the reliability of UE connections in S1AP.
|S1SIG.ConnEstabAtt||Number of S1AP connection attempts. |
See 3GPP 32.425 Section 126.96.36.199.
|S1SIG.ConnEstabSucc||Number of successful S1AP connections. |
See 3GPP 32.425 Section 188.8.131.52.
Paging related measurements (PAG)
Measurements in this group track the reliability of paging operations.
|PAG.ReceivedNbr||Number of paging messages received by the eNodeB. |
See 3GPP 32.425 Section 184.108.40.206.
|PAG.DiscardedNbr||Number of paging messages dropped without transmission by the eNodeB. |
See 3GPP 32.425 Section 220.127.116.11.
Measurements related to equipment resources (EQPT)
Measurements in this group track the health and status of hardware.
The standard measurements in this group are outside the scope of the YateeNB module.
|EQPT.LateSubframes||Number of subframes dropped due to heavy CPU loaading.|
Common LAs of overlapping RAT's coverage (RRC)
As of 21 Dec 2017, YateeNB does not produce measurements in this group.
RF Measurements (CARR)
Measurements in this group tack radio channel quality.
|CARR.WBCQIDist.Bin||Number of times each CQI was received. |
See 32.425 Section 18.104.22.168.
|CARR.TADist.Bin||Number of times each timing advance value was used. |
Values are in TAC units, 0.52 microseconds per unit.
See 32.425 Section 4.10.2.
|CARR.DlCapacity||Average DL capacity in bits/element.|
|CARR.UlCapacity||Average UL capacity in bits/element.|