printer

Abstract

To provide a printer having different print authorities for each user which can perform appropriate printing processing on the users.SOLUTION: An MFP 1 performs processing (S49) of specifying whether or not a user name 85 associated with a received print job 75 is registered in an authentication DB 73, and processing (S53) of specifying print authority of the user name 85 associated with the print job 75. The MFP 1 performs storage (S55) of the print job 75, and discard (S51) of the print job 75, according to a result of specification processing. The MFP 1 performs the print job 75 associated with a long-in user, according to log-in operation.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] The present invention relates to a printing device in which the printing authority differs for each user. Place This is regarding. [Background technology]

[0002] Conventionally, there are printing devices that execute processing based on user identification information included in a received print job (for example, Patent Document 1, etc.). The printer device described in Patent Document 1 executes printing as normal when a pre-registered user identifier is set in the print job data. If the user identifier set in the print job data is not registered, printing is not executed. Also, if a user identifier is not set in the print job data, the printer device executes the print job according to a pre-set operation mode. [Prior art documents] [Patent documents]

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

[0004] In the above-mentioned printer device, the process content is changed depending on whether or not the user can be registered. However, in this type of printer device, in addition to registering the user, if the authority of the user who can execute the printer is set in advance, for example, it is necessary to execute the process according to the authority of the set user. In addition, in the above-mentioned printer device, if the identification information of a previously registered user is set in the print job data, printing is executed when the print job data is received, so that the printed matter is discharged even if another user is operating the printer.

[0005] This specificationThe present invention has been proposed in view of the above-mentioned problems, and aims to provide a technique that can execute appropriate print processing for each user in a printing device in which printing authority differs for each user. [Means for solving the problem]

[0006] Disclosed herein The printing device includes a storage unit that stores authentication data in which user identification information for identifying a user and print permission information regarding whether or not a print process can be executed in response to a command from the user according to the user identification information are associated with each other, a communication unit, an operation unit that accepts operations by the user, a printing unit, and a control unit. The control unit performs a reception process of receiving a print job associated with the user identification information via the communication unit, a first determination process of determining whether or not the user identification information associated with the print job received by the reception process is registered in the authentication data, and a second determination process of determining whether or not the user identification information associated with the print job is registered in the authentication data. a second identification process for identifying the printability information in the authentication data corresponding to the printing information; a storage process for storing in the memory unit the print job for which a first identification result was obtained based on the results of the first identification process and the second identification process, and not storing in the memory unit the print job for which a second identification result different from the first identification result was obtained; an acceptance process for accepting a login operation using the user identification information by the operation unit; and a first printing process for printing by the printing unit an image related to the print job stored in the memory unit, which is the print job associated with the user identification information accepted in the login operation.

[0007] Effect of the Invention

[0008] Disclosed hereinAccording to the technology, whether or not to save a print job in a storage unit is controlled according to registration information regarding whether or not user identification information is registered and print permission information regarding printing authority. Therefore, it is possible to prevent unnecessary print jobs from being saved in the storage unit according to the user's registration status and user authority. In addition, the print job saved in the storage unit is printed when a login operation of the user is accepted. In other words, since the print job is not discharged as a printout until the user logs in, it is possible to prevent other users from viewing the printout, and appropriate printing processing can be provided to the user.

[0009] The technology disclosed in this specification can be realized in various forms, for example, the function of the above-mentioned device. Noh To achieve this method, The present invention can be realized in the form of a computer program, a recording medium on which the computer program is recorded, or the like. [Brief description of the drawings]

[0010] [Figure 1] FIG. 2 is a block diagram showing the electrical configuration of the MFP. [Diagram 2] FIG. 13 is a diagram showing data stored in an authentication DB. [Diagram 3] FIG. 2 is a diagram showing the contents of a print job written in PJL. [Figure 4] FIG. 11 is a sequence diagram showing state transitions of a screen displayed on a touch panel of the MFP. [Diagram 5] 13 is a flowchart showing the contents of a main process. [Figure 6] 13 is a flowchart showing the contents of a printing / storage process. [Figure 7] 13 is a flowchart showing the contents of a printing / storage process. [Figure 8] 13 is a flowchart showing the contents of a process after an icon is pressed. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] below, markAn MFP1, which is an embodiment of a printing device, will be described with reference to Fig. 1. Fig. 1 is a block diagram showing the electrical configuration of the MFP1.

[0012] (1. MFP Configuration) The MFP1 is a multifunction machine having a printing function, a copying function, a scanning function, and a fax function. As shown in Fig. 1, the MFP1 has a CPU 12, a RAM 13, a memory 15, a printing unit 16, an image reading unit 17, a fax communication unit 18, a user interface 20, and a network interface 24. The CPU 12 and the like are connected to each other via a bus 11. The MFP1 also has a power supply 25 that supplies power from a commercial power source. The power supply 25 has a power cord and a power supply circuit (bridge diode, smoothing circuit, etc.), generates DC power from the commercial power source, and supplies power to each unit of the MFP1 via a power line.

[0013] Memory 15( Note An example of the memory unit is a non-volatile memory such as NVRAM. Note The memory unit is not limited to NVRAM, but may be a volatile RAM, a ROM, a HDD, an external storage device (such as a USB memory) connected to the MFP1, or a combination of these. Note The memory unit may be a file server or the like connected via the network interface 24. The memory unit may also be a computer-readable storage medium. A computer-readable storage medium is a non-transitory medium. In addition to the above examples, non-transitory media also include recording media such as CD-ROMs and DVD-ROMs. A 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 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] The memory 15 stores various programs such as a control program 71. The control program 71 is, for example, a program that comprehensively controls each part of the MFP 1. The CPU 12 executes the control program 71 and controls each part connected by the bus 11 while temporarily storing the executed processing result in the RAM 13. The control program 71 also includes an EWS (Embedded Web Server) program that functions as a Web server. The CPU 12 executes the EWS program to make the MFP 1 function as a Web server. An authentication DB (abbreviation of database) 73 is also built in the memory 15 of this embodiment. As described later, the authentication DB 73 is data that associates, for example, the user name of a login user who can log in to the MFP 1, the authority of each user, and the email address of each user (see FIG. 2). In the following description, the MFP 1 that executes the control program 71 and the like by the CPU 12 may be simply described as a device name. For example, the statement "MFP 1 accepts operational input to touch panel 21" may mean "MFP 1 executes control program 71 in CPU 12 to control touch panel 21, thereby accepting operational input to touch panel 21."

