Manual

Cisco Packet Data Serving Node (PDSN) Release 2.0
Resource Management
15
12.3(11)T
• VPDN sessions with authentication and authorization for the user performed at AAA.
• Mobile IP sessions with FA-CHAP performed for the session/NAI at AAA.
• Proxy mobile IP sessions with authentication and authorization for the user performed at AAA.
Prepaid service is also available for sessions opened with MSID-based authentication access.
Note Either Volume-based or Duration-based, but not both options in one prepaid flow, are supported on the
PDSN. Multiple flows, each supporting either Volume or Duration based prepaid service, are allowed on
the PDSN. The PDSN can be configured to support only Volume-based, or only Duration-based, or either
type of Prepaid service per flow at any point in time.
Volume-based accounting for prepaid flows other than VPDN will count the bytes present in the PPP
payload. For VPDN flows, it will count the bytes present in the PPP packet including the PPP packet
header. A session that has multiple flows can have some of the flows with prepaid data service enabled,
each either Volume-based or Duration-based, while other flows may not be prepaid enabled.
Tariff-based prepaid service is also supported for volume-based prepaid data service on the PDSN. To
support tariff-based prepaid service, the Prepaid Billing Server should have the following capabilities:
• Charged by volume—different tariff for different time of day.
• The Billing server allocates a different quota (volume-based) for a user that is determined by a tariff
for a different time-of-day (this ensures the two charging rates do not overlap).
Restrictions for Prepaid Support in Cisco PDSN Release 2.0
• Prepaid for remote address based accounting is not supported.
• Online Access Request messages are sent with Service-Type as “outbound” (instead of “Authorize
Only”), and user password is included in the message.
• There is no Prepaid MIB support in the present release.
• Prepaid for the HA is not supported.
Prepaid Billing
When a user performs Simple IP access with AAA authentication, or Mobile IP access with FA-CHAP,
the Prepaid capable PDSN sends a RADIUS Access-Request message for Authentication and
Authorization. The Prepaid capable PDSN informs the Billing Server of its own Prepaid capabilities by
including a PPAC VSA in the RADIUS Access-Request message.
The Home RADIUS performs Authentication and Authorization procedures as usual. If the HAAA
identifies that a user is a prepaid user from its user profile, the HAAA interfaces with the Billing Server
to retrieve prepaid related information for the user, and passes on the prepaid related information in the
Access Request message. The Billing Server performs prepaid authorization for the user. The prepaid
authorization procedure at HAAA and Billing Server consists of the following steps:
• Checking the PPAC VSA.
• Checking the home network policy.
• Checking the user’s account balance and state.