Multi-Sector Credential Data Structure for Access Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Access control systems face limitations due to the need for different credentials for various lock types, which complicates access authorization and management, especially when multiple lock types with distinct privilege databases are involved.
Innovation Solution
A credential system with a multi-access permission data structure that stores permissions in a structured format, allowing different locks and readers to access specific portions of the data, authenticated through a centralized or local database, enabling secure and efficient access control across multiple lock types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If different credential types are used for different lock types, then access authorization can be tailored to specific lock database types, but system complexity increases and user convenience deteriorates
Solution Approach 1:
The patent implements a universal credential data structure that can interface with multiple lock database types (HID, Motorola, SIEMENS, etc.) through a standardized format. The credential contains organized data fields that can be mapped to different database types, allowing a single credential type to work across diverse lock systems without compromising authorization accuracy.
Solution Approach 2:
The credential data structure is segmented into distinct fields (user ID, access rights, timestamps, etc.) that can be selectively accessed and mapped to different database types. This segmentation allows the system to present only the relevant portion of the credential data to each specific lock type, maintaining compatibility while reducing overall complexity.
2Reliability
If multiple credential types are required for different lock types, then specific database compatibility is achieved, but ease of operation deteriorates due to managing multiple credentials
Solution Approach 1:
The system employs a universal credential format that maintains compatibility with multiple database types (HID, Motorola, SIEMENS, ASSA ABLOY, LIXIL) through standardized data fields. Users carry a single credential type that can be read by various lock readers, eliminating the need to manage multiple credential types while preserving database-specific compatibility through field mapping.
Solution Approach 2:
The patent introduces a standardized credential data structure as an intermediary between the user and diverse lock database types. This intermediate format contains all necessary information to interface with any specific database type, acting as a universal translator that simplifies user interaction while maintaining backend compatibility.
3Ease of operation
If a single credential supports multiple lock types, then ease of operation improves, but the credential must accommodate multiple database types which increases data structure complexity
Solution Approach 1:
The credential data structure is organized into segmented, hierarchical fields (basic user information, access rights, temporal constraints, etc.) that can be independently accessed and mapped to different database types. This segmentation manages complexity by allowing the system to retrieve only the necessary subset of data for each specific lock type interaction.
Solution Approach 2:
Different portions of the credential data structure are optimized for different database types. The credential contains localized data fields that can be selectively activated or mapped depending on which lock type is being accessed, allowing each section of the data structure to serve its specific purpose without requiring the entire structure to be optimized for all scenarios.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A credential for use in an access control system may include a first sector including first data of a first database type, and a second sector including second data of a second database type. The credential may further include a third sector including third data related to the second data. The first database type and the second database type may be different types.