Management device, system, method, and program

Abstract

To provide a management device, system, method and program, which make it more likely that a file is available to a user even in the event of a scanning error.SOLUTION: A management device disclosed herein determines succeeding processing to be temporary disabling when a test result indicates an error type that cannot be expected to be recovered over time, and determines the succeeding processing to be determination of retesting when the detection result indicates an error type that can be expected to be recovered over time.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present invention relates to a management device, a system, a method and a program. [Background technology]

[0002] In recent years, storage services that store files uploaded by users and provide them to users upon request are becoming more and more common. Some storage services have a function for sharing files with other users, and by using this function, users can send or share their own files with other users. Therefore, if an uploaded file is a malicious file infected with a virus, the infection will spread through the storage service. In order to prevent the spread of such secondary damage, virus countermeasures in storage services are becoming increasingly important.

[0003] Virus scanning service companies provide scanning services that can be used with storage services. In one form, scanning software is run on a server installed in the storage service's cloud, and files uploaded by users are scanned with the scanning software on the server. In this form, since the scanning software is included in the cloud, the storage service does not require communication with the scanning service. This form of scanning service is called the offline type. In the other form, a module provided by the scanning service is imported into the cloud, and the module communicates with the scanning service to provide the scanning function. This form of scanning service is called the online type. Furthermore, the online type can be broadly divided into two types based on the method used: a form in which the scanning service provides the scanning function, and a form in which the pattern file update function is provided. The former is called the scanning function providing type, and the latter the pattern file update function providing type.

[0004] In the case of the scan function provision type, the virus scan service company provides the storage service company with a scan service and the function to call it (scan service call function). By incorporating the scan service call function into the storage service, the storage service company is able to use the scan function. On the other hand, in the case of the pattern file update function provision type, the virus scan service company provides a pattern file management service and the function to call it (pattern file update call function). By incorporating the pattern file update call function into the storage service, the storage service company is able to use the scan function with the latest pattern files.

[0005] This online scanning service runs on a cloud service provided by a cloud service platform provider. Cloud services tend to be generally recognized as having high availability, but looking back at past failure histories, it can be seen that they have stopped working with a certain frequency. In other words, if the cloud service stops working, the online scanning service may not be able to provide the scanning service.

[0006] Here, the mechanism by which the storage service allows the user to access the uploaded file is as follows: when a file is uploaded, the storage service generates summary information for the file and presents the summary information to the user. The summary information is file attributes such as the file name and alias, or a proxy file generated from the file. In the case of an image file, it corresponds to a thumbnail image file. The user is able to access the file via the presented summary information. There are two main methods for providing files to users. One is to scan the uploaded file, generate summary information, and provide the summary information. The other is to generate summary information and delete the file if it is found to be an illegal file. In the former case, if a scan error occurs, the user cannot access the file. On the other hand, in the latter case, the user can access the unscanned file, so if it is found to be an illegal file, the illegal file will be unintentionally spread to other users.

[0007] Some scanning services provide error codes as a way to externally observe the status of the scanning service. Depending on the content of the error, there are some errors that can be expected to be recovered over time. By taking appropriate action for errors that can be expected to be recovered over time, it is possible to provide users with an opportunity to access their files.

[0008] As a technique for executing processing according to the scan result, i.e., the inspection result, the technique disclosed in Patent Document 1 is disclosed. In the technique disclosed in Patent Document 1, if the inspection result indicates that the file is an unauthorized file, access from the user is prohibited.

[0009] Furthermore, as a technique for executing processing in response to an error, the technique disclosed in Patent Document 2 is one in which an interface (I / F) is stopped in the event of a communication error, and all I / Fs are stopped in the event of other errors. [Prior art documents] [Patent documents]

[0010] [Patent Document 1] JP 2012-181878 A [Patent Document 2] Japanese Patent Application Publication No. 06-305204 Summary of the Invention [Problem to be solved by the invention]

[0011] However, the technology disclosed in Patent Document 1 allows a user to access a normal file, but prohibits access to the file if it is determined to be unauthorized, and does not disclose or suggest anything about the case of a scan error. Therefore, when a scan error occurs, as described above, the user may be unable to access the file, or unauthorized files may spread unintentionally.

[0012] In addition, in the technology disclosed in Patent Document 2, when a communication error occurs, communication of that I / F is stopped, so when an error occurs in the scan service, communication between the storage service and the scan service is stopped. Furthermore, when an error other than a communication error occurs, all I / F is stopped, so the user is not only unable to access unauthorized files, but is also unable to view normal files.

