Methods and devices in an IP network for congestion control

US9654399B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9654399-B2
Application numberUS-201114368423-A
CountryUS
Kind codeB2
Filing dateDec 28, 2011
Priority dateDec 28, 2011
Publication dateMay 16, 2017
Grant dateMay 16, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

The invention relates to a method 30 in a packet forwarding device 2 in an Internet Protocol, IP, network 10 for congestion control. The method 30 comprises: receiving 31 an IP packet 20 originating from a first network node 11 and addressed to a second network node 3 ; determining 32 a congestion status on a network path from the second network node 13 to the first network node 11 ; and entering 33 , for a congestion status indicating congestion, congestion information into a header 21, 22 of the IP packet 20 , the congestion status congestion information notifying the second network node 13 about congestion present on the network path. The invention also relates to a packet forwarding device 12 , a computer program 43 and computer program product 44.

First claim

Opening claim text (preview).

The invention claimed is: 1. A method in a packet forwarding device in an Internet Protocol, IP, network for congestion control, the method comprising: receiving an IP packet conveying a Transport Control Protocol, TCP, payload originating from a first network node and targeting a second network node, said first and second network nodes operating as TCP endpoints with respect to the TCP payload, and said IP packet going on a forward network path from the first network node to the second network node; performing a reverse path look up to determine a congestion status on a reverse network path from the second network node back to the first network node; entering, for a congestion status indicating congestion on the reverse network path, congestion information into the IP packet, to provide an indication to the second network node of congestion on the reverse network path; and forwarding the IP packet with the entered congestion information towards the second network node. 2. The method as claimed in claim 1 , wherein the determining of congestion status comprises determining at least one of the number of IP packets in an inbound directed queue from the second network node and the number of IP packets in an outbound directed queue to the first network node, wherein the congestion status indicates congestion if the number of IP packets exceeds a threshold number. 3. The method as claimed in claim 1 , wherein the determining of congestion status comprises determining at least one of a queuing delay of an inbound directed queue from the second network node and a queuing delay of an outbound directed queue to the first network node, wherein the congestion status indicates congestion if the queuing delay exceeds a threshold value. 4. The method as claimed in claim 1 , wherein the determining of congestion status comprises determining a congestion status of a network node located along the network path, the network node relaying IP packets between the packet forwarding device and the first or the second network node. 5. The method as claimed in claim 1 , wherein the entering of congestion information comprises setting an Explicit Congestion Control Echo, ECE, bit in a Transmission Control Protocol, TCP, header of the IP packet or in an IP packet header. 6. The method as claimed in claim 1 , wherein the congestion status indicates a congestion in the packet forwarding device or in a third network node located along the network path from the second network node to the forwarding device, the third network node relaying IP packets between the packet forwarding device and the second network node, or in a fourth network node located along the network path from the first network node to the forwarding device, the fourth network node relaying IP packets between the first network node and the forwarding device. 7. A packet forwarding device for relaying Internet Protocol, IP, packets between a first network node and a second network node of an IP network, the packet forwarding device comprising a processing unit and input device, the processing unit being configured to: receive an IP packet conveying a Transport Control Protocol, TCP, payload originating from a first network node and targeting a second network node, said first and second network nodes operating as TCP endpoints with respect to the TCP payload, and said IP packet going on a forward network path from the first network node to the second network node; perform a reverse path look up to determine a congestion status on a reverse network path from the second network node back to the first network node; enter, for a congestion status indicating congestion on the reverse network path, congestion information into the IP packet, to provide an indication to the second network node of congestion on the reverse network path; and forward the IP packet with the entered congestion information towards the second network node. 8. The packet forwarding device as claimed in claim 7 , wherein the processing unit is configured to determine the congestion status by determining at least one of the number of IP packets in an inbound directed queue from the second network node and the number of IP packets in an outbound directed queue to the first network node, and wherein the congestion status indicates congestion if the number of IP packets exceeds a threshold number. 9. The packet forwarding device as claimed in claim 7 , wherein the processing unit is configured to determine the congestion status by determining at least one of a queuing delay of an inbound directed queue from the second network node and a queuing delay of an outbound directed queue to the first network node, and wherein the congestion status indicates congestion if the queuing delay exceeds a threshold value. 10. The packet forwarding device as claimed in claim 7 , wherein the processing unit is configured to determine the congestion status by determining a congestion status of a network node located along the network path, the network node relaying IP packets between the packet forwarding device and the first or the second network node. 11. The packet forwarding device as claimed in claim 7 , wherein the processing unit is configured to enter the congestion information by setting an Explicit Congestion Control Echo, ECE, bit in a Transmission Control Protocol, TCP, header of the IP packet or in an IP packet header. 12. The packet forwarding device as claimed in claim 7 , wherein the congestion status indicates a congestion in the packet forwarding device or in a third network node located along the network path from the second network node to the forwarding device, the third network node relaying IP packets between the packet forwarding device and the second network node, or in a fourth network node located along the network path from the first network node to the forwarding device, the fourth network node relaying IP packets between the first network node and the forwarding device. 13. The method of claim 1 , wherein entering the congestion information comprises entering the congestion information in an IP header of the IP packet. 14. The method of claim 1 , wherein entering the congestion information comprises entering the congestion information in a TCP header of the TCP payload conveyed in the IP packet. 15. The method of claim 1 , wherein performing the reverse path look up comprises performing a reverse path look that includes at least that portion of the reverse path between the first network node and the forwarding device. 16. The packet forwarding device of claim 7 , wherein the processing unit is configured to enter the congestion information in an IP header of the IP packet. 17. The packet forwarding device of claim 7 , wherein the processing unit is configured to enter the congestion information in a TCP header of the TCP payload conveyed in the IP packet. 18. The packet forwarding device of claim 7 , wherein the processing unit is configured to perform the reverse path look up to include at least that portion of the reverse path between the first network node and the forwarding device.

Assignees

Inventors

Classifications

  • H04L47/12Primary

    Avoiding congestion; Recovering from congestion · CPC title

  • using forward notification · CPC title

  • In-band adaptation of TCP data exchange; In-band control procedures · CPC title

  • Interaction among intermediate nodes, e.g. hop by hop · CPC title

  • by tagging of packets, e.g. using discard eligibility [DE] bits · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9654399B2 cover?
The invention relates to a method 30 in a packet forwarding device 2 in an Internet Protocol, IP, network 10 for congestion control. The method 30 comprises: receiving 31 an IP packet 20 originating from a first network node 11 and addressed to a second network node 3 ; determining 32 a congestion status on a network path from the second network node 13 to the first network n…
Who is the assignee on this patent?
Liu Junhui, ERICSSON TELEFON AB L M (publ)
What technology area does this patent fall under?
Primary CPC classification H04L47/12. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue May 16 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).