Image reading device, control method thereof, and program

Abstract

To provide means for allowing a user to easily perform transmission at the time of push scanning using authentication information.SOLUTION: An image reading apparatus includes: reception means configured to receive, from an information processing apparatus, a scanning request for push scanning for a designated destination; generation means configured to scan an original document and generate image data in accordance with the scanning request; transmission means configured to transmit, to the destination, a request including authentication information for accessing the destination and the image data; storage means configured to store the image data for transmission based on reauthentication if a response indicating that there has been an error in authentication using the authentication information is received; and notification means configured to provide a notification of the error to the information processing apparatus. If the reception means receives the authentication information for the reauthentication in response to the notification of the error from the information processing apparatus, the transmission means transmits, to the destination, a request including authentication information for the reauthentication and the stored image data.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present invention relates to an image reading apparatus, a control method thereof, and a program. [Background technology]

[0002] The process of instructing an image reading device to scan a document and send the scanned image to a specific destination server is called "push scanning." In recent years, push scanning instructions are not limited to instructions from the operation panel on the image reading device, but can also be issued from another terminal (hereinafter referred to as a client terminal) connected to the network.

[0003] When sending to a destination server, authentication information (such as a combination of a user name and password) may be required for security reasons. There are several possible methods for determining the authentication information to use when sending to a server in a push scan from a client terminal. For example, one method is to use authentication information included in the push scan command from the client terminal, or to use authentication information stored internally in the image reading device.

[0004] In Patent Document 1, when a transmission error occurs in an image reading device, a means is provided for saving the scanned image, notifying the user of the error on an operation panel, and retransmitting the image. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2008-109479 Summary of the Invention [Problem to be solved by the invention]

[0006] However, if an authentication error occurs when performing push scanning using authentication information from a client terminal, the user must once again place the document and enter the authentication information from scratch in order to resend the document.

[0007] The present invention has been proposed in view of the above-mentioned problems, and aims to provide an image reading device that allows a user to easily transmit authentication information when performing push scanning using authentication information. [Means for solving the problem]

[0008] In order to achieve the above object, the image reading device of the present invention comprises a receiving means for receiving a scan request for push scanning with a specified destination from an information processing device, a generating means for scanning a document in accordance with the scan request and generating image data, a transmitting means for transmitting a request to the destination including authentication information for accessing the destination and the image data, a storing means for saving the image data for transmission by re-authentication when a response indicating that authentication using the authentication information was an error is received, and a notifying means for notifying the information processing device of the error, wherein when the receiving means receives authentication information for re-authentication in response to the error notification from the information processing device, the transmitting means sends a request to the destination including the authentication information for re-authentication and the saved image data. [Effects of the Invention]

[0009] According to the present invention, it is possible to provide an image reading device that allows a user to easily transmit authentication information when performing push scanning using authentication information. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing a system configuration according to a first embodiment. [Figure 2] FIG. 1 is a diagram showing the hardware configuration of an MFP according to a first embodiment. [Figure 3]FIG. 3 is a view showing a scan setting screen of a scan application of the client terminal according to the first embodiment. [Figure 4] FIG. 4 is a view showing an authentication information reception screen during push scanning of the MFP according to the first embodiment. [Figure 5] FIG. 4 is a view showing an authentication information re-entry screen of the scan application of the client terminal according to the first embodiment. [Figure 6] FIG. 4 is a view showing a transmission completion screen of the scan application of the client terminal according to the first embodiment. [Figure 7] 4 is a diagram showing the sequence of the MFP, client terminal, and destination terminal according to the first embodiment. [Figure 8] FIG. 4 is a diagram showing the flow of a client terminal according to the first embodiment. [Figure 9] FIG. 4 is a diagram showing details of the flow of push scanning in a client terminal according to the first embodiment. [Figure 10] FIG. 4 is a diagram showing communication content of push scan according to the first embodiment. [Figure 11] FIG. 4 is a diagram showing communication content for acquiring a scan status according to the first embodiment. [Figure 12] FIG. 3 is a flowchart showing the flow of push scanning in the MFP according to the first embodiment. [Figure 13] FIG. 4 is a flowchart showing a process flow when a scan status acquisition request is received by the MFP according to the first embodiment. [Figure 14] FIG. 11 is a diagram showing the sequence of an MFP, a client terminal, and a destination terminal according to the second embodiment. [Figure 15] FIG. 11 is a diagram showing details of the flow of push scanning in a client terminal according to the second embodiment. [Figure 16] FIG. 11 is a flowchart showing the flow of push scanning in the MFP according to the second embodiment. [Figure 17] FIG. 11 is a view showing a scan setting screen of a scan application of a client terminal according to the third embodiment. [Figure 18] FIG. 11 is a diagram showing the sequence of an MFP, a client terminal, and a destination terminal according to the third embodiment. [Figure 19]FIG. 11 is a diagram showing details of the flow of push scanning in a client terminal according to the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] The following describes embodiments of the present invention with reference to the drawings. Note that the following embodiments do not limit the scope of the invention as claimed, and not all of the combinations of features described in the embodiments are necessarily essential to the solution of the invention.

