Image Processing Device

Abstract

To provide a technology which, when an image processing device executes a job that includes a scan, transmits a log related to the job to a server following an appropriate procedure.SOLUTION: An MFP 1 is capable of executing a scan job that includes reading a plurality of document pages, generating image data based on the result of reading, and outputting a file in which the generated image data is written. The MFP 1 checks to see whether it is possible to access a log preservation server 4 upon receiving a scan job execution indication via a user interface 13, and aborts job execution without doing file output when it was impossible to access the log preservation server 4, or transmits a job-related log to the log preservation server 4 before outputting the file when it was possible to access the log preservation server 4, as well as outputs the file when it possible to preserve the log in the log preservation server 4 or aborts job execution without outputting the file when it was impossible to preserve the log in the log preservation server 4.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The technical field disclosed in this specification relates to an image processing apparatus, and more particularly to a technique for storing a log of jobs executed by the image processing apparatus in a server. [Background technology]

[0002] Conventionally, there has been known an image processing device capable of executing image processing based on image data, which, when executing a job including image processing, stores a log related to the job in a server. For example, Patent Document 1 discloses a system including a multifunction peripheral and a server, in which the multifunction peripheral monitors the copying and scanning of documents to acquire a log, transmits the acquired log to the server, and the server stores the log. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-160698 Summary of the Invention [Problem to be solved by the invention]

[0004] The system disclosed in Patent Document 1 discloses that a log of a job including scanning is sent to a server, but does not disclose details of the procedure for saving the log on the server. When executing a job including scanning, there are cases where it is required to reliably leave a log, and there is room for improvement in the procedure for saving the log. [Means for solving the problem]

[0005] The image processing device disclosed in this specification is an image processing device equipped with a scanner, and the image processing device is capable of executing a file output job, the file output job being a job including reading a document of a plurality of pages by the scanner, generating image data of a plurality of pages based on the read document of the plurality of pages, and outputting a file into which the generated image data is written to a specified output destination, and further the image processing device is configured to save a log relating to the file output job in a server when the image processing device executes the file output job, and further the image processing device, in response to receiving an instruction to execute the file output job via an input interface of the image processing device, and checks whether the server can be accessed, and if the server cannot be accessed, the file is not output to the specified output destination and execution of the file output job is stopped, and if the server can be accessed, the log related to the file output job is sent to the server before outputting the file into which the generated image data has been written to the specified output destination, and if the sent log can be saved on the server, the file into which the generated image data has been written is output to the specified output destination, and if the sent log cannot be saved on the server, the file is not output to the specified output destination and execution of the file output job is stopped.

[0006] When an image processing device disclosed in this specification receives an instruction to execute a file output job, it checks whether it can access the server before outputting the file, and if it cannot access the server, it cancels the file output job. Furthermore, if it cannot save the log, it also cancels the file output job. Therefore, it is possible to reduce the number of situations where a log related to a file output job cannot be saved on the server even though the file output job has been executed.

[0007] A control method for realizing the functions of the above-described device, a computer program, and a computer-readable storage medium storing the computer program are also novel and useful. [Effects of the Invention]

[0008] According to the technology disclosed in this specification, when an image processing apparatus executes a job including scanning, a log relating to the job is transmitted to a server in a suitable procedure. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a block diagram showing a schematic configuration of an MFP according to an embodiment of the present invention. [Figure 2] 10 is a flowchart illustrating a procedure for a job analysis process. [Figure 3] 10 is a flowchart showing a procedure for processing a printing job. [Figure 4] FIG. 10 is an explanatory diagram showing an example of a log storage setting acceptance screen. [Figure 5] FIG. 10 is an explanatory diagram illustrating an example of a log storage profile reception screen. [Figure 6] FIG. 4 is an explanatory diagram showing the timing of each operation when a print job is executed. [Figure 7] 10 is a flowchart showing a procedure for a scan-related job process. [Figure 8] FIG. 10 is an explanatory diagram showing an example of a scan function selection screen. [Figure 9] FIG. 10 is an explanatory diagram showing an example of a scan profile reception screen. [Figure 10] FIG. 10 is an explanatory diagram showing the timing of each operation when a scan-related job is executed. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, a multifunction peripheral (hereinafter referred to as "MFP") according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings. This embodiment discloses an MFP having an image processing function and a communication function.

[0011] 1, the MFP 1 of this embodiment includes a controller 10 including a CPU 11 and a memory 12. The MFP 1 also includes a user interface (hereinafter referred to as "user IF") 13, a communication interface (hereinafter referred to as "communication IF") 14, a print engine 15, and a scanner 16, which are electrically connected to the controller 10. The MFP 1 is an example of an image processing device.

[0012] The CPU 11 executes various processes in accordance with programs read from the memory 12 and based on user operations. Note that the controller 10 in Fig. 1 is a collective term for hardware and software used to control the MFP 1, and does not necessarily represent a single piece of hardware actually present in the MFP 1.

[0013] The memory 12 of the MFP 1 of this embodiment stores various programs and various data, including an operating system (hereinafter referred to as "OS") 21 and an image processing program 22. The memory 12 is also used as a work area when various processes are executed. The buffer provided in the CPU 11 is also an example of memory.

[0014] An example of memory is not limited to a ROM, RAM, HDD, etc. built into MFP 1, but may also be a storage medium that is readable and writable by CPU 11. For example, an external memory such as a USB memory or HDD connected to MFP 1 via communication IF 14, or a memory or HDD provided in a device connected to MFP 1 via communication IF 14 are also examples of memory.

