This section describes the counting procedures
for all KPIs.
SEPS:
The SEPS KPI is implemented
such that each session setup and session tear down is considered
as a separate event.
SEPS counter is incremented by 1 in the
following scenarios:- After receiving the "Create
Session Request" message or "Delete Session Request" message
- After sending the "Create Session Response" message
or "Delete Session Response" message
- If "Create Session Response" message contains
a failure cause
- If "Delete Session Response" message does
not have the cause IE equal "Request Accepted"
Network
Initiated Setup/Teardown Events Per Second KPI:
The
Network Initiated Setup/Teardown KPI is implemented such
that each created and deleted VoLTE (configured QCI value) dedicated
bearers are considered as a separate event.
Network Initiated
Setup/Teardown KPI counter is incremented by 1 in the following scenarios
for the configured QCI value:- After receiving the "Create
Bearer Response" message or "Delete Bearer Response" message
- After sending the "Create Bearer Request" message
or "Delete Bearer Request" message
- If "Create Bearer Response" message does not
have the cause IE equal "Request Accepted"
- If "Delete Bearer Response" message does not
have the cause IE equal "Request Accepted"
Gx-TPS:
Gx
Events Per Seconds (Gx-EPS) KPI measures the rate of sent and received
Gx event/messages. This KPI indicates the number of received
CCA and RAR Diameter messages (each received CCA and RAR message
is used to peg the counter) and sent CCR and RAA Diameter messages
(each sent CCR and RAA message is used to peg the counter). Gx-EPS
KPI considers each received message (CCA and RAR) and each sent
message (CCR and RAA) as a separate event.
Gy-TPS:
Gy
Events Per Seconds (Gy-EPS) KPI measures the rate of sent and received
Gy event/messages. This KPI indicates the number of received
CCA Diameter messages (each received CCA message is used to peg
the counter) and sent CCR Diameter messages (each sent CCR message
is used to peg the counter). Gy-EPS KPI considers each received
message (CCA) and each sent message (CCR) as a separate event.
S6b-TPS:
S6b
Events Per Seconds (S6b-EPS) KPI measures the rate of sent and received
S6b event/messages. This KPI indicates the number of received
(AAA, ASR, STA) Diameter messages and sent (AAR, STR, ASA) Diameter
messages (each received AAA, ASR, STA messages are used to peg the
counter and each sent AAR, STR, and ASA messages are used to peg
the counter). S6b-EPS KPI considers each received message (AAA,
ASR, STA) and each sent message (AAR, STR, ASA) as a separate event.
Rf-TPS:
Rf
Events Per Seconds (Rf-EPS) KPI measures the rate of sent and received
Rf event/messages. This KPI indicates the number of received
ACA Diameter message and sent ACR Diameter message (each received
ACA message is used to peg the counter and each sent ACR message
is used to peg the counter). Rf-EPS KPI considers each ACA received
message and each ACR sent message as a separate event.
SWm-TPS:
SWm
Events Per Seconds (SWm-EPS) KPI measures the rate of sent and received
SWm event/messages. This KPI indicates the number of received
STA and DEA Diameter messages and sent STR and DER Diameter messages
(each received STA and DEA message is used to peg the counter and
each sent STR and DER message is used to peg the counter). SWm-EPS
KPI considers each STA and DEA received message and each STR and
DER sent message as a separate event.
This feature does not
require any specific configuration for enabling but minimal configuration
of bucket intervals and QCIs is required for calculating the KPIs.
For more on this feature and the configuration details, refer to
the P-GW Administration Guide.