JP2019142171A - Printer - Google Patents

Abstract

Provided is a technique capable of printing a print job associated with unregistered user information after receiving the print job after registering the user information. When an MFP determines that a user name of a received print job is registered in an authentication DB stored in a memory, the MFP stores the print job in a storage area for storage in the memory. 52 (S57). If the MFP 1 determines that the print job has not been registered, the MFP 1 stores the print job 75 in the security printing storage area 51 different from the storage printing storage area 52 (S59). When the user name 111 in the authentication DB 73 is updated, the MFP 1 prints the print job 75 associated with the newly added user name 111 after the update in the security print storage area 51. The job 75 is stored in the storage printing storage area 52. [Selection diagram] FIG.

Description

  The present invention relates to a printing apparatus having a function of storing a print job in a storage unit and starting printing by inputting authentication information from a user.

  Conventionally, there is a printer device that executes processing based on user identification information included in a received print job (for example, Patent Document 1). The printer device described in Patent Document 1 executes printing as usual when a previously registered user identifier is set in the print job data. If the user identification information set in the print job data is not registered, the execution of the print job is terminated and the print data is discarded.

JP 2004-314547 A

  The above-described printing apparatus discards the unregistered user's print job when the print job is received. For this reason, if the user registration work by the operator is delayed, the print job is stored on the printing apparatus side even if it is originally registered in the printing apparatus and the print job is from a user who can print. The user may not be able to print.

  The present application has been proposed in view of the above problems, and an object thereof is to provide a technique capable of printing a print job associated with unregistered user information at the time of receiving a print job after the user information is registered. .

  A printing apparatus according to the present application includes a storage unit that stores a restriction table including user information, a communication unit, an operation unit that receives an operation, a printing unit that prints an image, and a control unit. A first reception process for receiving a print job associated with the user information via the communication unit, and the user information associated with the print job received by the first reception process are stored in the storage unit. Judgment processing for judging whether it is registered in the stored restriction table, and when it is judged that the job is registered as a result of the judgment processing, the print job is stored in the job storage area of the storage unit and registered. A first storage process for storing the print job in an area different from the job storage area when it is determined that the user information is received, and the user information is received via the operation unit. Print job associated with the user information received via the operation unit, out of the print jobs stored in the job storage area of the storage unit Acquisition processing, first print processing for printing an image related to the print job acquired by the acquisition processing by the printing unit, and when the user information in the restriction table is updated, newly added after the update When the print job associated with the user information is stored in the different area, a second storage process for storing the print job in the job storage area is executed.

  According to the technique according to the present application, a print job stored in the job accumulation area and associated with the user information of the login user is executed in response to a login operation by the user. In addition, when a print job associated with unregistered user information is stored in a predetermined area (different area) and new user information is added to the restriction table, the print job associated with the user information is stored in the job. Store in the accumulation area. Therefore, even if user registration is not in time when a print job is received, if a new user is registered in the restriction table, the print job associated with the new user information is stored in the job storage area and executed at login To do. Accordingly, even a print job received before registration of user information can be printed after registration.

  The technology disclosed in the present specification can be realized in various forms. For example, a method for realizing the functions of the above apparatus, a computer program, a recording medium on which the computer program is recorded, etc. Can be realized.

2 is a block diagram illustrating an electrical configuration of the MFP. FIG. It is a figure which shows the data memorize | stored in authentication DB. FIG. 6 is a diagram illustrating the contents of a print job described in PJL. FIG. 4 is a diagram illustrating a print job accumulation state in a security print storage area and a storage print storage area of a memory. It is a sequence diagram which shows the state transition of the screen displayed with a touch panel. It is a flowchart which shows the content of the main process. It is a flowchart which shows the content of the job accumulation judgment process. It is a flowchart which shows the content of an authentication DB update process.

  Hereinafter, an MFP 1 as an embodiment embodying the printing apparatus of the present application will be described with reference to FIG. FIG. 1 is a block diagram showing an electrical configuration of the MFP 1.

(1. Configuration of MFP)
The MFP 1 is a multifunction machine having a print function, a copy function, a scanner function, and a FAX function. As shown in FIG. 1, the MFP 1 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, a network interface 24, and the like. These CPUs 12 and the like are connected to each other by a bus 11. The MFP 1 also includes a power source 25 that supplies power from a commercial power source. The power supply 25 includes a power supply cord and a power supply circuit (a bridge diode, a smoothing circuit, etc.), generates a DC power supply from a commercial power supply, and supplies power to each unit included in the MFP 1 through a power supply line.

  The memory 15 (an example of the storage unit of the present invention) is a non-volatile memory such as NVRAM, for example. The storage unit of the present application is not limited to NVRAM, but may be a volatile RAM, ROM, HDD, an external storage device (such as a USB memory) connected to the MFP 1, or a storage unit that combines them. The storage unit of the present application may be a file server or the like connected via the network interface 24. The storage unit may 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-ROM and DVD-ROM in addition to the above examples. A non-transitory medium is also a tangible medium. On the other hand, an electrical signal that carries a program downloaded from a server on the Internet is a computer-readable signal medium that is a kind of computer-readable medium, but a non-transitory computer-readable storage. Not included in the media.

  The memory 15 stores various programs such as the control program 71. The control program 71 is a program that comprehensively controls each unit of the MFP 1, for example. The CPU 12 executes the control program 71 and controls each unit connected via the bus 11 while temporarily storing the executed processing result in the RAM 13. The control program 71 includes an EWS (Embedded Web Server) program that is a program that functions as a Web server. The CPU 12 causes the MFP 1 to function as a Web server by executing the EWS program. Also, an authentication DB (abbreviation of database) 73 is constructed in the memory 15 of the present embodiment. As will be described later, the authentication DB 73 is data in which, for example, a user name of a login user who can log in to the MFP 1, authority of each user, and mail address of each user are associated (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 by a device name. For example, the description “MFP1 accepts operation input to touch panel 21” means “MFP 1 accepts operation input to touch panel 21 by executing control program 71 and controlling touch panel 21 with CPU 12”. There is.

  The printing unit 16 includes a head 161 and an ink cartridge 162. The ink cartridge 162 stores ink. The head 161 discharges ink supplied from the ink cartridge 162 onto a sheet (paper, OHP, etc.). As a result, the printing unit 16 prints an image on the sheet by the inkjet method based on the control of the CPU 12. Note that the printing unit 16 of the present application is not limited to the configuration in which printing is performed by the inkjet method, but may be configured by other methods, for example, printing by an electrophotographic method.

  The image reading unit 17 includes a document table (not shown) 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 with respect 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 machines via a telephone line.

  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 emits light from the back side of the liquid crystal panel, a contact sensing film bonded to the surface of the liquid crystal panel, and the like. The user interface 20 displays various setting screens, operation states of the apparatus, and the like on the touch panel 21 based on the control of the CPU 12. In addition, the user interface 20 transmits a signal corresponding to an operation input to the touch panel 21 or the numeric keypad 22 to the CPU 12. Note that the MFP 1 of the present embodiment includes the touch panel 21 serving as both a display unit and an operation unit. However, the present invention is not limited to this, and for example, a hardware key may be provided as an operation unit separately from the display unit. Good.

  The network interface 24 is a LAN (Local Area Network) interface, for example, 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 of this embodiment. The user operates the PC 41 to transmit a print job 75 from the PC 41 to the MFP 1. The MFP 1 executes print processing based on the print job 75 received from the PC 41. In addition, the MFP 1 processes the mail received from the mail server 43 as a print job 75, and executes printing of a file attached to the mail. Note that the apparatus that transmits the print job 75 to the MFP 1 is not limited to the PC 41 or the mail server 43, and may be a portable terminal capable of wireless communication with the MFP 1, for example. The network connecting the MFP 1, 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).