[0015] Note that computer-readable storage media are non-transitory media. In addition to the above examples, non-transitory media also include storage media such as CD-ROMs and DVD-ROMs. Non-transitory media are also tangible media. On the other hand, electrical signals that carry programs downloaded from servers on the Internet are computer-readable signal media, which is a type of computer-readable medium, but are not included in non-transitory computer-readable storage media.

[0016] The user IF 13 includes hardware for displaying a screen for notifying the user of information and hardware for accepting user operations. The MFP 1 of this embodiment may be provided with a touch panel having a screen display function and an operation acceptance function as the user IF 13, or may be a combination of a display screen and operation buttons, or a combination of a touch panel and operation buttons. The user IF 13 is an example of an input interface.

[0017] The communication IF 14 includes hardware for communicating with external devices such as the log storage server 4 and the data storage server 6. The communication standards of the communication IF 14 include Ethernet (registered trademark), Wi-Fi (registered trademark), USB, etc. The MFP 1 may be equipped with multiple communication IFs 14 that support multiple communication standards.

[0018] The print engine 15 includes a configuration for printing an image on a print medium such as a sheet. The image formation method of the print engine 15 is, for example, an electrophotographic method or an inkjet method. The scanner 16 includes a configuration for reading an image of a document. The scanner 16 may be equipped with an automatic document feeder.

[0019] The MFP1 of this embodiment includes an embedded web server (hereinafter referred to as "EWS") 23 that contains programs and data for functioning as a web server. By accepting access to the EWS 23 from a device equipped with a web browser, such as a PC, the MFP1 can exchange various types of information with the PC via the EWS 23.

[0020] Next, the operation of the MFP 1 will be described. The following processes basically refer to the processing of the CPU 11 in accordance with instructions written in a program. In other words, processes such as "judging," "extracting," "selecting," "calculating," "deciding," "identifying," "acquiring," "receiving," and "control" in the following description represent the processing of the CPU 11. The processing by the CPU 11 also includes hardware control using an OS API. In this specification, the operation of each program will be described without mentioning the OS. In other words, in the following description, a statement to the effect that "program B controls hardware C" may also mean that "program B controls hardware C using the OS API." Furthermore, the processing of the CPU 11 in accordance with instructions written in a program may be described in abbreviated terms. For example, it may be described as "performed by CPU 11." Furthermore, the processing of the CPU 11 in accordance with instructions written in a program may be described in abbreviated terms, such as "performed by program A."

[0021] Note that "acquire" is used as a concept that does not require a request. In other words, the process of CPU 11 receiving data without a request is also included in the concept of "CPU acquiring data." Furthermore, "data" in this specification is represented by a bit string that can be read by a computer. Data with the same substantial meaning but different formats are treated as the same data. The same applies to "information" in this specification. Furthermore, "request" and "instruct" are concepts that indicate outputting information indicating a request or an instruction to the other party. Furthermore, information indicating a request or an instruction is also simply referred to as a "request" or "instruction."

[0022] Furthermore, the process by CPU 11 to determine whether information A indicates event B may be conceptually described as "determining whether event B is present from information A." The process by CPU 11 to determine whether information A indicates event B or event C may be conceptually described as "determining whether event B or event C is present from information A."

[0023] The procedure for job analysis processing by the image processing program 22 of the MFP 1 will be described with reference to the flowchart in Fig. 2. The job analysis processing is executed by the CPU 11 of the MFP 1 when an instruction to execute a job including image processing is accepted.

[0024] For example, in a standby state, the MFP 1 can display a standby screen on the user IF 13 and accept various instruction inputs via user operations on the displayed standby screen. The MFP 1 can also receive various commands transmitted from an external device, such as a PC, connected to the MFP 1. When the instruction input accepted via the user IF 13 or the command received from the external device via the communication IF 14 is an instruction to execute a job including image processing in the MFP 1, the MFP 1 executes job analysis processing based on the image processing program 22.

[0025] The CPU 11 determines whether the received execution instruction is an execution instruction for a print job or an execution instruction for a scan job (S101). A print job is an example of a print output job, and a scan job is an example of a file output job.

[0026] A print job is a job in which print data is generated from image data representing an image to be printed by image processing, and print engine 15 executes a print output based on the generated print data. MFP 1 accepts an instruction to execute a print job by receiving image data and a print command instructing the printing of the image data via communication IF 14, for example. MFP 1 can also accept an instruction to execute a print job by inputting an instruction via user IF 13.

[0027] Note that image data to be printed in an instruction to execute a print-related job via the user IF 13 corresponds to, for example, image data stored in memory 12, image data downloaded via communication IF 14, image data saved in a USB memory attached to MFP 1, and image data acquired by scanning a document set in scanner 16. In other words, instructions to execute FAX printing, stored printing, download printing, USB direct printing, copying, etc. are all instructions to execute a print-related job.

[0028] A scan-related job is a job that uses the scanner 16 to read multiple pages of a document, performs image processing to generate image data based on the images of the document, and then outputs an image file into which the generated image data is written. The MFP 1 receives an instruction to execute a scan-related job via the user IF 13, for example, when a document is placed on the scanner 16. In the instruction to execute a scan-related job, the MFP 1 receives a specification of the output destination of the generated image file. Note that an instruction to execute a copy may also be treated as an instruction to execute a scan-related job.

[0029] If the CPU 11 determines that the received instruction is an instruction to execute a print-related job (S101: print-related), it executes the print-related job processing (S111). On the other hand, if the CPU 11 determines that the received instruction is an instruction to execute a scan-related job (S101: scan-related), it executes the scan-related job processing (S121).

