EP1695300A1 - Procede pour facturer un service dans un reseau de communication - Google Patents

Procede pour facturer un service dans un reseau de communication

Info

Publication number
EP1695300A1
EP1695300A1 EP04804651A EP04804651A EP1695300A1 EP 1695300 A1 EP1695300 A1 EP 1695300A1 EP 04804651 A EP04804651 A EP 04804651A EP 04804651 A EP04804651 A EP 04804651A EP 1695300 A1 EP1695300 A1 EP 1695300A1
Authority
EP
European Patent Office
Prior art keywords
service
client
switching device
application server
service switching
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
EP04804651A
Other languages
German (de)
English (en)
Inventor
Walter Held
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Solutions and Networks GmbH and Co KG
Original Assignee
Siemens AG
Nokia Siemens Networks GmbH and Co KG
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Siemens AG, Nokia Siemens Networks GmbH and Co KG filed Critical Siemens AG
Priority to EP04804651A priority Critical patent/EP1695300A1/fr
Publication of EP1695300A1 publication Critical patent/EP1695300A1/fr
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
    • H04L12/1467—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network involving prepayment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0892—Network architectures or network communication protocols for network security for authentication of entities by using authentication-authorization-accounting [AAA] servers or protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/562—Brokering proxy services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos

Definitions

  • a packet-oriented communication network with service users (for example SIP clients), service providers (for example application servers) and a brokering application broker (for example SIP proxy) that is not in the service relationship between a service user device (client) and an application server for the duration of the service relationship this relationship is involved, (eg no stateful SIP proxy), it is impossible for the proxy to provide a reliable charging function for registered customers (users and service providers).
  • service users for example SIP clients
  • service providers for example application servers
  • a brokering application broker for example SIP proxy
  • Proxy remains in the communication relationship for the duration of the service relationship (stateful proxy), or billing runs separately between the application server and client without involving the proxy, ie the operator of the proxy is exclusively the access provider.
  • a total invoice from a single source, even for services used, can - if at all - only be achieved with great effort in postprocessing -> distributed billing functions at the proxy operator and at the application server provider.
  • this solution requires ensuring that the user of a service is a customer of the proxy and server operator at the same time, and on the other hand that data is transferred to the central invoice divider.
  • This provider is thus able to offer its end customers a reliable invoice from a single source with package-oriented services from a wide variety of partner service providers.
  • the basic service provider can act both as a simple broker of a service and as an intermediary with "rebranding" ("rebranding" means that the operator of the proxy is a service of a
  • Partner service provider does not offer under the original name of the service but under its own product name).
  • this procedure is: a) to charge registered end customers (clients) with a credit account in real time for user fees for requested and used services, or b) to create a uniform overall bill for all used services from different providers on a regular basis (e.g. monthly) for all used services ,
  • the procedure ensures that a) the customer only pays for what he uses, and b) the service provider is paid for his services.
  • this procedure creates the prerequisite for the customer to be able to be shown as an option in real time which charges have been made for the service or, in the case of prepaid service, how much credit is still available.
  • the basis of this solution is a reliable billing function, in which all partner components (client, proxy / application broker, application server) are integrated during service use.
  • Client Authenticates with the proxy and requests service.
  • Proxy / Application Broker Mediates service and keeps a record of the client's use of this service.
  • Application Server Offers service and uses tickets to inform the proxy about the establishment and course of the service relationship between him and the client.
  • Figure 1 describes the relationships of the partner components with one another and the basic sequence from the authentication of the client through the service request and service provision to charging.
  • the client After the client has authenticated to the authentication-authorization-accounting server (AAA server) using the proxy (l) / (2), it receives from the proxy together with information on where the application server is located ( Destination) a billing reference (pl) that is generated by the proxy to perform the billing function for the upcoming service use (3).
  • AAA server authentication-authorization-accounting server
  • the client uses the information it has received from the proxy to request the desired service from the application server (4). This confirms the service request to the client (5). This establishes the service relationship between the client and the application server.
  • the application server After the service relationship has been established between the client and the application server and as long as the service is in use, the application server creates tickets at regular intervals (e.g. 1 per minute), which are sent to the billing function on the proxy (6). These tickets contain the reference pl, which allows the proxy to be efficiently transferred to the billing table (billing Table), and the reference sl, which the server itself has created, and with which it can later access its data efficiently when it receives feedback from the proxy and terminate an existing service relationship.
  • billing table billing Table
  • the reference sl which the server itself has created, and with which it can later access its data efficiently when it receives feedback from the proxy and terminate an existing service relationship.
  • the proxy After receiving a ticket (6), the proxy determines the client (IP address C1) on the basis of the reference pl contained in the ticket and requests confirmation of this charging data for each ticket received (7). If the confirmation was not received after a certain time (e.g. 1 second), the request (7) is repeated once or twice.
  • the client After receipt of the confirmation request, the client verifies the ticket and, if necessary, sends a confirmation to the proxy (8).
  • the proxy After receiving a confirmation from the client, the proxy saves the ticket for later billing (9) and informs the server that the client has confirmed the ticket.
  • the billing function on the proxy updates the customer's credit balance.
  • the proxy informs the client that the credit has almost been used up. This can be done, for example, with the next request for a ticket (7). If the credit is used up, the proxy will delete the entry in the billing table and the application server will no longer accept further tickets for this customer and negatively acknowledge these tickets to the server, whereupon the server will possibly terminate the service relationship with the client.
  • the proxy informs the application server that a ticket has been negatively acknowledged, and returns the reference sl to the application server. Using the reference sl, the server is then able to terminate the service relationship with the client.
  • the proxy informs the application server that it could not receive a receipt from the client for a ticket, returning the reference sl to the application server. Using the reference sl, the server is then able to terminate the service relationship with the client.
  • Timer tl for billing table entry expires.
  • the proxy monitors the receipt of the tickets from the server. As soon as a ticket (6) arrives, the set timer is reset. When the timer expires, the entry in the table is deleted. Any tickets that subsequently arrive from the server will be negatively acknowledged.
  • this procedure does not require that the server and / or client log off from the proxy when the service relationship is ended. This means that a charge ticket is always sent to the client in advance for the current charging interval. This ensures that the client does not have to pay Uses services without paying for them by simply stopping the service before a charging interval expires to prevent it from being billed for the past interval.
  • the monitoring timer tl in the billing table must in any case be greater than the length of the charging interval that is agreed between the client and the application server. It must be chosen large enough to avoid that a lost (and therefore repeated by the server) ticket message to the proxy causes the proxy to invalidate the billing table entry.
  • tl must not be chosen too large, in order to avoid, for example, that denial-of-service attacks by malicious clients lead to a shortage of the billing table resources and ultimately to the unavailability of these services.
  • a reasonable value for tl is 2-3 times the length of the charging interval. Since the length of the charging intervals of the individual service relationships (see Fig. 1) can be different, the length of the monitoring timer tl is made variable. As soon as the proxy receives a ticket from the server, it uses the length of the charging interval specified therein and uses this to determine the length of tl in order to monitor the receipt of the next ticket from the server for this service relationship.
  • a fixed initial value for this timer is used for the billing table (eg 5 seconds).
  • the conditions for the service relationship are agreed between the client and server. By choosing a short 1st interval and, if necessary, special conditions for it, it can be ensured that even if the service is not provided (e.g. server failure, software error, incompatibility of client and server software) despite the service relationship being established for the Service users experience no or only a slight disadvantage.
  • the application server can possibly cancel the service relationship with the client due to the lack of a receipt on the ticket.
  • - Client functionality can be expanded e.g. at i. Accumulation of the fee messages transmitted by the proxy and display of these fees at the terminal for fee monitoring in real time, i. Possibility for end users to manually reject tickets as an option, e.g. when a certain self-imposed fee limit is reached.
  • the described method allows the operator of a stateless proxy or application broker to offer registered application service providers and registered customers a reliable, accurate and trustworthy billing function at defined intervals in a simple manner by the client and server constantly being in the background during the service provision Notify an independent third party (proxy) about the fees incurred and the billing function is also performed by the independent third party.
  • proxy independent third party

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Le procédé décrit permet à l'opérateur d'un courtier d'application ou mandataire passif d'offrir, de façon simple, à des fournisseurs de services applicatifs enregistrés et à des clients enregistrés une fonction de facturation fiable, précise et de confiance à intervalles définis, le client et le serveur étant en permanence informés du montant à payer pour le service, pendant la prestation de service, en arrière-plan à intervalles réguliers par l'intermédiaire d'un tiers indépendant (mandataire) et la fonction de facturation étant également fournie par ce tiers indépendant.
EP04804651A 2003-12-19 2004-12-02 Procede pour facturer un service dans un reseau de communication Ceased EP1695300A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP04804651A EP1695300A1 (fr) 2003-12-19 2004-12-02 Procede pour facturer un service dans un reseau de communication

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
EP03029455A EP1544815A1 (fr) 2003-12-19 2003-12-19 Procede pour la taxation d un service dans un reseau de communications
EP04804651A EP1695300A1 (fr) 2003-12-19 2004-12-02 Procede pour facturer un service dans un reseau de communication
PCT/EP2004/053226 WO2005062264A1 (fr) 2003-12-19 2004-12-02 Procede pour facturer un service dans un reseau de communication

