CN118555562A - Near field communication service processing method, device and equipment - Google Patents

Abstract

The embodiment of the specification discloses a near field communication service processing method. The method is applied to cashier equipment and comprises the following steps: acquiring service parameters to be processed generated by a local cashier application, wherein the cashier application is operated based on a local browser; generating a custom protocol website according to the service parameters to be processed and the protocol type custom to the URL protocol; in the cashing application, a user-defined protocol website is accessed through a browser to communicate with a receiving service interface program deployed on cashing equipment, and the receiving service interface program is triggered to transmit service parameters to be processed to inter-equipment communication driving software deployed on the cashing equipment through communication, wherein the service interface program communication and the inter-equipment communication driving software are provided by a service provider of NFC payment equipment, and the service parameters to be processed are transmitted from the cashing equipment to the NFC payment equipment in a corresponding communication mode through the inter-equipment communication driving software and are used for the NFC payment equipment to execute target services.

Description

Near field communication service processing method, device and equipment

Technical Field

The present invention relates to the field of near field communication technology, and in particular to near field communication service processing methods, devices and equipment.

Background Art

Near Field Communication (NFC) is a short-range, high-frequency radio technology that operates at a frequency of 13.56MHz within a distance of 20cm. It is an integration of contactless radio frequency identification (RFID) and interconnection technology, providing a very safe and fast communication method for various electronic products.

With the popularization of NFC-enabled smartphones, NFC technology is also being used more in the payment field. For example, merchants deploy NFC payment devices at checkout counters, and users can make payments through NFC-enabled mobile phones by interacting with NFC payment devices, which is very convenient.

At present, NFC payment devices and corresponding payment applications are provided by specialized payment service providers, and merchants usually have deployed cash register devices provided by other service providers at the cash register counter, as well as cash register applications used on cash register devices, mainly Software as a Service (SaaS) cash register applications. For cash register devices, cross-device interaction with NFC payment devices is required in order to use the capabilities of NFC payment devices normally.

For NFC payment devices that support Bluetooth communication, they are often connected to cash registers based on Bluetooth communication. Accordingly, it is necessary to install the NFC device Bluetooth driver software provided by the NFC payment device service provider on the cash register in advance to facilitate cross-device communication. However, in actual applications, many SaaS cash register applications are run based on the browser on the cash register device. In this case, for the merchant side, it is difficult and costly to implement the cash register application to call the Bluetooth service across processes to interact with the NFC payment device for data, which is not conducive to expanding the access to NFC payment devices for cash registers.

Based on this, for the scenario of a cash register application running on a browser on a cash register device, there is a need for a solution that helps to expand access to NFC payment devices for the cash register device in a more friendly manner.

Summary of the invention

One or more embodiments of the present specification provide a near field communication service processing method, apparatus and device to solve the following technical problem: For the scenario of a cash register application running based on a browser on a cash register device, a solution is needed to help the cash register device to be more friendly in expanding access to NFC payment devices.

To solve the above technical problems, one or more embodiments of this specification are implemented as follows:

One or more embodiments of this specification provide a near field communication service processing method, which is applied to a cash register device. The method includes:

Obtaining a to-be-processed business parameter generated by a local cashier application, where the cashier application is run based on a local browser;

Generate a custom protocol URL according to the service parameters to be processed and the custom protocol type for the URL protocol;

The custom protocol website is accessed through the browser in the cash register application to communicate with the receiving service interface program deployed on the cash register device, and through the communication, the receiving service interface program is triggered to pass the service parameters to be processed to the inter-device communication driver software deployed on the cash register device, wherein the service interface program communication and the inter-device communication driver software are provided by the service provider of the NFC payment device;

The service parameters to be processed are sent from the cash register device to the NFC payment device through the inter-device communication driver software and in a corresponding communication mode, so that the NFC payment device executes the corresponding target service in response to the cash register application.

One or more embodiments of this specification provide a near field communication service processing method, which is applied to a receiving service interface program deployed on a cash register device, wherein the receiving service interface program is provided by a service provider of an NFC payment device, and the method includes:

Determine a cash register application running on the cash register device based on a local browser;

In response to the triggering of the cashier application, the service parameters to be processed generated and transmitted by the cashier application are further transmitted to the inter-device communication driver software deployed on the cashier device, so that the inter-device communication driver software adopts its corresponding communication mode to send the service parameters to be processed from the cashier device to the NFC payment device, so that the NFC payment device executes the corresponding target service;

Among them, the trigger is achieved by accessing the custom protocol website through the browser in the cash register application to communicate with the receiving service interface program; the custom protocol website is generated according to the business parameters to be processed and the protocol type customized for the URL protocol; the inter-device communication driver software is provided by the service provider of the NFC payment device.

One or more embodiments of this specification provide a near field communication service processing device, which is applied to a cash register device. The device includes:

A module for obtaining business parameters to be processed, which obtains business parameters to be processed generated by a local cashier application, wherein the cashier application is run based on a local browser;

A custom protocol website generation module generates a custom protocol website according to the service parameters to be processed and a custom protocol type for the URL protocol;

A receiving service interface program interaction module, in the cash register application, accesses the custom protocol website through the browser to communicate with the receiving service interface program deployed on the cash register device, and through the communication, triggers the receiving service interface program to pass the service parameters to be processed to the inter-device communication driver software deployed on the cash register device, wherein the service interface program communication and the inter-device communication driver software are provided by the service provider of the NFC payment device;

The inter-device business parameter transmission module, through the inter-device communication driver software, adopts its corresponding communication method to send the to-be-processed business parameters from the cash register device to the NFC payment device, so that the NFC payment device executes the corresponding target business in order to respond to the cash register application.

One or more embodiments of this specification provide a near field communication service processing device, which is applied to a receiving service interface program deployed on a cash register device, wherein the receiving service interface program is provided by a service provider of an NFC payment device, and the device includes:

A cashier application determination module, which determines the cashier application running on the cashier device based on the local browser;

The service parameter transmission module, in response to the triggering of the cashier application, further transmits the service parameters to be processed generated and transmitted by the cashier application to the inter-device communication driver software deployed on the cashier device, so that the inter-device communication driver software adopts its corresponding communication mode to send the service parameters to be processed from the cashier device to the NFC payment device, so that the NFC payment device executes the corresponding target service;

Among them, the trigger is achieved by accessing the custom protocol website through the browser in the cash register application to communicate with the receiving service interface program; the custom protocol website is generated according to the business parameters to be processed and the protocol type customized for the URL protocol; the inter-device communication driver software is provided by the service provider of the NFC payment device.

One or more embodiments of this specification provide a near field communication service processing device, which is applied to a cash register device. The near field communication service processing device includes:

at least one processor; and,

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

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

Obtaining a to-be-processed business parameter generated by a local cashier application, where the cashier application is run based on a local browser;

Generate a custom protocol URL according to the service parameters to be processed and the custom protocol type for the URL protocol;

