KPI Description

Ericsson Information Store User Guide - Data
Description
1/1553-CNA 403 3397 Uen F

Copyright
© Ericsson LMI 2018. All rights reserved. No part of this document may be
reproduced in any form without the written permission of the copyright owner.
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of
this document.
Trademark List
All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.
1/1553-CNA 403 3397 Uen F | 2018-08-10

Contents
Contents
1 KPI Definitions 1
1.1 Initial E-RAB Establishment Success Rate 3
1.2 E-RAB Retainability - Percentage Lost 5
1.3 Average DL UE Latency 6
1.4 Average DL PDCP Cell Throughput 7
1.5 Average UL PDCP Cell Throughput 8
1.6 Average Downlink Volume 9
1.7 Average number of simultaneous Active UEs in DL 10
1.8 Average number of RRC Connected users 11
1.9 Average UE Session Time 12
1.10 Average Number of Simultaneous E-RABs 13
1.11 Average usage of Downlink PRB 14
1.12 VoIP Integrity 15
1.13 Initial E-RAB Establishment Success Rate per QCI 18
1.14 Added E-RAB Establishment Success Rate per QCI 20
1.15 Voip Integrity DL - RTP inter arrival GAP 22
1.16 Voip Integrity UL - RTP inter arrival GAP 23
1.17 E-RAB Retainability - Percentage Lost per QCI 24
1.18 IMS SBG Incoming Session Set-up Success Ratio 26
1.19 IMS SBG Outgoing Session Set-up Success Ratio 27
1.20 IMS A-SBG Initial Registration Success Ratio 29
1.21 IMS SBG SRVCC Access Transfer Success Ratio 31
1.22 IMS SBG Incoming Sessions Set-up Time 32
1.23 IMS SBG Outgoing Sessions Set-up Time 34
1.24 IMS A-SBG Initial Registration Time 36
1.25 SBG Total successful transfers in IMS 38
1.26 IMS SBG Media RTP Lost Packets Ratio 38
1.27 IMS SBG Media RTP Out of Sequence Packets Ratio 39
1.28 IMS SBG Incoming Priority Session Set-up Success Ratio 40
1.29 IMS SBG Emergency Session Set-up Success Ratio 42
1.30 IMS A-SBG Emergency Initial Registration Success Ratio 43
1.31 MSC SRVCC from LTE success rate per MME 44
1/1553-CNA 403 3397 Uen F | 2018-08-10

Ericsson Information Store User Guide - Data Description
1.32 MSC SRVCC from LTE Success for MSC 45

1.33 MSC Relocation success rate to target RNC 46
1.34 MSC Relocation success rate to target MSC,WCDMA 47
1.35 IMS CSCF Third Party Registration Success Ratio 48
1.36 IMS CSCF EATCF SRVCC Access Transfer Success Ratio 49
1.37 S5 Create Session Failure per APN (IMS) ratio 50
1.38 MME - SRVCC to WCDMA failure ratio 52
1.39 MME - SRVCC to GERAN failure ratio 54
1.40 MME: Total SRVCC Attempts 55
1.41 MME Dedicated Bearer Activation Success 56
1.42 MME VoLTE Uptake 57
1.43 IMS MMTEL AS Originating Session Set-up Success Ratio 58
1.44 IMS MMTEL AS Terminating Session Set-up Success Ratio 61
1.45 IMS SCC AS Session Setup from CS using CAP Registered
and Unregistered Users Success Ratio 65
1.46 IMS MMTel AS Orginating Session Completion Ratio 68
1.47 IMS MMTel AS Terminating Session Completion Ratio 69
1.48 IMS SCC AS Single Radio Voice Call Continuity (SRVCC)
Access Transfer Success Ratio 71
1.49 IMS MTAS Priority Call Successfully Established Ratio 72
1.50 Average interference measured in the PRBs for the PUSCH 73
1.51 Average interference measured in the PRBs for the PUCCH 76
1.52 Interference power per PRB 78
1.53 Interference power per antenna branch and PRB 79
1.54 UL/DL ACHIEVABLE THROUGHPUT PER EUTRANCELL 80
2 Data Tables 83
2.1 DIM_CV_ACM_CM_CONSTANTS 84
2.2 DIM_CV_ACM_CONFIG 85
2.3 DIM_CV_ACM_FREQBANDS 86
2.4 DIM_CV_ACM_UPLINK_TBS 86
2.5 DIM_CV_BULKCM_EUTRANCELLFDD 86
2.6 DIM_CV_BULKCM_EUTRANCELLTDD 87
2.7 DIM_CV_BULKCM_SECTORCARRIER 89
2.8 DIM_CV_MEASURE 89
2.9 DIM_CV_MEASURE_LIMITS 93
2.10 DIM_CV_NODE_CONTROL 95
1/1553-CNA 403 3397 Uen F | 2018-08-10

Contents
2.11 DIM_CV_SEGMENT 96
2.12 DIM_CV_ERBS 97
2.13 DIM_CV_ERBS_EUTRANCELL 97
2.14 DIM_CV_NODE_INFO 99
2.15 DC_CV_ERBS_EUTRANCELL_RAW_RANK 100
2.16 DC_CV_ERBS_PMULINTERFERENCEREPORT_RAW_RANK 100
2.17 DC_CV_CNAXE_MSC 101
2.18 DC_CV_CSCF_CSCF 101
2.19 DC_CV_ERBS_EUTRANCELL 102
2.20 DC_CV_ERBS_EUTRANCELL_V 102
2.21 DC_CV_ERBS_EUTRANCELL_ACM 103
2.22 DC_CV_ERBS_PMULINTERFERENCEREPORT 103
2.23 DC_CV_GGSN_PGW 104
2.24 DC_CV_IMSGW_SBG 104
2.25 DC_CV_MTAS_MTAS 105
2.26 DC_CV_SGSN_MME 105
2.27 DC_CV_SGSN_MME_V 105
Glossary 107
Reference List 109
1/1553-CNA 403 3397 Uen F | 2018-08-10

1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1 KPI Definitions
Listed below are the Measures with their corresponding Measure ids supported in
Information Store
Information Store provides KPI's which can be used by a reporting product. The
KPI's are stored in the ENIQ Statistics database where each Measure below
is the KPI name.
Table 1 List of KPI's

Measure Measure NODE TYPE STATUS
ID
Initial E-RAB Establishment Success Rate 1 ERBS Inactive
E-RAB Retainability - Percentage Lost 2 ERBS Inactive
Average DL UE Latency 3 ERBS Inactive
Average DL PDCP Cell Throughput 4 ERBS Inactive
Average UL PDCP Cell Throughput 5 ERBS Inactive
Average Downlink Volume 6 ERBS Inactive
Average number of simultaneous Active UEs in DL 7 ERBS Inactive
Average number of RRC Connected users 8 ERBS Inactive
Average UE Session Time 9 ERBS Inactive
Average Number of Simultaneous E-RABs 10 ERBS Inactive
Average usage of Downlink PRB 11 ERBS Inactive
VoIP Integrity 12 ERBS Inactive
Initial E-RAB Establishment Success Rate per QCI 13 ERBS Inactive
Added E-RAB Establishment Success Rate per QCI 14 ERBS Inactive
Voip Integrity DL - RTP inter arrival GAP 15 ERBS Inactive
Voip Integrity UL - RTP inter arrival GAP 16 ERBS Inactive
E-RAB Retainability - Percentage Lost per QCI 17 ERBS Inactive
IMS SBG Incoming Session Set-up Success Ratio 18 SBG Inactive
IMS SBG Outgoing Session Set-up Success Ratio 19 SBG Inactive
IMS A-SBG Initial Registration Success Ratio 20 SBG Inactive
IMS SBG SRVCC Access Transfer Success Ratio 21 SBG Inactive
IMS SBG Incoming Sessions Set-up Time 22 SBG Inactive
IMS SBG Outgoing Sessions Set-up Time 23 SBG Inactive
IMS A-SBG Initial Registration Time 24 SBG Inactive
1/1553-CNA 403 3397 Uen F | 2018-08-10 1


SBG Total successful transfers in IMS 25 SBG Inactive
IMS SBG Media RTP Lost Packets Ratio 26 SBG Inactive
IMS SBG Media RTP Out of Sequence Packets Ratio 27 SBG Inactive
IMS SBG Incoming Priority Session Set-up Success 28 SBG Inactive
Ratio
IMS SBG Emergency Session Set-up Success Ratio 29 SBG Inactive
IMS A-SBG Emergency Initial Registration Success 30 SBG Inactive
Ratio
MSC SRVCC from LTE success rate per MME 31 MSC Inactive
MSC SRVCC from LTE success rate per MSC 32 MSC Inactive
MSC Relocation success rate to target RNC 33 MSC Inactive
MSC Relocation success rate to target MSC,WCDMA 34 MSC Inactive
IMS CSCF Third Party Registration Success Ratio 35 CSCF Inactive
IMS CSCF EATCF SRVCC Access Transfer Success 36 CSCF Inactive
Ratio
S5 Create Session Failure per APN (IMS) ratio 37 GGSN Inactive
MME - SRVCC to WCDMA failure ratio 38 SGSN Inactive
MME - SRVCC to GERAN failure ratio 39 SGSN Inactive
MME: Total SRVCC Attempts 40 SGSN Inactive
MME Dedicated Bearer Activation Success 41 SGSN Inactive
MME VoLTE Uptake 42 SGSN Inactive
IMS MMTEL AS Originating Session Set-up Success 43 MTAS Inactive
Ratio
IMS MMTEL AS Terminating Session Set-up Success 44 MTAS Inactive
Ratio
IMS SCC AS Session Setup from CS using CAP 45 MTAS Inactive
Registered and Unregistered Users Success Ratio
IMS MMTel AS Orginating Session Completion Ratio 46 MTAS Inactive
IMS MMTel AS Terminating Session Completion 47 MTAS Inactive
Ratio
IMS SCC AS Single Radio Voice Call Continuity 48 MTAS Inactive
(SRVCC) Access Transfer Success Ratio
IMS MTAS Priority Call Successfully Established 49 MTAS Inactive
Ratio
Average interference measured in the PRBs for the 50 ERBS Inactive
PUSCH
2 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions

Average interference measured in the PRBs for the 51 ERBS Inactive
PUCCH
Interference power per PRB 52 ERBS Inactive
Interference power per antenna branch and PRB 53 ERBS Inactive
UL/DL ACHIEVABLE THROUGHPUT PER 54 ERBS Inactive
EUTRANCELL
Note: By default, all the Measures and the node type in the Information Store
are marked as Inactive.
KPIs will be calculated only when the particular Measure and its
corresponding NODE TYPE are ACTIVE on the server.
— Refer section 2.1, in the Information Store Configuration Document,

Reference [16] to update the Status of the node type to ACTIVE

Reference [16] to update the Status of the Measure to ACTIVE

Reference [16] to change the default threshold to the desired
threshold for the particular Measure
The Measures mentioned above are described in the following sections.
1.1 Initial E-RAB Establishment Success Rate
1.1.1 Description
This KPI gives the accessibility success rate for end-user services that are carried
by E-RABs included in the Initial UE Context setup procedure.
1.1.2 Node Type

ERBS
1.1.3 Formula
1/1553-CNA 403 3397 Uen F | 2018-08-10 3

where RRCMMEOVL = pmRrcConnEstabFailMmeOvlMos + pmRrcConnEstab

FailMmeOvlMod
1.1.4 Metric Type
Percentage (%)
1.1.5 Counters
Counter Description Scanner Counter Type

pmRrcConnEstabSuc The total number of successful RRC Primary PEG
c Connection Establishments.
pmRrcConnEstabAtt The total number of RRC Connection Primary PEG
Request attempts with establishment
cause emergency.
pmRrcConnEstabAtt The total number of RRC Connection Primary PEG
Reatt Request attempts that are considered as
re-attempts.
pmS1SigConnEstabS The total number of successful S1 Primary PEG
ucc signalling connection establishments.
pmS1SigConnEstabA The total number of S1 Signalling Primary PEG
tt connection establishment attempts for
any establishment cause.
pmS1SigConnEstabF The total number of failed S1 signaling Primary PEG
ailMmeOvlMos connection establishments with
Establishment cause Mobile Originating
Signaling due to MME overload.
pmErabEstabSuccIn The total number of successful initial Primary PEG
it E-RAB Establishments. Initial E-RABs
are all E-RABs present in the S1 message
Initial Context Setup Request.
4 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions

pmErabEstabAttIni The total number of initial E-RAB Primary PEG
t Establishment attempts. Initial E-RABs
are all E-RABs present in the S1 message
Initial Context Setup Request.
pmRrcConnEstabFai The total number of failed RRC Connection Primary PEG
lMmeOvlMos Establishments with Establishment cause
Mobile Originating Signaling due to MME
overload.
pmRrcConnEstabFai The total number of failed RRC Connection Primary PEG
lMmeOvlMod Establishments with Establishment cause
Mobile Originating Data due to MME
overload.
1.1.6 Reference
This KPI is defined in Key Performance Indicators in Section 2.1.1, Reference [2]
and Counter Description Reference [3].
1.2 E-RAB Retainability - Percentage Lost
1.2.1 Description
This KPI measures the impact on the end user with the purpose to reflect the
percentage of established E-RABs that are lost with an abnormal release.
1.2.2 Node Type
ERBS
1.2.3 Formula
1.2.4 Metric Type

Percentage (%)
1/1553-CNA 403 3397 Uen F | 2018-08-10 5

1.2.5 Counters

pmErabRelAbnormal The total number of abnormal E-RAB Primary PEG
EnbAct Releases per cell initiated by the eNB
and that there was data in either the
UL or DL buffer (i.e. active).
pmErabRelAbnormal The total number of E-RAB Releases Primary PEG
MmeAct initiated by the MME considered as
abnormal. The counter is stepped if
there was data in either the UL or DL
buffer (i.e. active).
pmErabRelAbnormal The total number of abnormal E-RAB Not included PEG
Enb Releases triggered by eNB per cell. in any
predefined
scanner
pmErabRelNormalEn The total number of normal E-RAB Not included PEG
b Releases triggered by eNB per cell. in any
predefined
scanner
pmErabRelMme The total number of E-RAB Releases Not included PEG
per cell initiated by the MME excluding in any
successful handover. The counter is predefined
stepped regardless of whether data scanner
was or was not lost in UL/DL buffers.
1.2.6 Reference
1.3 Average DL UE Latency
1.3.1 Description
This KPI measures the impact on the end user.

NOTE The latency will increase with more instantaneously active UEs and will
also depend on the scheduling algorithm(s) being used.
1.3.2 Node Type

ERBS
6 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.3.3 Formula
1.3.4 Metric Type

Milliseconds (ms)
1.3.5 Counters

pmPdcpLatTimeDl Aggregated DL Latency for a Primary ACC
measurement period. The effective
DL Latency time comprises the time from
PDCP DRB SDU entering the buffer until
the first data has been transmitted to the
UE. When carrier aggregation is used, the
DL Latency for all component carriers is
registered on the UE's primary component
carrier (PCell).
pmPdcpLatPktTrans Number of DRB packets for downlink Primary PEG
Dl Latency measurements.
1.3.6 Reference
1.4 Average DL PDCP Cell Throughput
1.4.1 Description
This KPI shows the average DL PDCP throughput for a cell.
1.4.2 Node Type
ERBS
1/1553-CNA 403 3397 Uen F | 2018-08-10 7

1.4.3 Formula
1.4.4 Metric Type

Kilobits Per Second (kbps)
1.4.5 Counters
These counters are defined per Cell.

pmPdcpVolDlDrb The total volume (PDCP SDU) on Primary ACC
Data Radio Bearers that has been
transferred (UM and AM) in the downlink
direction.When carrier aggregation is
used, a PDCP SDU can be sent over
multiple cells (PCell/SCell(s)). The total
volume (PDCP SDU) on Data Radio
Bearers that has been transferred (UM
and AM) in the downlink direction is
measured on PCell.
pmSchedActivityCel The aggregated number of ms in which Not includ PEG
lDl DRB data was required to be scheduled ed in any
in the downlink. predefine
d scanner
1.4.6 Reference
This KPI is defined in Key Performance Indicators in Section 2.3.3.3,Reference [2]
1.5 Average UL PDCP Cell Throughput
1.5.1 Description
This KPI shows the average UL PDCP throughput for a cell.
8 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.5.2 Node Type

