Server software adapted to convert messages to enable ATM and ATM host communication

• US 7,844,512 B2
• Filed: 04/04/2005
• Issued: 11/30/2010
• Est. Priority Date: 11/27/1996
• Status: Expired due to Fees

• Current Assignee: Diebold Nixdorf, Incorporated
• Original Assignee: Diebold Incorporated (Diebold Nixdorf, Incorporated)
• Inventors: Richards, Bruce G., Ess, Joseph C., Drummond, Jay Paul, Blackson, Dale, Smith, Mark D., Weis, David W., Cichon, Bob A., Moales, Mark A., Church, James
• Primary Examiner(s): Oyebisi; Ojo O
• Application Number:
  US11/099,369
• Publication Number:
  US 20050182723A1
• Time in Patent Office: 2,066 Days
• Field of Search: 235/379, 705/35, 705/37, 705/34, 705/43
• US Class Current: 705/34
• CPC Class Codes: G06F 16/95 Retrieval from the web
• CPC Class Codes: G06F 3/023 Arrangements for converting discrete items of information into a coded form, e.g. arrangements for interpreting keyboard generated codes as alphanumeric codes, operand codes or instruction codes
• CPC Class Codes: G06F 3/04895 Guidance during keyboard input operation, e.g. prompting
• 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/042 characterized in that the payment protocol involves at least one cheque
• CPC Class Codes: G06Q 20/1085 involving automatic teller machines [ATMs]
• CPC Class Codes: G06Q 20/18 involving self-service terminals [SST], vending machines, kiosks or multimedia terminals
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G07F 19/20 Automatic teller machines [ATMs]
• CPC Class Codes: G07F 19/201 Accessories of ATMs
• CPC Class Codes: G07F 19/206 Software aspects at ATMs
• CPC Class Codes: G07F 19/211 Software architecture within ATMs or in relation to the ATM network
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/5651 Reducing the amount or size of exchanged application data
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 : Network security protocols

Abstract

A server is in communication with an ATM host and at least one ATM. Sever software is adapted to operate in the server to cause messages to be converted to enable ATM and ATM host communication. The server is operative to receive messages from the ATM host and/or the ATM, cause the received messages to be converted for handling by the other one of the ATM host and the ATM, and then cause the converted messages to be sent to the other one of the ATM host and the ATM. In one embodiment, the server software is operative to cause HTTP messages to be converted to non-HTTP messages, and vice versa.

Claims

1. At least one article including computer executable instructions operative to cause at least one server

in operative communication with both

an ATM transaction host and

at least one automated teller machine (ATM)

including an ATM that comprises

at least one ATM computer including at least one browser,

 

wherein the at least one ATM computer is in operative connection with both

 

a customer input device including a card reader and

 

a currency dispenser,

to carry out a method comprising both (a) and (b),

wherein (a) comprises;

(a1) receiving through operation of the at least one server, at least one first HTTP message that pertains to at least one ATM transaction at the ATM, wherein the at least one first HTTP message is sent responsive at least in part to operation of the at least one browser and corresponds to an ATM request,

(a2) converting through operation of the at least one server, at least a portion of the at least one first HTTP message received in (a1) to at least one first non-HTTP message that pertains to the at least one ATM transaction, wherein the at least one first non-HTTP message corresponds to the ATM request, and

(a3) sending through operation of the at least one server, the at least one first non-HTTP message to the ATM transaction host; and

wherein (b) comprises;

(b1) receiving from the ATM transaction host through operation of the at least one server, at least one second non-HTTP message that pertains to the at least one ATM transaction at the ATM, wherein the at least one second non-HTTP message corresponds to a response to the ATM request, wherein the response to the ATM request includes an indication of whether the at least one ATM transaction at the ATM is authorized or denied,

(b2) converting through operation of the at least one server at least a portion of the at least one second non-HTTP message received in (b1) to at least one second HTTP message that pertains to the at least one ATM transaction, wherein the at least one second HTTP message corresponds to the response to the ATM request, and

(b3) sending through operation of the at least one server the at least one second HTTP message to the at least one browser.

2. The at least one article according to claim 1 wherein the computer executable instructions are operative to cause the at least one server to perform (a) prior to (b).

3. The at least one article according to claim 1 wherein (a1) includes receiving by remote method invocation a shared transaction data object including functions and ATM transaction data, and wherein (b3) includes sending by remote method invocation the shared transaction data object including modified ATM transaction data, wherein the modified ATM transaction data differs from the ATM transaction data of (a1).

4. The at least one article according to claim 1 wherein in (b1) the at least one second non-HTTP message includes data, wherein in (b2) the at least one second HTTP message comprises at least one HTTP transferable file including transaction data therein, wherein at least a portion of the transaction data corresponds to the data in the at least one second non-HTTP message received in (b1).

5. The at least one article according to claim 4 wherein the at least one second HTTP message sent in (b3) is operative to cause the ATM to operate at least one transaction function device thereof responsive to the transaction data in the at least one HTTP transferable file.

6. The at least one article according to claim 4 wherein the at least one HTTP transferable file of (b2) includes the transaction data in a shared data object, wherein the shared data object is located in software, and wherein the shared data object includes functions.

