NFC-based service execution method, device and equipment

Abstract

The embodiment of the invention discloses a service execution method, device and equipment based on NFC (Near Field Communication). According to the scheme, the method comprises the steps that based on a near field communication mode, an operating system obtains a uniform resource locator (URL) from NFC label equipment, a target application is determined based on domain name information in the URL, and the target application is started so that the target application can execute a service process corresponding to the URL. Wherein the URL comprises protocol type information and domain name information which indicate that the URL conforms to a hypertext transfer security protocol, and light application card information which is used for being recognized by an IOS operating system in a light application card mode.

Description

[0001] This application is a divisional application of the Chinese patent application. The application date of the original application is: August 5, 2024; the application number is: 202411067880.4; the name of the invention is: A business execution method, device and equipment based on NFC. Technical Field

[0002] The present invention relates to the technical field of service processing of wireless communications, and in particular to a service execution method, device and equipment based on NFC. Background Art

[0003] Near Field Communication (NFC) is widely used in various fields due to its convenience, security, and low power consumption. However, in some special scenarios, when executing services based on NFC, there may be situations where services cannot be executed successfully. For example, for terminal devices running the iOS operating system, when the terminal device is in the locked screen state, it is impossible to execute the call-end task based on NFC.

[0004] Therefore, how to improve the success rate of executing business based on NFC has become a technical problem that needs to be solved urgently. Summary of the invention

[0005] The embodiments of this specification provide a method, apparatus and device for executing a service based on NFC to improve the success rate of executing a service based on NFC.

[0006] To solve the above technical problems, the embodiments of this specification are implemented as follows:

[0007] An NFC-based service execution method provided in an embodiment of the present specification is applied to a user terminal device, including: an operating system obtains a uniform resource locator URL provided by an NFC tag device through near field communication; the URL contains protocol type information, domain name information and light application card parameters; the protocol type information indicates that the URL complies with the Hypertext Transfer Protocol Security Protocol; the light application card parameters are used to be identified by the IOS operating system in the form of a light application card; an application corresponding to the domain name information is started; and the application is used to execute the business process corresponding to the URL.

[0008] An NFC-based service execution method provided in an embodiment of this specification is applied to an NFC tag device, including:

[0009] Receive a near field communication signal transmitted by a user terminal device; in response to the near field communication signal, send a uniform resource locator URL to the user terminal device via near field communication; the URL includes protocol type information, domain name information and light application card parameters; the protocol type information indicates that the URL complies with the Hypertext Transfer Protocol Security Protocol; the light application card parameters are used to be identified by the IOS operating system in the form of a light application card; the domain name information is used by the user terminal device to start the application corresponding to the domain name information; the application is used to execute the business process corresponding to the URL.

[0010] An NFC-based service execution device provided in an embodiment of the present specification is applied to a user terminal device, including:

[0011] The URL acquisition module is used to acquire the uniform resource locator URL provided by the NFC tag device through near field communication; the URL includes protocol type information, domain name information and light application card parameters; the protocol type information indicates that the URL complies with the Hypertext Transfer Protocol Security Protocol; the light application card parameters are used to be identified by the IOS operating system in the form of a light application card;

[0012] An application startup module is used to start the application corresponding to the domain name information; the application is used to execute the business process corresponding to the URL.

[0013] An NFC-based service execution device provided in an embodiment of the present specification is applied to an NFC tag device, including:

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

[0015] An information sending module is used to send a uniform resource locator URL to a user terminal device via near field communication in response to the near field communication signal; the URL includes protocol type information, domain name information and light application card parameters; the protocol type information indicates that the URL complies with the Hypertext Transfer Protocol Security Protocol; the light application card parameters are used to be identified by the IOS operating system in the form of a light application card; the domain name information is used by the user terminal device to start the application corresponding to the domain name information; the application is used to execute the business process corresponding to the URL.

[0016] A user terminal device provided in an embodiment of the present specification includes:

[0017] at least one processor; and,

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

[0019] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can: obtain a uniform resource locator URL provided by an NFC tag device through near field communication; the URL contains protocol type information, domain name information and light application card parameters; the protocol type information indicates that the URL complies with the Hypertext Transfer Protocol Security Protocol; the light application card parameters are used to be identified by the IOS operating system in the form of a light application card; start an application corresponding to the domain name information; the application is used to execute the business process corresponding to the URL.

[0020] An NFC tag device provided in an embodiment of this specification includes:

[0021] at least one processor; and,

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

[0023] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can: receive a near field communication signal transmitted by a user terminal device; in response to the near field communication signal, send a uniform resource locator URL to the user terminal device via near field communication; the URL includes protocol type information, domain name information and light application card parameters; the protocol type information indicates that the URL complies with the Hypertext Transfer Protocol Security Protocol; the light application card parameters are used to be identified by the IOS operating system in the form of a light application card; the domain name information is used by the user terminal device to start the application corresponding to the domain name information; the application is used to execute the business process corresponding to the URL.

[0024] At least one embodiment of this specification can achieve the following beneficial effects:

[0025] The URL transmitted based on the near field communication method contains protocol type information that complies with the Hypertext Transfer Protocol Security Protocol, and contains light application card parameters that can be used to be identified by the iOS operating system in the form of a light application card. This allows the URL transmitted based on the near field communication method to be recognized by many operating systems, including but not limited to iOS, so that the call success rate of devices of various operating systems can be greatly improved on the basis that the URL can be recognized by many operating systems, thereby improving the success rate of business execution. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the following briefly introduces the drawings required for use in the embodiments or the prior art description. 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 creative work.

[0027] Figure 1 This is a schematic diagram of an application scenario of an NFC-based service execution method provided in an embodiment of this specification;

[0028] Figure 2 This is a flowchart of a method for executing a service based on NFC provided in an embodiment of this specification;

[0029] Figure 3 This is a schematic diagram of the structure of a URL provided in an embodiment of this specification;

[0030] Figure 4 This is a schematic diagram of a target application provided by an embodiment of this specification after being enabled;

[0031] Figure 5 This is a schematic diagram of a first preset page provided in an embodiment of this specification;

[0032] Figure 6 It is a schematic diagram of a display page including a banner page element provided in an embodiment of this specification;

[0033] Figure 7 This is a schematic diagram of a light application card provided in an embodiment of this specification;

[0034] Figure 8 This is a schematic diagram of a light application page provided in an embodiment of this specification;

[0035] Fig. 9 It is a flowchart of another NFC-based service execution method provided in an embodiment of this specification;

[0036] Fig.10 This specification provides an embodiment corresponding to Figure 2 and Fig. 9 A swim lane flow diagram of a business execution method based on NFC;

[0037] Fig.11 This specification provides an embodiment corresponding to Figure 2 and Fig. 9 Another swim lane flow chart of the NFC-based service execution method;

[0038] Fig.12 The embodiments of this specification provide corresponding to Figure 2A schematic diagram of the structure of a device for executing a service based on NFC;

[0039] Fig.13 The embodiments of this specification provide corresponding to Fig. 9 A schematic diagram of the structure of a device for executing a service based on NFC;

[0040] Fig.14 The embodiments of this specification provide corresponding to Figure 2 A schematic diagram of the structure of a user terminal device of a service execution method;

[0041] Fig.15 The embodiments of this specification provide corresponding to Fig. 9 A structural schematic diagram of an NFC tag device for executing a service. DETAILED DESCRIPTION

[0042] 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 specification, 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.

[0043] In order to facilitate understanding of the technical solutions of one or more embodiments of this specification, some terms are explained:

[0044] NFC: A short-range wireless communication technology that allows data exchange between NFC-enabled devices. NFC technology is based on radio frequency identification (RFID) technology, operates at a frequency of 13.56MHz, and the communication distance is usually within 10 cm.

[0045] URL: Uniform Resource Locator (URL), a standardized address format used to identify the location of resources on the Internet. Each part of the URL provides information about how to access the resource, including the protocol used, the host where the resource is located, the path, and query parameters.

[0046] Waking up a mobile application or making it active through a certain trigger mechanism.

[0047] Burning: Refers to the process of writing software, firmware or data to the storage medium in an electronic device or machine.

