Currency processing system, currency processing device, program, and method

Abstract

In order to reduce the load on an update server when updating the software of a currency processing device, provided is a currency processing system comprising: a first currency processing device having a first configuration unit that executes processing related to currency processing, and a first storage unit that stores first software for operating the first configuration unit; and a second currency processing device having a second configuration unit that executes processing related to currency processing, and a second storage unit that stores second software for operating the second configuration unit. When the second software is software resulting from updating the first software to a new version, and an update file for updating the first software to the second software can be acquired from the second currency processing device, the first currency processing device acquires the update file from the second currency processing device, and updates the first software to the second software.

Description

Money handling system, money handling device, program and method

[0001] The present disclosure relates to a currency processing system, a currency processing device, a program, and a method.

[0002] Conventionally, currency handling devices that perform currency deposit and withdrawal processes have been used in various locations. A control unit of the currency handling device executes pre-prepared software to control the components of the currency handling device, thereby realizing currency handling. The software of the currency handling device is updated as necessary. For example, Patent Document 1 discloses a system in which a server device distributes and updates programs and definition files to multiple ATMs (automated teller machines). The server device creates an update schedule based on the operating status of the ATMs, and distributes the programs and definition files to each ATM in accordance with the created update schedule. The ATMs update their programs and definition files using the programs and definition files distributed from the server device.

[0003] JP 2016-151878 A

[0004] However, with the above-mentioned conventional technology, as the number of currency processing devices to which update files are distributed increases, the load on the server device increases. For example, while it is possible to reduce the amount of communication per day by adjusting the distribution schedule for each currency processing device, the overall amount of data distributed from the server device remains unchanged, placing a load on the server device and the network.

[0005] The present disclosure has been made in consideration of the problems associated with the above-mentioned conventional technology, and one of its objectives is to provide a currency processing system, currency processing device, program, and method that can reduce the load on the update server when updating the software of a currency processing device.

[0006] The currency handling system of the present disclosure includes a first currency handling device having a first component unit that executes processing related to currency handling and a first memory unit that stores first software that operates the first component unit, and a second currency handling device having a second component unit that executes processing related to currency handling and a second memory unit that stores second software that operates the second component unit, and if the second software is software that updates the first software to a new version and an update file that updates the first software to the second software can be obtained from the second currency handling device, the first currency handling device obtains the update file from the second currency handling device and updates the first software to the second software.

[0007] The above configuration may further include a server that stores the update file. The server may manage software versions. The server may manage whether the second software is the latest version of the first software. The first currency processing device may determine whether the update file is available from the second currency processing device, and if the update file is available from the second currency processing device, acquire the update file from the second currency processing device and update the first software to the second software. The first currency processing device may determine whether the second software is the latest version, and if the second software is the latest version, acquire the update file from the second currency processing device. If the update file is not available from the second currency processing device, the first currency processing device may acquire the update file from the server and update the first software to the second software. If the second software is not the latest version, the first currency processing device may acquire the update file from the server.

[0008] In the above configuration, the second currency processing device may be connected to a network of a store to which the first currency processing device is connected.

[0009] In the above configuration, the second currency processing device may be installed in a store other than the store in which the first currency processing device is installed, and which is under the management of an organization to which the user of the first currency processing device belongs.

[0010] In the above configuration, the first software may include software for operating a currency recognition unit provided in the first currency processing device.

[0011] In the above configuration, the first software may include software for operating components including at least one of a currency deposit section, a currency withdrawal section, and a storage section provided in the first currency processing device.

[0012] In the above configuration, the first software may include software for operating peripheral devices of the first currency processing device.

[0013] In the above configuration, the first software may include software for operating a board possessed by the first currency processing device.

[0014] In the above configuration, the first currency handling unit and the second currency handling unit may be different types of devices. In the above configuration, the first currency handling unit and the second currency handling unit may be different types of devices, but the first component and the second component may be the same type of component.

[0015] The currency processing device of the present disclosure is a currency processing device that processes currency, and is equipped with a component that executes processes related to currency processing, a memory unit that stores software for controlling the component, a control unit that executes the software to control the component, and a communication unit that sends and receives data with an external device, and the control unit obtains an update file for the software from another currency processing device and updates the software using the update file.

[0016] The program according to the present disclosure is a program executed by a currency processing device that processes currency, and causes the currency processing device to obtain, from another currency processing device, a software update file for operating components of the currency processing device, and to update the software using the update file. The program according to the present disclosure may be recorded on a non-transitory computer-readable medium. The program according to the present disclosure may be provided as a computer program product that is executed by a control unit of the currency processing device to realize each of the above functions.

[0017] The method according to the present disclosure is a method executed by a currency processing device that processes currency, and includes the steps of obtaining, from another currency processing device, an update file for software for operating components of the currency processing device, and updating the software using the update file. The method according to the present disclosure may be realized by a control unit of the currency processing device executing a program recorded on a non-transitory computer-readable medium or a program provided as a computer program product.

[0018] According to the currency processing system, currency processing device, program, and method disclosed herein, the load on the update server can be reduced when updating software such as programs, firmware, data, etc. related to currency processing in a currency processing device.

[0019] FIG. 1 is a diagram illustrating an overview of a currency handling system according to this embodiment. FIG. 2 is a diagram illustrating an example of the configuration of a currency handling system. FIG. 3 is a diagram illustrating an example of a currency handling device used in the currency handling system. FIG. 4 is a diagram illustrating another example of a currency handling device used in the currency handling system. FIG. 5 is a diagram illustrating an example of a software update process for a currency handling device. FIG. 6 is a diagram illustrating another example of a software update process for a currency handling device. FIG. 7 is a diagram illustrating yet another example of a software update process for a currency handling device. FIG. 8 is a diagram illustrating an example of a software update process for a currency handling device newly added to the currency handling system. FIG. 9 is a diagram illustrating an example of a software update process performed using a server that manages the software for the currency handling device. FIG. 10 is a diagram illustrating an example of a software update process performed by obtaining an update file from a currency handling device in a different store. FIG. 11 is a diagram illustrating an update file used to update the software of a currency handling device.

[0020] Hereinafter, embodiments of a currency processing system, currency processing device, program, and method according to the present disclosure will be described with reference to the accompanying drawings.

[0021] [Overview of Money Handling System] Fig. 1 is a schematic diagram for explaining an overview of a money handling system 1 according to this embodiment. The money handling system 1 includes multiple money handling devices 100 (100a, 100b) and a server 10 that stores and manages software used by these money handling devices 100.

[0022] The currency handling device 100a is communicably connected to the server 10 and another currency handling device 100b via a network. There is no particular limitation on the number of currency handling devices 100 included in the currency handling system 1. Although two devices are shown in FIG. 1, the currency handling system 1 may include three or more currency handling devices 100. There is also no limitation on the type of currency handling device 100. The multiple currency handling devices 100 may be the same type of device or different types of devices. The currency handled by the currency handling device 100 may be banknotes, coins, or both banknotes and coins.

