SYSTEM AND METHOD FOR EXCHANGING INFORMATION AMONG EXCHANGE APPLICATIONS

• US 20070180150A1
• Filed: 12/01/2006
• Published: 08/02/2007
• Est. Priority Date: 12/01/2005
• Status: Abandoned Application

• Current Assignee: FireStar Software Incorporated
• Original Assignee: FireStar Software Incorporated
• Inventors: Eisner, Mark, Oancea, Gabriel
• Application Number:
  US11/566,185
• Publication Number:
  US 20070180150A1
• Time in Patent Office: Days
• US Class Current: 709/246
• 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

A system and method for communicating transaction information includes a plurality of client application devices distributed among one or more local client application devices and one or more remote client application devices, and a plurality of gateways distributed among one or more local gateways and one or more remote gateways. The one or more local gateways are configured to communicate the transaction information with the one or more local client application devices, with which the one or more local gateways are associated, using one or more local data formats. The one or more remote gateways are configured to communicate the transaction information with the one or more remote client application devices, with which the one or more remote gateways are associated, using one or more remote data formats. The one or more local gateways are configured to transform the transaction information in the one or more local data formats into one or more common data formats that are shared with the one or more remote gateways. The one or more remote gateways are configured to transform the transaction information in the one or more common data formats into the one or more remote data formats. The transaction information from the one or more local client application devices is communicated to the one or more remote client application devices for completing a transaction.

Claims

1. A system for communicating transaction information, comprising:

a plurality of client application devices distributed among one or more local client application devices and one or more remote client application devices; and

a plurality of gateways distributed among one or more local gateways and one or more remote gateways,

wherein the one or more local gateways are configured to communicate the transaction information with the one or more local client application devices, with which the one or more local gateways are associated, using one or more local data formats,

wherein the one or more remote gateways are configured to communicate the transaction information with the one or more remote client application devices, with which the one or more remote gateways are associated, using one or more remote data formats,

wherein the one or more local gateways are configured to transform the transaction information in the one or more local data formats into one or more common data formats that are shared with the one or more remote gateways,

wherein the one or more remote gateways are configured to transform the transaction information in the one or more common data formats into the one or more remote data formats, and

wherein the transaction information from the one or more local client application devices is communicated to the one or more remote client application devices for completing a transaction.

2. The system of claim 1, wherein the one or more remote gateways are configured to transform the transaction information in the one or more remote data formats into the one or more common data formats that are shared with the one or more local gateways,

wherein the one or more local gateways are configured to transform the transaction information in the one or more common data formats into the one or more local data formats, and

wherein the transaction information from the one or more remote client application devices is communicated to the one or more local client application devices for completing the transaction.

3. The system of claim 1, wherein the transaction comprises a compound transaction.

4. The system of claim 3, wherein the one or more local gateways and the one or more remote gateways are configured to suspend the compound transaction until a predetermined condition is satisfied.

5. The system of claim 4, wherein the predetermined condition comprises a time limit.

6. The system of claim 3, wherein each of the one or more local gateways and the one or more remote gateways are configured to determine a status of a component of the compound transaction.

7. The system of claim 3, wherein each of the one or more local gateways and the one or more remote gateways are configured to exchange a status of a component of the compound transaction.

8. The system of claim 1, wherein the transaction is supported by the one or more local application devices.

9. The system of claim 8, wherein the one or more common data formats includes information configured to allow the one or more remote client application devices to complete the transaction.

10. The system of claim 9, wherein the system is configured to facilitate an initiation and a completion of the transaction automatically.

11. The system of claim 1, wherein the transaction is associated with at least one of a commercial transaction, a legal transaction, a financial transaction, a governmental transaction, a medical transaction, a civic transaction, and a social transaction.

12. The system of claim 1, wherein the transaction is associated with at least one of a banking industry, a trading/securities/financial industry, a healthcare industry, a telecommunication industry, and a satellite service industry.

13. The system of claim 1, wherein the transaction is associated with at least one of an energy industry, a utility industry, a manufacturing industry, an automotive industry, and a pharmaceutical industry.

14. The system of claim 1, wherein the plurality of gateways are associated with a transaction administrator.

15. The system of claim 14, wherein the transaction administrator is configured to administer each gateway.

16. The system of claim 15, wherein the transaction administrator is configured to administer each gateway via automated messages.

17. The system of claim 16, wherein the plurality of gateways comprise processing modules that are configured to be updated using secure administrative messages.

18. The system of claim 17, wherein configuration information of each gateway is configured to be updated using the secure administrative messages.

19. The system of claim 1, wherein transaction information passed between the plurality of gateways include at least one of unique transaction ID tags, envelope ID tags, and message ID tags.

