NFC-based page opening method, apparatus, and device, and NFC-based information transmission method, apparatus, and device

Abstract

To provide an NFC-based page opening method, apparatus, and device, an NFC-based information transmission method, apparatus, and device, and a URL transmission method, apparatus, and device.SOLUTION: After obtaining a first URL from an NFC tag device based on a near field communication method, where the first URL includes a URL query identifier, a payment terminal device can determine, based on data already stored by the payment terminal device, a second URL that corresponds to the URL query identifier, where the second URL includes target information used to display a payment page, and display the payment page based on the second URL. A length of the first URL is less than or equal to a maximum quantity of bytes that can be transmitted by the NFC tag device at a time based on a near field communication method.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present specification relates to the field of near field wireless payment technology, and in particular to a method, apparatus, and device for opening an NFC-based payment page, an NFC-based information transmission method, apparatus, and device, and a URL transmission method, apparatus, and device. [Background technology]

[0002] Near-field communication (NFC) payment means that when purchasing goods or services, consumers can complete payments through communication conducted by an NFC tab device, such as a POS register, or a vending machine via an NFC radio frequency channel by using a user terminal that supports NFC functionality. NFC payment is a new mobile payment method. Consumers can make payments by simply bringing their mobile phone close to an NFC tag device provided by a merchant, without scanning a code. This is more convenient. Currently, the NFC payment process requires a long time for the app to call up when the user terminal is brought close to the NFC tag device, which causes a poor user experience.

[0003] Based on this, how to reduce the time consumed while opening the payment page in the NFC payment process and improve the app call speed has become a technical problem that needs to be urgently solved. Summary of the Invention

[0004] One or more embodiments of the present specification provide a method, apparatus, and device for opening an NFC-based payment page, an NFC-based information transmission method, apparatus, and device, and a URL transmission method and apparatus, which effectively reduce the time consumed while opening a payment page in an NFC payment process and improve the app invocation speed.

[0005] In order to achieve the above-mentioned technical problems, one or more embodiments of the present specification provide a method for opening an NFC-based payment page, which is applied to a payment terminal device, the method comprising: acquiring a first URL from an NFC tag device based on a near-field communication method, wherein a length of the first URL is equal to or less than a maximum number of bytes that can be transmitted at a time by the NFC tag device based on the near-field communication method, and the first URL includes a URL query identifier; determining a second URL corresponding to the URL query identifier based on data already stored by the payment terminal device, wherein the second URL includes target information used to display the payment page; and displaying the payment page based on the second URL.

[0006] One or more embodiments herein further provide an NFC-based information transmission method applied to an NFC tag device, the method comprising: receiving a near field communication signal transmitted by a payment terminal device; and transmitting a first URL to the payment terminal device via the near field communication method in response to the near field communication signal, wherein a length of the first URL is less than or equal to a maximum number of bytes that can be transmitted at one time by the NFC tag device based on the near field communication method, the first URL includes a URL query identifier, the URL query identifier is used by the payment terminal device to determine a second URL, and the second URL includes target information used to display a payment page.

[0007] One or more embodiments herein further provide a URL transmission method, applied to an application server, comprising: acquiring a URL acquisition request sent by an NFC tag device; generating a first URL in response to the URL acquisition request, wherein a length of the first URL is equal to or less than a predetermined byte threshold, the byte threshold being a maximum number of bytes that can be transmitted at one time based on NFC; and transmitting the first URL to the NFC tag device, wherein the first URL is used to be acquired by a payment terminal device from the NFC tag device via a near field wireless communication method, the first URL including a URL query identifier, the URL query identifier being used by the payment terminal device to query a second URL, the second URL including target information used by the payment terminal device to display a payment page.

[0008] One or more embodiments herein further provide an apparatus for opening an NFC-based payment page for use in a payment terminal device, the apparatus comprising: a URL acquisition module configured to acquire a first URL from an NFC tag device based on a near field communication method, wherein a length of the first URL is equal to or less than a maximum number of bytes that can be transmitted at a time by the NFC tag device based on the near field communication method, and the first URL includes a URL query identifier; a URL translation module configured to determine a second URL corresponding to the URL query identifier based on data already stored by the payment terminal device, wherein the second URL includes target information used to display the payment page; and a display module configured to display the payment page based on the second URL.

[0009] One or more embodiments herein further provide an NFC-based information transmission apparatus for use in an NFC tag device, the apparatus comprising: a signal receiving module configured to receive a near field communication signal transmitted by a payment terminal device; and a signal transmitting module configured to transmit a first URL to the payment terminal device via a near field communication method in response to the near field communication signal, wherein a length of the first URL is less than or equal to a maximum number of bytes that can be transmitted at one time by the NFC tag device based on the near field communication method, the first URL including a URL query identifier, the URL query identifier being used by the payment terminal device to determine a second URL, the second URL including target information used to display a payment page.

[0010] One or more embodiments herein further provide a URL sending apparatus for use in an application server, the apparatus including: a request acquiring module configured to acquire a URL acquisition request sent by an NFC tag device; a URL generation module configured to generate a first URL in response to the URL acquisition request, the length of the first URL being less than or equal to a predetermined byte threshold, the byte threshold being a maximum number of bytes that can be sent at one time based on NFC; and a URL sending module configured to send the first URL to the NFC tag device, the first URL being used to be acquired by a payment terminal device from the NFC tag device via a near field wireless communication method, the first URL including a URL query identifier, the URL query identifier being used by the payment terminal device to query a second URL, the second URL including target information used by the payment terminal device to display a payment page.

[0011] One or more embodiments herein further provide a payment terminal device comprising: at least one processor; and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor such that the at least one processor can: obtain a first URL from an NFC tag device based on a near field communication method, wherein a length of the first URL is less than or equal to a maximum number of bytes that can be transmitted at a time by the NFC tag device based on the near field communication method, and wherein the first URL includes a URL query identifier; determine a second URL corresponding to the URL query identifier based on data already stored by the payment terminal device, wherein the second URL includes target information used to display a payment page; and display the payment page based on the second URL.

[0012] One or more embodiments herein further provide an NFC tag device comprising: at least one processor; and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor such that the at least one processor is capable of receiving a near field communication signal transmitted by a payment terminal device; and transmitting a first URL to the payment terminal device via a near field communication method in response to the near field communication signal, wherein a length of the first URL is less than or equal to a maximum number of bytes that can be transmitted at one time by the NFC tag device based on the near field communication method, the first URL including a URL query identifier, the URL query identifier being used by the payment terminal device to determine a second URL, and the second URL including target information used to display a payment page.

[0013] One or more embodiments herein further provide an application server comprising at least one processor and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, the instructions executed by the at least one processor such that the at least one processor can: acquire a URL acquisition request sent by an NFC tag device; generate a first URL in response to the URL acquisition request, wherein a length of the first URL is less than or equal to a predetermined byte threshold, the byte threshold being a maximum number of bytes that may be transmitted at one time based on NFC; and transmit the first URL to the NFC tag device, wherein the first URL is used to be acquired by a payment terminal device from the NFC tag device via a near field wireless communication method, the first URL including a URL query identifier, the URL query identifier being used by the payment terminal device to query a second URL, the second URL including target information used by the payment terminal device to display a payment page.

[0014] At least one embodiment provided herein can achieve the following beneficial effects:

[0015] In one or more embodiments herein, the length of the first URL obtained by the payment terminal device from the NFC tag device based on the near field communication method is equal to or less than the maximum number of bytes that can be transmitted at one time by the NFC tag device based on the near field communication method, thereby avoiding a case where the NFC tag device must perform multiple subpacket transmissions with the payment terminal device due to a URL that is too long, thereby improving the transmission efficiency of information transmission between the NFC tag device and the payment terminal device and effectively shortening the information transmission time. In addition, the first URL transmitted by the NFC tag device to the payment terminal device via the near field communication method includes a URL query identifier, and the payment terminal device determines a second URL that needs to be used to display a payment page based on the URL query identifier and already stored data, obtains the second URL corresponding to the first URL via a local query, and opens the payment page based on the second URL, whereby network access does not need to be performed in the process of opening the payment page, further shortening the time consumed for opening the payment page in the NFC payment process, thereby effectively improving the app invocation speed and helping to improve user experience and NFC payment efficiency.

[0016] In order to more clearly describe one or more embodiments of the present specification or the technical solutions in the existing technology, the following briefly describes the accompanying drawings necessary for describing the embodiments or the existing technology. Obviously, the accompanying drawings in the following description only show some embodiments of the present application, and those skilled in the art can still derive other drawings from these accompanying drawings without creative efforts. [Brief explanation of the drawings]

