NFC-based service execution methods and apparatuses, and devices

Abstract

Disclosed in the embodiments of the present specification are near field communication (NFC)-based service execution methods and apparatuses, and devices. The solution may comprise: on the basis of an NFC mode, an operating system acquiring a uniform resource locator (URL) from an NFC tag device; determining a target application on the basis of domain name information in the URL; and launching the target application, such that the target application executes a service process corresponding to the URL, wherein the URL includes protocol type information indicating that the URL conforms to a hyper text transfer protocol secure, domain name information, and light-application card information configured to be recognized by an IOS operating system in the form of a light-application card.

Description

NFC-based service execution method, device and equipment

[0001] The present application claims priority to the Chinese patent application No. 202411067880.4, filed on August 5, 2024, and entitled "NFC-based service execution method, device and equipment", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the technical field of service processing of wireless communication, and in particular to an NFC-based service execution method, device and equipment. BACKGROUND

[0003] Near Field Communication (NFC) is widely used in various fields due to its convenience, safety and low power consumption. However, in some special scenarios, the process of executing a service based on NFC may fail. For example, for a terminal device running an IOS operating system, there is a client wake-up obstacle in the following scenarios: in a locked screen state, in a short time after the screen is unlocked, and in a short time after the screen is turned on, and the terminal device cannot execute a wake-up task based on NFC.

[0004] Therefore, how to improve the success rate of executing a service based on NFC has become a technical problem to be solved.

[0005] SUMMARY

[0006] The embodiments of the present specification provide an NFC-based service execution method, device and equipment to overcome the client wake-up obstacle in some scenarios and improve the success rate of executing a service based on NFC.

[0007] To solve the above technical problem, the embodiments of the present specification are implemented as follows: The NFC-based service execution method provided by the embodiments of the present specification is applied to a user terminal device, and includes: an operating system acquires a uniform resource locator (URL) provided by an NFC tag device through a near field communication (NFC) mode; the URL contains protocol type information, domain name information and a light application card parameter; the protocol type information indicates that the URL conforms to the hypertext transfer protocol secure (HTTPS) protocol; the light application card parameter is used to be recognized by an 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 a service flow corresponding to the URL.

[0008] The embodiment of the present specification provides a NFC-based service execution method, which is applied to an NFC tag device and includes the following steps: receiving a near field communication signal transmitted by a user terminal device; in response to the near field communication signal, sending a uniform resource locator (URL) to the user terminal device through a near field communication mode; the URL contains protocol type information, domain name information and light application card parameters; the protocol type information indicates that the URL conforms to the hypertext transfer protocol secure (HTTPS) protocol; the light application card parameters are used to be recognized by an IOS operating system in the form of a light application card; the domain name information is used to start an application corresponding to the domain name information by the user terminal device; and the application is used to execute a service flow corresponding to the URL.

[0009] The embodiment of the present specification provides a NFC-based service execution device, which is applied to a user terminal device and includes the following steps: a URL acquisition module is configured to acquire a uniform resource locator (URL) provided by an NFC tag device through a near field communication mode; the URL contains protocol type information, domain name information and light application card parameters; the protocol type information indicates that the URL conforms to the hypertext transfer protocol secure (HTTPS) protocol; the light application card parameters are used to be recognized by an IOS operating system in the form of a light application card; and an application starting module is configured to start an application corresponding to the domain name information; and the application is used to execute a service flow corresponding to the URL.

[0010] The embodiment of the present specification provides a NFC-based service execution device, which is applied to an NFC tag device and includes the following steps: a signal receiving module is configured to receive a near field communication signal transmitted by a user terminal device; and an information sending module is configured to send a uniform resource locator (URL) to the user terminal device through a near field communication mode in response to the near field communication signal; the URL contains protocol type information, domain name information and light application card parameters; the protocol type information indicates that the URL conforms to the hypertext transfer protocol secure (HTTPS) protocol; the light application card parameters are used to be recognized by an IOS operating system in the form of a light application card; the domain name information is used to start an application corresponding to the domain name information by the user terminal device; and the application is used to execute a service flow corresponding to the URL.

[0011] The user terminal device provided by the embodiments of the present specification comprises at least one processor and a memory in communication connection with the at least one processor; the memory stores instructions executable by the at least one processor; the instructions are executed by the at least one processor to enable the at least one processor to: acquire 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 conforms to the hypertext transfer protocol secure (HTTPS) protocol; the light application card parameters are used to be recognized by an 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 a business process corresponding to the URL.

[0012] The NFC tag device provided by the embodiments of the present specification comprises at least one processor and a memory in communication connection with the at least one processor; the memory stores instructions executable by the at least one processor; the instructions are executed by the at least one processor to enable the at least one processor to: receive a near field communication signal transmitted by a user terminal device; in response to the near field communication signal, send a uniform resource locator (URL) to the user terminal 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 conforms to the hypertext transfer protocol secure (HTTPS) protocol; the light application card parameters are used to be recognized by an IOS operating system in the form of a light application card; the domain name information is used to start an application corresponding to the domain name information by the user terminal device; and the application is used to execute a business process corresponding to the URL.

[0013] At least one embodiment in the present specification can achieve the following beneficial effects: the URL transmitted based on near field communication contains protocol type information conforming to the HTTPS protocol and light application card parameters that can be used to be recognized by an IOS operating system in the form of a light application card. The URL transmitted based on near field communication can be recognized by many operating systems including but not limited to IOS, so that the success rate of terminal calling of devices of various operating systems can be greatly improved on the basis of the URL being recognized by many operating systems, and the success rate of business execution is further improved. BRIEF DESCRIPTION OF DRAWINGS

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

[0015] FIG. 1 is a schematic diagram of an application scenario of a NFC-based service execution method according to an embodiment of the present specification;

[0016] FIG. 2 is a schematic diagram of a flow of a NFC-based service execution method according to an embodiment of the present specification;

[0017] FIG. 3 is a schematic diagram of a structure of a URL according to an embodiment of the present specification;

[0018] FIG. 4 is a schematic diagram of a target application being enabled according to an embodiment of the present specification;

[0019] FIG. 5 is a schematic diagram of a first preset page according to an embodiment of the present specification;

[0020] FIG. 6 is a schematic diagram of a display page containing a banner page element according to an embodiment of the present specification;

[0021] FIG. 7 is a schematic diagram of a light application card according to an embodiment of the present specification;

[0022] FIG. 8 is a schematic diagram of a light application page according to an embodiment of the present specification;

[0023] FIG. 9 is a schematic diagram of a flow of another NFC-based service execution method according to an embodiment of the present specification;

[0024] FIG. 10 is a schematic diagram of a swim lane flow corresponding to the NFC-based service execution method in FIG. 2 and FIG. 9 according to an embodiment of the present specification;

[0025] FIG. 11 is a schematic diagram of another swim lane flow corresponding to the NFC-based service execution method in FIG. 2 and FIG. 9 according to an embodiment of the present specification;

[0026] FIG. 12 is a schematic diagram of a structure of a device for NFC-based service execution corresponding to FIG. 2 according to an embodiment of the present specification;

[0027] FIG. 13 is a schematic diagram of a structure of a device for NFC-based service execution corresponding to FIG. 9 according to an embodiment of the present specification;

[0028] FIG. 14 is a schematic diagram of a structure of a user terminal device for the service execution method corresponding to FIG. 2 according to an embodiment of the present specification;

[0029] FIG. 15 is a schematic diagram of a structure of an NFC tag device for the service execution method corresponding to FIG. 9 according to an embodiment of the present specification. DETAILED DESCRIPTION

