Near field communication service processing

Abstract

Disclosed in embodiments of the present disclosure is a near field communication (NFC) service processing method, applied to a cash register device, and comprising: acquiring a service parameter to be processed generated by a local cash register application, wherein the cash register application runs on the basis of a local browser; generating a custom protocol uniform resource locator (URL) on the basis of said service parameter and a protocol type customized for a URL protocol; accessing, in the cash register application, the custom protocol URL by means of the browser to communicate with a receiving service interface program deployed on the cash register device, and triggering, by means of the communication, the receiving service interface program to transfer said service parameter to 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 a service provider of an NFC payment device; and sending, by means of the inter-device communication driver software and a communication mode corresponding thereto, said service parameter from the cash register device to the NFC payment device for the execution of a target service by the NFC payment device.

Description

Near Field Communication Service Processing Technical Field

[0001] This disclosure relates to the field of near-field communication technology, and in particular to near-field communication service processing. Background Technology

[0002] Near Field Communication (NFC) is a short-range, high-frequency radio technology that operates at a frequency of 13.56 MHz within a range of 20 centimeters. It evolved from contactless radio frequency identification (RFID) and interconnection technologies, providing a highly secure and fast communication method for various electronic products.

[0003] With the widespread use of smartphones that support NFC, NFC technology is being applied more extensively in the payment field. For example, when merchants deploy NFC payment devices at their checkout counters, users can make payments by interacting with the NFC payment devices using NFC-enabled smartphones, which offers good convenience.

[0004] Currently, NFC payment devices and corresponding payment applications are provided by specialized payment service providers. Merchants typically already have other service providers' POS devices and corresponding POS applications deployed at their checkout counters, primarily Software as a Service (SaaS) POS applications. For POS devices to function properly, cross-device interaction between the POS application and the NFC payment device is required.

[0005] For NFC payment devices that support Bluetooth communication, they often connect to POS devices via Bluetooth. Accordingly, the NFC device Bluetooth driver software provided by the NFC payment device service provider needs to be pre-installed on the POS device to enable cross-device communication. However, in practical applications, many SaaS POS applications run on a browser on the POS device. In this case, for merchants, enabling the POS application to call the Bluetooth service across processes to interact with the NFC payment device is difficult and costly to develop, thus hindering the expansion of POS devices to support NFC payment devices.

[0006] Therefore, for scenarios where POS applications run on browsers on POS devices, there is a need for solutions that can help extend the access of NFC payment devices to POS devices in a more user-friendly way. Summary of the Invention

[0007] This disclosure provides one or more embodiments of a near-field communication service processing method, apparatus, and device to solve the following technical problem: for scenarios where a POS application runs on a browser on a POS device, there is a need for a solution that helps to more conveniently extend the access of NFC payment devices to the POS device.

[0008] To solve the above-mentioned technical problems, one or more embodiments of this disclosure are implemented as follows.

[0009] This disclosure provides a near-field communication (NFC) service processing method, applied to a POS device, comprising: acquiring pending service parameters generated by a local POS application, wherein the POS application runs on a local browser; generating a custom protocol URL based on the pending service parameters and a custom protocol type for a URL protocol; accessing the custom protocol URL through the browser in the POS application to communicate with a receiving service interface program deployed on the POS device, and triggering the receiving service interface program to pass the pending service parameters to inter-device communication driver software deployed on the POS device, wherein the service interface program communication and the inter-device communication driver software are provided by a service provider of NFC payment devices; and sending the pending service parameters from the POS device to the NFC payment device through the inter-device communication driver software using its corresponding communication method, so that the NFC payment device can execute a corresponding target service in response to the POS application.

[0010] This disclosure provides a near-field communication (NFC) service processing method according to one or more embodiments, applied to a receiving service interface program deployed on a POS device. The receiving service interface program is provided by a service provider of the NFC payment device. The method includes: determining a POS application running on the POS device based on a local browser; responding to a triggering event by the POS application, continuing to pass the pending service parameters generated and transmitted by the POS application to inter-device communication driver software deployed on the POS device, so that the inter-device communication driver software uses its corresponding communication method to send the pending service parameters from the POS device to the NFC payment device for the NFC payment device to execute a corresponding target service; wherein, the triggering is achieved by accessing a custom protocol URL through the browser in the POS application to communicate with the receiving service interface program; the custom protocol URL is generated based on the pending service parameters and a custom protocol type for the URL protocol; the inter-device communication driver software is provided by a service provider of the NFC payment device.

[0011] This disclosure provides a near-field communication (NFC) service processing apparatus according to one or more embodiments, applied to a POS device. The apparatus includes: a pending service parameter acquisition module, which acquires pending service parameters generated by a local POS application, the POS application running on a local browser; a custom protocol URL generation module, which generates a custom protocol URL based on the pending service parameters and a custom protocol type for the URL protocol; a receiving service interface program interaction module, which accesses the custom protocol URL through the browser in the POS application to communicate with a receiving service interface program deployed on the POS device, and triggers the receiving service interface program to pass the pending service parameters to inter-device communication driver software deployed on the POS device through the communication, wherein the service interface program communication and the inter-device communication driver software are provided by the NFC payment device service provider; and an inter-device service parameter transmission module, which sends the pending service parameters from the POS device to the NFC payment device through the inter-device communication driver software using its corresponding communication method, so that the NFC payment device can execute the corresponding target service in order to respond to the POS application.

[0012] This disclosure provides a near-field communication (NFC) service processing apparatus according to one or more embodiments, applied to a receiving service interface program deployed on a POS device. The receiving service interface program is provided by a service provider of the NFC payment device. The apparatus includes: a POS application determination module, which determines a POS application running on the POS device based on a local browser; and a service parameter transmission module, which, in response to a triggering event by the POS application, further transmits the pending service parameters generated and transmitted by the POS application to inter-device communication driver software deployed on the POS device, so that the inter-device communication driver software uses its corresponding communication method to send the pending service parameters from the POS device to the NFC payment device for the NFC payment device to execute a corresponding target service. The triggering event is achieved by accessing a custom protocol URL through the browser in the POS application to communicate with the receiving service interface program; the custom protocol URL is generated based on the pending service parameters and a custom protocol type for the URL protocol; and the inter-device communication driver software is provided by a service provider of the NFC payment device.