Next, the authentication DB 73 stored in the memory 15 will be described.
FIG. 2 shows an example of data stored in the authentication DB 73. As shown in FIG. 2, in the authentication DB 73, 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 and registered as one record. ing. In the authentication DB 73 of the present embodiment, five public users (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.

  Further, the print authority flag 114, the scan authority flag 115, and the copy authority flag 116 are flag values for setting whether to give the authority to execute the print function, scan function, and copy function for the MFP 1 to each user. For example, in the example illustrated in FIG. 2, the public user and the user name “inoue” have the print authority and the scan authority, but do not have the copy authority. Further, in each record, a mail address 117 is set in association with the user name 111, the PIN number 113, and the like.

  The system administrator performs addition and deletion of users, change of authority, registration of the mail address 117, and the like shown in FIG. For example, the MFP 1 according to the present embodiment can accept the setting of the authentication DB 73 by 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 sets the authentication DB 73 based on the information received on the EWS web page. Note that the editing method of the authentication DB 73 is not limited to the method using the above-described WEB server. For example, the MFP 1 may edit the authentication DB 73 in response to an operation input on the touch panel 21. Further, the data items of the authentication DB 73 shown in FIG. 2 are examples. For example, the authentication DB 73 may have a flag value for granting the authority to execute the FAX function and a value for limiting the number of printed sheets for each user. .

(2. Security print function and stored print function)
The MFP 1 of this embodiment has a security printing function and a storage printing function. In the following description, as shown in FIG. 1, the print job 75 for executing the security printing function is referred to as a security printing job 75A, and the print job 75 for executing the storage printing function is referred to as the storage printing job. This will be described as 75B. Further, when the print job types are collectively referred to without distinction, the print job 75 will be described.

  When the accumulated print job 75B in which the user name 85 is set is received from the PC 41 or the like, the accumulated print function stores the received accumulated print job 75B in the memory 15 of the MFP 1. When the user name and the PIN number are input via the touch panel 21, the MFP 1 collates with the user name 111 and the PIN number 113 (see FIG. 2) registered in the authentication DB 73. If the user name 111 and PIN number 113 registered in the authentication DB 73 match as a result of the verification, the user who has performed the input operation logs in to the MFP 1. When the user logs in to the MFP 1, the stored print job 75 </ b> B associated with the user name 111 of the logged-in user is acquired from the memory 15 and printing is started.

  Setting of the accumulated printing function is performed by the system administrator operating the Web browser on the PC 41 and accessing the EWS of the MFP 1. When setting to execute the accumulated printing function is performed, the MFP 1 executes each process for accumulated printing described in the present embodiment on the print job 75 received from an external terminal such as the PC 41. When setting that the stored print function is not executed is performed, the MFP 1 starts the printing process without being stored in the memory 15 when receiving the print job 75 from the external terminal such as the PC 41. Note that not storing in the memory 15 in this case means that a trigger for starting printing is not provided separately, and processing for temporarily storing in the memory 15 for printing processing is not included. The printer driver executed on the PC 41 sets a user account for logging in to the PC 41 as the user name 85 (see FIG. 1) in the stored print job 75B, and transmits it to the MFP 1. 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. Each process in the present embodiment is premised on the setting for executing the accumulated printing function.

  With the security printing function, a security printing job 75A in which a job name 81 and a password 83 (see FIG. 1) are set is temporarily stored in the memory 15 of the MFP 1, and the user operates the touch panel 21 of the MFP 1 to perform a security printing job. This is a function for executing printing of the security printing job 75A by inputting the password 83 associated with 75A. When executing the security printing function, the PC 41 transmits to the MFP 1 a security printing job 75A in which a job name 81 and a password 83 are set. The job name 81 is, for example, the name of the print job 75 given by the printer driver executed on the PC 41. The password 83 is information (numbers, characters, etc.) set by the user on the printer driver setting screen executed on the PC 41 and associated with the security printing job 75A, for example. Although illustration is omitted, for example, the same user name 85 as the accumulated printing job 75B is set in the security printing job 75A of the present embodiment.

  The storage printing function and the security printing function are common in that the print job 75 received from the outside is stored in the memory 15 and printing is started when the user performs an authentication information input operation in the MFP 1. On the other hand, the authentication information to be input is a password 83 associated with the print job 75 in the security printing function, but the stored printing function is different in that it is a PIN number 113 corresponding to the user name 111 registered in the authentication DB 73. Also, the print job 75 to start printing is the print job 75 selected by the user in the security print function, but differs in that it is all print jobs 75 to be printed in the accumulated print function.

  FIG. 3 shows a print job 75 described in PJL (Printer Job Language) as an example. Note that the content of the data in FIG. 3 is an example. As shown in FIG. 3, for example, in the header of the print job 75, a command for setting variables (JOB_NAME, etc.) in the order of job name 81, user name 85, password 83, transmission time, description language type is described. ing. For example, the MFP 1 changes the processing content of the print job 75 based on the data set in the header of the received print job 75. 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. 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. For printer languages other than PJL, the setting state of the user name 85 or the like can be detected by determining the contents defined in each language.

  Also, the MFP 1 of the present embodiment sets the storage area for storing the security printing job 75A and the storage area for storing the accumulated printing job 75B in the storage areas of the memory 15 to be different areas. FIG. 4 schematically shows the state of the storage area of the memory 15. For example, the MFP 1 sets in the storage area of the memory 15 a secure print storage area 51 for storing the secure print job 75A and an accumulated print storage area 52 for storing the accumulated print job 75B. 75 is stored. FIG. 4 schematically shows, for example, a state in which print jobs 75 received later are stacked on each of the security print storage area 51 and the storage print storage area 52.

  FIG. 5 shows a state transition of a screen displayed on the touch panel 21 (see FIG. 1) of the MFP 1. Steps 11 to 17 in FIG. 5 (hereinafter simply referred to as “S”) are processes related to the security printing function. S19 to S29 are processes related to a login operation to the MFP 1. For example, after turning on the power and executing the control program 71 to start the system, the MFP 1 displays the standby screen 91 shown in the upper left of FIG. The MFP 1 displays a function icon 93 for selecting a FAX function, a copy function, a scan function, and the like at the center of the standby screen 91. Further, the MFP 1 displays a user display field 95 for displaying the currently selected user name on the upper left of the standby screen 91. Since nobody is logged in when the power is turned on, the MFP 1 displays on the user screen column 95 a state in which a public user indicating a logout state is selected on the standby screen 91. The MFP 1 of this embodiment processes a print job 75 of a user who is not registered in the authentication DB 73 as a print job 75 of this public user. In a state where the standby screen 91 is displayed, a function (such as a scan function) according to the authority (see FIG. 2) permitted to the public user can be executed.

  For example, in S <b> 11 of FIG. 2, when the user scrolls the standby screen 91 to the left, the MFP 1 displays the first standby screen 91 </ b> A on the touch panel 21. The MFP 1 displays a 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 by the user (S13), the MFP 1 displays the user selection window 100 on the touch panel 21. In the user selection window 100, the name of the user who has stored the security printing job 75A in the security printing storage area 51 is displayed. As will be described later, the user name displayed in the user selection window 100 includes a user name not registered in the authentication DB 73. Therefore, the MFP 1 according to the present embodiment displays the user ID set in the print job 75 of the unregistered user stored in the secure print storage area 51 in the user selection window 100.

  When the user name in the user selection window 100 is touched (S14), the MFP 1 displays the job selection window 101. The MFP 1 displays in the job selection window 101 the job name 81 of the user's security printing job 75A selected in S14. Accordingly, when a plurality of security printing jobs 75A related to one user are stored, all related job names 81 are displayed. The MFP 1 displays the attached file name of the received mail related to the user selected in S14 in the received mail received from the mail server 43 on the job selection window 101.

  When the job name 81 displayed on the job selection window 101 is touched (S15), the MFP 1 displays the password input window 103. The MFP 1 displays a numeric keypad 105 for inputting a password and a password input field 106 on the password input window 103. When the password 83 is input in the password input field 106, the MFP 1 determines whether the input password 83 matches the password 83 set in the security print job 75A selected in the job selection window 101. (S17). When the password 83 matches (S17), the MFP 1 prints an image related to the security print job 75A.

  Note that the MFP 1 also processes the received mail as a print job and executes print processing. For example, when an attached file name (such as “attached file 1”) is selected in the job selection window 101 (S15), the MFP 1 inputs a password associated with the attached file name selected in the job selection window 101 and a password. It is determined whether or not the password 83 input in the field 106 matches (S17). The password associated with the attached file is, for example, a password issued by the MFP 1 and is a password described in an email returned by the MFP 1 upon receipt of the email. When the password 83 matches, the MFP 1 prints the attached file of the received mail (S17).

  5, when the user touches the user display column 95 displaying the public user, the MFP 1 displays a user selection window 109. In the user selection window 109, the user name 111 registered in the authentication DB 73 is displayed. After the user name 111 registered in the authentication DB 73 is displayed on the user selection window 109, when any one of the user names 111 on the user selection window 109 is touched (S21), the MFP 1 inputs the PIN number 113 to input the PIN number 113. An input window 121 is displayed. 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 to the PIN number input field 124 using the numeric keypad 123, the MFP 1 includes the input PIN number 113 and the PIN number 113 associated with the user name 111 selected in the user selection window 109. Are matched (S23). When the PIN number 113 matches, the MFP 1 permits login. Although details will be described later, when the accumulated print job 75B associated with the logged-in user is accumulated in the memory 15, the MFP 1 prints all accumulated accumulated print jobs 75B (S23). The MFP 1 stores the received mail print data (attached file) when the print data of the received mail associated with the logged-in user is stored in the memory 15 and the logged-in user is authorized to print. Etc.) are printed (S23).

  The MFP 1 displays a second standby screen 91B after login. The MFP 1 displays the name of the logged-in user (for example, “inoue”) in the user display field 95 of the second standby screen 91B. In this state, the logged-in user can execute only the functions permitted by the authentication DB 73. Therefore, the MFP 1 limits the execution authority of each user by limiting the function 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 MFP 1 does not have to display the function icon 93 of the function for which the logged-in user has no authority, that is, the function that cannot be executed, on the second standby screen 91B. Even when the second standby screen 91B is operated and the function icon 93A for security printing is operated, the processes of S13 to S17 are executed. When the security printing function icon 93A is operated from the second standby screen 91B after login, the job selection after the login user is selected in the user selection window 100 without displaying the user selection window 100 is displayed. The window 101 may be displayed.

  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 for selecting whether to execute logout on the logout window 126. When the “YES” selection key 125 for instructing execution of logout is touched (S27), the MFP 1 displays a standby screen 91 on the touch panel 21. This completes logout. Further, when a predetermined time has elapsed while the second standby screen 91B is displayed, the MFP 1 returns the display on the touch panel 21 from the second standby screen 91B to the standby screen 91 (S29). This fixed time is, for example, 30 seconds to 1 minute.

