Near field communication service processing method, device and equipment, and cash register

Abstract

The embodiments of the present specification disclose a near field communication service processing method. The method is applied to a system comprising a cash register device and a near field communication based payment device, and comprises: on the cash register device, detecting, by an external software module provided by a service side of the near field communication based payment device, position data of user interaction in a service page of a self-owned software module of the cash register device, judging whether the user triggers a target service in the service page according to the position data; if yes, interacting with the near field communication based payment device through the external software module, so that the near field communication based payment device obtains capability requirement data adapted to the service side thereof; on the near field communication based payment device, executing a corresponding target service according to the capability requirement data, and returning execution result data to the cash register device.

Description

[0001] This application is a divisional application of the invention patent application No. 202411005058.5, filed with the China Patent Office on July 25, 2024, and entitled “Near Field Communication Service Processing Method, Device, and Equipment and Cash Register Equipment”, the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0002] The present specification relates to the technical field of near field communication, and in particular to a near field communication service processing method, device, and equipment and cash register equipment. BACKGROUND

[0003] Near Field Communication (NFC) is a short-range high-frequency radio technology that operates within a 20-centimeter distance at a frequency of 13.56 MHz. It is evolved from non-contact radio frequency identification (RFID) and interconnection technology, and provides a very safe and fast communication method for various electronic products.

[0004] With the popularization of the use of smart phones supporting NFC function, NFC technology is also more applied in the payment field. For example, a merchant deploys a near field communication-based payment device at a cash register, and a user can use a smart phone supporting NFC function to interact with the near field communication-based payment device to make a payment, which is convenient.

[0005] Currently, payment devices based on near field communication and corresponding payment applications are provided by a special payment service provider, and a merchant usually has deployed other service provider-provided cash register devices and cash register software used on the cash register devices, mainly Software as a Service (SaaS) cash register software, in this case, if the merchant wants to normally use the payment device based on near field communication provided by the payment service provider to obtain corresponding payment support capabilities based on near field communication, development access needs to be performed to enable the cash register device and its cash register software to normally dock with the payment device based on near field communication and its payment application. In this way, the merchant or the service provider of the cash register device and its cash register software (referred to as a customer from the perspective of the payment service provider) needs to integrate a Software Development Kit (SDK) to develop code to call and process corresponding interface logic, the customer involves development, testing, deployment and other processes, and the overall cycle is relatively long (usually several weeks or even months), and moreover, because most of the cash register software technology stacks are old and have poor maintainability, changing the code may trigger many online problems, not only that, in actual application, there are many cash register devices and their cash register software, involving different service providers, in this way, as the payment device based on near field communication is popularized and laid out, the total development access cost of the numerous customers will be higher.

[0006] Therefore, for the cash register device and its cash register software of a merchant, a more friendly solution is needed to extend access to the payment device based on near field communication to enable the merchant to obtain payment support capabilities based on near field communication. SUMMARY

[0007] One or more embodiments of the present specification provide a near field communication service processing method, device and equipment, and a cash register device, to solve the technical problem that for the cash register device and its cash register software of a merchant, a more friendly solution is needed to extend access to the payment device based on near field communication to enable the merchant to obtain payment support capabilities based on near field communication.

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

[0009] One or more embodiments of the present specification provide a near field communication service processing method, applied to a system including a cash register device and a payment device based on near field communication, and the method includes:

[0010] On the cash register device, detecting, by an extrinsic software module provided by a service provider of the payment device based on near field communication, position data of a user interacting in a service page of a native software module of the cash register device, and determining whether the user triggers a target service in the service page according to the position data.

[0011] If yes, interact with the near field communication based payment device through the external software module, so that the near field communication based payment device obtains the capability requirement data adapted to its service party, wherein the capability requirement data is generated according to the screenshot image;

[0012] On the near field communication based payment device, execute the corresponding target business according to the capability requirement data, and return execution result data to the cash register device.

[0013] One or more embodiments of the specification provide a near field communication business processing method, applied to an external software module provided by a service party of a near field communication based payment device, the external software module is pre-deployed on a cash register device, and the method comprises:

[0014] Detecting position data of user interaction in a business page of a self-owned software module of the cash register device, and judging whether the user triggers a target business in the business page according to the position data;

[0015] If yes, interact with the near field communication based payment device through the external software module, so that the near field communication based payment device obtains the capability requirement data adapted to its service party, and executes the corresponding target business according to the capability requirement data.

[0016] One or more embodiments of the specification provide a near field communication business processing device, applied to a system comprising a cash register device and a near field communication based payment device, and the device comprises:

[0017] A business action trigger detection module, on the cash register device, detects position data of user interaction in a business page of a self-owned software module of the cash register device through an external software module provided by a service party of the near field communication based payment device, and judges whether the user triggers a target business in the business page according to the position data;

[0018] An adapted capability requirement module, if yes, interacts with the near field communication based payment device through the external software module, so that the near field communication based payment device obtains the capability requirement data adapted to its service party;

[0019] A target business interaction execution module, on the near field communication based payment device, executes the corresponding target business according to the capability requirement data, and returns execution result data to the cash register device.

[0020] The one or more embodiments of the specification provide a near field communication service processing device, which is applied to an external software module provided by a service side of a near field communication-based payment device, the external software module is pre-deployed on a cash register device, and the device comprises:

[0021] a detection judgment module configured to detect position data of a user interacting in a service page of a self-owned software module of the cash register device, and determine whether the user triggers a target service in the service page according to the position data;

[0022] an interaction module configured to interact with the near field communication-based payment device if yes, so that the near field communication-based payment device obtains capability requirement data adapted to the service side thereof, and executes a corresponding target service according to the capability requirement data.

[0023] The one or more embodiments of the specification provide a cash register device, which comprises a self-owned software module and an external software module provided by a service side of a near field communication-based payment device;

[0024] The self-owned software module provides a service page for a user to interact in the service page;

[0025] The external software module detects position data of the user interacting in the service page, and determines whether the user triggers a target service in the service page according to the position data;

[0026] If yes, the external software module interacts with the near field communication-based payment device, so that the near field communication-based payment device obtains capability requirement data adapted to the service side thereof;

[0027] The self-owned software module receives execution result data returned by the near field communication-based payment device, which is obtained by executing a corresponding target service according to the capability requirement data.

