WO2019019864A1

WO2019019864A1 - Communication system, method and apparatus for embedded self-service terminal

Info

Publication number: WO2019019864A1
Application number: PCT/CN2018/093785
Authority: WO
Inventors: 潘煜豪; 熊飞; 黄三朋; 吴胜楠; 林宇龙; 梁建明
Original assignee: 广州广电运通金融电子股份有限公司; 广州广电汇通金融服务有限公司
Priority date: 2017-07-26
Filing date: 2018-06-29
Publication date: 2019-01-31
Also published as: CN107493266B; CN107493266A

Abstract

The present invention relates to a communication system, method and apparatus for an embedded self-service terminal. The communication system comprises: an application layer and a hardware device operation layer. The application layer comprises an interface matching module, a first serialization module and a first communication module. The hardware device operation layer comprises a second communication module, a second serialization module and a core processing module. The interface matching module is used for acquiring an API interface of a target program, and matching the API interface to an SPI interface complying with the hardware device operation layer. The first serialization module is used for parsing memory data into byte stream data. The first communication module and the second communication module are used for transceiving the byte stream data between the application layer and the hardware device operation layer. The second serialization module is used for parsing the byte stream data into the memory data. The core processing module is used for generating, according to the memory data, a corresponding command to drive a hardware device. The present invention can realize cross-platform, cross-system and cross-platform communication control on an embedded self-service terminal.

Description

Communication system, method and device for embedded self-service terminal

Technical field

The present invention relates to the field of self-service terminal technologies, and in particular, to a communication system, method and apparatus for an embedded self-service terminal.

Background technique

With the development of embedded technology, more and more self-service terminals have been developed in embedded mode, such as ATM (Automatic Teller Machine) equipment developed based on embedded mode. However, due to the low configuration of the embedded device, or the operating system of the embedded self-service terminal is not perfect for interface development and is not suitable for the development of a complicated UI (User Interface) program, the device developed by the embedded method is There are widespread problems in post-commissioning and the difficulty of developing upper-layer application software.

Summary of the invention

The embodiment of the invention provides a communication system, method and device for an embedded self-service terminal, which can realize cross-platform, cross-system and cross-platform communication control of the embedded self-service terminal.

An aspect of the present invention provides a communication system for an embedded self-service terminal, including:

The application layer and the hardware device operation layer are included; the application layer includes an interface matching module, a first serialization module, and a first communication module that are sequentially connected; the hardware device operation layer includes a second communication module and a second serialization module that are sequentially connected. And core processing module;

The interface matching module is configured to acquire an API interface of a current target program, and match the API interface to an SPI interface that conforms to an operation layer of the hardware device; the first serialization module is configured to parse the memory data into bytes. Streaming data; the first communication module and the second communication module are configured to implement sending and receiving of byte stream data between the application layer and the operating layer of the hardware device; and the second serialization module is configured to parse the byte stream data The memory processing module is configured to generate a corresponding command according to the received memory data to drive the corresponding hardware device.

Another aspect of the present invention provides a communication method for an embedded self-service terminal, including:

Establish a network connection between the application layer and the hardware device operation layer;

Obtaining an API interface corresponding to the target program, and matching the API interface to an SPI interface that conforms to an operation layer of the hardware device;

Receiving, by the SPI interface, memory data of the target program, and parsing the memory data into byte stream data, and sending the byte stream data to the hardware device operation layer through the network connection;

The hardware device operation layer parses the received byte stream data into memory data, and generates a corresponding command according to the obtained memory data to drive the corresponding hardware device.

Another aspect of the present invention provides a communication device for an embedded self-service terminal, including:

a communication connection unit, configured to establish a network connection of an application layer and a hardware device operation layer;

An interface matching unit, configured to acquire an API interface corresponding to the target program, and match the API interface to an SPI interface that conforms to an operation layer of the hardware device;

