Reader

Abstract

The objective is to provide a reader device that improves usability in authentication associated with pull scanning. [Solution] When the MFP10 controller 11 receives a pull scan execution instruction (S4:YES), if a main unit password is set (S52:YES), and if the external device password PWB included in the pull scan execution instruction corresponds to the main unit password (S62:YES), it executes the pull scan (S37:YES, S40). If they do not correspond (S62:NO), it restricts the pull scan (S37:NO, S41). Also, when the controller 11 receives a pull scan execution instruction, if a main unit password is not set (S52:NO), it does not require a correspondence between the external device password and the main unit password (S54) and executes the pull scan (S33:NO, S40).

Description

Technical Field

[0001] The present invention relates to a reading device that reads a document by a scanner.

Background Art

[0002] Patent Document 1 describes a reading device capable of executing a pull scan for causing a scanner to read a document according to an execution instruction from an external device. The reading device of Patent Document 1 performs authentication using a user ID and a password included in the execution instruction of the pull scan of the external device. When the authentication is successful, the reading device executes a pull scan to generate scan data and transmits the generated scan data to the external device.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the reading device of Patent Document 1, there is room for improvement in the method of authentication associated with the execution of the pull scan.

[0005] In view of the above problems, an object of the present invention is to provide a reading device capable of improving user usability in authentication associated with the execution of a pull scan.

Means for Solving the Problems

[0006] To solve the above problems, the reading device disclosed in this embodiment comprises a user interface, a scanner, and a controller, wherein the controller is capable of performing a push scan, which causes the scanner to read a document in response to an execution instruction corresponding to an operation on the user interface, and a pull scan, which causes the scanner to read a document in response to an execution instruction from an external device, the controller is capable of setting a main unit password to be used for the pull scan via the user interface, and when the controller receives an execution instruction for the pull scan from an external device, if the main unit password is set, the controller is capable of performing the pull scan if the external device password included in the execution instruction for the pull scan corresponds to the main unit password, and restricting the pull scan if the external device password does not correspond to the main unit password, and the controller is configured to perform the pull scan when the controller receives an execution instruction for the pull scan from an external device, if the main unit password is not set, without requiring a correspondence between the external device password and the main unit password.

[0007] In the above configuration, users performing pull scans from external devices can set a password on the main unit, thereby requiring authentication to perform pull scans. This restricts other users from performing pull scans. Furthermore, if a user performing a pull scan from an external device determines that authentication is unnecessary, they can send a pull scan command with the main unit password unset, allowing the pull scan to be performed without password authentication. Therefore, even users who are not administrators of the reader but can set the main unit password can switch between requiring and not requiring authentication for pull scans. This improves usability in the authentication process associated with performing pull scans. [Effects of the Invention]

[0008] According to the present invention, usability can be improved in authentication associated with pull scanning. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram showing the configuration of the MFP according to the first embodiment. [Figure 2] This flowchart shows the scan control process performed by the controller of the MFP according to the first embodiment. [Figure 3] This flowchart shows the process executed in S3 in Figure 2. [Figure 4] This is a flowchart showing the process executed in S5 of Figure 2. [Figure 5] This is a flowchart showing the process executed in S22 of Figure 4. [Figure 6] This is a flowchart showing the process executed in step S23 of Figure 4. [Figure 7] This is a flowchart showing the process executed in step S32 of Figure 6. [Figure 8] This is a flowchart showing the process executed in S36 of Figure 6. [Figure 9] This is a flowchart showing the process executed in step S43 of Figure 6. [Figure 10] This diagram shows the screen transitions displayed in the user interface, from the standby screen to the screen where the device password is set. [Figure 11] This flowchart shows the scan control process performed by the controller of the MFP according to the second embodiment, and is a flowchart of the process performed at S32 in Figure 6. [Figure 12] This flowchart shows the scan control process performed by the controller of the MFP according to the second embodiment, and is a flowchart of the process performed in S36 of Figure 6. [Figure 13] Figure 12 is a flowchart showing the process executed in S88. [Figure 14] This diagram illustrates the state in which a user password is set. [Modes for carrying out the invention]

[0010] (First Embodiment) A first embodiment of the reading device will be described using an MFP (Multi Function Peripheral). As shown in Figure 1, the MFP 10 includes a controller 11, memory 12, printer 13, FAXIF 14, scanner 15, user IF 16, USBIF 17, and communication IF 18. These components are connected to each other via bus 1 so as to be able to communicate with one another.

[0011] The printer 13 prints images onto a recording medium such as a sheet or a disc. The sheet can be, for example, paper or an OHP sheet. The printer 13 can employ an inkjet method or an electrophotographic method for printing. The scanner 15 has a reading sensor, such as a CCD or CIS, and generates image data corresponding to the reading of the original document.

[0012] User IF16 is an interface that can accept various operations on the MFP10. User IF16 includes a touch panel with an LCD display and various operation keys. USBIF17 allows for the detachable connection of storage media compliant with the USB standard, and enables data reading and writing via communication compliant with the USB standard. Storage media compliant with the USB standard include, for example, USB memory sticks. The MFP10 is connected to a network via Communication IF18 and communicates with the PC40 via the network according to a predetermined protocol (such as TCP / IP). Communication IF18 can be a wired LAN interface, a wireless LAN interface, or the like.

[0013] The controller 11 is a processing device including, for example, a CPU or the like. The memory 12 is composed of a combination of a volatile memory such as a RAM, a non-volatile memory such as an NVRAM, a ROM, and the like. As the non-volatile memory, an SSD, an HDD, or the like may be used. A buffer included in the controller 11 used when executing various programs may also be regarded as a part of the memory 12. Incidentally, the memory 12 may be a storage medium readable by the controller 11. A storage medium readable by the controller 11 is a non-transitory medium. Non-transitory media include, in addition to the above examples, recording media such as CD-ROMs and DVD-ROMs. Also, non-transitory media are tangible media. On the other hand, an electrical signal that conveys a program downloaded from a server on the Internet or the like is a computer-readable signal medium, which is a type of computer-readable medium, but is not included in non-transitory computer-readable storage media.

[0014] Stored in the memory 12 as a program executable by the controller 11 is a control program 2. The control program 2 is, for example, firmware that comprehensively controls each part of the MFP 10. The controller 11 controls each device connected to the bus 1 by executing the control program 2. In the present embodiment, mainly, the processing of the controller 11 according to the instructions described in the program is shown. That is, the processing such as "judgment", "specification", "confirmation", "acquisition", "restriction", etc. in the following description represents the processing of the controller 11. Incidentally, "acquisition" is used as a concept that does not require a request. That is, the process of the controller 11 receiving data without requesting it is also included in the concept of "the controller 11 acquires data". Also, the "data" in this specification is represented by a bit string readable by the controller 11. And data having substantially the same meaning content but different formats shall be treated as the same data. The same applies to the "information" in this specification.

