NFC Payment Page Opening with Local URL Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing NFC payment process is inefficient due to long URL transmission times and multiple network requests, leading to prolonged App calling times and poor user experience.
Innovation Solution
Implementing a method where the NFC tag device transmits a first URL with a length equal to or less than the maximum bytes allowed by NFC, including a query identifier, which the payment terminal device uses to determine a second URL for displaying the payment page locally, eliminating the need for additional network access and sub-packet transmissions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If the NFC tag device transmits a complete long URL, then the payment page can be opened directly, but the transmission time exceeds the NFC protocol limit and requires multiple sub-packet transmissions
Solution Approach 1:
The patent segments the URL transmission process into two parts: first transmitting a shortened first URL that fits within NFC protocol limits, then separately transmitting the complete second URL through other communication channels. This segmentation resolves the contradiction by allowing the initial NFC transmission to complete quickly while still delivering the full URL information eventually.
Solution Approach 2:
The patent introduces a URL shortening service as an intermediary mechanism. The first URL acts as a mediator that contains reference information pointing to the complete second URL. This intermediary allows the NFC transmission to stay within protocol limits while still enabling access to the full URL information through additional communication channels.
2Loss of information
If the payment terminal device performs multiple network requests to obtain the complete URL, then the full payment information can be retrieved, but the App calling time increases significantly
Solution Approach 1:
The patent performs preliminary action by pre-obtaining the complete second URL through alternative communication channels before or during the NFC payment initiation. The payment terminal device retrieves the full URL information in advance through Wi-Fi or mobile data, so that when the NFC transaction occurs, the complete payment information is already available without requiring multiple sequential network requests during the App calling process.
3Productivity
If the first URL contains all necessary payment information, then no additional network access is needed, but the URL length exceeds the maximum bytes that can be transmitted by NFC at a time
Solution Approach 1:
The patent segments the URL information into two components: a compact first URL that fits within NFC transmission limits and contains essential routing information, and a complete second URL that contains all payment details but is transmitted through other channels. This segmentation allows the NFC transmission to complete rapidly while the full information is delivered through complementary communication methods.
Solution Approach 2:
The patent creates a simplified copy (first URL) of the complete payment URL (second URL) that is suitable for NFC transmission. The first URL contains reference information that points to the full second URL, which is obtained through other communication channels. This copying approach allows the NFC protocol to transmit a valid reference quickly without being constrained by the length of the complete URL.
Data Source
AI summary
One or more implementations described include near field communication (NFC)-based payment page opening applied to a payment terminal device. Based on a near field communication way, a first uniform resource locator (URL) is acquired from an NFC tag device, where a length of the first URL is less than or equal to a maximum number of bytes that can be transmitted by the NFC tag device based on the near field communication way at a time, and where the first URL includes a URL query identifier. Based on data already stored by the payment terminal device, a second URL corresponding to the URL query identifier is determined, where the second URL comprises target information used to display a payment page. The payment page is displayed based on the second URL.