Improving TCP/IP performance over wireless networks
MobiCom '95 Proceedings of the 1st annual international conference on Mobile computing and networking
Dummynet: a simple approach to the evaluation of network protocols
ACM SIGCOMM Computer Communication Review
A comparison of mechanisms for improving TCP performance over wireless links
IEEE/ACM Transactions on Networking (TON)
TCP-real: improving real-time capabilities of TCP over heterogeneous networks
NOSSDAV '01 Proceedings of the 11th international workshop on Network and operating systems support for digital audio and video
TCP westwood: end-to-end congestion control for wired/wireless networks
Wireless Networks
Discriminating Congestion Losses from Wireless Losses using Inter-Arrival Times at the Receiver
ASSET '99 Proceedings of the 1999 IEEE Symposium on Application - Specific Systems and Software Engineering and Technology
I-TCP: indirect TCP for mobile hosts
ICDCS '95 Proceedings of the 15th International Conference on Distributed Computing Systems
Error differentiation with measurements based on wave patterns
Computer Communications
| Hi-index | 0.00 |
Residual bit-errors in wireless environments are well known to cause difficulties for congestion controlled protocols like TCP. In this study we focus on a receiver-based loss differentiation approach to mitigating the problems, and more specifically on two different loss notification schemes. The fully receiver-based 3-dupack scheme uses additional dupacks to implicitly influence the retransmission behavior of the sender. The second TCP option scheme uses a TCP option to explicitly convey a corruption notification. Although these schemes look relatively simple at first glance, when examining the details several issues exist which are highlighted and discussed. A performance evaluation based on a FreeBSD kernel implementation show that the TCP option scheme works well in all tested cases and provides a considerable throughput improvement. The 3-dupack scheme also provide performance gains in most cases, but the improvements varies more between different test cases, with some cases showing no improvement over regular TCP.