[0030] In order to make the purposes, technical solutions and advantages of one or more embodiments of the present specification clearer, the technical solutions of one or more embodiments of the present specification will be described clearly and completely below in conjunction with specific embodiments of the present specification and corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present specification, rather than all the embodiments. Based on the embodiments in the present specification, all other embodiments obtained by a person of ordinary skill in the art without creative labor fall within the protection scope of one or more embodiments of the present specification.

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

[0032] 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, with a working frequency of 13.56 MHz, and a communication distance usually within 10 centimeters.

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

[0034] Awakening: refers to waking up a mobile terminal application or making it enter an active state through a certain triggering mechanism.

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

[0036] In the prior art, when waking up an application at a mobile terminal based on NFC technology, the traditional URL protocol is usually used for awakening. The traditional URL protocol can be alipay, alipays, etc. However, based on the traditional URL protocol for awakening, when the operating system at the mobile terminal is an IOS system, the mobile terminal is in a locked state or within two seconds after the mobile terminal is unlocked, or the mobile terminal is in a screen-on state (for example, within two seconds after the screen is turned on from off), due to the protection mechanism carried by the IOS operating system itself, the traditional URL protocol cannot be recognized by the mobile terminal, there is a client awakening obstacle, and thus the awakening task of the application at the mobile terminal fails, therefore, the success rate of awakening the application at the mobile terminal through NFC technology in the prior art is low.

[0037] The technical solutions provided by the embodiments of the present specification will be described in detail below in conjunction with the drawings.

[0038] Fig. 1 is a schematic diagram of an application scenario of a NFC-based service execution method according to an embodiment of the present specification.

[0039] As shown in Fig. 1, the schematic diagram of the application scenario includes an initiating device 101 and a target device 102.

[0040] In the embodiments of the present specification, the initiating device is a device that initiates communication actively and is responsible for generating a radio frequency field and initiating a NFC communication process. The initiating device can include, but is not limited to, a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart interactive device, or other devices capable of actively sending NFC signals, etc., and the initiating device 101 is any one of the initiating devices.

[0041] The target device is a device that responds passively, which responds to the request of the initiating device and exchanges data. The target device can include, but is not limited to, an NFC tag, a smart card, an access control card, a payment terminal, or other smart devices, etc., and the target device 102 is any one of the target devices.

[0042] The initiating device interacts with the target device by sending commands and data, and the target device relies on the radio frequency field generated by the initiating device for energy supply and data transmission.

[0043] Fig. 2 is a schematic diagram of a flow of a NFC-based service execution method according to an embodiment of the present specification. From the software point of view, the execution subject of the flow can be a program or an application client carried on a user terminal device with NFC function. From the hardware point of view, the execution subject of the flow can be a user terminal device with NFC function.

[0044] As shown in Fig. 2, the method can include the following steps.

[0045] In step 202, an operating system acquires a uniform resource locator (URL) provided by an NFC tag device through near field communication (NFC); the URL contains protocol type information, domain name information, and a light application card parameter; the protocol type information indicates that the URL conforms to the hypertext transfer protocol secure (HTTPS) protocol; and the light application card parameter is used to be recognized by an IOS operating system in the form of a light application card.

[0046] In the embodiments of the present specification, the operating system can be any one of an Android operating system, a Harmony operating system, and an IOS operating system; or the operating system can also be any one of operating systems running on a device with NFC function, and the type of the operating system is not limited.

[0047] In the embodiments of the present specification, the terminal device where the operating system is located can be collectively referred to as a user terminal device. The user terminal device and the NFC tag device establish a communication connection through near field communication. Based on the established communication connection, the NFC tag device sends a URL to the user terminal device. The URL can be a URL pre-stored on the NFC tag device by a developer, or can be a URL generated in real time in response to a request of an actual operator.

[0048] In the embodiments of the present specification, the URL can include protocol type information, domain name information, path information, query parameter information, and the like. The protocol in the URL can 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 a target application.

[0049] In order to facilitate those skilled in the art to understand the present scheme, a specific example of the URL is proposed in the embodiments of the present specification.

[0050] As shown in FIG. 3, the URL contains 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.

[0051] Further, in the service parameter information corresponding to the second query parameter, “CCC” can represent scene type information carried at a specified position of the URL; “VALUE” can represent an information identifier carried at a specified position of the URL, or can represent a combination of an information identifier and an amount of money carried at a specified position of the URL. The information in the service parameter information other than “CCC” and “VALUE” is specified format information, and the application receiving the URL can extract “CCC” and “VALUE” therefrom based on identification of the format information.

[0052] In the example of the URL, AAA, BBB, CCC and VALUE are only illustrative symbols for indicating the positions of the corresponding information. In actual applications, AAA, BBB, CCC and VALUE in the URL can be actual strings. As in a specific example of a URL "https: / / ulink.alipay.com / snxxx?s=nfc&scheme=alipay%1A2B3c4d%1A2B3c4d%5E6F1q2w3e4r5t6y7u8i", the string "snxxx" corresponds to the path "AAA" in the example of FIG. 3, the string "nfc" corresponds to the value "BBB" of the first query parameter s in the example of FIG. 3, the string "sn" corresponds to the scenario type information "CCC" in the example of FIG. 3, and the string "1q2w3e4r5t6y7u8i" corresponds to the information identifier "VALUE" in the example of FIG. 3.

[0053] In addition, in actual applications, 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 information that is not changed in a period of time and does not change in different communication processes, so that the operating system, the operating system server, the application program, the application server and the like can identify and process the received URL according to the pre-set information. Of course, during software updating, scheme upgrading and the like, the foregoing agreed information can also be changed. For example, the domain name can be changed from ulink.alipay.com to render.alipay.com, and after the change, the operating system, the operating system server, the application program, the application server and the like need to be updated synchronously.

[0054] In the embodiments of the present specification, the IOS14 version and later operating systems have a light application function that allows users to quickly use an application without downloading and installing a complete application, i.e., a light application function running on the operating system. Therefore, in order to adapt to the light application function of the IOS14 version and later operating systems, the URL transmitted based on the NFC mode can include a light application card parameter for being recognized 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 parameter in the URL, the light application function in the IOS operating system can be triggered, and then the corresponding light application card is displayed based on the light application function, so as to improve the success rate of calling the IOS operating system.

[0055] Optionally, the light application card parameter can be carried in the path information of the URL.

[0056] Step 204: starting an application corresponding to the domain name information; the application is used to execute a business process corresponding to the URL.

[0057] In the embodiments of the present specification, based on the obtained URL, if the target application has been installed in the operating system, the operating system can start 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 target application has not been installed in the operating system, the operating system can open an application page corresponding to the URL, so that the user completes the subsequent business process according to the display information of the opened application page.

[0058] It should be understood that the order of some or all of the steps in the method described in one or more embodiments of the present specification can be exchanged according to actual needs, or some or all of the steps can be omitted or deleted.

[0059] The method in FIG. 2 can be recognized by the IOS operating system based on the URL transmitted by NFC and recognized by the Android system and the Hongmeng system. In the scenario of calling the terminal based on NFC, the device of the IOS operating system can also be successfully called, thereby greatly improving the calling success rate of the device of the IOS operating system, and improving the overall calling success rate of the user group device.

[0060] Based on the method in FIG. 2, the embodiments of the present specification also provide some specific implementations of the method, which are described below.

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

[0062] Optionally, the application corresponding to the domain name information in the embodiments of the present specification can specifically include: determining the application corresponding to the URL according to the domain name information; judging whether the application has been installed in the operating system to obtain a judgment result; and if the judgment result indicates that the application has been installed in the operating system, starting the application.

[0063] In the embodiments of the present specification, the domain name information can be information designed by the developer of the application program to determine the corresponding application. The domain name information corresponding to the application can be pre-registered on the World Wide Web, so that the corresponding application can be determined based on the domain name information.

