NFC-based service execution method and apparatus, and device

Abstract

To improve a success rate of NFC-based service execution.SOLUTION: One or more implementations of this specification disclose an NFC-based service execution method and apparatus, and a device. The solution may include: an operating system acquires a uniform resource locator (URL) from an NFC tag device based on a near field communication manner, determines a target application based on domain name information in the URL, and starts the target application, so that the target application performs a service process corresponding to the URL. The URL includes protocol type information representing that the URL complies with Hypertext Transfer Protocol Secure, domain name information, and light application card information used to be recognized by an iOS operating system in a light application card manner.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present application relates to the field of wireless communication service processing technology, and in particular to an NFC-based service execution method and apparatus and device. [Background technology]

[0002] Near Field Communication (NFC) is widely used in various fields due to its advantages of convenience, security, and low power consumption. However, in some special scenarios, NFC-based services may not be able to be successfully executed. For example, in a terminal device running the iOS operating system, a terminal device in a lock screen state cannot execute an NFC-based app call task. Summary of the Invention [Problem to be solved by the invention]

[0003] Therefore, how to improve the success rate of NFC-based service execution has become an urgent technical problem to be solved. [Means for solving the problem]

[0004] One or more embodiments herein provide an NFC-based service execution method and apparatus and device to improve the success rate of NFC-based service execution.

[0005] To solve the technical problems mentioned above, one or more embodiments of the present specification are implemented as follows: One or more embodiments of the present specification provide an NFC-based service execution method applied to a user terminal device, including: an operating system acquiring, in a near field communication manner, a uniform resource locator (URL) provided by an NFC tag device, the URL including protocol type information, domain name information, and light application card parameters, the protocol type information indicating that the URL complies with HyperText Transfer Protocol Secure, and the light application card parameters being used for recognition by the iOS operating system in the light application card manner; and starting an application corresponding to the domain name information, the application being configured to execute a service process corresponding to the URL.

[0006] One or more embodiments herein provide an NFC-based service execution method applied to an NFC tag device, the method including: receiving a near field communication signal transmitted by a user terminal device; and, in response to the near field communication signal, transmitting a uniform resource locator (URL) to the user terminal device in a near field communication manner, the URL including protocol type information, domain name information, and lightweight application card parameters, the protocol type information representing that the URL complies with Hypertext Transfer Protocol Secure, the lightweight application card parameters being used to be recognized by an iOS operating system in the lightweight application card manner, the domain name information being used by the user terminal device to launch an application corresponding to the domain name information, and the application being used to execute a service process corresponding to the URL.

[0007] One or more embodiments of the present specification provide an NFC-based service execution apparatus applied to a user terminal device, the apparatus including: a URL acquisition module configured to acquire a uniform resource locator (URL) provided by an NFC tag device in a near field communication manner, the URL including protocol type information, domain name information, and lightweight application card parameters, the protocol type information indicating that the URL complies with Hypertext Transfer Protocol Secure, and the lightweight application card parameters being used to be recognized by an iOS operating system in the lightweight application card manner; and an application launch module configured to launch an application corresponding to the domain name information, the application being used to execute a service process corresponding to the URL.

[0008] One or more embodiments of the present specification provide an NFC-based service execution apparatus applied to an NFC tag device, the NFC-based service execution apparatus including: a signal receiving module configured to receive a near field communication signal transmitted by a user terminal device; and an information sending module configured to send a uniform resource locator (URL) to the user terminal device in a near field communication manner in response to the near field communication signal, the URL including protocol type information, domain name information, and lightweight application card parameters, the protocol type information representing that the URL complies with Hypertext Transfer Protocol Secure, the lightweight application card parameters being used to be recognized by an iOS operating system in the lightweight application card manner, the domain name information being used by the user terminal device to launch an application corresponding to the domain name information, and the application being used to execute a service process corresponding to the URL.

[0009] One or more embodiments herein provide a user terminal device including at least one processor and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, and the instructions, when executed by the at least one processor, can perform the following operations: acquire, in a near field communication manner, a uniform resource locator (URL) provided by an NFC tag device, the URL including protocol type information, domain name information, and lightweight application card parameters, the protocol type information indicating that the URL conforms to Hypertext Transfer Protocol Secure, and the lightweight application card parameters being used for recognition by an iOS operating system in the lightweight application card manner; and launch an application corresponding to the domain name information, the application being configured to execute a service process corresponding to the URL.

[0010] One or more embodiments herein provide an NFC tag device including at least one processor and a memory communicatively coupled to the at least one processor. The memory stores instructions executable by the at least one processor, and the instructions, when executed by the at least one processor, cause the at least one processor to receive a near field communication signal transmitted by a user terminal device and, in response to the near field communication signal, transmit a uniform resource locator (URL) to the user terminal device via a near field communication scheme, the URL including protocol type information, domain name information, and lightweight application card parameters, the protocol type information indicating that the URL complies with Hypertext Transfer Protocol Secure, the lightweight application card parameters being used to be recognized by an iOS operating system via the lightweight application card scheme, the domain name information being used by the user terminal device to launch an application corresponding to the domain name information, and the application being used to execute a service process corresponding to the URL.

[0011] At least one embodiment of the present specification can achieve the following beneficial effects: Because the URL transmitted based on the near field communication scheme includes protocol type information conforming to the Hypertext Transfer Protocol Secure and includes lightweight application card parameters that can be used to be recognized by the iOS operating system by using the lightweight application card scheme, the URL transmitted based on the near field communication scheme can be recognized by multiple operating systems, including but not limited to the iOS operating system, and the success rate of calling an app on a device of each operating system can be greatly improved based on the fact that the URL can be identified by multiple operating systems, thereby further improving the success rate of service execution.

[0012] In order to more clearly describe the technical solutions in one or more embodiments of this specification or the prior art, the following will briefly describe the accompanying drawings needed to describe one or more embodiments or the prior art. Obviously, the accompanying drawings in the following description only show some embodiments of the present application, and those skilled in the art can still derive other accompanying drawings from these accompanying drawings without creative work. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a schematic diagram illustrating an application scenario of an NFC-based service execution method according to one or more embodiments herein. [Figure 2] 1 is a schematic flowchart illustrating an NFC-based service execution method, according to one or more embodiments herein. [Figure 3] 1 is a schematic structural diagram illustrating a URL according to one or more embodiments of the present specification. [Figure 4] FIG. 1 is a schematic diagram illustrating a case in which a target application is launched, according to one or more embodiments of the present disclosure. [Figure 5] FIG. 1 is a schematic diagram illustrating a first predetermined page according to one or more embodiments herein. [Figure 6] 1 is a schematic diagram illustrating a display page including a banner page element, in accordance with one or more embodiments of the present disclosure. [Figure 7] 1 is a schematic diagram illustrating a lightweight application card according to one or more embodiments herein. [Figure 8] 1 is a schematic diagram illustrating a lightweight application page in accordance with one or more embodiments of the present disclosure. [Figure 9] 1 is a schematic flowchart illustrating another NFC-based service execution method, according to one or more embodiments herein. [Figure 10] 10 is a schematic swim-lane flowchart illustrating an NFC-based service execution method corresponding to FIGS. 2 and 9, in accordance with one or more embodiments herein. [Figure 11] 10 is another schematic swim-lane flowchart illustrating an NFC-based service execution method corresponding to FIGS. 2 and 9, in accordance with one or more embodiments herein. [Figure 12] 3 is a schematic structural diagram illustrating an NFC-based service execution device corresponding to FIG. 2, according to one or more embodiments of the present disclosure. [Figure 13] 10 is a schematic structural diagram illustrating an NFC-based service execution device corresponding to FIG. 9, according to one or more embodiments of the present disclosure. [Figure 14] 3 is a schematic structural diagram illustrating an NFC-based service execution device corresponding to FIG. 2 according to one or more embodiments of the present specification. [Figure 15] FIG. 10 is a schematic structural diagram illustrating an NFC-based service execution device corresponding to FIG. 9, according to one or more embodiments of the present specification. DETAILED DESCRIPTION OF THE INVENTION

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

[0015] To facilitate understanding of the technical solutions of one or more embodiments of the present specification, some nouns are explained: NFC: A short-range wireless communication technology that enables data exchange between devices that support NFC, which is based on radio frequency identification (RFID) technology and operates at a frequency of 13.56 MHz, with a communication distance typically within 10 centimeters.

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

[0017] App invocation: This refers to launching an application on a mobile device or activating an application through some trigger mechanism.

[0018] Programming: This refers to the process of writing software, firmware, or data onto a storage medium within an electronic device or machine.

[0019] In the prior art, when a mobile terminal application is launched based on NFC technology, the app call is usually performed based on a conventional URL protocol. The conventional URL protocol can be Alipay, Alipays, or another type of protocol. However, during an app call based on the conventional URL protocol, if the operating system of the mobile terminal is the iOS system, if the mobile terminal is in a locked screen state or if the mobile terminal is unlocked within two seconds, the protection mechanism included in the iOS operating system prevents the mobile terminal from recognizing the conventional URL protocol, and the app call task for the mobile terminal application fails. As a result, the existing technology has a low success rate for app calls performed by a mobile terminal application using NFC technology.

