Cisco Cisco IOS Software Release 12.4(22)XR
209
Cisco Packet Data Serving Node Release 5.2 for Cisco IOS Release 12.4(22)XR4
OL-21580-01
Resource Management
When threshold for the quota is reached, the PDSN sends an access-request to HAAA to retrieve more
quota for the flow. In case the values of threshold for the quota and the quota allocated are same, then
on quota expiry (when Quota = Threshold), the PDSN will treat this as flow as closed, and send an
access-request with Update-reason as “Quota reached”.
quota for the flow. In case the values of threshold for the quota and the quota allocated are same, then
on quota expiry (when Quota = Threshold), the PDSN will treat this as flow as closed, and send an
access-request with Update-reason as “Quota reached”.
When the quota expires for the flow, the PDSN sends an online access-request to the HAAA to indicate
that the prepaid flow is released. During this time the PDSN marks the flow as deleted, and stops
switching any packets for the flow. On receipt of the access-accept from the AAA server for this
access-request, the PDSN deletes the prepaid flow for the user and sends an accounting stop.
that the prepaid flow is released. During this time the PDSN marks the flow as deleted, and stops
switching any packets for the flow. On receipt of the access-accept from the AAA server for this
access-request, the PDSN deletes the prepaid flow for the user and sends an accounting stop.
If resource revocation mechanism is enabled at the PDSN, then the PDSN will send a resource revocation
to the HA to clear binding at the HA, and the PDSN will clear the visitor information for the flow.
to the HA to clear binding at the HA, and the PDSN will clear the visitor information for the flow.
On receiving a RADIUS Disconnect Request (POD) or MIP revocation messages, the PDSN sends an
online RADIUS access-request message containing the used quota and the update-reason sub-type set to
“Remote forced disconnect”. The PDSN will delete the flow and send resource revocation message to
the HA, and will send the existing RADIUS Accounting-Stop.
online RADIUS access-request message containing the used quota and the update-reason sub-type set to
“Remote forced disconnect”. The PDSN will delete the flow and send resource revocation message to
the HA, and will send the existing RADIUS Accounting-Stop.
Volume-based Prepaid Data Service Flow
The metric for accounting volume-based prepaid service is total bytes flowing through the user flow in
upstream and downstream direction.
upstream and downstream direction.
Step 1
The prepaid capable PDSN determines that SIP or MIP setup requires a RADIUS access-request
message to be sent to the Home RADIUS Server. For SIP sessions, the use has to be authenticated with
the AAA server instead of local authentication. In case of MIP users, FA-CHAP authentication is
required.
message to be sent to the Home RADIUS Server. For SIP sessions, the use has to be authenticated with
the AAA server instead of local authentication. In case of MIP users, FA-CHAP authentication is
required.
The PDSN includes its own PPAC VSA to inform the HAAA or billing server that it supports prepaid
based on volume (value = 1 or 3). If resource revocation is enabled on the PDSN, then it will send a
SessionTerminationCapability (STC) attribute indicating that it can support resource revocation for MIP
sessions.
based on volume (value = 1 or 3). If resource revocation is enabled on the PDSN, then it will send a
SessionTerminationCapability (STC) attribute indicating that it can support resource revocation for MIP
sessions.
The Home RADIUS server performs the regular authentication and authorization of the access-request
sent by the user. If the user profile indicates the user is a prepaid subscriber, HAAA interfaces with the
billing server, and provides the billing server with the prepaid information for the user as received in the
access-request message.
sent by the user. If the user profile indicates the user is a prepaid subscriber, HAAA interfaces with the
billing server, and provides the billing server with the prepaid information for the user as received in the
access-request message.
Step 2
After the billing server receives the user prepaid information, it checks the capabilities of PDSN (sent
in the PPAC VSA). The billing server also checks that the user has a valid balance and account status.
The billing server then indicates to the PDSN that it supports prepaid packet data service based on
volume. It also assigns the initial quota for the user, which is typically a fraction of total available quota
for the user. The quota allocated for the user is identified by a quota ID assigned by the billing server for
the user for the current quota. The billing server interfaces with HAAA and provides this information to
the HAAA.
in the PPAC VSA). The billing server also checks that the user has a valid balance and account status.
The billing server then indicates to the PDSN that it supports prepaid packet data service based on
volume. It also assigns the initial quota for the user, which is typically a fraction of total available quota
for the user. The quota allocated for the user is identified by a quota ID assigned by the billing server for
the user for the current quota. The billing server interfaces with HAAA and provides this information to
the HAAA.
The HAAA encapsulates the prepaid information received for the user in a RADIUS access-accept
message and sends it to the PDSN. The RADIUS message includes:
message and sends it to the PDSN. The RADIUS message includes:
•
A PPAQ VSA that contains the following parameters:
–
Initialized quota for the user flow specified in VolumeQuota parameter
–
Quota ID for the quota allocated
–
A threshold value for the quota allocated in VolumeThreshold parameter
•
A PPAC VSA indicating prepaid service is based on volume.