[0064] In the embodiments of the present specification, after the operating system obtains the URL sent by the NFC tag device, the operating system 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 installed on the operating system based on the determined target application and each application installed on the operating system. If it is determined that the target application is installed on the operating system, the target application is started.

[0065] Optionally, taking the target application as Alipay as an example, the page after the target application is enabled for the payment scenario can be as shown in FIG. 4. The information displayed in FIG. 4 is only an example, and different information from that in FIG. 4 can be displayed in actual application, and other text, pictures, moving pictures, controls and the like can be displayed, and the information displayed in FIG. 4 is not limited.

[0066] In the embodiments of the present specification, if it is determined that the operating system does not install the target application, the operating system can display the corresponding page corresponding to the URL. Optionally, after the determination of whether the application is installed in the operating system is obtained, the method can further 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 a user to download the application.

[0067] In the embodiments of the present specification, the URL obtained by the operating system can be a resource address for identifying and locating a resource. Therefore, after it is determined that the operating system does not install the target application, the first preset page information corresponding to the URL can be obtained from the server of the target application based on the URL, and the corresponding first preset page can 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 and the like. The first preset page can include the first download control, and the user can trigger the download and installation process of the target application after performing a triggering operation on the first download control.

[0068] Optionally, taking the target application as Alipay as an example, the generated first preset page can be as shown in FIG. 5. In FIG. 5, the first download control 10 is a "download Alipay" control. The information displayed in FIG. 5 is only an example, and different information from that in FIG. 5 can be displayed in actual application, and other text, pictures, moving pictures, controls and the like can be displayed, and the information displayed in FIG. 5 is not limited.

[0069] In the embodiments of the present specification, after it is judged that the target application has been installed in the operating system, the target application can be directly started to improve user experience; when it is judged that the target application has not been 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 improve the user usage of the target application.

[0070] To improve user experience, after the operating system obtains the URL at the NFC tag device based on the NFC mode, prompt information for prompting whether the user needs to access the target application can be generated in advance, so that the target application can be started only after the authorization of the user is obtained, to avoid disturbing the user when the user does not need to open the target application.

[0071] Optionally, before the judging whether the application has been installed in the operating system, the method can further include: displaying a banner page element; the banner page element contains information for prompting to access the application; and obtaining a first trigger operation of the user on the banner page element.

[0072] The judging whether the application has been installed in the operating system can specifically include: in response to the first trigger operation, judging whether the application has been installed in the operating system.

[0073] In the embodiments of the present specification, after the operating system determines the target application based on the domain name information in the URL, a banner page element can be displayed in the current interface in which the operating system runs. The banner page element can contain prompt information for prompting whether the user needs to access the application program. The banner page element can be displayed in any one of the top region, the bottom region and the middle region in the visual region of the current interface, or the banner page element can be displayed in any region in the visual region of the current interface, and the display position of the banner page element is not limited.

[0074] Optionally, taking the target application as Alipay as an example, the display page containing the banner page element can be as shown in FIG. 6. In FIG. 6, the banner page element 20 is located in the top region of the visual region. The information displayed in FIG. 6 is only an example, and different information from that in FIG. 6 can be displayed in actual application, and other text, pictures, moving pictures, controls and the like can be displayed, and the information displayed in FIG. 6 is not limited.

[0075] In the embodiments of the present specification, if the operating system obtains the first trigger operation of the user on the banner page element within a preset time, the first trigger operation can be a click operation of the user on a preset control in the banner page element, or can also be a click operation of the user on any position of the banner page element. In response to the first trigger operation of the user, 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 has not been installed in the operating system, a target page for prompting the user to download the target application is displayed.

[0076] In the embodiments of the present specification, if the operating system does not obtain the first trigger operation of the user on the banner page element within a preset time, the display of the banner page element is stopped.

[0077] On the basis of the above-mentioned embodiments, in the embodiments of the present specification, the operating system can include an IOS operating system with a light application function. Before judging whether the application has been installed in the operating system, the method can further include: obtaining light application card information corresponding to the light application card parameter according to the light application card parameter; 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 on the application access control.

[0078] The judgment on whether the application has been installed in the operating system can specifically include:

[0079] In response to the second trigger operation, it is judged whether the application has been installed in the operating system.

[0080] In the embodiments of the present specification, the operating system can include an IOS operating system with a light application function, and specifically can be an operating system of IOS14 version and above. The light application can be an application program running in the operating system without the need for downloading. For example: app clips running on the IOS operating system.

[0081] In the embodiments of the present specification, the light application card information corresponding to the light application card parameter can be obtained based on the light application card parameter, and the light application card information corresponding to the light application card parameter can be obtained from the system server corresponding to the operating system based on the light application card parameter. The light application card information can include picture information, title information, subtitle information, and control information, etc. Different business scenarios can correspond to different light application card parameters, and the light application card information corresponding to each light application card parameter can be different. For example, the light application card parameter corresponding to the payment scenario is different from the light application card parameter corresponding to the gate opening scenario, and the light application card parameter corresponding to the payment scenario is also different from the light application card parameter corresponding to the service machine water selling business scenario.

[0082] In the embodiments of the present specification, the light application card information can be information registered in advance by the R&D personnel of the application corresponding to the light application card information at the system server corresponding to the operating system. For example, for the payment scenario of the target application, if the R&D personnel wants to display the picture of interface A when displaying the payment scenario of the target application, the R&D personnel can register the related information of the picture of interface A in advance 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 R&D personnel will also add the parameters of the related information about displaying the picture of interface A when displaying the payment scenario of the target application to the corresponding URL, so that the operating system can parse the light application card parameter for interface A after obtaining the URL, and obtain the corresponding light application card information from the system server based on the light application card parameter, 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.

[0083] Optionally, taking the target application Alipay as an example, for the payment scenario, the generated light application card can be as shown in FIG. 7. In FIG. 7, the application access control 30 is an “open” control. The information displayed in FIG. 7 is only an example, and different information from that in FIG. 7 can be displayed in actual application, and other text, picture, moving picture, control, etc. information can be displayed, and the information displayed in FIG. 7 is not limited.

[0084] In the embodiments of the present specification, if the operating system obtains the second triggering operation of the user on the application access control within a preset time, the judgment process for whether the target application has been installed in the operating system is performed in response to the second triggering operation, and if it is judged that the target application has been installed in the operating system, the target application is started.

[0085] In the embodiments 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.

[0086] Optionally, the URL can further include a light application page parameter. After determining whether the application is installed in the operating system, if the result of the determination indicates that the application is not installed in the operating system, light application page information corresponding to the light application page parameter can be obtained according to the light application page parameter. A light application page generated based on the light application page information can be displayed 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.

[0087] In the embodiments of the present specification, the light application page parameter can be carried in the query parameter information of the URL. Specifically, as shown in FIG. 3, the light application page parameter can be a parameter value corresponding to a first query parameter in the URL. For example, the parameter value corresponding to the parameter s.

[0088] In the embodiments of the present specification, in response to the second trigger operation, a determination process on whether the target application is installed in the operating system is performed. If it is determined that the target application is not installed in the operating system, light application page information corresponding to the light application page parameter can be obtained according to the light application page parameter. Specifically, the light application page information corresponding to the light application page parameter can be obtained from a system server corresponding to the operating system based on the light application page parameter. The light application page information can include image information, title information, subtitle information, and control information.

[0089] In the embodiments of the present specification, the light application page information can be information registered in advance by a developer of an application corresponding to the light application page information at a system server corresponding to the operating system.

[0090] In the embodiments of the present 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, a download and installation process of the target application can be triggered.