[0015] In addition, the controller 11 stores various setting values in the memory 12 and uses them. Storing the setting values in the memory 12 may also be described as, for convenience, setting them, etc. That the setting values are stored in the memory 12 may also be described as, for convenience, being set, being a setting, being in a set state, etc.

[0016] Next, the configuration of the PC 40 will be described. The PC 40 includes a communication IF (not shown), a memory, a controller, a display, and a user IF. An OS or the like is stored in the memory of the PC 40. The PC 40 is an example of an external device in this specification. Note that the external device is not limited to the PC 40, and other devices that can transmit an execution instruction for pulse scanning, which will be described later, to the MFP 10, such as mobile terminals like smartphones and tablets, may also be used.

[0017] Next, the procedure of the process executed by the controller 11 when the user uses the "scan" function of the MFP 10 will be described. The MFP 10 can execute "push scan" and "pull scan" as the "scan" function. The controller 11 generates scan data using the image data output by the scanner 15 reading a document. Scan data is also a type of image data. "Push scan" generates scan data by causing the scanner 15 to read a document in response to an execution instruction according to an operation on the user IF 16, and outputs the generated scan data to an output destination according to the execution instruction. For example, it transmits the scan data, which is a scan. The output destination of the data by push scan can be specified as the PC 40, a device connected to the MFP 10, for example, a device connected via the USB IF 17 or the communication IF 18. "Pull scan" is a scan that generates scan data by causing the scanner 15 to read a document in response to an execution instruction transmitted from an external device according to an operation on the external device, and transmits the generated scan data to the device that is the source of the execution instruction. In this embodiment, the external device is the PC 40.

[0018] Controller 11 starts the scan control process shown in Figure 2, for example, after the MFP 10 is powered on and the control program 2 is executed to start the system. Note that the conditions for starting the process in Figure 2 are not limited to the conditions for starting the system. For example, Controller 11 may start the process in Figure 2 when it returns from a power-saving mode that reduces power consumption.

[0019] In this embodiment, the MFP10 uses a total of three authentication passwords for performing a pull scan: two authentication passwords set on the MFP10 side and one authentication password set on the PC40 side. For convenience of explanation, the two authentication passwords set on the MFP10 side, i.e., the main unit side (hereinafter sometimes referred to as the main unit side passwords), will be described as the one-time password PWA1 and the retained password PWA2, respectively. The authentication password set on the PC40 side will be described as the external device side password PWB. When performing a pull scan, the MFP10 performs authentication (hereinafter sometimes referred to as password authentication) based on the correspondence between the main unit side password and the external device side password PWB.

[0020] The one-time password PWA1 is an authentication password set by user IF16, and is a device-side password that is deleted from MFP10 once password authentication is successful. The retained password PWA2 is an authentication password set by user IF16, and once set, is a device-side password that is set and retained in MFP10 unless deleted by user operation. The external device-side password PWB is a password set by PC40, and is sent from PC40 to MFP10 in response to password authentication for pull scan, and is an authentication password used for password authentication. For example, the one-time password PWA1, retained password PWA2, and external device-side password PWB can be strings that combine letters and numbers. The one-time password PWA1 is an example of a first-type device-side password in this specification. The retained password PWA2 is an example of a second-type device-side password. Note that the first and second-type device-side passwords are not limited to passwords of the above-described nature. For example, the first-type device-side password may be a password that is used less frequently or for a shorter period than the second-type device-side password. Specifically, the controller 11 may be configured to delete the first type of main unit password after it has been used a few times or for several days, and delete the second type of main unit password after it has been used dozens of times or for several months.

[0021] Figure 10 shows the screens displayed on the user interface 16, illustrating the screen transitions from the standby screen to the screen for setting the device password. As shown in the upper left of Figure 10, the controller 11 displays icons 51A to 51D on the standby screen 50 that perform various functions such as faxing, copying, scanning, and printing. The controller 11 executes each function when each of the icons 51A to 51D is touched. For example, when the icon 51A representing faxing is touched, the controller 11 displays a screen on the user interface 16 for executing the fax function. Note that the screen display shown in Figure 10 is just one example.

[0022] Furthermore, the controller 11 displays an icon 51E on the standby screen 50 for performing various settings. When the icon 51E is touched, the controller 11 displays the settings selection screen 53 shown in Figure 10 on the user interface 16. On the settings selection screen 53, the controller 11 displays selection fields 54A to 54E for selecting various settings such as general settings, shortcut settings, scan settings, fax settings, and print settings.

[0023] When the selection field 54C for performing scan settings is touched, the controller 11 displays the Scan settings screen 55. On the Scan settings screen 55, the controller 11 displays the selection field 56A for performing pull scan settings, the selection field 56B for performing push scan settings, etc. When the selection field 56A for performing pull scan settings is touched, the controller 11 displays the PullScan settings screen 57. When the selection field 58A for setting a password, one of the multiple selection fields displayed on the PullScan settings screen 57, is touched, the controller 11 displays the password setting screen 59.

[0024] Controller 11 displays a selection field 61A for setting the main unit password and a selection field 61B for selecting the type of main unit password to set on the password setting screen 59. When selection field 61B is touched, Controller 11 displays the type selection screen 62. On the type selection screen 62, Controller 11 displays a selection field 63A for selecting retained password PWA2 and a selection field 63B for selecting one-time password PWA1 as the type of main unit password to set. When selection field 63A is touched, Controller 11 processes the already set main unit password, or the main unit password to be set after selection, as retained password PWA2. Also, when selection field 63B is touched, Controller 11 processes the already set main unit password, or the main unit password to be set after selection, as one-time password PWA1. When either selection field 63A or selection field 63B is touched on the type selection screen 62, Controller 11 displays the standby screen 50 on the user interface 16.

[0025] Furthermore, when the selection field 61A is touched on the password setting screen 59, the controller 11 displays the password input screen 65. On the password input screen 65, the controller 11 accepts the input of the main unit password via the input key 66A and displays the accepted main unit password in the password display field 66B. When the OK button 66C is touched, the controller 11 stores the entered main unit password in the memory 12 as the main unit password of the type selected on the type selection screen 62 and displays the standby screen 50.

[0026] Furthermore, when the controller 11 displays the password input screen 65, if a previously set main unit password is stored in the memory 12, it displays the set password in the password display field 66B in a way that makes it unreadable, such as by displaying an asterisk. When the delete button 66D on the password input screen 65 is touched, the controller 11 deletes the previously set main unit password displayed in the password display field 66B and accepts input of a new main unit password.