[0023] The currency handling device 100 includes a control unit, a memory unit, a communication unit, and components for processing currency. The currency handling device 100 executes currency processing in accordance with instructions received from an operation unit provided in the currency handling device 100 or an external device such as an operation terminal connected to the currency handling device 100. Specifically, currency processing is realized by the control unit controlling the components for processing currency using software stored in the memory unit.

[0024] Multiple types of software are stored in the memory unit of the currency handling device 100. There is no particular limit to the type or number of software stored in each currency handling device 100. Multiple pieces of software may be stored in the same memory unit, or in different memory units. Note that the software referred to in this embodiment includes at least one of programs and data used by the currency handling device 100 to execute currency handling. Although the term software is mainly used in this embodiment, this is not intended to limit the types of programs, data, etc. stored in the memory unit of the currency handling device 100. For example, software programs, programs, data, files, firmware, resources, and other terms may also be included in the software referred to in this embodiment.

[0025] In the example shown in Figure 1, each currency handling device 100 stores software in three categories, first to third (first software, second software, and third software). As shown as "type" in Figure 1, software in the same category includes different types of software. For example, even within the first software, software of type "A01" and software of type "A02" are different software.

[0026] The server 10 is a computer device including a control unit, a memory unit, and a communication unit. The server 10 is a server device for software updates that manages the software of the currency handling system 100 included in the currency handling system 1. The server 10 manages the versions of each piece of software. The example shown in Figure 1 indicates that, for the first software, the latest version of type "A01" is "0001" and the latest version of type "A02" is "0005". Similarly, the latest version of type "B01" of the second software is "0002", the latest version of type "B02" is "0004", and the latest versions of types "C01" and "C02" of the third software are both "0003".

[0027] The server 10 stores update files that the currency handling device 100 uses to update each piece of software to the latest version. In the example shown in Figure 1, the first software of type "A02" can be updated to the latest version "0005" using update file 511. Similarly, the third software of type "C02" can be updated to the latest version "0003" using update file 521.

[0028] When an operation to instruct a software update is performed on an operation unit provided in the currency handling device 100a or an operation terminal connected to the currency handling device 100a, the currency handling device 100a starts the software update process. The process that triggers the start of the software update is not particularly limited. For example, the currency handling device 100a may start the software update process by receiving a signal instructing an update from the server 10.

[0029] The currency handling device 100a, which has started the update process, checks the latest version of each software item stored in the device (A1). The currency handling device 100a acquires information on the latest version of each software item managed by the server 10.

[0030] The currency handling device 100a identifies software that needs to be updated (A2). If the software stored in the memory unit of the currency handling device 100a includes software that is older than the latest version, the currency handling device 100a determines that this software needs to be updated.

[0031] In the example shown in Figure 1, the version of the second software of type "B01" stored in the currency handling device 100a is "0002", the same as the latest version of this software managed by the server 10. Therefore, the currency handling device 100a determines that an update of the second software is not necessary. On the other hand, the version of the first software of type "A02" stored in the currency handling device 100a is "0004", which is older than the latest version "0005" of this software managed by the server 10. Similarly, the version of the third software of type "C02" is "0002", which is older than the latest version "0003" of this software managed by the server 10. Therefore, the currency handling device 100a determines that an update of the first software and the third software is necessary.

[0032] The currency handling device 100a checks the version of the software that needs to be updated that is stored in another currency handling device 100b (A3). The currency handling device 100a searches for a currency handling device that stores the latest version of the software that needs to be updated.

[0033] The currency handling device 100a determines whether the other currency handling device 100b has stored therein the same type of software as the software to be updated. If the other currency handling device 100b has stored therein the same type of software, the currency handling device 100a determines whether the version of this software is the latest version.

[0034] The range within which the currency handling device 100a searches for other currency handling devices that have the latest version of the software stored therein is set in advance. For example, the search range is limited to the network of the store where the currency handling device 100a is installed, and currency handling devices connected to this network are searched for devices that have the latest version of the software to be updated. The search range may also be limited to devices under the management of the organization or company that uses the currency handling device 100a, and devices that have the latest version of the software stored therein may be searched for, including currency handling devices in stores other than the store where the currency handling device 100a is installed. In the example shown in FIG. 1 , there is only one other currency handling device 100b, but if there are multiple currency handling devices 100 within the search range, each device is checked to see whether it has the latest version of the software that needs to be updated in the currency handling device 100a.

[0035] In the example shown in Figure 1, currency handling device 100a recognizes that the latest version of the third software of type "C02" that needs to be updated is stored in another currency handling device 100b. Currency handling device 100a recognizes that the first software of type "A02" that needs to be updated is not stored in another currency handling device 100b.

[0036] After checking the type and version of software stored in the other currency handling device 100b, the currency handling device 100a determines where to obtain the update file (A4). If the other currency handling device 100b stores the latest version of the same type of software as the software to be updated, the currency handling device 100a determines this device as the source of the update file. On the other hand, for software to be updated that is not stored in the other currency handling device 100b, the currency handling device 100a determines the server 10 as the source of the update file. In other words, the currency handling device 100a prioritizes the other currency handling device 100b when determining where to obtain the update file. The currency handling device 100a determines the server 10 as the source of the update file only if it is unable to obtain the update file from the other currency handling device 100b.

[0037] In the example shown in Figure 1, currency handling device 100a determines that the update file for the third software of type "C02" will be obtained from currency handling device 100b. On the other hand, currency handling device 100a cannot obtain the update file for the first file of type "A02" from another currency handling device 100b. Therefore, currency handling device 100a determines that the update file for the first file of type "A02" will be obtained from server 10.

[0038] 1, the currency handling apparatus 100a acquires the update files 511 and 521 from the determined acquisition source. The update files 511 and 521 are acquired by transmitting and receiving data via a network.

[0039] The currency handling device 100a acquires an update file 521 for the third software of type "C02" from another currency handling device 100b (B). When updating the software, the currency handling device 100 stores the update file in its memory. Therefore, the memory of the currency handling device 100b stores an update file 521 corresponding to the latest version "0003" of the third software of type "C02". This update file 521 is transmitted from the currency handling device 100b to the currency handling device 100a via the network.

[0040] The currency handling device 100 may not store a software update file. In this case, the currency handling device 100 may prepare an update file. The currency handling device 100b stores the latest version "0003" of the third software type "C02" and executes this software to process currency. If this third software is an executable file or data file that can be transmitted and received between devices, the currency handling device 100b may copy it and send it to the currency handling device 100a as an update file 521. If the third software is in a format that cannot be transmitted to the currency handling device 100a as is, such as firmware written to the device's memory, the currency handling device 100b may dump the contents of the memory to generate an update file 521 and send it to the currency handling device 100a.

[0041] The currency handling device 100a acquires an update file 511 for the first software of type "A02" from the server 10 (C). The server 10 stores update files for updating each software to the latest version in its storage unit. The update file 511 corresponding to the latest version "0005" of the first software of type "A02" is transmitted from the server 10 to the currency handling device 100a via the network.

