Information management device, information management method, program, and information management system

Abstract

This suppresses requests to generate unnecessary summary information. [Solution] An information management device manages data and has: request means for requesting a summary generation device that generates summary information to generate summary information of the data; deletion means for deleting the data; and re-request control means for controlling the summary generation device to re-request generation of summary information of the data depending on the type of response to the request and the existence of the data. If the type of response is a failure to acquire data by the summary generation device and the data exists, the re-request control means controls to re-request the summary generation device to generate summary information of the data if the type of response is a failure to acquire data by the summary generation device but the data does not exist, and controls not to re-request the summary generation device to generate summary information of the data if the type of response is a failure to acquire data by the summary generation device but the data does not exist.

Description

Technical Field

[0001] The present disclosure relates to an information management device, an information management method, a program, and an information management system.

Background Art

[0002] There is an image management cloud service that manages images uploaded from a user's camera. The image management cloud service generates summary information of an image, which is information capable of determining what kind of image the image to be managed, such as a thumbnail, shooting information, and feature amounts of the image, and presents it to the user. In this type of image management cloud service, generation and the like may fail. In this regard, Patent Document 1 discloses a technique for performing processing according to the type of failure.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] <x By the way, a reference destination of an image managed by an image management cloud service is notified to a summary information generation MS (Micro Service: hereinafter referred to as MS) in which generation of summary information is microserviced to generate summary information of the image. And a configuration in which the generated summary information of the image is used in the image management cloud service can be considered.

[0005] In such a configuration, when the summary information generation MS fails to acquire the reference destination image due to an interruption in communication with the image management cloud service, the summary information generation MS is made to retry acquiring the reference destination image.

[0006] However, referenced images may be deleted for the following reasons. The first case is when a virus scanning service verifies the uploaded image for virus infection and deletes the uploaded image if an infection is detected. For example, the first upload may be judged as normal, but a second upload due to multiple instances of the application running may be judged as invalid and deleted. The second case is when the image is deleted due to an issue with another system. In this case, it is recommended to implement a process for when the image is deleted due to an issue with another system, based on the "Design For Failure" principle.

[0007] As in the two cases mentioned above, if the uploaded image is deleted and the summary information generation MS cannot generate summary information, it will result in unnecessary retries being requested from the summary information generation MS.

[0008] This disclosure provides a technology that suppresses the need to generate unnecessary summary information. [Means for solving the problem]

[0009] An information management device according to one aspect of the technology of this disclosure is an information management device for managing data, comprising a request means for requesting a summary generation device that generates summary information to generate summary information of the data, An inspection request means that causes the inspection device to inspect the aforementioned data, and based on the response of the inspection device, The system includes a deletion means for deleting the data, and a re-request control means for controlling the summary generation device to re-request the generation of summary information for the data, depending on the type of response to the request and whether the data exists, wherein the re-request control means controls the summary generation device to re-request the generation of summary information for the data if the type of response is a failure by the summary generation device to acquire the data and the data exists, and controls the summary generation device not to re-request the generation of summary information for the data if the type of response is a failure by the summary generation device to acquire the data but the data does not exist. [Effects of the Invention]

[0010] The technology described herein can suppress the need to generate unnecessary summary information. [Brief explanation of the drawing]

[0011] [Figure 1] This diagram shows an overview of the information management system. [Figure 2] This diagram shows an example of the configuration of an information management system. [Figure 3] This diagram shows an example of the terminal's hardware configuration. [Figure 4] This figure shows an example of the hardware configuration of an information processing device. [Figure 5] This figure shows an example of the functional configuration of an information management system. [Figure 6] This is a sequence diagram showing the overall processing flow of the information management system. [Figure 7] This is a sequence diagram showing the overall processing flow of the information management system. [Figure 8] This diagram illustrates the processing flow in an information management device. [Figure 9] This is a flowchart showing the detailed flow of the decision-making process. [Figure 10] This flowchart shows the detailed flow of the error cause classification process. [Figure 11] This flowchart shows the detailed flow of the existence / non-existence determination process. [Figure 12] This is an example of a table. [Figure 13] The figure shows examples of error codes. [Figure 14] This figure shows an example of an error cause classification table. [Figure 15] This figure shows an example of the functional configuration of an information management system. [Figure 16] This is a diagram illustrating the processing flow in an information management device. [Figure 17] This figure shows an example of the functional configuration of an information management system. [Figure 18]It is a diagram showing an example of a performance display screen.

Embodiments for Carrying Out the Invention

[0012] Hereinafter, with reference to the drawings, embodiments for implementing the technology of the present disclosure will be described in detail. Note that the configurations shown in the following embodiments are merely examples, and the embodiments are not limited to the illustrated configurations. Also, the following embodiments do not limit the technology of the present disclosure according to the claims. Not all combinations of the features described in the embodiments are essential as a solution means for the technology of the present disclosure, and a plurality of features may be arbitrarily combined. For the same configuration, the same reference numerals will be used for description. Also, each step (step) in the flowchart will be denoted by prefixing "S" at the beginning.

[0013] <<Embodiment 1>> Hereinafter, the information management system according to this embodiment will be described. <Overview of Information Management System 100> FIG. 1 is a diagram showing an overview of the information management system according to this embodiment. As shown in FIG. 1, the information management system 100 includes a personal computer (hereinafter referred to as PC) 101, a storage server 102, a scan server 103, and a thumbnail generation server 104. The storage server 102 provides an image management cloud service for managing image files and presenting summary information of images to users. The scan server 103 provides a virus scan service for verifying the virus infection of uploaded images and taking measures to prevent users from accessing them if they are infected. The thumbnail generation server 104 corresponds to a summary information generation MS having a summary information generation function for generating summary information of images, and provides a service for generating summary information of images.

[0014] A user 105 having an account on the storage server 102 operates the PC 101 to use the information management system 100. The PC 101 has a communication function and can transmit the file 111 to the storage server 102.

[0015] The storage server 102 has communication capabilities and can communicate with external devices such as the PC 101 and the scan server 103. The storage server 102 manages files 111 uploaded from the PC 101 by user 105. The storage server 102 accepts and manages uploads of all types of files 111 from the PC 101, including documents, images, videos, audio, and executable files.

[0016] The scan server 103 has a communication function and can communicate with the storage server 102. The thumbnail generation server 104 has a communication function and can communicate with the storage server 102.

[0017] The processes performed by the information management system 100 of this embodiment are described below. User 105 operates PC 101 to send files saved on PC 101 to storage server 102. Storage server 102 forwards the received files to scan server 103 and requests an inspection. Scan server 103 performs an inspection on the received files and sends the inspection results to storage server 102.

[0018] The storage server 102 receives the inspection results and determines whether the inspection results are normal or not. If the storage server 102 determines that the inspection results are normal, it requests the thumbnail generation server 104 to generate summary information for the files.

[0019] When the thumbnail generation server 104 receives a request from the storage server 102 to generate file summary information, it generates the file summary information and notifies the storage server 102 of the location where the generated file summary information is stored.

[0020] When the storage server 102 receives a notification from the thumbnail generation server 104 indicating the location of the file summary information, it retrieves the file summary information from the location of the file summary information indicated in the received notification.

[0021] <Information Management System> Figure 2 shows an example configuration of the information management system according to this embodiment. As shown in Figure 2, the information management system 200 includes a terminal 201, an information management device 202, an inspection device 203, a summary information generation device (summary generation device) 204, and a network 205. The terminal 201, information management device 202, inspection device 203, and summary information generation device 204 correspond to the PC 101, storage server 102, scan server 103, and thumbnail generation server 104 in Figure 1, respectively.

