Near field communication service processing method, apparatus and device, and point-of-sale device

Abstract

Disclosed in the embodiments of the present disclosure is a near field communication service processing method. The method is applied to a system comprising a point-of-sale device and an NFC payment device. The method comprises: on a point-of-sale device, detecting, by means of an external software module provided by a service provider of an NFC payment device, position data of interaction of a user in a service page of a self-owned software module of the point-of-sale device, and on the basis of the position data, determining whether the user has triggered a target service in the service page; if so, interacting with the NFC payment device by means of the external software module, such that the NFC payment device acquires capability requirement data adapted to the service provider thereof; and on the NFC payment device, executing the corresponding target service on the basis of the capability requirement data, and returning execution result data to the point-of-sale device.

Description

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

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

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

[0003] With the popularization of smart phones supporting NFC function, NFC technology is also more applied in the payment field. For example, merchants deploy NFC payment devices at the cash register, and users can interact with NFC payment devices through NFC-enabled mobile phones to make payments, which is more convenient.

[0004] At present, NFC payment devices and corresponding payment applications are provided by a special payment service provider. The merchant has usually deployed other service provider's cash register equipment and cash register software used on the cash register equipment at the cash register, mainly Software as a Service (SaaS) cash register software. In this case, if the merchant wants to normally use the NFC payment device provided by the payment service provider to obtain corresponding NFC payment support capability, it needs to be developed and accessed to make the cash register equipment and its cash register software and the NFC payment device and its payment application can be normally docked. Therefore, the merchant or the service provider of the cash register equipment and its cash register software (referred to as the 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). Moreover, because most of the cash register software technology stack is old and has poor maintainability, changing the code may trigger many online problems. Furthermore, in actual application, there are many cash register equipment and its cash register software, involving different service providers. Therefore, with the popularization and spread of NFC payment devices, the total development and access cost of numerous customers will be higher.

[0005] Therefore, for the cash register equipment and its cash register software of the merchant, a more friendly solution is needed to extend and access the NFC payment device to enable it to obtain NFC payment support capability. SUMMARY

[0006] One or more embodiments of the present disclosure provide a near field communication service processing method, device, equipment and cash register device to solve the technical problem that a merchant's cash register device and its cash register software need a more friendly solution that can extend to access an NFC payment device to enable the NFC payment support capability.

[0007] To solve the above technical problem, one or more embodiments of the present disclosure are implemented as follows.

[0008] One or more embodiments of the present disclosure provide a near field communication service processing method applied to a system including a cash register device and an NFC payment device. The method includes: detecting, on the cash register device, position data of a user interacting 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 NFC payment device, judging whether the user triggers a target service in the service page according to the position data, if yes, interacting with the NFC payment device through the external software module to enable the NFC payment device to obtain capability requirement data adapted to the service side of the NFC payment device, wherein the capability requirement data is generated according to the screenshot image, and executing a corresponding target service according to the capability requirement data on the NFC payment device and returning execution result data to the cash register device.

[0009] One or more embodiments of the present disclosure provide a near field communication service processing method applied to an external software module provided by a service side of an NFC payment device. The external software module is pre-deployed on a cash register device. The method includes: detecting position data of a user interacting 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 NFC payment device to enable the NFC payment device to obtain capability requirement data adapted to the service side of the NFC payment device, and executing a corresponding target service according to the capability requirement data.

[0010] The one or more embodiments of the present disclosure provide 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, on the cash register device, detecting position data of a user interacting in a service page of a self-owned software module of the cash register device through an external software module provided by a service provider of the NFC payment device, judging whether the user triggers a target service in the service page according to the position data; an adaptation capability requirement module, if yes, interacting with the NFC payment device through the external software module to make the NFC payment device obtain capability requirement data adapted to its service provider; a target service interaction execution module, on the NFC payment device, executing a corresponding target service according to the capability requirement data and returning execution result data to the cash register device.

[0011] The one or more embodiments of the present disclosure provide 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 device comprising: a detection and judgment module, detecting position data of a user interacting 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; an interaction module, if yes, interacting with the NFC payment device to make the NFC payment device obtain capability requirement data adapted to its service provider and executing a corresponding target service according to the capability requirement data.

[0012] The one or more embodiments of the present disclosure provide a cash register device comprising a self-owned software module and an external software module provided by a service provider of an NFC payment device; the self-owned software module provides a service page to a user for the user to interact in the service page; the external software module detects position data of the user interacting in the service page, judges whether the user triggers a target service in the service page according to the position data, and if yes, interacts with the NFC payment device to make the NFC payment device obtain capability requirement data adapted to its service provider; the self-owned software module receives execution result data returned by the NFC payment device, the execution result data being obtained by executing a corresponding target service according to the capability requirement data.