[0013] The present invention has been made to solve the above-mentioned problems, and aims to provide a management device, system, method, and program that can increase the likelihood that a user can use a file even if a scan error occurs. [Means for solving the problem]

[0014] As one means for achieving the above object, a management device of the present invention has the following configuration: That is, the management device communicates with an inspection device that inspects whether input information input from a terminal is invalid information and manages the input information, and includes an inspection means for generating an inspection result of the input information, a decision means for deciding that subsequent processing of the input information is to be temporarily disabled if the inspection result is a type of result that cannot be recovered over time, and for deciding that subsequent processing of the input information is to be a re-inspection decision processing if the inspection result is a type of result that can be recovered over time, a temporary invalidation means for making the input information temporarily unavailable from outside the management device based on the decision made by the decision means, and a re-inspection decision means for deciding whether to re-inspect the input information based on the decision made by the decision means. Effect of the Invention

[0015] According to the present invention having the above-mentioned configuration, even if a scan error occurs, the possibility that the user can use the file can be increased. [Brief description of the drawings]

[0016] [Figure 1] FIG. 2 is a diagram illustrating an example of an image of a management system. [Diagram 2] FIG. 2 is a diagram illustrating an example of a system configuration of a management system. [Diagram 3] FIG. 2 is a diagram illustrating an example of a hardware configuration of an information processing device. [Figure 4] FIG. 2 is a diagram illustrating an example of a logical configuration of a management system. [Diagram 5] FIG. 11 is a diagram illustrating an example of a process flow in a management system. [Figure 6] FIG. 11 is a diagram illustrating an example of a process flow in a management system. [Figure 7] FIG. 11 is a diagram illustrating an example of a process flow in a management system. [Figure 8] FIG. 13 is a diagram illustrating an example of a table. [Figure 9] FIG. 13 is a diagram showing an example of a reexamination instruction screen. [Figure 10] FIG. 13 is a diagram illustrating an example of a result of a load experiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] Hereinafter, the present invention will be described in detail based on preferred embodiments thereof with reference to the accompanying drawings. Note that the configurations shown in the following embodiments are merely examples, and the present invention is not limited to the configurations shown in the drawings.

[0018] <Embodiment 1> A first embodiment of the present invention will now be described.

[0019] <Image of Management System 100> FIG. 1 is a conceptual diagram of a management system 100 according to an embodiment of the present invention.

[0020] As shown in FIG. 1, the management system 100 includes a personal computer (hereinafter referred to as a PC) 101, a storage service 102, and a scan service 103.

[0021] A user 104 operates the PC 101 and uses the management system 100. The user 104 has an account for the storage service 102.

[0022] Reference numeral 101 denotes a PC that has a communication function and is capable of transmitting a file to a storage service 102. This file becomes input information for the storage service 102.

[0023] A storage service 102 has a communication function and can communicate with external devices such as the PC 101 and a scan service 103. The storage service 102 manages files uploaded by the user from the PC 101. All kinds of files, such as documents, images, videos, audio, and executable files, are accepted.

[0024] A scan service 103 has a communication function and can communicate with the storage service 102 .

[0025] The flow of the management system 100 in this embodiment will be described below.

[0026] A user 104 transmits a file stored in a PC 101 to a storage service 102 .

[0027] The storage service 102 transfers the received file to the scan service 103 and requests inspection.

[0028] The scan service 103 performs an inspection on the received file and transmits the inspection results to the storage service 102 .

[0029] The storage service 102 receives the inspection result, and if the inspection result is normal, generates summary information of the file and allows the user to handle the file via the summary information, whereas if the inspection result is abnormal, the file is moved to a quarantine storage.

[0030] The above is an overview of the management system 100 in this embodiment.

[0031] <System configuration of management system 100> FIG. 2 shows a system configuration of a management system 100 according to an embodiment of the present invention.

[0032] 2, the management system 100 includes a terminal 101, a management device 102, an inspection device 103, and a network 201. The terminal 101, the management device 102, and the inspection device 103 correspond to the PC 101, the storage service 102, and the scan service 103 in FIG.

[0033] The terminal 101, the management device 102, and the inspection device 103 are connected via a network 201. The network 201 is realized by, for example, a LAN (Local Area Network) or the Internet, and enables mutual communication between the connected devices. The terminal 101 will be described as a PC having a communication function, but is not limited to this. Any terminal that can transmit files to the management device, such as a digital camera with interchangeable lenses, a compact digital camera, a smartphone, or a tablet having a communication function, may be used.

