IP Library › Granted Patent US 12,750,320
Granted Patent B2
US 12,750,320 · App. 18/814,987 · Granted Sep 29, 2026

Method and system for a network congestion service

Inventors: Lap Tse (Marietta, GA); Mark T. Watts (Newport, RI)
Assignee: Verizon Patent and Licensing Inc.
H04L47/323H04L45/22H04L47/122
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,750,320
App. No.
18/814,987
Granted
Sep 29, 2026
Kind
B2
Abstract

A method, a network device, and a non-transitory computer-readable storage medium are described in relation to an network congestion service. The service includes adding bits to a packet that indicate a priority for dropping the packet when there is congestion. The service may add the bits to an Internet Protocol header of the packet. The service may also include re-routing the packet based on the drop packet priority value indicated by the added bits. The service may select an alternate communication path during congestion based on the value of the added bits. The service may also include adding a token to a packet that validates the added bits and their value.

Claims (45)

1 . A method comprising:

determining, by a network device of a network, that a first communication path to another network device is congested;

determining, by the network device, a drop packet priority value, which indicates a priority level from among multiple priority levels for which packets are not to be dropped during congestion, for a packet;

generating, by the network device, the packet that includes the drop packet priority value;

selecting, by the network device based on the drop packet priority value, a second communication path to the other network device; and

transmitting, by the network device via the second communication path, the packet to the other network device.

2 . The method of claim 1 , wherein the drop packet priority value is included in an Options field or an Extension header field.

3 . The method of claim 1 , wherein the determining comprises:

determining, by the network device, a type of control plane message to which the packet pertains.

4 . The method of claim 1 , wherein the determining comprises:

determining, by the network device, a category of application to which the packet of a control plane message pertains.

5 . The method of claim 1 , wherein the selecting comprises:

correlating, by the network device, the drop packet priority value to one or multiple candidate communication paths to the other network device.

6 . The method of claim 1 , wherein the selecting comprises:

selecting, by the network device, the second communication path based on the drop packet priority value and a correlated congestive state of the second communication path.

7 . The method of claim 1 , wherein the packet further includes a security token that validates the drop packet priority value.

8 . The method of claim 1 , wherein the packet is a control plane message, and the drop packet priority value is included in a Type of Service (ToS) field of an Internet Protocol (IP) version 4 header or a Traffic Class (TC) field of an IP version 6 header.

9 . A network device comprising:

a processor, wherein the processor is configured to:

determine that a first communication path to another network device is congested;

determine a drop packet priority value, which indicates a priority level from among multiple priority levels for which packets are not to be dropped during congestion, for a packet;

generate the packet that includes the drop packet priority value;

select, based on the drop packet priority value, a second communication path to the other network device; and

transmit, via the second communication path, the packet to the other network device.

10 . The network device of claim 9 , wherein the drop packet priority value is included in an Options field or an Extension header field.

11 . The network device of claim 9 , wherein, when determining, the processor is further configured to:

determine a type of control plane message to which the packet pertains.

12 . The network device of claim 9 , wherein, when determining, the processor is further configured to:

determine a category of application to which the packet of a control plane message pertains.

13 . The network device of claim 9 , wherein, when selecting, the processor is further configured to:

correlate the drop packet priority value to one or multiple candidate communication paths to the other network device.

14 . The network device of claim 9 , wherein, when selecting, the processor is further configured to:

select the second communication path based on the drop packet priority value and a correlated congestive state of the second communication path.

15 . The network device of claim 9 , wherein the packet further includes a security token that validates the drop packet priority value.

16 . The network device of claim 9 , wherein the packet is a control plane message, and the drop packet priority value is included in a Type of Service (ToS) field of an Internet Protocol (IP) version 4 header or a Traffic Class (TC) field of an IP version 6 header.

17 . A non-transitory computer-readable storage medium storing instructions executable by a processor of a network device that configures the network device to:

determine that a first communication path to another network device is congested;

determine a drop packet priority value, which indicates a priority level from among multiple priority levels for which packets are not to be dropped during congestion, for a packet;

generate the packet that includes the drop packet priority value;

select, based on the drop packet priority value, a second communication path to the other network device; and

transmit, via the second communication path, the packet to the other network device.

18 . The non-transitory computer-readable storage medium of claim 17 , wherein the drop packet priority value is included in an Options field or an Extension header field.

19 . The non-transitory computer-readable storage medium of claim 17 , wherein the network device is further configured to:

determine a category of application to which the packet of a control plane message pertains.

