A service execution method, apparatus and device based on NFC

Abstract

This specification discloses an NFC-based service execution method, apparatus, and device in its embodiments. The solution may include: based on near-field communication, the operating system obtains a Uniform Resource Locator (URL) from an NFC tag device, determines a target application based on the domain name information in the URL, and launches the target application to execute the business process corresponding to the URL. The URL contains protocol type information indicating that the URL conforms to the Hypertext Transfer Security Protocol (HTTP), domain name information, and lightweight application card information for identification by the iOS operating system as a lightweight application card.

Description

[0001] The present application is a divisional application of the Chinese patent application, the original application date of which is August 5, 2024, the application number of which is 202411067880.4, and the invention title of which is: a service execution method, device and equipment based on NFC. TECHNICAL FIELD

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

[0003] Near Field Communication (NFC) is widely used in various fields due to its convenience, safety, low power consumption and other advantages. However, in some special scenarios, the process of executing services based on NFC may fail. For example, for terminal devices running the IOS operating system, the terminal device cannot execute the task of calling the terminal based on NFC in the locked screen state.

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

[0005] The embodiments of the present application provide a service execution method, device and equipment based on NFC to improve the success rate of executing services based on NFC.

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

[0007] The service execution method based on NFC provided by the embodiments of the present application is applied to a user terminal device, which includes: an operating system acquires a uniform resource locator (URL) provided by an NFC tag device through a near field communication (NFC) mode; the URL contains protocol type information, domain name information and light application card parameters; the protocol type information indicates that the URL conforms to the hypertext transfer protocol secure (HTTPS) protocol; the light application card parameters are used to be recognized by an IOS operating system in the form of a light application card; an application corresponding to the domain name information is started; and the application is used to execute a service flow corresponding to the URL.

[0008] The service execution method based on NFC provided by the embodiments of the present application is applied to an NFC tag device, which includes:

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

[0010] The embodiment of the present specification provides a NFC-based business execution device, applied to a user terminal device, comprising:

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

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

[0013] The embodiment of the present specification provides a NFC-based business execution device, applied to a NFC tag device, comprising:

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

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

[0016] The embodiment of the present specification provides a user terminal device, comprising:

[0017] At least one processor; and,

[0018] A memory connected in communication with the at least one processor; wherein,

[0019] The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: acquire a uniform resource locator (URL) provided by an NFC tag device through near field communication; the URL includes protocol type information, domain name information, and a light application card parameter; the protocol type information indicates that the URL conforms to the hypertext transfer protocol secure (HTTPS) protocol; the light application card parameter is used to be recognized by an IOS operating system in the form of a light application card; start an application corresponding to the domain name information; and the application is used to execute a business process corresponding to the URL.

[0020] The NFC tag device provided by the embodiments of the present specification comprises:

[0021] at least one processor; and

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

[0023] The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: receive a near field communication signal transmitted by a user terminal device; in response to the near field communication signal, send a uniform resource locator (URL) to the user terminal device through near field communication; the URL includes protocol type information, domain name information, and a light application card parameter; the protocol type information indicates that the URL conforms to the hypertext transfer protocol secure (HTTPS) protocol; the light application card parameter is used to be recognized by an IOS operating system in the form of a light application card; the domain name information is used to start an application corresponding to the domain name information by the user terminal device; and the application is used to execute a business process corresponding to the URL.

[0024] The at least one embodiment in the specification can achieve the following beneficial effects:

[0025] The URL transmitted based on near field communication includes protocol type information conforming to the hypertext transfer protocol secure (HTTPS) protocol, and includes a light application card parameter that can be used to be recognized by an IOS operating system in the form of a light application card. The URL transmitted based on near field communication can be recognized by many operating systems including but not limited to IOS, so that the success rate of terminal calling of devices of various operating systems can be greatly improved on the basis of the URL being recognized by many operating systems, and the success rate of business execution is further improved. BRIEF DESCRIPTION OF DRAWINGS

[0026] In order to make the technical solutions in the embodiments of the present specification or the prior art clearer, the accompanying drawings needed to be used in the embodiments or prior art description are briefly introduced as follows. Obviously, the accompanying drawings in the following description only some embodiments described in the present application, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0027] Figure 1 is an application scenario of a NFC-based service execution method provided by an embodiment of the present specification;

[0028] Figure 2 is a flowchart of a NFC-based service execution method provided by an embodiment of the present specification;

[0029] Figure 3 is a structure diagram of a URL provided by an embodiment of the present specification;

[0030] Figure 4 is a diagram after a target application is enabled provided by an embodiment of the present specification;

[0031] Figure 5 is a first preset page diagram provided by an embodiment of the present specification;

[0032] Figure 6 is a display page diagram containing a banner page element provided by an embodiment of the present specification;

[0033] Figure 7 is a light application card diagram provided by an embodiment of the present specification;

[0034] Figure 8 is a light application page diagram provided by an embodiment of the present specification;

[0035] Figure 9 is a flowchart of another NFC-based service execution method provided by an embodiment of the present specification;

[0036] Figure 10 is a swimlane flowchart corresponding to the NFC-based service execution method in Figure 2 and Figure 9 provided by an embodiment of the present specification;

[0037] Figure 11 is another swimlane flowchart corresponding to the NFC-based service execution method in Figure 2 and Figure 9 provided by an embodiment of the present specification;

[0038] Figure 12 is a swimlane flowchart corresponding to the NFC-based service execution method in Figure 2A schematic diagram of the structure of a device for executing services based on NFC;

[0039] Figure 13 The embodiments provided in this specification correspond to Figure 9 A schematic diagram of the structure of a device for executing services based on NFC;

[0040] Figure 14 The embodiments provided in this specification correspond to Figure 2 A schematic diagram of the structure of a user terminal device for the business execution method;

[0041] Figure 15 The embodiments provided in this specification correspond to Figure 9 A schematic diagram of the structure of an NFC tag device for implementing business operations. Detailed Implementation

[0042] To make the objectives, technical solutions, and advantages of one or more embodiments of this specification clearer, the technical solutions of one or more embodiments of this specification will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of them. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the protection scope of one or more embodiments of this specification.

[0043] To facilitate understanding of the technical solutions of one or more embodiments of this specification, some terms are explained as follows:

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

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

[0046] "Activation" refers to waking up a mobile application or putting it into an active state through a certain triggering mechanism.

[0047] Burning: refers to the process of writing software, firmware, or data into the storage medium of electronic devices or machines.

[0048] In existing technologies, NFC-based applications on mobile devices are typically activated using traditional URL protocols. These protocols can be things like "alipay" or "alipays". However, when the mobile device is running iOS, the traditional URL protocol fails to recognize the device within two seconds of being locked or unlocked due to iOS's built-in protection mechanisms. This results in application activation failure. Therefore, the success rate of NFC-based applications on mobile devices is relatively low in current technologies.

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

[0050] Figure 1 This is a schematic diagram illustrating an application scenario of an NFC-based service execution method as described in the embodiments of this specification.

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

[0052] In the embodiments of this specification, the initiating device is a device that actively initiates communication, responsible for generating a radio frequency field and initiating the NFC communication process. The initiating device may include, but is not limited to, smartphones, tablets, laptops, desktop computers, smart interactive devices, or other devices capable of actively sending NFC signals, and initiating device 101 can be any one of these initiating devices.

[0053] The target device is a passively responding device that responds to the request from the initiating device and exchanges data. The target device may include, but is not limited to, NFC tags, smart cards, access cards, payment terminals, or other smart devices, and target device 102 can be any one of these target devices.

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

[0055] Figure 2 This is a flowchart illustrating an NFC-based service execution method provided in an embodiment of this specification. From a software perspective, the execution entity of the process can be a program or application client mounted on a user terminal device with NFC functionality. From a hardware perspective, the execution entity of the process can be a user terminal device with NFC functionality.

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

[0057] Step 202: The operating system obtains the Uniform Resource Locator (URL) provided by the NFC tag device through near-field communication; the URL includes protocol type information, domain name information, and lightweight application card parameters; the protocol type information indicates that the URL conforms to the Hypertext Transfer Security Protocol; the lightweight application card parameters are used by the iOS operating system to identify the application as a lightweight application card.

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

[0059] In the embodiments described in this specification, the terminal device where the operating system resides is hereinafter referred to as the user terminal device. The user terminal device and the NFC tag device establish a communication connection via near-field communication (NFC). Based on this established communication connection, the NFC tag device sends a URL to the user terminal device. This URL can be a URL pre-stored on the NFC tag device by the developers, or a URL generated in real-time in response to a request from the actual operator.

[0060] In the embodiments of this specification, the URL may include protocol type information, domain name information, path information, query parameter information, etc. The protocol in the URL can 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. The application corresponding to the URL is hereinafter referred to as the target application.