a data parsing and transmitting unit, configured to receive the memory data of the target program through the SPI interface, parse the memory data into byte stream data, and send the byte stream data to the hardware device through the network connection Operation layer

The data receiving and processing unit is configured to: the operating layer of the hardware device parses the received byte stream data into memory data, and generates a corresponding command according to the obtained memory data to drive the corresponding hardware device.

The communication system, method, and device for the embedded self-service terminal provided by the foregoing embodiment, the application layer includes an interface matching module, a first serialization module, and a first communication module that are sequentially connected; the operating layer of the hardware device includes a serial connection a communication module, a second serialization module, and a core processing module; capable of matching an API interface of the current target program to an SPI interface conforming to an operation layer of the hardware device; and further parsing the memory data into byte stream data and transmitting the data to the hardware device The operation layer; the hardware device operation layer restores the byte stream data to the memory data, and then generates a corresponding command according to the received memory data to drive the corresponding hardware device. The application layer and the hardware device operation layer can implement separate cross-host communication control, which overcomes the defect that the traditional hardware device operation layer is limited to the local communication control. In addition, the target program and the hardware device operation layer can run different operating systems, which facilitates compiling and running across operating systems, and reduces the difficulty of post-debugging and application development of the embedded self-service terminal.

DRAWINGS

1 is a schematic diagram of a communication system of an embedded self-service terminal according to an embodiment;

2 is a schematic flowchart of a communication method of an embedded self-service terminal according to an embodiment;

3 is a diagram showing an example of a structure definition of memory data issued by a target program of an embodiment;

4 is a schematic structural diagram of a communication device of an embedded self-service terminal according to an embodiment.

Detailed ways

The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

1 is a schematic diagram of a communication system for implementing an embedded self-service terminal according to an embodiment of the present invention; the communication system of the embedded self-service terminal includes an application layer and a hardware device operation layer. The application layer is used to run a corresponding application, which is also called APP (short for Application Layer), and mainly implements interaction with the user. The hardware device operation layer is a layer that drives a hardware device, and is a manager of a hardware resource, for example, provides operation and status information of a hardware device, and is also called SP (Service Providers), which can provide a SPI (Serial Peripheral Interface). Line Peripheral Interface) Interface. The hardware device operation layer SP can be provided by different vendors.

In this embodiment, the application layer APP includes an interface matching module, a first serialization module, and a first communication module that are sequentially connected; the hardware device operation layer SP includes a second communication module, a second serialization module, and a core processing module that are sequentially connected. . The interface matching module is configured to acquire an API (Application Programming Interface) interface of the current target program, and match the API interface to an SPI interface that conforms to the hardware device operation layer SP; the first serialization module The first communication module and the second communication module are configured to implement sending and receiving of byte stream data between the application layer APP and the hardware device operation layer SP; The second serialization module is configured to parse the byte stream data into the memory data; the core processing module is configured to generate a corresponding command according to the received memory data to drive the corresponding hardware device. For example, the core processing module receives the command sent by the application program through the second communication module, and performs some general processing on the command, such as queuing, canceling, scheduling, and executing the command, and implementing all the devices. General commands and mechanisms, and return results and messages through the second communication module.

The communication system based on the above structure, when the target program running in different operating systems needs to call the API interface to operate the hardware device, only the interface matching module is used for interface conversion, and the interface matching module uses the API interface and the corresponding SPI interface. The mapping is performed, and the data is parsed by the first serialization module, and then the request is sent to the corresponding hardware device operation layer SP, and the operation of the hardware device is implemented by the hardware device operation layer SP. Based on the serialization module and the communication module, the application layer APP and the hardware device operation layer SP can implement separate cross-host communication control, which overcomes the defect that the traditional hardware device operation layer SP is limited to the local communication control. In addition, the conventional hardware device operation layer SP is limited to development and operation only in a single operating system (such as windows), which is inconvenient to expand the migration, and the communication system of the embedded self-service terminal based on the above embodiment, the target program and the hardware device operation layer SP can run different operating systems, which is conducive to compiling and running across operating systems, reducing the difficulty of post-debugging and application development of embedded self-service terminals.

