Table Of Contents

Configuring ISG Support for Prepaid Billing

Contents

Prerequisites for ISG Prepaid Billing Support

Restrictions for ISG Prepaid Billing Support

Information About ISG Prepaid Billing Support

Overview of ISG Support for Prepaid Billing

Tips for Preventing ISG from Allocating More Volume Quota than Subscriber is Entitled

ISG Prepaid Threshold

ISG Prepaid Idle Timeout

ISG Prepaid Tariff Switching

Benefits of ISG Prepaid Billing

How to Configure ISG Support for Prepaid Billing

Configuring RADIUS Attribute Support for ISG Prepaid Billing

Creating an ISG Prepaid Billing Configuration

Default Prepaid Configuration

Prerequisites

Enabling ISG Prepaid Billing

Enabling ISG Prepaid Billing in a Service Policy Map

Enabling ISG Prepaid Billing in Service Profile on the AAA Server

Redirecting Subscriber Traffic upon Exhaustion of Credit

Credit-Exhausted Event

Configuring L4 Redirection in a Service Policy Map

Applying a Service Policy Map to Subscriber Traffic upon Exhaustion of Credit

What to Do Next

Forwarding Subscriber Traffic upon Depletion of Quota

Quota-Depleted Event

Prerequisites

What to Do Next

Monitoring ISG Prepaid Billing Sessions

Troubleshooting ISG Prepaid Billing Support

Configuration Examples for ISG Prepaid Billing Support

ISG Prepaid Billing Support: Example

ISG Policies for Handling Credit-Exhausted and Quota-Depleted Prepaid Billing Events: Example

Additional References

Related Documents

Technical Assistance

Feature Information for ISG Support for Prepaid Billing

Configuring ISG Support for Prepaid Billing

---

First Published: March 20, 2006

Last Updated: March 20, 2006

Intelligent Services Gateway (ISG) is a Cisco IOS software feature set that provides a structured framework in which edge devices can deliver flexible and scalable services to subscribers. ISG prepaid billing support allows an ISG to check a subscriber's available credit to determine whether to allow the subscriber access to a service and how long the access can last. ISG prepaid billing works on a repeated reauthorization model in which fragments of credit, called quotas, are allotted by a prepaid billing server. This model allows a subscriber to be connected to multiple simultaneous prepaid services, each with a different billing rate. ISG supports time- and volume-based prepaid billing.

This module provides information about how to configure ISG support for prepaid billing.

Finding Feature Information in This Module

Your Cisco IOS software release may not support all features. To find information about feature support and configuration and platform requirements, use the "Feature Information for ISG Support for Prepaid Billing" section.

Contents

•Prerequisites for ISG Prepaid Billing Support

•Restrictions for ISG Prepaid Billing Support

•Information About ISG Prepaid Billing Support

•How to Configure ISG Support for Prepaid Billing

•Configuration Examples for ISG Prepaid Billing Support

•Additional References

•Feature Information for ISG Support for Prepaid Billing

Prerequisites for ISG Prepaid Billing Support

For information about release and platform support, see the "Feature Information for ISG Support for Prepaid Billing" section.

The tasks in this document assume that a subscriber session has been created and a method of service activation is in place.

Restrictions for ISG Prepaid Billing Support

•ISG volume-based prepaid billing is not supported on the Cisco 10000-PRE2.

•ISG prepaid billing support can only be applied to traffic flows that have been defined by an ISG traffic class.

•Quotas are measured in seconds for time and in bytes for volume. There is no way to change the unit of measure.

•The volume quota is for combined upstream and downstream traffic.

Information About ISG Prepaid Billing Support

Before you configure support for ISG prepaid billing, you should understand the following concepts:

•Overview of ISG Support for Prepaid Billing

•Tips for Preventing ISG from Allocating More Volume Quota than Subscriber is Entitled

•ISG Prepaid Threshold

•ISG Prepaid Idle Timeout

•ISG Prepaid Tariff Switching

•Benefits of ISG Prepaid Billing

Overview of ISG Support for Prepaid Billing

