NFC-based method and apparatus for opening page, NFC-based method and apparatus for sending information, and devices

Abstract

Disclosed in the embodiments of the present description are a near field communication (NFC)-based method and apparatus for opening a payment page, a device, an NFC-based method and apparatus for sending information, a device, and a method and apparatus for sending a URL, and a device. A solution may comprise: after acquiring, on the basis of the NFC mode, from an NFC tag device a first URL comprising a URL query identifier, a payment terminal device may determine, on the basis of data stored in the payment terminal device, a second URL which corresponds to the URL query identifier and comprises target information for displaying a payment page, thereby displaying the payment page on the basis of the second URL, wherein the length of the first URL is less than or equal to the maximum number of bytes that the NFC tag device can transmit in a single operation on the basis of the near field communication mode.

Description

Method, device and equipment for opening page and information sending based on NFC

[0001] The present application claims priority from a Chinese patent application No. 202411092836.9 filed on August 8, 2024, and entitled "Method, device and equipment for opening page and information sending based on NFC", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present specification relates to the technical field of near field payment, and in particular to a method, device and equipment for opening a payment page based on NFC, a method, device and equipment for information sending based on NFC, and a method, device and equipment for sending a URL. BACKGROUND

[0003] Near field communication (NFC) payment refers to a payment process in which a consumer uses a user terminal supporting NFC function to communicate with a NFC tag device such as a POS cash register or a vending machine through an NFC radio frequency channel to complete payment when purchasing goods or services. NFC payment is a new mobile payment method, and the consumer only needs to bring the mobile phone close to the NFC tag device provided by the merchant to make payment, without the need to scan the code, which is more convenient. At present, in the NFC payment process, the time used for the process from the user terminal approaching the NFC tag device to the payment page being displayed in the user terminal is relatively long, which leads to poor user experience.

[0004] Therefore, how to reduce the time consumption for opening a payment page in the NFC payment process and improve the calling terminal speed has become a technical problem to be solved urgently.

[0005] SUMMARY

[0006] The method, device and equipment for opening a payment page based on NFC, the method, device and equipment for information sending based on NFC, and the method, device and equipment for sending a URL provided by the embodiments of the present specification can effectively reduce the time consumption for opening a payment page in the NFC payment process and improve the calling terminal speed.

[0007] To solve the above technical problems, the embodiments of the present specification provide a method for opening a payment page based on NFC, applied to a payment terminal device, comprising: obtaining a first URL from an NFC tag device based on a near field communication mode; the length of the first URL is less than or equal to the maximum number of bytes that the NFC tag device can transmit at a time based on the near field communication mode; the first URL contains a URL query identifier; determining a second URL corresponding to the URL query identifier based on the data stored by the payment terminal device; the second URL contains target information for displaying the payment page; and displaying the payment page based on the second URL.

[0008] The embodiments of the present specification also provide a method for sending information based on NFC, applied to an NFC tag device, comprising: receiving a near field communication signal transmitted by a payment terminal device; in response to the near field communication signal, sending a first URL to the payment terminal device through a near field communication mode; the length of the first URL is less than or equal to the maximum number of bytes that the NFC tag device can transmit at a time based on the near field communication mode; the first URL contains a URL query identifier; the URL query identifier is used to determine a second URL by the payment terminal device; and the second URL contains target information for displaying a payment page.

[0009] The embodiments of the present specification also provide a method for sending a URL, applied to an application server, comprising: obtaining a URL acquisition request sent by an NFC tag device; in response to the URL acquisition request, generating a first URL; the length of the first URL is less than or equal to a preset byte number threshold; the byte number threshold is the maximum number of bytes that can be transmitted at a time based on NFC; sending the first URL to the NFC tag device; the first URL is used to be obtained from the NFC tag device by a payment terminal device in a near field communication mode; the first URL contains a URL query identifier; the URL query identifier is used to query a second URL by the payment terminal device, and the second URL contains target information for displaying a payment page by the payment terminal device.

[0010] The embodiment of the present specification further provides a device for opening a payment page based on NFC, applied to a payment terminal device, comprising: a URL obtaining module, configured to obtain a first URL from an NFC tag device based on a near field communication mode; the length of the first URL is less than or equal to the maximum number of bytes that can be transmitted by the NFC tag device in a single time based on the near field communication mode; the first URL contains a URL query identifier; a URL conversion module, configured to determine a second URL corresponding to the URL query identifier based on the data stored in the payment terminal device; the second URL contains target information for displaying the payment page; and a display module, configured to display the payment page based on the second URL.

[0011] The embodiment of the present specification further provides a device for sending information based on NFC, applied to an NFC tag device, comprising: a signal receiving module, configured to receive a near field communication signal transmitted by a payment terminal device; a signal sending module, configured to send a first URL to the payment terminal device through a near field communication mode in response to the near field communication signal; the length of the first URL is less than or equal to the maximum number of bytes that can be transmitted by the NFC tag device in a single time based on the near field communication mode; the first URL contains a URL query identifier; the URL query identifier is used to determine a second URL by the payment terminal device; and the second URL contains target information for displaying a payment page.

[0012] The embodiment of the present specification further provides a device for sending a URL, applied to an application server, comprising: a request obtaining module, configured to obtain a URL obtaining request sent by an NFC tag device; a URL generating module, configured to generate a first URL in response to the URL obtaining request; the length of the first URL is less than or equal to a preset byte number threshold; the byte number threshold is the maximum number of bytes that can be transmitted in a single time based on NFC; a URL sending module, configured to send the first URL to the NFC tag device; the first URL is used to be obtained from the NFC tag device by a payment terminal device in a near field communication mode; the first URL contains a URL query identifier; and the URL query identifier is used to query a second URL by the payment terminal device, and the second URL contains target information for displaying a payment page by the payment terminal device.

[0013] The embodiment of the present specification further provides a payment terminal device, comprising: at least one processor; and a memory in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: acquire a first URL from an NFC tag device based on a near field communication mode; the length of the first URL is less than or equal to the maximum number of bytes that the NFC tag device can transmit at a time based on the near field communication mode; the first URL contains a URL query identifier; determine a second URL corresponding to the URL query identifier based on the data stored by the payment terminal device; the second URL contains target information for displaying the payment page; and display the payment page based on the second URL.

[0014] The embodiment of the present specification further provides an NFC tag device, comprising: at least one processor; and a memory in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: receive a near field communication signal transmitted by a payment terminal device; in response to the near field communication signal, send a first URL to the payment terminal device through a near field communication mode; the length of the first URL is less than or equal to the maximum number of bytes that the NFC tag device can transmit at a time based on the near field communication mode; the first URL contains a URL query identifier; the URL query identifier is used to determine a second URL by the payment terminal device; and the second URL contains target information for displaying a payment page.

[0015] The embodiment of the present specification further provides an application server, comprising: at least one processor; and a memory in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: acquire a URL acquisition request sent by an NFC tag device; in response to the URL acquisition request, generate a first URL; the length of the first URL is less than or equal to a preset byte number threshold; the byte number threshold is the maximum number of bytes that can be transmitted at a time based on NFC; send the first URL to the NFC tag device; the first URL is used to be acquired from the NFC tag device by a payment terminal device in a near field communication mode; the first URL contains a URL query identifier; and the URL query identifier is used to query a second URL by the payment terminal device, and the second URL contains target information for displaying a payment page by the payment terminal device.

[0016] At least one of the embodiments provided in the specification can achieve the following beneficial effects: In the embodiments of the specification, since the length of the first URL obtained by the payment terminal device from the NFC tag device based on the near field communication mode is not greater than the maximum number of bytes that can be transmitted by the NFC tag device based on the near field communication mode in a single time, the situation that the NFC tag device needs to transmit the URL to the payment terminal device multiple times due to the length of the URL is avoided, thereby improving the transmission efficiency of information transmission between the NFC tag device and the payment terminal device, and effectively reducing the information transmission time. Moreover, the first URL transmitted by the NFC tag device to the payment terminal device through the near field communication mode carries a URL query identifier, and the payment terminal device can determine the second URL needed for displaying the payment page based on the URL query identifier and the stored data, thereby obtaining the second URL corresponding to the first URL through local query, and then opening the payment page based on the second URL. The process of opening the payment page does not need to access the network, further reducing the time consumption of opening the payment page in the NFC payment process, effectively improving the speed of calling the terminal, and thereby improving the user experience and the NFC payment efficiency. BRIEF DESCRIPTION OF DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the embodiments of the specification or the prior art, the drawings needed to be used in the embodiments or the prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments described in the present application, and those skilled in the art can also obtain other drawings according to these drawings without creative labor.

