Printing device and printing system

Abstract

To provide a technique that can restrict the other person from cancelling reception of a printing job for storage-type printing, during the reception of the printing job.SOLUTION: A CPU 101 of an MFP 100 continues reception of a printing job, without cancelling the reception of the printing job due to input of an instruction for canceling the reception of the printing job from a cancel key 105b3 included in a key input part 105b of a panel 105, during the reception of the printing job including a user's name, in storage-type printing.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] This application relates to a technology for storing a received print job in a memory and then performing stored printing in response to a user's login. [Background technology]

[0002] Patent Document 1 describes a printing device that stores a received print job in a memory and then performs stored printing in response to a user logging in. [Prior art documents] [Patent documents]

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

[0004] However, in the printing device described in Patent Document 1, there is a risk that while a print job for stored printing is being received, the reception of the print job may be canceled by someone other than the user who sent the print job, such as the operator currently operating the printing device.

[0005] An object of the present application is to provide a technique for restricting a person from canceling the reception of a print job for stored printing while the print job is being received. [Means for solving the problem]

[0006] In order to achieve the above object, the printing device of the present application is a printing device equipped with a communication interface, a user interface, a memory, and a controller, and when the controller receives a print job including a user name from the communication interface, it stores the print job in memory without printing based on the print job, and then a user name is input from the user interface to log in, and if the receiving user name and the input user name match, it executes an accumulated printing process in which printing based on the accumulated print job is executed, and if an instruction to cancel printing based on the print job is input from the user interface during execution of printing based on the accumulated print job by the accumulated printing process, it executes a print stop process in which printing based on the print job is stopped when an instruction to cancel printing based on the print job is input from the user interface, the receiving user name is the user name included in the received print job, and the input user name is the user name input from the user interface, and the controller continues receiving the print job without canceling reception of the print job due to an instruction to cancel reception of the print job being input from the user interface while receiving the print job including the user name in the accumulated printing process. Effect of the Invention

[0007] According to the present invention, it is possible to restrict a third party from canceling the reception of a print job for storage printing while the print job is being received. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a block diagram of a printing system according to an embodiment of the present application. [Diagram 2] 2A to 2C are diagrams illustrating an example of a change in the state of a panel in response to a change in the internal state of the MFP in FIG. [Diagram 3] 3 is a diagram showing an example of a change in state of a panel different from that shown in FIG. 2. [Figure 4] 2 is a diagram showing an example of various data stored in the NVM of the MFP in FIG. 1. [Diagram 5] FIG. 4 illustrates an example of a data configuration of a print job. [Figure 6] 13 is a flowchart showing a procedure of a reception and printing process. [Figure 7] 7 is a flowchart showing a continuation of the reception and printing process of FIG. 6; [Figure 8] 13 is a flowchart showing a procedure for a panel operation process. [Figure 9] 13 is a flowchart showing a procedure of a display process. [Figure 10] 13 is a flowchart showing a procedure of a login process. [Figure 11] 2 is a flowchart showing the procedure of a browser process on the PC side and a main process on the MFP side in FIG. 1. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of the present application will be described in detail with reference to the drawings. Fig. 1 shows a control configuration of a printing system 1 including an MFP 100 (an example of a "printing device") according to an embodiment of the present application. The printing system 1 includes an MFP 100 and a PC 10 (an example of an "information processing device"). Note that MFP is an abbreviation for multifunction peripheral.

[0010] The MFP 100 is a multifunction machine equipped with a fax function, a copy function, a scan function, and a print function. The MFP 100 includes a CPU 101, a ROM 102, a RAM 103, and an NVM 104. Note that NVM is an abbreviation for non-volatile memory.

[0011] The CPU 101 controls the entire MFP 100. The ROM 102 is a memory that stores programs used at startup, such as a boot loader. The NVM 104 is a non-volatile memory that stores control programs (including programs for reception and printing processing (FIGS. 6 and 7), panel operation processing (FIG. 8), display processing (FIG. 9), and login processing (FIG. 10) described later) and also stores setting information and the like. The CPU 101 reads out the control programs stored in the NVM 104 and executes various processes. The RAM 103 is a memory that temporarily stores print jobs, image data, and the like. The RAM 103 is also used as a storage area that temporarily stores data, signals, and the like used by the CPU 101 when executing the control programs, or as a work area for data processing.

[0012] Moreover, MFP 100 has a panel 105 (which is an example of a "user interface" and also an example of a "display"). Panel 105 has a display unit 105a and a key input unit 105b. In this embodiment, display unit 105a is configured with a touch panel that allows touch operations, and various screens are displayed on display unit 105a depending on the state of MFP 100. A user of MFP 100 can perform input operations by touching input buttons displayed on the screen. Key input unit 105b is configured with multiple keys (e.g., three) and can be switched between a lit state and an unlit state for each key, for example, by switching a backlight on and off.

[0013] Furthermore, the MFP 100 includes a network IF 108 (an example of a "communication interface"). The network IF 108 connects the MFP 100 to a communication network 40. In this embodiment, the PC 10 is connected to the communication network 40, so that the MFP 100 can transmit and receive various data to and from the PC 10. The communication network 40 may be any of various types of networks. For example, it may be a wired or wireless LAN, a WAN, or the like.

[0014] The MFP 100 also includes a local IF 109. The local IF 109 is for locally connecting to an external device such as the PC 10A, a HDD, or a CD-ROMD at a short distance. The connection method may be USB, NFC, or the like. NFC is an abbreviation for near field communication. In this embodiment, a USBIF is adopted as the local IF 109.

[0015] The MFP 100 also includes a print engine 111 and a read engine 112. The print engine 111 is an electrophotographic print engine. The print engine may be of an inkjet type, a thermal type, or the like. The read engine 112 is a mechanism for reading an image from a document, and includes a sensor such as a CCD or a CIS.

[0016] The CPU 101, the ROM 102, the RAM 103, the NVM 104, the panel 105, the network IF 108, the print engine 111, and the reading engine 112 are connected to each other via a bus 130.

[0017] In this specification, the term basically refers to the processing of the CPU 101 according to the instructions written in the program. In other words, the processing of "judgment," "extraction," "selection," "calculation," "decision," "identification," "acquisition," "acceptance," "control," "setting," and the like in the following description represents the processing of the CPU 101. The processing by the CPU 101 also includes hardware control via the OS. Note that "acquisition" is used as a concept that does not require a request. In other words, the processing of the CPU 101 receiving data without a request is also included in the concept of "the CPU 101 acquiring data." In addition, "data" in this specification is represented by a bit string that can be read by a computer. Data that has the same substantial meaning but different formats is treated as the same data. The same applies to "information" in this specification. In addition, the processing of "command," "response," "request," and the like is performed by communicating information indicating the "command," "response," "request," and the like. In addition, the words "command," "response," "request," and the like may be written to mean the information itself indicating the "command," "response," "request," and the like.

