Table Of Contents

Configuring Prepaid Support

Configuring a Prepaid Billing Plan

Prepaid WAP Support

Configuring Prepaid Support

---

This chapter contains the following information about Content Service Gateway (CSG2) support for prepaid billing:

•Configuring a Prepaid Billing Plan

•Prepaid WAP Support

Configuring a Prepaid Billing Plan

A billing plan identifies one or more content billing services to be used for prepaid billing.

To define a billing plan, follow these steps, beginning in global configuration mode:

	Command	Purpose
Step 1	Router (config)# ip csg billing billing-plan-name	Defines a CSG2 billing plan, and enters CSG2 billing configuration mode.
Step 2	Router (config-csg-billing)# service service-name	Associates a service with a CSG2 billing plan.

The following example shows how to define a prepaid billing plan:

ip csg billing REGULAR

 service MOVIES

 service BROWSING

When a CSG2 prepaid subscriber initiates a new IP session, a large amount of quota might be reserved for the IP session if the IP session maps to a service configured for basis byte ip or basis byte tcp. The reservation often greatly exceeds the amount of quota that the session actually uses. This does not result in incorrect charging. However, as a result of one or more large reservations for IP sessions, the CSG2 might make additional requests for quota from the quota server.

Prepaid WAP Support

Some upstream WAP browsing traffic occurs because the CSG2 must inspect the reply before determining whether the traffic is an MMS transaction. However, the downstream WAP browsing replies are discarded if quota is depleted.

Control information is charged against quota for non-MMS transactions. WSP PDU types SUSPEND and RESUME are never charged against quota.