ERBS
1.5.3 Formula
1.5.4 Metric Type
Kilobits Per Second (kbps)
1.5.5 Counters

pmPdcpVolUlDrb The total volume (PDCP SDU) on Data Primary ACC
Radio Bearers that has been received in
the uplink direction and transmitted over
the GTP-U.
pmSchedActivityCel The aggregated number of ms in which Not included PEG
lUl DRB data was required to be scheduled in any
in the uplink. predefined
scanner
1.5.6 Reference
This KPI is defined in Key Performance Indicators in Section 2.3.5.3, Reference [2]
1.6 Average Downlink Volume
1.6.1 Description
This metric measures the load in the system in terms of downlink (DL) volume.
1.6.2 Node Type
ERBS
1/1553-CNA 403 3397 Uen F | 2018-08-10 9

1.6.3 Formula
The total volume received by the Packet Data Convergence Protocol (PDCP)
volume in the downlink per cell for L number of cells is given by the following
equations. The counters are on cell level:
P pmPdcpV olDlDrb pmPdcpV olDlSrb
DL V olume kilobits
[ ] =
L
( + )
Equation 1 Average DL Volume per Cell
1.6.4 Metric Type

KiloBits (kb)
1.6.5 Counters

pmPdcpVolDlD The total volume (PDCP SDU) on Data Radio Primary ACC
rb Bearers that has been transferred (UM and AM)
in the downlink direction.
pmPdcpVolDlS The total number of bits (PDCP SDU) on Primary ACC
rb Signalling Radio Bearers that has been
transferred (acknowledged by the UE) in the
downlink direction.
1.6.6 Reference
This PI is defined in Reference [1] and Counter(s) is/are defined in Managed

Object Model Class EUtranCellFDD and EUtranCellTDD .
1.7 Average number of simultaneous Active UEs in DL
1.7.1 Description
This metric measures the load in the system in terms of simultaneous number of
Active User Equipments (UEs) in DL.
1.7.2 Node Type

ERBS
10 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.7.3 Formula
The average number of Active UEs in DL per cell is given by the following equation.
The counters are on cell level:
pmActiveUeDlSum
Average number of Active UEs in DL = pmSchedActivityCellDl
Equation 2 Average Number of Simultaneous Active UEs in DL per Cell
1.7.4 Metric Type
Count
1.7.5 Counters

pmActiveUeDl Number of UEs considered active in the Not included in ACC
Sum downlink direction. any predefined
scanner
pmSchedActiv The aggregated number of ms in which Not included in PEG
ityCellDl DRB data was required to be scheduled in any predefined
the downlink. scanner
1.7.6 Reference
Object Model Class EUtranCellFDD and EUtranCellTDD.
1.8 Average number of RRC Connected users
1.8.1 Description
This metric measures the load in the system in terms of Radio Resource Control
(RRC) Connected users per cell.
1.8.2 Node Type

ERBS
1/1553-CNA 403 3397 Uen F | 2018-08-10 11

1.8.3 Formula
The average number of RRC Connected users per cell is given by the following
equation. The counters are on cell level:
pmRrcConnLevSum
Average number RRC Connected Users = pmRrcConnLevSamp
Equation 3 Average Number of RRC Connected Users per Cell
1.8.4 Metric Type

Count
1.8.5 Counters

pmRrcConnLevS Sum of all sample values recorded for Not included in ACC
um "number of UEs in RRC_CONNECTED any predefined
mode". scanner
pmRrcConnLevS Number of times the corresponding Not included in SCAN
amp Sum counter has accumulated a new any predefined
sample. Associated ACC pmCounter scanner
pmRrcConnLevSum.
1.8.6 Reference
1.9 Average UE Session Time
1.9.1 Description
The accumulated UE session time per cell.
1.9.2 Node Type

ERBS
12 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.9.3 Formula
The accumulated UE session time per cell for L number of cells is given by the
following equation. The counters are on cell level:
P pmSessionTimeUe
Average UE session Time s [ ] =
(
L
)
Equation 4 Average UE Session Time per Cell
1.9.4 Metric Type

Seconds (s)
1.9.5 Counters

pmSessionTimeUe This counters shows the accumulated Primary ACC
active session time for all UEs in a cell.
1.9.6 Reference
1.10 Average Number of Simultaneous E-RABs
1.10.1 Description
This metric measures the load in the system in terms of simultaneous E-UTRAN
Radio Access Bearer (E-RAB)s.
1.10.2 Node Type
ERBS
1.10.3 Formula
The average number of E-RABs per cell is given by the following equation. The
counters are on cell level:
1/1553-CNA 403 3397 Uen F | 2018-08-10 13

pmErabLevSum
Average number of E 0 RABs = pmErabLevSamp
Equation 5 Average Number of Simultaneous E-RABs.
1.10.4 Metric Type

Count
1.10.5 Counters

pmErabLevSum Sum of all sample values recorded for Not included in SCAN
Number of simultaneous E-RABs any predefined
scanner
pmErabLevSamp Counts the number of times the Not included in SCAN
corresponding Sum counters has been any predefined
incremented. Associated ACC pmCounter scanner
pmErabLevSum.
1.10.6 Reference
1.11 Average usage of Downlink PRB
1.11.1 Description
The average use of Downlink PRB during a reporting period. The counter is on
cell level.
1.11.2 Node Type
ERBS
1.11.3 Formula
pmPrbUsedDlSum
Average usage of Downlink PRB = pmPrbUsedDlSamp
Equation 6 Average usage of Downlink PRB over a measurement period
Note: This counter is not available on DUL-20.
14 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.11.4 Metric Type

-
1.11.5 Counters

pmPrbUsedDlSum Accumulated sum of DL PRB Not included in any ACC
usage. predefined scanner
pmPrbUsedDlSamp Total number of measured Not included in any ACC
samples of DL PRB usage. predefined scanner
1.11.6 Reference
1.12 VoIP Integrity
1.12.1 Description
This KPI measures the integrity impact for VoIP in the RAN.
VoIP integrity is a measurement that shows how many percent of the VoIP users
that have 99% of their UL packets within the packet delay budget.
This KPI should be measured for voice bearer during a call. Note that video
quality measurements are not supported this way. Radio uplink channel is the
most common source for pure media and therefore the measurement is proposed
to measure voice quality on network side. This counter is stepped for all ongoing
calls and call chunks in the particular cell for a measurement period (15 Min
usually) i.e. it is possible that different parts of a single call is reported in multiple
measurement periods.
1.12.2 Node Type

ERBS
1.12.3 Formula
VoIP Integrity (%) =
1/1553-CNA 403 3397 Uen F | 2018-08-10 15

1.12.4 Metric Type

Percentage (%)
1.12.5 Counters
These counters are defined per cell.
16 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions

pmVoipQualityRb The number of VoLTE sessions (radio bearers Not includ ACC
UlOk with serviceType= VOIP) of satisfactory ed in any
quality. predefined
scanner
The counter is incremented when the VoIP
session, i.e. the time when a radio bearer
which carries VoIP traffic is established,
has had a satisfactory VoIP quality. This
means that at least the minimum required
amount of VoIP packets are available for the
measurement, and that at least 99% of the
VoIP packets for the VoIP session had an
air interface delay within the packet delay
budget. If the above conditions are met then
counters can be incremented at the end of the
ROP or at the end of the call or both of them.
pmVoipQualityRb The number of VoLTE sessions (radio bearers Not includ ACC
UlNok with serviceType= VOIP) of unsatisfactory ed in any
quality. predefined
scanner
The counter is incremented when the VoIP
session, i.e. the time when a radio bearer
which carries VoIP traffic is established, has
had an unsatisfactory VoIP quality. This can
be caused by two conditions:
• (1) At least the minimum required amount
of VoIP packets are available for the
measurement and less than 99% of the
VoIP packets for the VoIP session had an
air interface delay within the packet delay
budget.
• (2) 50% or less of the VoIP packets of
the VoIP session had an air interface
delay within the packet delay budget,
regardless of the amount of VoIP packets
for measurement.
If the above conditions are met, then counters
can be incremented at the end of the ROP or
when the voice bearer is released by ERAB
Release procedure or both of them
1.12.6 Reference
For FDD, this KPI is defined as "VoIP Integrity" in "Key Performance Indicators,
FDD", 37/1553-HSC 105 50/1-V1, Rev BA, Section 2.3.13 Reference [4].
1/1553-CNA 403 3397 Uen F | 2018-08-10 17

For TDD, this KPI is defined as "VoIP Integrity" in "Key Performance Indicators,
TDD", 37/1553-HSC 105 50/1-V2, Rev BA, Section 2.3.13 Reference [5].
1.12.7 Notes
This KPI takes both radio types into account - FDD and TDD. Averages values
are from FDD and TDD tables.
1.13 Initial E-RAB Establishment Success Rate per QCI
1.13.1 Description
by E-RABs included in the Initial UE Context setup procedure.
1.13.2 Node Type

ERBS
1.13.3 Formula
Initial E-RAB Establishment Success Rate per QCI (%) =
Note: The index value indicates that only the value for QCI 1 is considered.
1.13.4 Metric Type

Percentage (%)
18 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.13.5 Counters
The counters are on cell level, and per QCI where appropriate.

pmErabEstabAtt The total number of initial E-RAB Not included PDF
InitQci setup attempts per QCI. in any predefi
ned scanner
pmErabEstabSuc The total number of successful initial Not included PDF
cInitQci E-RAB setups per QCI. in any predefi
ned scanner
pmRrcConnEstab The total number of RRC Connection Not included PEG
AttMod Request attempts with Establishment in any predefi
cause Mobile Originating Data. ned scanner
AttMta Request attempts with Establishment in any predefi
cause Mobile Terminating Access. ned scanner
AttReattMod Request attempts that are considered in any predefi
as reattempts for Establishment ned scanner
cause Mobile Originating Data.
AttReattMta Request attempts that are considered in any predefi
as reattempts for Establishment ned scanner
cause Mobile Terminating Access.
pmRrcConnEstab The total number of failed RRC Primary PEG
FailMmeOvlMod Connection Establishments with
Establishment cause Mobile
Originating Data due to MME
overload.
pmRrcConnEstab The total number of successful Not included PEG
SuccMod RRC Connection Establishments in any predefi
for Establishment cause Mobile ned scanner
Originating Data.
pmRrcConnEstab The total number of successful Not included PEG
SuccMta RRC Connection Establishments in any predefi
for Establishment cause Mobile ned scanner
Terminating Access.
pmS1SigConnEst This measurement provides the Primary PEG
abAttMod number of S1 Signalling connection
establishment attempts with RRC
Connection Request Establishment
cause Mobile Originating Data.
1/1553-CNA 403 3397 Uen F | 2018-08-10 19


pmS1SigConnEst This measurement provides the Primary PEG
abAttMta number of S1 Signalling connection
establishment attempts with RRC
Connection Request Establishment
cause Mobile Terminating Access.
pmS1SigConnEst The total number of successful S1 Primary PEG
abSuccMod signalling connection establishments
with Establishment cause Mobile
Originating Data.
pmS1SigConnEst The total number of successful S1 Primary PEG
abSuccMta signalling connection establishments
with Establishment cause Mobile
Terminating Access.
1.13.6 Reference
For FDD, this KPI is defined as "Initial E-RAB Establishment Success Rate per
QCI" in "Key Performance Indicators, FDD", 37/1553-HSC 105 50/1-V1, Rev
BA, Section 3.1.2 Reference [4].
For TDD, this KPI is defined as "Initial E-RAB Establishment Success Rate per
QCI" in "Key Performance Indicators, TDD", 37/1553-HSC 105 50/1-V2, Rev
1.13.7 Notes
This KPI takes both radio types into account- FDD and TDD. Averages values are
from FDD and TDD tables. This KPI is limited to Voice QCI.
1.14 Added E-RAB Establishment Success Rate per QCI
1.14.1 Description
by E-RABs included in the E-RAB setup procedure.
1.14.2 Node Type

ERBS
20 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.14.3 Formula
Note: QCI[1-9] is only considered
1.14.4 Metric Type

Percentage (%)
1.14.5 Counters

pmErabEstabSuccA The total number of successful Not included in any PDF
ddedQci additional E-RAB setup per QCI. predefined scanner
Unit
pmErabEstabAttAd The total number of additional Not included in any PDF
dedQci E-RAB setup attempts per QCI. predefined scanner
Unit
pmErabEstabAttAd The number of failed Not included in any PDF
dedHoOngoingQci establishment attempts of predefined scanner
added E-RABs due to ongoing Unit
handover per QCI
1.14.6 Reference
For FDD, this KPI is defined as "Initial E-RAB Establishment Success Rate per
QCI" in "Key Performance Indicators, FDD", 37/1553-HSC 105 50/1-V1, Rev
For TDD, this KPI is defined as "Initial E-RAB Establishment Success Rate per
QCI" in "Key Performance Indicators, TDD", 37/1553-HSC 105 50/1-V2, Rev
1.14.7 Notes
This KPI Takes both radio types into account - FDD and TDD. Averages values
are from FDD and TDD tables.
1/1553-CNA 403 3397 Uen F | 2018-08-10 21

1.15 Voip Integrity DL - RTP inter arrival GAP
1.15.1 Description
The Counter is stepped when a QCI1 DRB receives a PDCP SDU (or the QCI1 DRB
is released) and there has been greater than 1 second since the previous PDCP
SDU was received on that QCI1 DRB.
Warning: This counter may measure RTP GAPs other than the active Call
state, e.g. Alerting (with pre condition or early media) and Call hold (due to
periodic RTCP (5sec)) eNB is not aware of IMS Call state (e.g. Alerting with
precondition support, ringback tone, call waiting hold etc.) resulting measurement
interpretation inaccuracy.
1.15.2 Node Type

ERBS
1.15.3 Formula
Voip Integrity DL - RTP inter arrival GAP = pmPdcpInactSecDlVolteDistr
1.15.4 Metric Type
1.15.5 Counters
Counter Description Scanner Counter

Type
pmPdcpInactSec Distribution of the number of times there has Not included in PDF
DlVolteDistr been greater than 1 second without receiving any predefined
an SDU at the DL PDCP layer on a QCI1 DRB. scanner
Table 2 PDF Ranges

[0] [1..2] s
[1] [2..3] s
[2] [3..4] s
[3] [4..5] s
[4] [5..6] s
22 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
Table 2 PDF Ranges

[5] [6..7] s
[6] [7..8] s
[7] [8..9] s
[8] [9..10] s
[9] >=10 s
1.16 Voip Integrity UL - RTP inter arrival GAP
1.16.1 Description
The Counter is stepped when a QCI1 DRB receives a PDCP SDU (or the QCI1 DRB
is released) and there has been greater than 1 second since the previous PDCP
SDU was received on that QCI1 DRB.
Warning: This counter may measure RTP GAPs other than the active Call
state, e.g. Alerting (with pre condition or early media) and Call hold (due to
periodic RTCP (5sec)) eNB is not aware of IMS Call state (e.g. Alerting with
precondition support, ringback tone, call waiting hold etc.) resulting measurement
interpretation inaccuracy.
1.16.2 Node Type

ERBS
1.16.3 Formula
Voip Integrity UL - RTP inter arrival GAP = pmPdcpInactSecUlVolteDistr
1.16.4 Metric Type

-
1.16.5 Counters

pmPdcpInactSecU Distribution of the number of times there Not included PDF
lVolteDistr has been greater than 1 second without in any
receiving an SDU at the UL PDCP layer on predefined
a QCI1 DRB. scanner
1/1553-CNA 403 3397 Uen F | 2018-08-10 23

