On-Device Transaction Tags for Private Record Search
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing transaction record systems on client devices have limited search and filtering capabilities due to a small number of fields, resulting in inefficient and bandwidth-intensive searches.
Innovation Solution
A system that generates transaction tags on-device based on transaction characteristics, enabling efficient and secure on-device search and filtering of transaction records using predefined search queries and indexes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional search methods using limited transaction fields are used, then implementation is simple, but search effectiveness and filtering capability are poor
Solution Approach 1:
The system performs preliminary action by automatically generating and storing search indexes and transaction tags before search operations occur. Transaction records are pre-processed to extract characteristics and generate descriptive tags, which are stored in an index structure. This allows the search function to quickly retrieve relevant transactions without performing complex analysis during the actual search, thereby improving search effectiveness while maintaining implementation simplicity.
2Reliability
If cloud-based search processing is used, then comprehensive transaction data can be searched, but bandwidth consumption and processing costs increase
Solution Approach 1:
The system extracts the essential search functionality from the cloud environment and implements it locally on the user device. By generating and storing transaction indexes and tags locally, the device can perform search operations independently without continuously communicating with remote servers. This extraction of core search capabilities to the local device reduces bandwidth consumption and processing costs while maintaining search completeness for the user's transaction data.
3Extent of automation
If transaction data is processed on the server, then centralized control is maintained, but user privacy and data security are compromised
Solution Approach 1:
The system segments the transaction processing architecture by separating data storage and index generation (performed locally on user devices) from optional centralized services. Each user device independently generates and stores its own transaction indexes and tags, maintaining data locality and user privacy. Centralized servers can provide auxiliary services without accessing or processing the actual transaction data, thus maintaining centralized control for service coordination while eliminating privacy risks associated with centralized data processing.
Data Source
AI summary
Transaction data that represents transactions may be associated with one or more generated tags based on characteristics associated with the transactions. A set of suggested payment amounts for paying an account balance may be determined based on the tagged transactions. Information about at least one suggested payment amount may be presented at a user device.