2016 IEEE Sixth International Conference on Communications and Electronics (ICCE) 2016
DOI: 10.1109/cce.2016.7562675
|View full text |Cite
|
Sign up to set email alerts
|

Video QoE killer and performance statistics in WebRTC-based video communication

Abstract: Abstract-In this paper, we investigate session-related performance statistics of a Web-based Real-Time Communication (WebRTC) application called appear.in. We explore the characteristics of these statistics and explore how they may relate to users' Quality of Experience (QoE). More concretely, we have run a series of tests involving two parties and according to different test scenarios, and collected real-time session statistics by means of Google Chrome's WebRTC-internals tool. Despite the fact that the Chrom… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0

Year Published

2018
2018
2023
2023

Publication Types

Select...
5
2
1

Relationship

1
7

Authors

Journals

citations
Cited by 37 publications
(9 citation statements)
references
References 14 publications
0
9
0
Order By: Relevance
“…Data from two-and three-party video calls was collected under different CPU limitations and network impairments, using the WebRTC testbed described in [12]. Previous work [2], [3] has provided insights into the usefulness (and limitations) of WebRTC performance statistics gathered by Google Chrome and in the root causes of technical impairments that are perceivable (e.g., visually and/or auditory) by users. The work presented in this paper goes a step further and applies ML algorithms to the gathered datasets in order to estimate video blockiness, audio distortions, and to identify root causes of problems.…”
Section: A Overviewmentioning
confidence: 99%
See 2 more Smart Citations
“…Data from two-and three-party video calls was collected under different CPU limitations and network impairments, using the WebRTC testbed described in [12]. Previous work [2], [3] has provided insights into the usefulness (and limitations) of WebRTC performance statistics gathered by Google Chrome and in the root causes of technical impairments that are perceivable (e.g., visually and/or auditory) by users. The work presented in this paper goes a step further and applies ML algorithms to the gathered datasets in order to estimate video blockiness, audio distortions, and to identify root causes of problems.…”
Section: A Overviewmentioning
confidence: 99%
“…The statistics are collected per browser. Despite all the challenges, previous work has demonstrated the potential of using these statistics to study QoE aspects of WebRTC services [2], [3].…”
Section: B Data Collectionmentioning
confidence: 99%
See 1 more Smart Citation
“…Our performance evaluation focuses on a few key metrics such as data rate, frame rate, Round Trip Time (RTT), and call setup time, which have been shown to be the key factors that affect the user video experience [20,3]. Overall, this paper presents a thorough performance evaluation of WebRTC and discusses various performance-related tradeoffs.…”
Section: Introductionmentioning
confidence: 99%
“…Methodology: With our third study, we shifted from using the Samsung browser to using Chrome, as this provided the opportunity to access the webrtc-internals tool implemented within Chrome [6]. Webrtc-internals is an internal functionality for collecting statistics about ongoing WebRTC sessions [44]. To obtain statistics, a session has to be opened in the Chrome browser, and while in that session, another tab has to be open with the following URL: chrome://webrtcinternals.…”
Section: ) User Studymentioning
confidence: 99%