Near field communication service processing method, apparatus and device, and cashier device

Abstract

The embodiment of the invention discloses a near field communication service processing method. The method is applied to a system comprising cashier equipment and NFC payment equipment, and comprises the following steps: on the cashier equipment, through an external software module provided by a service party of the NFC payment equipment, detecting position data interacted by a user in a business page of a software module of the cashier equipment, and according to the position data, determining the position of the user in the business page of the software module of the cashier equipment; judging whether the user triggers a target service in the service page or not; if yes, interaction with the NFC payment equipment is carried out through an external software module, so that the NFC payment equipment obtains capability demand data matched with a service party of the NFC payment equipment; and on the NFC payment device, executing a corresponding target service according to the capability demand data, and returning execution result data to the cashier device.

Description

[0001] This application is a divisional application of the invention patent application submitted to the China Patent Office on July 25, 2024, with application number 202411005058.5 and invention name "Near Field Communication Business Processing Method, Device, Equipment and Cashier Equipment". The full text of the application is incorporated into this application by reference. Technical Field

[0002] The present invention relates to the field of near field communication technology, and in particular to near field communication service processing methods, devices, equipment and cash register equipment. Background Art

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

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

[0005] At present, NFC payment devices and corresponding payment applications are provided by specialized payment service providers, while merchants usually have deployed cash register devices provided by other service providers and cash register software used on the cash register devices at the cash register counter, mainly Software as a Service (SaaS) cash register software. In this case, if merchants want to use the NFC payment devices provided by the payment service provider normally to obtain the corresponding NFC payment support capabilities, they need to develop access so that the cash register devices and their cash register software can be normally connected with the NFC payment devices and their payment applications. In this case, merchants or service providers of cash register equipment and their cash register software (collectively referred to as customers from the perspective of payment service providers) need to integrate software development kits (SDKs) and develop codes to call and process corresponding interface logic. Customers are involved in development, testing, deployment and other processes, and the overall cycle is relatively long (usually weeks or even months). Moreover, since most cash register software technology stacks are old and have poor maintainability, code changes may trigger many online problems. Not only that, in actual applications, there are many types of cash register equipment and their cash register software, involving different service providers. As NFC payment devices are promoted and rolled out, the total development and access costs of many customers will be higher.

[0006] Based on this, merchants' cash register equipment and cash register software need to have a more user-friendly solution that can expand their access to NFC payment devices so that they can obtain NFC payment support capabilities. Summary of the invention

[0007] One or more embodiments of this specification provide near-field communication business processing methods, devices, equipment and cash register equipment to solve the following technical problems: There needs to be a more user-friendly solution for merchants' cash register equipment and cash register software that can expand access to NFC payment devices so that they can obtain NFC payment support capabilities.

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

[0009] One or more embodiments of this specification provide a near field communication service processing method, which is applied to a system including a cash register device and an NFC payment device, and the method includes:

[0010] On the cash register device, detecting the location data of the user interacting in the service page of the own software module of the cash register device through the external software module provided by the service provider of the NFC payment device, and judging whether the user has triggered the target service in the service page according to the location data;

[0011] If yes, interacting with the NFC payment device through the external software module, so that the NFC payment device obtains capability requirement data adapted to its service provider, wherein the capability requirement data is generated according to the screenshot image;

[0012] On the NFC payment device, the corresponding target service is executed according to the capability requirement data, and the execution result data is returned to the cash register device.

[0013] One or more embodiments of this specification provide a near field communication service processing method, which is applied to an external software module provided by a service provider of an NFC payment device, and the external software module is pre-deployed on a cash register device. The method includes:

[0014] Detecting location data of a user interacting in a business page of a proprietary software module of the cash register device, and determining whether the user has triggered a target business in the business page based on the location data;

[0015] If so, interact with the NFC payment device so that the NFC payment device obtains capability requirement data adapted to its service provider, and executes the corresponding target business according to the capability requirement data.

[0016] One or more embodiments of this specification provide a near field communication service processing device, which is applied to a system including a cash register device and an NFC payment device, and the device includes:

[0017] A service action trigger detection module detects, on the cash register device, location data of user interaction in a service page of the cash register device's own software module through an external software module provided by the service provider of the NFC payment device, and determines, based on the location data, whether the user has triggered a target service in the service page;

[0018] Adaptation capability requirement module, if yes, interacts with the NFC payment device through the external software module, so that the NFC payment device obtains capability requirement data adapted to its service provider;

[0019] The target service interaction execution module executes the corresponding target service on the NFC payment device according to the capability requirement data, and returns the execution result data to the cash register device.

[0020] One or more embodiments of this specification provide a near field communication service processing device, which is applied to an external software module provided by a service provider of an NFC payment device, and the external software module is pre-deployed on a cash register device, and the device includes:

[0021] A detection and judgment module detects the location data of the user's interaction in the business page of the self-owned software module of the cash register device, and judges whether the user triggers the target business in the business page according to the location data;

[0022] The interaction module, if yes, interacts with the NFC payment device so that the NFC payment device obtains capability requirement data adapted to its service provider and executes the corresponding target business according to the capability requirement data.

[0023] One or more embodiments of this specification provide a cash register device, including a proprietary software module and an external software module provided by a service provider of the NFC payment device;

[0024] The self-owned software module provides a business page to the user so that the user can interact in the business page;

[0025] The external software module detects the location data of the user's interaction in the business page, and determines whether the user has triggered a target business in the business page according to the location data;

[0026] If yes, interact with the NFC payment device so that the NFC payment device obtains capability requirement data adapted to its service provider;

[0027] The proprietary software module receives execution result data returned by the NFC payment device and obtained by executing a corresponding target service according to the capability requirement data.

