Autonomous Heritage Rule Access for Secure Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current solutions for managing access to secure data after a user's disappearance require intermediaries, such as server managers or notaries, and do not allow heirs to have personalized access without freezing the user's data.
Innovation Solution
A process and device for managing secure data access that includes storing heritage rules and authentication data for designated heirs, enabling them to access the data without intermediaries, using biometric data or motion capture-based rules to satisfy access conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If existing solutions (Locasto, WO2007/10427, commemoration accounts) are used to manage access after user disappearance, then access control is provided, but intermediaries (server managers, notaries, administration) are required and data access is frozen or restricted
Solution Approach 1:
The patent extracts the intermediary function from the system by implementing a heritage rule mechanism that operates autonomously within the existing access management system. The heritage rule, stored in the user's profile, enables direct heir authentication and data access without requiring external intermediaries like notaries or server managers to intervene in the access process.
Solution Approach 2:
The patent applies preliminary action by having users pre-configure their heritage rules and heir lists before disappearance. The system stores authentication data for designated heirs and access rules in advance, so that when the user disappears, the heirs can immediately authenticate and access data without needing to contact intermediaries or go through complex procedures.
2Reliability
If commemoration account structure is used, then data freezing is achieved for protection, but personalized access and administration by heirs is prevented
Solution Approach 1:
The patent applies local quality by implementing differentiated access rights for different heirs based on the user's specific heritage rules. Each heir in the list can have customized authentication requirements and data access permissions defined in their corresponding access rules, allowing personalized control over which heirs access which data under which conditions, rather than uniform freezing or access.
Solution Approach 2:
The patent implements dynamics by making the heritage rule satisfaction conditions configurable and adaptable. The system can require different authentication scenarios (single heir, multiple heirs, specific time periods, motion capture patterns) depending on what the user configured, allowing the access control to dynamically adapt to different heir situations while maintaining security.
3Extent of automation
If heritage rules with authentication data storage are implemented, then direct heir access is enabled, but system security requirements increase
Solution Approach 1:
The patent applies universality by using the existing access management system's authentication infrastructure to handle heritage access. The system reuses existing authentication mechanisms (biometric data, motion capture patterns, device identifiers) already deployed for user login, rather than creating separate authentication systems. This allows automated heir access management while leveraging existing security capabilities.
Solution Approach 2:
The patent applies copying by storing authentication data for heirs in their profile records within the existing database structure. Rather than creating separate secure storage systems, the system copies and stores heir authentication data (biometric templates, device identifiers) within the user profile, utilizing the existing database and authentication verification processes to validate heir identities.
Data Source
AI summary
A management process for access to secure data includes: storing secure data associated with a first user and authentication data of said first user, managing access to the secure data of the first user, as a function of the authentication data of this first user. The process includes: storing, in the secure data of the first user, a heritage rule and a list of at least one second user and, for each second user of said list, an rule for access to secure data of the first user, storing authentication data for each second user of said list, and when the heritage rule is satisfied, managing access, by said at least one second user, to the secure data of the first user, as a function of the authentication data of the second user and of the rule for access of the second user.