Table 3 PDF Ranges

[0] [1..2] s
[1] [2..3] s
[2] [3..4] s
[3] [4..5] s
[4] [5..6] s
[5] [6..7] s
[6] [7..8] s
[7] [8..9] s
[8] [9..10] s
[9] >=10 s
1.16.6 Reference
This is a new KPI.
1.17 E-RAB Retainability - Percentage Lost per QCI
1.17.1 Description
This KPI measures the impact on the end user with the purpose to reflect the
percentage of established E-RAB that are lost with an abnormal release. Good
retainability will be shown by a low value metric for example, < 5%.
In a packet switched system as LTE it is natural to establish and release E-RABs.

E-RABs do not have to be released just because they are inactive, they can be kept
to have a fast access once new data arrives. The definition of an Abnormal release
is that the release of the E-RAB had a negative impact on the end-user.
1.17.2 Node Type

ERBS
1.17.3 Formula
E-RAB Retainability - Percentage Lost per QCI (%) =
24 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
Note: The index value indicates that only the value for QCI 1-9 is considered.
1.17.4 Metric Type

Percentage (%)
1.17.5 Counters
The counters are on cell level, and per QCI.

pmErabRelAbno The total number of active E-RABs Not included in PDF
rmalEnbActQci released abnormally per cell per QCI for any predefined
requests initiated by eNB (per cell per scanner
QCI). , except active E-RABs released due
to successful HO. An E-RAB is considered
to be active when there are data in the DL
or UL queues for the E-RAB.
pmErabRelAbno The total number of E-RAB Releases Not included in PDF
rmalMmeActQci (per cell per QCI) initiated by the MME any predefined
considered as abnormal. The counter is scanner
stepped if data was lost in either the UL or
DL buffers.
pmErabRelAbno The total number of E-RABs released Not included in PDF
rmalEnbQci abnormally per cell per QCI for requests any predefined
initiated by eNB. scanner
pmErabRelNorm The total number of E-RABs released Not included in PDF
alEnbQci normally (per cell per QCI) for requests any predefined
initiated by eNB. scanner
pmErabRelMmeQ The total number of E-RAB Releases Not included in PDF
ci (per cell per QCI) initiated by the MME any predefined
excluding successful handover. The scanner
counter is stepped regardless of whether
data was or was not lost in UL/DL buffers.
1.17.6 Reference
For FDD, this KPI is defined as "E-RAB Retainability - Percentage Lost per QCI" in
"Key Performance Indicators, FDD", 37/1553-HSC 105 50/1-V1, Rev BA, Section
2.2.4 Reference [4].
1/1553-CNA 403 3397 Uen F | 2018-08-10 25

For TDD, this KPI is defined as "E-RAB Retainability - Percentage Lost per QCI" in
"Key Performance Indicators, TDD", 37/1553-HSC 105 50/1-V2, Rev BA, Section
1.17.7 Notes
Takes into account both radio types - FDD and TDD. Averages values from FDD
and TDD tables. Limited to Voice QCI.
The counters are defined per cell, but in the initial release these are presented
on an eNB basis only.
1.18 IMS SBG Incoming Session Set-up Success Ratio
1.18.1 Description
This KPI shows the success rate for SBG incoming session setup.
The session setup is considered as successful when:
— The user cancels in an early dialog
— The user is not registered
— One of the following responses - Busy Here (486), Forbidden (403), Not Found
(404), Decline (603), Address Incomplete (484) or Busy Everywhere (600)
This user behavior is considered as successful from the network performance

perspective.
1.18.2 Node Type

SBG
1.18.3 Formula
SBG Incoming Session Setup Success (%) =
1.18.4 Metric Type

Percentage (%)
26 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.18.5 Counters
These counters are defined per SBG.

Type
sbgSipNet Number of incoming INVITE sessions responded to with the PEG
IncSessio following success criteria:
nEstabNet
workSucce • 1. The first time at which the SBG opens the BGF pin
ss hole (for allowing authorized early media) and receives a
successful H.248 Modify reply.
• 2. SIP 180 RINGING message.
• 3. Final “SIP 200 OK (INVITE)” message – in cases when
the terminating user has automatic answering configured.
• 4. In case CANCEL (or corresponding event) from client is
received before any response except 100 Trying is sent.
• 5. In cases when a call setup was not successfully initiated
due to faults outside of IMS system or user behavior, that
specific call setup attempt shall be considered as an IMS
successful call setup. The following user behavior factor
cases shall be taken as successful session setup:
• User is not registered
• Busy Here (486)
• Forbidden (403)
• Not Found (404)
• Decline (603) outgoing only
• Address Incomplete (484)
• Busy Everywhere (600).
sbgSipTot Total incoming session setup attempts since system started. PEG
alIncSess This is the number of sessions initiated by incoming INVITEs.
Setups The session setups may have succeeded or failed.
1.18.6 Reference
This KPI is defined as "Equation 240. IMS SBG Incoming Session Set-up Success
Ratio" in "IMS Performance Indicators", 1/154 43-HSC 113 06, Rev T3, Section
1.19 IMS SBG Outgoing Session Set-up Success Ratio
1.19.1 Description
This KPI shows the success rate for SBG outgoing session setup.
1/1553-CNA 403 3397 Uen F | 2018-08-10 27

The session setup is considered as successful when:
— The user cancels in an early dialog
— The user is not registered
— One of the following responses - Busy Here (486), Forbidden (403), Not Found
(404), Decline (603), Address Incomplete (484) or Busy Everywhere (600)
This user behavior is considered as successful from the network performance

perspective.
1.19.2 Node Type
SBG
1.19.3 Formula
SBG Outgoing Session Setup Success (%) =
1.19.4 Metric Type
Percentage (%)
1.19.5 Counters
28 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions

sbgSipNet Number of outgoing INVITE sessions responded to PEG
OutSessio with the following success criteria:
nEstabNet
workSucce • 1. The first time at which the SBG opens the BGF
ss pin hole (for allowing authorized early media) and
receives a successful H.248 Modify reply.
• 3. Final “SIP 200 OK (INVITE)” message – in cases
when the terminating user has automatic answering
configured.
• 4. In case CANCEL (or corresponding event) from
client is received before any response except 100
Trying is sent.
• 5. In cases when a call setup was not successfully
initiated due to faults outside of IMS system or user
behavior, that specific call setup attempt shall be
considered as an IMS successful call setup. The
following user behavior factor cases shall be taken as
successful session setup:
• User is not registered
• Busy Here (486)
• Forbidden (403)
• Not Found (404)
• Decline (603) outgoing only
• Address Incomplete (484)
• Busy Everywhere (600).
sbgSipTot The number of outgoing session setup attempts. This is PEG
alOutSess the number of sessions initiated by outgoing INVITEs.
Setups The session setups may have succeeded or failed.
1.19.5.1 Reference
This KPI is defined as "Equation 241. IMS SBG Outgoing Session Set-up Success
1.20 IMS A-SBG Initial Registration Success Ratio
1.20.1 Description
This KPI shows the success of SBG Initial Registration Setup.
1/1553-CNA 403 3397 Uen F | 2018-08-10 29

IMS Registration Accessibility is defined as the probability of being able to

successfully register, re-register, and de-register into the IMS network.
1.20.2 Node Type

SBG
1.20.3 Formula
Note: This equation covers the deployment where SGC or P-CSCF is the entry
point to the IMS network. The registration is considered as successful
for response codes; “400 Bad Request”, “403” (Many reasons. e.g.
“Forbidden”), “403 No Roaming Agreement from Current Network”, “403
User Not Authorized”.
1.20.4 Metric Type

Percentage (%)
1.20.5 Counters
These counters are defined per A-SBG.

sbgSipRegStatI This counter holds the number of initial PEG
nitialAccCnt registration sessions accepted by the CSCF for
this access network.
sbgSipRegStatI This counter holds the number of initial PEG
nitialAttCnt registration attempts received by the SGC for this
access network. Responses to authentication
challenge are not included.
sbgSipRegStatR This counter holds the total number of initial PEG
ejInitialRegCn registrations rejected by the SGC or the core
t400 with '400 Bad Request' for this access network.
Registration query is not counted.
30 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions

t403 with '403 Forbidden' for this access network.
t404 with '404 Not Found' for this access network.
1.20.6 Reference
This KPI is defined as "Equation 236. IMS A-SBG Initial Registration Success
Ratio " in "IMS Performance Indicators", 1/154 43-HSC 113 06, Rev T3, Section
1.21 IMS SBG SRVCC Access Transfer Success Ratio
1.21.1 Description
This KPI shows the success rate for SBG SRVCC access transfers.
IMS Session Retainability is defined as the probability of being able to successfully

complete (normally terminate) an active session in the IMS network once it has
been successfully setup.
1.21.2 Node Type

SBG
1.21.3 Formula
Note: This formula is applicable for the ATCF specific CS network in SBG for
incoming SRVCC requests and responses.
1.21.4 Metric Type
Percentage (%)
1/1553-CNA 403 3397 Uen F | 2018-08-10 31

1.21.5 Counters

Type
sbgSipSuccessI Number of successfully answered incoming INVITE PEG
ncSessions sessions. (picking up the call). This counter belongs to
measurement family 'SIP session statistics'.
sbgSipTotalInc Total incoming session setup attempts since system PEG
SessSetups started. This is the number of sessions initiated by
incoming INVITEs. The session setups may have
succeeded or failed.
sbgSipRejected This counter holds the total number of incoming PEG
IncAlertingSes PS to CS SRVCC access transfer INVITEs that are
sions488 rejected by SGC with response code 488, due to lack of
SRVCC support during alerting phase. The counter is
applicable only for CS network.
sbgSipRejected This counter holds the total number of incoming initial PEG
IncPreAlerting access transfer INVITEs that are rejected by SGC with
Sessions488 response code 488, due to lack of SRVCC support
during alerting phase. The counter is applicable only
for CS network
1.21.6 Reference
This KPI is defined as "Equation 27. IMS SBG SRVCC Access Transfer Success
Ratio " in "IMS Performance Indicators", 1/154 43-HSC 113 06, Rev T3, Section
1.22 IMS SBG Incoming Sessions Set-up Time
1.22.1 Description
This KPI shows the time taken for SBG incoming session setup in milliseconds
where the originating user initiates a session setup.
The time period between when the IMS network receives an SIP INVITE
corresponding to when a user initiates an IMS session by e.g. pressing the session
setup button, and when the IMS network sends a SIP 180 Ringing or SIP 200 OK
response corresponding to when the originating user receives a callee alerted
notification, or in the case that terminating phone is configured to use automatic
answer, the originating user receives a notification that the session has been
set up.
32 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.22.2 Node Type

SBG
1.22.3 Formula
SBG Incoming Session Setup Time (ms) =
1.22.4 Metric Type

Milliseconds (ms)
1.22.5 Counters
1/1553-CNA 403 3397 Uen F | 2018-08-10 33


Type
sbgSipNetIncSe Increased with the time in milliseconds between the PEG
ssionSetupTime received initial INVITE and the first sent response with
the following success criteria:
• 1. The first time at which the SBG opens the BGF
pin hole (for allowing authorized early media) and
• 3. Final “SIP 200 OK (INVITE)” message – in
cases when the terminating user has automatic
answering configured. The mean response time
can be calculated by dividing this counter with
sbgSipNetIncSessionSetupUserSuccess.
Counter on SBG node.
sbgSipNetIncSe Number of incoming INVITE sessions responded to PEG
ssionSetupUser with the following success criteria:
Success
pin hole (for allowing authorized early media) and
• 3. Final “SIP 200 OK (INVITE)” message – in cases
when the terminating user has automatic answering
configured.
1.22.6 Reference
This KPI is defined as "Equation 36. IMS SBG Incoming Sessions Set-up Time"
in "IMS Performance Indicators", 1/154 43-HSC 113 06 Rev T3, Section 3.8.2
Reference [6].
1.23 IMS SBG Outgoing Sessions Set-up Time
1.23.1 Description
This KPI shows the time taken for SBG outgoing session setup in milliseconds for
the terminating case.
34 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
The time period between when the IMS network receives an SIP INVITE
corresponding to when a user initiates an IMS session by e.g. pressing the session
setup button, and when the IMS network sends a SIP 180 Ringing or SIP 200
OK response corresponding to when the originating user receives a call alerted
notification, or in the case that terminating phone is configured to use automatic
answer, the originating user receives a notification that the session has been
set up.
1.23.2 Node Type

SBG
1.23.3 Formula
SBG Outgoing Session Setup Time (ms) =
1.23.4 Metric Type

Milliseconds (ms)
1.23.5 Counters
1/1553-CNA 403 3397 Uen F | 2018-08-10 35


sbgSipNetOutSe Increased with the time in milliseconds between PEG
ssionSetupTime the sent initial INVITE and the first received
response with the following success criteria:
pin hole (for allowing authorized early media)
and receives a successful H.248 Modify reply.
• Final “SIP 200 OK (INVITE)” message – in
answering configured. The mean response time
can be calculated by dividing this counter with
sbgSipNetOutSessionSetupUserSuccess. Not
applicable to CS network since calls terminating
on CS network are not supported.
sbgSipNetOutSe Number of outgoing INVITE sessions responded PEG
ssionSetupUser to with the following success criteria:
Success
pin hole (for allowing authorized early media)
and receives a successful H.248 Modify reply.
• Final “SIP 200 OK (INVITE)” message – in
answering configured.
1.23.6 Reference
This KPI is defined as "Equation 37. IMS SBG Outgoing Sessions Set-up Time"
in "IMS Performance Indicators", 1/154 43-HSC 113 06 Rev T3, Section 3.8.2
Reference [6].
1.24 IMS A-SBG Initial Registration Time
1.24.1 Description
This KPI shows the time taken for SBG initial registration in milliseconds.
36 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
IMS Initial Registrations time is defined as the time period between, when a
user initiates an IMS initial registration and when the originating user receives
notification that the registration attempt is initiated or completed.
1.24.2 Node Type

SBG
1.24.3 Formula
SBG Initial Registration Time (ms) =
1.24.4 Metric Type

Milliseconds (ms)
1.24.5 Counters

Type
sbgInitRegTime This value represents the total time for initial register PEG
requests. The time is measured from when the
request arrives at the SGC until the 200 OK response
is sent back to the client. Time is only measured for
initial registers that gets a 2xx response, in particular
time is not measured for a 401 response or for any
subsequent re-register request. This value contains
the sum of all such initial register times. This value is
in milliseconds. Counter on A-SBG node.
sbgSipRegStatI This counter holds the number of initial registration PEG
nitialAccCnt sessions accepted by the CSCF for this access network.
Counter on A-SBG node.
1.24.6 Reference
This KPI is defined as "Equation 9 . IMS SBG Initial Registration Time" in "IMS
Performance Indicators", 1/154 43-HSC 113 06 Rev T3, Section 3.4.2 Reference
[6].
1/1553-CNA 403 3397 Uen F | 2018-08-10 37

1.25 SBG Total successful transfers in IMS
1.25.1 Description
This KPI shows the total number of successful SBG transfers.
1.25.2 Node Type

SBG
1.25.3 Formula
SBG Total Successful Transfers =
1.25.4 Metric Type
1.25.5 Counters

Type
sbgSipSucces Number of successfully answered (by 200 Ok) incoming PEG
sIncSessions INVITE sessions. (picking up the call / media transfer from
access to CS network). Sucessfully answered re-INVITEs
on an already established dialog are not counted here.
1.25.6 Reference
This is a new KPI.
1.26 IMS SBG Media RTP Lost Packets Ratio
1.26.1 Description
This KPI shows the percentage of SBG Media RTP Lost Packets.
38 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.26.2 Node Type

SBG
1.26.3 Formula
SBG Media RTP Lost Packets (%) =
1.26.4 Metric Type

Percentage (%)
1.26.5 Counters