(3. Operation of MFP1)
Next, the operation of the MFP 1 according to the present embodiment will be described with reference to FIGS. FIG. 6 shows the flow of main processing for processing the print job 75. For example, after the MFP 1 is turned on and the control program 71 is executed by the CPU 12 to start the system, the MFP 1 executes the main process shown in FIG. In the following description, a printing process based on the print job 75 will be mainly described. Since the printing process based on the received mail can be executed in the same manner as the print job 75, the description thereof will be omitted as appropriate.

  Note that the sequence diagrams and flowcharts in this specification basically show processing of the CPU 12 in accordance with instructions described in a program (such as the control program 71). That is, processes such as “determination”, “reception”, “acquisition”, “acceptance”, “control”, and “setting” in the following description represent processes of the CPU 12. The processing by the CPU 12 includes hardware control.

(3-1. Main processing)
First, in S <b> 33 of FIG. 6, the CPU 12 of the MFP 1 determines whether or not a print job 75 has been received. As will be described later, after executing S41 and the like, the CPU 12 executes S33 again. Therefore, after starting the system, the CPU 12 determines whether or not the print job 75 has been received periodically. If the CPU 12 determines that the print job 75 has been received (S33: YES), it executes the job accumulation determination process of S35. On the other hand, when determining that the print job 75 has not been received (S33: NO), the CPU 12 executes S37. For example, when receiving a plurality of print jobs 75, the CPU 12 processes the plurality of print jobs 75 in the order received.

  In S37, the CPU 12 determines whether or not the user has logged in. The CPU 12 determines that the user has logged in when the processes of S19 to S23 in FIG. 5 are performed. In S37 and subsequent steps, the CPU 12 executes processing related to the accumulated printing in S19 and subsequent steps in FIG. When determining that the user has logged in (S37: YES), the CPU 12 determines whether there is a stored print job 75B associated with the logged-in user among the stored print jobs 75B stored in the memory 15 (S39). . Specifically, among the accumulated printing jobs 75B accumulated in the accumulated printing storage area 52 of the memory 15, the user name 85 set to “PRINT_USER” is registered in the authentication DB 73 for the logged-in user. If the user name 111 matches, it is determined that there is an accumulated print job 75B associated with the logged-in user. If the print job 75 stored in the storage area 52 for storing and printing in the memory 15 is a received mail, and if there is a print job 75 having a sender mail address that matches the mail address 117 registered in the authentication DB 73, the login job It is determined that there is an accumulated print job 75B associated with the user who has performed. If the CPU 12 determines that there is an accumulated printing job 75B of the logged-in user (S39: YES), the printing unit 16 performs printing of the accumulated printing job 75B (S41). In this case, all the print jobs 75 stored in the memory 15 are automatically printed without requesting the user to select a job or input a password. Thereby, the complexity of operation by the user can be eliminated.

  After executing S41, the CPU 12 executes the processing from S33 again. If the CPU 12 is not logged in by the user 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 processing from S33. To do. Then, the CPU 12 determines reception of a new print job 75 in S33. After NO is determined in S41 or S37, the CPU 12 executes the function of the MFP 1 in accordance with the operation contents of the user operating the touch panel 21 such as the print processing of the secure print job 95A shown in S11 to S17 in FIG. To do.