[0015] The printing unit 16 has a head 161 and an ink cartridge 162. The ink cartridge 162 contains ink. The head 161 ejects the ink supplied from the ink cartridge 162 onto a sheet (such as paper or an OHP). In this way, the printing unit 16 prints an image on the sheet by inkjet printing based on the control of the CPU 12. mark The printing unit 16 is not limited to a configuration that performs printing using an inkjet method, and may be configured to perform printing using another method, for example, an electrophotographic method.

[0016] The image reading unit 17 includes an unillustrated document table and an image sensor such as a CIS (Contact Image Sensor) or a CCD (Charge-Coupled Device). The image reading unit 17 moves the CIS or the like relative to the document placed on the document table, reads the document, and generates image data. The FAX communication unit 18 transmits and receives FAX data to and from other facsimile devices via a telephone line.

[0017] The user interface 20 has operation buttons such as a touch panel 21 and a numeric keypad 22. The touch panel 21 includes, for example, a liquid crystal panel, a light source such as an LED that irradiates light from the rear side of the liquid crystal panel, and a touch-sensitive film attached to the surface of the liquid crystal panel. The user interface 20 displays, for example, various setting screens and the operating state of the device on the touch panel 21 under the control of the CPU 12. The user interface 20 also transmits signals corresponding to operation inputs to the touch panel 21 and the numeric keypad 22 to the CPU 12. Note that the MFP 1 of this embodiment includes the touch panel 21 that serves both as a display unit and an operation unit, but is not limited thereto, and for example, hardware keys may be provided as an operation unit in addition to the display unit.

[0018] The network interface 24 is, for example, a LAN (Local Area Network) interface, and is connected to the router 29 via a LAN cable (not shown). For example, a plurality of PCs 41 and a mail server 43 are connected to the router 29 in this embodiment. A user operates the PC 41 to transmit a print job 75 from the PC 41 to the MFP1. The MFP1 executes a print process based on the print job 75 received from the PC 41. The MFP1 also processes an email received from the mail server 43 as the print job 75, and executes printing of a file attached to the email, etc. Note that a device that transmits the print job 75 to the MFP1 is not limited to the PC 41 or the mail server 43, and may be, for example, a mobile terminal capable of wireless communication with the MFP1. Also, a network that connects the MFP1, the PC 41, and the mail server 43 is not limited to a wired LAN, and may be, for example, a wireless LAN or a WAN (including the Internet).

[0019] Next, the authentication DB 73 stored in the memory 15 will be described. 2 shows an example of data stored in the authentication DB 73. As shown in FIG. 2, for example, a user name 111, a PIN number 113, a print authority flag 114, a scan authority flag 115, a copy authority flag 116, and an email address 117 are associated with each other and registered as one record in the authentication DB 73. In the authentication DB 73 of this embodiment, five users, namely, a public user (PUBLIC), "inoue", "kato", "hayashi", and "minami", are registered as users. The user name 111 and the PIN number 113 are given to each user by, for example, a system administrator who manages the MFP 1. Each user performs a login operation of the MFP 1 using the user name 111 and the PIN number 113.

[0020] Furthermore, the print permission flag 114, scan permission flag 115, and copy permission flag 116 are flag values ​​that set whether to grant each user permission to execute the print function, scan function, and copy function of the MFP 1. For example, in the example shown in Fig. 2, a public user and a user name "inoue" have print permission and scan permission, but do not have copy permission.

[0021] In addition, in each record, an email address 117 is set in association with the user name 111, the PIN number 113, etc. The MFP 1 of this embodiment is capable of printing an attachment to an email received from the email server 43 as described above.

[0022] The system administrator adds or deletes users, changes the authority, registers the email address 117, and so on, as shown in FIG. 2, in the authentication DB 73. For example, the MFP 1 of this embodiment is capable of accepting settings for the authentication DB 73 through the EWS. For example, the system administrator operates a web browser on the PC 41 to access the EWS of the MFP 1. The MFP 1 executes settings for the authentication DB 73 based on information accepted on the web page of the EWS. Note that the method of editing the authentication DB 73 is not limited to the method using the web server described above. For example, the MFP 1 may edit the authentication DB 73 in response to an operation input to the touch panel 21. Also, the data items of the authentication DB 73 shown in FIG. 2 are merely examples, and the authentication DB 73 may have, for example, a flag value that grants authority to execute a FAX function, or a value that limits the number of prints for each user.

[0023] (2. Secure printing function and stored printing function) The MFP 1 of this embodiment has a security printing function and an accumulation printing function. In the following description, as shown in Fig. 1, a print job 75 for executing the security printing function is referred to as a security printing job 75A, and a print job 75 for executing the accumulation printing function is referred to as an accumulation printing job 75B.

[0024] When the accumulated print function receives print job 75 with user name 85 set from PC 41 or the like, it stores the received print job 75 in memory 15 of MFP 1 as accumulated print job 75B. When a user name and PIN number are input via touch panel 21 of MFP 1, they are collated with user name 111 and PIN number 113 (see FIG. 2) registered in authentication DB 73. If the collation results in a match with user name 111 and PIN number 113 registered in authentication DB 73, the user who performed the input operation logs in to MFP 1. When the user logs in to MFP 1, accumulated print job 75B associated with the logged-in user's user name 85 is retrieved from memory 15 and printing begins.

[0025] The accumulated print function is set by a system administrator operating a Web browser on the PC 41 and accessing the EWS of the MFP 1. When the accumulated print function is set to be executed, the MFP 1 executes each process for accumulated print, which will be described in this embodiment, for a print job 75 received from an external device such as the PC 41. When the accumulated print function is set not to be executed, the MFP 1 starts print processing without storing the print job 75 in the memory 15 when it receives the print job 75 from an external device such as the PC 41. In this case, not storing the print job in the memory 15 means that a trigger for starting printing is not provided separately, and does not include processing for temporarily storing the print job in the memory 15 for printing processing. In addition, the printer driver executed by the PC 41 sets the user account of the user for logging in to the PC 41 in the print job 75 and transmits it to the MFP 1. In addition, the same character string is used for the user account for logging in to the PC 41 and the user name 111 registered in the authentication DB 73.

