Processing system and processing method

Abstract

To improve the possibility of automatically inspecting a currency processing device without competition with program updating of the currency processing device.SOLUTION: A processing system includes a first acquisition unit for acquiring a first time range for performing automatic inspection of a currency processing device, a second acquisition unit for acquiring a second time range for performing program updating of the currency processing device, and a processing unit for performing the predetermined processing such that the first time range is not at least partially overlapped with the second time range when the first time range and the second time range are at least partially overlapped with each other.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to a processing system and a processing method.

Background Art

[0002] Patent Document 1 describes a cash processing machine inspection system that can perform an unscheduled inspection on a cash processing machine when there are no bank staff, such as at night or on holidays, based on an instruction from a monitoring server or a reservation received in advance, and notify the management responsible person of the inspection determination result. Patent Document 2 describes a cash handling device including a control unit that determines whether to perform an automatic inspection of the balance at night, and executes the automatic inspection of the balance early in the morning on the business day following the day when it is determined to perform the automatic inspection of the balance at night. The control unit sets the execution time of the automatic inspection of the balance at night, and when the power is turned on within a predetermined time from the execution time of the automatic inspection of the balance at night, the automatic inspection of the balance at night is executed.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document II

Summary of the Invention

Problems to be Solved by the Invention

[0004] When adopting a configuration that sets a time range for automatically inspecting a currency processing device regardless of the time range for updating the program of the currency processing device, there is a possibility that the program update and the automatic inspection of the currency processing device may conflict.

[0005] An object of the present invention is to increase the possibility of being able to perform an automatic inspection of a currency processing device without conflicting with the program update of the currency processing device.

Means for Solving the Problems

[0006] To this end, the present invention provides a processing system comprising: a first acquisition unit for acquiring a first time range for performing automatic scrutiny of a currency processing device; a second acquisition unit for acquiring a second time range for updating the program of the currency processing device; and a processing unit that performs predetermined processing to ensure that the first time range and the second time range do not overlap at least partially when the first time range and the second time range overlap at least partially. The prescribed process may be a process that outputs information indicating that at least one of the first time range and the second time range should be changed. The prescribed process may also be a process that modifies the first time range such that the first time range and the second time range do not overlap at least partially. The prescribed process may be a process that modifies the second time range so that the first time range and the second time range do not overlap at least partially. In that case, the prescribed process may be a process that modifies the second time range to a time range that falls within the second off-hours period after the first off-hours period, if the second time range falls within the first off-hours period. In that case, the second off-hours period may be the earliest off-hours period after the first off-hours period that satisfies the prescribed conditions indicating that it is possible to perform the program update that was scheduled to be performed within the second time range. Furthermore, in that case, the prescribed condition may be that the off-hours period is longer than the time required to perform the program update that was to be carried out within the second time range. Moreover, in that case, the off-hours period may be the first length on business days and a second length different from the first length on non-business days. Furthermore, in that case, the predetermined condition may be that even if the program update that was to be performed in the second time range is carried out, the number of currency processing units that perform the program update does not exceed the maximum number of currency processing units that can perform the program update simultaneously. The prescribed process may be a process that modifies the time range specified by the user from the first time range and the second time range so that the first time range and the second time range do not overlap at least partially. The automated inspection includes daytime automated inspection and nighttime automated inspection, and the first time range may be the time range during which the money processing unit performs nighttime automated inspection. The automatic verification includes a first automatic verification instructed from an operating unit provided in the currency processing device and a second automatic verification instructed from a remote terminal located remotely from the currency processing device, wherein the first time range may be the time range for performing the second automatic verification of the currency processing device. The processing unit may, if, as a result of ensuring that the first time range and the second time range do not overlap at least partially, the first time range and the second time range fall within the same non-business hours period, then prioritize the second time range over the first time range.

[0007] The present invention also provides a processing method that includes the steps of: a computer obtaining a first time range for performing automatic scrutiny of a currency processing device; a computer obtaining a second time range for updating the program of the currency processing device; and a computer performing predetermined processing to ensure that the first time range and the second time range do not overlap at least partially, if the first time range and the second time range overlap at least partially. [Effects of the Invention]

[0008] According to the present invention, there is a higher possibility that automatic inspection of a currency processing device can be performed without conflicting with program updates for the currency processing device. [Brief explanation of the drawing]

[0009] [Figure 1] This figure shows an example of the overall configuration of the processing system in an embodiment of the present invention. [Figure 2] This figure shows an example of the configuration of a currency processing device according to an embodiment of the present invention. [Figure 3]This is a block diagram showing a functional configuration example of the server device in the embodiment of the present invention. [Figure 4] This is a diagram showing an example of the setting information stored in the setting information storage unit. [Figure 5] This is a diagram showing an example of the automatic inspection information stored in the automatic inspection information storage unit. [Figure 6] This is a diagram showing an example of the program update information stored in the program update storage unit. [Figure 7] This is a diagram showing, by way of a specific example, the operation of the server device in the embodiment of the present invention. [Figure 8] This is a diagram showing an example of the program update information stored in the program update storage unit after the operation of the server device shown by way of a specific example is executed. [Figure 9] This is a flowchart showing an operation example of the server device in the embodiment of the present invention. [Figure 10] This is a flowchart showing the specific content of the update plan creation process in the embodiment of the present invention.

Embodiments for Carrying Out the Invention

