# US 2024/0205151 A1 · Systems, Apparatuses and Methods for Network Packet Management > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2024/0205151 A1 - Document ID: US20240205151A1 - Status: Published application - Kind: A1 - Application number: 18/542,584 - Filed: 2023-12-15 - Published: 2024-06-20 - Earliest claimed: 2016-07-05 - Assignees: Six Impossible Things Before Breakfast Limited - Applicants: Six Impossible Things Before Breakfast Limited - Inventors: Sergey IGNATCHENKO - Web page: https://patentgrep.com/patent/US20240205151A1 ## CPC - H04L 1/00: Arrangements for detecting or preventing errors in the information received {(correcting synchronisation H04L7/00)} - H04L 43/0864: Round trip delays - H04L 43/087: Jitter - H04L 43/0894: Packet rate - H04L 45/24: Multipath - H04L 45/302: Route determination based on requested QoS - H04L 45/3065: {for real time traffic} - H04L 45/70: {Routing based on monitoring results} - H04L 45/741: Routing in networks with a plurality of addressing schemes, e.g. with both IPv4 and IPv6 - H04L 45/745: Address table lookup; Address filtering - H04L 47/2416: Real-time traffic - H04L 47/56: implementing delay-aware scheduling - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Methods and systems are provided for latency-oriented router. An incoming packet is received on a first interface. The type of the incoming packet is determined. Upon the detection that the incoming packet belongs to latency-critical traffic, the incoming packet is duplicated into one or more copies. Subsequently, the duplicated copies are sent to a second interface in a delayed fashion where the duplicated copies are spread over a time period. The duplicated copies are received and processed at the second interface. ## Claims ### Claim at position 1 1-160. (canceled) ### Claim 161 A method of managing latency critical network traffic, the method comprising: receiving, by a routing device via a first set of one or more interfaces, a plurality of packets from a first source device and a plurality of packets from a second source device; determining, by the routing device, that the plurality of packets from the first source device comprise latency-critical packets and that the plurality of packets from the second source device comprise non-critical packets; detecting, by the routing device, a potential issue with the received plurality of packets by determining one or more characteristic of the plurality of packets received through the first set of one or more interfaces, wherein detecting the potential issue with the received packets comprises measuring a round trip time of packets transmitted to and packets received from the first source device, wherein at least one packet of the plurality of packets received from the first source device further comprises a first field indicating a reference identifier and a second field indicating an amount of time from when a first packet with the reference identifier was received by the target device to when the at least one packet was sent by the target device to the routing device; suppressing, by the routing device, transmission of the non-critical packets received from the second source device based on the detection of the potential issue; transmitting, by the routing device, the latency-critical packets to a first client device via a second set of one or more interfaces; and transmitting, by the routing device, the non-critical packets to a second client device via the second set of one or more interfaces. ### Claim 162 (depends on 161) The method of claim 161, wherein the first source device and the second source device are the same device. ### Claim 163 (depends on 161) The method of claim 161, wherein the first client device and the second client device are the same device. ### Claim 164 (depends on 161) The method of claim 161, wherein the non-critical packets received from the second source device are associated with a logical connection, wherein the logical connection is selected from among the group comprising: a Transmission Control Protocol (TCP) connection, a BitTorrent User Datagram Protocol (UDP) Tracker connection, and a Quick UDP Internet Connection (QUIC). ### Claim 165 (depends on 164) The method of claim 164, wherein suppressing the transmission of the non-critical packets is performed on a per logical connection basis. ### Claim 166 (depends on 161) The method of claim 161, wherein detecting the potential issue with the received packets further comprises detecting a rate of loss of ping packets received from an external device. ### Claim 167 (depends on 166) The method of claim 166, wherein the ping packets are Internet Control Message Protocol (ICMP) packets. ### Claim 168 (depends on 166) The method of claim 166, wherein the external device and the first source device are the same device. ### Claim 169 (canceled) ### Claim 170 (canceled) ### Claim 171 (depends on 161) The method of claim 161, wherein detecting the potential issue with the received packets further comprises measuring jitter. ### Claim 172 (depends on 161) The method of claim 161, wherein detecting the potential issue with the received packets further comprises receiving from the first source device a packet indicating a connection quality between the first set of one or more interfaces and the first source device. ### Claim 173 (depends on 161) The method of claim 161, wherein detecting the potential issue with the received packets further comprises determining a number of packets lost in transit between the first source device and the first set of one or more interfaces. ### Claim 174 (depends on 173) The method of claim 173, wherein determining the number of packets lost in transit comprises comparing the number of packets received from the first source device to an expected packet rate. ### Claim 175 (depends on 161) The method of claim 161, wherein suppressing the transmission of the non-critical packets comprises dropping one or more of the non-critical packets received from the second source device. ### Claim 176 (depends on 175) The method of claim 175, wherein dropping the one or more of the non-critical packets comprises dropping up to a predefined a percentage of the non-critical packets. ### Claim 177 (depends on 161) The method of claim 161, wherein suppressing the transmission of the non-critical packets comprises delaying transmission of one or more of the non-critical packets received from the second source device. ### Claim 178 (depends on 161) The method of claim 161, further comprising transmitting, by the routing device, packets to the second source device, wherein suppressing the transmission of the non-critical packets comprises attaching an Explicit Congestion Notification to packets transmitted from the routing device to the second source device. ### Claim 179 A routing device comprising: a first set of one or more interfaces and a second set of one or more interfaces; and a processor configured to: receive a plurality of packets from a first source device via the first set of one or more interfaces and a plurality of packets from a second source device via the first set of one or more interfaces; determine that the plurality of packets from the first source device comprise latency-critical packets and that the plurality of packets from the second source device comprise non-critical packets; detect a potential issue with the received plurality of packets by determining one or more characteristics of the plurality of packets received through the first set of one or more interfaces, wherein to detect the potential issue with the received packets, the processor is further configured to measure a round trip time of packets transmitted to and packets received from the first source device, wherein at least one packet of the plurality of packets received from the first source device further comprises a first field indicating a reference identifier and a second field indicating an amount of time from when a first packet with the reference identifier was received by the target device to when the at least one packet was sent by the target device to the routing device; suppress transmission of the non-critical packets received from the second source device based on the detection of the potential issue; transmit the latency-critical packets to a first client device via the second set of one or more interfaces; and transmit the non-critical packets to a second client device via the second set of one or more interfaces. ### Claim 180 (depends on 179) The routing device of claim 179, wherein the first source device and the second source device are the same device. ### Claim 181 (depends on 179) The routing device of claim 179, wherein the first client device and the second client device are the same device. ### Claim 182 (depends on 179) The routing device of claim 179, wherein the non-critical packets received from the second source device are associated with a logical connection, wherein the logical connection is selected from among the group comprising: a Transmission Control Protocol (TCP) connection, a BitTorrent User Datagram Protocol (UDP) Tracker connection, and a Quick UDP Internet Connection (QUIC) ### Claim 183 (depends on 182) The routing device of claim 182, wherein the processor suppresses the transmission of the non-critical packets by the second source device on a per logical connection basis. ### Claim 184 (depends on 179) The routing device of claim 179, wherein to detect the potential issue with the received packets, the processor is further configured to detect a rate of loss of ping packets received from an external device. ### Claim 185 (depends on 184) The routing device of claim 184, wherein the ping packets are Internet Control Message Protocol (ICMP) packets. ### Claim 186 (depends on 184) The routing device of claim 184, wherein the external device and the first source device are the same device. ### Claim 187 (canceled) ### Claim 188 (canceled) ### Claim 189 (depends on 179) The routing device of claim 179, wherein to detect the potential issue with the received packets, the processor is further configured to measure jitter. ### Claim 190 (depends on 179) The routing device of claim 179, wherein to detect the potential issue with the received packets, the processor is further configured to receive from the first source device a packet indicating a connection quality between the first set of one or more interfaces and the first source device. ### Claim 191 (depends on 179) The routing device of claim 179, wherein to detect the potential issue with the received packets, the processor is further configured to determine a number of packets lost in transit between the first source device and the first set of one or more interfaces. ### Claim 192 (depends on 191) The routing device of claim 191, wherein to determine the number of packets lost in transit, the processor is configured to compare the number of packets received from the first source device to an expected packet rate. ### Claim 193 (depends on 179) The routing device of claim 179, wherein to suppress the transmission of the non-critical packets, the processor is configured to drop one or more of the non-critical packets received from the second source device. ### Claim 194 (depends on 193) The routing device of claim 193, wherein to drop the one or more of the non-critical packets, the processor is configured to drop a percentage of the non-critical packets. ### Claim 195 (depends on 179) The routing device of claim 179, wherein to suppress the transmission of the non-critical packets, the processor is configured to delay transmission of one or more of the non-critical packets received from the second source device. ### Claim 196 (depends on 179) The routing device of claim 179, wherein the processor is further configured to transmit packets to the second source device, wherein to suppress the transmission of the non-critical packets, the processor is configured to attach an Explicit Congestion Notification to packets transmitted from the routing device to the second source device. ### Claim at position 38 197-238. (canceled)