Abstract: A network device receives, from a congestion controller, traffic policy information associated with a data stream between a sender and a receiver, where the traffic policy information includes a maximum round trip delay time (RTT) and a maximum throughput rate (Rate). The network device obtains a receiver advertised window size (RWND) for the receiver for the data stream. The network device modifies the RWND based on the RTT and the Rate to produce a modified receiver window size (RWND?) and sends the RWND? to the sender for use in controlling congestion on the data stream between the sender and the receiver.

Abstract: Systems and methods for pacing data transmission are described. An illustrative method includes transmitting, by a network device, a data stream at a pacing rate to a user equipment (UE) device. The method further includes accessing a metric of a radio access network (RAN) to which the UE device is connected, the metric associated with the UE device. The method further includes adjusting, based on the metric, the pacing rate at which the data stream is transmitted to the UE device.

Abstract: A user device may measure unidirectional latency of applications over asymmetric links. The user device may accurately measure application level unidirectional latency over cellular networks, without synchronizing system clocks. The user device may accurately measure the unidirectional latency in both an uplink direction and a downlink direction, without using a high-precision system clock and without synchronizing clocks between the user device and an application server.

Abstract: A system may include a first network device. The first network device may include a first processor configured to: obtain a copy of a first message sent from an application on a User Equipment device (UE); construct a signature based on the copy of the first message; and send a second message including the signature to a second network device. The second message may request the second network device to either train a classification model or to provide a device type of the UE or an application type of the application to the first network device.

Abstract: A network device includes a network interface for establishing a communication session with another network device, a memory to store instructions, and a processor to execute the instructions. The processor may, for each time period during the communication session, adjust a size of a receive buffer of a socket. When the processor adjusts the size, the processor, if a utilization number of the receive buffer is greater than a high threshold: may determine a first new size for the receive buffer, and set a size of the receive buffer to the first new size. If the utilization number is less than a low threshold, the processor may determine a second new size for the receive buffer; and set the size of the receive buffer to the second new size.

Abstract: A method, a device, and a non-transitory storage medium are described in which a network performance optimization service is provided. A load balancer device may receive, from an end device, an application service request for an application service that is available from multiple server devices of an application layer network. The load balancer device may determine, from a source identifier associated with the end device and obtained from the application service request, that the source identifier does not map to a network traffic forwarding rule of a set of stored network traffic forwarding rules. In response, the load balancer device may map the source identifier to an application service profile of a set of stored application service profiles; select, based on the application service profile, a first server device of the multiple server devices and establish the first server device to be the destination of the application service request.

Abstract: A method, a device, and a non-transitory storage medium are described in which a network performance optimization service is provided. A load balancer device may receive, from an end device, an application service request for an application service that is available from multiple server devices of an application layer network. The load balancer device may determine, from a source identifier associated with the end device and obtained from the application service request, that the source identifier does not map to a network traffic forwarding rule of a set of stored network traffic forwarding rules. In response, the load balancer device may map the source identifier to an application service profile of a set of stored application service profiles; select, based on the application service profile, a first server device of the multiple server devices and establish the first server device to be the destination of the application service request.

Abstract: A system can receive an indication associated with establishing a transmission control protocol (TCP) connection. The system can determine, based on the indication, information that identifies a user device associated with the TCP connection. The system can determine, based on the information that identifies the user device, a predicted congestion level of a base station associated with the TCP connection. The system can select, based on the predicted congestion level, a congestion control algorithm to be implemented for the TCP connection. The system can cause the TCP connection to be established and implement the congestion control algorithm for the TCP connection.

Abstract: Techniques for reducing network congestion are disclosed. In one embodiment, a method is disclosed comprising receiving, by a computing device, a packet from a sender over a network; retrieving, by the computing device, congestion information; inserting, by the computing device, congestion data representing the congestion information into a header option of the packet to generate an augmented packet; transmitting, by the computing device, the augmented packet to a receiver; receiving, by the computing device, a response packet, the response packet including the congestion data; and transmitting, by the computing device, the response packet to the sender.

Abstract: Techniques for reducing network congestion are disclosed. In one embodiment, a method is disclosed comprising receiving, by a computing device, a packet from a sender over a network; retrieving, by the computing device, congestion information; inserting, by the computing device, congestion data representing the congestion information into a header option of the packet to generate an augmented packet; transmitting, by the computing device, the augmented packet to a receiver; receiving, by the computing device, a response packet, the response packet including the congestion data; and transmitting, by the computing device, the response packet to the sender.

Abstract: Systems and methods for pacing data transmission are described. An illustrative method includes transmitting, by a network device, a data stream at a pacing rate to a user equipment (UE) device. The method further includes accessing a metric of a radio access network (RAN) to which the UE device is connected, the metric associated with the UE device. The method further includes adjusting, based on the metric, the pacing rate at which the data stream is transmitted to the UE device.

Abstract: Systems and methods for pacing data transmission are described. An illustrative method includes transmitting, by a network device, a data stream at a pacing rate to a user equipment (UE) device. The method further includes accessing a metric of a radio access network (RAN) to which the UE device is connected, the metric associated with the UE device. The method further includes adjusting, based on the metric, the pacing rate at which the data stream is transmitted to the UE device.

Abstract: A network device receives, from a congestion controller, traffic policy information associated with a data stream between a sender and a receiver, where the traffic policy information includes a maximum round trip delay time (RTT) and a maximum throughput rate (Rate). The network device obtains a receiver advertised window size (RWND) for the receiver for the data stream. The network device modifies the RWND based on the RTT and the Rate to produce a modified receiver window size (RWND?) and sends the RWND? to the sender for use in controlling congestion on the data stream between the sender and the receiver.

Abstract: Systems and methods for pacing data transmission are described. An illustrative method includes transmitting, by a network device, a data stream at a pacing rate to a user equipment (UE) device. The method further includes accessing a metric of a radio access network (RAN) to which the UE device is connected, the metric associated with the UE device. The method further includes adjusting, based on the metric, the pacing rate at which the data stream is transmitted to the UE device.

Abstract: A network device receives, from a congestion controller, traffic policy information associated with a data stream between a sender and a receiver, where the traffic policy information includes a maximum round trip delay time (RTT) and a maximum throughput rate (Rate). The network device obtains a receiver advertised window size (RWND) for the receiver for the data stream. The network device modifies the RWND based on the RTT and the Rate to produce a modified receiver window size (RWND?) and sends the RWND? to the sender for use in controlling congestion on the data stream between the sender and the receiver.

Abstract: A network device includes a network interface for establishing a communication session with another network device, a memory to store instructions, and a processor to execute the instructions. The processor may, for each time period during the communication session, adjust a size of a receive buffer of a socket. When the processor adjusts the size, the processor, if a utilization number of the receive buffer is greater than a high threshold: may determine a first new size for the receive buffer, and set a size of the receive buffer to the first new size. If the utilization number is less than a low threshold, the processor may determine a second new size for the receive buffer; and set the size of the receive buffer to the second new size.

Abstract: Network devices may receive a Transport Control Protocol (TCP) segment from a user device. The TCP segment includes a TCP header and a payload, and the payload includes either a Hypertext Transfer Protocol (HTTP) plaintext message or a Secure HTTP (HTTPS) encrypted message. The network devices may extract a TCP Synchronization (SYN) signature from the TCP header and determine whether the payload of the TCP segment includes a HTTP plaintext message or a HTTPS encrypted message. When the payload includes a HTTP plaintext message, the network devices may extract contents of a HTTP User-Agent field from the HTTP plaintext message, determine a device type identifier (ID) and a category ID based on the extracted contents, and update a plurality of device signatures based on the TCP signature, the device type ID, and the category ID.

Abstract: A network device includes a network interface for establishing a communication session with another network device, a memory to store instructions, and a processor to execute the instructions. The processor may, for each time period during the communication session, adjust a size of a receive buffer of a socket. When the processor adjusts the size, the processor, if a utilization number of the receive buffer is greater than a high threshold: may determine a first new size for the receive buffer, and set a size of the receive buffer to the first new size. If the utilization number is less than a low threshold, the processor may determine a second new size for the receive buffer; and set the size of the receive buffer to the second new size.

Abstract: A system described herein may provide a technique for selecting and configuring a capture component and a filtering and analysis component for traffic capture in a manner that suitably accounts for Service Level Agreements (“SLAs”) of traffic to be captured. A traffic capture request may indicate one or more SLAs and/or other attributes, and an orchestration system may identify a network function (such as a User Plane Function (“UPF”) of a wireless network) that handles traffic that includes the requested traffic and instantiate the capture component at a node that implements the network function. The orchestration system may select a node, from a cluster of nodes, that is able to filter and analyze the traffic in an expedient manner in accordance with SLA(s) associated with the requested traffic, and install the filtering and analysis component at the selected node.

Abstract: A device establishes a wireless link with a user device via a network and selects a time period for a slow start state of the wireless link. The device enters the slow start state after selecting the time period and repeatedly provides a quantity of packets over consecutive time periods to the user device. The device determines a delivery rate for each time period, of the consecutive time periods, based on the quantity of packets provided each time period and determines a maximum delivery rate for the delivery rates of the consecutive time periods. The device determines that the wireless link is at a maximum capacity when a current delivery rate satisfies a threshold rate, based on the maximum delivery rate, after a threshold time period of the consecutive time periods and exits the slow start state based on the wireless link being at the maximum capacity.