[0028] One or more embodiments of this specification provide a near field communication service processing device, which is applied to a system including a cash register device and an NFC payment device. The near field communication service processing device includes:

[0029] at least one processor; and,

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

[0031] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute:

[0032] On the cash register device, detecting the location data of the user interacting in the service page of the own software module of the cash register device through the external software module provided by the service provider of the NFC payment device, and judging whether the user has triggered the target service in the service page according to the location data;

[0033] If yes, interacting with the NFC payment device through the external software module, so that the NFC payment device obtains capability requirement data adapted to its service provider;

[0034] On the NFC payment device, the corresponding target service is executed according to the capability requirement data, and the execution result data is returned to the cash register device.

[0035] One or more embodiments of this specification provide a near field communication service processing device, which is applied to an external software module provided by a service provider of an NFC payment device, and the external software module is pre-deployed on a cash register device. The near field communication service processing device includes:

[0036] at least one processor; and,

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

[0038] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute:

[0039] Detecting location data of a user interacting in a business page of a proprietary software module of the cash register device, and determining whether the user has triggered a target business in the business page based on the location data;

[0040] If so, interact with the NFC payment device so that the NFC payment device obtains capability requirement data adapted to its service provider, and executes the corresponding target business according to the capability requirement data.

[0041] At least one of the above technical solutions adopted in one or more embodiments of this specification can achieve the following beneficial effects: for the payment service provider of NFC payment devices, there is no need for its customers (such as merchants, cashier service providers, etc.) to develop and transform the cashier devices and their own software modules (such as SaaS cashier applications), integrate software development kit processing interfaces, etc., but simply deploy the external software module provided by the payment service provider on the cashier device, connect the cashier device and the NFC payment device through methods such as serial ports, and conveniently access the NFC payment support capabilities. The own software module does not need to make cumbersome interface calls for the NFC payment device, and there is no need to cooperate with the external software module for additional development Instead, the external software module actively detects the user's interaction position against the own software module, and optionally, based on a pre-prepared decision model, it can infer whether there is an opportunity for the NFC payment device to play a role, and then generate capability demand data (for example, interface call data) through targeted methods such as screenshots, and then replace the own software module to interact with the NFC payment device, so as to help the cash register and its own software module to use the NFC payment support capability. It can be seen that this solution is mainly transformed and deployed by the payment service provider itself. Customers can easily expand access to NFC payment devices without development and modification. It is more user-friendly and also helps payment service providers to expand NFC payment business more widely. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0043] Figure 1 A flowchart of a near field communication service processing method provided for one or more embodiments of this specification;

[0044] Figure 2 A schematic flow chart of a labeling model preprocessing solution provided for one or more embodiments of this specification;

[0045] Figure 3 A flowchart of a capability requirement data processing solution provided for one or more embodiments of this specification;

[0046] Figure 4 A flowchart of a specific implementation scheme of a near field communication service processing method provided in one or more embodiments of this specification;

[0047] Figure 5 A schematic diagram of a process flow of a page layout patch processing solution provided for one or more embodiments of this specification;

[0048] Figure 6 A flowchart of another near field communication service processing method provided for one or more embodiments of this specification;

[0049] Figure 7 A schematic diagram of the structure of a near field communication service processing device provided in one or more embodiments of this specification;

[0050] Figure 8 A schematic diagram of the structure of another near field communication service processing device provided in one or more embodiments of this specification;

[0051] Fig. 9 A schematic diagram of the structure of a cash register device provided for one or more embodiments of this specification;

[0052] Fig.10 A schematic diagram of the structure of a near field communication service processing device provided for one or more embodiments of this specification;

[0053] Fig.11 A schematic diagram of the structure of another near field communication service processing device provided in one or more embodiments of this specification. DETAILED DESCRIPTION

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

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

[0056] In response to the problems mentioned in the background technology, the present application considers that the service provider of NFC payment devices, referred to as payment service provider, proactively conducts detection on cash register devices and their cash register software based on a decision model created through pre-processing work such as page area marking (used to understand some key areas in the business page of the cash register software), in order to try to instantly discover the demand for using NFC payment devices without the need for the cash register software to cooperate with development work such as interface modification. If the demand for using NFC payment devices is discovered, the payment service provider will still generate interface call data on its own based on the decision results and relevant page screenshots, so as to help the cash register devices and their cash register software use the capabilities of NFC payment devices, thereby enabling merchants to access NFC payment devices conveniently and efficiently, with almost no modification costs for the merchants.

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

[0058] Figure 1 A flowchart of a near field communication service processing method provided in one or more embodiments of this specification is applied to a system including a cash register device and an NFC payment device. In the system, the cash register device and the NFC payment device are connected by wire or wireless means, and the NFC payment device service assists the cash register device in its work. The execution subject of the process can be the entire system, and the specific steps can be executed by the corresponding software and hardware modules in the system.

[0059] The cash register device and the NFC payment device are provided by different service providers (usually independent companies that may not have a cooperative relationship with each other). The cash register device is a basic device that merchants usually use at the cash register. Common ones are desktop or handheld POS machines (usually based on Windows or Linux operating systems), etc., which can support one or more basic payment methods, such as bank card payment, membership card payment, QR code payment, etc. However, NFC payment is not yet supported. Therefore, it is intended to expand its NFC payment support capabilities through the solution of this application. The NFC payment device can provide NFC payment support capabilities. Users can sense mobile terminals such as smartphones and smart watches that support NFC functions by bringing them close to the NFC payment device, and then perform payment-related services based on near-field communication.

[0060] Figure 1 The process in includes the following steps:

[0061] S102: On the cash register device, the location data of the user's interaction in the business page of the cash register device's own software module is detected through the external software module provided by the service provider of the NFC payment device, and based on the location data, it is determined whether the user (e.g., cashier, consumer, etc.) has triggered the target business in the business page.

[0062] In one or more embodiments of the present specification, the two concepts of self-owned software module and external software module are used for the convenience of distinction.

[0063] Proprietary software modules refer to the basic cash register software installed on the cash register device, which is usually a SaaS cash register application provided by a SaaS application service provider. The cash register software on some cash register devices is self-contained, and usually belongs to the hardware and software integrated solution provided by the same service provider; of course, merchants can also choose cash register software provided by another service provider for the current cash register device as needed, especially cash register devices such as Windows POS machines (referring to those based on the Windows operating system), which are flexible and widely used. In addition, cash register devices can also be based on other common operating systems, or even niche self-developed systems.

[0064] The external software module is provided by the service provider of the NFC payment device (for example, the payment service provider mentioned above). The NFC payment device is pre-installed with the corresponding software, which is also provided by the service provider. Since they are under the R&D system of the same service provider, the connection between the software and the external software module will be easier to achieve at low cost. The problem in the background technology is essentially the connection between the software and the proprietary software module of the cash register device, which is not easy to achieve due to technical differences, costs, etc. This application mainly uses external software modules to work for the proprietary software module to achieve the connection with the NFC payment device and its software, and the proprietary software module itself does not need to actively cooperate with the external software module. The external software module creates the desired data for the proprietary software module by itself, and basically does not affect the work of the proprietary software module.

[0065] Merchants can obtain external software modules from the service provider of NFC payment devices in advance and deploy (for example, install the corresponding software) on the cash register. The external software module is used to determine whether the user has triggered the target business in the business page of the own software module. The target business can be one or more businesses that the NFC payment device is capable of at least partially executing, such as payment, member login, discount collection and other businesses. It should be noted that in order to avoid developing and modifying the own software module of the cash register, the external software module does not directly access the interface with the own software module to obtain the user's behavior in the business page of the own software module, but infers the user's behavior based on location detection and pre-performed page area marking.

[0066] The cash register device will display the business page of its own software module. It can detect the coordinates of the screen of the cash register device that are triggered (for example, by detecting clicks, slides, scrolls and other events to determine whether they are triggered) through system interfaces (so that no additional assistance from its own software module is required) and other means as the location data of the user's interaction in the business page; of course, the location data can also be determined by methods such as image detection of page effect changes. In such cases, the location data may not be expressed in specific coordinates, but may be expressed in other forms such as reference objects and markers.

[0067] In addition to detecting the location data, it is also necessary to infer the business significance corresponding to the location data, for example, this can be achieved based on a pre-built decision model. In one or more embodiments of this specification, it can be determined whether the user has triggered the target business in the business page based on the location data and the decision model, wherein the decision model is obtained by the service provider of the NFC payment device based on the page focus area pre-marked by the proprietary software module for the cash register device.

[0068] For ease of understanding, one or more embodiments of this specification provide a flowchart of a labeling model preprocessing solution, see Figure 2 .

[0069] Figure 2 The process in includes the following steps:

[0070] S202: Before determining whether the user has triggered the target business on the business page based on the location data and the decision model, pre-mark a page focus area for one or more SaaS cash register applications to obtain marking data, wherein the page focus area includes a focus button and related text areas.

[0071] Since the payment service provider needs to serve multiple merchants, there will be multiple cash register devices in the system, and not all merchants will choose the same cash register software (the above-mentioned proprietary software module). Different cash register software may have different page layouts, which will affect the accuracy of subsequent judgments. Therefore, during preprocessing, different cash register software can be processed separately. For example, in step S202, assuming that the cash register software is a SaaS cash register application, if there are multiple SaaS cash register applications, it is necessary to mark the page focus area for each SaaS cash register application.

[0072] The page focus area is the area related to the target business, and the information provided in it may be helpful for subsequent judgment, such as the corresponding trigger button area (such as payment button, member login button, etc.), text area (such as the display area of ​​the amount to be paid, the display area of ​​the member nickname), etc.

[0073] By marking, the scope of these areas can be determined, so that it is convenient to determine whether the user has interacted with any of the areas based on coordinates, events and other data.

[0074] Of course, in addition to the relatively reliable and accurate method of decision-making models, other methods can also be used. For example, based on location data, a simpler regular expression (which can be designed in advance based on the coordinate relationship on the business page to filter different page areas) is matched to determine whether the target business is triggered.

[0075] S204: Convert the marked data into a decision model that reflects the corresponding relationship between the location and the business or event.

[0076] The decision model can be in various forms, for example, a simple model in the form of a relatively simple data table, or a more complex model such as a decision tree, decision forest, or even a machine learning model, etc. A location can represent a corresponding area range (for example, a button), a business can represent a business (for example, payment) that may be triggered by a specified type of interaction (for example, click, etc.) within the area range, and an event can represent what type of interaction.

[0077] In the case of multiple SaaS cash register applications, multiple decision models can be obtained based on their respective targeted labeled data. Among these decision models, the decision model corresponding to each SaaS cash register application is selected, which helps to make subsequent judgments more accurately.

[0078] S206: Send the decision model to the cashier device where the corresponding SaaS cashier application is located.

[0079] The decision model can be sent to an external software module deployed on the cash register device to determine whether the user has triggered the target business on the business page; or the decision model can be called remotely. Figure 2 After the preprocessing process in is completed, you can execute Figure 1 The process in .

[0080] Continue to Figure 1 The next steps are described in .

[0081] S104: If yes, interacting with the NFC payment device through the external software module, so that the NFC payment device obtains capability requirement data adapted to its service provider.

