PDF(164.2 KB) View with Adobe Reader on a variety of devices
ePub(231.3 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(147.8 KB) View on Kindle device or Kindle app on multiple devices
Updated:April 14, 2025
Document ID:222951
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes the use of the Cisco ECS CC Usage Reporting options to specify the USU volumes that are reported to the OCS.
Background Information
The StarOS Enhanced Charging Service (ECS) uses the Credit Control (CC) configuration Mode to configure prepaid services for Diameter/RADIUS applications. Within The Credit Control configuration Mode of the Active Charging Service Configuration in the Local Context, one of three ACS Credit Control Usage Reporting types can be configured.
USU - Used Service Units
OCS - Offline Charging System
Exec > ACS Configuration > Credit Control Configuration active-charging service service_name > credit-control [local]host_name(config-dcca)#
- Suppresses the input and output octets. If the Granted-Service-Unit (GSU) AVP comes with CC-Total-Octets, then the device sends total input and output octets in Used-Service-Unit (USU) AVP. If it comes with Total-Octets, the device sends only Total-Octets in USU. - Use this command to configure reporting usage only for granted quota. On issuing this command, the Used-Service-Unit AVP reports quotas based on grant (for example, only the quotas present in the Granted-Service-Unit AVP).
With this command, only the units for which the quota was granted by the DCCA server is reported irrespective of the reporting reason.
A case study shows undesired reporting of Used Service Units by the PGW for an IoT device which was caused by the configuration. It also illustrates the configuration change made to resolve it. The OCS recorded twice the expected usage for IoT devices. This exhausted the IoT subscribers data bucket/allowance.
Observation
Two separate used-service unit (USU) were reported; one with THRESHOLD and another with OTHER_QUOTA_TYPE. The OCS combines both USUs, which then results in the generation of the CDR. Because the PGW had the default Usage Reporting configuration option, default usage-reporting quotas-to-report, the PGW included CC-Total-Octets under one USU and CC-Input-Octets/CC-Output-Octet in different USU. This caused the OCS to generate CDRs with twice the amount of usage for the subscriber.
Used Service Units
CC-Total-Octets
Used Service Units
CC-Input-Octets
CC-Output-Octets
Solution
The Credit Control Usage Reporting configuration was changed to use the option, Usage-reporting quotas-to-report based on grant. Consequently, the CCR-U has only one USU reported with CC-Total-Octets, CC-Input-Octets, and CC-Output-Octets. Other_quota_type was not reported. This ensured that the amount reported would only be counted once on the OCS.