KR102012396B1 - An automatic teller machine - Google Patents

Abstract

The present invention provides an AP file, an MW file and an SP file, a communication module for receiving a hash value table, and a hash value table for each of the AP file, the MW file, and the SP file. Generates an authentication result that authenticates the failure, and if it is confirmed that at least one of the XFS module and the authentication result, the AP file, the MW file, and the SP file is a failure authentication to the set mobile terminal, Provided is a financial automation device for controlling the communication module so that failure occurrence information is transmitted.

Description

Financial automated machine {An automatic teller machine}

The present invention relates to a financial automation device, and more particularly, to a financial automation device that is easy to prevent execution of an illegal application program (Malware) that targets a vulnerability of an XFS system.

The financial automation device includes a plurality of devices such as a keypad device, a customer service device, a card reader device, a media recognition device, and the like, and an appropriate device may be adopted to perform a requested financial transaction according to the type and task of the financial automation device. .

XFS-based financial automation devices may be provided with the CEN / XFS standard, which defines instructions for driving devices.

The CEN / XFS standard defines a user interface to provide consistent control over the operation of devices.

The XFS-based financial automation device includes an application for operation, a service provider provided for controlling the operation of devices, and an XFS manager connecting the application and the service provider. It may include.

Meanwhile, even if the device being used is changed to a device of another manufacturer, the XFS-based financial automation device can immediately use the changed device without additionally developing or changing an application according to the firmware of the changed device.

In other words, the XFS-based financial automation device independently controls a plurality of devices using XFS commands without using respective firmware commands provided by a vendor for each device for a plurality of devices.

Recently, since XFS-based allows multiple applications to run, Malware can communicate with sub-modules in addition to the main application, and Malware can impersonate a sub-application and attempt to withdraw sub-programs for illegal withdrawal. Research is underway to prevent accidents.

An object of the present invention is to provide a financial automation device that is easy to prevent the execution of illegal application program (Malware) to exploit the vulnerability of the XFS system.

The financial automation device according to the present invention includes an AP file, an MW file and an SP file, and a communication module for receiving a hash value table based on the hash value table. If it is determined that at least one of the XFS module and the authentication result, the AP file, the MW file, and the SP file that drive a plurality of devices is generated, the authentication result is authenticated whether or not each SP file is verified. The control module may control the communication module to transmit the failure occurrence information to the set mobile terminal.

The XFS module may be configured to authenticate an AP file for failure, generate a drive command for driving a plurality of devices, authenticate an MW file for failure, and execute the drive command generated by the application. It may include a service provider for authenticating the failure of the middleware and the SP file received, and for driving a plurality of devices in accordance with the driving command delivered from the middleware.

The XFS module may further include an XFS manager which transmits the authentication result to the middleware and delivers the driving command to the service provider.

When the application is initially started, the AP file hash value included in the hash value table is compared with the set AP hash value, and if the AP hash value and the AP file hash value are the same as each other, the AP file may be normally authenticated. Can be.

If the AP hash value and the AP file hash value are not equal to each other, the application may fail-authenticate the AP file and transmit the failure occurrence information to the control module.

The application may extract a hash value included in the AP file and extract the AP file hash value corresponding to the hash value from the hash value table.

When the middleware normally authenticates the AP file in the application, the set MW hash value is compared with the MW file hash value included in the hash table, and when the MW hash value and the MW file hash value are the same, The MW file can be authenticated normally.

If the MW hash value and the MW file hash value are not equal to each other, the middleware may fail-certify the MW file and transmit the control module to transmit the failure occurrence information.

The middleware may extract a hash value included in the MW file, and extract the MW file hash value corresponding to the hash value from the hash value table.

When the service provider normally authenticates the MW file in the middleware, the service provider compares the set SP hash value with the SP file hash value included in the hash table, and if the SP file value and the SP file hash value are the same, The SP file can be normally authenticated.

If the SP hash value and the SP file hash value are not equal to each other, the service provider may fail-authenticate the SP file and transmit the failure occurrence information to the control module.

When the AP file, the MW file, and the SF file are all normally authenticated, the application may control the communication module to transmit an AP hash value set for AP authentication to initiate a petroleum transaction to a work server.

The application may perform a financial transaction when country start information is transmitted from the business server through the communication module.

The financial automation device according to the present invention is based on the AP file, the MW file and the SP file, and the hash value table received from the XFS module, and determines whether the AP file, the MW file, and the SP file are faulty, that is, an illegal application program (Malware). Self-certification has the advantage of preventing accidents in financial transactions.

When the financial automation device according to the present invention authenticates itself with at least one failure of an AP file, an MW file, and an SP file, that is, an illegal application program (Malware), the mobile terminal, that is, a bank-related system configured with failure occurrence information; By transmitting to a maintenance company or the like, there is an advantage that can increase the convenience of the customer.

