Entity Record Linking with Segregated Session Caches
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing registration systems face issues with duplicate entity and login record creation, leading to database clutter and security risks, as users often forget or lose credentials, resulting in multiple registrations and potential exposure of sensitive information.
Innovation Solution
A computer-implemented method that processes record creation requests with a login key, including a primary identifier and password, to identify and update a single entity record, while segregating session data using cache files, allowing multiple logins with different credentials to access distinct data, thus maintaining security and privacy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users are allowed to register multiple times with different credentials, then user versatility and privacy are improved, but duplicate records and database clutter increase
Solution Approach 1:
The patent segments data storage into two distinct layers: a single entity record in the main database containing only essential identification information, and multiple segregated session data caches stored separately. Each cache is associated with a specific credential set but physically separated from other credentials' data. This segmentation allows multiple login credentials to be linked to one entity without creating duplicate entity records, thereby maintaining user privacy while preventing database clutter.
2Reliability
If session data is segregated using cache files for each login key, then data security is improved, but system complexity increases
Solution Approach 1:
The patent introduces session data caches as intermediary storage layers between the entity record and the credential authentication process. These caches act as mediators that hold credential-specific data temporarily during login sessions without requiring permanent storage in the main database. The caches are automatically created, populated, and destroyed based on session needs, providing security isolation without permanently complicating the database structure. This intermediary approach enables secure credential segregation while maintaining relative system simplicity through automated cache management.
Data Source
AI summary
A method for resolving ambiguity in computer data includes processing a record creation request transmitted from a computing device. The record creation request includes entity creation data and a login key. The login key includes a primary identifier and a password. The method also includes executing a matching algorithm with a selectable combination of the entity creation data at an entity database to identify a single entity record matching a selectable combination of the record creation request. The single entity record is linked to multiple different login keys. The method also includes updating one or more attributes of the single entity record with the entity creation data. Further, the method includes storing session data created during a session associated with the login key by using the login key to segregate the session data in the entity database, and linking the session data to the single entity record.