sbgSgcPktsLostRa Ratio of Sgc network connections lost RTP GAUGE
tioGauge packets. The number is 10000*ratio. Only
applicable for RTP streams.
1.26.6 Reference
This KPI is defined as "Equation 249. IMS SBG Media RTP Lost Packets Ratio"
in "IMS Performance Indicators", 1/154 43-HSC 113 06 , Rev T3, Section 8.3.5
Reference [6].
1.27 IMS SBG Media RTP Out of Sequence Packets Ratio
1.27.1 Reference
RTCP reports contain packet loss and jitter for end-to-end media flows.
1.27.2 Node Type

SBG
1/1553-CNA 403 3397 Uen F | 2018-08-10 39

1.27.3 Formula
SBG Media RTP Lost Packets (%) =
1.27.4 Metric Type

Percentage (%)
1.27.5 Counters
Table 4
Type
sbgSgcPktsOutof The ratio of the number of packets that arrived GAUGE
SeqRatioGauge out of sequence to the total number of received
packets on the network connection since the
last SBG restart.
1.27.6 Reference
This KPI is defined as "Equation 250. IMS SBG Media RTP Lost Packets Ratio"
in "IMS Performance Indicators", 1/154 43-HSC 113 06, Rev T3, Section 8.3.5
Reference [6].
1.28 IMS SBG Incoming Priority Session Set-up Success Ratio
1.28.1 Description
This KPI shows the percentage of SBG Priority Call Establishment Successes.
1.28.2 Node Type

SBG
40 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.28.3 Formula
SBG Incoming Priority Session Set-up Success Ratio (%) =
1.28.4 Metric Type

Percentage (%)
1.28.5 Counters

Type
sbgSgcIn The number of incoming priority call attempts per network, PEG
cPriorit including the priority calls that are either successful or failed.
yCallAtt The attribute is a counter and is specific to a particular
empts network. For each network, the counter shows the number
of priority call attempts that have been originated from
that network. This counter is incremented per network for a
priority call at the reception of an initial INVITE. This counter
belongs to the family 'Priority Service Statistics'.
sbgSgcIn The number of incoming priority calls that were successful. PEG
cPriorit The attribute is a counter and is specific to a particular
yCallSuc network. For each network, the counter shows the number of
cessSetu successful priority calls that have been originated from that
ps network. This counter is incremented for a network when the
200 OK for an initial priority call INVITE is forwarded to that
network. This counter belongs to the family 'Priority Service
Statistics'.
1.28.6 Reference
This KPI is defined as "Equation 243. IMS SBG Incoming Priority Session Set-up
Success Ratio" in "IMS Performance Indicators", 1/154 43-HSC 113 06, Rev T3,
Section 8.3.2 Reference [6].
1/1553-CNA 403 3397 Uen F | 2018-08-10 41

1.29 IMS SBG Emergency Session Set-up Success Ratio
1.29.1 Description
This KPI shows the percentage of SBG Emergency Call Establishment Successes.
1.29.2 Node Type

SBG
1.29.3 Formula
SBG Emergency Call Establishment Success (%) =
1.29.4 Metric Type
Percentage (%)
1.29.5 Counters

sbgSgcTotalEme Total number of emergency calls or call-back PEG
rgencyCallsSet setups. Emergency call-back setups are
ups counted on the core network connection.
sbgSgcTotalEme Total number of successful incoming PEG
rgencyCallsSuc emergency calls or call-back setups. Successful
cess emergency calls are counted on Access and
Foreign networks. Successful emergency
call-back setups are counted only on the core
network connection.
1.29.6 Reference
This KPI is defined as "Equation 242. IMS SBG Emergency Session Set-up Success
Ratio" in "IMS Performance Indicators", 1/154 43-HSC 113 06 , Rev T3, Section
42 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.30 IMS A-SBG Emergency Initial Registration Success Ratio
1.30.1 Description
This KPI shows the count of successful initial emergency registrations in SGC
during a reporting period.
1.30.2 Formula
1.30.3 Metric Type

Percentage (%)
1.30.4 Counters

Type
sbgSipEmerRegSt This counter holds the number of initial emergency PEG
atInitialAccCnt registrations accepted by the CSCF for this access
network.
sbgSipEmerRegSt This counter holds the number of initial emergency PEG
atInitialAttCnt registration attempts received by the SGC for this
access network. Responses to authentication
challenge are not included.
1.30.5 Reference
This KPI is defined as "Equation 238. IMS A-SBG Emergency Initial Registration
Success Ratio" in "IMS Performance Indicators", 1/154 43-HSC 113 06 , Rev T3,
1/1553-CNA 403 3397 Uen F | 2018-08-10 43

1.31 MSC SRVCC from LTE success rate per MME
1.31.1 Description
This KPI shows the success rate for Single Radio Voice Call Continuity (SRVCC)
procedure from LTE to CS.
The SRVCC procedure success rate is calculated as the quotient of the measured
values of successfully executed SRVCC procedures and the total number of
requests received on the Sv-Interface. All requests are counted including requests
to a not supported target. An SRVCC procedure is considered successful when all
related signalling on D-, Iu-, A-, and E-Interface is successfully completed and
on the Mw-Interface either INFO (alerting) or INFO (pre-alerting) or 200 OK
(INVITE) without prior INFO (alerting or pre-alerting) is received.
1.31.2 Node Type

MSC
1.31.3 Formula
MSC SRVCC from LTE Success for MME (%) =
1.31.4 Metric Type

Percentage (%)
1.31.5 Counters
These counters are defined per connected MME.
OBJECTTYPE: MMESV

P2CCOMPLACK Number of successfully completed SRVCC PEG
procedures
P2CREQUTOT Number of SRVCC procedure requests PEG
44 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.31.6 Reference
This KPI is defined as "MSC SRVCC from LTE success rate per MME" in "List
of Performance Indicators", 36/155 18-CSA 121 01/9, Rev. B, Section 3.3.17
Reference [7].
1.32 MSC SRVCC from LTE Success for MSC
1.32.1 Description
This KPI shows the success rate for Single Radio Voice Call Continuity (SRVCC)
procedure from LTE to CS.
The SRVCC procedure success rate is calculated as the quotient of the measured
values of successfully executed SRVCC procedures and the total number of
requests received on the Sv-Interface. All requests are counted including requests
to a not supported target. An SRVCC procedure is considered successful when all
related signalling on D-, Iu-, A-, and E-Interface is successfully completed and
on the Mw-Interface either INFO (alerting) or INFO (pre-alerting) or 200 OK
(INVITE) without prior INFO (alerting or pre-alerting) is received.
1.32.2 Node Type

MSC
1.32.3 Formula
MSC SRVCC from LTE Success for MSC (%) =
m: number of MMEs
1.32.4 Metric Type

Percentage (%)
1.32.5 Counters
These counters are defined per connected MME.
1/1553-CNA 403 3397 Uen F | 2018-08-10 45

OBJECTTYPE: MMESV

P2CCOMPLACK Number of successfully PEG
completed SRVCC procedures
P2CREQUTOT Number of SRVCC procedure PEG
requests
1.32.6 Reference
This KPI is defined as "SRVCC from LTE success rate per MSC" in "List of
Performance Indicators", 36/155 18-CSA 121 01/9, Rev. B, Section 3.3.17
Reference [7].
1.33 MSC Relocation success rate to target RNC
1.33.1 Description
This KPI shows the WCDMA success rate for SRVCC procedure from LTE to CS on
the Iu-Interface.
On the Iu-Interface, the relocation success rate for SRVCC procedures towards
the WCDMA RAN connected to the MSC is measured.
1.33.2 Node Type
MSC
1.33.3 Formula
MSC Relocation Success for Target RNC (%) =
1.33.4 Metric Type

Percentage (%)
46 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.33.5 Counters
These counters are defined per connected MSC.
OBJECTTYPE: SRVCC2U

NRELREQSUCC Number of successful relocation PEG
requests sent to the target RNC
NRELREQTOT Number of relocation request PEG
messages sent to the target RNC
1.33.6 Reference
This KPI is defined as "Relocation success rate to all target MSCs, WCDMA" in "List
of Performance Indicators", 36/155 18-CSA 121 01/9, Rev. B, Section 3.3.19
Reference [7].
1.34 MSC Relocation success rate to target MSC,WCDMA
1.34.1 Description
This KPI shows the WCDMA success rate for SRVCC procedure from LTE to CS
on the E-Interface.
On the E-Interface, the relocation success rate for SRVCC procedures towards the
WCDMA RAN connected to neighboring MSCs is measured per neighboring MSC
and for all neighboring MSCs.
1.34.2 Node Type
MSC
1.34.3 Formula
MSC Relocation Success for Target MSC (%) =
1/1553-CNA 403 3397 Uen F | 2018-08-10 47

n is the number of neighboring MSCs
1.34.4 Metric Type

Percentage (%)
1.34.5 Counters
These counters are defined per connected MSC.
OBJECTTYPE: NBRMSCS2U

Type
NS2UASUCC Number of successful LTE to WCDMA PEG
handovers to neighboring MSC.
NS2UATOT Number of LTE to WCDMA handover attempts PEG
to neighboring MSC.
1.34.6 Reference
This KPI is defined as "Relocation success rate to all target RNCs" in "List of
Performance Indicators", 36/155 18-CSA 121 01/9, Rev. B, Section 3.3.19
Reference [7].
1.35 IMS CSCF Third Party Registration Success Ratio
1.35.1 Description
This KPI shows the success of third party registration.

1.35.2 Node Type

CSCF
1.35.3 Formula
CSCF Third Party Registration Success Ratio (%)=
48 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.35.4 Metric Type

Percentage (%)
1.35.5 Counters
These counters are defined per S-CSCF.

scscfThirdPar Number of successful third party registration PEG
tyRegistratio procedures in the S-CSCF.
nSuccess
scscfThirdPar Number of failed third party registration PEG
tyRegistratio procedures in the S-CSCF. This counter is keyed
nFailure with the SIP response code. There is also a SUM
key, which is incremented for all response codes.
1.35.6 Reference
This KPI is defined as "Equation 5. IMS CSCF Third Party Registration Success
Ratio", in "IMS Performance Indicators", 1/154 43-HSC 113 06 Rev T3, Section
1.36 IMS CSCF EATCF SRVCC Access Transfer Success Ratio
1.36.1 Description
This KPI shows the success of third party registration.

1.36.2 Node Type

CSCF
1/1553-CNA 403 3397 Uen F | 2018-08-10 49

1.36.3 Formula
CSCF Third Party Registration Success Ratio (%)=
1.36.4 Metric Type

Percentage (%)
1.36.5 Counters
These counters are defined per S-CSCF.

Type
eatfSuccessful The number of successful Emergency SR-VCC PEG
EmergencySessi Access Transfer in EATF. Incremented by 1 when
onAccessTransf EATF receives an ACK of an emergency SR-VCC
er access transfer request from the CS UE.
eatfFailedEmer The number of failed Emergency SR-VCC Access PEG
gencySessionAc Transfer in EATF. This counter is keyed on the
cessTransfer negative response code (3xx-6xx) and SUM. The
SUM key represent the total number of failed
Emergency SR-VCC Access Transfer in EATF.
Incremented by 1 when EATF responds to an
emergency SR-VCC access transfer request with a
negative response (3xx-6xx).
1.37 S5 Create Session Failure per APN (IMS) ratio
1.37.1 Description
This KPI shows the failure rate for S5 session creation per APN.
The PGW create EPS bearer failure ratio denotes the probability of a failed attempt
to create a default EPS bearer (a new PDN connection), or a dedicated EPS bearer
(extension of an existing PDN connection) on the S5/S8, GTP-based S2a, and S2b
interfaces. All types of rejections and failures are included, such as the following:
— Rejection due to Online Charging System (OCS) quota denial
50 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
— Terminal errors
— User errors
— RADIUS server errors
— Time-outs
1.37.2 Node Type

GGSN
1.37.3 Formula
PGW Create Session Failure =
1.37.4 Metric Type

-
1.37.5 Counters
These counters are defined per APN for each PGW.

Type
pgwApnAttempted The total number of attempted IPv4, IPv6, PEG
EpsBearerActiva and IPv4v6 EPS bearer activations associated
tion with the APN on the PGW S5/S8, GTP
S2a/S2b interfaces.
pgwApnCompleted The total number of successful IPv4, IPv6, PEG
EpsBearerActiva and IPv4v6 EPS bearer activations associated
tion with the APN on the PGW S5/S8, GTP S2a
and GTP S2b interface.
1/1553-CNA 403 3397 Uen F | 2018-08-10 51

1.37.6 Reference
This KPI is defined as "Equation 5 PGW Create EPS Bearer Failure Ratio" in "EPG
Characteristics", 14/221 02-AXB 250 12-V2, Rev CS, Section 4.1.1.2 Reference
[11].
1.38 MME - SRVCC to WCDMA failure ratio
1.38.1 Description
The SRVCC to WCDMA failure ratio shows the MME view of the probability to
experience an SRVCC toward WCDMA failure. This KPI does not include the
probability of the complete call handling procedure being unsuccessful.
1.38.2 Node Type

SGSN
1.38.3 Formula
MME SRVCC to WCDMA Failure =
1.38.4 Metric Type
1.38.5 Counters
These counters are defined per MME.
52 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions

VS.MM.SrvccCsO This measurement provides the number PEG
nlyToWAtt.E of attempted SRVCC CS Only procedures
to WCDMA in the MME. It is incremented
when a Handover Required message with
the SRVCC HO Indication IE indicating 'CS
only' is received from the eNodeB over the
S1-MME interface.
VS.MM.SrvccCsO This measurement provides the number PEG
nlyToWSucc.E of successful SRVCC CS only procedures
to WCDMA in the MME. It is incremented
each time an SRVCC CS only procedure is
successfully concluded, at the reception of
an SRVCC PS to CS Complete Notification
message from the MSC server over the Sv
interface.
VS.MM.SrvccCsA This measurement provides the number of PEG
ndPsToWAtt.E attempted SRVCC CS and PS procedures
from LTE to WCDMA. It is incremented
when a Handover Required message with
the SRVCC HO Indication IE indicating "CS
and PS" is received from the eNodeB.
ndPsToWSucc.E successful SRVCC CS and PS procedures
from LTE to WCDMA. It is incremented
when both an SRVCC PS to CS Complete
Notification message from the MSC and a
Forward Relocation Complete Notification
from the SGSN is received.
ndPsToWCsSuccP SRVCC CS and PS procedures from LTE to
sFailed.E WCDMA where the CS part is successful
but the PS part fails. This counter is
incremented when a PS to CS Complete
Notification is received from MSC and a
Forward Relocation Response or Forward
Relocation Complete Notification either
times out or is received with cause code
indicating failure reported by the SGSN.
1.38.6 Reference
This KPI is defined as "SRVCC to GERAN Failure Ratio" in "LTE KPIs", 38/006
51-AXB 250 17, Rev FU, Section 2.3 Reference [8].
1/1553-CNA 403 3397 Uen F | 2018-08-10 53

1.39 MME - SRVCC to GERAN failure ratio
1.39.1 Description
The SRVCC to GERAN failure ratio specifies the MME probability to experience an
SRVCC toward GERAN failure. This KPI does not include the probability of the
complete call handling procedure being unsuccessful.
1.39.2 Node Type

MME
1.39.3 Formula
MME SRVCC to GERAN Failure Ratio=
1.39.4 Metric Type
1.39.5 Counters

Type
VS.MM.SrvccCsO This measurement provides the number of PEG
nlyToGAtt.E attempted SRVCC CS Only procedures to
GSM in the MME. It is incremented when
a Handover Required message with the
SRVCC HO Indication IE indicating "CS
only" is received from the eNodeB over the
S1-MME interface.
VS.MM.SrvccCsO This measurement provides the number of PEG
nlyToGSucc.E successful SRVCC CS only procedures to
GSM in the MME. It is incremented each time
an SRVCC CS only procedure is successfully
concluded, at the reception of an SRVCC PS
to CS Complete Notification message from
the MSC server over the Sv interface.
54 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.39.6 Reference
This KPI is defined as "SRVCC to GERAN Failure Ratio" in "LTE KPIs", 38/006
51-AXB 250 17, Rev FU, Section 2.5 Reference [8].
1.40 MME: Total SRVCC Attempts
1.40.1 Description
This KPI gives the total number of MME SRVCC attempts, i.e. IRAT handovers
with an ongoing VoLTE media session.
1.40.2 Node Type
MME
1.40.3 Formula
MME Total SRVCC Attempts =
1.40.4 Metric Type
1.40.5 Counters

