Information processor, method of controlling information processor, and program

Abstract

To solve the problem that when a push scan is made from a first seen image processor to a user's information processor, it is difficult for the user who does not have knowledge to perform required cumbersome work requiring technical knowledge of servers, networks, etc.SOLUTION: A client terminal 110 establishes a communication connection with a nearby MFP 100 (604 to 606), and actuates an FTP server on the communication connection with the MFP 100 (607). The MFP 100 sets information for enabling data transmission to the client terminal 110 on the communication connection with the client terminal 110 (609 to 611), executes scan processing as instructed by a user, and transmits scan data to the client terminal 110 (614 to 616). The client terminal 110 receives the scan data from the MFP 100 via the FTP server (617). Then the FTP server is turned off (619) and the communication connection with the MFP 100 is broken (620).SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present invention relates to an information processing device, a control method for an information processing device, and a program. [Background technology]

[0002] Conventionally, the main use case for using an MFP (Multi Function Peripheral) was to use a specific MFP located near one's desk in one's own office. In recent years, with the increase in distributed work, workplaces have diversified, shifting from company offices to coworking spaces and shared offices where employees share an office environment. Even within the office, mobile devices such as laptops (Personal Computers) and tablets are increasingly used, and free address systems have become widespread, moving away from fixed desks. Due to this situation, there are more and more opportunities to use MFPs that people have never seen before, rather than the traditional MFP located near their desk in their own office.

[0003] Patent document 1 proposes a technology in which, when performing push scanning from an MFP, destination information (such as server URL and authentication information) of the server to which the scanned data is to be sent is set from a client terminal, and the destination information is included in the instruction to the MFP to perform a push scan. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2023-030444 Summary of the Invention [Problem to be solved by the invention]

[0005] When using the technology of Patent Document 1 to perform push scanning from an unfamiliar MFP to a user's mobile device in, for example, a coworking space or shared office, the user must perform tasks that require technical knowledge of servers, networks, etc. For example, on the user's mobile device, the user must configure the server to receive data from the MFP and set up a network connection between the mobile device and the MFP. Furthermore, to send scanned data from the MFP to the mobile device, the user must configure the MFP for transmission, such as the mobile device's IP address and communication protocol. Performing such configuration requires technical knowledge of servers, networks, etc. However, general users who only use MFPs often lack this technical knowledge, making it difficult for them to scan documents and import the data into their mobile device in such an environment. Even for users with this technical knowledge, configuring the mobile device and MFP is a cumbersome task.

[0006] The present invention has been made to solve the above-mentioned problems, and aims to provide a mechanism that enables a user to easily receive scan data obtained by scanning an original document with an image processing device into their own information processing device, even in an environment where the user is using the image processing device for the first time. [Means for solving the problem]

[0007] The present invention is an information processing device characterized by having a connection means for establishing a communication connection with an image processing device located close to the information processing device, a control means for enabling a function for receiving scanned data from the image processing device in accordance with the communication connection with the image processing device, and a receiving means for receiving scanned data obtained by scanning an original document with the image processing device from the image processing device using the function. [Effects of the Invention]

[0008] According to the present invention, even in an environment where an image processing device is being used for the first time, it is possible to easily scan an original document using the image processing device and receive the resulting scan data on one's own information processing device. As a result, even a general user who does not have technical knowledge of servers or networks can easily perform push scanning from an image processing device that the user has not seen before, such as in a coworking space or shared office, to an information processing device such as a PC. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram showing an example of details of a controller unit of the MFP. [Figure 3] FIG. 2 is a block diagram showing an example of details of a client terminal. [Figure 4] FIG. 2 is a block diagram showing an example of the software configuration of an MFP. [Figure 5] FIG. 2 is a block diagram illustrating an example of a software configuration of a client terminal. [Figure 6] FIG. 4 is a diagram showing an example of a sequence when a scan is performed according to the embodiment. [Figure 7A] FIG. 4 is a diagram showing an example of a screen displayed on a client terminal according to the first embodiment. [Figure 7B] FIG. 4 is a diagram showing an example of a screen displayed on a client terminal according to the first embodiment. [Figure 8A] FIG. 2 is a diagram showing an example of a screen displayed on the MFP according to the first embodiment. [Figure 8B] FIG. 2 is a diagram showing an example of a screen displayed on the MFP according to the first embodiment. [Figure 9] 10 is a flowchart showing an example of processing of a client terminal in a simple scan according to the first embodiment. [Figure 10] 6 is a flowchart showing an example of processing by the MFP in simple scanning according to the first embodiment. [Figure 11] FIG. 10 is a diagram showing an example of a screen displayed on the MFP according to the second embodiment. [Figure 12A]10 is a flowchart showing an example of processing by the MFP in simple scanning according to the second embodiment. [Figure 12B] 10 is a flowchart showing an example of processing by the MFP in simple scanning according to the second embodiment. [Figure 13] 10 is a flowchart showing an example of processing of a client terminal in a simple scan according to the second embodiment. [Figure 14] FIG. 4 is a diagram showing an example of a screen displayed on a client terminal according to the first embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. However, not all of the features described in the embodiment are necessarily essential to the solution of the present invention. In the embodiment of the present invention, an example in which an image forming apparatus and a client terminal cooperate with each other will be described.

[0011] [First embodiment] FIG. 1 is a diagram showing an example of the configuration of a system according to an embodiment of the present invention. The system in this embodiment includes an MFP 100 and a client terminal 110. The MFP 100 and the client terminal 110 are communicably connected via a network 150. In this embodiment, the network 150 is a wireless connection.

[0012] The MFP 100 is an image processing device such as a multifunction peripheral. The MFP 100 has functions for reading images by scanning, printing images by printer, and sending and receiving faxes. The MFP 100 has an operation unit 102 that handles input and output from a user. The MFP 100 has a printer unit 103 that outputs electronic data to paper media. The MFP 100 has a scanner unit 104 that reads paper media and converts it into electronic data. The operation unit 102, printer unit 103, and scanner unit 104 are connected to a controller unit 101, and function as a multifunction peripheral under the control of the controller unit 101. Note that the MFP 100 does not necessarily have to have the printer unit 103.

[0013] The client terminal 110 is an information processing device configured to include application programs (hereinafter referred to as "applications") such as a simple scan application 111, an operating system (hereinafter referred to as "OS") (not shown), various drivers, etc. The client terminal 110 may also include various applications (not shown), such as document creation and spreadsheet applications.

[0014] The simple scan application 111 connects to the MFP 100, activates an internal file server, and receives electronic data scanned by the MFP 100 at the file server.

[0015] Examples of client terminals include notebook PCs, tablet terminals, smartphones, etc. Note that Fig. 1 only describes the configuration for explaining this embodiment, so it goes without saying that other configurations may be included as long as they satisfy the implementation of the present invention, and the connection form between the respective components is not limited to this.

[0016] FIG. 2 is a block diagram showing an example of details of the controller unit 101 of the MFP. The CPU 201 performs the main arithmetic processing within the controller. The CPU 201 is connected to the DRAM 202 via a bus. The DRAM 202 is used by the CPU 201 as a working memory for temporarily storing program data representing arithmetic instructions during the CPU 201's arithmetic operations and data to be processed.

[0017] The CPU 201 is also connected to an I / O controller 203 via a bus. The I / O controller 203 performs input and output to and from various devices in accordance with instructions from the CPU 201. A SATA (Serial Advanced Technology Attachment) I / F 205 is connected to the I / O controller 203, and a flash ROM 210 is connected to the SATA I / F 205. The CPU 201 uses the flash ROM 210 to permanently store programs for realizing the functions of the MFP and document files. Instead of the flash ROM, another storage device such as an HDD (Hard Disk Drive) may be connected, or a configuration in which both are used in combination may be used.

