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 Art

[0002] Patent Document 1 describes a printing apparatus that stores a received print job in a memory and then performs stored printing in response to a user's login.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the printing apparatus described in Patent Document 1, during the reception of a print job for stored printing, there is a risk that the reception of the print job may be canceled by someone other than the user who sent the print job, for example, an operator operating the printing apparatus.

[0005] An object of this application is to provide a technology for restricting someone other than the sender from canceling the reception of a print job for stored printing during the reception of the print job.

Means for Solving the Problems

[0006] To achieve the above object, the printing apparatus of the present application is a printing apparatus including a communication interface, a user interface, a memory, and a controller. When the controller receives a print job including a user name from the communication interface, it stores the print job in the memory without performing printing based on the print job. Then, when a user name is input from the user interface, logged in, and the received user name matches the input user name, the controller performs a cumulative printing process of performing printing based on the stored print job, and during the execution of printing based on the stored print job by the cumulative printing process, when a cancel instruction for printing based on the print job is input from the user interface, the controller can execute a print stop process of stopping the printing based on the print job. The received 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. During the reception of the print job including the user name in the cumulative printing process, the controller continues to receive the print job without canceling the reception of the print job due to the input of a cancel instruction for receiving the print job from the user interface.

Effect of the Invention

[0007] According to the present application, it is possible to limit others from canceling the reception of a print job for cumulative printing during the reception of the print job.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Mode for Carrying Out the Invention

[0009] Hereinafter, embodiments of the present application will be described in detail with reference to the drawings. FIG. 1 shows the 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 device having 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 bootloader. The NVM 104 is a non-volatile memory that stores control programs (including programs for reception & printing processing (Figs. 6 and 7), panel operation processing (Fig. 8), display processing (Fig. 9), and login processing (Fig. 10) described later), as well as 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, etc. Also, the RAM 103 is used as a storage area for temporarily storing data, signals, etc. used when the CPU 101 executes control programs, or as a work area for data processing.

[0012] Also, the MFP 100 includes a panel 105 (which is an example of a "user interface" and also an example of a "display"). The panel 105 includes a display unit 105a and a key input unit 105b. In this embodiment, the display unit 105a is composed of a touch panel capable of performing touch operations, and various screens are displayed on the display unit 105a according to the state of the MFP 100. The user of the MFP 100 can perform input operations by touching the input buttons displayed on the screen. The key input unit 105b is composed of a plurality (for example, three) of keys, and each key can be switched between a lit state and an extinguished state by switching the on and off of, for example, a backlight.

