Time-Based Lock Code Resynchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems lack an efficient method for managing access rights and associated access credentials over multiple remotely deployed locks and multiple personnel, where personnel and access rights change frequently.
Innovation Solution
An access-control system utilizing an access management server, locks, and time-based codes, where the lock adjusts its clock to resync with the server clock if a temporally proximate time-based code matches, and implements 'soft matching' by allowing input codes to match either current or proximate time-based codes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If time-based codes are used for access control with multiple personnel and locks, then access management efficiency is improved, but clock synchronization issues arise between locks and server
Solution Approach 1:
The system performs preliminary clock synchronization by checking for temporally proximate time-based codes and adjusting the lock clock before access operations occur. This preventive approach ensures that clocks remain synchronized without requiring continuous real-time adjustment during access events.
Solution Approach 2:
The system implements feedback mechanisms where the lock continuously monitors time-based code validity and automatically adjusts its clock when discrepancies are detected. The soft matching feature provides feedback tolerance by accepting codes within a temporal window, allowing the system to self-correct synchronization drift.
2Reliability
If strict time-based code matching is implemented, then security is improved, but access failures occur due to clock drift
Solution Approach 1:
The system applies partial matching by accepting time-based codes that are temporally proximate rather than requiring exact time matches. This soft matching approach provides a tolerance window that accommodates clock drift while maintaining security, allowing access even when timestamps are slightly off.
Solution Approach 2:
The system changes the matching parameter from exact time equality to temporal proximity threshold. By defining an acceptable time window for code validation, the system maintains security requirements while accommodating real-world clock variations and drift.
3Reliability
If clock adjustment features are added to locks, then synchronization reliability is improved, but device complexity increases
Solution Approach 1:
The lock performs self-service clock synchronization by automatically detecting temporal mismatches in time-based codes and adjusting its own clock without external intervention. This autonomous operation maintains synchronization reliability while minimizing the need for complex external synchronization infrastructure.
Solution Approach 2:
The system changes the operational parameter from static time-based code validation to dynamic adjustment based on temporal proximity detection. This allows the lock to adapt its timing parameters automatically, maintaining reliability without requiring complex manual configuration or external control systems.
Data Source
AI summary
An access-control system comprises using an access management server, a lock, and time-based codes. When a time-based code from the access management server does not match the time-based code computed by the lock, the lock may check temporally proximate time-based codes. Upon a determination that a temporally proximate time-based code matches, the lock may adjust its clock to re-sync with the access management server clock. Additionally, the lock may implement “soft matching” by determining that an input code is a match if it matches either a current or a proximate time-based code. Additionally, the access management server and lock may implement multiple parallel time-based code instances to facilitate additional functionality.