[0034] <Hardware configuration of information processing device 300> 3 is a diagram showing an example of a hardware configuration of an information processing device 300 functioning as the terminal 101, the management device 102, and the inspection device 103. The information processing device 300 has a CPU 301, a ROM 302, a RAM 303, a display 304, a keyboard 305, a secondary storage device 306, a network I / F 307, and a pointing device 308, and these components are connected to each other via a bus 309.

[0035] The CPU 301 is an arithmetic processing device that executes programs stored in the ROM 302 and the secondary storage device 306 to control each unit connected via the bus 309. The ROM 302 is a read-only memory that stores an OS and the like. The RAM 303 is a memory that temporarily stores data when the CPU 301 executes arithmetic processing. The display 304 is a display device that displays a UI screen and the like. The keyboard 305 and the pointing device 308 are input devices that allow the user to perform various input operations. The secondary storage device 306 stores various programs, setting value data, a database (DB), captured image data, and the like. The network I / F 307 is an interface for connecting to a network such as a local area network (LAN), an intranet, or the Internet.

[0036] <Logical Configuration of Management System 100> Next, a logical configuration of the management system 100 according to the present embodiment will be described with reference to Fig. 4. Note that since the terminals are general PCs, smartphones, tablets, etc., a description thereof will be omitted.

[0037] <Logical configuration of terminal 101> In the terminal 101, the CPU 301 loads a program stored in the ROM 302 into the RAM 303 and executes processes in accordance with sequence diagrams and flowcharts described later. The results of each process are then stored in the RAM 303.

[0038] The terminal 101 has a control unit 401, an input unit 402, a storage unit 403, an output unit 404, and a communication unit 405. Each functional unit will be described below.

[0039] Reference numeral 401 denotes a control unit that controls each component of the terminal 101 .

[0040] Reference numeral 402 denotes an input unit that accepts input from the user.

[0041] Reference numeral 403 denotes a storage unit for storing a program for transmitting a file to the management apparatus 102, a file to be transmitted to the management apparatus 102, an input from a user, and the like.

[0042] Reference numeral 404 denotes a display unit for displaying an input screen for a program for transmitting a file to the management apparatus 102, a transmission result, summary information of the file on the management apparatus 102, and the like.

[0043] Reference numeral 405 denotes a communication unit that communicates with the management device via a program for transmitting files to the management device 102. The communication unit 405 transmits a file designated by a user, receives list information of files managed by the management device 102, transmits operations on files managed by the management device 102, receives operation results, and the like.

[0044] <Logical configuration of management device 102> In the management device 102, the CPU 301 loads a program stored in the ROM 302 into the RAM 303 and executes processes in accordance with sequence diagrams and flowcharts described below, thereby realizing the above. Then, the RAM 303 stores the results of each process.

[0045] The management device 102 has a storage unit 411, an inspection unit 412, an inspection request unit 413, a decision unit 414, a validation unit 415, a temporary invalidation unit 416, a temporary information storage unit 417, a re-inspection decision unit 418, an invalidation unit 419, an incorrect information storage unit 420, a re-inspection instruction unit 421, an inspection history holding unit 422, and a registration unit 423. Each functional unit will be described below.

[0046] Reference numeral 411 denotes a storage unit that stores a file received from the terminal 101. When the storage unit 411 executes storage, it issues an event when the storage is executed. When an event is issued, a processing block that is set to receive the issued event can receive a notification of the event.

[0047] An inspection unit 412 requests an inspection request unit 413 to inspect a received file and generates an inspection result from the request result.

[0048] An inspection request unit 413 requests the inspection device 103 to inspect a file and returns the result of the request to the inspection unit 412 .

[0049] A decision unit 414 decides the subsequent processing based on the inspection result.

[0050] Reference numeral 415 denotes a validation unit that validates a file.

[0051] Reference numeral 416 denotes a temporary invalidation section for temporarily making a file unavailable.

[0052] Reference numeral 417 denotes a temporary information storage unit that stores temporarily invalidated files.

[0053] A recheck decision unit 418 decides whether or not to check the file again.

[0054] 419 is an invalidation unit that invalidates a file.

[0055] Reference numeral 420 denotes an illegal information storage unit that stores illegal files.

[0056] Reference numeral 421 denotes a reexamination instruction unit that receives an instruction for reexamination.

[0057] Reference numeral 422 denotes an inspection history storage unit that stores the history of inspections.

[0058] A registration unit 423 registers a file in the management device.

[0059] <Logical configuration of inspection device 103> In the inspection device 103, the CPU 301 loads a program stored in the ROM 302 into the RAM 303 and executes processes in accordance with sequence diagrams and flowcharts described later. Then, the results of each process are stored in the RAM 303.

[0060] The inspection device 103 includes an inspection execution unit 431 .

