Closed-Loop Congestion Control for Mixed Responsive and Non-Responsive Traffic


Dateien zu dieser Ressource

Prüfsumme: MD5:34492549ea86d4f8e1286466ddc71137

PLETKA, Roman, Andreas KIND, Marcel WALDVOGEL, Soenke MANNAL, 2003. Closed-Loop Congestion Control for Mixed Responsive and Non-Responsive Traffic. GLOBECOM '03. IEEE Global Telecommunications Conference. San Francisco, CA, USA. In: GLOBECOM '03. IEEE Global Telecommunications Conference (IEEE Cat. No.03CH37489). IEEE, pp. 4180-4185. ISBN 0-7803-7974-8. Available under: doi: 10.1109/GLOCOM.2003.1259014

@inproceedings{Pletka2003Close-6329, title={Closed-Loop Congestion Control for Mixed Responsive and Non-Responsive Traffic}, year={2003}, doi={10.1109/GLOCOM.2003.1259014}, isbn={0-7803-7974-8}, publisher={IEEE}, booktitle={GLOBECOM '03. IEEE Global Telecommunications Conference (IEEE Cat. No.03CH37489)}, pages={4180--4185}, author={Pletka, Roman and Kind, Andreas and Waldvogel, Marcel and Mannal, Soenke} }

<rdf:RDF xmlns:dcterms="" xmlns:dc="" xmlns:rdf="" xmlns:bibo="" xmlns:dspace="" xmlns:foaf="" xmlns:void="" xmlns:xsd="" > <rdf:Description rdf:about=""> <dspace:hasBitstream rdf:resource=""/> <dcterms:abstract xml:lang="eng">Today's known and widely used active queue management (AQM) schemes do not differentiate between packets from responsive (e.g., TCP sessions) and non-responsive traffic (e.g., UDP). This results in further widening the gap of unfair advantage already inherent to non-responsive traffic, as the responsive sender will significantly reduce its future transmit rate as a result of the congestion signals. As a simple work-around, responsive and non-responsive traffic are often assigned distinct AQM parameters. This approach however requires tuning for each traffic class that potentially depends on the current or expected offered load. In other words, responsiveness and TCP-friendliness cannot be estimated easily�not at last due to short-lived TCP sessions. In this paper we propose a closed-loop congestion control (CLCC) scheme on top of an existing AQM scheme to achieve fair bandwidth distribution among concurrent responsive and non-responsive traffic. The new scheme has the advantage that it does not need to estimate the level of responsiveness of traffic. We analyze our scheme on top of an existing rate-based AQM scheme known to approximate max-min fairness, and by means of simulations show that our extension significantly improves fair bandwidth allocation for responsive and non-responsive traffic. The simulation results have been verified with a prototype implementation on the IBM PowerNP 4GS3 network processor.</dcterms:abstract> <dspace:isPartOfCollection rdf:resource=""/> <dc:creator>Mannal, Soenke</dc:creator> <dc:creator>Pletka, Roman</dc:creator> <dc:contributor>Kind, Andreas</dc:contributor> <dc:creator>Waldvogel, Marcel</dc:creator> <dcterms:bibliographicCitation>First publ as paper in: IEEE Global Telecommunications Conference (Globecom 2003, San Francisco, CA, USA, 2003), Vol. 7, pp. 4180- 4185</dcterms:bibliographicCitation> <dcterms:rights rdf:resource=""/> <dc:contributor>Waldvogel, Marcel</dc:contributor> <dc:rights>terms-of-use</dc:rights> <dcterms:hasPart rdf:resource=""/> <dc:contributor>Mannal, Soenke</dc:contributor> <dc:contributor>Pletka, Roman</dc:contributor> <dcterms:issued>2003</dcterms:issued> <dc:creator>Kind, Andreas</dc:creator> <dcterms:isPartOf rdf:resource=""/> <dcterms:available rdf:datatype="">2011-03-24T16:11:29Z</dcterms:available> <bibo:uri rdf:resource=""/> <dc:language>eng</dc:language> <void:sparqlEndpoint rdf:resource="http://localhost/fuseki/dspace/sparql"/> <dc:date rdf:datatype="">2011-03-24T16:11:29Z</dc:date> <dc:format>application/pdf</dc:format> <foaf:homepage rdf:resource="http://localhost:8080/jspui"/> <dcterms:title>Closed-Loop Congestion Control for Mixed Responsive and Non-Responsive Traffic</dcterms:title> </rdf:Description> </rdf:RDF>

Dateiabrufe seit 01.10.2014 (Informationen über die Zugriffsstatistik)

closed_loop_congestion_control_for_responsive.pdf 139

Das Dokument erscheint in:

terms-of-use Solange nicht anders angezeigt, wird die Lizenz wie folgt beschrieben: terms-of-use

KOPS Suche


Mein Benutzerkonto