[0028] The one or more embodiments of the specification provide a near field communication service processing device, which is applied to a system comprising a cash register device and a near field communication-based payment device, and the near field communication service processing device comprises:

[0029] at least one processor; and

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

[0031] 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:

[0032] On the cash register device, a location data of a user interacting in a business page of a self-owned software module of the cash register device is detected through a foreign software module provided by a service party of the near field communication based payment device, and whether the user triggers a target business in the business page is judged according to the location data;

[0033] If yes, the near field communication based payment device is interacted with through the foreign software module, so that the near field communication based payment device obtains capability requirement data adapted to the service party thereof;

[0034] On the near field communication based payment device, a corresponding target business is executed according to the capability requirement data, and execution result data is returned to the cash register device.

[0035] One or more embodiments of the present specification provide a near field communication business processing device applied to a foreign software module provided by a service party of a near field communication based payment device, the foreign software module being pre-deployed on a cash register device, and the near field communication business processing device comprising:

[0036] at least one processor; and

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

[0038] 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 execute:

[0039] detecting a location data of a user interacting in a business page of a self-owned software module of the cash register device, and judging whether the user triggers a target business in the business page according to the location data;

[0040] If yes, the near field communication based payment device is interacted with through the foreign software module, so that the near field communication based payment device obtains capability requirement data adapted to the service party thereof, and a corresponding target business is executed according to the capability requirement data.

[0041] The above at least one technical solution adopted by one or more embodiments of the present specification can achieve the following beneficial effects: for a payment service provider of a near field communication-based payment device, without the need for its customers (such as merchants, cash register service providers, etc.) to develop and modify the cash register device and its own software module (such as a SaaS cash register application), integrate a software development kit processing interface, etc., but simply deploy an external software module provided by the payment service provider on the cash register device, connect the cash register device with the near field communication-based payment device through a serial port or the like, and conveniently access the near field communication-based payment support capability. The own software module does not need to make cumbersome interface calls for the near field communication-based payment device, and does not need to cooperate with the external software module for additional development, but the external software module actively detects the user's interaction position for the own software module. Optionally, it can also be based on a pre-prepared decision model to speculate whether there is an opportunity for the near field communication-based payment device to function, and then generate capability requirement data (such as interface call data) through targeted screenshot-based methods, and then replace the own software module and the near field communication-based payment device to interact, to help the cash register device and its own software module to realize the use of the near field communication-based payment support capability. As can be seen, this scheme is mainly modified and deployed by the payment service provider itself, and the customer can conveniently expand and access the near field communication-based payment device without the need for development and modification, which is more friendly, and also helps the payment service provider to more widely expand the near field communication-based payment business. BRIEF DESCRIPTION OF DRAWINGS

[0042] In order to more clearly illustrate the technical solutions in the embodiments of the present specification or the prior art, the drawings needed to be used in the embodiments or prior art description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments described in the present specification, and those skilled in the art can also obtain other drawings according to these drawings without creative labor.

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

[0044] Figure 2 A flowchart of a label model preprocessing scheme provided by one or more embodiments of the present specification;

[0045] Figure 3 A flowchart of a capability requirement data processing scheme provided by one or more embodiments of the present specification;

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

[0047] Figure 5 A flowchart of a page layout patch processing scheme provided for one or more embodiments of the present specification;

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

[0049] Figure 7 A structural diagram of a near field communication service processing apparatus provided for one or more embodiments of the present specification;

[0050] Figure 8 A structural diagram of another near field communication service processing apparatus provided for one or more embodiments of the present specification;

[0051] Figure 9 A structural diagram of a cash register provided for one or more embodiments of the present specification;

[0052] Figure 10 A structural diagram of a near field communication service processing apparatus provided for one or more embodiments of the present specification;

[0053] Figure 11 A structural diagram of another near field communication service processing apparatus provided for one or more embodiments of the present specification. DETAILED DESCRIPTION

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

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

[0056] In view of the problems mentioned in the background, the present application considers that the service provider of the payment device based on near field communication, referred to as the payment service provider, actively creates a decision model based on the pre-processing work such as page area marking (used to understand some key areas in the business page of the cashier software) for the cash register device and its cashier software, and conducts detection to try to discover the use demand of the payment device based on near field communication in real time without the development work such as interface modification of the cashier software. If the use demand of the payment device based on near field communication is found, the payment service provider will still generate interface call data according to the decision result and the relevant page screenshot to help the cash register device and its cashier software use the payment device based on near field communication, so that the merchant can conveniently and efficiently access the payment device based on near field communication, and the merchant almost does not need to pay for the modification cost.

[0057] Based on such general idea, the scheme of the present application will be further described below.

[0058] Figure 1 A flowchart of a near field communication service processing method provided for one or more embodiments of the present specification is shown. The method is applied to a system including a cash register device and a payment device based on near field communication. In the system, the cash register device and the payment device based on near field communication are connected by wired or wireless means, and the work of the cash register device is assisted by the payment device based on near field communication. The execution subject of the flowchart can be the whole 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 payment device based on near field communication are provided by different service providers (usually independent companies, which can have no cooperation relationship between them). The cash register device is a basic device used by the merchant at the cash register, commonly a desktop or handheld POS machine (usually based on Windows or Linux operating system) and the like, which can support one or more basic payment methods, such as bank card payment, member card payment, two-dimensional code payment, etc., but does not support payment based on near field communication. Therefore, the payment support capability based on near field communication is expanded by the scheme of the present application. The payment device based on near field communication can provide payment support capability based on near field communication. The user can perform sensing by bringing the mobile terminal supporting NFC function such as smart phone, smart watch, etc. close to the payment device based on near field communication, and then performing payment-related business based on near field communication.

[0060] Figure 1 The flowchart in the above embodiment includes the following steps:

[0061] S102: On the cash register device, detecting, by an external software module provided by a service party of the near field communication based payment device, position data of user interaction in a business page of a self-owned software module of the cash register device, and judging, according to the position data, whether the user (such as a cashier, a consumer, etc.) triggers a target business in the business page.

[0062] In one or more embodiments of the present specification, in order to facilitate the distinction, the concepts of self-owned software module and external software module are used.