[0082] If the target service itself has sufficient information to support correct execution, capability requirement data can be generated locally or on the NFC payment device directly based on the target service.

[0083] In one or more embodiments of the present specification, in order to correctly execute the target business, in addition to the information reflected by the target business itself, the external software module may also need to obtain other relevant auxiliary data. The auxiliary data can reflect the personalized factors of the target business, such as the difference between the current user and other users (for example, user nickname, etc.), the specific number of resources involved (for example, the amount to be paid, etc.), and the specific selection value of the user for the optional items (for example, whether to use the discount, etc.).

[0084] External software can implement screenshots by calling system capabilities or its own capabilities without the need for additional cooperation from its own software modules, and then obtain the required auxiliary data based on the screenshot image. Based on the target business and auxiliary data, capability requirement data can be generated to guide the NFC payment device on how to perform the target business. In this case, interacting with the NFC payment device may include: taking a screenshot of the area related to the target business in the business page, obtaining a screenshot image, and interacting with the NFC payment device, wherein the capability requirement data is generated based on the screenshot image.

[0085] In addition to the method of obtaining auxiliary data by taking screenshots, auxiliary data can also be obtained by monitoring the voice broadcast of the cash register device (if any), actively asking through synthetic voice, etc.

[0086] In one or more embodiments of this specification, the capability requirement data can be as light as possible (e.g., simple character strings, simple messages, or text with small data volume, etc.). In this case, the capability requirement data is generated by an external software module and then transmitted from the cash register device to the NFC payment device. In this way, the transmission capability requirement is relatively low (e.g., it can be transmitted based on small serial port instructions), which also helps to improve efficiency. On the contrary, if the transmission capability is strong, the screenshot image and service data can also be used as capability requirement data (with relatively larger data volume) and transmitted to the NFC payment device for further analysis and use by the NFC payment device.

[0087] S106: On the NFC payment device, execute the corresponding target service according to the capability requirement data, and return the execution result data to the cash register device.

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

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

[0090] pass Figure 1The method makes it unnecessary for payment service providers of NFC payment devices to have their customers (such as merchants, cash register service providers, etc.) develop and transform cash register devices and their own software modules (such as SaaS cash register applications), integrate software development kit processing interfaces, etc. Instead, they only need to simply deploy external software modules provided by the payment service provider on the cash register devices, connect the cash register devices to the NFC payment devices through methods such as serial ports, and conveniently access the NFC payment support capabilities. The own software modules do not need to make cumbersome interface calls for NFC payment devices, and do not need to cooperate with external software modules for additional development. Instead, the external software modules actively The proprietary software module detects the user's interaction position, and based on the pre-prepared decision model, infers whether there is an opportunity for the NFC payment device to play a role. Then, capability requirement data (for example, interface call data) is generated based on targeted screenshots, and then the proprietary software module interacts with the NFC payment device to help the cash register and its proprietary software module to use the NFC payment support capability. It can be seen that this solution is mainly transformed and deployed by the payment service provider itself. Customers can easily expand access to NFC payment devices without development and modification. It is more user-friendly and also helps payment service providers to expand NFC payment business more widely.

[0091] based on Figure 1 This specification also provides some specific implementation plans and extension plans of the method, which will be described below.

[0092] Generally speaking, the performance of cash register devices is stronger than that of NFC payment devices, especially desktop cash register devices. Therefore, it is considered to use the computing power of cash register devices to generate capacity requirement data by external software modules. Based on this, one or more embodiments of this specification provide a flow chart of a capacity requirement data processing solution, see Figure 3 .

[0093] Figure 3 The process in includes the following steps:

[0094] S302: Perform OCR recognition on the screenshot image through the external software module to obtain recognition result data.

[0095] In one or more embodiments of the present specification, capability requirement data adapted to the service provider of the NFC payment device is generated based on the target business and the recognition result data. The above-mentioned auxiliary data can be obtained from the recognition result data. For example, it has been determined that the target business is to pay the current order. Through OCR recognition, the amount to be paid entered by the cashier is identified in the screenshot image including the input area of ​​the amount to be paid. It can be known that the currently required capabilities include: the NFC payment device assists the current consumer in paying the amount to be paid.

[0096] S304: Determine, according to the target service, an interface to be called that is adapted to the service provider of the NFC payment device.

[0097] S306: Determine input parameters adapted to the interface to be called according to the recognition result data.

[0098] Continuing with the payment example, the interface to be called is, for example, an interface for requesting the NFC payment device to read the payment code value from the consumer's mobile phone based on near-field communication sensing. The input parameters include, for example, the amount to be paid. The payment code value to be read is the code value corresponding to the amount to be paid, and based on the payment code value, the authority is granted to deduct the amount to be paid from the current consumer's account.

[0099] S308: Generate interface calling data as capability requirement data according to the interface to be called and the input parameters.

[0100] In one or more embodiments of the present specification, the interface call data may be an interface call request that complies with a preset interface standard for an NFC payment device, thereby facilitating direct use of the NFC payment device; alternatively, the interface call data or other forms of capability requirement data may be lighter description data, and may even be simply described in natural language, and then further converted and used by the NFC payment device.

[0101] S310: Sending the capability requirement data to the NFC payment device via the cash register device.

[0102] If the interface call data is an interface call request, the sending process is equivalent to the external software module calling the interface provided by the software on the NFC payment device. Otherwise, the sending process is just a relatively simple data transmission process. For this type of situation, for example, a simple message (such as a small number of words, a short string, individual fields, etc.) can be generated by the external software module according to the screenshot image, and the simple message can be sent from the cash register device to the NFC payment device through serial communication, so that the NFC payment device converts the simple message into the interface call data adapted to its service provider as the capability requirement data; in this way, the requirements for external software modules and transmission capabilities can be reduced, and the impact on the cash register device will be further reduced, which will help improve security.

