Method, device and equipment for opening page and sending information based on NFC (Near Field Communication)

Abstract

The embodiment of the invention discloses a method, a device and equipment for opening a payment page based on NFC (Near Field Communication), a method, a device and equipment for sending information based on NFC, and a method, a device and equipment for sending a URL (Uniform Resource Locator). According to the scheme, the method comprises the steps that after payment terminal equipment obtains a first URL containing a URL query identifier from NFC label equipment based on a near field communication mode, a second URL which corresponds to the URL query identifier and contains target information used for displaying a payment page can be determined based on data stored in the payment terminal equipment; and displaying the payment page based on the second URL. Wherein the length of the first URL is smaller than or equal to the maximum number of bytes which can be transmitted by the NFC label equipment at a time based on a near field communication mode.

Description

Technical Field

[0001] The present invention relates to the field of near field payment technology, and in particular to a method, device and equipment for opening a payment page based on NFC, a method, device and equipment for sending information based on NFC, and a method, device and equipment for sending a URL. Background Art

[0002] Near Field Communication (NFC) payment refers to the process of consumers using NFC-enabled user terminals to complete payment by using NFC radio frequency channels to communicate with NFC tag devices such as POS cash registers or vending machines when purchasing goods or services. NFC payment is an emerging mobile payment method. Consumers only need to bring their mobile phones close to the NFC tag devices provided by merchants to make payments, without the need to scan codes, which is more convenient. Currently, in the NFC payment process, the time taken to call the terminal from the time the user terminal is close to the NFC tag device to the time the payment page is displayed on the user terminal is relatively long, resulting in a poor user experience.

[0003] Based on this, how to reduce the time spent on opening the payment page during NFC payment and improve the speed of calling the terminal has become a technical problem that needs to be solved urgently. Summary of the invention

[0004] The embodiments of this specification provide a method, device and equipment for opening a payment page based on NFC, a method, device and equipment for sending information based on NFC, and a method, device and equipment for sending a URL, which can effectively reduce the time spent on opening a payment page during NFC payment and improve the speed of calling the terminal.

[0005] In order to solve the above technical problems, the embodiments of this specification provide a method for opening a payment page based on NFC, which is applied to a payment terminal device, including:

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

[0007] Based on the data stored in the payment terminal device, determining a second URL corresponding to the URL query identifier; the second URL includes target information for displaying the payment page;

[0008] Based on the second URL, the payment page is displayed.

[0009] The embodiment of this specification also provides an NFC-based information sending method, which is applied to an NFC tag device, including:

[0010] Receiving a near field communication signal transmitted by a payment terminal device;

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

[0012] The embodiment of this specification also provides a method for sending a URL, which is applied to an application server and includes:

[0013] Get the URL request sent by the NFC tag device;

[0014] 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 a maximum number of bytes that can be transmitted in a single NFC transmission;

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

[0016] The embodiment of this specification also provides a device for opening a payment page based on NFC, which is applied to a payment terminal device, including:

[0017] A URL acquisition module is used to acquire a first URL from an NFC tag device based on a near field communication method; 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 at a time based on the near field communication method; and the first URL includes a URL query identifier;

[0018] A URL conversion module, for determining a second URL corresponding to the URL query identifier based on the data stored in the payment terminal device; the second URL includes target information for displaying the payment page;

[0019] A display module is used to display the payment page based on the second URL.

[0020] The embodiment of this specification also provides an NFC-based information sending device, which is applied to an NFC tag device, including:

[0021] A signal receiving module, used to receive a near field communication signal transmitted by a payment terminal device;

[0022] A signal sending module, used to respond to the near field communication signal and send a first URL to the payment terminal device via near field communication; the length of the first URL is less than or equal to the maximum number of bytes that can be transmitted at a single time by the NFC tag device based on the near field communication method; the first URL contains a URL query identifier; the URL query identifier is used by the payment terminal device to determine a second URL; the second URL contains target information for displaying a payment page.

[0023] The embodiment of this specification also provides a device for sending a URL, which is applied to an application server and includes:

[0024] A request acquisition module is used to obtain a URL acquisition request sent by an NFC tag device;

[0025] A URL generation module is used to generate 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 a maximum number of bytes that can be transmitted in a single NFC transmission;

[0026] A URL sending module is used to send the first URL to the NFC tag device; the first URL is used to be obtained 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 be used by the payment terminal device to query a second URL, and the second URL contains target information for the payment terminal device to display a payment page.

[0027] The embodiment of this specification also provides a payment terminal device, including:

[0028] at least one processor; and,

[0029] a memory communicatively connected to the at least one processor; wherein,

[0030] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

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

[0032] Based on the data stored in the payment terminal device, determining a second URL corresponding to the URL query identifier; the second URL includes target information for displaying the payment page;

[0033] Based on the second URL, the payment page is displayed.

[0034] The embodiment of this specification also provides an NFC tag device, including:

[0035] at least one processor; and,

[0036] a memory communicatively connected to the at least one processor; wherein,

[0037] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0038] Receiving a near field communication signal transmitted by a payment terminal device;

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

[0040] The embodiment of this specification also provides an application server, including:

[0041] at least one processor; and,

[0042] a memory communicatively connected to the at least one processor; wherein,

[0043] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0044] Get the URL request sent by the NFC tag device;

[0045] 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 a maximum number of bytes that can be transmitted in a single NFC transmission;

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

[0047] At least one embodiment provided in this specification can achieve the following beneficial effects:

[0048] In the embodiment of this 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 method is not greater than the maximum number of bytes that the NFC tag device can transmit at a time based on the near field communication method, the situation that the NFC tag device needs to perform multiple sub-packet transmissions to the payment terminal device due to the URL being too long 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. In addition, the first URL transmitted by the NFC tag device to the payment terminal device through the near field communication method carries a URL query identifier, and the payment terminal device can determine the second URL required to display the payment page based on the URL query identifier and the stored data, thereby obtaining the second URL corresponding to the first URL through a local query method, and then opening the payment page based on the second URL. The process of opening the payment page does not require network access, which further reduces the time consumption of opening the payment page during the NFC payment process, effectively improves the terminal call speed, and is conducive to improving the user experience and NFC payment efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0050] Figure 1 A schematic diagram of an application scenario of a method for opening a payment page based on NFC provided in an embodiment of this specification;