[0027] Furthermore, when the delete button 66D is touched and the main unit password in the password display field 66B is deleted, the controller 11 deletes the set main unit password from memory 12. The MFP 10 then has no main unit password set. Note that the screen transitions shown in Figure 10 are just examples. For example, the controller 11 may display the password setting screen 59 when the selection field 63A or selection field 63B is touched on the type selection screen 62. Also, the method for setting the main unit password is not limited to using the user interface 16. For example, the MFP 10 may function as a web server, and the main unit password may be set by accessing the web page of that web server from the PC 40. Alternatively, the main unit password entered via the web page may be registered as a retained password PWA2, and the main unit password entered via the user interface 16 may be registered as a one-time password PWA1. Alternatively, the device-side password entered via the web page may be registered as a retained password PWA2, and the device-side password entered via the user interface 16 may be registered as either a one-time password PWA1 or a retained password PWA2, depending on the user's actions via the user interface 16, such as actions on the type selection screen 62.

[0028] As shown in Figure 2, in step 1, the controller 11 displays a standby screen 50 to the user interface 16. Hereafter, steps will be referred to as "S". After displaying the standby screen 50, the controller 11 determines whether or not it has received an input from the user interface 16 to set the main unit password using the operation shown in Figure 10 (S2). If the controller 11 has received an input from the user interface 16 to set the main unit password (S2: YES), it executes the main unit password setting process in S3; otherwise (S2: NO), it executes S4.

[0029] For example, in the initial state, the MFP10 has no main-side password set, that is, neither the one-time password PWA1 nor the retained password PWA2 is stored in memory 12. The controller 11 makes a positive judgment in S2 (S2:YES) if, for example, the main-side password is set from the state where the main-side password is not set by an operation as shown in Figure 10, that is, an operation including entering the main-side password in the password display field 66B on the password input screen 65. The controller 11 also makes a positive judgment in S2 (S2:YES) if, for example, the set main-side password is changed by an operation including password input via the password input screen 65, or if the type of main-side password is changed by selecting selection field 63A or 63B via the type selection screen 62.

[0030] Furthermore, if the controller 11 has not performed the operation to set the main unit password after displaying the standby screen 50, it will make a negative judgment in S2 (S2: NO). The case where the operation to set the main unit password has not been performed includes cases where the screen shown in Figure 10 was operated, but the OK button 66C or the selection fields 63A and 63B on the type selection screen 62 were not operated, and the main unit password or type was not changed.

[0031] As shown in Figure 3, when the controller 11 starts processing S3, it stores the device-side password set in the operation shown in Figure 10 in memory 12 (S11). The controller 11 stores the one-time password PWA1 in volatile memory, for example RAM, and the retained password PWA2 in non-volatile memory, for example NVRAM. Next, the controller 11 determines whether the set device-side password is the one-time password PWA1 or not (S12). If the controller 11 is the one-time password PWA1 (S12: YES), it sets the password type flag, which is stored in memory 12 and indicates whether the set device-side password is the one-time password PWA1, to a value indicating that the one-time password PWA1 is set (S13), and terminates the processing shown in Figure 3. On the other hand, if the set device-side password is not the one-time password PWA1, i.e., the retained password PWA2 (S12: NO), the controller 11 sets the password type flag to a value indicating that the retained password PWA2 is set (S14).

[0032] As shown in Figure 2, when the controller 11 executes the process in S3, it executes S4. In S4, the controller 11 determines whether or not it has received a scan execution instruction. The controller 11 continues to execute the processes from S1 until it determines that it has received a push scan or pull scan execution instruction (S4: NO), and if it determines that it has received the instruction (S4: YES), it executes the scan request process in S5.

[0033] As shown in Figure 4, in S21, the controller 11 determines whether or not it has received an instruction to execute a push scan. Specifically, if the controller 11 receives an execution instruction to start the "scan" function through an operation on the user IF16 of the MFP 10, it determines that it has received an instruction to execute a push scan (S21: YES) and executes the push scan request processing in S22. For example, in response to receiving an operation on the user IF16, the controller 11 sends a push scan request to an external device (PC40 in this example). The external device that receives the request replies to the MFP 10 with an execution instruction to execute "scan". When the controller 11 receives this reply, it determines that it has received an instruction to execute a push scan. Also, if the controller 11 has performed an operation to start a scan on the external device and has received an execution instruction sent from the external device, it determines that it has received an instruction to execute a pull scan (S21: NO) and executes the pull scan request processing in S23.

[0034] Furthermore, the "Scan" execution command may include information indicating whether it is an execution command in response to an operation received by the user IF16 or an execution command in response to an operation on an external device. The controller 11 may determine whether it is an execution command for a push scan or a pull scan based on that information. Alternatively, the controller 11 may, upon receiving an operation from the user IF16, determine that it has received an execution command for a push scan without sending a request to the external device and execute S22.

[0035] First, we will explain the process that the controller 11 executes when it receives a push scan execution command. As shown in Figure 5, when the controller 11 starts processing S22, it executes the push scan execution command received in S4 (S28). The controller 11 instructs the scanner 15 to start scanning so that it can read the document placed on the document glass. In other words, in the case of a push scan, the controller 11 executes the process without requesting password authentication, regardless of whether a password has been set on the main unit side, and finishes the processes in Figures 4 and 5. As shown in Figure 2, when the controller 11 executes S5, it executes the process from S1 again.

[0036] Next, we will explain the process that the controller 11 executes when it receives a pull scan execution instruction from the PC 40. First, we will explain the process when a one-time password PWA1 is set. As shown in Figure 6, when the controller 11 starts the process in S23, it determines whether the execution of the pull scan is enabled or disabled in the MFP 10 (S31). For example, the controller 11 makes this determination based on the information stored in memory 12 that indicates whether the pull scan is enabled or disabled. In this example, assuming that the pull scan is enabled (S31: YES), the controller 11 executes the password authentication requirement determination process in S32. Through this password authentication requirement determination process, the controller 11 determines whether or not password authentication is required for the pull scan execution instruction. Note that if the pull scan is disabled in the MFP 10 (S31: NO), the controller 11 notifies the PC 40 that the pull scan cannot be executed (S41). In other words, if pull scanning is disabled in the MFP10, pull scanning will not be performed regardless of whether a password is set on the MFP10 itself.

[0037] As shown in Figure 7, when the controller 11 starts processing in S32, it checks whether a device-side password is set (S51) and determines whether a device-side password has been set or not (S52). For example, if a one-time password PWA1 or a retained password PWA2 is stored in memory 12, the controller 11 makes an affirmative decision in S52 (S52: YES). In this example, since a one-time password PWA1 is set (S52: YES), the controller 11 executes S53. In S53, the controller 11 sets that password authentication is required for the pull scan execution instruction. For example, the controller 11 sets a value indicating that password authentication is required in the necessity determination flag stored in memory 12, which indicates whether or not password authentication is required.