[0030] The procedure for processing a print-related job will be described with reference to the flowchart in Fig. 3. In processing a print-related job, the CPU 11 first determines whether or not a setting is made to save a log of the print-related job (S201). Various settings related to saving the log are registered in the MFP 1 in advance before an instruction to execute a job is received.

[0031] The MFP1 can accept various setting instructions related to log storage, for example, via the EWS 23. When the MFP1 accepts access to the EWS 23, it transmits web page data including various setting pages. An administrator who manages the MFP1 can access the EWS 23 of the MFP1 using, for example, an administration PC or the like, and display a web page related to log storage on the display of the administration PC or the like, thereby transmitting setting instructions related to log storage to the MFP1.

[0032] The web page data of the EWS 23 includes, for example, data showing a log storage setting reception screen 50, as shown in Fig. 4. The log storage setting reception screen 50 is a screen that receives the selection of log settings 51 and log storage profile settings 52 as log storage settings.

[0033] The MFP 1 accepts a setting for whether or not to save logs for each function in log settings 51. Log settings 51 on log save settings acceptance screen 50 shown in Fig. 4 includes, for example, radio button 511 for accepting a setting for whether or not to save operation log data and image log data for the scan function, and radio button 512 for accepting a setting for whether or not to save operation log data for the copy function and print function. The MFP 1 stores information on the various settings accepted via log save settings acceptance screen 50 in memory 12 as log save setting information 25, for example, as shown in Fig. 1.

[0034] The operation log data is log data related to the executed operations and is written to a log file as text data, for example. The image log data is log data based on image data generated by scanning in a scan job and is saved as an image log file, for example.

[0035] The MFP1 of this embodiment saves information on each item, such as the job function, execution date, execution time, the file name of the job execution target, the user name who issued the job execution instruction, output destination information, and number of pages, as operation log data. The file name is information indicating the file name of the print target for a print job other than a copy function, or the file name of the output target for a scan job. The output destination information is stored in the case of a scan job and indicates the output destination of the file. Note that the items included in the operation log data are not limited to these, and may also include, for example, information on print parameters and scan parameters received in the job execution instruction.

[0036] The MFP 1 accepts settings for log save profile settings 52 in log settings 51 on log save settings reception screen 50. As log save profile settings 52, the MFP 1 accepts the selection of a log save profile name and the selection of a file format for the log file in which operation log data is saved. In log save profile settings 52 on log save settings reception screen 50, the MFP 1 accepts the selection of a registered log save profile 27 (see FIG. 1). The various pieces of information accepted in log save profile settings 52 are parameters commonly used for saving logs regardless of the type of function for which logs are to be saved, and are an example of common parameters.

[0037] The MFP 1 can accept the registration of a log save profile via, for example, the EWS 23. For example, as shown in FIG. 5 , the web page data of the EWS 23 includes web page data of a log save profile reception screen 60 for accepting the setting of a log save profile. An administrator who manages the MFP 1 can display the log save profile reception screen 60 on the display of, for example, an administrative PC, and instruct the MFP 1 to register a log save profile. The MFP 1 stores the log save profile 27 in the memory 12 based on the information received via the log save profile reception screen 60. The log save profile reception screen 60 is an example of a setting screen.

[0038] 5, the log save profile reception screen 60 is a screen that receives the specification of a name 61, storage destination information 62, and authentication information 63 of the log save profile to be registered. The name 61 is information that is displayed as an option in the log save profile setting 52 on the log save setting reception screen 50 described above. The storage destination information 62 is information that indicates the storage destination where the operation log data and image log data are to be saved. The authentication information 63 is information required to access the log storage destination specified by the storage destination information 62. In other words, the log save profile 27 is information that includes the name 61, storage destination information 62, and authentication information 63.

[0039] 5, the log storage server 4 is specified as the storage destination in the storage destination information 62. In this case, the log storage server 4 is an example of a server, and the storage destination information 62 is information about the server and an example of access information. The storage destination information 62 corresponds to, for example, the file name of the log file to which the operation log data is written, the path to the folder of the log file, and the IP address of the log storage server 4. The authentication information 63 corresponds to, for example, a combination of the username and password of a user who is permitted to access the log storage server 4, or an access token. Note that if authentication information is not required to access the storage destination, the MFP 1 does not need to accept the authentication information 63.

[0040] The administrator can easily configure settings related to log storage because various parameters related to log storage are accepted by the log storage profile acceptance screen 60. The various parameters set by the log storage profile acceptance screen 60 can be selected collectively regardless of function in the log storage profile settings 52 on the log storage settings acceptance screen 50, making it easy for the administrator to manage the log storage settings.

[0041] Furthermore, an administrator who manages multiple devices can easily manage the devices by configuring the log files of each device to be stored in one log storage server 4. For example, the administrator can easily check the logs for each device by providing a folder and log file for each device to be managed in the log storage server 4 and specifying that folder or log file as the storage destination information 62 on the log storage profile reception screen 60 for each device. If the folder names and log file names are given with information that can identify each device, such as names that include the serial number, the relationship between the log files and the devices can be easily understood.

[0042] Returning to the description of the print-related job processing in Figure 3, if it is determined that the setting to save a log is not configured (S201: NO), the CPU 11 executes a normal print operation (S203) and does not generate or save a log. For example, if the log setting 51 shown in Figure 4 is accepted, the MFP 1 saves a log if the accepted job is a print function job, but does not save a log if the accepted job is a copy function job. After S203, the CPU 11 ends the print-related job processing and returns to the job analysis processing, thereby ending the job analysis processing.

