CDR generation is supported for S-GW in the Cisco UPC CUPS architecture.

CDRs in CUPS is generated to collect charging information for UE bearers in S-GW. On receiving a charging trigger, the Control Plane node of CUPS pulls the information from the corresponding user plane nodes and the collected volume counts are added to the S-GW CDR.

S-GW CDR is supported for both default and dedicated bearer.

Note	Currently, S-GW CDR is supported in custom24 dictionary.

Charging data is collected based on the following triggers:

• Access-side triggers:

  • ULI Change

  • RAT Change

  • Management intervention (Interim CDRs are not supported)

  • Normal/Abnormal call release

• Network-side triggers:

  • QCI Change

  • APN AMBR Change

Charging Characteristics Profile Information in 3GPP

The CUPS CP gateway adheres to 3GPP Release 8 of Specification 32.298, that states that the Charging Characteristic profile value is 4 bit as depicted as given (P1-P4) here.

The available cc-profile range is 0 to 15 and cannot go higher than 15.

If the cc-profile value corresponding to the 4 bits in the Charging Characteristics IE is not configured on the CP, there will be issues with volume reporting in CDRs.

For more information on the CLI command, see the CC topic in Command Line Interface Reference Guide.