scanner

Abstract

To provide a technique capable of reducing erroneous transmission of image data in a scanner capable of push scanning.SOLUTION: An MFP1 is capable of accepting a login operation, accepts, in a log-in state, an instruction to execute a push scan that designates, as a transmission destination PC, a PC3 that has transmitted device information including information indicating a user identical to the logged-in user, scans, in response to accepting the push scan execution instruction, a document placed on a document tray 161 to generate scan data and transmits the generated scan data to the designated PC 3. The MFP1 prohibits a PC 4 that has transmitted device information including information indicating a user different from the logged-in user from being designated as the transmission destination PC.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The technical field disclosed in this specification relates to a scanner capable of push scanning. [Background technology]

[0002] A known function of a scanner is push scanning, which accepts a destination information processing device based on a user's operation on the scanner, scans a document to generate image data, and transmits the image data to the information processing device specified by the user. Patent Document 1, for example, is an example of a document that describes the configuration of push scanning. [Prior art documents] [Patent documents]

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

[0004] When issuing a push scan command, the user must specify the destination information processing device via the scanner's user interface, and there is a risk that the user may accidentally specify another user's information processing device. In this case, the image data resulting from the scan may be sent to the other user's information processing device, resulting in information leakage. [Means for solving the problem]

[0005] The scanner disclosed in this specification is a scanner including a tray, an image reading unit, a user interface, and a communication interface, and the scanner is capable of receiving a push scan instruction specifying a destination information processing device via the user interface, and in response to receiving the push scan instruction, executes a push scan process, and in the push scan process, scans a document placed on the tray using the image reading unit to generate image data, and transmits the generated image data to the destination information processing device via the communication interface, and the scanner is further capable of receiving transmission target information from an information processing device connected via the communication interface, and receives a destination specification for the push scan process from among the information processing devices that have transmitted the transmission target information, and the transmission target information includes the destination information specified by the information processing device that transmitted the transmission target information. The scanner is further configured to be able to accept a login operation via the user interface, and in a state where the scanner is logged in by the login operation, the scanner is capable of accepting the push scan instruction specifying, as a destination information processing device, a first type device that is an information processing device that transmitted the information to be transmitted, the information including the user information that is the same as the login user who is logged in to the scanner, and in response to accepting the push scan instruction that specifies the first type device, in the push scan process, transmit the generated image data to the first type device specified as a destination via the communication interface, and disable a second type device that is an information processing device that transmitted the information to be transmitted, the user information being the same as the login user who is logged in to the scanner, from being specified as a destination information processing device.

[0006] The scanner disclosed in this specification can accept a push scan instruction specifying a destination device. When logged in, the scanner prevents a destination device from being specified as a destination device if a user other than the logged-in user is logged in. This reduces the possibility that scanned data from the logged-in user issuing the push scan instruction will be mistakenly sent to another user's information processing device.

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

[0008] The technology disclosed in this specification realizes a technology that can reduce erroneous transmission of image data in a scanner capable of push scanning. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a block diagram showing a schematic configuration of an MFP according to an embodiment of the present invention. [Figure 2] 10 is a flowchart showing the procedure of a push scan process. [Figure 3] FIG. 10 is an explanatory diagram showing an example of a standby screen. [Figure 4] FIG. 10 is an explanatory diagram showing an example of a device list. [Figure 5] 10 is a flowchart showing the procedure of an instruction receiving process. [Figure 6] 10 is a flowchart showing the procedure of an extraction process. [Figure 7] FIG. 10 is an explanatory diagram showing an example of a selection screen. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, an embodiment of a scanner will be described in detail with reference to the accompanying drawings. This specification discloses a multifunction peripheral (hereinafter referred to as "MFP") capable of performing multiple functions including a scanning function and a communication function.

[0011] As shown in Fig. 1, the MFP 1 of this embodiment includes a controller 10 including a CPU 11 and a memory 12. The MFP 1 also includes a user interface (hereinafter referred to as "user IF") 13, a communication interface (hereinafter referred to as "communication IF") 14, a print engine 15, and a reading unit 16, which are electrically connected to the controller 10. The MFP 1 is an example of a scanner. The reading unit 16 is an example of an image reading unit. Note that the controller 10 in Fig. 1 is a general term for hardware and software used to control the MFP 1, and does not necessarily represent a single piece of hardware actually present in the MFP 1.

[0012] The CPU 11 executes various processes in accordance with programs read from the memory 12 and based on user operations. The memory 12 stores various programs and data, including an operating system (hereinafter referred to as "OS") 21, a print program 22, and a scan program 23. The MFP 1 can also store user information 24, a device list 25, and push settings 26 in the memory 12. Note that the user information 24, device list 25, and push settings 26 may not be stored in the memory 12 when the MFP 1 is shipped from the factory. Details of the programs and data will be described later.

