Image processing device and control method for the image processing device
Patent Information
- Application Number
- JP2022153144
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-09-26
- Publication Date
- 2026-10-13
- Estimated Expiration
- 2042-09-26
AI Technical Summary
【0007】 本発明によれば、留置スキャンジョブの実行時のエラーにより、ユーザに無駄な作業が生じることを抑制することができる。
Smart Images

Figure 0007933607000001 
Figure 0007933607000002 
Figure 0007933607000003
Abstract
Description
Technical Field
[0001] The present invention relates to an image processing apparatus including a storage device and a scanner, and a control method for the image processing apparatus.
Background Art
[0002] In recent years, cases where a storage server such as a cloud is used as a destination for images scanned by an image processing apparatus have been increasing. In addition, by generating a reserved scan job including scan settings, a transmission destination of the storage server, and authentication information for accessing the storage server in advance on a client terminal, and submitting the reserved scan job to the image processing apparatus, scanning on the image processing apparatus can be easily performed. The client terminal is a PC, a smartphone, or the like. In the image processing apparatus, by simply placing a document and executing the reserved scan job submitted from the client terminal, the document can be transmitted to a desired storage server with desired settings. When executing a scan job on the image processing apparatus, a transmission error may occur. Causes of the transmission error include a case where access to the destination storage server is prohibited for operational reasons, a case where the destination cannot be accessed due to an incorrect network setting, and the like. Patent Document 1 discloses a unit that notifies an external terminal when an error is detected in a scan job.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problem to be Solved by the Invention
[0004] However, in reserved scanning, if an error is notified after the scan job is executed as in Patent Document 1, user actions such as moving to the image processing apparatus for executing the reserved scan job, placing a document, and selecting the reserved scan job to be executed are wasted.
[0005] The present invention aims to prevent users from having to perform unnecessary tasks due to errors during the execution of a storage scan job. [Means for solving the problem]
[0006] To solve the above problems, the present invention provides an image processing apparatus comprising a storage device and a scanner, the apparatus comprising: confirmation means for confirming whether a file containing an image generated by a scanning process performed by the scanner can be sent to a destination specified by a client terminal; notification means for notifying the client terminal of the confirmation result when it is confirmed by the confirmation means that the file cannot be sent to the destination; and storage means for saving a job including the settings for the scanning process and the destination of the file containing the image generated by the scanning process to the storage device, wherein the notification means notifies the client terminal of identification information corresponding to the job based on the confirmation result when it is confirmed that the file can be sent to the destination. [Effects of the Invention]
[0007] According to the present invention, it is possible to suppress unnecessary work for the user due to errors during the execution of a stationary scan job. [Brief explanation of the drawing]
[0008] [Figure 1] This diagram shows an example of the system configuration. [Figure 2] This diagram shows the hardware configuration of the control unit of the image processing device. [Figure 3] This diagram shows the hardware configuration of the control units for the authorization server and the storage server. [Figure 4] This diagram shows the hardware configuration of the control unit of the client terminal. [Figure 5] This diagram shows the software configuration of the image processing device. [Figure 6]This is a sequence diagram illustrating the sequence of steps in the implantation scan process in the first embodiment. [Figure 7] This is a sequence diagram illustrating the sequence of steps in the implantation scan process in the first embodiment. [Figure 8] This figure shows an example of the implantation scan setting screen in the first embodiment. [Figure 9] This figure shows an example of a configuration for an implanted scan job. [Figure 10] This figure shows an example of the results screen when the request for implantation scan is successful. [Figure 11] This figure shows an example of the indwelling scan selection screen. [Figure 12] This figure shows an example of the in-dwelling scan execution screen. [Figure 13] This is a sequence diagram illustrating the sequence of steps in the implantation scan process in the first embodiment. [Figure 14] This figure shows an example of a result screen when the request for implantation scan fails. [Figure 15] This figure shows a flowchart illustrating the process of a retained scan in a client terminal according to the first embodiment. [Figure 16] This figure shows a flowchart illustrating the process of a retained scan in a client terminal according to the first embodiment. [Figure 17] This flowchart shows the processing of the MFP upon receiving a storage scan request according to the first embodiment. [Figure 18] This is a flowchart showing the process of implantation scanning in the MFP according to the first embodiment. [Figure 19] This is a sequence diagram illustrating the sequence of steps in the implantation scan process in the second embodiment. [Figure 20] This is a sequence diagram illustrating the sequence of steps in the implantation scan process in the second embodiment. [Figure 21] This figure shows an example of the implantation scan setting screen in the second embodiment. [Figure 22]FIG. 11 is a diagram showing an example of a result screen of pre-transmission confirmation in the second embodiment. [Figure 23] FIG. 12 is a flowchart illustrating processing of retention scanning in the client terminal according to the second embodiment. [Figure 24] FIG. 13 is a flowchart illustrating processing of retention scanning in the client terminal according to the second embodiment. [Figure 25] FIG. 14 is a flowchart illustrating processing of the MFP that has received a request according to the second embodiment. [Description of Embodiments]
[0009] (First Embodiment) FIG. 1 is a diagram illustrating a configuration example of a system of the present embodiment. The system provides a scan service in which an image processing apparatus including a storage device and a scanner, a client terminal such as a PC or a smartphone, an authorization server, and a storage server cooperate with one another. The system in the present embodiment includes an MFP 100, an authorization server 110, a storage server 120, and a client terminal 130. The MFP 100, the authorization server 110, the storage server 120, and the client terminal 130 are connected to each other via a network 140.
[0010] An MFP (Multifunction Peripheral) 100 is an image processing apparatus including a storage device and a scanner. The MFP 100 has functions of, for example, reading an image with the scanner and printing an image with a printer, and in the present embodiment, is capable of executing retention scanning and saving a scanned image in a designated external storage. The MFP 100 includes an operation unit 102, a control unit 101, a printer unit 103, a scanner unit 104, a retention scan application 105, and a storage device 106. Note that the MFP 100 may have other functions such as a facsimile function and a box function, or may not have a printer function.
[0011] The scanner unit 104 optically reads documents placed on a document glass or ADF (Auto Document Feeder) (not shown) and generates image data (image files) as electronic data. Furthermore, the MFP 100 in this embodiment is capable of performing a retained scan process. A retained scan process involves saving (retaining) a retained scan job in the non-volatile area of the MFP 100, and then executing the job by a logged-in user who specifies the job and issues an execution command. This process includes scanning and transmission. A retained scan job is sent from the client terminal 130 to the MFP 100 as a scan ticket containing scan settings, destination (storage location), and a token. The retained scan application 105 performs processing related to the retained scan application. For example, the retained scan application 105 saves retained scan jobs received from the client terminal 130 to the storage device 106. The retained scan application 105 also executes retained scans based on the retained scan jobs stored in the MFP 100. Furthermore, the stationary scan application 105 of this embodiment also performs a process to check (verify) whether the images generated by the stationary scan can be sent to the storage 122 where they are stored. The storage device 106 can store stationary scan jobs received from the client terminal 130. The storage device 106 also stores a database containing user information for the image processing device. User information for the image processing device is used for user authentication performed when using the MFP 100.
[0012] The printer unit 103 forms an image according to the received print job and outputs it to paper, or optically reads the original image set in the scanner unit 104 and outputs it to paper. The operation unit 102 receives operations from the user and displays information to the user. The operation unit 102 is, for example, a touch panel, and the user gives instructions to the MFP 100, such as job execution instructions, on the user interface screen displayed on the touch panel. The control unit 101 controls the entire MFP 100. The operation unit 102, printer unit 103, scanner unit 104, and storage device 106 are connected to the control unit 101 and realize each function of the multifunction device according to the control of the control unit 101.
[0013] The storage server 120 provides a cloud storage service for storing various types of data. In this embodiment, the storage server 120 stores image data generated by scanning with the MFP 100. The storage server 120 includes a storage application 121 and storage 122. The storage application 121 receives instructions from the client terminal 130 and performs various processes such as saving files to storage 122 and returning a list of files and directories stored in storage 122. Storage 122 stores files such as image data. The services and functions provided by the storage server 120 may be realized by one or more information processing devices, a virtual machine (cloud service) utilizing resources provided by a data center including information processing devices, or a combination thereof.
[0014] The authorization server 110 manages the authority of clients to access the storage server 120. The authorization server 110 has an authorization application 111. In this embodiment, an example is described in which the authorization application 111 exchanges authorization information in accordance with the OAuth mechanism specified in RFC6479, but it is not limited to this. The authorization application 111 issues an access token containing authorization information, and the client terminal 130 uses the access token to receive services from the resource server, the storage server 120.
[0015] When client terminal 130 requests access to storage server 120 with appropriate authentication information, authorization application 111 issues an access token to client terminal 130 to grant access rights to storage server 120. Client terminal 130 uses the issued access token to request access to storage server 120. Storage server 120 verifies the validity of the access token passed from client terminal 130 to authorization server 110. Authorization server 110 determines the validity of the access token and returns the result to storage server 120. If the access token is valid, storage server 120 accepts access from client terminal 130. On the other hand, if the access token is not valid, it rejects access from client terminal 130. The services and functions provided by authorization server 110 may be implemented by one or more information processing devices, virtual machines (cloud services) utilizing resources provided by a data center including information processing devices, or a combination of these.
[0016] The client terminal 130 is an information processing device such as a smartphone or a PC. The client terminal 130 has a fixed scan application 131. The fixed scan application 131 creates a fixed scan job for performing a fixed scan on the MFP 100. The scan job includes one or more settings necessary for the scan process performed by the scanner and the process of sending the file containing the image generated by the scan process. Specifically, the scan ticket in this embodiment includes information on scan settings and the save location of the scanned image file. The fixed scan application 131 sends the configured scan job to the MFP 100.
[0017] Network 140 may consist of any of the following: a communication network such as a LAN or WAN, a cellular network (e.g., LTE or 5G), a wireless network, Wi-Fi (registered trademark), a telephone line, a dedicated digital line, or a combination thereof. The networks to which the MFP 100, authorization server 110, storage server 120, and client terminal 130 are connected do not all have to be of the same type. For example, the MFP 100, authorization server 110, and storage server 120 may be connected to the internet via a wired connection, while the client terminal 130 is connected via a data communication line. In other words, network 140 only needs to be configured to enable data transmission and reception, and any communication method may be adopted.
[0018] Figure 2 shows the hardware configuration of the control unit 101 of the MFP100. The control unit 101 includes a CPU 201, DRAM 202, I / O controller 203, network I / F 204, SARAI / F 205, panel I / F 206, printer I / F 207, scanner I / F 208, and FlashROM 209. The CPU 201 controls the entire MFP100 by performing arithmetic processing. The CPU 201 is connected to the DRAM 202 via a bus. The DRAM 202 is used by the CPU 201 as working memory to temporarily store program data representing arithmetic instructions and data to be processed during the calculation process. The CPU 201 is also connected to the I / O controller 203 via a bus. The I / O controller 203 controls input and output to various devices such as the operation unit 102, printer unit 103, scanner unit 104, and external devices according to the instructions of the CPU 201.
[0019] The I / O controller 203 connects to the storage device 106, which is a FlashROM 209, via a SATA (Serial Advanced Technology Attachment) interface 205. The CPU 201 uses the FlashROM 209 to store programs, document files, stored scan jobs, scanned images, etc., for implementing the functions of the MFP100. Alternatively, a large-capacity storage device such as an HDD may be connected to the SATA interface 205 instead of the FlashROM 209.
[0020] The I / O controller 203 is connected to the network interface 204, panel interface 206, printer interface 207, and scanner interface 208. Network 140 is connected to the network interface 204. The CPU 201 communicates with external devices such as client terminals 130 and storage servers 120 connected to network 140 via the network interface 204 and network 140. The CPU 201 provides user input / output to the control unit 102 via the panel interface 206. The CPU 201 performs printing using the printer unit 103 via the printer interface 207. The CPU 201 performs scanning using the scanner unit 104 via the scanner interface 208.
[0021] Here, we will explain an example of how the MFP100 performs its copy function. The CPU201 reads program data from the FlashROM209 into the DRAM202 via the SATAI / F205. The CPU201 detects a copy instruction from the user to the operation unit 102 via the panelI / F206, according to the program read into the DRAM202. Upon detecting the copy instruction, the CPU201 receives the original document as electronic data from the scanner unit 104 via the scannerI / F208 and stores it in the DRAM202. The CPU201 performs image processing, such as color conversion processing suitable for output, on the image data stored in the DRAM202. The CPU201 then sends the processed image data stored in the DRAM202 to the printer unit 103 via the printerI / F207 and performs the output process to paper media.
[0022] Next, we will describe an example of the MFP100 performing the transmission function. The process by which the CPU201 detects a transmission instruction from the user is the same as that for the copy function described above. The transmission instruction includes the transmission protocol, destination specification, and image format specified by the user. The transmission protocol may be SMB or FTP, and the destination specification may be UNC (Universal Naming Convention), for example. The image format may be JPEG or PDF. When the CPU201 detects a transmission instruction, it receives the original document as electronic data from the scanner unit 104 via scanner 1 / F208 and stores it in DRAM202. The CPU201 performs image format conversion and other operations on the image data stored in DRAM202 according to the user's specifications. The CPU201 sends the image data stored in DRAM202 to the destination via network I / F204 using the protocol specified by the user and saves it. Alternatively, the storage server 120 may be specified as the destination, and transmission may be performed using an authorization mechanism with an access token.
[0023] Figure 3 shows the hardware configuration of the authorization server 110 and the storage server 120. Below, an example of the configuration of the authorization server 110 is described. The storage server 120 also has a computer configuration similar to the authorization server 110, including a processor (CPU) and memory. The authorization server 110 includes a CPU 301, DRAM 302, I / O controller 303, network interface 304, SATA interface 305, and HDD 306.
[0024] The CPU 301 controls the entire authorization server 110. The CPU 301 is connected to the DRAM 302 via a bus. The DRAM 302 is used by the CPU 301 as working memory to temporarily store program data representing arithmetic instructions and data to be processed during the calculation process. The CPU 301 is also connected to the I / O controller 303 via a bus.
[0025] The I / O controller 303 controls input and output to the network interface 304 and SATA interface 305 according to instructions from the CPU 301. The I / O controller 303 connects to the network interface 304. The network interface 304 connects to the network 140. The CPU 301 communicates with external devices on the network 140 via the network interface 304 and the network 140. The I / O controller 303 connects to the HDD 306 via the SATA (Serial Advanced Technology Attachment) interface 305. The HDD 306 is an example of storage. In the authorization server 110, the HDD 306 stores programs such as the authorization application 111 and settings. In the storage server 120, the HDD 306 stores programs such as the storage application 121 and settings, as well as image data received from the MFP 100.
[0026] In this embodiment, for illustrative purposes, we illustrate a case where one CPU 301 uses one memory (DRAM 302) to perform each of the processes shown in the flowchart described later, but other configurations are also possible. For example, multiple processors, RAM, ROM, and storage can work together to execute each of the processes shown in the flowchart described later. Alternatively, multiple server computers can be used to execute each of the processes.
[0027] Figure 4 is a block diagram showing the hardware configuration of the client terminal 130. The client terminal 130 includes a CPU 401, DRAM 402, I / O controller 403, network interface 404, SATA interface 405, Flash ROM 406, and panel interface 407. The CPU 401 controls the entire client terminal 130. The CPU 401 is connected to the DRAM 402 via a bus. The DRAM 402 is used by the CPU 401 as working memory to temporarily store program data representing arithmetic instructions and data to be processed during the calculation process.
[0028] The CPU 401 also connects to the I / O controller 403 via a bus. The I / O controller 403 controls input and output to the network interface 404, SATA interface 405, and panel interface 407 according to instructions from the CPU 401. The I / O controller 403 connects to the network interface 404. The network interface 404 connects to network 140. The CPU 401 communicates with external devices on network 140 via the network interface 404 and network 140.
[0029] The I / O controller 403 connects to the FlashROM 410, which is a storage device, via the SATA (Serial Advanced Technology Attachment) I / F 405. Note that the storage device is not limited to FlashROM; a large-capacity storage device such as an HDD may also be used. The FlashROM 410 is used to store programs such as the fixed scan application 131 and various setting values. The I / O controller 403 also connects to the panel I / F 406. The CPU 401 provides user-facing input / output to the control panel of the client terminal 130, which is connected via the panel I / F 406. The control panel may include, for example, a touch panel or a camera that reads images.
[0030] Figure 5 shows the software configuration of the MFP100. The software configuration of the MFP100 is realized when the CPU 201 of the control unit 101 reads the program stored in the Flash ROM 211 into the DRAM 202 and then executes it. The MFP100 includes an operation control unit 501, a data storage unit 502, a job control unit 503, an image processing unit 504, a printing processing unit 505, a reading processing unit 506, a network control unit 507, and a fixed scan control unit 508.
[0031] The operation control unit 501 controls the display and operation reception on the operation unit 102. Specifically, the operation control unit 501 displays a user-facing screen image on the operation unit 102. The operation control unit 501 also detects user operations and executes processes associated with screen components such as buttons displayed on the screen. The data storage unit 502 controls recording to and reading from the storage device 106, which is the Flash ROM 211. For example, the data storage unit 502 stores scanned images generated by requests from other units or scanning processes in the Flash ROM 211.
[0032] The job control unit 503 controls the execution of jobs. The image processing unit 504 processes image data into a format suitable for its intended use, according to instructions from the job control unit 503. The printing processing unit 505 controls the printing process by the printer unit 103. Specifically, the printing processing unit 505 prints and outputs images onto paper media via the printer interface 207, according to instructions from the job control unit 503.
[0033] The reading processing unit 506 controls the scanning process performed by the scanner unit 104. Specifically, the reading processing unit 506 reads the set document via the scanner interface 208 according to instructions from the job control unit 503. The network control unit 507 controls the input and output of data to and from external devices via the network interface 204 and the network 140. In addition, the network control unit 507 enables the data storage unit 502 to access the data stored in the Flash ROM 209 from external devices. An example of data stored in the Flash ROM 209 is image data such as PDF and JPEG.
[0034] The retained scan control unit 508 controls the processing related to retained scans. For example, the retained scan control unit 508 receives retained scan jobs from external devices such as client terminals 130 via the network control unit 507. The retained scan control unit 508 also obtains access tokens from the client terminal 130 that are necessary for transmission processing using scan jobs. The retained scan control unit 508 also issues scan IDs corresponding to the retained scan jobs obtained from the client terminal 130 and controls the process of associating the received retained scan jobs with the scan IDs and saving them in the storage device 106. The scan ID is identification information for uniquely identifying retained scan jobs. The retained scan control unit 508 also controls the process of instructing the operation control unit 501 to display retained scan jobs on the operation unit 102. The retained scan control unit 508 also controls the process of confirming whether the scanned images can be sent to the specified destination (pre-transmission confirmation). During the pre-transmission check, the storage scan control unit 508 verifies whether transmission is possible based on at least one of the following: the network settings applied to the MFP100, the network policy settings applied to the MFP100, or the connection to the destination. Furthermore, the storage scan control unit 508 notifies the client terminal 130 of the results of the pre-transmission check. The storage scan control unit 508 also accepts the selection of a scan job by the user operating the MFP100 and executes the scan process based on the storage scan job. Finally, it controls the process of sending the file containing the image generated by the scan process to the storage server 120, which is the specified destination.
[0035] The outline of the stationary scan operation in the first embodiment will be explained using Figures 6 to 18. In the first embodiment, when the MFP 100 receives a stationary scan job from the client terminal 130, it performs a process to check whether the scanned image can be sent to the specified destination. By checking whether transmission is possible when the MFP 100 receives a stationary scan job, it is possible to inform the user whether it is possible to send the image to the currently set destination before the MFP 100 executes the stationary scan based on the stationary scan job.
[0036] Figures 6 and 7 are sequence diagrams illustrating the sequence of steps in the storage scan process in the first embodiment. Figures 6 and 7 show the case where transmission is determined to be possible in the confirmation of whether or not the scanned image can be transmitted. In this embodiment, each process performed by the MFP100 shown in Figures 6 and 7 is realized by the CPU201 reading the program stored in the FlashROM210 into the DRAM202 and executing it. Each process performed by the authorization server110 and storage server120 shown in Figures 6 and 7 is realized by the CPU301 reading the program stored in the HDD306 into the DRAM302 and executing it. Each process performed by the client terminal130 shown in Figures 6 and 7 is realized by the CPU401 reading the program stored in the FlashROM406 into the DRAM402 and executing it.
[0037] This process begins when the user selects the retained scan application 131 on the client terminal 130 to start setting up a retained scan. In S601, the CPU 401 of the client terminal 130 launches the retained scan application 131 in response to the user's operation. In S602, the retained scan application 131 on the client terminal 130 displays the retained scan settings screen and accepts the user's request for retained scan settings to be sent to the MFP 100.
[0038] Figure 8 shows an example of the fixed scan settings screen in the first embodiment. The fixed scan settings screen 800 is displayed on the screen of the client terminal 130 by the fixed scan application 131. The fixed scan settings screen 800 displays, for example, scan settings 801, destination 802, name 803, path selection button 804, OK button 805, etc. Scan settings 801 is an item for setting the scan. In scan settings 801, for example, you can set the size of the document to be scanned, such as A3 or A4, the color setting, such as full color or grayscale, and the file type of the image file to be saved, such as JPEG or PDF. Destination 802 is an item for specifying the location where the image data generated by the scan will be saved. In destination 802, for example, you can set the server and path to save the data.
[0039] Name 803 is an item for setting the name of the retained scan job. Path selection button 804 is a button for selecting the path to which the scanned image will be sent (saved). When path selection button 804 is pressed, the retained scan application 131 obtains an access token and displays the server's directory list screen. The user selects the save destination path from the directory list screen, and the retained scan application 131 accepts the user's selection and sets the save destination. If the storage server 120 is set as the save destination, the user selects the save destination path from the directory list screen of the storage server 120. In this embodiment, it is assumed that the storage server 120 is pre-specified as the server for destination 802 and the image processing device 100 is pre-specified as the destination for the retained scan job in the client terminal 130, but this is not limited to this. It is also possible to allow the user to select the storage server 120 or MFP 100 in the retained scan settings screen 800 without pre-specifying them in the client terminal 130. The OK button 805 is used to complete the retained scan settings and send a retained scan job based on those settings to the MFP 100. When the user presses the OK button 805, the retained scan application 131 generates a retained scan job with the retained scan settings at that time and requests a retained scan from the MFP 100. Note that the settings in Figure 8 are just an example, and other settings or even only some settings may be possible as long as this embodiment is feasible.
[0040] Returning to the explanation of Figure 6, in S603, when the client terminal 130's storage scan application 131 detects that the OK button 805 on the storage scan settings screen 800 has been pressed, it requests a storage scan from the MFP 100. In the storage scan request, the client terminal 130 sends to the MFP 100 an access token that allows the user to use the storage 122, which will be the storage destination for the storage scan job generated based on the settings in S602, with the user's authority. The access token is a token obtained from the authentication service provided by the authorization server 110.
[0041] In S604, the MFP100's storage scan control unit 508 refers to the storage scan settings included in the storage scan job received from the client terminal 130 and performs a check (pre-transmission check) to determine whether the specified scan image can be sent to the destination. The pre-transmission check checks, for example, whether the MFP100 can access the destination storage server 120, and whether the network policy applied to the MFP100 allows access to the destination storage server 120. However, the check is not limited to these, and other check methods may be used.
[0042] The following steps from S605 onwards describe the case where transmission was deemed possible in the pre-transmission check in S604. The case of failure will be described later using the sequence diagram shown in Figure 13. In S605, the MFP100's storage scan control unit 508 issues a scan ID corresponding to the storage scan job obtained from the client terminal 130 in response to the request in S603. In S606, the MFP100's storage scan control unit 508 saves the storage scan job settings in response to the request received from the client terminal 130. The storage scan control unit 508 saves the storage scan job settings based on the scan ticket and access token obtained from the client terminal 130 in response to the request in S603 and the scan ID issued in S605.
[0043] Figure 9 shows an example of a retained scan job setting. The retained scan job setting stores, for example, scan setting 901, destination 902, name 903, access token 904, and scan ID 905. Scan setting 901, destination 902, and name 903 are the contents set on the retained scan setting screen 800 in S602. Scan setting 901 corresponds to scan setting 801. Destination 902 corresponds to destination 802. Name 903 corresponds to name 803. Access token 904 is an access token used to save the scanned image to the destination, and is the access token that the retained scan application 131 obtained from the authorization server 110 and sent to the MFP 100 along with the retained scan job in S603. Scan ID 905 is the scan ID issued in S605.
[0044] Returning to the explanation of Figure 6, in S607, the MFP100's storage scan control unit 508 sends a response to the client terminal 130 for the storage scan request in S603. If the pre-transmission check in S604 determines that transmission is possible, that is, if the storage scan request is successful, the response will include a scan ID corresponding to the storage scan request issued in S605. In S608, the client terminal 130's storage scan application 131 displays the result of the storage scan request made to the MFP100 in S603 on the client terminal 130's display, based on the response obtained from the MFP100 in S607.
[0045] Figure 10 shows an example of a results screen when a request for a stationary scan is successful. The results screen 1000, when a request for a stationary scan is successful, displays a message 1001 indicating success, along with the scan ID 1002 issued by the MFP 100. The results screen 1000, when a request for a stationary scan is successful, may also display a button to cancel the requested stationary scan job or a button to change the settings of the stationary scan job.
[0046] Returning to the explanation of Figure 6, at S609, the implanted scan control unit 508 of the MFP100 launches the implanted scan application in response to instructions from the user operating the MFP100. At S610, the implanted scan control unit 508 of the MFP100 displays the implanted scan job selection screen on the operation unit 102 and accepts the user's selection of an implanted scan job. Figure 11 shows an example of the implanted scan selection screen. The implanted scan selection screen 1100 includes, A list of stored scan jobs 1101 stored in the MFP100 is displayed. The list of stored scan jobs 1101 displays, for example, the scan ID and selection button 1102 of the stored scan jobs. The user instructs the MFP100 to execute a stored scan job by selecting the selection button 1102 corresponding to the stored scan job they want to execute. Although an example has been described in which the scan ID is displayed in the list of stored scan jobs 1101, this is not the only example; for example, the name of the stored scan job may be displayed. In addition, other information such as scan settings and the date and time the stored scan job was specified may be displayed in the list of stored scan jobs 1101. Furthermore, although an example has been described in which user authentication is not performed in the MFP100 and all stored scan jobs stored in the MFP100 are displayed in the list of stored scan jobs 1101, this is not the only example. For example, user authentication may be performed when logging into the MFP100, and only stored scan jobs corresponding to the authenticated user may be displayed in the list of stored scan jobs 1101.
[0047] In S611, the storage scan control unit 508 of the MFP100 displays a storage scan execution screen on the operation unit 102 corresponding to the storage scan job selected in S610. Figure 12 shows an example of the storage scan execution screen. The storage scan execution screen 1200 displays, for example, scan ID 1201, scan settings 1202, destination 1203, name 1204, scan execution button 1205, back button 1206, etc. Scan ID 1201, scan settings 1202, destination 1203, and name 1204 are displayed based on the storage scan job settings saved in the MFP100 in S606. Scan ID 1201 is the scan ID of the storage scan job selected in S610. Scan settings 1202 are the scan settings set for the storage scan job selected in S610. The storage scan execution screen 1200 may also display a setting change button for changing the scan settings. When the user selects the setting change button, the stationary scan control unit 508 displays a scan setting change screen (not shown) on the operation unit 102. On the scan setting change screen, the user can change the scan settings to different settings from those set for the stationary scan job on the client terminal 130. If the scan settings are changed on the scan setting change screen, the stationary scan control unit 508 displays the changed scan settings in scan settings 1202. The destination 1203 is the storage location for the scanned image data set for the stationary scan job selected in S610. In this embodiment, the storage location on the storage server 120 is displayed as destination 1203. The name 1204 is the name of the stationary scan job selected in S610. When the scan execution button 1205 is selected, the stationary scan control unit 508 performs the process in S612. When the back button 1206 is selected, the stationary scan control unit 508 returns the screen displayed on the operation unit 102 to the stationary scan selection screen 1100. Additionally, the storage scan execution screen 1200 may display a button to cancel the currently displayed storage scan job.
[0048] When the scan execution button 1205 is selected, the MFP100 performs a scan process based on the scan settings 1202 in S612 and S613, and performs a save process to save the image data generated by the scan to the specified save location. First, in S612, the MFP100's stationary scan control unit 508 performs a scan process with the specified scan settings to generate an image file (image data). Then, in S613, the MFP100's stationary scan control unit 508 sends a file containing the image generated by the scan process to the storage server 120. The file sent to the storage server 120 includes, for example, the image file generated by the scan, the access token corresponding to the stationary scan job selected in S610, the destination and name of the storage server 120.
[0049] In S614, the storage application 121 of the storage server 120 checks with the authorization server 110 to confirm whether the access token received from the MFP 100 is valid. The storage application 121 sends the access token obtained from the MFP 100 to the authorization server 110 to confirm its validity. In S615, the authorization application 111 of the authorization server 110 checks whether the access token sent from the storage server 120 is valid. In this embodiment, the case in which the access token is valid is described. In S616, the authorization application 111 of the authorization server 110 notifies the storage server 120 of the result of the access token verification. In this embodiment, the authorization application 111 of the authorization server 110 notifies the storage server 120 that the access token is valid. If the access token is not valid, for example, the storage server 120 notifies the MFP 100 of an error, and the MFP 100 displays an error screen.
[0050] In S617, the storage application 121 of the storage server 120 checks the verification result of the access token received from the authorization server 110. If the access token is valid, it proceeds to the process in S618. In S618, the storage application 121 of the storage server 120 saves the image file to the storage location specified by the MFP 100, i.e., the transmission destination specified in S613. In S619, the storage application 121 of the storage server 120 notifies the MFP 100 of the result of sending the image file. This embodiment describes the case in which the image file transmission was successful. In S620, the storage scan control unit 508 of the MFP 100 displays the transmission result returned from the storage server 120 on the operation unit 102. If the saving of the image file to the specified storage location was successful, it displays a message indicating that the saving was successful. On the other hand, if the saving of the image file to the specified storage location failed, it displays an error message, for example, and terminates this sequence.
[0051] Figures 6 and 7 illustrate the case where transmission is possible during the confirmation of whether the scanned image can be transmitted in S604 (pre-transmission confirmation). Here, we will explain the case where transmission is not possible during the pre-transmission confirmation in S604. Figure 13 is a sequence diagram of the case where transmission is not possible during the pre-transmission confirmation. In this embodiment, each process performed by the MFP100 shown in Figure 13 is realized by the CPU201 reading the program stored in FlashROM210 into DRAM202 and executing it. Each process performed by the client terminal 130 shown in Figure 13 is realized by the CPU401 reading the program stored in FlashROM406 into DRAM402 and executing it.
[0052] In the process shown in Figure 13, the same reference numerals are used for processes similar to those in Figure 6, and their explanations are omitted. In S604, the MFP100's storage scan control unit 508 refers to the storage scan settings included in the storage scan job received from the client terminal 130 in S603 and checks whether the scanned image can be sent to the specified destination (pre-transmission check). If it is determined that it can be sent, it performs the process shown in S605 in Figure 6. On the other hand, if it is determined that it cannot be sent, it performs the process shown in S1301.
[0053] The following steps from S1301 onwards describe a case where the pre-transmission check in S604 determined that transmission was not possible (failed). In S1301, the storage scan control unit 508 of the MFP100 sends a response to the client terminal 130 regarding the storage scan request in S603. The response when the pre-transmission check fails may include the result of the pre-transmission check as well as the reason for the failure.
[0054] In S1302, the storage scan application 131 on the client terminal 130 displays the result of the storage scan request it made to the MFP 100 in S603, based on the response notified from the MFP 100 in S1301, on the display of the client terminal 130. Figure 14 shows an example of the result screen when the storage scan request fails. The result screen 1400 when the storage scan request fails displays, for example, a message 1401 indicating the failure, along with a reason for the failure 1402. The result screen 1400 when the storage scan request fails may also display a screen where the error can be handled or the destination settings can be changed.
[0055] Figures 6 and 13 illustrate an example in which, if transmission is possible during the pre-transmission check, a scan ID is issued in S605 and S606 to save the retained scan settings to the MFP100, and if transmission is not possible, a scan ID is not issued. However, the system is not limited to this example. In another embodiment, even if transmission is determined to be impossible during the pre-transmission check, a scan ID may be issued to save the retained scan settings to the MFP100, allowing the retained scan to be executed. By issuing a scan ID and retaining the scan job in the MFP100 even when transmission is determined to be impossible during the pre-transmission check, the user can execute the retained scan job without having to reconfigure the scan settings after addressing the cause of the transmission failure. Furthermore, when transmission is determined to be impossible during the pre-transmission check, the system may be configured to switch whether to issue a scan ID depending on the cause of the transmission failure. That is, if the cause of the transmission failure is a specific cause specified in advance, the scan ID is not issued and the job is not saved, and if the cause of the transmission failure is not a specific cause specified in advance, the scan ID is issued and the retained scan job is saved to the storage device 106. For example, if the transmission is deemed impossible due to a network policy, a scan ID will not be issued; however, if the transmission is deemed impossible due to a temporary downtime of the destination storage server, a scan ID will be issued.
[0056] Figures 15 and 16 are flowcharts illustrating the process of a stationary scan in the client terminal 130 according to the first embodiment. Each process shown in Figures 15 and 16 is executed by the stationary scan application 131 of the client terminal 130. Each process executed by the client terminal 130 shown in Figures 15 and 16 is realized by the CPU 401 reading a program stored in the Flash ROM 406 into the DRAM 402 and executing it.
[0057] This process begins when the user on the client terminal 130 selects the retained scan application 131 to start setting up retained scans, and the retained scan application 131 is launched. In S1501, the CPU 401 of the client terminal 130 displays the retained scan settings screen 800 (Figure 8). The process in S1501 corresponds to the process in S602 in Figures 6 and 13. In S1502, the retained scan application 131 of the client terminal 130 accepts (detects) user operations on the retained scan settings screen 800. Accepted operations include changing the settings for scan settings 801, destination 802, and name 803, as well as starting transmission by pressing the OK button 805.
[0058] In S1503, the stationary scan application 131 on the client terminal 130 determines whether the operation received from the user in S1502 is related to the scan setting 801. If it is a scan setting, it proceeds to S1504. In S1504, the stationary scan application 131 on the client terminal 130 updates the scan setting according to the user's operation. After that, it returns to the process in S1502. On the other hand, if it is not a scan setting, it proceeds to S1505.
[0059] In S1505, the client terminal 130's stationary scan application 131 determines whether the operation received from the user in S1502 relates to the settings of the destination 802. If it is a destination setting operation, it proceeds to S1506. In S1506, the client terminal 130's stationary scan application 131 updates the destination settings according to the user's operation. After that, it returns to the process in S1502. On the other hand, if it is not a destination setting operation, it proceeds to S1507.
[0060] In S1507, the stationary scan application 131 on the client terminal 130 determines whether the operation received from the user in S1502 is an operation related to setting the name 803. If it is a name setting operation, it proceeds to S1508. In S1508, the stationary scan application 131 on the client terminal 130 updates the name setting according to the user's operation. After that, it returns to the process in S1502. On the other hand, if it is not a name setting operation, it proceeds to S1509.
[0061] In S1509, the stationary scan application 131 on the client terminal 130 determines whether the operation received from the user is a transmission start. If it is a transmission start, that is, if the OK button 805 on the stationary scan settings screen 800 is pressed, the process in S1510 is performed. If it is not a transmission start, for example if the cancel button on the stationary scan settings screen 800 is pressed, this process is terminated.
[0062] In S1510, the client terminal 130's storage scan application 131 sends a storage scan request to the MFP 100. The processing in S1510 corresponds to the processing in S603 in Figures 6 and 13. Based on the storage scan request received from the client terminal 130, the MFP 100 checks whether the scanned image can be sent to the specified destination (pre-transmission check) and notifies the client terminal 130 of the check result as a response to the storage scan request. The client terminal 130's storage scan application 131 receives the response to the storage scan request from the MFP 100. In S1511, the client terminal 130's storage scan application 131 displays a screen showing the result of the storage scan request based on the response from the MFP 100. For example, if the storage scan request is successful, that is, if the MFP 100 determines that it can be sent during the pre-transmission check, the storage scan application 131 displays the result screen shown in Figure 10. On the other hand, if the request for a storage scan fails, that is, if the MFP100 determines that transmission is not possible during the pre-transmission check, the storage scan application 131 displays the results screen shown in Figure 14. Once the results screen is displayed, the storage scan application 131 on the client terminal 130 terminates this process.
[0063] Figure 17 is a flowchart showing the processing performed by the MFP100 upon receiving a storage scan request. Each process performed by the MFP100 shown in Figure 17 is realized by the CPU201 reading a program stored in the FlashROM210 into the DRAM202 and executing it.
[0064] In S1701, the MFP100's storage scan control unit 508 receives a storage scan request from the client terminal 130. In S1702, the MFP100's storage scan control unit 508 refers to the settings included in the storage scan request and checks whether it is possible to send the specified scan image to the destination (pre-transmission check). Examples of pre-transmission checks include checking whether the MFP100 can access the destination storage server, and checking whether the network policy applied to the MFP100 allows access to the destination storage server. These are merely examples, and other verification methods may be used. The process in S1702 corresponds to the process in S604 in Figures 6 and 13.
[0065] In S1703, the MFP100's storage scan control unit 508 determines whether the result of the pre-transmission check in S1702 is valid for transmission. If it determines that transmission is possible, it proceeds to the process in S1704. On the other hand, if it determines that transmission is not possible, it proceeds to the process in S1706. In S1704, the MFP100's storage scan control unit 508 issues a scan ID corresponding to the storage scan request received in S1701. The process in S1704 corresponds to the process in S605 in Figure 6. In S1705, the MFP100's storage scan control unit 508 saves the storage scan job settings corresponding to the storage scan request received from the client terminal 130 in S1701. Based on the storage scan job and access token obtained from the client terminal 130 in S1701 and the scan ID issued in S1704, the storage scan control unit 508 saves the storage scan job settings to the storage device 106. The process in S1705 corresponds to the process in S606 in Figure 6. In S1706, the MFP100's storage scan control unit 508 notifies the client terminal 130 that the storage scan request received in S1701 was successful. The notification includes the scan ID issued in S1704. The process in S1706 corresponds to the process in S607 in Figure 6. Thus, based on the confirmation that the data can be sent to the destination during the pre-transmission check, the MFP100's storage scan control unit 508 issues a scan ID corresponding to the storage scan job and notifies the client terminal 130 of the scan ID.
[0066] In S1707, the MFP100's storage scan control unit 508 notifies the client terminal 130 that the storage scan request received in S1701 has failed. At this time, the notification may also include the reason why the pre-transmission check failed. The reason for the pre-transmission check failure may be, for example, that the network policy applied to the MFP100 is denying access to the destination storage server. The process in S1707 corresponds to the process in S1301 in Figure 13. Once the MFP100's storage scan control unit 508 has finished notifying the client terminal 130 of the success or failure of the storage scan request based on whether the scanned image can be sent to the destination specified in S1706 or S1707, it terminates this process. In this way, the MFP100's storage scan control unit 508 notifies the client terminal 130 of the confirmation result when it is confirmed in the pre-transmission check that the image cannot be sent to the destination. As explained above, based on the pre-transmission confirmation results, the MFP100 sends a scan ID corresponding to the stored scan job to the client terminal 130 if it is confirmed that the data can be sent to the destination, and the confirmation result is sent to the client terminal 130 if it is confirmed that the data cannot be sent to the destination.
[0067] Figure 18 is a flowchart showing the process of a stationary scan in the MFP100. Each process performed in the MFP100 shown in Figure 18 is realized by the CPU201 reading a program stored in the FlashROM210 into the DRAM202 and executing it.
[0068] This process begins when the user activates the implanted scan application 105 on the MFP100 (S609). In S1801, the implanted scan control unit 508 of the MFP100 displays a list of implanted scan jobs (Figure 11) on the operation unit 102 and accepts the user's selection of an implanted scan job to be executed. The process in S1801 corresponds to the process in S601 in Figure 7. In S1802, the implanted scan control unit 508 of the MFP100 displays the execution screen (Figure 12) of the implanted scan job selected in S1801 on the operation unit 102. Note that the implanted scan execution screen 1200 shown in Figure 12 is merely an example; for example, a button to change the settings of the implanted scan job could be provided. The process in S1802 corresponds to the process in S611 in Figure 7.
[0069] In S1803, the MFP100's storage scan control unit 508 determines whether it has detected a user pressing the scan execution button 1205 on the storage scan execution screen 1200. If the scan execution button 1205 is pressed, it proceeds to the process in S1804. On the other hand, if the scan execution button 1205 is not pressed and the back button 1206 is pressed instead, it returns to the process in S1801. In S1804, the MFP100's storage scan control unit 508 executes a scan based on the storage scan job using the settings displayed in S1802. The process in S1804 corresponds to the process in S612 in Figure 7. In S1805, the MFP100's storage scan control unit 508 sends the image file generated by the scan to the destination specified in the storage scan job. In this embodiment, the image file is sent to the storage server 120. The process in S1805 corresponds to the process in S613 in Figure 7. In S1806, the MFP100's embedded scan control unit 508 displays the image file transmission result. The process in S1806 corresponds to the process in S602 in Figure 7. Once the display of the transmission result is complete, the MFP100 terminates this process.
[0070] In this embodiment, an example of performing a pre-transmission check at the time a request for a retained scan is received from the client terminal 130 has been described, but it is not limited to this. For example, after saving a retained scan job in the MFP 100, it is also possible to configure the system to perform a pre-transmission check for one or more destinations (senders) before executing the retained scan job. For example, the client terminal 130 or the like may instruct the MFP 100 to perform a pre-transmission check again, specifying a retained scan job that could not be sent in the previous pre-transmission check, and the MFP 100 will perform the pre-transmission check. A retained scan job can be specified, for example, by specifying a scan ID. It is also possible for the MFP 100 to check all destinations included in the retained scan jobs stored in the storage device 106 to be able to send data. The timing of this pre-transmission check may be when an instruction is received from a screen displayed on the MFP 100 as shown in Figures 11 and 12, or when an instruction is received from an external terminal such as the client terminal 130 connected to the network. Furthermore, the MFP 100 may be configured to perform pre-transmission checks automatically at regular intervals. Furthermore, instead of performing a pre-transmission check for all recipients, it is also possible to perform a check only for recipients that were identified as ineligible in the previous pre-transmission check. Additionally, while this embodiment assumes the use of OAuth, other authentication methods can also be used.
[0071] As described above, according to this embodiment, it is possible to verify whether the transmission of a fixed scan job will be successful before executing the job on the image processing device. This prevents unnecessary work from being performed by the user due to transmission errors during the execution of the fixed scan job.
[0072] (Second Embodiment) In the first embodiment, the success of transmitting the image generated by the embedded scan was verified at the time after the client terminal made an embedded scan request to the MFP and before the MFP performed the embedded scan. In the second embodiment, the success of transmitting the image generated by the embedded scan was verified before the client terminal made an embedded scan request to the MFP. The system configuration of this embodiment is the same as in the first embodiment. In this embodiment, the same reference numerals are used for the same configurations and processes as in the first embodiment, and their descriptions are omitted.
[0073] The general outline of the stationary scan operation in the second embodiment will be explained using Figures 19 to 25. In the second embodiment, before receiving a stationary scan job from the client terminal 130, the MFP 100 performs a process to check whether the scanned image can be sent to the specified destination.
[0074] Figures 19 and 20 are sequence diagrams illustrating the sequence of operations for the storage scan process in the second embodiment. In this embodiment, each process performed by the MFP 100 shown in Figures 19 and 20 is realized by the CPU 201 reading a program stored in the Flash ROM 210 into the DRAM 202 and executing it. Each process performed by the authorization server 110 and storage server 120 shown in Figures 19 and 20 is realized by the CPU 301 reading a program stored in the HDD 306 into the DRAM 302 and executing it. Each process performed by the client terminal 130 shown in Figures 19 and 20 is realized by the CPU 401 reading a program stored in the Flash ROM 406 into the DRAM 402 and executing it.
[0075] The stationary scan application 131 on the client terminal 130, launched in S1901, displays a screen for configuring stationary scans in S1902 and accepts the stationary scan settings to be requested from the MFP 100. S1901 and S1902 are the same processes as S601 and S602. In the second embodiment, the stationary scan settings screen displayed includes a button to confirm (pre-transmission confirmation) whether the MFP 100 can send images to the specified destination for scanned images.
[0076] Figure 21 shows an example of the fixed scan settings screen in the second embodiment. The fixed scan settings screen 2100 displays, for example, the scan settings 801, destination 802, name 803, path selection button 804, OK button 805, etc., which were also displayed in the fixed scan settings screen 800 of the first embodiment, as well as a pre-transmission confirmation button 2101. The fixed scan settings screen 2100 is displayed on the screen of the client terminal 130 by the fixed scan application 131. The pre-transmission confirmation button 2101 is a button that instructs the MFP 100 to confirm before transmission. When the pre-transmission confirmation button 2101 is pressed, the fixed scan application 131 on the client terminal 130 requests the MFP 100 to confirm whether it is possible to send the scanned image to the destination set in destination 802. In addition to confirming whether it is possible to send to the destination, the MFP 100 may also be requested to confirm whether scanning is possible with the current scan settings 801.
[0077] When the client terminal 130 detects that the pre-transmission confirmation button 2101 has been pressed, in S1903, the client terminal 130's storage scan application 131 requests pre-transmission confirmation from the MFP 100. When requesting pre-transmission confirmation, the client terminal 130's storage scan application 131 sends the MFP 100 the current scan settings, including the destination. Upon receiving the pre-transmission confirmation request from the client terminal 130, in S1904, the MFP 100's storage scan control unit 508 performs pre-transmission confirmation based on the storage scan settings obtained from the client terminal 130. In pre-transmission confirmation, the storage scan control unit 508 refers to the storage scan settings received from the client terminal 130 and verifies whether the specified scan image can be sent to the destination. For example, pre-transmission confirmation checks whether the MFP 100 can access the destination storage server 120, and whether the network policy applied to the MFP 100 allows access to the destination storage server 120. Please note that the verification methods are not limited to those listed above, and other verification methods are also acceptable.
[0078] In S1905, the MFP100's stationary scan control unit 508 responds to the client terminal 130 with the result of the pre-transmission check. For example, if it is confirmed that it is possible to send the scanned image to the specified destination, it sends a response to the client terminal 130 indicating that the pre-transmission check was successful. On the other hand, if it is confirmed that it is not possible to send the scanned image to the specified destination, it sends a response to the client terminal 130 indicating that the pre-transmission check failed.
[0079] In S1906, the storage scan application 131 on the client terminal 130 displays the result of the pre-transmission confirmation received in S1905. Figure 22 shows an example of the pre-transmission confirmation result screen in the second embodiment. Figure 22(A) is an example of the result screen 2200 when the pre-transmission confirmation was successful. The result screen 2200 is superimposed on, for example, the storage scan settings screen 2100. The result screen 2200 displays, for example, a message 2201 indicating that the pre-transmission confirmation was successful. The result screen 2200 may also display the response code when accessing the destination storage server. Figure 22(B) is an example of the result screen 2210 when the pre-transmission confirmation was unsuccessful. The result screen 2210 is superimposed on, for example, the storage scan settings screen 2100. The result screen 2210 displays, for example, a message 2211 indicating that the pre-transmission confirmation failed and a reason 2212 for the inability to send. Furthermore, the results screen 2210 may display how to deal with errors that cause transmission failure, or a screen that allows the user to change the destination settings. After checking the connection results, the user can change the settings of the stored scan job or the MFP100 settings as needed. For example, it is possible to change the destination settings and perform a pre-transmission check again.
[0080] The following process is executed if the pre-transmission verification is successful. In S1907, when the client terminal 130's storage scan application 131 detects that the OK button 805 on the storage scan settings screen 2100 has been pressed, it requests a storage scan from the MFP 100. In the storage scan request, the client terminal 130 sends the MFP 100 an access token that allows the user to use the storage 122, which will be the storage destination for the storage scan job generated based on the settings in S602, with the user's authority. The access token is a token obtained from the authentication service provided by the authorization server 110.
[0081] S1908 and S1909 are the same processes as S605 and S606 in the first embodiment. In S1910, the storage scan control unit 508 of the MFP100 responds to the storage scan request of S1907 with the client terminal 130. The response includes a scan ID corresponding to the storage scan request issued in S1908. In S1911, the storage scan application 131 of the client terminal 130 displays the result of the storage scan request that it requested from the MFP100 in S603, based on the response obtained from the MFP100 in S607, on the display of the client terminal 130. The storage scan application 131 displays, for example, a result screen 1000 including the scan ID 1002 issued by the MFP100 as shown in Figure 10. The process from S1912 to S1923, in which the user selects and executes a stored scan job stored in the MFP100, is the same as the process from S609 to S620 in the first embodiment. In this embodiment, the OAuth mechanism is assumed, but other authentication methods may also be used.
[0082] Figures 23 and 24 are flowcharts showing the process of a retained scan in the retained scan application 131 of the client terminal 130. Each process performed by the client terminal 130 shown in Figures 23 and 24 is realized by the CPU 401 reading a program stored in the Flash ROM 406 into the DRAM 402 and executing it.
[0083] This process begins when the user on the client terminal 130 selects the retained scan application 131 to start setting up retained scans, and the retained scan application 131 is launched. In S2301, the retained scan application 131 on the client terminal 130 displays the retained scan settings screen 2100 (Figure 21). The process in S2101 corresponds to the process in S1901 in Figure 19. In S2302, the retained scan application 131 on the client terminal 130 accepts (detects) user operations on the retained scan settings screen 800. Accepted operations include changing the settings for scan settings 801, destination 802, and name 803, starting the transmission of a retained scan job by pressing the OK button 805, and requesting a pre-transmission confirmation by pressing the pre-transmission confirmation button 2101. The processes from S2303 to S2308 are the same as the processes from S1503 to S1508 in the first embodiment.
[0084] If the operation received in S2302 is not a scan setting, destination setting, or name setting, then in S2309, the retained scan application 131 on the client terminal 130 determines whether the operation received in S2302 is a pre-transmission confirmation. If the received operation is a pre-transmission confirmation, the process in S2310 is performed. On the other hand, if the received operation is not a pre-transmission confirmation, the process in S2312 is performed. In S2310, the retained scan application 131 on the client terminal 130 requests a pre-transmission confirmation from the MFP 100 with the retained scan settings currently specified on the retained scan setting screen 2100, and receives the result of the pre-transmission confirmation from the MFP 100. In S2311, the retained scan application 131 on the client terminal 130 displays the result of the pre-transmission confirmation on the screen based on the response of the pre-transmission confirmation result from the MFP 100. For example, if the pre-transmission confirmation is successful, the result screen shown in Figure 22(A) is displayed, and if it fails, the result screen shown in Figure 22(B) is displayed. Once the display of the pre-transmission confirmation results is complete, the process returns to S2302.
[0085] In S2312, the storage scan application 131 on the client terminal 130 determines whether the operation received in S2302 is a transmission start. If it is a transmission start, it performs the process in S2313. On the other hand, if it is not a transmission start, this process ends. In S2313, the storage scan application 131 on the client terminal 130 requests a storage scan from the MFP 100 and receives a response to the request. In S2314, the storage scan application 131 on the client terminal 130 displays a screen showing the result of the storage scan request based on the response from the MFP 100. For example, if the storage scan request is successful, the screen shown in Figure 10 is displayed. Once the display of the storage scan request result is complete, the process ends.
[0086] Figure 25 is a flowchart showing the processing performed by the MFP 100 upon receiving a request from the client terminal 130. The requests that the MFP 100 receives from the client terminal 130 are either pre-transmission confirmation requests or hold scan requests. Each process performed by the MFP 100 shown in Figure 25 is realized by the CPU 201 loading a program stored in the Flash ROM 210 into the DRAM 202 and executing it.
[0087] In S2501, the MFP100's storage scan control unit 508 receives a request from the client terminal 130. In S2502, the MFP100's storage scan control unit 508 determines whether the request received from the client terminal 130 in S2501 is a pre-transmission confirmation request. If the received request is a pre-transmission confirmation request, it performs the process in S2503. On the other hand, if the received request is not a pre-transmission confirmation request, i.e., if it is a storage scan request, it performs the process in S2507.
[0088] In S2503, the storage scan control unit 508 of the MFP100 performs a pre-transmission check (pre-transmission check) to determine whether the specified scan image can be sent to the destination based on the storage scan settings included in the pre-transmission check request. Examples of pre-transmission checks include checking whether the MFP100 can access the destination storage server, and checking whether the network policy applied to the MFP100 allows access to the destination storage server. These are merely examples, and other check methods may be used.
[0089] In S2504, the storage scan control unit 508 of the MFP100 determines whether the pre-transmission check in S2503 was successful. If the pre-transmission check is successful, that is, if it is determined that transmission is possible, it proceeds to S2505. On the other hand, if the pre-transmission check fails, that is, if it is determined that transmission is not possible, it proceeds to S2506. In S2505, the storage scan control unit 508 of the MFP100 notifies the client terminal 130 that the pre-transmission check was successful. In S2506, the storage scan control unit 508 of the MFP100 notifies the client terminal 130 that the pre-transmission check failed.
[0090] In S2507, the MFP100's storage scan control unit 508 issues a scan ID corresponding to the storage scan request received in S2501. The MFP100 may perform a pre-transmission check based on the settings included in the storage scan request before issuing the scan ID, and may switch whether or not to issue the scan ID depending on the check result. If the pre-transmission check determines that transmission is not possible and the scan ID is not issued, the MFP100 notifies the client terminal 130 that the storage scan request received in S2501 has failed.
[0091] In S2508, the MFP100's storage scan control unit 508 stores the storage scan job settings in response to the storage scan request received from the client terminal 130. Based on the storage scan job and access token obtained from the client terminal 130 in S2501 and the scan ID issued in S2507, the storage scan control unit 508 stores the storage scan job settings in the storage device 106. In S2509, the MFP100's storage scan control unit 508 notifies the client terminal 130 of the result of the storage scan request received in S2501. If the notification indicates that the storage scan request was successful, the notification content will include the scan ID issued in S2507. If the notification indicates that the storage scan request failed, the notification content may include the reason why the pre-transmission confirmation failed.
[0092] As described above, according to the second embodiment, before the client terminal sends the fixed scan job to the image processing device, it is possible to check whether the transmission of the scanned image to the image processing device will be successful while the client terminal is setting up the fixed scan job. In this embodiment, pre-transmission confirmation is possible while the settings screen is open, and if transmission is not possible, the destination can be changed immediately on the settings screen. This makes it possible to suppress unnecessary work for the user due to transmission errors when executing a fixed scan job.
[0093] The disclosure of this embodiment includes the following configuration of an image processing apparatus. (Composition 1) Image processing apparatus comprising a storage device and a scanner, wherein the apparatus includes: confirmation means for confirming whether a file containing an image generated by a scanning process performed by the scanner can be sent to a destination specified by a client terminal; notification means for notifying the client terminal of the confirmation result when it is confirmed by the confirmation means that the file cannot be sent to the destination; and storage means for saving a job including the settings for the scanning process and the destination of the file containing the image generated by the scanning process to the storage device, wherein the notification means notifies the client terminal of identification information corresponding to the job based on the confirmation result when it is confirmed that the file can be sent to the destination. (Configuration 2) The image processing apparatus according to Configuration 1, characterized in that when the confirmation means receives a job from the client terminal including the settings for the scan process and the destination, it can confirm whether it is possible to send a file containing the image generated by the scan process executed based on the job to the destination specified in the job. (Composition 3) The image processing apparatus according to configuration 2, characterized in that, if the verification means confirms that the job can be transmitted to the destination, the storage means issues identification information corresponding to the job and stores the job containing the identification information in the storage device. (Composition 4) The image processing apparatus according to configuration 2 or 3, characterized in that, if the verification by the verification means confirms that the job cannot be sent to the destination, and the reason for the inability to send is a specific reason designated in advance, the storage means does not save the job, and the notification means notifies the client terminal of the verification result, and if the verification by the verification means confirms that the job cannot be sent to the destination, and the reason for the inability to send is not the specific reason, the storage means issues identification information corresponding to the job and saves the job including the identification information to the storage device, and the notification means notifies the client terminal of the verification result. (Composition 5) The image processing apparatus according to Configuration 1, characterized in that, when the client terminal receives an instruction to confirm whether the image generated by the scanning process can be sent to a specified destination, the confirmation means confirms whether it can be sent to the destination. (Composition 6) The image processing apparatus according to configuration 5, characterized in that, as a result of the verification by the verification means, it is confirmed that the data can be sent to the destination, the notification means notifies the client terminal of the verification result, the storage means, when it receives a job including the scan processing settings and the destination from the client terminal that has received the notification, issues identification information corresponding to the job and stores the job including the identification information in the storage device, and the notification means notifies the client terminal of the identification information. (Composition 7) The image processing apparatus according to any one of configurations 1 to 6, characterized in that the verification means can verify whether it is possible to send to all destinations included in the job stored in the storage device, destinations that were deemed untransmittable in the previous verification, or specified destinations. (Composition 8) The image processing apparatus according to any one of configurations 1 to 7, characterized in that the client terminal displays the confirmation result based on the notification received from the image processing apparatus. (Composition 9) The image processing apparatus according to any one of configurations 1 to 8, characterized in that the confirmation means confirms whether transmission is possible based on at least one of the network settings applied to the image processing apparatus, the network policy settings applied to the image processing apparatus, or the connection to the destination.
[0094] (Other embodiments) The present invention can also be realized by supplying a program that implements one or more of the functions of the above-described 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 realized by a circuit (e.g., an ASIC) that implements one or more functions.
[0095] Although preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and various modifications and changes are possible within the scope of its gist.
Claims
1. An image processing apparatus comprising a storage device and a scanner, A verification means for confirming whether a file containing an image generated by the scanning process performed by the scanner can be sent to a destination specified on the client terminal, In response to the confirmation by the aforementioned confirmation means that it is confirmed that the transmission to the recipient cannot be completed, a notification means notifies the client terminal of the confirmation result, The system includes storage means for storing a job, which includes the settings for the scan process and the destination for sending the file containing the image generated by the scan process, The image processing apparatus is characterized in that the notification means notifies the client terminal of identification information corresponding to the job based on the confirmation result by the confirmation means that it can be transmitted to the destination.
2. The image processing apparatus according to claim 1, characterized in that when the confirmation means receives a job from the client terminal that includes the settings for the scan process and the destination, it confirms whether it is possible to send a file containing the image generated by the scan process executed based on the job to the destination specified in the job.
3. The image processing apparatus according to claim 2, wherein, as a result of the verification by the verification means, it is confirmed that the job can be transmitted to the destination, the storage means issues identification information corresponding to the job and stores the job including the identification information in the storage device.
4. If the verification by the verification means confirms that the job cannot be sent to the destination, and the reason for the inability to send is a specific reason designated in advance, the saving means does not save the job, and the notification means notifies the client terminal of the verification result. The image processing apparatus according to claim 2, wherein, as a result of the verification by the verification means, it is confirmed that the transmission cannot be sent to the destination, and the cause of the inability to transmit is not the specific cause, the storage means issues identification information corresponding to the job and stores the job containing the identification information in the storage device, and the notification means notifies the client terminal of the verification result.
5. The image processing apparatus according to claim 1, characterized in that, when the client terminal receives an instruction to check whether the image generated by the scanning process can be sent to a specified destination, the confirmation means checks whether it can be sent to the destination.
6. In response to the confirmation by the verification means that it has been confirmed that the transmission to the destination can be made, the notification means notifies the client terminal of the confirmation result. When the storage means receives a job including the scan process settings and the destination from the client terminal that received the notification, it issues identification information corresponding to the job and stores the job including the identification information in the storage device. The image processing apparatus according to claim 5, characterized in that the notification means notifies the client terminal of the identification information.
7. The image processing apparatus according to claim 1, characterized in that the verification means can verify whether it is possible to send to all destinations included in the job stored in the storage device, destinations that were deemed untransmittable in the previous verification, or specified destinations.
8. The image processing apparatus according to claim 1, characterized in that the client terminal displays the confirmation result based on the notification received from the image processing apparatus.
9. The image processing apparatus according to any one of claims 1 to 8, characterized in that the confirmation means confirms whether transmission is possible based on at least one of the network settings applied to the image processing apparatus, the network policy settings applied to the image processing apparatus, and the connection to the destination.
10. A control method for an image processing apparatus comprising a scanner and a storage device capable of saving a job including the settings for a scan process specified on a client terminal and the destination for sending a file containing an image generated by the scan process, The process includes verifying whether the file containing the image generated by the scanning process performed by the scanner can be sent to the destination specified on the client terminal, The system includes a notification step in which, if it is confirmed as a result of the above-mentioned verification that the transmission to the recipient cannot be performed, the results of the said verification are notified to the client terminal, The control method is characterized in that, in the notification step, identification information corresponding to the job is notified based on the confirmation that it can be sent to the destination as a result of the confirmation.
Citation Information
Patent Citations
Network scanner system
JP2004282145A
Image system
JP2005064762A
Information processing device
JP2013186573A
Image processing apparatus and image processing program
JP2017169073A
Scan system, control program, and scanner device
JP2022010841A