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

Abstract

This reduces the load on the update server when updating the software of the currency processing system. [Solution] The currency processing system includes a first currency processing device having a first component that executes processing related to currency processing and a first storage unit that stores first software for operating the first component, and a second currency processing device having a second component that executes processing related to currency processing and a second storage unit that stores second software for operating the second component, wherein the second software is software that updates the first software to a newer version, and an update file for updating the first software to the second software can be obtained from the second currency processing device, the first currency processing device is configured to obtain the update file from the second currency processing device and update the first software to the second software.

Description

Technical Field

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

Background Art

[0002] Conventionally, currency processing apparatuses that perform currency deposit and withdrawal processing at various locations have been used. The control unit of the currency processing apparatus executes software prepared in advance to control the components of the currency processing apparatus, thereby realizing currency processing. The software of the currency processing apparatus is updated as necessary. For example, Patent Document 1 discloses a system for distributing and updating programs and definition files from a server apparatus to a plurality of ATMs (Automated Teller Machines). The server apparatus creates an update schedule based on the operating status of the ATMs, and distributes programs and definition files to each ATM according to the created update schedule. The ATM updates the programs and definition files using the programs and definition files distributed from the server apparatus.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the above prior art, when the number of currency processing apparatuses, which are the distribution destinations of update files, increases, the load on the server apparatus becomes high. For example, although the distribution schedule to each currency processing apparatus can be adjusted to reduce the communication volume per day, the total amount of data distributed from the server apparatus remains unchanged, imposing a load on the server apparatus and the network.

[0005] This disclosure has been made in view of the problems of the prior art described above, and one of its purposes is to provide a currency processing system, a currency processing device, and a currency processing program that can reduce the load on the update server when the software of the currency processing device is updated. [Means for solving the problem]

[0006] The currency processing system according to this disclosure includes a first currency processing device having a first component that executes processing related to currency processing and a first storage unit that stores first software for operating the first component, and a second currency processing device having a second component that executes processing related to currency processing and a second storage unit that stores second software for operating the second component, wherein the second software is software that updates the first software to a newer version, and an update file for updating the first software to the second software can be obtained from the second currency processing device, the first currency processing device obtains the update file from the second currency processing device and updates the first software to the second software.

[0007] In the above configuration, the first currency processing device may further include a server that stores the update file, and the first currency processing device may determine whether or not it can obtain the update file from the second currency processing device, and if it can obtain the update file from the second currency processing device, it may obtain the update file from the second currency processing device and update the first software to the second software, and if it cannot obtain the update file from the second currency processing device, it may obtain the update file from the server and update the first software to the second software.

[0008] In the above configuration, the two currency processing devices may be connected to the network of the 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 different store from the store where the first currency processing device is installed, and which is under the management of the 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 the currency identification unit of the first currency processing device.

[0011] In the above configuration, the first software may include software for operating a component of the first currency processing device that includes at least one of a currency deposit unit, a currency withdrawal unit, and a currency storage unit.

