Token-Based Resource Allocation for Mobile Payment Privacy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing resource allocation methods, particularly in mobile payments, expose users to privacy risks as they often require sharing personal information, increasing the vulnerability of privacy breaches, especially in sporadic transactions between strangers.
Innovation Solution
A method and device for resource allocation that utilizes token information to determine resource information without directly sharing it, allowing for secure allocation without revealing private information, using a server to process and manage resource allocation information between clients, and employing identification codes like barcodes or QR codes for secure transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If mobile payment methods share registration information (member account, real name, portrait photo, mobile phone number) between payer and payee, then resource allocation can be realized, but privacy security deteriorates and vulnerability to privacy breaches increases
Solution Approach 1:
The patent introduces a server as an intermediary that mediates all information exchange between payer and payee. The server generates and manages mask codes that replace direct sharing of registration information. When resource allocation is needed, the server receives requests from both parties, processes them centrally, and only shares necessary information through the mask code mechanism, thus enabling resource allocation while protecting privacy security.
Solution Approach 2:
The patent creates mask codes as simplified copies or representations of the actual registration information. Instead of sharing sensitive data like real names and portrait photos, the system uses these mask codes (which are easier to share and verify) as substitutes. The mask codes contain enough information to identify and verify parties involved in resource allocation but do not expose the underlying sensitive registration information.
2Productivity
If registration information is shared between parties for resource allocation, then transactions can be processed, but information security deteriorates especially in sporadic transactions between strangers
Solution Approach 1:
The server acts as a trusted intermediary that processes all transaction information. It generates mask codes that enable transaction processing without requiring direct exposure of sensitive registration information between parties. The server validates and processes resource allocation requests while maintaining information security, thus ensuring transaction productivity without increasing privacy breach risk.
Solution Approach 2:
The patent extracts only the essential identifying information needed for resource allocation into mask codes, separating it from the full registration information. This extraction allows transactions to be processed using only the necessary minimal information, while the remaining sensitive data stays protected on the server side and is not shared between parties.
3Ease of operation
If direct information sharing is used for resource allocation, then allocation can be realized, but the complexity of information management increases and privacy protection becomes difficult
Solution Approach 1:
The server as intermediary centralizes information management, taking on the complexity of managing registration information and mask code generation. This relieves the parties involved in resource allocation from having to directly manage and secure sensitive information exchanges. The server handles the complex tasks of information validation, mask code generation, and secure transmission, making the allocation process easier to implement while reducing information management complexity for the users.
Data Source
AI summary
Methods, systems, and apparatus, including computer programs encoded on computer storage media, for allocating resources are provided. One of the methods includes receiving a first request from a first client for accessing a server, wherein the first request includes token information corresponding to resource information of a second client; determining, according to the token information included in the first request, the resource information of the second client corresponding to the token information; receiving resource allocation information from the first client; and allocating resource according to the resource allocation information from the first client and the resource information of the second client.