Reading device

The reading device enables both push and pull scanning with controlled authentication, addressing the inconvenience of uniform prohibition in existing devices by balancing security and user convenience through flexible execution of pull scans based on pre-set restrictions.

JP2024158468APending Publication Date: 2024-11-08BROTHER KOGYO KK
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023073696
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-04-27
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

Existing reading devices uniformly prohibit unregistered users from performing pull scans, which can be inconvenient and lack a balance between security and user convenience.

Method used

A reading device that allows both push and pull scanning, with a controller that sets limit settings for push scans and determines whether authentication is required for pull scans based on these settings, executing pull scans without authentication if not needed, and only if authentication is successful.

Benefits of technology

Balances security and user convenience by allowing flexible execution of pull scans based on pre-set restrictions, differentiating security levels between push and pull scans, and ensuring authorized access.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024158468000001_ABST
    Figure 2024158468000001_ABST
Patent Text Reader

Abstract

To provide a reading device which can maintain balance between security and convenience of a user.SOLUTION: A controller 11 of a MFP10 can limit a push scan according to a restriction set value when receiving an instruction to execute a push scan. The controller determines whether authentication is necessary on the basis of the restriction set value when receiving an instruction to execute a pull scan from an external apparatus, executes a pull scan without requiring authentication when authentication is determined not to be necessary, and executes a pull scan if the authentication is a success when authentication is determined to be necessary, does not execute a pull scan, and does not execute a pull scan if the authentication is a failure.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a reading device that reads an original document using a scanner. [Background technology]

[0002] Patent Document 1 describes a reading device capable of performing pull scan, which causes a scanner to read a document in response to an execution instruction from an external device. In the reading device, a list of users who are permitted to execute pull scan is registered in advance, and when an execution instruction for pull scan is received, the reading device authenticates whether the user who issued the execution instruction matches a registered user. If the authentication is successful, the reading device starts pull scan. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2014-030182 A Summary of the Invention [Problem to be solved by the invention]

[0004] The reading device described in Patent Document 1 allows registered users to perform pull scan, but uniformly prohibits unregistered users from performing pull scan, which can be inconvenient for users and leaves room for improvement.

[0005] The present invention has been made in consideration of the above-mentioned problems, and has an object to provide a reading device that can balance security and user convenience. [Means for solving the problem]

[0006] In order to solve the above problems, the reading device disclosed in this embodiment includes a user interface, a scanner, and a controller. The controller is capable of executing push scan, which causes the scanner to read a document in response to an execution instruction according to an operation on the user interface, and 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 limit setting value for limiting the push scan, and restricting the push scan in response to the limit setting value when an execution instruction for the push scan is received via the user interface. When an execution instruction for the pull scan is received from the external device, the controller determines whether or not authentication is required based on the limit setting value, and when it determines that authentication is not required, executes the pull scan without requiring authentication, and when it determines that authentication is required, executes the pull scan if authentication is successful, and does not execute the pull scan if authentication fails.

[0007] In the above configuration, when an instruction to execute a pull scan is received, the controller determines whether or not authentication is required based on the restriction setting value set for push scan. If the controller determines that authentication is not required, the controller executes a pull scan without requiring authentication. On the other hand, if the controller determines that authentication is required based on the restriction setting value, the controller executes a pull scan if authentication is successful, and does not execute a pull scan if authentication is unsuccessful. This makes it possible to determine security for a pull scan according to the restrictions already set for push scan when an instruction to execute a pull scan is received. As a result, it is possible to strike a balance between security and user convenience. Effect of the Invention

[0008] According to the present invention, it is possible to provide a reading device capable of performing both push scanning and pull scanning, which is capable of achieving a balance between security and user convenience. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating the configuration of an MFP. [Diagram 2] 1 is a timing chart illustrating processing executed between a PC and an MFP. [Diagram 3] FIG. 2 is a diagram illustrating a home screen displayed by a browser. [Figure 4] FIG. 13 is a diagram illustrating a restriction setting screen. [Diagram 5] FIG. 2 is a diagram illustrating an SFL database. [Figure 6] 11 is a flowchart illustrating a process executed by a controller of the MFP. [Figure 7] 7 is a flowchart illustrating a process executed in S11 of FIG. 6. [Figure 8] 7 is a flowchart illustrating the process executed in S12 of FIG. 6. [Figure 9] 9 is a flowchart illustrating the process executed in S32 of FIG. 8. [Figure 10] 10 is a flowchart illustrating the process executed in S36 of FIG. 8. [Figure 11] 10 is a flowchart illustrating the process executed in S38 of FIG. 8. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0011] The communication IF 18 connects the MFP 10 to a network. This allows the MFP 10 to communicate with a PC 40 connected to the network via the network in accordance with a predetermined protocol. The scanner 15 has a reading sensor such as a CCD or CIS, and generates image data according to reading of an original. The printer 13 prints an image on a recording medium such as a sheet or a disk. A sheet is also called paper. The recording method of the printer 13 can be an inkjet method, an electrophotographic method, or the like.

[0012] The user IF 16 is an interface capable of accepting various operations on the MFP 10 by a user. The user IF 16 includes a touch panel including a liquid crystal display, various switches, and the like. The USB IF 17 reads and writes data in accordance with the USB standard from and to a detachably connected USB-compatible storage medium. An example of a USB-compatible storage medium is a USB memory. The communication IF 18 is an interface that connects the MFP 10 to a network. The communication IF 18 enables the MFP 10 to communicate with the PC 40 via a wired LAN or wireless LAN.

