IP Library Granted Patent US 12,206,591
Granted Patent B2
US 12,206,591 · App. 18/313,873 · Granted Jan 21, 2025

Managing data traffic congestion in network nodes

Inventors: Olivier Tilmans (Rixensart, BE); Koen De Schepper (Boortmeerbeek, BE)
Assignee: Nokia Solutions and Networks Oy
H04L47/28H04L47/12H04L47/56
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,206,591
App. No.
18/313,873
Granted
Jan 21, 2025
Kind
B2
Abstract

Example embodiments describe a method for managing data traffic congestion in a network communication node. The method comprising maintaining a marking probability based on a marking ratio indicative of a change in packets responsible for congestion in a network queue in the network communication node over a change in a total number of packets processed by the network queue. The method further comprising classifying packets processed by the network queue as scalable packets or other packets based on an identifier included in the packets; wherein the scalable packets support scalable congestion control. The method further comprising marking the scalable packets responsible for congestion in the network queue with a congestion mark to signal data traffic congestion; and marking the other packets that support unscalable congestion control with the congestion mark based on the marking probability.

Claims (30)

1. A method of managing data traffic congestion in a network communication node;

the method comprising:

maintaining a marking probability based on a marking ratio indicative of a change in a number of packets processed by a network queue and responsible for congestion in the network queue in the network communication node over a change in a total number of the packets processed by the network queue, wherein those of the packets responsible for congestion are causing a congestion parameter to exceed a threshold;

classifying packets processed by the network queue as scalable ones of the packets or other of the packets based on an identifier included in the packets, the scalable ones of the packets supporting scalable congestion control;

marking the scalable ones of the packets responsible for congestion in the network queue with a congestion mark to signal data traffic congestion; and

marking the other of the packets that support unscalable congestion control with the congestion mark based on the marking probability.

2. A method according to claim 1 , wherein the maintaining further comprises identifying those of the packets as responsible for congestion in the network queue before enqueuing the packets in the network queue.

3. A method according to claim 1 , wherein the maintaining further comprises identifying those of the packets as responsible for congestion in the network queue upon dequeuing the packets from the network queue.

4. A method according to claim 1 , wherein those of the packets are identified as responsible for congestion in the network queue in response to a size of the network queue exceeding a size threshold.

5. A method according to claim 1 , wherein those of the packets are identified as responsible for congestion in the network queue in response to a sojourn time of the packets in the network queue exceeding a time threshold.

6. A method according to claim 1 , further comprising:

before enqueuing the packets in the network queue, flagging the scalable ones of the packets for marking and flagging the other of the packets for marking based on the marking probability; and

upon dequeuing, performing the marking with the congestion mark for those of the packets that are flagged for marking and are identified as responsible for congestion in the network queue.

7. A method according to claim 1 , further comprising dropping a number of the packets in response to a size of the network queue exceeding a first drop threshold, or in response to a sojourn time of the packets in the network queue exceeding a second drop threshold.

8. A method according to claim 1 , further comprising dropping the other of the packets that are eligible for marking based on the marking probability and that do not support unscalable congestion control.

9. A method according to claim 1 , wherein the congestion mark and the identifier are included in an explicit congestion notification, ECN, field of an internet protocol, IP, header of the packets.

10. The method of claim 9 , wherein the marking further comprises overwriting the identifier included in the explicit congestion notification, ECN, field with the congestion mark.

11. A method according to claim 1 , wherein the maintaining of the marking probability comprises updating the marking probability and the marking ratio at a predetermined time interval, or at a predetermined change in the total number of packets processed by the network queue.

12. A method according to claim 1 , wherein the marking probability is based on a moving average of the marking ratio.

13. An apparatus, comprising:

a network communication node to manage data traffic congestion; and wherein the network communication node is configured to:

maintain a marking probability based on a marking ratio indicative of a change in a number of packets processed by a network queue and responsible for congestion in the network queue in the network communication node over a change in a total number of the packets processed by the network queue, wherein those of the packets responsible for congestion are causing a congestion parameter to exceed a threshold;

classify the packets processed by the network queue as scalable ones of the packets or other of the packets based on an identifier included in the packets, the scalable ones of the packets supporting scalable congestion control;