[0020] The following describes in detail the technical solutions provided in the embodiments of this specification with reference to the accompanying drawings.

[0021] FIG. 1 is a schematic diagram illustrating an application scenario of an NFC-based service execution method according to one or more embodiments herein.

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

[0023] In one or more embodiments herein, an initiating device is a device that actively initiates communication and is responsible for generating a radio frequency field to start the NFC communication process. An initiating device may include, but is not limited to, a smartphone, a tablet computer, a notebook computer, a desktop computer, an intelligent interaction device, or another device capable of actively transmitting NFC signals, and initiating device 101 is any of the initiating devices.

[0024] A target device is a passive, responsive device that exchanges data in response to a request from an initiating device. A target device can include, but is not limited to, an NFC tag, a smart card, an access card, a payment terminal, or another smart device, and target device 102 can be any of the target devices.

[0025] The initiating device interacts with the target device by transmitting commands and data, and the target device performs energy supply and data transmission based on the radio frequency field generated by the initiating device.

[0026] 2 is a schematic flowchart illustrating an NFC-based service execution method according to one or more embodiments of the present disclosure. From a software perspective, the process may be implemented by a program or application client device installed on a user terminal device having NFC capabilities. From a hardware perspective, the process may be implemented by a user terminal device having NFC capabilities.

[0027] As shown in FIG. 2, the method may include the following steps.

[0028] Step 202: The operating system acquires a uniform resource locator (URL) provided by the NFC tag device in a near field communication manner, where the URL includes protocol type information, domain name information, and lightweight application card parameters, where the protocol type information indicates that the URL complies with Hypertext Transfer Protocol Secure, and the lightweight application card parameters are used to be recognized by the iOS operating system in the lightweight application card manner.

[0029] In one or more embodiments herein, the operating system may be any of the Android operating system, the HarmonyOS operating system, or the iOS operating system, or the operating system may be any operating system running on a device with NFC capabilities, and there is no specific limitation on the type of operating system.

[0030] In one or more embodiments of the present specification, the terminal device on which the operating system is located may hereinafter be collectively referred to as a user terminal device. By using a near field communication method, a communication connection is established between the user terminal device and the NFC tag device, and the NFC tag device sends a URL to the user terminal device based on the established communication connection. The URL may be a URL pre-stored by a developer on the NFC tag device, or a URL generated in real time in response to a request from an actual operator.

[0031] In one or more embodiments herein, a URL may include protocol type information, domain name information, path information, query parameter information, etc. The protocol in the URL may be Hypertext Transfer Protocol (HTTP) or Hypertext Transfer Protocol Secure (HTTPS). The domain name information is used to determine the application corresponding to the URL. Hereinafter, the applications corresponding to the URL are collectively referred to as target applications.

[0032] To facilitate understanding of this approach by those skilled in the art, a specific example of a URL is provided in one or more embodiments herein.

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

[0034] Furthermore, in the service parameter information corresponding to the second query parameter, "CCC" can represent scenario type information included at the specified position of the URL, and "VALUE" can represent an information identifier included at the specified position of the URL, or a combination of an information identifier and amount information included at the specified position of the URL. Information other than "CCC" and "VALUE" in the service parameter information is specified format information, and the application receiving the URL can extract "CCC" and "VALUE" based on recognizing the format information.

[0035] In the example URL, AAA, BBB, CCC, and VALUE are merely schematic symbols used to indicate the location of the corresponding information. In reality, AAA, BBB, CCC, and VALUE in the URL may be actual character strings. For example, in the specific example URL "https: / / ulink.alipay.com / snxxx?s=nfc&scheme=alipay%1A2B3c4d%1A2B3c4dsn%5e6F1q2w3e4r5t6y7u8i", the character string "snxxx" corresponds to the path "AAA" in the example of FIG. 3, the character string "nfc" corresponds to the value "BBB" of the first query parameter s in the example of FIG. 3, the character string "sn" corresponds to the scenario type information "CCC" in the example of FIG. 3, and the character string "1q2w3e4r5t6y7u8i" corresponds to the information identifier "VALUE" in the example of FIG. 3.

[0036] In addition, 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 service parameter information corresponding to the second query parameter, and the overall structure of the URL may be predetermined information that should not be changed for a certain period of time and does not change with each communication, so that multiple terminals such as operating systems, operating system servers, application programs, and application servers can recognize and process the information for the received URL based on predetermined settings. Alternatively, the above-mentioned agreed-upon information may be changed during software updates, program updates, etc. For example, the domain name may be changed from ulink.alipay.com to render.alipay.com. When this change occurs, synchronized updates must be performed on the terminals that need to consume this information, among multiple terminals such as operating systems, operating system servers, application programs, and application servers.

[0037] In one or more embodiments herein, the iOS version 14 or later operating system has a lightweight application function that allows users to quickly use applications without downloading and installing a complete application program, i.e., a lightweight application function that runs on the operating system. Therefore, to accommodate the lightweight application function of iOS version 14 or later, a URL transmitted based on the NFC method may include a lightweight application card parameter that is used to be recognized by the iOS operating system using the lightweight application card method. After recognizing the lightweight application card parameter in the URL, the iOS operating system triggers the lightweight application function of the iOS operating system and further displays a corresponding lightweight application card based on the lightweight application function, thereby improving the success rate of app invocation in the iOS operating system.

[0038] Optionally, the lightweight application card parameters may be included in the path information of the URL.

[0039] Step 204: Start an application corresponding to the domain name information, and the application is used to execute a service process corresponding to the URL.

[0040] In one or more embodiments herein, if the target application is already installed in the operating system, the operating system can launch the target application based on the acquired URL, and the launched target application performs a corresponding service process based on query parameter information in the URL. If the target application is not installed in the operating system, the operating system can open an application page corresponding to the URL, and the user can complete the subsequent service process based on information displayed on the opened application page.

[0041] It should be understood that the sequence of some of the steps of the methods described in one or more embodiments herein may be interchanged based on actual needs, or some of the steps may be omitted or deleted.

[0042] In the method of FIG. 2 , the URL sent based on NFC can also be recognized by the iOS operating system based on being recognized by the Android system and the HarmonyOS system, so that in a scenario where an app call is performed based on NFC, the app call can also be successfully performed on a device with an iOS operating system, thereby significantly increasing the success rate of app calls on devices with an iOS operating system while improving the overall success rate of app calls across multiple user devices.

[0043] Based on the method of FIG. 2, one or more embodiments herein further provide several specific implementations of the method, as described below.

[0044] In one or more embodiments herein, one or more embodiments are provided for a process by which an operating system performs an app call based on a URL.

[0045] Optionally, in one or more embodiments herein, starting an application corresponding to the domain name information may include, inter alia, determining an application corresponding to the URL based on the domain name information, determining whether the application is already installed in the operating system to obtain a determination result, and starting the application if the determination result indicates that the application is already installed in the operating system.

[0046] In one or more embodiments of the present specification, the domain name information may be information designed by a developer of an application program to determine a corresponding application. In addition, the domain name information corresponding to the application may be correspondingly pre-registered on the World Wide Web. Therefore, the corresponding application may be determined based on the domain name information.

[0047] In one or more embodiments herein, after obtaining the URL sent by the NFC tag device, the operating system can determine a target application corresponding to the URL based on domain name information in the URL. The operating system determines whether the target application is already installed in the operating system based on the determined target application and various applications already installed in the operating system, and starts the target application if it determines that the target application is already installed in the operating system.

[0048] Optionally, for example, the target application is Alipay. For a payment scenario, the page obtained after the target application is enabled may be shown in FIG. 4. The information shown in FIG. 4 is only an example. In practice, information different from the information shown in FIG. 4 may be displayed. Specifically, information such as other text, images, videos, and operation means may be displayed, and there is no specific restriction on the information shown in FIG. 4.

[0049] In one or more embodiments herein, if it is determined that the target application is not installed in the operating system, the operating system may display a page corresponding to the URL. Optionally, to obtain a determination result, after determining whether the application is already installed in the operating system, the method may further include, if the determination result indicates that the application is not installed in the operating system, acquiring first predetermined page information corresponding to the URL from an application server of the application based on the URL, and displaying the first predetermined page generated based on the first predetermined page information, wherein the first predetermined page includes a first download operation means used to provide a prompt to instruct the user to download the application.

[0050] In one or more embodiments herein, the URL obtained by the operating system may be a resource address used to identify and locate a resource. Therefore, after it is determined that the target application is not installed in the operating system, first predetermined page information corresponding to the URL may be obtained from the server of the target application based on the URL, and the corresponding first predetermined page may be generated based on the first predetermined page information. The first predetermined page information may include all information for generating the first predetermined page, for example, but is not limited to, image information, title information, subtitle information, operation means information, etc. The first predetermined page may include a first download operation means, and the download and installation process for the target application may be triggered after a user performs a triggering operation on the first download operation means.

