Contents
| Table 1 | Measure Tables Contents |
| Table 2 | Gx Protocol Measures |
| Table 3 | Rx Protocol Measures |
| Table 4 | Sy Protocol Measures |
| Table 5 | Smp Protocol Measures |
| Table 6 | Sd Protocol Measures |
| Table 7 | Fair Usage Measures |
| Table 8 | Notification Measures |
| Table 9 | Capacity Measures |
| Table 10 | Resources Measures |
| Table 11 | ExtDb Measures |
| Table 12 | EBM Measures |
| Table 13 | Optional Measures |
| Table 14 | REST Provisioning Measures |
| Table 15 | Other Measures |
| Table 16 | The SAPC Measure Table Contents vs Reported Data XML Elements |
1 Measurements Introduction
The purpose of any Performance Management activity is to collect data, which can be used to verify the physical and logical configuration of the network and to locate potential problems as early as possible.
This document provides information on how to use measures that are collected by the SAPC for performance management. For more information, refer to Performance Management.
2 Measures
The SAPC provides statistic measures related to several interface protocol messages and functions. This chapter describes each measure that can be collected by the SAPC.
The following table explains the measures information explained in measures related tables along subsequent chapters.
|
Measure Name |
Name (identification) of the measure type. Indicates what is measured. |
|
Measure Meaning |
It explains the data collected in this measure. |
|
Measured Object Instance |
String key identifying the measured object (MOID). For example, a measure can be collected for a specific network element (Peer) that communicates to or from the SAPC using an external interface. Its corresponding MOID is the network identifier of the peer. For those cases, this document states <Network Peer>, for example <PcefDN PeerDN>. In other cases, the measure is collected in general for a concept in the SAPC, and in this case its MOID takes a fixed string value, for example "Sessions". |
|
Alarm Id |
For Fault Detection related measures, identifier of the associated alarm. A dash means that there is not any alarm related to it. |
|
Measurement Type |
It indicates the collection method for the measure:
Definitions of these measurement types in Performance Management. |
The measurements are read-only data, they show the information related to the SAPC and cannot be modified.
2.1 Gx Protocol Measures
The following table describes the measures provided by the SAPC belonging to the measure group: "policyControlFunctionGxMeasuresGroup".
|
Measure Name |
Measure Meaning |
Measured Object Instance(1) |
Alarm Id |
Measurement Type |
|---|---|---|---|---|
|
gxAdcStartEvents |
The number of ADC start events received. |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxAdcStopEvents |
The number of ADC stop events received. |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasErrorInitialParameters |
The number of CCAs initial sent indicating error with initial parameters (Experimental-Result-Code AVP set to 5140). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasInitEmergencyFailed |
The number of CCAs initial for emergency services sent indicating not success (Result-Code AVP set to a value different than 2001). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasInitEmergencySuccess |
The number of CCAs initial for emergency services sent indicating success (Result-Code AVP set to 2001). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasInitEmergencyTooBusy |
The number of CCAs initial for emergency services sent indicating too busy (Result-Code AVP set to 3004). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasInitFailed |
The number of initial CCAs sent indicating not success (Result-Code AVP set to a value different than 2001). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasInitInvalidAvp |
The number of initial CCAs sent indicating invalid AVP (Result-Code AVP set to 5004). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasInitMissingAvp |
The number of initial CCAs sent indicating missing AVP (Result-Code AVP set to 5005). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasInitMultimediaPriorityTooBusy |
The number of initial CCAs sent for Multimedia Priority Services indicating too busy (Result-Code AVP set to 3004). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasInitSuccess |
The number of initial CCAs sent indicating success (Result-Code AVP set to 2001). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasInitTooBusy |
The number of CCAs initial sent indicating too busy (Result-Code AVP set to 3004). |
<Pcef Peer> |
Major Type: 193 Minor Type: 7077899 |
Cumulative Counter |
|
gxCcasInitUnableToComply |
The number of CCAs sent indicating unable to comply (Result-Code AVP set to 5012) for IP-CAN session establishment. |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasInvalidInfo |
The number of CCAs sent indicating errors (Result-Code AVP set to 5004, 5005, 5007 or 5008). Incremented when receiving a message with a missing AVP or an AVP that does not have the correct value |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasRejected |
The number of CCAs sent indicating authorization rejected (Result-Code AVP set to 5003). |
<Pcef Peer> |
Major Type: 193 Minor Type: 7077890 |
Cumulative Counter |
|
gxCcasSuccess |
The number CCAs sent indicating success (Result-Code AVP set to 2001). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasTerminateSuccess |
The number of termination CCAs sent indicating success (Result-Code AVP set to 2001). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasTerminateTooBusy |
The number of termination CCAs sent indicating too busy (Result-Code AVP set to 3004). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasUnableToComply |
The number of CCAs sent indicating unable to comply (Result-Code AVP set to 5012). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasUnknownSession |
The number of CCAs sent indicating unknown session (Result-Code AVP set to 5002). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasUpdateEmergencyTooBusy |
The number of CCAs update for emergency services sent indicating too busy (Result-Code AVP set to 3004). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasUpdateMultimediaPriorityTooBusy |
The number of update CCAs sent for Multimedia Priority Services indicating too busy (Result-Code AVP set to 3004). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasUpdateSuccess |
The number of CCAs sent indicating successful (Result-Code AVP set to 2001) IP-CAN session modification. |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcasUpdateTooBusy |
The number of update CCAs sent indicating too busy (Result-Code AVP set to 3004). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcrsInit |
The number of initial CCRs received (CC-Request-Type AVP set to value INITIAL). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcrsTerminate |
The number of termination CCRs received (CC-Request-Type AVP set to value TERMINATION). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxCcrsUpdate |
The number of update CCRs received (CC-Request-Type AVP set to value UPDATE). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxChargingCharsRequested |
The number of CCRs requesting Charging Characteristics. |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxPushQosChange |
The number of RARs including a network initiated Qos change for the bearer. |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxPushRulesInstallation |
The number of RARs installing Pcc Rules. |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxQosAccepted |
<Pcef Peer> |
- |
Cumulative Counter | |
|
gxQosChanged |
The number of CCAs returning QoS changed. At least a QoS parameter is upgraded and some other QoS parameter is downgraded. |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxQosDowngraded |
<Pcef Peer> |
- |
Cumulative Counter | |
|
gxQosRequests |
The number of CCRs requesting Bearer QoS control. QoS for default bearer or APN. |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxQosUpgraded |
<Pcef Peer> |
- |
Cumulative Counter | |
|
gxRaas |
The number of RAAs received. |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxRaasFailed |
The number of RAAs received indicating not success (Result-Code AVP set to a value different than 2001). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxRaasOutOfSpace |
The number of RAAs received indicating out of space (Result-Code AVP set to 4002). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxRaasPendingTransaction |
The number of RAAs received indicating pending transaction (Experimental-Result-Code AVP set to 4144). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxRaasSuccess |
The number of RAAs received indicating success (Result-Code AVP set to 2001). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxRaasUnableToDeliver |
The number of RAAs received indicating unable to deliver (Result-Code AVP set to 3002). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxRaasUnknownSessionId |
The number of Gx RAAs received indicating unknown session (Result-Code AVP set to 5002). |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxRars |
The number of RARs sent. |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxRarsTimeout |
The number of RARs that did not reach the peer. |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxRuleSpaceChanged |
The number of CCAs sent changing the received suggested Rulespace. |
<Pcef Peer> |
- |
Cumulative Counter |
|
gxRuleSpaceSuggestedRequests |
The number of CCRs received requesting RuleSpace suggestion negotiation. |
<Pcef Peer> |
- |
Cumulative Counter |
(1) The peer identifier is the value received from the
PCEF in Origin-Host AVP
2.2 Rx Protocol Measures
The following table describes the measures provided by the SAPC belonging to the measure group: "policyControlFunctionRxMeasuresGroup".
|
Measure Name |
Measure Meaning |
Measured Object Instance(1) |
Alarm Id |
Measurement Type |
|---|---|---|---|---|
|
rxAaasAfSignallingSuccess |
The number of AAAs sent indicating the successful establishment or modification of an AF signalling session (Result-Code AVP set to 2001). The SAPC also increments rxAaasSuccess measure. |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasFailed |
The number of AAAs sent indicating not success (Result-Code AVP set to a value different than 2001). |
<Af Peer> |
Major Type: 193 Minor Type: 7077894 |
Cumulative Counter |
|
rxAaasInitEmergencyFailed |
The number of AAAs for emergency services sent indicating not successful emergency AF session creation (Result-Code AVP set to a value different than 2001). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasInitEmergencySuccess |
The number of AAAs for emergency services sent indicating successful emergency AF session creation (Result-Code AVP set to 2001). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasInitEmergencyTooBusy |
The number of initial AAAs for emergency services sent indicating too busy (Result-Code AVP set to 3004). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasInitMultimediaPriorityFailed |
The number of initial AAAs sent for Multimedia Priority Services indicating not success (Result-Code AVP set to a value different than 2001). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasInitMultimediaPriorityTooBusy |
The number of initial AAAs sent for Multimedia Priority Services indicating too busy (Result-Code AVP set to 3004). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasInitSuccess |
The number of initial AAAs sent indicating success (Result-Code AVP set to 2001). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasInitTooBusy |
The number of AAAs initial sent indicating too busy (Result-Code AVP set to 3004). |
<Af Peer> |
Major Type: 193 Minor Type: 7077900 |
Cumulative Counter |
|
rxAaasInvalidInfo |
The number of AAAs sent indicating invalid information (Result-Code AVP set to 5004, 5005, 5007 or 5008). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasIpSessionNotAvailable |
The number of AAAs indicating Ip Session not available (Result-Code AVP set to 5065). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasMultimediaPrioritySuccess |
The number of initial or update AAAs sent for Multimedia Priority Services indicating success (Result-Code AVP set to 2001). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasServiceNotAuthorized |
The number of AAAs sent indicating dynamic service authorization rejected (Result-Code AVP set to 5063). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasSuccess |
The number of AAAs sent indicating success (Result-Code AVP set to 2001). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasUnableToComply |
The number of AAAs sent indicating unable to comply (Result-Code AVP set to 5012). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasUnauthorizedNonEmergency |
The number of initial AAAs for emergency services sent indicating unauthorized non emergency session (Experimental-Result-Code AVP set to 5066). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasUnknownSessionId |
The number of AAAs sent indicating unknown session (Result-Code AVP set to 5002). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasUpdateEmergencyTooBusy |
The number of AAAs update for emergency services sent indicating too busy (Result-Code AVP set to 3004). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasUpdateMultimediaPriorityTooBusy |
The number of update AAAs sent for Multimedia Priority Services indicating too busy (Result-Code AVP set to 3004). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAaasUpdateTooBusy |
The number of AAAs update sent indicating too busy (Result-Code AVP set to 3004). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAarsAfSignalling |
The number of AARs received to establish or modify an AF signalling session. The SAPC also increments rxAarsInit or rxAarsUpdate measure, respectively. |
<Af Peer> |
- |
Cumulative Counter |
|
rxAarsInit |
The number of AARs received for AF session creation. Incremented for AARs received with Rx-Request-Type set to INITIAL_REQUEST (0) or for AARs without Rx-Request-Type AVP that create the AF session. |
<Af Peer> |
- |
Cumulative Counter |
|
rxAarsMultimediaPriority |
The number of initial or update AARs received for Multimedia Priority Services. |
<Af Peer> |
- |
Cumulative Counter |
|
rxAarsUpdate |
The number of AARs received for AF session update. Incremented for AARs received with Rx-Request-Type set to UPDATE_REQUEST (1) or for AARs without Rx-Request-Type that modify an existing AF Session. |
<Af Peer> |
- |
Cumulative Counter |
|
rxAsasAfSignallingSuccess |
The number of ASAs received indicating successful reception of the request to abort an AF signalling session (Result-Code AVP set to 2001). The SAPC also increments rxAsasSucces measure. |
<Af Peer> |
- |
Cumulative Counter |
|
rxAsasFailed |
The number of ASAs received indicating not success (Result-Code AVP set to a value different than 2001). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAsasSuccess |
The number of ASAs received indicating success (Result-Code AVP set to 2001). |
<Af Peer> |
- |
Cumulative Counter |
|
rxAsrs |
The number or ASRs sent. |
<Af Peer> |
- |
Cumulative Counter |
|
rxAsrsAfSignalling |
The number of ASRs sent to abort an AF signalling session. The SAPC also increments rxAsrs measure. |
<Af Peer> |
- |
Cumulative Counter |
|
rxAsrsTimeout |
The number of ASRs that did not reach the peer. |
<Af Peer> |
- |
Cumulative Counter |
|
rxRaasFailed |
The number of RAAs received indicating not success (Result-Code AVP set to a value different than 2001). |
<Af Peer> |
- |
Cumulative Counter |
|
rxRaasSuccess |
The number of RAAs received indicating success (Result-Code AVP set to 2001). |
<Af Peer> |
- |
Cumulative Counter |
|
rxRars |
The number of Rx RARs sent. |
<Af Peer> |
- |
Cumulative Counter |
|
rxRarsTimeout |
The number of RARs that did not reach the peer. |
<Af Peer> |
- |
Cumulative Counter |
|
rxStasAfSignallingSuccess |
The number of STAs sent indicating successful termination of an AF signalling session (Result-Code AVP set to 2001). The SAPC also increments rxStasSuccess measure. |
<Af Peer> |
- |
Cumulative Counter |
|
rxStasSuccess |
The number of STAs sent indicating success (Result-Code AVP set to 2001). |
<Af Peer> |
- |
Cumulative Counter |
|
rxStasTooBusy |
The number of STAs sent indicating too busy (Result-Code AVP set to 3004). |
<Af Peer> |
- |
Cumulative Counter |
|
rxStasUnknownSessionId |
The number of STAs sent indicating unknown session (Result-Code AVP set to 5002). |
<Af Peer> |
- |
Cumulative Counter |
|
rxStrs |
The number or STRs received. |
<Af Peer> |
- |
Cumulative Counter |
|
rxStrsAfSignalling |
The number of STRs received to terminate an AF signalling session. The SAPC also increments rxStrs measure. |
<Af Peer> |
- |
Cumulative Counter |
(1) The peer identifier is the value received from the
AF in Origin-Host AVP
2.3 Sy Protocol Measures
The following table describes measures provided by the SAPC belonging to the measure group: "policyControlFunctionSyMeasuresGroup".
|
Measure Name |
Measure Meaning |
Measured Object Instance |
Alarm Id |
Measurement Type |
|---|---|---|---|---|
|
sySlasFailed |
The number of SLAs received indicating not success (Result-Code AVP set to a value different than 2001). |
<OCS Peer> |
- |
Cumulative Counter |
|
sySlasSuccess |
The number of SLAs received indicating success (Result-Code AVP set to 2001). |
<OCS Peer> |
- |
Cumulative Counter |
|
sySlrs |
The number of SLRs sent. |
<OCS Peer> |
- |
Cumulative Counter |
|
sySlrsTimeout |
The number of SLRs that did not reach the peer. |
<OCS Peer> |
- |
Cumulative Counter |
|
sySnasFailed |
The number of SNAs sent indicating not success (Result-Code AVP set to a value different than 2001). |
<OCS Peer> |
- |
Cumulative Counter |
|
sySnasSuccess |
The number of SNAs sent indicating success (Result-Code AVP set to 2001). |
<OCS Peer> |
- |
Cumulative Counter |
|
sySnasTooBusy |
The number of SNAs sent indicating too busy (Result-Code AVP set to 3004). |
<OCS Peer> |
- |
Cumulative Counter |
|
sySnrs |
The number of SNRs received. |
<OCS Peer> |
- |
Cumulative Counter |
|
syStasFailed |
The number of STAs received indicating not success (Result-Code AVP set to a value different than 2001). |
<OCS Peer> |
- |
Cumulative Counter |
|
syStasSuccess |
The number of STAs received indicating success (Result-Code AVP set to 2001). |
<OCS Peer> |
- |
Cumulative Counter |
|
syStrs |
The number of STRs sent. |
<OCS Peer> |
- |
Cumulative Counter |
|
syStrsTimeout |
The number of STRs that did not reach the peer. |
<OCS Peer> |
- |
Cumulative Counter |
- Note:
- When the SAPC sends an SLR but does not receive the corresponding SLA after a time-out, it increases sySlrs and sySlasFailed counters. In this case, the SAPC uses Destination-Realm value as MOI, because Origin-Host value of the SLA is not known (SLA message is not received).
2.4 Smp Protocol Measures
The following table describes the measures provided by the SAPC belonging to the measure group: "policyControlFunctionSxMeasuresGroup".
|
Measure Name |
Measure Meaning |
Measured Object Instance |
Alarm Id |
Measurement Type |
|---|---|---|---|---|
|
sxCcasInitDropSxSession |
The number of initial CCAs sent indicating drop Sx session (Result-Code AVP set to 4011). |
<SGSN-MME Peer> |
- |
Cumulative Counter |
|
sxCcasInitFailed |
The number of initial CCAs sent indicating not success (Result-Code AVP set to value different than 2001). |
<SGSN-MME Peer> |
- |
Cumulative Counter |
|
sxCcasInitInvalidAvp |
The number of initial CCAs sent indicating invalid AVP (Result-Code AVP set to 5004). |
<SGSN-MME Peer> |
- |
Cumulative Counter |
|
sxCcasInitMissingAvp |
The number of initial CCAs sent indicating missing AVP (Result-Code AVP set to 5005). |
<SGSN-MME Peer> |
- |
Cumulative Counter |
|
sxCcasInitSuccess |
The number of initial CCAs sent indicating success (Result-Code AVP set to 2001). |
<SGSN-MME Peer> |
- |
Cumulative Counter |
|
sxCcasInitTooBusy |
The number of initial CCAs sent indicating that Diameter peer is too busy (Result-Code AVP set to 3004). |
<SGSN-MME Peer> |
Major Type: 193 Minor Type: 7077901 |
Cumulative Counter |
|
sxCcasInitUnableToComply |
The number of initial CCAs sent indicating unable to comply (Result-Code AVP set to 5012). |
<SGSN-MME Peer> |
- |
Cumulative Counter |
|
sxCcasInvalidInfo |
The number of CCAs sent indicating errors (Result-Code AVP set to 5004, 5005, 5007 or 5008) owing to: An AVP is missing, an AVP does not have the correct value. |
<SGSN-MME Peer> |
- |
Cumulative Counter |
|
sxCcasSuccess |
The number of CCAs sent indicating success (Result-Code AVP set to 2001). |
<SGSN-MME Peer> |
- |
Cumulative Counter |
|
sxCcasTerminateSuccess |
The number of termination CCAs sent indicating success (Result-Code AVP set to 2001). |
<SGSN-MME Peer> |
- |
Cumulative Counter |
|
sxCcasUnknownSession |
The number of CCAs sent indicating unknown session (Result-Code AVP set to 5002). |
<SGSN-MME Peer> |
- |
Cumulative Counter |
|
sxCcasUpdateSuccess |
The number of update CCAs sent indicating success (Result-Code AVP set to 2001). |
<SGSN-MME Peer> |
- |
Cumulative Counter |
|
sxCcrsInit |
The number of initial CCRs received (CC-Request-Type AVP set to value INITIAL). |
<SGSN-MME Peer> |
- |
Cumulative Counter |
|
sxCcrsTerminate |
The number of termination CCRs received (CC-Request-Type AVP set to value TERMINATION). |
<SGSN-MME Peer> |
- |
Cumulative Counter |
|
sxCcrsUpdate |
The number of update CCRs received (CC-Request-Type AVP set to value UPDATE). |
<SGSN-MME Peer> |
- |
Cumulative Counter |
2.5 Sd Protocol Measures
The following table describes the measures provided by the SAPC belonging to the measure group: "policyControlFunctionSdMeasuresGroup".
|
Measure Name |
Measure Meaning |
Measured Object Instance |
Alarm Id |
Measurement Type |
|---|---|---|---|---|
|
sdAdcStartEvents |
The number of ADC start events received through Sd. |
<TDF Peer> |
- |
Cumulative Counter |
|
sdAdcStopEvents |
The number of ADC stop events received through Sd. |
<TDF Peer> |
- |
Cumulative Counter |
|
sdCcasInvalidInfo |
The number of CCAs sent indicating errors (Result-Code AVP set to 5004 or 5005). Incremented when receiving a message with a missing AVP or an AVP that does not have the correct value. |
<TDF Peer> |
- |
Cumulative Counter |
|
sdCcasSuccess |
The number of CCAs sent indicating success (Result-Code AVP set to 2001). |
<TDF Peer> |
- |
Cumulative Counter |
|
sdCcasTerminateSuccess |
The number of termination CCAs sent indicating success (Result-Code AVP set to 2001). |
<TDF Peer> |
- |
Cumulative Counter |
|
sdCcasUnableToComply |
The number of CCAs sent indicating unable to comply (Result-Code AVP set to 5012). |
<TDF Peer> |
- |
Cumulative Counter |
|
sdCcasUnknownSession |
The number of CCAs sent indicating unknown session (Result-Code AVP set to 5002). |
<TDF Peer> |
- |
Cumulative Counter |
|
sdCcasUpdateSuccess |
The number of update CCAs sent indicating success (Result-Code AVP set to 2001). |
<TDF Peer> |
- |
Cumulative Counter |
|
sdCcasUpdateTooBusy |
The number of update CCAs sent indicating too busy (Result-Code AVP set to 3004). |
<TDF Peer> |
- |
Cumulative Counter |
|
sdCcrsTerminate |
The number of termination CCRs received (CC-Request-Type AVP set to value TERMINATION). |
<TDF Peer> |
- |
Cumulative Counter |
|
sdCcrsUpdate |
The number of update CCRs received (CC-Request-Type AVP set to value UPDATE). |
<TDF Peer> |
- |
Cumulative Counter |
|
sdRaasFailed |
The number of RAAs received indicating not success (Result-Code AVP set to a value different than 2001). |
<TDF Peer> |
- |
Cumulative Counter |
|
sdRaasSuccess |
The number of RAAs received indicating success (Result-Code AVP set to 2001). |
<TDF Peer> |
- |
Cumulative Counter |
|
sdRaasUnknownSessionId |
The number of RAAs received indicating unknown session (Result-Code AVP set to 5002). |
<TDF Peer> |
- |
Cumulative Counter |
|
sdRars |
The number of RARs sent. |
<TDF Peer> |
- |
Cumulative Counter |
|
sdRarsTimeout |
The number of RARs that did not reach the peer. |
<TDF Peer> |
- |
Cumulative Counter |
|
sdTsasFailed |
The number of TSAs received indicating not success (Result-Code AVP set to a value different than 2001). |
<TDF Peer> |
- |
Cumulative Counter |
|
sdTsasSuccess |
The number of TSAs received indicating success (Result-Code AVP set to 2001). |
<TDF Peer> |
- |
Cumulative Counter |
|
sdTsrs |
The number of TSRs sent. |
<TDF Peer> |
- |
Cumulative Counter |
|
sdTsrsTimeout |
The number of TSRs that did not reach the peer. |
<TDF Peer> |
- |
Cumulative Counter |
2.6 Fair Usage Control Measures
The following table describes the measures provided by the SAPC belonging to the measure group: "policyControlFunctionFairUsageMeasuresGroup".
|
Measure Name |
Measure Meaning |
Measured Object Instance |
Alarm Id |
Measurement Type |
|---|---|---|---|---|
|
usageLimitSurpassed |
The number of times a given usage limit is surpassed by a subscriber. |
<PceF Peer> |
Major Type: 193 Minor Type: 7077889 |
Cumulative Counter |
2.7 Notification Measures
The following table describes measures provided by the SAPC belonging to the measure group: "policyControlFunctionNotificationsMeasuresGroup".
|
Measure Name |
Measure Meaning |
Measured Object Instance |
Alarm Id |
Measurement Type |
|---|---|---|---|---|
|
smsNotificationsFailed |
The number of SMS subscriber notifications not delivered to a SMS center. Increased when SMS notifications are generated at a higher rate than the SAPC can deliver. |
<SMS Center Id> |
- |
Cumulative Counter |
|
smsNotificationsSent |
The number of SMS subscriber notifications successfully sent to a SMS destination. If the SMS notification message is fragmented, each SMS segment increments the value of this measure. |
<SMS Destination IP> |
- |
Cumulative Counter |
|
soapNotificationsFailed |
The number of SOAP notifications not delivered to a web service end point. Increased when SOAP notifications are generated at a higher rate than the SAPC can deliver. |
<Web Service End Point> |
- |
Cumulative Counter |
|
soapNotificationsSent |
The number of SOAP notifications successfully sent to a web service end point destination. |
<Web Service Url> |
- |
Cumulative Counter |
2.8 Capacity Measures
The following table describes measures provided by the SAPC belonging to the measure group: "policyControlFunctionCapacityMeasuresGroup".
|
Measure Name |
Measure Meaning |
Measured Object Instance |
Alarm Id |
Measurement Type |
|---|---|---|---|---|
|
afActiveSessions |
The total number of simultaneous active AF sessions created through Rx. |
Sessions |
- |
Gauge |
|
afEmergencyActiveSessions |
The total number of simultaneous active emergency AF sessions created through Rx. |
Sessions |
- |
Gauge |
|
afSignallingActiveSessions |
The total number of simultaneous active AF signalling sessions. |
Sessions |
- |
Gauge |
|
fixedActiveSessions |
The total number of simultaneous active fixed sessions. The SAPC counts as a fixed session an IP-CAN Session created via Gx, whose IP-CAN-Type is Non-3GPP-EPS and RAT-Type is WLAN, or IP-CAN-Type is DOCSIS or IP-CAN-Type is xDSL or IP-CAN-Type is FBA. |
Sessions |
- |
Gauge |
|
ipCanAuthenticatedEmergencyActiveSessions |
The total number of simultaneous authenticated active emergency IP-CAN sessions. The SAPC counts as an authenticated session, sessions including Subscription-Id AVP. |
Sessions |
- |
Gauge |
|
ipCanUnauthenticatedEmergencyActiveSessions |
The total number of simultaneous unauthenticated active emergency IP-CAN sessions. The SAPC counts as an unauthenticated session, sessions including Subscription-Id AVP missing. |
Sessions |
- |
Gauge |
|
mobileActiveSessions |
The total number of simultaneous active mobile sessions. The SAPC counts as a mobile session an IP-CAN session created via Gx whose IP-CAN-Type is 3GPP-GPRS, WiMAX, 3GPP2, 3GPP-EPS. The SAPC also counts as mobile sessions, those whose IP-CAN-Type is Non-3GPP-EPS and RAT-Type is not WLAN. |
Sessions |
- |
Gauge |
|
sdActiveSessions |
The total number of simultaneous active Sd sessions in the SAPC. |
Sessions |
- |
Gauge |
|
subscribers |
The total number of subscribers provisioned in the SAPC internal database. |
Subscribers |
- |
Gauge |
|
sxActiveGlobalSessions |
The total number of simultaneous global active Sx sessions in the SAPC. |
Sessions |
- |
Gauge |
2.9 Resources Measures
The following table describes measures provided by the SAPC related to resources consumption.
|
Measure Name |
Measure Meaning |
Measured Object Instance |
Alarm Id |
Measurement Type |
|---|---|---|---|---|
|
CPULoad.Total |
Total CPU usage (percentage). |
<SAPC Cluster Node> |
- |
Gauge |
|
Mem.PercentUsed |
Used memory (percentage). |
<SAPC Cluster Node> |
- |
Gauge |
2.10 External Database Measures
The following table describes the measures provided by the SAPC belonging to the measure group: "policyControlFunctionExtDbMeasuresGroup".
|
Measure Name |
Measure Meaning |
Measured Object Instance |
Alarm Id |
Measurement Type |
|---|---|---|---|---|
|
ldapModifyRequests |
<LDAP Peer URL> |
- |
Cumulative Counter | |
|
ldapModifyResponsesFailed |
The number of received unsuccessful LDAP modify responses. The SAPC considers an unsuccessful response any result code different than 'non-error' result codes (listed in RFC 4511, except noSuchObject (32)) or a modify request dropped due to time-out or TCP-RST conditions. |
<LDAP Peer URL> |
- |
Cumulative Counter |
|
ldapSearchRequests |
<LDAP Peer URL> |
- |
Cumulative Counter | |
|
ldapSearchResponsesFailed |
The number of received unsuccessful LDAP search responses. The SAPC considers an unsuccessful response any result code different than 'non-error' result codes (listed in RFC 4511, except noSuchObject (32)) or a search request dropped due to time-out or TCP-RST conditions. |
<LDAP Peer URL> |
- |
Cumulative Counter |
|
soapExtDbNotificationResponsesFailed |
The number of unsuccessful SOAP notification responses (HTTP result code 500) sent to the external database. |
- |
Cumulative Counter | |
|
soapExtDbNotificationsReceived |
The number of SOAP notification requests received from the external database. |
- |
Cumulative Counter | |
|
soapExtDbNotificationsReceivedTooBusy |
The number of SOAP notifications not processed due to overload protection. |
- |
Cumulative Counter |
2.11 EBM Measures
The following table describes measures provided by the SAPC belonging to the measure group: "policyControlFunctionEbmMeasuresGroup".
|
Measure Name |
Measure Meaning |
Measured Object Instance |
Alarm Id |
Measurement Type |
|---|---|---|---|---|
|
ebmBusinessEvents |
The number of EBM events generated by the SAPC. |
<EBM ServerName> |
- |
Cumulative Counter |
|
ebmBusinessEventsNotSent |
The number of dropped EBM events due to EBM component queue size exceeded. |
<EBM ServerName> |
- |
Cumulative Counter |
2.12 Optional Measures
The following table describes measures provided by the SAPC belonging to the measure group: "policyControlFunctionOptionalMeasuresGroup". These measures are stopped by default.
|
Measure Name |
Measure Meaning |
Measured Object Instance |
Alarm Id |
Measurement Type |
|---|---|---|---|---|
|
ipCanEmergencyActiveSessionsPerApn |
The number of simultaneous active emergency IP-CAN sessions established per APN. |
<APN Id> |
- |
Gauge |
|
ipCanUnknownEmergencyActiveSessions |
The total number of simultaneous authenticated emergency IP-CAN sessions for subscribers not found in the SAPC. |
Sessions |
- |
Gauge |
To activate these measures, follow the procedure Start Measurement Collection Job, using their respective PmJobs:
- policyControlFunctionIpCanEmergencyActiveSessionsPerApnJob.
- policyControlFunctionIpCanUnknownEmergencyActiveSessionsJob.
- Note:
- The ipCanUnknownEmergencyActiveSessions measure will be fully operational after activation when previous emergency sessions are terminated. In the meantime, these values might be imprecise.
2.13 REST Provisioning Measures
The following table describes measures provided by the SAPC belonging to the measure group: "policyControlFunctionRestProvMeasuresGroup".
|
Measure Name |
Measure Meaning |
Measured Object Instance |
Alarm Id |
Measurement Type |
|---|---|---|---|---|
|
restProvServiceUnavailable |
The number of REST provisioning messages indicating too busy (HTTP status code set to 503). |
<REST Client IP> |
- |
Cumulative Counter |
2.14 Other Measures
The following table describes measures provided by the SAPC belonging to the measure group: "policyControlFunctionOtherMeasuresGroup".
|
Measure Name |
Measure Meaning |
Measured Object Instance |
Alarm Id |
Measurement Type |
|---|---|---|---|---|
|
reauthsOnToDTooBusy |
The number of Time of Day reauthorizations not processed due to overload protection. |
TimeTrigger |
- |
Cumulative Counter |
|
unknownSubscribers |
The number of requests received from a traffic gateway with unknown subscriber identifier. These requests are only counted when there is not Unknown subscriber profile defined in the SAPC. |
<PCEF Peer> |
Major Type: 193 Minor Type: 7077892 |
Cumulative Counter |
3 Measurements Configuration
COM PM Service provides an information model to allow configuration of performance management to specify the behavior of the related measures (for example, enabled measurements, granularity period).
A Performance Measurement Job is the process executed in the Network Element (NE) to either accumulate data or generate alarms:
- A Measurement Job is the process to accumulate measurement result data and assemble it for collection, inspection, or both. It can be defined either to collect the values for a Group of Measurement Types or to collect the value of a specific Measurement Type.
- A Threshold Job is the process to monitor for surpassed thresholds. When a threshold is surpassed, a notification (alarm or alert) is issued. A Threshold Job does not generate any measurement data.
For more information related to managing operations, refer to Configuration Management chapter in Performance Management.
To ease the operation, the SAPC provides (at installation time) the jobs needed to collect all the SAPC performance management measures and raise threshold-related alarms. The following figure shows a summary of the SAPC performance default configuration.
Figure 1 The SAPC Performance Management Instances
For details, look for SapcInstancesCounters inside Managed Object Model (MOM).
3.1 Managing Measurement Collection
At deployment time, to be easier to use, the SAPC provides all measurement collection jobs active, except the ones related to Section 2.12 Optional Measures
To stop the collection of the SAPC measures, follow the procedure in Stop Measurement Collection Job.
3.2 Managing Threshold Monitoring
PM generates alarm notifications when threshold monitoring is activated.
The following cases can happen:
- A new alarm is raised when an alarm criteria is fulfilled and no alarm is active for the measured instance.
- A changed alarm notification is sent (for example, change the alarm severity), at the end of the GP, when a new alarm criteria is fulfilled while an alarm is active
- A cleared alarm notification is sent, at the end of the GP, when all alarms clear criteria is fulfilled
PmThresholdMonitoring defines two threshold values, low and high. This can be used to define a hysteresis for the corresponding alarm. If the threshold direction (refer to MeasurementType) is INCREASING and the measurement value at the end of the granularity period is higher than the high threshold, the alarm is newly raised or changed. If the value is lower than the low threshold, the alarm is cleared or changed. For threshold direction DECREASING, the opposite applies.
Threshold monitoring can be used with both Cumulative Counters (CC) and Gauges. However, the measurement value in the threshold parameters (thresholdHigh, thresholdLow of PmThresholdMonitoring) is defined in different ways:
- Gauge: an absolute value.
- Cumulative counter: rate of variation per granularity
period.
An example describing 3 consecutive granularity periods with the following values:
thresholdHigh=600 thresholdLow=300 granularity period = 5 minutes (300 seconds)
- Granularity Period 1: The counter value is 601 (or higher value): the alarm is raised
- Granularity Period 2: The counter value is 450: the alarm is kept
- Granularity Period 3: The counter value is 299 (or lower value): the alarm is cleared
To ease the operation, the SAPC provides (at installation time) the threshold monitors ACTIVE, configured with thresholdHigh=600, thresholdLow=300 (and granularity period set to 5 minutes).
To stop the collection of the SAPC threshold monitors, follow the procedure in Stop Threshold Monitoring Job.
4 Performance Measurement Reports
To collect the Performance Measurement Report files from an external system, use SFTP as explained in System Administrator Guide.
Once the measurement jobs are set up, CoreMW is responsible for collecting the measurement results for every job. Once the results are ready, at the end of the granularity period of every measurement job, the COM PM functionality writes results into Result Output Period (ROP) report files.
The ROP files are XML files compliant with the 3GPP TS 32.432. The file format for XSD-based XML PM report files generated is A.2 in 3GPP TS 32.435, refer to Performance Management Report File Format, which means that it uses the optional positioning attributes on measurement types and results.
To ease the tracking between the column titles of the tables stated in Section 2 and the corresponding XML elements within reported files where the SAPC measures are produced, see following table for the most significant elements:
|
SAPC Measure Table Contents |
XML Element |
Examples |
|---|---|---|
|
Measure Group |
measInfoId |
<measInfo measInfoId="policyControlFunctionGxMeasuresGroup"> |
|
Measure Name |
measType |
<measType p="1">gxCcasInitSuccess</measType> |
|
Measure Value |
measValue |
<measValue measObjLdn="PolicyControlFunction=1,Network=1,DiameterNodes=1,DiameterNode=ggsn2NodeHostname.ggsn2NodeHostRealm.com"> <r p="1">546</r> </measValue> |
- Note:
- If the job is active, the report files are always generated. But, if the measure is not increased, it does not appear in the report file.