[0061] To facilitate understanding of this solution by those skilled in the art, a specific example of a URL is provided in the embodiments of this specification.

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

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

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

[0065] Furthermore, in practical applications, the domain name ulink.alipay.com, the parameter name 's' of the first query parameter, the parameter name 'scheme' of the second query parameter, the format information in the business parameter information corresponding to the second query parameter, and the structure of the entire URL can be pre-defined information that will not change within a certain period of time and will not change during different communications. This allows multiple terminals, such as the operating system, operating system server, application, and application server, to identify and process the received URL according to the pre-defined settings. Of course, the aforementioned agreed-upon information can be changed during software updates, solution upgrades, etc. For example, the domain name can be changed from ulink.alipay.com to render.alipay.com, and after the change, all terminals that need to consume this information, such as the operating system, operating system server, application, and application server, need to be synchronized and updated.

[0066] In the embodiments described in this specification, iOS 14 and later operating systems have a Lite app feature that allows users to quickly use applications without downloading and installing the full application; that is, a Lite app feature that runs on the operating system. Therefore, to adapt to this Lite app feature in iOS 14 and later operating systems, the URL transmitted via NFC can contain Lite app card parameters for iOS to recognize as Lite app cards. This allows iOS to recognize the Lite app card parameters in the URL, triggering the Lite app feature and displaying the corresponding Lite app card, thereby improving the success rate of client activation on iOS.

[0067] Optionally, app card parameters can be included in the URL's path information.

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

[0069] In the embodiments described in this specification, the operating system, based on the obtained URL, can launch the target application if the target application is already installed on the operating system. This allows the launched target application to execute the corresponding business process based on the query parameters in the URL. If the target application is not installed on the operating system, the operating system can open the application page corresponding to the URL, allowing the user to complete subsequent business processes based on the information displayed on the opened application page.

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

[0071] Figure 2 The method described above, based on NFC-transmitted URLs, can be recognized by both Android and HarmonyOS operating systems, as well as iOS. This allows iOS devices to be successfully invoked in NFC-based wake-up scenarios, thereby significantly improving the wake-up success rate for iOS devices and enhancing the overall wake-up success rate for the user base.

[0072] based on Figure 2 In addition to the method described herein, this specification also provides some specific implementation methods of this method, which will be described below.

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

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

[0075] In the embodiments of this specification, the domain name information can be information designed by the application developers to identify the corresponding application. Furthermore, the domain name information corresponding to the application can be pre-registered on the World Wide Web, thus allowing the identification of the corresponding application based on the domain name information.

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

[0077] Optionally, taking Alipay as the target application as an example, for payment scenarios, the page after the target application is enabled can be as follows: Figure 4 As shown. Figure 4 The information shown is for illustrative purposes only; in actual applications, it may display the same information as in the example provided. Figure 4 Different information can be displayed, specifically other text, images, animations, controls, etc. Figure 4 The information displayed is not specifically limited.

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

[0079] In the embodiments of this specification, the URL obtained by the operating system can be a resource address used to identify and locate resources. Therefore, if it is determined that the target application is not installed in the operating system, the first preset page information corresponding to the URL can be obtained from the server of the target application based on the URL, and a corresponding first preset page can be generated based on the first preset page information. The first preset page information contains all the information needed to generate the first preset page, such as, but not limited to, image information, title information, subtitle information, control information, etc. The first preset page may contain a first download control; after the user performs a trigger operation on the first download control, the download and installation process of the target application can be triggered.

[0080] Optionally, taking Alipay as the target application as an example, the generated first preset page can be as follows: Figure 5 As shown. Figure 5 In the middle, the first download control 10 is the "Download Alipay" control. Figure 5 The information shown is for illustrative purposes only; in actual applications, it may display the same information as in the example provided. Figure 5 Different information can be displayed, specifically other text, images, animations, controls, etc. Figure 5 The information displayed is not specifically limited.

[0081] In the embodiments of this specification, after determining that the target application has been installed in the operating system, the target application can be launched directly to improve the user experience; when determining that the target application has not been installed in the operating system, a first preset page can be displayed to prompt the user to download the target application to increase the user usage of the target application.

[0082] To improve user experience, after the operating system obtains the URL of the NFC tag device via NFC, it can pre-generate a prompt message to ask the user whether they need to access the target application. This allows the target application to be launched only after obtaining the user's authorization, thus avoiding disturbing the user when they do not need to open the target application.

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

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

[0085] In the embodiments described in this specification, after the operating system determines the target application based on the domain name information in the URL, it can display a banner page element within the current interface on which the operating system is running. The banner page element may contain prompts to the user asking whether they need to access the application. The banner page element can be displayed in any one of the top, bottom, and middle areas of the visible area of ​​the current interface, or it can be displayed in any area of ​​the visible area of ​​the current interface; there is no specific limitation on the display position of the banner page element.

[0086] Optionally, taking Alipay as the target application as an example, the display page containing banner page elements can be as follows: Figure 6 As shown, Figure 6 In the image, banner page element 20 is located at the top of the visible area. Figure 6 The information shown is for illustrative purposes only; in actual applications, it may display the same information as in the example provided. Figure 6 Different information can be displayed, specifically other text, images, animations, controls, etc. Figure 6 The information displayed is not specifically limited.

[0087] In this embodiment of the specification, if the operating system receives a first trigger operation from the user on a banner page element within a preset time, the first trigger operation can be a click operation by the user on a preset control within the banner page element, or it can be a click operation by the user on any position within the banner page element. In response to the user's first trigger operation, a determination process is performed to determine whether the target application is installed in the operating system. If it is determined that the target application is installed in the operating system, the target application is launched; if it is determined that the target application is not installed in the operating system, a target page is displayed to prompt the user to download the target application.

[0088] In this embodiment of the specification, if the operating system does not receive the user's first trigger operation on the banner page element within a preset time, the banner page element will stop being displayed.

[0089] Based on the above embodiments, in this embodiment of the specification, the operating system may include an iOS operating system with lightweight application functionality; before determining whether the application has been installed in the operating system, the method may further include: obtaining lightweight application card information corresponding to the lightweight application card parameters; displaying a lightweight application card generated based on the lightweight application card information; the lightweight application card includes an application access control; the application access control is used to prompt the user to access the application; and obtaining a second trigger operation for the application access control.

[0090] The determination of whether the application is installed in the operating system may specifically include:

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

[0092] In the embodiments described in this specification, the operating system may include the iOS operating system with lightweight app functionality, specifically iOS version 14 or later. Lightweight apps are applications that run on the operating system and can be used without downloading. For example, app clips running on the iOS operating system.

[0093] In this embodiment of the specification, obtaining the lightweight application card information corresponding to the lightweight application card parameters based on the lightweight application card parameters may specifically include: obtaining the lightweight application card information corresponding to the lightweight application card parameters from the system server corresponding to the operating system. The lightweight application card information may include image information, title information, subtitle information, and control information, etc. Different business scenarios may correspond to different lightweight application card parameters, and the lightweight application card information corresponding to each parameter may be different. For example, the lightweight application card parameters corresponding to the payment scenario are different from those corresponding to the gate opening scenario; the lightweight application card parameters corresponding to the payment scenario are also different from those corresponding to the water vending machine service scenario.

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

[0095] Optionally, taking Alipay as the target application as an example, the generated mini-application card can be configured for payment scenarios as follows: Figure 7 As shown. Figure 7 In the application, access control 30 is the "Open" control. Figure 7The information shown is for illustrative purposes only; in actual applications, it may display the same information as in the example provided. Figure 7 Different information can be displayed, specifically other text, images, animations, controls, etc. Figure 7 The information displayed is not specifically limited.

[0096] In the embodiments of this specification, if the operating system obtains a second trigger operation from the user on the application access control within a preset time, in response to the second trigger operation, it performs a judgment process on whether the target application has been installed in the operating system. If it is determined that the target application has been installed in the operating system, the target application is launched.

[0097] In this embodiment of the specification, if the operating system does not receive a second trigger operation from the user for the application access control within a preset time, the display of the lightweight application card will be stopped.

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

[0099] In the embodiments of this specification, the parameters of the lightweight application page can be carried in the query parameter information of the URL, specifically, as follows: Figure 3 As shown, the parameters on a lightweight application page can be the parameter values ​​corresponding to the first query parameter in the URL. For example, the parameter value corresponding to parameter 's'.

[0100] In this embodiment of the specification, in response to the second triggering operation, a determination process is performed to determine whether the target application is installed in the operating system. If it is determined that the target application is not installed in the operating system, then the lightweight application page information corresponding to the lightweight application page parameters is obtained. Specifically, based on the lightweight application page parameters, the lightweight application page information corresponding to the lightweight application page parameters is obtained from the system server corresponding to the operating system. The lightweight application page information may include image information, title information, subtitle information, and control information, etc.