[0013] One or more embodiments of the present disclosure provide a near field communication service processing device applied to a system including a cash register device and an NFC payment 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, and the instructions are executed by the at least one processor to enable the at least one processor to perform: detecting, on the cash register device, position data of user interaction in a service page of a native software module of the cash register device through a foreign software module provided by a service party of the NFC payment device, judging whether the user triggers a target service in the service page according to the position data, and if yes, interacting with the NFC payment device through the foreign software module to enable the NFC payment device to obtain capability requirement data adapted to the service party thereof; and performing, on the NFC payment device, a corresponding target service according to the capability requirement data and returning execution result data to the cash register device.

[0014] One or more embodiments of the present disclosure provide a near field communication service processing device applied to a foreign software module provided by a service party of an NFC 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, and the instructions are executed by the at least one processor to enable the at least one processor to perform: detecting position data of user interaction in a service page of a native software module of the cash register device, judging whether the user triggers a target service in the service page according to the position data, and if yes, interacting with the NFC payment device to enable the NFC payment device to obtain capability requirement data adapted to the service party thereof and performing a corresponding target service according to the capability requirement data.

[0015] The at least one technical solution adopted by one or more embodiments of the present disclosure can achieve the following beneficial effects: for a payment service provider of an NFC payment device, without the need for customers (such as merchants, cash register service providers, etc.) to develop and transform 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 only need to simply deploy an external software module provided by the payment service provider on the cash register device, connect the cash register device and the NFC payment device through a serial port or the like, and access the NFC payment support capability conveniently. The own software module also does not need to make cumbersome interface calls for the NFC payment device, and also does not need to cooperate with the external software module for additional development, but actively detects the interaction position of the user for the own software module by the external software module. Optionally, it can also be based on a pre-prepared decision model to speculate whether there is an opportunity for the NFC payment device to play a role at present, and then generate capability requirement data (such as interface call data) through a screenshot or the like in a targeted manner, and then replace the own software module and the NFC payment device to interact, so as to help the cash register device and its own software module to realize the use of the NFC payment support capability. As can be seen, this scheme is mainly transformed and deployed by the payment service provider itself, and the customer can conveniently expand and access the NFC payment device without development and transformation, which is more friendly, and also helps the payment service provider to expand the NFC payment business more widely. BRIEF DESCRIPTION OF DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the related art, the drawings needed to be used in the embodiments or related art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments described in the present disclosure, and other drawings can also be obtained by those skilled in the art without creative labor.

[0017] FIG. 1 is a flowchart of a near field communication business processing method according to one or more embodiments of the present disclosure;

[0018] FIG. 2 is a flowchart of a marking model preprocessing scheme according to one or more embodiments of the present disclosure;

[0019] FIG. 3 is a flowchart of a capability requirement data processing scheme according to one or more embodiments of the present disclosure;

[0020] FIG. 4 is a flowchart of a specific implementation of a near field communication business processing method according to one or more embodiments of the present disclosure;

[0021] FIG. 5 is a flowchart of a page layout patch processing scheme according to one or more embodiments of the present disclosure;

[0022] FIG. 6 is a flow diagram of another method for processing near field communication business according to one or more embodiments of the present disclosure;

[0023] FIG. 7 is a structural diagram of a device for processing near field communication business according to one or more embodiments of the present disclosure;

[0024] FIG. 8 is a structural diagram of another device for processing near field communication business according to one or more embodiments of the present disclosure;

[0025] FIG. 9 is a structural diagram of a cash register device according to one or more embodiments of the present disclosure;

[0026] FIG. 10 is a structural diagram of a device for processing near field communication business according to one or more embodiments of the present disclosure;

[0027] FIG. 11 is a structural diagram of another device for processing near field communication business according to one or more embodiments of the present disclosure. DETAILED DESCRIPTION

[0028] The embodiments of the present disclosure provide a method, device, equipment, storage medium and cash register device for processing near field communication business.

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

[0030] In view of the problems mentioned in the background, the present application considers that the service provider of the NFC payment device, referred to as the payment service provider, actively detects the 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 cash register software) to try to discover the NFC payment device usage demand in real time without the development work such as interface modification of the cash register software. If the NFC payment device usage demand is found, the payment service provider generates interface call data according to the decision result and the relevant page screenshot to help the cash register device and the cash register software use the NFC payment device capability, so that the merchant can conveniently and efficiently access the NFC payment device, and the merchant almost does not need to pay for the modification cost.