Type
VS.MM.SrvccCsO This measurement provides the number of attempted PEG
nlyToWAtt.E SRVCC CS Only procedures to WCDMA in the MME. It
is incremented when a Handover Required message
with the SRVCC HO Indication IE indicating 'CS only' is
received from the eNodeB over the S1-MME interface.
VS.MM.SrvccCsA This measurement provides the number of attempted PEG
ndPsToWAtt.E SRVCC CS and PS procedures from LTE to WCDMA. It
is incremented when a Handover Required message
with the SRVCC HO Indication IE indicating "CS and
PS" is received from the eNodeB.
1/1553-CNA 403 3397 Uen F | 2018-08-10 55

1.41 MME Dedicated Bearer Activation Success
1.41.1 Description
This KPI shows the percentage of MME Dedicated Bearer Activation Successes.
Only values of QCI=1 (Voice) are used.
1.41.2 Node Type

MME
1.41.3 Formula
MME Dedicated Bearer Activation Success (%) =
Note: The index value indicates that only the value for QCI 1 is considered.
1.41.4 Metric Type

Percentage (%)
1.41.5 Counters

VS.SM.CreateD This measurement provides the number of PEG
edicatedBeare attempted EPS Bearer Activations for dedicated
rQCIAtt.E bearers with the indexed QCI on S11, initiated
from SGW/PGW towards MME. For each Create
Bearer Request for the indexed QCIs, this counter
is incremented with the number of bearers
included in the request.
edicatedBeare successful EPS Bearer Activations for dedicated
rQCISucc.E bearers with the indexed QCI on S11, initiated
from SGW/PGW towards MME. For each
successful Create Bearer Request for the indexed
QCIs, this counter is incremented with the number
of successful bearers included in the request.
56 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.41.6 Reference
This KPI is derived from "Dedicated Bearer Activation Failure Ratio per QCI" in
"LTE KPIs", 38/006 51-AXB 250 17, Rev EY, Section 1.7 Reference [8].
1.42 MME VoLTE Uptake
1.42.1 Description
This KPI shows the percentage of MME Dedicated Bearer Activation Successes
that can be attributed to QCI 1 compared to the total.
1.42.2 Node Type

MME
1.42.3 Formula
MME VoLTE Uptake (%) =
1.42.4 Metric Type

Percentage (%)
1.42.5 Counters

edicatedBeare attempted EPS Bearer Activations for dedicated
rQCIAtt.E bearers with the indexed QCI on S11, initiated
from SGW/PGW towards MME. For each Create
Bearer Request for the indexed QCIs, this
counter is incremented with the number of
bearers included in the request.
1/1553-CNA 403 3397 Uen F | 2018-08-10 57

1.42.6 Reference
The counter is defined in "LTE KPIs", 38/006 51-AXB 250 17, Rev EY, Section
1.7 Reference [8].
1.43 IMS MMTEL AS Originating Session Set-up Success Ratio
1.43.1 Description
This KPI shows the success rate for MTAS originating session setup.
IMS MTAS Session Retainability is defined as the probability of being able to

successfully complete (normally terminate) an active IMS MTAS session.
1.43.2 Node Type

MTAS
1.43.3 Formula
1.43.4 Metric Type

Percentage (%)
1.43.5 Counters
These counters are defined per MTAS.
58 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions

Type
MtasMmtOrigNet The accumulated number of successful MMTel PEG
workSuccessSes session establishments counted by the originating
sionEstablish MTAS. The response code (180 or 200) or string "
sum " is used as key. One instance of the counter
shall count sum of all events causing the counter
to increment in case with key= " sum " . Condition:
The counter is incremented when sending 180
message on initial INVITE or when sending 200
OK (INVITE) if no 180 message has been sent.
MtasMmtOrigUnr The accumulated number of successful PEG
egNetworkSucce MMTel session establishments counted by the
ssSessionEstab unregistered originating MTAS.The response code
lish (180 or 200) or string " sum " is used as key. One
instance of the counter shall count sum of all
events causing the counter to increment in case
with key= " sum " . Condition: The counter is
incremented when sending 180 message on initial
INVITE or when sending 200 OK (INVITE) if no
180 message has been sent.
MtasMmtOrigFai The accumulated number of failed MMTel PEG
ledAttemptCaus INVITEs, counted by the originating MTAS. The
e cause code and reason is used as key.The counter
is incremented when receiving 3xx/4xx/5xx/6xx
messages.
MtasMmtOrigUnr Number of received 3xx/4xx/5xx/6xx messages, PEG
egFailedAttemp by the originating unregistered MTAS. The counter
tCause is keyed with Status-code from 3xx-6xx response
and Reason phrase.Incremented by 1 when
receiving 3xx/4xx/5xx/6xx messages.
MtasMmtInitOri The accumulated number of MMTel session PEG
gSessOk attempts, in the originating MTAS, which was
either answered, not answered, or was rejected
by a service due to operator or user configuration.
The counter is keyed on the CSCF IP address.The
counter is incremented by 1 in the originating
MTAS when the INVITE-ACK transaction has
concluded after the final response or when the
INVITE was rejected by a service due to operator
or user configuration.
1/1553-CNA 403 3397 Uen F | 2018-08-10 59


Type
MtasMmtInitOri The counter is incremented by 1 in the originating PEG
gSessNOkE MTAS, if the INVITE-ACK transaction did not
conclude successfully or receiving a 4xx, 5xx,
or 6xx as the final response, or any signaling
transactions to external nodes failed or timed
out and the configuration of the MTAS required
the interaction with the external node to be
successful in order to proceed the session. The
counter will only be stepped for one of the reasons
(once, that is) for a particular session setup.The
accumulated number of MMTel session attempts,
in the originating MTAS, which was rejected due
to node external reasons. If the rejection is due to
the absence of a license; "LICENSES" will be used
as key.If the rejection is due to the absence of a
business license; "BL-LICENSES" will be used as
key. Otherwise the CSCF IP address will be used
as key.
MtasMmtInitOri The accumulated number of MMTel session PEG
gSessNOKI attempts, in the originating MTAS, which was
rejected due to node internal reasons. The counter
is keyed on the CSCF IP address.The counter is
incremented by 1 if the INVITE was rejected due
to processor, memory shortage or by other node
internal reason.
MtasMMtInitOri The total number of MMTel call attempts, PEG
gUnregSessNoKI in originating MTAS from an unregistered
user, which was rejected due to node internal
reasons. The counter is keyed with CSCF IP
address.Incremented by 1 if INVITE was rejected
due to processor/memory shortage.
60 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions

Type
MtasMMtInitOri Incremented by 1 in originating MTAS if; The PEG
gUnregSessNoKE INVITE-ACK transaction did not conclude
successfully or any signaling transactions towards
external nodes failed or timed out and the
configuration of MTAS required the interaction
with the external node to be successful in order to
proceed the call. The counter will only be stepped
for one of the reasons (i.e. once) for a particular call
setup.The total number of MMTel call attempts,
in originating MTAS from an unregistered user,
which was rejected due to node external reasons.
If the rejection is due to the absence of a license;
"LICENSES" will be used as key.If the rejection
is due to the absence of a business license;
"BL-LICENSES" will be used as key. Otherwise the
CSCF IP address will be used as key.
MtasMmtInitOri The total number of MMTel call attempts, in PEG
gUnregSessOk originating MTAS from an unregistered user,
which was either answered, not answered or
was rejected by a service due to operator or user
configuration. The counter is keyed with CSCF IP
address.Incremented by 1 in originating MTAS
when the INVITE-ACK transaction has concluded
after the final response or when the INVITE was
rejected by a service due to operator or user
configuration.
1.43.6 Reference
This KPI is defined as "Equation 110. IMS MMTEL AS Originating Session Set-up
Success Ratio " in "IMS Performance Indicators", 1/154 43-HSC 113 06, Rev T3,
1.44 IMS MMTEL AS Terminating Session Set-up Success

Ratio
1.44.1 Description
This KPI shows the success rate for MTAS terminating session setup.

1/1553-CNA 403 3397 Uen F | 2018-08-10 61

1.44.2 Node Type
MTAS
1.44.3 Formula
1.44.4 Metric Type

Percentage (%)
1.44.5 Counters

Type
MtasMmtTermNet The accumulated number of successful MMTel session PEG
workSuccessSes establishments counted by the terminating MTAS. The
sionEstablish response code (180 or 200) or string " sum " is used as
key.One instance of the counter shall count sum of all
events causing the counter to increment in case with
key= " sum " . Condition: The counter is incremented
when sending 180 message on initial INVITE or when
sending 200 OK (INVITE) if no 180 message has been
sent.
62 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions

Type
MtasMmtTermUnr The accumulated number of successful MMTel PEG
egNetworkSucce session establishments counted by the unregistered
ssSessionEstab terminating MTAS. The response code (180 or 200) or
lish string ' sum ' is used as key.One instance of the counter
shall count sum of all events causing the counter to
increment in case with key= " sum " . Condition: The
counter is incremented when sending 180 message on
initial INVITE or when sending 200 OK (INVITE) if no
180 message has been sent.
MtasMmtTermFai The accumulated number of failed MMTel INVITEs PEG
ledAttemptCaus made to registered PUIs, counted by the terminating
e MTAS. The cause code and reason is used as
key.The counter is incremented when receiving
3xx/4xx/5xx/6xx messages.
MtasMmtTermUnr The accumulated number of failed MMTel INVITEs PEG
egFailedAttemp made to unregistered PUIs, counted by the
tCause terminating MTAS. The cause code and reason is used
as key.The counter is incremented when receiving
3xx/4xx/5xx/6xx messages.
MtasMmtInitTer The accumulated number of MMTel session attempts, PEG
mSessOk in the terminating MTAS, which was either answered,
not answered, or was rejected by a service due to
operator or user configuration. The counter is keyed
on the CSCF IP address.The counter is incremented
by 1 in the terminating MTAS when the INVITE-ACK
transaction has concluded after receiving the final
response or when the INVITE was rejected by a service
due to operator or user configuration.
MtasMmtInitTer The counter is incremented by 1 in the terminating PEG
mSessNOKI MTAS if; the INVITE-ACK transaction did not conclude
successfully or any signaling transactions to external
nodes failed or timed out and the configuration of
the MTAS required the interaction with the external
node to be successful in order to proceed the session.
The counter will only be stepped for one of the
reasons (once, that is) for a particular session.The
accumulated number of MMTel session attempts, in
the terminating MTAS, which was rejected due to node
external reasons. If the rejection is due to the absence
of a license; "LICENSES" will be used as key.If the
rejection is due to the absence of a business license;
1/1553-CNA 403 3397 Uen F | 2018-08-10 63


Type
MtasMmtInitTer The counter is incremented by 1 in the terminating PEG
mSessNOkE MTAS if; the INVITE-ACK transaction did not conclude
nodes failed or timed out and the configuration of
the MTAS required the interaction with the external
node to be successful in order to proceed the session.
The counter will only be stepped for one of the
reasons (once, that is) for a particular session.The
accumulated number of MMTel session attempts, in
the terminating MTAS, which was rejected due to node
external reasons. If the rejection is due to the absence
of a license; "LICENSES" will be used as key.If the
rejection is due to the absence of a business license;
MtasMMtInitTer The accumulated number of MMTel session attempts, PEG
mUnregSessNoKI in the terminating MTAS, to an unregistered PUI,
which was rejected due to node internal reasons. The
counter is keyed on the CSCF IP address.The counter
is incremented by 1 if the INVITE was rejected due to
processor, memory shortage or by other node internal
reason.
MtasMMtInitTer The counter is incremented by 1 in the terminating PEG
mUnregSessNoKE MTAS if; The INVITE-ACK transaction did not conclude
nodes failed or timed out and the configuration of the
MTAS required the interaction with the external node
to be successful in order to proceed the session. The
(once, that is) for a particular session setup.The
accumulated number of MMTel session attempts,
in the terminating MTAS, to an unregistered PUI,
which was rejected due to node external reasons.
If the rejection is due to the absence of a license;
"LICENSES" will be used as key.If the rejection is due
to the absence of a business license; "BL-LICENSES"
will be used as key. Otherwise the CSCF IP address
will be used as key.
MtasMmtInitTer The accumulated number of MMTel session attempts, PEG
mUnregSessOk in the terminating MTAS, to an unregistered PUI, which
was either answered, not answered, or was rejected
by a service due to operator or user configuration. The
counter is keyed on the CSCF IP address.The counter
is incremented by 1 in the terminating MTAS when the
INVITE-ACK transaction has concluded after receiving
the final response or when the INVITE was rejected by
a service due to operator or user configuration.
64 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.44.6 Reference
This KPI is defined as "Equation 111. IMS MMTEL AS Terminating Session Set-up
Success Ratio" in "IMS Performance Indicators", 1/154 43-HSC 113 06, Rev T3,
1.45 IMS SCC AS Session Setup from CS using CAP Registered

and Unregistered Users Success Ratio
1.45.1 Description
This KPI shows the success rate for IMS SCC AS Originating Service Centralization
and Continuity (SCC) from CS using CAP Registered and Unregistered.
IMS SCC AS Centralization and Continuity (SCC) Service Accessibility is defined as

the probability of being able to successfully start the Service Centralization and
Continuity (SCC) Service from CS side and PS side.
1.45.2 Node Type

MTAS
1.45.3 Formula
Note: This formula is a combination of the CAP and SIP signalling for the SCC
CS service (registered and unregistered) invocation.
1.45.4 Metric Type

Percentage (%)
1.45.5 Counters
1/1553-CNA 403 3397 Uen F | 2018-08-10 65


Type
MtasSccInitOri The accumulated number of SCC session attempts PEG
gSessCsOk from the CS access domain, in the originating
MTAS, which was either answered, not answered,
or was rejected by a service due to operator
policy. The counter is keyed on the CSCF IP
address.Incremented by 1 when the INVITE-ACK
transaction has concluded after the final response
or when the INVITE was rejected by a service due
to operator policy.
gUnregSessCsOk from an unregistered user in the CS access
domain,in the originating MTAS, which was either
answered, not answered, or was rejected by a
service due to operator policy. The counter is
keyed on the CSCF IP address.Incremented by 1
when the INVITE-ACK transaction has concluded
after the final response or when the INVITE was
rejected by a service due to operator policy.
gSessCsNOkE from the CS access domain, in the originating
MTAS,which was rejected due to node external
reasons. The counter is keyed on the CSCF IP
address.The counter is incremented by 1 in the
originating MTAS, if the INVITE-ACK transaction
did not conclude successfully due to external
reasons, for example invalid feature tag or too
many media components in SDP or because of
receiving a 4xx, 5xx, or 6xx as the final response, or
any signaling transactions to external nodes failed
or timed out and the configuration of the MTAS
required the interaction with the external node to
be successful in order to proceed the session. The
(once, that is) for a particular session setup.
gSessCsNOkI from the CS access domain, in the originating
MTAS,which was rejected due to node internal
reasons. The counter is keyed on the CSCF IP
address.Incremented by 1 when the INVITE was
rejected due to internal reasons, for example
processor or memory shortage.
66 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions

Type
gUnregSessCsNO from an unregistered user on the CS access
kE domain,in the originating MTAS, which was
rejected due to node external reasons. The counter
is keyed on the CSCF IP address.Incremented
by 1 in originating MTAS if; The INVITE-ACK
transaction did not conclude successfully e.g
invalid feature tag or too many media components
in SDP or because SCC AS rejects an INVITE
unregistered from the CS domain due to external
reasons, e.g request not supported by SCC AS
or because any signaling transactions towards
external nodes failed or timed out and the
configuration of MTAS required the interaction
with the external node to be successful in order to
proceed the call. The counter will only be stepped
for one of the reasons (i.e. once) for a particular
call setup.
gUnregSessCsNO from an unregistered user in the CS access domain,
kI in the originating MTAS, which was rejected due
to node internal reasons. The counter is keyed on
the CSCF IP address.Incremented by 1 when the
INVITE was rejected due to internal reasons, for
example processor or memory shortage.
MtasSdsCapInit This counter is the accumulated number of PEG
DPOk CAMEL Application Part (CAP) InitialDP requests
processed successfully. Incremented by 1 when
a successful response is sent to CAP InitialDP
request.
MtasSdsCapInit This counter is the accumulated number of CAMEL PEG
DPNOkI Application Part (CAP) InitialDP requests that
failed because of problems internal to the SCC
AS, an IMRN could not be allocated, for example
because of no free IMRN.Incremented by 1 when
the SCC AS sends a failure response to a CAP
Initial DP request due to a problem in the SCC AS.
MtasSdsCapInit This counter is the accumulated number of CAMEL PEG
DPNOkE Application Part (CAP) InitialDP requests that
failed because the request message was faulty,
for example missing mandatory parameter or
parameter having unknown value.Incremented
by 1 when the SCC AS determines that a CAP
InitialDP request is faulty, and the SCC AS cannot
send a successful response.
1/1553-CNA 403 3397 Uen F | 2018-08-10 67

1.45.6 Reference
This KPI is defined as "Equation 154. IMS SCC AS Session Setup from CS using
CAP Registered and Unregistered Users Success Ratio" in "IMS Performance
Indicators", 1/154 43-HSC 113 06, Rev T3, Section 7.21.2 Reference [6].
1.46 IMS MMTel AS Orginating Session Completion Ratio
1.46.1 Description
This KPI shows the success rate for MTAS originating session setup.

1.46.2 Node Type

MTAS
1.46.3 Formula
1.46.4 Metric Type

Percentage (%)
1.46.5 Counters
68 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions

Type
MtasMmtTermOri The number of successful call completion in PEG
gSessOk Originating MMTEL AS triggered by UE. The counter
is keyed on cause in Reason Header.The counter
is incremented when BYE request with Reason
header with ?SIP;cause = 487? is received or with
?Q.850;cause=16? is received from network.
MtasMmtTermOri The accumulated number of MMTel sessions, in the PEG
gSessNOkI originating MTAS, terminated prematurely by the
MTAS due to internal reasons. The counter is keyed
by 1 in the originating MTAS when a session that
incremented the MtasMmtInitOrigSessOk counter
has concluded the BYE method successfully and the
BYE was initiated from the MTAS due to internal
reasons.
MtasMmtTermOri The accumulated number of MMTel sessions, in the PEG
gSessNOkE originating MTAS, terminated prematurely by the
MTAS due to external reasons. The counter is keyed
by 1 in the originating MTAS when a session that
incremented the MtasMmtInitOrigSessOk counter
BYE was initiated from the MTAS due to external
reasons.
1.46.6 Reference
This KPI is defined as "Equation 21. IMS MMTel AS Orginating Session Completion
1.47 IMS MMTel AS Terminating Session Completion Ratio
1.47.1 Description
This KPI shows the success rate for MTAS terminating session setup.

1.47.2 Node Type
MTAS
1/1553-CNA 403 3397 Uen F | 2018-08-10 69

1.47.3 Formula
1.47.4 Metric Type
Percentage (%)
1.47.5 Counters

Type
MtasMmtTermTer The number of successful call completion in PEG
mSessOk Terminating MMTEL AS triggered by UE. The counter
is keyed on cause in Reason Header.The counter
is incremented when BYE request with Reason
header with ?SIP;cause = 487? is received or with
?Q.850;cause=16? is received from network.
MtasMmtTermTer The accumulated number of MMTel sessions, in the PEG
mSessNOkI terminating MTAS, terminated prematurely by the
MTAS due to internal reasons. The counter is keyed
by 1 in the terminating MTAS when a session that
incremented the MtasMmtInitTermSessOk counter
BYE was initiated from the MTAS due to internal
reasons.
MtasMmtTermTer The accumulated number of MMTel sessions, in the PEG
mSessNOkE terminating MTAS, terminated prematurely by the
MTAS due to external reasons. The counter is keyed
by 1 in the terminating MTAS when a session that
incremented the MtasMmtInitTermSessOk counter
BYE was initiated from the MTAS due to external
reasons.
70 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.47.6 Reference
This KPI is defined as "Equation 22. IMS MMTel AS Terminating Session
Completion Ratio" in "IMS Performance Indicators", 1/154 43-HSC 113 06, Rev
T3, Section 3.6.2 Reference [6].
1.48 IMS SCC AS Single Radio Voice Call Continuity (SRVCC)

Access Transfer Success Ratio
1.48.1 Description
This KPI shows the success rate for MTAS Priority Call Establishment.
IMS MMTEL AS MtasPriorityCall Accessibility is defined as the probability of

being able to successfully establish new communication sessions with resource
priority setting.
1.48.2 Node Type
MTAS
1.48.3 Formula
1.48.4 Metric Type

Percentage (%)
1.48.5 Counters
These counters are defined per MTAS, and per WPS.

Type
MtasSrvccTran The number of successful access transfers using PEG
sferOk Single Radio Voice Call Continuity.The counter is
incremented when access transfer using Single Radio
Voice Call Continuity is successfully performed.
1/1553-CNA 403 3397 Uen F | 2018-08-10 71


Type
MtasSrvccTran The number of unsuccessful (due to node external PEG
sferNOkE error) access transfers attempts using Single Radio
Voice Call Continuity.The counter is incremented
when access transfer using Single Radio Voice Call
Continuity fails due to a node external error.
MtasSrvccTran The number of unsuccessful (due to node internal PEG
sferNOkI error) access transfers attempts using Single Radio
Voice Call Continuity.The counter is incremented
when access transfer using Single Radio Voice Call
Continuity fails due to a node internal error.
1.48.6 Reference
This KPI is defined as "Equation 28. IMS SCC AS Single Radio Voice Call Continuity
(SRVCC) Access Transfer Success Ratio" in "IMS Performance Indicators", 1/154
43-HSC 113 06, Rev T3, Section 3.6.2 Reference [6].
1.49 IMS MTAS Priority Call Successfully Established Ratio
1.49.1 Description
This KPI shows the success rate for MTAS Priority Call Establishment.
IMS MMTEL AS MtasPriorityCall Accessibility is defined as the probability of

being able to successfully establish new communication sessions with resource
priority setting.
1.49.2 Node Type

MTAS
1.49.3 Formula
72 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.49.4 Metric Type

Percentage (%)
1.49.5 Counters
These counters are defined per MTAS, and per WPS.

Type
MtasPriorityCa The counter accumulates number of new PEG
llWpsEstablish communication sessions with resource priority setting
ed determined by SIP Resource-priority header 'wps'
namespace (RFC 4412). The counter is keyed on wps
resource value. The counter is incremented by 1 when
a new session with wps resource-priority setting
enters 'established' state.
MtasPriorityCa The counter accumulates number of load regulation PEG
llWpsRequested requests at dialog setup, using parameter mapped
from SIP Resource-priority header 'wps' namespace
(RFC 4412). The counter is keyed on wps resource
value. The counter is incremented by 1 when an
execute permission is requested from TSP load
regulation, for processing an incoming INVITE,
which has a valid SIP Resource-priority header with
wps namespace, and is handled by MTAS Resource
Priority Handling function.
1.49.6 Reference
This KPI is defined as "Equation 164. IMS MMTel AS Priority Call Successfully
Established Ratio" in "IMS Performance Indicators", 1/154 43-HSC 113 06, Rev
T3, Section 7.29.2 Reference [6].
1.49.7 Notes
These counters are defined per MTAS, and per WPS, but are rolled up to node level.
1.50 Average interference measured in the PRBs for the

PUSCH
1.50.1 Description
This KPI shows the linear average of the interference in the PUSCH.
1/1553-CNA 403 3397 Uen F | 2018-08-10 73

This is the most compressed way to collect data about the interference situation
on the PUSCH, therefore it is collected in all cells. Since it is a distribution, there
can be clues to the nature of the interference in this counter, for this reason it is
collected even if e.g. pmRadioRecInterferencePwrPrb1-100 are collected.
1.50.2 Node Type

ERBS
1.50.3 Formula
P
Average interference =
measured in the PRBs for the PUSCH
( Numb er of Samples inbin 3 Average Power in bin )
10 3 log 10 Total numberof samples
Table 5 Average Power in each bin expressed in mW
Bin Average Power
[0] 7.9432823E-13
[1] 8.9716412E-13
[2] 1.12946271E-12
[3] 1.4219093E-12
[4] 1.79007775E-12
[5] 2.25357437E-12
[6] 2.83708205E-12
[7] 3.57167468E-12
[8] 4.49647202E-12
[9] 5.66072289E-12
[10] 1.107925268E-11
[11] 2.782982449E-11
[12] 6.990535853E-11
[13] 1.7559432158E-10
[14] 4.4107299382E-10
[15] 6.3095734448E-10
1.50.4 Metric Type

Decibel-Milliwatts (dBm)
74 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.50.5 Counters

pmRadioRecI The measured Noise and Interference Power on Not included PDF
nterference PUSCH, according to 36.214. in any
Pwr Condition: A wideband value for the frequency predefined
domain is measured in every valid UL subframe, scanner
including the UpPTS part of special subframe.
Table 6 PDF Ranges of pmRadioRecInterferencePwr

Bins Ranges
[0] N+I <= -121
[1] -121 < N+I <= -120
[2] -120 < N+I <= -119
[3] -119 < N+I <= -118
[4] -118 < N+I <= -117
[5] -117 < N+I <= -116
[6] -116 < N+I <= -115
[7] -115 < N+I <= -114
[8] -114 < N+I <= -113
[9] -113 < N+I <= -112
[10] -112 < N+I <= -108
[11] -108 < N+I <= -104
[12] -104 < N+I <= -100
[13] -100 < N+I <= -96
[14] -96 < N+I <= -92
[15] -92 < N+I
1.50.6 Reference
-
1.50.7 Notes
1/1553-CNA 403 3397 Uen F | 2018-08-10 75

1.51 Average interference measured in the PRBs for the

PUCCH
1.51.1 Description
This KPI shows the linear average of the interference in the PUCCH.
This is the only way to collect PM data about the interference situation on the
PUCCH, therefore it is collected in all cells.
1.51.2 Node Type

ERBS
1.51.3 Formula
P
Average interference =
measured in the PRBs for the PUCCH
( Number of Samples inBin 3 Average Power in Bin)
10 3 log 10 Total number of Samples
Table 7 Average Power in each bin expressed in mW

Bin Average Power
[0] 7.9432823E-13
[1] 8.9716412E-13
[2] 1.12946271E-12
[3] 1.4219093E-12
[4] 1.79007775E-12
[5] 2.25357437E-12
[6] 2.83708205E-12
[7] 3.57167468E-12
[8] 4.49647202E-12
[9] 5.66072289E-12
[10] 1.107925268E-11
[11] 2.782982449E-11
[12] 6.990535853E-11
[13] 1.7559432158E-10
[14] 4.4107299382E-10
[15] 6.3095734448E-10
76 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.51.4 Metric Type

1.51.5 Counters

Type
pmRadioRecInt The measured Noise and Interference Power on Not included PDF
erferencePwrP PUCCH, according to 36.214. in any
ucch Condition: A wideband value for the frequency predefined
domain is measured in every valid UL subframe. scanner
Table 8 PDF Ranges of pmRadioRecInterferencePwrPucch

Bins Ranges
[0] N+I <= -121
[1] -121 < N+I <= -120
[2] -120 < N+I <= -119
[3] -119 < N+I <= -118
[4] -118 < N+I <= -117
[5] -117 < N+I <= -116
[6] -116 < N+I <= -115
[7] -115 < N+I <= -114
[8] -114 < N+I <= -113
[9] -113 < N+I <= -112
[10] -112 < N+I <= -108
[11] -108 < N+I <= -104
[12] -104 < N+I <= -100
[13] -100 < N+I <= -96
[14] -96 < N+I <= -92
[15] -92 < N+I
1.51.6 Reference
1/1553-CNA 403 3397 Uen F | 2018-08-10 77

1.51.7 Notes
1.52 Interference power per PRB
1.52.1 Description
This KPI shows the linear average of the interference in each PRB of the PUSCH.
pmRadioRecInterferencePwrPrb[1-100], group of counters provide a detailed
view of the interference situation in each PRB of a cell. If PM data volume is not
an active constraint, these counters can be collected for all cells. At least they
should be collected for cells that periodically experience high interference levels.
1.52.2 Node Type

ERBS
1.52.3 Formula
Interference power per PRB =
10 3
log 10 ([X 1] + :: + [X 100]) 3 (power (2; 044)) 3 900003[Number of PRBs
40
used by PUSCH ]
Where X denotes pmRadioRecInterferencePwrPrb
1.52.4 Metric Type
1.52.5 Counters

Type
pmRadioRecInte The accumulated interference power for Not included in ACC
rferencePwrPrb PRB Condition: Samples summed over any predefined
[1…100] the measurement period. Measurements scanner
are averaged over receiver antennas. One
sample for each PRB per 40ms.
1.52.6 Reference
-
78 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.52.7 Notes
-
1.53 Interference power per antenna branch and PRB
1.53.1 Description
This KPI shows the linear average of the interference on each antenna branch in
each PRB of the PUSCH.
pmRadioRecInterferencePwrBrPrb[1-100], group of counters provide a detailed
view of the interference situation in each PRB on each receiver branch of a cell.
If PM data volume is not an active constraint these counters can be collected for
all cells. At least they should be collected for cells where it can be suspected that
there is some sort of problem with the antenna system, e.g.
In cells where interference is very high (constantly or temporarily), this could be
due to PIM in one or more of the branches; having data per branch will simplify
troubleshooting.
In cells where interference is very low, could indicate that one or more of the
antenna branches is not working properly which can be identified with the help
of these counters.
1.53.2 Node Type

ERBS
1.53.3 Formula
Interference power per antenna branch and PRB =

10 3
log 10 ([X 1] + :: + [X 100]) 3 (power (2; 044)) 3 900003[Number of PRBs
40
used by PUSCH ]
Where X denotes pmRadioRecInterferencePwrBrPrb
1.53.4 Metric Type

1/1553-CNA 403 3397 Uen F | 2018-08-10 79

1.53.5 Counters

Type
pmRadioRecInterfe The accumulated noise and interference power Not incl ACC
rencePwrBrPrb[1-1 for Physical Resource Block (PRB) on the uded in
00] antenna branch given by rfBranchRxRef. any pred
efined
scanner
1.53.6 Reference
-
1.53.7 Notes
-
1.54 UL/DL ACHIEVABLE THROUGHPUT PER EUTRANCELL
1.54.1 Description
Urgency Score is a score given to a cell to highlight its level of urgency for
optimization. It considers the Cell DL/UL Failure Rate and the number of Active
User Equipment (UE) instances in the cell. The Cell DL/UL Failure Rate PI formula,
used as part of the Urgency Score calculation, provides the percentage of Mobile
Broadband (MBB) User Experiences failing to meet the DL/UL Performance
Target (for example: 1 Mbps, 3 Mbps or 5 Mbps for DL and 0.15 Mbps, 0.3 Mbps or
1Mbps for UL) per Cell.
1.54.2 Node Type
ERBS
1.54.3 Formula
Urgency Score = Cell DL/UL Failure Rate * Number of Active UE Instances in
DL/UL.
1.54.4 Metric Type

None
80 1/1553-CNA 403 3397 Uen F | 2018-08-10

KPI Definitions
1.54.5 Reference
-
1.54.6 Notes
The DL/UL Failure Rate PI formula is Ericsson proprietary information and
therefore is not detailed in this document. The PI is calculated at Cell level.
1/1553-CNA 403 3397 Uen F | 2018-08-10 81

