Peripheral interface calling method and system based on business process, equipment and medium

Abstract

The invention discloses a peripheral interface calling method, system, equipment and medium based on a business process, and the method comprises the following steps: embedding a universal equipment processing module in a client program of a self-service terminal; accessing memory data in the client program based on the general equipment processing module; a general equipment processing module is adopted to support an external data configuration file; defining a data return rule in the data configuration file, and naming in combination with a business process; in response to the business process request, providing an interface service corresponding to the business process based on the client program, the universal equipment processing module and the data configuration file; according to the method, the client program debugging verification service process on the self-service terminal can be simpler and quicker, the problem that the service process is coupled with peripheral hardware is solved, the development efficiency of the client program is improved, the development cost of the client program is reduced, the defects in the prior art are overcome, and the method has higher application value.

Description

Technical Field

[0001] The present invention relates to the technical field of self-service terminals, and in particular to a method, system, device and medium for calling an external device interface based on a business process. Background Art

[0002] At present, many industries have applied a large number of self-service terminal devices to improve work efficiency and user satisfaction. These self-service terminal devices have greatly facilitated the handling of user business. Usually, these self-service terminal devices are deployed with a set of client programs that realize their business functions. These client programs complete their predetermined functions by calling various peripheral hardware on the self-service terminal devices. For client programs, the way to call peripheral hardware is to call the peripheral interface function indirectly or directly. However, no matter how the peripheral interface function is called, there is a problem of inflexibility.

[0003] In addition, during the development of the client program of the self-service terminal device, a lot of debugging and verification work is often required, because there are many codes that call peripheral hardware in the business process of the client program, which makes the debugging and verification of the client program very complicated and cumbersome, and it is difficult to verify certain problem points in the business process alone. Summary of the invention

[0004] The object of the present invention is to provide a method, system, device and medium for calling an external device interface based on a business process, thereby solving all or one of the above-mentioned problems existing in the prior art.

[0005] In order to solve the above technical problems, the specific technical solutions of the present invention are as follows: In one aspect, the present invention provides a method for calling an external device interface based on a business process, comprising the following steps: Configuration steps: In the client program of the self-service terminal, a general device processing module is embedded; based on the general device processing module, memory data in the client program is accessed; the general device processing module is used to support external data configuration files; return data rules are defined in the data configuration file and named in combination with the business process; Calling steps: In response to a business process request, an interface service corresponding to the business process is provided based on the client program, the general device processing module and the data configuration file.

[0006] As an improved solution, the interface service corresponding to the business process is provided based on the client program, the general device processing module and the data configuration file, including: When the business process request is a request for obtaining printer status, a business process flag is set by the client program; and a printer status obtaining interface function in the general device processing module is called by the client program to call the general device processing module to execute a corresponding process.

[0007] As an improved solution, calling the general device processing module to execute the corresponding process includes: The general device processing module is called to read the business process flag, and the corresponding external data configuration file is searched in combination with the device name and the interface function name, and the corresponding process is executed according to the external data configuration file.

[0008] As an improved solution, executing the corresponding process according to the external data configuration file includes: The general device processing module is called to load the external data configuration file found, the rules in the external data configuration file are parsed, and the corresponding process is executed according to the parsed rules.

[0009] As an improved solution, the corresponding process is executed according to the parsed rules, including: The definition in the installation rule of the general device processing module is called, first sleeps for 3000ms, and then returns data; then the call count of "Printer_GetPrinterStatus_WorkFlow_A.dat" in the general device processing module is increased by one.

[0010] As an improved solution, the executing the corresponding process according to the parsed rules further includes: When the call count exceeds the number of repetitions of the rule, the next rule in the external data configuration file is used.

[0011] As an improved solution, after executing the corresponding process, the general device processing module returns to the client program, and continues to execute the subsequent code of the business process through the client program.

[0012] On the other hand, the present invention also provides a business process-based peripheral interface calling system, comprising: The configuration module is used to: embed a general device processing module in the client program of the self-service terminal; access the memory data in the client program based on the general device processing module; use the general device processing module to support external data configuration files; define return data rules in the data configuration file and name them in combination with the business process; The calling module is used to: respond to a business process request and provide an interface service corresponding to the business process based on the client program, the general device processing module and the data configuration file.

[0013] On the other hand, the present invention further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the business process-based peripheral interface calling method are implemented.

[0014] On the other hand, the present invention further provides a computer device, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; wherein: The memory is used to store computer programs; The processor is used to execute the steps of the business process-based peripheral interface calling method by running the program stored in the memory.

[0015] The beneficial effects of the technical solution of the present invention are: 1. The business process-based peripheral interface calling method described in the present invention can make the client program debugging and verification business process on the self-service terminal simpler and faster, solve the problem of business process coupling with peripheral hardware, improve the development efficiency of the client program, reduce the development cost of the client program, make up for the defects of the existing technology, and have a high application value.