(3-2. Job accumulation determination process)
Next, the contents of the job accumulation determination process in S35 of FIG. 6 will be described with reference to FIG. When the job accumulation determination process is executed, a newly received print job 75 exists in S33 of FIG. 6 (S33: YES). The CPU 12 executes the processing from S43 onward with the newly received print job 75 as the print job 75 to be processed.

  First, in step S43, the CPU 12 determines whether the user name 85 is set for the print job 75 to be processed. For example, when a valid value is set in the “PRINT_USER” variable (see FIG. 3) in the print job 75, the CPU 12 determines that the user name 85 is set in the print job 75 to be processed ( (S43: YES), S45 is executed. 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 (S43: NO), the CPU 12 discards the print job 75 to be processed without storing it in the memory 15 (S44). When executing S44, the CPU 12 ends the job accumulation determination process and executes S37 of FIG. For example, depending on the type of printer driver, the user name 85 may not be given to the print job 75. Alternatively, some systems that transmit the print job 75 do not set the user name 85. Therefore, the MFP 1 may receive a print job 75 in which the user name 85 is not set. Therefore, the CPU 12 of this embodiment discards the print job 75 in which the user name 85 is not set. As a result, it is possible to prevent the print job 75 in which the user name 85 is not set from being continuously stored in the memory 15 without being printed and pressing the storage area of the memory 15 in advance. The CPU 12 may print the print job 75 in which the user name 85 is not set without accumulating in the memory 15.

  In S <b> 45, the CPU 12 determines whether or not 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, four user names 111 such as “inoue” are registered in the authentication DB 73 of this embodiment except “PUBLIC”. Accordingly, when the CPU 12 accesses the authentication DB 73 in S45 and the user name 85 set in the print job 75 to be processed corresponds to one of the four user names 111, the CPU 12 uses the user name 111 registered in the authentication DB 73. It is determined that there is (S45: YES). If the print job 75 is a received mail, the mail address of the transmission source and the mail address registered in the authentication DB 73 are determined. If 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 (S45: YES), the CPU 12 executes S47 and determines that the user name is not registered (S45: NO), S49 is executed.

  In S <b> 47, the CPU 12 determines whether or not printing authority is given to the user with the user name 85 set in the print job 75. As shown in FIG. 2, in the authentication DB 73 of this embodiment, printing authority is given to the users “inoue”, “kato”, and “hayashi” of the user name 111 (see the printing authority flag 114). Accordingly, when the user name 85 of the print job 75 to be processed is “inoue”, “kato”, or “hayashi”, the CPU 12 determines that the user has print authority (S47: YES), and executes S51. .

  On the other hand, if the CPU 12 determines that the user does not have printing authority (S47: NO), the CPU 12 discards the print job 75 to be processed (S53) and ends the job accumulation determination process. As a result, since the user does not have print authority, it is possible to prevent the print job 75 from being stored in the memory 15 without being able to execute the stored printing and suppressing the storage area of the memory 15 from being compressed.

  In S51, the CPU 12 determines whether or not the password 83 is set for the print job 75 to be processed. For example, when a valid value is set in the variable “JOB_PASSWORD” (see FIG. 3) in the print job 75, the CPU 12 determines that the password 83 is set in the print job 75 to be processed (S51). : YES) If the CPU 12 determines that the password 83 is set for the processing target print job 75 (S51: YES), the processing target print job 75 is set as the security printing job 75A and the security printing storage area 51 (see FIG. 4). (S55), and the job accumulation determination process is terminated. Therefore, the CPU 12 of the present embodiment stores a user print job 75 registered in the authentication DB 73 as a security print job 75A if the print job 75 is set with the password 83. If the CPU 12 determines that the password 83 is not set for the print job 75 to be processed (S51: NO), the CPU 12 stores the print job 75 to be processed in the accumulated print storage area 52 as the accumulated print job 75B. (S57) The job accumulation determination process ends.

  In step S49, the CPU 12 determines whether printing authority is given to the public user in the authentication DB 73. As shown in FIG. 2, printing authority can be set for the public user of this embodiment (see the printing authority flag 114). If the CPU 12 determines that the printing authority is not granted to the public user (S49: NO), it executes S53 and discards the print job 75 to be processed.

  On the other hand, if the CPU 12 determines that the printing authority is granted to the public user (S49: YES), the CPU 12 stores the print job 75 to be processed in the security printing storage area 51 as the security printing job 75A (S59). Therefore, the CPU 12 of this embodiment stores the print job 75 of the unregistered user as the security print job 75A when the printing authority is given to the public user. After the unregistered user is registered in the authentication DB 73, the CPU 12 can process the registered user's security print job 75A as the accumulated print job 75B. The CPU 12 may accumulate the print job 75 of the unregistered user as the security print job 75A regardless of the print authority of the public user. In this case, the CPU 12 may execute S59 after S45 (S45: NO).

  After executing S59, the CPU 12 executes S61. In S61, the CPU 12 executes notification to the system administrator and notification to the transmission source. For example, the CPU 12 may make a notification via the status monitor of the sender's PC 41 that has transmitted the print job 75. The status monitor here is, for example, a window that is displayed by the printer driver on the user's PC 41 and displays various information relating to printing such as the printing status of the transmitted print job 75 and the remaining amount of ink in the destination MFP 1. It is. For example, the CPU 12 may notify the PC 41 that is the transmission source of the print job 75 that the user name 85 and that the user name 85 has been stored as the security print job 75 </ b> A because the user name 85 is not registered in the authentication DB 73. Thereby, the user of the transmission source can execute an appropriate response such as requesting registration from the system administrator by confirming the content of the notification.

  Further, the CPU 12 may send a notification that the print job 75 from the unregistered user has been received to the e-mail address of the system administrator registered in advance in the MFP 1 by e-mail. For example, the CPU 12 may describe the user name 85 of the accumulated security print job 75 </ b> A and the URL for performing EWS user registration in an email transmitted to the system administrator. Thereby, the system administrator can reduce the burden of registration work, for example, by clicking the URL in the mail and copying and pasting the user name 85 for registration. Further, since the CPU 12 receives the mail as the print job 75 and the transmission source mail address of the mail is not registered in the authentication DB 73, when the CPU 12 stores it as the security print job 75 </ b> A, the mail address or print job of the system administrator is stored. 75 sender email addresses may be notified of unregistered email addresses and unregistered email addresses.

  Further, for example, when an application for managing the accumulation state of the print job 75, the execution state of printing, the occurrence of an error, etc. is installed in the PC 41 of the system administrator, the accumulation is performed in S59 via the application. The user name 85 of the security print job 75A may be displayed, and a display prompting registration of the user in the authentication DB 73 may be executed.

  For example, the CPU 12 may display on the touch panel 21 that the print job 75 of the unregistered user has been accumulated. Further, the CPU 12 may have a configuration capable of executing notification from the touch panel 21 to the system administrator. For example, as shown in the user selection window 100 in FIG. 5, the CPU 12 may display a notification button 107 that requests notification to the system administrator. Then, when the notification button 107 of the user selection window 100 is touched, the CPU 12 may transmit a user registration request mail to the system administrator. Accordingly, the user can request registration to the system administrator by operating the touch panel 21. After executing S61, the CPU 12 ends the job accumulation determination process.

