ISG Prepaid
- Overview
- Plug-in Configuration
- Configuration Overview
- Example - RADIUS Service Templates Configuration
- Use Case Configuration
- Validation
Overview
ISG Prepaid, a feature of the Cisco Intelligent Services Gateway (ISG), allows for the ISG to check the subscriber's available credit to determine whether to activate a specified service and how long the session can last. The subscriber's credit is administered by the CPS MsBM as a series of quotas representing either a duration of use (in seconds) or an allowable data volume (in bytes). 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.
The ISG uses the RADIUS protocol to facilitate interaction with CPS acting as the authentication, authorization, and accounting (AAA) server.
To obtain the first quota for a session, ISG submits an authorization request to the CPS, and CPS coordinates with the MsBM acting as 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 re-authorization. During re-authorization, 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.
Refer to the Cisco “Intelligent Services Gateway Configuration Guide” for further information on configuring ISG Prepaid on the ISG.
Plug-in Configuration
In order to install the plug-in, the following lines must be added to the following /etc/broadhop/xx/features files on the cluster manager:
iomanager0x/features file: com.broadhop.isgprepaid.service.feature pb/features file: com.broadhop.client.feature.isg.prepaid pcrf/features file com.broadhop.isgprepaid.interface.feature
After modifying the features files, run build_all.sh and reinit.sh on the cluster manager to update the system.
Set the Accounting and Authorization ports to match the ports configured on the ISG. The standard ports are 1815 for Accounting and 1814 for Authorization. Check the Enabled boxes in order to enable the ISG Prepaid service.
Configuration Overview
The following Prepaid configuration assumes familiarity with the basic ISG service configuration. The ISG Prepaid configuration is similar to the standard ISG configuration, with the addition of an MsBM Account Balance to set the quota and the setup of parameters needed by the ISG (for example, the name of the ISG Prepaid configuration that is configured on the ISG).
Following is an example of the ISG Prepaid configuration on the ISG:
subscriber feature prepaid WIFI_PREPAID threshold time 60 seconds threshold volume 1000000 bytes interim-interval 1 minutes method-list author PREPAID_AUTHOR_LIST method-list accounting PREPAID_ACCT_LIST password cisco
Example - RADIUS Service Templates Configuration
The following RADIUS Service Templates must be configured as part of an ISG Prepaid Service. Just as in a standard ISG Service, the ISG Prepaid service templates below will be added to the final ISG Service to be used by the subscriber.
The below example 2M-UP-DOWN-PREPAID uses the BASE_PREPAID_INTERNET_SERVICE template, and is instructing the ISG to use a prepaid configuration called WIFI_PREPAID which must be defined on the ISG. Change the values to match your particular setup.
The BASE_PREPAID_INTERNET_SERVICE template below is based on the ISG_PREPAID_ACCESS_ACCEPT which is a read-only template provided with the system. The values should match what is configured on your ISG.
The ISG_PREPAID_ACCESS_ACCEPT passes CONTROL-INFO parameters to the ISG. If you are only passing time or volume, you can select a different template to use to only pass the values needed by the ISG.
Use Case Configuration
| Step 1 | Open the Policy Builder GUI. | ||
| Step 2 | Go to the Services tab. | ||
| Step 3 | Under Use Case Templates, click Summary and then create a child use case template. | ||
| Step 4 | Name the new template IsgPrepaid. | ||
| Step 5 | In the newly
created template, under the
Service
Configurations section, click
Add. This lists all the service configuration
objects available on the PCRF and then select the
IsgChargeConfiguration object from the 'isgprepaid'
section as shown below:
  | ||
| Step 6 | Whenever a new Use Case Template is created, a corresponding empty Service Option container is created as well. Go to the Services section and then under Service Options find the IsgPrepaid folder, which represents the new ISG Prepaid Use Case Template created above. Create a child Service Option and name it IsgPrepaid. | ||
| Step 7 | Below are the
parameters that can be configured as part of the ISG Service Option. The actual
values will vary depending on your particular setup.
|
Validation
Verify prepaid accounting messages are being passed on ISG Prepaid accounting port 1815 and that quota is being debited from the CPS MsBM. Taking the tcpdump on ports 1814, 1815 and 1700 and analyzing the results in Wireshark can help verify proper transaction flow:
tcpdump -i any port 1700 or 1814 or 1815 -s0 -w pp.pcap
Feedback