[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 the communication network 40. In this embodiment, since a PC 10 is connected to the communication network 40, the MFP 100 can perform transmission and reception of various data with the PC 10. The communication network 40 can be various types of networks. For example, it can be a wired or wireless LAN, WAN, etc.

[0014] In addition, the MFP 100 is provided with a local IF 109. The local IF 109 is for locally connecting to external devices such as the PC 10A, HDD, CD-ROM D, etc. at a short distance. As the connection method, USB, NFC, etc. may be used. Note that NFC is an abbreviation for near field communication. In the present embodiment, a USB IF is adopted as the local IF 109.

[0015] In addition, the MFP 100 is provided with a printing engine 111 and a reading engine 112. The printing engine 111 is an electrophotographic printing engine. The method of the printing engine may be an inkjet method, a thermal method, etc. The reading engine 112 is a mechanism for reading an image from a document and has a sensor such as a CCD or CIS.

[0016] The CPU 101, ROM 102, RAM 103, NVM 104, panel 105, network IF 108, printing engine 111, and reading engine 112 are interconnected by a bus 130.

[0017] Note that in this specification, basically, the processing of the CPU 101 according to the instructions described in the program is shown. That is, the processing such as "judgment", "extraction", "selection", "calculation", "decision", "specification", "acquisition", "reception", "control", "setting", etc. in the following description represents the processing of the CPU 101. The processing by the CPU 101 includes hardware control via the OS. Note that "acquisition" is used as a concept that does not require a request. That is, the process of the CPU 101 receiving data without a request is also included in the concept of "the CPU 101 acquiring data". Also, the "data" in this specification is represented by a bit string readable by a computer. And data with the same substantial meaning content but different formats shall be treated as the same data. The same applies to the "information" in this specification. Also, the processing such as "instruction", "response", "request", etc. is performed by communicating the information indicating "instruction", "response", "request", etc. Also, the words such as "instruction", "response", "request", etc. may be described in the sense of the information itself indicating "instruction", "response", "request", etc.

[0018] When the power of the MFP100 is turned on, the CPU101 executes an initialization process (not shown) and starts panel operation processing (FIG. 8), display processing (FIG. 9), and reception & printing processing (FIGS. 6 and 7). Hereinafter, in the description of the procedures of each process, steps are denoted as "S".

[0019] When the display processing starts, in FIG. 9, first, the CPU101 displays the home screen on the display unit 105a (S51). FIG. 2(a) shows an example of the home screen (screen ID = 100) 105a1 displayed on the display unit 105a. The home screen 105a1 is composed of a "Public" button 105a11 and a function selection area 105a12 for selecting any one of the FAX function, copy function, and scan function of the MFP100. Note that a screen ID is associated with the screen displayed on the display unit 105a, and the screen display on the display unit 105a is switched according to the switching of the screen ID. The CPU101 writes the screen ID into a screen ID storage area (not shown) provided on the RAM103 in S3 and the like described later in the reception & printing process.

[0020] Also, when the panel operation processing starts, in FIG. 8, the CPU101 first determines whether a panel operation on the panel 105 has been detected (S31). If no panel operation is detected (S31: NO), then it determines whether the screen ID has changed (S38). If the screen ID has not changed (S38: NO), the process returns to S31. Then, the CPU101 repeats the determination of S31 and S38 until a panel operation is detected (S31: YES) or the screen ID changes (S38: YES). Note that the panel operation on the panel 105 includes a touch operation on the display unit 105a of the panel 105 and a key operation on the key input unit 105b of the panel 105.

[0021] For example, when the above home screen 105a1 is displayed on the display unit 105a and the "Public" button 105a11 is touch-operated, since the CPU 101 determines "YES" in S31 above, it then determines whether the panel operation is a key operation on the key input unit 105b (S32). Now, since the panel operation is 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 it in a touch operation storage area (not shown) provided on the RAM 103. Information stored in the touch operation notification storage area as a touch operation notification is, for example, the touch position on the display unit 105a.

[0022] In the above display process, after the process of S51, the CPU 101 determines whether a key notification or a touch operation notification has been detected (S52). The key notification is made in S35 described later in the above panel operation process. Specifically, the key notification is performed, like the above touch operation notification, by storing it in a key notification storage area (not shown) provided on the RAM 103. However, different from the touch operation notification, information stored in the key notification storage area as a key notification is information for specifying the operated key among the three keys of the key input unit 105b. Thus, since 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, in S52, the CPU 101 determines whether 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 determination of S52, if neither the key notification nor the touch operation notification is detected (S52: NO), the CPU 101 determines whether the screen ID written in the screen ID storage area has changed (S59). And in this determination, if the screen ID has not changed (S59: NO), the CPU 101 further determines whether a home screen display notification has been detected (S61). If the home screen display notification has not been detected (S61: NO), the CPU 101 returns the process to S52. Thus, after the process of S51, the CPU 101 repeats the determinations 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 process, when the CPU 101 is repeatedly making the determinations of S52, S59, and S61, if a touch operation of the "Public" button 105a11 is notified by the process of S37, the CPU 101 determines "YES" in S52. Next, it determines whether it is a pressing operation of the home key 105b2 (see Fig. 2(a)) among the three keys of the key input unit 105b, and whether the pressability information of the home key 105b2 is "OK" (S53).

[0025] Figure 4(b) shows an example of the screen according to the internal state of the MFP 100 and the table data 104b indicating whether keys can be pressed. The table data 104b consists of the internal state of the MFP 100, the screen ID that identifies the screen to be displayed on the display unit 105a of the panel 105 in that internal state, and three keys provided in the key input unit 105b of the panel 105 in that internal state, specifically, the back key 105b1, the home key 105b2, and the cancel key 105b3. When each of these keys is pressed, it indicates whether the press is valid ("OK" in Figure 4(b)) or invalid ("NG" in Figure 4(b)), which is the key press enable / disable information, and is registered in the NVM 104, for example. When the internal state of the MFP 100 is "Receiving Print Instruction", there is no screen ID (-). This is because the time when the internal state of the MFP 100 is "Receiving Print Instruction" is extremely short, so there is little need to switch the screen on the display unit 105a to the "Receiving Print Instruction" screen. Of course, this is not the only case. A screen ID for identifying the "Receiving Print Instruction" screen can be determined and the "Receiving Print Instruction" screen can be displayed. Also, as shown in Figure 4(c), display screen data 104c is also stored in the NVM 104 in association with each screen ID.

[0026] A plurality of internal states of the MFP 100 are defined in advance, and the CPU 101 selects a state that matches the current state from the defined plurality of internal states and stores it, for example, in an internal state storage area (not shown) provided on the RAM 103, thereby determining the internal state of the MFP 100. Therefore, the internal state of the MFP 100 refers to the internal state stored in the internal state storage area on the RAM 103. The writing of the internal state to the internal state storage area on the RAM 103 is appropriately performed by the CPU 101 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 is detected instead of a key notification, the CPU 101 determines "NO" in S53 above and checks the currently displayed screen (S54). Specifically, this check is performed by checking the screen ID written in the above screen ID storage area. Then, the CPU 101 determines whether a process for notifying a panel operation is being executed based on the confirmed screen (S55). If the screen ID confirmed in S54 is 100, the CPU 101 determines "NO", and if the screen ID is 101 - 105, the CPU 101 determines "YES". That is, when the screen ID is 101 - 105, the CPU 101 determines that the above reception & printing process (FIGS. 6 and 7) is being executed as the process for notifying a panel operation. Now, since the screen ID is 100, the CPU 101 determines "NO" in S55 and notifies screen update and / or process start according to the key of the key notification or the touch position of the touch operation notification (S57). Since the touch operation of the "Public" button 105a11 instructs the start of the login process (FIG. 10), the CPU 101 performs a screen update according to the touch position in S57 and notifies the start of the login process.

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

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

[0030] FIG. 4(a) shows an example of the user DB 104a for login management and function restriction management. Note that DB is an abbreviation for data base. 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 items such as the main body LoginUser name, PcUser name, PIN, and Function.

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

[0032] PIN is a so-called personal identification number, which is an abbreviation for personal identification number. The PIN is registered in advance as a set with the main body LoginUser name and is used at the time of login authentication of the MFP 100.

[0033] Function is information for the above function restriction management, and indicates whether the user registered with the main body LoginUser name can use the printing function, scanning function, and copying function (Print, Scan, and Copy in FIG. 4(a)). That is, the user registered with the main body LoginUser name can use the functions registered with "OK", but cannot use the functions registered with "NG". For example, a user with the main body LoginUser name of "suzuki" can use the printing function and scanning function of the MFP 100 when logging in to the MFP 100, but cannot use the copying function of the MFP 100.

[0034] Returning to FIG. 10, the CPU 101 waits until any one of the users displayed in the user list display area 105a32 is selected by the user (S72: NO). When any one of the users is selected (S72: YES), the CPU 101 displays a PIN input screen on the display unit 105a (S73).

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

[0036] In the determination of S75, when the input PIN is correct (S75: YES), the CPU 101 saves the login user name, that is, the selected main body LoginUser name, on the RAM 103 (S76), and then determines whether there is stored picture data accumulated by the login user (S77). Hereinafter, the selected main body LoginUser name will be described as the "selected LoginUser name". The CPU 101 determines whether there is stored picture data associated with the main body LoginUser name that matches the selected LoginUser name. In S6 of FIG. 6, the CPU 101 stores the picture data in association with the main body LoginUser name indicating the user who sent the base print job. Details will be described later.

[0037] In the determination of S77, when there is stored picture data accumulated by the login user, that is, the user indicated by the selected LoginUser name (S77: YES), the CPU 101 notifies the reception & print process of a print instruction for the accumulated picture data (S78), and then ends the login process.

[0038] Note that when the process proceeds from S77 to S78, there may be a plurality of frame data accumulated by the logged-in user. In this case, for example, the file names of the plurality of frame data may be displayed on the display unit 105a, and the logged-in user may be allowed to select the one to be printed from among them, or all the frame data may be printed without selection. Thus, it is possible for the same user to accumulate a plurality of frame data. However, for the sake of explanation below, it is assumed that each user accumulates only one piece of frame data.

[0039] On the other hand, in the determination of S77 above, when there is no frame data accumulated by the logged-in user (S77: NO), the CPU 101 performs a home screen display notification in the display process (S79), and then ends the login process. In the above S61 (FIG. 9) of the display process, when the CPU 101 detects this home screen display notification (S61: YES), the process returns to the above S51, and the home screen is displayed on the display unit 105a (S51). At this time, the CPU 101 determines whether the selected LoginUser name is stored on the RAM 103. If the selected LoginUser name is stored, the logged-in home screen is displayed 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 for displaying the selected LoginUser name and a function selection area 105a62. When a touch operation is performed on the selected LoginUser name displayed in the display area 105a61 of the logged-in home screen 105a6 to perform a logout operation, the CPU 101 deletes the selected LoginUser name stored on the RAM 103. The screen of the display unit 105a transitions to the home screen 105a1 of FIG. 2(a) above.

[0040] FIG. 11 shows the procedure for sending a main body report printing instruction from the PC10 to the MFP100. Here, the main body report (an example of "internal data") is, in this embodiment, a report for managing the MFP100. For example, it is a report for notifying the administrator of the toner remaining amount, the number of printed sheets, and the usage status of each function of the MFP100. The MFP100 stores each piece of information indicating the usage status in the NVM104 as each function is executed. The MFP100 may select the information to be printed according to the information indicating which usage status to print as the main body report included in the main body report printing instruction.

[0041] The browser process in FIG. 11 starts from the state where the PC10 is instructed to start the browser and the browser screen is displayed on the display of the PC10. When the logged-in user of the PC10, for example, the administrator of the MFP100, enters the URL of the EWS on the browser screen, the PC10 sends an EWS screen acquisition request to the MFP100 (S201). Note that EWS is an abbreviation for embedded Web server and is a Web server built into the MFP100. The EWS is realized by the processing of the CPU101 of the MFP100. At this time, the main process in FIG. 11 is the process of the CPU101 as the EWS. The main process is started in response to the power of the MFP100 being turned on.

[0042] When the CPU101 of the MFP100 receives the EWS screen acquisition request from the PC10, it sends the EWS screen data corresponding to the request to the PC10 (S101). The EWS screen is a type of Web page data. When the PC10 receives the EWS screen data from the MFP100, it displays the EWS screen on the browser screen. The PC10 waits until the administrator login password is entered from the login password input field provided in this EWS screen (S202: NO). When the administrator login password is entered (S202: YES), it sends an authentication request with the entered administrator login password to the MFP100 (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 input administrator login password is correct (S103). In this determination, if the input administrator login password is incorrect (S103: NO), the CPU 101 sends a message indicating that login is not allowed to the PC 10. On the other hand, if the input administrator login password is correct (S103: YES), the CPU 101 sends the post-login page data of the EWS screen to the PC 10 (S104).

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

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

[0046] Figures 6 and 7 show the procedures for reception & printing processing. In Figure 6, first, the CPU 101 determines whether or not it has started receiving a print job (S1). Specifically, the CPU 101 determines whether data is stored in the reception buffer. If it is stored, the CPU 101 determines whether the data is a print job. Further, if it is a print job, the CPU 101 determines whether the head 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 the outside of 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 the outside of the MFP 100, and various notifications performed by the CPU 101 for reception & printing processing may also be stored in the reception buffer. For example, the notification in S78 (Figure 10) may be performed by storing information for specifying the image data to be printed, specifically, information indicating the location where the image data is stored, in the reception buffer. In this embodiment, the print job is generated by the PC 10 and transmitted onto the communication network 40 from the PC 10, and the MFP 100 receives it via the network IF 108, or the MFP 100 receives it from the PC 10A (see Figure 1) connected via the local IF 109. Note that the PC 10A basically has the same configuration as the PC 10. That is, hereinafter, the description of the PC 10 also applies to the description of the PC 10A.

[0047] Figure 5 shows an example of the data configuration of the print job 200. As shown in Figure 5, the print job 200 has a configuration in which the PDL is surrounded by the PJL. Note that PDL is an abbreviation for page description language, and PJL is an abbreviation for printer job language. The head of the print job 200 is " <esc>Indicated by " <esc>It is indicated by "%-12345X". Therefore, when the print job to be received in S1 is the print job 200, the CPU 101 determines whether the reception of the print job has started or not from the received data " <esc>It makes a determination based on whether or not "%-12345X@PJL" is detected. Also, the print job 200 includes information such as the name of the print job, test.txt, the user name, suzuki, and the generation date and time, 20210413201010. Note that the data configuration of the print jobs received by the MFP 100 may be different from the data configuration of the print job 200. However, for the sake of explanation in this embodiment, it is assumed that the MFP 100 receives print jobs with the same data configuration as the print job 200.

[0048] Returning to FIG. 6, in the determination of S1 above, when the reception of a print job is started (S1: YES), the CPU 101 determines whether or not the print job is a print job corresponding to the 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)), it is determined as "YES". Note that the same user may use different user names on the MFP 100 and the PC 10. Therefore, the main body LoginUser name used in the MFP 100 and the PcUser name used in the PC 10 included in the print job are associated 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 when 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 as "YES" in S2 if the main body LoginUser name associated with the PcUser name included in the received print job is registered in the user DB 104a. For example, when the received print job includes "kato" as the PcUser name, since the PcUser name "kato" and the main body LoginUser name "kat" are registered in the user DB 104a in an associated manner, the CPU 101 determines as "YES" in S2.