(3-2. Authentication DB update process)
Next, update processing of the authentication DB by the system administrator will be described with reference to FIG. For example, when the CPU 12 receives an operation for displaying the authentication DB management page on the EWS Web page, the CPU 12 starts the authentication DB update process shown in FIG.

  For example, the system administrator operates the PC 41 to access the EWS of the MFP 1 and performs an operation to display the authentication DB management page. The authentication DB management page is a page in which the user name, PIN number, setting of each function authority, and mail address, which are registered information registered in the authentication DB, can be updated as a user list in response to an operation input. The CPU 12 creates an authentication DB management page according to information registered in the authentication DB 73 in response to an operation input to the EWS. The CPU 12 transmits the created authentication DB management page as a user list to the PC 41 and displays it on the PC 41 (S65 in FIG. 8). The system administrator confirms the user list displayed on the PC 41 and performs an update process for the authentication DB 73 such as a registration process for unregistered users.

  The CPU 12 determines whether the registered content received on the Web page is deletion of the registered user registered in the authentication DB 73 or change of the printing authority of the registered user (OK → NG) (S66). If neither the registered user deletion nor the registered user print authority change (OK → NG) (S66: NO), the CPU 12 determines whether or not an unregistered user has been registered as a user having the print authority ( S67). When the CPU 12 determines that an unregistered user has been registered as a user having printing authority (S67: YES), the CPU 12 stores the security printing job 75A of the newly registered user as an accumulated printing job 75B (S69). If the newly registered user's security printing job 75A is not registered in the security printing storage area 51, the process ends without processing S69. When registration of a plurality of unregistered users is received, the process of S69 is executed for each user who has received registration.

  A case where “USER_Y” which is an unregistered user is newly registered will be described with reference to FIG. For example, if the CPU 12 determines that “USER_Y” has been registered as a user with printing authority in S 67, the security printing job 75 A of “USER_Y” out of the security printing jobs 75 A accumulated in the security printing storage area 51. Then, the process proceeds to the storage area 52 for accumulated printing (S69). As a result, as shown on the right side of FIG. 4, the accumulated printing job 75 </ b> B (USER_Y_JOB <b> 1) of “USER_Y” is accumulated in the accumulated printing storage area 52. Further, the security printing job 75A of “USER_Y” is deleted from the security printing storage area 51. The accumulated printing job 75B of “USER_Y” is stored as the accumulated printing job 75B received at the top of the accumulated printing storage area 52, that is, the latest. The CPU 12 does not have to store the print job 75 to be transferred at the end of the storage area 52 for storage printing. For example, the CPU 12 may compare information on the transmission time of the print job 75 and store the security printing job 75A to be transferred in a position in the order of transmission time in the storage area 52 for accumulated printing. When executing S69, the CPU 12 ends the security printing job process shown in FIG.

  On the other hand, if the CPU 12 determines in S67 that an unregistered user has been registered as a user who does not have printing authority (S67: NO), the newly registered user's security printing job 75A is stored from the security printing storage area 51. Delete (S71). As a result, it is possible to suppress the occurrence of a situation in which the security printing job 75A of the registered user who does not have the printing authority is continuously stored in the memory 15. After executing S71, the CPU 12 ends the security printing job process.

  If the CPU 12 determines in S66 that the registered content received on the Web page is deletion of the registered user registered in the authentication DB or change of the printing authority of the registered user (OK → NG) (S66: YES) ) The accumulated printing job 75B and the security printing job 75A of the user to be deleted or the registered user who does not have the printing authority are discarded from the memory 15 (S73). Accordingly, it is possible to suppress the occurrence of a situation in which the accumulated printing job 75B and the security printing job 75A are continuously stored in the memory 15 without being printed due to a change in printing authority or registration deletion.

  The content of the authentication DB update process shown in FIG. 8 is an example. For example, when the system administrator who receives the mail operates the link destination included in the received mail, the registration process of the user name included in the received mail in the authentication DB 73 may be performed. Further, the CPU 12 may display a Web page that can be accepted by EWS that an unregistered user who has accumulated the security printing job 75A is not registered. When the system administrator accepts that an unregistered user is not registered, the security print job 75A in which the unregistered user name 85 is set may be deleted from the security print storage area 51. Further, the CPU 12 may delete the security printing job 75 </ b> A that has accumulated for a predetermined time in the security printing storage area 51. In this case, the CPU 12 may notify the system administrator or the like of the deletion.

  Here, as described in S59 of FIG. 7 described above, a print job 75 from a user who is not registered in the authentication DB 73 is stored in the memory 15 as a security print job 75A. As a result, even when the registration from the system administrator is not in time for the timing when the user needs the printed matter, the print job 75 is operated by operating the function icon 93A for printing the security print job 75A. Can be printed. On the other hand, when printing is performed as the security printing job 75A, the user name 85 may be set in the print job 75 transmitted from the unregistered user, but the password 83 may not be set. As a result, even if an unregistered user operates the touch panel 21 and selects his or her job name 81 in the job selection window 101, there is no password to be input. The user name 85 is set in the security printing job 75A stored in S59 (S43: YES). Therefore, the CPU 12 may use the user name 85 set in the security print job 75 </ b> A instead of the password 83. For example, when the user name of an unregistered user is selected in the user selection window 100 and the job name 81 is selected in the job selection window 101, the CPU 12 inputs the user name 85 of the unregistered user in the password input window 103. On this condition, the selected security printing job 75A is printed. Thereby, an unregistered user can execute printing using the user name 85 without waiting for registration.

  Note that the CPU 12 may not use the user name 85 instead of the password 83. In this case, the print job 75 of the unregistered user for which the password 83 is not set may be printable only as the accumulated print job 75B after registration. Thereby, the security of the printing process can be improved. The CPU 12 displays the user name in the user selection window 100 and the job name 81 in the job selection window 101 after a predetermined time has elapsed after storing the security printing job 75A in the security printing storage area 51 in S59. May be. This predetermined time is, for example, a time required for registration of the system administrator. Thereby, it can suppress that the job name 81 of the unregistered user of the registration plan is seen by other users.

  Incidentally, the MFP 1 is an example of a printing apparatus. 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 and a display unit. The network interface 24 is an example of a communication unit. The security printing storage area 51 is an example of an authentication job storage area. The storage area for storage printing 52 is an example of a job storage area. The authentication DB 73 is an example of a restriction table. The security print job 75A is an example of an authentication print job. User names 85 and 111 are examples of user information. The password 83 is an example of job authentication information.

