WSAMI: A Middleware Infrastructure for Ambient Intelligence based on Web Services

The WSAMI middleware is an open-source software freely distributed under the terms of the
GNU Lesser Public License (LGPL)


This work has received the support of the European Commission through the IST programme, as part of the IST Ozone project.

The WSAMI and related CSOAP software have been deposited at the APP under the respective names: IWSAMI and ICSOAP.

Overview


The OZONE WSAMI middleware is the first prototype implementation of the WSAMI middleware, which supports the dynamic composition of mobile Web services and is developed as part of the INRIA ARLES project-team research on mobile distributed systems for ambient intelligence.

Specifically, we are designing the WSAMI middleware to support the abstract specification of Ambient Intelligence applications in the form of software architectures, together with their dynamic composition according to the environment. The proposed middleware builds on the Web services architecture, whose pervasiveness enables service availability in most environments. In addition, dynamic composition of applications is dealt with in a way that enforces quality of service for deployed applications in terms of security and performance through the systematic customization of connectors that dynamically integrates relevant middleware-related services.

The WSAMI middleware prototype is a Java-based implementation of the WSAMI core middleware, which builds upon IEEE 802.11b as the underlying WLAN and integrates the following components:
  • The WSAMI SOAP-based core broker, including the CSOAP SOAP container for wireless, resource-constrained devices.
  • The Naming&Discovery service, including support for connector customization.
    The memory footprint of our CSOAP implementation is of 90KB, as opposed to the 1100KB of the Sun's reference implementation. The overall memory footprint of our Web services platform is of 3.9MB, dividing into 3MB for the CVM and 815KB for the Xerces XML parser, in addition to the CSOAP implementation.

    Content