US20070180150A1 - System and method for exchanging information among exchange applications - Google Patents

System and method for exchanging information among exchange applications Download PDF

Info

Publication number
US20070180150A1
US20070180150A1 US11/566,185 US56618506A US2007180150A1 US 20070180150 A1 US20070180150 A1 US 20070180150A1 US 56618506 A US56618506 A US 56618506A US 2007180150 A1 US2007180150 A1 US 2007180150A1
Authority
US
United States
Prior art keywords
gateway
message
transaction
data
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US11/566,185
Other languages
English (en)
Inventor
Mark Eisner
Gabriel Oancea
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
FireStar Software Inc
Original Assignee
FireStar Software Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by FireStar Software Inc filed Critical FireStar Software Inc
Priority to US11/566,185 priority Critical patent/US20070180150A1/en
Assigned to FIRESTAR SOFTWARE, INC. reassignment FIRESTAR SOFTWARE, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: EISNER, MARK, OANCEA, GABRIEL
Publication of US20070180150A1 publication Critical patent/US20070180150A1/en
Priority to US13/212,967 priority patent/US8838737B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/546—Message passing systems or structures, e.g. queues
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G06Q20/027—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] involving a payment switch or gateway
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/22—Payment schemes or models
    • G06Q20/223—Payment schemes or models based on the use of peer-to-peer networks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/30—Peripheral units, e.g. input or output ports
    • H04L49/3009—Header conversion, routing tables or routing tags
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/30—Peripheral units, e.g. input or output ports
    • H04L49/3081—ATM peripheral units, e.g. policing, insertion or extraction
    • H04L49/309—Header conversion, routing tables or routing tags
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/90—Buffering arrangements
    • H04L49/9042—Separate storage for different parts of the packet, e.g. header and payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0209—Architectural arrangements, e.g. perimeter networks or demilitarized zones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H04L63/123—Applying verification of the received information received data contents, e.g. message integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H04L63/126—Applying verification of the received information the source of the received data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/147—Signalling methods or messages providing extensions to protocols defined by standardisation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/561—Adding application-functional data or data for application control, e.g. adding metadata
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/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
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/548—Queue
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
    • H04L2463/102—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying security measure for e-commerce
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail

