# PCC-Profile Schema Statistics

The PCC-Profile schema provides operational statistics that can be used for monitoring and troubleshooting the following products from StarOS Release 14.0 onward: IPCF.
This schema provides the following types of statistics:

- Counter: A counter records incremental data cumulatively and rolls over when the counter limit is reached. All counter statistics are cumulative and reset only by one of the following methods: roll-over when limit is reached, after a system restart, or after a clear command is performed. The limit depends upon the data type.
- Gauge: A gauge statistic indicates a single value; a snapshot representation of a single point in time within a defined time frame. The gauge changes to a new value with each snapshot though a value may repeat from one period to the next. The limit depends upon the data type.
- Information: This type of statistic provides information, often intended to differentiate sets of statistics; for example, a VPN name or IP address. The type of information provided depends upon the data type.

The data type defines the format of the data for the value provided by the statistic. The following data types are used in statistics for this schema:

- Int32/Int64: An integer, either 32-bit or 64-bit: For statistics with the Int32 data type, the roll-over to zero limit is 4,294,967,295. For statistics with the Int64 data type, the roll-over to zero limit is 18,446,744,073,709,551,615.
- Float: A numeric value that can be represented fractionally; for example, 1.345.
- String: A series of ASCII alphanumeric characters in a single grouping, usually pre-configured.

IMPORTANT:

Unless otherwise indicated, all statistics are counters and all statistics are standards-based.

Key Variables: Every schema has some variables which are typically referred to as 'key variables'. These key variables provide index markers to identify which object the statistics apply to. For example, in the card schema, the card number (variable %card%) uniquely identifies a card. For an HA service, the keys would be "%vpnname%" plus "%servname%", as the combination uniquely identifies an HA service. So, in a given measurement interval, one row of statistics will be generated per unique key. The schema keys are identified in the Description section of the table.
Table 1. Bulk Statistic Variables in the PCC-Profile Schema

Variables | Description | Data Type
--- | --- | ---
vpnname | The name of the context in which PCC-Profile is configured. This is a key variable. | String
vpnid | The identity number of the context in which CC-Profile is configured. This is a key variable. | String
servname | The name of the PCC service in which CC-Profile is configured. This is a key variable. | String
servid | The identity number of the PCC service in which CC-Profile is configured. This is a key variable. | String
total-sgsn-change | Total SGSN change processed by PCC Profile. Trigger: When SGSN change is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-qos-change | Total QOS change processed by PCC Profile. Trigger: When QOS change is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-rat-change | Total RAT change processed by PCC Profile. Trigger: When RAT change is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-tft-change | Total TFT change processed by PCC Profile. Trigger: When TFT change is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-plmn-change | Total PLMN change processed by PCC Profile. Trigger: When PLMN change is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-loss-of-flow | Total loss of flow processed by PCC Profile. Trigger: When loss of flow is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-recovery-of-flow | Total recovery of flow processed by PCC Profile. Trigger: When recovery of flow is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-ip-can-change | Total IP CAN change processed by PCC Profile. Trigger: When IP CAN change is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-qos-change-exceeding-auth | Total QOS change exceeding authorization processed by PCC Profile. Trigger: When QOS change exceeding authorization is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-rai-change | Total RAI change processed by PCC Profile. Trigger: When RAI change is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-user-location-change | Total User Location change processed by PCC Profile. Trigger: When User Location change is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-out-of-credit | Total out of credit prcessed by PCC Profile. Trigger: When out of credit prcessed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-reallocation-of-credit | Total Reallocation of credit processed by PCC Profile. Trigger: When Reallocation of credit is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-revalidation-timeout | Total Revalidation timeout processed by PCC Profile. Trigger: When Revalidation timeout is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-ip-address-allocation | Total IP Address allocation processed by PCC Profile. Trigger: When IP Address allocation is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-ip-address-release | Total IP Address release processed by PCC Profile. Trigger: When IP Address release is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-def-eps-bearer-qos-change | Total default EPS bearer QOS change processed by PCC Profile. Trigger: When default EPS bearer QOS change is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-an-gw-change | Total AN Gateway Address change processed by PCC Profile. Trigger: When AN Gateway Address change is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-succ-resource-alloc | Total successful resource allocation processed by PCC Profile. Trigger: When successful resource allocation is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-resource-modification-req | Total Resource Modification Request processed by PCC Profile. Trigger: When Resource Modification Request is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-pgw-trace-control | Total PGW Trace Control processed by PCC Profile. Trigger: When PGW Trace Control is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-ue-time-zone-change | Total UE Timezone change processed by PCC Profile. Trigger: When UE Timezone change is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
total-usage-report | Total Usage Report processed by PCC Profile. Trigger: When Usage Report is processed by PCC Profile. Availability: Across all PCC Profiles. | Unsigned Int32
IMPORTANT: For information on statistics that are common to all schema see the Statistics and Counters Overview chapter.