[0051] Optionally, for example, the target application is Alipay. The first predetermined page generated may be as shown in FIG. 5. In FIG. 5, the first download operation means 10 is a "download Alipay" operation means. The information shown in FIG. 5 is only an example. In practice, information different from that shown in FIG. 5 may be displayed. Specifically, information such as other text, images, videos, and operation means may be displayed, and there is no specific restriction on the information shown in FIG. 5.

[0052] In one or more embodiments herein, after it is determined that the target application is already installed on the operating system, the target application may be directly launched to enhance the user experience, or when it is determined that the target application is not installed on the operating system, a first predetermined page may be displayed to the user to provide a prompt instructing the user to download the target application to increase user usage of the target application.

[0053] In order to improve the user experience, after obtaining the URL in the NFC tag device in the NFC manner, the operating system can pre-generate prompt information used to provide a prompt to indicate to the user whether the user needs to access the target application, so that the target application can only be started after approval is obtained from the user, thereby avoiding bothering the user when the user does not need to open the target application.

[0054] Optionally, after determining whether the application is already installed in the operating system, the method may further include the steps of displaying a banner page element, the banner page element including information used to provide a prompt to access the application, and obtaining a first trigger action of the user on the banner page element.

[0055] Determining whether the application is already installed on the operating system may particularly include determining whether the application is already installed on the operating system in response to the first triggering action.

[0056] In one or more embodiments herein, after determining the target application based on the domain name information in the URL, the operating system can display a banner page element in the current interface in which the operating system is running, and the banner page element can include prompt information used to provide a prompt indicating to the user whether the user needs to access the application program. The banner page element can be displayed in any of the upper, lower, and middle regions of the visible area in the current interface, or the banner page element can be displayed in any region of the visible area in the current interface, and there is no specific restriction on the display position of the banner page element.

[0057] Optionally, for example, the target application is Alipay. A display page including a banner page element may be as shown in Fig. 6. The banner page element 20 is located in the upper region of the visible area of ​​Fig. 6. The information shown in Fig. 6 is only an example. In practice, information different from the information shown in Fig. 6 may be displayed. Specifically, information such as other text, images, videos, and operation means may be displayed, and there is no specific restriction on the information shown in Fig. 6.

[0058] In one or more embodiments herein, when the operating system obtains a first user action on the banner page element within a predetermined time, the first action may be a user click action on a predetermined operating means in the banner page element or a user click action on a random position in the banner page element. In response to the user's first action, a process is performed to determine whether a target application is already installed in the operating system, and if it is determined that the target application is already installed in the operating system, the target application is launched, or if it is determined that the target application is not installed in the operating system, a target page is displayed to provide a prompt instructing the user to download the target application.

[0059] In one or more embodiments herein, if the operating system does not obtain a first user interaction with the banner page element within a predetermined time, the display of the banner page element is stopped.

[0060] Based on the above-mentioned embodiments, in one or more embodiments of the present specification, the operating system may include an iOS operating system having a lightweight application function, and determining whether the application is already installed in the operating system may further include: obtaining lightweight application card information corresponding to the lightweight application card parameters based on the lightweight application card parameters; displaying a lightweight application card generated based on the lightweight application card information, wherein the lightweight application card includes an application access operation means, and the application access operation means is used to provide a prompt instructing the user to access the application; and obtaining a second trigger action for the application access operation means.

[0061] Determining whether the application is already installed on the operating system may specifically include determining whether the application is already installed on the operating system in response to the second triggering action.

[0062] In one or more embodiments herein, the operating system may include an iOS operating system with lightweight application capabilities, and specifically may be an operating system of iOS version 14 or higher. The lightweight application may be an application program that runs on the operating system and can be used without being downloaded, for example, the app Clips that runs on the iOS operating system.

[0063] In one or more embodiments herein, obtaining lightweight application card information corresponding to the lightweight application card parameters based on the lightweight application card parameters may particularly include obtaining lightweight application card information corresponding to the lightweight application card parameters from a system server corresponding to an operating system based on the lightweight application card parameters. The lightweight application card information may include image information, title information, subtitle information, operation means information, etc. Different service scenarios may correspond to different lightweight application card parameters, and the lightweight application card information corresponding to the lightweight application card parameters may be different. For example, the lightweight application card parameters corresponding to a payment scenario are different from the lightweight application card parameters corresponding to a door-opening scenario, and the lightweight application card parameters corresponding to the payment scenario are also different from the lightweight application card parameters corresponding to a service machine water sales business scenario.

[0064] In one or more embodiments herein, the lightweight application card information may be pre-registered in a system server corresponding to the operating system by a developer of the application corresponding to the lightweight application card information. For example, if the developer intends to display the payment scenario of the target application as an image of interface A in the payment scenario of the target application, the developer may pre-register information about the image of interface A in the system server corresponding to the operating system to inform the system server to display the payment scenario of the target application as an image of interface A. In addition, the developer may also add parameters related to displaying the payment scenario of the target application as an image of interface A to the corresponding URL. After acquiring the URL, the operating system may parse the lightweight application card parameters for interface A and obtain corresponding lightweight application card information from the system server based on the lightweight application card parameters. The lightweight application card may further be generated based on the lightweight application card information and displayed to the user. The lightweight application card may include the title of the target application and an application access operation means corresponding to the target application. The user can access the corresponding target application through the application access operation means.

[0065] Optionally, for example, the target application is Alipay. The generated lightweight application card for a payment scenario may be as shown in Fig. 7. In Fig. 7, the application access operation means 30 is an "open" operation means. The information shown in Fig. 7 is only an example. In practice, information different from the information shown in Fig. 7 may be displayed. Specifically, information such as other text, images, videos, and operation means may be displayed, and there is no specific restriction on the information shown in Fig. 7.

[0066] In one or more embodiments herein, after obtaining a second user trigger action on the application access operation means within a predetermined time, in response to the second trigger action, the operating system performs a process to determine whether the target application is already installed in the operating system, and if it determines that the target application is already installed in the operating system, launches the target application.

[0067] In one or more embodiments herein, if the operating system does not receive a second user trigger action on the application access operation means within a predetermined time, the operating system stops displaying the lightweight application card.

[0068] Optionally, the URL may also include a lightweight application page parameter, and determining whether the application is already installed in the operating system may further include: obtaining lightweight application page information corresponding to the lightweight application page parameter based on the lightweight application page parameter if the determination result indicates that the application is not installed in the operating system; and displaying a lightweight application page generated based on the lightweight application page information in a lightweight application corresponding to the lightweight application card, wherein the lightweight application page includes a second download operation means used to provide a prompt to instruct the user to download the application.

[0069] In one or more embodiments herein, the lightweight application page parameter may be included in the query parameter information of the URL. Specifically, as shown in Figure 3, the lightweight application page parameter may be a parameter value corresponding to the first query parameter in the URL, such as a parameter value corresponding to parameter s.

[0070] In one or more embodiments herein, in response to the second triggering operation, a process for determining whether the target application is already installed in the operating system is performed. If it is determined that the target application is not installed in the operating system, lightweight application page information corresponding to the lightweight application page parameter is obtained based on the lightweight application page parameter. Specifically, based on the lightweight application page parameter, the lightweight application page information corresponding to the lightweight application page parameter is obtained from a system server corresponding to the operating system. The lightweight application page information may include image information, title information, subtitle information, operation means information, etc.

[0071] In one or more embodiments herein, the lightweight application page information may be information that has been pre-registered in a system server corresponding to the operating system by a developer of an application corresponding to the lightweight application page information.

[0072] In one or more embodiments of the present disclosure, the operating system may generate a corresponding lightweight application page based on the acquired lightweight application page information and display the lightweight application page in the lightweight application corresponding to the lightweight application card. The lightweight application page may include a second download operation means used to provide a prompt to instruct the user to download the target application. The download and installation process for the target application may be triggered after the user clicks on the second download operation means.

[0073] Optionally, for example, the target application is Alipay. The generated lightweight application page may be as shown in FIG. 8. The second download operation means 40 is a "download" operation means. The information shown in FIG. 8 is only an example. In practice, information different from the information shown in FIG. 8 may be displayed. Specifically, information such as other text, images, videos, and operation means may be displayed, and there is no specific restriction on the information shown in FIG. 8.

[0074] Based on the embodiments mentioned above, in one or more embodiments herein, the lightweight application page may further include a service operation means used to instruct the execution of a service process, and displaying the lightweight application page generated based on the lightweight application page information may further include obtaining a third trigger action of the user on the service operation means, and highlighting a second download control in response to the third trigger action.

[0075] In one or more embodiments of the present application, the service operation means may be an operation means used to provide a prompt to instruct the user to make a payment, or may be an operation means used to provide a prompt to indicate to the user to experience the target application. After the user's third triggering action on the service operation means is obtained, in response to the third triggering action, the second download operation means is highlighted to instruct the user to download and install the target application, thereby enhancing the convenience of the user in downloading and installing the target application and thereby further increasing the user's usage of the target application.

[0076] In one or more embodiments herein, one or more embodiments are also provided for a process in which a target application performs a service based on a URL.