[0048] In the prior art, when waking up an application at a mobile terminal based on NFC technology, the terminal is usually called up based on the traditional URL protocol. The traditional URL protocol can be alipay, alipays and other types of protocols. However, based on the traditional URL protocol, when the operating system at the mobile terminal is an IOS system, the mobile terminal is in a locked screen state or within two seconds after the mobile terminal is unlocked, due to the protection mechanism carried by the IOS operating system itself, the traditional URL protocol cannot be recognized by the mobile terminal, which leads to the failure of the wake-up task of the application at the mobile terminal. Therefore, the success rate of calling up the application at the mobile terminal through NFC technology in the prior art is low.

[0049] The technical solutions provided by the embodiments of this specification are described in detail below in conjunction with the accompanying drawings.

[0050] Figure 1 The following is a schematic diagram of an application scenario of an NFC-based service execution method in an embodiment of this specification.

[0051] like Figure 1 As shown, the application scenario diagram includes an initiator device 101 and a target device 102 .

[0052] In the embodiments of this specification, the initiating device is a device that actively starts communication, is responsible for generating a radio frequency field and initiating the NFC communication process. The initiating device may include but is not limited to a smart phone, a tablet computer, a laptop computer, a desktop computer, an intelligent interactive device or other device that can actively send an NFC signal, and the initiating device 101 is any one of the initiating devices.

[0053] The target device is a passive response device, which responds to the request of the initiating device and exchanges data. The target device may include but is not limited to NFC tags, smart cards, access control cards, payment terminals or other smart devices, and the target device 102 is any one of the target devices.

[0054] The initiator device interacts with the target device by sending commands and data, and the target device relies on the RF field generated by the initiator device for energy supply and data transmission.

[0055] Figure 2 A flowchart of a method for executing a service based on NFC is provided in an embodiment of this specification. From a software perspective, the execution subject of the process can be a program or application client installed on a user terminal device with NFC function. From a hardware perspective, the execution subject of the process can be a user terminal device with NFC function.

[0056] like Figure 2 As shown, the method may include the following steps.

[0057] Step 202: The operating system obtains the uniform resource locator URL provided by the NFC tag device through near field communication; the URL contains protocol type information, domain name information and light application card parameters; the protocol type information indicates that the URL complies with the Hypertext Transfer Protocol Security Protocol; the light application card parameters are used to be identified by the IOS operating system in the form of a light application card.

[0058] In the embodiments of this specification, the operating system can be any one of the Android operating system, the Hongmeng operating system, and the IOS operating system; or the operating system can also be any operating system running on a device with NFC function, and there is no specific limitation on the type of operating system.

[0059] In the embodiments of this specification, the terminal device where the operating system is located may be collectively referred to as the user terminal device below. A communication connection is established between the user terminal device and the NFC tag device via near field communication. Based on the established communication connection, the NFC tag device sends a URL to the user terminal device. The URL may be a URL pre-stored on the NFC tag device by a developer, or may be a URL generated in real time in response to a request from an actual operator.

[0060] In the embodiments of this specification, the URL may include protocol type information, domain name information, path information, query parameter information, etc. The protocol in the URL may be Hyper Text Transfer Protocol (HTTP) or Hyper Text Transfer Protocol Secure (HTTPS). The domain name information is used to determine the application corresponding to the URL. The application corresponding to the URL is collectively referred to as the target application below.

[0061] In order to facilitate those skilled in the art to understand the present solution, a specific example is provided for URL in the embodiments of this specification.

[0062] like Figure 3 As shown, the URL includes 1-protocol header https, 2-domain name ulink.alipay.com, 3-path AAA, 4-first query parameter s=BBB and 5-second query parameter scheme=alipay%1A2B3c4d%1A2B3c4dCCC%5e6FVALUE.

[0063] Furthermore, in the business parameter information corresponding to the second query parameter, "CCC" may represent the scenario type information carried at the specified position of the URL; "VALUE" may represent the information identifier carried at the specified position of the URL, or may represent the combination of the information identifier and the amount information carried at the specified position of the URL. The information in the business parameter information other than "CCC" and "VALUE" is information in a specified format, and the application that receives the URL can extract "CCC" and "VALUE" from it based on the recognition of the format information.

[0064] In the URL example, AAA, BBB, CCC and VALUE are only schematic symbols used to indicate the location of the corresponding information. In actual application, AAA, BBB, CCC and VALUE in the URL can be actual strings. For example, in a specific URL example "https: / / ulink.alipay.com / snxxx?s=nfc&scheme=alipay%1A2B3c4d%1A2B3c4dsn%5e6F1q2w3e4r5t6y7u8i", the string "snxxx" corresponds to Figure 3 In the example path "AAA", the string "nfc" corresponds to Figure 3 In the example, the value of the first query parameter s is "BBB", and the string "sn" corresponds to Figure 3 In the example of scene type information "CCC", the string "1q2w3e4r5t6y7u8i" corresponds to Figure 3 The information in the example is identified by "VALUE".

[0065] In addition, in actual application, the domain name ulink.alipay.com, the parameter name s of the first query parameter, the parameter name scheme of the second query parameter, the format information in the business parameter information corresponding to the second query parameter, and the structure of the entire URL can be pre-set information that will not change within a period of time and will not change during different communications, so that the operating system, operating system server, application, application server and other multiple terminals can identify and process the received URL according to the pre-set settings. Of course, the aforementioned agreed information can also be changed during software updates, solution upgrades, etc. For example, the domain name can be changed from ulink.alipay.com to render.alipay.com, and after the change, the operating system, operating system server, application, application server and other multiple terminals that need to consume the information need to be updated synchronously.

[0066] In the embodiments of this specification, the iOS 14 version and above operating system has a light application function that allows users to quickly use applications without downloading and installing complete applications, that is, a light application function that runs on the operating system. Therefore, in order to adapt to the light application function of the iOS 14 version and above operating system, the URL transmitted based on NFC can contain light application card parameters for being identified by the iOS operating system in the form of a light application card, so that after the iOS operating system recognizes the light application card parameters in the URL, it can trigger the light application function in the iOS operating system, and then display the corresponding light application card based on the light application function, so as to improve the success rate of the iOS operating system's call-end.

[0067] Optionally, light app card parameters can be carried in the path information of the URL.

[0068] Step 204: Start the application corresponding to the domain name information; the application is used to execute the business process corresponding to the URL.

[0069] In the embodiment of this specification, the operating system can start the target application based on the acquired URL, if the operating system has installed the target application, so that the started target application executes the corresponding business process based on the query parameter information in the URL. If the operating system does not have the target application installed, the operating system can open the application page corresponding to the URL, so that the user can complete the subsequent business process according to the displayed information of the opened application page.

[0070] It should be understood that the order of some steps in the methods described in one or more embodiments of this specification can be interchanged according to actual needs, or some steps can be omitted or deleted.

[0071] Figure 2 According to the method, the URL transmitted based on NFC can be recognized by the iOS operating system in addition to being recognized by the Android system and the Hongmeng system. In this way, in the scenario of calling the terminal based on NFC, the device of the iOS operating system can also be successfully called. Thus, while greatly improving the call success rate of the device of the iOS operating system, it can also improve the overall call success rate of the devices of the user group.

[0072] based on Figure 2 The method, the embodiments of this specification also provide some specific implementation methods of the method, which are described below.

[0073] In the embodiments of this specification, one or more embodiments are proposed for the process of the operating system calling the terminal based on the URL.

[0074] Optionally, launching the application corresponding to the domain name information in the embodiments of this specification may specifically include: determining the application corresponding to the URL based on the domain name information; determining whether the application has been installed in the operating system to obtain a determination result; if the determination result indicates that the application has been installed in the operating system, launching the application.

[0075] In the embodiments of this specification, the domain name information may be information designed by the developer of the application program to determine the corresponding application, and the domain name information corresponding to the application may be pre-registered on the World Wide Web, so the corresponding application may be determined based on the domain name information.

[0076] In the embodiment of this specification, after the operating system obtains the URL sent by the NFC tag device, it can determine the target application corresponding to the URL based on the domain name information in the URL. The operating system determines whether the target application is already installed on the operating system based on the determined target application and the various applications already installed on the operating system. If it is determined that the operating system has already installed the target application, the target application is started.

[0077] Optionally, taking Alipay as the target application, for the payment scenario, the page after the target application is enabled can be as follows Figure 4 shown. Figure 4 The information shown is only an example. Figure 4 Different information in the text box can be displayed, including other text, pictures, animated pictures, controls, etc. Figure 4 The information displayed is not specifically limited.

