Cisco Cisco IOS Software Release 12.4(22)XR
208
Cisco Packet Data Serving Node Release 5.2 for Cisco IOS Release 12.4(22)XR4
OL-21580-01
Resource Management
When the billing server successfully authorizes the user as a valid prepaid user, it notifies the HAAA
that it supports prepaid service based on volume, or duration, or both, depending on the configuration at
the billing server and capabilities as indicated by the PDSN. The HAAA encodes the information in a
PPAC VSA to the PDSN, and indicates that volume-based or duration-based prepaid (or both) service is
supported by the billing server.
that it supports prepaid service based on volume, or duration, or both, depending on the configuration at
the billing server and capabilities as indicated by the PDSN. The HAAA encodes the information in a
PPAC VSA to the PDSN, and indicates that volume-based or duration-based prepaid (or both) service is
supported by the billing server.
HAAA sends the authorization response to the prepaid capable PDSN using RADIUS access-accept or
reject messages. The authorization response includes a PPAQ VSA in the same RADIUS access-accept
message stating an initial quota, quota-id and a threshold value of the quota for the prepaid flow
corresponding to the user.
reject messages. The authorization response includes a PPAQ VSA in the same RADIUS access-accept
message stating an initial quota, quota-id and a threshold value of the quota for the prepaid flow
corresponding to the user.
When the PDSN sends online access-request messages to HAAA for prepaid related functionality, it
does not set the User-Password (= 2) field in the message, and normal RADIUS message authentication
is set and performed with Message Authenticator. Currently, the User-Password is set in online Access
Requests to the default value of “cisco”.
does not set the User-Password (= 2) field in the message, and normal RADIUS message authentication
is set and performed with Message Authenticator. Currently, the User-Password is set in online Access
Requests to the default value of “cisco”.
If the PDSN does not receive the PPAC VSA from the HAAA in the initial RADIUS access-accept
message, or the message is included but indicates that “Prepaid Accounting not used”, the PDSN will
release the user’s prepaid flow if the RADIUS access-accept message includes a PPAQ VSA. The PDSN
will send an access-request to HAAA to return the quota allocated with update-reason VSA that
indicates client service termination.
message, or the message is included but indicates that “Prepaid Accounting not used”, the PDSN will
release the user’s prepaid flow if the RADIUS access-accept message includes a PPAQ VSA. The PDSN
will send an access-request to HAAA to return the quota allocated with update-reason VSA that
indicates client service termination.
If the PDSN is capable of supporting prepaid service based on either volume or duration, then the PDSN
will enable prepaid service for the flow based on the Billing server-indicated service that applies to the
session in PPAC. If the Billing server also indicates that the PDSN can allocate either volume or
duration, then the PDSN will enable prepaid service based on the type of quota (volume or duration)
present in PPAQ from HAAA. If both types of quota are present in PPAQ, then prepaid flow is not opened
on the PDSN.
will enable prepaid service for the flow based on the Billing server-indicated service that applies to the
session in PPAC. If the Billing server also indicates that the PDSN can allocate either volume or
duration, then the PDSN will enable prepaid service based on the type of quota (volume or duration)
present in PPAQ from HAAA. If both types of quota are present in PPAQ, then prepaid flow is not opened
on the PDSN.
If the PDSN is capable of supporting prepaid service based on volume, and billing server indicates that
it will support prepaid service based on duration, then the PDSN will close the prepaid flow. The PDSN
will send an access-request message with update-reason VSA indicating “Client Service Termination”.
The same logic applies to the PDSN if it supports prepaid based on duration, and billing server returns
prepaid service based on volume.
it will support prepaid service based on duration, then the PDSN will close the prepaid flow. The PDSN
will send an access-request message with update-reason VSA indicating “Client Service Termination”.
The same logic applies to the PDSN if it supports prepaid based on duration, and billing server returns
prepaid service based on volume.
If the PDSN receives an access-accept message containing the PPAC VSA indicating prepaid service
supported, but the initial quota is not included in the message, the PDSN will close the flow. Since no
quota was received in the access-accept, the PDSN will not send further RADIUS access-request
message to HAAA.
supported, but the initial quota is not included in the message, the PDSN will close the flow. Since no
quota was received in the access-accept, the PDSN will not send further RADIUS access-request
message to HAAA.
To ignore billing server interaction of HAAA for access-requests sent by the PDSN during MIP
reregistration for FA-CHAP, the PDSN will include the Session-Continue VSA set to “TRUE” in the
online access-request messages.
reregistration for FA-CHAP, the PDSN will include the Session-Continue VSA set to “TRUE” in the
online access-request messages.
If multiple flows are present for the session that hosted the prepaid flow, and a prepaid flow was stopped,
and if it was the last flow for the session, then the session will be deleted by the PDSN. If one of MIP
flows expires and it is not the last flow for the session, then the PDSN will close the flow locally. If the
resource revocation mechanism is enabled on PDSN, the relevant resource revocation mechanism will
be applied in this case.
and if it was the last flow for the session, then the session will be deleted by the PDSN. If one of MIP
flows expires and it is not the last flow for the session, then the PDSN will close the flow locally. If the
resource revocation mechanism is enabled on PDSN, the relevant resource revocation mechanism will
be applied in this case.
If the SIP flow is closed (for example, a PPP session is torn down or quota for the SIP flow expires), then
all the other MIP flows, both prepaid and non-prepaid, will also get closed. If SIP flow is closing due to
allocated quota expiry, it will send access-request message with update-reason as “Quota Reached”. In
other cases where the SIP session is closed, the access-request will be sent with update-reason as “Client
Service Termination”. All other prepaid flows for the PPP session will also send access-request
messages to close the prepaid service and return unused quota. The update-reason for all these flows will
contain value for “Main SI Released”.
all the other MIP flows, both prepaid and non-prepaid, will also get closed. If SIP flow is closing due to
allocated quota expiry, it will send access-request message with update-reason as “Quota Reached”. In
other cases where the SIP session is closed, the access-request will be sent with update-reason as “Client
Service Termination”. All other prepaid flows for the PPP session will also send access-request
messages to close the prepaid service and return unused quota. The update-reason for all these flows will
contain value for “Main SI Released”.