[0018] FIG. 1 is a schematic diagram of an application scenario of a method for opening a payment page based on NFC provided by an embodiment of the specification;

[0019] FIG. 2 is a flowchart of a method for opening a payment page based on NFC provided by an embodiment of the specification;

[0020] FIG. 3a is a schematic diagram of a payment page provided by an embodiment of the specification;

[0021] FIG. 3b is a schematic diagram of another payment page provided by an embodiment of the specification;

[0022] FIG. 4 is a flowchart of a method for sending information based on NFC provided by an embodiment of the specification;

[0023] FIG. 5 is a flowchart of a method for sending a URL provided by an embodiment of the specification;

[0024] FIG. 6 is a swim lane diagram of a method for opening a payment page based on NFC corresponding to FIG. 2 provided by an embodiment of the specification;

[0025] FIG. 7 is a structural diagram of an NFC-based opening payment page device corresponding to FIG. 2 according to an embodiment of the present specification;

[0026] FIG. 8 is a structural diagram of an NFC-based information sending device corresponding to FIG. 4 according to an embodiment of the present specification;

[0027] FIG. 9 is a structural diagram of a URL sending device corresponding to FIG. 5 according to an embodiment of the present specification;

[0028] FIG. 10 is a structural diagram of a payment terminal device corresponding to FIG. 2 according to an embodiment of the present specification;

[0029] FIG. 11 is a structural diagram of an NFC tag device corresponding to FIG. 4 according to an embodiment of the present specification;

[0030] FIG. 12 is a structural diagram of an application server corresponding to FIG. 5 according to an embodiment of the present specification. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical solutions and advantages of one or more embodiments of the present specification clearer, the technical solutions of one or more embodiments of the present specification will be described clearly and completely below in conjunction with specific embodiments of the present specification and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present specification, rather than all the embodiments. Based on the embodiments in the present specification, all other embodiments obtained by those skilled in the art without creative work belong to the scope of protection of one or more embodiments of the present specification.

[0032] It should be understood that although the terms first, second, etc. can be used in one or more embodiments of the present application to describe various information, these information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of one or more embodiments of the present application, first can also be referred to as second, and similarly, second can also be referred to as first. Depending on the context, the word "if" as used herein can be interpreted as "when" or "upon" or "in response to determining".

[0033] 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 for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards in relevant regions, and provide corresponding operation portal for user to choose authorization or refusal.

[0034] In the prior art, the process of calling the terminal based on NFC payment is time-consuming, and the user needs to wait for a long time to see the payment page, which is not good for user experience. The reasons for this situation are mainly as follows: (1) In the process of NFC communication, the uniform resource locator (URL) transmitted by the NFC tag device to the payment terminal device is long. Since the communication standard of NFC stipulates the maximum number of bytes per packet, when the number of bytes of the URL to be transmitted exceeds the maximum number of bytes that can be transmitted by the NFC tag device based on near field communication at a time, it needs to be sent in multiple packets, which results in a long process of sending the URL from the NFC tag device to the payment terminal device. (2) The payment terminal device needs to request the code platform server to decode after obtaining the URL through network request, and then enter the payment page. The process of calling the terminal needs to make multiple network requests, which increases the time of calling the terminal.

[0035] In order to solve the defects in the prior art, the present scheme provides the following embodiments.

[0036] Figure 1 is a schematic diagram of an application scenario of a method for opening a payment page based on NFC provided by an embodiment of the present specification.

[0037] As shown in Figure 1, when the user needs to use the payment terminal device 101 he carries to make an order payment, he can open the NFC function of the payment terminal device 101 and then paste the payment terminal device 101 close to the NFC tag device 102 set by the merchant. After the NFC tag device 102 senses the NFC radio frequency field of the payment terminal device 101, it can send a first URL carrying a URL query identifier to the payment terminal device 101 at a time based on near field communication (wherein the length of the first URL is less than or equal to the maximum number of bytes that can be transmitted by the NFC tag device 102 based on near field communication at a time). After the payment terminal device 101 receives the first URL sent by the NFC tag device 102 based on near field communication, it can determine the second URL corresponding to the URL query identifier based on the data stored in the payment terminal device 101, and further render the payment page according to the second URL to display to the user.

[0038] The method in FIG. 1 avoids the situation that the NFC tag device needs to transmit the URL to the payment terminal device for multiple times due to the length of the first URL obtained by the payment terminal device from the NFC tag device based on the near field communication mode being greater than the maximum number of bytes that the NFC tag device can transmit at a single time based on the near field communication mode, thereby improving the transmission efficiency of information transmission between the NFC tag device and the payment terminal device and effectively reducing the information transmission time. Moreover, the first URL transmitted by the NFC tag device to the payment terminal device based on the near field communication mode carries the URL query identifier, and the payment terminal device can determine the second URL needed for displaying the payment page based on the URL query identifier and the stored data, thereby obtaining the second URL corresponding to the first URL through local query without network access, further reducing the time consumption for opening the payment page in the NFC payment process, effectively improving the opening speed, and further improving the user experience and the NFC payment efficiency.

[0039] FIG. 2 is a flowchart of a method for opening a payment page based on NFC provided in an embodiment of the present specification. From the hardware perspective, the execution subject of the flowchart can be a payment terminal device. From the program perspective, the execution subject of the flowchart can be an application program loaded on the payment terminal device. As shown in FIG. 2, the flowchart can include the following steps:

[0040] Step 202: obtaining a first URL from an NFC tag device based on a near field communication mode; the length of the first URL is less than or equal to the maximum number of bytes that the NFC tag device can transmit at a single time based on the near field communication mode; and the first URL contains a URL query identifier.

[0041] In the embodiment of the present specification, the NFC tag device can be a payment collection device set by a merchant in an offline payment scenario. The payment terminal device can be a smart phone supporting NFC function carried by a user, or other devices supporting NFC function and capable of completing NFC payment, which is not limited in particular.

[0042] In actual application, the maximum number of bytes that the NFC tag device can transmit at a single time based on the near field communication mode is usually 124 bytes, and therefore, the length of the first URL transmitted by the NFC tag device to the payment terminal device of the user based on the near field communication mode can be less than 124 bytes or equal to 124 bytes.

[0043] In the embodiment of the present application, since the length of the first URL obtained by the payment terminal device from the NFC tag device based on the near field communication mode is not greater than the maximum number of bytes that can be transmitted by the NFC tag device in a single time based on the near field communication mode, the situation that the NFC tag device needs to transmit the URL to the payment terminal device in multiple times due to the length of the URL is avoided, thereby improving the transmission efficiency of information transmission between the NFC tag device and the payment terminal device and effectively reducing the information transmission time.

[0044] In step 204, the second URL corresponding to the URL query identifier is determined based on the data stored by the payment terminal device. The second URL contains target information for displaying a payment page.

[0045] In actual application, different scene types can correspond to different second URLs. For example, the second URL of the NFC payment scene based on the POS machine can be different from the second URL of the NFC payment scene of the vending machine. Therefore, the URL query identifier for querying the second URL is related to the scene type. Different payment scenes can correspond to different URL query identifiers, different URL query identifiers can query different second URLs, and different payment pages can be displayed for users based on different second URLs. For example, different URL query identifiers can be used in different scenes such as POS machine payment and vending machine payment.

[0046] In the embodiment of the present application, the mapping relationship between the URL query identifier and the URL template can be included in the data stored by the payment terminal device. After the payment terminal device obtains the first URL, the URL template corresponding to the URL query identifier in the first URL can be queried based on the mapping relationship between the URL query identifier and the URL template stored locally. Then, the information identifier carried in the first URL is filled into the to-be-filled position of the URL template, and the second URL can be obtained. Since the subsequent embodiments of the present application will explain the process of determining the second URL in detail, the description is omitted here.

[0047] In step 206, the payment page is displayed based on the second URL.

[0048] In the embodiment of the present application, the target information for displaying the payment page included in the second URL can be information required for rendering the payment page, such as text information, image information, and amount information. After the payment terminal device determines the second URL, the payment page can be directly rendered based on the target information for displaying the payment page included in the second URL.

[0049] In the embodiment of the present specification, the first URL transmitted by the NFC tag device to the payment terminal device through the near field communication mode carries a URL query identifier, and the payment terminal device can determine the second URL required for displaying the payment page based on the URL query identifier and the stored data, so as to obtain the second URL corresponding to the first URL through local query, without network access, further reducing the time consumption of opening the payment page in the NFC payment process, effectively improving the speed of calling the terminal, and further improving the user experience and NFC payment efficiency.