[0077] Optionally, after launching the application corresponding to the domain name information, the method may further include a step of sending a URL to the application, where the URL may further include service parameter information, and the service parameter information is used as a basis used by the application to execute the service process corresponding to the URL.

[0078] In one or more embodiments of the present application, the service parameter information may be included in the query parameter information of the URL.

[0079] Optionally, as shown in FIG. 3, the service parameter information may be a parameter value corresponding to a second query parameter in the URL, for example, a parameter value corresponding to a parameter scheme.

[0080] In one or more embodiments herein, after the operating system determines that the target application is already installed in the operating system and launches the target application, the operating system sends a URL to the target application, and the target application performs a subsequent service process based on the service parameter information in the URL.

[0081] Based on the embodiments mentioned above, in one or more embodiments herein, the service parameter information may include scenario type information and an information identifier corresponding to the scenario type information, and the information identifier is used as a basis for querying the service description information.

[0082] After sending the URL to the application, the method may further include a step of querying by the application based on the scenario type information a URL template having a correspondence relationship with the scenario type information, wherein the URL template includes a replaceable mark, and the replaceable mark is used to identify a location where the information identifier can be input; a step of replacing the replaceable mark with the information identifier to obtain a service URL including the information identifier; and a step of performing a service process based on the service URL.

[0083] In one or more embodiments herein, scenario type information is used to reflect a specific implementation scenario used when a service is implemented, and service scenarios may include a payment scenario, a door-opening scenario, a food ordering scenario, a water vending scenario, etc. Optionally, the information identifier may be identification data generated based on service data generated when a service is implemented, such as identification data generated based on an order number or a merchant number. The information identifier may be encrypted identification data, which enhances the security of the service data. Optionally, the information identifier may be a random string. The generated information identifier and the service description information corresponding to the information identifier may be correspondingly stored in the application server, so that the service description information can be queried based on the information identifier when it needs to be used later.

[0084] In one or more embodiments herein, a mapping relationship may be pre-established between the scenario type information and the URL template, specifically, a mapping relationship in the form of a key-value pair may be established, where the scenario type information may be the key value and the URL template may be the value of the value.

[0085] To facilitate understanding of this approach by those skilled in the art, a specific example of converting a URL to a service URL is provided in one or more embodiments herein.

[0086] Assume the URL obtained by the operating system from the NFC tag device is: https: / / ulink.alipay.com / snxxx?s=nfc&scheme=alipay%1A2B3c4d%1A2B3c4dsn%5e6F1q2w3e4r5t6y7u8i

[0087] The service parameter information in the URL is the parameter value corresponding to the parameter scheme, the scenario type information is “sn” in the parameter value corresponding to the parameter scheme, and the information identifier is “1q2w3e4r5t6y7u8i” in the parameter value corresponding to the parameter scheme.

[0088] Based on the pre-established correspondence relationship between the scenario type information and the URL template, the URL template corresponding to "sn" is identified as alipays: / / platformapi / startApp?appId=112233&appScheme=NFC_ABC&pageParams=%12345q wert$[value]$%6789. The replaceable mark in the URL template is $[value]$.

[0089] The service URL obtained by replacing the replaceable mark $[value]$ in the URL template with the information identifier "1q2w3e4r5t6y7u8i" in the URL is as follows: alipays: / / platformapi / startApp?appId=112233&appScheme=NFC_ABC&pageParams=%12345q wert1q2w3e4r5t6y7u8i%6789

[0090] In one or more embodiments herein, a service URL used to execute a service process may be generated based on a URL transmitted between the user terminal device and the NFC tag device, so that the service URL used to execute the service process does not need to be transmitted between the user terminal device and the NFC tag device. Using such a setting, on the one hand, the risk of the service URL being leaked can be avoided and the confidentiality of the service URL can be improved. On the other hand, since the data amount of the URL is smaller than the data amount of the service URL, the amount of data transmitted between the user terminal device and the NFC tag device can be further reduced, thereby improving the efficiency of NFC communication and further improving the user experience.

[0091] Based on the above-mentioned embodiments, in one or more embodiments herein, the service URL includes rendering parameter information used to render the first application page, the information identifier is included in the rendering parameter information, and performing a service process based on the service URL may include, among other things, rendering the first application page based on the rendering parameter information.

[0092] In one or more embodiments of the present specification, a payment scenario is used as an example. Assume that the converted service URL is alipays: / / platformapi / startApp?appId=112233&appScheme=NFC_ABC&pageParams=%12345q wert$1q2w3e4r5t6y7u8i$%6789. The three parameters appid, appscheme, and pageparams in the converted service URL are all rendering parameters, and the corresponding parameter values ​​are all rendering parameter information.

[0093] In practice, the first application page may be rendered based on the rendering parameter information in the service URL, and the first application page may be an app calling landing page displayed to the user after the service process is started based on the NFC method, and may also be called the first page displayed to the user.

[0094] Based on the above-mentioned embodiments, in one or more embodiments of the present specification, the first application page may include a predetermined operation means, and rendering the first application page based on the rendering parameter information may further include: sending a service request to an application server of the application in response to a user's trigger action on the predetermined operation means, wherein the service request includes an information identifier; receiving service processing result information determined by the application server in response to the service request, wherein the service processing result information is determined by the application server based on service description information, and the service description information is obtained through a query by the application server based on the information identifier; and displaying a second application page generated based on the service processing result information.

[0095] Optionally, the information identifier included in the service URL may be information generated by the application server.

[0096] Optionally, the information identifier may be a token obtained by the application server by performing processing based on at least a portion of the information in the service description information by using predetermined information processing rules.

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

[0098] In practice, after the information identifier is generated, the information identifier may be stored in association with the corresponding service description information, and the information identifier is used as a query index for the service description information.

[0099] Optionally, the URL acquisition request may be sent by the NFC tag device to an application server, which then generates a URL and returns the URL to the NFC tag device.

[0100] In one or more embodiments herein, the first application page may include a predetermined operation means, which may be any of an input operation means, a button operation means, a selection operation means, and a multimedia operation means. If the target application receives a user's touch action on the predetermined operation means within a predetermined time, the target application responds to the touch action by sending a service request to an application server of the target application, the server request including an information identifier. The application server responds to the service request, analyzes the service request, obtains the information identifier included in the service request, and then uses the information identifier as a query index to identify service description information corresponding to the information identifier. The application server then determines corresponding service processing result information based on the service description information and sends the service processing result information to the target application. The target application generates a corresponding second application page, displays the second application page after receiving the service processing result information, and displays the second application page.

[0101] In one or more embodiments herein, the application server may perform process interactions with the target application multiple times in the process of determining the service processing result information, for example, in the process of decrypting the information identifier in the service URL, verifying the user's identity by using the target application, verifying the legitimacy of the service URL, and verifying the security of the service execution environment, and obtain related information that needs to be displayed on the second application page, etc.

[0102] In one or more embodiments herein, the second application page generated based on the service processing result information may include multiple types of pages. A payment scenario is used as an example. The second application page may be an application page displaying relevant information, such as "Payment successful." Alternatively, the second application page may be an application page displaying relevant information, such as a specific payment amount. If the user has opened the secret payment function, the user can directly click the payment button on the second application page to complete the payment. Alternatively, if the user has not opened the secret payment function, the second application page may redirect the user to a third application page after clicking the payment button on the second application page, and the user can enter the correct password on the third application page to complete the payment. Alternatively, the second application page may be an application page displaying a corresponding window in which the user needs to input the payment amount. If the user has opened the secret payment function, the user can directly click the corresponding payment button on the second application page to complete the payment. Alternatively, if the user has not opened the secret payment function, after the user enters the corresponding payment amount on the second application page and clicks the payment button corresponding to the payment amount, the second application page can redirect to the fourth application page, and the user can enter the correct password on the fourth application page to complete the payment.

[0103] Optionally, in a payment scenario, the service parameter information further includes amount information corresponding to the scenario type information. The amount information can be included in the rendering parameter information after being joined with the information identifier, and the first application page can further include a payment amount corresponding to the amount information.

[0104] Specifically, when the service parameter information includes both an information identifier and amount information, the information identifier and amount information may be joined by using a fixed character (e.g., _), and then in the subsequent process of URL conversion, both the amount information and the information identifier are put into the service URL after conversion.

[0105] In one or more embodiments herein, in a payment service scenario, the payment amount may be input by a merchant using service parameters including amount information to obtain a corresponding information identifier generated based on the payment amount, so that the rendering parameter information in the service URL may include the payment amount. A first application page rendered based on the rendering parameter information may include the payment amount input by the merchant. If the user has opened the secret payment function, the user can directly click a payment button in the first application page to complete the payment. Alternatively, if the user has not opened the secret payment function, the first application page may redirect the user to a fifth application page after clicking the payment button in the first application page, and the user can enter a correct password on the fifth application page to complete the payment.