[0013] Memory 12 is also used as a work area when various processes are executed. A buffer provided in CPU 11 is also an example of memory. Examples of memory are not limited to ROM, RAM, HDD, etc. built into MFP 1, but may also be a storage medium that is readable and writable by CPU 11. For example, external memory such as a USB memory or HDD connected to MFP 1 via communication IF 14, or a memory or HDD provided in a device connected to MFP 1 via communication IF 14 are also examples of memory.

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

[0015] The user IF 13 includes hardware for displaying a screen for notifying the user of information and hardware for accepting user operations. The MFP 1 of this embodiment includes a touch panel as the user IF 13, which has a screen display function and an operation acceptance function. Note that the user IF 13 may not include a touch panel and may instead be configured as a combination of a display screen and operation buttons.

[0016] The communication IF 14 includes hardware for communicating with external devices. The communication standards of the communication IF 14 include Ethernet (registered trademark), Wi-Fi (registered trademark), USB, etc. The MFP 1 may be equipped with multiple communication IFs 14 that support multiple communication standards.

[0017] The print engine 15 includes a configuration for printing an image on a print medium such as a sheet. The image formation method of the print engine 15 is, for example, an electrophotographic method or an inkjet method. The reading unit 16 includes a document tray 161 and includes a configuration for reading an image of a document placed on the document tray 161 and generating image data. The document tray 161 is an example of a tray. The document tray 161 includes, for example, a transmission sensor that can output different signals depending on whether a document is placed on it or not. The reading unit 16 may also include an automatic document feeder that includes the document tray 161.

[0018] As shown in FIG. 1, the MFP 1 of this embodiment can be connected to one or more personal computers (hereinafter referred to as "PCs"). In FIG. 1, the MFP 1 is connected to three PCs 3, 4, and 5. A scan application is installed on each PC. Scan application 31 of PC 3, scan application 41 of PC 4, and scan application 51 of PC 5 are all programs that enable the use of the scan function of the MFP 1. Scan applications 31, 41, and 51 may be the same program, or may be partially different programs. PC 3, PC 4, and PC 5 are examples of information processing devices.

[0019] The MFP 1 of this embodiment has a push scan function. With the push scan function, the MFP 1 reads an image of a document placed on document tray 161 using reading unit 16, generates scan data that is image data of the read result, and transmits the generated scan data to a device designated as a destination. A device that can be designated as a destination using the push scan function of the MFP 1 is a device that can communicate with the MFP 1 and that is running a scan application compatible with the MFP 1, such as PCs 3 to 5.

[0020] Next, we will explain the processing for using the push scan function of the MFP 1. Note that the MFP 1 can also accept operations other than those related to the push scan function, and can execute various functions based on the accepted instructions. In this specification, we will only explain the processing of each device related to the push scan function of the MFP 1, and will omit explanations of functions other than the push scan function.

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

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

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

[0024] The procedure for push scan processing in the MFP1 will be described with reference to the flowcharts in Figures 2, 5, and 6. The push scan processing is triggered when the MFP1 is started up, and after various initial operations, is executed by the CPU 11 of the MFP1. Note that the MFP1 has various functions other than the push scan function, such as a print function and a copy function, but the following describes only the procedure related to the push scan function, and descriptions of other functions will be omitted.

[0025] In the push scan process, the CPU 11 initializes the device list 25, which is a list capable of storing information about a plurality of devices (S101). The device information stored in the device list 25 is information about devices that can be selected as destinations for scan data sent using the push scan function.

[0026] The device information is information transmitted from PCs 3 to 5 to MFP 1, for example. Scan application 31 of PC 3 is set to be automatically started when PC 3 is started and to be resident on PC 3. Information about MFP 1 is registered in scan application 31 as the device that will execute scanning. Therefore, PC 3 periodically transmits its own device information to MFP 1, for example, every one to several minutes, based on scan application 31. Similarly, PCs 4 and 5 periodically transmit their own device information to MFP 1 while they are running. MFP 1 can receive device information from each of PCs 3 to 5 without the need for an instruction via user IF 13.

[0027] Specifically, PCs 3 to 5 transmit, as device information, at least information indicating the device name of their own device to MFP 1. Furthermore, when a user is logged in, PCs 3 to 5 can transmit information indicating the user name of the logged-in user. When a user is not logged in, PCs 3 to 5 may transmit information indicating that the user is not logged in, or may transmit device information that does not include information indicating the user name. For example, when a user with the user name "User A" is logged in to PC 3, device information including the device name "PC3" and the user name "User A" is transmitted from PC 3 to MFP 1. Device information is an example of information to be transmitted. A user name is an example of user information.