[0050] The method in FIG. 2 avoids the case that the NFC tag device needs to perform multiple package transmissions to 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 reducing the information transmission time. Moreover, the first URL transmitted by the NFC tag device to the payment terminal device through the near field communication mode carries a URL query identifier, and the payment terminal device can determine the second URL required for displaying the payment page based on the URL query identifier and the stored data, so as to obtain the second URL corresponding to the first URL through local query, and then open the payment page based on the second URL. In the process of opening the payment page, network access is not required, further reducing the time consumption of opening the payment page in the NFC payment process, effectively improving the speed of calling the terminal, and further improving the user experience and NFC payment efficiency.

[0051] Based on the method in FIG. 2, the present specification also provides some specific implementation schemes of the method, which are described below.

[0052] In actual application, after the payment terminal device obtains the first URL, the main process of the corresponding application program can be started according to the protocol header information in the first URL. The main process of the application program can analyze the business parameter information after the protocol header in the first URL to obtain a new URL, and extract the identifier information required for determining the second URL from the new URL.

[0053] Based on this, in step 204 of the method in FIG. 2, before determining the second URL corresponding to the URL query identifier based on the stored data of the payment terminal device, the following steps can be further included:

[0054] The service parameter information in the first URL is parsed to obtain a third URL; the service parameter information includes the URL query identifier and an information identifier; the information identifier is used to query service description information corresponding to the first URL.

[0055] The URL query identifier and the information identifier are extracted from the third URL.

[0056] In the embodiments of the present disclosure, the service parameter information in the first URL can refer to information after a parameter designation character (for example, scheme) in the link. For example, 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 can determine, according to information in the protocol header, that the URL is a URL for applying for NFC payment by using Alipay, so as to start a main process of Alipay. After the main process of Alipay is started, the service parameter information alipay%1A2B3c4d%1A2B3c4dCCC%5e6F${token}_${amount} after the designated character scheme can be parsed to obtain a third URL after parsing: alipay: / / nfc / app?s=CCC&v=${token}_${amount}, where CCC can represent the URL query identifier, ${token} can represent the information identifier, and ${amount} can represent the amount of money. It should be noted that CCC, ${token} and ${amount} can represent positions of the identifiers or information in the URL. In actual application, CCC, token and amount can be specific strings, for example, a 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 of money is specifically 0.01.

[0057] As described above, after the third URL is obtained, the URL query identifier and the information identifier can be extracted according to the composition structure of the third URL by using a preset URL processing flow.

[0058] In actual application, the service description information corresponding to the first URL can be related information of an order, which can include but is not limited to an order number, a merchant number, an order placing time, a first URL generation time, an order payment time limit, a payment user identifier, and an order payment result. The service description information can be stored in an application server. The application server can randomly generate an information identifier, and store an information identifier and service description information of an order in association, so that the first URL carrying the information identifier and the order associated with the information identifier are in a corresponding relationship. Thus, after the information identifier is obtained, the service description information of the corresponding order can be queried from the application server based on the information identifier.

[0059] In the embodiments of the present specification, after the URL query identifier is extracted from the third URL, the corresponding second URL template required for generating the second URL can be determined based on the URL query identifier.

[0060] Based on this, in the method in FIG. 2, in step 204, the second URL corresponding to the URL query identifier is determined based on the data stored in the payment terminal device, which can specifically include:

[0061] According to the URL query identifier, a URL template is queried; the URL template includes a to-be-filled position;

[0062] The information identifier is filled into the to-be-filled position to obtain the second URL; the second URL contains the target information; and the information identifier is carried in the target information.

[0063] In the embodiments of the present specification, the mapping relationship between the URL query identifier and the URL template can be included in the data stored in the payment terminal device. Thus, the URL template corresponding to the URL query identifier can be queried according to the mapping relationship. Then, the information identifier extracted from the third URL is filled into the to-be-filled position in the URL template, so that the second URL containing the target information for displaying the payment page can be obtained.

[0064] In actual application, if the first URL obtained by the payment terminal device further includes the amount information, the information identifier and the amount information can be filled into the to-be-filled position in the URL template to obtain a second URL including the amount information. Of course, if the first URL does not include the amount information, only the information identifier needs to be filled into the to-be-filled position in the URL template to obtain the second URL. For example, still taking the third URL as alipay: / / nfc / app?s=sn&v=1q2w3e4r5t6y7u8i_0.01, where the URL query identifier is sn, the information identifier is 1q2w3e4r5t6y7u8i, and the amount information is 0.01, 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 to-be-filled position. After the information identifier 1q2w3e4r5t6y7u8i and the amount information 0.01 are filled into the to-be-filled position in the URL template, the second URL alipays: / / platformapi / startApp?appId=112233&appScheme=NFC_ABC&pageParams=%12345qwert1q2w3e4r5t6y7u8i_0.01%6789 can be obtained.

[0065] In the embodiments of the present specification, the target information included in the second URL can include a component identifier, a task identifier, and a task parameter.

[0066] Correspondingly, in the method in FIG. 2, in step 206, the payment page is displayed based on the second URL, and specifically can include:

[0067] determining a first application component corresponding to the component identifier;

[0068] determining a page rendering task corresponding to the task identifier;

[0069] performing the page rendering task based on the task parameter by using the first application component to render the payment page.

[0070] In the embodiments of the present disclosure, different component identifiers can correspond to different application components, different task identifiers can correspond to different page rendering tasks, and different task parameters can be used to render different pages. The following takes an example to specifically illustrate the component identifier, the task identifier and the task parameter contained in the second URL. Take the second URL alipays: / / platformapi / startApp?appId=112233&appScheme=NFC_ABC&pageParams=%12345qwert1q2w3e4r5t6y7u8i_0.01%6789 as an example, where 112233 is a specific component identifier, NFC ABC is a specific task identifier, and %12345qwert1q2w3e4r5t6y7u8i_0.01%6789 is a specific task parameter. As can be seen, the information identifier (1q2w3e4r5t6y7u8i) is carried in the task parameter.

[0071] In the embodiments of the present disclosure, the first application component is a component in an application program of a payment terminal device for rendering a payment page based on the second URL. Specifically, the first application component can be an Activity component. In actual application, the page corresponding to the Activity component can be set to be visible to a user, so that during the running of the first application component, the application program can render the payment page corresponding to the second URL and show the payment page to the user.

[0072] In the embodiments of the present disclosure, the first application component is a component in an application program of a payment terminal device for rendering a payment page based on the second URL. Specifically, the first application component can be an Activity component. In actual application, the page corresponding to the Activity component can be set to be visible to a user, so that during the running of the first application component, the application program can render the payment page corresponding to the second URL and show the payment page to the user.

[0073] In actual application, when a preset condition is met, for example, when the native payment page has a fatal problem and cannot be used, or when a new capability needs to be urgently released, the payment page can also be rendered in the container mode to maximize the guarantee that the user can successfully open the payment page in the case that the payment page cannot be rendered in the native mode.

[0074] In the embodiments of the present disclosure, the payment page is the landing page of the terminal operation, or in other words, displaying the payment page means that the terminal is successful, and the first page that the user can see after initiating the NFC code scanning payment is the payment page.

[0075] In the embodiments of the present disclosure, the first application component is a component in an application program of a payment terminal device for rendering a payment page based on the second URL. Specifically, the first application component can be an Activity component. In actual application, the page corresponding to the Activity component can be set to be visible to a user, so that during the running of the first application component, the application program can render the payment page corresponding to the second URL and show the payment page to the user.

[0076] based on the task parameter, obtaining pre-stored page information; the page information includes at least one of picture information and text information;

[0077] based on the page information, performing the page rendering task by using the first application component to render a payment page.

[0078] In the embodiments of the present specification, the pre-stored page information obtained based on the task parameter can determine the information contained in the rendered payment page. If the pre-stored page information obtained based on the task parameter includes picture information and text information, the payment page rendered based on these page information can contain both picture information and text information.

[0079] In actual application, the picture information in the page information can include but is not limited to: NFC payment scene picture, NFC payment operation process guidance picture, NFC payment preferential activity picture, etc. The text information in the page information can include but is not limited to: "pay by touching, come and experience", "pay and paste", "NFC payment, be one step ahead", etc.

[0080] In the embodiments of the present specification, the task parameter contained in the second URL can also carry amount information; the amount information can include first amount information or second amount information; the first amount information represents a set amount value; the second amount information represents no provided amount value.

[0081] In the case where the amount information is the first amount information, the payment page displays the set amount value.