[0049] In the determination of S2, if the print job for which reception has started is a print job corresponding to the registered main body LoginUser name (S2: YES), the CPU 101 displays the reception in-progress screen on the display unit 105a of the panel 105 (S3).

[0050] In the above table data 104b, as internal states of the MFP 100 indicating that a print job is being received, there are three types: "Receiving Print Job", "Receiving Print Job (Printer Instruction Sender Logged In)", and "Receiving Print Job (Via USB Connection)". Therefore, when starting to receive a print job (S1: YES), the CPU 101 needs to determine which current internal state it corresponds to, for example, before proceeding to the above S2. First, the CPU 101 determines whether the received print job is from the network IF 108 or from the local IF 109. Since the print job from the network IF 108 and the print job from the local IF 109 are stored in different areas of the above receive buffer, the CPU 101 can determine from which of the network IF 108 and the local IF 109 the received print job is. And if the received print job is from the network IF 108, the CPU 101 further determines whether the print job started to be received while the printer instruction sender was logged in. When there is a logged-in user, as described in S76 of the above login process (Figure 10), since the selected LoginUser name is stored on the RAM 103, the CPU 101 determines whether the selected LoginUser name matches the PcUser name included in the print job. If they do not match, the CPU 101 determines whether the PcUser name included in the print job matches the main body LoginUser name associated with the user DB 104a and the selected LoginUser name. When the selected LoginUser name matches the PcUser name included in the print job, the CPU 101 writes "Receiving Print Job (Printer Instruction Sender Logged In)" to the above internal state storage area. The same applies when the main body LoginUser name associated with the PcUser name matches the selected LoginUser name. On the other hand, when the selected LoginUser name does not match the PcUser name included in the print job and the main body LoginUser name associated with the PcUser name does not match the selected LoginUser name, the CPU 101 writes "Receiving Print Job" to the internal state storage area.Also, when it is a print job received from the local IF 109, the CPU 101 writes "Print job receiving (via USB connection)" to the internal state storage area. Note that in this embodiment, the local IF 109 employs a USB IF as described above.

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