[0051] Figure 2 A flowchart of a method for opening a payment page based on NFC provided in an embodiment of this specification;

[0052] Figure 3a A schematic diagram of a payment page provided in an embodiment of this specification;

[0053] Figure 3b A schematic diagram of another payment page provided in an embodiment of this specification;

[0054] Figure 4 A flowchart of an NFC-based information sending method provided in an embodiment of this specification;

[0055] Figure 5 A flowchart of a method for sending a URL provided in an embodiment of this specification;

[0056] Figure 6 The embodiments of this specification provide corresponding to Figure 2 A swimlane diagram of a method of opening a payment page based on NFC;

[0057] Figure 7 The embodiments of this specification provide corresponding to Figure 2 A structural diagram of a device for opening a payment page based on NFC;

[0058] Figure 8 The embodiments of this specification provide corresponding to Figure 4 A structural schematic diagram of an information sending device based on NFC;

[0059] Fig. 9 The embodiments of this specification provide corresponding to Figure 5 A structural diagram of a device for sending a URL;

[0060] Fig.10 The embodiments of this specification provide corresponding to Figure 2 A schematic diagram of the structure of a payment terminal device;

[0061] Fig.11 The embodiments of this specification provide corresponding to Figure 4 A structural schematic diagram of an NFC tag device;

[0062] Fig.12 The embodiments of this specification provide corresponding to Figure 5 A schematic diagram of the structure of an application server. DETAILED DESCRIPTION

[0063] In order to make the purpose, technical solutions and advantages of one or more embodiments of this specification clearer, the technical solutions of one or more embodiments of this specification will be clearly and completely described below in combination with the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this description, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of one or more embodiments of this specification.

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

[0065] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards in the relevant regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0066] In the prior art, the process of calling the terminal based on NFC payment takes a long time, and the user needs to wait for a long time before seeing the payment page, which leads to a poor user experience. The main reasons for this situation are as follows: (1) During the NFC communication process, the length of the uniform resource locator (URL) transmitted by the NFC tag device to the payment terminal device is relatively long. Since the NFC communication standard stipulates the maximum number of bytes that can be sent in one 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 in a single near-field communication mode, it is necessary to send it in packets multiple times, which results in the process of the NFC tag device sending the URL to the payment terminal device taking a long time. (2) After obtaining the URL, the payment terminal device needs to request the code platform server to decode it through a network request before entering the payment page. The process of calling the terminal requires multiple network requests, and the process of making multiple network requests will increase the time consumption of calling the terminal.

[0067] In order to solve the defects in the prior art, this solution provides the following embodiments.

[0068] Figure 1 A schematic diagram of an application scenario of a method for opening a payment page based on NFC provided in an embodiment of this specification.

[0069] like Figure 1As shown, when a user needs to use the payment terminal device 101 that he carries with him to pay for an order, he can turn on the NFC function of the payment terminal device 101 and bring 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 in a single time based on the near field communication method (wherein the length of the first URL is less than or equal to the maximum number of bytes that the NFC tag device 102 can transmit in a single time based on the near field communication method). After the payment terminal device 101 receives the first URL sent by the NFC tag device 102 based on the near field communication method, 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 displayed to the user based on the second URL.

[0070] Figure 1 In the method, since the length of the first URL obtained by the payment terminal device from the NFC tag device based on the near field communication method is not greater than the maximum number of bytes that the NFC tag device can transmit at a time based on the near field communication method, the situation that the NFC tag device needs to perform multiple sub-packet transmissions to the payment terminal device due to the URL being too long 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. In addition, the first URL transmitted by the NFC tag device to the payment terminal device through the near field communication method carries a URL query identifier, and the payment terminal device can determine the second URL required to display the payment page based on the URL query identifier and the stored data, thereby obtaining the second URL corresponding to the first URL through a local query method, without the need to access through the network, further reducing the time spent on opening the payment page during the NFC payment process, effectively improving the terminal call speed, and thus helping to improve the user experience and NFC payment efficiency.

[0071] Figure 2 The following is a flow chart of a method for opening a payment page based on NFC provided in an embodiment of the present specification. From a hardware perspective, the execution subject of the process may be a payment terminal device. From a program perspective, the execution subject of the process may be an application installed on the payment terminal device. Figure 2 As shown, the process may include the following steps:

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

[0073] In the embodiments of this specification, the NFC tag device can be a payment device set up by a merchant in an offline payment scenario. The payment terminal device can be a smartphone that supports the NFC function carried by the user, or other devices that support the NFC function and can complete NFC payment, without specific limitation.

[0074] In actual applications, the maximum number of bytes that an NFC tag device can transmit at a time based on near field communication is usually 124 bytes. Therefore, the length of the first URL transmitted by the NFC tag device to the user's payment terminal device based on near field communication can be less than 124 bytes, or equal to 124 bytes.

[0075] In the embodiments of the present 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 method is not greater than the maximum number of bytes that the NFC tag device can transmit at a single time based on the near field communication method, the situation in which the NFC tag device needs to perform multiple sub-package transmissions to the payment terminal device due to the URL being too long 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.

[0076] Step 204: Based on the data stored in the payment terminal device, determine a second URL corresponding to the URL query identifier; the second URL includes target information for displaying the payment page.

[0077] In actual applications, different scenario types may correspond to different second URLs. For example, the second URL for a POS-based NFC payment scenario may be different from the second URL for a vending machine NFC payment scenario. Therefore, the URL query identifier used to query the second URL is related to the scenario type. Different payment scenarios may correspond to different URL query identifiers, and different URL query identifiers may query different second URLs, thereby displaying different payment pages to users based on different second URLs. For example, different URL query identifiers may be used in different scenarios such as POS payment and vending machine payment.

[0078] In the embodiments of this specification, the data stored in the payment terminal device may include a mapping relationship between a URL query identifier and a URL template. After the payment terminal device obtains the first URL, it can query the URL template corresponding to the URL query identifier based on the URL query identifier in the first URL and the mapping relationship between the URL query identifier and the URL template stored locally. Subsequently, the information identifier carried in the first URL is filled into the position to be filled in the URL template to obtain the second URL. Since the subsequent embodiments in the embodiments of this specification will explain the process of determining the second URL in detail, it will not be repeated here.

