Untethered Access Code for Secure Resource Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy electronic resource distribution systems lack adaptability to new functionalities, making it difficult for users to transfer funds or resources securely and conveniently, as resources are often tied to a specific user's identity and require authentication for access.
Innovation Solution
A system that generates a code untethering resources from an account, allowing any party with possession of the code to complete transactions, with the service provider obtaining authorization and ensuring the transaction complies with specified constraints, enabling secure and convenient transfer of funds or resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If resources are tethered to a specific user's identity in legacy systems, then security and authentication are maintained, but adaptability and ease of transfer are limited
Solution Approach 1:
The patent segments the resource access mechanism by introducing a separate code element that can be independently transferred from the account holder to the recipient. This code acts as a detachable token that carries resource access rights without being tied to the original account holder's identity, enabling flexible transfer while maintaining security through constraint-based control.
Solution Approach 2:
The access code serves as an intermediary between the account holder and the resource. Instead of directly transferring account access or requiring continuous authentication, the code mediates the transfer by encoding access rights and constraints, allowing the recipient to access resources without direct authentication to the account holder.
2Reliability
If authentication is required for resource access in legacy systems, then security is maintained, but convenience and speed of transaction are reduced
Solution Approach 1:
The system performs preliminary action by pre-establishing and encoding access constraints within the code itself before the transaction occurs. The code contains embedded instructions that define what resources can be accessed, under what conditions, and what limitations apply, eliminating the need for real-time authentication and constraint verification during the actual transaction.
Solution Approach 2:
The access code is designed to be self-contained with embedded authentication and constraint logic. The code itself carries the necessary information to validate access rights and enforce constraints without requiring external authentication systems, making the transaction process autonomous and faster.
3Adaptability or versatility
If legacy resource provider systems are used, then system compatibility is maintained, but functionality and adaptability to new features are limited
Solution Approach 1:
The access code is designed with universal compatibility, working across different resource provider systems and platforms. The code format and constraint structure are standardized, allowing the same code to be used for various resource types (digital content, physical goods, services) and across different provider infrastructures without requiring system-specific customization.
Solution Approach 2:
The system handles adaptability through parameter changes in the code structure and constraints rather than changing the fundamental system architecture. The code can encode different resource types, access levels, and constraints by varying parameters within the same overall framework, allowing legacy systems to support new functionalities through software updates rather than hardware changes.
Data Source
AI summary
A method is disclosed. The method includes receiving, at a computing system, from a user, a request for an access code and one or more constraints on a use of the access code, and identifying a portable device to be associated with the access code. The method also includes obtaining, using the portable device, authorization for one or more potential interactions using the access code. Upon obtaining authorization for the one or more interactions, the method includes generating the access code, which includes an identifier that causes an access request that includes the access code be routed to the computing system. The method also includes receiving, from an access device, an access request comprising the access code in an interaction. Upon determining that the interaction complies with the one or more transaction constraints, the computing system provides an indication to the access device that the interaction is authorized.