ISG prepaid billing support allows ISG to check the available credit for a subscriber to determine whether to activate the service for the subscriber and how long the session can last. The subscriber's credit is administered by a prepaid billing server as a series of quotas representing either a duration of use (in seconds) or an allowable data volume (in bytes). A quota is an allotment, or fragment, of available credit. Allocating quotas in fragments rather than providing all the credit at once enables ISG to support the use of credit for multiple simultaneous prepaid sessions.

ISG uses the RADIUS protocol to facilitate interaction between ISG and external authentication, authorization, and accounting (AAA) servers and prepaid billing servers. A single device can serve as the AAA server and the billing server.

To obtain the first quota for a session, ISG submits an authorization request to the AAA server. The AAA server contacts the prepaid billing server, which forwards the quota values to ISG. ISG then monitors the session to track the quota usage. When the quota runs out or a specified limit is reached, ISG performs reauthorization. During reauthorization, the prepaid billing server may provide ISG with an additional quota if there is available credit. If no further quota is provided, ISG will log the user off from the service or perform some other specified action.

When a service is deactivated, the cumulative usage is provided to the prepaid billing server in an Accounting-Stop message.

Tips for Preventing ISG from Allocating More Volume Quota than Subscriber is Entitled

The Cisco IOS prepaid volume monitor polling timer determines when ISG will initiate a prepaid reauthorization. The polling timer value is (15 seconds < polling-monitor-time < 300 seconds). This value is calculated dynamically based on the QV value, actual rate and the configured volume threshold. The prepaid volume monitor polling timer is not directly configurable.

To avoid revenue leak during the first authorization (when usage rate is unknown), the QV value should be a minimum of (15 x access-rate). In cases in which the usage rate is known, the QV value should be at least (15 x usage-rate).

In cases in which the input access-rate is much higher than the QV value, it is recommended that the correct QV value be calculated using the following formula: access-rate x 15 > QV < access-rate x 300. For example, an ADSL2 or VDSL user access-rate can be up to 20 Mbps. That is approximately 2.5 megabytes of data in one second. Calculate the QV value by using the following formula: 2.5 MB x 15 seconds > QV < 2.5 MB x 300 seconds. This calculation results in a QV value between 37.5 and 750 MB. We recommend avoiding the boundaries, so for this example you might pick a value of QV = 100MB

ISG Prepaid Threshold

By default, ISG sends reauthorization requests to the billing server when a subscriber's quota is exhausted. ISG prepaid thresholds allow ISG to send reauthorization requests before a quota is used up. When a prepaid threshold is configured, ISG sends a reauthorization request to the billing server when the amount of remaining quota is equal to the value of the threshold. Prepaid thresholds can be configured for both time and volume.

For example, if the prepaid threshold is configured for 10 seconds, and the prepaid billing server sends ISG a quota of 30 seconds, ISG will send a reauthorization request to the prepaid billing server when the subscriber has used up 20 seconds of the quota and has 10 seconds remaining.

ISG Prepaid Idle Timeout

The ISG prepaid idle timeout can be used to suspend a prepaid service session if no traffic is received for a specified period of time. ISG keeps the session up during the suspension but releases all quota previously received for the prepaid session. Subsequent traffic on the session will cause ISG to send a reauthorization request and download a new quota for the session.

ISG Prepaid Tariff Switching

Prepaid tariff switching allows changes in tariffs during the lifetime of a session. Typically, a service provider uses prepaid tariff switching to offer different tariffs to an end user during an active connection; for example, changing a user to a less expensive tariff during off-peak hours.

---

Note ISG is not involved in computing the billing rate changes that occur at tariff switch points. Billing rate change computations are performed by the prepaid billing server.

---

ISG supports prepaid tariff switching by using two quotas that correspond to the time before and the time after the switch point. In the authorization response to ISG, the prepaid billing server specifies the tariff switch point and the quotas for the periods before and after the tariff switch.

ISG uses the pre-tariff switch quota until the tariff switch occurs. If the pre-tariff switch quota is exhausted (or the threshold is reached) prior to the tariff switch, reathorization occurs as usual. Upon tariff switch, ISG starts using the post-tariff switch quota for prepaid session monitoring. Reauthorization occurs only when either of these quotas is exhausted, not when a tariff change occurs.