[0061] Reference numeral 431 denotes an inspection execution unit that receives a file inspection request from the management apparatus 102 and executes the inspection.

[0062] The functional units of the terminal 101, management device 102, and inspection device 103 may be distributed among multiple terminals or information processing devices. When the functions are distributed among multiple information processing devices, they are connected by a LAN or the like so as to be able to communicate with each other, and cooperate to perform a series of processes described below.

[0063] <Sequence of the management system 100> Next, the flow of processing in the management system 100 will be described with reference to the sequence diagrams shown in FIGS.

[0064] In step S101, the terminal 101 accepts an instruction to upload a file from the user 104. The instruction to upload is given by pressing an upload execution button displayed on the terminal, pressing a key on the keyboard, touching a touch panel, voice input from a microphone, etc. Alternatively, the instruction may be input from a controller or smartphone connected to the terminal 101 by wire or wirelessly, by pressing a shutter button provided on the terminal 101, uploading after a predetermined time has elapsed using a timer function, etc. Any method other than the above may be used as long as it can give an instruction.

[0065] In step S 102 , the terminal 101 transmits the file designated by the user 104 to the storage unit 411 based on an instruction from the user 104 .

[0066] In step S103, the storage unit 411 stores the received file and notifies the inspection unit 412 that the file has been stored.

[0067] In step S104, upon receiving the notification from the storage unit 411, the inspection unit 412 instructs the inspection request unit 413 to generate an inspection request for the file.

[0068] In step S105, the inspection request unit 413 requests the inspection execution unit 431 to inspect the file.

[0069] If the test result indicates that the device is normal, steps S106 to S112 are executed.

[0070] In step S106, the inspection execution unit 431 executes the inspection of the requested file.

[0071] In step S 107 , the inspection execution unit 431 transmits the inspection result to the inspection request unit 413 .

[0072] In step S 108 , the inspection request unit 413 transmits the received inspection results to the inspection unit 412 .

[0073] In step S109, the inspection unit 412 generates an inspection result in a format acceptable to the determination unit 414 from the received inspection result, and transmits the generated inspection result to the determination unit 414.

[0074] In step S110, the determination unit 414 instructs the validation unit 415 to validate the file that has been inspected. Specifically, this refers to generating summary information of the file and making the file accessible to the user 104 via the summary information.

[0075] In step S111, the validation unit 415 instructs the registration unit 423 to register the attribute information of the file.

[0076] In step S112, the registration unit 423 registers the attribute information of the received file in the database.

[0077] If the check results in a determination of fraud, steps S113 to S121 are executed.

[0078] In step S113, the inspection execution unit 431 executes the inspection of the requested file.

[0079] In step S 114 , the inspection execution unit 431 transmits the inspection result to the inspection request unit 413 .

[0080] In step S 115 , the inspection request unit 413 transmits the received inspection results to the inspection unit 412 .

[0081] In step S116, the inspection unit 412 transmits the inspection result to the determination unit 414.

[0082] In step S117, the determining unit 414 instructs the invalidation unit 419 to invalidate the file that is the subject of the inspection. Specifically, this means making the file inaccessible to the user 104.

[0083] In step S118, the invalidation unit 419 instructs the registration unit 423 to cancel the registration of the file.

[0084] In step S119, if an entry for the file exists in the database, the registration unit 423 cancels the registration.

[0085] In step S120, the invalidation unit 419 instructs the storage unit 411 to delete the file.

[0086] In step S121, the storage unit 411 deletes the file.

[0087] If the inspection results in a determination that the error is not recoverable, steps S201 to S214 are executed.

[0088] In step S201, the inspection request unit 413 transmits an error code indicating a deployment error or a license error, that is, an error code indicating an error that is unlikely to be recovered, as an inspection result to the inspection unit 412. Note that a deployment error is an error that occurs when the inspection request unit 413 is not operating. Also, a license error is an error that occurs when the authority to use the inspection device 103 is not held.

[0089] In step S202, the inspection unit 412 transmits the inspection result to the determination unit 414.

[0090] In step S203, the determination unit 414 instructs the temporary invalidation unit 416 to temporarily invalidate the file that was the subject of the inspection. The temporary invalidation process does not completely prevent the user from accessing the file in the future, but rather provides a leeway for the user to access the file if the file is reinspected and determined to be normal.

[0091] In step S204, the temporary invalidation unit 416 instructs the registration unit 423 to cancel the registration of the file.

[0092] In step S205, if there is an entry for the file in the database, the registration unit 423 cancels the registration. As a result, the summary information linked to the file is deleted, and the summary information becomes unavailable to the user. In other words, the file cannot be accessed via the summary information.