The custom protocol website is accessed through the browser in the cash register application to communicate with the receiving service interface program deployed on the cash register device, and through the communication, the receiving service interface program is triggered to pass the service parameters to be processed to the inter-device communication driver software deployed on the cash register device, wherein the service interface program communication and the inter-device communication driver software are provided by the service provider of the NFC payment device;

The service parameters to be processed are sent from the cash register device to the NFC payment device through the inter-device communication driver software and in a corresponding communication mode, so that the NFC payment device executes the corresponding target service in response to the cash register application.

One or more embodiments of this specification provide a near field communication service processing device, which is applied to a receiving service interface program deployed on a cash register device, wherein the receiving service interface program is provided by a service provider of an NFC payment device, and the near field communication service processing device includes:

at least one processor; and,

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

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

Determine a cash register application running on the cash register device based on a local browser;

In response to the triggering of the cashier application, the service parameters to be processed generated and transmitted by the cashier application are further transmitted to the inter-device communication driver software deployed on the cashier device, so that the inter-device communication driver software adopts its corresponding communication mode to send the service parameters to be processed from the cashier device to the NFC payment device, so that the NFC payment device executes the corresponding target service;

Among them, the trigger is achieved by accessing the custom protocol website through the browser in the cash register application to communicate with the receiving service interface program; the custom protocol website is generated according to the business parameters to be processed and the protocol type customized for the URL protocol; the inter-device communication driver software is provided by the service provider of the NFC payment device.

At least one of the above-mentioned technical solutions adopted in one or more embodiments of the present specification can achieve the following beneficial effects: by actively customizing the protocol type for the URL protocol of the browser on the cash register device and adapting to the corresponding custom protocol, the service provider of the NFC payment device develops a receiving service interface program that supports the custom protocol and deploys it on the cash register device, and the receiving service interface program is used to connect to the inter-device communication driver software (for example, Bluetooth communication driver software) also provided by the service provider of the NFC payment device, so that the cash register application can communicate with the local receiving service interface program by accessing the custom protocol URL in the browser, and then through the receiving service interface program across processes, the custom protocol call is converted into a communication service (for example, Bluetooth service) call for the inter-device communication driver software, so that it can interact with the NFC payment device normally. This method avoids complex development on the merchant side (which may include the cash register application and the service provider of the cash register device), has little impact on the cash register application, and is more friendly. For the scenario of the cash register application running based on the browser on the cash register device, it helps to expand the access to the NFC payment device for the cash register device in a more friendly way, and thus also helps to expand the access to the NFC payment device for more different cash register devices and different cash register applications more efficiently.

BRIEF DESCRIPTION OF THE DRAWINGS

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

FIG1 is a schematic diagram of a process flow of a near field communication service processing method provided by one or more embodiments of this specification;

FIG2 is a flow chart of a solution for performing a cross-process service call based on a URL custom protocol in an application scenario provided by one or more embodiments of this specification;

FIG3 is a flowchart of an example processing scheme for receiving a service interface program provided in one or more embodiments of this specification;

FIG4 is a schematic diagram of a flow chart of a local analysis solution for service parameters to be processed provided by one or more embodiments of this specification;

FIG5 is a flow chart of a differentiated processing solution for NFC inductive interaction gestures provided by one or more embodiments of this specification;

FIG6 is a schematic diagram of the architecture of a specific implementation scheme of a near field communication service processing method provided by one or more embodiments of this specification;

FIG7 is a schematic flow chart of another near field communication service processing method provided by one or more embodiments of this specification;

FIG8 is a schematic diagram of the structure of a near field communication service processing device provided by one or more embodiments of this specification;

FIG9 is a schematic diagram of the structure of another near field communication service processing device provided by one or more embodiments of this specification;

FIG10 is a schematic diagram of the structure of a near field communication service processing device provided by one or more embodiments of this specification;

FIG. 11 is a schematic diagram of the structure of another near field communication service processing device provided by one or more embodiments of this specification.

DETAILED DESCRIPTION

The embodiments of this specification provide a near field communication service processing method, apparatus, device, and storage medium.

In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this application, not all of them. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

Regarding the problems mentioned in the background technology, the reasons leading to the problem include: the browser supports a relatively general protocol, while the Bluetooth communication driver software is provided by the service provider of the NFC payment device and is relatively specialized. Therefore, there are naturally difficulties in docking the interface and protocol. Not only that, the cash register application itself is inconsistent with the service provider of the NFC payment device, which further increases the difficulty of docking and makes it difficult for the browser-based cash register application to call the Bluetooth service across processes (which can refer to the browser process and the Bluetooth communication driver software process, which are not the same process).

In order to solve these problems, this application considers that the service provider of the NFC payment device actively adds a custom protocol type of the URL protocol for the browser on which the cash register application on the cash register device is based, and provides a receiving service interface program that supports the custom protocol corresponding to the protocol type (also implemented by the service provider of the NFC payment device), which serves as a bridge between the cash register application and the Bluetooth communication driver software provided by the service provider of the NFC payment device. The custom protocol is called through the browser to open the bridge, thereby further realizing cross-process Bluetooth calls.

In this way, for cash register applications, it is possible to easily and reliably call such relatively proprietary Bluetooth services, with little need for merchant development and modification. For NFC payment device service providers, they can also reuse their own modification results at low cost on more other cash register devices and cash register applications, thereby bringing convenience to more merchants and increasing their enthusiasm for expanding access to NFC payment devices.

Based on this general idea, the solution of this application will be further described below.

FIG1 is a flowchart of a near field communication service processing method provided by one or more embodiments of this specification. The method is applied to a cash register device, and specifically, corresponding steps can be executed by one or more software modules on the cash register device.

The cash register device needs to deploy a basic cash register application (the application can be software used by PCs or mobile terminals such as smartphones) to perform cash register work. Some cash register devices have their own cash register application, which is usually a hardware and software integrated solution provided by the same service provider; of course, merchants can also choose a cash register application provided by another service provider for the current cash register device as needed, especially cash register devices such as Windows POS machines (referring to those based on the Windows operating system), which are flexible and widely used. In addition, cash register devices can also be based on other common operating systems, or even niche self-developed systems.

In one or more embodiments of this specification, a cash register application that needs to be run based on a browser is deployed on the cash register device, such as a SaaS cash register application (which can be referred to as Web SaaS) that runs based on a browser. The method also involves an NFC payment device, and the cash register device and the NFC payment device can be connected and communicated through methods such as Bluetooth (for ease of description, this method is mainly used as an example), and the NFC payment device service assists the work of the cash register device.

In order to achieve inter-device communication, it is necessary to pre-deploy the inter-device communication driver software (e.g., Bluetooth communication driver software) provided by the NFC payment device on the cash register device. Taking Bluetooth as an example, the inter-device communication driver software in this application can refer to the software on the cash register device that provides an interface to send cash register instructions and receive data to the NFC payment device via a Bluetooth transmitter.

