Token Reference Register Batch Registration for Secure Transactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic transaction systems face challenges in securely and efficiently registering sequences of transactions involving tokens, particularly when these transactions occur directly between secure elements and involve modifications such as splitting, merging, or switching tokens, while maintaining anonymity and preventing multiple spending attempts.
Innovation Solution
A method for registering tokens in an electronic transaction system that processes a batch or sequence of registration requests, verifying token references, and storing unique token references in a token reference register, allowing for secure and anonymous transactions without the need for continuous connection to a central register or decentralized ledger.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a sequence of transactions is processed individually one by one, then each transaction can be verified securely, but the registration process becomes time-consuming and inefficient
Solution Approach 1:
The system performs preliminary verification of all token references in a sequence before processing any transactions. The token reference register pre-loads and validates the entire sequence of token references, ensuring security requirements are met before batch processing begins. This allows subsequent transactions to be processed rapidly without repeated verification overhead.
Solution Approach 2:
Multiple individual transaction verifications are merged into a single batch processing operation. The system combines multiple token references into a sequence, verifies them collectively against the token reference register, and processes the entire batch in one operation rather than individually, significantly improving throughput while maintaining security.
2Ease of operation
If token information is stored centrally in a register, then transaction verification is simplified, but the system complexity and administrative overhead increase
Solution Approach 1:
The system extracts only the essential token reference information from full token data and stores it in a centralized register. Instead of storing complete token objects with all their attributes, only the critical reference identifiers are maintained centrally, while detailed token information remains distributed across participant units. This reduces central storage requirements and simplifies the register's structure.
Solution Approach 2:
Token references serve as intermediaries between the distributed participant units and the centralized register. Rather than requiring direct communication between all participants or storing complete token data centrally, the reference act as a lightweight mediator that enables verification without exposing the full system complexity.
3Reliability
If tokens are registered in real-time with each transaction, then multiple spending is prevented, but the registration process becomes slow and impractical for high-volume transactions
Solution Approach 1:
The system performs preliminary validation of token references in the sequence before batch processing. By pre-checking that all token references exist and are valid in the register, the system ensures multiple-spending prevention is maintained while enabling subsequent batch processing to proceed at high speed without individual verification delays.
Solution Approach 2:
Multiple registration operations are merged into a single batch registration process. Instead of registering each token individually with separate verification steps, the system combines multiple token references into a sequence and processes them collectively, achieving both security (through comprehensive verification) and high throughput (through batch processing).
4Reliability
If blockchain topology is used for transaction recording, then integrity protection is enhanced, but energy consumption and computational requirements increase significantly
Solution Approach 1:
The system extracts only the essential verification function from blockchain technology. Instead of implementing a full blockchain with distributed consensus, mining, and complete ledger replication, the patent extracts the core integrity-protection mechanism and implements it as a simplified centralized token reference register that provides the same verification capability with minimal computational overhead and energy consumption.
Data Source
Figure 1
Figure 2
Figure 3a~3b
AI summary
The invention relates to a secure element acting as a transaction unit, and to a method for registering tokens of an electronic transaction system which comprises in particular the secure element acting as a transaction unit and a token reference register. Each token of the transaction system has at least one token value and one private part of a token-individual key pair acting as token elements. The method comprises the following method steps: receiving, in a token reference register of the transaction system, a registration request from a sequence of registration requests, each registration request of the sequence having at least one token reference; using a verification unit of the token reference register to verify whether the at least one token reference contained in the received registration request can be uniquely assigned to a token of the transaction system; storing the at least one token reference in a memory unit of the token reference register in order to register the token uniquely assigned to this token reference in the transaction system if it is established in the verification step that the at least one token reference of the received register request can be uniquely assigned to a token of the transaction system and if the token reference is not yet stored in the token reference register. In the receiving step, the registration requests are received in the token reference register as a sequence of registration requests. In the verification and storage steps, the registration requests are processed in the token reference register as a sequence of registration requests.