[0091] Optionally, taking the target application as Alipay as an example, the generated light application page can be as shown in FIG. 8. The second download control 40 in FIG. 8 is a “download” control. The information displayed in FIG. 8 is only an example, and different information can be displayed in actual applications. Specifically, other text, images, moving pictures, controls, and the like can be displayed, and the information displayed in FIG. 8 is not limited.

[0092] On the basis of the above-mentioned embodiments, in the embodiments of the present specification, the light application page can further contain a business control for instructing execution of a business process; after the light application page generated based on the light application page information is displayed, the method can further include: obtaining a third triggering operation of the user on the business control; and in response to the third triggering operation, highlighting the second download control.

[0093] In the embodiments of the present specification, the business control can be a control for prompting the user to make a payment, or can also be a control for prompting the user to experience a target application. After obtaining the third triggering operation of the user on the business control, in response to the third triggering operation, the second download control is highlighted to guide the user to execute download and installation of the target application through the second download control. In this way, the convenience of the user for downloading and installing the target application is improved, and thus the user usage amount of the target application is improved.

[0094] In the embodiments of the present specification, one or more embodiments are further provided for the target application to execute a business process based on the URL.

[0095] Optionally, after the application corresponding to the domain name information is started, the method can further include: transmitting the URL to the application; the URL can further contain business parameter information; and the business parameter information is used as a basis for the application to execute a business process corresponding to the URL.

[0096] In the embodiments of the present specification, the business parameter information can be carried in the query parameter information of the URL.

[0097] Optionally, as shown in FIG. 3, the business parameter information can be a parameter value corresponding to a second query parameter in the URL. For example, a parameter value corresponding to a parameter scheme.

[0098] In the embodiments of the present specification, after the operating system judges that the operating system has installed the target application and starts the target application, the operating system will send the URL to the target application, and the target application executes a subsequent business process based on the business parameter information in the URL.

[0099] On the basis of the above-mentioned embodiments, in the embodiments of the present specification, the business parameter information can contain scene type information and information identifiers corresponding to the scene type information; and the information identifiers are used as a basis for querying business description information.

[0100] After the URL is transmitted to the application, the method can further include:

[0101] The application queries a URL template having a mapping relationship with the scene type information according to the scene type information; the URL template contains replaceable marks; the replaceable marks are used to identify positions where the information identifier can be input; the replaceable marks are replaced by the information identifier to obtain a service URL carrying the information identifier; and a service flow is executed based on the service URL.

[0102] In the embodiments of the present specification, the scene type information is used to reflect a specific implementation scene when a service is executed, and the service scene can include a payment scene, a gate opening scene, an ordering scene, and a service machine water selling scene, etc. Optionally, the information identifier can be identification data generated based on service data generated when a service is executed, such as identification data generated based on an order number or a merchant number. The information identifier can be encrypted identification data, and such a setting can improve the security of the service data. Additionally, the information identifier can be a random string. In the application server, the generated information identifier and the service description information corresponding to the information identifier can be correspondingly stored, so as to subsequently query based on the information identifier when the service description information needs to be used.

[0103] In the embodiments of the present specification, a mapping relationship can be pre-established between the scene type information and the URL template, and specifically, a key-value pair form mapping relationship can be established. The scene type information can be a key value, and the URL template can be a value.

[0104] In order to facilitate those skilled in the art to understand the present scheme, a specific example of converting a URL to a service URL is proposed in the embodiments of the present specification.

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

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

[0107] The service 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.

[0108] 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:

[0109] alipays: / / platformapi / startApp?appId=112233&appScheme=NFC_ABC&pageParams=%12345qwert$[value]$%6789. In the URL template, the replaceable mark is $[value].

[0110] The replaceable mark $[value] in the URL template is replaced by the information "1q2w3e4r5t6y7u8i" in the URL, and the business URL obtained is as follows:

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

[0112] In the embodiments of the present specification, based on the URL transmitted between the user terminal device and the NFC tag device, a business URL for executing a business process can be generated, so that the business URL for executing the business process does not need to be transmitted between the user terminal device and the NFC tag device. In this way, on the one hand, the risk of leakage of the business URL can be avoided, and the confidentiality of the business URL can be improved. On the other hand, since the data amount of the URL is smaller than that of the business URL, the data transmission amount between the user terminal device and the NFC tag device can also be reduced, the communication efficiency of the NFC can be improved, and the user experience can be improved.

[0113] On the basis of the above-mentioned embodiments, in the embodiments 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 the execution of the business process based on the business URL can specifically include:

[0114] rendering the first application page based on the rendering parameter information.

[0115] In the embodiments of the present specification, taking the payment scenario as an example, it is assumed that the converted business URL is as follows:

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

[0117] In actual application, the first application page can be rendered based on the rendering parameter information in the business URL. The first application page can be a landing page displayed to the user after the business process is initiated in the NFC mode, and can also be referred to as the first page displayed to the user.

[0118] On the basis of the above embodiment, in the embodiment of the present specification, the first application page can include a preset control. After the first application page is rendered based on the rendering parameter information, the method can further include: in response to a triggering operation of the preset control by the user, sending a business request to an application server of the application; the business request carries the information identifier; 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 business description information; the business description information is obtained by the application server according to the information identifier; and displaying a second application page generated based on the business processing result information.

[0119] Optionally, the information identifier carried in the business URL can be information generated by the application server.

[0120] Optionally, the information identifier can be a token obtained by processing at least part of the information in the business description information by the application server according to a preset information processing rule.

[0121] Optionally, the information identifier can be a random string generated by the application server.

[0122] In actual application, after the information identifier is generated, the information identifier and the corresponding business description information can be stored in association, and the information identifier is used as a query index of the business description information.

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

[0124] In the embodiments of the present specification, the first application page can include a preset control, wherein the preset control can be any one of an input control, a button control, a selection control, and a multimedia control. If the target application obtains a triggering operation of the user on the preset control within a preset time, the target application responds to the triggering 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 and parses the service request to obtain the information identifier carried in the service request, and then queries the business description information corresponding to the information identifier by taking the information identifier as a query index, and further determines the corresponding business processing result information based on the business description information, and sends the business processing result information to the target application. The target application generates a corresponding second application page after receiving the business processing result information and displays the second application page.

[0125] In the embodiments of the present specification, the application server can interact with the target application multiple times 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 legality of the business URL, the process of verifying the security of the business execution environment, and the process of obtaining the related information required to be displayed in the second application page.

[0126] In the embodiments of the present specification, the second application page generated based on the business processing result information can include multiple types of pages. Taking the payment scenario as an example, the second application page can be an application page displaying related information such as payment success. The second application page can also be an application page displaying related information such as a specific payment amount. If the user has opened 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 opened the password-free payment function, the second application page can jump to a third application page after the user clicks the payment button in the second application page, and the user can complete the payment after inputting the correct password in the third application page. The second application page can also be an application page displaying a corresponding window for the user to input the payment amount. If the user has opened the password-free payment function, the user can directly click the corresponding payment button to complete the payment after inputting the corresponding payment amount in the second application page. If the user has not opened the password-free payment function, the second application page can jump to a fourth application page after the user inputs the corresponding payment amount and clicks the payment button corresponding to the payment amount, and the user can complete the payment after inputting the correct password in the fourth application page.

[0127] Optionally, in the payment scenario, the service parameter information further comprises 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 further comprise a payment amount corresponding to the amount information.

[0128] Specifically, when the service parameter information comprises both the information identifier and the amount information, the information identifier and the amount information can be concatenated by a fixed character (for example, _), and then in the subsequent URL conversion process, the amount information and the information identifier can be filled in the service URL obtained after conversion.

