Remote Database Value Transfer via API Identifier Disassociation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing transaction processing systems for remote databases lack efficient mechanisms to transfer values securely and reliably without requiring transaction or locking semantics, particularly in scenarios involving stored value cards, where preventing modification by the originating entity is crucial.
Innovation Solution
A computer system and method that utilize a remote database API to identify and employ an appropriate application programming interface (API) to transfer a value from one entity to another, ensuring atomicity by disassociating the value from the originating entity's identifiers and associating it with new identifiers unknown to that entity, thereby preventing modification and facilitating a corresponding transfer of a second value.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional transaction processing mechanisms are used to transfer values in remote databases, then reliability of value transfer is improved, but device complexity increases due to requiring transaction or locking semantics
Solution Approach 1:
The patent extracts the value transfer mechanism from the complex transaction processing infrastructure. Instead of using full transaction semantics with locking mechanisms, the invention uses a simple API call to transfer values between database entries. The value is disassociated from the originating entity's identifiers and associated with new identifiers unknown to that entity, achieving reliable transfer without the overhead of transaction management systems.
Solution Approach 2:
The patent introduces an intermediary API layer between the application and the remote database. This API handles the value transfer operation, taking the value from the originating entity and transferring it to the destination entity through a controlled interface. The API acts as a mediator that ensures the transfer occurs without requiring the application to implement complex transaction logic.
2Ease of operation
If the originating entity retains control over value identifiers, then ease of operation is improved, but security deteriorates as the entity can interfere with or modify the value transfer
Solution Approach 1:
The patent inverts the traditional approach by having the system generate and control the destination identifiers rather than the originating entity. When a value is transferred, it is associated with new identifiers that are unknown to and uncontrollable by the originating entity. This inversion ensures that once the value leaves the originating entity's control, the entity cannot track, modify, or interfere with it, thereby securing the transfer while maintaining operational simplicity.
3Reliability
If atomicity is ensured through transaction semantics, then reliability of value transfer is improved, but loss of time increases due to locking operations
Solution Approach 1:
The patent extracts the atomicity guarantee from the transaction semantics and implements it through a simpler mechanism. The API call itself provides atomicity by either completing the entire value transfer operation or failing completely, without requiring locking operations. The value is transferred in a single atomic step from the originating entity to the destination entity, eliminating the time overhead associated with acquiring and releasing locks while maintaining the reliability of atomic transfer.
Data Source
AI summary
A method includes receiving a communication identifying a remote database and a first value stored in the remote database that is being transferred to a first entity by a second entity. That first value is capable of being modified by the second entity. Modification of the first value stored in the remote database by the second entity is prevented by identifying an application programming interface allowing operations to be performed on the remote database, and using that API to transfer the first value so as to be associated with one or more other identifiers unknown to the second entity. After modification of the first value stored by the second entity is prevented, a transfer of a second value to a database record associated with the second entity is triggered. Related systems and applications of the method and those systems are also disclosed.