[0012] [First embodiment] As a first embodiment of the present invention, a method will be described in which an image reading device re-accepts authentication information from a client terminal when an authentication error occurs during a push scan including authentication information from the client terminal. In this embodiment, HTTP is used for each communication, and it is assumed that the IP address of the MFP 101 is "192.168.1.100".

[0013] FIG. 1 is a diagram showing a system configuration according to a first embodiment. Referring to FIG. 1, an example configuration of an image processing system including an image reading device according to an embodiment of the present invention will be described. In the image processing system according to this embodiment, an MFP 101, a client terminal 102, and a destination terminal 103 are connected via a network 104. The MFP 101 (Multi Function Peripheral) is a full-color image reading device that employs an electrophotographic method and has copy and print functions. Thus, the MFP 101 is a multifunction peripheral that has not only a reading function but also a printing function. The MFP 101 has a function of transmitting an image read by a scanner to a specific destination terminal 103. The client terminal 102 is a terminal of a general information processing device such as a PC or a smartphone. The destination terminal 103 is a server that transmits and receives files via a file transmission protocol such as HTTP (Hyper Text Transfer Protocol) and performs user authentication as needed.

[0014] FIG. 2 is a diagram illustrating the hardware configuration of the MFP 101 according to the first embodiment. An example of the hardware configuration of the MFP 101 will be described with reference to FIG. 2. The MFP 101 includes a CPU 201, a ROM 202, a RAM 203, an operation unit 204, a scanner 205, a printer 206, an image processing circuit 207, a hard disk 208, and a network I / F 209. The CPU 201 is a control circuit that controls the entire system using programs stored in the ROM 202 and memory in the RAM 203. The operation unit 204 is a circuit that executes user operations. The scanner 205 reads images on a document and outputs the read images page by page. The printer 206 prints an image based on the scanned image onto a recording medium. The image processing circuit 207 includes a large-capacity image memory, an image rotation circuit, a resolution scaling circuit, and an encoding / decoding circuit for MH, MR, MMR, JBIG, JPEG, etc. The image processing circuit 207 can also perform various image processing such as shading, trimming, and masking. The hard disk 208 is a large-capacity recording medium connected via an I / F such as SCSI or IDE. The network I / F 209 is a circuit for connecting to the network line 104. The scanner 205, printer 206, and image processing circuit 207 are connected via a high-speed video bus separate from the CPU 201 bus from the CPU 201, and are configured to enable high-speed image transmission. The MFP 101 processes images read by the scanner 205 using the image processing circuit 207.

[0015] 3 is a diagram showing a scan setting screen of the scan application of the client terminal 102 according to the first embodiment. An example of the scan setting screen of the scan application of the client terminal 102 will be described with reference to FIG.

[0016] Buttons 301 to 303 are buttons for setting a transmission destination, and each button displays a current setting value. The "Set Destination" button 301 is a button for setting a destination. By pressing the "Set Destination" button 301, the user can select a desired destination from destinations registered in the client terminal 102. If the destination is not in the list of destinations, a new destination can be input. The folder path of the destination may also be specified. The "Set User Name" button 302 is a button for setting a username as authentication information when authentication is required when transmitting an image to the destination terminal 103. The "Set Password" button 303 is a button for setting a password as authentication information when authentication is required when transmitting an image to the destination terminal 103. Multiple destinations can be set, and authentication information may be set for each destination. Furthermore, while FIG. 3 shows only a username and password as authentication information, other authentication information, such as OAuth, may also be set.