[0013] The memory 12 is configured by combining a volatile memory such as RAM, a non-volatile memory such as NVRAM, a ROM, etc. As the non-volatile memory, an SSD, a HDD, etc. may be used. A buffer provided in the controller 11 and used when executing various programs may also be considered as a part of the memory 12. The memory 12 may be a storage medium readable by the controller 11. The storage medium readable by the controller 11 is a non-transitory medium. In addition to the above examples, the non-transitory medium also includes recording media such as CD-ROM and DVD-ROM. In addition, the non-transitory medium is also a tangible medium. On the other hand, an electrical signal carrying a program downloaded from a server on the Internet is a computer-readable signal medium, which is a type of computer-readable medium, but is not included in the non-transitory computer-readable storage medium.

[0014] The memory 12 stores firmware (not shown) as a program executable by the controller 11. In this embodiment, the process of the controller 11 according to the instructions written in the program is mainly shown. That is, the processes of the controller 11, such as "judging", "calculating", "identifying", "obtaining", "accepting", and "controlling" in the following description, represent the processes of the controller 11. Note that "obtaining" is used as a concept that does not require a request. That is, the process of the controller 11 receiving data without a request is also included in the concept of "the controller 11 obtaining data". In addition, "data" in this specification is represented by a bit string that can be read by the controller. Data with the same substantial meaning but different formats are treated as the same data. The same applies to "information" in this specification.

[0015] The controller 11 also functions as a web server for displaying a predetermined web page on the PC 40. The controller 11 can display the web page on a browser 41 (described later) of the PC 40 by transmitting web page data for displaying the web page to the PC 40. The controller 11 also functions as a web server by executing firmware (not shown).

[0016] Next, the configuration of the PC 40 will be described. The PC 40 includes a communication IF, a memory, a controller, a display, and a user IF, all of which are not shown. An OS and a browser 41 are stored in the memory of the PC 40. The browser 41 can display a web page on the display in accordance with web page data transmitted from the MFP 10. Note that the external device is not limited to the PC 40, and may be a mobile terminal such as a smartphone, as long as it is a device capable of transmitting an instruction to execute a pull scan, which will be described later, to the MFP 10.

[0017] Next, the procedure of a process for setting restriction setting values ​​relating to restrictions on each function of MFP 10 using the function of controller 11 as a Web server will be described with reference to Fig. 2. A user operates PC 40 to input a URL for identifying the Web server of MFP 10 to browser 41. Browser 41 transmits a GET request of HTTPS communication including the input URL at timing 10 (hereinafter, timing will also be referred to as "T"). When controller 11 receives the GET request from browser 41, it transmits an HTTPS response corresponding to the GET request.

[0018] The response returned in T11 includes web page data for displaying the home screen before login. When the browser 41 receives the web page data, in T12, the browser 41 uses the web page data to display the home screen before login on the display. Details of the home screen will be described later.

[0019] When the user inputs a login password in the password input field on the home screen, in T13 the browser 41 transmits a POST request including the login password to the controller 11. Upon receiving the POST request including the login password, in T14 the controller 11 performs user authentication processing using the login password included in the POST request.

[0020] In the user authentication process executed at T14, the controller 11 determines whether the input password included in the POST request matches the registered login password. The controller 11 compares the input password included in the POST request with the registered password, and permits user authentication for the MFP 10 if the two passwords match completely. Alternatively, the controller 11 may permit user authentication for the MFP 10 if the input password and the registered password match partially.

[0021] If the input password matches the registered password as a result of the user authentication process in T14, the controller 11 generates a response for when the user authentication process is successful. This response includes web page data for displaying a post-login home screen, which is a web page.

[0022] In S15, the controller 11 transmits a response to the browser 41 to display the post-login home screen. Upon receiving the response, the browser 41 in S16 displays the post-login home screen 20, which is a Web page, on the user IF 16. The post-login home screen 20 shown in FIG. 3 includes a page display field 21 made up of an item section 22 and a content display section 23. The item section 22 is a section in which icons that accept selection operations for various functions of the MFP 10 are displayed. In addition to this, a URL display field that displays the URL of a registered site may be included above the page display field 21.

[0023] When a selection operation is performed on any of the icons in the item section 22, the browser 41 transmits a GET request requesting Web page data corresponding to the selected icon to the controller 11. In response to the request, the controller 11 transmits a response including the Web page data to the PC 40. This allows the browser 41 to display a Web page corresponding to the selected item on the content display section 23. Note that instead of a configuration in which the controller 11 transmits Web page data as a response to the browser 41, a configuration may be adopted in which the controller 11 transmits only data indicating a screen to be displayed on the content display section 23 to the browser 41, and the browser 41 uses the data to change the display on the content display section 23.

[0024] This example shows a state in which the user has selected "User Restriction Function" from among the icon 22A "Administrator" in the item section 22 on the home screen 20 after logging in. The "User Restriction Function" is a function for setting a setting value related to restrictions for the user who uses the MFP 10. The setting value related to restrictions can also be said to be a setting value related to permission. The content display section 23 includes check boxes 24A, 24B, 24C, and 24D corresponding to the items "Off," "Secure Function Lock," "Active Direction Authentication," and "LDAP Authentication" for receiving instructions for detailed settings related to the function "User Restriction Function."

[0025] When the user checks the check box 24A for the item "Off" displayed on the content display unit 23, the function "User Restriction Function" is disabled, and when the user does not check the check box 24A but checks another check box, the function "User Restriction Function" is enabled. The item "Secure Function Lock" is an item that accepts restriction settings for each function of the MFP 10 for each user. In the following, "Secure Function Lock" is also referred to as "SFL." When the user checks the check box 24B for "SFL," it becomes possible to set a restriction setting value indicating the restriction of each function using a restriction setting screen 30 shown in FIG. 4, which will be described later.

