Reference Hub6
VAQoS: Architecture for End-to-End QoS Management of Value Added Web Services

VAQoS: Architecture for End-to-End QoS Management of Value Added Web Services

M. A. Serhani, R. Dssouli, H. Sahraoui, A. Benharref, M. E. Badidi
Copyright: © 2006 |Volume: 2 |Issue: 4 |Pages: 20
ISSN: 1548-3657|EISSN: 1548-3665|ISSN: 1548-3657|EISBN13: 9781615203697|EISSN: 1548-3665|DOI: 10.4018/jiit.2006100103
Cite Article Cite Article

MLA

Serhani, M. A., et al. "VAQoS: Architecture for End-to-End QoS Management of Value Added Web Services." IJIIT vol.2, no.4 2006: pp.37-56. http://doi.org/10.4018/jiit.2006100103

APA

Serhani, M. A., Dssouli, R., Sahraoui, H., Benharref, A., & Badidi, M. E. (2006). VAQoS: Architecture for End-to-End QoS Management of Value Added Web Services. International Journal of Intelligent Information Technologies (IJIIT), 2(4), 37-56. http://doi.org/10.4018/jiit.2006100103

Chicago

Serhani, M. A., et al. "VAQoS: Architecture for End-to-End QoS Management of Value Added Web Services," International Journal of Intelligent Information Technologies (IJIIT) 2, no.4: 37-56. http://doi.org/10.4018/jiit.2006100103

Export Reference

Mendeley
Favorite Full-Issue Download

Abstract

During the last few years, Value Added Web Services (VAWS) are increasingly becoming a hot issue in both research and industry. With the abundance of VAWS providers, Quality of Service (QoS) is a key factor to allow potential clients to differentiate between providers. In this paper, we propose a new architecture, called VAQoS, for managing and assuring QoS provision for VAWS. This architecture performs management of QoS by: (1) allowing providers to extend the service description with QoS-centered annotations, (2) including a validation process that enables providers to test their service interfaces as well as the level of QoS they can provide prior to publishing the service, (3) allowing clients to express their required functionalities with QoS requirements; (4) providing support for QoS negotiation between clients and providers, (5) allowing monitoring of the agreed QoS between clients and providers, and therefore, detecting any QoS violation; (6) providing an application programming interface that shields the application of the provider and client from the complexity of managing QoS specification, QoS publication, and QoS discovery. A first prototype of VAQoS is developed.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.