Professional Documents
Culture Documents
Department of Radiophysics
Tomsk State University
Tomsk, Russia
ngkushik@gmail.com, ninayevtushenko@yahoo.com
Number of publications
201
I.
INTRODUCTION
QoE
51
1996
1998
2000
2002
Year
2004
2006
2008
2010
QoS
101
___________________________________________________
1
151
587
PRELIMINARIES
588
III.
?date
q1
!date
q2
?fstat
?date
?exit
q0
q4
!not reserved
q3
!reserved
!not reserved
q6
?hstat
!date
q5
K B
K5
,
m = K1 Be + 2 e + K 3 Dc
256
L
r + K4
where K1, K2, K3, K4, K5 are coefficients which have values
between 0 and 1 and are defined by a network administrator,
Be is a channel bandwidth calculated as the ratio of the
integer 107 to minimal bandwidth (Kb/sec), L is a traffic
load with values 1, , 255, Dc is one tenth of overall delay
measured in microseconds, r is a relative reliability, e.g., the
percentage of successfully transmitted packets via this route.
If K5 = 0 then the reliability is not taken into account. By
default, K1 = K2 = 1, K3 = K4 = K5 = 0, and Cisco
recommends not to change these parameters.
Similar formulae for the QoS evaluation are used for
multimedia services [see for example, 34]. We note that
coefficients of the formula may not be given in the literature
and sometimes they are considered as know-how of the
company that evaluates quality of its services. Still, there are
some statistical data available that may help developers and
testers to evaluate QoS of services they are using.
An obvious advantage on this approach is that the quality
estimation based on the traffic analysis is well established
and is widely used, especially in the industry. However,
these approaches which work rather well for evaluating
audio and video transmitting systems become almost useless
when the parameters of interest are related to the user
satisfaction such as the comfort of proposed solutions, the
amount of money to be spent etc. In order to illustrate this
fact we consider a simple example.
589
equality
i =0
several services S1, , Sk parallel pattern (Fig. 3c), or ANDsplit pattern, is considered. Services executing tasks in
parallel can be further merged in order to execute a required
later task. If the next service is invoked only when all
preceding services have completed their tasks, the
synchronizing, or AND-joint, pattern (Fig. 3d) is considered.
Otherwise, if the next service is invoked after the first
service completes its task, the concurrent pattern (Fig. 3e), or
XOR-joint, is at hand. When some tasks should be repeated,
the loop pattern (Fig. 3f) is considered, and the number of
repetitions may be either known a priori or can be calculated
during the task execution. Without loss of generality, we
consider loops with a single starting point (service S1 in Fig.
3f) and any number of exits (service Si in Fig. 3f). For each
exit point probabilities of continuing the loop or of going out
may be specified.
S1
p1
S0
S1
S0
pk
S1
.
.
.
||
S0
Sk
a
S1
.
.
.
.
.
.
Sk+1
Sk
Sk
S1
Sk+1
Si
S1
Sk
Sk
.
.
.
590
TABLE I.
QoS Attribute
Sequential
k
ci
Cost (c)
i =1
k
ai
Availability (a)
i =1
k
ti
i =1
k
Parallel AND-joint
ci
i =1
ai
1 (1 ai )
k
ai
i =1
max(ti )
max(ti )
min(ti )
n ti
i =1
i =1
i =1
1 k
qi
k i =1
i =1
i =1
1
qi
k i =1
i =1
1
qi
k i =1
[18, 41]
[20, 41]
i =1
k
ri
i =1
1 k
qi
k i =1
[18, 21,
41]
[18, 21]
p i ci
pi t i
j
i =1 i
j 1
i =0 i
i = j +1 ci )
k
j 1
i =0 i
j
i =1 i
2
k
i =1 i
j =1
591
j
i =1 a i
k
i =1 pi
[20, 41]
[20]
k
i =1 i i
j =1
k
i =1 pi
2
k
i =1 i
j =1
i =1
i =1
)(1 p )( c +
(1 p )
( p )(1 p )
(1 p a )
p )(1 p )( t +
(1 p )
j 1
i =0 p i
pi a i
k
Reference
Loop
[20, 41]
i =1
ai
ri
i =1
Availability (a)
n ci
i =1
ri
Cost (c)
Reference
Loop
k
ci
i =1
QoS Attribute
ci
ri
1
qi
k i =1
TABLE II.
Parallel XOR-joint
ri
i =1
Reputation (q)
XOR-split
i = j +1 ti )
k
[20, 41]
FB
HB
Fig. 4. Workflow for the vacation planner service
592
The set of
QoBiz
parameters
Automatic evaluation
ACKNOWLEDGMENT
The work is partly supported by Futur et Ruptures
scholarship from Fondation Telecom (France) for Olga
Kondratyeva, and by Russian Ministry of High Education
and Science (contract 14.37.21.0622, Russia).
REFERENCES
[1]
[2]
Fig. 5. The relationship between sets of attributes used for different metrics
when evaluating the quality of web services
[3]
[4]
[5]
[6]
CONCLUSION
[7]
[8]
[9]
[10]
[11]
[12]
[13]
[14]
[15]
[16]
593
594