Publications (1)

Publication Number Publication Date
EP1695300A1 true EP1695300A1 (fr) 2006-08-30

Family

ID=34486275

Family Applications (2)

Application Number Title Priority Date Filing Date
EP03029455A Withdrawn EP1544815A1 (fr) 2003-12-19 2003-12-19 Procede pour la taxation d un service dans un reseau de communications
EP04804651A Ceased EP1695300A1 (fr) 2003-12-19 2004-12-02 Procede pour facturer un service dans un reseau de communication

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP03029455A Withdrawn EP1544815A1 (fr) 2003-12-19 2003-12-19 Procede pour la taxation d un service dans un reseau de communications

Country Status (4)

Country Link
US (1) US20080306747A1 (fr)
EP (2) EP1544815A1 (fr)
CN (1) CN1898706A (fr)
WO (1) WO2005062264A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101562529B (zh) * 2008-04-14 2011-06-01 华为技术有限公司 一种计费处理的方法及装置
CN101860835B (zh) * 2009-04-13 2013-07-31 中国联合网络通信集团有限公司 增值业务付费方法及增值业务付费系统
CN102111742B (zh) * 2011-02-22 2014-04-16 中国联合网络通信集团有限公司 分组域业务计费方法及系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10025565A1 (de) * 2000-03-01 2001-09-06 Siemens Ag Anordnung und Verfahren zur Bestätigung eines Kreditkarten-Zahlungsvorgangs über ein Mobilfunknetz
US6529593B2 (en) * 2000-12-21 2003-03-04 At&T Wireless Services, Inc. Prepaid phone service for both wired and wireless telecommunication devices
US20020165783A1 (en) * 2001-05-02 2002-11-07 Jean-Charles Gonthier Accounting in peer-to-peer data communication networks
EP1349359A1 (fr) * 2002-03-27 2003-10-01 Siemens Aktiengesellschaft Procédé de taxation des services de communications entre des terminaux de communications
EP1361550A1 (fr) * 2002-05-07 2003-11-12 Siemens Aktiengesellschaft Méthode pour la facturation de services fournis par Internet

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2005062264A1 *