[0042] The currency handling device 100a updates the first software and the third software using update files 511 and 521 (D). The first software of type "A02" is updated from version "0004" to "0005" using update file 511 obtained from server 10. The third software of type "C02" is updated from version "0002" to "0003" using update file 521 obtained from another currency handling device 100b. As a result, the currency handling device 100a becomes able to process currency by executing the first software of type "A02" with the latest version "0005" and the third software of type "C02" with the latest version "0003."

[0043] The currency handling device 100a stores update files 511 and 521 for updating to new versions in a storage unit within the device. As shown in Figure 1, update file 510 for updating the first software of type "A02" to version "0004" is replaced with update file 511 for updating to the latest version "0005." Update file 520 for updating the third software of type "C02" to version "0002" is replaced with update file 521 for updating to the latest version "0005."

[0044] In this way, when a currency handling system 1 currency handling device 100 can obtain a software update file from another currency handling device 100, it obtains the update file from the other currency handling device 100 and updates the software, rather than from the server 10. This reduces the load on the server 10 related to the update process compared to when all update files are obtained from the server 10. The processing load on the server 10 related to communication processing is reduced, and the communication load on the network connecting the server 10 and the currency handling device 100 is also reduced.

[0045] [Specific Example of Money Handling System] (System Configuration) A specific example of the money handling system 1 will be described using a bank branch as an example. FIG. 2 is a diagram showing an example of the configuration of the money handling system 1. The money handling system 1 shown in FIG. 2 includes a server 10, a banknote processing device 110, a banknote processing device 120 of a type different from the banknote processing device 110, and a valuable medium processing device 130. These devices 110, 120, and 130 are all examples of the money handling device 100 described in FIG. 1. Hereinafter, the banknote processing device 110 will be referred to as the first device 110, the banknote processing device 120 as the second device 120, and the valuable medium processing device 130 as the third device 130 to distinguish them from one another. In some cases, a separate server that manages the first device 110, the second device 120, and the third device 130 is used in a branch, but this will be described later.

[0046] The first device 110, the second device 120, and the third device 130 are installed in the store and are communicatively connected to one another via the store network 3. The first device 110, the second device 120, and the third device 130 are communicatively connected to the server 10 via an external network 2 and an internal network 3. An account processing server 4 that executes bank account-related processing is connected to the external network 2. The type of the external network 2 is not particularly limited, and may be, for example, a public line such as the Internet, or a dedicated line. Hereinafter, the Internet will be used as an example, and the external network 2 will be referred to as the Internet 2 to distinguish it from the internal network 3.

[0047] The first device 110 and the second device 120 are banknote processing devices installed at bank counters and used by tellers who serve customers. For example, the first device 110 is installed at the first counter, and the second device 120 is installed at the second counter. The first device 110 and the second device 120 are connected to operation terminals 111 and 121, respectively. The operation terminals 111 and 121 are, for example, computer devices equipped with an operation unit and a display unit. The teller at the first counter can operate the operation terminal 111 to deposit banknotes through the deposit unit 11 of the first device 110 and withdraw banknotes from the withdrawal unit 12. The teller at the second counter can operate the operation terminal 121 to deposit banknotes through the deposit unit 11 of the second device 120 and withdraw banknotes from the withdrawal unit 12.

[0048] For example, when a customer deposits money into a bank account at a counter, the teller operates the operation terminal 111 to deposit the banknotes received from the customer into the first device 110 and confirm the deposit amount, and the account processing server 4 then executes account processing to update the balance of the bank account based on the deposit amount. When a customer withdraws money from a bank account at a counter, the teller operates the operation terminal 111 to withdraw banknotes equivalent to the withdrawal amount from the first device 110, and the account processing server 4 then executes account processing to update the balance of the bank account based on the withdrawal amount. Similar processing is also executed in the operation terminal 121 and the second device 120.

[0049] The third device 130 is installed, for example, in a bank lobby and is used by customers visiting the bank. The third device 130 is configured by combining multiple types of devices. The third device 130 includes a banknote processing device 110 having the same configuration as the first device 110. The third device 130 further includes a wrapped coin processing device 131, a check processing device 132, a coin processing device 133, and a drop box 134. The devices 110 and 131 to 134 that make up the third device 130 are connected to a control terminal 135.

[0050] The control terminal 135 is a computer device equipped with, for example, a touch panel type liquid crystal display. Customers can process banknotes, coins, checks, and wrapped coins by operating the control terminal 135. The banknote processing device 110 performs deposit and withdrawal processes for banknotes. The coin processing device 133 performs deposit and withdrawal processes for loose coins. The wrapped coin processing device 131 performs withdrawal processes for wrapped coins. The check processing device 132 performs deposit processes using checks. The drop box 134 stores cash and checks that cannot be stored in the banknote processing device 110, coin processing device 133, and check processing device 132.

[0051] Customers can use the third device 130 in the lobby to deposit and withdraw banknotes, deposit and withdraw coins, withdraw wrapped coins, deposit checks, and the like. Customers can operate the control terminal 135 to perform deposit and withdrawal processes using the banknote processing device 110, the wrapped coin processing device 131, the check processing device 132, and the coin processing device 133. If a banknote is severely damaged and the banknote processing device 110 cannot accept and process it mechanically, the customer can store the banknote in the drop box 134 and operate the control terminal 135 to perform the deposit process. Similarly, for coins that cannot be mechanically processed by the coin processing device 133 or checks that cannot be mechanically processed by the check processing device 132, customers can store them in the drop box 134 and operate the control terminal 135 to perform the deposit process. Even when the third device 130 performs a deposit or withdrawal that requires account processing, the account processing server 4 performs account processing to change the balance of the customer's bank account based on the operations and processing performed by the third device 130.

[0052] (Configuration of currency processing device and board) Figure 3 is a diagram showing an example of the configuration of the first device 110. Figure 3(a) is a schematic cross-sectional view showing an example of the device configuration of the first device 110. Figure 3(b) shows an example of the configuration of the board and software of the first device 110. The firmware, identification software, main body software, driver software, system software and alarm software shown in Figure 3(b) are examples of the software described in Figure 1. Figure 3(c) shows an example of the configuration of the board.

[0053] As shown in FIG. 3A, the first device 110 is divided into an upper unit 110a and a lower unit 110b.

[0054] The upper unit 110a is provided with a deposit unit 11, a withdrawal unit 12, a recognition unit 20, and a temporary holding unit 30. The lower unit 110b is provided with a plurality of storage units 50. The transport unit 40 transports banknotes between the deposit unit 11, the withdrawal unit 12, the recognition unit 20, the temporary holding unit 30, and each storage unit 50 along a transport path connecting each unit. The transport unit 40 transports banknotes between the upper unit 110a and the lower unit 110b.