[0063] The self-owned software module refers to the basic cash register software installed on the cash register device, which is usually a SaaS cash register application provided by a certain SaaS application service provider. Some cash register software on the cash register device is self-contained, which usually belongs to a hardware and software integrated solution provided by the same service provider. Of course, the merchant can also select another service provider to provide cash register software according to the needs of the current cash register device, especially for Windows POS (referring to the Windows operating system-based) cash register device, which has flexibility and wide use. In addition to this, the cash register device can also be based on other common operating systems, or even a small number of self-developed systems.

[0064] The external software module is provided by the service party of the near field communication based payment device (such as the payment service provider mentioned above), and the corresponding software is pre-installed on the near field communication based payment device, which is also provided by the service provider. Since it is under the same research and development system of the service provider, the docking between the software and the external software module will be easier and lower cost to implement. The problem in the background art is essentially the docking between the software and the self-owned software module of the cash register device, which is not easy to implement due to technical differences, cost, etc. The present application mainly uses the external software module to do the work for the self-owned software module, to realize the docking with the near field communication based payment device and its software, and the self-owned software module itself also does not need to actively cooperate with the external software module. The external software module creates the data it wants for the self-owned software module, and basically does not affect the work of the self-owned software module.

[0065] The merchant can obtain a foreign software module from the service provider of the near field communication-based payment device in advance and deploy (e.g., install corresponding software) on the cash register device. The foreign software module is used to determine whether the user triggers a target service in the service page of the self-owned software module. The target service can be one or more services that the near field communication-based payment device is capable of performing at least partially, such as payment, member login, and discount collection. It should be noted that, in order to avoid development and modification of the self-owned software module of the cash register device, the foreign software module does not directly interface with the self-owned software module to obtain the user's behavior in the service page of the self-owned software module, but infers the user's behavior based on location detection and pre-marked page regions.

[0066] The cash register device displays the service page of the self-owned software module. The cash register device can detect the coordinates of the screen that are triggered (e.g., by detecting a click, swipe, scroll, or other event to determine whether the coordinates are triggered) as position data of the user's interaction in the service page through a system interface (without the need for additional assistance from the self-owned software module). Of course, the position data can also be determined by detecting changes in the image, in which case the position data is not necessarily represented by specific coordinates, but can be represented by other forms of references or markers.

[0067] In addition to detecting the position data, the business meaning of the position data needs to be inferred, which can be achieved based on a pre-built decision model. In one or more embodiments of the present specification, the user can be determined to have triggered a target service in the service page based on the position data and the decision model, wherein the decision model is obtained by the service provider of the near field communication-based payment device based on the pre-marked page attention area of the self-owned software module of the cash register device.

[0068] To facilitate understanding, one or more embodiments of the present specification provide a flowchart of a marking model preprocessing scheme, as shown in Figure 2 .

[0069] Figure 2 The flowchart in the above figure includes the following steps:

[0070] S202: Before determining whether the user triggers a target service in the service page based on the position data and the decision model, pre-marking a page attention area for one or more SaaS cash register applications to obtain marking data, wherein the page attention area includes an attention button and a related text area.

[0071] Since the payment service provider needs to serve multiple merchants, there are multiple cash register devices in the system globally, and not all merchants will choose the same cash register software (which belongs to the self-owned software module described above), and the page layout of different cash register software may be different, which will affect the accuracy of subsequent judgment, so during preprocessing, different cash register software can be processed respectively. For example, in step S202, assuming that the cash register software is a SaaS cash register application, in the case of multiple SaaS cash register applications, the page attention area needs to be marked for each SaaS cash register application.

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

[0073] By marking, the range of these areas can be determined, thereby facilitating subsequent determination of whether the user has interacted with a certain area therein according to coordinate, event, etc. data.

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

[0075] S204: Convert the marking data into a decision model reflecting the correspondence between the position and the business or event.

[0076] The form of the decision model can be diverse, such as a simple model in the form of a simple data table, a more complex model such as a decision tree, a decision forest, or a machine learning model, etc. The position can represent the corresponding area range (such as a certain button), the business can represent the business (such as payment) that may be triggered by the specified type (such as click, etc.) of interaction in the area range, and the event can represent the type of interaction.

[0077] In the case of multiple SaaS cash register applications, multiple decision models can be obtained according to the respective targeted marking data, and in these decision models, the decision model corresponding to each SaaS cash register application is selected, thereby facilitating more accurate subsequent judgment.

[0078] S206: The decision model is issued to the cash register device where the corresponding SaaS cash register application is located.

[0079] The decision model can be sent to an external software module deployed on the POS device to determine whether the user triggers the target service in the service page; or the decision model can be remotely invoked. Figure 2 After the pre-processing procedure in Figure 1 is executed, the procedure in can be executed.

[0080] The subsequent steps in Figure 1 are described.

[0081] S104: If yes, the external software module interacts with the near field communication-based payment device to enable the near field communication-based payment device to obtain the capability requirement data adapted to its service provider.

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

[0083] In one or more embodiments of the present disclosure, in order to correctly execute the target service, the external software module can need to obtain other related auxiliary data in addition to the reflected information of the target service itself, and the auxiliary data can reflect the individualized factors of the target service, such as the difference between the current user and other users (such as user nickname, etc.), the specific amount of resources involved in this time (such as the amount to be paid, etc.), the specific selection value of the user for the optional item (such as whether to use a discount, etc.), and the like.

[0084] The external software can realize screen capture by invoking system capabilities or its own capabilities without the need for additional cooperation of the self-owned software module, and then obtain the required auxiliary data according to the screen capture image. According to the target service and the auxiliary data, the capability requirement data can be generated to guide the near field communication-based payment device to specifically execute the target service. In this case, the interaction with the near field communication-based payment device can include: capturing a screen in the service page related to the target service to obtain a screen capture image, and interacting with the near field communication-based payment device, wherein the capability requirement data is generated according to the screen capture image.

[0085] In addition to the screen capture method for obtaining auxiliary data, the auxiliary data can also be obtained by listening to the voice broadcast of the POS device (if any), actively asking through synthesized voice, and the like.

[0086] In one or more embodiments of the present disclosure, the capability requirement data can be light data (e.g., simple string, simple message, or small amount of text, etc.), in which case the capability requirement data is generated by the foreign software module and uploaded from the cash register device to the near field communication based payment device, so that the transmission capability requirement is low (e.g., can be transmitted based on serial port small instruction), which helps to improve efficiency. Conversely, if the transmission capability is strong, the screenshot image and service data can also be used as the capability requirement data (relatively larger data amount), which is transmitted to the near field communication based payment device for further analysis and use by the near field communication based payment device.