[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 the circuit board of the first currency processing device.

[0014] The currency processing device according to this disclosure is a currency processing device that processes currency, comprising: a component that performs processing related to currency processing; a storage unit that stores software for controlling the component; a control unit that executes the software and controls the component; and a communication unit for sending and receiving data with 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.

[0015] The currency processing program relating to this disclosure is a currency processing program executed by a currency processing device that processes currency, and enables the currency processing device to have a function to obtain an update file for software that operates components of the currency processing device from another currency processing device, and a function to update the software using the update file. [Effects of the Invention]

[0016] According to the currency processing system, currency processing device, and currency processing program according to the present disclosure, when updating software such as programs, firmware, and data related to currency processing in the currency processing device, the load on the update server can be reduced.

Brief Description of the Drawings

[0017] [Figure 1] FIG. 1 is a diagram for explaining the outline of the currency processing system according to the present embodiment. [Figure 2] FIG. 2 is a diagram showing a configuration example of the currency processing system. [Figure 3] FIG. 3 is a diagram for explaining an example of the currency processing device used in the currency processing system. [Figure 4] FIG. 4 is a diagram for explaining an example of another currency processing device used in the currency processing system. [Figure 5] FIG. 5 is a diagram showing an example of the software update process of the currency processing device. [Figure 6] FIG. 6 is a diagram showing another example of the software update process of the currency processing device. [Figure 7] FIG. 7 is a diagram showing yet another example of the software update process of the currency processing device. [Figure 8] FIG. 8 is a diagram showing an example of the software update process of the currency processing device newly added to the currency processing system. [Figure 9] FIG. 9 is a diagram showing an example of the software update process performed using a server that manages the software of the currency processing device. [Figure 10] FIG. 10 is a diagram showing an example of the software update process of obtaining an update file from currency processing devices in different stores. [Figure 11] FIG. 11 is a diagram for explaining the update file used for software update of the currency processing device.

Embodiments for Carrying Out the Invention

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

[0019] [Overview of Currency Processing System] FIG. 1 is a schematic diagram for explaining the overview of a currency processing system 1 according to the present embodiment. The currency processing system 1 includes a plurality of currency processing apparatuses 100 (100a, 100b) and a server 10 that stores and manages software used in these currency processing apparatuses 100.

[0020] The currency processing apparatus 100a is communicably connected to the server 10 and other currency processing apparatuses 100b via a network. The number of currency processing apparatuses 100 included in the currency processing system 1 is not particularly limited. The currency processing system 1 may include three or more currency processing apparatuses 100. The types of the currency processing apparatuses 100 are also not limited. The plurality of currency processing apparatuses 100 may be of the same type or different types. The currency processed by the currency processing apparatus 100 may be banknotes, coins, or both banknotes and coins.

[0021] The currency processing apparatus 100 includes a control unit, a storage unit, a communication unit, and a component for processing currency. The currency processing apparatus 100 executes currency processing according to an instruction received from an operation unit provided in the currency processing apparatus 100 or an external device such as an operation terminal connected to the currency processing apparatus 100. Specifically, the control unit controls the component for processing currency by using the software stored in the storage unit, thereby realizing currency processing.

[0022] Multiple types of software are stored in the memory unit of the currency processing device 100. The types and number of software stored in each currency processing device 100 are not particularly limited. Multiple software may be stored in the same memory unit or in different memory units. In this embodiment, the software includes at least one of the programs and data that the currency processing device 100 uses to perform currency processing. In this embodiment, the term "software" is mainly used, but this is not intended to limit the types of programs, data, etc., stored in the memory unit of the currency processing device 100. For example, software programs, programs, data, files, firmware, resources, etc., which are also referred to by other names, may be included in the software as used in this embodiment.

[0023] In the example shown in Figure 1, each currency processing device 100 stores software from three categories: the first, second, and third software. As shown as "Type" in Figure 1, different types of software are included within the same category. For example, even within the first software category, software of type "A01" and software of type "A02" are different.

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

[0025] Server 10 stores update files for the currency processing device 100 to update each 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.

[0026] When an operation to instruct a software update is performed on the operation unit of the currency processing device 100a, or on an operation terminal connected to the currency processing device 100a, the currency processing 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 processing device 100a may start the software update process when it receives a signal from the server 10 instructing it to update.

[0027] The currency processing device 100a, having initiated the update process, checks for the latest version of each software stored within the device (A1). The currency processing device 100a then retrieves information on the latest version of each software managed by the server 10.

[0028] The currency processing device 100a identifies software that needs updating (A2). If the software stored in the memory unit of the currency processing device 100a contains software older than the latest version, the currency processing device 100a determines that this software needs updating.

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

[0030] The currency processing unit 100a checks the version of the software that needs updating that is stored in another currency processing unit 100b (A3). The currency processing unit 100 searches for a currency processing unit that stores the latest version of the software that needs updating.

[0031] The currency processing device 100a determines whether another currency processing device 100b stores the same type of software as the software to be updated. If the other currency processing device 100b stores the same type of software, the currency processing device 100a determines whether the version of this software is the latest version.

[0032] The scope within which the currency processing device 100a searches for other currency processing devices that store the latest version of the software is predetermined. For example, the search scope may be limited to the network of stores where the currency processing device 100a is installed, and the device storing the latest version of the software to be updated may be searched for among the currency processing devices connected to this network. Alternatively, the search scope may be limited to devices under the control of an organization or company using the currency processing device 100a, and the search for devices storing the latest version of the software may include currency processing devices in stores different from the store where the currency processing device 100a is installed. In the example shown in Figure 1, there is only one other currency processing device 100b, but if there are multiple currency processing devices 100 in the search scope, the presence of the latest version of the software that needs to be updated on the currency processing device 100a will be checked for each device.

[0033] In the example shown in Figure 1, the currency processing unit 100a recognizes that the latest version of the third software of type "C02" that needs updating is stored in the other currency processing unit 100b. The currency processing unit 100a recognizes that the first software of type "A02" that needs updating is not stored in the other currency processing unit 100b.

[0034] After confirming the type and version of software stored in the other currency processing device 100b, currency processing device 100a determines the source of the update file (A4). If the other currency processing device 100b stores the latest version of the same type of software as the software to be updated, currency processing 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 processing device 100b, currency processing device 100a determines server 10 as the source of the update file. In other words, currency processing device 100a prioritizes the other currency processing device 100b when determining the source of the update file. Currency processing device 100a determines server 10 as the source of the update file only if it cannot obtain the update file from the other currency processing device 100b.

[0035] In the example shown in Figure 1, the currency processing device 100a decides to obtain the update file for the third software of type "C02" from the currency processing device 100b. On the other hand, the currency processing device 100a cannot obtain the update file for the first file of type "A02" from the other currency processing device 100b. Therefore, the currency processing device 100a decides that the server 10 is the source from which to obtain the update file for the first file of type "A02".

[0036] As shown in Figure 1, the currency processing device 100a obtains update files 511 and 521 from the determined source. The acquisition of update files 511 and 521 is performed by sending and receiving data over the network.

[0037] The currency processing device 100a obtains an update file 521 for the third software of type "C02" from another currency processing device 100b (B). When updating the software, the currency processing device 100 stores the update file in its storage unit. For this reason, the storage unit of currency processing device 100b stores the update file 521 corresponding to the latest version "0003" of the third software of type "C02". This update file 521 is transmitted from currency processing device 100b to currency processing device 100a via the network.

[0038] The currency processing device 100 may not store software update files. In this case, the currency processing device 100 should prepare the update files. The currency processing device 100b stores the latest version "0003" of third software of type "C02" and performs currency processing by executing this software. If this third software is an executable file or data file that can be sent and received between devices, the currency processing device 100b should copy it and send it to the currency processing device 100a as an update file 521. If the third software is in a format that cannot be sent directly to the currency processing device 100a, such as firmware written to the memory of the device, the currency processing device 100b should dump the contents of the memory to generate an update file 521 and send it to the currency processing device 100a.

[0039] The currency processing device 100a obtains an update file 511 of type "A02" for the first software 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 type "A02" for the first software is transmitted from the server 10 to the currency processing device 100a via the network.

[0040] The currency processing 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 processing device 100b. As a result, the currency processing device 100a is able to perform currency processing by running the first software of type "A02" with the latest version "0005" and the third software of type "C02" with the latest version "0003".

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

[0042] Thus, if the currency processing device 100 of the currency processing system 1 can obtain software update files from another currency processing device 100, it will obtain the update files from that other currency processing device 100 instead of from the server 10 and update the software. This reduces the load on the server 10 related to the update process compared to obtaining all update files 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 processing device 100 is also reduced.

[0043] [Specific examples of monetary processing systems] (System Configuration) Next, a specific example of the currency processing system 1 will be described using a bank branch as an example. Figure 2 shows an example of the configuration of the currency processing system 1. The currency processing system 1 shown in Figure 2 includes a server 10, a banknote processing device 110, a banknote processing device 120 of a different type from the banknote processing device 110, and a valuable media processing device 130. These devices 110, 120, and 130 are all examples of the currency processing device 100 described in Figure 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 media processing device 130 as the third device 130 to distinguish them. In some cases, a separate server may be used to manage the first device 110, the second device 120, and the third device 130 in a bank branch, but this will be discussed later.

[0044] The first device 110, the second device 120, and the third device 130 are installed within the store and are connected to each other so as to be able to communicate via the store's network 3. The first device 110, the second device 120, and the third device 130 are connected to the server 10 so as to be able to communicate via the network outside the store 2 and the network inside the store 3. The account processing server 4, which performs processing related to bank accounts, is connected to the network outside the store 2. The type of network outside the store 2 is not particularly limited and may be a public line such as the internet, or a dedicated line. Hereinafter, using the internet as an example, the network outside the store 2 will be referred to as Internet 2 to distinguish it from the network inside the store 3.

[0045] 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 operating terminals 111 and 121, respectively. The operating terminals 111 and 121 are computer devices equipped with, for example, an operating unit and a display unit. The teller at the first counter can use the operating terminal 111 to deposit banknotes from the deposit unit 11 of the first device 110 and withdraw banknotes from the withdrawal unit 12. The teller at the second counter can use the operating terminal 121 to deposit banknotes from the deposit unit 11 of the second device 120 and withdraw banknotes from the withdrawal unit 12.

[0046] For example, when a customer makes a deposit into a bank account at the 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. The account processing server 4 then performs account processing to update the bank account balance based on the deposit amount. When a customer makes a withdrawal from a bank account at the counter, the teller operates the operation terminal 111 to withdraw the banknotes for the withdrawal amount from the first device 110. The account processing server 4 then performs account processing to update the bank account balance based on the withdrawal amount. Similar processing is performed in the operation terminal 121 and the second device 120.

[0047] The third device 130 is installed, for example, in the lobby of a bank and used by customers visiting the bank. The third device 130 is composed of a combination of several 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 packaged coin processing device 131, a check processing device 132, a coin processing device 133, and a drop box 134. The devices 110, 131-134 that make up the third device 130 are connected to a control terminal 135.

[0048] The control terminal 135 is, for example, a computer device equipped with a touch-panel liquid crystal display. Customers can operate the control terminal 135 to process banknotes, coins, checks, and packaged coins. The banknote processing device 110 performs banknote deposit and withdrawal processing. The coin processing device 133 performs loose coin deposit and withdrawal processing. The packaged coin processing device 131 performs packaged coin withdrawal processing. The check processing device 132 performs check deposit processing. 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.

[0049] Customers can also use the third device 130 in the lobby to deposit and withdraw banknotes, coins, dispense packaged coins, and deposit checks. Customers can operate the control terminal 135 to perform deposit and withdrawal operations at the banknote processing device 110, packaged coin processing device 131, check processing device 132, and coin processing device 133. If banknotes are severely damaged and the banknote processing device 110 cannot accept and process them, customers can place the banknotes in the drop box 134 and perform the deposit operation by operating the control terminal 135. Similarly, for coins that cannot be processed by the coin processing device 133, and checks that cannot be processed by the check processing device 132, customers can place them in the drop box 134 and perform the deposit operation by operating the control terminal 135. 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.

[0050] (Configuration of currency processing equipment and circuit board) Figure 3 shows an example 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 circuit board and software configuration of the first device 110. The firmware, identification software, main unit 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 circuit board configuration.

[0051] As shown in Figure 3(a), the first device 110 is divided into an upper unit 110a and a lower unit 110b.

[0052] The upper unit 110a is provided with a deposit section 11, a withdrawal section 12, an identification section 20, and a temporary holding section 30. The lower unit 110b is provided with multiple storage sections 50. The transport section 40 transports banknotes along transport paths connecting the deposit section 11, the withdrawal section 12, the identification section 20, the temporary holding section 30, and each storage section 50. The transport section 40 transports banknotes between the upper unit 110a and the lower unit 110b.

[0053] The deposit unit 11, the dispensing unit 12, the temporary holding unit 30, the transport unit 40, and the storage unit 50 are components for processing banknotes. The deposit unit 11 is a component comprising a structure for holding banknotes received from the outside and a dispensing mechanism for feeding the held banknotes to the transport unit 40. The dispensing unit 12 is a component comprising a structure for holding banknotes received from the transport unit 40 so that they can be discharged to the outside. The temporary holding unit 30 and the storage unit 50 are components comprising a structure for storing banknotes received from the transport unit 40 and a dispensing mechanism for feeding the stored banknotes to the transport unit 40. The transport unit 40 is a component comprising a transport mechanism consisting of belts and rollers. Note that the components for processing banknotes may not include some of the components described above, or they may include other components. For example, the components for processing banknotes may not include the temporary holding unit 30, or they may include the identification unit 20. The identification unit 20 includes one or more sensors for detecting the 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 identification unit 20 include, for example, at least one of an optical sensor, a magnetic sensor, a thickness sensor, and an ultrasonic sensor.

[0054] The lower unit 110b includes the safe 60. The safe door 61 is locked. The safe door 61 opens by performing a predetermined unlocking operation on the operating unit 62. The lower unit 110b is structured in such a way that the storage compartment 50 and circuit boards 70, 82, and 90 housed inside cannot be accessed unless the safe door 61 is opened.

[0055] During the deposit process, multiple banknotes received by the deposit unit 11 are fed one by one onto a transport path within the device and transported by the transport unit 40. After being identified by the identification unit 20, the banknotes are stored in the temporary holding unit 30. The identification unit 20 identifies the denomination of the banknotes. The identification unit 20 may also identify the authenticity and condition of the banknotes. Based on the identification result by the identification 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 the teller confirms the deposit amount on the operation terminal 111, the banknotes from the temporary holding unit 30 are dispensed and stored in the storage unit 50. For example, the denominations of banknotes to be stored in the storage unit 50 are pre-set, and the banknotes are stored in the storage unit 50 according to their denomination based on the identification result by the identification unit 20.

[0056] During the withdrawal process, the user operates the operation terminal 111 to dispense the specified banknotes from the storage unit 50. The banknotes are transported by the transport unit 40, identified by the identification unit 20, and then discharged from the device through the dispensing unit 12.

[0057] As shown in Figure 3(a), the first device 110 has a plurality of substrates 21, 70, 81, 82, and 90. The identification substrate 21 is provided inside the identification unit 20. In addition to the identification substrate 21, the upper unit 110a is provided with an upper substrate 81. The main substrate 70, the lower substrate 82, and the alarm kit substrate 90 are provided inside the safe 60 of the lower unit 110b. As shown in Figure 3(b), the upper substrate 81, the identification substrate 21, the lower substrate 82, and the alarm kit substrate 90 are communicated with the main substrate 70. The upper substrate 81 and the identification substrate 21 are also communicated with each other.

[0058] As shown in Figure 3(c), the main board 70 includes a control unit 71, a storage unit 72, and a communication unit 73. The identification board 21, upper board 81, lower board 82, and alarm kit board 90 also include a control unit, a storage unit, and a communication unit, similar to the main board 70. The control units of each board 21, 70, 81, 82, and 90 execute software stored in the storage unit and control each component of the first device 110 connected via the communication unit, thereby realizing the functions and operation of the first device 110. On the boards, saving and updating software in the storage unit, executing software stored in the storage unit, and controlling each component via the communication unit are performed by the control unit of the board, but these may be described below as the operation of the board or the currency processing device.

[0059] As shown in Figure 3(b), the upper circuit board 81 stores firmware for controlling each component and identification unit 20 in the upper unit 110a. Based on the firmware, the upper circuit board 81 controls the deposit unit 11, withdrawal unit 12, identification unit 20, temporary holding unit 30, and transport unit 40 in the upper unit 110a. During deposit processing, the upper circuit board 81 is responsible for sending banknotes from the deposit unit 11 into the device, transporting them with the transport unit 40, identifying them with the identification unit 20, and then storing them in the temporary holding unit 30. After the deposit amount is confirmed, the upper circuit board 81 also handles the process of dispensing banknotes from the temporary holding unit 30 and sending them to the lower unit 110b. During withdrawal processing, the upper circuit board 81 is also responsible for transporting banknotes received from the lower unit 110b to the upper unit 110a with the transport unit 40, identifying them with the identification unit 20, and then dispensing them from the withdrawal unit 12. The upper circuit board 81 controls each of the multiple sensors provided in various parts 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 being transported by the transport section 40 in the transport path within the upper unit 110a, as well as the output of the detection results from the sensors to the main circuit board 70.

[0060] The identification board 21 stores identification software for controlling the identification unit 20. When the identification board 21 executes the identification software, it detects and identifies the arrival of banknotes being transported by the transport unit 40, and outputs the identification result to the main board 70. Controls the 30 and the transport unit 40.

[0061] The lower circuit board 82 stores firmware for controlling each component in the lower unit 110b. Based on the firmware, the lower circuit board 82 controls the transport unit 40 and each storage unit 50 in the lower unit 110b. During deposit processing, the lower circuit board 82 is responsible for transporting banknotes received from the upper unit 110a to the lower unit 110b by the transport unit 40 and storing them in the storage unit 50. During withdrawal processing, the lower circuit board 82 is also responsible for dispensing the banknotes to be withdrawn from the storage unit 50 and sending them to the upper unit 110a by the transport unit 40. The lower circuit board 82 also controls each of the multiple sensors provided in various parts of the lower unit 110b, such as sensors that detect the presence and amount of banknotes in the storage unit 50 and sensors that detect the passage of banknotes transported by the transport unit 40 in the transport path within the lower unit 110b, as well as outputting the detection results from the sensors to the main circuit board 70.

[0062] The alarm kit board 90 stores alarm software for detecting security anomalies in the first device 110 and issuing alarms. When the alarm kit board 90 executes the alarm software, it performs processes to detect anomalies in the first device 110 and processes to notify the anomaly. For example, the alarm kit board 90 performs processes such as detecting when the safe door 61 has been forced open without unlocking it using the operation unit 62, based on a sensor installed on the safe door 61, and detecting when abnormal vibrations have occurred in the safe 60, based on a vibration-sensing sensor. The alarm kit board 90 also performs the output of the sensor detection results to the main board 70.

[0063] The main board 70 stores the main 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 part. For example, the main board 70 starts an OS such as Windows® or Linux®, executes the main software on the OS, and uses the driver software to control each part, thereby realizing the functions and operation of the first device 110. The main board 70 executes the main software and controls the upper board 81, identification board 21, lower board 82, and alarm kit board 90, thereby realizing currency processing, including the processing performed by each of the aforementioned boards.

[0064] The second device 120 shown in Figure 2 has the same configuration as the first device 110 shown in Figure 3. However, since the first device 110 and the second device 120 differ in some aspects of their configuration, the software used to control each part also differs in some aspects.

[0065] Specifically, the configuration of the upper unit is identical in the first device 110 and the second device 120. Therefore, the upper circuit board 81 and the firmware stored on the upper circuit board 81 are common to both the first device 110 and the second device 120. In other words, the upper circuit board 81 of the first device 110 and its firmware are identical to the upper circuit board 81 of the second device 120. However, because the model number (type) of the identification unit 20 differs between the first device 110 and the second device 120, the identification circuit board 21 and identification software of the first device 110 are different from the identification circuit board 21 and identification software of the second device 120.

[0066] The first device 110 and the second device 120 differ in the number and type of storage compartments 50 located in their lower units. Therefore, the lower circuit board 82 of the first device 110 and the firmware stored on it are different from the lower circuit board 82 of the second device 120 and the firmware stored on it.

[0067] The system software stored on the main board 70 is the same for both the first device 110 and the second device 120. As mentioned above, the first device 110 and the second device 120 differ in some aspects of their configuration. Therefore, the main board 70 of the first device 110, the main software and driver software stored on it, are different from the main board 70 of the second device 120, the main software and driver software stored on it.

[0068] The alarm kit board 90 is common to both the first device 110 and the second device 120, and the alarm software stored on the alarm kit board 90 is also common to both.

[0069] Figure 4 shows an example configuration of the third device 130. Figure 4(a) shows an example of the device configuration of the third device 130. Figure 4(b) shows an example of the circuit board and software configuration of the third device 130.

[0070] As shown in Figure 4(a), the third device 130 includes a banknote processing device 110, a packaged 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.

[0071] The third device 130, like an ATM (Automated Teller Machine), can process banknotes and coins and have the account processing server 4 execute account processing. As shown in Figure 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 developed to realize the functions of an ATM. The banknote processing device 110 is designed to operate based on the XFS standard. The control terminal 135 runs user interface software on system software consisting of Windows and displays the 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 with the XFS software and the banknote processing software, which is a service provider, to execute banknote deposits and withdrawals. Specifically, the main board 70 of the banknote processing device 110, which receives a command regarding banknote processing from the control terminal 135, controls each part via each board, similar to the first device 110 described above, and banknote processing is executed. Similarly, the control terminal 135 can run packaged coin processing software, check processing software, coin processing software, and dropbox software to control the packaged coin processing device 131, check processing device 132, coin processing device 133, and dropbox 134.

[0072] The first device 110 and the third device 130 are currency processing devices that differ in appearance and configuration, and also in the types of currency processing they can perform. However, as shown in Figure 4(b), the third device 130 includes a banknote processing device 110 with the same configuration as the first device 110. Therefore, the third device 130 includes the same circuit boards 21, 81, 82, and 90 as the first device 110, and stores the same firmware and software as the first device 110.

[0073] (Software update process) The software update process performed in the currency processing system 1, as described in Figures 2 to 4, will be explained with reference to Figures 5 to 10. Note that the communication between the server 10 and each currency processing device in Figures 5 to 10 takes place via the internet 2 and network 3 shown in Figure 2.

[0074] Figure 5 is a diagram illustrating an example of the software update process flow for the first device 110. The following explanation of the software update process will continue using the main unit software, identification software, and alarm kit software described in Figures 3 and 4 as examples.

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

[0076] The software version display shown in Figure 5 uses letters to indicate the software type and numbers to indicate the version. For example, the main unit software "P0002" indicates that the main unit software type is "P" and the version is "0002". The main unit software "Q0002" indicates that the main unit software type is "Q" (different from "P") and the version is "0002". Similarly, the identification software "X0002" indicates that the type is "X" and the version is "0002", and "Y0002" indicates that the main unit software type is "Y" (different from "X") and the version is "0002". Since there is only one type of alarm kit software, the version display does not include the letter indicating the type, and only the version number is shown.

[0077] The first device 110, which has started the software update process, checks for the latest version of each software stored within the device (step S1). The latest version is checked by querying the server 10. The server 10 may periodically notify the first device 110 of the latest version information.

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

[0079] If there is software that needs updating, the first device 110 checks the version of the software stored in other currency processing devices in the store (step S3). The software version check is performed by querying each of the multiple currency processing devices connected to the store's network 3 for the type and version of the software. As shown in Figure 5, after querying the second device 120 and the third device 130 for the type and version of the software, the first device 110 recognizes that the third device 130 has the latest version of the alarm kit software stored in it. On the other hand, regarding the identification software that needs updating, the first device 110 recognizes that there is no device in the store that has the latest version of the identification software stored in it.

[0080] The first device 110 determines the source from which to obtain the update file. If there is another currency processing device in the store that stores the latest version of the software that needs updating, 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 to update the software to the latest version (step S4). The currency processing device that receives the request from the first device 110 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 to update the alarm kit software to the latest version "0003", and the third device 130 sends the update file to the first device 110.

[0081] If the update file cannot be obtained from the currency processing device in the store, the first device 110 determines that the server 10 is the source for obtaining the update file. The first device 110 requests the server 10 to send an update file to update the software to the latest version (step S6). Upon receiving the request from the first device 110, the server 10 sends the update file to the first device 110 (step S7). The first device 110 requests the server 10 to send an update file to update the identification software to the latest version "X0002", which cannot be obtained from the currency processing device in the store, and the server 10 sends the update file to the first device 110.

[0082] The first device 110 updates the software within the device using update files obtained from other currency processing devices in the store and update files obtained 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 file obtained from the third device 130. The first device 110 updates the identification software to the latest version of the identification software "X0002" using the update file obtained from the server 10.

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

[0084] The second device 120, which has started the software update process, checks the latest version of each software stored within the device to identify the software that needs updating. The second device 120 also checks the software versions stored in other currency processing devices in the store. The second device 120 determines whether the update files for each software can be obtained from other currency processing devices in the store or need to be obtained from the server 10, and then determines the device from which to obtain the update files. The destination for obtaining the update files is determined with priority given to other currency processing devices in the store, and if they cannot be obtained from other currency processing devices, the server 10 is determined as the destination.

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

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

[0087] As shown in Figure 6, the third device 130, having received a request from the second device 120 to send an update file for the alarm kit software, sends the update file to the second device 120 to update to version "0003" of the alarm kit software (step S11).

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

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

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

[0091] The process by which the third device 130, which has started the software update process, checks the latest version of each software, identifies the software that needs updating, and determines the source of the update files is carried out as described in Figures 5 and 6.

[0092] The third device 130 determines that the main unit software needs to be updated to the latest version of the main unit software, "P0002," and the identification software needs to be updated to the latest version of the identification software, "Y0002." The third device 130 determines that the source for obtaining the update files for the main unit software is the first device 110, and that the source for obtaining the update files for the identification software is the second device 120.

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

[0094] When the second device 120 receives a request from the third device 130 to send an update file for identification software, it sends an update file to the third device 130 to update the identification software of the third device 130 to identification software "Y0002" (step S22).

[0095] The third device 130 uses update files obtained 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 the identification software to the latest version of the identification software "Y0002" (step S23). In this way, if update files can be obtained from other devices in the store, the update process can be executed without obtaining update files from the server device 10.

[0096] Software update processing is also performed when a new currency processing device is introduced to a store. Figure 8 is a diagram illustrating an example of the software update process for a currency processing device 200 newly added to the currency processing system 1. The currency processing device 200 is an example of the currency processing device 100 described in Figure 1, similar to the first device 110, the second device 120, and the third device 130.

[0097] The currency processing device 200 is a currency processing device of the same model (type) as the first device 110. The types of main unit software, identification software, and alarm kit software stored in the currency processing device 200 are the same as the types of main unit software, identification software, and alarm kit software stored in the first device 110.

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

[0099] The newly installed currency processing unit 200 is connected to the store's network 3, to which the first unit 110, the second unit 120, and the third unit 130 are connected. When a predetermined operation to instruct a software update is performed on an operating terminal connected to the currency processing unit 200 (step S31), the currency processing unit 200 starts the software update process.

[0100] The process by which the currency processing device 200 checks for the latest version of each software, identifies the software that needs updating, and determines the source from which to obtain the update files is carried out as described in Figures 5 to 7. The currency processing device 200 determines that the main software, identification software, and alarm kit software need to be updated. The currency processing device 200 determines that the source from which to obtain these update files is the first device 110.

[0101] 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 unit software, identification software, and alarm kit software, sends the update files to the currency processing device 200 (step S32).

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

[0103] In the example shown in Figure 8, the update file for the main software of the currency processing device 200 can be obtained from the third device 130, and the update file for the alarm kit software can 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 update files can be obtained, all update files may be obtained from a single device as described above. Also, in order to reduce the communication load on each device, update files may be obtained from as many devices as possible. Specifically, the currency processing device 200 may decide that the source for the main software update file is the third device 130, the source for the identification software update file is the first device 110, and the source for the alarm kit software update file is the second device 120. In this case as well, the update files can be obtained from each device and each software can be updated to the latest version.

[0104] In the example described above, a currency processing unit that initiated the update process identified the latest version of each software based on information obtained from server 10, and determined the source of the update files to update each software to the latest version by querying other currency processing units in the store. Alternatively, a separate server could be set up to manage information indicating the latest version of the software and information indicating the type and version of the software stored in each currency processing unit in the store. This server could then be used to check the version and determine the source of the update files.

[0105] Figure 9 illustrates an example of updating the software of the first device 110 using the store server 5, which manages the software version. Figure 9 shows the software update process when using the store server 5, under the same circumstances as the example shown in Figure 5.

[0106] 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 currency processing unit 110, 120, and 130 to manage the type and version of the software (step S41). The store server 5 manages information indicating the latest version of each software stored in the server 10. The store server 5 manages information indicating the type and version of the software stored in each currency processing unit 110, 120, and 130.

[0107] When updating the software of the first device 110, the store server 5 uses the information managed within the device to determine how to update the software of the first device 110 (step S42).

[0108] 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 the software that needs updating. Based on the type and version of software stored in each currency processing device within the store, the store server 5 searches for other currency processing devices that store the latest versions of the software that needs updating in the first device 110, and determines the source of the update files. For software for which the update files cannot be obtained from the currency processing devices within the store, the store server 5 determines that the source of the update files is the server 10. As a result, the store server 5 decides 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, similar to the example shown in Figure 5. The store server 5 notifies the first device 110 of the information indicating the software that needs updating and the information indicating the source of the update files for each software.

[0109] Upon receiving 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 an update file for the identification software from the server 10 (step S44). By updating the software using the update files, the first device 110 can update each piece of software in the first device 110 to the latest version, similar to the example shown in Figure 5.

[0110] Furthermore, the identification of software requiring updates and the determination of the source of update files may be performed by the first device 110 rather than the store server 5. The first device 110 can identify the software requiring updates and determine the source of update files by referring to the latest version of each software managed by the store server 5 and the type and version of software stored in each currency processing device within the store.

[0111] The acquisition of update files from server 10 may be performed by the store server 5 instead of the first device 110. Instead of step S44 shown in Figure 9, the store server 5 may perform the process of acquiring the update files for the identification software from server 10 and sending them to the first device 110. For example, if the currency processing device in the store cannot communicate with server 10 via the internet 2, the first device 110 may acquire the update files from server 10 via the store server 5. In this case as well, the first device 110 can update each software to the latest version as described above.

[0112] 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 software stored by the server 10, and information indicating the type and version of the software stored by each currency processing device 110, 120, and 130. When updating the software of the first device 110, the currency processing device functioning as the store server 5 can use the information it manages to determine how to update the software of the first device 110.

[0113] In the example described above, a currency processing device obtains an update file from another currency processing device installed within the same store. However, it is also possible to obtain the update file from a currency processing device located in a different store.

[0114] Figure 10 illustrates an example of a process for updating the software of the second device 120 by obtaining an update file from a currency processing device 300 located in a different store. Figure 10 shows a software update process performed under the same circumstances 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 processing device 300 is installed in store B. The currency processing device 300 is an example of the currency processing device 100 described in Figure 1, similar to the first device 110, the second device 120, and the third device 130.

[0115] Store A and Store B are, for example, different stores belonging to the same organization or company. The first device 110, the second device 120, and the third device 130 in Store A, and the currency processing device 300 in Store B are currency processing devices under the management of the same organization or company.

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

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

[0118] The alarm kit software can be obtained from the third device 130 located in the same store A. Therefore, the second device 120 decides that the source for obtaining the update files for the alarm kit software is the third device 130. The update files for the identification software cannot be obtained from other currency processing devices in store A, but they can be obtained from the currency processing device 300 in store B. Therefore, the second device 120 decides that the source for obtaining the update files for the identification software is the currency processing device 300 in store B. The update files for the main unit software cannot be obtained from currency processing devices in stores A and B. Therefore, the second device 120 decides that the source for obtaining the update files for the main unit software is the server 10.

[0119] As shown in Figure 10, the second device 120 obtains an update file for the alarm kit software from the third device 130 in store A (step S51). The second device 120 obtains an update file for the identification software from the currency processing device 300 in store B (step S52). The second device 120 obtains an update file for the main unit software from the server 10 (step S53). The second device 120 updates the software using the obtained update file (step S54). In this case as well, the second device 120 can update each software to the latest version, similar to the example described in Figure 6.

[0120] (Update file) Figure 11 illustrates an example of an update file used to update the software of a currency processing unit. Using the main software stored on the main board of the currency processing unit as an example, the structure of the update file and a specific example of the update process are explained.

[0121] In the example shown in Figure 11, the main software consists of a base program and an application. Figure 11 shows an example where the system software shown in Figure 3 is the base program, the main software is the application, and the software containing these is the main software. By executing the base program and then executing the application on top of the base program, control of each part by the main software is realized.

[0122] Table 400 in Figure 11(a) shows the relationship between the main software version and the versions of the base program and applications. Below Table 400, the structure of the update files 401 (401a to 401c) for updating the main software to each version is shown.

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

[0124] Signature data is data used to verify that an update file is a legitimate file. Signature data can be generated using conventionally known techniques. For example, the hash value of the data in update file 401 can be calculated, encrypted using a private key, and used as signature data. The currency processing device can verify that the data is genuine and untampered by comparing the hash value of the data contained in the update file with the hash value obtained by decrypting the signature data using a public key.

[0125] The parts list is data that shows a list of update data for the base program and application included in the update file. By referring to the parts list, the currency processing device can check the version of the base program and the version of the differential data used to update the application included in the update file.

[0126] In the example shown in Figure 11(a), version "1.3.0" of the main software is the initial software. For example, the main board is incorporated into the currency processing unit with version "1.3.0" base program and applications stored on it.

[0127] In version "1.3.1" of the main software, the base program remains version "1.3.0," while only the application has been updated to version "1.3.1." Since there are no changes to the base program, the update file 401a for updating to this version does not include the base program, but instead contains signature data, a parts list, and differential data to update the application to version "1.3.1."

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

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

[0130] When updating the main board's software from the initial version "1.3.0" to version "1.4.0", using update file 401b to perform the update process will overwrite the base program with the version "1.4.0" base program.

[0131] On the other hand, the initial version "1.3.0" application undergoes some data rewriting and data addition using differential data for version "1.3.1," becoming the version "1.3.1" application. Subsequently, some data rewriting and data addition using differential data for version "1.4.0" transforms the version "1.3.1" application into the version "1.4.0" application.

[0132] Even main boards with the main software version "1.3.1" can have their main software updated using update file 401b. When the update process is performed using update file 401b, the base program will be overwritten with the base program version "1.4.0".

[0133] On the other hand, since the application has already been updated to version "1.3.1", the differential data for version "1.3.1" included in update file 401b will not be used. Instead, some data will be rewritten and some data added using the differential data for version "1.4.0", resulting in the application becoming version "1.4.0".

[0134] When updating the main unit software to version "1.4.1", the update process is executed using update file 401c. When updating the main board's software from the initial version "1.3.0" using update file 401c, the base program of version "1.3.0" is rewritten with the base program of version "1.4.0". The application is then sequentially modified and data is added based on the differential data of versions "1.3.1", "1.4.0", and "1.4.1", resulting in the application of version "1.4.1".

[0135] When updating a main board with version "1.4.0" software using update file 401c, the base program remains unchanged because it is already version "1.4.0". The application, however, will be updated to version "1.4.1" by having some data modified or added based on the differential data for version "1.4.1".

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

[0137] The main board checks the parts list contained in the update file 401 (step S62). Based on the current version of the main unit software, the version of the base program contained in the update file 401, and the version of the differential data for application updates, the main board identifies the data to be used to update the main unit software from the data contained in the update file 401 (step S63).

[0138] The main board verifies the signature data contained in the update file 401 (step S64). Based on the signature data, the main board determines whether or not the update file 401 contains legitimate data (step S65).

[0139] If the data is not valid (Step S65; No), the main board will not perform the software update, but will execute error handling (Step S69) and terminate the process. Error handling includes notifying the user of the currency processing device, including the main board, that the software update has failed.

[0140] If it is confirmed that the data is legitimate (Step S65; Yes), the main board updates the software data by writing the update data identified in Step S63 to the main board's memory (Step S66). If the update data cannot be successfully written to the memory (Step S67; No), the main board performs error handling (Step S69) and terminates the process.

[0141] If the update data is successfully written to the memory unit (Step S67; Yes), and if there is any other update data remaining (Step S68; Yes), the process returns to Step S66 and the remaining update data is processed again. For example, as explained in Figure 11(a), the main board updates the base program data of the main software by rewriting it, and then updates the differential data of the application. If there are multiple differential data, the writing is repeated in order from the lowest version differential data, and the application is updated to the latest version. When the main software update is complete (Step S68; No), the main board completes the process successfully.

[0142] Figures 2 to 10 of 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, even for currency processing devices installed and used in retail stores, the software can be updated by sending and receiving update files between multiple currency processing devices, as described above. The appearance, device configuration, circuit board configuration, and software configuration of the currency processing device shown in Figures 2 to 10 are also illustrative examples and do not limit the appearance or configuration of the currency processing device.

[0143] In this embodiment, several examples of software types have been described, but the currency processing device is not limited to a configuration that includes all software, but may include only some of the software. Similarly, although several examples of software update processes have been described, the currency processing device is not limited to a configuration that performs all of the illustrated update processes, but may perform only some of the update processes. The source of the update files acquired by the currency processing device is also illustrative, and the update files will be acquired from at least one device among the server 10 and one or more other currency processing devices.

[0144] In this embodiment, an example is shown in which the currency processing system 1 is composed of a server 10 and a plurality of currency processing devices. The physical configuration of the currency processing system is not limited to the configuration described in this embodiment. For example, in the example shown in Figure 2, the third device 130 may be configured to realize 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 them can be configured to be functionally or physically distributed and integrated in any unit according to various loads and usage conditions.

[0145] While embodiments of the currency processing system, currency processing device, and currency processing program described above with reference to the drawings, the configuration and operation of the currency processing system and its constituent devices are not limited to the above embodiments. They may be implemented with various improvements, changes, and modifications based on the knowledge of a person skilled in the art, without departing from the spirit of the invention. [Industrial applicability]

[0146] The currency processing system, currency processing device, and currency processing program according to the present invention are useful for reducing the load on the update server when updating the software of the currency processing device. [Explanation of symbols]

[0147] 1. Currency Processing System 2, 3 Networks 10 servers 11. Deposit Section 12. Withdrawal Department 20 Identification unit 21 Identification board 30 Temporary holding section 40 Conveying section 50 Storage compartments 60 safes 70, 81, 82, 90 circuit boards 100, 110, 120, 130, 200, 300 currency processing device

Claims

1. A first currency processing device having a first component that executes processing related to currency processing, and a first storage unit that stores first software for operating the first component, A second currency processing device having a second component that executes processing related to currency processing, and a second storage unit that stores second software for operating the second component. Includes, If the second software is software that updates the first software to a newer version, and an update file for updating the first software to the second software can be obtained from the second currency processing device, the first currency processing device obtains the update file from the second currency processing device and updates the first software to the second software. A monetary processing system characterized by the following features.

2. Server that stores the aforementioned update files Furthermore, The first currency processing device determines whether or not it can obtain the update file from the second currency processing device. If the update file can be obtained from the second currency processing device, the update file is obtained from the second currency processing device and the first software is updated to the second software. If the update file cannot be obtained from the second currency processing device, the update file is obtained from the server and the first software is updated to the second software. The currency processing system according to feature 1.

3. The second currency processing device is connected to the network of the store to which the first currency processing device is connected. The currency processing system according to claim 1 or 2.

4. The second currency processing device is installed in a different store from the store where the first currency processing device is installed, and is under the management of the organization to which the users of the first currency processing device belong. The currency processing system according to claim 1 or 2.

5. The first software includes software for operating the currency identification unit of the first currency processing device. The currency processing system according to any one of claims 1 to 4.

6. The first software includes software for operating a component of the first currency processing device that includes at least one of a currency deposit unit, a currency withdrawal unit, and a currency storage unit. The currency processing system according to any one of claims 1 to 5.

7. The first software includes software for operating peripheral devices of the first currency processing device. The currency processing system according to any one of claims 1 to 6.

8. The first software includes software for operating the circuit board of the first currency processing device. The currency processing system according to any one of claims 1 to 7.

9. A money processing device for handling currency, A component that performs processing related to monetary transactions, A storage unit that stores software for controlling the aforementioned components, A control unit that executes the aforementioned software to control the aforementioned components, A communication unit for sending and receiving data with external devices and Equipped with, The control unit obtains an update file for the software from another currency processing device and updates the software using the update file. A currency processing device characterized by the following features.

10. A currency processing program executed by a currency processing device that processes currency, A function to obtain update files for the software used to operate the components of a currency processing device from other currency processing devices, The function of updating the software using the aforementioned update file. A currency processing program characterized by implementing this in a currency processing device.

Images