Definitions

  • the present invention relates generally to communication systems and, more particularly, to a system and method for exchanging information among remote exchange applications.
  • a computerized business transaction is a domain specific, distributed application that involves the sending and receiving of information that can be part of a multiple-enterprise business process.
  • the information exchanges in a business transaction are contained in standardized and self-defined messages.
  • Software applications in an enterprise create and process messages in preparation for sending them and process the messages after they have been received. In some cases, it can appear that human beings do the processing, such as ordering a widget online, and the like. However, since those individuals must interact through an application, say, for example, a browser, it is considered that an “application” is doing the processing.
  • Business transactions can be as simple as the one-way transmission of information, for example, a payment from an accounts payable application in Corporation A to an accounts receivable application in Corporation B.
  • the business transactions can be as complicated as a multi-step transaction that involves many players and include many sub-transactions, for example, the cross-border settlement of a stock purchase that could involve over a dozen players.
  • business transactions can span a very short time interval, for example, a Request/Response interaction that approves the use of a credit card, or can literally span days or months, for example, the settlement of an insurance claim.
  • 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.
  • FIG. 1 is a diagram illustrating system for system for communicating messages, in accordance with an exemplary embodiment of the present invention.
  • FIG. 2 is a diagram illustrating a gateway, in accordance with an exemplary embodiment of the present invention.
  • FIG. 3 is a diagram illustrating a gateway message, in accordance with an exemplary embodiment of the present invention.
  • FIG. 4 illustrates a one-step transaction using an activity diagram, in accordance with an exemplary embodiment of the present invention.
  • FIG. 5 illustrates a one-step transaction with a business acknowledgment, using an activity diagram, in accordance with an exemplary embodiment of the present invention.
  • FIG. 6 illustrates a one-step transaction with two business acknowledgments, using an activity diagram, in accordance with an exemplary embodiment of the present invention.
  • FIG. 7 illustrates a Request/Response transaction, using an activity diagram, in accordance with an exemplary embodiment of the present invention.
  • FIG. 8 illustrates a exemplary blocks in a message header of a gateway message, in accordance with an exemplary embodiment of the present invention.
  • FIG. 9 illustrates a block diagram of a process flow with abstract queues, in accordance with an exemplary embodiment of the present invention.
  • FIG. 10 illustrates a block diagram of a process flow for a raw message formatter in an IN queue, in accordance with an exemplary embodiment of the present invention.
  • FIG. 11 illustrates a block diagram of a process flow for a raw message formatter in an OUT queue, in accordance with an exemplary embodiment of the present invention.
  • FIG. 12 illustrates a process flow for generating a gateway message from a raw message, in accordance with an exemplary embodiment of the present invention.
  • FIG. 13 illustrates a flow diagram of selected steps in the process flow of FIG. 12 , in accordance with an exemplary embodiment of the present invention.
  • FIG. 14 illustrates an example of a data frame resulting from monitoring activity, in accordance with an exemplary embodiment of the present invention.
  • Exemplary embodiments of the present invention are directed to a system and method for system and method for exchanging information among remote exchange applications, such as to participate in and complete transactions.
  • the system is comprised of a distributed application platform that is configured, for example, to handle defined, computerized business transactions among a community of disparate companies.
  • the system can integrate existing client environments, regardless of the client's technology choices and data formats.
  • the system is configured to convert existing client data into a common model data that can be shared among all other clients.
  • the system includes the functions of a robust message system, and does not require a centralized processor or centralized database.
  • the system provides the capability to develop multi-enterprise business transaction exchange applications (i.e., gateway applications), with minimal impact on each client.
  • the system can be used by a controlling manager, such as, for example, a solution provider, that builds, distributes and manages the business transaction exchange applications among a group of clients.
  • the solution providers can define global transaction attributes, such as, for example, the transactions supported, global validation rules, security, message processes, data stores and common services, that are shared with each client.
  • each client can retain autonomy over their (perhaps unique and/or proprietary) transactions and data formats.
  • Each client can maintain a local store of transactions that are transmitted and received.
  • each client can use their existing file formats and transport software, as the system uses the client's existing infrastructure. Consequently, little or no changes are required for the client's applications.
  • the solution provider can design the gateway applications using exemplary embodiments of the present invention to build an application that can be distributed and installed at all desired client sites.
  • Each of the gateway applications is configured to communicate with other gateway applications in one or more common data formats that are shared and understood by all of the gateway applications.
  • the gateway application at a client's site is also integrated to the local client's data formats, transport protocols, and any customized requirements.
  • the local gateway applications are then configured to convert or otherwise transform the proprietary transaction information from the local client application into the common data format so that the information can be communicated to another, remote gateway application.
  • the remote gateway application can convert or otherwise transform the transaction information in the common data format to the data format required by the remote client application.
  • all clients can send and receive transaction information to and from other clients to perform inter-corporate, multi-enterprise automated business or other suitable transactions.
  • FIG. 1 is a diagram illustrating system 100 for system for communicating transaction information, in accordance with an exemplary embodiment of the present invention.
  • the system 100 includes a plurality of client application devices 105 (e.g., client application device 1 , client application device 2 , client application device 3 , . . . client application device M, where M can be any suitable number).
  • the client application devices 105 are distributed among one or more local client application devices and one or more remote client application devices.
  • the system 100 also includes a plurality of gateways 110 (e.g., gateway 1 , gateway 2 , . . ., gateway N, where N can be any suitable number).
  • the plurality of gateways 110 which can also be referred to as transaction exchangers, are distributed among one or more local gateways and one or more remote gateways.
  • the first gateway 110 i.e., gateway 1
  • the second through Nth gateways 110 i.e., gateway 2 , . . ., gateway N
  • the first and second client application devices 105 i.e., client application device 1 and client application device 2
  • the second and third through Mth client application devices 105 i.e., client application device 2 , client application device 3 , . . ., client application device M
  • the one or more local gateways 110 are configured to communicate transaction information with the one or more local client application devices 105 , with which the one or more local gateways 110 are associated, using one or more local data formats.
  • the one or more remote gateways 110 are configured to communicate the transaction information with the one or more remote client application devices 105 , with which the one or more remote gateways 110 are associated, using one or more remote data formats.
  • each gateway 110 is a local gateway with respect to itself.
  • the client application device 105 is a local client application device with respect to the local gateway 110 with which the client application device 105 is associated. Consequently, any gateways 110 not located locally are remote gateways 110 with respect to the local gateway 110 . Additionally, any client application devices 105 not located locally are remote client application devices 105 with respect to the local client application device 105 and the associated local gateway 110 .
  • Each client application device 105 communicates with the associated gateway 105 using one or more local data formats.
  • each gateway 110 understands the one or more local data formats used by the client application device 105 with which the gateway 110 is associated.
  • each client application device 105 can be a proprietary, customized or otherwise unique user application that uses proprietary, customized or otherwise unique data formats to undertake and process a transaction.
  • the local data format of each (local) client application device 105 may not be understood or otherwise compatible with local data formats used by other (remote) client application devices 105 . Therefore, according to exemplary embodiments, the one or more local gateways 110 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 110 .
  • each gateway 110 can convert the transaction information in the local data format used by the associated client application device 105 into a data format that is understood and used by all transactions exchangers 110 .
  • Such a common data format allows each gateway 110 to communicate and share data or other messages with one or more other gateways 110 .
  • the first gateway 110 can transform the transaction information from the first client application device 105 from the local data format used by the first client application device 105 to the common data format used by the gateways 110 . Once transformed, the first gateway 110 can transmit or otherwise communicate the transaction information in the common data format to another gateway 110 , such as the second gateway 110 .
  • the second gateway 110 receives the transaction information in the common data format, the second gateway 110 is configured to transform the transaction information in the common data format into the data format used by the third client application device 105 with which the second gateway 110 is associated.
  • the one or more remote gateways 110 can transform or otherwise convert 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 105 can be communicated to the one or more remote client application devices 105 for completing a transaction, without regard to the data formats used by each of the client application devices 105 .
  • the one or more remote gateways 110 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 110 .
  • the second gateway 110 can transform the transaction information from the third client application device 105 from the local data format used by the third client application device 105 to the common data format used by the gateways 110 . Once transformed, the second gateway 110 can transmit or otherwise communicate the transaction information in the common data format to another gateway 110 , such as the first gateway 110 .
  • the first gateway 110 receives the transaction information in the common data format
  • the first gateway 110 is configured to transform the transaction information in the common data format into the data format used by the first client application device 105 with which the first gateway 110 is associated.
  • the one or more local gateways 110 are configured to transform the transaction information in the one or more common data formats into the one or more local data formats that are used by the local client application devices 105 associated with the local gateway 110 .
  • the transaction information from the one or more remote client application devices 105 can be communicated to the one or more local client application devices 105 for completing the transaction, regardless of the data formats used by each of the client application devices 105 .
  • each client can send and receive transaction information to and from other clients to perform inter-corporate, multi-enterprise automated business or other suitable transactions via the gateways 110 according to exemplary embodiments of the present invention.
  • MOIs can be set up to serve a wide range of transaction-specific communities, from some that are very large and global, such as, for example, the community of banks that need to process cross-border payment transactions, to small local communities such as, for example, a small regional medical community including doctors, pharmacies, hospitals, payers, and the like.
  • Each member in an MOI sends/receives standardized transaction information from/to an internal application that is meant to process that information.
  • the client application devices 105 can comprise these internal applications.
  • a more general architecture than the MOI is referred to as a Service-Oriented Architecture (SOA).
  • SOA is a peer-to-peer network comprised of nodes that can usually be divided into client-nodes, which consume the processing done within the SOA, and service nodes, which provide an identifiable, single-purpose function to support the transaction.
  • An MOI can be considered as containing a special, stylized distributed application—the “business transaction application” (BTA)—that a user has created to support a specific set of business transactions.
  • BTA business transaction application
  • the BTA is built by configuring and customizing the gateways 110 .
  • the system 100 is a fully-distributed application based on an SOA.
  • the clients of the BTA are the client application devices 105 that are creating, sending, receiving and processing the standardized information contained in the business transaction. This information is contained in a message, which is referred to here as a gateway message.
  • the structure and format of gateway messages exchanged between gateways 110 in a BTA is fixed and defined by the users.
  • the (local) client application devices 105 interact with a local gateway 110 through message queues.
  • the MOI can contain a number of specialized service applications that perform specific functions that support the execution of the given business transaction, such as, for example, authentication, coordinated time-stamping, logging services, credit checks, non-repudiation, data augmentation, routing services, and the like.
  • FIG. 2 is a diagram illustrating a gateway 110 , in accordance with an exemplary embodiment of the present invention.
  • the gateway 110 includes an information queue module 205 .
  • the information queue module is configured to communicate transaction information in one or more local data formats with the client application device 105 , although the information queue module 205 can be in communication with any suitable number of (local) client application devices 105 . In other words, the information queue module 205 is configured to handle messages coming from the (local) client application device 105 .
  • the gateways 110 use message queues that are referred to herein as “abstract queues,” as these abstract queues can standardize and abstract the interface between the gateways 110 and a wide variety of message delivery mechanisms. From the viewpoint of the gateway 110 , an abstract queue can pass the message the abstract queue receives from either the (local) client application device 105 or from other (remote) gateways 110 , and can receive messages from the gateway 110 to be sent either to a (local) client application device 105 or to a (remote) gateway 110 .
  • the gateway 110 can interact with an abstract queue through simple APIs, which contain a small amount of basic information about the message and a reference to the bytes that make up the message.
  • Each abstract queue can have an associated error queue on which are placed messages that are not able to be processed for some reason, along with an error message (e.g., in a fixed format) describing the error.
  • the error queues can be, for example, folders on the (local) gateway 110 where the files are placed.
  • Such an error queue is at a level higher than the delivery mechanism error queue, which is specific to the delivery mechanism. For example, if the delivery mechanism is a JMS message broker, and the message cannot reach the intended message broker queue, then the message will be placed in the message broker's error queue.
  • the gateway 110 instantiates a queue listener as part of an abstract queue.
  • the queue listener “listens” for or otherwise detects a message received by an abstract queue.
  • the respective queue listener can send a signal to the information queue module 205 or the communication module 245 when the respective queue listener has received or detected a message.
  • Such signals can be the event that begins processing by the gateway 110 .
  • An abstract queue has the general qualities of a queue—for example, the ability to add and remove items, to create a listener for the queue and the like—but is abstract in the sense that it “sits on top” of the details of the mechanism that is implemented to send and receive messages (either to the client application device 105 or to other gateways 110 ).
  • the implementation of an abstract queue can be a standard JMS-based message broker or MOM, a Web service, FTP, an API call to an end user application, a database query, or the like.
  • One aspect of the abstract queue is to loosely couple the delivery mechanism and the business transaction in the gateway 110 .
  • the gateways 110 can be adapted to whatever transport mechanism is in place and being used by the client application devices 105 .
  • abstract queue allows connection to the MOI using configuration tools, rather than requiring software coding.
  • a set of pre-built abstract queue adapters can be configurable simply by setting suitable properties. If changes in delivery strategy are required by a gateway 110 , changes can be made to a different abstract queue type and suitable properties can be set, rather than re-coding the gateways 110 .
  • the abstract queue properties can depend on, for example, the abstract queue type, which will be based on the particular client application device 105 . Some properties of the abstract queues include the abstract queue name.
  • Abstract queues are addressable entities within the gateway 110 , and can therefore use a unique (within the gateway 110 ) name to identify them.
  • the name can be any suitable designation or address, such a combination of alphanumeric characters, an IP address, or the like. For abstract queues for connecting with other gateways 110 , such a name or designation should be available to other gateways 110 for addressing purposes.
  • the abstract queues can support guaranteed delivery.
  • a delivery mechanism that does not support guaranteed delivery may require additional processing by the sending/receiving gateways 110 .
  • the gateway 110 can temporarily persist the message, wait for a callback that indicated the message was received (e.g., the message acknowledgment), and then delete the message from temporary persistent storage.
  • the gateway 110 can re-send the message, up to the maximum number of retries.
  • “alert” properties can be established (e.g., Time To Alert, Alert Destination, Alert Text), so that if no acknowledgment is received within a certain time, then an alert occurs.
  • the abstract queues can also include suitable listener properties.
  • the listener properties can define what the abstract queue is listening for, e.g., what is the triggering event.
  • the listener property can be the name of the folder where the abstract queue checks for new files.
  • the listener properly can be the queue where the abstract queue checks for messages.
  • the MOI architecture can support asynchronous transactions through the use of abstract queues at each gateway 110 . The arrival of a message at an abstract queue can be the trigger that causes the gateway 110 to process that message.
  • Such an architecture provides a simple, loosely-coupled interaction framework for building business transactions between participants.
  • abstract queues allow BTAs to be built on a wide, diverse set of message protocols, including legacy transports, e.g., FTP, direct leased lines, and the like. Consequently, BTAs should not entail the large changes in infrastructure required by other service-oriented solutions, such as, for example, ESBs and the like.
  • legacy transports e.g., FTP
  • direct leased lines e.g., ESBs and the like.
  • An abstract queue is a JMS-compliant message broker abstract queue. Such an abstract queue can encapsulate a standard JMS interface to a message broker.
  • Manta Ray one such open source product, can be used with the gateways 110 .
  • Manta Ray is suited for the fully distributed, decentralized nature of an MOI, as Manta Ray is fully distributed, i.e., all processing is done within the Manta Ray client and there is no central bus server.
  • Additional JMS-compliant abstract queues may be necessary, depending upon the application. For example, an abstract queue may be necessary for MQSeries message brokers, because of the widespread popularity of such a message broker in the financial community.
  • An abstract queue is an FTP abstract queue. For example, much business transaction information is sent and received through batch-oriented FTP processes.
  • An abstract queue can be used to encapsulate such a mechanism for moving information.
  • Two versions of the abstract queue can be used—one that treats the file to be sent or received via FTP as a single payload, the other that treats each record within a file as a separate payload.
  • other configurations of the FTP abstract queue can be used.
  • the FTP abstract queue can provide a significant amount of flexibility to the gateway 110 .
  • a (local) client application device 105 can send a file to an FTP-based abstract queue used by the information queue module 205 .
  • the abstract queue can then pass each record of the file as a payload to the information queue module 205 .
  • the records can be re-packaged by an FTP-based abstract queue used by the communication module 245 and sent using FTP to another gateway 110 .
  • the records can be sent as separate messages using, for example, a JMS-based abstract queue.
  • An FTP abstract queue can be set up at the gateway 110 that is directed to the (local) client application device 105 .
  • the FTP abstract queue can check a particular directory (defined by a property) to “listen” for incoming information.
  • the client application device 105 adds a file to the directory
  • the FTP abstract queue can activate the gateway 110 as though a message were added to a queue.
  • Certain header information can be provided to the FTP abstract queue, such as, for example, the transaction type, the message type, the recipient's address and the like.
  • the FTP abstract queue can combine such information (the message metadata) with the non-normative data (the message content) to create a message that can be processed by the gateway 110 , the last step of which is to place the message on a FTP abstract queue that is in communication with the other (remote) gateways 110 .
  • the “network-facing” FTP abstract queue can then send the file to the appropriate destination using the FTP protocol.
  • the FTP abstract queue can send the bytes via FTP to the destination, which can be simply a directory.
  • the destination gateway 110 can include an FTP abstract queue set up to listen on that directory.
  • the gateway 110 can act as though a message was received on a queue, and perform processing to reconstitute the file as a message that the gateway 110 can understand. At that point, subsequent gateway 110 processing begins, as discussed below. It should be noted that FTP can be used to batch together multiple messages in one file, and have the receiving gateway 110 reconstitute the file as individual messages.
  • An abstract queue is a direct-line abstract queue. Much of current inter-enterprise transactions between applications is performed between client applications at the users' locations and a large centralized server at a remote server location. These client/server systems generally use direct leased line connections.
  • the direct-line abstract queue can wrap the underlying direct line messaging protocol, allowing the gateways 110 to be used with such legacy systems.
  • a further example of an abstract queue is a web services/SOAP abstract queue.
  • Such an abstract queue can use SOAP to handle the transmission of a message.
  • these web service abstract queues can be used to handle Request/Response messages when specific queries need a direct response.
  • Many internal system messages can also utilize this type of abstract queue.
  • an instantiation of a web service abstract queue can handle interactions with the (local) client application device 105 that, for efficiency, can utilize the normative XML messages (discussed below).
  • An advantage of the MOI and architecture of system 100 is the ease of integrating the gateways 110 with internal applications and databases.
  • the database integration abstract queue can access the message payload to make it simpler for users to send or receive messages directly from/to an internal database.
  • the database integration abstract queue can map data from an internal database to its own version of the message payload object model.
  • the abstract queue can then create a normative message (as discussed below) for that payload and pass the message onto the gateway 110 .
  • Such a process would be reversed to receive and store a message into an internal database. Substantially all of the capabilities necessary to interact with the internal database are supported.
  • Such functionality can include support for any JDBC driver so that many forms of tabular data can be accessed. It should be noted that the integration to internal applications is separated from the central mapping in the gateway 10 , so that management of the MOI can be performed (including, for example, handling injection and versioning (discussed below)), without interfering with the local customization efforts undertaken by users.
  • the messages communicated between the (local) client application device 105 and the information queue module 205 can be referred to as “queue messages” or “raw messages.”
  • the queue (or raw) message is a message received from an abstract queue.
  • the queue message can be comprised of, for example, a minimal header and the message data.
  • the header in a queue message can be different than the header used for other message types used by the gateway 110 , as discussed below.
  • the queue header can include a minimal amount of information, such as which formatter to use (if needed), the message type, the transaction type, and other like information.
  • the header information can be imparted to the message via the abstract queue.
  • the message data in a queue message is simply an array of bytes. Nothing else need be assumed about the payload.
  • the formatter module 215 can transform the queue messages into corresponding non-normative information, such as, for example, XML messages.
  • the gateway 110 optionally includes a first custom-processor module 210 in communication with the information queue module 205 .
  • the first custom-processor module 210 is configured to process the transaction information using the one or more local data formats used by the (local) client application device 105 .
  • the first custom-processor module 210 is provided to allow users to add customized processing capabilities to the gateway 110 .
  • the user can configure the first custom-processor module 210 to perform a series of actions on the transaction information while that information is still in the local data format (e.g., add or modify the transaction information, re-format the transaction information, and the like).
  • a wide variety of local processing can be supported, such as, for example, data enrichment, complex business rule authorizations, and the like.
  • the first custom-processor module 210 can be responsible for executing a series of steps called an “action list” on the message content (or payload) that is in the local data format.
  • the first custom-processor module 210 can perform, for example, validation, enforce local security policies, perform data enrichment, and the like, as desired by the user.
  • An action list defines the steps that the first-custom processor module 210 follows for a message.
  • Action lists can be associated with a particular message type.
  • Action list templates can be provided that can be used as a starting point for users to configure their action lists. The user can configure the appropriate parameters for the action lists, such as, for example, by specifying queue names, log file names, and the like.
  • no software coding is necessary for performing such a configuration.
  • the action list can specify that certain steps are required or that certain steps can be skipped that are not required. Additional steps can be added to an action list at any time to extend the processing that occurs with the first custom-processor module 210 . There is no restriction on the sequence in which steps can be defined for processing. However, the user should ensure that the sequence of steps are proper and logical. Separate action lists can reside in each gateway 110 .
  • one or more predefined steps can be used to create an action list for the first custom-processor module 210 .
  • predefined steps can include, but are not limited to: validate the message content; create an entry in a local log file; send a different message (different message type), for example, to creates a new transaction; send the message to an enterprise-facing abstract queue (discussed below), which can trigger additional processing via another application, web service, or the like; store the message and its state in a repository associated with the gateway 110 ; and other like predefined steps.
  • Each step may have different properties defined.
  • the log step might have properties for the log file location, while the send reply step might specify the message type to send, and the like.
  • the user can create additional customized steps can be used when building action lists.
  • steps can be processed in the order in which they are defined in the action list, in a linear sequence.
  • conditional branching, forking and joining can also be used.
  • steps can be synchronous, meaning that processing is blocked until a step is complete, although asynchronous processing can also be used.
  • a step can be flagged as a long-duration step (not to be confused with long-running transactions) if the processing for that step is not expected to return immediately. For example, such flagging can enable the inclusion of manual processing, or some other process that takes hours or even days to complete. Note that this facility may provide the “look and feel” of an asynchronous process, but is actually a synchronous process.
  • the message state can be persisted to a repository associated with the gateway 110 (e.g., the data storage module 250 discussed below), and a “listener” process can be established to wait for a return from the sub-processing that was invoked.
  • Long-duration steps can include additional properties specifying, for example, the maximum time to wait and the error queue to notify if the sub-process exceeds such a limit.
  • the action list can define which of the following can happen when a step fails: all further processing stops, and another action (from a short list) may be invoked, such as sending the message to an error queue; a warning is logged (either directly in the repository or via an administrative message), and processing continues with the next step in the Local Processor action list; or the failure is ignored. Additional or alternative error events can occur when one or more of the steps to be performed by the action list fail.
  • the gateway 110 includes a formatter module 215 in communication with the first custom-processor module 210 (or the information queue module 205 if no first custom-processor module 210 is used or present).
  • the formatter module 215 is configured to transform the transaction information in the one or more local data formats into a data format associated with the gateway 110 .
  • the data format associated with the gateway 110 can be any suitable data format that can be used by the gateway 110 .
  • the data format associated with the gateway is referred to herein as “non-normative information,” and can comprise XML or the like.
  • XML will be used as an example of the non-normative information, although any other suitable data formats can be used for the non-normative information.
  • messages processed within the gateway 110 can be well-formed XML documents.
  • messages from the (local) client application device 105 can be in a variety of formats, e.g., EDI, a flat file, or any other proprietary or custom format.
  • the formatter module 215 is configured to transform messages from/to such external formats to/from a non-normative XML message that the gateway 110 can understand and manipulate.
  • the formatter module 215 can be responsible for performing a one-for-one “tokenization” or transformation of a non-XML message into an XML message (e.g., EDI to XML), and vice versa.
  • the formatter module 215 can transform a queue (or raw) message (e.g., non-XML) from the (local) client application device 105 into a non-normative XML message format that the gateway 110 can process.
  • the gateway 110 can process the resulting non-normative XML message, because the gateway 110 uses a map between the non-normative XML message and a normative data model.
  • the formatter module 215 can transform a non-normative XML message into a queue message (e.g., non-XML) that the (local) client application device 105 can process.
  • the formatter module 215 can support any suitable transformation to/from the non-normative information (e.g., XML), such as, for example, EDIFACT, X 12 , FIN (or, more generally, SWIFT non-XML (ISO 7775 )), fixed-length flat files, delimited flat files, FIX, and the like.
  • a non-normative XML message is a well-formed XML message that conforms to an XML model that is part of the gateway 110 application map.
  • the XML model is mapped to the normative data model (the object model).
  • the difference between a non-normative XML message and a normative message is two-fold.
  • a non-normative XML message is an XML message, while a normative message can be either an XML message or an instantiated message object.
  • the second difference is one of degree. Both messages are represented by an XML model in the application map, but the XML model of the normative message can be considered to be an exact or substantially exact representation of the normative data model.
  • the XML model of the non-normative XML message is a variation on the normative data model.
  • a non-normative XML message is the result of a one-for-one “tokenization” or transformation of a non-XML message into an XML message by the formatter module 215 .
  • the formatter module 215 takes the queue message (for example, EDI) and changes the form of the queue message to the non-normative information, such as XML or the like.
  • Producing a non-normative XML message is the first step in the process of creating a normative message.
  • Each non-normative XML message is defined by an XML model in the application map, which is mapped to the normative data model (the object model). From such a mapping, a normative message can be created.
  • part of the processing of the gateway 110 can involve converting a message into the correct non-normative XML message format so that it can be transformed by the formatter module 215 into a queue message.
  • each gateway 110 can support one or more formatter modules 215 , with each formatter module 215 supporting a separate transformation format.
  • a single formatter module 215 can support numerous transformation formats, with the appropriate format selected based on information in the queue message.
  • the header may indicate that no formatting is required (e.g., the message is already in the correct format for the gateway 110 to process), in which case the processing performed by the formatter module 215 can be skipped.
  • the non-normative message is passed to the (optional) second custom-processor module 220 .
  • the formatter module 215 For a message received by a gateway 105 , the formatter module 215 is invoked after the (optional) second custom-processor module 220 is finished. The message is changed from a normative message to a non-normative message so that the formatter module 215 can process it. In addition, the formatter module 215 and the format map to be used can be determined based on information in the message header of the received gateway message. The formatter module 215 then transforms the message from a non-normative XML message into a queue message that is appropriate for the client application device 105 .
  • the formatter module 215 can be a COTS product that can include a design-time component that can be used to create standard transformations that would be included as part of a service offering.
  • the formatter module 215 can optionally use validation to confirm the accuracy of the transformation. For example, if the (local) client application device 105 requires a different or more stringent data format than that required by other MOI participants, such validation can be included in the format map used by the formatter module 215 .
  • the gateway 110 can optionally include the second custom-processor module 220 in communication with the formatter module 215 .
  • the second custom-processor module 220 can be configured to process transformed transaction information using the data format associated with the gateway 110 .
  • the second custom-processor module 220 can be used to process the non-normative XML message transformed by the formatter module 215 .
  • the second custom-processor module 220 is provided to allow users to add customized processing capabilities to the gateway 110 .
  • the user can configure the second custom-processor module 220 to perform a series of actions on the transaction information while that information is in the non-normative XML format (e.g., add or modify the transaction information, re-format the transaction information, and the like).
  • the second custom-processor module 220 can be responsible for executing one or more action lists on the non-normative XML message before further processing.
  • the gateway 110 includes a mapping module 225 in communication with the second custom-processor module 220 (or the formatter module 215 if no second custom-processor module 220 is used or present).
  • the mapping module 225 is configured to convert the transaction information in the data format associated with the gateway 110 into a common data format that is shared with at least one other gateway 110 , using a normative data model configured to generate normative transaction information.
  • a normative message reflects the normative data model used by members of the MOI.
  • the normative message can be either an instantiated message object (or set of objects), or an XML message.
  • a normative message can be sent to and received from any other gateway 110 in the MOI.
  • the normative data model can be based on industry-sponsored initiatives, such as HL 7, FIX, SWIFT, RosettaNet, or the like, or can be defined as part of a new application.
  • the normative data model can use any suitable type of mapping that is configured to transform or otherwise map the non-normative information into the normative information that can be shared with and understood by all of the gateways 110 .
  • the normative data model is part of the application map that can be used by the gateways 110 to perform the transformation or conversion between the data of different formats.
  • An application map can include, for example, a main map file, which simply points to the other files, an object model, and one or more XML maps, each of which is comprised of an XML model and a mapping between that model and the object model.
  • the object model is the normalized data model for the gateway 110 .
  • the object model describes the message classes and their relationships.
  • the object model can also contain the validation rules used by the validation module 230 (discussed below), as well as the business transaction definitions, and other suitable information.
  • An XML map is comprised of an XML model and an object-model-to-XML-model mapping.
  • An XML map can be used by the gateway 110 to transform an XML message to an instantiated message object based upon a given XML model, and to transform an instantiated message object back to XML.
  • Such a facility allows the gateways 110 to handle multiple XML message formats that map to the same normative data.
  • the object model represents the normative information shared by all members of the MOI, but each member can use different XML schemas to represent that data in an XML message.
  • the gateway 110 can also include a validation module 230 in communication with the mapping module 225 .
  • the validation module 230 is configured to validate the normative transaction information.
  • the validation module 230 can validate the normative transaction information to ensure that the normative transaction information includes data required by mandatory data fields and cross-data field constraints.
  • validation is performed by the validation module 230 using validation rules specified by the user.
  • the validation rules are part of the application map that each gateway 110 uses to participate in the MOI to ensure that messages exchanged between members are valid according to the commonly-accepted validation rules of the members.
  • message validation is not a separate service performed as part of a process flow. Rather, each gateway 110 can validate any message. Such a mechanism can be contrasted with conventional approaches that require a central validation service that can become a process bottleneck, or that include a separate validation service as part of a process flow.
  • validation can also be one of the steps that can be invoked by the action lists used by the first and second custom-processor modules 210 and 220 , respectively.
  • the user can define when the validation should be invoked, in addition to the validation performed by the validation module 230 when sending a message. Since action lists are defined on a per message type basis, such a mechanism allows for validation to be invoked for one message type but not another. The user can also make validation an optional step for certain message types and a required step for others.
  • the validation performed by the validation module 230 can be referred to as “local validation,” since the rules are defined and maintained for a particular gateway 110 , rather than globally for all gateways 110 . Local validation is generally not less stringent than global validation.
  • the validation rules are part of the application map.
  • the validation rules are associated with the normative data model (the object model), which is the “hub” of that map, rather than with the XML schemas to which the object model is mapped.
  • the validation module 230 validates the objects, not the XML. Such an approach allows for more comprehensive data validation than is possible using an approach that simply validates XML against XML schema. In particular, the latter approach, as used by conventional architectures, cannot handle cross-field validation (for example, if Field A is null, Field B must be greater than $1,000). In contrast, the validation module 230 is capable of performing cross-field validation.
  • Cross-field validation is a very common requirement for validating messages, but because it cannot be handled by validating against XML schema, it is generally handled by the business logic layer in conventional architectures.
  • the validation approach used by the validation module 230 can, therefore, extend data validation into the realm of business rules to allow more business rules to be handled by simpler validation rules.
  • the validation rules used by the gateway 110 can be of two types: field-level validation rules, that define the allowable data and format for a specific field; and cross-field validation rules, that can validate the data/format of one field in a message instance against the data/format of another field, as well as against global system values such as current date/time and the like.
  • Validation rules can use regular relational (>, ⁇ , and the like) and logical (AND, OR, NOT and the like) operators, as well as parenthesis for grouping.
  • arithmetic operators (+, ⁇ , * and /) can be used, as well as special operators such as “ISNULL”, “:” and the like.
  • a selected set of string, numeric, and Boolean functions can also be used to build the validation rules.
  • the gateway 110 can include a data enrichment module 235 in communication with the validation module 230 .
  • the data enrichment module 235 is configured to customize the validated normative transaction information to generate enriched normative transaction information.
  • the data enrichment module 235 can be used by the user to add, modify or otherwise customize, in any suitable manner, the normative transaction information that has been validated by the validation module 230 .
  • the data enrichment module 235 can be used to add the four digit add-on code (identifying a geographic segment within the five digit zip code delivery area) to a five-digit zip code or the like.
  • the data enrichment module 235 does not alter the validated normative transaction information in such a way as to make the data unusable by or unshareable with other gateways 110 . Rather, the data enrichment module 235 can be used to augment the validated normative transaction information to include additional (normative) information that can be shared with other gateways 110 and, ultimately, used by the (remote) client application devices 105 .
  • the gateway 110 includes a message processing module 240 in communication with the data enrichment module 235 .
  • the message processing module 240 is configured to generate a transaction or gateway message by providing an envelope for the (validated and possibly enriched) normative transaction information in the common data format. Transaction information is encapsulated in a message, in particular, a gateway message.
  • the message processing module 240 is further configured to execute predetermined next actions and processing demands that can be imposed by at least one other (remote) gateway 110 (e.g., to include information in the message that is expected by the (remote) gateway 110 ).
  • a message is comprised of an envelope that contains blocks of information.
  • the envelope has a small set of information including, for example, a unique ID for a message and certain other information that will permit the gateway 110 to process it.
  • the blocks contain the various sets of information that comprise the message.
  • One block type is the payload that contains the transaction information that is to be transmitted from an initiator to a target.
  • Other blocks can contain information to support processing by the gateway 110 , such as, for example, transmission, persistence, security and the like.
  • blocks can include information about the target's address, message security, and the like.
  • Two exemplary blocks that can be used in a message are: 1.) the transaction routing slip that defines the path the message is to follow in the MOI as it goes from initiator to target; and 2.) the message processing history that keeps a running record of all state changes incurred by the message, for example, visiting an intermediate service, and the like.
  • the envelope is a wrapper that is used to bundle the normative transaction information for transmission to other (remote) gateways 110 and the associated (remote) client application devices 105 .
  • the blocks other than the payload can be considered a message header for the gateway message.
  • FIG. 3 is a diagram illustrating a gateway message 300 , in accordance with an exemplary embodiment of the present invention.
  • the gateway message 300 comprises the message data 310 (payload or message content), message metadata 305 (header or message context), and, optionally, a message network header (e.g., as part of the message metadata 305 ).
  • the message data 310 is comprised of instances of classes from the application domain model (i.e., the application map).
  • the message data 310 can exist in a local data format (i.e., the data format used by the (local) client application device 105 ).
  • the message data 310 can also be encrypted when sent over the network.
  • the message metadata 305 is comprised of a set of user and system information that accompanies the message data 310 .
  • Some of the message metadata 305 can be supplied by the user (such as an addressee).
  • Other data elements can be supplied by the gateway 110 through the message processing module 240 , such as, for example, a unique message identifier, a timestamp, transaction context, and the like. Both users involved in a transaction (the local and remote client application devices 105 ) can view and otherwise use the metadata information.
  • the metadata information can be stored with the message data 310 in local data storage.
  • the optional message network header can be comprised of a set of system-generated information that is used by the communications layer to properly deliver the message.
  • the message network header is generally not visible or accessible to either users involved in a transaction, and does not have to be persistent. Some or all of the information in the message network header can be derived by the message processing module 240 from, for example, the message metadata 305 .
  • each message can include a unique message identifier, generated by the message processing module 240 of the originating gateway 110 .
  • a message identifier can be guaranteed to be unique within the MOI.
  • the message identifier generated by the message processing module 240 is independent of any message identifier generated by the communications infrastructure.
  • the system 100 can support itinerary-based routing for messages. In other words, messages can be routed based on the business transaction definitions created by the users. These definitions can define the central services through which a message passes for a given message type and transaction type.
  • the itinerary is carried with the gateway message 300 in one of the header blocks of the message metadata 305 as the gateway message 300 travels through the system 100 .
  • the itinerary can be declared as a linear sequence of gateways 110 through which the gateway message 300 passes until the gateway message 300 reaches its destination.
  • the system 100 can also support content-based routing.
  • a gateway 110 can make decisions on where a message is to be routed based on the contents of the message.
  • the message processing module 240 can use message header-based routing, in which the message processing module 240 determines the next leg of the route based on information in a specific message header block.
  • the message processing module 240 is also responsible for processing the header blocks in the message envelope when a message is received from a network-facing queue listener.
  • the message envelope can be an XML document comprised of blocks of data. Each block can include a corresponding class that processes the block. Blocks can be processed in a particular sequence, if desired.
  • the message envelope structure and the processing of the blocks can be the same for all messages exchanged among members of the MOI. For example, a configuration file can define the association between each message header block and the class that processes the message header block.
  • the gateway message 300 can include several types of blocks.
  • the message metadata 305 can include one or more predefined header blocks 315 , which include header information that cannot be customized or extended by the user, and one or more user-defined header blocks 320 , which include header information that can be customized and extended by the user.
  • the message data 310 can include one or more predefined content blocks 325 , which include message content that cannot be customized or extended by the user, and one or more user-defined content blocks 330 , which include message content that can be customized or extended by the user.
  • the normative transaction information can be contained in the user-defined content blocks 330 of the gateway message 300 .
  • any block can be an indirect link (e.g., using XLINK/XPATH or the like).
  • an indirect link By using an indirect link, much of the content of a message need not be in the message itself.
  • Such indirect links can be used, for example, for an often re-used routing slip, a very large payload that is actually a file to be FTP'ed, and the like.
  • Table 1 illustrates some of the types of information that can be included in the predefined header blocks 315 and the user-defined header blocks 320 , although additional and/or alternative information can be included in the message metadata 305 .
  • TABLE 1 Information in Predefined and User-Defined Header Blocks 315 and 320 Predefined or Block Description
  • User-Defined Message ID Uniquely identifies a message Predefined and its context. Includes message type, message ID, transaction ID, date/time created, message category (from several defined, e.g., business message, administrative message). Security For message authentication and Predefined encryption. Any message block can be signed and/or encrypted, and the digests are added to the Security block. Processing Date/time sent/received.
  • Each Predefined History gateway 110 updates the history and block as the message is User-Defined processed, so messages contain a record of where they have been and how they have been processed. The history can be included in the message acknowledgment which is returned to the original sender.
  • Message Message processing flags User-Defined Processing determine additional processing Flags for a message, e.g., processing for potential duplicate emission, non-repudiation, not-valid warning, and the like. The classes for these message processing flags are provided by the user.
  • Routing Routing slip specifies the User-Defined gateway 110 itinerary (e.g., addressing and routing information), including central services and the final recipient. The itinerary is associated with the message type and the transactions defined for it.
  • the routing slip can specify the entire route and the reply-to address, but at a minimum preferably specifies the next step and final destination. There can be arbitray number of steps before reaching the final destination. Custom To handle other processing as User-Defined needed.
  • the message metadata 305 can include the message processing history for the gateway message.
  • a history of that change can be stored in the message processing history.
  • Such changes in state can include, for example, when a message is accepted by a gateway 110 from an abstract queue, when a message is sent to an abstract queue, when a message is transformed in any way, and the like.
  • Message processing histories are used by the gateway 110 to understand the precise state of a gateway message 300 that it has received.
  • the combination of the routing information and the message processing history provides information that can be used by the gateway 110 to understand what processing is required to accomplish the next step in the transaction.
  • the message processing history can be comprised of individual information components (e.g., separate processing events), and the gateway 110 can be configured to process individual information components of the message processing history.
  • the message processing history can also include a history of the transaction to which the transaction information is directed.
  • a transaction can comprise a compound transaction, e.g., a multi-step transaction made up of simple (binary or one-step) transactions.
  • exemplary embodiments of the present invention can suspend and resume a compound transaction as required by the business needs of the users.
  • a compound transaction can be suspended until a predetermined condition is met.
  • the predetermined condition can be a time limit (e.g., the transaction is suspended until a certain amount of time has passed) or the like. The transaction can be resumed once the predetermined condition is satisfied.
  • users can determine the status of individual components of the compound transaction and exchange the status information, as needed, for completing the transaction.
  • the system 100 can process or otherwise execute the individual components of the compound transaction either sequentially or in parallel.
  • the routing information contained of the envelope can define the high-level process flow of the transaction, such as the addressing and routing information for the gateway message 300 .
  • the routing information can specify the message itinerary (e.g., the gateways 110 through which the message will pass) and the acknowledgment behavior.
  • the itinerary can be specified declaratively as a linear sequence of steps. For example, an itinerary can be specified as follows:
  • Step 1 “Send the message from ⁇ origin address ⁇ to ⁇ Service 1 address ⁇ ”
  • Step 2 “Send the message from ⁇ Service 1 address ⁇ to ⁇ destination address ⁇ ”
  • Step 3 “Send ACK from ⁇ destination address ⁇ to ⁇ origin address ⁇ ”
  • each gateway 110 does not specify what occurs at each gateway 110 .
  • the behavior of each gateway 110 can be determined by the message processing module 240 and the first and second custom-processors 210 and 220 of each gateway 110 , which, in turn, are based on the message type and other message metadata.
  • the routing can support a linear process. Alternatively or additionally, the routing can support forks, joins, or conditional processing behavior. The end point of a given step is considered to be the starting point of the next step.
  • the routing information can be changed by intermediate gateways 110 to allow for dynamic routing in which each gateway 110 can determine the next message hop.
  • Each block in the gateway message 300 can be encrypted using any suitable form of encryption. Descriptive information on the type of encryption of each block can be included in a block in the message metadata 305 . By encrypting individual blocks, a gateway 110 or a module within the gateway 110 can read a header block containing information for it, while not being able to read the contents of a block of message data 310 . Additionally, for a PKI-based encryption system, each block in the gateway message 300 can be individually, digitally signed. Digitally signing the blocks uniquely identifies the signer, incorporates a precise time and date stamp, and can guarantee that none of the content of the signed block has been changed or otherwise altered. Descriptive information of the digital signature of each block can be included in a block in the message metadata 305 .
  • the message processing module 240 can validate the signatures for any signed blocks in the gateway message 300 .
  • the message processing module 240 can also determine whether any encrypted blocks are intended for the current gateway 110 , and if so, can be read. By default, signed/encrypted blocks that are not intended for a gateway 110 cannot be modified by that gateway 110 . Conversely, blocks that are not signed or encrypted can be modified by any gateway 110 . If a gateway 110 modifies a signed/encrypted block that is not intended for it, then the processing associated with that block can leave the original block and signature as is, make a copy of it, modify the copy, and sign the copy.
  • the gateways 110 include one or more communication modules 245 in communication with the message processing module 240 .
  • the communication modules 245 are configured to communicate the gateway message with at least one other (remote) gateway 110 for completing the transaction.
  • the communication modules 245 can be in communication with the communication modules of other gateways 110 using any suitable communication link 247 (e.g., either wired or wireless) and any suitable transmission protocol (e.g., TCP or other suitable network communication protocol).
  • the communication modules 245 are also configured to receive gateway messages provided by the at least one other (remote) gateway 110 for completing the transaction.
  • the communication modules 245 are responsible for signing and encrypting a gateway message that is to be transmitted to another (remote) gateway 110 .
  • the communication modules 245 are also responsible for “finalizing” the gateway message before the gateway message is passed to the abstract queue for transmission. For example, the communication modules 245 can resolve references to the addresses of other gateways 110 , including determining the address of the next destination. The communication module 245 is also configured to send message acknowledgments, if required.
  • the communication modules 245 are further configured to record transmitted and received gateway messages and the transaction states of the transmitted and received gateway messages. For example, the communication module 245 can notify the information queue module 205 (using any suitable type of signal or event notification) and the (local) client application device(s) 105 that a gateway message has been transmitted. Receipt of a gateway message by the communication module 245 can be the event or signal that begins processing of the gateway message by the gateway 110 for communication of the transaction information contained in the gateway message to the (local) client application device 105 . Such processing of the received gateway message would be in a substantially reverse order to that which is performed for processing transaction information from the (local) client application device 105 to generate and transmit a gateway message.
  • the gateways 110 are configured to support security standards such as, for example, Public Key Cryptography Standards (PKCS), suitable IETF standards (e.g., X. 509 certificates, S-MIME, and the like), secure transport protocols (e.g., SSL and TLS), XML Encryption and XML Signature, conventional cryptographic algorithms, including encryption (e.g., RSA, 3-DES, and the like), digest (e.g., SHA, MD5, and the like), and message authentication codes (e.g., MAC, HMAC and the like), and other like security standards.
  • PKCS Public Key Cryptography Standards
  • suitable IETF standards e.g., X. 509 certificates, S-MIME, and the like
  • secure transport protocols e.g., SSL and TLS
  • XML Encryption and XML Signature e.g., conventional cryptographic algorithms, including encryption (e.g., RSA, 3-DES, and the like), digest (e.g., SHA, MD5, and the like
  • the gateways 110 are also configured to support message authentication and encryption from a level of no security (e.g., if using leased lines or working with low-value messages), to self-signed certificates, to public key infrastructure (PKI).
  • a level of no security e.g., if using leased lines or working with low-value messages
  • PKI public key infrastructure
  • the system 100 does not impose a security model on the users. Rather, the users can choose to use any of these or other security models, or none at all. However, once a model is chosen, all gateways 110 preferably comply with that security model.
  • the system 100 can support several models for authenticating/encrypting messages, including, for example, self-signed X. 509 certificates and PKI.
  • the system 100 can use self-signed certificates for performing authentication and encryption.
  • the self-signed certificates model is similar to the PKI model, except that there is no trusted third party (e.g., a certificate authority (CA)) that validates the certificates.
  • CA certificate authority
  • a sender creates the private key and the certificate with which the corresponding public key is broadcast, but the identity of the sender is not verified by a third party.
  • Such a model implies that there is some level of trust between parties that is established outside of the CA. For example, the parties might communicate via a secure leased line, or validate certificates out-of-band (e.g., through e-mail or the Web).
  • a PKI binds public keys to entities, enables other entities to verify public key bindings, and provides the services needed for ongoing management of keys in a distributed system.
  • PKI ensures that the entity identified as sending the transaction is actually the originator, that the entity receiving the transaction is the intended recipient, and that data integrity has not been compromised.
  • a certificate binds an identity (Distinguished Name or DN) to a public key. Information encrypted with the public key can only be decrypted with its corresponding private key, and vice versa.
  • the sender's gateway 110 would require a private key, held securely locally with the gateway 110 , and a certificate with which the corresponding public key is broadcast.
  • the key pair can be generated while creating a certificate application, which, when completed, is sent to the CA associated with the local user. It is the responsibility of the CA to verify the applicant's identity, to maintain a Certificate Revocation List (CRL) and to publish a list of valid certificates by Distinguished Name (DN). When the CA has satisfied its verification requirements, the certificate is sent to the gateway 110 and added to the list of valid certificates maintained by the gateway 110 .
  • CTL Certificate Revocation List
  • DN Distinguished Name
  • the list of valid message recipients for a given gateway 110 can be maintained and published by the CA associated with the (local) user.
  • the gateway 110 can maintain a cached copy of such a list. Before each time the list is used, the gateway 110 can ensure, via a suitable communication link with the CA, that the list is up-to-date.
  • the list can be made available to the (local) client application device 105 , via the gateway 110 , for presentation to the user while selecting the message recipient.
  • the decision about which message blocks, if any, to sign or encrypt and under what conditions is controlled by the users. More particularly, such information can be part of the envelope definition that is distributed to all members of the MOI.
  • the signing/encryption can be specified as being either mandatory, optional or not allowed.
  • Signing data includes encrypting the data digest with a private key associated with a certificate.
  • the gateways 110 can be configured to support the ability to sign only a portion of the data in a message. For example, particular blocks of data in an XML message (e.g., header blocks or payload blocks) can be signed.
  • the standard security processing generally prohibits a signed message block from being changed by any intermediate gateway 110 . However, if it is necessary for an intermediate gateway 110 to change signed message blocks, a copy of the original message block can be included in the message (along with its signature), then changes can be made to the copy and the copy signed.
  • Encrypting data generally includes the generation of a symmetric key, encrypting the message data with that key, and then encrypting the key with the public key of the intended recipient.
  • the gateways 110 can be configured to support the ability to encrypt specific blocks of data in an XML message. However, the security block of a message will not be encrypted.
  • certain processing occurs before a secure message is transmitted.
  • processing can be performed by the communication modules 245 , and can include the following, for example: acquire the certificate for the sender; look up the certificate for the recipient; validate the certificate; sign the gateway message or selected parts thereof; and encrypt the gateway message or selected parts thereof. Additional and/or alternative steps can also be performed by the communication modules 245 and/or the message processing module 240 .
  • the message processing module 240 or the communication modules 245 can process the gateway message in, for example, the following manner after the gateway message is passed from the associated queue listener: extract the certificate from the gateway message; validate the received certificate; validate the gateway message signature; and if encrypted, decrypt the gateway message or the encrypted parts thereof.
  • the various modules of the gateway 110 can then process the decrypted gateway message to pass the transaction information to the (local) client application device 105 .
  • Each gateway 110 can include a keystore that is configured to store the private key of the sender, as well as certificates for other (remote) gateways 110 with which the (local) gateway 110 can communicate.
  • a keystore can be kept up-to-date to reflect additions/deletions of participants from the list of possible message recipients, and to reflect changes to individual certificates (e.g., when a certificate expires).
  • the keystore can be maintained and accessed differently, depending on whether the MOI is using self-signed certificates or PKI.
  • the certificate for the new gateway 110 is distributed to all participants who are allowed to exchange messages with the new gateway 110 .
  • the keystores of those participants are then be updated with the new certificate.
  • the gateways 110 can create the certificates and have the certificates distributed to all the other participating gateways 110 (e.g., through a centralized distribution facility) so that the keystores of those gateways 110 can be updated.
  • the CA is the trusted third party responsible for vetting and confirming the identities of the gateways 110 .
  • the CA can provide a central location for certificate storage and distribution.
  • the gateways 110 use the abstract queues to send and receive messages.
  • the abstract queues can be responsible for message transport security. For example, if a JMS message broker using SSL is used, then such a transport security mechanism is abstracted from the gateway 110 processing, given the nature of the abstract queues. Thus, the gateway 110 simply places a message on the abstract queue, and the abstract queue will perform all necessary subsequent processing to ensure the message transport security.
  • the system 100 is also configured to support non-repudiation of delivery for gateway messages.
  • Non-repudiation of delivery provides proof that the recipient received a gateway message, and that the recipient recognized the content of the gateway message (e.g., the message could be understood by the receiving gateway 110 , although this does not necessarily imply that the gateway message could be understood/consumed by the (remote) client application device 105 ).
  • the security model for the gateways 110 can use self-signed X. 509 certificates or the like to achieve non-repudiation, which does not involve the services of a CA. Such a model can provide a base level of non-repudiation of delivery.
  • the gateways 110 can be enabled and configured for PKI security, which requires a CA. Whichever level is selected, non-repudiation can be provided without using a central service. In such a scenario, non-repudiation can be provided by the combination of digital signatures and timestamps included on transactions messages. With the addition of PKI, such signatures are vetted by the certificate chain that includes a trusted root (the CA).
  • a central service can be added, where gateway messages marked for non-repudiation can automatically pass and be recorded in a central archive.
  • Such a scenario can add some amount of processing overhead, but also offers a non-repudiation resolution service in which all records are easily accessible, storage can be rigorously controlled, and the like.
  • such functionality can be provided without using a central service.
  • the storage of gateway messages is scattered over a number of member repositories, some of which might have archived messages to offline storage, collecting the records required to prove non-repudiation may become somewhat more challenging. Nevertheless, storing gateway messages in member repositories only, as opposed to a central archive, assures that each member controls its own repository and need not entrust the control of storing gateway messages to a third party overseeing the central archive.
  • the gateway 110 includes a repository or data storage module 250 in communication with the gateway 110 .
  • the data storage module 250 which can also be referred to as a data store, is configured to store information transmitted and received by the gateway 110 , and any other information maintained by the gateway 110 .
  • the data storage module 250 can be used to enable reporting on the state of any gateway message.
  • the communication modules 245 can store the gateway message in the data storage module 250 after final processing of the gateway message is completed and before placing the gateway message on the appropriate abstract queue.
  • the appropriate queue listener can store the gateway message in the data storage module 250 before processing of the message begins.
  • the information queue module 205 can update the message (e.g., the status of the message) before the associated transaction information is communicated to the (local) client application device 105 .
  • the database storage module 250 can comprise any suitable type of computer database or computer storage device that is capable of storing data. However, the structure of the database storage module 250 can be based on the object model, which is the normative data model that is used by all members of the MOI of system 100 .
  • the data storage module 250 can also contain the information necessary for the gateway 110 to operate. However, each of these local data storage modules 250 is, in aggregate, an integral part of the BTA, as the data storage modules 250 are where the data for the BTA can be stored. While the information in the data storage modules 250 can be accessible and of interest to the (local) client application device 105 being serviced by the gateway 110 , the format and schema of the data storage module 250 can be defined in the process of creating a BTA.
  • the data storage module 250 can persist message and payload states until the transaction with which they are associated is complete.
  • the state of a gateway message can change as a result of, for example, processing by the gateway 110 .
  • the receipt of a gateway message by the receiving gateway 110 can trigger an acknowledgement to the sending gateway 110 .
  • Such an acknowledgement can be associated with the sent gateway message, and result in a change in the reported state of the (received) gateway message.
  • Queries of the data storage module 250 can provide reports on the state of gateway messages and transactions that have been processed by a gateway 110 .
  • the message and payload information persisted in the data storage module 250 can be retained until such information is explicitly removed.
  • the data storage module 250 is both a cache and a persistence mechanism, handling the ever-changing stream of information being processed by the gateway 110 , as opposed to a more traditional database, which stores information permanently for later retrieval.
  • the data storage module 250 can also hold any or all metadata needed by a gateway 110 , such as the XML schemas associated with message payloads, the maps used to transform messages, and the like. Additionally, since the data storage modules 250 associated with each gateway 110 can provide data storage in the aggregate for a BTA, the data storage modules 150 can also be used to store other information in addition to persisted gateway messages. In particular, such additional information can include a wide variety of setting and configuration files. Also, the data storage modules 250 can contain information that can be used to monitor activity of a local gateway 110 or to monitor the BTA as a whole.
  • the data storage modules 250 are further configured to support “data frame” functionality.
  • the data frame provides a mechanism for cutting and/or copying datasets from the data storage module 250 and preserving these datasets as, for example, a large XML document or other like data format.
  • the gateways 110 can access such data frames using the same interface used to read data from the data storage modules 250 .
  • import capabilities allow information within the data frame to be imported into the data storage module 250 .
  • data frames can be used for secondary back-up and restore. The primary back-up can rely on the conventional back-up capabilities of the database used by the data storage module 250 .
  • the data frames can also be used for secure archiving.
  • Such a feature involves cutting data from the data storage module 250 , signing the “cut” data and storing such signed data as an XML document.
  • the archived data can be read (by those that have permission) at anytime without the need for any special program.
  • the data frames can further be used for bulk transmission of information stored in the data storage module 250 .
  • any query into the data storage module 250 can become a data frame that can then be sent as the payload in a gateway message to another member in the MOI or sent externally as an XML document.
  • the data frames can be used for the transmission of metadata sets. Metadata can be expressed in XML documents and stored. The distribution of metadata can be accomplished by creating appropriate data frames of such metadata for distribution to and processing by the gateways 110 .
  • the data frames can also be used for signed, complete self-contained messages.
  • gateway message with all of the information relevant to that gateway message including, for example, the original version of the message, any local transformations, the XML schema defining the payload, message history, and the like. All such information can be captured as a data frame, signed for robust non-repudiation, and sent as the payload of a gateway message.
  • the data frame functionality can be used for other processing in conjunction with the data storage module 250 .
  • the security of the data storage module 250 can be performed using the trusted database account principle. Such a principle means that a fixed user account is used to access the data stored in the data storage module 250 , but the user will not be able to manipulate or access the database directly.
  • the gateway 110 can access the database using a user ID and password that can be encrypted and stored within a local configuration file stored in the gateway 110 .
  • the user ID and password can be generated by the installer when the gateway 110 is installed for the first time.
  • the gateway messages stored in the data storage module 250 do not need to be encrypted. However, the transactions messages can be encoded. Such encoding allows any Unicode characters to reside in the gateway message body without restrictions. For example, Base 64 encoding can be used, although any suitable encoding scheme can be used.
  • a signature can be stored together with each gateway message in the data storage module 250 to ensure data integrity.
  • the signature can include a digest of the gateway message (such as a CRC, MD 5 or the like), and be encrypted with the private installation key.
  • the private installation key can be generated when the gateway 110 is installed for the first time, on a per installation basis, and stored securely.
  • the generated key can be encrypted with a static private key internal to the gateway 110 , and stored in several locations, such as, for example, a special table in the data storage module 250 , a settings file and the like.
  • the gateway 110 can check the signature each time the gateway 110 opens a gateway message from the data storage module 250 . If the gateway message was tampered with, the gateway can log an entry in a log file and cancel the opening of the gateway message in question.
  • the data in an archive can comprise one (perhaps large) XML file (or other suitable data format) containing all or substantially all of the archived gateway messages, and any relevant records used by those gateway messages. Both gateway messages and data can be Base 64 encoded or the like. Although the data in the archive can be encrypted, there is no requirement to do so.
  • a checksum can be computed using, for example, the SHA algorithm or other suitable checksum algorithm.
  • the archived data file and the digest can then be compressed together in, for example, a ZIP file or the like for storage or for transmission to another site, for example, for offsite storage.
  • the digest of the archived data file can be calculated and compared with the decrypted checksum stored in the ZIP file. If the two do not match, the restore operation can be aborted, and the appropriate security violation logs can be written.
  • the system 100 can include a transaction administrator 115 .
  • the transaction administrator 115 can be in communication with each or any of the gateways 110 in the system 110 .
  • the transaction administrator 115 can be used to measure and maintain the gateways 110 .
  • the transaction administrator 115 can also be used to monitor any suitable statistics of the gateways 110 (e.g., number of messages sent and received by each gateway 110 , errors, disk reads/writes from/to data storage modules 250 , and the like). Any suitable number of transaction administrators 115 can be used in the system 110 to maintain and monitor the gateways 110 .
  • the transaction administrator 115 can be comprised of a gateway 110 with the administrative capabilities to configure, measure, monitor, maintain and otherwise govern the other gateways 110 in the system 100 .
  • the transaction administrator 115 can be configured to administer and update each gateway 110 via automated administrative messages, a process referred to herein as “injection.” Thus, the transaction administrator 115 can distribute updates to each or any gateway 10 using suitable administrative messages.
  • the administrative messages can be of the same structure as the gateway messages, such as the structure of gateway message 300 illustrated in FIG. 3 . Any suitable feature of the gateways 110 can be updated independently through injection, including, for example, the object model, the XML model, the mapping between the object model and XML model, business transaction definitions, global validation rules, envelope processing configuration, abstract queue implementations, local processing action lists and associated classes, formatter maps (includes local validation), configuration files, map and configuration file structures, and the like.
  • any custom processing performed in the gateways 110 can be updated using appropriate administrative message sent from the transaction administrator 115 .
  • the administrative messages like the gateway messages, can provide a definable block in the envelope of the administrative message that is configured to provide parameters for the customized processes.
  • the features of the gateways 110 can be updated using suitably-encrypted secure administrative messages.
  • the administrative message are configured to utilize message security in a manner similar to that used in the gateway messages (e.g., individual blocks can be encrypted and signed, and the like).
  • the transaction administrator 115 can be configured to query one or more gateways 110 to ascertain the status of a transaction, using the unique transaction ID tags, envelope ID tags, message ID tags or other identifying information contained in a gateway message.
  • the administrative messages used by the transaction administrator 115 can also be used to query any data stored in any data storage module 250 associated with any gateway 110 .
  • the gateways 110 include processing that can ensure reliability in case of failure.
  • the gateway 110 can achieve such reliability by using checkpoints at various points of the process between the modules of the gateway 110 .
  • a checkpoint is a transactional boundary that verifies the message is ready for the next step.
  • a checkpoint sends a signal to the prior checkpoint indicating that the message was successfully processed. The prior checkpoint can then remove that message from whatever storage mechanism was used. If an error condition occurs along the way to the next checkpoint, or a timeout occurs and the message never reaches it, the whole transaction is rolled back to the state of the message as it existed at the prior checkpoint.
  • a checkpoint can be located in the information queue module 205 at the interface to the client application device 105 .
  • a failure that occurs before this point can be handled by the abstract queue used to communicate with the client application device 105 .
  • a checkpoint can be located at the output of the communication module 245 . Failure before this point can roll the message back to the state it was in at the checkpoint for the information queue module 205 .
  • the gateway message can be stored in the data storage module 250 .
  • failure before this point can roll the message back to the state it was in at the checkpoint at the output of the communication module 245 of the sending gateway 110 , that is, to the state of the message when it was sent (which is persisted in the data storage module 250 of the sending gateway 110 ).
  • the gateway message If the gateway message is received correctly, processed, but fails at the checkpoint for the information queue module 205 (i.e., before the transaction information is passed to the client application device 105 ), the message can be rolled back to the state it was in when received (i.e., at the checkpoint of the communication module 245 ). It should be noted that when a gateway message is passed to an error queue, the transaction is considered to be complete.
  • the universe of message exchanges that can be used in a BTA is defined by business transactions that can be described utilizing activity diagrams.
  • activity diagram is graphic way of describing the interaction between objects or processes.
  • the activity diagram can describe the interaction between gateways 110 .
  • Each business transaction starts by an initiator client application device 105 placing a message (transaction information) on a queue.
  • the message is processed by the gateway 110 and then placed on the abstract queue associated with the communication module 245 to be picked up by one or more target gateways 110 for use by the (remote) client application device 105 .
  • nested transactions need not be used by the system 100 .
  • the reason for this is that a compound transaction can be suspended with all its states and then resumed, as discussed previously. Such a mechanism renders nested transactions unnecessary.
  • Such a capability can keep transactions smaller and simpler, and can allow a more arbitrary and dynamic aggregation of basic transactions.
  • the set of business transactions supported in a BTA can be expressed through stylized UML activity diagrams.
  • the business transaction definition determines the entire route of a message. It can be visualized as an activity diagram showing either a one-step transaction or a Request/Response.
  • FIG. 4 illustrates a one-step transaction using an activity diagram, in accordance with an exemplary embodiment of the present invention.
  • a message exchange occurs from A to B that passes through two central services, s 1 and s 2 .
  • the business transaction definition specifies a central service gateway 110 , s 1 , as the next destination.
  • the next destination can be a credit check service, an audit repository, or the like.
  • the service is specified generically, and it is up to the gateway 110 to resolve the actual endpoint address of the service before the message is sent.
  • the business transaction definition used for a particular message and transaction type can be the same at all gateways 110 .
  • Such commonality makes it possible to resolve addresses in two ways: 1.) the initiator can determine all of the addresses at the outset and specify them within the routing block of the message header; or 2.) each gateway 110 can specify the address of the next gateway 110 . As discussed previously, the address resolution is performed by the communication module 245 .
  • a message acknowledgment is an administrative message sent from one gateway 110 to another gateway 110 indicating positive receipt of a gateway message. It should be noted that negative acknowledgments are always sent if there is a delivery failure or other error.
  • a business acknowledgment can contain any suitable type of acknowledgment information about the original message, such as, for example: the message ID block, which provides unambiguous identifying information about the message; and the history block, which includes a record of each gateway 110 where the message has previously stopped.
  • the business transaction definition can specify the business acknowledgment behavior. There should be at least one business acknowledgment in a business transaction definition. When a gateway message reaches a destination on its itinerary, the business transaction definition can specify one or more gateways 110 that should receive a business acknowledgment. The gateways 110 that were part of the message's route can be sent a business acknowledgment.
  • FIG. 5 illustrates a one-step transaction with a business acknowledgment, using an activity diagram, in accordance with an exemplary embodiment of the present invention.
  • a one-step transaction from gateway A to gateway B occurs.
  • a business acknowledgment 505 is sent from the destination (B) to the origin (A).
  • FIG. 6 illustrates a one-step transaction with two business acknowledgments, using an activity diagram, in accordance with an exemplary embodiment of the present invention.
  • a one-step transaction again occurs from gateway A to gateway B.
  • the destination (B) now sends two business acknowledgments, one ( 610 ) to s 2 and another ( 605 ) to the origin (A).
  • gateway B sends both business acknowledgments; s 2 does not send the business acknowledgment to gateway A.
  • FIG. 7 illustrates a Request/Response transaction, using an activity diagram, in accordance with an exemplary embodiment of the present invention.
  • Request/Response transactions are defined where the information in the request gateway message is, in effect, a query and the information in the response gateway message provides the answer to that query. It should be noted that the response gateway message should return to the initiating client application device 105 , but does not necessarily have to pass through the same gateways 110 as the request gateway message.
  • gateway A sends a request to gateway B (step 1 ).
  • Gateway B sends a business acknowledgment to gateway A to acknowledge the request (step 2 ).
  • Gateway B then sends the reply to gateway A (step 3 ).
  • Gateway A then sends a business acknowledgment to gateway B to acknowledge the reply (step 4 ).
  • Many such business transaction both one-step and multi-step, can be specified using such activity diagrams.
  • Each of components of the system 100 including the gateways 110 and transaction administrator 115 , and each of the modules of the gateway 110 , including the information queue module 205 , the first custom-processor module 210 , the formatter module 215 , the second custom-processor module 220 , the mapping module 225 , the validation module 230 , the data enrichment module 235 , the message processing module 240 , the communication modules 245 and the data storage module 250 , or any combination thereof, can be comprised of any suitable type of electrical or electronic component or device that is capable of performing the functions associated with the respective element. According to such an exemplary embodiment, each component or device can be in communication with another component or device using any appropriate type of electrical connection that is capable of carrying electrical information. Alternatively, each of the components of the system 100 and the modules of the gateways 110 and transaction administrator 115 can be comprised of any combination of hardware, firmware and software that is capable of performing the function associated with the respective component or module.
  • the gateways 110 and transaction administrator 115 can each be comprised of a microprocessor and associated memory that stores the steps of a computer program to perform the functions of the modules of the respective components.
  • the microprocessor can be any suitable type of processor, such as, for example, any type of general purpose microprocessor or microcontroller, a digital signal processing (DSP) processor, an application-specific integrated circuit (ASIC), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically-erasable programmable read-only memory (EEPROM), a computer-readable medium, or the like.
  • DSP digital signal processing
  • ASIC application-specific integrated circuit
  • PROM programmable read-only memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically-erasable programmable read-only memory
  • the memory can be any suitable type of computer memory or any other type of electronic storage medium, such as, for example, read-only memory (ROM), random access memory (RAM), cache memory, compact disc read-only memory (CDROM), electro-optical memory, magneto-optical memory, or the like.
  • ROM read-only memory
  • RAM random access memory
  • CDROM compact disc read-only memory
  • electro-optical memory magneto-optical memory, or the like.
  • the memory can be programmed using conventional techniques known to those having ordinary skill in the art of computer programming.
  • the actual source code or object code of the computer program can be stored in the memory.
  • each of the client application devices 105 can be comprised of a suitable user application (e.g., a software application) that is either separate from (e.g., first, second and third client application devices 105 ) or integral with (e.g., Mth client application device 105 ) the associated gateway 110 .
  • the system 100 can include a graphical user interface. The graphical user interface can be configured to provide access to and management of the gateways 110 , for example, using the transaction administrator 115 .
  • Exemplary embodiments of the present invention are configured to facilitate the automatic initiation, processing and completion of a transaction.
  • Any suitable type of transaction that can be performed electronically using one or more steps can be supported by the system 100 .
  • the transaction can be one or more of a commercial transaction, a legal transaction, a financial transaction, a governmental transaction, a medical transaction, a civic transaction, a social transaction, or other suitable transaction.
  • the transaction can be associated with one or more or a banking industry, a trading/securities/financial industry, a healthcare industry, a telecommunication industry, a satellite service industry, an energy industry, a utility industry, a manufacturing industry, an automotive industry, a pharmaceutical industry or other like industry.
  • the Treasury Systems division within a bank wishes to receive automatic payment transactions from their corporate customers.
  • the bank has a specific back-end application format that they desire for all transactions received.
  • the bank also has certain data content, data validation, and other rules to which the bank desires that each automatic transaction conform.
  • Each customer has application systems that utilize a format or formats different than that desired by the bank. Exemplary embodiments of the present invention can allow such disparate application systems (between the bank and the bank's customers) to automatically exchange payments without modification to either the bank's or the customers' applications.
  • the bank begins by configuring a gateway 110 to include the content requirements of each desired payment transaction.
  • the bank defines the normative data model, data validation rules, security requirements and rules, custom processes, data enrichment processes, routing rules, error handling processes, and other pertinent processes.
  • the bank then configures a copy of the gateway 110 to operate within the bank, whereby each valid transaction received from another copy of the gateway 110 is translated from normative information into the bank's desired format for its back-office processing by the bank's client application device 105 .
  • the bank then configures a copy of the gateway 110 at the site of each corporate customer from whom they desire to receive automatic payment transactions.
  • the gateway 110 is configured to operate with each customer's local application(s) (i.e., the client application devices 105 ).
  • the gateway 110 processes payments from the format used by that customer's client application device 105 into the format (non-normative information) used by the customer's version of the gateway 110 .
  • the customer's version of the gateway 110 then validates, enriches, secures, records, logs the data according to the processes and/or rules established by the bank, returning errors to the customer as configured, and then sends successful payment gateway messages, in normative form, to the bank.
  • the gateway messages are received by the gateway 110 located at the bank, checked against all content and validation rules, then processed from normative form into the format used by the bank's gateway 110 , logged, confirmed and processed into the transaction information used by the bank's back-office application. Automated payment transactions can then flow from the gateways 110 located at customer sites to the gateway 110 located at the bank site—flowing payments from customer applications to the bank's back-office application, without modification to either the bank's or the customers' applications.
  • closed-end trading exchanges With respect to closed-end trading exchanges, assume that a group of companies or an independent Solution Provider wishes to create a closed-end trading network between selective buyers and sellers of a particular commodity, avoiding certain issues that they have on public trading forums such as the New York Mercantile Exchange (NYME). Such a service requires specific formats to be interchanged between participating companies. However, each buyer and seller currently has existing application systems that utilize different formats for analyzing and registering trades. The trading closed-end network cannot succeed unless these disparate systems can be linked. Exemplary embodiments of the present invention can allow such disparate application systems (between the buyers and the sellers) to automatically exchange the data required for successful commodity trading without modification to any potential counter-party's applications.
  • disparate application systems between the buyers and the sellers
  • Exemplary embodiments can allow the Solution Provider to determine the requirements of the transactions that will be processed (e.g., a format could be a simple trade of a fixed amount, at a fixed time, at a fixed price, or it could be a complex structure in which the amounts, timing of receipt of amount, price paid for each amount received, and credit/payment instructions vary).
  • the Solution Provider defines the types of transactions (e.g., bid, offer, execute).
  • the Solution Provider also defines data content, data validation, and other rules to which each transaction must conform (e.g., how anonymity is protected during the trading process, how to bill for the use of the system, and the like).
  • the Solution Provider begins by configuring a gateway 110 to include the content and processing requirements of each desired transaction.
  • the Solution Provider then defines the normative data model, data validation rules, security requirements and rules, custom processes, data enrichment processes, routing rules, error handling processes, administrative messages and rules, and other pertinent processes.
  • the Solution Provider then configures a copy of the gateway 110 so that the gateway 110 can receive valid gateway messages from another copy of the gateway 110 .
  • the Solution Provider then configures a copy of the gateway 110 at the site of each buyer and seller with whom they desire to be participants in the closed trading network.
  • Each of these gateways 110 is configured to operate with that particular customer's local application(s) (i.e., the client application devices 105 ).
  • the gateway 110 is also configured to interact with all other gateways 110 within the closed network, through the passing of normative information in the form of gateway messages.
  • Each gateway 110 can process information in the format of that participant's local client application device 105 into the format used by that participant's version of the gateway 110 .
  • the participant's version of the gateway 110 validates, enriches, secures, records, logs the data according to the processes and/or rules established by the service provider as well as rules and processes that the customer themselves can establish (e.g., what specific trading parties to whom a particular type or amount of transaction will be routed, details on the payment of the transaction), returning errors to the customer as configured, and then sending successful commodity trading gateway messages, in normative form, to another participant.
  • the gateway messages are received by the gateway 110 located at the other participant's site, checked against all content and validation rules, then processed from normative form into the format used by that participant's gateway 110 , logged, confirmed and then processed into the transaction information used by the participant's (local) application.
  • automated bids and purchases of the commodity can then flow from the gateways 110 located at each participant's site to the gateways 110 located at other participants' sites—flowing trades from each participant's application to other participants' applications, without modification.
  • a similar scenario can be used by a Solution Provider who wishes to create a private closed-end trading network between buyers and sellers of a security, a derivative of a security, or some other financial instrument.
  • the smooth supply of electricity relies on many different enterprises, such as, for example, generation suppliers, utilities that supply/manage the distribution of electricity, and transmission entities that are responsible for the transport of electricity.
  • ISO Independent Service Operator
  • Such collaboration involves the real-time exchange of numerous messages to balance electricity demand and supply and, most importantly, making sure that remittance information and records are properly conveyed.
  • the network of entities managed by the ISO is best served if the various messages, reports, and datasets can be directly integrated to the appropriate software applications that process this information in each entity.
  • Exemplary embodiments of the present invention can allow the ISO to utilize standard formats for the messages, reports and datasets, while at the same time allowing each entity involved to map these standards to there own internal formats.
  • exemplary embodiments can allow entities to maintain records of pending and completed transactions, as well as being able to produce archived information that can provide the basis for non-repudiation of a transaction by any of the parties involved in that transaction.
  • the ISO begins by configuring a transaction administrator 115 to include the definitions of a normative data model for all messages, reports and datasets to be exchanged.
  • the ISO also configures a transaction administrator 115 with administrative information such as the data about the bilateral and multi-lateral agreements between the entities for which it is responsible, the definition of any administrative messages, such as queries of each involved entity's data store to determine the state of transactions, and the like.
  • the ISO then distributes and verifies the installation of one or more gateways 110 to each entity in its network of responsibility.
  • the ISO provides in a secure a manner a private key that uniquely identifies each gateway 110 for each entity. Such a procedure allows the entities to uniquely encrypt and digitally sign messages reports and datasets.
  • the entity can then execute administrative transactions with the ISO that provide, for example, information about which other entities it can exchange messages, definitions of the transaction to be executed, definitions of the content of the messages, reports, datasets to be used in those transactions, and the like.
  • an entity using the tools provided with the gateway 110 , can integrate messages to the internal applications (i.e., the client application devices 105 ), specifically by configuring the appropriate transport wrapper and by mapping internal formats to the normative message definitions provided by the ISO.
  • Messages, reports and datasets can now flow from the client application devices 105 in one entity to the ISO or another allowed entity. Aspects of any messages, reports, and datasets can be encrypted and/or digitally signed to ensure the reliability and security of a transaction.
  • Each entity can have local, protected information of transactions in which it has been involved.
  • the ISO can have access to relevant information from all entities through its administrative queries.
  • the ISO manages a complex, dynamic set of entities and relationships. Changing requirements require message, reports and dataset formats to be modified or created. These changes can be efficiently handled in a non-disruptive and dynamic manner through the administrative message and re-mapping capabilities of the gateway 110 and transaction administrator 115 .
  • each parts supplier utilizes a different parts-ordering system, with different data types and formats that prohibit on-line interaction.
  • Each of these systems is built using differing technologies, differing data formats, and there is no capacity to receive orders from other computer systems, no capacity to identify part availability or price back to the manufacturer, and no capacity to roll up the collective information into a cohesive, accurate, real-time ability for the manufacturer to purchase parts automatically.
  • Exemplary embodiments of the present invention can allow such disparate parts systems (between the various suppliers, and the manufacturer) to automatically exchange part availability, price, quantity, and other desired information without modification to any of the existing systems (either suppliers' or manufacturer's).
  • the Solution Provider begins by configuring a gateway 110 to include the content requirements of each desired parts transaction.
  • the Solution Provider defines the normative data model, data validation rules, security requirements and rules, custom processes, data enrichment processes, routing rules, error handling processes, and other pertinent processes.
  • the Solution Provider then configures a copy of the gateway 110 to operate at the manufacture's site, whereby each valid parts transaction received from another copy of the gateway 110 is translated from the normative form into the Manufacturer's desired format for its processing by the Manufacturer's local application.
  • the Solution Provider then configures a copy of the gateway 110 at the site of each supplier's system from whom they desire to receive automatic parts transactions.
  • the gateway 110 is configured to operate with each supplier's local parts application(s) (i.e., the client application devices 105 ).
  • the gateway 110 processes transactions from the format used by the supplier's client application device 105 into the format used by the supplier's gateway 110 .
  • Each supplier's version of the gateway 110 then validates, enriches, secures, records, logs the data according to the processes and/or rules established by the solution provider, returning errors to the supplier's system as configured, and then sends successful parts gateway messages, in normative form, to the manufacturer's system.
  • the gateway messages are received by the gateway 110 located at the manufacturer, checked against all content and validation rules, then processed from normative form into the format used by the manufacturer's gateway 110 , logged, confirmed and processed into the transaction information used by the manufacturer's local application. Accordingly, automated parts orders can then flow from the gateways 110 located at each of the supplier sites to the gateway 110 located at the manufacturer—flowing part transactions from each remote, diverse, supplier application to the manufacturer's application, without modification to the manufacturer's or any of the existing supplier applications.
  • each armed service utilizes different logistical tracking systems, sometimes multiple systems. Each is built using differing technologies, differing data formats, and there is no capacity to share changes within any singular tracking system with any other tracking system, no capacity to move inventory between one tracking system and any other, and no capacity to roll up the collective information into a cohesive, accurate, real-time status of all forces' inventory, ordinance or other pertinent information. Exemplary embodiments of the present invention can allow such disparate logistics systems (between the various branches of the armed forces, within each force, and with each state National Guard) to automatically exchange information without modification to any of the existing systems.
  • the Solution Provider begins by configuring a gateway 110 to include the content requirements of each desired logistical information transaction.
  • the Solution Provider defines the normative data model, data validation rules, security requirements and rules, custom processes, data enrichment processes, routing rules, error handling processes, and other pertinent processes.
  • the Solution Provider then configures a copy of the gateway 110 to operate at the Federal level, whereby each valid logistic information transaction received from another copy of the gateway 110 is translated from the normative form into the Federal system's desired format for its processing.
  • the Solution Provider then configures a copy of the gateway 110 at the site of each logistics system from whom they desire to receive automatic information transactions.
  • the gateway 110 is configured to operate with each force's local logistic application(s) (i.e., the client application devices 105 ).
  • the gateway 110 processes payments in the format used by the client application device 105 into the format used by the force's version of the gateway 110 .
  • Each force's version of the gateway 110 then validates, enriches, secures, records, logs the data according to the processes and/or rules established by the solution provider, returning errors to the local logistics system as configured, and then sends successful logistical gateway messages, in normative form, to the federal system.
  • the gateway messages are received by the gateway 110 located at the federal level, checked against all content and validation rules, then processed from normative form into the format used by the gateway 110 at the federal level, logged, confirmed and processed into the transaction information used by the federal level local application. Accordingly, automated logistic information transactions can then flow from the gateways 110 located at each of the armed forces and state National Guard sites to the gateway 110 located at the federal level—flowing information from each remote, diverse, logistics application to the Federal applications, without modification to the Federal, state-level or any armed forces existing logistics applications.
  • a Solution Provider wishes to create a direct network between all participants associated with processing and executing elements of a property insurance claim process.
  • the participants in the property claims process can include insurance agents, claims adjustors, private contractors to bid and execute specific work, inspectors, payment providers, and others. While the collection of potential participants may desire to participate in such a direct network, they must also participate in claims processes outside of that network, as not all industry participants will join the service simultaneously. Therefore, the interested participants may not be willing to accept any requirements from the service provider that forces them to change their current operations, the internal systems that they currently utilize, or use two different processes—one for claims within the network and another for claims outside the network.
  • the Solution Provider has specific data requirements and data formats that define such transactions and that encompass the type of activities/transactions received during the process of making, substantiating, and ruling on a claim.
  • the Solution Provider also has certain data content, data validation, and other rules that they desire that each transaction conform to (e.g., what information a specific participant can access or cannot access in the transaction, a rule to determine who is qualified to participate in this specific transaction in the claims process, etc.).
  • each potential participant has application systems that utilize a different data format or formats. Exemplary embodiments of the present invention can allow such disparate application systems (between all participants of the claims process) to automatically exchange the specific formats or combination of the formats required of successful claims processing, without modification to their applications.
  • the Solution Provider begins by configuring a gateway 110 to include the content requirements of each desired format of the pertinent transactions.
  • the Solution Provider defines the normative data model, data validation rules, security requirements and rules, custom processes, data enrichment processes, routing rules, error handling processes, and other pertinent processes.
  • the Solution Provider then configures a copy of the gateway 110 so that it can receive valid transactions from another copy of the gateway 110 .
  • the Solution Provider then configures a copy of the gateway 110 for each participant with whom they desire to participate in the transactions.
  • the gateway 110 is configured to operate with each participant's local application(s) (i.e., the client application devices 105 ).
  • the gateway 110 processes transactions in the format of that participant 's client application device 105 into the format used by that participant's version of the gateway 110 .
  • the participant 's version of the gateway 110 then validates, enriches, secures, records, logs the data according to the processes and/or rules established by the Solution Provider as well as rules and processes that the participant themselves can establish, returning errors to the participant as configured, and then sending successful insurance claim gateway messages, in normative form, to another participant.
  • the gateway messages are received by the gateway 110 located at the other participant's site, checked against all content and validation rules, then processed from normative form into the format used by that participant's gateway 110 , logged, confirmed and processed into the transaction information used by that participant's local application. Accordingly, automated transactions can then flow from the gateways 110 located at participant sites to the gateways 110 located at other participant's sites—flowing insurance claim transactions from one participant's application to another participant's applications, without modification.
  • the healthcare industry is currently characterized by a multitude of disparate organizations involved in the care of common patients.
  • the difficulties associated with capturing critical patient data and making it available in a timely fashion is a well-documented problem plaguing the industry, often resulting in sub-par patient care, and always resulting in excessive cost.
  • Antiquated and disparate legacy systems within hospitals, physicians' offices, laboratories, pharmacies and insurance companies, combined with patient confidentiality and privacy regulations, are at the root of a data sharing challenge that has significantly restricted the industry.
  • Exemplary embodiments of the present invention can be used within the healthcare industry to address many aspects as such problems within the industry.
  • the Solution Provider begins by configuring a gateway 110 to include the content requirements of each desired format of the pertinent transactions.
  • the Solution Provider defines the content requirements of each desired healthcare transaction (e.g., an update to a medical record, a prescription, or an order for a medical test, and the like).
  • the Solution Provider then defines the normative data model, data validation rules, security requirements and rules, custom processes, data enrichment processes, routing rules, error handling processes, and other pertinent processes to perform against the data being transferred.
  • a copy of the gateway 110 is then configured for each independent health care organization, whereby each valid transaction received from another copy of the gateway 110 is translated from the normative form into the format used by that organization's gateway 110 to generate the transaction information in the format used by that organization's local applications.
  • the originator of the data is able to push the content to all interested parties with no incremental effort, and the overall access to medical information is vastly improved. At no time is sensitive patient data exposed beyond those entities that require the information.
  • Exemplary embodiments of the present invention in the pharmaceutical industry can allow such disparate application systems (hospitals, clinics, doctors, pharmacies, etc.) to automatically send pertinent clinical trial data to the pharmaceutical company, without modification to any of their existing applications, and without the use of paper.
  • the present invention can allow a pharmaceutical company to determine the requirements of the information that must be captured for a successful clinical trial, (i.e. patient history, age, weight, symptoms, etc., etc.).
  • the pharmaceutical company defines the types of transactions (e.g., routine data update, emergency data update, etc).
  • the pharmaceutical company also defines data content, data validation, and other rules that they require each trial record to conform to (e.g., how patient anonymity is protected at all times during the clinical trail, while important drug information is captured and sent on, etc.).
  • the pharmaceutical company begins by configuring a gateway 110 to include the content and processing requirements of each desired clinical trial transaction.
  • the pharmaceutical company then defines the normative data model, data validation rules, security requirements and rules, custom processes, data enrichment processes, routing rules, error handling processes, administrative messages and rules, and other pertinent processes.
  • the pharmaceutical company then configures a local copy of the gateway 110 so that the gateway 110 can receive valid clinical updates from any other copy of the gateway 110 , and so that any clinical updates that are received are processed into the format required by existing analysis applications within the pharmaceutical company, or to a new application.
  • the pharmaceutical company then configures a copy of the gateway 110 at the site of each doctor, hospital, or clinic with whom they desire to be participants in the closed clinical trail.
  • Each gateway 110 is configured to operate with that particular health care provider's application(s) (i.e., the client application devices 105 ).
  • the gateway 110 is also configured to interact with the pharmaceutical company's gateway 110 , passing to it normative versions of the clinical data transactions.
  • Each gateway 110 processes transaction information from that health care provider's client application device 105 into the format used by that health care provider's version of the gateway 110 .
  • the health care provider's version of the gateway 110 then validates, enriches, secures, records, logs the data according to the processes and/or rules established by the pharmaceutical company, as well as rules and processes that the health care provider's themselves can establish (e.g., local logging of their patients' data that was sent on to the pharmaceutical), returning errors to the health care provider as configured, and then sending successful healthcare gateway messages, in normative form, to the pharmaceutical company.
  • the gateway messages are received by the gateway 110 located at the pharmaceutical company site, checked against all content and validation rules, then processed from normative form into the format used by the pharmaceutical company's gateway 110 , logged, confirmed and processed into the transaction information used by the pharmaceutical company's local applications.
  • automated clinical trial data can then flow from the gateways 110 located at each health care provider's site to the gateways 110 located at the pharmaceutical company's site—flowing healthcare data from each health care provider's application to the pharmaceutical company's applications without modification, saving time, cost, and even lives.
  • HMO plans are riddled with industry rules and requirements that the member and the health care providers must adhere to in order to receive benefit payments from the insurance companies. For example, referrals and pre-authorizations are typically required for services delivered by a provider other than the member's PCP, or out of the member's home service area.
  • the providers, insurers, labs, pharmacies can automatically communicate with each other in automated, interactive fashion.
  • the industry has already defined standards for several health claim transactions, such as referrals and authorizations. As further agreed standards are accepted, the last hurdles will be the ease of integration, which the present invention directly addresses.
  • a Solution Provider can begin by configuring a gateway 110 to include the content requirements of each desired claims transaction.
  • the Solution Provider defines the normative data model, data validation rules, security requirements and rules, custom processes, data enrichment processes, routing rules, error handling processes, and other pertinent processes.
  • the Solution Provider then configures a copy of the gateway 110 to operate at the Insurer level, whereby each valid claims transaction received from another copy of the gateway 110 can be translated from the normative form into Insurer's desired format for processing the claims transaction.
  • the Solution Provider then configures a copy of the gateway 110 at the site of each participating provider system from whom they desire to receive automatic claims transactions.
  • the gateway 110 is configured to operate with each provider's local application(s) (i.e., the client application devices 105 ).
  • the gateway 110 processes claims from the format used by the provider's client application device 105 into the format used by the provider's version of the gateway 110 .
  • Each provider's version of the gateway 110 then validates, enriches, secures, records, logs the data according to the processes and/or rules established by the solution provider, returning errors to the local claims system as configured, and then sending successful claims gateway messages, in normative form, to the Insurer's system.
  • the gateway messages are received by the gateway 110 located at the Insurer level, checked against all content and validation rules, then processed from normative form into the format used by the Insurer's gateway 110 , logged, confirmed and processed into the transaction information used by the Insurer's local applications.
  • Multiple insurers can implement the Insurer's version of the gateway 110 .
  • Each provider that utilized a version of the gateway 110 can provide automatic claims to any Insurer that utilized an Insurer's version of the gateway 110 .
  • a fully integrated transaction network can grow that is capable of processing accurate claims without modifying any of the local applications, saving the industry significant time and money, while improving accuracy.
  • the Ticket Issuing and/or Payment Systems division within a ticket issuer wishes to receive automatic ticket issuing and/or payment transactions from their corporate customers.
  • the ticket issuer has a specific back-end application format that they desire for all transactions received.
  • the ticket issuer also has certain data content, data validation, and other rules that they desire that each automatic transaction conform to.
  • Each customer has application systems that utilize a format or formats different than that desired by the ticket issuer. Exemplary embodiments of the present invention can allow such disparate application systems (between the ticket issuer and the ticket issuer's customers) to automatically exchange ticket issuing and/or payments without modification to either the ticket issuer's or the customers' applications.
  • the ticket issuer begins by configuring a gateway 110 to include the content requirements of each desired ticket issuing and/or payment transaction.
  • the ticket issuer defines the normative data model, data validation rules, security requirements and rules, custom processes, data enrichment processes, routing rules, error handling processes, and other pertinent processes.
  • the ticket issuer then configures a copy of the gateway 110 to operate within the ticket issuer, whereby each valid transaction received from another copy of the gateway 110 is translated from the normative form into the ticket issuer's desired format for its back-office processing.
  • the ticket issuer then configures a copy of the gateway 110 at the site of each corporate customer from whom they desire to receive automatic ticket issuing and/or payment transactions.
  • the gateway 110 is configured to operate with each customer's local application(s) (i.e., the client application devices 105 ).
  • the gateway 110 processes ticket issuing and/or payments from the format used by that customer's client application device 105 into the format used by the customer's version of the gateway 110 .
  • the customer's version of the gateway 110 then validates, enriches, secures, records, logs the data according to the processes and/or rules established by the ticket issuer, returning errors to the customer as configured, and then sending successful ticket issuing and/or payment gateway messages, in normative form, to the ticket issuer.
  • the gateway messages are received by the gateway 110 located at the ticket issuer, checked against all content and validation rules, then processed from normative form into the format used by the ticket issuer's gateway 110 , logged, confirmed and processed into the transaction information used by the ticket issuer's back-office application. Accordingly, automated ticket issuing and/or payment transactions can then flow from the gateways 110 located at customer sites to the gateway 110 located at the ticket issuer site—flowing ticket issuing and/or payments from customer applications to the ticket issuer's back-end applications, without modification to either the ticket issuer's or the customers' applications.
  • SOX Verification and/or Financial Systems division within a corporation wishes to receive automatic verification and/or financial transactions from their corporate operating units.
  • the corporation has a specific back-end application format that they desire for all transactions received. They also have certain data content, data validation, and other rules to which they desire that each automatic transaction conform.
  • Each corporate operating unit has application systems that utilize a format or formats different than that desired by the corporation. Exemplary embodiments of the present invention can allow such disparate application systems (between the corporation and the corporation's operating units) to automatically exchange verification and/or financials without modification to either the corporation's or the corporate operating units' applications.
  • the corporation begins by configuring a gateway 110 to include the content requirements of each desired verification and/or financial transaction.
  • the corporation defines the normative data model, data validation rules, security requirements and rules, custom processes, data enrichment processes, routing rules, error handling processes, and other pertinent processes.
  • the corporation then configures a copy of the gateway 110 to operate within the corporation, whereby each valid transaction received from another copy of the gateway 110 is translated from the normative form into the corporation's desired format for its back-office processing.
  • the corporation then configures a copy of the gateway 110 at the site of each corporate operating unit from whom they desire to receive automatic verification and/or financial transactions.
  • the gateway 110 is configured to operate with each corporate operating unit's local application(s) (i.e., the client application devices 105 ).
  • the gateway 110 processes verification and/or financials from the format used by that corporate operating unit's client application device 105 into the format used by the corporate operating unit's version of the gateway 110 .
  • the corporate operating unit's version of the gateway 110 then validates, enriches, secures, records, logs the data according to the processes and/or rules established by the corporation, returning errors to the corporate operating unit as configured, and then sending successful verification and/or financial gateway messages, in normative form, to the corporation.
  • the gateway messages are received by the gateway 110 located at the corporation, checked against all content and validation rules, then processed from normative form into the format used by the corporation's gateway 110 , logged, confirmed and processed into the transaction information used by the corporation's back-office application.
  • automated verification and/or financial transactions can then flow from the gateways 110 located at corporate operating unit sites to the gateway 110 located at the corporation site—flowing verification and/or financials from corporate operating unit applications to the corporation's back-end applications, without modification to either the corporation's or the corporate operating units' applications.
  • gateway which can be a core component of a Business Transaction Application within a Members Only Internet, and the message construct that they process. These gateways have a wide use even as standalone platforms to handle message traffic to and from an application.
  • gateway messages that are sent within a system 100 are preferably formatted as XML documents with two main blocks, a message header and a payload.
  • the payload can comprise one or more payloads (content “messages”). These payloads are what are actually sent and received by the applications that the gateways 110 are serving.
  • the message header contains the information necessary for gateways 110 to process its payloads, i.e., the information to support functions such as sending, receiving, delivering, and persisting payloads. All messages are preferably described by an associated message type.
  • a structured description of each message type can be stored in the local data store of a gateway 110 .
  • a data store can be comprised of any on-lite mechanism for persisting data including a database and associated files.
  • a message is typically part of a simple transaction.
  • Gateway-based systems can support two or more types of simple transactions including: Class Description Transmissions Message goes from gateway A to gateway B Request/Response Message goes from gateway A to gateway B; return message goes from gateway B to gateway A
  • the message header preferably having an XML format contains a hierarchy of tags. Each XML tag in the first level of the message header is associated with a software module. These tags delineate separate blocks of information. Message processing is accomplished by moving down the tags and executing the software module associated with that tag's block. The content of the blocks provide the necessary arguments and data to execute the associated software module.
  • the Message Id block provides basic identification information about a message. It can have the following attributes: transaction-type, message-type, transaction-ID, message-ID, message alias, origin, destination, possible duplicate, etc.
  • a unique internal identifier can be created for the message and for the transaction of which it is a part. This ID is permanently unique and can always be used to definitively identify a message and the transaction of which it is a part.
  • each gateway 110 maintains an embedded database as a persistent store. Given this unique ID it is possible to retrieve all related data associated with a particular message or transaction from any gateway's local datastore. This can be useful, for example, for retrieval queries, to assure auditability, and for reconstructing a damaged datastore.
  • the Security Block provides information about the security of the message.
  • the Security Block contains a log of what is encrypted and by which entity. Conventionally, this information is not kept with the message.
  • Digital signing is a means to ensure that the integrity of a set of data has been preserved in a given state and to clearly identify the entity that is providing that surety.
  • PKI Public/Private Key Infrastructure
  • the mechanism involves a Private Key held by an entity and a Public key that is freely distributed to those entities that are potential counterparties. Either key can be used to encrypt some data, but its companion key must be used to decrypt that data. For example if A wants to encrypt a file he is sending to B so that only B can read it, then A would use B's Public key to encrypt it. B can decrypt the file using its Private Key.
  • An attacker else receiving the file, other than B cannot decrypt the file as they do not have B's Private Key.
  • a 509 certificate contains the party's public key, name or identification, serial number, expiration date, and the digital signature of the issuing authority so a receiving party can verify that public key has been vouched for by a trusted party.
  • Hashing Digital signing makes use of PKI and a mechanism in computing called “hashing.”
  • a hashing algorithm will take any set of data and produce a unique single number, called a hash-code, that represents that number. If even one bit of the input data is changed, then a very different hash code is produced. Hashing can be used to identify any change in a set of data.
  • entity A inputs the data to be signed into a hashing algorithm which produces a hash code for data. Then, entity A encrypts the hash code with its Private Key. The result is a digital signature.
  • entity B can decrypt the digital signing using A's Public key. It can then run the data through the same hashing algorithm. If the decrypted hash code from A matches the hash code produced by B, then B knows two things: one, the data came from A (as A is the only holder of its Private key); and two, the data sent by A has not been altered in any manner.
  • the digital signing is persisted with the data then it can provide a permanent record that particular data was sent on a particular day-time by a particular entity.
  • Important auxiliary information can be added to the data that is digitally signed. For example, with the date-time of the signing, there is not only a record of who signed a data set but exactly when it was signed, which increases audit-ability.
  • any XML tag block (or sub block) in the message can be encrypted by one or more entities.
  • gateway A can encrypt the Message History block so it can be seen by entity B and encrypt the payload block to be seen only by gateway C.
  • the sub-blocks within a payload can also be encrypted down to individual fields if the payload is structured and the gateway is aware of its addressing mechanism.
  • Another encryption scenario can be that gateway A encrypts the payload block targeted to gateway C.
  • the gateway B which may be a service, adds additional information, which it also encrypts for gateway C.
  • the sections that are targeted to the receiving gateway can be stored in the clear (i.e., decrypted), while other sections are left encrypted but still persisted.
  • all digital signings are preferably stored in the Security block, with pointers to the block in the message or payload that is signed. Digital signings can be executed by a gateway for a number of conditions.
  • a signing of the message or a block in the message can occur in a number of circumstances including: whenever a message is sent (i.e., when placed on a SEND or OUT abstract queue); whenever a service performs a particular function (typically, the particulars describing the particular functions are a customized block or are an entry in the Message History that is signed); when an internal procedure completes its function; or when certain error conditions arise and a state must be ensured.
  • the Target Block is meant to identify the ultimate target application that is to receive the message.
  • the target can be dynamic, i.e., it can change during the processing of a message so that the sender does not have to know the actual name/location of a target application.
  • a message may be a payment that the sending application assumes is to be sent to the accounts receivable of a large enterprise.
  • the target can be general (e.g., accounts receivable) but would be enough information for the sending gateway to know what an appropriate receiving gateway is.
  • the receiving gateway may know the address of an Accounts Receivable Distribution Server, and this information is enough for the receiving gateway to send the message to the gateway serving that Distribution Server.
  • the gateway at the distribution server can find out specifically to which Accounts Receivable to send the message.
  • the dynamic nature of the Target block allows for “Just-in-time” delivery of a message, i.e., the target of the message need not be fully identified until it is actually needed by either a SEND queue (Send queues send messages to other gateways) or an Out queue (Out queues send messages to “users,” i.e., the back office applications).
  • the Collection Block contains parameters that associate a gateway message with other messages. There are three types of collections.
  • a GROUP links any set gateway messages together, usually for the benefit of client applications.
  • a SET which defines a set of messages that are bound together for a purpose.
  • a SEQUENCE which is an ordered and enumerated set of messages bound together for a purpose.
  • the Routing Slip contains a template of the simple transaction of which the message is a part.
  • a Transmission a transaction that sends a message from gateway A to gateway B
  • a Request/Reply a transaction that sends a message from gateway A to gateway B with a required reply Message that is sent from gateway B to gateway A.
  • a message can stop at various services that perform specific functions, e.g., authorization, store and forward, authentication, etc.
  • the Routing Slip template can include any prescribed mandatory or optional service stops associated with the transaction.
  • the Routing Slip includes information of exactly what stops have been completed, so a receiving gateway can verify what action is to be done next. Because the current state of a simple transaction is, in effect, stored in the Routing Slip, a transaction can be stopped in mid-stream simply by persisting the message. When that transaction needs to restart, the Routing Slip in the persisted message has the necessary state information to restart it.
  • the History Block keeps a log of all the major events that have occurred to a message as the message progresses through a transaction. This includes, for example, that the was placed on a SEND or OUT queue, that the transaction was stopped because of an error condition, etc.
  • the fact that a log is maintained within a message header allows a receiving gateway and the applications that it is serving to know the history of the received message. This can be very useful in a distributed system. Often entries in the History Block will be digitally signed. This is very useful for auditability and non-repudiation.
  • the Attachment Block includes information about any attachments that are associated with a message.
  • the information can refer to one or more external files that are to be associated with a message.
  • Gateway attachments are similar to email attachments, but are handled in a different way. Attachments are not directly bound to a message; rather the location, name and supporting information about each attachment is provided in “tokens” that are stored in the Attachment Block of a message. When a message is sent to an application, these tokens are also delivered. The gateway then offers a service to the application to retrieve the attachment. The receiving application has two options: it can get a copy of the file; or it can directly access the file to read it. By using this token approach, attachments are only delivered when and if they there are needed by the receiving application.
  • the attachment can either be moved or copied into the sending gateway's data store. Once the attachment has entered the gateway's domain, the gateway can assure that the attachment's location is known and that its integrity is maintained. A receiving application can then read the attachment file by accessing the remote sending gateway's datastore or it can request that the attachment be moved to the receiving gateway datastore, thus the file will be local so accessing it will not be over a network.
  • Attachments can also remain in the sending applications data store, external to the gateway domain. In this case a gateway cannot assure either the location or integrity of the file. Maintaining attachments within the sending applications domain is useful in a number of ways; e.g., to send background data or information along with a message for which it is important that receiving application has reference access but does not have an immediate need; to provide access to a file such as a medical record, which will be periodically changed, in a way that the receiving application always has access to the up-to-date information.
  • the payload section of the message can contain one or more payloads. This is the information that is to be sent from a sending “user” application to a receiving “user” application.
  • a payload can either be processed as a blob, in which case the gateway does not process its content; or it can be a “known” structured message that the gateway can process.
  • a payload is “known” to the gateway if there is defining message-type information in the gateway's configuration data store. All structured payloads, which are sent between gateways as gateway messages, are preferably in a normative XML form.
  • the normative form for a payload can be defined, for example, by an XML message-type schema that is compatible with the serialization of an object model that represents the message-type.
  • Abstract queues are gateway mechanisms having several potential functions.
  • the abstract queues can standardize the way messages/payloads are sent and received form a “user” application i.e. the enterprise application that either needs to transmit some information or the enterprise application that needs to receive some information.
  • the abstract queues can also standardize the way messages (i.e., payloads with their complete header information) are sent and received between gateways.
  • the abstract queues can standardize the way errors are being reported (ReplyTo Queues), so that member application or local administrator can monitor the generated errors and take appropriate actions.
  • IN Queues 910 get information from a user application 950 and present it to the gateway 110 .
  • SEND Queues 920 send the information as a gateway message to other gateways 110 through a network 960 .
  • the RECEIVE Queues 930 gets a gateway message from a sending gateway 110 via the network 960 and presents it to a receiving gateway 110 .
  • OUT queues 940 send information to a receiving user application 950 .
  • any number of abstract queues of each type can be utilized by one gateway 110 . These abstract queues can provide different channels for an application to interact with a gateway 110 and for gateways 110 to interact with other gateways 110 .
  • the IN Queue 910 and OUT Queue 940 from one gateway 110 can also be configured to handle information to/from many user applications 950 as gateways 110 can run in a “server” mode.
  • REPLYTO Queue Another example of an abstract queue is called a REPLYTO Queue, which is used to maintain a separate communication channel between the gateway 110 and user applications 950 .
  • the REPLYTO Queue is used to provide auxiliary information, including error messages. Messages on the REPLYTO Queue can be directed to any user application 950 . For example, it may communicate with the user application 950 that sent the original message or it might communicate with a special error processing application.
  • the REPLYTO Queue can be used for other administrative or system messages that can be conveyed to a user application 950 .
  • Raw message formatters are used to standardize the connection between user applications 950 and the gateway 110 .
  • the IN Queues 910 have the job of providing enough information to a main gateway engine, in a standardized format, so that the engine can know how to process a payload into a gateway message. This information includes items such as transaction type and message type plus a bunch of other mandatory or optional parameters.
  • a raw message formatter has the job of obtaining this information, storing it into a raw message header, and then bundling it with the payload received from a user application 950 to create a raw message.
  • FIG. 10 illustrates this activity. As shown in FIG.
  • a raw message formatter 1010 receives data (i.e., an application payload) from an application 950 , creates a raw message header from the received data, which is bundled with the raw message header to create a raw message that is provided to the gateway 110 .
  • data i.e., an application payload
  • OUT Queues 940 have the job of taking a standardized raw message that has been created by the main gateway engine and putting it into a form that is expected by a user application 940 as illustrated in FIG. 11 .
  • the gateway 110 provides the raw message to the OUT Queue 940 , which converts it into data (or application payload) that is received by the application 950 .
  • Custom raw message formatters 1010 can be easily registered and used by the gateway 110 .
  • the gateway libraries also can include a set of standard raw message formatters 1010 , in addition to custom raw message formatters 1010 , that can be used for transformation between data and raw messages.
  • Abstract Queues provide an abstraction layer that wraps an existing message transport so any underlying message transport can be used.
  • the Internet Protocol provides the most utilized transport layer.
  • SOAP Web Services
  • SOAP Web Services
  • MOM Message-Oriented Middleware
  • JMS Java Message Service
  • File Transport Protocol older styled (non-IP) networks
  • direct port-to-port transports etc.
  • gateways 110 can be used to setup peer-to-peer networks in an existing heterogeneous multi-enterprise messaging environment and create communication channels between legacy applications that were never designed to communicate with each other. It also means that applications can be a “user” of a gateway network without requiring significant recoding by using an abstract queue that fits the data being produced by the legacy (existing) application or that fits the access interface of the legacy application.
  • applications 950 that are communicating with a gateway 110 are remote from the gateway, i.e., the applications 950 are running on a separate machine or in a separate partition of the same machine.
  • the applications 950 are running on a separate machine or in a separate partition of the same machine.
  • all of the regular abstract queue mechanisms and the normal processing of the gateway 110 can be utilized while the message transport is as efficient as it can be.
  • the system 100 can provide reliable messaging, which basically means that a message will not get lost during transmission or local processing. It does not mean that nothing will happen to a message but rather that if something does happen, the system 100 will either fix the problem or reliably provide information as to what has happened to a message.
  • abstract queues wrap existing message transports, abstract queues can rely on the underlying message transport to provide transport reliability.
  • Most modern message transports provide transmission reliability at least as an option and provide “guaranteed delivery” of a message of various sorts. Older transports such as FTP may not inherently provide guaranteed transmission reliability but will have some reliability mechanisms.
  • the transport reliability for a “gateway” transaction will only be as good as the transport reliability of the underlying message transport used for that transaction.
  • it in order for a gateway 110 to discover problems when an underlying transport may be unreliable, it preferably includes a mechanism to reliably send internal “administrative” messages between gateways 110 . Therefore a reliable message transport is bundled with the gateway 110 with appropriate SEND and RECEIVE abstract queues.
  • Messages cannot be lost while they are being processed within a gateway 110 .
  • a message is not removed from an input abstract queue until it is finished processing and it has been queued on an output abstract queue. Therefore, if there is any abnormal termination of the processing the message will still be on the input Abstract queue and will be reprocessed.
  • a message is not removed from the IN Queue 910 until it has been successfully queued on a SEND Queue 920 or until processing has been terminated by an error condition and a message has been placed on a REPLYTO Queue.
  • a message is not removed from the RECEIVE Queue 930 until it has been successfully queued on an OUT Queue 940 or has been terminated with a message on a REPLYTO Queue.
  • an IN-to-SEND process which takes a payload from an application 950 and sends it as a message to another gateway 10 ; and a RECEIVE-to-OUT process, which gets a message from a gateway 110 and sends its payload to an application 950 . Since these processes are more or less mirror images of each other, the following description is limited to the process flow for IN-to-SEND should be adequate.
  • each IN Queue 910 there is a queue listener. After an IN Queue 910 has created a raw message, the queue listener looks at the information in the raw message header, which preferably includes at least a transaction type and a message type, and instantiates a unit of work that processes the raw message into a gateway message. Since each unit of work can be configured to a transaction type and/or a message type, the procedures executed at each step of the message processing can be different for different messages. Also, since it is relatively easy to add custom procedures, there is great flexibility in how messages are processed.
  • a unit of work which has been initiated by the queue listener, is a self-contained class (process) that can be specific to a message type and/or transaction type and execute all the steps necessary to process a raw message into a gateway message. If a processing thread is available, then the unit of work will execute; otherwise, it waits for an available thread. As a result, messages can be processed in parallel up to the number of threads that are available from the thread pool.
  • process self-contained class
  • FIG. 12 is a diagram shows a template for an IN-SEND unit of work.
  • the triangles in the diagram are breakpoints in the processing where the state of the message can be persisted to the gateway's local data store.
  • the unit of work preferably persists the raw message at the beginning of processing (IO) and persists the message at the end of processing (SR) so there is always a record of what has been done to a message.
  • a RECEIVE-OUT unit of work which is symmetrical to the IN-SEND unit of work since the steps are processed in reverse (but with different modules);
  • a SYSTEM unit of work which handles message information messages that need to be conveyed to an application such as Receipts, Rejections and Faults;
  • an ADMINISTRATIVE unit of work which handles a wide number of internal, gateway-to-gateway administrative transactions;
  • a U-TURN unit of work which provides a mechanism to process a Request/response message or to perform a service within a transaction without needing to interact with a remote application.
  • U-turns allow a gateway to process a message purely through local processing, which typically includes executing custom procedures.
  • a U-turn is accomplished by not putting a message that has been processed by a unit of work on an output abstract queue but sending it the appropriate input abstract queue.
  • a message comes into the RECEIVE Queue 930 of a service gateway that has local procedures that can authenticate the sender of a message.
  • the local processing is accomplished, instead of sending the message to an OUT Queue 940 , it is directed to the queue listener of an IN Queue 910 .
  • a unit of work is executed, which in turn sends the processed message to a SEND Queue 920 .
  • the gateway 110 keeps track of the fact that these two units of work are linked together so that it can execute the proper actions in terms of error condition and reliable messaging.
  • the processing steps executed by a unit of work can be specific to a transaction type and message type, which provides a structured means for fine-grained processing of messages.
  • the unit of work approach also permits customized local modules to be easily inserted into the processing steps, which allows for a wide range of custom behaviors.
  • the gateway 110 can be configured as a specialized application platform.
  • a number of actions can take place. For example, there may be a need to communicate the error to the sending and/or receiving application. This communication can be accomplished by placing a message on a REPLYTO Queue.
  • the REPLYTO Queue is preferably monitored by the target application or by a surrogate application that is handling error conditions for the target application.
  • There are multiple categories of error messages including: Rejections, which are error conditions that are known; and Faults, which are error conditions that arise unexpectedly.
  • Certain processing errors can be logged and/or entered into the Message History block.
  • error conditions are packaged into administrative messages that can be transmitted to other gateways 110 , or sent to a monitoring service utilizing, for example, the JMX protocol.
  • a unit of work is finished processing or has terminated because of an error condition, its results (e.g., a message for a IN-SEND unit of work, a Raw Message for an RECEIVE-OUT unit of work) are sent to a queue resolver, which determines on which specific SEND, OUT or REPLYTO Queue the results should be placed.
  • This determination can be a complex decision based on, for example, knowing which target applications are serviced by which queues, rules execution based on the message content, desired transmission formats, etc.
  • there cam be a queue resolver API so that customized queue resolvers can be added.
  • the gateway 110 can validate messages locally before they are sent;
  • the gateway 110 is also useful in reliably moving blobs, which is payload content that the gateway 110 does not process but just passes on.
  • the gateway 110 intelligently processing structured payloads can yield even greater value. For example, by processing structured payloads (or messages), the gateway 110 can validate messages locally before they are sent. Since it allows local processing, these errors can often be repaired within a gateway 110 through a custom procedure. By performing content mapping, the gateway 110 can produce payloads in the formats of each local application 950 it is serving. Through its mapping capability, the gateway 110 can greatly reduce the cost of change introducing new message standards that map to older standards so that no change in legacy applications are required to handle the new messages—a process known as “injection and versioning.”
  • FIG. 13 is a diagram showing the major unit of work steps that involve message processing. Steps 4 and 7 involve local processing of messages. These local processing steps can be inserted in a unit of work anywhere. While the diagram of FIG. 13 portrays one step of each kind, there can be many steps of each type. In other words, there can be more than one transformation step; there can be more than one validation step, etc. As shown in FIG. 13 , processed messages are converted from the form as received from an application 950 into a normative message format, which has utility in the system 100 .
  • Normative messages ensure that a consistent payload format is sent between gateways 110 no matter what unique formats may be required by the applications 950 being serviced by a gateway 110 .
  • One dimension is “spatial”—various applications may use different formats for a message, some being proprietary and some being based on different internal standards.
  • the other is dimension is “time”—over time even industry standard message formats change. Rather than recode all of the legacy applications, it is simpler to map all the existing formats into a standard or normative form when sending a message, and in turn map this normative format into whatever version an application expects when receiving a message.
  • the gateway 110 preferably uses an XML message format for normative messages, which is useful for a number of reasons.
  • XML messages are self-defining because they are based on an accompanying XML schema that defines the message's message type. Given an XML schema, message types can be deterministically converted into an object model, and this object model can be instantiated and used by local operations and gateway modules to process a message.
  • normative messages types can be in the same format as industry standard messages.
  • users of the gateway will have existing XML schema for normative messages or will understand how to create them using the many known tools available for manipulating XML messages.
  • normative messages types can be first modeled as objects classes, using the more structured modeling paradigm of UML, and then automatically converted into an XML schema.
  • the gateway 110 can transmit these messages in very efficient internal formats. For example, normally XML messages are very verbose and are in character format, which requires parsing to be processed. Instead, the gateway 110 can transmit messages in an already parsed form, thus reducing the processing time.
  • step 3 (in the IN-SEND unit of work) involves a formatter that converts a structured payload from a raw message into a non-normative XML message.
  • the formatter is configured to remove the structured syntax from a raw message and get the message into an XML format.
  • Translating into a non-normative XML format avoids the difficulty of dealing with the structured syntax format found in raw messages. If the raw message is already in a valid XML format, with an associated schema, this step can be skipped.
  • Performing the syntax translation from a raw message to a non-normative XML message is a relatively complicated process that cannot be easily generalized. For example, it can involve parsing complicated fixed field EDI-like formats, such as the field formats found in older SWIFT messages.
  • the gateway 110 can offer are a number of formatters, each covering a category of raw formats, which simplifies the conversion problem.
  • the particular formatter that is used can be determined in accordance with configuration data associated with that message type.
  • For a RECEIVE-OUT process there is a comparable set of formatters that will take a non-normative payload and create the appropriate raw message as expected by the user application 950 .
  • Step 5 of FIG. 13 involves transforming, which is mapping a non-normative payload into a normative payload and vise versa. If the source payload is already in normative format, then this step can be skipped.
  • a design tool which can be referred to as a mapper, can be provided to define this mapping.
  • the mapping is done from the non-normative format to the object model version of the normative payload. Mapping from the non-normative format to the object model version of the normative payload may be done because many industry standards are being defined based on UML models of the industry interactions. In those cases, the UML models of the transactions can be read in by the mapper to create the normative message type format.
  • the transforming step can be executed more than once, which enables versioning to be accomplished efficiently.
  • the SWIFT system initially has an XML payment message called an MX 103 that serves as a normative message.
  • MX 103 that serves as a normative message.
  • the SWIFT system then upgrades the message with a new version called MX 103 a .
  • This new version becomes the normative message as it contains some additional fields. It would be inefficient to have to remap all of the raw messages into the MX 103 a format.
  • a two step transformation process is initiated.
  • the first transformation maps raw messages as before into the MX 103 format
  • a second transformation step maps the MX 103 format into the MX 103 a format. In this manner, only the second transformation needs to be defined for all to utilize the new normative message type format.
  • Step 6 is FIG. 13 is performed to validate a normative payload.
  • the mapper tool provides a means for entering validation rules and constraints for a normative message.
  • the standard XML Schema for a message type provides validation rules for individual fields.
  • the mapper also provides a dialect for appending cross field constraints to the schema to provide a fully validated payload. If a message is fully validated it can either be sent on to a SEND Queue 920 or sent to be processed into a raw message and sent to an OUT Queue 940 . Other incarnations of a message can also be validated by using custom local operations.
  • gateway 110 there are a number of reasons for a gateway 110 to act based on the state of a collection of messages in addition to processing individual messages. Doing so allows an application to maintain an association between heterogeneous messages or transactions, maintains integrity while processing batch files, and makes it possible to handle fuzzy two-phase commits when sending out a large set of configuration updates.
  • the gateway 110 supports several types of message collections including a GROUP, a SEQUENCE, and a SET.
  • the parameters associated with these collections are contained in a COLLECTION block in the message header.
  • a unit of work can call a specific collection procedure if a message is part of a collection.
  • the selection of the appropriate collection procedure can be based on the collection ID and type.
  • the gateway 110 is preferably bundled with some standard collection procedures to handle common uses of those collections, such as to handle a sequenced record in a batch or a fuzzy two-phased commit for software module distribution.
  • the ability to handle these collection types in the system 100 is a useful capability and also creates some building blocks to execute complex transactions from simple transactions.
  • a GROUP is a loose and informal collection of heterogeneous messages and/or transactions for which a user application 950 wants to maintain an association.
  • a GROUP is established by creating a unique GROUPID. Once established, the GROUP remains open until a message is received from an application or a remote gateway to close the GROUP. In most cases, GROUPs are not closed as there is little reason to do so.
  • a message that is identified as part of a GROUP through its GROUPID can also be a member of a SEQUENCE or SET.
  • SEQUENCE has an associated SEQUENCE-ID, SEQUENCE-Type, SEQUENCE-Number and SEQUENCE-End, which is a Boolean indicating whether the payload is the last element in the SEQUENCE.
  • SEQUENCE-ID SEQUENCE-Type
  • SEQUENCE-Number SEQUENCE-Number
  • SEQUENCE-End which is a Boolean indicating whether the payload is the last element in the SEQUENCE.
  • the appropriate collection-procedure updates a set of state variables, the values of which direct actions to be taken by the calling unit of work. Actions usually are either to continue processing to throw an exception, i.e., process an error conditions, or execute a “choice” based on the state variable.
  • An example of using a SEQUENCE is for batch file processing.
  • a very large percentage of automated transmission of information between enterprises is done by batch processing, which includes the movement of large files of bundled transactions. These bundles are treated as an ordered sequence of transactions.
  • the sending application may assume that the record in the file will be processed in sequence and may build in dependencies based on this assumption. If each record in a batch file is to be processed and mapped as a separate message, the gateway 110 is preferably configured to preserve the designated sequence of messages so as to preserve the dependency for the receiving application.
  • a SET is an unordered set of messages that when processed can create states that require action.
  • a Service Provider gateway can send out a large number of Request/Reply administrative messages whose payloads include a new message type schema and associated maps.
  • the sending gateway can send these messages as a SET.
  • the Reply which will be sent by a targeted gateway, is that it has received the payload and is prepared to use it.
  • the sending gateway will process these Replies as a SET, and when a critical mass of positive replies are received (e.g., 95% positive replies), the sending gateway will cause a new administrative message to be sent that tells all the receiving gateways that they can now use the new message type.
  • SETs have some characteristics of GROUPs and some characteristics of SEQUENCES. They have a SET-ID, a SET-Type, and a SET-End, but no sequence number.
  • the gateway 110 is designed so that most of its components can be replaced. To permit this replacement, a clean API can be presented for each component and specified parameters can be entered into the configuration data store so a new component can be invoked in the context of a transaction type and message type.
  • This modular design makes it easy to create and distribute new versions of all of these components. More important, it allows a Service Provider to create custom modules and distribute them and it allows each member or user, through their administrator, to create customized modules. The customizability enhances the ability of the gateway 110 to provide custom processing specific to a single gateway and transaction type.
  • gateway message processing is available for component access and distribution, including hierarchical access privilege maps, encryption, and digital signing to verify that modules have not been tampered with.
  • a queue resolver associated with a SEND queue 920 might decide where to send a message based on the message content using a rule that “all payments going to Europe that are over $1M must be sent to a small bank on the Isle of Mann.”
  • a data enrichment procedure might use a rule that “any Swiss bank payments where the beneficiary is specified with a name should be replaced with a coded account number.”
  • a screening procedure might use a rule that “any payments to banks in Afghanistan where the beneficiary's last name is Bin Laden should be flagged for review.”
  • Gateways 110 preferably include a standardized business rules API so that business rules engines, conforming to this API, can be used.
  • a conformant business rules procedure with a corresponding rules editor can be bundled with the gateway.
  • Data Enrichment involves the local insertion, update, or modification of elements in raw messages or gateway messages.
  • Data enrichment can be used to convert data from one format to another, such as by replacing a national account number with an IBAN. It can also be used to provide data not supplied in the message itself. This is especially useful in moving data from one message format to another where the focus is on moving a subset of data in the first message to data in the second. Further, data enrichment can improve the efficiency of message transmission. A full XML Message or payload need not be transferred as long as through the effective use common content identifiers, data enrichment can fill in the missing elements.
  • This type of data enrichment is useful when transmitting a binary form of a message that is to be turned into an instance of an XML model in the gateway 110 for proper processing.
  • Another desirable use of data enrichment is to handle a key part of lossless conversions, i.e., the reconstruction of data which has been down-mapped or down transformed.
  • the gateway's security mechanisms focus on the integrity and persistence of messages, data, and software.
  • the focus of security in most other network-oriented applications is transmission security. Since the gateway 110 relies on and wraps external message transports, it relies on these transports to provide transmission security, such as for preventing interception of messages, man-in-the-middle attacks, etc.
  • the gateway security mechanisms which focuses on data security, can ensure privacy through encryption and ensure audit-ability through digital signing.
  • Each gateway 110 preferably includes a keystore, which is a storage location for securely keeping PKI certificates and private key pairs.
  • Each gateway 110 keeps at least two current private key/public key certificate pairs, one for encryption and one for digital signing.
  • the meaning of “current” is that the keys can be actively used and are valid. Certificates normally expire after a period just like a driver's license.
  • the gateway 110 is concerned with security for persisted data, its keystore must hold and manage all previous key pairs. As a result, persisted data can still be decrypted or its digital signing verified no matter how long it has been persisted. For example, by law, some persisted financial data must be readable and verifiable for as long as 80 to 100 after it is first recorded.
  • the private key/public keys can initially be generated by each gateway 110 at initialization.
  • the gateways 110 preferably do not rely on a certificate authority, so the generated public key certificate is not certified by a trusted third party.
  • Certification involves a trusted third party digitally signing the certificate to authorize it.
  • the security architecture in the gateway 110 allows for a hierarchy of trusted third parties to authorize a certificate, so a federated security model can be implemented.
  • the Solution Provider can act as a trusted third party and authenticate a gateway's certificates.
  • Message security can be managed by means of cryptographic policies for each message type. These policies can also be shared among all gateways 110 in a gateway network. These per message policies are preferably stored in a Msglnfo configuration section of the configuration file.
  • a cryptographic policy specifies a set of cryptographic actions that are performed in sequence on a message. These actions include, for example, encrypting some payload elements or an entire payload entity, signing some payload elements or an entire payload entity, and signing specific message header elements. Some header elements may not be able to be encrypted, such as elements in the security block.
  • the cryptographic actions specified in the message type policy in the Msglnfo configuration section are executed just before placing the message on a SEND Queue 920 .
  • a gateway 110 performs the same actions in the reverse order just after removing the message from a RECEIVE Queue 930 .
  • Encryption is used to protect payload data or some sections of the message header from unauthorized accessed by users while a message is being processed or while it is persisted.
  • Public encryption is very specifically targeted to the holder of the private key that will be used for decryption. That means that one message may utilize a number of encryption signatures as service elements along a transaction path to deny access to some content and, in rare cases, the receiver of the message may need to be denied access to some elements that should only be available to a service. Instances may arise where the same payload is to be sent to many gateways. In that case, where individual encryption of each message instance would be too inefficient, it is possible to create an encryption certificate for a set of gateways 110 .
  • Digital signings are used to validate identity and to ensure content integrity.
  • a digital signing contains the signing gateway's identity, and a hash of the content that is being signed, which is all encrypted by the private key of the signing gateway.
  • Digital signings can be hierarchical, i.e., the content that is signed can itself contain digital signatures. For example a time-stamp can be combined with a digital signature and that entity, itself, digitally signed to provide a verifiable signing time to the original digital signature.
  • Any set of elements in a message or payload can be digitally signed, as defined by the cryptographic policy for that message. Digital signings within a Message will be persisted along with a message, since the signatures are stored in the Security Header block of the message. Other gateway entities, such as data frames, can also be digitally signed.
  • Digital signings provide a useful audit-ability capability. Not only are the signed records of a transaction persisted at one gateway, they will also, most likely, be independently persisted at the other gateways that have participated in the transactions. Since all transactions have unique IDs, all information about a transaction can, if needed, be aggregated to produce a robust and complete record of a transaction. This is especially true to settle disputes and allow for non-repudiation of a transaction. In the discussion of data frames, a use of signed data frames is presented that provides the most complete record of a transaction.
  • All the software modules e.g., JAR files
  • JAR files used at runtime by a gateway 110
  • these digital signatures are checked, and if they are not validated, the gateway will not start. Checking these digital signatures effectively makes the gateway 110 tamperproof.
  • all customized modules even if they are purely local, are preferably sent to a Solution Provider so that they can be properly digitally signed.
  • certificates in the gateway network are self signed. That means that the chain of trust is only one deep, that one being a Solution Provider.
  • any X509 certificate e.g., from the GSA certificate authority, can be used.
  • Privileges determine what access rights external entities have on a gateway's data store and meta-data store. These access rights include Read, Add, Update, and Delete. The access rights can apply to the various sections of configuration data, to other components of the meta-data, and to data in the data store. Priviliges are applied when request messages are received by the gateway from the external entities. A digital signature can ensure the secure identity of the requesting entity.
  • Entities that can make these requests are a gateway administration tool, when used by a local member administrator, other gateways, and a special gateway that belongs to the Solution Provider.
  • a request requires an access right, the sender's identity is checked against a privilege table stored in the configuration data store. Privileges can be specified, in order of precedence, for any individual gateway 110 , a Solution Provider (there are some privileges that can only be granted to the Solution Provider), a local entity (which is usually a request from the administration tool as exercised by a member administrator, the identity of the member administrator being stored in the gateway's configuration file), and a remote entity (which is usually another gateway 110 ).
  • gateways 110 provide an effective solution to the problem of managing private keys and certificates.
  • PKI private keys need to remain private.
  • certificates expire, forcing renewal of certificates in a secure and authenticated manner.
  • the effort to manage certificates does not scale well. Rather, it gets more costly and complicated the more certificates need to be issued. This is especially true if private keys are somehow extended to cover the identity of actual (human) users.
  • the gateway 110 provides a controlled, closed cross-enterprise environment that has a consistent structure that is easy to manage where the number of private keys and certificates is limited to the number of gateways 110 in the network. To accomplish this, the PKI mechanisms maintained within the gateway 110 provide security and identification for the other players in the network, specifically human users and the user applications 950 interacting with the gateways 110 .
  • the gateway 110 provides security mechanisms to applications 950 through a service and API that it offers where an application 950 can get a dataset encrypted or digitally signed using the gateway's key set.
  • the gateway 110 also provides a unique digital signing for an application 950 when that application 950 is registered as a user of the gateway 110 . This digital signing can be used by other gateways 110 and applications 950 to securely identify an application 950 that is the source of payloads.
  • the gateway 110 provides security mechanisms associated with human users of the system by providing identification through a digital signing essentially based on the user's actual signature. This digital signing can then be used as a secure identification of the individual, which provides the ability to permanently associate data with an individual. This is very useful for audit-ability and for avoiding mistakes when data, such as medical records, are associated with the wrong person.
  • the gateway 110 preferably includes a local database for persisting information about transactions, messages and payloads. When taken in aggregate across all of the gateways in a gateway network, these local databases form a distributed data store.
  • an IN-SEND unit of work first records a raw message it receives, and as a last step, it records the processed message.
  • These messages are preferably permanently stored in the data store as the last action of the queue resolver. This supports reliable messaging so that, if anything happens during unit of work processing, there will not be any erroneous message content stored in the database.
  • RECEIVE-OUT units of work the order is reversed. If desired, these messages can be signed. This means that there is a record of the raw message and the processed message so that it is clear what processing was done by the gateway 110 .
  • the state of a transaction as known by a gateway 110 is updated in the data store, such as an acknowledgement being received that a sent message was successfully received or the fact that a reply was received for a response message.
  • gateway data store Additional features include, for example, the ability to activate a number of breakpoints during unit of work processing where the state of a message can be stored. This feature makes it possible to debug processing problems as they occur.
  • some fields in a structured payload can be identified as key fields. These key fields can be extracted from a message and stored in the data store to add in data querying.
  • a data frame is a set of messages along with associated transaction data that is retrieved from the data store and/or a set of configuration meta-data.
  • the data frame which is produced by processing a data frame request (query), can be delivered as a set of XML documents collected together into a Zip file.
  • XML documents comprise, for example, retrieved messages, including raw messages; all of the transaction data associated with messages; any logs concerning the processing of the included messages.
  • Each of the XML documents in the data frame can be digitally signed, as well as the data frame itself, so any content changes can be detected.
  • a data frame request is preferably configured as an XML document that specifies the criteria for retrieving messages and their associated transaction data and specifies the criteria for retrieving configuration meta-data form the data store.
  • the data frame request can be created, for example, using the gateway administrative tool.
  • a data frame request can be written in a syntax that is similar to the syntax used in a SQL WHERE clause, as the gateway 100 can actual convert the data frame request into a SQL Query.
  • Queries can include any defined key fields. Queries can include any transaction states, such as “Completed” transaction, “Failed” transactions, etc.
  • Separate query expressions can be prepared for production messages and those messages that have been stored in the data store at internal breakpoints. However, both query expressions can exist in the same data frame request.
  • a data frame request XML document can be sent to a gateway as a message where it is processed. The resulting data frame is then sent back to the application or gateway that requested it. Since data frame requests are preferably implemented as XML documents, they can be used repeatedly. As a result, it is easy to set up data frame requests to provide effective monitoring of the activities of a gateway 110 .
  • FIG. 14 shows a simplified output of such a monitoring activity.
  • a data frame request is received by a gateway 110 either from an application 950 or from a remote gateway 110 .
  • a gateway 110 has executed the data frame request and produced a data frame, such as in the form of a zip file, the gateway 110 sends a response message treating the data frame as an attachment.
  • This action leverages the flexibility of attachments, informing the requestor of the size of the data frame, allowing for the lazy reading of a data frame, as data frames can get very large.
  • the mode discussed above is to “copy” the information and produce the data frame.
  • a second mode is to “cut” or delete the information that is used to produce the data frame.
  • the third mode is to “remote” the data by leaving the transaction information about a message in the data store, removing the message body, and replacing it with pointer to the data frame that will contain it.
  • the cut method provides a means to archive data and persist it for a long time. First of all, it removes data from the data store in a planned and orderly fashion, keeping that data store at a manageable size.
  • the extracted data frames create a very usable archive of the message traffic. Since the documents in a data frame are preferably in an XML format, they can be read long into the future without requiring any proprietary software, including that of a gateway 110 or any of its tools. If an archive of the signing gateway's public keys is kept, then the digital signatures on the content of the data frame can assure that the integrity of the archives is maintained.
  • Data frames are also useful to provide audit-ability and to provide non-repudiation of a transaction. All of the information concerning a transaction in a gateway's data store can be extracted and stored in a data frame, even including meta-data, that, for example, describe the syntax rules for describes definitions of a message syntax. This data frame can be digitally signed itself. Any information about a transaction at other gateways can also be extracted as signed data frames. All of these data frames form a complete and accurate record of a transaction that is audit-able and can be used for non-repudiation.
  • Configuration and state data which are stored in the data store, are used to control how a gateway 110 operates.
  • This data is designed to make a gateway 110 self-contained and remotely controllable, i.e., any expected changes in the behavior of a gateway 110 can be instituted by sending a message that updates some configuration values and the state of the gateway 110 can be ascertained by querying state data.
  • Configuration and state data can be queried and updated as long as the requestor has the appropriate privileges.
  • a standard API can be provided so that a software module running in the gateway 110 can directly access this data.
  • a set of administrative messages can also be provided to add additional entities and parameters remotely to the configuration and state data as long as the sender has the appropriate privileges.
  • Configuration data includes configuration entities, such as maps, transactions definitions, schemas, queue definitions, routing templates, etc., which are stored in the gateway's data store.
  • the declarative configuration data contains all of the parameters to run the gateway 110 . Updating the configuration entities allows gateway behavior to be changed without requiring recoding.
  • Configuration entities can be updated through administrative messages received by the gateway 110 , typically in the form of a data frame. Most updates can be implemented through a “hot” update, i.e., the gateway 110 does not have to be restarted for the update to take effect.
  • Gateways 110 can operate in a self contained mode where behavior changes are brought about by updating configuration data through remote messaging, which essentially obviates the need for local access to a gateway 110 once it is up and running.
  • a “static” BTA By providing all necessary configuration data during the initialization process.
  • Such a BTA can work with client gateways without the need for any service nodes. More commonly, the Configuration data included at initialization can be just enough to get the gateway 110 running so that a full configuration data store can be bootstrapped through messaging with a service that provides the rest of the needed configuration data.
  • Configuration entities include the following:
  • the Admin configuration entity specifies information about administrative transactions and messages.
  • Gatewaylnfos The Gatewaylnfos configuration entity includes information about other gateways 110 in the gateway network with which a particular gateway 110 can exchange messages. It also includes information about a particular gateway 110 that is exposed to other gateways 110 in the gateway network.
  • Header The header configuration entity defines the processing that occurs within a gateway 110 for the header part of a gateway message. It defines the blocks that are required and optional within the header, as well as the class that processes each block.
  • FileSignatures The FileSignatures configuration entity can be used to sign one or more files associated with a configuration. When signing a file using this entity, the administration tool adds a file signature to the configuration together with a reference to the signed file. Any change in the file content can be detected.
  • the InstanceData configuration entity includes general options for a gateway 110 , including instance name (gateway name), timeouts, thread pool options, JMX options, and logging options.
  • the InstancePlugins configuration entity specifies the classes used for the exception handler, OUT queue resolver, SEND queue resolver, local address resolver, network address resolver, and the Solution Provider instance name.
  • MapComponent The MapComponent configuration entity includes certain XML files associated with a map. It includes:
  • MAP file The map file. Pointer to the other files associated with the map;
  • OM file The object model. There is one OM file in a map;
  • XM files An XML model. There can be multiple XML models in a map, one for each schema; and
  • OXM files A mapping between an XML model and the object model. There can be multiple mappings in a map.
  • Msglnfo The Msglnfo configuration entity shows the payload block(s) of a message. It also defines the cryptographic actions that are performed on a message.
  • OperationDefs The OperationDefs configuration entity specifies classes and parameters for standard and custom operations.
  • OutQueueMaps For each defined target application, the OutQueueMaps configuration entity specifies the local OUT queue target based on message type.
  • Privileges The Privileges configuration entity sets access to configuration data and message data within the gateway network.
  • QueueDefs The QueueDefs tab is used to set up gateway queues. Each queue that is set up is initialized when the gateway 110 is started. IN, OUT, SEND, and RECEIVE queues can be defined.
  • RawForrnatterDefs The RawForrnatterDefs configuration entity defines the raw formatters that are available.
  • Schema Each schema used in a gateway network, whether for business messages, administrative messages, or system messages, is a Schema configuration entity.
  • SendQueueMaps The SendQueueMaps configuration entity controls how messages are routed to SEND Queues 920 from the gateway 110 .
  • SystemMsgDefs The SystemMsgDefs configuration entity shows the namespaces and content blocks for the system messages.
  • System messages include Receipts, Rejections, and Faults.
  • TargetApplnfos The TargetApplnfos configuration entity defines the physical address(es) to which messages associated with a particular application should be routed.
  • TxnlnfoFixed The TxnlnfoFixed configuration entity specifies the steps that will be taken for particular transaction types within a gateway 110 .
  • TxnlnfoLocal The TxnlnfoLocal configuration entity specifies the steps that will be taken for particular transaction types within a gateway 110 .
  • the parameters and entities stored as state data provide a profile of how a gateway 110 is operating. For example, this can include quality of service parameters, tracking parameters like the total number of messages received, and, often, licensing parameters to ascertain “charges” due. State data will also can variables utilized for the processing of collections.
  • BTA Gateway-Based Business Transaction Application
  • This section will present the general features of a Business Transaction Application as facilitated by a set of gateways 110 .
  • An SOA Service-Oriented Architecture
  • An SOA is a peer-to-peer network comprised of nodes that can usually be divided into client-nodes, which consume the processing done within the SOA, and service nodes, which provide an identifiable, single-purpose function to support a process.
  • the nodes are coupled together through a set of gateway/adapters that interface with a network.
  • One view of an SOA stack is presented in the diagram below.
  • the adapter/gateways that service both client and service nodes operate in a true peer-to-peer fashion. In all cases, the gateway 110 is interacting with an application whether that application is a client or service application.
  • SOAs are typically focused on service nodes, creating “composite applications” out of existing applications. This involves wrapping legacy applications with a new interface so they can be called as a component (or service) in that composite application, much like independent procedures are called in a traditional programming language.
  • client nodes such as a portal or a data warehouse.
  • the adapter/gateways are focused on wrapping applications with a Web Services interface, which is a standard for wrapping processes with a standardized remote procedure call based on an XML standard.
  • the process orchestration is done through a centralized business process monitor.
  • BTAs Business Transaction Applications
  • VANs Value-Added Networks
  • ESDs Enterprise Service Buses
  • the gateway 110 enables the implementation of a modem Business Transaction Application.
  • a gateway peer-to-peer network is designed to support a very large number of heterogeneous, new or legacy client nodes. It treats client nodes as the true “users” within a BTA.
  • the gateway 110 functions without the requirement for any centralized services, such as a transaction processor or centralized database. Basic functions of the gateway network are distributed and carried out within each gateway 110 . In fact, a static gateway-based BTA can be set-up with no requirement for any services.
  • Services can be easily added to a gateway network, to add services to manage the BTA and provide specific, needed functionality.
  • the gateway 110 effectively supports inter-enterprise BTAs, where many client nodes wish to transact with many other client nodes and the maintenance of centralized procedures and services is more problematic.
  • the gateway 110 also effectively supports intra-enterprise applications when peer-to-peer communication between client nodes is valued. This is especially applicable if the IT topology reflects the merger and acquisition of many divisions.
  • the gateway 110 is preferably designed as a logical gateway that provides a peer-to-peer connection between applications to run a Business Transaction Application.
  • a gateway 110 can be located in the neighborhood of the applications 950 that it serves. However, in many cases those in control of a neighborhood, e.g., an enterprise's internal IT department, may not want the responsibility or the risk of having the gateway 110 physically located in their neighborhood.
  • the gateway 110 is configured so that it can operate remotely from the applications 950 that it serving. This remote operation is possible as long as the networked connection between an application 950 and the abstract queues that service the application 950 is maintained.
  • the gateway 110 for a number of user applications 950 in an inter-enterprise BTA can exist in an external server farm and not reside within the user application's enterprise space.
  • Gateway Seen as a Centralized Processor
  • gateways 110 When gateways 110 are collected together on one or a set of servers, they take on many of the characteristics of a more traditional centralized Transaction or EAI (Enterprise Application Integration) engine. When viewed as a centralized engine, the collection of gateways 110 presents a profile with different benefits, which distinguish it from other transaction and EAI engines, such as a gateway's Chinese-wall privacy features. This different profile may be attractive to particular market segments of the traditional centralized VAN, EAI and Transaction market. For example, it can be used for a one-to-many, hub and spoke configuration, where an enterprise wants to service many of its counterparties (clients, suppliers, etc.) and flexibility for the gateway location is required.
  • EAI Enterprise Application Integration
  • the gateways 110 can communicate with each other through a set of “administrative” messages. These administration messages provide the mechanism for exchanging internal information of all sorts. Some examples of administrative messages include, for example, technical acknowledgements from a receiving gateway to a sending gateway that a message was received, a data frame request sent from a gateway to a remote gateway to retrieve information from the remote gateway data store, and a simple ping to make sure that a gateway is “up.” Administrative messages make it possible to have a fully distributed system as they are used to implement coordinated activity in a gateway-based BTA.
  • System messages are a class of administrative messages used to communicate information between a gateway 110 and a user application 950 that it is serving. System messages can be placed on any OUT/SEND/REPLYTO queue.
  • One example of a system message-type is the “RECEIPT.”
  • a RECEIPT is the technical acknowledgement that a message has arrived at its destination. It is sent by the receiving gateway to the sending gateway.
  • the RECEIPT makes it possible for the source user application 950 to know that a message has been received. Not all messages require receipts. If one is required, the requirement will be configured in the message definition of that message type. If a RECEIPT is asked for and not received within a proscribed time, the sending gateway can assume it has an error condition.
  • REJECTION reports expected error conditions to a user application 950 , such as that a message violates constraints specified in a validation rule, etc.
  • a FAULT reports unexpected error conditions, such as that a module unexpectedly terminated its processing and throws an exception.
  • Administrative messages form the coordinating backbone of a BTA, so it is desirable that they are sent and received over a reliable message transport, which can be bundled with the gateway along with the appropriate SEND and RECEIVE abstract queues.
  • a new message can be easily added for those that have that privilege, which is usually a Solution Provider.
  • the mechanism for defining a new message combines the normal designer processes for defining a message with the mechanism for defining an associated software module in a manner similar to the mechanism used to define an associated software module for a customized header block as described previously.
  • a merchant payment credit card payment may involve the following steps:
  • Bank A sends notice of debit to Bank B;
  • Bank A bundles all request for payment messages into a batch file
  • Bank A sends file to a clearing and settling agent
  • Bank B deducts payment from customer's account
  • Bank B sends payment acknowledgement to bank A;
  • Bank A send payment acknowledgement to merchant.
  • the gateway 110 provides a dynamic mechanism for complex transactions. It allows enterprise users to define their own customized transactions with effective transaction security, tracking and audit-ability. This is accomplished by building complex transactions out of the two-types of the simple transactions, Transmission and Request/Reply, bound together with a scripting language to define process flow. Since simple transactions cover the two basic types of interaction needed in a transaction, any complex transaction can be built using defined simple transactions.
  • the gateway 110 can ascertain what step in a complex transaction is next required by referring to an enriched Routing Slip that describes the transaction and the steps already accomplished. Since the execution of the current step involves a defined simple transaction, the gateway 110 knows how to execute the required step.
  • complex transactions can be paused to allow associated transactions to be completed through the use of a simple push-down stack mechanism. Upon the successful completion of associated transactions, the complex transaction can be resumed. This ability adds another level of dynamism to complex transactions while at the same time greatly simplifying the specification of nested complex transactions.
  • each gateway 110 becomes part of a distributed database.
  • at least one gateway 110 to be able to retrieve data from one or more remote gateways 110 .
  • This ability can be accomplished by using data frame requests and data frames.
  • Data frame requests are preferably created and stored as an XML document.
  • There is an administrative Request/Response message that can carry a query as a payload.
  • the receiving gateways executes the query and send back a Reply administrative message with a data frame as an attachment.
  • the receiving gateway checks its privileges to make sure that the requesting gateway has the right to execute the data frame request.
  • Data frame requests can be sent to multiple gateways as a SET, so the requesting gateway will know when all requests have been fulfilled.
  • data frame requests are preferably stored XML documents, sending them remotely can be scheduled, which makes them useful for many maintenance and monitoring activities over a set of gateways 110 .
  • a tool such as the admin tool, can be used to create data frame requests and to display data frames.
  • a number of useful parameterized data frame requests templates can also be provided in a library.
  • Messages can be extracted on a periodic basis through data frame requests, signed and archived. Signed information about any specific transaction can be gathered through local and remote data frame requests. These queries can include not only a record of messages sent and received but also of all relevant configuration and state information, e.g., exactly what message type schemas and maps were utilized, etc. All of this information can be digitally signed with time stamps to provide powerful non-repudiation of all aspects of the transaction.
  • a gateway 110 is designed to not require service nodes, a fully effective BTA can make use of many services. Some of these services are useful for the smooth running, maintenance and enhancement of a gateway-based BTA. These, in general will be provided by the vendor and may be bundled with the product. Other services can be perceived to be mandatory for a particular BTA or class of BTAs. The Solution Provider, who is running that application, would add those services. There will also be room for services that enhance the capabilities of a BTA. These maybe added by the vendor, the Solution Provider or a Third-party Provider. As long as any Provider properly utilizes a gateway 110 and integrates a service into the Routing Slip of various transactions, they can add a service to a BTA. Also any service can be replaced as long as the messaging interface of the original is maintained or new message type properly defined and integrated into a BTA.
  • gateway BTA To better understand how a gateway BTA operates, it is useful to understand the roles played by persons or organizations involved in a BTA. While there is a lot of flexibility in how a BTA can be set up and managed, there are some standard roles for people and organizations that may be assumed in designing the gateway to support BTAs.
  • any BTA there is some entity in charge, that can take help calls, initialize the BTA network, provide on-going updates, and if it is an inter enterprise BTA, make money by running the BTA.
  • This entity/role can be referred to as the Solution Provider.
  • the existence of a Solution Provider is a difference between gateway-based BTAs and transaction applications that simply provide connections between applications over the Internet.
  • Solution Provider gateway there is one gateway in a BTA that is denoted as the Solution Provider gateway.
  • This gateway has the widest array of privileges and is, initially, the only gateway that can author a change in privileges for other nodes. All of its authored changes will be appropriately signed for security reasons.
  • Solution Providers can delegate privileges to other entities at their discretion.
  • the Member Administrator role involves the ownership, maintenance and management of the client-side of a gateway 110 , i.e., the “local” processing, in a BTA.
  • Member Administrators can be responsible for one or more gateways 110 . Since gateways 110 are all designed to operate in a self-contained manner, Member Administrators can interact remotely with the gateways 110 in their purview.
  • the Solution Provider creates a Member Administrator by creating an appropriate privileges group. The Member Administrator can also delegate privileges.
  • Services are typically applications that will send raw messages, usually raw administrative messages to one or more gateways 110 .
  • the Admin Tool is the primary application used by Solution Provider or Member Administrator to bootstrap, maintain and monitor a gateway 110 . Since the Admin Tool is an application, it can communicate with a local gateway (one for which it is registered) by sending a raw administrative message.
  • the Admin Tool can create, update and package all of the components of a gateway 110 , e.g., configuration data, maps, schema, software modules, etc. In many cases, the packaging of these components can be in the form of a data frame.
  • the Admin Tool also can have a data frame editor that can be used to create data frame requests and to view data frames.
  • the Admin Tool is used to create the set of files that are used to initialize a gateway 110 .
  • the first gateway that must be setup is the Solution Provider gateway, as this is the gateway that has controlling privileges.
  • a normal gateway installation will be done through a bootstrapping process.
  • a “disk image” will be prepared that includes all the basic software modules and a minimum number of meta-data components to allow the new gateway to communicate with at least one other gateway, in most cases the Solution Provider gateway.
  • This package will include an installation program that instantiates the new gateway. Once instantiated, the new gateway can acquire additional modules and data, usually from the Solution Provider gateway, another central service or through a Member Administrator, to become fully configured.
  • the use of SETs and SEQUENCEs can support bootstrapping by making sure that all required messages are received.
  • All updates are created and packaged using the Admin Tool.
  • the Admin Tool can specify the set of gateways 110 to receive these updates.
  • the Admin Tool's local gateway will send administrative messages to each target gateway. It can utilize digital signing in sending the updates to verify their integrity.
  • the gateway 110 has a bundled SET process for executing updates using a fuzzy two-phase commit scheme so that changes are only operational when a critical mass of target gateways have incorporated them.
  • the Map Designer is a separate application that creates, edits, and packages transaction/message maps. These packaged maps are then picked up by the Admin Tool for distribution.
  • the Map Designer preferably includes the features of ObjectSpark, a product of FireStar and described in U.S. Patent Nos. 5,522,077, and 5,542,078, 5,937,402, and 6,101,502.
  • a gateway-based BTA will involve a dynamic set of gateways 110 (new ones being added, existing ones being decommissioned, etc.), and typically there will be an administrative entity that has responsibility for managing the BTA. That entity preferably knows the topology of the network it is serving. Also, each gateway 110 preferably knows what set of remote gateways with which it can interact. There are two bundled services that are provided to manage the topology of the BTA network.
  • a Registration Service keeps track of a profile of all the gateways 110 in the BTA.
  • a gateway 110 When a gateway 110 is initialized or when its profile changes, it sends an administrative Message to the Registration Service.
  • the Registration Service is responsible for providing a new gateway 110 with the address configurations of the set of gateways 110 with which it can communicate and for informing an existing set of gateways 110 with the address configuration of the new gateway 110 .
  • the Registration Service can include, in effect, a schematic of the BTA's topology. This is useful for various maintenance and monitoring functions, such as for reconstructing a network where many nodes have been corrupted.
  • a basic Registration Service is bundled with the gateway 110 but there are many options for a Solution Provider to provide their own service.
  • the only constraint is that the raw messages being passed between the service and its local gateway adhere to the standard raw administrative messages that are defined for Registration. Included in this set of raw administrative messages are a set of specific queries so that the network topology can be explored.
  • Privileges are a mechanism for refining the topology of a BTA network.
  • the Registration Service and the registration information in a local gateway's configuration data store indicate the remote gateways with which a local gateway can communicate.
  • the privileges in the local configuration data define what action and access remote gateways can perform in relationship to the local gateway with which they can communicate .
  • an initial set of privileges will be contained in the initial instantiation of a gateway 110 .
  • These initial privileges will, at a minimum, allow a Solution Provider read/write access to much of the local gateway's meta-data.
  • These initial privileges can also provide read/write access to a Member Administrator for certain sections of the meta-data and message data store, while denying similar write access to the Solution Provider or any other remote gateway for those sections. This arrangement ensures that aspects of the data store will remain private.
  • Privileges can be updated through the appropriate administrative message.
  • gateways 110 In a gateway network, all aspects of monitoring and maintenance, including bug tracking, can be done remotely. Maintenance that does not require human participation can handled through administrative messaging. Normal maintenance activity includes, for example, updating a gateway database, remote querying of the message database, etc. Remote UI-based tools can be provided for maintenance activities that do require human participation.
  • the remote monitoring and maintenance capabilities are designed to work over diverse WAN networks such as the public Internet. For example, in addition to traditional active network monitoring mechanisms, gateways 110 support passive or reactive mechanisms in order to provide effective monitoring in a WAN.
  • the Viewer is a local UI-based application that can be embedded with every gateway 110 . It provides capabilities to monitor the processing of a message within a gateway 110 and a testing framework to setup debugging, tracing and testing scenarios.
  • a browser-based remote access tool can be bundled with the gateway 110 to provide the ability to operte the Viewer remotely.
  • a set of administrative messages are provided to provide data for active monitoring of gateway states. These range from simple pings to ascertain that a gateway 110 is up to a set of canned data frame requests that can provide an operational profile of a gateway 110 . In order to provide this profile, there are a set of state variables that can be maintained in the configuration data store that are consistently updated by a local gateway.
  • the normal communication channels that utilize abstract queues may not work.
  • JMX standrad industry network monitoring and messaging channel that can be accessed through a standard interface
  • the gateway 110 preferably includes capabilities to handle a set of monitoring messages using the JMX interface.
  • this JMX channel is useful because it is an industry standard, and the gateway JMX messages can be incorporated into existing network monitoring facilities.
  • the use of JMx in a gateway-based BTA is primarily active monitoring. Regular heartbeats are sent to a gateway 110 being monitored to make sure that it is up and operating. Direct requests can be made of a gateway 110 to make sure key components, such as each abstract queue, are also up and operating.
  • a gateway-based BTA can bundle a monitoring console to display the results of JMX monitoring.
  • Reactive monitoring also makes use of both standard administrative messages and JMX. It differs from active monitoring as it relies on indirect detection of an error condition. For example, if the SEND Queue 920 in a sending gateway gets an error message that it cannot reach the receiving gateway, a message can be sent to a monitoring service that there is a possible problem. At that point, the monitoring service can initiate active monitoring to investigate the problem
  • a gateway 110 can offer special services to deal with either deliberate or accident situations in which a receiving gateway is not operating. For example, if a gateway 110 is not active but has requested the availability of a “post office box,” then messages directed to it will automatically be redirected to the store and forward service, which holds the messages until the receiving gateway is up again and requests its mail.
  • a system for communicating transaction information can comprise 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.
  • 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.
  • the one or more remote gateways can also be 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.
  • the transaction may comprise a compound transaction, 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.
  • the predetermined condition may be a time limit.
  • Each of the one or more local gateways and the one or more remote gateways can be configured to determine a status of a component of the compound transaction or to exchange a status of a component of the compound transaction.
  • the transaction can be supported by the one or more local application devices, 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.
  • the system can be configured to facilitate an initiation and a completion of the transaction automatically.
  • the transaction can be 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.
  • the transaction can be 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.
  • the transaction can also associated with at least one of an energy industry, a utility industry, a manufacturing industry, an automotive industry, and a pharmaceutical industry.
  • the plurality of gateways can be associated with a transaction administrator wherein the transaction administrator is configured to administer each gateway and to administer each gateway via automated messages.
  • the plurality of gateways can comprise processing modules that are configured to be updated using secure administrative messages, and configuration information of each gateway can be configured to be updated using the secure administrative messages.
  • Transaction information passed between the plurality of gateways may include at least one of unique transaction ID tags, envelope ID tags, and message ID tags.
  • An administrative message can be 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.
  • Each gateway can include information configured to form a fully distributed data store in aggregate with information associated with other gateways.
  • An administrative message can be configured to query the fully distributed data store, wherein information is generated into a standardized XML document.
  • the standardized XML documents generated from information contained in two or more gateways can be combined into one standardized XML document that is used for non-repudiation of a business transaction.
  • Customized processes can be associated with one or more transactions and be distributed via administrative messages.
  • the administrative messages can be 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.
  • a gateway can comprise 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.
  • the information queue module is configured to communicate transaction information in one or more local data formats with one or more local client applications
  • the formatter module can be configured to transform the transaction information in a data format associated with the gateway into the one or more local data formats, and the mapping module can be configured to convert the normative transaction information in the common data format into a data format associated with the gateway.
  • the message processing module can configured to process the envelope for the normative transaction information in the common data format, and the message processing module can be configured to execute predetermined next actions and processing demands imposed by the at least one other gateway.
  • the one or more communication modules can be configured to receive the gateway message provided by the at least one other gateway for completing the transaction.
  • the gateway can also include 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.
  • the data format associated with the gateway can be XML.
  • the gateway can further include 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.
  • the gateway may also include 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.
  • the validation module can be configured to validate the normative transaction information to ensure that the normative transaction information includes data required by mandatory data fields.
  • the validation module can also be configured to validate the normative transaction information to ensure that the normative transaction information includes data required by cross-data field constraints.
  • the gateway can also include 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.
  • the one or more communication modules can be configured to record transmitted gateway messages and transaction states of the transmitted gateway messages.
  • the one or more communication modules can also be configured to record received gateway messages and transaction states of received gateway messages.
  • the gateway can be configured to notify the information queue module and the one or more local client applications that a gateway message has been transmitted.
  • the gateway can also be configured to encrypt one or more blocks of normative transaction information, and wherein the envelope is configured to provide descriptive information of the encryption. More particularly, the gateway can be configured to digitally sign the one or more blocks of normative transaction information, wherein the envelope is configured to provide descriptive information of the digital signature.
  • the envelope of the normative transaction information can include message processing history for the gateway message.
  • the message processing history can comprise information components, and wherein the gateway is configured to process individual information components of the message processing history.
  • the message processing history can include a record of a change in state of the gateway message.
  • the envelope of the normative transaction information can include addressing and routing information for the gateway message.
  • the envelope of the normative transaction information may also include transaction history of the transaction.
  • the gateway can be in communication with a data storage module, wherein the data storage module is configured to store information transmitted and received by the gateway.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Theoretical Computer Science (AREA)
  • Computing Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Software Systems (AREA)
  • Accounting & Taxation (AREA)
  • Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Tourism & Hospitality (AREA)
  • Quality & Reliability (AREA)
  • Data Mining & Analysis (AREA)
  • Operations Research (AREA)
  • Finance (AREA)
  • Library & Information Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)
  • Debugging And Monitoring (AREA)
US11/566,185 2005-12-01 2006-12-01 System and method for exchanging information among exchange applications Abandoned US20070180150A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US11/566,185 US20070180150A1 (en) 2005-12-01 2006-12-01 System and method for exchanging information among exchange applications
US13/212,967 US8838737B2 (en) 2005-12-01 2011-08-18 System and method for exchanging information among exchange applications

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US74104605P 2005-12-01 2005-12-01
US11/566,185 US20070180150A1 (en) 2005-12-01 2006-12-01 System and method for exchanging information among exchange applications

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/212,967 Continuation US8838737B2 (en) 2005-12-01 2011-08-18 System and method for exchanging information among exchange applications

Publications (1)

Publication Number Publication Date
US20070180150A1 true US20070180150A1 (en) 2007-08-02

Family

ID=38092819

Family Applications (10)

Application Number Title Priority Date Filing Date
US11/566,185 Abandoned US20070180150A1 (en) 2005-12-01 2006-12-01 System and method for exchanging information among exchange applications
US11/566,175 Active 2029-01-01 US8620989B2 (en) 2005-12-01 2006-12-01 System and method for exchanging information among exchange applications
US11/566,186 Expired - Fee Related US7979569B2 (en) 2005-12-01 2006-12-01 System and method for exchanging information among exchange applications
US11/566,182 Expired - Fee Related US8838668B2 (en) 2005-12-01 2006-12-01 System and method for exchanging information among exchange applications
US11/566,177 Abandoned US20070171923A1 (en) 2005-12-01 2006-12-01 System and method for exchanging information among exchange applications
US11/566,167 Abandoned US20070168301A1 (en) 2005-12-01 2006-12-01 System and method for exchanging information among exchange applications
US13/212,967 Expired - Fee Related US8838737B2 (en) 2005-12-01 2011-08-18 System and method for exchanging information among exchange applications
US13/418,240 Expired - Fee Related US9742880B2 (en) 2005-12-01 2012-03-12 System and method for exchanging information among exchange applications
US13/419,298 Expired - Fee Related US9860348B2 (en) 2005-12-01 2012-03-13 System and method for exchanging information among exchange applications
US14/139,517 Abandoned US20140341217A1 (en) 2005-12-01 2013-12-23 System and method for exchanging information among exchange applications

Family Applications After (9)

Application Number Title Priority Date Filing Date
US11/566,175 Active 2029-01-01 US8620989B2 (en) 2005-12-01 2006-12-01 System and method for exchanging information among exchange applications
US11/566,186 Expired - Fee Related US7979569B2 (en) 2005-12-01 2006-12-01 System and method for exchanging information among exchange applications
US11/566,182 Expired - Fee Related US8838668B2 (en) 2005-12-01 2006-12-01 System and method for exchanging information among exchange applications
US11/566,177 Abandoned US20070171923A1 (en) 2005-12-01 2006-12-01 System and method for exchanging information among exchange applications
US11/566,167 Abandoned US20070168301A1 (en) 2005-12-01 2006-12-01 System and method for exchanging information among exchange applications
US13/212,967 Expired - Fee Related US8838737B2 (en) 2005-12-01 2011-08-18 System and method for exchanging information among exchange applications
US13/418,240 Expired - Fee Related US9742880B2 (en) 2005-12-01 2012-03-12 System and method for exchanging information among exchange applications
US13/419,298 Expired - Fee Related US9860348B2 (en) 2005-12-01 2012-03-13 System and method for exchanging information among exchange applications
US14/139,517 Abandoned US20140341217A1 (en) 2005-12-01 2013-12-23 System and method for exchanging information among exchange applications

Country Status (4)

Country Link
US (10) US20070180150A1 (fr)
EP (6) EP1955471A4 (fr)
CA (6) CA2631761A1 (fr)
WO (6) WO2008048304A2 (fr)

Cited By (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010025264A1 (en) * 1998-07-31 2001-09-27 Michael Deaddio Object oriented system for managing complex financial instruments
US20070168301A1 (en) * 2005-12-01 2007-07-19 Firestar Software, Inc. System and method for exchanging information among exchange applications
US20070214419A1 (en) * 2006-03-01 2007-09-13 Ashish Jain Integrated service creation and execution platforms for the converged networks
US20070288254A1 (en) * 2006-05-08 2007-12-13 Firestar Software, Inc. System and method for exchanging transaction information using images
US20080172654A1 (en) * 2007-01-15 2008-07-17 Andreas Frohlich Monitoring a Software System
US20100011096A1 (en) * 2008-07-10 2010-01-14 Blackwave Inc. Distributed Computing With Multiple Coordinated Component Collections
US20100228748A1 (en) * 2009-02-23 2010-09-09 International Business Machines Corporation Data subset retrieval from a queued message
US20100228766A1 (en) * 2009-02-23 2010-09-09 International Business Machines Corporations Queue message retrieval by selection criteria
US20100235192A1 (en) * 2009-03-11 2010-09-16 Nextgen Healthcare Information Systems, Inc. Health Quality Measures Systems and Methods
US20100332240A1 (en) * 2009-06-24 2010-12-30 Microsoft Corporation Decentralized account digest using signed electronic receipts
US20110047415A1 (en) * 2009-08-19 2011-02-24 Oracle International Corporation Debugging of business flows deployed in production servers
US20110208746A1 (en) * 2010-02-22 2011-08-25 Brignoli Winthrop A Systems and methods for message-based distributed computing
US20120065998A1 (en) * 2009-03-11 2012-03-15 Nextgen Healthcare Information Systems, Inc. Health Quality Measures Systems and Methods
US8429622B2 (en) 2010-04-15 2013-04-23 Oracle International Corporation Business process debugger with parallel-step debug operation
US20140032774A1 (en) * 2012-07-30 2014-01-30 Microsoft Corporation Client-emulating Gateways for Communication Network Migration
US20140089421A1 (en) * 2012-09-25 2014-03-27 Deep River Ventures, Llc Methods, Systems, and Program Products for Sharing a Data Object in a Data Store Via a Communication
US9342806B2 (en) 2013-02-28 2016-05-17 P800X, Llc Method and system for automated project management
US10013158B1 (en) 2012-09-22 2018-07-03 Sitting Man, Llc Methods, systems, and computer program products for sharing a data object in a data store via a communication
US10015122B1 (en) 2012-10-18 2018-07-03 Sitting Man, Llc Methods and computer program products for processing a search
US10021052B1 (en) 2012-09-22 2018-07-10 Sitting Man, Llc Methods, systems, and computer program products for processing a data object identification request in a communication
US10019135B1 (en) 2012-10-18 2018-07-10 Sitting Man, Llc Methods, and computer program products for constraining a communication exchange
US10033672B1 (en) 2012-10-18 2018-07-24 Sitting Man, Llc Methods and computer program products for browsing using a communicant identifier
US10158590B1 (en) 2010-07-09 2018-12-18 Gummarus LLC Methods, systems, and computer program products for processing a request for a resource in a communication
US10171392B1 (en) 2010-07-09 2019-01-01 Gummarus LLC Methods, systems, and computer program products for processing a request for a resource in a communication
US10212112B1 (en) 2010-07-09 2019-02-19 Gummarus LLC Methods, systems, and computer program products for processing a request for a resource in a communication
US10419374B1 (en) 2010-07-09 2019-09-17 Gummarus, Llc Methods, systems, and computer program products for processing a request for a resource in a communication
US10496942B2 (en) 2013-02-28 2019-12-03 P800X, Llc Method and system for automated project management of excavation requests
US10885051B1 (en) * 2008-03-07 2021-01-05 Infor (Us), Inc. Automatic data warehouse generation using automatically generated schema

Families Citing this family (400)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9427520B2 (en) 2005-02-11 2016-08-30 Carefusion 303, Inc. Management of pending medication orders
US9600633B2 (en) 2000-05-18 2017-03-21 Carefusion 303, Inc. Distributed remote asset and medication management drug delivery system
US7860583B2 (en) 2004-08-25 2010-12-28 Carefusion 303, Inc. System and method for dynamically adjusting patient therapy
US10353856B2 (en) * 2011-03-17 2019-07-16 Carefusion 303, Inc. Scalable communication system
US10062457B2 (en) 2012-07-26 2018-08-28 Carefusion 303, Inc. Predictive notifications for adverse patient events
US9741001B2 (en) 2000-05-18 2017-08-22 Carefusion 303, Inc. Predictive medication safety
US11087873B2 (en) 2000-05-18 2021-08-10 Carefusion 303, Inc. Context-aware healthcare notification system
US7389531B2 (en) * 2000-06-16 2008-06-17 Entriq Inc. Method and system to dynamically present a payment gateway for content distributed via a network
US6961858B2 (en) * 2000-06-16 2005-11-01 Entriq, Inc. Method and system to secure content for distribution via a network
US7991697B2 (en) * 2002-12-16 2011-08-02 Irdeto Usa, Inc. Method and system to digitally sign and deliver content in a geographically controlled manner via a network
US20050229003A1 (en) 2004-04-09 2005-10-13 Miles Paschini System and method for distributing personal identification numbers over a computer network
US10205721B2 (en) 2002-12-10 2019-02-12 Ewi Holdings, Inc. System and method for distributing personal identification numbers over a computer network
US7706540B2 (en) 2002-12-16 2010-04-27 Entriq, Inc. Content distribution using set of session keys
ES2409936T3 (es) 2003-01-31 2013-06-28 Good Technology Corporation Recuperación asíncrona de datos en tiempo real
US7131578B2 (en) 2003-05-28 2006-11-07 Ewi Holdings, Inc. System and method for electronic prepaid account replenishment
US7280644B2 (en) 2004-12-07 2007-10-09 Ewi Holdings, Inc. Transaction processing platform for faciliating electronic distribution of plural prepaid services
US11599873B2 (en) 2010-01-08 2023-03-07 Blackhawk Network, Inc. Systems and methods for proxy card and/or wallet redemption card transactions
US11475436B2 (en) 2010-01-08 2022-10-18 Blackhawk Network, Inc. System and method for providing a security code
US8340077B2 (en) 2005-06-15 2012-12-25 At&T Intellectual Property I, Lp Providing operation services for networks via operations service servers
US7788401B2 (en) 2005-06-15 2010-08-31 At&T Intellectual Property I, L.P. Operations switches and systems for providing operations service for networks
US8175891B2 (en) * 2005-10-18 2012-05-08 Walgreen Co. System for separating and distributing pharmacy order processing for compound medication
US8315887B2 (en) * 2005-10-18 2012-11-20 Walgreen Co. System for separating and distributing pharmacy order processing for specialty medication
US8311891B2 (en) * 2005-10-18 2012-11-13 Walgreen Co. System for separating and distributing pharmacy order processing for medication payments
US20070088569A1 (en) * 2005-10-18 2007-04-19 Walgreen Co. System for separating and distributing pharmacy order processing for prescription verification
US8666780B2 (en) * 2005-10-18 2014-03-04 Walgreen Co. System for separating and distributing pharmacy order processing
US20070088590A1 (en) * 2005-10-18 2007-04-19 Walgreen Co. System for separating and distributing pharmacy order processing for out of stock medication
CA2631197C (fr) 2005-11-28 2013-01-29 Commvault Systems, Inc. Systemes et procedes de gestion de donnees
US8930496B2 (en) * 2005-12-19 2015-01-06 Commvault Systems, Inc. Systems and methods of unified reconstruction in storage systems
US20200257596A1 (en) 2005-12-19 2020-08-13 Commvault Systems, Inc. Systems and methods of unified reconstruction in storage systems
FI20060046A0 (fi) * 2006-01-19 2006-01-19 Markku Matias Rautiola Piirikytkentäisen langattoman pääsyverkon liittäminen IP-multimedia-alijärjestelmään
US8788354B2 (en) * 2006-04-20 2014-07-22 Sybase 365, Inc. System and method for operator charging gateway
US7971187B2 (en) * 2006-04-24 2011-06-28 Microsoft Corporation Configurable software stack
US10838714B2 (en) 2006-04-24 2020-11-17 Servicenow, Inc. Applying packages to configure software stacks
US10296895B2 (en) 2010-01-08 2019-05-21 Blackhawk Network, Inc. System for processing, activating and redeeming value added prepaid cards
US8131644B2 (en) 2006-08-29 2012-03-06 Sap Ag Formular update
US8065661B2 (en) 2006-08-29 2011-11-22 Sap Ag Test engine
US20080059630A1 (en) * 2006-08-29 2008-03-06 Juergen Sattler Assistant
US7823124B2 (en) * 2006-08-29 2010-10-26 Sap Ag Transformation layer
US20080082517A1 (en) * 2006-08-29 2008-04-03 Sap Ag Change assistant
US20080071555A1 (en) * 2006-08-29 2008-03-20 Juergen Sattler Application solution proposal engine
US7912800B2 (en) 2006-08-29 2011-03-22 Sap Ag Deduction engine to determine what configuration management scoping questions to ask a user based on responses to one or more previous questions
US7831568B2 (en) * 2006-08-29 2010-11-09 Sap Ag Data migration
US20080059537A1 (en) * 2006-08-29 2008-03-06 Juergen Sattler Content subscription
US7831637B2 (en) * 2006-08-29 2010-11-09 Sap Ag System on the fly
US7827528B2 (en) * 2006-08-29 2010-11-02 Sap Ag Delta layering
US7908589B2 (en) 2006-08-29 2011-03-15 Sap Ag Deployment
WO2008085201A2 (fr) 2006-12-29 2008-07-17 Prodea Systems, Inc. Gestion de restauration et de traitement de secours de fichiers dans des emplacements de mémoire distants à l'aide d'un dispositif de passerelle multiservice côté locaux d'abonné
US9569587B2 (en) 2006-12-29 2017-02-14 Kip Prod Pi Lp Multi-services application gateway and system employing the same
US11316688B2 (en) 2006-12-29 2022-04-26 Kip Prod P1 Lp Multi-services application gateway and system employing the same
US9602880B2 (en) 2006-12-29 2017-03-21 Kip Prod P1 Lp Display inserts, overlays, and graphical user interfaces for multimedia systems
US20170344703A1 (en) 2006-12-29 2017-11-30 Kip Prod P1 Lp Multi-services application gateway and system employing the same
US11783925B2 (en) 2006-12-29 2023-10-10 Kip Prod P1 Lp Multi-services application gateway and system employing the same
US8977255B2 (en) 2007-04-03 2015-03-10 Apple Inc. Method and system for operating a multi-function portable electronic device using voice-activation
US8688850B2 (en) * 2007-04-10 2014-04-01 International Business Machines Corporation Method for inter-site data stream transfer in cooperative data stream processing
US8238889B1 (en) 2007-04-10 2012-08-07 Marvell International Ltd. Server for wireless application service system
US20080285731A1 (en) * 2007-05-15 2008-11-20 Say2Go, Inc. System and method for near-real-time voice messaging
US7904389B2 (en) * 2007-05-30 2011-03-08 Visa U.S.A. Inc. Real time account update
US7788542B2 (en) * 2007-05-31 2010-08-31 Red Hat, Inc. Debugging in a distributed system
US8752065B2 (en) * 2007-05-31 2014-06-10 Red Hat, Inc. Rules engine for a persistent message store
US7937497B2 (en) * 2007-05-31 2011-05-03 Red Hat, Inc. Apparatus for selectively copying at least portions of messages in a distributed computing system
US9591086B2 (en) 2007-07-25 2017-03-07 Yahoo! Inc. Display of information in electronic communications
US8819105B2 (en) * 2007-11-07 2014-08-26 Barclays Capital Inc. Method and system for data formatting
US8489668B2 (en) * 2007-11-13 2013-07-16 Intuit Inc. Open platform for managing an agent network
US20090138891A1 (en) * 2007-11-27 2009-05-28 Winig Robert J Integrating service-oriented architecture applications with a common messaging interface
US9584343B2 (en) 2008-01-03 2017-02-28 Yahoo! Inc. Presentation of organized personal and public data using communication mediums
US7986707B2 (en) * 2008-02-11 2011-07-26 International Business Machines Corporation Method and system for rules based workflow of media services
US20090222747A1 (en) * 2008-02-29 2009-09-03 Darrell Reginald May Designation of delegate for modifying an electronic meeting definition defined using electronic calendaring software
US9613079B2 (en) * 2008-03-14 2017-04-04 Palo Alto Research Center Incorporated System and method for providing a synchronized data rerepresentation
US9652309B2 (en) * 2008-05-15 2017-05-16 Oracle International Corporation Mediator with interleaved static and dynamic routing
US8250146B2 (en) * 2008-05-15 2012-08-21 Sap Ag Service adaptation machine
US8370851B2 (en) * 2008-06-06 2013-02-05 Microsoft Corporation Conversational parallelism for message processing
US8261286B1 (en) * 2008-06-18 2012-09-04 Amazon Technologies, Inc. Fast sequential message store
US10362131B1 (en) 2008-06-18 2019-07-23 Amazon Technologies, Inc. Fault tolerant message delivery
US20100228699A1 (en) * 2008-06-20 2010-09-09 Transenda International, Llc System and method for interacting with clinical trial operational data
US20100008358A1 (en) * 2008-07-10 2010-01-14 Utah State University System and Methods for Content Insertion within a Router
US8706622B2 (en) * 2008-08-05 2014-04-22 Visa U.S.A. Inc. Account holder demand account update
US8689008B2 (en) * 2008-08-05 2014-04-01 Net.Orange, Inc. Operating system
US20140257845A9 (en) * 2008-08-05 2014-09-11 Vasu Rangadass Operating System
US9104662B2 (en) * 2008-08-08 2015-08-11 Oracle International Corporation Method and system for implementing parallel transformations of records
US8160908B2 (en) * 2008-08-21 2012-04-17 At&T Intellectual Property I, L.P. Supply chain management
US8645843B2 (en) * 2008-08-29 2014-02-04 International Business Machines Corporation Supporting role-based access control in component-based software systems
US9444793B2 (en) 2008-09-15 2016-09-13 Vaultive Ltd. System, apparatus and method for encryption and decryption of data transmitted over a network
US8949344B2 (en) * 2008-09-15 2015-02-03 Microsoft Corporation Asynchronous queued messaging for web applications
JP5369587B2 (ja) * 2008-09-30 2013-12-18 富士通株式会社 情報処理装置、情報処理システム、方法、およびプログラム
US8135659B2 (en) 2008-10-01 2012-03-13 Sap Ag System configuration comparison to identify process variation
US20100106551A1 (en) * 2008-10-24 2010-04-29 Oskari Koskimies Method, system, and apparatus for process management
US9178842B2 (en) * 2008-11-05 2015-11-03 Commvault Systems, Inc. Systems and methods for monitoring messaging applications for compliance with a policy
US8396893B2 (en) * 2008-12-11 2013-03-12 Sap Ag Unified configuration of multiple applications
US8255429B2 (en) 2008-12-17 2012-08-28 Sap Ag Configuration change without disruption of incomplete processes
EP2361417B1 (fr) * 2008-12-18 2022-02-16 BlackBerry Limited Procédés et dispositif de partitionnement de données sensible au contenu et de déduplication de données
US8200278B2 (en) * 2009-01-08 2012-06-12 Red Hat, Inc. Adding SMS as a transport type for an enterprise service bus
US8453118B2 (en) * 2009-02-09 2013-05-28 Ricoh Company, Ltd. Automated multi-operating system testing with virtualization
US8606705B2 (en) * 2009-02-13 2013-12-10 Bank Of America Corporation Systems, methods and computer program products for managing payment processes in a comprehensive payment hub system
US8606706B2 (en) * 2009-02-13 2013-12-10 Bank Of America Corporation Systems, methods and computer program products for standardization of payment requests to facilitate comprehensive payment hub processing
US20100211499A1 (en) * 2009-02-13 2010-08-19 Bank Of America Corporation Systems, methods and computer program products for optimizing routing of financial payments
US20100211495A1 (en) * 2009-02-13 2010-08-19 Bank Of America Corporation Systems, methods and computer program products for improving foreign currency exchange in a comprehensive payment hub system
US8326931B2 (en) 2009-02-27 2012-12-04 Research In Motion Limited Systems and methods for protecting header fields in a message
US8499045B2 (en) * 2009-02-27 2013-07-30 Research In Motion Limited Systems and methods for protecting header fields in a message
US8254391B2 (en) 2009-04-04 2012-08-28 Oracle International Corporation Method and system for performing blocking of messages on errors in message stream
US9124448B2 (en) * 2009-04-04 2015-09-01 Oracle International Corporation Method and system for implementing a best efforts resequencer
US8578218B2 (en) * 2009-04-04 2013-11-05 Oracle International Corporation Method and system for implementing a scalable, high-performance, fault-tolerant locking mechanism in a multi-process environment
US8661083B2 (en) * 2009-04-04 2014-02-25 Oracle International Corporation Method and system for implementing sequence start and increment values for a resequencer
US20100254388A1 (en) * 2009-04-04 2010-10-07 Oracle International Corporation Method and system for applying expressions on message payloads for a resequencer
US8289981B1 (en) * 2009-04-29 2012-10-16 Trend Micro Incorporated Apparatus and method for high-performance network content processing
CN102460393B (zh) * 2009-05-01 2014-05-07 思杰系统有限公司 用于在虚拟存储资源之间建立云桥的系统和方法
EP2438571A4 (fr) 2009-06-02 2014-04-30 Yahoo Inc Carnet d'adresses à peuplement automatique
JP2011008701A (ja) * 2009-06-29 2011-01-13 Sony Corp 情報処理サーバ、情報処理装置、および情報処理方法
US8990323B2 (en) 2009-07-08 2015-03-24 Yahoo! Inc. Defining a social network model implied by communications data
US20110191717A1 (en) 2010-02-03 2011-08-04 Xobni Corporation Presenting Suggestions for User Input Based on Client Device Characteristics
US7930430B2 (en) 2009-07-08 2011-04-19 Xobni Corporation Systems and methods to provide assistance during address input
US9721228B2 (en) 2009-07-08 2017-08-01 Yahoo! Inc. Locally hosting a social network using social data stored on a user's computer
KR101496649B1 (ko) * 2009-08-21 2015-03-02 삼성전자주식회사 복합 네트워크 망을 통한 외부 디바이스의 기능 공유 방법 및 그 장치
US8938533B1 (en) * 2009-09-10 2015-01-20 AppDynamics Inc. Automatic capture of diagnostic data based on transaction behavior learning
US9167028B1 (en) * 2009-09-10 2015-10-20 AppDynamics, Inc. Monitoring distributed web application transactions
US10230611B2 (en) * 2009-09-10 2019-03-12 Cisco Technology, Inc. Dynamic baseline determination for distributed business transaction
US8904169B2 (en) 2009-09-15 2014-12-02 Symantec Corporation Just in time trust establishment and propagation
US8713325B2 (en) * 2011-04-19 2014-04-29 Authentify Inc. Key management using quasi out of band authentication architecture
US8719905B2 (en) 2010-04-26 2014-05-06 Authentify Inc. Secure and efficient login and transaction authentication using IPhones™ and other smart mobile communication devices
US8549601B2 (en) * 2009-11-02 2013-10-01 Authentify Inc. Method for secure user and site authentication
US8745699B2 (en) 2010-05-14 2014-06-03 Authentify Inc. Flexible quasi out of band authentication architecture
US8806592B2 (en) 2011-01-21 2014-08-12 Authentify, Inc. Method for secure user and transaction authentication and risk management
US8789153B2 (en) * 2010-01-27 2014-07-22 Authentify, Inc. Method for secure user and transaction authentication and risk management
US8458774B2 (en) * 2009-11-02 2013-06-04 Authentify Inc. Method for secure site and user authentication
US8769784B2 (en) 2009-11-02 2014-07-08 Authentify, Inc. Secure and efficient authentication using plug-in hardware compatible with desktops, laptops and/or smart mobile communication devices such as iPhones
US10581834B2 (en) 2009-11-02 2020-03-03 Early Warning Services, Llc Enhancing transaction authentication with privacy and security enhanced internet geolocation and proximity
US20110107084A1 (en) * 2009-11-05 2011-05-05 Verizon Patent And Licensing, Inc. System for and method for relaying messages
US9514466B2 (en) 2009-11-16 2016-12-06 Yahoo! Inc. Collecting and presenting data including links from communications sent to or from a user
US8584087B2 (en) 2009-12-11 2013-11-12 Sap Ag Application configuration deployment monitor
US9760866B2 (en) 2009-12-15 2017-09-12 Yahoo Holdings, Inc. Systems and methods to provide server side profile information
US8683498B2 (en) * 2009-12-16 2014-03-25 Ebay Inc. Systems and methods for facilitating call request aggregation over a network
US10037526B2 (en) * 2010-01-08 2018-07-31 Blackhawk Network, Inc. System for payment via electronic wallet
EP2521999A4 (fr) 2010-01-08 2015-01-07 Blackhawk Network Inc Système de traitement, d'activation et de remboursement de cartes prépayées à valeur ajoutée
EP2537295A1 (fr) * 2010-02-19 2012-12-26 Nokia Siemens Networks Oy Procédé et dispositif pour transporter des messages oam sur un réseau inter-opérateur
WO2011113042A2 (fr) * 2010-03-12 2011-09-15 Copiun, Inc. Catalogue distribué, mémoire de données et indexation
WO2011116087A2 (fr) 2010-03-16 2011-09-22 Copiun, Inc. Déduplication de données distribuée et hautement évolutive
TW201220952A (en) 2010-03-29 2012-05-16 Koninkl Philips Electronics Nv Network of heterogeneous devices including at least one outdoor lighting fixture node
US8375066B2 (en) 2010-04-26 2013-02-12 International Business Machines Corporation Generating unique identifiers
CA2800163A1 (fr) * 2010-05-21 2011-11-24 Vaultive Ltd. Systeme et procede pour commander et controler l'acces a des applications de traitement de donnees
US8620935B2 (en) 2011-06-24 2013-12-31 Yahoo! Inc. Personalizing an online service based on data collected for a user of a computing device
US8972257B2 (en) 2010-06-02 2015-03-03 Yahoo! Inc. Systems and methods to present voice message information to a user of a computing device
US8560698B2 (en) * 2010-06-27 2013-10-15 International Business Machines Corporation Allocating unique identifiers using metadata
CN103229161B (zh) 2010-08-24 2016-01-20 科派恩股份有限公司 连续接入网关和去重数据缓存服务器
AU2011293250A1 (en) 2010-08-27 2013-03-21 Blackhawk Network, Inc. Prepaid card with savings feature
US9235843B2 (en) * 2010-09-27 2016-01-12 T-Mobile Usa, Inc. Insertion of user information into headers to enable targeted responses
US9563751B1 (en) * 2010-10-13 2017-02-07 The Boeing Company License utilization management system service suite
US8904356B2 (en) 2010-10-20 2014-12-02 International Business Machines Corporation Collaborative software debugging in a distributed system with multi-member variable expansion
US9009673B2 (en) 2010-10-21 2015-04-14 International Business Machines Corporation Collaborative software debugging in a distributed system with collaborative step over operation
US8671393B2 (en) 2010-10-21 2014-03-11 International Business Machines Corporation Collaborative software debugging in a distributed system with client-specific dynamic breakpoints
US8972945B2 (en) 2010-10-21 2015-03-03 International Business Machines Corporation Collaborative software debugging in a distributed system with client-specific access control
US8990775B2 (en) 2010-11-10 2015-03-24 International Business Machines Corporation Collaborative software debugging in a distributed system with dynamically displayed chat sessions
US9411709B2 (en) 2010-11-10 2016-08-09 International Business Machines Corporation Collaborative software debugging in a distributed system with client-specific event alerts
US8850397B2 (en) * 2010-11-10 2014-09-30 International Business Machines Corporation Collaborative software debugging in a distributed system with client-specific display of local variables
US8566577B2 (en) * 2010-11-30 2013-10-22 Blackberry Limited Method and device for storing secured sent message data
US8863227B2 (en) * 2011-01-05 2014-10-14 Futurewei Technologies, Inc. Method and apparatus to create and manage a differentiated security framework for content oriented networks
KR101759254B1 (ko) * 2011-01-18 2017-07-19 삼성전자주식회사 헬스케어 시스템, 헬스케어 제어 장치 및 방법
US9832183B2 (en) 2011-04-19 2017-11-28 Early Warning Services, Llc Key management using quasi out of band authentication architecture
US8806438B2 (en) 2011-04-20 2014-08-12 International Business Machines Corporation Collaborative software debugging in a distributed system with variable-specific messages
US8739127B2 (en) 2011-04-20 2014-05-27 International Business Machines Corporation Collaborative software debugging in a distributed system with symbol locking
US8656360B2 (en) 2011-04-20 2014-02-18 International Business Machines Corporation Collaborative software debugging in a distributed system with execution resumption on consensus
US9137104B2 (en) * 2011-05-26 2015-09-15 Kaseya Limited Method and apparatus of performing remote management of a managed machine
US8806204B2 (en) 2011-06-20 2014-08-12 Liaison Technologies, Inc. Systems and methods for maintaining data security across multiple active domains
US10078819B2 (en) 2011-06-21 2018-09-18 Oath Inc. Presenting favorite contacts information to a user of a computing device
US8756577B2 (en) 2011-06-28 2014-06-17 International Business Machines Corporation Collaborative software debugging in a distributed system with private debug sessions
US9747583B2 (en) 2011-06-30 2017-08-29 Yahoo Holdings, Inc. Presenting entity profile information to a user of a computing device
US20130024345A1 (en) * 2011-07-21 2013-01-24 Chicago Mercantile Exchange Inc. Interest Accrual Provisions For Multi-Laterally Traded Contracts
US9076183B2 (en) 2011-07-21 2015-07-07 Chicago Mercantile Exchange Inc. Multi-laterally traded contract settlement mode modification
EP2798793B1 (fr) * 2011-12-29 2021-11-17 British Telecommunications public limited company Gestion de système distribué
SG11201403861XA (en) 2012-01-05 2014-08-28 Visa Int Service Ass Data protection with translation
US8812438B2 (en) * 2012-01-20 2014-08-19 Salesforce.Com, Inc. System, method and computer program product for synchronizing data using data identifying messages
US20130191136A1 (en) * 2012-01-23 2013-07-25 Affiliated Computer Systems, Inc. Provider Data Management and Routing
US8880463B2 (en) * 2012-01-25 2014-11-04 Sap Se Standardized framework for reporting archived legacy system data
US9311598B1 (en) 2012-02-02 2016-04-12 AppDynamics, Inc. Automatic capture of detailed analysis information for web application outliers with very low overhead
US9760584B2 (en) 2012-03-16 2017-09-12 Oracle International Corporation Systems and methods for supporting inline delegation of middle-tier transaction logs to database
US10133596B2 (en) 2012-03-16 2018-11-20 Oracle International Corporation System and method for supporting application interoperation in a transactional middleware environment
US8824750B2 (en) * 2012-03-19 2014-09-02 Next Level Security Systems, Inc. Distributive facial matching and notification system
US10977285B2 (en) 2012-03-28 2021-04-13 Verizon Media Inc. Using observations of a person to determine if data corresponds to the person
US11042870B2 (en) 2012-04-04 2021-06-22 Blackhawk Network, Inc. System and method for using intelligent codes to add a stored-value card to an electronic wallet
US9628438B2 (en) * 2012-04-06 2017-04-18 Exablox Consistent ring namespaces facilitating data storage and organization in network infrastructures
US9354998B2 (en) * 2012-05-04 2016-05-31 Aegis.Net, Inc. Automated conformance and interoperability test lab
US9348927B2 (en) * 2012-05-07 2016-05-24 Smart Security Systems Llc Systems and methods for detecting, identifying and categorizing intermediate nodes
US8874551B2 (en) * 2012-05-09 2014-10-28 Sap Se Data relations and queries across distributed data sources
US9325676B2 (en) 2012-05-24 2016-04-26 Ip Ghoster, Inc. Systems and methods for protecting communications between nodes
US10778659B2 (en) 2012-05-24 2020-09-15 Smart Security Systems Llc System and method for protecting communications
US8954602B2 (en) * 2012-05-31 2015-02-10 Sap Se Facilitating communication between enterprise software applications
US9716691B2 (en) 2012-06-07 2017-07-25 Early Warning Services, Llc Enhanced 2CHK authentication security with query transactions
US10025920B2 (en) 2012-06-07 2018-07-17 Early Warning Services, Llc Enterprise triggered 2CHK association
US8892523B2 (en) 2012-06-08 2014-11-18 Commvault Systems, Inc. Auto summarization of content
US20130347004A1 (en) * 2012-06-25 2013-12-26 Sap Ag Correlating messages
US20140006528A1 (en) * 2012-06-27 2014-01-02 Synchronoss Technologies, Inc. Protocol agnostic dynamic messaging platform and a system and a method thereof
US9424238B2 (en) * 2012-07-27 2016-08-23 Zynx Health Incorporated Methods and systems for order set processing and validation
US9465648B2 (en) * 2012-07-31 2016-10-11 Hewlett Packard Enterprise Development Lp Distributed transaction processing through commit messages sent to a downstream neighbor
KR101355080B1 (ko) 2012-08-23 2014-01-27 모트렉스(주) 컨텐츠 프로바이더를 위한 디지털 원본 컨텐츠 배포 시스템 및 방법
US20140089200A1 (en) * 2012-09-25 2014-03-27 Janice L. Hazel Method and Apparatus for Synergistic Online Services
DE102012219498A1 (de) 2012-10-25 2014-04-30 Robert Bosch Gmbh Handwerkzeugmaschinenvorrichtung
US10013672B2 (en) 2012-11-02 2018-07-03 Oath Inc. Address extraction from a communication
KR101976006B1 (ko) * 2012-11-08 2019-05-09 에이치피프린팅코리아 유한회사 웹 서버의 자체 서명 인증서를 이용한 사용자 인증 방법, 이를 수행하기 위한 클라이언트 장치 및 웹 서버를 포함하는 전자 장치
US9426209B2 (en) * 2012-11-12 2016-08-23 Sap Se Upload/download of mobile applications using a MIME repository
AU2013348020B2 (en) 2012-11-20 2019-09-19 Blackhawk Network, Inc. System and method for using intelligent codes in conjunction with stored-value cards
US10192200B2 (en) 2012-12-04 2019-01-29 Oath Inc. Classifying a portion of user contact data into local contacts
US9947007B2 (en) 2013-01-27 2018-04-17 Barry Greenbaum Payment information technologies
WO2014190200A1 (fr) 2013-05-22 2014-11-27 Carefusion 303, Inc. Gestion de flux de médicaments
US10430554B2 (en) 2013-05-23 2019-10-01 Carefusion 303, Inc. Medication preparation queue
US11182728B2 (en) 2013-01-30 2021-11-23 Carefusion 303, Inc. Medication workflow management
CN113470641B (zh) 2013-02-07 2023-12-15 苹果公司 数字助理的语音触发器
US9979757B1 (en) * 2013-03-11 2018-05-22 Ca, Inc. Method and apparatus for providing a media content from a collaborative meeting to a remote user
CN114267429A (zh) 2013-03-13 2022-04-01 康尔福盛303公司 预测性用药安全
BR112015019758B1 (pt) 2013-03-13 2022-07-05 Carefusion 303, Inc Sistema e método para uso com dispositivo médico para reduzir erros de medicação e meio de armazenamento legível à maquina
US20140279416A1 (en) * 2013-03-14 2014-09-18 Sas Institute Inc. Signature based transaction group processing and real-time scoring
US9215075B1 (en) * 2013-03-15 2015-12-15 Poltorak Technologies Llc System and method for secure relayed communications from an implantable medical device
US10362006B2 (en) 2013-03-15 2019-07-23 Mastercard International Incorporated Systems and methods for cryptographic security as a service
US9396320B2 (en) 2013-03-22 2016-07-19 Nok Nok Labs, Inc. System and method for non-intrusive, privacy-preserving authentication
US10270748B2 (en) 2013-03-22 2019-04-23 Nok Nok Labs, Inc. Advanced authentication techniques and applications
US9887983B2 (en) 2013-10-29 2018-02-06 Nok Nok Labs, Inc. Apparatus and method for implementing composite authenticators
US20140310175A1 (en) * 2013-04-12 2014-10-16 Jack Bertram Coronel System and device for exchanging cloud-based digital privileges
US11410173B1 (en) * 2013-05-07 2022-08-09 Amazon Technologies, Inc. Tokenization web services
US9996670B2 (en) 2013-05-14 2018-06-12 Zynx Health Incorporated Clinical content analytics engine
US9961077B2 (en) 2013-05-30 2018-05-01 Nok Nok Labs, Inc. System and method for biometric authentication with device attestation
US9112790B2 (en) 2013-06-25 2015-08-18 Google Inc. Fabric network
US9342554B2 (en) * 2013-07-05 2016-05-17 Facebook, Inc. Techniques to generate mass push notifications
US9940182B1 (en) * 2013-09-13 2018-04-10 Stott Creations LLC Business rule engine validation systems and related methods
US9836337B1 (en) * 2013-09-13 2017-12-05 Stott Creations LLC Enterprise service bus business activity monitoring system and related methods
US9842012B1 (en) * 2013-09-13 2017-12-12 Stott Creations LLC Business rule engine message processing system and related methods
US9985829B2 (en) 2013-12-12 2018-05-29 Exablox Corporation Management and provisioning of cloud connected devices
CN104714923B (zh) * 2013-12-17 2018-04-20 华为技术有限公司 一种实现设备共享的方法和装置
US11126627B2 (en) 2014-01-14 2021-09-21 Change Healthcare Holdings, Llc System and method for dynamic transactional data streaming
US10121557B2 (en) 2014-01-21 2018-11-06 PokitDok, Inc. System and method for dynamic document matching and merging
EP3100405A4 (fr) 2014-01-29 2017-08-30 Smart Security Systems LLC Systèmes et procédés de protection de communications
US9667736B2 (en) * 2014-04-29 2017-05-30 International Business Machines Corporation Parallel I/O read processing for use in clustered file systems having cache storage
US9654469B1 (en) 2014-05-02 2017-05-16 Nok Nok Labs, Inc. Web-based user authentication techniques and applications
US9577999B1 (en) 2014-05-02 2017-02-21 Nok Nok Labs, Inc. Enhanced security for registration of authentication devices
US9413533B1 (en) 2014-05-02 2016-08-09 Nok Nok Labs, Inc. System and method for authorizing a new authenticator
WO2015171916A1 (fr) * 2014-05-09 2015-11-12 Plains Mobile Inc. Système et procédé de gestion de transactions de données entre des applications
US10579212B2 (en) 2014-05-30 2020-03-03 Apple Inc. Structured suggestions
US10170123B2 (en) 2014-05-30 2019-01-01 Apple Inc. Intelligent assistant for home automation
US9715875B2 (en) 2014-05-30 2017-07-25 Apple Inc. Reducing the need for manual start/end-pointing and trigger phrases
US9665625B2 (en) * 2014-06-25 2017-05-30 International Business Machines Corporation Maximizing the information content of system logs
US10148630B2 (en) 2014-07-31 2018-12-04 Nok Nok Labs, Inc. System and method for implementing a hosted authentication service
US9455979B2 (en) * 2014-07-31 2016-09-27 Nok Nok Labs, Inc. System and method for establishing trust using secure transmission protocols
US9875347B2 (en) 2014-07-31 2018-01-23 Nok Nok Labs, Inc. System and method for performing authentication using data analytics
US9749131B2 (en) 2014-07-31 2017-08-29 Nok Nok Labs, Inc. System and method for implementing a one-time-password using asymmetric cryptography
US9906367B2 (en) * 2014-08-05 2018-02-27 Sap Se End-to-end tamper protection in presence of cloud integration
US9736154B2 (en) 2014-09-16 2017-08-15 Nok Nok Labs, Inc. System and method for integrating an authentication service within a network architecture
US10007757B2 (en) 2014-09-17 2018-06-26 PokitDok, Inc. System and method for dynamic schedule aggregation
US10095500B2 (en) 2014-09-30 2018-10-09 Apple Inc. Revision locking
US20170339277A1 (en) * 2014-10-27 2017-11-23 Rideshark Corporation Methods and systems for notifications in communications networks
CN104378272B (zh) * 2014-10-28 2019-01-25 奇瑞汽车股份有限公司 消息传输方法及装置
GB2537087A (en) 2014-12-18 2016-10-12 Ipco 2012 Ltd A system, method and computer program product for receiving electronic messages
GB2533379A (en) 2014-12-18 2016-06-22 Ipco 2012 Ltd A system and server for receiving transaction requests
GB2533432A (en) 2014-12-18 2016-06-22 Ipco 2012 Ltd A device system, method and computer program product for processing electronic transaction requests
GB2533562A (en) 2014-12-18 2016-06-29 Ipco 2012 Ltd An interface, method and computer program product for controlling the transfer of electronic messages
US10360520B2 (en) * 2015-01-06 2019-07-23 International Business Machines Corporation Operational data rationalization
US10417379B2 (en) 2015-01-20 2019-09-17 Change Healthcare Holdings, Llc Health lending system and method using probabilistic graph models
US10079779B2 (en) * 2015-01-30 2018-09-18 Nicira, Inc. Implementing logical router uplinks
EP3067849A1 (fr) * 2015-03-11 2016-09-14 Facebook, Inc. Faciliter l'envoi, la réception et la mise à jour de paiements à l'aide de files d'attente de message et de paiement
US10007682B2 (en) * 2015-03-30 2018-06-26 International Business Machines Corporation Dynamically maintaining data structures driven by heterogeneous clients in a distributed data collection system
US9614845B2 (en) 2015-04-15 2017-04-04 Early Warning Services, Llc Anonymous authentication and remote wireless token access
US20160307195A1 (en) * 2015-04-20 2016-10-20 Mastercard International Incorporated Systems and methods for message conversion and validation
EP3297359B1 (fr) 2015-05-13 2020-12-09 LG Electronics Inc. Procédé d'envoi ou de réception de trame dans un système lan sans fil, et appareil associé
US20160342750A1 (en) 2015-05-18 2016-11-24 PokitDok, Inc. Dynamic topological system and method for efficient claims processing
US11025565B2 (en) 2015-06-07 2021-06-01 Apple Inc. Personalized prediction of responses for instant messaging
US10496626B2 (en) * 2015-06-11 2019-12-03 EB Storage Systems Ltd. Deduplication in a highly-distributed shared topology with direct-memory-access capable interconnect
US10049350B2 (en) 2015-06-25 2018-08-14 Bank Of America Corporation Element level presentation of elements of a payment instrument for exceptions processing
US10229395B2 (en) 2015-06-25 2019-03-12 Bank Of America Corporation Predictive determination and resolution of a value of indicia located in a negotiable instrument electronic image
US10373128B2 (en) 2015-06-25 2019-08-06 Bank Of America Corporation Dynamic resource management associated with payment instrument exceptions processing
US10115081B2 (en) 2015-06-25 2018-10-30 Bank Of America Corporation Monitoring module usage in a data processing system
US10366204B2 (en) 2015-08-03 2019-07-30 Change Healthcare Holdings, Llc System and method for decentralized autonomous healthcare economy platform
US11102313B2 (en) * 2015-08-10 2021-08-24 Oracle International Corporation Transactional autosave with local and remote lifecycles
US10582001B2 (en) 2015-08-11 2020-03-03 Oracle International Corporation Asynchronous pre-caching of synchronously loaded resources
US10419514B2 (en) 2015-08-14 2019-09-17 Oracle International Corporation Discovery of federated logins
US10452497B2 (en) 2015-08-14 2019-10-22 Oracle International Corporation Restoration of UI state in transactional systems
US9729330B2 (en) * 2015-08-21 2017-08-08 Samsung Electronics Co., Ltd. Secure pairing of eHealth devices and authentication of data using a gateway device having secured area
US10445425B2 (en) 2015-09-15 2019-10-15 Apple Inc. Emoji and canned responses
US10084782B2 (en) 2015-09-21 2018-09-25 Early Warning Services, Llc Authenticator centralization and protection
WO2017053968A1 (fr) 2015-09-25 2017-03-30 Fsa Technologies, Inc. Système et procédé de redirection de données dans une jonction de communications à bifurcation
US10206079B1 (en) 2015-09-30 2019-02-12 Groupon, Inc. System and method for notification transmission and confirmation management
JP2018538595A (ja) 2015-10-15 2018-12-27 ポキットドク インコーポレイテッド Ａｐｉトランザクションにおける動的メタデータ存続及び相関のためのシステム及び方法
US10582012B2 (en) 2015-10-16 2020-03-03 Oracle International Corporation Adaptive data transfer optimization
US10164854B2 (en) 2015-11-20 2018-12-25 International Business Machines Corporation Providing dynamic latency in an integration flow
CN106888152B (zh) * 2015-12-16 2019-11-12 华为技术有限公司 一种消息处理方法、装置和系统
US11516153B2 (en) 2016-01-25 2022-11-29 Expensify, Inc. Computer system providing a chat engine
US10552823B1 (en) 2016-03-25 2020-02-04 Early Warning Services, Llc System and method for authentication of a mobile device
US10437630B2 (en) 2016-04-10 2019-10-08 Bank Of America Corporation System for transforming large scale electronic processing using application block chain and multi-structured data stores
WO2017193093A1 (fr) 2016-05-05 2017-11-09 Neustar, Inc. Systèmes et procédés pour permettre des communications de confiance entre des entités
US11277439B2 (en) 2016-05-05 2022-03-15 Neustar, Inc. Systems and methods for mitigating and/or preventing distributed denial-of-service attacks
US11108562B2 (en) 2016-05-05 2021-08-31 Neustar, Inc. Systems and methods for verifying a route taken by a communication
US10958725B2 (en) 2016-05-05 2021-03-23 Neustar, Inc. Systems and methods for distributing partial data to subnetworks
US11025428B2 (en) 2016-05-05 2021-06-01 Neustar, Inc. Systems and methods for enabling trusted communications between controllers
US10313316B2 (en) * 2016-05-26 2019-06-04 Pepsico, Inc. Secure gateways for connected dispensing machines
US10733562B2 (en) * 2016-06-03 2020-08-04 Arkadiusz Binder Method, device, system of model-driven engineering of efficient industrial automation process and business process modeling with BPMN using native computation of XML schemas and objects
US10102340B2 (en) 2016-06-06 2018-10-16 PokitDok, Inc. System and method for dynamic healthcare insurance claims decision support
CN107516176B (zh) 2016-06-17 2021-03-19 菜鸟智能物流控股有限公司 物流信息处理方法及装置
US10580069B1 (en) * 2016-06-20 2020-03-03 Jpmorgan Chase Bank, N.A. Method and system for implementing a messaging format validator tool
US10108954B2 (en) 2016-06-24 2018-10-23 PokitDok, Inc. System and method for cryptographically verified data driven contracts
US10769635B2 (en) 2016-08-05 2020-09-08 Nok Nok Labs, Inc. Authentication techniques including speech and/or lip movement analysis
US10637853B2 (en) 2016-08-05 2020-04-28 Nok Nok Labs, Inc. Authentication techniques including speech and/or lip movement analysis
US20180091447A1 (en) * 2016-09-23 2018-03-29 Intel Corporation Technologies for dynamically transitioning network traffic host buffer queues
US10911569B1 (en) * 2016-10-06 2021-02-02 Arora Engineers, Inc. System and method for asset management and integration
US10158737B2 (en) 2016-10-07 2018-12-18 Bank Of America Corporation Real time event capture and analysis of transient data for an information network
US10069672B2 (en) 2016-10-07 2018-09-04 Bank Of America Corporation Real time event capture, analysis and reporting system
US10067994B2 (en) 2016-10-07 2018-09-04 Bank Of America Corporation Real time event capture and transformation of transient data for an information network
US10540516B2 (en) 2016-10-13 2020-01-21 Commvault Systems, Inc. Data protection within an unsecured storage environment
FR3058293B1 (fr) * 2016-10-28 2019-05-10 Sagemcom Energy & Telecom Sas Procede de selection d'une passerelle pour l'emission d'une trame
WO2018080857A1 (fr) * 2016-10-28 2018-05-03 Panoptex Technologies, Inc. Systèmes et procédés de création, de stockage et d'analyse de données sécurisées
US10153983B2 (en) 2016-11-04 2018-12-11 Bank Of America Corporation Optimum resource routing using contextual data analysis
CN106557974B (zh) * 2016-11-21 2020-11-20 中国农业银行股份有限公司 一种imix协议数据的处理方法及系统
CN106603636B (zh) * 2016-11-29 2020-05-26 中国银联股份有限公司 一种差错交易的标准化方法及装置
US10824655B2 (en) * 2016-12-29 2020-11-03 Sap Se Data models for geo-enriched data
US10091195B2 (en) 2016-12-31 2018-10-02 Nok Nok Labs, Inc. System and method for bootstrapping a user binding
US10237070B2 (en) 2016-12-31 2019-03-19 Nok Nok Labs, Inc. System and method for sharing keys across authenticators
US11256572B2 (en) 2017-01-23 2022-02-22 Honeywell International Inc. Systems and methods for processing data in security systems using parallelism, stateless queries, data slicing, or asynchronous pull mechanisms
US10255458B2 (en) 2017-01-23 2019-04-09 Akiri, Inc. Trust based access to records via encrypted protocol communications with authentication system
US20180211312A1 (en) * 2017-01-25 2018-07-26 Jpmorgan Chase Bank, N.A. Systems and Methods for Intraday Facility Monitoring
US11010342B2 (en) * 2017-04-03 2021-05-18 Splunk Inc. Network activity identification and characterization based on characteristic active directory (AD) event segments
WO2018194736A1 (fr) * 2017-04-18 2018-10-25 Tbcasoft, Inc. Anonymat et traçabilité de transactions de propriétés numériques sur un réseau de consensus de transactions distribuées
DK179496B1 (en) 2017-05-12 2019-01-15 Apple Inc. USER-SPECIFIC Acoustic Models
US10303715B2 (en) 2017-05-16 2019-05-28 Apple Inc. Intelligent automated assistant for media exploration
GB2563382B (en) * 2017-06-06 2021-03-03 Metaswitch Networks Ltd Telephony signalling element
US10805072B2 (en) 2017-06-12 2020-10-13 Change Healthcare Holdings, Llc System and method for autonomous dynamic person management
US20190018545A1 (en) * 2017-07-13 2019-01-17 International Business Machines Corporation System and method for rapid financial app prototyping
CA3070412A1 (fr) * 2017-07-17 2019-01-24 Brian R. Knopf Systemes et procedes de distribution de donnees partielles a des sous-reseaux
US11258682B2 (en) * 2017-08-03 2022-02-22 Chicago Mercantile Exchange Inc. Compressed message tracing and parsing
US10681185B1 (en) * 2017-08-15 2020-06-09 Worldpay, Llc Systems and methods for cloud based messaging between electronic database infrastructure
US11947489B2 (en) 2017-09-05 2024-04-02 Robin Systems, Inc. Creating snapshots of a storage volume in a distributed storage system
US10685010B2 (en) 2017-09-11 2020-06-16 Amazon Technologies, Inc. Shared volumes in distributed RAID over shared multi-queue storage devices
WO2019055584A1 (fr) * 2017-09-12 2019-03-21 David Schnitt Système de gestion de transactions électroniques unifiées
JP6888682B2 (ja) * 2017-09-14 2021-06-16 日本電気株式会社 情報通信装置、情報通信方法、情報通信システム及びプログラム
US11868995B2 (en) 2017-11-27 2024-01-09 Nok Nok Labs, Inc. Extending a secure key storage for transaction confirmation and cryptocurrency
US11748203B2 (en) 2018-01-11 2023-09-05 Robin Systems, Inc. Multi-role application orchestration in a distributed storage system
US11392363B2 (en) 2018-01-11 2022-07-19 Robin Systems, Inc. Implementing application entrypoints with containers of a bundled application
US11582168B2 (en) 2018-01-11 2023-02-14 Robin Systems, Inc. Fenced clone applications
US11831409B2 (en) 2018-01-12 2023-11-28 Nok Nok Labs, Inc. System and method for binding verifiable claims
WO2019152515A1 (fr) * 2018-01-31 2019-08-08 Walmart Apollo, Llc Système et procédé de sécurité et d'authentification de prescription
US20190251204A1 (en) 2018-02-14 2019-08-15 Commvault Systems, Inc. Targeted search of backup data using calendar event data
US10642886B2 (en) 2018-02-14 2020-05-05 Commvault Systems, Inc. Targeted search of backup data using facial recognition
US11729612B2 (en) * 2018-03-08 2023-08-15 Cypress Semiconductor Corporation Secure BLE just works pairing method against man-in-the-middle attack
US11194930B2 (en) 2018-04-27 2021-12-07 Datatrendz, Llc Unobtrusive systems and methods for collecting, processing and securing information transmitted over a network
US10789200B2 (en) 2018-06-01 2020-09-29 Dell Products L.P. Server message block remote direct memory access persistent memory dialect
DK180639B1 (en) 2018-06-01 2021-11-04 Apple Inc DISABILITY OF ATTENTION-ATTENTIVE VIRTUAL ASSISTANT
CN109146679B (zh) 2018-06-29 2023-11-10 创新先进技术有限公司 基于区块链的智能合约调用方法及装置、电子设备
US20200074417A1 (en) * 2018-09-03 2020-03-05 Venuetize LLC Configuration Platform
US10432405B1 (en) 2018-09-05 2019-10-01 Accelor Ltd. Systems and methods for accelerating transaction verification by performing cryptographic computing tasks in parallel
US10404473B1 (en) 2018-09-05 2019-09-03 Accelor Ltd. Systems and methods for processing transaction verification operations in decentralized applications
US10333694B1 (en) 2018-10-15 2019-06-25 Accelor Ltd. Systems and methods for secure smart contract execution via read-only distributed ledger
WO2020104929A1 (fr) * 2018-11-19 2020-05-28 Entersekt (Pty) Ltd Établissement d'une session partagée entre des entités
US11985112B2 (en) * 2018-12-18 2024-05-14 Bae Systems Information And Electronic Systems Integration Inc. Securing data in motion by zero knowledge protocol
US11238386B2 (en) 2018-12-20 2022-02-01 Sap Se Task derivation for workflows
FR3091395B1 (fr) * 2018-12-27 2021-06-04 Bancontact Payconiq Company Procédé et dispositif pour des paiements push sécurisés
US11960473B2 (en) 2019-01-15 2024-04-16 Fisher-Rosemount Systems, Inc. Distributed ledgers in process control systems
US11115218B2 (en) * 2019-01-15 2021-09-07 Fisher-Rosemount Systems, Inc. System for secure metering from systems of untrusted data derived from common sources
US11405180B2 (en) 2019-01-15 2022-08-02 Fisher-Rosemount Systems, Inc. Blockchain-based automation architecture cybersecurity
US11157337B2 (en) * 2019-01-28 2021-10-26 Salesforce.Com, Inc. Method and system for processing a stream of incoming messages sent from a specific input message source and validating each incoming message of that stream before sending them to a specific target system
US11256659B1 (en) * 2019-02-27 2022-02-22 Massachusetts Mutual Life Insurance Company Systems and methods for aggregating and displaying data from multiple data sources
US12041039B2 (en) 2019-02-28 2024-07-16 Nok Nok Labs, Inc. System and method for endorsing a new authenticator
US11086725B2 (en) 2019-03-25 2021-08-10 Robin Systems, Inc. Orchestration of heterogeneous multi-role applications
US11792024B2 (en) 2019-03-29 2023-10-17 Nok Nok Labs, Inc. System and method for efficient challenge-response authentication
US11256434B2 (en) 2019-04-17 2022-02-22 Robin Systems, Inc. Data de-duplication
CN111835395B (zh) * 2019-04-18 2022-04-01 大唐移动通信设备有限公司 卫星通信系统参数的确定方法、装置、终端及服务设备
US11218513B2 (en) * 2019-05-22 2022-01-04 Bae Systems Information And Electronic Systems Integration Inc. Information sharing with enhanced security
US11226847B2 (en) 2019-08-29 2022-01-18 Robin Systems, Inc. Implementing an application manifest in a node-specific manner using an intent-based orchestrator
US11288640B2 (en) * 2019-08-30 2022-03-29 Salesforce.Com, Inc. Cloud computing platform, method and system having a payments platform for integrating an asynchronous payment gateway service with the cloud computing platform
US11538000B2 (en) 2019-08-30 2022-12-27 Salesforce.Com, Inc. Cloud computing platform, method and system having a payments platform for integrating a synchronous payment gateway service with the cloud computing platform
US11080704B2 (en) 2019-08-30 2021-08-03 Salesforce.Com, Inc. Payments platform, method and system having external and internal operating modes for ingesting payment transaction data from payment gateway services at a cloud computing platform
US11074559B2 (en) 2019-08-30 2021-07-27 Salesforce.Com, Inc. Payments platform, method and system for a cloud computing platform
US11249851B2 (en) 2019-09-05 2022-02-15 Robin Systems, Inc. Creating snapshots of a storage volume in a distributed storage system
US11520650B2 (en) 2019-09-05 2022-12-06 Robin Systems, Inc. Performing root cause analysis in a multi-role application
US11113158B2 (en) 2019-10-04 2021-09-07 Robin Systems, Inc. Rolling back kubernetes applications
US11347684B2 (en) 2019-10-04 2022-05-31 Robin Systems, Inc. Rolling back KUBERNETES applications including custom resources
US12094588B1 (en) * 2019-11-01 2024-09-17 Managed Health Care Associates, Inc. Rules-based processing of structured data
AU2020382768A1 (en) * 2019-11-13 2022-06-30 TechAum Innovations Pty Ltd Communications channel systems and methods
US11403188B2 (en) 2019-12-04 2022-08-02 Robin Systems, Inc. Operation-level consistency points and rollback
US10715484B1 (en) 2019-12-11 2020-07-14 CallFire, Inc. Domain management and synchronization system
US20210204116A1 (en) 2019-12-31 2021-07-01 Payfone, Inc. Identity verification platform
US11089141B2 (en) * 2020-01-08 2021-08-10 Bank Of America Corporation Method and system for data prioritization communication
US11570099B2 (en) * 2020-02-04 2023-01-31 Bank Of America Corporation System and method for autopartitioning and processing electronic resources
CN111626746A (zh) * 2020-04-28 2020-09-04 华润守正招标有限公司 客服方法、系统、电子设备及存储介质
US11108638B1 (en) 2020-06-08 2021-08-31 Robin Systems, Inc. Health monitoring of automatically deployed and managed network pipelines
US11528186B2 (en) * 2020-06-16 2022-12-13 Robin Systems, Inc. Automated initialization of bare metal servers
US11740980B2 (en) 2020-09-22 2023-08-29 Robin Systems, Inc. Managing snapshot metadata following backup
CN112134761B (zh) * 2020-09-23 2022-05-06 国网四川省电力公司电力科学研究院 基于固件分析的电力物联网终端脆弱性检测方法及系统
US11757735B2 (en) * 2020-09-28 2023-09-12 Jpmorgan Chase Bank, N.A. Method and system for facilitating an audit of event-based business processes
CN112115126B (zh) * 2020-09-29 2024-08-20 北京人大金仓信息技术股份有限公司 集合数据类型的处理方法、装置和数据库管理系统
US11743188B2 (en) 2020-10-01 2023-08-29 Robin Systems, Inc. Check-in monitoring for workflows
US11456914B2 (en) 2020-10-07 2022-09-27 Robin Systems, Inc. Implementing affinity and anti-affinity with KUBERNETES
US11271895B1 (en) 2020-10-07 2022-03-08 Robin Systems, Inc. Implementing advanced networking capabilities using helm charts
US11750451B2 (en) 2020-11-04 2023-09-05 Robin Systems, Inc. Batch manager for complex workflows
US11556361B2 (en) 2020-12-09 2023-01-17 Robin Systems, Inc. Monitoring and managing of complex multi-role applications
US12058528B2 (en) 2020-12-31 2024-08-06 Prove Identity, Inc. Identity network representation of communications device subscriber in a digital domain
CN112839038A (zh) * 2021-01-04 2021-05-25 城云科技（中国）有限公司 服务器之间单向通信传输数据的方法及系统
US12080389B2 (en) * 2021-01-29 2024-09-03 Unitedhealth Group Incorporated Scalable dynamic data transmission
EP4071631A1 (fr) * 2021-04-06 2022-10-12 Amadeus S.A.S. Système et procédé d'échange et de gestion des données stockées dans des sources de données hétérogènes
TWI769773B (zh) * 2021-04-06 2022-07-01 鼎新電腦股份有限公司 業務流程管理系統及業務流程管理方法
US20220377052A1 (en) * 2021-05-21 2022-11-24 Mastercard International Incorporated Systems and methods for distributing event driven network services
CN113726755B (zh) * 2021-08-23 2023-06-02 天津津航计算技术研究所 一种slip协议数据的处理方法
US12126613B2 (en) 2021-09-17 2024-10-22 Nok Nok Labs, Inc. System and method for pre-registration of FIDO authenticators
US20230093871A1 (en) * 2021-09-30 2023-03-30 Expensify, Inc. Computing system implementing automated transaction execution based on messaging triggers
CN115037616B (zh) * 2022-04-22 2023-09-29 东北大学 一种基于tssdn网络的确定性流调度及其更新方法
US20230393712A1 (en) * 2022-06-03 2023-12-07 Apple Inc. Task execution based on context
EP4354296A1 (fr) * 2022-10-10 2024-04-17 IPCO 2012 Limited Gestionnaire de transactions
US20240283724A1 (en) * 2023-02-16 2024-08-22 Arista Networks, Inc. Sampled packet information accumulation
US12050595B1 (en) * 2023-08-03 2024-07-30 Truist Bank Real-time processing request location system

Citations (93)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4445176A (en) * 1979-12-28 1984-04-24 International Business Machines Corporation Block transfers of information in data processing networks
US5522077A (en) * 1994-05-19 1996-05-28 Ontos, Inc. Object oriented network system for allocating ranges of globally unique object identifiers from a server process to client processes which release unused identifiers
US5542078A (en) * 1994-09-29 1996-07-30 Ontos, Inc. Object oriented data store integration environment for integration of object oriented databases and non-object oriented data facilities
US5774668A (en) * 1995-06-07 1998-06-30 Microsoft Corporation System for on-line service in which gateway computer uses service map which includes loading condition of servers broadcasted by application servers for load balancing
US5937402A (en) * 1997-06-19 1999-08-10 Ontos, Inc. System for enabling access to a relational database from an object oriented program
US5943137A (en) * 1991-07-22 1999-08-24 Cardiff Software, Inc. Unified method of creating and processing fax forms
US6081591A (en) * 1997-04-16 2000-06-27 Skoog; Frederick H. Signaling network gateway device and method for use in a signaling network
US6101502A (en) * 1997-09-26 2000-08-08 Ontos, Inc. Object model mapping and runtime engine for employing relational database with object oriented software
US6212546B1 (en) * 1998-10-01 2001-04-03 Unisys Corporation Providing a modular gateway architecture which isolates attributes of the client and server systems into independent components
US6253249B1 (en) * 1998-08-31 2001-06-26 Nortel Networks Limited Method and devices for bridging data and telephone networks
US20010039570A1 (en) * 2000-02-16 2001-11-08 Rocky Stewart Pluggable hub system for enterprise wide electronic collaboration
US20020007423A1 (en) * 2000-05-31 2002-01-17 Hidekazu Arao Message processing system and method
US20020010618A1 (en) * 2000-01-31 2002-01-24 Rocco Pellegrinelli Data distribution
US20020049603A1 (en) * 2000-01-14 2002-04-25 Gaurav Mehra Method and apparatus for a business applications server
US20020059170A1 (en) * 2000-04-17 2002-05-16 Mark Vange Load balancing between multiple web servers
US20020059390A1 (en) * 2000-11-15 2002-05-16 Global Esoft, Inc. Integration messaging system
US20020091533A1 (en) * 2001-01-05 2002-07-11 International Business Machines Corporation, Technique for automated e-business services
US20020116453A1 (en) * 2000-09-15 2002-08-22 Todorov Ivan A. Industrial process control data access server supporting multiple client data exchange protocols
US20020120603A1 (en) * 2001-02-26 2002-08-29 William Thompson Automatic generation of SQL for frame completion
US20020138582A1 (en) * 2000-09-05 2002-09-26 Mala Chandra Methods and apparatus providing electronic messages that are linked and aggregated
US20020156874A1 (en) * 2001-04-20 2002-10-24 Suorsa Raymond E. Automated provisioning of computing networks according to customer accounts using a network database data model
US20020174010A1 (en) * 1999-09-08 2002-11-21 Rice James L. System and method of permissive data flow and application transfer
US20020186697A1 (en) * 2001-04-23 2002-12-12 Thakkar Bina Kunal Protocol encoder and decoder
US6516353B1 (en) * 1999-04-02 2003-02-04 Frederick R. Richards System and method for interactive EDI transactions
US20030033349A1 (en) * 2001-07-30 2003-02-13 International Business Machines Corporation Method and apparatus for data transfer across a network
US20030050931A1 (en) * 2001-08-28 2003-03-13 Gregory Harman System, method and computer program product for page rendering utilizing transcoding
US20030097597A1 (en) * 2001-11-16 2003-05-22 Lewis John Ervin System and method for password protecting a distribution list
US20030101283A1 (en) * 2001-11-16 2003-05-29 Lewis John Ervin System for translation and communication of messaging protocols into a common protocol
US20030149594A1 (en) * 2001-04-13 2003-08-07 Beazley Donald E. System and method for secure highway for real-time preadjudication and payment of medical claims
US20040001226A1 (en) * 2002-06-26 2004-01-01 Casio Computer Co., Ltd. Network printing system, server, printing machine, and printing method
US6678782B1 (en) * 2000-06-27 2004-01-13 International Business Machines Corporation Flow architecture for remote high-speed interface application
US20040028212A1 (en) * 2002-05-09 2004-02-12 Lok Shek Hung Unified integration management - contact center portal
US6704747B1 (en) * 1999-03-16 2004-03-09 Joseph Shi-Piu Fong Method and system for providing internet-based database interoperability using a frame model for universal database
US20040078580A1 (en) * 2002-10-18 2004-04-22 Trend Micro Incorporated Antivirus network system and method for handling electronic mails infected by computer viruses
US20040090989A1 (en) * 2002-11-08 2004-05-13 Nec Infrontia Corporation Packet compression system, packet restoration system, packet compression method, and packet restoration method
US20040131082A1 (en) * 2002-02-08 2004-07-08 Evans James C. Construction of middleware adapters
US6768994B1 (en) * 2001-02-23 2004-07-27 Trimble Navigation Limited Web based data mining and location data reporting and system
US6778703B1 (en) * 2000-04-19 2004-08-17 International Business Machines Corporation Form recognition using reference areas
US6829634B1 (en) * 2000-07-31 2004-12-07 The Boeing Company Broadcasting network
US20050005266A1 (en) * 1997-05-01 2005-01-06 Datig William E. Method of and apparatus for realizing synthetic knowledge processes in devices for useful applications
US20050027851A1 (en) * 2001-05-22 2005-02-03 Mckeown Jean Christophe Broadband communications
US20050027683A1 (en) * 2003-04-25 2005-02-03 Marcus Dill Defining a data analysis process
US20050043940A1 (en) * 2003-08-20 2005-02-24 Marvin Elder Preparing a data source for a natural language query
US20050044197A1 (en) * 2003-08-18 2005-02-24 Sun Microsystems.Inc. Structured methodology and design patterns for web services
US20050060420A1 (en) * 2003-09-11 2005-03-17 Kovacevic Branko D. System for decoding multimedia data and method thereof
US20050066058A1 (en) * 2003-08-28 2005-03-24 International Business Machines Corporation Gateway for service oriented state
US20050089046A1 (en) * 2003-08-15 2005-04-28 Hachem Moussa Enhanced encapsulation mechanism using GRE protocol
US6901428B1 (en) * 2000-10-11 2005-05-31 Ncr Corporation Accessing data from a database over a network
US20050159969A1 (en) * 2004-01-21 2005-07-21 Sheppard Robert F. Managing information technology (IT) infrastructure of an enterprise using a centralized logistics and management (CLAM) tool
US20050165761A1 (en) * 2004-01-22 2005-07-28 Chan Eric J. Method and apparatus for data processing and retrieval
US20050228865A1 (en) * 2004-04-07 2005-10-13 Hirsch Frederick J System, apparatus, and method for using reduced Web service messages
US20050240445A1 (en) * 1998-09-29 2005-10-27 Michael Sutherland Medical archive library and method
US20050246415A1 (en) * 2000-06-22 2005-11-03 Microsoft Corporation Distributed computing services platform
US20050251611A1 (en) * 2004-04-27 2005-11-10 Creta Kenneth C Transmitting peer-to-peer transactions through a coherent interface
US20050257045A1 (en) * 2004-04-12 2005-11-17 Bushman M B Secure messaging system
US20050262025A1 (en) * 2004-05-21 2005-11-24 Wajih Abu Reza M Systems and methods for brokering data in a transactional gateway
US20060010495A1 (en) * 2004-07-06 2006-01-12 Oded Cohen Method for protecting a computer from suspicious objects
US20060026655A1 (en) * 2004-07-30 2006-02-02 Perez Milton D System and method for managing, converting and displaying video content on a video-on-demand platform, including ads used for drill-down navigation and consumer-generated classified ads
US20060059107A1 (en) * 2000-03-30 2006-03-16 Kevin Elmore System and method for establishing eletronic business systems for supporting communications servuces commerce
US20060056413A1 (en) * 2004-09-14 2006-03-16 Oracle International Corporation Methods and systems for efficient queue propagation using a single protocol-based remote procedure call to stream a batch of messages
US20060075102A1 (en) * 2004-09-29 2006-04-06 Fujitsu Network Communications, Inc. Method and system for provisioning services on a communication network
US20060085331A1 (en) * 2004-10-19 2006-04-20 Apollo Enterprise Solutions, Llc System for resolving transactions
US20060101089A1 (en) * 2004-11-05 2006-05-11 Parr Francis N Management of persistence in a data processing system
US20060136555A1 (en) * 2004-05-21 2006-06-22 Bea Systems, Inc. Secure service oriented architecture
US7069240B2 (en) * 2002-10-21 2006-06-27 Raphael Spero System and method for capture, storage and processing of receipts and related data
US7080408B1 (en) * 2001-11-30 2006-07-18 Mcafee, Inc. Delayed-delivery quarantining of network communications having suspicious contents
US7082458B1 (en) * 2001-08-01 2006-07-25 Luigi Guadagno Dialog facilitation system for generating contextual order-preserving dialog postings and posting summaries from electronic messages
US20060168318A1 (en) * 2003-02-12 2006-07-27 Adam Twiss Methods and apparatus for traffic management in peer-to-peer networks
US20060182103A1 (en) * 2005-02-16 2006-08-17 Phantom Technologies, Llc. System and method for routing network messages
US20060206558A1 (en) * 2005-03-08 2006-09-14 Microsoft Corporation Reliable request-response messaging over a request-response transport
US20060235716A1 (en) * 2005-04-15 2006-10-19 General Electric Company Real-time interactive completely transparent collaboration within PACS for planning and consultation
US20060248009A1 (en) * 2005-05-02 2006-11-02 Hicks Sydney S System and method for processing electronic payments
US7139844B2 (en) * 2000-08-04 2006-11-21 Goldman Sachs & Co. Method and system for processing financial data objects carried on broadcast data streams and delivering information to subscribing clients
US7149777B1 (en) * 2000-01-20 2006-12-12 Avaya Technology Corp. Method for administering message attachments
US20060294333A1 (en) * 2005-06-27 2006-12-28 Spiro Michaylov Managing message queues
US20070005774A1 (en) * 2005-06-29 2007-01-04 Visa U.S.A., Inc. Adaptive gateway for switching transactions and data on unreliable networks using context-based rules
US7167924B1 (en) * 1996-06-10 2007-01-23 Diebold, Incorporated Financial transaction processing system and method
US7181766B2 (en) * 2000-04-12 2007-02-20 Corente, Inc. Methods and system for providing network services using at least one processor interfacing a base network
US20070061393A1 (en) * 2005-02-01 2007-03-15 Moore James F Management of health care data
US20070107032A1 (en) * 2005-09-07 2007-05-10 Verizon Business Network Services, Inc. Method and apparatus for synchronizing video frames
US20070107031A1 (en) * 1994-07-25 2007-05-10 Techsearch, L.L.C. Information distribution and processing system
US20070154098A1 (en) * 2006-01-04 2007-07-05 International Business Machines Corporation Automated processing of paper forms using remotely-stored templates
US20070165625A1 (en) * 2005-12-01 2007-07-19 Firestar Software, Inc. System and method for exchanging information among exchange applications
US20070288254A1 (en) * 2006-05-08 2007-12-13 Firestar Software, Inc. System and method for exchanging transaction information using images
US20080171924A9 (en) * 2001-04-11 2008-07-17 Ridder Trent D Noninvasive determination of alcohol in tissue
US20080222042A1 (en) * 2004-12-03 2008-09-11 Stephen James Moore Prescription Generation Validation And Tracking
US7437362B1 (en) * 2003-11-26 2008-10-14 Guardium, Inc. System and methods for nonintrusive database security
US7447775B1 (en) * 2003-11-07 2008-11-04 Cisco Technology, Inc. Methods and apparatus for supporting transmission of streaming data
US7509414B2 (en) * 2004-10-29 2009-03-24 International Business Machines Corporation System and method for collection, aggregation, and composition of metrics
US7516214B2 (en) * 2004-08-31 2009-04-07 Emc Corporation Rules engine for managing virtual logical units in a storage network
US7650432B2 (en) * 2004-05-20 2010-01-19 Bea Systems, Inc. Occasionally-connected application server
US7650431B2 (en) * 2006-08-28 2010-01-19 Microsoft Corporation Serving locally relevant advertisements
US7689711B2 (en) * 2001-03-26 2010-03-30 Salesforce.Com, Inc. System and method for routing messages between applications

Family Cites Families (206)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US2005089A (en) * 1932-12-31 1935-06-18 Packard Motor Car Co Valve spring
JPS56111967A (en) * 1980-02-07 1981-09-04 Omron Tateisi Electronics Co Transaction process system
US6850252B1 (en) * 1999-10-05 2005-02-01 Steven M. Hoffberg Intelligent electronic appliance system and method
US5497491A (en) * 1993-01-26 1996-03-05 International Business Machines Corporation System and method for importing and exporting data between an object oriented computing environment and an external computing environment
US20050259797A1 (en) 1993-08-25 2005-11-24 Symbol Technologies, Inc. Self-service checkout system utilizing portable communications terminal
US5596697A (en) * 1993-09-30 1997-01-21 Apple Computer, Inc. Method for routing items within a computer system
US7143290B1 (en) * 1995-02-13 2006-11-28 Intertrust Technologies Corporation Trusted and secure techniques, systems and methods for item delivery and execution
US6948070B1 (en) * 1995-02-13 2005-09-20 Intertrust Technologies Corporation Systems and methods for secure transaction management and electronic rights protection
US6512525B1 (en) * 1995-08-07 2003-01-28 Apple Computer, Inc. Multiple personas for mobile devices
US6039245A (en) * 1996-06-10 2000-03-21 Diebold, Incorporated Financial transaction processing system and method
US5781902A (en) * 1996-07-12 1998-07-14 Microsoft Corporation Method, computer program product, and system for extending the capabilities of an existing process to store and display foreign data
US5850444A (en) * 1996-09-09 1998-12-15 Telefonaktienbolaget L/M Ericsson (Publ) Method and apparatus for encrypting radio traffic in a telecommunications network
US7848948B2 (en) * 1996-10-25 2010-12-07 Ipf, Inc. Internet-based product brand marketing communication network configured to allow members of a product brand management team to communicate directly with consumers browsing HTML-encoded pages at an electronic commerce (EC) enabled web-site along the fabric of the world wide web (WWW), using programable multi-mode virtual kiosks (MMVKS) driven by server-side components and managed by product brand management team members
US6353834B1 (en) * 1996-11-14 2002-03-05 Mitsubishi Electric Research Laboratories, Inc. Log based data architecture for a transactional message queuing system
US20020156814A1 (en) * 1997-01-13 2002-10-24 Ho Bruce K. Method and apparatus for visual business computing
US6629513B1 (en) * 1997-03-27 2003-10-07 Robert G. Goetzman Infinite loop engine
US5926550A (en) 1997-03-31 1999-07-20 Intel Corporation Peripheral device preventing post-scan modification
US6377993B1 (en) * 1997-09-26 2002-04-23 Mci Worldcom, Inc. Integrated proxy interface for web based data management reports
US6233248B1 (en) * 1997-10-14 2001-05-15 Itt Manufacturing Enterprises, Inc. User data protocol for internet data communications
US8000897B2 (en) * 1997-10-22 2011-08-16 Intelligent Technologies International, Inc. Intersection collision avoidance techniques
CA2228687A1 (fr) * 1998-02-04 1999-08-04 Brett Howard Reseaux prives virtuels proteges
US6442563B1 (en) * 1998-04-30 2002-08-27 Enterworks Workflow management system, method, and medium that morphs work items
US7209949B2 (en) 1998-05-29 2007-04-24 Research In Motion Limited System and method for synchronizing information between a host system and a mobile data communication device
GB2339622A (en) * 1998-07-15 2000-02-02 Ibm Client/server computing with transactional interface between legacy and non-legacy systems
US6769124B1 (en) * 1998-07-22 2004-07-27 Cisco Technology, Inc. Persistent storage of information objects
WO2000017775A2 (fr) * 1998-09-22 2000-03-30 Science Applications International Corporation Environnements a collaboration dynamique definis par l'utilisateur
GB2342195A (en) * 1998-09-30 2000-04-05 Xerox Corp Secure token-based document server
WO2000020966A1 (fr) * 1998-10-02 2000-04-13 Fujitsu Limited Dispositif de cooperation objets
US6385643B1 (en) * 1998-11-05 2002-05-07 Bea Systems, Inc. Clustered enterprise Java™ having a message passing kernel in a distributed processing system
US6356951B1 (en) * 1999-03-01 2002-03-12 Sun Microsystems, Inc. System for parsing a packet for conformity with a predetermined protocol using mask and comparison values included in a parsing instruction
US6594268B1 (en) * 1999-03-11 2003-07-15 Lucent Technologies Inc. Adaptive routing system and method for QOS packet networks
US6701432B1 (en) * 1999-04-01 2004-03-02 Netscreen Technologies, Inc. Firewall including local bus
US6845503B1 (en) * 1999-08-13 2005-01-18 Sun Microsystems, Inc. System and method for enabling atomic class loading in an application server environment
US6879995B1 (en) * 1999-08-13 2005-04-12 Sun Microsystems, Inc. Application server message logging
KR100608640B1 (ko) * 1999-08-20 2006-08-04 엘지전자 주식회사 음성통신을 위한 게이트웨이 시스템 및 제어방법
US6442269B1 (en) 1999-08-23 2002-08-27 Aspect Communications Method and apparatus for integrating business data and transaction data in a transaction processing environment
US6490564B1 (en) * 1999-09-03 2002-12-03 Cisco Technology, Inc. Arrangement for defining and processing voice enabled web applications using extensible markup language documents
US8032409B1 (en) * 1999-11-22 2011-10-04 Accenture Global Services Limited Enhanced visibility during installation management in a network-based supply chain environment
US7413546B2 (en) * 1999-12-07 2008-08-19 Univeristy Of Utah Research Foundation Method and apparatus for monitoring dynamic cardiovascular function using n-dimensional representations of critical functions
US7000120B1 (en) * 1999-12-23 2006-02-14 Nokia Corporation Scheme for determining transport level information in the presence of IP security encryption
US6904449B1 (en) * 2000-01-14 2005-06-07 Accenture Llp System and method for an application provider framework
US20010047326A1 (en) 2000-03-14 2001-11-29 Broadbent David F. Interface system for a mortgage loan originator compliance engine
AU2001247514A1 (en) * 2000-03-20 2001-10-03 Motient Communications Inc. Integrated real time and polled electronic messaging system and method
US7260635B2 (en) 2000-03-21 2007-08-21 Centrisoft Corporation Software, systems and methods for managing a distributed network
JP2001274813A (ja) 2000-03-28 2001-10-05 Canon Inc 情報信号処理装置及び情報信号処理方法並びに記憶媒体
US7002989B2 (en) * 2000-04-10 2006-02-21 At&T Corp. Method and apparatus for S.I.P./H. 323 interworking
US6971096B1 (en) 2000-05-19 2005-11-29 Sun Microsystems, Inc. Transaction data structure for process communications among network-distributed applications
US8719562B2 (en) 2002-10-25 2014-05-06 William M. Randle Secure service network and user gateway
US20010051884A1 (en) * 2000-06-12 2001-12-13 Gidon Wallis Method and system for controlling warranty-related data and services
US20050149759A1 (en) 2000-06-15 2005-07-07 Movemoney, Inc. User/product authentication and piracy management system
US6789085B2 (en) * 2000-06-23 2004-09-07 Microsoft Corporation System and method for maintaining a user's state within a database table and for accommodating null values
US20020035559A1 (en) * 2000-06-26 2002-03-21 Crowe William L. System and method for a decision engine and architecture for providing high-performance data querying operations
US20030167229A1 (en) 2001-04-03 2003-09-04 Bottomline Technologies, Inc. Modular business transations platform
CA2316003C (fr) * 2000-08-14 2009-02-03 Ibm Canada Limited-Ibm Canada Limitee Acces a des applications heritees a partir d'internet
JP3536800B2 (ja) * 2000-09-07 2004-06-14 有限会社 ユリアインターナショナル インターネットを介したｔｖ番組情報検索システム
US7272662B2 (en) * 2000-11-30 2007-09-18 Nms Communications Corporation Systems and methods for routing messages to communications devices over a communications network
US20020129059A1 (en) * 2000-12-29 2002-09-12 Eck Jeffery R. XML auto map generator
US7107236B2 (en) * 2001-01-02 2006-09-12 ★Roaming Messenger, Inc. Self-contained business transaction capsules
US7562041B2 (en) * 2001-01-09 2009-07-14 International Business Machines Corporation Method and apparatus for facilitating business processes
WO2002057917A2 (fr) * 2001-01-22 2002-07-25 Sun Microsystems, Inc. Plate-forme de reseau entre homologues
EP1356680B1 (fr) 2001-02-02 2013-05-22 Opentv, Inc. Procede et systeme de reformatage d'un contenu destine a etre affiche sur une television interactive
US7305697B2 (en) * 2001-02-02 2007-12-04 Opentv, Inc. Service gateway for interactive television
WO2002080457A1 (fr) * 2001-03-29 2002-10-10 Sphere Software Corporation Services d'application d'entreprise a structure en couches et utilisant des garde-barrieres semantiques
JP3842577B2 (ja) * 2001-03-30 2006-11-08 株式会社東芝 構造化文書検索方法および構造化文書検索装置およびプログラム
US8606965B1 (en) * 2001-04-11 2013-12-10 Jda Software Group, Inc. System and method for facilitating communication of data among entities in an electronic trading network
US8234338B1 (en) 2001-04-20 2012-07-31 Microsoft Corporation System and method for reliable message delivery
US6671358B1 (en) * 2001-04-25 2003-12-30 Universal Identity Technologies, Inc. Method and system for rewarding use of a universal identifier, and/or conducting a financial transaction
US7136485B2 (en) * 2001-05-04 2006-11-14 Hewlett-Packard Development Company, L.P. Packetizing devices for scalable data streaming
US20020194221A1 (en) * 2001-05-07 2002-12-19 Strong Philip C. System, method and computer program product for collecting information utilizing an extensible markup language (XML) framework
US20020174244A1 (en) * 2001-05-18 2002-11-21 Telgen Corporation System and method for coordinating, distributing and processing of data
US20040168124A1 (en) 2001-06-07 2004-08-26 Michael Beisiegel System and method of mapping between software objects & structured language element-based documents
US7099891B2 (en) * 2001-06-15 2006-08-29 International Business Machines Corporation Method for allowing simple interoperation between backend database systems
EP1410228B1 (fr) * 2001-06-22 2016-03-23 Wonderware Corporation Telesurveillance/telediagnostic centralises de composants repartis d'une application de commande de processus de controle et d'informations de fabrication
US6886046B2 (en) * 2001-06-26 2005-04-26 Citrix Systems, Inc. Methods and apparatus for extendible information aggregation and presentation
US7337441B2 (en) 2001-07-17 2008-02-26 Bea Systems, Inc. System and method for prepreparing a transaction process involving a chain of servers in a circular flow
IES20010666A2 (en) * 2001-07-17 2002-11-13 Aircraft Man Technologies Ltd An electronic operations and maintenance log and system for an aircraft
US7222187B2 (en) 2001-07-31 2007-05-22 Sun Microsystems, Inc. Distributed trust mechanism for decentralized networks
US7065706B1 (en) * 2001-08-06 2006-06-20 Cisco Technology, Inc. Network router configured for executing network operations based on parsing XML tags in a received XML document
US7398247B2 (en) 2001-08-23 2008-07-08 Pitney Bowes Inc. Secure tax meter and certified service provider center for collecting sales and/or use taxes on sales that are made via the internet and/or catalog
US7506068B2 (en) 2001-08-30 2009-03-17 Siebel Systems, Inc. Method, apparatus and system for transforming, converting and processing messages between multiple systems
US20030046422A1 (en) * 2001-09-04 2003-03-06 Ravi Narayanan Object-oriented routing
US20030046450A1 (en) * 2001-09-04 2003-03-06 Ravi Narayanan Dynamic data-centered programming
US7426486B2 (en) * 2001-10-31 2008-09-16 Call-Tell Llc Multi-party reporting system and method
US20030088876A1 (en) 2001-11-08 2003-05-08 Liberate Technologies Video on demand gateway
GB2382962A (en) * 2001-12-07 2003-06-11 Altio Ltd Data routing without using an address
US20030130856A1 (en) * 2002-01-04 2003-07-10 Masanobu Matsuo System, method and computer program product for obtaining information in an information exchange framework
US7096498B2 (en) 2002-03-08 2006-08-22 Cipher Trust, Inc. Systems and methods for message threat management
US6944788B2 (en) * 2002-03-12 2005-09-13 Sun Microsystems, Inc. System and method for enabling failover for an application server cluster
US20030177016A1 (en) * 2002-03-13 2003-09-18 Delta Air Lines, Inc. Revenue recognition system and method for efficiently performing business-related processing and storing of event information related to a transaction
US6813637B2 (en) * 2002-03-15 2004-11-02 Sun Microsystems, Inc. System and method for automatically partitioning an application between a web server and an application server
US7082446B1 (en) * 2002-04-15 2006-07-25 Steel Eye Technology, Inc. Hybrid transaction/intent log for data replication
JP4199477B2 (ja) * 2002-04-17 2008-12-17 パナソニック株式会社 デジタル双方向通信制御装置およびその方法
US7774791B1 (en) 2002-04-24 2010-08-10 Informatica Corporation System, method and computer program product for data event processing and composite applications
US20040172301A1 (en) * 2002-04-30 2004-09-02 Mihai Dan M. Remote multi-purpose user interface for a healthcare system
US6947929B2 (en) * 2002-05-10 2005-09-20 International Business Machines Corporation Systems, methods and computer program products to determine useful relationships and dimensions of a database
US7447687B2 (en) * 2002-05-10 2008-11-04 International Business Machines Corporation Methods to browse database query information
US20030212900A1 (en) * 2002-05-13 2003-11-13 Hsin-Yuo Liu Packet classifying network services
US20030217000A1 (en) * 2002-05-17 2003-11-20 Brian Wichman System and method for collecting information via the internet using existing web sites
US7685314B2 (en) 2002-06-27 2010-03-23 Siebel Systems, Inc. System integration system and method
US7454486B2 (en) * 2002-07-09 2008-11-18 Microsoft Corporation Profiling and tracing distributed applications
US20040260921A1 (en) 2002-07-18 2004-12-23 Treadwell William S. Cryptographic method, system and engine for enciphered message transmission
US7822688B2 (en) 2002-08-08 2010-10-26 Fujitsu Limited Wireless wallet
US7219149B2 (en) * 2003-06-12 2007-05-15 Dw Holdings, Inc. Versatile terminal adapter and network for transaction processing
US7213227B2 (en) 2002-08-29 2007-05-01 Sap Aktiengesellschaft Rapid application integration using an integrated development environment
US6909992B2 (en) * 2002-11-05 2005-06-21 Sun Microsystems, Inc. Automatically identifying replacement times for limited lifetime components
GB0226778D0 (en) * 2002-11-18 2002-12-24 Hewlett Packard Co Using semantic web technology to enhance current business-to-business integration approaches
US20040103367A1 (en) 2002-11-26 2004-05-27 Larry Riss Facsimile/machine readable document processing and form generation apparatus and method
US7774831B2 (en) * 2002-12-24 2010-08-10 International Business Machines Corporation Methods and apparatus for processing markup language messages in a network
US7593889B2 (en) * 2002-12-30 2009-09-22 Fannie Mae System and method for processing data pertaining to financial assets
US20040138934A1 (en) 2003-01-09 2004-07-15 General Electric Company Controlling a business using a business information and decisioning control system
US7181733B2 (en) * 2003-01-16 2007-02-20 Sun Microsystems, Inc. Method and apparatus for detecting an overflow condition in a kernel stack during operating system development
US20040168115A1 (en) * 2003-02-21 2004-08-26 Bauernschmidt Bill G. Method and system for visualizing data from multiple, cached data sources with user defined treemap reports
US7707564B2 (en) * 2003-02-26 2010-04-27 Bea Systems, Inc. Systems and methods for creating network-based software services using source code annotations
US20040177040A1 (en) 2003-03-05 2004-09-09 Ming-Ching Shiu Method for securing card transaction by using mobile device
US20060240851A1 (en) 2003-03-21 2006-10-26 Vocel, Inc. Interactive messaging system
US8762415B2 (en) * 2003-03-25 2014-06-24 Siebel Systems, Inc. Modeling of order data
KR100524069B1 (ko) * 2003-04-04 2005-10-26 삼성전자주식회사 홈 에이전트 관리장치 및 관리방법
US8065725B2 (en) * 2003-05-30 2011-11-22 Yuliang Zheng Systems and methods for enhanced network security
JP5068000B2 (ja) * 2003-07-31 2012-11-07 富士通株式会社 Ｘｍｌドリブンアーキテクチャにおける情報処理方法及びプログラム
EP1665838B1 (fr) * 2003-08-13 2010-03-10 Roamware, Inc. Passerelle de signalisation àa imsi multiples et services multiples msisdn (mimm) dans un seul sim pour multiples partenaires itinerants
US8069435B1 (en) * 2003-08-18 2011-11-29 Oracle America, Inc. System and method for integration of web services
US7191248B2 (en) * 2003-08-29 2007-03-13 Microsoft Corporation Communication stack for network communication and routing
US20050086384A1 (en) * 2003-09-04 2005-04-21 Johannes Ernst System and method for replicating, integrating and synchronizing distributed information
JP4226980B2 (ja) 2003-09-19 2009-02-18 株式会社リコー ネットワーク端末装置
US20050067482A1 (en) 2003-09-26 2005-03-31 Wu Daniel Huong-Yu System and method for data capture and management
US20070011322A1 (en) * 2003-09-30 2007-01-11 Corrado Moiso Method and system for providing access to web services
US7506072B2 (en) * 2003-10-14 2009-03-17 Sun Microsystems, Inc. Web browser as web service server in interaction with business process engine
EP1524661A1 (fr) * 2003-10-14 2005-04-20 Deutsche Thomson-Brandt Gmbh Traitement de défauts pour supports d'enregistrement
US7424513B2 (en) 2003-10-23 2008-09-09 Microsoft Corporation Decoupling an attachment from an electronic message that included the attachment
WO2005043274A2 (fr) * 2003-11-04 2005-05-12 Ebiz.Mobility Ltd. Commerce electronique mobile universel
JP2005184792A (ja) * 2003-11-27 2005-07-07 Nec Corp 帯域制御装置、帯域制御方法及び帯域制御プログラム
US20050135387A1 (en) * 2003-12-19 2005-06-23 International Internet Telecom, Inc. Modular gateway
US9026701B2 (en) 2003-12-30 2015-05-05 Siebel Systems, Inc. Implementing device support in a web-based enterprise application
US7353279B2 (en) * 2004-01-08 2008-04-01 Hughes Electronics Corporation Proxy architecture for providing quality of service(QoS) reservations
US20050159060A1 (en) * 2004-01-16 2005-07-21 Ten-Po Shao Composite laminate and method for making the same
US7031256B2 (en) * 2004-01-20 2006-04-18 Transwitch Corporation Methods and apparatus for implementing LCAS ( link capacity adjustment scheme) sinking with rate based flow control
US7664110B1 (en) * 2004-02-07 2010-02-16 Habanero Holdings, Inc. Input/output controller for coupling the processor-memory complex to the fabric in fabric-backplane interprise servers
US7990994B1 (en) * 2004-02-13 2011-08-02 Habanero Holdings, Inc. Storage gateway provisioning and configuring
US7526563B2 (en) * 2004-02-27 2009-04-28 Nokia Corporation Interworking gateway and method
AU2005232073B8 (en) 2004-03-26 2011-06-16 La Jolla Networks, Inc. System and method for scalable multifunctional network communication
US7587324B2 (en) 2004-03-30 2009-09-08 Sap Ag Methods and systems for detecting user satisfaction
US20050223368A1 (en) 2004-03-30 2005-10-06 Tonic Solutions, Inc. Instrumented application for transaction tracing
US7392397B2 (en) * 2004-04-06 2008-06-24 International Business Machines Corporation Security and analysis system
WO2005102016A2 (fr) * 2004-04-26 2005-11-03 Jp Morgan Chase Bank Systeme et procede d'acheminement de messages
US7716409B2 (en) * 2004-04-27 2010-05-11 Intel Corporation Globally unique transaction identifiers
MXPA06013129A (es) 2004-05-12 2007-02-28 Cit Alcatel Contencion automatizada de un invasor en redes.
US7499588B2 (en) 2004-05-20 2009-03-03 Microsoft Corporation Low resolution OCR for camera acquired documents
US20050267947A1 (en) 2004-05-21 2005-12-01 Bea Systems, Inc. Service oriented architecture with message processing pipelines
US8024476B2 (en) * 2004-05-21 2011-09-20 Microsoft Corporation Efficient message routing when using server pools
WO2006034201A2 (fr) * 2004-09-17 2006-03-30 Hobnob, Inc. Reseau de mise en quarantaine
US20060085850A1 (en) * 2004-10-14 2006-04-20 Microsoft Corporation System and methods for providing network quarantine using IPsec
US7848978B2 (en) * 2004-10-19 2010-12-07 Apollo Enterprise Solutions, Inc. Enhanced transaction resolution techniques
WO2006052996A2 (fr) * 2004-11-08 2006-05-18 Integration Technologies, Inc Systeme, procede et appareil destines a une plateforme d'entreprise repartie extensible
US8458467B2 (en) * 2005-06-21 2013-06-04 Cisco Technology, Inc. Method and apparatus for adaptive application message payload content transformation in a network infrastructure element
US7509431B2 (en) * 2004-11-17 2009-03-24 Cisco Technology, Inc. Performing message and transformation adapter functions in a network element on behalf of an application
US8099078B2 (en) * 2004-11-29 2012-01-17 Research In Motion Limited System and method for service activation in mobile network billing
US20060123225A1 (en) * 2004-12-03 2006-06-08 Utstarcom, Inc. Method and system for decryption of encrypted packets
US7987272B2 (en) * 2004-12-06 2011-07-26 Cisco Technology, Inc. Performing message payload processing functions in a network element on behalf of an application
US7562382B2 (en) * 2004-12-16 2009-07-14 International Business Machines Corporation Specializing support for a federation relationship
US7551567B2 (en) * 2005-01-05 2009-06-23 Cisco Technology, Inc. Interpreting an application message at a network element using sampling and heuristics
US20060165053A1 (en) * 2005-01-21 2006-07-27 Nec Laboratories America, Inc. Content based data packet routing using labels
US20060167818A1 (en) * 2005-01-21 2006-07-27 David Wentker Methods and system for performing data exchanges related to financial transactions over a public network
US20060171380A1 (en) * 2005-02-03 2006-08-03 Chia Kevin M K Method and system for integrated communications with access control list, automatic notification and telephony services
US8744937B2 (en) * 2005-02-25 2014-06-03 Sap Ag Consistent set of interfaces derived from a business object model
US7509649B2 (en) * 2005-03-03 2009-03-24 Research In Motion Limited System and method for conversion of generic services' applications into component based applications for devices
GB2425018A (en) * 2005-04-04 2006-10-11 Agilent Technologies Inc Method of sharing measurement data
GB2425014A (en) * 2005-04-04 2006-10-11 Agilent Technologies Inc Monitoring progress of a signalling message and network monitoring
US7463637B2 (en) * 2005-04-14 2008-12-09 Alcatel Lucent Public and private network service management systems and methods
US7483438B2 (en) * 2005-04-14 2009-01-27 Alcatel Lucent Systems and methods for managing network services between private networks
US8223745B2 (en) * 2005-04-22 2012-07-17 Oracle America, Inc. Adding packet routing information without ECRC recalculation
US7565463B2 (en) * 2005-04-22 2009-07-21 Sun Microsystems, Inc. Scalable routing and addressing
US7672737B2 (en) * 2005-05-13 2010-03-02 Rockwell Automation Technologies, Inc. Hierarchically structured data model for utilization in industrial automation environments
US7706831B2 (en) * 2005-06-13 2010-04-27 Dyna Llc Simplified intuitive cell phone user interface
US7836027B2 (en) * 2005-06-22 2010-11-16 Statware, Inc. Method and apparatus for communicating list orders
EP1894388A1 (fr) * 2005-06-24 2008-03-05 Nokia Corporation Procede, systeme, dispositif et programme de transmission de donnees multimedia
US7953886B2 (en) * 2005-07-08 2011-05-31 Cisco Technology, Inc. Method and system of receiving and translating CLI command data within a routing system
US7778230B2 (en) * 2005-08-02 2010-08-17 WAAU Inc. Mobile router device
US20070107012A1 (en) 2005-09-07 2007-05-10 Verizon Business Network Services Inc. Method and apparatus for providing on-demand resource allocation
US8682795B2 (en) * 2005-09-16 2014-03-25 Oracle International Corporation Trusted information exchange based on trust agreements
US8745252B2 (en) * 2005-09-21 2014-06-03 Sap Ag Headers protocol for use within a web services message processing runtime framework
US7716279B2 (en) * 2005-09-21 2010-05-11 Sap Ag WS addressing protocol for web services message processing runtime framework
US7711836B2 (en) * 2005-09-21 2010-05-04 Sap Ag Runtime execution of a reliable messaging protocol
US8176004B2 (en) 2005-10-24 2012-05-08 Capsilon Corporation Systems and methods for intelligent paperless document management
US7986685B2 (en) * 2005-11-08 2011-07-26 Avaya Inc. Real-time XML messaging protocol
US7761591B2 (en) * 2005-12-16 2010-07-20 Jean A. Graham Central work-product management system for coordinated collaboration with remote users
US7913234B2 (en) * 2006-02-13 2011-03-22 Research In Motion Limited Execution of textually-defined instructions at a wireless communication device
US8046441B2 (en) 2006-02-13 2011-10-25 Infosys Limited Business to business integration software as a service
US7890853B2 (en) * 2006-02-13 2011-02-15 Nextair Corporation Apparatus and machine-readable medium for generating markup language representing a derived entity which extends or overrides attributes of a base entity
US8156148B2 (en) * 2006-02-24 2012-04-10 Microsoft Corporation Scalable algorithm for sharing EDI schemas
US8028025B2 (en) 2006-05-18 2011-09-27 International Business Machines Corporation Apparatus, system, and method for setting/retrieving header information dynamically into/from service data objects for protocol based technology adapters
US20070283150A1 (en) 2006-06-01 2007-12-06 Kabushiki Kaisha Toshiba System and method for secure messaging and web service communication
US7865584B2 (en) * 2006-06-20 2011-01-04 Alcatel Lucent Network service performance monitoring apparatus and methods
US8332253B1 (en) * 2006-07-27 2012-12-11 Adobe Systems Incorporated Just in time workflow construction
US8589239B2 (en) 2006-09-29 2013-11-19 Ebay Inc. Real-time bidding using instant messaging clients
US8060437B2 (en) * 2006-10-31 2011-11-15 International Funding Partners Llc Automatic termination of electronic transactions
WO2008085201A2 (fr) 2006-12-29 2008-07-17 Prodea Systems, Inc. Gestion de restauration et de traitement de secours de fichiers dans des emplacements de mémoire distants à l'aide d'un dispositif de passerelle multiservice côté locaux d'abonné
US8073863B2 (en) 2007-02-12 2011-12-06 Bsp Software Llc Batch management of metadata in a business intelligence architecture
US20080249938A1 (en) 2007-04-03 2008-10-09 Cpni Inc. System and method for merchant discovery and transfer of payment data
US7650782B2 (en) * 2007-11-30 2010-01-26 Chevron U.S.A. Inc. Device for use in rating engine deposits
US7996352B2 (en) 2008-05-30 2011-08-09 International Business Machines Corporation Distributed rule processing for ubiquitous computing environments
EP2329391A1 (fr) 2008-08-13 2011-06-08 Secure Exchange Solutions, Llc Système de carte sécurisé utilisant un échange sécurisé
US8417561B2 (en) 2008-09-24 2013-04-09 Bank Of America Corporation Market dynamics
US8549589B2 (en) * 2008-11-10 2013-10-01 Jeff STOLLMAN Methods and apparatus for transacting with multiple domains based on a credential
US8126449B2 (en) * 2008-11-13 2012-02-28 American Express Travel Related Services Company, Inc. Servicing attributes on a mobile device
US20100169134A1 (en) 2008-12-31 2010-07-01 Microsoft Corporation Fostering enterprise relationships
US20110161132A1 (en) * 2009-12-29 2011-06-30 Sukriti Goel Method and system for extracting process sequences

Patent Citations (96)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4445176A (en) * 1979-12-28 1984-04-24 International Business Machines Corporation Block transfers of information in data processing networks
US5943137A (en) * 1991-07-22 1999-08-24 Cardiff Software, Inc. Unified method of creating and processing fax forms
US5522077A (en) * 1994-05-19 1996-05-28 Ontos, Inc. Object oriented network system for allocating ranges of globally unique object identifiers from a server process to client processes which release unused identifiers
US20070107031A1 (en) * 1994-07-25 2007-05-10 Techsearch, L.L.C. Information distribution and processing system
US5542078A (en) * 1994-09-29 1996-07-30 Ontos, Inc. Object oriented data store integration environment for integration of object oriented databases and non-object oriented data facilities
US5774668A (en) * 1995-06-07 1998-06-30 Microsoft Corporation System for on-line service in which gateway computer uses service map which includes loading condition of servers broadcasted by application servers for load balancing
US7167924B1 (en) * 1996-06-10 2007-01-23 Diebold, Incorporated Financial transaction processing system and method
US6081591A (en) * 1997-04-16 2000-06-27 Skoog; Frederick H. Signaling network gateway device and method for use in a signaling network
US20050005266A1 (en) * 1997-05-01 2005-01-06 Datig William E. Method of and apparatus for realizing synthetic knowledge processes in devices for useful applications
US5937402A (en) * 1997-06-19 1999-08-10 Ontos, Inc. System for enabling access to a relational database from an object oriented program
US6101502A (en) * 1997-09-26 2000-08-08 Ontos, Inc. Object model mapping and runtime engine for employing relational database with object oriented software
US6253249B1 (en) * 1998-08-31 2001-06-26 Nortel Networks Limited Method and devices for bridging data and telephone networks
US20050240445A1 (en) * 1998-09-29 2005-10-27 Michael Sutherland Medical archive library and method
US6212546B1 (en) * 1998-10-01 2001-04-03 Unisys Corporation Providing a modular gateway architecture which isolates attributes of the client and server systems into independent components
US6704747B1 (en) * 1999-03-16 2004-03-09 Joseph Shi-Piu Fong Method and system for providing internet-based database interoperability using a frame model for universal database
US6516353B1 (en) * 1999-04-02 2003-02-04 Frederick R. Richards System and method for interactive EDI transactions
US20020174010A1 (en) * 1999-09-08 2002-11-21 Rice James L. System and method of permissive data flow and application transfer
US20020049603A1 (en) * 2000-01-14 2002-04-25 Gaurav Mehra Method and apparatus for a business applications server
US7149777B1 (en) * 2000-01-20 2006-12-12 Avaya Technology Corp. Method for administering message attachments
US20020010618A1 (en) * 2000-01-31 2002-01-24 Rocco Pellegrinelli Data distribution
US20010039570A1 (en) * 2000-02-16 2001-11-08 Rocky Stewart Pluggable hub system for enterprise wide electronic collaboration
US20060059107A1 (en) * 2000-03-30 2006-03-16 Kevin Elmore System and method for establishing eletronic business systems for supporting communications servuces commerce
US7181766B2 (en) * 2000-04-12 2007-02-20 Corente, Inc. Methods and system for providing network services using at least one processor interfacing a base network
US20020059170A1 (en) * 2000-04-17 2002-05-16 Mark Vange Load balancing between multiple web servers
US6778703B1 (en) * 2000-04-19 2004-08-17 International Business Machines Corporation Form recognition using reference areas
US20020007423A1 (en) * 2000-05-31 2002-01-17 Hidekazu Arao Message processing system and method
US20050246415A1 (en) * 2000-06-22 2005-11-03 Microsoft Corporation Distributed computing services platform
US6678782B1 (en) * 2000-06-27 2004-01-13 International Business Machines Corporation Flow architecture for remote high-speed interface application
US6829634B1 (en) * 2000-07-31 2004-12-07 The Boeing Company Broadcasting network
US7139844B2 (en) * 2000-08-04 2006-11-21 Goldman Sachs & Co. Method and system for processing financial data objects carried on broadcast data streams and delivering information to subscribing clients
US20020138582A1 (en) * 2000-09-05 2002-09-26 Mala Chandra Methods and apparatus providing electronic messages that are linked and aggregated
US20020116453A1 (en) * 2000-09-15 2002-08-22 Todorov Ivan A. Industrial process control data access server supporting multiple client data exchange protocols
US6901428B1 (en) * 2000-10-11 2005-05-31 Ncr Corporation Accessing data from a database over a network
US20020059390A1 (en) * 2000-11-15 2002-05-16 Global Esoft, Inc. Integration messaging system
US20020091533A1 (en) * 2001-01-05 2002-07-11 International Business Machines Corporation, Technique for automated e-business services
US6768994B1 (en) * 2001-02-23 2004-07-27 Trimble Navigation Limited Web based data mining and location data reporting and system
US20020120603A1 (en) * 2001-02-26 2002-08-29 William Thompson Automatic generation of SQL for frame completion
US7689711B2 (en) * 2001-03-26 2010-03-30 Salesforce.Com, Inc. System and method for routing messages between applications
US20080171924A9 (en) * 2001-04-11 2008-07-17 Ridder Trent D Noninvasive determination of alcohol in tissue
US20030149594A1 (en) * 2001-04-13 2003-08-07 Beazley Donald E. System and method for secure highway for real-time preadjudication and payment of medical claims
US20020156874A1 (en) * 2001-04-20 2002-10-24 Suorsa Raymond E. Automated provisioning of computing networks according to customer accounts using a network database data model
US20020186697A1 (en) * 2001-04-23 2002-12-12 Thakkar Bina Kunal Protocol encoder and decoder
US20050027851A1 (en) * 2001-05-22 2005-02-03 Mckeown Jean Christophe Broadband communications
US20030033349A1 (en) * 2001-07-30 2003-02-13 International Business Machines Corporation Method and apparatus for data transfer across a network
US7082458B1 (en) * 2001-08-01 2006-07-25 Luigi Guadagno Dialog facilitation system for generating contextual order-preserving dialog postings and posting summaries from electronic messages
US20030050931A1 (en) * 2001-08-28 2003-03-13 Gregory Harman System, method and computer program product for page rendering utilizing transcoding
US20030097597A1 (en) * 2001-11-16 2003-05-22 Lewis John Ervin System and method for password protecting a distribution list
US20030101283A1 (en) * 2001-11-16 2003-05-29 Lewis John Ervin System for translation and communication of messaging protocols into a common protocol
US7080408B1 (en) * 2001-11-30 2006-07-18 Mcafee, Inc. Delayed-delivery quarantining of network communications having suspicious contents
US20040131082A1 (en) * 2002-02-08 2004-07-08 Evans James C. Construction of middleware adapters
US20040028212A1 (en) * 2002-05-09 2004-02-12 Lok Shek Hung Unified integration management - contact center portal
US20040001226A1 (en) * 2002-06-26 2004-01-01 Casio Computer Co., Ltd. Network printing system, server, printing machine, and printing method
US20040078580A1 (en) * 2002-10-18 2004-04-22 Trend Micro Incorporated Antivirus network system and method for handling electronic mails infected by computer viruses
US7069240B2 (en) * 2002-10-21 2006-06-27 Raphael Spero System and method for capture, storage and processing of receipts and related data
US20040090989A1 (en) * 2002-11-08 2004-05-13 Nec Infrontia Corporation Packet compression system, packet restoration system, packet compression method, and packet restoration method
US20060168318A1 (en) * 2003-02-12 2006-07-27 Adam Twiss Methods and apparatus for traffic management in peer-to-peer networks
US20050027683A1 (en) * 2003-04-25 2005-02-03 Marcus Dill Defining a data analysis process
US20050089046A1 (en) * 2003-08-15 2005-04-28 Hachem Moussa Enhanced encapsulation mechanism using GRE protocol
US20050044197A1 (en) * 2003-08-18 2005-02-24 Sun Microsystems.Inc. Structured methodology and design patterns for web services
US20050043940A1 (en) * 2003-08-20 2005-02-24 Marvin Elder Preparing a data source for a natural language query
US20050066058A1 (en) * 2003-08-28 2005-03-24 International Business Machines Corporation Gateway for service oriented state
US20050060420A1 (en) * 2003-09-11 2005-03-17 Kovacevic Branko D. System for decoding multimedia data and method thereof
US7447775B1 (en) * 2003-11-07 2008-11-04 Cisco Technology, Inc. Methods and apparatus for supporting transmission of streaming data
US7437362B1 (en) * 2003-11-26 2008-10-14 Guardium, Inc. System and methods for nonintrusive database security
US20050159969A1 (en) * 2004-01-21 2005-07-21 Sheppard Robert F. Managing information technology (IT) infrastructure of an enterprise using a centralized logistics and management (CLAM) tool
US20050165761A1 (en) * 2004-01-22 2005-07-28 Chan Eric J. Method and apparatus for data processing and retrieval
US20050228865A1 (en) * 2004-04-07 2005-10-13 Hirsch Frederick J System, apparatus, and method for using reduced Web service messages
US20050257045A1 (en) * 2004-04-12 2005-11-17 Bushman M B Secure messaging system
US20050251611A1 (en) * 2004-04-27 2005-11-10 Creta Kenneth C Transmitting peer-to-peer transactions through a coherent interface
US7650432B2 (en) * 2004-05-20 2010-01-19 Bea Systems, Inc. Occasionally-connected application server
US20060136555A1 (en) * 2004-05-21 2006-06-22 Bea Systems, Inc. Secure service oriented architecture
US20050262025A1 (en) * 2004-05-21 2005-11-24 Wajih Abu Reza M Systems and methods for brokering data in a transactional gateway
US20060010495A1 (en) * 2004-07-06 2006-01-12 Oded Cohen Method for protecting a computer from suspicious objects
US20060026655A1 (en) * 2004-07-30 2006-02-02 Perez Milton D System and method for managing, converting and displaying video content on a video-on-demand platform, including ads used for drill-down navigation and consumer-generated classified ads
US7516214B2 (en) * 2004-08-31 2009-04-07 Emc Corporation Rules engine for managing virtual logical units in a storage network
US20060056413A1 (en) * 2004-09-14 2006-03-16 Oracle International Corporation Methods and systems for efficient queue propagation using a single protocol-based remote procedure call to stream a batch of messages
US20060075102A1 (en) * 2004-09-29 2006-04-06 Fujitsu Network Communications, Inc. Method and system for provisioning services on a communication network
US20060085331A1 (en) * 2004-10-19 2006-04-20 Apollo Enterprise Solutions, Llc System for resolving transactions
US7509414B2 (en) * 2004-10-29 2009-03-24 International Business Machines Corporation System and method for collection, aggregation, and composition of metrics
US20060101089A1 (en) * 2004-11-05 2006-05-11 Parr Francis N Management of persistence in a data processing system
US20080222042A1 (en) * 2004-12-03 2008-09-11 Stephen James Moore Prescription Generation Validation And Tracking
US20070061393A1 (en) * 2005-02-01 2007-03-15 Moore James F Management of health care data
US20060182103A1 (en) * 2005-02-16 2006-08-17 Phantom Technologies, Llc. System and method for routing network messages
US20060206558A1 (en) * 2005-03-08 2006-09-14 Microsoft Corporation Reliable request-response messaging over a request-response transport
US20060235716A1 (en) * 2005-04-15 2006-10-19 General Electric Company Real-time interactive completely transparent collaboration within PACS for planning and consultation
US20060248009A1 (en) * 2005-05-02 2006-11-02 Hicks Sydney S System and method for processing electronic payments
US20060294333A1 (en) * 2005-06-27 2006-12-28 Spiro Michaylov Managing message queues
US20070005774A1 (en) * 2005-06-29 2007-01-04 Visa U.S.A., Inc. Adaptive gateway for switching transactions and data on unreliable networks using context-based rules
US20070107032A1 (en) * 2005-09-07 2007-05-10 Verizon Business Network Services, Inc. Method and apparatus for synchronizing video frames
US20070198437A1 (en) * 2005-12-01 2007-08-23 Firestar Software, Inc. System and method for exchanging information among exchange applications
US20070171923A1 (en) * 2005-12-01 2007-07-26 Firestar Software, Inc. System and method for exchanging information among exchange applications
US20070168301A1 (en) * 2005-12-01 2007-07-19 Firestar Software, Inc. System and method for exchanging information among exchange applications
US20070165625A1 (en) * 2005-12-01 2007-07-19 Firestar Software, Inc. System and method for exchanging information among exchange applications
US20070154098A1 (en) * 2006-01-04 2007-07-05 International Business Machines Corporation Automated processing of paper forms using remotely-stored templates
US20070288254A1 (en) * 2006-05-08 2007-12-13 Firestar Software, Inc. System and method for exchanging transaction information using images
US7650431B2 (en) * 2006-08-28 2010-01-19 Microsoft Corporation Serving locally relevant advertisements

Cited By (52)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7801782B2 (en) 1998-07-31 2010-09-21 Jpmorgan Chase Bank, Na Object oriented system for managing complex financial instruments
US20010025264A1 (en) * 1998-07-31 2001-09-27 Michael Deaddio Object oriented system for managing complex financial instruments
US20100094747A1 (en) * 1998-07-31 2010-04-15 Deaddio Michael L Object Oriented System For Managing Complex Financial Instruments
US8099347B2 (en) 1998-07-31 2012-01-17 JPMorgan Chase Bank, N.A, Object oriented system for managing complex financial instruments
US8732049B2 (en) 1998-07-31 2014-05-20 Jpmorgan Chase Bank, Na Object oriented system for managing complex financial instruments
US9824341B2 (en) 1998-07-31 2017-11-21 Jpmorgan Chase Bank, N.A. Object oriented system for managing complex financial instruments
US20070168301A1 (en) * 2005-12-01 2007-07-19 Firestar Software, Inc. System and method for exchanging information among exchange applications
US8838668B2 (en) 2005-12-01 2014-09-16 Firestar Software, Inc. System and method for exchanging information among exchange applications
US20070171924A1 (en) * 2005-12-01 2007-07-26 Firestar Software, Inc. System and method for exchanging information among exchange applications
US9742880B2 (en) 2005-12-01 2017-08-22 Firestar Software, Inc. System and method for exchanging information among exchange applications
US8620989B2 (en) 2005-12-01 2013-12-31 Firestar Software, Inc. System and method for exchanging information among exchange applications
US7979569B2 (en) 2005-12-01 2011-07-12 Firestar Software, Inc. System and method for exchanging information among exchange applications
US9860348B2 (en) 2005-12-01 2018-01-02 Firestar Software, Inc. System and method for exchanging information among exchange applications
US20070171923A1 (en) * 2005-12-01 2007-07-26 Firestar Software, Inc. System and method for exchanging information among exchange applications
US20070214419A1 (en) * 2006-03-01 2007-09-13 Ashish Jain Integrated service creation and execution platforms for the converged networks
US20070288254A1 (en) * 2006-05-08 2007-12-13 Firestar Software, Inc. System and method for exchanging transaction information using images
US20080172654A1 (en) * 2007-01-15 2008-07-17 Andreas Frohlich Monitoring a Software System
US8230398B2 (en) * 2007-01-15 2012-07-24 Software Ag Monitoring a software system based on a service oriented architecture
US8850401B2 (en) 2007-01-15 2014-09-30 Software Ag Monitoring a software system using an interpretation rule of an ontology
US10885051B1 (en) * 2008-03-07 2021-01-05 Infor (Us), Inc. Automatic data warehouse generation using automatically generated schema
US8650270B2 (en) * 2008-07-10 2014-02-11 Juniper Networks, Inc. Distributed computing with multiple coordinated component collections
US20100011096A1 (en) * 2008-07-10 2010-01-14 Blackwave Inc. Distributed Computing With Multiple Coordinated Component Collections
US20100228766A1 (en) * 2009-02-23 2010-09-09 International Business Machines Corporations Queue message retrieval by selection criteria
US20100228748A1 (en) * 2009-02-23 2010-09-09 International Business Machines Corporation Data subset retrieval from a queued message
US20120065998A1 (en) * 2009-03-11 2012-03-15 Nextgen Healthcare Information Systems, Inc. Health Quality Measures Systems and Methods
US20100235192A1 (en) * 2009-03-11 2010-09-16 Nextgen Healthcare Information Systems, Inc. Health Quality Measures Systems and Methods
US8924229B2 (en) * 2009-03-11 2014-12-30 Qsi Management, Llc Health quality measures systems and methods
US8682691B2 (en) * 2009-03-11 2014-03-25 Qsi Management, Llc Health quality measures systems and methods
US20100332240A1 (en) * 2009-06-24 2010-12-30 Microsoft Corporation Decentralized account digest using signed electronic receipts
US8122292B2 (en) * 2009-08-19 2012-02-21 Oracle International Corporation Debugging of business flows deployed in production servers
US20110047415A1 (en) * 2009-08-19 2011-02-24 Oracle International Corporation Debugging of business flows deployed in production servers
US20110208746A1 (en) * 2010-02-22 2011-08-25 Brignoli Winthrop A Systems and methods for message-based distributed computing
US8250090B2 (en) * 2010-02-22 2012-08-21 Brignoli Winthrop A Method for performing message-based distributed computing, involves executing expression of matched message response on members identified by set instance definition using dimension values derived from message
US8429622B2 (en) 2010-04-15 2013-04-23 Oracle International Corporation Business process debugger with parallel-step debug operation
US10419374B1 (en) 2010-07-09 2019-09-17 Gummarus, Llc Methods, systems, and computer program products for processing a request for a resource in a communication
US10158590B1 (en) 2010-07-09 2018-12-18 Gummarus LLC Methods, systems, and computer program products for processing a request for a resource in a communication
US10171392B1 (en) 2010-07-09 2019-01-01 Gummarus LLC Methods, systems, and computer program products for processing a request for a resource in a communication
US10212112B1 (en) 2010-07-09 2019-02-19 Gummarus LLC Methods, systems, and computer program products for processing a request for a resource in a communication
US20140032774A1 (en) * 2012-07-30 2014-01-30 Microsoft Corporation Client-emulating Gateways for Communication Network Migration
US10613737B1 (en) 2012-09-22 2020-04-07 Motion Offense, Llc Methods, systems, and computer program products for sharing a data object in a data store via a communication
US10013158B1 (en) 2012-09-22 2018-07-03 Sitting Man, Llc Methods, systems, and computer program products for sharing a data object in a data store via a communication
US12028299B1 (en) 2012-09-22 2024-07-02 Motion Offense, Llc Methods, systems, and computer program products for processing a data object identification request in a communication
US10021052B1 (en) 2012-09-22 2018-07-10 Sitting Man, Llc Methods, systems, and computer program products for processing a data object identification request in a communication
US11611520B1 (en) 2012-09-22 2023-03-21 Motion Offense, Llc Methods, systems, and computer program products for processing a data object identification request in a communication
US11044215B1 (en) 2012-09-22 2021-06-22 Motion Offense, Llc Methods, systems, and computer program products for processing a data object identification request in a communication
US20140089421A1 (en) * 2012-09-25 2014-03-27 Deep River Ventures, Llc Methods, Systems, and Program Products for Sharing a Data Object in a Data Store Via a Communication
US10019135B1 (en) 2012-10-18 2018-07-10 Sitting Man, Llc Methods, and computer program products for constraining a communication exchange
US10841258B1 (en) 2012-10-18 2020-11-17 Gummarus, Llc Methods and computer program products for browsing using a communicant identifier
US10033672B1 (en) 2012-10-18 2018-07-24 Sitting Man, Llc Methods and computer program products for browsing using a communicant identifier
US10015122B1 (en) 2012-10-18 2018-07-03 Sitting Man, Llc Methods and computer program products for processing a search
US10496942B2 (en) 2013-02-28 2019-12-03 P800X, Llc Method and system for automated project management of excavation requests
US9342806B2 (en) 2013-02-28 2016-05-17 P800X, Llc Method and system for automated project management

Also Published As

Publication number Publication date
WO2007064878A2 (fr) 2007-06-07
WO2007064877A2 (fr) 2007-06-07
US20070198437A1 (en) 2007-08-23
EP1955171A2 (fr) 2008-08-13
EP1955171A4 (fr) 2009-03-11
EP1955490A4 (fr) 2009-12-02
EP1955281A2 (fr) 2008-08-13
US20130044749A1 (en) 2013-02-21
US9860348B2 (en) 2018-01-02
US20140341217A1 (en) 2014-11-20
WO2007064876A3 (fr) 2007-11-01
EP1960896A4 (fr) 2009-03-11
US20070171923A1 (en) 2007-07-26
WO2008048304A2 (fr) 2008-04-24
EP1955471A2 (fr) 2008-08-13
CA2631756A1 (fr) 2007-06-07
US20120023193A1 (en) 2012-01-26
WO2007064876A2 (fr) 2007-06-07
CA2631753A1 (fr) 2007-04-28
US20070171924A1 (en) 2007-07-26
US20070168301A1 (en) 2007-07-19
US7979569B2 (en) 2011-07-12
US9742880B2 (en) 2017-08-22
US8838668B2 (en) 2014-09-16
EP1955221A2 (fr) 2008-08-13
US8620989B2 (en) 2013-12-31
EP1960896A2 (fr) 2008-08-27
US20070165625A1 (en) 2007-07-19
EP1955471A4 (fr) 2009-03-11
CA2631763A1 (fr) 2007-06-07
US8838737B2 (en) 2014-09-16
WO2008048304A3 (fr) 2008-09-18
EP1955490A2 (fr) 2008-08-13
WO2007064878A3 (fr) 2007-11-22
US20130041888A1 (en) 2013-02-14
CA2631770A1 (fr) 2007-06-07
EP1955281A4 (fr) 2009-03-11
WO2007064879A3 (fr) 2009-04-30
WO2007064880A3 (fr) 2007-10-04
WO2007064880A2 (fr) 2007-06-07
EP1955221A4 (fr) 2009-03-11
WO2007064879A2 (fr) 2007-06-07
WO2007064877A3 (fr) 2007-11-22
CA2631671A1 (fr) 2007-06-07
CA2631761A1 (fr) 2007-06-07

Similar Documents

Publication Publication Date Title
US9860348B2 (en) System and method for exchanging information among exchange applications
US20070288254A1 (en) System and method for exchanging transaction information using images
US9467405B2 (en) Routing messages between applications
US7478402B2 (en) Configurable message pipelines
US8639843B2 (en) System and method for routing messages between applications
US7249195B2 (en) Apparatus and methods for correlating messages sent between services

Legal Events

Date Code Title Description
AS Assignment

Owner name: FIRESTAR SOFTWARE, INC., MASSACHUSETTS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:EISNER, MARK;OANCEA, GABRIEL;REEL/FRAME:019048/0050

Effective date: 20070314

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION