A queue management method, system, and recording medium include Selective Acknowledgments (SACK) examining to examine SACK blocks of the forwarder to selectively drop packets in the forward flow queue based on a reverse flow queue and MultiPath Transmission Control Protocol (MPTCP) examining configured to examine multipath headers to recognize MPTCP flows and examine the reverse flow queue to determine if redundant data has been sent such that the dropping drops the redundant data.

The present invention discloses methods and systems for transmitting and receiving packets through a plurality of logical connections based on priority levels. When an encapsulating packets is received from a second network device via a logical network connection, priority level of a packet encapsulated in the encapsulating packet is determined, and the encapsulating packet is stored in a queue or transmitted to a host based on GSEQ, PSEQ, TSEQ, and the priority level. When a packet is received from a host via a LAN connection, the packet is retrieved from a priority queue based on the priority level a first logical network connection is selected for transmitting the packet. The packet is encapsulated in an encapsulating packet, and the payload of the encapsulating packet comprises the packet, GSEQ, TSEQ, PSEQ, and priority level of the packet. The encapsulating packet is then sent through the first logical network connection.

Apparatuses, methods, and systems are disclosed for rules handling. One apparatus includes a processor that determines whether a remote unit will apply network traffic steering data for routing data traffic on a first route across a first access network and a second route across a second access network. In some embodiments, the first and second routes may be different. In various embodiments, the apparatus includes a transmitter that transmits information that indicates whether the remote unit will apply the network traffic steering data.

Packet-switching operations in a network device are managed based on the detection of excessive-rate traffic flows. A network device receives a data unit, determines the traffic flow to which the data unit belongs, and updates flow tracking information for that flow. The network device utilizes the tracking information to determine when a rate at which the network device is receiving data belonging to the flow exceeds an excessive-rate threshold and is thus an excessive-rate flow. The network device may enable one or more excessive-rate policies on an excessive-rate traffic flow. Such a policy may include any number of features that affect how the device handles data units belonging to the flow, such as excessive-rate notification, differentiated discard, differentiated congestion notification, and reprioritization. Memory and other resource optimizations for such flow tracking and management are also described.

A method for controlling congestion in a datacenter network or server is described. The server includes a processor configured to host a plurality of virtual machines and an ingress engine configured to maintain a plurality of per-virtual machine queues configured to store received packets. The processor is also configured to execute a CPU-fair fair queuing process to control the processing of the packets by the processor. The processor is also configured to selectively trigger temporary packet per second packet transmission limits on top of a substantially continuously enforced bit per second transmission limit upon detection of a per virtual machine queue overload.

An in-vehicle network system includes first device and second device configured to send or receive to or from each other, and an intermediate node connected between the first device and the second device, the intermediate node being configured to output buffered messages in a sequence determined by a relative priority scheme. The first device includes a control unit configured to measure a communication delay for each of a plurality of different priority messages, set a delay representative value less than a maximum value of the plurality of communication delays, and adjust time that a time management unit manages, based on time that the first device manages, time that the second device manages, and the delay representative value.

Various example embodiments for supporting intent-based networking within a communication network are presented herein. Various example embodiments for supporting intent-based networking within a communication network may be configured to support a management system configured to support management of a network based on use of change management for management of the network. Various example embodiments for supporting intent-based networking within a communication network may be configured to support a management system configured to support management of a network based on use of change management for management of the network where the change management is based on validation of changes in the network before the changes are permanently effected in the network (e.g., based on application of the changes in the network for validation of the changes, based on application of the changes in a network that mirrors the real network before applying the changes to the real network, or the like).

Systems and methods in a node in an Ethernet network include, responsive to enabling burst monitoring between the node and a peer node in the Ethernet network, obtaining rate and burst size information from the peer node; configuring a counter at a traffic disaggregation point based on the rate and the burst size information, wherein the counter is based on a dual token bucket that is used to count out-of-profile frames in excess of a Committed Information Rate (CIR); and detecting a burst based on the out-of-profile frames during a monitored time interval.

Packet-switching operations in a network device are managed based on the detection of excessive-rate traffic flows. A network device receives a data unit, determines the traffic flow to which the data unit belongs, and updates flow tracking information for that flow. The network device utilizes the tracking information to determine when a rate at which the network device is receiving data belonging to the flow exceeds an excessive-rate threshold and is thus an excessive-rate flow. The network device may enable one or more excessive-rate policies on an excessive-rate traffic flow. Such a policy may include any number of features that affect how the device handles data units belonging to the flow, such as excessive-rate notification, differentiated discard, differentiated congestion notification, and reprioritization. Memory and other resource optimizations for such flow tracking and management are also described.

Packet-switching operations in a network device are managed based on the detection of excessive-rate traffic flows. A network device receives a data unit, determines the traffic flow to which the data unit belongs, and updates flow tracking information for that flow. The network device utilizes the tracking information to determine when a rate at which the network device is receiving data belonging to the flow exceeds an excessive-rate threshold and is thus an excessive-rate flow. The network device may enable one or more excessive-rate policies on an excessive-rate traffic flow. Such a policy may include any number of features that affect how the device handles data units belonging to the flow, such as excessive-rate notification, differentiated discard, differentiated congestion notification, and reprioritization. Memory and other resource optimizations for such flow tracking and management are also described.