[0018] A network I / F 204 is also connected to the I / O controller 203. Wired LAN devices and wireless LAN devices are connected to the network I / F 204. The CPU 201 controls the wired LAN devices and wireless LAN devices via the network I / F 204 to realize communication on the network 150. A panel I / F 206 is also connected to the I / O controller 203. The CPU 201 performs input and output to the operation unit 102 via the panel I / F 206 for the user.

[0019] A printer I / F 207 is also connected to the I / O controller 203. The CPU 201 performs output processing on paper media using the printer unit 103 via the printer I / F 207. A scanner I / F 208 is also connected to the I / O controller 203. The CPU 201 uses the scanner unit 104 via the scanner I / F 208 to implement a process of reading an image from a document.

[0020] The MFP 100 has various applications for utilizing the functions of the MFP. Examples of such applications include applications for copy, transmission, fax, box, etc. The CPU 201 loads program data corresponding to these functions from the Flash ROM 210 via the SATA I / F 205 into the DRAM 202 and executes the program data, thereby realizing these functions.

[0021] When performing the copy function, the CPU 201 detects a copy instruction from the user via the operation unit 102 via the panel I / F 206 in accordance with a program loaded into the DRAM 202. When the CPU 201 detects a copy instruction, it receives an original document as electronic data from the scanner unit 104 via the scanner I / F 208 and stores the data in the DRAM 202. The CPU 201 performs color conversion processing suitable for output on the image data stored in the DRAM 202. The CPU 201 transfers the image data stored in the DRAM 202 to the printer unit 103 via the printer I / F 207, and performs output processing onto paper media.

[0022] When the transmission function is performed, the CPU 201 detects a transmission instruction from the user in the same manner as in the copy function described above. The transmission instruction includes a transmission protocol, destination specification, image format, and the like from the user. The transmission protocol is, for example, Server Message Block (SMB) or File Transfer Protocol (FTP), and the destination specification is, for example, specified by Universal Naming Convention (UNC). The image format is, for example, Joint Photographic Experts Group (JPEG) or Portable Document Format (PDF). When the CPU 201 detects a transmission instruction, it receives the original as electronic data from the scanner unit 104 via the scanner I / F 208 and stores the data in the DRAM 202. The CPU 201 performs image format conversion, etc., as specified by the user, on the image data stored in the DRAM 202. The CPU 201 transfers the image data stored in the DRAM 202 to the destination via the network I / F 204 using the protocol specified by the user.

[0023] When the fax function is performed, the CPU 201 detects a fax instruction from the user in the same process as in the copy function described above. When the CPU 201 detects a fax instruction, it receives the original as electronic data from the scanner unit 104 via the scanner I / F 208 and stores it in the DRAM 202. The CPU 201 performs image format conversion for fax on the image data stored in the DRAM 202. The CPU 201 transfers the image data stored in the DRAM 202 to a fax telephone number specified in the fax instruction via a telephone line network (not shown) to which the fax I / F 209 is connected. Faxing via a telephone line is one example, and the data may also be an Internet fax.

[0024] The box function stores scanned images in a storage area within the MFP 100 or in a memory medium connected to the MFP 100, and also makes the images stored in the MFP 100 available to an external PC (not shown) or another MFP by using the MFP 100 as a file server. When the box function is implemented, the CPU 201 detects a box save instruction from the user in the same manner as the copy function described above. The box save instruction includes the user's save destination and image format. The save destination is a path to the internal storage of the MFP 100 or to a memory medium connected to the MFP 100. The image format is JPEG, PDF, or the like. Upon detecting a box save instruction, the CPU 201 receives the document as electronic data from the scanner unit 104 via the scanner I / F 208 and stores it in the DRAM 202. The CPU 201 then performs image format conversion, etc., as specified by the user, on the image data stored in the DRAM 202. The CPU 201 transfers the image data stored in the DRAM 202 via the SATA I / F 205 to a storage destination designated by the user, such as a flash ROM 210 inside the MFP 100 or a memory medium (not shown).

[0025] In the fax function, received images may not be printed but may be converted into a format viewable on a PC or the like and saved in a box. Furthermore, as a box function, the MFP 100 functions as a file server such as an SMB server, and makes the contents of the Flash ROM 210 public. In the box function, the CPU 201 detects an external box access instruction via the network I / F 204. The box access instruction includes the image file path of the access destination. The CPU 201 transfers the image data stored in the Flash ROM 210 corresponding to the specified image file path to the source of the box access instruction via the network I / F 204. The above is an example of the functions of the MFP 100, and other functions may also be included.

[0026] FIG. 3 is a block diagram showing an example of the details of the client terminal 110. As shown in FIG. The CPU 301 is connected to the DRAM 302 via a bus. The DRAM 302 is used by the CPU 301 as a working memory for temporarily storing program data representing arithmetic instructions and data to be processed during the arithmetic process performed by the CPU 301.

[0027] The CPU 301 is connected to the I / O controller 303 via a bus. A network I / F 304 is connected to the I / O controller 303. A wired LAN device, a wireless LAN device, or a data communication device is connected to the network I / F 304. The CPU 301 controls the wired LAN device, the wireless LAN device, or the data communication device via the network I / F 304 to realize communication on the network 150.

[0028] Furthermore, the I / O controller 303 performs input and output to and from various devices in accordance with instructions from the CPU 301 . A SATA (Serial Advanced Technology Attachment) I / F 305 is connected to the I / O controller 303, and a HDD 306 is connected to the SATA I / F 305. Instead of an HDD, other storage devices such as an SSD (Solid State Drive) or an eMMC (embedded MultiMediaCard) may be connected, or both may be used. The CPU 301 uses the HDD 306 to permanently store setting values ​​for programs such as the simple scan application 111 and the simple print application 112.

[0029] An input / output I / F 307 is also connected to the I / O controller 303, and the CPU 301 performs input / output for the user with respect to an input / output device of the connected client terminal 110 via the input / output I / F 307. As an example of an input / output device, a touch panel that also functions as an input / output device may be connected to the input / output I / F 307, or an output device such as a display for displaying and an input device such as a keyboard for inputting may both be connected to the input / output I / F 307.

[0030] 4 is a block diagram showing an example of the software configuration executed by controller unit 101 of MFP 100. The software executed by controller unit 101 is executed after CPU 201 reads a program stored in Flash ROM 210 into DRAM 202, and realizes, for example, functional units such as those shown as 401 to 409 in FIG.

[0031] The operation control unit 401 executes a process of displaying a screen image for the user on the operation unit 102, and also executes a process of detecting a user operation from the operation unit 102 and a process associated with a screen component such as a button displayed on the screen. The data storage unit 402 stores requests from other control units in the flash ROM 210 and reads them out.

[0032] A job control unit 403 controls the execution of jobs in accordance with instructions from other control units. An image processing unit 404 processes image data into a format suitable for each purpose in accordance with instructions from the job control unit 403 . A print processing unit 405 prints and outputs an image on a paper medium via a printer I / F 207 in accordance with an instruction from the job control unit 403 . The reading processing unit 406 reads the set document via the scanner I / F 208 in accordance with an instruction from the job control unit 403 .

[0033] In accordance with instructions from each control unit, the network control unit 407 inputs and outputs data from a LAN, Wi-Fi (registered trademark), or a public line network via the network I / F 204. The network control unit 407 also enables the data storage unit 402 to access data stored in the flash ROM 210 from an external device via the network control unit 407. Examples of data stored in the flash ROM 210 include images such as PDF and JPEG.

