SYSTEM AND METHOD FOR EXCHANGING INFORMATION AMONG EXCHANGE APPLICATIONS

• US 20070198437A1
• Filed: 12/01/2006
• Published: 08/23/2007
• Est. Priority Date: 12/01/2005
• Status: Active Grant

• Current Assignee: FireStar Software Incorporated
• Original Assignee: FireStar Software Incorporated
• Inventors: Eisner, Mark, Oancea, Gabriel
• Granted Patent: US 8,838,668 B2
• Time in Patent Office: Days
• US Class Current: 705/79
• 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 performing message-based business processes among a plurality of applications, a gateway message is received at the gateway, the gateway message including a gateway message header and a payload, the gateway message header including a routing slip block providing a template of a complex transaction in which the gateway message is participating, the complex transaction comprising one or more simple transactions performed in a defined order. A copy of the received gateway message is persisted in a data store in the gateway. The gateway executes at least one simple transaction in accordance with the template in the routing slip in the received gateway message and persists a copy of the gateway message, after executing the at least one simple transaction, in the data store.

Claims

1. A method for performing message-based business processes among a plurality of applications, comprising:

receiving a gateway message at the gateway, the gateway message including a gateway message header and a payload, the gateway message header including a routing slip block providing a template of a complex transaction in which the gateway message is participating, the complex transaction comprising one or more simple transactions performed in a defined order;

persisting a copy of the received gateway message in a data store in the gateway;

executing at the gateway at least one simple transaction in accordance with the template in the routing slip in the received gateway message; and

persisting a copy of the gateway message, after executing the at least one simple transaction, in the data store.

2. The method according to claim 1, further comprising storing configuration data in the data store in the gateway, the configuration data including information defining the one or more simple transactions that can be performed by the gateway,

wherein the at least one simple transaction is executed in accordance with the information defining one or more simple transactions in the configuration data stored in the data store.

3. The method according to claim 1, wherein the gateway message header further includes a transaction identification block providing an identifier of the transaction in which the gateway message is participating.

4. The method according to claim 3, further comprising:

receiving a data frame request, which is a structured SQL query;

applying the received data frame request to the gateway data store, which stores messages; and

generating a data frame comprising 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.

5. The method according to 4, further comprising:

storing configuration data and state data in the data store;

wherein the data frame further comprises at least one of configuration data or state data from the data store that is responsive to the data frame request.

6. The method according to 5, further comprising deleting the at least one of the configuration data or the state data from the data store that are provided in the data frame.

7. The method according to 4, further comprising deleting the messages from the data store that are provided in the data frame.

8. The method according to 4, wherein each message includes a header and a payload, the method further comprising:

deleting the payloads from the data store of the messages that are provided in the data frame; and

adding a reference to the data store of the data frame having the payloads deleted from the data store.

9. The method according to 4, further comprising importing the data frame into the data store.

10. The method according to claim 4, wherein the data frame request includes the identifier, and the generated data frame includes messages from the data store having the identifier it the transaction identification block.

11. The method according to claim 10, further comprising:

referencing a routing slip block in at least one of the messages responsive to the received data frame request; and

transmitting the data frame request to a target gateway based on information in the routing slip block in at least one of the messages responsive to the received data frame request.

12. The method according to claim 1, wherein the gateway message includes financial transaction data.

13. The method according to claim 1, wherein the gateway message includes medical or patient data.

14. The method according to claim 1, wherein the gateway message includes security and access control data.

15. The method according to claim 1, wherein the gateway message includes compliance and regulatory data.

16. The method according to claim 1, wherein the gateway message includes communication protocols and network data.

17. A gateway for performing message-based business processes among a plurality of applications, 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 a gateway message at the gateway, the gateway message including a gateway message header and a payload, the gateway message header including a routing slip block providing a template of a complex transaction in which the gateway message is participating, the complex transaction comprising one or more simple transactions performed in a defined order;

persist a copy of the received gateway message in a data store in the gateway;

execute at the gateway at least one simple transaction in accordance with the template in the routing slip in the received gateway message; and

persist a copy of the gateway message, after executing the at least one simple transaction, in the data store.

18. The gateway according to claim 17, wherein the memory further comprises an instruction configured to store configuration data in the data store in the gateway, the configuration data including information defining the one or more simple transactions that can be performed by the gateway,

wherein the at least one simple transaction is executed in accordance with the information defining one or more simple transactions in the configuration data stored in the data store.

19. The gateway according to claim 17, wherein the gateway message header further includes a transaction identification block providing an identifier of the transaction in which the gateway message is participating.

20. The gateway according to claim 19, wherein the memory further comprises instructions configured to:

receive a data frame request, which is a structured SQL query;

apply the received data frame request to the gateway data store, which stores messages; and

generate a data frame comprising 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.

21. The gateway according to 20, wherein the memory further comprises an instruction configured to delete the messages from the data store that are provided in the data frame.

22. The gateway according to 20, wherein each message includes a header and a payload, wherein the memory further comprises instructions configured to:

delete the payloads from the data store of the messages that are provided in the data frame; and

add a reference to the data store of the data frame having the payloads deleted from the data store.

23. The gateway according to claim 20, wherein the data frame request includes the identifier, and the generated data frame includes messages from the data store having the identifier it the transaction identification block.

24. The gateway according to claim 23, wherein the memory further comprises an instruction configured to:

reference a routing slip block in at least one of the messages responsive to the received data frame request; and

transmit the data frame request to a target gateway based on information in the routing slip block in at least one of the messages responsive to the received data frame request.

25. A gateway for performing message-based business processes among a plurality of applications, comprising:

an abstract queue configured to receive a gateway message at the gateway, the gateway message including a gateway message header and a payload, the gateway message header including a routing slip block providing a template of a complex transaction in which the gateway message is participating, the complex transaction comprising one or more simple transactions performed in a defined order;

a data store configured to persist a copy of the received gateway message in a data store in the gateway; and

at least one processing unit configured to execute at the gateway at least one simple transaction in accordance with the template in the routing slip in the received gateway message,

wherein the data store is further configured to persist a copy of the gateway message after executing the at least one simple transaction.

26. The gateway according to claim 25, wherein the memory further comprises an instruction configured to store configuration data in the data store in the gateway, the configuration data including information defining the one or more simple transactions that can be performed by the gateway,

wherein the at least one simple transaction is executed in accordance with the information defining one or more simple transactions in the configuration data stored in the data store.

27. The gateway according to claim 25, wherein the gateway message header further includes a transaction identification block providing an identifier of the transaction in which the gateway message is participating.

28. The gateway according to claim 27, wherein the memory further comprises instructions configured to:

receive a data frame request, which is a structured SQL query;

apply the received data frame request to the gateway data store, which stores messages; and

generate a data frame comprising 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.

29. The gateway according to 28, wherein the memory further comprises an instruction configured to delete the messages from the data store that are provided in the data frame.

30. The gateway according to 28, wherein each message includes a header and a payload, wherein the memory further comprises instructions configured to:

delete the payloads from the data store of the messages that are provided in the data frame; and

add a reference to the data store of the data frame having the payloads deleted from the data store.

31. The gateway according to claim 28, wherein the data frame request includes the identifier, and the generated data frame includes messages from the data store having the identifier it the transaction identification block.

32. The gateway according to claim 31, wherein the memory further comprises an instruction configured to:

reference a routing slip block in at least one of the messages responsive to the received data frame request; and

transmit the data frame request to a target gateway based on information in the routing slip block in at least one of the messages responsive to the received data frame request.