[0103] According to the above description, in order to facilitate implementation and be more intuitive, one or more embodiments of this specification also provide a flowchart of a specific implementation scheme of the near field communication service processing method, see Figure 4 .exist Figure 4In the scenario, the above-mentioned cash register device is specifically a Windows POS machine used by the merchant's offline store, and the proprietary software module is specifically a SaaS cash register application installed on the Windows POS machine.

[0104] Figure 4 The scheme includes two stages: pre-processing preparation stage and actual operation stage.

[0105] The pretreatment preparation stage mainly includes the following steps:

[0106] Run the automated collection and marking software provided by the payment service provider, and mark the key buttons and text areas related to payment, membership, and other traffic patterns in the SaaS cash register application according to the instructions.

[0107] The marked data is converted into specific model data such as coordinates and events to form a decision model, which is uploaded to the cloud and stored in association with the corresponding SaaS cash register application identifier for accurate distribution.

[0108] The actual operation phase mainly includes the following steps:

[0109] Distribute the decision model to the Windows POS machine where the corresponding SaaS cash register application is located, and deploy the detection and processing software provided by the payment service provider (that is, the above-mentioned external software module) on the Windows POS machine. Start it automatically when the machine is turned on. This can pre-process the security issues of the system registry and device security software and obtain the corresponding self-start permissions.

[0110] Monitor the system interface to pay attention to the interaction trends on the screen and / or keyboard of the Windows POS machine (for example, using the touch screen or keyboard to click the button on the business page displayed on the screen), obtain the coordinates of the interaction, and then combine the decision model to determine whether the target business such as payment or member login is triggered.

[0111] If a target business such as payment or member login is triggered, a screenshot of the relevant local area is executed according to the decision model to obtain a screenshot image.

[0112] Perform OCR recognition on the screenshot image to obtain the recognized text, and then combine it with the target business determined previously to convert it into specific interface calls and parameter input.

[0113] The interface call and parameter input are passed from the Windows POS machine to the NFC payment device through small instructions (with a small amount of data to be transmitted), and the NFC payment device performs payment, member login and other services accordingly. For the transmission method here, for example, the two devices can be connected through the KD4 serial port, supporting two-way communication of small instructions between the two devices.

[0114] After the NFC payment device performs payment, membership and other target services, it simulates the human interface device through the Human Interface Device (HID) protocol, and fills the obtained data corresponding to the target service (for example, the service code value) back into the corresponding input box of the SaaS cash register application of the Windows POS machine, thereby realizing the connection of the business flow between the SaaS cash register application and the software on the NFC payment device. Among them, the human interface device protocol supports the one-way transmission mode from the NFC payment device to the Windows POS machine, which facilitates the efficient direct backfilling of data without going through the above-mentioned external software module.

[0115] In the previous solution, users are directly allowed to trigger the target business through the original buttons and other areas of the own software module. However, for some cash register applications, the prompt information for the area may be more rigorous, and they do not originally support NFC. Therefore, there may be ambiguity or conflict with NFC-related fields, which may cause user misunderstanding. In order to reduce this risk, this application considers adding an additional page layout patch to indirectly help users correctly trigger the target business, combined with Figure 5 To explain, Figure 5 A flow chart of a page layout patch processing solution is provided for one or more embodiments of the present specification.

[0116] Figure 5 The process in includes the following steps:

[0117] S502: Generate a visualized page layout patch according to the target business.

[0118] The page layout patch can be made into a control form such as a button or a slider, and is a part of an external software module. It can provide more correct and reliable prompts for the page layout patch to facilitate user interaction.

[0119] In one or more embodiments of the present specification, a business page simulation style learned based on the business page can be obtained; based on the target business and the business page simulation style, a page layout patch with a visual style consistent with the business page is generated to facilitate subsequent supplementary layout, and after the layout, the global appearance is coordinated, so that users can more easily understand the page layout patch as an original part of the business page.

[0120] S504: Generate an additional local layer for the business page, and display the page layout patch in the local layer.

[0121] In order to prevent the possible interaction in other areas of the business page from being affected, the size of the page layout patch can be made as sufficient as possible to avoid unnecessary expansion of the scope. The corresponding local layers can also be limited to a sufficient range as much as possible.

[0122] In addition to the method of adding additional layers, if the cash register equipment and the proprietary software module have given authorization, the page layout patch can also be embedded directly into the business page through other methods such as front-end code injection, so that the integration effect is better.

[0123] S506: Determine whether the user has triggered the page layout patch on the business page.

[0124] Since the page layout patch can provide more accurate prompts, when there is a need to use NFC payment capabilities, the user can more accurately trigger the page layout patch. This action actually shows the user's intention to trigger the target service. Therefore, the external software module will then actually trigger the target service on behalf of the user.

[0125] S508: If so, automatically trigger the service control of the own software module corresponding to the target service, and determine that the user has triggered the target service.

[0126] In this case, the judgment result obtained in step S102 is yes. It can be seen that in this process, there is no need for the cooperation of the own software module for development and transformation, and the usability of the solution for users is further improved.

[0127] Figure 1 The cash register device and NFC payment device are described as a whole from the perspective of the whole. For payment service providers, the transformation is mainly reflected in the above-mentioned external software modules. Therefore, based on the same idea, the description is re-made from the perspective of external software modules. Figure 6 , Figure 6 A flowchart of another near field communication service processing method provided for one or more embodiments of this specification.

[0128] This other near field communication service processing method is applied to an external software module provided by a service provider of an NFC payment device, and the external software module is pre-deployed on a cash register device. Figure 6 The process in includes the following steps:

