Abstract
Multipath transport protocols are aimed at increasing the throughput of data flows as well as maintaining fairness between users, which are both crucial factors to maximize user satisfaction. In this paper, a mixed (non)linear programming (MINLP) solution is developed which provides an optimum solution to allocate link capacities in a network to a number of given traffic demands considering both the maximization of link utilization as well as fairness between transport layer data flows or subflows. The solutions of the MINLP formulation are evaluated w. r. t. their throughput and fairness using well-known metrics from the literature. It is shown that network flow fairness based capacity allocation achieves better fairness results than the bottleneck-based methods in most cases while yielding the same capacity allocation performance.
Highlights
The aim of transport-layer protocols is the reliable end-to-end transport of data
In the context of Transmission Control Protocol (TCP) coexisting with other transport protocols on shared links, the term “TCP friendliness” means that a flow should not use a larger portion of the link capacity than a legacy TCP flow [2]
The aim of this work was a rigorous analysis of fairness in multipath transport
Summary
For best performance and resulting user satisfaction, Internet providers expect that transport protocols utilize links in an optimum way and avoid congestion in the network. Fairness means that a transport protocol should respond to congestion notifications such as packet loss or increase of delay by reducing the traffic load injected into the network. The most commonly used transport protocol in today’s Internet is the Transmission Control Protocol (TCP) [1]. It is used by “classical” applications which rely on reliable transmissions—such as web, e-mail or file transfer—and by some soft-real-time applications where delay is less critical, such as video streaming. In the context of TCP coexisting with other transport protocols on shared links, the term “TCP friendliness” means that a flow should not use a larger portion of the link capacity than a legacy TCP flow [2]
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
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 callDisclaimer: 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.
