Minimize recycle SYN issues for split TCP hot flows to improve system reliability and performance
First Claim
1. A method for managing communication over a network, comprising the actions of:
- providing a connection flow request to a traffic management device (“
TMD”
) that is operative to manage communication between at least one client device and at least one server device, wherein the TMD includes a control segment (“
CS”
) that handles at least one flow of control communication and two or more data flow segments (“
DFS”
) that separately maintain an incoming direction and an outgoing direction for a flow of data communication;
employing the TMD to generate an identifier that corresponds to a connection flow based on the connection flow request, wherein the identifier is separate from a connection flow signature of the connection flow, and wherein the CS caches the identifier and provides the identifier to the two or more DFSs;
employing the CS to establish the connection flow between a client device and a server device that is based at least on the identifier and the connection flow request, wherein the two or more DFSs store the identifier separately from the CS;
employing the two or more DFSs to provide an update to the connection flow and the separately stored identifier to the CS;
comparing the identifier provided by the two or more DFSs to the CS to the identifier cached at the CS, wherein a match indicates the update is valid and a difference indicates the update is invalid; and
determining when the update is valid based on the comparison of the identifier provided by the two or more DFSs to the CS and the identifier cached at the CS, wherein a validated update is employed by the CS for further handling the control communication for the connection flow.
1 Assignment
0 Petitions
Accused Products
Abstract
Embodiments are directed towards employing a packet traffic management device that has a split data flow segment (“DFS”) and control segment (“CS”) to determine if a connection flow update provided by the DFS to the CS is valid. The CS may be utilized to establish connection flows at the DFS based on connection flow requests. The CS may generate a connection flow identifier (“CFID”) for a connection flow request. The CS may cache the CFID at the CS. The CS may establish a connection flow at the DFS based at least on the connection flow request and the CFID. After a connection flow is established, a DFS may provide a connection flow update and a corresponding CFID to the CS. The CS may determine that the connection flow update is valid if the corresponding CFID matches the CFID cached at the CS.
98 Citations
28 Claims
-
1. A method for managing communication over a network, comprising the actions of:
-
providing a connection flow request to a traffic management device (“
TMD”
) that is operative to manage communication between at least one client device and at least one server device, wherein the TMD includes a control segment (“
CS”
) that handles at least one flow of control communication and two or more data flow segments (“
DFS”
) that separately maintain an incoming direction and an outgoing direction for a flow of data communication;employing the TMD to generate an identifier that corresponds to a connection flow based on the connection flow request, wherein the identifier is separate from a connection flow signature of the connection flow, and wherein the CS caches the identifier and provides the identifier to the two or more DFSs; employing the CS to establish the connection flow between a client device and a server device that is based at least on the identifier and the connection flow request, wherein the two or more DFSs store the identifier separately from the CS; employing the two or more DFSs to provide an update to the connection flow and the separately stored identifier to the CS; comparing the identifier provided by the two or more DFSs to the CS to the identifier cached at the CS, wherein a match indicates the update is valid and a difference indicates the update is invalid; and determining when the update is valid based on the comparison of the identifier provided by the two or more DFSs to the CS and the identifier cached at the CS, wherein a validated update is employed by the CS for further handling the control communication for the connection flow. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A traffic management device (“
- TMD”
) for managing communication over a network, comprising;a network interface device for communicating over a network; a memory device for storing instructions; and a processor device for executing instructions to enable actions, including; processing a connection flow request that is operative to manage communication between at least one client device and at least one server device, wherein the TMD includes a control segment (“
CS”
) that handles at least one flow of control communication and two or more data flow segments (“
DFS”
) that separately maintain an incoming direction and an outgoing direction for a flow of data communication;generating an identifier that corresponds to a connection flow based on the connection flow request, wherein the identifier is separate from a connection flow signature of the connection flow, and wherein the CS caches the identifier and provides the identifier to the two or more DFSs; employing the CS to establish the connection flow between a client device and a server device that is based at least on the identifier and the connection flow request, wherein the two or more DFSs store the identifier separately from the CS; employing the two or more DFSs to provide an update to the connection flow and the separately stored identifier to the CS; comparing the identifier provided by the two or more DFSs to the CS to the identifier cached at the CS, wherein a match indicates the update is valid and a difference indicates the update is invalid; and determining when the update is valid based on the comparison of the identifier provided by the two or more DFSs to the CS and the identifier cached at the CS, wherein a validated update is employed by the CS for further handling the control communication for the connection flow. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17)
- TMD”
-
18. A system for managing communication over a network, comprising:
-
a client device; a server device; and a traffic management device (“
TMD”
), including;a network interface device for communicating over a network; a memory device for storing instructions; and a processor device for executing instructions to enable actions, including; processing a connection flow request that is operative to manage communication between at least one client device and at least one server device, wherein the TMD includes a control segment (“
CS”
) that handles at least one flow of control communication and two or more data flow segments (“
DFS”
) that separately maintain an incoming direction and an outgoing direction for a flow of data communication;generating an identifier that corresponds to a connection flow based on the connection flow request, wherein the identifier is separate from a connection flow signature of the connection flow, and wherein the CS caches the identifier and provides the identifier to the two or more DFSs; employing the CS to establish the connection flow between a client device and a server device that is based at least on the identifier and the connection flow request, wherein the two or more DFSs store the identifier separately from the CS; employing the two or more DFSs to provide an update to the connection flow and the separately stored identifier to the CS; comparing the identifier provided by the two or more DFSs to the CS to the identifier cached at the CS, wherein a match indicates the update is valid and a difference indicates the update is invalid; and determining when the update is valid based on the comparison of the identifier provided by the two or more DFSs to the CS and the identifier cached at the CS, wherein a validated update is employed by the CS for further handling the control communication for the connection flow. - View Dependent Claims (19, 20, 21, 22, 23, 24)
-
-
25. A processor readable non-transitive storage media that includes instructions for managing communication over a network, wherein the execution of the instructions by a network device enables actions, comprising:
-
providing a connection flow request to a traffic management device (“
TMD”
) that is operative to manage communication between at least one client device and at least one server device, wherein the TMD includes a control segment (“
CS”
) that handles at least one flow of control communication and two or more data flow segments (“
DFS”
) that maintain at least one flow of data communication;employing the TMD to generate an identifier that corresponds to a connection flow based on the connection flow request, wherein the identifier is separate from a connection flow signature of the connection flow, and wherein the CS caches the identifier and provides the identifier to the two or more DFSs; employing the CS to establish the connection flow between a client device and a server device that is based at least on the identifier and the connection flow request, wherein the two or more DFSs store the identifier separately from the CS; employing the two or more DFSs to provide an update to the connection flow and the separately stored identifier to the CS; comparing the identifier provided by the two or more DFSs to the CS to the identifier cached at the CS, wherein a match indicates the update is valid and a difference indicates the update is invalid; and determining when the update is valid based on the comparison of the identifier provided by the two or more DFSs to the CS and the identifier cached at the CS, wherein a validated update is employed by the CS for further handling the control communication for the connection flow. - View Dependent Claims (26, 27, 28)
-
Specification