[0010] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0011] [Overall Configuration of the Processing System] FIG. 1 is a diagram showing an overall configuration example of the processing system 1 in the present embodiment. As shown in the figure, the processing system 1 is configured by connecting currency processing devices 10a to 10c and a server device 20 via a communication line 80.

[0012] The currency processing devices 10a to 10c are devices installed in stores of financial institutions such as banks, etc., and perform currency deposit processing and withdrawal processing. The currency processing devices 10a to 10c also execute an automatic inspection process that automatically checks whether the balance data stored in the memory within the device matches the actual balance of the currency stored within the device. The currency processing devices 10a to 10c execute each process by operating a control program (hereinafter simply referred to as "program"). This program is updated (upgraded) as necessary. Incidentally, when not distinguishing between these, the currency processing devices 10a to 10c may also be referred to as the currency processing device 10. Although three currency processing devices 10 are shown in the figure, two or fewer or four or more currency processing devices 10 may be provided.

[0013] The server device 20 is a device installed in, for example, a center that monitors the currency processing device 10, and performs a process of distributing and updating the program operating on the currency processing device 10. The server device 20 may be connected to a terminal device (not shown), and the program to be distributed and updated may be registered from this terminal device to the server device 20. Incidentally, distributing and updating the program operating on the currency processing device 10 also includes distributing data for updating the program operating on the currency processing device 10 and updating the program with this data.

[0014] The communication line 80 is a line for communicating information between the currency processing devices 10a to 10c and the server device 20. As the communication line 80, although not limited to this, for example, the Internet may be used.

[0015] [Currency Processing Device] FIG. 2 is a diagram showing a configuration example of the currency processing device 10 in the present embodiment. Incidentally, here, only the function of processing banknotes among the functions of the currency processing device 10 is described, and the description of the function of processing coins is omitted.

[0016] As shown in the figure, the currency processing device 10 includes a display unit 101 for displaying various information and an operation unit 102 operated by the user to input information. The currency processing device 10 further includes a deposit slot 103 for depositing banknotes, a reject slot 104 for ejecting counterfeit banknotes, a dispensing slot 105 for dispensing banknotes, and a reject compartment 106 for storing abnormal banknotes. The currency processing device 10 further includes an identification unit 110 for identifying the denomination and authenticity of passing banknotes, a front / back reversal unit 111 for reversing the front and back of passing banknotes, and a dispensing identification unit 112 for identifying abnormalities such as dispensing two banknotes at once or banknotes being skewed. The currency processing device 10 further includes a 10,000 yen storage compartment 120 for storing 10,000 yen banknotes, a 5,000 yen storage compartment 130 for storing 5,000 yen banknotes, a 2,000 yen storage compartment 140 for storing 2,000 yen banknotes, and a 1,000 yen storage compartment 150 for storing 1,000 yen banknotes. Note that the 10,000 yen storage compartment 120, the 5,000 yen storage compartment 130, the 2,000 yen storage compartment 140, and the 1,000 yen storage compartment 150 may be simply referred to as storage compartments 120-150 when not distinguished. The currency processing device 10 further includes temporary holding compartments 121-151 corresponding to storage compartments 120-150, respectively. The currency processing device 10 further includes a communication unit 160 that receives programs from the server device 20, and a card reader 161 that reads the user's card. The currency processing device 10 also further includes a memory that stores data on the balance of each denomination of currency, a control unit that controls the entire system, and so on (not shown in the figure).

[0017] The currency processing device 10 uses an identification unit 110 to identify the denomination and authenticity of banknotes deposited into the deposit slot 103. The currency processing device 10 then uses a front / back reversal unit 111 to align the front and back of genuine banknotes and stores them in storage compartments 120 to 150 according to denomination (10,000 yen, 5,000 yen, 2,000 yen, 1,000 yen) via temporary holding units 121 to 151. The currency processing device 10 ejects counterfeit banknotes and the like into the reject slot 104. Furthermore, when a withdrawal instruction is received, the currency processing device 10 dispenses banknotes stored in storage compartments 120-150 one by one according to the denomination to be withdrawn, and dispenses them to the withdrawal slot 105 via the withdrawal identification unit 112. Any abnormal banknotes, such as double bills or skewed banknotes, are stored in the reject compartment 106. The reject compartment 106 is equipped with a shutter (not shown), and the stored banknotes cannot be removed unless the shutter is opened.

[0018] Furthermore, when an automatic verification instruction is received, the currency processing device 10 sequentially dispenses all denominations of banknotes one by one, passes them through the dispensing identification unit 112, then through the temporary holding units 121 to 151, and finally re-stores them in the storage units 120 to 150, respectively. This automatically determines the balance of banknotes in the storage units 120 to 150. On the other hand, for banknotes whose denomination and number could not be determined during dispensing due to double dispensing or skewed banknotes, the balance is determined by an operator manually removing the banknotes from the reject storage unit 106, confirming the number of banknotes of each denomination, and inputting the information using the operation unit 102. The currency processing device 10 then performs a verification by comparing the sum of these balances with the balance data stored in memory, and displays the results on the display unit 101.

[0019] [Server device configuration] Figure 3 is a block diagram showing an example of the functional configuration of the server device 20 in this embodiment. As shown in the figure, the server device 20 includes a control unit 21, a storage unit 22, a display unit 23, an operation unit 24, and a communication unit 25.

