2014
DOI: 10.1007/978-3-662-45391-9_28
|View full text |Cite
|
Sign up to set email alerts
|

QoS-Aware Complex Event Service Composition and Optimization Using Genetic Algorithms

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
10
0

Year Published

2015
2015
2019
2019

Publication Types

Select...
5
3
1

Relationship

2
7

Authors

Journals

citations
Cited by 18 publications
(12 citation statements)
references
References 7 publications
0
10
0
Order By: Relevance
“…Also, the requested service type (ces:TrafficReportService) is an exact match for the service type in Listing 2, making the service described in Listing 2 a matching service candidate for the request. When the discovery component finds all candidate services suitable for the request, a Simple-Additive-Weighting algorithm [55] is used to rank the service candidates based on q d , q r and pref.…”
Section: Sensors Streams Discoverymentioning
confidence: 99%
“…Also, the requested service type (ces:TrafficReportService) is an exact match for the service type in Listing 2, making the service described in Listing 2 a matching service candidate for the request. When the discovery component finds all candidate services suitable for the request, a Simple-Additive-Weighting algorithm [55] is used to rank the service candidates based on q d , q r and pref.…”
Section: Sensors Streams Discoverymentioning
confidence: 99%
“…However, not all metrics supported by OWL-Q and not all composition patterns supported by WSSL are covered in existing work (e.g. [9,14,17,26,34]). To address this, we propose a set of generalised QoS aggregation functions, as shown in Table 2.…”
Section: Qos Aggregation For Composite Sbasmentioning
confidence: 99%
“…Instead, most reviewed ASC approaches only concentrate on one nonfunctional consideration, and the most widely studied nonfunctional consideration in ASC research is the QoS. Pure QoS-based service selection approaches, such as [27], [28], [31], [39], [71], [72], [77], [79], [80], [81], [91], [92], [93], [94], [95], [96], [97], and [98], only require the QoS information that is relevant to their available component services. Consequently, their SD formulation only needs to contain one composite tuple Q (QoS), and its child elements vary from approach to approach.…”
Section: Generic Tuple-based Sd Modelmentioning
confidence: 99%