[0055] The depositing unit 11, the dispensing unit 12, the escrow unit 30, the transporting unit 40, and the storage unit 50 are components for processing banknotes. The depositing unit 11 is a component including a structure for holding banknotes received from the outside and a feeding mechanism for sending the held banknotes to the transporting unit 40. The dispensing unit 12 is a component including a structure for holding banknotes received from the transporting unit 40 so that they can be discharged to the outside. The escrow unit 30 and the storage unit 50 are components including a structure for storing banknotes received from the transporting unit 40 and a feeding mechanism for sending the stored banknotes to the transporting unit 40. The transporting unit 40 is a component including a transport mechanism made of belts and rollers. Note that the components for processing banknotes may not include some of the components described above, or may include other components. For example, the components for processing banknotes may not include the escrow unit 30, or may include the recognition unit 20. The recognition unit 20 includes one or more sensors for detecting characteristics of banknotes and a processing circuit for determining the type of banknote based on the output of each sensor. The sensors included in the recognition unit 20 include, for example, at least one of an optical sensor, a magnetic sensor, a thickness sensor, and an ultrasonic sensor.

[0056] The lower unit 110b is configured to include a safe 60. The safe door 61 is locked. The safe door 61 opens by performing a predetermined unlocking operation with the operation unit 62. The lower unit 110b is configured such that the storage unit 50 and the circuit boards 70, 82, and 90 housed therein cannot be accessed unless the safe door 61 is opened.

[0057] During a deposit process, multiple banknotes received by the deposit unit 11 are sent out one by one to a transport path within the device and transported by the transport unit 40. The banknotes are recognized by the recognition unit 20 and then stored in the temporary holding unit 30. The recognition unit 20 recognizes the denomination of the banknotes. The recognition unit 20 may also recognize the authenticity and fitness of the banknotes. Based on the recognition result by the recognition unit 20, the deposit amount, which is the total amount of banknotes received by the deposit unit 11, is counted. The deposit amount of banknotes is displayed on the screen of the display unit of the operation terminal 111. When a teller performs an operation on the operation terminal 111 to confirm the deposit amount, the banknotes from the temporary holding unit 30 are fed out and stored in the storage unit 50. For example, the denominations of banknotes to be stored in the storage unit 50 are set in advance, and the banknotes are stored in the storage unit 50 by denomination based on the recognition result by the recognition unit 20.

[0058] During a dispensing process, banknotes to be dispensed, which are specified by operating the operation terminal 111, are fed from the storage unit 50. The banknotes are transported by the transport unit 40, recognized by the recognition unit 20, and then discharged from the dispensing unit 12 to the outside of the device.

[0059] As shown in FIG. 3( a), the first device 110 has multiple boards 21, 70, 81, 82, and 90. The identification board 21 is provided inside the identification unit 20. In addition to the identification board 21, the upper unit 110a is provided with an upper board 81. The main board 70, the lower board 82, and the alarm kit board 90 are provided inside the safe 60 of the lower unit 110b. As shown in FIG. 3( b), the upper board 81, the identification board 21, the lower board 82, and the alarm kit board 90 are communicatively connected to the main board 70. The upper board 81 and the identification board 21 are also communicatively connected to each other.

[0060] As shown in FIG. 3( c), the main board 70 includes a control unit 71, a memory unit 72, and a communication unit 73. Like the main board 70, the identification board 21, the upper board 81, the lower board 82, and the alarm kit board 90 also include a control unit, a memory unit, and a communication unit. The control unit of each board 21, 70, 81, 82, 90 executes software stored in the memory unit and controls each component of the first device 110 connected via the communication unit, thereby realizing the functions and operations of the first device 110. The storage and update of software in the memory unit, execution of software stored in the memory unit, and control of each unit via the communication unit are performed by the control unit of the board, but hereinafter these may be referred to as the operation of the board or the currency processing device.

[0061] As shown in FIG. 3( b), the upper substrate 81 stores firmware for controlling the components of the upper unit 110a and the recognition unit 20. The upper substrate 81 controls the depositing unit 11, dispensing unit 12, recognition unit 20, escrow unit 30, and transport unit 40 in the upper unit 110a based on the firmware. During a depositing process, the upper substrate 81 realizes the process of sending banknotes from the depositing unit 11 into the device, transporting them by the transporting unit 40, recognizing them by the recognition unit 20, and storing them in the escrow unit 30, and the process of feeding banknotes from the escrow unit 30 and sending them to the lower unit 110b after the deposit amount has been determined. During a dispensing process, the upper substrate 81 also realizes the process of transporting banknotes received by the upper unit 110a from the lower unit 110b by the transporting unit 40, recognizing them by the recognition unit 20, and dispensing them from the dispensing unit 12. The upper board 81 also controls each of the multiple sensors provided in each part of the upper unit 110a, such as sensors that detect the presence or absence of banknotes in the deposit section 11 and the withdrawal section 12, and sensors that detect the passage of banknotes transported by the transport section 40 on the transport path within the upper unit 110a, and outputs the detection results from the sensors to the main board 70.

[0062] The recognition board 21 stores recognition software for controlling the recognition unit 20. The recognition board 21 executes the recognition software to realize the process of detecting the arrival of banknotes transported by the transport unit 40 and recognizing them in the recognition unit 20, as well as the process of outputting the recognition results to the main board 70.

[0063] The lower board 82 stores firmware for controlling each component in the lower unit 110b. The lower board 82 controls the transport unit 40 and each storage unit 50 in the lower unit 110b based on the firmware. During a deposit process, the process of transporting banknotes received by the lower unit 110b from the upper unit 110a using the transport unit 40 and storing them in the storage units 50 is realized by the lower board 82. During a withdrawal process, the process of feeding banknotes to be withdrawn from the storage units 50 and sending them to the upper unit 110a using the transport unit 40 is also realized by the lower board 82. The lower board 82 also controls each of the multiple sensors provided in each part of the lower unit 110b, such as sensors that detect the presence or absence and amount of banknotes in the storage units 50 and sensors that detect the passage of banknotes transported by the transport unit 40 through the transport path in the lower unit 110b, and outputs the detection results from the sensors to the main board 70.

[0064] The alarm kit board 90 stores alarm software for detecting security abnormalities that occur in the first device 110 and issuing an alarm. The alarm kit board 90 executes the alarm software to realize processes for detecting abnormalities in the first device 110 and for reporting the abnormalities. For example, the alarm kit board 90 realizes processes such as a process in which a sensor provided on the safe door 61 detects that the safe door 61 has been forced open without performing an unlocking operation on the operation unit 62, and a process in which a vibration sensor detects that abnormal vibrations have occurred in the safe 60. The alarm kit board 90 also realizes output of the detection results from the sensors to the main board 70.

[0065] The main board 70 stores main body software for overall control of the first device 110. The main board 70 also stores system software such as an OS (Operating System) and driver software necessary for controlling each component. For example, the main board 70 starts an OS such as Windows (registered trademark) or Linux (registered trademark), executes the main body software on the OS, and controls each component using the driver software, thereby realizing the functions and operations of the first device 110. The main board 70 executes the main body software to control the upper board 81, the identification board 21, the lower board 82, and the alarm kit board 90, thereby realizing currency processing, including processing by each of the above-mentioned boards.

[0066] The second device 120 shown in Fig. 2 has a similar configuration to the first device 110 shown in Fig. 3. However, the first device 110 and the second device 120 have partially different device configurations, and therefore the software for controlling each part is also partially different.

