Systems, software, and methods for routing events among publishers and subscribers on a computer network

• US 6,021,443 A
• Filed: 09/19/1997
• Issued: 02/01/2000
• Est. Priority Date: 01/18/1996
• Status: Expired due to Term

• Current Assignee: SimpleAir, Inc.
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Jankowski, Steve M., Bracho, Raphael
• Primary Examiner(s): Harrell, Robert B.
• Application Number:
  US08/934,452
• Time in Patent Office: 865 Days
• Field of Search: 364/DIG. 1 MS File, 364/DIG. 2 MS File, 395/200.3, 395/200.31, 395/200.32, 395/200.33, 395/200.36, 395/200.37, 395/200.47, 395/200.49, 395/200.52, 395/200.53, 395/200.54 , 395/200.56, 395/200.57, 395/200.58, 395/200.62, 395/200.68, 395/200.69, 395/200.71, 395/200.72, 395/200.73, 709/241
• US Class Current: 709/241
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 45/12 Shortest path evaluation
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

A method and apparatus for publishing and receiving events to and from a network. A plurality of "publisher" entities publish information and a plurality of "subscriber" entities request and use the information. Publishers and subscribers are connected to each other through a network. The network is a "store and forward" network whose routing is "content-based." The basic quanta of information is called an "event." Publishers publish events and subscribers subscribe to events that match criteria defined by the subscriber. Publication and subscription are performed asynchronously. Publishers and subscribers do not have direct knowledge of each other. The system receives a published event from a publisher and routes the event to all appropriate subscribers. Each subscriber is guaranteed to receive all events published on the system if, and only it they match the subscription criteria specified by the subscriber. A legacy data base can be added to the network by way of a data base connector, which can be a publisher, a subscriber, or both.

Claims

1. A method of routing an event in a data processing system including a plurality of interconnected hubs, between a publisher, which publishes events, and a subscriber, which subscribes to events, where the publisher is connected to a publisher hub and the subscriber is connected to a subscriber hub, the method comprising the steps of:

providing a data structure in a memory of at least the publisher hub and the subscriber hub, where each hub containing the data structure is termed a current hub and all hubs connected to a current hub are neighbor hubs of the current hub, the data structure being created by the current hub in accordance with information about physical hub connections, event types, advertisements, routes, and subscriptions of the system to form thereby a chain of subscriptions from the publisher hub to the subscriber hub; and

sending the event, by the publisher hub, to one of its neighbor hubs, the data structure in the publisher hub indicating that the neighbor hub is part of the chain of subscriptions extending from the publisher hub to the subscriber hub.

2. The method of claim 1, wherein the event is initially defined using OMG'"'"'s Interface Definition Language (IDL).

3. The method of claim 2, further including the steps of:

compiling the IDL to yield source code in the C programming language that includes a declaration of a type for the event and that further includes source code for creating and accessing the event; and

incorporating the declaration and the source code into source code for the publisher and source code for the subscriber.

4. The method of claim 1, further comprising the steps of:

receiving the event from the publisher hub, by a neighbor hub of the publisher hub; and

sending the event, by the neighbor hub of the publisher hub, to a neighbor hub of the neighbor hub, the data structure in the neighbor hub of the publisher hub indicating that its neighbor hub is on the least-cost path to the subscriber.

5. The method of claim 1, further comprising the step of:

receiving the event, by a hub that is not connected to the subscriber;

determining, by the hub that is not connected to the subscriber, in accordance with that hub'"'"'s data structure, that a neighbor hub is connected either directly or indirectly on the least-cost path to the subscriber; and

sending, by the hub not connected to the subscriber, the event to its neighbor hub, so that the event can be forwarded to the subscriber.

6. The method of claim 1, wherein the sending step includes the step of:

sending an event, by the publisher hub, to one of its neighbor hubs when the publisher hub indicates that the subscriber subscribes to events having values found in the event.

7. The method of claim 1, further including the step of:

sending an event, by the neighbor hub, to one of its neighbor hubs when the neighbor hub indicates that the subscriber subscribes to events having values found in the event.

8. The method of claim 1, wherein cost is measured in terms of the expense of sending information between two hubs.

9. The method of claim 1, wherein cost is measured in terms of the time required to send information between two hubs.

10. The method of claim 1, wherein cost is measured in terms of the convenience of sending information between two hubs.

11. The method of claim 1, further including the steps, performed by the subscriber, of:

registering as a subscriber with the subscriber hub;

registering subscriptions with the subscriber hub; and

setting up a call-back routine that will be invoked when the subscriber hub receives an event for the subscriber.