[0026] When the user checks the "SFL" check box 24B included in the content display section 23 of the home screen 20 and operates the approval button 26, at T17 the browser 41 transmits a GET request to the MFP 10 requesting web page data for displaying the restriction setting screen 30 shown in Fig. 4 on the content display section 23. Upon receiving the GET request from the PC 40, the MFP 10 transmits response data including web page data for displaying the restriction setting screen 30 on the browser 41 to the PC 40 at T18. Note that if the user operates the PC 40 to operate the cancel button 25 on the home screen 20, the input made to the content display section 23 of the home screen 20 is canceled.

[0027] When the browser 41 receives the response data from the MFP 10, at T19, it displays the restriction setting screen 30 shown in Fig. 4. The restriction setting screen 30 includes a restriction specification field 31 that accepts specification of the users and functions to be restricted in the function "SFL" described above. The restriction specification field 31 also includes user specification items 32 (32A, 32B) that specify the users to be restricted, and function specification items 33 that specify the functions to be restricted. Each value on the restriction setting screen 30 corresponds to the registered contents of the SFL database 19 stored in the memory 12 of the MFP 10.

[0028] Among the user specification items 32, "Public Mode" 32A is an item that specifies the target of the function "SFL" to be a state where the user is not logged in. It can also be said to be an item that sets restrictions without specifying a user. Among the user specification items 32, individual user item 32B is an item that specifies the target of the function "SFL" to be the input user, i.e., a specific user.

[0029] The function designation item 33 is an item that accepts designation of a function for which a restriction is set by the function "SFL". In the restriction setting screen 30 shown in FIG. 4, a check box indicating whether or not a restriction is set is displayed in the function designation item 33 for each of the functions "print", "copy", "scan", "FAX", "USB", and "Web connection" of the MFP 10. The function "scan" corresponds to push scan, which will be described later. In the function designation item 33, a checked function is a function for which no restriction is specified, and a non-checked function is a function for which a restriction is specified. Although not shown, the function "FAX" includes individual functions of "FAX transmission" and "FAX reception", and each of the individual functions has a check box. The function "USB" includes individual functions of "USB direct print" and "Scan to USB", and each of the individual functions has a check box. The "Web connection" includes individual functions of "upload" and "download", and each of the individual functions has a check box.

[0030] In addition to the restrictions on each of the above functions, function specification item 33 also includes "Page Limits", which specifies the upper limit on the number of pages that can be printed, and "Page Counters", which indicates the cumulative number of pages printed when not logged in or for each user.

[0031] For example, in the function designation item 33 related to the "Public Mode" 32A among the user designation items 32, only the function "scan" is not checked, and the other functions are checked. Therefore, when no one is logged in to the MFP 10, it indicates that the execution of the function "scan" is restricted, and the execution of the other functions is not restricted. Similarly, in the function designation item 33 related to "User A" of the individual user item 32B, only the function "scan" is not checked, and the other functions are checked. Therefore, it indicates that when "User A" logs in, the execution of the function "scan" is restricted, and the other functions are not restricted. In the function designation item 33 related to "User B" of the individual user item 32B, all functions are checked. Therefore, it indicates that when "User B" logs in, the execution of all functions including the function "scan" is not restricted.

[0032] When the user operates a confirm button (not shown) with the limit setting screen 30 displayed on the home screen 20, in T20 the browser 41 sends to the MFP 10 a POST request including information "ON" indicating that the function "SFL" is enabled and the contents of each limit setting value specified on the limit setting screen 30. When the controller 11 receives the POST request including the information indicating that the function "SFL" is enabled and the specified contents of each limit setting value, in T21 it updates the contents of the SFL database 19 stored in the memory 12.

[0033] FIG. 5 shows a part of the SFL database 19 updated using the designated contents of the restriction setting value designated on the restriction setting screen 30 shown in FIG. 4. In FIG. 5, the first column 19A has a restriction setting value "ON" registered, which indicates that the function "SFL" is enabled. In column 19B, a restriction setting value for each function is registered for "Public Mode", i.e., a state where the user is not logged in. Specifically, in column 19B, a restriction setting value "Restrict" is registered, which indicates that the function "Scan" is restricted, i.e., execution of "Scan" is not enabled. Similarly, in column 19C, a restriction setting value for each function is registered for "User A", and a restriction setting value "Restrict" is registered, which indicates that the function "Scan" is restricted. In column 19D, a restriction setting value for each function is registered for "User B", and a restriction setting value "Allow" is registered, which indicates that the function "Scan" is not restricted, i.e., execution of "Scan" is enabled. Execution being enabled can also be said to be permitted.

[0034] Next, the procedure of the process executed by the controller 11 when the user utilizes the "scan" function of the MFP 10 will be described. The MFP 10 is capable of executing "push scan" and "pull scan" as the "scan" function. "Push scan" is a scan that causes the scanner 15 to read an original document in response to an execution instruction corresponding to an operation on the user IF 16. "Pull scan" is a scan that causes the scanner 15 to read an original document in response to an execution instruction transmitted from an external device in response to an operation on the external device. In this embodiment, the external device is the PC 40.

[0035] First, in step 10, the controller 11 determines whether or not an instruction to execute a push scan has been received. Hereinafter, a step is also referred to as "S". Specifically, when an instruction to execute the function "scan" has been received by an operation on the user IF 16 of the MFP 10, the controller 11 determines that an instruction to execute a push scan has been received (S10: YES), and proceeds to S11. In response to receiving the operation on the user IF 16, the controller 11 transmits a request for a push scan to an external device (in this example, the PC 40). The external device that receives the request returns an instruction to execute "scan" to the MFP 10. When this reply is received, the controller 11 determines that an instruction to execute a push scan has been received. When an execution instruction transmitted from an external device in response to an operation on the external device has been received, the controller 11 determines that an instruction to execute a pull scan has been received (S10: NO), and proceeds to S12.