[0087] S106: On the near field communication based 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.

[0088] In one or more embodiments of the present disclosure, after the near field communication based payment device obtains the capability requirement data, it can wait for the user (e.g., the consumer) to approach the mobile phone to the near field communication based payment device for inductive recognition. If the user does not perform such an operation, it indicates that the user may not want to execute the target service through the near field communication based payment device. In this case, the near field communication based payment device can return to standby state after waiting for a timeout to wait for the next opportunity. If the user cooperates, the near field communication based payment device can execute the target service accordingly. Of course, the consumer can also perform NFC inductive recognition in advance, and then the cashier can operate on the cash register device, and then complete the execution of the target service in cooperation with the cash register device and the near field communication based payment device.

[0089] It should be noted that the near field communication based payment device can only complete part of the work contained in the target service, for example, it can identify the user's payment code value as the execution result data returned to the cash register device, and then the cash register device will further complete the target service according to the execution result data. Conversely, if the near field communication based payment device basically completes the target service, the execution result data can only be a final result for feedback to the consumer.

[0090] By Figure 1The method makes it unnecessary for a payment service provider of a near field communication-based payment device to develop and modify customers such as merchants, cash register service providers, etc. for cash register devices and their own software modules (such as SaaS cash register applications), integrate software development kit processing interfaces, etc., but only needs to simply deploy an external software module provided by the payment service provider on the cash register device, connect the cash register device with the near field communication-based payment device through a serial port or the like, and access the near field communication-based payment support capability conveniently. The own software module does not need to make cumbersome interface calls for the near field communication-based payment device, and does not need to cooperate with the external software module for additional development, but the external software module actively detects the user's interaction position for the own software module, and based on a prepared decision model, infers whether there is an opportunity for the near field communication-based payment device to function, and then generates capability requirement data (such as interface call data) based on the screenshot, and then replaces the own software module and the near field communication-based payment device to interact, to help the cash register device and its own software module to realize the use of the near field communication-based payment support capability. It can be seen that this scheme is mainly modified and deployed by the payment service provider itself, and the customer can conveniently expand and access the near field communication-based payment device without development and modification, which is more friendly, and is also helpful for the payment service provider to expand the near field communication-based payment business more widely.

[0091] Based on Figure 1 the method, the specification also provides some specific embodiments and extension schemes of the method, which are described below.

[0092] Generally, the performance of the cash register device is stronger than that of the near field communication-based payment device, especially the desktop cash register device. Therefore, the computing power of the cash register device is considered to generate the capability requirement data by the external software module. Based on this, one or more embodiments of the specification provide a flowchart of a capability requirement data processing scheme, which is shown in Figure 3 .

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

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

[0095] In one or more embodiments of the present disclosure, according to the target service and the recognition result data, capability requirement data adapted to the service side of the near field communication based payment device is generated. For the recognition result data, the above-mentioned auxiliary data can be obtained therefrom, for example, it has been determined that the target service is to pay the current order, through OCR recognition, in the screenshot image including the to-be-paid amount input area, the to-be-paid amount input by the cashier is recognized, and it is further known that the current required capability includes the near field communication based payment device assisting the current consumer to pay the to-be-paid amount.

[0096] S304: According to the target service, determine the to-be-called interface adapted to the service side of the near field communication based payment device.

[0097] S306: According to the recognition result data, determine the input parameter adapted to the to-be-called interface.

[0098] Taking the payment example, the to-be-called interface is, for example, an interface for requesting the near field communication based payment device to read the payment code value from the consumer's mobile phone based on near field communication induction, and the input parameter includes, for example, the to-be-paid amount, so the payment code value to be read is the code value corresponding to the to-be-paid amount, and based on the payment code value, the to-be-paid amount can be authorized to be deducted from the current consumer's account.

[0099] S308: According to the to-be-called interface and the input parameter, generate interface calling data as capability requirement data.

[0100] In one or more embodiments of the present disclosure, the interface calling data can be an interface calling request conforming to the preset interface standard of the near field communication based payment device, so as to facilitate the direct use of the near field communication based payment device; or the interface calling data or other forms of capability requirement data can also be more lightweight description data, or even a simple natural language description, which can be further converted and used by the near field communication based payment device.

[0101] S310: Send the capability requirement data to the near field communication based payment device through the cash register device.

[0102] If the interface calling data is an interface calling request, the sending process is equivalent to an external software module calling an interface provided by software on the near field communication-based payment device. Conversely, the sending process is only a relatively simple data transmission process. For such cases, the external software module can generate a simple message (e.g., a few words, a short string, an individual field, etc.) based on the screenshot image and send the simple message from the cash register device to the near field communication-based payment device through serial communication, so that the near field communication-based payment device converts the simple message into interface calling data suitable for the service side thereof as capability requirement data. In this way, the requirements for the external software module and the transmission capability can be reduced, the impact on the cash register device will be further reduced, and the security can be improved.

[0103] According to the foregoing description, for the convenience of implementation and more intuitively, the one or more embodiments of the present specification also provide a flowchart of a specific implementation scheme of the near field communication service processing method, which is shown in Figure 4 . In Figure 4 the scenario, the cash register device is specifically a Windows POS machine used by a merchant offline store, and the self-owned software module is specifically a SaaS cash register application installed on the Windows POS machine.

[0104] Figure 4 The scheme includes two stages, a preprocessing preparation stage and an actual running stage.

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

[0106] The automatic acquisition marking software provided by the payment service provider is run, and the key buttons and text areas related to payment, membership, and the like in the SaaS cash register application are marked according to the instructions.

[0107] The marked data is converted into coordinate, event, and other specific model data to form a decision model, which is uploaded to the cloud and associated with the identifier of the corresponding SaaS cash register application for storage, so as to be accurately distributed.

[0108] The actual running stage mainly includes the following steps:

[0109] The decision model is distributed to the Windows POS machine where the corresponding SaaS cash register application is located, and the detection processing software (i.e., the external software module described above) provided by the payment service provider is deployed on the Windows POS machine and automatically started to run. The system registry and security issues of the device security software can be preprocessed, and the corresponding self-starting permission can be obtained.

