Printing apparatus

Abstract

To provide a technology that enables appropriate printing processes to be performed for each user in a printing device where each user has different printing permissions. [Solution] The MFP1 performs the following processes: (S49) to determine whether the username 85 associated with the received print job 75 is registered in the authentication DB 73, and (S53) to determine the printing authority of the username 85 associated with the print job 75. Depending on the result of the determination process, the MFP1 performs either saving the print job 75 (S55) or discarding the print job 75 (S51). Then, in response to the login operation, the MFP1 executes the print job 75 associated with the logged-in user.

Description

Technical Field

[0001] The present invention relates to a printing device having different printing permissions for each user. Place

Background Art

[0002] Conventionally, there is a printing device that executes processing based on identification information of a user included in a received print job (for example, Patent Document 1). When an identifier of a registered user is set in the print job data, the printer device described in Patent Document 1 executes printing as normal. When the identifier of the user set in the print job data is not registered, printing is not executed. Further, when the identifier of the user is not set in the print job data, the printer device executes the print job according to a preset operation mode.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the above-described printer device, the processing content is changed according to whether the user is registered or not. However, in this type of printing device, not only user registration but also, for example, when the user's authority that can be executed on the printing device is preset, it is necessary to execute processing according to the set user authority. Further, in the above-described printing device, when the identification information of a pre-registered user is set in the print job data, printing is executed when the print job data is received. Therefore, even when another user is operating the printing device, printed matter is discharged.

[0005] This specification ​This proposal was made in light of the above-mentioned issues, and aims to provide a technology that can perform appropriate printing processes for each user in a printing device where printing permissions differ for each user. [Means for solving the problem]

[0006] Disclosed herein The printing apparatus comprises a storage unit that stores authentication data associated with user identification information that identifies a user and print permission information that indicates whether or not a printing process can be executed in response to a command from the user corresponding to the user identification information, a communication unit, an operation unit that receives operations from the user, a printing unit, and a control unit, wherein the control unit includes a receiving process that receives a print job associated with the user identification information via the communication unit, a first identification process that determines whether or not the user identification information associated with the print job received by the receiving process is registered in the authentication data, and the user identification information associated with the print job The system performs the following steps: a second identification process for identifying printability information in the authentication data corresponding to the information; a storage process for storing print jobs for which a first identification result has been obtained based on the results of the first and second identification processes in the storage unit, and not storing print jobs for which a second identification result different from the first identification result has been obtained in the storage unit; a reception process for which the operation unit receives a login operation using the user identification information; and a first printing process for which the printing unit prints the image of the print job associated with the user identification information received in the login operation, which has been stored in the storage unit.

[0007] [Effects of the Invention]

[0008] Disclosed hereinAccording to the technology, whether or not to save a print job to the storage unit is controlled based on registration information regarding whether or not user identification information is registered and print permission information regarding print permissions. Therefore, it is possible to prevent unnecessary print jobs from being saved to the storage unit, depending on the user's registration status and permissions. Furthermore, print jobs saved to the storage unit are printed when the user logs in. In other words, since the printed material is not output until the user logs in, it is possible to prevent other users from seeing the printed material and to provide the user with appropriate printing services.

[0009] Furthermore, the technology disclosed herein can be implemented in various forms, for example, the mechanism of the above-mentioned apparatus Noh To make it happen method, This can be implemented in the form of a computer program, a recording medium on which that computer program is stored, and so on. [Brief explanation of the drawing]

[0010] [Figure 1] This is a block diagram showing the electrical configuration of an MFP (Multi-Function Product File). [Figure 2] This diagram shows the data stored in the authentication database. [Figure 3] This diagram shows the contents of a print job described in PJL. [Figure 4] This is a sequence diagram showing the state transitions of the screen displayed on the MFP's touch panel. [Figure 5] This is a flowchart showing the contents of the main process. [Figure 6] This is a flowchart showing the details of the printing / storage process. [Figure 7] This is a flowchart showing the details of the printing / storage process. [Figure 8] This flowchart shows the process after clicking the icon. [Modes for carrying out the invention]

[0011] below, markReferring to FIG. 1, an MFP1 embodying a brush device will be described. FIG. 1 is a block diagram showing the electrical configuration of the MFP1.

[0012] (1. Configuration of MFP) The MFP1 is a multifunction peripheral having a printing function, a copying function, a scanner function, and a FAX function. As shown in FIG. 1, the MFP1 includes 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, etc. These CPU 12, etc. are connected to each other by a bus 11. Further, the MFP1 includes a power supply 25 that supplies power from a commercial power supply. The power supply 25 includes a power cord and a power circuit (such as a bridge diode and a smoothing circuit), generates a DC power supply from the commercial power supply, and supplies power to each part included in the MFP1 through a power line.

[0013] The memory 15 ( Note an example of the storage unit) is, for example, a non-volatile memory such as an NVRAM. Note that Note the storage unit is not limited to an NVRAM, and may be a volatile RAM, ROM, HDD, an external storage device (such as a USB memory) connected to the MFP1, or a storage unit combining them. Further, Note the storage unit may be a file server or the like connected via the network interface 24. The storage unit may also be a computer-readable storage medium. A computer-readable storage medium is a non-transitory medium. Non-transitory media include recording media such as CD-ROMs and DVD-ROMs in addition to the above examples. A non-transitory medium is also a tangible medium. On the other hand, an electrical signal that conveys a program downloaded from a server on the Internet or the like is a computer-readable signal medium, which is a kind of computer-readable medium, but is not included in non-transitory computer-readable storage media.