[0036] The instruction to execute "scan" may include information indicating whether the instruction is an instruction in response to an operation on the user IF 16 or an operation on an external device. The controller may determine whether the instruction is an instruction to execute a push scan or an instruction to execute a pull scan based on the information. Furthermore, the controller 11 may determine that an instruction to execute a push scan has been accepted in response to an operation on the user IF 16, without transmitting a request to the external device, and proceed to S11.

[0037] This section describes the procedure for restricting the push scan in S11 when the controller 11 receives an instruction to execute a push scan via the user IF 16 (S10: YES), in accordance with the limit setting value registered in the SFL database 19. Figure 7 is a flowchart illustrating the procedure for the push scan request processing executed by the controller 11 in S11.

[0038] First, the process in a state where no one has logged in to the MFP 10 will be described. For convenience, the state in which no one has logged in to the MFP 10 will also be referred to as "Public Mode." In S20, the controller 11 refers to the enabled "ON" or disabled "OFF" of the function "SFL" registered in the field 19A of the SFL database 19 stored in the memory 12.

[0039] When the controller 11 determines that the function "SFL" is disabled (S21: NO), the process proceeds to S29, and executes a scan process in which the scanner 15 reads the document set on the document platen. That is, the controller 11 executes the process without imposing any restrictions on the push scan, and ends the processes in FIGS. 6 and 7.

[0040] 5, the restriction setting value indicating whether the function "SFL" is enabled is "ON", so the controller 11 determines that the function "SFL" is enabled (S21: YES). Then, the controller 11 proceeds to S22, and checks the presence or absence of a logged-in user by operating the user IF 16. In this example, since no user is logged in to the MFP 10 (S23: YES), the controller 11 proceeds to S24, and refers to the restriction setting value in the SFL database 19 that corresponds to the function "scan" in "Public Mode".

[0041] Since the restriction setting value corresponding to the function "scan" in "Public Mode" in the SFL database 19 is "restricted" (S25: YES), the controller 11 proceeds to S28 and notifies an error indicating that the function "scan" cannot be executed. In this embodiment, the controller 11 notifies by having the user IF 16 display an error screen indicating that the function "scan" cannot be executed. That is, the controller 11 places a restriction on push scanning when the user is not logged in. In this embodiment, the restriction on the function "scan" means that scan processing is not executed. The controller 11 ends the processing of Figs. 6 and 7.

[0042] Next, a process when "user A" is logged in to the MFP 10 will be described. Since "user A" is logged in (S23: NO), the controller 11 refers to the restriction setting value corresponding to the function "scan" for user A in the SFL database 19 in S26. As shown in FIG. 5, in column 19C, the restriction setting value corresponding to the function "scan" for "user A" is set to "restricted." Since the restriction setting value corresponding to the function "scan" for user A, who is the corresponding logged-in user, indicates "restricted" (S27: YES), the controller 11 proceeds to S28. In S28, the controller 11 notifies an error indicating that scanning cannot be executed, as already described, and ends the processes in FIGS. 6 and 7.

[0043] Next, a process will be described when "user B" is logged in to the MFP 10. Since the limit setting value "ON" that does not limit the function "scan" for "user B" is registered in the SFL database 19 (S27: NO), the controller 11 proceeds to S29 and executes a scan process (push scan). That is, the controller 11 executes the push scan without imposing any restrictions.

[0044] Here, login will be described. User information of "user A" and "user B" is registered in the SFL database 19. The user information is a user ID and a password corresponding to the user ID. When a user ID registered in the SFL database 19 and a password corresponding to the user ID are input via the user IF 16 in the login process, the controller 11 performs various processes assuming that the MFP 10 is in a login state corresponding to the input user information. For example, when the user ID "user A" and the corresponding password are input, the controller 11 performs various processes assuming that the MFP 10 is in a login state corresponding to the input "user A". The user information registered in the SFL database 19 can also be said to be user information of a user permitted to log in to the MFP 10. The login state corresponding to the user information is also referred to as a state in which the user indicated by the user information is logged in. The login state corresponding to "user A" is also referred to as a state in which "user A" is logged in. The user indicated by the user information when the user indicated by the user information is in a logged-in state is also referred to as a "logged-in user". The user ID and password in the login process may be input by bringing an ID card corresponding to the user ID registered in SFL database 19 close to or into contact with MFP 10. Information used in the login process may be stored in an area of ​​memory 12 other than SFL database 19. In this case, controller 11 may refer to that area in memory 12 in the login process and in the process of FIG.

[0045] Next, a process will be described that the controller 11 executes when an instruction to execute a pull scan is received from the PC 40. First, a process will be described in which a "user A" executes a pull scan by operating the PC 40 in a state where no login has been made to the MFP 10, i.e., in "Public Mode."

[0046] FIG. 8 is a flowchart for explaining the procedure of the process executed by the controller 11 in S12. In S30, the controller 11 determines whether the execution of pull scan is enabled or disabled in the MFP 10. In this example, assuming that the pull scan is enabled (S31: YES), the controller 11 proceeds to S32 and executes a user authentication necessity determination process. By this user authentication necessity determination process, the controller 11 determines whether user authentication is required for an instruction to execute a pull scan by using a restriction setting value corresponding to a push scan in "Public Mode". Note that, if the pull scan is disabled in the MFP 10 (S31: NO), the controller 11 proceeds to S41 and notifies the PC 40 that the pull scan cannot be executed. That is, if the pull scan is disabled in the MFP 10, the pull scan is not executed regardless of who is logging in to the MFP 10. Information indicating whether the pull scan is enabled or disabled is stored in the memory 12 separately from the SFL database 19.

