Method and apparatus for implementing persistent and reliable message delivery

• US 7,376,092 B2
• Filed: 03/28/2003
• Issued: 05/20/2008
• Est. Priority Date: 04/03/2002
• Status: Active Grant

• Current Assignee: Precache Incorporated
• Original Assignee: Precache Incorporated
• Inventors: Wang, Chung-Yih, Lin, Chih-mei, Yajnik, Shalini, Huang, Yennun, Chen, Tsu-Wei
• Primary Examiner(s): Orgad; Edan
• Assistant Examiner(s): Patel; Jay P.
• Application Number:
  US10/400,462
• Publication Number:
  US 20030189946A1
• Time in Patent Office: 1,880 Days
• Field of Search: 370/270, 370/401
• US Class Current: 370/270
• CPC Class Codes: H04L 67/53 using third party service providers
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

A method and apparatus provide for persistent caching of methods delivered via a publish-subscribe network. At a first node, a message having data via the network is received. The data is time-marked. The data is cached in a cache memory at the first node. The message is routed to a second node using content-based routing. These steps are repeated at a second node. A router that includes modules for executing this method is provided. A publish-subscribe network that includes nodes that include modules for executing this method is provided. A computer-readable medium that includes instructions for executing this method is provided.

Claims

1. A method for providing persistent caching of messages delivered via a publish-subscribe network, comprising the steps of:

(a) receiving, at a first node, a message having data via the network;

(b) time-marking the data;

(c) caching the data in a cache memory at the first node;

(d) routing the message to a second node using content-based routing;

(e) repeating steps (a) through (d) at the second node, wherein the data is cached in a cache memory at the second node;

(f) routing at least one of the messages from the second node to a subscriber machine using content-based routing;

(g) the second node receiving a request for cached data from the subscriber machine;

(h) determining a time-amount of cached data to retrieve in response to the request; and

(i) retrieving the determined time-amount of cached data based on the time-mark of the cached data.

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

determining if a time granularity G has passed since the caching step (c); and

moving the cached data from the cache memory to a disk based on a determination that G has passed.

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

determining if a persistent time-frame T has passed since the caching step (c) for a last block of the cached data; and

deleting the cached data based on a determination that T has passed for the last block of the cached data.

4. The method of claim 3, wherein T is set based on a channel with which the data is associated.

5. The method of claim 1, wherein the first node comprises an intelligent router and the receiving step (a) receives the message at the intelligent router.

6. The method of claim 5, wherein the intelligent router includes a cache manager and the cache manager performs steps (b) and (c).

7. The method of claim 1, wherein the second node comprises a subscriber machine.

8. A router for providing persistent caching of messages delivered via a publish-subscribe network, comprising modules for executing the method of claim 1.

9. A publish-subscribe network for providing persistent caching of messages, comprising nodes that include modules for executing the method of claim 1.

10. A computer-readable medium comprising instructions for executing the method of claim 1.

11. A method for providing persistent caching of messages delivered via a publish-subscribe network, comprising the steps of:

(a) receiving a plurality of messages having data via the network at a plurality of upstream nodes;

(b) time-marking the data;

(c) caching the data in cache memories at one or more of the plurality of upstream nodes;

(d) routing the messages to an edge node using content-based routing;

(e) repeating steps (a) through (c) at the edge node, wherein the data is cached in a cache memory at the edge node;

(f) routing at least one of the messages from the edge node to a subscriber machine using content-based routing;

(g) the edge node receiving a request for cached data from the subscriber machine;

(h) determining a time-amount of cached data to retrieve in response to the request; and

(i) retrieving the determined time-amount of cached data based on the time-mark of the cached data.

12. The method of claim 11, wherein the time-amount is determined from the request, wherein the request includes a requested time-amount of cached data to be retrieved.

13. The method of claim 11, wherein the time-amount is determined by calculating a disconnected time for the subscriber machine, wherein the disconnected time is the amount of time that the subscriber machine was disconnected from the publish-subscribe network.

14. The method of claim 11, further comprising the step of determining that at least some requested cached data is stored at one or more of the plurality of upstream nodes.

16. The method of claim 14, further comprising the steps of:

communicating the request for cached data to one or more of the plurality of upstream nodes;

retrieving requested cached data from the one or more of the plurality of upstream nodes; and

,

routing the retrieved data to the subscriber machine.

17. The method of claim 16, further comprising the step of performing duplicate suppression on the retrieved data.

18. A publish-subscribe network for providing persistent caching of messages, comprising a plurality of upstream nodes and an edge node, wherein the nodes include modules for executing the method of claim 11.

15. A method for providing persistent caching of messages delivered via a publish-subscribe network, comprising the steps of:

(a) receiving a plurality of messages having data via the network at a plurality of upstream nodes;

(b) time-marking the data;

(c) caching the data in cache memories at one or more of the plurality of upstream nodes;

(d) routing the messages to an edge node using content-based routing; and

,

(e) repeating steps (a) through (c) at the edge node, wherein the data is cached in a cache memory at the edge node;

(f) determining that at least some requested cached data is stored at one or more of the plurality of upstream nodes; and

(g) the edge node receiving a list of upstream nodes from the subscriber machine.