[0101] In the embodiments of this specification, the lightweight application page information can be information that the developers of the corresponding application have pre-registered with the system server of the operating system.

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

[0103] Optionally, taking Alipay as the target application as an example, the generated mini-application page can be as follows: Figure 8 As shown, Figure 8 The second download control 40 in the text is the "Download" control. Figure 8 The information shown is for illustrative purposes only; in actual applications, it may display the same information as in the example provided. Figure 8 Different information can be displayed, specifically other text, images, animations, controls, etc. Figure 8 The information displayed is not specifically limited.

[0104] Based on the above embodiments, in the embodiments of this specification, the lightweight application page may further include business controls for instructing the execution of business processes; after displaying the lightweight application page generated based on the lightweight application page information, it may further include: obtaining a third trigger operation of the user on the business controls; in response to the third trigger operation, highlighting the second download control.

[0105] In the embodiments of this specification, the business control can be a control used to prompt the user to make a payment, or it can be a control used to prompt the user to experience the target application. Upon receiving a third trigger operation from the user on the business control, in response to the third trigger operation, the second download control is highlighted to guide the user to download and install the target application through the second download control. This improves the convenience for users to download and install the target application, thereby increasing the user base of the target application.

[0106] In the embodiments of this specification, one or more embodiments are also proposed for the process of a target application performing business based on a URL.

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

[0108] In the embodiments described in this specification, business parameter information can be carried in the query parameter information of the URL.

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

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

[0111] Based on the above embodiments, in the embodiments of this specification, the business parameter information may include scenario type information and information identifiers corresponding to the scenario type information; the information identifiers are used as the basis for querying business description information.

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

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

[0114] In this embodiment, the scenario type information reflects the specific implementation scenario when the business is executed. Business scenarios can include payment scenarios, gate opening scenarios, food ordering scenarios, and water vending machine scenarios, etc. Optionally, the information identifier can be identifier data generated based on business data produced during business execution, such as identifier data generated based on order number or merchant number. The information identifier can be encrypted identifier data, which improves the security of business data. Alternatively, the information identifier can be a random string. The generated information identifier and the corresponding business description information can be stored in the application server so that when the business description information is needed later, it can be queried based on the information identifier.

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

[0116] To facilitate understanding of this solution by those skilled in the art, a specific example of converting a URL to a business URL is presented in the embodiments of this specification.

[0117] Suppose the operating system obtains the following URL from the NFC tag device:

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

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

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

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

[0122] Replace the replaceable tag $[value]$ in the URL template with the information identifier "1q2w3e4r5t6y7u8i" from the URL to obtain the following business URL:

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

[0124] In the embodiments described in this specification, a business URL for executing a business process can be generated based on the URL transmitted between the user terminal device and the NFC tag device, thereby eliminating the need to transmit the business URL for executing the business process between the user terminal device and the NFC tag device. This setup avoids the risk of business URL leakage, improving the confidentiality of the business URL; furthermore, since the data size of the URL is smaller than that of the business URL, it also reduces the amount of data transmitted between the user terminal device and the NFC tag device, improving NFC communication efficiency and ultimately enhancing the user experience.

[0125] Based on the above embodiments, in the embodiments of this specification, the business URL includes rendering parameter information for rendering the first application page; the information identifier is carried in the rendering parameter information; the execution of the business process based on the business URL may specifically include: rendering the first application page based on the rendering parameter information.

[0126] In the embodiments of this specification, taking a payment scenario as an example, we assume the converted business URL is as follows:

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

[0128] In practical applications, the first application page can be rendered based on the rendering parameter information in the business URL. This first application page can be the landing page displayed to the user after the business process is initiated based on NFC, or the first page displayed to the user.

[0129] Based on the above embodiments, in this embodiment of the specification, the first application page may include preset controls; after rendering the first application page based on the rendering parameter information, it may further include: in response to the user's triggering operation on the preset controls, sending a business request to the application server of the application; the business request carrying the information identifier; receiving business processing result information determined by the application server in response to the business request; the business processing result information being determined by the application server based on business description information; the business description information being obtained by the application server based on the information identifier; and displaying a second application page generated based on the business processing result information.

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

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

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

[0133] In practical applications, after generating the information identifier, it can be associated with and stored with the corresponding business description information, and the information identifier can be used as a query index for the business description information.

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

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

[0136] In the embodiments of this specification, the application server may interact with the target application multiple times during the process of determining the business processing result information. For example, the process of decrypting the information identifier in the business URL, verifying the identity information of the user using the target application, verifying the legality of the business URL, verifying the security of the business execution environment, and obtaining the relevant information to be displayed in the second application page.

[0137] In the embodiments of this specification, the second application page generated based on business processing result information can include various types of pages. Taking a payment scenario as an example, the second application page can be an application page displaying information such as payment success. The second application page can also be an application page displaying information such as the specific payment amount. If the user has enabled the password-free payment function, the user can directly click the payment button on the second application page to complete the payment; if the user has not enabled the password-free payment function, after clicking the payment button on the second application page, the second application page can redirect to a third application page, where the user enters the correct password to complete the payment. The second application page can also be an application page displaying a corresponding window requiring the user to enter the payment amount. If the user has enabled the password-free payment function, after entering the corresponding payment amount on the second application page, the user can directly click the corresponding payment button to complete the payment; if the user has not enabled the password-free payment function, after entering the corresponding payment amount on the second application page and clicking the payment button corresponding to the payment amount, the second application page can redirect to a fourth application page, where the user enters the correct password to complete the payment.

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

[0139] Specifically, when the business parameter information contains both the information identifier and the amount information, the information identifier and the amount information can be concatenated with a fixed character (e.g., _), and then in the subsequent URL conversion process, the amount information and the information identifier can be filled into the converted business URL at the same time.

[0140] In the embodiments of this specification, in a payment business scenario, the merchant can input the payment amount to obtain business parameters carrying the amount information. Based on this payment amount, a corresponding information identifier is generated so that the rendering parameter information in the business URL can carry the payment amount. The first application page rendered based on this rendering parameter information can contain the payment amount input by the merchant. If the user has enabled the password-free payment function, the user can directly click the payment button on the first application page to complete the payment; if the user has not enabled the password-free payment function, after the user clicks the payment button on the first application page, the first application page can redirect to a fifth application page, where the user enters the correct password to complete the payment.

[0141] It should be noted that, in the embodiments of this specification, by carrying the amount information in plaintext within the business parameter information, and subsequently within the business URL, when the user terminal device obtains the business URL, it can display the corresponding payment amount on the rendered first application page based on the plaintext amount information in the business URL. In other words, the user can see the amount to be paid on the landing page, improving the user's payment experience. Optionally, when the amount information carries a payment amount, the payment amount can be displayed on the first application page. Optionally, when the amount information does not carry a payment amount, for example, only carries a character indicating that no payment amount has been provided (e.g., 'n'), the payment amount is not displayed on the first application page.

[0142] To facilitate understanding of this solution by those skilled in the art, this specification provides a specific example of converting a URL to a business URL when carrying monetary information.

[0143] Suppose the operating system obtains the following URL from the NFC tag device:

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

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

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

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

[0148] Replace the replaceable tag $[value]$ in the URL template with the information identifier and amount information "1q2w3e4r5t6y7u8i_0.1" from the URL to obtain the following business URL:

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

[0150] In this example, the first application page that the client lands on can display the amount to be paid as "0.1" to the user.

[0151] Based on the above embodiments, in the embodiments of this specification, when querying URL templates based on scene type information, there may still be cases where the query fails.

[0152] Optionally, after querying a URL template that has a mapping relationship with the scene type information based on the scene type information, the application may further include: if no URL template that has a mapping relationship with the scene type information is found, obtaining the homepage URL of the application; and displaying the homepage of the application based on the homepage URL.

[0153] In this embodiment, the application's homepage URL can be pre-stored on the application client. If no matching URL template is found based on the scenario type information in the business URL, the application can directly display its homepage using the pre-stored homepage URL on the client. This configuration improves the speed of displaying the application's homepage. If the application client does not pre-store the homepage URL, and no matching URL template is found, the application can generate a request to retrieve the homepage URL and send it to the application server. The application server responds to the request by sending the homepage URL to the application client. The application then displays its homepage based on the received homepage URL. This configuration reduces the resource consumption of the application client's storage.

[0154] In the embodiments described in this specification, when the application cannot parse out specific business information or the application page to be displayed, the application's homepage can be displayed to the user to reduce the user's negative experience with the application.

[0155] Optionally, when the scenario type information represents a specified business scenario, the application can access the page corresponding to the specified business URL. Based on this, the business parameter information may include scenario type information and the specified business URL corresponding to the scenario type information; after transmitting the URL to the application, the process may further include: when the value of the scenario type information is a specified parameter, the application obtains the specified page information corresponding to the specified business URL from the specified server corresponding to the specified business URL; and displays the specified page generated based on the specified page information.

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

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