[0017] Buttons 304 to 309 are buttons for setting the read settings, and each button displays the current setting value. The "Read Target Settings" button 304 is a button for setting the read target (pressure plate or feeder). The "Paper Size Settings" button 305 is a button for setting the paper size to be read (A4 size, A3 size, etc.). The "Color Mode Settings" button 306 is a button for setting the color mode (color, black and white, etc.) during scanning. The "Feed Direction Settings" button 307 is a button for setting the feed direction of the document (short edge feed or long edge feed). The "File Format Settings" button 308 is a button for setting the file format of the image to be sent (JPEG, PDF, etc.). The "Resolution Settings" button 309 is a button for setting the resolution during scanning (300 dpi, 600 dpi, etc.).

[0018] The "Start Sending" button 310 is a button for starting the sending process. The "Cancel" button 311 is a button for closing this application.

[0019] Fig. 4 is a diagram showing an authentication information reception screen during push scanning of the MFP 101 according to the first embodiment. An example of the screen when an authentication error occurs during image transmission during push scanning on the MFP 101 will be described with reference to Fig. 4. A "Cancel" button 401 is a button for canceling the transmission process.

[0020] FIG. 5 is a diagram showing an authentication information re-entry screen for the scan application of the client terminal 102 according to the first embodiment. An example of a screen that accepts re-entry of authentication information from a user when an authentication error occurs during image transmission during push scanning in the scan application will be described with reference to FIG. 5. A "Set User Name" button 501 is a button for setting a username as authentication information when instructing the MFP 101 to retransmit. A "Set Password" button 502 is a button for setting a password as authentication information when instructing the image reading device to retransmit. When OAuth authentication is used as the authentication method, the screen may be configured so that authentication information is entered via a browser. A "Start Sending" button 503 is a button for requesting retransmission. A "Cancel" button 504 is a button for canceling retransmission.

[0021] Fig. 6 is a diagram showing a transmission completion screen of the scan application of the client terminal 102 according to the first embodiment. An example of the transmission completion screen of the scan application will be described with reference to Fig. 6. The "Done" button 601 is a button for closing the scan application.

[0022] 7 is a diagram showing the sequences of the MFP 101, the client terminal 102, and the destination terminal 103 according to the first embodiment. The sequence of processes implemented in the MFP 101, the client terminal 102, and the destination terminal 103 according to this embodiment will be described with reference to FIG.

[0023] 3 (S701). The client terminal 102 accepts destination setting and read setting operations and performs the respective settings (S702). The client terminal 102 detects that the "Start Sending" button 310 has been pressed (S703).

[0024] The client terminal 102 requests the MFP 101 to execute a push scan, and the MFP 101 responds to the request (S704). In this embodiment, the client terminal 102 is an example of an information processing device that issues a scan request for a push scan with a specified destination. In this embodiment, the network I / F 209 of the MFP 101 is an example of a receiving unit that receives the scan request.

[0025] The MFP 101 executes scanning (S705) and sends the scanned image to the specified destination (S706). In this case, the MFP 101 switches processing depending on whether an authentication error has occurred during transmission. This sequence describes the case where an authentication error has occurred. Here, in this embodiment, the scanner 205 of the MFP 101 is an example of a generating unit that scans a document and generates image data in accordance with a scan request. Also, in this embodiment, the network I / F 209 of the MFP 101 is an example of a transmitting unit that transmits a request including authentication information for accessing the destination and image data to the destination.

[0026] The MFP 101 stores the scanned image internally (S707). In this embodiment, the ROM 202 of the MFP 101 is an example of a storage unit that stores image data for transmission by re-authentication when a response indicating that authentication using the authentication information resulted in an error is received.

[0027] 4 (S708). The client terminal 102 requests the MFP 101 to acquire the scan status, and the MFP 101 responds to the request (S709). In this embodiment, the CPU 201 of the MFP 101 is an example of a notification unit that notifies the client terminal 102 of an error.