[0079] Step 206: Based on the second URL, display the payment page.

[0080] In the embodiment of the present specification, the target information for displaying the payment page contained in the second URL may be information required for rendering the payment page, such as text information, image information, amount information, etc. After the payment terminal device determines the second URL, it may directly render the payment page based on the target information for displaying the payment page contained in the second URL.

[0081] In the embodiments of the present specification, the first URL transmitted by the NFC tag device to the payment terminal device via near field communication carries a URL query identifier. The payment terminal device can determine the second URL required to display 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 spent on opening the payment page during the NFC payment process, effectively improving the terminal call speed, and thus helping to improve the user experience and NFC payment efficiency.

[0082] Figure 2 In the method, since the length of the first URL obtained by the payment terminal device from the NFC tag device based on the near field communication method is not greater than the maximum number of bytes that the NFC tag device can transmit at a time based on the near field communication method, the situation that the NFC tag device needs to perform multiple sub-packet transmissions to the payment terminal device due to the URL being too long 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. In addition, the first URL transmitted by the NFC tag device to the payment terminal device through the near field communication method carries a URL query identifier, and the payment terminal device can determine the second URL required to display the payment page based on the URL query identifier and the stored data, thereby obtaining the second URL corresponding to the first URL through a local query method, and then opening the payment page based on the second URL. The process of opening the payment page does not require network access, which further reduces the time consumption of opening the payment page during the NFC payment process, effectively improves the terminal call speed, and is conducive to improving the user experience and NFC payment efficiency.

[0083] based on Figure 2 The method in this specification also provides some specific implementation plans of the method, which are described below.

[0084] In actual applications, after the payment terminal device obtains the first URL, it can start the main process of the corresponding application according to the protocol header information in the first URL. The main process of the application can parse the business parameter information after the protocol header in the first URL to obtain a new URL, and extract the identification information required to determine the second URL from the new URL.

[0085] Based on this, Figure 2 The method in step 204, before determining the second URL corresponding to the URL query identifier based on the data stored in the payment terminal device, may further include the following steps:

[0086] Parsing 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 the service description information corresponding to the first URL;

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