[0047] Fig. 9 is a flowchart explaining the procedure of the process executed by the controller 11 in S32 of Fig. 8. First, in S50, the controller 11 refers to column 19A of the SFL database 19. Since the function "SFL" is set to enabled in the SFL database 19 shown in Fig. 5 (S51: YES), the process proceeds to S52 and refers to the restriction setting value corresponding to the function "scan" in "Public Mode" of the SFL database 19. In other words, the controller 11 refers to column 19B of the SFL database 19 to determine whether or not the restriction setting value indicates that push scanning in a non-logged-in state is to be restricted.

[0048] 5, the restriction setting value "restriction" indicating a restriction is registered for the function "scan" in "Public Mode" (S53: YES), so the process proceeds to S54. In S54, the controller 11 sets that user authentication is required for an instruction to execute a pull scan. For example, the controller 11 sets the necessity determination flag to a value indicating that user authentication is required.

[0049] The controller 11 proceeds to S33 in FIG. 8, and because the necessity determination flag is set to a value indicating that user authentication is necessary, that is, because user authentication is necessary (S33: YES), the controller 11 proceeds to S34, and issues a GET request to the PC 40 to request user information required for user authentication. When the PC 40 accepts the request for user information from the MFP 10, the PC 40 transmits response data including user information of the user operating the PC 40 to the MFP 10. Specifically, the user information is a user ID and a password. In this case, the PC 40 transmits response data including user information of "user A". The PC 40 may transmit response data including user information of the user logged in to the PC 40. The PC 40 may transmit response data including user information input when the user logged in to the PC 40.

[0050] It should be noted that if the PC 40 does not transmit user information in response to the GET request from the MFP 10, the user authentication process in S36, which will be described later, cannot be executed. Therefore, if the controller 11 does not receive user information from the PC 40 (S35: NO), the controller 11 proceeds to S41 and notifies the PC 40 that the scan process (pull scan) cannot be executed.

[0051] Here, assuming that the controller 11 has received user information from the PC 40 (S35: YES), the process proceeds to S36 and executes user authentication processing. FIG. 10 is a flowchart explaining the procedure of the processing executed by the controller 11 in S36. First, in S60, the controller 11 checks whether the user information received from the PC 40 (information indicating user A in this example) is registered in the SFL database 19 as information to be used in the login process. As shown in FIG. 5, the SFL database 19 has user information registered therein relating to at least "user A" and "user B."

[0052] Since the user information received from the PC 40, i.e., the user ID and password, are registered in the SFL database 19 (S61: YES), the controller 11 proceeds to S62 and sets that the user authentication has been successful. For example, the controller 11 sets an authentication flag, which indicates whether the user authentication has been successful, to a value indicating success.

[0053] If the user information received from PC 40 in S61 is not registered in the SFL database 19 (S61: NO), the controller 11 proceeds to S63 and sets that the user authentication has failed. The controller 11 sets the authentication flag to a value indicating failure. Then, since the user authentication has failed in S37 of Fig. 8 (S37: NO), the controller 11 proceeds to S41 and notifies PC 40 that the scan process cannot be executed.

[0054] In this example, since the user authentication is successful in S37 of Fig. 8 (S37: YES), the controller 11 proceeds to S38 and executes a scan permission confirmation process. Fig. 11 is a flowchart for explaining the procedure of the process executed by the controller 11 in S38.

[0055] In S70, the controller 11 determines whether or not the MFP 10 is in a logged-in state, that is, whether or not the MFP 10 is in "Public Mode." In this example, since the MFP 10 is in "Public Mode" (S70: NO), the process proceeds to S74.

[0056] In S74, the controller 11 refers to the restriction setting value of the function "scan" for the user who has been successfully authenticated in S36, as already described. In this example, the restriction setting value "restricted" indicating a restriction is registered for the function "scan" corresponding to "user A" in column 19C of the SFL database 19. Therefore, since the function "scan" is restricted for "user A" in S75 (S75: YES), the controller 11 proceeds to S73 and sets a flag indicating that the start of scanning is not permitted.

[0057] 8, the controller 11 determines that a flag is set indicating that the start of scanning is not permitted, that is, scanning processing is not permitted (S39: NO), so the controller 11 proceeds to S41 and notifies the PC 40 that pull scanning cannot be performed. Since restrictions on push scanning are set for "User A," pull scanning is restricted even if authentication is successful in the user authentication processing in S36. Then, the controller 11 ends the processing in FIG. 8.

[0058] Next, a process will be described in a case where "User A" operates the PC 40 to execute a pull scan while "User A" is logged in to the MFP 10. In this example, the controller 11 also executes the processes of S30 to S37 in FIG. 8, which have already been described. In the user authentication necessity determination process of S32, the controller 11 determines that push scanning in "Public Mode" is restricted, and determines in S33 that user authentication is required (S33: YES). Then, on the condition that the user authentication is successful (S37: YES), the controller 11 executes the scan permission confirmation process in S38.

[0059] 11, since "user A" is logged in (S70: YES), the controller 11 proceeds to S71 and determines whether the user who requested the pull scan matches the logged-in user. Specifically, the controller 11 compares the user information used in the user authentication process in S36, already described, with the user information of the logged-in user to determine whether the users match. That is, the controller 11 determines whether the user who requested the start of a pull scan by operating the PC 40 matches the user who is logged in to the MFP 10.