[0028] The client terminal 102 displays an authentication information re-entry screen as shown in FIG. 5 (S710). The client terminal 102 accepts input of authentication information (S711). The client terminal 102 detects that the start transmission button has been pressed (S712). The client terminal 102 requests the MFP 101 to execute a push scan using the authentication information input in S711, and the MFP 101 responds to the request (S713). The MFP 101 transmits the scanned image saved in S707 to the specified destination, including the authentication information included in S713 (S714). In this embodiment, the authentication information included in S713 is authentication information for re-authentication. In this case, the MFP 101 switches processing depending on whether or not a transmission authentication error has occurred. In this sequence, a case where a transmission authentication error has not occurred will be described.

[0029] The client terminal 102 requests the MFP 101 to acquire the scan status, and the MFP 101 responds to the request (S715). The client terminal 102 displays a transmission completion screen as shown in FIG.

[0030] 8 is a diagram showing the flow of the client terminal 102 according to the first embodiment. The flow of the client terminal 102 according to this embodiment will be described with reference to FIG.

[0031] The client terminal 102 displays a scan setting screen as shown in Fig. 3 (S801). The client terminal 102 receives an operation from the user (S802). The client terminal 102 determines whether the received operation is a read setting (S803). If it is a read setting, the client terminal 102 updates the corresponding read setting (S804). Then, the process proceeds to S802.

[0032] If the received operation is not a read setting, the client terminal 102 determines whether the received operation is a destination setting (S805). If it is a destination setting, the client terminal 102 updates the corresponding destination setting (S806). Then, the process proceeds to S802.

[0033] If the received operation is not a destination setting, the client terminal 102 determines whether the received operation is to start transmission (S807). If the received operation is not to start transmission, the process ends.

[0034] If transmission is to start, the client terminal 102 executes push scanning to the MFP 101 (S808). The client terminal 102 displays a transmission completion screen as shown in Fig. 6 (S809). Thereafter, the process ends.

[0035] Fig. 9 is a diagram showing details of the push scan flow of the client terminal 102 according to the first embodiment. Specifically, it shows details of the flow when the push scan of S808 in Fig. 8 is executed. The push scan flow of the client terminal 102 will be explained based on Fig. 9, and other figures will be used as necessary.

[0036] The client terminal 102 requests a push scan from the MFP 101 (S901). FIG. 10 shows the communication content of a push scan according to the first embodiment. FIG. 10(A) shows an example of the push scan request content. The request is made by using the POST method to the URI "http: / / 192.168.1.100 / ScanJob." Settings are written in the XML format of the ScanJob element in the message body. The Source element indicates the read target, with "Platen" indicating that the read target is a platen. The Direction element indicates the feed direction, with "ShortEdgeFeed" indicating that the feed direction is short edge feed. The Size element indicates the paper size to be read, with "A4" indicating that the paper size to be read is A4. The Format element indicates file transmission, with "jpeg" indicating that the file format is JPEG. The ColorMode element indicates the color mode, with "Color" indicating that the color mode is color. The Resolution element indicates the resolution at the time of scanning. The Destination element and below indicate destination information. The Uri element represents the destination URI. The UserName element represents the username of the authentication information. The Password element represents the password of the authentication information. If the authentication method is OAuth authentication, a separate element indicating access token information may be used. Figure 10(B) is an example of a successful response to an HTTP POST request.

[0037] The client terminal 102 sends a scan status acquisition request to the MFP 101 (S902). The request is sent using the GET method to the URI "http: / / 192.168.1.100 / ScanStatus."

[0038] FIG. 11 is a diagram showing the content of communication for acquiring a scan status according to the first embodiment. In response to a scan status acquisition request, the MFP 101 sends a response such as those shown in FIGS. 11A to 11C. Details of the scan status are described below the ScanStatus element in XML format in the message body. The State element indicates the status of the scan job, with "Scanning" indicating that scanning is in progress and "Idle" indicating that the job is waiting. The ScanPage element indicates the number of pages that have been scanned. The JobStatus element indicates the status of the scan job, with "Processing" indicating that processing is in progress, "WaitingAuth" indicating that re-authentication information is being accepted, and "Completed" indicating that the job has been completed. The JobResult element indicates the result of the scan job, with "Success" indicating successful completion and "Failure" indicating abnormal completion.