[0158] In the embodiments described in this specification, based on user needs, a specified page of another application can be opened within the target application, so that the user has more autonomy to choose and improve the user experience for the target application.

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

[0160] Based on and Figure 2 Following the same approach as the solution shown, this specification also provides another NFC-based service execution method in its embodiments. Figure 9 This is a flowchart illustrating another NFC-based service execution method provided in an embodiment of this specification. From a software perspective, the executor of the process can be a program or application client mounted on an NFC tag device. From a hardware perspective, the executor of the process can be an NFC tag device. For example...Figure 9 As shown, the process may include:

[0161] Step 902: Receive near-field communication signals transmitted by the user terminal equipment.

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

[0163] Step 904: In response to the near-field communication signal, a Uniform Resource Locator (URL) is sent to the user terminal device via near-field communication; the URL includes protocol type information, domain name information, and lightweight application card parameters; the protocol type information indicates that the URL conforms to the Hypertext Transfer Security Protocol; the lightweight application card parameters are used by the iOS operating system to identify the application as a lightweight application card; the domain name information is used by the user terminal device to launch the application corresponding to the domain name information; the application is used to execute the business process corresponding to the URL.

[0164] In the embodiments described in this specification, the NFC tag device, based on a received near-field communication signal, sends a URL to the user terminal device via near-field communication in response to the signal. The URL may include protocol type information, domain name information, port information, path information, query parameter information, etc. The protocol in the URL can be Hypertext Transfer Protocol (HTTP) or Hypertext Transfer Protocol Secure (HTTPS). The domain name information is used to determine the target application corresponding to the URL. After the target application is launched, it can execute the business process corresponding to the URL.

[0165] In the embodiments described in this specification, iOS 14 and later operating systems have a Lite app feature that allows users to quickly use applications without downloading and installing the full application; that is, a Lite app feature that runs on the operating system. Therefore, to adapt to this Lite app feature in iOS 14 and later operating systems, the URL transmitted via NFC can contain Lite app card parameters for iOS to recognize as Lite app cards. This allows iOS to recognize the Lite app card parameters in the URL, triggering the Lite app feature and displaying the corresponding Lite app card, thereby improving the success rate of client activation on iOS.

[0166] Optionally, app card parameters can be included in the URL's path information.

[0167] In the embodiments of this specification, the method for obtaining the URL within the NFC tag device can vary depending on the application scenario. For example, in some vending machine scenarios, the URL can typically carry fixed information; therefore, the URL containing fixed information can be pre-programmed into the NFC tag device. In other scenarios, the URL can carry business data related to the current transaction, such as the order number, user identifier, and order amount; therefore, the corresponding URL can be generated in real time when the transaction occurs.

[0168] Figure 9 The method described above, based on NFC-transmitted URLs, can be recognized by both Android and HarmonyOS operating systems, as well as iOS. This allows iOS devices to be successfully invoked in NFC-based wake-up scenarios, thereby significantly improving the wake-up success rate for iOS devices and enhancing the overall wake-up success rate for the user base.

[0169] based on Figure 9 In addition to the method described in the embodiments of this specification, some specific implementation schemes of the method are also provided, which will be described below.

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

[0171] In the embodiments of this specification, the preset triggering operations may differ for different business scenarios. For example, a cashier's payment collection operation, a payment collection operation initiated after the water sales at the vending machine have ended, a shopper's payment operation initiated after selecting items at the vending machine, and a user's payment operation initiated after shopping on the merchant's corresponding application, etc.

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

[0173] In the embodiments described in this specification, the information identifier can be a token generated by the application server based on the business description information.

[0174] Optionally, the application server can process at least a portion of the information in the business description using preset information processing rules to obtain a token. These preset information processing rules can vary depending on the scenario. For example, in a payment scenario, the token can be obtained by processing the merchant ID or order number. In a water vending machine scenario, the token can be obtained by concatenating the serial number (SN) and the process identifier (PID). In a vending machine scenario, the token can be obtained by processing the vending machine number and the product identifier.

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

[0176] In the embodiments described in this specification, the application server can associate and store information identifiers and business description information. This allows the application server to retrieve the business description information, including the business information, based on the information identifier when an application sends a business request to the application server using a URL, thereby advancing the business process. This configuration improves the security of business information and makes the URL shorter, reducing the amount of data transmitted.

[0177] It should be noted that, for a given NFC tag device, the information identifier in the URL to be generated can change. If the URL also contains monetary information, that information can also change. Otherwise, other information can remain constant. Specifically, the protocol type, domain name, mini-application card parameters, mini-application page parameters, and scenario type information in the URL to be generated can all remain unchanged. Furthermore, if the URL to be generated includes a specific business URL, that specific business URL can also remain unchanged. For each near-field communication performed on the NFC tag device, the URLs sent in different transmissions can differ only in the information identifier and monetary information (if any).

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

[0179] In the embodiments of this specification, for payment business scenarios, based on the NFC communication method between the user terminal device and the NFC tag device, payment can be completed by tapping between devices. This is to facilitate payment for people with disabilities who use smartphones, such as the elderly, without the need for the user to operate the smartphone, for example, without the user opening a scanning device to scan the merchant's QR code. This makes payment more convenient for users, improves the user experience during the payment process, and thus increases user stickiness to the target application.

[0180] The embodiments in this specification also provide corresponding... Figure 2 and Figure 9 The swimlane flow diagram of the NFC-based service execution method.

[0181] like Figure 10 As shown, for Android or HarmonyOS operating systems, this NFC-based business execution process can involve execution entities such as the terminal device operating system, the target application, and the target application server.

[0182] In this embodiment, the terminal device's operating system obtains the URL via NFC near-field communication, determines the target application corresponding to the URL based on the domain name information in the URL, and checks whether the target application is already installed in the operating system. If the target application is not installed, the operating system's built-in browser opens the application download page corresponding to the URL. The application download page displays a download request control. After obtaining the user's trigger operation on the download request control, the target application is downloaded. If the target application is already installed, the target application is activated, and the URL is sent to the target application. The URL contains business parameter information, which includes scene type information and an information identifier corresponding to the scene type information.

[0183] After obtaining the URL, the target application queries a pre-generated mapping table based on the scene type information in the URL to find URL templates that have a mapping relationship with the scene type information. Then, it replaces the replaceable tags in the retrieved URL templates with the information identifier corresponding to the scene type information, thus obtaining the business URL. Based on the rendering parameter information in the business URL, it generates the first application page (the landing page for the client). This first application page contains preset controls. After receiving a user's trigger action on these preset controls, the target application sends a business request carrying an information identifier to the application server.

[0184] After receiving a business request from the target application, the target application server will parse the information identifier carried in the business request to obtain the business description information corresponding to the information identifier. Then, based on the business description information, it will determine the business processing result information and send the business processing result information to the target application so that the target application can display the second application page based on the business processing result information.

[0185] It should be noted that for some other operating systems, such as iOS 13 and earlier, after the terminal device operating system identifies the target application based on the domain name information in the URL, it can also display a pop-up message to prompt the user whether they need to open the target application. Only after receiving the user's trigger action on the pop-up message will the operation of determining whether the target application is already installed in the operating system be executed.

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

[0187] In this embodiment, the terminal device's operating system obtains the URL via NFC near-field communication, determines the target application corresponding to the URL based on the domain name information in the URL, and sends the lightweight application card parameters contained in the path information of the URL to the operating system server. The operating system server queries the corresponding lightweight application card information based on the received lightweight application card parameters, where the lightweight application card information is relevant information pre-registered by the target application's developer on the operating system server. After obtaining the lightweight application card information retrieved by the operating system server, the operating system generates a lightweight application card based on this information and displays the lightweight application card to the user. The lightweight application card contains a first control used to prompt the user whether they need to open the target application. If the operating system detects a user's trigger operation on the first control, the operating system initiates a check to determine if the target application is already installed on the operating system. If it determines that the target application is not installed on the operating system, the operating system sends the lightweight application page parameters contained in the URL query parameters to the operating system server. The operating system server queries the corresponding lightweight application page information based on the received lightweight application page parameters, where the lightweight application page information is relevant information pre-registered by the target application's developer on the operating system server. After obtaining the lightweight application page information retrieved from the operating system server, the operating system generates a lightweight application page based on this information and displays it to the user. This lightweight application page contains a second control that prompts the user whether they want to download the target application. Upon receiving a user interaction with the second control, the target application is downloaded. If it is determined that the target application is already installed on the operating system, the target application is invoked, and a URL is sent to it. This URL contains business parameter information, including scenario type information and an information identifier corresponding to the scenario type.