82 1/1553-CNA 403 3397 Uen F | 2018-08-10

Data Tables
2 Data Tables
The KPIs are calculated per ROP and are stored in several database tables in
ENIQ Statistics.
The Supported ENIQ version : 17B, 18A, 18B.
Following are the dimension tables:
— DIM_CV_ACM_CM_CONSTANTS
— DIM_CV_ACM_CONFIG
— DIM_CV_ACM_FREQBANDS
— DIM_CV_ACM_UPLINK_TBS
— DIM_CV_BULKCM_EUTRANCELLFDD
— DIM_CV_BULKCM_EUTRANCELLTDD
— DIM_CV_BULKCM_SECTORCARRIER
— DIM_CV_MEASURE
— DIM_CV_MEASURE_CONTROL
— DIM_CV_MEASURE_LIMITS
— DIM_CV_NODE_CONTROL
— DIM_CV_SEGMENT
Following are the views created on the base tables:
— DIM_CV_ERBS
— DIM_CV_ERBS_EUTRANCELL
— DIM_CV_NODE_INFO
— DC_CV_ERBS_EUTRANCELL_RAW_RANK
— DC_CV_ERBS_PMULINTERFERENCEREPORT_RAW_RANK
Following are the fact tables:
— DC_CV_CNAXE_MSC (RAW/DAY)
— DC_CV_CSCF_CSCF (RAW/DAY)
— DC_CV_ERBS_EUTRANCELL (RAW/DAY)
1/1553-CNA 403 3397 Uen F | 2018-08-10 83

— DC_CV_ERBS_EUTRANCELL_V (RAW/DAY)
— DC_CV_ERBS_EUTRANCELL_ACM (RAW/DAY)
— DC_CV_ERBS_PMULINTERFERENCEREPORT (RAW/DAY)
— DC_CV_GGSN_PGW (RAW/DAY)
— DC_CV_IMSGW_SBG (RAW/DAY)
— DC_CV_MTAS_MTAS (RAW/DAY)
— DC_CV_SGSN_MME (RAW/DAY)
— DC_CV_SGSN_MME_V (RAW/DAY)
Figure 1 Database schema
Structure of the above tables are described in the following sections.
2.1 DIM_CV_ACM_CM_CONSTANTS
Type : Mapping Table
This table describes the reference mapping of Bandwidth
The columns in this table are described below.
84 1/1553-CNA 403 3397 Uen F | 2018-08-10

Data Tables
Table 9 DIM_CV_ACM_CM_CONSTANTS Columns

Column Name Data Type
TECHNOLOGY varchar(20)
Number_OF_TxAntennas integer
DL_Channel_Bandwidth integer
Effective_CFIMODE integer
Number_CCE_Per_Subframe numeric(18,8)
Temp_TDD_Multiplier numeric(18,8)
The values in this table are predefined.
2.2 DIM_CV_ACM_CONFIG
Type : Topology Table
This table describes the Rates that have the possibility of being modified
Table 10 DIM_CV_ACM_CONFIG Columns

RATE integer
SLOGAN varchar(128)
RATE_VALUE numeric(18,8)
TRANSMISSION varchar(128)
STATUS varchar(16)
The values in this table are predefined and are as described below.
Table 11 DIM_CV_ACM_CONFIG Values

RATE TRANSMISSION SLOGAN RATE_VALUE STATUS
1 DOWNLINK 1Mbps 1.00000 ACTIVE
1 UPLINK 0.15Mbps 0.15000 ACTIVE
2 UPLINK 0.3Mbps 0.30000 ACTIVE
3 UPLINK 1Mbps 1.00000 ACTIVE
1/1553-CNA 403 3397 Uen F | 2018-08-10 85

2.3 DIM_CV_ACM_FREQBANDS
This table describes the reference mapping of Frequency Bands
Table 12 DIM_CV_ACM_FREQBANDS Columns

EUTRANBAND integer
DUPLEX_MODE varchar(16)
FREQ_MHZ integer
BAND_AND_FREQ varchar(40)
2.4 DIM_CV_ACM_UPLINK_TBS
This table describes the sinR and PRBs to ISLANDSIZE mapping
Table 13 DIM_CV_ACM_UPLINK_TBS Columns

sinR integer
PRBs integer
ISLANDSIZE integer
2.5 DIM_CV_BULKCM_EUTRANCELLFDD
This table describes the cells changes through bulk cm
86 1/1553-CNA 403 3397 Uen F | 2018-08-10

Data Tables
Table 14 DIM_CV_BULKCM_EUTRANCELLFDD Columns

EUTRANCELLFDD varchar(64)
DLCHANNELBANDWIDTH integer
PDCCHCFIMODE tinyint
HOST_NAME varchar(50)
OSS_ID varchar(50)
ELEMENT varchar(50)
FREQBAND integer
LATITUDE integer
LONGITUDE integer
DATE_ID date
COMMONSRPERIODICITY integer
NOOFPUCCHCQIUSERS integer
NOOFPUCCHSRUSERS integer
PZERONOMINALPUSCH integer
ULCHANNELBANDWIDTH integer
ALPHA integer
CELLRANGE integer
NPUCCHSR numeric(18,8)
NPUCCHHARQ numeric(18,8)
ULPRBPUCCHFORMAT1 numeric(18,8)
PUCCHPRBS numeric(18,8)
PRACHPRBS numeric(18,8)
PRODUCTDATA_PRODUCTNAME varchar(50)
PROD_RELEASE varchar(50)
MAXNUMSE_UL integer
DATETIME_ID datetime
UTC_DATETIME_ID datetime
2.6 DIM_CV_BULKCM_EUTRANCELLTDD
1/1553-CNA 403 3397 Uen F | 2018-08-10 87

This table describes the cells changes through bulk cm
Table 15 DIM_CV_BULKCM_EUTRANCELLTDD Columns

EUTRANCELLTDD varchar(64)
CHANNELBANDWIDTH integer
PDCCHCFIMODE tinyint
SUBFRAMEASSIGNMENT integer
OSS_ID varchar(50)
ELEMENT varchar(50)
FREQBAND integer
LATITUDE integer
COMMONSRPERIODICITY integer
NOOFPUCCHCQIUSERS integer
NOOFPUCCHSRUSERS integer
PZERONOMINALPUSCH integer
ALPHA integer
CELLRANGE integer
NPUCCHSR numeric(18,8)
NPUCCHHARQ numeric(18,8)
PUCCHPRBS numeric(18,8)
PRACHPRBS numeric(18,8)
PRODUCTDATA_PRODUCTNAME varchar(50)
PROD_RELEASE varchar(50)
MAXNUMSE_UL integer
LONGITUDE integer
DATE_ID date
88 1/1553-CNA 403 3397 Uen F | 2018-08-10

Data Tables
2.7 DIM_CV_BULKCM_SECTORCARRIER
This table describes the sectorcarrier changes through bulk cm
Table 16 DIM_CV_BULKCM_SECTORCARRIER Columns

SECTORCARRIER varchar(35)
NOOFTXANTENNAS integer
NOOFRXANTENNAS integer
ANTENNACORR numeric(18,8)
OSS_ID varchar(50)
DATE_ID date
2.8 DIM_CV_MEASURE
This is a dimension table that maps MEASURE_ID to a MEASURE description.
Table 17 DIM_CV_MEASURE Columns

MEASURE_NAME varchar(255)
MEASURE_ID integer
SHORT_NAME varchar(16)
UNIT_TYPE varchar(16)
METRIC_TYPE varchar(255integer)
MEASURE_CATEGORY varchar(50)
MEASURE_VERSION varchar(16)
HIGHLOW varchar(4)
AVERAGING_METHOD varchar(50)
1/1553-CNA 403 3397 Uen F | 2018-08-10 89

Table 17 DIM_CV_MEASURE Columns

AGGREGATION_METHOD varchar(50)
NODE_TYPE varchar(16)
MULTIPLE_QUERIES integer
KPI_FRAGMENT varchar(255)
QCI_MEASURE integer
MAPPING TABLE varchar(1024)
Table 18 DIM_CV_MEASURE Values

MEASURE_NAME MEAS UNIT_T METRIC_T MEASURE_C AGGRE NODE
URE_ YPE YPE ATEGORY GATIO _TYP
ID N_MET E
HOD
Initial E-RAB 1 % Percentage Accessibility Average ERBS
Establishment Success
Rate
E-RAB Retainability - 2 % Percentage Retainability Average ERBS
Percentage Lost
Average DL UE Latency 3 ms Counter Integrity Average ERBS
Average DL PDCP Cell 4 kbps Counter Integrity Average ERBS
Throughput
Average UL PDCP Cell 5 kbps Counter Integrity Average ERBS
Throughput
Average Downlink Volume 6 kb Counter null Average ERBS
Average number of 7 null Counter null Average ERBS
simultaneous Active UEs in
DL
Average number of RRC 8 null Counter null Average ERBS
Connected usersAverage
UE Session Time
Average UE Session Time 9 s Counter null Average ERBS
Average Number 10 null Counter null Average ERBS
of Simultaneous
E-RABsAverage UE Session
Time
Average usage of Downlink 11 null Counter null Average ERBS
PRB
VoIP Integrity 12 % Percentage Integrity Average ERBS
90 1/1553-CNA 403 3397 Uen F | 2018-08-10

Data Tables

Initial E-RAB 13 % Percentage Accessibility Average ERBS
Rate per QCI
Added E-RAB 14 % Percentage Accessibility Average ERBS
Rate per QCI
Voip Integrity DL - RTP 15 null Counter Integrity Sum ERBS
inter arrival GAP
Voip Integrity UL - RTP 16 null Counter Integrity Sum ERBS
inter arrival GAP
Added E-RAB 17 % Percentage Retainability Average ERBS
Rate per QCI E-RAB
Retainability - Percentage
Lost per QCI
IMS SBG Incoming Session 18 % Percentage Accessibility Average SBG
Set-up Success Ratio
IMS SBG Outgoing Session 19 % Percentage Accessibility Average SBG
Set-up Success Ratio
IMS A-SBG Initial 20 % Percentage Accessibility Average SBG
Registration Success Ratio
IMS SBG SRVCC Access 21 % Percentage Retainability Average SBG
Transfer Success Ratio
IMS SBG Incoming 22 ms Millisecond Integrity Sum SBG
Sessions Set-up Time s
IMS SBG Outgoing Sessions 23 ms Millisecond Integrity Sum SBG
Set-up Time s
IMS A-SBG Initial 24 ms Millisecond Integrity Max SBG
Registration Time s
SBG Total successful 25 null Counter Integrity Sum SBG
transfers in IMS
IMS SBG Media RTP Lost 26 % Percentage Integrity Average SBG
Packets Ratio
IMS SBG Media RTP Out of 27 % Percentage Integrity Average SBG
Sequence Packets Ratio
IMS SBG Incoming Priority 28 % Percentage Accessibility Average SBG
Session Set-up Success
Ratio
IMS SBG Emergency 29 % Percentage Accessibility Average SBG
Ratio
1/1553-CNA 403 3397 Uen F | 2018-08-10 91


IMS A-SBG Emergency 30 % Percentage Accessibility Average SBG
Initial Registration Success
Ratio
MSC SRVCC from LTE 31 % Percentage Retainability Average MSC
success rate per MME
MSC SRVCC from LTE 32 % Percentage Retainability Average MSC
success rate per MSC
MSC Relocation success 33 % Percentage Retainability Average MSC
rate to target RNC
MSC Relocation success 34 % Percentage Retainability Average MSC
rate to target MSC,WCDMA
IMS CSCF Third Party 35 % Percentage Accessibility Average CSCf
Registration Success Ratio
IMS CSCF EATCF SRVCC 36 % Percentage Retainability Average CSCF
Access Transfer Success
Ratio
S5 Create Session Failure 37 null Ratio Accessibility Average GGSN
per APN (IMS) ratio
MME - SRVCC to WCDMA 38 null Ratio Retainability Average SGSN
failure ratio
MME - SRVCC to GERAN 39 null Ratio Retainability Average SGSN
failure ratio
MME: Total SRVCC 40 null Counter Integrity Sum SGSN
Attempts
MME Dedicated Bearer 41 % Percentage Accessibility Average SGSN
Activation Success
MME VoLTE Uptake 42 % Percentage Accessibility Average SGSN
IMS MMTEL AS Originating 43 % Percentage Accessibility Average MTAS
Ratio
IMS MMTEL AS 44 % Percentage Accessibility Average MTAS
Terminating Session Set-up
Success Ratio
IMS SCC AS Session 45 % Percentage Accessibility Average MTAS
Setup from CS using
CAP Registered and
Unregistered Users Success
Ratio
IMS MMTel AS Orginating 46 % Percentage Retainability Average MTAS
Session Completion Ratio
92 1/1553-CNA 403 3397 Uen F | 2018-08-10

Data Tables

IMS MMTel AS Terminating 47 % Percentage Retainability Average MTAS
Session Completion Ratio
IMS SCC AS Single Radio 48 % Percentage Retainability Average MTAS
Voice Call Continuity
(SRVCC) Access Transfer
Success Ratio
IMS MTAS Priority Call 49 % Percentage Accessibility Average MTAS
Successfully Established
Ratio
Average interference 50 dBm Decibels-mi Accessibility Average ERBS
measured in the PRBs for lliwatts
the PUSCH
Average interference 51 dBm Decibels-mi Accessibility Average ERBS
measured in the PRBs for lliwatts
the PUCCH
Interference power per PRB 52 dBm Decibels-mi Accessibility Average ERBS
lliwatts
Interference power per 53 dBm Decibels-mi Accessibility Average ERBS
antenna branch and PRB lliwatts
UL/DL ACHIEVABLE 54 % Percentage null Average ERBS
THROUGHPUT PER
EUTRANCELL
2.9 DIM_CV_MEASURE_LIMITS
This is a dimension table that maps MEASURE_ID to threshold limits.
Table 19 DIM_CV_MEASURE_LIMITS Columns

MEASURE_ID integer
ERROR_THRESHOLD numeric(18,8)
WARNING_THRESHOLD numeric(18,8)
LIMIT_VALUE numeric(18,8)
1/1553-CNA 403 3397 Uen F | 2018-08-10 93

Table 20 DIM_CV_MEASURE_LIMITS Values

MEASURE_ID ERROR_THRESHOLD WARNING_THRESH LIMIT_VALUE
OLD
1 95.0000 97.5000 100.0000
2 10.0000 5.0000 0.0000
3 Null Null Null
4 Null Null Null
5 Null Null Null
6 Null Null Null
7 Null Null Null
8 Null Null Null
9 Null Null Null
10 Null Null Null
11 Null Null Null
12 95.0000 97.0000 100.0000
13 95.0000 97.0000 100.0000
14 95.0000 97.0000 100.0000
15 95.0000 97.0000 100.0000
16 95.0000 97.0000 100.0000
17 5.0000 3.0000 0.0000
18 95.0000 97.0000 100.0000
19 95.0000 97.0000 100.0000
20 95.0000 97.0000 100.0000
21 95.0000 97.0000 100.0000
22 Null Null Null
23 Null Null Null
24 Null Null Null
25 Null Null Null
26 5.0000 3.0000 0.0000
27 5.0000 3.0000 0.0000
28 95.0000 97.0000 100.0000
29 95.0000 97.0000 100.0000
30 95.0000 97.0000 100.0000
31 95.0000 97.0000 100.0000
94 1/1553-CNA 403 3397 Uen F | 2018-08-10

Data Tables
Table 20 DIM_CV_MEASURE_LIMITS Values