[0039] The client terminal 102 determines whether the scan job requested in S901 has been completed (S903).

[0040] If the JobStatus element of the XML acquired in S902 is "Completed," it is determined that the scan job is complete. If it is determined that the scan job is complete, the client terminal 102 ends the push scan process.

[0041] If the scan job is not completed, the client terminal 102 determines whether an authentication error has occurred (S904). If there is no authentication error, the process proceeds to S902.

[0042] If there is an authentication error, the client terminal 102 displays an authentication information re-entry screen as shown in FIG. 5 (S905). The client terminal 102 accepts the input of authentication information (S906). The client terminal 102 transmits the authentication information to the MFP 101 (S907). In this case, the client terminal 102 transmits the authentication information to the URI "http: / / 192.168.1.100 / ScanJob". More specifically, the client terminal 102 transmits the authentication information by specifying only the Destination element in XML format in the message body of the POST method. Note that the authentication information may also be transmitted using a URI dedicated to authentication information. Thereafter, the process proceeds to S902.

[0043] Fig. 12 is a diagram showing the flow of push scanning by the MFP 101 according to the first embodiment. The flow of push scanning by the MFP 101 according to this embodiment will be described with reference to Fig. 12. The flow of push scanning by the MFP 101 will be described based on Fig. 12, and other figures will be used as necessary.

[0044] The MFP 101 receives a push scan request (S1201). The MFP 101 sends a response to the requestor as shown in FIG. 10B (S1202). The MFP 101 performs scanning using the scan settings included in the scan request (S1203). The MFP 101 sends the scanned image to the specified destination included in the scan request (S1204). The MFP 101 determines whether the transmission was successful (S1205). If the transmission was successful, the MFP 101 ends the processing. If the transmission failed, the MFP 101 determines whether an authentication error occurred (S1206). If there was no authentication error, the MFP 101 ends the processing. If there was an authentication error, the MFP 101 stores the scanned image internally (S1207). The MFP 101 displays an authentication information reception screen as shown in FIG. 4 (S1208). The MFP 101 receives the authentication information (S1209). If the authentication information is not accepted for a certain period of time, or if a cancellation notice is received from the client terminal 102 via a specific URI prepared in advance, a predetermined process may be performed. Examples of the predetermined process include stopping the acceptance of the authentication information, deleting the saved image, and terminating the push scan process. Then, the process proceeds to S1204.

[0045] Fig. 13 is a diagram showing a flow when a scan status acquisition request is received by the MFP 101 according to the first embodiment. The flow of the scan status acquisition request by the MFP 101 according to this embodiment will be described with reference to Fig. 13. The description of the flow of the scan status acquisition request by the MFP 101 will be based on Fig. 13, and other figures will also be used as necessary.

[0046] The MFP 101 receives a scan status acquisition request (S1301). The MFP 101 acquires the scan status (S1302). The MFP 101 sends a response to the requestor as shown in FIGS. 11A to 11C depending on the scan status (S1303). If the scan job is currently being processed, the MFP 101 sends a response as shown in FIG. 11A. If the scan job has encountered an authentication error and is currently accepting authentication information again, the MFP 101 sends a response as shown in FIG. 11B. If the scan job has completed, the MFP 101 sends a response as shown in FIG. 11C.

[0047] According to the first embodiment, when an information processing device instructs an image reading device to perform a push scan including authentication information, if an authentication error occurs, the user can be prevented from having to place the document or perform the scan operation again. Note that in this embodiment, authentication information is accepted again when an authentication error occurs in the image forming device, but this is not limited to this. For example, a setting value may be provided that switches between accepting authentication information again or terminating the process with an authentication error when an authentication error occurs in the image forming device.

[0048] [Second embodiment] As a second embodiment of the present invention, a method will be described in which, when a client terminal 102 requests a push scan including authentication information from an MFP 101, the client terminal 102 checks in advance whether authentication will be successful using that authentication information. In this embodiment, it is assumed that HTTP is used for each communication, and that the IP address of the MFP 101 is "192.168.1.100."