[0022] Terminal 201, information management device 202, inspection device 203, and summary information generation device 204 are connected via network 205 to enable the sending and receiving of files. Network 205 is implemented, for example, as a LAN (Local Area Network) or the Internet, and enables mutual communication between connected devices. Although terminal 201 is described as a PC with communication capabilities as an example, it is not limited to this. Terminal 201 can be any terminal device that has communication capabilities, such as an interchangeable-lens digital camera, compact digital camera, smartphone, or tablet, as long as it can send files to the information management device 202.

[0023] <Terminal Hardware Configuration> Figure 3 shows an example of the hardware configuration of terminal 201. Terminal 201 includes a CPU 301, ROM 302, RAM 303, display 304, input unit 305, secondary storage device 306, network interface 307, and imaging unit 308. These units are connected to each other via a bus 309 so that data can be sent and received from each other. Examples of terminal 201 include interchangeable-lens digital cameras and compact digital cameras, but are not limited to these; smartphones and tablet terminals with camera functions may also be used.

[0024] The CPU (Central Processing Unit) 301 is an arithmetic processing unit that controls various parts connected via the bus 309 by loading programs stored in the ROM 302 and secondary storage device 306 into the RAM 303 and executing them. The ROM (Read Only Memory) 302 is a read-only memory that stores the OS (Operating System) and other data. The RAM 303 is a random access memory that temporarily stores data when the CPU 301 performs arithmetic processing. The display 304 is a display device that displays information necessary for the user, such as images obtained through imaging and various UI screens. The input unit 305 consists of buttons, a touch panel, a microphone, etc., and is an input device that accepts various user operations such as imaging instructions and various setting instructions. The secondary storage device 306 stores various programs, captured image data, and setting values ​​of imaging settings included in the accompanying information. The imaging settings include ISO sensitivity, shutter speed, exposure compensation, and F-number.

[0025] The network interface 307 is an interface for connecting to networks such as local area networks (LANs), intranets, and the internet. The imaging unit 308 is a module that converts light received by an image sensor such as a CCD (Charge Coupled Device) or CMOS (Complementary Metal Oxide Semiconductor) into electrical signals and records them as images.

[0026] <Hardware configuration of the information processing device> Figure 4 shows an example of the hardware configuration of an information processing device 400 that functions as an information management device 202, an inspection device 203, and a summary information generation device 204. The information processing device 400 includes a CPU 401, ROM 402, RAM 403, a display 404, a keyboard 405, a secondary storage device 406, a network I / F 407, and a pointing device 408. These components are connected to each other via a bus 409 so that data can be sent and received from each other.

[0027] The CPU 401 is an arithmetic processing unit that controls various parts connected via the bus 409 by loading programs stored in the ROM 402 and secondary storage device 406 into the RAM 403 and executing them. The ROM 402 is a read-only memory that stores the OS and other data. The RAM 403 is a random access memory that temporarily stores data when the CPU 401 performs arithmetic processing. The display 404 is a display device that displays UI screens and the like. The keyboard 405 and pointing device 408 are input devices for the user to perform various input operations. The secondary storage device 406 stores various programs, setting value data, databases (DB), and captured image data. The network interface 407 is an interface for connecting to networks such as local area networks (LANs), intranets, and the Internet.

[0028] <Functional Configuration of Information Management System> Figure 5 shows an example of the functional configuration of the information management system according to this embodiment. ≪Device Functional Configuration≫ This is achieved when the CPU 301 of terminal 201 loads the program stored in ROM 302 into RAM 303 and executes the processing according to the sequence diagram and flowchart described later. The results of each process are stored in RAM 303.

[0029] Terminal 201 includes a control unit 501, an input unit 502, a storage unit 503, a display unit 504, and a communication unit 505. Each functional unit will be described below. Note that each functional unit may perform some of the functions of other functional units.

[0030] The control unit 501 controls each component of the terminal 201. The input unit 502 receives input from the user. The storage unit 503 stores the program for sending images to the information management device 202, the images to be sent to the information management device 202, user input, etc. The display unit 504 displays the input screen for sending images to the information management device 202, the transmission results, summary information of the images on the information management device 202, etc.

[0031] The communication unit 505 exchanges data with the information management device 202 using the network interface 307. It performs tasks such as sending images specified by the user, receiving a list of images managed by the information management device 202, sending operations on images managed by the information management device 202, and receiving the results of those operations.

[0032] ≪Functional Configuration of Information Management Device≫ This is achieved when the CPU 401 of the information processing device 400, which functions as an information management device 202, loads the program stored in the ROM 402 into the RAM 403 and executes the processing according to the sequence diagram and flowchart described later. The results of each process are stored in the RAM 403.

[0033] The information management device 202 includes a control unit 511, an input unit 512, a storage unit 513, an output unit 514, a communication unit 515, a holding unit (data holding unit) 516, a request unit 517, a deletion unit 518, a response receiving unit 519, a decision unit 520, an existence / non-existence determination unit 521, and a re-request unit 522. Each functional unit will be described below. Note that each functional unit may perform some of the functions of other functional units.

[0034] The control unit 511 controls each component of the information management device 202. The input unit 512 receives input from the user. The storage unit 513 stores programs that operate on the information management device 202, inputs from the terminal 201, the inspection device 203, the summary information generation device 204, etc.

[0035] The output unit 514 outputs the processing results from the information management device 202, images held by the holding unit 516, etc. The communication unit 515 exchanges data with the terminal 201, inspection device 203, and summary information generation device 204 using the network interface 407.

[0036] The storage unit 516 stores images (uploaded images) received from the terminal 201, inspection results received from the inspection device 203, summary information acquired from the summary information generation device 204, etc. When the storage unit 516 performs storage, it issues an event triggered by the execution of storage. Processing blocks configured to receive event issuance can receive event notifications when an event is issued.

[0037] The request unit 517 requests the summary information generation device 204 to generate summary information for the image. The deletion unit 518 deletes the uploaded image based on the response from the inspection device 203. The response receiving unit 519 receives the response from the summary information generation device 204 to the request to generate summary information for the image.

[0038] The decision unit 520 determines the subsequent processing of the information management device 202 according to the type of response received. The existence determination unit 521 determines whether the target image exists among the images held by the holding unit 516 if the type of response received indicates a failure to acquire the image by the summary information generation device 204. If it is determined that the image exists, the re-request unit 522 re-requests the summary information generation device 204 to generate summary information for the target image.

[0039] ≪Functional Configuration of the Inspection Device≫ This is achieved when the CPU 401 of the information processing device 400, which functions as an inspection device 203, loads the program stored in the ROM 402 into the RAM 403 and executes processing according to the sequence diagram and flowchart described later. The results of each process are stored in the RAM 403. Each functional unit may also perform some of the functions of other functional units.

[0040] The inspection device 203 has an inspection execution unit 531. When the inspection execution unit 531 receives an image inspection request from the information management device 202, it performs an image inspection.

[0041] ≪Functional Configuration of the Summary Information Generation Device≫ This is achieved when the CPU 401 of the information processing device 400, which functions as a summary information generation device 204, loads the program stored in the ROM 402 into the RAM 403 and executes processing according to the sequence diagram and flowchart described later. The results of each process are stored in the RAM 403.

[0042] The summary information generation device 204 includes a control unit 541, an input unit 542, a storage unit 543, a communication unit 544, a summary information generation unit 545, and an output unit 546. Each functional unit will be described below.

[0043] The control unit 541 controls each component of the summary information generation device 204. The input unit 542 receives input from the user. The storage unit 543 stores programs that operate in the summary information generation device 204, inputs from the information management device 202, etc. The communication unit 544 exchanges data with the information management device 202 using the network interface 407.

