This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
research:context [2006/06/30 19:20] jorge |
research:context [2009/11/30 16:55] dharnie *prog->soft |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Role-Based Ambient Communications ====== | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | ===== Motivation ===== | ||
- | |||
- | Within the domain of pervasive computing, context-awareness has commonly been defined as the ability of an application to adapt itself to its dynamic environment. The context of an application is defined as any information or service in the application' | ||
- | |||
- | Our observation is that in an interaction between two entities, the behaviour of the message receiver may not only depend on the context itself, but also on the context of the sender. We have illustrated this idea in a high level **[[research: | ||
- | |||
- | We claim that in order to deal with context-dependent communications in mobile networks, we need a model that satisfies the following conditions: | ||
- | |||
- | * **Dynamic Context Adaptation**: | ||
- | |||
- | * **Dynamic Behaviour Composition**: | ||
- | |||
- | * **Context Passing Mechanism**: | ||
- | |||
- | ===== Design ===== | ||
- | |||
- | At the PROG lab, we are currently exploring different language constructs for the development of context-aware applications. The construct presented in this page is called Split Objects (Bardou et al, ECOOP 1996). In such a model, application entities are composed of roles (known as viewpoints) which represent the different behaviours the entity can adopt according to their context. A role is a particular point of view on an entity that has an identification and a partial definition of that entity. The model' | ||
- | |||
- | {{ rolemodel.jpg }} | ||
- | |||
- | The problem with the split objects model is that the message sender must know before hand which are the roles a receiver could take. We claim that in dynamic environments like the scenarios of pervasive computing, it is practically impossible to have this level of acknowledgment of all the participants of the network. Hence we have extended this model in such a way that the sender only have to include its own context information in the messages (and not a role). At the receiver side there will be an entity that will take as input the context of both sender and receiver, and will map this information to a role. We have called this entity th context-dependent role selector. For further information about this model, we refer the interested reader to [ [[http:// | ||
- | |||
- | ===== Ongoing and Future Work ===== | ||
- | |||
- | * Composition of context-dependent application behaviours using prototype-based solutions (delegation hierarchies, | ||
- | | ||
- | * Context-dependent adaptations of behaviour using role-based models. | ||
- | |||
- | * Rule-based systems for context reasoning and role selection. | ||
- | |||
- | * Role-based communications. | ||
- | |||
- | * Combining actor and role models for the development of context-dependent applications. | ||
- | |||
- | * Ad-hoc and intentional actor grouping. | ||
- | |||
- | * Intra and Inter actor layers for context-dependent adaptations. | ||
- | |||
- | * Dynamic scope for context-dependent communications. | ||
- | |||
- | ===== Further Reading ===== | ||
- | |||
- | **A Role-Based Implementation of Context-Dependent Communications Using Split Objects**. Jorge Vallejos, Peter Ebraert, Brecht Desmet. In " |