Three tier financial transaction system with cache memory

• US 6,023,684 A
• Filed: 10/01/1997
• Issued: 02/08/2000
• Est. Priority Date: 10/01/1997
• Status: Expired due to Term

• Current Assignee: S1 Incorporated (ACI Worldwide Incorporated)
• Original Assignee: Security First Technologies Incorporated
• Inventors: Pearson, Mark P.
• Primary Examiner(s): Volltz, Emmanuel Todd
• Assistant Examiner(s): Hayes, John W.
• Application Number:
  US08/941,966
• Time in Patent Office: 860 Days
• Field of Search: 705/35, 705/36, 705/42, 707/9, 707/10, 707/102, 707/516, 707/103, 395/280, 395/500, 395/200.3, 395/200.7, 395/200.8, 395/200.33, 395/200.63, 395/836, 709/224, 709/228
• US Class Current: 705/36.00R
• CPC Class Codes: G06Q 20/00 Payment architectures, schemes or protocols apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12
• CPC Class Codes: G06Q 20/108 Remote banking, e.g. home banking
• CPC Class Codes: G06Q 40/06 Asset management; Financial planning or analysis

Abstract

A three tier financial transaction system having a local data memory is disclosed. The three tier system includes a client interface, an application service, a host interface, and a local data memory. The client interface communicates data messages between a client program and the financial transaction system. The client interface converts client requests to a format compatible with the application service so the application service may process client requests from client programs. At the initiation of a logical session with a client program, the application service refreshes data for the customer associated with the client program using data obtained from a back end processing system through the host interface. The data in the local data memory is then used by the application service for processing client requests during the logical session. Response data generated by the application service is provided to the client interface for presentation to the client program. Communication between the client program and the client interface is preferably performed over an open communication network. The local data memory permits the processing of the client service request to be decoupled from the updating of the back end processing system to improve response times for client request processing.

Claims

1. A financial transaction system for supporting communication between a plurality of financial institution customers and at least one financial institution back end processing system comprising:

an application service program for processing client requests from a client program executing on a computer associated with at least one of the customers;

a client interface for communicating messages between said client program and said application service program;

a host interface for coupling said application service program to a back end processing system for a financial institution; and

a local data memory coupled to said application service program, said local data memory for storing customer data refreshed with data received through said host interface, said application service program processes said client messages received through said client interface with said customer data stored in said local data memory.

2. The system of claim 1, said client interface further comprising:

a presentation logic program for communicating with said client program in a client program protocol; and

a personality library for converting application service calls generated by said presentation logic program with data from said client messages to an application service protocol and for converting responsive data received from said application service program to said client program protocol.

3. The system of claim 2 wherein said presentation logic program parses said client messages, authenticates said client program sending said client messages, generates said application service calls with data from said client messages, and generates output for said client program.

4. The system of claim 3 wherein said presentation logic program renders output for a fat client program.

5. The system of claim 3 wherein said presentation logic program renders output for a thin client program.

6. The system of claim 2 wherein said personality library converts application service calls to one of Java, ActiveX, C, or C++.

7. The system of claim 1 further comprising:

a transaction processing (TP) monitor for coupling said client interface to said application service program and for coupling said application service program to said host interface.

8. The system of claim 7, said TP monitor having host configuration data for identifying whether said back end processing system is one of a real time and a near time system.

9. The system of claim 1 wherein said local data memory is one of a relational data base system, a data object repository, a random access memory (RAM) with a memory access controller, and a cluster data base.

10. The system of claim 1 wherein said client interface program is coupled to a plurality of client programs over an open network.

16. The system of claim 1, wherein the customer data is refreshed with data received through said host interface in response to an initiation of a logical session by the client program.

17. The system of claim 16, wherein the application service program, responsive to the initiation of the logical session, is operative to determine the customer data that requires refreshing, obtain the data for refreshing the customer data from the back end processing system via the host interface, and store the data in the local data memory, thereby modifying content stored by the local data memory.

18. The system of claim 1, wherein the client interface generates a client refresh application service call in response to an initiation of a logical session, and the application service program is responsive to the client refresh application service call to examine a user token and configuration information for the customer to determine the customer data requiring updating in the local data memory.

19. The system of claim 18, wherein the application service program obtains data from the back end processing system to update the customer data maintained in the local data memory.

11. A method for providing financial institution customers access to their accounts at a financial institution comprising the steps of:

initiating a logical session between a client program and a client interface;

refreshing data in a local data memory with customer data received from a back end processing system through a host interface;

processing client requests using the refreshed data stored in the local data memory; and

sending system responses generated from processing said client requests to said client program through said client interface.

12. The method of claim 11 further comprising the steps of:

generating back end processing system updates from processing said client requests; and

sending said back end processing system updates to said back end processing system through said host interface.

13. The method of claim 11 wherein said initiating step further comprises the steps of:

authenticating said client program for access to said back end processing system; and

sending secret data decrypted from a message received from said client program to authenticate said client interface to said client program.

14. The method of claim 11 further comprising the steps of:

verifying an external token to authenticate a session interaction during a logical session;

generating a new external token for authenticating a next session interaction during said logical session; and

returning said new external token to said client program through said client interface.

15. The method of claim 14 further comprising the steps of:

generating an internal token during a session interaction; and

passing said internal token to an application service program for authenticating an application service call.

20. The method of claim 11, wherein the step of refreshing data in the local data memory comprises:

generating a client refresh application service call in response to an initiation of a logical session; and

in response to the client refresh application service call, examining a user token and configuration information the customer to determine the data requiring updating in the local data memory.