[0020] The control unit 21 is equipped with arithmetic circuits such as a CPU (Central Processing Unit) and controls each part of the server device 20 (display unit 23, operation unit 24, communication unit 25, etc.) according to the program stored in the memory unit 22. The memory unit 22 is equipped with ROM (Read Only Memory), RAM (Random Access Memory), etc., and stores the program of the control unit 21. It is also used as a work area during the control processing of the control unit 21. The program of the control unit 21 includes a program for the control unit 21, which is a computer, to execute the processes described later. The display unit 23 is, for example, a display that shows various kinds of information. The operation unit 24 is, for example, a keyboard or mouse that the user operates to input information. The communication unit 25 communicates information with the currency processing unit 10 via the communication line 80.

[0021] Here, the configuration of the control unit 21 will be described in detail. The control unit 21 comprises an operation reception unit 211, a setting information acquisition unit 212, a priority determination unit 213, an automatic review information acquisition unit 214, a program update information acquisition unit 215, an update plan creation unit 216, and a display control unit 217.

[0022] The operation reception unit 211 receives operations performed by the user using the operation unit 24. Specifically, the operation reception unit 211 determines whether the user has performed an operation to instruct the creation of a program update plan, and if it determines that the user has performed an operation to instruct the creation of a program update plan, it accepts that operation. The user may, for example, perform an operation to instruct the creation of a program update plan on a web screen displayed on the display unit 23, and the operation reception unit 211 may accept such an operation.

[0023] The configuration information acquisition unit 212 acquires configuration information from the storage unit 22 when the operation reception unit 211 receives an operation from the user instructing the creation of a program update plan. Configuration information is pre-configured information used, for example, by the update plan creation unit 216 when creating a program update plan. The configuration information includes the unit time period, the unit data amount, the maximum multiplicity, the business day update time period, and the holiday update time period. The unit time period is the smallest unit allocated for the time period in which program updates are performed. The unit data amount is the amount of program data that can be updated in a unit time period by one currency processing unit 10. The maximum multiplicity is the number of currency processing units 10 that can be updated simultaneously in a unit time period. The business day update time period is the time period in which program updates can be performed on business days. The holiday update time period is the time period in which program updates can be performed on holidays.

[0024] The priority determination unit 213 determines the priority order for program updates of multiple currency processing devices 10. For example, the priority determination unit 213 may determine the priority order according to the financial institution where the currency processing device 10 is installed, the region where the currency processing device 10 is installed, the model of the currency processing device 10, etc. However, this is merely an example, and the priority determination unit 213 may determine the priority order according to any rules.

[0025] The automatic verification information acquisition unit 214 acquires automatic verification information from the storage unit 22. Automatic verification information refers to information about automatic verification performed on the currency processing device 10 that is the target of program update planning among the multiple currency processing devices 10. The automatic verification information includes the nighttime automatic verification date of the currency processing device 10 that is the target of program update planning. In the following, the timing of nighttime automatic verification is defined by day, but it may also be defined by day and time. More generally, this can be understood as defining the timing of nighttime automatic verification by time range. There are also daytime automatic verifications and nighttime automatic verifications. In the following, only nighttime automatic verifications are assumed as automatic verifications, but daytime automatic verifications may also be assumed as automatic verifications. In this embodiment, the nighttime automatic verification date is used as an example of a first time range for performing automatic verification of currency processing devices, and the automatic verification information acquisition unit 214 is provided as an example of a first acquisition unit that acquires the first time range.

[0026] The program update information acquisition unit 215 acquires program update information from the storage unit 22. Program update information refers to information regarding program updates in the currency processing device 10 that is the target of program update planning among the multiple currency processing devices 10. The program update information includes the amount of data of the program to be updated and the instructed update date, which is the update date instructed when the program update was registered. In the following, the timing of the program update instructed when the program update was registered is defined by day, but it may also be defined by day and time zone. More generally, this can be understood as defining the timing of the instructed program update by time range. In this embodiment, the instructed update date is used as an example of a second time range for performing program updates of currency processing devices, and the program update information acquisition unit 215 is provided as an example of a second acquisition unit that acquires the second time range.

[0027] The update plan creation unit 216 determines whether the nighttime automatic review date acquired by the automatic review information acquisition unit 214 matches the instructed update date acquired by the program update information acquisition unit 215. If it determines that the nighttime automatic review date and the instructed update date match, it creates a program update plan such that the nighttime automatic review date and the program update date and time do not match. In this embodiment, the timing of the nighttime automatic review and the timing of the instructed program update are defined by day, so the update plan creation unit 216 determines whether the nighttime automatic review date and the instructed update date match, but this is not limited to this. If the timing of the nighttime automatic review and the timing of the instructed program update are defined by time ranges, the update plan creation unit 216 only needs to determine whether those time ranges overlap at least partially. In this embodiment, the update plan creation unit 216 is provided as an example of a processing unit that performs predetermined processing to ensure that the first time range and the second time range do not overlap at least partially when the first time range and the second time range overlap at least partially.

[0028] Furthermore, if the update plan creation unit 216 determines that the nighttime automatic review date and the instructed update date coincide, it shifts the program update date and time to a later date than the instructed update date, thereby preventing the nighttime automatic review date and the program update date and time from coinciding. In this embodiment, the nighttime automatic review and program update are assumed to be performed during off-hours that do not span across midnight, and the update plan creation unit 216 shifts the program update date and time to a later date; however, it is not limited to this. The nighttime automatic review and program update may also be performed during off-hours that span across midnight, and the update plan creation unit 216 may shift the program update date and time to a later off-hours period. In this embodiment, the update plan creation unit 216 is provided as an example of a processing unit that modifies the second time range so that the first time range and the second time range do not overlap at least partially. Furthermore, in this embodiment, as an example of the first off-hours period, the day including the timing of the instructed program update is used, and as an example of the second off-hours period which is later than the first off-hours period, the day including the shifted timing of the program update is used. And, if the second time range is included in the first off-hours period, an update plan creation unit 216 is provided as an example of a processing unit that performs processing to change the second time range to a time range included in the second off-hours period which is later than the first off-hours period.