[0038] Controller 11 executes S33 in Figure 6, and since the necessity judgment flag is set to a value indicating that password authentication is required, i.e., password authentication is required (S33: YES), in S34, it communicates with PC 40 to request the external device password PWB required for password authentication. When PC 40 receives the request for the external device password PWB from MFP 10, it sets the login password used by the user operating PC 40 to log in to PC 40 as the external device password PWB and sends response data including the external device password PWB to MFP 10. Alternatively, PC 40 may include the password set in the printer driver as the external device password PWB in the response data and send it. Furthermore, after receiving the request for password authentication information, PC 40 may receive the external device password PWB from the user and include it in the response data and send it.

[0039] The pull scan execution instruction received in S4 in Figure 2 is an example of the first instruction in this specification. The response data received in S34 in Figure 6 is an example of the second instruction. In the above explanation, the external device password PWB was included in the second instruction, which is different from the first instruction, but this is not limited to this. The external device password PWB may also be included in the first instruction. That is, the pull scan execution instruction that is first transmitted to the MFP10 and received in S1 may include the external device password PWB. The controller 11 may then execute the processes in S35 and S36 described later based on the external device password PWB included in the first instruction received in S4. In this case, it is not necessary to request the external device password PWB in S34, but communication related to the transmission and reception of scan data will still occur between the MFP10 and the PC40 even after the first instruction has been exchanged. The instructions in this communication are an example of the second instruction. Even when a retained password PWA2 is set, the controller 11 may similarly perform the processes in S35 and S36 based on the external device password PWB included in the first instruction.

[0040] After executing S34, the controller 11 determines whether or not it has received the external device password PWB from the PC 40 (S35). If the PC 40 does not send the external device password PWB in response to the user authentication information request from the MFP 10, the password authentication process in S36, described later, cannot be performed. Therefore, if the controller 11 does not receive the external device password PWB from the PC 40 (S35: NO), it notifies the PC 40 in S41 that it cannot perform a pull scan.

[0041] Here, assuming that the controller 11 has received the external device password PWB from the PC 40 (S35:YES), it executes the password authentication process in S36. As shown in Figure 8, when the controller 11 starts processing in S36, it determines whether the configured main unit password matches the external device password PWB received in S34 (S61). In this example, since the one-time password PWA1 is set as the main unit password, the controller 11 determines in S61 whether the one-time password PWA1 matches the external device password PWB.

[0042] If the controller 11 finds that the one-time password PWA1 and the external device password PWB match (S62:YES), it executes S63 and sets the password authentication to be successful. For example, the controller 11 sets the authentication completion flag, which is stored in memory 12 and indicates whether or not password authentication was successful, to a value indicating success (true). If the passwords do not match in S62 (S62:NO), the controller 11 sets the authentication completion flag to a value indicating that password authentication failed (false) (S64). If the value indicating that password authentication failed (false) is set, the controller 11 determines in S37 of Figure 6 that user authentication has failed (S37:NO) and executes S41.

[0043] In S61, the condition for determining that the main unit password and the external device password PWB included in the pull scan execution instruction match is that the passwords match exactly. However, in this specification, "corresponding passwords" does not necessarily mean that the passwords match exactly. For example, it is acceptable to determine that passwords match if only a part of the password matches. It is also acceptable to determine that passwords match if they indicate information that substantially represents the same user, rather than just matching passwords. For example, if one of two authentication passwords is a password and the other is a password ID that indicates that password, it is acceptable to determine that the passwords match. Furthermore, if the authentication information includes information indicating the group to which the user belongs, it is acceptable to determine that the passwords match if they are the passwords of users in the same group. The same applies to the conditions for determining password correspondence in S93, S98, and S101 shown in Figure 13 of the second embodiment described later. In addition, the controller 11 may perform authentication using a user ID or the like in addition to the password.

[0044] Furthermore, in this embodiment, the restriction on the "Scan" function is to not perform the scan process. Alternatively, the restriction on the "Scan" function could be to reduce the quality of the scan performed. Alternatively, the restriction on the "Scan" function could be to require an additional special permission operation by an administrator to perform the scan.

[0045] In this example, the controller 11 determines in S37 of Figure 6 that the passwords match (S37: YES) and instructs the scanner 15 to start scanning, similar to S28 (S40). That is, if a password is set on the main unit side, the controller 11 performs a pull scan on the condition that the main unit side password and the external device side password PWB match. After executing S40 or S41, the controller 11 performs the password post-processing in S43.

[0046] As shown in Figure 9, the controller 11 checks the type of password set on the main unit (S71) and determines whether the set type of password is a one-time password PWA1 (S72). In this example, a one-time password PWA1 is set as the password on the main unit (S72: YES), so the controller 11 deletes the information about the one-time password PWA1 stored in memory 12 (S73). Then, the controller 11 finishes the processes shown in Figures 4 to 9 and executes the process from S1 in Figure 2 again.

[0047] Furthermore, in S73, the controller 11 deletes the one-time password PWA1 as a process to invalidate it when it receives an instruction to perform a pull scan for the next time or later. However, invalidating it in this specification is not limited to the method of deletion. For example, the controller 11 may store the one-time password PWA1 in memory 12 but render it unusable, or it may retain it as a past history.

[0048] Furthermore, if controller 11 executes S41 with one-time password PWA1 configured, specifically if the pull scan setting is disabled (S31: NO), if the external device password PWB could not be obtained (S35: NO), or if password authentication fails (S37: NO), controller 11 deletes the one-time password PWA1 stored in memory 12 (S43). For this reason, when controller 11 receives a command to execute a pull scan with one-time password PWA1 configured, it disables the configured one-time password PWA1 regardless of whether authentication by one-time password PWA1 is performed or whether a pull scan is performed. Note that controller 11 does not need to disable one-time password PWA1 in at least one of the following cases: if the pull scan setting is disabled (S31: NO), if the external device password PWB could not be obtained (S35: NO), or if password authentication fails (S37: NO).

[0049] Next, we will explain the process when a pull scan command is received while the retained password PWA2 is set as the main unit password. In this example as well, the controller 11 executes the processes of S5 in Figure 2, S23 in Figure 4, and S31 and S32 in Figure 6, which have already been explained. In S32 (Figure 7), the controller 11 determines that password authentication is required because the retained password PWA2 is set as the main unit password (S52: YES), and sets a value indicating that password authentication is required in the necessity judgment flag (S53), and in S33 in Figure 6, it determines that password authentication is required (S33: YES). The controller 11 executes a pull scan (S40) on the condition that the external device password PWB obtained by requesting it from the PC 40 in S34 matches the retained password PWA2 (S37: YES).