[0016] 2. The business process-based peripheral interface calling system described in the present invention can realize the business process-based peripheral interface calling method described in the present invention through the mutual cooperation of system modules.

[0017] 3. The computer-readable storage medium described in the present invention can realize the cooperation of the guiding system module, and then realize the peripheral interface calling method based on business process described in the present invention, and the computer-readable storage medium described in the present invention also effectively improves the operability of the peripheral interface calling method based on business process.

[0018] 4. The computer device described in the present invention can store and execute the computer-readable storage medium, thereby realizing the business process-based peripheral interface calling method described in the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0020] Figure 1It is a flowchart of the business process-based peripheral interface calling method described in Example 1 of the present invention; Figure 2 It is a schematic diagram of the logical architecture of the business process-based peripheral interface calling method described in Example 1 of the present invention; Figure 3 It is a schematic diagram of the architecture of the business process-based peripheral interface calling system according to Embodiment 2 of the present invention; Figure 4 is a schematic diagram of the structure of the computer device described in Example 4 of the present invention; The symbols in the accompanying drawings are explained as follows: 1501, processor; 1502, communication interface; 1503, memory; 1504, communication bus. DETAILED DESCRIPTION

[0021] The preferred embodiments of the present invention are described in detail below in conjunction with the accompanying drawings so that the advantages and features of the present invention can be more easily understood by those skilled in the art, thereby making a clearer and more definite definition of the protection scope of the present invention.

[0022] In the description of the present invention, it should be noted that the embodiments described in the present invention are only part of the embodiments of the present invention, rather than all of the embodiments; based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present invention.

[0023] The terms "first", "second", etc. in the specification and claims of this article and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of this article described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment. Example 1

[0024] This embodiment provides a method for calling an external device interface based on a business process, such as Figure 1 and Figure 2 As shown, the following steps are included: The core function of this method is to embed a general device processing module in the client program of the self-service terminal, encapsulate all interface functions of the peripheral hardware through this module, and return response data according to the business process tag and external data configuration file defined by the client program, thereby realizing the peripheral interface simulation calling scheme combined with the business process, overcoming the difficulty of debugging and verification work caused by the client program calling the peripheral hardware, as follows: S100, configuration steps, including: In the client program of the self-service terminal, a general device processing module is embedded; Among them, the general device processing module is embedded into the client program through source code integration, and exists together with the client program after being compiled by the compiler. Therefore, the general device processing module can access any memory data in the client program; the general device processing module supports external data configuration files, which define the rules for returning data and are named in combination with business processes; It should be noted that the client program runs on the self-service terminal device, displays the main operation interface, and waits for user operation; S200, calling step, including: In response to the request to obtain the printer status, the complete calling process is as follows: 1. The client program sets the business process flag: for example, set it to "WorkFlow_A"; 2. The client program calls the interface function for obtaining the printer status in the general device processing module: For example, if "GetPrinterStatus" is called, the execution flow enters the general device processing module; 3. The general device processing module reads the business process flag, combines the device name and interface function name, and searches for the corresponding external data configuration file, such as "Printer_GetPrinterStatus_WorkFlow_A.dat"; 4. The general device processing module loads the external data configuration file found and parses the rules in the data configuration file; the content of the data configuration file is such as: "0|312000|3000|9999|", and the meaning of the rule described by its content is "rule header|return value|sleep time before return in ms|number of repetitions|"; 5. The installation rule of the general device processing module defines that it sleeps for 3000ms first and then returns the data "312000". Then, the call count of "Printer_GetPrinterStatus_WorkFlow_A.dat" in the general device processing module is increased by 1. When the call count exceeds the repetition count of this rule, 9999, the next rule in the data configuration file is used. 6. The execution process returns to the client program, and the client program continues to execute the subsequent code of the business process.

[0025] It should be noted that the above examples are only for explaining the present invention and cannot limit the protection scope of the present invention. Example 2

[0026] This embodiment is based on the same inventive concept as the method for calling an external device interface based on a business process described in Embodiment 1, and provides a system for calling an external device interface based on a business process, such as Figure 3 As shown, including: The configuration module is used to: embed a general device processing module in the client program of the self-service terminal; access the memory data in the client program based on the general device processing module; use the general device processing module to support external data configuration files; define return data rules in the data configuration file and name them in combination with the business process; The calling module is used to: respond to a business process request and provide an interface service corresponding to the business process based on the client program, the general device processing module and the data configuration file. Example 3

[0027] This embodiment provides a computer-readable storage medium, including: The storage medium is used to store computer software instructions used to implement the business process-based peripheral interface calling method described in the above-mentioned Example 1, which includes a program for executing the above-mentioned program set for the business process-based peripheral interface calling method; specifically, the executable program can be built into the business process-based peripheral interface calling system described in Example 2, so that the business process-based peripheral interface calling system can implement the business process-based peripheral interface calling method described in Example 1 by executing the built-in executable program.