1 is a control block diagram showing a control configuration of a financial automation device according to the present invention.
2 is an operation diagram illustrating an operation of the application illustrated in FIG. 1.
3 is an operation diagram illustrating an operation of the middleware shown in FIG. 1.
4 is an operation diagram illustrating an operation of the service provider shown in FIG. 1.

Hereinafter, some embodiments of the present invention will be described in detail with reference to the accompanying drawings. In adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are assigned to the same components as much as possible even though they are shown in different drawings. In addition, in describing the embodiments of the present invention, when it is determined that a detailed description of a related well-known configuration or function interferes with the understanding of the embodiments of the present invention, the detailed description thereof will be omitted.

In addition, in describing the components of the embodiment of the present invention, terms such as first, second, A, B, (a), and (b) may be used. These terms are only for distinguishing the components from other components, and the nature, order or order of the components are not limited by the terms. If a component is described as being "connected", "coupled" or "connected" to another component, that component may be directly connected or connected to that other component, but between components It will be understood that may be "connected", "coupled" or "connected".

The financial device according to an embodiment of the present invention, for example, obtains various media such as banknotes, securities (including checks), giro, coins, gift certificates, and the like, and processes such as deposit processing, giro storage, gift certificate exchange, and / or withdrawal processing. It is a device that performs financial operations such as media processing, such as processing, releasing to the market, and releasing gift certificates. Examples of such a financial device may be an ATM (Automated Teller Machine) such as a cash dispenser (CD), a cash recycling device (Cash Recycling Device). However, the financial device is not limited to the above-described example, and may be various devices for automating financial tasks such as a financial information system (FIS).

Hereinafter, embodiments of the present invention will be described. However, these assumptions are merely for convenience of explanation, and the technical concept of the present invention is not limited to the automatic teller machine.

1 is a control block diagram showing a control configuration of a financial automation device according to the present invention, FIG. 2 is an operation diagram showing the operation of the application shown in FIG. 1, FIG. 3 is an operation diagram and operation diagram showing the operation of the middleware shown in FIG. 4 is an operation diagram showing the operation of the service provider shown in FIG.

1 to 4, the financial automation device 100 may include a communication module 110, an XFS module 120, and a control module 130.

In an embodiment, the XFS module 120 is described as having a different configuration as the control module 130, but may be formed integrally with the control module 130, but is not limited thereto.

The communication module 110 may receive an AP file, an MW file and an SP file, and a hash value table H_T transmitted from the file server 112.

In addition, the communication module 110 may transmit fault recognition information a transmitted from at least one of the XFS module 120 and the control module 130 to the set mobile terminal 114.

The XFS module 120 may include an applicator 122, middleware 124, an XFS manager 126, and a service provider 128.

The application 122 may refer to a financial transaction application that allows a financial transaction to proceed by driving a plurality of devices included in the financial automation device 100.

When the application 122 is initially started, the application 122 may self-authenticate whether or not the AP file is received by the communication module 110.

Here, referring to FIG. 2, the application 122 may operate as follows.

First, the application 122 compares the set AP hash value AP H_V with the AP file hash value AP file H_V included in the hash value table H_T at the first startup, and compares the AP hash value AP H_V and the AP hash value AP H_V. It is possible to authenticate whether the AP file hash values (AP file H_V) are normal or not.

That is, the application 122 extracts the hash value included in the AP file, extracts the AP file hash value AP file H_V corresponding to the hash value from the hash value table H_T, and then accesses the AP hash. The normality may be authenticated depending on whether the value AP H_V and the AP file hash value AP file H_V are the same.

Thereafter, the application 122 normally authenticates the AP file if the AP hash value AP H_V and the AP file hash value AP file H_V are the same, and instructs the middleware 124 to authenticate itself. I can deliver it.

In addition, when the AP hash value AP H_V and the AP file hash value AP file H_V are not equal to each other, the application 122 may fail-authenticate the AP file and fail information (a) in the control module 130. ) May be transmitted to the control module 130 to be transmitted to the mobile terminal 114.

3, the middleware 124 may operate as follows.

The middleware 124 may authenticate the failure of the MW file and receive the driving command generated by the application and transmit the received driving command to the XFS manager 126.

Here, when the middleware 124 normally authenticates the AP file in the application 122, the MW file hash value MW file H_V included in the set MW hash value MW H_V and the hash value table H_T. ), It is possible to authenticate whether the MW hash value MW H_V and the MW file hash value MW file H_V are the same.

That is, the middleware 124 extracts the hash value included in the MW file (MW file), extracts the MW file hash value (MW file H_V) corresponding to the hash value from the hash value table H_T, and then MW. It is possible to authenticate whether the hash value AP H_V and the MW file hash value AP file H_V are equal to each other.

Thereafter, the middleware 124 normally authenticates the MW file (MW file) when the MW hash value (MW H_V) and the MW file hash value (MW file H_V) are the same, and provides a service provider through the XFS manager 126. At 128, the command can be passed to authenticate itself.