[0188] After obtaining the URL, the target application queries a pre-generated mapping table based on the scene type information in the URL to find URL templates that have a mapping relationship with the scene type information. Then, it replaces the replaceable tags in the retrieved URL templates with the information identifier corresponding to the scene type information, thus obtaining the business URL. Based on the rendering parameter information in the business URL, it generates the first application page (the landing page for the client). This first application page contains preset controls. After receiving a user's trigger action on these preset controls, the target application sends a business request carrying an information identifier to the application server.

[0189] After receiving a business request from the target application, the target application server will parse the information identifier carried in the business request to obtain the business description information corresponding to the information identifier. Then, based on the business description information, it will determine the business processing result information and send the business processing result information to the target application so that the target application can display the second application page based on the business processing result information.

[0190] Based on the same idea, embodiments of this specification also provide apparatus corresponding to the above methods. Figure 12 The embodiments provided in this specification correspond to Figure 2 A schematic diagram of the structure of an NFC-based service execution device. Figure 12 As shown, the device may include:

[0191] The URL acquisition module 1202 is used to acquire the Uniform Resource Locator (URL) provided by the NFC tag device through near-field communication. The URL includes protocol type information, domain name information, and lightweight application card parameters. The protocol type information indicates that the URL conforms to the Hypertext Transfer Security Protocol (HTTP). The lightweight application card parameters are used to be recognized by the iOS operating system as a lightweight application card.

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

[0193] based on Figure 12 The embodiments of this specification also provide some specific implementations of the device, which will be described below.

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

[0195] The application determination unit is used to determine the application corresponding to the URL based on the domain name information.

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

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

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

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

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

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

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

[0203] Obtain the user's first trigger action on the banner page element.

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

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

[0206] Optionally, the operating system includes an iOS operating system with lightweight application functionality. The application launch module 1204 may further include:

[0207] The card information acquisition unit is used to acquire the light application card information corresponding to the light application card parameters based on the light application card parameters.

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

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

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

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

[0212] Optionally, the URL may also include lightweight application page parameters.

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

[0214] The lightweight application page information acquisition unit is used to acquire lightweight application page information corresponding to the lightweight application page parameters based on the lightweight application page parameters if the judgment result indicates that the application is not installed in the operating system.

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

[0216] Optionally, the lightweight application page may also include business controls for instructing the execution of business processes.

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

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

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

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

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

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

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

[0224] The URL template query unit is used by the application to query a URL template that has a mapping relationship with the scene type information based on the scene type information; the URL template contains a replaceable tag; the replaceable tag is used to identify the position where the information can be entered.

[0225] A replaceable tag replacement unit is used to replace the replaceable tag with the information identifier to obtain a business URL carrying the information identifier.

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

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

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

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

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

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

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

[0233] Optionally, the business parameter information may also include amount information corresponding to the scenario type information; the amount information and the information identifier are concatenated and carried in the rendering parameter information; the first application page may also include the payment amount corresponding to the amount information.

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

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

[0236] The homepage display unit is used to display the homepage of the application based on the homepage URL.

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

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

[0239] The specified page information acquisition unit is used to, when the value of the scenario type information is a specified parameter, obtain the specified page information corresponding to the specified business URL from the specified server corresponding to the specified business URL based on the specified business URL.

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

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

[0242] Figure 13 The embodiments provided in this specification correspond to Figure 9 A schematic diagram of the structure of an NFC-based service execution device. Figure 13 As shown, the device may include:

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

[0244] The information sending module 1304 is used to respond to the near-field communication signal and send a Uniform Resource Locator (URL) to the user terminal device via near-field communication. The URL includes protocol type information, domain name information, and lightweight application card parameters. The protocol type information indicates that the URL conforms to the Hypertext Transfer Security Protocol (HTTP). The lightweight application card parameters are used by the iOS operating system to identify the application as a lightweight application card. The domain name information is used by the user terminal device to launch the application corresponding to the domain name information. The application is used to execute the business process corresponding to the URL.

[0245] based on Figure 13 The embodiments of this specification also provide some specific implementations of the device, which will be described below.

[0246] Optional, Figure 13 The device described herein may further include:

[0247] The trigger operation acquisition module is used to acquire preset trigger operations.

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

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

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

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

[0252] Based on the same idea, this specification also provides devices corresponding to the above methods in its embodiments.

[0253] Figure 14 The embodiments provided in this specification correspond toFigure 2 A schematic diagram of the structure of a user terminal device for implementing business operations. For example... Figure 14 As shown, device 1400 may include:

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

[0255] The memory 1430 stores instructions 1420 that can be executed by the at least one processor 1410, the instructions being executed by the at least one processor 1410 to enable the at least one processor 1410 to:

[0256] The URL of the Uniform Resource Locator (URL) provided by the NFC tag device is obtained through near-field communication. The URL includes protocol type information, domain name information, and mini-application card parameters. The protocol type information indicates that the URL conforms to the Hypertext Transfer Security Protocol (HTTP). The mini-application card parameters are used by the iOS operating system to identify the mini-application card.

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

[0258] Figure 15 The embodiments provided in this specification correspond to Figure 9 A schematic diagram of the structure of an NFC tag device for implementing business operations. For example... Figure 15 As shown, device 1500 may include:

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

[0260] The memory 1530 stores instructions 1520 that can be executed by the at least one processor 1510, the instructions being executed by the at least one processor 1510 to enable the at least one processor 1510 to:

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

[0262] In response to the near-field communication signal, a Uniform Resource Locator (URL) is sent to the user terminal device via near-field communication. The URL includes protocol type information, domain name information, and lightweight application card parameters. The protocol type information indicates that the URL conforms to the Hypertext Transfer Security Protocol (HTTP). The lightweight application card parameters are used by the iOS operating system to identify the application as a lightweight application card. The domain name information is used by the user terminal device to launch the application corresponding to the domain name information. The application is used to execute the business process corresponding to the URL.

[0263] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0264] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on its differences from other embodiments. In particular, for... Figure 14 and Figure 15 As the device shown is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0265] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0266] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

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

[0268] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

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

[0270] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0271] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0272] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

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

[0274] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

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

[0276] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0277] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0278] This application can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0279] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A NFC-based service execution method applied to a user terminal device, the user terminal device serving as an NFC card reader, and an operating system running on the user terminal device comprising an IOS operating system, an Android operating system or a Harmony operating system; the method comprising: obtaining, by the operating system, a uniform resource locator (URL) provided by an NFC tag device via near field communication (NFC); the URL containing protocol type information, domain name information and a light application card parameter; the protocol type information indicating that the URL conforms to the hypertext transfer protocol secure (HTTPS) or the hypertext transfer protocol (HTTP); if the operating system is an IOS operating system, determining, by the IOS operating system, a target application corresponding to the URL according to the domain name information; if the IOS operating system is an IOS operating system with a light application function, displaying, by the IOS operating system with the light application function, a light application card according to the light application card parameter, and starting the target application in response to a triggering operation on the light application card in a case where the target application has been installed, so that the target application executes a service flow corresponding to the URL; if the IOS operating system is an IOS operating system of version 13 or below, displaying, by the IOS operating system of version 13 or below, pop-up information corresponding to the target application, and starting the target application in response to a triggering operation on the pop-up information in a case where the target application has been installed, so that the target application executes a service flow corresponding to the URL; if the operating system is an Android operating system or a Harmony operating system, starting, by the Android operating system or the Harmony operating system, a target application corresponding to the URL in a case where the target application has been installed, and sending the URL to the target application, so that the target application executes a service flow corresponding to the URL.

2. The method of claim 1, wherein the displaying of the light application card according to the light application card parameter specifically comprises: obtaining light application card information corresponding to the light application card parameter according to the light application card parameter; and displaying a light application card generated based on the light application card information, the light application card containing an application access control for prompting access to the target application. The starting of the target application in response to the triggering operation on the light application card specifically comprises: starting the target application in response to a second triggering operation on the application access control.

3. The method of claim 1, wherein the displaying of the pop-up information specifically comprises: displaying a banner page element; and the banner page element containing information for prompting access to the target application. The starting of the target application in response to the triggering operation on the pop-up information specifically comprises: starting the target application in response to a first triggering operation on the banner page element.

4. The method of claim 1, wherein, The URL further contains a light application page parameter, and the method further comprises: If the operating system is an IOS operating system with a light application function, and the target application is not installed, the operating system acquires light application page information corresponding to the light application page parameter according to the light application page parameter; In the light application corresponding to the light application card, a light application page generated based on the light application page information is displayed; the light application page contains a second download control for prompting a user to download the target application.

5. The method of claim 1, further comprising: If the operating system is an IOS operating system of IOS 13 and below, an Android operating system, or a Harmony operating system, and the target application is not installed, the operating system opens an application download page corresponding to the URL using a browser; the application download page displays a download request control; the download request control is used to download the target application after a trigger operation.

