A QoS and Security Adaptation Model for Autonomic Pervasive Systems

Abstract

The unpredictable fluctuations in computing resources, contexts, and user preferences that characterize pervasive environments have stressed the need for context-aware selfadaptive systems. So far, this research area mostly dealt exclusively with concerns related either to standard QoS or to security. Taking into account trade-offs between these two conflicting concerns is a key issue, since they both compete for the same resources. This paper presents a general adaptivity model that reconciles these two concerns. This model is formalized as a component composition selection process, where the best composition is found by reasoning on security and non-security properties of the system. Utility functions are used to quantify how a component composition alternative is appropriate in a given context, with respect to the user preferences.

Mobile user profiles for Personal Networks: The MAGNET Beyond case

“…In this context, project Daidalos [9] deals with the role of user preferences in pervasive systems and proposes handling those via static and dynamic (depending on the case) personalization. Moreover, the topic of profile definition is often implicitly handled through research regarding personalization and QoS in pervasive systems, as for example in [10,11].…”

Putting together QoS and security in autonomic pervasive systems

“…A first component-based adaptation model taking into account QoS and security was sketched by Alia and Lacoste in [3]. In this model (refered to as AL-model in the sequel), adaptation planning is formalized as a component composition selection problem where each implementation of a component type may provide different QoS and/or security properties.…”

Components and Aspects Composition Planning for Ubiquitous Adaptive Services

“…this solution does not scale when the number of concerns increases, meaning that the combination of C concerns for an application typically implies the development of 2 C realizations of this application. Furthermore, adding such concerns into the applications usually introduce trade offs between Quality of Service (QoS) dimensions, such as security level and response time [4] that should be taken into account.…”