mark the scalable ones of the packets responsible for congestion in the network queue with a congestion mark to signal data traffic congestion; and

mark the other of the packets that support unscalable congestion control with the congestion mark based on the marking probability.

14. A non-transitory computer readable storage medium comprising computer-executable instructions for performing the following steps when the instructions are executed on a computer:

maintaining a marking probability based on a marking ratio indicative of a change in a number of packets processed by a network queue and responsible for congestion in the network queue in a network communication node over a change in a total number of the packets processed by the network queue, wherein those of the packets responsible for congestion are causing a congestion parameter to exceed a threshold;

classifying the packets processed by the network queue as scalable ones of the packets or other of the packets based on an identifier included in the packets, the scalable ones of the packets supporting scalable congestion control;

marking the scalable ones of the packets responsible for congestion in the network queue with a congestion mark to signal data traffic congestion; and

marking the other of the packets that support unscalable congestion control with the congestion mark based on the marking probability.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 26, 2023
From: TILMANS, OLIVIER; SCHEPPER, KOEN DE
To: NOKIA BELL NV
Reel/Frame 065950/0676 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 26, 2023
From: NOKIA BELL NV
To: NOKIA SOLUTIONS AND NETWORKS OY
Reel/Frame 065950/0679 →
Priority Claims (1)
EP 22172415 · May 9, 2022 · regional
Continuity (1)
Related Publication 20230362099A1 · Nov 9, 2023
References Cited (18)
US 20170019343A1 · De Schepper · 2017 [cited by examiner]
US 20200021532A1 · Borikar · 2020 [cited by examiner]
US 20220150171A1 · Matthews · 2022 [cited by examiner]
US 20220167206A1 · Tilmans · 2022 [cited by examiner]
EP 3340551A1 · 2018 [cited by applicant]
EP 4007225A1 · 2022 [cited by applicant]
WO 2017009715A1 · 2017 [cited by applicant]
De Schepper et al., “PI2: A Linearized AQM for both Classic and Scalable TCP”, Proceedings of the 12th International on Conference on emerging Networking Experiments and Technologies, Dec. 2016, pp. 105-119. [cited by applicant]
McKenney, “Stochastic Fairness Queuing”, Proceedings. IEEE INFOCOM '90: Ninth Annual Joint Conference of the IEEE Computer and Communications Societies@m_The Multiple Facets of Integration, Jun. 3-7, 1990, pp. 733-740. [cited by applicant]
Joergensen et al., “The Flow Queue CoDel Packet Scheduler and Active Queue Management Algorithm”, RFC 8290, Internet Engineering Task Force (IETF), Jan. 2018, pp. 1-25. [cited by applicant]
Briscoe, “Tunnelling of Explicit Congestion Notification”, RFC 6040, Internet Engineering Task Force (IETF), Nov. 2020, pp. 1-35. [cited by applicant]
Kent et al., “Security Architecture for the Internet Protocol”, RFC 4301, Network Working Group, Dec. 2005, pp. 1-101. [cited by applicant]
Briscoe, “Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim”, draft-ietf-tsvwg-rfc6040update-shim-16, Transport Area Working Group, Mar. 2023, 19 pages. [cited by applicant]
De Schepper et al., “Identifying Modified Explicit Congestion Notification (ECN) Semantics for Ultra-Low Queuing Delay”, draft-ietf-tsvwg-ecn-14s-id-01, Transport Services, Internet-Draft, Oct. 30, 2017, pp. 1-32. [cited by applicant]
Briscoe et al., “Low Latency, Low Loss, Scalable Throughput (L4S) Internet Service: Architecture”, draft-ietf-tsvwg-14s-arch-00, Transport Area Working Group, Internet-Draft, May 5, 2017, pp. 1-31. [cited by applicant]
De Schepper et al., “Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)”, RFC 9332, Internet Engineering Task Force (IETF), Jan. 2023, pp. 1-53. [cited by applicant]
Extended European Search Report received for corresponding European Patent Application No. 22172415.6, dated Sep. 2, 2022, 7 pages. [cited by applicant]
Notice of Allowance received for corresponding European Patent Application No. 22172415.6, dated Aug. 26, 2024, 7 pages. [cited by applicant]