Impact of the LTE scheduler on achieving good QoE for DASH video streaming

Abstract

Dynamic adaptive video over HTTP (DASH) is fast becoming the protocol of choice for content providers for their online video streaming delivery. Concurrently, dependence on cellular Long Term Evolution (LTE) networks is growing to serve user demands for bandwidth-hungry applications, especially video. Each LTE base station's (eNodeB) scheduler assigns wireless resources to individual clients. Several alternative schedulers have been proposed, especially to meet the user's desired quality of experience (QoE) with video. In this paper, we investigate the impact of the scheduler on DASH performance, motivated by the fact that video performance and the underlying traffic models are different from other HTTP/TCP applications. We use our laboratory testbed employing real video content and streaming clients, over a simulated ns-3 LTE network. We quantify the impact of the scheduler and show that it has a significant impact on key video streaming performance metrics such as stalls and QoE, for different client adaptation algorithms. Additionally, we show the impact of user mobility within a cell, which has the side-effect of improving performance by mitigating long-term fading effects. Our detailed assessment of four LTE schedulers in ns-3 shows that the proportional fair scheduler achieves the best overall user experience, although somewhat disadvantaging static cell-edge users

Variable-threshold buffer based adaptation for DASH mobile Video Streaming

“…Zahran et al [13] evaluate the performance of different adaptation logics with different schedulers over cellular LTE networks. The results show that proportional fairness is the most suitable scheduler for video streaming in LTE networks.…”

D-LiTE: A platform for evaluating DASH performance over a simulated LTE network

“…This permits H.264 and H.265 decoding at the clients. Information on the implementation steps used for the NS-3/LTE aspect of the demo can be found in [4]. The DASH dataset [5] utilised for this demo is available at 2 .…”