[0078] In the embodiment of this specification, if it is determined that the target application is not installed in the operating system, the operating system may display the corresponding page corresponding to the URL. Optionally, the determination of whether the application is installed in the operating system, after obtaining the determination result, may also include: if the determination result indicates that the application is not installed in the operating system, obtaining first preset page information corresponding to the URL from the application server of the application based on the URL; displaying a first preset page generated based on the first preset page information; the first preset page includes a first download control for prompting the user to download the application.

[0079] In the embodiments of this specification, the URL obtained by the operating system may be a resource address for identifying and locating resources. Therefore, when it is determined that the target application is not installed in the operating system, the first preset page information corresponding to the URL may be obtained from the server of the target application based on the URL, and the corresponding first preset page may be generated based on the first preset page information. The first preset page information includes all information for generating the first preset page, such as but not limited to picture information, title information, subtitle information, control information, etc. The first preset page may include a first download control, and after the user performs a trigger operation on the first download control, the download and installation process for the target application may be triggered.

[0080] Optionally, taking Alipay as an example, the first preset page generated may be as follows: Figure 5 shown. Figure 5 In the example, the first download control 10 is a "download Alipay" control. Figure 5 The information shown is only an example. Figure 5 Different information in the text box can be displayed, including other text, pictures, animated pictures, controls, etc. Figure 5 The information displayed is not specifically limited.

[0081] In an embodiment of the present specification, after determining that the target application has been installed in the operating system, the target application can be directly started to improve the user experience; when determining that the target application is not installed in the operating system, a first preset page for prompting the user to download the target application can be displayed to the user to increase user usage of the target application.

[0082] In order to improve the user experience, after the operating system obtains the URL of the NFC tag device based on NFC, it can pre-generate prompt information to prompt the user whether he needs to access the target application, so that the target application can be started only after obtaining the user's authorization, so as to avoid disturbing the user when the user does not need to open the target application.

[0083] Optionally, before determining whether the application has been installed in the operating system, the process may further include: displaying a banner page element; wherein the banner page element includes information for prompting access to the application; and obtaining a first trigger operation of the user for the banner page element.

[0084] The determining whether the application has been installed in the operating system may specifically include: in response to the first triggering operation, determining whether the application has been installed in the operating system.

[0085] In the embodiments of this specification, after the operating system determines the target application based on the domain name information in the URL, it can display a banner page element in the current interface running the operating system, and the banner page element can include prompt information for prompting the user whether to access the application. The banner page element can be displayed in any of the top area, bottom area, and middle area in the visible area of ​​the current interface, or the banner page element can also be displayed in any area in the visible area of ​​the current interface, and there is no specific limitation on the display position of the banner page element.

[0086] Optionally, taking Alipay as an example, the display page containing the banner page element can be as follows: Figure 6 As shown, Figure 6 In the example, the banner page element 20 is located in the top area of ​​the visible area. Figure 6 The information shown is only an example. Figure 6 Different information in the text box can be displayed, including other text, pictures, animated pictures, controls, etc. Figure 6 The information displayed is not specifically limited.

[0087] In the embodiment of the present specification, if the operating system obtains the user's first trigger operation on the banner page element within the preset time, the first trigger operation may be a user's click operation on a preset control in the banner page element, or may also be a user's click operation on any position of the banner page element. In response to the user's first trigger operation, a judgment process is performed on whether the target application has been installed in the operating system. If it is judged that the target application has been installed in the operating system, the target application is started; if it is judged that the target application is not installed in the operating system, a target page for prompting the user to download the target application is displayed.

[0088] In the embodiment of the present specification, if the operating system does not obtain the first triggering operation of the user on the banner page element within a preset time, the banner page element stops being displayed.

[0089] Based on the above embodiments, in an embodiment of the present specification, the operating system may include an IOS operating system with a light application function; before determining whether the application has been installed in the operating system, it may also include: obtaining light application card information corresponding to the light application card parameters according to the light application card parameters; displaying a light application card generated based on the light application card information; the light application card includes an application access control; the application access control is used to prompt the user to access the application; and obtaining a second trigger operation for the application access control.

[0090] The determining whether the application has been installed in the operating system may specifically include:

[0091] In response to the second triggering operation, it is determined whether the application has been installed in the operating system.

[0092] In the embodiments of this specification, the operating system may include an iOS operating system with a light application function, specifically an iOS version 14 or higher. Light applications may be applications that can be used without downloading and run in the operating system. For example, app clips running on the iOS operating system.

[0093] In the embodiments of the present specification, the obtaining of the light app card information corresponding to the light app card parameters according to the light app card parameters may specifically include: based on the light app card parameters, obtaining the light app card information corresponding to the light app card parameters from the system server corresponding to the operating system. The light app card information may include picture information, title information, subtitle information, and control information, etc. Different business scenarios may correspond to different light app card parameters, and the light app card information corresponding to each light app card parameter may be different. For example: the light app card parameters corresponding to the payment scenario are different from the light app card parameters corresponding to the gate opening scenario; the light app card parameters corresponding to the payment scenario are also different from the light app card parameters corresponding to the service machine water selling business scenario.

[0094] In the embodiments of this specification, the light application card information can be information pre-registered at the system server corresponding to the operating system by the developer of the application corresponding to the light application card information. For example, for the payment scenario of the target application, if the developer wants to display a picture of interface A when displaying the payment scenario of the target application, the developer can pre-register the relevant information of the picture of interface A at the system server corresponding to the operating system to inform the system server to display the picture of interface A when displaying the payment scenario of the target application. At the same time, the developer will also add the parameters of the relevant information about the display of the payment scenario of the target application with the picture of interface A to the corresponding URL, so that after the operating system obtains the URL, it can parse the light application card parameters for interface A, and obtain the corresponding light application card information from the system server based on the light application card parameters, and then generate a light application card based on the light application card information, and display the light application card to the user. The light application card can include the title of the target application and the application access control corresponding to the target application. The user can access the corresponding target application through the application access control.

[0095] Optionally, taking Alipay as the target application, for payment scenarios, the generated light application card can be as follows Figure 7 shown. Figure 7 , the application access control 30 is an "open" control. Figure 7The information shown is only an example. Figure 7 Different information in the text box can be displayed, including other text, pictures, animated pictures, controls, etc. Figure 7 The information displayed is not specifically limited.

[0096] In an embodiment of the present specification, if within a preset time, the operating system obtains a second trigger operation of the user for the application access control, in response to the second trigger operation, a judgment process is performed as to whether the target application has been installed in the operating system. If it is determined that the target application has been installed in the operating system, the target application is started.

[0097] In the embodiment of the present specification, if the operating system does not obtain the second trigger operation of the user on the application access control within the preset time, the light application card is stopped from being displayed.

[0098] Optionally, the URL may also include light application page parameters. After determining whether the application has been installed in the operating system, the process may also include: if the determination result indicates that the application is not installed in the operating system, obtaining light application page information corresponding to the light application page parameters according to the light application page parameters; displaying a light application page generated based on the light application page information in the light application corresponding to the light application card; and including a second download control in the light application page for prompting the user to download the application.

[0099] In the embodiment of this specification, the light application page parameters can be carried in the query parameter information of the URL, specifically, Figure 3 As shown, the light application page parameter may be the parameter value corresponding to the first query parameter in the URL, for example, the parameter value corresponding to parameter s.

[0100] In the embodiment of the present specification, in response to the second trigger operation, a judgment process is performed on whether the target application has been installed in the operating system. If it is judged that the target application is not installed in the operating system, the light application page information corresponding to the light application page parameter is obtained according to the light application page parameter. Specifically, based on the light application page parameter, the light application page information corresponding to the light application page parameter is obtained from the system server corresponding to the operating system. The light application page information may include picture information, title information, subtitle information, and control information.

[0101] In the embodiment of the present specification, the light application page information may be information pre-registered by a developer of the application corresponding to the light application page information at a system server corresponding to the operating system.

[0102] In the embodiment of this specification, the operating system can generate a corresponding light application page based on the obtained light application page information, and display the light application page in the light application corresponding to the light application card. The light application page includes a second download control for prompting the user to download the target application. After the user clicks the second download control, the download and installation process for the target application can be triggered.