(4. Effect)
As mentioned above, according to above-mentioned embodiment, there exist the following effects.
(1) The MFP 1 (printing apparatus) of the present embodiment includes a memory 15 that stores an authentication DB 73 including a user name 111, a network interface 24, a touch panel 21 that receives an operation, a printing unit 16 that prints an image, and a CPU 12. And comprising. The CPU 12 receives the first reception process (S33) for receiving the print job 75 associated with the user name 85 via the network interface 24, and the user name 85 associated with the print job 75 received by the first reception process. A determination process (S45) for determining whether or not it is registered in the authentication DB 73 stored in the memory 15, and if it is determined that it is registered as a result of the determination process, the print job 75 is stored in the storage area 52 for storing and printing. (S57), and when it is determined that the print job 75 is not registered, the print job 75 is stored in an area (security print storage area 51) different from the storage area 52 for storage print (S59) a first storage process; In response to accepting the user name 85 via the touch panel 21, the login state is set to execute the function of the own device. Of the print jobs 75 stored in the storage area for accumulated printing 52 of the memory 15, the acquisition process (S39) for acquiring the print job 75 associated with the user name 85 received via the touch panel 21, and the acquisition process When the first print process (S41) for printing the image related to the acquired print job 75 by the printing unit 16 and the user name 111 in the authentication DB 73 are updated, the user name 111 associated with the newly added user name 111 is updated. If the print job 75 is stored in a different area, a second storage process (S69) for storing the print job 75 in the storage area 52 for accumulated printing is executed.

  According to this, in response to a login operation by the user, the print job 75 stored in the storage area 52 for accumulated printing and associated with the user name 85 of the login user is executed. Further, a print job 75 associated with an unregistered user name 85 is stored in a predetermined area (different area), and when a new user name 111 is added to the authentication DB 73, the print job 75 associated with the user name 111 is associated. The print job 75 is stored in the storage area 52 for accumulated printing. For example, when a new user who uses the MFP 1 requests registration from the system administrator but the registration work is delayed, the print job 75 of the new user is immediately stored without being stored in the MFP 1. This may reduce convenience. On the other hand, even if the user registration is not in time when the print job 75 is received, if the user is registered as a new user in the authentication DB 73, the print job 75 associated with the new user name 111 is stored in the storage area 52 for storing and printing. And can be executed at login. As a result, even a print job 75 received before registration of the user name 111 can be printed after registration, and user convenience can be improved.