Cash register equipment and NFC payment equipment can be provided by different service providers (usually independent companies that may not have a cooperative relationship with each other). Cash register applications and NFC payment equipment (of course, NFC payment equipment also has supporting NFC payment software) can be provided by different service providers.

Cash registers are basic devices that merchants usually use at cash registers. Common ones are desktop or handheld POS machines, etc. Their operating systems can be diverse, such as Windows, Linux or mobile operating systems, etc. They can support one or more basic payment methods, such as bank card payment, membership card payment, QR code payment, etc. However, they do not support NFC payment yet. Therefore, NFC payment devices are used to expand their NFC business support capabilities. Users can sense mobile terminals such as smartphones and smart watches that support NFC functions by bringing them close to NFC payment devices, and then perform payment-related services based on near-field communication.

The process in Figure 1 includes the following steps:

S102: Acquire the to-be-processed business parameters generated by a local cashier application, where the cashier application runs based on a local browser.

The cashier application generates pending business parameters based on the operation of the user (cashier or consumer, etc.). The pending business parameters reflect the target business itself (such as cashier instructions, etc.), or may further include specific data required to execute the target business. For example, the target business may be a payment-related business (such as payment of the current order, transfer, member login, discount collection, etc.), and the specific data may be the business type, amount to be paid, transfer amount, member type, discount type, etc.

The target service may be executed by other existing methods (such as scanning a code, swiping a card, etc.) of the cash register application, but in this application, it can be attempted to be at least partially executed by the NFC payment device. Of course, this is not mandatory, and the user can be allowed to independently choose the other method to execute. If the user does not cooperate with the NFC method, the NFC payment device can continue to be idle and standby.

In addition, under the premise of minimizing the cost impact on the merchant side, the existing business can be modified in advance or some new business can be created by adapting to NFC payment devices. In this case, the corresponding target business may need to be executed normally in NFC mode, so that NFC payment devices can be more fully demonstrated and it will also help bring more convenience to users.

S104: Generate a custom protocol URL according to the service parameters to be processed and the custom protocol type for the URL protocol.

URL, the full name of which is Uniform Resource Locator, is often referred to as a web address, or URL for short. An exemplary format is: [protocol type]://[server address]:[port number]/[resource level UNIX file path][file name]?[query]#[fragment ID]. HTTP is one of the most commonly used protocol types. Based on the HTTP protocol, you can access an HTTP URL and initiate an HTTP request to interact with a remote server, so as to achieve business purposes such as downloading web content to display in a local browser.

Based on the above-mentioned format characteristics, this application intends to customize the protocol type of the URL protocol, and accordingly create a custom protocol corresponding to the protocol type to indicate that the URL under the custom protocol is used to access the locally specified interface program instead of accessing the remote server, thereby facilitating the conversion of the custom protocol call into a proprietary service call locally.

In one or more embodiments of the present specification, in addition to the custom protocol type, a field carrying the service parameters to be processed is also customized in the URL format, so that the service parameters can be locally transmitted and processed through the custom protocol URL, in preparation for continuing to transmit and process the service parameters across devices. Of course, the field of the specific instruction action can also be customized in the URL format to indicate what action the interface program or other local modules behind the interface program, or other devices as the recipient need to perform, thereby effectively improving the flexibility of the custom protocol and helping to expand more special services.

S106: In the cash register application, the custom protocol website is accessed through the browser to communicate with the receiving service interface program deployed on the cash register device, and through the communication, the receiving service interface program is triggered to pass the service parameters to be processed to the inter-device communication driver software deployed on the cash register device, wherein the service interface program communication and the inter-device communication driver software are provided by the service provider of the NFC payment device.

In one or more embodiments of the present specification, the receiving service interface program is developed according to the above-mentioned custom protocol, and the receiving service interface program can be located according to the custom protocol and the custom protocol website, so as to call the interface provided by the receiving service interface program by accessing the custom protocol website, thereby facilitating the indirect access to the process of the inter-device communication driver software by stepping out of the browser process through the receiving service interface program. Since the communication of the receiving service interface program itself is also provided by the service provider of the NFC payment device, the compatibility between the receiving service interface program and the inter-device communication driver software provided by the service provider of the same NFC payment device can be more fully considered during development, and the receiving service interface program can more conveniently and reliably call the communication service provided by the inter-device communication driver software through various resources within the service provider (for example, internal shared library functions, interfaces, authorization credentials, etc.), and such a call is exactly what the receiving service interface program does for the cashier application.

S108: The service parameters to be processed are sent from the cash register device to the NFC payment device by using the inter-device communication driver software and the corresponding communication method, so that the NFC payment device executes the corresponding target service to respond to the cash register application.

In one or more embodiments of this specification, the NFC payment device obtains the parameters of the pending service and can wait for the user (e.g., consumer) to bring the mobile phone close to the NFC payment device for induction identification. If the user does not do so, it indicates that the user may not want to execute the target service through the NFC payment device. In this case, the NFC payment device can return to the standby state after the waiting timeout to wait for the next opportunity. If the user cooperates with the operation, the NFC payment device can execute the target service accordingly. Of course, the consumer can also perform NFC induction identification in advance, and then the cashier can operate on the cash register device, and then complete the execution of the target service with the cooperation of the cash register device and the NFC payment device.

It should be noted that the NFC payment device may only complete part of the work included in the target business. For example, it may identify the user's payment code value as the execution result data and return it to the cash register device, and the cash register device will further complete the target business based on the execution result data. On the contrary, if the NFC payment device basically completes the target business, the execution result data may only be a final result for feedback to the consumer.

Through the method of FIG. 1 , by actively customizing the protocol type for the URL protocol of the browser on the cash register device and adapting to the corresponding custom protocol, the service provider of the NFC payment device develops a receiving service interface program that supports the custom protocol and deploys it on the cash register device. The receiving service interface program is used to connect to the inter-device communication driver software (e.g., Bluetooth communication driver software) also provided by the service provider of the NFC payment device, so that the cash register application can access the custom protocol URL in the browser to communicate with the local receiving service interface program, and then through the receiving service interface program across processes, the custom protocol call is converted into a communication service (e.g., Bluetooth service) call for the inter-device communication driver software, so that it can interact with the NFC payment device normally. This method avoids complex development on the merchant side (which may include the cash register application and the service provider of the cash register device), has little impact on the cash register application, and is more friendly. For the scenario of the cash register application running on the browser on the cash register device, it helps to expand the access to the NFC payment device for the cash register device in a more friendly way, and thus also helps to expand the access to the NFC payment device for more different cash register devices and different cash register applications in a more efficient way.

Based on the method of FIG. 1 , this specification also provides some specific implementation schemes and extension schemes of the method, which will be described below.