[0028] Then, the CPU 11 displays a standby screen on the user IF 13 (S102). The standby screen is a screen that includes a plurality of icons and can accept user operations, as shown in Fig. 3, for example. The standby screen 60 includes a plurality of icons including a scan icon 61, and a login button 63 that accepts a user login instruction. The MFP 1 can then accept user operations on the standby screen 60 that is being displayed, for example, operations on the icons and buttons that are being displayed.

[0029] The CPU 11 determines whether or not device information has been received from an external device (S105). If it determines that device information has not been received (S105: NO), the CPU 11 determines whether or not an operation to the user IF 13 has been accepted (S106). If it determines that an operation to the user IF 13 has not been accepted (S106: NO), the CPU 11 waits for reception of device information and an operation to the user IF 13.

[0030] When it is determined that device information has been received from PCs 3 to 5 (S105: YES), the CPU 11 registers the received device information as new destination information in the device list 25 (S111). For example, as shown in Fig. 4, the device list 25 stores a device name 251 and a user name 252 in association with each other for each source of device information.

[0031] For example, when device information is received from a device that is not registered in the device list 25, the CPU 11 adds and registers the device as a new destination in the device list 25 based on the device information. For example, when PC4 is not registered in the device list 25 and device information including the device name "PC4" and the user name "User B" is received from PC4, the CPU 11 registers destination B, whose device name 251 is "PC4" and whose user name 252 is "User B," in the device list 25, as shown in Fig. 4. Furthermore, when information indicating that the user is not logged in is received from PC5, the CPU 11 registers destination C, whose device name 251 is "PC5" and whose user name 252 indicates that the user is not logged in, as shown in Fig. 4.

[0032] Furthermore, for example, when device information is received from a device already registered in the device list 25, the CPU 11 overwrites the device list 25 based on the device information. For example, when PC3 is registered in the device list 25 in association with "User C," and the CPU 11 receives device information from PC3 that includes the device name "PC3" and the user name "User A," the CPU 11 updates the information registered in the device list 25 for destination A, whose device name 251 is "PC3," so that the user name 252 becomes "User A." In other words, when the login user of the source device is changed, the CPU 11 changes the user name 252 to the user name of the new device information. Note that the CPU 11 may, for example, compare the received device information with the information registered in the device list 25 and overwrite the information if it has been updated. Furthermore, when a predetermined time has passed since the last time device information was received, but no new device information has been received from that device, the CPU 11 may delete the information of that device from the device list 25.

[0033] Even if the MFP 1 has not received an instruction to execute a push scan, when it receives device information from a PC or the like, it stores the information in the device list 25. In other words, the MFP 1 stores information about devices to which scan data can be sent, regardless of the instruction received by the MFP 1. Therefore, the MFP 1 can specify the destination device sooner after receiving an instruction to execute a push scan, compared to when the MFP 1 requests device information after receiving an instruction to execute a push scan.

[0034] After S111, the CPU 11 proceeds to S102, displays the standby screen 60, and waits for reception of device information and an operation on the user IF 13. On the other hand, if it is determined that an operation on the user IF 13 has been accepted (S106: YES), the CPU 11 determines whether the accepted operation is an operation indicating a scan instruction, a login operation, or a logout operation (S121).

[0035] When it is determined that a login operation has been accepted (S121: Login), the CPU 11 performs user authentication based on the accepted login information (S122). The login information may be, for example, information entered on an input screen displayed based on the login operation, or information read from an IC card or the like brought close to the MFP 1 as the login operation. Furthermore, when the CPU 11 detects the proximity of an electronic device such as a smartphone instead of an IC card, it may determine that the operation indicates a login and acquire the login information from the electronic device.

[0036] Then, the CPU 11 determines whether or not the user authentication has been successful (S123). The CPU 11 determines whether or not the user who performed the login operation is a user who is permitted to use the MFP 1, for example, based on the user information 24 (see FIG. 1) stored in the memory 12. The MFP 1 may have an external device, such as an authentication server, perform the user authentication instead of performing it itself.

[0037] The MFP 1 can accept registration of users authorized to use the MFP 1, for example, through an administrator's operation, and stores information about each registered user in the user information 24. The MFP 1 can also accept, for example, instructions for setting available functions for each user, and store the accepted setting information in the user information 24. In S123, the CPU 11 determines whether the user is authorized to use the MFP 1, for example, based on whether the accepted login information is information indicating a user registered in the user information 24. The MFP 1 can accept various settings via the user IF 13 when accepting a login to the MFP 1 with administrator privileges, or can accept settings from an external device via an embedded web server function.