[0026] The secure printing function is a function in which a print job 75 associated with a password is temporarily stored in memory 15 of MFP 1, and the user operates touch panel 21 of MFP 1 to input the password associated with print job 75, thereby executing printing of print job 75. When executing the secure printing function, PC 41 transmits to MFP 1 a security printing job 75A in which a job name 81 and a password 83 are set. Job name 81 is, for example, a name of print job 75 given by a printer driver executed by PC 41. Password 83 is, for example, information (such as numbers or letters) set by the user on a setting screen of the printer driver executed by PC 41 and associated with security printing job 75A.

[0027] The stored printing function and the secure printing function are common in that a print job 75 received from outside is stored in memory 15, and printing is started when the user inputs authentication information on the MFP 1. However, the authentication information to be input is a password 83 associated with the print job 75 in the secure printing function, whereas it is a PIN number 113 corresponding to a user name 111 registered in the authentication DB 73 in the stored printing function. Also, the print job 75 that starts printing is a print job 75 selected by the user in the security printing function, whereas it is all print jobs 75 to be printed in the stored printing function.

[0028] FIG. 3 shows a print job 75 described in PJL (Printer Job Language) as an example. Note that the contents of the data in FIG. 3 are only an example. As shown in FIG. 3, for example, the header of the print job 75 describes commands for setting variables (JOB_NAME, etc.) in the order of job name 81, user name 85, password 83, transmission time, and description language type. The MFP 1 changes the processing contents of the print job 75 based on the data set in the header of the received print job 75, for example. For example, when a valid value is set in the variable "JOB_PASSWORD" indicating the password 83, the MFP 1 determines that the password 83 is set in the received print job 75 and treats it as a job 75A for security printing. Also, for example, when a valid value is set in "PRINT_USER" indicating the user name 85, the MFP 1 determines that the user name 85 is set in the received print job 75. Note that for printer languages ​​other than PJL, the setting state of the user name 85, etc. can be detected by determining the contents defined in each language in the same manner.

[0029] FIG. 4 shows the state transition of the screen displayed on the touch panel 21 of the MFP1. S19 to S29 in FIG. 4 are processes related to a login operation to the MFP1. For example, after the MFP1 is powered on and executes the control program 71 to start the system, the MFP1 displays the standby screen 91 shown in the upper left of FIG. 4 on the touch panel 21 (see FIG. 1). The MFP1 displays function icons 93 for selecting a FAX function, a copy function, a scan function, etc., in the center of the standby screen 91. The MFP1 also displays a user display field 95 for displaying the currently selected user name in the upper left of the standby screen 91. When the power is turned on, since no one has logged in yet, the MFP1 displays in the user display field 95 on the standby screen 91 that a public user, which indicates a logout state, is selected. The MFP1 of this embodiment processes a print job 75 of a user not registered in the authentication DB 73 as the print job 75 of this public user. When standby screen 91 is displayed, functions (such as a scan function) according to the authority granted to the public user (see FIG. 2) can be executed. The MFP 1 displays a date and time field 97 indicating the current time and date in the lower right of standby screen 91. The MFP 1 also displays triangular icons 98 on both the left and right sides of standby screen 91, indicating that scrolling in the left and right directions is possible.

[0030] 4, when the user touches the user display field 95 displaying the public users, the MFP 1 displays a user selection window 109 on the touch panel 21. In the user selection window 109, user names 111 registered in the authentication DB 73 are displayed.

[0031] After displaying the user names 111 registered in the authentication DB 73 in the user selection window 109, when the user touches any of the user names 111 in the user selection window 109, for example, the user name 111 of "inoue" (S21), the MFP 1 displays a PIN number input window 121 for inputting the PIN number 113. The MFP 1 displays a numeric keypad 123 for inputting the PIN number 113 and a PIN number input field 124 in the PIN number input window 121. When the PIN number 113 is input in the PIN number input field 124 using the numeric keypad 123, the MFP 1 determines whether the input PIN number 113 matches the PIN number 113 associated with the user name 111 selected in the user selection window 109 (in this case, "1111" of "inoue" in FIG. 2) (S23). If the PIN numbers 113 match, the MFP 1 permits login. Although details will be described later, if stored print jobs 75B associated with the logged-in user are stored in memory 15 and the logged-in user has print authority, the MFP 1 prints all of the stored stored print jobs 75B (S23). Also, if print data of received e-mails associated with the logged-in user are stored in memory 15 and the logged-in user has print authority, the MFP 1 prints all of the stored print data of the received e-mails (such as attachments) (S23).

[0032] The MFP1 displays the second standby screen 91B after login. The MFP1 displays the name of the logged-in user (for example, "inoue") in a user display field 95 on the second standby screen 91B. In this state, the logged-in user can execute only functions permitted in the authentication DB 73. Therefore, the MFP1 restricts the execution authority of each user by restricting the functions after login based on the authority set in the authentication DB 73. For example, even if a user without copy authority touches the copy function icon 93, the function is not executed. Note that the MFP1 does not have to display the function icon 93 of a function for which the logged-in user does not have authority, i.e., cannot execute, on the second standby screen 91B.

[0033] When the user display field 95 is touched while the second standby screen 91B is displayed (S25), the MFP 1 displays a logout window 126. The MFP 1 displays a selection key 125 in the logout window 126 for selecting whether or not to execute logout. When the selection key 125 for "YES" instructing the execution of logout is touched (S27), the MFP 1 displays the standby screen 91 on the touch panel 21. This completes the logout. Furthermore, if a certain period of time has elapsed while the second standby screen 91B is displayed, the MFP 1 returns the display on the touch panel 21 to the standby screen 91 from the second standby screen 91B (S29). This certain period of time is, for example, 30 seconds to 1 minute.

[0034] (3. Operation of MFP1) Next, the operation of the MFP1 of this embodiment will be described with reference to Fig. 5 to Fig. 8. Fig. 5 shows the flow of main processing for processing a print job 75. For example, when the power is turned on, the MFP1 executes the control program 71 in the CPU 12 to start up the system, and then executes the main processing shown in Fig. 5. In the following explanation, the print processing based on the print job 75 will be mainly explained. As the print processing based on a received email can be executed in the same way as the print job 75, the explanation thereof will be omitted as appropriate.