[0044] The summary information generation unit 545 generates summary information for an image based on a request for summary information generation from the information management device 202. The output unit 546 outputs the processing results from the summary information generation device 204, the summary information for the image generated by the summary information generation unit 545, etc.

[0045] <Processing flow in an information management system> The processing flow in the information management system 200 of this embodiment will be explained using the sequence diagrams shown in Figures 6 and 7. In the sequence diagrams, "alt" indicates a branch, showing branching processing based on the results of the previous sequence. "opt" indicates processing that is executed only if the result of the previous processing satisfies a condition.

[0046] In S601, user 105 instructs terminal 201 to send an image via input unit 305. In S602, terminal 201 sends an image to information management device 202 based on the image transmission instruction from input unit 305.

[0047] In S603, the information management device 202 requests the inspection device 203 to inspect the image upon receiving it. In S604, the inspection device 203 performs the inspection of the received image. The inspection device 203 obtains an inspection result indicating either "normal" or "incorrect" upon performing the inspection. In S605, the inspection device 203 transmits the inspection result to the information management device 202.

[0048] The information management device 202 performs the processes from S606 to S613 when it receives an inspection result indicating "normal" from the inspection device 203, and performs the processes from S614 to S615 when it receives an inspection result indicating "incorrect" from the inspection device 203.

[0049] In S606, the information management device 202, having received an inspection result indicating "normal," requests the summary information generation device 204 to generate summary information for the image.

[0050] Here, we will explain how to handle the occurrence of a reception event. Note that reception events do not occur intentionally, but are a phenomenon that occurs unintentionally with a certain probability due to the limitations of the platform on which the information management device 202 is built.

[0051] In S607, the information management device 202 unintentionally issues another image inspection request to the inspection device 203 due to the occurrence of a received event.

[0052] In S608, the inspection device 203 performs an inspection of the received image based on the inspection request in S607. At this time, the virus definition file of the inspection device 203 is updated, and it determines that the image is a malicious file. In S609, the inspection device 203 sends the inspection result indicating "malicious" to the information management device 202. In S610, the information management device 202 receives the inspection result indicating malicious and deletes the image that was inspected in S608.

[0053] In S611, the summary information generation device 204 attempts to acquire the target image from the information management device 202 in order to generate summary information for the image based on the request in S606. If no reception event occurs, the target image exists in the information management device 202, and therefore the summary information generation device 204 acquires the target image from the information management device 202. On the other hand, if a reception event occurs, the target image was deleted in S610 and no longer exists in the information management device 202, and therefore the summary information generation device 204 fails to acquire the target image from the information management device 202.

[0054] In S612, the summary information generation device 204 attempts to generate summary information. If no reception event occurs, the summary information generation device 204 generates summary information for the target image from the target image acquired in S611. On the other hand, if a reception event occurs, the summary information generation device 204 fails to generate summary information for the target image because it failed to acquire the target image in S611. In S613, the summary information generation device 204 transmits the request result for the summary information generation request to the information management device 202.

[0055] In S614, the information management device 202 deletes the image in question because it has received an inspection result indicating "incorrect". In S615, the information management device 202 terminates processing based on the inspection result transmitted from the inspection device 203.

[0056] The information management device 202 processes according to the content of the request result transmitted from the inspection device 203, which is either "Information Management Device Side Cause / Undefined Cause," "Summary Information Generation Device Side Cause," or "Success." The information management device 202 processes S616 if it receives a request result indicating "Information Management Device Side Cause" or "Undefined Cause." The information management device 202 processes S617 to S625 if it receives a request result indicating "Summary Information Generation Device Side Cause." The information management device 202 processes S626 to S628 if it receives a request result indicating "Success."

[0057] In S616, the information management device 202 terminates its processing because it has received a request result indicating a cause on the information management device 202's side or an undefined cause.

[0058] In S617, the information management device 202 receives a request result indicating the cause on the summary information generation device 204 side, and performs a process to determine whether or not an image exists.

[0059] Here, we will explain the processing according to the result of the image existence determination process. If the information management device 202 obtains a determination result indicating "existence," it performs the processing from S618 to S624, and if it obtains a determination result indicating "non-existence," it performs the processing in S625.

[0060] In S618, the information management device 202, having obtained a determination result indicating the existence of an image, generates a time-limited reference destination for the image. The time-limited reference destination for the image indicates a reference destination that can only be accessed or the image retrieved within a predetermined time limit. The time limit for the reference destination is set to, for example, one hour, but is not limited to this. When communication between devices takes place in a relatively more secure communication environment, a time longer than one hour may be set as the time limit for the reference destination. When communication between devices takes place in a relatively less secure communication environment, a time shorter than one hour may be set as the time limit.

[0061] In S619, the information management device 202 requests the summary information generation device 204 to generate summary information for the image.

[0062] In S620, the summary information generation device 204 acquires an image from the information management device 202. In S621, the summary information generation device 204 generates summary information for the image acquired in S620. In S622, the summary information generation device 204 sends a request result to the information management device 202. The request result includes a time-limited reference destination for the storage of the summary information. In S623, the information management device 202 acquires the time-limited reference destination for the summary information from the received request result and acquires the summary information from that reference destination. In S624, the information management device 202 stores the summary information acquired in S623 in the storage unit 516.

[0063] In S625, the information management device 202 terminates its processing because it has obtained a determination result indicating the absence of an image.

[0064] In S626, the information management device 202, having received a request result indicating success, obtains a time-limited reference destination for summary information from the received request result and obtains the summary information of the target image from that reference destination. In S627, the information management device 202 stores the summary information of the target image obtained in S626 in the holding unit 516. In S628, the information management device 202 terminates its processing.

[0065] In S629, user 105 instructs terminal 201 to display summary information of the image via input unit 305. In S630, terminal 201 requests summary information of the image from information management device 202 based on the instruction to display summary information of the image from input unit 305. In S631, information management device 202 transmits summary information of the image corresponding to the request in S630 to terminal 201. Terminal 201 receives the summary information transmitted from information management device 202 and displays it on display unit 504. In S632, user 105 views the summary information of the image displayed on display unit 504.

[0066] <Processing flow in information management device 202> Figure 8 is a diagram illustrating the flow of processing performed by the information management device 202.

[0067] In S801, the request unit 517 requests the summary information generation device 204 to generate summary information for the image uploaded to the information management device 202.

[0068] In S802, the deletion unit 518 determines whether the inspection result received from the inspection device 203 is "incorrect". If the result is false (NO in S802), the process moves to S804. Thus, if the received inspection result is "normal" and not "incorrect", the process skips S803, and the uploaded image is not deleted. If the result is true (YES in S802), the process moves to S803. In S803, the deletion unit 518 deletes the uploaded image.

[0069] In S804, the response receiving unit 519 receives the response of the request result from the summary information generation device 204. The response of the request result, i.e., the response information, is either success or error. In the case of an error, the response information includes an error code. Figure 13 shows the error codes output by the summary information generation device 204 in the event of an error. The error causes corresponding to each error code are as follows.

[0070] • If the summary information generation device 204 fails to acquire an image from the information management device 202 • If the parameters used when the information management device 202 called the summary information generation device 204 were incorrect. - If the summary information generation device 204 fails to send the processing result to the information management device 202 • If essential parameters are missing when the information management device 202 calls the summary information generation device 204 If the request header was missing when the information management device 202 called the summary information generation device 204 If the summary information generation device 204 fails to issue a time-limited reference for transmitting the results of the summary information generation process to the information management device 202. If the parameter type was invalid when the information management device 202 called the summary information generation device 204 - If the image format (data format) of the uploaded image is not supported by the summary information generator 204. • If the summary information generator 204 fails to execute a library it calls internally, such as when the image is corrupted. If an error occurs during the internal processing of the summary information generation device 204 - If the call to the job management API that issues the job ID for the job that manages internal calls of the summary information generation device 204 fails. • If authentication fails when the summary information generator 204 accesses a time-limited reference: - If the communication path between the information management device 202 and the summary information generation device 204 is not encrypted. • If the information management device 202 does not make a request using a specified method when calling the summary information generation device 204. If the information management device 202 is unable to obtain the job ID or image ID: If a response is not returned from the summary information generation device 204 within a predetermined time.