[0013] This disclosure provides a near-field communication (NFC) service processing device according to one or more embodiments, applied to a POS device. The NFC service processing device includes: at least one processor; and a memory communicatively connected to the at least one processor. The memory stores instructions executable by the at least one processor, which, when executed, enable the at least one processor to: acquire pending service parameters generated by a local POS application running on a local browser; generate a custom protocol URL based on the pending service parameters and a custom protocol type for a URL protocol; access the custom protocol URL through the browser in the POS application to communicate with a receiving service interface program deployed on the POS device, and through this communication, trigger the receiving service interface program to pass the pending service parameters to inter-device communication driver software deployed on the POS device, wherein the service interface program communication and the inter-device communication driver software are provided by a service provider of the NFC payment device; and through the inter-device communication driver software, using its corresponding communication method, send the pending service parameters from the POS device to the NFC payment device, so that the NFC payment device can execute the corresponding target service in response to the POS application.

[0014] This disclosure provides one or more embodiments of a near-field communication (NFC) service processing device applied to a receiving service interface program deployed on a POS device. The receiving service interface program is provided by a service provider for the NFC payment device. The NFC service processing device includes: at least one processor; and a memory communicatively connected to the at least one processor. The memory stores instructions executable by the at least one processor, which, when executed, enable the at least one processor to: determine a POS application running on the POS device based on a local browser; and, in response to a triggering event by the POS application, generate and transmit a pending event from the POS application. The processing parameters are then passed to the inter-device communication driver software deployed on the POS device. This allows the driver software to use its corresponding communication method to send the processing parameters from the POS device to the NFC payment device, enabling the NFC payment device to execute the corresponding target transaction. The triggering is achieved by accessing a custom protocol URL through the browser in the POS application to communicate with the receiving service interface program. The custom protocol URL is generated based on the processing parameters and a custom protocol type for the URL protocol. The inter-device communication driver software is provided by the NFC payment device service provider.

[0015] The above-mentioned at least one technical solution adopted in one or more embodiments of this disclosure can achieve the following beneficial effects: By actively customizing the protocol type for the URL protocol of the browser on the POS device and adapting it to the corresponding custom protocol, the NFC payment device service provider develops a receiving service interface program that supports the custom protocol and deploys it on the POS device. The receiving service interface program connects to the device communication driver software (e.g., Bluetooth communication driver software) provided by the NFC payment device service provider. This allows the POS application to communicate with the local receiving service interface program by accessing the custom protocol URL in the browser. Then, through the receiving service interface program, the custom protocol call is transformed into a communication service (e.g., Bluetooth service) call for the device communication driver software, thereby enabling normal interaction with the NFC payment device. This method avoids complex development on the merchant's side (which may include the POS application and the POS device service provider), has less impact on the POS application, and is more user-friendly. For scenarios where the POS application runs on the browser on the POS device, it helps to extend the access of the POS device to NFC payment devices in a more user-friendly way, and also helps to extend the access of more different POS devices and different POS applications to NFC payment devices more efficiently. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments or related technologies of this disclosure, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments recorded in this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 is a flowchart illustrating a near-field communication service processing method provided in one or more embodiments of this disclosure;

[0018] Figure 2 is a flowchart illustrating a cross-process service call scheme based on a custom URL protocol in an application scenario provided by one or more embodiments of this disclosure.

[0019] Figure 3 is a flowchart illustrating an example processing scheme of a receiving service interface program provided in one or more embodiments of this disclosure;

[0020] Figure 4 is a flowchart illustrating a local analysis scheme for business parameters to be processed provided by one or more embodiments of this disclosure;

[0021] Figure 5 is a flowchart illustrating an NFC sensing interactive gesture differentiation processing scheme provided by one or more embodiments of this disclosure;

[0022] Figure 6 is a schematic diagram of the architecture of a specific implementation of the near-field communication service processing method provided in one or more embodiments of this disclosure;

[0023] Figure 7 is a flowchart illustrating another near-field communication service processing method provided by one or more embodiments of this disclosure;

[0024] Figure 8 is a schematic diagram of a near-field communication service processing device provided in one or more embodiments of the present disclosure;

[0025] Figure 9 is a schematic diagram of another near-field communication service processing device provided in one or more embodiments of this disclosure;

[0026] Figure 10 is a schematic diagram of the structure of a near-field communication service processing device provided in one or more embodiments of the present disclosure;

[0027] Figure 11 is a schematic diagram of another near-field communication service processing device provided in one or more embodiments of this disclosure. Detailed Implementation

[0028] This disclosure provides near-field communication service processing methods, apparatus, devices, and storage media.

[0029] To enable those skilled in the art to better understand the technical solutions in this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this application.

[0030] Regarding the issues mentioned in the background technology, the reasons for this problem include: browsers support relatively general protocols, while Bluetooth communication driver software is provided by NFC payment device service providers and is relatively proprietary. Therefore, there are inherent difficulties in interface and protocol integration. Moreover, the POS application itself is not the same as the NFC payment device service provider, which further increases the integration difficulty, making it difficult for browser-based POS applications to call Bluetooth services across processes (referring to the browser process and the Bluetooth communication driver software process, which are not the same process).

[0031] To address these issues, this application proposes that the NFC payment device service provider proactively add a custom protocol type to the URL protocol of the browser on which the POS application is based, and provide a receiving service interface program that supports the custom protocol corresponding to this protocol type (also implemented by the NFC payment device service provider). This program serves as a bridge between the POS application and the Bluetooth communication driver software provided by the NFC payment device service provider. The custom protocol is called through the browser to establish the bridge, thereby enabling cross-process Bluetooth calls.

[0032] In this way, POS applications can easily and reliably call these relatively proprietary Bluetooth services without requiring merchants to make any development modifications. NFC payment device service providers can also reuse their modifications at low cost on more other POS devices and applications, thereby bringing convenience to more merchants and increasing their enthusiasm for expanding the integration of NFC payment devices.

[0033] Based on this overall approach, the solution proposed in this application will be further explained below.

[0034] Figure 1 is a flowchart illustrating a near-field communication service processing method provided by one or more embodiments of this disclosure. The method is applied to a cash register device, and the corresponding steps can be executed by one or more software modules on the cash register device.

[0035] A basic POS application (which can be software for PCs or mobile devices like smartphones) needs to be deployed on a POS device to perform checkout operations. Some POS devices come with their own built-in POS application, usually part of an integrated hardware and software solution provided by the same service provider. Of course, merchants can also choose a different POS application from another service provider based on their needs, especially with Windows POS machines (referring to those based on the Windows operating system), which offer flexibility and wide applicability. In addition, POS devices can also be based on other common operating systems, or even niche self-developed systems.

[0036] In one or more embodiments of this disclosure, the POS device deploys a POS application that needs to run on a browser, such as a browser-based SaaS POS application (which may be simply referred to as: Web SaaS). The method also relates to an NFC payment device, which can connect and communicate with the NFC payment device via a means such as Bluetooth (this is used as an example for ease of description), with the NFC payment device serving to assist the operation of the POS device.

