Abstract: The technologies disclosed herein provide improvements to the Low Extra Delay Background Transport (LEDBAT) protocol. Some aspects of the present disclosure introduce an adaptive congestion window gain for background connections. In some configurations, a gain value for influencing the transmission rate of a background connection is dynamically adjusted based on data indicating a round trip time (RTT). The RTT includes a sum of a time in which the data is communicated to a remote device and a time in which acknowledgement is data returned from the remote device. In some configurations, the gain is decreased when the RTT is below a threshold and the gain is increased when the RTT is above the threshold. Among other features, the present disclosure also provides techniques involving a modified slow-start, multiplicative decrease and periodic slowdowns. The features disclosed herein mitigate some existing issues, such as latency drift, inter-LEDBAT fairness, and unnecessary slowdowns.

Abstract: A system communicates packets of data between two computers starting at an initial rate. The system then enters a slow start mode and increases the rate. As the rate increases, the system monitors acknowledgement data indicating a round trip time (RTT) associated with individual packets. When the RTT meets or exceeds a threshold, the system exits the slow start mode and continues the background connection a selected rate. The selected rate is based on the acknowledgement data associated with one or more packets having an RTT that meet or exceed the threshold. The features disclosed herein mitigate some of the issues with the LEDBAT protocol and other congestion control techniques, some which may include queue overflows and unnecessary slowdowns.

Abstract: The technologies disclosed herein provide improvements to the Low Extra Delay Background Transport (LEDBAT) protocol. Some aspects of the present disclosure introduce an adaptive congestion window gain for background connections. In some configurations, a gain value for influencing the transmission rate of a background connection is dynamically adjusted based on data indicating a round trip time (RTT). The RTT includes a sum of a time in which the data is communicated to a remote device and a time in which acknowledgement is data returned from the remote device. In some configurations, the gain is decreased when the RTT is below a threshold and the gain is increased when the RTT is above the threshold. Among other features, the present disclosure also provides techniques involving a modified slow-start, multiplicative decrease and periodic slowdowns. The features disclosed herein mitigate some existing issues, such as latency drift, inter-LEDBAT fairness, and unnecessary slowdowns.

Abstract: The technologies disclosed herein provide improvements to the Low Extra Delay Background Transport (LEDBAT) protocol. In some scenarios, a LEDBAT connection cannot obtain accurate measurements for the base delay that it relies on. Slowing down a connection, initially and periodically, can ensure that base delay measurements begin accurately and remain accurate throughout the life of a connection. Data is communicated between two computers in a slow start mode, where a rate of the communication is increased over time from an initial rate. When one or more conditions are met, e.g., an interval lapses, the communication is slowed for a predetermined time period. The communication of the data then resumes in a slow start mode, where a rate of the communication is increased over time from an initial rate.

Abstract: Keep alive management techniques are described. In one or more implementations, a keep alive interval is calculated by an operating system of the computing device. The keep alive interval is used to maintain one or more notification channels between one or more applications of the computing device and a network.

Abstract: Wake pattern management techniques are described. In one or more implementations, network traffic received by a network interface device of a computing device is monitored and a traffic pattern is recognized in the monitored network traffic. An application of the computing device is identified that corresponds to the recognized traffic pattern and responsive to this identification, at least a portion of the identified application is woken.

Abstract: Keep alive management techniques are described. In one or more implementations, a keep alive interval is calculated by an operating system of the computing device. The keep alive interval is used to maintain one or more notification channels between one or more applications of the computing device and a network.

Abstract: Keep alive management techniques are described. In one or more implementations, a keep alive interval is calculated by an operating system of the computing device. The keep alive interval is used to maintain one or more notification channels between one or more applications of the computing device and a network.

Abstract: Wake pattern management techniques are described. In one or more implementations, network traffic received by a network interface device of a computing device is monitored and a traffic pattern is recognized in the monitored network traffic. An application of the computing device is identified that corresponds to the recognized traffic pattern and responsive to this identification, at least a portion of the identified application is woken.