[0034] The FAX control unit 408 receives and processes FAX data received from the network control unit 407 in accordance with instructions from the job control unit 403, instructs the print processing unit 405 to print, and converts the FAX data into an image such as PDF or JPEG and stores it in the data storage unit 402. The FAX control unit 408 also transmits FAX data via the network control unit 407 based on image data read by the reading processing unit 406.

[0035] The simple scan control unit 409 performs processing related to scanning with the client terminal 110. The simple scan control unit 409 is a control unit for realizing processing on the MFP 100 side for realizing the function of the simple scan application 111 described in FIG. 1. The simple scan control unit 409 performs communication processing with the client terminal 110 using the network control unit 407. The simple scan control unit 409 also displays a scan execution screen and an error screen using the operation control unit 401. The simple scan control unit 409 also issues a scan instruction to the job control unit 403, executes scanning using the reading processing unit 406, and transmits the scan data stored in the data storage unit 402 to the client terminal 110 using the network control unit 407.

[0036] 5 is a block diagram showing an example of the software configuration of the client terminal 110. The software including the simple scan application 111 executed on the client terminal 110 is executed after the CPU 301 loads a program stored in the HDD 306 into the DRAM 302, and realizes, for example, functional units such as those shown as 501 to 509 in FIG.

[0037] The client operation control unit 501 executes processing for displaying a screen image for the user, detecting user operations, and processing associated with screen components such as buttons displayed on the screen. The client data storage unit 502 stores and reads electronic data such as image files in the HDD 306 .

[0038] The client network control unit 503 performs network communication with external devices. The client FTP server control unit 504 executes the FTP server function within the client terminal 110 and exchanges data with the MFP 100 using the client network control unit 503 .

[0039] The client simple scan control unit 505 uses the above-mentioned control units 501 to 504 to provide the user of the client terminal 110 with a simple scan function (the function of the simple scan application 111). The client terminal 110 operates on an OS, and applications such as the simple scan application 111 run on the OS. However, since this is not the essence of this embodiment, the operation of the OS will be omitted.

[0040] The operation of this embodiment will be outlined below with reference to FIGS. 6, 7A, 7B, 8A, and 8B. Fig. 6 is a diagram showing an example of a sequence when client terminal 110 connects to MFP 100 and executes a scan. Note that the processing of client terminal 110 in Fig. 6 is executed by a function realized by CPU 301 loading a program stored in HDD 306 into DRAM 302 and executing it. Also, the processing of MFP 100 is executed by a function realized by CPU 201 loading a program stored in Flash ROM 210 into DRAM 202 and executing it. 7A and 7B are diagrams showing examples of screens displayed on the client terminal 110 in the first embodiment. FIG. 8 is a diagram showing an example of a screen displayed on the MFP 100 of the first embodiment. Hereinafter, Figures 7A and 7B will be collectively referred to as "Figure 7," and Figures 8A and 8B will be collectively referred to as "Figure 8."

[0041] When the user issues an instruction to launch the simple scan application to the client terminal 110 (601), the client terminal 110 accepts the instruction to launch the simple scan application from the user.

[0042] When the client terminal 110 receives an instruction to start the simple scan application, it starts the simple scan application 111 in 602. When the simple scan application 111 starts, a connection screen such as that shown in FIG. 7(a) is displayed on the output device connected to the input / output I / F 307 of the client terminal 110.

[0043] As shown in FIG. 7( a ), the connection screen displays a connection button 701 for connecting to an MFP 100 near the client terminal 110 . When the user presses the connection button 701 to connect to a nearby MFP 100 (603), the client terminal 110 detects the pressing of the connection button 701 and accepts an instruction to connect to the nearby MFP. Note that if there are multiple nearby MFPs, the user may select the MFP to connect to from a list of nearby MFPs. When the client terminal 110 receives an instruction from the user to connect to a nearby MFP, it makes a connection request to the nearby MFP, MFP 100 (604).

[0044] When the MFP 100 receives a connection request from the client terminal 110, it performs connection processing (605). As a result, a network connection (communication connection) is established between the MFP 100 and the client terminal 110 (606). Note that the network connection between the MFP 100 and the client terminal 110 in the above steps 604 to 606 is established, for example, by the well-known Wi-Fi Direct. This connection directly connects the client terminal 110 and the MFP 100 by wireless communication, and may be realized not only by Wi-Fi Direct but also by other wireless communication such as Bluetooth (registered trademark). This connection may also be established using a wired LAN.

[0045] When a network connection with the MFP is established, the client terminal 110 starts up an FTP server (607). Note that, in this embodiment, an example is shown in which FTP is used as the file transfer protocol for scanned electronic data between the MFP 100 and the client terminal 110, but it is not limited to FTP as long as it is a protocol that can transmit files. For example, SFTP (SSH File Transfer Protocol or Secure File Transfer Protocol), SMB, WebDAV (Web-based Distributed Authoring and Versioning), HTTP (Hyper Text Transfer Protocol), etc. may also be used. That is, in 607, a function for receiving scan data from the MFP 100 is enabled in accordance with the communication connection with the MFP 100. Next, the client terminal 110 displays a scan preparation completion screen as shown in FIG. 7(b) on the output device of the client terminal 110 (608).

[0046] After the network connection is established in step 605, the MFP 100 acquires the IP address of the connected client terminal 110 (step 609). For example, the MFP 100 acquires the IP address that was set when the connection was established via Wi-Fi Direct.

[0047] Furthermore, MFP 100 acquires a user name and password to be used in FTP for transmitting the scanned electronic data (610). The user name and password may be fixed and predetermined between MFP 100 and client terminal 110. Alternatively, a unique value may be generated using an assigned IP address, date and time, and a hash function common to MFP 100 and client terminal 110. Alternatively, the IP address of client terminal 110 and the above-mentioned user name, password, etc. may be transmitted from client terminal 110 to MFP 100, and received by MFP 100. Furthermore, the MFP 100 sets the IP address acquired in 609 and the user name and password acquired in 610 as the destination of the scanned electronic data (611).

[0048] The MFP 100 is now ready to execute scanning through the above steps 609 to 611, and displays a simple scan execution screen as shown in FIG. 8(a) on the operation unit 102 (612).

[0049] As shown in FIG. 8(a), the easy scan execution screen displays default scan settings 801. In the example of FIG. 8(a), the scan resolution is set to 300 dpi, the color setting is set to automatic detection, double-sided scanning, and the file format is set to PDF. The scan settings may be other than those shown in the default scan settings 801. For example, the easy scan execution screen may be configured to allow image stitching (scanning a document larger than the platen into multiple parts and stitching them together into a single image). In this embodiment, an example using an ADF (Automatic Document Feeder) is described, but scanning may also be performed by placing a document on the platen.

[0050] The change settings button 803 is a button for changing scan settings. The start scan button 802 is a button for executing a scan. The stop button 804 is a button that is pressed when canceling a simple scan. The stop button 804 is a button for canceling a simple scan when, for example, a certain user connects the client terminal 110 to the MFP 100 but leaves the MFP 100 connected without using it, and another user wants to use the MFP 100 for copying or the like.

[0051] The user places a document on the MFP 100 and presses the scan start button 802 on the simple scan execution screen in Fig. 8(a) to instruct the start of scanning (613). In response, the MFP 100 accepts a command to start scanning from the user. It is also possible to display the simple scan execution screen in 612 immediately after the connection is established in 606, and then execute the processes in 609 to 611. In this case, the user can issue a scan instruction immediately after the connection is established between the client terminal 110 and the MFP 100.

[0052] When the MFP 100 receives an instruction to start scanning, it reads the original using, for example, the ADF and executes the scan process (614) in accordance with the scan-related settings in the scan settings 801. In the example of Fig. 6, scanning is executed with settings of 300 dpi resolution, automatic color detection, and double-sided scanning. At this time, the MFP 100 displays a screen (such as the one in Fig. 8(b)) on the operation unit 102 indicating that scanning is in progress.