In a preferred embodiment, the interface matching module includes an SPI interface layer and an XFS (Extensions for Financial Services) manager. The SPI interface layer is configured to provide a corresponding SPI interface for the hardware device operation layer SP; the XFS manager is configured to match an API interface corresponding to a target program (eg, a Windows-based application) to an SPI corresponding to the hardware device operation layer SP interface.

Preferably, the SPI interface layer is configured to provide an SPI interface conforming to the CEN/XFS specification, for receiving a command sent by the XFS manager, sending back a return value, completing a message, an event, or receiving a command sent by the XFS manager. , send back the return value, complete the message.

The following is a further explanation for understanding the XFS Manager. WOSA (Windows Open System Architecture) is a software architecture under the Windows operating system. Essentially WOSA is an interface that enables Windows-based desktop applications to connect to multiple computing environments without having to rewrite applications for each platform, allowing Windows-based applications to connect to multiple computing environments without having to be per platform Rewrite the application. XFS is part of WOSA for financial extension services and is a software architecture for the financial industry. XFS is also a set of C-based WIN32API, so it is convenient for both application developers and service providers. The driver interface for various financial peripherals is defined by XFS. Applications using this interface can run on any financial device that provides an interface that conforms to this specification, regardless of vendor. Therefore, based on the interface matching module, separation of the application layer APP and the hardware device operation layer SP can be implemented. The elements of the CEN/XFS standard are the API and corresponding SPI definitions, which allow XFS Mananger to communicate with the hardware device operating layer SP and a series of support for the hardware device operating layer SP. In the XFS implementation, these elements are combined to provide access to financial peripherals for Windows-based applications. A standard set of interfaces defined in the CEN/XFS standard enables interoperability of multi-vendor devices. If an application API successfully communicates with the hardware device operating layer SP, it can run on different types of hardware of the same type. The device operating layer SP (which may be developed by another vendor) does not require any changes; similarly, the hardware device operating layer SP built using SPI can work with a range of different structured applications.

In a preferred embodiment, the application layer and the hardware device operating layer communicate over a TCP/IP network. The first communication module and the second communication module implement socket data transmission and reception by using a socket method. To achieve cross-host physical communication control.

Generally, data transmitted in the same host is in-memory data (for example, pointer data), and contains storage information of data types and data. For example, the structure definition of the memory data emitted by the target program is shown in Figure 3. In the case of a cross-host scenario, the memory data of the first application layer needs to be specially processed and sent to the receiving end (in this embodiment, the hardware device operation layer). SP), and the receiving end must allocate memory according to the received data and return the allocated memory address information to the core processing module. This is equivalent to local communication from the perspective of the core processing module, thereby reducing the coupling of data processing. Preferably, in order to implement cross-host communication control, the first serialization module and the second serialization module may perform data parsing according to a standard xml format to implement data copy operations across hosts, systems, and platforms. XML (eXtensible Markup Language) can be used to extend the markup language. Like HTML, it is SGML (Standard Generalized Markup Language). XML is a cross-platform, content-dependent technology in the Internet environment that is a powerful tool for processing structured document information. XML is a simple data storage language that uses a series of simple tags to describe data, and these tags can be built in a convenient way, so XML is extremely simple and easy to grasp and use. The simplicity of XML makes it easy to read and write data in any application, making XML the only common language for data exchange, and different applications basically support XML. In this embodiment, this means that the hardware device operation layer SP layer can be more easily combined with information generated under Windows, Mac OS, Linux, and other platforms, and then the XML data can be easily loaded into the program and analyzed, and The output is in XML format.

