Granted Patent B2

US 12,425,347 · App. 17/967,795 · Granted Sep 23, 2025

Inventors: Navaneeth Krishnan Ramaswamy (Chennai, IN); Gopa Kumar (Milpitas, CA)

H04L47/2483H04L12/44H04L12/4633H04L12/4641H04L12/66H04L45/38H04L45/64H04L45/74H04L47/2441H04L47/803H04L67/1031

Abstract

Claims (21)

1. A software-defined wide area network (SD-WAN) connecting first and second sites, the SD-WAN comprising:

first and second edge forwarding nodes deployed respectively at first and second sites;

a plurality of sets of hub forwarding nodes deployed at a third site, with different sets of hub forwarding nodes configured to forward different types of traffic between the first and second sites;

wherein the first and second sites are branch office sites and the third site is a datacenter;

wherein each edge forwarding node at each particular site is configured:

to use flow attributes of received flows to identify, for each flow, a hub-selection rule from a plurality of hub selection rules, each hub-selection rule identifying at least one hub forwarding node at the third site for receiving one or more flows from the particular site, the plurality of hub-selection rules comprising at least one hub-selection rule identifying at least one hub forwarding node that is not identified by another hub-selection rule;

to use the hub-selection rule identified for each flow to identify a hub forwarding node at the third site; and

to send each flow from the particular site to the hub forwarding node identified for the flow.

2. The SD-WAN of claim 1 , wherein the flow attributes comprise five-tuple identifiers of the flows.

3. The SD-WAN of claim 1 , wherein the flow attributes comprise attributes other than layers 2-4 header values.

4. The SD-WAN of claim 3 , wherein the flow attributes comprise layer 7 (L7) attributes of the flows.

5. The SD-WAN of claim 4 , wherein the L7 attribute identifies a traffic type of the particular flow.

6. The SD-WAN of claim 1 , wherein each hub-selection rule in the plurality of hub-selection rules specifies at least two different sets of hub forwarding nodes for receiving at least two different categories of flows.

7. The SD-WAN of claim 6 , wherein at least two hub-selection rules identify a same set of hub forwarding nodes for receiving flows of first and second categories.

8. The SD-WAN of claim 1 , wherein the hub forwarding nodes act as gateways for accessing the resources at other branch sites or at a datacenter.

9. The SD-WAN of claim 8 , wherein the hub forwarding nodes also provide access to resources of a third-party Saas (Software as a Service) datacenter.

10. The SD-WAN of claim 1 , wherein the first and second sites are arranged topologically around the third site in a hub and spoke topology.

11. The SD-WAN of claim 1 further comprising a set of one or more controllers for generating a plurality of hub selection rules for the first and second edge forwarding nodes to use to select hub forwarding nodes for flows processed by the first and second edge forwarding nodes.

12. The SD-WAN of claim 11 , wherein the controller set collects statistics from the hub forwarding nodes, updates a set of hub selection rules based on the collected statistics, and distributes the updated set of hub selection rules to the first and second edge forwarding nodes.

13. The SD-WAN of claim 12 , wherein the controller analyzes the network traffic statistics to identify each set of forwarding hub nodes that needs additional or fewer hub forwarding nodes.

14. The SD-WAN of claim 12 , wherein an initial one hub-selection rule identifies a first set of hub nodes for first and second different sets of flow, and a updated hub-selection rule identifies a second set of hub nodes for the second set of flows.

Assignments (2)

Priority Claims (1)

Continuity (2)

References Cited (400)