Design Issues for Prepaid Data Service
draft-francis-prepaid-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Paul Francis , James Brandt , Bryan Gleeson | ||
| Last updated | 2002-06-26 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Prepaid voice services have proven to be extremely successful. There is a desire to replicate this success for data services. Prepaid for data presents new technical challenges, primarily due to the wide range of billing that may be applied to data services--- volume or time billing, differential billing by type of application (gaming, steaming, browsing, voice), billing by destination, and even billing of specific content. Furthermore, a single data prepaid service may need to accomodate simultaneous network access by multiple devices (phone, laptop, PDA). This paper discusses design issues for a protocol between a prepaid application and the data network element. It defines an architecture and terminology. It describes basic characteristics of data prepaid service, as well as some advanced features. It analyzes the main technical issues, especially performance issues. Finally, this paper describes the semantics of an illustrative prepaid data service protocol. This document does not, however, specify such a protocol.
Authors
Paul Francis
James Brandt
Bryan Gleeson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)