6. The method of claim 1, wherein the URL further contains service parameter information; the service parameter information is used as a basis for the target application to execute a service process corresponding to the URL.

7. The method of claim 6, wherein, The service parameter information contains scene type information and information identifier corresponding to the scene type information; the method further comprises: The target application queries a URL template having a mapping relationship with the scene type information according to the scene type information; the URL template contains a replaceable mark; the replaceable mark is used to identify a position where the information identifier can be input; The information identifier is used to replace the replaceable mark to obtain a service URL carrying the information identifier; A service process is executed based on the service URL.

8. The method of claim 7, wherein, The service URL contains rendering parameter information used to render a first application page; The information identifier is carried in the rendering parameter information; the execution of the service process based on the service URL specifically comprises: A first application page is rendered based on the rendering parameter information.

9. The method of claim 8, wherein, The first application page contains a preset control; after the first application page is rendered based on the rendering parameter information, the method further comprises: In response to a trigger operation of the user on the preset control, a service request is sent to an application server of the target application; the service request carries the information identifier; Service processing result information determined by the application server in response to the service request is received; the service processing result information is determined by the application server according to service description information; the service description information is obtained by the application server according to the information identifier; A second application page generated based on the service processing result information is displayed.

10. The method of claim 8, wherein, The service parameter information further contains amount information corresponding to the scene type information; the amount information is concatenated with the information identifier and carried in the rendering parameter information; the first application page further contains a payment amount corresponding to the amount information.

11. The method of claim 7, further comprising: If no URL template having a mapping relationship with the scene type information is queried, a home page URL of the target application is acquired; Display a home page of the target application based on the home page URL.

12. The method of claim 6, wherein, The business parameter information includes scene type information and a specified business URL corresponding to the scene type information; and the method further includes: In a case where the value of the scene type information is a specified parameter, the target application acquires specified page information corresponding to the specified business URL from a specified server corresponding to the specified business URL based on the specified business URL; Display a specified page generated based on the specified page information.

13. The method of any one of claims 1 to 12, wherein, The target application includes a payment application, and the business process includes a payment process.

14. A NFC-based business execution method applied to an NFC tag device, the method comprising: receiving a near field communication signal transmitted by a user terminal device; in response to the near field communication signal, sending a uniform resource locator (URL) to the user terminal device through a near field communication mode; an operating system running on the user terminal device includes an IOS operating system, an Android operating system, or a Harmony operating system; the URL includes protocol type information, domain name information, and a light application card parameter; the protocol type information indicates that the URL conforms to a hypertext transfer protocol secure (HTTPS) or a hypertext transfer protocol (HTTP); wherein the domain name information is used by the IOS operating system as a basis for determining a target application corresponding to the URL; the light application card parameter is used by the IOS operating system with a light application function to identify a light application card, the light application card is used to start the target application in a case where the target application has been installed, in response to a trigger operation, so that the target application executes a business process corresponding to the URL; the URL is used to trigger an IOS 13 and later version of the IOS operating system to display pop-up information corresponding to the target application, the pop-up information is used to start the target application in a case where the target application has been installed, in response to a trigger operation, so that the target application executes a business process corresponding to the URL; the URL is used to trigger the Android operating system or the Harmony operating system to start the target application and send the URL to the target application in a case where the target application corresponding to the URL has been installed, so that the target application executes a business process corresponding to the URL.

15. The method of claim 14, wherein, The URL further includes a light application page parameter; the light application page parameter is used by the IOS operating system with a light application function to display a light application page in a light application corresponding to the light application card in a case where the operating system is the IOS operating system with a light application function and the target application has not been installed, the light application page is used to prompt to download the target application.

16. The method of claim 14, wherein, The URL further includes business parameter information; the business parameter information is used as a basis for the target application to execute a business process corresponding to the URL.

17. The method of claim 16, wherein the business parameter information includes scene type information and information identification corresponding to the scene type information. wherein The scene type information is used to query a URL template having a mapping relationship with the scene type information. The URL template contains replaceable marks; The replaceable marks are used to identify positions where the information identifier can be inputted; The information identifier is used to replace the replaceable marks in the URL template to obtain a service URL carrying the information identifier; the service URL is used to execute the service process corresponding to the URL.

18. The method of claim 17, wherein, The service parameter information further contains amount information corresponding to the scenario type information; the amount information is spliced with the information identifier and carried in rendering parameter information of the service URL; The rendering parameter information is used to render a first application page of the target application; the first application page contains a payment amount corresponding to the amount information.

19. The method of claim 16, wherein, The service parameter information contains scenario type information and a specified service URL corresponding to the scenario type information; the specified service URL is used to, when the value of the scenario type information is a specified parameter, cause the target application to obtain specified page information corresponding to the specified service URL from a specified server corresponding to the specified service URL; the specified page information is used to generate a specified page displayed in the target application.

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

21. The method of claim 20, wherein, The information identifier is a token generated by the application server according to the service description information.

22. The method of claim 20, wherein, The trigger operation includes initiating a collection operation or a payment operation, the target application includes a payment application, and the service process includes a payment process.

23. The method of any one of claims 14 to 22, wherein, The URL is pre-burned in the NFC tag device.

24. The method of any one of claims 14 to 22, wherein, The URL is a URL corresponding to the service generated when the service occurs.

25. An NFC-based service execution method applied to a user terminal device, the user terminal device serving as an NFC reader, the method comprising: an operating system obtaining a uniform resource locator (URL) provided by an NFC tag device through near field communication (NFC); the URL containing domain name information, light application card parameters, and service parameter information; the light application card parameters being used to be recognized by an IOS operating system with light application function in the form of a light application card, the light application card being used to prompt access to a target application corresponding to the domain name information; the service parameter information being used as a basis for the target application to execute a service process corresponding to the URL when the target application is installed in the operating system; if the target application is installed in the operating system, the target application is invoked. The target application is used to execute a service process corresponding to the URL based on the service parameter information.

26. The method of claim 25, wherein, The operating system is an IOS operating system; and the method further includes: According to the domain name information, the target application corresponding to the URL is determined.

27. The method of claim 26, wherein, The operating system is an IOS operating system with a light application function; Before arousing the target application, the method further includes: According to the light application card parameter, a light application card is displayed to the user; If the target application has been installed in the operating system, the target application is aroused, and specifically, the method includes: If the target application has been installed in the IOS operating system with a light application function, the target application is aroused in response to a triggering operation on the light application card.

28. The method of claim 26, wherein, The operating system is an IOS operating system with a light application function; The URL further includes a light application page parameter; and the method further includes: If the target application has not been installed in the IOS operating system with a light application function, light application page information corresponding to the light application page parameter is acquired; In a light application corresponding to the light application card, a light application page generated based on the light application page information is displayed; and the light application page includes a second download control for prompting the user to download the target application.

29. The method of claim 26, wherein, The operating system is an IOS operating system of version 13 or below; and before arousing the target application, the method further includes: A banner page element is displayed; the banner page element includes information for prompting to access the target application; A first triggering operation of the user on the banner page element is acquired; If the target application has been installed in the operating system, the target application is aroused, and specifically, the method includes: If the target application has been installed in the IOS operating system of version 13 or below, the target application is aroused in response to the first triggering operation.

30. The method of claim 29, further comprising: If the target application has not been installed in the IOS operating system of version 13 or below, a browser is used to open an application download page corresponding to the URL; the application download page displays a download request control; and the download request control is used to download the target application in response to a triggering operation.

31. The method of claim 25, wherein, The operating system is an Android operating system or a Hong Meng operating system; If the target application has not been installed in the operating system, a browser is used to open an application download page corresponding to the URL; the application download page displays a download request control; and the download request control is used to download the target application in response to a triggering operation.

32. The method of claim 25, wherein the service parameter information includes scene type information and an information identifier corresponding to the scene type information; and the method further includes: The target application queries a URL template having a mapping relationship with the scene type information according to the scene type information; The URL template includes a replaceable mark; The replaceable mark is used to identify a position where the information identifier can be input; The replaceable mark is replaced by the information identifier to obtain a service URL carrying the information identifier. Perform a business process based on the business URL.

33. The method of claim 32, wherein the business URL comprises rendering parameter information for rendering a first application page; the information is carried in the rendering parameter information; and performing a business process based on the business URL specifically comprises: rendering the first application page based on the rendering parameter information.

34. The method of claim 33, wherein, The first application page comprises a preset control; and after rendering the first application page based on the rendering parameter information, the method further comprises: in response to a triggering operation of the preset control by a user, sending a business request to an application server of the target application; the business request carries the information identifier; receiving business processing result information determined by the application server in response to the business request; the business processing result information is determined by the application server according to business description information; the business description information is obtained by the application server according to the information identifier; displaying a second application page generated based on the business processing result information.

