IP Library Granted Patent US 8,149,736
Granted Patent B2
US 8,149,736 · App. 12/728,977 · Granted Apr 3, 2012

Distributed storage of routing information in a link state protocol controlled network

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,149,736
App. No.
12/728,977
Granted
Apr 3, 2012
Kind
B2
Abstract

A distributed hash table is implemented to store routing information on a network. Node IDs exchanged in connection with implementation of a link state routing protocol are used as keys in the distributed hash table, and routes are stored at one or more nodes on the network. When a route is learned, the route is processed against the set of keys to determine which nodes should store the route. When a route is needed, the route is processed against the set of keys to determine which nodes should have the route information. The manner in which the route is processed against the set of keys is the same in both instances, so that the DHT may be used to store and retrieve route information on the network. The DHT may be implemented to store MAC addresses, IP addresses, MPLS labels, or other information of interest to enable routes to be stored and learned by network elements on the network.

Claims (37)

1. A method of learning a route to a destination address in link state protocol controlled network having a link state database implemented as a distributed hash table, the method comprising the steps of:

performing a hash on the destination address to obtain a route identifier;

comparing the route identifier with node identifiers in a membership table to determine at least one node of the distributed hash table to query for routing information for the route identifier, the membership table containing a listing of all nodes in the network implementing the distributed hash table;

determining, from the membership table, a network address of the at least one determined node; and

querying the at least one determined node for routing information for the route identifier.

2. A method as defined in claim 1 , further comprising:

receiving route information from at least one of the queried nodes.

3. A method as defined in claim 1 , wherein the step of comparing the route identifier with node identifiers comprises performing an XOR process between the route identifier and each of the node identifiers to determine at least one node identifier that is considered closest to the route identifier.

4. A method as defined in claim 3 , wherein:

the step of comparing the route identifier with node identifiers determines a plurality of nodes to query for routing information for the route identifier; and

the step of querying the at least one determined node for routing information comprises querying plural determined nodes.

5. A method as defined in claim 4 , further comprising:

receiving route information from plural queried nodes; and

selecting route information from the received route information.

6. A method as defined in claim 1 , wherein the node identifiers correspond to network addresses, and the route identifiers correspond to destination network addresses.

7. A method as defined in claim 6 , wherein the node identifiers are derived from the corresponding network addresses.

8. A method as defined in claim 6 , wherein the route identifiers are derived from the corresponding destination network addresses.

9. A method as defined in claim 6 , wherein the corresponding network addresses are addresses in a first OSI addressing layer.

10. A method as defined in claim 6 , wherein the corresponding network addresses are addresses selected from the group consisting of MAC addresses and IP addresses.

11. The method of claim 1 , further comprising the step of exchanging node IDs using a routing system, and wherein the listing of all nodes in the network implementing the distributed hash table is learned from the routing system.

12. Apparatus for learning a route to a destination address in link state protocol controlled network having a link state database implemented as a distributed hash table, comprising:

a processor configured to perform a hash on the destination address to obtain a route identifier and to compare the route identifier with node identifiers in a membership table to determine at least one node of the distributed hash table to query for routing information for the route identifier, the membership table containing a listing of all nodes in the network implementing the distributed hash table, the processor further being configured to determine, from the membership table, a network address of the at least one determined node; and

a transmitter configured to query to the at least one determined node for routing information for the route identifier.

13. An apparatus as defined in claim 12 , further comprising:

a receiver configured to receive route information from at least one of the queried nodes.

14. An apparatus as defined in claim 12 , wherein the processor is configured to compare the route identifier with node identifiers by performing an XOR process between the route identifier and each of the node identifiers to determine at least one node identifier that is considered closest to the route identifier.

15. An apparatus as defined in claim 14 , wherein:

the processor is configured to determine a plurality of nodes to query for routing information for the route identifier; and

the transmitter is configured to query plural determined nodes.

16. An apparatus as defined in claim 15 , wherein:

the receiver is configured to receive route information from plural queried nodes; and

the processor is configured to select route information from the received route information.

17. An apparatus as defined in claim 12 , wherein the node identifiers correspond to network addresses, and the route identifiers correspond to destination network addresses.

18. An apparatus as defined in claim 17 , wherein the node identifiers are derived from the corresponding network addresses.

19. An apparatus as defined in claim 17 , wherein the route identifiers are derived from the corresponding destination network addresses.

20. An apparatus as defined in claim 17 , wherein the corresponding network addresses are addresses in a first OSI addressing layer.

21. An apparatus as defined in claim 17 , wherein the corresponding network addresses are addresses selected from the group consisting of MAC addresses and IP addresses.

Assignments (5)
RELEASE (REEL 038041 / FRAME 0001) Recorded Jan 2, 2018
From: JPMORGAN CHASE BANK, N.A.
To: RPX CORPORATION; RPX CLEARINGHOUSE LLC
Reel/Frame 044970/0030 →
SECURITY AGREEMENT Recorded Mar 9, 2016
From: RPX CORPORATION; RPX CLEARINGHOUSE LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 038041/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 9, 2015
From: ROCKSTAR CONSORTIUM US LP; ROCKSTAR CONSORTIUM LLC; BOCKSTAR TECHNOLOGIES LLC; CONSTELLATION TECHNOLOGIES LLC; MOBILESTAR TECHNOLOGIES LLC; NETSTAR TECHNOLOGIES LLC
To: RPX CLEARINGHOUSE LLC
Reel/Frame 034924/0779 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 11, 2013
From: ROCKSTAR BIDCO, LP
To: ROCKSTAR CONSORTIUM US LP
Reel/Frame 031390/0206 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 28, 2011
From: NORTEL NETWORKS LIMITED
To: ROCKSTAR BIDCO, LP
Reel/Frame 027143/0717 →