[0129] S602: Detecting location data of a user interacting in a business page of a proprietary software module of the cash register device, and determining whether the user has triggered a target business in the business page based on the location data.

[0130] S604: If yes, interact with the NFC payment device so that the NFC payment device obtains capability requirement data adapted to its service provider, and executes corresponding target services according to the capability requirement data.

[0131] You can refer to the previous description to understand Figure 6 The steps in are not repeated here.

[0132] Since the external software module is provided by the service provider of the NFC payment device, there is no need for merchants, cash register equipment and cash register software to develop and modify it. It is more friendly to them and helps to increase merchants' enthusiasm for expanding the use of NFC payment devices.

[0133] Based on the same idea, one or more embodiments of this specification also provide devices and apparatuses corresponding to the above methods, such as Figure 7 to Figure 11 The apparatus and device can accordingly execute the above method and related optional solutions.

[0134] Figure 7 A schematic diagram of the structure of a near field communication service processing device provided in one or more embodiments of this specification is applied to a system including a cash register device and an NFC payment device, and the device includes:

[0135] The service action trigger detection module 702 detects, on the cash register device, the location data of the user's interaction in the service page of the cash register device's own software module through the external software module provided by the service provider of the NFC payment device, and determines whether the user has triggered the target service in the service page according to the location data;

[0136] Adaptation capability requirement module 704: if yes, interacting with the NFC payment device through the external software module, so that the NFC payment device obtains capability requirement data adapted to its service provider;

[0137] The target service interactive execution module 706 executes the corresponding target service on the NFC payment device according to the capability requirement data, and returns the execution result data to the cash register device.

[0138] Optionally, the business action trigger detection module 702 determines whether the user has triggered the target business in the business page based on the location data and the decision model, wherein the decision model is obtained by the service provider of the NFC payment device based on the page focus area pre-marked by its own software module for the cash register device.

[0139] Optionally, the adaptation capability requirement module 704 takes a screenshot of an area related to the target business in the business page to obtain a screenshot image, and interacts with the NFC payment device, wherein the capability requirement data is generated according to the screenshot image.

[0140] Optionally, the proprietary software module of the cash register device includes a SaaS cash register application, and the SaaS cash register application and the NFC payment device are provided by different service providers.

[0141] Optionally, the system includes multiple cash register devices, and at least two cash register devices among the multiple cash register devices have different SaaS cash register applications, which are provided by different service providers.

[0142] Optionally, it also includes:

[0143] The external software preprocessing module 708, before determining whether the user has triggered the target business on the business page according to the location data and the decision model, marks a page focus area for one or more SaaS cashier applications to obtain marking data, wherein the page focus area includes a focus button and a related text area;

[0144] Converting the marked data into a decision model reflecting the corresponding relationship between the location and the business or event;

[0145] The decision model is sent to the cash register device where the corresponding SaaS cash register application is located.

[0146] Optionally, the adaptability requirement module 704 performs OCR recognition on the screenshot image through the external software module to obtain recognition result data;

[0147] Generating capability requirement data adapted to the service provider of the NFC payment device according to the target business and the identification result data;

[0148] The capability requirement data is sent to the NFC payment device through the cash register device.

[0149] Optionally, the adaptation capability requirement module 704 determines, according to the target business, an interface to be called that is adapted to the service provider of the NFC payment device;

[0150] Determine input parameters adapted to the interface to be called according to the recognition result data;

[0151] According to the interface to be called and the input parameters, interface calling data is generated as capability requirement data.

[0152] Optionally, the adaptation capability requirement module 704 generates a simple message according to the screenshot image through the external software module, and sends the simple message from the cash register device to the NFC payment device through serial port communication, so that the NFC payment device converts the simple message into interface call data adapted to its service provider as capability requirement data.

[0153] Optionally, the execution result data includes a service code value of the user corresponding to the target service;

[0154] The target business interaction execution module 706 fills the business code value of the user corresponding to the target business into the corresponding input box of the own software module of the cash register device through the human-machine interface device protocol.

[0155] Optionally, the business action trigger detection module 702 generates a visualized page layout patch according to the target business;

[0156] For the business page, generate an additional local layer, and display the page layout patch in the local layer;

[0157] Determine whether the user has triggered the page layout patch on the business page;

[0158] If so, the service control of the own software module corresponding to the target service is automatically triggered, and it is determined that the user has triggered the target service.

[0159] Optionally, the business action trigger detection module 702 obtains a business page simulation style learned from the business page;

[0160] A page layout patch whose visual style is consistent with the business page is generated according to the target business and the business page simulation style.

[0161] Optionally, the target service can be executed on the cash register device in a manner other than NFC;

[0162] The target service interaction execution module 706 executes the target service in an NFC manner on the NFC payment device according to the capability requirement data.

[0163] Optionally, the target business includes: payment or member login.

[0164] Figure 8 A schematic diagram of the structure of another near field communication service processing device provided in one or more embodiments of this specification, which is applied to an external software module provided by a service provider of an NFC payment device, and the external software module is pre-deployed on a cash register device, and the device includes:

[0165] A detection and judgment module 802 detects the location data of the user's interaction in the business page of the self-owned software module of the cash register device, and judges whether the user triggers the target business in the business page according to the location data;

[0166] Interaction module 804: If yes, interact with the NFC payment device so that the NFC payment device obtains capability requirement data adapted to its service provider and executes the corresponding target business according to the capability requirement data.

[0167] Fig. 9 A schematic diagram of the structure of a cash register device provided in one or more embodiments of this specification, wherein the cash register device includes a proprietary software module and an external software module provided by a service provider of the NFC payment device;

