Back to results
US 11,063,785 B2Granted
Multipath traffic management
AssigneeIntel Corporation
InventorsGeorge Milescu, Silviu Petria, Andra Paraschiv
Life of this patent
Estimating the term…
Abstract
One embodiment provides an apparatus. The apparatus includes client traffic management (CTM) logic. The CTM logic is to trigger implementation of a selected network traffic flow related to the client device, the triggering based, at least in part, on a network traffic flow related to the client device. The network traffic flow is associated with a connection and includes at least one subflow. Each subflow is carried by a respective path associated with the connection. The triggering includes at least one of constraining and/or adjusting an allowable throughput at a service provider for one or more of the at least one subflow. The selected traffic policy is to be implemented in a transport layer.
Claims18
An apparatus comprising:
- multipath proxy circuitry to:
- capture network traffic flow data included in packet headers, the network traffic flow data related to a network traffic flow to each respective one of a plurality of communicatively coupled client devices;
- and
- client traffic management (CTM) circuitry to, for each respective client device of the plurality of communicatively coupled client devices:
- determine a round trip time (RTT) for the network traffic flow using the captured network traffic flow data;
- select, based on the RTT for the network traffic flow associated with the respective client device, a traffic management policy from a plurality of traffic management policies stored at a policy store communicatively coupled to the CTM circuitry, the selected traffic management policy including one of:
- an application-based policy associated with a type of network traffic of the network traffic flow, a congestion-based policy associated with congestion for the network traffic flow, or a service level agreement (SLA)-based policy associated with SLA parameters specified for the network traffic flow by an SLA;
- and
- trigger implementation of the selected traffic management policy on network traffic associated with the respective client device, based on the network traffic flow data associated with the respective client device, by adjusting an allowable throughput for a selected subflow within the network traffic flow associated with the respective client device;
- wherein the selected traffic management policy is implemented without transmitting the traffic management policy to the plurality of communicatively coupled client devices.
7 more elements
A method comprising:
- capturing, by multipath proxy circuitry, network traffic flow data included in packet headers, the network traffic flow data related to a network traffic flow to each respective one of a plurality of communicatively coupled client devices;
- and
- for each respective client device of the plurality of communicatively coupled client devices:
- determining, by client traffic management (CTM) circuitry, a round trip time (RTT) for the network traffic flow using the network traffic flow data captured by the multipath proxy circuitry;
- selecting, by the CTM circuitry and based on the RTT for the network traffic flow associated with the respective client device, a traffic management policy from a plurality of traffic management policies stored at a policy store communicatively coupled to the CTM circuitry, the selected traffic management policy including one of:
- an application-based policy associated with a type of network traffic of the network traffic flow, a congestion-based policy associated with congestion for the network traffic flow, or a service level agreement (SLA)-based policy associated with SLA parameters specified for the network traffic flow by an SLA;
- and
- triggering, by the CTM circuitry, implementation of a selected traffic management policy on network traffic associated with the respective client device, based on a the network traffic flow data associated with the respective client device, by adjusting an allowable throughput for a selected subflow within the network traffic flow associated with the respective client device;
- wherein the selected traffic management policy is implemented without transmitting the traffic management policy to the plurality of communicatively coupled client devices.
6 more elements
A system comprising:
- a processor;
- a communication interface to communicate with one or more client devices;
- multipath proxy circuitry to:
- capture network traffic flow data included in packet headers, the network traffic flow data related to a network traffic flow to each respective one of a plurality of communicatively coupled client devices;
- and
- client traffic management (CTM) circuitry to, for each respective client device of the plurality of communicatively coupled client devices:
- determine a round trip time (RTT) for the network traffic flow using the network traffic flow data captured by the multipath proxy circuitry;
- select, based on the RTT for the network traffic flow associated with the respective client device, a traffic management policy from a plurality of traffic management policies stored at a policy store communicatively coupled to the CTM circuitry, the selected traffic management policy including one of:
- an application-based policy associated with a type of network traffic of the network traffic flow, a congestion-based policy associated with congestion for the network traffic flow, or a service level agreement (SLA)-based policy associated with SLA parameters specified for the network traffic flow by an SLA;
- and
- trigger implementation of the selected traffic management policy on network traffic associated with the respective client device, based on the network traffic flow data associated with the respective client device, by adjusting an allowable throughput for a selected subflow within the network traffic flow associated with the respective client device;
- wherein the selected traffic management policy is implemented without transmitting the traffic management policy to the one or more client devices.
9 more elements
Dependencies are inferred from the claim text.