[0037] To enable inter-device communication, inter-device communication driver software (e.g., Bluetooth communication driver software) provided by the NFC payment device needs to be pre-deployed on the POS device. Taking Bluetooth as an example, in this application, the inter-device communication driver software can refer to the software on the POS device that provides an interface for sending payment instructions to the NFC payment device and receiving data via a Bluetooth transmitter.

[0038] POS devices and NFC payment devices can be provided by different service providers (usually independent companies that may not have a partnership). Similarly, POS applications and NFC payment devices (and of course, NFC payment devices also have accompanying NFC payment software) can be provided by different service providers.

[0039] Point-of-sale (POS) devices are basic equipment typically used by merchants at the checkout counter. Common examples include desktop or handheld POS machines. Their operating systems can vary, such as Windows, Linux, or mobile operating systems, and they support one or more basic payment methods, such as bank card payments, membership card payments, and QR code payments. However, they do not currently support NFC payments. Therefore, NFC payment devices are used to extend their NFC business support capabilities. Users can perform payment-related transactions by bringing NFC-enabled smartphones, smartwatches, or other mobile devices close to the NFC payment device, based on near-field communication.

[0040] The process shown in Figure 1 includes the following steps.

[0041] S102: Obtain the pending business parameters generated by the local POS application, which runs based on a local browser.

[0042] The POS application generates pending transaction parameters based on user (cashier or customer) actions. These parameters reflect the target transaction itself (e.g., payment instructions) or may further include specific data required to execute the target transaction. For example, the target transaction could be a payment-related transaction (e.g., paying for a current order, transferring funds, logging in as a member, claiming a discount), and the specific data could include the transaction type, amount to be paid, transfer amount, membership type, discount type, etc.

[0043] The target transaction could have been executed using other methods already available in the POS application (such as scanning a QR code or swiping a card), but in this application, it can be attempted, at least partially, via an NFC payment device. Of course, this is not mandatory; users can choose this alternative method. If the user does not cooperate by responding to the NFC method, the NFC payment device can remain idle and ready to proceed.

[0044] In addition, existing services can be modified or new services can be created in advance to adapt to NFC payment devices while minimizing the cost impact on merchants. In this case, the target services may require NFC to function properly, thus fully utilizing NFC payment devices and providing greater convenience to users.

[0045] S104: Generate a custom protocol URL based on the business parameters to be processed and the custom protocol type for the URL protocol.

[0046] URL, short for Uniform Resource Locator, is often referred to as a web address or simply a website address. An exemplary format is: [protocol type]: / / [server address]:[port number] / [resource-level UNIX file path][filename]?[query]#[fragment ID]. HTTP is one of the most commonly used protocol types. Based on the HTTP protocol, by accessing an HTTP URL, an HTTP request can be initiated to interact with a remote server, enabling business purposes such as downloading web page content for display in a local browser.

[0047] Based on the above format characteristics, this application intends to define the protocol type of the URL protocol and create a corresponding custom protocol to indicate that the specified local interface program is accessed through the URL under the custom protocol, instead of accessing the remote server, thereby facilitating the conversion of custom protocol calls into dedicated service calls locally.

[0048] In one or more embodiments of this disclosure, in addition to a custom protocol type, a field carrying the service parameters to be processed is also defined in the URL format. This allows the service parameters to be transmitted locally via the custom protocol URL, preparing for the continued transmission of service parameters across devices. Alternatively, a field specifying the specific instruction action can be defined in the URL format to instruct the interface program as the receiver, other local modules behind the interface program, or other devices on what specific actions need to be performed. This effectively improves the flexibility of the custom protocol and helps to expand into more specialized services.

[0049] S106: In the POS application, the browser accesses the custom protocol URL to communicate with the receiving service interface program deployed on the POS device. Through the communication, the receiving service interface program is triggered to pass the business parameters to be processed to the inter-device communication driver software deployed on the POS device. The service interface program communication and the inter-device communication driver software are provided by the NFC payment device service provider.

[0050] In one or more embodiments of this disclosure, the receiving service interface program is developed based on the aforementioned custom protocol. The receiving service interface program can be located based on the custom protocol and its URL, enabling access to the interface provided by the receiving service interface program via the custom protocol URL. This facilitates indirect access to the inter-device communication driver software process by bypassing the browser process. Since the communication of the receiving service interface program itself is provided by the NFC payment device service provider, its compatibility with the inter-device communication driver software provided by the same NFC payment device service provider can be more fully considered during development. Through various resources within the service provider (such as shared library functions, interfaces, and authorization credentials), the receiving service interface program can more conveniently, reliably, and seamlessly call the communication services provided by the inter-device communication driver software. This calling is precisely what the receiving service interface program performs for the POS application.

[0051] S108: The device communication driver software, using its corresponding communication method, sends the business parameters to be processed from the POS device to the NFC payment device, so that the NFC payment device can execute the corresponding target business in order to respond to the POS application.

[0052] In one or more embodiments of this disclosure, the NFC payment device obtains the parameters of the service to be processed and can wait for the user (e.g., a consumer) to bring their mobile phone close to the NFC payment device for sensing and identification. If the user does not perform this action, 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 a standby state after a timeout, waiting for the next opportunity. If the user cooperates, the NFC payment device can execute the target service accordingly. Of course, the consumer can also perform NFC sensing and identification in advance, and then the cashier can operate on the POS device, thereby completing the execution of the target service with the cooperation of the POS device and the NFC payment device.

[0053] It's important to note that an NFC payment device may only complete a portion of the target transaction. For example, it might identify the user's payment code value and return it as the result data to the POS terminal, which will then use this result data to further complete the target transaction. Conversely, if the NFC payment device has essentially completed the target transaction, the result data may simply be a final result used to provide feedback to the consumer.

[0054] The method shown in Figure 1 involves proactively customizing the URL protocol type for the browser on the POS device and adapting it accordingly. The NFC payment device service provider develops a receiving service interface program supporting this custom protocol and deploys it on the POS device. This receiving service interface program then interfaces with inter-device communication driver software (e.g., Bluetooth communication driver software) provided by the same NFC payment device service provider. This allows the POS application to communicate with the local receiving service interface program by accessing the custom protocol URL in the browser. Furthermore, the receiving service interface program can cross-process to convert custom protocol calls into communication service calls (e.g., Bluetooth service) calls for the inter-device communication driver software, enabling normal interaction with the NFC payment device. This approach avoids complex development on the merchant's side (which may include both the POS application and the POS device service provider), minimizes the impact on the POS application, and is more user-friendly. For POS applications running on browsers on POS devices, this method facilitates a more user-friendly expansion of POS devices to NFC payment devices, and also helps to more efficiently expand the integration of NFC payment devices for more diverse POS devices and applications.

[0055] Based on the method in Figure 1, this disclosure also provides some specific implementation schemes and extension schemes of the method, which will be further described below.

