System and method for exchanging information among exchange applications

• US 9,742,880 B2
• Filed: 03/12/2012
• Issued: 08/22/2017
• Est. Priority Date: 12/01/2005
• Status: Expired due to Fees

• Current Assignee: FireStar Software Incorporated
• Original Assignee: FireStar Software Incorporated
• Inventors: Eisner, Mark, Oancea, Gabriel
• Primary Examiner(s): Nguyen, Thuong
• Application Number:
  US13/418,240
• Publication Number:
  US 20130041888A1
• Time in Patent Office: 1,989 Days
• Field of Search: 709223, 709224, 709225, 707102, 707201, 370401, 370428, 370474
• CPC Class Codes: G06F 15/16 Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs coordinating program control therefor G06F9/52; in regulating and control system G05B
• CPC Class Codes: G06F 2209/548 Queue
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 20/027 involving a payment switch or gateway
• CPC Class Codes: G06Q 20/223 based on the use of peer-to-peer networks
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: H04L 2463/102 applying security measure for e-commerce data processing systems or methods, specially adapted for e-commerce G06Q30/00
• CPC Class Codes: H04L 49/3009 Header conversion, routing tables or routing tags
• CPC Class Codes: H04L 49/309 Header conversion, routing tables or routing tags
• CPC Class Codes: H04L 49/9042 Separate storage for different parts of the packet, e.g. header and payload
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 63/0209 Architectural arrangements, e.g. perimeter networks or demilitarized zones
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/102 Entity profiles
• 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 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/147 Signalling methods or messages providing extensions to protocols defined by standardisation
• CPC Class Codes: H04L 67/56 : Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/561 : Adding application-functional data or data for application control, e.g. adding metadata
• 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 69/161 : Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
• CPC Class Codes: H04L 69/22 : Parsing or analysis of headers
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]

Abstract

In a system and method for accessing messages in a data store in a gateway, a data frame request, which is a structured SQL query, is received at the gateway. The received data frame request is applied to the gateway data store, which stores messages. A data frame is generated that comprises messages from the data store that are responsive to the received data frame request, the data frame having a format that is readable by a character editor.

Claims

1. A method for accessing transaction messages in a data store of a first gateway, comprising:

receiving, by the first gateway, a data frame request from a second gateway, the data frame request comprising a structured query and including criteria for retrieving at least one transaction message transmitted by or received at the first gateway and stored in the data store of the first gateway,

wherein the at least one transaction message stored at the first gateway includes information of a transaction identified by metadata associated with the at least one transaction message, the metadata comprising a unique message identifier and zero or more of a unique transaction identifier, a message type, or a transaction type, and

wherein the criteria for retrieving the at least one transaction message included in the data frame request includes the metadata associated with the at least one transaction message;

retrieving, by the first gateway, the at least one transaction message from the data store of the first gateway using the criteria for retrieving the at least one transaction message included in the received data frame request; and

generating, by the first gateway comprising at least one processor, a data frame comprising the at least one transaction message retrieved from the data store of the first gateway, the data frame having a format that is readable by a character editor; and

sending, by the first gateway to the second gateway, responsive to the data frame request, the generated data frame.

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

storing state data as metadata associated with the transaction message in the data store of the first gateway; and

retrieving the state data for generating the data frame based on a data frame request criteria.

3. The method according to claim 1, further comprising deleting the at least one transaction message from the data store of the first gateway that are provided in the generated data frame.

4. The method according to claim 1, wherein the at least one transaction message in the data store of the first gateway includes a header and a payload, the method further comprising:

deleting, from the data store, the payload of the at least one transaction message that are provided in the generated data frame; and

creating a reference to the generated data frame that contains the delete payload, the reference being stored in the metadata of the transaction message.

5. The method according to claim 1, further comprising importing, by the second gateway, the at least one transaction message including the metadata in the generated data frame into the data store of the second gateway.

6. The method according to claim 1, wherein at least one of the transaction messages in the data frame includes financial transaction data.

7. The method according to claim 1, wherein at least one of the transaction messages in the data frame includes medical or patient data.

8. The method according to claim 1, wherein at least one of the transaction messages in the data frame includes security and access control data.

9. The method according to claim 1, wherein at least one of the transaction messages in the data frame includes compliance and regulatory data.

10. The method according to claim 1, wherein at least one of the transaction messages in the data frame includes communication protocols and network data.

11. The method according to claim 1, wherein the data frame request is one of a set of data frame requests being sent by the second gateway, the set of data frame requests including requests for the information of the transaction identified by metadata associate with the transaction messages, and at least one of the set of data frame requests being sent to another gateway, further comprising:

receiving, by the second gateway, a first response message from the first gateway and a second response message from the another gateway; and

generating, by the second gateway, a second data frame comprising at least one of the response messages received from the first gateway and the another gateway.

12. A method for accessing data in a data store in a first gateway, comprising:

receiving, by the first gateway, a data frame request from a second gateway, the data frame request comprising a structured query and including criteria for retrieving state data stored in the data store of the first gateway;

wherein the state data is associated with at least one transaction message stored at the first gateway, the at least one transaction message including information of a transaction identified by metadata associated with the at least one transaction message, the metadata comprising a unique message identifier and zero or more of a unique transaction identifier, a message type, or a transaction type, and

wherein the criteria for retrieving the state data included in the data frame request includes the metadata associated with the at least one transaction message;