[0082] In the case where the amount information is the second amount information, the payment page does not display the amount value.

[0083] In the embodiments of the present specification, if the payment terminal device of the user obtains the first URL which does not include the amount information, the amount information in the task parameter contained in the second URL corresponds to the second amount information, and the payment page finally displayed for the user does not display the amount value. FIG. 3a is a schematic diagram of a payment page provided by the embodiments of the present specification, as shown in FIG. 3a, the payment page does not display the amount value.

[0084] In the embodiments of the present application, if the payment terminal device of the user acquires the first URL including the amount information, the amount information in the task parameter included in the second URL corresponds to the first amount information, and the payment page finally displayed for the user displays the amount value. FIG. 3b is a schematic diagram of another payment page provided by the embodiments of the present application. As shown in FIG. 3b, the payment page displays the amount value to be paid by the user as 0.01 yuan.

[0085] In actual application, after the payment terminal device of the user displays the payment page, the user can click the payment control in the payment page to indicate the user's consent to the payment. After obtaining the consent of the user, the payment terminal device can send a service request for performing the payment processing of the order to the application server, so that the application server can perform the subsequent payment processing based on the information carried in the service request.

[0086] Based on this, the payment page can further include a payment control.

[0087] Correspondingly, in the method of FIG. 2, after displaying the payment page based on the second URL in step 206, the method can further include:

[0088] In response to the triggering operation of the user on the payment control, a service request is sent to the application server based on the second URL; the service request carries an information identifier; the information identifier is used to query the business description information corresponding to the first URL;

[0089] Business execution result information returned by the application server is received; the business execution result information is determined by the application server according to the business description information; the business description information is obtained by the application server according to the information identifier;

[0090] Based on the business execution result information, a payment result page is displayed.

[0091] In the embodiments of the present application, the payment control in the payment page can specifically include a payment confirmation control. In actual application, the payment control can also specifically include a payment cancellation control. The payment page can simultaneously include the payment confirmation control and the payment cancellation control for the user to select; or as shown in FIG. 3b, the payment control included is "Confirm Payment" and no payment cancellation control is included. The setting of the payment control can be flexibly set and adjusted according to actual needs.

[0092] In actual application, the application program for performing the NFC payment processing at the payment terminal device needs to be started before displaying the payment page for the user, and the starting of the application program includes cold starting and hot starting, and the corresponding terminal processes of the two starting modes are different.

[0093] Based on this, in the method in FIG. 2, in step 206, displaying the payment page based on the second URL can specifically include:

[0094] In the case of cold start of the application program, the payment page is directly displayed.

[0095] In the embodiments of the present specification, cold start of the application program refers to the process of starting the application program again after the application program has not been run or the process is terminated. In this process, the system needs to recreate the process and initialize the application, which usually takes longer than hot start (the application is still running in the memory). In the process of cold start, the system needs to load all resources and data of the application from zero, including the execution file of the application, the data file, and the system resources that may be needed.

[0096] In the prior art, when the cold start of the terminal is called, the application program at the payment terminal device additionally loads processes other than the main process, such as the push process, the tools process, and the applet process. These processes other than the main process are unnecessary processes in the NFC payment calling process, and running these processes will reduce the calling efficiency and increase the calling time. When the cold start of the terminal is called, multiple pages need to be loaded, such as the terminal calling page, the transfer page, the scan-in-between page, the splash page, the application program home page, and the payment page. Among them, only the terminal calling page and the payment page are necessary pages, and loading other redundant pages will inevitably increase the calling time.

[0097] In the embodiments of the present specification, the direct display of the payment page in the case of cold start of the application program refers to that, in the case of cold start of the application program, the application program home page, the splash page, the transfer page, and the scan-in-between page, and other unnecessary pages in the NFC payment process are no longer loaded, and other processes other than the main process are no longer loaded, but the main process directly loads and displays the payment page. Thus, the time consumption of loading unnecessary processes is avoided, and the time consumption of loading some unnecessary pages before loading the payment page is avoided, the time consumption of opening the payment page in the NFC payment process is effectively reduced, and the calling efficiency is improved.

[0098] For the case of hot start, in the method in FIG. 2, before displaying the payment page based on the second URL in step 206, the following can also be included:

[0099] In the case of hot start of the application program, the page stack is executed to clear the stack.

[0100] In the embodiments of the present specification, application hot start refers to that the application has been opened on the user terminal, but due to some reasons (such as the user pressing the back key, the Home key, etc.), the application is placed in the background, and the user opens the application again. In the hot start, since the process of the application already exists in the background of the user terminal, the system does not need to re-create the Application class, but directly recovers the state of the application from the existing process and creates and initializes the Main Activity class. Therefore, the process of the hot start is relatively fast, and the user experience is more smooth.

[0101] In the Android system, when the user starts multiple pages in the application, each page can be a page stack. The page (Activity) stack is a mechanism designed by the Android framework to manage the Activity life cycle. The "stack" referred to here is not the stack data structure in the programming language, but a logical concept used to track Activity (i.e., each page in the application) in application life cycle management. Whenever a new Activity is started, the newly started Activity is added to the top of the Activity stack, i.e., "stacked in". When the user navigates back to the previous page, the Activity of the current page is removed from the top of the stack, i.e., "stacked out".

[0102] In the Activity stack, each Activity has its own state information, including its view state, life cycle state, and other related data, which can be saved and restored through the system's life cycle management mechanism. The "stack clearing" operation refers to removing some or all Activities in the Activity stack. In actual application, the stack clearing operation can be implemented through startActivityForRe sult, the Flags of Intent, or the method inside the component.

[0103] In the embodiments of the present specification, performing stack clearing on the page stack can clear the pages of the application that already exist in the background, such as: clearing the existing home page, splash page, and scan page of the application. Thus, the user can be presented with irrelevant pages during the NFC payment process, and the payment page can be jumped from the irrelevant pages. After performing stack clearing on the page stack, the payment page can be directly presented to the user during the terminal process, which is beneficial to improve the user's experience.

[0104] In actual application, the user's payment terminal device and the NFC tag device establish near field communication, and the user's payment terminal device can be used as the NFC master device for transmitting near field communication signals.

[0105] Based on this, in the method in FIG. 2, in step 202, the first URL is acquired from the NFC tag device based on the near field communication mode, which can specifically include:

[0106] The payment terminal device transmits the near field communication signal as an NFC master device;

[0107] The first URL sent by the NFC tag device in response to the near field communication signal is acquired through the near field communication mode.

[0108] In actual application, the first URL acquired by the payment terminal device based on NFC can further include domain name information, which can be used to indicate the application program at the payment terminal device that needs to be used for this NFC payment.

[0109] Based on this, in the method in FIG. 2, in step 202, the first URL is acquired from the NFC tag device based on the near field communication mode, which can specifically include:

[0110] The first URL provided by the NFC tag device is acquired by the operating system through the near field communication mode; the first URL further includes domain name information;

[0111] An application program corresponding to the domain name information is determined;

[0112] The first URL is transmitted to the application program.

[0113] In the embodiments of the present disclosure, after the payment terminal device acquires the first URL sent by the NFC tag device based on NFC, the protocol type information of the first URL can be recognized by the operating system first, to determine whether to respond to the first URL, and then the domain name information in the first URL is recognized, to determine the application program that needs to be called according to the domain name information. After the operating system determines the application program that needs to be called, the first URL can be transmitted to the application program, so that the main process of the application program can determine the second URL according to the first URL, and further render the payment page according to the second URL.

[0114] In actual application, the first URL can further include path information, which can be used to indicate the application component of the application program that needs to be used for this NFC payment.

[0115] Correspondingly, the determination of the application program corresponding to the domain name information can specifically include:

[0116] A second application component corresponding to the domain name information and the path information is determined.

[0117] Correspondingly, the transmission of the first URL to the application program can specifically include:

[0118] transmitting the first URL to the second application component.

[0119] In an embodiment of the present specification, after the operating system obtains the first URL, the operating system can identify domain name information and path information in the first URL, and determine an application component for processing the first URL according to the domain name information and the path information. The application component can be an application component corresponding to the domain name information and the path information, which is pre-registered in the operating system.

[0120] In an embodiment of the present specification, the second application component can be a component in the application program for converting the first URL. Specifically, the second application component can be an Activity component. In actual applications, a page corresponding to the second application component can be set as invisible. During the running of the second application component, the application program can convert the first URL into a second URL.

[0121] In an embodiment of the present specification, the second application component corresponding to the domain name information and the path information can run in the main process of the application program. In the case of cold start, the second application component for processing the first URL can be created, and the main process of the application program for running the second application component can be created; in the case of hot start, the second application component for processing the first URL can also be created, and the second application component can be caused to run in the main process of the application program.