[0056] In one or more embodiments of this disclosure, before accessing a custom protocol URL through a browser in a POS application, in order for the POS device to support the custom protocol normally, the custom protocol corresponding to the custom protocol type can be enabled by writing system configuration (for example, in a Windows scenario, it can be registered through the system registry; of course, similar configuration operations can be performed in other scenarios such as Linux or some mobile operating systems). The service interface program communication is developed according to the custom protocol in order to support URL access based on the custom protocol.

[0057] Furthermore, one or more embodiments of this disclosure provide a flowchart illustrating a scheme for cross-process service calls based on a custom URL protocol in an application scenario, as shown in Figure 2. In this application scenario, the aforementioned inter-device communication driver software includes Bluetooth driver software, and the corresponding communication method includes Bluetooth communication.

[0058] The process shown in Figure 2 includes the following steps.

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

[0060] The receiving service interface program can be set to start automatically when the POS device is powered on, so that no additional intervention is required from the POS application.

[0061] S204: After the user triggers the target business in the POS application, a custom protocol URL is generated based on the pending business parameters corresponding to the target business.

[0062] Users can trigger the target transaction by clicking on interactive controls (usually a button, such as a payment button) displayed in the POS application using a keyboard or touchscreen. The parameters for the transaction to be processed can be determined based on the information entered by the user in the POS application. For the POS application, this mainly involves calling a custom protocol, which is simple to implement and has minimal impact. Moreover, this operation can even be performed by software pre-deployed on the POS device by the NFC payment device service provider (e.g., through POS application behavior detection software or the receiving service interface program itself). Thus, the POS application itself does not even need to be modified.

[0063] S206: In the POS application, the browser accesses the custom protocol URL to call the Bluetooth service provided by the inter-device communication driver software across processes through the receiving service interface program deployed on the POS device. The processes include the browser process and the inter-device communication driver software process.

[0064] In one or more embodiments of this disclosure, the POS software frequently triggers various business transactions in practical applications. Many of these transactions may involve NFC payment devices. Each time, these target transactions may trigger the receiving service interface program to create a new instance for cross-process call conversion processing via the browser. Over time, the receiving service interface program may consume more and more resources. To prevent this from happening, this application considers converging resource consumption to individual instances through inter-instance interaction. Based on this idea, one or more embodiments of this disclosure provide a flowchart of the instance processing scheme of the receiving service interface program, as shown in Figure 3.

[0065] The process shown in Figure 3 includes the following steps.

[0066] S302: In the POS application, the browser accesses the custom protocol URL, triggering the receiving service interface program to create a new instance, and obtains the business parameters to be processed through the new instance.

[0067] S304: Determine whether there is an old instance of the receiving service interface program, the old instance containing at least some historical business parameters related to the POS application.

[0068] In one or more embodiments of this disclosure, 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 POS device is powered on.

[0069] S306: If so, the pending service parameters obtained by the new instance are passed to the old instance, and the new instance is exited so that the old instance can interact with the device communication driver software.

[0070] The new instance only involves this call. By passing business parameters between instances, the old instance can accumulate more historical business parameters, so it can not only handle this call normally, but also optionally use the accumulated historical business parameters to assist this call in more specific execution.

[0071] For example, historical transaction parameters can be compared with those of the transaction to be processed. Based on the comparison results, a target device execution mode can be selected from a range of predefined device execution modes. Using a previous example, the transaction parameters and the target device execution mode are transmitted to the inter-device communication driver software, enabling the NFC payment device to execute the target transaction according to the target device execution mode and the transaction parameters. This is particularly useful when the transaction parameters are relatively complex (e.g., real-time recording of cashier or customer descriptions via voice or text, which increases the flexibility of the transaction parameters and allows for more diverse and complex representation of current business needs). The target device execution mode with good feedback from historical transaction parameter processing can be referenced to select the appropriate execution mode for similar transaction parameters after comparison. For the same target transaction, the NFC payment device may use different device execution modes to execute it, resulting in different execution results or providing users (e.g., consumers) with different real-time experiences. Different device execution modes can be distinguished from one or more dimensions. Optional dimensions include: additional auxiliary methods provided to consumers during interaction (e.g., how to display prompts, whether to turn on lights and voice, whether to collect additional business evidence to prevent risks, etc.), execution efficiency (e.g., whether to use queue-jumping multi-threaded processing, whether to use offline processing, etc.), and whether to provide additional customized services for consumers.

[0072] After the business parameters are passed, a new instance can be exited in a timely manner to reduce resource consumption.

[0073] In one or more embodiments of this disclosure, to improve the flexibility and scalability of NFC payment device capabilities across different application scenarios, a flowchart illustrating a local analysis scheme for pending business parameters is also provided, as shown in Figure 4. This can be executed during 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 POS device.

[0074] The process shown in Figure 4 includes the following steps.

[0075] S402: Trigger the receiving service interface program to analyze the service parameters to be processed, and generate NFC sensing interaction gesture indication information based on the analysis results.

[0076] In one or more embodiments of this disclosure, based on the information content of the service parameters to be processed, the specific semantics of the parameters, the service's preferential set, the service type, or other dimensions, a target NFC sensing interaction gesture can be matched from various different NFC sensing interaction gestures (of course, new NFC sensing interaction gestures can also be adaptively generated, thus improving flexibility and technological sophistication), thereby generating corresponding indication information. It should be noted that when a user interacts with NFC, traditionally, simply bringing the mobile phone or other sensing object close to the NFC payment device is sufficient; there is no distinction between different NFC sensing interaction gestures. As long as normal near-field communication can be achieved successfully, the specific service to be executed through interaction will not differ due to different interaction gestures.

[0077] NFC sensing interaction gestures refer to the actions and postures with which the sensing object approaches the NFC payment device, and / or, after successful sensing or communication, how the sensing object moves further while remaining close. To more accurately distinguish different NFC sensing interaction gestures, the necessary sensors can be deployed for NFC payment devices or point-of-sale devices.

[0078] S404: The receiving service interface program transmits the business parameters to be processed and the NFC sensing interaction gesture indication information to the device communication driver software deployed on the cash register, so as to instruct the target sensing object to use the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device.

[0079] If the target object correctly adopts the NFC sensing interaction gesture, the NFC payment device can correctly process the target transaction accordingly. Optionally, the NFC payment device can also perform additional transactions for the user, and the additional transactions corresponding to different NFC sensing interaction gestures can be different.

[0080] Furthermore, in order to improve fault tolerance to ensure user experience and enhance the user's additional sense of gain, one or more embodiments of this disclosure provide a flowchart of an NFC sensing interaction gesture differentiation processing scheme, as shown in Figure 5.

[0081] The process shown in Figure 5 includes the following steps.