In addition, if the MW hash value (MW H_V) and the AP file hash value (MW file H_V) are not the same, the middleware 124 may fail-authenticate the MW file (MW file) and generate information on the occurrence of failure in the control module 130 ( The authentication result may be transmitted to the control module 130 such that a) is transmitted to the mobile terminal 114.

The XFS manager 126 may deliver the service provider 128 to operate the actual financial device 10 according to the command from the middleware 124.

In addition, the XFS manager 126 may forward the response from the service provider 128 to the middleware 124 to be delivered to the application 122.

Here, referring to FIG. 4, the service provider 128 may operate as follows.

When the service provider 128 normally authenticates the MW file in the middleware 124, the service provider 128 compares the set SP hash value SF H_V with the SP file hash value SF file H_V included in the hash table HT. If the SP hash value (SF H_V) and the SP file hash value (SF file H_V) are the same, the SP file (SF file) can be normally authenticated.

Thereafter, the service provider 128 may normally authenticate the SP file if the SP hash value SP H_V and the SP file hash value SP file H_V are the same.

In addition, if the SP hash value (SP H_V) and the SP file hash value (SP file H_V) are not equal to each other, the service provider 128 may fail-authenticate the SP file and fail information in the control module 130. The authentication result may be transmitted to the control module 130 such that (a) is transmitted to the mobile terminal 114.

If a failure authentication is transmitted from at least one of the application 122, the middleware 124, and the service provider 128 according to the authentication result of the XFS module 120, the control module 130, the failure occurrence information (a) Control the communication module 110 to be transmitted to the business server.

In the above description, it is described that all the components constituting the embodiments of the present invention are combined or operated in one, but the present invention is not necessarily limited to these embodiments. In other words, within the scope of the present invention, all of the components may be selectively operated in combination with one or more. In addition, the terms "comprise", "comprise" or "having" described above mean that the corresponding component may be inherent unless specifically stated otherwise, and thus excludes other components. It should be construed that it may further include other components instead. All terms, including technical and scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. Terms used generally, such as terms defined in a dictionary, should be interpreted to coincide with the contextual meaning of the related art, and shall not be interpreted in an ideal or excessively formal sense unless explicitly defined in the present invention.

The above description is merely illustrative of the technical idea of the present invention, and those skilled in the art to which the present invention pertains may make various modifications and changes without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention but to describe the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the equivalent scope should be interpreted as being included in the scope of the present invention.

Claims (13)

A communication module for receiving the AP file, the MW file and the SP file, and the hash value table transmitted from the file server;
An XFS module configured to generate an authentication result of authenticating failure of each of the AP file, the MW file, and the SP file based on the hash value table, and to drive a plurality of devices; And
And a control module for controlling the communication module to transmit failure occurrence information to the set mobile terminal when it is confirmed that at least one of the AP file, the MW file, and the SP file is failure authentication.
The XFS module,
An application for authenticating a failure of the AP file and generating a driving command for driving a plurality of devices;
Middleware for authenticating a failure of the MW file and receiving the driving command generated by the application; And
And a service provider for authenticating a failure of the SP file and driving a plurality of devices according to the driving command transmitted from the middleware. delete The method of claim 1,
The XFS module,
And an XFS manager which transmits the authentication result of the service provider to the middleware and delivers the driving command to the service provider. The method of claim 1,
The application,
And, at the first startup, compare the set AP hash value with the AP file hash value included in the hash value table, and if the AP hash value and the AP file hash value are equal to each other, normalize the AP file. The method of claim 4, wherein
The application,
And if the AP hash value and the AP file hash value are not equal to each other, verify the failure of the AP file, and transmit the failure occurrence information to the control module. The method of claim 1,
The application,
And extracting a hash value included in the AP file and extracting the AP file hash value corresponding to the hash value from the hash value table. The method of claim 3, wherein
The middleware,
When the AP file is normally authenticated in the application, the MW hash value included in the hash value table is compared with the set MW hash value. When the MW hash value and the MW file hash value are the same, the MW file is determined. Normally certified financial automation devices. The method of claim 7, wherein
The middleware,
And if the MW hash value and the MW file hash value are not equal to each other, fail authentication of the MW file, and deliver the control module to transmit the failure occurrence information. The method of claim 7, wherein
The middleware,
And extracting a hash value included in the MW file and extracting the MW file hash value corresponding to the hash value from the hash value table. The method of claim 7, wherein
The service provider,
If the MW file is normally authenticated by the middleware, the SP file hash value and the SP file hash value included in the hash value table are compared. If the SP hash value and the SP file hash value are the same, the SP file is determined. Normally certified financial automation devices. The method of claim 10,
The service provider,
And if the SP hash value and the SP file hash value are not equal to each other, verify the failure of the SP file and transmit the failure occurrence information to the control module. The method of claim 1,
The application,
And if the AP file, the MW file, and the SP file are all normally authenticated, controlling the communication module to transmit an AP hash value set for AP authentication to open a financial transaction to a work server. The method of claim 12,
The application,
And perform financial transactions when country start information is transmitted from the business server through the communication module.

Images