[0060] If the controller 11 determines that the users match (S72: NO), the process proceeds to S74. In S74, the controller 11 determines whether or not a restriction is set on the function "scan" for the user whose user authentication in S36 was successful. Since the function "scan" is restricted for user A whose user authentication was successful in the SFL database 19 (S75: YES), the controller 11 proceeds to S73 and does not permit the start of scan processing (pull scan). The controller 11 proceeds to S39 in Fig. 8, and since scan processing is not permitted (S39: NO) as already explained, the process proceeds to S41 and notifies the PC 40 that pull scan cannot be executed.

[0061] 11, if the controller 11 determines that the users do not match (S72: NO), the process proceeds to S73 and does not permit the start of the scan process (pull scan). Therefore, since the scan process is not permitted (S39: NO) in FIG. 8, the controller 11 proceeds to S41 and notifies the PC 40 that the pull scan cannot be executed.

[0062] Next, a process will be described in which "User B" operates the PC 40 to perform a pull scan in "Public Mode" when the user is not logged in to the MFP 10. In the user authentication necessity determination process of S32, the controller 11 determines that push scanning in "Public Mode" is restricted, and determines in S33 that user authentication is required (S33: YES). Then, on condition that the user authentication is successful (S37: YES), the controller 11 executes a scan permission confirmation process in S38.

[0063] 11 is in "Public Mode" (S70: NO), the controller 11 proceeds to S74. In S74, the controller 11 refers to the restriction setting value corresponding to the function "scan processing" in the SFL database 19 for user B, whose user authentication was successful. In this example, "permitted" is registered as the restriction setting value corresponding to the function "scan" for "user B" in column 19D of the SFL database 19. Therefore, since the function "scan" is not restricted (S75: NO), the controller 11 proceeds to S76 and sets a flag indicating that scanning start is permitted.

[0064] In S39 of Fig. 8, the controller 11 sets a flag indicating that scanning is permitted, i.e., scanning is permitted (S39: YES), so the controller 11 proceeds to S40 and executes scanning (pull scanning). That is, since no restrictions are set on push scanning for "user B," the controller 11 executes pull scanning on the condition that authentication is successful. Then, the controller 11 ends the processing of Fig. 8.

[0065] Next, a process will be described in which "user B" operates the PC 40 to execute a pull scan while logged in to the MFP 10. In the user authentication necessity determination process of S32, the controller 11 determines that push scanning in "Public Mode" is restricted, and determines in S33 that user authentication is necessary (S33: YES). Then, on condition that the user authentication is successful (S37: YES), the controller 11 executes a scan permission confirmation process in S38. Since "user B" is logged in at S70 in FIG. 11 (S70: YES), the controller 11 proceeds to S71 and determines whether or not the user who operated the PC 40 to request a pull scan matches the logged-in user of the MFP 10.

[0066] If the controller 11 determines that the users match (S72: NO), the process proceeds to S74, where it determines whether or not a restriction has been set for the function "scanning" for the user whose user authentication has succeeded. As already explained, since the restriction setting value for the function "scanning" for "user B" in the SFL database 19 is "permitted" (S75: NO), the controller 11 proceeds to S76, where it permits the start of scanning (pull scanning). The controller 11 proceeds to S39 in Fig. 8, and since scanning is permitted (S39: YES) as already explained, the controller 11 proceeds to S40, where it executes a pull scan, and ends the process in Fig. 8.

[0067] 11, if the controller 11 determines that the users do not match (S72: NO), the process proceeds to S73, and does not permit the start of scan processing (pull scan). That is, even if user authentication for "user B" is successful and the restriction setting value for the function "scan" for "user B" in the SFL database 19 is "permitted," if the users do not match, pull scan is not permitted. Therefore, since scan processing is not permitted (S39: NO) in FIG. 8, the controller 11 proceeds to S41, and notifies the PC 40 that pull scan cannot be executed.

[0068] Next, an example of a case where a pull scan is executed when a restriction setting value "Allowed" that does not indicate a restriction on the function "Scan" in "Public Mode" in the column 19B is registered, unlike the SFL database 19 shown in Fig. 5. In this example, the controller 11 also executes the processes of S30 and S31 in Fig. 8 already described.

[0069] In S32, the controller 11 executes a process for determining whether user authentication is required. In S51 of Fig. 9, since the function "SFL" is enabled "ON" in the SFL database 19 (S51: YES), the controller 11 proceeds to S52 and refers to the restriction setting value for the function "scan" in "Public Mode". In this example, since the restriction setting value "permitted" is registered for the function "scan" in "Public Mode" in the SFL database 19 (S53: NO), the controller 11 proceeds to S55. In S55, the controller 11 sets a flag indicating that user authentication is not required for an instruction to execute a push scan.

[0070] 8, since user authentication is not required (S33: NO), the controller 11 proceeds to S40 and executes the scan process (push scan) as described above. That is, in this example, since push scan is not restricted in "Public Mode", pull scan is not restricted for anyone.

[0071] Next, an example will be described in which the function "SFL" is set to "OFF", i.e., disabled, in the SFL database 19. In S32, the controller 11 executes a user authentication necessity determination process. In S50 of FIG. 9, the controller 11 refers to the setting value of the function "SFL" in column 19A of the SFL database 19, i.e., "ON", which is enabled, or "OFF", which is disabled. In this example, since the function "SFL" is set to "OFF", which is disabled, in the SFL database 19 (S51: NO), the process proceeds to S55, where it is set that user authentication is not required for an instruction to perform a push scan. The controller 11 sets the necessity determination flag to a value indicating that user authentication is not required.

[0072] 8, since user authentication is not required (S33: NO), the controller 11 proceeds to S40 and executes the scan process. That is, in this example, since the function "SFL" is disabled, the pull scan is not restricted to anyone.