[0018] When the MFP 100 is powered on, the CPU 101 executes an initialization process (not shown) and starts a panel operation process (FIG. 8), a display process (FIG. 9), and a reception and printing process (FIGS. 6 and 7). In the following explanation of the procedure of each process, steps are abbreviated as "S".

[0019] When the display process starts, in FIG. 9, first, the CPU 101 displays a home screen on the display unit 105a (S51). FIG. 2(a) shows an example of a home screen (screen ID=100) 105a1 displayed on the display unit 105a. The home screen 105a1 is configured with a “Public” button 105a11 and a function selection area 105a12 for selecting one of the FAX function, copy function, and scan function of the MFP 100. Note that a screen ID is associated with a screen displayed on the display unit 105a, and the screen display on the display unit 105a is also switched in response to switching of the screen ID. The CPU 101 writes the screen ID in a screen ID storage area (not shown) provided on the RAM 103 in S3, which will be described later, of the reception and printing process.

[0020] 8, when the panel operation process starts, CPU 101 first judges whether or not a panel operation on panel 105 has been detected (S31), and if no panel operation has been detected (S31: NO), then judges whether or not the screen ID has changed (S38), and if the screen ID has not changed (S38: NO), returns the process to S31. CPU 101 then repeats the judgments of S31 and S38 until a panel operation is detected (S31: YES) or the screen ID changes (S38: YES). The panel operation on panel 105 includes a touch operation on display unit 105a of panel 105 and a key operation on key input unit 105b of panel 105.

[0021] For example, when the "Public" button 105a11 is touched while the home screen 105a1 is displayed on the display unit 105a, the CPU 101 determines "YES" in S31 and then determines whether the panel operation is a key operation on the key input unit 105b (S32). Since the panel operation is now a touch operation on the display unit 105a (S32: NO), the CPU 101 notifies the display process of the touch operation (S37). This notification is performed, for example, by storing the information in a touch operation storage area (not shown) provided on the RAM 103. Information stored in the touch operation notification storage area as the touch operation notification is, for example, the touch position on the display unit 105a.

[0022] In the display process, after the process of S51, CPU 101 judges whether or not a key notification or a touch operation notification is detected (S52). Key notification is performed in S35 (described later) in the panel operation process. Specifically, like the touch operation notification, key notification is performed by storing it in a key notification storage area (not shown) provided on RAM 103. However, unlike the touch operation notification, the information stored in the key notification storage area as the key notification is information for identifying an operated key among the three keys of key input unit 105b. In this way, the key notification is stored in the key notification storage area, and the touch operation notification is stored in the touch operation notification storage area, so in S52, CPU 101 judges whether or not a key notification or a touch operation notification is stored in the key notification storage area or the touch operation notification storage area.

[0023] In the judgment of S52, if neither a key notification nor a touch operation notification is detected (S52: NO), CPU 101 judges whether the screen ID written in the screen ID storage area has changed (S59). If the judgment of the screen ID has not changed (S59: NO), CPU 101 further judges whether a home screen display notification has been detected (S61). If a home screen display notification has not been detected (S61: NO), CPU 101 returns the process to S52. In this way, after the process of S51, CPU 101 repeats the judgments of S52, S59, and S61 until a key notification or a touch operation notification is detected (S52: YES), until the screen ID changes (S59: YES), or until a home screen display notification is detected (S61: YES).

[0024] In the display processing, while the CPU 101 is repeatedly making the judgments of S52, S59, and S61, if a touch operation of the "Public" button 105a11 is notified by the processing of S37 described above, the CPU 101 judges "YES" in S52, and therefore next judges whether the operation is a press operation of the home key 105b2 (see FIG. 2(a)) among the three keys of the key input section 105b, and whether the pressability information of the home key 105b2 is "OK" (S53).

[0025] Fig. 4(b) shows an example of table data 104b indicating screens and key pressability according to the internal state of MFP 100. Table data 104b includes the internal state of MFP 100, a screen ID specifying a screen to be displayed on display unit 105a of panel 105 in that internal state, and key pressability information indicating whether to validate ("OK" in Fig. 4(b)) or invalidate ("NG" in Fig. 4(b)) the pressing of three keys provided on key input unit 105b of panel 105 in that internal state, specifically, back key 105b1, home key 105b2, and cancel key 105b3, when the keys are pressed, and is registered in NVM 104, for example. When the internal state of MFP 100 is "receiving print instructions", there is no screen ID (-). This is because the time during which MFP 100's internal state is "receiving print instructions" is extremely short, and therefore there is little need to switch the screen of display unit 105a to the "receiving print instructions" screen. Of course, this is not limiting, and a screen ID that identifies the "receiving print instructions" screen may be determined to display the "receiving print instructions" screen. Furthermore, display screen data 104c is also stored in NVM 104 in association with each screen ID, as shown in FIG. 4(c).

[0026] The internal state of MFP 100 is determined by having a plurality of internal states defined in advance and having CPU 101 select a state that matches the current state from the plurality of defined internal states and store the selected state in, for example, an internal state storage area (not shown) provided on RAM 103. Therefore, the internal state of MFP 100 is the internal state stored in the internal state storage area on RAM 103. CPU 101 appropriately writes the internal state to the internal state storage area on RAM 103 when it is necessary to switch from the current internal state to another internal state.

[0027] Returning to FIG. 9, since a touch operation notification, not a key notification, is detected now, the CPU 101 judges "NO" in the above S53 and checks the currently displayed screen (S54). This check is specifically performed by checking the screen ID written in the above screen ID storage area. Then, the CPU 101 judges whether or not a process that should notify a panel operation is being executed based on the confirmed screen (S55). If the screen ID confirmed in S54 is 100, the CPU 101 judges "NO", and if the screen ID is 101 to 105, the CPU 101 judges "YES". In other words, if the screen ID is 101 to 105, the CPU 101 judges that the above-mentioned reception and printing process (FIGS. 6 and 7) is being executed as a process that should notify a panel operation. Since the screen ID is now 100, the CPU 101 judges "NO" in S55 and notifies a screen update and / or process start according to the key of the key notification or the touch position of the touch operation notification (S57). The touch operation of the "Public" button 105a11 is an instruction to start the login process (FIG. 10), so in S57 the CPU 101 updates the screen in accordance with the touch position and notifies the start of the login process.

[0028] In response to this, the CPU 101 starts the login process of FIG. 10 and displays a list of users on the display unit 105a (S71).

[0029] 2(c) shows an example of a user selection screen 105a3 displayed on the display unit 105a. The user selection screen 105a3 is composed of a display area 105a31 that displays an instruction to select a user (for example, a display of "Select User"), and a user list display area 105a32 that displays a list of users. The operator of the MFP 100 can proceed to login authentication by selecting his / her own user name from the users displayed in the user list display area 105a32.

[0030] 4(a) shows an example of a user DB 104a for login management and functional restriction management. Note that DB is an abbreviation of database. The user DB 104a is created, for example, by an administrator who manages the MFP 100, and is stored in the NVM 104 of the MFP 100. The user DB 104a is composed of the following items: main body LoginUser name, PcUser name, PIN, and Function.