[0082] S502: After the pending business parameters are sent from the cash register 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, the first execution result of the target business is received from the NFC payment device.

[0083] In one or more embodiments of this disclosure, the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information can be a predetermined special proximity gesture (compared to the traditional direct proximity, it involves some additional actions, such as drawing circles, intermittent proximity, etc.). The first execution result can serve as the normal processing result of the target service and as basic feedback data. Of course, more strictly speaking, if the user does not use the corresponding NFC sensing interaction gesture but uses other NFC sensing interaction gestures, the NFC payment device may not execute the target service but instead remind the user.

[0084] S504: 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, receive the second execution result of the additional auxiliary service pre-associated with the target service or the NFC sensing interaction gesture from the NFC payment device.

[0085] The second execution result can be an additional result different from the first execution result. In step S504, the NFC payment device can provide feedback on both the first and second execution results. The execution of additional auxiliary services can provide users with additional benefits (such as corresponding internet resources, a better service experience, etc.).

[0086] In one or more embodiments of this disclosure, 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, new NFC sensing interaction gestures and / or new additional auxiliary services can be unlocked for the target sensing object. This may bring advanced differentiated experiences when different users interact with the same NFC payment device for the same service, thereby helping to increase users' enthusiasm for using NFC payment devices and helping to better promote NFC payment devices.

[0087] The scheme shown in Figure 5 can increase users' willingness to adopt differentiated NFC sensing interaction gestures, and also help NFC payment devices to perform business more flexibly and support a variety of differentiated services.

[0088] Based on the foregoing description, for ease of implementation and to make it more intuitive, one or more embodiments of this disclosure also provide a schematic diagram of the architecture of a specific implementation of the near-field communication service processing method, see Figure 6.

[0089] In the scenario shown in Figure 6, the POS device is specifically a PC-based POS machine (assuming a Windows operating system), and the NFC payment device is specifically an NFC POS device. The browser-based POS application described above is a Web SaaS, the service interface program is a custom URL Protocol receiving service (referred to as the receiving service), and the device communication driver software is the NFC device Bluetooth driver software. Of course, both devices also have Bluetooth transmitter modules.

[0090] Design a custom protocol for the URL protocol in advance. For example, a custom protocol format could include: PosAssistant: / / {params}; where "PosAssistant" represents the custom protocol type 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 this protocol format. After assigning the corresponding values, a custom protocol URL can be generated.

[0091] The custom protocol type is pre-registered in the system, so that when the browser requests the corresponding custom protocol URL, it will trigger the receiving service response. The receiving service can start automatically when the POS machine starts, or it can be triggered by the Web SaaS. After that, it keeps a process running. When a new instance starts, it will pass the adoption count to the old instance, so that it can continue to run based on the old instance.

[0092] Taking trigger-based startup as an example, when a cashier triggers a checkout on the Web SaaS business page, the receiving service can be automatically started by calling a custom URL protocol through the browser. At the same time, the checkout instruction is carried in the pending business parameters in the custom protocol URL and the receiving service calls the Bluetooth service provided by the NFC device's Bluetooth driver software across processes.

[0093] After the cross-process call, the NFC POS device executes the corresponding target transaction. Then, the NFC POS device can return the execution result (such as the corresponding transaction code value, success or failure notification information, etc.) to the POS machine. Here, this return action can be performed using a simulated Human Interface Device (HID) through a human-machine interface protocol, allowing the execution result to be filled into the corresponding input fields of the POS application.

[0094] Thus, in the scheme shown in Figure 6, the browser's custom URL protocol and simulated HID input are combined into a new two-way communication method between Web SaaS and NFC POS devices, which greatly facilitates the expansion of NFC POS devices on the merchant side. The calling method is efficient, the receiving link is reliable, and there is almost no need for the merchant side to pay additional modification costs.

[0095] Figure 1 describes the POS device and NFC payment device as a whole, from the perspective of this whole. For payment service providers, one of the main modifications is reflected in the aforementioned receiving service interface program. Therefore, based on the same idea, it is described again from the perspective of the receiving service interface program, as shown in Figure 7. Figure 7 is a flowchart illustrating another near-field communication service processing method provided by one or more embodiments of this disclosure.

[0096] This alternative near-field communication service processing method is applied to a receiving service interface program deployed on the POS device, which is provided by the NFC payment device service provider. The process in Figure 7 includes the following steps.

[0097] S702: Determine the POS application running on the POS device based on a local browser.

[0098] S704: In response to the trigger of the POS application, the pending business parameters generated and transmitted by the POS application are further transmitted to the inter-device communication driver software deployed on the POS device, so that the inter-device communication driver software uses its corresponding communication method to send the pending business parameters from the POS device to the NFC payment device, for the NFC payment device to execute the corresponding target business; wherein, the trigger is achieved by accessing a custom protocol URL through the browser in the POS application to communicate with the receiving service interface program; the custom protocol URL is generated based on the pending business parameters and a custom protocol type for the URL protocol; the inter-device communication driver software is provided by the NFC payment device service provider.

[0099] You can refer to the previous description to understand the steps in Figure 7, which will not be repeated here.

[0100] Since the receiving service interface program is provided by the NFC payment device service provider, there is basically no need for merchants, POS devices, and POS applications to develop or modify it. This is more user-friendly for them and helps to increase merchants' enthusiasm for expanding the use of NFC payment devices.

[0101] Based on the same approach, one or more embodiments of this disclosure also provide apparatus and devices corresponding to the above methods, as shown in Figures 8 to 11. The apparatus and devices are capable of executing the above methods and related optional solutions accordingly.

[0102] Figure 8 is a schematic diagram of a near-field communication (NFC) service processing device provided in one or more embodiments of this disclosure, applied to a POS device. The device includes: a pending service parameter acquisition module 802, which acquires pending service parameters generated by a local POS application, the POS application running on a local browser; a custom protocol URL generation module 804, which generates a custom protocol URL based on the pending service parameters and a custom protocol type for the URL protocol; a receiving service interface program interaction module 806, which accesses the custom protocol URL through the browser in the POS application to communicate with a receiving service interface program deployed on the POS device, and triggers the receiving service interface program to pass the pending service parameters to the inter-device communication driver software deployed on the POS device through the communication, wherein the service interface program communication and the inter-device communication driver software are provided by the NFC payment device service provider; and an inter-device service parameter transmission module 808, which sends the pending service parameters from the POS device to the NFC payment device through the inter-device communication driver software using its corresponding communication method, so that the NFC payment device can execute the corresponding target service in order to respond to the POS application.

[0103] Optionally, the POS application is a SaaS POS application, and the service provider of the SaaS POS application is different from the service provider of the NFC payment device.