[0050] Then, the controller 11 executes S43, and in S72 of Figure 9, since the retained password PWA2 is set (S72: NO), it does not delete the set retained password PWA2 from memory 12. Therefore, if retained password PWA2 is set as the main unit password, the controller 11 will use the same retained password PWA2 for password authentication in subsequent pull scans. In addition, the controller 11 retains the retained password PWA2 in memory 12 until it is deleted on the password input screen 65 shown in Figure 10, or until the type of main unit password is changed to one-time password PWA1. The controller 11 may also set an upper limit on the number of times the same retained password PWA2 can be used.

[0051] Next, we will explain the process when a pull scan command is received while no password is set on the main unit. In this example as well, the controller 11 executes the processes already explained in Figure 2 (S5), Figure 4 (S23), and Figure 6 (S31, S32). In Figure 7 (S52), the controller 11 sets the necessity judgment flag to a value indicating that password authentication is not required because no password is set on the main unit (S52: NO) (S54). Then, in Figure 6 (S33), the controller 11 determines that password authentication is not required (S33: NO) and instructs the scanner 15 to start scanning (S40). In other words, in this example, since no password is set on the main unit, pull scans are not restricted to anyone. Note that if no password is set on the main unit, the process in S43 can be omitted.

[0052] The first embodiment described above can achieve the following effects. When the MFP10's controller 11 receives a pull scan command from the PC 40 (S4:YES), if a main unit password (one-time password PWA1 or retained password PWA2) is set (S52:YES), and if the external device password PWB included in the pull scan command corresponds to the main unit password (S62:YES), the controller 11 executes the pull scan (S37:YES, S40). If the external device password PWB does not correspond to the main unit password (S62:NO), the controller 11 restricts the pull scan (S37:NO, S41). Also, when the controller 11 receives a pull scan command from the PC 40, if a main unit password is not set (S52:NO), the controller 11 does not require a correspondence between the external device password PWB and the main unit password (S54) and executes the pull scan (S33:NO, S40).

[0053] According to this, when the controller 11 receives a command to execute a pull scan, if a password is set on the main unit side, it determines the correspondence between the main unit password and the external device password PWB. If the two passwords match, the controller 11 executes the pull scan; otherwise, it restricts the pull scan. This allows a user executing a pull scan from the PC 40 to require password authentication to execute the pull scan by setting a password on the main unit side. This also restricts other users from executing pull scans.

[0054] Furthermore, if the controller 11 receives a pull scan command and no password is set on the main unit, it will execute the pull scan without determining whether a password is set. This means that if the user executing the pull scan from the PC 40 determines that authentication is not required, they can send a pull scan command with the main unit password unset, allowing the pull scan to be executed without password authentication. Therefore, even users who are not administrators of the MFP 10 but can set the main unit password can switch whether authentication is required or not for executing a pull scan. This improves usability in the authentication process associated with executing a pull scan.

[0055] Furthermore, in the above embodiment, the pull scan execution instruction from PC40 consists of multiple instructions (S4, S34), and the first instruction that is transmitted first (S4) does not include the external device side password PWB. When the controller 11 receives the pull scan execution instruction from PC40, if the main unit side password is set (S52: YES), it requests PC40 to include a second instruction from the multiple instructions that constitute the pull scan execution instruction, which can include the external device side password PWB (S34). The controller 11 determines the correspondence between the external device side password PWB included in the second instruction received from PC40 and the main unit side password (S62).

[0056] According to this, after confirming that a password is set on the main unit, the external device password PWB can be requested from PC40. If a password is not set on the main unit, it can prevent unnecessary transmission of the external device password PWB to PC40. Furthermore, PC40 can only send the external device password PWB if a password is set on the main unit.

[0057] Furthermore, the first instruction that is initially sent may include the external device password PWB. When the controller 11 receives a pull scan execution instruction from the PC 40, if a main unit password is set, it may determine the correspondence between the external device password PWB included in the first instruction and the main unit password.

[0058] This reduces the number of communications between the MFP10 and PC40. Furthermore, because the external device password (PWB) is obtained during the first instruction stage, password authentication can be initiated more quickly if a password is set on the main unit.

[0059] Furthermore, if the controller 11 has a one-time password PWA1 set and the external device password PWB included in the pull scan execution instruction corresponds to the one-time password PWA1 (S62: YES), it executes the pull scan (S40) and invalidates the one-time password PWA1 when it receives a pull scan execution instruction for the next time (S73). This prevents situations where a user using the MFP10 in the future is unable to perform a pull scan due to the main unit's password by invalidating the one-time password PWA1 after it has been used once.

[0060] Furthermore, if the retained password PWA2 is set and the external device side password PWB included in the pull scan execution instruction corresponds to the retained password PWA2 (S62: YES), the controller 11 executes the pull scan (S40), and also makes the retained password PWA2 valid for subsequent pull scan execution instructions, and performs authentication using the retained password PWA2 (S72: NO). This allows the retained password PWA2, once set, to be used repeatedly for password authentication. This eliminates the need to set the main unit password each time to perform a pull scan with password authentication.

[0061] (Second Embodiment) Next, a second embodiment of this specification will be described. In the first embodiment described above, one authentication password could be set as the retained password PWA2. Once the retained password PWA2 was set, the same retained password PWA2 was used to perform password authentication on multiple PCs 40 connected to the network, unless the retained password PWA2 was changed. In contrast, the MFP 10 of the second embodiment differs from the MFP 10 of the first embodiment in that a different main unit password can be set for each user of the PC 40. In the following description, the main unit password associated with user identification information that identifies the user of the external device will be referred to as the user password PWA3. Also, in the following description, the same configurations and processing contents as in the first embodiment described above will be omitted as appropriate.

[0062] Figure 11 shows a flowchart of the scan control process executed by the controller 11 of the MFP 10 in the second embodiment. In the second embodiment as well, the controller 11 executes the processes shown in Figures 2 to 6 and 9, which have already been described. First, let's explain the case where the one-time password PWA1 is set. If the one-time password PWA1 is set, the controller 11 executes S31 to S36 in Figure 6, as in the first embodiment. Note that S32 in Figure 6 is processed in the same way as in the first embodiment, as shown in Figure 11 (S52: YES, S53).

