You can assign subscribers a quota limit on selected services.
Each subscriber has 16 quota buckets, each of which you can define for volume or
sessions. When a subscriber uses a certain service, the amount of consumed volume or
number of sessions is subtracted from one of the buckets.
The service configuration determines which bucket to use for each service. Consumption
of volume buckets is measured in units of L3 kilobytes. Consumption of session buckets
is measured by the number of sessions. For example, you can define that the Browsing and
E-Mail services consume quota from Bucket #1, that the P2P service consumes quota from
Bucket #2, and that all other services are not bound to any particular bucket.
External quota provisioning systems can use the Quota Provisioning API to modify the
quota in each bucket dynamically. For example, you can increase the quota of a certain
bucket when a subscriber purchases additional quota. These external systems can also
query the amount of remaining quota in each bucket. This can be used, for example, to
show subscribers in a personal web page how much of their quota remains. For details on
Quota Provisioning API, see the Cisco Service Control SCE Subscriber API
External quota provisioning can also be acquired using the Quota Manager (QM), an
off-the-shelf solution provided by Cisco. For more information about the installation
and operation of the QM, see the Cisco Service Control Management Suite Quota
Manager User Guide.
External quota provisioning can also be acquired using the Gy quota model and Gx quota
model. For more information, see the Cisco Service Control Mobile Solution Guide
External quota provisioning is not supported when unidirectional classification is
The internal Cisco SCA BB quota provisioning system replenishes each quota bucket by a
fixed amount at fixed intervals.
Subscribers can be notified when they breach the quota in any bucket.