[0035] Note that the sequence diagrams and flowcharts in this specification basically show the processing of the CPU 12 according to instructions written in a program (such as the control program 71). That is, the processing of "determination," "reception," "acquisition," "acceptance," "control," "setting," and the like in the following description represent the processing of the CPU 12. The processing by the CPU 12 also includes hardware control.

[0036] First, in S31 of FIG. 5, the CPU 12 of the MFP 1 confirms receipt of a print job 75. As described below, the CPU 12 executes S31 again after executing S41 and the like. Therefore, after starting the system, the CPU 12 periodically checks whether a print job 75 has been received. The CPU 12 determines whether a print job 75 has been received based on the confirmation result of S31 (S33). If the CPU 12 determines that the print job 75 has been received (S33: YES), it executes the print / storage process of S35. On the other hand, if the CPU 12 determines that the print job 75 has not been received (S33: NO), it executes S37. Note that, for example, if the CPU 12 receives multiple print jobs 75, it executes the processes from S31 onwards for the multiple print jobs 75 in the order in which they were received.

[0037] In S37, the CPU 12 determines whether a user has logged in. The CPU 12 determines that a user has logged in when the processes of S19 to S23 in FIG. 4 have been performed. In S37 and after, the CPU 12 executes the processes related to the accumulated printing from S19 in FIG. 4 described above. When the CPU 12 determines that a user has logged in (S37: YES), the CPU 12 determines whether there is an accumulated printing job 75B associated with the logged-in user among the accumulated printing jobs 75B accumulated in the memory 15 (S39). Specifically, when the user name 85 set in "PRINT_USER" among the accumulated printing jobs 75B accumulated in the memory 15 matches the user name 111 registered in the authentication DB 73 for the logged-in user, it determines that there is an accumulated printing job 75B associated with the logged-in user. Furthermore, if the print job 75 stored in memory 15 is a received email, and there is a print job 75 with a sender email address that matches the email address 117 registered in authentication DB 73, it is determined that there is a stored print job 75B associated with the logged-in user. When CPU 12 determines that there is a stored print job 75B for the logged-in user (S39: YES), it executes printing of the stored print job 75B by printing unit 16 (S41). In this case, printing of all print jobs stored in memory 15 is automatically started without requiring the user to select a job or enter a password. This eliminates the need for complicated operations by the user.

[0038] After executing S41, the CPU 12 executes the process from S31 again. If the user is not logged in in S37 (S37: NO), or if there is no stored print job 75B associated with the logged-in user in S39 (S39: NO), the CPU 12 executes the process from S31. Then, the CPU 12 confirms receipt of a new print job 75 in S31 and executes the process from S33 onward.

[0039] (3-1. Printing / Storage Processing) Next, the contents of the print / storage process in S35 in Fig. 5 will be described with reference to Fig. 6 and Fig. 7. When the print / storage process is executed, a newly received print job 75 is determined to exist in S33 in Fig. 5 (S33: YES). The CPU 12 executes the processes from S43 onward, treating this newly received print job 75 as the print job 75 to be processed. First, in S43, the CPU 12 checks whether a user name 85 and a password 83 are set in the print job 75 to be processed.

[0040] Next, in S45, the CPU 12 determines whether or not a password 83 is set for the print job 75 to be processed based on the confirmation result of S43. For example, if a valid value is set for the variable "JOB_PASSWORD" (see FIG. 3) in the print job 75, the CPU 12 determines that a password 83 is set for the print job 75 to be processed (S45: YES). If the CPU 12 determines that a password 83 is set for the print job 75 to be processed (S45: YES), it executes S46 in FIG. 7. If the CPU 12 determines that a password 83 is not set for the print job 75 to be processed (S45: NO), it determines whether or not a user name 85 is set for the print job 75 to be processed (S47).

[0041] For example, when a valid value is set in the variable "PRINT_USER" in the print job 75 (see FIG. 3), the CPU 12 determines that the user name 85 is set in the print job 75 to be processed (S47: YES) and executes S49. On the other hand, when the CPU 12 determines that the user name 85 is not set in the print job 75 to be processed (S47: NO), the CPU 12 discards the print job 75 to be processed without saving it in the memory 15 (S51). After executing S51, the CPU 12 ends the print / storage process. For example, depending on the type of printer driver, the user name 85 may not be assigned to the print job 75. Alternatively, some systems that transmit the print job 75 do not set the user name 85. For this reason, the MFP 1 may receive the print job 75 to which the user name 85 or password 83 is not set. Therefore, the CPU 12 of this embodiment discards the print job 75 to which the user name 85, etc. are not set. This makes it possible to prevent print jobs 75 for which no user name 85 or the like is set from being stored in memory 15 without being printed, which may cause a load on the storage area of ​​memory 15. Note that CPU 12 may print print jobs 75 for which no user name 85 or the like is set, without storing the print jobs in memory 15.

[0042] In addition, in S49, the CPU 12 judges whether the user name 85 set in the print job 75 to be processed is the user name 111 (see FIG. 2) registered in the authentication DB 73. As shown in FIG. 2, in the authentication DB 73 of this embodiment, four user names 111, such as "inoue", are registered, excluding "PUBLIC". Therefore, the CPU 12 accesses the authentication DB 73 in S49, and if the user name 85 set in the print job 75 to be processed corresponds to any one of the four user names 111, it judges that the user name is the user name 111 registered in the authentication DB 73 (S49: YES). In addition, if the print job 75 is an incoming email, it judges the sender's email address and the email address 117 registered in the authentication DB 73.

[0043] When the CPU 12 determines that the user name 85 of the print job 75 is the user name 111 registered in the authentication DB 73 (S49: YES), it determines whether the user is authorized to print (S53). As shown in FIG. 2, in the authentication DB 73 of this embodiment, the users with the user names 111 "inoue" and "hayashi" are authorized to print (see the print authority flag 114). Therefore, when the user name 85 of the print job 75 to be processed is "inoue" or "hayashi", the CPU 12 determines that the user has the authorization to print (S53: YES) and executes S55. Here, when the CPU 12 of this embodiment stores the print job 75 in the memory 15, for example, the storage area for storing the security print job 75A and the storage area for storing the stored print job 75B are different storage areas. In S55, the CPU 12 stores the print job 75 to be processed in the storage area of ​​the memory 15 for storing the stored print job 75B. The print job 75 stored in the memory 15 in S55 is printed as a stored print job 75B in S41 of Fig. 5. After executing S55, the CPU 12 ends the print / storage process.