[0063] As shown in Figure 12, in S36, the controller 11 checks the type of password set on the main unit (S85) and determines whether the checked main unit password is a one-time password PWA1 (S85). In this example, since a one-time password PWA1 is set (S86: YES), the controller 11 executes the process in Figure 8 (the process in S36 of the first embodiment) in S87. Therefore, in the second embodiment as well, password authentication is performed based on the one-time password PWA1 and the external device password PWB, and the one-time password PWA1 is deleted after authentication (S43 in Figure 6).

[0064] Next, we will explain the process when the retained password PWA2 is set as the main unit password. In this example as well, the controller 11 executes the processes S31 to S36 in Figure 6, which have already been explained, makes a negative judgment in S86 in Figure 12 (S86: NO), and executes the user-specific retained password authentication process in S88.

[0065] As shown in Figure 13, the controller 11 checks in S91 whether a user password PWA3 associated with the login username exists. Figure 14 is a diagram illustrating the state in which the user password PWA3 is set. Note that the memory state of the MFP 10's memory 12 transitions between a state in which the user password PWA3 is not stored, a state in which it is stored, or a state in which it is changed. Figure 14 shows one such state of memory 12, and the state of the user password PWA3 stored in memory 12 is not limited to the state shown in Figure 14.

[0066] As shown in Figure 14, the memory 12 stores the user password PWA3 separately from the retained password PWA2. In the initial state, for example, the MFP10 does not store any of the one-time password PWA1, retained password PWA2, or user password PWA3 in the memory 12, and the main unit password is not set.

[0067] First, we will explain the process when the retained password PWA2 is set and the user password PWA3 is not set. In S91, the controller 11 checks if the user password PWA3 associated with the login username is stored, and in S92, it determines whether the associated user password PWA3 exists. In this example, since the user password PWA3 is not set (S92: NO), the controller 11 executes S93. Similar to S61 and S62 in Figure 8, the controller 11 determines whether the external device side password PWB obtained from the PC 40 matches the retained password PWA2 stored in memory 12 (S93), and if they match (S94: YES), it executes S95.

[0068] In S95, the controller 11 stores the configured retention password PWA2 as the user password PWA3 in memory 12, associating it with the login username of PC 40 (S95). The controller 11 stores the user password PWA3 in non-volatile memory, such as NVRAM. For example, in S34 of Figure 6, the controller 11 requests PC 40 to send the login username and PC name in addition to the external device password PWB. The login username of PC 40 is, for example, the username of the user who was operating PC 40 when the pull scan execution instruction was issued. The PC name is the computer name set on PC 40 that sent the pull scan execution instruction. In S95, the controller 11 stores the login username and PC name obtained from PC 40, associating them with the user password PWA3 (retention password PWA2).

[0069] For example, as shown in Figure 14, when a pull scan is received from PC40A, whose PC name is "PCA", if the retained password PWA2 matches the login password "AAA" of PC40A (S94:YES), the retained password PWA2 "AAA" is stored in memory 12, associated with the PC name "PCA" and login username "userA" of PC40A. Note that in S94, if the passwords do not match (S94:NO), the controller 11 sets the authentication completion flag to a value indicating that password authentication failed (false) (S96), similar to S64 in Figure 8. If a value indicating that password authentication failed (false) is set, the controller 11 determines in S37 in Figure 6 that user authentication has failed (S37:NO) and executes S41.

[0070] Furthermore, in S95, the user identification information associated with the user password PWA3 may be at least one of the following: the login username of the user logged into PC40, or the PC name of PC40. Alternatively, the user identification information may be information other than the login username and PC name, such as the IP address of PC40. Also, the timing for requesting the login username and PC name is not limited to the timing of S34 in Figure 6. For example, PC40 may send the login username and PC name when sending the pull scan execution instruction in S4. That is, the first instruction may include the user identification information. In addition, the controller 11 may request the user identification information from PC40 when executing S95.

[0071] After executing S95, controller 11 executes S97. In S97, controller 11 sets the authentication completion flag to a value indicating success (true), similar to S63 in Figure 8. Controller 11 finishes the processes in Figures 13 and 12 and performs a pull scan (S37: YES, S40 in Figure 6). Note that in this example, the device-side password is retained as password PWA2 and is therefore not deleted (S72: NO in Figure 9).

[0072] Next, we will explain the case where "AAA" is set as the retained password PWA2, PC40B with the login password "BBB" as shown in Figure 14 sends a pull scan execution command, and the user password PWA3 associated with the login username "userB" of PC40B is not stored in memory 12. In this example, since the user password PWA3 associated with the login username "userB" is not stored (S92: NO), the controller 11 executes S93. Since the login password, the external device side password PWB "BBB", and the retained password PWA2 "AAA" do not match (S94: NO), the controller 11 does not execute a pull scan (S96), and does not store the user password PWA3 "BBB" in memory 12. In this example, if the retained password PWA2 is changed from "AAA" to "BBB", the external device password PWB and the retained password PWA2 will match (S94:YES). Therefore, the controller 11 stores the retained password PWA2 "BBB" in memory 12, associating it with the PC name "PCB" and login username "userB" of PC40B. The same applies if another PC40C sends a pull scan execution command.

[0073] Next, we will describe the case where the retained password PWA2 "AAA" is set, and the user password PWA3 "AAA" associated with the login username "userA" is stored, and PC40A with login password "AAA" sends a pull scan execution command. In this example as well, the controller 11 executes the processes shown in Figures 11 and 12, which have already been explained. In this example, since the user identification information sent from the external device, i.e., the user password PWA3 "AAA" associated with the login username "userA" of PC40A is stored (S92: YES in Figure 13), the controller 11 executes S98.

[0074] Furthermore, in S92, the controller 11 may determine whether the user identification information obtained from PC 40 matches the information stored in memory 12 for both the login username and PC name. That is, if the login username and PC name of PC 40 that sent the pull scan execution instruction match the login username and associated PC name stored in memory 12, the controller 11 may determine whether the user password PWA3 associated with those usernames and PC names is stored in memory 12. For this reason, if the combination of login username and PC name differs from the information in memory 12, the controller 11 may make a negative determination in S92.

[0075] In S98, the controller 11 determines whether the external device password PWB obtained from PC40A matches the user password PWA3 associated with the login username of PC40A. In this example, the external device password PWB "AAA" matches the user password PWA3 "AAA" associated with the username "userA" (S99: YES), so the controller 11 performs a pull scan (S97). Therefore, PC40, once the user password PWA3 has been registered, can perform a pull scan regardless of whether the set retained password PWA2 matches the external device password PWB, provided that the associated user password PWA3 matches the external device password PWB.

