Syntax
grant service-type to extended-percent percent quota-type for BEST OF quota-name using mon-key
Parameters
- service-type
- One of the following:
- time
- total volume
- uplink volume
- downlink volume
Note: If you are using a policy table for this parameter, click Use Policy Table, choose the field (column) representing the parameter.
Click OK.
- extended-percent
- An extended, non-integer percentage that can exceed 100 (for example, 102.4%).
Note: If you are using a policy table for this parameter, click Use Policy Table, choose the field (column) representing the parameter.
Click OK.
- quota-type
- One of the following:
- used (default)—Calculates the quota to grant by subtracting the specified amount in bytes from the initial quota limit minus the quota used so far.
- initial—Calculates the quota to grant by subtracting the specified amount in bytes from the initial quota limit.
Note: If you are using a policy table for this parameter, click Use Policy Table, choose the field (column) representing the parameter.
Click OK.
- quota-name
- Name(s) of quota defined in the CMP database.
Note: If you are using a policy table for this parameter, click Use Policy Table, choose the field (column) representing the parameter.
Click OK.
- mon-key
- Name(s) of a monitoring key in the CMP database.
Note: If you are using a policy table for this parameter, click Use Policy Table, choose the field (column) representing the parameter.
Click OK.
Description
Allows quota profiles to be associated with one or more monitoring keys. This action can be used at the session and rule levels. If two policy actions grant usage for the same monitoring key or usage instance, the last action takes precedence, unless an action grants uplink volume followed by an action that grants downlink volume (or vice versa), which case the actions are grouped as one action when the message is processed. A policy that grants quota for a monitoring key will overwrite any previous grant of quota for that same monitoring key. This includes any subtraction previously enabled for the same monitoring key. See
Managing Quotas for information on quotas. See
Managing Monitoring Keys for information on monitoring keys. The best quota is determined using the following rules:
- Passes are always better than plans
- Between two passes, the one with the higher priority is better
- Between two passes with equal priorities, the one with the earlier expiration date is better
- Between two passes with equal priorities and expiration dates, the one with the earlier purchase date is better
Example
where the request is creating a new session
grant total volume to 100 percent used for BEST OF Monthly1,Daily1 using key1
continue processing message