Revenue management system and method utilizing database backup

• US 8,117,358 B2
• Filed: 07/28/2006
• Issued: 02/14/2012
• Est. Priority Date: 07/28/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Labuda, David S., Krishnamoorthy, Jayaprakash, Haddock, James R., Douglas, Giles, Rockel, Alexander S., Brefczynski, Keith M.
• Primary Examiner(s): Tsai, Henry
• Assistant Examiner(s): SNYDER, STEVEN G
• Application Number:
  US11/496,057
• Publication Number:
  US 20070198283A1
• Time in Patent Office: 2,027 Days
• Field of Search: None
• US Class Current: 710/38
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/12 Accounting
• CPC Class Codes: G06Q 50/60 Business processes related to postal services shipping G06Q10/083; franking apparatus G07B17/00

Abstract

A real-time customer relation management system is disclosed. The system can provide increased availability, reduced internal latencies, and reduced data processing and transfer. The system can provide real time processing and batch processing. The system architecture can have an in-memory write-through cache. The cache can store data that would have otherwise been sent to a database. The system can have a backup in-memory write-through cache. The system can use a warm standby, for example, to enhance data backup efficiency.

Claims

1. A computer-based telecommunications network account management system comprising:

a first memory having a first memory access speed and storing one or more transient objects related to a communication on the telecommunications network, wherein the first memory manages the transient objects per communication and wherein the transient objects are not persisted;

a second memory having a second memory access speed and storing one or more reference objects related to the communication, wherein the second memory persists the reference objects; and

a first memory manager configured to route a first request for a first object to the first memory, and configured to route a second request for a second object not to the first memory,

wherein the first memory has a faster access speed than the second memory, wherein routing the first request for the first object to the first memory and routing the second request for the second object to the second memory are performed based on an object type for each of the first object and the second object and wherein the object types for the first object and the second object are defined in a user defined data dictionary stored in the second memory and wherein the data dictionary stores a user defined object type for the first object and a user defined object type for the second object.

2. The system of claim 1, further comprising a second memory manager configured to route the second object to the second memory.

3. The system of claim 1, wherein the second memory comprises a hard drive.

4. The system of claim 1, wherein the first memory comprises solid state memory.

5. The system of claim 1, wherein the first memory comprises Random Access Memory (RAM).

6. The system of claim 1, wherein the second memory comprises a relational database.

7. The system of claim 1, further comprising a database cluster.

8. The system of claim 1, further comprising a gateway configured to interface with a telecommunications network.

9. The system of claim 1, wherein the first request comprises a query.

10. The system of claim 9, wherein the second request comprises a query.

11. The system of claim 1, wherein the first request comprises a request to write.

12. The system of claim 11, wherein the second request comprises a request to write.

13. The system of claim 1, wherein the object type for the first object comprises a transient object.

14. The system of claim 13, wherein the object type for the second object comprises a reference object.

15. A method for managing a telecommunications network account, the method comprising:

storing in a first memory having a first memory access speed one or more transient objects related to a communication on the telecommunications network, wherein the first memory manages the transient objects per communication and wherein the transient objects are not persisted;

storing in a second memory having a second memory access speed one or more reference objects related to the communication, wherein the second memory persists the reference objects;

routing by a first memory manager a first request for a first object to the first memory; and

routing by the first memory manager a second request for a second object not to the first memory,

wherein the first memory has a faster access speed than the second memory, wherein routing the first request for the first object to the first memory and routing the second request for the second object to the second memory are performed based on an object type for each of the first object and the second object and wherein the object types for the first object and the second object are defined in a user defined data dictionary stored in the second memory and wherein the data dictionary stores a user defined object type for the first object and a user defined object type for the second object.

16. The method of claim 15, further comprising routing by a second memory manager the second object to the second memory.

17. The method of claim 15, wherein the second memory comprises a hard drive.

18. The method of claim 15, wherein the first memory comprises solid state memory.

19. The method of claim 15, wherein the first memory comprises Random Access Memory (RAM).

20. The method of claim 15, wherein the second memory comprises a relational database.

21. The method of claim 15, wherein the first request comprises a query.

22. The method of claim 21, wherein the second request comprises a query.

23. The method of claim 15, wherein the first request comprises a request to write.

24. The method of claim 23, wherein the second request comprises a request to write.

25. The method of claim 15, wherein the object type for the first object comprises a transient object.

26. The method of claim 25, wherein the object type for the second object comprises a reference object.

27. A computer-readable memory having stored thereon a sequence of instruction which, when executed by a processor, cause the processor to manage a telecommunications network account by:

storing in a first memory having a first memory access speed one or more transient objects related to a communication on the telecommunications network, wherein the first memory manages the transient objects per communication and wherein the transient objects are not persisted;

storing in a second memory having a second memory access speed one or more reference objects related to the communication, wherein the second memory persists the reference objects;

routing by a first memory manager a first request for a first object to the first memory; and

routing by the first memory manager a second request for a second object not to the first memory,

wherein the first memory has a faster access speed than the second memory, wherein routing the first request for the first object to the first memory and routing the second request for the second object to the second memory are performed based on an object type for each of the first object and the second object and wherein the object types for the first object and the second object are defined in a user defined data dictionary stored in the second memory and wherein the data dictionary stores a user defined object type for the first object and a user defined object type for the second object.

28. The computer-readable memory of claim 27, further comprising routing by a second memory manager the second object to the second memory.

29. The computer-readable memory of claim 27, wherein the second memory comprises a hard drive.

30. The computer-readable memory of claim 27, wherein the first memory comprises solid state memory.

31. The computer-readable memory of claim 27, wherein the first memory comprises Random Access Memory (RAM).

32. The computer-readable memory of claim 27, wherein the second memory comprises a relational database.