2009
DOI: 10.1108/17440080910947295
|View full text |Cite
|
Sign up to set email alerts
|

A survey on context‐aware web service systems

Abstract: Purpose of this paperThis survey aims at studying and analyzing current techniques and methods for context-aware Web service systems, discussing future trends and proposing further steps on making Web services systems being context-aware.Design/methodology/approach We analyzed and compared existing context-aware Web servicebased systems based on techniques they support, such as context information modeling, context sensing, distribution, security and privacy, and adaptation techniques. Existing systems are als… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
84
0
2

Year Published

2012
2012
2019
2019

Publication Types

Select...
4
4

Relationship

0
8

Authors

Journals

citations
Cited by 174 publications
(86 citation statements)
references
References 42 publications
0
84
0
2
Order By: Relevance
“…This means that static (e.g., services description available in Service Level Agreements -SLAs) or runtime (e.g., the time instant a service is requested or replies, or the expected resources usage) information can be retrieved using knowledge given by ESB. Consequently, having access to the ESB provides knowledge on the set of generic services running at any time t. We refer to this information as context-awareness of the considered SOA; note that we do not require information on the user context, contrary to what is typically done in the state-of-the-art on context-awareness [16], [17]. We can exploit this information to define more precisely the boundaries between normal and anomalous behavior of the SOA.…”
Section: Considering Context-awarenessmentioning
confidence: 99%
See 1 more Smart Citation
“…This means that static (e.g., services description available in Service Level Agreements -SLAs) or runtime (e.g., the time instant a service is requested or replies, or the expected resources usage) information can be retrieved using knowledge given by ESB. Consequently, having access to the ESB provides knowledge on the set of generic services running at any time t. We refer to this information as context-awareness of the considered SOA; note that we do not require information on the user context, contrary to what is typically done in the state-of-the-art on context-awareness [16], [17]. We can exploit this information to define more precisely the boundaries between normal and anomalous behavior of the SOA.…”
Section: Considering Context-awarenessmentioning
confidence: 99%
“…This is not surprising since most of the systems include these layers: building solutions which fetch data from these layers allow building frameworks that fit in a very wide range of contexts. Regarding context-awareness, as highlighted in [16], in service-oriented architectures it usually refers to knowledge of the user environment to improve the performances of web services. For example, the Akogrimo project [17] aims at supporting mobile users to access data, knowledge, and computational services on the Grid focusing on user-context (such as user location and environmental information).…”
Section: State Of the Art And Comparison With Other Solutionsmentioning
confidence: 99%
“…However, most context-aware systems are closed, composed of highly coupled constituents, and generated ad-hoc for a specific domain [6,54]. The same problem occurs when designing a dialog system.…”
Section: Introductionmentioning
confidence: 98%
“…Several authors [31,35,54] have highlighted the importance of standardizing and sharing a common base for context sensitivity and web services systems. However, most context-aware systems are closed, composed of highly coupled constituents, and generated ad-hoc for a specific domain [6,54].…”
Section: Introductionmentioning
confidence: 99%
“…Context information includes any additional information, e.g. a consumer's name, current location and address, type of client device and so on, which can be used to improve the behavior of a service in a situation [3], [4], [5], [6]. Without such additional information, the service would be operable as normal but with context information, which is arguable that the service can operate better or more appropriately [7], [8], [9], [10].…”
mentioning
confidence: 99%