Abstract: Wake pattern management techniques are described. In one or more implementations, network traffic received by a network interface device of a computing device is monitored and a traffic pattern is recognized in the monitored network traffic. An application of the computing device is identified that corresponds to the recognized traffic pattern and responsive to this identification, at least a portion of the identified application is woken.

Abstract: A network interface that connects a computing device to a network may be configured to process incoming packets and determine an action to take with respect to each packet, thus decreasing processing demands on a processor of the computing device. The action may be indicating the packet to an operating system of the computing device immediately, storing the packet in a queue of one or more queues or discarding the packet. When the processor is interrupted, multiple packets aggregated on the network interface may be indicated to the operating system all at once to increase the device's power efficiency. Hardware of the network interface may be programmed to process the packets using filter criteria specified by the operating system based on information gathered by the operating system, such as firewall rules.

Abstract: Wake pattern management techniques are described. In one or more implementations, network traffic received by a network interface device of a computing device is monitored and a traffic pattern is recognized in the monitored network traffic. An application of the computing device is identified that corresponds to the recognized traffic pattern and responsive to this identification, at least a portion of the identified application is woken.

Abstract: Wake pattern management techniques are described. In one or more implementations, network traffic received by a network interface device of a computing device is monitored and a traffic pattern is recognized in the monitored network traffic. An application of the computing device is identified that corresponds to the recognized traffic pattern and responsive to this identification, at least a portion of the identified application is woken.

Abstract: Keep alive management techniques are described. In one or more implementations, a keep alive interval is calculated by an operating system of the computing device. The keep alive interval is used to maintain one or more notification channels between one or more applications of the computing device and a network.

Abstract: A network interface that connects a computing device to a network may be configured to process incoming packets and determine an action to take with respect to each packet, thus decreasing processing demands on a processor of the computing device. The action may be indicating the packet to an operating system of the computing device immediately, storing the packet in a queue of one or more queues or discarding the packet. When the processor is interrupted, multiple packets aggregated on the network interface may be indicated to the operating system all at once to increase the device's power efficiency. Hardware of the network interface may be programmed to process the packets using filter criteria specified by the operating system based on information gathered by the operating system, such as firewall rules.

Abstract: Keep alive management techniques are described. In one or more implementations, a keep alive interval is calculated by an operating system of the computing device. The keep alive interval is used to maintain one or more notification channels between one or more applications of the computing device and a network.

Abstract: In embodiments of a programming interface for data communications, a request queue and a completion queue can be allocated from a user-mode virtual memory buffer that corresponds to an application. The request queue and the completion queue can be pinned to physical memory and then mapped to kernel-mode system addresses so that the request queue and the completion queue can be accessed by a kernel-mode execution thread. A request can be received from an application for the kernel to handle data in the request queue, and a system issued to the kernel for the kernel-mode execution thread to handle the request. The kernel-mode execution thread can then handle additional requests from the application without additional system calls being issued.

Abstract: Keep alive management techniques are described. In one or more implementations, a keep alive interval is calculated by an operating system of the computing device. The keep alive interval is used to maintain one or more notification channels between one or more applications of the computing device and a network.

Abstract: Wake pattern management techniques are described. In one or more implementations, network traffic received by a network interface device of a computing device is monitored and a traffic pattern is recognized in the monitored network traffic. An application of the computing device is identified that corresponds to the recognized traffic pattern and responsive to this identification, at least a portion of the identified application is woken.

Abstract: A network interface that connects a computing device to a network may be configured to process incoming packets and determine an action to take with respect to each packet, thus decreasing processing demands on a processor of the computing device. The action may be indicating the packet to an operating system of the computing device immediately, storing the packet in a queue of one or more queues or discarding the packet. When the processor is interrupted, multiple packets aggregated on the network interface may be indicated to the operating system all at once to increase the device's power efficiency. Hardware of the network interface may be programmed to process the packets using filter criteria specified by the operating system based on information gathered by the operating system, such as firewall rules.