[0103] Optionally, taking Alipay as the target application, the generated light application page can be as follows: Figure 8 As shown, Figure 8 The second download control 40 in is a "download" control. Figure 8 The information shown is only an example. Figure 8 Different information in the text box can be displayed, including other text, pictures, animated pictures, controls, etc. Figure 8 The information displayed is not specifically limited.

[0104] Based on the above embodiment, in the embodiment of the present specification, the light application page may also include a business control for indicating the execution of a business process; after displaying the light application page generated based on the light application page information, it may also include: obtaining a third trigger operation of the user on the business control; in response to the third trigger operation, highlighting the second download control.

[0105] In the embodiments of this specification, the business control may be a control for prompting the user to make a payment, or may be a control for prompting the user to experience the target application. After obtaining the third trigger operation of the user on the business control, in response to the third trigger operation, the second download control is highlighted to guide the user to download and install the target application through the second download control. This improves the convenience of the user downloading and installing the target application, thereby increasing the user usage of the target application.

[0106] In the embodiments of this specification, one or more embodiments are also proposed for the process of executing services based on URLs by target applications.

[0107] Optionally, after starting the application corresponding to the domain name information, it may also include: transmitting the URL to the application; the URL may also include business parameter information; the business parameter information is used as a basis for the application to execute the business process corresponding to the URL.

[0108] In the embodiment of this specification, the service parameter information may be carried in the query parameter information of the URL.

[0109] Optional, such as Figure 3As shown, the business parameter information may be a parameter value corresponding to the second query parameter in the URL, for example, a parameter value corresponding to the scheme parameter.

[0110] In the embodiment of this specification, after the operating system determines that the target application has been installed and started, the operating system will send the URL to the target application, and the target application will execute subsequent business processes based on the business parameter information in the URL.

[0111] On the basis of the above-mentioned embodiment, in the embodiment of this specification, the service parameter information may include scenario type information and an information identifier corresponding to the scenario type information; the information identifier is used as a basis for querying the service description information.

[0112] After transmitting the URL to the application, the method may further include:

[0113] The application queries a URL template that has a mapping relationship with the scene type information based on the scene type information; the URL template contains a replaceable tag; the replaceable tag is used to identify the location where the information identifier can be entered; the information identifier is used to replace the replaceable tag to obtain a business URL carrying the information identifier; and a business process is executed based on the business URL.

[0114] In the embodiments of this specification, the scene type information is used to reflect the specific implementation scenario when the business is executed. The business scenario may include a payment scenario, a gate opening scenario, a meal ordering scenario, and a water vending machine scenario. Optionally, the information identifier may be identification data generated based on the business data generated when the business is executed, such as identification data generated based on an order number or a merchant number. The information identifier may be encrypted identification data, and such a setting may enhance the security of the business data. Alternatively, the information identifier may be a random string. In the application server, the generated information identifier and the business description information corresponding to the information identifier may be stored accordingly, so that when the business description information is needed later, it can be queried based on the information identifier.

[0115] In the embodiments of this specification, a mapping relationship may be pre-established between the scene type information and the URL template, and specifically, a mapping relationship in the form of a key-value pair may be established, wherein the scene type information may be a key value, and the URL template may be a value value.

[0116] In order to facilitate those skilled in the art to understand the present solution, a specific example of converting a URL to a business URL is proposed in the embodiments of this specification.

[0117] Assume that the URL obtained by the operating system from the NFC tag device is as follows:

[0118] https: / / ulink.alipay.com / snxxx?s=nfc&scheme=alipay%1A2B3c4d%1A2B3c4dsn%5e6F1q2w3e4r5t6y7u8i.

[0119] The business parameter information in the URL is the parameter value corresponding to the parameter scheme; the scene type information is "sn" in the parameter value corresponding to the parameter scheme; and the information identifier is "1q2w3e4r5t6y7u8i" in the parameter value corresponding to the parameter scheme.

[0120] Based on the pre-established mapping relationship between the scene type information and the URL template, the URL template corresponding to "sn" is queried as follows:

[0121] alipays: / / platformapi / startApp?appId=112233&appScheme=NFC_ABC&pageParams=%12345qwert$[value]$%6789. The replaceable token in the URL template is $[value]$.

[0122] Use the information identifier "1q2w3e4r5t6y7u8i" in the URL to replace the replaceable tag $[value]$ in the URL template. The resulting business URL is as follows:

[0123] alipays: / / platformapi / startApp? appId=112233&appScheme=NFC_ABC&pageParams=%12345qwert1q2w3e4r5t6y7u8i%6789.

[0124] In the embodiments of this specification, a business URL for executing a business process can be generated based on the URL transmitted between the user terminal device and the NFC tag device, thereby eliminating the need to transmit the business URL for executing the business process between the user terminal device and the NFC tag device. This configuration can, on the one hand, avoid the risk of leakage of the business URL and improve the confidentiality of the business URL; on the other hand, since the data volume of the URL is smaller than the data volume of the business URL, the data transmission volume between the user terminal device and the NFC tag device can also be reduced, thereby improving the communication efficiency of NFC and thus improving the user experience.

[0125] Based on the above embodiments, in an embodiment of the present specification, the business URL contains rendering parameter information for rendering the first application page; the information identifier is carried in the rendering parameter information; and executing the business process based on the business URL may specifically include: rendering the first application page based on the rendering parameter information.

[0126] In the embodiment of this specification, taking the payment scenario as an example, it is assumed that the converted business URL is as follows:

[0127] alipays: / / platformapi / startApp?appId=112233&appScheme=NFC_ABC&pageParams=%12345qwert$1q2w3e4r5t6y7u8i$%6789. The three parameters appid, appscheme, and pageparams in the converted business URL are all rendering parameters, and the corresponding parameter values ​​are all rendering parameter information.

[0128] In actual applications, the first application page can be rendered based on the rendering parameter information in the business URL. The first application page can be the call-end landing page displayed to the user after the business process is initiated based on NFC, and can also be called the first page displayed to the user.

[0129] Based on the above embodiments, in an embodiment of the present specification, the first application page may include a preset control; after rendering the first application page based on the rendering parameter information, it may also include: in response to a user triggering operation on the preset control, sending a service request to an application server of the application; carrying the information identifier in the service request; receiving business processing result information determined by the application server in response to the business request; the business processing result information is determined by the application server according to the business description information; the business description information is obtained by the application server by querying the information identifier; and displaying a second application page generated based on the business processing result information.

[0130] Optionally, the information identifier carried in the service URL may be information generated by an application server.

[0131] Optionally, the information identifier may be a token obtained by the application server after processing at least part of the information in the service description information according to a preset information processing rule.

[0132] Optionally, the information identifier may be a random character string generated by the application server.

[0133] In actual application, after the information identifier is generated, the information identifier and the corresponding service description information may be associated and stored, and the information identifier may be used as a query index for the service description information.

[0134] Optionally, the NFC tag device may send a URL acquisition request to an application server, and then the application server generates a URL and returns it to the NFC tag device.

[0135] In an embodiment of the present specification, the first application page may include preset controls, wherein the preset controls may be any one of input controls, button controls, selection controls, and multimedia controls. If within a preset time, the target application obtains a trigger operation of the user on the preset control, the target application responds to the trigger operation and sends a service request to the application server of the target application, wherein the service request carries the information identifier. The application server responds to the service request, parses the service request, obtains the information identifier carried in the service request, and then uses the information identifier as a query index to query the service description information corresponding to the information identifier, and then determines the corresponding service processing result information based on the service description information, and sends the service processing result information to the target application. After receiving the service processing result information, the target application generates a corresponding second application page and displays the second application page.

[0136] In the embodiments of the present specification, the application server may perform multiple interactive processes with the target application in the process of determining the business processing result information, such as the process of decrypting the information identifier in the business URL, the process of verifying the identity information of the user using the target application, the process of verifying the legitimacy of the business URL, the process of verifying the security of the business execution environment, and obtaining relevant information that needs to be displayed in the second application page.

[0137] In the embodiment of the present specification, the second application page generated based on the business processing result information may include multiple types of pages. Taking the payment scenario as an example, the second application page may be an application page that displays relevant information such as successful payment. The second application page may also be an application page that displays relevant information such as a specific payment amount. If the user has enabled the password-free payment function, the user can directly click the payment button in the second application page to complete the payment; if the user has not enabled the password-free payment function, after the user clicks the payment button in the second application page, the second application page may jump to the third application page, and the user completes the payment after entering the correct password in the third application page. The second application page may also be an application page that displays a corresponding window in which the user needs to enter the payment amount. If the user has enabled the password-free payment function, after the user enters the corresponding payment amount in the second application page, the user can directly click the corresponding payment button to complete the payment; if the user has not enabled the password-free payment function, the user enters the corresponding payment amount in the second application page, and after clicking the payment button corresponding to the payment amount, the second application page may jump to the fourth application page, and the user completes the payment after entering the correct password in the fourth application page.

