Evaluation of MPTCP congestion control for DASH
01 Sep 2017-pp 279-283
TL;DR: This paper investigates the performance of MPTCP when DASH clients use this protocol and shows that QoE achieved by the clients significantly changes due to congestion control algorithm thatMPTCP uses.
Abstract: Dynamic Adaptive HTTP Streaming (DASH) is a popular MPEG standard. In DASH systems, the clients adapt quality based on the observed network and internal parameters in order to achieve high Quality of Experience (QoE). The throughput of Internet applications can be increased if the underlying transport protocol utilizes the network conditions by using multiple end-to-end connections. MPTCP is a recent technology that allows clients to open multiple TCP connections without requiring a change in the client software. In this paper, we investigate the performance of MPTCP when DASH clients use this protocol. The experimental results show that QoE achieved by the clients significantly changes due to congestion control algorithm that MPTCP uses.
Citations
More filters
14 Oct 2019
TL;DR: The performances of different MPTCP schedulers are investigated and it is shown how the selection of the paths forMPTCP subflows affect communication performance in case of link failures.
Abstract: In order to sustain the connectivity in case of a technology related disaster, providing multipath connection infrastructure can be an alternative. Multipath TCP (MPTCP) is a transport layer protocol which allows more than one path to transfer TCP segments by utilizing multi-homed devices. MPTCP can be used for minimizing the connectivity problems in case of a failure. It is known that the performance of MPTCP can be increased if the paths for the subflows are carefully chosen by considering the disjointness and end-to-end delay of the paths. On the other hand, the scheduler affects the performance of MPTCP especially when connectivity problems exist. In this paper, we investigate the performances of different MPTCP schedulers and show how the selection of the paths for MPTCP subflows affect communication performance in case of link failures.
4 citations
Cites background from "Evaluation of MPTCP congestion cont..."
...Although the performance of MPTCP congestion control has been widely studied [3], [4], [5], there is limited work on the performance of MPTCP schedulers in the literature....
[...]
05 Jul 2019
TL;DR: The results show that the performance of DASH decreases when the paths of MPTCP have different bandwidths.
Abstract: Recently, dynamic adaptive streaming over HTTP (DASH) is a dominated traffic in Internet. The client requests a suitable representation depending on the current network condition. On the other hand, multipath transmission control protocols emerges as potential data transmission utilizing multiple network paths concurrently. In this paper, we conduct extensively experiments to evaluate the performance of DASH over MPTCP. Four different performance metrics are investigated, i.e., time on high quality, impactful switches, switch frequency, and average bitrate. The results show that the performance of DASH decreases when the paths of MPTCP have different bandwidths.
1 citations
Cites methods from "Evaluation of MPTCP congestion cont..."
...The work [7] evaluates the performance of different congestion control algorithms when transmitting DASH....
[...]
References
More filters
TL;DR: The CUBIC protocol modifies the linear window growth function of existing TCP standards to be a cubic function in order to improve the scalability of TCP over fast and long distance networks.
Abstract: CUBIC is a congestion control protocol for TCP (transmission control protocol) and the current default TCP algorithm in Linux. The protocol modifies the linear window growth function of existing TCP standards to be a cubic function in order to improve the scalability of TCP over fast and long distance networks. It also achieves more equitable bandwidth allocations among flows with different RTTs (round trip times) by making the window growth to be independent of RTT -- thus those flows grow their congestion window at the same rate. During steady state, CUBIC increases the window size aggressively when the window is far from the saturation point, and the slowly when it is close to the saturation point. This feature allows CUBIC to be very scalable when the bandwidth and delay product of the network is large, and at the same time, be highly stable and also fair to standard TCP flows. The implementation of CUBIC in Linux has gone through several upgrades. This paper documents its design, implementation, performance and evolution as the default TCP algorithm of Linux.
2,088 citations
"Evaluation of MPTCP congestion cont..." refers background in this paper
...These congestion control algorithms are cubic [14], Reno [13], lia [15] (Linked Increase Algorithm), olia [16] (Opportunistic Linked Increase Algorithm), wVegas [17]...
[...]
20 Oct 2010
TL;DR: The greatest value of Mininet will be supporting collaborative network research, by enabling self-contained SDN prototypes which anyone with a PC can download, run, evaluate, explore, tweak, and build upon.
Abstract: Mininet is a system for rapidly prototyping large networks on the constrained resources of a single laptop The lightweight approach of using OS-level virtualization features, including processes and network namespaces, allows it to scale to hundreds of nodes Experiences with our initial implementation suggest that the ability to run, poke, and debug in real time represents a qualitative change in workflow We share supporting case studies culled from over 100 users, at 18 institutions, who have developed Software-Defined Networks (SDN) Ultimately, we think the greatest value of Mininet will be supporting collaborative network research, by enabling self-contained SDN prototypes which anyone with a PC can download, run, evaluate, explore, tweak, and build upon
1,890 citations
23 Feb 2011
TL;DR: In this paper, some insight and background into the Dynamic Adaptive Streaming over HTTP (DASH) specifications as available from 3GPP and in draft version also from MPEG is provided.
Abstract: In this paper, we provide some insight and background into the Dynamic Adaptive Streaming over HTTP (DASH) specifications as available from 3GPP and in draft version also from MPEG. Specifically, the 3GPP version provides a normative description of a Media Presentation, the formats of a Segment, and the delivery protocol. In addition, it adds an informative description on how a DASH Client may use the provided information to establish a streaming service for the user. The solution supports different service types (e.g., On-Demand, Live, Time-Shift Viewing), different features (e.g., adaptive bitrate switching, multiple language support, ad insertion, trick modes, DRM) and different deployment options. Design principles and examples are provided.
1,203 citations
"Evaluation of MPTCP congestion cont..." refers background in this paper
...Generally, if the client observes the throughput is high enough to play the video with high quality, then the segments of the high-quality video is requested [6]....
[...]
TL;DR: A new standard to enable dynamic and adaptive streaming of media over HTTP is finalized, which aims to address the interoperability needs between devices and servers of various vendors.
Abstract: MPEG has recently finalized a new standard to enable dynamic and adaptive streaming of media over HTTP. This standard aims to address the interoperability needs between devices and servers of various vendors. There is broad industry support for this new standard, which offers the promise of transforming the media-streaming landscape.
1,085 citations
Additional excerpts
...As a result of this tendency, MPEG group has standardized DASH to provide interoperability between video streaming server and clients developed by different companies[1]....
[...]
Proceedings Article•
25 Apr 2012
TL;DR: The constraints--partly due to various types of middleboxes-- that influenced the design of Multipath TCP are reviewed and how the implementation was handled is shown to achieve its deployability goals.
Abstract: Networks have become multipath: mobile devices have multiple radio interfaces, datacenters have redundant paths andmultihoming is the normfor big server farms. Meanwhile, TCP is still only single-path.
Is it possible to extend TCP to enable it to support multiple paths for current applications on today's Internet? The answer is positive. We carefully review the constraints--partly due to various types of middleboxes-- that influenced the design of Multipath TCP and show how we handled them to achieve its deployability goals.
We report our experience in implementing Multipath TCP in the Linux kernel and we evaluate its performance. Our measurements focus on the algorithms needed to efficiently use paths with different characteristics, notably send and receive buffer tuning and segment reordering. We also compare the performance of our implementation with regular TCP on web servers. Finally, we discuss the lessons learned from designing MPTCP.
559 citations