An Energy-Aware Middleware for Integrating Wireless Sensor Networks and the Internet

Abstract

Wireless sensor networks (WSNs) have great potential for many distributed applications in different scenarios. As they grow in popularity and importance, it becomes increasingly desirable and necessary to share their data over the Internet. This paper presents an energy-aware middleware that focuses on integrating the Internet and WSNs at service level by providing transparency of access, location, and technology. In particular, it describes and evaluates the implemented strategies to reduce the energy consumption, which are essential for prolonging the WSN lifetime.

A Framework for Integrating Wireless Sensor Networks and the Internet

“…For that purpose, WISeMid provides an infrastructure that allows integrating these services in such a transparent manner that services provided by both WSN nodes or Internet hosts are accessed the same way. Moreover, WISeMid implements the following mechanisms for saving energy in WSNs [9]: Aggregation service, which aggregates the last n data sensed by a node; Reply Storage Timeout, which avoids sending equivalent messages to the sensor nodes while the last sensed data is still considered up-to-date; Automatic Type Conversion, which removes unnecessary bytes from the messages; and the implementation of asynchronous invocation patterns, which prevents the sensor application from wasting power for being blocked during a service request.…”

“…Property values are defined in properties clauses (8)(9)(10), which are related to the service type that specified the property type (8). Every property type defined as MANDATORY or MANDATORY_READ_ONLY in the service type must have a property value associated to its name in the properties clause (9).…”

“…Every property type defined as MANDATORY or MANDATORY_READ_ONLY in the service type must have a property value associated to its name in the properties clause (9). Specifying a value for property types of other modes is optional.…”

“…The first two patterns are used for one-way operations, while the last ones are used for request-response operations. Details on WISeMid implementation of those patterns can be found in [9].…”

“…Then, this variable is copied to a partner link (8)(9)(10)(11). Finally, the invocation to the updated partner link is done (12).…”