retrieving, by the first gateway, the state data from the data store of the first gateway using the criteria for retrieving the state data included in the received data frame request; and

generating, by the first gateway comprising at least one processor, a data frame comprising the state data retrieved from the data store, the data frame having a format that is readable by a character editor; and

sending, by the first gateway to the second gateway, responsive to the data frame request, the generated data frame.

13. The method according to claim 12, wherein the data frame request is one of a set of data frame requests being sent by the second gateway, the set of data frame requests including requests for the state data identified by metadata associate with the transaction messages, and at least one of the set of data frame requests being sent to another gateway, further comprising:

receiving, by the second gateway, a first response message from the first gateway and a second response message from the another gateway; and

generating, by the second gateway, a second data frame comprising at least one of the response messages received from the first gateway and the another gateway.

14. A gateway for storing and accessing transaction messages in a data store, comprising:

a processor; and

a memory, coupled to the processor, the memory comprising a plurality of instructions executed by the processor, the plurality of instructions configured to;

receive, at the gateway, a data frame request from a second gateway, the data frame request comprising a structured query and including criteria for retrieving at least one transaction message transmitted by or received at the gateway and stored in the data store of the gateway;

wherein the at least one transaction message stored at the first gateway includes information of a transaction identified by metadata associated with the at least one transaction message, the metadata comprising a unique message identifier and zero or more of a unique transaction identifier, a message type, or a transaction type, and

wherein the criteria for retrieving the at least one transaction message included in the data frame request includes the metadata associated with the at least one transaction message;

retrieve, at the gateway, the at least one transaction message from the data store of the gateway using the criteria for retrieving the at least one transaction message included in the received data frame request; and

generate, at the gateway, a data frame comprising the at least one transaction message retrieved from the data store, the data frame having a format that is readable by a character editor; and

send, to the second gateway, responsive to the data frame request, the generated data frame.

15. The gateway according to claim 14, wherein the memory further comprises instructions configured to:

store state data as metadata associated with the transaction message in the data store of the gateway; and

retrieve the state data for generating the data frame based on a data frame request criteria.

16. The gateway according to claim 14, wherein the memory further comprises an instruction configured to delete the at least one transaction message from the data store of the gateway that are provided in the data frame.

17. The gateway according to claim 14, wherein the at least one transaction message in the data store of the gateway includes a header and a payload, wherein the memory further comprises instructions configured to:

delete from the data store the payload of the at least one transaction message that are provided in the generated data frame; and

create a reference to the generated data frame that contains the delete payload, the reference being stored in the metadata of the transaction message.

18. The gateway according to claim 14, wherein the memory further comprises an instruction configured to import the at least one transaction message including the metadata in the generated data frame into a data store of the second gateway.

19. The gateway according to claim 14, wherein the data frame request is one of a set of data frame requests being sent by the second gateway, the set of data frame requests including requests for the information of the transaction identified by metadata associate with the transaction messages, and at least one of the set of data frame requests being sent to another gateway, further comprising:

receiving, by the second gateway, a first response message from the gateway and a second response message from the another gateway; and

generating, by the second gateway, a second data frame comprising at least one of the response messages received from the gateway and the another gateway.

20. A gateway, comprising:

a data store storing transaction messages, each message including a message header with one or more header blocks and a payload;

an abstract queue configured to receive a data frame request from a second gateway comprising a structured query and including criteria for retrieving at least one transaction message transmitted by or received at the gateway and stored in the data store of the gateway,

wherein the at least one transaction message stored at the first gateway includes information of a transaction identified by metadata associated with the at least one transaction message, the metadata comprising a unique message identifier and zero or more of a unique transaction identifier, a message type, or a transaction type, and

wherein the criteria for retrieving the at least one transaction message included in the data frame request includes the metadata associated with the at least one transaction message;

at least one processing unit configured to;

retrieve the at least one transaction message from the data store of the gateway using the criteria for retrieving the at least one transaction message included in the received data frame request;

generate a data frame comprising the at least one transaction message retrieved from the data store, the data frame having a format that is readable by a character editor; and

send, from the gateway to the second gateway, responsive to the data frame request, the generated data frame.

21. The gateway according to claim 20, wherein the data store further includes state data as metadata associated with the transaction message, and

wherein the data frame further comprises the state data retrieved from the data store based on the data frame request.

22. The gateway according to claim 20, wherein the at least one processing unit is further configured to delete the at least one transaction message from the data store of the gateway that are provided in the generated data frame.

23. The gateway according to claim 20, wherein the at least one processing unit is further configured to:

delete the payload of the at least one transaction message that are provided in the generated data frame; and

create a reference to the generated data frame that contains the delete payload, the reference being stored in the metadata of the transaction message.

24. The gateway according to claim 20, wherein the second gateway is configured to import the at least one transaction message including the metadata in the generated data frame into a data store of the second gateway.

25. The gateway according to claim 20, wherein the data frame request is one of a set of data frame requests being sent by the second gateway, the set of data frame requests including requests for the information of the transaction identified by metadata associate with the transaction messages, and at least one of the set of data frame requests being sent to another gateway, further comprising:

receiving, by the second gateway, a first response message from the gateway and a second response message from the another gateway; and

generating, by the second gateway, a second data frame comprising at least one of the response messages received from the gateway and the another gateway.