Revenue management systems and methods with re-rating and rebilling

• US 8,422,651 B2
• Filed: 06/08/2007
• Issued: 04/16/2013
• Est. Priority Date: 04/30/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Krishnamoorthy, Jayaprakash, Labuda, David S., Haddock, James R., Subramanian, Mahadevan
• Primary Examiner(s): TRAN, QUOC DUC
• Application Number:
  US11/760,472
• Publication Number:
  US 20080040267A1
• Time in Patent Office: 2,139 Days
• Field of Search: 379/114.01, 379/114.03, 379/126, 379/133, 455405-408, 705/52, 705/1, 705/34
• US Class Current: 379/114.03
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

A revenue management system for telecommunication systems is disclosed. The revenue management system can have multiple integrated modules. The modules can include a revenue generation module, a revenue capture module, a revenue collection module, a revenue intelligence module, and others. The revenue management system can also be configured to simultaneously manage revenue for prepaid, postpaid, now-paid payment models.

Claims

1. A method of rating services in a revenue management system of telecommunications network, the method comprising:

detecting by a revenue capture layer of the revenue management system a backdated operation related to a user in a current billing cycle, the operation being backdated to a date and wherein the backdated operation comprises a change to a service plan of the user; and

re-rating by the revenue capture layer of the revenue management system service events for the user occurring after the date based on the backdated operation and the change to the service plan for the user, wherein the service events comprise a sequence of a plurality of real-time events and wherein re-rating the service events is performed based on the sequence of the real-time events.

2. The method of claim 1, wherein the backdated operation comprises a service plan purchase.

3. The method of claim 1, wherein the backdated operation comprises a service plan cancellation.

4. The method of claim 1, wherein the backdated operation comprises a service plan transition.

5. The method of claim 1, wherein re-rating service events comprises:

creating a queue of one or more re-rating jobs;

adding a re-rating job related to the backdated operation to the queue; and

running the re-rating job from the queue.

6. The method of claim 5, wherein running the re-rating job from the queue is performed during an off-peak period.

7. The method of claim 1, wherein re-rating comprises determining whether an event is a billed event or an unbilled event.

8. The method of claim 7, further comprising, in response to determining the event is a billed event, posting an adjustment in the current billing period.

9. The method of claim 7, further comprising, in response to determining the event is an unbilled event, creating one or more shadow events to account for the re-rating.

10. The method of claim 1, wherein the date is in a previous billing cycle.

11. The method of claim 1, wherein the date is in the current billing cycle.

12. A system for rating services in a revenue management system of telecommunications network, the system comprising:

a revenue capture layer communicatively coupled with the telecommunication network supporting the services and adapted to detect a backdated operation related to a user in a current billing cycle, the operation being backdated to a date and wherein the backdated operation comprises a change to a service plan of the user, and re-rate service events for the user occurring after the date based on the backdated operation and the change to the service plan, wherein the service events comprise a sequence of a plurality of real-time events and wherein re-rating the service events is performed based on the sequence of the real-time events.

13. The system of claim 12, wherein the backdated operation comprises a service plan purchase.

14. The system of claim 12, wherein the backdated operation comprises a service plan cancellation.

15. The system of claim 12, wherein the backdated operation comprises a service plan transition.

16. The system of claim 12, wherein re-rating service events comprises:

creating a queue of one or more re-rating jobs;

adding a re-rating job related to the backdated operation to the queue; and

running the re-rating job from the queue.

17. The system of claim 16, wherein running the re-rating job from the queue is performed during an off-peak period.

18. The system of claim 12, wherein re-rating comprises determining whether an event is a billed event or an unbilled event.

19. The system of claim 18, wherein re-rating further comprises, in response to determining the event is a billed event, posting an adjustment in the current billing period.

20. The system of claim 18, wherein re-rating further comprises, in response to determining the event is an unbilled event, creating one or more shadow events to account for the re-rating.

21. The system of claim 12, wherein the date is in a previous billing cycle.

22. The system of claim 12, wherein the date is in the current billing cycle.