[0168] The self-owned software module provides a business page to the user so that the user can interact in the business page;

[0169] The external software module detects the location data of the user's interaction in the business page, and determines whether the user has triggered a target business in the business page according to the location data;

[0170] If yes, interact with the NFC payment device so that the NFC payment device obtains capability requirement data adapted to its service provider;

[0171] The proprietary software module receives execution result data returned by the NFC payment device and obtained by executing a corresponding target service according to the capability requirement data.

[0172] Fig.10 A schematic diagram of the structure of a near field communication service processing device provided for one or more embodiments of this specification is applied to a system including a cash register device and an NFC payment device, and the near field communication service processing device includes:

[0173] at least one processor; and,

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

[0175] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute:

[0176] On the cash register device, detecting the location data of the user interacting in the service page of the own software module of the cash register device through the external software module provided by the service provider of the NFC payment device, and judging whether the user has triggered the target service in the service page according to the location data;

[0177] If yes, interact with the NFC payment device so that the NFC payment device obtains capability requirement data adapted to its service provider;

[0178] On the NFC payment device, the corresponding target service is executed according to the capability requirement data, and the execution result data is returned to the cash register device.

[0179] Fig.11 A schematic diagram of the structure of another near field communication service processing device provided in one or more embodiments of this specification, which is applied to an external software module provided by a service provider of an NFC payment device, and the external software module is pre-deployed on a cash register device, and the near field communication service processing device includes:

[0180] at least one processor; and,

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

[0182] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute:

[0183] Detecting location data of a user interacting in a business page of a proprietary software module of the cash register device, and determining whether the user has triggered a target business in the business page based on the location data;

[0184] If so, interact with the NFC payment device so that the NFC payment device obtains capability requirement data adapted to its service provider, and executes the corresponding target business according to the capability requirement data.

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

[0186] On the cash register device, detecting the location data of the user interacting in the service page of the own software module of the cash register device through the external software module provided by the service provider of the NFC payment device, and judging whether the user has triggered the target service in the service page according to the location data;

[0187] If yes, interacting with the NFC payment device through the external software module, so that the NFC payment device obtains capability requirement data adapted to its service provider;

[0188] On the NFC payment device, the corresponding target service is executed according to the capability requirement data, and the execution result data is returned to the cash register device.

[0189] One or more embodiments of this specification also provide another non-volatile computer storage medium, which is applied to an external software module provided by a service provider of an NFC payment device, and the external software module is pre-deployed on a cash register device, and the medium stores computer executable instructions, and the computer executable instructions are set to:

[0190] Detecting location data of a user interacting in a business page of a proprietary software module of the cash register device, and determining whether the user has triggered a target business in the business page based on the location data;

[0191] If so, interact with the NFC payment device so that the NFC payment device obtains capability requirement data adapted to its service provider, and executes the corresponding target business according to the capability requirement data.

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

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

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

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

[0196] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification may be in the form of complete hardware embodiments, complete software embodiments, or embodiments in combination with software and hardware. Moreover, the embodiments of this specification may be in the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

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

[0198] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0199] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

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

[0201] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

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

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

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

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

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

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

Claims

1. A near field communication service processing method, applied to a system including a cash register device and an NFC payment device, the method comprising: On the cash register device, detecting the location data of the user interacting in the service page of the own software module of the cash register device through the external software module provided by the service provider of the NFC payment device, and judging whether the user has triggered the target service in the service page according to the location data; If yes, interacting with the NFC payment device through the external software module, so that the NFC payment device obtains capability requirement data adapted to its service provider, wherein the capability includes NFC payment support capability; On the NFC payment device, the corresponding target service is executed according to the capability requirement data, and the execution result data is returned to the cash register device.

2. The method according to claim 1, wherein judging whether the user has triggered the target service on the service page according to the location data specifically comprises: According to the location data and the decision model, it is determined whether the user has triggered the target business in the business page, wherein the decision model is obtained by the service provider of the NFC payment device based on the page focus area pre-marked by the proprietary software module of the cash register device.

3. The method according to claim 1, wherein the interacting with the NFC payment device comprises: A screenshot is taken of an area related to the target business in the business page to obtain a screenshot image, and the NFC payment device is interacted with, wherein the capability requirement data is generated according to the screenshot image.

4. The method according to claim 2, wherein the proprietary software module of the cash register device comprises a SaaS cash register application, and the SaaS cash register application and the NFC payment device are provided by different service providers.

5. The method as claimed in claim 4, wherein the system comprises a plurality of cash register devices, and at least two of the plurality of cash register devices have different SaaS cash register applications, which are provided by different service providers.

6. The method according to claim 4, before judging whether the user has triggered the target service in the service page according to the location data and the decision model, the method further comprises: Marking a page focus area for one or more SaaS cash register applications to obtain marking data, wherein the page focus area includes a focus button and a related text area; Converting the marked data into a decision model reflecting the corresponding relationship between the location and the business or event; The decision model is sent to the cash register device where the corresponding SaaS cash register application is located.

7. The method according to claim 3, wherein the interacting with the NFC payment device so that the NFC payment device obtains capability requirement data adapted to its service provider comprises: Performing OCR recognition on the screenshot image through the external software module to obtain recognition result data; Generating capability requirement data adapted to the service provider of the NFC payment device according to the target business and the identification result data; The capability requirement data is sent to the NFC payment device through the cash register device.

8. The method according to claim 7, wherein generating capability requirement data adapted to the service provider of the NFC payment device according to the target service and the identification result data comprises: According to the target business, determine an interface to be called that is adapted to the service provider of the NFC payment device; Determine input parameters adapted to the interface to be called according to the recognition result data; According to the interface to be called and the input parameters, interface calling data is generated as capability requirement data.