[0122] FIG. 4 is a flowchart of a method for sending information based on NFC according to an embodiment of the present specification. From the hardware perspective, the execution subject of the flowchart can be an NFC tag device. From the program perspective, the execution subject of the flowchart can be an application program loaded on the NFC tag device. As shown in FIG. 4, the flowchart can include the following steps:

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

[0124] Step 404: in response to the near field communication signal, sending a first URL to the payment terminal device through near field communication; the length of the first URL is less than or equal to the maximum number of bytes that the NFC tag device can transmit at a time based on near field communication; the first URL contains a URL query identifier; the URL query identifier is used to determine a second URL by the payment terminal device; the second URL contains target information for displaying a payment page.

[0125] In the embodiments of the present application, 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 target information of the payment page can have the same meaning as the terms mentioned in the embodiments of the method in FIG. 2. Since the process of sending the first URL from the NFC tag device to the payment terminal device through the near field communication has been described in detail, the details are not repeated here.

[0126] In the embodiments of the present application, the payment terminal device is used as the NFC reader. When the payment terminal device is close to the NFC tag device, the payment terminal device can send a near field communication signal to the NFC tag device, thereby triggering the near field communication between the NFC tag device and the payment terminal device, and obtaining the first URL from the NFC tag device.

[0127] In the method in FIG. 4, since the length of the first URL obtained by the payment terminal device from the NFC tag device based on the near field communication is not greater than the maximum number of bytes that can be transmitted by the NFC tag device based on the near field communication in a single time, the situation that the NFC tag device needs to transmit the URL to the payment terminal device for multiple times due to the length of the URL is avoided, thereby improving the transmission efficiency of information transmission between the NFC tag device and the payment terminal device, and effectively reducing the information transmission time. Moreover, the first URL transmitted by the NFC tag device to the payment terminal device through the near field communication carries the URL query identifier, and the payment terminal device can determine the second URL required for displaying the payment page based on the URL query identifier and the stored data, thereby obtaining the second URL corresponding to the first URL through local query, without network access, further reducing the time consumption of opening the payment page in the NFC payment process, effectively improving the speed of opening the payment page, and thereby improving the user experience and the NFC payment efficiency.

[0128] Based on the method in FIG. 4, the embodiments of the present application further provide some specific implementation schemes of the method, which are described below.

[0129] In the embodiments of the present application, the method in FIG. 4, before receiving the near field communication signal emitted by the payment terminal device in step 402, the method can further include:

[0130] Obtaining a preset trigger operation;

[0131] Obtaining first service information in response to the trigger operation;

[0132] Sending a URL obtaining request to an application server, wherein the URL obtaining request carries the first service information;

[0133] receiving the first URL returned by the application server; the first URL carrying an information token; the information token being used to query service description information; the service description information including the first service information and second service information; the second service information including information related to the first URL and the service acquired by the application server.

[0134] In the embodiments of the present application, the preset trigger operation can include, but is not limited to, a cashier clicking a payment button on a payment device, a user clicking a payment button on a vending machine, etc. The first service information can include, but is not limited to, an order number, a merchant number, an order time, an order amount, etc. The second service information can include, but is not limited to, a generation time of the first URL, a delivery time of the first URL, a content of the first URL, a payment time limit of the order, whether the order has been paid, an identifier of a payment user, etc.

[0135] In actual application, the first service information can include order-related information sent by an NFC tag device to an application server. Part of the second service information can include information sent by a payment terminal device to the application server, such as an identifier of a payment user. Part of the second service information can also include information generated by the application server, for example, a generation time of the first URL, a time limit of the information token, etc.

[0136] In the embodiments of the present application, the application server can obtain the information token by generating a random code, and store the information token in association with the service description information. Thus, when the application server receives a service request sent by the payment terminal device and carrying the information token, the corresponding service description information can be queried based on the information token, and the service process is further promoted.

[0137] FIG. 5 is a flowchart of a method for sending a URL according to an embodiment of the present application. From the hardware perspective, the execution subject of the flowchart can be an application server. From the program perspective, the execution subject of the flowchart can be an application program running on the application server. As shown in FIG. 5, the flowchart can include the following steps:

[0138] Step 502: Acquiring a URL acquisition request sent by an NFC tag device.

[0139] Step 504: Generating a first URL in response to the URL acquisition request; the length of the first URL is less than or equal to a preset byte number threshold; the byte number threshold is based on the maximum number of bytes that can be transmitted by NFC in one time.

[0140] Step 506: sending the first URL to the NFC tag device; the first URL is used by the payment terminal device to acquire from the NFC tag device in a near field communication manner; the first URL contains a URL query identifier; the URL query identifier is used by the payment terminal device to query a second URL, and the second URL contains target information used by the payment terminal device to display a payment page.

[0141] In the embodiments of the present application, 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 target information of the payment page can have the same meanings as those mentioned in the embodiments of the method of FIG. 2. Since the process of sending the first URL from the NFC tag device to the payment terminal device in the near field communication manner has been described in detail above, no further description is given here.

[0142] In the embodiments of the present application, the first URL is generated by the application server in response to a URL acquisition request sent by the NFC tag device, and the URL acquisition request can carry information about the type of the business scenario in which the NFC tag device is located.

[0143] Based on this, in step 504 of the method of FIG. 5, in response to the URL acquisition request, the first URL is generated, which can specifically include:

[0144] In response to the URL acquisition request, determining the type of the business scenario in which the NFC tag device is located;

[0145] Generating the first URL corresponding to the type of the business scenario; the URL query identifier carried in the first URL is used to query the second URL corresponding to the type of the business scenario.

[0146] In the embodiments of the present application, the type of the business scenario in which the NFC tag device is located can include, but is not limited to, a POS machine payment scenario, a vending machine payment scenario, a service machine water vending scenario, a gate opening scenario, an ordering scenario, and the like. In actual applications, different business scenarios can correspond to different URL query identifiers, different URL query identifiers can query different second URLs, and then different payment pages can be displayed for users based on different second URLs. Since the process of determining the second URL corresponding to the type of the business scenario according to the URL query identifier carried in the first URL has been described in detail above, no further description is given here.

[0147] Optionally, in step 504 of the method of FIG. 5, in response to the URL acquisition request, the first URL is generated, which can specifically include:

[0148] generate an information identifier according to the first service information carried in the URL acquisition request; the information identifier is used to query service description information corresponding to the first URL; the service description information includes the first service information and second service information; the second service information includes information related to the service corresponding to the first URL and acquired by the application server;

[0149] generate the first URL carrying the information identifier.

[0150] In the embodiments of the present disclosure, the information identifier can be generated by the application server based on the first service information, for example, the application server generates the information identifier based on an order number or a merchant number. Alternatively, the information identifier can also be a random string generated by the application server. In the application server, the generated information identifier and the service description information can be correspondingly associated and stored, so that when the service description information is needed to be used later, the information identifier can be used for querying.

[0151] Correspondingly, in the method in FIG. 5, after the first URL is sent to the NFC tag device in step 506, the method can further include:

[0152] acquire a service request sent by the payment terminal device; the service request carries the information identifier;

[0153] query service description information used to execute the service corresponding to the service request based on the information identifier;

[0154] execute the service based on the queried service description information to obtain service execution result information;

[0155] send the execution result information to the payment terminal device.

[0156] Specifically, taking a payment service for an order as an example, when the payment terminal device of the user displays a payment page for the user, if the user approves the order, the payment confirmation control in the payment page can be triggered. After the user triggers the payment confirmation control in the payment page, the payment terminal device can send a service request to the application server to request the application server to execute the order service.

[0157] After the application server receives the service request sent by the payment terminal device, the application server can query the service description information stored in association with the information identifier according to the information identifier carried in the service request. Since the service description information can involve information related to the order, the application server can execute the payment service for the order based on the queried service description information, obtain the corresponding payment result, and feed back the payment result information to the payment terminal device.

[0158] FIG. 6 is a swim lane diagram of a method for opening a payment page based on NFC according to an embodiment of the present specification. As shown in FIG. 6, the method for opening a payment page based on NFC can involve an NFC tag device, a payment terminal device, and an application server as execution subjects; the method can include a first URL generation stage, a first URL transmission stage, a terminal calling stage, and a business execution stage, and can include the following steps:

[0159] Step 602: The NFC tag device acquires a preset trigger operation.

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

[0161] Step 606: The NFC tag device sends a URL acquisition request carrying the first business information to the application server.

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