[0031] The main body LoginUser name is a user name used when logging in to the MFP 100. The PcUser name is an alias associated with the main body LoginUser name. In S71 above, the list of users displayed on the display unit 105a is a list of main body LoginUser names registered in the user DB 104a.

[0032] PIN is a personal identification number. The PIN is registered in advance together with the LoginUser name of the main unit and is used for login authentication of the MFP100.

[0033] Function is information for the above-mentioned function restriction management, and indicates whether or not a user with a registered main body LoginUser name can use the print function, scan function, and copy function (Print, Scan, and Copy in FIG. 4(a)). In other words, a user with a registered main body LoginUser name can use functions for which "OK" is registered, but cannot use functions for which "NG" is registered. For example, when a user with a main body LoginUser name of "suzuki" logs in to MFP100, he or she can use the print function and scan function of MFP100, but cannot use the copy function of MFP100.

[0034] Returning to FIG. 10, CPU 101 waits, for example, until a user is selected from among the users displayed in user list display area 105a32 (S72: NO), and when a user is selected (S72: YES), CPU 101 displays a PIN entry screen on display unit 105a (S73).

[0035] Next, CPU 101 waits until PIN entry is completed (S74: NO), and when PIN entry is completed (S74: YES), determines whether the entered PIN is correct (S75).

[0036] If it is determined in S75 that the entered PIN is correct (S75: YES), CPU 101 stores the login user name, i.e., the selected main body LoginUser name, in RAM 103 (S76), and then determines whether image data accumulated by the login user has been accumulated (S77). Hereinafter, the selected main body LoginUser name will be referred to as the "selected LoginUser name." CPU 101 determines whether image data associated with a main body LoginUser name that matches the selected LoginUser name has been accumulated. In S6 of FIG. 6, CPU 101 accumulates the image data in association with the main body LoginUser name that indicates the user who sent the original print job. This will be described in detail later.

[0037] If it is determined in S77 that image data has been accumulated by the logged-in user, i.e., the user indicated by the selected LoginUser name (S77: YES), CPU 101 notifies the receiving and printing process of an instruction to print the accumulated image data (S78), and then terminates the login process.

[0038] When the process proceeds from S77 to S78, there may be cases where the logged-in user has accumulated multiple pieces of image data. In this case, the file names of the multiple pieces of image data, for example, may be displayed on the display unit 105a, and the logged-in user may select the image he or she wishes to print from the displayed file names, or all of the image data may be printed without selection. In this way, it is possible for the same user to accumulate multiple pieces of image data, but for the sake of convenience in the following explanation, it is assumed that each user accumulates only one piece of image data.

[0039] On the other hand, if there is no image data stored by the login user in the judgment of S77 (S77: NO), the CPU 101 executes the display process for the home screen display notification (S79) and then ends the login process. In the display process of S61 (FIG. 9) above, when the CPU 101 detects the home screen display notification (S61: YES), the process returns to S51 above and displays the home screen on the display unit 105a (S51). At this time, the CPU 101 judges whether the selected LoginUser name is stored on the RAM 103, and if the selected LoginUser name is stored, displays the logged-in home screen on the display unit 105a. FIG. 3(b) shows an example of the logged-in home screen 105a6 displayed on the display unit 105a. The logged-in home screen 105a6 is composed of a display area 105a61 that displays the selected LoginUser name and a function selection area 105a62. When the selected LoginUser name displayed in the display area 105a61 of the logged-in home screen 105a6 is touched and an operation to log out is performed, the CPU 101 deletes the selected LoginUser name saved in the RAM 103. The screen of the display unit 105a transitions to the home screen 105a1 of FIG. 2(a) above.

[0040] 11 shows a procedure for sending a main body report print instruction from PC 10 to MFP 100. In this embodiment, the main body report (an example of "internal data") is a report for managing MFP 100, such as a report for informing an administrator of the remaining toner amount and number of pages printed of MFP 100, and the usage status of each function. As each function is executed, MFP 100 stores each piece of information indicating the usage status in NVM 104. MFP 100 may select the information to be printed according to information included in the main body report print instruction that indicates which usage status is to be printed as the main body report.

[0041] The browser process in Fig. 11 starts from a state in which PC 10 is instructed to start a browser and a browser screen is displayed on the display of PC 10. When a logged-in user of PC 10, for example an administrator of MFP 100, inputs an EWS URL on the browser screen, PC 10 transmits an EWS screen acquisition request to MFP 100 (S201). Note that EWS is an abbreviation for embedded Web server, and is a Web server built into MFP 100. The EWS is realized by processing of CPU 101 of MFP 100. At this time, the main process in Fig. 11 is processing of CPU 101 as the EWS. The main process is started in response to the power of MFP 100 being turned on.

[0042] When the CPU 101 of the MFP 100 receives an EWS screen acquisition request from the PC 10, it transmits EWS screen data corresponding to the request to the PC 10 (S101). An EWS screen is a type of Web page data. When the PC 10 receives the EWS screen data from the MFP 100, it displays the EWS screen on the browser screen. The PC 10 waits until an administrator login password is entered in a login password input field provided in the EWS screen (S202: NO), and when the administrator login password is entered (S202: YES), it transmits an authentication request to the MFP 100 using the entered administrator login password (S203).

[0043] When the CPU 101 of the MFP 100 receives an authentication request from the PC 10, it performs the authentication (S102) and determines whether the entered administrator login password is correct (S103). If the entered administrator login password is incorrect (S103: NO), the CPU 101 transmits a login denial to the PC 10. On the other hand, if the entered administrator login password is correct (S103: YES), the CPU 101 transmits post-login page data of the EWS screen to the PC 10 (S104).

[0044] When PC 10 receives the post-login page data from MFP 100, it displays the post-login page on the browser screen. In the post-login page, an operator for sending a main body report print instruction to MFP 100 is displayed, so when the administrator operates the operator, PC 10 sends a main body report print instruction to MFP 100 (S204).

[0045] When the CPU 101 of the MFP 100 receives the instruction to print the main body report from the PC 10, it notifies the reception and printing process (FIGS. 6 and 7) described next of the instruction to print the main body report from outside (S105).

[0046] 6 and 7 show the procedure of the reception and printing process. In FIG. 6, first, the CPU 101 judges whether or not the reception of a print job has started (S1). Specifically, the CPU 101 judges whether or not data is stored in the reception buffer, and if the data is stored, judges whether or not the data is a print job, and if the data is a print job, judges whether or not the leading end of the print job is stored. The reception buffer is provided, for example, on the RAM 103, and is an area for storing data received from outside the MFP 100 via the network IF 108 and the local IF 109. Note that the data stored in the reception buffer is not limited to data from outside the MFP 100, and various notifications that the CPU 101 sends to the reception and printing process may also be stored in the reception buffer. For example, the notification in S78 (FIG. 10) may be performed by storing information that identifies the image data to be printed, specifically, information indicating the location where the image data is stored, in the reception buffer. In this embodiment, there are two types of print jobs: one is generated by PC 10 and transmitted from PC 10 onto communication network 40, which is received by MFP 100 via network IF 108, and the other is received by MFP 100 via local IF 109 from PC 10A (see FIG. 1) connected via local IF 109. Note that PC 10A basically has the same configuration as PC 10. That is, hereinafter, the description of PC 10 is also the description of PC 10A.

