IP Library Granted Patent US 9,007,912
Granted Patent B2
US 9,007,912 · App. 13/778,628 · Granted Apr 14, 2015

Serial clustering

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 9,007,912
App. No.
13/778,628
Granted
Apr 14, 2015
Kind
B2
Abstract

Serial clustering uses two or more network devices connected in series via a local and/or wide-area network to provide additional capacity when network traffic exceeds the processing capabilities of a single network device. When a first network device reaches its capacity limit, any excess network traffic beyond that limit is passed through the first network device unchanged. A network device connected in series with the first network device intercepts and will process the excess network traffic provided that it has sufficient processing capacity. Additional network devices can process remaining network traffic in a similar manner until all of the excess network traffic has been processed or until there are no more additional network devices. Network devices may use rules to determine how to handle network traffic. Rules may be based on the attributes of received network packets, attributes of the network device, or attributes of the network.

Claims (46)

1. A device adapted to process network traffic in conjunction with a plurality of additional devices, the device comprising:

a processor; and

a non-transitory computer-readable storage medium storing instructions that are executable by the processor, the instructions comprising:

instructions to receive a network packet;

instructions to determine if the device has sufficient processing capacity to process network traffic associated with the network packet;

instructions to identify, from among a plurality of rules, at least one matching rule matching the network packet, wherein the at least one matching rule is identified separately from at least one nonmatching rule not matching the network packet;

instructions to evaluate the network packet using the at least one identified matching rule to determine whether to accept or pass-through the network packet, wherein at least one nonmatching rule is skipped in evaluating the network packet and the at least one identified matching rule is evaluated in an order specified by a rule list;

instructions to forward the network packet to a selected additional device in response to a determination that the device does not have sufficient processing capacity to process the associated network traffic;

instructions to forward the network packet to the selected additional device in response to the evaluation of the at least one identified matching rule determining to pass-through the network packet; and

instructions to accept the network packet in response to a determination that the device does have sufficient processing capacity to process the associated network traffic and in response to the evaluation of the at least one identified matching rule determining to accept the network packet;

wherein the device is connected to the selected additional device in a serial cluster, and

wherein the devices in the serial cluster are configured to not respond to auto-discovery probe messages from each other.

2. The device of claim 1 , wherein the instructions to receive the network packet include instructions to intercept the network packet on a data network between a source and a destination.

3. The device of claim 1 , wherein the network traffic associated with the network packet includes at least one network connection.

4. The device of claim 3 , wherein the network connection is a TCP connection.

5. The device of claim 3 , wherein the network packet includes a request to initiate the network connection.

6. The device of claim 3 , wherein the at least one identified matching rule accepts the network packet if the network connection has been previously accepted by the device.

7. The device of claim 3 , wherein the at least one identified matching rule causes the network packet to pass-through if the network connection has been previously accepted by the additional device.

8. The device of claim 1 , wherein the at least one identified matching rule causes the network packet to pass-through if the network packet includes auto discovery information associated with the additional device.

9. The device of claim 1 , wherein the at least one identified matching rule includes a criteria for evaluating the network packet.

10. The device of claim 9 , wherein the criteria specifies a condition for accepting the network packet.

11. The device of claim 9 , wherein the criteria specifies a condition for passing-through the network packet.

12. The device of claim 9 , wherein the criteria is based on a property of the network packet.

13. The device of claim 9 , wherein the criteria is based on a property of the device.

14. The device of claim 1 , wherein the at least one identified matching rule accepts the network packet if the network packet is directed to a network entity associated with the device.

15. The device of claim 14 , wherein the network entity is a client computer.

16. The device of claim 14 , wherein the network entity is a server computer.

17. The device of claim 14 , wherein the network entity is connected with the device via a local data network connection.

18. The device of claim 1 , wherein the processing capacity of the device includes a maximum number of network connections.

19. The device of claim 1 , wherein the processing capacity of the device includes a maximum bandwidth of the device.

20. The device of claim 1 , wherein the device is configured to operate in a serial cluster with the additional device.

21. The device of claim 20 , wherein the device communicates with the selected additional device via a local data network.

