Mobile Attendance Tracking via One-Time Code Tuples
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional attendance tracking methods fail to accurately record user presence over time and may compromise security features, as they do not guarantee attendance at events beyond initial check-in and can be costly to implement.
Innovation Solution
A system that uses a user device with a QR code reader function to create and log data tuples comprising a one-time code, current time, and user identifier, which are stored in a database, ensuring accurate attendance tracking by generating unique codes that change frequently to prevent mismatches and validate user presence throughout an event.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If smartcard readers are installed at various locations throughout a building facility to identify user presence, then attendance tracking reliability is improved, but device complexity and installation cost increase
Solution Approach 1:
The patent uses digital copies of user credentials (one-time codes) transmitted via mobile devices instead of physical smartcard readers at every location. The system creates virtual replicas of access control functionality that can be shared across multiple locations without installing physical hardware at each site, thereby reducing system complexity while maintaining reliability.
Solution Approach 2:
The mobile device serves multiple functions: it acts as both the user's personal identifier and the access control credential. The same device that communicates user presence to the server also validates against one-time codes, eliminating the need for separate dedicated readers at each location and reducing overall system complexity.
2Ease of operation
If conventional check-in methods are used at meeting tables or manual entry points, then ease of operation is improved, but measurement precision of user presence deteriorates
Solution Approach 1:
The system implements continuous feedback loops where the mobile device constantly communicates with the server to validate presence. The one-time codes change frequently and the system provides real-time feedback on whether the user is properly authenticated and present, enabling precise measurement of actual attendance rather than relying on manual check-in alone.
Solution Approach 2:
The patent maintains continuous monitoring and validation of user presence throughout the event duration. Rather than a single check-in moment, the system continuously verifies presence through ongoing communication between the mobile device and server, ensuring accurate measurement of actual attendance while keeping the user experience simple.
3Reliability
If one-time codes change frequently to prevent mismatches, then security is improved, but device complexity increases
Solution Approach 1:
The mobile device automatically generates, stores, and manages its own one-time codes without user intervention. The code generation and validation processes are handled autonomously by the device and server, eliminating the need for manual code distribution or management. This self-service approach maintains high security through frequent code changes while keeping the user experience simple.
Solution Approach 2:
The system pre-generates and stores one-time codes in the mobile device before the event begins. These codes are ready for immediate use and validation, eliminating the need for real-time code generation or complex management during the event. The preliminary preparation of security credentials simplifies the overall system operation while maintaining security.
Data Source
AI summary
One example method of operation may include receiving an access attempt from a user device, retrieving a user identifier associated with the user device stored in a database, creating a data tuple having three or more data elements based on the access attempt from the user device, storing the data tuple in the database, the data tuple includes at least a one-time code generated by an access device, a current time and the user identifier, and logging a successful access attempt by the user device when the user identifier is identified as being part of a list of user identifiers.