[0052] In the above display process (FIG. 9), when the CPU 101 does not detect a key notification or a touch operation notification (S52: NO), the CPU 101 determines whether the screen ID written in the screen ID storage area has changed (S59). When the screen ID has changed (S59: YES), the CPU 101 reads the display screen data associated with the changed screen ID from the NVM 104 and displays it on the display unit 105a to update the screen (S60).

[0053] Figure 2(b) shows an example of the receiving screen (screen ID = 101) 105a2 displayed on the display unit 105a. The receiving screen 105a2 is composed of a display area 105a21 for displaying the internal state of the MFP 100 and a display area 105a22 for displaying the operation state of the MFP 100. Figure 3(d) shows an example of the receiving screen (screen ID = 105) 105a8 displayed on the display unit 105a. The receiving screen 105a8, similar to the receiving screen 105a2, is composed of a display area 105a81 for displaying the internal state of the MFP 100 and a display area 105a82 for displaying the operation state of the MFP 100. Although the screen IDs of the receiving screen 105a2 in Figure 2(b) and the receiving screen 105a8 in Figure 3(d) are different, the display contents of the screens are the same. However, the lighting / extinguishing states of the three keys 105b1 to 105b3 of the key input unit 105b are different between Figure 2(b) and Figure 3(d). The lighting / extinguishing control of these keys 105b1 to 105b3 is performed within the above panel operation process (Figure 8).