In one or more embodiments of the present specification, before accessing a custom protocol URL through a browser in a cash register application, in order to enable the cash register device to normally support the custom protocol, the system configuration can be written to make the custom protocol corresponding to the custom protocol type effective (for example, in a Windows scenario, the corresponding registration can be performed through the system registry. Of course, the corresponding configuration operations can also be performed in other scenarios such as Linux or some mobile operating systems), wherein the service interface program communication is developed based on the custom protocol to support URL access based on the custom protocol.

Further, one or more embodiments of this specification provide a flow chart of a solution for cross-process service call based on URL custom protocol in an application scenario, see Figure 2. In this application scenario, the above-mentioned inter-device communication driver software includes Bluetooth driver software, and the corresponding communication method includes Bluetooth communication.

The process in Figure 2 includes the following steps:

S202: Start the receiving service interface program deployed on the cash register device.

The receiving service interface program can be set to start automatically when the cash register device is turned on, so that no additional intervention from the cash register application is required.

S204: After the user triggers the target service in the cashier application, a custom protocol URL is generated according to the to-be-processed service parameters corresponding to the target service.

The user can use the keyboard or touch screen to click on the interactive control (usually a button, such as a payment button) displayed by the cash register application to trigger the target business. The parameters of the business to be processed can be determined based on the content entered by the user in the cash register application. For the cash register application, it mainly involves calling the custom protocol, which is simple to implement and has little impact. Moreover, this operation can even be performed by the software pre-deployed on the cash register device by the service provider of the NFC payment device (for example, through the cash register application behavior detection software, or the receiving service interface program itself, etc.). In this way, the cash register application itself does not even need to be modified.

S206: Access the custom protocol URL through the browser in the cash register application to call the Bluetooth service provided by the inter-device communication driver software across processes through the receiving service interface program deployed on the cash register device. The process includes the browser process and the inter-device communication driver software process.

In one or more embodiments of this specification, the cash register software will frequently trigger various services in actual applications, many of which may involve NFC payment devices. These target services may trigger the receiving service interface program to create a new instance through the browser each time to perform cross-process call conversion processing. Over time, the receiving service interface program may occupy more and more resources. In order to prevent this from happening, the present application considers converging resource consumption to individual instances through interactions between instances. Based on this idea, one or more embodiments of this specification provide a flow chart of the instance processing scheme of the receiving service interface program, see Figure 3.

The process in Figure 3 includes the following steps:

S302: Accessing the custom protocol website through the browser in the cashier application to trigger the receiving service interface program to create a new instance, and obtaining the to-be-processed business parameters through the new instance.

S304: Determine whether there is an old instance of the receiving service interface program, wherein the old instance includes at least part of historical business parameters related to the cashier application.

In one or more embodiments of the present specification, the old instance is generated when a custom protocol call is previously made, and preferably only one is retained, such as the first instance generated by the receiving service interface program after the cash register device is turned on.

S306: If yes, the service parameters to be processed obtained by the new instance are passed to the old instance, and the new instance is exited, so as to interact with the inter-device communication driver software through the old instance.

The new instance only involves this call. By passing business parameters between instances, the old instance can accumulate more historical business parameters, so that it can not only process this call normally, but also optionally use the accumulated historical business parameters to assist in more special execution of this call.

For example, the historical business parameters can be compared with the business parameters to be processed, and according to the comparison results, the target device execution mode can be selected from the predetermined multiple device execution modes, and the business parameters to be processed and the target device execution mode can be passed to the inter-device communication driver software through the old instance, so that the NFC payment device can execute the target business according to the target device execution mode and the business parameters to be processed. In particular, when the business parameters to be processed are relatively complex (for example, the description voice and text of the cashier or consumer is input in real time, in which case the flexibility of the business parameters to be processed can be improved, and the current actual business needs can be more diverse and complex), the target device execution mode with better feedback effect used when processing the historical business parameters can be referred to, and the target device execution mode can be selected for the business parameters to be processed that are similar after comparison. For the same target business, the NFC payment device may use different device execution modes to execute, and correspondingly obtain different execution results, or enable users (for example, consumers) to obtain different instant feelings. Different device execution modes can be distinguished from one or more dimensions, and optional dimensions include: additional auxiliary methods provided to consumers during interaction (for example, how to display prompt information, whether to turn on lights and voice, whether to collect additional business evidence to prevent risks, etc.), execution efficiency (for example, whether to use queue-jumping multi-threaded processing, whether to use offline processing, etc.), and whether to provide additional customized services for consumers.

After the business parameters are passed, the new instance can be exited in time to reduce resource usage.

In one or more embodiments of this specification, in order to improve the flexibility and scalability of the NFC payment device capability usage scenario, a flowchart of a local analysis solution for pending business parameters is also provided, see Figure 4. It can be executed in the process of triggering the receiving service interface program to pass the pending business parameters to the inter-device communication driver software deployed on the cash register device.

The process in Figure 4 includes the following steps:

S402: triggering the receiving service interface program to analyze the service parameters to be processed, and generating NFC sensing interaction gesture indication information according to the analysis result.

In one or more embodiments of this specification, the target NFC sensing interaction gesture can be matched according to the information volume of the service parameters to be processed, the specific semantics of the parameters, the preferential set of the service, the service type or other dimensions, among a variety of different NFC sensing interaction gestures (of course, new NFC sensing interaction gestures can also be adaptively generated, so that flexibility and sense of technology are better), and then the corresponding indication information is generated. It should be noted here that when the user interacts with NFC, traditionally, only the mobile phone or other sensing object is close to the NFC payment device, and no distinction is made between different NFC sensing interaction gestures. As long as normal near-field communication can be smoothly sensed and realized, the specific service to be executed through interactive sensing will not be different due to different interactive gestures.

NFC induction interaction gestures refer to the movements and postures of the sensing object approaching the NFC payment device, and/or how the sensing object moves further while remaining close to the NFC payment device after successful induction or communication. In order to more accurately distinguish different NFC induction interaction gestures, the required sensors can also be deployed for NFC payment devices or cash registers.

S404: The service parameter to be processed and the NFC induction interaction gesture indication information are transmitted to the inter-device communication driver software deployed on the cash register device through the receiving service interface program, so as to instruct the target sensing object to use the NFC induction interaction gesture corresponding to the NFC induction interaction gesture indication information to interact with the NFC payment device.

If the target sensing object correctly adopts the NFC sensing interaction gesture, the NFC payment device can accordingly correctly process the target service, and optionally the NFC payment device can also perform additional services for the user, and different NFC sensing interaction gestures may correspond to different additional services.

Furthermore, in order to improve fault tolerance to ensure user experience and enhance the user's sense of additional gain, one or more embodiments of this specification provide a flow chart of a differentiated processing solution for NFC inductive interaction gestures, see FIG. 5 .

The process in Figure 5 includes the following steps:

S502: After sending the to-be-processed business parameters from the cash register device to the NFC payment device, if the target sensing object does not use the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device, receiving a first execution result of the target business fed back by the NFC payment device.