[0076] Next, we will explain the case where the retained password PWA2 "AA2" is set, and the user password PWA3 "AAA" is registered in association with the login username "userA" of PC40A, and PC40A with login password "AA2" sends a pull scan execution command. That is, we will explain the case where a pull scan is performed with an external device side password PWB "AA2" which is different from the user password PWA3 "AAA" already stored in association with the login username "userA", and which matches the retained password PWA2. In this example as well, the controller 11 executes S91, S92, S98, and S99 in Figure 13.

[0077] In this example, the external device password PWB "AA2" and the user password PWA3 "AAA" associated with the username "userA" on PC40A do not match (S99: NO), so the controller 11 executes S101. In S101, the controller 11 determines whether the external device password PWB matches the retained password PWA2 (S101). In this example, the login password "AA2" obtained from PC40A matches the retained password PWA2 (S102: YES), so in S103, the controller 11 asks whether to update the user password PWA3 already associated with the login username to the retained password PWA2. Note that if the external device password PWB and the retained password PWA2 do not match (S102: NO), the controller 11 does not perform a pull scan (S96). Therefore, if the external device password PWB does not match either the retained password PWA2 or the user password PWA3, the controller 11 restricts the execution of the pull scan.

[0078] In S103, the controller 11 communicates with PC40A, for example, to display a pop-up screen on PC40A to confirm whether an update is necessary. If the controller 11 obtains information from PC40A that the user agrees to update the user password PWA3 (S104: YES), it updates the user password PWA3 in S105. For example, as shown in Figure 14, the controller 11 updates the user password PWA3 "AAA" already associated with the login username "userA" of PC40A, which sent the pull scan command, to the external device side password PWB "AA2" obtained from PC40A in this pull scan command. After updating the user password PWA3, the controller 11 executes the pull scan (S97). If the user of PC40A does not agree to update the user password PWA3 (S104: NO), the controller 11 executes the pull scan without updating the user password PWA3 associated with the login username "userA" to "AAA" (S97).

[0079] Next, we will explain the process when a pull scan command is received after the previously set retained password PWA2 has been deleted and the main unit password (both retained password PWA2 and one-time password PWA1) is not set. In this example, the controller 11 makes a negative determination at S52 in Figure 11 (S52: NO), and, as in the first embodiment, sets a value in the necessity determination flag indicating that password authentication is not required (S54).

[0080] Next, the controller 11 checks in memory 12 whether a user password PWA3 associated with the login username is stored (S81). If at least one user password PWA3 is stored in memory 12 (S82: YES), the controller 11 deletes all stored user password PWA3s and the login username and PC name information associated with the user password PWA3s (S83). The controller 11 performs a pull scan without requesting password authentication (S33: NO in Figure 6). If no user password PWA3s are stored (S82: NO), the controller 11 also performs a pull scan without requesting password authentication (S33: NO). In S83, the controller 11 deletes the user password PWA3s as a process to invalidate them when it receives instructions to perform a pull scan in the future. However, it is not limited to this; the user password PWA3s may also be stored in memory 12 in an unusable state, or they may be retained as past history.

[0081] The second embodiment described above can achieve the same effects as the first embodiment. Furthermore, the second embodiment can achieve the following effects. Controller 11 can set a user password PWA3 corresponding to the login username that identifies the user of PC 40, for each login username. Controller 11 executes a pull scan (S97) if the external device password PWB (login password) included in the pull scan execution instruction matches the user password PWA3 associated with the login username included in the pull scan execution instruction (S99:YES), and restricts the pull scan (S96) if they do not match (S99:NO).

[0082] According to this, a user password PWA3 can be set for each user identification piece of information (such as the login username). By registering the user password PWA3, even if the retained password PWA2 is changed, the registered user password PWA3 can be used as the external device's password PWB, allowing a pull scan to be performed using password authentication.

[0083] Furthermore, the user identification information is the login username of the user logged into PC40 when PC40 sends a pull scan execution command that includes the user identification information. This allows the user who issued the pull scan execution command to be identified by the login username, and password authentication can be performed. Also, even if the PC40 being used is changed, a pull scan can be performed from another PC40 using password authentication by setting the login username and login password.

[0084] Furthermore, the user identification information may also be the computer name of the external device that sent the pull scan execution command containing the user identification information from the external device. This allows the user who issued the pull scan execution command to be identified by the PC name, and password authentication can be performed.

[0085] Furthermore, if the user password PWA3 associated with the login username included in the pull scan execution instruction is not set (S92: NO), and if the external device side password PWB and the retained password PWA2 correspond (S94: YES), the controller 11 executes a pull scan and stores the retained password PWA2 as the user password PWA3, associated with the login username (S95). If the external device side password PWB and the retained password PWA2 do not correspond (S94: NO), the controller 11 restricts the pull scan.

[0086] According to this, if the user password PWA3 is not set, the retained password PWA2 can be set as the user password PWA3 by issuing a pull scan command. By setting the retained password PWA2 on the MFP10 side and then executing a pull scan, an arbitrary user password PWA3 can be set for each user.

[0087] Furthermore, if the external device password PWB and the user password PWA3 associated with the login username do not match (S99: NO), the controller 11 performs a pull scan if the external device password PWB and the retained password PWA2 match (S102: YES), and restricts the pull scan if they do not match (S102: NO).

[0088] According to this, when a single PC40 is shared, any user can register a user password PWA3 by logging into that PC40 and performing a pull scan. Furthermore, another user can log into that PC40 with a different username and login password and perform a pull scan. If the MFP10 is configured with their own login password as the retained password PWA2, they can perform the pull scan using password authentication. This allows for proper management of user-specific scan data on a shared PC.

[0089] Furthermore, if the external device password PWB and the user password PWA3 associated with the login username do not match (S99: NO), the controller 11 checks whether to update the user password PWA3 associated with the login username to the retained password PWA2 if the external device password PWB and the retained password PWA2 match (S102: YES) (S103). If the controller 11 receives an instruction to update (S104: YES), it updates the user password PWA3 to the retained password PWA2 (S105), and if it does not receive an instruction to update (S104: NO), it does not change the user password PWA3.

[0090] According to this, when the login password for PC40 is changed, the user password PWA3 associated with the login username can be updated by also changing the PWA2 password held on the MFP10. The user can instruct the MFP10 whether or not to update.

[0091] Furthermore, when the controller 11 receives a pull scan command, if the main unit password is not set (S52: NO), it does not require a correspondence between the external device password PWB and the main unit password (S54), executes the pull scan, and disables the user password PWA3 associated with the login username (S83). As a result, by executing a pull scan with the main unit password unset, the user password PWA3 stored in memory 12 up to that point can be disabled.

