Event-Based Data Management Stack for Wireless Sensor Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data management approaches in wireless sensor networks, such as those using relational database management systems, are not suitable for sensor nodes with limited resources like power, memory, or processing capability.

Innovation Solution

A wireless sensor network architecture that employs an event-based data management model with a data management stack comprising multiple layers, including an execution layer on each producer node to identify events of interest and transmit relevant data to consumer nodes, using a producer/consumer and publish/subscribe model to optimize data management and resource utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If relational database management systems are used for data management in wireless sensor networks, then data can be organized into tables with structured query capabilities, but the system becomes unsuitable for sensor nodes with limited resources such as power, memory, and processing capability

Engineering Contradiction:
Improvedata management capabilityVSAvoidpower consumption
Core Design Contradiction:
Ease of operationVSUse of energy by moving object

Solution Approach 1:

The data management system is segmented into multiple layers: the execution layer resides on resource-constrained sensor nodes to perform local event detection and filtering, while the query layer resides on the base station to handle complex query processing. This segmentation allows simple operations to be performed locally with minimal energy consumption, while complex operations are offloaded to the base station with adequate resources.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

An event-based intermediary mechanism is introduced where sensor nodes detect events locally and generate event notifications, which are then processed by the base station. This intermediary approach allows sensor nodes to avoid transmitting all raw data, instead only sending relevant event information, thereby reducing communication energy consumption and processing load on resource-constrained nodes.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If relational database management systems are used for data management in wireless sensor networks, then structured data organization and query mechanisms are available, but the complexity of the system increases making it unsuitable for resource-constrained sensor nodes

Engineering Contradiction:
Improvedata organization capabilityVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system is divided into two complexity zones: sensor nodes implement only the simple execution layer with event detection and filtering capabilities, while the base station implements the complex query layer with full query processing functionality. This segmentation allows sensor nodes to maintain low complexity suitable for resource constraints, while the base station handles the complex data management tasks.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Sensor nodes are equipped with self-service event detection and filtering capabilities that allow them to autonomously identify relevant events and generate notifications without requiring complex centralized processing. This self-service approach reduces the computational burden on sensor nodes while maintaining effective data management.

Inventive Principle:
Principle #25Self-service

3Loss of information

If all sensor data is transmitted to the base station for processing, then complete data availability is achieved, but energy consumption and network traffic increase significantly

Engineering Contradiction:
Improvedata completenessVSAvoidenergy consumption
Core Design Contradiction:
Loss of informationVSLoss of energy

Solution Approach 1:

The system extracts only the relevant information from sensor data by implementing event detection and filtering at the sensor node level. Instead of transmitting all raw sensor data, only events that meet specified criteria are extracted and transmitted to the base station, thereby maintaining data completeness for relevant information while significantly reducing energy consumption and network traffic.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Event detection and filtering operations are performed preliminarily at the sensor node before data transmission. This preliminary processing ensures that only relevant event data is transmitted to the base station, maintaining complete information availability for events of interest while minimizing energy consumption and network traffic by avoiding transmission of irrelevant data.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8027280B2Layered architecture for data management in a wireless sensor network
Publication Date: 2011.09.27 HONEYWELL INTERNATIONAL INC
  • US8027280B2 patent drawing
  • US8027280B2 patent drawing
  • US8027280B2 patent drawing

AI summary

A wireless sensor network comprises a plurality of nodes that communicate over wireless communication links. At least one of the plurality of nodes receives sensor data from a sensor. The wireless sensor network is queried by specifying a set of events of interest. For each event of interest included in the set of events of interest, a producer node included in the plurality of nodes identifies when that event of interest occurs and, when that event of interest occurs, transmits event data related to that event of interest to a consumer node included in the plurality of nodes. The wireless sensor network further comprises a data management stack that comprises a plurality of layers. The plurality of layers comprises an execution layer that executes on each producer node included in the plurality of nodes. For each event of interest included in the set of events of interest, the execution layer executing on the producer node for that event of interest identifies when that event of interest occurs.