[0043] On the other hand, if it is determined that the setting to save the log is enabled (S201: YES), the CPU 11 starts generating print data for the first page (S211, t2 in FIG. 6). FIG. 6 is a diagram schematically showing the processing order and elapsed time from the timing (t1) when an execution instruction is received for a print job including an image of three pages.

[0044] If the function to be executed is a print function, CPU 11 performs rasterization based on the PDL data to be printed, for example, to generate print data for printing. If the function to be executed is a copy function, CPU 11 operates scanner 16 and generates print data for printing based on the scan results. The print data is an example of image data representing a raster image to be printed.

[0045] After generating the print data for the first page (t3 in FIG. 6), the CPU 11 accesses the log storage server 4, which is set as the log storage destination, and starts the printing operation (S212, t4 in FIG. 6). The CPU 11 attempts to access the log file 41 (see FIG. 1), which is specified as the storage destination in the log storage profile setting 52, via the communication IF 14. The CPU 11 also starts the printing operation by passing the print data to the print engine 15.

[0046] Then, the CPU 11 determines whether or not access to the log storage server 4 was successful (S215). For example, if communication with the log storage server 4 is successful, the CPU 11 may determine that the access was successful. Alternatively, for example, if data requesting access is sent to the log storage server 4 and a reply is received from the log storage server 4 within a predetermined time, the CPU 11 may determine that the access was successful.

[0047] On the other hand, for example, if communication with the log storage server 4 fails, the CPU 11 may determine that the access has failed. Also, for example, if data requesting access is sent to the log storage server 4 and there is no response from the log storage server 4 within a predetermined time, the CPU 11 may determine that the access has failed. Also, for example, if name resolution or address resolution of the log storage server 4 fails, the CPU 11 may determine that the access has failed.

[0048] If it is determined that the access was not successful (S215: NO), the CPU 11 suspends the printing operation started in S212 (S216) and deletes the print data generated in S211 (S217). If the generation of print data for the next page has started, the CPU 11 also suspends that process. The CPU 11 may also delete the received image data, etc.

[0049] If it is determined that access to the log storage server 4 was successful (S215: YES), the CPU 11 writes part of the operation log data related to the currently executed print job to the specified log file 41 (S218). The part of the operation log data is information that is known at this point among the items of the operation log data, such as the function, execution date, execution time, file name, and user name, other than the number of printed pages.

[0050] Then, the CPU 11 determines whether or not the writing of the operation log data was successful (S219). For example, after sending an instruction to write to the log file 41, if a reply indicating that the writing was successful is received, the CPU 11 determines that the writing was successful.

[0051] If a log file 41 with the specified file name does not exist in the folder specified as the log file save destination, the CPU 11 may create a new log file 41 and write the log data therein, or may report an error. Specifically, for example, if the CPU 11 sends an instruction to write to the log file 41 to the log storage server 4 and receives an error response indicating that the log file 41 does not exist, the CPU 11 may send an instruction to create a new log file 41 and then resend an instruction to write to the created log file 41. On the other hand, if the CPU 11 sends an instruction to write to the log file 41 to the log storage server 4 and receives an error response indicating that the log file 41 does not exist, the CPU 11 may determine that the write attempt failed. Furthermore, for example, if the log storage server 4 receives an instruction to write to the log file 41 when the log file 41 does not exist, the CPU 11 may create a new log file 41, write the log data into it, and report a successful write.

[0052] On the other hand, for example, if the CPU 11 fails to send an instruction to write to the log file 41 to the log storage server 4, the CPU 11 may determine that the writing has failed. Furthermore, for example, if a reply indicating an error is received after sending an instruction to write to the log file 41, the CPU 11 may determine that the writing has failed. Furthermore, for example, if no reply is received within a predetermined time after sending an instruction to write to the log file 41, the CPU 11 may determine that the writing has failed. Furthermore, for example, similar to S215, if communication with the log storage server 4 fails, the CPU 11 may determine that the writing has failed. If the CPU 11 determines that the writing of the operation log data was not successful (S219: NO), the CPU 11 proceeds to S216, interrupts the printing operation, and deletes the print data.

[0053] After receiving an instruction to start the printing operation, the print engine 15 performs warm-up of each component, paper transport operations, etc. Therefore, for example, as shown in Fig. 6, the time (t4 to t5) required to attempt access to the log storage server 4 and write operation log data is often shorter than the time (t4 to t6) required from the start of the printing operation to the completion of printing on the first sheet. Therefore, if the parallel operations are started in S212 and then interrupted when a NO determination is made in S215 or S219, the possibility of completing printing of the first page without saving the log is low.

[0054] On the other hand, in this embodiment, the MFP1 generates the print data for the first page (t2 to t3 in Figure 6) before attempting to access the log storage server 4 or writing the operation log data (t4 in Figure 6), so there is little chance that the process for saving the log will cause a delay in the start of printing.

[0055] The MFP 1 of this embodiment saves part of the operation log data before completing the generation of print data for all pages, so even if a job is canceled before printing is completed due to a user operation to cancel the job or an error, a trace of the job remains in the log saving server 4. Therefore, the administrator of the MFP 1 can also keep track of jobs that have been canceled midway.

[0056] If it is determined that the operation log data has been successfully written (S219: YES), the CPU 11 continues the printing operation. Specifically, the CPU 11 determines whether or not there is a next page in the image to be printed for the job instructed to be executed (S221). If it is determined that there is a next page (S221: YES), the CPU 11 generates print data for the next page (S222) and continues the printing operation (S223).