[0093] In step S206, the temporary invalidation unit 416 instructs the storage unit 411 to move the file to the temporary information storage unit 417.

[0094] In step S207, the storage unit 411 moves the file to the temporary information storage unit 417.

[0095] In step S208, the temporary invalidation unit 416 instructs the reexamination instruction unit 421 to check whether or not a reexamination instruction has been issued from the system administrator of the management apparatus 102.

[0096] In step S209, the reexamination instruction unit 421 checks whether or not a reexamination instruction has been issued from the system administrator. Details of the UI (user interface) in the reexamination instruction unit 421 will be described later with reference to FIG.

[0097] In step S210, the re-examination instruction unit 421 instructs the inspection unit 412 to re-examine the file.

[0098] In step S211, the inspection unit 412 instructs the inspection history storage unit 422 to store the inspection history.

[0099] In step S212, the inspection history holding unit 422 holds the inspection history. In step S213, the inspection unit 412 re-inspects the file. The process in this step is to input the file to be re-inspected to the inspection unit 412. This process corresponds to an event of a component that calls the inspection unit 412 being fired, and the inspection unit 412 being called with the file identifier of the inspection target. That is, this causes the inspection unit 412 to act in the same way as in step S103. The process after the file to be re-inspected is input to the inspection unit 412 is the same as in step S104, and therefore a description thereof will be omitted.

[0100] If the inspection results in a determination that the error is likely to be recoverable, steps S301 to S313 are executed.

[0101] In step S301, the inspection request unit 413 transmits an error code representing an error from which recovery is possible to the inspection unit 412 as an inspection result. Examples of errors from which recovery is possible include a file acquisition error, an internal error, a timeout error, and a throttling error. The file acquisition error is an error that occurs when the inspection execution unit 431 fails to acquire a file to be inspected because the communication path is disconnected or the communication quality is deteriorated when the inspection execution unit 431 acquires a file to be inspected. The internal error is an error that occurs inside the inspection request unit 413 or the inspection execution unit 431. In this case, the processing ends during the inspection request processing. The timeout error is an error that occurs when the inspection request unit 413 is unable to receive the inspection result within a predetermined time after instructing the inspection execution unit 431 to execute the inspection. In other words, it is an error that fails because the time required for the inspection request processing is longer than a predetermined time. The throttling error is an error that occurs when multiple inspection requests occur in a short period of time, and the scaling of the inspection request unit 413 or the inspection execution unit 431 is not in time, and some of the requested inspection requests are not executed. In other words, this is an error that occurs because the parallelism of the computer resources handling the processing of the inspection request exceeds a predetermined parallelism.

[0102] For example, when there are not enough virtual computers running to execute the processing of the inspection request unit 413 or the inspection execution unit 431, if a large number of inspection requests are received in a short period of time, the virtual computers will not be able to start up in time, and some of the inspection requests will fail.

[0103] In step S302, the inspection unit 412 transmits the inspection result to the decision unit 414.

[0104] In step S303, the determination unit 414 instructs the reexamination determination unit 418 to determine whether or not reexamination is required for the file that has been the subject of the examination.

[0105] In step S304, the reexamination determination unit 418 instructs the inspection history holding unit 422 to transmit the inspection history of the file.

[0106] In step S305, the inspection history holding unit 422 transmits the inspection history of the file to the re-inspection deciding unit 418.

[0107] If it is determined from the inspection history that re-inspection has been performed, steps S306 to S309 are executed. In other words, if the number of re-inspections exceeds a predetermined number, it is determined that re-inspection is unnecessary and subsequent processing is invalidated.

[0108] In step S306, the reexamination determination unit 418 instructs the registration unit 423 to cancel the registration of the entry corresponding to the file.

[0109] In step S307, the registration unit 423 releases the entry corresponding to the file.

[0110] In step S308, the reexamination determination unit 418 instructs the temporary invalidation unit 416 to temporarily invalidate the file.

[0111] In step S309, the temporary invalidation unit 416 executes temporary invalidation of the file. This process is similar to step S203 in which the temporary invalidation unit 416 receives a temporary invalidation instruction from the determination unit 414, and therefore a description thereof will be omitted.

[0112] If it is determined from the inspection history that the file has not been reinspected, steps S310 to S313 are executed. In other words, if the number of times the file has been reinspected is equal to or less than a predetermined number, it is determined that the file needs to be reinspected, and the subsequent process is determined to be inspection.

[0113] In step S310, the re-examination decision unit 418 instructs the examination unit 412 to examine the file.