9. The method according to claim 3, wherein the interaction with the NFC payment device so that the NFC payment device obtains capability requirement data adapted to its service provider comprises: A simple message is generated according to the screenshot image through the external software module, and the simple message is sent from the cash register device to the NFC payment device through serial port communication, so that the NFC payment device converts the simple message into interface call data adapted to its service provider as capability requirement data.

10. The method according to claim 1, wherein the execution result data comprises a service code value of the user corresponding to the target service; The step of returning the execution result data to the cash register device specifically includes: Through the human-machine interface device protocol, the business code value of the user corresponding to the target business is filled back into the corresponding input box of the proprietary software module of the cash register device.

11. The method according to claim 1, wherein determining whether the user has triggered the target service in the service page specifically comprises: Generate visual page layout patches based on target business; For the business page, generate an additional local layer, and display the page layout patch in the local layer; Determine whether the user has triggered the page layout patch on the business page; If so, the service control of the own software module corresponding to the target service is automatically triggered, and it is determined that the user has triggered the target service.

12. The method according to claim 11, wherein generating a visualized page layout patch according to the target business specifically comprises: Obtaining a business page simulation style learned from the business page; A page layout patch whose visual style is consistent with the business page is generated according to the target business and the business page simulation style.

13. The method according to claim 1, wherein the target service can be executed on the cash register device in a manner other than NFC; The executing of the corresponding target service on the NFC payment device according to the capability requirement data specifically includes: On the NFC payment device, the target service is executed based on the NFC method according to the capability requirement data.

14. The method according to claim 1, wherein the target service comprises: Payment or member login.

15. A near field communication service processing method, applied to an external software module provided by a service provider of an NFC payment device, the external software module being pre-deployed on a cash register device, the method comprising: Detecting location data of a user interacting in a business page of a proprietary software module of the cash register device, and determining whether the user has triggered a target business in the business page based on the location data; If so, interact with the NFC payment device so that the NFC payment device obtains capability requirement data adapted to its service provider, and executes corresponding target services according to the capability requirement data, wherein the capability includes NFC payment support capability.

16. A near field communication service processing device, applied to a system including a cash register device and an NFC payment device, the device comprising: A service action trigger detection module detects, on the cash register device, location data of user interaction in a service page of the cash register device's own software module through an external software module provided by the service provider of the NFC payment device, and determines, based on the location data, whether the user has triggered a target service in the service page; Adaptation capability requirement module, if yes, interacts with the NFC payment device through the external software module, so that the NFC payment device obtains capability requirement data adapted to its service provider, the capability including NFC payment support capability; The target service interaction execution module executes the corresponding target service on the NFC payment device according to the capability requirement data, and returns the execution result data to the cash register device.

17. The device according to claim 16, wherein the service action trigger detection module determines whether the user has triggered the target service in the service page according to the location data and the decision model, wherein: The decision model is obtained by the service provider of the NFC payment device according to the page focus area pre-marked by the proprietary software module of the cash register device.

18. The apparatus according to claim 16, wherein the adaptability requirement module takes a screenshot of the area related to the target business in the business page to obtain a screenshot image and interacts with the NFC payment device, wherein: The capability requirement data is generated based on the screenshot image.

19. The apparatus according to claim 17, wherein the proprietary software module of the cash register device comprises a SaaS cash register application, and the SaaS cash register application and the NFC payment device are provided by different service providers.

20. The apparatus as claimed in claim 19, wherein the system comprises a plurality of cash register devices, and at least two of the plurality of cash register devices have different SaaS cash register applications, which are provided by different service providers.

21. The apparatus of claim 19, further comprising: The external software preprocessing module, before determining whether the user has triggered the target business on the business page according to the location data and the decision model, marks a page focus area for one or more SaaS cashier applications to obtain marking data, wherein the page focus area includes a focus button and a related text area; Converting the marked data into a decision model reflecting the corresponding relationship between the location and the business or event; The decision model is sent to the cash register device where the corresponding SaaS cash register application is located.

22. The device according to claim 18, wherein the adaptability requirement module performs OCR recognition on the screenshot image through the external software module to obtain recognition result data; Generating capability requirement data adapted to the service provider of the NFC payment device according to the target business and the identification result data; The capability requirement data is sent to the NFC payment device through the cash register device.

23. The apparatus according to claim 22, wherein the adaptability requirement module determines, according to the target service, an interface to be called that is adapted to the service provider of the NFC payment device; Determine input parameters adapted to the interface to be called according to the recognition result data; According to the interface to be called and the input parameters, interface calling data is generated as capability requirement data.

24. A cash register device, comprising a proprietary software module and an external software module provided by a service provider of an NFC payment device; The self-owned software module provides a business page to the user so that the user can interact in the business page; The external software module detects the location data of the user's interaction in the business page, and determines whether the user has triggered a target business in the business page according to the location data; If yes, interact with the NFC payment device so that the NFC payment device obtains capability requirement data adapted to its service provider, wherein the capability includes NFC payment support capability; The proprietary software module receives execution result data returned by the NFC payment device and obtained by executing a corresponding target service according to the capability requirement data.

25. A near field communication service processing device, applied to an external software module provided by a service provider of an NFC payment device, the external software module being pre-deployed on a cash register device, the near field communication service processing device comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute: Detecting location data of a user interacting in a business page of a proprietary software module of the cash register device, and determining whether the user has triggered a target business in the business page based on the location data; If so, interact with the NFC payment device so that the NFC payment device obtains capability requirement data adapted to its service provider, and executes corresponding target services according to the capability requirement data, wherein the capability includes NFC payment support capability.

Images