Device configuration and data extraction using a portable transaction format

• US 8,195,805 B2
• Filed: 02/28/2006
• Issued: 06/05/2012
• Est. Priority Date: 02/28/2006
• Status: Active Grant

• Current Assignee: Harris Global Communications, Inc. (L3Harris Technologies, Inc.)
• Original Assignee: Harris Corporation (L3Harris Technologies, Inc.)
• Inventors: Auzar, Adzim, Laveck, Robert, Mesh, Nathan
• Primary Examiner(s): Winder, Patrice
• Assistant Examiner(s): Hussain, Tauqir
• Application Number:
  US11/363,603
• Publication Number:
  US 20070204053A1
• Time in Patent Office: 2,289 Days
• Field of Search: 709/230
• US Class Current: 709/227
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level

Abstract

Method for performing a data transaction (200) with a server (108) using a portable computer (106). The method includes receiving (402) in the portable computer a portable transaction file (104-1, 104-2, 104-3, 104-n) in a predetermined portable transaction file format (500) that includes two or more data fields. The data fields can contain a set of transaction parameters that define a type specific server protocol for a data transaction session with a particular server type (108-1, 108-2, 108-3, 108-n). By using a generic data transaction engine (302, 303) a data transaction session can be performed with any type of server for which a portable transaction file has been provided.

Claims

1. A method for performing a data transaction with a server using a portable computer, comprising:

prior to establishing a data communications link between a portable computer and a server of a selected server type, receiving in said portable computer from a computer remote from said server one or more portable transaction files in a predetermined portable transaction file format that includes a plurality of data fields, each of said portable transaction files specifying in one or more of said data fields a plurality of transaction parameters comprising a transaction parameter set that defines a type specific server protocol that is to be used during a data transaction session between said portable computer and a server of one of a plurality of different particular server types;

establishing said data communications link between said portable computer and said server;

executing on said portable computer a generic data transaction engine software application;

using said transaction parameter set of a respective portable transaction file of said portable transaction files to configure said generic data transaction engine software application such that session communications between said portable computer and said server can be performed in accordance with said type specific server protocol, said respective portable transaction file being provided for said selected server type; and

performing said data transaction session with said server if one of said portable transaction files has been provided for said selected server type by using said generic data transaction engine software application;

wherein said generic data transaction engine software application is universally configurable for facilitating data transaction session communications between said portable computer and servers of said plurality of different particular server types using a plurality of type specific server protocols, said generic data transaction engine software application being universally configurable based on said portable transaction files;

wherein said transaction parameter set is defined to specify at least (1) a set of connection properties required for communicating with the server of said one of said plurality of particular server types, (2) a set of commands for controlling the server of said one of said plurality of particular server types, (3) a sequence of requests, (4) a set of pre-conditions to be satisfied before each request occurs, (5) a set of queries for obtaining information from the server of said one of said plurality of particular server types, and (6) a set of error scenario parameters.

2. A method for performing a data transaction with a server using a portable computer, comprising:

prior to establishing a data communications link between a portable computer and a server of a selected server type, providing said portable computer with a generic data transaction engine comprising a generic data transaction software application dynamically configurable for facilitating data transaction session communications between said portable computer and servers of a plurality of different server types using a plurality of type specific server protocols;

providing said portable computer with one or more portable transaction files from another computer remote from said server in a predetermined portable transaction file format that includes a plurality of data fields, said plurality of data fields in each of said portable transaction files provided for specifying a transaction parameter of a transaction parameter set that defines a type specific server protocol that is to be used during a data transaction session of said data transaction sessions between said portable computer and one of said servers; and

responsive to establishing a data communication link between said portable computer and said server, performing said data transaction session between said portable computer and said server by using said generic data transaction engine, if one of said portable transaction files is associated with said selected server type;

wherein said transaction parameter set is selected to specify at least (1) the information that should be sent to a server of one of said plurality of different server types, (2) the information that is required from the server of the one of said plurality of different server types, and (3) the overall connection information specifying how the portable computer is to connect to the server of the one of said plurality of different server types.

3. A portable computer for performing a data transaction with a server, comprising:

a data store in said portable computer containing one or more portable transaction files in a predetermined portable transaction file format that includes a plurality of data fields, each of said portable transaction files specifying in one or more of said data fields a plurality of transaction parameters comprising a transaction parameter set that defines a type specific server protocol that is to be used during a data transaction session between said portable computer and one of a plurality of different particular server types;

at least one transceiver element for establishing a data communications link between said portable computer and a server of a selected server type and for receiving said portable transaction files from another computer remote from said server; and

a processing element executing a software application comprising a generic data transaction engine software application that is universally configurable for facilitating data transaction session communications between said portable computer and servers of said plurality of different particular server types using a plurality of type specific server protocols, said generic data transaction engine software application being universally configurable based on said portable transaction files, wherein responsive to said establishing said data communications link, said processing element performs said data transaction session with said server if one of said portable transaction file has been provided for said selected server type;

wherein said transaction parameter set specifies at least (1) a set of connection properties required for communicating with a server of the one of said plurality of different particular server types, (2) a set of commands for controlling the server of the one of said plurality of different particular server types, (3) a sequence or ordering of requests, (4) a set of pre-conditions to be satisfied before each request occurs, (5) a set of queries for obtaining information from the server of the one of said plurality of different particular server types, and (6) a set of error scenario parameters.