[0017] [Figure 1] FIG. 1 is a schematic diagram illustrating an application scenario of a method for opening an NFC-based payment page according to one or more embodiments herein. [Figure 2]1 is a schematic flow chart illustrating a method for opening an NFC-based payment page, according to one or more embodiments herein. [Figure 3a] FIG. 10 is a schematic diagram illustrating a payment page according to one or more embodiments herein. [Figure 3b] FIG. 10 is a schematic diagram illustrating another payment page according to one or more embodiments herein. [Figure 4] 1 is a schematic flow chart illustrating an NFC-based information transmission method according to one or more embodiments herein. [Figure 5] 1 is a schematic flowchart illustrating a URL transmission method, according to one or more embodiments of the present disclosure. [Figure 6] FIG. 3 is a swimlane diagram illustrating a method for opening an NFC-based payment page corresponding to FIG. 2 in accordance with one or more embodiments herein. [Figure 7] 3 is a schematic diagram illustrating the structure of a device that opens an NFC-based payment page corresponding to FIG. 2, in accordance with one or more embodiments herein. [Figure 8] 5 is a schematic diagram illustrating the structure of an NFC-based information transmission device corresponding to FIG. 4, according to one or more embodiments herein. [Figure 9] 6 is a schematic diagram illustrating the structure of a URL transmission device corresponding to FIG. 5, according to one or more embodiments of the present disclosure. [Figure 10] FIG. 3 is a schematic diagram illustrating the structure of a payment terminal device corresponding to FIG. 2, in accordance with one or more embodiments herein. [Figure 11] FIG. 5 is a schematic diagram illustrating the structure of an NFC tag device corresponding to FIG. 4, in accordance with one or more embodiments of the present disclosure. [Figure 12] 6 is a schematic diagram illustrating the structure of an application server corresponding to FIG. 5, in accordance with one or more embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0018] In order to make the objectives, technical solutions and advantages of one or more embodiments of the present specification clearer, the technical solutions in one or more embodiments of the present specification will be clearly and completely described below with reference to some specific embodiments of the present specification and corresponding accompanying drawings. Obviously, the described embodiments are only a part, not all, of the embodiments of the present specification. All other embodiments obtained by those skilled in the art based on the embodiments of the present specification without creative efforts fall within the protection scope of one or more embodiments of the present specification.

[0019] In one or more embodiments of the present application, terms such as "first" and "second" may be used to describe various types of information, but it should be understood that the information is not limited to these terms. These terms are used only to distinguish between the same types of information. For example, a first thing could be referred to as a second thing, and similarly, a second thing could be referred to as a first thing, without departing from the scope of one or more embodiments of the present application. As used herein, the word "if" can be interpreted as "when" or "during" or "depending on the decision," depending on the context.

[0020] It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) used in this application are information and data authorized by the user or fully authorized by all parties, and the related data must be collected, used, and processed in accordance with the relevant laws, regulations, and standards of the relevant regions, and corresponding action entries are provided for the user to choose to allow or deny.

[0021] In existing technologies, the app invocation process for NFC payments takes a long time, forcing users to wait a long time before viewing the payment page, resulting in a poor user experience. There are two main reasons for this. One is that (1) in the NFC communication process, the uniform resource locator (URL) transmitted from the NFC tag device to the payment terminal device is long. Because the NFC communication standard specifies the maximum number of bytes that can be transmitted at one time, multiple subpacket transmissions are required when the number of bytes in the transmitted URL exceeds the maximum number of bytes that can be transmitted at one time by an NFC tag device based on a near-field communication method. As a result, the process of transmitting the URL from the NFC tag device to the payment terminal device takes a long time. The second is that (2) after obtaining the URL, the payment terminal device needs to request the service end of the code platform to perform decryption in the network request method before entering the payment page. This requires multiple network requests to be performed during the app invocation process, which increases the app invocation time.

[0022] To alleviate the deficiencies of existing technologies, this solution provides the following embodiments.

[0023] FIG. 1 is a schematic diagram illustrating an application scenario of an NFC-based payment page opening method according to one or more embodiments herein.

[0024] As shown in FIG. 1 , when a user needs to pay for an order by using the payment terminal device 101 owned by the user, the user may turn on the NFC function of the payment terminal device 101 and then bring the payment terminal device 101 close to the NFC tag device 102 set by the merchant. After sensing the NFC radio frequency field of the payment terminal device 101, the NFC tag device 102 may send a first URL including a URL query identifier (wherein the length of the first URL is equal to or less than the maximum number of bytes that can be sent by the NFC tag device 102 at a time based on the near field communication method) to the payment terminal device 101 based on the near field communication method. After receiving the first URL sent by the NFC tag device 102 based on the near field communication method, the payment terminal device 101 may determine a second URL corresponding to the URL query identifier based on data already stored by the payment terminal device 101, and further render a payment page to be displayed to the user based on the second URL.

[0025] In the method of Fig. 1, the length of the first URL obtained by the payment terminal device from the NFC tag device through the near field communication method is equal to or less than the maximum number of bytes that can be transmitted at one time by the NFC tag device through the near field communication method, thereby avoiding the need for the NFC tag device to perform multiple subpacket transmissions with the payment terminal device due to a long URL, thereby improving the transmission efficiency of information transmission between the NFC tag device and the payment terminal device and effectively shortening the information transmission time. In addition, the first URL transmitted by the NFC tag device to the payment terminal device through the near field communication method includes a URL query identifier, and the payment terminal device determines a second URL to be used to display a payment page based on the URL query identifier and previously stored data, obtains the second URL corresponding to the first URL through a local query, and opens the payment page based on the second URL. In this case, no network access is required in the process of opening the payment page, further shortening the time consumed for opening the payment page in the NFC payment process, thereby effectively improving the app invocation speed and improving the user experience and NFC payment efficiency.

[0026] 2 is a schematic flowchart illustrating an NFC-based payment page opening method according to one or more embodiments of the present disclosure. From a hardware perspective, the process may be performed by a payment terminal device. From a program perspective, the process may be performed by an application program installed on the payment terminal device. As shown in FIG. 2, the process may include the following steps:

[0027] Step 202: Obtain a first URL from the NFC tag device based on a near field communication method, where the length of the first URL is less than or equal to the maximum number of bytes that can be transmitted at one time by the NFC tag device based on the near field communication method, and the first URL includes a URL query identifier.

[0028] In one or more embodiments herein, the NFC tag device may be a payment collection device set by a merchant in an offline payment scenario, and the payment terminal device may be a smartphone that supports NFC functionality and is carried by a user, or may be another device that supports NFC functionality and can complete an NFC payment, but this is not particularly limited.

[0029] In practice, the maximum number of bytes that can be transmitted at one time by an NFC tag device based on a near field communication method is typically 124 bytes, and therefore the length of the first URL transmitted by the NFC tag device to a user's payment terminal device based on a near field communication method may be 124 bytes or less.

[0030] In one or more embodiments herein, the length of the first URL obtained by the payment terminal device from the NFC tag device based on the near field communication method is equal to or less than the maximum number of bytes that can be transmitted at one time by the NFC tag device based on the near field communication method, thereby avoiding a case where the NFC tag device has to perform multiple subpacket transmissions with the payment terminal device due to the URL being too long, thereby improving the transmission efficiency of information transmission between the NFC tag device and the payment terminal device and effectively shortening the information transmission time.

[0031] Step 204: Determine a second URL corresponding to the URL query identifier based on data already stored by the payment terminal device, where the second URL includes target information used to display the payment page.

[0032] In practice, different scenario types may correspond to different second URLs. For example, the second URL for a POS-based NFC payment scenario may be different from the second URL for a vending machine NFC payment scenario. Therefore, the URL query identifier used to query the second URL is related to the scenario type. Different payment scenarios correspond to different URL query identifiers, which may identify different second URLs, and further, different payment pages may be displayed to the user based on the different second URLs. For example, there are different URL query identifiers in different scenarios, such as POS payment and vending machine payment.

[0033] In one or more embodiments herein, the data already stored by the payment terminal device may include a mapping relationship between a URL query identifier and a URL template. After acquiring the first URL, the payment terminal device can identify a URL template corresponding to the URL query identifier based on the URL query identifier in the first URL and the mapping relationship between the locally stored URL query identifier and the URL template. Subsequently, the position to be filled in the URL template is filled with the information identifier included in the first URL to obtain a second URL. The process of determining the second URL will be described in detail in subsequent embodiments herein. For brevity, details will be omitted here.

[0034] Step 206: Display a payment page based on the second URL.

[0035] In one or more embodiments herein, the target information included in the second URL used to display the payment page may be information necessary to render the payment page, such as text information, image information, amount information, etc. After determining the second URL, the payment terminal device may directly render the payment page based on the target information included in the second URL used to display the payment page.

[0036] In one or more embodiments herein, the first URL sent by the NFC tag device to the payment terminal device in the long-distance wireless communication method includes a URL query identifier, and the payment terminal device determines a second URL that needs to be used to display a payment page based on the URL query identifier and already-stored data, obtains the second URL corresponding to the first URL through a local query, and opens the payment page based on the second URL, wherein no network access needs to be performed in the process of opening the payment page, and the time consumed during opening the payment page in the NFC payment process is further reduced, thereby effectively improving the app invocation speed and helping to improve user experience and NFC payment efficiency.

