Payment Device Update Mechanism Using Provisional Volatile Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing payment networks face limitations in updating pre-authorized balances and limits due to resource constraints, such as limited byte sizes for issuer scripts and authentication data, leading to potential errors and the need for storing multiple sets of values in non-volatile memory.
Innovation Solution
A method and system that allow updates to be applied to a payment device's non-volatile memory only after successful transaction completion, using provisional storage and authentication processes to ensure data integrity and avoid errors, without requiring additional bytes in issuer authentication data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If update information is stored in non-volatile memory during transaction processing, then data integrity is improved, but device complexity increases due to need for provisional storage and authentication mechanisms
Solution Approach 1:
The system performs preliminary actions by provisionally storing update information in volatile memory before finalizing the transaction. This allows the system to prepare updates in advance and only commit them to non-volatile memory upon successful authentication and transaction completion, ensuring data integrity while managing complexity through staged processing
Solution Approach 2:
The patent introduces an intermediary mechanism using volatile memory as a temporary storage buffer between the incoming update information and the final non-volatile memory storage. This intermediary layer allows for authentication and verification processes to occur before permanent storage, mediating between the need for reliability and the complexity of the update mechanism
2Reliability
If multiple sets of values are stored in non-volatile memory for updates, then reliability is improved by having backup values, but memory space is consumed
Solution Approach 1:
The system extracts the backup value requirement from the non-volatile memory by moving provisional storage to volatile memory. This separation allows the system to maintain reliability through having alternative values available during processing without permanently consuming non-volatile memory space for multiple sets of update values
Solution Approach 2:
The patent implements a discard and recover mechanism where update information is provisionally stored in volatile memory during transaction processing. If authentication fails or transaction is aborted, the provisional updates are discarded and non-volatile memory retains its original values. If successful, the updates are committed and previous values are no longer needed, freeing memory space
3Productivity
If updates are applied immediately during transaction processing, then transaction speed is improved, but error risk increases due to potential authentication failures
Solution Approach 1:
The system performs preliminary storage of update information in volatile memory without immediately applying it to non-volatile memory. This preliminary action allows fast processing appearance while actually preparing updates for later commitment only after successful authentication, thus maintaining both speed perception and reliability
Solution Approach 2:
The patent implements a cushioning mechanism by storing update information provisionally in volatile memory before final commitment. This creates a buffer or cushion that prevents direct application of potentially erroneous updates to non-volatile memory, allowing authentication checks to occur without delaying the apparent transaction processing speed
4Adaptability or versatility
If issuer authentication data size is increased to include more update information, then update capability is improved, but network bandwidth consumption increases
Solution Approach 1:
The system segments the update information transmission by separating the authentication data (kept compact for bandwidth efficiency) from the update information itself (transmitted separately). This segmentation allows the authentication phase to remain bandwidth-efficient while still enabling comprehensive update capabilities through subsequent separate transmission of update data
Solution Approach 2:
The patent adds another dimension to the update process by separating the authentication dimension (using compact issuer authentication data) from the update information dimension (transmitted separately). This dimensional separation allows the system to maintain small authentication data sizes for bandwidth efficiency while still achieving comprehensive update capabilities through the additional dimension of separate update information transmission
Data Source
AI summary
A payment device and method and system for using the payment device is described capable of utilizing a pre-authorized amount on existing infrastructure, including POS terminals or for using offline pre-paid products on this infrastructure. The updates for the pre-authorized or offline prepaid products can be sent by the issuer and applied by the card contemporaneously with the card's processing of the issuer authentication data but without requiring any additional bytes in the issuer authentication data. The updates performed by the issuer can be larger and more extensive than could be achieved by using any available space in the issuer authentication data.