[0106] In one or more embodiments herein, the amount information is included in the service parameter information through plain text information and further included in the service URL. Therefore, when acquiring the service URL, the user terminal device can display the payment amount corresponding to the amount information on the rendered first application page based on the plain text amount information in the service URL. In other words, it allows the user to view the amount to be paid on the app calling landing page, thereby improving the user's payment experience. Optionally, the payment amount can be displayed on the first application page when the amount information includes the payment amount. Optionally, when the payment amount is not included in the amount information, for example, only a character (e.g., n) used to represent that no payment amount is provided is included, and the payment amount is not displayed on the first application page.

[0107] To facilitate understanding of this approach by those skilled in the art, a specific example of converting a URL into a service URL when monetary information is included is provided in one or more embodiments of this specification.

[0108] Assume that the URL obtained by the operating system from the NFC tag device is: https: / / ulink.alipay.com / snxxx?s=nfc&scheme=alipay%1A2B3c4d%1A2B3c4dsn%5e6F1q2w3e4r5t6y7u8i_0.1

[0109] The service parameter information in the URL is the parameter value corresponding to the parameter scheme, the scenario type information is "sn" in the parameter value corresponding to the parameter scheme, and the information identifier and amount information is "1q2w3e4r5t6y7u8i_0.1" in the parameter value corresponding to the parameter scheme.

[0110] Based on the pre-established correspondence relationship between the scenario type information and the URL template, the URL template corresponding to "sn" is identified as alipays: / / platformapi / startApp?appId=112233&appScheme=NFC_ABC&pageParams=%12345qwert$[value]$%6789. The replaceable mark in the URL template is $[value]$.

[0111] The service URL obtained by replacing the replaceable mark $[value]$ in the URL template with the information identifier and amount information “1q2w3e4r5t6y7u8i_0.1” in the URL is alipays: / / platformapi / startApp?appId=112233&appScheme=NFC_ABC&pageParams=%12345qwert1q2w3e4r5t6y7u8i_0.1%6789.

[0112] In this example, the amount to be paid of "0.1" may be displayed to the user on the first application page where the app call landing is performed.

[0113] Based on the embodiments mentioned above, in one or more embodiments herein, there are also cases where the query fails when querying a URL template based on scenario type information.

[0114] Optionally, after the application queries a URL template having a correspondence relationship with the scenario type information based on the scenario type information, the method may further include a step of obtaining a home page URL of the application if a URL template having a correspondence relationship with the scenario type information is not identified, and a step of displaying a home page of the application based on the home page URL.

[0115] In one or more embodiments herein, the home page URL of an application may be pre-stored in the application client device, and if a URL template having a corresponding relationship is not identified based on the service type information in the service URL, the application can directly display the home page of the application based on the pre-stored home page URL in the client device. Such a setting can speed up the display of the home page of the application. If the home page URL is not pre-stored in the application client device and a URL template having a corresponding relationship is not identified, the application can generate a fetch request used to fetch the home page URL and send the fetch request to the application server. The application server sends the home page URL to the application client device in response to the fetch request, and the application displays the home page of the application based on the received home page URL. Such a setting can reduce the utilization of storage resources in the application client device.

[0116] In one or more embodiments herein, if an application is unable to find specific service information or is unable to find the application page that needs to be displayed, the application's home page may be displayed to the user to minimize the user's negative experience on the application.

[0117] Optionally, when the scenario represented by the scenario type information is a specified service scenario, the application may access a page corresponding to the specified service URL. Based on this, the service parameter information may include scenario type information and a specified service URL corresponding to the scenario type information, and after sending the URL to the application, the method may further include: when a value of the scenario type information is the specified parameter, the application acquires, based on the specified service URL, specified page information corresponding to the specified service URL from a specified server corresponding to the specified service URL, and displays the specified page generated based on the specified page information.

[0118] In one or more embodiments herein, the service parameter information in the URL and acquired by the operating system from the NFC tag device may include scenario type information and a designated service URL corresponding to the scenario type information. After acquiring the URL, if the scenario type information in the service parameter information is determined to be a designated parameter, the target application does not need to query a URL module having a correspondence relationship with the scenario type information, and can display a designated page determined based on the designated service URL.

[0119] In one or more embodiments herein, the application corresponding to the specified service URL is a different application from the target application, and the server corresponding to the specified service URL is a different server from the server of the target application. A payment scenario is used as an example. The target application may be Alipay. The application corresponding to the specified service URL may be another application, such as an applet application, and the specified page displayed may not be the native Alipay page, but a different page of the applet opened on the Alipay application page. The server corresponding to the specified service URL may be a server on the merchant's side or a server on another side, such as a third party's side. The specified service URL may be a URL specified by the merchant, and the protocol type of the specified service URL may be any of http, https, Alipay, or Alipays.

[0120] In one or more embodiments herein, a specified page of another application may be opened in the target application based on a user's request, allowing the user more autonomy in the choice, thereby improving the user's experience with the target application.

[0121] Optionally, the application comprises a payment application and the service process comprises a payment process.

[0122] Based on the same idea as the approach shown in Fig. 2, one or more embodiments herein further provide another NFC-based service execution method. Fig. 9 is a schematic flowchart illustrating another NFC-based service execution method according to one or more embodiments herein. From a software perspective, the process may be implemented by a program or application client device installed in an NFC tag device. From a hardware perspective, the process may be implemented by an NFC tag device. As shown in Fig. 9, the process may include: Step 902: Receive a near field communication signal transmitted by a user terminal device.

[0123] In one or more embodiments herein, a user terminal device may be used as an NFC reader, and when the user terminal is near an NFC tag device, the user terminal device sends an acquisition request to the NFC tag device by using a method of transmitting a near field communication signal, and the acquisition request is used to request to acquire a URL from the NFC tag device.

[0124] Step 904: In response to the near field communication signal, send a uniform resource locator (URL) to the user terminal device via a near field communication method, where the URL includes protocol type information, domain name information, and lightweight application card parameters, where the protocol type information indicates that the URL complies with Hypertext Transfer Protocol Secure, the lightweight application card parameters are used to be recognized by the iOS operating system via the lightweight application card method, the domain name information is used by the user terminal device to launch an application corresponding to the domain name information, and the application is used to execute a service process corresponding to the URL.

[0125] In one or more embodiments herein, the NFC tag device responds to a near field communication signal by using a near field communication scheme to send a URL to a user terminal device based on the received near field communication signal. The URL may include protocol type information, domain name information, port information, path information, query parameter information, etc. The protocol in the URL may be Hypertext Transfer Protocol (HTTP) or Hypertext Transfer Protocol Secure (HTTPS). The domain name information is used to determine the target application to which the URL corresponds. After being started, the target application can implement a service process corresponding to the URL based on the URL.

[0126] In one or more embodiments of the present specification, the iOS operating system of version 14 or later has a lightweight application function, i.e., a lightweight application function that runs on the operating system, that allows users to quickly use applications without downloading and installing the entire application program. Therefore, to accommodate the lightweight application function of iOS version 14 or later, a URL transmitted based on the NFC method may include a lightweight application card parameter that is used to be recognized by the iOS operating system using the lightweight application card method. After recognizing the lightweight application card parameter in the URL, the iOS operating system triggers the lightweight application function of the iOS operating system and further displays a corresponding lightweight application card based on the lightweight application function, thereby improving the success rate of app invocation in the iOS operating system.

[0127] Optionally, the lightweight application card parameters may be included in the path information of the URL.

[0128] In one or more embodiments herein, the method for obtaining a URL in an NFC tag device may differ in different application scenarios. For example, in some vending scenarios, a URL may usually contain fixed information, so a URL containing the fixed information may be programmed into the NFC tag device. In another example, in some scenarios, a URL may contain service data related to a current service, such as a product order number, a user identifier, and an order amount. Thus, a corresponding URL may be generated in real time as the service occurs.

[0129] In the method of FIG. 9 , the URL sent based on NFC can also be recognized by the iOS operating system based on being recognized by the Android system and the HarmonyOS system, so in a scenario where an app call is performed based on NFC, the app call can also be successfully executed on a device with an iOS operating system, thereby significantly increasing the success rate of app calls on devices with an iOS operating system while improving the overall success rate of app calls on user group devices.

[0130] Based on the method of FIG. 9, one or more embodiments herein further provide some specific implementation strategies of the method, as described below.

[0131] Optionally, before receiving the near field communication signal transmitted by the user terminal device, the method may further include: acquiring a predetermined trigger action; acquiring first service information in response to the trigger action; sending a URL acquisition request to an application server, where the URL acquisition request includes the first service information; and receiving a URL returned by the application server, where the URL includes an information identifier, where the information identifier is used to query service description information, where the service description information includes the first service information and second service information, where the second service information includes information acquired by the application server and related to the service corresponding to the URL.

[0132] In one or more embodiments herein, the predetermined triggering action may be different for different service scenarios, such as a payment collection action initiated by a cashier, a payment collection action initiated in the water vending section of a service machine, a payment action initiated by a customer after selecting a product in a vending machine, or a payment action initiated by a user after making a purchase on an application program corresponding to a merchant.