[0071] The job management API is located within the summary information generation device 204. When the summary information generation device 204 receives a request to generate summary information, it sends the request to the job management API. The job management API manages the request as a job. At that time, the job management API issues a job ID to identify the job. By notifying the source of the summary information generation request of this job ID, the source can inquire about the progress of the job using the job ID. The information management device 202 also sends the job ID to the summary information generation device 204 when checking the progress of summary information generation and when obtaining summary information.

[0072] In S805, the decision unit 520 determines the subsequent processing of the information management device 202 according to the type of response received.

[0073] <Details of the decision-making process> Figure 9 is a flowchart showing the detailed flow of the decision process (S805). The decision process is performed by the decision unit 520.

[0074] In S901, the decision unit 520 obtains response information indicating the response result of the request. In S902, the decision unit 520 determines whether the result attribute of the response information obtained in S901 is success or not. If it is determined to be success (YES in S902), the process moves to S903. If it is determined not to be success (NO in S902), the process moves to S904.

[0075] In S903, the determination unit 520 sets a value indicating success for the request result as a result of processing by the determination unit 520.

[0076] In S904, the determination unit 520 determines the error cause classification from the response information obtained in S902.

[0077] <Details of the error cause classification process> Figure 10 is a flowchart showing the detailed flow of the error cause classification and determination process (S904). The error cause classification and determination process (S904) is performed by the determination unit 520.

[0078] In S1001, the decision unit 520 obtains response information r. Response information r is the response information obtained in S901. In S1002, the decision unit 520 obtains the error cause classification table. Details of the error cause classification table will be described later using Figure 14. In S1003, the decision unit 520 initializes the error cause classification result. In S1004, the decision unit 520 initializes the counter.

[0079] In S1005, the decision unit 520 determines whether or not the processing has been completed for all elements. If the determination is made that the processing has not been completed for all elements (NO in S1005), the process proceeds to S1006. If the determination is made that the processing has been completed for all elements (YES in S1005), the flow shown in Figure 10 is completed.

[0080] In S1006, the determination unit 520 obtains the error code e of the element pointed to by the counter. In S1007, the determination unit 520 determines whether the error code indicated in the response information matches the error code obtained in S1006. If it is determined that the error code indicated in the response information matches the error code obtained in S1006 (YES in S1007), the process proceeds to S1009. If it is determined that the error code indicated in the response information does not match the error code obtained in S1006 (NO in S1007), the process proceeds to S1008.

[0081] In S1008, the determination unit 520 increments the counter. After completing the process in S1008, the process moves on to S1005.

[0082] In S1009, the determination unit 520 obtains the error cause classification c for the element pointed to by the counter. In S1010, the determination unit 520 sets c as the processing result of S904 (the result of the error cause classification determination). Once the setting of the processing result is complete, the flow shown in Figure 10 is terminated.

[0083] Returning to the explanation of Figure 9, in S905, the decision unit 520 determines whether the error cause, which is the result of the error cause classification in S904, is a caller-side cause. If the result of the determination is true (YES in S905), the process moves to S906. If it is false (NO in S905), the process moves to S907.

[0084] The caller-side cause is as follows: • If the parameters used when the information management device 202 called the summary information generation device 204 were incorrect. • If essential parameters are missing when the information management device 202 calls the summary information generation device 204 If the request header was missing when the information management device 202 called the summary information generation device 204 If the parameter type was invalid when the information management device 202 called the summary information generation device 204 - If the image format of the uploaded image is not supported by the summary information generator 204 If the summary information generator 204 fails to execute the library it calls internally - If the call to the job management API that issues the job ID for the job that manages internal calls of the summary information generation device 204 fails. • If authentication fails when the summary information generator 204 accesses a time-limited reference: - If the communication path between the information management device 202 and the summary information generation device 204 is not encrypted. • If the information management device 202 does not make a request using a specified method when calling the summary information generation device 204. If the information management device 202 is unable to obtain the job ID or image ID:

[0085] In S906, the determination unit 520 sets a value representing the caller's cause in the request result as a result of processing by the determination unit 520.

[0086] In S907, the determination unit 520 determines whether the error cause, which is the result of the error cause classification in S904, is a cause on the summary information generation device 204 side. If the result of the determination is true (YES in S907), the process moves to S908. If it is false (NO in S907), the process moves to S909.

[0087] The cause on the summary information generation device 204 side is as follows: • If the summary information generation device 204 fails to acquire an image from the information management device 202 - If the summary information generation device 204 fails to send the processing result to the information management device 202 If the summary information generation device 204 fails to issue a time-limited reference for transmitting the results of the summary information generation process to the information management device 202. If an error occurs during the internal processing of the summary information generation device 204 If a response is not returned from the summary information generation device 204 within a predetermined time.

[0088] In S908, the decision unit 520 sets a value representing the cause on the summary information generation device 204 side in the requested result as a result of processing by the decision unit 520. In S909, the decision unit 520 sets a value representing the cause of an undefined cause in the requested result as a result of processing by the decision unit 520.

[0089] In steps S903, S906, S908, and S909 described above, once the processing result settings are complete, the flow shown in Figure 9 is terminated.

[0090] Returning to the explanation of Figure 8, in S806, the control unit 511 determines the type of subsequent processing (response) determined in S805. If the type of response is determined to be success, the process proceeds to S807. If the type of response is determined to be due to the summary information generation device 204, the process proceeds to S808. If the type of response is determined to be due to the caller or an undefined cause, the flow shown in Figure 8 is terminated.

[0091] In S807, the control unit 511 obtains summary information from the reference source of the summary information included in the response information and stores it in the holding unit 516.

[0092] In S808, the existence determination unit 521 determines whether or not the uploaded image exists in the storage unit 516. If the result of the determination is that the uploaded image exists in the storage unit 516 (YES in S808), the process proceeds to S809. If the uploaded image does not exist in the storage unit 516 (NO in S808), the flow shown in Figure 8 is terminated.

[0093] In S809, the re-request unit 522 regenerates a time-limited reference destination for the uploaded image and sends it to the summary information generation device 204, thereby re-requesting the generation of summary information. After completing the processing in S808, the process moves on to S804.

[0094] <Details of the existence / non-existence determination process> Figure 11 is a flowchart showing the detailed flow of the existence / non-existence determination process (S617). The existence / non-existence determination process is performed by the existence / non-existence determination unit 521.

[0095] In S1101, the existence determination unit 521 obtains the image bucket name from the storage unit 513. In S1102, the existence determination unit 521 obtains the image key from the storage unit 513. In S1103, the existence determination unit 521 specifies the image bucket name, key, and expiration date and obtains the time-limited reference destination for the image.

[0096] In S1104, the existence / non-existence determination unit 521 determines the type of exception and whether or not an exception occurred, and then determines the subsequent processing in the existence / non-existence determination unit 521. If an argument error occurs as a result of the determination, the process proceeds to S1105. If a client error occurs as a result of the determination, the process proceeds to S1106. If no exception occurs as a result of the determination, the process proceeds to S1107.

[0097] In S1105, the existence / non-existence determination unit 521 generates an argument error and sends an error to the caller. As a result, an argument error is raised to the caller.

[0098] In S1106, the existence determination unit 521 generates a system error and sends an error to the caller. As a result, a system error is raised to the caller. In S1107, the existence determination unit 521 returns a time-limited reference to the caller.