[0129] In the embodiments of the present specification, in the payment service scenario, a merchant can input a payment amount to obtain service parameter information carrying amount information, generate a corresponding information identifier based on the payment amount, so that the rendering parameter information in the service URL can carry the payment amount. The first application page rendered based on the rendering parameter information can comprise the payment amount input 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 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 can complete payment after inputting the correct password in the fifth application page.

[0130] It should be noted that in the embodiments of the present specification, the amount information is carried in the service parameter information in the form of plaintext, and then carried in the service URL, so that when the user terminal device obtains the service URL, the payment amount corresponding to the amount information can be displayed in the rendered first application page based on the plaintext amount information in the service URL, in other words, the user can see the payment amount to be paid in the landing page, thereby improving the payment experience of the user. 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 (for example, n) indicating that no payment amount is provided, the payment amount is not displayed in the first application page.

[0131] In order to facilitate those skilled in the art to understand the present scheme, a specific example of conversion from URL to service URL in the case of carrying amount information is provided in the embodiments of the present specification.

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

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

[0134] Wherein, the service 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; the information identifier and the amount information are "1q2w3e4r5t6y7u8i_0.1" in the parameter value corresponding to the parameter scheme.

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

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

[0137] The replaceable mark $[value]$ in the URL template is replaced by the information identifier and the amount information "1q2w3e4r5t6y7u8i_0.1" in the URL, and the service URL obtained is as follows:

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

[0139] In this example, in the first application page landing on the terminal, the user can be displayed "0.1" as the amount to be paid.

[0140] On the basis of the above embodiment, in the embodiment of the present specification, when the URL template is queried based on the scene type information, there can also be a case of query failure.

[0141] Optionally, the application can further include, after querying the URL template having the mapping relationship with the scene type information according to the scene type information: if the URL template having the mapping relationship with the scene type information is not queried, obtaining a home page URL of the application; and displaying a home page of the application based on the home page URL.

[0142] In the embodiments of the present specification, the homepage URL of the application can be pre-stored at the application client. If the URL template with the mapping relationship is not queried based on the scenario type information in the service URL, the application can directly display the homepage of the application based on the pre-stored homepage URL at the client. In this way, the rate of displaying the homepage of the application can be improved. If the homepage URL is not pre-stored at the application client, when the URL template with the mapping relationship is not queried, the application can generate an acquisition request for acquiring the homepage URL and send it to the application server. The application server sends the homepage URL to the application client in response to the acquisition request. The application displays the homepage of the application based on the received homepage URL. In this way, the occupancy rate of the storage resources at the application client can be reduced.

[0143] In the embodiments of the present specification, when the application cannot parse specific service information or cannot parse the application page to be displayed, the homepage of the application can be displayed to the user to reduce the bad experience of the user for the application.

[0144] Optionally, when the scenario type information represents a specified business scenario, the application can access the page corresponding to the specified business URL. Based on this, the scenario type information and the specified business URL corresponding to the scenario type information can be included in the service parameter information. After the URL is transmitted to the application, the application can further include: in the case where the value of the scenario type information is a specified parameter, the application acquires specified page information corresponding to the specified business URL from a specified server corresponding to the specified business URL based on the specified business URL; and displays a specified page generated based on the specified page information.

[0145] In the embodiments of the present specification, the service parameter information in the URL acquired by the operating system from the NFC tag device can include scenario type information and a specified business URL corresponding to the scenario type information. After the target application acquires the URL, if it is judged that the scenario type information in the service parameter information is a specified parameter, the application does not need to query the URL template with the mapping relationship with the scenario type information, and can display a specified page determined based on the specified business URL.

[0146] In the embodiments of the present specification, the application corresponding to the specified business URL is different from the target application, and the server corresponding to the specified business URL is different from the server of the target application. Taking the payment scenario as an example, the target application can be Alipay, the application corresponding to the specified business URL can be other mini-program application, and the displayed specified page can be other mini-program page opened in the Alipay application page, instead of the native page of Alipay. The server corresponding to the specified business URL can be a server of a merchant side or other third-party side. The specified business URL can be a URL specified by a merchant, and the protocol type thereof can be any one of http, https, alipay, and alipays.

[0147] In the embodiments of the present specification, based on user demand, the specified page of other application can be opened in the target application, so that the user can have more autonomous selection right, thereby improving the user experience of the target application.

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

[0149] Based on the same idea as the scheme shown in FIG. 2, the present specification also provides another NFC-based business execution method. FIG. 9 is a flowchart of another NFC-based business execution method provided by the present specification. From the software point of view, the execution subject of the flowchart can be a program or application client carried on the NFC tag device. From the hardware point of view, the execution subject of the flowchart can be the NFC tag device. As shown in FIG. 9, the flowchart can include:

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

[0151] In the embodiments of the present specification, the user terminal device can act as an NFC card reader. When the user terminal device is close to the NFC tag device, the user terminal device sends a request for acquisition to the NFC tag device in the form of sending a near field communication signal, and the request for acquisition is used to request the NFC tag device to acquire a URL.

[0152] Step 904: in response to the near field communication signal, sending a uniform resource locator URL to the user terminal device through the near field communication mode; the URL includes protocol type information, domain name information, and light application card parameters; the protocol type information indicates that the URL conforms to the hypertext transfer protocol secure; the light application card parameters are used to be recognized by the IOS operating system in the form of a light application card; the domain name information is used to start an application corresponding to the domain name information by the user terminal device; and the application is used to execute a business process corresponding to the URL.

[0153] In the embodiments of the present specification, the NFC tag device transmits a URL to the user terminal device in a near field communication manner based on the received near field communication signal in response to the near field communication signal. The URL can include protocol type information, domain name information, port information, path information, query parameter information, and the like. The protocol in the URL can be Hyper Text Transfer Protocol (HTTP) or Hyper Text 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 target application can execute the business process corresponding to the URL based on the URL.

[0154] In the embodiments of the present specification, the IOS14 version and later operating system has a light application function that allows users to quickly use the application without downloading and installing the complete application, i.e., the light application function running on the operating system. Therefore, in order to adapt to the light application function of the IOS14 version and later operating system, the URL transmitted based on the NFC mode can contain a light application card parameter used to be recognized 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 parameter in the URL, the light application function in the IOS operating system can be triggered, and then the corresponding light application card can be displayed based on the light application function, so as to improve the success rate of calling the terminal of the IOS operating system.

[0155] Optionally, the light application card parameter can be carried in the path information of the URL.

[0156] In the embodiments of the present specification, the URL in the NFC tag device can be different for different application scenarios. For example, in the part of the automatic vending scenario, the URL can usually carry fixed information, so the URL containing the fixed information can be pre-burned into the NFC tag device. For example, in some scenarios, the URL can carry business data related to the current business, such as: product order number, user identifier, and order amount information, so the corresponding URL can be generated in real time when the business occurs.

[0157] The method in FIG. 9 can be recognized by the IOS operating system based on the NFC transmission URL that can be recognized by the Android system and the Hongmeng system. In order to successfully call the terminal of the IOS operating system device in the NFC calling terminal scenario, the overall success rate of calling the terminal of the user group device can be improved while the success rate of calling the terminal of the IOS operating system device is greatly improved.

[0158] Based on the method in FIG. 9, the embodiments of the present specification further provide some specific implementation solutions of the method, which are described as follows.

[0159] Optionally, before receiving the near field communication signal transmitted by the user terminal device, the method can further include: obtaining a preset trigger operation; obtaining first service information in response to the trigger operation; sending a URL obtaining request to an application server; the URL obtaining request carrying the first service information; receiving the URL returned by the application server; the URL carrying an information identifier; the information identifier being used to query service description information; the service description information including the first service information and second service information; the second service information including information related to the service corresponding to the URL obtained by the application server.

