Sensor Network Event Collection via Distributed Module Installation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing sensor network systems face challenges in managing network traffic and responding to changes in sensor network topology, leading to increased network traffic and load concentration on server nodes.
Innovation Solution
An event collection method that involves storing module definition information, collecting and categorizing event information, and determining the optimal installation destination for modules within the sensor network based on topology and attribute matching, allowing for distributed installation of modules across lower nodes to reduce traffic and load.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If all events are collected at the server node, then event processing can be centralized, but network bandwidth becomes tight and server node load increases
Solution Approach 1:
The patent divides the centralized event processing function into distributed segments by installing modules at intermediate nodes. These modules filter and aggregate events locally, segmenting the data flow so that only processed events reach the server node, thereby reducing network traffic while maintaining centralized processing capability through modular distribution
Solution Approach 2:
The patent introduces intermediate nodes as mediators between sensor nodes and the server node. These intermediate nodes execute filtering and aggregation modules, acting as intermediaries that process events before they reach the server, thus reducing the volume of data transmitted over the network while preserving the ability to perform comprehensive event processing
2Quantity of substance
If modules are installed at lower nodes to reduce traffic, then network load decreases, but system complexity increases due to distributed module management
Solution Approach 1:
The patent implements a universal module management mechanism where the server node maintains a module definition database that can be applied across multiple intermediate nodes. This multi-functional approach allows the same filtering and aggregation logic to be deployed consistently throughout the network, reducing management complexity despite the distributed architecture
Solution Approach 2:
The patent performs preliminary action by pre-defining module parameters and filtering criteria in the module definition database at the server node before events need processing. This preliminary configuration allows intermediate nodes to execute complex filtering operations locally without requiring real-time centralized control, simplifying distributed management while reducing network traffic
3Power
If events are filtered and aggregated at intermediate nodes, then server node load decreases, but event processing delay increases
Solution Approach 1:
The patent segments the event processing function across multiple levels: local filtering at sensor nodes, aggregation at intermediate nodes, and final processing at the server node. This segmentation allows time-sensitive filtering to occur close to the data source while preserving the ability to perform comprehensive analysis at the server, balancing processing capacity with acceptable delay
Solution Approach 2:
The patent applies local quality by implementing filtering and aggregation operations with different characteristics at different levels of the network. Intermediate nodes perform aggregation operations that combine data from multiple sensor nodes, while the server node performs final processing. This local differentiation optimizes processing capacity at each level while managing end-to-end delay through hierarchical processing
Data Source
AI summary
An event collection method collects an event from a sensor network, the method includes: retrieving on a per process basis for a module, based on a module definition information and an occurred event information, an occurrence node identifier categorized by an attribute value corresponding to an attribute name, with input event type associated with an occurred event type; determining, when there is a single retrieved occurrence node identifier with respect to the process of the module, a node identified by the occurrence node identifier as an installation destination of the module that is identified by the module identifier; referencing, when there is a plurality of retrieved occurrence node identifiers with respect to the process of the module, a connection relation information of nodes and determining an upper node common to the plurality of occurrence node identifiers as an installation destination of the module identified by the module identifier.