35. The method of claim 33, wherein, The business parameter information further comprises amount information corresponding to the scene type information; the amount information is concatenated with the information identifier and carried in the rendering parameter information; and the first application page further comprises a payment amount corresponding to the amount information.

36. The method of claim 32, further comprising: if no URL template having a mapping relationship with the scene type information is found, obtaining a home page URL of the target application; displaying a home page of the target application based on the home page URL.

37. The method of claim 25, wherein, The business parameter information comprises scene type information and a specified business URL corresponding to the scene type information; and the method further comprises: if the value of the scene type information is a specified parameter, the target application obtains specified page information corresponding to the specified business URL from a specified server corresponding to the specified business URL based on the specified business URL; displaying a specified page generated based on the specified page information.

38. The method of any one of claims 32 to 37, wherein, The operating system comprises an IOS operating system, an Android operating system, or a Hongmeng operating system.

39. The method of any one of claims 25 to 37, wherein, The target application comprises a payment application, and the business process comprises a payment process.

40. A NFC-based business execution method applied to an NFC tag device, the method comprising: receiving a near field communication signal transmitted by a user terminal device; in response to the near field communication signal, sending a uniform resource locator (URL) to the user terminal device through a near field communication mode; the URL comprises domain name information, light application card parameters, and business parameter information; the light application card parameters are used to be recognized by an IOS operating system with light application function in the form of a light application card, and the light application card is used to prompt access to a target application corresponding to the domain name information; the business parameter information is used as a basis for the target application to perform a business process corresponding to the URL when the target application is installed in the operating system and is invoked.

41. The method of claim 40, wherein, the domain name information is used as a basis for the IOS operating system to determine the target application corresponding to the URL.

42. The method of claim 40, wherein, The URL further comprises a light application page parameter; The light application page parameter is used for displaying a light application page in a light application corresponding to the light application card by an IOS operating system with a light application function in a case where the IOS operating system with the light application function is installed and the target application is not installed.

43. The method of claim 40, wherein, The business parameter information comprises scene type information and information identifier corresponding to the scene type information; The scene type information is used for querying a URL template having a mapping relationship with the scene type information; The URL template comprises a replaceable mark; The replaceable mark is used for identifying a position where the information identifier can be input; The information identifier is used for replacing the replaceable mark in the URL template to obtain a business URL carrying the information identifier; and the business URL is used for executing a business process.

44. The method of claim 43, wherein, The business parameter information further comprises amount information corresponding to the scene type information; and the amount information is concatenated with the information identifier and carried in rendering parameter information of the business URL. The rendering parameter information is used for rendering a first application page of the target application; and the first application page comprises a payment amount corresponding to the amount information.

45. The method of claim 40, wherein, The business parameter information comprises scene type information and specified business URL corresponding to the scene type information; the specified business URL is used for acquiring specified page information corresponding to the specified business URL from a specified server corresponding to the specified business URL when a value of the scene type information is a specified parameter; and the specified page information is used for generating a specified page displayed in the target application.

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

47. The method of claim 46, wherein, The information identifier is a token generated by the application server according to the business description information.

48. The method of claim 46, wherein, The trigger operation comprises initiating a collection operation or a payment operation; the target application comprises a payment application; and the business process comprises a payment process.

49. The method of any one of claims 40 to 48, wherein, The URL is pre-burned in the NFC tag device.

50. The method of any one of claims 40 to 48, wherein, The URL is a URL corresponding to the business generated when the business occurs.

51. A NFC-based business execution method applied to a user terminal device, the user terminal device serving as an NFC card reader, the method comprising: obtaining a uniform resource locator (URL) provided by an NFC tag device through a near field communication mode; The URL contains scene type information and information identifier corresponding to the scene type information; The target application corresponding to the URL queries a URL template having a mapping relationship with the scene type information according to the scene type information; The URL template contains replaceable marks; The replaceable marks are used to identify positions where the information identifier can be input; The replaceable marks are replaced by the information identifier to obtain a service URL carrying the information identifier; A service flow is performed based on the service URL.

52. The method of claim 51, wherein, The service URL contains rendering parameter information used for rendering a first application page; The information identifier is carried in the rendering parameter information; and the service flow is performed based on the service URL, specifically including: A first application page is rendered based on the rendering parameter information.

53. The method of claim 52, wherein, The first application page contains a preset control; after the first application page is rendered based on the rendering parameter information, the method further includes: In response to a triggering operation of the preset control by a user, a service request is sent to an application server of the target application; the service request carries the information identifier; Service processing result information determined by the application server in response to the service request is received; the service processing result information is determined by the application server according to service description information; the service description information is obtained by the application server according to the information identifier; A second application page generated based on the service processing result information is displayed.

54. The method of claim 52, wherein, The service URL further contains amount information corresponding to the scene type information; the amount information is concatenated with the information identifier and carried in the rendering parameter information; and the first application page further contains a payment amount corresponding to the amount information.

55. The method of claim 51, further comprising: if no URL template having a mapping relationship with the scene type information is queried, obtaining a home page URL of the target application; and displaying a home page of the target application based on the home page URL.

56. The method of claim 51, wherein, The URL further contains a specified service URL corresponding to the scene type information; and the method further includes: if a value of the scene type information is a specified parameter, obtaining specified page information corresponding to the specified service URL from a specified server corresponding to the specified service URL based on the specified service URL; and displaying a specified page generated based on the specified page information.

57. The method of any one of claims 51 to 56, wherein, The target application includes a payment application, and the service flow includes a payment flow.

58. A NFC-based service execution method, applied to an NFC tag device, and including: receiving a near field communication signal transmitted by a user terminal device; in response to the near field communication signal, sending a uniform resource locator (URL) to the user terminal device through a near field communication mode; the URL contains scene type information and information identifier corresponding to the scene type information; and the information identifier is carried in the rendering parameter information; and the service flow is performed based on the service URL, specifically including: a first application page is rendered based on the rendering parameter information. The scene type information is used for querying, by a target application corresponding to the URL, a URL template having a mapping relationship with the scene type information; the URL template includes a replaceable mark; and the replaceable mark is used for identifying a position at which the information identifier can be input. The information identifier is used for replacing the replaceable mark in the URL template to obtain a service URL carrying the information identifier; and the service URL is used for executing a service process in the target application.

59. The method of claim 58, wherein, The URL further includes amount information corresponding to the scene type information; and the amount information is concatenated with the information identifier and carried in rendering parameter information of the service URL. The rendering parameter information is used for rendering a first application page of the target application; and the first application page includes a payment amount corresponding to the amount information.

60. The method of claim 58, wherein, The URL further includes a specified service URL corresponding to the scene type information; the specified service URL is used for, when a value of the scene type information is a specified parameter, acquiring, by the target application, specified page information corresponding to the specified service URL from a specified server corresponding to the specified service URL; and the specified page information is used for generating a specified page displayed in the target application.

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

62. The method of claim 61, wherein, The information identifier is a token generated by the application server according to the service description information.

63. The method of claim 61, wherein, The trigger operation includes initiating a collection operation or a payment operation, and the target application includes a payment application.

64. The method of any one of claims 58 to 63, wherein, The URL is pre-burned in the NFC tag device.

65. The method of any one of claims 58 to 63, wherein, The URL is a URL corresponding to the service generated when the service occurs.

66. An NFC-based service execution apparatus applied to a user terminal device, the user terminal device serving as an NFC card reader, and an operating system running on the user terminal device including an IOS operating system, an Android operating system, or a Harmony operating system; the apparatus comprising: a URL obtaining module configured to obtain, by the operating system, a uniform resource locator (URL) provided by an NFC tag device in a near field communication (NFC) manner; the URL including protocol type information, domain name information, and a light application card parameter; the protocol type information indicating that the URL conforms to a hypertext transfer protocol secure (HTTPS) or a hypertext transfer protocol (HTTP); an application starting module configured to: If the operating system is an IOS operating system, the IOS operating system determines a target application corresponding to the URL according to the domain name information; If the IOS operating system is an IOS operating system with light application function, the IOS operating system with light application function displays a light application card according to the light application card parameter, and starts the target application in response to a triggering operation on the light application card in the case that the target application has been installed, so that the target application executes a business process corresponding to the URL; If the IOS operating system is an IOS operating system of IOS13 and below, the IOS operating system of IOS13 and below displays pop-up information corresponding to the target application, and starts the target application in response to a triggering operation on the pop-up information in the case that the target application has been installed, so that the target application executes a business process corresponding to the URL; If the operating system is an Android operating system or a Hongmeng operating system, the Android operating system or the Hongmeng operating system starts the target application corresponding to the URL in the case that the target application has been installed, and sends the URL to the target application, so that the target application executes a business process corresponding to the URL.