[0037] In the method of Fig. 2, the length of the first URL obtained by the payment terminal device from the NFC tag device through the near field communication method is equal to or less than the maximum number of bytes that can be transmitted at one time by the NFC tag device through the near field communication method, thereby avoiding the need for the NFC tag device to perform multiple subpacket transmissions with the payment terminal device due to a long URL, thereby improving the transmission efficiency of information transmission between the NFC tag device and the payment terminal device and effectively shortening the information transmission time. In addition, the first URL transmitted by the NFC tag device to the payment terminal device through the near field communication method includes a URL query identifier, and the payment terminal device determines a second URL to be used to display the payment page based on the URL query identifier and previously stored data, obtains the second URL corresponding to the first URL through a local query, and opens the payment page based on the second URL, whereby no network access is required in the process of opening the payment page, further shortening the time consumed for opening the payment page in the NFC payment process, thereby effectively improving the app invocation speed and helping to improve user experience and NFC payment efficiency.

[0038] Based on the method of FIG. 2, one or more embodiments herein further provide solutions for some specific embodiments of the method, as described below.

[0039] In practice, after obtaining the first URL, the payment terminal device can start the main process of the corresponding application program based on the protocol header information in the first URL, and the main process of the application program analyzes the service parameter information after the protocol header in the first URL to obtain a new URL, and extracts the identification information from the new URL required to determine the second URL.

[0040] Based on this, before the step of determining a second URL corresponding to the URL query identifier based on data already stored by the payment terminal device in step 204, the method of FIG. 2 may further include the steps of analyzing service parameter information of the first URL to obtain a third URL, where the service parameter information includes a URL query identifier and an information identifier, and the information identifier is used to query service description information corresponding to the first URL, and extracting the URL query identifier and the information identifier from the third URL.

[0041] In one or more embodiments herein, the service parameter information of the first URL may refer to information following a specified character (e.g., a scheme) of the parameter in the link. For example, if the first URL is https: / / render.alipay.com / p / s / ulink / ?s=nfc&scheme= alipay %1A2B3c4d%1A2B3c4dCCC%5e6F${token}_${amount}, where https: / / render.alipay.com / p / s / ulink / ? s=nfc is a protocol header, and the payment terminal device determines, based on the information in the protocol header, that this URL is a URL that applies to Alipay, performs NFC payment, and starts the Alipay main process. Once started, the Alipay main process can analyze part of the service parameter information, specifically, alipay%1A2B3c4d%1A2B3c4dCCC%5e6F${token}_${amount} after the specified character scheme, and obtains a third URL after analysis, specifically, alipay: / / nfc / app?s=CCC&v=${token}_${amount}, where CCC may represent a URL query identifier, ${token} may represent an information identifier, and ${amount} may represent amount information. It is worth noting that CCC, ${token}, and ${amount} can represent the location of these identifiers or information in the URL, and in practice, CCC, token, and amount are specific strings. For example, the specific third URL is alipay: / / nfc / app?s=sn&v=1q2w3e4r5t6y7u8i_0.01, where the URL query identifier is specifically sn, the information identifier is specifically 1q2w3e4r5t6y7u8i, and the amount information is specifically 0.01.

[0042] As described above, after the third URL is obtained, the URL query identifier and the information identifier can be extracted based on the composition structure of the third URL by using a predetermined URL processing process.

[0043] In practice, the service description information corresponding to the first URL may be information related to an order, and the service description information may include, but is not limited to, an order number, a seller number, an order acceptance time, a first URL generation time, an order acceptance time limit, a payment user identifier, and an order payment result. The service description information may be stored on the application server side. The application server side may randomly generate an information identifier and store the information identifier associated with the service description information of an order. In this case, there is a mapping relationship between the first URL containing the information identifier and the order stored in association with the information identifier. In this way, after the information identifier is obtained, the service description information of the corresponding order may be queried from the application server side based on the information identifier.

[0044] In one or more embodiments herein, after the URL query identifier is extracted from the third URL, a corresponding URL template required to generate the second URL may be further determined based on the URL query identifier.

[0045] Based on this, the step 204 of the method in FIG. 2 of determining a second URL corresponding to the URL query identifier based on data already stored by the payment terminal device specifically includes: querying a URL template based on the URL query identifier, where the URL template has a position to be filled; and filling the position to be filled with an information identifier to obtain a second URL, where the second URL includes target information and the information identifier is included in the target information.

[0046] In one or more embodiments herein, data already stored by the payment terminal device may include a mapping relationship between a URL query identifier and a URL template. Therefore, a URL template corresponding to the URL query identifier may be identified based on the mapping relationship. Then, the location to be filled in the URL template is filled with the information identifier extracted from the third URL to obtain a second URL containing target information used to display the payment page.

[0047] In practice, the first URL acquired by the payment terminal device further includes amount information, and the position to be filled in the URL template is filled with the information identifier and the amount information, and a second URL including the amount information is acquired. Indeed, if the first URL does not include amount information, the position to be filled in the URL template is filled with only the information identifier, and a second URL is acquired. For example, still using the example where the third URL is alipay: / / nfc / app?s=sn&v=1q2w3e4r5t6y7u8i_0.01, where the URL query identifier is sn, the information identifier is 1q2w3e4r5t6y7u8i, the amount information is 0.01, and the URL template corresponding to the query identifier sn is alipays: / / platformapi / startApp?appId=112233&appScheme=NFC_ABC&pageParams=%12345qwert$[value]$%6789, where $[value]$ represents the position to be filled. After filling the position to be filled in the URL template with the information identifier 1q2w3e4r5t6y7u8i and the amount information 0.01, the second URL, alipays: / / platformapi / startApp?appId=112233&appScheme=NFC_ABC&pageParams=%12345qwert1q2w3e4r5t6y7u8i_0.01%6789, can be obtained.

[0048] In one or more embodiments herein, the target information included in the second URL may include a component identifier, a task identifier, and task parameters.

[0049] Correspondingly, in step 206 of the method of FIG. 2 , the step of displaying a payment page based on the second URL may specifically include the steps of determining a first application component corresponding to the component identifier, determining a page rendering task corresponding to the task identifier, and executing the page rendering task based on the task parameters by using the first application component to render the payment page.

[0050] In one or more embodiments of the present specification, different component identifiers may correspond to different application components, different task identifiers may correspond to different page rendering tasks, and different task parameters may be used to render different pages. The following provides an example that specifically illustrates the component identifier, task identifier, and task parameter included in the second URL, using an example where the second URL is: alipays: / / platformapi / startApp?appId=112233& appScheme=NFC_ABC&pageParams=%12345qwert1q2w3e4r5t6y7u8i_0.01%6789, where 112233 is a specific component identifier, NFC_ABC is a specific task identifier, and %12345qwert1q2w3e4r5t6y7u8i_0.01%6789 is a specific task parameter. It can be seen that the information identifier (1q2w3e4r5t6y7u8i) is included in the task parameter.

[0051] In one or more embodiments herein, the first application component is a component of an application program of the payment terminal device for rendering a payment page based on the second URL. Specifically, the first application component may be an activity component. In practice, a page corresponding to the activity component is set to be visible to the user, and during operation of the first application component, the application program can render a payment page corresponding to the second URL and display the payment page to the user.

[0052] In one or more embodiments herein, executing a page rendering task to render a payment page based on task parameters by using a first application component may specifically mean rendering the payment page in a native manner, since there is no need to load a container for rendering the payment page in a native manner, improving page rendering efficiency and thereby reducing the time required to render the page.

[0053] In practice, when certain conditions are met, for example, when the native payment page is unavailable due to a critical issue or when a new feature needs to be released urgently, the payment page will be rendered in a container manner instead, which can ensure that users can open the payment page smoothly when the payment page cannot be rendered in a native manner.

[0054] In one or more embodiments herein, the payment page is the landing page of the app invocation operation; in other words, displaying the payment page means that the app invocation is successful, and the first page the user can see after an NFC code scan payment is initiated is the payment page.

[0055] The step of performing a page rendering task based on the task parameters by using the first application component to render the payment page may specifically include the steps of: acquiring pre-stored page information based on the task parameters, where the page information includes at least one of photo information and copywriting information; and performing a page rendering task based on the page information by using the first application component to render the payment page.

[0056] In one or more embodiments herein, the pre-stored page information obtained based on the task parameters can determine the information included in the rendered payment page. If the pre-stored page information obtained based on the task parameters includes photo information and copywriting information, the payment page rendered based on the page information can include both photo information and copywriting information.

[0057] In practice, the photo information in the page information may include, but is not limited to, NFC payment scenario photos, NFC payment operation process guide photos, and NFC payment discount activity photos. The copywriting information in the page information may include, but is not limited to, "Tap to pay. Come experience it," "Stay close to pay," and "NFC payment, even faster."

[0058] In one or more embodiments herein, the task parameters included in the second URL further include amount information, the amount information including first amount information and second amount information, the first amount information representing a set amount value and the second amount information representing that no amount value is provided, and when the amount information is the first amount information, the set amount value is displayed on the payment page, and when the amount information is the second amount information, the amount value is not displayed on the payment page.