[0138] Optionally, in a payment scenario, the business parameter information also includes amount information corresponding to the scenario type information; the amount information and the information identifier can be concatenated and carried in the rendering parameter information; the first application page can also include the payment amount corresponding to the amount information.

[0139] Specifically, when the business parameter information includes both the information identifier and the amount information, the information identifier and the amount information can be concatenated with a fixed character (for example, _), and then in the subsequent URL conversion process, the amount information and the information identifier can be simultaneously filled into the business URL obtained after the conversion.

[0140] In the embodiments of this specification, in the payment business scenario, the merchant can input the payment amount to obtain the business parameter carrying the amount information, and generate the corresponding information identifier based on the payment amount, so that the rendering parameter information in the business URL can carry the payment amount. The first application page rendered based on the rendering parameter information can include the payment amount entered by the merchant. If the user has enabled the password-free payment function, the user can directly click the payment button in the first application page to complete the payment; if the user has not enabled the password-free payment function, after the user clicks the payment button in the first application page, the first application page can jump to the fifth application page, and the user completes the payment after entering the correct password in the fifth application page.

[0141] It should be noted that, in the embodiments of the present specification, the amount information is carried in the business parameter information in plain text, and then carried in the business URL, so that when the user terminal device obtains the business URL, the payment amount corresponding to the amount information can be displayed in the rendered first application page based on the plain text amount information in the business URL. In other words, the user can see the amount to be paid in the call-end landing page, thereby improving the user's payment experience. Optionally, when the amount information carries the payment amount, the payment amount can be displayed in the first application page. Optionally, when the amount information does not carry the payment amount, for example, only carries a character used to indicate that the payment amount is not provided (for example, n), the payment amount is not displayed in the first application page.

[0142] In order to facilitate those skilled in the art to understand the present solution, the embodiments of this specification propose a specific example of converting a URL to a business URL when carrying amount information.

[0143] Assume that the URL obtained by the operating system from the NFC tag device is as follows:

[0144] https: / / ulink.alipay.com / snxxx?s=nfc&scheme=alipay%1A2B3c4d%1A2B3c4dsn%5e6F1q2w3e4r5t6y7u8i_0.1.

[0145] The business parameter information in the URL is the parameter value corresponding to the parameter scheme; the scenario type information is "sn" in the parameter value corresponding to the parameter scheme; the information identifier and amount information are "1q2w3e4r5t6y7u8i_0.1" in the parameter value corresponding to the parameter scheme.

[0146] Based on the pre-established mapping relationship between the scene type information and the URL template, the URL template corresponding to "sn" is queried as follows:

[0147] alipays: / / platformapi / startApp?appId=112233&appScheme=NFC_ABC&pageParams=%12345qwert$[value]$%6789. The replaceable token in the URL template is $[value]$.

[0148] Use the information identifier and amount information "1q2w3e4r5t6y7u8i_0.1" in the URL to replace the replaceable token $[value]$ in the URL template. The resulting business URL is as follows:

[0149] alipays: / / platformapi / startApp? appId=112233&appScheme=NFC_ABC&pageParams=%12345qwert1q2w3e4r5t6y7u8i_0.1%6789.

[0150] In this example, the amount to be paid, "0.1", can be displayed to the user in the first application page that is landed on the calling end.

[0151] On the basis of the above-mentioned embodiment, in the embodiment of this specification, when querying the URL template based on the scene type information, there may still be a situation where the query fails.

[0152] Optionally, after the application queries a URL template having a mapping relationship with the scene type information according to the scene type information, it may also include: if no URL template having a mapping relationship with the scene type information is found, obtaining the home page URL of the application; and displaying the home page of the application based on the home page URL.

[0153] In the embodiments of this specification, the homepage URL of the application can be pre-stored at the application client. If the URL template with a mapping relationship is not found based on the scenario type information in the business URL, the application can directly display the homepage of the application based on the homepage URL pre-stored at the client. This setting can increase the rate of displaying the homepage of the application. If the homepage URL is not pre-stored at the application client, when the URL template with a mapping relationship is not found, the application can generate a request to obtain the homepage URL and send it to the application server. The application server responds to the request and sends the homepage URL to the application client. The application displays the homepage of the application based on the received homepage URL. This setting can reduce the occupancy rate of storage resources at the application client.

[0154] In the embodiments of the present specification, when the application cannot parse out specific business information or cannot parse out the application page required to be displayed, the homepage of the application can be displayed to the user to reduce the user's bad experience with the application.

[0155] Optionally, when the scenario represented by the scenario type information is a designated business scenario, the application can access the page corresponding to the designated business URL. Based on this, the business parameter information can include the scenario type information and the designated business URL corresponding to the scenario type information; after transmitting the URL to the application, it can also include: when the value of the scenario type information is a designated parameter, the application obtains the designated page information corresponding to the designated business URL from the designated server corresponding to the designated business URL based on the designated business URL; and displays the designated page generated based on the designated page information.

[0156] In the embodiment of this specification, the service parameter information in the URL obtained by the operating system from the NFC tag device may include the scene type information and the designated service URL corresponding to the scene type information. After the target application obtains the URL, if it is determined that the scene type information in the service parameter information is a designated parameter, it does not need to query the URL module that has a mapping relationship with the scene type information, and can display the designated page determined based on the designated service URL.

[0157] In the embodiments of this specification, the application corresponding to the designated business URL is different from the target application, and the server corresponding to the designated business URL is different from the server of the target application. Taking the payment scenario as an example, the target application may be Alipay, and the application corresponding to the designated business URL may be other mini-program applications. The designated page displayed may be other mini-program pages opened in the Alipay application page, rather than the native page of Alipay. The server corresponding to the designated business URL may be a server on the merchant side or other third-party side. The designated business URL may be a URL specified by the merchant, and its protocol type may be any one of http, https, alipay, and alipays.

[0158] In the embodiments of this specification, based on user needs, designated pages of other applications can be opened within the target application, so that the user can have more independent choices to improve the user experience for the target application.

[0159] Optionally, the application includes a payment application, and the business process includes a payment process.

[0160] Based on Figure 2 With the same idea as the solution shown in , the embodiment of this specification also provides another service execution method based on NFC. Fig. 9 The following is a flowchart of another NFC-based service execution method provided in the embodiments of this specification. From a software perspective, the execution subject of the process can be a program or application client installed on an NFC tag device. From a hardware perspective, the execution subject of the process can be an NFC tag device. Fig. 9 As shown, the process may include:

[0161] Step 902: Receive a near field communication signal transmitted by a user terminal device.

[0162] In the embodiments of this specification, the user terminal device can be used as an NFC card reader. When the user terminal device is close to the NFC tag device, it will send a request to the NFC tag device by sending a near field communication signal. The request is used to request the NFC tag device to obtain a URL.

[0163] Step 904: In response to the near field communication signal, a uniform resource locator URL is sent to the user terminal device via near field communication; the URL includes protocol type information, domain name information and light application card parameters; the protocol type information indicates that the URL complies with the Hypertext Transfer Protocol Security Protocol; the light application card parameters are used to be identified by the IOS operating system in the form of a light application card; the domain name information is used by the user terminal device to start the application corresponding to the domain name information; the application is used to execute the business process corresponding to the URL.

[0164] In the embodiment of this specification, the NFC tag device sends the URL to the user terminal device in a near field communication manner based on the received near field communication signal and in response to the near field communication signal. The URL may include protocol type information, domain name information, port information, path information, query parameter information, etc. The protocol in the URL may be HyperText Transfer Protocol (HTTP) or HyperText Transfer Protocol Secure (HTTPS). The domain name information is used to determine the target application corresponding to the URL. After the target application is started, the business process corresponding to the URL can be executed based on the URL.