[0047] FIG. 5 shows an example of the data structure of a print job 200. As shown in FIG. 5, the print job 200 is structured by enclosing a PDL in PJL. Note that PDL is an abbreviation for page description language, and PJL is an abbreviation for printer job language. The beginning of the print job 200 begins with " <esc>%-12345X@PJL" and the end of print job 200 is " <esc>%-12345X". Therefore, when the print job to be received in S1 is print job 200, CPU 101 determines whether reception of the print job has started by checking the received data. <esc>The determination is made based on whether "print job 200. %-12345X@PJL" is detected. Print job 200 also includes information such as the print job name test.txt, the user name suzuki, and the creation date and time 20210413201010. Note that the data configuration of the print job received by MFP 100 may differ from the data configuration of print job 200, but for convenience of explanation in this embodiment, it is assumed that MFP 100 receives a print job with the same data configuration as print job 200.

[0048] Returning to FIG. 6, when the CPU 101 starts receiving a print job in the judgment of S1 (S1: YES), the CPU 101 judges whether the print job corresponds to a registered main body LoginUser name (S2). Specifically, when the PcUser name included in the print job matches any of the main body LoginUser names registered in the user DB 104a (FIG. 4(a)), the judgment is "YES". Note that the same user may use different user names in the MFP 100 and the PC 10. Therefore, the main body LoginUser name used in the MFP 100 and the PcUser name included in the print job and used in the PC 10 are linked by the user DB 104a. In this embodiment, it is assumed that a print job including the user name logged in to the PC 10 as the PcUser name is created by the printer driver of the PC 10. Therefore, even if the PcUser name included in the print job does not match any of the main body LoginUser names registered in the user DB 104a, the CPU 101 determines "YES" in S2 if the main body LoginUser name linked to the PcUser name included in the received print job is registered in the user DB 104a. For example, if the received print job includes "kato" as the PcUser name, the PcUser name "kato" and the main body LoginUser name "kat" are registered in the user DB 104a in association with each other, so the CPU 101 determines "YES" in S2.

[0049] If it is determined in S2 that the print job that has started to be received is a print job that corresponds to a registered main body LoginUser name (S2: YES), CPU 101 displays a receiving screen on display unit 105a of panel 105 (S3).

[0050] In the table data 104b, there are three types of internal states of the MFP 100 indicating that a print job is being received: "print job being received", "print job being received (print instructor Login)", and "print job being received (via USB connection)". When a print job is started to be received (S1: YES), the CPU 101 must determine which of the three internal states the current internal state corresponds to before proceeding to S2. First, the CPU 101 determines whether the print job that has started to be received is a print job from the network IF 108 or a print job from the local IF 109. The print job from the network IF 108 and the print job from the local IF 109 are stored in different areas of the receive buffer, so the CPU 101 can determine whether the print job is received from the network IF 108 or the local IF 109. If the print job is received from the network IF 108, the CPU 101 further determines whether the print job is received during the print instructor Login. If there is a login user, as explained in S76 of the login process (FIG. 10), the selected LoginUser name is stored in RAM 103, so CPU 101 determines whether the selected LoginUser name matches the PcUser name included in the print job. If they do not match, CPU 101 determines whether the main body LoginUser name linked to the PcUser name included in the print job by user DB 104a matches the selected LoginUser name. If the selected LoginUser name matches the PcUser name included in the print job, CPU 101 writes "Receiving print job (print instructor Login)" to the internal state storage area. The same applies if the main body LoginUser name linked to the PcUser name matches the selected LoginUser name. On the other hand, if the selected LoginUser name does not match the PcUser name included in the print job, and the main body LoginUser name linked to the PcUser name does not match the selected LoginUser name, CPU 101 writes "print job being received" to the internal status storage area.Furthermore, if the print job is received from the local IF 109, the CPU 101 writes "print job being received (via USB connection)" in the internal state storage area. Note that the local IF 109 employs a USBIF as described above in this embodiment.

[0051] In S3 of FIG. 6, CPU 101 displays the receiving screen on display unit 105a. Specifically, CPU 101 writes screen ID "101" or "105" in the screen ID storage area. Here, whether "101" or "105" is to be written as the screen ID in the screen ID storage area is determined based on the internal state of MFP 100. That is, CPU 101 refers to table data 104b, and when the internal state of MFP 100 is "receiving print job", CPU 101 writes screen ID "101" in the screen ID storage area. On the other hand, when the internal state of MFP 100 is "receiving print job (print instructor Login)", CPU 101 writes screen ID "105" in the screen ID storage area. When the internal state of MFP 100 is "receiving print job (via USB connection)", CPU 101 writes screen ID "105" in the screen ID storage area.

[0052] In the above display process (FIG. 9), when CPU 101 detects neither a key notification nor a touch operation notification (S52: NO), it determines whether the screen ID written in the screen ID storage area has changed (S59), and if the screen ID has changed (S59: YES), CPU 101 reads out display screen data associated with the changed screen ID from NVM 104 and displays it on display unit 105a, thereby updating the screen (S60).

[0053] FIG. 2(b) shows an example of a receiving screen (screen ID=101) 105a2 displayed on the display unit 105a. The receiving screen 105a2 is configured with a display area 105a21 that displays the internal state of the MFP 100 and a display area 105a22 that displays the operation state of the MFP 100. FIG. 3(d) shows an example of a receiving screen (screen ID=105) 105a8 displayed on the display unit 105a. The receiving screen 105a8 is configured with a display area 105a81 that displays the internal state of the MFP 100 and a display area 105a82 that displays the operation state of the MFP 100, similar to the receiving screen 105a2. The receiving screen 105a2 in FIG. 2(b) and the receiving screen 105a8 in FIG. 3(d) have different screen IDs, but the display contents of the screens are the same. However, the on / off states of the three keys 105b1 to 105b3 of the key input section 105b are different between Fig. 2(b) and Fig. 3(d). The on / off control of the keys 105b1 to 105b3 is performed within the panel operation process (Fig. 8).