[0059] In one or more embodiments herein, if the first URL acquired by the user's payment terminal device does not include amount information, the amount information in the task parameters included in the second URL corresponds to the second amount information, and the amount value is not displayed on the payment page ultimately displayed to the user. Figure 3a is a schematic diagram illustrating a payment page according to one or more embodiments herein. As shown in Figure 3a, the amount value is not displayed on the payment page.

[0060] In one or more embodiments of the present specification, if the first URL acquired by the user's payment terminal device includes amount information, the amount information in the task parameters included in the second URL corresponds to the first amount information, and the amount information is finally displayed on the payment page displayed to the user. Figure 3b is a schematic diagram showing another payment page according to one or more embodiments of the present specification. As shown in Figure 3b, the amount value of 0.01 yuan to be paid by the user is displayed on the payment page.

[0061] In practice, after the user's payment terminal device displays the payment page to the user, the user can indicate that the user agrees to make the payment by clicking a payment control on the payment page. After obtaining the user's consent, the payment terminal device can send a service request to the application server, which is used to perform payment processing for the order, and the application server can perform subsequent payment processing based on the information included in the service request.

[0062] Based on this, the payment page further includes payment controls.

[0063] Consequently, after the step of displaying a payment page based on the second URL in step 206, the method of FIG. 2 may further include the steps of: sending a service request to an application server based on the second URL in response to a user's trigger operation on the payment control, wherein the service request includes an information identifier, and the information identifier is used to query service description information corresponding to the first URL; receiving service execution result information returned by the application server, wherein the service execution result information is determined by the application server based on the service description information, and the service description information is obtained through a query by the application server based on the information identifier; and displaying a payment result page based on the service execution result information.

[0064] In one or more embodiments herein, the payment controls on the payment page specifically include a payment confirmation control. In practice, the payment controls may specifically further include a payment cancellation control. The payment page may include both a payment confirmation control and a payment cancellation control for a user to select, or may include the payment control "Confirm Payment" but not the payment cancellation control, as shown in FIG. 3b. The settings of the payment controls may be flexibly provided and adjusted based on actual needs.

[0065] In practice, the application program for NFC payment processing in the payment terminal device also needs to be started before displaying the payment page to the user, and the starting of the application program can be divided into cold start and hot start, and the two starting methods correspond to different application invocation processes.

[0066] Based on this, in step 206 of the method of FIG. 2, displaying the payment page based on the second URL may specifically include directly displaying the payment page during a cold start of the application program.

[0067] In one or more embodiments herein, a cold start of an application program refers to the process in which an application program is started when it is not running or after processing has finished. This process requires the system to create a process and start the application, which typically takes longer than a hot start (when the application is still running in memory). During a cold start, the system must load all of the application's resources and data from scratch, including the application's executable files, data files, and required system resources.

[0068] In existing technologies, during an app invocation using a cold start, the application program in the payment terminal device additionally loads other processes that are not the main process, such as a push process, a tool process, and a small program process. These processes other than the main process are not essential processes for the NFC payment app invocation process, and running these processes reduces the efficiency of the app invocation and increases the time it takes to invoke the app. In addition, during an app invocation using a cold start, multiple pages need to be loaded, such as the app invocation execution page, transit page, intermediate scan page, splash screen page, application program homepage, and payment page. Only the app invocation execution page and payment page are necessary pages, and loading other redundant pages inevitably increases the time it takes to invoke the app.

[0069] In one or more embodiments herein, directly displaying the payment page during a cold start of the application program means that during a cold start of the application program, pages that are not essential for the NFC payment process, such as the application program's homepage, splash screen page, transit page, intermediate scan page, etc., are not loaded, and other processes other than the main process are not loaded, and the main process is directly loaded to display the payment page. In this way, the time required to load non-essential processes is reduced, and the time required to load some non-essential pages before the payment page is loaded is reduced, thereby effectively shortening the time required to open the payment page in the NFC payment process and improving the efficiency of app invocation.

[0070] In the case of a hot start, before the step of displaying the payment page based on the second URL in step 206, the method of FIG. 2 may further include a step of performing stack clearing on the page stack during the hot start of the application program.

[0071] In one or more embodiments herein, a hot start of an application program refers to a user reopening the application program when the application program is open on a user terminal but is placed in the background for some reason (e.g., the user presses the return key, the home key, etc.). During a hot start, since the application program process already exists in the background of the user terminal, the system does not need to create an application class, but directly restores the application state from the existing process and creates and initializes a main activity class. Therefore, the hot start process is faster and the user experience is better.

[0072] In the Android® operating system, when a user starts multiple pages in an application program, each of the pages can be served as a page stack. The page (activity) stack is a mechanism designed by the Android® framework to manage the lifecycle of activities. The term "stack" herein does not refer to a programming language stack data structure, but rather to a logical concept used to track activities (i.e., each page of an application) in application lifecycle management. Each time a new activity is started, it is added to the top of the activity stack, i.e., "pushed onto the stack." When a user returns to a previous page, the activity for the current page is removed from the top of the stack, i.e., "pulled off the stack."

[0073] In the activity stack, each activity has its state information, including its view state, lifecycle state, and other related data, which can be stored and restored through the system's lifecycle management mechanism. A "stack clearing" operation refers to removing some or all activities from the activity stack. In practice, stack clearing operations can be achieved through startActivityForResult, a flag in an intent, or a method within a component.

[0074] In one or more embodiments herein, performing stack clearing on the page stack deletes pages of an application program that are already present in the background, such as deleting the home page, splash screen page, and scan page of the application program that are already present. This prevents an unrelated page from being presented to the user and redirecting the unrelated page to a payment page in the NFC payment process. After stack clearing on the page stack is performed, the payment page can be directly presented to the user in the app invocation process, leading to an improved user experience.

[0075] In practice, near field communication is established between a user's payment terminal device and an NFC tag device, and the user's payment terminal device can be used as a primary NFC device that transmits near field communication signals.

[0076] Based on this, in step 202 of the method of FIG. 2 , the step of obtaining a first URL from the NFC tag device based on a near field communication method may specifically include the steps of: sending a near field communication signal by using the payment terminal device as a primary NFC device; and obtaining the first URL sent by the NFC tag device via a near field communication method in response to the near field communication signal.

[0077] In practice, the first URL obtained by the payment terminal device based on NFC further includes domain name information, which can be used in the payment terminal device to indicate the NFC application program to be used for this NFC payment.

[0078] Based on this, in step 202 of the method of FIG. 2, the step of obtaining a first URL from the NFC tag device based on a near field communication method may specifically include the steps of obtaining, by the operating system, the first URL provided by the NFC tag device based on a near field communication method, where the first URL further includes domain name information; determining an application program corresponding to the domain name information; and sending the first URL to the application program.

[0079] In one or more embodiments herein, after the payment terminal device obtains the first URL sent by the NFC tag device based on NFC, the operating system can first identify protocol type information of the first URL to determine whether to respond to the first URL, and further identify domain name information in the first URL and determine an application program that needs to be called based on the domain name information. After determining the application program that needs to be called, the operating system can send the first URL to the application program, and the main process of the application program can determine a second URL based on the first URL and render a payment page based on the second URL.

[0080] In practice, the first URL further includes path information, which can be used to indicate an application component of an application program that needs to be used for the current NFC payment.

[0081] Accordingly, determining the application program corresponding to the domain name information may specifically include determining a second application component corresponding to the domain name information and the path information.

[0082] Accordingly, sending the first URL to the application program may specifically include sending the first URL to the second application component.

[0083] In one or more embodiments herein, after obtaining the first URL, the operating system can identify domain name information and path information of the first URL and determine an application component to be used to process the first URL based on the domain name information and path information. The application component can be an application component that is pre-registered in the operating system and corresponds to the domain name information and path information.

[0084] In one or more embodiments herein, the second application component may be a component in an application program used to convert the first URL. Specifically, the second application component may be an activity component. In practice, the page corresponding to the second application component may be set to hidden. During operation of the second application component, the application program can convert the first URL to the second URL.

[0085] In one or more embodiments herein, the second application component corresponding to the domain name information and path information can be executed in the main process of the application program. During a cold start, the second application component used to process the first URL can be created, and the main process of the application program used to execute the second application component can be created; during a hot start, the second application component used to process the first URL can be similarly created, and the second application component can be enabled to execute in the main process of the application program.

[0086] 4 is a schematic flowchart illustrating an NFC-based information transmission method according to one or more embodiments of the present disclosure. From a hardware perspective, the process may be performed by an NFC tag device. From a program perspective, the process may be performed by an application program installed on the NFC tag device. As shown in FIG. 4, the process may include the following steps:

[0087] Step 402: Receive a near field communication signal transmitted by a payment terminal device.

[0088] Step 404: Send a first URL to the payment terminal device via a near field communication method in response to the near field communication signal, where the length of the first URL is less than or equal to the maximum number of bytes that can be sent at one time by the NFC tag device based on the near field communication method, the first URL includes a URL query identifier, the URL query identifier is used by the payment terminal device to determine a second URL, and the second URL includes target information used to display the payment page.