[0067] Specifically, the configuration of the upper unit is the same in the first device 110 and the second device 120. Therefore, the upper board 81 and the firmware stored in the upper board 81 are common to the first device 110 and the second device 120. That is, the upper board 81 and the firmware of the upper board 81 of the first device 110 are the same as the firmware of the upper board 81 and the upper board 81 of the second device 120. However, because the model numbers (types) of the identification units 20 are different between the first device 110 and the second device 120, the identification board 21 and the identification software of the first device 110 are different from the identification board 21 and the identification software of the second device 120.

[0068] The first device 110 and the second device 120 differ in the number and type of storage compartments 50 in the lower unit. Therefore, the firmware stored on the lower board 82 and the lower board 82 of the first device 110 differs from the firmware stored on the lower board 82 and the lower board 82 of the second device 120.

[0069] The system software stored on the main board 70 is common to the first device 110 and the second device 120. As described above, the first device 110 and the second device 120 have partially different device configurations. Therefore, the main board 70 of the first device 110, and the main software and driver software stored on the main board 70, are different from the main board 70 of the second device 120, and the main software and driver software stored on the main board 70.

[0070] The first device 110 and the second device 120 share the alarm kit board 90 and the alarm software stored in the alarm kit board 90 is also common.

[0071] 4A and 4B are diagrams showing an example of the configuration of the third device 130. Fig. 4A shows an example of the device configuration of the third device 130. Fig. 4B shows an example of the board and software configuration of the third device 130.

[0072] As shown in FIG. 4( a ), the third device 130 includes a banknote processing device 110 , a wrapped coin processing device 131 , a check processing device 132 , a coin processing device 133 , and a drop box 134 , all connected to a control terminal 135 .

[0073] The third device 130 processes banknotes and coins in the same way as an ATM (automated teller machine) and can cause the account processing server 4 to perform account processing. As shown in FIG. 4( b), the control terminal 135 of the third device 130 stores XFS (Xtensions for Financial Services) software to comply with the XFS standard. The XFS standard is an interface standard established to realize ATM functions. The banknote processing device 110 is configured to operate based on the XFS standard. The control terminal 135 executes user interface software on system software consisting of Windows and displays a user interface on the screen. When a customer visiting the bank operates the control terminal 135, the control terminal 135 controls the banknote processing device 110 using the XFS software and banknote processing software provided by a service provider to deposit and withdraw banknotes. Specifically, banknote processing is performed by the main board 70 of the banknote processing device 110 receiving commands related to banknote processing from the control terminal 135 and controlling each section via each board in the same way as the above-mentioned first device 110. Similarly, the control terminal 135 can execute wrapped coin processing software, check processing software, coin processing software, and drop box software to control the wrapped coin processing device 131, check processing device 132, coin processing device 133, and drop box 134.

[0074] The first device 110 and the third device 130 are currency processing devices that differ in appearance and configuration and in the types of currency processing that can be performed, but as shown in Figure 4 (b), the third device 130 includes a banknote processing device 110 that has the same configuration as the first device 110. Therefore, the third device 130 includes the same boards 21, 81, 82, and 90 as the first device 110, and stores the same firmware and software as the first device 110.

[0075] (Software update process) The software update process performed in the currency handling system 1 described in Figures 2 to 4 will be described with reference to Figures 5 to 10. Note that communication between the server 10 and each currency handling device in Figures 5 to 10 is performed via the Internet 2 or network 3 shown in Figure 2.

[0076] 5 is a diagram illustrating an example of the flow of a software update process for first device 110. The software update process will be described below using the main body software, identification software, and alarm kit software described in FIGS. 3 and 4 as examples.

[0077] Server 10 stores update files for updating the software of first device 110, second device 120, and third device 130 to the latest version. The table shown under server 10 in Figure 5 shows the versions of update files for the main software, identification software, and alarm kit software stored in server 10. The tables shown under first device 110, second device 120, and third device 130 show the current versions of the software stored in each device.

[0078] In the software version display shown in Figure 5, letters indicate the type of software and numbers indicate the version. For example, main software "P0002" indicates that the main software type is "P" and the version is "0002." Main software "Q0002" indicates that the main software type is "Q," which is different from "P," and the version is "0002." Similarly, identification software "X0002" indicates that the type is "X" and the version is "0002," and "Y0002" indicates that the main software type is "Y," which is different from "X," and the version is "0002." Because there is only one type of Alarm Kit software, the version display does not include letters indicating the type, but only displays the version indicated by numbers.

[0079] After starting the software update process, first device 110 checks the latest version of each piece of software stored therein (step S1). The latest version is checked by querying server 10. Server 10 may periodically notify first device 110 of information about the latest version.

[0080] The first device 110 identifies software that needs to be updated (step S2). The first device 110 determines that identification software "X0001" needs to be updated to the latest version of identification software "X0002" managed by the server 10. The first device 110 determines that alarm kit software needs to be updated from version "0001" to the latest version "0003" managed by the server 10. The first device 110 determines that main body software "P0002" does not need to be updated because it is the same as the latest version of main body software "P0002" managed by the server 10.

[0081] If any software needs to be updated, the first device 110 checks the software versions stored in other currency processing devices in the store (step S3). The software version check is performed by inquiring about the type and version of software from each of the multiple currency processing devices connected to the store's network 3. As shown in FIG. 5 , the first device 110, having inquired about the type and version of software from the second device 120 and the third device 130, recognizes that the third device 130 has the latest version of the Alarm Kit software stored therein. On the other hand, with regard to the identification software that needs to be updated, the first device 110 recognizes that there is no device in the store that stores the latest version of the identification software.

[0082] The first device 110 determines where to obtain the update file. If the store has another currency processing device that stores the latest version of the software that needs to be updated, the first device 110 prioritizes the other currency processing device as the source from which to obtain the update file. The first device 110 requests this currency processing device to send an update file for updating the software to the latest version (step S4). Upon receiving the request from the first device 110, the currency processing device sends the update file to the first device 110 (step S5). The first device 110 requests the third device 130 to send an update file for updating the Alarm Kit software to the latest version "0003," and the third device 130 sends the update file to the first device 110.

[0083] If the update file cannot be obtained from the currency processing device in the store, the first device 110 determines the server 10 as the source from which to obtain the update file. The first device 110 requests the server 10 to send an update file for updating the software to the latest version (step S6). The server 10, having received the request from the first device 110, sends the update file to the first device 110 (step S7). The first device 110 requests the server 10 to send an update file for updating the identification software, which cannot be obtained from the currency processing device in the store, to the latest version "X0002," and the server 10 sends the update file to the first device 110.

[0084] The first device 110 updates the software within the device using the update files acquired from other currency processing devices in the store and the update files acquired from the server 10 (step S8). The first device 110 updates the alarm kit software to the latest version "0003" of the alarm kit software using the update files acquired from the third device 130. The first device 110 updates the identification software to the latest version "X0002" of the identification software using the update files acquired from the server 10.

[0085] Fig. 6 is a diagram illustrating an example of the flow of a software update process for second device 120. For example, after the software update process for first device 110 shown in Fig. 5 is completed, the process shown in Fig. 6 starts.

