Manual

Cisco Packet Data Serving Node (PDSN) Release 2.0
Resource Management
24
12.3(11)T
The Billing Server updates its database with the amount of quota utilized by the user. Since the user
indicates quota renewal, the Billing Server apportions a fraction of prepaid account balance of the user.
It also assigns a new Quota ID for the current allocated quota and a corresponding threshold value for
the assigned quota. This information is passed on to the HAAA.
The Billing Server also indicates to the HAAA the time remaining in seconds for the next Tariff Switch
trigger point.
The HAAA sends the information received from the Billing Server into a RADIUS Access-Accept
message to be sent to PDSN. The attributes that are encapsulated into a PPAQ VSA include:
• New Quota ID for the current quota
• Allocated quota into VolumeQuota parameter
• Threshold corresponding to the assigned quota into VolumeThreshold parameter
The PTS attribute contains following subtypes:
– Quota ID previously received
– TariffSwitchInterval that indicates the time (in seconds) remaining before which the tariff
switch condition will trigger.
– Optionally TimeIntervalafterTariffSwitchUpdate that indicates the duration after the tariff
switch point when the PDSN will send an on-line Access Request if threshold point is not
reached.
After the PDSN receives the Access-Accept message from AAA, it parses the RADIUS packet and
retrieves the attributes inside it. The PDSN stores the information present in the packet, and updates it
with the quota allocated for the flow and the current threshold value corresponding to the allocated flow.
It also stores the new Quota-ID allocated for the current quota.
Additionally, the PDSN re-starts the timer indicated in TariffSwitchInterval attribute. The PDSN starts
the timer only if the timestamp of the Access Request + Tariff Switch Interval is more than the timestamp
of the Access Accept message. This time indicates the time remaining in seconds before the next tariff
switch condition will be hit.
Mobile IP Call Processing Per Second (CPS) Improvements
In previous Cisco PDSN Releases, the Mobile IP CPS rate was approximately 40—comparatively low
to that of Simple IP CPS which around 125. Mobile IP CPS was low because some of the Mobile IP
configurations are interface specific. When these configurations are applied to the virtual-template
interface (which is typical for the PDSN software), it takes considerable time to clone the virtual-access
from the Virtual-Template because of the presence of the Mobile IP configuration, and this directly
affects the CPS for Mobile IP service. The virtual-access are cloned when the calls are setup. To reduce
virtual-access cloning time, PDSN Release 2.0 supports commonly used per-interface configurations in
global configuration mode, and supports per-interface for backward compatibility.