This dual-quota approach to accounting for prepaid tariff switching staggers reauthorization requests according to the usage of the subscriber and prevents the billing server from being overwhelmed with reauthorization requests at the time of a tariff switch.

Benefits of ISG Prepaid Billing

Concurrent Prepaid Service Access

The ISG Support for Prepaid Billing feature is capable of supporting concurrent prepaid service access while maintaining the same pool of quota at the prepaid billing server. ISG services can be configured for concurrent or sequential access. Concurrent access allows users to log on to a service while simultaneously connected to other services.

Real-Time Billing

The ISG Support for Prepaid Billing feature allows for real-time billing with maximum flexibility, regardless of the type of service and billing scheme. Users can be billed on a flat rate, air-time, or volume basis.

Redirection Upon Exhaustion of Quota

When a user runs out of quota, ISG can redirect the user to a portal where the user can replenish the quota without being disconnected from the service.

Returning Residual Quota

ISG can return residual quota to the billing server from services that a user is logged into but not actively using. The quota that is returned to the billing server can be applied to other services that the user is actively using.

Threshold Values

ISG enables you to configure threshold values that cause prepaid sessions to be reauthorized before the subscriber completely consumes the allotted quota for a service.

Traffic Status During Reauthorization

You can prevent revenue leaks by configuring ISG to drop connected traffic during reauthorization of a service. The user remains connected to the service and does not need to log in to the service again, but no traffic is forwarded during the reauthorization process. This prevents a user from continuing to use a service for which the user has run out of quota while ISG sends a reauthorization request to the billing server.

Simultaneous Volume-Based and Time-Based Prepaid Billing

ISG supports rating on both time and volume simultaneously for prepaid services. The prepaid billing server may allocate quotas in both time and volume, and ISG monitors the session on both these parameters. ISG performs a reauthorization whenever either of these quota types is exhausted.

How to Configure ISG Support for Prepaid Billing

This section documents the following tasks:

•Configuring RADIUS Attribute Support for ISG Prepaid Billing (required)

•Creating an ISG Prepaid Billing Configuration (optional)

•Enabling ISG Prepaid Billing (required)

•Redirecting Subscriber Traffic upon Exhaustion of Credit (optional)

•Forwarding Subscriber Traffic upon Depletion of Quota (optional)

•Monitoring ISG Prepaid Billing Sessions (optional)

•Troubleshooting ISG Prepaid Billing Support (optional)

Configuring RADIUS Attribute Support for ISG Prepaid Billing

Perform this task to enable ISG to include RADIUS attribute 44 in Access-Request packets and attribute 55 in Accounting-Request packets.

SUMMARY STEPS

1. enable

2. configure terminal

3. radius-server attribute 44 include-in-access-req [vrf vrf-name]

4. radius-server attribute 55 include-in-acct-req

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	radius-server attribute 44 include-in-access-req [vrf vrf-name] Example: Router(config)# radius-server attribute 44 include-in-access-req	Sends RADIUS attribute 44 (Accounting Session ID) in Access-Request packets before user authentication.
Step 4	radius-server attribute 55 include-in-acct-req Example: Router(config)# radius-server attribute 55 include-in-acct-req	Sends the RADIUS attribute 55 (Event-Timestamp) in Accounting-Request packets.

Creating an ISG Prepaid Billing Configuration

Perform this task to create or modify an ISG prepaid billing parameters configuration. This configuration can be referenced in service profiles or service policy maps in which ISG prepaid support has been enabled.

Default Prepaid Configuration

Note that a default prepaid configuration exists with the following parameters:

subscriber feature prepaid default

 threshold time 0 seconds

 threshold volume 0 bytes

 method-list authorization default

 method-list accounting default

 password cisco

The default configuration will not show up in the output of the show running-config command unless you change any one of the parameters.

The parameters of named prepaid configurations are inherited from the default configuration, so if you create a named prepaid configuration and want only one parameter to be different from the default configuration, you have to configure only that parameter.

Prerequisites

This task assumes that AAA method lists, server groups, and servers have been configured. See the Cisco IOS Security Configuration Guide for more information.

SUMMARY STEPS

1. enable

2. configure terminal

3. subscriber feature prepaid {name-of-config | default}

4. interim-interval number-of-minutes

