2014
DOI: 10.2478/bpasts-2014-0021
|View full text |Cite
|
Sign up to set email alerts
|

Fluid flow approximation of time-limited TCP/UDP/XCP streams

Abstract: Abstract. This article presents the use of fluid flow approximation to model interactions between a set of TCP, UDP and XCP flows in the environment of IP routers using AQM (Active Queue Management) algorithms to control traffic congestion. In contrast to other works, independent UDP and TCP streams are considered and the model allows to start and end data transmissions in TCP, UDP and XCP streams at any time moment. It incorporates several Active Queue Management mechanisms: RED, NLRED, CHOKe.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
10
0

Year Published

2015
2015
2023
2023

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 12 publications
(10 citation statements)
references
References 56 publications
(92 reference statements)
0
10
0
Order By: Relevance
“…Our main goal is to show the behavior of the two completely different TCP mechanisms, taking into account various network scenarios in terms of amount of TCP flows as well as queue management disciplines (namely, standard FIFO with tail drop and RED, the best-known example of AQM mechanism). For numerical fluid flow computations we used a software written in Python and previously presented in [4]. During the tests we assumed the following TCP connection parameters:…”
Section: Resultsmentioning
confidence: 99%
See 1 more Smart Citation
“…Our main goal is to show the behavior of the two completely different TCP mechanisms, taking into account various network scenarios in terms of amount of TCP flows as well as queue management disciplines (namely, standard FIFO with tail drop and RED, the best-known example of AQM mechanism). For numerical fluid flow computations we used a software written in Python and previously presented in [4]. During the tests we assumed the following TCP connection parameters:…”
Section: Resultsmentioning
confidence: 99%
“…In the literature, traffic composed of TCP and UDP streams has been already considered, but in most works (for instance, in [5,13]) all TCP sources had the same window dynamics and UDP streams were permanently associated with the TCP stream. Instead, in this paper, extending our previous work presented in [4], the TCP and UDP streams are treated as separate flows. Moreover, unlike [9] and [14], TCP connections start at different times with various values of initial CWND.…”
Section: Introductionmentioning
confidence: 99%
“…We have also proposed and evaluated a few variants (cf. Domańska et al 2014a;2014c;Augustyn et al, 2010;Domański et al, 2012).…”
Section: A Domański Et Almentioning
confidence: 99%
“…In this article, the TCP and UDP streams are treated as separate streams. In the works of Kiddle et al (2003) and Yung et al (2001) a separate UDP stream was used; our work (described by Domańska et al (2014c)) differs in this respect in that TCP can start from various initial window sizes. Additionally, we can set up a time after which the stream (TCP or UDP) will be started.…”
Section: A Domański Et Almentioning
confidence: 99%
See 1 more Smart Citation