[0053] When the scan process executed in 614 above is completed, the MFP 100 generates (615) an image file according to the file format of the scan settings 801. In the example of Fig. 6, a PDF file is created. The file name may be a unique name based on the date and time the scan was executed, or the name may be obtained from the results of OCR (Optical Character Recognition).

[0054] Next, MFP 100 connects to client terminal 110 via FTP using the IP address, user name, and password set in 611 above, and transmits the file generated in 615 above to client terminal 110 (616). At this time, the scanned file may be transmitted to the top directory of the FTP server of client terminal 110, or a directory named after the date of scanning may be created instead of the top directory of the FTP server and the file may be transmitted under that directory, or the file may be transmitted to another directory. Note that authentication and file transmission using a file transfer protocol such as FTP are well-known techniques, and therefore details thereof will be omitted.

[0055] In the client terminal 110, the FTP server performs a process of receiving the file from the MFP 100 (617). Then, when the reception process of the FTP server in 617 is completed, the client terminal 110 displays a file reception completion screen as shown in FIG. 7(c) on the output device of the client terminal 110 (618).

[0056] As shown in Fig. 7(c), the file reception completion screen displays a destination directory display button 702. When the user presses the destination directory display button 702, the client terminal 110 displays the directory in which the scanned electronic data is saved, as shown in Fig. 7(d). Furthermore, the client terminal 110 terminates (619) the FTP server started in the above step 607. That is, in step 619, the function for receiving scan data from the MFP 100 is disabled. Then, the client terminal 110 requests the MFP 100 to disconnect (620).

[0057] When the MFP 100 receives the disconnection request from the client terminal 110, it executes a Wi-Fi Direct disconnection process based on the disconnection request (621) and discards the network connection between the MFP 100 and the client terminal (622). Then, the MFP 100 displays a menu screen on the operation unit 102 that allows the user to perform functions such as copying and faxing (not shown), and ends the simple scan process (623).

[0058] As described above, the user can easily perform push scanning from the MFP to their own PC by simply issuing an instruction to start the simple scan app (601), an instruction to connect to the MFP (603), and an instruction to set a document and execute scanning (613). Then, once the scan is complete, the connection to the MFP is automatically disconnected. This prevents the user from remaining connected to the MFP if they forget to disconnect the MFP. When the simple scan application is started, the simple scan application may automatically start a connection with a nearby MFP without an MFP connection instruction (603) from the user.

[0059] The processing of the client terminal 110 in the simple scan will be described below. 9 is a flowchart showing an example of processing of the client terminal 110 in simple scanning according to the first embodiment (processing when the client terminal 110 connects to the MFP 100 and executes simple scanning). The processing in FIG. 9 is executed by a function realized by the CPU 301 loading a program stored in the HDD 306 into the DRAM 302 and executing it. The processing of this flowchart starts when the user starts the simple scanning app on the client terminal 110 and the simple scanning app 111 is launched.

[0060] In S901, the client simple scan control unit 505 checks whether it has received an instruction to connect to the MFP 100. Specifically, the client simple scan control unit 505 determines whether the connection button 701 on the connection screen shown in FIG. 7A has been pressed by checking a response from the client operation control unit 501. If it is determined that the instruction to connect to the MFP 100 has not been received (No in S901), the client simple scan control unit 505 repeats the process of S901. On the other hand, if it is determined that an instruction to connect to the MFP 100 has been received (Yes in S901), the client simple scan control unit 505 advances the process to S902.

[0061] In S902, the client simple scan control unit 505 executes a process for connecting to the MFP 100 via the client network control unit 503. In the process for connecting to the MFP 100, the processes on the client terminal 110 side shown in 604 to 606 in FIG. 6 are performed, and the MFP 100 and the client terminal 110 are connected.

[0062] Next, in step S903, the client simple scan control unit 505 determines whether or not the connection with the MFP 100 has been completed. Specifically, the client network control unit 503 checks whether or not the connection with the MFP 100 has been established. Here, if it is determined that the connection with the MFP 100 has not been completed (No in S903), the client simple scan control unit 505 advances the process to S904.

[0063] In S904, the client simple scan control unit 505 determines whether a connection timeout has occurred. A predetermined connection timeout time is set, and if this value is exceeded, it is determined that a connection timeout has occurred. If this value is not exceeded, it is determined that a connection timeout has not occurred.

[0064] If it is determined that a connection timeout has not occurred (No in S904), the client simple scan control unit 505 returns the process to S903 and reconfirms whether the connection with the MFP 100 has been completed.

[0065] On the other hand, if it is determined that a connection timeout has occurred (Yes in S904), the process proceeds to S905. In S905, the client network control unit 503 uses the client operation control unit 501 to display an error screen such as that shown in Fig. 7(e) on the output device of the client terminal 110, indicating that connection with the MFP 100 has not been completed. Fig. 7(e) is an example of the error screen. In this case, since connection with the MFP 100 has not been established, the client network control unit 503 displays the error screen and then ends the processing of this flowchart.

[0066] Furthermore, in the above S903, if it is determined that the connection with the MFP 100 has been completed (Yes in S903), the client network control unit 503 advances the process to S906.

[0067] In S906, since the client network control unit 503 has completed the connection with the MFP 100, it starts the FTP server using the client FTP server control unit 504. This enables the client terminal 110 to communicate with the MFP 100 using the FTP protocol. As described above, in this embodiment, FTP is used as the file transfer protocol, but communication with the MFP 100 may also be performed using another protocol.

[0068] Next, in S907, the client simple scan control unit 505 sets a user name and password that can access the FTP server started in S906 (a user name and password that permits connection to the FTP server). As shown in 610 in Fig. 6, the user name and password may be fixed values, or a unique value may be generated using a hash function or the like, as long as they are common to the MFP 100 and the client terminal 110. Furthermore, the user name and password, the IP address of the client terminal 110, and the like may be transmitted from the client terminal 110 to the MFP 100.

[0069] Next, in S908, the client simple scan control unit 505 uses the client operation control unit 501 to display a scan preparation completion screen such as that shown in Fig. 7(b) on the client terminal 110. Fig. 7(b) is an example of the scan preparation completion screen.

[0070] Next, in S909, the client simple scan control unit 505 confirms whether electronic data (file) from the MFP 100 has been transmitted to a predetermined directory via the client FTP server control unit 504 and the client data storage unit 502. Specifically, the client FTP server control unit 504 receives the electronic data from the MFP 100 via the client network control unit 503 using the FTP protocol, and stores the data in a predetermined directory using the client data storage unit 502. The client FTP server control unit 504 then notifies the client simple scan control unit 505 that it has completed receiving the electronic data from the MFP 100. The client simple scan control unit 505 receives a completion notification from the client FTP server control unit 504, and confirms, using the client data storage unit 502, whether electronic data with a predetermined file name has been stored in a predetermined directory. Note that the predetermined file name conforms to a rule that the file name is unique between the MFP 100 and the client terminal 110, as shown by 615 in FIG. 6 .

[0071] Here, if electronic data with the specified file name is not stored in the specified directory, the client simple scan control unit 505 determines that electronic data (file) has not been sent from the MFP 100 (No in S909), and proceeds to S910. On the other hand, if electronic data with the specified file name is stored in the specified directory, the client simple scan control unit 505 determines that electronic data (file) has been sent from the MFP 100 (Yes in S909), and proceeds to S912.

[0072] In S910, since electronic data with the specified file name is not stored in the specified directory, the client simple scan control unit 505 checks whether a predetermined file transfer timeout value has been exceeded. If the timeout value has not been exceeded (No in S910), the client simple scan control unit 505 returns the process to S909 and checks again whether the electronic data sent from the MFP 100 has been stored in the specified directory.

