Token Embedded Data Directive Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems for managing data access are inefficient and insecure, as they require numerous database and API calls, consume significant resources, and pose security risks due to the need for intermediary entities to store and manage large amounts of data, leading to processing delays and potential data breaches.
Innovation Solution
The system generates a token with an embedded data directive for a data recipient, allowing for direct filtering of user information without referencing external databases, and associates separate network resources with each data provider to enhance security and scalability, reducing the burden on intermediary entities and improving data processing efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If an intermediary entity stores and manages large amounts of user data to enable data access, then data access control is achieved, but security risks increase and resource consumption increases
Solution Approach 1:
The patent extracts the filtering logic from external databases and embeds it directly into the token structure. The data directive containing filtering instructions is now part of the token itself, eliminating the need for the intermediary entity to store large amounts of user data in external databases, thereby reducing security risks associated with data storage while maintaining access control capabilities
Solution Approach 2:
The patent creates a copy of the filtering instructions and embeds them within the token structure. Instead of referencing external databases during data filtering, the system uses the embedded data directive copy within the token to perform filtering operations, reducing the need for the intermediary entity to maintain large external data stores
2Reliability
If an intermediary entity stores and manages large amounts of user data to enable data access, then data access control is achieved, but resource consumption increases
Solution Approach 1:
The patent extracts filtering instructions from external storage and embeds them within the token structure. This eliminates the need for the intermediary entity to load and process large amounts of data from external databases during each access operation, significantly reducing computational resources and energy consumption while maintaining data access control
Solution Approach 2:
The patent performs preliminary action by embedding the data directive with filtering instructions into the token before the actual data access occurs. This pre-packaging of filtering logic eliminates the need for repeated database queries and data processing during each access operation, reducing resource consumption
3Ease of operation
If numerous database and API calls are made to process data requests, then data access is enabled, but processing delays increase
Solution Approach 1:
The patent merges the filtering instructions directly into the token structure, combining what were previously separate operations (token validation and filtering instructions retrieval) into a single embedded structure. This eliminates multiple database and API calls, reducing processing delays while maintaining data access functionality
Solution Approach 2:
The patent performs preliminary action by embedding the data directive with filtering instructions into the token before data access occurs. This pre-packaging eliminates the need for subsequent database queries and API calls during the actual data processing operation, significantly reducing processing delays
4Ease of operation
If tokens reference external databases for filtering instructions, then data filtering is enabled, but data security decreases and processing efficiency decreases
Solution Approach 1:
The patent extracts filtering instructions from external databases and embeds them directly within the token structure. This eliminates the security vulnerability of referencing external databases during data processing, as all necessary filtering information is now self-contained within the immutable token, improving data security while maintaining filtering functionality
Solution Approach 2:
The patent creates an embedded copy of the filtering instructions within the token structure. This copy eliminates the need to reference external databases during data processing, improving both security (by removing external references) and efficiency (by having immediate access to filtering rules)
Data Source
AI summary
Systems and methods are described for generating, at an intermediary entity, a first data recipient token for a data recipient for accessing data from a first data provider, and associating a first network resource with the first data provider, wherein the first network resource is used by the data recipient to request data from the first data provider. The systems and methods may generate, at the intermediary entity, a second data recipient token for the data recipient for accessing data from a second data provider, and associate a second network resource with the second data provider, wherein the second network resource is used by the data recipient to request data from the second data provider.