[0014] The memory 15 stores various programs such as the 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 while temporarily storing the executed processing results in the RAM 13, controls each part connected by the bus 11. Further, the control program 71 includes an EWS (Embedded Web Server) program that functions as a Web server. The CPU 12 makes the MFP 1 function as a Web server by executing the EWS program. Also, an authentication DB (abbreviation for database) 73 is constructed in the memory 15 of the present embodiment. As will be described later, the authentication DB 73 is, for example, data associating the user names of login users who can log in to the MFP 1, the authorities of each user, and the mail addresses of each user (see FIG. 2). In the following description, the MFP 1 that executes the control program 71 etc. by the CPU 12 may sometimes be simply described by the device name. For example, the description "The MFP 1 receives an operation input to the touch panel 21" may mean "The MFP 1 executes the control program 71 by the CPU 12 and controls the touch panel 21, thereby receiving an operation input to the touch panel 21."

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

[0016] The image reading unit 17 includes a document tray (not shown) and an image sensor such as a CIS (Contact Image Sensor) or CCD (Charge-Coupled Device). The image reading unit 17 moves the CIS or the like over the document placed on the document tray to read the document and generate 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 includes a touch panel 21 and operation buttons such as a numeric keypad 22. The touch panel 21 includes, for example, a liquid crystal panel, a light source such as an LED that illuminates light from the back of the liquid crystal panel, and a contact sensing film attached to the surface of the liquid crystal panel. Based on the control of the CPU 12, the user interface 20 displays, for example, various setting screens and the operating status of the device on the touch panel 21. The user interface 20 also transmits signals to the CPU 12 in response to operation input to the touch panel 21 and the numeric keypad 22. In this embodiment, the MFP1 is equipped with a touch panel 21 that serves as both a display and an operation unit, but it is not limited to this, and, for example, hardware keys may be provided as an operation unit separate from 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). In this embodiment, the router 29 is connected to, for example, multiple PCs 41 and a mail server 43. The user sends a print job 75 from the PC 41 to the MFP1 by operating the PC 41. The MFP1 executes the printing process based on the print job 75 received from the PC 41. The MFP1 also processes emails received from the mail server 43 as print jobs 75 and performs tasks such as printing files attached to the emails. Note that the device that sends the print job 75 to the MFP1 is not limited to the PC 41 or the mail server 43, but may also be, for example, a mobile terminal capable of wireless communication with the MFP1. Furthermore, the network connecting the MFP1, PC 41, and mail server 43 is not limited to a wired LAN, but may also be, for example, a wireless LAN or a WAN (including the Internet).

[0019] Next, we will explain the authentication DB73 stored in memory 15. Figure 2 shows an example of data stored in the authentication DB 73. As shown in Figure 2, the authentication DB 73 registers, for example, a username 111, a PIN number 113, a print permission flag 114, a scan permission flag 115, a copy permission flag 116, and an email address 117 as a single record. In this embodiment, the authentication DB 73 has five users registered: public user (PUBLIC), "inoue", "kato", "hayashi", and "minami". The username 111 and PIN number 113 are assigned to each user, for example, by the system administrator who manages the MFP1. Each user uses this username 111 and PIN number 113 to log in to the MFP1.

[0020] Furthermore, the print permission flag 114, scan permission flag 115, and copy permission flag 116 are flag values ​​that determine whether to grant each user the right to execute the print, scan, and copy functions on the MFP1. For example, in the example shown in Figure 2, the public user and the user named "inoue" have print and scan permissions, but do not have copy permissions.

[0021] Furthermore, each record has an email address 117 associated with a username 111, a PIN number 113, etc. As described above, the MFP1 in this embodiment is capable of printing attachments of emails received from the mail server 43.

[0022] The system administrator performs actions such as adding or deleting users, changing permissions, and registering email addresses 117 to the authentication DB 73, as shown in Figure 2. For example, the MFP1 in this embodiment can accept settings for the authentication DB 73 via the EWS. For example, the system administrator operates a web browser on PC 41 and accesses the EWS of the MFP1. The MFP1 executes the settings for the authentication DB 73 based on the information received from the EWS web page. 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 MFP1 may edit the authentication DB 73 in response to operation input on the touch panel 21. Also, the data items of the authentication DB 73 shown in Figure 2 are just examples, and for example, the authentication DB 73 may have flag values ​​that grant execution privileges for the FAX function, or values ​​that limit the number of pages each user can print.

[0023] (2. Secure printing function and storage printing function) The MFP1 of this embodiment is equipped with a security printing function and a storage printing function. In the following description, as shown in Figure 1, the print job 75 for executing the security printing function will be referred to as security printing job 75A, and the print job 75 for executing the storage printing function will be referred to as storage printing job 75B.

[0024] The storage print function, upon receiving a print job 75 with user name 85 set from a PC 41 or other device, stores the received print job 75 as a storage print job 75B in the MFP1's memory 15. When a user name and PIN number are entered via the MFP1's touch panel 21, they are compared with the user name 111 and PIN number 113 (see Figure 2) registered in the authentication DB 73. If the comparison matches the user name 111 and PIN number 113 registered in the authentication DB 73, the user who performed the input operation logs into the MFP1. Upon the user logging into the MFP1, the storage print job 75B associated with the logged-in user's user name 85 is retrieved from memory 15 and printing begins.

