Secure Token Registering for Offline Transaction Chains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic payment systems face inefficiencies in registering and verifying chains of offline transactions, particularly for secure token transactions, which require multiple replacement requests and signatures, increasing data length and complexity with each transaction.
Innovation Solution
A secure token transaction unit that transforms input tokens into intermediate tokens and partner tokens, generating a replacement request that is stored along with the transaction record, allowing subsequent transactions to update this request, thus requiring only a single signature and registration, even for multiple transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple replacement requests are generated for each offline transaction, then transaction security is maintained, but registration data length and complexity increase with each transaction
Solution Approach 1:
The patent merges multiple replacement requests into a single cumulative replacement request that accumulates all offline transactions. Instead of registering each transaction separately, the system combines them into one registration operation, reducing data complexity while maintaining security through cryptographic signatures that validate the entire transaction chain.
Solution Approach 2:
The system performs preliminary cryptographic signing of replacement requests during offline transactions, allowing multiple transactions to be prepared and accumulated locally. The actual registration with the token reference register is deferred until online connectivity is available, at which point the accumulated requests are registered in a single operation.
2Reliability
If each transaction is registered individually with the token reference register, then transaction integrity is verified, but registration time and system overhead increase
Solution Approach 1:
Multiple individual transaction registrations are merged into a single cumulative registration operation. The token reference register receives one consolidated replacement request that represents the entire chain of offline transactions, reducing registration time and system overhead while maintaining integrity verification through cryptographic validation of the accumulated transactions.
Solution Approach 2:
The system maintains continuous offline transaction capability without requiring intermittent online registrations after each transaction. Multiple transactions can occur continuously offline, and the registration process is performed continuously in the background when online, eliminating registration delays from the transaction flow.
3Reliability
If online access is required for token verification, then transaction security is enhanced, but offline transaction capability is reduced
Solution Approach 1:
The transaction process is segmented into offline and online phases. Offline, cryptographic signatures and replacement requests are generated and accumulated locally without network access. Online, the accumulated requests are registered with the token reference register for verification. This segmentation allows offline transactions to proceed with local security measures while periodic online connections provide centralized verification.
Solution Approach 2:
Cryptographic replacement requests serve as intermediaries that carry transaction information between offline and online phases. These signed requests allow offline transactions to be prepared and validated locally, then submitted for centralized registration when online, bridging the gap between offline capability and online security verification.
Data Source
AI summary
A secure token transaction unit is part of an electronic payment system and includes: a secure memory that stores multiple tokens, each representing a monetary value, such as a central bank digital currency token; and a control module configured to generate a first replacement request during a transaction that converts an input token stored in the secure memory into a first intermediate token and a first intermediate partner token. It also creates a token record for this transaction, storing the first intermediate token and the first replacement request. The control module can update the token record for a second transaction by replacing the first replacement request with a second replacement request.