[0031] The scheme of the present application will be described below based on the above general idea.

[0032] FIG. 1 is a flowchart of a near field communication service processing method provided by one or more embodiments of the present disclosure, which is applied to a system including a cash register device and an NFC payment device, and in which the cash register device and the NFC payment device are connected by wire or wirelessly, and the NFC payment device assists the work of the cash register device. 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.

[0033] The cash register device and the NFC payment device are provided by different service providers (usually different companies independent of each other, which can have no cooperation relationship between them). The cash register device is a basic device usually used by a merchant at a cash register, commonly a desktop or handheld POS machine (usually based on a 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, and two-dimensional code payment, but does not support NFC payment. Therefore, the scheme of the present application is intended to expand the NFC payment support capability. The NFC payment device can provide NFC payment support capability, and a user can perform a payment-related service based on near field communication by bringing a mobile terminal supporting NFC function, such as a smart phone or a smart watch, close to the NFC payment device for induction.

[0034] The flowchart in FIG. 1 includes the following steps.

[0035] S102: On the cash register device, detect position data of a user interacting in a service page of a self-owned software module of the cash register device through an external software module provided by a service provider of the NFC payment device, and determine whether the user (such as a cashier, a consumer, etc.) triggers a target service in the service page according to the position data.

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

[0037] 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 software and hardware integrated solution provided by the same service provider. Of course, the merchant can also select cash register software provided by another service provider according to the current cash register device and needs, especially for Windows POS machines (based on Windows operating system), which have 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.

[0038] The foreign software module is provided by a service provider of the NFC payment device (such as the payment service provider mentioned above), and the corresponding software pre-installed on the NFC payment device is also provided by the service provider. Since the software and the foreign software module are under the same research and development system of the service provider, the connection between the software and the foreign software module is easier and lower in cost to implement. The problem in the background art is essentially the connection 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, and other reasons. The present application mainly uses the foreign software module to perform the task for the self-owned software module, realizes the connection with the NFC payment device and its software, and the self-owned software module itself does not need to actively cooperate with the foreign software module. The foreign software module itself creates the desired data for the self-owned software module, and basically does not affect the work of the self-owned software module.

[0039] The merchant can obtain the foreign software module from the service provider of the NFC payment device in advance and deploy (such as install corresponding software) it on the cash register device. The foreign software module is used to determine whether the user triggers a target business in the business page of the self-owned software module. The target business can be one or more businesses that the NFC payment device has the ability to at least partially perform, such as payment, member login, and discount collection. It should be noted that, in order to avoid developing and modifying 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 business page of the self-owned software module, but infers the user's behavior based on location detection and pre-marked page regions.

[0040] The cash register device will display the business page of its self-owned software module. The coordinates of the screen of the cash register device that are triggered (such as whether they are triggered by detecting clicks, swipes, scrolls, and other events) can be detected as position data of the user's interaction in the business page through system interfaces (so that the self-owned software module does not need to assist additionally); of course, the position data can also be determined by detecting changes in page effects such as images, in which case the position data is not necessarily represented by specific coordinates, but can be represented by other forms such as reference objects and markers.

[0041] In addition to detecting position data, the business meaning of the position data also needs to be inferred, which can be achieved based on a pre-created decision model. In one or more embodiments of the present disclosure, whether the user triggers a target business in the business page can be determined according to the position data and the decision model, wherein the decision model is obtained by the service provider of the NFC payment device according to the pre-marked page attention area of the self-owned software module of the cash register device.

[0042] For ease of understanding, one or more embodiments of the present disclosure provide a flowchart of a marking model preprocessing scheme, see FIG. 2.

[0043] The flow in FIG. 2 includes the following steps.

[0044] S202: Before judging whether the user triggers a target business in the business page according to the position data and the decision model, mark the page attention area of one or more SaaS cashier applications in advance to obtain marking data, wherein the page attention area includes an attention button and a related text area.

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

[0046] 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.

[0047] Through 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.

[0048] Of course, in addition to the decision model which is a relatively reliable and accurate way, other ways 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 judge whether the target business is triggered.

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

[0050] 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, and the like. The position can represent a corresponding area range (such as a certain button), the business can represent a business (such as payment) that can be triggered by an interaction of a specified type (such as clicking, etc.) in the area range, and the event can represent what type of interaction.

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

[0052] S206: The decision model is issued to the POS device where the corresponding SaaS POS application is located.

[0053] The decision model can be issued to an external software module deployed on the POS device to determine whether the user has triggered the target business in the business page, or the decision model can be remotely called. After the preprocessing process in FIG. 2 is completed, the process in FIG. 1 can be performed.

[0054] The subsequent steps in FIG. 1 are described as follows.

[0055] S104: If yes, the external software module interacts with the NFC payment device to enable the NFC payment device to obtain the capability requirement data adapted to the service provider thereof.

[0056] If the target business itself has sufficient information to support correct execution, the capability requirement data can be generated locally or on the NFC payment device according to the target business.

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

[0058] The external software can realize the screen capture by calling the system capability or the self capability, without the cooperation of the self 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 NFC payment device to perform the target service. In this case, the interaction with the NFC payment device can include: capturing the screen in the region related to the target service in the service page to obtain a screen capture image, and interacting with the NFC payment device, wherein the capability requirement data is generated according to the screen capture image.

[0059] In addition to the screen capture method for obtaining auxiliary data, the auxiliary data can also be obtained by means such as listening to the voice broadcast of the cash register device (if any), actively inquiring by synthesized voice, and the like.

[0060] In one or more embodiments of the present disclosure, the capability requirement data can be light data (such as a simple string, a simple message, or a small amount of text, etc.), in which case the capability requirement data is generated by the external software module and then transmitted from the cash register device to the NFC payment device, so that the transmission capability requirement is low (such as based on serial small instruction transmission), which is also helpful to improve the efficiency. Conversely, if the transmission capability is strong, the screen capture image and the service data can also be transmitted to the NFC payment device as the capability requirement data (the data amount is relatively larger), and the NFC payment device further analyzes and uses them.

[0061] S106: According to the capability requirement data, the corresponding target service is executed on the NFC payment device, and the execution result data is returned to the cash register device.

[0062] In one or more embodiments of the present disclosure, after the NFC payment device obtains the capability requirement data, it can wait for the user (such as the consumer) to approach the NFC payment device for inductive identification. If the user does not have such operation, it indicates that the user may not want to execute the target service through the NFC payment device. In this case, the NFC payment device can return to the standby state after the waiting timeout, to wait for the next opportunity. If the user cooperates, the NFC payment device can execute the target service accordingly. Of course, the consumer can also perform the NFC inductive identification in advance, and then the cashier can operate on the cash register device, so as to complete the execution of the target service under the cooperation of the cash register device and the NFC payment device.

[0063] It should be noted that the NFC payment device can only complete a part of the target business, for example, the user's payment code value can be identified as the execution result data returned to the cash register device, and the cash register device will further complete the target business according to the execution result data. Conversely, if the NFC payment device basically completes the target business, the execution result data can only be a final result for feedback to the consumer.

[0064] Through the method of FIG. 1, for the payment service provider of the NFC payment device, the customer (such as a merchant, a cash register service provider, etc.) does not need to develop and modify the cash register device and its own software module (such as a SaaS cash register application) for the cash register device, integrate a software development kit processing interface, 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 NFC payment device through a serial port or the like, and access the NFC payment support capability conveniently. The own software module also does not need to make cumbersome interface calls for the NFC 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 pre-prepared decision model, infers whether there is an opportunity for the NFC payment device to play a role at present, and then generates capability requirement data (such as interface call data) based on the screenshot in a targeted manner, and then replaces the own software module and the NFC payment device to interact, to help the cash register device and its own software module to realize the use of the NFC payment support capability. It can be seen that this scheme is mainly modified and deployed by the payment service provider itself, the customer does not need to develop and modify to conveniently expand the NFC payment device, is more friendly, and is also helpful for the payment service provider to expand the NFC payment business more widely.

[0065] Based on the method of FIG. 1, the present disclosure also provides some specific embodiments and extension schemes of the method, which will be described below.

[0066] Generally, the performance of the cash register device is stronger than that of the NFC 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 present disclosure provide a flow diagram of a capability requirement data processing scheme, as shown in FIG. 3.

[0067] The flow in FIG. 3 includes the following steps.

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

[0069] 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 NFC 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 for 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 NFC payment device assisting the current consumer to pay the to-be-paid amount.

[0070] S304: According to the target service, determine the to-be-called interface adapted to the service side of the NFC payment device.

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

[0072] Taking the payment example, the to-be-called interface 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 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 right to deduct the to-be-paid amount from the current consumer's account is obtained.

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

[0074] 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 NFC payment device, so that the NFC payment device can be directly used; 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 NFC payment device.

[0075] S310: Send the capability requirement data to the NFC payment device through the cash register device.

[0076] If the interface calling data is an interface calling request, the sending process is equivalent to a foreign software module calling an interface provided by software on the NFC payment device. Conversely, the sending process is only a relatively simple data transmission process. For such cases, the foreign software module can generate a simple message (e.g., a few words, a short string, individual fields, etc.) based on the screenshot image and send the simple message from the cash register device to the NFC payment device through serial communication, so that the NFC payment device converts the simple message into interface calling data suitable for the service side thereof as the capability requirement data. In this way, the requirements for the foreign 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.

[0077] According to the foregoing description, for the convenience of implementation and more intuitively, the disclosure one or more embodiments also provide a flowchart of a specific implementation of a near field communication service processing method, see Figure 4. In the scenario of Figure 4, the cash register device described above 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.

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

[0079] The preprocessing preparation stage mainly includes the following steps.

[0080] Run the automatic acquisition marking software provided by the payment service provider, and mark the key buttons and text areas related to payment, membership, etc. in the SaaS cash register application according to the instructions.

[0081] Convert the marked data into coordinate, event, etc. specific model data, form a decision model, and upload it to the cloud for associated storage with the identifier of the corresponding SaaS cash register application, so as to accurately distribute it.

[0082] The actual running stage mainly includes the following steps.

[0083] Distribute the decision model to the Windows POS machine where the corresponding SaaS cash register application is located, and deploy the detection processing software (i.e. the foreign software module described above) provided by the payment service provider on the Windows POS machine. The detection processing software can run automatically after starting up, and can pre-process the system registry and security issues of the device security software to obtain the corresponding self-starting permission.

[0084] Listen to the system interface to pay attention to the interaction on the screen and / or keyboard of the Windows POS machine (such as, using a touch screen or a keyboard, clicking a button in a 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.

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

[0086] The screenshot image is subjected to OCR recognition to obtain recognized text, and then combined with the target business determined in the foregoing, the recognized text is converted into specific interface calling and parameter input.

[0087] The interface calling and parameter input are transmitted from the Windows POS machine to the NFC payment device through small instructions (with less data transmission amount), and the NFC payment device executes the business such as payment and member login according to the interface calling 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.

[0088] After the NFC payment device executes the target business such as payment and member, the data (such as a business code value) corresponding to the target business is obtained through a human interface device (HID) protocol, a human interface device is simulated, and the data is backfilled into a corresponding input box of a SaaS cash register application of the Windows POS machine, so that the business flow of the SaaS cash register application and the software on the NFC payment device is connected in series. The human interface device protocol supports one-way transmission mode from the NFC payment device to the Windows POS machine, which facilitates efficient and direct backfilling of data without the need for the external software module.

[0089] 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 described in combination with FIG. 5. FIG. 5 is a flowchart of a page layout patch processing scheme provided by one or more embodiments of the present disclosure.

[0090] The flowchart in FIG. 5 includes the following steps.

[0091] S502: According to the target business, a visual page layout patch is generated.

[0092] 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, and can be prompted more correctly and reliably for the page layout patch, so as to interact with the user.

[0093] In one or more embodiments of the present disclosure, a business page simulation style learned according to a business page can be obtained; a visual style consistent with the business page is generated according to a target business and the business page simulation style, so as to facilitate subsequent supplementary layout, 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 business page originally has.

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

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

[0096] 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 business page through other methods such as front-end code injection, so that the integration effect is better.

[0097] S506: Determine whether the user triggers the page layout patch in the business page.

[0098] Since the page layout patch can be prompted more accurately, in the case of NFC payment capability use demand, the user can more accurately trigger the page layout patch, and this action actually shows the user's intention to trigger the target business, so the external software module replaces the user to actually trigger the target business.

[0099] S508: If yes, automatically trigger the business control of the self-owned software module corresponding to the target business, and determine that the user triggers the target business.

[0100] In this case, the judgment 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.

[0101] Fig. 1 is a description from the perspective of the whole of the cash register device and the NFC payment device. For the payment service provider, the modification mainly embodies in the above-mentioned foreign software module, therefore, based on the same idea, the description is made from the perspective of the foreign software module, see Fig. 6, which is a flow diagram of another NFC service processing method provided by one or more embodiments of the present disclosure.

[0102] The another NFC service processing method is applied to the foreign software module provided by the service side of the NFC payment device, and the foreign software module is pre-deployed on the cash register device. The flow in Fig. 6 includes the following steps.

[0103] S602: detecting position data of user interaction in the service page of the self-owned software module of the cash register device, and judging whether the user triggers a target service in the service page according to the position data.

[0104] S604: if yes, interacting with the NFC payment device to make the NFC payment device obtain capability requirement data adapted to the service side thereof, and executing the corresponding target service according to the capability requirement data.

[0105] The steps in Fig. 6 can be understood by referring to the foregoing description, and will not be repeated here.

[0106] Since the foreign software module is provided by the service side of the NFC payment device, it is unnecessary to develop and modify the merchant, the cash register device and the cash register software, which is friendly to them and helps to improve the enthusiasm of the merchant to expand the use of the NFC payment device.

[0107] Based on the same idea, one or more embodiments of the present disclosure further provide a device and equipment corresponding to the above-mentioned method, as shown in Figs. 7-11. The device and equipment can correspondingly execute the above-mentioned method and related optional solutions.

[0108] FIG. 7 is a structural schematic diagram of a near field communication service processing apparatus according to one or more embodiments of the present disclosure, which is applied to a system including a cash register device and an NFC payment device, and the apparatus includes: a service action trigger detection module 702, on the cash register device, detecting position data of a user interacting 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 NFC payment device, and judging whether the user triggers a target service in the service page according to the position data; an adaptation capability requirement module 704, if yes, interacting with the NFC payment device through the external software module to make the NFC payment device obtain capability requirement data adapted to the service side thereof; and a target service interaction execution module 706, on the NFC payment device, executing a corresponding target service according to the capability requirement data, and returning execution result data to the cash register device.

[0109] Optionally, the service action trigger detection module 702 judges 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 side of the NFC payment device according to a page attention area pre-marked for a self-owned software module of the cash register device.

[0110] Optionally, the adaptation capability requirement module 704 screens a region related to the target service in the service 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.

[0111] Optionally, the self-owned 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 sides.

[0112] 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 respectively provided by different service sides.

[0113] Optionally, the system further includes an external software preprocessing module 708, which marks a page attention area for one or more SaaS cash register applications to obtain marking data before judging whether the user triggers a target service in the service page according to the position data and a decision model, wherein the page attention area includes an attention button and a related text area; converts the marking data into a decision model reflecting a corresponding relationship between a position and a service or an event; and delivers the decision model to a cash register device where a corresponding SaaS cash register application is located.

[0114] Optionally, the adaptation capability requirement module 704, 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 NFC payment device according to the target service and the recognition result data; and sends the capability requirement data to the NFC payment device through the cash register device.

[0115] Optionally, the adaptation capability requirement module 704 determines a to-be-called interface adapted to the service side of the NFC payment device according to the target service; determines an input parameter adapted to the to-be-called interface according to the recognition result data; and generates interface calling data as the capability requirement data according to the to-be-called interface and the input parameter.

[0116] 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 NFC payment device through serial communication, so that the NFC payment device converts the simple message into interface calling data adapted to the service side thereof as the capability requirement data.

[0117] Optionally, the execution result data includes a business code value corresponding to the target service of the user; and 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 a self-owned software module of the cash register device through a human-computer interface device protocol.

[0118] Optionally, the business action trigger detection module 702 generates a visual page layout patch according to a target service; generates an additional local layer for the business page, and displays the page layout patch in the local layer; determines whether a user has triggered the page layout patch on the business page; if yes, automatically triggers a business control corresponding to the target service of the self-owned software module, and determines that the user has triggered the target service.

[0119] Optionally, the business action trigger detection module 702 obtains a business page simulation style learned according to the business page; and generates a visual page layout patch with consistency with the business page according to the target service and the business page simulation style.

[0120] Optionally, the target service can be executed on the cash register device in a mode other than the NFC mode; and the target service interaction execution module 706 executes the target service in the NFC payment device in the NFC mode according to the capability requirement data.

[0121] Optionally, the target service includes payment or member login.

[0122] Fig. 8 is a structural schematic diagram of another near field communication service processing apparatus provided by one or more embodiments of the present disclosure, applied to a foreign software module provided by a service party of an NFC payment device, the foreign software module being pre-deployed on a cash register device, the apparatus including: a detection and judgment module 802, detecting position data of a user interacting in a service page of a self-owned software module of the cash register device, and judging whether the user triggers a target service in the service page according to the position data; an interaction module 804, if yes, interacting with the NFC payment device to enable the NFC payment device to obtain capability requirement data adapted to its service party, and performing a corresponding target service according to the capability requirement data.

[0123] Fig. 9 is a structural schematic diagram of a cash register device provided by one or more embodiments of the present disclosure, the cash register device including a self-owned software module and a foreign software module provided by a service party of the NFC payment device; the self-owned software module provides a service page to a user for the user to interact in the service page; the foreign software module detects position data of the user interacting in the service page, judges whether the user triggers a target service in the service page according to the position data, and if yes, interacts with the NFC payment device to enable the NFC payment device to obtain capability requirement data adapted to its service party; the self-owned software module receives execution result data returned by the NFC payment device according to the capability requirement data and obtained by performing a corresponding target service.

[0124] Fig. 10 is a structural schematic diagram of a near field communication service processing device provided by one or more embodiments of the present disclosure, applied to a system including a cash register device and an NFC payment device, the near field communication service processing device including: 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: on the cash register device, detecting, by a foreign software module provided by a service party of the NFC payment device, position data of a user interacting 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, and if yes, interacting with the NFC payment device to enable the NFC payment device to obtain capability requirement data adapted to its service party; on the NFC payment device, performing a corresponding target service according to the capability requirement data, and returning execution result data to the cash register device.

[0125] FIG. 11 is a structural schematic diagram of another near field communication service processing device provided by one or more embodiments of the present disclosure, applied to a foreign software module provided by a service side of an NFC 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 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 NFC payment device to enable the NFC 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.

[0126] Based on the same idea, one or more embodiments of the present disclosure further provide a non-volatile computer storage medium applied to a system comprising a cash register device and an NFC payment device, the medium storing computer executable instructions, the computer executable instructions being configured to: on the cash register device, detecting position data of user interaction in a service page of a self-owned software module of the cash register device through a foreign software module provided by a service side of the NFC payment device, judging whether the user triggers a target service in the service page according to the position data; if yes, interacting with the NFC payment device through the foreign software module to enable the NFC payment device to obtain capability requirement data adapted to the service side thereof; on the NFC payment device, performing a corresponding target service according to the capability requirement data and returning execution result data to the cash register device.

[0127] One or more embodiments of the present disclosure further provide another non-volatile computer storage medium applied to a foreign software module provided by a service side of an NFC payment device, the foreign software module being pre-deployed on a cash register device, the medium storing computer executable instructions, the computer executable instructions being configured to: detecting 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 NFC payment device to enable the NFC 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.

[0128] 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 to be compiled is written in a specific programming language, which is called a hardware description language (HDL), and there are many such languages, 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 be aware that, as long as the method flow is logically programmed in the above-mentioned hardware description languages and programmed into an integrated circuit, a hardware circuit implementing the logical method flow can be easily obtained.

[0129] 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 also be implemented to perform the same functions in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers and embedded microcontrollers, etc. by logically programming the method steps. Therefore, such a controller can be considered as a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can even be considered as both a software module implementing a method and a structure within a hardware component.

[0130] 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.

[0131] 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 disclosure.

[0132] Those skilled in the art will understand that the embodiments of the present disclosure can be provided as a method, a system or a computer program product. Therefore, the embodiments of the present disclosure 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 disclosure 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.

[0133] The 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 flowchart block or blocks.

[0134] 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 flowchart block or blocks.

[0135] 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 flowchart block or blocks.

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

[0137] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) and / or cache memory, for storing instructions and data used by one or more of the components of the computing device. The memory can further include non-volatile memory, such as read-only memory (ROM), electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, or nonvolatile random access memory (NVRAM) for storing instructions and data used by one or more of the components of the computing device. For example, the memory can include one or more components or circuits that store programming instructions for execution by one or more of the processors of the computing device.

[0138] 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.

[0139] 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.

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

[0141] The various embodiments in the present disclosure are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on the difference from other embodiments. In particular, for the device, apparatus, 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 part of the method embodiment.

[0142] The above describes particular embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order and still achieve desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown or sequential order in order to achieve the desired results. In some implementations, multitasking and parallel processing can be advantageous or necessary.

[0143] The above descriptions merely serve as one or more embodiments of the present disclosure and are not intended to limit the present disclosure. One or more embodiments of the present disclosure can have various modifications and changes for those skilled in the art. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of one or more embodiments of the present disclosure should be included in the scope of claims of the present disclosure.

Claims

1. A method for processing near field communication (NFC) service, applied to a system comprising a cash register device and an NFC 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 through a foreign software module provided by a service provider of the NFC 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 NFC payment device through the foreign software module to make the NFC payment device obtain capability requirement data adapted to the service provider of the NFC payment device; and executing the target service according to the capability requirement data on the NFC payment device, 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 NFC payment device according to a page attention area pre-marked for the native software module of the cash register device. 3.The method of claim 1, wherein the interacting with the NFC payment device specifically comprises: taking a screenshot in a region related to the target service in the service page to obtain a screenshot image, and interacting with the NFC 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 NFC 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 among 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 a page attention area for one or more SaaS cash register applications to obtain marking data, wherein the page attention area comprises an attention button and a related text area; converting the marking data into a decision model reflecting a corresponding relationship between a position and a service or an event; and delivering the decision model to a cash register device where a corresponding SaaS cash register application is located. 7.The method of claim 3, wherein the interacting with the NFC payment device to make the NFC payment device obtain capability requirement data adapted to the service provider of the NFC payment device specifically comprises: performing OCR recognition on the screenshot image through the foreign 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 service and the recognition result data; and sending the capability requirement data to the NFC payment device through the cash register device. ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ 8. The method of claim 7, wherein the generating, according to the target service and the identification result data, the capability requirement data adapted to the service provider of the NFC payment device comprises: determining, according to the target service, a to-be-invoked interface adapted to the service provider of the NFC payment device; determining, according to the identification result data, an input parameter adapted to the to-be-invoked interface; and generating, according to the to-be-invoked interface and the input parameter, interface invocation data as the capability requirement data.

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

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

11. The method of claim 1, wherein the judging whether the user triggers a target service in the service page comprises: generating a visual page layout patch according to the target service; generating an additional local layer for the service page and displaying the page layout patch in the local layer; judging whether the user triggers the page layout patch in the service page; and if yes, automatically triggering a service 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 service page simulation style learned according to the service page; and generating a visual page layout patch with consistency between the style and the service page according to the target service and the service page simulation style.

13. The method of claim 1, wherein the target service can be executed on the cash register device based on a mode other than NFC mode; and the executing, on the NFC payment device, the corresponding target service according to the capability requirement data comprises: executing, on the NFC payment device, the target service based on NFC mode according to the capability requirement data. Payment or member login.

15. A near field communication service processing method applied to a foreign software module provided by a service provider of an NFC payment device, wherein the foreign software module is pre-deployed on a cash register device, and the method comprises: ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ 14. The method of claim 1, the target service 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 NFC payment device to enable the NFC payment device to obtain capability requirement data adapted to its service provider, and performing a corresponding target service according to the capability requirement data. 16.A near field communication service processing apparatus applied to a system comprising a cash register device and an NFC payment device, the apparatus comprising: a service action trigger detection module, on the cash register device, detecting 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 provider of the NFC payment device, and determining whether the user triggers a target service in the service page according to the position data; an adapted capability requirement module, if yes, interacting with the NFC payment device through the external software module to enable the NFC payment device to obtain capability requirement data adapted to its service provider; a target service interaction execution module, on the NFC payment device, performing a corresponding target service according to the capability requirement data, and returning 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 provider of the NFC payment device according to a pre-labeled page attention area of a self-owned software module of a 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 NFC 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 NFC payment device are provided by different service providers. 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 in the plurality of cash register devices are different and are provided by different service providers respectively. 21.The apparatus of claim 19, further comprising: an external software preprocessing module, before the determining whether the user triggers a target service in the service page according to the position data and the decision model, labeling page attention areas for one or more SaaS cash register applications to obtain labeling data, wherein the page attention areas comprise attention buttons and related text areas; converting the labeling data into a decision model reflecting a corresponding relationship between a position and a service or an event; downloading the decision model to a cash register device where a corresponding SaaS cash register application is located. 22.The apparatus of claim 18, wherein the adapted capability requirement module performs OCR identification on the screenshot image through the external software module to obtain identification result data; generates capability requirement data adapted to the service provider of the NFC payment device according to the target service and the identification result data; and sends the capability requirement data to the NFC payment device through the cash register device. 23.The apparatus of claim 22, wherein the adaptation capability requirement module is configured to: determine, according to the target service, a to-be-invoked interface adapted to a service provider of the NFC payment device; determine, according to the identification result data, an input parameter adapted to the to-be-invoked interface; and generate, according to the to-be-invoked interface and the input parameter, interface invocation data as the capability requirement data. 24.A cash register device comprising a self-owned software module and a foreign software module provided by a service provider of an NFC payment device; wherein 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, the foreign software module interacts with the NFC payment device to enable the NFC payment device to obtain capability requirement data adapted to the service provider of the NFC payment device; and the self-owned software module receives execution result data returned by the NFC payment device according to the capability requirement data and execution of the corresponding target service. 25.A near field communication service processing device applied to a foreign software module provided by a service provider of an NFC payment device, wherein the foreign software module is pre-deployed on a cash register device, and the near field communication service processing device comprises: at least one processor; and a memory in communication connection with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to: detect position data of a user 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; and if yes, the at least one processor interacts with the NFC payment device to enable the NFC payment device to obtain capability requirement data adapted to the service provider of the NFC payment device, and execute the corresponding target service according to the capability requirement data. ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​

Images