[0025] The settings for the storage print function are configured by the system administrator using a web browser on PC41 to access the EWS on MFP1. When the setting to execute the storage print function is configured, MFP1 executes the storage print processes described in this embodiment for print jobs 75 received from external sources such as PC41. When the setting to not execute the storage print function is configured, MFP1 starts the printing process without storing the print job 75 in memory 15 upon receiving it from an external source such as PC41. Note that not storing it in memory 15 in this case means that no separate trigger is provided for starting printing, and does not include the process of temporarily storing it in memory 15 for printing. The printer driver executed on PC41 sets the user account of the user who logs into PC41 in the print job 75 and sends it to MFP1. The same string is used for the user account for logging into PC41 and the username 111 registered in the authentication DB 73.

[0026] The secure printing function is a function that stores a password-associated print job 75 in the memory 15 of the MFP1, and then executes printing of the print job 75 by having the user operate the touch panel 21 of the MFP1 and enter the password associated with the print job 75. When the PC41 executes the secure printing function, it sends a secure printing job 75A with a job name 81 and password 83 set to the MFP1. The job name 81 is, for example, the name of the print job 75 assigned by the printer driver running on the PC41. The password 83 is, for example, information (numbers, letters, etc.) set by the user on the settings screen of the printer driver running on the PC41 and associated with the secure printing job 75A.

[0027] The storage printing function and the secure printing function share the common feature of storing print jobs 75 received from an external source in memory 15 and initiating printing when the user enters authentication information on the MFP1. However, they differ in that the authentication information to be entered is a password 83 associated with the print job 75 in the secure printing function, while it is a PIN number 113 corresponding to a username 111 registered in the authentication DB 73 in the storage printing function. Furthermore, they differ in that the print job 75 to be started is the print job 75 selected by the user in the secure printing function, while it is all print jobs 75 that are to be printed in the storage printing function.

[0028] Figure 3 shows a print job 75 written in PJL (Printer Job Language) as an example. Note that the data in Figure 3 is just an example. As shown in Figure 3, for example, the header of print job 75 contains commands to set variables (such as JOB_NAME) in the following order: job name 81, username 85, password 83, transmission time, and type of writing language. MFP1 changes the processing content of the received print job 75 based on the data set in the header of the received print job 75. For example, if a valid value is set in the variable "JOB_PASSWORD" which indicates password 83, MFP1 determines that password 83 is set in the received print job 75 and treats it as a secure print job 75A. Also, for example, if a valid value is set in "PRINT_USER" which indicates username 85, MFP1 determines that username 85 is set in the received print job 75. Similarly, for printer languages ​​other than PJL, the setting status of username 85, etc. can be detected by determining the content defined in each language.

[0029] Figure 4 shows the state transitions of the screen displayed on the touch panel 21 of the MFP1. Steps S19 to S29 in Figure 4 are processes related to logging into the MFP1. For example, after the MFP1 is powered on and the control program 71 is executed to start the system, the MFP1 displays the standby screen 91 shown in the upper left of Figure 4 on the touch panel 21 (see Figure 1). The MFP1 displays function icons 93 for selecting functions such as fax, copy, and scan in the center of the standby screen 91. The MFP1 also displays a user display field 95 in the upper left of the standby screen 91, which displays the currently selected username. When the power is turned on, no one has logged in yet, so the MFP1 displays in the user display field 95 on the standby screen 91 that a public user has been selected, indicating that the user is logged out. In this embodiment, the MFP1 processes print jobs 75 of users not registered in the authentication DB 73 as print jobs 75 of this public user. When the standby screen 91 is displayed, public users can execute functions (such as the scanning function) according to the permissions granted to them (see Figure 2). The MFP1 also displays a date and time field 97 showing the current time and date in the lower right corner of the standby screen 91. In addition, the MFP1 displays triangular icons 98 on both the left and right sides of the standby screen 91 to indicate that horizontal scrolling is possible.

[0030] In S19 of Figure 4, when the user touches the user display area 95 which displays public users, the MFP1 displays a user selection window 109 on the touch panel 21. The user selection window 109 displays the username 111 registered in the authentication DB 73.

[0031] After displaying the usernames 111 registered in the authentication DB 73 in the user selection window 109, if a user touches one of the usernames 111 in the user selection window 109, for example, the username 111 "inoue" (S21), the MFP1 displays a PIN number input window 121 for entering the PIN number 113. The MFP1 displays a numeric keypad 123 for entering the PIN number 113 and a PIN number input field 124 in the PIN number input window 121. When the PIN number 113 is entered into the PIN number input field 124 using the numeric keypad 123, the MFP1 determines whether the entered PIN number 113 matches the PIN number 113 associated with the username 111 selected in the user selection window 109 (in this case, "1111" for "inoue" in Figure 2) (S23). If the PIN numbers 113 match, the MFP1 allows the login. As will be explained in more detail later, if MFP1 has stored print jobs 75B associated with the logged-in user in memory 15 and the logged-in user has been granted print permissions, MFP1 will print all of the stored print jobs 75B (S23). Also, if MFP1 has stored print data of received emails associated with the logged-in user in memory 15 and the logged-in user has been granted print permissions, MFP1 will print all of the stored print data (attachments, etc.) of received emails (S23).

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