[0029] Furthermore, if there are multiple candidates for a date later than the instructed update date, the update plan creation unit 216 selects the earliest date that meets the predetermined conditions from among the multiple candidates and shifts the program update date and time to that date. In this case, the specified condition may be that the off-hours period is longer than the time required to perform the program update that was scheduled to be performed on the instruction update day. In this case, the off-hours period may be longer on non-business days than on business days. Alternatively, more generally, the off-hours period may be of different lengths on business days and non-business days. In other words, the off-hours period may be a first length on business days and a second length different from the first length on non-business days. Furthermore, the predetermined condition may also be that even if a program update that was scheduled to be performed on the instruction update day is carried out, the number of currency processing devices 10 that perform the program update does not exceed the maximum multiplicity, which is the maximum number of currency processing devices 10 that can perform the program update simultaneously. However, these conditions are merely examples, and other conditions may be used as predetermined conditions. In this embodiment, the earliest day that satisfies the predetermined conditions is used as an example of the earliest off-hours period that satisfies the predetermined conditions, which is to show that it is possible to perform a program update that was scheduled to be carried out within the second time range of off-hours periods that are later than the first off-hours period.

[0030] The display control unit 217 controls the display unit 23 to display information. Specifically, the display control unit 217 determines whether the nighttime automatic review date acquired by the automatic review information acquisition unit 214 matches the instructed update date acquired by the program update information acquisition unit 215. If it determines that the nighttime automatic review date and the instructed update date match, it controls the display unit 23 to display information indicating that a program update plan should be created so that the nighttime automatic review date and the program update date and time do not match. For example, the display control unit 217 may control the display unit 23 to display information indicating that the nighttime automatic review date should be shifted, information indicating that the program update date and time should be shifted, or information indicating that both the nighttime automatic review date and the program update date and time should be shifted. This will cause the user to create a program update plan so that the nighttime automatic review date and the program update date and time do not match. In this embodiment, the timing of the nightly automatic review and the timing of the instructed program update are defined by day, so the display control unit 217 determines whether the nightly automatic review day and the instructed update day coincide, but this is not limited to this. If the timing of the nightly automatic review and the timing of the instructed program update are defined as time ranges, the display control unit 217 only needs to determine whether those time ranges overlap at least partially. In this embodiment, the display control unit 217 is provided as an example of a processing unit that performs predetermined processing to ensure that the first time range and the second time range do not overlap at least partially when the first time range and the second time range overlap at least partially. In this embodiment, the display control unit 217 is provided as an example of a process that outputs information indicating that at least one of the first time range and the second time range should be changed.

[0031] Next, the configuration of the memory unit 22 will be described in detail. The memory unit 22 comprises a setting information storage unit 221, an automatic verification information storage unit 222, and a program update information storage unit 223. The configuration information storage unit 221 stores the configuration information. Details of the configuration information will be described later. The automatic verification information storage unit 222 stores the automatic verification information. Details of the automatic verification information will be described later. The program update information storage unit 223 stores program update information. Details of the program update information will be described later.

[0032] Figure 4 shows an example of setting information stored in the setting information storage unit 221. As shown in the figure, the setting information is a correspondence between setting items and setting values. The settings stored include time zones, data volume per unit, maximum multiplicity, business day update time zones, and holiday update time zones. As described above, the unit time zone is the smallest unit of time allocated for program updates. The time zones for program updates are multiples of this unit time zone. As described above, the unit data amount is the amount of program data that can be updated in a unit time zone by one currency processing unit 10. As mentioned above, the maximum multiplicity is the number of currency processing units 10 that can be updated simultaneously in a unit of time. Here, since it is assumed that the program is distributed to the currency processing units 10 and updated immediately, the maximum multiplicity is set to mean the number of currency processing units 10 that can simultaneously receive the program in a unit of time. The business day update time slot, as mentioned above, is the time period during which program updates can be performed on business days. The holiday update time slot, as mentioned above, is the time period during which program updates can be performed on holidays. These time slots are set as a single continuous time period between 0:00 and 24:00. The default settings are 60 minutes for each time unit, 50 MB for each data unit, 3 for the maximum concurrency, 0:00 to 6:00 for the business day update time, and 0:00 to 22:00 for the non-business day update time. However, these values ​​are merely examples, and any other values ​​may be stored as default settings. In this example, the configuration information is assumed to be common within processing system 1, but this is not the only option. For example, the configuration information may differ for each financial institution or branch.

[0033] Figure 5 shows an example of automatic inspection information stored in the automatic inspection information storage unit 222. As shown in the figure, the automatic inspection information associates the device ID with the nighttime automatic inspection date. The device ID is information that identifies the currency processing device 10. The "Nighttime Automatic Verification Day" is information indicating the day on which the nighttime automatic verification of the currency processing device 10, identified by the corresponding device ID, is performed. The diagram shows, for example, that the automatic nighttime inspection of the currency processing device 10 with device ID "M10" will be performed on April 3rd. Furthermore, the currency processing device 10 transmits automatic verification information indicating the next nighttime automatic verification date to the server device 20 at a predetermined time each day. As a result, the server device 20 stores the automatic verification information in the automatic verification information storage unit 222.