Based on the first serialization module and the first communication module, the second communication module, and the second serialization module, the application layer APP and the hardware device operation layer SP can be run in different operating systems, so that the switch can be more flexibly switched. The application layer APP or the hardware device operates the layer SP without affecting the traffic of a certain part thereof. For example, the application layer APP can be run on the Windows operating system host, and the hardware device operation layer SP can be run on the Linux operating system host; of course, the application layer APP and the hardware device operation layer SP can also exist in the same Windows operating system host at the same time.

With reference to FIG. 1 and the above description of the communication system of the embedded self-service terminal, an embodiment of the communication method of the embedded self-service terminal will be described below.

2 is a schematic flowchart of a communication method of an embedded self-service terminal according to an embodiment; as shown in FIG. 2, the communication method of the embedded self-service terminal in this embodiment includes the following steps:

S11. Establish a network connection between the application layer and the operation layer of the hardware device.

In this implementation, the application layer and the hardware device operation layer may be respectively located on different hosts, and establish a TCP/IP connection between the application layer and the hardware device operation layer.

S12. Acquire an API interface corresponding to the current target program, and match the API interface to an SPI interface that conforms to an operation layer of the hardware device.

In a preferred embodiment, the matching of the API interface to the SPI interface of the hardware device operating layer is implemented by the XFS manager and the preset SPI interface layer. The SPI interface layer is configured to provide an SPI interface conforming to the CEN/XFS specification, and is configured to receive a command sent by the XFS manager, send back a return value, complete a message, an event, or receive a command sent by the XFS manager, and send back the command. Return value, completion message.

S13. Receive, by the SPI interface, memory data of the target program, and parse the memory data into byte stream data, and send the byte stream data to the hardware device operation layer through the network connection.

In a preferred embodiment, the byte stream data may be sent to the hardware device operation layer in a socket manner. So-called sockets are often referred to as "sockets", and applications typically make requests to the network or respond to network requests via "sockets." Socket is used when establishing a network connection. When the connection is successful, both ends of the application will generate a Socket instance, operate the instance, and complete the required session. For a network connection, the sockets are equal and there is no difference, not because of the different levels on the server side or on the client side.

In a preferred embodiment, the connection process between the application layer and the socket of the hardware device operation layer can be divided into three steps: server listening, client request, and connection confirmation. The application layer can serve as a client, and the hardware device operation layer can serve as a server.

Server snooping: The server-side socket does not locate a specific client socket, but is in a state of waiting for a connection to monitor the network status in real time. Client request: refers to the client's socket to make a connection request, the target to be connected is the server-side socket. To do this, the client's socket must first describe the socket of the server it is connecting to, indicate the server-side socket's address and port number, and then make a connection request to the server-side socket. Connection confirmation: When the server-side socket listens to or receives a connection request from the client socket, it responds to the client socket request, creates a new thread, and puts the server-side socket. The description is sent to the client, and once the client confirms the description, the connection is established. The server-side socket continues to be listening and continues to receive connection requests from other client sockets.

In a preferred embodiment, the manner in which the memory data is parsed into byte stream data in this step may be: parsing the memory data into byte stream data according to a standard xml format.

Assume that the structure definition of the memory data issued by the target program is as shown in Figure 3. The data structure is an xml format data, where: GrgSpSerialConfig is the name of the data structure, which is defined for each command; each command includes a command The ID, the length of the command parameter, the type of the command parameter, and the start position of the command. If there are multiple parameters, they can be represented by Block0, Block1, and so on. The specific manner of parsing the memory data into byte stream data may be: firstly, searching for an xml node according to the command ID number, and then acquiring the length of the data and the position of the pointer according to the xml node, and correspondingly according to the type of the pointer The data is combined into a network data stream.

S14. The hardware device operation layer parses the received byte stream data into the memory data, and generates a corresponding command according to the obtained memory data to drive the corresponding hardware device.