[0033] When the second standby screen 91B is displayed and the user display area 95 is touched (S25), the MFP1 displays the logout window 126. The MFP1 displays a selection key 125 in the logout window 126 for the user to choose whether to perform a logout. When the user touches the "YES" selection key 125 to instruct them to perform a logout (S27), the MFP1 displays the standby screen 91 on the touch panel 21. This completes the logout process. Also, if a certain period of time has elapsed while the MFP1 is displaying the second standby screen 91B, the MFP1 returns the display on the touch panel 21 from the second standby screen 91B back to the standby screen 91 (S29). This period of time is, for example, 30 seconds to 1 minute.

[0034] (3. Operation of MFP1) Next, the operation of the MFP1 in this embodiment will be explained with reference to Figures 5 to 8. Figure 5 shows the flow of the main processing for processing the print job 75. For example, after the MFP1 is powered on and the control program 71 is executed by the CPU 12 to start the system, it executes the main processing shown in Figure 5. Furthermore, the following explanation will mainly describe the printing process based on the print job 75. The printing process based on received emails can be executed in the same way as the print job 75, so its explanation will be omitted as appropriate.

[0035] The sequence diagrams and flowcharts in this specification basically show the processing of the CPU 12 according to the instructions written in the program (control program 71, etc.). In other words, the processes such as "decision," "reception," "acquisition," "acceptance," "control," and "setting" 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 Figure 5, the CPU 12 of MFP1 confirms the receipt of print job 75. As will be described later, the CPU 12 executes S41, etc., and then executes S31 again. Therefore, after the system starts up, the CPU 12 periodically checks whether print job 75 has been received. Based on the confirmation result of S31, the CPU 12 determines whether print job 75 has been received (S33). If the CPU 12 determines that print job 75 has been received (S33: YES), it executes the print / storage process in S35. On the other hand, if the CPU 12 determines that print job 75 has not been received (S33: NO), it executes S37. For example, if the CPU 12 receives multiple print jobs 75, it executes the processes from S31 onwards for each print job 75 in the order in which they were received.

[0037] In S37, CPU12 determines whether a user has logged in. CPU12 determines that a user has logged in if the processes in S19 to S23 in Figure 4 have been performed. From S37 onward, CPU12 executes the processes related to stored printing from S19 onward in Figure 4 as described above. If CPU12 determines that a user has logged in (S37: YES), it determines whether there is a stored printing job 75B associated with the logged-in user among the stored printing jobs 75B stored in memory 15 (S39). Specifically, if the username 85 set in "PRINT_USER" among the stored printing jobs 75B stored in memory 15 matches the username 111 registered in the authentication DB 73 for the logged-in user, it determines that there is a stored printing job 75B associated with the logged-in user. Furthermore, if a print job 75 stored in memory 15 is an received email, and there is a print job 75 with a sender email address that matches the email address 117 registered in the authentication DB 73, the CPU 12 determines that there is a stored print job 75B associated with the logged-in user. When the CPU 12 determines that there is a stored print job 75B for the logged-in user (S39: YES), the printing unit 16 executes the printing of that stored print job 75B (S41). In this case, all print jobs stored in memory 15 are automatically printed without requiring the user to select a job or enter a password. This eliminates the complexity of user operation.

[0038] After executing S41, CPU12 repeats the process from S31. Furthermore, if no user is logged in at S37 (S37:NO), or if there are no stored print jobs 75B associated with a logged-in user at S39 (S39:NO), CPU12 executes the process from S31. Then, at S31, CPU12 confirms the receipt of a new print job 75 and executes the process from S33 onwards.

[0039] (3-1. Printing / Storage Processing) Next, the contents of the print / storage process in S35 of Figure 5 will be explained using Figures 6 and 7. When the print / storage process is executed, a newly received print job 75 will exist in S33 of Figure 5 (S33: YES). The CPU 12 will execute the processes from S43 onwards, treating this newly received print job 75 as the print job to be processed. First, in S43, the CPU 12 checks whether the user name 85 and password 83 are set for 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 in S43. For example, if a valid value is set in the "JOB_PASSWORD" variable (see Figure 3) within 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 Figure 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 username 85 is set for the print job 75 to be processed (S47).

[0041] For example, if the CPU 12 has a valid value set for the "PRINT_USER" variable (see Figure 3) in the print job 75, it determines that the user name 85 is set for the print job 75 to be processed (S47:YES) and executes S49. On the other hand, if the CPU 12 determines that the user name 85 is not set for the print job 75 to be processed (S47:NO), it discards the print job 75 without saving it to memory 15 (S51). After executing S51, the CPU 12 terminates 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 send the print job 75 may not set the user name 85. Therefore, the MFP1 may receive a print job 75 that does not have the user name 85 or password 83 set. In this embodiment, the CPU 12 discards print jobs 75 that do not have the user name 85, etc. set. This prevents print jobs 75 that do not have a username 85, etc., set from being stored in memory 15 without being printed, thus preventing the memory 15 from becoming overloaded. The CPU 12 may, however, execute printing for print jobs 75 that do not have a username 85, etc., set without storing them in memory 15.

[0042] Furthermore, in S49, the CPU 12 determines whether the username 85 set for the print job 75 to be processed is the same as the username 111 (see Figure 2) registered in the authentication DB 73. As shown in Figure 2, the authentication DB 73 in this embodiment has four usernames 111 registered, excluding "PUBLIC" and including "inoue". Therefore, in S49, the CPU 12 accesses the authentication DB 73 and determines that the username 85 set for the print job 75 to be processed is one of the four usernames 111, and that it is the username 111 registered in the authentication DB 73 (S49: YES). Also, if the print job 75 is an incoming email, the CPU 12 determines the sender's email address and the email address 117 registered in the authentication DB 73.

