Abstract
SummaryThe throughput of a TCP flow depends on the average size of Congestion Window (cwnd) of a congestion control mechanism being used during the communication. The size of cwnd depends upon the usage of available link bandwidth during communication. The response function is a measure of average throughput of a single TCP flow of congestion control mechanism as the level of random packet loss is varied. Nowadays, many organizations are deploying IoT based applications for the analytics of their Big Data. TCP CUBIC and TCP Compound are the default congestion control mechanisms in Linux and Microsoft Windows Operating Systems respectively. Whereas, TCP Reno which is also known as Standard TCP congestion control mechanism is act as a trademark congestion control mechanism. During communication among different IoT applications, TCP CUBIC flows use more available link bandwidth as compared to TCP Reno flows, thus, the average cwnd size of TCP CUBIC flows are greater than the TCP Reno flows. It implies that these both kinds of flows are not sharing available link fairly, which refers as low TCP friendliness of TCP CUBIC. It means that the throughput of TCP CUBIC flows is higher than the trademark congestion control mechanism, i.e., TCP Reno flows. As a result, friendliness behavior or fair share of available link bandwidth among TCP CUBIC flows and TCP Reno flows is decreased. In other words, TCP friendliness of TCP CUBIC flows is reduced. Now, it is important to decrease the average cwnd size of TCP CUBIC flows, such that available link bandwidth can be shared fairly among flows of TCP CUBIC and TCP Reno. The aim of this research is to enhance the TCP friendliness behavior of TCP CUBIC congestion control mechanism for IoT based applications using Big Data. In this paper, an Advance Response Function of TCP CUBIC (ARFC) is designed to share fairly available link bandwidth among flows of TCP CUBIC and TCP Reno. Results show that TCP friendliness behavior of TCP CUBIC is increased by using ARFC. Overall, 18.6% performance is increased by using ARFC.
Published Version
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: Concurrency and Computation: Practice and Experience
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
