2013
DOI: 10.1002/ett.2641
|View full text |Cite
|
Sign up to set email alerts
|

Estimation of in‐service quality of experience for peer‐to‐peer live video streaming systems using a user‐centric and context‐aware approach based on Bayesian networks

Abstract: In this paper, a modified and improved quality of experience (QoE) estimation approach has been presented on the basis of the user‐behavior modelling and context‐aware modelling. We have implemented this proposed approach for peer‐to‐peer live video streaming systems because of the dynamically adaptive and distributed nature of these systems. The problem of estimating QoE is formulated as a Bayesian network model using user‐behavior and context‐related variables as nodes. The relationship between these nodes a… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2013
2013
2019
2019

Publication Types

Select...
2
1
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(1 citation statement)
references
References 20 publications
0
1
0
Order By: Relevance
“…The problems with route‐by‐name anycast are listed as follows: (i) server selection is solely based on routing metrics, so that it lacks flexibility in server selection; (ii) anycast addresses or name prefixes have to be published into the entire routing system, which will inflate routing tables and significantly threaten routing scalability ; (iii) in name‐based routing architectures such as DONA, NDN and SCAFFOLD, flexible‐length names degrade routing efficiency ; and (iv) it is difficult to support flow affinity , that is, to direct sequential requests within a session to the same server. This is indeed a basic feature for stateful multimedia services .…”
Section: Introductionmentioning
confidence: 99%
“…The problems with route‐by‐name anycast are listed as follows: (i) server selection is solely based on routing metrics, so that it lacks flexibility in server selection; (ii) anycast addresses or name prefixes have to be published into the entire routing system, which will inflate routing tables and significantly threaten routing scalability ; (iii) in name‐based routing architectures such as DONA, NDN and SCAFFOLD, flexible‐length names degrade routing efficiency ; and (iv) it is difficult to support flow affinity , that is, to direct sequential requests within a session to the same server. This is indeed a basic feature for stateful multimedia services .…”
Section: Introductionmentioning
confidence: 99%