[0160] In the embodiments of the present specification, the preset trigger operation can be different for different service scenarios. For example, a cashier initiates a payment operation, a service machine initiates a payment operation after selling water, a shopper initiates a payment operation after selecting goods from a vending machine, and a user initiates a payment operation after shopping on the application program corresponding to the merchant, etc.

[0161] In the embodiments of the present specification, taking the payment scenario as an example, the first service information can include information such as a commodity order number, a merchant identifier, an order generation time, and an order generation location. The second service information can include information such as the generation time of the URL, the specific attributes of the URL, the effective time limit of the URL, the identifier of the payment user, and the payment situation of the user.

[0162] In the embodiments of the present specification, the information identifier can be a token generated by the application server according to the service description information.

[0163] Optionally, the application server can process at least part of the information in the service description information according to a preset information processing rule to obtain the token. The preset information processing rule can be different for different scenarios. For example, in the payment scenario, the merchant number or the order number can be processed to obtain the token. In the service machine water selling scenario, the serial number (SN) and the process identifier (PID) can be spliced to obtain the token. In the vending machine selling scenario, the vending machine number and the commodity identifier can be processed to obtain the token.

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

[0165] In the embodiments of the present specification, the application server can store the information identifier in association with the service description information, so that when the application sends a service request to the application server based on the URL, the application server can query the service description information including the service information based on the information identifier, and then promote the service process. In this way, the security of the service information can be improved, and the URL can be shortened, and the amount of data transmitted by the URL can be reduced.

[0166] It should be noted that for a determined NFC tag device, the information identifier in the to-be-generated URL can change, and if the to-be-generated URL also contains amount information, the amount information can also change, and other information can be fixed. Specifically, the protocol type information, domain name information, light application card parameter, light application page parameter, and scene type information in the to-be-generated URL can be unchanged. In addition, in the case where the to-be-generated URL contains a specified service URL, the specified service URL can also be unchanged. In the URL sent by each near field communication performed by the NFC tag device, only the information identifier and the amount information (if any) in the URL sent by different times can be different.

[0167] Optionally, the triggering operation can include initiating a collection operation, the application can include a payment application, and the service flow can include a payment flow.

[0168] In the embodiments of the present specification, for a payment service scenario, based on the NFC communication mode between the user terminal device and the NFC tag device, the payment can be completed through a one-touch operation between devices, so that for users with disabilities such as the elderly using a smart phone, the user can complete payment smoothly without the need for the user to operate the smart phone, such as without the need for the user to open a code scanning device to scan a merchant's two-dimensional code, so that the user payment is more convenient, so as to improve the user experience of the user in the payment process, and then improve the user's stickiness to the target application.

[0169] The embodiments of the present specification also provide a swim lane flow diagram corresponding to the NFC-based service execution method in FIG. 2 and FIG. 9.

[0170] As shown in FIG. 10, for an Android operating system or a Harmony operating system, the NFC-based service execution flow can involve terminal device operating systems, target applications, target application servers, and other execution subjects.

[0171] In the embodiments of the present specification, the terminal device operating system obtains a URL through an NFC near field communication mode, determines a target application corresponding to the URL according to domain name information in the URL, judges whether the target application has been installed in the operating system, if it is judged that the target application has not been installed in the operating system, opens an application download page corresponding to the URL using a browser built in the operating system, wherein a download request control is displayed in the application download page, and after obtaining a trigger operation of the user on the download request control, the target application is downloaded. If it is judged that the target application has been installed in the operating system, the target application is invoked, and the URL is sent to the target application, wherein the URL contains service parameter information, and the service parameter information contains scene type information and an information identifier corresponding to the scene type information.

[0172] After the target application obtains the URL, the scene type information in the URL is used to query a pre-generated mapping relationship table, a URL template having a mapping relationship with the scene type information is queried, and an information identifier corresponding to the scene type information is used to replace a replaceable mark in the queried URL template to obtain a service URL. Based on rendering parameter information in the service URL, a first application page (a landing page) is generated, wherein the first application page contains a preset control. After obtaining a trigger operation of the user on the preset control, the target application sends a service request carrying the information identifier to an application server.

[0173] After the target application server receives the service request sent by the target application, the information identifier carried in the service request is analyzed to obtain service description information corresponding to the information identifier, and then service processing result information is determined based on the service description information, and the service processing result information is sent to the target application, so that the target application displays a second application page based on the service processing result information.

[0174] It should be noted that for some other operating systems, such as operating systems of IOS13 version and below, after the terminal device operating system determines the target application according to the domain name information in the URL, a pop-up window information can be displayed to prompt the user whether to open the target application, and only after obtaining a trigger operation of the user on the pop-up window information, the operation of judging whether the target application has been installed in the operating system is performed.

[0175] As shown in FIG. 11, for operating systems of IOS14 version and above, the NFC-based service execution process can involve terminal device operating systems, operating system servers, target applications, target application servers and other execution subjects.

[0176] In the embodiments of the present specification, the terminal device operating system obtains a URL through an NFC near field communication mode, determines a target application corresponding to the URL according to domain name information in the URL, and sends light application card parameters contained in path information in the URL to an operating system server. The operating system server queries corresponding light application card information based on the received light application card parameters, wherein the light application card information is related information registered by a developer of the target application in advance at the operating system server. After the operating system obtains 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 for prompting the user whether to open the target application. If the operating system obtains a trigger operation of the user on the first control, the operating system starts an operation of judging whether the target application has been installed in the operating system. If it is judged that the target application has not been installed in the operating system, the operating system sends light application page parameters contained in query parameter information of the URL to the operating system server, and the operating system server queries corresponding light application page information based on the received light application page parameters, wherein the light application page information is related information registered by the developer of the target application in advance at the operating system server. After the operating system obtains the light application page information queried by the operating system server, the operating system 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 contains a second control for prompting the user whether to download the target application. After obtaining a trigger operation of the user on the second control, the target application is downloaded. If it is judged that the target application has been installed in the operating system, the target application is invoked, and the 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.

[0177] After the target application obtains the URL, the target application queries a URL template having a mapping relationship with the scene type information by querying a mapping relationship table generated in advance according to the scene type information in the URL, and replaces a replaceable mark in the queried URL template using the information identifier corresponding to the scene type information, to obtain a business URL. Based on rendering parameter information in the business URL, a first application page (a landing page) is generated, wherein the first application page contains a preset control. After obtaining a trigger operation of the user on the preset control, the target application sends a business request carrying the information identifier to an application server.

[0178] The target application server, after receiving the service request sent by the target application, queries the service description information corresponding to the information identifier based on the analysis operation on the information identifier carried in the service request, and then determines the service processing result information based on the service description information, and sends the service processing result information to the target application, so that the target application displays the second application page based on the service processing result information.

[0179] Based on the same idea, the present specification embodiment also provides a device corresponding to the above method. Fig. 12 is a structural schematic diagram of a NFC-based service execution device corresponding to Fig. 2 provided by the present specification embodiment. As shown in Fig. 12, the device can include:

[0180] The URL acquisition module 1202 is configured to acquire a uniform resource locator (URL) provided by an NFC tag device through a near field communication (NFC) mode; the URL includes protocol type information, domain name information, and a light application card parameter; the protocol type information indicates that the URL conforms to a hypertext transfer protocol secure (HTTPS) protocol; and the light application card parameter is used to be recognized by an IOS operating system in the form of a light application card.

[0181] The application starting module 1204 is configured to start an application corresponding to the domain name information; the application is used to execute a service flow corresponding to the URL.

[0182] Based on the device of Fig. 12, the present specification embodiment also provides some specific implementation schemes of the device, which are described below.

[0183] Optionally, the application starting module 1204 can specifically include:

[0184] The application determining unit is configured to determine the application corresponding to the URL according to the domain name information.

[0185] The application judging unit is configured to judge whether the application has been installed in the operating system to obtain a judgment result.

[0186] The application starting unit is configured to start the application if the judgment result indicates that the application has been installed in the operating system.

[0187] Optionally, the application starting module 1204 can further include:

[0188] The first preset page information acquisition unit is configured to acquire first preset page information corresponding to the URL from an application server of the application if the judgment result indicates that the application has not been installed in the operating system.

[0189] The first preset page display unit is configured to display a first preset page generated based on the first preset page information, wherein the first preset page comprises a first download control configured to prompt a user to download the application.

[0190] Optionally, the application starting module 1204 can further include:

[0191] The page element display unit is configured to display a banner page element, wherein the banner page element comprises information configured to prompt a user to access the application.

[0192] The first trigger operation acquisition unit is configured to acquire a first trigger operation of the user on the banner page element.

[0193] Optionally, the application judging unit can specifically include:

[0194] The first application judging sub-unit is configured to judge whether the application has been installed in the operating system in response to the first trigger operation.

[0195] Optionally, the operating system comprises an IOS operating system with a light application function. The application starting module 1204 can further include:

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

[0197] The card display unit is configured to display a light application card generated based on the light application card information, wherein the light application card comprises an application access control configured to prompt a user to access the application.

[0198] The second trigger operation acquisition unit is configured to acquire a second trigger operation on the application access control.

[0199] Optionally, the application judging unit can specifically include:

[0200] The second application judging sub-unit is configured to judge whether the application has been installed in the operating system in response to the second trigger operation.

[0201] Optionally, the URL further comprises a light application page parameter.

[0202] Optionally, the application starting module 1204 can further include:

[0203] The light application page information acquisition unit is configured to acquire 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 has not been installed in the operating system.

[0204] The light application page display unit is configured to display a light application page generated based on the light application page information in the light application corresponding to the light application card; and the light application page includes a second download control for prompting a user to download the application.

[0205] Optionally, the light application page further includes a business control for indicating execution of a business process.

[0206] Optionally, the application starting module 1204 can further include:

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

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

[0209] Optionally, the application starting module 1204 can further include:

[0210] The URL transmission unit is configured to transmit the URL to the application; the URL further includes business parameter information; and the business parameter information is used as a basis for the application to execute a business process corresponding to the URL.

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

[0212] Optionally, the application starting module 1204 can further include:

[0213] The URL template query unit is configured to query, by the application, a URL template having a mapping relationship with the scene type information according to the scene type information; and the URL template includes a replaceable mark; and the replaceable mark is used to identify a position at which the information identifier can be input.

[0214] The replaceable mark replacement unit is configured to replace the replaceable mark with the information identifier to obtain a business URL carrying the information identifier.

[0215] The business process execution unit is configured to execute a business process based on the business URL.

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

[0217] The rendering sub-unit is configured to render a first application page based on the rendering parameter information.

[0218] Optionally, the first application page contains a preset control; the business flow execution unit can further include:

[0219] A business request sending subunit is configured to send a business request to an application server of the application in response to a triggering operation of the preset control by a user; the business request carries the information identifier.

[0220] A business processing result information receiving subunit is configured to receive 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 business description information; the business description information is obtained by the application server according to the information identifier.

[0221] A second application page displaying subunit is configured to display a second application page generated based on the business processing result information.

[0222] Optionally, the business parameter information further contains 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 further contains a payment amount corresponding to the amount information.

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

[0224] A home page URL obtaining unit is configured to obtain a home page URL of the application if no URL template having a mapping relationship with the scene type information is found.

[0225] A home page displaying unit is configured to display a home page of the application based on the home page URL.

[0226] Optionally, the business parameter information contains scene type information and specified business URL corresponding to the scene type information.

[0227] Optionally, the application starting module 1204 can further include:

[0228] A specified page information obtaining unit is configured to, in a case where the value of the scene type information is a specified parameter, obtain, by the application, specified page information corresponding to the specified business URL from a specified server corresponding to the specified business URL based on the specified business URL.

[0229] A specified page displaying unit is configured to display a specified page generated based on the specified page information.

[0230] Optionally, the application includes a payment application, and the business flow includes a payment flow.

[0231] Fig. 13 is a structural schematic diagram of an NFC-based service execution apparatus corresponding to Fig. 9, provided by an embodiment of the present specification. As shown in Fig. 13, the apparatus can include:

[0232] The signal receiving module 1302 is configured to receive a near field communication signal transmitted by a user terminal device.

[0233] The information sending module 1304 is configured to send a uniform resource locator (URL) to the user terminal device through a near field communication mode in response to the near field communication signal; the URL contains protocol type information, domain name information and a light application card parameter; the protocol type information indicates that the URL conforms to the hypertext transfer protocol secure (HTTPS) protocol; the light application card parameter is used to be recognized by an IOS operating system in the form of a light application card; the domain name information is used to start an application corresponding to the domain name information by the user terminal device; and the application is used to execute a service flow corresponding to the URL.

[0234] Based on the apparatus of Fig. 13, the present specification further provides some specific implementation schemes of the apparatus, which are described below.

[0235] Optionally, the apparatus in Fig. 13 can further include:

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

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

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

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

[0240] Optionally, the trigger operation includes initiating a collection operation, the application includes a payment application, and the service flow includes a payment flow.

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

[0242] Fig. 14 is a structural schematic diagram of a user terminal device corresponding to the service execution method of Fig. 2, provided by an embodiment of the present specification. As shown in Fig. 14, the device 1400 can include:

[0243] at least one processor 1410; and a memory 1430 connected with the at least one processor in communication; wherein

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

[0245] acquire a 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 conforms to the hypertext transfer protocol secure (HTTPS); and the light application card parameters are used to be recognized by the IOS operating system in the form of a light application card.

[0246] start an application corresponding to the domain name information; the application is used to execute a business process corresponding to the URL.

[0247] FIG. 15 is a structural schematic diagram of an NFC tag device corresponding to the business execution method of FIG. 9 according to an embodiment of the present specification. As shown in FIG. 15, the device 1500 can include:

[0248] at least one processor 1510; and a memory 1530 connected with the at least one processor in communication; wherein

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

[0250] receive a near field communication signal transmitted by a user terminal device.

[0251] In response to the near field communication signal, send a uniform resource locator (URL) to the user terminal 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 conforms to the hypertext transfer protocol secure (HTTPS); the light application card parameters are used to be recognized by the IOS operating system in the form of a light application card; and the domain name information is used to start an application corresponding to the domain name information by the user terminal device; the application is used to execute a business process corresponding to the URL.

[0252] The above described embodiments of the present specification have been described. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order and still achieve desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing can be advantageous or necessary.

[0253] Each of the various embodiments in the present specification is described in a progressive manner, and the same or similar parts between each embodiment can be referred to each other, and each embodiment focuses on the difference from other embodiments. In particular, for the apparatuses shown in FIG. 14 and FIG. 15, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the part of the method embodiment.

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

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

[0256] The systems, apparatuses, modules or units illustrated by the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can 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.

[0257] For the sake of description, the above apparatuses are described in functional division and are described respectively as various units. Of course, the functions of the units can be implemented in the same or multiple software and / or hardware in the implementation of the present application.

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

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

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

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

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

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

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

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

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

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

[0268] The above merely provides an example of the present application, and is not intended to limit the present application. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present application should be included in the scope of claims of the present application.

Claims