[0038] If it is determined that the user authentication was successful (S123: YES), the CPU 11 stores the user name of the user who performed the login operation in the memory 12 as the logged-in user (S124). As a result, the MFP 1 enters a logged-in state. After S124, the CPU 11 proceeds to S102 and displays the standby screen 60. The standby screen 60 displayed in this case includes, for example, information indicating the logged-in user and a logout button instead of the login button 63.

[0039] If it is determined that the user authentication was not successful (S123: NO), the CPU 11 proceeds to S102 and re-displays the standby screen 60. The CPU 11 may display a message indicating that the user authentication has failed, or may re-display the login information input screen.

[0040] Furthermore, if it is determined that a logout operation has been accepted while the user is logged in (S121: Logout), the CPU 11 deletes the user name stored in S124 from the memory 12 (S126). This puts the MFP 1 in a state where the user is not logged in. After S126, the CPU 11 proceeds to S102 and displays the standby screen 60. The standby screen 60 displayed in this case includes a login button 63. Note that the MFP 1 may also log out the user if a predetermined time has passed without accepting any operation while the user is logged in. In this case, the CPU 11 may automatically erase the login user name and display the standby screen 60 including the login button 63.

[0041] On the other hand, if it is determined that an instruction to perform push scanning has been received through an operation on the scan icon 61 on the standby screen 60 (S121: scan instruction), the CPU 11 executes an instruction reception process (S131). The procedure of the instruction reception process will be described with reference to the flowchart in Fig. 5. Note that the MFP 1 may also be able to receive a selection of an instruction to perform push scanning through an operation on a selection screen that is displayed after an operation on the scan icon 61.

[0042] In the instruction reception process, the CPU 11 determines whether or not the user is logged in (S201). As described above, when the CPU 11 receives an operation on the login button 63 and succeeds in user authentication, the CPU 11 enters a logged-in state and stores the username of the logged-in user in the memory 12. The CPU 11 determines, for example, whether or not the username of the logged-in user is stored in the memory 12.

[0043] If it is determined that the logged-in user is logged in (S201: YES), the CPU 11 determines whether the logged-in user is permitted to perform push scanning (S211). The CPU 11 determines whether the logged-in user is permitted to perform push scanning based on the user information 24.

[0044] If it is determined that the user is permitted to perform push scanning (S211: YES), the CPU 11 executes extraction processing (S212). The extraction processing is processing for extracting devices that can be selected as destinations for scan data sent by push scanning. The procedure of the extraction processing will be described with reference to the flowchart in FIG. 6.

[0045] In the extraction process, the CPU 11 first clears destination candidates (S301). The destination candidates are a list of destinations that will be options for accepting user selection in a later procedure. The CPU 11 then determines whether device information that can be a destination is stored in the device list 25 (see FIG. 4) (S302). If it is determined that device information is stored in the device list 25 (S302: YES), the CPU 11 checks the device information registered in the device list 25 one by one.

[0046] If it is determined that no device information is stored in the device list 25 (S302: NO), there is no device that can be selected as a destination, and the CPU 11 cannot extract a device that can be a destination. In this case, the CPU 11 ends the extraction process and returns to the instruction acceptance process. The CPU 11 may, for example, wait a predetermined time until it receives device information from an external device, and then make the determination in S302 again.

[0047] CPU 11 determines whether or not user name 252 of the device information to be checked includes information indicating a specific user (S311). As described above, PCs 3 to 5 transmit device information including a user name indicating a specific user when a user is logged in, but transmit device information including information indicating that the user is not logged in or device information not including a user name when a user is not logged in. In other words, CPU 11 determines whether or not a user is logged in to the device that transmitted the device information to be checked.

[0048] If it is determined that the device information to be checked includes a user name 252 indicating a specific user (S311: YES), the CPU 11 determines whether the user name 252 in the device information and the user name of the login user who is logged in to the MFP1 are information indicating the same user (S312). The user name of the login user who is logged in to the MFP1 is information stored in the memory 12 in S124 of the push scan process (see FIG. 2). For example, the CPU 11 determines that the user name 252 in the device information and the user name of the login user are information indicating the same user if they match. For example, the CPU 11 may determine that the user name 252 in the device information and the user name of the login user are information indicating the same user if they include common elements.

[0049] If it is determined that the user name 252 of the device information to be confirmed and the user name of the logged-in user are information indicating the same user (S312: YES), the CPU 11 decides to include the device indicated by the device name 251 of this device information as a candidate destination (S313).

[0050] Furthermore, if it is determined that the user name 252 of the device information to be confirmed and the user name of the logged-in user are information indicating different users (S312: NO), the CPU 11 decides not to include the device indicated by the device name 251 of this device information as a candidate destination (S314).