32 95.0000 97.0000 100.0000
33 95.0000 97.0000 100.0000
34 95.0000 97.0000 100.0000
35 95.0000 97.0000 100.0000
36 95.0000 97.0000 100.0000
37 5.0000 3.0000 0.0000
38 5.0000 3.0000 0.0000
39 5.0000 3.0000 0.0000
40 Null Null Null
41 95.0000 97.0000 100.0000
42 95.0000 97.0000 100.0000
43 95.0000 97.0000 100.0000
44 95.0000 97.0000 100.0000
45 95.0000 97.0000 100.0000
46 95.0000 97.0000 100.0000
47 95.0000 97.0000 100.0000
48 95.0000 97.0000 100.0000
49 95.0000 97.0000 100.0000
50 -118.0000 -119.0000 -120.0000
51 -118.0000 -119.0000 -120.0000
52 -118.0000 -119.0000 -120.0000
53 -118.0000 -119.0000 -120.0000
54 Null Null Null
Note: Values defined above are default Thresholds of the KPI.

Refer Information Store Configuration Document, Reference [16] for
updating the Threshold of the KPI to the desired value.
2.10 DIM_CV_NODE_CONTROL
This table describes the list of nodes for which KPIS are available and its status.
1/1553-CNA 403 3397 Uen F | 2018-08-10 95

Table 21 DIM_CV_NODE_CONTROL Columns

SYSTEM_AREA varchar(50)
EXECUTION_FREQUENCY integer
NODE_MEASURE_STATUS varchar(16)
TIME_OFFSET integer
Table 22 DIM_CV_NODE_CONTROL Values

NODE_TYPE SYSTEM_AREA EXECUTION_FR NODE_MEASUR TIME_OFFSET
EQUENCY E_STATUS
ERBS RAN 15 INACTIVE -45
SGSN EPC 15 INACTIVE -45
CSCF IMS 5 INACTIVE -45
MSC CORE 15 INACTIVE -45
SBG IMS 5 INACTIVE -45
MTAS IMS 5 INACTIVE -45
GGSN EPC 15 INACTIVE -45
Note: KPIs will be calculated only for the Node type whose NODE_MEASURE_S
TATUS Column is ACTIVE.
Refer Information Store Configuration Document, Reference [16] to
update the Node_Measure_Status from INACTIVE to ACTIVE .
2.11 DIM_CV_SEGMENT
Type : Config Table
This table describes the segments that have the possibility of being
created/modified and deleted.
Table 23 DIM_CV_SEGMENT Columns

SEGMENT_ID varchar(50)
NODE_FDN varchar(255)
96 1/1553-CNA 403 3397 Uen F | 2018-08-10

Data Tables
Table 23 DIM_CV_SEGMENT Columns

SEGMENT_STATUS varchar(16)
2.12 DIM_CV_ERBS
Type : view
This view describes the topology information of ERBS.
Base Topology Tables
— DIM_E_LTE_ERBS
The columns in this view are described below.
Table 24 DIM_CV_ERBS Columns

ERBS_VERSION varchar(35)
ERBS_ID varchar(50)
SITE_FDN varchar(255)
MECONTEXTID varchar(50)
fingerprint varchar(35)
OSS_ID varchar(50)
ERBS_NAME varchar(128)
SITE_ID varchar(70)
NEMIMVERSION varchar(50)
ERBS_FDN varchar(255)
managedElementType varchar(50)
prodDesignation tinyint
2.13 DIM_CV_ERBS_EUTRANCELL
Type : view
This view describes the topology information of ERBS(EUCELL).
— DIM_E_LTE_EUCELL
1/1553-CNA 403 3397 Uen F | 2018-08-10 97

Table 25 Columns for DIM_CV_ERBS_EUTRANCELL

Name Data Type
additionalPlmnList varchar(50)
bPlmnList varchar(50)
CELL_ID tinyint
CELL_TYPE varchar(35)
cellRange integer
earfcn integer
earfcndl integer
earfcnul integer
ENodeBFunction varchar(35)
ERBS_FDN varchar(255)
ERBS_ID varchar(50)
EUTRANCELL_FDN varchar(255)
EUtranCellId varchar(50)
hostingDigitalUnit varchar(255)
mappingInfoSIB10 varchar(15)
MCC smallint
MNC smallint
MNC_LENGTH smallint
noOfPucchCqiUsers integer
noOfPucchSrUsers integer
98 1/1553-CNA 403 3397 Uen F | 2018-08-10

Data Tables
Table 25 Columns for DIM_CV_ERBS_EUTRANCELL

OSS_ID varchar(50)
pdcchCfiMode integer
SEQUENCE_INDEX tinyint
siPeriodicitySI1 integer
STATUS varchar(16)
tac integer
TAC_NAME integer
ulChannelBandwidth numeric(18,8)
userLabel varchar(128)
VENDOR varchar(16)
2.14 DIM_CV_NODE_INFO
Type : view
This view describes the topology information of the nodes.
— DIM_E_CN_AXE
— DIM_E_CN_CN
— DIM_E_CN_GGSN
— DIM_E_LTE_ERBS
1/1553-CNA 403 3397 Uen F | 2018-08-10 99

Table 26 DIM_CV_NODE_INFO Columns

FDN varchar(255)
NODE_NAME varchar(128)
OSS_ID varchar(50)
NODE_VERSION varchar(35)
NODE_TYPE char(4)
SYSTEM_AREA char(4)
2.15 DC_CV_ERBS_EUTRANCELL_RAW_RANK
Type : view
This view describes the ranking information of the nodes.
Base Fact Tables
— DC_CV_ERBS_EUTRANCELL_RAW
Table 27 DC_CV_ERBS_EUTRANCELL_RAW_RANK Columns

CELL_FDN varchar(255)
OSS_ID varchar(50)
MEASURE_ID integer
MeasureValue numeric(18,8)
Rank integer
2.16 DC_CV_ERBS_PMULINTERFERENCEREPORT_RAW_
RANK
Type : view
This view describes the Ranking information of the nodes.
Base Fact Tables
— DC_CV_ERBS_PMULINTERFERENCEREPORT_RAW
100 1/1553-CNA 403 3397 Uen F | 2018-08-10

Data Tables
Table 28 DC_CV_ERBS_PMULINTERFERENCEREPORT_RAW_RANK Columns

OSS_ID varchar(50)
MEASURE_ID integer
BRANCH varchar(50)
Rank integer
2.17 DC_CV_CNAXE_MSC
This is a fact table that contains measure values corresponding to the measure_id.
Table 29 DC_CV_CNAXE_MSC Columns

MEASURED_OBJECT varchar(255)
MEASURE_ID integer
OSS_ID varchar(50)
The values in this table are created dynamically at each ROP.
2.18 DC_CV_CSCF_CSCF
Table 30 DC_CV_CSCF_CSCF Columns

MEASURE_ID integer
1/1553-CNA 403 3397 Uen F | 2018-08-10 101

Table 30 DC_CV_CSCF_CSCF Columns

OSS_ID varchar(50)
2.19 DC_CV_ERBS_EUTRANCELL
Table 31 DC_CV_ERBS_EUTRANCELL Columns

MEASURE_ID integer
OSS_ID varchar(50)
2.20 DC_CV_ERBS_EUTRANCELL_V
Table 32 DC_CV_ERBS_EUTRANCELL_V Columns

MEASURE_ID integer
OSS_ID varchar(50)
DCVECTOR_INDEX integer
102 1/1553-CNA 403 3397 Uen F | 2018-08-10

Data Tables
2.21 DC_CV_ERBS_EUTRANCELL_ACM
This is a fact table that contains PI values corresponding to the measure_id.
Table 33 DC_CV_ERBS_EUTRANCELL_ACM Columns

MEASURE_ID integer
OSS_ID varchar(50)
PROBABILITY_OF_FAILURE_DL_1 numeric(18,8)
PROBABILITY_OF_FAILURE_UL_1 numeric(18,8)
URGENCY_SCORE_DL_1 numeric(18,8)
URGENCY_SCORE_UL_1 numeric(18,8)
ACTIVE_UEs_DL numeric(18,8)
ACTIVE_UEs_UL numeric(18,8)
2.22 DC_CV_ERBS_PMULINTERFERENCEREPORT
Table 34 DC_CV_ERBS_PMULINTERFERENCEREPORT Columns

1/1553-CNA 403 3397 Uen F | 2018-08-10 103

Table 34 DC_CV_ERBS_PMULINTERFERENCEREPORT Columns

MEASURE_ID integer
OSS_ID varchar(50)
BRANCH varchar(50)
2.23 DC_CV_GGSN_PGW
Table 35 DC_CV_GGSN_PGW Columns

MEASURE_ID integer
OSS_ID varchar(50)
2.24 DC_CV_IMSGW_SBG
Table 36 DC_CV_IMSGW_SBG Columns

MEASURE_ID integer
OSS_ID varchar(50)
104 1/1553-CNA 403 3397 Uen F | 2018-08-10

Data Tables
2.25 DC_CV_MTAS_MTAS
Table 37 DC_CV_MTAS_MTAS Columns

MEASURE_ID integer
OSS_ID varchar(50)
2.26 DC_CV_SGSN_MME
Table 38 DC_CV_SGSN_MME Columns

MEASURE_ID integer
OSS_ID varchar(50)
2.27 DC_CV_SGSN_MME_V
1/1553-CNA 403 3397 Uen F | 2018-08-10 105

Table 39 DC_CV_SGSN_MME_V Columns

MEASURE_ID integer
OSS_ID varchar(50)
QosClassIdentifier integer
106 1/1553-CNA 403 3397 Uen F | 2018-08-10

Glossary
Glossary
Glossary FK
Additional glossary definitions are included in Foreign Key
VoLTE Abbreviation List Reference [9].
GERAN
ACM GSM EDGE Radio Access Network
App Coverage Map
GPRS
APN General Packet Radio Service
Access Point Name
GTP
A-SBG GPRS Tunneling Protocol
Access-Session Boarder Gateway
IMS
ATCF IP Multimedia Subsystem
Access Transfer Control Function
IRAT
CAMEL Inter Radio Access Technology
Customized Applications for Mobile Networks
Enhanced Logic KPI
Key Performance Indicator
CAP
CAMEL Application Part LTE
Long Term Evolution
CSCF
Call Session Control Function MME
Mobility Management Entity
DL
Downlink MMTel
Multimedia Telephony
eNB
E-UTRAN Node-B MSC
Mobile Switching Center
eNodeB
E-UTRAN Node-B MTAS
Multimedia Telephony Application Server
E-RAB
E-UTRAN Radio Access Bearer PDCP
Packet Data Convergence Protocol
EPS
Evolved Packet System PDF
Probability Distribution Function
E-UTRAN
Evolved UTRAN PDN
Packet Data Network
FDD
Frequency Division Duplex PGW
PDN Gateway
1/1553-CNA 403 3397 Uen F | 2018-08-10 107

PK SIP
Primary Key Session Initiation Protocol
PMS SRVCC
Performance Management Subsystem Single Radio - Voice Call Continuity
PRB TDD
Physical Resource Block Time Division Duplex
PUSCH UE
Physical Uplink Shared Channel User Equipment
PUCCH UL
Physical Uplink Control Channel Uplink
PUI UMTS
Public User Identity Universal Mobile Telecommunications System
QCI UTRAN
QoS Class Identifier UMTS Terrestrial Radio Access Network
QoS VoLTE
Quality of Service Voice Over LTE
RNC WCDMA
Radio Network Controller Wideband Code Division Multiple Access
ROP WPS
Recording Output Period Wireless Priority Service
RRC
Radio Resource Control
RTP
Real-Time Transport Protocol
SBG
Session Border Gateway
SGC
Session Gateway Controller
SCC
Service Centralization and Continuity
SCC-AS
Service Centralization and Continuity
Application Server
SGW
Serving Gateway
108 1/1553-CNA 403 3397 Uen F | 2018-08-10

Reference List
Reference List
[1] License and Resource Use Indicators, 47/1553-HSC 105 50/1, Revision: AB
[2] Key Performance Indicators, 37/1553-HSC 105 50/1, Revision: AL
[3] Counter Description, 1/00651-AXB 250 892/2, Revision: Y
[4] Key Performance Indicators, FDD", 37/1553-HSC 105 50/1-V1
[5] Key Performance Indicators, TDD", 37/1553-HSC 105 50/1-V2
[6] IMS Performance Indicators, 1/154 43-HSC 113 06
[7] List of Performance Indicators, 36/155 18-CSA 121 01/9
[8] LTE KPIs, 38/006 51-AXB 250 17
[9] VoLTE Abbreviation List, 1/0033-HSC 120 34
[10] Operations Support System (OSS) Glossary, 0033-AOM 901 017/2
[11] EPG Characteristics", 14/221 02-AXB 250 12-V2
[12] Key Performance Indicators (KPI) for the IP Multimedia Subsystem (IMS);
Definitions", 3GPP TS 32.454
[13] Counter List, 24/006 51-HSC 105 50/1
[14] SBG Management Information Model, 13/155 54-CXA 112 350
[15] OSS Library Typographic Conventions, 1/154 43-AOM 901 017/4
[16] Information Store Configuration, 1/1543-CNA 403 3397
1/1553-CNA 403 3397 Uen F | 2018-08-10 109

KPI Description

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

KPI Description

Uploaded by

Copyright:

Available Formats

Ericsson Information Store User Guide - Data

1/1553-CNA 403 3397 Uen F

1/1553-CNA 403 3397 Uen F | 2018-08-10

1/1553-CNA 403 3397 Uen F | 2018-08-10

1.32 MSC SRVCC from LTE Success for MSC 45

1/1553-CNA 403 3397 Uen F | 2018-08-10

Reference List 109

1/1553-CNA 403 3397 Uen F | 2018-08-10

1/1553-CNA 403 3397 Uen F | 2018-08-10

Table 1 List of KPI's

1/1553-CNA 403 3397 Uen F | 2018-08-10 1

Table 1 List of KPI's

2 1/1553-CNA 403 3397 Uen F | 2018-08-10

Table 1 List of KPI's

— Refer section 2.1, in the Information Store Configuration Document,

— Refer section 2.2, in the Information Store Configuration Document,

— Refer section 2.3, in the Information Store Configuration Document,

The Measures mentioned above are described in the following sections.

1.1 Initial E-RAB Establishment Success Rate

1.1.2 Node Type

1/1553-CNA 403 3397 Uen F | 2018-08-10 3

where RRCMMEOVL = pmRrcConnEstabFailMmeOvlMos + pmRrcConnEstab

1.1.4 Metric Type

Counter Description Scanner Counter Type

4 1/1553-CNA 403 3397 Uen F | 2018-08-10

Counter Description Scanner Counter Type

1.2 E-RAB Retainability - Percentage Lost

1.2.2 Node Type

1.2.4 Metric Type

1/1553-CNA 403 3397 Uen F | 2018-08-10 5

Counter Description Scanner Counter Type

1.3 Average DL UE Latency

This KPI measures the impact on the end user.

1.3.2 Node Type

6 1/1553-CNA 403 3397 Uen F | 2018-08-10

1.3.4 Metric Type

Counter Description Scanner Counter Type

1.4 Average DL PDCP Cell Throughput

1.4.2 Node Type

1/1553-CNA 403 3397 Uen F | 2018-08-10 7

1.4.4 Metric Type

These counters are defined per Cell.

Counter Description Scanner Counter Type

1.5 Average UL PDCP Cell Throughput

8 1/1553-CNA 403 3397 Uen F | 2018-08-10

1.5.2 Node Type

1.5.4 Metric Type

Kilobits Per Second (kbps)

Counter Description Scanner Counter Type

1.6 Average Downlink Volume

1.6.2 Node Type

1/1553-CNA 403 3397 Uen F | 2018-08-10 9

Equation 1 Average DL Volume per Cell

1.6.4 Metric Type

Counter Description Scanner Counter Type

This PI is defined in Reference [1] and Counter(s) is/are defined in Managed

1.7 Average number of simultaneous Active UEs in DL

1.7.2 Node Type

10 1/1553-CNA 403 3397 Uen F | 2018-08-10

1.7.4 Metric Type

Counter Description Scanner Counter Type

1.8 Average number of RRC Connected users

1.8.2 Node Type

1/1553-CNA 403 3397 Uen F | 2018-08-10 11