In a preferred embodiment, the received byte stream data is parsed into the in-memory data by parsing the received byte stream data into memory data according to a standard xml format. Specifically, the byte stream data of the specified command ID is restored to the memory data, that is, the xml node is first searched according to the command ID number, and then the length of the data is obtained according to the xml node, and the memory is allocated according to the position and type of the pointer. And returning the pointer of the memory to form a return result structure; that is, converting a stream of bytes into data of the xml structure as shown in FIG.

Through steps S13 and S14, data copy operations across hosts, systems, and platforms can be implemented.

Through the communication method of the embedded self-service terminal in the above embodiment, the separate cross-host, cross-system and cross-platform communication control is performed through the socket, thereby realizing the separation of the application layer and the operation layer of the hardware device, and also solving the application layer and the hardware. The device operation layer can be run in different operating systems, so that the application layer or hardware device operation layer can be switched more flexibly without affecting the traffic of a certain part of it. For example, according to the above framework structure, the application layer can be run on the Windows operating system host, and the hardware device operation layer runs on the Linux operating system host; or, for example, the application layer and the hardware device operation layer exist simultaneously on the same Windows operating system host.

It should be noted that, for the foregoing method embodiments, for the sake of brevity, they are all described as a series of action combinations, but those skilled in the art should understand that the present invention is not limited by the described action sequence, because In accordance with the present invention, certain steps may be performed in other sequences or concurrently. Further, any combination of the above embodiments can be made, and other embodiments can be obtained.

Based on the same idea as the embedded self-service terminal communication method in the above embodiment, the present invention also provides a communication device for an embedded self-service terminal, which can be used to execute the communication method of the embedded self-service terminal. For the convenience of the description, in the structural diagram of the embodiment of the communication device of the embedded self-service terminal, only the parts related to the embodiment of the present invention are shown. Those skilled in the art can understand that the illustrated structure does not constitute a limitation on the device, and Includes more or fewer components than shown, or combines some components, or different component arrangements.

4 is a schematic structural diagram of a communication device of an embedded self-service terminal according to an embodiment of the present invention; as shown in FIG. 4, the communication device of the embedded self-service terminal of the present embodiment includes: a communication connection unit 310 and an interface matching unit 320. The data analysis and transmission unit 330 and the data reception and processing unit 340. The modules are detailed as follows:

The communication connection unit 310 is configured to establish a network connection between an application layer and a hardware device operation layer;

The interface matching unit 320 is configured to acquire an API interface corresponding to the target program, and match the API interface to an SPI interface that conforms to an operation layer of the hardware device;

a data parsing and transmitting unit 330, configured to receive, by using the SPI interface, memory data of a target program, and parse the memory data into byte stream data, and send the byte stream data to the hardware through the network connection Equipment operation layer

The data receiving and processing unit 340 is configured to: the hardware device operation layer parses the received byte stream data into memory data, and generates a corresponding command according to the obtained memory data to drive the corresponding hardware device.

It should be noted that, in the implementation manner of the communication device of the embedded self-service terminal of the above example, the information exchange, the execution process, and the like between the units are based on the same concept as the foregoing method embodiment of the present invention. The effect is the same as the foregoing method embodiment of the present invention. For details, refer to the description in the method embodiment of the present invention, and details are not described herein again.

In addition, in the implementation manner of the communication device of the embedded self-service terminal of the above example, the logical division of each functional unit is only an example, and the actual application may be considered according to requirements, for example, for the configuration requirements of the corresponding hardware or the convenience of implementation of the software. The above function assignment is performed by different functional units, that is, the internal structure of the communication device of the embedded self-service terminal is divided into different functional modules to complete all or part of the functions described above. Each functional unit can be implemented in the form of hardware or in the form of a software functional unit.

It will be understood by those skilled in the art that all or part of the processes in the above embodiments may be implemented by a computer program to instruct related hardware, and the program may be stored in a computer readable storage medium as Independent product sales or use. The program, when executed, may perform all or part of the steps of an embodiment of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