[0114] In step S311, the inspection unit 412 instructs the inspection history storage unit 422 to store the inspection history.

[0115] In step S312, the inspection history storage unit 422 stores the inspection history.

[0116] In step S313, the inspection unit 412 inspects the file. The process after the file to be inspected is input to the inspection unit 412 is the same as in step S104, and therefore a description thereof will be omitted.

[0117] In this embodiment, the inspection request unit 413 requests the inspection execution unit 413 to inspect a file, but this is not limited to this. For example, virus patterns of typical malicious files and frequently occurring malicious files are stored internally. Then, if the received file matches these, an inspection request is not made to the inspection device 103, but an inspection result is generated and transmitted to the inspection unit 412. With this configuration, it is possible to reduce the dependency on the inspection device 103, and therefore the frequency of occurrence of scan errors.

[0118] In this embodiment, the inspection unit 412 generates an inspection result in a format acceptable to the determination unit 414 from the received inspection result, but this is not limited to this. For example, if the received inspection result is in a format acceptable to the determination unit 414, the inspection result may be directly transmitted to the determination unit 414.

[0119] In this embodiment, the error that cannot be recovered from is defined as a deployment error or a license error, but this is not limited to this, and it may be defined as only a license error.

[0120] In addition, examples of errors that can be recovered from include, but are not limited to, file acquisition errors, internal errors, timeout errors, and throttling errors. Errors that can be recovered from may also include an excess or shortage of arguments when calling the scan service, argument inconsistencies (a value different from the specifications is set), and an inability to read a configuration file referenced by the scan service. Errors that can be recovered from may also include an inability to open a log file that records the processing history of the scan service, and an inability to properly specify a file to be inspected. Such a configuration makes it possible to handle scan services with such error systems.

[0121] In this embodiment, in the case of a license error, the system administrator is prompted to select whether or not to recheck, but the present invention is not limited to this. A notification may also be sent to license management personnel, such as the legal department of the company that operates the management device 102. Also, a notification may be sent to check whether the license contract period has expired. With this configuration, it is possible to notify license management personnel directly, rather than contacting license management personnel via the system administrator. This makes it possible to deal with license problems more quickly and shorten the period during which users cannot access files.

[0122] In this embodiment, in the event of a deployment error, the system administrator is notified, but it may also be possible to notify the deployment person in the development department that operates the management device 102. With this configuration, the deployment person can be notified directly, rather than contacting the deployment person via the system administrator, so that problems related to deployment can be dealt with more quickly and the period during which users are unable to access files can be shortened.

[0123] In this embodiment, the necessity of retesting is determined when a timeout error or a throttling error occurs, but a process of suppressing the occurrence of both errors may be performed by detecting a sign of the occurrence of both errors. For example, the processing time of each computer resource per unit time of the test request unit 418 is monitored, and when the time difference of the processing times exceeds a predetermined value, the computer resource that processes the test request unit 418 is scaled out. This makes it possible to suppress the occurrence of both errors. This is based on the results of an experiment conducted by the inventor of the present invention. The results of this experiment will be described later with reference to FIG. 10.

[0124] Alternatively, the processing time of each computer resource per unit time of the storage unit 411 is monitored, and when the time differential of the processing time exceeds a predetermined value, the computer resource that processes the inspection request unit 418 is scaled out. This makes it possible to suppress the occurrence of both types of errors.

[0125] In this embodiment, an example of scale-out has been shown for suppressing the occurrence of errors in the inspection request unit 418, but the present invention is not limited to this. When a sign of an error occurrence is detected, a lightweight file may be input to the inspection request unit 418 to keep the computer resources running. With such a configuration, it is possible to reduce cold starts of computer resources, and as a result, it is possible to suppress the occurrence of errors.

[0126] In this embodiment, the determination unit 414 determines the subsequent process by branching the process, but the present invention is not limited to this. The subsequent process may be determined by using a correspondence table that associates the error code of the inspection result with the subsequent process. An example of the correspondence table will be described later with reference to FIG. 8(d). By using the error code table 504 in FIG. 8(d), the process branch can be determined with less calculation amount than by branching the process.

[0127] Next, the tables managed by the management device 102 according to this embodiment will be described with reference to FIG. 8(a) and FIG. 8(b).

[0128] Reference numeral 501 denotes a user table managed by the management device 102 .

[0129] By storing a user ID for uniquely identifying a user in association with the registration date when the user completed user registration in the management device 102 and a login ID for logging in, the registration date and login ID can be referenced using the user ID as a key.

[0130] Reference numeral 502 denotes a file table managed by the management device 102 .

