System and method for exchanging information among exchange applications

• US 8,838,668 B2
• Filed: 12/01/2006
• Issued: 09/16/2014
• Est. Priority Date: 12/01/2005
• Status: Active Grant

• Current Assignee: FireStar Software Incorporated
• Original Assignee: FireStar Software Incorporated
• Inventors: Eisner, Mark, Oancea, Gabriel
• Primary Examiner(s): VOSTAL, ONDREJ C
• Application Number:
  US11/566,182
• Publication Number:
  US 20070198437A1
• Time in Patent Office: 2,846 Days
• Field of Search: 709/201, 705/79, 705/64, 726/13
• US Class Current: 709/201
• 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 persisting information associated with performing message-based business processes among a plurality of different applications, comprising:

receiving or sending a gateway message at a gateway, the gateway message comprising a message header and a payload, the message header comprising a history block and a security block, and the payload comprising payload information,

wherein entries in the history block comprise at least two states, wherein the at least two states comprise a first state of processing a transaction and a second state of processing the transaction, wherein the first state preceded the second state in the history of processing the transaction,

wherein entries in the security block comprise information associated with security of the message and indicating what is encrypted or digitally signed in the message and by which entity, and wherein the entries in the security block are not encrypted,

persisting the entries in the history block in a data store of the gateway;

persisting the entries in the security block in the data store of the gateway; and

persisting the payload in the data store of the gateway.

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

3. The method according to claim 1, wherein the message header further comprises 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, the method further comprising:

persisting the complex transaction template and associated state information about the complex transaction.

4. The method according to claim 1, wherein the gateway message comprises financial transaction data.

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

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

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

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

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

persisting the gateway message in temporary storage;

when the gateway message was not received within a predetermined period of time, resending the gateway message;

when the gateway message was received, waiting for a callback that indicates that the message was received; and

deleting the message from temporary storage.

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

persisting a message state; and

establishing a listener process to wait for a return from a sub-process.

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

persisting any message that is to be transmitted from the gateway that is associated with a simple transaction in which the gateway message is participating; and

persisting information about a state of the simple transaction;

wherein the header of the received or sent gateway message further comprises a transaction identification block which comprises an identifier of the simple transaction.

12. A gateway for persisting information associated with performing message-based business processes among a plurality of different 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 or send a gateway message at the gateway, the gateway message comprising a message header and a payload, the message header comprising a history block and a security block, and the payload comprising payload information,

wherein entries in the history block comprises at least two states, wherein the at least two states comprise a first state of processing a transaction and a second state of processing the transaction the first state preceded the second state in the history of processing the transaction,

wherein entries in the security block comprise information associated with security of the message and indicating what is encrypted or digitally signed in the message and by which entity, and wherein the entries in the security block are not encrypted,

persist the entries in the history block in a data store of the gateway;

persist the entries in the security block in the data store of the gateway; and

persist the payload information.

13. The gateway according to claim 12, wherein the plurality of instructions are further configured to persist configuration data in the data store in the gateway, the configuration data comprising information defining one or more simple transactions that can be performed by the gateway.

14. The gateway according to claim 12, wherein the message header further comprises 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;

and

wherein the plurality of instructions are further configured to persist the complex transactions template and associated state information about the complex transaction.

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

an abstract queue configured to receive a gateway message at the gateway, the gateway message comprising a message header and a payload, the message header comprising a history block and a security block, and the payload comprising payload information,

wherein entries in the history block comprise at least two states, wherein the at least two states comprise a first state of processing a transaction and a second state of processing the transaction, wherein the first state preceded the second state in the history of processing the transaction,

wherein entries in the security block comprise information associated with security of the message and indicating what is encrypted or digitally signed in the message and by which entity, and wherein the entries in the security block are not encrypted,

a data store; and

a processor configured to;

persist the entries in the history block in the data store;

persist the entries in the security block in the data store; and

persist the payload information in the data store.

16. The gateway according to claim 15, wherein the processor is further configured to persist configuration data in the data store in the gateway, the configuration data comprising information defining one or more simple transactions that can be performed by the gateway.

17. The gateway according to claim 15, wherein the message header further comprises 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;

and

wherein the processor is further configured to persist the complex transaction template and associated state information about the complex transaction.

18. The gateway according to claim 15, wherein the data store stores information necessary for the gateway to operate.

19. The gateway according to claim 15, wherein the data store archives information stored in the gateway.

20. The gateway according to claim 15, wherein the data store stores a signature with each gateway message to ensure data security.