Distributed Event Data Management in Access Control Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Access control systems face challenges in managing large volumes of event data, leading to potential memory overflow and network traffic overload, especially during busy periods, without a central server to maintain a complete set of event data.
Innovation Solution
Implementing a distributed system with each controller having two memory areas for event data storage, where one area is larger for local data and another is smaller for data from other controllers, with processors managing data distribution and removal based on memory space, network traffic, and subscription priorities, allowing for decentralized data management and reduced load during busy times.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If event data is stored in a single central server, then complete event data can be maintained, but memory overflow and network traffic overload occur during busy periods
Solution Approach 1:
The patent divides the centralized event data storage into multiple distributed controllers, each maintaining a portion of the event data. Each controller has its own memory space for storing event data, eliminating the single point of failure and overload issues associated with a central server while maintaining complete system-wide event data coverage.
Solution Approach 2:
The patent transitions from a single-dimension centralized storage model to a multi-dimensional distributed storage model across multiple controllers. This dimensional shift allows event data to be replicated and distributed across the network, reducing the load on any single device while maintaining data completeness through cross-controller availability.
2Reliability
If all controllers store complete event data from all devices, then data completeness is achieved, but memory space requirements increase significantly
Solution Approach 1:
The patent implements local quality by allowing each controller to store event data based on its specific needs and capabilities. Controllers store event data locally in their own memory spaces rather than duplicating complete data sets, with each controller maintaining appropriate portions of event data relevant to its function and the events it generates or monitors.
Solution Approach 2:
The patent uses selective copying where controllers replicate only the necessary portions of event data from other controllers rather than maintaining complete copies. This allows data completeness to be achieved through strategic replication of specific event data sets across multiple controllers, reducing overall memory consumption while maintaining accessibility.
3Reliability
If event data is distributed across multiple controllers, then memory overflow is prevented, but network traffic increases due to data distribution and synchronization
Solution Approach 1:
The patent applies preliminary action by pre-establishing data distribution rules and subscription relationships between controllers before event data needs to be shared. Controllers proactively distribute event data to subscribed controllers based on predefined criteria, avoiding the need for continuous query-response cycles and reducing real-time network traffic overhead.
Solution Approach 2:
The patent implements feedback mechanisms where controllers monitor their own memory usage and network conditions, adjusting their data distribution and reception behavior accordingly. When a controller's memory is sufficient, it can accept more distributed data; when memory is constrained or network traffic is high, it can reduce data reception, creating a self-regulating system that minimizes network overhead.
4Ease of operation
If a central server is used to manage event data, then data distribution is simplified, but the system becomes vulnerable to single points of failure
Solution Approach 1:
The patent merges the data distribution management functions across multiple controllers rather than relying on a single central server. Each controller participates in both generating and receiving event data, creating a distributed management model where no single point of failure exists. The system combines the capabilities of multiple controllers to achieve the collective function of centralized management with the reliability of distributed architecture.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
A method disclosed may include storing event data in a physical access control system (110) originating from a first device of a plurality of security devices in a first data area (369) of a memory (350). The method may include storing event data originating from devices other than the first device in a second data area (368). The method may include removing the event data from the first data area (369) to prevent the first data area from occupying more than a first memory space and removing the event data from the second data area (368) to prevent the second data area (368) from occupying more than a second memory space. The method may include distributing the event data from the first data area (369) to the other devices through a network interface (218).