[0043] When the CPU 12 determines that the username 85 of the print job 75 is the same as username 111 registered in the authentication DB 73 (S49: YES), it determines whether or not that user has printing privileges (S53). As shown in Figure 2, in the authentication DB 73 of this embodiment, users "inoue" and "hayashi" with username 111 have printing privileges (see printing privilege flag 114). Therefore, if the username 85 of the print job 75 to be processed is "inoue" or "hayashi", the CPU 12 determines that the user has printing privileges (S53: YES) and executes S55. Here, in this embodiment, for example, when the CPU 12 saves the print job 75 to memory 15, it uses different memory areas for saving security print jobs 75A and for saving storage print jobs 75B. In S55, the CPU 12 saves the print job 75 to be processed to the memory area of ​​memory 15 that is used to save storage print jobs 75B. The print job 75, which is stored in memory 15 in S55, is processed as a stored print job 75B in S41 of Figure 5. When CPU 12 executes S55, it terminates the print / storage process.

[0044] Furthermore, if the CPU 12 determines in S53 that the user does not have printing privileges (S53:NO), it discards the print job 75 to be processed (S51). This prevents the print job 75 from accumulating in memory 15 because the user does not have printing privileges and therefore cannot be executed, thus preventing it from putting pressure on the memory 15's storage area.

[0045] Furthermore, if CPU 12 determines in S49 that the username 85 of the print job 75 to be processed is not registered in the authentication DB 73 (S49: NO), it processes the print job 75 as a print job 75 for a public user (S57 in Figure 7). In S57 in Figure 7, CPU 12 determines whether the public user in the authentication DB 73 has print privileges.

[0046] As shown in Figure 2, print permissions can be set for public users in this embodiment. If a public user is granted print permissions (see print permission flag 114), the CPU 12 starts processing to print the target print job 75 (S59). Therefore, the CPU 12 in this embodiment processes the unregistered user's print job 75 as the public user's print job 75 and starts immediate printing without accumulating it. On the other hand, if a public user is not set to print permissions (S57: NO), the CPU 12 discards the target print job 75 without saving it to memory 15 (S61) and terminates the print / accumulation process. This enhances security by prohibiting printing by unregistered users. Furthermore, it prevents print jobs 75 with an unregistered username 85 from being continuously accumulated in memory 15 without being printed, thus preventing the memory 15 from becoming overloaded. Note that in Figure 2, "OK (immediate print)" is written as an example of a public user's print permission. This explanation includes "(immediate print)" to clarify that if a public user has print privileges in the stored print function, the printout will be printed immediately without being stored. However, for registration in the authentication DB73, only "OK" needs to be set. Additionally, to make it easier for system administrators to understand what kind of printing process will be performed, a settings screen indicating "OK (immediate print)" may be displayed if the stored print function is enabled.

[0047] Furthermore, in S59, the CPU 12 determines whether at least one of the following conditions is met: the user is logged in and the print job 75 is running. If the CPU 12 finds that at least one of the following conditions is met (S59: NO), the determination process in S59 is repeatedly executed. If a print job 75 with an unregistered username 85 is executed while the user is logged in or printing is in progress, there is a risk that the printed materials ejected into the output tray of the MFP1 may be mixed with those of other users. As a result, there is a risk that confidential documents may be seen or taken by other users. Therefore, in this embodiment, the CPU 12 does not execute a print job 75 with an unregistered username 85 while the user is logged in or the print job 75 is running. This prevents, for example, the execution of a print job 75 with an unregistered username 85 and the mixing of printed materials when the user is logged in and operating the touch panel 21, or when the user has logged out but is executing a print job 75.

[0048] Furthermore, if neither of the conditions of being logged in nor executing print job 75 is met, i.e., printing is not being performed while logged out (S59: YES), the CPU 12 determines whether a certain amount of time has elapsed since the completion of the previous printing process (S63). If the next printing process is started immediately after the completion of the previous printing process, there is a risk of the printed materials ejected from the MFP1 getting mixed up. Therefore, the CPU 12 in this embodiment waits for a certain amount of time after the completion of the previous printing process before executing the printing of the target print job 75. This makes it more reliable to prevent users from mixing up printed materials and enhances security.

[0049] CPU12 executes S67 if a certain amount of time has elapsed since the completion of the previous printing process (S63: NO). If a certain amount of time has not elapsed since the completion of the previous printing process (S63: YES), CPU12 waits for a certain amount of time (S65) before executing S67. The waiting time in S65 is, for example, the time required for the user to take the previously printed documents from the output tray, and is, for example, 5 to 15 seconds.

[0050] In S67, CPU 12 executes the printing of the target print job 75, that is, the print job 75 with the unregistered username 85 set. This allows the print job 75 with the unregistered username 85 to be printed immediately without being stored, using the print privileges of a public user. After executing S67, CPU 12 terminates the print / storage process.

[0051] Here, as shown in S29 of Figure 4, in this embodiment, if 30 seconds have elapsed while the MFP1 is displaying the second waiting screen 91B after login, for example, the display on the touch panel 21 will return from the second waiting screen 91B to the waiting screen 91. Therefore, if the user logs out due to a timeout, it is highly likely that the 5 to 15 seconds described above, which is a certain period of time after the completion of printing, has elapsed. Accordingly, if the logout is based on a timeout, the CPU 12 will start printing (S67) without waiting for a certain period of time after the logout (S63: NO). On the other hand, if the logout is based on an operation on the touch panel 21, it is possible that a certain period of time has not elapsed since the completion of the previous printing process. Therefore, the CPU 12 will determine the certain period of time in S63, and if the certain period of time has not elapsed, it will wait in S65.