[0044] Furthermore, when the CPU 12 determines in S53 that the user does not have the printing authority (S53: NO), it discards the print job 75 to be processed (S51). This prevents the print job 75 from continuing to be accumulated in the memory 15 because the user does not have the printing authority and cannot execute the accumulated printing, thereby preventing the storage area of ​​the memory 15 from being overloaded.

[0045] Furthermore, if the CPU 12 determines in S49 that the user name 85 of the print job 75 to be processed is not registered in the authentication DB 73 (S49: NO), the CPU 12 processes the print job 75 to be processed as a print job 75 of a public user (S57 in FIG. 7). In S57 in FIG. 7, the CPU 12 determines whether the public user in the authentication DB 73 has been granted printing authority.

[0046] As shown in FIG. 2, the public user in this embodiment can be set with a print authority. If the public user is given the print authority (see the print authority flag 114), the CPU 12 starts processing to print the print job 75 to be processed (S59). Therefore, the CPU 12 in this embodiment processes the print job 75 of the unregistered user as the print job 75 of the public user, and starts immediate printing processing without storing it. On the other hand, if the print authority is not set for the public user (S57: NO), the CPU 12 discards the print job 75 to be processed without storing it in the memory 15 (S61), and ends the print / storage processing. This makes it possible to enhance security by prohibiting printing by an unregistered user. In addition, it is possible to prevent the print job 75, which has a user name 85 but is set to an unregistered user name 85, from continuing to be stored in the memory 15 without being printed, thereby preventing the storage area of ​​the memory 15 from being overwhelmed. In addition, in FIG. 2, "OK (immediate printing)" is written as an example of the print authority of the public user. This explanation uses "(immediate printing)" to clarify that when a public user is granted printing authority in the stored printing function, printing is performed immediately without storage, but it is sufficient to set only "OK" as the registration in the authentication DB 73. Also, to allow the system administrator to easily understand what kind of printing process is being performed, a setting screen that shows "OK (immediate printing)" may be displayed when the stored printing function is set.

[0047] Further, in S59, the CPU 12 judges whether or not at least one of the conditions of the user being logged in and the print job 75 being executed is satisfied. When at least one of the conditions of the registered user being logged in and the print job 75 being executed is satisfied (S59: NO), the CPU 12 repeatedly executes the judgment process of S59. If the print job 75 with an unregistered user name 85 is executed during login or printing processing, there is a risk that the printed matter discharged to the paper output tray of the MFP 1 will be mixed. As a result, there is a risk that confidential documents, etc., will be seen or taken by other users. Therefore, the CPU 12 of this embodiment does not execute the print job 75 with an unregistered user name 85 during login or execution of the print job 75. This makes it possible to prevent the print job 75 with an unregistered user name 85 from being executed and the printed matter from being mixed, for example, while the user is logged in and operating the touch panel 21, or while the user is logged out but executing the print job 75.

[0048] Furthermore, when neither the condition of being logged in nor the print job 75 being executed is satisfied, i.e., when printing is not being executed in a logged out state (S59: YES), the CPU 12 judges whether a certain time has passed since the end of the previous print process (S63). If the next print process is started immediately after the end of the print process, there is a risk that the printed materials discharged from the MFP 1 will be mixed up. Therefore, the CPU 12 of this embodiment waits a certain time from the end of the print process, and then executes printing of the print job 75 to be processed. This more reliably prevents the user from mixing up the printed materials, and enhances security.

[0049] If a certain amount of time has passed since the previous print process was completed (S63: NO), the CPU 12 executes S67. If a certain amount of time has not passed since the previous print process was completed (S63: YES), the CPU 12 waits for a certain amount of time (S65) before executing S67. The wait time in S65 is, for example, the time required for the user to remove the previously printed matter from the paper output tray, and is, for example, 5 to 15 seconds.

[0050] In S67, the CPU 12 executes printing of the print job 75 to be processed, i.e., the print job 75 for which the unregistered user name 85 is set. This allows the print job 75 for which the unregistered user name 85 is set to be printed immediately without storage, using the printing authority of the public user. After executing S67, the CPU 12 ends the print / storage process.

[0051] Here, as shown in S29 of FIG. 4, when 30 seconds have elapsed while the second standby screen 91B after login is displayed, the MFP 1 of this embodiment returns the display of the touch panel 21 from the second standby screen 91B to the standby screen 91. Therefore, when logging out due to a timeout, it is highly likely that the above-mentioned certain time after the end of printing, which is 5 to 15 seconds, has elapsed. Therefore, when logout is based on a timeout, the CPU 12 starts printing (S67) without waiting for the certain time after logout (S63: NO). On the other hand, when logout is based on an operation on the touch panel 21, there is a possibility that the certain time has not elapsed since the end of the previous printing process. Therefore, the CPU 12 judges the certain time in S63, and if the certain time has not elapsed, it waits in S65.

[0052] 6, when the CPU 12 determines that the print job 75 to be processed has a password 83 set (S45: NO), it determines whether the print job 75 to be processed matches a predetermined condition (S46 in FIG. 7). Among the print jobs 75 to which the password 83 is set, there are, for example, 1) those for which the user name 85 is not set, 2) those for which the user name 85 is set and there is printing authority, 3) those for which the user name 85 is set and the user name 85 is not registered, and 4) those for which the user name 85 is set and there is no printing authority. The CPU 12 makes a judgment in S46 based on these conditions.

[0053] In the case of 1), the print job 75 is a print job 75 without a user name 85 and with a password 83 set, that is, a security printing job 75A to be subjected to security printing. Therefore, when the CPU 12 determines that the user name 85 is not set for the print job 75 of 1) (S46: NO), it stores the print job 75A with the password 83 in the memory 15 (S69) and ends the print / storage process. For example, the CPU 12 stores the print job 75 to be processed in a storage area of ​​the memory 15 for storing the security printing job 75A. Also, in the case of 2), the CPU 12 executes S69. In this case, since the user has the printing authority, the print job 75 is processed as a security printing print job 75. Also, in the case of 3), the CPU 12 executes S69. In this case, since there is a possibility that an unregistered user who cannot execute storage printing wants to execute security printing, the print job 75 is processed as a security printing print job 75.

