Congestion control using congestion prefix information in a named data networking environment

Abstract

An example method for congestion control using congestion prefix information in a Named Data Networking (NDN) environment is provided and includes sensing, at a first node, congestion preventing an interest packet from being forwarded over a link to a second node, generating a prefix marker associated with a class of traffic to which the interest packet belongs, generating a negative acknowledgement (NACK) packet that includes the prefix marker, the NACK packet being indicative of congestion for any interest packet in the class of traffic indicated by the prefix marker over any path that includes the link, and transmitting the NACK packet over the NDN environment towards a sender of the interest packet.

What is claimed is: 
     
       1. A method, comprising:
 sensing, at a first node in a Named Data Networking (NDN) environment, congestion preventing an interest packet from being forwarded over a link to a second node; 
 generating a prefix marker associated with a class of traffic to which the interest packet belongs; 
 generating a negative acknowledgement (NACK) packet comprising the prefix marker, wherein the NACK packet indicates congestion for any interest packet in the class of traffic indicated by the prefix marker over any path that includes the link; and 
 transmitting the NACK packet over intermediate nodes in the NDN environment towards a sender of the interest packet, wherein the intermediate nodes re-route any interest packet in the class of traffic indicated by the prefix marker over at least one non-congested path subsequent to receiving the NACK packet. 
 
     
     
       2. The method of  claim 1 , wherein the prefix marker includes a forwarding information base (FIB) prefix at the first node that caused the interest packet to be attempted to be forwarded to the second node, wherein each interest packet includes at least a portion of the FIB prefix in a content name, wherein the FIB prefix is indicative of the class of traffic. 
     
     
       3. The method of  claim 1 , wherein each intermediate node retards any interest packet in the class of traffic indicated by the prefix marker subsequent to receiving the NACK packet. 
     
     
       4. The method of  claim 1 , wherein each intermediate node maintains a congestion marker (CM) table at an interface on which the NACK packet was received, wherein the CM table comprises an association between the prefix marker and a CM, wherein the CM represents a congestion level associated with the prefix marker at the interface. 
     
     
       5. The method of  claim 4 , wherein the CM decays over time. 
     
     
       6. The method of  claim 4 , wherein an output interest queue at each intermediate node executes a queuing logic to slow down any interest packet in the class of traffic indicated by the prefix marker, wherein the queuing logic increases weights of interest packets having names matching prefix markers in the CM table, wherein the respective weights are proportionally increased with the CMs. 
     
     
       7. The method of  claim 6 , wherein the queuing logic comprises at least one of weighted random early detection and weighted fair queuing. 
     
     
       8. The method of  claim 4 , wherein each interest packet includes a hash marker based on a corresponding FIB entry, wherein the hash marker represents congestion. 
     
     
       9. Non-transitory tangible media that includes instructions for execution, which when executed by a processor, is operable to perform operations comprising:
 sensing, at a first node in a NDN environment, congestion preventing an interest packet from being forwarded over a link to a second node; 
 generating a prefix marker associated with a class of traffic to which the interest packet belongs; 
 generating a NACK packet comprising the prefix marker, wherein the NACK packet indicates congestion for any interest packet in the class of traffic indicated by the prefix marker over any path that includes the link; and 
 transmitting the NACK packet over intermediate nodes in the NDN environment towards a sender of the interest packet, wherein the intermediate nodes re-route any interest packet in the class of traffic indicated by the prefix marker over at least one non-congested path subsequent to receiving the NACK packet. 
 
     
     
       10. The media of  claim 9 , wherein the prefix marker includes a FIB prefix at the first node that caused the interest packet to be attempted to be forwarded to the second node, wherein each interest packet includes at least a portion of the FIB prefix in a content name, wherein the FIB prefix is indicative of the class of traffic. 
     
     
       11. The media of  claim 9 , wherein each intermediate node maintains a CM table at an interface on which the NACK packet was received, wherein the CM table comprises an association between the prefix marker and a CM, wherein the CM represents a congestion level associated with the prefix marker at the interface. 
     
     
       12. The media of  claim 11 , wherein an output interest queue at each intermediate node executes a queuing logic to slow down any interest packet in the class of traffic indicated by the prefix marker, wherein the queuing logic increases weights of interest packets having names matching prefix markers in the CM table, wherein the respective weights are proportionally increased with the CMs. 
     
     
       13. A first node, comprising:
 a memory element for storing data; and 
 a processor, wherein the processor executes instructions associated with the data, wherein the processor and the memory element cooperate, such that the first node is configured for:
 sensing, at the first node in a NDN environment, congestion preventing an interest packet from being forwarded over a link to a second node; 
 generating a prefix marker associated with a class of traffic to which the interest packet belongs; 
 generating a NACK packet comprising the prefix marker, wherein the NACK packet indicates congestion for any interest packet in the class of traffic indicated by the prefix marker over any path that includes the link; and 
 transmitting the NACK packet over intermediate nodes in the NDN environment towards a sender of the interest packet, wherein the intermediate nodes re-route any interest packet in the class of traffic indicated by the prefix marker over at least one non-congested path subsequent to receiving the NACK packet. 
 
 
     
     
       14. The first node of  claim 13 , wherein the prefix marker includes a FIB prefix at the first node that caused the interest packet to be attempted to be forwarded to the second node, wherein each interest packet includes at least a portion of the FIB prefix in a content name, wherein the FIB prefix is indicative of the class of traffic. 
     
     
       15. The first node of  claim 13 , wherein each intermediate node maintains a CM table at an interface on which the NACK packet was received, wherein the CM table comprises an association between the prefix marker and a CM, wherein the CM represents a congestion level associated with the prefix marker at the interface. 
     
     
       16. The first node of  claim 15 , wherein an output interest queue at each intermediate node executes a queuing logic to slow down any interest packet in the class of traffic indicated by the prefix marker, wherein the queuing logic increases weights of interest packets having names matching prefix markers in the CM table, wherein the respective weights are proportionally increased with the CMs.