Also Published As

Publication number Publication date
US20080306747A1 (en) 2008-12-11
CN1898706A (zh) 2007-01-17
EP1544815A1 (fr) 2005-06-22
WO2005062264A1 (fr) 2005-07-07

Similar Documents

Publication Publication Date Title
DE69933130T2 (de) Abrechnung in einem Kommunikationsnetz
DE60301196T2 (de) System und verfahren zur vergebührung basierend auf der übermittelten verkehrslast in einem paketorientierten telekommunikationsnetzwerk
DE602005006094T2 (de) Verarbeitungsverfahren auf der basis eines charging-trigger-ereignisses und eines neuauthorisationsereignisses eines paketdatenflusses
EP1278383A2 (fr) Méthode, dispositifs et programmes pour transmettre des messages entre élements d'un réseau de télécommunications
DE60314673T2 (de) Mittel und verfahren zur steuerung der dienstprogression zwischen verschiedenen domänen
DE60204680T2 (de) Verfahren zur erzeugung von abrechnungsdaten in einem datennetzwerk und datennetzwerk
WO2002093513A2 (fr) Procede pour tarifer des services proposes dans un reseau informatique
EP1347620A1 (fr) Facturation de l'utilisation des données de contenu mis à la disposition dans l'internet par un terminal mobile
EP1881688A1 (fr) Procédé de sélection d'un compte pour facturer un service offert par un réseau de communication
EP1503538B1 (fr) Procédé pour la détermination de tarif pour une transmission de données
EP1249996A1 (fr) Procédé de facturation de services dans un réseau de communication
EP1503539B1 (fr) Méthode pour le calcul d'un tarif pour la facturation d'une transmission de données
EP1065838A2 (fr) Service à prépaiement pour réseaux de données par paquets mobiles
EP1695300A1 (fr) Procede pour facturer un service dans un reseau de communication
DE602004012872T2 (de) System und verfahren zur implementierung einer vorausbezahlung für datendienste
DE69930537T2 (de) Verfahren und System zur Identifizierung und Angebührung eines mit einem Dienst verknüpften Teilnehmers in einem Kommunikationssystem
EP1488627B1 (fr) Procede pour decompter les taxes telephoniques d'une liaison entre des terminaux de communication
WO2005062265A1 (fr) Procede pour facturer un service dans un reseau de communication
WO2003036527A2 (fr) Procede d'autorisation de paiements dans un reseau de communication
WO2007124974A1 (fr) Procédé et serveur pour gérer la taxation d'abonnés
DE60205080T2 (de) Verfahren zur Planung der Dateifernübertragung für drahtlose Netzwerke
EP1302917A2 (fr) Procédé et dispositif pour des paiements électroniques de produits ou de services, notamment pour une application sur un réseau de données
EP1315131B1 (fr) Méthode permettant la compensation d'argent entre systèmes de payement dans un réseau de communication
EP1522202B1 (fr) Etablissement d'accords de services pour l'utilisation de fonctions internes a des reseaux de telecommunication
EP1246429B1 (fr) Méthode afin de supporter le transfert d'information à travers un système de communication

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20060529

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): DE ES GB

17Q First examination report despatched

Effective date: 20070123

DAX Request for extension of the european patent (deleted)
RBV Designated contracting states (corrected)

Designated state(s): DE ES GB

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA SIEMENS NETWORKS GMBH & CO. KG

RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA SIEMENS NETWORKS S.P.A.

RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA SIEMENS NETWORKS GMBH & CO. KG

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20080428