Blank 01

Architecture Overview
MassWare (Mobile Ad-hoc and Sensor Systems' Middleware) is an extension of AwareWare to wireless mobile networks and sensor networks, where network and hardware resources are extremely constraint and dynamic. The MassWare mobile system can reduce the reconfiguration time in context-aware mobile environments. It is located between the lower hardware and network layer and the upper application layer to monitor environments and support application adaptation. MassWare is peer-to-peer middleware and there is one middleware agent per application in each host. There are five parts in each MARCHES agent: measurement tools, event sensors based on a hierarchical event model, a script parser based on XML, a decision engine, and a dynamic reconfigurator. Measurement tools are the lowest building blocks that monitor the heterogeneous environments and report the environment awareness results as the contextual information to be processed by the event sensors. The sensors and actuators, in addition to adaptation rules, are defined by application developers in a XML script file. There are two types of actuators, proactive and reactive ones. The XML script parser parses the script file and constructs the sensors and proactive actuators to process local data. The reactive actuators are constructed through a synchronization process with peer agents to process the received data. Once a context triggers an event sensor, a corresponding proactive actuator will be activated. In the operation layer, various services are offered by software components that implement specific algorithms and protocols. There are two types of components in the operation layer: functional components (called masslets) for performing vehicle communication and control, and context-awareness components (called masstools) for measuring and evaluating situational contexts. Because we focus on improving the vehicle middleware efficiency in this research, we do not include such nonfunctional components as the concurrency and security etc. and their reconfiguration, which are potentially supported by MassWare

Architecture Overview

MassWare (Mobile Ad-hoc and Sensor Systems' Middleware) is an extension of AwareWare to wireless mobile networks and sensor networks, where network and hardware resources are extremely constraint and dynamic. The MassWare mobile system can reduce the reconfiguration time in context-aware mobile environments. It is located between the lower hardware and network layer and the upper application layer to monitor environments and support application adaptation. MassWare is peer-to-peer middleware and there is one middleware agent per application in each host. There are five parts in each MARCHES agent: measurement tools, event sensors based on a hierarchical event model, a script parser based on XML, a decision engine, and a dynamic reconfigurator.

Measurement tools are the lowest building blocks that monitor the heterogeneous environments and report the environment awareness results as the contextual information to be processed by the event sensors. The sensors and actuators, in addition to adaptation rules, are defined by application developers in a XML script file. There are two types of actuators, proactive and reactive ones. The XML script parser parses the script file and constructs the sensors and proactive actuators to process local data. The reactive actuators are constructed through a synchronization process with peer agents to process the received data. Once a context triggers an event sensor, a corresponding proactive actuator will be activated.

In the operation layer, various services are offered by software components that implement specific algorithms and protocols. There are two types of components in the operation layer: functional components (called masslets) for performing vehicle communication and control, and context-awareness components (called masstools) for measuring and evaluating situational contexts. Because we focus on improving the vehicle middleware efficiency in this research, we do not include such nonfunctional components as the concurrency and security etc. and their reconfiguration, which are potentially supported by MassWare