[0054] On the other hand, in the case of 4), although the password 83 and the user name 85 are set in the print job 75, the user name 85 does not have the printing authority. In this case, the system administrator does not intentionally permit this user to print. For this reason, it is preferable not to permit such a user to execute secure printing. Therefore, the CPU 12 determines that the print job 75 in which the user name 85 of a registered user without printing authority is set matches a predetermined condition (S46: YES), and discards it (S61). This ensures security of the print process in line with the intention of the system administrator, and suppresses accumulation of unnecessary print jobs 75. Note that the judgment conditions and judgment results of 1) to 4) described above are merely examples, and may be appropriately changed according to, for example, the security policy or usability of a company or the like. For example, the CPU 12 may discard the print job 75 in which the user name 85 is set but is not registered (S61). This makes it possible to prohibit printing by unregistered users in both accumulated printing and secure printing.

[0055] (3-2. Processing after pressing an icon) Next, the processing of the CPU 12 in security printing will be described with reference to Fig. 8. Fig. 8 shows the contents of the icon pressing process after pressing the function icon 93A of the security printing function shown on the first standby screen 91A in Fig. 4. For example, in S11 of Fig. 4, when the user performs an operation to scroll the standby screen 91 displayed on the touch panel 21 to the left, the CPU 12 displays the first standby screen 91A on the touch panel 21. The CPU 12 displays the function icon 93A for security printing on the first standby screen 91A. When the function icon 93A on the first standby screen 91A is touched, the CPU 12 displays the job selection window 101 (S13 of Fig. 4) and starts the processing shown in Fig. 8.

[0056] First, in S71 of FIG. 8, the CPU 12 displays a list of job names 81 of the security printing jobs 75A stored in S69 of FIG. 7 in the job selection window 101 of the touch panel 21 (see FIG. 4). In this embodiment, in S46 of FIG. 7, the CPU 12 stores in the memory 15 not only the print job 75 with only the password 83 in 1), but also the print jobs 75 in the cases of 2) and 3) (S69). Therefore, for example, the print job 75 with the password 83 and the user name 85 with printing authority is also displayed in the job selection window 101 as the security printing job 75A. Note that, when the function icon 93A of the security printing function is touched by scrolling the screen on the second standby screen 91B during login shown in FIG. 4, the CPU 12 may display all the stored security printing jobs 75A in the job selection window 101. Alternatively, the CPU 12 may collectively store and print the security printing job 75A and the stored printing job 75B related to the logged-in user in response to the login operation in S23.

[0057] Next, the CPU 12 determines whether any of the job names 81 displayed in the job selection window 101 has been touched (S73). The CPU 12 repeatedly executes the process of S73 until a job name 81 is touched (S73: NO). If no job name 81 is selected after a certain period of time (e.g., 30 seconds) has elapsed, the CPU 12 may erase the job selection window 101 and return the display on the touch panel 21 to the first standby screen 91A or the standby screen 91.

[0058] When any job name 81 in the job selection window 101 is touched (S73: YES, S15 in FIG. 4), the CPU 12 displays the password input window 103 in FIG. 4 on the touch panel 21 (S75). After displaying the password input window 103, the CPU 12 determines whether or not the input of the password 83 in the password input window 103 has been confirmed (S77). For example, when the confirmation key of the numeric keypad 22 (see FIG. 1) is pressed while the password input window 103 in FIG. 4 is displayed, the CPU 12 determines that the input of the password 83 has been confirmed (S77: YES). The CPU 12 repeatedly executes the process of S77 until the input of the password 83 is confirmed (S77: NO). Note that if the input of the password 83 is not confirmed even after a certain period of time has elapsed, the CPU 12 may erase the password input window 103 and display the job selection window 101.

[0059] When the input of the password 83 is confirmed (S77: YES), the CPU 12 judges whether the password 83 input in the password input window 103 matches the password 83 of the selected security print job 75A (S79, S17 in FIG. 4). If the passwords 83 match (S79: YES), the CPU 12 executes printing of the security print job 75A (S81, S17 in FIG. 4). The CPU 12 ends the process in FIG. 8 and, for example, displays the print execution screen 107 in FIG. 4 on the touch panel 21 during printing, and displays the standby screen 91 on the touch panel 21 when printing is completed.

[0060] On the other hand, if the passwords 83 do not match (S79: NO), the CPU 12 displays an error message on the touch panel 21 (S83). After displaying the error message for a fixed period of time, the CPU 12 ends the process of FIG. 8 and displays the password input window 103 again. The CPU 12 executes the process from S75 again, for example. In this manner, the CPU 12 of this embodiment executes the secure printing function.

[0061] Incidentally, the MFP 1 is an example of a printing device. The CPU 12 is an example of a control unit. The memory 15 is an example of a storage unit. The touch panel 21 is an example of an operation unit. The network interface 24 is an example of a communication unit. The authentication DB 73 is an example of authentication data. The password 83 is an example of authentication information. The user names 85 and 111 are examples of user identification information. The print permission flag 114 is an example of print permission information.

[0062] (4. Effects) According to the above-described embodiment, the following effects are achieved. (1) The MFP 1 of this embodiment includes a memory 15 that stores an authentication DB 73 in which a user name 111 that identifies a user and a print authority flag 114 indicating whether or not a print process can be executed in response to a command from a user corresponding to the user name 111 are associated with each other, a network interface 24, a touch panel 21 that accepts user operations, a printing unit 16, and a CPU 12. The CPU 12 executes a receiving process (S31) for receiving the print job 75 associated with the user name 85 via the network interface 24, a first identification process (S49) for identifying whether the user name 85 associated with the print job 75 received by the receiving process is registered in the authentication DB 73, a second identification process (S53) for identifying the print authority flag 114 in the authentication DB 73 corresponding to the user name 85 associated with the print job 75, a storage process for storing in the memory 15 the print job 75 for which a first identification result has been obtained as a result of the first identification process and the second identification process (S55) and not storing in the memory 15 the print job 75 for which a second identification result different from the first identification result has been obtained (S51), a receiving process (S23) for receiving a login operation by the user name 85 via the touch panel 21, and a first printing process (S23) for printing, by the printing unit 16, an image related to the print job 75 stored in the memory 15, which is the print job 75 associated with the user name 85 accepted in the login operation.