[0073] On the other hand, if the timeout value has been exceeded (Yes in S910), the client simple scan control unit 505 advances the process to S911. In S911, since the electronic data could not be sent from the MFP 100 within the specified time, the client simple scan control unit 505 displays a transmission failure error screen using the client operation control unit 501. Fig. 7(f) is an example of the transmission failure error screen. In order to end the processing after displaying the transmission failure error screen, the client simple scan control unit 505 advances the processing to S913 and performs termination processing of the FTP server.

[0074] Furthermore, in S912, since the electronic data transmitted from the MFP 100 has been stored in a predetermined directory with a predetermined file name, the client simple scan control unit 505 uses the client operation control unit 501 to display a scan completion screen such as that shown in Fig. 7(c) on the output device of the client terminal 110. Fig. 7(c) is an example of the scan completion screen, and as it has already been explained in 618 of Fig. 6, details will be omitted. After displaying the scan completion screen, the client simple scan control unit 505 advances the process to S913.

[0075] In S913, the client simple scan control unit 505 terminates the FTP server function. Specifically, the client simple scan control unit 505 instructs the client FTP server control unit 504 to terminate the FTP server, and terminates the FTP server function. After terminating the FTP server function, the client simple scan control unit 505 advances the process to S914.

[0076] In S914, the client simple scan control unit 505 executes disconnection processing to the MFP 100 via the client network control unit 503. In the disconnection processing with the MFP 100, the processing on the client terminal 110 side shown by 620 to 622 in Fig. 6 is performed, and the MFP 100 and the client terminal 110 are disconnected. After the processing of S914, the client simple scan control unit 505 ends the processing of this flowchart.

[0077] The processing of the MFP 100 in simple scanning will be described below. 10 is a flowchart showing an example of processing by MFP 100 in simple scanning according to the first embodiment (processing from when MFP 100 receives an instruction to start simple scanning from client terminal 110, executes scanning, and transmits a file to client terminal 110). The processing in FIG. 10 is executed by a function realized by CPU 201 loading a program stored in Flash ROM 210 into DRAM 202 and executing it. The processing of this flowchart starts when MFP 100 starts up.

[0078] In S1001, the simple scan control unit 409 checks whether a connection instruction has been received from the client terminal 110. Specifically, the simple scan control unit 409 queries the network control unit 407 to check whether a connection request has been received from the client terminal 110.

[0079] If no connection request is received from the client terminal 110 (No in S1001), the simple scan control unit 409 performs the process of S1001 again to check again whether a connection request has been received from the client terminal 110. On the other hand, if a connection request has come from the client terminal 110 (Yes in S1001), the simple scan control unit 409 advances the process to S1002.

[0080] In S1002, the simple scan control unit 409 executes connection processing with the client terminal 110 via the network control unit 407. In the connection processing with the client terminal 110, processing on the MFP 100 side shown in 604 to 606 in FIG. 6 is performed, and the MFP 100 and the client terminal 110 are connected.

[0081] Next, in S1003, the simple scan control unit 409 determines whether or not the connection with the client terminal 110 has been completed. Specifically, the network control unit 407 checks whether or not the connection with the client terminal 110 has been established. Here, if it is determined that the connection with the client terminal 110 has not been completed (No in S1003), the simple scan control unit 409 advances the process to S1004.

[0082] In S1004, the simple scan control unit 409 determines whether a connection timeout has occurred. In this process, a predetermined connection timeout period is set, and it is determined whether this period has been exceeded. If it is determined that a connection timeout has not occurred (No in S1004), the simple scan control unit 409 returns the process to S1003 and reconfirms whether the connection with the client terminal 110 has been completed.

[0083] On the other hand, if it is determined that a connection timeout will occur (Yes in S1004), the simple scan control unit 409 advances the process to S1005. In S1005, the network control unit 407, using the operation control unit 401, displays an error screen such as that shown in FIG. 8C on the operation unit 102 because connection with the client terminal 110 was not completed. FIG. 8C is an example of the error screen. When the end button 810 on the error screen is pressed, the network control unit 407 advances the process to S1024, and displays a menu screen (not shown) on the MFP 100.

[0084] Furthermore, in the above S1003, if it is determined that the connection with the client terminal 110 has been completed (Yes in S1003), the simple scan control unit 409 advances the process to S1006.

[0085] In S1006, the simple scan control unit 409 acquires the IP address of the connected client terminal 110. Specifically, the simple scan control unit 409 inquires of the network control unit 407 about the IP address of the connected client terminal 110.

[0086] Next, in S1007, the simple scan control unit 409 sets the IP address acquired in S1006 as the destination of the scanned electronic data. Specifically, the simple scan control unit 409 sets the IP address acquired in S1006 as the destination of the FTP.

[0087] In S1008, the simple scan control unit 409 sets a directory in the client terminal 110 where the scanned electronic data is to be stored. The directory is predetermined by the MFP 100 and the client terminal 110, and is, for example, the top directory of the FTP server of the client terminal 110. As described in 616 in Fig. 6, instead of sending the scanned file to the top directory of the FTP server of the client terminal 110, a directory with the date of scanning may be created and the data may be sent under that directory, or the data may be sent to another directory.

[0088] Next, in S1009, the simple scan control unit 409 sets authentication information for communicating with the client terminal 110 (i.e., information for enabling data transmission addressed to the client terminal 110). The authentication information is a user name and a password, and for example, information common to the MFP 100 and the client terminal 110 is used using the method described in 610 of FIG. 6 . Note that the simple scan control unit 409 may receive and set the IP address of the client terminal 110, the above-mentioned user name and password, etc. from the client terminal 110 via the network control unit 407. Note that in this embodiment, FTP is used as the file transmission protocol, and therefore a user name and password are used as the authentication information; however, if another protocol is used, other authentication information may be used depending on the protocol.

[0089] Next, in S1010, the simple scan control unit 409 instructs the operation control unit 401 to display a simple scan execution screen such as that shown in Fig. 8(a) on the operation unit 102. Fig. 8(a) is an example of the simple scan execution screen.

[0090] Next, in S1011, the simple scan control unit 409 inquires of the operation control unit 401 to check whether a scan instruction has been issued. Specifically, the operation control unit 401 makes this determination based on whether the scan start button 802 has been pressed. Here, if there is no scan instruction (No in S1011), the simple scan control unit 409 advances the process to S1012.

[0091] In S1012, the simple scan control unit 409 checks whether a timeout has occurred after a specified time has elapsed without a scan being executed. This is performed to check whether a user has connected to the MFP 100 but left it without executing a scan. If it is determined that no timeout has occurred (No in S1012), the simple scan control unit 409 advances the process to S1013.

[0092] In S1013, the simple scan control unit 409 checks with the operation control unit 401 whether the stop button 804 has been pressed. If it is determined that the stop button has not been pressed (No in S1013), the simple scan control unit 409 returns the process to S1011 and checks again whether a scan instruction has been issued.

[0093] On the other hand, if it is determined that the cancel button has been pressed (Yes in S1013), the user has instructed to end the simple scan process, so the simple scan control unit 409 proceeds to S1023 to end the process, and performs processing to terminate the connection with the client terminal 110.

[0094] Furthermore, if it is determined in S1012 that a timeout has occurred (Yes in S1012), the simple scan control unit 409 advances the process to S1014. In S1014, the simple scan control unit 409 instructs the operation control unit 401 to display a scan execution timeout error screen such as that shown in Fig. 8(d) on the operation unit 102. Fig. 8(d) is an example of the scan execution timeout error screen. After the processing of S1014, the simple scan control unit 409 advances the processing to S1023 and performs processing to discard the connection with the client terminal 110.