[0110] The listening system interface pays attention to the interaction on the screen and / or keyboard of the Windows POS machine (such as clicking the button in the business page displayed on the screen by touch or keyboard), obtains the coordinates of the interaction, and judges whether the target business such as payment or member login is triggered according to the decision model.

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

[0112] The screenshot image is subjected to OCR recognition, the recognized text is obtained, and the target business judged in the foregoing is converted into specific interface call and parameter input.

[0113] The interface call and parameter input are transmitted from the Windows POS machine to the near field communication-based payment device through small instructions (small amount of data transmission), and the near field communication-based payment device executes the business such as payment and member login according to the interface call and parameter input. For the transmission mode herein, for example, the two devices can be connected through a KD4 serial port, and small instruction bidirectional communication between the two devices is supported.

[0114] After the near field communication-based payment device executes the target business such as payment and member, the data (such as business code value) corresponding to the target business is fed back to the corresponding input box of the SaaS cash register application of the Windows POS machine through the human interface device (HID) protocol, so as to realize the business flow series connection between the SaaS cash register application and the software on the near field communication-based payment device. The human interface device protocol supports one-way transmission mode of the near field communication-based payment device to the Windows POS machine, which facilitates efficient direct data feeding back without the need of the external software module.

[0115] In the foregoing scheme, the user directly triggers the target business through the original button area of the self-owned software module, but for some cash register applications, the prompt information of the area may be relatively strict, and the cash register application itself does not originally support NFC, so there may be ambiguity or conflict with the NFC related field, which may cause user misunderstanding. In order to reduce the risk, the present application considers indirectly helping the user to correctly trigger the target business by additionally adding a page layout patch, which is combined with Figure 5 The description is provided. Figure 5 A flowchart of a page layout patch processing scheme is provided for one or more embodiments of the present application.

[0116] Figure 5 The flowchart in the foregoing embodiment includes the following steps:

[0117] S502: generating a visual page layout patch according to the target service.

[0118] The page layout patch can be made in the form of a button or a control such as a block, and is part of an external software module, which can provide more accurate and reliable prompts for the page layout patch, so as to interact with the user.

[0119] In one or more embodiments of the present specification, a service page simulation style learned according to a service page can be obtained; a visual style consistent with the service page is generated according to the target service and the service page simulation style, so as to facilitate subsequent layout supplementing, and the overall appearance after the layout has coordination, so that the user is more likely to understand the page layout patch as a part of the service page originally has.

[0120] S504: generating an additional local layer for the service page, and displaying the page layout patch in the local layer.

[0121] In order to prevent the interaction that may occur in other areas of the service page, the size of the page layout patch can be made as much as possible, and the range can be avoided to be unnecessarily expanded, and the corresponding local layer can also be limited as much as possible within the range.

[0122] In addition to the method of adding a layer, if the cash register device and the self-owned software module are authorized, the page layout patch can also be directly embedded in the service page through other methods such as front-end code injection, so that the integration effect is better.

[0123] S506: determining whether the user triggers the page layout patch in the service page.

[0124] Since the page layout patch can provide more accurate prompts, in the case of using the payment function based on near field communication, the user can more accurately trigger the page layout patch, and this action actually shows the user's intention to trigger the target service, so the external software module will actually trigger the target service instead of the user.

[0125] S508: if yes, automatically triggering the service control of the self-owned software module corresponding to the target service, and determining that the user triggers the target service.

[0126] In this case, the determination result obtained in step S102 is yes, it can be seen that in this process, the self-owned software module does not need to be developed and transformed, and the ease of use of the scheme for the user is further improved.

[0127] Figure 1This describes the POS device and the near-field communication-based payment device as a whole, from the perspective of this entire system. For payment service providers, the modifications mainly involve the aforementioned external software modules. Therefore, based on the same approach, this description is also presented from the perspective of these external software modules. See [link / reference]. Figure 6 , Figure 6 This is a flowchart illustrating another near-field communication service processing method provided in one or more embodiments of this specification.

[0128] This alternative near-field communication service processing method is applied to an external software module provided by the service provider of a near-field communication-based payment device, which is pre-deployed on the POS device. Figure 6 The process includes the following steps:

[0129] S602: Detect the location data of the user's interaction on the business page of the proprietary software module of the POS device, and determine whether the user has triggered the target business on the business page based on the location data.

[0130] S604: If so, then interact with the near-field communication-based payment device to enable the near-field communication-based payment device to obtain capability requirement data adapted to its service provider, and execute the corresponding target service according to the capability requirement data.

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

[0132] Since the external software modules are provided by the service providers of the near-field communication (NFC)-based payment devices, there is no need for merchants, POS devices, and POS software to develop or modify them. This is more user-friendly for them and helps to increase merchants' enthusiasm for expanding the use of NFC-based payment devices.

[0133] Based on the same idea, one or more embodiments of this specification also provide apparatus and devices corresponding to the above methods, such as... Figures 7-11 As shown. The apparatus and equipment are capable of performing the above methods and related alternatives accordingly.

[0134] Figure 7 This specification provides a schematic diagram of a near-field communication service processing device according to one or more embodiments, applied to a system including a cash register device and a near-field communication-based payment device. The device includes:

[0135] The business action trigger detection module 702 detects, on the cash register device, position data of user interaction in a business page of a native software module of the cash register device through an external software module provided by a service provider of the near field communication-based payment device, and determines whether the user triggers a target business in the business page according to the position data.

[0136] The adaptive capability requirement module 704 interacts with the near field communication-based payment device through the external software module to make the near field communication-based payment device obtain capability requirement data adapted to the service provider of the near field communication-based payment device if the determination result is yes.

[0137] The target business interaction execution module 706 executes a corresponding target business on the near field communication-based payment device according to the capability requirement data, and returns execution result data to the cash register device.

[0138] Optionally, the business action trigger detection module 702 determines whether the user triggers a target business in the business page according to the position data and a decision model, where the decision model is obtained by a service provider of the near field communication-based payment device according to a page attention area pre-marked for a native software module of the cash register device.

[0139] Optionally, the adaptive capability requirement module 704 performs screenshot on an area related to the target business in the business page to obtain a screenshot image, and interacts with the near field communication-based payment device, where the capability requirement data is generated according to the screenshot image.

