Reflective Middleware Solutions for Context-Aware Applications

Licia Capra, Wolfgang Emmerich, Cecilia MascoloReflection 2001 · DOI

TL;DR

This paper proposes a novel middleware architecture for mobile, context-aware applications by combining reflection and metadata. It addresses the limitations of traditional middleware in dynamic mobile environments by allowing applications to dynamically inspect and influence their behavior based on context changes.

What Problem Does This Paper Address?

The proliferation of mobile devices and wireless networking has created a new paradigm for distributed systems. Traditional middleware, designed for stable, wired networks, assumes a "black box" transparency that hides distribution complexities. However, this approach is ill-suited for mobile environments where devices experience frequent disconnections, fluctuating bandwidth, and limited resources. Mobile applications need to be aware of their "context" – factors like location, battery life, and network availability – to adapt their behavior effectively. The challenge lies in providing this context awareness without burdening application designers with low-level distribution details or forcing them to hardcode context-dependent logic.

Methods

The authors propose a reflective middleware architecture that leverages two key concepts:

  • Metadata: This separates concerns by distinguishing what the middleware does from how it does it. Metadata is used to store information about how the middleware should behave in different contexts.
  • Reflection: This provides applications with a mechanism to dynamically inspect and alter the middleware's metadata. This allows applications to influence the middleware's behavior based on their current execution context.

Specifically, the middleware maintains an "application profile" which acts as metadata for the middleware. This profile is written by the application designer and specifies how the application wants to react to context changes and how it prefers services to be delivered. The authors propose using XML and XML Schema for modeling this information, allowing for structured and flexible representation of context-aware policies.

The middleware monitors the underlying network operating system for context changes. When a change occurs, it consults the application profiles to determine the appropriate actions. Applications can also dynamically update their profiles, enabling them to adapt to evolving user needs and environmental conditions.

Datasets

Not discussed in the paper.

Key Insights and Ideas

  • Transparency vs. Awareness: The paper argues that the transparency model of traditional middleware is counterproductive for mobile, context-aware applications. Instead, a degree of "awareness" is necessary.
  • Separation of Concerns: By using metadata, the middleware clearly separates the application's functional requirements from its context-dependent behavior.
  • Dynamic Adaptation: Reflection enables applications to dynamically adapt their behavior to changing contexts without requiring code modifications or redeployments.
  • XML for Context Modeling: The use of XML and XML Schema is highlighted as a powerful and flexible way to represent complex context-aware policies and application profiles.
  • User vs. Application Metadata: The paper distinguishes between user profiles (customizations for a specific user) and application profiles (middleware metadata influencing behavior based on context).

Key Results

The paper presents a conceptual model and a design for a reflective middleware. While specific quantitative results are not detailed, the authors demonstrate how their model can handle:

  • Context-aware setup: Applications can specify policies for reacting to context changes, such as disconnecting when battery power is low.
  • Service request policies: Applications can define preferred policies for service delivery based on context, like choosing between "copy" and "link" for data access depending on available memory and bandwidth.

Limitations and Future Work

The authors acknowledge several limitations and outline future research directions:

  • Conflicting Policies: The paper raises the question of how to handle situations where multiple applications or even a single application have conflicting policies for the same context.
  • Security: The reflective nature of the middleware, which allows access to internal data structures, poses potential security risks. Malicious programs could exploit this to disclose, modify, or delete data.
  • Extending the Prototype: The authors plan to extend their existing prototype to fully support the proposed reflective model.
  • Further Investigation: They intend to further investigate the issues of conflicting policies and security in mobile middleware.

Summary updated

BibTeX
@inproceedings{capra2001reflective,
  author = {Licia Capra and Wolfgang Emmerich and Cecilia Mascolo},
  title = {{Reflective Middleware Solutions for Context-Aware Applications}},
  booktitle = {Reflection},
  year = {2001},
  doi = {10.1007/3-540-45429-2\_10},
}
Figure