In one or more embodiments of the present specification, the NFC inductive interaction gesture corresponding to the NFC inductive interaction gesture indication information may be a predetermined special approach gesture (compared to the traditional direct approach, there are some additional actions, such as drawing circles, intermittent approach, etc.). The first execution result can be used as a normal processing result of the target business and can be used as basic feedback data. Of course, more strictly, if the user does not use the corresponding NFC inductive interaction gesture, but uses other NFC inductive interaction gestures, the NFC payment device may not execute the target business, but remind the user.

S504: When the target sensing object adopts the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device, receiving a second execution result of an additional auxiliary service pre-associated with the target service or the NFC sensing interaction gesture fed back by the NFC payment device.

The second execution result may be an additional result different from the first execution result. In the case of step S504, the NFC payment device may feedback both the first execution result and the second execution result. The execution of the additional auxiliary service can enable the user to obtain additional benefits (such as corresponding Internet resources, better service experience, etc.).

In one or more embodiments of the present specification, when the target sensing object uses the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device, a new NFC sensing interaction gesture and/or new additional auxiliary services can be unlocked for the target sensing object, thereby enabling different users to interact with the same NFC payment device for the same service, which may bring advanced and differentiated experiences, thereby helping to increase users' enthusiasm for using NFC payment devices and help to better promote NFC payment devices.

The solution of FIG. 5 can improve the user's enthusiasm for adopting differentiated NFC sensing interaction gestures, and also help NFC payment devices to perform services more flexibly and support a variety of differentiated services.

According to the foregoing description, in order to facilitate implementation and be more intuitive, one or more embodiments of this specification also provide a schematic diagram of the architecture of a specific implementation scheme of the near field communication service processing method, see FIG6 .

In the scenario of Figure 6, the cash register device is specifically a PC-based POS machine (assuming that it uses the Windows operating system), and the NFC payment device is specifically an NFC cash register device. The above-mentioned browser-based cash register application is Web SaaS, the receiving service interface program is a custom URL Protocol receiving service (referred to as receiving service), and the inter-device communication driver software is the NFC device Bluetooth driver software. Of course, there are Bluetooth transmitter modules on both devices.

The custom protocol of the URL protocol is designed in advance. Exemplary custom protocol formats include:

PosAssistant://{params};

Among them, "PosAssistant" represents the protocol type customized for the URL, and "params" represents the field used to carry the business parameters to be processed. In addition, more optional fields can be added to the protocol format, and the customized protocol URL can be generated after the corresponding assignment.

Register the custom protocol type in the system in advance, so that when the browser requests the corresponding custom protocol URL, it will trigger the receiving service response. The receiving service can be started automatically when the POS machine is started, or it can be started by triggering Web SaaS, and then maintain a process. When the new instance is started, it will pass the adoption number to the old instance, so that it can continue to run based on the old instance.

Take trigger start as an example. When the cashier triggers cashiering in the business page of Web SaaS, the receiving service can be automatically started by calling the URL custom protocol through the browser, and the cashier instruction is carried in the form of pending business parameters in the custom protocol URL, and the Bluetooth service provided by the NFC device Bluetooth driver software is called through the receiving service across processes.

After the cross-process call, the NFC cash register device executes the corresponding target business. Afterwards, the NFC cash register device can return the execution result (such as the corresponding business code value, success or failure notification information, etc.) to the POS machine. Here, the above return action can be performed through the human-computer interaction protocol, using the method of simulating the human interface device (Human Interface Device, HID), so that the execution result can be filled back into the corresponding input box of the cash register application.

Thus, in the scheme of FIG6 , the browser custom URL protocol and simulated HID input are combined into a new two-way communication method between Web SaaS and NFC cash register devices, which provides great convenience for merchants to expand NFC cash register devices. The calling method is efficient, the receiving link is reliable, and there is almost no need for merchants to pay additional transformation costs.

FIG1 describes the cash register device and the NFC payment device as a whole from the perspective of the whole. For the payment service provider, one of the main modifications is reflected in the above-mentioned receiving service interface program. Therefore, based on the same idea, the description is repeated from the perspective of the receiving service interface program, see FIG7, which is a flowchart of another near field communication service processing method provided by one or more embodiments of this specification.

Another near field communication service processing method is applied to a receiving service interface program deployed on a cash register device, and the receiving service interface program is provided by a service provider of an NFC payment device. The process in FIG7 includes the following steps:

S702: Determine a cash register application running on the cash register device based on a local browser.

S704: In response to the triggering of the cashier application, the pending business parameters generated and transmitted by the cashier application are further transmitted to the inter-device communication driver software deployed on the cashier device, so that the inter-device communication driver software adopts its corresponding communication method to send the pending business parameters from the cashier device to the NFC payment device, so that the NFC payment device executes the corresponding target business; wherein, the triggering is achieved by accessing the custom protocol website through the browser in the cashier application to communicate with the receiving service interface program; the custom protocol website is generated according to the pending business parameters and the protocol type customized for the URL protocol; the inter-device communication driver software is provided by the service provider of the NFC payment device.

The steps in FIG. 7 may be understood by referring to the previous description, and will not be described in detail here.

Since the receiving service interface program is provided by the service provider of the NFC payment device, there is basically no need for merchants, cash register equipment and cash register applications to carry out development and modification. This is more friendly to them and helps to increase merchants' enthusiasm for expanding the use of NFC payment devices.

Based on the same idea, one or more embodiments of this specification also provide devices and equipment corresponding to the above method, as shown in Figures 8 to 11. The devices and equipment can execute the above method and related optional solutions accordingly.

FIG8 is a schematic diagram of the structure of a near field communication service processing device provided by one or more embodiments of this specification, which is applied to a cash register device, and the device includes:

The to-be-processed business parameter acquisition module 802 acquires the to-be-processed business parameters generated by a local cashier application, where the cashier application is run based on a local browser;

A custom protocol website generating module 804 generates a custom protocol website according to the service parameters to be processed and a protocol type customized for the URL protocol;

The receiving service interface program interaction module 806 accesses the custom protocol website through the browser in the cash register application to communicate with the receiving service interface program deployed on the cash register device, and through the communication, triggers the receiving service interface program to pass the service parameters to be processed to the inter-device communication driver software deployed on the cash register device, wherein the service interface program communication and the inter-device communication driver software are provided by the service provider of the NFC payment device;

The inter-device business parameter transmission module 808, through the inter-device communication driver software, adopts its corresponding communication method to send the to-be-processed business parameters from the cash register device to the NFC payment device, so that the NFC payment device executes the corresponding target business in order to respond to the cash register application.

Optionally, the cashier application is a SaaS cashier application, and a service provider of the SaaS cashier application is different from a service provider of the NFC payment device.

Optionally, the inter-device communication driver software includes Bluetooth driver software, and the corresponding communication method includes Bluetooth communication;