[0034] Figure 6 shows an example of program update information stored in the program update information storage unit 223. As shown in the figure, the program update information associates the device ID, program ID, data amount, instruction update date, update date and time, and planned flag. The device ID is information that identifies the currency processing device 10, as described in relation to Figure 5. The program ID is information that identifies the program to be updated in the currency processing device 10 identified by the corresponding device ID. The data amount is the amount of data for the program to be updated in the currency processing device 10 identified by the corresponding device ID. The unit of data amount is MB. The instruction update date is information indicating the update date instructed when a program update was registered for the currency processing device 10 identified by the corresponding device ID. The update date and time is information indicating the date and time when the program update is scheduled to be performed for the currency processing device 10 identified by the corresponding device ID. The Planned Flag indicates whether a program update is planned for the currency processing device 10 identified by the corresponding device ID. The Planned Flag is "ON" if the program update is planned, and "OFF" if the program update is not planned. The diagram shows, for example, that a program update with program ID "P01" is scheduled for the currency processing device 10 with device ID "M01," and that the data size is 300MB. It also shows that the program update is instructed to take place on April 1st, and that the update is planned to take place between 0:00 and 6:00 on April 1st. The diagram also shows, for example, that a program update with program ID "P03" is scheduled for the currency processing device 10 with device ID "M03," and that the data size is 100MB. It also shows that the program update is instructed to take place on April 1st, but the actual date of the update has not been planned.

[0035] [Server device operation] Figure 7 is a diagram illustrating the operation of the server device 20 in this embodiment using a specific example. Figure 7 shows a case where 10 currency processing units 10 are subject to program update planning. Of these, program update plans have already been created for the two currency processing units 10 enclosed in thick lines, and plans will be created for the remaining 8 currency processing units 10. Furthermore, for these currency processing units 10, the smaller the device ID, the higher the priority for program update.

[0036] Figure 7 includes columns for "Data Volume" and "Number of Unit Time Zones." The "Data Volume" column shows the same data volume as shown in Figure 6. The "Number of Unit Time Zones" column shows the number of unit time zones required to update the data volume in the "Data Volume" column, with each unit time zone being 60 minutes and the unit data volume being 50 MB. Figure 7 shows the program update schedule for each time unit within the update period for April 1st (a business day), April 2nd (a non-business day), and April 3rd and 4th (both business days). As shown in Figure 4, the update period for business days is from 0:00 to 6:00, and the update period for non-business days is from 0:00 to 22:00. Also, as in Figure 6, the instruction update date for all currency processing devices 10 is set to April 1st. Furthermore, the nighttime automatic verification will be performed on April 3rd. In addition, Figure 7 includes a multiplicity column at the bottom row, which shows the number of currency processing units 10 currently scheduled for program updates for each unit of time. The maximum multiplicity is set to 3, as shown in Figure 4.

[0037] The number of time units required to update the program of the currency processing device 10 with device ID "M03" is "2," as shown in the diagram. Since this number of time units is less than the number of time units required for the update on April 1st, the program update will be completed on April 1st. Moreover, regardless of the time of day the program update is performed, the maximum multiplicity will not be exceeded. Therefore, the program update is planned to be performed on April 1st. The program update can be performed at any time, but it is planned to be performed between 0:00 and 2:00, whichever is earliest.

[0038] The number of time units required to update the program of the currency processing device 10 with device ID "M04" is "7," as shown in the diagram. Since this number of time units is greater than the number of time units required for the update on April 1st, the program update will not be completed on April 1st. However, since this number of time units is less than the number of time units required for the update on April 2nd, the program update will be completed on April 2nd. Therefore, the program update is planned to be performed on April 2nd.

[0039] The number of time units required to update the program of the currency processing device 10 with device ID "M05" is "4," as shown in the diagram. Since this number of time units is less than the number of time units required for the update on April 1st, the program update will be completed on April 1st. Moreover, performing the program update between 2:00 and 6:00 will not exceed the maximum multiplicity. Therefore, the program update is planned to be performed between 2:00 and 6:00 on April 1st.

[0040] The number of time units required to update the program of the currency processing device 10 with device ID "M06" is "17," as shown in the diagram. Since this number of time units is greater than the number of time units required for the update on April 1st, the program update will not be completed on April 1st. However, since this number of time units is less than the number of time units required for the update on April 2nd, the program update will be completed on April 2nd. Therefore, the program update is planned to be performed on April 2nd.

[0041] The number of time units required to update the program of the currency processing device 10 with device ID "M07" is "1," as shown in the diagram. Since this number of time units is less than the number of time units required for the update on April 1st, the program update will be completed on April 1st. Moreover, if the program update is performed between 5:00 and 6:00, the maximum multiplicity will not be exceeded. Therefore, the program update is planned to be performed between 5:00 and 6:00 on April 1st.

[0042] The number of time units required to update the program of the currency processing device 10 with device ID "M08" is "18," as shown in the diagram. Since this number of time units is greater than the number of time units required for the update on April 1st, the program update will not be completed on April 1st. However, since this number of time units is less than the number of time units required for the update on April 2nd, the program update will be completed on April 2nd. Therefore, the program update is planned to be performed on April 2nd.