(2) Further, if the CPU 12 determines that it is not registered in the authentication DB 73 as a result of the determination process, the CPU 12 notifies information including the user name 85 associated with the received print job 75 to a previously registered notification destination. The user information notification process (S61) is executed. According to this, by appropriately registering the contact information of the system administrator or the like as the notification destination in the MFP 1, the system administrator or the like who has received the notification can take appropriate measures such as registering the user in the authentication DB 73 as necessary. Can be executed.

(3) If the CPU 12 determines that it is not registered in the authentication DB 73 as a result of the determination process, the CPU 12 sends information indicating that it has not been registered to the transmission source device (such as the PC 41) of the received print job 75. An unregistered information notification process to be notified (S61) is executed. Accordingly, the user who has received the notification can recognize that printing cannot be performed due to unregistered information. The user who has received the notification can take appropriate measures such as requesting the system administrator for user registration.

(4) The MFP 1 includes the touch panel 21. The CPU 12 receives, via the network interface 24, the second reception process (S33) for receiving the security print job 75A associated with the password 83 and the security print job 75A received by the second reception process in the memory 15. Third storage processing (S55) stored in the security printing storage area 51, display processing (S14) for displaying a job list related to the security printing job 75A accumulated in the security printing storage area 51 on the touch panel 21, and the touch panel When the password 83 associated with the security printing job 75A selected from the job list displayed on the screen 21 matches the password 83 received via the touch panel 21, the selected security printing job 75A is selected. In charge of Second printing process for printing by the printing unit 16 an image and (S17), the execution. A different area of the present embodiment is a security printing storage area 51.

  According to this, the print job 75 transmitted by the unregistered user is stored in the security print storage area 51. Therefore, even if the print job 75 is transmitted by an unregistered user, it can be confirmed from the job list that the print job 75 is accumulated.

(5) When the security printing job 75A stored in the security printing storage area 51 by the first storage processing is selected from the job list displayed on the touch panel 21, the CPU 12 replaces the password 83 with a security On the condition that the user name 85 associated with the print job 75A is input from the touch panel 21, the third print processing (S17) is performed in which the printing unit 16 prints an image related to the selected security print job 75A. To do.

  According to this, a print job 75 of a user not registered in the authentication DB 73 can be printed by inputting the user name 85. Thereby, the convenience of an unregistered user can be improved, maintaining a fixed security level.

(6) The MFP 1 has both a printing function and a scanner function. In the authentication DB 73, the availability of each function is registered in association with the user name 111 (see FIG. 2). The CPU 12 executes a discarding process (S53) for discarding the print job 75 associated with the user name 111 registered in the case of not using the print function.

  According to this, since the print job 75 of the user name 111 (for example, “minami”) that does not use the print function is discarded without being stored in the memory 15, the storage area of the memory 15 is wasted. Can be suppressed.

(7) In addition, when the user name 111 in the authentication DB 73 is deleted, if the print job 75 associated with the user name 111 is stored in the accumulated print storage area 52 after the update, the CPU 12 prints the print job 75. Is deleted from the storage area 52 for accumulated printing (S73). Thereby, it is possible to suppress the occurrence of a situation in which the accumulated printing job 75B is continuously stored in the memory 15 without being printed due to the registration deletion.