[0054] In the determination of S31 in Figure 8, when no panel operation on the panel 105 is detected (S31: NO), the CPU 101 determines whether the screen ID written in the screen ID storage area has changed in the same manner as S59 (Figure 9) (S38). In this determination, when the screen ID has changed (S38: YES), the 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 the table data 104b, lights the keys that can be pressed and extinguishes the keys that cannot be pressed (S41). That is, when the internal state is "receiving a print job", as shown in Figure 2(b), all three keys 105b1 to 105b3 are extinguished, and when the internal state is "receiving a print job (print requester logged in)" or "receiving a print job (via USB connection)", as shown in Figure 3(d), only the cancel key 105b3 is lit and the other keys 105b1, 105b2 are extinguished. Thus, the lighting / extinguishing of the keys 105b1 to 105b3 corresponds to the validity / invalidity of each key 105b1 to 105b3.

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

[0056] In the determination of S4 above, if the accumulation printing function is enabled (S4: YES), the CPU 101 performs RIP processing on the print data included in the print job (S5), and accumulates the image data after the RIP processing in a predetermined area on the RAM 103 in association with the user name of the user who sent the base print job (S6). Specifically, the CPU 101 also stores the body LoginUser name in association with the image data when it is determined in S2 that the PcUser name included in the print job matches any of the body LoginUser names registered in the user DB 104a, or when it is determined in S2 that the body LoginUser name associated with the PcUser name included in the received print job is registered in the user DB 104a.

[0057] Next, the CPU 101 determines whether or not the accumulation of the image data onto the RAM 103 has been completed (S7). If the accumulation of the image data onto the RAM 103 has not been completed yet (S7: NO), the CPU 101 determines whether or not a cancel key notification has been received (S8). If a cancel key notification has not been received (S8: NO), the CPU 101 returns the process to S7 above. On the other hand, in the determination of S8, if a cancel key notification has been received (S8: YES), the CPU 101 cancels the accumulation of the image data onto the RAM 103 in the middle (S9), and then advances the process to S16. Also, while receiving a print job, when the CPU 101 performs RIP processing on the print job and is accumulating image data, not only the accumulation is canceled, but also the reception of the print job is canceled. Here, the cancel key notification is made in S56 of the above display process (FIG. 9). Since it has been determined in S34 of the above panel operation process (FIG. 8) whether or not the cancel key 105b3 can be pressed before that, the control of the cancel key notification will be described below based on the related processes in the panel operation process and the display process.

[0058] In the determination of S32 in FIG. 8, when the detected panel operation is a key operation on the key input unit 105b (S32: YES), the CPU 101 confirms the internal state stored in the internal state storage area in the same manner as in S40 above (S33). Next, the CPU 101 refers to the table data 104b (FIG. 4(b)) and determines whether the key operation is an operation of a key that can be pressed in the current internal state (S34). In the table data 104b, when the current internal state is "print job receiving", the availability of pressing the return key 105b1, home key 105b2, and cancel key 105b3 of the key input unit 105b is all "NG". Therefore, in this case, for any key operation of keys 105b1 to 105b3, the determination in S34 is "NO". On the other hand, when the current internal state is "print job receiving (print requester logged in)" or "print job receiving (via USB connection)", the availability of pressing the return key 105b1 and home key 105b2 is "NG", but the availability of pressing the cancel key 105b3 is "OK". Therefore, in this case, if it is a key operation of the cancel key 105b3, the determination in S34 is "YES".

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