67. An NFC-based business execution device applied to an NFC tag device, the device comprising: a signal receiving module configured to receive a near field communication signal transmitted by a user terminal device; an information sending module configured to send a uniform resource locator (URL) to the user terminal device through a near field communication mode in response to the near field communication signal; an operating system running on the user terminal device comprises an IOS operating system, an Android operating system, or a Hongmeng operating system; the URL contains protocol type information, domain name information, and light application card parameters; the protocol type information indicates that the URL conforms to the hypertext transfer protocol secure (HTTPS) or the hypertext transfer protocol (HTTP); wherein the domain name information is used by the IOS operating system as a basis for determining a target application corresponding to the URL; the light application card parameter is used by an IOS operating system with light application function to identify a light application card, and the light application card is used to start the target application in response to a triggering operation in the case that the target application has been installed, so that the target application executes a business process corresponding to the URL; the URL is used to trigger an IOS operating system of IOS13 and below to display pop-up information corresponding to the target application, and the pop-up information is used to start the target application in response to a triggering operation in the case that the target application has been installed, so that the target application executes a business process corresponding to the URL; the URL is used to trigger an Android operating system or a Hongmeng operating system to start the target application corresponding to the URL in the case that the target application has been installed, and send the URL to the target application, so that the target application executes a business process corresponding to the URL. 68.A NFC-based service execution apparatus applied to a user terminal device, the user terminal device serving as a NFC reader, the apparatus comprising: a URL obtaining module configured to obtain a uniform resource locator (URL) provided by a NFC tag device through a near field communication (NFC) manner; the URL containing domain name information, light application card parameters and service parameter information; the light application card parameters being used for being recognized by an IOS operating system with light application function in a light application card manner, the light application card being used for prompting access to a target application corresponding to the domain name information; the service parameter information being used for serving as a basis for the target application to execute a service flow corresponding to the URL in a case where the target application has been installed in the operating system; an application starting module configured to, if the target application has been installed in the operating system, invoke the target application; the target application being configured to execute the service flow corresponding to the URL based on the service parameter information. 69.A NFC-based service execution apparatus applied to a NFC tag device, the apparatus comprising: a signal receiving module configured to receive a near field communication signal transmitted by a user terminal device; an information sending module configured to, in response to the near field communication signal, send a uniform resource locator (URL) to the user terminal device through a near field communication manner; the URL containing domain name information, light application card parameters and service parameter information; the light application card parameters being used for being recognized by an IOS operating system with light application function in a light application card manner, the light application card being used for prompting access to a target application corresponding to the domain name information; the service parameter information being used for serving as a basis for the target application to execute a service flow corresponding to the URL in a case where the target application has been installed in the operating system and the target application is invoked. 70.A NFC-based service execution apparatus applied to a user terminal device, the user terminal device serving as a NFC reader, the apparatus comprising: a URL obtaining module configured to obtain a uniform resource locator (URL) provided by a NFC tag device through a near field communication (NFC) manner; the URL containing scene type information and information identifier corresponding to the scene type information; a URL template obtaining module configured to, according to the scene type information, the target application corresponding to the URL queries a URL template having a mapping relationship with the scene type information; the URL template containing a replaceable mark; the replaceable mark being used for identifying a position where the information identifier can be input; a service URL determining module configured to replace the replaceable mark with the information identifier to obtain a service URL carrying the information identifier; a service flow execution module configured to execute a service flow based on the service URL. 71.A NFC-based service execution apparatus applied to a NFC tag device, the apparatus comprising: a signal receiving module configured to receive a near field communication signal transmitted by a user terminal device; The information sending module is configured to send a uniform resource locator (URL) to the user terminal device through near field communication in response to the near field communication signal, wherein the URL contains scene type information and an information identifier corresponding to the scene type information. The scene type information is used to query a URL template having a mapping relationship with the scene type information by a target application corresponding to the URL. The information identifier is used to replace the replaceable mark in the URL template to obtain a service URL carrying the information identifier. The service URL is used to execute a service process in the target application.

72. A user terminal device, which is configured to serve as an NFC card reader, the user terminal device comprising: at least one processor; and a memory connected to the at least one processor in communication; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: obtain a uniform resource locator (URL) provided by an NFC tag device through near field communication, wherein the URL contains protocol type information, domain name information, and a light application card parameter; an operating system running on the user terminal device includes an IOS operating system, an Android operating system, or a Harmony operating system; and the protocol type information indicates that the URL complies with the Hypertext Transfer Protocol Secure (HTTPS) or the Hypertext Transfer Protocol (HTTP). If the operating system is an IOS operating system, the IOS operating system determines a target application corresponding to the URL according to the domain name information. If the IOS operating system is an IOS operating system with a light application function, the IOS operating system with the light application function displays a light application card according to the light application card parameter, and starts the target application in response to a triggering operation on the light application card if the target application has been installed, so that the target application executes a service process corresponding to the URL. If the IOS operating system is an IOS operating system of version 13 or below, the IOS operating system of version 13 or below displays pop-up information corresponding to the target application, and starts the target application in response to a triggering operation on the pop-up information if the target application has been installed, so that the target application executes a service process corresponding to the URL. If the operating system is an Android operating system or a Harmony operating system, the Android operating system or the Harmony operating system starts the target application corresponding to the URL and sends the URL to the target application if the target application has been installed, so that the target application executes a service process corresponding to the URL.

73. An NFC tag device, comprising: at least one processor; and a memory connected to the at least one processor in communication; wherein The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: receive a near field communication signal transmitted by a user terminal device; in response to the near field communication signal, send a uniform resource locator URL to the user terminal device in a near field communication manner; an operating system running on the user terminal device includes an IOS operating system, an Android operating system, or a Harmony operating system; the URL contains protocol type information, domain name information, and light application card parameters; the protocol type information indicates that the URL conforms to the Hypertext Transfer Protocol Secure or the Hypertext Transfer Protocol; wherein the domain name information is used as a basis for determining a target application corresponding to the URL by the IOS operating system; the light application card parameter is used to be recognized by the IOS operating system with light application function in the form of a light application card, and the light application card is used to start the target application in response to a trigger operation in the case that the target application has been installed, so that the target application executes a business process corresponding to the URL; the URL is used to trigger the IOS 13 and below version IOS operating system to display pop-up information corresponding to the target application, and the pop-up information is used to start the target application in response to a trigger operation in the case that the target application has been installed, so that the target application executes a business process corresponding to the URL; the URL is used to trigger the Android operating system or the Harmony operating system to start the target application corresponding to the URL and send the URL to the target application in the case that the target application has been installed, so that the target application executes a business process corresponding to the URL.

74. A user terminal device, the user terminal device as an NFC card reader, the user terminal device comprising: at least one processor; and, a memory in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: acquire a uniform resource locator URL provided by an NFC tag device in a near field communication manner; the URL contains domain name information, light application card parameters, and business parameter information; the light application card parameter is used to be recognized by the IOS operating system with light application function in the form of a light application card, and the light application card is used to prompt to access a target application corresponding to the domain name information; the business parameter information is used as a basis for the target application to execute a business process corresponding to the URL in the case that the target application has been installed in the operating system; if the target application has been installed in the operating system, the target application is invoked; the target application is used to execute a business process corresponding to the URL based on the business parameter information.

75. An NFC tag device, comprising: at least one processor; and, a memory in communication connection with the at least one processor; wherein The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: receive a near field communication signal transmitted by a user terminal device; in response to the near field communication signal, send a uniform resource locator URL to the user terminal device by near field communication; the URL contains domain name information, light application card parameters and service parameter information; the light application card parameters are used to be recognized by an IOS operating system with light application function in the form of a light application card, and the light application card is used to prompt access to a target application corresponding to the domain name information; the service parameter information is used as a basis for the target application to execute a service process corresponding to the URL in the case that the target application is installed in the operating system and is invoked. 76.A user terminal device, serving as an NFC card reader, comprising: at least one processor; and a memory in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: obtain a uniform resource locator URL provided by an NFC tag device by near field communication; the URL contains scene type information and information identifier corresponding to the scene type information; a target application corresponding to the URL queries a URL template having a mapping relationship with the scene type information according to the scene type information; the URL template contains replaceable markers; the replaceable markers are used to identify positions where the information identifier can be input; the information identifier is used to replace the replaceable markers to obtain a business URL carrying the information identifier; a service process is executed based on the business URL. 77.An NFC tag device, comprising: at least one processor; and a memory in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: receive a near field communication signal transmitted by a user terminal device; in response to the near field communication signal, send a uniform resource locator URL to the user terminal device by near field communication; the URL contains scene type information and information identifier corresponding to the scene type information; wherein the scene type information is used by a target application corresponding to the URL to query a URL template having a mapping relationship with the scene type information; the URL template contains replaceable markers; the replaceable markers are used to identify positions where the information identifier can be input; the information identifier is used to replace the replaceable markers in the URL template to obtain a business URL carrying the information identifier; the business URL is used to execute a service process in the target application.

Images