[0095] Furthermore, if it is determined in S1011 above that a scan instruction has been issued (Yes in S1011), the simple scan control unit 409 proceeds to S1015. Note that in this embodiment, for simplicity of explanation, the process of changing the scan-related setting values ​​shown in 612 in Fig. 6 is not illustrated, but it may be performed as follows: Before the instruction to execute a scan is issued in S1011 above, it may be determined whether the setting change button 803 has been pressed, and the process of changing the scan-related settings may be performed.

[0096] In S1015, the simple scan control unit 409 executes the scan process. Specifically, the simple scan control unit 409 issues a scan job to the job control unit 403, and the job control unit 403 uses the reading processing unit 406 to read the document and generate electronic data. However, the electronic data generated at this point is device-specific and is not yet in a format that can be generally handled. When scanning is performed using the ADF, the document set in the ADF is read sequentially in this scan process, and the scan process is completed when all the documents set in the ADF have been read. When scanning is performed by placing a document on the document platen, a screen is displayed on the operation unit 102 each time one document is read, in order to receive a user instruction to select whether to read the next document or to end the scan. When the user issues an instruction to read the next document, the document is read, and when the user issues an instruction to end the scan, the scan process is completed. Furthermore, when the scan setting is set to "double sided," both sides of the document are read, and when the scan setting is set to "image stitching," the control is such that the number of scans to be stitched together is read for one document.

[0097] Next, in S1016, the simple scan control unit 409 generates a file name to be sent to the client terminal 110. As described in 615 of FIG. 6, the file name may be uniquely named based on the date and time the scan was performed, or may be named based on the results of OCR (Optical Character Recognition). Note that while this embodiment describes the scanned electronic data as being in a multi-page format such as PDF or TIFF, it may also be in a single-page format such as JPEG. If the format is a single-page format, a unique file name may be created by adding a number indicating the page number to the end of the file name generated by the method described above with reference to 615 of FIG. 6.

[0098] Next, in S1017, the simple scan control unit 409 generates a file to be sent to the client terminal 110 with the file name generated in S1016 above, in accordance with the file format setting of the scan settings 801. Specifically, the job control unit 403 instructs the image processing unit 404 to convert the scanned electronic data into a desired image format. Thereafter, the data storage unit 402 stores the electronic data converted into the desired image format in a storage area of ​​the MFP 100.

[0099] Next, in S1018, the simple scan control unit 409 transmits the file generated in S1017 to the client terminal 110. Specifically, the simple scan control unit 409 instructs the network control unit 407 to retrieve the electronic data stored in the data storage unit 402, and transmits the file to the client terminal 110 via communication using the FTP protocol. Note that in the description of this embodiment, FTP negotiation, authentication, and the like are well-known technologies and are not essential, so a description thereof will be omitted, but it goes without saying that they are implemented to transmit files via FTP.

[0100] Next, in S1019, the simple scan control unit 409 checks whether the scanned electronic data has been successfully transmitted to the client terminal 110. Specifically, the simple scan control unit 409 checks with the network control unit 407 to confirm whether all the data of the desired file has been successfully transmitted to the client terminal 110.

[0101] If it is determined that transmission was not possible due to a network problem or the like (No in S1019), the simple scan control unit 409 advances the process to S1020. In S1020, the simple scan control unit 409 uses the operation control unit 401 to display a file transmission error screen such as that shown in Fig. 8(e) on the operation unit 102. Fig. 8(e) is an example of the file transmission error screen. After the processing of S1020, the simple scan control unit 409 advances the processing to S1023.

[0102] Furthermore, in the above S1019, if it is determined that transmission has been successful (Yes in S1019), the simple scan control unit 409 advances the process to S1021. In S1021, the simple scan control unit 409 checks whether a disconnection instruction has been received from the client terminal 110. This is to check whether a disconnection instruction has been received from the MFP 100 after the disconnection process from the client terminal 110 to the MFP 100 has been executed in S914 of Fig. 9. Specifically, the simple scan control unit 409 queries the network control unit 407 to check whether a disconnection instruction has been received from the client terminal 110.

[0103] Here, if it is determined that there is no disconnection instruction from the client terminal 110 (No in S1021), the simple scan control unit 409 advances the process to S1022. In S1022, after transmitting the scanned electronic data to the client terminal 110, the simple scan control unit 409 checks whether a disconnection instruction from the client terminal 110 has timed out without arriving within a specified time.

[0104] If it is determined that the timeout has not occurred (No in S1022), the simple scan control unit 409 returns the process to S1021 and checks again for a disconnection instruction from the client terminal 110. On the other hand, if it is determined that a timeout has occurred (Yes in S1022), The process proceeds to S1023, where disconnection processing from the client terminal 110 is performed.

[0105] Furthermore, in the above S1021, if it is determined that a disconnection instruction has been received from the client terminal 110 (Yes in S1021), the simple scan control unit 409 advances the process to S1023.

[0106] In S1023, the simple scan control unit 409 executes processing to disconnect from the client terminal 110 via the network control unit 407. In the processing to disconnect from the client terminal 110, the processing on the MFP 100 side shown in 620 to 622 in Fig. 6 is performed to disconnect the MFP 100 and the client terminal 110. Note that if a timeout occurs in S1022 above and there is no disconnection instruction from the client terminal 110, the MFP 100 forcibly discards the connection with the client terminal 110. After the processing of S1023, the simple scan control unit 409 advances the processing to S1024.

[0107] In S1024, the simple scan control unit 409 ends the simple scan function and instructs the operation control unit 401 to display a menu screen on the operation unit 102 that enables execution of functions such as copying and faxing (not shown) in order to release the MFP 100 to other users. After S1024, the simple scan control unit 409 temporarily ends the processing of this flowchart, but this flowchart is executed again, and the simple scan control unit 409 waits in S1001 to accept the next request from the client terminal 110.

[0108] Through the above processing, even in an environment where an MFP is being used for the first time, a user can simply instruct the client terminal 110 to scan with the MFP 100, and make settings for sending scan data between the client terminal 110 and the MFP 100. This makes it possible to easily execute a scan and send the data to the client terminal 110. Therefore, even a general user who only uses an MFP and does not have technical knowledge of servers, networks, etc. can easily perform push scanning from an MFP they have never seen before in a coworking space, shared office, or the like to their own PC. This significantly improves the usability of push scanning from an MFP to a PC.

[0109] [Second Example] In the first embodiment, the simple scan ends after the first scan is completed. In the present embodiment, however, an example will be described in which scanning can be continued after the first scan is completed.

[0110] The processing of MFP 100 in simple scanning according to the second embodiment will be described below with reference to Figures 11, 12A, and 12B. Figures 12A and 12B will be collectively referred to as "Figure 12" below. FIG. 11 is a diagram showing an example of a screen displayed on the MFP 100 of the second embodiment. Fig. 12 is a flowchart showing an example of processing by MFP 100 in simple scanning according to the second embodiment (processing in which, after scanning is completed, confirmation is made as to whether scanning should be continued and scanning can be continued). The processing in Fig. 12 is executed by a function realized by CPU 201 loading a program stored in Flash ROM 210 into DRAM 202 and executing it. This flow starts when MFP 100 is started. In Fig. 12, the same steps as those in Fig. 10 are assigned the same step numbers, and descriptions thereof will be omitted.

[0111] In the second embodiment, if the simple scan control unit 409 determines in S1019 that the scanned electronic data has been successfully transmitted to the client terminal 110 (Yes in S1019), the process proceeds to S1201.

