Uplink data congestion detection for low-latency services in wireless communication networks
US-2024373448-A1 · Nov 7, 2024 · US
US9282041B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9282041-B2 |
| Application number | US-201313943136-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 16, 2013 |
| Priority date | Jul 16, 2013 |
| Publication date | Mar 8, 2016 |
| Grant date | Mar 8, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method may include transmitting data frames from a reaction point of a source device. The method may also include receiving, at the reaction point, congestion notification messages corresponding to the transmitted data frames and containing congestion feedback data regarding a particular network switching device and an identifier of the particular network switching device. The method may also include modifying a congestion profile for the particular network switching device by correlating the identifier of the particular network switching device to a profile entry, and updating the profile entry with the congestion feedback data.
Opening claim text (preview).
What is claimed is: 1. A computer implemented method for generating congestion profiles for network switching devices, comprising: transmitting data frames from a reaction point of a source device; receiving, at the reaction point, congestion notification messages corresponding to the transmitted data frames, each congestion notification message including congestion feedback data regarding a particular network switching device and an identifier of the particular network switching device; and modifying a congestion profile for the particular network switching device by: correlating the identifier of the particular network switching device to a profile entry in a congestion point data sub-table, updating the profile entry with the congestion feedback data and a timestamp in response to a determination that the profile entry in the congestion point data sub-table exists, and creating a new profile entry in the congestion point data sub-table, the new profile entry including the congestion feedback data and a timestamp, in response to a determination that the profile entry does not already exist in the congestion point data sub-table. 2. The method of claim 1 , further comprising adjusting a data transmission rate for transmitting data frames based on an analysis of the congestion profile. 3. The method of claim 1 , further comprising adjusting a data transmission route for transmitting data frames through a network based on an analysis of one or more congestion profiles stored in corresponding congestion point data sub-tables. 4. The method of claim 1 , further comprising creating a congestion point data table having one or more records therein, each record including a congestion point identifier and a bucket pointer that points to a congestion point data sub-table that is configured to store congestion point data for the device identified by the congestion point identifier. 5. The method of claim 4 , wherein each congestion point data sub-table comprises one or more profile entries for the device identified by the congestion point identifier, each profile entry including: a timestamp indicating when the profile entry was added to the congestion point data sub-table; an encapsulated priority value that indicates a data frame's congestion notification priority; a quantized feedback value; a Qoffset value; and a Qdelta value. 6. The method of claim 1 , wherein the particular network switching device is a network switch with a quantized congestion notification enabled queue, and wherein the identifier is a congestion point identifier having a 64 bit value. 7. The method of claim 1 , further comprising allocating resources of the particular network switching device based on an analysis of the congestion profile. 8. The method of claim 1 , wherein the congestion feedback data includes an encapsulated priority value, a quantized feedback value, a Qoffset value, or a Qdelta value. 9. A computer system including a processor and a memory encoded with instructions, wherein the instructions when executed on the processor perform the following operations: transmitting data frames from a reaction point of a source device; receiving, at the reaction point, congestion notification messages corresponding to the transmitted data frames, each congestion notification message including congestion feedback data regarding a particular network switching device and an identifier of the particular network switching device; and modifying a congestion profile for the particular network switching device by: correlating the identifier of the particular network switching device to a profile entry in a congestion point data sub-table, updating the profile entry with the congestion feedback data and a timestamp in response to a determination that the profile entry in the congestion point data sub-table exists, and creating a new profile entry in the congestion point data sub-table, the new profile entry including the congestion feedback data and a timestamp, in response to a determination that the profile entry does not already exist in the congestion point data sub-table. 10. The computer system of claim 9 , wherein the instructions when executed on the processor perform adjusting a data transmission rate for transmitting data frames based on an analysis of the congestion profile. 11. The computer system of claim 9 , wherein the instructions when executed on the processor perform adjusting a data transmission route for transmitting data frames through a network based on an analysis of one or more congestion profiles stored in corresponding congestion point data sub-tables. 12. The computer system of claim 9 , wherein the instructions when executed on the processor perform creating a congestion point data table having one or more records therein, each record including a congestion point identifier and a bucket pointer that points to a congestion point data sub-table that is configured to store congestion point data for the device identified by the congestion point identifier. 13. The computer system of claim 12 , wherein each congestion point data sub-table comprises one or more profile entries for the device identified by the congestion point identifier, each profile entry including: a timestamp indicating when the profile entry was added to the congestion point data sub-table; an encapsulated priority value that indicates a data frame's congestion notification priority; a quantized feedback value; a Qoffset value; and a Qdelta value. 14. The computer system of claim 9 , wherein the particular network switching device is a network switch with a quantized congestion notification enabled queue. 15. The computer system of claim 9 , wherein the identifier is a congestion point identifier having a 64 bit value. 16. The computer system of claim 9 , wherein the congestion feedback data includes an encapsulated priority value, a quantized feedback value, a Qoffset value, or a Qdelta value. 17. A computer implemented method for generating congestion profiles for network source devices that are configured to transmit data to a destination device, comprising: receiving, at a congestion point, data frames from a reaction point of a source device, wherein the data frames contain congestion feedback data regarding the source device and an identifier of the source device; and modifying a congestion profile for the source device by: correlating the identifier of the source device to a profile entry in a congestion point data sub-table, updating the profile entry with the congestion feedback data and a timestamp in response to a determination that the profile entry in the congestion point data sub-table exists, and creating a new profile entry in the congestion point data sub-table, the new profile entry including the congestion feedback data and a timestamp, in response to a determination that the profile entry does not already exist in the congestion point data sub-table. 18. The method of claim 17 , further comprising adjusting congestion point resources based on an analysis of one or more congestion profiles stored in corresponding congestion point data sub-tables. 19. The method of claim 17 , wherein the reaction point operates within data link layer (layer 2) of Open Systems Interconnection (OSI) model. 20. The method of claim 17 , wherein the source device is a network server. 21. The method of claim 17 , wherein the source device is a network switch with a quantized congestion notification enabled queue.
Identifying congestion · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.