[0054] 8, if no panel operation on panel 105 is detected (S31: NO), CPU 101 determines whether or not the screen ID written in the screen ID storage area has changed (S38), similarly to S59 (FIG. 9). If the screen ID has changed (S38: YES), CPU 101 checks the internal state stored in the internal state storage area (S40), and based on the key pressability information corresponding to this internal state in table data 104b, lights up keys that can be pressed and turns off keys that cannot be pressed (S41). That is, when the internal state is "Receiving a print job", all three keys 105b1 to 105b3 are turned off as shown in Fig. 2(b), and when the internal state is "Receiving a print job (Login by print instructor)" or "Receiving a print job (via USB connection)", only the cancel key 105b3 is turned on and the other keys 105b1 and 105b2 are turned off as shown in Fig. 3(d). In this way, the lighting / turning off of the keys 105b1 to 105b3 corresponds to the enable / disable of each of the keys 105b1 to 105b3.

[0055] Returning to FIG. 6, next, CPU 101 judges whether the accumulated print function is enabled (S4). The accumulated print function is a function that accumulates a received print job in a memory (RAM 103 in this embodiment, but is not limited thereto, and may be NVM 104 or a USB memory attached to a USBIF) and then prints the job in response to a user's login. The concept of the accumulated print function includes accumulating a received print job in a memory as it is and then printing the job in response to a user's login, as well as executing RIP processing on a received print job, accumulating the generated image data in a memory, and then printing the image data in response to a user's login, as in this embodiment. In this embodiment, an example in which the generated image data is accumulated on RAM 103 will be described (see the following S5 and S6). Note that RIP is an abbreviation for raster image processor. The accumulated print function may be set, for example, by selecting enable / disable through various settings of MFP 100. The selection setting of enable / disable of the accumulated print function may be performed by PC 10 via network IF 108.

[0056] If the determination in S4 above indicates that the accumulated print function is enabled (S4: YES), CPU 101 RIPs the print data included in the print job (S5), and accumulates the RIPped image data in a predetermined area on RAM 103 in association with the user name that sent the original print job (S6). Specifically, even if CPU 101 determines in S2 that the PcUser name included in the print job matches any of the main body LoginUser names registered in user DB 104a, or if it determines in S2 that the main body LoginUser name linked to the PcUser name included in the received print job is registered in user DB 104a, CPU 101 stores the main body LoginUser name in association with the image data.

[0057] Next, CPU 101 determines whether the accumulation of image data in RAM 103 is complete (S7), and if the accumulation of image data in RAM 103 is not yet complete (S7: NO), CPU 101 determines whether a cancel key notification has been received (S8), and if the cancel key notification has not been received (S8: NO), CPU 101 returns the process to S7. On the other hand, if the determination in S8 shows that a cancel key notification has been received (S8: YES), CPU 101 cancels the accumulation of image data in RAM 103 midway (S9) and then proceeds to S16. Also, while receiving a print job, CPU 101 RIPs the print job, and if the image data is being accumulated, not only cancels the accumulation but also cancels the reception of the print job. Here, the cancel key notification is issued in S56 of the above display process (FIG. 9). Before that, whether or not the cancel key 105b3 can be pressed is determined in S34 of the above panel operation process (FIG. 8), so the control of the cancel key notification will be described below based on the related processes in the panel operation process and display process.

[0058] 8, if the detected panel operation is a key operation on the key input unit 105b (S32: YES), the CPU 101 checks the internal state stored in the internal state storage area in the same manner as in S40 (S33). Next, the CPU 101 refers to the table data 104b (FIG. 4(b)) and determines whether the key operation is a key operation that can be pressed in the current internal state (S34). In the table data 104b, if the current internal state is "receiving a print job", the pressability of the back key 105b1, home key 105b2, and cancel key 105b3 of the key input unit 105b is all "NG", so in this case, the determination in S34 is "NO" regardless of the key operation of any of the keys 105b1 to 105b3. On the other hand, if the current internal state is "Receiving print job (Print instructor Login)" or "Receiving print job (via USB connection)", the return key 105b1 and the home key 105b2 can be pressed "NG", but the cancel key 105b3 can be pressed "OK". In this case, if the cancel key 105b3 is pressed, the judgment in S34 is "YES".

[0059] If it is determined in S34 that the key operation is an operation on a key that can be pressed in the current internal state (S34: YES), CPU 101 notifies the display process of the operated key (S35), and then returns the process to S31. On the other hand, if it is determined in S34 that the key operation is not an operation on a key that can be pressed in the current internal state (S34: NO), CPU 101 sounds a rejection sound to notify the operator that the key operation has been rejected (S36), and then returns the process to S31. In S35, as described above, CPU 101 stores information identifying the operated key in the key notification storage area.

[0060] Next, when the process proceeds to S52 of the display process (FIG. 9), a key notification may or may not be stored in the key notification storage area. That is, when the process proceeds from S34 to S35, a key notification is stored in the key notification storage area, but when the process proceeds from S34 to S36, no key notification is stored in the key notification storage area. If a key notification is currently stored in the key notification storage area, no touch operation notification is stored in the touch operation notification storage area. When the CPU 101 detects a key notification (S52: YES) and the detected key notification indicates that the enabled home key 105b2 has been pressed (S53: YES), the process returns to S51 and the home screen is displayed on the display unit 105a.

[0061] In the judgment of S53, if the home key 105b2 in an invalid state is pressed or if the home key 105b2 itself is not pressed (S53: NO), CPU 101 checks the currently displayed screen (S54). This check is performed by checking the screen ID written in the screen ID storage area, as described above. CPU 101 then judges whether or not a process that should be notified of a panel operation is being executed based on the confirmed screen (S55). As described above, if the screen ID is 101 to 105, CPU 101 judges that the receive & print process in FIG. 6 is being executed as a process that should be notified of a panel operation (S55: YES), and CPU 101 notifies the process that should be notified of a panel operation of the key notification key (S56). For example, as shown in FIG. 3(d) above, when the receiving screen 105a8 is displayed on the display unit 105a, if the illuminated cancel key 105b3 on the key input unit 105b is pressed, the CPU 101 judges "YES" in S52 and "YES" in S55, and therefore notifies the reception and printing process of information identifying the cancel key 105b3 related to the key notification. In the reception and printing process, if the CPU 101 receives this notification (S8: YES) before the accumulation of image data is completed (S7: NO), the accumulation of image data is cancelled midway (S9). Although the screen ID is not specified, a screen ID is also assigned to the screen displayed in the login process (FIG. 10) and the menu screen described later. Therefore, when a list of users is displayed or when a PIN entry screen is displayed, the CPU 101 can determine that a panel operation should be notified to the login process, and when a menu screen is displayed and an operation is performed to instruct printing of a main body report, the CPU 101 can determine that a panel operation should be notified to the receive and print process.

[0062] The operation of pressing the cancel key 105b3 includes a short press (an example of a "first cancel instruction") and a long press (an example of a "second cancel instruction"). For example, when the current internal state is "print job receiving (print instructor Login)", a print job included in one of the multiple transmitted jobs may be RIP-processed and stored. At that time, when the cancel key 105b3 is short-pressed, the CPU 101 cancels the storage of one print job being stored, and when the cancel key 105b3 is long-pressed, the CPU 101 cancels the reception of one print job being stored and cancels the reception of the remaining print jobs newly received during the long press. In other words, if multiple print jobs are received during the long press, the reception of the multiple print jobs is canceled. The possibility of pressing the cancel key 105b3 in S34 above applies to both a short press and a long press. As described above, when CPU 101 receives one job and stores image data based on that job, it also cancels the reception of that job regardless of whether the key operation is a short press or a long press.