[0073] The present embodiment described above can provide the following advantages. When the controller 11 of the MFP 10 receives an instruction to execute a pull scan, it determines whether or not user authentication is required based on the restriction setting value set for push scan. If the controller determines that user authentication is not required, it executes a pull scan without requiring user authentication. On the other hand, if the controller determines that user authentication is required, it executes a pull scan if user authentication is successful, and does not execute a pull scan if user authentication fails. This makes it possible to determine security for pull scan in accordance with the restrictions already set for push scan when an instruction to execute a pull scan is received. As a result, it is possible to strike a balance between security and user convenience.

[0074] When the controller 11 receives an instruction to execute a pull scan from the PC 40, if the restriction setting value "restricted" is registered in the SFL database 19 for the function "scan" in "Public Mode", the controller 11 determines that user authentication is required, and if the restriction setting value "permitted" is not registered for the function "scan" in "Public Mode", the controller 11 determines that user authentication is not required. In this way, if a restriction is set for push scan when the user is not logged in, a restriction is also set for pull scan, thereby making it possible to prevent a difference in security between push scan and pull scan.

[0075] When the controller 11 determines that user authentication is required because the restriction setting value "restricted" is registered for the function "scan" in "Public Mode" in the SFL database 19, if the restriction setting value "permitted" is registered for the push scan of the logged-in user and the conditions for successful user authentication are met, the controller 11 executes a pull scan. On the other hand, if the restriction setting value "restricted" is registered for the push scan of the logged-in user, the controller 11 restricts, i.e., does not execute, the pull scan even if the conditions for successful user authentication are met. In this way, when it is set to restrict push scan for a specific user, even if authentication is successful for this user, by restricting pull scan, it is possible to prevent a difference in security level between push scan and pull scan.

[0076] When the controller 11 receives an instruction to execute a pull scan from the PC 40 and determines that user authentication is required, if the limit setting value "Allowed" is registered in the SFL database 19 for the function "Scan" for the user indicated by the user information, and the conditions for successful user authentication are met, the controller 11 executes a pull scan. On the other hand, if the limit setting value "Restricted" is registered in the SFL database 19 for the function "Scan" for the user indicated by the user information, the controller 11 restricts the pull scan even if the conditions for successful user authentication are met. This makes it possible to execute user authentication using the user information included in the instruction to execute a pull scan.

[0077] (Modification of the first embodiment) In the above embodiment, the controller 11 requires user authentication for pull scan if the limit setting value "LIMIT" is registered in the SFL database 19 for the function "Scan" in "Public Mode", i.e., for push scan in a non-logged-in state (S53: YES). Alternatively, the controller 11 may require user authentication for pull scan if the limit setting value "LIMIT" is registered for the function "Scan" corresponding to all registered users in the SFL database 19 referred to in S52 (S53: YES). Furthermore, the controller 11 may require user authentication for pull scan if the limit setting value "LIMIT" is registered for the function "Scan" for a predetermined specific user in the SFL database 19 referred to in S52 (S53: YES).

[0078] The controller 11 may execute the user authentication process in S36 and the scan permission confirmation process in S38 in Fig. 8 as follows. In this example, in the user authentication process executed in S36, it is determined whether or not the user who operates the PC 40 matches the user who logged in to the MFP 10 (processing of S70 to 72 in Fig. 11). First, in the user authentication process executed in S36, the controller 11 checks whether or not the user information received from the PC 40 is registered in the memory 12 as an authentication target in S60. If the user information is registered as an authentication target (S61: YES), the controller 11 determines whether or not the user has already logged in to the MFP 10 in S70 described in Fig. 11. If the user has already logged in to the MFP 10 (S70: YES), the controller 11 proceeds to S71 and determines whether or not the user who requested the pull scan matches the logged-in user. If the controller 11 determines that the users match (S72: YES), the process proceeds to S62 (FIG. 10), sets a flag indicating that the user authentication has been successful, and proceeds to S37. If the controller 11 determines that the user has not yet logged in (S70: NO), the process proceeds to S62, sets a flag indicating that the user authentication has been successful, and proceeds to S37. On the other hand, if the controller 11 determines that the users do not match (S72: NO), the process proceeds to S63, sets a flag indicating that the user authentication has failed, and proceeds to S37.

[0079] When the controller 11 determines that the user authentication has been successful in S37 of FIG. 8 (S37: YES), the process proceeds to S38 and performs a scan permission confirmation process. In the scan permission confirmation process performed in S38, the processes of S70 to S72 that have already been performed in the user authentication process in S36 are not performed. Specifically, in S74, the controller 11 refers to the restriction setting value of the function "scan process" corresponding to the user whose user authentication has been successful. In S75, if the restriction setting value "restricted" is registered in the SFL database 19 for the function "scan" of the user whose user authentication has been successful (S75: YES), the controller 11 proceeds to S73 and does not permit the start of the scan process (pull scan). On the other hand, if the restriction setting value "permitted" is registered in the SFL database 19 for the function "scan" of the user whose user authentication has been successful (S75: NO), the controller 11 proceeds to S76 and permits the start of the pull scan.

[0080] (Other embodiments) The reading device is not limited to the above-described embodiment, and various modifications are possible without departing from the spirit of the invention. In the above embodiment, when "Secure Function Lock" is selected on the Web page 20 shown in FIG. 3, the restriction setting screen 30 shown in FIG. 4 is used to set a restriction setting value indicating a restriction on each function. Alternatively, when the check box 24C of the item "Active Directory Authentication" or the check box 24D of "LDAP Authentication" is checked on the Web page 20 shown in FIG. 3, the restriction setting screen 30 shown in FIG. 4 may be used to set a restriction setting value indicating a restriction on each function, and the processes shown in FIGS. 6 to 11 may be executed. When the check box 24C is checked and "Active Directory Authentication" is enabled, the controller 11 may perform login authentication to the MFP 10 based on authentication information stored in an Active Directory (registered trademark) server. The controller 11 may also store a restriction setting value in the Active Directory server and use it in the processes shown in FIGS. 6 to 11. When the check box 24D is checked and "LDAP Authentication" is enabled, the controller 11 may perform login authentication to the MFP 10 based on authentication information stored in an LDAP (abbreviation for Lightweight Directory Access Protocol) server. Furthermore, controller 11 may store the limit setting value in an LDAP server and use it in the processes of Figures 6 to 11. Furthermore, the authentication information and the limit setting value may be stored in different storage units. For example, controller 11 may perform login authentication to MFP 10 based on authentication information stored in a server, store the limit setting value in SFL database 19 in memory 12, and use it in the processes of Figures 6 to 11.

