Telephone/Transaction Entry Device and System for Entering Transaction Data into Databases

Abstract

A data transaction processing system in which transaction data is entered by the user in response to prompts in a template which is tailored to each user application. The template and entered data are accumulated into data transactions which are immediately transmitted upon completion to an external database server for processing and storage. The data transactions are not locally stored for processing, and no conventional operating system is necessary. No local processing needs to be provided, and the only local storage is a flash PROM which stored the control firmware, a flash memory which stores the data streams making up the forms and menus, and a small RAM which operates as an input/output transaction buffer for storing the data streams of the template and the user replies to. the prompts during assembly of a data transaction. The data transaction is received via standard protocols at a database server which, depending upon the application, stores the entire data transaction, explodes the data transaction to produce ancillary records which are then stored, and/or forwards the data transaction or some or all of the ancillary records to other database servers for updating other databases associated with those database servers. Also, in response to requests from the transaction entry device, the database server may return data streams for use in completing the fields in the data transaction or in presenting a menu on the display which was read in from the database server or a remote phone mail system. The transaction entry device is integrated with a telephone and is accessed via a touch screen, an optional keyboard, a magnetic card reader, voice entry, a modem, and the like.

1 . A method, comprising: 
 initiating a data transaction;    creating a record of the transaction;    establishing an identification associated with the record;    after said establishing, allowing entry of said identification of the record;    responsive to said identification, reading the record, and enabling editing of the record; and    after editing the record, allowing the edited record to be sent to at least one specified server.    
     
     
         2 . A method as in  claim 1 , further comprising allowing the record identification to be deleted.  
     
     
         3 . A method as in  claim 1 , wherein said transaction is exploding  
     
     
         4 . A method, comprising: 
 receiving information indicative of a form from a remote server;    receiving a list of possible values that can complete at least one value within the form;    allowing a user to select from said list of said possible values; and    sending the information from the form to plural specified servers.    
     
     
         5 . A method as in  claim 4 , wherein each of plural fields in the form is associated with a different server, and said sending uses an association from a field to determine a destination for information in the field.  
     
     
         6 . A method as in  claim 4 , wherein said values are text values.  
     
     
         7 . A method as in  claim 4 , wherein said values are sound values entered by voice.  
     
     
         8 . A method as in  claim 4 , wherein said values are menu values that are selected using scrolling keys.  
     
     
         9 . A method, comprising: 
 receiving information indicative of a form that has parts that require data entry, from a remote server;    accepting transaction information as said data entry into said form;    validating values in the form using said received information;    otherwise returning an error to the user if the values are not validated; and    sending the transaction information to at least one specified server using information in the form, only if the values are validated.    
     
     
         10 . A method as in  claim 9 , wherein each of plural fields in the form is associated with a different server, and said sending uses an association from a field to determine a destination for information in the field.  
     
     
         11 . A method as in  claim 9 , wherein said values are text values.  
     
     
         12 . A method as in  claim 9 , wherein said values are sound values entered by voice.  
     
     
         13 . A method as in  claim 9 , wherein said values are menu values that are selected using scrolling keys.  
     
     
         14 . A method, comprising 
 obtaining transaction data entered by a user, said transaction data including at least one request for information;    converting the request for information into a request to a server, said converting including converting the transaction data to a different file format, said different file format being one associated with the database, and information indicative of the file format being within said information, based on said transaction data and also based on stored information; and    sending a request in the different file format to said server.    
     
     
         15 . A method as in  claim 14 , wherein said file format converts from one operating system to another operating system that is usable with said server.  
     
     
         16 . A method, comprising: 
 receiving information indicative of a data transaction;    based on information received as part of the transaction, sending said information to a plurality of different servers, where said sending uses a first address for a first of said servers, and uses a second address for a second of said servers, where said first address is different than said first address, and where each of the servers is capable of handling the entire data transaction.