In the above embodiments, the descriptions of the various embodiments are all focused, and the parts that are not detailed in a certain embodiment can be referred to the related descriptions of other embodiments.

The above-described embodiments are merely illustrative of several embodiments of the invention and are not to be construed as limiting the scope of the invention. It should be noted that a number of variations and modifications may be made by those skilled in the art without departing from the spirit and scope of the invention. Therefore, the scope of the invention should be determined by the appended claims.

Claims

An embedded self-service terminal communication system, comprising: an application layer and a hardware device operation layer; the application layer comprises an interface matching module, a first serialization module and a first communication module connected in sequence; the hardware device operation layer The second communication module, the second serialization module and the core processing module are sequentially connected;

The interface matching module is configured to acquire an API interface of the target program, and match the API interface to an SPI interface that conforms to an operation layer of the hardware device; the first serialization module is configured to parse the memory data into a byte stream. The first communication module and the second communication module are configured to implement sending and receiving of byte stream data between the application layer and the hardware device operation layer; and the second serialization module is configured to parse the byte stream data into the memory data. The core processing module is configured to generate a corresponding command according to the received memory data to drive the hardware device.
The embedded self-service terminal communication system according to claim 1, wherein the interface matching module comprises an SPI interface layer and an XFS manager;

The SPI interface layer is configured to provide a corresponding SPI interface for the hardware device operation layer; the XFS manager is configured to match the API interface corresponding to the target program to the SPI interface corresponding to the operation layer of the hardware device.
The communication system of the embedded self-service terminal according to claim 2, wherein the SPI interface layer is configured to provide an SPI interface conforming to the CEN/XFS specification.
The communication system of the embedded self-service terminal according to any one of claims 1 to 3, wherein the first communication module and the second communication module implement byte transceiver data transmission and reception by using a socket method.
The communication system of the embedded self-service terminal according to any one of claims 1 to 3, wherein the first serialization module and the second serialization module perform data analysis according to a standard xml format.
A communication method for an embedded self-service terminal, comprising:

Establish a network connection between the application layer and the hardware device operation layer;

Obtaining an API interface corresponding to the target program, and matching the API interface to an SPI interface that conforms to an operation layer of the hardware device;

Receiving, by the SPI interface, memory data of the target program, and parsing the memory data into byte stream data, and sending the byte stream data to the hardware device operation layer through the network connection;

The hardware device operation layer parses the received byte stream data into memory data, and generates a corresponding command according to the obtained memory data to drive the corresponding hardware device.
The communication method of the embedded self-service terminal according to claim 6, wherein the establishing a network connection between the application layer and the operation layer of the hardware device comprises: establishing a TCP/IP connection of the application layer and the operation layer of the hardware device.
The communication method of the embedded self-service terminal according to claim 7, wherein the sending of the byte stream data to the operation layer of the hardware device by using the network connection comprises:

The byte stream data is sent to the hardware device operation layer in a socket manner through the network connection.
The communication method of the embedded self-service terminal according to claim 6, wherein the parsing the memory data into byte stream data comprises: parsing the memory data into byte stream data according to a standard xml format;

Parsing the received byte stream data into memory data includes: parsing the received byte stream data into memory data according to a standard xml format.
A communication device for an embedded self-service terminal, comprising:

a communication connection unit, configured to establish a network connection of an application layer and a hardware device operation layer;

An interface matching unit, configured to acquire an API interface corresponding to the target program, and match the API interface to an SPI interface that conforms to an operation layer of the hardware device;

a data parsing and transmitting unit, configured to receive the memory data of the target program through the SPI interface, parse the memory data into byte stream data, and send the byte stream data to the hardware device through the network connection Operation layer

And a data receiving and processing unit, configured to: the hardware device operation layer parses the received byte stream data into memory data, and generates a corresponding command according to the obtained memory data to drive the corresponding hardware device.