[0086] When the second device 120 starts the software update process, it checks the latest version of each piece of software stored within the device and identifies the software that needs to be updated. The second device 120 checks the versions of the software stored in other currency processing devices in the store. The second device 120 determines whether the update file for each piece of software can be obtained from other currency processing devices in the store or whether it needs to be obtained from the server 10, and then determines the device from which to obtain the update file. The source from which the update file is obtained is determined with priority given to other currency processing devices in the store, and if the update file cannot be obtained from other currency processing devices, the server 10 is determined to be the source.

[0087] These processes are performed as described in steps S1 to S3 of Figure 5. The second device 120 determines that the main software needs to be updated to the latest version "Q0002" and the identification software needs to be updated to the latest version "Y0002". The second device 120 determines that the AlarmKit software needs to be updated to the latest version "0003".

[0088] The second device 120 determines that the source of the update file for the alarm kit software is the third device 130. The second device 120 determines that the source of the update files for the main software and the identification software that cannot be obtained from the currency processing device in the store is the server 10.

[0089] As shown in Figure 6, when the third device 130 is requested by the second device 120 to send an update file for the alarm kit software, the third device 130 sends the update file for updating the alarm kit software to version "0003" to the second device 120 (step S11).

[0090] When the server 10 receives a request from the second device 120 to send an update file for the main software, the server 10 sends the update file for updating the main software of the second device 120 to the main software "Q0002" to the second device 120 (step S12). Similarly, when the server 10 receives a request from the second device 120 to send an update file for the identification software, the server 10 sends the update file for updating the identification software of the second device 120 to the identification software "Y0002" to the second device 120 (step S13).

[0091] The second device 120 updates the alarm kit software to the latest version using the update file obtained from the third device 130, and updates the main software and identification software to the latest versions using the update file obtained from the server 10 (step S14). In this way, the main software, identification software, and alarm kit software of the second device 120 are updated to main software "Q0002", identification software "Y0002", and alarm kit software "0003", respectively.

[0092] Fig. 7 is a diagram illustrating an example of the flow of a software update process for the banknote processing device 110 included in the third device 130. For example, the process shown in Fig. 7 starts after the software update process for the first device 110 shown in Fig. 5 and the software update process for the second device 120 shown in Fig. 6 are completed.

[0093] The third device 130 that has started the software update process checks the latest version of each piece of software, identifies the software that needs to be updated, and determines where to obtain the update file, as described in Figures 5 and 6.

[0094] Third device 130 determines that the main body software needs to be updated to the latest version of main body software "P0002" and the identification software needs to be updated to the latest version of identification software "Y0002." Third device 130 determines that first device 110 will be the source from which to obtain the main body software update file, and second device 120 will be the source from which to obtain the identification software update file.

[0095] As shown in Figure 7, when the first device 110 receives a request from the third device 130 to send an update file for the main software, the first device 110 sends the update file to the third device 130 to update the main software of the third device 130 to main software "P0002" (step S21).

[0096] The second device 120, which has been requested by the third device 130 to send an update file for the identification software, sends the update file to the third device 130 to update the identification software of the third device 130 to identification software "Y0002" (step S22).

[0097] The third device 130 uses the update files acquired from the first device 110 and the second device 120 to update the main software of the banknote processing device 110 to the latest version of the main software "P0002" and to update the identification software to the latest version of the identification software "Y0002" (step S23). In this way, if the update files can be acquired from other devices in the store, the update process can be performed without acquiring the update files from the server 10.

[0098] The software update process is also performed when a new currency handling device is introduced into a store. Figure 8 is a diagram illustrating an example of the flow of the software update process for a currency handling device 200 that has been newly added to the currency handling system 1. The currency handling device 200, like the first device 110, the second device 120, and the third device 130, is an example of the currency handling device 100 described in Figure 1.

[0099] Currency handling device 200 is a currency handling device of the same model number (type) as first device 110. The types of main body software, identification software, and alarm kit software stored in currency handling device 200 are the same as the types of main body software, identification software, and alarm kit software stored in first device 110.

[0100] The main software, identification software, and alarm kit software stored in the first device 110 have been updated to the latest versions by the update process shown in Figure 5. On the other hand, the versions of each software in the currency handling device 200 are all older than the latest versions.

[0101] A new currency handling device 200 installed in a store is connected to the store's network 3, which is connected to the first device 110, the second device 120, and the third device 130. When a predetermined operation to instruct a software update is performed on an operation terminal connected to the currency handling device 200 (step S31), the currency handling device 200 starts the software update process.

[0102] The process in which currency handling device 200 checks the latest version of each piece of software, identifies software that needs to be updated, and determines where to obtain the update files is performed as described in Figures 5 to 7. Currency handling device 200 determines that the main software, identification software, and alarm kit software need to be updated. Currency handling device 200 determines that first device 110 will be the source from which to obtain these update files.

[0103] As shown in Figure 8, the first device 110, which has been requested by the currency processing device 200 to send update files for the main software, identification software, and alarm kit software, sends the update files to the currency processing device 200 (step S32).

[0104] The currency handling device 200 updates the main software, identification software, and alarm kit software to the latest versions using the update files obtained from the first device 110. In this way, even for a currency handling device 200 newly installed in a store, if update files can be obtained from another currency handling device in the store, the update process can be performed without obtaining update files from the server 10.

[0105] In the example shown in FIG. 8 , the update file for the main software of the currency handling device 200 can also be obtained from the third device 130, and the update file for the alarm kit software can also be obtained from either the second device 120 or the third device 130. In such a case, in order to minimize the number of devices from which the update files are obtained, all update files may be obtained from a single device as described above. Furthermore, in order to reduce the communication load on each device, update files may be obtained from as many devices as possible. Specifically, the currency handling device 200 may determine that the update file for the main software will be obtained from the third device 130, the update file for the identification software will be obtained from the first device 110, and the update file for the alarm kit software will be obtained from the second device 120. In this case, update files can be obtained from each device to update each software to the latest version.

[0106] In the above example, a currency processing device that has started an update process identifies the latest version of each software item based on information obtained from server 10, and determines where to obtain update files for updating each software item to the latest version by inquiring with other currency processing devices in the store. Alternatively, a separate server may be provided that manages information indicating the latest version of the software and information indicating the type and version of software stored in each currency processing device in the store, and this server may be used to check the version and determine where to obtain update files.

[0107] 9 is a diagram illustrating an example of updating software of the first device 110 using the store server 5 that manages software versions. FIG. 9 illustrates the software update process when the store server 5 is used in the same situation as the example shown in FIG.

[0108] The store server 5 shown in Figure 9 is a computer device that includes a control unit, a storage unit, and a communication unit, similar to the server 10. The store server 5 communicates with the server 10 and each of the currency processing devices 110, 120, and 130 to manage the type and version of software (step S41). The store server 5 manages information indicating the latest version of each piece of software stored in the server 10. The store server 5 manages information indicating the type and version of software stored in each of the currency processing devices 110, 120, and 130.

[0109] When updating the software of the first device 110, the store server 5 uses information managed within the device to determine a method for updating the software of the first device 110 (step S42).