[0165] In the embodiments of this specification, the iOS 14 version and above operating system has a light application function that allows users to quickly use applications without downloading and installing complete applications, that is, a light application function that runs on the operating system. Therefore, in order to adapt to the light application function of the iOS 14 version and above operating system, the URL transmitted based on NFC can contain light application card parameters for being identified by the iOS operating system in the form of a light application card, so that after the iOS operating system recognizes the light application card parameters in the URL, it can trigger the light application function in the iOS operating system, and then display the corresponding light application card based on the light application function, so as to improve the success rate of the iOS operating system's call-end.

[0166] Optionally, light app card parameters can be carried in the path information of the URL.

[0167] In the embodiments of this specification, the method of obtaining the URL in the NFC tag device may be different for different application scenarios. For example, in some vending scenarios, the URL can usually carry fixed information, so the URL containing fixed information can be pre-burned into the NFC tag device. For another example, in some scenarios, the URL can carry business data related to the current business, such as: product order number, user ID, order amount and other information, so the corresponding URL can be generated in real time when the business occurs.

[0168] Fig. 9 According to the method, the URL transmitted based on NFC can be recognized by the iOS operating system in addition to being recognized by the Android system and the Hongmeng system. In this way, in the scenario of calling the terminal based on NFC, the device of the iOS operating system can also be successfully called. Thus, while greatly improving the call success rate of the device of the iOS operating system, it can also improve the overall call success rate of the devices of the user group.

[0169] based on Fig. 9 The method in this specification also provides some specific implementation plans of the method, which are described below.

[0170] Optionally, before receiving the near-field communication signal transmitted by the user terminal device, it may also include: obtaining a preset trigger operation; obtaining first business information in response to the trigger operation; sending a URL acquisition request to an application server; the URL acquisition request carries the first business information; receiving the URL returned by the application server; the 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 URL obtained by the application server.

[0171] In the embodiments of this specification, the preset trigger operations may be different for different business scenarios, such as the cashier-initiated payment operation, the service machine-initiated payment operation after selling water, the shopper-initiated payment operation after selecting items at the vending machine, and the user-initiated payment operation after shopping on the merchant's corresponding application.

[0172] In the embodiments of this specification, taking the payment scenario as an example, the first business information may include information such as the product order number, merchant ID, order generation time, and order generation location. The second business information may include information such as the generation time of the URL, specific attributes of the URL, the validity period of the URL, the ID of the paying user, and the user's payment status.

[0173] In the embodiment of this specification, the information identifier may be a token generated by the application server according to the service description information.

[0174] Optionally, the application server may process at least part of the information in the business description information according to preset information processing rules to obtain a token. The preset information processing rules may vary depending on the scenario. For example, in a payment scenario, the merchant number or order number may be processed to obtain a token. In a service machine water sales scenario, the serial number (SN) and the process identifier (PID) may be concatenated to obtain a token. In a container sales scenario, the container number and the product identification may be processed to obtain a token.

[0175] Optionally, the information identifier corresponding to the service description information may be a random code generated by the server.

[0176] In the embodiments of this specification, the application server can associate and store information identifiers with business description information, so that when the application sends a business request to the application server based on the URL, the application server can query the business description information including the business information based on the information identifier, thereby advancing the business process. This setting can improve the security of business information, make the URL shorter, and reduce the amount of data transmitted in the URL.

[0177] It should be noted that, for a certain NFC tag device, the information identifier in the URL to be generated can change. If the URL to be generated also contains amount information, the amount information can also change. Other than that, other information can be fixed. Specifically, the protocol type information, domain name information, light application card parameters, light application page parameters, scene type information and other information in the URL to be generated can remain unchanged. Moreover, when the URL to be generated contains a specified business URL, the specified business URL can also remain unchanged. In the URL sent for each near-field communication performed by the NFC tag device, only the information identifier and the amount information (if any) may be different in the URLs sent at different times.

[0178] Optionally, the triggering operation may include initiating a payment collection operation, the application may include a payment application, and the business process may include a payment process.

[0179] In the embodiments of this specification, for payment business scenarios, based on the NFC communication method between the user terminal device and the NFC tag device, payment can be completed by a tap-to-pay operation between devices. This is convenient for people with disabilities who use smartphones, such as the elderly, to complete payment smoothly without having to operate the smartphone, for example: without the user opening a scanning device to scan the merchant's QR code, making payment more convenient for users, thereby improving the user experience during the payment process and thereby improving the user's stickiness to the target application.

[0180] The embodiments of this specification also provide corresponding Figure 2 and Fig. 9 A swim lane flow diagram of the NFC-based business execution method in FIG.

[0181] like Fig.10 As shown, for the Android operating system or the Hongmeng operating system, the NFC-based business execution process may involve execution entities such as the terminal device operating system, target application, and target application server.

[0182] In the embodiment of this specification, the terminal device operating system obtains the URL through NFC near-field communication, determines the target application corresponding to the URL according to the domain name information in the URL, and determines whether the target application has been installed in the operating system. If it is determined that the target application is not installed in the operating system, the browser provided by the operating system is used to open the application download page corresponding to the URL, wherein a download request control is displayed in the application download page, and after obtaining the user's trigger operation on the download request control, the target application is downloaded. If it is determined that the target application has been installed in the operating system, the target application is invoked and a URL is sent to the target application, wherein the URL contains business parameter information, and the business parameter information contains scene type information and an information identifier corresponding to the scene type information.

[0183] After obtaining the URL, the target application generates a mapping relationship table in advance by querying according to the scene type information in the URL, queries the URL template that has a mapping relationship with the scene type information, and uses the information identifier corresponding to the scene type information to replace the replaceable mark in the queried URL template to obtain the business URL. Based on the rendering parameter information in the business URL, the first application page (call-end landing page) is generated, wherein the first application page contains a preset control. After obtaining the user's trigger operation on the preset control, the target application will send a business request carrying the information identifier to the application server.

[0184] After receiving the business request sent by the target application, the target application server will query and obtain the business description information corresponding to the information identifier based on the parsing operation of the information identifier carried in the business request, and then determine the business processing result information based on the business description information, and send the business processing result information to the target application, so that the target application displays the second application page based on the business processing result information.

[0185] It should be noted that for some other operating systems, such as IOS13 and below, after the terminal device operating system determines the target application based on the domain name information in the URL, it can also display pop-up information to prompt the user whether to open the target application. Only after obtaining the user's trigger operation for the pop-up information will it execute the operation to determine whether the target application has been installed in the operating system.

[0186] like Fig.11 As shown, for operating systems of IOS14 and above, the NFC-based business execution process may involve execution entities such as the terminal device operating system, operating system server, target application, and target application server.

[0187] In the embodiment of the present specification, the operating system of the terminal device obtains the URL through NFC near field communication, determines the target application corresponding to the URL according to the domain name information in the URL, and sends the light application card parameters contained in the path information in the URL to the operating system server. The operating system server queries the corresponding light application card information based on the received light application card parameters, wherein the light application card information is the relevant information pre-registered at the operating system server by the developer of the target application. After obtaining the light application card information queried by the operating system server, the operating system generates a light application card based on the light application card information and displays the light application card to the user, wherein the light application card contains a first control, and the first control is used to prompt the user whether to open the target application. If the operating system obtains the user's trigger operation on the first control, the operating system starts the operation of determining whether the target application has been installed in the operating system. If it is determined that the target application is not installed in the operating system, the operating system sends the light application page parameters contained in the query parameter information of the URL to the operating system server, and the operating system server queries the corresponding light application page information based on the received light application page parameters, wherein the light application page information is the relevant information pre-registered at the operating system server by the developer of the target application. After the operating system obtains the light application page information queried by the operating system server, it generates a light application page based on the light application page information and displays the light application page to the user, wherein the light application page includes a second control, and the second control is used to prompt the user whether to download the target application. After obtaining the user's trigger operation on the second control, the target application is downloaded. If it is determined that the target application has been installed in the operating system, the target application is called up and a URL is sent to the target application, wherein the URL includes business parameter information, and the business parameter information includes scene type information and an information identifier corresponding to the scene type information.

[0188] After obtaining the URL, the target application generates a mapping relationship table in advance by querying according to the scene type information in the URL, queries the URL template that has a mapping relationship with the scene type information, and uses the information identifier corresponding to the scene type information to replace the replaceable mark in the queried URL template to obtain the business URL. Based on the rendering parameter information in the business URL, the first application page (call-end landing page) is generated, wherein the first application page contains a preset control. After obtaining the user's trigger operation on the preset control, the target application will send a business request carrying the information identifier to the application server.