[0057] If it is determined that there is no next page (S221: NO), that is, if it is determined that generation of print data for all pages of the job instructed to be executed has been completed, the CPU 11 adds and writes the remaining operation log data to the log file 41 to which some of the information was written in S218 (S225). The remaining operation log data is, for example, information on the number of pages to be printed.

[0058] 6, after completing printing of the third page (t7), the CPU 11 writes the remaining operation log data to the log file 41 (t8). The timing for writing the remaining operation log data is not limited to after printing of the final page is completed, and may be any timing after the timing (t9) when generation of the print data for the final page is completed. After S225, the CPU 11 may close the log file 41 to which the operation log data has been written, and disconnect from the log storage server 4.

[0059] After S217 and S225, the CPU 11 ends the print job processing, returns to the job analysis processing, and ends the job analysis processing. The MFP 1 displays a standby screen, for example, and goes into a standby state.

[0060] Next, the procedure for scan-related job processing, which is the processing performed when it is determined that the received instruction is an instruction to execute a scan-related job, will be described with reference to the flowchart in Fig. 7. In scan-related job processing, the CPU 11 determines whether or not a setting is made to save a log of the scan-related job (S301).

[0061] As in the case of print-related jobs, CPU 11 determines whether or not the setting for saving the log of a scan-related job is in place based on log saving setting information 25 stored in memory 12. For scan-related jobs, since it is possible to accept settings for saving both operation log data and image log data, CPU 11 determines that the setting for saving the log is in place when the setting for saving at least one of these is in place.

[0062] If it is determined that the setting is to save the log (S301: YES), the CPU 11 attempts to access the log save destination before operating the scanner 16. Specifically, similar to a print-related job, the CPU 11 reads the log save profile 27 selected in the log save profile setting 52 shown in Fig. 4 and acquires the save destination information 62 included in the log save profile 27. The CPU 11 attempts to access the log save server 4 specified as the save destination in the save destination information 62 (S302).

[0063] Then, CPU 11 determines whether the access was successful (S303). S303 is the same process as S215 in print-related job processing. Note that if the setting is such that both operation log data and image log data are saved, but the save destinations for the operation log data and the image log data are different, CPU 11 attempts to access both save destinations, and if access to both save destinations is successful, CPU 11 determines the access as successful in S303.

[0064] If it is determined that access to the log storage server 4 was not successful (S303: NO), the CPU 11 ends the scan-related job processing without operating the scanner 16, returns to the job analysis processing, and ends the job analysis processing. If the log storage server 4 cannot be accessed, the MFP 1 cannot save the log. If access to the log storage server 4 fails, the MFP 1 does not start a scan operation, thereby avoiding unnecessary operations.

[0065] If it is determined that access to the log storage server 4 was successful (S303: YES), the CPU 11 attempts to access the output destination of the image file based on the scan profile selected by the user (S305). For example, if the data storage server 6 is specified as the output destination of the image file, the CPU 11 attempts to access the data storage server 6 and determines whether the access was successful (S306).

[0066] When a scan function is selected on the standby screen, the MFP 1 displays a scan function selection screen 70 on the user IF 13, as shown in FIG. 8, to accept the designation of a scan profile for the scan job to be executed. The scan function selection screen 70 includes, for example, a scan profile selection field 71 and a start button 72, and is a screen that accepts the selection by the user who issues an instruction to execute the job. The scan function selection screen 70 is an example of a selection screen. In S305, when the start button 72 on the scan function selection screen 70 is operated, the CPU 11 acquires information about the output destination of the image file based on the scan profile selected in the scan profile selection field 71.

[0067] 1, the MFP 1 stores registered scan profiles 26 in the memory 12. The MFP 1 can register multiple scan profiles 26, and a scan profile selection field 71 on the scan function selection screen 70 is a field that accepts the selection of one of the scan profiles 26 registered in the MFP 1. The scan profile 26 includes information that specifies the output destination of the image file that is the read result, and information for creating the image file. The scan profile 26 is an example of a job profile.

[0068] The MFP 1 receives an instruction to register the scan profile 26, for example, via the EWS 23. The web page data of the EWS 23 includes, for example, web page data of a scan profile reception screen 80 for receiving instructions to set and register a scan profile, as shown in FIG. 9 . An administrator who manages the MFP 1 can display the scan profile reception screen 80 on the display of, for example, an administrative PC, and instruct the MFP 1 to register a scan profile. The MFP 1 stores the scan profile 26 in the memory 12 based on the information received via the scan profile reception screen 80.

[0069] 9, the scan profile reception screen 80 is a screen that receives the designation of a name 81 of the scan profile to be registered, output destination information 82, and parameters 83. The name 81 is information that is displayed as an option in the scan profile selection field 71 of the scan function selection screen 70 described above.

[0070] The output destination information 82 is information that indicates the output destination to which the image file resulting from the reading is output. As the output destination of the image file, for example, the data storage server 6 connected to the MFP 1 or a USB memory attached to the MFP 1 can be selected. In the example of FIG. 9, the data storage server 6 is specified as the output destination. In this case, the data storage server 6 is an example of storage. The output destination information 82 is an example of storage information and an example of an output destination parameter.

[0071] The parameters 83 are multiple pieces of information referenced by the MFP 1 in the processes from scanning to generating an image file. The parameters 83 include at least one piece of information, for example, parameters related to reading such as scan quality, parameters related to generating image data such as the cropping range, and parameters related to file generation such as the file name and file type of the image file to be generated. The parameters 83 are an example of file generation parameters.