7. The at least one article according to claim 6 wherein (a1) includes receiving from the ATM at least one first HTTP message including the shared data object with modified transaction data, wherein the modified transaction data differs from the transaction data of (b2).

8. The at least one article according to claim 1 wherein (a2) includes converting at least one HTTP message to a Diebold 91X formatted message, and wherein (b2) includes converting a Diebold 91X formatted message to at least one HTTP message.

9. The at least one article according to claim 1 wherein in (a) the at least one first non-HTTP message and the at least one first HTTP message both correspond to a request to dispense currency from the currency dispenser.

10. The at least one article according to claim 1 wherein in (b) the response to the ATM request includes authorization to carry out the at least one ATM transaction.

11. The at least one article according to claim 10 wherein the at least one second HTTP message sent in (b3) is operative to cause operation of at least one transaction function device of the ATM in carrying out the at least one ATM transaction.

12. The at least one article according to claim 1 wherein the at least one server resides in the ATM, and wherein in (b) the at least one second HTTP message and the at least one second non-HTTP message both include data corresponding to authorization to dispense currency through operation of the currency dispenser.

13. The at least one article according to claim 1 wherein (a2) includes communicating with at least one database including HTTP-to-non-HTTP conversion data, and wherein (b2) includes communicating with at least one database including non-HTTP-to-HTTP conversion data.

14. At least one article including computer executable instructions operative to cause at least one server

in operative connection with both

an ATM transaction host and

at least one automated teller machine (ATM)

including an ATM that comprises

at least one ATM computer including at least one browser,

 

wherein the at least one ATM computer is in operative connection with both

 

a customer input device including a card reader and

 

a currency dispenser,

to carry out a method comprising both (a) and (b),

wherein (a) comprises;

(a1) receiving through operation of the at least one server, a shared transaction data object, wherein the shared transaction data object includes software and is sent responsive at least in part to operation of the at least one browser, wherein the shared transaction data object includes functions and ATM transaction data, and wherein the ATM transaction data pertains to a currency dispense transaction associated with the currency dispenser;

(a2) modifying the ATM transaction data received in (a1);

(a3) generating through operation of the at least one server, a transaction message responsive to receiving the shared transaction data object in (a1); and

(a4) sending through operation of the at least one server, the transaction message generated in (a3) to the ATM transaction host;

wherein (b) comprises;

(b1) receiving from the ATM transaction host through operation of the at least one server, a transaction message; and

(b2) sending through operation of the at least one server, a shared transaction data object to the at least one browser responsive to receiving the transaction message in (b1), wherein the shared transaction data object includes software, wherein the shared transaction data object includes functions and ATM transaction data, wherein the ATM transaction data pertains to the currency dispense transaction associated with the currency dispenser, and wherein the ATM transaction data includes the modified ATM transaction data.

15. The at least one article according to claim 14 wherein the computer executable instructions are operative to enable the at least one server to communicate with at least one database including conversion data to convert HTTP ATM transaction messages to non-HTTP ATM transaction messages and convert non-HTTP ATM transaction messages to HTTP ATM transaction messages.

16. The at least one article according to claim 14 wherein (a1) includes receiving the shared transaction data object by remote method invocation, and wherein (b2) includes sending the shared transaction data object by remote method invocation.

17. At least one article including computer executable instructions operative to cause at least one computer in operative connection with an automated teller machine (ATM) that includes at least one ATM computer in operative connection with both a customer input device including a card reader and a cash dispenser, and that operates responsive to data bearing records, to carry out a method comprising:

a) receiving with the at least one computer, at least one first message from one of an ATM transaction host or the ATM, wherein the at least one first message comprises;

(a1) an HTTP message pertaining to a cash dispensing transaction at the ATM, or

(a2) a non-HTTP message pertaining to a cash dispensing transaction at the ATM;

b) producing through operation of the at least one computer, at least one second message, wherein the at least one second message comprises;

(b1) when the at least one first message received in (a) comprises the HTTP message of (a1), a non-HTTP message corresponding to the at least one first message, or

(b2) when the at least one first message received in (a) comprises the non-HTTP message of (a2), an HTTP message corresponding to the at least one first message; and

c) sending the at least one second message from the at least one computer to one of the ATM transaction host or the ATM, wherein the at least one second message is sent to the ATM transaction host when the at least one first message was received from the ATM in (a), and wherein the at least one second message is sent to the ATM when the at least one first message was received from the ATM transaction host in (a).

18. The at least one article according to claim 17,

wherein in (a) the at least one first message comprises the non-HTTP message of (a2) received from the ATM transaction host,

wherein in (b) the at least one second message comprises the HTTP message of (b2), and

wherein in (c) the HTTP message of (b2) is sent to the ATM.

19. The at least one article according to claim 17,

wherein in (a) the at least one first message comprises the HTTP message of (a1) received from the ATM,

wherein in (b) the at least one second message comprises the non-HTTP message of (b1), and

wherein in (c) the non-HTTP message of (b1) is sent to the ATM transaction host.