1. A NFC-based service execution method applied to a user terminal device, comprising: obtaining, by an operating system, a uniform resource locator (URL) provided by a near field communication (NFC) tag device through a near field communication mode; the URL containing domain name information and a light application card parameter; the light application card parameter being used for being recognized by an IOS operating system in a light application card manner; starting an application corresponding to the domain name information; the application being used for executing a service flow corresponding to the URL.

2. The method of claim 1, wherein, the URL further containing protocol type information; the protocol type information indicating that the URL conforms to a hypertext transfer protocol secure (HTTPS) or a hypertext transfer protocol (HTTP).

3. The method of claim 1, wherein, the light application card parameter being carried in path information of the URL. 4.The method of claim 1, wherein the starting the application corresponding to the domain name information specifically comprises: determining the application corresponding to the URL according to the domain name information; judging whether the application is installed in the operating system to obtain a judgment result; if the judgment result indicates that the application is installed in the operating system, starting the application.

5. The method of claim 4, wherein, after the judging whether the application is installed in the operating system to obtain the judgment result, further comprising: 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 containing a first download control for prompting a user to download the application. 6.The method of claim 5, wherein after the displaying the first preset page generated based on the first preset page information, further comprising: triggering a download and installation process of a target application after a user performs a trigger operation on the first download control.

7. The method of claim 4, wherein, before the judging whether the application is installed in the operating system, further comprising: displaying a banner page element; the banner page element containing information for prompting to access the application; obtaining a first trigger operation of a user on the banner page element; the judging whether the application is installed in the operating system specifically comprises: judging whether the application is installed in the operating system in response to the first trigger operation.

8. The method of claim 4, wherein, the operating system comprises an IOS operating system with a light application function; before the judging whether the application is installed in the operating system, further comprising: obtaining light application card information corresponding to the light application card parameter according to the light application card parameter; displaying a light application card generated based on the light application card information; the light application card containing an application access control; the application access control being used for prompting a user to access the application; obtaining a second trigger operation on the application access control; the judging whether the application is installed in the operating system specifically comprises: judging whether the application is installed in the operating system in response to the second trigger operation. 9.The method of claim 8, wherein the URL further contains a light application page parameter; and after the judging whether the application is installed in the operating system, further comprising: If the judgment result indicates that the application is not installed in the operating system, light application page information corresponding to the light application page parameter is obtained according to the light application page parameter; In the light application corresponding to the light application card, a light application page generated based on the light application page information is displayed; the light application page includes a second download control for prompting a user to download the application.

10. The method of claim 9, wherein the light application page further includes a business control for indicating execution of a business process. After the light application page generated based on the light application page information is displayed, the method further includes: obtaining a third triggering operation of the user on the business control; in response to the third triggering operation, highlighting the second download control.

11. The method of claim 9, wherein the light application includes an app clip running on an IOS operating system.

12. The method of claim 1, after the application corresponding to the domain name information is started, the method further includes: transmitting the URL to the application; the URL further includes business parameter information; the business parameter information is used as a basis for the application to execute a business process corresponding to the URL.

13. The method of claim 12, wherein the service parameter information comprises scene type information and information identification corresponding to the scene type information. the information identifier is used as a basis for querying business description information; after the URL is transmitted to the application, the method further includes: the application queries a URL template having a mapping relationship with the scene type information according to the scene type information; the URL template includes a replaceable mark; the replaceable mark is used to identify a position where the information identifier can be input; the replaceable mark is replaced by the information identifier to obtain a business URL carrying the information identifier; a business process is executed based on the business URL.

14. The method of claim 13, wherein the business URL includes rendering parameter information for rendering a first application page; the information identifier is carried in the rendering parameter information; the business process is executed based on the business URL, specifically including: a first application page is rendered based on the rendering parameter information. the first application page includes a preset control; after the first application page is rendered based on the rendering parameter information, the method further includes:

15. The method of claim 14, wherein, in response to a triggering operation of the user on the preset control, a business request is sent to an application server of the application; the business request carries the information identifier; business processing result information determined by the application server in response to the business request is received; the business processing result information is determined by the application server according to business description information; the business description information is queried by the application server according to the information identifier; a second application page generated based on the business processing result information is displayed.

16. The method of claim 14, wherein the business parameter information further 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 further includes a payment amount corresponding to the amount information. ​ 17. The method of claim 13, wherein, The information identifier is specifically a token obtained by processing at least part of the service description information according to a preset information processing rule by the application server.

18. The method of claim 13, after the application querying a URL template having a mapping relationship with the scene type information according to the scene type information, the method further comprises: if no URL template having a mapping relationship with the scene type information is queried, obtaining a home page URL of the application; displaying a home page of the application based on the home page URL.

19. The method of claim 12, the service parameter information comprising scene type information and a specified service URL corresponding to the scene type information; after the application transmitting the URL, the method further comprises: in a case where the value of the scene type information is a specified parameter, the application obtaining specified page information corresponding to the specified service URL from a specified server corresponding to the specified service URL based on the specified service URL; displaying a specified page generated based on the specified page information.

20. The method of claim 19, wherein, The specified page is a mini-program page in the application.

21. The method of claim 1, wherein, The operating system comprises any one of an Android operating system, a Hongmeng operating system, and an IOS operating system.

22. The method of any one of claims 1 to 21, wherein, The application comprises a payment application, and the service flow comprises a payment flow.

23. A NFC-based service execution method applied to an NFC tag device, comprising: receiving a near field communication signal transmitted by a user terminal device; in response to the near field communication signal, sending a uniform resource locator (URL) to the user terminal device through a near field communication mode; the URL comprising domain name information and light application card parameters; the light application card parameters being used for being recognized by an IOS operating system in a light application card mode; the domain name information being used for starting an application corresponding to the domain name information by the user terminal device; the application being used for executing a service flow corresponding to the URL.

24. The method of claim 23, wherein, The URL further comprises protocol type information; the protocol type information indicating that the URL conforms to a hypertext transfer protocol secure (HTTPS) or a hypertext transfer protocol (HTTP).

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

26. The method of claim 25, wherein, The trigger operation comprises initiating a collection operation, the application comprises a payment application, and the service flow comprises a payment flow.

27. A NFC-based service execution apparatus applied to a user terminal device, comprising: The URL acquisition module is configured to acquire a uniform resource locator (URL) provided by the NFC tag device through near field communication. The URL contains domain name information and a light application card parameter. The light application card parameter is used to be recognized by an IOS operating system in the form of a light application card. The application starting module is configured to start an application corresponding to the domain name information. The application is used to execute a business process corresponding to the URL. 28.A NFC-based business execution apparatus applied to an NFC tag device, comprising: The signal receiving module is configured to receive a near field communication signal transmitted by a user terminal device. The information sending module is configured to send a uniform resource locator (URL) to the user terminal device through near field communication in response to the near field communication signal. The URL contains domain name information and a light application card parameter. The light application card parameter is used to be recognized by an IOS operating system in the form of a light application card. The domain name information is used to start an application corresponding to the domain name information by the user terminal device. The application is used to execute a business process corresponding to the URL. 29.A user terminal device, comprising: at least one processor; and a memory connected to the at least one processor in communication; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: acquire a uniform resource locator (URL) provided by an NFC tag device through near field communication. The URL contains domain name information and a light application card parameter. The light application card parameter is used to be recognized by an 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 a business process corresponding to the URL. 30.A NFC tag device, comprising: at least one processor; and a memory connected to the at least one processor in communication; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: receive a near field communication signal transmitted by a user terminal device. In response to the near field communication signal, send a uniform resource locator (URL) to the user terminal device through near field communication. The URL contains domain name information and a light application card parameter. The light application card parameter is used to be recognized by an IOS operating system in the form of a light application card. The domain name information is used to start an application corresponding to the domain name information by the user terminal device. The application is used to execute a business process corresponding to the URL.

Images