[0089] In one or more embodiments herein, the NFC tag device, the payment terminal device, the near field communication, the first URL, the URL query identifier, the second URL, the payment page, and the payment page target information have the same meanings as the terms referenced in the method embodiment of Fig. 2. Since the above description has detailed the process of the NFC tag device sending the first URL to the payment terminal device via the near field communication method, details will be omitted here.

[0090] In one or more embodiments herein, the payment terminal device is used as an NFC card reader, and when the payment terminal device is brought close to the NFC tag device, the payment terminal device can transmit a near field communication signal to the NFC tag device, trigger near field communication with the NFC tag device, and obtain a first URL from the NFC tag device.

[0091] In the method of Fig. 4, the length of the first URL obtained by the payment terminal device from the NFC tag device through the near field communication method is equal to or less than the maximum number of bytes that can be transmitted at one time by the NFC tag device through the near field communication method, thereby avoiding the need for the NFC tag device to perform multiple subpacket transmissions with the payment terminal device due to a long URL, thereby improving the transmission efficiency of information transmission between the NFC tag device and the payment terminal device and effectively shortening the information transmission time. In addition, the first URL transmitted by the NFC tag device to the payment terminal device through the near field communication method includes a URL query identifier, and the payment terminal device determines a second URL to be used to display the payment page based on the URL query identifier and previously stored data, obtains the second URL corresponding to the first URL through a local query, and opens the payment page based on the second URL. In this case, no network access is required in the process of opening the payment page, further shortening the time consumed for opening the payment page in the NFC payment process, thereby effectively improving the app invocation speed and improving the user experience and NFC payment efficiency.

[0092] Based on the method of FIG. 4, one or more embodiments herein further provide solutions for some specific implementations of the method, as described below.

[0093] In one or more embodiments herein, in step 402, before the step of receiving the near field communication signal transmitted by the payment terminal device, the method of FIG. 4 may further include the steps of: acquiring a predetermined trigger operation; acquiring first service information in response to the trigger operation; sending a URL acquisition request to an application server, where the URL acquisition request includes the first service information; and receiving a first URL returned by the application server, where the first URL includes an information identifier, where the information identifier is used to query service description information, where the service description information includes the first service information and second service information, where the second service information is information acquired by the application server and includes information related to the service corresponding to the first URL.

[0094] In one or more embodiments herein, the predetermined trigger operation may include, but is not limited to, an operation such as a cashier clicking a collect payment button on a cash register device and a user clicking a pay button on a vending machine. The first service information may include, but is not limited to, information such as an order number, a merchant number, an order time, and an order amount. The second service information may include, but is not limited to, information such as a generation time of the first URL, a transmission time of the first URL, the content of the first URL, a payment deadline for the order, whether the order has been paid, and an identifier of the paying user.

[0095] In practice, the first service information may include order-related information sent to the application server by the NFC tag device. Some information in the second service information may include information sent to the application server by the payment terminal device, such as the payment user's identification information. Some information in the second service information may further include information generated by the application server, such as the generation time of the first URL and the expiration date of the information identifier.

[0096] In one or more embodiments herein, the application server can obtain an information identifier (token) by a method of generating a random code, and store the information identifier in association with server description information. Thus, upon receiving a service request sent by a payment terminal device and including the information identifier, the application server queries corresponding service description information based on the information identifier to further the service process.

[0097] 5 is a schematic flowchart illustrating a URL transmission method according to one or more embodiments of the present disclosure. From a hardware perspective, the process may be performed by an application server. From a program perspective, the process may be performed by an application program installed on the application server. As shown in FIG. 5, the process includes the following steps:

[0098] Step 502: Obtain a URL acquisition request sent by the NFC tag device.

[0099] Step 504: Generate a first URL in response to the URL acquisition request, where the length of the first URL is less than or equal to a predetermined byte threshold, the byte threshold being the maximum number of bytes that can be transmitted at one time based on NFC.

[0100] Step 506: Send a first URL to the NFC tag device, where the first URL is used to be acquired by the payment terminal device from the NFC tag device via a near field communication method, the first URL includes a URL query identifier, the URL query identifier is used by the payment terminal device to query a second URL, and the second URL includes target information used by the payment terminal device to display a payment page.

[0101] In one or more embodiments herein, the NFC tag device, the payment terminal device, the near field communication, the first URL, the URL query identifier, the second URL, the payment page, and the payment page target information have the same meanings as the terms referenced in the method embodiment of Fig. 2. Since the above description has detailed the process of the NFC tag device sending the first URL to the payment terminal device via the near field communication method, details will be omitted here.

[0102] In one or more embodiments herein, the first URL is generated by an application server in response to a URL acquisition request sent by the NFC tag device, and the URL acquisition request may include information about a service scenario type of the NFC tag device.

[0103] Based on this, the step of generating a first URL in response to a URL acquisition request in step 504 of the method of FIG. 5 may specifically include the steps of determining a service scenario type of the NFC tag device in response to the URL acquisition request, and generating a first URL corresponding to the service scenario type, wherein a URL query identifier included in the first URL is used to query a second URL corresponding to the service scenario type.

[0104] In one or more embodiments herein, the service scenario types of the NFC tag device may include, but are not limited to, a POS payment scenario, a vending machine payment scenario, a water vending service scenario through a service machine, a gate opening scenario, and a food ordering scenario. In practice, different service scenarios correspond to different URL query identifiers, and the different URL query identifiers identify different second URLs, resulting in different payment pages being displayed to the user based on the different second URLs. The above description details the process by which the second URL corresponding to the service scenario type is determined based on the URL query identifier included in the first URL, so details are omitted here.

[0105] Optionally, the step of generating a first URL in response to the URL acquisition request in step 504 of the method of FIG. 5 may specifically include the steps of generating an information identifier based on first service information included in the URL acquisition request, where the information identifier is used to query service description information corresponding to the first URL, where the service description information includes the first service information and second service information, and the second service information is information acquired by the application server and includes information related to the service corresponding to the first URL; and generating the first URL including the information identifier.

[0106] In one or more embodiments herein, the information identifier is generated by the application server based on the first service information, for example, the application server generates the information based on an order number or a seller number. Optionally, the information identifier can be a string randomly generated by the application server. The generated information identifier and the service description information can be stored in the application server in a corresponding association manner, so that the service description information can be queried based on the information identifier when the service description information needs to be subsequently used.

[0107] Accordingly, after the step of sending the first URL to the NFC tag device in step 506, the method of FIG. 5 may further include the steps of: acquiring a service request sent by the payment terminal device, where the service request includes an information identifier; querying service description information used to perform the service corresponding to the service request based on the information identifier; performing the service based on the identified service description information to obtain service execution result information; and sending the service execution result information to the payment terminal device.

[0108] Specifically, an example in which the service is a payment service for an order is used for explanation. When the user's payment terminal device displays a payment page to the user, the user can trigger a payment confirmation control on the payment page if they approve the order. When the user triggers the payment confirmation control on the payment page, the payment terminal device can send a service request to the application server to request the application server to perform the service for the order.

[0109] After receiving the service request sent by the payment terminal device, the application server can identify service description information stored in association with the information identifier based on the information identifier included in the service request, and since the service description information may include information related to the order, the application server can execute the payment service for the order based on the identified service description information, obtain the corresponding payment result, and feed back the payment result information to the payment terminal device.

[0110] 6 is a swimlane diagram illustrating a method for opening an NFC-based payment page corresponding to FIG. 2, according to one or more embodiments of the present specification. As shown in FIG. 6, the process of the method for opening an NFC-based payment page involves execution entities such as an NFC tag device, a payment terminal device, and an application server, and the process of the method includes a first URL generation stage, a first URL transmission stage, an app invocation stage, and a service execution stage, and may specifically include the following steps:

[0111] Step 602: The NFC tag device acquires a predetermined trigger operation.

[0112] Step 604: The NFC tag device acquires first service information in response to the trigger operation.

[0113] Step 606: The NFC tag device sends a URL acquisition request including the first service information to the application server.

[0114] Step 608: After receiving the URL acquisition request, the application server generates an information identifier.

[0115] Step 610: The application server stores the information identifier in association with the service description information, and generates a first URL including the information identifier.

[0116] Step 612: The application server feeds back the first URL to the NFC tag device.

[0117] Step 614: The NFC tag device obtains the first URL.

[0118] Step 616: The payment terminal device transmits a near field communication signal.

[0119] Step 618: The NFC tag device receives the near field communication signal transmitted by the payment terminal device.

[0120] Step 620: In response to the near field communication signal, the NFC tag device transmits the first URL to the payment terminal device via a near field communication method.

[0121] Step 622: The payment terminal device obtains the first URL.

[0122] Step 624: The payment terminal device analyzes the service parameter information of the first URL to obtain a third URL.

[0123] Step 626: The payment terminal device extracts the URL query identifier and the information identifier from the third URL.

[0124] Step 628: The payment terminal device queries a URL template based on the URL query identifier.

[0125] Step 630: The payment terminal device fills the position to be filled in the URL template with the information identifier to obtain a second URL.

[0126] Step 632: The payment terminal device performs rendering based on the second URL to obtain a payment page.

[0127] Step 634: The payment terminal device sends a service request to the application server in response to a user's triggering operation on a payment control on the payment page.

