Non-repudiable Transaction Protocol via Trusted Third Party
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current transaction protocols lack effective mechanisms for ensuring non-repudiation, leading to potential unfairness and difficulties in proving the authenticity of transactions, especially in distributed systems where honesty is assumed and disputes may arise.
Innovation Solution
The implementation of a transaction manager that acts as a trusted third party, generating and managing non-repudiation tokens at various stages of a transaction, including non-repudiation of origin-work (NRO-W), non-repudiation of receipt-work (NRR-W), non-repudiation of origin-completion (NRO-C), and non-repudiation of receipt-completion (NRR-C) evidence, to prevent either party from gaining an advantage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a transaction protocol operates in a distributed system assuming honesty among parties, then the system maintains simplicity and ease of operation, but it becomes vulnerable to repudiation and lacks mechanisms to prove transaction authenticity
Solution Approach 1:
The patent introduces a Trusted Third Party (TTP) as an intermediary that issues non-repudiation tokens to transaction parties. The TTP mediates between clients and resource managers by providing cryptographic proof tokens that verify transaction origins and receipts, thereby enhancing reliability without requiring the parties themselves to implement complex verification mechanisms.
Solution Approach 2:
The patent implements preliminary action by having the Trusted Third Party issue non-repudiation tokens before transactions occur. The TTP pre-generates cryptographic proof tokens that parties can use to authenticate their transactions, eliminating the need for complex real-time verification protocols and ensuring authenticity from the outset.
2Reliability
If non-repudiation tokens are exchanged between parties to prevent repudiation, then transaction security is enhanced, but the exchange process becomes more complex and time-consuming
Solution Approach 1:
The Trusted Third Party performs preliminary action by pre-generating and storing non-repudiation tokens before transactions occur. When a transaction happens, parties simply retrieve and exchange these pre-prepared tokens, avoiding time-consuming cryptographic operations during the actual transaction and minimizing loss of time.
Solution Approach 2:
The system implements self-service by allowing parties to autonomously retrieve and exchange non-repudiation tokens from the Trusted Third Party without requiring complex mutual verification protocols. Each party independently obtains their own authentication tokens, simplifying the exchange process and reducing time requirements.
3Ease of operation
If the system assumes honesty among transaction parties to maintain simplicity, then ease of operation is improved, but the system cannot prevent or detect repudiation attempts
Solution Approach 1:
The Trusted Third Party serves as an intermediary that provides cryptographic non-repudiation tokens, allowing the system to maintain operational simplicity while preventing repudiation. Parties continue to operate simply by exchanging tokens, but the TTP's cryptographic infrastructure ensures reliability and prevents false repudiation attempts.
Solution Approach 2:
The patent replaces the mechanical assumption of honesty with cryptographic mechanisms. Instead of relying on parties being honest, the system uses cryptographic non-repudiation tokens that mathematically prove transaction origins and receipts, substituting trust-based mechanics with mathematically guaranteed security while maintaining ease of operation.
Data Source
AI summary
A non-repudiable transaction protocol system includes a memory, at least one processor in communication with the memory, an operating system executing on the at least one processor, a resource manager configured to manage a storage system, and a transaction manager. The transaction manager is configured to provide NRO-W evidence of a work request from a client to the resource manager and provide NRR-W evidence to the client that the resource manager has completed initial work for the work request. Additionally, the transaction manager is configured to provide NRO-C evidence to the resource manager that the client requested completion of the initial work and NRR-C evidence to the client that the resource manager promised to execute the completion. Each of the NRO-W evidence, the NRR-W evidence, the NRO-C evidence, and the NRR-C evidence are exchanged to prevent either one of the client and the resource manager from gaining an advantage.