Dynamic User Attribute Storage Eliminating Empty Fields
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data storage methods for user personal attributes result in a large number of empty fields, leading to inefficient storage space usage and the need for frequent table locking, which hampers the provision of accurate services due to the time-consuming process of adding new fields for varying user needs.
Innovation Solution
A data processing method that dynamically allocates storage fields based on user identifiers and attribute values, allowing multiple attribute correspondences to be stored in a single field, and creates new fields as needed, eliminating empty spaces and avoiding the need for table locking.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If a fixed table structure with pre-defined fields is used to store user personal attributes, then data retrieval is simple and direct, but storage space is wasted due to numerous empty fields when user attributes vary significantly
Solution Approach 1:
The patent segments the fixed table structure into user-specific attribute groups. Instead of one large table with all possible attributes, each user's attributes are stored as separate records containing only their actual attributes. This segmentation eliminates empty fields while maintaining data organization.
Solution Approach 2:
The patent transitions from a static fixed-table structure to a dynamic record-based structure where each user's attributes are stored flexibly according to their actual needs. The system dynamically allocates storage space based on individual user attribute requirements rather than pre-allocating for all possible attributes.
2Adaptability or versatility
If new attribute fields are added to accommodate varying user needs, then the system becomes more adaptable to different user requirements, but table locking is required which slows down service provision
Solution Approach 1:
The patent implements a dynamic attribute storage system where each user's attributes are stored as independent records. When new attributes need to be added, the system simply creates new attribute records for affected users without requiring table-wide locking. This dynamic approach maintains adaptability while eliminating the productivity bottleneck caused by table locking.
Solution Approach 2:
The patent prepares the data structure in advance to accommodate varying attributes by using a flexible record format. Each user record can independently contain different attributes without requiring pre-definition of all possible attributes across the system, enabling rapid adaptation to new user needs.
3Reliability
If all possible user attributes are collected and stored in advance, then comprehensive service provisioning is enabled, but the number of empty fields increases when users have different attribute sets
Solution Approach 1:
The patent extracts only the necessary attributes for each individual user from the complete set of possible attributes. Instead of storing all possible attributes for every user, the system extracts and stores only the attributes that each user actually possesses, eliminating redundant empty field storage while maintaining service accuracy.
Solution Approach 2:
The patent applies local quality by allowing different users to have different attribute sets tailored to their specific needs. Each user record contains attributes relevant to that particular user, rather than enforcing a uniform attribute structure across all users. This local customization reduces overall data volume while maintaining comprehensive service capability.
Data Source
AI summary
A user identifier is obtained and an attribute identifier and an attribute value of at least one personal attribute corresponding to the user identifier is obtained. A target attribute correspondence to each personal attribute of the at least one personal attribute is generated based on the attribute identifier and the attribute value of the personal attribute. A determination is performed as to whether a target attribute storage field corresponding to the user identifier exists in stored first correspondences between one or more user identifiers and one or more attribute storage fields. When the target attribute storage field exists in the stored first correspondences, the target attribute correspondences are stored in the target attribute storage field.