[0063] On the other hand, as shown in FIG. 2(b) above, when the receiving screen 105a2 is displayed on the display unit 105a, if the unlit cancel key 105b3 is pressed on the key input unit 105b, the CPU 101 judges "NO" in S52 and does not proceed to S56, so does not notify the reception and printing process of information specifying the cancel key 105b3 related to the key notification. As a result, in the reception and printing process, the CPU 101 does not receive this notification (S8: NO), so the accumulation of image data is completed without being canceled midway (S7: YES). In this way, when the internal state is "receiving a print job", the reception of the print job "receiving a print job" cannot be canceled by the cancel key 105b3. As a result, the MFP 100 of this embodiment can prevent a person other than the user who transmitted the print job for storage printing from canceling the reception of the print job transmitted from the PC 10 via the network, which is located far from the MFP 100, during the reception of the print job for storage printing. In this embodiment, when an off key is pressed, the key press operation itself is accepted (see S32 of the panel operation process), but no processing according to the pressed key is performed (see S34 of the panel operation process). However, without being limited to this, when an off key is pressed, the key press operation itself may not be accepted.

[0064] On the other hand, if it is determined in the above S7 that the accumulation of image data in RAM 103 has been completed (S7: YES), CPU 101 advances the process to S16. In S16, CPU 101 displays the home screen on display unit 105a of panel 105. Specifically, CPU 101 writes screen ID "100" in the above screen ID storage area on RAM 103. Note that, before performing the process of S16, CPU 101 writes "operation completed" in the above internal state storage area. As a result, in S16, CPU 101 refers to table data 104b and writes screen ID "100" when the internal state is "operation completed" in the screen ID storage area, so that the home screen is displayed on display unit 105a by S60 of the above display process. After the process of S16, CPU 101 returns the process to S1.

[0065] On the other hand, if the storage print function is disabled in the determination of S4 (S4: NO), CPU 101 performs RIP processing on the print data included in the print job in the same manner as in S5 (S10). Then, CPU 101 displays a printing screen on display unit 105a of panel 105 (S11). Specifically, CPU 101 writes screen ID "102" in the screen ID storage area on RAM 103. Note that CPU 101 writes "printing image data" in the internal state storage area before performing the process of S11. As a result, in S11, CPU 101 refers to table data 104b and writes screen ID "102" when the internal state is "printing image data" in the screen ID storage area, so that the printing screen is displayed on display unit 105a. FIG. 3(a) shows an example of a printing screen (screen ID=102, 103) 105a5 displayed on display unit 105a. Printing screen 105a5 is made up of display area 105a51 that displays the internal state of MFP 100, and display area 105a52 that displays the operating state of MFP 100. CPU 101 then outputs the image data after RIP processing to print engine 111, thereby starting printing (S12).

[0066] Next, CPU 101 determines whether printing is complete (S13). If printing is not complete (S13: NO), CPU 101 determines whether a cancel key notification has been received (S14) in the same manner as in S8 above. If a cancel key notification has not been received (S14: NO), CPU 101 returns the process to S13 above. On the other hand, if a cancel key notification has been received (S14: YES) in the determination in S14, CPU 101 cancels printing midway (S15) and then proceeds to S16.

[0067] FIG. 3(a) also shows the key input section 105b when the internal state is "printing image data". In this key input section 105b, only the cancel key 105b3 is lit, and the other keys 105b1 and 105b2 are off. In other words, the state of this key input section 105b is the same as the state of the key input section 105b in FIG. 3(d). Therefore, when the internal state is "printing image data", the cancel key 105b3 is valid, so when the printing of the image data is incomplete (S13: NO), if the cancel key 105b3 is pressed, the CPU 101 receives a cancel key notification (S14: YES) and cancels the printing of the image data in progress (S15). In this way, when the internal state is "printing image data", the printing of the image data being printed can be canceled by the cancel key 105b3. In this case, the printing of the image data being printed is not printed by the accumulated printing function, so the cancellation of the printing is permitted.

[0068] On the other hand, if it is determined in S13 that the printing is completed (S13: YES), the CPU 101 advances the process to S16.

[0069] On the other hand, if it is determined in the above S2 that the print job that has started to be received is not a print job that corresponds to the registered main body LoginUser name (S2: NO), the CPU 101 cancels the reception without RIP processing the print job (S17), and then ends the reception and printing process. Note that instead of canceling in S17, printing based on the print job may be performed.

[0070] On the other hand, if the determination in S1 above indicates that reception of a print job has not started (S1: NO), CPU 101 determines whether or not an external instruction to print a main body report has been received (S20 in FIG. 7). CPU 101 also makes this determination depending on whether or not an external instruction to print a main body report has been stored in the receive buffer, specifically, whether or not the notification in S105 above (FIG. 11) has been received.

[0071] If it is determined in S20 that a main body report print instruction has been received from outside (S20: YES), CPU 101 causes a printing screen to be displayed on display 105a of panel 105 (S21). Specifically, CPU 101 writes screen ID "104" to the screen ID storage area on RAM 103. Note that before performing the process of S21, CPU 101 writes "Main body report printing by external instruction" to the internal status storage area. The timing of this write is not limited to this, and may be before or after CPU 101 notifies the reception and printing process of the instruction (S105) in response to receiving the main body report print instruction sent by PC 10 in S204 (FIG. 11) above. As a result, in S21, CPU 101 refers to table data 104b and writes screen ID "104" when the internal state is "printing main body report by external instruction" into the screen ID storage area, so that the printing screen is displayed on display unit 105a by S60 of the display process described above. FIG. 3(c) shows an example of printing screen (screen ID=104) 105a7 displayed on display unit 105a. Printing screen 105a7 is composed of display area 105a71 that displays the internal state of MFP 100 and display area 105a72 that displays the operating state of MFP 100, similar to printing screen 105a5 (FIG. 3(a)). Next, CPU 101 generates image data of the instructed main body report and outputs it to print engine 111 to start printing (S22), and then proceeds to the process of S13 (FIG. 6) described above.

[0072] FIG. 3C also shows the key input section 105b when the internal state is "printing a main body report by external instruction". In this key input section 105b, all three keys 105b1 to 105b3 are off. That is, the state of this key input section 105b is the same as the state of the key input section 105b in FIG. 2B. Therefore, when the internal state is "printing a main body report by external instruction", the cancel key 105b3 is invalid. Therefore, even if the cancel key 105b3 is pressed when the printing of the main body report is incomplete (S13: NO), the CPU 101 does not receive a cancel key notification (S14: NO), and the printing of the main body report is completed without being canceled (S13: YES). In this way, when the internal state is "printing a main body report by external instruction", the printing of the main body report being printed cannot be canceled by the cancel key 105b3. This makes it possible to prevent a person other than the user of the PC 10 from canceling the printing of a main body report, for example, while the print is being performed in response to an external instruction from the PC 10.