[0131] The file ID for uniquely identifying a file is stored in association with the user ID of the file's owner, the upload date of the file, the file name of the file, the file type of the file, and the image reference destination in the storage unit. This makes it possible to refer to the user ID, upload date, file name, file type, and image reference destination using the file ID as a key.

[0132] Reference numeral 503 denotes an examination history table managed by the management apparatus 102 .

[0133] By associating and storing, in a file ID for uniquely identifying a file, an inspection history or the like that stores the number of times the file has been reinspected, the inspection history can be referenced using the file ID as a key.

[0134] 504 is an error code table managed by the management device 102.

[0135] By associating, with an error code for uniquely identifying an error code included in an inspection result, an identifier of a function for executing subsequent processing corresponding to the error code, the identifier of the function for executing subsequent processing can be referenced using the error code as a key.

[0136] <Configuration of UI> Next, with reference to FIG. 9, a management screen generated by the management device 102 according to the present embodiment will be described.

[0137] 601 is a reinspection instruction screen generated for a system administrator who manages the management device 102. It is displayed on a display device connected to the management device 102 or an information processing device connected via the network 201.

[0138] 602 is a text area that displays, together with the number of temporarily disabled files, a message prompting the selection of execution / non-execution of reinspection.

[0139] 603 is a list of temporarily disabled files that displays a list of temporarily disabled files together with the error type.

[0140] 604 is an OK button that receives an instruction from the user regarding the execution of reinspection. When the pressing of the OK button 604 is received, the management device 102 advances the process to step S210.

[0141] 605 is a cancel button that receives an instruction from the user regarding the non-execution of reinspection. When the pressing of the cancel button 605 is received, the management device 102 ends the iterative process of instruction acquisition, that is, the standby.

[0142] <Load test results> Next, the results of a load experiment conducted by the inventor of the present invention will be described with reference to FIGS. 10(a) and 10(b).

[0143] Reference numeral 701 denotes a graph showing the occurrence of errors in the inspection request unit 413 when a concentrated load is applied to the management apparatus 102. The horizontal axis indicates time, and the vertical axis indicates the number of errors. 1000 users were made to upload 1000 files at the same time.

[0144] Reference numeral 702 denotes the transition of the number of files input to the inspection request unit 413 .

[0145] Reference numeral 703 denotes the transition of the processing time of each computer resource per unit time of the inspection request unit 413 .

[0146] Reference numeral 704 denotes the transition of the number of errors that occurred in the inspection request unit 413 .

[0147] According to 703 and 704, after 703 increases sharply, 704 takes on a value following it. In other words, errors start to occur with a sudden increase in the processing time of each computer resource per unit time. This shows that the occurrence of an error can be predicted by using a sudden increase in the processing time of each computer resource per unit time as a precursor.

[0148] Next, reference numeral 711 denotes a graph showing the occurrence of errors in the storage unit 411 when a concentrated load is applied to the management device 102. The horizontal axis indicates time, and the vertical axis indicates the number of errors. 1000 users were made to upload 1000 files at the same time.

[0149] 712 indicates the transition of the number of files input to the storage unit 411.

[0150] Reference numeral 713 denotes the transition of the processing time of each computer resource per unit time in the storage unit 411 .

[0151] Numeral 714 indicates the transition of the number of errors that occurred in the storage unit 411 .

[0152] According to 713 and 714, after 713 increases sharply, 714 has a value following it. In other words, errors start to occur with a sudden increase in the processing time of each computer resource per unit time. This shows that the occurrence of an error can be predicted by using a sudden increase in the processing time of each computer resource per unit time as a precursor.

[0153] According to the technology described above, files are saved as much as possible in accordance with the inspection results, so that it is possible to prevent users from becoming unable to access files.

[0154] Specifically, if the inspection result is a type of result that cannot be recovered over time, the subsequent process is determined to be a temporary invalidation process. Also, if the inspection result is a type of result that can be recovered over time, the subsequent process is determined to be a re-inspection process. Therefore, even if a scan error occurs, the possibility of determining that the file is normal can be increased.

[0155] <Other embodiments> Although the embodiment has been described above in detail, the present invention can be embodied as, for example, a system, an apparatus, a method, a program, or a recording medium (storage medium), etc. Specifically, the present invention may be applied to a system composed of multiple devices (for example, a host computer, an interface device, an imaging device, a Web application, etc.), or may be applied to an apparatus composed of a single device.