[0051] For example, if the user name of the user logged in to MFP1 is "User A" and the device information as shown in Fig. 4 is registered in device list 25, then "Destination A" has user name 252 of "User A" and is the same user as the logged-in user. Meanwhile, in the same situation, "Destination B" has user name 252 of "User B" and is a different user from the logged-in user.

[0052] In this case, if the device information to be confirmed is "destination A," the CPU 11 determines YES in S312 and includes the device indicated by the device name 251 of "destination A," i.e., PC3, in the candidates for destinations. In this case, PC3 is an example of a first-class device.

[0053] If the device information to be confirmed is "destination B," the CPU 11 determines NO in S312 and does not include the device indicated by the device name 251 of "destination B," i.e., PC4, in the candidates for the destination. In this case, PC4 is an example of a second-type device.

[0054] On the other hand, if it is determined that the user name 252 of the device information to be checked is information indicating that the user is not logged in (S311: NO), the CPU 11 determines whether the push setting 26 (see Figure 1) is information indicating "OK" (S321).

[0055] The push setting 26 is information indicating whether or not scan data from a push scan can be sent to a device that is not logged in. For example, the MFP 1 can accept the setting of the push setting 26 by an administrator, and when the MFP 1 accepts a setting that allows sending to a device that is not logged in, information indicating "OK" is stored in the push setting 26. Also, when the MFP 1 accepts a setting that prevents sending to a device that is not logged in, information indicating "NO" is stored in the push setting 26.

[0056] If the CPU 11 determines that the push setting 26 is information indicating "OK" (S321: YES), the CPU 11 decides to include the device indicated by the device information to be confirmed as a candidate for the destination (S313). On the other hand, if the CPU 11 determines that the push setting 26 is information indicating "NO" rather than "OK" (S321: NO), the CPU 11 decides not to include the device indicated by the device information to be confirmed as a candidate for the destination (S322).

[0057] In the example of device list 25 shown in Fig. 4, information indicating that the user is not logged in is stored in user name 252 of "destination C." If push setting 26 is "OK," CPU 11 includes the device indicated by device name 251 of "destination C," i.e., PC5, as a candidate destination; if push setting 26 is "NO," CPU 11 does not include PC5 as a candidate destination. In this case, PC5 is an example of a third-type device.

[0058] After any of S313, S314, and S322, the CPU 11 determines whether all device information registered in the device list 25 has been checked (S331). If it is determined that there is unchecked device information (S331: NO), the CPU 11 proceeds to S311 and performs similar processing on the next device information. If it is determined that all device information registered in the device list 25 has been checked (S331: YES), the CPU 11 ends the extraction process and returns to the instruction acceptance process.

[0059] Returning to the description of the instruction reception process in Fig. 5, the CPU 11 determines whether one or more devices have been extracted as destination candidates by the extraction process of S212 (S213). If it is determined that one or more devices have been extracted (S213: YES), the CPU 11 causes the user IF 13 to display a selection screen that includes the extracted destination candidates in a list and that receives a user selection (S214).

[0060] If the logged-in user is "User A" and the push setting 26 is "OK," the CPU 11 causes the user IF 13 to display a selection screen 71 including PC3 and PC5 as options, as shown in FIG. 7A, for example. The user can select the destination of the scan data from PC3, to which the user is logged in, and PC5, to which no one is logged in. On the other hand, PC4, to which a user other than the logged-in user is logged in, is not displayed as an option on the selection screen 71, and therefore cannot be specified as a destination. The selection screen 71 is an example of a limited selection screen.

[0061] By displaying selection screen 71 that does not include PC4 as an option and accepting the user's selection, it is unlikely that a PC to which another user is logged in will be selected. Furthermore, PC5, to which no one is logged in, may be used by a user logged in to MFP1. By including PC5 as an option, it is possible to avoid the problem of the logged-in user being unable to select the PC to use.

[0062] 7(A) includes device information extracted as candidates as options, and displays a device name 251 and a user name 252 for each option. By displaying the user name, the logged-in user can distinguish between a PC to which the logged-in user is logged in and a PC to which the logged-in user is not logged in and appropriately select a destination device. In other words, it is possible to prevent scan data from being sent erroneously.

[0063] Furthermore, if the logged-in user is "User A" and the push setting 26 is "NO," the CPU 11 causes the user IF 13 to display a selection screen 72 that includes only PC3 as an option, as shown in FIG. 7(B), for example. PC4, to which a user other than the logged-in user is logged in, and PC5, to which no one is logged in, are not displayed as options on the selection screen 72, and therefore cannot be specified as a destination. The user can select only PC3, to which the user is logged in, as a destination for scan data. The selection screen 72 is an example of a limited selection screen. Note that, since the selection screen 72 shown in FIG. 7(B) displays only devices to which the logged-in user is logged in, user name information may not be displayed.