[0163] Step 610: The application server stores the information identifier in association with the business description information and generates a first URL carrying the information identifier.

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

[0165] Step 614: The NFC tag device acquires the first URL.

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

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

[0168] Step 620: The NFC tag device sends the first URL to the payment terminal device through near field communication in response to the near field communication signal.

[0169] Step 622: The payment terminal device acquires the first URL.

[0170] Step 624: The payment terminal device parses the business parameter information in the first URL to obtain a third URL.

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

[0172] Step 628: The payment terminal device queries a URL template according to the URL query identifier.

[0173] Step 630: The payment terminal device fills the information identifier into the to-be-filled position of the URL template, to obtain a second URL.

[0174] Step 632: The payment terminal device renders a payment page according to the second URL.

[0175] Step 634: The payment terminal device sends a service request to the application server in response to a triggering operation of a payment control in the payment page by the user.

[0176] Step 636: The application server acquires the service request sent by the payment terminal device, and queries service description information for performing a service corresponding to the service request based on the information identifier carried in the service request.

[0177] Step 638: The application server performs the service based on the queried service description information, obtains service execution result information, and sends the execution result information to the payment terminal device.

[0178] Step 640: The payment terminal device acquires and displays the execution result information to the user.

[0179] The steps 602 to 614 are a first URL generation phase, in which information interaction between the NFC tag device and the application server can be involved. The steps 616 to 622 are a first URL transmission phase, in which information interaction between the NFC tag device and the payment terminal device can be involved. The steps 624 to 632 are a terminal calling phase, which can be performed at the payment terminal device. The steps 634 to 640 are a service execution phase, in which information interaction between the payment terminal device and the application server can be involved.

[0180] Based on the same idea, the present specification also provides a device corresponding to the above method.

[0181] FIG. 7 is a structural schematic diagram of a device for opening a payment page based on NFC corresponding to FIG. 2 according to an embodiment of the present specification. The device can be applied to a payment terminal device, and includes:

[0182] The URL obtaining module 702 is configured to obtain a first URL from the NFC tag device based on the near field communication mode; the length of the first URL is less than or equal to the maximum number of bytes that can be transmitted by the NFC tag device based on the near field communication mode at a time; and the first URL contains a URL query identifier.

[0183] The URL conversion module 704 is configured to determine a second URL corresponding to the URL query identifier based on the data stored by the payment terminal device; and the second URL contains target information for displaying a payment page.

[0184] The display module 706 is configured to display the payment page based on the second URL.

[0185] Based on the apparatus of FIG. 7, the embodiments of the present specification further provide some specific implementations of the apparatus, which are described below.

[0186] Optionally, the apparatus can further include:

[0187] The parsing module is configured to parse the service parameter information in the first URL to obtain a third URL; the service parameter information includes the URL query identifier and an information identifier; the information identifier is used to query service description information corresponding to the first URL.

[0188] The extraction module is configured to extract the URL query identifier and the information identifier from the third URL.

[0189] Optionally, the URL conversion module 704 can specifically include:

[0190] The URL template query unit is configured to query a URL template according to the URL query identifier; the URL template includes a to-be-filled position.

[0191] The second URL obtaining unit is configured to fill the information identifier into the to-be-filled position to obtain a second URL; the second URL includes the target information; the information identifier is carried in the target information.

[0192] Optionally, the target information can include a component identifier, a task identifier, and a task parameter.

[0193] Correspondingly, the display module 706 can specifically include:

[0194] The first determination unit is configured to determine a first application component corresponding to the component identifier.

[0195] The second determination unit is configured to determine a page rendering task corresponding to the task identifier.

[0196] The rendering unit is configured to execute the page rendering task based on the task parameter by using the first application component to render the payment page.

[0197] Optionally, the rendering unit can specifically include:

[0198] The page information obtaining sub-unit is configured to obtain pre-stored page information based on the task parameter; the page information includes at least one of picture information and script information.

[0199] The rendering subunit is configured to execute the page rendering task by using the first application component based on the page information, and render a payment page.

[0200] Optionally, the task parameter can further carry amount information; the amount information includes first amount information or second amount information; the first amount information can represent a set amount value; the second amount information can represent that no amount value is provided; in a case where the amount information is the first amount information, the payment page displays the set amount value; and in a case where the amount information is the second amount information, the payment page does not display an amount value.

[0201] Optionally, the payment page can include a payment control.

[0202] Correspondingly, the apparatus can further include:

[0203] The business request sending module is configured to send a business request to an application server based on the second URL in response to a triggering operation of the payment control by a user; the business request carries information identification; and the information identification is used to query business description information corresponding to the first URL.

[0204] The business execution result information receiving module is configured to receive business execution result information returned by the application server; the business execution result information is determined by the application server according to business description information; and the business description information is obtained by the application server according to the information identification.

[0205] The payment result page display module is configured to display a payment result page based on the business execution result information.

[0206] Optionally, the display module 706 can specifically include:

[0207] The display unit is configured to directly display a payment page in a case where an application program is cold started.

[0208] Optionally, the apparatus can further include:

[0209] The stack clearing module is configured to execute stack clearing on a page stack in a case where an application program is hot started.

[0210] Optionally, the URL obtaining module 702 can specifically include:

[0211] The signal transmitting unit is configured to transmit a near field communication signal by taking the payment terminal device as an NFC master device.

[0212] The first URL obtaining unit is configured to obtain the first URL sent by the NFC tag device through the near field communication mode in response to the near field communication signal.

[0213] Optionally, the URL obtaining module 702 can specifically include:

[0214] The first URL obtaining unit is configured to obtain the first URL provided by the NFC tag device by the operating system through the near field communication mode; the first URL further includes domain name information.

[0215] The application program determining unit is configured to determine an application program corresponding to the domain name information.

[0216] The first URL transmitting unit is configured to transmit the first URL to the application program.

[0217] Optionally, the first URL can further include path information.

[0218] Correspondingly, the application program determining unit can specifically include:

[0219] The application program determining sub-unit is configured to determine a second application component corresponding to the domain name information and the path information.

[0220] Correspondingly, the first URL transmitting unit can specifically include:

[0221] The first URL transmitting sub-unit is configured to transmit the first URL to the second application component.

[0222] FIG. 8 is a structural schematic diagram of a NFC-based information sending device corresponding to FIG. 4 provided by an embodiment of the present specification. The device can be applied to an NFC tag device, and includes:

[0223] The signal receiving module 802 is configured to receive the near field communication signal transmitted by the payment terminal device.

[0224] The signal sending module 804 is configured to send a first URL to the payment terminal device through the near field communication mode in response to the near field communication signal; the length of the first URL is less than or equal to the maximum number of bytes that can be transmitted by the NFC tag device based on the near field communication mode at a single time; the first URL includes a URL query identifier; the URL query identifier is used to determine a second URL by the payment terminal device; the second URL includes target information used to display a payment page.

[0225] Optionally, the device can further include:

[0226] The first obtaining module is configured to obtain a preset trigger operation.

[0227] The second obtaining module is configured to obtain first service information in response to the trigger operation.

[0228] The URL obtaining request sending module is configured to send a URL obtaining request to an application server, wherein the first service information is carried in the URL obtaining request.

[0229] The first URL receiving module is configured to receive the first URL returned by the application server, wherein the first URL carries an information identifier, the information identifier is used to query service description information, the service description information comprises the first service information and second service information, and the second service information comprises information related to a service corresponding to the first URL and obtained by the application server.

[0230] FIG. 9 is a structural schematic diagram of a device for sending a URL according to an embodiment of the present specification. The device can be applied to an application server and comprises:

[0231] The request obtaining module 902 is configured to obtain a URL obtaining request sent by an NFC tag device.

[0232] The URL generating module 904 is configured to generate a first URL in response to the URL obtaining request, wherein the length of the first URL is less than or equal to a preset byte number threshold, and the byte number threshold is based on the maximum number of bytes that can be transmitted by NFC in one time.

[0233] The URL sending module 906 is configured to send the first URL to the NFC tag device, wherein the first URL is used to be obtained from the NFC tag device by a payment terminal device in a near field communication manner, the first URL contains a URL query identifier, and the URL query identifier is used to query a second URL by the payment terminal device, wherein the second URL contains target information used to display a payment page by the payment terminal device.

[0234] Optionally, the URL generating module 904 can specifically comprise:

[0235] The service scenario type determining unit is configured to determine a service scenario type in which the NFC tag device is located in response to the URL obtaining request.

[0236] The first URL generating unit is configured to generate a first URL corresponding to the service scenario type, wherein the URL query identifier carried in the first URL is used to query a second URL corresponding to the service scenario type.

