Verified message broker

• US 20030065725A1
• Filed: 10/01/2001
• Published: 04/03/2003
• Est. Priority Date: 10/01/2001
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Hahn, Stefan, Kallvikbacka, Erkki, Denereaz, Pierre, Doczi, Nicholas L., Delmer, Jean-Francois
• Application Number:
  US09/969,342
• Publication Number:
  US 20030065725A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 63/0263 Rule management

Abstract

A gate-keeping message broker spanning a firewall to provide interconnected message brokering services spanning the firewall. The gate-keeping message broker provides for the creation of an international business transaction information system (“IBTIS”) for a user having service needs regarding the relocation of purchased goods across international borders. The IBTIS is configured to work with a plurality of internal service engines and reference servers that are present on both sides of the firewall. The gate-keeping message broker also provides form and syntax validation for messages that it brokers. It further provides content verification and completion services on the content of the messages, the verification being based on business-logic specific to the type of message being brokered.

Claims

1. A system for use with a plurality of service engines configured for sending and receiving messages, each service engine sending and receiving messages containing data representing an event of a type from among one or more possible event types, comprising:

a verification module including analysis rules configured for verifying the internal consistency of data within a given message, the verification being based on sets of one or more verification rules, each set being particular to an event type; and

a message broker for routing messages from a source to a destination, the message broker including communications links to the plurality of service engines and the verification module for sending and receiving messages;

wherein the message broker is configured to forward received messages to the verification module for verification prior to routing the received messages.

2. The system of claim 1, wherein:

sets of one or more verification rules exist for some, but not all, of the possible event types that the message broker is configured to rout; and

the message broker is configured to forward to the verification module only the messages containing data representing events that are of an event type for which verification rules exist.

3. The system of claim 1, wherein the service engines are configured to process messages representing a series of events related to a given international business transaction, wherein:

the messages representing the series of events are each routed between service engines via the message broker; and

the message broker forwards a plurality of the events for a given transaction to the verification module for verification.

4. The system of claim 3, wherein the plurality of forwarded events for each given transaction includes the first event in the series of events and the last event in the series of events.

5. The system of claim 3, wherein the verification module and message broker are configured such that messages containing data that fails to pass verification are routed back to an original source for the series of events.

6. The system of claim 3, wherein the verification module and message broker are configured such that messages containing data that fails to pass verification are routed to a person having expertise in message correction.

7. The system of claim 1, wherein the message broker comprises a plurality of modules, including:

a reception module configured to receive messages from the plurality of service engines in a plurality of connection technologies;

a mapping module configured to map each received message to a format meeting an internal-broker data standard;

a data extraction module configured for determining each destination to which each message should be routed, and configured to map each message to a format meeting standards of its determined destination for each such determined destination; and

a data transfer module configured to send messages to each determined destination using a connection technology appropriate to each destination.

8. The system of claim 1, configured for use with a software firewall, the message broker and the plurality of service engines being on one side of the firewall, and with a second plurality of service engines on an opposite side of the firewall from the first message broker, and further comprising:

a second message broker on the opposite side of the firewall from the first message broker; and

a communications link placing the first and second message brokers in communication.

9. The system of claim 8, wherein the first message broker includes one or more modules, including:

a reception module configured to receive messages from the plurality of internal service engines in a plurality of connection technologies;

a mapping module configured to map each received message to a format meeting a first-broker data standard;

a data extraction module configured for determining each destination to which each message should be routed, and configured to map each message to a format meeting standards of its determined destination for each such determined destination; and

a data transfer module configured to send messages to each determined destination using a connection technologies appropriate to each destination.

10. The system of claim 9, wherein the second message broker includes one or more modules, including:

a reception module configured to receive messages from the plurality of external service engines in a plurality of connection technologies;

a mapping module configured to map each received message to a format meeting a second-broker data standard;

a data extraction module configured for determining each destination to which each message should be routed, and configured to map each message to a format meeting standards of its determined destination for each such determined destination; and

a data transfer module configured to send messages to each determined destination using a connection technologies appropriate to each destination.

11. The system of claim 10, wherein the first-broker data standard is the same as the second-broker data standard.

12. The system of claim 9, wherein:

the first message broker further includes a validation module configured to validate the syntax of one or more data of each received message using a set of syntax rules;

the validation module is configured to identify a set of correctable format errors in the format of each message, and is configured to correct each message that exhibits one or more of the correctable format errors; and

the second message broker is configured to authenticate that each message received from its side of the firewall is from an authorized source.