20. The system of claim 19, wherein an administrative message is configured to query one or more gateways to ascertain a status of the transaction, based on the at least one of the unique transaction ID tags, envelope ID tags and message ID tags.

21. The system of claim 1, wherein each gateway includes information configured to form a fully distributed data store in aggregate with information associated with other gateways.

22. The system of claim 21, wherein an administrative message is configured to query the fully distributed data store.

23. The system of claim 21, wherein information is generated into a standardized XML document.

24. The system of claim 23, wherein standardized XML documents generated from information contained in two or more gateways are combined into one standardized XML document that is used for non-repudiation of a business transaction.

25. The system of claim 1, wherein customized processes are associated with one or more transactions.

26. The system of claim 25, wherein the customized processes are distributed via administrative messages.

27. The system of claim 26, wherein the administrative messages are configured to utilize message security and provide a definable block in an envelope,

wherein the definable block is configured to provide parameters for the customized processes.

28. A gateway, comprising:

an information queue module, wherein the information queue module is configured to communicate transaction information in one or more local data formats with one or more local client applications;

a formatter module in communication with the information queue module, wherein the formatter module is configured to transform the transaction information in the one or more local data formats into a data format associated with the gateway;

a mapping module in communication with the formatter module, wherein the mapping module is configured to convert the transaction information in the data format associated with the gateway into a common data format that is shared with at least one other gateway, using a normative data model configured to generate normative transaction information;

a message processing module in communication with the mapping module, wherein the message processing module is configured to generate a gateway message by providing an envelope for the normative transaction information in the common data format; and

one or more communication modules in communication with the message processing module, wherein the one or more communication modules are configured to communicate the gateway message with at least one other gateway for completing a transaction.

29. The gateway of claim 28, wherein the formatter module is configured to transform the transaction information in a data format associated with the gateway into the one or more local data formats.

30. The gateway of claim 29, wherein the mapping module is configured to convert the normative transaction information in the common data format into a data format associated with the gateway.

31. The gateway of claim 30, wherein the message processing module is configured to process the envelope for the normative transaction information in the common data format.

32. The gateway of claim 31, wherein the message processing module is configured to execute predetermined next actions and processing demands imposed by the at least one other gateway.

33. The gateway of claim 31, wherein the one or more communication modules are configured to receive the gateway message provided by the at least one other gateway for completing the transaction.

34. The gateway of claim 28, comprising:

a first custom-processor module in communication between the information queue module and the formatter module, wherein the first custom-processor module is configured to process the transaction information using the one or more local data formats.

35. The gateway of claim 28, wherein the data format associated with the gateway comprises XML.

36. The gateway of claim 34, comprising:

a second custom-processor module in communication between the formatter module and the mapping module, wherein the second custom-processor is configured to process transformed transaction information using the data format associated with the gateway.

37. The gateway of claim 28, comprising:

a validation module in communication between the mapping module and the message processing module, wherein the validation module is configured to validate the normative transaction information.

38. The gateway of claim 37, wherein the validation module is configured to validate the normative transaction information to ensure that the normative transaction information includes data required by mandatory data fields.

39. The gateway of claim 37, wherein the validation module is configured to validate the normative transaction information to ensure that the normative transaction information includes data required by cross-data field constraints.

40. The gateway of claim 37, comprising:

a data enrichment module in communication between the validation module and the message processing module, wherein the data enrichment module is configured to customize the validated normative transaction information to generate enriched normative transaction information.

41. The gateway of claim 28, wherein the one or more communication modules are configured to record transmitted gateway messages and transaction states of the transmitted gateway messages.

42. The gateway of claim 41, wherein the one or more communication modules are configured to record received gateway messages and transaction states of received gateway messages.

43. The gateway of claim 28, wherein the gateway is configured to notify the information queue module and the one or more local client applications that a gateway message has been transmitted.

44. The gateway of claim 28, wherein the gateway is configured to encrypt one or more blocks of normative transaction information, and wherein the envelope is configured to provide descriptive information of the encryption.

45. The gateway of claim 44, wherein the gateway is configured to digitally sign the one or more blocks of normative transaction information, and

wherein the envelope is configured to provide descriptive information of the digital signature.

46. The gateway of claim 28, wherein the envelope of the normative transaction information includes message processing history for the gateway message.

47. The gateway of claim 46, wherein the message processing history comprises information components, and

wherein the gateway is configured to process individual information components of the message processing history.

48. The gateway of claim 46, wherein the message processing history includes a record of a change in state of the gateway message.

49. The gateway of claim 28, wherein the envelope of the normative transaction information includes addressing and routing information for the gateway message.

50. The gateway of claim 28, wherein the envelope of the normative transaction information includes transaction history of the transaction.

51. The gateway of claim 28, wherein the gateway is in communication with a data storage module,

wherein the data storage module is configured to store information transmitted and received by the gateway.