[0088] In the embodiment of the present specification, the business parameter information in the first URL may refer to the information after the parameter specified characters (e.g., 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 the protocol header, and the payment terminal device can determine that this URL is the URL for applying for NFC payment using Alipay based on the information in the protocol header, thereby starting the main process of Alipay. After the main process of Alipay is started, the business parameter information of alipay%1A2B3c4d%1A2B3c4dCCC%5e6F${token}_${amount} after the specified characters scheme can be parsed to obtain the parsed third URL: 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 information. It should be noted that CCC, ${token} and ${amount} can represent the location of these 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 information is specifically 0.01.

[0089] As described above, after obtaining the third URL, the URL query identifier and the information identifier can be extracted according to the composition structure of the third URL using the preset URL processing flow.

[0090] In actual applications, the business description information corresponding to the first URL may be relevant information for an order, and these business description information may include but are not limited to: order number, merchant number, order placement time, first URL generation time, order payment time limit, payment user ID, and order payment result. These business description information can be stored on the application server. The application server can randomly generate an information identifier, and store an information identifier in association with the business description information of an order, so that there is a corresponding relationship between the first URL carrying the information identifier and the order stored in association with the information identifier. Therefore, after obtaining the information identifier, the business description information of the corresponding order can be queried from the application server based on the information identifier.

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

[0092] Based on this, Figure 2 In the method, in step 204, determining the second URL corresponding to the URL query identifier based on the data stored in the payment terminal device may specifically include:

[0093] According to the URL query identifier, query the URL template; the URL template includes a position to be filled;

[0094] The information identifier is filled into the position to be filled to obtain a second URL; the second URL includes the target information; and the information identifier is carried in the target information.

[0095] In the embodiment of this specification, the data stored in the payment terminal device may include a mapping relationship between a URL query identifier and a URL template. Therefore, the URL template corresponding to the URL query identifier can be queried based on the mapping relationship. Then, the information identifier extracted from the third URL is filled into the position to be filled in the URL template, and a second URL containing target information for displaying the payment page can be obtained.

[0096] In actual application, if the first URL obtained by the payment terminal device also includes amount information, the information identifier and the amount information can be filled into the position to be filled in the URL template to obtain the second URL containing the amount information. Of course, if the first URL does not include the amount information, the second URL can be obtained by simply filling the information identifier into the position to be filled in the URL template. For example: still taking the third URL as: alipay: / / nfc / app? s=sn&v=1q2w3e4r5t6y7u8i_0.01 as an example, where the URL query identifier is sn, the information identifier is 1q2w3e4r5t6y7u8i, the amount information is 0.01, and the URL template corresponding to the query identifier sn is: alipays: / / platformapi / startApp? appId=112233&appScheme=NFC_ABC&pageParams=%12345qwert$[value]$%6789, where $[value]$ represents the position to be filled. After filling the information identifier 1q2w3e4r5t6y7u8i and the amount information 0.01 into the to-be-filled position of the URL template, the second URL can be obtained: alipays: / / platformapi / startApp?appId=112233&appScheme=NFC_ABC&pageParams=%12345qwert1q2w3e4r5t6y7u8i_0.01%6789.

[0097] In this embodiment of the specification, the target information included in the second URL may include a component identifier, a task identifier, and a task parameter.

[0098] Correspondingly, Figure 2 In the method, in step 206, displaying the payment page based on the second URL may specifically include:

[0099] Determine a first application component corresponding to the component identifier;

[0100] Determine the page rendering task corresponding to the task identifier;

[0101] The first application component is used to execute the page rendering task based on the task parameters to render the payment page.

[0102] In the embodiments of this specification, different component identifiers may correspond to different application components, different task identifiers may correspond to different page rendering tasks, and different task parameters may be used to render different pages. The following example specifically illustrates the component identifier, task identifier, and task parameter contained in the second URL, taking the second URL as 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. It can be seen that the information identifier (1q2w3e4r5t6y7u8i) is carried in the task parameter.

[0103] In the embodiment of this specification, the first application component is a component in the application of the payment terminal device for rendering the payment page based on the second URL. Specifically, the first application component can be an Activity component. In actual applications, the page corresponding to the Activity component can be set to be visible to the user, so that during the operation of the first application component, the application can render the payment page corresponding to the second URL and display the payment page to the user.

[0104] In the embodiment of this specification, the use of the first application component to perform the page rendering task based on the task parameters to render the payment page may specifically refer to rendering the payment page in a native manner. Since the payment page is rendered in a native manner without loading a container, the page rendering efficiency can be improved, which is conducive to reducing the time consumption of page rendering.

[0105] In actual applications, when the preset conditions are met, for example, when the native payment page has a fatal problem and is unavailable, or when new capabilities need to be released urgently, the payment page can also be rendered in a container manner to maximize the guarantee that users can open the payment page smoothly when the native method cannot render the payment page.

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

[0107] The adopting the first application component to perform the page rendering task based on the task parameters to render the payment page may specifically include:

[0108] Based on the task parameters, obtaining pre-stored page information; the page information includes at least one of picture information and text information;

[0109] Based on the page information, the first application component is used to perform the page rendering task to render a payment page.

[0110] In an embodiment of the present specification, the pre-stored page information obtained based on the task parameters may determine the information included in the rendered payment page. If the pre-stored page information obtained based on the task parameters includes image information and text information, the payment page rendered based on the page information may include both image information and text information.

[0111] In practical applications, the image information in the page information may include but is not limited to: NFC payment scene pictures, NFC payment operation process guidance pictures, NFC payment promotion pictures, etc. The text information in the page information may include but is not limited to: "Pay with one touch, come and experience it", "Pay with a sticker", "NFC payment, one step faster", etc.

[0112] In the embodiment of the present specification, the task parameter included in the second URL may also carry amount information; the amount information may include first amount information or second amount information; the first amount information indicates a set amount value; the second amount information indicates that no amount value is provided;

[0113] When the amount information is the first amount information, the payment page displays the set amount value;

[0114] When the amount information is the second amount information, the amount value is not displayed in the payment page.

[0115] In an embodiment of the present specification, if the first URL obtained by the user's payment terminal device does not include amount information, the amount information in the task parameters contained in the second URL corresponds to the second amount information, and the payment page displayed to the user does not display the amount value. Figure 3a A schematic diagram of a payment page provided in an embodiment of this specification, such as Figure 3a As shown, the amount is not displayed on the payment page.

[0116] In an embodiment of the present specification, if the first URL obtained by the user's payment terminal device includes amount information, the amount information in the task parameters contained in the second URL corresponds to the first amount information, and the amount value will be displayed on the payment page finally displayed to the user. Figure 3bA schematic diagram of another payment page provided in an embodiment of this specification, such as Figure 3b As shown, the payment page shows that the amount to be paid by the user is 0.01 yuan.

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

[0118] Based on this, the payment page may also include a payment control.

[0119] Correspondingly, Figure 2 The method of claim 1, wherein in step 206, after displaying the payment page based on the second URL, the method may further include:

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

[0121] receiving the service execution result information returned by the application server; 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 through querying according to the information identifier;

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

[0123] In the embodiments of this specification, the payment control in the payment page may specifically include a payment confirmation control. In actual applications, the payment control may also specifically include a payment cancellation control. The payment page may include both a payment confirmation control and a payment cancellation control for the user to select; or Figure 3b As shown in , the included payment control is "Confirm Payment", but the payment cancellation control is not included. The settings for the payment controls can be flexibly set and adjusted according to actual needs.

[0124] In actual applications, the application that performs NFC payment processing at the payment terminal device needs to be started before displaying the payment page to the user. The startup of the application is divided into cold start and hot start, and the call-end processes corresponding to these two startup methods are different.

[0125] Based on this, Figure 2 In the method, in step 206, displaying the payment page based on the second URL may specifically include:

[0126] When the application is cold started, the payment page is displayed directly.

[0127] In the embodiments of this specification, application cold start refers to the process of restarting an application after it has not been run or the process has been terminated. In this process, the system needs to recreate the process and initialize the application, which usually takes longer than a hot start (the application is still running in memory). During the cold start process, the system needs to load all resources and data of the application from scratch, including the application's executable files, data files, and possible system resources.

[0128] In the prior art, when the caller is cold-started, the application at the payment terminal device will also load other processes besides the main process, such as the push process, the tools process, and the mini-program process. These processes besides the main process are non-essential processes in the NFC payment caller process. Running these processes will reduce the caller efficiency and increase the caller time. When the caller is cold-started, multiple pages need to be loaded, such as: the caller connection page, the transfer page, the scan intermediate page, the splash screen page, the application homepage, and the payment page. Among them, only the caller connection page and the payment page are necessary pages. Loading other redundant pages will inevitably increase the caller time.

[0129] In the embodiments of this specification, the direct display of the payment page in the case of a cold start of the application means that in the case of a cold start of the application, non-essential pages in the NFC payment process such as the application home page, splash page, transfer page, and scan intermediate page 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. This avoids the time-consuming loading of non-essential processes, and also avoids the time-consuming loading of some non-essential pages before loading the payment page, effectively reducing the time-consuming opening of the payment page in the NFC payment process and improving the efficiency of the call end.

[0130] For hot start, Figure 2 In the method, in step 206, before displaying the payment page based on the second URL, the method may further include:

[0131] When the application is hot-started, the page stack is cleared.

[0132] In the embodiments of this specification, application hot start refers to the user opening the application again when the application has been opened on the user terminal but is placed in the background for some reason (such as the user pressing the back key, the Home key, etc.). 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 recreate the Application class, but directly restores the state of the application from the existing process and creates and initializes the MainActivity class. Therefore, the hot start process is relatively fast and the user experience is smoother.

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

[0134] In the Activity stack, each Activity has its own state information, including its view state, life cycle state, and other related data. This information can be saved and restored through the system's life cycle management mechanism. The "clear stack" operation refers to removing some or all Activities in the Activity stack. In actual applications, the clear stack operation can be implemented through startActivityForResult, Intent Flags, or methods inside the component.

[0135] In the embodiments of this specification, clearing the page stack can clear the pages of the application already existing in the background, such as clearing the home page, splash screen page, scan page, etc. of the existing application. This can avoid the user being presented with irrelevant pages during the NFC payment process, and then jumping from the irrelevant page to the payment page. After clearing the page stack, the payment page can be directly presented to the user during the call process, which is conducive to improving the user experience.

[0136] In actual applications, near field communication is established between the user's payment terminal device and the NFC tag device, and the user's payment terminal device can be used as an NFC main device to transmit near field communication signals.

[0137] Based on this, Figure 2In the method, in step 202, obtaining the first URL from the NFC tag device based on the near field communication method may specifically include:

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

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

[0140] In actual applications, the first URL obtained by the payment terminal device based on NFC may also include domain name information, and the domain name information may be used to indicate an application at the payment terminal device that needs to be used for this NFC payment.

[0141] Based on this, Figure 2 In the method, in step 202, obtaining the first URL from the NFC tag device based on the near field communication method may specifically include:

[0142] The operating system obtains a first URL provided by the NFC tag device through near field communication; the first URL also includes domain name information;

[0143] Determining an application corresponding to the domain name information;

[0144] The first URL is transmitted to the application.

[0145] In the embodiment of the present specification, after the payment terminal device obtains the first URL sent by the NFC tag device based on NFC, the operating system can first identify the protocol type information of the first URL to determine whether to respond to the first URL, and then identify the domain name information in the first URL to determine the application to be called according to the domain name information. After the operating system determines the application to be called, the first URL can be transmitted to the application, so that the main process of the application can determine the second URL according to the first URL, and further render the payment page according to the second URL.

[0146] In actual applications, the first URL may also include path information, and the path information may be used to indicate an application component of an application program that needs to be used for this NFC payment.

[0147] Correspondingly, the determining the application corresponding to the domain name information may specifically include:

[0148] Determine a second application component corresponding to the domain name information and the path information.

[0149] Correspondingly, transmitting the first URL to the application may specifically include:

[0150] The first URL is transmitted to the second application component.

[0151] In an embodiment of the present specification, after the operating system obtains the first URL, it can identify the domain name information and path information in the first URL, and determine the 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 pre-registered in the operating system and corresponding to the domain name information and the path information.

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

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

[0154] Figure 4 The following is a flow chart of a method for sending information based on NFC provided in an embodiment of the present specification. From a hardware perspective, the execution subject of the process may be an NFC tag device. From a program perspective, the execution subject of the process may be an application installed on the NFC tag device. Figure 4 As shown, the process may include the following steps:

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

[0156] Step 404: In response to the near field communication signal, a first URL is sent to the payment terminal device via near field communication; the length of the first URL is less than or equal to the maximum number of bytes that can be transmitted at a single time by the NFC tag device based on the near field communication method; the first URL includes a URL query identifier; the URL query identifier is used by the payment terminal device to determine a second URL; the second URL includes target information for displaying a payment page.

[0157] In the embodiments of this specification, 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 be Figure 2 The meanings of the terms mentioned in the embodiments of the method are consistent. Since the process of the NFC tag device sending the first URL to the payment terminal device through the near field communication method has been described in detail above, it will not be repeated here.

[0158] In the embodiment of this specification, the payment terminal device is used as an NFC card reader. When the payment terminal device is close to the NFC tag device, it can transmit a near field communication signal to the NFC tag device, thereby triggering near field communication with the NFC tag device, and then obtaining the first URL from the NFC tag device.

[0159] Figure 4 In the method, since the length of the first URL obtained by the payment terminal device from the NFC tag device based on the near field communication method is not greater than the maximum number of bytes that the NFC tag device can transmit at a time based on the near field communication method, the situation that the NFC tag device needs to perform multiple sub-packet transmissions to the payment terminal device due to the URL being too long 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. In addition, the first URL transmitted by the NFC tag device to the payment terminal device through the near field communication method carries a URL query identifier, and the payment terminal device can determine the second URL required to display the payment page based on the URL query identifier and the stored data, thereby obtaining the second URL corresponding to the first URL through a local query method, without the need to access through the network, further reducing the time spent on opening the payment page during the NFC payment process, effectively improving the terminal call speed, and thus helping to improve the user experience and NFC payment efficiency.

[0160] based on Figure 4 The method in this specification also provides some specific implementation plans of the method, which are described below.

[0161] In the embodiments of this specification, Figure 4 In the method, in step 402, before receiving the near field communication signal transmitted by the payment terminal device, the method may also include:

[0162] Get the preset trigger operation;

[0163] In response to the trigger operation, obtaining first service information;

[0164] Sending a URL acquisition request to an application server; the URL acquisition request carries the first service information;

[0165] Receive the first URL returned by the application server; the first URL carries an information identifier; the information identifier is used to query business description information; the business description information includes the first business information and the second business information; the second business information includes information related to the business corresponding to the first URL obtained by the application server.

[0166] In the embodiments of this specification, the preset trigger operation may include but is not limited to: the cashier clicks the payment button on the payment device, the user clicks the payment button on the vending machine, etc. The first business information may include but is not limited to: order number, merchant number, order time, order amount, etc. The second business information may include but is not limited to: the generation time of the first URL, the issuance time of the first URL, the content of the first URL, the payment time limit of the order, whether the order has been paid, the identity of the paying user, etc.

[0167] In actual applications, the first business information may include order-related information sent by the NFC tag device to the application server. Some of the information in the second business information may include information sent by the payment terminal device to the application server, such as identification information of the payment user. Some of the information in the second business information may also include information generated by the application server, such as the generation time of the first URL, the validity period of the information identification, etc.

[0168] In the embodiment of this specification, the application server can obtain the information identifier (token) by generating a random code, and store the information identifier in association with the business description information. Thus, when the application server receives a business request with the information identifier sent by the payment terminal device, it can query the corresponding business description information based on the information identifier, and then promote the business process.

[0169] Figure 5 The flowchart of a method for sending a URL provided in an embodiment of the present specification is shown in FIG. From a hardware perspective, the execution subject of the process may be an application server. From a program perspective, the execution subject of the process may be an application program installed on the application server. Figure 5 As shown, the process may include the following steps:

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

[0171] Step 504: 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 in a single NFC transmission.

[0172] Step 506: Send the first URL to the NFC tag device; the first URL is used to be obtained from the NFC tag device by the payment terminal device in a near field communication manner; the first URL includes a URL query identifier; the URL query identifier is used by the payment terminal device to query a second URL, and the second URL includes target information for the payment terminal device to display a payment page.

[0173] In the embodiments of this specification, 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 be Figure 2 The meanings of the terms mentioned in the embodiments of the method are consistent. Since the process of the NFC tag device sending the first URL to the payment terminal device through the near field communication method has been described in detail above, it will not be repeated here.

[0174] In the embodiment of the present specification, 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 may carry information about the type of business scenario in which the NFC tag device is located.

[0175] Based on this, Figure 5 In the method, in step 504, generating a first URL in response to the URL acquisition request may specifically include:

[0176] In response to the URL acquisition request, determining the business scenario type of the NFC tag device;

[0177] A first URL corresponding to the business scenario type is generated; the URL query identifier carried in the first URL is used to query a second URL corresponding to the business scenario type.

[0178] In the embodiments of this specification, the business scenario types of the NFC tag device may include but are not limited to: POS payment scenario, vending machine payment scenario, service machine water sales business scenario, gate opening scenario, ordering scenario, etc. In actual applications, different business scenarios may correspond to different URL query identifiers, and different URL query identifiers may query different second URLs, and then display different payment pages to users based on different second URLs. Since the aforementioned content has already elaborated in detail the process of determining the second URL corresponding to the business scenario type according to the URL query identifier carried in the first URL, it will not be repeated here.

[0179] Optional, Figure 5In the method, in step 504, generating a first URL in response to the URL acquisition request may specifically include:

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

[0181] A first URL carrying the information identifier is generated.

[0182] In the embodiment of the present specification, the information identifier may be generated by the application server based on the first business information, for example, the application server generates the information identifier based on the order number or the merchant number. Alternatively, the information identifier may also be a character string randomly generated by the application server. In the application server, the generated information identifier and the business description information may be correspondingly associated and stored, so that when the business description information is needed later, it can be queried based on the information identifier.

[0183] Correspondingly, Figure 5 The method, in step 506, after sending the first URL to the NFC tag device, may also include:

[0184] Obtaining a service request sent by a payment terminal device; the service request carries the information identifier;

[0185] Based on the information identifier, querying the business description information for executing the business corresponding to the business request;

[0186] Execute the business based on the queried business description information and obtain business execution result information;

[0187] The execution result information is sent to the payment terminal device.

[0188] Specifically, take the payment service for a certain order as an example: when the user's payment terminal device displays the payment page for the user, if the user approves the order, the payment confirmation control in the payment page can be triggered. When 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.

[0189] After receiving 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 carried in the service request. Since the service description information may involve relevant information of 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 feedback the payment result information to the payment terminal device.

[0190] Figure 6 The embodiments of this specification provide corresponding to Figure 2 A swimlane diagram of a method of opening a payment page based on NFC. Figure 6 As shown, the method flow of opening a payment page based on NFC may involve execution entities such as an NFC tag device, a payment terminal device, and an application server; the method flow may include a first URL generation phase, a first URL transmission phase, a terminal calling phase, and a service execution phase, and may specifically include the following steps:

[0191] Step 602: The NFC tag device obtains a preset trigger operation.

[0192] Step 604: the NFC tag device obtains first service information in response to the triggering operation.

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

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

[0195] Step 610: The application server associates and stores the information identifier with the service description information, and generates a first URL carrying the information identifier.

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

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

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

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

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

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

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

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

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

[0205] 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.

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

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

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

[0209] Step 638: The application server executes 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.

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

[0211] Among them, steps 602 to 614 are the first URL generation stage, and in the first URL generation stage, information interaction between the NFC tag device and the application server may be involved. Steps 616 to 622 are the first URL transmission stage, and in the first URL transmission stage, information interaction between the NFC tag device and the payment terminal device may be involved. Steps 624 to 632 are the call-up stage, and the call-up stage may be performed at the payment terminal device. Steps 634 to 640 are the service execution stage, and in the service execution stage, information interaction between the payment terminal device and the application server may be involved.

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

[0213] Figure 7 The embodiments of this specification provide corresponding to Figure 2 A schematic diagram of a device for opening a payment page based on NFC. The device can be applied to a payment terminal device, including:

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

[0215] The URL conversion module 704 is used 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.

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

[0217] based on Figure 7 The present specification also provides some specific implementations of the device, which will be described below.

[0218] Optionally, the device may further include:

[0219] A parsing module is used to parse the business parameter information in the first URL to obtain a third URL; the business parameter information includes the URL query identifier and the information identifier; the information identifier is used to query the business description information corresponding to the first URL.

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

[0221] Optionally, the URL conversion module 704 may specifically include:

[0222] The URL template query unit is used to query the URL template according to the URL query identifier; the URL template includes a position to be filled.

[0223] The second URL acquisition unit is used to fill the information identifier into the to-be-filled position to obtain a second URL; the second URL includes the target information; and the information identifier is carried in the target information.

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

[0225] Correspondingly, the display module 706 may specifically include:

[0226] The first determining unit is used to determine a first application component corresponding to the component identifier.

[0227] The second determining unit is used to determine the page rendering task corresponding to the task identifier.

[0228] A rendering unit is used to use the first application component to perform the page rendering task based on the task parameters to render the payment page.

[0229] Optionally, the rendering unit may specifically include:

[0230] The page information acquisition subunit is used to acquire pre-stored page information based on the task parameters; the page information includes at least one of picture information and text information.

[0231] The rendering subunit is used to use the first application component to perform the page rendering task based on the page information and render a payment page.

[0232] Optionally, in the device, the task parameters may also carry amount information; the amount information includes first amount information or second amount information; the first amount information may indicate a set amount value; the second amount information may indicate that no amount value is provided; when the amount information is the first amount information, the set amount value is displayed on the payment page; when the amount information is the second amount information, the amount value is not displayed on the payment page.

[0233] Optionally, the payment page may include a payment control.

[0234] Correspondingly, the device may further include:

[0235] A business request sending module is used to send a business request to an application server based on the second URL in response to a user's triggering operation on the payment control; the business request carries an information identifier; the information identifier is used to query the business description information corresponding to the first URL.

[0236] The service execution result information receiving module is used to receive the service execution result information returned by the application server; 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.

[0237] The payment result page display module is used to display the payment result page based on the business execution result information.

[0238] Optionally, the display module 706 may specifically include:

[0239] The display unit is used to directly display the payment page when the application is cold started.

[0240] Optionally, the device may further include:

[0241] The stack clearing module is used to clear the page stack when the application is hot started.

[0242] Optionally, the URL acquisition module 702 may specifically include:

[0243] The signal transmitting unit is used for the payment terminal device to transmit a near field communication signal as an NFC master device.

[0244] The first URL acquisition unit is used to acquire the first URL sent by the NFC tag device in a near field communication manner in response to the near field communication signal.

[0245] Optionally, the URL acquisition module 702 may specifically include:

[0246] The first URL acquisition unit is used for the operating system to acquire a first URL provided by the NFC tag device through a near field communication method; the first URL also includes domain name information.

[0247] An application determining unit is used to determine an application corresponding to the domain name information.

[0248] The first URL transmission unit is used to transmit the first URL to the application.

[0249] Optionally, the first URL may also include path information.

[0250] Correspondingly, the application determination unit may specifically include:

[0251] The application program determination subunit is used to determine a second application component corresponding to the domain name information and the path information.

[0252] Correspondingly, the first URL transmission unit may specifically include:

[0253] The first URL transmission subunit is used to transmit the first URL to the second application component.

[0254] Figure 8 The embodiments of this specification provide corresponding to Figure 4 A schematic diagram of a structure of an information sending device based on NFC. The device can be applied to an NFC tag device, including:

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

[0256] The signal sending module 804 is used to send a first URL to the payment terminal device via near field communication 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 at a single time by the NFC tag device based on the near field communication method; the first URL contains a URL query identifier; the URL query identifier is used by the payment terminal device to determine a second URL; the second URL contains target information for displaying a payment page.

[0257] Optionally, the device may further include:

[0258] The first acquisition module is used to acquire a preset trigger operation.

[0259] The second acquisition module is used to acquire the first service information in response to the trigger operation.

[0260] The URL acquisition request sending module is used to send a URL acquisition request to the application server; the URL acquisition request carries the first business information.

[0261] A first URL receiving module is used to receive the first URL returned by the application server; the first URL carries an information identifier; the information identifier is used to query business description information; the business description information includes the first business information and the second business information; the second business information includes information related to the business corresponding to the first URL obtained by the application server.

[0262] Fig. 9 The embodiments of this specification provide corresponding to Figure 5 A schematic diagram of a device for sending a URL. The device can be applied to an application server, including:

[0263] The request acquisition module 902 is used to acquire the URL acquisition request sent by the NFC tag device.

[0264] The URL generation module 904 is used to generate 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 the maximum number of bytes that can be transmitted in a single NFC transmission.

[0265] The URL sending module 906 is used to send the first URL to the NFC tag device; the first URL is used to be obtained 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 by the payment terminal device to query a second URL, and the second URL contains target information for the payment terminal device to display a payment page.

[0266] Optionally, the URL generation module 904 may specifically include:

[0267] A business scenario type determination unit is used to determine the business scenario type of the NFC tag device in response to the URL acquisition request.

[0268] The first URL generating unit is used to generate a first URL corresponding to the business scenario type; the URL query identifier carried in the first URL is used to query a second URL corresponding to the business scenario type.

[0269] Optionally, the URL generation module 904 may specifically include:

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

[0271] The first URL generating unit is used to generate a first URL carrying the information identifier.

[0272] Optionally, the device may further include:

[0273] The service request acquisition module is used to acquire the service request sent by the payment terminal device; the service request carries the information identifier.

[0274] The service description information query module is used to query the service description information used to execute the service corresponding to the service request based on the information identifier.

[0275] The business execution result information acquisition module is used to execute the business based on the queried business description information and obtain the business execution result information.

[0276] The execution result information sending module is used to send the execution result information to the payment terminal device.

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

[0278] Fig.10 The embodiments of this specification provide corresponding to Figure 2 A schematic diagram of the structure of a payment terminal device. Fig.10 As shown, the device 1000 may be a payment terminal device, and the device 1000 may include:

[0279] at least one processor 1010; and,

[0280] A memory 1030 in communication with the at least one processor; wherein,

[0281] The memory 1030 stores instructions 1020 executable by the at least one processor 1010. The instructions are executed by the at least one processor 1010 to enable the at least one processor 1010 to:

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

[0283] Based on the data stored in the payment terminal device, a second URL corresponding to the URL query identifier is determined; the second URL includes target information for displaying the payment page.

[0284] Based on the second URL, the payment page is displayed.

[0285] Fig.11 The embodiments of this specification provide corresponding to Figure 4 A schematic diagram of the structure of an NFC tag device. Fig.11 As shown, the device 1100 may be an NFC tag device, and the device 1100 may include:

[0286] at least one processor 1110; and,

[0287] A memory 1130 is communicatively connected to the at least one processor; wherein,

[0288] The memory 1130 stores instructions 1120 executable by the at least one processor 1110. The instructions are executed by the at least one processor 1110 to enable the at least one processor 1110 to:

[0289] Receive near field communication signals transmitted by payment terminal equipment.

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

[0291] Fig.12The embodiments of this specification provide corresponding to Figure 5 A schematic diagram of the structure of an application server. Fig.12 As shown, the device 1200 may be an application server, and the device 1200 may include:

[0292] at least one processor 1210; and,

[0293] A memory 1230 is communicatively connected to the at least one processor; wherein,

[0294] The memory 1230 stores instructions 1220 executable by the at least one processor 1210. The instructions are executed by the at least one processor 1210 to enable the at least one processor 1210 to:

[0295] Get the URL request sent by the NFC tag device.

[0296] 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 a maximum number of bytes that can be transmitted in a single NFC.

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

[0298] Each embodiment in this specification is described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. Figure 10-12 As for the device shown, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0299] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0300] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, 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. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0301] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers 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 also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