[0112] In S1201, the simple scan control unit 409 instructs the operation control unit 401 to display a scan continuation confirmation screen such as that shown in Fig. 11(a) on the operation unit 102. Fig. 11(a) is an example of the scan continuation screen. The scan continuation screen includes a scan continuation button 1101 for continuing scanning and an end button 1102 for ending scanning.

[0113] Next, in S1202, the simple scan control unit 409 determines whether an instruction to continue scanning has been given on the scan continuation screen displayed in S1201. In detail, the simple scan control unit 409 uses the operation control unit 401 to check whether the scan continuation button 1101 or the end button 1102 has been pressed. For example, if the user wants to continue scanning another document, the user places the document to be read next in the ADF or the like of the MFP 100 and presses the scan continuation button 1101.

[0114] Here, if it is determined that the continue scan button 1101 has been pressed and scanning is to be continued (Yes in S1202), the simple scan control unit 409 advances the process to S1203. In S1203, the simple scan control unit 409 uses the network control unit 407 to send a scan continuation notification to the client terminal 110. Any method of notification may be used as long as it allows the MFP 100 to notify the client terminal 110 that scanning will continue. For example, a specific folder for receiving notifications from the MFP 100 may be prepared in the client terminal 110. One possible mode of notifying the client terminal 110 that scanning will continue is to send a file named "continue.txt" from the MFP 100 via FTP as a file indicating that scanning will continue. Confirming that scanning will continue by sending a file in this manner is one example, and other mechanisms may be used as long as they can realize notification of scanning continuation between the MFP 100 and the client terminal 110.

[0115] Next, in S1204, the simple scan control unit 409 determines whether the client terminal 110 has received a scan continuation instruction from the MFP 100. More specifically, the simple scan control unit 409 uses the network control unit 407 to check whether the client terminal 110 has received a scan continuation instruction. For example, in the case where the MFP 100 transmits a file indicating that scanning should be continued to the client terminal 110 as described above, when the client terminal 110 receives the scan continuation instruction, the file indicating that scanning should be continued is deleted (see S1305 in FIG. 13 described below). The simple scan control unit 409 checks, via the network control unit 407, a specific folder in the client terminal 110 for receiving notifications from the MFP 100 as described above. If the file indicating that scanning should be continued transmitted in S1203 above does not exist in the folder, the simple scan control unit 409 determines that the client terminal 110 has received a scan continuation instruction from the MFP 100. On the other hand, if the file indicating that scanning should be continued transmitted in S1203 above exists in the folder, the simple scan control unit 409 determines that the client terminal 110 has not received a scan continuation instruction from the MFP 100. Furthermore, instead of deleting the file indicating the instruction to continue at the client terminal, the following method may be used: The file name indicating the instruction to continue is changed at the client terminal 110 to, for example, continue_OK.txt. If the MFP 100 subsequently finds the changed file name, it determines that an instruction to continue scanning has been received and deletes the file. On the other hand, if the MFP 100 does not find the changed file name, it determines that an instruction to continue scanning has not been received.

[0116] Here, if it is determined that the client terminal 110 has received an instruction to continue scanning (Yes in S1204), the simple scan control unit 409 proceeds to S1010, displays the simple scan execution screen again, and waits for the next scan instruction.

[0117] On the other hand, if it is determined that the client terminal 110 has not received the instruction to continue scanning (No in S1204), the simple scan control unit 409 advances the process to S1205.

[0118] In S1205, after notifying the client terminal 110 of the continuation of scanning, the simple scan control unit 409 checks whether a timeout has occurred because it has not been possible to confirm that a continuation of scanning notification has been received from the client terminal 110 within a specified time. If it is determined that the timeout has not occurred (No in S1205), the simple scan control unit 409 returns the process to S1204 and checks again whether the client terminal 110 has received an instruction to continue scanning.

[0119] On the other hand, if it is determined that a timeout has occurred (Yes in S1205), the simple scan control unit 409 advances the process to S1206. In S1206, the simple scan control unit 409 uses the operation control unit 401 to display a scan continuation error screen such as that shown in FIG. 11(b) on the operation unit 102. FIG. 11(b) is an example of the scan continuation error screen. In this case, since the scan could not be continued, the simple scan control unit 409 advances the process to S1023 and performs disconnection processing with the client terminal 110.

[0120] Furthermore, in the above S1202, if it is determined that the end button 1102 has been pressed and scanning is to be ended (No in S1202), the simple scan control unit 409 advances the process to S1207.

[0121] In S1207, the simple scan control unit 409 receives an instruction from the user to end the scan, and therefore uses the network control unit 407 to transmit a scan end instruction to the client terminal 110. Any method may be used for the transmission as long as it allows the MFP 100 to notify the client terminal 110 that the scan has ended. For example, a specific folder for receiving notifications from the MFP 100 may be prepared in the client terminal 110. One possible form of notifying the client terminal 110 that the scan has ended is to transmit a file named, for example, complete.txt, from the MFP 100 via FTP as a file indicating the scan end. Notifying the client terminal 110 of the scan end by transmitting a file is one example, and it is sufficient if the MFP 100 and the client terminal 110 can realize the scan end notification.

[0122] After the processing of S1207 above, the simple scan control unit 409 advances the processing to S1021 and waits for a disconnection instruction from the client terminal 110. Note that, unlike an instruction to continue scanning, in the case of scanning end, a disconnection instruction is sent from the client terminal 110 to the MFP 100, and therefore confirmation that the client terminal 110 has received a scan end notification is omitted.

[0123] Note that, even if a timeout occurs in S1205 (Yes in S1205), a scan end instruction may be sent to the client terminal 110, as in S1207, and the process may proceed to S1021.

[0124] Hereinafter, the processing of the client terminal 110 in the simple scan of the second embodiment will be described with reference to FIGS. 13 is a flowchart showing an example of processing by the client terminal 110 in simple scanning according to the second embodiment (processing to allow scanning to continue after scanning is completed by confirming whether to continue scanning). The processing in FIG. 13 is executed by a function realized by the CPU 301 loading a program stored in the HDD 306 into the DRAM 302 and executing it. This flow starts when the user starts the simple scan app on the client terminal 110 and launches the simple scan app 111. Note that in FIG. 13, the same processes as those in FIG. 9 are assigned the same numbers, and descriptions thereof will be omitted. FIG. 14 is a diagram showing an example of a screen displayed on the client terminal 110 in the second embodiment.

[0125] In the second embodiment, if the client simple scan control unit 505 determines in S909 that electronic data (file) has been sent from the MFP 100 (Yes in S909), the process proceeds to S1301.

[0126] In S1301, the client simple scan control unit 505 checks whether an instruction to continue scanning has been received from the MFP 100. Note that the instruction to continue scanning may be given by any method as long as it allows the MFP 100 to notify the client terminal 110 of the continuation of scanning. For example, as shown in S1203 of FIG. 12 , a specific folder for receiving notifications from the MFP 100 is prepared. Furthermore, it is assumed that the continuation of scanning is notified by sending a file named, for example, continue.txt, from the MFP 100 to the client terminal 110 via FTP in that folder as a file indicating the continuation of scanning. Then, the client simple scan control unit 505, using the client FTP server control unit 504, determines whether an instruction to continue scanning has been received from the MFP 100 based on whether a file indicating the notification to continue scanning exists in the specific folder for receiving notifications from the MFP 100.

[0127] If it is determined that an instruction to continue scanning has been issued (Yes in S1301), the client simple scan control unit 505 advances the process to S1305. In S1305, since an instruction to continue scanning has been issued, the client simple scan control unit 505 performs a receiving process to indicate that an instruction to continue scanning has been received from the MFP 100. For example, as shown in S1203 of FIG. 12, assume that a file named continue.txt has been placed from the MFP 100 as a file indicating that scanning should continue. In order to indicate that the instruction to continue scanning has been received, the continue.txt file is deleted. As shown in S1204 of FIG. 12, the MFP 100 determines that the instruction to continue scanning has been received from the client terminal 110 by confirming that the file (continue.txt) indicating the instruction to continue scanning does not exist.