[0052] Furthermore, in S45 of Figure 6, if the CPU 12 determines that a password 83 is set for the print job 75 to be processed (S45: NO), it determines whether the print job 75 to be processed meets predetermined conditions (S46 of Figure 7). Among the print jobs 75 with a password 83 set, for example, there are: 1) those for which no username 85 is set, 2) those for which a username 85 is set and the user has printing privileges, 3) those for which a username 85 is set and the user has unregistered username 85, and 4) those for which a username 85 is set and the user does not have printing privileges. The CPU 12 makes the determination in S46 based on these conditions.

[0053] In case 1), print job 75 is a print job 75 without a username 85 and with a password 83 set, i.e., a security print job 75A that is subject to security printing. Therefore, if the CPU 12 determines that the print job 75 in case 1) does not have a username 85 set (S46: NO), it stores it in memory 15 as a security print job 75A with a password 83 (S69) and terminates the print / storage process. For example, the CPU 12 stores the print job 75 to be processed in the memory area of ​​memory 15 that is used to store security print jobs 75A. In case 2), the CPU 12 also executes S69. In this case, since the user has printing privileges, it is processed as a print job 75 for security printing. In case 3), the CPU 12 also executes S69. In this case, since there is a possibility that an unregistered user who cannot perform storage printing may want to perform security printing, it is processed as a print job 75 for security printing.

[0054] On the other hand, in case 4), although the print job 75 has a password 83 and a username 85 set, the username 85 does not have print privileges. In this case, the system administrator has intentionally not allowed this user to print. For this reason, it is preferable not to allow such a user to perform secure printing either. Therefore, the CPU 12 discards the print job 75 with the username 85 of a registered user who does not have print privileges, as it meets the predetermined conditions (S46: YES) (S61). This ensures the security of the printing process in accordance with the system administrator's intentions and suppresses the accumulation of unnecessary print jobs 75. Note that the judgment conditions and results in 1) to 4) described above are just examples and may be changed as appropriate according to the security policy and usability of a company, for example. For example, the CPU 12 may discard the print job 75 with username 85 set but with an unregistered username 85 (S61). This makes it possible to prohibit printing by unregistered users in both stored printing and secure printing.

[0055] (3-2. Post-icon processing) Next, we will explain the processing of the CPU 12 in secure printing using Figure 8. Figure 8 shows the post-icon pressing process after pressing the function icon 93A of the secure printing function shown in the first standby screen 91A of Figure 4. For example, in S11 of Figure 4, when the user scrolls 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 secure 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 Figure 4) and starts the processing shown in Figure 8.

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

[0057] Next, the CPU 12 determines whether one of the job names 81 displayed in the job selection window 101 has been touched (S73). The CPU 12 repeatedly executes the process in S73 until a job name 81 is touched (S73: NO). If a job name 81 is not selected after a certain period of time (for example, 30 seconds), the CPU 12 may close 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 a job name 81 in the job selection window 101 is touched (S73:YES, S15 in Figure 4), the CPU 12 displays the password input window 103 shown in Figure 4 on the touch panel 21 (S75). After displaying the password input window 103, the CPU 12 determines whether or not the input of password 83 to the password input window 103 has been confirmed (S77). For example, if the confirmation key on the numeric keypad 22 (see Figure 1) is pressed while the password input window 103 shown in Figure 4 is displayed, the CPU 12 determines that the input of password 83 has been confirmed (S77:YES). The CPU 12 repeatedly executes the process in S77 until the input of password 83 is confirmed (S77:NO). If the input of password 83 is not confirmed after a certain period of time, the CPU 12 may close the password input window 103 and display the job selection window 101.

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

[0060] On the other hand, if the password 83 does not match (S79: NO), the CPU 12 displays an error message on the touch panel 21 (S83). For example, after displaying the error message for a certain period of time, the CPU 12 terminates the process shown in Figure 8 and displays the password input window 103 again. For example, the CPU 12 then executes the process from S75 again. In this way, the CPU 12 of this embodiment performs the security printing function.

[0061] Incidentally, MFP1 is an example of a printing device. CPU12 is an example of a control unit. Memory15 is an example of a storage unit. Touch panel21 is an example of an operation unit. Network interface24 is an example of a communication unit. Authentication DB73 is an example of authentication data. Password83 is an example of authentication information. Usernames85,111 are examples of user identification information. Print permission flag114 is an example of print permission information.

[0062] (4. Effects) As described above, the embodiments provide the following effects. (1) The MFP1 of this embodiment includes a memory 15 that stores an authentication DB 73 associated with a username 111 that identifies a user and a print authorization flag 114 that indicates whether or not printing can be performed in response to a command from the user corresponding to the username 111, a network interface 24, a touch panel 21 that accepts user operations, a printing unit 16, and a CPU 12. The CPU 12 performs the following: a reception process (S31) to receive a print job 75 associated with a username 85 via the network interface 24; a first identification process (S49) to determine whether the username 85 associated with the print job 75 received in the reception process is registered in the authentication DB 73; a second identification process (S53) to identify the print authorization flag 114 in the authentication DB 73 corresponding to the username 85 associated with the print job 75; a saving process (S55) to save print jobs 75 for which a first identification result has been obtained based on the results of the first and second identification processes to the memory 15, and not save print jobs 75 for which a second identification result different from the first identification result has been obtained to the memory 15 (S51); a reception process (S23) to accept a login operation by username 85 via the touch panel 21; and a first printing process (S23) to print the image related to the print job 75 that has been saved in the memory 15 and is associated with the username 85 received in the login operation, using the printing unit 16.