[0064] By displaying selection screen 72 that does not include PC4 or PC5 as options and accepting the user's selection, it is unlikely that a device other than the device to which the logged-in user is logged in will be selected. This reduces erroneous transmissions. Furthermore, because MFP1 can accept push settings 26, for example, an administrator can set whether or not to display devices to which no one is logged in as options. This allows for greater flexibility in push scan operation.

[0065] On the other hand, if it is determined that the MFP 1 is not logged in (S201: NO), the CPU 11 determines whether or not a non-logged-in user is permitted to use the push scan function, based on the user information 24 (S221). If it is determined that the push scan function is permitted (S221: YES), the CPU 11 causes the user IF 13 to display a selection screen 73 that includes all of the device information registered in the device list 25 as options, as shown in FIG. 7(C) (S222). The selection screen 73 displays the device name 251 and user name 252 of each piece of device information. The selection screen 73 is an example of an unrestricted selection screen.

[0066] If the MFP1 is not logged in, it is not possible to identify the user who performed the operation indicating the push scan instruction, and therefore it is not possible to extract destination candidates based on the user name. In this case, by not limiting the options based on the user name 252 in the device list 25 and instead displaying all device information registered in the device list 25 as selectable, the use of the push scan function is not restricted, resulting in improved usability. In particular, by displaying the destination device name 251 and user name 252 on the selection screen 73, the user can recognize PCs logged in by others and then appropriately select the destination device. In other words, it is possible to prevent scan data from being sent erroneously.

[0067] After displaying one of the selection screens 71 to 73, the CPU 11 waits until it receives an operation to select an option included in the selection screen (S231). The operation to select a destination device on the selection screens 71 to 73 that are displayed after performing an operation on the scan icon 61 is an example of a push scan instruction in which a destination device is specified. Note that even if there is only one option, the CPU 11 will receive an operation to select an option. The user can determine the timing to start scanning by selecting a destination after preparing the document to be push scanned.

[0068] When an operation to select an option is accepted (S231: YES), the CPU 11 causes the reading unit 16 to read the document placed on the document tray 161 and generates scan data (S232). Furthermore, the CPU 11 transmits the generated scan data to the destination device selected by the user (S233). Steps S232 and S233 are examples of push scan processing, and the scan data is an example of image data. The destination device receives and saves the scan data.

[0069] If it is determined that the logged-in user is not authorized to perform push scanning (S211: NO), or if no selectable destinations are extracted in the extraction process (S213: NO), or if the user is not logged in and is not authorized to use the push scanning function (S221: NO), the CPU 11 displays an error (S241) and does not perform push scanning. The CPU 11 may also display the reason for the error.

[0070] After S233 or S241, the CPU 11 ends the instruction transmission process and returns to the push scan process of Fig. 2. Then, in the push scan process, upon completion of the instruction transmission process of S131, the CPU 11 proceeds to S102 and displays the standby screen 60.

[0071] As described above in detail, the MFP 1 of this embodiment can accept a selection of a destination for scan data and an instruction to execute a push scan. In this case, the MFP 1 prevents a PC logged in by a user other than the logged-in user who is logged in to the MFP 1 from being specified as a destination for scan data. This reduces the possibility that a logged-in user issuing an instruction to execute a push scan will select a PC logged in by another user as a destination for scan data. In other words, the possibility of scan data being sent by mistake is reduced.

[0072] It should be noted that the present embodiment is merely an example and does not limit the present invention in any way. Therefore, the technology disclosed in this specification can naturally be improved and modified in various ways without departing from the spirit and scope of the present invention. For example, the scanner is not limited to the MFP1, and may be any device that has a scanning function and a communication function, such as a single-function scanner without a printing function, a fax machine, or a copy machine. Furthermore, the destination device to which scanned data is sent from the MFP1 is not limited to a PC, and may be a mobile device such as a smartphone or tablet computer.

[0073] Furthermore, the screens illustrated in each drawing are merely examples, and the display format is not limited to the illustrated examples. For example, the wording of messages and the shapes and arrangements of buttons displayed on each screen are not limited to the illustrated examples.

[0074] Furthermore, in the embodiment, the MFP 1 stores, as user information 24, information indicating whether or not each user can use the scan function. However, the setting of whether or not each user can use the scan function may not be necessary. For example, the MFP 1 may allow all users to use the scan function, regardless of whether or not they are registered. In that case, steps S211 and S221 of the instruction reception process (see FIG. 5) may be omitted. That is, after step S201 of the instruction reception process, the CPU 11 may proceed to step S212 or S222.

[0075] Furthermore, for example, the MFP 1 may be configurable as to whether or not to allow use of the scan function by a user not registered in the user list, or whether or not to allow use of the scan function when login is not accepted.