5. method-list {accounting | authorization} name-of-method-list

6. password password

7. threshold {time seconds | volume {kilobytes Kbytes | megabytes Mbytes | bytes bytes}}

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	subscriber feature prepaid {name-of-config | default} Example: Router(config)# subscriber feature prepaid conf-prepaid	Creates a new ISG prepaid configuration or specifies an existing configuration so it can be modified.
Step 4	interim-interval number-of-minutes Example: Router(config-prepaid)# interim-interval 5	Enables interim prepaid accounting and specifies the interval at which ISG will send interim prepaid accounting records.
Step 5	method-list {accounting | authorization} name-of-method-list Example: Router(config-prepaid)# method-list accounting list1	Specifies the AAA method list to be used for ISG prepaid accounting or authorization.
Step 6	password password Example: Router(config-prepaid)# password cisco	Configures the password to be used for ISG prepaid authorization and reauthorization requests.
Step 7	threshold {time seconds | volume {kilobytes Kbytes | megabytes Mbytes | bytes bytes}} Example: Router(config-prepaid)# threshold time 20	Configures the threshold at which ISG will send a reauthorization request to the prepaid billing server. The quota provided by the billing server minus the configured threshold equals the value at which ISG will send a reauthorization request •This command can be entered twice to configure thresholds in both time and volume.

Enabling ISG Prepaid Billing

Perform one of the following tasks to enable prepaid billing in a service policy map or a remote service profile:

•Enabling ISG Prepaid Billing in a Service Policy Map

•Enabling ISG Prepaid Billing in Service Profile on the AAA Server

Enabling ISG Prepaid Billing in a Service Policy Map

Perform this task to enable ISG prepaid billing support in a service policy map.

Prerequisites

ISG prepaid billing is enabled in a traffic class within a service policy map. This task assumes that you have defined the traffic class map and associated IP access lists. See the module "Configuring ISG Subscriber Services" for more information.

SUMMARY STEPS

1. enable

2. configure terminal

3. policy-map type service policy-map-name

4. [priority] class type traffic class-map-name

5. prepaid config name-of-configuration

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	policy-map type service policy-map-name Example: Router(config)# policy-map type service mp3	Creates or defines a service policy map, which is used to define an ISG service.
Step 4	[priority] class type traffic class-map-name Example: Router(config-service-policymap)# class type traffic class-acl-101	Associates a previously configured traffic class with the policy map.
Step 5	prepaid config name-of-configuration Example: Router(config-control-policymap-class-traffic)# prepaid config conf-prepaid	Enables ISG support for prepaid billing and applies a configuration that defines the prepaid billing parameters. Note The presence of this command does not guarantee that prepaid billing will be applied to the flow. This command causes the first prepaid authorization request. Whether prepaid billing will be applied to the flow is determined by the billing server.

What to Do Next

You may want to configure a method of activating the service policy map or service profile; for example, control policies can be used to activate services. For more information about methods of service activation, see the module "Configuring ISG Subscriber Services."

Enabling ISG Prepaid Billing in Service Profile on the AAA Server

Perform this task to enable ISG support for prepaid billing in a service profile that is configured on a remote AAA server.

SUMMARY STEPS

1. Add the ISG Traffic Class attribute to the service profile.

2. Add the ISG Prepaid Billing VSA to the service profile.

DETAILED STEPS

	Command or Action	Purpose
Step 1	Add the ISG Traffic Class attribute to the service profile. Cisco-AVpair = "ip:traffic-class=in access-group [<acl_number> | name <acl_name>] [priority <n>]" or Cisco-AVpair = "ip:traffic-class=out access-group [<acl_number> | name <acl_name>] [priority <n>]"	Specifies input and output traffic to which the service will apply. •Both an input and output traffic classifier can be added to a service profile.
Step 1	Add the ISG Prepaid Billing VSA to the service profile. 26,9,1 = "prepaid-config={<name-of-config> | default"	Enables ISG support for prepaid billing and applies a configuration that defines the prepaid billing parameters.

What to Do Next

You may want to configure a method of activating the service policy map or service profile; for example, control policies can be used to activate services. For more information about methods of service activation, see the module "Configuring ISG Subscriber Services."