[0302] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, 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.

[0303] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0304] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0305] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0306] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0307] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

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

[0309] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0310] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. 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 technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0311] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0312] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification may 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 may be located in local and remote computer storage media, including storage devices.

[0313] The above description is only an embodiment of the present specification and is not intended to limit the present specification. For those skilled in the art, the present specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification shall be included in the scope of the claims of the present specification.

Claims

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

2. The method according to 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 the service parameter information in the first URL to obtain a third URL; The service parameter information includes the URL query identifier and the information identifier; The information identifier is used to query the business description information corresponding to the first URL; The URL query identifier and the information identifier are extracted from the third URL.

3. The method according to claim 2, wherein parsing the service parameter information in the first URL specifically comprises: Determine, according to the protocol header information in the first URL, an application corresponding to the protocol header information; The main process of the application is started to parse the service parameter information after the designated characters in the first URL.

4. The method according to claim 2, wherein determining the second URL corresponding to the URL query identifier based on the data stored in the payment terminal device specifically comprises: Querying the URL template according to the URL query identifier; The URL template includes a position to be filled; Fill the information identifier into the position to be filled to obtain a second URL; the second URL contains the target information; The information identifier is carried in the target information.

5. According to the method as claimed in claim 1, different payment scenarios correspond to different URL query identifiers.

