Path coupled accounting mechanisms for "all IP networks"

Andreas Klenk, Philipp Schlicker, Ralph Kühne, Ali Fessi, Changpeng Fan, Falko Dressler, Georg Carle

Research output: Contribution to journalConference articlepeer-review

3 Scopus citations

Abstract

Accounting in Beyond 3G (B3G) networks is especially challenging, because of the rapidly increasing number of new services and tariff models introduced or to be introduced. Services are not provided statically anymore but must be deployed in short time spans to meet the volatile market demands. As the complexity of the services grows the demand for an equally flexible accounting mechanism increases as well. However nowadays' static accounting approaches with dedicated meters for certain metering tasks might scale badly in this envisioned dynamic environment. Innovative services can not be deployed if expensive accounting tasks in terms of metering resources are required and the dedicated systems cannot guarantee to handle the additional load. On-path configuration of the meters can provide for a dynamic metering configuration. The accounting configuration can be performed agnostic of the roles of the accounting entities in the B3G network architecture allowing a more flexible accounting. The distributed nature of on-path accounting allows for fault tolerance and provides load-balancing. Thus existing metering resources are utilized better and this enables the introduction of demanding accounting mechanisms for new services.

Original languageEnglish
Pages (from-to)267-271
Number of pages5
JournalIEE Conference Publication
Issue number2005-11182
DOIs
StatePublished - 2005
Externally publishedYes
Event6th IEE International Conference on 3G and Beyond, 3G 2005 - London, United Kingdom
Duration: 7 Nov 20059 Nov 2005

Keywords

  • Accounting
  • All IP Networks
  • Distributed Load Balancing
  • Meter Selection Algorithms
  • NSIS

Fingerprint

Dive into the research topics of 'Path coupled accounting mechanisms for "all IP networks"'. Together they form a unique fingerprint.

Cite this