[0072] If a scan profile 26, in which output destination information 82 and parameters 83 are associated, has been registered in advance in the MFP 1 by an administrator, a user instructing execution of a job can simply select the registered scan profile 26. In other words, a user of the MFP 1 can simply select a registered scan profile 26 in the scan profile selection field 71 on the scan function selection screen 70 shown in FIG. 8 and operate the start button 72, allowing for easy specification without needing to know detailed information and reducing the amount of work required. This also prevents users from specifying inappropriate output destinations or parameters, allowing the administrator to appropriately manage file output destinations and parameters. It is preferable that the registration and editing of scan profiles 26 be possible only with administrator privileges or using a dedicated program installed on an administrator's PC, etc., and not available to general users.

[0073] Returning to the explanation of the scan-related job processing in Figure 7, if it is determined that access to the data storage server 6 was not successful (S306: NO), the CPU 11 ends the scan-related job processing without operating the scanner 16, returns to the job analysis processing, and ends the job analysis processing. If the data storage server 6 cannot be accessed, the MFP 1 cannot output an image file even if it has been generated. If access to the data storage server 6 fails, the MFP 1 can avoid unnecessary operations by not starting a scan operation.

[0074] If it is determined that access to both the log storage server 5 and the data storage server 6 was successful (S306: YES), the CPU 11 operates the scanner 16 to start reading the document and generating image data (S311). In S311, the CPU 11 causes the scanner 16 to execute a scan using parameters specified in the selected scan profile 26. That is, after successfully accessing the log storage server 5 (t12 to t13 in FIG. 10), the CPU 11 starts generating image data (t14 in FIG. 10). FIG. 10 is a diagram schematically showing the processing order and elapsed time from the timing (t11) when an execution instruction is received for a scan-related job to read a three-page document.

[0075] The CPU 11 reads the documents in order from the first page, and generates image data based on the reading results. For example, when documents are inserted into the automatic document feeder, the scanner 16 reads the inserted documents in order from the first page, and when no documents are inserted into the automatic document feeder, the scanner 16 reads the documents placed on the flatbed one by one. Then, the CPU 11 determines whether reading of all pages of the documents has been completed (S312). If it determines that there are documents that have not been read (S312: NO), the CPU 11 continues the reading operation until reading of all pages has been completed.

[0076] If it is determined that reading of all pages has been completed (S312: YES, t15 in FIG. 10), the CPU 11 generates an image file by writing the image data of all pages generated by reading into the image file (S313). The CPU 11 generates the image file using parameters specified in the scan profile 26 selected in the scan execution instruction, and temporarily stores the image file in the memory 12.

[0077] After generating the image file, the CPU 11 saves the log determined in S301 to be set to be saved (t16 to t17 in FIG. 10). The CPU 11 determines whether or not the setting to save operation log data is set (S321). If it determines that the setting to save operation log data is set (S321: YES), the CPU 11 opens the log file 41, which is the save destination for the operation log data, and writes information about the currently executed scan-related job, thereby saving the operation log data (S322). The operation log data for a scan-related job is an example of parameters used for reading. The CPU 11 then determines whether or not the saving of the operation log data was successful (S323).

[0078] If it is determined that the setting to save the operation log data is not enabled (S321: NO), or if it is determined that the setting to save the operation log data is successful (S323: YES), the CPU 11 determines whether the setting to save the image log data is enabled (S325).

[0079] If it is determined that the setting for saving image log data is enabled (S325: YES), CPU 11 generates an image log file for saving the image log data in the folder designated as the destination for saving the image log data, and writes the image log data based on the image data acquired by scanning (S326). Note that MFP 1 stores in advance a generation rule for generating an image log file name for saving the image log data, and generates an image log file with that file name in the folder designated as the destination for saving the image log data. CPU 11 then determines whether or not the image log file was successfully saved (S327). S323 and S327 are the same processes as S219 in the print job processing.

[0080] The image log file may be the image file itself generated in S313 to be sent, a file containing image data generated by scanning, or a file containing data that has been processed by image processing such as reduction or monochrome conversion. Furthermore, when multiple pages are scanned and image data for multiple pages is generated, the image log file may be a single file containing the image data for all pages, multiple files for each page, or a file based on the image data for some pages. By storing data based on the scanned image data in the log, the administrator can check what images were scanned, for example, whether highly confidential documents were scanned.

[0081] If it is determined that the setting to save the image log data is not enabled (S325: NO), or if it is determined that the image log data has been successfully saved (S327: YES), the CPU 11 outputs the image file generated in S313 to the output destination specified in the scan profile 26 selected in the scan execution instruction (S329, t18 in Figure 10).

[0082] After S329, or if it is determined that the operation log data was not successfully saved (S323: NO), or if it is determined that the image log data was not successfully saved (S327: NO), the CPU 11 deletes the image file generated in S313 from the memory 12 (S331). If the log was not successfully saved, the CPU 11 does not output the image file.

[0083] In the case of a scan-related job, image data for all pages is output together as an image file, so if the job is interrupted midway, even if there is scanned image data, none of the page's image data will be output. In the case of a scan-related job, there is little need to leave a trace of the job midway. The MFP1 of this embodiment outputs the image file only if the log has actually been successfully saved, so it is possible to avoid outputting the image file without saving the log related to the scan-related job.

[0084] On the other hand, if it is determined that the setting to save scan-related logs is not enabled (S301: NO), the CPU 11 attempts to access the data storage server 6 that is specified as the output destination of the image file in the selected scan profile 26 (S351). Then, the CPU 11 determines whether the access was successful (S352).

