%0 Conference Proceedings
%T The Design of a Single Funding Point Charging Architecture
%+ Universität Zürich [Zürich] = University of Zurich (UZH)
%+ Institute of Mathematics University of Zurich
%A Tsiaras, Christos
%A Waldburger, Martin
%A Machado, Guilherme, Sperb
%A Vancea, Andrei
%A Stiller, Burkhard
%Z Part 3: Management
%< avec comité de lecture
%( Lecture Notes in Computer Science
%B 18th European Conference on Information and Communications Technologies (EUNICE)
%C Budapest, Hungary
%Y Róbert Szabó
%Y Attila Vidács
%I Springer
%3 Information and Communication Technologies
%V LNCS-7479
%P 148-160
%8 2012-08-29
%D 2012
%R 10.1007/978-3-642-32808-4_14
%K Accounting
%K Authorization
%K Single Funding Point
%K Charging Architecture
%Z Computer Science [cs]
%Z Computer Science [cs]/Networking and Internet Architecture [cs.NI]Conference papers
%X Most federations across the world apply Single Sign-On (SSO) Authentication and Authorization Infrastructure (AAI) platforms. Thus, access to services offered by organizations, which belong to such a federation, can be granted to their users independent of their current location. The increasing demand to charge users for those service usages lead organizations to establish various charging mechanisms. However, until today the majority of organizations is using service-dependent solutions to perform charging. This policy absorbs the utility of an SSO system, since users still have to monitor and control each credit account separately. Therefore, the approach proposed defines an extension to SSO platforms, which is consolidated, non dispersed and service-independent. A Single Funding Point Charging Architecture (SFP-CA) allows users to settle payments using funds from the same credit account, for any type of service they use inside their federation.
%G English
%Z TC 6
%Z WG 6.2
%Z WG 6.6
%2 https://inria.hal.science/hal-01543145/document
%2 https://inria.hal.science/hal-01543145/file/978-3-642-32808-4_14_Chapter.pdf
%L hal-01543145
%U https://inria.hal.science/hal-01543145
%~ IFIP-LNCS
%~ IFIP
%~ IFIP-TC
%~ IFIP-TC6
%~ IFIP-WG6-6
%~ IFIP-WG6-2
%~ IFIP-EUNICE
%~ IFIP-LNCS-7479