[0237] Optionally, the URL generating module 904 can specifically comprise:

[0238] An information identifier generating unit is configured to generate an information identifier according to first service information carried in the URL acquisition request; the information identifier is used to query service description information corresponding to the first URL; the service description information includes the first service information and second service information; the second service information includes information related to a service corresponding to the first URL and acquired by the application server.

[0239] A first URL generating unit is configured to generate a first URL carrying the information identifier.

[0240] Optionally, the apparatus can further include:

[0241] A service request acquiring module is configured to acquire a service request sent by a payment terminal device; the service request carries the information identifier.

[0242] A service description information querying module is configured to query, based on the information identifier, service description information used to execute a service corresponding to the service request.

[0243] A service execution result information acquiring module is configured to acquire service execution result information by executing the service based on the queried service description information.

[0244] An execution result information sending module is configured to send the execution result information to the payment terminal device.

[0245] Based on the same idea, the embodiments of the present specification also provide a device corresponding to the above method.

[0246] FIG. 10 is a structural schematic diagram of a payment terminal device corresponding to FIG. 2 provided by an embodiment of the present specification. As shown in FIG. 10, the device 1000 can be a payment terminal device, and the device 1000 can include:

[0247] at least one processor 1010; and

[0248] a memory 1030 in communication connection with the at least one processor; wherein

[0249] the memory 1030 stores instructions 1020 executable by the at least one processor 1010, and the instructions are executed by the at least one processor 1010 to enable the at least one processor 1010 to:

[0250] acquire a first URL from an NFC tag device based on a near field communication mode; the length of the first URL is less than or equal to the maximum number of bytes that can be transmitted by the NFC tag device based on the near field communication mode at a time; and the first URL includes a URL query identifier.

[0251] Determine a second URL corresponding to the URL query identifier based on the data stored by the payment terminal device; the second URL contains target information for displaying a payment page.

[0252] Display the payment page based on the second URL.

[0253] FIG. 11 is a structural schematic diagram of an NFC tag device corresponding to FIG. 4 according to an embodiment of the present specification. As shown in FIG. 11, the device 1100 can be an NFC tag device, and the device 1100 can include:

[0254] at least one processor 1110; and

[0255] a memory 1130 in communication with the at least one processor; wherein

[0256] the memory 1130 stores instructions 1120 executable by the at least one processor 1110, and the instructions are executed by the at least one processor 1110 to enable the at least one processor 1110 to:

[0257] receive a near field communication signal transmitted by a payment terminal device.

[0258] in response to the near field communication signal, send a first URL to the payment terminal device through near field communication; the length of the first URL is less than or equal to the maximum number of bytes that can be transmitted by the NFC tag device in a single time based on the near field communication; the first URL contains a URL query identifier; the URL query identifier is used to determine a second URL by the payment terminal device; the second URL contains target information for displaying a payment page.

[0259] FIG. 12 is a structural schematic diagram of an application server corresponding to FIG. 5 according to an embodiment of the present specification. As shown in FIG. 12, the device 1200 can be an application server, and the device 1200 can include:

[0260] at least one processor 1210; and

[0261] a memory 1230 in communication with the at least one processor; wherein

[0262] the memory 1230 stores instructions 1220 executable by the at least one processor 1210, and the instructions are executed by the at least one processor 1210 to enable the at least one processor 1210 to:

[0263] obtain a URL acquisition request sent by an NFC tag device.

[0264] In response to the URL acquisition request, a first URL is generated; the length of the first URL is less than or equal to a preset byte number threshold; the byte number threshold is based on the maximum number of bytes that can be transmitted by NFC in a single time.

[0265] The first URL is sent to the NFC tag device; the first URL is used to be acquired from the NFC tag device by the payment terminal device in a near field communication manner; the first URL contains a URL query identifier; the URL query identifier is used to query a second URL by the payment terminal device, and the second URL contains target information used to display a payment page by the payment terminal device.

[0266] Each of the embodiments in the specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other. Each of the embodiments focuses on the difference from other embodiments. In particular, for the devices shown in FIGS. 10-12, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the part of the method embodiments.

[0267] The above describes specific embodiments of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different than the order in the embodiments and still achieve the desired result. In addition, the processes depicted in the figures do not necessarily require the particular order shown or sequential order to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous or possible.

[0268] In the 1990s, it was quite obvious to distinguish whether an improvement in a technology was in hardware (e.g., improvement in circuit structures of diodes, transistors, switches, etc.) or in software (improvement in method flow). However, as technology has evolved, many improvements in method flow today can be considered as direct improvements in hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structures by programming the improved method flow into hardware circuits. Therefore, it cannot be said that an improvement in a method flow cannot be implemented by hardware entity modules. For example, a programmable logic device (PLD) (e.g., a field programmable gate array (FPGA)) is an integrated circuit whose logic function is determined by user programming of the device. A digital system is "integrated" on a PLD by the designer programming it, rather than by asking a chip manufacturer to design and fabricate a custom integrated circuit chip. Moreover, instead of manually fabricating integrated circuit chips, this programming is now mostly implemented by "logic compiler" software, which is similar to software compilers used in program development, and the original code to be compiled is written in a specific programming language, which is called a hardware description language (HDL), and there are many such languages, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., and the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should be aware that, as long as the method flow is logically programmed in the above-mentioned hardware description languages and programmed into an integrated circuit, a hardware circuit implementing the logical method flow can be easily obtained.

[0269] The controller can be implemented in any suitable way, for example, the controller can take the form of a microprocessor or processor and a computer readable medium storing computer readable program code, such as software or firmware, executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also know that, in addition to being implemented in pure computer readable program code, the controller can equally well be implemented to perform the same functions using logic gates, switches, an application specific integrated circuit, a programmable logic controller and an embedded microcontroller, etc. by means of a logical programming of the method steps. The controller can thus be considered as a hardware component, and the means comprised therein for performing the various functions can be considered as structures within the hardware component. Alternatively, the means for performing the various functions can even be considered as both a software module implementing the method and a structure within the hardware component.

[0270] The systems, apparatuses, modules or units illustrated by the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0271] For the sake of description, the above apparatuses are described in various units by functions respectively. Of course, the functions of each unit can be implemented in one or more software and / or hardware in the implementation of the present specification.

[0272] Those skilled in the art will understand that the embodiments of the present application can be provided as a method, a system or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.

[0273] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

[0274] These computer program instructions can also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart block or blocks.

[0275] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

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

[0277] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) and / or cache memory, for storing, in general, data and / or program instructions. The memory can also include non-volatile memory, such as read-only memory (ROM), electrically programmable read-only memory (EPROM), electrically erasable read-only memory (EEPROM), flash memory, or non-volatile random access memory (NVRAM), for storing, in general, data and / or program instructions. The memory is an example of computer readable media.

[0278] Computer-readable media includes permanent and non-permanent, movable and non-movable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to a computing device. According to the definition herein, computer-readable media does not include transitory media such as modulated data signals and carriers.

[0279] It should also be noted that the terms "comprising", "containing", or any other variant thereof are intended to cover non-exclusive inclusions, so that a process, method, article or apparatus that includes a list of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or apparatus. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article or apparatus that includes the element.

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

[0281] The above only describes the embodiments of the specification and is not intended to limit the specification. The specification can have various changes and variations for those skilled in the art. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the specification shall be included in the scope of claims of the specification.

Claims

1. A method for opening a payment page based on NFC, applied to a payment terminal device, comprising: obtaining a first URL from an NFC tag device based on a near field communication mode; the first URL containing a URL query identifier; determining a second URL corresponding to the URL query identifier based on data stored in the payment terminal device; the second URL containing target information for displaying the payment page; displaying the payment page based on the second URL.

2. The method of claim 1, wherein, The length of the first URL is less than or equal to the maximum number of bytes that the NFC tag device can transmit at a time based on the near field communication mode.