Redirecting Subscriber Traffic upon Exhaustion of Credit

Service providers often want to offer subscribers an opportunity to recharge their accounts when they have run out of credit for their prepaid services. The tasks in this section enable you to redirect a subscriber's Layer 4 traffic to a specified server when the subscriber has run out of credit.

Before you configure ISG Layer 4 Redirect for exhaustion of credit, you should understand the following concept:

•Credit-Exhausted Event

Perform the following tasks to redirect a subscriber's Layer 4 traffic upon exhaustion of credit:

•Configuring L4 Redirection in a Service Policy Map

•Applying a Service Policy Map to Subscriber Traffic upon Exhaustion of Credit

Credit-Exhausted Event

The ISG credit-exhausted event occurs when the prepaid server responds with an Access-Accept packet with a quota value of zero (time or volume) and an idle timeout greater than zero. In this case, the prepaid server has determined for certain that the subscriber does not have enough credit, but the idle timeout provides a grace period in which the subscriber could recharge the account. Typically, a service provider would want to redirect the subscriber's traffic to a web portal where the subscriber could recharge the account. At the end of the idle-timeout interval, ISG will send a reauthorization request.

The default ISG behavior is to drop subscriber packets when the credit-exhausted event occurs.

---

Note Layer 4 redirection is one action that a service provider could take when a subscriber has run out of credit. Other actions can be configured instead of or in addition to Layer 4 redirection.

---

Configuring L4 Redirection in a Service Policy Map

Perform this task to configure ISG Layer 4 redirection in a service policy map.

The ISG Layer 4 Redirect feature can also be configured in a service profile on a AAA server. For more information about redirecting Layer 4 subscriber traffic, see the module "Redirecting Subscriber Traffic Using ISG Layer 4 Redirect".

Prerequisites

The ISG Layer 4 Redirect feature is configured under a traffic class within the service policy map. This task assumes that you have defined the traffic class map. See the module "Configuring ISG Subscriber Services" for more information.

Traffic can be redirected to a server or server group. If you are redirecting traffic to a server group, this task assumes that the server group has been configured. See the module "Configuring ISG Subscriber Services" for more information about configuring server groups.

SUMMARY STEPS

1. enable

2. configure terminal

3. policy-map type service policy-map-name

4. [priority] class type traffic class-name

5. redirect to {group server-group-name | ip ip-address [port port-number]} [duration seconds] [frequency seconds]

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	policy-map type service policy-map-name Example: Router(config)# policy-map type service redirect-service	Creates or defines a service policy map, which is used to define an ISG service.
Step 4	[priority] class type traffic class-name Example: Router(config-service-policymap)# class type traffic class-all	(Optional) Associates a previously configured traffic class with the policy map.
Step 5	redirect to {group server-group-name | ip ip-address [port port-number]} [duration seconds] [frequency seconds] Example: Router(config-service-policymap-class-traffic)# redirect to group redirect-sg	Redirects traffic to a specified server or server group.

Applying a Service Policy Map to Subscriber Traffic upon Exhaustion of Credit

Perform this task to configure a control policy that will apply a service to subscriber traffic upon exhaustion of credit.

Prerequisites

If you specify a named control class map, this task assumes that the class map has been configured. See the module "Configuring ISG Control Policies" for information about configuring control class maps.

SUMMARY STEPS

1. enable

2. configure terminal

3. policy-map type control policy-map-name

4. class type control {control-class-name | always} event credit-exhausted

5. action-number service-policy type service name policy-map-name

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	policy-map type control policy-map-name Example: Router(config)# policy-map type control policyA	Creates or modifies a policy map that defines a control policy.
Step 4	class type control {control-class-name | always} event credit-exhausted Example: Router(config-control-policymap)# class type control always event credit-exhausted	Specifies a control class and event for which actions may be configured.
Step 5	action-number service-policy type service name policy-map-name Example: Router(config-control-policymap-class-control)# 1 service-policy type service name redirect-profile	Applies the specified service policy map. •Applies the service policy map or service profile in which the ISG Layer 4 Redirect feature has been configured.

What to Do Next

Control policies must be applied to a context by using the service-policy type control command.

Forwarding Subscriber Traffic upon Depletion of Quota