[0128] Step 636: The application server obtains the service request sent by the payment terminal device, and queries the service description information used to perform the service corresponding to the service request based on the information identifier included in the service request.

[0129] Step 638: The application server executes the service according to the identified service description information, obtains the service execution result information, and sends the service execution result information to the payment terminal device.

[0130] Step 640: The payment terminal device obtains the service execution result information, and presents the service execution result information to the user.

[0131] Steps 602 to 614 are a first URL generation stage, which may include information exchange between the NFC tag device and an application server. Steps 616 to 622 are a first URL transmission stage, which may include information exchange between the NFC tag device and a payment terminal device. Steps 624 to 632 are an app invocation stage, which may be executed in the payment terminal device. Steps 634 to 640 are a service execution stage, which may include information exchange between the payment terminal device and an application server.

[0132] Based on a similar idea, one or more embodiments herein further provide an apparatus for the above-described method.

[0133] 7 is a schematic diagram illustrating the structure of an apparatus for opening an NFC-based payment page corresponding to FIG. 2, in accordance with one or more embodiments herein. The apparatus for use in a payment terminal device includes: a URL acquisition module 702 configured to acquire a first URL from an NFC tag device based on a near field communication method, where the length of the first URL is equal to or less than the maximum number of bytes that can be transmitted at a time by the NFC tag device based on the near field communication method, and where the first URL includes a URL query identifier; a URL translation module 704 configured to determine a second URL corresponding to the URL query identifier based on data already stored by the payment terminal device, where the second URL includes target information used to display the payment page; and a display module 706 configured to display the payment page based on the second URL.

[0134] Based on the device of FIG. 7, one or more embodiments herein further provide several specific embodiments of the device, as described below.

[0135] Optionally, the apparatus comprises: an analysis module configured to analyze service parameter information of the first URL to obtain a third URL, the service parameter information including a URL query identifier and an information identifier, the information identifier being used to query service description information corresponding to the first URL; and an extraction module configured to extract the query identifier and the information identifier from the third URL.

[0136] Optionally, the URL conversion module 704 may specifically include: a URL template query unit configured to query a URL template based on a URL query identifier, the URL template including a location where the URL template should be filled; and a second URL acquisition unit configured to fill the location where the URL template should be filled with an information identifier and acquire a second URL, the second URL including target information, and the information identifier included in the target information.

[0137] Optionally, the target information may include a component identifier, a task identifier, and task parameters.

[0138] Accordingly, the display module 706 may specifically include: a first determination unit configured to determine a first application component corresponding to the component identifier; a second determination unit configured to determine a page rendering task corresponding to the task identifier; and a rendering unit configured to perform the page rendering task based on the task parameters by using the first application component to render a payment page.

[0139] Optionally, the rendering unit may specifically include: a page information acquiring subunit configured to acquire pre-stored page information based on the task parameters, where the page information includes at least one of photo information and copywriting information; and a rendering subunit configured to perform a page rendering task based on the page information by using the first application component to render the payment page.

[0140] Optionally, in the device, the task parameters further include amount information, the amount information including first amount information and second amount information, the first amount information representing a set amount value and the second amount information representing that no amount value is provided, and when the amount information is the first amount information, the set amount value is displayed on the payment page, and when the amount information is the second amount information, the amount value is not displayed on the payment page.

[0141] Optionally, the payment page may include payment controls.

[0142] Accordingly, the apparatus may further include: a service request sending module configured to send a service request to an application server based on a second URL in response to a user's trigger operation on a payment control, wherein the service request includes an information identifier, and the information identifier is used to query service description information corresponding to the first URL; a service execution result information receiving module configured to receive service execution result information returned by the application server, wherein the service execution result information is determined by the application server based on the service description information, and the service description information is obtained via a query by the application server based on the information identifier; and a payment result page display module configured to display a payment result page based on the service execution result information.

[0143] Optionally, the display module 706 may include a display unit specifically configured to directly display a payment page during a cold start of the application program.

[0144] Optionally, the apparatus may include a stack clearing module configured to perform stack clearing on the page stack during a hot start of the application program.

[0145] Optionally, the URL acquisition module 702 may specifically include: a signal sending unit configured to send a near field communication signal by using the payment terminal device as a primary NFC device; and a first URL acquisition unit configured to acquire a first URL sent by the NFC tag device via a near field communication method in response to the near field communication signal.

[0146] Optionally, the URL acquisition module 702 may specifically include: a first URL acquisition unit configured to acquire, by an operating system, a first URL provided by the NFC tag device via a near field communication method, where the first URL further includes domain name information; an application program determination unit configured to determine an application program corresponding to the domain name information; and a first URL sending unit configured to send the first URL to the application program.

[0147] Optionally, the first URL may further include path information.

[0148] Accordingly, the application program determination unit may specifically include an application program determination subunit configured to determine a second application component corresponding to the domain name information and the path information.

[0149] Accordingly, the first URL sending unit may specifically include a first URL sending subunit configured to send the first URL to the second application component.

[0150] 8 is a schematic diagram illustrating the structure of an NFC-based information transmission apparatus corresponding to FIG. 4, in accordance with one or more embodiments herein. The apparatus may include: a signal receiving module 802 for use in an NFC tag device, configured to receive a near field communication signal transmitted by a payment terminal device; and a signal transmitting module 804 configured to transmit a first URL to the payment terminal device via a near field communication method in response to the near field communication signal, wherein a length of the first URL is less than or equal to a maximum number of bytes that can be transmitted at one time by the NFC tag device based on the near field communication method, the first URL including a URL query identifier, the URL query identifier being used by the payment terminal device to determine a second URL, the second URL including target information used to display a payment page.

[0151] Optionally, the apparatus may further include a first acquisition module configured to acquire a predetermined trigger operation; a second acquisition module configured to acquire first service information in response to the trigger operation; a URL acquisition request sending module configured to send a URL acquisition request to an application server, the URL acquisition request including the first service information; and a first URL receiving module configured to receive a first URL returned by the application server, the first URL including an information identifier, the information identifier being used to query service description information, the service description information including the first service information and second service information, the second service information being information acquired by the application server and including information related to the service corresponding to the first URL.

[0152] 9 is a schematic diagram illustrating the structure of a URL transmission apparatus corresponding to FIG. 5, in accordance with one or more embodiments herein. The apparatus includes: a request acquisition module 902 for use in an application server and configured to acquire a URL acquisition request sent by an NFC tag device; a URL generation module 904 configured to generate a first URL in response to the URL acquisition request, where the length of the first URL is less than or equal to a predetermined byte threshold, the byte threshold being a maximum number of bytes that can be transmitted at one time based on NFC; and a URL transmission module 906 configured to transmit the first URL to the NFC tag device, where the first URL is used to be acquired by a payment terminal device from the NFC tag device via a near field wireless communication method, the first URL including a URL query identifier, the URL query identifier being used by the payment terminal device to query a second URL, the second URL including target information used by the payment terminal device to display a payment page.

[0153] Optionally, the URL generation module 904 may specifically include: a service scenario type determination unit configured to determine a service scenario type of the NFC tag device in response to the URL acquisition request; and a first URL generation unit configured to generate a first URL corresponding to the service scenario type, where a URL query identifier included in the first URL is used to query a second URL corresponding to the service scenario type.

[0154] Optionally, the URL generation module 904 may specifically include: an information identifier generation unit configured to generate an information identifier based on first service information included in the URL acquisition request, where the information identifier is used to query service description information corresponding to the first URL, the service description information including the first service information and second service information, the second service information being information acquired by the application server and including information related to the service corresponding to the first URL; and a first URL generation unit configured to generate a first URL including the information identifier.

[0155] Optionally, the apparatus may further include a service request acquisition module configured to acquire a service request transmitted by the payment terminal device, the service request including an information identifier; a service description information query module configured to query, based on the information identifier, service description information to be used for performing a service corresponding to the service request; a service execution result information acquisition module configured to perform the service based on the identified service description information and obtain service execution result information; and an execution result information transmission module configured to transmit the service execution result information to the payment terminal device.

[0156] Based on a similar idea, one or more embodiments herein further provide a device for the above-described method.

[0157] 10 is a schematic diagram illustrating the structure of a payment terminal device corresponding to FIG. 2, in accordance with one or more embodiments herein. As shown in FIG. 10, device 1000 may be a payment terminal device, the device 1000 comprising at least one processor 1010 and a memory 1030 communicatively connected to the at least one processor, the memory 1030 storing instructions 1020 executable by the at least one processor 1010, the instructions being executed by the at least one processor 1010 to: acquire a first URL from an NFC tag device based on a near field communication method, the length of the first URL being equal to or less than a maximum number of bytes that can be transmitted at a time by the NFC tag device based on the near field communication method, the first URL including a URL query identifier; determine a second URL corresponding to the URL query identifier based on data already stored by the payment terminal device, the second URL including target information used to display a payment page; and display the payment page based on the second URL.