[0063] This makes it possible to prevent unnecessary print jobs 75 from being stored in memory 15 according to the user's registration status and authority. Furthermore, print jobs 75 stored in memory 15 are printed when a login operation by the user is accepted. In other words, since the print job is not discharged as a printout until the user logs in, it is possible to prevent other users from viewing the printout, and appropriate printing processing can be provided to the user.

[0064] (2) When the user name 85 associated with the print job 75 is set as the authority in the authentication DB 73 to be "print permitted" as the first identification result, the CPU 12 saves the print job 75 (S53: YES). When the user name 85 associated with the print job 75 is not registered in the authentication DB 73 as the second identification result (S49: NO) and the authority for an unregistered user is set as "print prohibited" in the authentication DB 73 (S57: NO), the CPU 12 does not save the print job 75 (S61). When the user name 85 associated with the print job 75 is not registered in the authentication DB 73 as the second identification result (S49: NO) and the authority for an unregistered user is set as "print prohibited" in the authentication DB 73 as the second identification result, the CPU 12 does not save in the memory 15 the print job 75 for which the third identification result is obtained as a result of the first identification process and the second identification process, the authority in the authentication DB 73 to be "print prohibited" is set. In addition, the CPU 12 executes a second printing process (S67) in which the image related to the print job 75 for which a fourth identification result has been obtained in which the user name 85 associated with the print job 75 is not registered in the authentication DB 73 (S49: NO) as a result of the first identification process and printing is set as the authority for the unregistered user in the authentication DB 73, is printed by the printing unit 16 without requiring a login operation.

[0065] According to this, based on the registration information and the print permission information of each user and unregistered users in the authentication DB 73, appropriate processing can be executed according to each of the first to fourth identification results.

[0066] (3) Furthermore, when a fourth identification result is obtained, the CPU 12 executes a login determination process (S59) to determine whether or not the user is logged in using the user name 85. If the login determination process determines that the user is logged in using the user name 85 (S59: NO), the CPU 12 does not execute the second printing process (S67). If the login determination process determines that the user is not logged in using the user name 85 (S59: YES), the CPU 12 executes the second printing process (S67).

[0067] When logged in, printing processing of print jobs 75 of unregistered users is not executed, so that printed materials printed by a user while logged in can be prevented from being mixed with printed materials of unregistered users. This prevents a user from taking other users' printed materials, and increases the security of printed materials.

[0068] (4) Furthermore, if the CPU 12 determines in the login determination process that the user name 85 is currently logged in (S59: NO), the CPU 12 executes the print job 75 for which the fourth identification result was obtained in the second print process (S67) after logging out by the currently logged-in user name 85. Furthermore, if the logout is based on an operation on the touch panel 21 (S63: YES), the CPU 12 waits a certain period of time after the logout and then starts printing (S65). Furthermore, if the logout is based on a timeout in which a certain period of time has elapsed without accepting an operation on the touch panel 21 (S63: NO), the CPU 12 starts printing without waiting a certain period of time after logout.

[0069] When logging out by operating the touch panel 21, if a printed matter is discharged immediately after logging out, there is a risk that the user who logged out may mistakenly believe that the discharged printed matter is their own printed matter. Therefore, in the case of logout based on operation of the touch panel 21, by waiting a certain period of time before executing the second printing process, it is possible to prevent the user from confusing the printed matter. Also, in the case of logout based on a timeout, by executing the second printing process without waiting a certain period of time, it is possible to start printing promptly.

[0070] (5) If the printing unit 16 is not currently printing (S59: YES), the CPU 12 executes an elapsed time determination process (S63) to determine whether a certain amount of time has elapsed since printing ended. If the login determination process determines that the user is not currently logged in with the user name 85 (S59: YES) and if the elapsed time determination process determines that a certain amount of time has elapsed (S63: NO), the CPU 12 executes a second print process (S67).

[0071] If the next printed material is discharged immediately after printing, the user who printed first may mistake the printed material discharged later for his / her own printed material. Therefore, the print job 75 of the unregistered user is not executed immediately after the previous printing, but is executed after a certain time has passed. This prevents the user from confusing the printed materials.

[0072] (6) The CPU 12 also stores in the memory 15 the print job 75 received via the network interface 24, the print job 75 including at least one of the user name 85 and the password 83. In response to receiving a login operation via the touch panel 21, the CPU 12 retrieves from the memory 15 and prints the stored print job 75B, the print job 75 associated with the user name 85 acquired in the login operation and not including the password 83 (S23). In response to the selection of the print job 75 associated with the password 83 via the touch panel 21 (S15), the CPU 12 receives input of the password 83 via the touch panel 21, and retrieves from the memory 15 and prints the secure print job 75A including the password 83 (S17).

[0073] According to this, the accumulated printing job 75B that does not include the password 83 can be printed by a login operation after being accumulated in the memory 15 (accumulated printing). Also, the secure printing job 75A that includes the password 83 can be printed by accepting the input of the password 83 (secure printing).

[0074] (5. Modifications) still, This specification is not limited to the above embodiment, This specification Needless to say, various improvements and modifications are possible without departing from the spirit and scope of the present invention. For example, in the above embodiment, when the user name 85 associated with the print job 75 is not registered in the authentication DB 73 (S49: NO), the CPU 12 determines the print authority of the unregistered user in the authentication DB 73. However, the CPU 12 may not determine the print authority of the unregistered user. For example, when the user name 85 is not registered in the authentication DB 73 (S49: NO), the CPU 12 may discard the print job 75 regardless of the print authority of the unregistered user in the authentication DB 73. In this case, the print job 75 set with the user name 85 not registered in the authentication DB 73 is not stored in the memory 15. This can prevent the print job 75 of the unregistered user from being stored in the memory 15 and the storage area of ​​the memory 15 from being unnecessarily consumed.