12. The method of claim 1, further including the steps, performed by the publisher, of:

determining whether it is time to publish an event;

providing an event data structure;

filling the event data structure with data; and

publishing the event by sending the event to the publisher hub.

13. The method of claim 1, wherein the publisher hub adds an envelope data structure containing information about the event to the event before the event is sent.

14. The method of claim 1, wherein the publisher hub adds a routing block to the event before the event is sent, a plurality of the routing blocks of the event defining a route that the event has taken from the publisher hub to the current hub.

15. The method of claim 1, further comprising the step of:

receiving the event, by a hub that is not connected to a second subscriber;

determining, by the hub that is not connected to the second subscriber, in accordance with that hub'"'"'s data structure, that a neighbor hub is connected either directly or indirectly on the least-cost path to the second subscriber; and

sending, by the hub not connected to the second subscriber, the event to its neighbor hub, so that the event can be forwarded to the second subscriber.

16. A method of routing an event in a data processing system having a plurality of interconnected hubs, between a publisher, which publishes events, and a subscriber, which subscribes to events, where the publisher is connected to a publisher hub and the subscriber is connected the method comprising the steps, of:

distributing information, among the plurality of hubs, about the interconnections among the plurality of hubs;

distributing information, among the plurality of hubs, identifying event types of events that the publisher may publish;

distributing, among the plurality of hubs, advertisements that describe events that the publisher may publish;

distributing, among the plurality of hubs, about routes among the plurality of hubs;

informing the plurality of hubs that the subscriber has subscribed to a type of event; and

creating a data structure in at least the publisher hub and the subscriber hub, where each hub containing the data is termed a current hub and all hubs connected to a neighbor hubs of the current hub, the data structure indicating which neighbor hub is on a oath between the subscriber'"'"'s hub, the data structure being including information about physical hub connections, event types, advertisements, routes, and subscriptions related to the plurality of hubs.

17. The method of claim 16, further comprising the step of:

sending the event, by the publisher hub, to one of its neighbor hubs, the data structure in the publisher hub indicating that the neighbor hub is on the least-cost path to the subscriber.

18. The method of claim 17, further comprising the step of:

receiving the event, by the hub connected to the subscriber;

determining, by the hub connected to the subscriber, in accordance with that hub'"'"'s data structure, that the subscriber has subscribed to the event; and

sending, by the hub connected to the subscriber, the event to the subscriber.

19. A system for routing an event in a data processing system having a plurality of interconnected hubs, comprising:

a publisher connected to a publisher hub of the plurality of hubs, which publishes event;

a subscriber connected to a subscriber hub of the plurality of hubs, which subscribes to events;

a memory containing a data structure, located in at least the publisher hub and the subscriber hub, where each hub containing the data structure is termed a current hub and all hubs connected to a current hub are neighbor hubs of the current hub, indicating which neighbor hub is on a path of hubs between publisher'"'"'s hub and the subscriber'"'"'s hub, the data structure including information about physical hub connections, event types, advertisements, routes, and subscriptions of the system;

a sending portion, in the publisher hub, configured to send the event to one of the publisher hub'"'"'s neighbor hubs, the data the publisher hub indicating that the neighbor hub is on the path to the subscriber; and

a receiving portion, in the subscriber hub, configured receive the event from a neighbor hub;

a determining portion, in the subscriber hub, in accordance with that subscriber hub'"'"'s data structure, that the subscriber has subscribed to the event; and

a sending portion, in the subscriber hub, configured to send the event to the subscriber.

20. A computer usable medium having computer embodied therein for routing an event between a publisher and a subscriber in a network of interconnected hubs, the program product comprising:

computer readable program code devices configured to cause a computer to effect provision of a data structure in a memory of at least the publisher hub and the subscriber hub, where the data structure is termed a current hub and all hubs to a current hub are neighbor hubs of the current hub, the data indicating which neighbor hub is on a path between the publisher'"'"'s hub and the subscriber'"'"'s hub, the data structure including information about physical hub connections, event types, advertisements, routes, subscriptions of the system;

computer readable program code devices configured a computer to effect sending the event, by the publisher hub, to of its neighbor hubs, the data structure in the publisher hub indicating the neighbor hub is on the path of the subscriber; and

computer readable program code devices configured to cause a computer to effect receiving the event, by the subscriber hub;

computer readable program code devices configured computer to effect determining, by the subscriber hub, with the hub'"'"'s data structure, that the subscriber has subscribed to the event; and

computer readable program code devices configured computer to effect sending, by the hub connected to the subscriber, the event to the subscriber.