22. The device of claim 1 , wherein the device communicates with the selected additional device via a wide-area data network.

23. A method of processing network traffic, the method comprising:

receiving a network packet by a network device;

determining if the network packet is initiating a network connection;

identifying, from among a plurality of rules, a matching rule matching the network packet in response to the determination that the network packet is initiating a network connection, wherein the identified matching rule is identified separately from at least one nonmatching rule not matching the network packet;

evaluating the identified matching rule on the network packet in response to the identified matching rule matching the network packet to determine if the network packet should be accepted or passed-through, wherein at least one nonmatching rule is skipped in evaluating the network packet and the identified matching rule is evaluated in an order specified by a rule list;

determining if there is sufficient processing capacity to handle the network packet and an associated network connection in response to the identified matching rule indicating that the network packet should be accepted;

determining if there is sufficient processing capacity to handle the network packet and the associated network connection in response to the network packet not matching any rules;

accepting the network packet in response to the determination that there is sufficient processing capacity to handle the network packet;

passing the network packet through to a selected device in response to the identified rule indicating that the network packet should be passed-through; and

passing the network packet through to the selected device in response to the determination that there is not sufficient processing capacity;

wherein the network device is connected with the selected device in a serial cluster,

wherein the network devices in the serial cluster are configured to not respond to auto-discovery probe messages from each other.

24. The method of claim 23 , wherein passing the network packet through includes forwarding the network packet to an additional network device.

Assignments (17)
RELEASE OF SECURITY INTEREST Recorded Aug 11, 2023
From: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC; RIVERBED HOLDINGS, INC.
Reel/Frame 064673/0739 →
CHANGE OF NAME Recorded Feb 18, 2022
From: RIVERBED TECHNOLOGY, INC.
To: RIVERBED TECHNOLOGY LLC
Reel/Frame 059232/0551 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS U.S. COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0169 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0046 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0108 →
SECURITY INTEREST Recorded Dec 10, 2021
From: RIVERBED TECHNOLOGY LLC (FORMERLY RIVERBED TECHNOLOGY, INC.); ATERNITY LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS U.S. COLLATERAL AGENT
Reel/Frame 058486/0216 →
PATENT SECURITY AGREEMENT Recorded Oct 27, 2021
From: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 057943/0386 →
PATENT SECURITY AGREEMENT SUPPLEMENT - FIRST LIEN Recorded Oct 14, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 057810/0502 →
PATENT SECURITY AGREEMENT SUPPLEMENT - SECOND LIEN Recorded Oct 14, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
Reel/Frame 057810/0559 →
RELEASE OF SECURITY INTEREST IN PATENTS RECORED AT REEL 056397, FRAME 0750 Recorded Oct 13, 2021
From: MACQUARIE CAPITAL FUNDING LLC
To: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 057983/0356 →
SECURITY INTEREST Recorded May 26, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: MACQUARIE CAPITAL FUNDING LLC
Reel/Frame 056397/0750 →
PATENT SECURITY AGREEMENT Recorded Mar 5, 2021
From: RIVERBED TECHNOLOGY, INC.
To: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
Reel/Frame 055514/0249 →
CORRECTIVE ASSIGNMENT TO CORRECT THE CONVEYING PARTY NAME PREVIOUSLY RECORDED ON REEL 035521 FRAME 0069. ASSIGNOR(S) HEREBY CONFIRMS THE RELEASE OF SECURITY INTEREST IN PATENTS. Recorded Jun 2, 2015
From: JPMORGAN CHASE BANK, N.A.
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 035807/0680 →
SECURITY INTEREST Recorded May 1, 2015
From: RIVERBED TECHNOLOGY, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 035561/0363 →
RELEASE OF SECURITY INTEREST IN PATENTS Recorded Apr 28, 2015
From: BARCLAYS BANK PLC
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 035521/0069 →
PATENT SECURITY AGREEMENT Recorded Dec 27, 2013
From: RIVERBED TECHNOLOGY, INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 032421/0162 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 25, 2013
From: WU, DAVID TZE-SI; GUPTA, NITIN; LY, KAND
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 030289/0948 →