2011
DOI: 10.1186/1687-1499-2011-23
|View full text |Cite
|
Sign up to set email alerts
|

TCP NCE: A unified solution for non-congestion events to improve the performance of TCP over wireless networks

Abstract: In this article, we propose a unified solution called Transmission Control Protocol (TCP) for Non-Congestion Events (TCP NCE), to overcome the performance degradation of TCP due to non-congestion events over wireless networks. TCP NCE is capable to reduce the unnecessary reduction of congestion window size and retransmissions caused by non-congestion events such as random loss and packet reordering. TCP NCE consists of three schemes. Detection of non-congestion events (NCE-Detection), Differentiation of non-co… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0

Year Published

2012
2012
2020
2020

Publication Types

Select...
7
1

Relationship

0
8

Authors

Journals

citations
Cited by 24 publications
(9 citation statements)
references
References 24 publications
(26 reference statements)
0
9
0
Order By: Relevance
“…FTP sources start sending data at time 0 and are staggered to avoid synchronization. All simulations [37] are run for 150 seconds. The receiver advertises a large window such that the sending rate is not limited by the receiver dynamics.…”
Section: Simulation Environment and Resultsmentioning
confidence: 99%
“…FTP sources start sending data at time 0 and are staggered to avoid synchronization. All simulations [37] are run for 150 seconds. The receiver advertises a large window such that the sending rate is not limited by the receiver dynamics.…”
Section: Simulation Environment and Resultsmentioning
confidence: 99%
“…With frequent RTOs, before TCP sender raises size of cwnd to a reasonable value, it is compelled to resets it to a smallest value. Therefore, the effective size of cwnd over the data transfer phase is found inadequate to attain suitable bandwidth share [8] and hence retaining of the same leads to insignificant improvement. b) When BER is small, retaining of cwnd can potentially aggravate congestion in the network and cause heavy packet loss, both for itself and for other traffic in the network, especially if the old estimate of the rate is stale (due to sudden change in the network congestion) [5] [26].…”
Section: Solutions To Retain Value For Cwnd/ssthreshmentioning
confidence: 99%
“…If the loss rate due to wireless errors is high, a TCP sender with large values for TCP state variables has high possibility to have frequent burst losses and long go-back-N retransmissions [5]. Besides, the inaccuracy for estimation the common problem is that, all above techniques paid no attention on revising the Loss Window when RTO's are triggered regardless of congestion [8]. This in turn, inappropriately decelerates slow-start process after RTO, due to minimum Loss Window.…”
Section: Solutions With Advance Value For Cwnd/ssthreshmentioning
confidence: 99%
See 1 more Smart Citation
“…Therefore, one needs to differentiate congestion packet losses against random packet losses [4]. To this direction a number of various versions of TCP have been proposed including TCP Veno [5], TCP New Jersey [6] and TCP NCE [7]. In another work [8], the impact of TCP variants on the performance in MANETs routing protocols is investigated.…”
Section: Related Workmentioning
confidence: 99%