[0133] In one or more embodiments herein, a payment scenario is used as an example, and the first service information may include information such as a product order number, a merchant identifier, an order occurrence time, and an order occurrence location, etc. The second service information may include information such as a URL occurrence time, a specific attribute of the URL, an expiration date of the URL, an identifier of the paying user, and a user's payment status.

[0134] In one or more embodiments herein, the information identifier may be a token generated by the application server based on the service description information.

[0135] Optionally, the application server can process at least a part of the service description information based on a predetermined information processing rule to obtain a token. The predetermined information processing rule can be different for each scenario. For example, in a payment scenario, a merchant number or an order number can be processed to obtain a token. In a service machine water vending scenario, a serial number (SN) can be joined with a process identifier (PID) to obtain a token. In a vending machine vending scenario, a vending machine number and a product identifier can be processed to obtain a token.

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

[0137] In one or more embodiments herein, when an application sends a service request to an application server based on the URL, the application server can store the information identifier in association with the service description information, so that the application server can identify service description information including the service information based on the information identifier and thereby further the service process. Such a setting can improve the security of the service information and make the URL shorter, thereby reducing the amount of data during the transmission of the URL.

[0138] It is worth noting that for a determined NFC tag device, the information identifier in the URL to be generated may vary, and if the URL to be generated further includes amount information, the amount information may also vary, while other information other than the amount information may be fixed. Specifically, information such as protocol type information, domain name information, lightweight application card parameters, lightweight application page parameters, and scenario type information in the URL to be generated may not be changed. In addition, when the URL to be generated includes a specified service URL, the specified service URL may also not be changed. In the URLs sent for all opportunities of near field wireless communication implemented for the NFC tag device, only the information identifier and amount information (if any) may be different among the URLs sent at different times.

[0139] Optionally, the triggering action may include a payment collection initiation action, the application may include a payment application, and the service process may include a payment process.

[0140] In one or more embodiments herein, in a payment service scenario, based on an NFC communication method between a user terminal device and an NFC tag device, payment is completed by a touch-and-go operation between the devices, without the user needing to operate a smartphone, for example, without the user needing to open a code-swiping device to scan a merchant's two-dimensional code, which can facilitate smooth payment for people who cannot use smartphones, such as the elderly, making payment more convenient for users, thereby improving the user experience in payment processing and further increasing user attachment to the target application.

[0141] A schematic swim-lane flowchart illustrating an NFC-based service execution method corresponding to FIGS. 2 and 9 is further provided in one or more embodiments herein.

[0142] As shown in FIG. 10, in the Android operating system or the HarmonyOS operating system, the NFC-based service execution process may include execution subjects such as a terminal device operating system, a target application, and a target application server.

[0143] In one or more embodiments of the present specification, the operating system of the terminal device acquires a URL by using an NFC short-range wireless communication method, determines a target application corresponding to the URL based on domain name information in the URL, determines whether the target application is already installed in the operating system, and if it determines that the target application is not installed in the operating system, opens an application download page corresponding to the URL by using a browser included in the operating system, where the application download page displays a download request operation means, and downloads the target application after obtaining a user's trigger action on the download request operation means; or if it determines that the target application is already installed in the operating system, invokes the target application and sends the URL to the target application, where the URL includes service parameter information, and the service parameter information includes scenario type information and an information identifier corresponding to the scenario type information.

[0144] After obtaining the URL, the target application pre-generates a correspondence relationship table based on the scenario type information in the URL through a query, identifies a URL template having a correspondence relationship with the scenario type information, replaces the replaceable mark in the identified URL template with an information identifier corresponding to the scenario type information, and obtains a service URL. A first application page (app calling landing page) is generated based on the rendering parameter information in the service URL, and the first application page includes a predetermined operation means. After obtaining a user's trigger action on the predetermined operation means, the target application sends a service request including the information identifier to an application server.

[0145] After receiving the service request sent by the target application, the target application server obtains service description information corresponding to the information identifier through a query based on the analysis operation of the information identifier included in the service request, then determines service processing result information based on the service description information, and sends the service processing result information to the target application, allowing the target application to display a second application page based on the service processing result information.

[0146] In some other operating systems, such as iOS version 13 or below, after determining the target application based on the domain name information in the URL, the terminal device operating system may further display pop-up information to prompt the user on whether to open the target application, and only after obtaining the user's action on the pop-up information performs the operation of determining whether the target application is already installed in the operating system.

[0147] As shown in FIG. 11, in an operating system of iOS version 14 or above, the NFC-based service execution process may include execution entities such as the operating system of the terminal device, an operating system server, a target application, and a target application server.

[0148] In one or more embodiments of the present disclosure, the terminal device operating system acquires a URL via a near-field communication (NFC) method, determines a target application corresponding to the URL based on domain name information in the URL, and sends lightweight application card parameters included in the path information in the URL to an operating system server. The operating system server identifies corresponding lightweight application card information based on the received lightweight application card parameters, where the lightweight application card information is related information pre-registered by the developer of the target application in the operating system server. After acquiring the lightweight application card information identified by the operating system server, the operating system generates a lightweight application card based on the lightweight application card information and displays the lightweight application card to a user. The lightweight application card includes a first operating means, and the first operating means is used to provide a prompt to the user indicating whether the user needs to open the target application. If the operating system acquires the user's trigger action on the first operating means, the operating system begins an operation to determine whether the target application is already installed in the operating system. If it is determined that the target application is not installed in the operating system, the operating system sends lightweight application page parameters included in the query parameter information of the URL to the operating system server, and the operating system server identifies corresponding lightweight application page information based on the received lightweight application page parameters, and the lightweight application page information is relevant information pre-registered by the developer of the target application in the operating system server.After obtaining the lightweight application page information identified by the operating system server, the operating system generates a lightweight application page based on the lightweight application page information and displays the lightweight application page to the user. The lightweight application page includes a second operating means, which is used to provide a prompt to the user indicating whether the user needs to download the target application. After obtaining a user's trigger action on the second operating means, the target application is downloaded. If it is determined that the target application is already installed in the operating system, the operating system invokes the target application and sends a URL to the target application, where the URL includes service parameter information, and the service parameter information includes scenario type information and an information identifier corresponding to the scenario type information.

[0149] After obtaining the URL, the target application pre-generates a correspondence relationship table based on the scenario type information in the URL through a query, identifies a URL template having a correspondence relationship with the scenario type information, replaces the replaceable mark in the identified URL template with an information identifier corresponding to the scenario type information, and obtains a service URL. A first application page (app calling landing page) is generated based on the rendering parameter information in the service URL, and the first application page includes a predetermined operation means. After obtaining a user's trigger action on the predetermined operation means, the target application sends a service request including the information identifier to an application server.

[0150] After receiving the service request sent by the target application, the target application server obtains service description information corresponding to the information identifier through a query based on the analysis operation of the information identifier included in the service request, then determines service processing result information based on the service description information, and sends the service processing result information to the target application, allowing the target application to display a second application page based on the service processing result information.

[0151] Based on the same idea, one or more embodiments of the present specification further provide an apparatus corresponding to the above-mentioned method. Figure 12 is a schematic diagram showing the structure of an NFC-based service execution apparatus corresponding to Figure 2 according to one or more embodiments of the present specification. As shown in Figure 12, the apparatus includes: a URL acquisition module 1202 configured to acquire a uniform resource locator (URL) provided by an NFC tag device in a near field communication manner, the URL including protocol type information, domain name information, and lightweight application card parameters, the protocol type information indicating that the URL complies with Hypertext Transfer Protocol Secure, and the lightweight application card parameters being used for recognition by the iOS operating system in the lightweight application card manner;

[0152] and an application startup module 1204 configured to start an application corresponding to the domain name information, where the application is used to execute a service process corresponding to the URL.

[0153] Based on the device of FIG. 12, one or more embodiments herein further provide some specific implementation strategies for the device, as described below.

[0154] Optionally, the application initiation module 1204 is particularly configured to determine an application corresponding to a URL based on domain name information; and

[0155] an application determining unit configured to determine whether the application is already installed in the operating system, and obtain a determination result;

[0156] and an application launch unit configured to launch the application if the determination result indicates that the application is already installed in the operating system.

[0157] Optionally, the application startup module 1204 further includes a first predetermined page information obtaining unit configured to obtain, based on the URL, first predetermined page information corresponding to the URL from an application server of the application when the determination result indicates that the application is not installed in the operating system;

[0158] and a first predetermined page display unit configured to display a first predetermined page generated based on the first predetermined page information, the first predetermined page including a first download operation means used to provide a prompt instructing the user to download the application.

[0159] Optionally, the application startup module 1204 may further include a page element display unit configured to display a banner page element, where the banner page element includes information used to provide a prompt to access the application, and to obtain a first trigger action of the user on the banner page element.

[0160] Optionally, the application determining unit may particularly include a first application determining subunit configured to determine, in response to the first triggering operation, whether the application is already installed in the operating system.

[0161] Optionally, the operating system includes an iOS operating system with lightweight application functions. The application launch module 1204 further includes: a card information acquisition unit configured to acquire lightweight application card information corresponding to the lightweight application card parameters based on the lightweight application card parameters;