[0076] Furthermore, in the embodiment, it is determined whether or not to display devices that are not logged in as options based on the push setting 26, but the push setting 26 may not be necessary. That is, the MFP 1 may be configured to display devices that are not logged in as options, or may be configured not to display devices that are not logged in as options.

[0077] Furthermore, in the embodiment, the device name and user name are displayed on the selection screens 71 to 73 (see FIG. 7), but instead of displaying the user name, information indicating whether the user is the same as the logged-in user may be displayed.

[0078] Furthermore, in the embodiment, after accepting an instruction to perform a push scan by operating the scan icon 61, the MFP 1 determines the devices that can be selected as destinations and displays the selection screens 71 to 73. However, the MFP 1 may, for example, determine the devices that can be selected as destinations after accepting login, without accepting an operation on the scan icon 61. In that case, the MFP 1 may display a scan icon for each selectable destination when displaying the standby screen. In that case, an operation on the scan icon also serves as a destination selection operation, and the standby screen on which the scan icon for each destination is displayed is an example of a limited selection screen.

[0079] In the embodiment, each PC transmits device information voluntarily, but the PC may transmit device information upon receiving a request from the MFP 1. In this case, the MFP 1 may periodically request device information from PCs with which it can communicate. Furthermore, if the MFP 1 does not receive a response from a device registered in the device list 25, the MFP 1 may delete the device from the device list 25.

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

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

[0082] 1 MFP 12 Memory 13 User Interface 14 Communication Interface 16 Reading unit 161 Document tray 3, 4, 5 PC

Claims

1. Tray and an image reading unit; A user interface; a communication interface; A scanner comprising: The scanner a push scan instruction specifying a destination information processing device can be received via the user interface; executes a push scan process in response to receiving the push scan instruction, and in the push scan process, scans the document placed on the tray using the image reading unit to generate image data, and transmits the generated image data to an information processing device designated as a destination via the communication interface; The scanner further comprises: The information processing device is capable of receiving transmission target information from an information processing device connected via the communication interface, and accepts designation of a transmission destination by the push scan process from among the information processing devices that have transmitted the transmission target information, and the transmission target information may include user information indicating a user who is logged in to the information processing device that has transmitted the transmission target information; The scanner further comprises: A login operation can be accepted via the user interface; When you are logged in by the login operation, a first type device, which is an information processing device that has transmitted the transmission target information including the user information that indicates the same user as the login user who is logged in to the scanner, is made capable of receiving the push scan instruction, which specifies the first type device as a transmission destination information processing device; and in response to receiving the push scan instruction specifying the first type device, in the push scan process, transmitting the generated image data to the first type device specified as a transmission destination via the communication interface; a second type device that is an information processing device that has transmitted the transmission target information including the user information indicating a user different from the login user who is logged in to the scanner cannot be designated as a destination information processing device; A scanner configured to:

2. 2. The scanner according to claim 1, It has memory, The scanner storing the transmission target information in the memory in response to receiving the transmission target information from the information processing device connected via the communication interface without requiring the push scan instruction via the user interface; The scanner further comprises: When the transmission target information is stored in the memory and the user has logged in by the login operation, the first type device is made capable of receiving the push scan instruction specifying the first type device as a destination information processing device, and in response to receiving the push scan instruction specifying the first type device, in the push scan processing, the generated image data is transmitted to the first type device specified as a destination via the communication interface; The second type device cannot be designated as a destination information processing device. A scanner configured to:

3. 3. The scanner according to claim 2, The scanner the information processing device is capable of receiving the transmission target information from each of the plurality of information processing devices connected via the communication interface without the need for the push scan instruction via the user interface, and stores the received transmission target information in the memory every time the information processing device receives the transmission target information; The scanner further comprises: In a state where a plurality of pieces of transmission target information are stored in the memory and the user has logged in by the login operation, displaying a limited selection screen on the user interface, the limited selection screen including the first type device as an option and not including the second type device as an option, and accepting a designation of the information processing device as a destination in the push scan instruction by selection from the limited selection screen; In response to receiving the push scan instruction in which the first type device is designated by selection from the limited selection screen, the push scan process transmits the generated image data to the first type device designated as a destination via the communication interface. A scanner configured to:

4. 4. The scanner according to claim 3, The scanner In a state where a plurality of pieces of transmission target information are stored in the memory and the user has logged in by the login operation, displaying, on the user interface, the limited selection screen in which options are limited by the user information included in the transmission target information so that the first type device is included as an option and the second type device is not included as an option, and accepting designation of the information processing device as a transmission destination in the push scan instruction by selection from the limited selection screen; in response to receiving the push scan instruction in which the first type device is designated by selection on the limited selection screen, the push scan process transmits the generated image data to the first type device designated as a destination by selection on the limited selection screen via the communication interface; When a plurality of pieces of transmission target information are stored in the memory and the user is not logged in, displaying, on the user interface, an unrestricted selection screen in which the information processing device that transmitted the information to be transmitted stored in the memory is set as an option and the options are not limited by the user information included in the information to be transmitted, and accepting designation of the information processing device as a transmission destination in the push scan instruction by selection from the unrestricted selection screen; In response to receiving the push scan instruction in which a destination information processing device is designated by selection from the unrestricted selection screen, the push scan process transmits the generated image data to the information processing device designated as the destination by selection from the unrestricted selection screen via the communication interface. A scanner configured to:

5. 4. The scanner according to claim 3, the transmission target information received from each of the plurality of information processing devices connected via the communication interface without the need for the push scan instruction via the user interface may include the user information indicating a user logged in to the information processing device that transmitted the transmission target information, or may not include the user information; The scanner In a state where a plurality of pieces of transmission target information are stored in the memory and the user has logged in by the login operation, displaying, on the user interface, the limited selection screen that includes the first type device as an option, does not include the second type device as an option, and does not include, as an option, a third type device that is an information processing device that has transmitted the transmission target information that does not include the user information; and accepting designation of the information processing device as a transmission destination in the push scan instruction by selection from the limited selection screen; In response to receiving the push scan instruction in which the first type device is designated by selection from the limited selection screen, the push scan process transmits the generated image data to the first type device designated as a destination via the communication interface. A scanner configured to:

6. 4. The scanner according to claim 3, the transmission target information received from each of the plurality of information processing devices connected via the communication interface without the need for the push scan instruction via the user interface may include the user information indicating a user logged in to the information processing device that transmitted the transmission target information, or may not include the user information; The scanner In a state where a plurality of pieces of transmission target information are stored in the memory and the user has logged in by the login operation, displaying, on the user interface, the limited selection screen, which includes the first type device as an option, does not include the second type device as an option, and further includes, as an option, a third type device that is an information processing device that has transmitted the transmission target information that does not include the user information; and accepting designation of the information processing device as a transmission destination in the push scan instruction by selection from the limited selection screen; In response to receiving the push scan instruction in which the first type device or the third type device is designated by selection on the limited selection screen, the push scan process transmits the generated image data to the first type device or the third type device designated as a destination via the communication interface. A scanner configured to:

7. 7. The scanner according to claim 6, The scanner In a state where a plurality of pieces of transmission target information are stored in the memory and the user has logged in by the login operation, displaying, on the user interface, the limited selection screen, which includes the first type device as an option, does not include the second type device as an option, and further includes the third type device as an option, and the options of the first type device are displayed in association with the user information included in the information to be transmitted, and accepting designation of the information processing device as a transmission destination in the push scan instruction by selection from the limited selection screen; In response to receiving the push scan instruction in which the first type device or the third type device is designated by selection on the limited selection screen, the push scan process transmits the generated image data to the first type device or the third type device designated as a destination via the communication interface. A scanner configured to:

8. 4. The scanner according to claim 3, the transmission target information received from each of the plurality of information processing devices connected via the communication interface without the need for the push scan instruction via the user interface may include the user information indicating a user logged in to the information processing device that transmitted the transmission target information, or may not include the user information; The scanner It is possible to set whether or not a third-type device, which is an information processing device that has transmitted the transmission target information that does not include the user information, can be designated as a transmission destination information processing device; The scanner further comprises: In a state where a plurality of pieces of transmission target information are stored in the memory and the user has logged in by the login operation, displaying, on the user interface, the limited selection screen that includes the first type device as an option, does not include the second type device as an option, and further includes the third type device as an option if a setting is made to enable designation as a destination information processing device, but does not include it as an option if a setting is made to enable designation as a destination information processing device, and accepting designation of the destination information processing device in the push scan instruction by selection from the limited selection screen; In response to receiving the push scan instruction in which the first type device or the third type device is designated by selection on the limited selection screen, the push scan process transmits the generated image data to the first type device or the third type device designated as a destination via the communication interface. A scanner configured to:

9. 4. The scanner according to claim 3, The scanner A standby screen including an icon corresponding to push scanning can be displayed on the user interface; When a plurality of pieces of transmission target information are stored in the memory and the user has logged in through the login operation, and an operation on the icon is accepted, displaying the limited selection screen on the user interface, and accepting a designation of a destination information processing device in the push scan instruction by selection from the limited selection screen; In response to receiving the push scan instruction in which the first type device is designated by selection from the limited selection screen, the push scan process transmits the generated image data to the first type device designated as a destination via the communication interface. A scanner configured to:

Images