[0099] After completing the processes S1105, S1106, and S1107 described above, the flow shown in Figure 11 is completed.

[0100] The tables managed by the information management device 202 according to this embodiment will be explained using Figures 12(a) and 12(b). Figure 12(a) is a diagram showing an example of a user table managed by the information management device 202 according to this embodiment.

[0101] In user table 1200, the information shown in the fields User ID 1201, Registration Date 1202, and Login ID 1203 is linked and managed.

[0102] The User ID 1201 column stores information indicating a user ID that uniquely identifies the user, such as "U001" or "U002". The Registration Date 1202 column stores the registration date on which the user completed user registration with the information management device 202. The Login ID 1203 column stores the login ID and other information used for logging in.

[0103] By associating a user ID, which uniquely identifies a user, with the registration date on which the user completed user registration with the information management device 202, and the login ID used for logging in, the user ID can be used as a key to refer to the registration date and login ID.

[0104] Figure 12(b) shows an example of a file table managed by the information management device 202 in this embodiment. File table 1210 is managed by the information management device 202.

[0105] File table 1210 manages the information shown in each of the following fields: File ID 1211, User ID 1212, Upload Date 1213, File Name 1214, File Type 1215, and Image Reference 1216, by linking them together.

[0106] The File ID 1211 column stores information indicating a file ID that uniquely identifies the file, such as "I001" or "I002". The User ID 1212 column stores information indicating a user ID that uniquely identifies the user who owns the file, such as "U001" or "U002".

[0107] The Upload Date column 1213 stores the upload date on which the user uploaded the file to the information management device 202. The File Name column 1214 stores the file name, which is the name of the file. The File Type column 1215 stores information indicating the type of file. The Image Reference Location column 1216 stores information indicating the storage location where the target image is stored by the storage unit.

[0108] In file table 1210, the file ID is associated with the user ID of the file owner, the upload date, file name, file type, and image reference destination of the file. This allows the user ID, upload date, file name, file type, and image reference destination to be accessed using the file ID as the key.

[0109] <List of Error Codes> Figure 13 illustrates the error codes output by the summary information generation device 204 according to this embodiment.

[0110] The error code list table 1300 shows a list of error codes output by the summary information generation device 204, and manages the information stored in each item of error code 1301 and cause 1302 in a linked manner. Error code 1301 stores an error code for uniquely identifying the error. Cause 1302 indicates the cause of the error to which error code 1301 is associated.

[0111] <Error Cause Classification Table> Figure 14 illustrates the error cause classification table. The error cause classification table 1400 is managed by the information management device 202.

[0112] The error cause classification table 1400 manages the information shown in the column for error code 1401 and the information shown in the column for classification code 1402 by linking them together.

[0113] By associating error code 1401 with classification code 1402 and storing them together, classification code 1402 can be referenced using error code 1401 as the key. Classification code C001 represents an error caused by the summary information generation device 204, and C002 represents an error caused by the calling device.

[0114] Error code E011 is classified under C002 for the following reasons: This is because the error is due to a cloud infrastructure issue, not a problem with the summary information generator itself, such as an unexpected abnormal termination of the virtual server instance on the cloud infrastructure where the summary information generator is built, or the gateway provided by the cloud infrastructure rejecting the request for some reason.

[0115] As explained above, in this embodiment, a re-request control is implemented to re-request the summary information generation device to generate summary information for data, depending on the type of response to the request to the summary generation device and whether or not data exists. Specifically, if the type of response is a failure to acquire data by the summary information generation device and data exists in the information management device, control is executed to re-request the summary information generation device to generate summary information for data. Even if the type of response is a failure to acquire data by the summary information generation device, if data does not exist in the information management device, control is executed not to re-request the summary information generation device to generate summary information for data. In this way, when requesting the generation of summary information, the summary information generation device is requested to generate summary information for an image only if an image managed by the information management device exists, thus unnecessary requests can be suppressed.

[0116] <<Embodiment 2>> This embodiment describes a method for determining subsequent processing according to the processing status of the summary information generation device. The overview and configuration of the information management system, the hardware configuration of the terminal, and the hardware configuration of the information processing device according to this embodiment are the same as in Embodiment 1, so their description is omitted. This embodiment will mainly describe the differences from Embodiment 1.

[0117] <Functional Configuration of Information Management System> Figure 15 shows an example of the functional configuration of the information management system according to this embodiment. The information management system of this embodiment includes a terminal 201, an inspection device 203, an information management device 1510, and a summary information generation device 1520.

[0118] ≪Functional Configuration of Information Management Device≫ This is achieved when the CPU 401 of the information processing device 400, which functions as an information management device 1510, loads the program stored in the ROM 402 into the RAM 403 and executes the processing according to the sequence diagram and flowchart described later. The results of each process are stored in the RAM 403.

[0119] In addition to having functional units 511-515 and 517-522, the information management device 1510 further includes a holding unit 1511, a processing status acquisition unit 1512, a re-request decision unit 1513, an alternative information holding unit 1514, and a provision unit 1515. Each functional unit may also perform some of the functions of the other functional units.

[0120] The holding unit 1511 holds the information necessary for processing. The processing status acquisition unit 1512 acquires the processing status of the summary information generation process, which is the process of generating summary information in the summary information generation device 1520. The re-request decision unit 1513 decides whether or not to re-request the generation of summary information based on the processing status of the summary information generation process.

[0121] The alternative information holding unit 1514 holds alternative information. Alternative information refers to information such as images, text, audio, and video that is provided to the user as a substitute when uploaded images and summary information do not exist. The providing unit 1515 provides alternative information to the terminal 201 when uploaded images and summary information do not exist.

[0122] ≪Functional Configuration of the Summary Information Generation Device≫ The CPU 401 of the information processing device 400, which functions as a summary information generation device 1520, loads the program stored in the ROM 402 into the RAM 403 and executes processing according to the sequence diagram and flowchart described later. The results of each process are stored in the RAM 403. Each functional unit may also perform some of the functions of other functional units.

[0123] In addition to having functional units 541 to 546, the summary information generation device 1520 further includes a processing status generation unit 1521. The processing status generation unit 1521 generates information (processing status information) indicating the processing status of the summary information generation process by the summary information generation device 1520.

[0124] <Processing flow in information management device 1510> Figure 16 is a diagram illustrating the processing flow in the information management device 1510.

[0125] In S1601, the control unit 511 initializes the storage area S0, which stores the processing status of the previous processing, which is the processing status when the summary information generation device 1520 was requested to generate summary information. In S1602, the control unit 511 initializes the retry counter, which counts the number of retries.

[0126] In S1603, the request unit 517 requests the summary information generation device 1520 to generate summary information. In S1604, the control unit 511 initializes a timer that measures the elapsed time since the request for summary information generation. In S1605, the response receiving unit 519 receives response information from the summary information generation device 1520.

[0127] In S1606, the processing status acquisition unit 1512 acquires processing status information indicating the processing status from the response information. The response information has a processing status attribute that represents the processing status of the summary information generation process. Therefore, in the process of S1606, the value of the processing status attribute is acquired from the response information. The value of the processing status attribute indicates one of the following: before processing, in progress, or completed. The storage area S0 stores "before processing" if the processing is before processing, "in progress" if the processing is in progress, and "completed" if the processing is completed.

[0128] In S1607, the re-request determination unit 1513 determines the subsequent processing in the information management device 1510 based on the processing status. If the processing status is complete, the process moves to S1608. If the processing status is before processing, the process moves to S1609. If the processing status is in progress, the process moves to S1610.

[0129] In S1608, the control unit 511 acquires summary information from the summary information generation device 1520 and stores it in the holding unit 1511.