[0104] 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 URL through the browser in the POS 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 POS device, wherein the processes include the browser process and the inter-device communication driver software process.

[0105] Optionally, the custom protocol URL generation module 804, before accessing the custom protocol URL through the browser in the POS application, writes the custom protocol corresponding to the custom protocol type into the system configuration to enable the custom protocol, wherein the receiving service interface program is developed based on the custom protocol; the receiving service interface program interaction module 806, when accessing the custom protocol URL through the browser in the POS application, generates a custom protocol call request; and through the receiving service interface program, converts the custom protocol call request into an inter-device communication service call request for the inter-device communication driver software.

[0106] Optionally, the receiving service interface program interaction module 806 triggers the receiving service interface program to create a new instance and obtains the pending business parameters through the new instance; determines whether there is an old instance of the receiving service interface program, the old instance containing at least some historical business parameters related to the POS application; if so, the pending business parameters obtained by the new instance are passed to the old instance, and the new instance is exited, so that the old instance can interact with the device communication driver software.

[0107] Optionally, the receiving service interface program interaction module 806 compares the historical service parameters with the service parameters to be processed; based on the comparison result, it selects a target device execution mode from a predetermined number of device execution modes; and through the old instance, it transmits the service parameters to be processed and the target device execution mode to the inter-device communication driver software, so that the NFC payment device executes the target service according to the target device execution mode and the service parameters to be processed.

[0108] Optionally, the receiving service interface program interaction module 806 triggers the receiving service interface program to analyze the business parameters to be processed, and generates NFC sensing interaction gesture indication information based on the analysis results; the receiving service interface program then transmits the business parameters to be processed and the NFC sensing interaction gesture indication information to the device communication driver software deployed on the cash register, for instructing the target sensing object to use the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information to interact with the NFC payment device.

[0109] Optionally, the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information is a predetermined special proximity gesture; the receiving service interface program interaction module 806, after sending the service parameters to be processed from the cashier device to the NFC payment device, receives a first execution result of the target service from 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; and receives a second execution result of the NFC payment device for additional auxiliary services pre-associated with the target service or the NFC sensing interaction gesture 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.

[0110] Optionally, the receiving service interface program interaction module 806, 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, unlocks a new NFC sensing interaction gesture and / or new additional auxiliary services for the target sensing object.

[0111] Optionally, after the business parameter transmission module 808 sends the business parameter to be processed from the POS device to the NFC payment device, it receives the business code value obtained and returned by the NFC payment device through the execution of the target business; in response to the return operation executed by the NFC payment device through the human-computer interaction protocol, the business code value is filled back into the corresponding input box of the POS application.

[0112] Figure 9 is a schematic diagram of another near-field communication service processing device provided by one or more embodiments of this disclosure, applied to a receiving service interface program deployed on a POS device. The receiving service interface program is provided by the service provider of the NFC payment device. The device includes: a POS application determination module 902, which determines the POS application running on the POS device based on a local browser; and a service parameter transmission module 904, which, in response to a triggering event of the POS application, continues to transmit the pending service parameters generated and transmitted by the POS application to the inter-device communication driver software deployed on the POS device, so that the inter-device communication driver software uses its corresponding communication method to send the pending service parameters from the POS device to the NFC payment device for the NFC payment device to execute the corresponding target service. The triggering event is achieved by accessing a custom protocol URL through the browser in the POS application to communicate with the receiving service interface program. The custom protocol URL is generated based on the pending service parameters and a custom protocol type for the URL protocol. The inter-device communication driver software is provided by the service provider of the NFC payment device.

[0113] Figure 10 is a schematic diagram of the structure of a near-field communication (NFC) service processing device provided in one or more embodiments of this disclosure, applied to a POS device. The NFC service processing device includes: at least one processor; and a memory communicatively connected to the at least one processor. The memory stores instructions executable by the at least one processor, which, when executed, enable the at least one processor to: acquire pending service parameters generated by a local POS application running on a local browser; generate a custom protocol URL based on the pending service parameters and a custom protocol type for the URL protocol; access the custom protocol URL through the browser in the POS application to communicate with a receiving service interface program deployed on the POS device, and through this communication, trigger the receiving service interface program to pass the pending service parameters to inter-device communication driver software deployed on the POS device, wherein the service interface program communication and the inter-device communication driver software are provided by the NFC payment device service provider; and through the inter-device communication driver software, using its corresponding communication method, send the pending service parameters from the POS device to the NFC payment device for the NFC payment device to execute the corresponding target service in response to the POS application.

[0114] Figure 11 is a schematic diagram of another near-field communication service processing device provided in one or more embodiments of this disclosure, applied to a receiving service interface program deployed on a POS device. The receiving service interface program is provided by the service provider of the 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, which, when executed by the at least one processor, enable the at least one processor to perform: determining a POS application running on the POS device based on a local browser; and, in response to a triggering of the POS application, generating... The pending business parameters are then passed to the inter-device communication driver software deployed on the POS device, enabling the driver software to use its corresponding communication method to send the pending business parameters from the POS device to the NFC payment device, so that the NFC payment device can execute the corresponding target business. The triggering is achieved by accessing a custom protocol URL through the browser in the POS application to communicate with the receiving service interface program. The custom protocol URL is generated based on the pending business parameters and a custom protocol type for the URL protocol. The inter-device communication driver software is provided by the NFC payment device service provider.

[0115] Based on the same idea, one or more embodiments of this disclosure also provide a non-volatile computer storage medium applied to a POS device. The medium stores computer-executable instructions, which are configured to: obtain pending business parameters generated by a local POS application, the POS application running on a local browser; generate a custom protocol URL based on the pending business parameters and a custom protocol type for the URL protocol; access the custom protocol URL through the browser in the POS application to communicate with a receiving service interface program deployed on the POS device, and through the communication, trigger the receiving service interface program to pass the pending business parameters to inter-device communication driver software deployed on the POS device, wherein the service interface program communication and the inter-device communication driver software are provided by the NFC payment device service provider; and send the pending business parameters from the POS device to the NFC payment device through the inter-device communication driver software using its corresponding communication method, so that the NFC payment device can execute the corresponding target business in response to the POS application.

[0116] One or more embodiments of this disclosure also provide another non-volatile computer storage medium applied to a receiving service interface program deployed on a POS device. The receiving service interface program is provided by a service provider of the NFC payment device. The medium stores computer-executable instructions configured to: determine a POS application running on the POS device based on a local browser; and, in response to a triggering event by the POS application, continue to pass the pending business parameters generated and transmitted by the POS application to inter-device communication driver software deployed on the POS device, so that the inter-device communication driver software uses its corresponding communication method to send the pending business parameters from the POS device to the NFC payment device for the NFC payment device to execute the corresponding target business. The triggering event is achieved by accessing a custom protocol URL through the browser in the POS application to communicate with the receiving service interface program; the custom protocol URL is generated based on the pending business parameters and a custom protocol type for the URL protocol; and the inter-device communication driver software is provided by a service provider of the NFC payment device.

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

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