[0189] After receiving the business request sent by the target application, the target application server will query and obtain the business description information corresponding to the information identifier based on the parsing operation of the information identifier carried in the business request, and then determine the business processing result information based on the business description information, and send the business processing result information to the target application, so that the target application displays the second application page based on the business processing result information.

[0190] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method. Fig.12 The embodiments of this specification provide corresponding to Figure 2 A schematic diagram of the structure of a service execution device based on NFC. Fig.12 As shown, the device may include:

[0191] The URL acquisition module 1202 is used to obtain the uniform resource locator URL provided by the NFC tag device through near field communication; the URL contains protocol type information, domain name information and light application card parameters; the protocol type information indicates that the URL complies with the Hypertext Transfer Protocol Security Protocol; the light application card parameters are used to be identified by the IOS operating system in the form of a light application card.

[0192] The application startup module 1204 is used to start the application corresponding to the domain name information; the application is used to execute the business process corresponding to the URL.

[0193] based on Fig.12 The present specification also provides some specific implementation schemes of the device, which are described below.

[0194] Optionally, the application starting module 1204 may specifically include:

[0195] An application determining unit is used to determine the application corresponding to the URL according to the domain name information.

[0196] The application determination unit is used to determine whether the application has been installed in the operating system and obtain a determination result.

[0197] An application starting unit is used to start the application if the judgment result indicates that the application has been installed in the operating system.

[0198] Optionally, the application starting module 1204 may further include:

[0199] The first preset page information obtaining unit is configured to obtain first preset page information corresponding to the URL from an application server of the application based on the URL if the judgment result indicates that the application is not installed in the operating system.

[0200] A first preset page display unit is configured to display a first preset page generated based on the first preset page information; the first preset page includes a first download control for prompting a user to download the application.

[0201] Optionally, the application starting module 1204 may further include:

[0202] A page element display unit, used to display a banner page element; the banner page element contains information for prompting access to the application;

[0203] The first triggering operation of the user on the banner page element is obtained.

[0204] Optionally, the application determination unit may specifically include:

[0205] The first application determination subunit is configured to determine, in response to the first trigger operation, whether the application has been installed in the operating system.

[0206] Optionally, the operating system includes an IOS operating system with a light application function. The application startup module 1204 may also include:

[0207] The card information acquisition unit is used to acquire the light application card information corresponding to the light application card parameter according to the light application card parameter.

[0208] A card display unit is used to display a light application card generated based on the light application card information; the light application card includes an application access control; the application access control is used to prompt a user to access the application.

[0209] The trigger operation acquisition unit is used to acquire a second trigger operation for the application access control.

[0210] Optionally, the application determination unit may specifically include:

[0211] The second application determination subunit is configured to determine, in response to the second trigger operation, whether the application has been installed in the operating system.

[0212] Optionally, the URL also includes light application page parameters.

[0213] Optionally, the application starting module 1204 may further include:

[0214] The light application page information acquisition unit is used to acquire the light application page information corresponding to the light application page parameter according to the light application page parameter if the judgment result indicates that the application is not installed in the operating system.

[0215] A light application page display unit is used to display a light application page generated based on the light application page information in the light application corresponding to the light application card; the light application page includes a second download control for prompting the user to download the application.

[0216] Optionally, the light application page also includes a business control for instructing the execution of a business process.

[0217] Optionally, the application starting module 1204 may further include:

[0218] The third trigger operation acquisition unit is used to acquire a third trigger operation of the user on the business control.

[0219] The second download control display unit is used to highlight the second download control in response to the third trigger operation.

[0220] Optionally, the application starting module 1204 may further include:

[0221] A URL transmission unit is used to transmit the URL to the application; the URL also includes business parameter information; the business parameter information is used as a basis for the application to execute the business process corresponding to the URL.

[0222] Optionally, the service parameter information includes scenario type information and an information identifier corresponding to the scenario type information; the information identifier is used as a basis for querying the service description information.

[0223] Optionally, the application starting module 1204 may further include:

[0224] A URL template query unit is used for the application to query a URL template that has a mapping relationship with the scene type information according to the scene type information; the URL template contains a replaceable tag; the replaceable tag is used to identify a location where the information identifier can be entered.

[0225] The replaceable tag replacing unit is used to replace the replaceable tag with the information identifier to obtain a service URL carrying the information identifier.

[0226] The business process execution unit is used to execute the business process based on the business URL.

[0227] Optionally, the business URL includes rendering parameter information for rendering the first application page; the information identifier is carried in the rendering parameter information; and the business process execution unit may specifically include:

[0228] The rendering subunit is used to render the first application page based on the rendering parameter information.

[0229] Optionally, the first application page includes a preset control; and the business process execution unit may further include:

[0230] The service request sending subunit is used to send a service request to the application server of the application in response to the user's triggering operation on the preset control; the service request carries the information identifier.

[0231] The business processing result information receiving subunit is used to receive the business processing result information determined by the application server in response to the business request; the business processing result information is determined by the application server according to the business description information; the business description information is obtained by the application server according to the information identifier query.

[0232] The second application page display subunit is used to display the second application page generated based on the business processing result information.

[0233] Optionally, the business parameter information also includes amount information corresponding to the scene type information; the amount information is concatenated with the information identifier and carried in the rendering parameter information; the first application page also includes the payment amount corresponding to the amount information.

[0234] Optionally, the application starting module 1204 may further include:

[0235] The home page URL acquisition unit is used to acquire the home page URL of the application if no URL template having a mapping relationship with the scene type information is found.

[0236] A home page display unit is used to display the home page of the application based on the home page URL.

[0237] Optionally, the service parameter information includes scene type information and a designated service URL corresponding to the scene type information.

[0238] Optionally, the application starting module 1204 may further include:

[0239] The designated page information acquisition unit is used for, when the value of the scenario type information is a designated parameter, for the application to acquire, based on the designated service URL, designated page information corresponding to the designated service URL from a designated server corresponding to the designated service URL.

[0240] The designated page display unit is used to display the designated page generated based on the designated page information.

[0241] Optionally, the application includes a payment application, and the business process includes a payment process.

[0242] Fig.13 The embodiments of this specification provide corresponding to Fig. 9 A schematic diagram of the structure of a service execution device based on NFC. Fig.13 As shown, the device may include:

[0243] The signal receiving module 1302 is used to receive the near field communication signal transmitted by the user terminal device.

[0244] The information sending module 1304 is used to send a uniform resource locator URL to a user terminal device via near field communication in response to the near field communication signal; the URL includes protocol type information, domain name information and light application card parameters; the protocol type information indicates that the URL complies with the Hypertext Transfer Protocol Security Protocol; the light application card parameters are used to be identified by the IOS operating system in the form of a light application card; the domain name information is used by the user terminal device to start the application corresponding to the domain name information; the application is used to execute the business process corresponding to the URL.

[0245] based on Fig.13 The present specification also provides some specific implementation schemes of the device, which are described below.

[0246] Optional, Fig.13 The device may also include:

[0247] The trigger operation acquisition module is used to obtain the preset trigger operation.

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

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

[0250] A URL receiving module is used to receive the URL returned by the application server; the 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.

[0251] Optionally, the triggering operation includes initiating a payment collection operation, the application includes a payment application, and the business process includes a payment process.

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

[0253] Fig.14 The embodiments of this specification provide corresponding to Figure 2 A schematic diagram of the structure of a user terminal device of a service execution method. Fig.14 As shown, the device 1400 may include:

[0254] At least one processor 1410; and a memory 1430 communicatively connected to the at least one processor; wherein,

[0255] The memory 1430 stores instructions 1420 executable by the at least one processor 1410. The instructions are executed by the at least one processor 1410 to enable the at least one processor 1410 to:

[0256] The uniform resource locator URL provided by the NFC tag device is obtained through near field communication; the URL contains protocol type information, domain name information and light application card parameters; the protocol type information indicates that the URL complies with the Hypertext Transfer Protocol Security Protocol; the light application card parameters are used to be identified by the IOS operating system in the form of a light application card.

[0257] Start an application corresponding to the domain name information; the application is used to execute the business process corresponding to the URL.

[0258] Fig.15 The embodiments of this specification provide corresponding to Fig. 9 A schematic diagram of the structure of an NFC tag device for a service execution method. Fig.15 As shown, the device 1500 may include:

[0259] At least one processor 1510; and a memory 1530 communicatively connected to the at least one processor; wherein,

[0260] The memory 1530 stores instructions 1520 executable by the at least one processor 1510. The instructions are executed by the at least one processor 1510 to enable the at least one processor 1510 to:

[0261] Receive near field communication signals transmitted by user terminal equipment.

[0262] In response to the near field communication signal, a uniform resource locator URL is sent to the user terminal device via near field communication; the URL includes protocol type information, domain name information and light application card parameters; the protocol type information indicates that the URL complies with the Hypertext Transfer Protocol Security Protocol; the light application card parameters are used to be identified by the IOS operating system in the form of a light application card; the domain name information is used by the user terminal device to start the application corresponding to the domain name information; the application is used to execute the business process corresponding to the URL.

[0263] The above is a description of a specific embodiment of the present 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.

[0264] 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. Fig.14 and Fig.15 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0277] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt 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.) that contain computer-usable program code.

[0278] The present application 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. The present application 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.

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

Claims

1. A service execution method based on NFC, applied to a user terminal device, comprising: The operating system obtains the uniform resource locator URL provided by the NFC tag device through near field communication; The URL includes domain name information and light app card parameters; Displaying the light app card to the user according to the light app card parameters; In response to a triggering operation of the user on the light application card, starting an application corresponding to the domain name information; The application is used to execute the payment process corresponding to the URL.

2. The method according to claim 1, wherein displaying the light app card to the user according to the light app card parameters specifically comprises: According to the light application card parameter, acquiring light application card information corresponding to the light application card parameter; Based on the light application card information, generate a light application card; The light app card is displayed to the user.

3. The method according to claim 2, wherein the light application card includes an application access control; the application access control is used to prompt the user to access the application; The step of starting the application corresponding to the domain name information in response to the user's triggering operation on the light application card specifically includes: In response to a second trigger operation on the application access control, an application corresponding to the domain name information is started.

4. The method according to claim 1, wherein in response to the user triggering the light application card, starting the application corresponding to the domain name information specifically comprises: Determine the application corresponding to the URL according to the domain name information; Determine whether the application has been installed in the operating system, and obtain a determination result; If the judgment result indicates that the application has been installed in the operating system, in response to the user's triggering operation on the light application card, the application corresponding to the domain name information is started.

5. The method according to claim 4, wherein after determining whether the application has been installed in the operating system, the step further comprises: If the judgment result indicates that the application is not installed in the operating system, obtaining first preset page information corresponding to the URL from an application server of the application based on the URL; Displaying a first preset page generated based on the first preset page information; The first preset page includes a first download control for prompting the user to download the application.

6. The method according to claim 5, wherein the URL further includes a light application page parameter; and obtaining the first preset page information corresponding to the URL from the application server of the application based on the URL specifically comprises: According to the light application page parameter, acquiring light application page information corresponding to the light application page parameter; The displaying of the first preset page generated based on the first preset page information specifically includes: In the light app corresponding to the light app card, displaying a light app page generated based on the light app page information; The light application page includes a second download control for prompting the user to download the application.

7. The method according to claim 6, wherein the light application page further comprises a business control for indicating the execution of a business process; After displaying the light application page generated based on the light application page information, the method further includes: Acquire a third trigger operation of the user on the service control; In response to the third trigger operation, the second download control is highlighted.

8. The method as claimed in claim 1, wherein the operating system includes an operating system of IOS14 version and above.

9. The method according to claim 1, after starting the application corresponding to the domain name information, further comprising: transmitting the URL to the application; The URL also includes business parameter information; The business parameter information is used as a basis for the application to execute the business process corresponding to the URL.

10. The method according to claim 9, wherein the service parameter information includes scene type information and an information identifier corresponding to the scene type information; The information identifier is used as a basis for querying the service description information; after transmitting the URL to the application, the method further includes: The application searches for a URL template having a mapping relationship with the scene type information according to the scene type information; the URL template includes a replaceable tag; the replaceable tag is used to identify a location where the information identifier can be input; Using the information identifier to replace the replaceable tag, to obtain a service URL carrying the information identifier; The business process is executed based on the business URL.

11. The method according to claim 10, wherein the service URL includes rendering parameter information for rendering the first application page; the information identifier is carried in the rendering parameter information; and the executing the service process based on the service URL specifically comprises: Based on the rendering parameter information, render the first application page.

12. The method of claim 11, wherein: The first application page includes a preset control; after rendering the first application page based on the rendering parameter information, the method further includes: In response to a user triggering operation on the preset control, sending a service request to an application server of the application; the service request carries the information identifier; Receiving service processing result information determined by the application server in response to the service request; the service processing 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; A second application page generated based on the business processing result information is displayed.

13. According to the method as claimed in claim 11, the business parameter information also includes amount information corresponding to the scene type information; the amount information is concatenated with the information identifier and carried in the rendering parameter information; the first application page also includes the payment amount corresponding to the amount information.

14. The method according to claim 10, after the application searches for a URL template having a mapping relationship with the scene type information according to the scene type information, further comprising: If no URL template having a mapping relationship with the scene type information is found, the homepage URL of the application is obtained; Based on the home page URL, the home page of the application is displayed.

15. The method according to claim 9, wherein the service parameter information includes scenario type information and a designated service URL corresponding to the scenario type information; after transmitting the URL to the application, the method further comprises: In a case where the value of the scenario type information is a specified parameter, the application obtains, based on the specified service URL, specified page information corresponding to the specified service URL from a specified server corresponding to the specified service URL; A designated page generated based on the designated page information is displayed.

16. The method according to any one of claims 1 to 15, wherein: The applications include payment applications.

17. A method for executing a service based on NFC, applied to an NFC tag device, comprising: Receiving near field communication signals transmitted by user terminal equipment; In response to the near field communication signal, sending a uniform resource locator URL to a user terminal device via near field communication; The URL includes domain name information and light application card parameters; the light application card parameters are used by the user terminal device to display the light application card to the user according to the light application card parameters; The domain name information is used by the user terminal device to start the application corresponding to the domain name information in response to the user's triggering operation on the light application card; the application is used to execute the payment process corresponding to the URL.

18. The method according to claim 17, before receiving the near field communication signal transmitted by the user terminal device, further comprising: Get the preset trigger operation; In response to the trigger operation, obtaining first service information; Send a URL request to the application server; The URL acquisition request carries the first service information; Receive the URL returned by the application server; the 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 URL obtained by the application server.

19. The method of claim 18, wherein: The trigger operation includes initiating a payment collection operation, the application includes a payment application, and the business process includes a payment process.

20. A service execution device based on NFC, applied to a user terminal device, comprising: A URL acquisition module is used to acquire a uniform resource locator URL provided by an NFC tag device through a near field communication method; The URL includes domain name information and light app card parameters; A generating module, used for displaying a light application card to a user according to the light application card parameters; An application startup module, configured to start the application corresponding to the domain name information in response to the user's triggering operation on the light application card; The application is used to execute the payment process corresponding to the URL.

21. A service execution device based on NFC, applied to an NFC tag device, comprising: A signal receiving module, used to receive a near field communication signal transmitted by a user terminal device; An information sending module, configured to send a uniform resource locator URL to a user terminal device via a near field communication method in response to the near field communication signal; the URL includes domain name information and light application card parameters; the light application card parameters are used by the user terminal device to display the light application card to the user according to the light application card parameters; The domain name information is used by the user terminal device to start the application corresponding to the domain name information in response to the user's triggering operation on the light application card; the application is used to execute the payment process corresponding to the URL.

22. A user terminal device, the user terminal device serving as an NFC card reader, 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 uniform resource locator URL provided by the NFC tag device through near field communication; the URL includes domain name information and light application card parameters; Displaying the light app card to the user according to the light app card parameters; In response to the user's triggering operation on the light application card, the application corresponding to the domain name information is started; the application is used to execute the payment process corresponding to the URL.

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 near field communication signals transmitted by user terminal equipment; In response to the near-field communication signal, a uniform resource locator URL is sent to the user terminal device via near-field communication; the URL includes domain name information and light application card parameters; the light application card parameters are used by the user terminal device to display a light application card to the user according to the light application card parameters; the domain name information is used by the user terminal device to respond to the user's triggering operation on the light application card, and start the application corresponding to the domain name information; the application is used to execute the payment process corresponding to the URL.

Images