[0110] Specifically, the store server 5 compares the versions of the main software, identification software, and alarm kit software of the first device 110 with the latest versions of each software obtained from the server 10 to identify software that needs to be updated. Based on the type and version of software stored in each currency processing device in the store, the store server 5 searches for other currency processing devices that store the latest version of the software that needs to be updated in the first device 110, and determines where to obtain the update file. For software for which the update file cannot be obtained from a currency processing device in the store, the store server 5 determines that the update file will be obtained from the server 10. As a result, similar to the example shown in FIG. 5 , the store server 5 determines to obtain the update file for the identification software from the server 10 and the update file for the alarm kit software from the third device 130. The store server 5 notifies the first device 110 of information indicating the software that needs to be updated and information indicating the source of the update file for each software.

[0111] Upon receiving the notification from the store server 5, the first device 110 obtains an update file for the alarm kit software from the third device 130 (step S43), and obtains an update file for the identification software from the server 10 (step S44). The first device 110 updates the software using the update file (step S45), thereby updating each piece of software in the first device 110 to the latest version, as in the example shown in FIG.

[0112] It is also possible for the first device 110 to identify software that needs to be updated and determine where to obtain the update file, rather than the store server 5. The first device 110 can identify software that needs to be updated and determine where to obtain the update file by referring to the latest version of each piece of software managed by the store server 5 and the type and version of software stored in each currency processing device in the store.

[0113] The acquisition of the update file from the server 10 may be performed by the store server 5, rather than the first device 110. Instead of step S44 shown in FIG. 9 , the store server 5 may execute a process of acquiring an update file for the identification software from the server 10 and transmitting it to the first device 110. For example, if the currency processing device in the store cannot communicate with the server 10 via the Internet 2, the first device 110 may acquire the update file from the server 10 via the store server 5. In this case, the first device 110 can also update each piece of software to the latest version as described above.

[0114] Alternatively, a specific currency processing device within the store may function as the store server 5. For example, the third device 130 manages information indicating the latest version of each piece of software stored in the server 10 and information indicating the type and version of software stored in each of the currency processing devices 110, 120, and 130. When updating the software of the first device 110, the currency processing device functioning as the store server 5 may use the information managed within the device to determine the method for updating the software of the first device 110.

[0115] In the above example, a currency processing device obtains an update file from another currency processing device installed in the same store, but it may also obtain an update file from a currency processing device located in another store.

[0116] Figure 10 is a diagram illustrating an example of a process for obtaining an update file from a currency handling device 300 in a different store and updating the software of the second device 120. Figure 10 shows a software update process that is executed in the same situation as the example shown in Figure 6. The first device 110, the second device 120, and the third device 130 are installed in store A, and the currency handling device 300 is installed in store B. The currency handling device 300, like the first device 110, the second device 120, and the third device 130, is an example of the currency handling device 100 described in Figure 1.

[0117] Store A and store B are different stores that belong to the same organization or company, for example. The first device 110, the second device 120, and the third device 130 in store A and the currency handling device 300 in store B are currency handling devices under the control of the same organization or company.

[0118] The first device 110, second device 120, and third device 130 in store A and the currency handling device 300 in store B can communicate via the Internet 2. However, the method of communication between the currency handling device in store A and the currency handling device in store B is not particularly limited. For example, communication may be performed using a dedicated communication line, or may be performed using a VPN (Virtual Private Network) or the like.

[0119] As described in Figure 6, the second device 120, which has started the software update process, determines where to obtain update files for the main software, identification software, and alarm kit software. The second device 120 can include a currency processing device 300 located in a store B other than the store A where the second device 120 is installed as a source of update files. The second device 120 determines where to obtain the update files in the following order of priority: the currency processing device located in the store A where the second device 120 is installed, the currency processing device located in the other store B, and the server 10.

[0120] The alarm kit software can be obtained from a third device 130 located in the same store A. Therefore, the second device 120 determines that the third device 130 is the source from which to obtain the update file for the alarm kit software. The identification software update file cannot be obtained from other currency processing devices located in store A, but can be obtained from a currency processing device 300 located in store B. Therefore, the second device 120 determines that the identification software update file is obtained from the currency processing device 300 in store B. The main software update file cannot be obtained from the currency processing devices located in stores A and B. Therefore, the second device 120 determines that the server 10 is the source from which to obtain the update file for the main software.

[0121] As shown in FIG. 10 , the second device 120 acquires an update file for the alarm kit software from the third device 130 in store A (step S51). The second device 120 acquires an update file for the identification software from the currency processing device 300 in store B (step S52). The second device 120 acquires an update file for the main software from the server 10 (step S53). The second device 120 updates the software using the acquired update file (step S54). In this case, the second device 120 can also update each piece of software to the latest version, similar to the example described in FIG. 6 .

[0122] (Update file) Figure 11 is a diagram for explaining an example of an update file used to update software in a currency handling device. Using the main software stored on the main board of the currency handling device as an example, the structure of the update file and a specific example of the update process will be explained.

[0123] In the example shown in Fig. 11, the main body software is composed of a base program and an application. Fig. 11 shows an example in which the system software shown in Fig. 3 is the base program, the main body software is the application, and software that includes these is the main body software. By executing the base program and then executing the application on the base program, control of each part by the main body software is realized.

[0124] 11A shows the relationship between the main software version and the base program and application versions. Below table 400, the structure of update files 401 (401a to 401c) for updating the main software to each version is shown.

[0125] Update file 401a is a package file that includes signature data, a parts list, and update data. The update data may consist of only application difference data, as shown in update file 401a, or may include base program data and application difference data, as shown in update files 401b and 401c.

[0126] The signature data is used in the process of verifying that the update file is a legitimate file. The signature data can be generated using conventionally known technology. For example, a hash value of the data in the update file 401 is calculated and encrypted using a private key, which is then used as the signature data. The currency processing device can compare the hash value of the data contained in the update file with the hash value obtained by decrypting the signature data using the public key to verify that the data is legitimate and has not been tampered with.

[0127] The parts list is data that lists the update data for the base program and the application included in the update file. By referencing the parts list, the currency processing device can confirm the version of the base program and the version of the differential data used to update the application included in the update file.

[0128] In the example shown in Figure 11(a), the main board is initially installed with the base program and application software version "1.3.0" stored therein.

[0129] In the main body software of version "1.3.1," the base program remains at version "1.3.0," and only the application has been upgraded to version "1.3.1." Because there is no change to the base program, the update file 401a for updating to this version does not include the base program, but instead includes signature data, a parts list, and difference data for updating the application to version "1.3.1."

[0130] When updating the main board's main software from the initial version "1.3.0" to version "1.3.1," the update process is performed using the update file 401a. In the update process, the base program remains the same and only the application is updated. Specifically, some data is rewritten and additional data is added to the initial version "1.3.0" application using differential data to update it to version "1.3.1." As a result, the application becomes version "1.3.1."

[0131] In the main body software version "1.4.0," both the base program and the application have been upgraded to version "1.4.0." The update file 401b for updating to this version includes signature data, a parts list, and the base program version "1.4.0." The update file 401b also includes difference data for updating the application from the initial version "1.3.0" to version "1.3.1," and difference data for updating from version "1.3.1" to version "1.4.0."