[0073] On the other hand, if it is determined in S20 that a main body report print instruction has not been received from the outside (S20: NO), it is determined whether a main body report print instruction has been received from panel 105 (S23). A main body report print instruction can be issued not only from the outside, but also from display unit 105a of panel 105. Specifically, for example, when home screen 105a1 (FIG. 2(a)) is displayed on display unit 105a, if a menu button (not shown) in home screen 105a1 is touched, the menu screen is displayed, and if a main body report print instruction is touched on the menu screen, CPU 101 notifies the receive and print process of the main body report print instruction.

[0074] If it is determined in S23 that a main body report print instruction has been issued from panel 105 (S23: YES), CPU 101 causes a printing screen to be displayed on display unit 105a of panel 105 (S24). Specifically, CPU 101 writes screen ID "103" to the screen ID storage area on RAM 103. Note that CPU 101 writes "Main body report being printed by panel instruction" to the internal state storage area before carrying out the process of S24. The timing of this writing is not limited to this, and may be before or after receiving a touch operation for a main body report print instruction from the menu screen and notifying the receive and print process of the main body report print instruction. Thus, in S24, CPU 101 refers to table data 104b and writes screen ID "103" when the internal state is "Main body report being printed by panel instruction" to the screen ID storage area, so that the printing screen is displayed on display unit 105a by S60 of the display process. The printing screen 105a5 in FIG. 3A serves as both the printing screen with the screen ID "102" and the printing screen with the screen ID "103". Next, the CPU 101 advances the process to S22.

[0075] The key input section 105b in FIG. 3(a) serves both as the key input section 105b when the internal state is "printing image data" and as the key input section 105b when the internal state is "printing a main body report by panel instruction". Therefore, when the internal state is "printing a main body report by panel instruction", the cancel key 105b3 is valid just as when the internal state is "printing image data". Therefore, when the printing of the main body report is not yet completed (S13: NO), if the cancel key 105b3 is pressed, the CPU 101 receives a cancel key notification (S14: YES) and cancels the printing of the main body report in progress (S15). In this way, when the internal state is "printing a main body report by panel instruction", the printing of the main body report being printed can be canceled by the cancel key 105b3. This is because the user who instructed the printing of the main body report from the panel 105 cancels the printing.

[0076] On the other hand, if it is determined in the above S23 that the instruction to print the main body report has not been issued from the panel 105 (S23: NO), the CPU 101 determines whether or not an instruction to print the accumulated image data has been issued (S25). The instruction to print the accumulated image data is issued in S78 of the above login process.

[0077] If it is determined in S25 that a print instruction for the accumulated image data has been notified (S25: YES), CPU 101 displays a printing screen on display unit 105a of panel 105 (S26). Specifically, CPU 101 writes screen ID "102" to the screen ID storage area on RAM 103. Note that CPU 101 writes "accumulated image data being printed" to the internal state storage area before carrying out the process of S26. The timing of this write is not limited to this, and may be before or after CPU 101 notifies the reception and printing process of the print instruction in S78 (FIG. 10). As a result, in S24, CPU 101 refers to table data 104b and writes screen ID "102" when the internal state is "accumulated image data being printed" to the screen ID storage area, so that the printing screen with screen ID "102" is displayed on display unit 105a. Next, CPU 101 starts printing by outputting the accumulated image data to print engine 111 (S27), and then proceeds to the process at S13 (FIG. 6) above. Note that since the image data to be printed has already been specified in the print instruction for the accumulated image data, in S26 CPU 101 only needs to output the specified image data to print engine 111. An example of the printing screen with screen ID "102" has already been shown as printing screen 105a5 in FIG. 3(a) above. Also, key input section 105b in FIG. 3(a) also shows key input section 105b when the internal state is "printing accumulated image data". Therefore, when the internal state is "printing stored image data", the cancel key 105b3 is valid, just as when "printing image data" and "printing a main unit report by panel instruction" are being performed. Therefore, when the printing of the stored image data is incomplete (S13: NO) and the cancel key 105b3 is pressed, the CPU 101 receives a cancel key notification (S14: YES) and cancels the printing of the stored image data midway (S15). In this way, when the internal state is "printing stored image data", the printing of the image data being printed can be canceled by the cancel key 105b3. This allows the logged-in user to cancel the printing of image data for the stored print job that the user himself / herself has instructed PC 10A.

[0078] On the other hand, if it is determined in S25 that a print instruction for the accumulated image data has not been received (S25: NO), the CPU 101 returns the process to S1 (FIG. 6).

[0079] In this embodiment, when a cancel key notification is received (S8: YES) while receiving a print job when the accumulated print function is enabled, the reception of the print job is cancelled (S9 above), and the reception of a cancel key notification while receiving a print job when the accumulated print function is disabled is not taken into consideration, but the present invention is not limited to this, and even if the accumulated print function is disabled, the reception of the print job may be cancelled when a cancel key notification is received, as in the case when the accumulated print function is enabled. In this way, MFP 100 of this embodiment can at least prevent a person other than the user who sent the print job for accumulated printing from cancelling the reception of the print job while receiving the print job for accumulated printing that was sent from PC 10 via the network, which is located far from MFP 100.

[0080] In addition, in this embodiment, while receiving screen 105a2 is displayed on display unit 105a, pressing of the cancel key is not transmitted to the receiving and printing process, but while receiving screen 105a8 is displayed on display unit 105a, pressing of the cancel key may not be transmitted to the receiving and printing process. In this way, MFP 100 in this embodiment can at least prevent a user other than the user who sent the print job for stored printing from canceling the reception of the print job sent from PC 10 via the network, which is located far from MFP 100, while the print job for stored printing is being received.

[0081] Also, when the internal state is "print job receiving (print instructor Login)", a receiving screen 105a2 having the screen ID 101 may be displayed on the display unit 105a.

[0082] In this embodiment, the key input unit 105b is configured with three keys 105b1 to 105b3, and each key can be switched between a lit state and an unlit state. However, the present invention is not limited to this. Buttons corresponding to the three keys 105b1 to 105b3 may be displayed on the display unit 105a, and display / non-display control of the buttons may be performed instead of the light-on / light-off control in S41 described above.

[0083] In this embodiment, a communication IF for local connection in a short distance is used as the local IF 109, but the present invention is not limited to this. A communication IF for a method mainly assuming one-to-one connection may be used as the local IF, and in that case, for example, a communication IF for a Bluetooth (registered trademark) method or a Wi-Fi Direct method may be used as the local IF. A communication IF for a method mainly assuming temporary connection may be used as the local IF, and in that case, for example, a communication IF for a Bluetooth method or a Wi-Fi Direct method may be used as the local IF.

[0084] The present invention is not limited to the above-described embodiment, and various modifications are possible without departing from the spirit of the present invention.