[0119] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, in implementing this disclosure, the functions of each unit can be implemented in one or more software and / or hardware.

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

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

[0122] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0123] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

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

[0125] The various embodiments in this disclosure are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments of apparatus, devices, and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

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

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

Claims

1. A method for processing near field communication (NFC) service, applied to a cash register device, the method comprising: obtaining a to-be-processed service parameter generated by a local cash register application, the cash register application being run based on a local browser; generating a custom protocol address based on the to-be-processed service parameter and a protocol type customized for a URL protocol; accessing the custom protocol address in the cash register application through the browser to communicate with a receiving service interface program deployed on the cash register device, and triggering the receiving service interface program to pass the to-be-processed service parameter to an inter-device communication driver software deployed on the cash register device through the communication, wherein the service interface program communication and the inter-device communication driver software are provided by a service provider of an NFC payment device; and sending the to-be-processed service parameter from the cash register device to the NFC payment device through the inter-device communication driver software in a corresponding communication mode thereof, for the NFC payment device to execute a corresponding target service in response to the cash register application. 2.The method of claim 1, wherein the cash register application is a SaaS cash register application, and a service provider of the SaaS cash register application is different from a service provider of the NFC payment device. 3.The method of claim 1, wherein the inter-device communication driver software comprises a Bluetooth driver software, and the corresponding communication mode comprises Bluetooth communication; and the accessing the custom protocol address in the cash register application through the browser to communicate with the receiving service interface program deployed on the cash register device specifically comprises: accessing the custom protocol address in the cash register application through the browser to cross-process call a Bluetooth service provided by the inter-device communication driver software through the receiving service interface program deployed on the cash register device, the processes including a process of the browser and a process of the inter-device communication driver software. 4.The method of claim 1, wherein before the accessing the custom protocol address in the cash register application through the browser, the method further comprises: enabling a custom protocol corresponding to the custom protocol type through system configuration writing, wherein the receiving service interface program is developed according to the custom protocol; and the accessing the custom protocol address in the cash register application through the browser to communicate with the receiving service interface program deployed on the cash register device specifically comprises: accessing the custom protocol address in the cash register application through the browser to generate a custom protocol call request; and converting the custom protocol call request into an inter-device communication service call request for the inter-device communication driver software through the receiving service interface program. 5.The method of claim 1, wherein the communicating with the receiving service interface program deployed on the cash register device specifically comprises: triggering the receiving service interface program to create a new instance, and obtaining the to-be-processed service parameter through the new instance. ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ determining whether an old instance of the receiving service interface program exists, the old instance containing historical business parameters related at least in part to the cash register application; if so, passing the to-be-processed business parameters obtained by the new instance to the old instance, and exiting the new instance so as to interact with the device intercommunication driver software through the old instance.

6. The method of claim 5, wherein the interacting with the device intercommunication driver software through the old instance specifically comprises: comparing the historical business parameters with the to-be-processed business parameters; selecting a target device execution mode from a plurality of predetermined device execution modes according to a comparison result; passing the to-be-processed business parameters and the target device execution mode to the device intercommunication driver software through the old instance, so that the NFC payment device executes the target business according to the to-be-processed business parameters in the target device execution mode.

7. The method of claim 1, wherein the triggering the receiving service interface program to pass the to-be-processed business parameters to the device intercommunication driver software deployed on the cash register device specifically comprises: triggering the receiving service interface program to analyze the to-be-processed business parameters, and generating NFC induction interaction gesture instruction information according to an analysis result; passing the to-be-processed business parameters and the NFC induction interaction gesture instruction information to the device intercommunication driver software deployed on the cash register device, so as to instruct a target induction object to interact with the NFC payment device by adopting an NFC induction interaction gesture corresponding to the NFC induction interaction gesture instruction information.

8. The method of claim 7, wherein the NFC induction interaction gesture corresponding to the NFC induction interaction gesture instruction information belongs to a predetermined special proximity gesture; and wherein the method further comprises: after the passing the to-be-processed business parameters from the cash register device to the NFC payment device, receiving a first execution result of the target business fed back by the NFC payment device in a case where the target induction object does not interact with the NFC payment device by adopting the NFC induction interaction gesture corresponding to the NFC induction interaction gesture instruction information; receiving a second execution result of an additional auxiliary business pre-associated with the target business or the NFC induction interaction gesture fed back by the NFC payment device in a case where the target induction object interacts with the NFC payment device by adopting the NFC induction interaction gesture corresponding to the NFC induction interaction gesture instruction information.

9. The method of claim 8, further comprising: in the case where the target induction object interacts with the NFC payment device by adopting the NFC induction interaction gesture corresponding to the NFC induction interaction gesture instruction information, unlocking a new NFC induction interaction gesture and / or a new additional auxiliary business for the target induction object.

10. The method of claim 1, wherein the method further comprises: ​ receiving a service code value returned by the NFC payment device through performing the target service; in response to the NFC payment device performing the returning operation through the man-machine interaction protocol, causing the service code value to be backfilled into a 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 cashier device, the receiving service interface program being provided by a service provider of an NFC payment device, and the method comprising: determining a cashier application running on the cashier device based on a local browser; in response to a trigger of the cashier application, continuing to pass a to-be-processed service parameter generated and passed by the cashier application to an inter-device communication driver software deployed on the cashier device, so that the inter-device communication driver software sends the to-be-processed service parameter from the cashier device to the NFC payment device in a corresponding communication mode of the inter-device communication driver software, for the NFC payment device to perform a corresponding target service; wherein the trigger is achieved by accessing a custom protocol website in the cashier application through the browser to communicate with the receiving service interface program; the custom protocol website is generated according to the to-be-processed service parameter and a protocol type customized for a URL protocol; and the inter-device communication driver software is provided by the service provider of the NFC payment device. 12.A near field communication service processing apparatus, applied to a cashier device, the apparatus comprising: a to-be-processed service parameter acquisition module, configured to acquire a to-be-processed service parameter generated by a local cashier application, the cashier application being run based on a local browser; a custom protocol website generation module, configured to generate a custom protocol website according to the to-be-processed service parameter and a protocol type customized for a URL protocol; a receiving service interface program interaction module, configured to access the custom protocol website in the cashier application through the browser to communicate with a receiving service interface program deployed on the cashier device, and trigger the receiving service interface program to pass the to-be-processed service parameter to an inter-device communication driver software deployed on the cashier device through the communication, wherein the service interface program communication and the inter-device communication driver software are provided by a service provider of an NFC payment device; an inter-device service parameter passing module, configured to send the to-be-processed service parameter from the cashier device to the NFC payment device in a corresponding communication mode of the inter-device communication driver software, for the NFC payment device to perform a corresponding target service, so as to respond to the cashier application. 13.The apparatus of 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 of claim 12, wherein the inter-device communication driver software comprises a Bluetooth driver software, and the corresponding communication mode comprises Bluetooth communication. The receiving service interface program interaction module accesses the custom protocol website through the browser in the cash register application to cross-process call the Bluetooth service provided by the inter-device communication driver software through the receiving service interface program deployed on the cash register device, the processes including the process of the browser and the process of the inter-device communication driver software.