[0085] If it is determined that the data storage server 6 has been accessed (S352: YES), the CPU 11 executes a normal scan (S353). Specifically, the CPU 11 operates the scanner 16 to read the document based on the scan profile 26 and generate image data based on the read results. Furthermore, when scanning of all pages is completed, the CPU 11 generates an image file containing the image data and transmits the image file to the data storage server 6.

[0086] After S353, or if it is determined that the data storage server 6 could not be accessed (S352: NO), the CPU 11 ends the scan-related job processing, returns to the job analysis processing, and ends the job analysis processing. Note that if the data storage server 6 could not be accessed, the CPU 11 may display an error message on the user IF 13.

[0087] As described above in detail, when the MFP 1 of this embodiment receives an instruction to execute a scan-related job, it checks access to the log storage server 4 before outputting an image file, and cancels the scan-related job if it cannot access the log storage server 4, and also cancels the scan-related job if it cannot save the log in the log storage server 4. This reduces the situation where a log related to the executed scan-related job is not saved in the log storage server 4 despite the scan-related job having been executed.

[0088] Furthermore, the MFP 1 of this embodiment attempts to access the log storage server 4 before starting to read an original, and if access is not possible, does not start reading, thereby avoiding unnecessary scanning operations.

[0089] Furthermore, in this embodiment, the MFP1 stores common access information in advance in memory 12 when confirming access to the log storage server 4 and when saving logs, so by using this access information, the log is reliably saved in the desired server.

[0090] Furthermore, the MFP1 of this embodiment accepts settings of various parameters related to log storage via the EWS 23 and stores the accepted parameters in memory 12, allowing an administrator to set various parameters using an administrative PC, etc., making management easy. Also, the MFP1 can register parameters related to file output for scan-related jobs separately from parameters related to log storage, making it easy for users of the MFP1 to select parameters when executing scan-related jobs.

[0091] It should be noted that the present embodiment is merely an example and does not limit the present invention in any way. Therefore, the technology disclosed in this specification can naturally be improved and modified in various ways without departing from the spirit and scope of the present invention. For example, the log storage server and data storage server are not limited to one unit, and multiple units may be used. Furthermore, for example, the image processing device is not limited to an MFP as long as it has at least a scanning function and a communication function, and may be a scanner, copier, or fax machine.

[0092] Furthermore, the screens illustrated in each figure are merely examples, and the display format is not limited to the illustrated examples. For example, the wording of messages and the shapes of buttons, etc. displayed on each screen are not limited to the illustrated examples. Furthermore, while examples of various setting screens displayed on the display of a PC or the like via the EWS 23 have been described in FIGS. 4, 5, 8, and 9 assuming that the MFP 1 includes the EWS 23, the MFP 1 may not include the EWS 23. For example, the MFP 1 may display various setting screens on the user IF 13 and accept various settings from an administrator managing the MFP 1 via the user IF 13. Furthermore, the MFP 1 may accept various settings from an administrator managing the MFP 1 by commands transmitted from an application installed in the PC or the like.

[0093] Furthermore, the configuration of the folder in which logs are saved is not limited to one for each managed device. For example, logs for multiple devices may be written to a single folder. In this case, the MFP 1 may write logs to different log files for each device, may write logs for multiple devices to a single log file, or may write logs to a single log file for each job execution date, regardless of the device.

[0094] In addition, in this embodiment, an example has been described in which operation log data is added and written to the log file 41 prepared in the log storage server 4 in S218 and S225 of print job processing and S323 and S327 of scan job processing, but it may also be configured, for example, so that the MFP 1 generates a log file into which operation log data is written for each job and sends the log file to a specified folder.

[0095] In addition, in this embodiment, an example has been shown in which image data for all pages is output as a single image file for a scan-related job, but multiple files in which image data is written for each page may be output. Also, in this embodiment, various settings such as the output destination of files for a scan-related job are selected from registered scan profiles in the scan profile selection field 71 on the scan function selection screen 70 shown in Fig. 8, but these may also be accepted when issuing an instruction to execute scanning.

[0096] Furthermore, the timing for checking access to the log storage server 4 for a print job is not limited to when generation of the print data for the first page is completed, but may be any time after generation of image data for the first page has started and before output of the image data for the first page. For example, access may be checked when it is determined that the received data is a print job during analysis of the data, or when rasterization begins.

[0097] In addition, in this embodiment, an example has been shown in which the operation log data for a print-related job is saved twice in S218 and S225 of the print-related job processing, but this is not limited to this. For example, S225 may be deleted, and only the information acquired in S218 of the print-related job processing may be saved as operation log data, with the remaining information not being saved. Furthermore, for example, if access to the log storage server 4 is successful, the printing operation may continue without writing in S218 or making the judgment in S219, and all operation log data may be saved in S225. Furthermore, instead of checking access to the log storage server 5 and starting the printing operation in parallel in S212, the access check may be performed first, and the printing operation may be started if the access is successful.

[0098] Furthermore, in scan-related job processing, the timing of the access confirmation to the log storage server 4 (S303) for scan-related jobs may be any time between the time when the execution instruction is received and the time when the image data of the first page is output (S329), and is not limited to the time before the reading of the first page starts. For example, it may be started in parallel with the reading of the document (S311), or after the reading of the document has been completed (YES in S312).

[0099] In addition, in this embodiment, the log setting 51 shown in Figure 4 is an example in which the user is asked to select whether or not to save a log for each of the scan function, copy function, and print function, but it is sufficient if at least the log for the scan function can be saved, and the log saving function for the copy function and print function does not have to be provided.

[0100] Furthermore, in any flowchart disclosed in the embodiments, the execution order of multiple processes in any multiple steps can be arbitrarily changed or can be executed in parallel, as long as no contradiction occurs in the processing content.