[0081] In the above embodiment, the limit setting value for the function "SFL" is set using the Web page (home screen 20) transmitted from the controller 11 of the MFP 10. Alternatively, the limit setting value for the function "SFL" may be set by operating the user IF 16 of the MFP 10.

[0082] Although the MFP 10 has been described as an example of the reading device, the reading device may be a device capable of executing only the function "scanner." [Explanation of symbols]

[0083] 10...MFC, 11...controller, 15...scanner, 16...user IF, 18...communication IF, 19...SFL database, 40...PC

Claims

1. a user interface; a scanner; and a controller, the controller comprising: It is possible to execute push scanning, which causes the scanner to read an original document in response to an execution instruction corresponding to an operation on the user interface, and pull scanning, which causes the scanner to read an original document in response to an execution instruction from an external device; The controller: setting a limit setting value regarding the limit of the push scan; When an instruction to execute the push scan is received via the user interface, the push scan is restricted in accordance with the restriction setting value, The controller: When an instruction to execute the pull scan is received from an external device, it is determined whether or not authentication is required based on the restriction setting value; When it is determined that the authentication is not required, the pull scan is performed without requiring the authentication. When it is determined that the authentication is required, if the authentication is successful, the pull scan is executed, and if the authentication is unsuccessful, the pull scan is not executed. A reading device having a configuration.

2. The controller: The restriction setting value can be set in association with each user, and the restriction setting value can also be set in association with a non-logged-in state, The controller: Once you’re logged in, If the restriction setting value indicates that the push scan is to be restricted for the logged-in user, the push scan is restricted in accordance with the restriction setting value; If the restriction setting value does not indicate that the push scan should be restricted for the logged-in user, the push scan is not restricted according to the restriction setting value. If you are not logged in, If the restriction setting value indicates that the push scan in a non-logged-in state is to be restricted, the push scan is restricted in accordance with the restriction setting value; If the restriction setting value does not indicate that the push scan is to be restricted when the user is not logged in, the push scan is not restricted according to the restriction setting value. When an instruction to execute the pull scan is received from an external device, If the restriction setting value indicates that the push scan is to be restricted when the user is not logged in, the authentication is determined to be required; If the restriction setting value does not indicate that the push scan is restricted when the user is not logged in, it is determined that the authentication is not required.

2. The reading device according to claim 1, wherein said reading device has a configuration.

3. The controller: Regardless of whether the user is logged in or not, when the user receives an instruction to execute the pull scan from an external device, If the restriction setting value indicates that the push scan is to be restricted when the user is not logged in, the authentication is determined to be required; If the restriction setting value does not indicate that the push scan is restricted when the user is not logged in, it is determined that the authentication is not required.

3. The reading device according to claim 2, wherein said reading device has a configuration.

4. The controller: While logged in, the command to execute the pull scan is accepted, When it is determined that the authentication is required because the restriction setting value indicates that the push scan in a non-logged-in state is to be restricted, If the restriction setting value does not indicate that the push scan of the logged-in user is to be restricted, the pull scan is executed if the condition for successful authentication is satisfied; When the restriction setting value indicates that the push scan of the logged-in user is to be restricted, the pull scan is restricted even if the condition for successful authentication is satisfied.

4. The reading device according to claim 3, further comprising:

5. The controller: The limit setting value can be set in association with each user, The controller: The authentication is performed based on user information included in the instruction to perform the pull scan; When an instruction to execute the pull scan is received from an external device and it is determined that the authentication is required, If the restriction setting value does not indicate that the push scan is restricted for the user indicated by the user information, the pull scan is executed if the condition for successful authentication is satisfied. When the restriction setting value indicates that the push scan is to be restricted for the user indicated by the user information, the pull scan is restricted even if the condition for successful authentication is satisfied.

2. The reading device according to claim 1, wherein said reading device has a configuration.

6. The initial pull scan instruction from the external device does not include the user information, The controller: When it is determined that the authentication is required for the execution instruction of the pull scan, a request is made to an external device for an execution instruction of the next pull scan including the user information; performing the authentication based on user information included in the execution instruction for the next pull scan; 6. The reading device according to claim 5, wherein said reading device has a configuration.

7. a user interface; a scanner; and a controller, the controller comprising: In response to an execution instruction, a scan can be executed to cause the scanner to read an original document; The controller: When an instruction to execute the scan is received, the scan can be restricted according to a restriction setting value; The controller: When an instruction to execute a pull scan, which is an instruction to execute the scan from an external device, is received, if a restriction setting value corresponding to restricting the scan is set, authentication is performed, if the authentication is successful, the pull scan is executed, and if the authentication is unsuccessful, the pull scan is restricted. when a push scan execution instruction, which is an instruction to execute the scan in response to an operation on the user interface, is received, if a restriction setting value corresponding to restricting the scan is set, restricting the push scan without performing the authentication. A reading device having a configuration.

Citation Information

Patent Citations

  • Device for producing high-purity distilled water

    JP1991000182A