[0092] (Other embodiments) The reading device is not limited to the above embodiment, and various modifications are possible without departing from its spirit. The order and content of the processes shown in Figures 3 to 9 and 11 to 13 in the above embodiment are examples only. For example, if the user password PWA3 associated with the login username included in the pull scan execution instruction is not set (S92: NO), the controller 11 may ask the user whether or not to register the external device password PWB as the user password PWA3 in memory 12. Furthermore, if the external device password PWB and the stored user password PWA3 do not match (S98:NO), the controller 11 does not need to determine whether the external device password PWB matches the retained password PWA2. In this case, the execution of a pull scan may be restricted. Furthermore, the controller 11 does not need to perform the confirmation (S103) to whether or not to update the user password PWA3 associated with the login username to the retained password PWA2. In this case, the controller 11 may or may not update without confirmation. Furthermore, if no password is set on the main unit side (S52:NO), the controller 11 does not need to delete the user password PWA3.

[0093] Furthermore, the storage location of the passwords in each embodiment is merely an example. For example, in each embodiment, the controller 11 may store both the one-time password PWA1 and the retained password PWA2 in volatile memory, or it may store both in non-volatile memory. Also, in the second embodiment, the controller 11 may store the user password PWA3 in volatile memory. Furthermore, the MFP10 may be configured to allow editing of the user password PWA3 and associated information stored in memory 12 using a user interface 16 or the like. Furthermore, the controller 11 may be configured to perform only one of either password authentication using a one-time password PWA1 or password authentication using a retained password PWA2. Furthermore, while the controller 11 was configured to store only one of either the one-time password PWA1 or the retained password PWA2 in the memory 12, it may also be configured to store both passwords simultaneously in the memory 12. The controller 11 may also be configured to manage the storage and deletion of the two authentication passwords individually and to allow switching between the authentication passwords to be used. As an example of a reading device, the MFP10 was used in the explanation, but the reading device may be any device capable of performing only the "scanner" function. [Explanation of symbols]

[0094] 10 MFP (Reader), 11 Controller, 15 Scanner, 16 User Interface (User IF), 40 PC (External Device), PWA1 One-Time Password (Device-side password, Type 1 device-side password), PWA2 Retention Password (Device-side password, Type 2 device-side password), PWB External Device Password, PWA3 User Password.

Claims

1. User interface and Scanner and Controller and Equipped with, The aforementioned controller, It is possible to perform push scans, in which the scanner reads a document based on execution instructions corresponding to operations on the user interface, and pull scans, in which the scanner reads a document based on execution instructions from an external device. The aforementioned controller, It is possible to set the main unit password used for the pull scan via the user interface. The aforementioned controller, When an instruction to perform the pull scan is received from an external device, and a password is set on the main unit side, if the password on the external device side included in the instruction to perform the pull scan corresponds to the password on the main unit side, the pull scan can be performed; if the password on the external device side and the password on the main unit side do not correspond, the pull scan can be restricted. The aforementioned controller, When the pull scan execution command is received from the external device, if the main unit password is not set, the pull scan is executed without requiring a correspondence between the external device password and the main unit password. A reading device configured in such a way.

2. The instruction to execute the pull scan from the external device is: It consists of multiple instructions, and of these instructions, the first instruction that is sent first does not include the password for the external device. The aforementioned controller, When the pull scan execution instruction is received from the external device, if the main unit password is set, the system requests the external device to provide a second instruction from among the multiple instructions constituting the pull scan execution instruction, which can include the external device password, and determines the correspondence between the external device password included in the second instruction received from the external device and the main unit password. The reading device according to claim 1, configured as described above.

3. The instruction to execute the pull scan from the external device is: It consists of multiple instructions, and the first instruction that is sent first contains the password for the external device. The aforementioned controller, When the pull scan execution instruction is received from the external device, if the main unit has a password set, the correspondence between the external device password included in the first instruction and the main unit password is determined. The reading device according to claim 1, configured as described above.

4. The aforementioned controller, It is possible to set a user password corresponding to the user identification information that identifies the user of the external device, for each piece of user identification information. The aforementioned controller, When an instruction to execute the pull scan, including the user identification information, is received from the external device, if the external device password included in the pull scan instruction corresponds to the user password associated with the user identification information included in the pull scan instruction, the pull scan is executed. If the external device password included in the pull scan instruction does not correspond to the user password associated with the user identification information included in the pull scan instruction, the pull scan is restricted. The reading device according to claim 1 or claim 2, configured as described above.

5. The aforementioned controller, It is possible to set a Type 1 device-side password and a Type 2 device-side password as the aforementioned device-side passwords. The aforementioned controller, If the first type of main unit password is set, and the external device password included in the pull scan execution instruction corresponds to the first type of main unit password, the pull scan is executed, and the first type of main unit password is invalidated when the next pull scan execution instruction is received. If the second type of main unit password is set, and the external device password included in the pull scan execution instruction corresponds to the second type of main unit password, the pull scan is executed, and the second type of main unit password is kept valid for subsequent pull scan execution instructions, and authentication using the second type of main unit password is performed. The reading device according to claim 1 or claim 2, configured as described above.

6. The user identification information is, The reader according to claim 4, wherein when the external device transmits an execution instruction for the pull scan including the user identification information, the user name is the logged-in username of the user logged into the external device.

7. The user identification information is, The reading device according to claim 4, wherein the computer name of the external device is the name of the external device when the external device transmits the instruction to perform the pull scan, which includes the user identification information.

8. The aforementioned controller, When the external device receives an instruction to execute the pull scan, which includes the user identification information, and the user password associated with the user identification information included in the pull scan instruction is not set, If the external device password included in the pull scan execution instruction corresponds to the main unit password, the pull scan is executed, and the main unit password is stored as the user password in association with the user identification information. If the password for the external device and the password for the main unit do not match, the pull scan is restricted. The reading device according to claim 4, configured as described above.

9. The aforementioned controller, If the external device password included in the pull scan execution instruction does not correspond to the user password associated with the user identification information included in the pull scan execution instruction, the pull scan is executed if the external device password and the main unit password correspond, and the pull scan is restricted if the external device password and the main unit password do not correspond. The reading device according to claim 4, configured as described above.

10. The aforementioned controller, If the external device password included in the pull scan execution instruction does not correspond to the user password associated with the user identification information included in the pull scan execution instruction, and if the external device password and the main unit password do correspond, then check whether to update the user password associated with the user identification information to the main unit password. The system will confirm whether or not to update the password, and if it accepts the update instruction, it will update the user password to the device's password; if it does not accept the update instruction, it will not change the user password. The reading device according to claim 9, configured as described above.

11. The aforementioned controller, When the pull scan execution command is received from the external device, if the main unit password is not set, the pull scan is executed without requiring a correspondence between the external device password and the main unit password, and the user password associated with the user identification information is invalidated. The reading device according to claim 4, configured as described above.

Images