Charging in a communication system

• US 20060234674A1
• Filed: 04/04/2006
• Published: 10/19/2006
• Est. Priority Date: 12/22/2000
• Status: Active Grant

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Koskinen, Juha-Pekka, Vallinen, Juha, Hopeaharju, Merja
• Granted Patent: US 7,725,097 B2
• Time in Patent Office: Days
• US Class Current: 455/406
• CPC Class Codes: H04M 15/31 Distributed metering or calculation of charges
• CPC Class Codes: H04M 15/41 Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
• CPC Class Codes: H04M 15/49 Connection to several service providers
• CPC Class Codes: H04M 15/55 for hybrid networks
• CPC Class Codes: H04M 15/854 Available credit
• CPC Class Codes: H04M 17/00 Prepayment of wireline communication systems, wireless communication systems or telephone systems using a coded card to authorise calls from a telephone set H04M1/675
• CPC Class Codes: H04M 17/10 Account details or usage
• CPC Class Codes: H04M 17/106 using commercial credit or debit cards
• CPC Class Codes: H04M 2017/14 using commercial credit/debit cards, e.g. VISA, AMEX
• CPC Class Codes: H04M 2215/0164 Billing record, e.g. Call Data Record [CDR], Toll Ticket[TT], Automatic Message Accounting [AMA], Call Line Identifier [CLI], details, i.e. parameters, identifiers, structure
• CPC Class Codes: H04M 2215/2026 Wireless network, e.g. GSM, PCS, TACS
• CPC Class Codes: H04M 2215/204 UMTS; GPRS
• CPC Class Codes: H04M 2215/32 Involving wireless systems
• CPC Class Codes: H04M 2215/44 Charging/billing arrangements for connection made over different networks, e.g. wireless and PSTN, ISDN, etc.
• CPC Class Codes: H04M 2215/46 Connection to several service providers
• CPC Class Codes: H04M 2215/8166 Available credit
• CPC Class Codes: H04M 2215/96 Distributed calculation of charges, e.g. in different nodes like for mobiles between HLR and VLR, or between the terminal and the billing function
• CPC Class Codes: H04W 4/24 Accounting or billing

Abstract

The invention provides, according to one embodiment, a method for charging for services in a communication system which includes a charging entity and at least two connection support entities for providing resources to support a connection in the communication system. The method may include detecting initiation of a connection for provision by the connection support entities, generating a charging identity at a first one of the connection support entities for identifying the connection to the at least two connection support entities, transmitting a first charging message from the first connection support entity to the charging entity, the message specifying a first tariff and including the charging identity, transmitting a second charging message from the second connection support entity to the charging entity, the message specifying a second tariff and including the charging identity, and storing the first tariff and the second tariff.

Claims

1. A method for charging for services in a communication system comprising a charging entity and at least two connection support entities for providing resources to support a connection in the communication system, the method comprising:

detecting initiation of a connection for provision by the connection support entities;

generating a charging identity at a first one of the connection support entities for identifying the connection to the at least two connection support entities;

transmitting a first charging message from the first connection support entity to the charging entity, the message specifying a first tariff and including the charging identity;

transmitting a second charging message from the second connection support entity to the charging entity, the message specifying a second tariff and including the charging identity;

storing the first tariff and the second tariff, and

during the connection the charging entity performing the steps of

determining according to the first stored tariff a first charge for the support of the connection by the first connection support entity;

determining according to the second stored tariff a second charge for the support of the connection by the second connection support entity; and

periodically estimating a charge for the connection according to the first and second charges and comparing the estimate charge with the balance of an account to which the connection is to be charged.

2. A method as claimed in claim 1, wherein at least one of the first and second charges is determined based on the duration of the connection.

3. A method as claimed in claim 1, wherein at least one of the first and second charges is determined based on the amount of data transmitted during the connection.

4. A method as claimed in claim 3, wherein the connection supports the carrying of data in packet form and at least one of the first and second charges is determined based on the number of packets transmitted during the connection.

5. A method as claimed in claim 1, wherein at least one of the first and second charges is of a fixed value.

6. A method as claimed in claim 1, wherein each of the first and second connection support entities has a unique identity.

7. A method as claimed in claim 1, comprising the step of transmitting the charging identity from the connection support entity to the other of the connection support entities.

8. A method as claimed in claim 6, wherein each of the connection support entities maintains a count of the charging identities it has generated, and the charging identity is formed by combining the unique identity of the entity that generates the charging identity and the next number in the count maintained by that entity.

11. A method as claimed in claim 1, comprising dividing the estimate charge into at least two portions and comparing one of those portions to a first account and the second of those portions to another account.

12. A method as claimed in claim 11, wherein the first account is associated with a terminal that initiated the connection.

13. A method as claimed in claim 12, wherein the second user account is associated with another terminal to which the terminal that initiated the connection has been connected by means of the connection.

14. A method as claimed in claim 12, wherein the second user account is unassociated with another terminal to which the terminal that initiated the connection has been connected by means of the connection.

15. A method as claimed in claim 6, comprising the steps of:

transmitting from the first connection support entity to the charging entity the unique identity of the first connection support entity; and

transmitting from the second connection support entity to the charging entity the unique identity of the second connection support entity.

9-10. -10. (canceled)

16-23. -23. (canceled)

24. A connection support entity for providing resources to support a connection in a communication system comprising a charging entity and at least one other connection support entity, the connection support entity being configured to perform the following steps:

detect initiation of a connection;

generate a charging identity for identifying the connection to the at least two connection support entities and the charging entity;

make available the charging identity to the at least one other connection support entity and the charging entity;

determine according to a stored tariff a charge for the support of the connection by the connection support entity; and

transmit a charging message to the charging entity, the message specifying the charge and including the charging identity.

27. A connection support entity as claimed in claim 24, wherein the charge is determined based on the duration of the connection.

28. A connection support entity as claimed in claim 24, wherein the charge is determined based on the amount of data transmitted during the connection.

29. A connection support entity as claimed in claim 28, wherein the connection supports the carrying of data in packet form and the charge is determined based on the number of packets transmitted during the connection.

30. A connection support entity as claimed in claim 24, wherein the charge is of a fixed value.

31. A connection support entity as claim in claim 24, wherein the connection support entity has a unique identity.

32. A connection support entity as claimed in claim 24, the connection support entity being further configured to transmit the charging identity to the other of the connection support entities.

33. A connection support entity as claimed in claim 31, wherein the connection support entity maintains a count of the charging identities it has generated, and the charging identity is formed by combining the unique identity of the connection support entity and the next number in the count.

25. A charging entity for charging for services in a communication system comprising at least two connection support entities for providing resources to support a connection in the communication system, the charging entity being configured to perform the following steps:

receive a charging identity from a first one of the connection support entities for identifying a connection to the charging entity and the at least two connection support entities, the at least two connection support entities providing resources to support that connection;

receive a first charging message from the first connection support entity, the message specifying a first charge and including the charging identity;

receive a second charging message from a second connection support entity, the message specifying a second charge and including the charging identity;

add the first and second charging messages to a transaction to form a total value for the transaction; and

debit the total value of the transaction from an account indicated in the first or second charging message.

34. A charging entity as claimed in claim 25, wherein the charging entity receives from the first connection support entity the unique identity of the first connection support entity and from the second connection support entity the unique identity of the second support entity.

26. (canceled)