[0140] Optionally, the native software module of the cash register device includes a SaaS cash register application, and the SaaS cash register application and the near field communication-based payment device are provided by different service providers.

[0141] Optionally, the system includes a plurality of cash register devices, and SaaS cash register applications of at least two cash register devices in the plurality of cash register devices are different and are provided by different service providers, respectively.

[0142] Optionally, the system further includes:

[0143] The external software preprocessing module 708 marks a page attention area for one or more SaaS cash register applications to obtain marking data before determining whether the user triggers a target business in the business page according to the position data and a decision model, where the page attention area includes an attention button and a related text area.

[0144] The marking data is converted into a decision model reflecting a corresponding relationship between a position and a business or an event.

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

[0146] Optionally, the adaptation capability requirement module 704 performs OCR identification on the screenshot image through the foreign software module to obtain identification result data.

[0147] According to the target service and the identification result data, generate capability requirement data adapted to the service side of the near field communication-based payment device.

[0148] The capability requirement data is sent to the near field communication-based payment device through the cash register device.

[0149] Optionally, the adaptation capability requirement module 704 determines, according to the target service, a to-be-called interface adapted to the service side of the near field communication-based payment device.

[0150] According to the identification result data, determine an input parameter adapted to the to-be-called interface;

[0151] According to the to-be-called interface and the input parameter, generate interface calling data as capability requirement data.

[0152] Optionally, the adaptation capability requirement module 704 generates a simple message according to the screenshot image through the foreign software module, and sends the simple message from the cash register device to the near field communication-based payment device through serial communication, so that the near field communication-based payment device converts the simple message into interface calling data adapted to the service side thereof as capability requirement data.

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

[0154] The target service interaction execution module 706 backfills the business code value corresponding to the target service of the user into a corresponding input box of the self-owned software module of the cash register device through a human-computer interface device protocol.

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

[0156] An additional local layer is generated for the business page, and the page layout patch is displayed in the local layer.

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

[0158] If yes, the self-owned software module automatically triggers a business control corresponding to the target business, and determines that the user triggers the target business.

[0159] Optionally, the business action trigger detection module 702 acquires a business page simulation style learned according to the business page;

[0160] According to the target business and the business page simulation style, a visual style is generated, and the page layout patch has consistency with the business page.

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

[0162] The target business interaction execution module 706 executes the target business based on NFC on the near field communication-based payment device according to the capability requirement data.

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

[0164] Figure 8 Another structural schematic diagram of a near field communication business processing apparatus provided for one or more embodiments of the present specification is provided, which is applied to an external software module provided by a service side of a near field communication-based payment device, the external software module is pre-deployed on a cash register device, and the apparatus includes:

[0165] The detection judgment module 802 detects position data of a user interacting in a business page of a self-owned software module of the cash register device, and judges whether the user triggers a target business in the business page according to the position data.

[0166] The interaction module 804 interacts with the near field communication-based payment device if yes, so that the near field communication-based payment device obtains capability requirement data adapted to a service side thereof, and executes a corresponding target business according to the capability requirement data.

[0167] Figure 9 A structural schematic diagram of a cash register device provided for one or more embodiments of the present specification includes a self-owned software module and an external software module provided by a service side of a near field communication-based payment device;

[0168] The self-owned software module provides a business page to a user, so that the user interacts in the business page.

[0169] The external software module detects position data of the user interacting in the business page, and judges whether the user triggers a target business in the business page according to the position data.

[0170] If yes, interact with the near field communication based payment device to make the near field communication based payment device obtain the capability requirement data adapted to its service party;

[0171] The self-owned software module receives execution result data returned by the near field communication based payment device, which is obtained by executing corresponding target business according to the capability requirement data.

[0172] Figure 10 A structural schematic diagram of a near field communication business processing device is provided for one or more embodiments of the present specification, applied to a system including a cash register device and a near field communication based payment device, and the near field communication business processing device includes:

[0173] At least one processor; and,

[0174] A memory in communication connection with the at least one processor; wherein,

[0175] 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 execute:

[0176] On the cash register device, detect position data of user interaction in a business page of a self-owned software module of the cash register device through an external software module provided by a service party of the near field communication based payment device, and determine whether the user triggers a target business in the business page according to the position data;

[0177] If yes, interact with the near field communication based payment device to make the near field communication based payment device obtain the capability requirement data adapted to its service party;

[0178] On the near field communication based payment device, execute corresponding target business according to the capability requirement data, and return execution result data to the cash register device.

[0179] Figure 11 Another structural schematic diagram of a near field communication business processing device is provided for one or more embodiments of the present specification, applied to an external software module provided by a service party of a near field communication based payment device, and the external software module is deployed on a cash register device in advance, and the near field communication business processing device includes:

[0180] At least one processor; and,

[0181] A memory in communication connection with the at least one processor; wherein,

[0182] 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:

[0183] detecting position data of user interaction in a service page of a self-owned software module of the cash register device, and determining whether the user triggers a target service in the service page according to the position data;

[0184] If yes, interacting with the near field communication-based payment device to enable the near field communication-based payment device to obtain capability requirement data adapted to its service party, and performing a corresponding target service according to the capability requirement data.

[0185] Based on the same idea, one or more embodiments of the present specification also provide a nonvolatile computer storage medium applied to a system including a cash register device and a near field communication-based payment device, and the medium stores computer executable instructions, and the computer executable instructions are configured to:

[0186] detecting, on the cash register device, position data of user interaction in a service page of a self-owned software module of the cash register device through an external software module provided by a service party of the near field communication-based payment device, and determining whether the user triggers a target service in the service page according to the position data;

[0187] If yes, interacting with the near field communication-based payment device through the external software module to enable the near field communication-based payment device to obtain capability requirement data adapted to its service party;

[0188] performing a corresponding target service according to the capability requirement data on the near field communication-based payment device, and returning execution result data to the cash register device.

[0189] One or more embodiments of the present specification also provide another nonvolatile computer storage medium applied to an external software module provided by a service party of a near field communication-based 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 configured to:

[0190] detecting position data of user interaction in a service page of a self-owned software module of the cash register device, and determining whether the user triggers a target service in the service page according to the position data;

[0191] If yes, interacting with the near field communication-based payment device to enable the near field communication-based payment device to obtain capability requirement data adapted to its service party, and performing a corresponding target service according to the capability requirement data.