[0075] Also, recognition The authentication information is not limited to numbers such as a PIN number, but may be characters or the like. recognition The authentication based on the identification information may be authentication using information on an authentication card or biometric authentication such as a fingerprint. Furthermore, in S59 of FIG. 7, the CPU 12 determines whether or not at least one of the conditions that the user is currently logged in and that the print job 75 is currently being executed is satisfied, but it may determine only one of the conditions. Furthermore, the CPU 12 may execute a print job 75 of an unregistered user even in a logged-in state. Furthermore, the CPU 12 may execute the print job 75 of an unregistered user without waiting a certain period of time after printing is completed. Furthermore, the CPU 12 may execute a process in which, if printing is executed at login, the user is not allowed to log out until the printing is completed. Furthermore, after logging in, MFP 1 may also execute printing of stored stored print job 75B in response to a predetermined operation on touch panel 21.

[0076] Furthermore, the MFP1 is provided with a touch panel 21 as an operation unit that accepts a login operation, but the login operation may be performed by other methods. For example, the MFP1 may determine whether to permit login based on data received from a mobile terminal. The user may enter a user name 85 or a PIN number 113 on the mobile terminal and transmit it to the MFP1 to perform a login operation. In this case, the communication unit that communicates with the mobile terminal may be Miscellaneous This is an example of a work. In the above embodiment, system Although the CPU 12 that executes a predetermined program is employed as the control unit, the present invention is not limited to this. For example, the control unit may be configured with dedicated hardware such as an ASIC (Application Specific Integrated Circuit). Also, the control unit may be configured to operate using a combination of software processing and hardware processing. In the above embodiment, mark Although the MFP1, which is a multifunction printer, is used as the printing device, the present invention is not limited to this. mark The printing device may be a printer device having only a printing function. [Explanation of symbols]

[0077] 1 MFP (printing device), 12 CPU (control unit), 15 memory (storage unit), 16 printing unit, 21 touch panel (operation unit), 24 network interface (communication unit), 73 authentication DB (authentication data), 75 print job, 83 password (authentication information), 85, 111 user name (user identification information), 114 print authority flag (print permission information).

Claims

1. a storage unit that stores authentication data in which user identification information for identifying a user and print permission information regarding whether or not a print process can be executed in response to a command from the user corresponding to the user identification information are associated with each other; The Communications Department and an operation unit that accepts an operation by the user; A printing department; A control unit; Equipped with The control unit is a receiving process of receiving a print job associated with the user identification information via the communication unit; a first determination process for determining whether the user identification information associated with the print job received by the receiving process is registered in the authentication data; a second identification process for identifying the print permission information in the authentication data corresponding to the user identification information associated with the print job; a storage process for storing, in the storage unit, the print job for which a first identification result has been obtained as a result of the first identification process and the second identification process, and not storing, in the storage unit, the print job for which a second identification result different from the first identification result has been obtained; a reception process of receiving a login operation using the user identification information by the operation unit; a first printing process for printing, by the printing unit, an image related to the print job associated with the user identification information accepted in the login operation and stored in the storage unit; A printing device that performs the

2. The preservation process includes: When the first identification result indicates that printing permission is set as the authority in the authentication data of the user identification information associated with the print job, the print job is stored; When the second identification result indicates that the user identification information associated with the print job is not registered in the authentication data and the authorization for an unregistered user is set to "print prohibited" in the authentication data, the print job is not saved, not storing the print job for which a third identification result is obtained as a result of the first identification process and the second identification process, in which the authorization in the authentication data of the user identification information associated with the print job is set to "unprintable" in the storage unit; The control unit is a second printing process for printing, by the printing unit, an image related to the print job for which a fourth identification result has been obtained as a result of the first identification process, in which the user identification information associated with the print job is not registered in the authentication data and the authentication data has set "printable" as the authority for an unregistered user; and The printing device of claim 1 , further comprising:

3. The control unit is When the fourth identification result is obtained, a login determination process is executed to determine whether the user is currently logged in using the user identification information; A printing device as described in claim 2, wherein, in the login determination process, if it is determined that the user is logged in using the user identification information, the second printing process is not executed, and if it is determined that the user is not logged in using the user identification information, the second printing process is executed.

4. The control unit is When it is determined in the login determination process that the user is currently logged in using the user identification information, the print job for which the fourth identification result has been obtained is executed in the second print process after the user currently logged in uses the user identification information to log out; The second printing process includes: if the logout is based on an operation on the operation unit, after the logout, the printing is started after waiting for a certain period of time; The printing device according to claim 3 , wherein when the logout is based on a timeout that occurs when a predetermined period of time has elapsed without receiving any operation on the operation unit, printing is started after the logout without waiting for the certain period of time.

5. The control unit is executes an elapsed time determination process for determining whether or not a certain time has elapsed since the end of printing when the printing unit is not currently executing printing; A printing device as described in claim 3 or claim 4, wherein the second printing process is executed when it is determined in the login determination process that the user is not logged in using the user identification information and when it is determined in the elapsed time determination process that the certain period of time has elapsed.

6. The control unit is When the first identification result indicates that printing permission is set as the authority in the authentication data of the user identification information associated with the print job, the print job is stored; A printing device as described in claim 1, wherein if the second identification result is that the user identification information associated with the print job is not registered in the authentication data, the print job is not saved regardless of the printing authority of the unregistered user in the authentication data.

7. The control unit is storing, in the storage unit, a print job received via the communication unit, the print job including at least one of the user identification information and the authentication information; In response to receiving the login operation by the operation unit, retrieve from the storage unit the print job associated with the user identification information acquired in the login operation, the print job not including the authentication information, and print the print job; A printing device as described in any one of claims 1 to 6, wherein in response to selection of the print job associated with the authentication information via the operation unit, the operation unit accepts input of the authentication information, and retrieves the print job including the authentication information from the memory unit and prints it.

8. a receiving step of receiving a print job associated with the user identification information via a communication unit; a first identification step of identifying whether or not the user identification information associated with the print job received in the receiving step is registered in authentication data related to usage restrictions of a printing device; a second specifying step of specifying the print permission information corresponding to the user identification information associated with the print job based on the print permission information related to the print authority registered in the authentication data; a storage step of storing, in a storage unit, the print job for which a first identification result has been obtained based on the results of the first identification step and the second identification step, and not storing, in the storage unit, the print job for which a second identification result different from the first identification result has been obtained; a receiving step of receiving a login operation using the user identification information; a printing step of printing, by a printing unit, an image related to the print job associated with the user identification information accepted in the login operation and stored in the storage unit; A printing control method comprising:

Images