[0162] a card display unit configured to display a lightweight application card generated based on the lightweight application card information, the lightweight application card including an application access operation means, the application access operation means being used to provide a prompt to instruct a user to access the application; and

[0163] and a trigger action acquisition unit configured to acquire a second trigger action for the application access operation means.

[0164] Optionally, the application determining unit may particularly include a second application determining subunit configured to determine whether the application is already installed in the operating system in response to the second triggering operation.

[0165] Optionally, the URL further includes lightweight application page parameters.

[0166] Optionally, the application startup module 1204 further includes: a lightweight application page information acquisition unit configured to acquire, based on the lightweight application page parameter, lightweight application page information corresponding to the lightweight application page parameter when the determination result indicates that the application is not installed in the operating system; and

[0167] and a lightweight application page display unit configured to display a lightweight application page generated based on the lightweight application page information in a lightweight application corresponding to the lightweight application card, the lightweight application page including a second download operation means used to provide a prompt to instruct the user to download the application.

[0168] Optionally, the lightweight application page further includes a service operation means used to instruct the execution of a service process.

[0169] Optionally, the application initiation module 1204 further includes: a third trigger action acquisition unit configured to acquire a third trigger action of the user on the service operation means;

[0170] and a second download operation means display unit configured to highlight the second download operation means in response to a third triggering action.

[0171] Optionally, the application startup module 1204 may further include a URL sending unit configured to send a URL to the application, where the URL further includes service parameter information, and the service parameter information is used as a basis used by the application to execute a service process corresponding to the URL.

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

[0173] Optionally, the application initiation module 1204 further includes: a URL template query unit configured to query, by the application based on the scenario type information, a URL template having a mapping relationship with the scenario type information, where the URL template includes a replaceable marker, and the replaceable marker is used to identify a position where the information identifier can be input; and

[0174] a replaceable marker replacement unit configured to replace the replaceable marker with an information identifier and obtain a service URL including the information identifier;

[0175] and a service process execution unit configured to execute a service process based on the service URL.

[0176] Optionally, the service URL may include rendering parameter information used to render the first application page, the information identifier may be included in the rendering parameter information, and the service process execution unit may particularly include a rendering subunit configured to render the first application page based on the rendering parameter information.

[0177] Optionally, the first application page includes a predetermined operation means, and the service process execution unit is further configured to send a service request to an application server of the application in response to a user's trigger action on the predetermined operation means, the service request sending subunit including an information identifier; and

[0178] a service processing result information receiving subunit configured to receive service processing result information determined by an application server in response to a service request, wherein the service processing result information is determined by the application server based on service description information, and the service description information is obtained by the application server through a query based on an information identifier;

[0179] and a second application page display subunit configured to display a second application page generated based on the service processing result information.

[0180] Optionally, the service parameter information further includes amount information corresponding to the scenario type information, the amount information being included in the rendering parameter information after being joined with the information identifier, and the first application page further includes a payment amount corresponding to the amount information.

[0181] Optionally, the application startup module 1204 further includes: a home page URL obtaining unit configured to obtain a home page URL of the application when a URL template having a mapping relationship with the scenario type information is not identified;

[0182] and a home page display unit configured to display a home page of the application based on the home page URL.

[0183] Optionally, the service parameter information includes scenario type information and a specified service URL corresponding to the scenario type information.

[0184] Optionally, the application startup module 1204 further includes: a designated page information acquisition unit configured to, when the value of the scenario type information is a designated parameter, acquire, by the application based on the designated service URL, designated page information corresponding to the designated service URL from a designated server corresponding to the designated service URL;

[0185] and a designated page display unit configured to display a designated page generated based on the designated page information.

[0186] Optionally, the application comprises a payment application and the service process comprises a payment process.

[0187] 13 is a schematic diagram illustrating the structure of an NFC-based service execution device corresponding to FIG. 9, according to one or more embodiments of the present disclosure. As shown in FIG. 13, the device includes: a signal receiving module 1302 configured to receive a near field communication signal transmitted by a user terminal device;

[0188] and an information sending module 1304 configured to send a Uniform Resource Locator (URL) to the user terminal device in a near field communication manner in response to the near field communication signal, where the URL includes protocol type information, domain name information, and lightweight application card parameters, where the protocol type information represents that the URL complies with HyperText Transfer Protocol Secure, the lightweight application card parameters are used to be recognized by the iOS operating system in the lightweight application card manner, the domain name information is used by the user terminal device to launch an application corresponding to the domain name information, and the application is used to execute a service process corresponding to the URL.

[0189] Based on the device of FIG. 13, one or more embodiments herein further provide some specific implementation strategies for the device, as described below.

[0190] Optionally, the apparatus of FIG. 13 further comprises: a trigger action acquisition module configured to acquire a predetermined trigger action;

[0191] a first service information acquisition module configured to acquire first service information in response to the triggering action;

[0192] a URL acquisition request sending module configured to send a URL acquisition request to an application server, the URL acquisition request including first service information;

[0193] and a URL receiving module configured to receive a URL returned by the application server, the URL including an information identifier, the information identifier being used to query service description information, the service description information including first service information and second service information, the second service information including information obtained by the application server and related to the service corresponding to the first URL.

[0194] Optionally, the triggering action comprises a payment collection initiation action, the application comprises a payment application and the service process comprises a payment process.

[0195] Based on the same idea, one or more embodiments herein further provide a device corresponding to the above-mentioned method.

[0196] Figure 14 is a schematic diagram illustrating the structure of a user terminal corresponding to Figure 2, in accordance with one or more embodiments herein. As shown in Figure 14, the device 1400 may include at least one processor 1410 and a memory 1430 communicatively coupled to the at least one processor. The memory 1430 stores instructions 1420 that can be executed by the at least one processor 1410, and when the instructions are executed by the at least one processor 1410, the at least one processor 1410 can perform the following operations: acquire a uniform resource locator (URL) provided by an NFC tag device in a near field communication manner, the URL including protocol type information, domain name information, and lightweight application card parameters, the protocol type information indicating that the URL complies with Hypertext Transfer Protocol Secure, and the lightweight application card parameters being used to be recognized by the iOS operating system in the lightweight application card manner; and launch an application corresponding to the domain name information, the application being used to execute a service process corresponding to the URL.

[0197] 15 is a schematic diagram illustrating a structure of an NFC tag device corresponding to FIG. 9, in accordance with one or more embodiments herein. As shown in FIG. 15, device 1500 may include at least one processor 1510 and a memory 1530 communicatively coupled to the at least one processor. The memory 1530 stores instructions 1520 that can be executed by the at least one processor 1510, such that the at least one processor 1510 receives a near field communication signal transmitted by a user terminal device;

[0198] In response to the near field communication signal, a uniform resource locator (URL) can be sent to the user terminal device via a near field communication scheme, the URL including protocol type information, domain name information, and lightweight application card parameters, the protocol type information representing that the URL complies with Hypertext Transfer Protocol Secure, the lightweight application card parameters being used to be recognized by the iOS operating system via the lightweight application card scheme, the domain name information being used by the user terminal device to launch an application corresponding to the domain name information, and the application being used to execute a service process corresponding to the URL.

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

[0200] The embodiments herein are described in a progressive manner. References may be made to the same or similar parts of the embodiments. Each embodiment will focus on differences from other embodiments. Specifically, the device embodiment shown in Figures 14 and 15 is basically similar to the method embodiment, and will be briefly described. For relevant parts, reference may be made to the relevant description of the method embodiment.

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

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

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

[0204] For ease of explanation, the above-mentioned devices are described by dividing their functions into various units. Of course, when the present application is implemented, the functions of the units may be implemented in one or more of software and / or hardware.

[0205] Those skilled in the art should understand that some embodiments of the present application may be provided as a method, a system, or a computer program product. Thus, the present application may take the form of a hardware-only embodiment, a software-only embodiment, or an embodiment using a combination of software and hardware. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk memory, CD-ROM, and optical memory) containing computer-usable program code.

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

[0207] These computer program instructions, which can instruct a computer or another programmable data processing device to operate in a particular manner, can be stored in a computer-readable memory, such that the instructions stored in the computer-readable memory create an artifact that includes an instruction apparatus that implements a particular function in one or more processes in the flowcharts and / or one or more blocks in the block diagrams.

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

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

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

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

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

[0213] Those skilled in the art should understand that the embodiments of the present application may be provided as a method, a system, or a computer program product. Therefore, the present application may use the form of a hardware-only embodiment, a software-only embodiment, or an embodiment using a combination of software and hardware. In addition, the present application may use the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk memory, CD-ROM, optical memory, etc.) containing computer-usable program code.

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

[0215] The above description is merely a few embodiments of the present application and is not intended to limit the present application. Those skilled in the art can make various changes and modifications to the present application. Any modifications, equivalent replacements, or improvements made without departing from the spirit and scope of the present application shall fall within the scope of the claims of the present application. [Explanation of symbols]

