Method and system for real-time tiered rating of communication services

• US 20040009761A1
• Filed: 04/10/2002
• Published: 01/15/2004
• Est. Priority Date: 04/10/2002
• Status: Active Grant

• Current Assignee: Sprint Spectrum LP (Deutsche Telekom AG)
• Original Assignee: Sprint Spectrum LP (Deutsche Telekom AG)
• Inventors: McConnell, Von, Money, Jesse
• Granted Patent: US 7,062,253 B2
• Time in Patent Office: Days
• US Class Current: 455/406
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1417 Advice of charge with threshold, e.g. user indicating maximum cost
• CPC Class Codes: H04L 12/1485 Tariff-related aspects
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/07 Split billing, i.e. both A-party and B-party charged for the communication
• CPC Class Codes: H04M 15/08 Metering calls to called party , i.e. B-party charged for the communication
• CPC Class Codes: H04M 15/10 Metering calls from calling party , i.e. A-party charged for the communication
• CPC Class Codes: H04M 15/16 according to connection obtained
• CPC Class Codes: H04M 15/42 Dynamic individual rates per user
• CPC Class Codes: H04M 15/56 for VoIP communications
• CPC Class Codes: H04M 15/59 based on real time
• CPC Class Codes: H04M 15/80 Rating or billing plans; Tariff determination aspects
• CPC Class Codes: H04M 15/8005 Flat-fee
• CPC Class Codes: H04M 15/8083 involving reduced rates or discounts, e.g. time-of-day reductions or volume discounts
• CPC Class Codes: H04M 15/81 Dynamic pricing, e.g. change of tariff during call
• CPC Class Codes: H04M 15/8228 Session based
• CPC Class Codes: H04M 15/88 Provision for limiting connection, or expenditure
• CPC Class Codes: H04M 2215/0112 Dynamic pricing, e.g. change of tariff during call
• CPC Class Codes: H04M 2215/0116 Provision for limiting expenditure, e.g. limit on call expenses or account
• CPC Class Codes: H04M 2215/0152 General billing plans, rate plans, e.g. charge rates, numbering plans, rate centers, customer accounts
• CPC Class Codes: H04M 2215/0168 : On line or real-time flexible customization or negotiation according to wishes of subscriber
• CPC Class Codes: H04M 2215/0184 : involving reduced rates or discounts, e.g. time-of-day reductions, volume discounts, cell discounts, group billing, frequent calling destination(s) or user history list
• CPC Class Codes: H04M 2215/202 : VoIP; Packet switched telephony
• CPC Class Codes: H04M 2215/2026 : Wireless network, e.g. GSM, PCS, TACS
• CPC Class Codes: H04M 2215/32 : Involving wireless systems
• CPC Class Codes: H04M 2215/62 : Called party billing, e.g. reverse billing, freephone, collect call, 0800 or 0900
• CPC Class Codes: H04M 2215/64 : Split billing, sharing the cost of calls, e.g. between calling and called parties
• CPC Class Codes: H04M 2215/7833 : Session based
• CPC Class Codes: H04W 4/24 : Accounting or billing

Abstract

A service agent can receive a request to establish a communication session between a communicative entity and another communicative entity. The service agent can access profile information for the communicative entity. Using the profile information the service agent can detect a transition from a first billing mode to a second billing mode, and it can prompt the communicative entity for an authorization to transfer from the first billing mode to the second billing mode.

Claims

1. A method for managing real-time billing modes in a communication network, the method comprising:

receiving a signaling message indicative of a communication session involving a communicative entity;

detecting a transfer from a first billing mode for the communicative entity to a second billing mode for communicative entity; and

responsively sending a message to the communicative entity requesting an approval of the transfer.

2. The method of claim 1, wherein receiving a signaling message includes:

receiving from the communicative entity a SIP INVITE message requesting initiation of the communication session with another communicative entity.

3. The method of claim 1, wherein receiving a signaling message includes:

receiving from another communicative entity a SIP INVITE message requesting initiation of the communication session with the communicative entity.

4. The method of claim 1 wherein receiving a signaling message includes:

receiving a Hypertext Transfer Protocol message requesting initiation of the communication session.

5. The method of claim 1, wherein the communication session is an instant messaging session between the communicative entity and an instant messaging server.

6. The method of claim 1, wherein the communication session is a Push to Talk session between the communicative entity and a Push to Talk server.

7. The method of claim 1, wherein a profile store (i) defines the first billing mode for the communicating entity as a first billing rate for use of up to a threshold number of communication units, (ii) defines the second billing mode for the communicating entity as a second billing rate for use of more than the threshold number of communication units, and (iii) indicates a number of communication units used so far by the communicating entity, and wherein detecting the transfer from the first billing mode to the second billing mode comprises:

referring to the profile store to determine the threshold and the number of communication units used so far by the communicating entity; and

determining that the number of communication units used so far by the communicating entity exceeds the threshold.

8. The method of claim 1, wherein the profile information is stored in a RADIUS accounting server and wherein detecting a transfer from a first billing mode to a second billing mode includes:

accessing a RADIUS accounting server, wherein the RADIUS accounting server stores profile information keyed to communicative entities; and

receiving a response from the RADIUS accounting server.

9. The method of claim 8, wherein the RADIUS accounting server stores profile information keyed to communicative entity users.

10. The method of claim 1, wherein the profile information is stored in an Authentication, Authorization and Accounting server and wherein detecting a transfer from a first billing mode to a second billing mode includes:

accessing an Authentication, Authorization and Accounting server, wherein the Authentication, Authorization and Accounting server stores profile information keyed to communicative entities.

11. The method of claim 1, further comprising:

transferring form the first billing mode to the second billing mode; and

recording a usage for the communication session.

12. The method of claim 11, wherein recording a usage for the communication session includes:

generating a usage detail record for the communication session, wherein the usage detail record indicates a type of the communication session, and wherein the usage detail record indicates a duration of the communication session.

13. The method of claim 1, wherein responsively sending a message to the communicative entity requesting an approval to transfer:

sending the communicative entity a web page, wherein the web page includes an input mechanism, and wherein the input mechanism can be used to authorize the transfer from the first billing mode to the second billing mode.

14. The method of claim 1, further comprising:

receiving from the communicative entity an authorization to transfer from the first billing mode to the second billing mode; and

transferring from the first billing mode to the second billing mode.

15. The method of claim 1, wherein the communicative entity is a mobile station.

16. The method of claim 1, wherein the communicative entity is a SIP user.

17. A method for transferring billing modes in a communication system, the method comprising:

receiving a request to establish a session between a communicative entity and another communicative entity;

determining a number of communication units used so far by the communicative entity;

detecting, based at least in part on the number of communication units used so far by the communicative entity, a transfer from a first billing mode for the communicative entity to a second billing mode for the communicative entity; and

requesting from the communicative entity an authorization for the transfer from the first billing mode to the second billing mode.

18. The method of claim 17, further comprising:

receiving from the mobile station the authorization to transfer from the first billing mode to the second billing mode;

recording the authorization in the profile database; and

establishing the session.

19. The method of claim 17, wherein a profile store (i) defines the first billing mode for the communicating entity as a first billing rate for use of up to a threshold number of communication units, (ii) defines the second billing mode for the communicating entity as a second billing rate for use of more than the threshold number of communication units, and (iii) indicates a number of communication units used so far by the communicating entity, and wherein determining a number of communication units used so far by the communicative entity:

referring to the profile store to determine the threshold and the number of communication units used so far by the communicating entity; and

determining that the number of communication units used so far by the communicating entity exceeds the threshold.

20. The method of claim 17, wherein the number of communication units is a predetermined number of communication sessions.

21. The method of claim 17, wherein the number of communication units is a predetermined number of instant messaging sessions.

22. The method of claim 17, wherein the number of communication units is a predetermined number of Push to Talk sessions.

23. The method of claim 17, wherein the number of communication units is a predetermined number of airtime minutes.

24. The method of claim 17, wherein detecting a transfer from a first billing mode for the communicative entity to a second billing mode for the communicative entity further comprises:

accessing an Authentication, Authorization and Accounting server, wherein the Authentication, Authorization and Accounting server stores profile information keyed to communicative entities.

25. The method of claim 17, wherein detecting a transfer from a first billing mode for the communicative entity to a second billing mode for the communicative entity further comprises:

accessing a RADIUS accounting server, wherein the RADIUS accounting server stores profile information keyed to communicative entities.

26. The method of claim 17, wherein the communicative entity is a cellular telephone.

27. The method of claim 17, wherein the communicative entity is a subscriber.

28. A method for detecting real-time billing mode changes in a communication system comprising:

accessing profile information, wherein the profile information defines a first billing mode and a second billing mode for a mobile station, wherein the profile information defines a communication unit, wherein the first billing mode corresponds to a predetermined number of communication units, and wherein the second billing mode corresponds to communication units in excess of the predetermined number of communication units;

determining a current usage of the communicative entity, wherein the current usage is measured in communications units, and wherein the communicative entity is currently in a communication session with another communicative entity

detecting a transfer from the first billing mode to the second billing mode when the current usage exceeds the predetermined number of communication units;

suspending the communication session between the communicative entity and the other communicative entity; and

requesting an authorization from the communicative entity to transfer from the first billing mode to the second billing mode.

29. The method of claim 28, further comprising:

receiving from the communicative entity the authorization to transfer from the first billing mode to the second billing mode; and

resuming the communication session between the communicative entity and the other communicative entity.

30. The method of claim 28, further comprising:

receiving from the communicative entity a disapproval to transfer from the first billing mode to the second billing mode; and

terminating the communication session between the communicative entity and the other communicative entity.

31. The method of claim 28, wherein the communication unit is a predetermined number of airtime minutes.

32. The method of claim 28, wherein the communication unit is a predetermined number of communication sessions.

33. A service agent, comprising

a processor;

data storage;

communicative entity interface logic stored in the data storage and executable by the processor (i) to receive a first request from a communicative entity, and (ii) to send the first request to another communicative entity; and

processing logic stored in the data storage and executable by the processor (i) to access communicative entity profile information stored in a plurality of databases, (ii) to determine a current billing mode for the communicative entity, (iii) to detect a transfer from the current billing mode to an updated billing mode, (iv) to request an authorization from the communicative entity to transfer from the current billing mode to the updated billing mode, and (v) to record the authorization from the communicative entity in one of the plurality of databases.

34. The service agent of claim 33, further comprising:

destination device interface logic stored in the data storage and executable by the processor (i) to receive a second request from the other communicative entity, and (ii) to send the second request to the communicative entity.

35. The service agent for claim 33, further comprising:

database interface logic stored in the data storage and executable by the processor (i) to receive a plurality of requests to access the communicative entity profile information, (ii) to formulate the plurality of requests into at least one search, (iii) to access the plurality of databases using the at least one search, and (iv) to partition data retrieved from the plurality of databases based on the plurality of requests.