(5. Modifications)
Needless to say, the present application is not limited to the above-described embodiment, and various improvements and modifications can be made without departing from the spirit of the present invention.
For example, although not particularly mentioned in the above embodiment, the security printing storage area 51 and the storage printing storage area 52 may have different address ranges in one memory 15 or may have a configuration in which the address ranges overlap each other. good. For example, the CPU 12 may manage each print job 75 with identification information, and associate attribute information indicating that the job is a security printing job 75A or a stored printing job 75B with the identification information. In this case, even if the address ranges of the security printing storage area 51 and the storage printing storage area 52 overlap, the CPU 12 performs the print job 75 stored in the memory 15 based on the identification information and the attribute information. Can be determined whether the job is a security printing job 75A or an accumulated printing job 75B.
Further, the security printing storage area 51 and the storage printing storage area 52 may be provided in separate memories 15.
Further, the CPU 12 does not have to execute the process of notifying the information of the unregistered user in S61 (user information notification process or unregistered information notification process). The CPU 12 may notify the system administrator or one of the transmission source users in S61. Further, the CPU 12 may notify the information of unregistered users to users and devices other than the system administrator and the transmission source user.
In addition, although the CPU 12 discards the print job 75 associated with the user name 111 registered to reject the use of the print function in S53, it may continue to be stored in the memory 15 without being discarded. Further, the CPU 12 moves the print job 75 of the user deleted from the authentication DB or the user changed to not use the print function from the accumulated print storage area 52 to the secure print storage area 51 without discarding it. It may be memorized. In this case, when the public of the authentication DB 73 has the print authority, it is stored as the secure print job 75A, and when the public does not have the print authority, the print job 75 associated with the user is deleted from the memory 15 ( (Discard).

The MFP 1 includes the touch panel 21 as an operation unit that receives a login operation. However, the MFP 1 may have a configuration in which a login operation can be performed by another method. For example, the MFP 1 may determine whether to allow login based on data received from the mobile terminal. The user may input the user name 85 and the PIN number 113 on the portable terminal and transmit the input to the MFP 1 to perform a login operation. In this case, the communication unit that communicates with the mobile terminal is an example of the operation unit of the present application.
Moreover, in the said embodiment, although CPU12 which executes a predetermined program as a control part of this application was adopted, it is not restricted to this. For example, the control unit may be configured by dedicated hardware such as ASIC (Application Specific Integrated Circuit). In addition, the control unit may be configured to operate using, for example, software processing and hardware processing together.
In the above-described embodiment, the MFP 1 that is a multifunction peripheral is used as the printing apparatus of the present application, but the present invention is not limited to this. The printing apparatus of the present application may be a printer apparatus having only a printing function.

  DESCRIPTION OF SYMBOLS 1 MFP (printing apparatus), 12 CPU (control part), 15 Memory (storage part), 16 Printing part, 21 Touch panel (operation part, display part), 24 Network interface (communication part), 51 Security printing storage area ( Authentication job storage area), 52 storage print storage area (job storage area), 73 authentication DB (restriction table), 75 print job, 75A security print job (authentication print job), 83 password (job authentication information), 85, 111 User name (user information).

Claims (7)

A storage unit for storing a restriction table including user information;
A communication department;
An operation unit for receiving an operation;
A printing section for printing an image;
A control unit,
The controller is
A first reception process for receiving a print job associated with the user information via the communication unit;
A determination process for determining whether the user information associated with the print job received by the first reception process is registered in the restriction table stored in the storage unit;
As a result of the determination process, the print job is stored in the job storage area of the storage unit when it is determined that it is registered, and the print job is stored in a different area from the job storage area when it is determined that it is not registered A first storage process stored in
Among the print jobs stored in the job storage area of the storage unit, when the user information is received via the operation unit and the login state is set to execute the function of the own apparatus, An acquisition process for acquiring a print job associated with the user information received via the operation unit;
A first print process for printing an image related to the print job acquired by the acquisition process by the printing unit;
When the user information in the restriction table is updated, if the print job associated with the user information newly added after the update is stored in the different area, the print job is stored in the job accumulation area. A second storage process stored in
Run the printing device. The controller is
As a result of the determination process, when it is determined that the information is not registered in the restriction table, a user information notification process for notifying a previously registered notification destination of information including the user information associated with the received print job is performed. The printing apparatus according to claim 1, wherein the printing apparatus is executed. The controller is
As a result of the determination process, if it is determined that it is not registered in the restriction table, an unregistered information notification process for notifying information indicating that it has not been registered is executed to the device that has transmitted the received print job. The printing apparatus according to claim 1 or 2. With a display,
The controller is
A second reception process for receiving an authenticated print job associated with job authentication information via the communication unit;
A third storage process for storing the authentication print job received in the second reception process in an authentication job storage area of the storage unit;
A display process for causing the display unit to display a job list related to the authentication print job stored in the authentication job storage area;
The job authentication information associated with the authenticated print job selected from the job list displayed on the display unit matches the job authentication information received via the operation unit. A second printing process for printing an image related to the authentication print job by the printing unit;
Run
The different areas are
The printing apparatus according to claim 1, which is the authentication job storage area. The controller is
When the print job stored in the authentication job storage area by the first storage process is selected from the job list displayed on the display unit, it is associated with the print job instead of job authentication information. 5. The printing apparatus according to claim 4, wherein a third printing process for printing an image related to the selected print job by the printing unit is performed on the condition that the user information is input by the operation unit. The printing apparatus includes:
It has both a printing function and a scanner function.
The restriction table is
The availability of each function is registered in association with the user information,
The controller is
The printing apparatus according to claim 1, wherein a discarding process for discarding the print job associated with the user information registered when the use of the print function is not performed is executed. The controller is
When the user information in the restriction table is deleted, if the print job associated with the user information after update is stored in the job storage area, the print job is deleted from the job storage area. The printing apparatus according to any one of claims 1 to 6.

Images