[0049] The system configuration, the hardware configuration of the MFP 101, and the setting screen of the scan application of the client terminal 102 are the same as those in the first embodiment, so their explanations will be omitted and refer to Figures 1, 2, and 3, respectively. The screen that appears when an authentication error occurs when authentication information is verified in advance by the scan application of the client terminal 102 is the same as those in the first embodiment, so their explanations will be omitted and refer to Figure 5. The transmission completion screen of the scan application of the client terminal 102 is the same as those in the first embodiment, so their explanations will be omitted and refer to Figure 6.

[0050] 14 is a diagram showing the sequences of the MFP 101, the client terminal 102, and the destination terminal 103 according to the second embodiment. The sequence of processes implemented in the MFP 101, the client terminal 102, and the destination terminal 103 according to this embodiment will be described with reference to FIG.

[0051] 3 (S1401). The client terminal 102 accepts operations for destination setting and read setting, and performs the respective settings (S1402). The client terminal 102 detects that the "Start Sending" button 310 has been pressed (S1403).

[0052] The client terminal 102 verifies whether authentication with the destination terminal 103 will be successful using the authentication information entered in S1402 (S1404). In this case, the client terminal 102 switches processing depending on whether an authentication error has occurred. This sequence will explain the case where an authentication error has occurred. The client terminal 102 displays an authentication information re-entry screen as shown in FIG. 5 (S1405). The client terminal 102 accepts the input of authentication information (S1406). The client terminal 102 detects that the "Start Send" button 503 has been pressed (S1407). The client terminal 102 verifies whether authentication with the destination terminal 103 will be successful using the authentication information entered in S1406 (S1408). In this case, the client terminal 102 switches processing depending on whether an authentication error has occurred. This sequence will explain the case where an authentication error has not occurred. The client terminal 102 requests the MFP 101 to execute a push scan, and the MFP 101 responds to the request (S1409). The MFP 101 executes the scan (S1410) and transmits the scanned image to the specified destination (S1411). The client terminal 102 requests the MFP 101 to acquire the scan status, and the MFP 101 responds to the request (S1412). The client terminal 102 displays a transmission completion screen such as that shown in FIG. 6 (S1413).

[0053] The flow of the client terminal 102 is similar to the flow shown in Fig. 8 of the first embodiment, but the operation of the push scan in S808 is different. Therefore, the operation of the push scan in this embodiment will be explained in detail. Fig. 15 is a diagram showing the details of the push scan flow of the client terminal 102 according to the second embodiment. The details of the flow when a push scan is executed are shown with reference to Fig. 15.

[0054] The client terminal 102 verifies the authentication information (S1501). Examples of verification methods include obtaining a list of files in the destination folder path in the case of Basic authentication, and checking the expiration date of the access token in the case of OAuth authentication. If the authentication method is OAuth authentication and the access token has expired, a process of checking the renewal expiration date using a refresh token may be performed, and if the renewal is successful, it may be determined that the authentication is successful, or if the renewal is unsuccessful, it may be determined that an authentication error has occurred.

[0055] The client terminal 102 determines whether the verification result in S1501 is an authentication error (S1502).

[0056] In the case of an authentication error, the client terminal 102 displays an authentication information re-entry screen as shown in Fig. 5 (S1503). The client terminal 102 accepts the input of authentication information (S1504). Then, the process returns to S1501.

[0057] If there is no authentication error, the client terminal 102 requests a push scan from the MFP 101 (S1505). An example of the push scan request content is the same as in the first embodiment, so refer to FIG. 10A and a description thereof will be omitted. The client terminal 102 requests the MFP 101 to obtain a scan status (S1506). The request is made using a GET method to the URI "http: / / 192.168.1.100 / ScanStatus". The response to this request is the same as in the first embodiment, so a description thereof will be omitted and refer to FIGS. 11A and 11C. The client terminal 102 determines whether the scan job requested in S1505 has been completed (S1507).

[0058] If it is determined that the scan job is not completed, the process proceeds to S1506. On the other hand, if it is determined that the scan job is completed, the client terminal 102 ends the push scan process.

[0059] 16 is a diagram showing the flow of push scanning by the MFP 101 according to the second embodiment. The flow of push scanning by the MFP 101 according to this embodiment will be described with reference to FIG.