[0192] In the 1990s, it was quite obvious to distinguish whether an improvement in a technology was in hardware (e.g., improvement in circuit structures of diodes, transistors, switches, etc.) or in software (improvement in method flow). However, as technology has evolved, many improvements in method flow today can be considered as direct improvements in hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structures by programming the improved method flow into hardware circuits. Therefore, it cannot be said that an improvement in a method flow cannot be implemented by hardware entity modules. For example, a programmable logic device (PLD) (e.g., a field programmable gate array (FPGA)) is an integrated circuit whose logic function is determined by user programming of the device. A digital system is "integrated" on a PLD by the designer programming it, rather than by asking a chip manufacturer to design and fabricate a custom integrated circuit chip. Moreover, instead of manually fabricating integrated circuit chips, this programming is now mostly implemented by "logic compiler" software, which is similar to software compilers used in program development, and the original code before compilation is also written in a specific programming language, which is called a hardware description language (HDL), and 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, RHDL (Ruby Hardware Description Language), etc., and the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also be aware that it is quite easy to obtain hardware circuits implementing the logical method flow by only logically programming the method flow in the above-mentioned hardware description languages and programming it into an integrated circuit.

[0193] The controller can be implemented in any suitable way, for example, the controller can take the form of a microprocessor or processor and a computer readable medium storing computer readable program code, such as software or firmware, executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller and an embedded microcontroller, examples of which 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 will also know that, in addition to being implemented in pure computer readable program code, the controller can equally well be implemented to perform the same functions using logic gates, switches, an application specific integrated circuit, a programmable logic controller and an embedded microcontroller, etc. by means of a logical programming of the method steps. The controller can thus be considered as a hardware component, and the means comprised therein for performing the various functions can be considered as structures within the hardware component. Alternatively, the means for performing the various functions can even be considered as both a software module implementing the method and a structure within the hardware component.

[0194] The systems, apparatuses, modules or units illustrated by the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can 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 sake of description, the above apparatuses are described in functional division and are described respectively. Of course, the functions of the units can be implemented in the same or multiple software and / or hardware when implementing the present specification.

[0196] Those skilled in the art will understand that the embodiments of the present specification can be provided as a method, a system or a computer program product. Therefore, the embodiments of the present specification can take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware aspects. Moreover, the embodiments of the present specification can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0197] The specification is presented with reference to flow diagrams and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the specification. It will be understood that each block of the flow diagrams and / or block diagrams, and combinations of blocks in the flow diagrams 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 processing element 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 the flow diagrams and / or block diagrams block or blocks. Figure 1 one or more flow or multiple flows and / or blocks Figure 1 one or more flow or multiple flows and / or blocks

[0198] These computer program instructions can also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the function specified in the flow diagrams and / or block diagrams block or blocks. Figure 1 one or more flow or multiple flows and / or blocks Figure 1 one or more flow or multiple flows and / or blocks

[0199] These computer program instructions can 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 the flow diagrams and / or block diagrams block or blocks. Figure 1 one or more flow or multiple flows and / or blocks Figure 1 one or more flow or multiple flows and / or blocks

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

[0201] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) and / or cache memory, non-volatile memory, such as read-only memory (ROM), EPROM, and / or flash memory, etc. The memory is an example of computer-readable media.

[0202] Computer-readable media includes permanent and non-permanent, movable and non-movable media that can be implemented by any method or technology to store information. The 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 technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to a computing device. According to the definition herein, computer-readable media does not include transitory media such as modulated data signals and carriers.

[0203] It should also be noted that the terms "comprising", "containing", or any other variant thereof are intended to cover non-exclusive inclusion, such that a process, method, article or apparatus that comprises a list of elements does not only include those elements, but also includes other elements not explicitly listed or inherent to such a process, method, article or apparatus. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article or apparatus that includes the element.

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

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

[0206] The above-described embodiments of the application have special structure and can achieve the desired results. Other embodiments can have different structures and achieve the same results. The purpose of the above-described embodiments is to illustrate the principles of the application and not to limit the scope of the application. The scope of the application is defined by the claims and their equivalents. Other embodiments are within the scope of the claims.

[0207] The above description is merely illustrative of the embodiments of the present application and is not intended to limit the scope of the present application. Various modifications can be made by those skilled in the art based upon the teachings disclosed herein. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiments of the present application shall fall within the scope of the claims of the present application.

Claims

1. A method for processing a near field communication service, applied to a system comprising a cash register device and a near field communication based payment device, the method comprising: detecting, on the cash register device, position data of a user interacting in a service page of a native software module of the cash register device by a foreign software module provided by a service provider of the near field communication based payment device, and determining whether the user triggers a target service in the service page according to the position data; if yes, interacting with the near field communication based payment device by the foreign software module to make the near field communication based payment device obtain capability requirement data adapted to the service provider of the near field communication based payment device, the capability including near field communication based payment support capability; on the near field communication based payment device, performing a corresponding target service according to the capability requirement data, and returning execution result data to the cash register device. 2.The method of claim 1, wherein the determining whether the user triggers a target service in the service page according to the position data specifically comprises: determining whether the user triggers a target service in the service page according to the position data and a decision model, wherein the decision model is obtained by the service provider of the near field communication based payment device according to a pre-marked page attention area of the native software module of the cash register device. 3.The method of claim 1, wherein the interacting with the near field communication based payment device specifically comprises: taking a screenshot of an area related to the target service in the service page to obtain a screenshot image, and interacting with the near field communication based payment device, wherein the capability requirement data is generated according to the screenshot image. 4.The method of claim 2, wherein the native software module of the cash register device comprises a SaaS cash register application, and the SaaS cash register application and the near field communication based payment device are provided by different service providers. 5.The method of claim 4, wherein the system comprises a plurality of cash register devices, and the SaaS cash register applications of at least two cash register devices of the plurality of cash register devices are different and are provided by different service providers respectively. 6.The method of claim 4, wherein before the determining whether the user triggers a target service in the service page according to the position data and a decision model, the method further comprises: marking page attention areas for one or more SaaS cash register applications to obtain marking data, wherein the page attention areas include attention buttons and related text areas; converting the marking data into a decision model reflecting a corresponding relationship between a position and a service or an event; and downloading the decision model to a cash register device on which a corresponding SaaS cash register application is located. 7.The method of claim 3, wherein the interacting with the near field communication based payment device to make the near field communication based payment device obtain capability requirement data adapted to the service provider of the near field communication based payment device specifically comprises: performing OCR recognition on the screenshot image by the foreign software module to obtain recognition result data. According to the target service and the identification result data, generate capability requirement data adapted to the service side of the near field communication based payment device; Through the cash register device, send the capability requirement data to the near field communication based payment device.

