Hot service flow hardware offloads based on service priority and resource usage
First Claim
1. A method for managing communication over a network with a traffic management device (TMD) that includes a plurality of components and is operative to perform actions, comprising:
- employing at least one data flow segment (DFS) component to provide packet level flow handling for a portion of a plurality of connection flows;
employing at least one control segment (CS) component to perform actions, including;
managing the plurality of connection flows and handling a remainder portion of the plurality of connection flows;
generating, based on at least one received network packet for at least one of the plurality of managed connection flows, directional-bound patterns indicating directional traffic distributions within each service type within a plurality of service types;
generating, based on the at least one received network packet for the at least one of the plurality of managed connection flows, service patterns indicating a traffic distribution among the plurality of services;
employing the generated directional-bound patterns and service patterns to determine each hot connection flow in the plurality of managed connection flows to be handled by the DFS component; and
employing the DFS component to handle each determined hot connection flow, wherein the directional bound patterns and service patterns are employed by the CS to determine when one or more hot connection flows allocated for handling by the DFS is instead handled by the CS.
1 Assignment
0 Petitions
Accused Products
Abstract
Embodiments are directed towards improving the performance of network traffic management devices by optimizing the management of hot connection flows. A packet traffic management device (“PTMD”) employs a data flow segment (“DFS”) and control segment (“CS”). The CS performs high-level control functions and per-flow policy enforcement for connection flows maintained at the DFS, while the DFS performs statistics gathering, and per-packet policy enforcement, on connection flows maintained at the DFS. The DFS may include high-speed flow caches and other high-speed components. Making efficient use of the high speed flow cache capacity may be improved by maximizing the number of hot connection flows based on unique service and network traffic characteristics through adaptive feedback pattern learning together with administrator configurable service preferences that may have flow control data for most bandwidth hungry and desired hot services offloaded to the high-speed flow cache, at appropriate time.
116 Citations
23 Claims
-
1. A method for managing communication over a network with a traffic management device (TMD) that includes a plurality of components and is operative to perform actions, comprising:
-
employing at least one data flow segment (DFS) component to provide packet level flow handling for a portion of a plurality of connection flows; employing at least one control segment (CS) component to perform actions, including; managing the plurality of connection flows and handling a remainder portion of the plurality of connection flows; generating, based on at least one received network packet for at least one of the plurality of managed connection flows, directional-bound patterns indicating directional traffic distributions within each service type within a plurality of service types; generating, based on the at least one received network packet for the at least one of the plurality of managed connection flows, service patterns indicating a traffic distribution among the plurality of services; employing the generated directional-bound patterns and service patterns to determine each hot connection flow in the plurality of managed connection flows to be handled by the DFS component; and employing the DFS component to handle each determined hot connection flow, wherein the directional bound patterns and service patterns are employed by the CS to determine when one or more hot connection flows allocated for handling by the DFS is instead handled by the CS. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A network device, comprising:
-
a memory that is operative to store instructions; and one or more non-transitory processing devices that is operative to execute instructions that enable actions, including; employing at least one data flow segment (DFS) component to provide packet level flow handling for a portion of a plurality of connection flows; employing at least one control segment (CS) component to perform actions, including; managing the plurality of connection flows and handling a remainder portion of the plurality of connection flows; generating, based on at least one received network packet for at least one of the plurality of managed connection flows, directional-bound patterns indicating directional traffic distributions within each service type within a plurality of service types; generating, based on the at least one received network packet for the at least one of the plurality of managed connection flows, service patterns indicating a traffic distribution among the plurality of services; employing the generated directional-bound patterns and service patterns to determine each hot connection flow in the plurality of managed connection flows to be handled by the DFS component; and employing the DFS component to handle each determined hot connection flow, wherein the directional bound patterns and service patterns are employed by the CS to determine when one or more hot connection flows allocated for handling by the DFS is instead handled by the CS. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. An apparatus comprising a non-transitory computer readable medium, having computer-executable instructions stored thereon, that in response to execution by a network device, cause the network device to perform operations, comprising:
-
employing at least one data flow segment (DFS) component to provide packet level flow handling for a portion of a plurality of connection flows; employing at least one control segment (CS) component to perform actions, including; managing the plurality of connection flows and handling a remainder portion of the plurality of connection flows; generating, based on at least one received network packet for at least one of the plurality of managed connection flows, directional-bound patterns indicating directional traffic distributions within each service type within a plurality of service types; generating, based on the at least one received network packet for the at least one of the plurality of managed connection flows, service patterns indicating a traffic distribution among the plurality of services; employing the generated directional-bound patterns and service patterns to determine each hot connection flow in the plurality of managed connection flows to be handled by the DFS component; and employing the DFS component to handle each determined hot connection flow, wherein the directional bound patterns and service patterns are employed by the CS to determine when one or more hot connection flows allocated for handling by the DFS is instead handled by the CS. - View Dependent Claims (16, 17, 18, 19, 20)
-
-
21. A method that manages communication over a network with a traffic management device (TMD) that includes a plurality of components and is operative to perform actions, comprising:
-
employing at least one data flow segment (DFS) component to provide packet level flow handling for a portion of a plurality of connection flows; employing at least one control segment (CS) component to perform actions, including; managing the plurality of connection flows and handling a remainder portion of the plurality of connection flows; generating at least one connection flow metric based on at least one received network packet for at least one of the plurality of managed connection flows, the at least one connection flow metric providing information for each directional flow of packets for each of a plurality of services; employing the at least one connection flow metric to determine each hot connection flow in the plurality of managed connection flows; determining each hot connection flow to be handled by the DFS component based on a directional-bound traffic patterns within a same service type, and service patterns across different services within the plurality of services; modifying the hot connection flows that are determined to be handled by the DFS component based on real-time service priorities, service predictions, and a service usage limit; and employing the DFS component to handle each determined hot connection flow, wherein the directional bound patterns and service patterns are employed by the CS to determine when one or more hot connection flows allocated for handling by the DFS is instead handled by the CS. - View Dependent Claims (22, 23)
-
Specification