[0130] In S1609, the re-request determination unit 1513 determines whether the retry counter is less than the retry threshold. The retry threshold is, for example, 2 times. If the determination is true (YES in S1609), the process proceeds to S1611. If it is false (NO in S1609), the flow shown in Figure 16 is terminated.

[0131] In S1610, the retry request determination unit 1513 determines whether the retry counter is less than the retry threshold. If the determination is true (YES in S1610), the process proceeds to S1615. If it is false (NO in S1610), the flow shown in Figure 16 is terminated.

[0132] In S1611, the re-request determination unit 1513 determines whether the storage area S0 is in the pre-processing state and whether the timer has exceeded the timeout period T1. The timeout period T1 is set to, for example, 130 seconds. The process in S1611 can also be described as determining whether to re-request if the processing status is the first processing status (pre-processing) and a predetermined amount of time has elapsed since the previous request. If the result of the determination is true (YES in S1611), the process moves to S1612. If it is false (NO in S1611), the process moves to S1613.

[0133] In S1612, the re-request determination unit 1513 determines whether or not an uploaded image exists and determines the subsequent processing. If it is determined that an uploaded image exists (YES in S1612), the process proceeds to S1614. If it is determined that an uploaded image does not exist (NO in S1612), the process proceeds to S1618. Note that if an uploaded image exists, the generation of summary information is requested again, so it can also be said that this determines whether or not to request the generation of summary information again.

[0134] In S1613, the processing status acquisition unit 1512 inquires about the processing status from the summary information generation device 1520. After the processing in S1613 is completed, the process moves on to S1605.

[0135] In S1614, the control unit 511 increments the retry counter. After completing the process in S1614, the process moves on to S1603.

[0136] In S1615, the re-request determination unit 1513 determines whether or not the storage SO is being processed. If it is determined to be being processed (YES in S1615), the process proceeds to S1617. If it is determined to be not being processed (NO in S1615), the process proceeds to S1616.

[0137] In S1616, the re-request determination unit 1513 determines whether the timer has exceeded the timeout period T2. The timeout period T2 is set to, for example, 300 seconds. Note that the setting of the timeout period T2 is not limited to 300 seconds; for example, it may be the same as the timeout period T1, 130 seconds. If it is determined that the timer has exceeded the timeout period T2 (YES in S1616), the flow shown in Figure 16 is terminated. If it is determined that the timer has not exceeded the timeout period T2 (NO in S1616), the process moves to S1613.

[0138] In S1617, the re-request determination unit 1513 determines whether the timer has exceeded the timeout period T2. In the process of S1617, it can also be said that a determination is made whether to re-request if the processing status is the second processing status (processing) and a predetermined amount of time has elapsed since the previous request. If it is determined that the timer has exceeded the timeout period T2 (YES in S1617), the process moves to S1612. If it is determined that the timer has not exceeded the timeout period T2 (NO in S1617), the process moves to S1613.

[0139] In S1618, the provisioning unit 1515 retrieves alternative information from the alternative information holding unit 1514 and saves the alternative information to the storage location where the summary information should be saved. While the provisioning unit 1515 saves the alternative information to the summary information storage location, it is not limited to this. For example, it may send the alternative information each time a summary information acquisition request is received from the terminal. Furthermore, any method that allows the user to receive alternative information when summary information does not exist is acceptable. By providing some information to the user in this way, it is possible to avoid situations where the user is confused by not receiving any information when summary information cannot be generated.

[0140] As explained above, according to this embodiment, a threshold is set for the number of times the generation of summary information is re-requested, so unnecessary requests can be suppressed.

[0141] Furthermore, the re-request decision unit 1513 is not limited to the above decision method, and may interrupt processing with a timeout period different from the timeout period specified by the summary information generation device 1520. This avoids making the user wait unnecessarily.

[0142] Furthermore, the information management device may be configured to back up uploaded images as error images and delete them from their storage location in the following cases: when retries fail after a predetermined number of attempts; when a retry is not possible error occurs; or when the response is placed in a dedicated error handling queue. This prevents the system or administrator from inadvertently accessing unauthorized images.

[0143] Furthermore, the system may be configured to automatically delete backed-up uploaded images after a predetermined number of days, such as 30 days. This prevents the system or administrator from inadvertently accessing inappropriate images. Note that the predetermined number of days is not limited to 30 days. If an operational system is in place to immediately investigate the cause and take countermeasures when a backup occurs, the predetermined number of days may be set to a shorter number, such as 3 or 5 days. Alternatively, a longer number of days, such as 60 days, may be set to allow for re-verification if necessary later.

[0144] Furthermore, if the generation of image summary information fails, a failure log may be collected and stored. The failure log may include, for example, the date and time the failure to generate the summary information occurred, the user ID, and the file ID.

[0145] In this embodiment, alternative information is provided when uploaded images and summary information are unavailable, but this is not the only option. For example, the information management device 1510 may be configured to include a summary information generation module and utilize it.

[0146] <<Embodiment 3>> This embodiment describes a configuration that allows for verification of the performance of the information management device. The overview and configuration of the information management system, the hardware configuration of the terminal, and the hardware configuration of the information processing device according to this embodiment are the same as in Embodiment 1, so their description is omitted. This embodiment will mainly describe the differences from Embodiment 1.

[0147] <Functional Configuration of Information Management System> Figure 17 shows an example of the functional configuration of the information management system according to this embodiment. The information management system of this embodiment includes a terminal 201, an inspection device 203, a summary information generation device 204, and an information management device 1710.

[0148] ≪Functional Configuration of Information Management Device 1710≫ The realization is achieved by the CPU 401 of the information processing apparatus 400 that functions as the information management apparatus 1710 expanding the program stored in the ROM 402 to the RAM 403 and executing the processes according to the sequence diagram and flowchart. Note that the execution results of each process are held in the RAM 403.

[0149] In addition to having the functional units 511 to 522, the information management apparatus 1710 further has a performance output unit 1711 and a performance display unit 1712. Note that each functional unit may perform part of the functions of other functional units.

[0150] The performance output unit 1711 outputs performance information that records the result of requesting generation of summary information. Note that the performance information is information including the reception time from the summary information generation apparatus 204 and the reception result.

[0151] The performance display unit 1712 displays the performance information. The performance display unit 1712 displays a combination of the total value obtained by adding the reception results at a predetermined aggregation granularity and the reception time. Here, the aggregation granularity will be described. The reception of an image is counted when the user transmits an image from the terminal 201 and the information management apparatus 1710 receives it. However, since it depends on the timing of transmission by the user, the reception occurs irregularly. The aggregation granularity indicates that the number of receptions is totaled every fixed period such as every second or every minute, and the total value is managed as the number of receptions in that time interval. In the example of FIG. 18, the total value for each day is plotted in units of one day, and the aggregation granularity indicates in which time interval the total value is displayed.

[0152] [[ID=1—>16]]<UI Configuration> FIG. 18 is a diagram for explaining the performance display screen generated by the information management apparatus 1710.

[0153] The UI screen 1800 displays a graph representing the number of daily errors. In the graph, the horizontal axis indicates time, and the vertical axis indicates the number of daily errors. Note that the scale of the horizontal axis is not limited to daily, and it may be configured to be displayed in a scale that is easy for the administrator to observe, such as seconds, minutes, hours, days, weeks, months, years, or any arbitrarily specified period.

[0154] The black circle 1801 represents the total number of errors per day. The black triangle 1802 represents the number of errors that will be retried per day.

[0155] The UI screen 1800 is displayed on the display 404 of the information processing device 400, which functions as an information management device 1710. The UI screen 1800 displayed on the display 404 allows users to check the actual results of requests for summary information generation. Furthermore, the actual results include the reception time and the reception result received from the summary information generation device, allowing users to check the details of the summary information generation process by the summary information generation device.