The receiving service interface program interaction module 806 accesses the custom protocol website through the browser in the cash register application, so as to call the Bluetooth service provided by the inter-device communication driver software across processes through the receiving service interface program deployed on the cash register device. The process includes the browser process and the inter-device communication driver software process.

Optionally, the custom protocol website generation module 804, before accessing the custom protocol website through the browser in the cashier application, writes through system configuration to make the custom protocol corresponding to the custom protocol type effective, wherein the receiving service interface program is developed according to the custom protocol;

The receiving service interface program interaction module 806 accesses the custom protocol website through the browser in the cashier application to generate a custom protocol call request;

The custom protocol call request is converted into an inter-device communication service call request for the inter-device communication driver software through the receiving service interface program.

Optionally, the receiving service interface program interaction module 806 triggers the receiving service interface program to create a new instance, and obtains the service parameter to be processed through the new instance;

Determining whether there is an old instance of the receiving service interface program, wherein the old instance includes at least part of historical business parameters related to the cashier application;

If so, the to-be-processed service parameters obtained by the new instance are passed to the old instance, and the new instance is exited, so as to interact with the inter-device communication driver software through the old instance.

Optionally, the receiving service interface program interaction module 806 compares the historical service parameters with the service parameters to be processed;

According to the comparison result, a target device execution mode is selected from a plurality of predetermined device execution modes;

The service parameters to be processed and the target device execution mode are passed to the inter-device communication driver software through the old instance, so that the NFC payment device executes the target service according to the target device execution mode and the service parameters to be processed.

Optionally, the receiving service interface program interaction module 806 triggers the receiving service interface program to analyze the service parameters to be processed, and generates NFC sensing interaction gesture indication information according to the analysis results;

Through the receiving service interface program, the service parameters to be processed and the NFC sensing interaction gesture indication information are passed to the inter-device communication driver software deployed on the cash register device, so as to instruct the target sensing object to adopt the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device.

Optionally, the NFC induction interaction gesture corresponding to the NFC induction interaction gesture indication information is a predetermined special proximity gesture;

The receiving service interface program interaction module 806 receives, after sending the to-be-processed service parameter from the cash register device to the NFC payment device, a first execution result of the target service fed back by the NFC payment device when the target sensing object does not use the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device;

When the target sensing object adopts the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device, a second execution result of the additional auxiliary service pre-associated with the target service or the NFC sensing interaction gesture is received, which is fed back by the NFC payment device.

Optionally, the receiving service interface program interaction module 806 unlocks a new NFC sensing interaction gesture and/or a new additional auxiliary service for the target sensing object when the target sensing object adopts the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device.

Optionally, the inter-device service parameter transmission module 808 receives a service code value obtained and returned by the NFC payment device through executing the target service after sending the service parameter to be processed from the cash register device to the NFC payment device;

In response to the return operation performed by the NFC payment device through the human-computer interaction protocol, the service code value is filled back into the corresponding input box of the cashier application.

FIG9 is a schematic diagram of the structure of another near field communication service processing device provided by one or more embodiments of this specification, which is applied to a receiving service interface program deployed on a cash register device, and the receiving service interface program is provided by a service provider of an NFC payment device, and the device includes:

A cashier application determining module 902 determines a cashier application running on the cashier device based on a local browser;

The business parameter transmission module 904, in response to the triggering of the cashier application, continues to transmit the pending business parameters generated and transmitted by the cashier application to the inter-device communication driver software deployed on the cashier device, so that the inter-device communication driver software adopts its corresponding communication mode to send the pending business parameters from the cashier device to the NFC payment device, so that the NFC payment device executes the corresponding target business;

Among them, the trigger is achieved by accessing the custom protocol website through the browser in the cash register application to communicate with the receiving service interface program; the custom protocol website is generated according to the business parameters to be processed and the protocol type customized for the URL protocol; the inter-device communication driver software is provided by the service provider of the NFC payment device.

FIG10 is a schematic diagram of the structure of a near field communication service processing device provided by one or more embodiments of this specification, which is applied to a cash register device. The near field communication service processing device includes:

at least one processor; and,

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

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

Obtaining a to-be-processed business parameter generated by a local cashier application, where the cashier application is run based on a local browser;

Generate a custom protocol URL according to the service parameters to be processed and the custom protocol type for the URL protocol;

The custom protocol website is accessed through the browser in the cash register application to communicate with the receiving service interface program deployed on the cash register device, and through the communication, the receiving service interface program is triggered to pass the service parameters to be processed to the inter-device communication driver software deployed on the cash register device, wherein the service interface program communication and the inter-device communication driver software are provided by the service provider of the NFC payment device;

The service parameters to be processed are sent from the cash register device to the NFC payment device through the inter-device communication driver software and in a corresponding communication mode, so that the NFC payment device executes the corresponding target service in response to the cash register application.

FIG11 is a schematic diagram of the structure of another near field communication service processing device provided by one or more embodiments of this specification, which is applied to a receiving service interface program deployed on a cash register device. The receiving service interface program is provided by a service provider of an NFC payment device. The near field communication service processing device includes:

at least one processor; and,

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

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

Determine a cash register application running on the cash register device based on a local browser;

In response to the triggering of the cashier application, the service parameters to be processed generated and transmitted by the cashier application are further transmitted to the inter-device communication driver software deployed on the cashier device, so that the inter-device communication driver software adopts its corresponding communication mode to send the service parameters to be processed from the cashier device to the NFC payment device, so that the NFC payment device executes the corresponding target service;

Among them, the trigger is achieved by accessing the custom protocol website through the browser in the cash register application to communicate with the receiving service interface program; the custom protocol website is generated according to the business parameters to be processed and the protocol type customized for the URL protocol; the inter-device communication driver software is provided by the service provider of the NFC payment device.

Based on the same idea, one or more embodiments of this specification further provide a non-volatile computer storage medium, which is applied to a cash register device, wherein the medium stores computer executable instructions, and the computer executable instructions are configured as follows:

Obtaining a to-be-processed business parameter generated by a local cashier application, where the cashier application is run based on a local browser;

Generate a custom protocol URL according to the service parameters to be processed and the custom protocol type for the URL protocol;

The custom protocol website is accessed through the browser in the cash register application to communicate with the receiving service interface program deployed on the cash register device, and through the communication, the receiving service interface program is triggered to pass the service parameters to be processed to the inter-device communication driver software deployed on the cash register device, wherein the service interface program communication and the inter-device communication driver software are provided by the service provider of the NFC payment device;

The service parameters to be processed are sent from the cash register device to the NFC payment device through the inter-device communication driver software and in a corresponding communication mode, so that the NFC payment device executes the corresponding target service in response to the cash register application.

One or more embodiments of the present specification further provide another non-volatile computer storage medium, which is applied to a receiving service interface program deployed on a cash register device, wherein the receiving service interface program is provided by a service provider of an NFC payment device, and wherein the medium stores computer executable instructions, wherein the computer executable instructions are configured as follows:

Determine a cash register application running on the cash register device based on a local browser;

In response to the triggering of the cashier application, the service parameters to be processed generated and transmitted by the cashier application are further transmitted to the inter-device communication driver software deployed on the cashier device, so that the inter-device communication driver software adopts its corresponding communication mode to send the service parameters to be processed from the cashier device to the NFC payment device, so that the NFC payment device executes the corresponding target service;

Among them, the trigger is achieved by accessing the custom protocol website through the browser in the cash register application to communicate with the receiving service interface program; the custom protocol website is generated according to the business parameters to be processed and the protocol type customized for the URL protocol; the inter-device communication driver software is provided by the service provider of the NFC payment device.

In the 1990s, it was very clear whether the improvement of a technology was hardware improvement (for example, improvement of the circuit structure of diodes, transistors, switches, etc.) or software improvement (improvement of the method flow). However, with the development of technology, many improvements of the method flow today can be regarded as direct improvements of the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be implemented with hardware entity modules. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming themselves, without having to ask chip manufacturers to design and make dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

The controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (e.g., software or firmware) executable by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller may also be implemented as part of the control logic of the memory. It is also known to those skilled in the art that, in addition to implementing the controller in a purely computer-readable program code manner, the controller may be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller may be considered as a hardware component, and the devices for implementing various functions included therein may also be considered as structures within the hardware component. Or even, the devices for implementing various functions may be considered as both software modules for implementing the method and structures within the hardware component.

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

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

This specification is described with reference to the flowcharts and/or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and/or box in the flowchart and/or block diagram, as well as the combination of the processes and/or boxes in the flowchart and/or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

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

Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment, and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

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

The above description is only one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, one or more embodiments of this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of this specification shall be included in the scope of the claims of this specification.

Claims (24)