[0101] The processes disclosed in the embodiments may be executed by hardware such as a single CPU, multiple CPUs, or ASIC, or a combination thereof. The processes disclosed in the embodiments may be realized in various ways, such as a storage medium storing a program for executing the processes, or a method. [Explanation of symbols]

[0102] 1 MFP 12 Memory 13 User Interface 14 Communication Interface 16 Scanner

Claims

1. An image processing device equipped with a scanner, The image processing device includes: a file output job can be executed, the file output job being a job including reading a document of a plurality of pages by the scanner, generating image data of a plurality of pages based on the document of the plurality of pages that has been read, and outputting a file into which the generated image data has been written to a specified output destination; Furthermore, the image processing device When the file output job is executed, a log relating to the file output job is stored in a server, Furthermore, the image processing device storing common parameters commonly used for accessing the server in a memory of the image processing device, the common parameters including access information for accessing the server; Furthermore, the image processing device output destination parameters for outputting the file to a specified output destination are stored in the memory of the image processing device separately from the common parameters, and the output destination parameters include storage information indicating a storage to which the file is to be output; Furthermore, the image processing device In response to receiving an instruction to execute the file output job via an input interface of the image processing apparatus, confirming whether or not the server can be accessed using the common parameters stored in the memory; If the server cannot be accessed, the file is not output to the specified output destination, and the execution of the file output job is stopped. When the server is accessible, before outputting the file into which the generated image data is written to a specified output destination, the log relating to the file output job is transmitted to the server using the common parameters stored in the memory; If the transmitted log can be saved in the server, the file into which the generated image data is written is output to a specified output destination using the output destination parameter stored in the memory; If the transmitted log cannot be saved on the server, the file is not output to the specified output destination, and the execution of the file output job is stopped. Furthermore, the image processing device a selection screen is displayed on a display, allowing a plurality of output destination parameters to be registered, and allowing the user to select one of the registered output destination parameters; Furthermore, the image processing device A plurality of job profiles can be registered, and the job profiles are associated with the output destination parameters and file generation parameters for file generation. One of the registered job profiles is selected on the selection screen, and the output destination parameters included in the job profile selected on the selection screen are stored in the memory of the image processing device. An image processing device configured as follows.

2. 2. The image processing device according to claim 1, Furthermore, the image processing device In response to receiving an instruction to execute the file output job via the input interface of the image processing apparatus, before starting to read an original, it is confirmed whether or not the server can be accessed; If the server cannot be accessed, the execution of the file output job is stopped without starting to read the document. When the server is accessible, the document reading is started, the image data is generated, and then the log relating to the file output job is transmitted to the server before the file into which the generated image data is written is output. If the transmitted log can be saved in the server, the file containing the generated image data is output to a specified output destination; If the transmitted log cannot be saved in the server, the file is not output to the specified output destination, and the execution of the file output job is stopped. An image processing device configured as follows.

3. In the image processing device according to claim 1 or claim 2, The image processing device includes: displaying a setting screen for setting the common parameters on a display, and storing the common parameters input on the setting screen in the memory of the image processing device; Furthermore, the image processing device In response to receiving an instruction to execute the file output job via the input interface of the image processing device, confirming whether or not the server can be accessed using the common parameters stored in the memory; If the server cannot be accessed, the file is not output to the specified output destination, and the execution of the file output job is stopped. When the server is accessible, before outputting the file into which the generated image data is written to a specified output destination, the log relating to the file output job is transmitted to the server using the common parameters stored in the memory; If the transmitted log can be saved in the server, the file containing the generated image data is output to a specified output destination; If the transmitted log cannot be saved in the server, the file is not output to the specified output destination, and the execution of the file output job is stopped. An image processing device configured as follows.

4. In an image processing device according to any one of claims 1 to 3, The image processing device includes: A print job can be executed, the print job being a job including generation of the image data for a plurality of pages representing a raster image for printing, and print output based on the raster image represented by the generated image data, Furthermore, the image processing device When the print job is executed, a log relating to the print job is also stored in the server, Furthermore, the image processing device In the case of the print output job, before starting to print out the raster image represented by the generated image data, confirming whether or not the server can be accessed using the common parameters stored in the memory; If the server is accessible, transmitting the log relating to the print output job to the server and initiating print output of the raster image represented by the generated image data; If the server cannot be accessed, the print output job is stopped without starting the print output of the raster image represented by the generated image data; In the case of the file output job, In response to receiving an instruction to execute the file output job via the input interface of the image processing device, confirming whether or not the server can be accessed using the common parameters stored in the memory; If the server cannot be accessed, the file is not output to the specified output destination, and the execution of the file output job is stopped. When the server can be accessed, before outputting the file into which the generated image data is written to a specified output destination, the log relating to the file output job is transmitted to the server using the common parameters stored in the memory. An image processing device configured as follows.

5. 5. The image processing device according to claim 1, Furthermore, the image processing device In response to receiving an instruction to execute the file output job via the input interface of the image processing device, it is confirmed whether or not the server can be accessed; If the server cannot be accessed, the file is not output to the specified output destination, and the execution of the file output job is stopped. When the server can be accessed, before outputting the file into which the generated image data is written to a specified output destination, parameters used for reading and data based on the generated image data are transmitted to the server as the log related to the file output job; If the transmitted log can be saved in the server, the file containing the generated image data is output to a specified output destination; If the transmitted log cannot be saved in the server, the file is not output to the specified output destination, and the execution of the file output job is stopped. An image processing device configured as follows.

Images