[0028] In addition, the computer-readable storage medium of this embodiment may adopt any combination of one or more computer-readable storage media, wherein the computer-readable storage medium includes electrical, optical, electromagnetic, infrared or semiconductor systems, devices or components, or any combination thereof. Example 4

[0029] This embodiment provides an electronic device, such as Figure 4 As shown, the electronic device may include: a processor 1501 , a communication interface 1502 , a memory 1503 and a communication bus 1504 , wherein the processor 1501 , the communication interface 1502 , and the memory 1503 communicate with each other via the communication bus 1504 .

[0030] Memory 1503, used for storing computer programs; The processor 1501 is used to implement the steps of the business process-based peripheral interface calling method described in the above-mentioned embodiment 1 when executing the computer program stored in the memory 1503.

[0031] As an embodiment of the present invention, the communication bus mentioned in the above terminal can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0032] As an implementation mode of the present invention, the communication interface is used for communication between the above-mentioned terminal and other devices.

[0033] As an embodiment of the present invention, the memory may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0034] As an embodiment of the present invention, the above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0035] Different from the existing technology, the present application adopts a business process-based peripheral interface calling method, system, device and medium, which can make the client program debugging and verification business process on the self-service terminal simpler and faster, solve the problem of business process coupling with peripheral hardware, improve the development efficiency of client programs, reduce the development cost of client programs, make up for the defects of the existing technology, and have high application value.

[0036] It should be understood that in the various embodiments of this document, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this document.

[0037] It should also be understood that in the embodiments of this article, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0038] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this article.

[0039] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0040] In the several embodiments provided herein, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.

[0041] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of this article.

[0042] In addition, each functional unit in each embodiment of this invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of software functional unit.

[0043] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this article is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of this article. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0044] The above descriptions are merely embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A peripheral interface calling method based on business process, characterized in that: The following steps are involved: Configuration steps: In the client program of the self-service terminal, a general device processing module is embedded; based on the general device processing module, memory data in the client program is accessed; the general device processing module is used to support external data configuration files; return data rules are defined in the data configuration file and named in combination with the business process; Calling steps: In response to a business process request, an interface service corresponding to the business process is provided based on the client program, the general device processing module and the data configuration file.

2. The method for calling an external device interface based on a business process according to claim 1, characterized in that: The providing of an interface service corresponding to the business process based on the client program, the general device processing module and the data configuration file includes: When the business process request is a request for obtaining printer status, a business process flag is set by the client program; and a printer status obtaining interface function in the general device processing module is called by the client program to call the general device processing module to execute a corresponding process.

3. The method for calling an external device interface based on a business process according to claim 2, characterized in that: The calling of the general device processing module to execute the corresponding process includes: The general device processing module is called to read the business process flag, and the corresponding external data configuration file is searched in combination with the device name and the interface function name, and the corresponding process is executed according to the external data configuration file.

4. The method for calling an external device interface based on a business process according to claim 3, characterized in that: The executing a corresponding process according to the external data configuration file includes: The general device processing module is called to load the external data configuration file found, the rules in the external data configuration file are parsed, and the corresponding process is executed according to the parsed rules.

5. The method for calling an external device interface based on a business process according to claim 4, characterized in that: The corresponding process is executed according to the parsed rules, including: The definition in the installation rule of the general device processing module is called, first sleeps for 3000ms, and then returns data; then the call count of "Printer_GetPrinterStatus_WorkFlow_A.dat" in the general device processing module is increased by one.

6. The method for calling an external device interface based on a business process according to claim 5, characterized in that: The executing of the corresponding process according to the parsed rules also includes: When the call count exceeds the number of repetitions of the rule, the next rule in the external data configuration file is used.

7. The method for calling an external device interface based on a business process according to claim 6, characterized in that: After executing the corresponding process, the general device processing module returns to the client program and continues to execute the subsequent code of the business process through the client program.

8. A peripheral interface calling system based on business process, characterized in that: include: The configuration module is used to: embed the general device processing module in the client program of the self-service terminal; Access the memory data in the client program based on the general device processing module; use the general device processing module to support external data configuration files; define return data rules in the data configuration file and name them in combination with the business process; The calling module is used to: respond to a business process request and provide an interface service corresponding to the business process based on the client program, the general device processing module and the data configuration file.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, the steps of the business process-based peripheral interface calling method described in any one of claims 1 to 7 are implemented.

10. A computer device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; wherein: The memory is used to store computer programs; The processor is used to execute the steps of the business process-based peripheral interface calling method according to any one of claims 1 to 7 by running the program stored in the memory.

Images