1. A near field communication service processing method, applied to a cash register device, the method comprising: Obtaining a to-be-processed business parameter generated by a local cashier application, where the cashier application is run based on a local browser; Generate a custom protocol URL according to the service parameters to be processed and the custom protocol type for the URL protocol; The custom protocol website is accessed through the browser in the cash register application to communicate with the receiving service interface program deployed on the cash register device, and through the communication, the receiving service interface program is triggered to pass the service parameters to be processed to the inter-device communication driver software deployed on the cash register device, wherein the service interface program communication and the inter-device communication driver software are provided by the service provider of the NFC payment device; The service parameters to be processed are sent from the cash register device to the NFC payment device through the inter-device communication driver software and in a corresponding communication mode, so that the NFC payment device executes the corresponding target service in response to the cash register application. 2. The method according to claim 1, wherein the cashier application is a SaaS cashier application, and a service provider of the SaaS cashier application is different from a service provider of the NFC payment device. 3. The method according to claim 1, wherein the inter-device communication driver software comprises Bluetooth driver software, and the corresponding communication mode comprises Bluetooth communication; The step of accessing the custom protocol website through the browser in the cash register application to communicate with the receiving service interface program deployed on the cash register device specifically includes: The custom protocol URL is accessed through the browser in the cash register application to call the Bluetooth service provided by the inter-device communication driver software across processes through the receiving service interface program deployed on the cash register device. The process includes the browser process and the inter-device communication driver software process. 4. The method according to claim 1, before accessing the custom protocol website through the browser in the cash register application, the method further comprises: Writing in the system configuration makes the custom protocol corresponding to the custom protocol type effective, wherein the receiving service interface program is developed according to the custom protocol; The step of accessing the custom protocol website through the browser in the cash register application to communicate with the receiving service interface program deployed on the cash register device specifically includes: In the cashier application, access the custom protocol website through the browser to generate a custom protocol call request; The custom protocol call request is converted into an inter-device communication service call request for the inter-device communication driver software through the receiving service interface program. 5. The method according to claim 1, wherein the communication with the receiving service interface program deployed on the cash register device specifically comprises: Trigger the receiving service interface program to create a new instance, and obtain the service parameters to be processed through the new instance; Determining whether there is an old instance of the receiving service interface program, wherein the old instance includes at least part of historical business parameters related to the cashier application; If so, the to-be-processed service parameters obtained by the new instance are passed to the old instance, and the new instance is exited, so as to interact with the inter-device communication driver software through the old instance. 6. The method according to claim 5, wherein the interacting with the inter-device communication driver software through the old instance specifically comprises: Comparing the historical service parameters with the service parameters to be processed; According to the comparison result, a target device execution mode is selected from a plurality of predetermined device execution modes; The service parameters to be processed and the target device execution mode are passed to the inter-device communication driver software through the old instance, so that the NFC payment device executes the target service according to the target device execution mode and the service parameters to be processed. 7. The method according to claim 1, wherein triggering the receiving service interface program to pass the service parameters to be processed to the inter-device communication driver software deployed on the cash register device specifically comprises: Triggering the receiving service interface program to analyze the service parameters to be processed, and generating NFC induction interaction gesture indication information according to the analysis results; Through the receiving service interface program, the service parameters to be processed and the NFC sensing interaction gesture indication information are passed to the inter-device communication driver software deployed on the cash register device, so as to instruct the target sensing object to adopt the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device. 8. The method according to claim 7, wherein the NFC induction interaction gesture corresponding to the NFC induction interaction gesture indication information is a predetermined special approach gesture; After sending the to-be-processed service parameters from the cash register device to the NFC payment device, the method further includes: In a case where the target sensing object does not use the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device, receiving a first execution result of the target service fed back by the NFC payment device; When the target sensing object adopts the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device, a second execution result of the additional auxiliary service pre-associated with the target service or the NFC sensing interaction gesture is received, which is fed back by the NFC payment device. 9. The method of claim 8, further comprising: When the target sensing object adopts the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device, a new NFC sensing interaction gesture and/or a new additional auxiliary service is unlocked for the target sensing object. 10. The method according to claim 1, after sending the to-be-processed business parameters from the cash register device to the NFC payment device, the method further comprises: Receiving a service code value obtained and returned by the NFC payment device through executing the target service; In response to the return operation performed by the NFC payment device through the human-computer interaction protocol, the service code value is filled back into the corresponding input box of the cashier application. 11. A near field communication service processing method, applied to a receiving service interface program deployed on a cash register device, the receiving service interface program is provided by a service provider of an NFC payment device, the method comprising: Determine a cash register application running on the cash register device based on a local browser; In response to the triggering of the cashier application, the service parameters to be processed generated and transmitted by the cashier application are further transmitted to the inter-device communication driver software deployed on the cashier device, so that the inter-device communication driver software adopts its corresponding communication mode to send the service parameters to be processed from the cashier device to the NFC payment device, so that the NFC payment device executes the corresponding target service; Among them, the trigger is achieved by accessing the custom protocol website through the browser in the cash register application to communicate with the receiving service interface program; the custom protocol website is generated according to the business parameters to be processed and the protocol type customized for the URL protocol; the inter-device communication driver software is provided by the service provider of the NFC payment device. 12. A near field communication service processing device, applied to a cash register device, the device comprising: A module for obtaining business parameters to be processed, which obtains business parameters to be processed generated by a local cashier application, wherein the cashier application is run based on a local browser; A custom protocol website generation module generates a custom protocol website according to the service parameters to be processed and a custom protocol type for the URL protocol; A receiving service interface program interaction module, in the cash register application, accesses the custom protocol website through the browser to communicate with the receiving service interface program deployed on the cash register device, and through the communication, triggers the receiving service interface program to pass the service parameters to be processed to the inter-device communication driver software deployed on the cash register device, wherein the service interface program communication and the inter-device communication driver software are provided by the service provider of the NFC payment device; The inter-device business parameter transmission module, through the inter-device communication driver software, adopts its corresponding communication method to send the to-be-processed business parameters from the cash register device to the NFC payment device, so that the NFC payment device executes the corresponding target business in order to respond to the cash register application. 13. The apparatus according to claim 12, wherein the cashier application is a SaaS cashier application, and a service provider of the SaaS cashier application is different from a service provider of the NFC payment device. 14. The apparatus according to claim 12, wherein the inter-device communication driver software comprises Bluetooth driver software, and the corresponding communication method comprises Bluetooth communication; The receiving service interface program interaction module accesses the custom protocol website through the browser in the cash register application, so as to call the Bluetooth service provided by the inter-device communication driver software across processes through the receiving service interface program deployed on the cash register device. The process includes the browser process and the inter-device communication driver software process. 15. The device according to claim 12, wherein the custom protocol website generation module, before accessing the custom protocol website through the browser in the cashier application, writes the system configuration to make the custom protocol corresponding to the custom protocol type effective, wherein the receiving service interface program is developed according to the custom protocol; The receiving service interface program interaction module accesses the custom protocol website through the browser in the cashier application to generate a custom protocol call request; The custom protocol call request is converted into an inter-device communication service call request for the inter-device communication driver software through the receiving service interface program. 16. The device according to claim 12, wherein the receiving service interface program interaction module triggers the receiving service interface program to create a new instance, and obtains the service parameter to be processed through the new instance; Determining whether there is an old instance of the receiving service interface program, wherein the old instance includes at least part of historical business parameters related to the cashier application; If so, the to-be-processed service parameters obtained by the new instance are passed to the old instance, and the new instance is exited, so as to interact with the inter-device communication driver software through the old instance. 17. The device according to claim 16, wherein the receiving service interface program interaction module compares the historical service parameters with the service parameters to be processed; According to the comparison result, a target device execution mode is selected from a plurality of predetermined device execution modes; The service parameters to be processed and the target device execution mode are passed to the inter-device communication driver software through the old instance, so that the NFC payment device executes the target service according to the target device execution mode and the service parameters to be processed. 18. The device of claim 12, wherein the receiving service interface program interaction module triggers the receiving service interface program to analyze the service parameters to be processed, and generates NFC sensing interaction gesture indication information according to the analysis result; Through the receiving service interface program, the service parameters to be processed and the NFC sensing interaction gesture indication information are passed to the inter-device communication driver software deployed on the cash register device, so as to instruct the target sensing object to adopt the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device. 19. The device of claim 18, wherein the NFC induction interaction gesture corresponding to the NFC induction interaction gesture indication information is a predetermined special approach gesture; The receiving service interface program interaction module receives, after sending the to-be-processed service parameter from the cash register device to the NFC payment device, a first execution result of the target service fed back by the NFC payment device when the target sensing object does not use the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device; When the target sensing object adopts the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device, a second execution result of the additional auxiliary service pre-associated with the target service or the NFC sensing interaction gesture is received, which is fed back by the NFC payment device. 20. The device as described in claim 19, wherein the receiving service interface program interaction module unlocks a new NFC sensing interaction gesture and/or a new additional auxiliary service for the target sensing object when the target sensing object adopts the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device. 21. The apparatus according to claim 12, wherein the inter-device service parameter transmission module receives a service code value obtained and returned by the NFC payment device through executing the target service after the service parameter to be processed is sent from the cash register device to the NFC payment device; In response to the return operation performed by the NFC payment device through the human-computer interaction protocol, the service code value is filled back into the corresponding input box of the cashier application. 22. A near field communication service processing device, applied to a receiving service interface program deployed on a cash register device, the receiving service interface program is provided by a service provider of an NFC payment device, the device comprising: A cashier application determination module, which determines the cashier application running on the cashier device based on the local browser; The service parameter transmission module, in response to the triggering of the cashier application, further transmits the service parameters to be processed generated and transmitted by the cashier application to the inter-device communication driver software deployed on the cashier device, so that the inter-device communication driver software adopts its corresponding communication mode to send the service parameters to be processed from the cashier device to the NFC payment device, so that the NFC payment device executes the corresponding target service; Among them, the trigger is achieved by accessing the custom protocol website through the browser in the cash register application to communicate with the receiving service interface program; the custom protocol website is generated according to the business parameters to be processed and the protocol type customized for the URL protocol; the inter-device communication driver software is provided by the service provider of the NFC payment device. 23. A near field communication service processing device, applied to a cash register device, the near field communication service processing device comprising: at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform: Obtaining a to-be-processed business parameter generated by a local cashier application, where the cashier application is run based on a local browser; Generate a custom protocol URL according to the service parameters to be processed and the custom protocol type for the URL protocol; The custom protocol website is accessed through the browser in the cash register application to communicate with the receiving service interface program deployed on the cash register device, and through the communication, the receiving service interface program is triggered to pass the service parameters to be processed to the inter-device communication driver software deployed on the cash register device, wherein the service interface program communication and the inter-device communication driver software are provided by the service provider of the NFC payment device; The service parameters to be processed are sent from the cash register device to the NFC payment device through the inter-device communication driver software and in a corresponding communication mode, so that the NFC payment device executes the corresponding target service in response to the cash register application. 24. A near field communication service processing device, applied to a receiving service interface program deployed on a cash register device, the receiving service interface program is provided by a service provider of an NFC payment device, the near field communication service processing device comprising: at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform: Determine a cash register application running on the cash register device based on a local browser; In response to the triggering of the cashier application, the service parameters to be processed generated and transmitted by the cashier application are further transmitted to the inter-device communication driver software deployed on the cashier device, so that the inter-device communication driver software adopts its corresponding communication mode to send the service parameters to be processed from the cashier device to the NFC payment device, so that the NFC payment device executes the corresponding target service; Among them, the trigger is achieved by accessing the custom protocol website through the browser in the cash register application to communicate with the receiving service interface program; the custom protocol website is generated according to the business parameters to be processed and the protocol type customized for the URL protocol; the inter-device communication driver software is provided by the service provider of the NFC payment device.