[0063] According to this, it is possible to prevent unnecessary print jobs 75 from being stored in memory 15, depending on the user's registration status and user privileges. Furthermore, print jobs 75 stored in memory 15 are printed when the user logs in. In other words, since they are not printed until the user logs in, it is possible to prevent other users from seeing the printed materials and to provide users with appropriate printing services.

[0064] (2) The CPU 12 saves the print job 75 if, as a first identification result, the user name 85 associated with the print job 75 is set to print permission in the authentication DB 73 (S53: YES). The CPU 12 also does not save the print job 75 if, as a second identification result, the user name 85 associated with the print job 75 is not registered in the authentication DB 73 (S49: NO), and the authentication DB 73 is set to print prohibition as an authority for unregistered users (S57: NO) (S61). The CPU 12 also does not save the print job 75 in memory 15 if, as a result of the first and second identification processes, a third identification result is obtained in which the user name 85 associated with the print job 75 is set to print prohibition in the authentication DB 73 (S51). Furthermore, the CPU 12 executes a second printing process (S67) in which, as a result of the first identification process, the user name 85 associated with the print job 75 is not registered in the authentication DB 73 (S49: NO), and a fourth identification result is obtained in the authentication DB 73 where the user has the authority to print as an unregistered user. The CPU 12 prints the image related to the print job 75 using the printing unit 16 without requiring a login operation.

[0065] According to this, appropriate processing can be performed according to each of the first to fourth identification results, based on the registration information and the printability information of each user and unregistered user in the authentication DB73.

[0066] (3) If the CPU 12 obtains the fourth identification result, it executes a login determination process (S59) to determine whether the user is logged in with username 85. In the login determination process, if it determines that the user is logged in with username 85 (S59: NO), it does not execute the second printing process (S67). If it determines that the user is not logged in with username 85 (S59: YES), it executes the second printing process (S67).

[0067] When a user is logged in, the system will not process print job 75 for an unregistered user. This prevents the mixing of printed documents from the logged-in user with those of an unregistered user. Furthermore, it helps prevent situations such as users taking other users' printed documents, thereby enhancing the security of printed materials.

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

[0069] When logging out by operating the touch panel 21, if a printout is ejected immediately after logging out, the logged-out user may mistake the ejected printout for their own. Therefore, in the case of logout based on operation of the touch panel 21, the second printing process is executed after a certain period of time, thereby preventing the user from confusing printouts. In the case of logout based on a timeout, printing can be started quickly by executing the second printing process without waiting for a certain period of time.

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

[0071] If the next print job is ejected immediately after the previous one, the user who performed the first print job may mistakenly believe the later ejected print job is their own. Therefore, print job 75 for an unregistered user is not executed immediately after the previously executed print job, but after a certain period of time has elapsed. This helps to prevent users from confusing their print jobs.

[0072] (6) The CPU 12 also stores in memory 15 any print jobs 75 received via the network interface 24 that include at least one of a username 85 and a password 83. When the CPU 12 receives a login operation via the touch panel 21, it retrieves a stored print job 75B from memory 15 that is associated with the username 85 obtained in the login operation but does not include a password 83, and prints it (S23). When the CPU 12 receives a print job 75 associated with a password 83 via the touch panel 21 (S15), it receives input of the password 83 via the touch panel 21, retrieves a security print job 75A that includes the password 83 from memory 15, and prints it (S17).

[0073] According to this, for storage print jobs 75B that do not include password 83, they can be stored in memory 15 and then printed upon login (storage print). For security print jobs 75A that include password 83, they can be printed after the password 83 is entered (security print).

[0074] (5. Variant) still, This specification The embodiments described above are not limited to the above-described embodiments. This specification Needless to say, various improvements and modifications are possible as long as they do not deviate from the original intent. For example, in the above embodiment, the CPU 12 determined the printing authority of an unregistered user in the authentication DB 73 when the username 85 associated with the print job 75 was not registered in the authentication DB 73 (S49: NO). However, it is not necessary to determine the printing authority of an unregistered user. For example, the CPU 12 may discard the print job 75 when the username 85 is not registered in the authentication DB 73 (S49: NO), regardless of the printing authority of the unregistered user in the authentication DB 73. In this case, print jobs 75 with a username 85 that is not registered in the authentication DB 73 are not uniformly saved in memory 15. This prevents unregistered users' print jobs 75 from being saved in memory 15 and prevents unnecessary consumption of memory space in memory 15.

[0075] Also, recognition The verification information is not limited to numbers like PIN numbers; it can also include letters or other characters. recognition Authentication using authentication information can include authentication using information on an authentication card, or biometric authentication such as fingerprints. Furthermore, in S59 of Figure 7, the CPU 12 determined whether at least one of the following conditions was met: that the user was logged in and that the print job 75 was being executed. However, it is also acceptable to determine only one of these conditions. Furthermore, CPU12 may execute print job 75 for an unregistered user even if it is logged in. Furthermore, CPU 12 may execute print job 75 for an unregistered user without waiting a certain amount of time after the print job is finished. Additionally, CPU12 may execute a process that prevents the user from logging out until printing is complete, if printing is performed during login. Furthermore, after logging in, MFP1 may execute printing of the stored print jobs 75B in response to a predetermined operation on the touch panel 21.

