1 / 6

RADIUS Prepaid Extensions

This document proposes extensions to RADIUS for prepaid services, enabling support for one-time charging events, tariff switching, querying, and balancing of prepaid resources. It aims to align RADIUS with Diameter Credit Control for feature equivalence and integration. The document emphasizes the need for flexibility and efficiency in managing prepaid quotas and charging events to enhance user experience.

roscar
Download Presentation

RADIUS Prepaid Extensions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RADIUS Prepaid Extensions draft-lior-radius-prepaid-extensions-07.txt A. Lior, Y. Li, Bridgewater Systems P. Yegani, Cisco K. Chowdhury, Nortel C. Guenther, Siemens Lior, Chowdhury,Yegani,Guenther

  2. Changes from 05 • Added support for One-time charging event. • As discussed in IETF60 incorporated the Guenther draft -- see: draft-guenther-radext-ppebc-00.txt) • Added support to allow a RADIUS Prepaid server to re-balance quotas using (see: draft-chiba-radius-dynauthor-ext-00.txt) • Added support for tariff switching • Cleaned up. Lior, Chowdhury,Yegani,Guenther

  3. One-Time Charging Event • Used for charging of Service Events where there is no session (or no immediate session). • purchase of a ring-tone. • purchase of a right-to-view content. • Note: • the actual downloading of the ring-tone maybe charged or not as part of the network access. It’s up to the operators to determine what gets charged. • If we don’t want to charge for the actual download • The ring-tone price can be adjusted down for prepaid users; • Use a IP-flow that is not prepaid metered. • Credit the account. Lior, Chowdhury,Yegani,Guenther

  4. Querying and Rebalancing Prepaid Resources • In cases where a Service Access Device (e.g. NAS) has been allocated quota and the user’s account is depleted (or near depletion) • For example, the user is attempting to purchase a ring-tone at one Service-Device, but his account is near zero, but quota is still outstanding at the NAS. • It should be possible for the Prepaid system to query the NAS to find out what is its current usage AND to allow the Prepaid system to reclaim some Quota and transfer it to another Service Access Device (in this case the Ring-Tone vending Device) Lior, Chowdhury,Yegani,Guenther

  5. Tariff Switching • Tariff rates switch based on time-of-day • NAS reports traffic used before the tariff switch and after the tariff switch. • Support single flows and multiple flows. Lior, Chowdhury,Yegani,Guenther

  6. Work Ahead • Feature-for-Feature equivalence to Diameter Credit Control. • Cleanup. • Incorporate ideas that are being developed now. • Capability Exchange etc.. • Integration with Diameter Credit Control. • Going to be hard. • The idea of having a simple translation function is not possible. • Fundamental difference exists. For example, in RADIUS the quotas are cumulative and in Diameter they are deltas. Lior, Chowdhury,Yegani,Guenther

More Related