Two-Dimensional Code Verification via Scenario Data Comparison
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional technologies fail to securely verify two-dimensional codes, leading to malicious replacements that can result in property theft, as they lack effective mechanisms to ensure the authenticity and integrity of the codes during generation and scanning processes.
Innovation Solution
A method and device that involve obtaining and comparing scenario information from both electronic devices involved in two-dimensional code interaction, using a rich execution environment and a trusted execution environment to verify the authenticity of the code, ensuring that the code is generated by a trusted device and not maliciously altered.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If scenario information verification is added to two-dimensional code processing, then security against malicious replacement is improved, but device complexity increases
Solution Approach 1:
The verification system is segmented into independent components: a scenario information acquisition module that collects device identifiers and environmental data, a verification module that compares scenario information against stored references, and a code processing module that executes based on verification results. This segmentation allows security functionality to be added without fundamentally redesigning the entire system.
Solution Approach 2:
Scenario information (device identifiers, location data, time stamps) is collected and stored in advance during the code generation phase. When code scanning occurs, this pre-collected information is quickly verified against the scanning device's current scenario data, enabling rapid security verification without adding significant processing time.
2Reliability
If scenario information is obtained and verified for each code interaction, then code authenticity is improved, but processing time increases
Solution Approach 1:
Scenario information including device identifiers, location coordinates, and time stamps is collected and prepared during the code generation phase. This pre-preparation means that during scanning, the verification process only needs to compare pre-formatted data rather than gathering information in real-time, significantly reducing processing time.
Solution Approach 2:
The scenario information is copied from the generation device's stored data and compared against the scanning device's current scenario. This copying approach avoids redundant data collection and processing, enabling rapid verification by simply comparing data copies rather than重新 gathering information.
3Adaptability or versatility
If scenario information is embedded in two-dimensional code, then verification capability is improved, but code complexity increases
Solution Approach 1:
The two-dimensional code maintains its universal compatibility with standard scanning devices while embedding additional scenario verification data. The code structure uses standard encoding formats that existing scanners can read, with verification information embedded in designated fields that do not interfere with the core code functionality, allowing one code to serve multiple purposes.
Solution Approach 2:
Scenario verification information is embedded as intermediary data within the two-dimensional code structure, acting as a mediator between the code's primary payment/transaction function and the security verification function. This intermediary layer allows verification data to be transmitted without disrupting the code's primary purpose or requiring specialized scanning hardware.
Data Source
AI summary
A two-dimensional code processing method and a device. The method includes: obtaining, by a first electronic device, two-dimensional code information displayed by a second electronic device; obtaining first scenario information, where the first scenario information is scenario information related to the first electronic device; determining two-dimensional code data and second scenario information based on the two-dimensional code information, where the second scenario information is scenario information related to the second electronic device; and when determining that the first scenario information and the second scenario information meet a preset condition, performing, by the first electronic device, preset processing on the two-dimensional code data. The scenario information of the two electronic devices that need to perform two-dimensional code interaction is compared, and further, two-dimensional code verification is completed.