[0085] (1) In the above embodiment, the MFP 100 has been taken as an example of a printing device, but the printing device is not limited to the MFP 100 and may be a standalone printer.

[0086] (2) In the above embodiment, one CPU 101 is used as an example of a controller, but the present invention is not limited to this, and a controller consisting of multiple CPUs may be used, or a controller including a CPU consisting of multiple cores may be used. Also, the controller may have a CPU and a dedicated circuit. Examples of the dedicated circuit include an ASIC and an FPGA. [Explanation of symbols]

[0087] 1...printing system, 10...PC, 40...communication network, 100...MFP, 101...CPU, 102...ROM, 103...RAM, 104...NVM, 105...panel, 105a...display unit, 105b...key input unit, 108...network IF, 109...local IF, 111...printing engine, 112...reading engine, 130...bus.< / esc> < / esc> < / esc>

Claims

1. A communication interface; A user interface; Memory, A controller; A printing device comprising: The controller: a storage printing process in which, when a print job including a user name is received from the communication interface, the print job is stored in the memory without printing based on the print job, and then the user name is input from the user interface to log in, and if the received user name matches the input user name, printing based on the stored print job is performed; a print stop process for stopping the printing based on the print job when a cancel instruction for the printing based on the print job is input from the user interface during the execution of the printing based on the stored print job by the stored print process; It is possible to execute the receiving user name is a user name included in the received print job, the input user name is a user name input through the user interface, The controller: during reception of the print job including the user name in the stored print process, continuing to receive the print job without canceling reception of the print job due to an instruction to cancel reception of the print job being input from the user interface; Printing device.

2. The controller: a first cancellation process for canceling reception of the data when a first cancellation instruction is received from the user interface while data including the print job is being received from the communication interface; a second cancellation process of canceling reception of the data from the communication interface while a second cancellation instruction is being accepted from the user interface; It is possible to execute In the stored print process, neither the first nor the second cancel instruction is accepted. The printing device of claim 1 .

3. The controller: The user interface is switchable between a first state indicating that the cancel instruction is acceptable and a second state indicating that the cancel instruction is not acceptable, while printing based on the stored print job is being executed by the stored print process, the user interface is set to the first aspect, and when an instruction to cancel the printing based on the print job is input from the user interface in the first aspect, the printing is canceled; during reception of a print job including the user name in the stored print process, the user interface is set to the second mode, and reception of the print job is continued without canceling reception of the print job due to input of an instruction to cancel reception of the print job from the user interface in the second mode; 3. The printing device according to claim 1 or 2.

4. The controller: an instruction to enable a stored print function can be received from at least one of the user interface and the communication interface; when an instruction to enable the stored print function is received, the stored print function is set to be enabled, and the stored print process is executed when the stored print function is set to be enabled; When the stored print function is disabled, the print job can be received and printing can be performed based on the print job; while the print job is being received when the stored print function is disabled, the user interface is in the first mode, and when the cancel instruction is input from the user interface in the first mode, the reception of the print job is cancelled; while the print job is being received when the stored print function is enabled, the user interface is set to the second mode, and the reception of the print job is continued without being cancelled by inputting an instruction to cancel the reception of the print job from the user interface in the second mode. The printing device according to claim 3 .

5. The controller: The user interface is switchable between a first state indicating that the cancel instruction is acceptable and a second state indicating that the cancel instruction is not acceptable, an instruction to enable a stored print function can be received from at least one of the user interface and the communication interface; when an instruction to enable the stored print function is received, the stored print function is set to be enabled, and the stored print process is executed when the stored print function is set to be enabled; When the stored print function is disabled, the print job can be received and printing can be performed based on the print job; while the print job is being received when the stored print function is disabled, the user interface is in the first mode, and when the cancel instruction is input from the user interface in the first mode, the reception of the print job is cancelled; while the print job is being received when the stored print function is enabled, the user interface is set to the second mode, and the reception of the print job is continued without being cancelled by inputting an instruction to cancel the reception of the print job from the user interface in the second mode.

3. The printing device according to claim 1 or 2.

6. the memory stores correspondence information between the receiving user name and the input user name corresponding to the receiving user name; The controller: A process for determining whether the received user name matches the input user name. It is possible to execute In the determination process, when the input user name corresponding to the receiving user name is stored in the memory as the corresponding information, it is determined that the receiving user name and the input user name match; In the stored print process, when it is determined that the received user name and the input user name match, printing is performed based on the stored print job. The printing device according to any one of claims 1 to 5.

7. The controller: When a user name is input from the user interface, and after logging in with that user name, an instruction to cancel reception of the print job including the user name is given from the user interface while the print job is being received, If the receiving user name included in the print job for which the cancellation instruction is given does not match the input user name, continuing to receive the print job without canceling the reception of the print job; canceling reception of the print job when the receiving user name included in the print job for which the cancellation instruction is given matches the input user name; 3. The printing device according to claim 1 or 2.

8. the memory stores correspondence information between the receiving user name and the input user name corresponding to the receiving user name; The controller: A process for determining whether the received user name matches the input user name. It is possible to execute In the determination process, when the input user name corresponding to the receiving user name is stored in the memory as the corresponding information, it is determined that the receiving user name and the input user name match; When a user name is input from the user interface, and after logging in with that user name, an instruction to cancel reception of the print job including the user name is given from the user interface while the print job is being received, determining whether the receiving user name included in the print job for which the cancel instruction is given matches the input user name by the determination process; If the receiving user name does not match the input user name, the reception of the print job is continued without being canceled; canceling reception of the print job if the receiving user name matches the input user name; The printing device according to claim 7.

9. The communication interface includes a network interface and a local communication interface; The controller: When an instruction to cancel reception of a print job including the user name is given from the user interface during reception of the print job, If the print job is a print job being received from the network interface, the reception of the print job is continued without being canceled; If the print job is a print job being received from the local communication interface, canceling the reception of the print job. The printing device according to any one of claims 1 to 8.

10. A printing system including an information processing device and a printing device connected to the information processing device, The information processing device includes: A communication interface; A controller; Equipped with The controller: transmitting a print job including a user name from the communication interface to the printing device; The printing device includes: A communication interface; A user interface; Memory, A controller; Equipped with The controller of the printing device a storage printing process in which, when a print job including the user name is received from the information processing device through the communication interface of the printing device, the print job is stored in the memory without printing based on the print job, and then the user name is input from the user interface to log in, and if the received user name matches the input user name, printing based on the stored print job is performed; a print stop process for stopping the printing based on the print job when a cancel instruction for the printing based on the print job is input from the user interface during the execution of the printing based on the stored print job by the stored print process; It is possible to execute the receiving user name is a user name included in the received print job, the input user name is a user name input through the user interface, The controller of the printing device during reception of the print job including the user name in the stored print process, continuing to receive the print job without canceling reception of the print job due to an instruction to cancel reception of the print job being input from the user interface; Printing system.

Images