6. The method according to claim 1, wherein the target information includes a component identifier, a task identifier and a task parameter; The displaying the payment page based on the second URL specifically includes: Determine a first application component corresponding to the component identifier; Determine the page rendering task corresponding to the task identifier; The first application component is used to execute the page rendering task based on the task parameters to render the payment page.

7. The method according to claim 6, wherein the step of using the first application component to perform the page rendering task based on the task parameters to render a payment page specifically comprises: Based on the task parameters, obtaining pre-stored page information; The page information includes at least one of picture information and text information; Based on the page information, the first application component is used to perform the page rendering task to render a payment page.

8. The method according to claim 6, wherein the task parameter also carries amount information; the amount information includes first amount information or second amount information; the first amount information indicates a set amount value; the second amount information indicates that no amount value is provided; When the amount information is the first amount information, the payment page displays the set amount value; When the amount information is the second amount information, the amount value is not displayed in the payment page.

9. The method according to claim 1, wherein the payment page includes a payment control; after displaying the payment page based on the second URL, the method further includes: In response to a triggering operation of the payment control by the user, sending a service request to an 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; Receiving the service execution result information returned by the application server; 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 through querying according to the information identifier; Based on the business execution result information, a payment result page is displayed.

10. The method according to claim 1, wherein displaying the payment page based on the second URL specifically comprises: When the application is cold started, the payment page is displayed directly.