[0128] After the processing of S1305 above, the client simple scan control unit 505 returns the process to S909 and waits for transmission of the next scan data from the MFP 100. Note that the method of indicating that the instruction to continue scanning has been received is not limited to deletion, and any form of mechanism that can indicate that the instruction to continue scanning has been received between the MFP 100 and the client terminal 110 may be used. For example, the client terminal 110 may change the name of the file to continue_OK.txt, and the MFP 100 may detect the changed file name to notify that the instruction to continue scanning has been received.

[0129] Furthermore, in the above S1301, if it is determined that there is no instruction to continue scanning (No in S1301), the client simple scan control unit 505 advances the process to S1302. In S1302, the client simple scan control unit 505 checks whether an instruction to end scanning has been received from the MFP 100. Any method may be used as long as it allows the MFP 100 to notify the client terminal 110 of the end of scanning. For example, as shown in S1207, a specific folder for receiving notifications from the MFP 100 is prepared. Furthermore, it is assumed that the end of scanning is notified by sending a file named, for example, complete.txt, from the MFP 100 to the client terminal 110 via FTP as a file indicating the end of scanning. Then, the client simple scan control unit 505 uses the client FTP server control unit 504 to determine whether an instruction to end scanning has been received from the MFP 100 based on whether a file indicating the end of scanning is present in the specific folder for receiving notifications from the MFP 100.

[0130] If it is determined that an instruction to end the scan has been issued (Yes in S1301), the client simple scan control unit 505 advances the process to S912, displays a scan completion screen, and ends the simple scan (S913 to S914).

[0131] On the other hand, if it is determined that there is no scan end instruction (No in S1301), the client simple scan control unit 505 advances the process to S1303. In S1303, the client simple scan control unit 505 checks whether a timeout has occurred because it has not been possible to confirm that a scan continuation notification or a scan end notification has been received from the MFP 100 for a specified time (whether a specified time has passed without receiving a scan end notification).

[0132] If it is determined that the timeout has not occurred (No in S1303), the client simple scan control unit 505 returns the process to S1301 and checks again whether the MFP 100 has issued an instruction to continue scanning.

[0133] On the other hand, if it is determined that a timeout has occurred (Yes in S1303), the client simple scan control unit 505 advances the process to S1304. In S1304, the client simple scan control unit 505 uses the client operation control unit 501 to display a client scan continuation error screen as shown in Fig. 14 on the output device of the client terminal 110. Fig. 14 is an example of the client scan continuation error screen. In this case, because it was not possible to confirm that the MFP 100 wants to continue scanning, when the OK button 1401 on the client scan continuation error screen is pressed, the client simple scan control unit 505 advances the process to S912, displays a scan completion screen to present only the portion of the scan that was successfully executed to the user, and ends the simple scan (S913 to S914).

[0134] The above process not only provides the effect of the first embodiment, but also makes it possible to continue scanning after the current scan is completed.

[0135] It goes without saying that the configurations and contents of the various data described above are not limited to those described above, and that the data may be configured in various configurations and contents depending on the application and purpose. Although one embodiment has been described above, the present invention can be embodied as, for example, a system, an apparatus, a method, a program, a storage medium, etc. Specifically, the present invention may be applied to a system made up of multiple devices, or may be applied to an apparatus made up of a single device. Furthermore, the present invention also includes any combination of the above embodiments.

[0136] Other Embodiments 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. Furthermore, the present invention may be applied to a system made up of multiple devices, or to an apparatus made up of a single device. The present invention is not limited to the above-described embodiments, and various modifications (including organic combinations of the embodiments) are possible based on the spirit of the present invention, and these modifications are not excluded from the scope of the present invention. In other words, all configurations that combine the above-described embodiments and their modifications are included in the present invention.

[0137] The disclosure of this embodiment includes the following configuration, method, and program. (Configuration 1) An information processing device, a connection means for establishing a communication connection between the information processing device and an image processing device located in the vicinity of the information processing device; a control unit that enables a function for receiving scan data from the image processing device in accordance with a communication connection with the image processing device; a receiving means for receiving scan data obtained by scanning an original with the image processing device from the image processing device by the function; An information processing device comprising: (Configuration 2) a transmitting means for transmitting information to the image processing device to enable data transmission to the information processing device; 2. The information processing apparatus according to configuration 1, wherein the receiving means receives the scan data transmitted from the image processing apparatus using the information transmitted by the transmitting means. (Configuration 3) The information processing device according to configuration 1, wherein the receiving means receives the scanned data transmitted from the image processing device using predetermined information as information for enabling data transmission to the information processing device. (Configuration 4) The information processing device according to configuration 2 or 3, wherein the control means starts a server for receiving scan data from the image processing device, and sets a user name and password that allows connection to the server as the information for the server. (Configuration 5) 4. The information processing device according to any one of configurations 1 to 3, wherein the connection means directly connects the information processing device and the image processing device via wireless communication. (Configuration 6) 4. The information processing apparatus according to any one of configurations 1 to 3, wherein the control means disables the function and disconnects the communication connection when the scan data is received. (Configuration 7) The information processing device according to any one of configurations 1 to 3, wherein the control means disables the function and disconnects the communication connection when receiving an instruction to end scanning from the image processing device. (Method 1) A control method for an information processing device, comprising: a connecting step of establishing a communication connection between the information processing device and an image processing device located in proximity to the information processing device; a control step of enabling a function for receiving scan data from the image processing device in accordance with a communication connection with the image processing device; a receiving step of receiving scan data obtained by scanning an original with the image processing device from the image processing device by the function; 1. A method for controlling an information processing device, comprising: (Program 1) A program for causing a computer to function as each of the means of the information processing device according to any one of configurations 1 to 3.

Claims

1. An information processing device, a connection means for establishing a communication connection between the information processing device and an image processing device located in the vicinity of the information processing device; a control unit that enables a function for receiving scan data from the image processing device in accordance with a communication connection with the image processing device; a receiving means for receiving scan data obtained by scanning an original with the image processing device from the image processing device by the function; An information processing device comprising:

2. a transmitting means for transmitting information to the image processing device to enable data transmission to the information processing device; 2. The information processing apparatus according to claim 1, wherein the receiving means receives the scan data transmitted from the image processing apparatus using the information transmitted by the transmitting means.

3. 2. The information processing apparatus according to claim 1, wherein the receiving means receives the scanned data transmitted from the image processing apparatus using predetermined information as information for enabling data transmission to the information processing apparatus.

4. 4. The information processing device according to claim 2, wherein the control means starts a server for receiving scanned data from the image processing device, and sets a user name and password that allows connection to the server as the information for the server.

5. 4. The information processing apparatus according to claim 1, wherein the connection means directly connects the information processing apparatus and the image processing apparatus via wireless communication.

6. 4. The information processing apparatus according to claim 1, wherein the control means disables the function and disconnects the communication connection when the scan data is received.

7. 4. The information processing device according to claim 1, wherein the control means disables the function and disconnects the communication connection when an instruction to end scanning is received from the image processing device.

8. A control method for an information processing device, comprising: a connecting step of establishing a communication connection between the information processing device and an image processing device located in proximity to the information processing device; a control step of enabling a function for receiving scan data from the image processing device in accordance with a communication connection with the image processing device; a receiving step of receiving scan data obtained by scanning an original with the image processing device from the image processing device by the function; 1. A method for controlling an information processing device, comprising:

9. A program for causing a computer to function as each of the means of the information processing device according to any one of claims 1 to 3.

Images