20 . The non-transitory computer-readable storage medium of claim 17 , wherein the packet is a control plane message, and the drop packet priority value is included in a Type of Service (ToS) field of an Internet Protocol (IP) version 4 header or a Traffic Class (TC) field of an IP version 6 header.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 26, 2024
From: TSE, LAP; WATTS, MARK T.
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 068397/0653 →
Continuity (1)
Related Publication 20260058914A1 · Feb 26, 2026
References Cited (58)
US 6904015B1 · Chen · 2005 [cited by examiner]
US 7046665B1 · Walrand · 2006 [cited by examiner]
US 7133362B2 · Chu · 2006 [cited by examiner]
US 7706353B2 · Roy · 2010 [cited by examiner]
US 10069748B2 · Shpiner · 2018 [cited by examiner]
US 10932306B2 · Zee · 2021 [cited by examiner]
US 11290395B1 · Goldman · 2022 [cited by examiner]
US 11528227B1 · Seely · 2022 [cited by examiner]
US 11558298B2 · Leib · 2023 [cited by examiner]
US 11855901B1 · Kwan · 2023 [cited by examiner]
US 20030088690A1 · Zuckerman · 2003 [cited by examiner]
US 20030123447A1 · Smith · 2003 [cited by examiner]
US 20050157641A1 · Roy · 2005 [cited by examiner]
US 20070008884A1 · Tang · 2007 [cited by examiner]
US 20090135729A1 · Saffre · 2009 [cited by examiner]
US 20140301195A1 · Briscoe · 2014 [cited by examiner]
US 20160021017A1 · Thubert · 2016 [cited by examiner]
US 20170048144A1 · Liu · 2017 [cited by examiner]
US 20170171099A1 · Shpiner · 2017 [cited by examiner]
US 20170214623A1 · Finkelstein · 2017 [cited by examiner]
US 20180097853A1 · Wiley · 2018 [cited by examiner]
US 20190089644A1 · Shpiner · 2019 [cited by examiner]
US 20190208555A1 · Zee · 2019 [cited by examiner]
US 20190253351A1 · Ihlar · 2019 [cited by examiner]
US 20200145331A1 · Bhandari · 2020 [cited by examiner]
US 20200328981A1 · Ghanwani · 2020 [cited by examiner]
US 20210112436A1 · Hoffner · 2021 [cited by examiner]
US 20210168075A1 · Leib · 2021 [cited by examiner]
US 20210400537A1 · Zhang · 2021 [cited by examiner]
US 20210409335A1 · Zhu · 2021 [cited by examiner]
US 20220038374A1 · Koral · 2022 [cited by examiner]
US 20220124043A1 · Zhu · 2022 [cited by examiner]
US 20220141148A1 · Patil · 2022 [cited by examiner]
US 20220210075A1 · Musleh · 2022 [cited by examiner]
US 20230079715A1 · Seely · 2023 [cited by examiner]
US 20230188447A1 · Alleyne · 2023 [cited by examiner]
US 20230198896A1 · Zhou · 2023 [cited by examiner]
US 20230344772A1 · Johansson · 2023 [cited by examiner]
US 20240039852A1 · Matthews · 2024 [cited by examiner]
US 20240056885A1 · Zhu · 2024 [cited by examiner]
US 20240129260A1 · Farrokhbakht · 2024 [cited by examiner]
US 20240146655A1 · Jaiswal · 2024 [cited by examiner]
US 20240205738A1 · Shilov · 2024 [cited by examiner]
US 20240224114A1 · Watts · 2024 [cited by examiner]
US 20240267792A1 · Zhu · 2024 [cited by examiner]
US 20240414089A1 · Nainar · 2024 [cited by examiner]
US 20240414582A1 · Taneja · 2024 [cited by examiner]
US 20250106680A1 · Patil · 2025 [cited by examiner]
US 20250133023A1 · Östberg · 2025 [cited by examiner]
US 20250150402A1 · Östberg · 2025 [cited by examiner]
US 20250220494A1 · He · 2025 [cited by examiner]
US 20250227548A1 · Talebi Fard · 2025 [cited by examiner]
US 20250240250A1 · Taft · 2025 [cited by examiner]
US 20250274806A1 · Talebi · 2025 [cited by examiner]
US 20250274810A1 · Talebi · 2025 [cited by examiner]
US 20250358671A1 · Kanamarlapudi · 2025 [cited by examiner]
US 20250358673A1 · Goel · 2025 [cited by examiner]
WO WO2024165147A1 · 2024 [cited by examiner]