[0132] When updating the main board's main software from the initial version "1.3.0" to version "1.4.0", if the update process is performed using update file 401b, the base program will be overwritten with the base program of version "1.4.0".

[0133] On the other hand, the initial version "1.3.0" application has some data rewritten and data added using the difference data for version "1.3.1" to become the version "1.3.1" application. Then, some data is rewritten and data is added using the difference data for version "1.4.0", and the version "1.3.1" application becomes the version "1.4.0" application.

[0134] The main board with the main software version "1.3.1" can also be updated using the update file 401b. When the update process is performed using the update file 401b, the base program is overwritten with the base program version "1.4.0".

[0135] On the other hand, since the application has already been updated to version "1.3.1", the differential data for version "1.3.1" contained in the update file 401b is not used, and some data is rewritten and data is added using the differential data for version "1.4.0", so that the application becomes a version "1.4.0" application.

[0136] When updating the main software to version "1.4.1," the update process is performed using update file 401c. When updating the main board's main software from its initial version "1.3.0" using update file 401c, the version "1.3.0" base program is rewritten to the version "1.4.0" base program. The application is partially rewritten and partially updated using the differential data for versions "1.3.1," "1.4.0," and "1.4.1," resulting in the version "1.4.1" application.

[0137] When updating a main board whose main software is version "1.4.0" using the update file 401c, the base program is already version "1.4.0" and so remains unchanged. The application becomes version "1.4.1" by partially modifying and adding data using the difference data for version "1.4.1."

[0138] 11(b) is a flowchart showing an example of the flow of the software update process executed on the main board. As described above, the main board of the currency processing device acquires the update file 401 from another currency processing device or the server 10 (step S61).

[0139] The main board checks the parts list included in the update file 401 (step S62). The main board identifies the data to be used to update the main software from among the data included in the update file 401, based on the current main software version, the base program version included in the update file 401, and the version of the application update difference data (step S63).

[0140] The main board checks the signature data included in the update file 401 (step S64). The main board determines whether the update file 401 includes legitimate data based on the signature data (step S65).

[0141] If the data is not authentic (step S65; No), the main board does not update the software, but executes error processing (step S69), and terminates the processing. The error processing includes notifying the user of the currency processing device including the main board that the software update has failed.

[0142] If the data is confirmed to be authentic (step S65; Yes), the main board updates the software data by writing the update data identified in step S63 to the memory unit of the main board (step S66). If the update data cannot be written to the memory unit normally (step S67; No), the main board executes error processing (step S69) and ends the process.

[0143] If the update data has been successfully written to the storage unit (step S67; Yes), and if other update data remains (step S68; Yes), the process returns to step S66, and processing is again performed using the remaining update data. For example, as described in FIG. 11(a), the main board rewrites and updates the base program data of the main software, and then updates the application difference data. If there is more than one difference data, the difference data is written in order from the lowest version to the latest version, and the application is updated to the latest version. When the main software update is complete (step S68; No), the main board normally ends processing.

[0144] 2 to 10 in this embodiment illustrate an example of a currency processing device installed in a bank branch, but the type of branch is not particularly limited. For example, as described above, even in a currency processing device installed and used in a retail store, software can be updated by sending and receiving update files between multiple currency processing devices. The appearance, device configuration, board configuration, and software configuration of the currency processing device shown in FIGS. 2 to 10 are also examples and are not intended to limit the appearance or configuration of the currency processing device.

[0145] In this embodiment, examples of multiple types of software have been described, but the currency processing device is not limited to including all of the illustrated software, and may include only some of the software. Furthermore, examples of multiple types of software update processes have been described, but the currency processing device is not limited to executing all of the illustrated update processes, and may execute only some of the update processes. The source from which the update file obtained by the currency processing device is obtained is also an example, and the update file will be obtained from at least one of the server 10 and one or more other currency processing devices.

[0146] In this embodiment, an example is shown in which the currency handling system 1 is configured with a server 10 and multiple currency handling devices. The physical configuration of the currency handling system is not limited to the configuration described in this embodiment. For example, in the example shown in FIG. 2 , the third device 130 may implement some or all of the functions and operations of the server 10 described above. The form of distribution and integration of each device is not limited to the example described above, and all or part of the devices can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc.

[0147] The above describes embodiments of the currency handling system, currency processing device, program, and method according to the present disclosure with reference to the drawings. However, the configuration and operation of the currency handling system and each device that constitutes it are not limited to the above embodiments, and may be implemented with various improvements, changes, and modifications based on the knowledge of those skilled in the art, within the scope that does not deviate from the intent of the system.

Claims

1. A currency handling system comprising: a first currency handling device having a first component that executes processes related to currency handling and a first memory unit that stores first software that operates the first component; and a second currency handling device having a second component that executes processes related to currency handling and a second memory unit that stores second software that operates the second component; wherein if the second software is software that updates the first software to a newer version and an update file that updates the first software to the second software can be obtained from the second currency handling device, the first currency handling device obtains the update file from the second currency handling device and updates the first software to the second software.

2. The currency handling system of claim 1, further comprising a server that stores the update file, wherein the first currency handling device determines whether the update file can be obtained from the second currency handling device, and if the update file can be obtained from the second currency handling device, obtains the update file from the second currency handling device and updates the first software to the second software, and if the update file cannot be obtained from the second currency handling device, obtains the update file from the server and updates the first software to the second software.

3. A currency handling system as described in claim 1 or 2, characterized in that the second currency handling device is connected to the store network to which the first currency handling device is connected.

4. A currency handling system as described in claim 1 or 2, characterized in that the second currency handling device is installed in a store other than the store in which the first currency handling device is installed, and which is under the control of an organization to which the user of the first currency handling device belongs.

5. A currency handling system as described in any one of claims 1 to 4, characterized in that the first software includes software for operating a currency identification unit provided in the first currency handling device.

6. A currency handling system as described in any one of claims 1 to 5, characterized in that the first software includes software for operating components including at least one of a currency deposit section, a currency withdrawal section, and a currency storage section provided in the first currency handling device.

7. A currency handling system as described in any one of claims 1 to 6, characterized in that the first software includes software for operating peripheral devices of the first currency handling device.

8. A currency processing system as described in any one of claims 1 to 7, characterized in that the first software includes software for operating a board possessed by the first currency processing device.

9. A currency processing device that processes currency, comprising: a component that executes processes related to currency processing; a memory unit that stores software for controlling the component; a control unit that executes the software to control the component; and a communication unit that sends and receives data to and from an external device, wherein the control unit obtains an update file for the software from another currency processing device and updates the software using the update file.

10. A program executed by a currency processing device that processes currency, characterized by causing the currency processing device to realize the functions of obtaining software update files for operating components of the currency processing device from other currency processing devices, and updating the software using the update files.

11. A method executed by a currency processing device that processes currency, comprising the steps of: acquiring, from another currency processing device, an update file for software for operating components of the currency processing device; and updating the software using the update file.

Images