[0060] The MFP 101 receives a push scan request (S1601). The MFP 101 responds to the push scan request to the request source (S1602). The response content is the same as in the first embodiment, so a description will be omitted and refer to FIG. 10(B). The MFP 101 executes scanning using the read settings included in the scan request (S1603). The MFP 101 transmits the scanned image to the specified destination included in the scan request (S1604). The MFP 101 then ends the process.

[0061] The flow of the scan status acquisition request from the MFP 101 is the same as in the first embodiment, so the description will be omitted and reference will be made to FIG.

[0062] According to the second embodiment, when an information processing device instructs an image reading device to perform a push scan including authentication information, if an authentication error occurs, the user does not have to go through the trouble of placing a document again or setting up the scan again. Note that in this embodiment, re-authentication is performed in the preliminary verification of the authentication information in the information processing device, but this is not limited to this. For example, if an authentication error occurs in the preliminary verification of the authentication information in the client terminal, a setting value may be provided to switch between performing re-authentication or terminating with an authentication error.

[0063] [Third embodiment] As a third embodiment of the present invention, a method will be described in which, when an image reading device receives a push scan instruction, authentication information associated with the destination and the login user of the image reading device is used. The system configuration and the hardware configuration of the MFP 101 are the same as those in the first embodiment, so their explanation will be omitted and reference will be made to FIGS. 1 and 2, respectively.

[0064] 17 is a diagram showing a scan setting screen of the scan application of the client terminal 102 according to the third embodiment. An example of the scan setting screen of the scan application of the client terminal 102 will be described with reference to FIG.

[0065] The "Set destination" button 1701 is a button for setting a destination. By pressing the "Set destination" button 1701, the user can select a desired destination from the destinations registered in the client terminal 102. If the desired destination is not in the list of destinations, a new destination can be entered. It may also be possible to specify the folder path of the destination. Multiple destinations can be set, and a configuration may also be possible in which authentication information can be set for each destination.

[0066] Buttons 1702 to 1707 are buttons for setting the read settings, and each button displays the current setting value. The "Read Target Settings" button 1702 is a button for setting the read target (pressure plate or feeder). The "Paper Size Settings" button 1703 is a button for setting the paper size to be read (A4 size, A3 size, etc.). The "Color Mode Settings" button 1704 is a button for setting the color mode (color, black and white, etc.) during scanning. The "Feed Direction Settings" button 1705 is a button for setting the feed direction of the original (portrait feed or landscape feed). The "File Format Settings" button 1706 is a button for setting the file format of the image to be sent (JPEG, PDF, etc.). The "Resolution Settings" button 1707 is a button for setting the resolution during scanning (300 dpi, 600 dpi, etc.).

[0067] The "Start Sending" button 1708 is a button for starting the sending process. The "Cancel" button 1709 is a button for closing this application.

[0068] The transmission completion screen of the scan application of the client terminal 102 is the same as that in the first embodiment, so the description will be omitted and only refer to FIG.

[0069] 18 is a diagram showing the sequences of the MFP 101, the client terminal 102, and the destination terminal 103 according to the third embodiment. The sequence of processes implemented in the MFP 101, the client terminal 102, and the destination terminal 103 according to this embodiment will be described with reference to FIG.

[0070] The MFP 101 accepts a login operation (S1801). The client terminal 102 displays a scan setting screen as shown in Fig. 17 (S1802). The client terminal 102 accepts operations for destination setting and read setting, and performs the respective settings (S1803). The client terminal 102 detects that the "Start Sending" button 1708 has been pressed (S1804).

[0071] The client terminal 102 requests the MFP 101 to execute a push scan, and the MFP 101 responds to the request (S1805). The MFP 101 acquires the destination information included in the push scan request and the authentication information associated with the user who logged in in S1801 (S1806). Here, the ROM 202 of the MFP 101 is an example of a storage unit that stores the authentication information for accessing the destination in association with the logged-in user.

[0072] Table 1 is an example of a table for managing destination information and authentication information linked to the logged-in user. When Basic authentication is used as the authentication method, one record registers the logged-in user, destination, and the username and password as authentication information. When OAuth authentication is used as the authentication method, it may also be possible to register an access token or refresh token as authentication information. [Table 1]