15. The apparatus of claim 12, wherein the custom protocol URL generation module, prior to accessing the custom protocol URL through the browser in the POS application, causes the custom protocol corresponding to the custom protocol type to take effect through a system configuration write. 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 cash register application to generate a custom protocol call request; The receiving service interface program converts the custom protocol call request into an inter-device communication service call request for the inter-device communication driver software.

16. The apparatus of claim 12, the receiving service interface program interaction module triggers the receiving service interface program to create a new instance and obtain the to-be-processed business parameter through the new instance; determining whether there is an old instance of the receiving service interface program, the old instance containing at least part of historical business parameters related to the cash register application; if yes, passing the to-be-processed business parameter obtained by the new instance to the old instance and exiting the new instance so as to interact with the inter-device communication driver software through the old instance.

17. The apparatus of claim 16, the receiving service interface program interaction module compares the historical business parameter with the to-be-processed business parameter; selecting a target device execution mode from a plurality of predetermined device execution modes according to the comparison result; passing the to-be-processed business parameter and the target device execution mode to the inter-device communication driver software through the old instance so that the NFC payment device executes the target business according to the to-be-processed business parameter in the target device execution mode.

18. The apparatus of claim 12, the receiving service interface program interaction module triggers the receiving service interface program to analyze the to-be-processed business parameter and generates NFC induction interaction gesture indication information according to the analysis result; passing the to-be-processed business parameter and the NFC induction interaction gesture indication information to the inter-device communication driver software deployed on the cash register device to instruct a target induction object to interact with the NFC payment device by using an NFC induction interaction gesture corresponding to the NFC induction interaction gesture indication information.

19. The apparatus of claim 18, the NFC induction interaction gesture corresponding to the NFC induction interaction gesture indication information belongs to a predetermined special close gesture. The receiving service interface program interaction module receives a first execution result of the target service fed back by the NFC payment device in a case where the target sensing object does not interact with the NFC payment device by using the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information after the sending of the to-be-processed service parameter from the cash register device to the NFC payment device. The receiving service interface program interaction module receives 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 in a case where the target sensing object interacts with the NFC payment device by using the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information.

20. The apparatus of claim 19, wherein the receiving service interface program interaction module, in a case where the target sensing object interacts with the NFC payment device by using the NFC sensing interaction gesture corresponding to the NFC sensing interaction gesture indication information, unlocks a new NFC sensing interaction gesture and / or a new additional auxiliary service for the target sensing object.

21. The apparatus of claim 12, wherein the device-to-device service parameter transmission module receives a service code value obtained and returned by the NFC payment device by executing the target service after the sending of the to-be-processed service parameter from the cash register device to the NFC payment device. The service code value is backfilled into a corresponding input box of the cash register application in response to the return operation of the NFC payment device by using the human-computer interaction protocol.

22. A near field communication service processing apparatus applied to a receiving service interface program deployed on a cash register device, the receiving service interface program being provided by a service provider of an NFC payment device, and the apparatus comprising: a cash register application determination module configured to determine a cash register application running on the cash register device based on a local browser; a service parameter transmission module configured to, in response to a trigger of the cash register application, continue to transmit to-be-processed service parameters generated and transmitted by the cash register application to an inter-device communication driver software deployed on the cash register device, so that the inter-device communication driver software transmits the to-be-processed service parameters from the cash register device to the NFC payment device by using a corresponding communication mode of the inter-device communication driver software, for the NFC payment device to execute a corresponding target service; wherein the trigger is achieved by accessing a custom protocol website in the cash register application by using the browser to communicate with the receiving service interface program; the custom protocol website is generated according to the to-be-processed service parameters and a protocol type customized for a URL protocol; and 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 in communication connection with the at least one processor; wherein the at least one processor is configured to determine a cash register application running on the cash register device based on a local browser, and in response to a trigger of the cash register application, continue to transmit to-be-processed service parameters generated and transmitted by the cash register application to an inter-device communication driver software deployed on the cash register device, so that the inter-device communication driver software transmits the to-be-processed service parameters from the cash register device to the NFC payment device by using a corresponding communication mode of the inter-device communication driver software, for the NFC payment device to execute a corresponding target service; wherein the trigger is achieved by accessing a custom protocol website in the cash register application by using the browser to communicate with the receiving service interface program; the custom protocol website is generated according to the to-be-processed service parameters and a protocol type customized for a URL protocol; and the inter-device communication driver software is provided by the service provider of the NFC payment device. The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform: obtaining a to-be-processed business parameter generated by a local cash register application, the cash register application being based on a local browser; generating a custom protocol website according to the to-be-processed business parameter and a protocol type customized for a URL protocol; accessing the custom protocol website in the cash register application through the browser to communicate with a receiving service interface program deployed on the cash register device, and triggering the receiving service interface program to pass the to-be-processed business parameter to an inter-device communication driver software deployed on the cash register device through the communication, wherein the service interface program communication and the inter-device communication driver software are provided by a service provider of the NFC payment device; sending the to-be-processed business parameter from the cash register device to the NFC payment device through the inter-device communication driver software in a corresponding communication mode thereof, for the NFC payment device to perform a corresponding target business in response to the cash register application. 24.A near field communication business processing device applied to a receiving service interface program deployed on a cash register device, the receiving service interface program being provided by a service provider of an NFC payment device, the near field communication business processing device comprising: at least one processor; and a memory in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform: determining a cash register application running on the cash register device based on a local browser; in response to a trigger of the cash register application, continuing to pass a to-be-processed business parameter generated and passed by the cash register application to an inter-device communication driver software deployed on the cash register device, so that the inter-device communication driver software sends the to-be-processed business parameter from the cash register device to the NFC payment device in a corresponding communication mode thereof, for the NFC payment device to perform a corresponding target business; wherein the trigger is achieved by accessing a custom protocol website in the cash register application through the browser to communicate with the receiving service interface program; the custom protocol website is generated according to the to-be-processed business parameter and a protocol type customized for a URL protocol; and the inter-device communication driver software is provided by a service provider of the NFC payment device.

Images