[0156] Furthermore, UI screen 1800 displays a graph that combines the total value obtained by adding the received results at a predetermined aggregation granularity with the received date and time (receive time), allowing users to check the total number of errors that occurred during the generation of summary information and the number of errors that were retried on a daily basis.

[0157] Furthermore, the information management device 202 may be configured to send a notification to the administrator terminal if the number of errors exceeds a predetermined threshold. The predetermined threshold is set to, for example, three times. However, the predetermined threshold is not limited to this and may be set to one time or two times.

[0158] As described above, according to this embodiment, in addition to suppressing the request for the generation of unnecessary summary information, the total number of errors that occurred in the generation of summary information and the number of errors that should be retried can be checked on a predetermined scale such as on a daily basis.

[0159] <Other embodiments> As detailed above in the embodiments, the technology of this disclosure can take the form of, for example, a system, apparatus, method, program, or recording medium (storage medium). Specifically, it may be applied to a system consisting of multiple devices (for example, a host computer, interface devices, imaging devices, web applications, etc.), or to an apparatus consisting of a single device.

[0160] Furthermore, it goes without saying that the objective of the technology disclosed herein is achieved as follows: a recording medium (or storage medium) containing software program code (computer program) that realizes the functions of the embodiments described above is supplied to a system or device. Such storage medium is, of course, a computer-readable storage medium. The computer (or CPU or MPU) of the system or device then reads and executes the program code stored on the recording medium. In this case, the program code read from the recording medium itself realizes the functions of the embodiments described above, and the recording medium containing that program code constitutes the technology disclosed herein.

[0161] This disclosure is not limited to the embodiments described above, and various modifications may be made, or parts of the embodiments may be combined as appropriate.

[0162] Furthermore, each functional unit of the device constituting the information management system may be implemented in a distributed manner across multiple terminals or information processing devices. When functions are distributed across multiple information processing devices, they are connected via a LAN or similar means to enable communication with each other, and they collaborate to perform the series of processes described later.

[0163] Furthermore, each functional unit of the devices constituting the information management system is realized by the execution of a program by the CPU of each device, but is not limited to this. Other hardware, such as a GPU or FPGA (not shown), may also be used. Each functional unit may be realized through the cooperation of software and hardware such as a dedicated IC, or some or all of the functions may be realized by hardware alone.

[0164] This disclosure can also be implemented by supplying a program that implements one or more of the functions of the above embodiments to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be implemented by a circuit (e.g., an ASIC) that implements one or more functions. Furthermore, the program may be recorded on a recording medium readable by a computer and provided.

[0165] This embodiment includes the following configuration examples. (Composition 1) An information management device for managing data, A request means for requesting a summary generation device that generates summary information to generate summary information for the aforementioned data, A deletion means for deleting the aforementioned data, A re-request control means controls the summary generation device to re-request the generation of summary information for the data, depending on the type of response to the request and whether the data exists or not. It has, The aforementioned re-request control means is If the type of response is a failure to acquire the data by the summary generation device, and the data exists, control is performed to request the summary generation device to generate summary information of the data again. Even if the type of response is a failure to acquire the data by the summary generation device, if the data does not exist, control is performed so as not to request the summary generation device to generate summary information of the data again. An information management device characterized by the following features. (Configuration 2) The information management device according to Configuration 1, characterized in that the re-request control means generates a time-limited reference destination for the data and transmits the time-limited reference destination to the summary generation device. (Composition 3) The re-request control means, if the error is caused by the summary generation device, controls the summary generation device to re-request the generation of summary information for the data. An information management device according to configuration 1 or 2, characterized by the above. (Composition 4) Errors caused by the aforementioned summary generation device are, If the summary generation device fails to acquire the data, If the summary generation device fails to transmit the result of the process that generates the summary information, If the summarization device fails to issue a time-limited reference to which it transmits the results of the process of generating summary information, If an error occurs in the internal processing of the summary generation device, If no response is returned from the summary generation device within a predetermined time, The information management device according to configuration 3, characterized in that it is at least one of the following. (Composition 5) The re-request control means, if the error is caused by the information management device, controls the summary generation device not to re-request the generation of summary information for the data. An information management device according to any one of configurations 1 to 4, characterized by the above. (Composition 6) Errors caused by the aforementioned information management device are: If the parameters used when the information management device invoked the summary generation device were incorrect, If essential parameters are missing when the information management device calls the summary generation device, If the request header was missing when the information management device called the summary generation device, If the type of the parameter used when the information management device invoked the summary generation device was invalid, If the data format of the aforementioned data is not supported by the summary generation device, If the summary generation device fails to execute the library it calls internally, If the call to the job management API that issues the job ID for the job that manages the internal calls of the summary generation device fails, If the summary generation device fails to authenticate when accessing a time-limited reference, If the communication path between the information management device and the summary generation device is not encrypted, If the request made by the information management device to the summary generation device was not in a method specified in the prescribed method, If the aforementioned information management device is unable to obtain the job ID and image ID: The information management device according to configuration 5, characterized in that it is at least one of the following. (Composition 7) An acquisition means for acquiring processing status information indicating the processing status of the summary generation device from the response to the aforementioned request, A re-request determination means that determines to re-request the summary generation device to generate summary information of the data according to the processing status indicated in the processing status information, An information management device according to any one of configurations 1 to 7, further comprising the above. (Composition 8) The re-request determination means determines, if the processing status is the state before the summary information generation process and a predetermined amount of time has elapsed since the previous request, to re-request the summary generation device to generate the summary information for the data. The information management device according to configuration 7, characterized by the features described above. (Composition 9) The re-request determination means determines, if the processing status is in the state of generating the summary information and a predetermined amount of time has elapsed since the previous request, to re-request the summary generation device to generate the summary information for the data. The information management device according to configuration 7, characterized by the features described above. (Composition 10) The re-request determination means interrupts processing at a second timeout period that is different from the first timeout period defined by the summary generation device. The information management device according to configuration 7, characterized by the features described above. (Composition 11) The re-request determination means saves the data if the re-request fails a predetermined number of times. The information management device according to configuration 7, characterized by the features described above. (Composition 12) The aforementioned backed-up data will be deleted after a predetermined number of days have elapsed. The information management device according to configuration 11, characterized by the features described above. (Composition 13) Alternative information holding means for holding alternative information in place of the summary information, If the aforementioned data and summary information are not available, a providing means provides the alternative information held in the alternative information holding means, An information management device according to any one of configurations 7 to 12, characterized by having the following: (Composition 14) The providing means stores the alternative information in the storage location where the summary information should be stored. The information management device according to configuration 13, characterized by the features described above. (Composition 15) The information management device according to configuration 13, characterized in that the providing means transmits the alternative information each time a terminal that has transmitted the data to the information management device requests to acquire it. (Composition 16) The system further includes output means for outputting performance information that records the results of the request for the generation of the aforementioned summary information, The aforementioned performance information includes the time of reception and the reception result from the summary generation device. An information management device according to any one of configurations 1 to 15, characterized by the above. (Composition 17) The system further includes a display means that displays a combination of the sum obtained by adding the reception results at a predetermined aggregation granularity and the reception time. An information management device according to any one of configurations 1 to 16, characterized by the above. (Composition 18) The information management device according to any one of configurations 1 to 17, characterized in that the summary information of the aforementioned data is information that can determine what kind of data the aforementioned data is. (Composition 19) If the data is an image, the summary information of the data includes at least one of the following: a thumbnail of the image, information on the image being captured, and features of the image. An information management device according to any one of configurations 1 to 18, characterized by the above. (Composition 20) The system further includes data holding means for holding the aforementioned data, The deletion means deletes the data held in the data holding means. An information management device according to any one of configurations 1 to 19, characterized by the above. (Composition 21) A data management method for managing data, A request step of requesting a summary generation device that generates summary information to generate summary information of the aforementioned data, A deletion step to delete the aforementioned data, A re-request control step is performed to control the summary generation device to re-request the generation of summary information for the data, depending on the type of response to the request and whether or not the data exists. Includes, In the aforementioned re-request control process, If the type of response is a failure to acquire the data by the summary generation device, and the data exists, control is performed to request the summary generation device to generate summary information of the data again. Even if the type of response is a failure to acquire the data by the summary generation device, if the data does not exist, control is performed so as not to request the summary generation device to generate summary information of the data again. An information management method characterized by the following features. (Composition 22) A program to cause a computer to function as an information management device described in any one of configurations 1 through 20. (Composition 23) An information management system having an information management device for managing data and a summary generation device, The aforementioned information management device is A request means for requesting a summary generation device that generates summary information to generate summary information for the aforementioned data, A deletion means for deleting the aforementioned data, A re-request control means controls the summary generation device to re-request the generation of summary information for the data, depending on the type of response to the request and whether the data exists or not. Yes, The summary generation device is The system has a generation means for generating summary information of the aforementioned data, The aforementioned re-request control means is If the type of response is a failure to acquire the data by the summary generation device, and the data exists, control is performed to request the summary generation device to generate summary information of the data again. Even if the type of response is a failure to acquire the data by the summary generation device, if the data does not exist, control is performed so as not to request the summary generation device to generate summary information of the data again. An information management system characterized by the following features.

