Meta-tagging in content routed networks

• US 7,526,493 B2
• Filed: 12/16/2004
• Issued: 04/28/2009
• Est. Priority Date: 12/19/2003
• Status: Active Grant

• Current Assignee: Solace Corp.
• Original Assignee: Solace Systems, Inc. (United Kingdom)
• Inventors: Barnes, Martin, Ashton, Peter, Bertin, Greg, Pochopsky, David, Burwell, Wayne, Betts, Craig
• Primary Examiner(s): Le; Debbie M
• Assistant Examiner(s): Hotelling; Harold A
• Application Number:
  US11/012,168
• Publication Number:
  US 20050138019A1
• Time in Patent Office: 1,594 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/30 Routing of multiclass traffic
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]

Abstract

A method of adding meta-data to document in a content-routed network including a plurality of routers interconnected by links involves adding an encoded meta-tag to the document.

Claims

1. A computer-implemented method of forwarding a document through a content-routed network including a plurality of content based routers interconnected by links, wherein documents are forwarded through the network based on their content, comprising:

(a) receiving the document from a publisher at an ingress router;

(b) said ingress router matching the content of said document received from the publisher with subscriptions for the network in accordance with a content routing protocol to identify the address of egress routers requiring the document for distribution to subscribers attached thereto based on the content of the document as received from the publisher;

(c) said ingress router attaching a meta-data tag to the document;

(d) said meta-data tag including at least one meta-data field updatable at each router traversed by the document and representative of the progress of said document through the network;

(e) said meta-data tag further including an address meta-data field containing the address of the ingress router and the address of each said identified egress router requiring the document for distribution to subscribers attached thereto as determined by said content routing protocol;

(f) forwarding said document to downstream routers determined by said address meta-data field;

(g) receiving the document at said one or more downstream routers;

(h) reading said at least one updatable meta-data field at one or more said downstream routers;

(i) each of said one or more downstream routers performing a preliminary check by comparing the value of said updatable meta-data field with predetermined criteria to determine whether the document should be discarded prior to determining how said document should be forwarded; and

(j) if the data in said meta-data field matches said predetermined criteria, discarding said document, and

(k) if the data in said meta-data field does not match said predetermined criteria, determining whether the address of said downstream router appears in said address meta-data field, and if the address of said downstream router appears in said address meta-data field matching the content of said document against a database of local subscribers who require a copy of the document and forwarding the document to said local subscribers after stripping off the meta-data tag so that said local subscribers receive said document as supplied by the publisher;

(l) each of said one or more downstream routers updating said meta-data field to indicate that the document has been received by that downstream router;

(m) forwarding the document to any further downstream routers listed in said address meta-data field, and

(n) repeating steps g to m at each remaining downstream router listed in said address meta-data field, and

wherein said meta-data tag further comprises a “

Traversed Routers”

field, each router through which the document passes adds its own address to said “

Traversed Routers”

field, and when a downstream router reads its own address in said “

Traversed Routers field”

, that downstream router discards the document.

2. The computer-implemented method of claim 1, wherein said document is transmitted over an HTTP connection, and said meta-data is added to an HTTP header.

3. The computer-implemented method of claim 2, wherein said meta-data tag comprises a “

hops left”

field determining the number of routers the document is permitted to traverse, and wherein each downstream router decrements the value of said “

hops left”

field as the document passes therethrough until said value reaches a predetermined value, whereupon when a particular said downstream router reads said predetermined value in said “

hops left”

field, that downstream router discards the document.

4. The computer-implemented method of claim 3, wherein said meta-data tag includes a field identifying the publisher of the document.

5. The computer-implemented method of claim 3, wherein said meta-data tag further comprises a priority field assigning a priority level to said document, and wherein after reading said priority field, said downstream routers use the value of said priority field to enforce quality of service policies in processing different documents.

6. The computer-implemented method of claim 1, wherein publishers and subscribers are organized into entitlement groups, each entitlement group being assigned a unique identifier, said entitlement groups determining which subscribers are permitted to receive documents from any particular publisher, and said meta-data tag further comprises an “

entitlement group”

field, and when a said downstream router matches a received document against a subscription, that downstream router reads said entitlement field to determine whether the corresponding matching subscriber is a member of the entitlement group identified in the entitlement group field, and only if the matching subscriber is a member of the corresponding entitlement group does the downstream router forward the document to the matching subscriber.

7. The computer-implemented method of claim 1, wherein said meta-data tag further comprises a “

checksum”

field, and downstream routers read the checksum field to determine whether a document has become corrupted as it traverses the network.

8. The computer-implemented method of claim 1, wherein said meta-data tag further comprises a “

version”

field that differentiates between old formats or semantics and a newer format or semantics of the meta-data.

9. The computer-implemented method of claim 1, wherein said document is XML encoded, and said meta-data tags are attached to said XML document.

10. The computer-implemented method of claim 9, wherein said meta tag is an XML header (XMH) that is inserted by the first content router traversed by said document.

11. The computer-implemented method of claim 10, wherein said XML header is stripped from said document by the last content router that delivers the document to a subscriber.

12. The computer-implemented method of claim 1, wherein an egress content-based router is configured to supply some of the meta-data with the document, with possible transformation, when delivering said document to an attached subscriber.

13. The computer-implemented method of claim 1, wherein an egress content-based router delivering said document to an attached subscriber is configured to remove, replace or transform some meta-data items when sending a document over a link to a different administrative domain, or when receiving a document over a link from a different administrative domain.