Method for maintaining account consistency

• US 20030046230A1
• Filed: 08/02/2002
• Published: 03/06/2003
• Est. Priority Date: 08/30/2001
• Status: Abandoned Application

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Messinger, Adam, Jacobs, Dean Bernard, Woollen, Rob, White, Seth
• Application Number:
  US10/211,712
• Publication Number:
  US 20030046230A1
• Time in Patent Office: Days
• US Class Current: 705/42
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/108 Remote banking, e.g. home banking
• CPC Class Codes: G06Q 20/389 Keeping log of transactions for guaranteeing non-repudiation of a transaction
• CPC Class Codes: G06Q 20/4037 Remote solvency checks
• CPC Class Codes: G07F 19/201 Accessories of ATMs
• CPC Class Codes: G07F 7/08 by coded identity card or credit card or other personal identification means without personal verification means G07F7/02
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/288 Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

In an account transaction such as an ATM transaction, a server in communication with an ATM stores a copy of the account balance. Before processing the transaction, the server reads the balance from memory and determines whether the account contains sufficient funds for the transaction. In order to prevent overdrawing of the account, the server makes any balance update predicated on the fact that the current balance in the account database is the same as the balance of the local copy of the account. If the account balance stored in the database is not the same, the server rolls back the request and updates the account balance stored in the local copy. This process continues until either the account balance is updated or the transaction is aborted.

Claims

1. A method for maintaining account balance consistency in networked account access systems, comprising:

receiving a request relating to the account balance of a customer, the request being received by an account access system storing a local copy of the account balance;

processing the request using the local copy;

verifying that the local copy reflects the current account balance for the user; and

updating the account balance on the network in response to the request.

2. A method according to claim 1, further comprising:

notifying other account access systems on the network that the account balance has been updated.

3. A method according to claim 1, further comprising:

requesting the account balance if the local copy is not current with the account balance.

4. A method for maintaining account balance consistency in networked account access systems, comprising:

processing an update request on an account access system, the account access system storing a local copy of an account balance to be used in processing the request; and

sending a predicated update request to an account database containing the account balance, whereby the account database updates the account balance if the local copy is current with the account balance before the update, and whereby the account database does not update the account balance if the local copy is not current with the account balance before the update.

5. A method according to claim 4, further comprising:

receiving a message from the account database to the account access system indicating whether the account balance has been updated.

6. A method according to claim 4, further comprising:

reading the account balance from the account database and storing a local copy of the account balance on the account access system.

7. A method according to claim 4, further comprising:

receiving an update request from a client to the account access system, the client specifying the account balance to be updated.

8. A method according to claim 4, further comprising:

checking the local copy to determine whether the update request can be processed.

9. A method according to claim 4, further comprising:

updating the local copy on the account access system if the account balance in the account database is updated.

10. A method according to claim 4, further comprising:

deleting the local copy and storing a new copy of the account balance on the account access system if the local copy is not current with the account balance.

11. A method according to claim 10, further comprising:

sending an additional predicated update request to the account database containing the account balance, whereby the account database updates the account balance if the new copy is current with the account balance before the update, and whereby the account database does not update the account balance if the new copy is not current with the account balance before the update.

12. A method according to claim 10, further comprising:

determining whether the client initiating the update request wishes to attempt the update with the account balance current with the new copy.

13. A method according to claim 4, further comprising:

notifying another account access system on the network that the account balance in the account database has been updated.

14. A method according to claim 4, further comprising:

multicasting an update message to other account access systems on the network.

15. A method according to claim 4, further comprising:

multicasting a version number for the updated account balance to other account access systems on the network.

16. A method according to claim 4, further comprising:

heartbeating the version number for the updated account balance to other account access systems on the network.

17. A method according to claim 4, further comprising:

dropping a local copy of the account balance on any other account access system on the network after the account balance is updated.

18. A method according to claim 4, further comprising:

requesting an updated copy of the account balance on any other account access system on the network.

19. A method according to claim 13, further comprising:

deleting a local copy of the account balance on any other account access system on the network being notified the account balance has been updated.

20. A method according to claim 4, further comprising:

notifying another account access system on the network that the account balance in the database is going to be updated.

21. A method according to claim 20, further comprising:

allowing said another account access system to veto the update of the account balance in the database.

22. A method according to claim 4, further comprising:

sending a packet of information to another account access system on the network, the packet of information containing changes to the account balance due to the update.

23. A method according to claim 22, wherein:

the packet of information contains changes between the state of the account balance after the update and the prior state of the account before the update.

24. A method according to claim 4, further comprising:

determining whether other account access systems on the network can accept the update to the data item; and

committing the update to the other account access systems if the other account access systems can accept the update.

25. A method according to claim 24, further comprising:

rolling back the update if the other account access systems cannot accept the update.

26. A method for quickly verifying the availability of sufficient funds before allowing a withdrawal on a customer account from an automated teller machine, comprising:

receiving a request to withdraw funds from a customer account to an automated teller machine, the automated teller machine storing a local copy of the account balance;

processing the request using the local copy;

verifying that the local copy is current with the account balance for the user in an account database;

updating the account balance in the account database in response to the request if the local copy is current with the account balance; and

disbursing funds to the user in response to the request.

27. A method for providing quick electronic transactions, comprising:

receiving a transaction request from a participant in a transaction to an electronic transaction system, the electronic transaction system storing a local copy of information related to a participant in the transaction;

processing the request with the local copy;

verifying that the local copy reflects the current information for the participant in a main database; and

updating the information for the participant in the main database in response to the request.

28. A method for maintaining concurrency for account information cached on a network, comprising:

receiving an update request to a network server, the network server storing a local copy of a account information in a local cache;

processing the request using the local copy of the account information;

sending a predicated update request to a network database storing an original copy of the account information, whereby the database updates the account information if the local copy is current with the account information, and whereby the database does not update the account information if the local copy is not current with the account information;

receiving a current copy of the account information to the network server and sending another predicated update if the local copy was not the same version as the original copy; and

notifying any other servers on the network storing a local copy of the account information that the original copy has been updated.

29. A system for assuring concurrency among account access systems on a network, comprising:

an account access system adapted to receive a transaction request from a customer and process the request using a local copy of the account information for the customer, the account information being stored in an account database;

wherein the account access system is adapted to send a predicated update request to the account database, whereby the account database updates the account information if the local copy is current with the account information before the update, and whereby the account database does not update the account information if the local copy is not current with the account information before the update.

30. A system according to claim 29, further comprising:

an account database adapted to contain the account information for the customer.

31. A system according to claim 29, further comprising:

a client terminal adapted to allow a customer to initiate the transaction request.

32. A system according to claim 29, wherein:

the account access system is adapted to receiving a message from the account database indicating whether the account information has been updated.

33. A system according to claim 29, wherein:

the account access system is further adapted to check the local copy to determine whether the update request can be processed.

34. A system according to claim 29, wherein:

the account access system is further adapted to update the local copy if the account information in the account database is updated.

35. A system according to claim 29, wherein:

the account access system is further adapted to delete the local copy and store a new copy of the account information if the local copy is not current with the account information.

36. A system according to claim 35, wherein:

the account access system is further adapted to send an additional predicated update request to the account database, whereby the account database updates the account information if the new copy is current with the account information before the update, and whereby the account database does not update the account information if the new copy is not current with the account information before the update.

37. A system according to claim 29, further comprising:

additional account access systems on the network capable of storing a local copy of the data item.

38. A system according to claim 37, wherein:

the account access system is further adapted to notify the additional account access systems that the account information in the account database has been updated.

39. A system according to claim 38, wherein:

the account access system is further adapted to notify the additional account access systems by one of multicasting and point-to-point messaging.

40. A system according to claim 38, wherein:

the account access system is further adapted to include a version number for the account information when notifying the additional account access systems.

41. A system according to claim 40, wherein:

the account access system is further adapted to heartbeat the version number for the account information after the update to the additional account access systems.

42. A system according to claim 37, wherein:

the additional account access systems are each adapted to do at least one of delete a local copy of the account information and request an updated copy of the account information.

43. A system according to claim 37, wherein:

the account access system is further adapted to notify the additional account access systems that the account information in the account database is going to be updated.

44. A system according to claim 37, wherein:

the additional account access systems are each capable of vetoing the update of the account information in the database.

45. A system according to claim 37, wherein:

the account access system is further adapted to send a packet of information to the additional account access systems, the packet of information containing changes to the account information due to the update.

46. A system according to claim 37, wherein:

the account access system is further adapted to determine whether the additional account access systems can accept the update to the account information and commit the update to the additional account access systems if the additional account access systems can accept the update.

47. A system according to claim 37, wherein:

the account access system is further adapted to roll back the update if the additional account access systems cannot accept the update.

48. A system for allowing a transaction over an account access system network, comprising:

an ATM terminal adapted to allow a customer to make a transaction request involving bank account information;

an account access system adapted to store a copy of the bank account information for the customer and process the transaction request; and

a bank account database adapted to store bank account information for the customer and provide access to that bank account information over the network;

wherein the account access system is adapted to send a predicated update request to the bank account database after processing the request, whereby the bank account database is adapted to update the bank account information if the local copy is current with the bank account information before the update, and whereby the bank account database does not update the bank account information if the local copy is not current with the bank account information before the update.