Claims

1. An information management device for managing data, A request means for requesting a summary generation device that generates summary information to generate summary information for the aforementioned data, An inspection request means for causing the inspection device to inspect the aforementioned data, A deletion means for deleting the data based on the response of the inspection device, A re-request control means controls the summary generation device to re-request the generation of summary information for the data, depending on the type of response to the request and whether the data exists or not. It has, The aforementioned re-request control means is If the type of response is a failure to acquire the data by the summary generation device, and the data exists, control is performed to request the summary generation device to generate summary information of the data again. Even if the type of response is a failure to acquire the data by the summary generation device, if the data does not exist, control is performed so as not to request the summary generation device to generate summary information of the data again. An information management device characterized by the following features.

2. The information management device according to claim 1, characterized in that the re-request control means generates a time-limited reference destination for the data and transmits the time-limited reference destination to the summary generation device.

3. The re-request control means is If the summary generation device fails to transmit the result of the process that generates the summary information, If the summarization device fails to issue a time-limited reference to which it transmits the results of the process of generating summary information, If an error occurs in the internal processing of the summary generation device, If no response is returned from the summary generation device within a predetermined time, The information management device according to claim 1, characterized in that if at least one of the above is true, the device controls the summary generation device to re-request the generation of summary information for the data.

4. The re-request control means, if the error is caused by the information management device, controls the summary generation device not to re-request the generation of summary information for the data. The information management device according to feature 1.

5. Errors caused by the aforementioned information management device are: If the parameters used when the information management device invoked the summary generation device were incorrect, If essential parameters are missing when the information management device calls the summary generation device, If the request header was missing when the information management device called the summary generation device, If the type of the parameter used when the information management device invoked the summary generation device was invalid, If the data format of the aforementioned data is not supported by the summary generation device, If the summary generation device fails to execute the library it calls internally, If the call to the job management API that issues the job ID for the job that manages the internal calls of the summary generation device fails, If the summary generation device fails to authenticate when accessing a time-limited reference, If the communication path between the information management device and the summary generation device is not encrypted, If the request made by the information management device to the summary generation device was not in a method specified in the prescribed method, If the aforementioned information management device is unable to obtain the job ID and image ID: The information management device according to claim 4, characterized in that it is at least one of the following.

6. An acquisition means for acquiring processing status information indicating the processing status of the summary generation device from the response to the aforementioned request, A re-request determination means that determines to re-request the summary generation device to generate summary information of the data according to the processing status indicated in the processing status information, The information management device according to claim 1, further comprising the above.

7. The re-request determination means determines, if the processing status is the state before the summary information generation process and a predetermined amount of time has elapsed since the previous request, to re-request the summary generation device to generate the summary information for the data. The information management device according to feature 6.

8. The re-request determination means determines, if the processing status is in the state of generating the summary information and a predetermined amount of time has elapsed since the previous request, to re-request the summary generation device to generate the summary information for the data. The information management device according to feature 6.

9. The re-request determination means interrupts processing at a second timeout period that is different from the first timeout period defined by the summary generation device. The information management device according to feature 6.

10. The re-request determination means saves the data if the re-request fails a predetermined number of times. The information management device according to feature 6.

11. The aforementioned backed-up data will be deleted after a predetermined number of days have elapsed. The information management device according to claim 10.

12. Alternative information holding means for holding alternative information in place of the summary information, If the aforementioned data and summary information are not available, a providing means provides the alternative information held in the alternative information holding means, The information management device according to claim 6, characterized by having the following:

13. The providing means stores the alternative information in the storage location where the summary information should be stored. The information management device according to claim 12.

14. The information management device according to claim 12, characterized in that the providing means transmits the alternative information each time a terminal that has transmitted the data to the information management device requests to acquire it.

15. The system further includes output means for outputting performance information that records the results of the request for the generation of the aforementioned summary information, The aforementioned performance information includes the time of reception and the reception result from the summary generation device. The information management device according to feature 1.

16. The information management device according to claim 15, further comprising a display means for displaying a set of the total value obtained by adding the reception results at a predetermined aggregation granularity and the reception time.

17. The information management device according to claim 1, characterized in that the summary information of the aforementioned data is information that can determine what kind of data the aforementioned data is.

18. If the data is an image, the summary information of the data includes at least one of the following: a thumbnail of the image, information on the image being captured, and features of the image. The information management device according to feature 1.

19. The system further includes data holding means for holding the aforementioned data, The deletion means deletes the data held in the data holding means. The information management device according to feature 1.

20. A data management method for managing data, A request step of requesting a summary generation device that generates summary information to generate summary information of the aforementioned data, A process of requesting an inspection to have the aforementioned data inspected by an inspection device, A deletion step is performed to delete the data based on the response of the inspection device, A re-request control step is performed to control the summary generation device to re-request the generation of summary information for the data, depending on the type of response to the request and whether or not the data exists. Includes, In the aforementioned re-request control process, If the type of response is a failure to acquire the data by the summary generation device, and the data exists, control is performed to request the summary generation device to generate summary information of the data again. Even if the type of response is a failure to acquire the data by the summary generation device, if the data does not exist, control is performed so as not to request the summary generation device to generate summary information of the data again. An information management method characterized by the following features.

21. A program for causing a computer to function as an information management device as described in claim 1.

22. An information management system having an information management device for managing data and a summary generation device, The aforementioned information management device is A request means for requesting a summary generation device that generates summary information to generate summary information for the aforementioned data, An inspection request means for causing the inspection device to inspect the aforementioned data, A deletion means for deleting the data based on the response of the inspection device, A re-request control means controls the summary generation device to re-request the generation of summary information for the data, depending on the type of response to the request and whether the data exists or not. Yes, The summary generation device is The system has a generation means for generating summary information of the aforementioned data, The aforementioned re-request control means is If the type of response is a failure to acquire the data by the summary generation device, and the data exists, control is performed to request the summary generation device to generate summary information of the data again. Even if the type of response is a failure to acquire the data by the summary generation device, if the data does not exist, control is performed so as not to request the summary generation device to generate summary information of the data again. An information management system characterized by the following features.

Images