Offline Mobile Transactions via Local Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for online transactions between mobile devices face challenges in maintaining security and data integrity when internet connectivity is lost, as they lack robust verification methods to ensure transaction accuracy and protect account functionality.
Innovation Solution
The method leverages personal area networks (PANs) to facilitate peer-to-peer mobile device transactions without an internet connection, using short-range communication protocols like Bluetooth or NFC. It employs periodically updated databases on each mobile device to store account information, allowing transactions to be verified and processed locally before being synced with the central server once internet connectivity is restored.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If offline transactions are enabled using local databases, then transaction availability is improved, but security and data integrity deteriorate due to lack of real-time verification
Solution Approach 1:
The system performs preliminary actions by pre-synchronizing account data to local databases before offline transactions occur. The mobile application stores copies of account information locally, enabling transactions to be processed without real-time internet connectivity while maintaining security through pre-established data copies.
Solution Approach 2:
The system implements feedback mechanisms through post-transaction verification processes. After an offline transaction is completed, the system verifies the transaction against the local database and synchronizes any changes back to the central server, ensuring data integrity is maintained through feedback loops that confirm transaction accuracy.
2Reliability
If real-time verification with central server is required, then data integrity is improved, but transaction speed deteriorates due to internet connection dependencies
Solution Approach 1:
The system segments the transaction verification process into two distinct phases: local verification phase and central server synchronization phase. During offline transactions, only local database verification is required for immediate transaction speed, while comprehensive central server verification occurs asynchronously in the background, maintaining both speed and integrity.
Solution Approach 2:
The system performs preliminary local verification actions using cached account data before requiring central server confirmation. This allows transactions to proceed at high speed through local validation while the more comprehensive central verification is handled in advance or asynchronously, reducing the perceived transaction delay.
3Reliability
If comprehensive verification processes are implemented, then security is improved, but system complexity increases due to multiple verification steps
Solution Approach 1:
The mobile application performs self-service verification by autonomously validating transactions against its local database copy without requiring constant central server intervention. The application independently manages its own verification process, reducing the complexity burden on the central system while maintaining high security standards through distributed verification capability.
Solution Approach 2:
The system applies local quality by implementing verification processes that are optimized for local offline conditions. The mobile application uses simplified but sufficient verification logic tailored to local database checks, rather than replicating the full complex central server verification process locally, thus maintaining security while managing complexity.
Data Source
AI summary
A method for facilitating electronic transactions between a first mobile device and a second mobile device is provided. At a central server, when internet connection is established, the method may include receiving transaction data and prior to processing an electronic transaction based on the transaction data, verifying the electronic transaction. The verifying may include retrieving a first activity log from the first mobile device and a first browser timeout history. The method may further include retrieving from the second mobile device a second activity log and a second browser timeout history. The method may further include verifying that a first mobile application was active when a browser on the first mobile device was in timeout and that a second mobile application was active when a browser on the second mobile device was in timeout.