QoE evaluation of dynamic adaptive streaming over HTTP (DASH) with promising transport layer protocols
- PDF / 1,109,174 Bytes
- 16 Pages / 595.276 x 790.866 pts Page_size
- 76 Downloads / 209 Views
REGULAR PAPER
QoE evaluation of dynamic adaptive streaming over HTTP (DASH) with promising transport layer protocols Transport layer protocol performance over HTTP/2 DASH Koffka Khan1 · Wayne Goodridge1 Received: 10 March 2020 / Accepted: 4 November 2020 © China Computer Federation (CCF) 2020
Abstract Recently, dynamic adaptive streaming over HTTP (DASH) has become an increasingly popular way to view video over the Internet. In particular compared to other video streaming services these DASH approaches deliver superior QoE to viewers. This is due to improved video segment selection. Generally, Transmission Control Protocol (TCP) CUBIC is the defacto transport layer protocol use by DASH. To improve the robustness of the transport layer to network congestion many other TCP variants were implemented such as Compound TCP and BBR. Nevertheless some were made to work specifically in LAN environments for example Agile-SD. However, recently another transport layer protocol User Datagram Protocol (UDP) has been used in Google’s QUIC implementation. To date no work has be found giving the performance of these transport layer protocols with DASH. In this paper we test the performance of Agile-SD, CUBIC, Compound TCP, BBR and QUIC using the BBA, MPC, Pensieve and Oboe DASH approaches. Experiments simulate congested bottleneck link conditions common at household routers where families view multiple videos at the same time. We observe Oboe and Agile-SD is the most promising combination with CUBIC and Pensieve next. However, even though QUIC was touted to have superior transport layer performance by Google it was the worst performing. Keywords HTTP · DASH · Rate · Adaptation · Video · Segment · CUBIC · TCP · UDP · QUIC · Congestion · Compound · BBR · BBA · MPC · Pensieve · Agile-SD · Oboe
1 Introduction The popularity of DASH (Sodagar 2011) rose in recent years. This is created by the robustness of its video feed to varying network conditions (Khan and Goodridge 2019a, b). A DASH video is broken up into many segments of different sizes. These are stored on a media server. Typical segment sizes range from 2 to 20s. Take a video with 6s segments available in three different qualities. On the DASH server there would be the entire video of 6s segments of low, medium and high quality, respectively and all will be * Koffka Khan [email protected]; [email protected] 1
Department of Computing and Information Technology (DCIT), Faculty of Science and Technology (FST), The University of The West Indies (UWI), St. Augustine, Trinidad
available to client players. Choosing a single quality from these three different quality video segments for next segment download makes DASH very attractive in best-effort networks such as the Internet. Transmission Control Protocol (TCP) (Postel 1981) has supplanted User Datagram Protocol (UDP) (Postel 1980) in Internet video delivery systems. Nowadays, adaptive video streaming players at the application layer employ TCP as their transport layer protocol. One of the main reasons is TCP tra
Data Loading...
