The Volume Reporting over Gx (VoGx) feature provides PCRF the capability to make real-time decisions based on the data usage by subscribers.

This feature is implemented using the existing non-CUPS architecture, for Control Plane. This implementation is done by mapping the existing VoGx framework and the CUPS data structures such as FAR, PDR, URR and so on.

Important

Volume Reporting over Gx is applicable only for volume quota.

The following steps explain how Volume Reporting over Gx works:

1. PCEF, after receiving the message from PCRF, parses the usage monitoring-related AVPs and sends the information to IMSA.

2. IMSA updates the information to ECS.

3. After the ECS is updated with the usage monitoring information from PCRF, the PCEF (ECS) starts tracking the data usage.

4. For session-level monitoring, the ECS maintains the amount of data usage.

5. For PCC rule monitoring, usage is monitored with the monitoring key as the unique identifier. Each node maintains the usage information per monitoring key. When the data traffic is passed, the usage is checked and reported against the usage threshold values.

   Note	In releases earlier than 21.22, the monitoring key value was in the range of 0-134217727. In 21.22 and later releases, the monitoring key value is in the range of 1-4000000000.

6. The PCEF continues to track data usage after the threshold is reached and before a new threshold is provided by the PCRF. If a new usage threshold is not provided by the PCRF in the acknowledgment of an IP-CAN Session modification where its usage was reported, then usage monitoring does not continue in the PCEF for that IP CAN session.

For additional information about this feature, refer the SAEGW Administration Guide.

Supported Standards

The Volume Reporting over Gx feature is based on the following standard: 3GPP TS 29.212 V9.5.0 (2010-06): 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control over Gx reference point (Release 9).

From Release 21.22 onwards, it is mandatory to define the monitoring-key urr-id-prefix entries for all the monitoring keys configured locally in the PCEF as part static and predefined rules.

Use the following configurations to enable the monitoring key range.

configure 
   active-charging service service_name 
      mon-key-urr-list list_name 
         monitoring-key value urr-id-prefix urr_id 
         end 

NOTES:

• mon-key-urr-list list_name : Specifies the name of monitoring key list. list_name must be a string of size 1-63.

• monitoring-key value : value must be an integer in the range of 1-4000000000.

• urr-id-prefix urr_id : urr_id must be an integer in the range of 1-8388607.

• Multiple monitoring key and URR ID combinations under the list name can be configured. The recommended limit is 2500 entries.

• This CLI command can be configured in both Control Plane and User Plane. After configuring the CLI command in Control Plane, it is mandatory to push the configuration to User Plane using PFD push mechanism. For RCM, it is mandatory to configure require rcm-configmgr on User Plane before configuring the CLIs. Both Control Plane and User Plane must be configured through CLI in RCM configuration.

• You should configure only unique monitoring key and URR-ID combinations. These URR-IDs configured through mon-key-urr-list should not coincide with the URR-IDs configured through urr-list . If such a configuration is attempted, the CLI throws an error.

• If there is a run-time addition of this CLI at Control Plane, it is necessary to push the CLIs using PFD push mechanism so that configurations can be updated at both ends. These configurations will apply next call onwards or at the time of next URR creation.

This section provides information about the CLI commands available for monitoring and troubleshooting VoGx in CUPS.