Content router with multiple forwarding elements instantiated on hardware entities

• US 7,844,733 B2
• Filed: 12/16/2004
• Issued: 11/30/2010
• 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): NGUYEN, THUONG
• Application Number:
  US11/012,169
• Publication Number:
  US 20050137998A1
• Time in Patent Office: 2,175 Days
• Field of Search: 709/241, 709/242, 709/244, 370/390, 370/393, 707/1, 707/755, 707/756, 707/791, 707/802, 707/2, 707/4, 707/102, 718/105
• US Class Current: 709/242
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 40/154 Tree transformation for tree-structured or markup documents, e.g. XSLT, XSL-FO or stylesheets
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1006 with static server selection, e.g. the same server being selected for a specific client

Abstract

A carrier grade content router, includes a distinct management plane for housing externally visible management applications, and coordinating and relaying external management requests to appropriate underlying application code in the router; a distinct control plane for running control protocols required within an XML routed network; and a distinct data plane for receiving and forwarding customer data. Some functions can be implemented in software or via a hardware accelerator.

Claims

1. A carrier grade router for use in an XML content-routed network wherein XML documents are routed through the XML content-routed network using XML markup language by matching content of the XML documents with subscriptions distributed through the network with an XML subscription management protocol, comprising:

a management plane for running management applications, and coordinating and relaying external management requests to appropriate management applications in the router;

a separate and distinct control plane for running an XML link state protocol to discover and monitor the topology of the XML content-routed network and the XML subscription management protocol to register and validate publishers and subscribers; and

a separate and distinct data plane for receiving and forwarding customer data, wherein said data plane is responsible for the following tasks;

terminating and separating control from data plane traffic in HTTP connections;

parsing XML documents and searching the content forwarding information database for matching XPath Expressions; and

performing document and application level transformations and the muiticast forwarding of individual documents; and

wherein said data plane comprises;

a common forwarding element manager for presenting a common interface from said data plane to said management plane and said control plane,

a plurality of XML forwarding elements in the router, each containing a content routing information base and instantiated on a distinct hardware entity, which is separate from other forwarding elements, for performing parsing, content matching and content transformation of incoming XML documents in parallel prior to forwarding said XML documents through the network, and

a load balancer for assigning incoming XML documents to each of said XML forwarding elements so as to distribute said incoming XML documents among said XML forwarding elements in accordance with a predetermined load balancing scheme.

2. The router of claim 1, wherein said management plane is configured to coordinate and relay said management requests via a management plane controller that forwards management requests and responses between management applications and other applications in said content router.

3. The router of claim 1, wherein XML parsing functions and content forwarding information database lookup functions are implemented in the companion hardware accelerator.

4. The router of claim 3, which is configured to permit access to the data plane components from the rest of the system through software abstraction techniques to allow other software subsystems to be independent of the data plane being implemented in hardware or software.

5. The router of claim 1, wherein said load balancer is configured to perform load balancing by one or more methods selected from the group consisting of:

interface load balancing;

socket based load balancing;

publisher based load balancing;

entitlement group load balancing;

dynamic usage based load balancing; and

preliminary content inspection based load balancing.

6. The router of claim 5, comprising at least one lookup table for identifying a forwarding element to use.

7. The router of claim 6, wherein said at least one lookup table comprises a first lookup table storing a logical element identifier and a second lookup table storing a physical forwarding element identifier, and whereby said logical forwarding element identifier is used to find the physical forwarding element identifier in said second table so that when a switchover occurs only an entry in the second lookup table need be updated.