11. The method according to claim 1, before displaying the payment page based on the second URL, further comprising: When the application is hot-started, the page stack is cleared.

12. The method according to claim 1, wherein obtaining the first URL from the NFC tag device based on near field communication specifically comprises: The payment terminal device transmits a near field communication signal as an NFC master device; The first URL sent by the NFC tag device through near field communication in response to the near field communication signal is obtained.

13. The method according to claim 1, wherein obtaining the first URL from the NFC tag device based on near field communication specifically comprises: The operating system obtains the first URL provided by the NFC tag device through near field communication; The first URL also includes domain name information; Determining an application corresponding to the domain name information; The first URL is transmitted to the application.

14. The method according to claim 13, wherein the first URL further includes path information; and the determining the application corresponding to the domain name information specifically comprises: Determine a second application component corresponding to the domain name information and the path information; The transmitting the first URL to the application specifically includes: The first URL is transmitted to the second application component.

15. The method of claim 1, wherein: The length of the first URL is less than or equal to the maximum number of bytes that can be transmitted at one time by the NFC tag device based on the near field communication method; the maximum number of bytes includes 124 bytes.

16. An information sending method 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 via near field communication; the first URL includes a URL query identifier; The URL query identifier is used by the payment terminal device to determine a second URL; the second URL contains target information for displaying a payment page.