[0043] The number of time units required to update the program of the currency processing device 10 with device ID "M09" is "11," as shown in the diagram. Since this number of time units is greater than the number of time units required for the update on April 1st, the program update will not be completed on April 1st. However, since this number of time units is less than the number of time units required for the update on April 2nd, the program update will be completed on April 2nd. Moreover, if the program update is performed after 7:00, the maximum multiplicity will not be exceeded. Therefore, the program update is planned to be performed on April 2nd. The program update can be performed at any time after 7:00 as long as 11 time units can be secured, but it is planned to be performed between 7:00 and 18:00, whichever is earliest.

[0044] The number of time units required to update the program of the currency processing device 10 with device ID "M10" is "6," as shown in the diagram. This number of time units is less than the number of time units required for the update on April 1st, but it exceeds the maximum multiplicity regardless of when the program update is performed. Furthermore, this number of time units is less than the number of time units required for the update on April 2nd, but it exceeds the maximum multiplicity regardless of when the program update is performed. In addition, April 3rd is a nighttime automatic scrutiny day, so the program update cannot be performed on that day. Therefore, the program update is planned to be performed on April 4th.

[0045] In other words, in this embodiment, the server device 20 automatically creates a program update plan for each currency processing device 10 using the update time period, data volume, and maximum concurrency as conditions, and these conditions include the nighttime automatic review day for each currency processing device 10.

[0046] Furthermore, after the program update plan shown in Figure 7 is created, the server device 20 may also receive automatic verification information from the currency processing device 10. Here, for example, let's assume that the server device 20 receives automatic verification information indicating that an automatic nighttime verification will be performed on April 1st. As a result, for example, the program update for the currency processing device 10 with device ID "M05" will be automatically scheduled to skip its originally planned date of April 1st and instead be allocated to an available time slot from April 2nd onwards.

[0047] Figure 8 shows an example of program update information stored in the program update information storage unit 223 after the operation of the server device 20, as shown by a specific example in Figure 7, has been performed. As shown in the figure, the program update information stores the time period indicated in Figure 7 as the time when the program update will be performed as the update date and time for device IDs "M03" to "M10", and stores "ON" as the planned flag.

[0048] Figure 9 is a flowchart showing an example of the operation of the server device 20 in this embodiment.

[0049] First, in the server device 20, the operation reception unit 211 determines whether the user has performed an operation to instruct the creation of a program update plan using the operation unit 24 (step 201). If it is not determined in step 201 that the user has performed an operation to instruct the creation of a program update plan, the operation reception unit 211 repeats the process of step 201. If it is determined in step 201 that the user has performed an operation to instruct the creation of a program update plan, the setting information acquisition unit 212 acquires setting information from the setting information storage unit 221 (step 202). Specifically, the setting information acquisition unit 212 acquires the unit time period, unit data volume, maximum multiplicity, business day update time period, holiday update time period, etc. Next, the priority determination unit 213 determines the priority order for updating the programs of the multiple currency processing devices 10 (step 203). Specifically, the priority determination unit 213 determines the priority order for updating the programs of the currency processing devices 10 for which the planned flag in the program update information storage unit 223 is "OFF".

[0050] Next, the control unit 21 focuses on the currency processing device 10 with the highest priority among the unprocessed currency processing devices 10, based on the priority determined in step 203 (step 204), and performs the processing in steps 205 to 207. Specifically, the automatic verification information acquisition unit 214 first acquires automatic verification information related to the currency processing device 10 that was identified in step 204 from the automatic verification information storage unit 222 (step 205). In particular, the automatic verification information acquisition unit 214 acquires the nighttime automatic verification date corresponding to the currency processing device 10 that was identified in step 204. Next, the program update information acquisition unit 215 acquires program update information related to the currency processing device 10 that was identified in step 204 from the program update information storage unit 223 (step 206). Specifically, the program update information acquisition unit 215 acquires the data amount and the instructed update date corresponding to the currency processing device 10 that was identified in step 204. Next, the update plan creation unit 216 executes an update plan creation process (step 207) to create a program update plan using the configuration information obtained in step 202, the automatic verification information obtained in step 205, the program update information obtained in step 206, etc. Details of the update plan creation process will be described later.

[0051] Subsequently, the control unit 21 determines whether there are any unprocessed currency processing devices 10 (step 208). If it is determined in step 208 that there are unprocessed currency processing devices 10, the control unit 21 returns the process to step 204. If it is not determined in step 208 that there are any unprocessed currency processing devices 10, the control unit 21 terminates the process.

[0052] Figure 10 is a flowchart showing the specific details of the update plan creation process in this embodiment.

[0053] First, the update plan creation unit 216 determines the instruction update date included in the program update information obtained in step 206 as a candidate update date (step 251). Next, the update plan creation unit 216 determines whether the candidate update date determined in step 251 matches the nighttime automatic review date included in the automatic review information obtained in step 205 (step 252).

[0054] If step 252 determines that the candidate update date and the nightly automatic review date coincide, the update plan creation unit 216 determines the day after the candidate update date as the new candidate update date (step 253) in order to perform the program update while avoiding the nightly automatic review date, and returns the process to step 252. In this case, in step 252, the update plan creation unit 216 will use the candidate update date determined in step 253 as the candidate update date, rather than the candidate update date determined in step 251.

