Distributed Authentication Data Caching for Faster Face Recognition
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing face authentication systems face challenges with high misrecognition rates, slow response times, and data leak risks due to large volumes of authentication data, particularly when network dependency is high.
Innovation Solution
A system architecture with an origin node and multiple bottom nodes, allowing for localized caching and deletion of authentication data based on usage patterns and storage capacity thresholds, reducing the number of authentication data pieces and optimizing data management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all authentication data is stored in a central server, then data completeness is improved, but response time deteriorates due to network dependency
Solution Approach 1:
The patent divides the centralized authentication data storage into multiple distributed bottom nodes, each storing a portion of the authentication data. This segmentation allows local authentication operations without requiring network communication with the central server, thereby reducing response time while maintaining data completeness across the distributed system.
Solution Approach 2:
The patent introduces relay nodes as intermediaries between bottom nodes and the origin server. These relay nodes cache authentication data and manage data distribution, enabling bottom nodes to perform local authentication operations while maintaining connection to the central data source when needed, thus balancing response time and data completeness.
2Loss of time
If authentication data is cached at bottom nodes, then response time is improved, but data leak risk increases
Solution Approach 1:
The patent changes the state of cached data from authentic authentication data to dummy data that appears identical but contains no real information. This parameter change maintains the system's ability to perform fast local authentication operations while eliminating the security risk of storing sensitive authentication data at distributed bottom nodes.
Solution Approach 2:
The patent creates dummy data copies that mimic the structure and appearance of real authentication data. These dummy copies are stored at bottom nodes for local processing, allowing the system to maintain fast response times while the actual authentication data remains secure at the origin server.
3Object-affected harmful factors
If dummy data is used for caching, then data security is improved, but authentication accuracy may deteriorate
Solution Approach 1:
The patent implements a dynamic system where the origin server determines whether to provide real authentication data or dummy data to bottom nodes based on current security requirements and authentication needs. This dynamic approach allows the system to switch between security-focused mode (using dummy data) and accuracy-focused mode (using real data) as conditions change.
Solution Approach 2:
The patent establishes a feedback mechanism where the origin server monitors authentication performance and security requirements, then adjusts the provision of real versus dummy data to bottom nodes accordingly. This feedback loop ensures that authentication accuracy is maintained when needed while security is prioritized when required.
Data Source
AI summary
A system comprising an origin node having an origin storage unit storing a plurality of pieces of target-related data and a plurality of bottom nodes is provided, each of the plurality of bottom nodes has: a bottom storage unit which stores target-related data received from the origin node; a service provision unit which, if the target-related data corresponding to the provision target, which is the target to which the service is provided, is stored in the bottom storage unit, provides a service using the target-related data to the provision target; and if the target-related data corresponding to the target is not stored in the bottom storage unit and is stored in the origin node, provides a service using the target-related data stored in the origin node to the provision target and stores the target-related data in the bottom storage unit.