[0060] Next, when the process proceeds to the above S52 of the display process (FIG. 9), there are cases where a key notification is stored in the key notification storage area and cases where it is not stored. 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. Now, when a key notification is stored in the key notification storage area, no touch operation notification is stored in the touch operation notification storage area. The CPU 101 detects a key notification (S52: YES), and when the detected key notification indicates that the valid home key 105b2 has been pressed (S53: YES), the process returns to S51 to display the home screen on the display unit 105a.

[0061] In the determination of S53, when the invalid home key 105b2 is pressed or the home key 105b2 itself is not pressed (S53: NO), the CPU 101 checks the currently displayed screen (S54). This check is performed by checking the screen ID written in the above screen ID storage area as described above. Then, the CPU 101 determines whether a process for which a panel operation notification should be made is being executed based on the confirmed screen (S55). As described above, when the screen ID is 101 to 105, the CPU 101 determines that the reception & printing process of FIG. 6 is being executed as a process for which a panel operation notification should be made (S55: YES), and the CPU 101 notifies the key of the key notification to the process for which a panel operation notification should be made (S56). For example, as shown in FIG. 3(d) above, when the cancel key 105b3 that is lit on the key input unit 105b is pressed while the reception screen 105a8 is displayed on the display unit 105a, the CPU 101 determines "YES" in S52 and also determines "YES" in S55. Therefore, information specifying the cancel key 105b3 related to the key notification is notified to the reception & printing process. In the reception & printing process, when the CPU 101 receives this notification before the accumulation of the drawing data is completed (S7: NO) (S8: YES), the accumulation of the drawing data is cancelled halfway (S9). Although the screen ID is not specified, a screen ID is also assigned to the screen displayed in the above login process (FIG. 10) and the menu screen described later. Therefore, the CPU 101 can determine that a panel operation notification should be made to the login process when the user list is displayed and when the PIN input screen is displayed, and can determine that a panel operation notification should be made to the reception & printing process when an operation for instructing the main body report printing is performed while the menu screen is displayed.

[0062] Note that the pressing operation on the cancel key 105b3 includes a short press (an example of "first cancel instruction") and a long press (an example of "second cancel instruction"). For example, when the current internal state is "receiving a print job (the print instructor is logged in)", the print job included in one of the multiple transmitted jobs may be in the middle of being 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. 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 while the long press is being made. That is, if multiple print jobs are received while the long press is being made, the reception of those multiple print jobs will be cancelled. Whether the cancel key 105b3 can be pressed in S34 above applies to both the case of a short press and the case of a long press. Note that as described above, when the CPU 101 is receiving one job and storing the image data based on that job, regardless of whether the key operation is a short press or a long press, the reception of that job is also cancelled.

[0063] On the other hand, as shown in FIG. 2(b) above, when the cancel key 105b3 that is off is pressed on the key input unit 105b while the reception screen 105a2 is being displayed on the display unit 105a, the CPU 101 determines "NO" in S52 and does not proceed with the process to S56. Therefore, the CPU 101 does not notify the reception & printing process of the information identifying the cancel key 105b3 related to the key notification. As a result, in the reception & printing process, since the CPU 101 does not receive this notification (S8: NO), the accumulation of image data is completed without being canceled midway (S7: YES). Thus, when the internal state is "print job reception in progress", the reception of the print job in the "print job reception in progress" cannot be canceled by the cancel key 105b3. Thereby, the MFP 100 of the present embodiment can prevent a person other than the user who transmitted the print job for accumulation, which is transmitted from the PC 10 via the network and is located far from the MFP 100, from canceling the reception of the print job for accumulation during the reception of the print job for accumulation. In the present embodiment, when a key that is off is pressed, although the key press operation itself is accepted (see S32 of the panel operation process), the process corresponding to the pressed key is not performed (see S34 of the panel operation process). However, the present invention is not limited to this, and when a key that is off is pressed, the key press operation itself may not be accepted.

[0064] On the other hand, in the determination of S7 above, when the accumulation of the image data on the RAM 103 is completed (S7: YES), the CPU 101 proceeds with the process to S16. In S16, the CPU 101 causes the home screen to be displayed on the display unit 105a of the panel 105. Specifically, the CPU 101 writes the screen ID "100" into the above-mentioned screen ID storage area on the RAM 103. Note that before performing the process of S16, the CPU 101 writes "operation completed" into the above-mentioned internal state storage area. As a result, in S16, the CPU 101 refers to the table data 104b and writes the screen ID "100" when the internal state is "operation completed" into the screen ID storage area. Therefore, by S60 of the above-mentioned display process, the home screen is displayed on the display unit 105a. After the process of S16, the CPU 101 returns the process to the above-mentioned S1.