[0055] If step 252 does not determine that the candidate update date and the nighttime automatic review date match, the update plan creation unit 216 obtains the update time slot for the candidate update date (step 254). Specifically, if the candidate update date is a business day, the update plan creation unit 216 obtains the business day update time slot included in the configuration information obtained in step 202 as the update time slot for the candidate update date. If the candidate update date is a non-business day, the update plan creation unit 216 obtains the non-business day update time slot included in the configuration information obtained in step 202 as the update time slot for the candidate update date. In this case, the update plan creation unit 216 may determine whether the candidate update date is a business day or a non-business day using a calendar common to all banks, or it may determine it using a calendar specific to each bank.

[0056] Next, the update plan creation unit 216 determines whether the program update will be completed within the update time slot of the candidate update date obtained in step 254 (step 255). Specifically, the update plan creation unit 216 calculates the number of unit time slots required for the program update by dividing the amount of data included in the program update information obtained in step 206 by the amount of unit data included in the setting information obtained in step 202. Then, the update plan creation unit 216 determines whether the program update will be completed within the update time slot by comparing this calculated number of unit time slots with the number of unit time slots included in the update time slot obtained in step 254. If the former number of unit time slots is less than or equal to the latter number of unit time slots, the update plan creation unit 216 determines that the program update will be completed within the update time slot; if the former number of unit time slots exceeds the latter number of unit time slots, it does not determine that the program update will be completed within the update time slot.

[0057] If step 255 does not determine that the program update can be completed within the update time frame of the candidate update date, the update plan creation unit 216 determines the day following this candidate update date as the new candidate update date (step 253), and returns the process to step 252. In this case, in step 252, the update plan creation unit 216 will use the candidate update date determined in step 253 as the candidate update date, rather than the candidate update date determined in step 251.

[0058] If step 255 determines that the program update can be completed within the update time slot of the candidate update date, the update plan creation unit 216 determines whether the program update is possible within the maximum multiplicity included in the setting information obtained in step 202 (step 256). Specifically, the update plan creation unit 216 calculates the number of unit time slots required for the program update in the same manner as in step 255. Then, the update plan creation unit 216 searches for available time slots consisting of this calculated number of unit time slots from the update time slot of the candidate update date. Here, an available time slot is a time slot in which, even if a program update is performed, the sum of the number of currency processing devices 10 in which the program update is performed for all unit time slots in that time slot does not exceed the maximum multiplicity. The update plan creation unit 216 determines whether the program update is possible within the maximum multiplicity by checking whether such an available time slot can be found. If an available time slot is found, the update plan creation unit 216 determines that the program update is possible within the maximum multiplicity; if no available time slot is found, it does not determine that the program update is possible within the maximum multiplicity.

[0059] If it is not determined in step 256 that a program update is possible within the maximum concurrency, the update plan creation unit 216 determines the day following this candidate update date as a new candidate update date (step 253), and returns the process to step 252. In this case, in step 252, the update plan creation unit 216 will use the candidate update date determined in step 253 as the candidate update date, rather than the candidate update date determined in step 251.

[0060] If it is determined in step 256 that a program update is possible within the maximum concurrency, the update plan creation unit 216 determines the available time slot found in step 256 as the update date and time (step 257). If multiple available time slots are found in step 256, the update plan creation unit 216 may, for example, use the earliest available time slot as the update date and time. After that, the update plan creation unit 216 sets the planned flag for the program update information to "ON" (step 258) and returns to the process shown in Figure 9.

[0061] In the above example, the server device 20 automatically created a program update plan to prevent the nightly automatic review date and the program update date from coinciding, but this is not limited to this. The server device 20 may instruct the user to create a program update plan to prevent the nightly automatic review date and the program update date from coinciding. In this case, the server device 20 performs an update plan creation instruction process instead of the update plan creation process in step 207 of Figure 9. In the update plan creation instruction process, for example, the display control unit 217 displays on the display unit 23 that a program update plan should be created if the instructed update date and the nightly automatic review date coincide. Alternatively, the display control unit 217 may display on the display unit 23 that a program update plan should be created only if it receives automatic review information from the currency processing device 10 after a program update plan has been created.

[0062] [Differentiation] In the above, when the nighttime automatic review date and the instructed update date are determined to coincide, the update plan creation unit 216 shifts the program update date and time so that the nighttime automatic review date and the program update date and time do not coincide. However, this is not the only option. When the nighttime automatic review date and the instructed update date are determined to coincide, the automatic review date change unit (not shown) may shift the nighttime automatic review date so that the nighttime automatic review date and the program update date and time do not coincide. In this case, the automatic review date change unit is an example of a processing unit that performs processing to change the first time range so that the first time range and the second time range do not overlap at least partially. Alternatively, if it is determined that the nighttime automatic review date and the instructed update date coincide, the user may be able to set whether to prioritize the nighttime automatic review or the program update. In other words, the control unit 21 may execute the process specified by the user from among the process in which the update plan creation unit 216 shifts the program update date and time, and the process in which the automatic review date change unit (not shown) shifts the nighttime automatic review date. In this case, the control unit 21 is an example of a processing unit that performs processing to change the time range specified by the user from the first time range and the second time range so that the first time range and the second time range do not overlap at least partially.