[0073] The MFP 101 executes the scan (S1807) and sends the scanned image to the specified destination using the authentication information acquired in S1806 (S1808). The client terminal 102 requests the MFP 101 to acquire the scan status, and the MFP 101 responds to the request (S1809). The client terminal 102 displays a transmission completion screen such as that shown in FIG. 6 (S1810).

[0074] The flow of the client terminal 102 is the same as that of Fig. 8 in the first embodiment, but the push scan operation in S808 is different. Fig. 19 is a diagram showing details of the push scan flow of the client terminal 102 according to the third embodiment. Referring to Fig. 19, the details of the flow when a push scan is executed are shown.

[0075] The client terminal 102 requests a push scan from the MFP 101 (S1901). An example of the push scan request content is the same as that of the first embodiment, excluding the UserName element and Password element, and therefore, description thereof will be omitted and refer to FIG. 10(A). The client terminal 102 requests the MFP 101 to obtain a scan status (S1902). The request is made by using a GET method with the URI "http: / / 192.168.1.100 / ScanStatus". The response to this request is the same as that of the first embodiment, as shown in FIGS. 11(A) and 11(C), and therefore description thereof will be omitted and refer to FIG. 11(A) and 11(C). The client terminal 102 determines whether the scan job requested in S1901 has been completed (S1903).

[0076] If it is determined that the scan job is not completed, the process proceeds to S1902. If it is determined that the scan job is completed, the client terminal 102 ends the push scan process.

[0077] The flow of push scanning by the MFP 101 is the same as in the second embodiment, so its description will be omitted and refer to Fig. 12. The flow of a scan status acquisition request by the MFP 101 is the same as in the first embodiment, so its description will be omitted and refer to Fig. 13.

[0078] The third embodiment allows a user to request a push scan without inputting authentication information. In the present embodiment, when an image reading device receives a push scan instruction, authentication information associated with the destination and the logged-in user of the image reading device is used, but this is not limited to this. For example, a setting value may be provided that switches whether or not to use authentication information associated with the destination and the logged-in user of the image reading device when the image reading device receives a push scan instruction.

[0079] [Other embodiments] Although the present invention has been described in detail based on preferred embodiments thereof, the present invention is not limited to these specific embodiments, and various modifications within the scope of the present invention are also included in the present invention. In addition, parts of the above-described embodiments may be combined as appropriate.

[0080] The present invention can also be realized by supplying a program that realizes one or more functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program.The present invention can also be realized by a circuit (e.g., ASIC) that realizes one or more functions. [Explanation of symbols]

[0081] 101...MFP 102...Client terminal 103...Destination terminal 201...CPU 202...ROM 203...RAM 205...Scanner 209...Network I / F

Claims

1. a receiving means for receiving a scan request for a push scan with a specified destination from the information processing device; a generating means for scanning an original document and generating image data in accordance with the scan request; a transmitting means for transmitting a request including authentication information for accessing the destination and the image data to the destination; a storage means for storing the image data for transmission by re-authentication when a response indicating that authentication using the authentication information has resulted in an error is received; a notification means for notifying the information processing device of the error; When the receiving means receives authentication information for re-authentication in response to the error notification from the information processing device, the transmitting means transmits a request including the authentication information for re-authentication and the stored image data to the destination. An image reading device characterized by:

2. the receiving means receives, from the information processing device, authentication information for re-authentication in response to the error notification and the destination; The image reading device is a multifunction device that also has a printing function.

2. The image reading device according to claim 1, wherein:

3. The storage means stores the image data when authentication using the authentication information results in an error.

3. The image reading device according to claim 1, wherein the image reading device is a scanning device.

4. a receiving step of receiving a scan request for push scanning with a specified destination from the information processing device; a generating step of scanning an original document and generating image data in accordance with the scan request; a sending step of sending a request to the destination, the request including authentication information for accessing the destination and the image data; a storing step of storing the image data for transmission by re-authentication when a response indicating that authentication using the authentication information was an error is received; a notification step of notifying the information processing device of the error, When authentication information for re-authentication in response to the error notification is received from the information processing device in the receiving step, a request including the authentication information for re-authentication and the stored image data is transmitted to the destination in the transmitting step.

2. A method for controlling an image reading device, comprising:

5. 4. A program for causing a computer to function as each of the means of the image reading apparatus according to claim 1.

Images