[0156] Needless to say, the object of the present invention can be achieved by the following: That is, a recording medium (or storage medium) on which is recorded a program code (computer program) of software that realizes the functions of the above-mentioned embodiments is supplied to a system or device. Needless to say, such a storage medium is a computer-readable storage medium. Then, a computer (or a CPU or MPU) of the system or device reads and executes the program code stored in the recording medium. In this case, the program code itself read from the recording medium realizes the functions of the above-mentioned embodiments, and the recording medium on which the program code is recorded constitutes the present invention. [Explanation of symbols]

[0157] 100 Management Systems 101 PCs / terminals 102 Storage service / management device 103 Scanning services / Inspection equipment 104 users 201 Network 301 CPU 302 ROM 303 RAM 304 Display 305 Keyboard 306 Secondary storage device 307 Network Interface 308 Pointing Device 309 Bus 401 Control section 402 Input section 403 Storage section 404 Output section 405 Communications Department 411 Storage Department 412 Inspection Department 413 Inspection Request Department 414 Decision Section 415 Enabling Department 416 Temporary Invalidation Section 417 Temporary Information Storage Department 418 Re-examination Decision Division 419 Nullification Section 420 Fraudulent Information Storage Department 421 Re-examination Instructions Department 422 Inspection history storage unit 423 Registration Department 431 Inspection Execution Department 501 User Table 502 File Table 503 Inspection History Table 504 Error Code Table 601 Retest instruction screen 602 Text Area 603 Temporary Invalidation File List 604 OK button 605 Cancel button 701 Graph showing error occurrence status 702 Change in the number of files entered 703 Transition of processing time of each computer resource per unit time 704 Changes in the number of errors that occurred 711 Graph showing error occurrence status 712 Change in the number of files entered 713 Transition of processing time of each computer resource per unit time 714 Changes in the number of errors that occurred

Claims

1. A management device that communicates with an inspection device that inspects whether or not input information input from a terminal is invalid, and manages the input information, A verification means for generating a verification result of the input information; If the inspection result is a result of a type that cannot be recovered over time, it is determined that subsequent processing on the input information is to be temporarily disabled; a determination means for determining that a subsequent process for the input information is a re-examination process when the inspection result is a type of result that can be expected to be recovered over time; a temporary invalidation means for temporarily disabling the input information from outside the management device based on the determination by the determination means; a recheck decision means for deciding whether or not to check the input information again based on the decision made by the decision means; A management device comprising:

2. The management device according to claim 1, characterized in that the decision means decides to temporarily disable subsequent processing of the input information when the inspection result is an error that occurs when the management device does not have authority to use the inspection device.

3. Further, an inspection requesting means for requesting the inspection device to inspect the input information is provided, 2. The management device according to claim 1, wherein the determination means determines to temporarily disable subsequent processing of the input information when the inspection result indicates an error that occurs when the inspection request means is not operating.

4. The inspection requesting means is configured to request the inspection device to inspect the input information, and the determining means determines whether the inspection result is an error that occurs when the inspection request means cannot acquire the input information; An error that occurs when the inspection requesting means ends processing during the request processing; The management device described in claim 1, characterized in that when at least one of the following errors occurs: an error occurs when the time required for the requested processing by the inspection request means is greater than a predetermined time and the processing fails because the parallelism of the inspection request means is greater than a predetermined parallelism and the processing fails, the management device determines that subsequent processing of the input information should be re-inspected.

5. The apparatus further includes a storage unit for storing summary information associated with the input information, The management device according to claim 1 , wherein the temporary invalidation means makes it impossible to use summary information linked to the input information.

6. The retest decision means determines that retesting is necessary when the number of retests for the input information is equal to or less than a predetermined number, and decides that a subsequent process is to be a test; 2. The management device according to claim 1, wherein, when the number of retests for the input information exceeds a predetermined number, it is determined that retesting is unnecessary and subsequent processing is invalidated.

7. The management device according to claim 1, further comprising a re-examination instruction means for receiving a re-examination instruction from a system administrator, waiting for processing until the re-examination instruction is input, and performing re-examination when the re-examination instruction is input.

8. A management method for managing input information by communicating with an inspection device that inspects whether or not input information input from a terminal is invalid, comprising the steps of: an inspection step for generating an inspection result of the input information; If the inspection result is a result of a type that cannot be recovered over time, it is determined that subsequent processing on the input information is to be temporarily disabled; a determining step of determining that a subsequent process for the input information is a re-examination process if the inspection result is a type of result that can be expected to be recovered over time; a temporary invalidation step of temporarily disabling the input information from outside the management device based on the determination made in the determination step; a recheck decision step for deciding whether or not to check the input information again based on the decision made by the decision step; A management method comprising:

9. A program for causing a computer to function as the management device according to any one of claims 1 to 7.

Images