By default, ISG drops subscriber packets when a subscriber's quota has been depleted. This task enables you override the default and forward subscriber traffic when the quota-depleted event occurs.

Before you perform this task you should understand the concept described in the "Quota-Depleted Event" below.

Quota-Depleted Event

A quota-depleted event occurs when a subscriber's quota is exhausted and ISG has not yet received a reauthorization response from the billing server. This event can occur in two situations:

•When a prepaid threshold is not configured and the subscriber's quota is used up.

•When a prepaid threshold is configured but the quota is exhausted before the prepaid server responds to the reauthorization request that ISG sent when the threshold was met.

The quota-depleted event is not necessarily an indication that a subscriber does not have any more credit. ISG does not know for certain whether the subscriber has any more credit until a reauthorization response is returned from the billing server. For this reason, some service providers may choose to forward subscriber packets upon quota depletion until a reauthorization response is returned.

The default ISG behavior is to drop subscriber packets when a quota-depleted event occurs.

Prerequisites

If you specify a named control class map, this task assumes that the class map has been configured. See the module "Configuring ISG Control Policies" for information about configuring control class maps.

SUMMARY STEPS

1. enable

2. configure terminal

3. policy-map type control policy-map-name

4. class type control {control-class-name | always} event quota-depleted

5. action-number set-param drop-traffic false

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	policy-map type control policy-map-name Example: Router(config)# policy-map type control policyB	Creates or modifies a policy map that can be applied globally, to an interface, or to an ATM VC to specify a control policy.
Step 4	class type control {control-class-name | always} event quota-depleted Example: Router(config-control-policymap)# class type control always event quota-depleted	Specifies a control class and event for which actions may be configured.
Step 5	action-number set-param drop-traffic false Example: Router(config-control-policymap-class-control)# 1 set-param drop-traffic false	Configures ISG to continue to allow traffic to pass when they quota has been depleted.

What to Do Next

Control policies must be applied to a context by using the service-policy type control command.

Monitoring ISG Prepaid Billing Sessions

Perform this task to monitor ISG prepaid sessions.

SUMMARY STEPS

1. enable

2. show subscriber session [detailed] [identifier identifier | uid session-id | username name]

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	show subscriber session [detailed] [identifier identifier | uid session-id | username name] Example: Router# show subscriber session detailed	Displays ISG subscriber session information.

Troubleshooting ISG Prepaid Billing Support

Perform these steps to troubleshoot ISG prepaid billing support.

SUMMARY STEPS

1. show subscriber session

2. Make sure service authentication was successful.

3. Make sure the AAA method list is valid and has been configured.

4. test aaa

5. debug subscriber policy prepaid

DETAILED STEPS

---

Step 1 Use the show subscriber session command to make sure the service in which prepaid billing support is configured has been activated.

Step 2 If the service requires service authentication, make sure the authentication succeeded.

Step 3 Make sure the AAA method list referred to in the prepaid billing configuration is valid and has been configured with the aaa accounting network command.

Step 4 Use the test aaa command to make sure the AAA server is reachable from ISG.

Step 5 Use the debug subscriber policy prepaid command to display debug messages about prepaid operation.

---

Configuration Examples for ISG Prepaid Billing Support

This section contains the following examples:

•ISG Prepaid Billing Support: Example

•ISG Policies for Handling Credit-Exhausted and Quota-Depleted Prepaid Billing Events: Example

ISG Prepaid Billing Support: Example

The following example shows ISG prepaid billing support configured with the following parameters:

•The time threshold is 20 seconds.

•The volume threshold is 1000 bytes.

•When the quota-depleted event occurs, ISG will drop subscriber packets until the billing server sends another quota.

•When the credit-exhausted event occurs, subscriber packets will be redirected to the server group "redirect-sg".

•The prepaid service is called "mp3" and is configured directly on the router in a service policy map.

•The AAA method list that will be used for this service to authenticate subscribers is called "cp-mlist". That is the same method list to which the service accounting records will be sent.

•Prepaid authorization, reauthorization and accounting messages will be sent to the AAA method list called "ap-mlist".

!

aaa authorization network default local

aaa authorization network ap-mlist group sg2