[0216] 101 Starting Device 102 Target Devices 1202 URL Acquisition Module 1204 Application Startup Module 1302 signal receiving module 1304 Signal Transmitting Module 1400 devices 1410 processor 1420 Instructions 1430 memory 1500 devices 1510 processor 1520 Instructions 1530 memory

Claims

1. 1. An NFC-based service execution method applied to a user terminal device, comprising: Acquiring, by an operating system in a near field communication manner, a uniform resource locator (URL) provided by an NFC tag device, the URL comprising protocol type information, domain name information, and lightweight application card parameters, the protocol type information indicating that the URL complies with HyperText Transfer Protocol Secure, and the lightweight application card parameters being used to be recognized by an iOS operating system in the lightweight application card manner; and starting an application corresponding to the domain name information, the application being used to execute a service process corresponding to the URL.

2. The step of starting an application corresponding to the domain name information particularly includes: determining the application corresponding to the URL based on the domain name information; determining whether the application is already installed on the operating system to obtain a determination result; and if the determination indicates that the application is already installed on the operating system, starting the application.

3. To obtain a determination result, after the step of determining whether the application is already installed in the operating system, the method further comprises: When the determination result indicates that the application is not installed in the operating system, obtaining first predetermined page information corresponding to the URL from an application server of the application based on the URL; and displaying a first predetermined page generated based on the first predetermined page information, the first predetermined page comprising a first download operation means used to provide a prompt to instruct the user to download the application.

4. Before the step of determining whether the application is already installed on the operating system, the method further comprises: displaying a banner page element, the banner page element comprising information used to provide a prompt to access the application; acquiring a first user trigger action on the banner page element; The step of determining whether the application is already installed on the operating system particularly comprises: The method of claim 2 , further comprising the step of determining, in response to the first triggering action, whether the application is already installed on the operating system.

5. The operating system comprises an iOS operating system with lightweight application capabilities, and prior to the step of determining whether the application is already installed on the operating system, the method further comprises: obtaining lightweight application card information corresponding to the lightweight application card parameters according to the lightweight application card parameters; displaying a lightweight application card generated based on the lightweight application card information, the lightweight application card comprising an application access operation means, the application access operation means being used to provide a prompt to instruct a user to access the application; and obtaining a second trigger action for the application access operation means; The step of determining whether the application is already installed on the operating system particularly comprises: The method of claim 2 , further comprising the step of determining, in response to the second triggering action, whether the application is already installed on the operating system.

6. The URL further comprises a lightweight application page parameter, and after the step of determining whether the application is already installed on the operating system, the method further comprises: When the determination result indicates that the application is not installed in the operating system, obtaining lightweight application page information corresponding to the lightweight application page parameter according to the lightweight application page parameter; and displaying a lightweight application page generated based on the lightweight application page information in the lightweight application corresponding to the lightweight application card, wherein the lightweight application page comprises a second download operation means used to provide a prompt to instruct the user to download the application.

7. The lightweight application page further comprises a service operation means used to instruct the execution of the service process; After the step of displaying a lightweight application page generated based on the lightweight application page information, the method further comprises: obtaining a third triggering action of the user on the service operation means; and highlighting the second download operation means in response to the third triggering action.

8. After the step of starting an application corresponding to the domain name information, the method further comprises:

2. The method of claim 1, further comprising the step of sending the URL to the application, wherein the URL further comprises service parameter information, and the service parameter information is used as a basis used by the application to execute the service process corresponding to the URL.

9. the service parameter information comprises scenario type information and an information identifier corresponding to the scenario type information, the information identifier being used as a basis for querying service description information, and after the step of sending the URL to the application, the method further comprises: a step of querying, by the application based on the scenario type information, a URL template having a correspondence relationship with the scenario type information, the URL template comprising a replaceable mark, the replaceable mark being used to identify a position where the information identifier can be input; replacing the replaceable mark with the information identifier to obtain a service URL comprising the information identifier; and performing the service process based on the service URL.

10. The service URL comprises rendering parameter information used to render a first application page, and the information identifier is included in the rendering parameter information, and the step of performing the service process based on the service URL particularly includes: The method of claim 9 , comprising rendering the first application page based on the rendering parameter information.

11. The first application page comprises a predetermined operation means, and after the step of rendering the first application page based on the rendering parameter information, the method further comprises: a step of transmitting a service request to an application server of the application in response to a user's triggering action on the predetermined operating means, the service request including the information identifier; receiving service processing result information determined by the application server in response to the service request, wherein the service processing result information is determined by the application server based on the service description information, and the service description information is obtained through a query by the application server based on the information identifier; and displaying a second application page generated based on the service processing result information.

12. The method of claim 10, wherein the service parameter information further comprises amount information corresponding to the scenario type information, the amount information being included in the rendering parameter information after being joined with the information identifier, and the first application page further comprises a payment amount corresponding to the amount information.

13. After the step of querying, by the application based on the scenario type information, a URL template having a correspondence relationship with the scenario type information, the method further comprises: If the URL template having the correspondence relationship with the scenario type information is not identified, acquiring a homepage URL of the application; and displaying a home page of the application based on the home page URL.

14. the service parameter information comprises scenario type information and a specified service URL corresponding to the scenario type information, and after the step of sending the URL to the application, the method further comprises: When the value of the scenario type information is a specified parameter, acquiring, by the application based on the specified service URL, specified page information corresponding to the specified service URL from a specified server corresponding to the specified service URL; and displaying a designated page generated based on the designated page information.

15. 15. The method of claim 1, wherein the application comprises a payment application and the service process comprises a payment process.

16. 1. An NFC-based service execution method applied to an NFC tag device, comprising: receiving a near field communication signal transmitted by a user terminal device; and in response to the near field communication signal, sending a uniform resource locator (URL) to the user terminal device via a near field communication scheme, wherein the URL comprises protocol type information, domain name information, and lightweight application card parameters, the protocol type information indicating that the URL complies with HyperText Transfer Protocol Secure, the lightweight application card parameters being used to be recognized by an iOS operating system via the lightweight application card scheme, the domain name information being used by the user terminal device to launch an application corresponding to the domain name information, and the application being used to execute a service process corresponding to the URL.

17. Before the step of receiving a near field communication signal transmitted by a user terminal device, the method further comprises: acquiring a predetermined triggering action; acquiring first service information in response to the triggering action; sending a URL acquisition request to an application server, the URL acquisition request comprising the first service information; receiving the URL returned by the application server, wherein the URL comprises an information identifier, the information identifier is used to query service description information, the service description information comprises the first service information and second service information, the second service information comprising information obtained by the application server and relating to a service corresponding to the URL.

18. 18. The method of claim 16 or 17, wherein the triggering action comprises a payment collection initiation action, the application comprises a payment application, and the service process comprises a payment process.

19. An NFC-based service execution device applied to a user terminal device, comprising: a URL acquisition module configured to acquire a uniform resource locator (URL) provided by an NFC tag device in a near field communication manner, the URL comprising protocol type information, domain name information, and lightweight application card parameters, the protocol type information indicating that the URL complies with Hypertext Transfer Protocol Secure, and the lightweight application card parameters being used for recognition by an iOS operating system in the lightweight application card manner; an application startup module configured to start an application corresponding to the domain name information, wherein the application is used to execute a service process corresponding to the URL.

20. An NFC-based service execution device applied to an NFC tag device, comprising: a signal receiving module configured to receive a near field communication signal transmitted by a user terminal device; and an information sending module configured to send a uniform resource locator (URL) to the user terminal device via a short-range wireless communication scheme in response to the near-field wireless communication signal, wherein the URL comprises protocol type information, domain name information, and lightweight application card parameters, the protocol type information indicating that the URL complies with HyperText Transfer Protocol Secure, the lightweight application card parameters being used to be recognized by an iOS operating system in a lightweight application card scheme, the domain name information being used by the user terminal device to launch an application corresponding to the domain name information, and the application being used to execute a service process corresponding to the URL.

21. at least one processor; a memory communicatively coupled to the at least one processor; The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, such that the at least one processor: In a near field communication manner, acquiring a uniform resource locator (URL) provided by an NFC tag device, the URL comprising protocol type information, domain name information, and lightweight application card parameters, the protocol type information indicating that the URL complies with Hypertext Transfer Protocol Secure, and the lightweight application card parameters being used to be recognized by an iOS operating system in the lightweight application card manner; and starting an application corresponding to the domain name information, the application being used to execute a service process corresponding to the URL.

22. at least one processor; a memory communicatively coupled to the at least one processor; The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, such that the at least one processor: receiving a near field communication signal transmitted by a user terminal device; In response to the near field communication signal, the NFC tag device can send a uniform resource locator (URL) to the user terminal device in a near field communication manner, the URL comprising protocol type information, domain name information, and lightweight application card parameters, the protocol type information indicating that the URL complies with Hypertext Transfer Protocol Secure, the lightweight application card parameters being used to be recognized by an iOS operating system in a lightweight application card manner, the domain name information being used by the user terminal device to launch an application corresponding to the domain name information, and the application being used to execute a service process corresponding to the URL.

Images