SRC VTA Overview
The SRC Volume-Tracking Application (SRC VTA) allows service providers to track and control the network usage of subscribers and services. You can control volume and time usage on a per-subscriber or per-service basis. This level of control means that service providers can offer tiered services that use volume as a metric, while also controlling abusive subscribers and applications.
When a subscriber or service exceeds bandwidth limits (or quotas), the SRC VTA can take actions, including imposing rate limits on traffic, sending an e-mail notification, or charging extra for additional bandwidth consumed. You can configure multiple SRC VTAs.
If you use the SRC VTA with the deep packet inspection (DPI) feature, you can control the volume of traffic for specific applications, such as peer-to-peer file sharing.
Table 1 defines terms that are used in the SRC VTA documentation and sample data.
For information about loading the sample data for the SRC VTA, see Loading Sample Data into a Juniper Networks Database (SRC CLI).
Table 1: SRC VTA Terms
Allowance of data volume that subscribers purchase and can transfer (upload or download) at any time. (This term is used in sample and typical SRC VTA configurations and is not inherent in the SRC VTA itself.)
Record that details a subscriber’s use of bought quota. (This term is used in sample and typical SRC VTA configurations and is not inherent in the SRC VTA itself.)
Allowance of data volume that a service provider allocates to subscribers on a recurrent basis. Subscribers use this allowance to upload or download data. (This term is used in sample and typical SRC VTA configurations and is not inherent in the SRC VTA itself.)
Record that tracks a subscriber’s use of periodic quota. (This term is used in sample and typical SRC VTA configurations and is not inherent in the SRC VTA itself.)
Service for which the SRC VTA monitors usage. The SRC VTA activates the service for subscribers when they have a positive balance in their SRC VTA accounts, and deactivates the service when the SRC VTA account has a negative balance. (This term is used in sample and typical SRC VTA configurations and is not inherent in the SRC VTA itself.)
Record of credit and debit entries that track a subscriber’s use of a particular network resource.
Period of activity between a subscriber and an SRC VTA.
SRC VTA Service and Subscriber Accounts
SRC VTA accounts represent the resources available to a service or a subscriber. You can configure SRC VTA accounts and then charge a particular service or subscriber’s usage against the account. Each subscriber or service can have a different quota, or allowance of data volume.
You can set up the way the SRC VTA charges accounts and how account balances are updated.
You can also configure actions in response to changes in account balances. Available actions include stopping a service, starting a service, updating an account balance, sending an e-mail, and running a script. For example, if account A is emptied, the action might be to stop services X and Y, and start service Z.
The SRC VTA requires a relational database to store information about accounts. The SRC VTA installation includes sample schemas for the MySQL and Oracle databases.
SRC VTA Sessions
The SRC VTA tracks subscriber activity through VTA sessions. SRC VTA sessions do not necessarily correspond to an individual subscriber session or service session. For example, a single service session can correspond to multiple SRC VTA sessions if the service session covers multiple billing periods.
The SRC VTA can track more than just the volume and time of a service session, it can track any state of a subscriber derived from SAE plug-in events and respond to the state change.
The SRC VTA requires a relational database to store information about sessions. The SRC VTA installation includes sample schemas for the MySQL and Oracle databases.
The SRC VTA lets you set triggers at multiple levels to provide flexible and extensive volume-based services. For example:
When the volume remaining for the account is 300 MB, turn on the internet-256 service, turn off the internet-512 service, and send an e-mail to the subscriber.
When the volume level reaches 100 MB, send an e-mail warning to the subscriber.
When the volume level is 0 MB, turn on the continue-TCP-only service, turn off the internet-256 service, send an e-mail to the subscriber, and notify the accounting server.
When the volume level is –100 MB, turn off the continue-TCP-only service, send an e-mail to subscriber, and notify the accounting server.