URL-Based 2D Code Service Decoupling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The management of 2D codes in mobile transaction processing lacks uniformity and efficiency, particularly in scenarios where different merchants use different payment institutions or service platforms, leading to complex service processing and security concerns.
Innovation Solution
The implementation of URL-based 2D codes that decouple service information from the code itself, allowing a backend digital service network to manage and update service information, enabling efficient and secure service processing across multiple service institutions without the need for frequent code updates or redeployment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If service information is embedded in 2D codes for each merchant, then service information can be directly accessed, but the cost and complexity of managing and updating codes increases significantly
Solution Approach 1:
The system segments service information into two parts: a stable merchant identifier embedded in the 2D code and dynamic service information stored in a backend database. This allows the code to remain simple while enabling comprehensive service information access through the backend system.
Solution Approach 2:
A backend service system acts as an intermediary between the 2D code and service information. The code contains only a merchant identifier, which the backend system uses to retrieve and provide comprehensive service information, eliminating the need to embed full service information in each code.
2Adaptability or versatility
If different merchants use different payment institutions or service platforms, then merchants have flexibility in service selection, but service processing becomes complex and lacks uniformity
Solution Approach 1:
The backend service system provides universal service processing capabilities that work across different merchants, payment institutions, and service platforms. It handles multiple service types (payments, reservations, information queries) through a unified interface, maintaining consistency while supporting diversity.
Solution Approach 2:
The backend service system serves as a mediating platform that standardizes interactions between diverse merchants and service providers. It translates various service requests into uniform processing workflows, enabling flexible service selection without increasing processing complexity.
3Reliability
If service information is updated by redeploying 2D codes, then the latest information is provided, but the cost and time for code updates increases
Solution Approach 1:
The system separates the static merchant identifier (in the code) from the dynamic service information (in the backend database). Only the backend information needs updating, while the physical codes remain valid, eliminating the need for frequent code redeployment.
Solution Approach 2:
Service information is pre-loaded into the backend database during system setup. When updates are needed, only the database records are modified, not the physical codes. This preliminary organization of data enables rapid updates without physical code redistribution.
4Loss of information
If full service information is embedded in 2D codes, then information is immediately available, but data security risks increase
Solution Approach 1:
The system extracts sensitive service information from the 2D code and stores it securely in a backend database. The code retains only a non-sensitive merchant identifier, eliminating the security risk of embedding full service information while maintaining immediate availability through backend retrieval.
Data Source
AI summary
Implementations of the present disclosure provide a service processing method, device, and system associated with unified resource locator (URL)-based two-dimensional (code). In an implementation, a URL is received from a first service institution. The URL is obtained by a mobile device from scanning a 2D code provided by a service provider and sent to the first service institution. The URL is then parsed to identify one or more data elements including a service network identifier, a service institution identifier, and a payload including a service object identifier. The one or more data elements is sent to the second service institution based on the service institution identifier. Service information associated with the service object is received from the second service institution based on the service object identifier, and the service information is sent to the first service institution for presenting on the mobile device.