[0076] Furthermore, although the MFP1 is equipped with a touch panel 21 as an operation unit for accepting login operations, it may also be configured to allow login operations by other methods. For example, the MFP1 may decide whether to allow login based on data received from a mobile terminal. The user may also perform the login operation by entering a username 85 and PIN number 113 on their mobile terminal and sending them to the MFP1. In this case, the communication unit that communicates with the mobile terminal is: Miscellaneous This is an example of a production department. Furthermore, in the above embodiment, system While a CPU 12 is used to execute a predetermined program, the system is not limited to this. For example, the control unit may be configured with dedicated hardware such as an ASIC (Application Specific Integrated Circuit). Furthermore, the control unit may be configured to operate using a combination of software processing and hardware processing. Furthermore, in the above embodiment, mark We adopted the MFP1, a multifunction printer, as our printing device, but it is not the only option. mark The printing device may be a printer that has only a printing function. [Explanation of Symbols]

[0077] 1 MFP (Printer), 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 Username (User Identification Information), 114 Print Permission Flag (Printing Permit Information).

Claims

1. A storage unit that stores authentication data associated with user identification information that identifies a user and print permission information that indicates whether or not a print process can be executed in response to a command from the user corresponding to the user identification information, Communications Department and, The operation unit that receives user input, The printing department, Control unit and Equipped with, The control unit, A receiving process that receives a print job associated with the user identification information via the communication unit, A first identification process that determines whether the user identification information associated with the print job received by the reception process is registered in the authentication data, A second identification process for identifying print permission information in the authentication data corresponding to the user identification information associated with the print job, Based on the results of the first and second identification processes, a storage process is performed to store the print jobs for which a first identification result was obtained in the storage unit, and not to store the print jobs for which a second identification result different from the first identification result was obtained in the storage unit. A reception process in which the operation unit receives a login operation using the user identification information, A first printing process in which the printing unit prints an image related to the print job, which is associated with the user identification information received in the login operation and stored in the storage unit, A printing device that performs this task.

2. The aforementioned preservation process is As a first identification result, if print permission is set as an authorization in the authentication data of the user identification information associated with the print job, the print job is saved. As a second determination result, if the user identification information associated with the print job is not registered in the authentication data, and the authentication data has a setting that print is disabled for unregistered users, the print job will not be saved. If, as a result of the first and second identification processes, a third identification result is obtained in which the authorization in the authentication data of the user identification information associated with the print job is set to "print not allowed", the print job is not stored in the storage unit. The control unit, A second printing process is performed in which, as a result of the first identification process, the user identification information associated with the print job is not registered in the authentication data, and a fourth identification result is obtained in which the authentication data has permission to print for unregistered users, and the image related to the print job is printed by the printing unit without requiring the login operation. A printing apparatus according to claim 1, which performs the following:

3. The control unit, If the above-mentioned fourth identification result is obtained, a login determination process is executed to determine whether the user is logged in using the user identification information. The printing apparatus according to 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, In the login determination process, if it is determined that the user is logged in using the user identification information, the print job for which the fourth identification result was obtained is executed in the second print process after the user is logged out using the user identification information that was logged in. The second printing process described above is: If the logout is based on an operation on the control unit, after the logout, the printer waits for a certain period of time before starting to print. The printing apparatus according to claim 3, wherein if the logout is based on a timeout occurring after a predetermined period of time has elapsed without accepting any operation on the control unit, printing is started without waiting for the predetermined period of time after the logout.

5. The control unit, If the printing unit is not currently performing printing, a time elapsed determination process is executed to determine whether a certain amount of time has elapsed since the completion of printing. The printing apparatus according to claim 3 or 4, wherein if the login determination process determines that the user is not logged in using the user identification information and the elapsed time determination process determines that a certain amount of time has elapsed, the second printing process is executed.

6. The control unit, As a first identification result, if print permission is set as an authorization in the authentication data of the user identification information associated with the print job, the print job is saved. The printing apparatus according to claim 1, wherein, as a second identification result, if 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, A print job received via the communication unit, which includes at least one of the user identification information and authentication information, is stored in the storage unit. In response to the login operation being received by the operation unit, the operation unit retrieves from the storage unit the print job associated with the user identification information obtained in the login operation, which does not include the authentication information, and prints it. A printing apparatus according to any one of claims 1 to 6, wherein, in response to the selection of the print job associated with the authentication information via the operation unit, the operation unit receives input of the authentication information, retrieves the print job including the authentication information from the storage unit, and prints it.

8. A receiving process that receives print jobs associated with user identification information via a communication unit, A first identification step involves determining whether the user identification information associated with the print job received in the receiving step is registered in the authentication data for restrictions on the use of the printing device, A second identification step involves identifying the print permission information corresponding to the user identification information associated with the print job, based on the print permission information regarding print authorization registered in the authentication data. A storage step in which, based on the results of the first and second identification steps, the print jobs for which a first identification result was obtained are stored in the storage unit, and the print jobs for which a second identification result different from the first identification result was obtained are not stored in the storage unit; A reception process for accepting login operations using the aforementioned user identification information, A printing step in which the printing unit prints the image related to the print job, which is associated with the user identification information received in the login operation and which is stored in the storage unit, A printing control method, including a print control method.

Images