[0065] On the other hand, in the determination of S4, when the accumulation printing function is invalid (S4: NO), the CPU 101 RIP-processes the print data included in the print job in the same manner as in S5 (S10). Then, the CPU 101 causes the print-in-progress screen to be displayed on the display unit 105a of the panel 105 (S11). Specifically, the CPU 101 writes the screen ID "102” to the screen ID storage area on the RAM 103. Note that before performing the process of S11, the CPU 101 writes "printing image data" to the internal state storage area. As a result, in S11, the CPU 101 refers to the table data 104b and writes the screen ID "102” when the internal state is "printing image data" to the screen ID storage area, so that the print-in-progress screen is displayed on the display unit 105a. FIG. 3(a) shows an example of the print-in-progress screen (screen ID = 102, 103) 105a5 displayed on the display unit 105a. The print-in-progress screen 105a5 is composed of a display area 105a51 for displaying the internal state of the MFP 100 and a display area 105a52 for displaying the operation state of the MFP 100. Further, the CPU 101 starts printing by outputting the image data after RIP processing to the print engine 111 (S12).

[0066] Next, the CPU 101 determines whether printing has been completed (S13). In this determination, when printing is not completed (S13: NO), the CPU 101 determines whether a cancel key notification has been received in the same manner as in S8 (S14). When a cancel key notification has not been received (S14: NO), the CPU 101 returns the process to S13. On the other hand, in the determination of S14, when a cancel key notification has been received (S14: YES), the CPU 101 cancels the printing in the middle (S15) and then proceeds to S16 with the process.

[0067] Fig. 3(a) also shows the key input unit 105b when the internal state is "printing picture data". In this key input unit 105b, only the cancel key 105b3 is lit, and the other keys 105b1, 105b2 are turned off. That is, the state of this key input unit 105b is the same as the state of the key input unit 105b in Fig. 3(d) above. Therefore, when the internal state is "printing picture data", since the cancel key 105b3 is valid, if the printing of the picture data is not completed (S13: NO), when the cancel key 105b3 is pressed, the CPU 101 receives the key notification of cancellation (S14: YES) and cancels the printing of the picture data in the middle (S15). Thus, when the internal state is "printing picture data", the printing of the picture data being printed can be canceled by the cancel key 105b3. In this case, since the printing of the picture data being printed is not by the accumulation printing function, the cancellation of the printing is recognized.

[0068] On the other hand, in the determination of S13 above, if the printing is completed (S13: YES), the CPU 101 proceeds to S16 for processing.

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

[0070] On the other hand, in the determination of S1 above, if the reception of the print job is not started (S1: NO), the CPU 101 determines whether an external main body report print instruction has been received (S20 in Fig. 7). This determination is also made by the CPU 101 according to whether an external main body report print instruction is stored in the reception buffer, specifically, whether the notification by the above S105 (Fig. 11) has been received.

[0071] In the determination of S20, when receiving an instruction to print the main body report from the outside (S20: YES), the CPU 101 causes the print-in-progress screen to be displayed on the display unit 105a of the panel 105 (S21). Specifically, the CPU 101 writes the screen ID "104" into the above-mentioned screen ID storage area on the RAM 103. Note that before performing the process of S21, the CPU 101 writes "Printing the main body report by external instruction" into the above-mentioned internal state storage area. This writing timing is not limited to this, and may also be the timing before or after the CPU 101 receives and notifies the instruction to the print process in response to receiving the main body report print instruction transmitted by the PC 10 in S204 (FIG. 11). Thus, in S21, since the CPU 101 refers to the table data 104b and writes the screen ID "104" when the internal state is "Printing the main body report by external instruction" into the screen ID storage area, the print-in-progress screen is displayed on the display unit 105a by the display process of S60. FIG. 3(c) shows an example of the print-in-progress screen (screen ID = 104) 105a7 displayed on the display unit 105a. Similar to the print-in-progress screen 105a5 (FIG. 3(a)), the print-in-progress screen 105a7 is composed of a display area 105a71 for displaying the internal state of the MFP 100 and a display area 105a72 for displaying the operation state of the MFP 100. Next, after the CPU 101 starts printing by generating the image data of the instructed main body report and outputting it to the print engine 111 (S22), the process proceeds to S13 (FIG. 6).

[0072] Fig. 3(c) also shows the key input section 105b when the internal state is "printing the main body report according to an external instruction". In this key input section 105b, all three keys 105b1 to 105b3 are turned 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. 2(b) above. Therefore, when the internal state is "printing the main body report according to an external instruction", since the cancel key 105b3 is invalid, 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 the key notification of cancellation (S14: NO), and the printing of the main body report is completed without being cancelled halfway (S13: YES). Thus, when the internal state is "printing the main body report according to an external instruction", the printing of the main body report being printed cannot be cancelled by the cancel key 105b3. Thereby, for example, it becomes possible to prevent others who are not the user of the PC 10 from cancelling the printing of the main body report during the printing of the main body report according to an external instruction from the PC 10.

[0073] On the other hand, in the determination of S20 above, when an external main body report printing instruction is not received (S20: NO), it is determined whether a main body report printing instruction is notified from the panel 105 (S23). The main body report printing instruction can be issued not only from the outside as described above but also from the display section 105a of the panel 105. Specifically, for example, when the home screen 105a1 (Fig. 2(a)) is displayed on the display section 105a and a menu button (not shown) within the home screen 105a1 is touched, the above menu screen is displayed, and when the main body report printing instruction is touched and operated on that menu screen, the CPU 101 receives the main body report printing instruction and notifies it to the printing process.