8. The method of claim 7, wherein the generating, according to the target service and the identification result data, capability requirement data adapted to the service side of the near field communication based payment device comprises: determining, according to the target service, a to-be-invoked interface adapted to the service side of the near field communication based payment device; determining, according to the identification result data, an input parameter adapted to the to-be-invoked interface; generating, according to the to-be-invoked interface and the input parameter, interface invocation data as capability requirement data.

9. The method of claim 3, wherein the interacting with the near field communication based payment device to enable the near field communication based payment device to obtain capability requirement data adapted to the service side thereof comprises: generating, according to the screenshot image, a simple message by the foreign software module, and sending the simple message from the cash register device to the near field communication based payment device through serial communication, to enable the near field communication based payment device to convert the simple message into interface invocation data adapted to the service side thereof as capability requirement data.

10. The method of claim 1, wherein the execution result data comprises a business code value corresponding to the target service of the user; the returning execution result data to the cash register device comprises: returning, by a human-computer interface device protocol, the business code value corresponding to the target service of the user to a corresponding input box of a self-owned software module of the cash register device.

11. The method of claim 1, wherein the determining whether the user triggers a target service in the business page comprises: generating a visual page layout patch according to the target service; generating an additional local layer for the business page, and displaying the page layout patch in the local layer; determining whether the user triggers the page layout patch in the business page; if yes, automatically triggering a business control corresponding to the target service of the self-owned software module, and determining that the user triggers the target service.

12. The method of claim 11, wherein the generating a visual page layout patch according to the target service comprises: obtaining a business page simulation style learned according to the business page; generating a visual page layout patch with consistency between the style and the business page according to the target service and the business page simulation style.

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

14. The method of claim 1, the target service comprising: Payment or member login.

15. A near field communication service processing method applied to an external software module provided by a service side of a near field communication-based payment device, the external software module being pre-deployed on a cash register device, the method comprising: detecting position data of user interaction in a service page of a self-owned software module of the cash register device, and determining whether the user triggers a target service in the service page according to the position data; if yes, interacting with the near field communication-based payment device to enable the near field communication-based payment device to obtain capability requirement data adapted to the service side thereof, and performing a corresponding target service according to the capability requirement data, the capability including near field communication-based payment support capability.

16. A near field communication service processing apparatus applied to a system comprising a cash register device and a near field communication-based payment device, the apparatus comprising: a service action trigger detection module configured to detect, on the cash register device, position data of user interaction in a service page of a self-owned software module of the cash register device through an external software module provided by a service side of the near field communication-based payment device, and determine whether the user triggers a target service in the service page according to the position data; an adapted capability requirement module configured to, if yes, interact with the near field communication-based payment device through the external software module to enable the near field communication-based payment device to obtain capability requirement data adapted to the service side thereof, the capability including near field communication-based payment support capability; a target service interaction execution module configured to perform a corresponding target service according to the capability requirement data on the near field communication-based payment device, and return execution result data to the cash register device.

17. The apparatus of claim 16, wherein the service action trigger detection module determines whether the user triggers a target service in the service page according to the location data and a decision model. The decision model is obtained by the service side of the near field communication-based payment device according to a pre-marked page attention area of the self-owned software module of the cash register device.

18. The apparatus of claim 16, wherein the adaptation capability requirement module is configured to capture a screenshot of a region associated with the target service in the service page to obtain a screenshot image, and interact with the near field communication based payment device, and wherein, The capability requirement data is generated according to the screenshot image.

19. The apparatus of claim 17, wherein the self-owned software module of the cash register device comprises a SaaS cash register application, and the SaaS cash register application and the near field communication-based payment device are provided by different service sides.

20. The apparatus of claim 19, wherein the system comprises a plurality of cash register devices, and SaaS cash register applications of at least two cash register devices of the plurality of cash register devices are different and are provided by different service sides, respectively.

21. The apparatus of claim 19, further comprising: an external software preprocessing module configured to, before the determining whether the user triggers the target service in the service page according to the position data and the decision model, mark page attention areas for one or more SaaS cash register applications to obtain marking data, wherein the page attention areas comprise an attention button and a related text area; convert the marking data into a decision model reflecting a corresponding relationship between a position and a service or an event; issue the decision model to a cash register device on which a corresponding SaaS cash register application is located. 22.The apparatus of claim 18, wherein the adaptation capability requirement module, through the foreign software module, performs OCR recognition on the screenshot image to obtain recognition result data; generates capability requirement data adapted to the service side of the near field communication based payment device according to the target service and the recognition result data; sends the capability requirement data to the near field communication based payment device through the cash register device. 23.The apparatus of claim 22, wherein the adaptation capability requirement module, according to the target service, determines an interface to be invoked adapted to the service side of the near field communication based payment device; determines input parameters adapted to the interface to be invoked according to the recognition result data; generates interface invocation data as capability requirement data according to the interface to be invoked and the input parameters. 24.A cash register device comprising a self-owned software module and a foreign software module provided by a service side of a near field communication based payment device; the self-owned software module provides a service page to a user for interaction by the user in the service page; the foreign software module detects position data of the user in the service page, and determines whether the user triggers a target service in the service page according to the position data; if yes, interacts with the near field communication based payment device to make the near field communication based payment device obtain capability requirement data adapted to the service side thereof, the capability including near field communication based payment support capability; the self-owned software module receives execution result data returned by the near field communication based payment device according to the capability requirement data and obtained by performing a corresponding target service. 25.A near field communication service processing device applied to a foreign software module provided by a service side of a near field communication based payment device, the foreign software module being pre-deployed on 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 memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform: detecting position data of a user in a service page of a self-owned software module of the cash register device, and determining whether the user triggers a target service in the service page according to the position data; if yes, interacting with the near field communication based payment device to make the near field communication based payment device obtain capability requirement data adapted to the service side thereof, and performing a corresponding target service according to the capability requirement data, the capability including near field communication based payment support capability.

Images