3. The method of claim 2, wherein, The length of the first URL is less than or equal to 124 bytes. 4.The method of claim 1, before determining the second URL corresponding to the URL query identifier based on the data stored in the payment terminal device, further comprising: parsing service parameter information in the first URL to obtain a third URL; the service parameter information contains the URL query identifier and an information identifier; 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. 5.The method of claim 4, wherein the parsing of the service parameter information in the first URL comprises: parsing the service parameter information after a specified character in the first URL. 6.The method of claim 5, wherein the parsing of the service parameter information after the specified character in the first URL comprises: determining an application corresponding to a protocol header information in the first URL according to the protocol header information; and starting a main process of the application to parse the service parameter information after the specified character in the first URL. 7.The method of claim 4, wherein the determining of the second URL corresponding to the URL query identifier based on the data stored in the payment terminal device comprises: querying a URL template according to the URL query identifier; the URL template includes a to-be-filled position; filling the information identifier into the to-be-filled position to obtain the second URL; the second URL contains the target information; the information identifier is carried in the target information. 8.The method of claim 1, wherein different payment scenarios correspond to different URL query identifiers. 9.The method of claim 1, wherein the target information includes a component identifier, a task identifier, and a task parameter; and the displaying of the payment page based on the second URL comprises: determining a first application component corresponding to the component identifier; determining a page rendering task corresponding to the task identifier; using the first application component to execute the page rendering task based on the task parameter to render the payment page.

10. The method of claim 9, wherein, the first application component renders the payment page in a native manner.

11. The method of claim 9, wherein the rendering the payment page based on the task parameter by using the first application component comprises: obtaining pre-stored page information based on the task parameter; wherein the page information comprises at least one of image information and text information; and rendering the payment page based on the page information by using the first application component.

12. The method of claim 9, wherein the task parameter further carries amount information; the amount information comprises first amount information or second amount information; the first amount information represents a set amount value; and the second amount information represents no provided amount value; wherein, in a case where the amount information is the first amount information, the payment page displays the set amount value; and in a case where the amount information is the second amount information, the payment page does not display the amount value. In a case where the first URL does not include the amount information, the amount information in the task parameter included in the second URL is the second amount information; and in a case where the first URL includes the amount information, the amount information in the task parameter included in the second URL is the first amount information.

14. The method of claim 1, wherein the payment page comprises a payment control; and the method further comprises, after displaying the payment page based on the second URL: sending a service request to an application server based on the second URL in response to a triggering operation of the payment control by a user; wherein the service request carries an information identifier; the information identifier is used to query service description information corresponding to the first URL; and the method further comprises: receiving service execution result information returned by the application server; wherein the service execution result information is determined by the application server according to the service description information; the service description information is obtained by the application server according to the information identifier; and the method further comprises: displaying a payment result page based on the service execution result information.

15. The method of claim 1, wherein the displaying the payment page based on the second URL comprises: directly displaying the payment page in a case where an application program is cold started.

16. The method of claim 1, wherein the method further comprises, before the displaying the payment page based on the second URL: performing stack clearing on a page stack in a case where an application program is hot started.

17. The method of claim 1, wherein the obtaining the first URL from the NFC tag device based on the near field communication mode comprises: transmitting a near field communication signal by the payment terminal device as an NFC master device; and obtaining the first URL sent by the NFC tag device through the near field communication mode in response to the near field communication signal.

13. The method of claim 12, wherein, 18. The method of claim 1, wherein the obtaining the first URL from the NFC tag device based on the near field communication mode comprises: obtaining the first URL provided by the NFC tag device by an operating system through the near field communication mode; and wherein the first URL further comprises domain name information. ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ determining an application corresponding to the domain name information; transmitting the first URL to the application.

19. The method of claim 18, wherein the first URL further comprises path information; and the determining the application corresponding to the domain name information specifically comprises: determining a second application component corresponding to the domain name information and the path information; the transmitting the first URL to the application specifically comprises: transmitting the first URL to the second application component.

20. The method of claim 1, wherein, The payment terminal device specifically comprises a device supporting NFC function for completing NFC payment.

21. A NFC-based information sending method applied to an NFC tag device, comprising: receiving a near field communication signal transmitted by a payment terminal device; in response to the near field communication signal, sending a first URL to the payment terminal device through a near field communication mode; the first URL comprising a URL query identifier; the URL query identifier is used for determining a second URL by the payment terminal device; the second URL comprising target information for displaying a payment page.

22. The method of claim 21, wherein, The length of the first URL is less than or equal to the maximum number of bytes that can be transmitted by the NFC tag device based on the near field communication mode in a single time.

23. The method of claim 22, wherein, The length of the first URL is less than or equal to 124 bytes.

24. The method of claim 21, wherein before the receiving the near field communication signal transmitted by the payment terminal device, the method further comprises: obtaining a preset trigger operation; in response to the trigger operation, obtaining first service information; sending a URL obtaining request to an application server; the URL obtaining request carrying the first service information; receiving the first URL returned by the application server; the first URL carrying an information identifier; the information identifier being used for querying service description information; the service description information comprising the first service information and second service information; the second service information comprising information related to the first URL and obtained by the application server.

25. The method of claim 21, wherein, The NFC tag device specifically comprises a collection device in an offline payment scenario.

26. A method for sending a URL, applied to an application server, comprising: obtaining a URL obtaining request sent by an NFC tag device; in response to the URL obtaining request, generating a first URL; sending the first URL to the NFC tag device; the first URL being used for being obtained by a payment terminal device from the NFC tag device in a near field communication mode; the first URL comprising a URL query identifier; the URL query identifier being used for querying a second URL by the payment terminal device; the second URL comprising target information for displaying a payment page by the payment terminal device.

27. The method of claim 26, wherein, The length of the first URL is less than or equal to a preset byte number threshold; the byte number threshold being the maximum number of bytes that can be transmitted based on NFC in a single time.

28. The method of claim 27, wherein, The length of the first URL is less than or equal to 124 bytes.

29. The method of claim 26, wherein the generating the first URL in response to the URL obtaining request specifically comprises: In response to the URL acquisition request, a service scenario type in which the NFC tag device is located is determined; A first URL corresponding to the service scenario type is generated; The URL query identifier carried in the first URL is used to query a second URL corresponding to the service scenario type.

30. The method of claim 26, wherein the generating the first URL in response to the URL acquisition request comprises: generating an information identifier according to first service information carried in the URL acquisition request; the information identifier is used to query service description information corresponding to the first URL; the service description information comprises the first service information and second service information; the second service information comprises information related to the first URL acquired by the application server; generating the first URL carrying the information identifier.

31. The method of claim 30, wherein after the sending the first URL to the NFC tag device, the method further comprises: acquiring a service request sent by a payment terminal device; the service request carries the information identifier; based on the information identifier, querying service description information used to execute a service corresponding to the service request; based on the queried service description information, executing the service to obtain service execution result information; sending the execution result information to the payment terminal device.

32. An apparatus for opening a payment page based on NFC, applied to 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 mode; the first URL comprises a URL query identifier; a URL conversion module, configured to determine a second URL corresponding to the URL query identifier based on data stored in the payment terminal device; the second URL comprises target information used to display the payment page; a display module, configured to display the payment page based on the second URL.

33. An information sending apparatus based on NFC, applied to an NFC tag device, comprising: a signal receiving module, configured to receive a near field communication signal transmitted by a payment terminal device; a signal sending module, configured to send a first URL to the payment terminal device through a near field communication mode in response to the near field communication signal; the first URL comprises a URL query identifier; the URL query identifier is used to determine a second URL by the payment terminal device; the second URL comprises target information used to display a payment page.

34. An apparatus for sending a URL, applied to an application server, comprising: a request acquisition 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; a URL sending module, configured to send the first URL to the NFC tag device; the first URL is used to be acquired from the NFC tag device by a payment terminal device in a near field communication mode; the first URL comprises a URL query identifier; The URL query identification is used for querying a second URL by the payment terminal device, and the second URL contains target information used for displaying a payment page by the payment terminal device.

35. A payment terminal device, comprising: at least one processor; and a memory connected with the at least one processor in communication; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: obtain a first URL from an NFC tag device based on a near field communication mode; the first URL contains a URL query identification; determine a second URL corresponding to the URL query identification based on data stored by the payment terminal device; the second URL contains target information used for displaying the payment page; display the payment page based on the second URL.

36. An NFC tag device, comprising: at least one processor; and a memory connected with the at least one processor in communication; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: receive a near field communication signal transmitted by a payment terminal device; send a first URL to the payment terminal device through a near field communication mode in response to the near field communication signal; the first URL contains a URL query identification; the URL query identification is used for determining a second URL by the payment terminal device; the second URL contains target information used for displaying a payment page.

37. An application server, comprising: at least one processor; and a memory connected with the at least one processor in communication; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: obtain a URL obtaining request sent by an NFC tag device; generate a first URL in response to the URL obtaining request; send the first URL to the NFC tag device; the first URL is used for being obtained from the NFC tag device by a payment terminal device in a near field communication mode; the first URL contains a URL query identification; the URL query identification is used for querying a second URL by the payment terminal device, and the second URL contains target information used for displaying a payment page by the payment terminal device.

Images