[0158] 11 is a schematic diagram illustrating the structure of an NFC tag device corresponding to FIG. 4, in accordance with one or more embodiments herein. As shown in FIG. 11, device 1100 may be an NFC tag device, the device 1100 comprising at least one processor 1110 and a memory 1130 communicatively coupled to the at least one processor, the memory 1130 storing instructions 1120 executable by the at least one processor 1110, the instructions executed by the at least one processor 1110, which perform the following operations: receive a near field communication signal transmitted by a payment terminal device; and transmit a first URL to the payment terminal device via a near field communication method in response to the near field communication signal, the first URL having a length equal to or less than a maximum number of bytes that can be transmitted at one time by the NFC tag device based on the near field communication method, the first URL including a URL query identifier, the URL query identifier being used by the payment terminal device to determine a second URL, the second URL including target information used to display a payment page.

[0159] 12 is a schematic diagram illustrating the structure of an application server corresponding to FIG. 5, according to one or more embodiments of the present specification. As shown in FIG. 12, a device 1200 may be an application server, the device 1200 including at least one processor 1210 and a memory 1230 communicably connected to the at least one processor, the memory 1230 storing instructions 1220 executable by the at least one processor 1210, the instructions being executed by the at least one processor 1210, the at least one processor 1210 acquiring a URL acquisition request sent by an NFC tag device, and generating a first URL in response to the URL acquisition request, the first URL being acquired. the length of L is less than or equal to a predetermined byte threshold, the byte threshold being the maximum number of bytes that can be transmitted at one time based on NFC; and transmitting a first URL to the NFC tag device, the first URL being used to be obtained by the payment terminal device from the NFC tag device via a near field communication method, the first URL including a URL query identifier, the URL query identifier being used by the payment terminal device to query a second URL, the second URL including target information being used by the payment terminal device to display a payment page.

[0160] The embodiments herein are described in a progressive manner. Identical or similar parts in the embodiments may be referenced to each other. Each embodiment will focus on differences from other embodiments. Specifically, the device embodiments shown in Figures 10 to 12 are basically similar to the method embodiments, and will be briefly described. For relevant parts, reference may be made to the relevant descriptions of the method embodiments.

[0161] Specific embodiments of the present specification are described above. Other embodiments are within the scope of the following claims. In some cases, the actions or steps described in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes described in the accompanying figures do not necessarily require the particular order or sequential order shown to achieve desirable results. In some implementations, multitasking and simultaneous processing may be possible or advantageous.

[0162] In the 1990s, technological improvements were clearly distinguishable between hardware improvements (e.g., improvements to circuit structures such as diodes, transistors, or switches) and software improvements (improvements to method procedures). However, as technology has developed, many current improvements to method procedures can be considered direct improvements to hardware circuit structures. Designers typically program improved method procedures into hardware circuits to obtain corresponding hardware circuit structures. Thus, method procedures can be improved by using hardware entity modules. For example, programmable logic devices (PLDs) (e.g., field programmable gate arrays (FPGAs)) are such integrated circuits, and the logical functions of the programmable logic device are determined by the user through programming of the device. Designers independently perform programming to “build” digital systems into PLDs without requiring chip manufacturers to design and manufacture application-specific integrated circuit chips. Furthermore, now, instead of manually manufacturing integrated circuit chips, this type of programming is often performed by using “logic compiler” software. The programming is similar to the software compilers used to develop and write programs. The original code must be written in a specific programming language for compilation. The language is called a Hardware Description Language (HDL). There are many HDLs, such as Advanced Boolean Expression Language (ABEL), Altera Hardware Description Language (AHDL), Confluence, Cornell University Programming Language (CUPL), HDCal, Java Hardware Description Language (JHDL), Lava, Lola, MyHDL, PALASM, and Ruby Hardware Description Language (RHDL). Very High Speed ​​Integrated Circuit Hardware Description Language (VHDL) and Verilog are the most commonly used.Those skilled in the art will also understand that the method steps can be logically programmed using some of the described hardware description languages ​​and, when programmed into an integrated circuit, readily result in a hardware circuit that implements the logical method steps.

[0163] The controller may be implemented using any suitable method. For example, the controller may take the form of a microprocessor or processor, a computer-readable medium storing computer-readable program code (such as software or firmware) executable by the microprocessor or processor, logic gates, switches, an application-specific integrated circuit (ASIC), a programmable logic controller, and a built-in microprocessor. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. A memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will recognize that in addition to implementing a controller using computer-readable program code, logical programming of method steps may also be performed such that the controller implements the same function in the form of logic gates, switches, an application-specific integrated circuit, a programmable logic controller, a built-in microprocessor, etc. Thus, the controller may be considered a hardware component, and devices configured to implement various functions in the controller may be considered structures within the hardware component. Alternatively, the apparatus configured to implement various functions can even be thought of as both software modules that implement methods and structures within hardware components.

[0164] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or may be implemented by products having specific functions. A typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0165] For ease of explanation, the above-mentioned apparatus is described by dividing the functions into various units. Of course, in the embodiments herein, the functions of the units can be implemented in one or more pieces of software and / or hardware.

[0166] Those skilled in the art will appreciate that one or more embodiments of the present application may be provided as a method, a system, or a computer program product. Thus, the present application may use the form of a hardware-only embodiment, a software-only embodiment, or an embodiment that combines software and hardware. Furthermore, the present application may use the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk memory, CD-ROM, optical memory, etc.) that contains computer-usable program code.

[0167] The present application is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to one or more embodiments of the present application. It should be understood that each process and / or each block of the flowcharts and / or block diagrams, and combinations of processes and / or blocks of the flowcharts and / or block diagrams, can be implemented using computer program instructions. These computer program instructions are provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or another programmable data processing device to generate a machine, and the instructions, executed by the processor of the computer or another programmable data processing device, generate an apparatus for implementing the particular functionality of one or more processes of the flowcharts and / or one or more blocks of the block diagrams.

[0168] These computer program instructions may be stored in a computer-readable storage that can instruct a computer or another programmable data processing device to act in a particular manner, such that the instructions stored in the computer-readable storage produce a manufactured product that includes an instruction apparatus that implements a particular function of one or more processes in the flowcharts and / or one or more blocks in the block diagrams.

[0169] These computer program instructions may alternatively be loaded into a computer or other programmable data processing device such that a sequence of operations and steps are executed on the computer or other programmable device, thereby producing a computer-implemented process. Thus, the instructions executing on the computer or other programmable device provide steps for implementing a particular function of one or more processes in the flowcharts and / or one or more blocks in the block diagrams.

[0170] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0171] Memory may include non-persistent memory, random access memory (RAM), non-volatile memory, and / or other forms of computer-readable media, such as read-only memory (ROM) or flash read-only memory (flash ROM). Memory is an example of a computer-readable medium.

[0172] Computer-readable media include permanent and non-permanent, removable and non-removable media, and may implement information storage using any method or technology. Information may be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change random access memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory, or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disk (DVD), or other optical storage, cassette magnetic disk storage, magnetic tape / magnetic disk storage, other magnetic storage devices, or any other non-transmission medium. Computer storage media may be configured to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carriers.

[0173] It is further meaningful to note that the terms "include," "comprise," or any other variation thereof, are intended to include a non-exclusive inclusion, such that a process, method, product, or device that includes a list of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, product, or device. Absent further constraints, an element preceded by "includes a ..." does not exclude the presence of additional identical elements in a process, method, product, or device that includes that element.

[0174] This specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. This specification may alternatively be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media, including storage devices.

[0175] The above description is merely an embodiment of the present specification and is not intended to limit the present specification. Those skilled in the art can make various modifications and changes to the present specification. All modifications, equivalent replacements, or improvements made without departing from the spirit and principles of the present application fall within the scope of the claims of the present specification. [Explanation of symbols]

[0176] 101 Payment Terminal Device 102 NFC tag devices 702 URL Acquisition Module 704 URL Conversion Module 706 Display Module 802 signal receiving module 804 signal transmission module 902 Requirements Acquisition Module 904 URL Generation Module 906 URL sending module

Claims

1. 1. A method for opening an NFC-based payment page applied to a payment terminal device, comprising: acquiring a first URL from an NFC tag device based on a near field communication method, wherein a length of the first URL is equal to or less than a maximum number of bytes that can be transmitted at one time by the NFC tag device based on the near field communication method, and the first URL includes a URL query identifier; determining a second URL corresponding to the URL query identifier based on data already stored by the payment terminal device, the second URL including target information used to display a payment page; displaying the payment page based on the second URL; A method comprising:

2. Prior to the step of determining a second URL corresponding to the URL query identifier based on data already stored by the payment terminal device, the method further comprises: analyzing service parameter information of the first URL to obtain a third URL, the service parameter information including the URL query identifier and an information identifier, and the information identifier is used to query service description information corresponding to the first URL; extracting the URL query identifier and the information identifier from the third URL; The method of claim 1 further comprising:

3. The step of determining a second URL corresponding to the URL query identifier based on data already stored by the payment terminal device specifically includes: Querying a URL template based on the URL query identifier, the URL template having a location to be filled; filling the location to be filled with the information identifier and obtaining the second URL, wherein the second URL includes the target information and the information identifier is included in the target information; The method of claim 2, comprising:

4. the target information includes a component identifier, a task identifier, and task parameters; The step of displaying the payment page based on the second URL includes: determining a first application component corresponding to the component identifier; determining a page rendering task corresponding to the task identifier; executing the page rendering task based on the task parameters by using the first application component to render the payment page; 2. The method of claim 1, comprising:

5. The step of executing the page rendering task based on the task parameters by using the first application component to render the payment page specifically includes: obtaining pre-stored page information based on the task parameters, the page information including at least one of photo information and copywriting information; performing the page rendering task based on the page information by using the first application component to render the payment page; 5. The method of claim 4, comprising:

6. the task parameters further include monetary information, the monetary information includes first monetary information and second monetary information, the first monetary information represents a set monetary value, and the second monetary information represents that no monetary value is provided; When the amount information is the first amount information, the set amount value is displayed on the payment page; The method of claim 4 , wherein when the amount information is second amount information, an amount value is not displayed on the payment page.

7. The payment page includes a payment control, and after the step of displaying the payment page based on the second URL, the method further comprises: In response to a user's triggering of the payment control, sending a service request to an application server based on the second URL, the service request including an information identifier, the information identifier being used to query service description information corresponding to the first URL; receiving service execution result information returned by the application server, wherein the service execution result information is determined by the application server based on the service description information, and the service description information is obtained through a query by the application server based on the information identifier; displaying a payment result page based on the service execution result information; The method of claim 1 , comprising:

8. The step of displaying the payment page based on the second URL specifically includes: The method of claim 1 , including the step of directly displaying the payment page during a cold start of an application program.

9. Before the step of displaying the payment page based on the second URL, the method further comprises: The method of claim 1 , comprising performing stack clearing on a page stack during a hot start of an application program.

10. The step of acquiring a first URL from the NFC tag device based on a near field communication method specifically includes: transmitting near field communication signals by using the payment terminal device as a primary NFC device; acquiring the first URL transmitted by the NFC tag device via the near field communication method in response to the near field communication signal; 2. The method of claim 1, comprising:

11. The step of acquiring a first URL from the NFC tag device based on a near field communication method specifically includes: acquiring, by an operating system, the first URL provided by the NFC tag device in the near field communication method, wherein the first URL further includes domain name information; determining an application program corresponding to the domain name information; sending the first URL to the application program; 2. The method of claim 1, comprising:

12. The first URL further includes path information, and the step of determining the application program corresponding to the domain name information specifically includes: determining a second application component corresponding to the domain name information and the path information; The step of transmitting the first URL to the application program specifically includes: The method of claim 11 , further comprising sending the first URL to the second application component.

13. 1. An NFC-based information transmission method applied to an NFC tag device, comprising: receiving a near field communication signal transmitted by a payment terminal device; transmitting a first URL to the payment terminal device via a near field communication method in response to the near field communication signal, wherein a length of the first URL is equal to or less than a maximum number of bytes that can be transmitted at one time by the NFC tag device based on the near field communication method, the first URL including a URL query identifier, the URL query identifier being used by the payment terminal device to determine a second URL, the second URL including target information used to display a payment page; A method comprising:

14. Prior to the step of receiving a near field communication signal transmitted by the payment terminal device, the method further comprises: Obtaining a predetermined trigger operation; acquiring first service information in response to the trigger operation; sending a URL acquisition request to an application server, the URL acquisition request including the first service information; receiving the first URL returned by the application server, the first URL including an information identifier, the information identifier being used to query service description information, the service description information including first service information and second service information, the second service information being information obtained by the application server and including information related to the service corresponding to the first URL; The method of claim 13, comprising:

15. A URL transmission method applied to an application server, comprising: acquiring a URL acquisition request sent by an NFC tag device; generating a first URL in response to the URL acquisition request, wherein a length of the first URL is equal to or less than a predetermined byte threshold, the byte threshold being a maximum number of bytes that can be transmitted at one time based on NFC; sending the first URL to the NFC tag device, the first URL being used to be acquired by a payment terminal device from the NFC tag device via a near field communication method, the first URL including a URL query identifier, the URL query identifier being used by the payment terminal device to query a second URL, the second URL including target information being used by the payment terminal device to display a payment page; A method comprising:

16. The step of generating a first URL in response to the URL acquisition request specifically includes: determining a service scenario type of the NFC tag device in response to the URL acquisition request; generating a first URL corresponding to the service scenario type, wherein the URL query identifier included in the first URL is used to query a second URL corresponding to the service scenario type; 16. The method of claim 15, comprising:

17. The step of generating a first URL in response to the URL acquisition request specifically includes: generating an information identifier based on first service information included in the URL acquisition request, wherein the information identifier is used to query service description information corresponding to the first URL, the service description information including the first service information and second service information, and the second service information is information acquired by the application server and includes information related to the service corresponding to the first URL; generating a first URL including the information identifier; 16. The method of claim 15, comprising:

18. After the step of transmitting the first URL to the NFC tag device, the method further comprises: obtaining a service request transmitted by the payment terminal device, the service request including the information identifier; querying, based on the information identifier, service description information used to perform a service corresponding to the service request; executing the service based on the identified service description information and obtaining service execution result information; sending the service execution result information to the payment terminal device; The method of claim 17, comprising:

19. 1. An NFC-based payment page opening apparatus for use in a payment terminal device, comprising: a URL acquisition module configured to acquire a first URL from an NFC tag device based on a near field communication method, wherein a length of the first URL is equal to or less than a maximum number of bytes that can be transmitted at one time by the NFC tag device based on the near field communication method, and the first URL includes a URL query identifier; a URL translation module configured to determine a second URL corresponding to the URL query identifier based on data already stored by the payment terminal device, the second URL including target information used to display a payment page; and a display module configured to display the payment page based on the second URL; and An apparatus comprising:

20. 1. An NFC-based information transmission device for use in an NFC tag device, comprising: a signal receiving module configured to receive a near field communication signal transmitted by the payment terminal device; a signal transmission module configured to transmit a first URL to the payment terminal device via a near field communication method in response to the near field communication signal, the first URL having a length equal to or less than a maximum number of bytes that can be transmitted at one time by the NFC tag device based on the near field communication method, the first URL including a URL query identifier, the URL query identifier being used by the payment terminal device to determine a second URL, the second URL including target information used to display a payment page; and An apparatus comprising:

21. A URL transmission device used in an application server, comprising: a request acquisition module configured to acquire a URL acquisition request sent by the NFC tag device; a URL generation module configured to generate a first URL in response to the URL acquisition request, wherein a length of the first URL is less than or equal to a predetermined byte threshold, the byte threshold being a maximum number of bytes that can be transmitted at one time based on NFC; and a URL transmission module configured to transmit the first URL to the NFC tag device, the first URL being used to be acquired by a payment terminal device from the NFC tag device via a near field communication method, the first URL including a URL query identifier, the URL query identifier being used by the payment terminal device to query a second URL, the second URL including target information being used by the payment terminal device to display a payment page; An apparatus comprising:

22. 1. A payment terminal device, comprising: at least one processor; a memory communicatively connected to the at least one processor; The memory stores instructions executable by the at least one processor, the instructions comprising: acquiring a first URL from an NFC tag device based on a near field communication method, wherein a length of the first URL is equal to or less than a maximum number of bytes that can be transmitted at one time by the NFC tag device based on the near field communication method, and the first URL includes a URL query identifier; determining a second URL corresponding to the URL query identifier based on data already stored by the payment terminal device, the second URL including target information used to display a payment page; displaying the payment page based on the second URL; and a payment terminal device, wherein the payment terminal device is executed by the at least one processor so that the at least one processor can perform the following:

23. An NFC tag device, at least one processor; a memory communicatively connected to the at least one processor; The memory stores instructions executable by the at least one processor, the instructions comprising: receiving a near field communication signal transmitted by a payment terminal device; transmitting a first URL to the payment terminal device via a near field communication method in response to the near field communication signal, wherein a length of the first URL is equal to or less than a maximum number of bytes that can be transmitted at one time by the NFC tag device based on the near field communication method, the first URL including a URL query identifier, the URL query identifier being used by the payment terminal device to determine a second URL, the second URL including target information used to display a payment page; and a NFC tag device, wherein the NFC tag device is executed by the at least one processor so that the at least one processor can perform the following.

24. an application server, at least one processor; a memory communicatively connected to the at least one processor; The memory stores instructions executable by the at least one processor, the instructions comprising: Acquiring a URL acquisition request sent by an NFC tag device; generating a first URL in response to the URL acquisition request, wherein a length of the first URL is equal to or less than a predetermined byte threshold, the byte threshold being a maximum number of bytes that can be transmitted at one time based on NFC; sending the first URL to the NFC tag device, the first URL being used to be acquired by a payment terminal device from the NFC tag device via a near field communication method, the first URL including a URL query identifier, the URL query identifier being used by the payment terminal device to query a second URL, the second URL including target information being used by the payment terminal device to display a payment page; an application server executed by the at least one processor so that the at least one processor can perform the following:

Images