[0074] In the determination of S23, when a main body report printing instruction is notified from the panel 105 (S23: YES), the CPU 101 causes the printing screen to be displayed on the display unit 105a of the panel 105 (S24). Specifically, the CPU 101 writes the screen ID "103" into the screen ID storage area on the RAM 103. Note that before performing the process of S24, the CPU 101 writes "Printing main body report according to panel instruction" into the internal state storage area. This writing timing is not limited to this, and it may also be the timing before or after receiving the touch operation of the main body report printing instruction from the menu screen and notifying the main body report printing instruction to the printing process. Thereby, in S24, the CPU 101 refers to the table data 104b and writes the screen ID "103" when the internal state is "Printing main body report according to panel instruction" into the screen ID storage area. Therefore, by the display process of S60, the printing screen is displayed on the display unit 105a. The printing screen 105a5 in FIG. 3(a) serves as both the printing screen with the screen ID "102" and the printing screen with the screen ID "103". Next, the CPU 101 proceeds with the process to S22.

[0075] The key input unit 105b in FIG. 3(a) serves as both the key input unit 105b when the internal state is "Printing picture data" and the key input unit 105b when the internal state is "Printing main body report according to panel instruction". Therefore, when the internal state is "Printing main body report according to panel instruction", similar to when the internal state is "Printing picture data", the cancel key 105b3 is valid. Thus, when the printing of the main body report is not completed (S13: NO) and the cancel key 105b3 is pressed, the CPU 101 receives the key notification of cancellation (S14: YES) and cancels the printing of the main body report in the middle (S15). In this way, when the internal state is "Printing main body report according to panel instruction", the printing of the main body report being printed can be cancelled 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 himself / herself.

[0076] On the other hand, in the determination of S23, when the main body report print instruction is not notified from the panel 105 (S23: NO), the CPU 101 determines whether a print instruction for the stored frame data has been notified (S25). The print instruction for the stored frame data is notified in S78 of the above login process.

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

[0078] On the other hand, in the determination of S25, if the print instruction for the stored image data is not received (S25: NO), the CPU 101 returns the process to S1 (FIG. 6).

[0079] In this embodiment, when a cancel key notification is received during the reception of a print job when the stored print function is valid (S8: YES), the reception of the print job is canceled (S9 above). Although it does not consider receiving a cancel key notification during the reception of a print job when the stored print function is invalid, this is not the only case. Even when the stored print function is invalid, when a cancel key notification is received, similar to when the stored print function is valid, the reception of the print job may be canceled. Thereby, the MFP 100 of this embodiment can prevent others other than the user who transmitted the stored print job from canceling the reception of the stored print job, at least during the reception of the stored print job transmitted from the PC 10 via the network and located far from the MFP 100.

[0080] Also, in this embodiment, when the receiving screen 105a2 is displayed on the display unit 105a, the pressing of the cancel key is not received and transmitted to the print process. However, when the receiving screen 105a8 is displayed on the display unit 105a, the pressing of the cancel key may also not be received and transmitted to the print process. Thereby, the MFP 100 of this embodiment can prevent others other than the user who transmitted the stored print job from canceling the reception of the stored print job, at least during the reception of the stored print job transmitted from the PC 10 via the network and located far from the MFP 100.

[0081] Also, when the internal state is "during print job reception (print instruction sender logged in)", the receiving screen 105a2 with the screen ID 101 may be displayed on the display unit 105a.

[0082] In this embodiment, as the key input unit 105b, one composed of three keys 105b1 to 105b3 that can switch the lighting state and the extinguished state for each key is adopted. However, it is not limited to this. Buttons corresponding to the three keys 105b1 to 105b3 may be displayed on the display unit 105a, and instead of the lighting / extinguishing control in S41, button display / non-display control may be performed.

[0083] Also, in this embodiment, as the local IF 109, a communication IF for local connection at a short distance is adopted. However, it is not limited to this. A communication IF of a system mainly assuming one-to-one connection may be used as the local IF. In that case, for example, a communication IF of the Bluetooth (registered trademark) system or the Wi-Fi Direct system may be used as the local IF. Also, a communication IF of a system mainly assuming temporary connection may be used as the local IF. In that case, for example, a communication IF of the Bluetooth system or the Wi-Fi Direct system may be used as the local IF.

[0084] Note that the present invention is not limited to the above embodiment, and various modifications are possible without departing from the spirit thereof.

[0085] (1) In the above embodiment, as an example of the printing apparatus, the MFP 100 is described as an example. However, the printing apparatus is not limited to the MFP 100, and a single printer may also be used.

[0086] (2) In the above embodiment, as an example of the controller, one CPU 101 is used. However, it is not limited to this, and a controller composed of a plurality of CPUs may be used, or one including a CPU composed of a plurality of cores may be used. Also, it may have a CPU and a dedicated circuit. Examples of the dedicated circuit include an ASIC and an FPGA.

Explanation of Reference Numerals

[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 matches the input user name, 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, The determination process determines whether or not the receiving user name included in the print job for which the cancellation instruction is given matches the input user name; 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 when 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