Flexible rating rules and calender rules implemented in a real-time charging system for a telecommunications network

• US 8,195,783 B2
• Filed: 05/25/2007
• Issued: 06/05/2012
• Est. Priority Date: 05/26/2006
• Status: Active Grant

• Current Assignee: Intellectual Ventures II LLC (Intellectual Ventures LLC)
• Original Assignee: Intellectual Ventures II LLC (Intellectual Ventures LLC)
• Inventors: Crimi, Joseph, Hopson, Alan, Hsu, Jeff, Johnson, Robert, Mir, Amanullah, Nettar, Dinesh, Silverstein, Glenn, Gupla, Arvind, Stilborn, Richard, McMahon, Cathryn S.
• Primary Examiner(s): RUDY, ANDREW J
• Application Number:
  US11/807,002
• Publication Number:
  US 20080014904A1
• Time in Patent Office: 1,838 Days
• Field of Search: 370/114.01, 370/255, 455406-408, 455/414.1, 705/30, 705/34, 379/114.01, 379/114.03, 379/114.09, 379/114.12, 379/114.28, 709/203, 709/219, 709/223
• US Class Current: 709/223
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• 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/22 according to time of day
• CPC Class Codes: H04M 15/43 Billing software details
• CPC Class Codes: H04M 15/59 based on real time
• CPC Class Codes: H04M 15/7652 shared by users
• CPC Class Codes: H04M 15/80 Rating or billing plans; Tariff determination aspects
• 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/7245 Shared by users, e.g. group accounts or one account for different users
• CPC Class Codes: H04M 2215/74 Rating aspects, e.g. rating parameters or tariff determination apects

Abstract

By coupling a rating engine with call processing, rating rules are generated that enable a flexible interface between call process and call rating without necessitating that fixed data be passed between them. The real time charging system (RCS) provides a process that creates a generic entity, called a bucket, and uses it to keep track of account information and/or to count types of usage. The bucket allows an operator to define accounts and usage counters and how they are used as part of the rating rules. Use of these buckets is defined in rating rules, thus turning control over subscriber account and usage counters to the network operator. Further, the RCS provides a calendar option for limiting times during which calls to general telephone numbers can be made or received.

Claims

1. A method, comprising:

receiving a service request for a requested service at a computer, the computer configured to access a plurality of rating rules;

determining a charge for the requested service at the computer based on at least one rating rule of the plurality of rating rules and a tag, wherein the tag is based on at least one of information in the service request, network provided data, configuration data, and subscriber data; and

generating, at the computer, one or more balance buckets for tracking a balance of the requested service and one or more usage buckets for tracking a usage of the requested service based on the at least one rating rule of the plurality of rating rules.

2. The method of claim 1, further comprising:

generating a call detail record at the computer regarding the requested service.

3. The method of claim 1, further comprising:

indicating that the service request is allowable at the computer based on a time of the service request and a calendar set of restrictions.

4. The method of claim 1, further comprising:

creating one or more shared balance buckets and one or more shared usage buckets at the computer, each shared balance bucket and each shared usage bucket for a group of subscribers, wherein each balance bucket and each usage bucket for each subscriber in the group of subscribers is at a lower level of a hierarchy than the shared balance buckets and the shared usage buckets for the group of subscribers.

5. The method of claim 1, wherein one or more of the balance buckets have an associated expiration date after which any remaining balance cannot be used.

6. The method of claim 1, wherein each usage bucket has a reset date after which date the usage bucket will be reset to zero.

7. A system, comprising:

a computer, comprising;

memory that contains a plurality of rating rules; and

software that causes the computer to perform operations comprising;

receiving a service request for a requested service;

determining a charge for the requested service based on at least one rating rule of the plurality of rating rules and a tag, wherein the tag is based on at least one of information in the service request, network provided data, configuration data, and subscriber data; and

causing a rating engine to generate one or more balance buckets for tracking a balance of the requested service and one or more usage buckets for tracking a usage of the requested service based on the one of the one or more rating rules.

8. The system of claim 7, wherein the operations further comprise:

generating a call detail record regarding the requested service.

9. The system of claim 7, wherein the operations further comprise:

indicating that the service request is allowable based on a time of the service request and a calendar set of restrictions.

10. The system of claim 7, wherein the operations further comprise:

creating one or more shared balance buckets and one or more shared usage buckets, each shared balance bucket and each shared usage bucket for a group of subscribers, wherein each balance bucket and each usage bucket for each subscriber in the group of subscribers is at a lower level of a hierarchy than the shared balance buckets and the shared usage buckets for the group of subscribers.

11. The system of claim 7, wherein one or more of the balance buckets have an associated expiration date after which any remaining balance cannot be used.

12. The system of claim 7, wherein each usage bucket has a reset date after which date the usage bucket will be reset to zero.

13. A system, comprising:

means for receiving a service request for a requested service;

means for accessing a plurality of rating rules;

means for determining a charge for the requested service based on at least one rating rule of the plurality of rating rules and a tag, wherein the tag is based on at least one of information in the service request, network provided data, configuration data, and subscriber data; and

means for generating one or more balance buckets for tracking a balance of the requested service and one or more usage buckets for tracking a usage of the requested service based on the at least one rating rule of the plurality of rating rules.

14. The system of claim 13, further comprising:

means for generating a call detail record regarding the requested service.

15. The system of claim 13, further comprising:

means for indicating that the service request is allowable based on a time of the service request and a calendar set of restrictions.

16. The system of claim 13, further comprising:

means for creating one or more shared balance buckets and one or more shared usage buckets, each shared balance bucket and each shared usage bucket for a group of subscribers, wherein each balance bucket and each usage bucket for each subscriber in the group of subscribers is at a lower level of a hierarchy than the shared balance buckets and the shared usage buckets for the group of subscribers.

17. A non-transitory computer-readable medium having instructions stored thereon, the instructions comprising:

instructions to receive a service request for a requested service at a computer, the computer configured to access a plurality of rating rules;

instructions to determine a charge for the requested service based on at least one rating rule of the plurality of rating rules and a tag, wherein the tag is based on at least one of information in the service request, network provided data, configuration data, and subscriber data; and

instructions to generate one or more balance buckets for tracking a balance of the requested service and one or more usage buckets for tracking a usage of the requested service based on the at least one rating rule of the plurality of rating rules.

18. The non-transitory computer-readable medium of claim 17, further comprising instructions to generate a call detail record at the computer regarding the requested service.

19. The non-transitory computer-readable medium of claim 17, further comprising instructions to indicate that the service request is allowable based on a time of the service request and a calendar set of restrictions.

20. The non-transitory computer-readable medium of claim 17, further comprising instructions to create one or more shared balance buckets and one or more shared usage buckets, each shared balance bucket and each shared usage bucket for a group of subscribers, wherein each balance bucket and each usage bucket for each subscriber in the group of subscribers is at a lower level of a hierarchy than the shared balance buckets and the shared usage buckets for the group of subscribers.

21. The non-transitory computer-readable medium of claim 17, wherein one or more of the balance buckets have an associated expiration date after which any remaining balance cannot be used.

22. The non-transitory computer-readable medium of claim 17, wherein each usage bucket has a reset date after which date the usage bucket will be reset to zero.