[0063] In the above, it was stated that the server device 20 may also determine whether the daytime automatic scrutiny date matches the instructed update date, but this is not required. When the server device 20 receives automatic scrutiny information including the daytime automatic scrutiny date and the nighttime automatic scrutiny date from the currency processing device 10, it may determine whether only the nighttime automatic scrutiny date matches the instructed update date. In this case, the first time range is the time range during which the currency processing device performs nighttime automatic scrutiny. Furthermore, the automatic verification may include automatic verification instructed from an operation unit 102 provided on the currency processing device 10, and automatic verification instructed from a remote terminal located far from the currency processing device 10. When the server device 20 receives automatic verification information for both types of automatic verification from the currency processing device 10, it may determine whether the automatic verification date for the latter type of automatic verification matches the instructed update date. In this case, the former type of automatic verification is an example of the first type of automatic verification, and the latter type of automatic verification is an example of the second type of automatic verification. The first time range is the time range in which the currency processing device 10 performs the second type of automatic verification.

[0064] Although not mentioned above, if the timing for automatic scrutiny and program updates is defined by day and time, it may occur that these timings fall on the same day, even if they do not overlap at least partially. In such cases, the control unit 21 should prioritize the program update timing over the automatic scrutiny timing. This is because performing a program update while rejected currency has been generated by automatic scrutiny would create a complex situation.

[0065] In the above example, the server device 20 is assumed to distribute the program to the currency processing device 10 and update it immediately, but this is not the only option. The server device 20 may distribute the program to the currency processing device 10 in advance and update the program at the update date and time set in the program update plan. In that case, the maximum concurrency does not need to be considered when creating the program update plan. Furthermore, while the above describes a scenario where the nightly automatic verification date of the currency processing device 10 and the update date and time of the program for the currency processing device 10 are not to coincide, this is not limited to this. The nightly automatic verification date of the currency processing device 10 and the distribution date and time of the program for the currency processing device 10 may also be to be not to coincide.

[0066] [Effects of the embodiment] In this embodiment, when the time range for automatic inspection of the currency processing device 10 and the time range for updating the program of the currency processing device 10 overlap at least partially, the system is designed so that these time ranges do not overlap at least partially. This increases the likelihood that automatic inspection of the currency processing device 10 can be performed without conflicting with the program update of the currency processing device 10. As a result, the likelihood of avoiding errors in the currency processing unit 10 at the start of the day, for example, at a financial institution's branch, has increased. For example, when the currency processing unit 10 performs an automatic nightly check, it waits for rejected currency to be removed from the reject storage unit 106. If a program update is performed in this state, the currency processing unit 10 will have an error when it starts the next morning. However, if the nightly automatic check and the program update do not conflict, the occurrence of such errors can be suppressed.

[0067] Furthermore, in this embodiment, since the nightly automatic review and program updates no longer conflict, there is no need to redistribute the program, which in turn makes it possible to reduce the amount of data transmitted. [Explanation of symbols]

[0068] 1…Processing system, 10…Currency processing device, 20…Server device, 21…Control unit, 211…Operation reception unit, 212…Setting information acquisition unit, 213…Priority determination unit, 214…Automatic verification information acquisition unit, 215…Program update information acquisition unit, 216…Update plan creation unit, 217…Display control unit, 22…Storage unit, 221…Setting information storage unit, 222…Automatic verification information storage unit, 223…Program update information storage unit, 23…Display unit, 24…Operation unit, 25…Communication unit

Claims

1. A first acquisition unit that acquires a first time range for performing automatic verification of a currency processing device, A second acquisition unit that acquires a second time range for updating the program of the currency processing device, A processing unit that performs predetermined processing to prevent the first time range and the second time range from overlapping, when the first time range and the second time range overlap at least partially. Equipped with, The processing system is a process that outputs information indicating that at least one of the first time range and the second time range should be changed.

2. A first acquisition unit that acquires a first time range for performing automatic verification of a currency processing device, A second acquisition unit that acquires a second time range for updating the program of the currency processing device, A processing unit that performs predetermined processing to prevent the first time range and the second time range from overlapping, when the first time range and the second time range overlap at least partially. Equipped with, The processing system is characterized by the predetermined processing being, when the second time range is included in the first off-hours period, the processing being to change the second time range to a time range included in the second off-hours period that is later than the first off-hours period.

3. The processing system according to claim 2, wherein the second off-hours period is the earliest off-hours period that is later than the first off-hours period and satisfies predetermined conditions indicating that it is possible to perform the program update that was scheduled to be performed within the second time range.

4. The processing system according to claim 3, wherein the predetermined condition is that the off-hours period is longer than the time required to perform the program update that was to be performed within the second time range.

5. The processing system according to claim 4, wherein the length of the non-business hours is a first length on business days and a second length different from the first length on non-business days.

6. The processing system according to claim 3, wherein the predetermined condition is that even if a program update is performed within the second time range, the number of currency processing devices that perform the program update does not exceed the maximum number of currency processing devices that can perform the program update simultaneously.

7. A first acquisition unit that acquires a first time range for performing automatic verification of a currency processing device, A second acquisition unit that acquires a second time range for updating the program of the currency processing device, A processing unit that performs predetermined processing to prevent the first time range and the second time range from overlapping, when the first time range and the second time range overlap at least partially. Equipped with, The processing unit, in a case where the first time range and the second time range do not overlap, and as a result, the first time range and the second time range fall within the same non-business hours period, the processing system places the second time range before the first time range.

8. The steps include: obtaining a first time range in which the computer performs an automated inspection of the currency processing device; The steps include: obtaining a second time range for the computer to perform a program update on the currency processing device; The computer performs a predetermined process to prevent the first time range and the second time range from overlapping if the first time range and the second time range overlap at least partially. Includes, The processing method wherein the predetermined processing is a process that outputs information indicating that at least one of the first time range and the second time range should be changed.

Images