17. A method for sending a URL, applied to an application server, comprising: Get the URL acquisition request sent by the NFC tag device; In response to the URL acquisition request, generating a first URL; Sending the first URL to the NFC tag device; The first URL is used to be obtained by the payment terminal device from the NFC tag device in a near field communication manner; the first URL includes a URL query identifier; The URL query identifier is used by the payment terminal device to query a second URL, and the second URL contains target information for the payment terminal device to display a payment page.

18. The method of claim 17, wherein generating a first URL in response to the URL acquisition request specifically comprises: In response to the URL acquisition request, determining the business scenario type of the NFC tag device; Generate a first URL corresponding to the business scenario type; The URL query identifier carried in the first URL is used to query a second URL corresponding to the business scenario type.

19. A device for opening a payment page based on NFC, applied to a payment terminal device, comprising: A URL acquisition module, used to acquire a first URL from an NFC tag device based on a near field communication method; The first URL includes a URL query identifier; A URL conversion module, for determining a second URL corresponding to the URL query identifier based on the data stored in the payment terminal device; the second URL includes target information for displaying the payment page; A display module is used to display the payment page based on the second URL.

20. An NFC-based information sending device, applied to an NFC tag device, comprising: A signal receiving module, used 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 via near field communication in response to the near field communication signal; the first URL includes a URL query identifier; The URL query identifier is used by the payment terminal device to determine a second URL; the second URL contains target information for displaying a payment page.

21. A device for sending a URL, applied to an application server, comprising: A request acquisition module is used to obtain a URL acquisition request sent by an NFC tag device; A URL generation module, configured to generate a first URL in response to the URL acquisition request; The byte number threshold is the maximum number of bytes that can be transmitted in a single NFC transmission; A URL sending module, used for sending the first URL to the NFC tag device; The first URL is used to be obtained by the payment terminal device from the NFC tag device in a near field communication manner; the first URL includes a URL query identifier; The URL query identifier is used by the payment terminal device to query a second URL, and the second URL contains target information for the payment terminal device to display a payment page.

22. A payment terminal device, comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: Acquire a first URL from an NFC tag device based on a near field communication method; the first URL includes a URL query identifier; Based on the data stored in the payment terminal device, determining a second URL corresponding to the URL query identifier; the second URL includes target information for displaying the payment page; Based on the second URL, the payment page is displayed.

23. An NFC tag device, comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: 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 via near field communication; the first URL includes a URL query identifier; The URL query identifier is used by the payment terminal device to determine a second URL; the second URL contains target information for displaying a payment page.

24. An application server, comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: Get the URL acquisition request sent by the NFC tag device; In response to the URL acquisition request, generating a first URL; The first URL is sent to the NFC tag device; the first URL is used to be obtained from the NFC tag device by the payment terminal device in a near field communication manner; the first URL includes a URL query identifier; the URL query identifier is used by the payment terminal device to query a second URL, and the second URL includes target information for the payment terminal device to display a payment page.

Images