aaa authentication network cp-mlist group sg1

aaa accounting network cp-mlist group sg1

aaa accounting network ap-mlist group sg2

service-policy type control RULEA 

!

class-map type traffic CLASS-ALL

!

class-map type traffic CLASS-ACL-101

    match access-group input 101

!

policy-map type control RULEA

 class type control always event credit-exhausted

  1 service-policy type service name redirectprofile

!

policy-map type service redirectprofile

 class type traffic CLASS-ALL

  redirect to group redirect-sg

policy-map type service mp3

 class type traffic CLASS-ACL-101

  authentication method-list cp-mlist

  accounting method-list cp-mlist

  prepaid conf-prepaid 

subscriber feature prepaid conf-prepaid

 threshold time 20

 threshold volume 1000 bytes

 method-list accounting ap-mlist

 method-list authorization default

 password cisco

ISG Policies for Handling Credit-Exhausted and Quota-Depleted Prepaid Billing Events: Example

In the following example, a single control policy called "RULEA" has been defined to override the ISG prepaid default behavior by forwarding subscriber packets after a quota-depleted event and redirecting subscriber packets after a credit-exhausted event.

!class-map type traffic CLASS-ALL

!

policy-map type control RULEA

 class type control always event quota-depleted

  1 set-param drop-traffic false

 class type control always event credit-exhausted

  1 service-policy type service name l4redirect

!

policy-map type service l4redirect

 class type traffic CLASS-ALL

  redirect to group SESM

!

subscriber feature prepaid conf-prepaid

 threshold time 100

 threshold volume 1000 bytes

 method-list author prepaidlist

 method-list accounting default

 password cisco

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122sb/cr/isg_r/index.htmber 
feature prepaid default

 threshold time 0

 threshold volume 0 

 method-list author default

 method-list accounting default

 password cisco

Additional References

The following sections provide references related to ISG support for prepaid billing.

Related Documents

Related Topic	Document Title
ISG commands	Cisco IOS Intelligent Services Gateway Command Reference
AAA configuration tasks	The "Authentication, Authorization, and Accounting (AAA)" section in the Cisco IOS Security Configuration Guide, Release 12.2
AAA commands	The "Authentication, Authorization, and Accounting (AAA)" section in the Cisco IOS Security Command Reference, Release 12.2

Technical Assistance

Description	Link
Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.	http://www.cisco.com/public/support/tac/home.shtml

Feature Information for ISG Support for Prepaid Billing

Table 16 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.2(28)SB or later releases appear in the table. If you are looking for information on a feature in this technology that is not documented here, see the "Intelligent Services Gateway Features Roadmap."

Not all commands may be available in your Cisco IOS software release. For details on when support for specific commands was introduced, see the command reference documents.

Cisco IOS software images are specific to a Cisco IOS software release, a feature set, and a platform. Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.

---

Note Table 16 list only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.

---

Table 16 Feature Information for ISG Support for Prepaid Billing

Feature Name	Releases	Feature Configuration Information
ISG: Accounting: Tariff Switching	12.2(28)SB	Prepaid tariff switching allows changes in tariffs during the lifetime of a session. ISG supports prepaid tariff switching by using two quotas that correspond to the time before and the the time after the tariff switch point. Tariff switching can also be used between accounting methods, such as switching from prepaid billing to post paid billing. •ISG Prepaid Tariff Switching •How to Configure ISG Support for Prepaid Billing
ISG: Accounting: Time-Based Prepaid	12.2(28)SB	ISG prepaid billing support allows ISG to check a subscriber's available credit to determine whether to allow the subscriber access to a service and how long the access can last. ISG supports time-based prepaid billing. The following sections provide information about this feature: •Information About ISG Prepaid Billing Support •How to Configure ISG Support for Prepaid Billing
ISG: Accounting: Volume-Based Prepaid	12.2(28)SB	ISG prepaid billing support allows ISG to check a subscriber's available credit to determine whether to allow the subscriber access to a service and how long the access can last. ISG supports volume-based prepaid billing. The following sections provide information about this feature: •Information About ISG Prepaid Billing Support •How to Configure ISG Support for Prepaid Billing

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2007 Cisco Systems, Inc. All rights reserved.